Recently it is using a ridiculous amount of data (started a few days ago). I checked the data usage and found the name: com.quicinc.cne.CNEService.CNEServiceApp. How do I disable it?
I don't think it's a service you can actually disable. It's part of the chipset and is used to determine whether a WiFi or data connection is stronger in real time and keep you on the stronger connection. My understanding is that all of your data goes through that service regardless of which app is actually using the data so thinking it's that service itself that's using all your data is backwards. That number is basically a catch all for the data used on your phone by other various apps and services.
jhs39 said:
I don't think it's a service you can actually disable. It's part of the chipset and is used to determine whether a WiFi or data connection is stronger in real time and keep you on the stronger connection. My understanding is that all of your data goes through that service regardless of which app is actually using the data so thinking it's that service itself that's using all your data is backwards. That number is basically a catch all for the data used on your phone by other various apps and services.
Click to expand...
Click to collapse
Is there any way to figure out what app or service is it?
LesterX said:
Is there any way to figure out what app or service is it?
Click to expand...
Click to collapse
Using Stock ROM? I had this some time ago. It's because it's downloading an OTA update in the background, failing to install because of custom recovery/root/something else, and retrying forever.
Some have suggested disabling automatic updates in dev settings, but for me it didn't fix it.
Flash the latest images and you'll be fine.
josdehaes said:
Using Stock ROM? I had this some time ago. It's because it's downloading an OTA update in the background, failing to install because of custom recovery/root/something else, and retrying forever.
Some have suggested disabling automatic updates in dev settings, but for me it didn't fix it.
Flash the latest images and you'll be fine.
Click to expand...
Click to collapse
Thanks. I did root the phone. I just turned off the automatic update, hope it'll work.
Like mentioned by josdehaes, having automatic updates turned off still allowed the usage on my rooted Verizon phone. I saw one person suggest the issue might be specific to rooted Verizon phones, but I have no idea if that's accurate or not. Since my phone is rooted with SuperSU, and because I don't have anything else like TWRP installed, I just started using FlashFire to update. Keeping the phone updated to the latest software has worked so far, and letting FlashFire install the OTA on the phone is a lot quicker than messing with factory images or sideloading the full OTA. If that wouldn't have worked, I thought about installing a ROM that doesn't use the OTA, since the only other procedure I've ran across for stopping stock updates kept my phone from going into deep sleep.
High CNEService can probably be caused by a hundred things other than a failed OTA update and if it actually was an OTA update you should see an Android notification mentioning the fact that there's an update. Having a rooted phone on stock does not stop OTA updates from downloading successfully and it certainly doesn't prevent the Android notification telling you that an update downloaded or is available for your phone. If you bother to do a Google search on your "problem' you will find that people complain about the same exact thing on an assortment of Android devices regardless of manufacturer and most of the people doing the complaining do not have rooted phones. It has nothing to do with Verizon and most probably nothing to do with what the earlier poster suggested.
jhs39 said:
Having a rooted phone on stock does not stop OTA updates from downloading successfully
Click to expand...
Click to collapse
Having a Pixel rooted with SuperSU certainly can stop an OTA update. Although my phone had been updating fine using the OTA before installing SuperSU, either SuperSU or the changes I made with root would no longer allow the OTA, even after SuperSU was removed.
If you bother to do a Google search on your "problem' you will find that people complain about the same exact thing on an assortment of Android devices regardless of manufacturer and most of the people doing the complaining do not have rooted phones. It has nothing to do with Verizon and most probably nothing to do with what the earlier poster suggested.
Click to expand...
Click to collapse
All the discussions I've read in the Pixel and Pixel XL forums that mention unexplainable and abnormally high cellular data usage, which the phone lists as being from a CNEService process, have been rooted phones that are not running the current update. As previously noted, it's the most likely guess, since that's the consensus from multiple threads. All I know for absolute certainty is that the Automatic system updates setting had been turned off, and my phone stopped the excessive data usage after updating to the current version. I had never seen any listings of which phones in the discussions were Verizon phones, so I'm not sure where the presumption came from that only Verizon phones might have been affected when automatic updates were turned off.
jhs39 said:
High CNEService can probably be caused by a hundred things other than a failed OTA update and if it actually was an OTA update you should see an Android notification mentioning the fact that there's an update. Having a rooted phone on stock does not stop OTA updates from downloading successfully and it certainly doesn't prevent the Android notification telling you that an update downloaded or is available for your phone. If you bother to do a Google search on your "problem' you will find that people complain about the same exact thing on an assortment of Android devices regardless of manufacturer and most of the people doing the complaining do not have rooted phones. It has nothing to do with Verizon and most probably nothing to do with what the earlier poster suggested.
Click to expand...
Click to collapse
Pixels redownloading the OTA's over and over while failing silently has been reported many times here. No idea why, but they are always modded or rooted phones and usually​ a VZ phone or a Google phone with a VZ SIM
alluringreality said:
Having a Pixel rooted with SuperSU certainly can stop an OTA update. Although my phone had been updating fine using the OTA before installing SuperSU, either SuperSU or the changes I made with root would no longer allow the OTA, even after SuperSU was removed.
All the discussions I've read in the Pixel and Pixel XL forums that mention unexplainable and abnormally high cellular data usage, which the phone lists as being from a CNEService process, have been rooted phones that are not running the current update. As previously noted, it's the most likely guess, since that's the consensus from multiple threads. All I know for absolute certainty is that the Automatic system updates setting had been turned off, and my phone stopped the excessive data usage after updating to the current version. I had never seen any listings of which phones in the discussions were Verizon phones, so I'm not sure where the presumption came from that only Verizon phones might have been affected when automatic updates were turned off.
Click to expand...
Click to collapse
I'm not saying that having a rooted phone on stock wouldn't stop an OTA from updating successfully --on any other phone besides a Pixel that would pretty much guarantee that an OTA would fail to install. What I'm saying is that the OTA would still download and you would still see an Android notifications informing you that either an update was available for your phone or that one was downloaded and ready to install. Even if you are rooted on stock or are using a stock based Rom it wouldn't normally interfere with either the download or the notification --only the ultimate installation of the OTA. The fact that turning off Automatic Updates lowered your reported CNEService usage also doesn't prove that the problem was actually a failed OTA update --it could be that turning off Automatic Updates stopped a background process that was misbehaving or corrupted on your phone. Reporting of high CNEService usage isn't any more common on rooted phones than unrooted ones and if it is actually a sign of a problem and not simply a misinterpretation of what the number means then a factory reset pretty much always fixes it.
People have also frequently reported that turning off both WiFi assistant and the scan for open networks options fixed the same problem on their phones, even though logically you would think that would do the opposite and make the problem worse. But Android likes to simplify things for users by grouping the numbers for multiple processes under the same header, which is apparently the case for that number which is why it can actually indicate different problems on different phones, providing that there actually is a problem in the first place. People sometimes see that number and freak out assuming that it represents separate data used completely apart from their other apps and services but that isn't the case.
I should have mentioned that turning off both WiFi Helper and the automatically connect to open networks setting solution to high CNEService data usage actually came from the official Pixel Support thread on Google. People on XDA probably assume the issue is related to root because people on XDA like to root--to a hammer everything looks like a nail. But the same issue is also common on phones running full stock.
Far as I can tell, the original poster indicated that they had a rooted phone and allowed automatic updates. Prior discussions appear to suggest that could correlate with these high data usage events. I'd still take the position that turning off the automatic update setting on a rooted phone is probably a decent suggestion. Based on my own experience, I hesitate to suggest that turning off automatic updates eliminates the possibility of high data usage happening on future updates.
jhs39 said:
The fact that turning off Automatic Updates lowered your reported CNEService usage also doesn't prove that the problem was actually a failed OTA update --it could be that turning off Automatic Updates stopped a background process that was misbehaving or corrupted on your phone.
Click to expand...
Click to collapse
Actually, that is not a fact in relation to my comments. I personally had Automatic Updates turned off before the update notification.
Reporting of high CNEService usage isn't any more common on rooted phones than unrooted ones and if it is actually a sign of a problem and not simply a misinterpretation of what the number means then a factory reset pretty much always fixes it.
Click to expand...
Click to collapse
Mainly I just take this sort of statement as merely a suggestion to consider other possible avenues in troubleshooting the situation, since I'm not sure what data someone might use that would be a necessarily superior choice. I probably did factory reset my phone after the high usage, so I suppose that might be an alternate explanation for it only happening one time.
People have also frequently reported that turning off both WiFi assistant and the scan for open networks options fixed the same problem on their phones, even though logically you would think that would do the opposite and make the problem worse.
Click to expand...
Click to collapse
I thought Wi-Fi scanning was always turned off on my phone, but one time when I was out of town I noticed it was actually on, so it's possible Wi-Fi scanning could have been on when I had my own high data usage event while ignoring the software update message. I think the Wi-Fi Assistant setting was most likely turned off.
People sometimes see that number and freak out assuming that it represents separate data used completely apart from their other apps and services but that isn't the case.
Click to expand...
Click to collapse
Again, I take this comment as merely a suggestion of alternate possibilities. The only thing out of the ordinary on my phone at the time was Google Earth, but it didn't seem to correlate with the usage, since the timeline didn't appear to match up and short-term use over Wi-Fi usually only reports as a few MB. I suppose with how Android automatically updates apps, maybe there was something on my phone at the time that was unusually using data that has since been corrected, yet I still don't see a clear reason to entirely discount the possibility that the event might have related with the software update being ignored.
Did anybody actually found a solution to this problem, or is it simply unsolvable?
dya said:
Did anybody actually found a solution to this problem, or is it simply unsolvable?
Click to expand...
Click to collapse
it would be nice if msomeone did bc I'm having this issue and it's driving me insane. tasker controls my connections. I use android so I don't have to rely on closed source apps
Just turned off mobile data or wifi and CNE is turned off,
If you want to remove this service just goto /vendor/app/cne.apk
...
CNE - Connectivity Engine is the brain of the modem driver or Qualcomm chipset driver.
...
Removing this service makes your device save a lots of power best for you.
...
Removing this service can soft brick your device or simply your device can't connect to the internet.
*From*
ROM Tester, ROM developer , Custom ROM Lover.
Related
i want to downgrade my htc one m8 from lolipop to kitkat 4 again. can you please help me i dont like this os . kitkat was perfect
mohamedabdallah2010 said:
i want to downgrade my htc one m8 from lolipop to kitkat 4 again. can you please help me i dont like this os . kitkat was perfect
Click to expand...
Click to collapse
You need to unlock/s-off to get 100% downgrade, or, you can unlock bootloader, flash twrp, and install a kittkatt custom rom.
thanks
thanks but i was on iphone i dont know whats all this. can you please tell me steps
It's not a case of following some steps. What you want is very technical and not for someone with no prior knowledge of rooting Android phones.
What don't you like about lollipop? It's no different, visually, to Kit Kat on the M8
slower
its slower and more battery consume and i dont like the notifications
mohamedabdallah2010 said:
its slower and more battery consume and i dont like the notifications
Click to expand...
Click to collapse
Sounds like you update by OTA. In which case, updating by OTA and keeping user data is often the root of random issues. Try backing up any important personal data and doing a factory reset (to wipe user data - and NO this will not return you to a former OS version as some folks mistakenly believe). Lollipop isn't slower than KitKat in any significant way that I've noticed. You're probably seeing bugs due to conflicts with pre-existing user data (settings and apps).
Battery consumption may be due to the new radio. But it might also be a bug caused by pre-existing data, or you may just need to do a full charge-discharge cycle to properly calibrate the battery meter (mandatory after a major OS update).
Also, OTAs contain important security updates. So it should be considered that you won't have these if you "downgrade".
Something to consider - do you use Facebook Messenger? Turns out since the new Google Play services it's been eating battery like no one's business! Read the reviews on the Play Store for proof but it does seem to be linked to Lollipop and (for me) Google Play services 6.7.74
There's bugs even in OTA updates from 4.4.4 seems most if not all manufacturers having problems and they can really screw your handset up - apps consuming battery (not just Play Store) bad mobile internet, losing Wi-Fi , corrupting system, removing apps, deleting SDCard data.
Probably due to crap OTA "patched" system updates. Myself, once handset is back from warranty repair (12 days use, 4 of which OTA stuffed it up) I'll not use OTA again that's for sure.
Bashing away at my HTC Desire C
Since I've removed Facebook Messenger my phone is back to normal, battery life as it was on 4.4.4 and everything is OK so I'm happy (don't use FB Messenger enough to warrant having it!)
thanks
thank you all about reply's. i searched google and i see all people talking about battery and fb messanger on all phones. so you recommend to me to stay on lollipop ? but i dont like really this notification control
So I'm not alone in facing issues with Lollipop
When I update, I was getting terrible battery life so I performed a hard reset from bootloader.
Now almost everything is fine but Google Play Services, more specifically "Mobile radio active" has been eating into the standby time, not like before but still bad, goes on upto 3 hours. "Keep awake" also goes on upto 2 hours.
Any fix or suggestions would be helpful. I don't use Messenger and Facebook, as they were the major battery eaters.
Rather than keeping an eye on pointless stats, how long does your battery actually last? I honestly think people are making up issues. Now, the FB Messenger HAS been eating battery but once I removed that my battery life went back to normal
My battery was better but mobile data was screwed, WiFi only showing my router and no others, never used facebook (so it's not that app alone) blinkfeed consumed 46% of battery use. All on 4.4.4 update so to say people are making a big issue of it, yeah damn right, it was 100% better without the update!
Bashing away at my HTC Desire C
But that's your individual issue between your phone/router/apps/etc. I've had zero issues with Lollipop bar this one with FB Messenger since the new Google Play services so I uninstalled it and now I'm back to running perfectly so clearly the OTA update isn't the issue
Have you done a factory reset to clear out anything left over from 4.4.4? It's always recommended to do so, as annoying as it is, when moving to a new version of Android. I set my phone up from scratch and have no problems with 5.0.1
I have done... Update still goosed it, so maybe you having no problems it's you that's the lucky one! That's why it's back at HTC!
If these patched updates were any good nobody would have issues!
Makes more sense than... It's just your issue!
Bashing away at my HTC Desire C
---------- Post added at 07:47 PM ---------- Previous post was at 07:31 PM ----------
Uninstalling facebook so obviously not stock so the fact you're flashing quite possibly other ROM's negates your lack of problems. Fully stock phone updated worked worse than what I'm using now. Full stop.
There is also the fact I was told by my phone supplier that problems with updates are industry wide since 4.4.4 and if all the update are, are patches, then it's not going to be a quick fix, like it's known there's variations in the handsets with the carriers.
Bashing away at my HTC Desire C
If there were issues they'd pull the update and there'd be more media coverage. I've not flashed anything on my phone, I'm 100% stock and I've not rooted a phone in well over a year. My phone is running the latest Sense build released and have no issues. Now I only use about ten third party apps so it could just be that that means I'm not having issues. Or it could be I close all apps once I've finished with them. I don't know. But I don't think there's anything wrong with what HTC have released
Doesn't explain the problems people are having, my handset was working 100% A-ok the update which I never applied or accepted stuffed it, maybe it's not in the media because it's not affecting, like yourself, people who don't use it as heavily as others, like I said I've been told the industry is having problems with them, maybe the lucky ones less or not affected are low use.
Bashing away at my HTC Desire C
Who told you the industry is having issues, though? I've not heard of Samsung of LG owners having issues, nor those with Nexus devices (well, not huge numbers of people anyway!), so I don't think Lollipop as a whole is the issue at all. Now, I'm not saying people don't have issues, but I think those issues are down to individual setups (apps installed, usage, even the components used in that particular handset). Perhaps I am lucky, but if I am I've been lucky with every phone I've ever owned
thank you all . here is what i did. i did a hard reset and restored my data then installed whatsapp only and now my battery is back to be very good as it was on kitkat and better. i will install every single app one a day to check which one eating the battery. and i will update you with details. and i see much people talking about this issue on other sites and other handsets.thanks
For me battery works good sometimes and then suddenly starts losing charge during standby, so I check and find Mobile Radio Active has been eating away the battery, while this was not the case with 4.4.4. Even with FB and Messenger installed I didn't have any problems but now I do. I uninstalled both so battery is better than what it was with them but still I lose charge mysteriously in standby randomly.
Root developers are saying don't take the updates. Few people are reporting that the updates made anything better. Don't take the updates if you can help it.
Follow the instructions below, and report back with your phone info (carrier, variant, software version, etc.). Also report if updates were successfully blocked, or if they installed anyway, or if you just get a nag screen. Thanks!
If your phone has already downloaded the update and is trying to install it, follow the advice here. This won't work for AT&T phones because they removed recovery mode.
Start here:
Get debloater (works without root!) and set up your computer so you can run ADB and connect with your phone. You may need to install the LG United Mobile Driver.
Please donate to the Debloater developer, gatesjunior! Debloater has made this so much easier!
There are many packages you can block that will improve the performance and battery life of your phone (see my blocked.txt below), but the packages you want to block that will hopefully prevent updates are:
LGDMSClient.apk (Blocking breaks WiFi calling setup on Sprint only.)
LGUpdateCenter.apk
LGFOTA.apk Two users reported calls going straight to voicemail with this blocked.
LGLDB.apk I don't know if it's related to updates but it seems to be MLT spyware.
Not all carriers will have all these files, but block what you do have and report any problems so I can update this post with what works and what doesn't
Carrier specific files:
Sprint users may want to block:
Sprint_Installer.apk
ItsOnService.apk
ItsOnUID.apk
Tierez reported that blocking the ItsOn files breaks WiFi. They also reported that blocking LGDMSClient.apk broke the WiFi calling setup screen.
Verizon users should block:
VerizonIgnite.apk, It's a post-sale bloatware installer. Thanks alan242!
@JeffXT inadvertently blocked a Verizon file that enabled tethering.
AT&T users should block:
WildTangent.apk
T-Mobile users should block:
AdaptClient.apk
This will break the software update screen in about phone and so far has prevented my phone from trying to update. My AT&T H810 hasn't tried to update and I can't force it to update since I blocked LGDMSClient.apk, but it seems we can't be too safe in preventing forced updates so leave no questionable package unblocked!
Something I also did during setup was to not agree to the optional LG EULA that would have allowed app updating. I've also blocked:
LGStartupEula.apk
LicenseProvider.apk
UnifiedEULA.apk
Don't block LGSystemServer.apk, it breaks notifications and other stuff (LED, sound, and vibration).
Autoprime is listing which software versions are updating the firmware to V1 here.
Good luck!
Don't block LGSystemSetup.apk or LGSetupWizard.apk! You'll need it to run if there phone gets reset. Ignore the blocked.txt file below.
phineous said:
After seeing the mysterious "security enhancements" mentioned in the AT&T release notes on the July 1st update I think it's important to prevent further updates incase they break future rooting methods. Also, why take their update if it's not shown to improve performance? Come on! There's an update to Uber, but no mention of touch screen fixes?!
FIrst, get debloater (works without root!)and set up your computer so you can run ADB and connect with your phone. You may need to install the LG United Mobile Driver.
There's a ton of packages you can block that will improve the performance and battery life of the phone, but the package you want to block to prevent updates is LGDMSClient.apk. This will break the software update screen in about phone and so far has prevented my phone from trying to update.
Good luck!
Click to expand...
Click to collapse
Just a quick heads up (might just be me, might be US Cellular in general....I am not sure) I went through and did this after hearing about different companies basically force feeding their clientel these OTA Updates and even though I did it all right down to the letter and did not skip anything my US991 still went ahead and did a forced update to 10c (not sure why or even when it did this, just know that it did at some point).
Hopefully they are not blocking any exploits with this stupid 10c update (which I assume they did as my device was running buttery smooth and had no issues that would have needed an update in order to correct).
Z3ldaFan88 said:
Just a quick heads up (might just be me, might be US Cellular in general....I am not sure) I went through and did this after hearing about different companies basically force feeding their clientel these OTA Updates and even though I did it all right down to the letter and did not skip anything my US991 still went ahead and did a forced update to 10c (not sure why or even when it did this, just know that it did at some point).
Hopefully they are not blocking any exploits with this stupid 10c update (which I assume they did as my device was running buttery smooth and had no issues that would have needed an update in order to correct).
Click to expand...
Click to collapse
Sorry to hear it didn't prevent your update.
I've added more files to block, and one to unblock in the OP.
phineous said:
Sorry to hear it didn't prevent your update.
Try blocking LGUpdateCenter.apk also. My AT&T H810 hasn't tried to update and I can't force it to update since I blocked LGDMSClient.apk. Seems we can't be too safe in preventing forced updates so leave no questionable package unblocked!
Something I also did during setup was to not agree to the optional LG EULA that would have allowed app updating. I've also blocked:
LGStartupEula.apk
LicenseProvider.apk
UnifiedEULA.apk
I've attached a Debloater blocked.txt that shows all the packages I've blocked.
Click to expand...
Click to collapse
No worries, it just is what it is (yeah I was angry about it, but not like I can do anything about it). I will certainly go through and block the rest of the applications that you mentioned though so hopefully I can prevent any future aggravations caused by these damn self-updates. Thanks for posting how you went about it and letting us know that (so far at least) it is going according to plan.
Holy Cow! I thought T-Mobile was bad with the bloat but jeez....AT&T makes our bloat look like....well, I dunno it's still bloat, but we've got a LOT less of it lol. I use the debloater tool, but UX 4.0 isn't that bad by its self. I removed all the T-Mo stuff and that's about it.
Thanks!
painedglass said:
Holy Cow! I thought T-Mobile was bad with the bloat but jeez....AT&T makes our bloat look like....well, I dunno it's still bloat, but we've got a LOT less of it lol. I use the debloater tool, but UX 4.0 isn't that bad by its self. I removed all the T-Mo stuff and that's about it.
Click to expand...
Click to collapse
Did removing the TMobile bloat affect wifi calling?
G4'ed it!
Not at all, less lag and a bit smoother. Battery lasts longer since apps that drain the battery are disabled. Just be smart about what you disable. It has a search feature, so I'll search for say "tmo" any apk or service with that search term in it will show up in the list, disable it and move on to the next apk/service. You dont even need to reboot, you can watch them get disabled in real time.
I just bought my second G4, trying the phone again. It is another Verizon model.
People raised interesting points about holding off on updates, in case it makes root more difficult, so I got the Debloater tool (that is awesome!) and tried to block the items listed in the original post.
With Verizon, I don't see an entry for "LGUpdateCenter.apk", so I could not block that one. I hope the remaining 5 will be enough to keep the update at-bay for now.
phineous, that's an interesting point about the optional LG EULA. I agreed to something from LG during initial setup today, I guess I didn't give any real thought to not agreeing.
I have not yet applied anyone's complete Debloater list, I guess I'm not quite brave enough for that just yet. I only went through and disabled things I could identify and knew I wouldn't need at the moment.
How many apks does the AT&T G4 have? My Tmobile has 273.
Replacing my earlier post, to avoid confusion: Verizon messed up something on my line. After a day, they got it fixed, and now I can use Advanced Calling on my G4, still with the original software (having not gotten the recent update). Everything seems to be working now.
RedOCtobyr said:
Replacing my earlier post, to avoid confusion: Verizon messed up something on my line. After a day, they got it fixed, and now I can use Advanced Calling on my G4, still with the original software (having not gotten the recent update). Everything seems to be working now.
Click to expand...
Click to collapse
What's your Baseband Version and Build number? I'm buying the Verizon G4 this Saturday and would like to know if I have the OTA out of the box.
GUGUITOMTG4 said:
How many apks does the AT&T G4 have? My Tmobile has 273.
Click to expand...
Click to collapse
I don't remember how many it came with originally, but I've blocked 85 out of a total of 297. I've probably installed about 57. I would guess around 240 originally.
flamadiddle said:
What's your Baseband Version and Build number? I'm buying the Verizon G4 this Saturday and would like to know if I have the OTA out of the box.
Click to expand...
Click to collapse
Don't let the salesperson set up the phone! They seem to delight in downloading updates. I'd keep the phone off or at least disable WiFi till I could connect it to a computer and Debloat it.
Good luck!
phineous said:
Don't let the salesperson set up the phone! They seem to delight in downloading updates. I'd keep the phone off or at least disable WiFi till I could connect it to a computer and Debloat it.
Good luck!
Click to expand...
Click to collapse
Yeah, that's the plan. I'd just like a frame of reference so I know if all my efforts to prevent the OTA work or if I was defeated before I even got the phone.
phineous said:
I don't remember how many it came with originally, but I've blocked 85 out of a total of 297. I've probably installed about 57. I would guess around 240 originally.
Click to expand...
Click to collapse
Wow 85 is such a relief I blocked just 34. At least it does not get high temps now.T-mobile seems to add much lesser bloat indeed. My 273 include around 40 downloaded apps.
flamadiddle said:
What's your Baseband Version and Build number? I'm buying the Verizon G4 this Saturday and would like to know if I have the OTA out of the box.
Click to expand...
Click to collapse
See attached. I believe the item of interest, relative to the OTA, is the Software Version. The new one (updated) ends in 611A, I think.
They did a brief setup at Best Buy for me. I Factory Reset when I got home, then Debloated the items that would start the update:
http://forum.xda-developers.com/g4/help/how-to-prevent-updates-g4-t3148650
But it wasn't until the next day, after another Factory Reset, that I forgot to Debloat those immediately, and had turned on the WiFi. I noticed when the update was halfway downloaded. Turned off WiFi, and turned on Airplane Mode, until I was able to Debloat the offending items.
No updates stuff since then, several days ago, even with WiFi on.
RedOCtobyr said:
But it wasn't until the next day, after another Factory Reset, that I forgot to Debloat those immediately, and had turned on the WiFi. I noticed when the update was halfway downloaded. Turned off WiFi, and turned on Airplane Mode, until I was able to Debloat the offending items.
No updates stuff since then, several days ago, even with WiFi on.
Click to expand...
Click to collapse
Look at how sneaky the carriers are now! It's a good thing the devs are being quiet about their root method.
RedOCtobyr said:
See attached. I believe the item of interest, relative to the OTA, is the Software Version. The new one (updated) ends in 611A, I think.
They did a brief setup at Best Buy for me. I Factory Reset when I got home, then Debloated the items that would start the update:
http://forum.xda-developers.com/g4/help/how-to-prevent-updates-g4-t3148650
But it wasn't until the next day, after another Factory Reset, that I forgot to Debloat those immediately, and had turned on the WiFi. I noticed when the update was halfway downloaded. Turned off WiFi, and turned on Airplane Mode, until I was able to Debloat the offending items.
No updates stuff since then, several days ago, even with WiFi on.
Click to expand...
Click to collapse
Exactly what I needed. Thank you! :good:
flamadiddle said:
Exactly what I needed. Thank you! :good:
Click to expand...
Click to collapse
You are welcome! Please report back if discover any problems or other files to block.
Hey everyone! I was having phone troubles and was wondering if anyone could help solve them. I lurk more than I post on the forums, so forgive me if I make any mistakes.
My phone is an AT&T Galaxy Note 5 (of course) 32GB variant on stock 7.0. For what ever reason, my phone restarts with out reason and sometimes does it multiple times a day. It usually happens when I am on Wi-Fi, or the phone is looking for Wi-Fi. At first, I thought it was due to 3rd party apps trying to access data with low signal, but the problem still occurs after multiple factory resets. The phone doesn't restart as much when I turn Wi-Fi off, but the problem still occurs with Data.
The problem began around the time I updated my phone to Android 7.0 when AT&T released the update. I usually keep Wi-Fi, Bluetooth, Location, and Sync enabled if that helps. I also clear the cache partition after each security update.
I also believe that it has something to do with the Wi-Fi because even listening to music sometimes with Wi-Fi enabled, causes the audio to freeze or stutter. I read on a post that this might be due to Wi-Fi scanning or Bluetooth Scanning for location purposes, but the phone still restarts with those options disabled. I am unsure of what else to do besides just living with the problem. I took it to AT&T to see if they could help, but just wanted to sell me a new phone.
If anyone could help, I would greatly appreciate it. Thanks for reading and for the help in advance!
This is most commonly a botched upgrade and the way to repair it is to flash the entire current firmware to the device again which will delete all your personal files, photos, contacts, text messages, music, app data and anything else you have stored on the phone. Most of the time you can download your firmware from a link provided through this site, be weary of any other source of downloads links besides xda-developers.com!! Your AT&T store can flash the entire firmware to your phone again for you while retaining your data, but if you are holding out on upgrading so you can gain root this will defeat your efforts. For 99% of the people you should just take your phone to an AT&T store.
There's a chance that the next upgrade will repair your phone by replacing the problematic file but you'd be lucky to have that serendipitous outcome.
droidvoider said:
This is most commonly a botched upgrade and the way to repair it is to flash the entire current firmware to the device again which will delete all your personal files, photos, contacts, text messages, music, app data and anything else you have stored on the phone. Most of the time you can download your firmware from a link provided through this site, be weary of any other source of downloads links besides xda-developers.com!! Your AT&T store can flash the entire firmware to your phone again for you while retaining your data, but if you are holding out on upgrading so you can gain root this will defeat your efforts. For 99% of the people you should just take your phone to an AT&T store.
There's a chance that the next upgrade will repair your phone by replacing the problematic file but you'd be lucky to have that serendipitous outcome.
Click to expand...
Click to collapse
I was about to take it to an AT&T store, but I turned off Data Saver mode and did the latest update, and everything has been fine since. It's really the weirdest thing but I'm glad nothing too much had to be done to fix it. Thanks for the help and reply though!
Totally satisfied with 11.2.9.9 and wish to disable updates for good-ish. I did this on my Pixel 3XL and needed to jump through some hoops to stop the insistent nag pop up but got it done with help from XDA good guys. Like the Pixel, the notification does not allow to be silenced or disabled so need to dig deeper. I don't want to delete or uninstall the updater service but am open to freezing it if that won't cause any other issues. I'm rooted of course. Help would be appreciated, Thanks
I'm not sure turning down the already sporadic security patches released for Android phones is a good idea to start with, refusing them while rooted is an even worse plan.
With prevalent betaware updates makes sense for some to stay stable for once AFWall+
miravision said:
With prevalent betaware updates makes sense for some to stay stable for once AFWall+
Click to expand...
Click to collapse
That would be reasonable if the betas weren't explicitly opt-in. Blocking consumer release updates is an entirely different kettle of fish.
miravision said:
With prevalent betaware updates makes sense for some to stay stable for once AFWall+
Click to expand...
Click to collapse
Nailed it Mr Vision -
My phone is 90% de-googled so my biggest security risk has been neutralized.
I usually freeze the update service app in between updates to avoid the nagging while I'm waiting on a full zip to be released, or if it's just an inconvenient time for me to mess with it. It has never caused any issues other than the obvious: if you try to select System Update from Settings while frozen it will force close. Just unfreeze the update service when you're ready to update.
That said, I'm in agreement with other folks who say not taking security updates on a rooted device "ever" is generally a bad idea. New kernel exploits are discovered all the time, and plenty of core system packages have the potential for vulnerabilities.
terlynn4 said:
I usually freeze the update service app in between updates to avoid the nagging while I'm waiting on a full zip to be released, or if it's just an inconvenient time for me to mess with it. It has never caused any issues other than the obvious: if you try to select System Update from Settings while frozen it will force close. Just unfreeze the update service when you're ready to update.
That said, I'm in agreement with other folks who say not taking security updates on a rooted device "ever" is generally a bad idea. New kernel exploits are discovered all the time, and plenty of core system packages have the potential for vulnerabilities.
Click to expand...
Click to collapse
Thanks.
I would keep my phone updated but the ColorOS 12 update pretty much ruined the perfect experience. I'll update in a few months. Hopefully, they'll fix all the issues by then.
terlynn4 said:
"I usually freeze the update service app in between updates to avoid the nagging while I'm waiting on a full zip to be released, "
Click to expand...
Click to collapse
Yes thanks for the reminder this is possible. I went ahead and froze com.oneplus.opbackup. My setup is safely locked in until I decide it needs to be changed!
Maybe some folks from this thread will see my thread lol and rethink the early adopter or as I like to call it, guinea pig strategy.
12 "Stable" Issues Thread
Besides the general low quality of this piece of software, here are some specific pains: 1. SafetyNet test fails (no root) - WTF? Can't use any of my work applications because of that. 2. Status bar notification icons don't appear (except for...
forum.xda-developers.com
Just use a package disabler, a ADB edit or if your rooted you have even more apps to block OTA updates.
Security in real life isn't an issue with Android 9 or higher unless you do something stupid. This stock N10+ has been running on Android 9 for over 2 years with no updates.
The current OS load is over 1.5 yo, still fast, stable with minimum maintenance. I take a few precautions especially with app installations and downloads. Android 9 and higher are reasonably secure even if Google claims otherwise.
So enjoy your current platform for as long as you want. Don't let updates break your phone... they sure as hell can and do.
Redundantly backup all critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC. Time stagger backups to them incrementally as an added precaution. Have a plan in place for password resets and bank accounts (which are insured from fraud anyway).
In the case of malware if you can't completely isolate and delete it within an hour or two, go full nuke and reload. It takes far less time to reload then it does to attempt to optimize and adapt to a new OS version.
Fools leave in fear, pragmatists live within reality.
Don't ever update to Android 12 then. Remember, you have been warned. No matter what, stay on Oxygen 11
@blackhawk - Yeah I really like App Manager does all you say plus a whole lot more.
@giaur
Both you guys, EXACTLY! Ran Android 9 for 3 years on my rooted Pixel 3XL, no updates past 9/19 no issues no regrets.
11.2.10.10 is safe. But I dont update to A12 soon.
You can disable the updates very easy.
1st: Settings -> System -> System Updates -> Top right the gear -> Disable Auto download over Wifi
2nd: Settings -> System -> Dev. Options -> Disable "Automatic system updates"
RheinPirat said:
11.2.10.10 is safe. But I dont update to A12 soon.
You can disable the updates very easy.
1st: Settings -> System -> System Updates -> Top right the gear -> Disable Auto download over Wifi
2nd: Settings -> System -> Dev. Options -> Disable "Automatic system updates"
Click to expand...
Click to collapse
See the thing is this doesn't stop the random often reoccurring pop-up nag that prompts to download the update. The fear there is the potential for an accidental tap. I don't want the giant update file hanging out on my phone ready to spring into gear at the slightest wrong move on my part. Maybe the tap would be interpreted by the phone as an overide to the 'disable' option selected in Dev Options. Don't know, don't want to find out.
Then use a fire wall and allow apps you want. I never got a update notification since I have the phone. I always updated it by myself.
chetqwerty said:
See the thing is this doesn't stop the random often reoccurring pop-up nag that prompts to download the update. The fear there is the potential for an accidental tap. I don't want the giant update file hanging out on my phone ready to spring into gear at the slightest wrong move on my part. Maybe the tap would be interpreted by the phone as an overide to the 'disable' option selected in Dev Options. Don't know, don't want to find out.
Click to expand...
Click to collapse
Use service disabler from playstore to disable system updater(requires root)
chetqwerty said:
Yes thanks for the reminder this is possible. I went ahead and froze com.oneplus.opbackup. My setup is safely locked in until I decide it needs to be changed!
Click to expand...
Click to collapse
Yes goofy to quote myself but wanted to post an update that sadly this only worked for about a month then the nags returned even though the com.oneplus.opbackup service was frozen. Getting the system update nags every other day after they stopped for a month. Gotta figure this out, I'm sure that sinister google has their hand in this someway!
Back a couple of weeks ago or so at least two people mentioned they weren't receiving automatic updates to their apps. I can't find the thread now when I search for it - was probably posts buried in one of the existing threads.
I was having a problem with one particular app yesterday, and I was wondering if it needed an update. It didn't, the problem was probably the particular company's, but I noticed there were over 40 apps that needed updates, and just now I received a notification that 24 apps had updates available.
I chose to update them all, and then after they updated I started checking each of them one by one on the Play Store, and they were all set to not Auto update. I've had this before but only work select apps, not a bunch.
I don't know if it's related to me using Swift Backup to restore only some apps' data or what could do this. Even Swift Backup was set not to auto-update.
It's frustrating that after all this time there's no way to just get a list of those set but to auto-update and not, and be able to toggle a bunch all from one screen instead of each individually.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I keep getting 'unable to update' or whatever. Some apps only update by manual update
Hmm, that's an oddity. I'll start with some simple guesses for what could potentially be causing such an issue.
This hasn't happened to me yet, however, I don't use any backup apps after a full wipe or a phone swap; so that could potentially be affecting your device's apps. But also - and this probably isn't related to the problem - but do you disable verity and verification each time that you flash an update? So many people have been saying that it is no longer necessary, however, I have been doing it every single time just in case. Lastly, you are definitely using the correct factory image from Google's site, right? If you purchased the phone directly from Google, you're not supposed to use the image labeled as "For US Carriers" (although I'm not sure that using that image anyway would cause this issue)... These are all things that I've learned/started doing just to play it safe.
*Edit* - Oh, and which Google Play system update are you rocking?
fil3s said:
I keep getting 'unable to update' or whatever. Some apps only update by manual update
Click to expand...
Click to collapse
Interesting! Have you looked at any of those apps' individual checkboxes to see if they're set to auto-update?
NippleSauce said:
Hmm, that's an oddity. I'll start with some simple guesses for what could potentially be causing such an issue.
Click to expand...
Click to collapse
Hi, thanks for your suggestions on the subject.
Update of sorts: I scrolled through all 256 apps (not all of them user apps, and now uninstalled two) and didn't detect any particular pattern to the ones which had the checkbox set and which didn't. I believe among stock (in the firmware) installed apps that they were usually checked but I didn't pay close attention if any of those were not. I believe there were a few that were not.
At least 75% of the apps, but definitely not all - even not all of the user-installed apps, had auto-updates disabled.
As a side note, besides the usual pain of having to check that setting for each individual app, it's especially a pain to try to hit the 3-dot menu button right beside the curved edge of the screen, 250+ times. There was more than one app that it took several trials and errors to click the menu button.
NippleSauce said:
This hasn't happened to me yet, however, I don't use any backup apps after a full wipe or a phone swap; so that could potentially be affecting your device's apps.
Click to expand...
Click to collapse
The most recent time I factory reset, I only restored backups through Swift backup for particular apps that don't implement Google's cloud backup for the app data. I didn't restore the actual apps, just the data. Previous to that, I had actually had Google's cloud backup restore everything. I always do and have never had any obvious problems for several years now.
NippleSauce said:
But also - and this probably isn't related to the problem - but do you disable verity and verification each time that you flash an update? So many people have been saying that it is no longer necessary, however, I have been doing it every single time just in case.
Click to expand...
Click to collapse
I did disable them the last time that I flashed because I knew I was going to be flashing the updated CleanSlate kernel and I wasn't sure if it was still going to be necessary. At this point, I don't remember if I later flashed verity and verification without disabling them (to enable them).
When the January update arrives, I plan on not disabling verity and verification. I know that the CleanSlate kernel has been updated to not require those being disabled.
NippleSauce said:
Lastly, you are definitely using the correct factory image from Google's site, right? If you purchased the phone directly from Google, you're not supposed to use the image labeled as "For US Carriers" (although I'm not sure that using that image anyway would cause this issue)... These are all things that I've learned/started doing just to play it safe.
Click to expand...
Click to collapse
I am on raven-sq1d.211205.017-factory-bf3da4b2 - for all U.S. Carriers.
You are the second or third person who has said in this section that the US Carrier image isn't the correct one if using the factory unlocked variant. I'd like to know what the source is of this information, as no one has pointed to an article or official Google source saying one way or the other.
At this point, over two months since my wife and I received our P6Ps, I don't remember the exact firmware that was on it, nor the exact OTA version that was available immediately - either one of the following two:
SD1A.210817.019.B1, Oct 2021, AT&T
or
SD1A.210817.019.C2, Oct 2021, T-Mobile (US), USCC, Google Fi, CA, & TW carriers.
I tend to keep things simple when possible and my interpretation and advice to everyone who has asked what update they should flash is simply, whichever one matches your carrier. After all, they contain radio optimizations geared towards the carrier(s) available in those areas. Certainly, all of the firmware versions work on any bootloader unlocked Pixel, but without evidence to the contrary, I have no reason to think I shouldn't be flashing the one for U.S. Carriers, and the December one that didn't specify a particular place would be for "everywhere else" other than the three others which did specify.
If you can lead me to the solid information that says I shouldn't, I'd greatly appreciate it. I'm not trying to be contrary or argumentative - I'm just genuinely curious what the source is for this information. It would have to be a very solid source for me to change my thought on the matter.
NippleSauce said:
*Edit* - Oh, and which Google Play system update are you rocking?
Click to expand...
Click to collapse
I am on the November Play System update, with no update available.
Before I accidentally factory reset my phone three weeks ago, I had gotten the December Play System update. I remember reporting at the time in a thread here which someone made about the Play System update that the phone reported the update to December was ~650 MB, which was tons larger than what most were reporting as ~50 MB or so. As others have speculated, there are probably multiple updates available in the same month sometimes, so perhaps I was on an older October update before that, and most others were already on November - just speculation, though.
I didn't root right away because I was waiting on all the positive reports on success and methods, and then I had to wait for a time I felt comfortable taking the time necessary to set everything up on the freshly factory reset phone. I believe I had unlocked the bootloader immediately, as I knew that would factory reset and would be necessary for rooting, but of course then there was the disabling verity and verification which I didn't know about when I unlocked the bootloader, anyway, so I did that later, and then I had to factory reset yet again.
For the record, I haven't had any other problems, like others have.
Interesting! Have you looked at any of those apps' individual checkboxes to see if they're set to auto-update?
Click to expand...
Click to collapse
Yeah it's setup to automatically update as I have unlimited wifi. I just get one or two apps fail to update about once a day.
fil3s said:
Yeah it's setup to automatically update as I have unlimited wifi. I just get one or two apps fail to update about once a day.
Click to expand...
Click to collapse
You took a look at my screenshots in the OP? I just want to make sure you and I are talking about the same thing. My Play Store settings, in general, have always (or at least for many, many years) been set to auto-update over both Wi-Fi and mobile data connections (I used to do Wi-Fi only a long time ago as well), however, each app's page in the Play Store has its own individual checkbox for auto-update located in the upper right corner's 3-dot menu, which is independent of the overall Play Store settings for auto-update, and takes overrides it, at least when the general setting for the Play Store is to auto-update.
I haven't had the issue you're having with 'unable to update' or anything similar, for what it's worth.
roirraW edor ehT said:
You took a look at my screenshots in the OP? I just want to make sure you and I are talking about the same thing. My Play Store settings, in general, have always (or at least for many, many years) been set to auto-update over both Wi-Fi and mobile data connections (I used to do Wi-Fi only a long time ago as well), however, each app's page in the Play Store has its own individual checkbox for auto-update located in the upper right corner's 3-dot menu, which is independent of the overall Play Store settings for auto-update, and takes overrides it, at least when the general setting for the Play Store is to auto-update.
I haven't had the issue you're having with 'unable to update' or anything similar, for what it's worth.
Click to expand...
Click to collapse
I use swift backup Pro also, but haven't used it on my p6pro yet.
Yeah sorry about that I didn't read your post properly. Blame the psyche meds I'm on, or my frontal lobe damage
fil3s said:
I use swift backup Pro also, but haven't used it on my p6pro yet.
Yeah sorry about that I didn't read your post properly. Blame the psyche meds I'm on, or my frontal lobe damage
Click to expand...
Click to collapse
LOL!!! No sweat.
I've been noticing the same. However I also saw this issue on my OP8T running LOS18.1. I do manually disable auto-update on YouTube (since I use Vanced) all other apps are set to auto-update. I wonder if it has to do with having even one app not set to not auto-update or if it is Swift (since Google doesn't restore my 2FA Authenticator data and until recently you couldn't export).
As for the question about Verity, mine is off from when I rooted right after Dec update when it was required.
Based on your response, I'm going to guess that this could either be due to the incorrect factory image use or due to the use of SwiftBackup. We're both on the Play System update from November - so that seems like an unlikely cause.
I, personally, never backup anything before wiping my phone. Does that make it a real pain in the arse to setup again? It definitely does =(.
As for my information regarding the correct factory image to use, I don't have the links to where that information was discussed, however, it was stated by a Google employee on the Google forums and was also (I believe) discussed on Twitter from a Google rep. I may not be 100% correct on the other discussion happening on Twitter as I don't fully remember discovering everything related to the factory image confusion being that it was one of the first things that I had corrected after getting this phone. But, when I went to the correct factory image, a lot of the odd things that my phone would experience (such as an abnormally high usage temperature no matter what) were resolved. Perhaps the different P6 variants have a slightly different hardware design that isn't mentioned anywhere?
Also for the disable verity and verification stuff - I still don't think it could be causing the issue, however, I've been sure to disable it with every single factory image update. So perhaps this has more of an impact on stability than was previously thought .
Regardless, my apologies for my crummy formatting in this response and also for possibly missing some details. I'm on mobile right now and have had a severe traumatic brain injury about a year and a half ago. After reading the short message from @fil3s , it seems that XDA is the safe ground for us brain injury nerds, haha =)
NippleSauce said:
Based on your response, I'm going to guess that this could either be due to the incorrect factory image use or due to the use of SwiftBackup. We're both on the Play System update from November - so that seems like an unlikely cause.
Click to expand...
Click to collapse
Of those two choices, I would lean towards Swift Backup, however, I doubt if it's that either since I definitely didn't restore anything using Swift for so many of my apps - I only restored very select apps' data after I had restored from Google Backup. Hell, it could be a Google Backup/Restore bug for all I know. I've had nothing (else) but good experience with restores from Google over the last five years or so.
NippleSauce said:
I, personally, never backup anything before wiping my phone. Does that make it a real pain in the arse to setup again? It definitely does =(.
Click to expand...
Click to collapse
I prefer to manually over-backup and restore only what I need to as I need it - any app data that Google's Cloud Backup didn't restore for apps that are slightly more painful to remember how I had them set up. It's better for me to not need the data but have it backed up, then need it and not have it backed up.
NippleSauce said:
As for my information regarding the correct factory image to use, I don't have the links to where that information was discussed, however, it was stated by a Google employee on the Google forums and was also (I believe) discussed on Twitter from a Google rep. I may not be 100% correct on the other discussion happening on Twitter as I don't fully remember discovering everything related to the factory image confusion being that it was one of the first things that I had corrected after getting this phone. But, when I went to the correct factory image, a lot of the odd things that my phone would experience (such as an abnormally high usage temperature no matter what) were resolved. Perhaps the different P6 variants have a slightly different hardware design that isn't mentioned anywhere?
Click to expand...
Click to collapse
I'll definitely need more than that before I switch my thinking on that subject, but thank you for sharing what you do know or remember. The easy way to find out, of course, is for someone who's completely on stock unrooted, preferably even bootloader still locked, running on AT&T like me to share with us which December OTA they received - for those relatively few who actually received it.
I may go ahead and make a question thread/XDA poll on the subject: Poll only for non-rooted factory unlocked P6P owners running on any US carrier who received the December over the air update, not manually flashed
NippleSauce said:
Also for the disable verity and verification stuff - I still don't think it could be causing the issue, however, I've been sure to disable it with every single factory image update. So perhaps this has more of an impact on stability than was previously thought .
Click to expand...
Click to collapse
I doubt if it is a factor for stability, or at least only indirectly through the increased security they provide. See the section on that subject with information that other more knowledgeable folks in the first four posts in my P6P thread that I have in my signature below if it's information you're not already aware of.
NippleSauce said:
Regardless, my apologies for my crummy formatting in this response and also for possibly missing some details. I'm on mobile right now and have had a severe traumatic brain injury about a year and a half ago. After reading the short message from @fil3s , it seems that XDA is the safe ground for us brain injury nerds, haha =)
Click to expand...
Click to collapse
I'm very sorry to hear about your brain injury. I hope you cope as well as possible. Don't worry about formatting - even if it's not easy to read/digest XDA's newer software makes it easier to break up into chunks and respond to individual portions, from what I remember over the old software. My brain issues are more psychological (so far), however, the Army did feed us beef that was potentially from mad cows in Britain in the mid-1980s, but the only way anyone will ever know if I was exposed to it is if I die from it - at least that was the information that was given to me when I found out about that almost 20 years ago when I went to give blood.
roirraW edor ehT said:
Back a couple of weeks ago or so at least two people mentioned they weren't receiving automatic updates to their apps. I can't find the thread now when I search for it - was probably posts buried in one of the existing threads.
I was having a problem with one particular app yesterday, and I was wondering if it needed an update. It didn't, the problem was probably the particular company's, but I noticed there were over 40 apps that needed updates, and just now I received a notification that 24 apps had updates available.
I chose to update them all, and then after they updated I started checking each of them one by one on the Play Store, and they were all set to not Auto update. I've had this before but only work select apps, not a bunch.
I don't know if it's related to me using Swift Backup to restore only some apps' data or what could do this. Even Swift Backup was set not to auto-update.
It's frustrating that after all this time there's no way to just get a list of those set but to auto-update and not, and be able to toggle a bunch all from one screen instead of each individually.
View attachment 5503665
View attachment 5503667
Click to expand...
Click to collapse
I've been noticing the same with my Pixel 3 and 6 Pro. When I upgraded my 3 to Android 12, I had trouble updating apps and checked the setting. It was turned off, for almost every app (I never did turn any of these boxes off manually). I guess it's an Android 12 thing-y / bug. Since my P6 Pro also had several of these settings turned off, it has probably nothing to do with upgrading to Android 12, but Android 12 in general just being a buggy mess.
Morgrain said:
I've been noticing the same with my Pixel 3 and 6 Pro. When I upgraded my 3 to Android 12, I had trouble updating apps and checked the setting. It was turned off, for almost every app (I never did turn any of these boxes off manually). I guess it's an Android 12 thing-y / bug. Since my P6 Pro also had several of these settings turned off, it has probably nothing to do with upgrading to Android 12, but Android 12 in general just being a buggy mess.
Click to expand...
Click to collapse
Thanks! That does sound more likely. I guess I can officially list myself as having one problem.