Related
Most of what is below is still accurate, but see this post for links to the kernel download and important infoshttp://forum.xda-developers.com/showpost.php?p=12397646&postcount=580
1-18-11
v.4 - GB’s Impressive Sounding Name Kernel
* As always, many, many thanks to xcaliburinhand.
* Consolidating Steam and Voodoo/CWM kernels into one thread. The two kernels are the same except for recovery, and jfs support in the Steam kernel.
* Started using a proper changelog
* Implemented Impressive Sounding Name Technology AND Dynamic Naming Technology patches; next update to include Dramatic Use of Imagery, with possible Reference to Mythical Creatures patch.
* Cherry-picked some recent commits not included in JPX source. (Will post source this evening, I hadn’t planned on releasing this just yet, but it seems as though it’s already being packaged into a ROM so might as well, right?)
* CONFIG_ARM_THUMBEE=y, enables ThumbEE processor mode, should give some minor JIT performance improvement.
* config_hz=100. With this value, kernel hz = user hz which eliminates HZ <--> USER_HZ conversions. It should also slightly increase battery life without affecting performance.
* Increased default overclock to 1280 MHz. Your may want to revise your undervolt settings, 1280MHz runs at the same voltage as 1200MHz did/does, so you **may** not be able to undervolt as much at 1280. (Yes, I previously said I wouldn’t go past 1200MHz, but, I feel ok going to 1280 since the voltage hasn’t changed and it’s still well below the max vdd_arm.) Use voltage control or setCPU to limit clock speed if you don’t want to use this. Delete your Voltage Control boot settings before booting this kernel. I’m currently using Voltage Control 3.0a.
* Added Voodoo Sound. I hadn’t really planned on it but there were a lot of requests for it.
* Removed i9000 splash screen and replaced with an old familiar one.
* Want lower screen brightness? I know Hardcore did tinkering with the kernel source to do this, but I really like Screen Filter, it even has a Tasker plugin.
* From previous versions: Backlightnotification 2.3, Voodoo color/video fixes re-enabled against my better judgment and even though single-blind testers couldn't tell me which kernels had it and which did not. .
Downloads of v.4 - The file you want is something like rGB-v.4-011811-XXXXX.zip/tar
By clicking any of these links, you agree to flash delete your Dalvik cache and remove any oc/uv boot settings you have before booting. v.4 ClockworkMod zip at the bottom of this post, tar files of Voodoo5/CWM and Steam below for those of you who like to use Odin.
tar of v.4 with Voodoo5 & CWM recovery
tar of v.4 with Steam recovery
Credits
Xcaliburinhand, supercurio, raspdeep, SztupY, sorry if I forgot anyone else.
Stuff I wrote a while ago and may or may not be accurate any more.
1-6-11
This seems to be stable again. Started over from scratch and added in BLN 2.3. Everyone who was affected by charging problems with the previous kernels has not had a shutdown over the last two days of testing. Hopefully we're good again.
1-4-11
Closed testing on newer kernels until I'm fairly confident the issue is resolved again. I had still been getting intermittent reports of charger instability from the reoriented-balls-1-3-11-ocuv-bln23.zip (#47) kernel. Anyone affected by this please switch back to the 'f' builds below, which is the last known rock solid (I think) version.
-----------------------------------------------------------------------------------------------
This kernel is fast, and this kernel is stable. It's overclocked by default to 1.2GHz, but if you don't want to overclock at all, just install either setCPU or download xan's app which I have attached to this post and set the max clock speed to 1.0GHz. This kernel supports init.d scripts, so you have save your settings and have them load at boot.
1100-1200+ Quadrant score on RFS at 1GHz. 1500-1700+ on /data, /dbdata, and /cache on ext4. ~14.1 Linpack at 1GHz. Compare that to any other kernel available here at the same speed and I think you'll see this one comes out on top. I'm not doing this for donations, I just want to my experience with the phone as good as possible. Since this is a Voodoo 5 kernel, you can also make /system ext4 as well for an even smoother experience. This kernel has great battery life and is very stable as well. And when I say stable, I mean, you can use the phone however you want to, you don't have to do any workarounds to keep it from freezing. (edit - as long as you're using one of the build f kernels it seems...) Although, as always, if you aren't 100% satisfied with any of my products, I will give you a full refund.
What this kernel is -
Kernel for 2.2.1 ROMs, (may work on 2.2, but I haven't personally tested it), built from JPX source, with Supercurio's Voodoo 5, overclocked by default to 1.2GHz with raspdeep's code, and Neldar's backlight notification enabled, and re-oriented with xcaliburinhand's code. The undervolting code has been fixed to keep your phone from dying while charging. I'll not be supporting anything beyond 1.2GHz. I hardly use 1.2GHz myself, and from what I've read, many users (but obviously not all) have stability issues with anything much beyond that. This post from one of the senior Android engineers at Google also struck a nerve with me, and is also part of the reason I'll not support anything past 1.2GHz. Samsung actually wrote most of the code for 1.2GHz into the kernel source but had it commented out, so I don't have a problem providing software that will allow users to push it to that level.
Again, for voltage control, use xan's app. I've attached an older version of the app as I'm not sure if the newer one is backwards compatible with the 'older' methods of power management.
Also, standard disclaimers about how if this blows up your phone or tells your girlfriend she's getting fat, it's not my fault. I've had this kernel on my phone for a couple days, so none of that should happen.
How to install - Either flash in ClockworkMod, or use Neldar's really awesome kernel flashing app.
gb-reorient-12-23-build-f.zip is a zip tarred zImage. Unzip, then flash the tar with Odin, or extract the zImage and flash it with Heimdall or Neldar's kernel flashing app.
gb-reorient-fixed-ocuv-f-cwm.zip is a ClockworkMod flashable kernel.
Some thoughts on undervolting
The whole point of undervolting is to safely do the same amount of work with your CPU while using less energy (ie more battery life). Your phone is idle most of the time, so you can the most from undervolting lower frequencies more. Undervolting is safe WHEN you find the settings that work for your phone. Generally, -75mV seems to be stable for everyone. If you want to push it further, go ahead, but realize that if you push it too far, you phone will freeze, and you'll have to pull the battery. Relatively harmless, but, be aware it can happen. Personally, my phone is perfectly stable at the following settings (from 100MHz to 1000MHz) -125mV, -100mV, -100mV, -100mV, -75mV. These settings may not work for your phone. You might find that you can get by with undervolting a little more, but your system will freeze randomly, so if that happens, don't undervolt as aggresively. So, for example, I found that I can usually get by with -150, -125, -125, -125, -100, but every once in a while the phone will freeze up. And since I want a stable system, I've backed down from that. I can't tell you what to do though, but keep in mind that undervolting too much may lead to system instability.
- If you still want to try to find a oc/uv kernel which works for you, don't undervolt at all and tell me if it still happens with kernel #7 (12-23 build from my other thread). As far as I know, no one has had an issue with charger instability on that kernel. If it does still happen, I need to know the kernel version # and for good measure, the production code under your battery (can someone tell me what the name for this is again, I don't feel like shutting off my phone to check), it will be a number like 08.10, 10.10, etc.
- If even with the 12/23 build f kernels and not undervolting at all, you're still get shutdowns when charging, you probably want to get a different kernel. If you insist upon using that one anyway, try charging via USB instead of the wall outlet, it seemed to happen less frequently on older kernels, and I haven't had a charge death in weeks now, so, I'm good at least.
- See if your phone is one of the ones being recalled. If your phone is under recall and these don't work for you, I'm not sure what else I can do.
- These fixes work for me and a lot other people who had the same problem with other oc/uv kernels. Like I said, we're running these out of spec, so a few unlucky souls might not have phones that can handle this. Or maybe some of these kernels have been sprinkled with pixie dust and others haven't. If you find a different kernel that works for you by all means use it. It's all about choice people.
Thanks. Going to try it now.
I flashed 'em at 94%, so we'll see.
But FWIW- I think I've had MAYBE 2 charge deaths when I was on perception. But I was using Setiron's kernels, so I dunno...
I'll report back in a bit.. gonna let it over-charge for a bit and see what happens.
Darky 7.0.1 with your kernel and 100% battery power for 2.5 hours plugged in to the wall and no power off yet. Hopefully this is the fix, I am tired of leaving my computer on all night to charge on usb
thank you so much for this...been looking for something exactly like this, and seems sleep death is gone
darky 7.0.1 here also.
I had it charge around an hr and a half past 100% and no death!
So we'll see how it does overnight
I'll try it out and let you know how it goes, i charge by ac overnight so I should have the results of it to you by morning I'm using it with Assonance 5.2 by the way.
Well no charge death for me last night...
Sent from my GT-I9000 using XDA App
Absolutely no problem, left on ac all night with an undervolt and everything. Great job with this, it made oc/uv usable for me.
Doc's 6.1.3 + your kernel = 100% joy
I found your thread last night after a long and happy Christmas day with the family. Followed your instructions to the letter. Charged overnight from 45% and woke up to find the phone operating fine. This might be the answer to all our prayers!! Thank you so much!
Runs great with eugenes ginger clone. Slightly better benchmarks than other rom/kernel combos. I peak out at 1.3ghz so 1.2 seems like a good medium. One request though is to look into changing the divider for the gpu. I know we don't need it but its good for bragging. Unhelpful had this and I could set the gpu down to 166.750 For lower clocks to save battery and up to 222.334 (stable) for benchmarks. I never tried other clocks so I don't know if it would work on other settings. It depends on how his code works. but it seems by my math the gpu is divided off a 2000 or 2001mhz frequency. There is a margin of error I guess. and stock is divided by 10. In unhelpfuls code it is divided by 9 (222.334) default but could be set to 10 or 12. If we bump that up to 15 or 20 we might reduce battery consumtion with a gpu clock at 133 or even 100mhz. Id also like to try the divider at 8 for 250mhz. Im curious as to how that would benchmark if its stable.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Ive been charging since 2pm yesterday and its still on. I think you got the fix
No problems here charging overnight. For those who care about quadrant scores, mine was about 250 points higher than the other 1.2ghz kernel I was using.
I get better quadrant scores too vs.my setiron 1.47 1200 kernel. I don't know if it's due to this kernel, but for some reason I'm getting much better battery life since flashing it.
opcow said:
I get better quadrant scores too vs.my setiron 1.47 1200 kernel. I don't know if it's due to this kernel, but for some reason I'm getting much better battery life since flashing it.
Click to expand...
Click to collapse
Same here, battery life seems better..I've noticed it not draining so quickly, im at 85% when usually id be at 50-60%
Sent from my Captivate
I've found Darky's 7.01 works best on my phone, could it be true this makes it run faster? Do I need to have full charge or can i flash this at any battery level?
I didn't look at the actual quadrant score. But my fps is on average about 2-3 greater. Similar to running at 1300 on other kernels. Battery life is much improved over the kernel in eugenes ginger clone rom.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I just flashed it over SetiroN 1.5.6 and can see a speed difference already. 1200 O/C is perfect, I really like the kernel. Working great on Darkys 7.0.1
I too just installed over Darky's 7.0.1, bit more speed is noticable but i mainly did it for the possibility of better battery because right now thats all i am after.
i just installed but i want some more about voltage control
how can i modified that option?
thx a lot!
Helloooooo community!
I have a question...
I'm using HD2 with nand android and the rom
MDJ's CyanogenMod 7 v. 2.6
I installed the SetCPU and I managed to OC my device @ 1536MHz
I stess tested and it is stable, plus I'm using it for 2 days now!
stock temps after stress test: 33c
OC temps after stress test: 35-37c
My question is, is it safe to leave it as it is?
Cause according to temps, I don't think I have problem...
Also my profile is "On Demand"
Max: 1536MHz
Min: 245MHz
Thanks!
Hi,
From what I understand, on demand will not OC your CPU to 1.5 ghz, but use the CPU according to the performance it requires. If you use really intensive apps, CPU *might* go to 1.5 ghz, but it really just raises about as high as what's being used. I wouldn't recommend 1.5 ghz OC on your phone for a long term use. You never know what might happen.
Alot of people do it though, but my phone isn't stable at 1.2ghz so I'm not one of them.
After reading through the Thread for the Pre Release of FuguMod Ultra in the development section of this forum I thought I would post some info up for people who are wondering why it doesn't work with their phone, and just some general info on overclocking.
- First off, not all phones will be able to run at 1366MHz. Every CPU made has a range of freuqencies it will work at, and it is different for every single one. So some may be able to handle 1366MHz and above, others may max out at 900MHz. If you are getting black screens, freezes, or random behaviour, then your CPU doesn't like the frequency you have it at, try a lower frequency.
- Always keep an eye on the temp of the CPU when testing overclocking, if the CPU gets too hot, and fail safes don't work, there is a chance you could fry your CPU.
- With the FuguMod Ultra kernel, you must also be aware that gpu bus frequencies have been changed, so if your phone is not happy with that it will black screen. (as bus speeds are like cpu speeds, every different device can handle different clock speeds)
- plls values have been changed, and these may cause problems on your phone.
So if you want to have a go at overclocking your phone, back it up, and then give it a go. Select a frequency, and test with something pretty cpu intensive (3d game, multiple quadrant passes) and see if there are any bugs/overheating during a 15min time period. If you notice any problems/too much heat, try a lower frequency, and try again. And if for some reason your phone doesn't like the kernel, you can reflash with your previous kernel or a new ROM as you have already backed up your data.
If you have any other questions about overclocking, feel free to post here and I will try my best to answer them.
--- Samsung G3, InDroid 4.3, FuguMod 2.4 B3 800MHz ---
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
dilzo said:
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
The battery temp is a good representation of how hot the processor is getting as it is right next to the battery (only a thin sheet of metal seperating it) If the battery rises in temperature by a few degrees, then you can summize that the cpu is probably getting a few degrees hotter than that. I really wouldn't recommend letting the battery get above 55degrees (celcius) as this means the CPU may be getting up close to 65degrees (celcius) which is a very bad thing.
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
marcellusbe said:
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
Click to expand...
Click to collapse
Yes, Very true!!
Must also say, Your kernels are pretty legendary! Waiting patiently for the offical release of your FuguMod Ultra
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Piyush Rawal said:
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Click to expand...
Click to collapse
How have you got your phone set up? i.e. what ROM are you using etc.
I am using stock jpq with app2sd, swap, zipalign, ramhack and stuff. Setcpu is installed with default min/max freakquency, No profiles in use and undervolt a bit.
Ok,
This may be an issue caused by XXJPQ, as it is a new release there may be some sort of conflict. Have you tried asking if anyone else has this issue in this thread? http://forum.xda-developers.com/showthread.php?t=1132697
I haven't played around with JPQ yet so don't know what the bugs are yet.
Also, are you running a stock kernel? Have you confirmed that the phone has been rooted properly as well?
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Piyush Rawal said:
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Click to expand...
Click to collapse
Ok cool, I'll report the bug to the developer so that he can have a look into it. Thanks for testing and proving to the kernel.
Little bit of info some might find helpful. After some recent testing, I have found that some people might experience a black screen freeze when phone is in standby for a while with 83MHz min setting and on demand governor. I am not sure of the exact reason for this, whether it is a bug, or that the processor just doesn't like going that low for extended periods of time. If you experience this type of error, just hard reset the phone then open setcpu after phone has loaded and change the "standby" profile minimum to at least the next step up on the slider. Personally I use 223 setting as it provides a smoother lock screen animation, and no significant difference in battery drain.
Sent from my super smooth GT-I5800 using XDA App
Hi
Sorry cant post in the development thread since i just joined.
Using TS1700-GPUOC-4.1.2-mr1-fr-ALPHA12 with CM10 causes Nexus 7 to Freeze/crash and reboot when you remove a USB pen drive or 2.5 harddrive that is connected with a OTG cable. It happens if you do a dismount from settings/storage or just pull the cable OTG cable out.
Otherwise its a very good kernel for Nexus 7.
/cazrack
cazrack said:
Hi
Sorry cant post in the development thread since i just joined.
Using TS1700-GPUOC-4.1.2-mr1-fr-ALPHA12 with CM10 causes Nexus 7 to Freeze/crash and reboot when you remove a USB pen drive or 2.5 harddrive that is connected with a OTG cable. It happens if you do a dismount from settings/storage or just pull the cable OTG cable out.
Otherwise its a very good kernel for Nexus 7.
/cazrack
Click to expand...
Click to collapse
Finally! I could Kiss you!! I wont don't worry.... at least however a manly high five will do. I am having this issue since using the Trinity Kernel and like an idiot never once though it was the Kernel. Strange how the units will still turn off even if you just plug and unplug in the OTG cable with nothing plugged into the cable itself. So we think it is the Kernel then?
Casanub said:
Finally! I could Kiss you!! I wont don't worry.... at least however a manly high five will do. I am having this issue since using the Trinity Kernel and like an idiot never once though it was the Kernel. Strange how the units will still turn off even if you just plug and unplug in the OTG cable with nothing plugged into the cable itself. So we think it is the Kernel then?
Click to expand...
Click to collapse
Yes, 100% certain its kernel related.
When you run CM10 updater from inside CM10 and a new nightly build gets installed it removes Trinity kernel and install the default CM10 kernel and that makes the problem go away.
After you flash Trinity kernel back you get the freeze and crash/reboot issue again.
If you use this Kernel, please contact morfic. check his site below for email and other contact information.
derkernel.com
(sorry no real link, just joined.)
/cazrack
cazrack said:
Yes, 100% certain its kernel related.
When you run CM10 updater from inside CM10 and a new nightly build gets installed it removes Trinity kernel and install the default CM10 kernel and that makes the problem go away.
After you flash Trinity kernel back you get the freeze and crash/reboot issue again.
If you use this Kernel, please contact morfic. check his site below for email and other contact information.
derkernel.com
(sorry no real link, just joined.)
/cazrack
Click to expand...
Click to collapse
Thank you Cazrack. I will email him now, I can imagine he will be inundated with emails
Another two quick questions "sorry" with Trinity, do you use setcpu to overclock or do you find the kernel gives you all the speed you need? secondly have you had the issue of the unit turning off on an overnight charge? I do not do this normally but I fell asleep with it plugged in and found in the morning it was turned off, when I turned it on it was at 100% so thought is might have turned off as a safety feature but just wondering if you experienced this or heard of it happening?
Thank you again for you help.
The same thing happens to me with the Trinity kernel but it also happens with LeanKernel for 4.2. It did not happen with LeanKernel for 4.1.2, so I don't think it is just a kernel only issue. It doesn't happen on the stock kernel, M-Kernel+, or Franco r30.
O2Blevel said:
The same thing happens to me with the Trinity kernel but it also happens with LeanKernel for 4.2. It did not happen with LeanKernel for 4.1.2, so I don't think it is just a kernel only issue. It doesn't happen on the stock kernel, M-Kernel+, or Franco r30.
Click to expand...
Click to collapse
Cheers for the response, always good to know its not the hardware . Defo a Kernel issue, I have emailed derkernel.com, I am sure we should have a fix soon, otherwise it aint that much of a big issue.
Casanub said:
Thank you Cazrack. I will email him now, I can imagine he will be inundated with emails
Another two quick questions "sorry" with Trinity, do you use setcpu to overclock or do you find the kernel gives you all the speed you need? secondly have you had the issue of the unit turning off on an overnight charge? I do not do this normally but I fell asleep with it plugged in and found in the morning it was turned off, when I turned it on it was at 100% so thought is might have turned off as a safety feature but just wondering if you experienced this or heard of it happening?
Thank you again for you help.
Click to expand...
Click to collapse
I keep the stock clock speed 1.3 ghz but I use setcpu to set certain programs to scale to 1.7 ghz.
For example webbrowsers benefit from 1.7 ghz in faster loading and smoothness.
overclocking for games i prefer to run cpu stock and have my gpu overclocked to 600 mhz.
stock gpu is 416 or 418 mhz.
cant overc to much during long gaming sessions since it get to hot and gpu oc give more than cpu.
when i used franco kernel r25 the power off thing happend to me too.
only 1 night during charging but i flashed a new kernel after that.
/cazrack
cazrack said:
I keep the stock clock speed 1.3 ghz but I use setcpu to set certain programs to scale to 1.7 ghz.
For example webbrowsers benefit from 1.7 ghz in faster loading and smoothness.
overclocking for games i prefer to run cpu stock and have my gpu overclocked to 600 mhz.
stock gpu is 416 or 418 mhz.
cant overc to much during long gaming sessions since it get to hot and gpu oc give more than cpu.
when i used franco kernel r25 the power off thing happend to me too.
only 1 night during charging but i flashed a new kernel after that.
/cazrack
Click to expand...
Click to collapse
Ah I see I have done the same it works very well. However you mentioned overclocking the gpu to 600mhz how is this achieved? its not an option in setcpu, suppose the programe is called setgpu
I think I will stick with the the Trinity as the OTG restart is not that much of a issue really. I am sure derkernel will have an update soon.
Casanub said:
Ah I see I have done the same it works very well. However you mentioned overclocking the gpu to 600mhz how is this achieved? its not an option in setcpu, suppose the programe is called setgpu
I think I will stick with the the Trinity as the OTG restart is not that much of a issue really. I am sure derkernel will have an update soon.
Click to expand...
Click to collapse
yes you can OC the gpu for better gaming fps on some kernels.
for example Trinity kernel and Franco kernel allow this if you use franco.kernel.updater from google play store.
i have tested 700 mhz but but during long gaming sessions with games pushing the gpu hardware like spiderman it just get to hot.
484 and 520 mhz is considerd very safe from the information i gatherd.
600 should work even for longer gaming sessions but the device will be warmer.
650 i will test this but im sceptical about long gaming sessions.
750 some crazy people run this....
at the moment im using cpu gov ondemand in setcpu with value 50 in cpu scaling.
have you tried the elite kernel? 1.8 ghz cpu 650 mhz gpu..
/cazrack
cazrack said:
yes you can OC the gpu for better gaming fps on some kernels.
for example Trinity kernel and Franco kernel allow this if you use franco.kernel.updater from google play store.
i have tested 700 mhz but but during long gaming sessions with games pushing the gpu hardware like spiderman it just get to hot.
484 and 520 mhz is considerd very safe from the information i gatherd.
600 should work even for longer gaming sessions but the device will be warmer.
650 i will test this but im sceptical about long gaming sessions.
750 some crazy people run this....
at the moment im using cpu gov ondemand in setcpu with value 50 in cpu scaling.
have you tried the elite kernel? 1.8 ghz cpu 650 mhz gpu..
/cazrack
Click to expand...
Click to collapse
Okay I see it comes full circle, I will give it a bash.
The elite was going to be my next kernel... only reason for using Trinity was, I was advised to do so as a first try. It might be the next step to get rid of the OTG restart and of course the 650 mhz gpu stock oc. Have you tried it or going to try it?
Casanub said:
Okay I see it comes full circle, I will give it a bash.
The elite was going to be my next kernel... only reason for using Trinity was, I was advised to do so as a first try. It might be the next step to get rid of the OTG restart and of course the 650 mhz gpu stock oc. Have you tried it or going to try it?
Click to expand...
Click to collapse
is it supposed to work with cm10? ive tried to flash it but it didnt seem to flash in good
because trinity animation still showing after flash... but nexus isnt booting up.
no problem just boot into recovery and reflash trinity kernel or a cm10 rom.
any clue?
prehaps reflash elite when you have updated to a 100% cm10 nightly installed.
/cazrack
cazrack said:
is it supposed to work with cm10? ive tried to flash it but it didnt seem to flash in good
because trinity animation still showing after flash... but nexus isnt booting up.
no problem just boot into recovery and reflash trinity kernel or a cm10 rom.
any clue?
prehaps reflash elite when you have updated to a 100% cm10 nightly installed.
/cazrack
Click to expand...
Click to collapse
Sounds strange did you delete the cache? As I had that issue originally? I am just using stock ROM tbh as it seems to be the most responsive at the moment but I have not tried them all obviously
Suppose we best keep on keeping and seeing if the smart devas can release a fix.
Casanub said:
Sounds strange did you delete the cache? As I had that issue originally? I am just using stock ROM tbh as it seems to be the most responsive at the moment but I have not tried them all obviously
Suppose we best keep on keeping and seeing if the smart devas can release a fix.
Click to expand...
Click to collapse
I think i did, but i will try again. Could be that extreme kernel is not compatible with cm10?
I would like to try to OC cpu even more up to 2 ghz would be intresting but i dont think there is such a kernel to download.
Once i reach 10 posts ill post in XDA Trinity developer thread
/cazrack.
I found when running Shadowrun Returns with the ElementalX 1.4 kernel http://forum.xda-developers.com/showthread.php?t=2389022 at 1.944 GHZ the back of the Nexus 7 gets hot. This worried me but I noticed when I installed the kernel was an option to use cool thermal throttling. I tried this and now the tablet does not heat up at all. You need to be rooted though to install the kerne of course not sure if ElementalX 1.4 works with stock though, I'm running the latest CM 10.2 nightly. It doesn't seem to affect the performance of either Shadowrun Returns or Wild Blood, the two games I'm playing at the moment, I still have the GPU overclocked to 487 and the Dalvik etc overclocked at the moderate ElementalX setting. . I think being able to run at 1.944 GHZ on my tablet with the cooler thermal throttling is better then running at stock and I believe that even some running at stock have that issue.
Hope this helps others that have this problem.
KedarWolf said:
I found when running Shadowrun Returns with the ElementalX 1.4 kernel http://forum.xda-developers.com/showthread.php?t=2389022 at 1.944 GHZ the back of the Nexus 7 gets hot. This worried me but I noticed when I installed the kernel was an option to use cool thermal throttling. I tried this and now the tablet does not heat up at all. You need to be rooted though to install the kerne of course not sure if ElementalX 1.4 works with stock though, I'm running the latest CM 10.2 nightly. It doesn't seem to affect the performance of either Shadowrun Returns or Wild Blood, the two games I'm playing at the moment, I still have the GPU overclocked to 487 and the Dalvik etc overclocked at the moderate ElementalX setting. . I think being able to run at 1.944 GHZ on my tablet with the cooler thermal throttling is better then running at stock and I believe that even some running at stock have that issue.
Hope this helps others that have this problem.
Click to expand...
Click to collapse
That's a good sign as you know the heat is being distributed effectively away from the internals. You don't need to be rooted to flash custom kernel. And setting different governors will have a major impact on your CPU.
http://forum.xda-developers.com/showthread.php?p=28002345
About The Heat At Least I'm Sure My Advice Is Sound.
Username invalid said:
That's a good sign as you know the heat is being distributed effectively away from the internals. You don't need to be rooted to flash custom kernel. And setting different governors will have a major impact on your CPU.
http://forum.xda-developers.com/showthread.php?p=28002345
Click to expand...
Click to collapse
You might be right about not needing to root to install a custom kernel though I couldn't find a definitive answer in the Nexus 7 2013 forums. I assumed it was needed from using custom kernels on other devices.
My device gets hot while gaming. When you are doing intense gaming like I am I'm sure pretty much any governor will max out the CPU. I know Intellidemand which I use does for sure.
When overclocking, heat is the enemy and it can damage, crash CPUs and even affect the performance of them. I believe if you are concerned about your Nexus 7 heating up (mine does for a good area between the logo and the camera when not using the ElementalX cool thermal throttling) then my advice is good.
Peace.
P.S. How the heck have you done 675 posts since June 2013?
KedarWolf said:
You might be right about not needing to root to install a custom kernel though I couldn't find a definitive answer in the Nexus 7 2013 forums. I assumed it was needed from using custom kernels on other devices.
My device gets hot while gaming. When you are doing intense gaming like I am I'm sure pretty much any governor will max out the CPU. I know Intellidemand which I use does for sure.
When overclocking, heat is the enemy and it can damage, crash CPUs and even affect the performance of them. I believe if you are concerned about your Nexus 7 heating up (mine does for a good area between the logo and the camera when not using the ElementalX cool thermal throttling) then my advice is good.
Peace.
Click to expand...
Click to collapse
Kernel is flashed separately from the ROM. Rooting is only for running apps like Trickster Mod to configure to kernel. Otherwise you can have stock 4.3 ROM with any kernel you want. Heating up will obvious affect performance due to thermal throttling but I was not concerned of damage even when the CPU of my 2012 Nexus 7 got to 80 degrees celsius from running overclocked performance stress test under direct sunlight in a case. If your CPU crashes then it's likely not overclocked correctly. Otherwise if it remains stable under artificial stress test, it will handle any game no problem.
I would really appreciate if someone explain me how exactly this function works?
I mean, tablet don't have fan, so how it keeps the cpu cool, and also what this option does to my nexus in order to keep it cooler?
I would not over clock this device. It us more than fast enough for any Android game.
Throttling does just what the word describes. In basic terms your cpu will be slowed down when getting hot and this defeats the purpose of over clocking.
I won't mention the instability that can be caused or the possibility of doing damage.
Just my thoughts.. To each how own and I do have my I7 pc cpu over clocked big time but it has a huge fan.
Sent from my shiny new(bought last Nov), scratch less Nexus 4!
I agreed, throttling and over clock doesn't make sense but this CPU is underclocked and it is designed to go higher like the one on the galaxy s4 and the GPU is meant to go higher but due to battery life Google underclock it
Sent from my Nexus 7 (2013) using XDA Premium [HD], for the man who wants to use the best tablet screen ever made.
Blade Zero (W1nst0n) said:
I agreed, throttling and over clock doesn't make sense but this CPU is underclocked and it is designed to go higher like the one on the galaxy s4 and the GPU is meant to go higher but due to battery life Google underclock it
Sent from my Nexus 7 (2013) using XDA Premium [HD], for the man who wants to use the best tablet screen ever made.
Click to expand...
Click to collapse
Well , its not under clocked by Google, this is underclocked cheap from the factory , its just a lower bin s600 that has been rebranded as S4 Pro .. If it was regular s600 it wouldn't be underclocked .
theofanis said:
I would really appreciate if someone explain me how exactly this function works?
I mean, tablet don't have fan, so how it keeps the cpu cool, and also what this option does to my nexus in order to keep it cooler?
Click to expand...
Click to collapse
When the CPU reaches a certain temperature threshold it begins to cycle down the CPU speed in order to cool down the processor. It makes the CPU start running at lower frequencies to keep it cool.
Exactly, so a quick oc and u got a better processor without worries of damaging the chip
Sent from my Nexus 7 (2013) using XDA Premium [HD], for the man who wants to use the best tablet screen ever made.
Trickster Mod Thermal Throttling Settings
Hey,
If your CPU is getting hot (especially if it's overclocked and hitting 80 C or near to it) At 1944 the back of my case would get noticeably hot. I still say it isn't good for the CPU. From what I know about overclocking if any CPU gets too hot it can damage the CPU or degrade it over time. I definitely wouldn't want it even getting to 80C before it throttles but I found in Trickster Mod, even the free version, you can set the throttling to custom settings if you are rooted. Custom kernels set their voltages to scale depending on the clock speed which means lower clock speeds, less voltages, less heat. I'd rather keep the temps lower on the CPU then risk damaging the device or degrading it over time. Also you can undervolt the CPU at the kernel different clock speeds so it heats up less. You can run the free AnTuTu Benchmark stability test to see if your clock speed voltages are stable and will not crash your device. I have my CPU overclocked to 1944, thermal throttling down clocks the CPU to 1836 at 73 C, 1620 at 75 C, 1512 at 77 C and 1134 at 80 C. My voltages I lowered and are stable at 1944 - 1087500, 1890 - 1062500, 1836 - 1035000, 1728 - 1025000, 1620 - 1000000, 1512 - 987500. The lower voltages are undervolted as well but not going to list them all here.
Peace,
KedarWolf
P.S. When it was posted in this thread you can install custom kernels without rooting it is correct, I recall reading that at one point. Like it was said to use Trickster Mod, change governors or custom throttling settings you need to be rooted.
Bump bump