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
I thought I'd put this together given the amount of questions and apparent lack of knowledge on what you're getting yourself into with overclocking. While it's a one-click-wonder with SetCPU and JuiceDefender, it's not that simple when it comes to what it's actually doing to the phone.
The first thing you need to know is this:
All devices are not created equal!
Even when they come off the production line together they may not be capable of even getting close to each other with an overclock. This is down to numerous variables, the most important of which is the processor itself. Processors are manufactured in batches from something called a wafer (basically a big chunk of silicon), that batch is then tested to a maximum stable speed and then marketed at a slightly lower speed for the sake of rock solid stability. Dual/multicore processors may have a faulty core disabled and be marketed as something else (hence AMD's Tri-Core processors). This is the reason overclocking works, and the long and the short of it is just because Person A can get 1.3Ghz running stable, doesn't mean Person B can.
So, now we know that whingeing that my Desire can get 1300Mhz but yours crashes every time you go above 1100Mhz is irrelevant, we can move on to the risks. Overclocking is dangerous. That's not an exaggeration, so let me reiterate...
Overclocking is dangerous, You can potentially kill your phone stone dead.
But yet again it's not that simple. Yes, in very rare cases a processor will just go bang and give up, but most of the time other things will happen, behind the scenes, that you won't know about until it's too late.
The basic premise of overclocking is to get a faster processor clock speed. A small jump can probably be attained just by upping the speed itself and be perfectly stable. Going higher is where the problems start. If you start getting crashes/freezes/reboots then the next step is to increase the voltage to the processor to make it more stable, but more voltage means more heat, and excess heat is bad. This can either cook the processor as a whole or a group of transistors. This is more of a problem on a device like the Desire as where do you put the extra cooling?
Another problem is that more voltage can fry an IC track, and/or arc across to a track it shouldn't be on. This could do nothing, but it could also kill a single transistor on the processor or other chips in the device, or maybe multiple transistors and it can also lock them open or closed. This takes us back to random reboots, freezes, and crashes - but this time it can't be fixed.
Then theres a twist. Undervolting can also break things. A transistor is either on or off, and if it doesn't get enough power one of three things can happen - it can work fine, it can not work at all, or it can continually switch until it breaks (what an example? go and flick a light switch on and off until it stops - and it might not be the bulb that goes). If it decides not to work when other parts think it should, guess what happens.
So, bear this in mind when overclocking. If you start getting ANY issues test at stock speed. If you still have issues and/or you kill your phone, it's your own fault.
Mods - I've put this here as it's the place most people seem to ask about OCing, please move it if i'm wrong...
Nicely written and informative. Users must always take their own responsibility when trying to do something "out-of-spec" with their device. I didn't know undervolting could break things though.
It's far far less common and it's not the actual undervolting that causes the issue - it's the power requirements of the device. If you're unfortunate enough to have something keep tripping - it's kind of like when a PSU goes and keeps clicking, there's not quite enough power to flick to On permanently so it just ticks at you till you turn it off or it gives up completely. 9 times out of 10 you'd be fine, but theres always that chance.
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
My phone freezed several times a day with defrost. But no freez with MIUI/OpenDesire. I dont know why but Defrost §$%#s my phone
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
It can be that it is your ext3 partition if you have one...i had a user with freezes...and i did not know what it was...i say him...make all new...he flasht a original rom...root again with unrevoked...flasht my rom again and it was the same...freezes...so he formated the card...and maked a new ext3 and now he have no more problems with freezes
with kind regards..Alex
Good write up. Hopefully people will actually read this and understand the risks before they start pushing zip files with overclocked/undervolted kernels. Personally I've never overclocked any mobile device since I'm not comfortable with the risks that may lead to long term damages.
great job! thumbs up! vote for sticky or linking this in one of the stickys
i'm familiar with overclocking since i've been doing it to my PCs for years. i'm wondering if aosp roms push the phone harder or something than sense based ones?
reason i ask is i've tried a few aosp roms (open desire, defrost etc) and all the various kernels i've tried cause a reboot after a while - 30 mins, upto a few hours. now, i tried richard trips sense kernel and OCd with that no problems at all. very weird
p,s all Ocing was on the relatively small 1113mhz.
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Deshabilitado said:
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Click to expand...
Click to collapse
I cover this in the guide I wrote in general (which has been pushed down quite a ways) but anyways here goes another version.
Overclocking varies from device to device, even of the same model. Variances in tolerance is on a per chip basis, as long as they pass within a certain range they are sent out for production in devices. Overclocking in general is within means of the chip's abilities, if it isn't, you'll know it. Generally speaking, 1.4 GHz is perfectly fine on our devices. 1.5 GHz is also usually ok, but is the upper end of what the Tegra2 can usually tolerate. Few an go past 1.58 GHz, my old G2x's tegra2 could hit 1.7 GHz,but that's well beyond "normal" range.
Overclocking a device is the same as overclocking a PC, you need to be careful with it. Don't just ramp it to 65% overclock and expect it to run fine. Every chip is different. Do it in steps, and test each step before moving on. Test it in normal usage, test it in heavy usage, gaming, etc.
An overclocked device will certainly run hotter then normal, it's running faster, drawing more power, and that creates a hotter running core, no way around it. Keeping in mind there is no airflow in these things, that makes the biggest enemy to CPUs even more dangerous.Does it run so hot that it can shorten component life? Sure it can. Will you still have the device when it happens? I doubt it. Likely, we'll be on Tegra5 before it even begins to show signs of stress.
One of the nice things, though, is our CPUs range so much in speed according to load that just because your Max is 1.5 GHz, it doesn't always run there. Most times, it won't even be in the overclocked speeds. Does it run faster? Sure does. Benchmarks will raise nicely, and games that maybe got choppy before will smooth out, movies that couldn't play well will be fluid, the heavens will align, mankind will discover world peace and I'll win the lottery.
All that being said, I don't usually overclock, in fact I tend to underclock a little to 800MHz. Its usually sufficient to do normal tablet stuff, and I adjust the speed according to what I require. If my movie is lagging, I'll bump it up until it smooths out. Same for a game if it needs it.
In the end, its all personal choice, really. Just because you CAN overclock, doesn't mean you NEED to. IMO a well tuned governor will give as good a result as overclocking in normal usage, and a good I/O Scheduler will also help alot, without adding anymore heat or stress to your device.
TL;DNR:
Overclocking is fun. It causes more heat. It likely won't explode within the time you own it. Or your children. Your battery will suck.
thanks pio for the answer, thats what i needed to read, cuz usually when u talk about OC its like "yeah dude, OC its "tha greeeeeat doi it dude" or something like "dont do it!!! u will decrease your tablet life" and yes, i know that devices are way to diferent even if they are the same model, and also im agree with u, governors and I/O works better than OC but we dont have many for our device, i miss the smartass v2 governor,or the brazzilianwax too, but well, hope someone can port it for us someday.
I'm running SOA B2 with their kernel, in performance setting it allows me to go up to a maximum of 1836 MHz, is this safe?
Will battery life worsen?
Should I change the governor or I/O scheduler?
If you know what any of it means, it'd probably be best to stay away from it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have many app ideas, but don't have the skill or the time to learn how to make an app. if you would like to know an idea and attempt to make one, just message me.
Listen arianaLarge, don't bother replying if all you are gonna do is talk ****. Help the rookie out. This is a place for learning and contributing, its a community, it does not belong to you.
Having said that,.....you will lose stability and battery life if you go that high.
You will gain considerable performance but for what really?
Do you need it, probably not.
Personally I underclock to 1.18 for 80% of the day during the week, and run at 1.67ghz all day on the weekends. Its very easy to kick it up higher if you need the performance boost.
Also educate yourself on the various governors to better manage your CPU draw.
Google is your friend and the greatest tool you have for information.
Use tricksterMod or system tuner in the play store to manage CPU states and governors, both are free.
Both are great
there is no spoon.....
I never touch my CPU settings and use stock rom kernels....I've never seen a significant reason to bother with changing things. And I've never had hardly any of the problems I read in the rom dev threads.
Just my two cents.
Sent from my cell phone telephone....
Make sure you don't click the save on reboot button (or whatever it's called) because you may end up in a boot loop until you can flash some recovery to reset the setting. I don't think you're at too much of a risk, but the phone may not run stable and will likely shut down if it's pushed too hard. That's what I think.
Yes the battery life will be shorter. It may not be drastic unless you are constantly using it because the CPU speed will go back down when you idle.
Hello everyone! I am very, very happy because i bought a Nexus 7 2013 a week ago. That same night I got home from the shop I knew it was getting root permissions. So i did the rooting method with WugFreshes toolkit and it worked like a dream I must admit. TWRP and Superuser installed in a flash.
After root permissions the fun started - Custom Rom's, Mods, Tweaks you name it. I am currently using Stock Kitkat 4.4 ROM with many tweaks:
PureGraphic HD
PurePeformances
AwesomeBeats
PureAudio
I have the Franco Kernel and it's great. I have had no issues what so ever so far. It's smooth, fast and responsive. Games run extraordinary fast, I can amp up the graphics without to much frame drops, this includes games like GTA SA, GTA VC, Modern Combat 4 and N64/PS1 Emulators (and yes i own the roms :highfive. Back to the Kernel. All Wireless adapters are working (bluetooth, wifi, nfc etc), and wifi seems faster. Battery doesn't drain very fast at all, even with intensive load. But here is where my question actually is ...
I do understand that this question has been answered somewhere else in the Nexus 7 2013 forum, however can someone tell me my question in more detail? Thanks. :good:
Q. My question is, between what cpu temperatures is safe for my nexus 7 2013 to play intensive games at (etc emualtors, gta series, MC4)? What temperatures should i be alerted at. I am currently running GTA Sandreas and emulators at around 50-65 Degrese celcius (yes that's right celcius us auzzies use the metric system :silly: . )
Also if i overclocked it to 1.7GHZ then what would a stable temp be while idling and heavy load? (thanks!)
(last minute edit... Also what CPU is really used in this? People say it's an undercloked s4 pro or something? So if overcloked back to 1.7GHZ it'll be fine? Right?...)
Other information consist of:
.All the mods i said i have, stated earlier
.Franco Kernal
.Wireless devices faster tweaks
.Use 4x MSSA
.Warn at 65 Degrees Celcius
.Other small mods i can not think of...
.Stock GPU & CPU clock speeds
If anyone can ask my question A.S.A.P it would be greatly appreciated, i am currently new to XDA but not the the Android OS. And to all of you whom think Android is a terrible OS go get one of the most biggest fails since Apple Newton the iPad.
P.S The XDA forums is great, and everyone on here deserves a good old beer. If this thread violates any T&C please go right ahead and delete it. Thanks so much,
" Be nice to nerds, because chances are you will probably work for one someday" - Bill Gates.
My devices and devices i have had:
.Samsung Galaxy Ace S5830
.Galaxy S2 I900T White
.Galaxy S2 I900T Black
.Sony Xperia Z
.Pendo Pad 7
.Softwner Tablet 7"
.Huawei Acend y201
.Galaxy Nexus
.Nexus 7 2013
How come nobody has said nothing to this question?
Btw, my cpu hit 91º C this morning while I was playing nova 3 and I was using an overlay to see my gpu frequencies and usage. I think is too much.
CheyTac-12 said:
How come nobody has said nothing to this question?
Btw, my cpu hit 91º C this morning while I was playing nova 3 and I was using an overlay to see my gpu frequencies and usage. I think is too much.
Click to expand...
Click to collapse
I personally wouldn't worry about cpu temp that much. All the developers of custom kernels will set the thermal limits to whatever they think is appropriate. A much bigger concern than the cpu temp is heat being conducted to the battery. I would make a point of keeping the battery below 120F and I personally don't want to see over 110F (around 45C).
wantabe said:
I personally wouldn't worry about cpu temp that much. All the developers of custom kernels will set the thermal limits to whatever they think is appropriate. A much bigger concern than the cpu temp is heat being conducted to the battery. I would make a point of keeping the battery below 120F and I personally don't want to see over 110F (around 45C).
Click to expand...
Click to collapse
The overlay thing I was talking about earlier was the cause for that cpu temp, it used like 2 entire cores to function, without it, temps are more stable, can you believe that the tablet actually kinda burned my fingers if I pressed too hard? That's insane.
Now, I understand that the battery's temperature is something important, so you don't ruin your battery lifespan, but how come cpu temps don't matter as much as battery's does? What's the max temp for these devices?
CheyTac-12 said:
The overlay thing I was talking about earlier was the cause for that cpu temp, it used like 2 entire cores to function, without it, temps are more stable, can you believe that the tablet actually kinda burned my fingers if I pressed too hard? That's insane.
Now, I understand that the battery's temperature is something important, so you don't ruin your battery lifespan, but how come cpu temps don't matter as much as battery's does? What's the max temp for these devices?
Click to expand...
Click to collapse
I'm going to "guess" and say somewhere around 100C for the cpu. Just a guess. 60C for the battery would absolutely be bad news. 50C would make me nervous. Also the cpu will start to get throttled (underclocked) once it gets up to a certain temp, And once it reaches the max temp the cpu will get shut down and you will have to wait for it to cool down before it will boot back up. I would worry about the heat affecting the motherboard and the components on that before I would worry about heat damaging the cpu.
XxAuzzi3L3g3ndx said:
Hello everyone! I am very, very happy because i bought a Nexus 7 2013 a week ago. That same night I got home from the shop I knew it was getting root permissions. So i did the rooting method with WugFreshes toolkit and it worked like a dream I must admit. TWRP and Superuser installed in a flash.
After root permissions the fun started - Custom Rom's, Mods, Tweaks you name it. I am currently using Stock Kitkat 4.4 ROM with many tweaks:
PureGraphic HD
PurePeformances
AwesomeBeats
PureAudio
I have the Franco Kernel and it's great. I have had no issues what so ever so far. It's smooth, fast and responsive. Games run extraordinary fast, I can amp up the graphics without to much frame drops, this includes games like GTA SA, GTA VC, Modern Combat 4 and N64/PS1 Emulators (and yes i own the roms :highfive. Back to the Kernel. All Wireless adapters are working (bluetooth, wifi, nfc etc), and wifi seems faster. Battery doesn't drain very fast at all, even with intensive load. But here is where my question actually is ...
I do understand that this question has been answered somewhere else in the Nexus 7 2013 forum, however can someone tell me my question in more detail? Thanks. :good:
Q. My question is, between what cpu temperatures is safe for my nexus 7 2013 to play intensive games at (etc emualtors, gta series, MC4)? What temperatures should i be alerted at. I am currently running GTA Sandreas and emulators at around 50-65 Degrese celcius (yes that's right celcius us auzzies use the metric system :silly: . )
Also if i overclocked it to 1.7GHZ then what would a stable temp be while idling and heavy load? (thanks!)
(last minute edit... Also what CPU is really used in this? People say it's an undercloked s4 pro or something? So if overcloked back to 1.7GHZ it'll be fine? Right?...)
Other information consist of:
.All the mods i said i have, stated earlier
.Franco Kernal
.Wireless devices faster tweaks
.Use 4x MSSA
.Warn at 65 Degrees Celcius
.Other small mods i can not think of...
.Stock GPU & CPU clock speeds
If anyone can ask my question A.S.A.P it would be greatly appreciated, i am currently new to XDA but not the the Android OS. And to all of you whom think Android is a terrible OS go get one of the most biggest fails since Apple Newton the iPad.
P.S The XDA forums is great, and everyone on here deserves a good old beer. If this thread violates any T&C please go right ahead and delete it. Thanks so much,
" Be nice to nerds, because chances are you will probably work for one someday" - Bill Gates.
My devices and devices i have had:
.Samsung Galaxy Ace S5830
.Galaxy S2 I900T White
.Galaxy S2 I900T Black
.Sony Xperia Z
.Pendo Pad 7
.Softwner Tablet 7"
.Huawei Acend y201
.Galaxy Nexus
.Nexus 7 2013
Click to expand...
Click to collapse
Theorically speaking, the safe working temperatures would be the where the thermal limit is which is around 105ºC.
However, it doesn't work like this because heat spreads to other components and more importantly, it spreads to the battery and we all know batteries don't like hot temperatures since it drastically reduces their life span and charge capability.
On practice, I would say keeping your CPU below 70ºC which will result in a colder battery aswell is the sweet spot.
On the Overclock matter, I have mine at 1900'ish Mhz and my GPU is at 490'ish Mhz and I haven't experienced any abnormal temperatures while runing benchmarks. Infact, the temps were kept below 50ºC which is more than fine.
wantabe said:
I'm going to "guess" and say somewhere around 100C for the cpu. Just a guess. 60C for the battery would absolutely be bad news. 50C would make me nervous. Also the cpu will start to get throttled (underclocked) once it gets up to a certain temp, And once it reaches the max temp the cpu will get shut down and you will have to wait for it to cool down before it will boot back up. I would worry about the heat affecting the motherboard and the components on that before I would worry about heat damaging the cpu.
Click to expand...
Click to collapse
I think the battery burns like hell when you're playing and charging it at the same time, am I right? I wonder, if the cpu and gpu are underload, the battery will drain quickly, does this mean that this produces more heat to the battery? How does that work.
CheyTac-12 said:
The overlay thing I was talking about earlier was the cause for that cpu temp, it used like 2 entire cores to function, without it, temps are more stable, can you believe that the tablet actually kinda burned my fingers if I pressed too hard? That's insane.
Now, I understand that the battery's temperature is something important, so you don't ruin your battery lifespan, but how come cpu temps don't matter as much as battery's does? What's the max temp for these devices?
Click to expand...
Click to collapse
Thanks m8. I don't have to worrie about it anymore... The Nexus came to a screen smashing end...