Database Info

Undervolting FAQ

I read a lot about undervolting on here and i think i have an idea about what it does but i may be way off, and im sure each device is different. in pimp my cpu there are multiple options, and while this sounds newbish i think this should be explained to folks in some more detail.
this is what im assuming.
undervolting allows for less power consumption.
UV on higher OC levels controls power spikes to the CPU?
what is a safe level to UV and at what frequencies specific to the G2x
i am reading up on this, to get a better idea. http://www.android.net/forum/android-rooting/58117-droid-x-guide-undervolting-guide.html

Here's my understanding of the whole undervolting thing..
In order to maintain stable operation across devices with varying production quality (not all chips are created equal), manufactures use voltage levels higher than necessary for most devices. They cater to the least common denominator. But most phones will still operate reliably at a lower voltage. By undervolting you can extend your battery life and ward off chip killing heat. This all becomes even more important when overclocking. When you overclock your device you increase the power usages (those extra megahertz aren't without cost). This increases both the drain on your battery and the heat produced by your CPU. Undervolting helps to offset both issues.
As for the proper undervolting levels...that will vary with the tolerance of each individual device. But I'm sure someone can provide some general guidelines...sorry I haven't undervolted the g2x yet and don't want to steer you wrong.
Hope this helped...

Good info. I dropped mine .25 on each higher level. So ill see how it goes
G2x with CM7 and faux kernel

what confuses me on this topic is the "it's different for each device" phrase that I keep reading. Is this in reference to the rom/kernel that is being used or is it specific to apps installed/how the phone is used.. or is it a combo of both?
It's confusing me because its seems that OC/UV is hardware specific and each phone has the same hardware. So I don't quite get this "it's different for each device" thing..

schmit said:
It's confusing me because its seems that OC/UV is hardware specific and each phone has the same hardware.
Click to expand...
Click to collapse
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.

i think you mean this.
cybereclipse said:
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
Click to expand...
Click to collapse
yes all g2x's have a tegra 2 chip.
But production does not always produce the same tolerances for all the chips.
ussually(with the quality control apparently given to the g2x who knows) but ussually all chips are tested and every chip that is in a g2x will perform reliably at 1ghz as it is specified and sold at.
some of these will run reliably at 1500 or better while some will not go over 1100 without starting to get unreliable.
example is the droid 1 was sold at 550 mhz. they did an update that upped it to 600mhz so they knew all chips were tested to be ok at that threshold. Mine would run at 1200 reliably no overheating(except running flash) no reboots.
with 2 different kernels. there was another kernel that they messed with the voltages so that i would get constant reboots even at 700mhz.
some droids would not run over 700 without experiencing problems.
So yes the tegra 2 chips is the same but the abilities of it can be different. they are guarenteed to run at the speed they are sold at but most will function at a much higher speed without problems while some will not.
oh just thought of a great example. the AMD tri-core processors.
those are quadcores where 1 of the cores did not pass the tests but the other 3 did so instead of scrapping the entire chip they turned off the bad processor and sold it as a tricore. there are motherboards out there that allow this core to be turned back on and many have done this and it works just fine. its just that core didnt pass whatever minimum they set on it even though it was perfectally functional they determined that if it got to this temp or didnt run at this speed(over what it was sold at) it didnt pass.
So while this kernel at this voltage may run fine on your phone it may caused reboots or lock ups on others.
hope this makes some sense.

eagle1967 said:
yes all g2x's have a tegra 2 chip.
But production does not always produce the same tolerances for all the chips.
ussually(with the quality control apparently given to the g2x who knows) but ussually all chips are tested and every chip that is in a g2x will perform reliably at 1ghz as it is specified and sold at.
some of these will run reliably at 1500 or better while some will not go over 1100 without starting to get unreliable.
example is the droid 1 was sold at 550 mhz. they did an update that upped it to 600mhz so they knew all chips were tested to be ok at that threshold. Mine would run at 1200 reliably no overheating(except running flash) no reboots.
with 2 different kernels. there was another kernel that they messed with the voltages so that i would get constant reboots even at 700mhz.
some droids would not run over 700 without experiencing problems.
So yes the tegra 2 chips is the same but the abilities of it can be different. they are guarenteed to run at the speed they are sold at but most will function at a much higher speed without problems while some will not.
oh just thought of a great example. the AMD tri-core processors.
those are quadcores where 1 of the cores did not pass the tests but the other 3 did so instead of scrapping the entire chip they turned off the bad processor and sold it as a tricore. there are motherboards out there that allow this core to be turned back on and many have done this and it works just fine. its just that core didnt pass whatever minimum they set on it even though it was perfectally functional they determined that if it got to this temp or didnt run at this speed(over what it was sold at) it didnt pass.
So while this kernel at this voltage may run fine on your phone it may caused reboots or lock ups on others.
hope this makes some sense.
Click to expand...
Click to collapse
Nice...that was much better than my explanation.

cybereclipse said:
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
Click to expand...
Click to collapse
lol. dude, I'm in the g2x forum.. not the "whatever phone ya wanna talk about" forum. I was referring to the g2x's having the same hardware, lol.
Thanks to the other guy for the awesome explanation

About CPU

Hi. My question us what CPU speed can I use before the desire s takes damage? Thanks
Sent from my HTC Desire S using XDA Premium App

Would not go over 1200mhz for general use but in the end it comes down to heat and chip quality. Some chips will run faster and produce less heat then others, you'll have to test yours! Don't over volt even if it is possible?
That's about all I can give you on the matter.
Sent from my HTC Desire S using XDA App

um... just a quick question... why do You need more power? I mean what for??
n64 and psx emulators - full speed, gameloft's dungeon hunter 2 and rainbow six - smooth as my wifes ass, all the flash movies on web or divx offline - no problem, general use - as good as gingerbread can deliver.
I was thinking about which dual core beast shall I buy and ended up with this pocketable and powerful beauty.
... back to the topic - I wouldn't overclock it over 1.5 ghz, even then only for demanding tasks. battery life would decrease as well and I wouldn't trade that for a bit more fps.

Okay. Thank you guys
Sent from my HTC Desire S using XDA Premium App

bronx said:
um... just a quick question... why do You need more power? I mean what for??
n64 and psx emulators - full speed, gameloft's dungeon hunter 2 and rainbow six - smooth as my wifes ass, all the flash movies on web or divx offline - no problem, general use - as good as gingerbread can deliver.
I was thinking about which dual core beast shall I buy and ended up with this pocketable and powerful beauty.
... back to the topic - I wouldn't overclock it over 1.5 ghz, even then only for demanding tasks. battery life would decrease as well and I wouldn't trade that for a bit more fps.
Click to expand...
Click to collapse
Good response, I bought a Desire S recently too and feared the "single core" 1 GHz CPU wouldn't be much faster than my Legend clocked at 768 MHz, after all it is only 232 MHz difference. Couldn't have been more wrong. The phone is a beast.

1.2 ghz is a good speed if you wanna overclock (& also this speed is more than enough)
1.4-1.5 ghz is the limit, anything more than that is very unstable and can cause damage to your cpu

Hey guys. I have a Desire HD. Although they're different phones, i'm sure the internals are almost exactly the same, bar few differences. As such, the cpu should also be the same. I tried out different cpu speeds. I kept my phone at 1.72ghz for a couple of weeks. The phone got pretty hot when using Wifi and such, but didn't get too hot. I'd say the safe point is 1.5ghz but at the stock voltage. Works for me, should work for you guys too I can get 1.7ghz at 1325mv, which is good enough for me I didn't get random crashes etc. My persona highest on this phone was around 2.1 ghz, which was insanely high, the phone was super fast, but got hot blazing hot and the phone started flashing orange led lights and then shut down for like 10 minutes straight. I thought it was gone but...nope, was lucky thank god LOL
Always be careful. If you have insurance, then go ahead and by all means clock the hell out of it if you don't mind a decrease in battery life. But if you have no insurance, and bought it sim-free...i'd suggest 1.3ghz...better be safe than sorry, wouldn't you agree?

the phone started flashing orange led lights and then shut down for like 10 minutes straight. I thought it was gone but...nope, was lucky thank god LOL
Click to expand...
Click to collapse
Haha, bet that was a ball-shrinking moment. Made me laugh reading it.
But seriously, considering the potential damage & the native performance of the DS you wouldn't want to go crazy really.
Sent from my HTC Desire S

Hi!
I succesfully overclocked my DS to 1,5GHz(first to 1,3GHz, than to 1,4GHz), and it's fully stable with stock voltages. I use virtuous unity 1.29.0, and tweaked the built in OC daemon. Tested with stability test v1.5, and no problems after 30 minutes. Temperature is around 40 C(plugged in, charging, and running stability test).
What do you think, can I use it for 24/7? The temperatures are not high, and the phone is rock stable, so is it safe?
Thanks for answer.

ffodi said:
Hi!
I succesfully overclocked my DS to 1,5GHz(first to 1,3GHz, than to 1,4GHz), and it's fully stable with stock voltages. I use virtuous unity 1.29.0, and tweaked the built in OC daemon. Tested with stability test v1.5, and no problems after 30 minutes. Temperature is around 40 C(plugged in, charging, and running stability test).
What do you think, can I use it for 24/7? The temperatures are not high, and the phone is rock stable, so is it safe?
Thanks for answer.
Click to expand...
Click to collapse
why do you need to run it on 1.5ghz? it is very fast at 1.2ghz
& also 1.5ghz will consume more battery & if you put some load on the cpu like a little gaming or a lot of browsing it can get heated up
overclocking more than necessary isnt good as there can be hidden damage to the chip(even if the processor doesn't get heated up)
read post #3 here
so always go easy on the overclocking

kartkk said:
why do you need to run it on 1.5ghz? it is very fast at 1.2ghz
& also 1.5ghz will consume more battery & if you put some load on the cpu like a little gaming or a lot of browsing it can get heated up
overclocking more than necessary isnt good as there can be hidden damage to the chip(even if the processor doesn't get heated up)
read post #3 here
so always go easy on the overclocking
Click to expand...
Click to collapse
Thanks for the answer! I overclocked it to 1,5GHz becouse I like it if everything is fast as lightning.
I know it can consume more battery, but it's not a problem for me.
I've read that post, it's useful thanks, but i think if everything is on stock voltage it cant hurt the cpu. I overclock my desktop rig also since ~15 years, and never had problems with that. I know that it's not the same, but I hope there will be no problems with that.

Is 1.5Ghz too high?

I have my Sensation set to 1.5Ghz and it works perfectly. The only thing is that it's getting a little hot (which is expected btw). It's currently fixed at 42C. 1.5Ghz is great but is it really that necessary? Should I just OC it to 1.3Ghz? I'm trying to find a nice temp base.

monkey hung said:
I have my Sensation set to 1.5Ghz and it works perfectly. The only thing is that it's getting a little hot (which is expected btw). It's currently fixed at 42C. 1.5Ghz is great but is it really that necessary? Should I just OC it to 1.3Ghz? I'm trying to find a nice temp base.
Click to expand...
Click to collapse
To answer your question, each device will have a differing operational ceiling depending on the quality of the SoC, soldering, silk-screening etc. They aren't all created equal. If 1.5GHz works fine for you, stick with it I see OC kernels pushing to 1.8GHz now.
Naturally the higher you go the hotter your SoC will run, so I'd play around and find the point where you gain some performance, but negligible heat over stock. Heat will kill not only your SoC, but your battery as well.
I'm only going from personal experience, but I've never found an OC to be worth it in terms of an actual, real-life performance increase, on any device. It looks good in benchmarks, but I'd rather have a phone that was smooth as butter in day-to-day operation than a jerky piece of sh*t that gets 10,000 in Quadrant YMMV of course!
The heat stress and battery drainage costs, plus stability issues, outweigh the positives for me.

How can I reset my CPU back to stock then?

monkey hung said:
How can I reset my CPU back to stock then?
Click to expand...
Click to collapse
Most of the Sensation ROMs feature what's called an OC Daemon.
This is pretty much an automatic overclocker of sorts. It can change your clock ceiling/floor automatically depending on load. Read a bit more about it here.
If you have something like SetCPU installed, the Daemon is redundant, giving you manual control over your clocks. The easiest way to return to 'stock' frequencies would be to simply delete SetCPU and allow the Daemon to do it's thing

Well I uninstalled it and I have LeeDroid. How do I find this "daemon"? Where would it be located? What do I do I'm a noob

monkey hung said:
Well I uninstalled it and I have LeeDroid. How do I find this "daemon"? Where would it be located? What do I do I'm a noob
Click to expand...
Click to collapse
I couldn't see whether the daemon in included on LeeDroid, or whether LeeDroid has actually just modified the frequency tables (list of supported frequencies) to allow for the ~1730MHz ceiling. If the daemon is there, it'll already be working for you - you don't see it
I don't believe it's something you can just download and tack on. I think you'd have to be running a supported ROM. You may need to dig a little deeper into the LeeDroid thread and do some reading, or perhaps retitle this thread to ask 'Does LeeDroid include the OC Daemon' or something similar.
Sorry I can't be more help, I'm a devout Android Revolution HD supporter myself, although I am running the UNITY kernel.
Good luck mate!

personally I can't see the need to over clock, given that all software is probably written for devices currently in use, I do not know of any dual core 1.5 or higher phones, so why oc ?
I agree , I would rather have a fast stable phone, than some jerky fc piece of ****e that gets 10000 jiggawatts in a benchmark, and that can cook my crumpets..................... on second thoughts, I do like my crumpets.

[Kernel] 3.2-oc,uv,explosions. razzle dazzle.. pretty much everything (12-07-2011)

Ok. 12-06-2011 kernel should work now.. both renditions.. seems like the addition of bfs knocked the kernel's proverbial **** in the dirt.. so no bfs yet.
I'm having a hard time keeping track of the names people are calling this kernel.. so in light of various others naming their kernels.. i shall call this one.. hmmm. i suck at naming things.. the first thing that popped into my head was...
Razzle Dazzle <--kidding. just an example of why I stick to appending dates on the filenames.. (and i will do the same for my children)
http://home.comcast.net/~ibladesi/TF101-CryBaby-12-07-2011-nomVchanges.zip <---This boots at 1232mhz, and insults your manhood.
and for those menly men that like their tf101 fast all the time. 1592mhz boot clock..
http://home.comcast.net/~ibladesi/TF101-CptAwesome-12-07-2011-nomVchanges.zip <---
These two have very high vcore... it is meant for people who would like to adjust their voltage themselves. If you have trouble with the normal kernels, and suspect the undervolting is causing the issues... try this.. but remember to undervolt.. really...
http://home.comcast.net/~ibladesi/TF101-CptAwesome-12-07-2011-flamable.zip
http://home.comcast.net/~ibladesi/TF101-CryBaby-12-07-2011-flamable.zip
previous:
http://home.comcast.net/~ibladesi/TF101-11-26-2011.zip
Newer stuff is in bold... just in case you can't read dates.
Testing out memory timings that may bite you.. If anyone can help cut through the bull**** that is MC/EMC clocks... just chime in here.. Originally I increased (slowed down) the timings and bumped up the clock by 33mhz.. and got fail. So... advancing the timings it is.. They are pretty pitiful stock.. What really pisses me off is the missing 33mhz (and thus 66mhz from emc).. we could use that... Well.. lets see if waking up the wimpy timings helps.
edit:1680mhz. The updater-script still says the max is 1656mhz for this zip.. but the max is 1680.. i promise
http://home.comcast.net/~ibladesi/TF101-08-20-2011-1680.zip
Same as above, but a slightly advance of the memory timings. Am I even using the correct word, I seem to be in car tuning mode.. Tighter memory timings, I guess? My plan is to push it until its crashy. This is not crashy: http://home.comcast.net/~ibladesi/TF101-08-24-2011.zip
edit: throttle_temp is at 56... voltage bumped up for freqs above 1224.. So this could get a little toasty
http://home.comcast.net/~ibladesi/TF101-08-21-2011-highmv.zip
Edit: Now on github. http://www.github.com/ibladesi
Also because some people asked..
OhYouLikeTheKernel?

I just installed.
Boot up ok! (no boot loop)
I set it up to 1544mhz. So far so good. I will keep testing and let you know of any problem.

Well.. it defaults to 1544.. go_maxspeed_load is set to 96.. I should've set that to 99 so it would have a better chance of hitting all the clocks. Asus had it at 80.. and that's good for stock clock, but for oc - it ends up skipping past certain freqs.
Thanks for trying it out.. ntfs compat - try that too if u get a chance.

Blades said:
Thanks for trying it out.. ntfs compat - try that too if u get a chance.
Click to expand...
Click to collapse
no ntfs compatibility, at least with any of my drives.

Tested it with revolver 2.1.2
Results with kernels so far:
v7 : reboot loop, and CWM crashing after aprox. 20 seconds
v8 : running smooth @ 1.4 ghz, connecting hdmi crashes on both my tv as my monitor (dvi)
TF101-08-20-2011.zip : force closes on startup. Ending up with a popup in the middle of the screen saying 'ENGLISH' . HDMI working on tv, not on monitor.
I don't know what hdmi changes are made in the last kernels, even on stock i am not able to connect to my dvi-d monitor through hdmi (samsung 2343 , no speakers in it)
Monitor supports the resolution and supports hdcp. connector is fine (popcorn mediaplayer works fine with it, also hdmi 1.3a)
I still think\hope this is a software\driver issue. Not a hardware issue.

Governors acting weird
I tried the new Kernel and is working somewhat stable atm, a few FC at 1.544+ . Installed with no issues on my B60 + Prime 1.7.
As for the performance, is kind of a tough call. Even thus I'm reaching new high "stable" speeds it seems like they don't really follow the governors set. For instance, If I set 1.544 @ Performance, speed drops constantly below 1.4. Benchmarks also show a lower scores than what I used to achieve with Clensym-Blades v7a for intance on Antutu I used to reach scores of 6000+ at 1.4 Ghz now, even thus I'm running at a "higher" clock I get sub -5800.
I tried to enforce the 1.544 setting it as the min speed as well with the same result.
This all makes me think that there is some kind enforcement to throttle down using trigger, which I guess will be CPU temp, however, my CPU did not go higher than 32 C even stress testing it, but as this changes occur very fast, I could be wrong on that statement.
Any ways, good first release, hope to at least comprehend what's cooking inside.

runner50783 said:
I tried the new Kernel and is working somewhat stable atm, a few FC at 1.544+ . Installed with no issues on my B60 + Prime 1.7.
As for the performance, is kind of a tough call. Even thus I'm reaching new high "stable" speeds it seems like they don't really follow the governors set. For instance, If I set 1.544 @ Performance, speed drops constantly below 1.4. Benchmarks also show a lower scores than what I used to achieve with Clensym-Blades v7a for intance on Antutu I used to reach scores of 6000+ at 1.4 Ghz now, even thus I'm running at a "higher" clock I get sub -5800.
I tried to enforce the 1.544 setting it as the min speed as well with the same result.
This all makes me think that there is some kind enforcement to throttle down using trigger, which I guess will be CPU temp, however, my CPU did not go higher than 32 C even stress testing it, but as this changes occur very fast, I could be wrong on that statement.
Any ways, good first release, hope to at least comprehend what's cooking inside.
Click to expand...
Click to collapse
I'll up the 1.544 voltage. Amazing temps. It downclocks at 49degC.
Read from sysfs
cat t /sys/devices/platform/tegra-i2c.3/i2c-4/4-004c/ext_temperature
Edit: Tried that antutu bench, 7397 @1656mhz. Chart topper for this device.
edit: antutu pissing contest motivated me to try out 1680.. and that works great.. I really don't like these single threaded benchmarks.. Its luck of the draw.. whatever cpu the process is assigned to really factors in on the score.. If most of the android processes are on cpu0 - then cpu1 is obviously the desirable core to use.. because android just gleefully rapes cpu cycles whenever it pleases.
antutu: 7500 @ 1.680ghz .. lost to the damn xoom by 3pts.. I am #3 for all devices.. cuz I'm ****in awesome.. I'll be telling that to all the lovely ladys at the bar.. #3 in antutu *****.. can you buy me a drink.

jwilliamf said:
no ntfs compatibility, at least with any of my drives.
Click to expand...
Click to collapse
Was the /system/lib/modules/ntfs.ko module loaded?
/dev/block/sda4 on /Removable/USBDisk1 type ntfs (rw,relatime,uid=0,gid=0,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_multiplier=1)
I had to load the module and make the directory.. for some reason it wasn't automatically mounted.. but it works.. Ok.. so writing to the drive is not working.. I have the module compiled with RW access enabled.. Must have something to do with the way I'm mounting it. Honestly I don't use it enough to care too much.. NTFS has been found to be slower on things like flash drives.. But it does piss me off..
/system/xbin/tcpsvd -vE 0.0.0.0 21 ftpd -t 30000 -T 30000 -w / &
ftp server works wonders 4.0-4.2 MB/sec wowie!
I hate android.. I'll bet ntfs rw works on ubuntu (on tf101)

Tuxera | Leading NTFS, exFAT Interoperability on Android, Linux ...
Industrial Grade. Industry standard Tuxera NTFS, exFAT and HFS+ deliver the most reliable and highest-performing Windows and Mac interoperability.
www.tuxera.com
this is the maker of the (stock) tntfs.ko module found in the stock ramdisk.. it probably doesn't load on modded 2.6.36.4 kernels..
http://www.tuxera.com/news/asus-selects-tuxera-file-system-software-for-eee-pad™-tablets/

You are Amazing Blades, keep it up. Will try the new updated Kernel and post results back.

does HDMI work for this release as in clemsyn? is this everything clemsyn has but with different timings?

runner50783 said:
You are Amazing Blades, keep it up. Will try the new updated Kernel and post results back.
Click to expand...
Click to collapse
Watch out.. still need to up the voltage you requested.. 1.544 might be finicky.. and as I'm typing this.. my laptop is quickly (very quickly).. running out of batteries.. Its not a fun computer to use on batteries.. as HP implemented some sort of lame processor (bios level) scaling mechanism that cuts the max pstate to 1... which is 1100mhz.. Using TurionPowerControl I set that pstate to 2.2 ghz.. So whats up now.. Batteries in hp's laptops only display the %... no discharge rate = no remaining time.. Which leads me to my tablet relevance.. Should I go and get that Touchpad for 99$?
thanks for the compliments.. oh.. I forgot.. tntfs.ko does load without issues..
so here..
http://home.comcast.net/~ibladesi/tntfs.ko
put it wherever.. /data/local/ for me (for now)
insmod /data/local/tntfs.ko
test out some ntfs stuff.. silly proprietary ntfs module..
edit: Woohoo, works flawlessly.. So the asus HC storage framework is meant to use this proprietary module.. I don't really like them bloating up the ramdisk with it sitting in /sbin.. but I understand why they would do that (and subsequently call it in the init script).. because without it.. the fancy "External storage inserted" notification would not work... and (at least in my case), writing to NTFS disks wouldn't work either! Seems to be pretty damn fast too...
another note.. When copying files.. its best to copy to /data/media/ as opposed to /mnt/sdcard/ - if you can.. I/O through /mnt/sdcard results in high cpu usage by the /system/bin/sdcard process.. go figure eh? symlinks aren't good enough, huh?

Blades said:
Watch out.. still need to up the voltage you requested.. 1.544 might be finicky.. and as I'm typing this.. my laptop is quickly (very quickly).. running out of batteries.. Its not a fun computer to use on batteries.. as HP implemented some sort of lame processor (bios level) scaling mechanism that cuts the max pstate to 1... which is 1100mhz.. Using TurionPowerControl I set that pstate to 2.2 ghz.. So whats up now.. Batteries in hp's laptops only display the %... no discharge rate = no remaining time.. Which leads me to my tablet relevance.. Should I go and get that Touchpad for 99$?
thanks for the compliments.. oh.. I forgot.. tntfs.ko does load without issues..
so here..
http://home.comcast.net/~ibladesi/tntfs.ko
put it wherever.. /data/local/ for me (for now)
insmod /data/local/tntfs.ko
test out some ntfs stuff.. silly proprietary ntfs module..
edit: Woohoo, works flawlessly.. So the asus HC storage framework is meant to use this proprietary module.. I don't really like them bloating up the ramdisk with it sitting in /sbin.. but I understand why they would do that (and subsequently call it in the init script).. because without it.. the fancy "External storage inserted" notification would not work... and (at least in my case), writing to NTFS disks wouldn't work either! Seems to be pretty damn fast too...
another note.. When copying files.. its best to copy to /data/media/ as opposed to /mnt/sdcard/ - if you can.. I/O through /mnt/sdcard results in high cpu usage by the /system/bin/sdcard process.. go figure eh? symlinks aren't good enough, huh?
Click to expand...
Click to collapse
Thanks for your replay Blades, I did notice that the voltage increase was still not made available, hoping on it anxiously!
After following your advice of reading cat t /sys/devices/platform/tegra-i2c.3/i2c-4/4-004c/ext_temperature and yes, it seems my proc is hitting the 49 C threshold. I understand that 40-60 C its within the recommended temperature range and the max will be like 105 C. While I appreciate the fact that you are trying to take care or our transformers by setting up the 49 C temp threshold : ) I would still like to know if there is a way for me to disable or rise it manually? (script, edit files, etc)
Chist!, where do you guys learn so much?
Thanks for the tntfs.ko tip!
Also, have you tried the new ADW Launcher EX?, the thing is fast on HC, At last I have some really smooth scrolling going on even in portrait : D

I haven't tried that yet.. I fear it would make my hc tablet look and act too much like my froyo gtab. Then again, that could be a good thing.
Theres now a kernel up for you.. Let me know if you want me to set all higher freqs to something crazy like 1400-1450 so users can apply their own voltage settings..

Blades said:
I haven't tried that yet.. I fear it would make my hc tablet look and act too much like my froyo gtab. Then again, that could be a good thing.
Theres now a kernel up for you.. Let me know if you want me to set all higher freqs to something crazy like 1400-1450 so users can apply their own voltage settings..
Click to expand...
Click to collapse
My friend, let me tell you the you just created the fastest kernel avaliable for the transformer. The got my self into the antutu's top 10 for my device scoring 6766 @ 1544 Which is the fastest speed at the current voltage settings that I'm able to be "usable" at. Still suffering from occasional reboots at that soeed so yes probably a little more juice should help and probably a 60c temp threshold for throttling down?
Anyway the mV increments did help as I now have 1472 as my new stable speed also scoring near 6700 on antutu.
Did extensive testing using "pimp my cpu" and "StabilityTest" to test the whole range of frequencies and it all went OK for 1472 or lower.
Anyway, very pleased with the results. My quasi elite tegra chip is out performing higher clocked bros, I guess your mem tweaking has to do with that.
The unique abilities of your kernel to provide a wider range of frequencies and voltages is giving us the chance of getting the most out of our tablets where is that donate button btw?
Edit: Why not having all >= 1544 set to 1400 - 1450 : ), Ok, Ok, it will burn lots off chips.
Edit: 6905 on Antutu!, the thing is flying at 1544, just a little more juice, I know I can achieve "rock solid" stability at that speed, just a little more juice!

runner50783 said:
My friend, let me tell you the you just created the fastest kernel avaliable for the transformer. The got my self into the antutu's top 10 for my device scoring 6766 @ 1544 Which is the fastest speed at the current voltage settings that I'm able to be "usable" at. Still suffering from occasional reboots at that soeed so yes probably a little more juice should help and probably a 60c temp threshold for throttling down?
Anyway the mV increments did help as I now have 1472 as my new stable speed also scoring near 6700 on antutu.
Did extensive testing using "pimp my cpu" and "StabilityTest" to test the whole range of frequencies and it all went OK for 1472 or lower.
Anyway, very pleased with the results. My quasi elite tegra chip is out performing higher clocked bros, I guess your mem tweaking has to do with that.
The unique abilities of your kernel to provide a wider range of frequencies and voltages is giving us the chance of getting the most out of our tablets where is that donate button btw?
Edit: Why not having all >= 1544 set to 1400 - 1450 : ), Ok, Ok, it will burn lots off chips.
Edit: 6905 on Antutu!, the thing is flying at 1544, just a little more juice, I know I can achieve "rock solid" stability at that speed, just a little more juice!
Click to expand...
Click to collapse
Well, I did 7210 in antutu with one of the elite kernels from Clemsyn at 1706 mhz, performance mode... Blades, your kernel is really good. But I find it a little not as stable as Clemsyn one at really high oc values. The tablet is really hot too because for I don't know the reason I can't uv at the two highest frequencies with pimp my cpu. I can with Clemsyn one. But, Blades : good work! Keep up!
Sent from my Transformer TF101

Bump because I updated. So far its pretty good... I actually had one real freeze.. as in lock up.. stress testing at 1680 via usb1->microsd usb2->/data/media transfers/decompression simultaneously.. going to teat out 7z bench.. as in '7z b' - that should thrash the memory/CPU quite a bit.

Hey Blades I have a couple of questions about this OC kernal:
1. Could this be installed on custom roms such as prime and revolver? Is the kernal from the latest firmware build?
2. What's the highest temperature that this device could reach safely? which program we use to checK?
3. Does this has voodoo sound module?>

Imppy said:
Hey Blades I have a couple of questions about this OC kernal:
1. Could this be installed on custom roms such as prime and revolver? Is the kernal from the latest firmware build?
2. What's the highest temperature that this device could reach safely? which program we use to checK?
3. Does this has voodoo sound module?>
Click to expand...
Click to collapse
1. Yes, of course. I always am checking the Asus FTP for new source (and posting about it here too). No this is not the 8.6.6.9 from the tf101g, but I nothing different between 8.6.5.7 and that.
2. Throttles down to 1424 when temps reach 49degC (unless otherwise noted in description of zip file. http://forum.xda-developers.com/showthread.php?t=1137520 see my reply at the end. Gotta love my ability too clear out a thread - like a fart in an elevator or something.
3. No. The voodoo thread in this forum does not mention that its compatible with 3.2 (but it probably is). I don't use it so I wouldn't be testing it. I'm sure if I included a module the world wouldn't implode. But eh, when in doubt, I omit.

Blades, any way to get Voodoo sound working with this awesome kernel? Sorry to bring it up again... it's just I can get the Voodoo Plus app to load the wrapper for other 3.2 kernels but not yours. Is it because this is based on 2.6.36.4 and not 2.6.36.3?

Linpack Scores Relatively Low

I am just wondering why the Sensation is only hitting around 80MFlops at most in Linpack @ 1.5GHz. It seems that this phone should be getting 100+ every time. I have also noticed that the single core may score 55MFlops while the multicore will only raise that to 60MFlops.
Does it have something to do with the Java libraries? I also saw something about NEON libraries?
I think the highest I've ever scored with my Sensation is 91MFlops.
Thanks for any input on this guys. I know it's just a benchmark, but I'm just curious.
EDIT: Just scored a 27. I'm just gonna uninstall this app and use AnTuTu. How does this CPU ACTUALLY perform against other high end CPUs?

snelan said:
I am just wondering why the Sensation is only hitting around 80MFlops at most in Linpack @ 1.5GHz. It seems that this phone should be getting 100+ every time. I have also noticed that the single core may score 55MFlops while the multicore will only raise that to 60MFlops.
Does it have something to do with the Java libraries? I also saw something about NEON libraries?
I think the highest I've ever scored with my Sensation is 91MFlops.
Thanks for any input on this guys. I know it's just a benchmark, but I'm just curious.
EDIT: Just scored a 27. I'm just gonna uninstall this app and use AnTuTu. How does this CPU ACTUALLY perform against other high end CPUs?
Click to expand...
Click to collapse
Qualcomm actually has better floating point calculations than others, it's one of the benefits of the dragons. If you're using Sense, try linpack on Vanilla and it will be higher. Sense & benches don't go together b/c of something HTC screwed up.
http://www.nordichardware.com/news/...lcomm-demonstrates-new-msm8660-processor.html

what exactly is a floating point calculation?

Awesome, thanks!
By Vanilla, do you just mean a stock ROM without Sense? Would CM7 work? I just installed CM7 and set my min max to 1620/1620 and topped out at 101MFlops, but that was only out of 3 runs.
Does this also mean that Sense has slower real-world performance? Or just for benchmarks?

snelan said:
Awesome, thanks!
By Vanilla, do you just mean a stock ROM without Sense? Would CM7 work? I just installed CM7 and set my min max to 1620/1620 and topped out at 101MFlops, but that was only out of 3 runs.
Does this also mean that Sense has slower real-world performance? Or just for benchmarks?
Click to expand...
Click to collapse
Yeah cm or aosp, sense has always been slow with benches since the HTC hero. It doesn't play nice with any bench really, compare the same phone on sense and vanilla and scores are different. I don't know much about floating points but its probably related to how fast things are calculated. The hummingbird had a lower linpack than the scorpions of that time. And this doesn't mean sense is slower but it rapes the phone's ram excessively. When ics is out benches should be done to see how this phone really performs, most of the 1 core is sleep anyway or not at max.
Sent from my T-Mobile Sensation 4G using XDA App

One important thing:
When you score in multi-thread is just about 10 points above the single-thread score, it's because your second core (CPU1) didn't go online, or simply too late, so multi-thread was just using one core
Try this: with root explorer, go to sys/devices/system/CPU/CPU1/online
in this file replace 0 by one, then save. Immediatly set the permissions to read only (on "write" is ticked by default, untick it)
Now your both cores are always online, ready to scale up, and multi-thread scores will always be far superior to single-thread.
(it's not sticky, everything we go back as it was after a reboot)
Also my very best score with Linpak was 115, at 1.782ghz, CPU1 forced online, I posted a screenshot somewhere in Bricked kernel thread. This is a real battery drain and hot device to get this score
In real life, 90 or 95 at 1.5ghz is pretty good

i900frenchaddict said:
One important thing:
When you score in multi-thread is just about 10 points above the single-thread score, it's because your second core (CPU1) didn't go online, or simply too late, so multi-thread was just using one core
Try this: with root explorer, go to sys/devices/system/CPU/CPU1/online
in this file replace 0 by one, then save. Immediatly set the permissions to read only (on "write" is ticked by default, untick it)
Now your both cores are always online, ready to scale up, and multi-thread scores will always be far superior to single-thread.
(it's not sticky, everything we go back as it was after a reboot)
Also my very best score with Linpak was 115, at 1.782ghz, CPU1 forced online, I posted a screenshot somewhere in Bricked kernel thread. This is a real battery drain and hot device to get this score
In real life, 90 or 95 at 1.5ghz is pretty good
Click to expand...
Click to collapse
Wow! Never knew about that, I just assumed that the second core's clocks were off or something. Thank you very much good sir!