hello all, this is my first post, and i am new to this kind of things but i have been downloading and testing aloooooooooooot of roms, and i have been suffering from battery drain until i find the solution by my self, and i said why not share it with all this people facing the same problem.
first flash the LT15i_4.1.B.0.431_Europe 1 from here http://forum.xda-developers.com/showthread.php?t=1330314
flash some kenel which will give you CWM ( any kernel )
then download this one again (KA20.1_Ice_Cream_Sony_Arc&ArcS) from here but please follow the instruction of how to install this one http://forum.xda-developers.com/showthread.php?t=1539752
after this download from the same post the " on screen bottons '' because the light of bottons of the arc goes off with this patch. do it if you like i have done it. here is the link http://www.mediafire.com/?g82pgwabvx80dbg
now here is what to do after installing all these things and having arc ran under KA20.1 go back to LT15i_4.1.B.0.431_Europe and flash only the KERNEL of it and nothing else or you can just flash the stock ics kernel with flashtool or fastboot but without CWM just and only the stock kernel withouuuut CWM
we are going to install CWM dont be afraid, now turn on the phone and go to the market and install from it Xperia CWM.
when it is installed open Xperia CWM on your menu and install the CWM or just follow this http://forum.xda-developers.com/show....php?t=1437840
you are done now all you have to do is desable bravia from the brightness menu and leave the baseband on 72 dont change it and you will notice a big diffirence in the battery life.
download the stock kernel that works just fine from the attachmente
if it works to you please say it.
What is the battery usage you got with this trick
2 days with usage and stuff but in sleep mode it stays where ever is it doesnt change. in usage you get less battery drain. try it your self and see
So essentially your talking about installing a Rom then using a stock kernel, which is suggested in most Rom threads for ics as Sony hadn't released the source, you'll find this change now as the source is out.
Sent from my LT18i using XDA
I see. Quite astonishing that i'd used this kind of method when flashing the KA20.1 ROM. The differences is i just re-flash back the LT18i V2 kernel, install and setup Fast Reboot and freeze some unused .apk in Link2SD. Luckily the battery is 34% after 3 days using it.
Demons Of Razgriz
LT18i KA20.1 Ice Cream Sony
LT18i V2 Kernel
Related
Hey all.
I cannot post in the development section as I just recently made an account.
Sorry to ask a noob question if it is, but I had stock SG2 with carrier bloatware installed when I first brought my SG2 and last night I installed Lite'ning ROM 1.4, now Im not 100% sure but touchWiz and other Samsung apps etc are still installed, my question is - wats the proper noob friendly way to completely wipe my phone and then flash with Lite'ning rom ?? So its like a fresh install as if I just reformatted my PC. Or is this not needed ??
harri077 said:
Hey all.
I cannot post in the development section as I just recently made an account.
Sorry to ask a noob question if it is, but I had stock SG2 with carrier bloatware installed when I first brought my SG2 and last night I installed Lite'ning ROM 1.4, now Im not 100% sure but touchWiz and other Samsung apps etc are still installed, my question is - wats the proper noob friendly way to completely wipe my phone and then flash with Lite'ning rom ?? So its like a fresh install as if I just reformatted my PC. Or is this not needed ??
Click to expand...
Click to collapse
hey!
Lite'ning ROM 1.4 is not a complete replacement of your stock s/w. Its just a Stock Kernel with some tweaks. Lite'ning ROM 1.5 is more or less the same thing with a few more tweaks and LitePro removed the TouchWiz from it. You can install Lite'ning ROM 1.5 if you want to get rid of TW4.
Now, coming to wiping everything, I am not an expert on that... all I can say that its not as simple as reformatting the PC . But you can try Factory Reset (shutdown phone then hold vol-, home and power button together).
HTH,
Dull
Thanks for your info.
So if I reboot into recovery and do Factory reset, would I still be able to go into Download to instal Fresh lite'ning ROM 1.5 ?? I feel as if because I have not completely wiped my phone I dont get any real battery improvements, some people claim in VillianROM they have 2x better battery!!
For VillianROM how would you install that ?? odin doesn't work with that type of file.
Thank you
For VR, may be you can push CF-Root using Odin and flash VR 1.4 under recovery mode
Before flash just ensure you wipe cache partition (vol up + home + power) use vol buttons to navigate the menu and select with home button. Also download 'battery callibrator' from market place and run this when you have 100 battery. After each flash I do this so my battery data is new each time I install a new rom.
You have to use a different method to flash Villian rom, as you can't with Odin his instructions are pretty easy to follow. I personally found litening a better rom but Stock KF3 has been the most stable and better battery for me
O2 UK i9100
Sent from my GT-I9100 using XDA App
ok thank you for your info mate will try your suggestions
I have this way and I get really bad stutters when I open close things on my phone, I think I may go back to lite'ning 1.4
Mine SGS2 with Lite'ning ROM 1.5 still has TouchWiz and LauncherPRO in addition.
I installed my 1.5 straight over my bloated phone. If i now cleared cache and done a factory wipe, can i leave it at that? or should i reflash over it again after doing that?
i was trying to make full format and I made a mess...
i choose full reformat and i install SDE
boot into the AngStrom OS
i trying to Install android firmware 2.4.83
i choose "Update Firmware"
but
update failed
what should i do now?
somebody help please...
please...someone???
Im stuck here...
Hi!
Try another cable or download again the firmware. Verify if it's the good version.
Tell us which tab you have
Sent from my GT-I9000 using XDA
And try to learn how to use the search function of this forum, as we had this question and many answers allready.
for ex: did you make sure that the aos file has the correctg name?
Or maybee you could post the complete errorcode!
Sorry if there is another same thread
When I installed UrukDroid 1.6.4 update I got 2 problems..
1.when the device was in standby mode,the hard drive was working and I consumes the battery in a few hours.
2.I tried to install applications from the market but no luck because ''not be installed in space usb or sd card''
So I decided to do Reformat the Device...
I installed SDE
after I installed android firmware(bizcuite you had absolutely right buddy.i download again the firmware and everything is ok now.)
I installed the custom kernel + initramfs and then UrukDroid 1.6.
so far so good...
when I tried to install again UrukDroid 1.6.4 update the Device stuck (The screen and buttons didn't respond)...
now I reinstall again the SDE and android firmware
reinstall the custom kernel + initramfs
and reinstall the custom kernel + initramfs UrukDroid
i am trying to reinstall UrukDroid but the Device stuck in screen ''tranfer now installation file over usb and press power button once''
what should i do now?
i have a Archos A70H
sorry but my english is not very good
As stated here and in the dev part, stay away from uruk as long as you don't know what you are doing.
Uruk is still not ready for the harddrive version.
Thanks for your reply but could you be a little more gentle with me???
still learning here...
so I can not installed yet UrukDroid...???
Simple method will start installation on SDCard or HD (A70H)
http://code.google.com/p/urukdroid/wiki/EasyInstall
Thanks again for your answer...
It wasn't meant to be hard on you.
Uruk is optimised for the sd version.
ATM it is installed on the harddrive and therefore it consumes alot more batterie and is not really as stable as on the A70S.
That's why you really have to know what you are doing.
And $auron has the Problem ATM that his device is broken, so the development is not as fast as before.
I think I got much info here.
fzelle said:
It wasn't meant to be hard on you.
Uruk is optimised for the sd version.
ATM it is installed on the harddrive and therefore it consumes alot more batterie and is not really as stable as on the A70S.
That's why you really have to know what you are doing.
And $auron has the Problem ATM that his device is broken, so the development is not as fast as before.
Click to expand...
Click to collapse
i understand...
have you any advice for my device???
Not ATM.
The problem is that the A70H is different to the A70S as the h only has 2gb of ssd and that is partitioned differently and as neither $auron nor divx118 have one to test it will probably not change in the near feature.
So atm the best thing you can do is chulri's root or live with the restrictions of UrukDroid.
fzelle said:
Not ATM.
The problem is that the A70H is different to the A70S as the h only has 2gb of ssd and that is partitioned differently and as neither $auron nor divx118 have one to test it will probably not change in the near feature.
So atm the best thing you can do is chulri's root or live with the restrictions of UrukDroid.
Click to expand...
Click to collapse
I did chulri's root
(Install SDE , Install my android firmware , Install the custom kernel + initramfs)
but
when am in Developer Edition the device stuck and the screen does not respond
only in android edition the device works normally...but I have not superuser options...
I have same device, im running uruk 1.6.3 boot with .2 init everything runs smoothly but i also upgraded from 1.6.2 so maybe try an upgrade from there, i will try 1.6.4 though and let you know how it goes
Edit: ive upgraded to 1.6.4 and everything is running smooth, i had one bad startup where touchscreen was not at all responsive, a reboot in recovery an fix permission and clearin dalv cache and its now been a few days with no (unknown) force close, just a couple of my own doing lol
Sent from my A70H using XDA
When you are in standby mode the hard drive was work???
When my device is in sleep mode or standby my hdd doesnt spin an cause any abnormal drain.. yesterday i was out for 12 hours in he sun skateboardin and hiking with music on and/or in standby.. i had 67% batt left when i came home
Sent from my A70H using XDA
Dyverse said:
When my device is in sleep mode or standby my hdd doesnt spin an cause any abnormal drain.. yesterday i was out for 12 hours in he sun skateboardin and hiking with music on and/or in standby.. i had 67% batt left when i came home
Sent from my A70H using XDA
Click to expand...
Click to collapse
How is that possible????
with 1.6.4 ???
It shows a lower % at times then actual voltage drain of battery, if you deep sleep it an wake up the % will jump up from say a 50% to about 80%, i also take some power savin precautions like disablein wifi and using nightmode (thanks chainfire3d) it helps with display power and also no glare lol, but i havnt really ever had a power drain issue as far as it goes lol i guess i got lucky somehow or managed to do something righ for a change lol
Sent from my A70H using XDA
so..i have problem..again...
can someone tell me the steps to format like when I bought it???
i choose full reformat.
Install SDE , Install my android firmware , Install the custom kernel + initramfs
ok but...
the device starts normally android but the screen does not respond..
any ideas please???
Only touch screen is not responsive, or nothing is displayed at all?
You can still see the boot progress on the screen?
so...
i Install again the SDE and android firmware normally...(thank God)
no custom kernel + initramfs
reboot
the device is working normally in android mode.
When I go to the option dev edition the screen stuck to developer edition boot in progress...
when i reboot the device in normally mode the screen does not respond
i don't know what to do to solve the problem
So im dealing with this all frikn' day, so i was messing around and i wanted to flash Rachts legendary roms to remind me how awesome his work was and i gone to the Stock kernel and i was pressing the back button and simply nothing happend i was tapping the back button like crazy and it din't go to the Xrecovery. So i done a lot of other things but long story short gone back to Custom kernel and Poof! recovery loopin all day. So only Stock kernel works with the stock rom. Srsly guys i cant stand the 2.1!
Recovery loop happening on EVERY custom kernel.
No one knows the solution to this?
First start - need to press Home Button, them (next then first start)Back Button.Install it from FlashTool.
Hmm, this is weird, try to restore using seus and then install a custom kernel
Skickat från min ST18i via Tapatalk 2
well im on Rachts Sense rom 2.1 now Still on stock kernel.
Got Recovery Loop on Stock kernel too. -.- Im throwing my x8 into the garbage it has 0 use.
I tried everything, even some tutorials on Xda. Din't work, soo im just gonna crush my X8 with an axe or something. Im like getting no sleep , i was fixing it all day.
Spevky ...
1. Flashtool -> Restore back to stock (I think you know the tango).
2. Root through Flashtool (psneuter)
3. Then use x8toolbox to inject the dual-mode recovery and flash to the custom ROM of your choice.
EDIT: In case you're on a unlocked boot-loader ...
- ONLY flash the Stock Kernel FTF
- When flashing the Stock ROM FTF ONLY select system.sin, cache.sin, data.sin.
Do NOT flash any of the baseband parts or the loader.sin!
You find everything you need in the "Sony Ericsson" folder under the "My MediaFire" link in my signature.
In case of questions post or shoot me a PM; I'll reply as soon as possible.
@dude
I read your posts 5 times and I can't understand what is your problem and what you want to do..
you don't have xrecovery?
you don't have cwm?
you have softbrick?
you want the xrecovery files?
you want the cwm files?
you want dual recovery files?
What i've done.
Left my phone alone for 30 mins ( It got really hot)
Then i gone back to stock (Seus style)
Run 2.1 stock charged it to 100%
And turned off the phone
Flashed Alfs
And ran my backup of GDX v26.
WORKS.
And oh boy i got some wild bugs on the 2.1
For recovery option with stock kernel ,
Either rom should have recovery or you have to just push the 3 files named
1. xrecovery.tar
2. busybox
3. chargemon
in /system/bin/
Then only you can get recovery menu for stock kernel!!!!
Hello All,
I post this thread below several days ago discussing the strange battery behavior for stock 4.2.2
http://forum.xda-developers.com/showthread.php?t=2348174
and found many users facing the same issue.
Now I manage to find a way to fix the issue, just delete your XZDualRecovery. I believe there is something wrong during phone boot, then I delete XZDualRecovery, and the bug gone.
You can choose what to do, hope @[NUT] can fix the issue soon.
[new edit]
after a few days test, i found the battery issue is still there. so i am totally wrong, the issue has nothing to do with the recoveries. you can keep your recoveries, sorry for that. i am now thingking about rooting. i will unroot my phone and see if it works.
[new edit2]
unroot does not take effect. it seems that there is nothing we can do but wait for next update. hope it will not kill our batteries. sigh...
[new edit3]
Tips from @[NUT]
[NUT] said:
To make it clear for anyone who is experiencing this bug:
A regular reboot (using either the reboot command from terminal or by using an app to reboot) does not always trigger the bug;
It happens when your battery reaches around 20-35% and you do a battery reset (power+volup);
When you use TWRP and CWM when at or around the same battery level as they use a reboot function that works similar;
Installing the 4.1.2 binary does NOT fix the issue;
If you run your phone while experiencing the bug until you run out of juice, you risk destroying your battery!!
To charge 100% again after this bug, connect power supply when you go to sleep and keep it connected during the night. Trickle charging makes it charge to the true 100% again.
In any case, it's a bug only Sony can fix, even if it IS a bug in the kernel and @DooMLoRD might be able to fix it, you would need to unlock your bootloader to get the DooMKernel to fix it![/SIZE]
Click to expand...
Click to collapse
[new edit 4]
to be confirmed on the newest .244 fw. some says the bug is gone, while there are still reports showing the bug still exists. will update after testing.
Regards
I think CWM is fine. When I enter TWRP and flash something and return to the OS after that, it cause battery bug.
Everything is fine when I'm using CWM.
//Btw when I hardreset my phone by holding power button + volumn up, it also causes battery bug
Me too had some issues previously after updating my c6602 to v4.2.2
1)every time when I rebooting the mobile it started "Android Upgrading & Optimising Applications"
2)Misbehavior of Battery
3)Whenever I tried to open the camera there was a error message like "Unable to access Camera, Camera not found"
I had these issues even if I updated the Rom after full wife. Those were very annoying. Thank you.....thanks for you advice I simply followed that. I just replaced 'Nuts XZ Dual Recovery' with 'TWRP Recovery V2.4' Now all those issues are gone no battery misbehavior, camera is working normally again.
So definitely there are some serious bugs in Nut's Dual Recovery.... @Nut we are not blaming you. You are doing such a wonderful job in this forum and helping a lot to the newbies like me. I used your previous roms. 307&.434 in my xperia z c6602 without any issues. You are the only person in this forum releasing both c6602 & c6603 variation roms. We hope soon you will be back with your new recovery with all the bugs fixed
EDITED:"Same problems occur in TWRP recovery too after using the mobile for sometimes"
viswavj said:
Me too had some issues previously after updating my c6602 to v4.2.2
1)every time when I rebooting the mobile it started "Android Upgrading & Optimising Applications"
2)Misbehavior of Battery
3)Whenever I tried to open the camera there was a error message like "Unable to access Camera, Camera not found"
I had these issues even if I updated the Rom after full wife. Those were very annoying. Thank you.....thanks for you advice I simply followed that. I just replaced 'Nuts XZ Dual Recovery' with 'TWRP Recovery V2.4' Now all those issues are gone no battery misbehavior, camera is working normally again.
So definitely there are some serious bugs in Nut's Dual Recovery.... @Nut we are not blaming you. You are doing such a wonderful job in this forum and helping a lot to the newbies like me. I used your previous roms. 307&.434 in my xperia z c6602 without any issues. You are the only person in this forum releasing both c6602 & c6603 variation roms. We hope soon you will be back with your new recovery with all the bugs fixed
Click to expand...
Click to collapse
glad it works
Sent from my Nexus 7 using xda premium
kkd28 said:
glad it works
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
How should I do to remove Dualrecovery? ._.
Skickat från min C6603 via Tapatalk 2
I know you're not blaming me for the issue, but I'm actually scratching my head in confusion, it might be that the wrong chargemon got installed while installing XZDualRecovery but when you are actually using one of my ROM's I made sure the one by Sony remained...
My guess is that as all other packages install a 4.1.2 chargemon to make sure there still is one there the problem really IS Sony's to fix but can be fixed using the 4.1.2 chargemon in the meantime...
I'll have a try at fixing this this weekend, but it will need some testing and trying so it might take some time to figure it out...
Sent from my C6603 using xda app-developers app
ok glad found this thread ... i thought my battery was having a LEAK!! , in a bathroom i usually carry my phone to play
before i checked it was 77% , then i play 5 - 10 minutes angry bird , after finish i check now its 40%!!! WTHH
guess 4.2.2 still plenty of bugss
It can be nuts recovery, but not just his if it is. I had the original cwm installed and had the same battery issue.
Maybe it's all the recoveries.
Didn't have this issue with the old fw and recoveries installed, so technically speaking the new fw. 4.2.2 is not fully compatible with any recoveries and causes a bug like this one.
Sent from my C6603 using xda premium
Android Upgrading
I have found out the cause of "Android Upgrading" every time when I reboot the mobile. That's because of flashing "PyreX Audio v19" Before flashing this there was no issue of android upgrading. The problem occurs only after flashing the v19. Same issue doesn't occur in v18. I checked up this by flashing the v18 of PureX Audio after factory reset....still couldn't find out the cause of other issues....
For anyone having this issue, can you please confirm your chargemon (in case of no recovery) or chargemon.stock (in case of any recovery) binary sizes and md5sums?
The 4.1.2 binary size should be 62K and it's md5sum should be 9c3d979effb81a5c407c65f3a649a92f
The 4.2.2 binary size should be 82K and it's md5sum should be 9bb5cc9c9a7632dbc62935f641f24962
You can install Android Terminal Emulator and perform the following actions:
Code:
ls -lah /system/bin/chargemon[.stock]
md5sum /system/bin/chargemon[.stock]
Busybox might be needed to perform the md5sum, not sure about that.
I'm currently running the 4.1.2 binary on my phone in my final test, i had the correct 4.2.2 binary and it did what this thread describes... when rebooting with only ~25% of battery left, a reboot caused it to show a little more then 50% battery. I'm now looking at what happens when i use the old binary.
[NUT] said:
For anyone having this issue, can you please confirm your chargemon (in case of no recovery) or chargemon.stock (in case of any recovery) binary sizes and md5sums?
The 4.1.2 binary size should be 62K and it's md5sum should be 9c3d979effb81a5c407c65f3a649a92f
The 4.2.2 binary size should be 82K and it's md5sum should be 9bb5cc9c9a7632dbc62935f641f24962
You can install Android Terminal Emulator and perform the following actions:
Code:
ls -lah /system/bin/chargemon[.stock]
md5sum /system/bin/chargemon[.stock]
Busybox might be needed to perform the md5sum, not sure about that.
I'm currently running the 4.1.2 binary on my phone in my final test, i had the correct 4.2.2 binary and it did what this thread describes... when rebooting with only ~25% of battery left, a reboot caused it to show a little more then 50% battery. I'm now looking at what happens when i use the old binary.
Click to expand...
Click to collapse
Yesterday I flashed JB v4.2.2 10.3.A.0.423 India Unbranded.....so far I haven't experienced the battery issue my chargemon.stock file's size is 81.39kb & md5sum is 9bb5cc9c9a7632dbc62935f641f24962....I'll inform if I have the issue again.....
EDITED: I flashed Aroma Rom Mutator v0.12. Flashing the file was successful but there was a error message " Fixing Some Permissions Failed". I checked the chargemon.stock file after reboot now the file size is 61kb & md5sum is
9c3d979effb81a5c407c65f3a649a92f....I don't know whether this file will work or not......
--- I have
The 4.2.2 binary size is 82K and it's md5sum is 9bb5cc9c9a7632dbc62935f641f24962
and it did what this thread describes ---
Can I delete the above and replace with the 4.1.2. If so can anyone post/link the that file
Thanks
V
vayu said:
--- I have
The 4.2.2 binary size is 82K and it's md5sum is 9bb5cc9c9a7632dbc62935f641f24962
and it did what this thread describes ---
Can I delete the above and replace with the 4.1.2. If so can anyone post/link the that file
Thanks
V
Click to expand...
Click to collapse
You can use my aroma ROM mutator package in my update-to thread. Just be sure to create a backup of the one you now have before using the mutator.
Sent from my C6603 using xda app-developers app
[NUT] said:
For anyone having this issue, can you please confirm your chargemon (in case of no recovery) or chargemon.stock (in case of any recovery) binary sizes and md5sums?
The 4.1.2 binary size should be 62K and it's md5sum should be 9c3d979effb81a5c407c65f3a649a92f
The 4.2.2 binary size should be 82K and it's md5sum should be 9bb5cc9c9a7632dbc62935f641f24962
You can install Android Terminal Emulator and perform the following actions:
Code:
ls -lah /system/bin/chargemon[.stock]
md5sum /system/bin/chargemon[.stock]
Busybox might be needed to perform the md5sum, not sure about that.
I'm currently running the 4.1.2 binary on my phone in my final test, i had the correct 4.2.2 binary and it did what this thread describes... when rebooting with only ~25% of battery left, a reboot caused it to show a little more then 50% battery. I'm now looking at what happens when i use the old binary.
Click to expand...
Click to collapse
So does it work?
kkd28 said:
So does it work?
Click to expand...
Click to collapse
heh, i haven't hit 25% battery yet, so I don't know yet. will happen today though...
I need my phone for work during the day, so I can't risk it running low on battery then, but in the evening it's usually somewhere between 20% and 30% charge left, so, I'll have an answer in around 10-11 hours
Battery Bug
Today I rebooted my mobile when the battery level is 21% after rebooting it became 51%.....going to check Aroma Rom Mutator.....
I too have this annoying battery bug (along with laggy apps like album, chrome etc) ever since the 4.2.2 update. I'm on stock India rom (.423) with no custom recovery but still have this bug! The battery% shoots up (from ~30 to ~60%) after reboot, which then rapidly falls after staying idle for few minutes. This issue seems to occur only if I reboot the phone while charging it or if I try to charge after switching it off. However, no issues if I charge normally (phone switched on) & don't reboot while charging! Btw, battery backup seems slightly better than before (ignoring this bug though).
So it seems that it is a bug of v4.2.2 Rom not XZ dual recovery. Sony should fix this annoying bug soon
I can also confirm that the bug is with the 4.2.2 firmware..I am using it rite now and no Dualrecovery installed..And yet its the same issue of battery going to 50%
ethan3686 said:
I can also confirm that the bug is with the 4.2.2 firmware..I am using it rite now and no Dualrecovery installed..And yet its the same issue of battery going to 50%
Click to expand...
Click to collapse
lets see if @[NUT] can solve this problem by using 4.1.2 chargmon file.
Sent from my Nexus 7 using xda premium
I wanted to get imperial kernel v3.3 since they added a google services battery fix
Ran script wiped etc... Phone just stays on model number inital boot screen. :0 This also happened on a stock root rom i tried.
Hybridmax works great but ive got passive battery drain and its a bit outdated. With hulk i cant get wifi working Maybe if tw v2 comes out itll work!? . Kushan seems unstable.
I was hoping imperial would patch the problem yet still no changes :/
any advice?
Try this.
*Update your recovery.
*download the zip again
*flash the file
*clear cache and dalvinks.
*remove the battery and keep it away for 1 min or so.
*place the battery again and turn the phone on
Revert.
DeepankarS said:
Try this.
*Update your recovery.
*download the zip again
*flash the file
*clear cache and dalvinks.
*remove the battery and keep it away for 1 min or so.
*place the battery again and turn the phone on
Revert.
Click to expand...
Click to collapse
I tried your advice before with no results.
Im guessing if trying on a clean install of a different rom had the same problem then the issue lies in a strange place
The other rom was a stock with root :0 so im guessing king of similar to what im running now. Maybe the stock roms have some problems ?
LyQi said:
I tried your advice before with no results.
Im guessing if trying on a clean install of a different rom had the same problem then the issue lies in a strange place
The other rom was a stock with root :0 so im guessing king of similar to what im running now. Maybe the stock roms have some problems ?
Click to expand...
Click to collapse
versions 3.4 resolved the issue i hope my battery life will be as good as everyone says