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.
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.
Hi,
I hope I made this in the right section but I've got myself into a really nasty problem and I know how to fix it after spending full 10 hours. Maybe this will help anybody.
I re-used my Arc after a while and learned about custom roms and all. I've updated to Stock 2.3.4 - Stock 4.0.4 - Ultrakitkat 2.0.1 - Stock 4.0.4 (back because of trying to compare performances between custom and stock) - Ultimate HD 5.0.1.
When going from Ultrakitkat to Stock 4.0.4, after a day I woke up and found my phone rebooting Android on a loop while in the wall-charger. Went to take a shower and the phone was dead.
Charger didn't work, put it on my laptop USB and went on, only to find the battery at 100%. When disconnecting the phone, it immediately went blank and didn't turned on. I've looked for this problem for so many hours and tried flashing my romand kernel for some time (including phone drops dead WHILE in flashing) and trying out different way's to connect and boot but nothing worked. Installed many battery tools and apps but still nothing.
I;ve searched a lot and didn't found any conclusion anywhere, but combining every information online I've solved it!!
Apperantly there is an error inbetween roms, that when you go from custom rom + certain kernels, back to stock rom, it stops recognizing the battery.
To solve this (for me it worked):
Flashtool stock TFT 4.0.4
Fastboot flash the LUPUSV16 kernel (the magic trick!)
Turn on phone, and put it on a charger for 15 minutes, it should start recharging somewhere and show the correct battery %
I wanted to use the Ultimate HD just for a try and when flashing (I use Advanced Stock Kernel) + Ultimate HD
DO NOT WIPE BATTERY STATS! This will recreate the problem.
This worked for me and I hope this will help someone too who's thinking there is a problem with the battery.
Mostly reflashing the kernel does the job
Sent from my LT18i using xda app-developers app
0 or 100 percent battery
hridayharia said:
Mostly reflashing the kernel does the job
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
Leaving the phone turned off for some hours worked for me!
Thank you!
if you dont want see this problem
do not downgrade to stock kernel
Same issue here.. after fastbooting stock ftf.. Phone not charging and not recognized in fastboot/flashmode
Guys worked for me
Flash rush kernel after downgrading and tada its done.
Its just coz rush recognizes the hardware chip algorithm for battery stats
Sent from my Xperia Arc S using Tapatalk
Swapyyyyy said:
Guys worked for me
Flash rush kernel after downgrading and tada its done.
Its just coz rush recognizes the hardware chip algorithm for battery stats
Sent from my Xperia Arc S using Tapatalk
Click to expand...
Click to collapse
yes, it works flashing other kernel but i encountered a another problem. I lost some of the apps and keep geeting crashing report from diferent sistem apps Does some know how to extract those battery fix from those kernel am apllly it to stock kernel?
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.
Hello,
I have installed the android 6 to my p8 lite dual sim phone. C432b574 - I got the OTA update recently but it didn't update, and others told me to update manually, so I did.
I updated from b170.
The problem is the battery started heating up like never before with normal usage. Besides that when I checked the consumption levels it showed that hardware used 95-99% and softwares used the remaining. It is unnatural because I use the phone like I used to use with lollipop. I had been using it for 2 weeks now.
I tried wiping cache partition, updated all of the apps and someone told me the google services may screw up with the new system so I deleted those too, the problem still on.
Should I take it to the repair shop for a battery exchange? Maybe mine is faulty?
Regards, Ghostmuffin - thanks in advancew
I've also had those problems, the high hardware consumption is probably a first time error. For me, the one's causing havoc are the Google Play Services, actually you didn't remove anything, you can't remove them without basically turning your phone useless. Time to consider a deodexed ROM and using amplify (requires Xposed)
KillerDam said:
I've also had those problems, the high hardware consumption is probably a first time error. For me, the one's causing havoc are the Google Play Services, actually you didn't remove anything, you can't remove them without basically turning your phone useless. Time to consider a deodexed ROM and using amplify (requires Xposed)
Click to expand...
Click to collapse
I could remove the updates.
And you installed deodexed update or how did you manage to solve it then?
I'll wait for other replies before rooting the phone.
I have never rooted a phone before, one thing is not clear for me, can I install a custom android 6 while it is currently on the phone or should I downgrade it first? The other question is, does it wipe my data?
GhostMuffin said:
I could remove the updates.
And you installed deodexed update or how did you manage to solve it then?
I'll wait for other replies before rooting the phone.
I have never rooted a phone before, one thing is not clear for me, can I install a custom android 6 while it is currently on the phone or should I downgrade it first? The other question is, does it wipe my data?
Click to expand...
Click to collapse
This is emui problem don't worry it's normal. This occurs on every Huawei device.
Suleiman01 said:
This is emui problem don't worry it's normal. This occurs on every Huawei device.
Click to expand...
Click to collapse
Well I worry because with the heating up the battery life is reduced. And I wonder if it can be solved because in general the marshmallow is much better than lollipop
GhostMuffin said:
Well I worry because with the heating up the battery life is reduced. And I wonder if it can be solved because in general the marshmallow is much better than lollipop
Click to expand...
Click to collapse
Well my device also heats up when playing heavy games like gta san andreas, modern strike,asphalt 8 etc.... I think this is due to octa core processor. Which generates more heat as compare to quad core. I haven't used any octa core devices other than this so might be wrong.
Suleiman01 said:
Well my device also heats up when playing heavy games like gta san andreas, modern strike,asphalt 8 etc.... I think this is due to octa core processor. Which generates more heat as compare to quad core. I haven't used any octa core devices other than this so might be wrong.
Click to expand...
Click to collapse
I am not playing games, and it didn't warm up before while just browsing or texting.
GhostMuffin said:
I could remove the updates.
And you installed deodexed update or how did you manage to solve it then?
I'll wait for other replies before rooting the phone.
I have never rooted a phone before, one thing is not clear for me, can I install a custom android 6 while it is currently on the phone or should I downgrade it first? The other question is, does it wipe my data?
Click to expand...
Click to collapse
Removing updates fixes nothing, as it seems to be a problem with Marshmallow itself, and yes, I downloaded a custom ROM, it's not a very advanced procedure but you should be careful. You should install it over the current ones, making wipes with a custom recovery, and yes, it will wipe your data, however you can back it up from recovery.
KillerDam said:
Removing updates fixes nothing, as it seems to be a problem with Marshmallow itself, and yes, I downloaded a custom ROM, it's not a very advanced procedure but you should be careful. You should install it over the current ones, making wipes with a custom recovery, and yes, it will wipe your data, however you can back it up from recovery.
Click to expand...
Click to collapse
But if it is with marshmallow, a custom rom will still have this problem, won't it? - and which custom rom should i install? from where did you download it?
GhostMuffin said:
But if it is with marshmallow, a custom rom will still have this problem, won't it? - and which custom rom should i install? from where did you download it?
Click to expand...
Click to collapse
Maybe you should try custom kernel before flashing a rom.
Suleiman01 said:
Maybe you should try custom kernel before flashing a rom.
Click to expand...
Click to collapse
From my own experience, it seems like it's a wakelock problem. And using Xposed on a stock Rom broke calls, so that's why I was suggesting it
---------- Post added at 11:08 AM ---------- Previous post was at 11:06 AM ----------
GhostMuffin said:
But if it is with marshmallow, a custom rom will still have this problem, won't it? - and which custom rom should i install? from where did you download it?
Click to expand...
Click to collapse
Yes, but they're much more customizable, as I said, if it's a wakelock problem, Amplify will solve it. I recommend Sokoban's ROMS and Nautilus
KillerDam said:
From my own experience, it seems like it's a wakelock problem. And using Xposed on a stock Rom broke calls, so that's why I was suggesting it
Yes, but they're much more customizable, as I said, if it's a wakelock problem, Amplify will solve it. I recommend Sokoban's ROMS and Nautilus
Click to expand...
Click to collapse
Well, I give it a try, I can return to stock lollipop if it doesn't help after all. I don't think a battery extender will solve the problem, though.
GhostMuffin said:
Hello,
I have installed the android 6 to my p8 lite dual sim phone. C432b574 - I got the OTA update recently but it didn't update, and others told me to update manually, so I did.
I updated from b170.
The problem is the battery started heating up like never before with normal usage. Besides that when I checked the consumption levels it showed that hardware used 95-99% and softwares used the remaining. It is unnatural because I use the phone like I used to use with lollipop. I had been using it for 2 weeks now.
I tried wiping cache partition, updated all of the apps and someone told me the google services may screw up with the new system so I deleted those too, the problem still on.
Should I take it to the repair shop for a battery exchange? Maybe mine is faulty?
Regards, Ghostmuffin - thanks in advancew
Click to expand...
Click to collapse
Yes, there is few problems with Marshmallow and battery.. Flash Custom ROM, i haven't had any problem since flashing custom rom ..
Sent from my ALE-L21 using XDA-Developers mobile app