Database Info

i9020a overclocking

Has anyone been successfull? i have tried every OC kernel and as soon as i overclock it just reboots my phone to a freeze (only way out is to either pull the battery or adb reboot). That being said the UV kernel runs fine.

Not sure if it has to do with the I9020A series.
But overall, each NS phone can tolerate its own OC levels. Some phones can tolerate only up to 1.2 GHz, some may be able to achieve 1.4GHz (or beyond). And for some of the unfortunate, some aren't able to OC at all.

Thus this post. I hope my phone is'nt the issue. it would be nice to push a little bit more out of it if i needed it down the line.

I over clocked mine to 1.4 and it was fine, I leave it at 1.0 tho, this friggin thing is quick enough for now.

hmm how do you check your radio. I'm gonna try that as a last resort. And i can set mine as 1.4 but as soon as i run a resource heavy task (n64) my phone locks up and reboot freezes.

themapleboy said:
hmm how do you check your radio. I'm gonna try that as a last resort. And i can set mine as 1.4 but as soon as i run a resource heavy task (n64) my phone locks up and reboot freezes.
Click to expand...
Click to collapse
Not sure why a radio would affect your ability to OC but...
Menu -> Settings -> About Phone -> Baseband Version
the last 3 are what you want to look at "JK8/KB1/KB3"
List all the kernels you've tried. The best in my opinion is Netarchy's 1.3.0.3-CFS kernel using SetCPU
Try intervals of 1.2 GHz too. My phone can only go up to 1.2 GHz

Yeah actually i had tried all of the bfs kernels. I just succeeded in getting Netarchy's 1.3.0.3-CFS kernel. And i can run up to 1.4 . Maybe the brain fk scheduler does not play nice with 9020a's

themapleboy said:
Yeah actually i had tried all of the bfs kernels. I just succeeded in getting Netarchy's 1.3.0.3-CFS kernel. And i can run up to 1.4 . Maybe the brain fk scheduler does not play nice with 9020a's
Click to expand...
Click to collapse
awesome. I just prefer CFS because with BFS the boot animation doesn't show, and it bothers me.

zephiK said:
awesome. I just prefer CFS because with BFS the boot animation doesn't show, and it bothers me.
Click to expand...
Click to collapse
i flashed the BFS first, and lost my boot animation. Then i switched to the CFS, and the boot animation still didnt appear.
Any ideas as to how i can get it back?
Also, is there anyway to recover the stock kernel? I'd like to have it handy to be able to go back to it.
thnks

mixxy said:
i flashed the BFS first, and lost my boot animation. Then i switched to the CFS, and the boot animation still didnt appear.
Any ideas as to how i can get it back?
Also, is there anyway to recover the stock kernel? I'd like to have it handy to be able to go back to it.
thnks
Click to expand...
Click to collapse
Wipe dalvik and cache. Flash a rom that flashes stock. Like cm7 but netarchys is so much better than stock
You can also get ogdobbers which is stock + ext4 + voodoo.
Sent from my Nexus S using XDA Premium App

Hey everyone,
This is an off topic question but does anyone know what happened to the 1.6 OC support for Netarchy? I loved to see the absurdly high quadrant scores and instantaneous screen transitions.
Thanks,
Justin

JTECJ said:
Hey everyone,
This is an off topic question but does anyone know what happened to the 1.6 OC support for Netarchy? I loved to see the absurdly high quadrant scores and instantaneous screen transitions.
Thanks,
Justin
Click to expand...
Click to collapse
you're better off asking that in the netarchy kernel thread in dev forums.
netarchy could answer that... not a lot of phones can tolerate 1.6 GHz Oc

Thanks, yeah i felt a little bad posting the question here. Though ive been an avid user for a long time i have never posted so i didnt have sufficient rites to post in the decelopment section yet : (
Justin
Sent from my Nexus S using XDA Premium App

zephiK said:
Wipe dalvik and cache. Flash a rom that flashes stock. Like cm7 but netarchys is so much better than stock
You can also get ogdobbers which is stock + ext4 + voodoo.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
so cm7 flashes the stock kernel?

mixxy said:
so cm7 flashes the stock kernel?
Click to expand...
Click to collapse
yep! low on bugs and freezes but no voodoo or bln.. dammit

AdamComb and VegaComb Team Up

I think the Gtab devs should team up too.
http://tabletroms.com/index.php/2011/07/08/adamcomb-v0-1-vegacomb-beta-1-7-released-today-782011/

Wonder is this AdamComb v0.1 can be flashed on gtab ?
Anybody knows ?
Dave,

I haven't tried it, but it probably can, so long as you also flash Clem's HC kernel. Some of the drivers might not be there though, like wifi.
I'm really hoping zhyong makes that his next bl1.1 project.
MC

Should be able to.

Ok, I nvflashed back to 1.2, installed adamcomb. wifi works. I'll start testing other things.
I didn't install clem or pershoot kernel. I'm wondering if the vega/adam teams are using anything from Eduardo's .36 kernel port?
MC

Thanks for the heads up. I'll take a look at it.

MicroChip said:
Ok, I nvflashed back to 1.2, installed adamcomb. wifi works. I'll start testing other things.
I didn't install clem or pershoot kernel. I'm wondering if the vega/adam teams are using anything from Eduardo's .36 kernel port?
MC
Click to expand...
Click to collapse
Great work ! I assume that you are using standard recovery to flash, not CWM1.2 bl friendly ?
Keep us posted with your evaluation, please.
Dave

I used bl 1.2 with cwm. I'm doing testing now. I'm probably going to want to add pershoot kernel but want to test all the other stuff first like flash, youtube, etc...
MC

Adamcomb does work on the gtab, I just installed with cwm, Bootloader 1.2 required, will report later after testing.
.
Thanks

As I suspected, adding pershoot kernel killed wifi. I know which files to move and from where, but will test that later or in the morning.
Once I have that, I don't mind packaging as a rom but could use a little advice (or a wiki somewhere) on how to take the rom, copy pershoot's kernel to it, sort out the meta-inf's or whatever I have to do to get it to install kernel, and rezip it.
If anybody can help me there, I'm willing to start maintaining this rom...
MC

MicroChip said:
As I suspected, adding pershoot kernel killed wifi. I know which files to move and from where, but will test that later or in the morning.
Once I have that, I don't mind packaging as a rom but could use a little advice (or a wiki somewhere) on how to take the rom, copy pershoot's kernel to it, sort out the meta-inf's or whatever I have to do to get it to install kernel, and rezip it.
If anybody can help me there, I'm willing to start maintaining this rom...
MC
Click to expand...
Click to collapse
Can't help but +1 for the effort. I hope you get this going

MicroChip said:
As I suspected, adding pershoot kernel killed wifi. I know which files to move and from where, but will test that later or in the morning.
Once I have that, I don't mind packaging as a rom but could use a little advice (or a wiki somewhere) on how to take the rom, copy pershoot's kernel to it, sort out the meta-inf's or whatever I have to do to get it to install kernel, and rezip it.
If anybody can help me there, I'm willing to start maintaining this rom...
MC
Click to expand...
Click to collapse
Uh... I hope you know how to sign a zip file so it will install in an android device. If not, tell me and I'll add instructions on my website so that everyone can become a dev.

MicroChip said:
As I suspected, adding pershoot kernel killed wifi. I know which files to move and from where, but will test that later or in the morning.
Once I have that, I don't mind packaging as a rom but could use a little advice (or a wiki somewhere) on how to take the rom, copy pershoot's kernel to it, sort out the meta-inf's or whatever I have to do to get it to install kernel, and rezip it.
If anybody can help me there, I'm willing to start maintaining this rom...
MC
Click to expand...
Click to collapse
Best luck to you and wish that you will gain the knowledge somehow to do so. Your initiative to take on this subject is to be complimented.
Meanwhile, our friendly developer tlbardelljr just ported some features from this rom to the Flashback rev 5.3 http://forum.xda-developers.com/showthread.php?t=1138100. However, I hope (perhaps many would agree) that you would continue your path. It is fun and educational anyway.
Dave

goodintentions said:
Uh... I hope you know how to sign a zip file so it will install in an android device. If not, tell me and I'll add instructions on my website so that everyone can become a dev.
Click to expand...
Click to collapse
Great idea. Your works are much appreciated by a great many.
Dave

As I hoped, Zhyong got it done. He's way ahead of me in terms of knowledge and putting roms together.
I found that using Adamcomb by itself didn't cause sleep of death, but when I added pershoot kernel, I got sleep of death and couldn't sort that out. Going to play with Zhyong's bl1.1 and 1.2 versions and try to see how he did it.
His roms based on Adamcomb are in the Rom dev forum here and it's his 3.0.
MC

MicroChip said:
I found that using Adamcomb by itself didn't cause sleep of death, but when I added pershoot kernel, I got sleep of death and couldn't sort that out.
Click to expand...
Click to collapse
Sleep of death is usually due to undervolting. Pershoot's kernel does that. Some tegra-2 cpus can undervolt lower than others. If yours can't, the "sleep of death" is the result.

schettj said:
Sleep of death is usually due to undervolting. Pershoot's kernel does that. Some tegra-2 cpus can undervolt lower than others. If yours can't, the "sleep of death" is the result.
Click to expand...
Click to collapse
Possibly, but it only happens with bl1.2 roms, and not bl1.1 roms. I'm pretty sure zhyong used the same adamcomb base, and pershoot kernel, and made one for bl1.1 and one for bl1.2 and I installed and got no sleep of death on 1.1. I'll try his 1.2 and see if the result is the same.
It would possibly make sense as I think originally roebeet built his 1.2 honeycomb roms with clemsyn kernel and switched to pershoot around his version 4 or 5 and before that I didn't have sod, but even now, if I take adamcomb and put clemsyn kernel on 1.2, I get sod. It definitely seems bl 1.2 related, though I know some people have the problem and some don't.
MC

GtabComb is basically a direct port of AdamComb, but with some very useful gTab optimizations. In my (limited) testing it is fully compatible with other Pershoot kernels as well.

[Q] Help with infusion kernel v1.1

Hey, i am running on infused v2.1.0 and i have transfuzion theme. Anyway i tried to flash the kernel and i thought i did it right went to recovery mode then falsh zip from sd watever then reboot consol. i go back to my About Phone and still no infusion 1.1 it says : Kernel Version 2.6.35.7-I1997RUXKG-3-CL366622... Any help would be appreciated ! Thank you for your time .

IrInfuseD said:
Hey, i am running on infused v2.1.0 and i have transfuzion theme. Anyway i tried to flash the kernel and i thought i did it right went to recovery mode then falsh zip from sd watever then reboot consol. i go back to my About Phone and still no infusion 1.1 it says : Kernel Version 2.6.35.7-I1997RUXKG-3-CL366622... Any help would be appreciated ! Thank you for your time .
Click to expand...
Click to collapse
I'm pretty sure that is the Infusion kernel. If you read the rest it should say [email protected] # infusion gb

I'd suggest downloading Voltage Control and seeing what options you have in there. You'll know you installed it correctly if you see speeds up to 1600 in there. Plus it's a good tool if you want to Under Voltage a little bit to help on battery life.

Kernel Version number is 2.6.35.7-1997RUXKG3-CL366622 for infusion 1.1. Your good.

TheCajun said:
Kernel Version number is 2.6.35.7-1997RUXKG3-CL366622 for infusion 1.1. Your good.
Click to expand...
Click to collapse
Actually that version string is useless for determining which kernel you're running other than "based on Rogers Gingerbread" - since the proprietary Samsung modules force kernel devs to avoid doing anything that modifies that string. (Modify that string = device will not boot.)
The best way to figure out which kernel you're running are:
1) Featureset. If you have frequencies higher than 1200 MHz you're running Infusion as it's the only overclock kernel there is. If you have netarchy-style voltage control but no overclock, you're likely on my Daily Driver. If you have neither, you're probably on Hellraiser or the stock Infused ROM kernel.
2) Build username/host of the kernel to determine who built it. If you look back through my posts you should find one with a list of a few known user/host combos for various kernel devs.

Thanks for the replies guys! I checked in my voltage control i have the 1600mhz in there but i dont really know how to set them... ive looked around i did something but im not sure if thats the best set up. I sitll do not know if i am running on infusion 1.1 i have infused 2.1 for sure but not sure about the kernel. Anyway thanks for the reply guys the help is much appreciated but IF you can help me figure out this voltage thing it'll be great! Also i have downloaded the tranzfusion theme and i dont really like it is there anyway i can delete it?

Entropy512 said:
Actually that version string is useless for determining which kernel you're running other than "based on Rogers Gingerbread" - since the proprietary Samsung modules force kernel devs to avoid doing anything that modifies that string. (Modify that string = device will not boot.)
The best way to figure out which kernel you're running are:
1) Featureset. If you have frequencies higher than 1200 MHz you're running Infusion as it's the only overclock kernel there is. If you have netarchy-style voltage control but no overclock, you're likely on my Daily Driver. If you have neither, you're probably on Hellraiser or the stock Infused ROM kernel.
2) Build username/host of the kernel to determine who built it. If you look back through my posts you should find one with a list of a few known user/host combos for various kernel devs.
Click to expand...
Click to collapse
Sorry didnt know this, thanks for the correction. I dont like giving people bad info.
---------- Post added at 10:05 PM ---------- Previous post was at 09:58 PM ----------
IrInfuseD said:
Thanks for the replies guys! I checked in my voltage control i have the 1600mhz in there but i dont really know how to set them... ive looked around i did something but im not sure if thats the best set up. I sitll do not know if i am running on infusion 1.1 i have infused 2.1 for sure but not sure about the kernel. Anyway thanks for the reply guys the help is much appreciated but IF you can help me figure out this voltage thing it'll be great! Also i have downloaded the tranzfusion theme and i dont really like it is there anyway i can delete it?
Click to expand...
Click to collapse
If you installed 1.1 and voltage control tells you can OC to 1600 then you have 1.1 installed. People use different setups for the Overclocking. use Cfq as scheduler and Ondemand as governor. make sure you turn on 1600 by hitting the red button next to it if you already havent. dont use more than 5-6 mhz speeds at one time. I use 200 400 800 1200 1600.

Just to the OP...the easiest way to me to flash a kernel is simply by downloading SGS Kernel Flasher, selecting the kernel, and flashing it. It's about as painless as you can get.

Thanks for the replies guys much appreciated !

OK my TF101 is now rooted, now what ?

Be gentle
Just been playing with my new TF101, Razorclaw rooted it.
Now I'm thinking, what do I do next
Changemode through ROM Manager ?
Is there custom ROMs out already ?
Can I overclock it
Been though the developers section and I find it a bit confusing now, starting to get old and my brain isn't as sharp That and all the beer last night
So really this is a general question to 'what have you done and why' ?

You can do whatever you want...
ROMS:
-Android Revolution HD
-Prime
-Revolver
-KRAKD
-EeeBomb
Kernels:
-Prime kernel (has Overclock)
-Clemsyn (has OC and Undervolt)
-Blades (OC and UV)
ROMmanager doesn't work with the transformer
For overclocking, install an OC kernel and use SetCPU or No-frills cpu control or a few other that'll find in the market.

Nice thanks will search them out later.

Revolver with blade a good mix ?

Make a backup.

BorgCymru said:
Revolver with blade a good mix ?
Click to expand...
Click to collapse
I tried that combo went back to revolver and prime 2.0.6 kernel
O/C 1.5
I/O sched SIO
Nice and quick with no lag
Sent from my tf101 using xda premium 1.54Ghz

Martijn1971 said:
Make a backup.
Click to expand...
Click to collapse
Yep already done and sat on a spare Micro card and hard drive.

Any of the ROMS have 3G Dongle support built in now ? Would love that. Be very handy.
Thanks

OK I've searched for Prime kernel and it just seems to list loads of un related posts.
Where are the 'kernals' people speak of ?

BorgCymru said:
OK I've searched for Prime kernel and it just seems to list loads of un related posts.
Where are the 'kernals' people speak of ?
Click to expand...
Click to collapse
Goto Post #2 in the Prime ROM thread and you will see the kernel 2.0.6 there I believe that is what everyone is referring to

Cool thanks
I used Revolver parts and used that to install it but my WiFi didn't work with it, so I went to Blade 2. Still can't figure out how to use the 3G dongle though after installing the 3G mod from Revolver parts though.
Many many thanks for replying.

Not able to overclock rooted Tf101 with ANY kernel

Im extremely frustrated...Ive been trying to OC my Tf101 for days now w/ no success. Ive tried several ROMs + kernel(s) and now Ive tried FROZN 1.0.9 because I heard they do GREAT work and the ROM is supposed to include a Guevor Kernel allowing OC, I think to 1.7.
I rooted w/ ViperMOD Prime (latest ver)
I installed CWM (5.5.0.4 I think, latest ver)
I flashed:
[ROM] FROZN 1.0.9 █Apr. 2 2012█ 9.2.2.3 █ ICS for TF █Super-Optimized█ Guevor Kernel
...but when I use the included NoFrills CPU app it will only allow me to clock to 1.000?
What am I possibly missing or not understanding? Is the a Tf101 that is simply NOT capable of OC?
ANY ideas would greatly be appreciated...I am sooo anxious to OC because everyone seems to be doing so with great success.
Thanks all.

fwbflash said:
Im extremely frustrated...Ive been trying to OC my Tf101 for days now w/ no success. Ive tried several ROMs + kernel(s) and now Ive tried FROZN 1.0.9 because I heard they do GREAT work and the ROM is supposed to include a Guevor Kernel allowing OC, I think to 1.7.
I rooted w/ ViperMOD Prime (latest ver)
I installed CWM (5.5.0.4 I think, latest ver)
I flashed:
[ROM] FROZN 1.0.9 █Apr. 2 2012█ 9.2.2.3 █ ICS for TF █Super-Optimized█ Guevor Kernel
...but when I use the included NoFrills CPU app it will only allow me to clock to 1.000?
What am I possibly missing or not understanding? Is the a Tf101 that is simply NOT capable of OC?
ANY ideas would greatly be appreciated...I am sooo anxious to OC because everyone seems to be doing so with great success.
Thanks all.
Click to expand...
Click to collapse
The kernel included with frozn only goes to 1.2ghz and the default clock is 1ghz
Ics testy meh sio init.d kernel goes to 1.6 i would try that one
Sent from my Transformer TF101 using XDA Premium HD app

ok mate...that one sounds a bit better to me for the final number, however I cant get mine to clock past 1.000 at all. Ive tried ROMs + kernel(s) and Ive tried ROMs w/ kernel included, install goes fine but when I try to OC w/ CPU app, it only goes to 1.000.
I thought I was reading someone else w/ this problem and the issue revolved around a botched recovery flash or something?...but I cant seem to find that thread again. I did try to unsuccessfully flash back to stock ASUS recovery a while back, didnt work (CWM was still present afterwards). Wonder if that is creating an issue of some kind?...although I am struggling to imagine what one would have to do w/ the other.
Thanks for the reply mate...Im willing t listen to ANY ideas at this point!

"The kernel included with frozn only goes to 1.2ghz and the default clock is 1ghz"
BTW...wanted to check on the FROZN OC kernel abilities...the latest FROZN ver sets CPU default at 1.2 and allows OC to 1.7. But anyhow, only allowed me 1.000 default and no OC.

Yeah I'm on frozen oc'd at 1.4. Your issue is weird I've never heard of that before. What happens if you select anything higher than 1.0, do you get an error or anything?
Sent from my Transformer TF101 using Tapatalk

I dont even get the option to go higher than 1.000.

UPDATE: apparently this inability to OC the kernel in any way is happening to those of us experiencing the CWM bootloop issue...so since the loader goes immediately to CWM it never runs the flashed kernel.
So in these forums is a thread to fix the CWM bootloop and if you follow the instructions carefully, you fix the bootloop and thus allowing the flashed kernels a chance to actually install. I chose the Roach method which you can install the code using Terminal Emulator pretty intuitively. I didnt choose the other method because I didnt want to mess w/ setting up an ADB terminal on my PC, which seemed MUCH more difficult.
So...now FINALLY
ViperMOD Prime rooted
ClockworkMOD Touch Recovery 5.8.8
FROZN 1.0.9 ROM (w/ built-in Guevor kernel @ 1.2 default) and am OCd @ 1.54 (np's at all so far, lightning fast, havent even tried 1.6 or 1.7).
Only issue so far is File Manager app crashes on startup...which isnt good because now the other file manager app I tried doesnt see my ext_SDcard...the stock File Manager did.

fwbflash said:
ok mate...that one sounds a bit better to me for the final number, however I cant get mine to clock past 1.000 at all. Ive tried ROMs + kernel(s) and Ive tried ROMs w/ kernel included, install goes fine but when I try to OC w/ CPU app, it only goes to 1.000.
I thought I was reading someone else w/ this problem and the issue revolved around a botched recovery flash or something?...but I cant seem to find that thread again. I did try to unsuccessfully flash back to stock ASUS recovery a while back, didnt work (CWM was still present afterwards). Wonder if that is creating an issue of some kind?...although I am struggling to imagine what one would have to do w/ the other.
Thanks for the reply mate...Im willing t listen to ANY ideas at this point!
Click to expand...
Click to collapse
Tried flashing rogue recovery???
Sent from my Transformer TF101 using XDA Premium HD app

Overclock up to 1.6 - 1.7ghz
I just share with u how i overclock my tf101 upto 1.7ghz with stock rom....ALL ASUS APPS IS WORKING
- i root my device with ViperMod prime v5.4 (choose option 1)
http://forum.xda-developers.com/showthread.php?t=1427125
- then, install rom manager from android market (to flash clockworkmod recovery). i am using standard recovery, not the touch recovery...u all can try if u want.for me its doesn't matter.
http://www.clockworkmod.com/rommanager
-lastly, i flash the kernel 9b(by using clockworkmod recovery)...u can get the latest kernel from here:
http://forum.xda-developers.com/showthread.php?t=1565519
- currently, i can overclock my tf101 up to 1.7ghz with beloved stock rom..
- antutu benchmark 76++....
hopefully its helpful......enjoy your enthusiant tf101 speed...

I cant talk from experience, but Ive read at several places that ROM manager is NOT recommended to use.
How, when or why I do not know. Theres another app thats recommended for the TF, simply called "recovery installer". Its listed in the epic noob guide.
As I said, Ive only read that rommanager isnt recommended for the tf.