▲ 238 ▼ A compulsory mandated app installed on every Indian citizen's new phone (lemmy.ml) submitted 11 months ago by cm0002@mander.xyz to c/privacy@programming.dev 35 comments fedilink hide all child comments https://www.livemint.com/news/india/if-you-don-t-want-jyotiraditya-scindia-says-sanchar-saathi-app-is-optional-amid-strong-opposition-protests-11764659707854.html
[–] biotin7@sopuli.xyz 21 points 11 months ago* (last edited 11 months ago) (4 children) But is it illegal to remove it ? Well then use ADB permalink fedilink source hideshow 4 child comments replies: [–] brbposting@sh.itjust.works 33 points 11 months ago (3 children) Read the article Then you’ll still have no idea like me :) permalink fedilink source parent hideshow 3 child comments replies: [–] DahGangalang@infosec.pub 18 points 11 months ago (2 children) Union Minister for Communications Jyotiraditya Scindia claimed on Tuesday that the Sanchar Saathi app, a fraud reporting app the government wants pre-installed on all devices, will be optional and can be deleted by users. “... If you don't want Sanchar Saathi, you can delete it. It is optional... It is our duty to introduce this app to everyone. Keeping it in their devices or not is up to the user,” he said to reporters. So it sounds like it can be removed, though I can't help but feel like it might leave malicious artifacts (this is based on absolutely no evidence and is purely speculation on my part) permalink fedilink source parent hideshow 2 child comments replies: [–] 0_o7@lemmy.dbzer0.com 7 points 11 months ago (1 child) In recent Android devices, you can disable and even uninstall apps for users. But for some system apps, when you go back the disabled apps info page, the "Force Stop" button isn't greyed out like it should be anymore. Like why is the force stop button active when the app is disabled. And this usually happens in OEM devices stock ROMs, not on custom ROMs afaik. It's either a bug or intentional. Can't tell. permalink fedilink source parent hideshow 1 child comment replies: [–] DahGangalang@infosec.pub 5 points 11 months ago Did a pinch of digging and this Stack Overflow Question seems to be the best "all in one" answer to your question. To try to explain from what I'm seeing: Disable stops any "autostart" services/processes from starting. It also tries to gracefully stop any background processes and services. Force Stop kills those processes forcefully (but doesn't necessarily stop them from auto starting again). Its possible (though unlikely) for you to Disable an app and there to be a delay for all processes and services to die. Thus it can be useful to Disable, then Force Stop if you really want something dead. That said, in most cases it looks like its more likely to be a "UI Bug". Theoretically, if no processes are running for an app, the Force Stop button is supposed to be deactivated (greyed out), but this check is apparently not very authoritatively checked, and defaults to Active if the OS isn't sure. Hopefully any wrong info I've stated will summon a true expert to explain better. permalink fedilink source parent
[–] brbposting@sh.itjust.works 33 points 11 months ago (3 children) Read the article Then you’ll still have no idea like me :) permalink fedilink source parent hideshow 3 child comments replies: [–] DahGangalang@infosec.pub 18 points 11 months ago (2 children) Union Minister for Communications Jyotiraditya Scindia claimed on Tuesday that the Sanchar Saathi app, a fraud reporting app the government wants pre-installed on all devices, will be optional and can be deleted by users. “... If you don't want Sanchar Saathi, you can delete it. It is optional... It is our duty to introduce this app to everyone. Keeping it in their devices or not is up to the user,” he said to reporters. So it sounds like it can be removed, though I can't help but feel like it might leave malicious artifacts (this is based on absolutely no evidence and is purely speculation on my part) permalink fedilink source parent hideshow 2 child comments replies: [–] 0_o7@lemmy.dbzer0.com 7 points 11 months ago (1 child) In recent Android devices, you can disable and even uninstall apps for users. But for some system apps, when you go back the disabled apps info page, the "Force Stop" button isn't greyed out like it should be anymore. Like why is the force stop button active when the app is disabled. And this usually happens in OEM devices stock ROMs, not on custom ROMs afaik. It's either a bug or intentional. Can't tell. permalink fedilink source parent hideshow 1 child comment replies: [–] DahGangalang@infosec.pub 5 points 11 months ago Did a pinch of digging and this Stack Overflow Question seems to be the best "all in one" answer to your question. To try to explain from what I'm seeing: Disable stops any "autostart" services/processes from starting. It also tries to gracefully stop any background processes and services. Force Stop kills those processes forcefully (but doesn't necessarily stop them from auto starting again). Its possible (though unlikely) for you to Disable an app and there to be a delay for all processes and services to die. Thus it can be useful to Disable, then Force Stop if you really want something dead. That said, in most cases it looks like its more likely to be a "UI Bug". Theoretically, if no processes are running for an app, the Force Stop button is supposed to be deactivated (greyed out), but this check is apparently not very authoritatively checked, and defaults to Active if the OS isn't sure. Hopefully any wrong info I've stated will summon a true expert to explain better. permalink fedilink source parent
[–] DahGangalang@infosec.pub 18 points 11 months ago (2 children) Union Minister for Communications Jyotiraditya Scindia claimed on Tuesday that the Sanchar Saathi app, a fraud reporting app the government wants pre-installed on all devices, will be optional and can be deleted by users. “... If you don't want Sanchar Saathi, you can delete it. It is optional... It is our duty to introduce this app to everyone. Keeping it in their devices or not is up to the user,” he said to reporters. So it sounds like it can be removed, though I can't help but feel like it might leave malicious artifacts (this is based on absolutely no evidence and is purely speculation on my part) permalink fedilink source parent hideshow 2 child comments replies: [–] 0_o7@lemmy.dbzer0.com 7 points 11 months ago (1 child) In recent Android devices, you can disable and even uninstall apps for users. But for some system apps, when you go back the disabled apps info page, the "Force Stop" button isn't greyed out like it should be anymore. Like why is the force stop button active when the app is disabled. And this usually happens in OEM devices stock ROMs, not on custom ROMs afaik. It's either a bug or intentional. Can't tell. permalink fedilink source parent hideshow 1 child comment replies: [–] DahGangalang@infosec.pub 5 points 11 months ago Did a pinch of digging and this Stack Overflow Question seems to be the best "all in one" answer to your question. To try to explain from what I'm seeing: Disable stops any "autostart" services/processes from starting. It also tries to gracefully stop any background processes and services. Force Stop kills those processes forcefully (but doesn't necessarily stop them from auto starting again). Its possible (though unlikely) for you to Disable an app and there to be a delay for all processes and services to die. Thus it can be useful to Disable, then Force Stop if you really want something dead. That said, in most cases it looks like its more likely to be a "UI Bug". Theoretically, if no processes are running for an app, the Force Stop button is supposed to be deactivated (greyed out), but this check is apparently not very authoritatively checked, and defaults to Active if the OS isn't sure. Hopefully any wrong info I've stated will summon a true expert to explain better. permalink fedilink source parent
[–] 0_o7@lemmy.dbzer0.com 7 points 11 months ago (1 child) In recent Android devices, you can disable and even uninstall apps for users. But for some system apps, when you go back the disabled apps info page, the "Force Stop" button isn't greyed out like it should be anymore. Like why is the force stop button active when the app is disabled. And this usually happens in OEM devices stock ROMs, not on custom ROMs afaik. It's either a bug or intentional. Can't tell. permalink fedilink source parent hideshow 1 child comment replies: [–] DahGangalang@infosec.pub 5 points 11 months ago Did a pinch of digging and this Stack Overflow Question seems to be the best "all in one" answer to your question. To try to explain from what I'm seeing: Disable stops any "autostart" services/processes from starting. It also tries to gracefully stop any background processes and services. Force Stop kills those processes forcefully (but doesn't necessarily stop them from auto starting again). Its possible (though unlikely) for you to Disable an app and there to be a delay for all processes and services to die. Thus it can be useful to Disable, then Force Stop if you really want something dead. That said, in most cases it looks like its more likely to be a "UI Bug". Theoretically, if no processes are running for an app, the Force Stop button is supposed to be deactivated (greyed out), but this check is apparently not very authoritatively checked, and defaults to Active if the OS isn't sure. Hopefully any wrong info I've stated will summon a true expert to explain better. permalink fedilink source parent
[–] DahGangalang@infosec.pub 5 points 11 months ago Did a pinch of digging and this Stack Overflow Question seems to be the best "all in one" answer to your question. To try to explain from what I'm seeing: Disable stops any "autostart" services/processes from starting. It also tries to gracefully stop any background processes and services. Force Stop kills those processes forcefully (but doesn't necessarily stop them from auto starting again). Its possible (though unlikely) for you to Disable an app and there to be a delay for all processes and services to die. Thus it can be useful to Disable, then Force Stop if you really want something dead. That said, in most cases it looks like its more likely to be a "UI Bug". Theoretically, if no processes are running for an app, the Force Stop button is supposed to be deactivated (greyed out), but this check is apparently not very authoritatively checked, and defaults to Active if the OS isn't sure. Hopefully any wrong info I've stated will summon a true expert to explain better. permalink fedilink source parent
