This is the restarted thread of my ICS Kernel
-
Codename Harmony
Current features are the following (more will follow) :
EVERY firmware avaiable is supported ! This means you can use my kernel on every ASUS-based roms like Revolver, Frozn or ARHD, but also on AOKP, CM9 Nightlies, Megatron, EOS, CNA, TEAMGUMMY, and all other AOSP-based roms out there.
Full 3G support on roms which support 3G
Stable Overclock up to 1.6 GHz
Stable GPU - Overclock ! -- Better 2D and 3D performance !
This is a HV (HighVoltage) Kernel. This means voltages are increased, but I use lower voltages than guevor does.
Extended File System support : Full CIFS, JFS, XFS, NTFS and REISERFS Support inbuilt in the kernel - no need for modules !
Added back missing powersave governor. This is nothing useful other than setting up profiles in setcpu, powersave governor for "screen off" profile does make much sense here.
Added Deadline I/O Scheduler for fancy testing.
Added Simple I/O Scheduler for ultimate I/O performance.
Readahead tweak for massive I/O performance boost.
Added minmax, wheatly, intellidemand, lagfree, smartassv2 governors.
That's it for now. You shall know I'm always open for user's request and will do my best to implement things from your wishlist if others and I do approve.
Changelog
Code:
[COLOR=Red][B]#FINAL[/B][/COLOR]
[LIST]
[*]Governor improvements - SmartAssv2 fully fixed !
[*]VooDoo sound added
[*]Countless overall improvements and code updates
[*][B]Remember : [/B]Downloads are now at my GITHUB !
[/LIST]
[COLOR=Red][B]UNIVERSE - Branch :[/B][/COLOR]
[LIST]
[*]Revision 1 (rev01) : Added support for all roms avaiable to our beloved transformers. WiFi should work on all versions now, including CM9 Nightlies, which was a huge hassle. 3G support is now added for use with roms, that support 3G ! Kernel Modules like NTFS, CIFS, File Systems, etc. are now all inbuilt, so you don't need to insmod anything. That's why my update.zps are so small - There are hardly any modules to copy over to system. Only NTFS automount is missing on CM9 for now, as it's a bit more complex, but it will be fixed in Revision 2; all other versions should work.
[/LIST]
[LIST]
[*]Revision 3 (rev03) : Improved overall stability, fixed misformed memory management, 3g enabled on all versions now, aosp kernel uses slightly lower voltage than asus one.
[/LIST]
[COLOR=Red][B]RELEASE - CANDIDATE Branch[/B][/COLOR]
[LIST]
[*]RC1 :
Completely recoded from scratch.
Based on 9.2.2.6 Asus Kernel Source.
Yet the biggest fixes to governors ever made by me.
Intellidemand governor fully fixed, smartassv2 is now somewhere near-stable.
Fixes to clocks and voltages, no more freeze at 1.2 GHZ.
FINALLY, GPU overclocking ! (--> stable !)
Tweaked SIO scheduler, now working perfectly on our device.
Readahead tweak for massive I/O performance boost.
Added in new CIFS and NTFS modules directly integrated into the kernel.
Revamped the updater script; more eye candy over here.
Other small changes and fixes to asus code.
[*]RC2 :
Recoded the voltage table, giving more juice to the gpu unit, raised read ahead value. Added CIFS and XFS modules kernel-builtin, will release the modules seperately for you to insmod once I rebuild with CIFS and etc. modular. IMPORTANT : IF THE KERNEL DOESN'T BOOT, HOLD DOWN POWER UNTIL IT REBOOTS. IF IT STILL DOESN'T BOOT, DO THE SAME AGAIN. IT WILL BOOT, TRUST ME.
[/LIST]
[COLOR=Red][B] BETA - Branch :[/B][/COLOR]
[LIST]
[*]BETA5 : initial public upload, after +- 20 hours of testing.
[*]BETA6 : added hotplug governor, added simple I/O scheduler,improved governors and cpu driver + deep sleep code.
[*]BETA7 : removed hotplug governor, caused me and the kernel headaches. Fully fixed the minmax governor, you should choose it as it delivers the best battery life at maximum performance. Lowered voltages, improved battery life and optimized sleep codes once again to get the maximun out of our battery life. Changed kernel versioning system, because of this build number has started at #0 again, is now #2 on BETA7. Also I added some suspending code, you should have no more deep sleep /RR with my kernel from BETA7 on.
[*]BETA8 : Using a new kernel config that fixes the random hangings. Excluded the 'smartassv2' governor for now, will include again in BETA 9, when it's fixed again. Improved SIO I/O scheduler, fixes to cpufreq and block.
[*]BETA-X : Massive fixes to governors, added some new (wheatly, lag free, intellidemand). Optimised voltages, increased frequency bus on overclock. Massive improvements on stability, more reliable in all situations. Improvements on battery life.
[/LIST]
CREDITS
I want to thank everyone who supported and helped me.
marcellusbe
dharam_maniar (formerly dharamG3)
guevor
hillbeast
All my testers, but especially scottyf79 (Gummy and AOKP Tester), cholywell (AOKP tester), ajohn117 (3G Tester) !
DOWNLOADS
NEWEST DOWNLOADS ALWAYS AT GITHUB
giving the kernel a run out now......smartassv2 with noop is blazing for web browsing! works pretty awesome with smartass and deadline aswell.
tried to change to interactive with noop and the tf locked up and i had to force a reboot......il see if i have logcat and post it up.
Will this work with AOKP? I think build 38 switched to the nl80211 wifi driver and the wifi won't work on custom kernels.
scottyf79 said:
giving the kernel a run out now......smartassv2 with noop is blazing for web browsing! works pretty awesome with smartass and deadline aswell.
tried to change to interactive with noop and the tf locked up and i had to force a reboot......il see if i have logcat and post it up.
Click to expand...
Click to collapse
Yeah, I encountered this as well, but I couldn't see any kernel panic in this, might be something else.
My next goal ist to port the linux 3.4 kernel, as they already included android source code in the mainline branch. Thsi would take the kernel to the next level.
But most of my worktime still goes into this kernel
cholywell said:
Will this work with AOKP? I think build 38 switched to the nl80211 wifi driver and the wifi won't work on custom kernels.
Click to expand...
Click to collapse
You're absolutely right. Everything will work fine except for wifi. If more users want this, I will make a aokp version with different wifi driver.
I think a CM9 AOKP version would be very popular. I don't think there any custom kernels for those roms and all the ones based off them.
+1.......the Cm9 builds like Skank etc could do with some loving
scottyf79 said:
+1.......the Cm9 builds like Skank etc could do with some loving
Click to expand...
Click to collapse
Did you try some cm9 rom with my kernel ?
I'm not aware of them having changed the wifi driver to something other than bcmhd...ko , in other wirds, asus stock.
Correct me if I'm wrong.
I'm on a trip the next days, so I will be able to continue work on this kernel let's say.. next tuesday if everything goes well. Just tell me which wifi driver to use and I will compile it
ok ive just tried Skang (cm9) and Gummy (aosp/cm9) with the kernel and neither connect to wifi. also when i tried to change the cpu speed with the baked in cpu controller i found they auto reverted back to 1000mhz with interactive and would not stick on 1200mhz or the selected guvenor.
I'll ask the respective devs what may be required to fix.
thanks for the work..i'm not going to test it due to stocked tf before assistance centre sending,but when i'll receive back my tablet,i'd love to be able to try this kernel...for my taste,i'd love to see wheatley governor inside..for me it's a very efficent governor.think about that mate.cheers and keep up the hard work!
A little update in the meantime : Beta6 is ready, added fully working sio-scheduler and hotplug governor. There is a bug because of which hotplug gov is rebooting instantly after being woken up from deep sleep.
More changes are :
Improved smartassv2 governor, working almost perfectly now !
Improved minmax governor. Ths does now work, but actually needs some further love from me, I think.
Will update the thread next week, along with Beta7.
Beta6 currently avaiable at : http://db.tt/XSK0na2Y
What about version for AOKP? All kernel brake wifi on b38
Seems like I miss my own deadline. Beta7 will be avaiable in a few minutes.
Random governor lockup while changing in setcpu or nofrills etc. should be fixed now.
I also improved all governors balancing and fully fixed the minmax governor.
Added sio scheduler to get the best I/O performance possible.
I will have a look on an AOKP and CM9 version with enhanced wifi drivers next week. Stay tuned !
Hi and thanks for your work.
Here's my experience with BETA7
TF101 b50, always docked with microsd always inserted
rom: revolver 4 rc2, kernel: harmony beta7
I tried your kernel after a long time using guevor's v20, because v20 gave me SOD after 3-4 days of normal operation.
I just wiped cache and dalvik, and then flashed beta7. It seemed to work smooth enough - had some stuttering in Modern Combat3, but that went away after a few minutes of playing.
The major problem was that it just RR while i was in a fring video call. Talking, as usual and then just bam! speakers started making this weird clicking noise for 1-2 seconds, video froze, and my tablet rebooted. This never happened before - i actually didn't have the RR problem even on stock rom+kernel.
I decided to test it overnight, only to wake up and see it rebooted again. It wasn't charging, it was only docked.
The good thing was that battery consumption was good ~1% per hour, with wi-fi on. It goes into deep-sleep, but also, before it does that, it does some random wake-ups.
So here's a summary of MY experience with BETA7 kernel
PRO's:
- no SOD
- good battery life (~1%/hour with wi-fi on, in deep sleep)
CON's:
- Random Reboots
- some random wake-ups
- some stuttering in 3d apps that seems to be loading-related
I'll be going back to guevor's, but i'll definitely keep an eye on this one.
Sorry, i didn't think of saving any kernel logs...
Keep up the good work!
Kernel based on Asus 9.2.2.4 ?
Hi,
is your kernel based on the Asus 9.2.2.4 stock kernel?
Because I've a TF101G 3G model and this the only kernel wich is stable (for about a week no RR or SOD's at all) on this tablet version while using Wifi and 3G functionalities.
BTW I'm using ARHD 3.3.1_3G rom.
I would like overclock it but this is not supported which the stock kernel.
Many thanks in advange.
zdalin2003 said:
Hi and thanks for your work.
Here's my experience with BETA7
TF101 b50, always docked with microsd always inserted
rom: revolver 4 rc2, kernel: harmony beta7
I tried your kernel after a long time using guevor's v20, because v20 gave me SOD after 3-4 days of normal operation.
I just wiped cache and dalvik, and then flashed beta7. It seemed to work smooth enough - had some stuttering in Modern Combat3, but that went away after a few minutes of playing.
The major problem was that it just RR while i was in a fring video call. Talking, as usual and then just bam! speakers started making this weird clicking noise for 1-2 seconds, video froze, and my tablet rebooted. This never happened before - i actually didn't have the RR problem even on stock rom+kernel.
I decided to test it overnight, only to wake up and see it rebooted again. It wasn't charging, it was only docked.
The good thing was that battery consumption was good ~1% per hour, with wi-fi on. It goes into deep-sleep, but also, before it does that, it does some random wake-ups.
So here's a summary of MY experience with BETA7 kernel
PRO's:
- no SOD
- good battery life (~1%/hour with wi-fi on, in deep sleep)
CON's:
- Random Reboots
- some random wake-ups
- some stuttering in 3d apps that seems to be loading-related
I'll be going back to guevor's, but i'll definitely keep an eye on this one.
Sorry, i didn't think of saving any kernel logs...
Keep up the good work!
Click to expand...
Click to collapse
Random reboots are definately rom - related, try ARHD rom, has been the bost rom ever for our transformer, I always put my trust in it. Revolver is halfway abandoned, outdated and not frequently updated.
Random wake-ups are rom related, too. I do not encounter any of your errors, sorry.
Maybe if you could get me a kernel message (kmsg, google it) , I could help you.
antond57 said:
Hi,
is your kernel based on the Asus 9.2.2.4 stock kernel?
Because I've a TF101G 3G model and this the only kernel wich is stable (for about a week no RR or SOD's at all) on this tablet version while using Wifi and 3G functionalities.
BTW I'm using ARHD 3.3.1_3G rom.
I would like overclock it but this is not supported which the stock kernel.
Many thanks in advange.
Click to expand...
Click to collapse
Kernel is based on 9.2.1.24 . I haven't found any newer source on the asus site, but you may redirect me to it, then I will use it.
Related
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 !!!!
This is my personal kernel, that I decided to release now. It is extremely lean to minimize memory footprint and optimize perfomance. It is built from HTC official GB sources, with some of bananacakes, siberes, snq-s and my own patches. I intend to keep it at 2.6.35.10, as I see more problems than advantages in upstreaming to newer revisions.
Features:
-Hybrid adaptive voltage scaling (HAVS)
-V(R) i/o scheduler
-TinyRCU
-Overclock up to 1190
-Undervolt
-Ondemand, Virtuous and SmartassV2 governors (I use Virtuous for wake and Ondemand for sleep)
-AXI
-Lowered WiFi voltage
-EXT4 support
-snq-'s Autobrightnessmod (Enable all 10 levels)
-sibere's Battfix
-USB fast charge
-Optional 2 way call recording
-Hardcoded SD Speed Patch to 2048. No need for init script anymore
-Hardcoded highly tweaked Lowmemkiller (3584,4096,8192,20992,23040,25088). Throw away Autokiller and/or init scripts.
To make it more lean, I have disabled EXT2 support. SWAP isn't supported either, as I find it completely useless.
I have added CIFS and TUN as modules. To install, download and extract the file and push it to /system/lib/modules like so:
Code:
adb remount
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
And add the following line to your modules init script:
Code:
insmod /system/lib/modules/cifs.ko
insmod /system/lib/modules/tun.ko
The kernel comes in 2 flavors. BFS and CFS. Differences between them are here:
BFS - Brain F**k Scheduler
The scheduler essentially handles CPU resource allocation. It controls how the CPU ramps up in frequency and down again when not needed. The BFS version is generally very snappy (possibly more so than CFS) but is an older scheduler. It is designed to minimise latency on low spec'd machines (desktops generally)
Further details here:
http://en.wikipedia.org/wiki/Brain_****_Scheduler
CFS - Completely Fair Scheduler
This particular scheduler is newer than BFS. It is designed to make the best of High end machines (desktops again). In the early days, CFS seemed much laggier than BFS but now there is not too much in it. I am quite happily running a modern CFS kernel and I don't experience any lag issues.
Further details here:
http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
I am aware that the BFS version throws some errors about 'bad cgroup data' in logcat, I haven't been able to get rid of them. I have disabled everything cgroup related in the kernel, but vm still throws the errors. Don't know why. Doesn't seem to impact performance.
I personally use the BFS version, as I find it somewhat faster than the CFS one. I have absolutely no wake lag, and I get good battery time.
Thanks go out to: snq-, bananacakes, sibere, tobi01001, thalamus, eviollet. If I forgot anyone, pls inform me.
CHANGELOG:
V05:
XZ compression
Fixed Wifi sleep
Tweaked OJ settings for better responsiveness (bananacakes)
Changed ramdisk compression method to gzip.
Rebuilt tun.ko and cifs.ko
v04b:
Fixed WIFI. (My bad. Forgot to adapt install script after including new ramdisk.)
v04:
Added Lowmemkiller tweak to ramdisk (3584,4096,8192,20992,23040,25088) No need for Autokiller or init scripts anymore. Over time I will move more tweaks into the ramdisk to minimize the need for init scripts.
Updated BFS to 0.406
Reverted battery gauge polling to 60 secs.
Added Virtuous governor. Virtuous is a highly tweaked SmartassV2.
Removed Lagfree governor again, as I found OndemandX better.
v03:
Hardcoded SD Speed Tweak to 2048. No need for init script anymore
Made 2-way call recording optional. Check downloads
Reduced battery gauge polling from 60 to 5 secs. (Untested)
A few bits more, can't remember it all.
v02:
Added Lagfree governor. Gives me a wee bit better battery, but sometimes lags when listening to music. Maybe I'll remove it again. Tell me what you think.
Added a minor change from tobi01001 to the lightsensor driver. Details here
Hopefully fixed USB fast charge.
Compiler optimizations
Link to my github: https://github.com/tristan202
Earlier i heard lot's of people complaining about reboots / hang up's when browsing internet with lowered WIFI voltages, i will give it a try today anyway thanks.
k3lcior said:
Earlier i heard lot's of people complaining about reboots / hang up's when browsing internet with lowered WIFI voltages, i will give it a try today anyway thanks.
Click to expand...
Click to collapse
I have been running with lowered wifi voltage for a few days without any problems at all. Doesn't browse much though, but market another wifi stuff have been working fine.
I'll give you feedback soon.
Thx and congratz.
Tapatalking.
tristan202 said:
I have been running with lowered wifi voltage for a few days without any problems at all. Doesn't browse much though, but market another wifi stuff have been working fine.
Click to expand...
Click to collapse
I've been using your kernel for several weeks now (tried all the rest) is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Thanks a lot mate the combination of HAVS, BFS, 1190 OC with UV to 825 working very nicely for me
beanbean50 said:
is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Click to expand...
Click to collapse
Just ask HTC they know everything about your phone
beanbean50 said:
I've been using your kernel for several weeks now (tried all the rest) is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Click to expand...
Click to collapse
siberes battery fix is included, and I have been making some tweaks to since the last release. Some minor stuff, but still some improvement.
tristan202 said:
siberes battery fix is included, and I have been making some tweaks to since the last release. Some minor stuff, but still some improvement.
Click to expand...
Click to collapse
wow, many thanks....
is there much difference between the 2 governors ondemandx and smartassV2...?
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
ziggy1001 said:
Thanks a lot mate the combination of HAVS, BFS, 1190 OC with UV to 825 working very nicely for me
Just ask HTC they know everything about your phone
Click to expand...
Click to collapse
haha...!
Yes, HTC, Google and every other Tom, **** and Harry...
beanbean50 said:
wow, many thanks....
is there much difference between the 2 governors ondemandx and smartassV2...?
Click to expand...
Click to collapse
Ondemand:
The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. This is available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
Smartass:
This is based on the concept of the interactive governor. This is included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Interactive:
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
This is available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
ironjon said:
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
Click to expand...
Click to collapse
tobi's autobrightnessmod is included. Adding to OP.
Thanks, I'll be testing this! I've been using snq-'s kernel builds but since the OC/UV ones have freezing problems, and gingercakes won't work for me without MASSIVE lag, I look forward to seeing how this works out.
ironjon said:
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
Click to expand...
Click to collapse
It seems to work, yes. I've just pushed my patched framework-res.apk, and auto-brightness seems to do exactly what it did on snq-'s patched kernel.
EDIT: Ah, ninja'd. Well, there you have it then.
tristan202 said:
Ondemand:
The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. This is available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
Smartass:
This is based on the concept of the interactive governor. This is included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Interactive:
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
This is available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
Click to expand...
Click to collapse
but we only have the first two governors to choose from, Interactive is not an option (in setcpu) or am I being stupid as per usual ...?
is usb fast charge enabled?
ZeGuitarist said:
Thanks, I'll be testing this! I've been using snq-'s kernel builds but since the OC/UV ones have freezing problems, and gingercakes won't work for me without MASSIVE lag, I look forward to seeing how this works out.
It seems to work, yes. I've just pushed my patched framework-res.apk, and auto-brightness seems to do exactly what it did on snq-'s patched kernel.
EDIT: Ah, ninja'd. Well, there you have it then.
Click to expand...
Click to collapse
where can I find the patched framework ?
beanbean50 said:
where can I find the patched framework ?
Click to expand...
Click to collapse
You have to patch your own framework-res
Tapatalking.
ironjon said:
You have to patch your own framework-res
Tapatalking.
Click to expand...
Click to collapse
can you guess my next question ...? hehe
Here you go i like helping the aged especially when, poor eyesight, liver damage, and tropical diseases have taken their toll
[How to] Adjust auto-brightness on GB Sense ROM
beanbean50 said:
where can I find the patched framework ?
Click to expand...
Click to collapse
You can't find it anywhere, you need to patch your own framework. The framework apk differs for each ROM, and contains each individual user's UOT kitchen mods too... So to be safe, you really shouldn't use someone else's framework.
Anyway, here's how to do it:
http://forum.xda-developers.com/showthread.php?p=17713587
It's pretty easy, as long as you know where your ROM's framework apk is (in internal /system, or in /sd-ext). Also, the thread suggest you put your framework mod in a flashable zip, but it's easier to just boot in recovery, and use adb to remove your old framework and push the new one.
Alright so here's the first release of this kernel for codeworkx's CM9 with hardware acceleration.
Again this is for codeworkx's cm9.
Also, this is for codeworkx's cyanogenmod 9.
One more time, this is for cm9 only.
Finally, this is for cm9 and cm9 only!
Don't let the "alpha" title fool you into thinking it's not stable... it is... It's only alpha because it's still in the "testing" phase.
FEATURES/CHANGES
Overclockable to 1.38GHz
Underclockable to 150MHz
GPU overclocked to 384MHz (highest possible without bottlenecking and battery waste)
Tuned OnDemand Governor (recommended)
Interactive Governor with time view concept (learns from your use and adjust parameters accordingly)
Wheatley Governor (optimized use of C4 state)
Hotplug Governor (turns of one of the cpus to save power when load is very low)
Pegasusq Governor (A better version of Hotplug, but experimental and not designed for our devices)
SIO scheduler for speed/performance with flash storage
Linaro Toolchain
Linaro optimizations and patches
Linaro makefile compiler flags
Makefile Optimizations to boost performance
Optimized CRC32
Optimized ARM RWSEM algorithm
Tiler Memory increased to 32MB (linaro)
Other Tiler patches/tweaks to improve 2D gpu performance
SLQB allocator
lib/string use glibc version for speed
lib/memcopy use glibc version for speed
lib/sha1: use the git implementation of SHA-1 and removed ARM sha1 routines
I/O backport from 3.2 linux kernel for less dirty throttling
Tweak CPUIDLE to enter deep sleep faster thus saving battery
LowMemoryKiller backported from 3.4 kernel
Disable GENTLE_FAIR_SLEEPERS for improved performance
Allow Deep Sleep to occur when media decoder is active allowing the cpu to shut off when playing music or video.
Allow MPU logic to power down when in deep sleep to save power.
Increased default readahead value to 1024KB for faster sdcard reads
A lot of stuff I probably forgot I did.
Also includes a ridiculous amount of bugfixes, patches, and tweaks that can found on my github commit log.
***Read Me***
DO NOT, UNDER ANY CIRCUMSTANCE, USE SETCPU PROFILES OF ANY KIND OR ANYTHING SIMILAR WITH THIS DEVICE. Things like screen off max frequency, temperature throttling, and others are already built in to the OMAP architecture. Using ANY profiles will ONLY lead to problems, instabilities, and battery drain.
***************
Let me know how it "feels" especially by default without overclocking or underclocking. Also I'd be interested in how the battery treats you. Thanks!
DOWNLOAD
a1 - Only for 7 inch
a2 - Only for 7 inch - Changes to: Wifi, GPU, Low Memory Killer, others
a3 - Only for 7 inch - Changes to: ondemand, interactive, add wheatley, add pegasusq, deep idle, compiler flags, SDcard read, others
a4 - not working... fix soon - Changes to: Compiler flags, CPUidle, RCU, others.
a5 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_10.1_CM9_a5.zip - reverts and bugfixes, use 10.1 ramdisk in 10.1 version.
a6 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_10.1_CM9_a6.zip - CLASSIFIED change, NEED feedback on speed, slowness, smoothness, and lag compared to stock and a5. Reverted some revets. Reverted changes to RCU to fix SODs. For 10.1 fixed overclocking.
Thanks go out to - CodeworkX, Ezekeel, Francisco Franco, Imoseyon, Faux123, Fugumod, Sonicxml, Texas Instruments, Samsung, Google, and all the others I probably forgot about. Sorry!
Source
https://github.com/Metallice
______________________________________________________________________________________________________________________
So, I'm a broke college student without a job this summer - instead taking extra classes and studying like crazy for the MCAT. If you like my work and want to thank me, feel free to buy a coffee or an energy drink so I can continue to stay up late studying and working on Android stuff (or help me pay for med school ). I don't want to have to choose! Thanks and I appreciate your support!
Metallice said:
Alright so here's the first release of this kernel for codeworkx's CM9 with hardware acceleration.
Again this is for clockworkx's cm9.
One more time, this is for clockworkx's cyanogenmod 9.
Finally, this is for cm9 and cm9 only!
Don't let the "alpha" title fool you into thinking it's not stable... it is... It's only alpha because it's still in the "testing" phase.
NO CLUE IF THIS WILL WORK AT ALL. I DO NOT HAVE THIS DEVICE.
***Read Me***
DO NOT, UNDER ANY CIRCUMSTANCE, USE SETCPU PROFILES OF ANY KIND OR ANYTHING SIMILAR WITH THIS DEVICE. Things like screen off max frequency, temperature throttling, and others are already built in to the OMAP architecture. Using ANY profiles will ONLY lead to problems, instabilities, and battery drain.
***************
Let me know how it "feels" especially by default without overclocking or underclocking. Also I'd be interested in how the battery treats you. Thanks!
DOWNLOAD
a1 - Only for 7 inch
a2 - Only for 7 inch - Changes to: Wifi, GPU, Low Memory Killer, others
a3 - Only for 7 inch - Changes to: ondemand, interactive, add wheatley, add pegasusq, deep idle, compiler flags, SDcard read, others
a4 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_10.1_CM9_a4.zip - Changes to: Compiler flags, CPUidle, RCU, others.
If you would like to overclock but your device can't handle it... and are willing to suffer through extreme battery drain to try this - Link
Thanks go out to - CodeworkX, Ezekeel, Francisco Franco, Imoseyon, Faux123, Fugumod, Sonicxml, Texas Instruments, Samsung, Google, and all the others I probably forgot about. Sorry!
Source
https://github.com/Metallice
______________________________________________________________________________________________________________________
So, I'm a broke college student without a job this summer - instead taking extra classes and studying like crazy for the MCAT. If you like my work and want to thank me, feel free to buy a coffee or an energy drink so I can continue to stay up late studying and working on Android stuff (or help me pay for med school ). I don't want to have to choose! Thanks and I appreciate your support!
Click to expand...
Click to collapse
I LOVEEEEEE YOU i absulutely love you MAN!~~~~~~~~~~~~~~~
His kernels and ROM's for the 7 are right on.
Good luck with this Metallice.
Thanks, but it didn't seem to go past the boot screen for me.
Sent from my Galaxy Nexus using Tapatalk 2
kuronosan said:
Thanks, but it didn't seem to go past the boot screen for me.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Which boot screen. I think I know the issue if its not the cyanogenmod one.
Sent from my GT-P3113 using xda premium
I have this issue too and it's the Tab2 10.1 screen. (the first one that shows during boot)
It's the Tab 2 Splash screen. I can adb, go into DL, and get into CWM so it's fine... it just won't boot.
Yeah its probably because I forgot to use the 10.1 ramdisk. I'll upload a fixed version shortly.
Sent from my GT-P3113 using xda premium
No worries man.
Thanks for getting started anyway, a lot of devs can use your fork now.
New version up. In addition to some bugfixes and reverts, this time the espresso10 ramdisk is actually used instead of the 7 inch version
Now it installs fine. What app should I use to control it? NSTools, Voltage Control, CPU Master, etc...
MultipleMonomials said:
Now it installs fine. What app should I use to control it? NSTools, Voltage Control, CPU Master, etc...
Click to expand...
Click to collapse
Glad to hear it. Let me know how it runs.
Really doesn't matter what you use as they all modify the same sysfs entries. I like no frills CPU control because its simple and only does what I need it to do.
Sent from my GT-P3113 using xda premium
Changing OC settings with NSTools or CPU control causes reboot. Settings don't change.
I can change min freq and governor (tried it with interactive and wheatly), just not max freq.
Works like a charm now. I'll keep you up to date on performance once I've done some testing.
Works fine in voltage control, and stable at 1380 so far with little heat. I haven't really stressed it though but it does run smoother and more responsive than before. The GPU seems snappier too. Great job.
Sent from my GT-P5113 using Tapatalk 2
Can you post a complete "feature list" with next version ? Oh, and can Voodoo sound be integrated for better (sound) quality ? I'll keep pressing the thanks button.
Thanks for the kernel, will test it later this day.
Maybe you can add an how to flash guide for the n00bs who want to flash but don't know how to do it?
works works works!!!!!!!!!! like an awsomeness thing! hehe i know that i can trust on you m8, but i did ask for it..yet and you made it! thx really THX!!!!!!
Hi,
Thank you for work but is what I am to have a problem of hangs and of connection with WIFI
Been testing the kernel with default settings for some hours now ... started using it since 11.oo this morning and started with a full battery. After playing some games (tablet/battery temperature stayed normal) and browsing the net, checking emails and some more stuff i must say the kernel works smooth and my tablet runs faster. Am using the kernel for 3.5 hours and the battery is at 71%. No weird things happened so far. WiFi and bluetooth both work fine in other words...
the kernel feels goOOOood
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
****Ares-Kernel****
****By****
****The~Skater~187****
This kernel is a combination of SmartPack/Boeffla-Venom Samsung Galaxy S5 Lineage OS kernel, with some tweaks and additions from around the net. I have decided that since SmartPack was EOL and with sunilpaulmathews ok, I would just combine our two kernels (since fbs has Boeffla-Kernels covered) to make it easier for me to maintain his work and my own.
/* DISCLAIMER! *\
*I am not responsible for any damage to your device*
* Everything you are doing on your device is at your own risk*
*Don't forget to make a back up before flashing*
~~~~~~~~~~~~~~~Flash at own risk~~~~~~~~~~~~~~~~~~
/* Supported devices *\
klte: SM-G900F, SM-G900AZ, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
kltekor: SM-G900K/L/S
kltedv: SM-G900P/I
klteduos: SM-G900FD, SM-G900MD
kltekdi: SCL23
/* Compatibility *\
DO NOT FLASH OVER CUSTOM KERNELS!
This kernel is only meant to work on Lineage-OS 15.1/16 and nothing else. However, it may work on other LOS-15.1/16 (and AOSP) based Oreo/Pie ROMs
This kernel will NOT work in Samsung Stock and other TW ROMs.
/* How-to-Install *\
*Download Kernel*
1. Go to recovery (TWRP recommend)
2. Flash Kernel
3. Reboot and enjoy
/* Incorporated SmartPack Features *\
Build from latest Lineage OS source code.
Built using latest GCC-8.x.
Anykernel for compatibility with maximum devices.
Linux Kernel version is updated to 3.4.113
Kernel tweaker app recommend: SmartPack-Kernel Manager (Please note: official Kernel Adiutor is NOT fully compatible with this kernel).
Added features include...
CPU voltage control
CPU Freq Gov: INTELLIDEMAND, INTELLIACTIVE, SMARTMAX, LIONHEART, NIGHTMARE, ADAPTIVE, ALUCARD, ZZMOVE, etc.
(for those who want to use zzzmove, I strongly suggest to carefully read this forum post by @Saber)
CPU hotplugs: Lazyplug, Alucard, and mako hotplug.
Full control over AC, USB and Wireless charging rate in SmartPack-Kernel Manager (Default charging rates: AC: 1800 mA; USB 700 mA; Wireless: 900 mA).
Boeffla Sound to control speaker and headphone volume.
(for official KA users, follow these instructions by @Exzu to create respective custom controllers for Boeffla Sound and Fast Charge.)
Adreno_Idler
CPU Input boost (configurable in SmartPack-Kernel Manager)
IO schedulers: FIOPS, SIO, VR, ZEN, FIFO, TRIPNDROID.
TCP congestion algorithms: Westwood, reno, cubic etc.
FRandom
Dynamic sync control 2.0
Boeffla Generic Wakelock Blocker
268 MHz CPU underclocked frequency cycle
Additional 27 MHz GPU frequency step (idle frequency)
KCAL v2
SELinux "Enforcing" by default (can be switched to "Permissive" in SmartPack-Kernel Manager)
a lot more...
/* Incorporated Boeffla-Venom Features *\
*Enable OC to 2995:
-DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. (I AM NOT RESPOSIBLE FOR YOUR DEVICE)
*Fast Charge
*ZZmoove adjusted to acommodate Overclocking (Thanks to Legitsu)
*Tweak bandwith on higher OC steps (Thanks to ktoonsz)
*Deadline I/O Tweaks (Ktoonsz)
*Fix memory leak with sysfs when stats table are freed (Ktoonsz)
*Bump up Max Voltage (Adjusted for higher OC) (Ktoonsz)
*Dirty Writeback Tweaks
*Increased VM_MAX_READAHEAD to 512 (default)
*Increased default entropy levels (both read and write)
*Optimized Kernel Samepage Merging
*QuickWakeup (Thanks CrazyGamer)
*PowerSuspend (Thanks Faux123)
*Cortex_A15 Optimizations (Fusion-Rom Dev Team)
*Slimbus Overclock (Ktoonsz)
*Slimbus Optimized Overclocking Of Master Component (CrazyGamer)
*VFP Tweaks (Ktoonsz)
*EXT4 Tweaks(Ktoonsz)
*GPU Overclocked up to 657 (Ktoonsz)
*Disable Swap Readahead
*Increase Maximum Swappiness
*Kernel mode neon (ShinySide)
*Disable Direct Reclaim File Pages
*Enable Unaligned Capability For ARM (CrazyGamerGR)
*Update min-default adreno frequency to be 200 MHz (kholk)
*Fixed memory entry leak when calling Adreno Convertaddr (Shubhraprakash Das)
*Changed clock rates to 19.2 MHz (Faux123/Qualcomm)
*Optimized Sched/Fair a bit (Faux123)
*Applied many new compiler optimizations (Synergy kernel Team & Decimalman)
*Zswap: Uses LZ4 now (if available)
*Support for LZ4-compressed kernel
*Fix memory leak in Mass Storage
*Added back Intellithermal V.2 Thermal Engine (for those who prefer it)
*Modified LowMemoryKiller (fbs)
/* Downloads Can Be Found Here *\
https://app.box.com/s/nx7nuf7vb2eubd5sfrr5rerjsatcp42i
/* Special note to Korean S5 users *\
(Thanks to sunilpaulmathews defconfig files)
Flashing this kernel after AOSP/LOS based Oreo/Pie ROMs originally build for the klte (SM-G900F) variant SHOULD allow the use of those ROMs on SM-G900S/K/L.
/* Acknowledgements *\
@haggertk for LineageOS for Galaxy S5
@Lord Boeffla
@franciscofranco
@Sultanxda
@arter97
@faux123
@CrazyGamerGR
@Saber
@nathanchance
@ZaneZam
@osm0sis for AnyKernel project
@Grarak for Kernel Adiutor
@sunilpaulmathew
@justjr for SmartPack efficiency profile
@ktoonsez
@KazuDante
@fbs
@kholk
@decimalman
@Synergy Kernel Team
Many other XDA developers
XDA:DevDB Information
Ares-Kernel, Kernel for the Sprint Samsung Galaxy S5
Contributors
The~Skater~187, sunilpaulmathew
Source Code: https://github.com/187MoD/Ares-Kernel
Kernel Special Features: Boeffla-Venom + SmartPack Kernels
Version Information
Status: Beta
Current Beta Version: Beta-v1.6
Beta Release Date: 2019-02-15
Created 2019-02-15
Last Updated 2019-08-26
***Ares Kernel Changelog***
~~~~~Beta-v1.7~~~~~
*Up-to-date with Lineage-OS source as of 01.01.2020
*Update Intelli-plug to version 3.9 (Compliments of Pascua28)
*sound: Compiled with -Os optimization (Compliments of Pascua28)
*A few other optimizations
~~~~~Beta-v1.6~~~~~
*Up-to-date with Lineage-OS source as of 08.25.2019
*Compiled using Bleeding-Edge Toolchain 9.2
*Cortex A-15 MSM-memutil optimizations for better memory performance
*GPU compiler optimizations
*Enable: Frontswap
*Enable: Runtime compcache
*Removed un-supported SOC features (Thanks pascua28)
*Fix possible memory leak in slub.c (Thanks pascua28)
*Add Missing xor-neon file
*Compiled with many new compiler optimizations
*Plus more
~~~~~Beta-v1.5~~~~~
*Up-to-date with Lineage-OS source as of 07.15.2019
~~~~~Beta-v1.4~~~~~
*Up-to-date with Lineage-OS source as of 05.27.2019
*Compiled with "Bleeding-Edge-Toolchain" 9.1
*Compiled with 03 compiler optimizations
~~~~~Beta-v1.3~~~~~
*revert: disabled "CAF" cpu policy save code (Fixed cores not scaling properly)
*MSM Limiter updated
~~~~~Beta-v1.2~~~~~
*Up-to-date with Lineage-OS source as of 03.19.2019
*reverted to stock Lineage-OS LMK (Low Memory Killer)
*bumped OC up to 3072 -DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. I AM NOT RESPONSIBLE FOR YOUR DEVICE!)
*bumped up voltage overhead to hopefully help stabilize new OC step
*added Intelliplug_hotplug driver (Now default hotplug service)
*added Touchboost driver (adjusted for 3072 oc)
*added MSM CPU Limiter (adjusted for 3072 oc)
*enabled Arch Power
*added the ability to Toggle Arch Power And Sleepers (compatible with SmartPack Manager)
*disabled "CAF" cpu policy save code (Faux123)
*added msm_mem_utils for added memory performance
*disabled constant spam in dmesg from 'undefined instruction' print statement in traps.c
*ZZmoove: adjusted to acommodate Overclocking to 3072
*added Boeffla-compiled In-Kernel Busybox
*some other things
~~~~~Beta-v1.1~~~~~
*Up-to-date with Lineage-OS source as of 03.02.2019
*Ares-Kernel boot script: update default profile settings (credits: justjr)
*import Core Control fix (sunilpaulmathew)
*import "Hotspot" fix (sunilpaulmathew)
*added a compatible version of "Tuned" LowMemoryKiller (fbs)
*added support for lz4 compressed kernel
*added some compression tweaks to help with boot performance
*driver/char: add missing frandom commits
*fs/sdcardfs/mmap.c: add AIO optimization flag compatibility fix up
*kernel/power: add missing quickwakeup commit
*Optimized ARM RWSEM Algorithm (Faux123)
*Tuned thermal management a bit
*Some other stuff
~~~~~Beta-v1.0~~~~~
-Initial Merge of SmartPack/Venom Sources
*Synced With latest LineageOS Sources as of 02.13.19
*Built with Latest 8.2.1 toolchain using SunilPaulMathews build Framework
*Compatible With Kernel Auditor & Should Be Compatible SmartPack-Kernel Manager
*Enable OC to 2995:
-DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. I AM NOT RESPOSIBLE FOR YOUR DEVICE)
*Boeffla Sound
*Fast Charge
*ZZmoove: adjusted to acommodate Overclocking (Thanks to Legitsu)
*Enable 268 mhz underclock (Thanks to SunilPaulMatthew)
*Tweak bandwith on higher OC steps (Thanks to ktoonsz)
*Tweak deadline: Allow 0ms deadline latency, increase the read speed (Ktoonsz)
*Set audience sleep delay to 0 to fix delay upon making phone calls
*Async I/O latency to a ssd greatly increased (34% gain,kleikamp & Ktoonsz)
*Fix possible memory leak with sysfs when stats table are freed (Ktoonsz)
*Bump up Max Voltage (Adjusted for higher OC) (Ktoonsz)
*Dirty Writeback Tweaks
*Increased VM_MAX_READAHEAD to 512
*Increased default entropy levels (both read and write)
*Optimized Kernel Samepage Merging
*QuickWakeup (Thanks CrazyGamer)
*PowerSuspend (Thanks Faux123)
*Cortex_A15 Optimizations (Fusion-Rom Dev Team)
*Add Missing Graphite Define (Ktoonsz)
*Slimbus Overclock (Ktoonsz)
*Slimbus Optimized Overclocking Of Master Component (CrazyGamer)
*VFP Tweaks (Ktoonsz)
*EXT4 Tweaks(Ktoonsz)
*GPU Overclock up to 657 (Ktoonsz)
*Disable Swap Readahead
*Boeffla wakelock blocker (Thanks to sunilpaulmathew & franciscofranco)
*Increase Maximum Swappiness
*Kernel mode neon (ShinySide)
*Disable Direct Reclaim File Pages
*Enable Unaligned Capability For ARM (CrazyGamerGR)
*Update min-default adreno frequency to be 200 MHz (kholk)
*Fixed memory entry leak when calling Adreno Convertaddr (Shubhraprakash Das)
*Change clock rates to 19.2 MHz (Faux123/Qualcomm)
*Optimize Sched/Fair a bit (Faux123)
*Applied many new compiler optimizations (Synergy kernel Team & Decimalman)
*Zswap: Uses LZ4 now (if available)
*Support for LZ4-compressed kernel
*Fix memory leak in Mass Storage
*Alucard, LazyPlug & Mako Hotplugging
*Enabled VNSWAP
*Added back Intellithermal V.2 Thermal Engine (for those who prefer it)
*Modified LowMemoryKiller (fbs)
# All Changes
# Signed Off
# By
# The~Skater~187
Reserved
~~~~~~~~~~~ Please note~~~~~~~~~~~
If you need support, please supply the following or support will not be given:
*Device Variant
*Current Rom & Android Version
*Bootloader & Baseband version
*Recovery & Version
*Recovery Log
I can't help if the only details given are "It didn't work" or "I can't flash this".
One More For Good Measure
YES.!!!!
sdfat code have syntax errors, aren't even compiling here.. humm
ok, fixed it and stealed it
Thanks for ur good kernel. Flashed on haggertk android pie no problem so far. At first I was getting random reboots,it caused by my magisk modules. I disable them and the problem fix. Thanks again.
LKT magisk module on this kernel cause random reboots.
Thanks for your work
So I popped over to this thread you linked to from the Venom thread and want to make sure I'm clear. This kernel (Ares-Kernel) should not be used on a Resurrection Nougat based ROM? I think that Resurrection Nougat ROM is a Lineage 14 based ROM, correct? Or even though it is Lineage 14 based, can the Areas-Kernel still be used because it is based off Lineage.
Thanks for any clarification. Left this post in other thread to just to make sure I got it in right spot. Disregard which ever one is posted in wrong spot. Thanks.
awesome dude!!! thank you so much! i'm really glad that someone continues the smart-pack kernel!
:laugh: big, Big, BIG Thank you @The~Skater~187! Really appreciate your effort and dedication in helping to keep this old phone alive and competitive! :highfive:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as the tunable io_is_busy 0 to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
justjr said:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
Click to expand...
Click to collapse
I do apologize about the credit issue, I thought I had put your name in the acknowledgment section right before ktoonsz last night, as I noticed your name on a few of the files in the RamDisk. I will definitely straighten that out and thank you for pointing that out. You are correct, I so far have just synced SmartPack source, then started applying things from my other kernel for now. I wanted to get something up-to-date and stable out for you guys before I started diving deeper into other kernel related things.
As for the rest of your suggestions, I will look into them for sure. Feel free to p.m. me with any thoughts or other suggestions.
Sent from my kltespr using Tapatalk
The~Skater~187 said:
I do apologize about the credit issue, I thought I had put your name in the acknowledgment section right before ktoonsz last night, as I noticed your name on a few of the files in the RamDisk. I will definitely straighten that out and thank you for pointing that out. You are correct, I so far have just synced SmartPack source, then started applying things from my other kernel for now. I wanted to get something up-to-date and stable out for you guys before I started diving deeper into other kernel related things.
As for the rest of your suggestions, I will look into them for sure. Feel free to p.m. me with any thoughts or other suggestions.
Sent from my kltespr using Tapatalk
Click to expand...
Click to collapse
Many thanks!
On other news, I was getting some random reboots, and found out that it was because of my undervolt settings. It's super weird, because they never gave me any problems since 3~4 months with the smartpack kernel, and it should be a setting particular to my specific device/cpu, and have the same limits across any kernel. I used the same across lots of roms, and different versions of smartpack, for nougat, oreo and pie, so, I hope you can see why I find this very weird.
But, I don't know if it's actually a 'bug', I will find some time to fine tune it, raise some voltages to see where I can go with Ares kernel without crashing. For now I'm using the default voltages.
justjr said:
Many thanks!
On other news, I was getting some random reboots, and found out that it was because of my undervolt settings. It's super weird, because they never gave me any problems since 3~4 months with the smartpack kernel, and it should be a setting particular to my specific device/cpu, and have the same limits across any kernel. I used the same across lots of roms, and different versions of smartpack, for nougat, oreo and pie, so, I hope you can see why I find this very weird.
But, I don't know if it's actually a 'bug', I will find some time to fine tune it, raise some voltages to see where I can go with Ares kernel without crashing. For now I'm using the default voltages.
Click to expand...
Click to collapse
I did do a bit of an overhaul on the voltage table when I added the higher oc steps, due to the fact that on my other kernel lower voltages stock we're causing problems and random freezes.
Sent from my kltespr using Tapatalk
Yeah, I'm sure you know, undervolting need to be done step by step, making sure the lowest you can go, device specific, so risking repeating myself, same voltages should probably 99,99% of the time works across any kernel/rom on a given device. I don't think it is the undervolt anymore.
It took a while but I still had some reboots with default voltage, once I was finally able to press up and home right after it, so it rebooted directly to TWRP and I copied the last_kmsg, it's attached, all configs were on default. I hope it helps to find out what it may be.
I'm back on smartpack for now, cause the same setup and profile runs without no problems, so I think it should not be a problem just on my end, is it? Anybody else?
Fun fact, I was are able to dirty install smartpack kernel over ares and vice-versa and it detected and updated itself without any problems.
I'm able to go kinda low here with no crashes:
660
670
680
690
700
710
720
730
745
750
775
795
825
865
925
965
990
1005
1035
1060
@The~Skater~187 edit: oh, I just noticed, there's no option to input 268 MHz voltage. My voltages are getting placed on the wrong frequency because of that, found the problem!
I recovered the backup I just made before installing the kernel, I had installed the shushified bootleggers 3.0 on top of the unshushified 3.0, they are the same rom except for official (shushified) status, but anyway, that may be the cause of some of my problems, adding up to the 268 missing voltage that was overlooked by me.
After that I installed Ares kernel again with no undervolt and gone to sleep. Woke up today, and no reboots, then I was trying to test undervolting it and found out about the missing 268 voltage, so every previous voltage I used was getting used on 1 clock step above, so, not enough power for sure.
Just put my exactly same volts on their correspondent freq and no reboots until now!
It also seems that Core Control is staying enabled and VD Restrictions is disabled correctly now too. So, if you experience the same you may disregard it as well.
Thanks for this!!
Great so far, this with Pie ROMs is the best battery life I've had since stock.
4-5 hours sot, 7h active, 12h idle..(gsam stats) on this original 2800mah. I've gone from 4-5 charges a day to 1-2.
And kernel brightness control keeps the flickers away.
Edit: did notice both vdd and core thermals being active, didn't cause any overheating/reboots (i often run cpu info as overlay) but I stuck with core control only to be safe. It doesn't stick after reboot.
S5 klte
Latako said:
Edit: did notice both vdd and core thermals being active, didn't cause any overheating/reboots (i often run cpu info as overlay) but I stuck with core control only to be safe. It doesn't stick after reboot.
S5 klte
Click to expand...
Click to collapse
Yeah, after some further analysis, I came to find out exactly the same.
After a reboot both VDD and CC come back up, and I have to do a little dance, like, disable vdd and cc, enable intellithermal, then enable only cc, or something like that, then it will stick with only cc until the next reboot.
Ok, so I decided I'm going keep an "unofficial" SmartPack kernel going (nothing more than source updates will be applied) as well as my off shoot kernel project. I will have it available for you guys tomorrow evening.
Sent from my kltespr using Tapatalk
justjr said:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as the tunable io_is_busy 0 to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
Click to expand...
Click to collapse
So is it possible to use your profile without any errors?