Related
*** THIS IS EXPERIMENTAL ***
Thanks to toastcfh, maejrep, AssassinsLament, Estimated Prophet, Cicatrize, joeykrim, geyes30, kpkimmel and all the others from the kernel & display cap threads who have been working tirelessly, and continue to do so. This isn't over until we can find the real cap! But I think this avenue has progressed enough for it to have its own thread, if only to give hope, since we now know both Epson and Novatek panels physically can do it!
What Doesn't Work
Nothing. Now based on the official kernel with everything working.
About This Kernel
This is just a dirty hack. We haven't yet figured out where the real cap in framerate is coming from. But until we do, this is the best we have. At least it shows the display itself can handle a higher framerate and isn't physically incapable like HTC would have us believe.
Novatek panels can now get up to 46fps pretty reliably. Run fps2d a few times.
Stdev depends on system activity. If you're going to be judging stdev, DON'T measure it immediately after booting, set your CPU throttle mode to "performance", be sure to run fps2d several times, then average those stdev numbers in your head.
The changes are now immediately applied upon boot. There is no need to cycle your display anymore.
This kernel has support for overclocking/underclocking, up to 1.119 MHz. Also includes my own undervolting and overvolting for higher speeds to increase stability.
You can get dramatically tighter stdev numbers by setting your CPU governor to "performance" in SetCPU. It seems scaling really messes with the framerate. Obviously this will drain your battery faster, as your CPU will constantly be running at full speed. Set it back to "ondemand" if you don't need it.
Some people are reporting their touchscreen grounding issues have been cured.
Support to change the T2 value on the fly [thanks to maejrep]
Support for 5 simultaneous touch points! Use Dotty (in the Market) to see it in action. It'd be cool if someone would make a simple app to demonstrate what can be done with more than the mere 2 points we are used to. People have suggested new lock types, security locks, ways to rotate things, etc. [thanks to maejrep]
Some hardware fails to accept 5 points, so a fail-safe has been added to default back to 2 points for some EVOs
AssassinsLament has created an awesome app to provide an easy way for people to change their T2 timing. Check out his app here: http://forum.xda-developers.com/showthread.php?t=716659 [thanks to AssassinsLament]
Changes to display timings are now sticky until rebooted (w/ the above app, or set manually)
What's New
v5.1.1: Using the official kernel. We've lost some fps, but we've gained camera, video, 4G, etc. 46fps is now average.
v5.1.1: Expanded user-modifiable timing settings. Change at your own risk.
v5.1.1: Audio patched [thanks Geniusdog254 and KERKEDAGAIN]
Instructions
Do a nandroid backup, and flash this over pretty much any ROM. If you have problems, you can just flash a stock boot.img again. There should never be any need to wipe anything.
IMPORTANT: This will only work with the stock bcm4329.ko! Using the newer files and flashing this kernel will result in wifi being unable to start, and vice versa. To correct this, you'll need to flash over the correct wifi files.
Changing Timing Settings
You can use the following commands from adb shell to temporarily change timing on the fly. Do it while your screen is on.
Set: echo NUMBER > /sys/devices/platform/mddi_c_b9f6_5582.1/PARAMETER
Check: cat /sys/devices/platform/mddi_c_b9f6_5582.1/PARAMETER
Parameters:
t2 - 245 to 1023 [Default Eclair: 437, Froyo: 432]
t3 - 0 to 7 [Default Eclair: 1, Froyo: 0]
fte - 0 to 879 [Default Eclair: 35, Froyo: 60] (Frame Tearing Effect, change this if you have tearing problems)
Flashable ZIP - Undervolted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
Flashable ZIP - Undervolted kernel v5.1.1 for use with 2.2 (Froyo) ROMs
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.2 (Froyo) ROMs
Note: Certain things like the camera still don't work, since our Froyo ROMs aren't official.
Flashable ZIP - WiFi-N + 4G for all custom kernels based on toastcfh's GoDmOdE kernel (compatible with v5.2+)
Flashable ZIP - WiFi-N + 4G for stock/custom kernels (compatible with v5.1 and below)
Flashable ZIP - WiFi-N + 4G for the OTA kernel (NOT compatible with the kernel in this post)
*** REMEMBER! No one here is responsible if you damage your phone! ***
See the Evo, Droid X and Nexus One benchmarked together here: http://androidspin.com/2010/06/25/droid-x-vs-htc-evo-vs-google-nexus-one-in-benchmark-face-off
Want NenaMark1? It usually doesn't show in the Market, so get it here: http://nena.se/downloads.html
Awesome, just flashed and it is soo smooth, thank you devs.
This works great for me.
Not really related to this but my phone locks up when I change the cpu frequency with setcpu. EDIT: (How do I overvolt the phone?)
Oh and yes I do get 50hz.
Is there 2.2 support or no
ttieder said:
Is there 2.2 support or no
Click to expand...
Click to collapse
Nope I wish there was. Droid X skin + 50hz would be very cool.
ttieder said:
Is there 2.2 support or no
Click to expand...
Click to collapse
Second this question..I'm loving the EvolutionX froyo rom and would be sweet to get this baby on board with froyo.
Does this work for Epson panels too?
This works great. Touchscreen SEEMS a bit more responsive in in multitouch vis test. Grounding issue is nowhere near as bad, but still there. If you pull the same trick that everyone is doing to test grounding problem, you won't notice it at first, and very rarely will it stop sensing you finger all together, but it definitely does cut out for an instant every now and then, and I had it drop visibility where it normally does a few times for a split second.
Epic delete
As this is a development thread, please don't start posting your results like the Godmode thread. It will only clutter the thread.
Can you zip your modified files and post them too? Source would be nice
sweteg said:
As this is a development thread, please don't start posting your results like the Godmode thread. It will only clutter the thread.
Click to expand...
Click to collapse
This thread was made to avoid the clutter from the Godmode thread.
Thanks for the excellent dev work!
You might want to add to the first post that this kernel breaks 4G. it will turn on but not able to find any network.
Other than that, works as described
The device feels so much smoother!
Great work! I get 52 in fps2d, 680 in quadrant, and 51 in gears. I can't wait until this is completely fixed but I'm loving it and the undervolt and oc patches are awesome additions.
automatic brightness still does not work with this kernel though. At least not for me. Is it possible I have a different light sensor as no custom kernel has worked with auto brightness yet and other reports say it works just fine.
Also... fps2d spikes into 99 fps and at one point I watched it flash past 100
Definetly works
Installed the kernel and got over 50 fps on my nova panel i have hardware config 002 it runs much much smoother thanks devs for the hard work.
wow this kernel is insane, I mean FPS hack and overclock hack without force closes...wow is all I can say. Used the OC widget and it detects the oc clocks quickly.
Man if this kernel makes it to Froyo..Evo will be truly evil
2 vertical lines just showed up on the right side of the screen, haven't tried anything yet, let me restart and see if it goes back, then try to duplicate the issue.
Edit: It went away after I got a text, not sure if it was coincidence or not. I'm guessing this is the tearing issue that the FPS fix causes, but nothing about it was written in OP.
Mrtankjump said:
2 vertical lines just showed up on the right side of the screen, haven't tried anything yet, let me restart and see if it goes back, then try to duplicate the issue.
Edit: It went away after I got a text, not sure if it was coincidence or not. I'm guessing this is the tearing issue that the FPS fix causes, but nothing about it was written in OP.
Click to expand...
Click to collapse
My Evo has an Epson panel so I can't use this fix but, my understanding was that this method didn't cause the tearing like we saw from Toast's custom kernel on Epson displays, so your problem might be something else and not necessarily the fps cap being raised.
Thanks for the kernel, but I still have one big problem- my battery still will not charge with this kernel installed. It will only charge when I turn off the EVO and turn it back on. But as soon as I unplug and replug it in, it will look like it charges for 5 seconds, then the orange light shuts off and it stops charging. I've enclosed a dump of my dmesg. Can someone please take a look at this?
hey, just stumbled upon this:
Adrenaline™ Engine
http://forum.xda-developers.com/showthread.php?t=1604315
apparently it improves ram by using zipalign, improves sd card read/write and mounting, as well as network tweaks, and more!
I'm wondering if we could apply it to the ChaCha.
The tweaks seem pretty generic. I imagine only minor details would need to be tweaked to apply to other devices.
I've already seen parts of it applied to other devices.
If some dev wouldn't mind taking a look at it and giving an opinion, I'd appreciate it
kronflux, have u used it?
This is a tweak I came accross while browsing some threads on xda.What is does is it forces hardware rendering instead of forcing cpu to carry out all the renderings..This is all I know about it.
Tested this out and I noticed slight performance boosts.Games are a bit faster and all those frequent "hiccups" which we experience on tipo are reduced ,if not eliminated.
Works on phones with adreno200 gpus..
for more info and to download the tweak, please refer the original thread
http://forum.xda-developers.com/showthread.php?t=1877183
Sent from my ST21i using xda premium
Hi,
I can not make the CWM, gives error.
However I did the manual procedure:
Put a unzip file: http://forum.xda-developers.com/attachment.php?attachmentid=976632&d=1333283208 in the file folder system/lib/egl/ and deleted the libGLES_android.so from egl folder.
I changed the build.prop, as the line was not added at the end dalvik.vm.dexopt-flags=m=y,o=v,u=y and recorded.
I did restart the smartphone,'ve played but honestly I do not notice improvements.
I look forward to more opinions.
Regards,
Jorge Moreira
Won't forcing gpu rendering for all apps reduce battery life?
Sent from my ST21i
Jorge Moreira said:
Hi,
I can not make the CWM, gives error.
However I did the manual procedure:
Put a unzip file: http://forum.xda-developers.com/attachment.php?attachmentid=976632&d=1333283208 in the file folder system/lib/egl/ and deleted the libGLES_android.so from egl folder.
I changed the build.prop, as the line was not added at the end dalvik.vm.dexopt-flags=m=y,o=v,u=y and recorded.
I did restart the smartphone,'ve played but honestly I do not notice improvements.
I look forward to more opinions.
Regards,
Jorge Moreira
Click to expand...
Click to collapse
Well you are right in a way..there were no improvements in the general ui fluidity..but my claim is based on the fact that the games which I tested(dead trigger , bad piggies and offload legends) were definately smoother.Lesser stutterings
Others please try it out and post you opinions
Sent from my ST21i using xda premium
satan89 said:
Won't forcing gpu rendering for all apps reduce battery life?
Sent from my ST21i
Click to expand...
Click to collapse
I didnt notice any such thing
Sent from my ST21i using xda premium
Didn't notice any improvements.Manually unpacked and set perms, rebooted.
balboarocky said:
This is a tweak I came accross while browsing some threads on xda.What is does is it forces hardware rendering instead of forcing cpu to carry out all the renderings..This is all I know about it.
Tested this out and I noticed slight performance boosts.Games are a bit faster and all those frequent "hiccups" which we experience on tipo are reduced ,if not eliminated.
Works on phones with adreno200 gpus..
for more info and to download the tweak, please refer the original thread
http://forum.xda-developers.com/showthread.php?t=1877183
Sent from my ST21i using xda premium
Click to expand...
Click to collapse
I also have noticed slight performance boosts in my Xperia Tipo. But I'm not sure if this will have any negative effects in the smartphone, because I guess that Sony would have set down this option by default for a reason
P.D.: Yes, I'm not english and I probably I would have mistakes, but i hope for you can understand me!
edit: What i have done is enable the option in Settings -> Developer options -> Force GPU rendering
this script like supermacy?
ICS already using hardware rendering instead of software rendering for the default setting. you might feel drastic change if you're using GB based rom. however, if you're using ICS based rom you won't feel anything. anyway, if you want to do it in easier way, go to setting>developer option>force gpu for 2d rendering.
balboarocky said:
This is a tweak I came accross while browsing some threads on xda.What is does is it forces hardware rendering instead of forcing cpu to carry out all the renderings..This is all I know about it.
Tested this out and I noticed slight performance boosts.Games are a bit faster and all those frequent "hiccups" which we experience on tipo are reduced ,if not eliminated.
Works on phones with adreno200 gpus..
for more info and to download the tweak, please refer the original thread
http://forum.xda-developers.com/showthread.php?t=1877183
Sent from my ST21i using xda premium
Click to expand...
Click to collapse
Force rendering is essential only for Old apps which don't use GPU. Forcing that will be effective only for those apps.
This will cause GPU to be running all time. Basic graphic tasks are handled by CPU very well. If there are lags then System uses GPU.
There may be slight performance improvement on cost of decreased battery life. So its better to leave it unmarked.
:good:
adrenalin engine
If you really want to unlock the potential of tipo use THIS
✔ Increase touchscreen sensitivity
✔ Less RAM usage through zipalign. | World first smart zipaligning
✔ Reduced /dbdata, /data, /sdcard usage of *.db files and faster database access. | World first smart sqlite optimizing
✔ Faster disk access through remount script (noatime, disabled barrier etc) | World first smart remounting
✔ Better network throughput from TCP tweaks and 3G tweaks
✔ Tons of prop tweaks
✔ Overall Better Performance and Battery Life
✔ Less lags through LMK Tweak and Various VM Tweaks
✔ Faster SDCARD Read/Write Speed
✔ Bypass website like thepiratebay.se
NOTE: There are two different zips for stock and CM..
I have been using Stock+Adrenalin for quite sometime now. It is stable.
Hit "THANKS" if I helped you
Hey guys. First off, Apologies if this has been created or discussed before. I have searched before this posting; as I am not big on creating new threads, and the stigma related.
Anyway, On my HTC EVO 3D, I used Kernel Manager, as it had a great layout, allowed cpu/gpu adjustments, AMAZING widget, mpdecision support, ThermalD suppport (I do know the support comes from the kernel, Im saying the app allowed me to customize it), set vsync, color depth, whole nine yards. Im looking for something like it that would work well with the Infinity. Ive noticed kernel manager and ROM Toolbox are both finnicky with the tablet and it doesnt do as well. Kernel tuner works best, still it seems to not get along with the extra 2 CPUS. their governors always revert, it wont display CPU temp properly, no GPU settings, The battery drain is always +/-errmA (i guess error Milliamps) and the widget only displays two of the four CPUS. Anybody have any suggestions, or a solution to make kernel tuner work? Anything is welcomed and appreciated. Thanks in advance.
*FOR ANY DEVICE USING QUALCOMM CHIP***
Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0
Are power save settings included in your mod?
I made some test with Antutu on stock CPU speed..
1.) Stock kernel
- original file = > 43911
- your file "interactiveX" => 43545
- your file "interactive" => 41690
2.) Lean kernel
- original file = > 44047
- your file "interactiveX" => 42484
- your file "interactive" => 41804
tkari4 said:
Are power save settings included in your mod?
I made some test with Antutu on stock CPU speed..
1.) Stock kernel
- original file = > 43911
- your file "interactiveX" => 43545
- your file "interactive" => 41690
2.) Lean kernel
- original file = > 44047
- your file "interactiveX" => 42484
- your file "interactive" => 41804
Click to expand...
Click to collapse
I wouldn't be too concerned with benchmark scores.
Performance ≠ a higher score in antutu. But suit yourself.
Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.
Updated file and link is now available... I highly recommend anybody (devs included) use this in your current setup. Lot of fixes to the stock file that were critical to stability, power saving, and performance.
red_can_soda said:
Updated file and link is now available... I highly recommend anybody (devs included) use this in your current setup. Lot of fixes to the stock file that were critical to stability, power saving, and performance.
Click to expand...
Click to collapse
I wonder if this would work on lollipop leak. I'm running ayra mod v2 and could test this out.
fookea said:
I wonder if this would work on lollipop leak. I'm running ayra mod v2 and could test this out.
Click to expand...
Click to collapse
My guess is that it would work on 5.0... I would need to see a 5.0 post_boot file, though, to compare and look for any major changes.
red_can_soda said:
Updated file and link is now available... I highly recommend anybody (devs included) use this in your current setup. Lot of fixes to the stock file that were critical to stability, power saving, and performance.
Click to expand...
Click to collapse
I've installed your script (on stock 4.4.2 kernel) but didn't notice any performance, stabilty nor battery improvements.. It's more placebo effect than a real improvement.
ranwej said:
I've installed your script (on stock 4.4.2 kernel) but didn't notice any performance, stabilty nor battery improvements.. It's more placebo effect than a real improvement.
Click to expand...
Click to collapse
You are probably right, evidenced in the reports by everyone else that has used this saying the exact opposite. Lol
For me, it's noticeable. I have tested it pretty thoroughly and the script isn't just some cute ideas thrown together. From the lpm fixes (you can thank Qualcomm for that mistake), to some of the finer things like the deadline IO tuning (geared specifically for flash memory access), to some of the virtual machine parameters I've adjusted... There is logic and reasoning behind every single line of code I put together for this.
To be frank, I don't mind opinions. Hell I love them. But you need to know what you are talking about before you make a snide comment... Not for my sake, but for somebody who might not use it simply because they saw your remarks.
Many things appear to be placebo when it comes to this kind of stuff... But go start unzipping a large compressed file before and after using this script, or move a massive amount of data from your internal storage while playing music, browsing the web, and downloading an app at the same time.... I'd doubt you come in here talking about placebo.
You have yourself a wonderfully intelligent day.
Here you go, this is the post boot file. I'm running ayra mod v3 on noa5 leak with nl8 bootloader. The file appears to be modified on 11 Feb 2015