Develop Bugs

[Q] G2 randomly turns off after rooting

so i got a warranty replacement T-mobile g2. i rooted it using gfree method. loaded cm7 nightly...206 i think was the latest. the next day i pulled my phone from my pocket to find it had shut off. i had to pull the battery before it would power up. it did this once a day at different times. i pulled back the overclocking to 806mhz from 1113mhz. no change. i wiped and reinstalled cm7. no change. i reverted to stock. no problems for two weeks. then i thought maybe i had done something wrong during the rooting process or had a bad nightly, so i rooted again. i installed cm7 nightly 216 last night. My phone shut off again today and i had to pull the battery. my searches have revealed that this problem is fairly common, but why only when rooted? any ideas?

spudkinks said:
so i got a warranty replacement T-mobile g2. i rooted it using gfree method. loaded cm7 nightly...206 i think was the latest. the next day i pulled my phone from my pocket to find it had shut off. i had to pull the battery before it would power up. it did this once a day at different times. i pulled back the overclocking to 806mhz from 1113mhz. no change. i wiped and reinstalled cm7. no change. i reverted to stock. no problems for two weeks. then i thought maybe i had done something wrong during the rooting process or had a bad nightly, so i rooted again. i installed cm7 nightly 216 last night. My phone shut off again today and i had to pull the battery. my searches have revealed that this problem is fairly common, but why only when rooted? any ideas?
Click to expand...
Click to collapse
If you're running anything like SetCPU, you might have your min speed/screen off profile set too low.
Pull the /proc/last_kmsg next time it happens; if it is actually powering off (as opposed to just not having the clock speed to wake up), that's where you'll need to look to see what happened.
Sent from my T-Mobile G2 using XDA App

Thanks..that makes sense...I use the cm CPU settings had minimum set to 245mhz...I bumped it
up top 368...I forgot that every processor is different
Sent from my HTC Vision using xda premium

spudkinks said:
so i got a warranty replacement T-mobile g2. i rooted it using gfree method. loaded cm7 nightly...206 i think was the latest. the next day i pulled my phone from my pocket to find it had shut off. i had to pull the battery before it would power up. it did this once a day at different times. i pulled back the overclocking to 806mhz from 1113mhz. no change. i wiped and reinstalled cm7. no change. i reverted to stock. no problems for two weeks. then i thought maybe i had done something wrong during the rooting process or had a bad nightly, so i rooted again. i installed cm7 nightly 216 last night. My phone shut off again today and i had to pull the battery. my searches have revealed that this problem is fairly common, but why only when rooted? any ideas?
Click to expand...
Click to collapse
Could be the battery moving ever so slightly... check out this post: http://forum.xda-developers.com/showpost.php?p=17876904&postcount=276

I've seen similar posts/threads...I'll keep it in mind...I tried the "tape over the sdcard method" to no avail...this is just as easy I'll give it a couple days to see if the min CPU speed is my prob
Sent from my HTC Vision using xda premium

spudkinks said:
Thanks..that makes sense...I use the cm CPU settings had minimum set to 245mhz...I bumped it
up top 368...I forgot that every processor is different
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Ouch, that's probably the problem; when I was using SetCPU I have mine at 386 without any issues, when I had it lower I was running into the same problem as you.
Sent from my T-Mobile G2 using XDA App

I hope that's it...my first G2 had no issues with 245 min setting. I guess this one is just more finicky
Sent from my HTC Vision using xda premium

Well...it went 36 hours, but it did it again. I've also had one random reboot today and massive force close. By that I mean my browser, swype, and adw all force closed at the same time. Maybe my warranty replacement is someone elses unfixed warranteed phone...
Sent from my HTC Vision using xda premium

Intermittent Hanging When Switching From Screen On to Off and back On

Alright I have only had my white DInc2 for a week and I have noticed this since day one, certainly on CM7 (with and without custom kernels) and possibly on sense too (I'm not positive since I flash constantly but I deffinitely use CM7 more). Basically when I hit the power button to shut the screen off, and then almost immediately hit it again turn it back on, the phone will hang and the screen may not come on for 30 - 60 seconds. It doesn't matter how many times I hit the button. This happened almost right after I bought the phone, running cm7 but at stock speeds and overclocked. As I said above it's happened on at least a few different kernels. So what could be the issue? I've seen something similar on the Eris back in the day and that was caused by the minimum voltage being to low on screen off. But like I said its done this even at stock speeds. I still have a little time left to return this phone if need be, or I have insurance that covers everything (including water damage) so I can always get another phone if need be. And the insurance has no deductible, so that's a plus.
If anyone can help me out here, it would be much appreciated.
Thanks
Sent from my Incredible 2 using Tapatalk

n0yd said:
Alright I have only had my white DInc2 for a week and I have noticed this since day one, certainly on CM7 (with and without custom kernels) and possibly on sense too (I'm not positive since I flash constantly but I deffinitely use CM7 more). Basically when I hit the power button to shut the screen off, and then almost immediately hit it again turn it back on, the phone will hang and the screen may not come on for 30 - 60 seconds. It doesn't matter how many times I hit the button. This happened almost right after I bought the phone, running cm7 but at stock speeds and overclocked. As I said above it's happened on at least a few different kernels. So what could be the issue? I've seen something similar on the Eris back in the day and that was caused by the minimum voltage being to low on screen off. But like I said its done this even at stock speeds. I still have a little time left to return this phone if need be, or I have insurance that covers everything (including water damage) so I can always get another phone if need be. And the insurance has no deductible, so that's a plus.
If anyone can help me out here, it would be much appreciated.
Thanks
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
What are your screen off clock speeds.
Sent from my HTC Incredible 2 using xda premium

245, though on a sense Rom I had it lower and didn't have a problem.
Sent from my ADR6350 using Tapatalk

n0yd said:
245, though on a sense Rom I had it lower and didn't have a problem.
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
Try upping it.
Sent from my HTC Incredible 2 using xda premium

knipp21 said:
Try upping it.
Sent from my HTC Incredible 2 using xda premium
Click to expand...
Click to collapse
I'll try it but its so random, its very odd. It happened quite a bit when I first got the phone, then it didn't happen at all for a good 4 or 5 days. Also it only seems to happen when I switch off and back on right away, if I switch off and come back to the phone 15min later it comes right on at the press of a button.
Sent from my ADR6350 using Tapatalk

A little update. Running a sense 3.5 rom I had my screen off set to 245 min AND max. I haven't had any problems. So that's more evidence leaning towards it not being a minimum voltage problem. But the problem is so damn intermittent, I'm really not sure what to think of it. I did see on another forum someone else had the same problem but they didn't go into detail.
Well if anyone else has ideas, shoot them my way. Thanks
Sent from my Incredible 2 using Tapatalk

I had similar problems on my eris and it was related to the governor settings (my eris hated smartass in particular.) The min clock speed affected it as well but not as much. I would try a different governor.
Sent from my Incredible 2 HD using XDA App

SGH-i747m overheating

Hello there xda. I bought my first SGH-i747m(Canada Bell version) and it had a pretty serious heat problem when I did use my cellphone doing anything for more than 5 minutes. After 15 minutes it usually bothers me too much so I just stop using my device.
I didn't try anything to fix it yet other than using a JB rom(ParanoidAndroid) on both my first device, and now my second device. They both do the absolute same thing. The bottom half gets really hot while the top half stays really cool.
Is that a common thing? If so, is there any fixes? It's really horrible to use a half hot/cold device, even worse than using a fully hot device.

Nah
Try turning Powersave On.
I had issues with overheating too.
Now they are all gone.
I'm running Nostalgia 7.5

It gets hot at the bottom because that's where the CPU and all that good stuff are, and that good stuff gets hot. Mine doesn't get crazy hot down there but it is definitely warmer down there then the top, that much is normal. Yours may be to hot down there however... Idk. But I've seen others with this issue cool the phone down with custom kernels. I've also seen people say custom kernels make there phone hotter.. Try it out.
Sent from my SGH-I747M using Tapatalk 2

bravomail said:
Try turning Powersave On.
I had issues with overheating too.
Now they are all gone.
I'm running Nostalgia 7.5
Click to expand...
Click to collapse
I'm on custom JB, so there' no "powersave".
I guess I'll try different kernels etc. I'm quite close to actually selling the device, overheating is one of my pet peeves.

Are you sure its overheating?
Like the gentleman a few posts up said. Depending on how you use it. The phone will get warm.
It should never be actually hot, to the point where it will harm you if you pick it up.
Sent from my SAMSUNG-SGH-I747 using xda premium

try going back to stock, all of a sudden the phone doesnt get as hot.
or try underclocking your kernel on custom. AOKP and CM both have an out of the box clock of 1.8 Ghz.
tune it down to 1.3 or 1.1. issue gone.

ThatJawn said:
Are you sure its overheating?
Like the gentleman a few posts up said. Depending on how you use it. The phone will get warm.
It should never be actually hot, to the point where it will harm you if you pick it up.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I feel like I shouldn't be complaining, and that it's not "overheating" but it's getting warm. I'm used to my SGS1 which runs ice cold whatever I do.
I just underclocked it, but I don't even feel the difference. I'm now running the new ParanoidAndroid with the custom kernel recommended in here. It has all the tweaking tools necessary.

Happened even on stock ROM
Mine runs a bit warm too. It is warm to the point where is gets uncomfortable to keep in my pocket at times and as far as I know it is doing "nothing". It will be fine, then I check an email or G+ notification then it goes crazy.
One commenter suggested going back to stock but mine has been doing the same thing since then, it just seem a bit more regular for the last few days. I am now in KyanROM 1.3. I am going to give that po.wer save thing a shot over the next day or so and let you guys know how that goes.

Use setcpu load up the setcpu widget and tell up what tempature your phone is
Sent from my SAMSUNG-SGH-I747

I notcied it is overheating when it's on LTE and the battery drain fast. I turned LTE off and I am using 4g or wifi and i don't have this problem

I noticed my phone started connecting to LTE since this week too but my overheating problem started long before that. What I noticed though is that the battery also started to drain a lot faster when it started. For the battery drain, I am thinking it is either that LTE thing or a rouge app trying access my GPS a lot since the icon keeps popping up more and more in the notification bar "searching". For now I have disabled LTE and GPS until I have time to investigate them.
By the way, I tried using PowerSave, as someone suggested to help with the overheating, but it screwed up how some of my emails are displayed so I turned it off.

ROM stability vs features questions

As a noob I'm realizing I might have gotten pretty lucky. I've never rooted a phone (and probably won't - can't live without it if it bricks!) but I successfully rooted my Kindle on the first try and have been fooling around with various ROMs and have had only seemingly trivial issues. I started with Android Open Kang Project - otter - milestone 6. I can't even remember now the particulars of what I didn't like about it but I quickly switched to CM10 Jelly Bean with SG17 enhancements [linaro]. I liked it but had some instability with 20120916 so installed 20120920 which has been more stable for me so far. I also installed the UNOFFICIAL CM10 +3.x kernel for kindle fire but switched back alley because it didn't have a tablet UI (so odd since it's a build specifically for the kindle - did I overlook the setting???]
So my questions are:
How lucky have I been? Should I look for an older totally stable ROM and stick with it or even go back to stock?
If I do decide to continue experimenting what level of risk is it really to look for the ROM that I like - e.g. tablet UI, pretty basic, quick - vs looking solely for something rock solid.
Finally, what advice for a noob on what to look for and how to test various ROMs and any thoughts on your favorite for the Fire and why.
BTW, I also tried eye candy and did not care for it. In fact I'm irritated that my twrp was sort of hijacked with an eye candy mod and I can't figure out how to get it off. Have not loaded jandycane but want to because I can. Pushing that luck?
Sent from my Amazon Kindle Fire using xda app-developers app

I wanted to edit typos and add that use GO Launcher EX so the launcher features of the ROM are irrelevant. Don't see an edit option...
Sent from my Amazon Kindle Fire using xda app-developers app

Running custom roms are not for everyone. They normally come with some needed trouble shooting. As long as you do your needed research before hand you will be fine but there is always a risk when rewritting the OS on any device. Be it cellphone, tablet or PC.
No one will be able to tell you what is the best for your device. Its a flash and test yourself type of thing
Sent from my SGH-I777 using Tapatalk 2

sharonbw said:
As a noob I'm realizing I might have gotten pretty lucky. I've never rooted a phone (and probably won't - can't live without it if it bricks!) but I successfully rooted my Kindle on the first try and have been fooling around with various ROMs and have had only seemingly trivial issues. I started with Android Open Kang Project - otter - milestone 6. I can't even remember now the particulars of what I didn't like about it but I quickly switched to CM10 Jelly Bean with SG17 enhancements [linaro]. I liked it but had some instability with 20120916 so installed 20120920 which has been more stable for me so far. I also installed the UNOFFICIAL CM10 +3.x kernel for kindle fire but switched back alley because it didn't have a tablet UI (so odd since it's a build specifically for the kindle - did I overlook the setting???]
So my questions are:
How lucky have I been? Should I look for an older totally stable ROM and stick with it or even go back to stock?
If I do decide to continue experimenting what level of risk is it really to look for the ROM that I like - e.g. tablet UI, pretty basic, quick - vs looking solely for something rock solid.
Finally, what advice for a noob on what to look for and how to test various ROMs and any thoughts on your favorite for the Fire and why.
BTW, I also tried eye candy and did not care for it. In fact I'm irritated that my twrp was sort of hijacked with an eye candy mod and I can't figure out how to get it off. Have not loaded jandycane but want to because I can. Pushing that luck?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Rooting and installing ROMs may not be everyone's forte, but there is nothing to fear if you've done every step correctly. Many of these CM builds are nightly builds; that is they release one every short interval of time fixing small bugs encountered in the previous release. If you really want to enjoy CM, you could go for the latest stable build.
To your first question: Yeah, switch back to an older ROM. That's generally more stable and you have the whole thread to sort through if you get into some tough spot. You've been pretty lucky to have gotten so far without bricking your device, I must say. I don't recommend reverting back to stock; you'd miss a lot of the features that aren't there on the KF.
To your second one: that's totally up to you. I confess, I don't own a KF, but with the phones I've had, I've always been experimenting with them. My old Moto Razr, my Moto Ming, my Nokia 5800, my Nokia N8...the list goes on. Changing ROMs, it's kind of like an hobby of mine.
You could lean towards a better UI( I really like the one on stock KF though) or a rock solid feature rich performance ROM. It's up to you.
As to your third question: I can't really answer that sorry. I'm a Galaxy Tab user, so I don't know much about KFs. As to testing ROMs, well, you said it. Test them. There's no other way to know if you're going to like them or not otherwise.
Yes, install Jandycane. It's not pushing your luck. There's no room for error unless you're so excited that you even make silly mistakes.
You can modify posts by tapping on it, selecting Modify, then edit.
Hope I helped you some.
One ****ing minute! - Billie Joe Armstrong at iHeartRadio Music Fest 2012

It's not luck if u spent time reading n following the rooting tutorial, it's ur work, though small compared to developers. I'm exactly like u, 1st time ever use an android device, but with experience with my Nokia5800, it's easier for me to solve problems, not to panic when rooting a device .
For me, keep rooting different Roms until the most suitable for personal use is enough. As time passes, I feel tired of doing the setting again after installing every new Rom. I stick with twa 's Linaro 'til now.
I think the risk of experimenting new Rom is small because the device memory is very hard to malfunction. As long as ur PC and KF is there, u don't have to worry.
There's still a lot to learn abt android, not only rooting, I think. Right now I'm learning about OTG and how to use external devices with KF, like flash drive or microphone.
All credits and thanks to our developers such as hashcode and twa.
Sent from my Amazon Kindle Fire using Tapatalk 2

Thanks for the replies. I did go ahead and play around wiping and installing new ROMs starting with going back to stock all the way through pretty much the same sequence I did before with the same result LOL! I ended right back here with tw_priv's CM10. I like it very much and other than some random burps and glitches I've experienced - things others have also seen (Facebook - keyboard not opening; sleep of death - multiple times; WWF is totally messed up but that might be 100% zynga), its been pretty darn stable.
My biggest issue is that my battery life sucks! Anyone want to advise me on how to analyze/improve that?
I love reading here and learning but I'll never be a dev or even a power user. Do the dev of custom ROMs even want people like me to use them? This site is definitely not user friendly ha ha
Sent from my Amazon Kindle Fire using xda app-developers app

sharonbw said:
Thanks for the replies. I did go ahead and play around wiping and installing new ROMs starting with going back to stock all the way through pretty much the same sequence I did before with the same result LOL! I ended right back here with tw_priv's CM10. I like it very much and other than some random burps and glitches I've experienced - things others have also seen (Facebook - keyboard not opening; sleep of death - multiple times; WWF is totally messed up but that might be 100% zynga), its been pretty darn stable.
My biggest issue is that my battery life sucks! Anyone want to advise me on how to analyze/improve that?
I love reading here and learning but I'll never be a dev or even a power user. Do the dev of custom ROMs even want people like me to use them? This site is definitely not user friendly ha ha
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
That's what you get for a $200 tablet sorry. You could look around your device forum asking for prop.build tweak that optimize battery life.
You'll understand all the big dev terms sooner or later. Its just a matter of time.
Sent from my GT-S5360 using Tapatalk 2

zelendel said:
Running custom roms are not for everyone. They normally come with some needed trouble shooting. As long as you do your needed research before hand you will be fine but there is always a risk when rewritting the OS on any device. Be it cellphone, tablet or PC.
No one will be able to tell you what is the best for your device. Its a flash and test yourself type of thing
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I know this is off topic, I'm sorry. But I don't see any risk with rewriting the OS of a PC versus a Phone. A Phone has a rom chip that is fairly easy to break. By unplugging the device during rooting, for example. But on a PC, if something goes wrong, you can always stick the disc in and try again.
On topic, with custom roms you will always run into stability issues. However, if you do not care about the latest and greatest, try a rom based on CM7. They are stable (in use for years on different devices)

x10knight said:
I know this is off topic, I'm sorry. But I don't see any risk with rewriting the OS of a PC versus a Phone. A Phone has a rom chip that is fairly easy to break. By unplugging the device during rooting, for example. But on a PC, if something goes wrong, you can always stick the disc in and try again.
On topic, with custom roms you will always run into stability issues. However, if you do not care about the latest and greatest, try a rom based on CM7. They are stable (in use for years on different devices)
Click to expand...
Click to collapse
There are many things that could go wrong when rewritting the OS on your PC that could make that not an option.
Sent from Arkham

My battery life (which wasn't terrible "cheap" tablet or not - this is the kindle fire forum, right?) got worse after I rooted it and flashed custom ROM. I had hoped it would get better since that seems to be something all the devs are after. I was hoping someone could point out settings I may not have adjusted correctly after installing. Or would that be too easy?
Sent from my Amazon Kindle Fire using xda app-developers app

sharonbw said:
My battery life (which wasn't terrible "cheap" tablet or not - this is the kindle fire forum, right?) got worse after I rooted it and flashed custom ROM. I had hoped it would get better since that seems to be something all the devs are after. I was hoping someone could point out settings I may not have adjusted correctly after installing. Or would that be too easy?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Yes, it is the KF forum. You could try underclocking the device. That way, less CPU and more battery. If you could point out your current ROM, I'll take a deeper look and help you out.
Sent from my asus_laptop using Tapatalk 2

gadgetroid said:
Yes, it is the KF forum. You could try underclocking the device. That way, less CPU and more battery. If you could point out your current ROM, I'll take a deeper look and help you out.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
I appreciate the offer! This is the first rooted device I've had. I don't really know what underclocking is but would like to learn. I'm using twa_priv's ROM 20120923 (I think - maybe 25)
Sent from my Amazon Kindle Fire using xda app-developers app

sharonbw said:
I appreciate the offer! This is the first rooted device I've had. I don't really know what underclocking is but would like to learn. I'm using twa_priv's ROM 20120923 (I think - maybe 25)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
CM9 and CM10 roms (the one you are using is CM10) tend to have worse battery life than other ROMs. It's kind of a trade-off, worse battery for more functionality. If you want really great battery life, you could use one of the old CM7 roms. They'll likely have the best overall battery life, but won't be quite as fancy/snappy as the newer ROMs would be.

Aesrys said:
CM9 and CM10 roms (the one you are using is CM10) tend to have worse battery life than other ROMs. It's kind of a trade-off, worse battery for more functionality. If you want really great battery life, you could use one of the old CM7 roms. They'll likely have the best overall battery life, but won't be quite as fancy/snappy as the newer ROMs would be.
Click to expand...
Click to collapse
Yes, that's true.
@OP underclocking means that you simply set the CPU to operate at a give frequency. It doesn't go more than that. My Android tablet has an Intel Core i3-350M 2.26 GHz processor. Average battery life is around an hour; but then when I underclock it to 800MHz, I get close to five hours.
Sent from my asus_laptop using Tapatalk 2

gadgetroid said:
Yes, that's true.
@OP underclocking means that you simply set the CPU to operate at a give frequency. It doesn't go more than that. My Android tablet has an Intel Core i3-350M 2.26 GHz processor. Average battery life is around an hour; but then when I underclock it to 800MHz, I get close to five hours.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
I have some issues w/ sleep of death. I saw a post that suggested doubling minimum CPU frequency. Is that underclocking or overclocking or neither??
Clock data: min 300 Max 1200 current 300
CPU - whatever comes in the kindle fire. :8
Sent from my Amazon Kindle Fire using xda app-developers app

sharonbw said:
I have some issues w/ sleep of death. I saw a post that suggested doubling minimum CPU frequency. Is that underclocking or overclocking or neither??
Clock data: min 300 Max 1200 current 300
CPU - whatever comes in the kindle fire. :8
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
You're at 300 MHz? Wow! That's way too slow! I even wonder how you get most of the jobs done. You're underclocking the device. If you're having Sleep of death issues, then increase the frequency to about 600 MHz. That should take care of it. Also, that won't eat up much battery, so you should be safe. But, as suggested, you should switch to older CM7 ROMs as they have excellent battery backup.
Sent from my asus_laptop using Tapatalk 2

gadgetroid said:
You're at 300 MHz? Wow! That's way too slow! I even wonder how you get most of the jobs done. You're underclocking the device. If you're having Sleep of death issues, then increase the frequency to about 600 MHz. That should take care of it. Also, that won't eat up much battery, so you should be safe. But, as suggested, you should switch to older CM7 ROMs as they have excellent battery backup.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app

sharonbw said:
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
The KF on stock ROM operates between 400-800 MHz. It is set that low on all Custom ROMs, whatever the device may be (That is, if they have their own kernel). There is no normal frequency. It's like a car. You go in third gear or fourth gear as you wish. There are no steadfast rules that you have to go in fourth gear on a road and the fifth in another. CPU governors are how you set the frequencies. I don't know what you get on the KF, but on the other devices that I have tried, "Blackcats" is the one for day-day usage. Not too much, not too less.
Yes, that's the thing about having a fancy ROM. I have a completely transparent ROM on my Galaxy Y and sometimes, the thing goes bonkers. Since my phone doesn't have CM yet, these fancy transparent ROMs are the best bet for a flashy and beautiful ROM. On stock, I get around 1-2 days, but on these transparent ROMs, I get like 5-6 hours a day. Not too bad, considering that my completely transparent W7 laptop only stays for an hour on battery.
Sent from my asus_laptop using Tapatalk 2

sharonbw said:
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I honestly don't think your SOD (sleep of death) is due to the 300 Min frequency. I've had that set on any recent KF rom I've used without a problem (as mentioned previously, it tends to be the default value, with max being 1000 or 1200 (don't remember the exact value). It's more likely that something you have installed, or some setting that has been changed, is causing the problem.
One way to find out would be to do a complete wipe of the system in TWRP (factory reset, system, cache, and dalvik) and install whatever ROM you're interested in fresh (don't forget to install gapps too) and then see if you continue to have the SOD problems. Stick with stock settings for a while and see if something happens. Just my two cents of course.

Aesrys said:
I honestly don't think your SOD (sleep of death) is due to the 300 Min frequency. I've had that set on any recent KF rom I've used without a problem (as mentioned previously, it tends to be the default value, with max being 1000 or 1200 (don't remember the exact value). It's more likely that something you have installed, or some setting that has been changed, is causing the problem.
One way to find out would be to do a complete wipe of the system in TWRP (factory reset, system, cache, and dalvik) and install whatever ROM you're interested in fresh (don't forget to install gapps too) and then see if you continue to have the SOD problems. Stick with stock settings for a while and see if something happens. Just my two cents of course.
Click to expand...
Click to collapse
It's too early to know for sure but no SoD since I upped it. I've done clean several installs and i've had it since the first iteration using twa_priv's CM10. I'm currently running 20120923.
I'm still a little unclear on what clocking is but I guess that's a deficit in my knowledge of physics.
UPDATE: Well came back to my kindle after watching tv and it was in the SoD. Force power off and reboot and I'm back in business. I'll leave the clock speed at min 300 since I didn't notice any difference.
I'm going to do a search but anyone want to give me a link to a 'how to' for doing a logcat? (Is that even the right term? ) I don't know that the developers want to hear from me but I could at least post the log when I experience SoD.
Edit: nevermind. I found how to logcat.
Sent from my Galaxy Nexus using xda app-developers app

[Q] help with battery saving kernel settings

Hello. Not sure if this is the correct section or not. But here goes.
I was running rootbox 4.2.2 and kt747 kernel. Along with baconatorx something script to apply settings to second core. I was getting roughly 3 to 4 hours screen on time. Great!
Recently I installed slimbean 4.3.1 after hearing so many people say it has the best battery life. With the according 4.3 kt747 kernel. I applied the same tweaks etc but at best I can get 2 hours of screen on time. Maybe there is a new script I'm unaware of.
I use my phone frequently but not heavily. Just phone calls SMS and abit of chrome. Can anyone give me some advice. Or someone with some working settings with the combo I have? Or should I just go back to what I had?
Any help would be great.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app

Anyone?
Sent from my Nexus 7 using XDA Premium HD app

See my posts on this page for my set and the battery life I am getting. Maybe these could help you:
http://forum.xda-developers.com/showthread.php?t=1969201&page=386

diablo009 said:
See my posts on this page for my set and the battery life I am getting. Maybe these could help you:
http://forum.xda-developers.com/showthread.php?t=1969201&page=386
Click to expand...
Click to collapse
Thanks. Just tried out your settings on my setup with the badass gov and slightly more under clock. And that's all you done?
I'm on 34% and only 1 hour 25 min screen on time.
And its 3rd on the list in battery stats.
I might be wrong but should cell stand by and phone idle be on top for battery usage? This is driving me nuts I have to carry my damn charger during the day.
I will report back after a few cycles.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app

ronedogg said:
Thanks. Just tried out your settings on my setup with the badass gov and slightly more under clock. And that's all you done?
I'm on 34% and only 1 hour 25 min screen on time.
And its 3rd on the list in battery stats.
I might be wrong but should cell stand by and phone idle be on top for battery usage? This is driving me nuts I have to carry my damn charger during the day.
I will report back after a few cycles.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
What I am putting down below are purely from my view and my observations over the past few years.
There could be multiple issues:
1. Your battery might be getting old. On 2.8 I set the record at a whopping 7 hours display time (battery less than 6 months old). On the same ROM I was getting barely 2-3 hours (battery near to or over 18 months old) a few days before I flashed 4.1. So when I got 3h45m today, I consider that a pretty good battery.
2. You signal levels at home, the areas you roam, and at your work/school. These too kill more. Example, battery discharges slowly (when idle) at home compared to when I am at work cos of low signal levels at my work place.
3. Maybe there are too many background apps.
Example: Kik, Facebook, Google Plus. These are known battery hogs. You either uninstall these or freeze them when not needed. Your battery will thank you.
4. Kernels don't suit every phone. What works for me might not work for you. Example: Kernel of 2.8 people loved. But for me it drained battery crazy. I used Kernel C of prior version of ROM. Try out multiple, but give atleast 3 days to validate each.
5. Most importantly, do no UC too much. A phone spending 10 seconds at 1000 MHz could need 30 seconds at 800 MHz to get the same task done, and this could actually drain your battery more. For me, after using multiple phones on multiple ROMs, I found speeds between 800-1200 quite satisfactory. This is the reason my clock is normally set to 1000 as max.
6. I barely UV. UVing a little aggressively might seem to extend battery a little, but in the process it kills the phone processors and other parts. This is because they are getting strained working with lower currents than recommended. Also it is a normal practice to actually send a little more than needed currents to phone processor to avoid phone being shut off.
Our devs here who make kernels already reduce the voltage to sustainable levels to improvise on the kernel. This is also one reason why I don't bother about UVing any more.
Sorry about being lengthy and boring :victory:

diablo009 said:
What I am putting down below are purely from my view and my observations over the past few years.
There could be multiple issues:
1. Your battery might be getting old. On 2.8 I set the record at a whopping 7 hours display time (battery less than 6 months old). On the same ROM I was getting barely 2-3 hours (battery near to or over 18 months old) a few days before I flashed 4.1. So when I got 3h45m today, I consider that a pretty good battery.
2. You signal levels at home, the areas you roam, and at your work/school. These too kill more. Example, battery discharges slowly (when idle) at home compared to when I am at work cos of low signal levels at my work place.
3. Maybe there are too many background apps.
Example: Kik, Facebook, Google Plus. These are known battery hogs. You either uninstall these or freeze them when not needed. Your battery will thank you.
4. Kernels don't suit every phone. What works for me might not work for you. Example: Kernel of 2.8 people loved. But for me it drained battery crazy. I used Kernel C of prior version of ROM. Try out multiple, but give atleast 3 days to validate each.
5. Most importantly, do no UC too much. A phone spending 10 seconds at 1000 MHz could need 30 seconds at 800 MHz to get the same task done, and this could actually drain your battery more. For me, after using multiple phones on multiple ROMs, I found speeds between 800-1200 quite satisfactory. This is the reason my clock is normally set to 1000 as max.
6. I barely UV. UVing a little aggressively might seem to extend battery a little, but in the process it kills the phone processors and other parts. This is because they are getting strained working with lower currents than recommended. Also it is a normal practice to actually send a little more than needed currents to phone processor to avoid phone being shut off.
Our devs here who make kernels already reduce the voltage to sustainable levels to improvise on the kernel. This is also one reason why I don't bother about UVing any more.
Sorry about being lengthy and boring :victory:
Click to expand...
Click to collapse
Lengthy but not boring at all. ill try to add some more info on my phone and its setup.
1. my phone is less then 6 months old. 2.8 what? kernel version? 7 hours id poop a brick. lol
2. my signal strengths haven't changed at home or at work. I work outside lol however at home i do have a mountain behind me. literally a cliff side and i always got half signal since i got the phone.
3. i got the background stuff kicked. got greenify running and i have it hibernating just about everything it will let me.
4. ok this brings me back to what i was thinking originally. maybe i should just go back to what i had with rootbox 4.2.2 + kt747 kernel and scripts.... was trying to avoid this lol. 4.3 must just not jive with my phone.
5. i do have my voltages under volted 50 across the board. i have had the odd random reboot. my clocks were always either 1.2 or 1.0 ghz. never did oc or uc too much.
i will set my voltages back to stock after a few cycles.
also i run fs trim. supposed to stop lag or something. i been running it on all my devices so i figured i may as well follow suit with my s3. i also renamed mpdesion.
my standby time is still good. ill get 2 days on weekends when im not using phone much. but screen time is still less then 2 hours.
i just finished the first full charge with what u recommended. so lets see. heading out for 10 hours here soon. lets see how it does!

My bad! All my references to ROM or kernel versions pertains to Intergalatic ROM and its kernels. Sorry, I should've mentioned that.

diablo009 said:
My bad! All my references to ROM or kernel versions pertains to Intergalatic ROM and its kernels. Sorry, I should've mentioned that.
Click to expand...
Click to collapse
Thanks for your time. I've tried your settings for a few cycles. 3+ hours battery. And 2 days total. Not bad!
I have a question. I'm reading on that intergalactic ROM, and it says about certain bootloaders. One is non reverse able or something. I've read on it and I can't figure out what one to use. My phone is on telus if that means anything.
Sent from my Nexus 7 using XDA Premium HD app

ronedogg said:
Thanks for your time. I've tried your settings for a few cycles. 3+ hours battery. And 2 days total. Not bad!
I have a question. I'm reading on that intergalactic ROM, and it says about certain bootloaders. One is non reverse able or something. I've read on it and I can't figure out what one to use. My phone is on telus if that means anything.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I used the first one (reversible):
Option A: MJ2 bootloader and MJB modem

diablo009 said:
I used the first one (reversible):
Option A: MJ2 bootloader and MJB modem
Click to expand...
Click to collapse
Thanks man. I downloaded the mj2 boot loader and mjb modem package. Do I flash this prior to the ROM? And say I choose to go back to slimbean, do I have to do anything to reverse this?
Sorry I just never had to do this on my nexus 7 or ace Android devices . I just wanna make sure I cover all bases. I kinda miss a two based ROM and after hearing your success with battery on it. Its obvisouly the ROM and kernel combo for me. Games I could care less about, I use my phone for texting Facebook and browser. And I go long periods without access to charger.
Thank you so much for all your assistance.

ronedogg said:
Thanks man. I downloaded the mj2 boot loader and mjb modem package. Do I flash this prior to the ROM? And say I choose to go back to slimbean, do I have to do anything to reverse this?
Sorry I just never had to do this on my nexus 7 or ace Android devices . I just wanna make sure I cover all bases. I kinda miss a two based ROM and after hearing your success with battery on it. Its obvisouly the ROM and kernel combo for me. Games I could care less about, I use my phone for texting Facebook and browser. And I go long periods without access to charger.
Thank you so much for all your assistance.
Click to expand...
Click to collapse
Yes. Following the same sequence of steps mentioned there. I too did the same.
And rest assured, once you are on this, I don't see a reason you'd even want to go back
Until this release neither we had to do all this boot loader thingy. But with the latest release Samsung did something that created all this mess.

diablo009 said:
Yes. Following the same sequence of steps mentioned there. I too did the same.
And rest assured, once you are on this, I don't see a reason you'd even want to go back
Until this release neither we had to do all this boot loader thingy. But with the latest release Samsung did something that created all this mess.
Click to expand...
Click to collapse
Hey. When I try to flash the boot loader and modem zip it gives me a error in twrp saying it can't load the zip.
Sent from my Nexus 7 using XDA Premium HD app

ronedogg said:
Hey. When I try to flash the boot loader and modem zip it gives me a error in twrp saying it can't load the zip.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
1. Try updating your TWRP.
2. Try downloading the zip again, and verify the zip.

diablo009 said:
1. Try updating your TWRP.
2. Try downloading the zip again, and verify the zip.
Click to expand...
Click to collapse
Thanks. This wasn't my issue. I needed the i747m boot loader mk5. Intergalactic thread op directed me to it in the s3rx thread.
About to install here soon, backing up and doing a nandroid just incase.. Im going to go With kt kernel and your simple adjustments.
I see u were using 1 15 kernel. I got 1 18. Shouldn't make a difference?
What are u getting now for screen time?

ronedogg said:
Thanks. This wasn't my issue. I needed the i747m boot loader mk5. Intergalactic thread op directed me to it in the s3rx thread.
About to install here soon, backing up and doing a nandroid just incase.. Im going to go With kt kernel and your simple adjustments.
I see u were using 1 15 kernel. I got 1 18. Shouldn't make a difference?
What are u getting now for screen time?
Click to expand...
Click to collapse
That was very dangerous. Sorry, I too should've asked. Had it gone through, you could've ended up bricking your phone. Whew! Missed by a whisker!
And I flashed 1.15. I am not sure of 1.18 'cos I haven't installed it. But newer version should be better.

diablo009 said:
That was very dangerous. Sorry, I too should've asked. Had it gone through, you could've ended up bricking your phone. Whew! Missed by a whisker!
And I flashed 1.15. I am not sure of 1.18 'cos I haven't installed it. But newer version should be better.
Click to expand...
Click to collapse
Hey!
So I ended up leaving that tw ROM for now. I made a nandroid so I will try it again.
But I'm here to report my new setup and battery stats.
I'm running slimkat rc2 with the latest ktoonsez kernel.
I'm using your settings in ktweaker but I ended up back on koonservative gov and enabled hotplugging.
7h screen on time. WiFi on the whole time. Browsing forms reading emails.
Lag free 100%
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app

Do I need to post a screenshot for proof? Or does it really matter lol
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app

ronedogg said:
Do I need to post a screenshot for proof? Or does it really matter lol
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
We are all so used to getting good battery, it hardly matters anymore, unless someone posted a hard-to-believe 10 hours on stock battery.