Database Info

[KERNEL/GPL/Sense]ScaryKernel 1.8 super uv/oc/uc/smartass/scary governor/bfq

PaulB007 said:
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Click to expand...
Click to collapse
Link to bcnice20's 1.5ghz kernel: http://forum.xda-developers.com/showthread.php?t=941728
If that doesn't work, try flashing over his 1.8ghz kernel(This is what worked for me, bcnice, if you want me to take down this link just let me know.) - http://thebcblends.com/shift/kernels/Sense-1.8ghz-bfq-test1.zip
Table of contents:
Intro
Features/what this includes
Why it's labeled unstable
Disclaimer
Latest kernels
Instructions for using swap
Governor exlainations
Governor strategies
Recommended apps
Locating cpu% Eaters && other negative items towards battery life
FAQ!
Changelog
Stable/safe voltage kernels
Notes
Source
Credits
Intro: I'm scaryghoul.
What this includes
Swap
BFQ I/o scheduler
Extreme undervolt
Overclocked & underclocked values
HW3D enabled
Sleepers disabled
Smartass governor
New Scary governor!
Tweaked conservative governor
and much more(All of bcnice20's kernel)
Why it's labeled unstable: So I don't get people poking me in the eyes with spoons if/when it freezes up. It actually works quite well, but since I heavily undervolted an undervolted kernel, it is bound to not be 100% stable(It is about 90% stable =P)
Disclaimer: What everyone else puts in kernel threads, about me not being responsible, ect.
Latest kernels
The voltages of the superUV will not work for everyone, if they don't work for you, then try the builds labeled stable
Recommended speeds 245-800mhz or 245-1ghz on scary governor && no setcpu profiles
Scarykernel 1.8 suv - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Suv.zip
Scarykernel 1.8 stable undervolt - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Stable.zip
Instructions for using swap
For a swapfile do something like this.
dd if=/dev/zero of=$Swapfile bs=1048576 count=$Size
Where $Swapfile is the location of the file you want, and $Size is the amount of mb for swap you want to use.
Then type
mkswap $Path
swapon $Path
Replacing $Path/$Size with your own values of course, so if I wanted 20mb of swap I'd execute the commands
dd if=/dev/zero of=/sdcard/swapfile bs=1048576 count=20
mkswap /sdcard/swapfile
swapon /sdcard/swapfile
Governor exlainations
Toasty makes one transition to the max speed and stays there(benchmarks only usually)
Batterysave! sits at the bottom and when the cpu load increases past the threshhold it scales up to the next speed and takes another load sample and keeps doing that(best on battery life/performance ratio)
Ondemand sits at the bottom and when the cpu load increases past the threshhold, it scales ot the max speed then takes another load sample and scales down accordingly
Powersave makes one transition to the bottom speed and stays there
Smartass(Quoted from another author http://www.ziggy471.com/2010/11/07/smartass-governor-info ) - "is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
Governor strategies
Conservative - Upthreshold 85, downthreshold 60
Smartass - Sleep max 245760Hz, Ramp up at 384000Hz at a time, up threshold 90, downthreshold 60
Scary - Upthreshold 80, down threshold 45, sleep max 245760Hz, sleep min, 122880Hz
Recommended apps =)
Zdbox - Great toolbox app, just don't let it run in your notifications bar, it's a cpu eater
Setcpu/Nofrills - Apps that help manage your cpu/profiles/ect.(I don't use them but they're pretty okay)
Perfect system or Elixer widgets - Widgets that monitor battery, current, cpu%, cpu speed, and more(Great for battery guru's)
Adw ex - Smoothest/fasted/lightest ratio in a launcher I've seen so far, and least cpu intensive(for me that's a big thing so the cpu scales less)
Colorize widgets - Great widgets to replace the lpp ones for those converting to other launchers.
AppMonster(pro or free) - Great backup utility, automatically backs up all apps.(I like it better than TB)
GPS Status - Great application for finding satalites near you and helping get a quick lock.
Any go dev team app - Great dev team, all their apps are worth looking at.
Frequently asked questions
Question: My phone is boot looping/not booting on the released suv, what do I do?
Answer: Your phone cannot handle the super undervolted values, you will need to flash the stable undervolted kernel
Question: My phone is running slow on the batterysave or scary governors, what do I do?
Answer: Set your minimum speed higher, those governors spend a lot of time at the lowest values
Question: How do I flash this?
Answer: You probably shouldn't be flashing one of my kernels if you don't know how(Mine are unstable =P)
Question: I'm not getting the amazing battery life/benchmark scores that others are getting
Answer: Well, every device is different, so you may not be able to score as high as some others, but you should get close at least, and the battery completely depends on usage patterns
Question: My phone can't clock to 1.8ghz, or some of the other higher values but does fine on the lower ones
Answer: Every device is different and not all can handle the same speeds/voltages, you are probably better off staying away from the higher speeds, I enabled the speeds but hope that you all are mature enough to handle them
Locating cpu% eating applications.
When in ADB shell type the following
top |grep app
Then look for items with high amounts of cpu% while the phone is idle.

Changelog
v1.8 - Initial kernel release for sense
Safe voltage kernels
v1.8
Scarykernel 1.8 stable - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Stable.zip
Notes:
No I can't take the overclock any higher, I think everyone who's had a chance to take a crack at this source has tried, and going any higher seizes up after a few seconds.
Here is the source code for this build. I'll try to maintain it, I have a lot of kernel sources, but this will always be the latest release code, unless I state otherwise.
https://github.com/Scaryghoul
Credits: bcnice20 - For 99.8% of his kernel source.
Dogejcr/Preludedrew - For helping me get my laptop setup for kernel compiling.
Testers - For flashing this even though it says unstable :-X
JoesephMother - For helping me unlock the new lower clock values && other kernel related matters =)
x99percent - I used his middle clock speeds between the 3xx->7xx values as a base(edited voltages) as well as used his smartass source.

I see nobody else has chimed in on this kernel yet.. I will install Mikshift tomorrow and report my findings.

Bummer, my phone is a wuss! I can't boot either one of these. Just sits on white screen. They look cool as hell though.
Sent from my PG06100 using Tapatalk

Yeah both versions don't work on mine.

If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.

Tried going strait from BC's still no go.
Sent from my PG06100 using Tapatalk

ozzie1p said:
Bummer, my phone is a wuss! I can't boot either one of these. Just sits on white screen. They look cool as hell though.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Did you flash over bcnice20's kernel?
PaulB007 said:
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Click to expand...
Click to collapse
Thanks for clarifying that, I took down the links until we can get this working on several devices.
ozzie1p said:
Tried going strait from BC's still no go.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Did you try both of them over bcnice20's 1.5ghz? Not everyone can handle the suv one.
edit: Links back up! I need some testers to try the fix at the top.

Ya, I flashed right over the top of bc's. Ill try these new ones.
Sent from my PG06100 using Tapatalk

Scaryghoul are the reposted links any different than the old kernels you had up the first time? If not, the suv build would boot and run, but after using the phone after awhile for cpu intensive tasks it would lock up and require a battery pull. Im wondering if just a tiny bit more voltage would solve this problem.
On the stable build, it would run a minute or so and always lock up and require a battery pull..

PaulB007 said:
Scaryghoul are the reposted links any different than the old kernels you had up the first time? If not, the suv build would boot and run, but after using the phone after awhile for cpu intensive tasks it would lock up and require a battery pull. Im wondering if just a tiny bit more voltage would solve this problem.
On the stable build, it would run a minute or so and always lock up and require a battery pull..
Click to expand...
Click to collapse
Same links....and I see. If the stable build has the same issue as the suv, then it's not the voltage >.<

Oops. Thought they were new. At least I got the flash bug scratched. Flashed over both bc 1.5 and 1.8, no go.
Sent from my PG06100 using Tapatalk

Scaryghoul said:
Same links....and I see. If the stable build has the same issue as the suv, then it's not the voltage >.<
Click to expand...
Click to collapse
Whats the suspected culprit?

ozzie1p said:
Oops. Thought they were new. At least I got the flash bug scratched. Flashed over both bc 1.5 and 1.8, no go.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
PaulB007 said:
Whats the suspected culprit?
Click to expand...
Click to collapse
I don't know so much for the freezes, but I believe that the booting has to do with me using my old voltages, and sense handling things differently than aosp >.<
I'll redo the voltage table later.

Just Wondering?
When Source Code is released will you make a suv kernel for the Gingerbread Update i loved it on froyo and mikshift and gave great battery life.

notsointeresting said:
Just Wondering?
When Source Code is released will you make a suv kernel for the Gingerbread Update i loved it on froyo and mikshift and gave great battery life.
Click to expand...
Click to collapse
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).

Scaryghoul said:
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Click to expand...
Click to collapse
Ah ok that sucks was really hoping for it but I understand thanks for the fast reply

Scaryghoul said:
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Click to expand...
Click to collapse
The ndk from google's web site has the toolchains needed to build gb kernel in it. The dl isn't terribly huge.
Sent from my PG06100 using XDA Premium App

[Q] Tiamat Kernel Question

I have been looking for a couple of days, and I can't seem to find my answer anywhere. Sorry if this question has already been asked. Does the Tiamat Kernel come overclock already, or do you need to use an app like SetCPU?

SetCPU is needed

Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.

anovinger said:
Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.
Click to expand...
Click to collapse
If you do not run an overclock program, the stock max is still on the CPU.
Sent from my Xoom

Do you know what the set Max is on the tiamat kernel?

anovinger said:
Do you know what the set Max is on the tiamat kernel?
Click to expand...
Click to collapse
1ghz
Sent from my Xoom

bwcorvus said:
1ghz
Sent from my Xoom
Click to expand...
Click to collapse
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?

Bandit504 said:
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?
Click to expand...
Click to collapse
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100

bwcorvus said:
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100
Click to expand...
Click to collapse
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?

Bandit504 said:
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?
Click to expand...
Click to collapse
Yea setcpu is not 100% yet. Does your widget show both cpus? What we were testing was the second CPU. After you xoom goes to sleep, the second CPU is never set again by setcpu (known bug). So lets say you are running 1.0/1.5. After you xoom goes to sleep you will wake up with cpu 0 at a max of 1.5, but cpu 1 will have a max of 1.0. The info i gave earlier was said wrong. I was actually looking at the wrong line, so you may in fact be correct on the 1.5ghz random jump . Gonna stop talking now, as we are hyjacking someone else's thread .
In theory, you should not need overclocking software, as the max is set at 1ghz on both cpus. But as said above by Bandit504, this may NOT be the case .

Thanks bwcorvus and Bandit504 . So I guess to call it is safe, it would be good idea to use SetCPU, or Droid Overclock and have the maximum set to 1 ghz, to keep the proc from hitting the 1.5 ghz speed. I just hate to ruin the hardware with the overclock, and have to drop another $600 for another xoom.

[Q] Random Reboot with +1.5Ghz OC Kernels

Ok, sorry if this seems like a stupid question but... I have flashed/tested all of the Tiamat Kernels onto my xoom and it seems that I can only run the 1.4 Ghz Kernel with no random reboots. So I thought that if i download the higher 1.5Ghz or the 1.6Ghz and just under-clock it to 1.4Ghz that should stop it from doing random reboots, but sadly it doesnt and I still get random reboots even with Setcpu Under-clocking it to 1.4Ghz. Now is this typical or am I missing or misunderstanding something? Is there a reason why I cant use the higher Kernels and Under-clock them to 1.4Ghz and get no random reboots? I am only asking because I flashed the Riptide and under-clocked it to 1.4Ghz and it really made my xoom feel much faster and nicer in my hands and would love to keep using the Riptide Kernel.
Thanks in advance,
-Dez

I have the same issues and have been wondering the same thing.

I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !

nexan21 said:
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
Click to expand...
Click to collapse
I too have noticed this, after reading your post I tried keeping the Kernels but with no OC and left it at 1.0Ghz and it still has random reboots. So is there something in the Higher Kernels that are causing it to be unstable regardless of what Ghz you clock it to?

watch setcpu at times. It doesn't matter what you set the clock at in setcpu it will still go to the max clock the kernel allows. I am not sure if it is a bug with setcpu or if it is just the way the kernel works. If you reboot your Xoom when setcpu is at 1ghz, then go and play with the xoom after reboot for awhile. Go back into setcpu and look under the info tab. You will see that the cpu has indeed been running the higher clocks then 1ghz at times. It doesn't run those higher clocks much but it does. Which is most likely why you are getting lockups or reboots. My Xoom seems to love the 1.5ghz kernel but hates the 1.6ghz one.

Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk

tribalb said:
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The oc is in the kernal i think , i dont have setcpu installed but cpu still at times peaks at the max 1.504 ghz ac ording to
"Temp+cpu"
https://market.android.com/details?id=com.sanels.tempcpuv2&feature=more_from_developer

[Q] How to test if an OC works on the TF?

I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..

acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
I've found that, in overclocking several Android devices, more often than not if you have an unstable OC, the device will either fail to boot, or will crash constantly. If it's not doing that, you're likely fine.

Um, you're not OCed yet. You need to install setcpu or cpu master and crank up the clock. Clemsyn or Blades gives you the option to OC. It doesn't just OC for you.

lol, and learn from my mistake: when overclocking, don't check the option of "set on boot" untill you have tried overclocking at the Ghz level that you want to use. Believe me, you don't want a bootloop that can only be solved by flashing or restoring from a backup.

acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
I have done extensive overclocking and undervolting.
Set your OC and voltage settings. Then use setcpu or pimpmycpu min and max to your highest OC MHz.
Then play 1 round of Dungon Defenders. If you make it through that then open the camera.
Repeat this on every MHz from top to bottom. If you are unstable at a frequency then increase your voltage slightly (like 10 - 20 mV) and try again.
If you are stable and want to get a little bit better battery do the same thing but lower the mV until dungeon defenders crashes.
Then start to increase it until you are stable.
If your tablet reboots your way low on mV
If it freezes your low on mV
If the widgets act funny, and/ or disapear every once in awhile your in the right ball park
If everything works except your camera freezes you are very close
Some kernels have more aggressive GPU timings which you can't really change so you might want to try another's kernel if you can't get stable.

Well, it seems that I can't go higher than the 1.2 GHZ. If I go any higher, I get some weird freezes and reboots.
Now I saw the post above but I dont see where I can adjust the different voltages, etc..Maybe I am not using the right program?

acdcking12345 said:
Well, it seems that I can't go higher than the 1.2 GHZ. If I go any higher, I get some weird freezes and reboots.
Now I saw the post above but I dont see where I can adjust the different voltages, etc..Maybe I am not using the right program?
Click to expand...
Click to collapse
What program are you using? Try SetCpu or Pimpmycpu

baseballfanz said:
What program are you using? Try SetCpu or Pimpmycpu
Click to expand...
Click to collapse
SetCPU is what I loaded

acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
Are you referring to this kernel?
I'm wondering because I have never heard about a "Blades 2" kernel.
EDIT: Nevermind, I figured it out. This is what Revolver Parts calls Blades' 10-01-2011 kernel.

Blades uses some aggressive GPU timings in some of his kernels. You may want to try Clemsyn 22 if you want to try and go above 1.2 GHz.

[Q] Some nonspecific whining about performance...

Hey all -
I have been a Transformer (and modding) fan since my TF101, and I just leapt from a TF201 to the infinity.
I'm not sure quite what I was expecting, but I surely wasn't expecting it to be slower. Responses to screen taps and swipes are very delayed, to the point where it's extremely annoying.
This is all subjective, I realize, but I was wondering if this is a widespread thing or if I should try to RMA it.
I had heard that CROMi-X was the rom to have, so I flashed 4.6.7.
I had also heard that the GPU was an ass-kicker, so I put on my favorite piece of eye-candy (that I've purchased) which is "Asphalt 7: Heat." - and it ran DOG SLOW, and wasn't particularly candy-ish.
Well, maybe that's an exaggeration, but having the 201 and 700 side-by-side (literally, driving one with each hand, and poorly at that) the 700 was choppy and would pause every so often. It took MUCH longer to load, too.
So I was unhappy.
I read about the slow internal I/O and re-flashed with a Data2SD option, formatted the microcard, the whole nine yards, and it didn't really get any better. fsync is turned OFF.
I side-graded to the older CleanROM Inheritance 3.4.7, and it actually seems SLIGHTLY better, but the UI has a tendency to be very laggy.
I'm going to try "AndroWook" next, I had that on my Prime with good success.
I've googled and found plenty, plenty plenty of people who have a problem with the TF700 and its speed, which is really disappointing because it's supposed to be the top of the line.
So.. is anyone out there really HAPPY with their TF700? Is it zippy and satisfying? What ROM are you using?
Maybe I'll try to unload it on craigslist and go back to the TF201. It has lower "Androbench" marks, but is crazy more responsive.
*shrug*
I'd love to hear anyone's thoughts...
R

Just learned about 'lagfix.'
Gonna try that.
Is 4.1.1 better performance? I realize it'd technically be a step backwards...

rprussell said:
Just learned about 'lagfix.'
Gonna try that.
Is 4.1.1 better performance? I realize it'd technically be a step backwards...
Click to expand...
Click to collapse
I'm still using 4.1.1. I run Cromi 3.4.6 with Hund's kernel 2.2, along with most of the tweaks found here (http://forum.xda-developers.com/showthread.php?t=2232715). I am not running data2sd and my CPU/GPU profiles are not as aggressive. Apparently some people have been getting bootloops after applying these tweaks but I've never had it.
I've tried 4.2 several times (with different versions of Cromi-X) but usually come back to 4.1.1 within a day because it seems to run better.
Having said this, I think "lags" can be quite subjective - I personally think my tf700 is zippy but perhaps you wouldn't agree.

rprussell said:
Hey all -
I have been a Transformer (and modding) fan since my TF101, and I just leapt from a TF201 to the infinity.
I'm not sure quite what I was expecting, but I surely wasn't expecting it to be slower. Responses to screen taps and swipes are very delayed, to the point where it's extremely annoying.
This is all subjective, I realize, but I was wondering if this is a widespread thing or if I should try to RMA it.
I had heard that CROMi-X was the rom to have, so I flashed 4.6.7.
I had also heard that the GPU was an ass-kicker, so I put on my favorite piece of eye-candy (that I've purchased) which is "Asphalt 7: Heat." - and it ran DOG SLOW, and wasn't particularly candy-ish.
Well, maybe that's an exaggeration, but having the 201 and 700 side-by-side (literally, driving one with each hand, and poorly at that) the 700 was choppy and would pause every so often. It took MUCH longer to load, too.
So I was unhappy.
I read about the slow internal I/O and re-flashed with a Data2SD option, formatted the microcard, the whole nine yards, and it didn't really get any better. fsync is turned OFF.
I side-graded to the older CleanROM Inheritance 3.4.7, and it actually seems SLIGHTLY better, but the UI has a tendency to be very laggy.
I'm going to try "AndroWook" next, I had that on my Prime with good success.
I've googled and found plenty, plenty plenty of people who have a problem with the TF700 and its speed, which is really disappointing because it's supposed to be the top of the line.
So.. is anyone out there really HAPPY with their TF700? Is it zippy and satisfying? What ROM are you using?
Maybe I'll try to unload it on craigslist and go back to the TF201. It has lower "Androbench" marks, but is crazy more responsive.
*shrug*
I'd love to hear anyone's thoughts...
R
Click to expand...
Click to collapse
It is odd. With what you said, your TF700 should be very smooth unless there is a hardware problem Did you try a clean install? BTW, if you reinstall again, I would recommend that you should use Cromi X V4.6.5 instead of 4.6.7.
For some reason when I used the Advanced Wipe and wiped everything in TWRP. I still found some old files on my internal SD. However, when I used a formatted option, everything was gone and clean. Maybe you should do that. Also if you use Data2Ram, you should reformat your MicroSD as the same time with your clean install. A combination of Fsync Off, D2R, and Cromi X should work very well. My kernel is Hund's V3.0.6 with OC of 1.4G CPU, 520M GPU for Power Saving, 1.6G CPU, 600M GPU for Normal, and 1.8G CPU, 650M GPU for my Performance with UV about 35mV. My quandrant scores are 5800 for Power Saving = Game Mode, 6400 for Normal = Normal Activities, and 7000s for Performance = Browsing and streaming movies. Please report back if you decide to do a clean install, thanks and good lucks.

Here are my settings and quadrant scores using Hund 2.2:
Power Saving - GPU 650Mhz, CPU 1.45/1.4Ghz - Quadrant 5331
Balanced - GPU 700Mhz, CPU 1.65/1.6Ghz - Quadrant 6336
Performance - GPu 775Mhz, CPU 1.85/1.8 Ghz - Quadrant 7005
Personally I take the quadrant scores with a grain of salt because I've had setups where the scores were better but the tablet was not as responsive. I mostly run on Power Saving mode without any problems.

LetMeKnow said:
Did you try a clean install? BTW, if you reinstall again, I would recommend that you should use Cromi X V4.6.5 instead of 4.6.7.
Click to expand...
Click to collapse
Several totally clean installs at this point.
AndroWook was bust, it didn't even get past the "ASUS" logo.
I'm back to Cromi 3.4.7 with _that's kernel 3.1.10. A lot of folks are mentioning Hund 2.2, perhaps I'll try overlaying that now.
Drenus said:
Having said this, I think "lags" can be quite subjective - I personally think my tf700 is zippy but perhaps you wouldn't agree.
Click to expand...
Click to collapse
I totally agree. I added a bunch of the PimpMyRom tweaks and rebooted. I'm letting it settle down and then going to see what's what.
I can't get the GPU overclock to take, though. I think I've mounted the FS r/w and I'm editing the GPU cap files to contain 1460 as directed, but the next time I open the file it's back to 1300. Weird.
So, my Quadrant score after all the tweaks were put in, on "Balanced," is 5266. On "Performance," it's 5139.
Erugh?

rprussell said:
So, my Quadrant score after all the tweaks were put in, on "Balanced," is 5266. On "Performance," it's 5139.
Click to expand...
Click to collapse
Strange. I get 5200 in balanced mode without any special tweaks, and over 6000 in performance mode with fsync off.
The general user experience is acceptable, but not exceptionally smooth - lost frames in animations are common, but there are no long waiting times anywhere.

_that said:
Strange. I get 5200 in balanced mode without any special tweaks, and over 6000 in performance mode with fsync off.
Click to expand...
Click to collapse
Did I mention I also have fsync off?
('Coz I do.)
Maybe it's faulty, which would make me sad because I doubt I can return it what with unlocking and flashing the crapola out of it. Hm hm.

rprussell said:
I can't get the GPU overclock to take, though. I think I've mounted the FS r/w and I'm editing the GPU cap files to contain 1460 as directed, but the next time I open the file it's back to 1300. Weird.
So, my Quadrant score after all the tweaks were put in, on "Balanced," is 5266. On "Performance," it's 5139.
Click to expand...
Click to collapse
That is really odd. Unfortunately my knowledge of tweaking is entirely based on following other people's instructions so I don't know why the GPU changes are not taking. Are your CPU changes taking? Did you follow the instructions on init.d scripts/enabling his voltage table and governor tweaks?
Here's are my cpu.sh files. I switched the profile for powering saving mode and balanced mode because the tablet always defaults to balanced mode.
-----------------------
Also, when I made the profile too aggressive (too high on CPU or GPU), the tablet got way hot and my quadrant score dropped. Since our tablets are all different on the amount of overclocking they can handle, maybe you're pushing your tablet too much. Have you tried easing down on overclocking?

Drenus said:
Here are my settings and quadrant scores using Hund 2.2:
Power Saving - GPU 650Mhz, CPU 1.45/1.4Ghz - Quadrant 5331
Balanced - GPU 700Mhz, CPU 1.65/1.6Ghz - Quadrant 6336
Performance - GPu 775Mhz, CPU 1.85/1.8 Ghz - Quadrant 7005
Personally I take the quadrant scores with a grain of salt because I've had setups where the scores were better but the tablet was not as responsive. I mostly run on Power Saving mode without any problems.
Click to expand...
Click to collapse
LOL I totally agreed with on that. :laugh: However, I still think that it is better with some numbers as references others than words lags, smooth, choppy, slow, fast, and so on. :good: It is just my way of explanations.

This might be my final entry - after doing the PMR tweaks, and flashing Hund 2.2 (no offense, _that ) the Quadrant score in Performance mode is ... uh.. well, indeterminate because suddenly I can't attach to our wifi. Sigh. Perhaps I overtweaked.
Although, Asphalt ran VERY smoothly. I credit the GPU overclock, in combination with assigning all the 2D stuff to the GPU.
Yeah, definitely. After flashing hund 2.2, it won't acquire an IP address.
Today is surely an interesting day.

rprussell said:
This might be my final entry - after doing the PMR tweaks, and flashing Hund 2.2 (no offense, _that ) the Quadrant score in Performance mode is ... uh.. well, indeterminate because suddenly I can't attach to our wifi. Sigh. Perhaps I overtweaked.
Although, Asphalt ran VERY smoothly. I credit the GPU overclock, in combination with assigning all the 2D stuff to the GPU.
Yeah, definitely. After flashing hund 2.2, it won't acquire an IP address.
Today is surely an interesting day.
Click to expand...
Click to collapse
You probably have problems because of PMR tweaks I remember I also had wifi issues after PMR and I think I didn't enable all the tweaks in the guide. Try PMR recovery where it restores all your previous settings-it should restore your wifi. If not, then maybe a clean install of Cromi and then doing the init.d/Hund/CPU/GPU tweaks should give you quite a bit of performance boost.
Hope by "final entry" you don't mean you're giving up!

Drenus said:
You probably have problems because of PMR tweaks I remember I also had wifi issues after PMR and I think I didn't enable all the tweaks in the guide. Try PMR recovery where it restores all your previous settings-it should restore your wifi. If not, then maybe a clean install of Cromi and then doing the init.d/Hund/CPU/GPU tweaks should give you quite a bit of performance boost.
Hope by "final entry" you don't mean you're giving up!
Click to expand...
Click to collapse
Yeah, it seems as if the "Fast DNS" internet tweak means it has somehow thrown off DHCP.
I'm connected to the wifi AP, but I get no IP address, etc.
I guess I'll flash the recovery thing. Darn, everything but that was working great
No, I had meant to say 'final entry' insofar as I was finally happy with it - but while i was typing it, I wanted to put in the Quadrant score, and then I realize I couldn't connect to the website, and then I realized I had no IP, and here we are.
So that post sort of morphed as I was typing...

rprussell said:
I guess I'll flash the recovery thing. Darn, everything but that was working great
Click to expand...
Click to collapse
Huh.
Wont' flash, at least not with twrp 2.4.4.0
Growf.

rprussell said:
Huh.
Wont' flash, at least not with twrp 2.4.4.0
Growf.
Click to expand...
Click to collapse
Which is just as well, since when I rebooted I had an IP again.
Recovery image went south too, and I had to re-flash that via adb.
There is truly some weird stuff happening here.
Anyway, the quadrant score - now on "Performance" because I swapped cpu2 and cpu3, what a great idea - is...
IS.....
IS.....
5057.
Ah, the hell with it.

rprussell said:
Which is just as well, since when I rebooted I had an IP again.
Recovery image went south too, and I had to re-flash that via adb.
There is truly some weird stuff happening here.
Anyway, the quadrant score - now on "Performance" because I swapped cpu2 and cpu3, what a great idea - is...
IS.....
IS.....
5057.
Ah, the hell with it.
Click to expand...
Click to collapse
Wow, that is just odd. Does the tablet get really hot when you run quadrant? It might be that the GPU/CPU settings are too high. Hope actual performance is still working out for you.
And as for recovery, I meant running the rescue package inside PMR that "un-pimps" the rom. Thinking back on when I installed the tweaks, I think I did everything mentioned in PMR except for Network & Internet mods. And I love the xloud mod!

Drenus said:
Wow, that is just odd. Does the tablet get really hot when you run quadrant? It might be that the GPU/CPU settings are too high. Hope actual performance is still working out for you.
And as for recovery, I meant running the rescue package inside PMR that "un-pimps" the rom. Thinking back on when I installed the tweaks, I think I did everything mentioned in PMR except for Network & Internet mods. And I love the xloud mod!
Click to expand...
Click to collapse
It was pretty warm, yeah. I knocked the cpu back from 1900mhz to 1800mhz - which doesn't seem to matter since according to the little floating CPU monitor I have ("Cool Tool") it's never going over 1600mhz anyway.
I mean, I've got PMR trying to control stuff on one hand, the built-in "Power Saving/Balanced/performance" thing on the other, and also "Trickster Mod"
Idunno.
It does seem perkier after all this, so maybe it doesn't matter.
I wish Quadrant would let me see my score without hitting the internet though. I backed off the voltages by 0.025v per speed, and came up with 5499 this time. Although I don't know whether that's "performance" or what.

rprussell said:
It was pretty warm, yeah. I knocked the cpu back from 1900mhz to 1800mhz - which doesn't seem to matter since according to the little floating CPU monitor I have ("Cool Tool") it's never going over 1600mhz anyway.
Click to expand...
Click to collapse
Did you use Hundsbuah's app to set whatever parameters need to be set?
Sorry for not being more specific, I have no experience with it, I just know Hundsbuah didn't only add awesome overclocking features into his kernel, but he also wrote an app to control it.

rprussell said:
I mean, I've got PMR trying to control stuff on one hand, the built-in "Power Saving/Balanced/performance" thing on the other, and also "Trickster Mod"
Click to expand...
Click to collapse
And this is in addition to changing cpu#.ch files? I wonder if you've got too many cooks in the kitchen.
rprussell said:
It does seem perkier after all this, so maybe it doesn't matter.
I wish Quadrant would let me see my score without hitting the internet though. I backed off the voltages by 0.025v per speed, and came up with 5499 this time. Although I don't know whether that's "performance" or what.
Click to expand...
Click to collapse
Is Asphalt still running better than before? I think the most important thing is that the applications you use are running smoothly and not upsetting you that (1) you spent $$$ on the tablet, (2) you spent a lot of time tweaking the tablet, and (3) you're not getting the performance you want.
I once spent a few hours tweaking CPU/GPU to figure out how I can maximize Quadrant score and what I came away from it is that high score doesn't matter if the tablet is getting way to hot for comfort and that low score doesn't matter if the tablet is running to my satisfaction. I almost never change my power setting and that means my score is probably around 5300, but I still like how the tablet responds.
Anyways, hope your tablet's running better than before and good luck with any additional tweaking! :victory:

_that said:
Did you use Hundsbuah's app to set whatever parameters need to be set?
Click to expand...
Click to collapse
Well.. that's just madness.
No, I was not. I had these other tools and was messing with those.
Might be time to re-flash the kernel again.