How do I get rid of it?
{
"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"
}
Hey
my screenshots looks nearly the same and I try to understand this ConnectivityServices too. Any suggestions?
Gesendet von meinem GT-I9300
Are we in the wrong Forum?
Connectivityservice
I am also suffering from huge battery drain after flashing CM 10.1 due to ConnectivityService wakelock and ActivityManager wakelock. I have searched on the Internet for a solution but found nothing yet. Does anyone know how to fix this?
I am really frustrated with this problem.
Bump.
http://forum.xda-developers.com/showpost.php?p=30088906&postcount=3
hope it'll help
Also have the same issue on my OnePlus One running Exodus 5.0.2 rom.
Connectivityservice wakelock ongoing for 5 hours, no apps installed other than betterbatterystats. All data is off, set to 2G, no roaming etc. Tried suggestion here:
http://forum.xda-developers.com/showpost.php?p=30088906&postcount=3
Didn't help. Tried several radios, neither works. I get great signals, battery graph shows signal strength as green so it's OK and apps like Network Signal Info showed that I'm getting a -60dbm signal which is pretty decent. Still, not sure why I'm getting this wakelock.
On my Galaxy Note 3, I've had similar issues as well running CM or AOSP based roms. However on custom Touchwiz roms, it doesn't exist. Radios are all the same coz the custom roms for Galaxy Note 3 don't touch the radios (I confirmed it's the same anyway using Phone Info). So maybe it's a CM/AOSP thing?
chaoscreater said:
Also have the same issue on my OnePlus One running Exodus 5.0.2 rom.
Connectivityservice wakelock ongoing for 5 hours, no apps installed other than betterbatterystats. All data is off, set to 2G, no roaming etc. Tried suggestion here:
http://forum.xda-developers.com/showpost.php?p=30088906&postcount=3
Didn't help. Tried several radios, neither works. I get great signals, battery graph shows signal strength as green so it's OK and apps like Network Signal Info showed that I'm getting a -60dbm signal which is pretty decent. Still, not sure why I'm getting this wakelock.
On my Galaxy Note 3, I've had similar issues as well running CM or AOSP based roms. However on custom Touchwiz roms, it doesn't exist. Radios are all the same coz the custom roms for Galaxy Note 3 don't touch the radios (I confirmed it's the same anyway using Phone Info). So maybe it's a CM/AOSP thing?
Click to expand...
Click to collapse
This is a Nexus 4 forum/thread, I'd suggest you either post in the 1+1 forum, or in the BetterBatteryStats thread in Android Apps & Games (with a log). That thread is specialised in wakelock analysis...
I have heard, though, of several 1+1 users mentioning this wakelock recently.
Related
I just received my evo4g from sprint and rooted/flashed etc to cm7. with cm7 kernel + rom + amon ra recovery.
After I did all of this I used it for a couple days and I was having very bad battery life (4 and a half hours of normal use). This is strange considering others with similar setups are getting leaps and bounds more than I am.
I changed the kernel to tiamat 4.1 and undervolted the proc via vipermod, but I am not seeing any gains.
I have even re calibrated the battery and battery life seems worse (4hours of normal use from 100%-0%)
Is there something I'm doing wrong here? Why is my phone dying so quickly?
(I dont have a screen cap but cell radio says 37%-40% avg of battery use each 100-0 discharge (if my memory is serving me well)).
Help.
Try upgrading or downgrading radios from calkulins thread in dev section sometimes its a trial and error or different combos if radio wimax pri and NV, in your battery info is your awake bar solid or broken up if broken what's it look like compared to the screen on bar a screeny would be nice
-EViL-KoNCEPTz- said:
Try upgrading or downgrading radios from calkulins thread in dev section sometimes its a trial and error or different combos if radio wimax pri and NV, in your battery info is your awake bar solid or broken up if broken what's it look like compared to the screen on bar a screeny would be nice
Click to expand...
Click to collapse
I just upgraded to the most recent radios per your suggestion, I will do a full charge + a battery calibrate tomorrow to see what my batt life is like now.
If u still have the issue get me a screen shot of your battery info with the status bars on the bottom that say cell radio, screen on, awake and what ever the last one is, if u go to the battery info in about phone and click on the top graph it will pull up the extended graph page with that info
Still having the issue
..
{
"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"
}
Sent from my EVO4G_cm7_savagezen2.2
You appear to be having a minor wakelock issue, search for the radio pack for wakelocks on GB by calkulin and give it a shot its a combo of older radios and pri NV should be radio 2.15.xx.x2 can't remember the exact number and pri or NV is 1.77 not sure if both are or one is something different but there's a thread about the radio wakelock on gb and it has the flashable pack it fixed my issue but now I'm on the most recent available pack from calkulin and haven't had too bad of a wakelock issue I had a minor one the first day but it seems to have settled down now
We are legion, for we are many.
Hi Folks,
I have been suffering with abysmal battery life for the past couple of weeks since I got my device(910F). So much so that yesterday I rooted the phone just to get betterbatterystats to give me more information on what was draining the battery.
Low and behold it turns out bluetooth is the culprit. I have a moto 360 that I have paired with the phone.
Before I switched bluetooth off i had 2 kernel wakelocks occupying 88% of the time since i took it off charge (bluesleep & msm-serial_hs_dma).
As soon as I switched off bluetooth these wakelocks where immediately released.
Also when checking CPU states prior to disabling bluetooth no time was spent in deepsleep. As soon as I turn off bluetooth I'm now seeing 23% (and growing) of the time spent in deep sleep.
Has anyone else had this issue with their Note? Seems like bluetooth is keeping the phone awake and not letting it enter deep sleep.
some images to help see what im on about!
bluetooth on
{
"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"
}
bluetooth off
I've the same problem whit my Note 4 (N910F). I've 3 devices constantly connected with my phone: LG G Watch R, Fitbit Flex and Xiaomi MiBand.
I've a custom rom: Emotion Revolution Note4 Lollipop based (BOB4 and BOC3 versions have the same problem)
bean_ian said:
some images to help see what im on about!
Click to expand...
Click to collapse
I have exactly the same issue on my Sony Z3. Take a look to here. You'll feel at home!!
Did you find any solution workaround?
This things is driving me crazy.
It looks to not a very popular issue around XDA. Could it be an app? Hw problem?
My note 4 is on 5.0.1, and this just started yesterday. I always keep my Bluetooth on with great battery life. Today, however, my phone will not enter deep sleep until I turn off Bluetooth.
I cleared the data on the Bluetooth and BluetoothTest processes, and my problem is solved. Now, understand that I've been turning bluetooth off and on constantly as I use my hands-free device for calls and turn bluetooth back off to save battery, so something may started functioning properly along the way without clearing those previously mentioned data and caches. Either way, I leave bluetooth on 100% of the time again, and my battery life is again stellar.
I'm getting this bug in every Lollipop Phone I own. And sadly this bug seems to be present in the M Developer preview too.
Usually my day starts with wifi but as soon as I leave the wifi connection and start using 3G the battery starts to drain.
It has gotten so annoying that I switched back to KitKat and my phones are awesome again.
Present for me on Z3 and S4
Cozmos23 said:
I'm getting this bug in every Lollipop Phone I own. And sadly this bug seems to be present in the M Developer preview too.
Usually my day starts with wifi but as soon as I leave the wifi connection and start using 3G the battery starts to drain.
It has gotten so annoying that I switched back to KitKat and my phones are awesome again.
Present for me on Z3 and S4
Click to expand...
Click to collapse
I noticed this today. Was using WiFi screen was at about 36% use and Android OS at about 6%. Switched to Mobile data, And before 30 minutes, screen was at 28% and Android OS was 30%+
Crazy really! Don't know if a reboot would fix. Back on WiFi tho and it seems normal again.
The above comment was made by me, my friend logged into his xda on my phone and i didn't know, when i knew it was too late.
Basically every app that uses mobile radio keeps the connection active and drains the battery fast.
As seen in the battery tab with "mobile radio active" for hours.
At first I switched to lollipop I thought its just an "feature" but its the bad bug.
Especially for people who doesn't charge their phone for days because of light usage
Cozmos23 said:
Basically every app that uses mobile radio keeps the connection active and drains the battery fast.
As seen in the battery tab with "mobile radio active" for hours.
At first I switched to lollipop I thought its just an "feature" but its the bad bug.
Especially for people who doesn't charge their phone for days because of light usage
Click to expand...
Click to collapse
Someone said he doesn't experience it in Moonbreaker ROM. i might just flash that and see...
Yeh thats a nice Rom, but the bug was present there for me too like in every LP Rom even on CM.
Cozmos23 said:
Yeh thats a nice Rom, but the bug was present there for me too like in every LP Rom even on CM.
Click to expand...
Click to collapse
I take it you are on CM now?
The Z3 is now .77 stock KitKat, the s4 is CM11 M11
Thats what it should look like:
{
"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"
}
so, overall, the power consumption in KK is way better than in L? [assuming similar usage]
cause i bought this phone already on L...
On WiFi it's as good as Kitkat, the problem starts when you have mobile data enabled, from what I hear the issue carried on into the test builds of Android M.
Phonearena even did an article on the issue, and it has the 3rd or 4th most votes on Google 's bug tracker yet it's still labeled as small priority... I hope Sony fixes it by itself somehow.
This plagued my Le Pro3 and Oneplus 3T...It is 100% fine on OOS but when you flash an AOSP/CAF-based ROM there will be a few occasions where the status bar will reflect no signal. It's purely cosmetic but it can be misleading when I'm driving around in an unknown area and not be aware if I can make a call or not while using Android Auto.
Any devs able to chime in? Currently tested RR and it had the issue. I believe all devices are using the same device tree though to build from source. The system is reading 99 ASU which is returning an unknown signal strength which tells the system to display no signal. Any idea where the 99 asu is being read from?
{
"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 have had the exact same issue on multiple devices running Lineage or Lineage based ROMs: ZUK Z1, Meizu PRO5 and One plus 5T.
All of them tend to bounce around no bars (ASU 99) and full bars but the network speed doesn't seem to be actually affected.
Meanwhile, all of their stock ROMs, even the ZUK Z1 which ran Cyanogen OS, had always 3-5 bars at all times.
Seems to be a silly visual bug. Anyone knows of a fix?
SirYar said:
I have had the exact same issue on multiple devices running Lineage or Lineage based ROMs: ZUK Z1, Meizu PRO5 and One plus 5T.
All of them tend to bounce around no bars (ASU 99) and full bars but the network speed doesn't seem to be actually affected.
Meanwhile, all of their stock ROMs, even the ZUK Z1 which ran Cyanogen OS, had always 3-5 bars at all times.
Seems to be a silly visual bug. Anyone knows of a fix?
Click to expand...
Click to collapse
Not sure what it is, but is has been on many devices. It also displays on the Le Pro3, OP3T, and OP5/5T. I don't know if I have a reliable signal when I'm using Android auto and driving around in an unknown area.
Since I updated my device to Nougat 7.1 stock rom my phone switch off at 30-40% battery randomly.
I want to ask if replacing battery would solve this problem? Is there any other work around for this specific problem?
Sent from my XT1562 using Tapatalk
I have the same problem. Today when im using FB Messenger phone turns off with 46% battery..
karol12124 said:
I have the same problem. Today when im using FB Messenger phone turns off with 46% battery..
Click to expand...
Click to collapse
Same happened with me 2 days ago. Phone switch off randomly at any percentage below 50%
Sent from my XT1562 using Tapatalk
Same here, the device goes suddenly from 15-20% to 0 and then it shuts off. Could seem like an old battery symptom, but since it happens only on Nougat, it is likely to be software-related.
Can i say that have the same problem if my phone shut down on 7%?? :/ i dont understand why it happen
I have the same problem. To prevent this, I turn on battery power economy when it reaches 40%.
I've had a similar problem, changing the battery has solved it for me
harry_martini said:
I've had a similar problem, changing the battery has solved it for me
Click to expand...
Click to collapse
Did it happen to you on MXP with Nougat?
This is a bug in custom rom (LOS) I don't know about all other roms but this never used to happen when i was using stock 7.1.1
sachin1594 said:
This is a bug in custom rom (LOS) I don't know about all other roms but this never used to happen when i was using stock 7.1.1
Click to expand...
Click to collapse
I am using the Stock ROM.
{
"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"
}
https://screenshot.net/pt/m8xk9f7
https://screenshot.net/pt/m8xk9f7
It happened to me in all custom roms, after changing the battery it works fine
Sold my moto x play & bought MI Max 2. Goodbye guys
Hi there, having this exact same issue... any workaround or solution?
thanks in advance
I tried several roms, formatted, flashed stock, etc., didn't solve. Changing battery (it was 2 years old), the only and right solution for the problem.
Actually this happens when the battery gets weak. I have been experiencing the same problem for nearly two months. At first my X PLAY tended to switch off when charge was around 22 percentage and then battery got way too weak. After getting too weak,my X PLAY would switch off randomly at 30 to 40 battery percentage. Actually i have experienced this not only in X PLAY, but also in wide variety of Androids like XPERIA ZR , XPERIA Z2 , MOTO G2 , MOTO G4. So the solution for all these mobiles was to go for a new battery and it was brand as new with a healthy battery life.
Get back to MM problem will get solved. Done the same with my friends moto