A
AC Question
I use three browsers, Firefox, Opera, and Yandex, and each can leave a background process that eats down the battery.
The browsers have been exited, and if necessary exited in the Task Mngr, but the browser background processes showing in settings/battery cannot be stopped. In settings/battery I can click the process then click Force Stop but it does not stop. Restarting the phone does not remove or stop these processes.
The browser apps have to be uninstalled to get rid of the background processes. As the problem can occur randomly (today, tomorrow, three days from now) I would be uninstalling/reinstalling multiple times a week.
I called T-Mobile; no help. I called Samsung; no help.
If this problem cannot be fixed such that I shouldn’t use these browsers on the S3 then it is just a dumb phone. I hesitate to upgrade to a new phone as this problem could still occur.
Please do not tell me to not use these browsers. There are features in each that I use. Three browsers from three difference vendors all cannot have the same bug. I think this is an Android service level bug.
Samsung Galaxy S3
SGH-T999
Android v4.3
The browsers have been exited, and if necessary exited in the Task Mngr, but the browser background processes showing in settings/battery cannot be stopped. In settings/battery I can click the process then click Force Stop but it does not stop. Restarting the phone does not remove or stop these processes.
The browser apps have to be uninstalled to get rid of the background processes. As the problem can occur randomly (today, tomorrow, three days from now) I would be uninstalling/reinstalling multiple times a week.
I called T-Mobile; no help. I called Samsung; no help.
If this problem cannot be fixed such that I shouldn’t use these browsers on the S3 then it is just a dumb phone. I hesitate to upgrade to a new phone as this problem could still occur.
Please do not tell me to not use these browsers. There are features in each that I use. Three browsers from three difference vendors all cannot have the same bug. I think this is an Android service level bug.
Samsung Galaxy S3
SGH-T999
Android v4.3