Database Info

[APP] NovaFreq v1.2.1 (For Novatek Panels Only) [ Updated 07/18/10 ]

Evo Switch v1.1.1 NovaFreq v1.2.1
(APP NAME CHANGED TO SOMETHING MORE APPROPRIATE)
This is an Android application developed to change the panel frequency for Novatek Panels for the Sprint HTC EVO 4G, in conjunction with ffolkes' Novatek Kernel and netarchy's Kernel,
and any kernel that has maejrep's T2 Interface built in. Every device is different, and with that, those specified kernel's default settings may or may not be optimized with your device.
With this application, you can change those settings on the fly and find the best setting for your device.
[ Please use this application with extreme caution! I am not responsible for any damage this may cause to your device. ]
Requirements:
-HTC EVO 4G
-Android 2.1 +
-Any custom kernel that is built off of toastcfh's htc source
-Novatek Panel
-Root Access
Uses:
-Use as an fps frequency turbo switch for when you need extra fps.
-Use as a debugging tool to test frequencies.
-Use to keep frequency settings even beyond reboots. (new)
Settings:
-340 [Stock] is how HTC intended the EVO to be. This frequency works out to 61hz, but we are capped at 30hz.
-370 [Kernel Default] sets the panel frequency lower than stock, yet provides most around 55fps.
-250 [Stable High Freq] sets the panel frequency higher than stock, which usually gives around 40fps.
-400 [Stable Low Freq] - V2's setting.
-Favorite Setting - Find the most stable setting, and if it's not one of the listed, then "Set Favorite".
-Sticky Settings - Now you can reboot and not have to re-apply your settings!
Custom Setting:
You can put arbitrary settings here, but be warned this may mess up your screen, but usually you can reboot your phone
to change it back to default. Minimum Recommended: 250 Maximum Recommended: 999.
Please do not go lower then the minimum recommended of 250, nor higher than the maximum recommended 999.
To Do:
-Favorite Setting - So you can save the best setting for your device. 07/04/10 - Done!
Change Log:
-Changed app name from Evo Switch to NovaFreq (Novatek Frequency / Freek)
-Totally redid code, should be more optimized.
-Frequencies stick beyond a reboot
-Changed a few of the defaults
-Changed back sleep time to 500ms so the current displayed setting can update (v1.2.1)
Don't be alarmed if you see NovaFreq running in the background. To be able to sticky settings beyond a reboot, NovaFreq has to be run at boot up.
After that you can kill NovaFreq if you want, android will kill it when needed so don't worry.
Thanks To:
ffolkes, netarchy, maejrep, toastcfh, halfline, Cicitrize, geyes30, kpkimmel, joeykrim, and many others involved in trying to uncap the EVO.

Reserved...

Reserved again.

woah, this is badass. I will check it out soon

works great! Whats the number I set it at to equal the V2 setting of ffolkes kernel? I think its 400, is that correct?

Awesome!! This is the first time I've been able to break 30 fps! (thanks to your app!)
I'm on Froyo and the v4 had never worked, but now v4 + high frequency with your app = 40 fps.
I love you.

this may a silly question... but would this fix camera when i have it disabled as to if i switch it on the camera is now broke? or just the kernel itself breaks the camera??

Great little app, I would recommend users experiment with the values just ever so slightly for optimum performance. Using the default value of 361 netted me about 50-51 fps, whereas using 365 nets me about 54-55. Not a huge bump, but even a little bit is nice

Great application. May I suggest adding maybe a quick cycle to move between frequencies so users can go through a number of settings at once? Kinda like the Scan feature in most radios to pick the best frequencies.

timgt said:
works great! Whats the number I set it at to equal the V2 setting of ffolkes kernel? I think its 400, is that correct?
Click to expand...
Click to collapse
Yes, I think V2 was 400.
madunix said:
this may a silly question... but would this fix camera when i have it disabled as to if i switch it on the camera is now broke? or just the kernel itself breaks the camera??
Click to expand...
Click to collapse
Every custom kernel does not have a working camera, because we do not have the source code for it. When HTC finally releases the source code, then we will be able to fix the camera.

antiphon said:
Great application. May I suggest adding maybe a quick cycle to move between frequencies so users can go through a number of settings at once? Kinda like the Scan feature in most radios to pick the best frequencies.
Click to expand...
Click to collapse
This sounds like something to think about. Only problem is, while scanning, no one will know what the fps is unless they have their favorite fps app running, but then we wouldn't know what the frequency setting is since the fps app is running in focus. Might be a bit difficult to pull off without building an fps test into the app.

Well done!! Thanks

AssassinsLament said:
This sounds like something to think about. Only problem is, while scanning, no one will know what the fps is unless they have their favorite fps app running, but then we wouldn't know what the frequency setting is since the fps app is running in focus. Might be a bit difficult to pull off without building an fps test into the app.
Click to expand...
Click to collapse
Yeah I agree it would be difficult to implement without a built in fps counter. I was thinking more along the lines of something that would flag or eliminate the frequencies that are really bad (ie the ones which make your screen go haywire). So maybe the user could, for example, pick frequencies 300-310 and then the app would cycle through them 1 second at a time. From there the user would be able to run FPS2D or whatever to test out those frequencies that didn't make their screen all blotchy.
Anyways, just something to think about. Great work nonetheless!

antiphon said:
Yeah I agree it would be difficult to implement without a built in fps counter. I was thinking more along the lines of something that would flag or eliminate the frequencies that are really bad (ie the ones which make your screen go haywire). So maybe the user could, for example, pick frequencies 300-310 and then the app would cycle through them 1 second at a time. From there the user would be able to run FPS2D or whatever to test out those frequencies that didn't make their screen all blotchy.
Anyways, just something to think about. Great work nonetheless!
Click to expand...
Click to collapse
This won't work, because the interface that is used to write these settings to the panel cannot handle both full-speed graphics, and setting panel registers. I tried this when I first created the sysfs attr file, and if fps2d is running, it seems impossible to set or query the current T2 value. the display pretty much has to be idle for this to work.
Using a mutex lock might help, but I didn't look into it any further.

maejrep said:
This won't work, because the interface that is used to write these settings to the panel cannot handle both full-speed graphics, and setting panel registers. I tried this when I first created the sysfs attr file, and if fps2d is running, it seems impossible to set or query the current T2 value. the display pretty much has to be idle for this to work.
Using a mutex lock might help, but I didn't look into it any further.
Click to expand...
Click to collapse
Yep, that's why I had to put in a "sleep" command in my app so that the system could process the change and update the app on if the register changed or not. Thanks for the interface maejrep!

Where is the link to the switch app?
Sent from my PC36100 using XDA App

Yeah? Where is version 1.1.1? 1.1.0 is the only available for download? Or am I a special needs kid?

Force close only.

apollooff320 said:
Where is the link to the switch app?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
VoXHTC said:
Yeah? Where is version 1.1.1? 1.1.0 is the only available for download? Or am I a special needs kid?
Click to expand...
Click to collapse
Sorry, maybe I forgot to change the version in the app, 1.1.1 should be the only one linked in the original post.
Sprockethead said:
Force close only.
Click to expand...
Click to collapse
Do you meet the minimal requirements on the original post? Because you have to be running a custom kernel with the T2 interface in it.

wont recognize
im not sure whats wrong, i downloaded this on my phone and it says it dosent recognize the file i downloaded

[Kernel]netarchy-toastmod, Stable: 4.3.1 Beta: 4.3.4 (17-Mar-2011) Now With HDMwIn

NOTICES: If you are noticing abnormally high battery drain and/or uptime, and you've updated to PRI 1.90, it has come to my attention
that this PRI has been problematic for a number of people, often resulting in large uptimes and/or poor battery life.
This issue affects people regardless of whether or not they are using a custom kernel
Downgrading your PRI and NV to 1.77 has been reported to resolve this issue.
You can find all PRI and NV versions by clicking here.
Due to troubling reports of battery issues possibly caused by the SBC battery charger modification, it is worth mentioning that by using any SBC build, you
fully assume any and all potential risks that the SBC modification may pose.
"netarchy-toastmod" is a kernel originally based on the GoDmOdE sources (Courtesy of Toast) integrating my work on fixing the fps for the Epson panels, and as of version 3.6.1, also integrating a fix for the Nova panels that does not require the use of Evo switch or manually setting any registers, etc, courtesy of work done by AssassinsLament (Well done on the nova fix). Special thanks needs to go out as well to Cyanogen and the cyanogen mod team, as a number of bugfixes and updates to the kernel in recent revisions have been ported over from cyanogen mod to enhance the overall netarchy-toastmod experience.
Click to expand...
Click to collapse
So what's in the kernel?
- Overclocking Support
- HDMwIn (As of 4.3.4)
- Audio gain tweaks (read: make it louder!)
- Fps Fixes
- tun.ko for openvpn users
- CIFS support (as of 4.2.2)
- BFS (in select builds)
- BFQ (in select builds)
- HAVS (as of 4.1.9)
- Assorted fixes/tweaks (that are sadly too numerous to list here)
- An army of rabid naked bunnies
Click to expand...
Click to collapse
The zipalign script in the kernel's modified inits is based on code in the Damage Control rom, and extended to check more places for apps.
The Dalvik code in the inits is courtesy of Ninpo/Hacre from the VillainRom team (over in the HTC Hero forums).
Click to expand...
Click to collapse
mroneeyedboh has written a handy little kernel starter guide with a lot of general information about custom kernels and various terms you might see flying around (such as cfs/bfs, havs/nohavs, etc).
You can view this guide Here
Click to expand...
Click to collapse
Current Revision: Stable: 4.3.1 - For Froyo Sense roms | Beta: 4.3.4
Click to expand...
Click to collapse
A note on multitouch:
Some of you may have used my 5point multitouch test builds with success, others with failure. Research has shown that the Evo's contain at least 2 different versions of the touch sensor, one of which does not support 5point multitouch (but it DOES support 3point). You can check which sensor you have using adb by issuing the following command: "adb shell cat /sys/android_touch/vendor" and examining the result. If your result is ATMEL_x0080_x0016, your phone can support 5point. If your result is ATMEL_x004F_x0016, your phone will only support up to 3point.
Click to expand...
Click to collapse
Disclaimer:
While these builds have been deemed generally safe, it is not feasible to account for all possible combinations of custom roms and uses,
custom roms may experience some breakage depending on how some features are set up, as these builds are not aimed at any one particular rom.
As such your mileage may vary, use these at your own risk.
Click to expand...
Click to collapse
2.2 Kernels (THESE WILL NOT WORK ON 2.1 ROMS):
These have only been tested against the rooted HTC 2.2 stock rom, they *may* work on the various custom 2.2 roms,
but this is NOT guaranteed. MAKE A NANDROID BACKUP JUST IN CASE!
Click to expand...
Click to collapse
If you get force closes on the camera, go to Menu -> Settings -> Applications -> Manage Applications -> All -> Camera -> clear data.
Click to expand...
Click to collapse
-----------------------------
2.6.32-based Kernels:
Click to expand...
Click to collapse
Beta Testing Builds
When making a post about any issues concerning beta builds, please include ALL of the
following information if possible:
1. Which kernel build(s) (ie; bfs/cfs havs/nohavs etc) are you using with the issue?
2. What Rom are you using?
3. If known, what OTA base is your rom using (ie; is it based on 3.29, 3.30, 3.70, etc)?
4. Does the issue persist if you go back to a stable kernel build?
5. The issue being experienced (obviously ;D)
4.3x:
To clear up some confusion that is apparently being spread around,
4.3x builds do in fact work on all current evo models, not just the newest model.
4.3.4:
--CFS builds--
No SBC:
4.3.4-cfs-nohavs-noUV-nosbc (No Undervolting)
4.3.4-cfs-nohavs-suv-nosbc (Static Undervolting)
4.3.4-cfs-havs-less-nosbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-nosbc (More Aggressive HAVS)
SBC: Use sbc builds at your own risk.
4.3.4-cfs-nohavs-noUV-sbc (No Undervolting)
4.3.4-cfs-nohavs-suv-sbc (Static Undervolting)
4.3.4-cfs-havs-less-sbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-sbc (More Aggressive HAVS)
For older beta builds click here.
---------------------------------------
Stable Kernels:
Universal Builds:
4.3.1:
--CFS builds--
No SBC:
netarchy-toastmod-cfs-havs-nosbc-universal
netarchy-toastmod-cfs-nohavs-nosbc-universal
--BFS builds--
No SBC:
netarchy-toastmod-bfs-havs-nosbc-universal
netarchy-toastmod-bfs-nohavs-nosbc-universal
These use Koush's anykernel for installation and should theoretically work on -any- rom.
*note* This is designed to be flashed over a phone that already has a working kernel of some kind flashed,
whether it's a stock kernel, or another custom kernel. In other words, if you can currently boot up your phone into whatever rom you have, this should work. ;D
The universal kernel also does not contain the tweak scripts of the normal build (ie; zipalign on boot and the dalvik tweak), it's intended to be a universally compatible kernel.
This also happens to mean the universal builds will probably work on CM
For older builds click here.
-------------

FAQ:
Code:
Havs: Hybrid Adaptive Voltage Scaling, basically tries to undervolt as much as possible to conserve power, but adapts to things like cpu load and temperature.
No Havs: Static voltage scaling, every cpu speed pulls a specific amount of power from the battery, no variation
CFS: http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Q: Do I need to be rooted to use this kernel?
A: Yes, you need to be rooted, preferably a full root with nand unlock,
Q: How do I flash this kernel?
A: Copy the zip to your sdcard, and flash it from recovery mode
Q: My phone is suddenly unstable after using this kernel and I experience
weird things like reboots or other bugs
A: Are you overclocking? Try lowering the max speed of your overclock.
If the problems stop, you were overclocking too hard. If not,
please include the following information when reporting issues:
1. Your Baseband
2. What rom you're using
3. Your software number
4. Your panel type (Nova or Epson)
5. A Description of what's happening
Q: Why can I only overclock to 1152mhz? (In builds prior to 4.1.x)
A: Frequencies above 1152 have repeatedly turned out to be unstable for
a large percentage of users, so they have been removed to
eliminate the temptation to use them (and then complain because
they are unstable ;D).
Q: Does this kernel work with 2.2 (Froyo) roms?
A: The "Froyoized" kernels do
Q: Will this kernel work with my custom rom?
A: Maybe. The general population build of the kernel should work with
*most* custom roms, but as each custom rom can have it's own
customizations, your mileage may vary. In some cases, particularly
when a lot of customizations are in the rom's ramdisk, the kernel
must be repackaged with the ramdisk from the custom rom to be compatible.
Release notes:
Code:
Notes for Revision 4.3.4
- HDMwIn support added, you still need to download the free HDMwIn app
from the android market to use HDMI mirroring
- Timer tick set to 1000hz
- Unnecessary extra debugging turned off for public builds, should result in a small speed boost
Notes for Revision 4.3.2
- Wimax code updated, 4g should behave a bit better
- SD card read ahead fixed, higher class SD cards should
have an easier time reaching their potential speeds
Notes for Revision 4.3.1
- Screen tearing issues on sense roms should be fixed
Notes for Revision 4.3
- Camera drivers updated to support phones with the newer camera sensors
- ms79723's SBC v7 mod integrated for enhanced battery charging
- Misc speed tweaks/optimizations
Notes for Revision 4.2.2
- Kernel updated to 2.6.32.27
- Conservative set as default governor again
- Conservative governor defaults tweaked
- Less aggressive build has even more relaxed undervolting to aid those with REALLY picky phones
Notes for Revision 4.2.1
- Kernel updated from a 2.6.32.15 to 2.6.32.25
- Interactive governor added and tentatively set as default in some test builds
- Smartass governor added and tentatively set as default in some test builds
- Added BFS 357 smartass builds
Notes for Revision 4.1.9.1
- HAVS has made a return, this should help improve battery life by automatically dynamically undervolting the cpu when possible
Notes for Revision 4.1.8
- Added the BFQ I/O scheduler
- Split out kernel editions, now users have a choice between a CFS or a BFS kernel, if you don't like one, try the other ;D
- Enabled shadow writes on the gpu, which may result in better performance in opengl applications
Notes for Revision 4.1.7
- Add BFS to the kernel
- Allocate more memory to the gpu, this may result in better performance in opengl applications
- A rabid naked bunny vampire has materialized under your bed. Be afraid.
Notes for Revision 4.1.6
- Users with touchscreen issues should find their touchscreen is no longer as responsive as a stereotypical wife on her 10th anniversary
Notes for Revision 4.1.5
- Banished HAVS into the fiery pits of hell for now due to its inability to remain stable with any attempts to overclock. I'll be working on this on the side for possible future re-inclusion
- Clock frequency table remains opened up, with static undervolting in place
- Thanks to l33tlinuxh4x0r for being a guinea pig and helping test this build
Notes for Revision 4.1.4
- The beast responsible for the ridiculous overclocking instability at *any* speed beyond stock has been severely beaten and castrated by rabid naked bunnies (without anesthetic)
- Update scripts redone in the interests of making sure people who have had issues flashing the kernel in the past can do so
- The conservative governor has had some more tweaks to give it better out of the box performance, but you are free to set ondemand as your governor in setcpu if you wish. (If you want to migrate to ondemand you'll also need to set it as the governor in your setcpu profiles)
- The clock frequency table is fully opened up (re-detect frequencies in setcpu to see them) As always your mileage in overclocking may vary, but for some perspective, I ran 1152 through many loops of neocore and quadrant just fine.
Notes for Revision 4.1.3
- The ondemand governor is enabled as an option (switch to it in setcpu if you want to use it, remember you'll have to update your profiles to use it as well).
The default currently remains conservative to have a balance between performance and battery.
- The small segment of users getting bootloops due to the undervolting being too aggressive should be able to boot the kernel now (though if it persists the undervolting can still be adjusted)
Notes for Revision 4.1.2
- All frequencies above 1152 should now be properly visible/usable in setcpu (You may need to re-detect speeds in setcpu first)
Notes for Revision 4.1.1
- Hot on the heels of 4.1.0, a minor versioning fix ;D (4.1.0 reports itself as 4.0.3)
Notes for Revision 4.1.0
- Adapted HAVS for the evo, this may improve battery life by allowing the cpu to run at lower voltages when possible
- The overclocking range has expanded to allow attempting to clock above 1152, Remember that overclocking is unpredictable and potentially unstable by nature, if you encounter problems overclocking, lower the speed.
- Some threshold adjustments to the conservative governor in the interest of improving performance without obliterating battery
- Wired tethering should theoretically work, however if there are problems with the app, an alternative is azilink for wired tethering
Notes for Revision 4.0.3a
- An experiment of sorts, changing from the ondemand speed governor to the conservative governor (with some tweaks), in the interests of keeping good performance with less impact to battery life.
- Rewritten update scripts to hopefully alleviate the small number of people who seem to be having a problem flashing the kernel
Notes for Revision 4.0.2:
- People having stability issues with overclocking to 1152 *may* find it is a bit more stable (your mileage may vary)
Notes for Revision 4.0.1:
- Speed range should now allow underclocking to 128mhz (You may need to re-detect frequencies in setcpu)
- The Nova panel T2 register should be changeable again (for you Evo Switch/Novareq users)
Notes for Revision 4.0:
- Updated to the latest HTC released kernel sources (2.6.32)
- Camera should now be working properly
- HDMI output should be working in Froyo again
Notes for 3.7.8b-Froyoized
- Camera should no longer take dark snapshots when using the flash, the monster responsible has been severely beaten with a twig.
Notes for 3.7.8-Froyoized
- Camera app should no longer crash when changing from 5:3 widescreen to 4:3 standard ratio
- Camera app should properly allow 720p video recording and playback
- Japanese researchers have begun construction on a mecha-rabid naked bunny, codenamed: Bunnytron.
Notes for 3.7.7-Froyoized
- Re-integrate zipalign check and Dalvik cache tweak from the 2.1 line
- Some adjustments made to bluetooth-specific audio tweaks to combat distortion
- Audio adjustments to combat background noise overpowering the voice on the other end of a call
- Set version tag correctly (har har!)
- Super-mutant rabid naked bunny successfully created in lab conditions, however it disintegrates upon exposure to reality.
Notes for 3.7.6c-Froyoized
- SDcards with ext partitions added on should now cease confusing Froyo and allow the card to be mounted properly (Special thanks to Ninpo for directing me to the fix)
Notes for 3.7.6b-Froyoized
- Touchscreen adjustments, this may fix those who had touchscreen issues with 3.7.6
Notes for 3.7.6-Froyoized:
- Compatibility with the leaked 2.2 ota (and probably other 2.2-based roms)
- Working Camera (Limited to 3megapixels) EDIT: Reports indicate it claims 3mp but actually functions at 8mp
- Fps fix (of course ;D)
- Wireless Tether is reported as working with this as well
- 4g is confirmed as working
Notes for 3.7.5:
- Toned back audio boost tweaks a little to address distortion issues
- Updated gpu code for some 3d speed improvements
- Prevented the horde of mutant hairy toe-monsters from spreading toejam
all over the thread.
Notes for 3.7.4:
- Updated bluetooth code, courtesy of cyanogenmod
(You may have to re-pair your bluetooth devices)
- A new audio boost tweak has been applied
(This should not have the issues of the previous audio boost)
- Fixed an issue that would cause some Nova users to mysteriously
revert to 30fps. (Bad nova! no cookie!)
- Successfully avoided maiming any sabretooth'd tiger-striped cows
during the production of this update.
Notes for 3.7.3c:
- Some more tweaks to default performance (when not using setcpu/overclock widget)
Notes for 3.7.3b
- Killed that damn bug monster that decided yet again to sneak into one of my builds. Bad monster! No cookie.
Notes for 3.7.3:
- Adjusted the behavior of the speed scaling governor to give better performance out of the box for people that don't use setcpu or overclock widget
- Made adjustments to the general population build in the interests of making it compatible with Apps2SD by request.(Damage control users should have already been unaffected)
Notes for 3.7.2a
- Gave the monster holding wifi and 4g hostage a spanking (read: wifi/4g should be fixed)
Notes for 3.7.2
- Tweaked Nova settings in the interests of making sure everyone with a nova panel benefits from the fps fix
Notes for 3.7.1:
- Kernel should now have 100% more working HDMI output, no really, we mean it this time!
Notes for 3.7:
- HDMI output should now work in conjunction with boosted Nova/Epson fps
- tun.ko is now included by default for VPN users
Notes for 3.6.4:
- Behold, the return of 5point multitouch! This build should now automatically enable 5point multitouch for all phones that can support it. If the phone does not support 5point, it will default to 3point.
Notes for 3.6.3:
-Removed problematic audio boost patch that was giving issues with bluetooth
-Adjusted overclocking frequency tables to remove some problematic frequencies (Yes I know a small selection of you are going to be disappointed with the lowered cap, but I felt that the problems were more important at this time.)
-Evo switch ideally should not be required for decent framerates on Nova panels, but if users desire, by popular request, they can now use Evo Switch to tweak their T2 register [U]without[/U] it resetting after a screen cycle
-Default T2 value adjusted to 370, AssassinsLament believes this to present a good balance between out of the box performance and compatibility
-No fluffy pink bunnies were harmed in the making of this build

Can this be flashed with clockwork? Or just amon ra?
Is this a Froyo or Eclaire kernel? Any radio requirements?

Awesome, I have a Novatek. /facedesk.

jerryparid said:
Can this be flashed with clockwork? Or just amon ra?
Is this a Froyo or Eclaire kernel? Any radio requirements?
Click to expand...
Click to collapse
Should be flashable with either Clockwork or Amon Ra. Theoretically it might work on Froyo, but I've only tested it on Eclair.

This was not answered in the Godmode kernel thread. Does Camera work on this for 2.1.

mattrb said:
This was not answered in the Godmode kernel thread. Does Camera work on this for 2.1.
Click to expand...
Click to collapse
Yes the camera works on this in 2.1

Just flashed on Snacks v0.8 w/ Clockwork.
fps2d, avg 53-55, ~12 std
fixes touchscreen delay
can observe tearing
camera works
screen seems to be less responsive?

VoXHTC said:
Awesome, I have a Novatek. /facedesk.
Click to expand...
Click to collapse
me too. I am going to wait till things cool down a bit and bother HTC for another phone.

jerryparid said:
Just flashed on Snacks v0.8 w/ Clockwork.
fps2d, avg 53-55, ~12 std
fixes touchscreen delay
can observe tearing
camera works
screen seems to be less responsive?
Click to expand...
Click to collapse
I haven't noticed any loss of responsiveness on my end, if anything I'd swear it feels more responsive. Touch lag seems fairly significantly lessened.
I wonder if it could be related to the fact that I'm using a 1.47.651.1 based rom plus the latest radio/etc, curious.
Makes one wonder what all HTC changed in the update...

imaxreed said:
me too. I am going to wait till things cool down a bit and bother HTC for another phone.
Click to expand...
Click to collapse
umm? http://forum.xda-developers.com/showthread.php?t=711964

Best kernel on my epson screen. I like how i can overclock as well

jerryparid said:
umm? http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
Thanks. I have seen that thread a hundred times but never entered it. The FPS doesn't bother me too much I am going to mess with this tomorrow i have the day off thank you.

jerryparid said:
umm? http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
Yeah i'd love to see this fix for nova

netarchy said:
I haven't noticed any loss of responsiveness on my end, if anything I'd swear it feels more responsive. Touch lag seems fairly significantly lessened.
I wonder if it could be related to the fact that I'm using a 1.47.651.1 based rom plus the latest radio/etc, curious.
Makes one wonder what all HTC changed in the update...
Click to expand...
Click to collapse
I just flashed back to the Snacks kernel (v0.8 is 1.47 based); there is a substantial difference in sensitivity (not delay) between the two kernels.

jerryparid said:
I just flashed back to the Snacks kernel (v0.8 is 1.47 based); there is a substantial difference in sensitivity (not delay) between the two kernels.
Click to expand...
Click to collapse
Hrmm, is it glaringly obvious in any particular app? I'd like to see if I can reproduce the experience myself.

My phone keeps locking up when trying to watch youtube videos. Sorry if this is already a known issue.

krazyflipj said:
My phone keeps locking up when trying to watch youtube videos. Sorry if this is already a known issue.
Click to expand...
Click to collapse
Trying it out now, no problems with youtube for me.
Tearing doesn't seem as bad as I remember, but still bothersome.

when i seen this, i jumped into the air with my fist up like a touchdown at the superbowl.
flashing in juuusssst a second..

VoXHTC said:
Awesome, I have a Novatek. /facedesk.
Click to expand...
Click to collapse
same !!!!

[KERNEL] [BETA] [2.6.34.5] [4Sense] [Oc] [Uv] #1 "Sorry For the Wait"

I DO NOT have an HTC Evo, but would LOVE to have one for development, and am saving for one. Bear with me until then I just wanted to say thank you to the few who have donated. I am almost there, any help is appreciated!!! I plan to have my HTC Evo fairly soon
DO NOT FORGET TO READ THE ENTIRE POST ON MY SITE, THERE IS IMPORTANT INFO
THIS KERNEL IS BUILT FOR SENSE ROMS 2.2+
So, it's finally here. It is nowhere near its finished state, or perfect, but I want to get all the bugs reported and taken care of. A BIG shoutout to @toastcfh and @cyanogen for all their work on the .34 kernel for the Evo, without them, this would have been impossible. The .34 branch introduces some nice speed increases along with a few other things. As of now, it does not have HAVS or BFS, but these will soon be implemented. IT IS CURRENTLY BETA. I know this will change however.
Bugs:
* There are some graphical glitches, these will get worked out
* As a result of these glitches, the touchscreen can be wonky
Code:
Also, a little info on HAVS and AVS:
The purpose of HAVS is to minimize the power used by the CPU by determining
and setting the optimal voltage. At the same time, the maximum voltage by
which HAVS can scale to is fixed to a specified voltage depending on the
CPU frequency in order to prevent scaling to a higher voltage than what is
normally used at a specified voltage. The optimal voltage is actively determined
for each frequency and temperature. HAVS actively adjusts the CPU voltage as the
CPU frequency and temperature changes.
ENJOY!
Credits: Cyanogen, ToastCFH for ALL his work on the .34 branch, Netarchy (epson fps panel fix), ffolkes - all for bits of their code (see changelog), Koush for his any kernel .zip, AssasinsLaminent (nova fix), and most importantly, HTC for their kernel source
Download:
As you would expect, I am not responsible for anything that happens to your device
If you like my work follow me on Twitter:

CFS Changelog
Kernel #1
- First kernel release
- Built for sense ROMs
- All things backported you would need:
* WiFi
* Bluetooth
* Wimax (4G)
* Touchscreen
- Noticeable speed increase from .32
- Overclock capable up to 1.113Ghz
- Undervolted for LONGER BATTERY LIFE
- FPS unlocked
- Touchpanel fixes
- All cpu governors included
- OpenVPN support built into the kernel
- All modules compiled that I always include
- New BCM wireless module with combo scan
- Much much more I need to add, it's a first kernel release!

downloading

Thank king
Sent from my PC36100

DL and installing on VirusROM Sense 1.0..

flashing now, thanks King!

THunDA said:
flashing now, thanks King!
Click to expand...
Click to collapse
no problem
All bugs will be worked out over time

Just flashed, and its doin' great! Thanks

this is a kernel based on the new release??? sorry for the question

alcangel64 said:
this is a kernel based on the new release??? sorry for the question
Click to expand...
Click to collapse
kingklick said:
The .34 branch introduces some nice speed increases along with a few other things.
Click to expand...
Click to collapse
unless .34 =/= .34, then yes

Severe over sensitivity in screen touch for me. Just scrolling down app list launched 4 apps in one swipe. impossible to type or even swipe between homescreens. Hw rev 2 novatec panel here. Also some minor screen issues where lines of black would appear. Can't wait for next kernel to try again....
Sent from my PC36100 using XDA App

gtkansan said:
Severe over sensitivity in screen touch for me. Just scrolling down app list launched 4 apps in one swipe. impossible to type or even swipe between homescreens. Hw rev 2 novatec panel here. Also some minor screen issues where lines of black would appear. Can't wait for next kernel to try again....
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
same issue, scrolling acting weird and launches apps when i scroll ;(

Joker022 said:
Just flashed, and its doin' great! Thanks
Click to expand...
Click to collapse
Good. I'm guessing u have an epson screen?
Sent from my HTC Desire using XDA App

Same issues... nova screen hw rev 2... oversensative.. can't type or do normal functions. You can tell its a lot faster than .32 versions...

Yep...severe issues on nova screens. Sounds promising but if you have a nova screen hold off for the next revision unless you would like to help log the bugs for him
Sent from my EVO, the true iPhone killer!

zergburger said:
unless .34 =/= .34, then yes
Click to expand...
Click to collapse
I think he was talking about the new release as in the kernel in 3.28 OTA update which is still a .32 kernel.

I'm having the same screen issues as the above posters with an Epson screen...

I have a Epson Screen. I run the Burn Droid rom.
Same as others reported, severe touch screen over sensitivity, was barely able to slide down to unlock. opened at least four differnent sections in settings and changed a few settings all while swiping downwards.
Quite a few graphical glitches.

been good last couple hours.. epson. nice work as always

downloading... will report back!

[DEV][KERNEL][Overclock] CM10.1 (4.2.2) - 3.1 kernel

To All,
I have Compiled a kernel, compatible with Derartem's CM10.1 (4.2.2). It is actually a clone of DerArtems kernel tree, with overclock additions (some borrowed from Xoom and AC100).
Overclock up to 1400Mhz (1600Mhz is also available in the overclocking list, but crashes hard on my Folio, altough it uses similar speed&voltages as the Xoom) -> Update: works at 1.6Ghz (Folio can't handle the overvolting of the Xoom, but is stable at lower voltage). However.. It does not really benefit from 1.6Ghz in benchmarks (probably due to worse multipliers)
I have also changed parameters of the 3D clocks to become similar to the Xoom overclock, so it might also have overclocked the GPU (but I'm not able to test this)
In V2 I have tried to reclaim some memory. GPU uses 128Mb, but 64Mb won't work in Jelly Bean. The HDMI Framebuffer uses 16Mb, so I have reclaimed this space (result: probably broken HDMI)
->361Mb usable
In V3: LP1 state
In V4: LP2 state seems to work better than LP1 (immediate wake-up, no double click of power button). No SOD on my unit up to 1.4Ghz. Not sure what it will do for battery life in sleep (processor still goes to deep sleep state, so impact might be limited). Also first step made to disable battery alarm.
V1: only OC (1.4Ghz works)
V1 OC boot image
V2: OC up to 1.6Ghz, + some memory remapped
V2 OC+mempatch boot image
V3: OC up to 1.6Ghz, + LP1 sleep
V3 OC+mempatch+LP1 boot image
V4: OC up to 1.6Ghz + LP2 sleep
V4 V4 second download source
V4b: OC up to 1.6Ghz, buth with (standard) LP0 sleep
V4b
V5: OC up to 1.6Ghz, LP0 sleep and some clock cleanups (e.g. removed 216Mhz)
V5
V6: V5 + Workaround for 1.6Ghz SOD
V6 link
V7: V6 + Deadline I/O scheduler (can be enabled in developer mode or your favourite overclock app). Default stays the NOOP scheduler
V7
V8: Try SOD workaround on the MMC
V8 link
Source:
Source
Be careful. I'm not responsible to damages to your Folio. Overclocking might destroy your tablet
(Tough, a burned Folio it is a perfect excuse to buy a new tablet... I can really recommend the Nexus 10 or the Galaxy Note 10.1 )
How to install:
Be sure to have DerArtem's CM10.1 release (only tested with alpha2)
run these commands with fastboot (check forum on how to install this on your PC. Enter fastboot mode on the folio by 3xpower+Volume Up):
Code:
fastboot erase linux
fastboot flash linux boot-ovc.img
Overclock can be enabled in "Instellingen -> Prestaties -> Processor -> Maximale kloksnelheid"
(translated to English this should be something like "Setup -> Performance -> Processor -> Maximum clockspeed")
Don't be too quick to set the overclocking speed at boot until you tested it well.
What to expect?
1000Mhz (no overclock)
Antutu: 8211
Linpack Multithread: 80
3DMark: 1461 (on Par with a stock Xoom)
1400Mhz (max overclock)
Antutu: 11654
Linpack Multithread: 121
3DMark: 1915
Credits:
DerArtem
Nopy
m32
guevor
The Cyanogenmod Team
The other Tegra Dev Teams where we have borrowed code (Adam, GTab, Vega, AC100, Xoom)
EDIT (known issue): Some more SOD issues come up when putting the Folio on standby at high clocks, but it is quite stable during use.
SOD's
Apparently not everyone has SOD's, but for some it is still a problem.
- Many use advanced wifi lock: this works, but keeps the tablet completely on (hight battery usage)
- At 1.6Ghz I also have an SOD (reproducable), but can be worked around with the app "Overclock Widget". Here you can set a max speed of 1600 in use, and 1000 when screen is off. Maybe this is also usable for the SOD at 1000Mhz (set e.g. to 600 when screen is off, overclock kernel is not necessary).

Nice job spicyalan.
Just one question, why OC instructions are in german ? Does this mean that the menu will switch to german or the ui will remain as it is now ?
Onother question, whay did you try to reclaim memory ?
Thanks

miazza said:
Nice job spicyalan.
Just one question, why OC instructions are in german ? Does this mean that the menu will switch to german or the ui will remain as it is now ?
Onother question, whay did you try to reclaim memory ?
Thanks
Click to expand...
Click to collapse
They are in dutch, but you will get them in the language your system is setup.
After compiling and installing the kernel several times, I was just too lazy to set the language of my folio to "english" for explaining
(You also need to set the setup app in developer mode (tapping on the build number numerous times)
One of the problems the folio is slow in 4.2, especially task switching, is the lack of memory (even zram does not solve this).
Out of 512mb:
- 128Mb is reserved for the GPU
- 8Mb for the framebuffer
- 16Mb for the hdmi framebuffer
Setting the gpu memory to 64 works, but fails to accellerate some 3d content (even outside games). This would have worked in gingerbread, but not jelly bean. I couldn't try 96Mb (crash at boot), so it needs to stay at 128. Framebuffer is also a nono, but the framebuffer ram of the hdmi can be reused (if you don't use the hdmi)
For the SOD, more investigation is needed.
No folio ROM was ever free of SODs (not even stock), but some roms have more problems with it than others. For me, gingerbread (7.2?) And the most recent derartem was the most stable in that regard. It is not easy to know where the SODs come from, but with the overclocking, I noticed it is worse at higher overclock. I'm starting to guess it has something to do with the processor going from total sleep to max speed too fast (if you prevent cpu sleep, it also helps the sod, but using a lot of battery during sleep. Some roms did this).
Same with wifi.
I'm going to test a new version of the rom soon (derartem's version, with cm10.1 upstream, and oc kernel), so stay tuned (but be patient...)

Very nice work! Finally an overclocked kernel that can increase a bit performances.
Thank you man
Inviato dal mio folio100 utilizzando Tapatalk

I have put an experiment online with the LP state
According to tegra documentation, there are 3 states:
-LP0: shut down everything, only a few interrups can wake the device
-LP1: shut down a lot, but more things can wakeup the device
-LP2: shut down less.
If I look in the the sources, there are only 2 devboards that use LP0, and the betelgeuse (folio) is one of them. But, as all other boards can only use LP1 (andseeing the exceptionally bad SOD track record of the folio), I would be surprised if the folio as actually able to to this.
I have places a version online that uses LP1 state, that I will test (but as I don't have the problem as often, it could be nice if others could also test to confirm if it is better or not). I was not able to have an SOD today on a clock lower than 1.2Ghz.
I did experience sometimes that I have to push twice on the power button to wake it up (reminds me of CM7.2)
next to that, I also suspect the wifi driver of some SOD'in (especially in higher overclock mode). It shouldn't actually shut down in sleep mode....

Hello,
I was on the way to try V3: OC up to 1.6Ghz, + LP1 sleep but the lik seems dead...
Can you check ?
Thanks
PS: V1 works great

miazza said:
Hello,
I was on the way to try V3: OC up to 1.6Ghz, + LP1 sleep but the lik seems dead...
Can you check ?
Thanks
PS: V1 works great
Click to expand...
Click to collapse
Sorry,
Typo in the filename.
I think the lp1 sleep might nog be the answer to the sod (which is worse on higher clocks). But worth a try.
Probably the wifi driver is te cause (wifi lock is the only thing that keeps sod away at high clocks). At 1000mhz, my folio has no sod.

spicyalan said:
At 1000mhz, my folio has no sod.
Click to expand...
Click to collapse
This is really something struggleing me. I have SOD:
- every boot is I do forget to unlock my profile before of sleep (I have two profiles)
- almost every time i put the tablet in std-by
what a strange behaviour and difference...

miazza said:
This is really something struggleing me. I have SOD:
- every boot is I do forget to unlock my profile before of sleep (I have two profiles)
- almost every time i put the tablet in std-by
what a strange behaviour and difference...
Click to expand...
Click to collapse
the same is here - any action with screensaver ends with reboot
branch android-tegra-nv-3.1 i my case is stabler - i'v no sods than rel-15r7

m32 said:
the same is here - any action with screensaver ends with reboot
branch android-tegra-nv-3.1 i my case is stabler - i'v no sods than rel-15r7
Click to expand...
Click to collapse
I have compared both tree's, and it seems rel-15r7 is +500 patches ahead, but also 136 behind. Most changes are now useless (e.g. many refer to the old partition system), but I have found a few wifi and SOD fixes in there not present in rel15r7. But they need to be hand-picked and checked.

For me this ROM update-cm-9.0.0-RC0-2012.03.04-betelgeuse-KANG-signed have NO SOD.
Sometimes have a problem with WiFi connection, but when you clear all saved and then connect again, then have no problem.

Cantdownload de kernels.. it shows only another page with te text.
Or may i have to copy the text?

spicyalan said:
I have compared both tree's, and it seems rel-15r7 is +500 patches ahead, but also 136 behind. Most changes are now useless (e.g. many refer to the old partition system), but I have found a few wifi and SOD fixes in there not present in rel15r7. But they need to be hand-picked and checked.
Click to expand...
Click to collapse
Waiting for you to make the miracle...

miazza said:
Waiting for you to make the miracle...
Click to expand...
Click to collapse
No luck yet...
Most of the patches conflict, and the few others result in an unbootable kernel...
I'm not an experienced kernel developer, so I'm kind of flying blind (and using the trial and error method)
My folio doesn't show sod's that often in cm 10.1 (maybe once every 2 weeks), but is do have them at 1400mhz and up. The only thing keeping them away at this speed is advanced wifi lock.
I'm going to move the file hosting to goo.im soon (the files seem to download fine in firefox on windows, but in the default android browser, I also get a .txt.... weird)

spicyalan said:
No luck yet...
Most of the patches conflict, and the few others result in an unbootable kernel...
I'm not an experienced kernel developer, so I'm kind of flying blind (and using the trial and error method)
My folio doesn't show sod's that often in cm 10.1 (maybe once every 2 weeks), but is do have them at 1400mhz and up. The only thing keeping them away at this speed is advanced wifi lock.
I'm going to move the file hosting to goo.im soon (the files seem to download fine in firefox on windows, but in the default android browser, I also get a .txt.... weird)
Click to expand...
Click to collapse
U have to much free time ?
Cant follow U I'm like U not so expirenced in linux kernel drivers building, perhaps we can share our/ouus findings with nopy and artem ?
My folio works few days without sod - but it weakups time to time when battery goes too low - as i'm in home, i can see it - screen blinks for few seconds, derartem has ported drivers from 2.6 to 3.1. In my opinion it's worth to wait for him.

m32 said:
U have to much free time ?
Cant follow U I'm like U not so expirenced in linux kernel drivers building, perhaps we can share our/ouus findings with nopy and artem ?
My folio works few days without sod - but it weakups time to time when battery goes too low - as i'm in home, i can see it - screen blinks for few seconds, derartem has ported drivers from 2.6 to 3.1. In my opinion it's worth to wait for him.
Click to expand...
Click to collapse
Not too much time... but sometimes I have
Waking up on low battery is still normal (many phones do it), but it shouldn't sod, nor should it wake up at random
Did anyone have contact with nopy or derartem these last months?

miazza said:
Waiting for you to make the miracle...
Click to expand...
Click to collapse
New tryout online
This time with LP2, and some clock fixes. no SOD on my unit up to 1400Mhz (still at 1600).
At 1600Mhz, I just benchmarked sunspiper in Chrome: 982ms. There is now 1 benchmark making this Folio faster than a stock Galaxy Note 10.1 (2012) -> Actually, just proves that javascript is quite single threaded

spicyalan said:
New tryout online
This time with LP2, and some clock fixes. no SOD on my unit up to 1400Mhz (still at 1600).
At 1600Mhz, I just benchmarked sunspiper in Chrome: 982ms. There is now 1 benchmark making this Folio faster than a stock Galaxy Note 10.1 (2012) -> Actually, just proves that javascript is quite single threaded
Click to expand...
Click to collapse
v4 just hangs on cm splash

m32 said:
v4 just hangs on cm splash
Click to expand...
Click to collapse
Weird... Is the size correct ? (maybe something happened in the download)
EDIT: I have added a new download source... Hosting at goo.im is stll not working
EDIT2: found a trick to work around the 1.6Ghz SOD (see 1st post), might give a clue for other SOD's?
According to kernel code, the CPU is set to max speed when resuming (max speed during board initialization might be a bad idea). I think this should be throttled (e.g. 600Mhz) until the screen is on. This can be simulated with overclock widget and its "screen off clockspeed profile".
Again something to test for someone with SOD's

I'm right now testing v4 at 1600. It looks stable. Nice job.
Edit: when the tablet goes to sleep with the blinking led I cannot wake it up. I need to maintain wakelock at 5.
Sent from Folio 100 using tapatalk

[Post your benchmark] Simple Antutu video (N7 2013 vs N5 vs Moto G vs Xperia S)

Hello guys,
Here is a simple video to show benchmark scores in Antutu between four devices:
- Nexus 7 2013: CleanROM 3.5 (Kitkat 4.4.4), ElementalX kernel
- Moto G Gpe: Stock rooted 4.4.2 Google play edition, stock kernel
- Xperia S: Stock 4.1.2, stock kernel
- Nexus 5: Stock 4.4.3, stock kernel
Link: http://www.youtube.com/watch?v=e8Q7PORuxi0
Thanks for watching !

Cool video, well made!!
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)

n01z said:
Cool video, well made!!
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)
Click to expand...
Click to collapse
Well thank you !
Nice score :good:

lulu14150 said:
Well thank you !
Nice score :good:
Click to expand...
Click to collapse
Thanks, right back atcha!! I think I'm the first S5 to break 42K, if I combined all of my best individual catagory scores, I would break 44K.. Got some work to do, got a bunch of tweaks lined up that I haven't tested yet, I think I'm gonna wait for some others to catch up.. or until I get bored again!!
---------- Post added at 07:11 PM ---------- Previous post was at 07:04 PM ----------
The settings that I use on my overclock (OC) are borderline stupid dangerous. And the settings I use to bench are straight up dangerous. For this reason, I will not be sharing them.
HOWEVER, You can find my non-overclocked faux settings here:
https://plus.google.com/app/basic/stream/z13tu3aq0krxchnnv234jdkbrnzrvlpcq
These settings scored 38256, no OC, AEL Kernel controlled by fauxclock.
Note: What we are doing here can result in you frying your snartphone- not worth it just to get a ranking.
For me, I just can't help but to experiment and push my device to it's limits. HOWEVER, my benchmark settings differ from my daily use settings, slightly (for stability) because I love my S5 and would possibly cry if we were to have to part!!
I'm going to share some of my best benching tips (no "tricks" just my observations)
1. Make sure that your Kernel control app has a boot delay of at least 20 seconds. (Mine is at 30 seconds, remember-patience is a vitrue!!)
2. Completely dim your screen, put your phone into airplane mode, disable any motion gestures.
3. Turn phone off for 5 min.
4. Boot your phone, but don't touch it, just let the lockscreen time out, wait 2 minutes, unlock the phone and let it sit for another minute.
5. Do not flip screens or pull the notification bar (we want to NOT trigger any background processes, so turn off any motion gestures- because they are using the CPU while monitoring your sensors and be sure to leave your default homescreen free of widgets).
6. Open Antutu, wait about 30 sec..
7. Click Test Again then uncheck Optimize Memory (your ROM should already have optimized memory and I assure you thay Antutu doesn't know your device better than the OEM or Custom ROM devs) Now, wait about a minute and a half..
8. Click TEST then don't touch/move your phone until it's done..
More Notes:
Make sure that you only ever change one parameter at a time and be sure to run a CPU Monitor when you do, to see the affects of each change..
Reboot inbetween every bench and turn your screen brightness to MIN before you reboot to bench..
Also, I recommend to try running a CPU Monitor once or twice while you run a bench in antutu so you can get an idea of how long it takes for antutu's CPU use to chill out, (same can be done after boot to find out what your device likes, since I've never had any samsung bloat- as I rooted and flashed custom ROMS and Kernels the first day I got my S5- I literally have no experience with Stock)..
Also, running a CPU Monitor when you are getting low benches will help you see if it's being thermal throttled during a bench (throttling has caused me to score as low as 32K) and it will give you the best idea of what may be going wrong and where.
I actually know very little about Kernels, I am just patient, never give up and trial and error sweetspots until I get what I want..
Extra Note: Sweetspots vary from each individual device, so ya just gotta keep at it!!
P.S. These tips should work/help with any benching app.
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)

n01z said:
Thanks, right back atcha!! I think I'm the first S5 to break 42K, if I combined all of my best individual catagory scores, I would break 44K.. Got some work to do, got a bunch of tweaks lined up that I haven't tested yet, I think I'm gonna wait for some others to catch up.. or until I get bored again!!
---------- Post added at 07:11 PM ---------- Previous post was at 07:04 PM ----------
The settings that I use on my overclock (OC) are borderline stupid dangerous. And the settings I use to bench are straight up dangerous. For this reason, I will not be sharing them.
HOWEVER, You can find my non-overclocked faux settings here:
https://plus.google.com/app/basic/stream/z13tu3aq0krxchnnv234jdkbrnzrvlpcq
These settings scored 38256, no OC, AEL Kernel controlled by fauxclock.
Note: What we are doing here can result in you frying your snartphone- not worth it just to get a ranking.
For me, I just can't help but to experiment and push my device to it's limits. HOWEVER, my benchmark settings differ from my daily use settings, slightly (for stability) because I love my S5 and would possibly cry if we were to have to part!!
I'm going to share some of my best benching tips (no "tricks" just my observations)
1. Make sure that your Kernel control app has a boot delay of at least 20 seconds. (Mine is at 30 seconds, remember-patience is a vitrue!!)
2. Completely dim your screen, put your phone into airplane mode, disable any motion gestures.
3. Turn phone off for 5 min.
4. Boot your phone, but don't touch it, just let the lockscreen time out, wait 2 minutes, unlock the phone and let it sit for another minute.
5. Do not flip screens or pull the notification bar (we want to NOT trigger any background processes, so turn off any motion gestures- because they are using the CPU while monitoring your sensors and be sure to leave your default homescreen free of widgets).
6. Open Antutu, wait about 30 sec..
7. Click Test Again then uncheck Optimize Memory (your ROM should already have optimized memory and I assure you thay Antutu doesn't know your device better than the OEM or Custom ROM devs) Now, wait about a minute and a half..
8. Click TEST then don't touch/move your phone until it's done..
More Notes:
Make sure that you only ever change one parameter at a time and be sure to run a CPU Monitor when you do, to see the affects of each change..
Reboot inbetween every bench and turn your screen brightness to MIN before you reboot to bench..
Also, I recommend to try running a CPU Monitor once or twice while you run a bench in antutu so you can get an idea of how long it takes for antutu's CPU use to chill out, (same can be done after boot to find out what your device likes, since I've never had any samsung bloat- as I rooted and flashed custom ROMS and Kernels the first day I got my S5- I literally have no experience with Stock)..
Also, running a CPU Monitor when you are getting low benches will help you see if it's being thermal throttled during a bench (throttling has caused me to score as low as 32K) and it will give you the best idea of what may be going wrong and where.
I actually know very little about Kernels, I am just patient, never give up and trial and error sweetspots until I get what I want..
Extra Note: Sweetspots vary from each individual device, so ya just gotta keep at it!!
P.S. These tips should work/help with any benching app.
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)
Click to expand...
Click to collapse
Thank you for sharing your configuration !
My Nexus 7 2013 configuration:
- ElementalX Kernel (1,7GHz CPU, 490MHz GPU and a small undervolt --> Perferct for daily use)
- Rom CleanROM (just with Forced GPU 2D rendering in Developer Options)
Score between 26k and 27k