I have a Note II (N7100) from Germany (DBT), carrier-free, and was on the Samsung stock Jelly Bean LL7 (DBT) ROM. I only CF-Auto-Root'ed (and Triangle Away'ed) this ROM but that's enough to get a "Modified" system status and thus not being able to get system software update notifications (for example, manually triggering the check for new firmwares only gets you to the "wait, checking for new firmwares" window, which keeps checking forever until you cancel it).
...Or so I thought.
Yesterday I received the notification that the new MC3 firmware was available even though if I manually check for updates it never finishes the check and, above all, even though I DISABLED the automatic check for new updates since the system doesn't seem to be able to find new updates with a modified status!
Trying to accept the update only brought me to the same "wait, checking for new firmwares" window which still hung forever so I tried to connect to Kies (latest version, of course) and it too told me that the new MC3 firmware was available so I tried to update it through Kies and... it worked!
Previously I had temporarily checked "keep root" in SuperSU Pro and I had disabled USB Debug (which I need especially for GMD Gesture Control, which I also temporarily disabled).
The update was completely successful (if a bit long) and everything works perfectly fine.
Does somebody have an explanation for why I received the notification even though manual checks don't work and (especially) I even had the automatic checks disabled (thinking it doesn't work)?
At first I even thought it was a fake notification from some malware (although I have only a couple of games, which are the usual source of malware -which I have never got before BTW-, installed)! LOL
I had same problem until i updated with kies. yesterday my phone was so hot i almost got burned from touching it and almost discarged, even thougt i was in charger, i think i was because it was constant searching for update. my guess is the servers was overloaded so my phone could not get the update or samsung pulled the update before my phone could download it. my phone is Dansih version.
Question is: did it kept your phone rooted? ( after you updated through Kies )
Answer is No root after update.
Sendt fra min GT-N7105 med Tapatalk2
jca1981 said:
I had same problem until i updated with kies. yesterday my phone was so hot i almost got burned from touching it and almost discarged, even thougt i was in charger, i think i was because it was constant searching for update. my guess is the servers was overloaded so my phone could not get the update or samsung pulled the update before my phone could download it. my phone is Dansih version.
Click to expand...
Click to collapse
That should not be possible and sounds to me like you have a serious fault there, and quite likely a fire hazard.
jca1981 said:
I had same problem until i updated with kies. yesterday my phone was so hot i almost got burned from touching it and almost discarged, even thougt i was in charger, i think i was because it was constant searching for update. my guess is the servers was overloaded so my phone could not get the update or samsung pulled the update before my phone could download it. my phone is Dansih version.
Click to expand...
Click to collapse
Actually I didn't mean it as a "problem" at all :laugh:
The overheating problem doesn't sound like something "normal" anyway, try doing something CPU-intensive like a benchmark or a heavy game for say 15 minutes and check the temperatures against another Note II doing similar tasks if you can, getting "almost burned" is NOT normal, you might have an HW fault (assuming of course you haven't OC'ed your phone).
Stressing CPUs/GPUs gets the phone *warm*, even "very warm" (they all are subjective definitions after all), but never "almost burning" hot!
carlitos66 said:
Question is: did it kept your phone rooted? ( after you updated through Kies )
Click to expand...
Click to collapse
I have SuperSU Pro and I checked Survival Mode but the SuperSU app wasn't there after the update.
TBH maybe simply reinstalling it from the market might have been all that was necessary but I simply re-rooted via PC Odin because I don't care about the warranty since my personal data on my devices are worth much more than the devices themselves to me (i.e. sending my devices for repair with my data on them is unthinkable to me and if they are broken in some way but can boot and can let me securely erase everything first then I can always "unroot" and "triangle away" later).
Related
I am using the Focus and I used the Cheveronupdate tool like as soon as it came out, I have just done a 3min search to see what this update does for the focus. Has anyone else had this occur recently?
And the Update PR stunt (note)
I guess the generic MS saying it will prevent your phone from updating is now proven false as well, granted I don't know if this update has done anything yet since I am on step 7 of it creating a backup file.
ATT Focus
I also used the Chevron Updater and updated to 7390. I received a notification via Zune for the standard update last night and tried to update. Went through all steps and then I got an error 80180005 for which I could find no explanation, but the update failed. I then plugged my USB cable to the back USB ports on my laptop and the installation succeeded and changed the bootloader number, firmware and radio software numbers. These numbers were NOT CHANGED with the NoDo update from the CXhevron Updater method.
This is the Samsung firmware update.
I also unlocked my phone using Chevron to update to NOdO weeks ago but am yet to see the samsung firmware update.
buffalosolja42 said:
I guess the generic MS saying it will prevent your phone from updating is now proven false as well, granted I don't know if this update has done anything yet since I am on step 7 of it creating a backup file.
Click to expand...
Click to collapse
Not quite the case.
@BrandonWatson said:
@Strider_Aus our guidance remains - Walshed phones will not update past NoDo (specififcally build 7390)
Click to expand...
Click to collapse
well mine went through
without a hitch yes OS revision numbers didn't change and I am not sure about firmware. Can't tell you that I see any difference right now.
capacitive buttons should be less sensitive, and dont work if you press the screen on a different place at the same time (for gaming or video playback etc, accidently hitting back button, it should be disabled now)
camera should auto default to anti-shake setting ON.
screen should be responsive even on a soft surface (pillow)
this is what I read, not sure, can people confirm this? Is this also for the omnia7? Mine is at the store for repair but these things were some annoying things and will be nice if they are fixed on the omnia as well.
I bought my s3 in March of this year, and everything was working just fine until May. It's an awsome phone and I love it. However, since May, my phone no longer connects to 4g EVER and the 3g comes and goes and never stays connected for more than 10 minutes while in use. I've NEVER even come CLOSE to reaching my plans provided 2.5GB of data, so I know that's not the issue. The phone has never been dropped, or wet, as I am always very delicate with my phones. I have never placed it too close to the TV...
I contacted Boost mobile. They gave me a long list of things to try. I have tried EVERYTHING: making sure the mobile networks is checked, preferred network setting CDMA/LTE, soft reset, clear browser cache, update PRL, profile update, software update, firmware update, ##72786#, and even did a factory reset. Nothing helped. Boost said there was nothing else they could do for me, and that I needed to contact samsung.
Samsung said the only way for them to find the problem is for me to send them my phone, and wait 2 to 4 weeks for them to revise it and send it back. That's not an option as I need my phone monday through friday for my job. (UPDATE: I got so irritated with this problem that I went ahead and bought an LG Volt, since I didn't have the money to buy another galaxy. It's nice but I don't like it as much. I'm still afraid to send the Galaxy into Samsung. They have expressed to me that if they can't find an issue(just my luck), or if they find the issue to be my fault(IE I put the phone too close to a credit card magnet or some dumb crap like that), then they will charge me not only for the parts and labor, but for the return shipping... and we all know that they'll charge me way more than the phone is worth.
I was just wondering if anyone else has had this problem, and if there's anyway to fix it without having to send my phone in to samsung? I have been told, also, that I could try reflashing the phone to it's original firmware and software, but I am afraid of screwing the phone up since I've never done anything like that before.
Thanks!
First off, Welcome to the forms.
Secondly, you came to the right place. On this form you'll find crazy people like me who like to do custom flashing updating all the technical stuff. And then there's section of the form where people just want a normal phone and just want the basic troubleshooting tips. As with any user will have to search through the forms because there's a high likely chance that someone already has or had your issue just at different time.
There could be multiple reasons as to what you're experiencing. First off I think you should confirm and verify that you will do live in a good 3G or 4G location so that any further test can be actually validated. Secondly if you're not being able to connect to data it seems that you need to reactivate your phone by getting back on the boost/Sprint network. A full factory restore with data wipe and then updating over the air with firmware, PRL, reboot should work. Make sure you are set to use LET, under mobile data, and that you have enabled Automatic connections to the tower. Reactivate the phone again, if still not connected, reboot.
If you're still not having connection and I think you probably need to do a reflash via ODIN. This is pretty much what Samsung would do I'm except they have their own proprietary tools. Here on XDA we just have great developers.
Good luck.
Thanks button if this helped.
ChocaHermosa said:
I bought my s3 in March of this year, and everything was working just fine until May. It's an awsome phone and I love it. However, since May, my phone no longer connects to 4g EVER and the 3g comes and goes and never stays connected for more than 10 minutes while in use. I've NEVER even come CLOSE to reaching my plans provided 2.5GB of data, so I know that's not the issue. The phone has never been dropped, or wet, as I am always very delicate with my phones. I have never placed it too close to the TV...
I contacted Boost mobile. They gave me a long list of things to try. I have tried EVERYTHING: making sure the mobile networks is checked, preferred network setting CDMA/LTE, soft reset, clear browser cache, update PRL, profile update, software update, firmware update, ##72786#, and even did a factory reset. Nothing helped. Boost said there was nothing else they could do for me, and that I needed to contact samsung.
Samsung said the only way for them to find the problem is for me to send them my phone, and wait 2 to 4 weeks for them to revise it and send it back. That's not an option as I need my phone monday through friday for my job. (UPDATE: I got so irritated with this problem that I went ahead and bought an LG Volt, since I didn't have the money to buy another galaxy. It's nice but I don't like it as much. I'm still afraid to send the Galaxy into Samsung. They have expressed to me that if they can't find an issue(just my luck), or if they find the issue to be my fault(IE I put the phone too close to a credit card magnet or some dumb crap like that), then they will charge me not only for the parts and labor, but for the return shipping... and we all know that they'll charge me way more than the phone is worth.
I was just wondering if anyone else has had this problem, and if there's anyway to fix it without having to send my phone in to samsung? I have been told, also, that I could try reflashing the phone to it's original firmware and software, but I am afraid of screwing the phone up since I've never done anything like that before.
Thanks!
Click to expand...
Click to collapse
You could definitely flash the stock ROM and kernel to your phone via ODIN. However, the safest and most foolproof way to do this would be to download Samsung's KIES software here: http://www.samsung.com/ca/support/usefulsoftware/KIES/JSP
Once in KIES, you would plug in your phone to the USB port and, if needed, download any drivers for your phone. Then, you would follow this path: Tools --> Firmware Upgrade and Initilisation. This will give you a warning that you will lose all your stored data on the phone, and will offer you to make a backup -- a very limited backup -- of information on your phone. If you don't have any worthwhile information, I'd skip the backup and go right to stock ROM restore.
Hope this helps.
tO rcatank, I have already done all of those things. I have a new phone (which I don't like as much) that is connected to 4g almost always.
Higgs_Boson said:
You could definitely flash the stock ROM and kernel to your phone via ODIN. However, the safest and most foolproof way to do this would be to download Samsung's KIES software here:
Once in KIES, you would plug in your phone to the USB port and, if needed, download any drivers for your phone. Then, you would follow this path: Tools --> Firmware Upgrade and Initilisation. This will give you a warning that you will lose all your stored data on the phone, and will offer you to make a backup -- a very limited backup -- of information on your phone. If you don't have any worthwhile information, I'd skip the backup and go right to stock ROM restore.
Hope this helps.
Click to expand...
Click to collapse
I download KIES onto my computer or the phone? The phone already has something called "KIES Air" on it, is that the same thing? And then one I download the KIES software and hook up my phone and go through the prompts you've provided, it does the rest itself?
ChocaHermosa said:
tO rcatank, I have already done all of those things. I have a new phone (which I don't like as much) that is connected to 4g almost always.
I download KIES onto my computer or the phone? The phone already has something called "KIES Air" on it, is that the same thing? And then one I download the KIES software and hook up my phone and go through the prompts you've provided, it does the rest itself?
Click to expand...
Click to collapse
No, Kies Air is not the same thing. To do a stock restore, you have to hook it up to Kies on your PC via USB. Follow the steps I showed you, follow the steps on the screen, and Kies will take care of the rest.
Higgs_Boson said:
No, Kies Air is not the same thing. To do a stock restore, you have to hook it up to Kies on your PC via USB. Follow the steps I showed you, follow the steps on the screen, and Kies will take care of the rest.
Click to expand...
Click to collapse
+1 on this
Higgs_Boson said:
No, Kies Air is not the same thing. To do a stock restore, you have to hook it up to Kies on your PC via USB. Follow the steps I showed you, follow the steps on the screen, and Kies will take care of the rest.
Click to expand...
Click to collapse
Ok, thanks very much! One more question though... does it matter that the galaxy is no longer activated? I mean, obviously to test it to see if it works I'd have to re-activate it. But for this process, does it need to be activated?
ChocaHermosa said:
Ok, thanks very much! One more question though... does it matter that the galaxy is no longer activated? I mean, obviously to test it to see if it works I'd have to re-activate it. But for this process, does it need to be activated?
Click to expand...
Click to collapse
Without it being activated, I don't think you'll be able to receive data of any kind. In order to test 4G capabilities, you are probably going to need to reactivate.
But, to restore it via Kies, no activation is necessary.
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.
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.
Hello first time poster here. My work acquired a few demo Galaxy Watches SM-815u these have been sitting for about a year without any use. My boss asked about seeing if these are usable and I powered one on connected to my phone and everything seemed to be working good. However after about 15 minutes a popup showed this device is managed by Reemo Health via Knox and it took over the watch and installed some application. None of the sensors seem to work anymore but were working before the SDK was installed. I called Reemo Health to return the devices or see what they wanted to do with them and they said throw them away as they are no longer used and they do not want them back.
Now im on a mission to see if there is anything I can do to make these usable again. I flashed new firmware and they booted up but then the Reemo Health SDK attempted to install and failed and is now stuck on a screen saying to reach out to their team. Is there anything I can do to remove the Reemo SDK or disable Knox to prevent the install of the Reemo information? These are paper weights at the moment so willing to do just about anything to see if I can get them working. Maybe I am just SOL but would be nice to know haha.