I know for a fact the phone gets hot when playing some games like Asphalt 7 and that is understandable but it never used to get hot while in regular use such as browsing the web or text messaging on stock and i could have the screen on for an hour. Ever since i installed CM10 and now on AOKP by task650 I have noticed the bottom half of the phone gets very warm even when doing simple things. I have the brightness set to auto at all times and within 15 minutes or so it starts to get hot.
Does this happen to anyone else or its just me? Also maybe there is a tweak for the screen in the ROM?
How long has it been since you installed these AOSP roms. In my experience, it takes one or two days for everything to settle down after installation, during which the phone might overheat and battery life takes a hit. My advice would be to give it some time, but if you're really worried, try fixing permissions or even going back to a touchwiz ROM.
jebise101 said:
I know for a fact the phone gets hot when playing some games like Asphalt 7 and that is understandable but it never used to get hot while in regular use such as browsing the web or text messaging on stock and i could have the screen on for an hour. Ever since i installed CM10 and now on AOKP by task650 I have noticed the bottom half of the phone gets very warm even when doing simple things. I have the brightness set to auto at all times and within 15 minutes or so it starts to get hot.
Does this happen to anyone else or its just me? Also maybe there is a tweak for the screen in the ROM?
Click to expand...
Click to collapse
I am having the same problem with CM10. I have tried multiple nightlies with the stock CM10 kernel and my phone just seems to run warmer. I can't figure it out. When I flash back to the stock ROM it doesn't do it unless like you said, I am playing Asphalt or some other games.
Nah not worried because i have extended warranty on my phone. Its just i like my electronics to function the way they should and when they don't i HAVE to fix them or i will loose my mind, plus its kinda annoying when hold it.
I know it needs a few charge cycles and installed CM earlier this week so its been at least 3 days, but still noticed the phone heating up. I installed AOKP today and will try cycling the battery a few times.
Pardon my ignorance but why would fixing permissions have anything to do with this? Also there is no negative effects to doing this? I don't see any as it wil just mark everything rwx-r--r-- or whatever the default is, but just want to confirm.
RobbieL811 said:
I am having the same problem with CM10. I have tried multiple nightlies with the stock CM10 kernel and my phone just seems to run warmer. I can't figure it out. When I flash back to the stock ROM it doesn't do it unless like you said, I am playing Asphalt or some other games.
Click to expand...
Click to collapse
I was thinking it maybe the CM kernel, would you mind flashing Kooz kernel? If you have CM for a few days. I still testing AOKP so might be a while before i can flash.
The bottom of mine gets real hot after about 15 minutes of browsing on LTE. It did it right out of the box, and I'm on stock.
Stock ICS on my S3
I disabled LTE yet its still gets hot.
jebise101 said:
Nah not worried because i have extended warranty on my phone. Its just i like my electronics to function the way they should and when they don't i HAVE to fix them or i will loose my mind, plus its kinda annoying when hold it.
I know it needs a few charge cycles and installed CM earlier this week so its been at least 3 days, but still noticed the phone heating up. I installed AOKP today and will try cycling the battery a few times.
Pardon my ignorance but why would fixing permissions have anything to do with this? Also there is no negative effects to doing this? I don't see any as it wil just mark everything rwx-r--r-- or whatever the default is, but just want to confirm.
I was thinking it maybe the CM kernel, would you mind flashing Kooz kernel? If you have CM for a few days. I still testing AOKP so might be a while before i can flash.
Click to expand...
Click to collapse
That's what I was thinking it might be and no, I don't mind flashing the other kernel. As a matter of fact, I was wanting to try that myself but I couldn't figure out wich download I needed off the link that you just posted. Wich one should I download and flash with CM10? He's got several flashable kernels posted under the "Downloads" section. I just need to know wich one I need to use with CM10.
jebise101 said:
Nah not worried because i have extended warranty on my phone. Its just i like my electronics to function the way they should and when they don't i HAVE to fix them or i will loose my mind, plus its kinda annoying when hold it.
I know it needs a few charge cycles and installed CM earlier this week so its been at least 3 days, but still noticed the phone heating up. I installed AOKP today and will try cycling the battery a few times.
Pardon my ignorance but why would fixing permissions have anything to do with this? Also there is no negative effects to doing this? I don't see any as it wil just mark everything rwx-r--r-- or whatever the default is, but just want to confirm.
I was thinking it maybe the CM kernel, would you mind flashing Kooz kernel? If you have CM for a few days. I still testing AOKP so might be a while before i can flash.
Click to expand...
Click to collapse
Fixing permissions tends to remedy certain glitches on my end. I don't nearly have enough knowledge to tell you why though. However, there are certain aspects of this phone that will lead to heat production no matter what you do: lte chip; powerful dual core CPU, etc. Furthermore, aosp ROMs are not stable nor are they fully optimized for the phone at this point, this will also lead to more resources being spent, which ultimately results in faster heat production. If it really bothers you, stick to what works and flash a stock ROM.
Sent from my SGH-I747 using xda premium
RobbieL811 said:
That's what I was thinking it might be and no, I don't mind flashing the other kernel. As a matter of fact, I was wanting to try that myself but I couldn't figure out wich download I needed off the link that you just posted. Wich one should I download and flash with CM10? He's got several flashable kernels posted under the "Downloads" section. I just need to know wich one I need to use with CM10.
Click to expand...
Click to collapse
You need to flash one of the AOSP JB kernels since you are on CM10. I can't tell you which one because that depends on which nightly you have installed. I guess there was major code changes after the 14th.
IUH1991 said:
Fixing permissions tends to remedy certain glitches on my end. I don't nearly have enough knowledge to tell you why though. However, there are certain aspects of this phone that will lead to heat production no matter what you do: lte chip; powerful dual core CPU, etc. Furthermore, aosp ROMs are not stable nor are they fully optimized for the phone at this point, this will also lead to more resources being spent, which ultimately results in faster heat production. If it really bothers you, stick to what works and flash a stock ROM.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Yeah but it never did that with stock and its not a deal breaker i love AOKP no way am i flashing back to touchwiz. You know the ROM has been so stable that I expected everything to work but your right its not stable yet and some things are probably not optimized and that is the cause for the phone to heat up more then usual or kernel. Guess it can't hurt to make a nandroid and then fix permissions and if it goes south i have a backup:victory:
jebise101 said:
Yeah but it never did that with stock and its not a deal breaker i love AOKP no way am i flashing back to touchwiz. You know the ROM has been so stable that I expected everything to work but your right its not stable yet and some things are probably not optimized and that is the cause for the phone to heat up more then usual or kernel. Guess it can't hurt to make a nandroid and then fix permissions and if it goes south i have a backup:victory:
Click to expand...
Click to collapse
Yeah, to my understanding, chipsets are designed to withstand a heat threshold of about 60 degrees Celsius. It is extremely hard to get it to that temp at stock speeds, so I wouldn't worry too much about something going awry with your phone.
Sent from my SGH-I747 using xda premium
jebise101 said:
You need to flash one of the AOSP JB kernels since you are on CM10. I can't tell you which one because that depends on which nightly you have installed. I guess there was major code changes after the 14th.
Yeah but it never did that with stock and its not a deal breaker i love AOKP no way am i flashing back to touchwiz. You know the ROM has been so stable that I expected everything to work but your right its not stable yet and some things are probably not optimized and that is the cause for the phone to heat up more then usual or kernel. Guess it can't hurt to make a nandroid and then fix permissions and if it goes south i have a backup:victory:
Click to expand...
Click to collapse
Ok. Thanks. I'll figure it out.
Can a mod please delete this unintended post?
RobbieL811 said:
Ok. Thanks. I'll figure it out.
Click to expand...
Click to collapse
hehe keep me posted. I fixed permissions, we will see how it goes.
jebise101 said:
hehe keep me posted. I fixed permissions, we will see how it goes.
Click to expand...
Click to collapse
I've clean flashed the new nightly and task's kernel. My phone still seems to be running warm! I'll run it for about 24 hours or so and see how it does. IDK what the hell it could be. Is there other people running CM10 that are having this same problem? And by the way...Do you know of a fix for the MMS? My pictures that were taken vertically show up in an MMS horizontally and visa versa. Is there no way to fix that?
RobbieL811 said:
I've clean flashed the new nightly and task's kernel. My phone still seems to be running warm! I'll run it for about 24 hours or so and see how it does. IDK what the hell it could be. Is there other people running CM10 that are having this same problem? And by the way...Do you know of a fix for the MMS? My pictures that were taken vertically show up in an MMS horizontally and visa versa. Is there no way to fix that?
Click to expand...
Click to collapse
It seemed a bit better today, but then i been out all day and its been wet and cold so might not have noticed. Its not Task's kernel but rather Kooz but they do work together. Can you also keep an eye on battery life? his kernel is suppose to have amazing battery life and CM/AOKP for me have very bad battery life. Also make sure to cycle the battery at least 3 time.
NOTE: Battery cycling mean charging it to 100% and letting it die to 0% and repeating, this will calibrate the battery and maybe will help.
Just a recommendation for you to give AOKP a try. I always used CM, but CM had some bugs when i tried so i thought might as well give AOKP a try and its actually been solid and has more features then CM. Best part is the build in LED configuration for apps/notifications.
These devs make it so hard to choose, both are very good ROMS.
Yeah. That's a problem I have too. I can't decide which one I want. The KT 747 kernel has seemed to take care of my heat problems. I was cycling the battery anyways. Where can I get the AOKP ROM? Is it posted under original development? The 747 kernel also gave me some much better benchmark scores!
Edit - I see in ktweaker where you can change some voltages but I have NO clue about any of that! Any advice? I think there is a thread on here somewhere about it. I'll have to find it & read it I guess.
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
RobbieL811 said:
Yeah. That's a problem I have too. I can't decide which one I want. The KT 747 kernel has seemed to take care of my heat problems. I was cycling the battery anyways. Where can I get the AOKP ROM? Is it posted under original development? The 747 kernel also gave me some much better benchmark scores!
Edit - I see in ktweaker where you can change some voltages but I have NO clue about any of that! Any advice? I think there is a thread on here somewhere about it. I'll have to find it & read it I guess.
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
Click to expand...
Click to collapse
go into the ktweaker voltages then hit menu and you have an option to add or subtract 5-25 mv. Take away a bit and do a stress test if its good then try some more etc etc. You get the picture
Sent from my SGH-I747M using xda premium
thatsupnow said:
go into the ktweaker voltages then hit menu and you have an option to add or subtract 5-25 mv. Take away a bit and do a stress test if its good then try some more etc etc. You get the picture
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Yeah. But the lower I set my voltages, will that affect the speeds that my phone runs at? Idk how to word my question. I guess what I'm saying is, if I lower the voltage on my 1.5GHz setting will it make my benchmark lower?
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
RobbieL811 said:
Yeah. But the lower I set my voltages, will that affect the speeds that my phone runs at? Idk how to word my question. I guess what I'm saying is, if I lower the voltage on my 1.5GHz setting will it make my benchmark lower?
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
Click to expand...
Click to collapse
Pfft! You should know at this point in the game that benchmarks mean nothing, its all about real world performance. Basically I'd just start playing around its the only way to learn what works and what doesn't on your device! Cause afterall every device is different no 2 chips are the same, what works on one device might not work on another
Sent from my SGH-I747M using xda premium
Yeah. I know. I guess I didn't necessarily mean my benchmark. I guess I meant speed.
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
Related
CM6 is definitely great, I think without question it is a vast improvement.
The only issue I have is my battery life is ABSOLUTELY HORRIBLE. Could be the worst battery life I've had with any phone. But maybe that's just the EVO, with it's big screen and speedy processor. I underclock to 384 mhz sometimes but then the thing slows down and even freezes. I have 3 different batteries and they all perform about the same (not good.) Before I had a partial wake issue but that's gone, and battery life still stinks. I've also tried calibrating but nothing really seems to make it better.
I hear the snap thing is good for battery life but I everytime I open that thread I get a headache. I love this phone and am obsessed wtih it but that thread is a bit much even for me!
Can anyone give me a quick and dirty explaination of what snap is / how to use snap? Which kernel to flash? Some day I hope to digest that mammoth of a thread, but right now I'm too busy reading texts for college and Just want better battery life.
Thanks!
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
nyc_zx10 said:
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
Click to expand...
Click to collapse
Yeah, I tried System Panel but the things eating my battery were mostly system things, like Browser. I guess I could give it another go.
Why are Juice Defender reviews so bad? I've considered it before also, maybe will try playing with it again
snap 8.2 is the current release. you can try any of the kernels, but i would avoid the 7.0/7.1 SD Card implementations since that technology has been put on the back burner for a bit.
Snap allows you to you Overclock and Undervolt (aka: UV).
Overclocking of course is for speed and Undervolting may save battery.
all EVOs are not created equal. some like undervolting some do not. so snap is available in multiple flavors. each with a different UV floor. the lower the floor the more potential battery saving..but also the more chance for a random reboot or wifi/gps acting funny. remember UV retards the amount of power so things can act goofy. the different UV floors are 800mv - 925mv. for example...i use the 8.2_900 because it works well with my EVO. the 8.2_800 booted great but after a while started rebooting itself. 8.2_850 just hung at bootup. the 8.1 kernels didn't work for me at all. 7.3b1 was great.
HAVs is adaptive..so don't get stressed if your device fails to boot properly the first time. wipe the cache/dalvik and try again.
so download a few of the 8.2 kernels.
make your nandroid
begin trial and error (I'd suggest starting at 800, 850 then 900 to get a feel)
don't be afraid to wipe the Cache and Dalvik multiple times.
don't worry about the whole thread. just grab the last few pages and read the OP. then feel free to ask.
i also recommend setCPU. you can find some threads for SetCPU configurations to help. BUT....make sure SetCPU is disabled when flashing the new kernel. once you get a working kernel you can enable SetCPU...but during testing phase it will give you gray hair.
jmxp69 said:
Just a few quick thoughts on voltages/freqs after seeing a handful of discussion in the thread:
1) Every 8.2 kernel has voltages lower than stock. The default stock voltage @ 245 is something around 1050.
2) No real effort is made to UV at the top end. It's a little lower, but the objective at the highest CPU frequency is not to UV. Most of the benefit of UV comes at the low end of the scale when your phone is idle (most of the time). Less voltage = less draw.
3) nHAVS scales voltage at each step. There is a min.max voltage at every cpu frequency. This range is fairly small--50-75mv, but it enables HAVS to decide based on feedback from the CPU which one to apply. And the max at each step is lower than stock. So no matter how you slice it, even if you're running 925, you are undervolted. This becomes a question of how undervolted.
4) OC is not about undervolting, it's about overclocking. The differences is voltage vs. frequency. OC means we're increasing the CPU frequency beyond stock which is 998mhz in the case of Evo. If you move your SetCPU slider beyond 998mhz, you're overclocking.
The objective of overclocking is speed. The objective of undervolting is battery savings. Snap gives you both. We overclock when we increase the fequency with SetCPU. We undervolt automatically via nHAVS. As of this writing, UV is handled in the kernel, it happens most at the bottom end of the frequency scale.
I hope this helps clear up some of the questions. Great conversation by the way.
Click to expand...
Click to collapse
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Thank you Dragin!!!
That helps a lot! So once you have Snap setup at what you feel is "good" does your phone seem to perform as well as before you had it undervolted? Man, sounds like a pretty involved process - maybe I better wait until I can really sit down and play with it.
goodelyfe said:
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Click to expand...
Click to collapse
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
foueddyf said:
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I think he's talking about when ur figuring out the best setup
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
I had the same issue, left to stock with kingx.
Sent from my PC36100 using XDA App
nyc_zx10 said:
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do you know what in particular Juice is doing to give you better battery life? like what does Turn off certain things based on conditions or?
That is some good battery life.
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
nyc_zx10 said:
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Meh... see I really don't want to do those things. I can turn off data sync myself and just have gmail forward me a text message when I have an email. I just was hoping there was a way to get decent battery life without going back to the days of Winmo
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
berardi said:
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
Click to expand...
Click to collapse
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
DraginMagik said:
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
Click to expand...
Click to collapse
Thanks man, appreciate the breakdown.
You have inspired me, I'm going to bite the bullet and try this snap7.5_925 kernel. I'll report back my luck
I do enjoy this stuff, really - just right now it would be irresponsible for me to spend too much time on it. School comes first right now.
DraginMagik said:
... after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
Click to expand...
Click to collapse
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
loupy said:
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
Click to expand...
Click to collapse
Yeah dragin, don't hog those sweet settings! I'm enjoying Snap 7.6 and it seems to be helping out my battery life a bit, but I'd love to see your SetCPU details.
I've found that the issue for me is bluetooth. If I have it on constantly my battery will drain 10-15% per hour. With bluetooth off it's only draining 1%-2% per hour.
Seems like the bluetooth needs work on CM6 in order to have the efficiency that the other ROMs i've tried (Fresh and EViO) have. Nonetheless, I'm sticking with CM6 and just use the bluetooth when necessary.
I have the same issue with bluetooth on CM 6.0.0. I am running the stock kernel that comes with cyanogenmod, so this is definitely not a snap issue. There was a bug submitted about a month ago:
code.google.com/p/cyanogenmod/issues/detail?id=2136
I *really* hope this can get fixed for the 6.1 release, but it is currently listed with a low priority. I really love CM6, but basically making bluetooth unusable for more than a few hours really makes me struggle with the using this rom.
Why not the 7.6 with turbo...just wonderin
has anyone else experienced this? i have this happen to me quite a few times using bullet/synergy kernal
basically what happens is that my phone will always heat up and crash then it restarts itself..even when it's idle
i've used faux clock to keep my phone from ocing but this still seems to happen..
Try Fauxs kernels.. always stable....check your OC setting and UV settings...flash it and use at it's out of the box setting
Sent from my SGS2
Vinsane said:
Try Fauxs kernels.. always stable....check your OC setting and UV settings...flash it and use at it's out of the box setting
Sent from my SGS2
Click to expand...
Click to collapse
oc settings is set to keep the clocks at stock
i tried undervolting it by 12mv and my phone was ok, then i went a bit lower and my phone crashed again, not quite sure if i should try another custom kernel, i feel like im on the brink of bricking my phone
Yeah..not all chips are created equal...so keep it to where it's stable and you should be good. Flash Fauxs.. leave all the settings as it came and see how it does for you
Sent from my SGS2
Vinsane said:
Yeah..not all chips are created equal...so keep it to where it's stable and you should be good. Flash Fauxs.. leave all the settings as it came and see how it does for you
Sent from my SGS2
Click to expand...
Click to collapse
i dont think its actually a chip issue
my settings were
1.512ghz max 384mhz min
and
at screen off
540max
384 min
my phone heated up and crashed when i turned the screen offf..so it seems more like a software bug rather than hardware imo..
i think you misunderstood me lul. so here's the entire story
i flashed synergy a couple weeks back and had this issue, so i thought o well and went back to eaglesblood(which is pretty much stock everything)
then i decided to try jugs+bullet, it seemed fined until i went to sleep and wokeup with a phone that has its battery drained and is hot to the touch
now the settings were set to not overclock, so it doesnt seem like my chip is causing the issue
If your chip heats up enough to cause it to crash and reboot...that's not a good sign man..especially if you've tried different kernels and don't have crazy settings.
One more flash won't hurt right?
Maybe try a new combo... different rom and kernel?
Sent from my SGS2
Vinsane said:
If your chip heats up enough to cause it to crash and reboot...that's not a good sign man..especially if you've tried different kernels and don't have crazy settings.
One more flash won't hurt right?
Maybe try a new combo... different rom and kernel?
Sent from my SGS2
Click to expand...
Click to collapse
im on faux right now
it does sound bad, but its been fine when im on eaglesblood(stock kernel)
so im a bit confused all around
thing is, im playing gta 3 right now and its barely heated up, so it confuses me why it would heat up and crash/restart when its friggen idle..
Like some are saying try faux's kernal. I used to have the same problem when ocing my sgs and g2x everyone's phones are different but so far faux kernal is very stable
Sent from my SGH-T989 using xda premium
BowLow said:
Like some are saying try faux's kernal. I used to have the same problem when ocing my sgs and g2x everyone's phones are different but so far faux kernal is very stable
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
read up lul, im using it and it's been good so far
ya the faux kernel is doing really really well
on synergy/bullet i used to get under 4500 antutu score..
now im getting 6458 and im not even overclocking..
I unerstand this isn't what was asked, but I've never had heat issues, using the stock roms cleaned-up by myself after root. The new 2.3.6 is solid as well.
heinrich said:
I unerstand this isn't what was asked, but I've never had heat issues, using the stock roms cleaned-up by myself after root. The new 2.3.6 is solid as well.
Click to expand...
Click to collapse
i wasnt talking about the stock kernel, i was talking about synergy and bullet
Cool. Glad it worked out for you man
Hint - find his. 06 version with gpu Turbo.... freaking awesome
Sent from my SGS2
Vinsane said:
Cool. Glad it worked out for you man
Hint - find his. 06 version with gpu Turbo.... freaking awesome
Sent from my SGS2
Click to expand...
Click to collapse
This things plenty fast without overclocking, I'm in no overcompensation contest to get my benchmark scores higher lull
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
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.
There is something going on with my phone, Samsung Galaxy S3, V4.3 where occasionally, lately it has been once a day the power draw from the battery will spike as high as 2,000ma (2 amps). This last long enough to drop the charge 10 - 20% and creates excessive battery heat. It happens on charge or off charge. I have tried viewing the running processes with System Tuner and nothing shows up in the list using an excessive amount of CPU. Better Battery Staus also doesn't pinpoint the problem. I have most everything Greenified accept Google stuff of course and useful stuff like email, etc. I now believe it could be connected with GPS since I turned off the GPS I have not had another event other than a 800ma spikes that quickly go away. Need more time to confirm it is GPS related. Are there any programs that will log which applications are using GPS? Any other ideas what could be the problem? I don't understand why System Tuner doesn't show me which process is eating the battery? Can anyone point me in the right direction.
I thonk it may be the radio itself. I have recently noticed similar issues on mine but its usually when streaming videos. I rarely use gps so i cant speak on that right now.
If i have it plugged in while doing this, it gets hot enough to trigger a shutdown due to thermal event....it crashes!
DocHoliday77 said:
I thonk it may be the radio itself. I have recently noticed similar issues on mine but its usually when streaming videos. I rarely use gps so i cant speak on that right now.
If i have it plugged in while doing this, it gets hot enough to trigger a shutdown due to thermal event....it crashes!
Click to expand...
Click to collapse
Same here, I also noticed with System Tuner that several applications that normally use 1% or less of CPU seem to spike to 8 - 30%. This all seem very odd. Now I am wondering if the background radio steals CPU cycles and leaves no time for normal applications. Anyway, the issues are reduced with GPS off although the battery does get warm sometimes without any reason I can fine. I'll try streaming audio and see if it triggers.
I would be willing to try a different radio. My current software is Model Number SGH-T999, Android version 4.3, BaseBand version T999UVUENC2, Kernel 3.0.31-1962493, Build number JSS15J.T999UVUENC2.
Unfortunately, no other radio will work. You can try one just to be sure about it. It wont brick, but just wont function. Youll have unknown imei and baseband until you flash the NC2 modem back.
Im currently running my port of S3Rx 4.0, but ill flash back to NC2 in a couple if days to test more on mine. Im also using a case/housing not meant for the T999 so theres a good chance that is contributing to my problems though.
DocHoliday77 said:
Unfortunately, no other radio will work. You can try one just to be sure about it. It wont brick, but just wont function. Youll have unknown imei and baseband until you flash the NC2 modem back.
Im currently running my port of S3Rx 4.0, but ill flash back to NC2 in a couple if days to test more on mine. Im also using a case/housing not meant for the T999 so theres a good chance that is contributing to my problems though.
Click to expand...
Click to collapse
Okay, thank you for the replies. Please stop by if you learn anything new. Velis Auto Brightness is up to 64% CPU usage, grrr. I posted on developers forum maybe troubleshooting that will lead to a fix. The 2 amp spikes haven't occurred since I disabled GPS, so I am guess you are correct about the radio.
The problem returned so turning off GPS isn't a complete fix, seems to reduce the frequency is all. It looks like Android System is the problem. If I shut down pull the battery reboot the bad behaviour continues, only fix seems to wait it out. My next phone most likely will not be a sammy.
Im not really sure what to suggest at this point. I can say that what we are experiencing isnt typical though.
Out of curiosity, have you given any of the ported kk roms a try? I think my Sprint port is probably the most stable/bug free, but they are all good and ive had pretty good battery on each one compared stock. (Ive always had good battery life even on stock though, aside from a few recent issues that I believe are more my own fault). TMS3KK is a solid rom with very few issues. S3Rx 4.0 is as well, but ill be posting an update to it hopefully later today, so I cant say its really been thoroughly vetted yet. Still worth a look though, imo.
DocHoliday77 said:
Im not really sure what to suggest at this point. I can say that what we are experiencing isnt typical though.
Out of curiosity, have you given any of the ported kk roms a try? I think my Sprint port is probably the most stable/bug free, but they are all good and ive had pretty good battery on each one compared stock. (Ive always had good battery life even on stock though, aside from a few recent issues that I believe are more my own fault). TMS3KK is a solid rom with very few issues. S3Rx 4.0 is as well, but ill be posting an update to it hopefully later today, so I cant say its really been thoroughly vetted yet. Still worth a look though, imo.
Click to expand...
Click to collapse
No time to try a different ROM yet. I should have time the weekend after next. Thank you for all your suggestions.
I tried replacing the battery. After the first charge the phone lasted for 2 days before the battery dropped to 5%. It took 6 hours to charge back to 100%. No problems until later, it seems to dislike being unplugged moved to a new location and plugged in again. This appears to be when the problem occurs. I usually just leave the phone plugged in all the time. I'll test further with the power before I make up my mind. I think this will be the last Sammy phone for me?
Is it a non stock battery? I've always had issues with those reporting correctly.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Is it a non stock battery? I've always had issues with those reporting correctly.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Usually I would buy a non stock battery however since this phone lays next to me in bed to wake me in the mornings I am a little concerned with a fire so it is a Samsung battery from Samsung. Leaving it unplugged for a bit and plugging it back in didn't work stop the battery drain. There are no processes eating the battery according to System Tuner so got to change the ROM.
Should I try a ROM first or kernel or both? Could it be an Xposed module, thinking about turning all of those hacks off?
I just remembered, this only happens if the screen is on and the phone is plugged into the charger. And rebooting doesn't clear the problem.
I would start with a stock based ROM. If it were me I'd go full stock rooted. But yeah I'd ditch xposed for now. You might even try reflashing your current ROM, factory resetting and this time don't use any exposed mods. If it still has problems, then try a different ROM.
It wouldn't surprise me at all to find xposed was the culprit. Its really cool, and the dev is amazing, but I prefer not to use it at all. IMO, it's much better to have the mods coded into the ROM itself.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
I would start with a stock based ROM. If it were me I'd go full stock rooted. But yeah I'd ditch xposed for now. You might even try reflashing your current ROM, factory resetting and this time don't use any exposed mods. If it still has problems, then try a different ROM.
It wouldn't surprise me at all to find xposed was the culprit. Its really cool, and the dev is amazing, but I prefer not to use it at all. IMO, it's much better to have the mods coded into the ROM itself.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you Doc, will do so and report back here the results.
My phone does the same thing now. My phone never did this when I first got it a couple years ago. I use GPS a lot because son plays on a travel hockey team. I could drive 3 - 4 hours away with the phone on and plugged in using the GPS without any issues. Now, my phone gets so hot in about an hour of the same type of use and it shuts down.
I thought that maybe there was something wrong with the phone because of age but now I see it could be something different.
It very well could be age related, or it could be partially due to that too. But I'd do as I suggested above and run stock for a bit to test. If on a custom rom, and especially kernel, you could run into issues like that too.
If you have the same problem on stock, (and you're sure its not an app acting up), there's a very good possibility that its more of a hardware related issue.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
And it is not the battery. I can't load stock until next weekend, need my phone for work.
You can always use better battery stats to investigate while you use it normally. Let it log all wakelocks, including kernel wakelocks for a full cycle.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
You can always use better battery stats to investigate while you use it normally. Let it log all wakelocks, including kernel wakelocks for a full cycle.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Tried that, been there, odd thing is nothing shows there. I'm gonna reload with stock per your suggestion next weekend and if that doesn't work I'll try a custom kernel.
Try remove greenify app and see what happens. Cuz with my case the latest version (2.4.x.x) of greenify driving my phone nuts. That app used to be great.
I'm back. Loaded stock 4.3 ROM / kernel, radio is at newest versions, I am going to say the problem is gone. The battery heats up to about 32-33 degrees Celsius however the phone isn't hot like it is burning up so I believe the problem is like Doc suggested earlier with the radio. Which would explain why the process monitors never see any rouge application using to much CPU. So after some pondering, this doesn't stop a rouge application from using to much bandwidth and cooking the radio so to type. If I had to pin it down I am going to suggest it maybe one of these two applications: FCC speedtest and or Opensignal or some other application. Both of the listed applications periodically test the network bandwidth and report back to a central server. I suspect that this maybe trigger the heat problem from the extend radio usage. No proof at this time just conjecture.
I am considering jumping to an AOSP ROM to be free of the Samsung bloat, NOT CM, don't care for CM, does anyone have any good suggestions to try?