Develop Bugs

[Q] Battery drain: mystery network usage?

I'm running CM6.1 RC2, and the past couple of days I have experienced excessive drain, mainly in the first 50%. I attached a picture of the issue. I went to spare parts battery history to see the network usage, since in the about phone battery usage cell standby was 84% of the battery usage, and under network usage there was just an entry for 0, using the most network. When I clicked on '0' the settings application crashed. Yesterday it dropped 35% in 2.5 hours, before it slowed down. It was ridiculous, never used to have this problem, and the battery is only a couple of weeks old so it has to be software. Today it is at 53% after 7.5 hours, which is pretty decent, but at around 70% I disabled 3g and background data to save some energy for a few hours. Is there any way of figuring out what is causing this, or should I reflash? Could it be a CM6.1 RC2 bug? Anyone else having this issue? Thanks in advance
BTW I have no idea why the dialer was so high in usage I only had like MAYBE 15 minutes total of voice calls in 2 hours. The 0 is what I'm concerned about.

Anyone? Bump? No one else is having the issue? Still happening to me on RC3.

I've been getting that problem too.
I used to have battery life of up to 4 days (Mostly standby), now I'm lucky if I get 1.5 (Same usage).
I went in to spare parts and it crashed for me too.

Battery drain here too since cm 6.1
Sent from my T-Mobile myTouch 3G Slide using XDA App

Well '0' is he system's ID, 0 is root. In the graph the blue is bytes sent, red is bytes received. Have you checked other usage like CPU usage? That might be a better indicator of what's using your battery. Then from there you can start to narrow it down to a specific process or app. I'm using the latest nightly and don't have that issue, never have. I use a bit more battery than I think I should but nothing crazy.
Do you have wifi or bluetooth on? Those drain your battery like no other.

I havent used wifi at all today, unplugged at around 6:30, it's 3:45 now and I'm at 63%, but from around 9:50 to 11:45 and then from 12:20 to 2:20 I had airplane mode enabled since the time without a signal was at 70%, very low signal area. So it seems like for only 4 hours or maybe 5~ of non airplane mode time I should be at above 63%. I only had wifi on for a half an hour today. I'm considering going back to stock for a few days just to see the battery life comparison, and then nandroiding back to CM6.1. I always end up going back to AOSP-based roms in the end. I don't have a data plan on my phone at the moment, getting it today I'm pretty sure, so could all of the blue be from the phone continuously trying to access a website? But other people said they have the same issue and I'm assuming that they have data plans, so that can't be too much related. Hmm.
I also checked cpu usage and such like you suggested, there were a lot of things listed but all but two of them were too small to even have a bar. The two that did have a bar visible were minuscule to put it lightly, so that can't be an issue. Battery use in the about phone area always has cell standby at the top, normally between 40 and 80%. It would seem like there is way too much cell communication going on, moreso than normal. Cell standby stays at the top in even high signal areas, so it's not the signal levels. Kind of stumped here.

Well if the cell is in standby then it's linked to a tower and awaiting activity. Every now and then it 'checks in'. If it's doing that too often then that could seriously drain the battery. You're right though, I'd just switch back. Trouble shooting the exact issue wouldn't be worth the time. Maybe try flashing it again later, could have just been a corrupt download that didn't flash properly.

After conditioning my battery religiously (full to empty with every charge cycle) I am back up to about 15 to 16 hours from full battery to system shut down which is way better than the 10-12 hours I was getting when I first loaded RC2. CR_OTA ROM gave me up to 24-30 hours off of one charge with the exact CPU/2g/3g/wi-fi "routine" as I am using with RC2. Tracked battery usage with System Panel app and RC2 has a steady and even drain pattern ... an even diagonal line down the graph (100% to 0%). Cell standby uses a ridiculous 40% of the battery from full charge! On the stock ROM System Panel app shows plateaus throughout the day when the phone screen is off/sleeping where battery use is virtually non-existent. I'm going to load RC3 today and track the cell standby and battery usage. This time I am not going to use setCPU and just let the ROM run as the CM team designed it to be used and see if anything has changed. I tried this with RC2 and the battery still trended absolutely evenly from 100% to 0%. I can live with a 16 hour battery cycle for the CM ROM because it is very smooth and never has a glitch. The stock ROM is smooth as well but it has some buggy behaviors that I just cannot stand for and it does not run the latest GAPPS.

I've noticed i have exacly the same problem(was actually gonna post it when i found this thread)
Needless to say that on eclair my battery lasted ~48 hours constantly, not its drained in max 24...

The highest I have EVER gotten was 24 hours, and that was on a cm6.1 nightly build, pre RC2. I loaded cr_mod and experienced a HUGE drain. I had airplane mode on, just to test, and it dropped 7% in an hour, in AIRPLANE mode, with no screen on time. I went into spare parts and looked at the usage, and sure enough, "running" was at the top, with 99% of the time spent without sleeping. This has never happened before though, so I can probably attribute that to my modifications. I deleted a few apk's and de-odexed it before I flashed it, and I have a feeling something I did corrupted something else, so I'll flash plain old cr_mod and see where that leaves me. I should probably get back into the habit of full charge/drain every cycle. I used to do that until my battery started lasting longer than I was awake for, so I always had to plug it in at around 15 to 30%. I'll run some more "trials" and see what's going on.
Also, on an unrelated note, I love the stock rom, I always love the sense UI, but I hate HTC_IME compared to the froyo Latin_IME, is there any way at all I could port the froyo Latin_IME to the eclair stock rom?
Edit: also, I flashed dumfuq's OC kernel over cr_mod, could that have been the culprit to the battery drain?

Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?

KCRic said:
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
Click to expand...
Click to collapse
Actually, by process of elimination, the kernel was the issue. I remember hearing about there being a bug in the older dumfuq kernels with something idle being null, I really don't remember but it had something to do with sleeping. I flashed pure CR_mod and then 3.5 dumfuq and I experienced the same issue where it wouldn't sleep. I flashed 4.0, but I think it's too soon to determine whether or not the same issue with sleep is occurring.
I tried doing what you said with LatinIME.apk, I even imported the lib file from /system/lib on CM6.1, but the it was nowhere to be found in the system when I booted. It wasn't under keyboard settings, and HTC_IME was gone. I figured it was an incompatibility between froyo and eclair, since the stock sense rom is eclair and the LatinIME.apk is from a froyo ROM. Do I have to something more than just adb push the apk and lib file? I also tried installing it with a file manager, and no surprise, problem parsing the package. It's a system apk so I didnt expect it to be able to install via a file manager. Do I have to use adb install instead of adb push? I'm wondering if htc IME is so wired into the system that it won't work that way. What if I rename LatinIME.apk to htcime.apk or whatever the name of HTCime is and see if that works, because the system may be is treating that as the stock android keyboard, rather than a third party one, because it is labeled touch input in settings, just like LatinIME in aosp roms.
I'll experiment some more I guess
edit: Nevermind, 4.0 is draining as well, albeit less rapidly. Ah well. I guess I'll have to go back to CM6.1 if I want to do overclock. Shame, I love sense so much.
ANOTHER edit: nevermind, you were right, it isn't the kernel at all. It happens when I turn wifi off. I'm assuming that's because I don't have a data plan so it's continually retrying a server that it can't access. I don't know why it didn't do this on the stock HTC kernel, but I'm pretty sure it's the issue. If I turn wifi AND mobile data connection off, it stays at normal drain as well. Well, I'm at 11% and my battery app is estimating roughly 1 hour and 20 minutes remaining, so I don't know if that's GOOD, but I'll give it a good full charge tonight and run it tomorrow. I hopefully will have data activated tomorrow so I can really test it.

Hey guys new to the slide forum but not new to the site. I come from the G1 thread and we had the similar problem. How is your battery life on a 2.1 ROM? I have my phone rooted with a Sense ROM and it has 2.2 and i do see a bad battery drain as well. I remember froyo ROMs battery life may not be the greatest yet. I remember that was always a big problem over there and it looks like it still hurts here. Have you tried setcpu settings?

Maybe this information will help, i forgot to mention last time i posted that i'm not using a HTC device, i'm using Samsung Galaxy S, and there are more ppl with this problem on our forum aswell, so maybe someone can use this information correctly, i mean, it's either a program that's doing this or some strange freaky froyo process that not everybody has? or idk..

We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.

KCRic said:
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
Click to expand...
Click to collapse
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.

MusicMan374 said:
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
Click to expand...
Click to collapse
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.

KCRic said:
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
Click to expand...
Click to collapse
Yeah that'd be cool. It must have something to do with that, since it's the cell radio sucking battery.
Sent from my T-Mobile myTouch 3G Slide using XDA App

I flashed 6.1.0 stable, battery drain seems to be slightly less. I'm still at around 5 or 10% below where I was at this time on stock, with 9.5 hours off the charger, current level 57%. Although, I did use airplane mode for almost 2 hours, so really I'm like 10 or 20% below where I should be. I just can't figure it out, cell standby is at like 80% usage in this ROM. It's ridiculous, is it the polling intervals or something? How can it be so much less battery efficient than stock?

I flashed 6.1 RC2 with a low battery and had trouble with battery life. TMO's service was acting very strange for a couple of weeks and my cell standby was consuming a lot of juice. Flashed 6.1 RC3 with a well conditioned full battery. At first I used no setCPU just to see how things would go ... 11 hours from full battery to empty. Added setCPU to RC3 and got 27+ hours out of a full charge. Either TMO fixed it's towers or RC3 was better with cell standby because my network usage was not cranking overtime like it had been. Finally, I flashed 6.1 stable with setCPU and I average around 22 to 24 hours on one charge.
One observsation - when I first flashed RC2 I was really into my phone again. I was constantly tweaking it and flipping through options, testing apps, digging new Gapps, etc. ... bottom line I was just using my device waaaaay more than usual and I think that played a huge role in my (supposed) poor battery performance. All seems to be well with 6.1 stable.

[Q] HTC Kaiser CPU Doesn't Sleep?

Did a search, and didn't find anything regarding this, so I'll point this out. I've noticed whenever my Kaiser (KAIS100) goes to sleep, it doesn't actually sleep, I can still press every button and the phone will "wake", screen comes on.
When I check Spare Parts > Battery History, it shows my phone's been running for 5days even though it's been on for 10 minutes actual. If I continue to put the phone to sleep that time grows exponentially.
Is my KAIS really sleeping, or is there a bug somewhere?
I'm running l1q1d's latest .32 kernel, with Fat Free Froyo build with system/data on NAND.
Battery also only lasts about 8hrs in "standby", and not even 2hrs with full use. With WinMo, I get about 36hrs standby, and about 5hrs full use.

Krazy-Killa said:
I've noticed whenever my Kaiser (KAIS100) goes to sleep, it doesn't actually sleep, I can still press every button and the phone will "wake", screen comes on.
Click to expand...
Click to collapse
Screen comes on, obiusly, but its locked right? that the way its ment to be... if you wanna check the hour or see if u got messages or missed calls... or it unlocks?
Krazy-Killa said:
When I check Spare Parts > Battery History, it shows my phone's been running for 5days even though it's been on for 10 minutes actual. If I continue to put the phone to sleep that time grows exponentially.
Click to expand...
Click to collapse
I guess its not completley implemented yet, search this forum I remember I looked something about it, or post a comment to our good friend n2rjt in that thread:
http://forum.xda-developers.com/showthread.php?t=782269
Have you modified .nbh file with atools and entered the correct value on the advanced batt capacity? (units = battery real mAh * 1.6) if you havent or if you own an old battery you'll experience a lot of batt consumption or inaccurate readings....

albertorodast2007 said:
Screen comes on, obiusly, but its locked right? that the way its ment to be... if you wanna check the hour or see if u got messages or missed calls... or it unlocks?
I guess its not completley implemented yet, search this forum I remember I looked something about it, or post a comment to our good friend n2rjt in that thread:
http://forum.xda-developers.com/showthread.php?t=782269
Have you modified .nbh file with atools and entered the correct value on the advanced batt capacity? (units = battery real mAh * 1.6) if you havent or if you own an old battery you'll experience a lot of batt consumption or inaccurate readings....
Click to expand...
Click to collapse
The phone locks like it's suppose too, but the problem I'm having is the CPU of the Kaiser isn't actually falling asleep. I'm getting the same battery consumption as when the screen is off compared to on, and sitting there (no activity on my part, just leaving the screen on for no reason )
Every so often the phone will be asleep, and the only way to bring it back on is by hitting the power button, but about 95% of the time I can press the call button, end button, OK button, IE button, hell even push down on the wheel on the other side of the Kaiser and the screen will come on showing the lock screen.
As far as the battery capacity, I have not done that, but the phone's been auto-learning my capacity, and it will get to the 2160 units, compared to the 2000 it's always set too, and sometimes reach 2377 units.
I have tried several Radio versions, down to 1.65.xx.xx version (which was the original version on my phone), and no changes, and tried different builds and no change either. DZOs kernel doesn't make a difference either, except screw up my battery meter completely. lol

uhm thats wierd.. i can only unlock through the power button, what i have experienced is that if its conected to an external power source it does reacts to any button I press.... but not on battery... maybe its a build issue... right now im using scoots CM rls 5a, dont remember if warbyte's donut behave like that...

albertorodast2007 said:
uhm thats wierd.. i can only unlock through the power button, what i have experienced is that if its conected to an external power source it does reacts to any button I press.... but not on battery... maybe its a build issue... right now im using scoots CM rls 5a, dont remember if warbyte's donut behave like that...
Click to expand...
Click to collapse
Did some more testing, and found that without it plugged into power it does only respond to the power button, but again it's only about 15-20% of the time, and even those times seem iffy as it just seems like the phone's just slow to respond.
Phone is also somewhat warm as well even when "off", and I do have the phone overclocked to 450MHz, kernel is set to 425 (running a test on speed/stability atm)
At 425MHz it's still reasonably warm, and at 450 the temperature jumps alot.
Anyone else have an issue of the tap sounds when tapping on the screen sometimes not playing? Granted phone quality is great, and GPS is working well, though Camera is broken on my end, even though it was working before.

It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.

n2rjt said:
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
Click to expand...
Click to collapse
by chanse wasnt weather widget? had a really bad slowdown over scoots CM because of that widget, was constantly trying to update the weather....

albertorodast2007 said:
by chanse wasnt weather widget? had a really bad slowdown over scoots CM because of that widget, was constantly trying to update the weather....
Click to expand...
Click to collapse
Yes that's the one. it needs to be removed, and can be replaced by Fancy Widget.
Sent from my Android on HTC Kaiser/Kaiser/Polaris using XDA App

n2rjt said:
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
Click to expand...
Click to collapse
Ok, I'll give it a whirl, and remove some of the widgets I have running, and see if it does help out. Right now though I'm re-installing /system as I tried messing around with the density as 110 seems to work real well with where things are placed on the home screen (no widgets are overlapping each other), but Market won't work, and the Android Keyboard keeps crashing (on-screen).
But anyways, phone's booting back up, so I'll test out the battery life here again, as I got about 95% charge right now, so should serve as a good test for battery life, and CPU Sleepage.

Having a similar issue, seems to behave ok (screen lock comes on when I press power button) but power usage on standby is similar to original poster's. About 8 hours standby. Went to bed last night and it said 66% charged (1300mAH battery) and it didn't last the night. Takes a looooong time to charge to full though so I doubt it's lying about fully charging the battery, suggesting it's using it up at a fast rate.
How do I check background tasks?
Edit: This is with WiFi, GPS and Sync OFF by the way. On the other hand I live in a low signal area (typically 1-2 bars) could it be straining to get a better signal? Used to have an old nokia that used to run itself flat in no time when there was a low/missing signal!
Edit 2 : Figured it out, turns out the ebay app has a service and a process running - even with notifications turned off! Have killed these and see if anything improves

That could very well be part of the problem, although it shouldn't kill it from 66% with just the radio. How much capacity does it calibrate itself to?

cycloid said:
Having a similar issue, seems to behave ok (screen lock comes on when I press power button) but power usage on standby is similar to original poster's. About 8 hours standby. Went to bed last night and it said 66% charged (1300mAH battery) and it didn't last the night. Takes a looooong time to charge to full though so I doubt it's lying about fully charging the battery, suggesting it's using it up at a fast rate.
How do I check background tasks?
Edit: This is with WiFi, GPS and Sync OFF by the way. On the other hand I live in a low signal area (typically 1-2 bars) could it be straining to get a better signal? Used to have an old nokia that used to run itself flat in no time when there was a low/missing signal!
Click to expand...
Click to collapse
Phone Radio really shouldn't use more power with low signal, in fact it really shouldn't affect power output at all (well except the fact that it's on). I have a 1350mAH battery, but it's reading at 2470 adjusted, so I re-flashed a new kernel with the new battery changes, now it's reading 2437units adjusted, which is over 1500mAH for the battery which is not what I own. But on the bright side, my battery capabilities are improving, and the battery meter is starting to read alittle more accurately.

Krazy-Killa said:
Phone Radio really shouldn't use more power with low signal, in fact it really shouldn't affect power output at all (well except the fact that it's on). I have a 1350mAH battery, but it's reading at 2470 adjusted, so I re-flashed a new kernel with the new battery changes, now it's reading 2437units adjusted, which is over 1500mAH for the battery which is not what I own. But on the bright side, my battery capabilities are improving, and the battery meter is starting to read alittle more accurately.
Click to expand...
Click to collapse
yes, i boutght seidio 1600 mAh, and the kernel ended up adjusting it to 3260 units... (about 2000 mAh) maybe the 1.6 factor isnt right just as n2rjt said, maybe its closer to the 2.0

Seems like ebay may have been the culprit. Killed the ebay process and application in the background and only used about 10% over night (as opposed to over 60% the night before). I'll have to leave it overnight with ebay running again for a proper scientific test next

cycloid said:
Seems like ebay may have been the culprit. Killed the ebay process and application in the background and only used about 10% over night (as opposed to over 60% the night before). I'll have to leave it overnight with ebay running again for a proper scientific test next
Click to expand...
Click to collapse
Yah, I'm starting to run into issues with certain apps keeping the phone awake and not letting it sleep. I kill some of the apps and it actually helps out the battery some.
I installed the original launcher from one of the other froyo builds, but came across with an FC with acore, so now back with ADW.Launcher or LauncherPro.

Krazy-Killa said:
Yah, I'm starting to run into issues with certain apps keeping the phone awake and not letting it sleep. I kill some of the apps and it actually helps out the battery some.
I installed the original launcher from one of the other froyo builds, but came across with an FC with acore, so now back with ADW.Launcher or LauncherPro.
Click to expand...
Click to collapse
When you install a app, take a look at its requirements, like "PREVENT FROM SLEEP". You might have a app doing just that..

daedric said:
When you install a app, take a look at its requirements, like "PREVENT FROM SLEEP". You might have a app doing just that..
Click to expand...
Click to collapse
Yep, most of the apps I download have that. But in sad news, I'm actually going back to WMO 6.5 as I can't seem to keep Android stable on my kaiser.. I've reinstall the same build twice (which I know is not corrupted, as it was working fine 2 days ago), and Market is always corrupted...... So, for now, until I have a secondary phone I can revert too, I'll be going back to WMO for the time being.

Krazy-Killa said:
Yep, most of the apps I download have that. But in sad news, I'm actually going back to WMO 6.5 as I can't seem to keep Android stable on my kaiser.. I've reinstall the same build twice (which I know is not corrupted, as it was working fine 2 days ago), and Market is always corrupted...... So, for now, until I have a secondary phone I can revert too, I'll be going back to WMO for the time being.
Click to expand...
Click to collapse
Umh... sad...
We'll wait for you! Bye bye

daedric said:
Umh... sad...
We'll wait for you! Bye bye
Click to expand...
Click to collapse
LOL! Not like I'm leaving, I'll be popping on here every so often, and still doesn't mean I'll use Haret to load up Android to test out new builds that come out, and new kernels that are released in the future.

Krazy-Killa said:
LOL! Not like I'm leaving, I'll be popping on here every so often, and still doesn't mean I'll use Haret to load up Android to test out new builds that come out, and new kernels that are released in the future.
Click to expand...
Click to collapse
Man... that's a sin! You can't do that! You'll be off from the Brotherhood!
Kiddin' ;D

[Q] Nil's Business Gingersense 3.0 (v2.3) question

Hey everyone,
I'm under 10 posts, so I have to post here. With that said, I have a question.
I'm running nil's Business Gingersense 3.0 v2.3. When my 3G is on, my battery life seems to be sucked down about 2-3% every minute or so. Now, when I installed this ROM I did a full wipe of data/cache, dalvik, battery stats, return to stock. I also followed his instructions in his thread on his ROM about battery saving. In addition, I did my normal turning off syncing, setting apps to update only when opened, turning off all vibration features, etc. My battery still drops that 2-3% every minute.
I'm curious if anyone else is having/had this problem? If so, did you fix it?
I'm going to try Tiny's newest release kernel tonight, but wanted to see if anyone else had the same thing(s) going on with their DInc that I have.
Thanks in advance for you help!

Curious if you've noticed this after a full charge and after the battery percentage drops below ~94%?

I'm in the same boat with less than 10 posts so I also need to ask here. I am noticing that the HTC weather app seems to indicate a very different location than the one I am in. I also notice it with the weather bug app, so it seems to be a location issue and not an app issue. Sometimes if I go into settings/location and uncheck/recheck use wireless networks it corrects itself and sometimes it needs a reboot. Any ideas why or how to fix it? Thanks.

Bull_Moose said:
Curious if you've noticed this after a full charge and after the battery percentage drops below ~94%?
Click to expand...
Click to collapse
Hey Bull_Moose,
I refrained from posting a response until after I gave Tiny's kernel a couple of days of use. I haven't noticed the drop as much with the new kernel as well as switching out the Yahoo mail app for K9 Mail. It still seems to be dropping a little quicker than I'd like, but perhaps that's because I am actually seeing percentage numbers now and thus it's creating a simulated quick drop effect.
I'll give it some more testing, but it seems better now after those two fixes. Like I said, not as good as it seemed with Froyo custom ROMs or even the Gingerbread OTA leak, but perhaps that because of all the little tweaks I can do with the ROM.

m6droid said:
Hey Bull_Moose,
I refrained from posting a response until after I gave Tiny's kernel a couple of days of use. I haven't noticed the drop as much with the new kernel as well as switching out the Yahoo mail app for K9 Mail. It still seems to be dropping a little quicker than I'd like, but perhaps that's because I am actually seeing percentage numbers now and thus it's creating a simulated quick drop effect.
I'll give it some more testing, but it seems better now after those two fixes. Like I said, not as good as it seemed with Froyo custom ROMs or even the Gingerbread OTA leak, but perhaps that because of all the little tweaks I can do with the ROM.
Click to expand...
Click to collapse
I was the same way when I first used a ROM that showed % drops so part of it may just be the fact that you're keeping a closer eye on the battery life now. Once fully charged, these batteries will drain a couple of % even if it is still plugged in. That's why after five minutes of being unplugged your phone could have dropped 5% or more, it's simply "catching up" to the actual battery level.
But if you're noticing a quick drain after that initial drop then it's probably an app doing too much in the background. It is possible that the ROM/kernel/ROM and kernel combo is causing it, but I've never had this problem with any of Nils' ROMs even with the kernel he uses. (Tiny's is better though, in my opinion)

I have been using this ROM for about a week or two now and I am having an issue with the Friends widget. It will only set the default number on one person all the others go into my vcard and says set a default but it never stays set. Any suggestions???
Also can anyone tell me how to get the verizon backup assistant back. I know that I can use google for whatever reason I just prefer verizon. I have read a few forums but can't seem to find a solid answer. Also I am very new to this stuff so the more instruction from start to finish the better. Thanks in advance!!!

Is it possible at all with Nils Gingersense 3.0 or 3.5 to ever use fastboot, or is it completely out of the question (With the file being so large and all...)?

lol
lmbo im in the same boat with the 10 posts... is gay... yea this is part of getting my 10 done... im no noob!!!

Right...
gutiejor said:
lmbo im in the same boat with the 10 posts... is gay... yea this is part of getting my 10 done... im no noob!!!
Click to expand...
Click to collapse
Yeah, what's the deal with that? Makes me feel like a lesser class being or something

you have less 10 posts. that means your good at following instructions.. and you know how to fix certain troubles on your phone..

Looks like ICS has some problems!

I am seeing battery life, signal, speed, camera and wifi calling issues everywhere!
Is this in the official update from TMO as well as the ROM's that are popping up in the Dev section also? Did Samsung/TMO release a flakey ICS?
I am kind of worried and staying on GB at the moment...

I have noticed a definite decrease in battery life as well as
When listening to stock music player, if you get a text the sound goes to full volume which is quite annoying.
Randomly freezes for 5-10 seconds at a time.
Seems a bit laggy transitioning from program to program.
had to uninstall gosms, private box stopped working and for some reason would no longer vibrate on silent.
I suppose there will probably be an update at some point to fix some of these issues. not too worried, phone still kicks ass

I just recieved my S II today, and promply updated it to ICS. Everything is smooth, and I'll comment on battery life tonight.
Quadrant:
3776

It was really bad for me after about 2 hours after updating Tuesday when it released. That was the stock/unrooted GB update to the last update prior, then updated to ICS on Tuesday.
Since then I completely wiped everything, even used tdj's superwipe, reflashed stock and after that the only update kies had for me was the actual ICS bits.
Since flashing that last night it's settled down much better than Tuesday night. Battery seems to have stabilized and I'm pretty much running *everything*.
What will seriously shut down the battery drain is enabling the System Powersaving or whatever under the powersaving menu in settings.
It really makes the phone chop but if you're out and about or somehow away from a charge whatever it does really does save battery lol. It warns you the phone will mostly suck if you enable it but kinda interesting.
With the wallpaper changes, removal of some of the classic AOSP animation stuff etc. - I can only think T-Mobile is really paranoid of having people complaining about choppy phones so are in an under-the-table kind of way turning stuff off for you.
I'd rather decide that myself but that's why I'm here at XDA

i think the update have quite a few problem
sometime it freeze on text message,also don't show keyboard or laggy

Exactly! How can they release this with these critical issues?! Don't they have a QA team?

[Q] Fast battery drain inconsistent behaviour

I flashed a custom ROM [unofficial CM9 ICS4.0.4]. Everything seems to be working fine, but there are a few problems and I'm wondering if this is normal for those using this. It's my first time flashing a ROM on my android and I'm not sure if it's normal. Did some searching in the forum, couldn't find much info too. Maybe I didn't search hard enough!
Anyway, here are some issues, I'm not even sure if it's the ROM.
1. Sometimes, the apps just bring me back to the home screen several times. Example: Running whatsapp brings me to home screen a few times, or when I go into a conversation, it brings me back to the conversation list but eventually it works.
2. On another occasion, every app that I ran would be unresponsive and I needed to end it. Solved it by rebooting.
3. Battery drain is very fast with little usage. I thought running a custom ROM usually provides better battery life.
I've not overclocked it, it's still in it's default value after flashing 1024. So I doubt it's anything to do with that. But since we're on the topic on overclocking. Desire HD didn't have anything beyond Gingerbread. So if we're flashing anything greater, is there a need overclock to be able to work comfortably on a higher OS? Is there a minimum or maximum for it to function comfortably?
Thanks!

Hmm, did more reading up.
Could it be I didn't calibrate my battery after flashing a new ROM?
Just flashed ARHD 6.4, will try to calibrate after that.
Appreciate any other advice though