Related
Dear mobile friends,
Recently i have installed NBD on my MDA vario t-mobile Aku2 phone.
I like it alot!
For the chef cook who made this wonderful recipe, A big thanks for all the effort!
I do have one little question...my battery is empty after one day
Any idea how to fix this¿
Thanks in advance.
Regards, Rogier.
mobile-eenheid said:
Dear mobile friends,
Recently i have installed NBD on my MDA vario t-mobile Aku2 phone.
I like it alot!
For the chef cook who made this wonderful recipe, A big thanks for all the effort!
I do have one little question...my battery is empty after one day
Any idea how to fix this¿
Thanks in advance.
Regards, Rogier.
Click to expand...
Click to collapse
get a different phone?
Are you saying your battery is dead 1 day after continuously having this program activated? If so, I'm amazed the battery lasted that long! How old is your device and battery? Does the battery charge o.k. when it's plugged to a charger?
Hi Hotdog,
Thanks for your reply.
My device is 1 year old and the battery drains even when the phone is inactive(battery charges just fine).
Before installing NBD, the battery lasted like 3 days (not really an active user of the phone) and now only 1 day.
Am i the only person experiencing this issue around the forums??
Device info:
ROM version 6.6.6.666 WWE
ROM date 8/23/07
RADIO version 02.19.11
Protocol version 4.1.1309
MDA Vario T-mobile AKU2 model.
Thx.
mobile-eenheid said:
Hi Hotdog,
Thanks for your reply.
My device is 1 year old and the battery drains even when the phone is inactive(battery charges just fine).
Before installing NBD, the battery lasted like 3 days (not really an active user of the phone) and now only 1 day.
Am i the only person experiencing this issue around the forums??
Device info:
ROM version 6.6.6.666 WWE
ROM date 8/23/07
RADIO version 02.19.11
Protocol version 4.1.1309
MDA Vario T-mobile AKU2 model.
Thx.
Click to expand...
Click to collapse
Ive seen many people with this problem. all I can suggest to you is, lower rom numbers on WM6 use up the battery faster. I dont know why that is but that is the trend.
Im not suggesting you go out there and get 2.69 radio rom. the higher you go the more unstable the rom is. all Im saying is, it might be the radio rom mixed with WM6. try a reflash back to wm5 and see if battery is back to 3 days.
One other thing you can try is drain the battery completely, recharge it fully, drain it a second time and recharge it fully again. sometimes when you flash the battery memory gets messed up, it's happened to me once.
elmetal said:
Ive seen many people with this problem. all I can suggest to you is, lower rom numbers on WM6 use up the battery faster. I dont know why that is but that is the trend.
Im not suggesting you go out there and get 2.69 radio rom. the higher you go the more unstable the rom is. all Im saying is, it might be the radio rom mixed with WM6. try a reflash back to wm5 and see if battery is back to 3 days.
One other thing you can try is drain the battery completely, recharge it fully, drain it a second time and recharge it fully again. sometimes when you flash the battery memory gets messed up, it's happened to me once.
Click to expand...
Click to collapse
Thanks for the reply elmetal!
That brings me to my second question,
Is there a Radio ROM out there for my T-mobile that is stable and runs smooth under NBD 8.0?
What comes after RADIO version 02.19.11? 2.69 radio rom?
I did actually flash back to the original T-mobile NL ROM (latest version)
And there the battery is functioning as expected.
(you can really tell, in the afternoon, the battery is almost at 50% with NBD)
Thank you so much for your help! really appreciated.
mobile-eenheid said:
Thanks for the reply elmetal!
That brings me to my second question,
Is there a Radio ROM out there for my T-mobile that is stable and runs smooth under NBD 8.0?
What comes after RADIO version 02.19.11? 2.69 radio rom?
I did actually flash back to the original T-mobile NL ROM (latest version)
And there the battery is functioning as expected.
(you can really tell, in the afternoon, the battery is almost at 50% with NBD)
Thank you so much for your help! really appreciated.
Click to expand...
Click to collapse
hmm.. I never focus much on tmobile users with radio problems, more cingular users. some say the 2.47 works, some say the 2.69 is flawless, I personally use the cingular 2.25.11. it's the stock cingular rom and it works fine.
Im gonna give the forum a good look for tmobile radio rom threads and ill redirect you
I suggest you try the cingular 2.25.11 (being that tmobile in the us uses a lot of cingular towers) since its really really stable.
EDIT
http://forum.xda-developers.com/showthread.php?t=314235&highlight=t+mobile+radio+rom
try that, its a decent thread on the ROM workin in the UK, Im not exactly sure where you're stationed but the point is this, there's probably an existing thread out there.
Only thing is, many different people have many different results. Updating Radio ROMs is a little dangerous for me cus the calls I receive can be very important so I try not to mess with it.
Install a new radio rom, leave your phone in standby for a few hours and test texting and calling to see if itll wake up on its own, some roms wont work well. trial and error
Goodluck!
elmetal said:
hmm.. I never focus much on tmobile users with radio problems, more cingular users. some say the 2.47 works, some say the 2.69 is flawless, I personally use the cingular 2.25.11. it's the stock cingular rom and it works fine.
Im gonna give the forum a good look for tmobile radio rom threads and ill redirect you
I suggest you try the cingular 2.25.11 (being that tmobile in the us uses a lot of cingular towers) since its really really stable.
EDIT
http://forum.xda-developers.com/showthread.php?t=314235&highlight=t+mobile+radio+rom
try that, its a decent thread on the ROM workin in the UK, Im not exactly sure where you're stationed but the point is this, there's probably an existing thread out there.
Only thing is, many different people have many different results. Updating Radio ROMs is a little dangerous for me cus the calls I receive can be very important so I try not to mess with it.
Install a new radio rom, leave your phone in standby for a few hours and test texting and calling to see if itll wake up on its own, some roms wont work well. trial and error
Goodluck!
Click to expand...
Click to collapse
Point taken
Will do some more research on Tmobile Dutch(Netherlands) Radio Roms to see if that helps.
Thanks for all the effort elmetal!
Nope it's not the Radio Rom 2.19 is the most stable and loses less energy.
The 2.69 radio Has more problems keeping the signal so it uses more energy to maintain the signal, and of course you might lose some calls here and there.
Earlier posts do indeed have the classic basic Battery drain tips.
But what about deleting the items from the Windows\StartUp folder?
Flash a fully loaded battery.
How about borowing my new battery and see if it makes a difference since my wizard is on repair.
Some users even have reported that 8.2 actually was better on the battery then 8.3.
Some believe that it might have something to do with the memory leak problem most Wizard roms have issues with. Keeping more memory reffreshed does require more power. So try to set the weather plug in to only update mannualy set the homescreen to not time out. Or try setting up the included smartskey to overclock instead of Battery status althought i don't think that battery status causes isseus.
Or do a Combo. Drain the battery recharge it perform a hard reset or clear storage. You could also try a lower pagepool rom version, nowadays you can change the pagepool without reflashing. Lower is slower but again it uses less memory. You could also use wizard registry wizard to change the font cache to lower setting and other cache settings.
My advice is to charge as less as possible as my USB connector got ****ed.
I tried the 25.11 on T-mobile network but quit using it as it either froze the ROM or could just not connect.
Or yes you could get another phone
Also make sure you change the settings of the network registry to not automaticly scanning for the network.
elmetal said:
Ive seen many people with this problem. all I can suggest to you is, lower rom numbers on WM6 use up the battery faster. I dont know why that is but that is the trend.
Im not suggesting you go out there and get 2.69 radio rom. the higher you go the more unstable the rom is. all Im saying is, it might be the radio rom mixed with WM6. try a reflash back to wm5 and see if battery is back to 3 days.
One other thing you can try is drain the battery completely, recharge it fully, drain it a second time and recharge it fully again. sometimes when you flash the battery memory gets messed up, it's happened to me once.
Click to expand...
Click to collapse
I have a MDA and I am running WM6 and using the 2.69.11 radio and I have no problems. I found that changing the task manager settings so that the program actually closes when you click x helps increase free ram and also, don't use any overclocker software such as battery status(it kills your battery and it doesnt make that much of a difference anyways...). Another thing you want to do is disable the today timeout under today settings. that tends to use more ram and thus, kills the battery faster.
See i knew i wasn't crazy about the today timeout
Thanks for the confirm.
I had the same problem with I upgraded to 8.1. Battery drain was pretty bad.. Usually getting home from work, I'd still be in the 90's with moderate texting, but with 8.1 i'd be in like the 50's. I just went back to 7.9.
The problem isn't the ROM... it's the audio manager from HTC, that sucker eats battery like I've never seen... been having this issue too, until I stoped using the audio manager and started using windows media player!
dferreira said:
The problem isn't the ROM... it's the audio manager from HTC, that sucker eats battery like I've never seen... been having this issue too, until I stoped using the audio manager and started using windows media player!
Click to expand...
Click to collapse
Same here i (as in i didn't actually notice it) but i stopped using the audio manager in favour of WMP as it gave better reactions to using the Stereo Bluetooth headset. As in Audio manager sometimes did not pick up the next and previous commands or would stop playing.
As i said i never really paid attention and i can only speculate that the battery drained faster when i did use Audiomanager.
Just goes to show that closing apps completely is always the best practice.
BTW, dferreira.
Ai's it Funny how one month after your WM5SE release people actually reacted after my post
What is your reason to use WM5 base?
WM5 is the native OS for Wizards... so, I find it to be more quick than WM6... Never gave me problems, like WM6 did. WM6 is just a face lift on WM5 so... I'm trying to make it as good as WM6 but quicker
Noonski....
You are my sunshine, my only sunshine
You make me happy when skies are gray
You'll never know dear how much I love you
Please don't take my sunshine away
Battery drain solved by flashing to NBD 8.0!!(¿)
Thanks for all the effort mobile friends!
mobile-eenheid said:
Noonski....
You are my sunshine, my only sunshine
You make me happy when skies are gray
You'll never know dear how much I love you
Please don't take my sunshine away
Battery drain solved by flashing to NBD 8.0!!(¿)
Thanks for all the effort mobile friends!
Click to expand...
Click to collapse
What build were you having a problem to begin with?
BTW you should see Alban's Touch running on 312MHZ with 12 MB Pagepool.
It Fliesszzzzzzzzzzzzzzzzzzzz.
As the title says is it possible that PRI 1.70_003 is causing the 100% awake issue on our Google Branded Sprint Hero's? It seems like the phones with 1.68_003 were fixed with the update and all of us with PRI: 1.70 are fixed for a day and then goes back to 100%.
I am on 1.70.003 and have no issues with awake time.
I'm also running PRI 1.70_003 and went all day today with occasional use & still have 76% battery on .6b fresh ROM w/ Optimization pack overlayed & Blue Pack overlayed on that... Runs & looks great! Battery life is now amazing.
Agimax said:
I'm also running PRI 1.70_003 and went all day today with occasional use & still have 76% battery on .6b fresh ROM w/ Optimization pack overlayed & Blue Pack overlayed on that... Runs & looks great! Battery life is now amazing.
Click to expand...
Click to collapse
On the Exact same with no problem to report
I had my wake time down to around the normal level, 20-40% depending after installing 0.6. I just checked for updates on and ran across this thread and thought I'd check my status. To my surprise, I am at 100% again. I also noticed my PRI is 1.68 instear of 1.70. I was under the impression that installing a rom based on the updates would do all of the updating. I did not do an OTA when it was released. Whats up?
I'm on 1.70_003 and yesterday I flashed my phone back to stock + MR + rooted + deleted Sprint apps + Optimized/zipaligned pack from elsewhere in this forum.
Roughly 24 hours later, it went from having a very low awake time to constantly climbing. I rebooted it and now I stick at 100%. Frustrating! This is the third time I've done this entire process and it keeps happening.
Glad to see I'm not alone.
BTW, I started a new thread about the problem since I'm pretty sure it's not caused by the PRI or PRL or anything like that.
http://forum.xda-developers.com/showthread.php?t=592993
What do you all think of this post I found on Androidforums:
Those with worse battery life with Fresh 2.0b
I found a solution!! If you go to settings->About Phone->Battery->Battery Use It will show what items are using your battery. For me if I tapped on Cell standby, time without a signal was at 50%. It accounted for 73% of my battery usage. (Please note that I am using flipz newest radio also)
Here's how to fix it:
Open the dialer
Dial: *#*#4636#*#*
After a second, the testing menu will show up
Tap Phone information
If you scroll down, the preferred network type was defaulted to GSM auto (PRL)
Change it to CDMA only
Time without a signal should change to 0-1%. Also note that the battery use menu is only updated after unplugging the phone from the charger.
Makes sense. Will try it! Thanks!
I am running damagecontrol, and it was already set correctly to CDMA...figured I would just put this out there.
Let me change that...it says "CDMA auto (PRL)"
Wasney said:
I am running damagecontrol, and it was already set correctly to CDMA...figured I would just put this out there.
Click to expand...
Click to collapse
Wasney, what is your time without a signal percent?
noticed 50% without signal with damagecontrol also. just changed to cdma only.
I'll let you know in about 12 hrs what happend!
rjj1976 said:
Wasney, what is your time without a signal percent?
Click to expand...
Click to collapse
That isn't even listed for me...But then again I reset my phone this morning, an have been in good signal all day.
mine was at 50% with damageless rom. it was set to CDMA auto (PRL) but i changed it to CDMA only and will see what the result is.... just plugged it in and unplugged it to reset the battery stats....
I've noticed 50-56% as well, Damageless1.0 and it is set properly to CDMA auto (PRL).
ill run the CDMA only on my end
so far so good! I'm on DamageControl v1 set it to cdma only and my battery usage to cell has dropped to 28%! i'll update again later.
Good info......
without Auto PRL, wouldn't we not get the latest and most updated cell tower frequencies? i mean for home locations i guess it what wouldn't really matter, but what about in areas without sprint coverage? how would it know which network to roam on?
ajaholic said:
without Auto PRL, wouldn't we not get the latest and most updated cell tower frequencies? i mean for home locations i guess it what wouldn't really matter, but what about in areas without sprint coverage? how would it know which network to roam on?
Click to expand...
Click to collapse
Yeah I would assume this would be the case, but that bat increase is pretty decent. I am going to enable it and use it for a day or so around the city.
update: Noticed after a couple reboots my connected time was back up to 50%... I never left my house and i have good coverage here. What gives?
So is this worth doing?
PRGUY85 said:
So is this worth doing?
Click to expand...
Click to collapse
not yet. i mean, make sure you're not set for GSM but CDMA Only isn't helping me -- still always at 50%. Weird.
Probably a radio bug in this firmware
feld said:
not yet. i mean, make sure you're not set for GSM but CDMA Only isn't helping me -- still always at 50%. Weird.
Probably a radio bug in this firmware
Click to expand...
Click to collapse
Are you using Flips' Radio file?
So currently mine says CDMA auto (PRL)....I guess I should leave it at that then.
PRGUY85 said:
Are you using Flips' Radio file?
Click to expand...
Click to collapse
I'm not aware of a Flips radio file? Was this something hidden in that giant Damagecontrol thread?
edit: found it and flashed the radio. Will have to wait to see if this makes any difference. Currently on the suggested "CDMA Only" from this thread.
http://geekfor.me/downloads/radio-241040203/
I'm not notcing any diferent in connect percentage. Still at 50% as others have stated. Battery life seems the same too.
Does anyone else notice that the first day after flashing a rom, the battery life is great? Then the next day it's back to normal. This happens to me with every single rom I upgrade to. Just an observation.
I thought I'd start a thread detailing my successful experience installing Doc's Froyo rom with the few snags I met along the way, and see if anyone had similar experiences they were able to fix.
I'd been running JH2 for a few months without any major issues, but wanted Adobe Air support so I figured I'd bite the bullet and update. I followed the steps below:
- Backed everything up (nandroid and Titanium, just in case)
- Cleared caches via CWM
- Didn't do a factory reset because I was feeling brazen
- Used CWM to flash rom
- Rebooted as the instructions told me to, set up the various tweaks and voodoo kernel
- Installed the Swype pack
- Applied the application packs
The applications wouldn't install unless I dropped out of CWM to 2e and flashed them as an update.zip, which was odd but worked once I tried it that way.
So far, two days later, my phone has been stable and responsive with no FC issues. Incoming and outgoing calls work well, all of the data from my apps was where it needed to be and I've not experienced any market issues; all-in-all, it's a great experience. A few minor (I'm assuming) problems below:
- I've noticed that when the screen is on, the phone runs MUCH warmer than it used to. About the same temperature as it gets when I'm making a call and the signal is quite low.
- The battery life seems to be directly related to the temperature, if the phone is asleep, it appears to give me the same amount of drain overnight as my previous JH2 system. If I use the phone with the screen on, however, I lose approximately 13% per hour with nothing running other than gmail in the background, handcent, and an offline card game.
My next steps will be to test various lag-fixes included to see if the temperature and battery problems persist, but as long as they're not affecting anything (e.g. won't kill my internal / external SD) I can comfortably say I'm still very happy with the upgrade. In the meantime, if anyone has any information they'd like to share that might help out, I'd be very appreciative!
*a couple hours later*
I disabled the lag fix and have had the phone running a 20 minute video on YouTube over the HSPA connection after sitting with the screen on (min brightness) for a half hour. The results: the phone is barely warm to the touch and the battery has only dropped a few percent. That would lead me to believe that the problems were almost certainly based on the lag fix I had applied in the modified CWM included with Doc's rom. I'm going to mess around a bit more to see if I can verify this for certain, but I thought I'd update this post in the meantime.
My phone is very warm with this setup as well.
Further Investigating Reveals...
The lag fix really does appear to be the culprit for both the temperature and battery life problems I was having. I left my phone doing various things and took some notes:
5:11pm - Batt: 39% - Started Quake 2 and left it running with sound on
5:21pm - Batt: 35% - Quit Quake 2 and left the phone running with google talk, screen on
6:00pm - Batt: 28% - Screen still on, various apps running here and there, a bit of youtube
7:00pm - Batt: 19% - Turned screen off, left google talk running, received a few texts and gtalk messages
7:41pm - Batt: 18% - Screen still off, more messages
8:03pm - Batt: 16% - Standby, still...
8:35pm - Batt: 15% - Still on standby, few more texts
10:45pm - Batt: 9% - Standby, texts, just going to let it die completely at this point
Throughout all of that, I checked the temperature on the phone by touching the back of the case and the screen. With the lag-fix enabled, they were both quite hot just playing a card game, but this time running quake and streaming video left the screen cool to the touch and the back never got more than slightly warm.
So that's where I am right now, I'm going to try some of the other lag-fixes tomorrow when I have some time.
I just recently changed to docs rom and checking out which lagfix will give me the performance I want but the battery life I can use. Going oclf to jfs to ext 4 over the next few days with no other changes. We will see
Sent from my GT-I9000 using XDA App
jpo or jpa? what modem?
striker456 said:
jpo or jpa? what modem?
Click to expand...
Click to collapse
Sorry, completely forgot to post that. JPO with the JPE modem (installed from the JPD update package in Doc's post)
Try Doc's JP6 V6 Rom.. the battery life on it is great... the new version 7.6.2 my battery life is not that good its likely the radio causing the issue. if you clear your battery stats files you do get better battery life. also when you clear your battery stats make sure you do it when the phone is at 100%
I flashed the latest doc rom. Lost 850 band and even though it's selected in the 0011 menu it never switches to out anymore. Other than that minor bugs but very quick.
Sent from my GT-I9000 using XDA App
Felixpau86 said:
I flashed the latest doc rom. Lost 850 band and even though it's selected in the 0011 menu it never switches to out anymore. Other than that minor bugs but very quick.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
There is a topic in the general section that will help you restore your 850 band just look for bell 850 in search terms.
Sent from my GT-I9000 using XDA App
what are you guys using to root? just want to make sure there isn't a special method for the 9000m
striker456 said:
what are you guys using to root? just want to make sure there isn't a special method for the 9000m
Click to expand...
Click to collapse
Doc's ROM and other come pre-rooted
Mortify1 said:
Doc's ROM and other come pre-rooted
Click to expand...
Click to collapse
i wanted to back up my /efs folder via adb as per doc's instructions. maybe i am confused by the instructions, but do i need to be rooted to
Code:
su
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
Click to expand...
Click to collapse
PrinceOD said:
Sorry, completely forgot to post that. JPO with the JPE modem (installed from the JPD update package in Doc's post)
Click to expand...
Click to collapse
What made you use the JPD update package modem?
TriC_101 said:
What made you use the JPD update package modem?
Click to expand...
Click to collapse
The reports of better battery life on that one in the (very extensive) thread on Doc's rom. I noticed it was hot nearly immediately after booting up, so that was one of the first things I did which means I can't really say whether or not it was worthwhile.
The battery life while I'm using this build isn't great, and I noticed yesterday the phone was certainly running warmer with the screen on than normal. My data speeds also seem relatively slow, about half of what I was used to before, but that could just be where I was in the house when I ran Speed Test.
Still 80% happy, though, and am able to work on some app development in Adobe Air, which was my main motivation for 2.2
I installed 7.6.2 last night, had some problems getting SWYPE installed but mostly because I didn't realize I needed to use 2e to get it to work.
Lost 850 band but using the COMBI menu I was able to re-add it and it seems okay now. I installed a different icon pack so I'm probably not used to how it looks now, signal sort of seems lower but maybe just my perception.
Battery life seems a little lower but I haven't used the phone enough to know for sure and I'm using a round battery indicator with numbers which is a lot more accurate than the crappy indicator that comes with the default stock rom.
My biggest issue now is that I can't take incoming calls. The phone app FCs and I don't know how to fix it. It was suggested I copy my /efs backup overtop of what exists on the device now but I can't see how that will make any difference.
I installed JPA (instead of JPO) but I'm not sure that matters much.
If copying over /efs makes no difference I may be forced to do a factory reset and try again, which I'm not thrilled about since the phone is so close to being 100% functional. I guess if I HAVE to try again I'll try JPO instead.
pr0cs said:
I installed 7.6.2 last night, had some problems getting SWYPE installed but mostly because I didn't realize I needed to use 2e to get it to work.
Lost 850 band but using the COMBI menu I was able to re-add it and it seems okay now. I installed a different icon pack so I'm probably not used to how it looks now, signal sort of seems lower but maybe just my perception.
Battery life seems a little lower but I haven't used the phone enough to know for sure and I'm using a round battery indicator with numbers which is a lot more accurate than the crappy indicator that comes with the default stock rom.
My biggest issue now is that I can't take incoming calls. The phone app FCs and I don't know how to fix it. It was suggested I copy my /efs backup overtop of what exists on the device now but I can't see how that will make any difference.
I installed JPA (instead of JPO) but I'm not sure that matters much.
If copying over /efs makes no difference I may be forced to do a factory reset and try again, which I'm not thrilled about since the phone is so close to being 100% functional. I guess if I HAVE to try again I'll try JPO instead.
Click to expand...
Click to collapse
I have read that a factory reset from FroYo can brick your phone, I'd avoid that. Did you try clearing all of the caches from the clockwork recovery menu? I recall reading somewhere that would fix the FC on incoming calls issue.
Did any of you sucessfully flashed a bunch of times and had no sd corruption on i9000m ?
I bricked 2 phones already... Froyo was working fine for 1 week then, one morning black screen
PrinceOD said:
I have read that a factory reset from FroYo can brick your phone, I'd avoid that. Did you try clearing all of the caches from the clockwork recovery menu? I recall reading somewhere that would fix the FC on incoming calls issue.
Click to expand...
Click to collapse
No dice, launched into CWR, cleared the cache and dalvik cache, fixed the permissions, then rebooted, took forever and still get FC when the phone rings.
It feels like some sort of software issue so the other hint I got about copying back the backup of /efs seems like a red herring to me. At this point I'm at a loss. The ROM seems pretty decent (I don't know if I agree with a lot of the hype around it) but without incoming calls it's pointless.
Lightarrow said:
Did any of you sucessfully flashed a bunch of times and had no sd corruption on i9000m ?
I bricked 2 phones already... Froyo was working fine for 1 week then, one morning black screen
Click to expand...
Click to collapse
I have flashed my phone about 20 times since Aug... not issues here.
flashed 7.6.2 today. seems to be working great. snappy. no lagfixes applied.
i see the he just released v8, but didn't want to try it so soon after release.
edit: phone was fine and then everything was FC'ing. I restarted it and now I loop the boot screen. still have cwm, so i will start fooling around with it tomorrow.
edit2: flashed with odin back to jh2. seems to be okay.
Hello everyone I hope I got the right forum
I have a problem with the new system update released
The new update did not help at all to my nexus
I ran out of battery really fast, before the update it was fine
Battery had stayed a long time
What should I do?
1headshot said:
Hello everyone I hope I got the right forum
I have a problem with the new system update released
The new update did not help at all to my nexus
I ran out of battery really fast, before the update it was fine
Battery had stayed a long time
What should I do?
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=2385843
To get battery like this:
http://forum.xda-developers.com/showpost.php?p=44364085&postcount=5089
:cyclops:
Galaxo60 said:
Read this:
http://forum.xda-developers.com/showthread.php?t=2385843
To get battery like this:
http://forum.xda-developers.com/showpost.php?p=44364085&postcount=5089
:cyclops:
Click to expand...
Click to collapse
A quick look through that thread shows that it is focused on problems relating to Google Services. Since the update, I too am having issues with the battery draining more quickly than it ever did before. However, it appears to be msm_hsic_host wakelock causing the problem. Google services are a very small part of my battery usage.
I have posted a couple times about it in various threads, but I haven't seen a fix that applies to 4.3.
The battery drain is out of hand. I love my N4, but this is a big turn off for me.
I have tried these configurations to make sure it wasn't an oddball app causing the problem -
Stock 4.3 with stock Kernel - no root/stock recovery - Only apps being the ones that load on a factory reset
Wiped all partitions and reloaded stock 4.3/gapps/no root/stock recovery
Stock 4.3/rooted/TWRP/Stock gapps
Stock 4.3/rooted/TWRP/gapps+ a handful of other apps (photobucket/es file explorer/bbs - essentially, my normal config)
Added note - I also have cell broadcasts of all types turned off.
All of the above combinations respond the same way in regard to battery drain overnight. 7-9 hours off the charger/no screen time nets me 25-30% loss of battery from a full charge. msm_hsic shows up in BBS with 1.75 to 2.5 hours of wake time and is the highest power consumer. Putting the phone in flight mode reduces power consumption to ~2% over the same 7-9 hour timeframe. Just turning wifi off doesn't change anything.
Ideas anyone?
Calebz said:
A quick look through that thread shows that it is focused on problems relating to Google Services. Since the update, I too am having issues with the battery draining more quickly than it ever did before. However, it appears to be msm_hsic_host wakelock causing the problem. Google services are a very small part of my battery usage.
I have posted a couple times about it in various threads, but I haven't seen a fix that applies to 4.3.
The battery drain is out of hand. I love my N4, but this is a big turn off for me.
I have tried these configurations to make sure it wasn't an oddball app causing the problem -
Stock 4.3 with stock Kernel - no root/stock recovery - Only apps being the ones that load on a factory reset
Wiped all partitions and reloaded stock 4.3/gapps/no root/stock recovery
Stock 4.3/rooted/TWRP/Stock gapps
Stock 4.3/rooted/TWRP/gapps+ a handful of other apps (photobucket/es file explorer/bbs - essentially, my normal config)
Added note - I also have cell broadcasts of all types turned off.
All of the above combinations respond the same way in regard to battery drain overnight. 7-9 hours off the charger/no screen time nets me 25-30% loss of battery from a full charge. msm_hsic shows up in BBS with 1.75 to 2.5 hours of wake time and is the highest power consumer. Putting the phone in flight mode reduces power consumption to ~2% over the same 7-9 hour timeframe. Just turning wifi off doesn't change anything.
Ideas anyone?
Click to expand...
Click to collapse
As far as I know, this wakelock is caused because of the usage of 3G, like browsing, syncing, or any other thing that consumes data. This drain for me is usually between 10%-15%. There is no way t completely get rid of it, because it is part of the Android system.
There are many kernels that tried to fix this, about stock image and JW branch I don´t know, but maybe you should try to install an AOSP variant, because AOSP has many bugs fixed.
Also I remember I read somewhere that also bad radio could be causing this kind of issues, so try to get latest radio/bootloader for 4.3.
Hope it helps.
:highfive:
Galaxo60 said:
As far as I know, this wakelock is caused because of the usage of 3G, like browsing, syncing, or any other thing that consumes data. This drain for me is usually between 10%-15%. There is no way t completely get rid of it, because it is part of the Android system.
There are many kernels that tried to fix this, about stock image and JW branch I don´t know, but maybe you should try to install an AOSP variant, because AOSP has many bugs fixed.
Also I remember I read somewhere that also bad radio could be causing this kind of issues, so try to get latest radio/bootloader for 4.3.
Hope it helps.
:highfive:
Click to expand...
Click to collapse
To avoid having loose ends out there (in case anyone finds this thread during a search) - The problem turned out to be the latest radio. Not my lack of it :lol:
After flashing back to the .48 radio, from the .84 radio - everything is back to normal. No more weird Android OS wakelocks. ~3-4% battery drain overnight instead of 20-30%
There are more and more people popping up on XDA with this problem. So far, all of them that I have seen are outside the US. A few have even discovered the same fix.
So - future person that finds this thread during a search, look into the possibility of flashing back to version .48 of the radio. Hopefully this saves someone the trouble of experimenting with a bunch of different ROMs and kernels.
Calebz said:
To avoid having loose ends out there (in case anyone finds this thread during a search) - The problem turned out to be the latest radio. Not my lack of it :lol:
After flashing back to the .48 radio, from the .84 radio - everything is back to normal. No more weird Android OS wakelocks. ~3-4% battery drain overnight instead of 20-30%
There are more and more people popping up on XDA with this problem. So far, all of them that I have seen are outside the US. A few have even discovered the same fix.
So - future person that finds this thread during a search, look into the possibility of flashing back to version .48 of the radio. Hopefully this saves someone the trouble of experimenting with a bunch of different ROMs and kernels.
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: