Related
Sorry for disappearing guys, I wasn't in the mood for posting or working on the kernel: unfortunately it looks like I bricked my phone.
I couldn't believe it myself but as soon as I restarted it phone after CWM-flashing my usual JPO rom, going back from official JPU+803.pit, the screen went black and never came up again, no matter the key combination. No signs of life besides warming up slightly after pressing power or connecting the USB cable. No luck with a JIG cable aswell, tried all the way from 290K to 315K Ohm and nothing happens... I guess there's nothing I can do.
The problem is, I came back to Europe last month and official Samsung centers around here are refusing to offer repair services on US phones because of some kind of freak policy they have, even if I pay myself.
Update Dec 13:
I have no words to explain how thankful I am: PAulyhoffman offered to donate a spare phone he had, and promptly shipped it on the same day.
A special mention goes to Patrick Richter, Pauly's father in law, who just passed away on Saturday: a most generous man in honor of whom he would like to dedicate the donation.
I've already covered the shipping fee myself but customs will add a variable amount in taxes (most definitely 20% of original value as they usually do, although the specified value is just $100).
Hoping customs won't hold the package over the holidays, untested version versions will have to do for now.
HUGE thanks go to every single one who offered help, I really am moved by the affection demonstrated by this wonderful community.
Click to expand...
Click to collapse
I've compiled a Kernel based on Sztupy's ULF and xcaliburinhand's re-oriented kernels, including OC/UV support, 340Mb RAM and compiling optimizations.
Being based on the i9000 JPM source, it comes with every issue xcaliburinhand's kernel might have.
As I have absolutely no kernel programming knowledge, all credit goes to the respective coders: I've merely copied, pasted and compiled things, so I won't be able to offer much additional support or modify any of the function unless they provide source.
THIS IS A FROYO KERNEL, USE ONLY WITH A 2.2 ROM, PREFERABLY AN I9000 ONE
DO NOT USE SETCPU
Features:
- Sztupy's Ultimate Lag Fix V. pre-0.4https://github.com/sztupy
Multiple configurable Lagfix options:
Ext4 No-Journal DATA: /data converted to Ext4 with no journaling, everything else stays RFS
Ext4 No-Journal ALL: /data, /cache and /dbdata converted to Ext4 with no journaling
Ext4 DATA: /data converted to Ext4, everything else stays RFS
Ext4 ALL: /data, /cache and /dbdata converted to Ext4
Ext2 DATA: /data converted to Ext2, everything else stays RFS
Ext2 ALL: /data, /cache and /dbdata converted to Ext2
Advanced options: lets you specifically configure each partition and eventually add an Ext2 loop on top of them
Ext3/4 mount options: enables writeback journaling mode
(Using BIND_DATA_TO_DBDATA you might run out of space with many apps installed)
Suggested configuration (Ext4 ALL):
DATA_FS=ext4
CACHE_FS=ext4
DBDATA_FS=ext4
DATA_LOOP=false
CACHE_LOOP=false
DBDATA_LOOP=false
BIND_DATA_TO_DBDATA=false
Use FAST mount opts
You will get a "Configuration has changed" recovery screen at the first reboot after setting lagfix options, it's perfectly normal. If you wish to keep your current data, select the first option and wait (a separate backup is recommended).
- Modded CWM integrated
- CWM pre-installed (no more install from update.zip)
- reboot to 2e recovery
- reboot to download mode
- tweaking options
- root from recovery
- configure lagfix
- raspdeep's OC/UVhttp://forum.xda-developers.com/showthread.php?t=822027
If you do not want to mess with commands, use Xan's Voltage Settings app
- do note that you're subtracting voltage from the default setting, which varies with frequency:
Code:
1600MHz CPU 200MHz GPU 1400mV
1552MHz CPU 194MHz GPU 1375mV
1488MHz CPU 186MHz GPU 1350mV
1440MHz CPU 205MHz GPU 1325mV
1400MHz CPU 200MHz GPU 1300mV
1344MHz CPU 192MHz GPU 1300mV
1288MHz CPU 184MHz GPU 1300mV
1200MHz CPU 200MHz GPU 1300mV
1000MHz CPU 200MHz GPU 1275mV
800MHz CPU 200MHz GPU 1200mV
400MHz CPU 200MHz GPU 1050mV
200MHz CPU 200MHz GPU 950mV
100MHz CPU 100MHz GPU 950mV
the lastest Voltage Settings version includes voltage calculation
- 345Mb available RAM with 720p and JPU support
And improved minfree memory management
- Hardcore's SpeedModhttp://forum.xda-developers.com/showthread.php?t=822756
- jhash3
- Kernel HZ
- startup tweak scripts (available from cwm)
- ext4 kernel patches from http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/
- compiling optimizations:
(thanks to laststufo)
-O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mthumb -fno-gcse -fprefetch-loop-arrays --param l2-cache-size=512 --param l1-cache-size=64 --param simultaneous-prefetches=6 --param prefetch-latency=400 --param l1-cache-line-size=64
- config optimizations: (XT variant only)
CONFIG_UACCESS_WITH_MEMCPY=y
CONFIG_KSM=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
additional config settings found in other kernels are pointless or even counterproductive for performance/stability
- BFQ I/O schedulerhttp://lwn.net/Articles/306641/
Set as default, you may change it using Xan's Voltage Settings app
- supercurio's Voodoo Color&Sharpnesshttps://github.com/project-voodoo
- HSUPA support (with i9000 modems)
Enable WCDMA 850Mhz by dialing *#2263# (COMBI BANDS -> choose WCDMA 850)
- neldar's v2.2 BackLight Notifications supporthttps://github.com/neldar/backlightnotification
Configure with BacklightNotification settings app
To enable BLN it is necessary to flash a CWM zip or enable BLN in CWM from ULK advanced options
- Boot animations support
http://forum.xda-developers.com/showthread.php?t=819686
http://forum.xda-developers.com/showthread.php?t=822955
http://forum.xda-developers.com/showthread.php?t=623960
Once again, none of it comes from me and all credit goes to the original developers, especially xcaliburinhand, raspdeep and hardcore
Nevertheless, if you're feeling particularly generous and have already provided for the developers, I'll gladly accept a token of gratitude (after all, being so ignorant I did have to invest quite a bit of time into it).
Everything comes at your own risk, I offer no support at all.
Thank you aleadam, ReedX50v, junktzu, shaolin95, Shane, krl66, Smokestack76, Henry, Xstop, lpsi200, Arffer, newter55, Lertets, txRangerXDA, id10terrordfw and Bedwa for your donations.
Code:
- v1.5.6
fixed boot-up and CWM instability
updated modules from JPX kernel
new frequency table
full compatibility with Voltage Control 3 (lowering frequency with it seems to cause freezes)
removed update_frequency, making changes to the freq table immediately applies them
- v1.4.7
fixed boot animation issues
fixed init.d script execution
fixed CIFS support
- v1.5.5
lowered default freq to 1000MHz
updated ram disk to late 1.4.x versions
improved wi-fi performance
fixed internal SD mount as CD-ROM on JPU
- v1.4.6
improved wi-fi performance
fixed internal SD mount as CD-ROM on JPU
Changelog:
- v1.4.5
Frequencies/battery fix
- v1.4.4
added workaround script inside the update.zip to execute voltage control boot settings directly from the program's data dir, eliminating the necessity to remount /system
gained an additional MB of RAM thanks to kernel size optimization
implemented Xcaliburinhand's wired headset fix
optimized RAM utilization (minfree tweaks)
updated CWM to include Hardcore's latest additions
slight menus reorganization
updated optimization scripts (now including battery optimizations, GPS tweaks, CIFS support)
built-in support for ext2, ext3 and ext4 no-journaling (you will see a "configuration changed" screen if you manually disabled journaling - select "No, enter recovery mode" and switch ext4 to ext4nj)
built-in support for ext4 mount optimizations (writeback mode)
HZ=500, PREEMPT_VOLUNTARY
JPU variant with modules and mem config extracted from samsung's JPU kernel: DO NOT USE IT ON FIRST BOOT OR YOU'LL GET AN ENDLESS VIBRATING BLACK SCREEN, BOOT ON SAMSUNG JPU AND ONLY THEN FLASH THIS KERNEL
v1.5.4
initial boot and recovery frequency lowered from 1200MHz to 800MHz
reduced voltage change delay
frequency jumps set up more like 1.4 in order to improve performance
v1.5.3
/system mounts as RO
added workaround script inside the update.zip to execute voltage control boot settings directly from the program's data dir, eliminating the necessity to remount /system
corrected frequencies script, should now work on every ROM
only available as a CWM update.zip to make sure everyone has working init scripts
increased default voltages for 1456-1464MHz to 1325mV, 1504-1544MHz to 1375mV and 1600MHz to 1400mV, regulate your UV settings BEFORE upgrading
gained an additional MB of RAM thanks to kernel size optimization
v1.5.2
DELETE USER GENERATED SCRIPTS IN /system/etc/init.d/ BEFORE UPGRADING
(remember it's necessary to unlock higher frequencies from both freq_table and Xan's app)
implemented Xcaliburinhand's wired headset fix
mount /system R/W - could be dangerous, but solves script creation issues
optimized frequency jumps for better battery life
optimized RAM utilization (minfree tweaks)
workaround for the highest frequency step being sometimes briefly used during bootup and recovery operation
effectively set 1200MHz as the default frequency
corrected wrong display of highest frequency in Quadrant
added frequencies scheduler script in the CWM zip package with a visual aid
reorganized performance levels with a few additions
- v1.5.1
skipped, integrated in 1.5.2
- v1.5
updated raspdeep's OC/UV to v300
multiple performance levels:
100
200
400
800
1000
1200
1360 (GPU downclocked, don't worry performance improves anyway)
1400
1440 (GPU slightly overclocked)
1460 (GPU downclocked)
Default clock at 1200MHz, additional frequencies can be enabled by editing /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
in order to update the states table it's necessary to edit to 1 /sys/devices/system/cpu/cpu0/cpufreq/update_states (echo from terminal or by manually editing the file, just like the states table)
added compatibility with Xan's voltage app v2.0 (please update, v1.9x wouldn't work correctly)
reduced 14xxMHz default voltage to 1.3v
updated CWM to include Hardcore's latest additions
slight menus reorganization
updated optimization scripts (now including battery optimizations and CIFS support)
built-in support for ext2, ext3 and ext4 no-journaling (you will see a "configuration changed" screen if you manually disabled journaling - select "No, enter recovery mode" and switch ext4 to ext4nj)
built-in support for ext4 mount optimizations (writeback mode)
- v1.4.3
fixed 2e recovery, now completely functional
added 1350Mhz, 1400MHz and 1450MHz variants, only available as ODIN packages. The latter two have a default voltage of 1350mV. Keep using Xan's Voltage App v1.98b's 1200MHz setting to undervolt, higher frequencies replace the 1200MHz step, bear in mind the app doesn't show the updated frequency/voltage. Remember to reset said setting before upgrading and please realize how 14xxMHz will only run on few lucky devices
from now on there won't be a CWM version for 1350MHz+ and XT variants as well as a release integrating the modem, just install it on its own if necessary
- v1.4.2
implemented Tiny RCU
re-enabled Samsung's bootanimation when there's no bootanimation.zip
re-added -noatime optimization script
XT variant: 1280MHz, config optimizations: HZ=500, PREEMPT_VOLUNTARY, UACCESS_WITH_MEMCPY, KSM (possibly unstable, slightly higher performance and battery drain, might be necessary to lower UV)
- v1.4.1
fixed BLN (flashing as update.zip or re-enabling it from CWM might be necessary)
- v1.4
raspdeep's OCUV updated to v217
implemented fastscaling for 100-400MHz frequencies
added 1280MHz variant (UV setting for 1200MHz applies to 1280MHz, so reset it)
ULF updated to pre-0.4, modified to support bootanimations
fixed potential /system corruption
integrated JK3 modem in CWM flash package
kernel version updated to reflect frequency variant (#140-1280 / #140-1200)
BLN has issues
- v1.3.5
removed config optimizations
removed -noatime remount script
(should provide stability for those experiencing hangups/reboots/charging issues)
- v1.2.6
removed config optimizations (should provide stability for those experiencing hangups/reboots/charging issues)
HZ=300
- v1.3.4
rebuilt from scratch
even more stability fixes
build # updated according to version (#134->v1.3.4)
- v1.2.5
rebuilt from scratch
additional FS optimization script to remount partitions with -noatime included in the I/O Scheduler script
fixed script execution
kernel HZ back to default
build # updated according to version (#125->v1.2.5)
- v1.3.3
fixed screen lock issue
kernel HZ lowered to 300
more stability fixes
supposedly fixed charging issues (oneclick to JF6, reset battery stats and masterclear)
- v1.3.2
stability fixes
- v1.3.1
included ext4 patches from [url]http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/[/url]
additional FS optimization script to remount partitions with -noatime included in the I/O Scheduler script
- v1.3
Corrected a small bug that was preventing scripts from running
updated raspdeep's OC/UV to v2.1
update [url=http://forum.xda-developers.com/showthread.php?t=829731]Xan's app[/url] to undervolt
- v1.2.1
hopefully fixed script execution on Captivate ROMs aswell
fixed CWM option for enabling BLN
fixed 500hz setting
enabled CONFIG_UACCESS_WITH_MEMCPY and CONFIG_PREEMPT_VOLUNTARY as they apparently make no difference in battery use
- v1.2
increased available RAM to 343Mb
updated BLN to v2.2
- v1.1.1
enabled init.d script execution on boot (Xan's app voltage settings are now being kept)
- v1.1
added BFQ I/O scheduler
updated Voodoo color&sharpness
BLN reverted to v2.0, now working (flashing from an update.zip is required to install the Library)
- v1.0.1
fixed JFS filesystem support, added bootanimations, BLN still not working (no clue why not, waiting for xcaliburinhand's upcoming update)
- v1.0
initial release
RESET ALL UV SETTINGS (DELETE INIT.D SCRIPTS) BEFORE UPGRADING TO HIGHER VERSIONS
IF YOU'RE HAVING SLEEP DEATH ISSUES, REVISE UV SETTINGS
Modules and mem config extracted from samsung's JPU kernel: DO NOT USE THIS KERNEL ON JPU FIRST BOOT OR YOU'LL GET AN ENDLESS VIBRATING BLACK SCREEN, BOOT ON SAMSUNG STOCK AND ONLY THEN FLASH THIS KERNEL
The XT variant is slightly faster but can cause instability (which might require higher voltage) and charging death.
Voltage Control 3 supports enabling higher frequencies from the freq table, but doesn't yet let you disable selective ones.
To disable a certain frequency its corresponding value in /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table has to be set to '0'.
Changing update_states is no longer necessary. That file can either be manually edited or modified through an 'echo' command, which is much more convenient if you're in front of a PC and able to use ADB.
It's a volatile RAM file, which means changes made to it won't stick through reboots; I've included a script that reapplyies settings on boot in the CWM package (also attached to this post).
Let's say you wish to overclock to 1400MHz and disable 1288-1344:
1344MHz corresponds to the 6th value, 1288 to the 7th:
Code:
#!/system/bin/sh
#SET OC - below are GHz decimals (i.e. 1.60GHz, 1.55GHz, 1.50GHz and so on)
#60 55 48 44 40 34 28 20 00 .8 .4 .2 .1
[color=red]#[/color]echo 0 0 0 0 1 [color=blue]0[/color] [color=blue]0[/color] 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
REMEMBER TO REMOVE # FROM THE LAST LINE
jk3_modem_update.zip
SetiroN_v1.4.7xt_1600.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7_1600.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7xt_1552.tar.7z [email protected] frequency - 194MHz GPU
SetiroN_v1.4.7_1552.tar.7z [email protected] frequency - 194MHz GPU
SetiroN_v1.4.7xt_1488.tar.7z [email protected] frequency - 186MHz GPU
SetiroN_v1.4.7_1488.tar.7z [email protected] frequency - 186MHz GPU
SetiroN_v1.4.7xt_1440.tar.7z [email protected] frequency - 205MHz GPU
SetiroN_v1.4.7_1440.tar.7z [email protected] frequency - 205MHz GPU
SetiroN_v1.4.7xt_1400.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7_1400.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7xt_1344.tar.7z [email protected] frequency - 192MHz GPU
SetiroN_v1.4.7_1344.tar.7z [email protected] frequency - 192MHz GPU
SetiroN_v1.4.7xt_1288.tar.7z [email protected] frequency - 184MHz GPU
SetiroN_v1.4.7_1288.tar.7z [email protected] frequency - 184MHz GPU
SetiroN_v1.4.7xt_1200.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7_1200.tar.7z [email protected] frequency - 200MHz GPU
setiron_v1.5.6.tar.7z
setiron_v1.5.6_cwmupdate.zip
setiron_v1.5.6xt.tar.7z
setiron_v1.5.6xt_cwmupdate.zip
Voltage Control 3 alpha3
FINALLY! Going back to 2.2 so i can try this out. Can't wait for the link.
Sent from my Cappy using mental telepathy, *****ezz.
SetiroN said:
- neldar's v2.2 BackLight Notifications support
coming in the next release
Click to expand...
Click to collapse
Awwww that's a deal breaker for me, need bln badly. But yes finally, sztupy ulf on the cappy.
BLN now included, untested.
Awesome. I've been trying to figure out the how to do all this as well. I edited the code this morning at work and I just thought I'd check XDA while CodeSourcery finished installing...and what do I see?
I'll be flashing this immediately. FWIW, I've actually been running raspdeep's OC/UV 2.0 since Monday. I have it set at -100UVLF, -75UVHF, and I've had absolutely no problems with it at all, but it seems to be a YMMV situation. I don't think all processors can handle the UV. Even with (I think) unhelpful's, JAC's, and kingklick's kernels for the Galaxy S, phones handle the UV fine, some don't. Battery life is amazing with this though.
Also, I've had problems with screen off settings with setCPU. You probably don't want to use them at all.
SetiroN said:
BLN now included, untested.
Click to expand...
Click to collapse
that's some fast support...
Yes please. Link?
DOAlaboratories said:
that's some fast support...
Click to expand...
Click to collapse
Can I get this uploaded in Shep's rom since he is "unavailable" until tomorrow Since you are so fast at making peoples dreams come true
/sarcasm
so has anyone run this yet? it seems pretty alpha and my phone just went into download mode to test it
By the way everyone - the UV is still what I think raspdeep considers alpha. You will probably want to stress your system a bit to ensure it can handle it. I found that with -100UVLF/-75UVHF flash video was a little bit choppier than with the settings at -75UVLF/-50UVHF.
That said, it has been steady for me over the last couple days, no problems at all with it. I can watch flash video and my CPU temps still stay under 100.
Also, link to xan's UV GUI seems to be missing - so here is another one.
And having alogcat installed and knowing how to use it would probably be the best practice if you want to help raspdeep make this even better.
Athailias said:
Can I get this uploaded in Shep's rom since he is "unavailable" until tomorrow Since you are so fast at making peoples dreams come true
/sarcasm
Click to expand...
Click to collapse
Just get in download mode and flash it over
SetiroN said:
I've compiled a Kernel based on Sztupy's ULF and xcaliburinhand's re-oriented kernels
Click to expand...
Click to collapse
Which version of reorient is this based on?
Thanks!
Since I see the compass patch works, it is at least version 2.1.1...
watch out, i think this may have master cleared me...
simething did at least.
no worries though, i have a whole SDCARD backup, so it's all good
This is freaking sweet. I am undoing voodoo at the moment and then will flash and give it a try. I am on the memory version of reorient at the moment so I will post back when results
it keeps booting intoa recovery loop on me after applying a lagfix
DOAlaboratories said:
it keeps booting intoa recovery loop on me after applying a lagfix
Click to expand...
Click to collapse
What lagfix are you trying to install? I got that with trying to use all=jfs, switching to all=ext4 worked.
BLN doesn't seem to be working. Yes I did enable it in the custom recovery menu, and yes I'm using a version of Mms.apk that supports "led notifications."
Has anyone tried with cogs new b2.3 rom yet? How is the battery life?
glitterballs said:
What lagfix are you trying to install? I got that with trying to use all=jfs, switching to all=ext4 worked.
Click to expand...
Click to collapse
JFS overkill was what did it me and obsessing over having the best ****.
i'll try RFS overkill and see if that works. also, after i got it to boot back up, it wouldn't install any apps
Can I flash this over Tayutama's Tom using ODIN? What slot do I put the file in?
The Onix Kernel (aka SuckerPunch) is based off Speedmod K13D with OC/UV up to 1.6ghz + More!
Since based on i9000 sources, use an i9000 modem
As always, flash at your own risk, im not responsible for any damages!
Get support at #suckerpunch
Download older versions HERE
Latest development is found on GitHub
Latest official sources is attatched below <<Recommended
>>>FAQ Post #2<<<
--To install--
Always have a backup incase something goes wrong
Flash with CWM or Odin/Heimdall
I recommend to clear Cache and Dalvik Cache (first boot will take longer)
EXT4 lagfix is recommended
If coming from a different OC/UV kernel, delete Voltage settings before flashing
Follow shaolin95's Mini Overclocking Guide
Check out shane87's Voltage Control EX designed for Onix!!
Kernel Features:
Compiled using codesourcery 2010.09: Faster and more battery efficient
Works on all stock Froyo 2.2 and 2.2.1 ROMs and popular custom ROMs
Built from i9000 JPX 2.2.1 sources
Supercurios Voodoo Sound v7
Hardcores Brightness Fix (disable via CWM)
Gamma 2.2 and Improved sharpness: turned on AMOLED mode in MDNIE
Selectable Color Profiles in CWM (neutral, cold, warm)
Includes Neldar's Backlight Notification
340MB RAM (720p WORKING)
Kernel HZ=128
Simple IO Scheduler
Sched_Autogroup Patch
Properly working TinyRCU Patch
Patched lowmemorykiller
Disabled printk for improved performance and battery life
Android_Logger (Logcat) disabled - Enable via CWM
OC/UV support up to 1600mhz
hpcall supprt (Calls routed via headphones when available)
Captivate Audio Dock Support
Versions:
Onix-2.x.x-OC.tar = Odin flashable,OC/UV,Kernel HZ=128
Onix-2.x.x-OC.zip =CWM flashable,OC/UV,Kernel HZ=128
Onix-2.x.x-OC-1000hz.zip = CWM flashable,OC/UV,Kernel HZ=1000
Onix-2.0.5-OC.tar md5: 83d18d765cf7ae2f938bd4ba813f95ed
Onix-2.0.5-OC.zip md5: 450555c45e6d48e3d194ec43cad06713
Onix-2.0.5-OC-1000hz.zip md5: 29b5908a445870a7d221ba4907fd36dd
Onix-2.0.4-OC.tar md5: 67ddb217364033ae36641cfec946f73c
Onix-2.0.4-OC.zip md5: 7ec4492f0b256c81454d9a91d3ddbe81
Onix-2.0.4-OC-1000hz.zip md5: 3c39bbb14949711617937d9a852059fd
Onix-2.0.3-OC.tar md5: bc908bdc7407e6aa784c5c2bf6cf1f54
Onix-2.0.3-OC.zip md5: 6c4aa1ad6d8ddab6b34dae1cfea3f2a3
Onix-2.0.3-OC-1000hz.zip md5: 265d37fc402271fef13a800779e88ec5
Onix-2.0.2-OC.tar md5: 853e13ef9b1310b0992a0e47b764c67b
Onix-2.0.2-OC.zip md5: 18d6d21c5eaa0f1dc632842b5140d9cd
Onix-2.0.2-OC-1000hz.zip md5: 487b28152556148a27cf37488b89de7c
Onix-2.0.1-OC.tar md5: 214b229930c79972a41df09435e0a0b1
Onix-2.0.1-OC.zip md5: bb1ef03753f86ed3e89ca4004506eed6
Onix-2.0.1-OC-1000hz.zip md5: aef052e58ff9405cbdf5243eae85979f
Onix v2.0.5
-compiled with O2 + laststufo optimized CFLAGS
-randomize the location of the heap (brk) (security)
-add address randomization to mmap() (security)
-random ISN (28 bits hash instead of 24) (security)
-add fstack-protector support (security)
-more sched/mm tweaks and removed more debug
-revert PMEM_ADSP/MEMSIZE_BCM memory configs
-adjust read-ahead max to 512kb - min to 32kb
-limit read-ahead size for small memory systems
-add read-ahead tweak to recovery (1024)
Onix v2.0.4
-O3 compiler optimizations except sound soc codecs
-optimized CFLAGS inspired by laststufo
-set read_ahead to 2048kb (sdcard fix)
-few sched and mm fixes/tweaks
-optimize cache flush
-changed 100hz version-set CONFIG_HZ to 128; USER_HZ to 150
-removed useless patch to lowmemkill
-remove DEVMEM/DEVKMEM and set MMAP_MIN_ADDR=32768 (security)
-removed some kernel debug info
-disabled 900mhz by default
Onix v2.0.3
-update Voodoo Sound v7
-lowmemkill: only check cache for thresholds
-lowmemkill: don't try to kill the same pid over and over
Onix v2.0.2
-Add new boot image
-Add audio car/home dock support
--Audio uses dock when available - use this app
--Call audio uses dock when available
Onix v2.0.1
- Add OC up to 1.6ghz
- Update Voodoo Sound v6
- Attempt to fix WiFi error message when turning WiFi on sometimes
- Kernel modules updated from ZSJPJ kernel
- Ported fix from ZSJPJ kernel for downloading apps >30MB from Market
- Default lowmemorykiller minfree changed to 36MB
- New 'Onix' Recovery
---CPU Performance Threshold Tweak and Optimize Memory Timings (Onix Features/TWEAKS)
---Option to delete Voltage Control Settings (Advanced Features)
- Removed module and all references to Si4709 driver in ramdisk (FM Radio)
To check frequency time used, use Storm717's app HERE
Memory configs:
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=2048
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=4096
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500
CONFIG_WLAN_SAMSUNG_MEMSIZE_BCM=256
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=12288
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=32768
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=32768
CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=10240
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMD=3072
Thanks to Hardcore, Xcal, Supercurio, Raspdeep, sztupy, DG, Laststufo, Morfic, Trasig, and eSPyel
NOTE
When flashing a new kernel/rom your battery indicator may be off.
This means that you can have zero battery drain or a huge battery drain at the beginning.
Let the phone go through 3-5 complete charge cycles for the battery to recalibrate itself.
Onix v2 FAQ
Since a few things have changed with Onix v2.0.x and Onix recovery, heres a little bit of information on some of the new tweaks with Onix v2..
How to remove Voltage Control settings from Onix Recovery
Since its easy to save unstable oc/uv boot settings, you can now delete them in recovery.. Goto Advanced Features / Wipe Voltage Settings ...easy as that!
A few new 'tweaks' in Onix recovery
1) CPU Performance Threshold tweak [Onix Speed Tweaks/Tweaks] - The CPU Threshold defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether or not it should increase the frequency. For example when the up threshold is set to its default value of '90' it means that between the checking intervals the CPU needs to be on average more than 90% in use to then decide that the CPU frequency needs to be increased, meaning it wont scale high so quickly..For the down threshold, when set to its default value of '55' it means that if the CPU usage needs to be below 55% between samples to have the frequency decreased..meaning it will scale lower quicker.. When enabling the tweak, it sets the up threshold to 70 and the down to 30, so it would only need to be at 70% for it to increase (instead of 90), meaning it will scale higher quicker and for it to decrease it needs to be below 30% before decreasing (instead of 55), meaning it wont scale down as quick..
Use the tweak if you want max performance, leave the tweak disabled if you want best battery life
2) Optimized Memory Timings [Onix Speed Tweaks/Tweaks] - enabling this tweak will set more optimized ram timings,
giving optimal ram performance based on Samsung data sheets..There is NO need to use the S_mem_timings.sh file anymore, you can delete it.. originally took from laststufo
What happened to 'MISC BATTERY TWEAKS'?
The tweaks are actually still there, I just moved them to under Kernel VM Management.. since the tweak actually writes to /proc/sys/vm/dirty_writeback_centisecs and /proc/sys/vm/dirty_expire_centisecs , its actually a VM tweak.. I moved it to save some room for upcoming new tweaks.
As of right now the Onix Recovery is in a fairly early stage, more tweaks will be added soon..
Whats the difference between 100hz and 1000hz?
HZ is an internal timer value used by the Android/Linux kernel. It affects the timer granularity of some kernel functions. With Kernel HZ=100, the Kernel HZUser HZ conversion is eliminated, giving better battery life while giving about the same performance (compared to stock)..With Kernel HZ=1000, it should give smoother results.
Which lagfix should I use?
I personally recommend using ext4 on all partitions (system,data,dbdata,cache).. I personally think ext4 is faster over rfs and is overall a better file system. There is NO difference in battery life when using ext4
More info coming soon...still adding/removing things and will update as I go
Onix Kernel now!! No longer SuckerPunch.
Hmmm, I'll have to give this a try on s-dipity5.0 whenever it's released.
Interesting, will give this a spin tomorrow
damn, just did a fresh rom install with xcals newest. just got finished with restoring and now i see this. very intrigued. DLing now.
Interesting. Hoping the UV doesn't make my phone unstable.
Just loaded, like the boot screen. Running Serendipity 4.3 with KP1 modem, know its early but runs smooth. Let you know if I see any issues. Thanks
Just flashed.
D.A.M.N.
Runs very smooth. And has all of SpeedMod's features.
New default kernel (provided it remains smooth and endures my testing)
Great work! Incredible!
Regards
Smith
EDIT: For those looking for a quick review without having to read through posts!
I'm running #24 right now, OC'd to 1200MHz UV to 1200MV. Runs incredibly smooth, I love it. Battery life is incredible. Better than any other kernel/rom combo (running serendipity 4.3 btw)
Maxfactor said:
Just loaded, like the boot screen. Running Serendipity 4.3 with KP1 modem, know its early but runs smooth. Let you know if I see any issues. Thanks
Click to expand...
Click to collapse
Thats my rom/kernel/modem setup as well. You will enjoy!! Don't forget to enable the recommended tweaks in recovery and apply ext4 lagfix (if it isn't already) and don't forget to set those undervolt settings for maximum battery and performance!!
Been testing this, its rock solid.
I actually really cant wait for a 1200-1280 version of this kernel. You know you wanna make it
If we already have speedmod tweaks enabled, can we just flash it? or is it recommended to remove them first?
No just flash.
doreyu said:
If we already have speedmod tweaks enabled, can we just flash it? or is it recommended to remove them first?
Click to expand...
Click to collapse
You can leave them enabled
This looks great, waiting for the dalvik cache to rebuild then I'll start messing with it!
I'm trying this now. Let's see how's the battery life on this.
This one goes to 1.1...2.
Sent from my GT-I9000 using XDA App
Going to give this a go
Sent from my Captivate running FireFly 2.0.5
IBshaolin95's1400mhzrequest. btw
RuizGT said:
IBshaolin95's1400mhzrequest. btw
Click to expand...
Click to collapse
LOL @ 1400 mhz, lets look forward to the 1200 mhz that MAY be coming!!
This kernel is based on teamhacksung's kernel for Jellybean
This kernel is meant be working on every Rom based on cm10
Many Thanks to:
Teamhacksung
Zacharias.maladroit
Onecosmic
ytt3r
TK Glitch
Ezekeel
Eugene373
franciscofranco
Sunra
scheichuwe
perka
sztupy, for his great work, to get usb host mode driver
mialwe
stratosk
F4k for the idea to flash bigmem libs
...
sources:
https://github.com/DerTeufel
Click to expand...
Click to collapse
Working on this kernel is taking many hours almost every day. With a small donation, you show me, that my work is appreciated by you.
If you like this kernel, please donate to me
Download link and changelog can be found here:
http://www.hellybean.com/jelly.html
Click to expand...
Click to collapse
Kernels with VC in the name are coming with Voodoo Color
Changelog:
changelog 02.08.2012:
- bug fix to bln, to prevent kernel panic in some situations (thx to thalamus)
- switched from deep_idle 2 to idle2 (also thx to thalamus)
- updated kernel to linux 3.0.38
- dockaudio sysfs for captivate and fascinate
IDLE2 can be enabled with the following command:
echo 0 > /sys/module/cpuidle/parameters/idle2_disabled
IDLE2 can be disabled with the following command:
echo 1 > /sys/module/cpuidle/parameters/idle2_disabled
Stats can be obtained from the standard cpuidle interface, which, for
IDLE2 is located at:
/sys/devices/system/cpu/cpu0/cpuidle/state*/time
where * = 1, 2, 3
Click to expand...
Click to collapse
changelog 27.07.2012:
- hack mfc driver, to give all available mem to an application, if the requested mem is more than the max. available (maybe useful later, does not change anything right now (afaik))
- fix execution of boot-patch.sh, disabled twice execution of init.d, enabled tv-out server for all devices (i9000 already had this)
- battery: fix charging display for car dock
- increase read-ahead on moviNAND
changelog 25.07.2012 part2:
- fixed cwm backup and restore for kernels without /datadata partition
changelog 25.07.2012:
- updated recovery (no "sdcard format"-bug anymore, external sd card is named correctly)
- vibrant: hopefully fixed froyo ril
- jellybean: galaxy s settings working now
changelog 22.07.2012:
- updated kernal base to linux 3.0.36
- updated "block" to linux 3.3
- readded fiops io scheduler (kept cfq this time)
- updated cwm recovery to 6.0.1.0 (please create a new nandroid, because of possible incompatibilities between old/new recovery)
- compiled with linaro toolchain (gcc 4.7.1) and O3 compiler flags
- made uksm scan less often (save cpu time and power)
- at first boot: only delte init.d scripts created by other kernels
- increased usb write performance
- lowered ram and display voltages a little bit
- fixed some bugs related to devil settings (they should stick now after reboot, if set by one of the devil apps)
- support for scripts in /system/etc/shutdown.d (thx to Efpophis)
all scripts placed at /data/local/shutdown.d or /system/etc/shutdown.d get executed at shutdown/reboot
you can use this, to play a shutdown sound for example.
by default 00shutdown gets created, which plays a music file, when it is placed at one of these folders/places
/system/media/audio/ui/shutdown.ogg
/data/media/audio/ui/shutdown.ogg
Click to expand...
Click to collapse
- disabled some debugging options
- audio (and for fascinate: camera fixes) by Efpophis+
- patch for improving batterie life by CML
- nfts read/write driver built in (for use with usb host mode)
- reverted refreshrate_mod and gpu_oc mod, as both weren't working
changelog 18.06.2012:
- some changes to load balancing
- added ultra ksm (metioned by zach thx for this my friend)
- readded fiops io scheduler (still experimental and could cause instablilities)
- using snappy compression for zram now (2 times faster, but only 2% less compression)
- added the possibility to change zram size (at /data/local/devil/zram_size, with valid values: 50, 75, 100 and 150 (all in mb))
- fixed the applying of user_min/max freq after reboot
- vibrant: fixed gps
- fascinate: fixed nandroid in cwm recovery
what is ksm? http://en.wikipedia.org/wiki/Kernel_SamePage_Merging_(KSM)
uksm is more optimized and also working for single core systems. using this should give much better ram usage, but at the cost of more cpu usage
############# most probably not working (yet)##############
i have added seperate gpu oc from jt1134's galaxy_tab (to switch between 200 and 250 mhz), but i did not get any improvements in antutu...further tests needed
echo 1 > /sys/kernel/pvr_oc/pvr_oc (for 250 mhz)
echo 0 > /sys/kernel/pvr_oc/pvr_oc (for 200 mhz), no reboot needed
and also have changend default screen refreshrate from 60 to 56, with the possibility to change it:
echo 1 > /sys/kernel/refreshrate/enable (60 hz)
echo 0 > /sys/kernel/refreshrate/enable (56 hz)
######################################################
changelog 10.06.2012:
cwm recovery:
- fixed mounting of external sd card to pc
kernel:
- picked two commits from linux 3.0.32 (avoid a possible memory leak, small fix to ext4 driver)
fascinate:
- fixed wrong mount points
changelog 09.06.2012:
- updated Zram and Zcache from linux 3.3
- updated android binder driver from linux 3.3
- fixed restoring of backups within TWRP recovery
- added virtual buttons to cwm recovery (Attention: they still don't work!)
- call vol hack from tk glitch (take a look at init.d folder and edit the script to make changes to call vol hack)
- bigmem values get applied at first boot after power on (if there is a value at /data/local/devil/bigmem, 1 for 391 mb and 2 for 403 mb (the last one breaks 720p)
- prevent phantom key presses (from tk glitch)
changelog 24.05.2012:
- Smooth_ui included to ondemand, conservative, smartass, lulzactive, lagfree and lazy governor (only one setting for activating/deactivating it in general)
- 3 cpu governor presets (smooth, normal, powersave) for ondemand, conservative, smartass, lulzactive, lagfree (only one setting for switching the mode in general)
- no need for activating/deactivating of selective live_oc anymore --> just change target low and target high
- BLX back in
- fixes to devil idle to be more stable while in call
- 1,5 mb more ram (thanks to mialwe)
- added aroma filemanager to cwm recovery
- added fully working TWRP recovery optional to cwm recovery (to use TWRP, just create a file named "twrp" at /cache)
- added option to select ram config in kernel --> no need for flashing an other kernel to get more ram (thanks to stratosk)
- switched to new initramfs from stratosk and mialwe ( now there will be cmw zip and odin tar file of every kernel version)
- added possibility to use Zram instead of Swap
- no need for flashing/using special scripts to make swap/zram working anymore
- added zcache
- added frontpage
- added cleancache
- added fudgeswap (thanks to ezterry and faux123)
changelog 01.05.2012:
- all changes from cm9 stock kernel (including mount points option)
- some fine tuning to deadline and sio
- Devil Idle: limiting bus/ram/gpu speed to 100 mhz for 100-800 mhz cpu freq, while screen off (automatic mode) or always (permanet), both modes automatically reduce the int voltages of the affected freq by 50 mV
- compiled with swap support
- added stratosk's smooth_ui to lulzactive governor (activated by default)
- rest oc_value to 100 while screen off, and back when screen turns on (combined with devil idle automatic, can't be turn on/off without devil idle)
- added posibility for different voltages while screen off (also bundled with devil_idle, with default settings, stock arm voltages are applied, because of live_oc set to 100)
- added the possibility to set freq limits while screen off (min and max freq)
19.04.2012
- even better fix to selective live_oc (last one (in test kernel) generated some overhead)
- fixed sampling rate of ondemand and conservative (have ported mialwe's/stratosk's sleep multipliers)
- new tunables for ondemand and conservativ
sleep multiplier and tunables:
mialwe and stratosk had the great idea, to change the sampling rate of conservative and ondemand governor while display of. for this, he introduced the sleepmultiplier (in his case factor 3). this means, if you set sampling rate to 20000, it changes to 60000 while screen off, and back, when screen on.
for ondemand and conservative:
i have made this multipliers tunable. proper values are between 1 and 5, because one could want a higher multiplier while screen off, if sampling rate is very low while screen on (higher sampling rate means, less checking for work load --> better batterie, worse performance). with this tunables you get better batterie, without making the performance worse while screen on.
two other tunables: up_threshold_min_freq and responsiveness_freq
the first one is a very low threshold while on low freq (by default 40), to make the governor scale up faster, until the responsiveness_freq is reached.
the responsiveness_freq is set to 400000 (400 mhz) by default. while the freq is below this value, up_threshold is the same as up_threshold_min_freq, and freq jumps to responsiveness_freq, with skipping the freq between the actual one and the responsiveness_freq. (conservative governor does not jump up to this step)
responsiveness_freq can be set to values between 100000 and 1400000
up_threshold_min_freq can be set to the same values as the normal up_threshold.
not tunable: while screen off, up_threshold is set to 95, no matter your other settings, to save more batterie.
up_threshold_min_freq is disbaled by default for conservative governor
for lulzactive:
for this governor, i did similar things, but they are not tunable till now.
when screen off:
- inc_cpu_load is set to 90, and back to the original value, when screen turns on
- up_sample_time is set to 50000, and back to the original value, when screen turns on
- down_sample_time is set to 40000, and back to the original value, when screen turns on
other changes:
- fix to touchwake from ezekeel, and another fix from stratosk
- upstream fix to compass
- building for i9000B now, too (big thanks to F4k for the hints by pn )
- removed some typos from recovery
- removed some annoying "no's" and "yes" from recovery in misc menu
- fixed wifi mode switch (pm_fast is the one with better signal)
14.04.2012:
- new b versions (only stock ram) changend to 377 mb, VC version needs the 720p fix from my ftp server. cmc version already patched
13.04.2012:
- updated wifi driver
- added the possibility to switch between wifi PM_Fast and PM_Max mode (Pm_Fast = better signal, PM_Max = better batterie, default is PM_Max)
- user interface to disable fsync (this gives more performace, at the risk of data loss on a crash, taken from ezekeel, so it should be ok ), default is off, to be safe
- fixed voodoo color kernels (these have the VC in their names)
10.04.2012:
- added vibrator intensity control (by mialwe), presets can be changend in recovery
- stock ram version now available (348 mb ram), XL (390 mb), XL_bm (402 mb)
- removed 1080 mhz freq for now
- small correction to touchwake
- small correction to selective live_oc (now the low freq really are not live_oc'ed)
05.04.2012:
- fixed bug in selective live_oc, which caused the target high not taking affect to the highest freq, if highest freq equals target high
- fixed another bug in selective live_oc, which could lead to gpu crashes due to overclocking the ram, but not the cpu freq (for low steps)
- added a switch to change between "normal" and selective live_oc
by changing the live_oc mode while using it, live_oc value is set back to 100, to prevent strange things
- added possibility to set max. freq for boot (in recovery). This freq is set until init.d is executeted (it is automatically set to 1000 at this point, to make sure there are no conflicts with other cpu settings from users)
#Already in the last version, but i forgot about it:
- deep idle fixes from stratosk (many thanks)
- added possibility to underclock by using live_oc (limit is 90 now, which means lowering all freq and bus speed by 10%, to save more batterie when really needed)
03.04.2012:
For now there are three different RAM versions:
- stock mem kernel has 379 mb ram, everything working
- "slim ics" (XL) kernel comes with 390 mb, this is breaking playback of some high resolution videos
- XL_BM is coming with 402 mb ram, but breaking 720p
(while flashing the kernel, the modded rom files are also flashed, so you don't need to flash a new rom to get 379 or 390 mb)
-added new frequency: 1080 mhz (1100 does not like live_oc)
- fixed SmartassV2 for live_oc (after changing live_oc value, you have to change the smartass values, too, but then they automatically apply to the live_oc value (although you can only select 800 mhz in nstools (for example))
- touch recovery with custom devil menu (for some reason it takes a few seconds to load the first time, missing virtual keys is a warning, because there are no virtual keys yet)
-fast charge (thx to chad0989 for this), disabled by default.
you also can use the widget from chad (to place on homescreen) to toggle the fast_charge mode
https://play.google.com/store/apps/d...stchargewidget
Click to expand...
Click to collapse
while fast charge is activated you cannot connect as usb device
- added datafix script to init.d (this script is deactivated by deafult. to make it work, you have to creat a file named datafix and placed in /data/local/)
- reworking and cleaning many parts to get more ram, speed, and stability
05.03.2012:
- updated sio i/o scheduler to latest version
- small updates to ondemand and conservative governor from linux 3.2
- bettter performance for CFS kernel due to tuning and patches
- tuning to deadline scheduler
- better i/o performance
- changed bootlogo (probably not the last time )
28.02.2012
- finally working bln V9 (no need for LED2 anymore)
- fixed lockscreen freezes
- reverted memory tweaks, which could be the reason for lagging after using a day
- again wlan fixes from tk-glitch
- tweaked conservative and ondemand governor (conservative still is not too aggressive)
- added dm-cache again (who has removed this from my github? )
- improve usb signal quality
- xcaliburinhand's dock audio support (untested, do not have a dock)
- less debugging
- fixed kernel version not displayed under "about phone"
12.02.2012
- Added newest Fiops scheduler (tuned for more performance)
- When Gpu is active, min CPU freq is set to second lowest step
- fixes to live_oc and custom voltage
- default mount parameter NOATIME and NODIRATIME (faster)
- updated Wifi drivers (thanks to tk-glitch)
- tuned intellidemand for better performance
- removed some stuff (zram, swap, tweaks to cpufreq untill I know what was causing the instabilities of last build)
05.02.2012
- added Touchwake
- added BLX
- upgraded BLN from V8 to V9 (working for missed calls, blinking or static light, configurabel by using NSTools or BLN Pro App)
- added Intellidemand governor
- added mdnie settings to voodoo color version
- readded deep idle v2 again (I think it is the best/only working one, although
- version with CFS (instead of BFS) now also available (maybe better multitasking and batterie life, but slower)
- removed BFQ I/O Scheduler
- tons of smaller fixes and improvements
30.01.2012
-revert: Voodoo Sound now to be set with DSP Manager
29.01.2012
- Linux kernel 3.1.10
- Deep Idle from Eugene373 (always enabled, no stats)
- added BFQ v 3.1 I/O Scheduler
- Voodoo Sound now to be set with DSP Manager
- Zram (can be disabled by removing Zram file from init.d)
- Zcache and Cleancache (not working yet?)
- optimized rwsem algorithm
- USB Host V5
24.01.2012
- init.d support (the folder is not created by the kernel. You have to do it for yourself)
- Deep Idle V2 back in
- new Cpu governors: MinMax, Lagfree, Lulzactiv
- LED V2 (you can set blinking by using nstools, also working for missed calls in most cases (sometimes it is not working for missed calls, don't know why at the moment))
- Backlight Dimmer (only LED version): used to turn led backlight of, while screen is on, after defined period of time. Deactivating it, makes your backlight stay on all the time
- I/O-less dirty throttling completely backported from kernel 3.2
- Ext4 with 3.2 patches
- Proportional Rate Reduction for TCP - by Google
- USB Host V 4
19.01.2012
- Usb Host drivers integrated
- Cm9 Color adjustment
- Removed Deep Idle because of Bluetooth problems (hopefully it will come back, still testing)
16.01.2012:
- Updated Kernel basis to Linux 3.1.9
15.01.2012:
- fixed bug in cpu spy, caused by live_oc
- still using voodoo color for now, maybe two additional kernel versions tomorrow
[/quote]
files with .zip have to be flashed within recovery (twrp or cwm)
files with .tar can be flashed by using odin or heimdall (they are placed at the end of post 3)
Downloads:
http://rootaxbox.no-ip.org/divers/jellybean/ many thanks to Rootax
http://devil.haxer.org/ many thanks to SysTem-X (not updatet yet)
just in case ...
First
Sent from my Cappy powered with Jelly Bean using Tapatalk 2
Continuing my discussion from ICS thread here. Either I effed up enabling Idle2 or running a internal Cat of kmsg is not letting my phone drop to idle . Can Idle 2 be enabled from the app or that needs to be implemented?
Edit: Got everything to work. Here is the KMSG that I got. The problem is, if I use ADB the phone doesn't activate Idle2 but i feel like making my phone cat kmsg while I'm trying to crash it might not get the whole txt? I could be wrong. Hope it provides more info.
Idle2kmsg.txt
Wait so what's the difference between deep_idle 2 and idle2? Anyways I'm going to flash it and see what's the difference!
Sent from my SGH-I897 using xda app-developers app
@DerTeufel
Apparently I don't get SoD with idle2, my phone locks up. Screen Actually showed lockscreen this time when I attempted to wake it up while playing music. Sadly my computer doesn't see the device during this state. Any advice? Did you take a look at the kmsg I provided in my earlier post?
Thanks for your contribution .
Can't get to recovery?
Hello all, first time in Devil kernel.
First flash went well, I flashed and tested it was working by rebooting back into recovery. I set a few options (such as vibrate intensity) and rebooted, everything was OK (even better even, because Waze started working finally).
I did a 'touch /data/twrp' to try to enable the TWRP recovery, and rebooted, but now I'm kinda stuck at the kernel logo. Capacitive buttons do light up (but don't vibrate the phone), and I can reboot by holding all three hard buttons for ten seconds.
I noticed in the changelog that "for some reason" it takes a few seconds to start TWRP, but I waited for ten minutes (and dropped by battery 43%) before giving up. Coincidentally, now I'm getting the "android.process.media" has stopped error, waiting to see if a appdata wipe will help on that one...
Thing is, even after deleting the file I touched, it's still not letting me into Recovery (the normal CWM). Are there any hints at this? Or should I look at trying to get Heimdall working to try reflashing the kernel?
Tsaukpaetra said:
Hello all, first time in Devil kernel.
First flash went well, I flashed and tested it was working by rebooting back into recovery. I set a few options (such as vibrate intensity) and rebooted, everything was OK (even better even, because Waze started working finally).
I did a 'touch /data/twrp' to try to enable the TWRP recovery, and rebooted, but now I'm kinda stuck at the kernel logo. Capacitive buttons do light up (but don't vibrate the phone), and I can reboot by holding all three hard buttons for ten seconds.
I noticed in the changelog that "for some reason" it takes a few seconds to start TWRP, but I waited for ten minutes (and dropped by battery 43%) before giving up. Coincidentally, now I'm getting the "android.process.media" has stopped error, waiting to see if a appdata wipe will help on that one...
Thing is, even after deleting the file I touched, it's still not letting me into Recovery (the normal CWM). Are there any hints at this? Or should I look at trying to get Heimdall working to try reflashing the kernel?
Click to expand...
Click to collapse
yes, i think best would be to reflash the kernel, and then try to get to recovery.
DerTeufel1980 said:
yes, i think best would be to reflash the kernel, and then try to get to recovery.
Click to expand...
Click to collapse
Yeah, on the thoughts that it might have been a bad flash, I did try that. Now I've downloaded the 8/1 version for testing, we'll see what results. TWRP should be rom-independent, right?
I just don't know what else I might be doing wrong. Perhaps it's reading the TWRP information from a previous version and hanging up? Oh well, I supposed it can wait.
I renamed the TWRP file from a previous kernel's version and tried to reflash, but still no go...
Tsaukpaetra said:
Yeah, on the thoughts that it might have been a bad flash, I did try that. Now I've downloaded the 8/1 version for testing, we'll see what results. TWRP should be rom-independent, right?
I just don't know what else I might be doing wrong. Perhaps it's reading the TWRP information from a previous version and hanging up? Oh well, I supposed it can wait.
I renamed the TWRP file from a previous kernel's version and tried to reflash, but still no go...
Click to expand...
Click to collapse
i think twrp is not working at the moment with jellybean. i try to fix this tomorrow.
till then, you have to go to cache and delte the twrp file from there. if this file isn't present, then please attch your /boot.txt
DerTeufel1980 said:
i think twrp is not working at the moment with jellybean. i try to fix this tomorrow.
till then, you have to go to cache and delte the twrp file from there. if this file isn't present, then please attch your /boot.txt
Click to expand...
Click to collapse
Ok. Somehow the Devil Kernel Config app wasn't properly deleting the file, once I used an actual command to delete it, it worked OK to be in CWM recovery.
Just for kicks, I attached my /boot.txt log.
Tsaukpaetra said:
Ok. Somehow the Devil Kernel Config app wasn't properly deleting the file, once I used an actual command to delete it, it worked OK to be in CWM recovery.
Just for kicks, I attached my /boot.txt log.
Click to expand...
Click to collapse
Boot.txt is fine now
Gesendet von meinem GT-I9000 mit Tapatalk 2
Just for clarification, doesn't the boot.txt file get overwritten each boot? So if I'm having issues getting into TWRP, and I reboot to get out of recovery mode, the boot.txt file will only give information about the current boot (not the broken TWRP)?
Tsaukpaetra said:
Just for clarification, doesn't the boot.txt file get overwritten each boot? So if I'm having issues getting into TWRP, and I reboot to get out of recovery mode, the boot.txt file will only give information about the current boot (not the broken TWRP)?
Click to expand...
Click to collapse
Yes. That's right. It would have been helpful, if you grep it with adb, while stuck. I already did this now, and it wasn't helpful
Gesendet von meinem GT-I9000 mit Tapatalk 2
DerTeufel1980 said:
Yes. That's right. It would have been helpful, if you grep it with adb, while stuck. I already did this now, and it wasn't helpful
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
One thing that always frustrated me was the fact that there is literally no way to watch the kernel messages on the display as it boots. That's one of my most trusted debug methods on the computer: Have it show what it's doing on the console.
Of course, there is a serial port somewhere, but it's apparently not easily accessible without special hardware...
Something just occurred to me: What if we could manually load the TWRP ramdisk and chroot into it? Would that allow us to interactively watch it? or (since stuff is already loaded and junk) that may not be possible? I noticed that adb starts, but we can't get a shell, so...
There is 1.1.3 kernel uploaded.
http://rootaxbox.no-ip.org/derteufel/jellybean/Cappy/113/
Sent from my SGH-I897 using xda premium
Search Button not working. Press it, not working, no response.. Have to go to the search app instead.
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Please click one of the Quick Reply icons in the posts above to activate Quick Reply.
---------- Post added at 05:40 PM ---------- Previous post was at 05:39 PM ----------
Please click one of the Quick Reply icons in the posts above to activate Quick Reply.
The search button no longer invokes the normal search function in an app, instead it launched Google Now in Jelly Bean. If that feature is missing in your ROM, nothing will happen when you press it, you must press-and-hold instead.
Current release: Version 2.0 (stable) [09/08/2012]
SOURCE CODE: Available at GitHub
*WARNING PLEASE USE AT YOUR OWN RISK*
DISCLAIMER
FIRST OF ALL THIS IS NOT AN OFFICIAL KERNEL, IT IS NOT SUPPORTED BY OFFICIAL CM10 ROMS OR ANY PREVIEW ROMS.
ONCE YOU INSTALL THIS KERNEL YOU WILL NOT BE SUPPORTED IN THE CM10 / CM9 OFFICIAL/UNOFFICIAL DEVELOPMENT THREADS
OF ANY FORUM i.e XDA, SLATEDROID, etc.. THIS MEANS THAT YOU MUST NOT REPORT ANY ANDROID / CM BUGS TO THE ORIGINAL
COMMUNTIY THREADS FOR THE ROM YOU USE! YOU MAY HOWEVER REPORT ANY CM/ANDROID/KERNEL RELATED ISSUES TO THIS THREAD ONLY!
Click to expand...
Click to collapse
Features
CPU Overclocking up to 1500mHz (default is set at stock 1000mhz)
Stable GPU Overclock @ 450mhz (scales from 300 - 450)
Userspace CPU undervolting support
Brick prevention/precaution - disabled MMC_CAP_ERASE function from kernel
I/O Schedulers: BFQ, CFQ, SIO, DEADLINE, NOOP, V(R) (Default VR as of v1.3 - prior to 1.2 default = deadline)
Autogroup Scheduler patched to work with Android via User ID task grouping
CPU Governors: Lionheart, SavagedZen, Lazy, Scary, Intellidemand, LagFree, Wheatley, Lulzactive, SmartAssv2, Interactive, Ondemand, Powersave, Userspace, Performance (depending on ROM - interactive governor is usually set as default gov from userspace during init)
ARM libs from Linux 3.x (v2.0+)
Android Drivers from Linux 3.x (v2.0+)
Linux Security from Linux 3.x (v2.0+)
Cleancache + Zcache Support (v2.0+)
Working Zram - to enable see instructions below (v2.0+)
Fixed Video driver glitches (v1.4+)
Cleaned up tons dmesg errors and warnings (v2.0+)
Memory management fixes and patches from 3.x (v2.0+)
Alsa SoC Tiny HAL patch for better compatibility with Jelly Bean and ICS (reduces/eliminates popping sounds)
Plus various other improvements to kernel configuration and code.
Downloads
Current Release:
v2.0
Previous Releases:
v1.6
RC3
RC2
RC1
Tools:
Code:
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/toggle-ag.sh"]toggle-ag[/URL] Tool to Enable/Disable Autogroup and check the status.
'toggle-ag' now included with kernel zip as of 1.3a and is located at /system/xbin/toggle-ag - You may run from a terminal or create Script Manager widgets for each of the script arguments:
Code:
toggle-ag status
toggle-ag on
toggle-ag off
toggle-ag help
Please remember that this script has to be ran as root if you plan to enable/disable autogroup, however you may run as regular user to check the status or get the help dialog.
Important info on toggle-ag script usage (from the script comments):
#**Please note that toggling back and forth the scheduler will
#produce undesired effects, as it takes the system a few minutes
#to switch the process scheduler each time effectively. Imagine
#all processes that run in the backround are rearranged each time
#you switch the process scheduler. In other words you shouldn't
#toggle back and forth to make comparisons as they WILL NOT be
#effective immediately!!
Click to expand...
Click to collapse
Goo Manager Support (NEW!)
You can now download my custom kernels, tweaks, etc from Goo Manager, available on the Play Store. Goo Manager is similar to ROM Manager, except it works very well with TWRP 2.x
First time use instructions:
Set Download path to: /sdcard/goomanager/ in "Settings" (This is important as the location on Android and TWRP need to both be exact same!)
Go back to the main screen in Goo Manager and click Browse Compatible Roms
Choose 'godmachine81'
For kernels choose a500_kernel (you are welcome to look around in my other directories)
Choose the release you wish to download
Choose 'begin download'
You will see a notification for 'Download Finished' - Tap on it
It will prompt you to Select Zip(s) to flash, you may choose more than 1!
After you have selected all the zips you want to flash, go to the option 'Order and flash selected' or if you want to add a zip from a custom location, choose the 'Add zip from another location option'
Once in the Order and flash menu, it is important that you set the order to flash in the proper order, when you are sure it is right, then click Flash (First time you use Goo Manager, it will prompt you that an OpenRecovery is needed, choose that you already have one)
After You click flash, the system will reboot to TWRP, flash your .zip files, and reboot back to android without any user interaction.
ZRAM
What is it?
Zram was developed so that systems with a limited amount of physical ram may allocate a percentage of that to a system swap device using compression. By compressing the data that is in the swap space you can fit more data into the same amount of ram. For example App#1 is consuming 500mb of a total 725mb ram, this leaves you with 225mb free. If you have Zram enabled then App#1 may begin to swap to the zram device, when doing this you will have an advantage, because any amount of data from App#1 that gets swapped out to Zram will be compressed meaning it is actually using less physical ram. So instead of only 225mb free of 725mb you may now end up with something more like 400mb free because data from App#1 is compressed in Zram, in this example thanks to compression you cut the 500mb memory usage of App#1 to 325mb. Zram should have a minimal impact on performance while giving you the benefit of fitting more data into the amount of physical ram your device has.
HOWTO
This kernel includes functional ZRAM support, however to take advantage of it you must enable it from userspace (Android). Cyanogen Mod has an option in Settings > Performance > Memory to enable Zram, however it doesn't properly work - I'm not sure exactly how it is coded in the cm sources, but when you enable zram it doesn't create the zram swap device like it should. To work around this I wrote the following flashable .zip files that contain a script to automatically create the zram swap device at boot, please download and flash the size you wish to allocate to zram:
Zram - 100MB (14% ram)
Zram - 150MB (20% ram)
Zram - 200MB (28% ram)
Zram - 250MB (34% ram)
Zram - 300MB (41% ram)
Zram - 350MB (~50% ram)
To Disable/Remove Zram
In the event that you want to disable Zram then just remove the file(s) at:
/system/etc/init.d/50zram-*
After the 50zram- file has been removed, just reboot your device and you will no longer have Zram enabled. To re-enable just reflash one of the above files.
ChangeLog:
2.0
Backport several bits mainline code from Linux 3.5 - including Security, ARM Libs, MM, and Android specifics
Zcache + Cleancache added
Ability to concatenate kernel cmdline configuration to Bootloader's cmdline without breaking compatibility with any bootloaders ( needed for zcache/cleancache to work)
Zram patches and updates
Clean up dmesg logs
Deadline IO Sched tweak (1:1 ratio writes/fifo) - VR remains default IOsched
CONFIG: turn off some verbose logging/debugging to reduce overhead, enabled Load Lens Correction Data to smooth out camera operation
TweakIO init script included by default to optimize disk read/write performance
Several other small patches and tweaks to underlying sources
1.6
Minor update adds support for USB-DVB devices, provided in two separate files for convenience to users who do not wish to use DVB-USB all that is needed is the kernel package, for users who wish to use DVB please flash both the USB-DVB and the Kernel pkgs. **Warning please only install the USB-DVB package if you have the matching kernel pkg installed. This may require you download firmware for your DVB device to work, also for the modules to load automatically you will need an init script that loads the needed modules for the device - reason I didn't do this is because there are 79 different modules for universal support, it would be crazy to load them all for everyone all the time, so if you want this feature please do some research on how to get the proper modules (and firmware if needed) to load properly automatically via init script. For help join #iconia-dev on irc.freenode.net and look for godmachine81.
1.5
Add support for USB devices [USB Audio, game controllers, mice, keyboards, etc]
Adjust GPU/CPU voltages and frequencies - should have impact on GPU performance
Interactive governor default again and backported from Nexus 7 / NVidia Grouper kernel v 3.1
1.3a
Script: toggle-ag now included in zip, installs to /system/xbin/toggle-ag
Default IO Scheduler V(R)
Default CPU Governor Lulzactive
1.2b
Bug Fix release for 1.2 - BFQ randomly causing "black screen" issue immediately after boot animation, preventing full boot - reboot resolved issue in most cases, but comes back at random on boot - Setting default I/O scheduler to NOOP until BFQ issue is resolved.
1.2
Autogroup per UID instead of TTY task (huge improvement to autogroup on android)
Set BFQ as default I/O Scheduler
Allocator: Switch to SLUB from SLAB
Remove verbose debugging symbols
Set proper firmware/calibration paths for WiFi in configuration
1.1
Add userspace support for undervolting
GPU OC (400mHZ) on CPU OC > 1000mHZ
Fix "Recent Apps" bug - The glitchy behavior when loading an app cached in the "Recent Apps" menu. Pointed out by DarkNight
Tune SmartassV2 for better behavior and ideal freq set at 760mHZ
Add the following CPU Governors: Lionheart, SavagedZen, Lazy, Scary, Intellidemand, LagFree, Wheatley
Deprecated the non-autogroup release also known as (default)
various other improvements to CPU, voltage, video.
1.0.1b
Add SmartAssv2 CPU Governor
Fix LOCALVERSION
1.0.1
Patched MMC_CAP_ERASE as precautionary to avoid hard brick
1.0-pre
V(R) I/O scheduler Added
SIO I/O scheduler Added
Zram sources backported from 3.0 resolved compile issue
Alpha (First public download)
Overclock added: Min Freq: 216 Max Freq: 1504
CPU Governors: Lulzactive, Ondemand, Interactive, Conservative, Userspace, Performance, Powersave
IO Schedulers: Noop, Deadline, CFQ, BFQ
Autogroup or Default Kernel available
Patch for Tiny HAL - resolves popping in audio on JB/ICS
Click to expand...
Click to collapse
To cut down on general discussion in this thread please note that I have been in the Freenode IRC Dev channel a lot lately. server: irc.freenode.net channel: #iconia-dev My IRC handle is godmachine81 Join me there for general discussion if you don't mind. Thanks!
If you would like to help out with the continuance of kernel development for your Acer Iconia Tab A500 please consider a small donation to help out with bills, baby formula, wipes, diapers, etc. All donations are very appreciated by my family and I! Thanks
Well,
I'm always looking to flash things. I suppose it doesn't include 3g and GPS for the 501?
Should be a simple merge to use ICS 501 source from Acer.
However, I'll throw in a flash just to check install. Will report back later. Supermarket trip first.
MD
EDIT: I am to assume this is for ICS. Also, I noticed in your install script, there is no provision to delete current module files. I would suspect this would cause an issue if you already have an OC/UV kernel with modified ko files?
Probably is best to modify the IS to delete current lib/module files, and replace them with the required ones.
Hi,
I flashed the kernel over cm10 preview with TWPR and it boots up fine.
I found one bug yet:
when selecting lagfree governor the tablet freezes and reboots.
Moscow Desire said:
Well,
I'm always looking to flash things. I suppose it doesn't include 3g and GPS for the 501?
Should be a simple merge to use ICS 501 source from Acer.
However, I'll throw in a flash just to check install. Will report back later. Supermarket trip first.
MD
Click to expand...
Click to collapse
PSensor3G the appropriate driver for what you are wanting? It isn't a default in the A500 config, but I can definitely recompile it with it turned on.
**Edit - I had already merged in the A501 code drop, so if those things are not working it should be as simple as altering the config. I build simdetect in static instead of a module - it was a new feature in the 501 code drop, if it has issues being built in statically please let me know, as far as gps goes, it is included and *should* work, however I have no way of testing these things first to make sure.
GPS should work, don't see why it wouldn't.
KennyWuLee said:
Hi,
I flashed the kernel over cm10 preview with TWPR and it boots up fine.
I found one bug yet:
when selecting lagfree governor the tablet freezes and reboots.
Click to expand...
Click to collapse
Interesting as that isn't happening with the A100. I'll check into it or maybe remove lagfree, it's kind of misleading anyway, because imho it produces more lag than any of the other governors..
linuxsociety said:
PSensor3G the appropriate driver for what you are wanting? It isn't a default in the A500 config, but I can definitely recompile it with it turned on.
**Edit - I had already merged in the A501 code drop, so if those things are not working it should be as simple as altering the config. I build simdetect in static instead of a module - it was a new feature in the 501 code drop, if it has issues being built in statically please let me know, as far as gps goes, it is included and *should* work, however I have no way of testing these things first to make sure.
GPS should work, don't see why it wouldn't.
Click to expand...
Click to collapse
Thanks Mate. Will check it out in a few hours. The issue with GPS, is 501 uses a different radio than the 500.
But I'll check it out as soon as I can. Thanks!
MD
Moscow Desire said:
Well,
I'm always looking to flash things. I suppose it doesn't include 3g and GPS for the 501?
Should be a simple merge to use ICS 501 source from Acer.
However, I'll throw in a flash just to check install. Will report back later. Supermarket trip first.
MD
EDIT: I am to assume this is for ICS. Also, I noticed in your install script, there is no provision to delete current module files. I would suspect this would cause an issue if you already have an OC/UV kernel with modified ko files?
Probably is best to modify the IS to delete current lib/module files, and replace them with the required ones.
Click to expand...
Click to collapse
The script will remove modules from system/lib/modules and replace them with 1 module which is the wifi module, everything else is built into this kernel, it WILL NOT cause an issue at all, when you reflash a different kernel it should overwrite the modules installed by mine. Aside from that nothing in the ramdisk will be touched. And this is for HC/ICS/JB, it should run on any of roms you have as this entire kernel is built static, except for the wifi module.
Moscow Desire said:
Thanks Mate. Will check it out in a few hours. The issue with GPS, is 501 uses a different radio than the 500.
But I'll check it out as soon as I can. Thanks!
MD
Click to expand...
Click to collapse
Recompiled with the Psensor3G support built in, you may download here and give it a test: https://github.com/downloads/godmac...ustom-Kernel/gm-a500-v1.5-alpha-3g-signed.zip
I would like to see extreme edition and yes lagfree makes it freeze, also smartassV2 made it freeze ones , I use SavagedZen and it is very smooth.
So cif and other are build in kernel.
civato said:
I would like to see extreme edition and yes lagfree makes it freeze, also smartassV2 made it freeze ones , I use SavagedZen and it is very smooth.
So cif and other are build in kernel.
Click to expand...
Click to collapse
Thanks for reporting, I will check into what the differences would be between how the A500 and A100 boards handle the cpufreq transistions between gov. Not sure why they are causing issues with A500 and not with A100/A200 since they are all tegra2 and the cpufreq drivers are all tuned for the same processor, that's a bit weird, but thanks for reporting they are having issues, I will take note of that with A500 and may remove them or may patch whatever is necessary causing the lockup on gov change. Thanks again
**edit: yes all the FS supports are built in - if you have need for them being modules due to problems being built in statically let me know and I can just rebuild them as .ko instead of static. - Not had issues with any of the SMB/CIFS connections with A100 and static CIFS. Also NTFS is built in for whoever might have a weird sd card that is formatted with ntfs instead of fat32, or if they need to mount NTFS partition in any other manor
**edit2: haven't built A500 Xtreme edition yet, A100/A200 are working with xtreme until 100% load is reached for a duration of around 2-3 minutes and then freq nose dives to 216-456 and never raises back, has to do with the voltages clocks in dvfs / tegra2_clocks It's on my todo list of things to fix, and if I get it fixed I'll compile for A500. Kinda doing the A500 work in the blind, but doing the best I can to not have the device present.
Gotta clear something, not smartass V2 made it freeze it is caused by switching from interacriveX to SavageZen.
civato said:
Gotta clear something, not smartass V2 made it freeze it is caused by switching from interacriveX to SavageZen.
Click to expand...
Click to collapse
Thanks, that makes more sense now, as I just added interactiveX into my sources today and I haven't fully tested it. That's why there isn't a new release to the A100/A200 guys yet and I have done a few more things also as tests. If interactiveX is an issue it can be removed, I can just build again out of a 1.3 / 1.4 tag and eliminate that issue. I will be testing on my a100 to try to reproduce the problem. appreciate the info
**Edit and yes I can reproduce that bug on my A100 - I greatly appreciate the info civato! It isn't just switching to smartassv2 from interactiveX it is when switching to any other governor from interactiveX - I will check the sources for how interactiveX is handling the handoff right now
**Here is what I have concluded on: interactiveX has a serious bug when switching to another governor, I have looked at the sources and tried to debug dmesg/logcat info while the switch occurs and can't come up with any relevant information needed to pin point what the exact cause is with interactiveX - I made a few modifications on how the governor gets disabled when switching to another governor - didn't help... Still happens. Good news is: The regular 'interactive' driver that we have is backported from the nv grouper 3.1 kernel and should be much better at powersave/performance ratio than the older 2.6.3x interactive governors we have been using. So what I am going to do for you guys is the same thing I'll do for the A100/A200 guys (which never had this problem because interactiveX was never released to their devices - A500 kernel got compiled before I have pushed anything upstream to github or made other flashables.) I am going to take out interactiveX completely, keep the backported interactive assuming that you guys aren't experiencing any issues with 'interactive', and we'll make the release 1.5. Hopefully that will clear up any bugs you may have with this alpha test and people can begin to use this as a daily driver on their tabs. I appreciate all the help you guys have given me with this alpha release, not only have you helped me to find a bug with the A500 but also with A200/A100 before I released the downloads of 1.5. Thanks guys!
ntfs usb stick is not recognized , if I switch back to ezterry's oc kernel it works again. Even adding ufsd.ko acer ntfs module doesn't work.
civato said:
ntfs usb stick is not recognized , if I switch back to ezterry's oc kernel it works again. Even adding ufsd.ko acer ntfs module doesn't work.
Click to expand...
Click to collapse
Of course that wouldn't work since the ntfs module is built in (would conflict). I will make it module and recompile, need to see what is in the user land that depends on ntfs being a module and not static.
Civato: see how this works please.. InteractiveX has been removed, and NTFS is a module. thanks
download: https://github.com/downloads/godmac...Custom-Kernel/gm-a500-v1.5-alpha-2-signed.zip
I did not add the ufsd.ko to the modules. If you could tell me if the mainline ntfs.ko is not working, could you get me dmesg output on the ufsd.ko when trying to load it. Thanks in advance!
linuxsociety said:
Civato: see how this works please.. InteractiveX has been removed, and NTFS is a module. thanks
download: https://github.com/downloads/godmac...Custom-Kernel/gm-a500-v1.5-alpha-2-signed.zip
I did not add the ufsd.ko to the modules. If you could tell me if the mainline ntfs.ko is not working, could you get me dmesg output on the ufsd.ko when trying to load it. Thanks in advance!
Click to expand...
Click to collapse
No , no luck , ntfs is not working , I did 2 tests . One without modding the ramdisk and one where I added the following line "insmod system/lib/modules/ntfs.ko" .
Did you try with the ufsd.ko module that comes with the acer A500 stock kernel?
If you download the kernel from my flexreaper thread , see my sig you can find it there.
civato said:
No , no luck , ntfs is not working , I did 2 tests . One without modding the ramdisk and one where I added the following line "insmod system/lib/modules/ntfs.ko" .
Did you try with the ufsd.ko module that comes with the acer A500 stock kernel?
Click to expand...
Click to collapse
if you have that handy can u stick it in /system/lib/modules and reboot to see if it loads, not sure why there is a problem as i have module support for other versions enabled.
Civato: not exactly sure why this would be any different if you have the same .ko file and have already placed it in system/lib/modules/ and rebooted, but here is a download that contains the ntfs.ko and ufsd.ko in the modules if you don't mind testing it:
https://github.com/downloads/godmac...Custom-Kernel/gm-a500-v1.5-alpha-3-signed.zip
Just an initial look see. 3g and GPS work for the 501.
A little sluggish on first boot for a minute, but settled down. Will take a couple days to do battery rundown, and to check on 3g screen freeze and SOD. These issues haunted the 501 when it came to UV kernels. It's a lot less tolerant to UV than the 500 due to the 3g.
MD
linuxsociety said:
Civato: not exactly sure why this would be any different if you have the same .ko file and have already placed it in system/lib/modules/ and rebooted, but here is a download that contains the ntfs.ko and ufsd.ko in the modules if you don't mind testing it:
https://github.com/downloads/godmac...Custom-Kernel/gm-a500-v1.5-alpha-3-signed.zip
Click to expand...
Click to collapse
sorry , still no go
Note that while you can download the most current kernel from the links below, this thread is no longer being updated. Go to Devs-base for the active user thread. Watch this for details.
Here's a custom kernel for you all to try out. It should work with the Evervolv nightlies. Not tested with other ROM's.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTICE: This kernel can be overclocked over the standard Touchpad voltage regulator settings. It may or may not be stable for your particular Touchpad. I am not responsible in any way for anything that occurs as a result of your use of this kernel. You agree that by flashing this kernel, you are doing so with a full understanding that you assume full liability for any and all issues that may arise from doing so.
Click to expand...
Click to collapse
This kernel must be flashed from recovery (DO NOT USE TP TOOLKIT!) No need to clear caches, format system, or any other preparation. Flash and boot. You can set the kernel parameters from the EVToolkit, but I highly recommend Kernel Adiutor for more detailed and granular control of settings. If you don't like it, recover by reflashing your base EV ROM.
Here's a few facts:
CPU Overclockable to 1890KHz
Level 2 frequency boost to 1890KHz
Stepped 2D & 3D GPU OC up to 267 MHz and 320 Mhz, respectively
Additional governors and schedulers
Use Kernel Adiutor for tuneable parameters in the kernel
READ HERE FOR INFORMATION ABOUT GOVERNORS AND SCHEDULERS: Guide Link
NOTE!: The kernel has stability up to 1836 KHz, so if you decide to try the higher frequencies or change the cpu voltages, be sure and UNSET THE 'APPLY AT BOOT' option in your kernel tuner app. If your tablet can't handle the higher frequencies or voltages, it will either freeze or reboot. If it freezes, you will have to do a hard boot (hold power and HOME key simultaneously until it reboots). It should revert back to the default frequency of 1512 KHz max, 384 KHz min., but if it doesn't, Kernel Adiutor (KA) has a delay in setting the options. Get into KA as soon as you can after it reboots and set the CPU options to a stable setting.
Download links. No system/full wipes or cache clearing required.
Primary
GPL Compliance: Kernel Source
CHANGELOG
Code:
-> 16JUN17
- Adapted from APQ8064: Improve GPU response when waking from sleep
-> 14JUN17
- Ported from board-8960: Increase MM ION heap to 60MB
- defconfig: Enable arm neon optimized crypto
-> 12JUN17
- Fix defconfig DERPs in merge
- tcp: add sociopath congestion control
- Hack __pm_wakeup_event to reduce wakelocks
-> 07JUN17
- Merge upstream
-> 05JUN17
- rwsem: Optimized ARM RWSEM algorithm
- net: Controlled Delay AQM (CODEL)
-> 30MAY17
- Merge upstream
- Reduce zramdisksize to 268MB
-> 25MAY17
- int_sqrt: 3x faster integer sqrt
-> 16MAY17
- Merge upstream
- defconfig: Enable QUICK_WAKEUP and FRANDOM
- lowmemorykiller: numerous patches to improve performance
including adaptive LMK
-> 10MAY17
- block: Add driver to change the I/O scheduler when the screen turns off
-> 03MAY17
- Add more processes to power efficient workqueue
- workqueue: Provide destroy_delayed_work_on_stack()
- workqueue: use schedule_timeout_interruptible() instead of open code
- Remove WQ_POWER_EFFICIENT from kblockd
- Add frandom and quickwakeup drivers
- cpufreq: Notify governors when cpus are hot-[un]plugged
- cpu: Abort suspend when hotplug is already in progress
-> 01MAY17
- Reduce boot splash size
-> 30APR17
- add several more processes to the power efficient workqueue
- SKZ-ify the boot splash
-> 25APR17
- sched: cpu_power: enable ARCH_POWER
- splice: introduce FMODE_SPLICE_READ and FMODE_SPLICE_WRITE
- binfmt_elf.c: use get_random_int() to fix entropy depleting
- CHROMIUM: mm: Fix calculation of dirtyable memory
- writeback: increase bdi_min_ratio to 5
- power: msm_battery: increase battery check interval from 5 to 15 seconds
- scsi: Remove scsi_wait_scan
- kernel: Reduce latency
-> 24APR17
- Revert undervolt the lower frequencies a bit more
-> 15APR17
- Undervolt the lower frequencies a bit more
- hrtimer: enhance power efficiency
- cpu: enhance power efficiency
- sched: Trying to reduce power usage
- changes for relaxed functions
-> 07APR17
- Misc. code improvements
-> 05APR17
- Build for 4g
-> 03APR17
- Undervolt
-> 27MAR17
- Adjust overclock and voltage settings
-> 27FEB17
- Revert tenderloin: disable CONFIG_MSM_CPU_FREQ_SET_MIN_MAX
-> 22FEB17
- Add darkness governor
-> 14FEB17
- merge upstream. LZ4 and zram restored
-> 09FEB17
- Revert all ev lz4 and zram commits
-> 08FEB17
- Remove medusa governor (for now)
- cpufreq: Optimize cpufreq_frequency_table_verify()
- msm: kgsl: fix sync file error handling
-> 27JAN17
- Fix medusa governor freezes by locking cpu_up/down
-> 26JAN17
- Revert clean up medusa governor min frequency code
- Revert merge upstream
-> 25JAN17
- Merge upstream
- Clean up medusa governor min frequency code and set some tuneables
-> 23JAN17
- fix medusa governor freezes
- fix SECTION_MISMATCH errors during compile
-> 20JAN17
- Add new original medusa governor
- Add lionheart governor
-> 11JAN17
- Revert 'Move wireless regulator timeout to power efficient workqueue' & 'Fix PCC disablement' and rebase
- Merge upstream
- Update smartmax governor
-> 05JAN17
- Move wireless regulator timeout to power efficient workqueue
- Add Link Time Optimization support
- Fix PCC disablement
- Distinguish skz kernel localversion from ev stock
-> 04JAN17
- Add optimized SHA256 arm crypto routines (improves encryption performance by up to 20%)
- Add voltage interface
-> 03JAN17
- Merge upstream
- Compile with O3 optimizations
- Restructure 3d_pdata to improve graphic performance
-> 02JAN17
- Set boot frequency to 1728 KHz
- Enable gpu 2d frequency to 267 MHz
-> 28DEC16
- Merge upstream
- Add invisiblek's [I]enable CONFIG_UID_CPUTIME [/I]commit
- Match smartmax and smartmax_EPS get_cpu_idle_time function code
-> 19DEC16
- Add tripndroid scheduler
- Clean up governor code
- Regen defconfig
-> [U]15DEC16[/U]
- Remove maple io-scheduler
- Add dynamic interactive and alucard governors
-> [U]13DEC16[/U]
- REALLY remove divide-by-zero errors in kernel
- Add maple io-scheduler
-> [U]11DEC16[/U]
- Merge upstream
- Remove divide-by-zero errors in kernel
- Tune hyper governor
-> [U]09DEC16[/U]
- Tuned Smartmax_EPS governor for improved Touchpad performance
- Added dancedance governor (very smooth and fast with good battery performance. I love it!)
- Added hyper governor (based on conservative with some smartass features)
-> [U]05DEC16 Initial upload[/U]
- CPU Overclock to 1836 MHz
- L2 OC to 1836 MHz
- 2D GPU OC to 228 MHz
- 3D GPU OC to 320 MHz
- Add Smartmax_EPS governor
Will it work on android evervolv 7.1 ?
You didn'texplain what tweak did you do except overclock. What are the benefit except higher freq ?
Steelskinz said:
Will it work on android evervolv 7.1 ?
-SNIP-
Click to expand...
Click to collapse
Yes.
Thanks Shumash. If you wish to return to stock EV kernel you do a full wipe and reflash the ROM?
Nomad1600 said:
Thanks Shumash. If you wish to return to stock EV kernel you do a full wipe and reflash the ROM?
Click to expand...
Click to collapse
No need to do a wipe since only the kernel will change. There is another way to do it if you know your way around, i.e.,
Before flashing the SKZ kernel, copy the uImage.Evervolv file in /boot to a location on your 'sdcard'.
Flash the SKZ kernel
If you decide to restore the original EV kernel, delete the uImage.Evervolv file in /boot
Copy the saved copy of uImage.Evervolv on the 'sdcard' to /boot.
Reboot and stock kernel will be restored (any settings you made while in the SKZ kernel will be lost).
New Tricks, Old tablet
shumash said:
No need to do a wipe since only the kernel will change. There is another way to do it if you know your way around, i.e.,
Before flashing the SKZ kernel, copy the uImage.Evervolv file in /boot to a location on your 'sdcard'.
Flash the SKZ kernel
If you decide to restore the original EV kernel, delete the uImage.Evervolv file in /boot
Copy the saved copy of uImage.Evervolv on the 'sdcard' to /boot.
Reboot and stock kernel will be restored (any settings you made while in the SKZ kernel will be lost).
Click to expand...
Click to collapse
Nice thanks Shumash :highfive: I'm going to try this out
Update:
Checkout the performance boost with the SKZ kernel @ 1836! Looking good Shumash:good:
View attachment 3961347
Note: Tested with Antutu Benchmark here:
[SKZ Update] 09 DEC 2016
Update available.
CHANGELOG
Code:
-> 09DEC16
- Tuned Smartmax_EPS governor for improved Touchpad performance
- Add dancedance governor (very smooth and fast, good battery performance. I love it!)
- Add hyper governor (based on conservative with some smartass features)
Are there any details on which versions of android this will work with, e.g., if we want to use it with android 4.4.4?
Razor512 said:
Are there any details on which versions of android this will work with, e.g., if we want to use it with android 4.4.4?
Click to expand...
Click to collapse
Nope. That's why it's stated for EV. You just need to try it out and see. Keep in mind that other ROM's name the uImage as cyanogenmod or AOKP, etc., and this kernel won't work unless renamed to match the kernel it replaces. Report back for others
Has anyone tried the 12/9 kernel over the 12/9 nightly? I got boot error. Rom worked fine before I tried the kernel. I just reflashed from and it works fine.
Crashes with Antutu Benchmark when OC'd
jerryatherton said:
Has anyone tried the 12/9 kernel over the 12/9 nightly? I got boot error. Rom worked fine before I tried the kernel. I just reflashed from and it works fine.
Click to expand...
Click to collapse
I was able to boot fine but when I OC to 1836 and tried the dancedance governor I rebooted in antutu benchmark(twice now). Been trying to fetch some logs with the Evervolv bug reporter but it doesn't seem to be working for me. Tested again, stock speeds, default governor and I was able to complete Antutu Benchmark.
Shumash be advised that the 12/9 nightly has moved up to Android 7.1.1, not sure if that's an issue.
http://www.evervolv.com/devices/tenderloin
RolandDeschain79 said:
I was able to boot fine but when I OC to 1836 and tried the dancedance governor I rebooted in antutu benchmark(twice now). Been trying to fetch some logs with the Evervolv bug reporter but it doesn't seem to be working for me. Tested again, stock speeds, default governor and I was able to complete Antutu Benchmark.
Shumash be advised that the 12/9 nightly has moved up to Android 7.1.1, not sure if that's an issue.
http://www.evervolv.com/devices/tenderloin
Click to expand...
Click to collapse
Works fine for me (including 7.1.1), but I'll try and see if I can duplicate the Antutu issue. Did you try dancedance at a lower clock?
Results, 7.1.1 (home rolled on 12/10), 1836 MHz, dancedance governor, fiops scheduler, 320 gpu.
shumash said:
Results, 7.1.1 (home rolled on 12/10), 1836 MHz, dancedance governor, fiops scheduler, 320 gpu.
Click to expand...
Click to collapse
1836 caused a reboot, but the one below didn't. Currently testing hyper...
[SKZ Update] 11 DEC 2016
Update available.
CHANGELOG
Code:
-> 11DEC16
- Merge upstream
- Remove most divide-by-zero errors in kernel
Enjoy.
DELETED. See updated update below
Only 1836 causes crashing
shumash said:
Works fine for me (including 7.1.1), but I'll try and see if I can duplicate the Antutu issue. Did you try dancedance at a lower clock?
Click to expand...
Click to collapse
w1ll1m said:
1836 caused a reboot, but the one below didn't. Currently testing hyper...
Click to expand...
Click to collapse
Yes lower clocks were OK but the max overclock was the problem for me too. Going to test out the newest version of the kernel with the latest nightly and I'll report back thanks:highfive:
[SKZ Update] 11 DEC 2016
shumash said:
Update available.
CHANGELOG
Code:
-> [U]11DEC16[/U]
- Merge upstream
- Remove divide-by-zero errors in kernel
- Tune hyper governor
Enjoy.
Click to expand...
Click to collapse
Updated again. Re-download the latest
Testing
shumash said:
Updated again. Re-download the latest
Click to expand...
Click to collapse
I redownloaded my kernel zip and the latest Evervolv 12,11 nightly but I'm still experiencing crashing with Antutut benchmark when the CPU is set to 1836. It always crashes in the same place after the video tests @ Image processing blur load screen. However when I set the CPU to 1782 it finishes the test every time and gets a great score.
Note: using the default governor while testing
RolandDeschain79 said:
I redownloaded my kernel zip and the latest Evervolv 12,11 nightly but I'm still experiencing crashing with Antutut benchmark when the CPU is set to 1836. It always crashes in the same place after the video tests @ Image processing blur load screen. However when I set the CPU to 1782 it finishes the test every time and gets a great score.
Note: using the default governor while testing
View attachment 3966730
Click to expand...
Click to collapse
As you are aware, some 'pads can OC, some can't. Mine can (with the default governor, 19793).
Mine could also oc to 2.1ghz back in jellybean but my phone could not reach it own max oc, it mostly depend of if you got a good SoC batch but they required more cheaper one for metting the demand or a bad one which was intended for getting use has lower end. That mostly the case with PC CPU but since all mobile device was underclocked by default, it did not make any difference for end user because of the heat and energy consumption of full clock or overclock.
Great to see the Tenderloin still alive with at less a single custom roms but seeing a custom kernel on rolland's video on my youtube feed made me fell like "wtf, i need to get updated on that device devellopement, it's really happening ! ". Thank shumash, my tenderloin might not be my main tablet anymore (buyed an Surface Pro 3 and found a Nexus 7 2012 in the dump) but's still a very good device for light stuff or has a second screen in bed for a guide in a game. You are amazing like always.