Database Users

Fix battery drain on arc 4.0.4 (new way)

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

N4 upgrade failed

Help me XDA, you're my only hope...
First, background: I bought my Nexus 4 over the internet, because it was never officially released in Belgium. I had to have the screen replaced, and let a 3rth party do it. Glass damage isn't covered by the warranty and it would mean sending my phone by international mail if i used the official warranty people. They told me that the also had to replace the proximity sensor.
My phone worked perfectly afterwards. Until I tried to install the automatic upgrade to 4.3.
First it stopped at the X-logo screen and became very hot. I contacted play support and did all the things they advised (including a factory reset, rebooting in safe mode), none of it works. I found someone with the same problem who managed to get past the X-screen by flashing back the 4.2.2 radio version. And that worked: the phone booted and the update started.
However, since that moment I got a lot of problems:
- random shutdowns
- random locking of the SIM card
- phone not starting unless plugged in charger.
Worst of all, reflashing stock images for 4.2 and 4.2.2 or AOKP does nothing to solve these problems. I also tried a new SIM card, and still nothing.
I'm at my wit's end now. Could there be a driver issue? Any other things I can try?
TIA

Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Click to expand...
Click to collapse
any suggestions for a good kernel that can run stock android?

If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.

BobWalker said:
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
Click to expand...
Click to collapse
Well, I tried again. (For the 6th time this month) No different as before: it's been stuck on the X screen for 20 minutes now and getting warmer.
EDIT: I finally managed to get into the recovery menu. No idea why it wouldn't let me use volume up + power...

As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?

Joenr76 said:
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Click to expand...
Click to collapse
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Click to expand...
Click to collapse
I never did that before: do I flash the kernel first or the Rom first? Are there any guides?
EDIT: I just read that Paranoid Android comes with the halfbreed kernel included. Is that the one you linked too?

Before jumping into the kernel thing (also because i wanted to be able to work with a device that can actually boot), I reinstalled the 4.2.2 factory image. It took about 5 minutes for the first shutdown to happen. *sigh*
And without plugging it in, it goes into a boot loop (going to x screen for a while, then restarting.) When I plug it in, it starts immediately, but shows the battery as empty. It was 63% when it shut itself down.
It's a clean install, I just don't understand...

Okay so, I'm assuming you have a custom recovery like TWRP. Open it and flash the newest boot loader and radio. Then flash Paranoid Android and GApps. Then try flashing Faux kernel and clearing cache/dalvik. If you still have problems, then I have no idea
Sent from my Nexus 4 using xda premium

Open up your phone to see the battery is securely checked and to see if all the components are okay. Then look do a full wipe of cache,dalvik,system,data,and sd (internal storage). Then use wugs toolkit to a upgrade on a clean flash. Double check to make sure you wipe everything!
Sent from my Nexus 4 using Tapatalk 4

TheNerd:] said:
Open up your phone to see the battery is securely checked and to see if all the components are okay.
Click to expand...
Click to collapse
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...

Joenr76 said:
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Click to expand...
Click to collapse
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.

tykate said:
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
Click to expand...
Click to collapse
Tried that before. I did some research and I guess this is relevant: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/ Especially since I ordered my Nexus from the Netherlands.
I'll have to wait until that bug gets fixed until I can upgrade my radio.

[Q] Failed OTA update help?

I just got the OTA update to Android 4.4, and being eager to get it installed, hit the install button right away. I told a few people I was going to be a few minutes while installing the update... and tapped the button.
That was three hours ago, roughly.
I'm on a rooted nexus 4 with CWM Touch edition installed as a recovery. I don't know exactly what version right now but it was the latest when I installed it a few months ago.
The install launched CWM, and I waited as the loading bar filled. Right at the end it gave an error message - in a panic I didn't take note of what it was, hit the onscreen buttons and went through a window telling me I might have lost SU permissions - which I told it to fix. The startup animation (with four dots, the new 4.4 animation I guess?) started... and continued for more than five minutes.
I was still panicking and instantly launched back into CWM, downloaded a (I think correct, checked it multiple times, as on does...) update zip from the web, and flashed it via adb sideload. This gave me an "Error 7" and a failed install. I tried again, same result. Then gave up and hit the restart button in the hope that one of the attempts had indeed worked...
I now have a Nexus 4 sitting on my desk playing a nice dotty animation, and it's been doing that for fifteen minutes as of now. I'm intending to leave it as such hoping that it will actually turn on and it's just having a very long boot.
So, the question. Anyone have any ideas how to save my Nexus?
I'd rather like to end up with the data on the device intact (stupidly did not back up before installing and can't get any files off it until an install works) and possibly with Android KitKat running on it, as was the original aim of tonight, but if neither are possible, I'd at least like to end up with a functioning phone... just with any stock rom.
Thanks in advance.
P.S. I'm not new to flashing ROMs manually - my last phone was a ZTE Blade which never ran any ROM well, so I must have flashed on that phone at least ten times, including via ADB.

Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD

totally-not-me said:
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
Click to expand...
Click to collapse
Your post saved me from a complete wipe and reinstall, so thank you for sharing your fix. I had a very similar issue but my Status 7 appeared to be because of my previous root and the new install not being able change the permissions on some /system files.
Now I just need to re-enable root via the NRT.

at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk

dethrat said:
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.

I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.

thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
Not blaming you xda has almost become useless in terms of finding real info in the past week. Bombardment of repeated posts about 4.4
Sent from my Nexus 4 using Tapatalk

Lokitez said:
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
Click to expand...
Click to collapse
Sideloading is only for flashable zip packages, not official factory images that required using fastboot. Use the guide links in my signature for instruction to flash factory image.
Or you can use sideload to flash flashable stock roms: http://forum.xda-developers.com/showthread.php?t=2527806
Unless your wife is really into flashing, I suggest just leaving it everything stock.

thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user

RickyBO89 said:
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
Click to expand...
Click to collapse
It will softbrick the device, or atleast fail. I don't even have to try CWM, but with TWRP, if I make any changes to the /system partition it failed. I suggest you just flash a stock 4.4 rom: http://forum.xda-developers.com/showthread.php?t=2010887

Any one updated their nexus 4 to 4.4.3 yet? any issues?

So far I found out that if you flash Franco's kernel you will break WiFi. Any other I should know?

Fuzzy Taco said:
So far I found out that if you flash Franco's kernel you will break WiFi. Any other I should know?
Click to expand...
Click to collapse
For now i suggest stick to stock ! or else mod your stock 4.4.3 kernel using Dsixda's Android Kitchen....
or else wait for developers to upload new kernels !
otherwise no issues, performance got a bit low n battery life got better

I just did, via fasboot from Google's image. I don't have a working wi-fi now... Logged on 3G, but then automatic restore starts downloading apps which is not cool on my 3G. Also my N4 is not seen as 8GB, which is not a biggie, has happened before.

Nope, didn't work. Can't figure out why.
So I downloaded the factory image, unzipped it as I always used to, then run the "flash-all.bat" script. And I get this message:
error: cannot open radio-<rest of file name>
The same goes for all files except for the bootloader.
Bootloader is unlocked, was running stock until recently, then used CM for a while, now trying desperately (and in vain) to go back to stock.
Any help would be appreciated. No amount of searching seems to be taking me anywhere.
(Before you ask: I verified MD5 to make sure the file wasn't corrupted; there was no issue on that end.)

kittuboy said:
So I downloaded the factory image, unzipped it as I always used to, then run the "flash-all.bat" script. And I get this message:
error: cannot open radio-<rest of file name>
The same goes for all files except for the bootloader.
Bootloader is unlocked, was running stock until recently, then used CM for a while, now trying desperately (and in vain) to go back to stock.
Any help would be appreciated. No amount of searching seems to be taking me anywhere.
(Before you ask: I verified MD5 to make sure the file wasn't corrupted; there was no issue on that end.)
Click to expand...
Click to collapse
before running the *.bat file, you need to do two things to avoid a complete (including your SDCard) wipe.
1. edit the *.bat file with notepad and then delete the "-w" in the last line. This will prevent a fill wipe.
2. cd into the directory where the factory image and *.bat files are located, THEN run the script - this is why your terminal can't find the files to flash.
Hope this helps.

rickbosch said:
before running the *.bat file, you need to do two things to avoid a complete (including your SDCard) wipe.
1. edit the *.bat file with notepad and then delete the "-w" in the last line. This will prevent a fill wipe.
2. cd into the directory where the factory image and *.bat files are located, THEN run the script - this is why your terminal can't find the files to flash.
Hope this helps.
Click to expand...
Click to collapse
The SD card wipe is the least of my worries I have a full backup, so that's fine. Right now I'm trying to get my phone to boot up fully!
I edited the bat file to reflect the correct path. (Put shortcuts to the original adb and fastboot in the folder with the factory images, replace path in bat file and replace fastboot with "fastboot.lnk")
My strong doubt is that there is some issue with the phone. Will try a toolkit and let you know what happens.
UPDATE:
This is seriously good. I used Wug's NR and some fiddling later, all was well. I still suspect the phone, but ehhh.... 4.4.3. Cheers!

kittuboy said:
The SD card wipe is the least of my worries I have a full backup, so that's fine. Right now I'm trying to get my phone to boot up fully!
I edited the bat file to reflect the correct path. (Put shortcuts to the original adb and fastboot in the folder with the factory images, replace path in bat file and replace fastboot with "fastboot.lnk")
My strong doubt is that there is some issue with the phone. Will try a toolkit and let you know what happens.
Click to expand...
Click to collapse
Cool, but that's a very long way to do it. Just hold shift and right click in the folder where the file is "open command window here" and run the *.bat file. No editing or anything needed.

That's why I never use the bat. Just extract and flash all partitions via fastboot.
Sent from my Nexus 4 using XDA Free mobile app

rickbosch: Er, I should probably explain. My adb and fastboot programs (the entire sdk in fact) are deep inside one drive (the G: drive to be precise. Yes. Stop s******ing.) while the factory image is in the C: drive. So just opening a command prompt in the sdk folder will require me to navigate through to the download folder, and vice versa. So I changed the path in the bat, placed shortcuts in the folder and renamed commands to <command>.lnk. And that was all it took. (It's actually much quicker when done )
oxious119: Fastboot kept bawling that it was unable to flash the radio file. That was why I posted here in the first place. I was eventually forced to use a toolkit (Wug's NRT in case you want to know) and thankfully that solved it for me.
What happened was that I had flashed CM, then I could still go into bootloader and recovery modes. I made the mistake of relocking and unlocking the bootloader. This stopped the phone from booting completely. To make matters worse, for some reason, I was unable to flash the radio (though it was perfectly fine) The toolkit, much as I hate to admit it, did what I could not: it got my phone working. May the heavens praise Wug.

My notification led stop working after flash stock 4.4.3 on my nexus 4. I did a clean install, wiping everything 2 times and no success.
I rollback to 4.4.2 and the led is working again.

My N4 reboots while using camera, did clean flash of factory image an factory reset.

Matr1x kernel issue
Matr1x kernel was the best battery saving kernel I've used. It worked excellent till 4.4.2, but now, after updating to stock 4.4.3, wifi breaks down! Doesn't connect at all! Now running on stock kernel and the battery life has again gone to worse! I wish they'd update soon! Waiting for them to release an update!!!

thawfu said:
Matr1x kernel was the best battery saving kernel I've used. It worked excellent till 4.4.2, but now, after updating to stock 4.4.3, wifi breaks down! Doesn't connect at all! Now running on stock kernel and the battery life has again gone to worse! I wish they'd update soon! Waiting for them to release an update!!!
Click to expand...
Click to collapse
Try THIS, should work for Matr1x too.
Tapatalked from my N4

***Some Problems Still Persist***
I flashed the factory image of 4.4.3 available on Google site on my Nexus 4 and to my huge disappointment the battery drain issue was still there and the phone would shutdown when the battery level would reach below 60%
I was on stock 4.4.2 before I updated.
PS : If anyone out here got a fix to this, please tell me.

I've updated my N4 to 4.4.3, and my Galaxy On Fire 2 HD saves won't load I've baked up them via Titanium Backup PRo, but after restore, when I'm trying to load my game it says "an error occured. please try again later"... and I'm afraid I've lost 30h of gameplay :/

valkyrjur said:
My notification led stop working after flash stock 4.4.3 on my nexus 4. I did a clean install, wiping everything 2 times and no success.
I rollback to 4.4.2 and the led is working again.
Click to expand...
Click to collapse
Working again.

@meatboy371, thank you, thank you, thank you ... It worked ...
Sent from my Nexus 4 using XDA Premium 4 mobile app

Hybrid radio
Anyone know if there's a new hybrid LTE radio for this?

jbounds3 said:
Anyone know if there's a new hybrid LTE radio for this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/ref-mako-hybrid-modem-collection-v2-t2412052

I updated a few days ago and flashed fanco kernel #209 and everything seems to be working good! :laugh:

Battery life & kernel ambasadi rom i9505

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