Hello all,
Has anybody else out there experienced the Notifications Bug - I have seen some mention of it in older posts, is it just my setup ??
I use a PDA2K EVDO,
McAfee Virusscan for PDA
Device has password lock and prompts every time it is woken up
I don't use Bluetooth, and there have been no ROM updates released for my device.
The device is permanently connected to corporate network via EVDO and syncs my mail every 20 mins.
My PDA2K EVDO has been giving me a lot of problems since I bought it in Novemeber. I last performed a hard reset in early January. It worked fine for a while but I've had a variety of problems with it recently and was almost ready to dump it/rebuild it again.
In the past few weeks I've probably soft reset at least once per day
Yesterday I downloaded the Notifications check app from scarybearsoftware.com (gotta love that name) and discovered that I had 3800 notifications.
They are not the sstimechange, connmgr or IA_caller_Id message that the software specifically mentions.
The notifications mostly seemed to be in server.exe.
The events are either Apprunaftersync or Apprunafterwakeup.
I deleted 2787 duplicate events (leaving 17) and hey presto - it seemed to be fine again.
After about 20 hours - I'm already up to 80 notifications.
Does anybody understand what the notifcations are all about ??
Thanks
T
Shot in the dark, but do you think it's related to your antivirus software on your PDA, like it's scanning the moment it powers on or checks the PDA after an ActiveSync? Just a guess, since I don't have any AV software yet on my PDA2K.
Ever since upgrading to Lollipop (5.0.1), my G3 has been consuming vast quantities of mobile data (much more than it does on Wi-Fi) , at a rate that is threatening even my 1GB monthly cap. I have never had this issue with this phone before upgrading, nor with any other phone I have owned, and I can't find any resources about it online. It appears to use small amounts of data (a few KB) continuously throughout the day, not in large chunks, so it is not Google trying and failing to download a software update like come CM users have seen.
I uninstalled every app that I did not have before the Lollipop upgrade, as well as any potentially troublesome apps, to no avail. Then I tried booting into safe mode, removing all my synced accounts except the main Google one, turning off sync for that account, turning off data backup, clearing the caches of all my apps, and not opening any non-stock apps for a day. Even with all that, it still ran through a few megs in just an afternoon. Turning everything back on and setting accounts back up did not increase or decrease the data consumption. Restricting its background data does stop it from using mobile data, but it also seriously cripples my device (Play store stops working, sync stops working, calendar etc. stop working...)
I attached screenshots that show its data usage. It decreased considerably around June 9th because I finally got Wi-Fi in my room. But even still, it continues to eat my data for no apparent reason. I REALLY want to avoid a factory reset (and I doubt it would help anyway, since it was factory reset for the upgrade, and running everything completely stock doesn't help).
Can anyone give me some ideas here?
Info about the phone:
Model: LG-D851 (T-Mobile)
Android version: 5.0.1 (stock, rooted)
Kernel version: 3.4.0
Software version: D85120b
Network: olleh (South Korea, the same SIM card I used with the phone before the upgrade)
Google Play Services version: 7.5.71 (1955121-430)
Google Services Framework/Google Account Manager versions: 5.0.1-1602158
Hey, try limiting background data. There should be a tick above the usage graph.
Also many people have problems after upgrading to lollipop, including me, you should try factory reset. I had like half of my apps broken and frequent crashes after upgrading.
Martin
SareMa96 said:
Hey, try limiting background data. There should be a tick above the usage graph.
Also many people have problems after upgrading to lollipop, including me, you should try factory reset. I had like half of my apps broken and frequent crashes after upgrading.
Martin
Click to expand...
Click to collapse
Hi Martin, thanks for the reply. I'm trying to avoid restricting background data because I often have to go long stretches without Wi-Fi, and a lot of my apps stop working properly if background data is restricted. And I don't want to factory reset because it takes me days to set my phone back up to how it was.
I got a notification for a software update yesterday. After downloading and installing 2/2, the phone moved on to the usual optimising apps stage that happens after an update. It stuck at 174/199 or thereabouts, and it has been frozen at that overnight.
It took a while to get it to restart this morning, and when it did it carried on optimising 17/19. Since then, many Apps crash out on their logo splash page, or do not load at all, and The Play Store is unavailable.
I probably need a factory reset to sort it out, but backup programs will not run.
What an absolute pain. Seems a number of people have the same issue
I'm wondering whether this is the cause of the extremely sporadic data connectivity I'm getting. Until I applied this latest update I had no problems to speak of. Now I'm rarely getting a data connection, even with strong signal. Google Authenticator crashes. I'm roaming in California using a UK Three SIM, so I ought to be "feeling at home".
lge/g3_global_com/g3:5.0/LRX21R.A1440231662/1440231662:user/release-keys
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.
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!