what's the issue with this wakelock?
According to BatterBatteryStats my screen was on for 40m but awake for one hour and 40 min. WHY??
It's driving me nuts. I'm running all stock after a factory reset, have nothing installed except BBS and whatsapp, signal at max for most of the time — why is still happening?
It's so frustrating. It feels like my phone could get a much better battery life if this issue was resolved.
Any ideas?
I could always try a different ROM I suppose, but I don't have any experience doing that and kind of scared..
This shouldn't happen on stock.
its from *can you hear me now* lol i kid. At this moment 4.3 has a lot of issues. Are you running stock? Flashing different Rom is nothing to be afraid off. Make sure to follow the instruction step by step. If you are not sure about something feel free to ask here. There are many users that will help you.
I had this issue in 4.2.2 as well, thought that this update would finally address that.
It simply is caused by the modem waking up the phone to transmit data. But anyway, a Google search would've taken you here... http://forum.xda-developers.com/showpost.php?p=41876742&postcount=1
korockinout13 said:
It simply is caused by the modem waking up the phone to transmit data. But anyway, a Google search would've taken you here... http://forum.xda-developers.com/showpost.php?p=41876742&postcount=1
Click to expand...
Click to collapse
So it seems I need a kernel change instead of a rom change to solve this issue? is that correct?
which kernel should I use?
I'm getting two hours of screen time currently, pretty bad.
No, I don't think that's necessary. You're going to want to check for apps that are using data in the background. Or perhaps connection where you are is just bad.
Sent from my Nexus 7 using Tapatalk 4 Beta
Since android 4.3 my battery was draining fast.
During the night (+- 7 hours), with everything off (wifi, 3g, bt, sync etc) it drained about 20 - 25 %!
BBS showed 'msm_hsic_host' kernel wakelocks.
I didn't had this with android 4.2.3 so I was glad I did a nandroid backup of this before I upgraded to 4.3.
However, then the 'strange' thing happened.. after the restore it was still draining.
I did a factory reset, installed no apps but still draining..
Finally I found the solution!! I saw some people had troubles with android 4.3 and tele2 (dutch provider). It gave sim card resets so they had to re-enter their pincode. The solution was to go back to the .48 radio/modem.
Hmmm.. I quickly googled and read that CWM Nandroid didn't performed a backup/restore of the radio! Flashed the .48 radio myself and my problem is solved!!
FYI, I have the dutch 'telfort' provider.
elpino.rv said:
Since android 4.3 my battery was draining fast.
During the night (+- 7 hours), with everything off (wifi, 3g, bt, sync etc) it drained about 20 - 25 %!
BBS showed 'msm_hsic_host' kernel wakelocks.
I didn't had this with android 4.2.3 so I was glad I did a nandroid backup of this before I upgraded to 4.3.
However, then the 'strange' thing happened.. after the restore it was still draining.
I did a factory reset, installed no apps but still draining..
Finally I found the solution!! I saw some people had troubles with android 4.3 and tele2 (dutch provider). It gave sim card resets so they had to re-enter their pincode. The solution was to go back to the .48 radio/modem.
Hmmm.. I quickly googled and read that CWM Nandroid didn't performed a backup/restore of the radio! Flashed the .48 radio myself and my problem is solved!!
FYI, I have the dutch 'telfort' provider.
Click to expand...
Click to collapse
I ran into the same problem. Same fix, as well. Fance - Orange/Free provider.
All instances of this problem I have seen so far have been from outside the US. So much for being an international phone :lol:
elpino.rv said:
Since android 4.3 my battery was draining fast.
During the night (+- 7 hours), with everything off (wifi, 3g, bt, sync etc) it drained about 20 - 25 %!
BBS showed 'msm_hsic_host' kernel wakelocks.
I didn't had this with android 4.2.3 so I was glad I did a nandroid backup of this before I upgraded to 4.3.
However, then the 'strange' thing happened.. after the restore it was still draining.
I did a factory reset, installed no apps but still draining..
Finally I found the solution!! I saw some people had troubles with android 4.3 and tele2 (dutch provider). It gave sim card resets so they had to re-enter their pincode. The solution was to go back to the .48 radio/modem.
Hmmm.. I quickly googled and read that CWM Nandroid didn't performed a backup/restore of the radio! Flashed the .48 radio myself and my problem is solved!!
FYI, I have the dutch 'telfort' provider.
Click to expand...
Click to collapse
I put your post into my thread for people looking for an answer to this wakelock. Hope you don´t mind. Credits to you are there.
http://forum.xda-developers.com/showthread.php?p=44122105
:fingers-crossed:
elpino.rv said:
Since android 4.3 my battery was draining fast.
During the night (+- 7 hours), with everything off (wifi, 3g, bt, sync etc) it drained about 20 - 25 %!
BBS showed 'msm_hsic_host' kernel wakelocks.
I didn't had this with android 4.2.3 so I was glad I did a nandroid backup of this before I upgraded to 4.3.
However, then the 'strange' thing happened.. after the restore it was still draining.
I did a factory reset, installed no apps but still draining..
Finally I found the solution!! I saw some people had troubles with android 4.3 and tele2 (dutch provider). It gave sim card resets so they had to re-enter their pincode. The solution was to go back to the .48 radio/modem.
Hmmm.. I quickly googled and read that CWM Nandroid didn't performed a backup/restore of the radio! Flashed the .48 radio myself and my problem is solved!!
FYI, I have the dutch 'telfort' provider.
Click to expand...
Click to collapse
Hi elpino! First of all, I am on "Telfort" too. Jammer
I am having the same problems you have, with Telfort... Anyway, this weekend I had an amazing battery life, with 3G off... but guess what? I was in Belgium, for pukkelpop... so no Telfort!
Anyway, can you explain to me this whole issue like I was a dumb 2 year old? I am on stock 4.3, lousy battery life, msm_hsic_host wakelocks draining it.
I want to better understand the problem you identified... and the fix of course.
thanks!
rlop.es said:
Hi elpino! First of all, I am on "Telfort" too. Jammer
I am having the same problems you have, with Telfort... Anyway, this weekend I had an amazing battery life, with 3G off... but guess what? I was in Belgium, for pukkelpo... so no Telfort!
Anyway, can you explain to me this whole issue like I was a dumb 2 year old? I am on stock 4.3, lousy battery life, msm_hsic_host wakelocks draining it.
I want to better understand the problem you identified... and the fix of course.
thanks!
Click to expand...
Click to collapse
I think my problem was written well in my first post. Also how I found the fix (went back to 4.2.2 but my problem was still there, then I found out that my radio/modem was still .84, the 4.3 version).
Anyhow, you probably want to know how to flash the .48 radio/modem. Just go to http://forum.xda-developers.com/showthread.php?t=2087227, download the .48 radio/modem and flash it like instructed in that post. (via custom recovery or manually with fastboot)
[edit] I'm now running android 4.3 with the .48 radio/modem. Battery life is good and no problems seen yet with that old modem/radio version.
elpino.rv said:
I think my problem was written well in my first post. Also how I found the fix (went back to 4.2.2 but my problem was still there, then I found out that my radio/modem was still .84, the 4.3 version).
Anyhow, you probably want to know how to flash the .48 radio/modem. Just go to http://forum.xda-developers.com/showthread.php?t=2087227, download the .48 radio/modem and flash it like instructed in that post. (via custom recovery or manually with fastboot)
[edit] I'm now running android 4.3 with the .48 radio/modem. Battery life is good and no problems seen yet with that old modem/radio version.
Click to expand...
Click to collapse
Thanks! I will try it then!
About the problem, I was just curious on how specific it was to Telfort. Did you try it with another sim card?
nope, haven't tried another simcard.
How big was the difference in battery life between .84 and .48?
It's especially noticeable during the night (+- 7 hours) when I turned everything off (wifi, 3g, sync, BT etc). With the .84 modem it took about 25%, with the .48 modem it takes about 1%.
Note that I have faux kernel. I think with stock kernel it could be more then 1% during the night, maybe 5% or something. Also note that I changed the kernel later. It's not faux kernel that solves the problem.
elpino.rv said:
I think my problem was written well in my first post. Also how I found the fix (went back to 4.2.2 but my problem was still there, then I found out that my radio/modem was still .84, the 4.3 version).
Anyhow, you probably want to know how to flash the .48 radio/modem. Just go to http://forum.xda-developers.com/showthread.php?t=2087227, download the .48 radio/modem and flash it like instructed in that post. (via custom recovery or manually with fastboot)
[edit] I'm now running android 4.3 with the .48 radio/modem. Battery life is good and no problems seen yet with that old modem/radio version.
Click to expand...
Click to collapse
elpino, your fix worked for me!
Before, I was getting 18h of battery life (while doing practically nothing), 25% awake time and 39% battery life dedicated to Android OS.
After your fix, and in my first cycle, I got 1day and 18h of battery life, 7% awake time, and 13% Android OS.
So, it seems it works here as well!
Thanks!
I have msm_hsic_host wakelock on 4.4.2. Someone have a solariów?
No data, no 3g.
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
I have the same problem on t-mobile in the UK. I am using stock ROM with Franco kernel.
Related
OK, this is unbelievable.
The battery drain on XXJVO was driving me crazy. Reading the forums I noticed some people said the Android OS issue was fixed on 2.3.4. Yesterday, I flashed XXJVR with re-partition and bootloaders via Odin, using the OXAJVQ CSC. I also installed the Voodoo lagfix for XXJVR.
I did a factory reset before and after the flash. Did a battery pull, all the steps that we're used to.
For my surprise, a few minutes ago, the phone discharged in 8 hours to 47%. Guess what? Its the Android OS again. Take a look at the attached screenshots.
Did I do something wrong? Is this normal on 2.3.4?
EDIT: Following $omator and madrooster's advice, I decided to flash everything again from scratch and install all the apps directly from the Android Market. Apparently, the issue was being triggered by a restored appdata backup via TitaniumBackup. I've been using the phone for about a week now, with no issues at all.
im running custom rom gingerreal 7.1.4 JVQ with galaxianEE kernel and lagfix enabled. my modem is ZSJPG and csc XAJVQ.
no issues like u have.
but i have to say, that the battery drain is heavier than on froyo.
Man, that's pretty serious drain. I'm running Ramad's stock deodexed JVR since it was postes with semaphore kernel and my usage is never more than 15%. Why don't you post a pic of the bigger graph?
only way to avoid battery drain is that you remove the battery from phone
have no idea haw did you managed to break jvr but you did it =)
i guess youve runed some app that was not letting phone to sleep
or the system got some broken ones tat caused this (yes wrongly flashed system maybe hehe)
btw notice the blue line under your graph - it should look more like on attached screen
Im also running gingerreal 7.1.4 JVQ with semaphore 1.32 and after 2 weeks of use no battery drain.
Android OS is always below 10% (mostly on 4-5%)
The Android OS bug was fixed from stock JVQ onwards. The reason you guys experience that is because you are using custom kernels built from old source codes released by Samsung or heavily modified by the developer. Go complain to your respective custom kernel thread.
jbdroid said:
The Android OS bug was fixed from stock JVQ onwards. The reason you guys experience that is because you are using custom kernels built from old source codes released by Samsung or heavily modified by the developer. Go complain to your respective custom kernel thread.
Click to expand...
Click to collapse
Thanks jb. That could be the reason. I am using Voodoo kernel, maybe that's what causing the drain. Has anyone else on Voodoo experienced the same problem?
Heritz said:
Thanks jb. That could be the reason. I am using Voodoo kernel, maybe that's what causing the drain. Has anyone else on Voodoo experienced the same problem?
Click to expand...
Click to collapse
Were you playing orientation/sensor-based games?
jbdroid said:
Were you playing orientation/sensor-based games?
Click to expand...
Click to collapse
jb, I remember that I played Captain America in the morning, but the phone froze and I had to battery pull it. After the restart, I didn't touch it again for like 6 hours. In the night, the phone rang and when I tried to pick up the call, the screen wouldn't turn on, so I had to battery pull it again.
After I turned it back on, I checked the battery stats and noticed the Android OS was running crazy, as you can see in the screenshots.
Captain America afaik is not sensor based, and I battery pulled the phone after I played, cuz it froze. I'd love to blame the game, but I cannot.
Edit: But... looking at the stats, the orientationd process is right next to the Android OS. Could this happen if the phone wasn't resting on a flat surface? :S
Yup the orientationd process was burning you battery juice, the reason why you got Android OS bug. I guess you should try to change your custom kernel or if you really like your current phone setup, you should install Watchdog lite or any similar app to monitor system processes, such as Android OS, for unusually high cpu usage and just reboot your phone when it does occur
i wonder what else is broken in this guys phone that wathcdog and reserting will not fix =)
$omator said:
i wonder what else is broken in this guys phone that wathcdog and reserting will not fix =)
Click to expand...
Click to collapse
$omator help me out here. What kernel would you recommend for JVR that keeps everything as stock as possible but includes lagfix? I use Voodoo since it is pretty light, but it doesn't seem to behave so well after all.
stock + cfroot is always a win
jbdroid said:
The Android OS bug was fixed from stock JVQ onwards. The reason you guys experience that is because you are using custom kernels built from old source codes released by Samsung or heavily modified by the developer. Go complain to your respective custom kernel thread.
Click to expand...
Click to collapse
+1 very true the kernels for me to showd diffrnt results
No battery drain for me here I've been on it for weeks with heavy use friend, never pass 5 hours in any froyo firmware
Sent from my GT-I9000 using xda premium
Android os drain goes away for my 2.3.3 kg3 stock setup after wiping cache partition and dalvik cache. Ran for weeks and never came back.
Sent from my GT-I9000M using XDA app
This battery drain problem is caused by the kernel you have. It is caused by a bug in a specific device driver.
The phone tries to go into power save mode but something prevents it. When the phone fails to reach a low power mode, you see the battery drain. In summary, if you run a custom, non stock Rom you might not have the battery drain fix. Try to make sure that any custom kernel you use has the same kernel version as stock.
Wow that is pretty big drain.. On my xxjvr (2.3.4 ) it only uses 9 to 10% don't know what's wrong though
Sent from my GT-I9000 using xda premium
$omator said:
stock + cfroot is always a win
Click to expand...
Click to collapse
Not for me...
1. Clean the phone.
Flashed JVR (from samfirmware). Flashed CF-Root-XX_OXA_JVR-v4.1-CWM3RFS. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX.
All closed by me in settings (NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 22.00 hour battery was at 98%.
Next day in the morning at 10.30 hour, the phone beeps that the battery is at 15%... Looking in the Battery use, discover that in about 12 hours, the Android OS (90%) is draining the battery. OMG...
2. Fully charge the phone, clean the phone.
Flashed JVR (from samfirmware). Flashed speedmod-kernel-k15i-t10. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX.
All closed by me in settings(NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 22.00 hour battery was at 96%. Next day in the morning at 09.30 hour, check the phone.
Surprise! At about 12 hours, the battery "lose" only 4%. And NO Android OS in the battery use.
3. Next day, clean the phone. Fully charge the phone.
Flashed JVR (from samfirmware). Flashed TalonDEV-0.4.4.22-1200-I9000-BIGMEM-CWM3. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX. All closed by me in settings(NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 23.00 hour battery was at 98%. Next day in the morning at 08.00 hour, check the phone.
Surprise! At about 10 hours, the battery "lose" only 5%. And NO Android OS in the battery use.
4. Next day, clean the phone. Fully charged battery.
Download again the CF-Root-XX_OXA_JVR-v4.1-CWM3RFS.
Flashed JVR (from samfirmware). Flashed again CF-Root-XX_OXA_JVR-v4.1-CWM3RFS. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX.
All closed by me in settings (NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 21.00 hour battery was at 90%. Next day in the morning at 07.00 hour, looking in the Battery use, discover that in about 8 hours, the Android OS (90%) is draining the battery and the battery is at 25%...
I'm not a specialist in Android, but with this experiment, understand that in my case, the "drayner" of the battery was decided by the kernel, and I decided to flash the JVR stock+ with speedmod-kernel-k15i-t10.
I don't say that the CFroot is bad or that another kernel is good, but for me CFroot don't works good.
I have problems with the battery of my nexus 7 since last week when I realized it was charging slow, after that it runs down very quickly, and tried everything that is on this forum and nothing. I put The latest franco kernel. and nothing.... is the battery damage ??
nexus 7 stock rom 4.2.2
unlocked and rooted
franco kernel r61
sorry for my bad english :silly:
THANKS
Probably, but have you tried perform factory reset?
Sound like software related problem to me, like some rouge apps running all the time and prevent your tablet from deep sleep.
why always me said:
Probably, but have you tried perform factory reset?
Sound like software related problem to me, like some rouge apps running all the time and prevent your tablet from deep sleep.
Click to expand...
Click to collapse
Thanks
Yes,did a factory reset,flashed stock rom
Hi, i've been getting this on my lollipop gpe s4 i9505. how can i fix this? it's been present for like 5-6 hours.
Danvdh lollipop?
He says it is just a visual bug.
GDReaper said:
Danvdh lollipop?
He says it is just a visual bug.
Click to expand...
Click to collapse
yes, then why in one hour, the battery went down by 11%. BBS say's it was in deep sleep during that time. there was only like 1 minute wlan_rx_wake. nothing else.
Only thing i was able to pinpoint was the mobile radio active. i've flashed his 'fix' but it doesn't do much.
salespalace said:
yes, then why in one hour, the battery went down by 11%. BBS say's it was in deep sleep during that time. there was only like 1 minute wlan_rx_wake. nothing else.
Only thing i was able to pinpoint was the mobile radio active. i've flashed his 'fix' but it doesn't do much.
Click to expand...
Click to collapse
What kernel? I had massive battery drain using Alucard's kernel.
GDReaper said:
What kernel? I had massive battery drain using Alucard's kernel.
Click to expand...
Click to collapse
Googy's kernel, i think it's most likely to do with the modem, i might flash the latest kitkat modem, to see if there's any changes.
there's no difference in flashing a modem on the s4, than any other device right? through recovery.
salespalace said:
Googy's kernel, i think it's most likely to do with the modem, i might flash the latest kitkat modem, to see if there's any changes.
there's no difference in flashing a modem on the s4, than any other device right? through recovery.
Click to expand...
Click to collapse
I think it is done through Odin.
Did you find any sollution to this problem? I'm facing it too, idle battery performance is really bad and lot of apps have this Mobile Radio Active on for hours!
Hi. To begin with i have to say that, yes, I have searched to find the solution, but havent found it yet.
So my problem is that my tablet is unusable, it is wery slow (5.1.1 CM) and the battery doesnt even last overnight whan not using it. I hava tried fs trim and so on, doesnt work. However when I boot into safemode the performance of the tablet is OK and so is the battery. So does anybody have any sugestions how could I fix it or what rom should I use? Also I have no apps installed apart from gapps.
Thanks
did u update last TWRP?? it's important if u came from kitkat. try flash another rom or try to flash just the rom
ahvipardik said:
Hi. To begin with i have to say that, yes, I have searched to find the solution, but havent found it yet.
So my problem is that my tablet is unusable, it is wery slow (5.1.1 CM) and the battery doesnt even last overnight whan not using it. I hava tried fs trim and so on, doesnt work. However when I boot into safemode the performance of the tablet is OK and so is the battery. So does anybody have any sugestions how could I fix it or what rom should I use? Also I have no apps installed apart from gapps.
Thanks
Click to expand...
Click to collapse
I noticed longer battery life and better performance on KitKat 4.4.4, CM11 or AOSP(Paranoid) version. ~30% longer battery life, no battery drain when sleeping,
my spec: Nexus 7 2012 3G, ext4 latest TWRP +MultiROM
also you should use Greenify app.
hey guys, so i have a retgb stock rom for lollipop, how would i go about just flashing the modem from that rom. I want to do this to test a theory i have about the battery drain on marshmallow, to see if its caused by the new modem, any help would be appreciated...
certainly not caused by the modem. Did you clean flash? What did you do to upgrade? etc? have you disabled wifi/bluetooth scanning in the extended location settings, deleted play services data yet?
Benjamin_L said:
certainly not caused by the modem. Did you clean flash? What did you do to upgrade? etc? have you disabled wifi/bluetooth scanning in the extended location settings, deleted play services data yet?
Click to expand...
Click to collapse
updated from a stock moto x play single sim, retgb to marshmellow via normal ota, had no root or bootloader unlocked. After the ota i installed twrp and rooted, wiped cache and data, did a factory reset. Then did everything you said above. Then tried with squid kernel, still have massive battery drain about 1 hour sot and barely lasts me 1 day. So yea... i thought it was worth a shot just trying my idea about the modem...
Tvman1231 said:
updated from a stock moto x play single sim, retgb to marshmellow via normal ota, had no root or bootloader unlocked. After the ota i installed twrp and rooted, wiped cache and data, did a factory reset. Then did everything you said above. Then tried with squid kernel, still have massive battery drain about 1 hour sot and barely lasts me 1 day. So yea... i thought it was worth a shot just trying my idea about the modem...
Click to expand...
Click to collapse
Really strange. Any special apps you use? Whats the app on top of your battery stats?
Benjamin_L said:
Really strange. Any special apps you use? Whats the app on top of your battery stats?
Click to expand...
Click to collapse
Mobile standby and phone idle, i have xposed and greenify installed, no speacial apps installed if you dont include kernel adiutor. Im gonna try going back to 5.1.1 stock and try a 6.0 stock rom via twrp, il post the results later.
Frequency stats probably show deep sleep as unused state?
Benjamin_L said:
Frequency stats probably show deep sleep as unused state?
Click to expand...
Click to collapse
no, deep sleep is being used like 92% of the time
So basically everything is working fine. In some other thread I read xposed seriously cripples battery life. I'm not using it so I can't tell
Benjamin_L said:
So basically everything is working fine. In some other thread I read xposed seriously cripples battery life. I'm not using it so I can't tell
Click to expand...
Click to collapse
well im currently going back to stock 5.1.1 for now, im gonna try my therory, then i try with and without xposed, see if it makes a difference
@Benjamin_L well i can safely say that xposed makes no differece that i can see to the battery life so far. After flashing the old stock (5.0, including the modem, through fastboot) then going back to 6.0 by flashing the stock rom by GtrCraft via twrp my battery life seems to have improved quite a bit. So maybe it is the modem after all? Also why did you say it cant be the modem in the first post? just curious...
Tvman1231 said:
@Benjamin_L well i can safely say that xposed makes no differece that i can see to the battery life so far. After flashing the old stock (5.0, including the modem, through fastboot) then going back to 6.0 by flashing the stock rom by GtrCraft via twrp my battery life seems to have improved quite a bit. So maybe it is the modem after all? Also why did you say it cant be the modem in the first post? just curious...
Click to expand...
Click to collapse
I ran both modems on 5.1.1 and 6.0 on several roms and stock firmwares and there was no difference, except for rom related things. And I never heard modem influences battery life dramtically if at all. On my old n4 i flashed several basebands and never noticed any difference in battery consumption at all.
Benjamin_L said:
I ran both modems on 5.1.1 and 6.0 on several roms and stock firmwares and there was no difference, except for rom related things. And I never heard modem influences battery life dramtically if at all. On my old n4 i flashed several basebands and never noticed any difference in battery consumption at all.
Click to expand...
Click to collapse
well, my phones now getting around 4hrs sot so im happy. XD