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?
##DISCLAIMER##
Though this is tested and I am using this, and nothing evil happened until now, it might slap you so hard in your face that not even google is able to find you anymore.
No kidding: !Experimental! This does not fix one bug of CM9 nor does it attempt to do so. So don't b*t*h me about that. This is meant as a test for KSM, to see if any problems arise and how much use (performance gain / more free ram) this gives on Android. (theoretically it should be very useful)
For everyone who wants to give it a try:
Bricked-CM9Kang v4
based on AOSP CM9 #Kangified
What does it give you:
Everything from CM9 + Touchscreen fixes (Dees_Troy27) + KSM (Kernel Samepage Merging) + fixed init.d script autoexecution on bootup (turl)
Bricked v0.4 with KSM support, Default clocks @ 1566/192 ondemand
- OC up to 1914Mhz, Voltage Control via sysfs (SystemTuner, etc), etc, etc.... Look here.
Install:
Do you want a fresh install? Wipe data/factory reset & just flash from recovery.
Already on cm9 and don't want to loose your data? Just flash over your current install without wiping (don't forget to reinstall gapps afterwards).
Download:
v4
ROM + Kernel:
mediafire.com: Click Me
http mirror: Click me
SHA1: 14db526c93962359995ea260c80d2811ba32eaae
Gapps: Click Me
SHA1: 1d277d2d7e802eb13975757df46c09afbaafcd2c
Gappsfixer: Click Me
This removes bad <shared-user> elements from packages.xml and lets android regenerate them. This fixes a problem with gapps signatures. (Just flash it after gapps, there can nothing go wrong)
SHA1: 5b66a2e160922626d67b30b459b5323deb8f549d
#cyanogenmod-touchpad Readme and Gapps:
http://ergh.org/cmtp/
Mirror (Folder by jassycliq):
mediafire.com, adfree: Click Me
What is KSM - Kernel Samepage Merging?
From Wikipedia, the free encyclopedia
Kernel SamePage Merging (KSM) (also: Kernel Shared Memory, Memory Merging) lets system share identical memory pages amongst different processes or virtualized guests. This is done by scanning through the memory finding duplicate pages. The duplicate pair is then merged into a single page, and mapped into both original locations. The page is also marked as "copy-on-write", so the kernel will automatically separate them again should one process modify its data.[1]
KSM was originally intended to run more virtual machines on one host by sharing memory between processes as well as virtual machines. Upon implementation, it was also found to be useful for non-virtualized environments where memory is at a premium [2][3]. An experimental implementation of KSM by Red Hat found that 52 virtual instances of Windows XP with 1GB of memory, could run on a host computer that had only 16GB of RAM [4].
KSM first appeared in the version 2.6.32 Linux operating system kernel [2]. To be effective, the operating system kernel must find similar memory pages held by different processes. As well it needs to decide whether the pages are going to update infrequently enough that SamePage Merging would be an efficient use of processor resources [3]. When first proposed, there were concerns that this feature could be exploit as a security vulnerability (this concern has since been addressed). Another concern is that although memory usage is reduced, CPU usage is increased, thus negating potential increases in performance [1].
References
^ a b "Home Page". lwn.net. kernel.org. Retrieved 2010-08-21.
^ a b "Home Page". IBM DeveloperWorks. IBM. Retrieved 2010-08-21.
^ a b "Home Page". kernel.org. kernel.org. Retrieved 2010-08-21.
^ "Home Page". kernelnewbies. kernelnewbies. Retrieved 2010-08-21.
more to KSM: http://bitcube.co.uk...merging-and-kvm
How to see the Magic happening?
Code:
cat /sys/kernel/mm/ksm/full_scans
cat /sys/kernel/mm/ksm/pages_shared
cat /sys/kernel/mm/ksm/pages_sharing
cat /sys/kernel/mm/ksm/pages_to_scan
cat /sys/kernel/mm/ksm/pages_unshared
cat /sys/kernel/mm/ksm/pages_volatile
cat /sys/kernel/mm/ksm/run
cat /sys/kernel/mm/ksm/sleep_millisecs
or just:
Code:
cat /sys/kernel/mm/ksm/*
to get all at once.
Check your RAM stats with:
Code:
free
Source for KSM implementation:
Android source modifications: Click Me
Kernel source modifications: Click Me
(ofc KSM must be enabled in your kernel config)
Source for Bricked:
Click Me
Thanks to everyone who ever contributed anything (even only a whitespace) to any of the used software.
Code:
[B][U][SIZE="5"]Changelog:[/SIZE][/U][/B]
[B]*** v4 ***[/B]
ROM:
synced with CM9 repo @ 05:04 PST 31/01/12
KSM code cleanup. Testing new configuration
Tweaking KSM, lowering CPU usage
Fixing restore of gapps after install (my fault, c&p was being a b*tch)
Allow reboot to recovery (http://review.cyanogenmod.com/#change,12311)
Allow power options menu (http://review.cyanogenmod.com/#change,12315)
Added CombinedBar Auto Hide (http://review.cyanogenmod.com/#change,12281)
SurfaceFlinger: Set the buffer size in the GraphicBufferAlloc (http://review.cyanogenmod.com/#change,12263)
Preference to disable bootanimation for faster boot (http://review.cyanogenmod.com/#change,12169)
Kernel:
ksm update from bricked-pyra source
Lowered min voltage once again (now: 700mV)
Updated KGSL driver with bricked-pyramid:
msm: kgsl: 8Stages 3D scaling, highest @ 300Mhz (fraction 33)
msm: kgsl: 6stages 2D scaling, highest @ 266,7Mhz, 33,35% Overclocked (fraction 100)
msm: kgsl: GPU off while screen off!
msm: kgsl: improved KGSL suspend
msm: kgsl: Use the correct virtual address for pmem regions
msm: kgsl: Delay 30ms to make sure GPU is ready during resume time
msm: kgsl: Update pwrlevel_change
msm: kgsl: Add sysfs attribute to turn GPU DCVS off/on
msm: kgsl: Early Suspend drivers
msm: kgsl: Turbo Mode
msm: kgsl: Don't check for idle while suspended
msm: kgsl: Make kgsl_idle_check check if a nap is allowed
msm: kgsl: fix parameter checking in adreno_ringbuffer_issueibcmds
msm: kgsl: Abort kgsl_pwrctrl_wake() when in KGSL_STATE_INIT
msm: kgsl: create singlethread wq instead of per-cpu wq
msm: kgsl: Fixing earlysuspend/lateresume for multiple devices.
msm: kgsl: run kgsl_idle_check after resuming a device
msm: kgsl: fix coding derp for init pwrctrl
[B]*** v3 ***[/B]
repo synced with CM9 (18:00 CET, 27/01/12)
touchscreen fixups by Dees_Troy, ts: lower touch threshold to help with light touches
touchscreen optimization by Dees_Troy, remove unneeded code and optimize filter
disable_dock_switch, fixes touchstone freezes, thanks to nomadman
hq bootanimation, by Kevin1981 from #cyanogenmod-touchpad on freenode
new quicksettings options, optimized for tablets, http://review.cyanogenmod.com/12162
External Bluetooth GPS support, http://review.cyanogenmod.com/#change,12095
...and many more stuff from the sync, take a look under settings ;)
[B]*** v2 - installfix ***[/B]
*fix setting Bricked as default kernel.
*delete uImage.CyanogenMod
[B]*** Initial Release - v2 ***[/B]
Based on cm9 a0.5
Touchscreen fix by Dees_Troy27
init.d script on boot execution fix by Turl
KSM support kernel & rom side
_
Nice
Sent from my Touchpad using xda premium
sweet dude. I was wondering when the custom ROMs would start showing up. East coast so too late to flash tonight but I will definitely try this out tomorrow. Nice work on the kernel btw.
Any sod fixes on this?
Sent from my Galaxy Nexus using xda premium
Bed time now, I will download and install tomorrow. Thanks!
Great stuff! If we are already using your kernel with CM9, can we just wipe and flash this, or is there something more that needs to be done?
OP updated.
v2 - installfix
###########################################
hotts23 said:
Great stuff! If we are already using your kernel with CM9, can we just wipe and flash this, or is there something more that needs to be done?
Click to expand...
Click to collapse
show-p1984 said:
Install:
Do you want a fresh install? Wipe data/factory reset & just flash from recovery.
Already on cm9 and don't want to loose your data? Just flash over your current install without wiping (don't forget to reinstall gapps afterwards).
Click to expand...
Click to collapse
When I saw the word "bricked" I was utterly scared.
Thanks for all your hard work.
Installed and its AMAZINGLY FAST.
But no WIFI working.. Bummer.
Going back to 0.5
Sent from Epic Touch HD with Tapatalk
axiapc said:
Installed and its AMAZINGLY FAST.
But no WIFI working.. Bummer.
Going back to 0.5
Sent from Epic Touch HD with Tapatalk
Click to expand...
Click to collapse
It has wifi Oo
gimme adb shell uname -a please
Or if you installed the v2 without the "installfix" in it's name, just download the installfix one and flash it over, flash gapps, done.
what is the gappsfixer file for?
Sent from my cm_tenderloin using xda premium
brigked said:
what is the gappsfixer file for?
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
It removes bad <shared-user> elements from packages.xml and lets android regenerate them. This fixes a problem with gapps signatures. (Just flash it, there can nothing go wrong )
show-p1984 said:
It removes bad <shared-user> elements from packages.xml and lets android regenerate them. This fixes a problem with gapps signatures. (Just flash it, there can nothing go wrong )
Click to expand...
Click to collapse
OK. Thanks for quick response. Just wondering because i didnt see an explanation on the op. Anyways, flashed it and its working great. wifi is working for me. Thanks!
Sent from my cm_tenderloin using xda premium
show-p1984 said:
It has wifi Oo
gimme adb shell uname -a please
Or if you installed the v2 without the "installfix" in it's name, just download the installfix one and flash it over, flash gapps, done.
Click to expand...
Click to collapse
K brb
Sent from Epic Touch HD with Tapatalk
Just flashed over alpha 0 with the hotfixes, no wipe. Got a kernel panic when it finished booting right after I unlocked it. A quick power+home button reboot got me back to normal. Didn't remember to get a log and haven't been able to reproduce it again, so I'll just attribute the bug to not wiping.
Other than that, everything seems to be working very smooth so far! Thank you!
Reflashed and now WiFi uppppppp...
ICS HP Touchpad using Tapatalk HD
it might be early to request, but can we have the option to permanently enable OTA ADB? please?
Good work dude
I'll flash it later in the evening (GMT).
what's the change log for Bricked V0.34 coz dedicated thread states v.0.31 as latest?
Sent from my Desire HD
question about installing:
If I am still on CM7, do I need to use ACME installer to install your rom?
I know you stated that for fresh install we can just use recovery, but for CM9 it was suggested to use acme installer instead of recovery
thank you
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.
This custom kernel is base on diego-ch's TWRP kernel.
I call it CoCore.
( Responsibility )
I'M IN NO WAY RESPONSIBLE OF ANY DAMAGE CAUSED BY USING THIS CUSTOM KERNEL.
( Compatibility )
This kernel works well on i9070.
I am sorry that it causes high cpu load on i9070P!
( What is needed )
* An I9070 (Andorid 2.3.6)
* Some Android experience
* Know some knowledge of how to use Android Terminal
* More patience
( Features )
TWRP Recovery 2.2.1
28 CPU Governers
8 I/O Schedulers
IO Unlocked (increased a bit speed)
Init.d Script
Custom Bootanimation
Deeper Sleep Mode
zRAM, SWAP Supported
NTFS(Read Only)
CIFS
ARM ThumbEE
ARM VFP with neon
Optimized RWSEM Algorithm
Mali GPU Tweakes/Controls
LZO Kernel Compression ( for faster boot )
Removed Useless Drivers ( for faster boot )
SLUB Memory Allocator
Automatic readahead cache size
Audio Boost*
Linaro GCC Toolchain
And many miscellaneous tweaks, it's hard to make a list for them.
Maybe i also forgot them.
A ton of new features in my updates,please Check the updated version.( See below )
( Detailed explanation )
CPU Governers Supported:
Code:
Performance, OnDemand(default), Lionheart, Powersave, Userspace,
Conservation, OndemandX, SmartassV2, Interactive, Scary, Sakuractive,
PegasusQ, Intellidemand, Lazy, Wheatley, HotPlug,
SmartAss, LagFree, BrazilianWax, InteractiveX, MinMax, SavagedZen,
Aggressive, AggressiveX, Gallimaufry, GallimaufryX, AbyssPlug, Skywalker
* To get stable scores, please use Performance to run benchmarks.
* For daily using, i recommend PegasusQ.
* Please test the governors by yourself.
* And the PegasusQ will hotplug the second cpu when screen turns off,that might cause music skip when system load is heavy.
* If unsure,please use ondemand(default)
IO Schedulers Supported:
Code:
NOOP, Deadline, CFQ, BFQ(default), SIO, VR, anticipatory, ZEN
* To get more information about governers/io schedulers, here:
http://forum.xda-developers.com/showthread.php?t=1369817
* For daily using, i recommend SIO/BFQ/ZEN
* Please choose a best io scheduler by yourself.
Init.d Script:
* Please make sure there is a latest busybox in your system.I found that init.d didn't work properly on some devices which have old version busybox.
* The init.d folder (/system/etc/init.d) must have 0755 permissions.
* If the scripts dont have execution permissions,it wont be execute automatically.
Custom Bootanimation:
* Please put the bootanimation.zip in /system/media with right permissions(0644).
* If there isn't any custom bootanimation, kernel will load Samsung official bootanimation.
DeepSleep Mode:
* Default mode is State4, i changed it to State5. Increased standby life time.
* If you use a hotplug governor,it might be unstable when you use the deepest sleep mode.
* Some users reported that ondemand works well with deepest sleep mode.
* If you mind the standby time of the phone,please give it a try.
* You can get information about CPU sleep states:
Code:
cat /d/cpuidle/stats
* To change the allowed deepest sleep mode: (e.g. Allow State6)
Code:
#echo 6 > /d/cpuidle/deepest_state
zRAM & SWAP:
* zRAM must be enabled by script/command.
Code:
mkswap /dev/block/zram0
swapon /dev/block/zram0
* SWAP must use with a SWAP partition in sdcard.
Code:
mkswap /dev/block/mmcblk1p2
swapon /dev/block/mmcblk1p2
* Because we have a large memory, the zRAM/SWAP is low activity.
* Some users said that zRAM/SWAP wont help the performance of games,they might drop more battery.
NTFS:
* Need a binary called "ntfs-3g" to read/write ntfs sdcard. Built-in NTFS feature only can read.
* Stock Android 2.3 cannot mount NTFS sdcard automatically.
Mali GPU:
* Allowed larger memory.
* Allowed larger OS memory for buffer. ( 6m -> 10m )
* L2 cache max reads tweakable
* Enabled some features in Makefile.
* Disable a big debugging checking
Audio Tweaks:
* Enabled directly rendering
* Enabled 32k_clk ( a feature of AB8500 )
* Volume Boost! ( v3.6-3.8rc,optional in v4.0 )
* Dynamic Range Enhanced! ( v3.6-3.8rc,optional in v4.0 )
( Installation )
Method 1
1. Flash the kernel which has TWRP via Odin. You can flash diego-ch's TWRP kernel, or flash "GT-I9070-Kernel-CoCore.tar.md5" in attachments.
Here diego-ch's TWRP kernel: http://forum.xda-developers.com/showthread.php?t=1873119
( flash custom kernel will increase binary counter!! )
2. Run Odin, Put the md5 files in PDA, Pit files doesn't need.
3. Only check "Auto Reboot" and "F.Reset Time"
4. Click Start to flash, wait for phone reboot.
5. Boot into TWRP, Tap Install, Select i9070_kernel_CoCore_TWRP.zip, Flash it.
And, if you have TWRP kernel already, flash the zip via TWRP directly.
Method 2 (Experienced users only)
This method will not increased binary counter, but ROOT permission is needed.
1. Get kernel.bin.md5 from i9070_kernel_CoCore_TWRP.zip
2. Put kernel.bin.md5 in sdcard
3. Run your favourite terminal app, type these codes
Code:
$su
#dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15
4. Reboot
If you typed a wrong patition number, perhaps it will brick your phone!!!
Think twice before you hit Enter.
( Updates )
01/03/2013 Update: CoCore v4.1
Hmm,This is BETA version.
Block: Added ZEN io scheduler (Bases on noop,deadline and sio)
CPUFreq: Added Skywalker governor (FreqTable tweaked)
Mali: Increased the default l2 max reads 28kb -> 48kb
Mali: Disabled a big debugging tracking
RCU: jRCU -> TreeRCU (For better CPU/RAM throughput!)
NWFPE: Enabled ex-nwfpe
Please remove the mali l2 init.d script tweaks,guys
CoCore-mini 1.4 is at #842 post.
12/23/2012 Update: CoCore v4.0
Mali: Driver updated, re-tweak the parameters
ASoC/ab8500: Driver updated
NET/conf: Enable HSTCP(high-speed tcp),Westwood+,Veno,Hybla,YeAh configs. Cubic(stock) conf is default.
Block: Set BFQ as default io scheduler
Block: Automatic readahead cache size limit (depend on the size of your sdcard)
Block: Re-tweak SIO/VR/Deadline for flash nand devices
MM: SLQB -> SLUB
SCHED: Remove fair_sleepers, revert the parameters back to stock
MISC: Remove a ton of juck!!!, Highest complie optimization level, boot faster(compare to old versions,8800ms~9100ms now)
PS.
The cifs.ko and smbfs.ko have been put out ramdisk.They will be installed to /system/lib/modules (for faster boot)
And i forgot the changes,see my source on my github.There is a changelog.
To change the net configs:
Create a new init.d script:
Change the 'highspeed' to other confs.
Use `sysctl -a | grep cubic` to know what conf you can change to.
`ping` is the simple way to test whether the conf you use fix you or not.
For me,i am using highspeed now. If unsure,keep default(Cubic)
Code:
#!/system/bin/sh
sysctl -w net.ipv4.tcp_congestion_control=highspeed;
I have set the mali l2 cache back to 28kb by default.
To set it to 48kb(max).Use an init.d script.
Code:
#!/system/bin/sh
echo 0x00000030 > /sys/module/mali/parameters/mali_l2_max_reads;
The game fps should be improved a bit,
The values you `echo` must be HEX
BUT,if it doesnt or feels lagged,remove this script.
For me,48kb works well.
The volume++ version is volume boosted. (Someone requires this)
The lagged sound will be increased,too!
12/09/2012 Update: CoCore v3.9Beta8
This is BETA VERSION!!
CpuFreq: Added AbyssPlug (Base on OnDemand+Hotplug)
Mali: Increased the priority of OSMEM (5 -> 1) (See the dmesg)
Mali: Unlocked mali_l2_max _reads in sysfs (You can tweak this parameter now) (Dont set over 48)
(If you find a good value,please share with us!)
Mali: Misc tweaks
Kernel/hz: Fix the defconfig issue (Thanks! @hafidzduddin)
Net/SCH: Reverted back to stock (To experiment the latency of enabling mobile data)
Makefile: More optimization flags
PS.
The Mali parameters are in /sys/module/mali/parameters/
Use scripts/terminal to set them.
12/07/2012 Update: CoCore v3.9Beta3
This is BETA VERSION!
J4FS: J4FS driver works! Bugfree now!
CpuIdle: Revert the ApDeepSleep to stock,and added ApSleep++ custom state
(ApSleep++ and ApDeepSleep only works with non-hotplug governors,e.g: ondemand)
(New sleep state is disabled by default.You can enable them by yourself,if you prefer longer battery.)
CpuFreq: Added Aggressive, AggressiveX, Gallimaufry and GallimaufryX (These are optimazed version of Conservation/OnDemand)
CpuFreq: Fix a hotplug bug of PegasusQ
FS/SYNC: Removed Dynamic Fsync Control,added Ezekeel FSync Control
ASoc/ux500: Raise the pcm buffer size to MAX
NET/Scheduler: Re-tweaked, to experiment the latency of mobile data
Unknown: Fix the touchscreen sudden lost response (According to my using these days,it has been happended again!)
PS.
The FSYNC is enabled by default.Disabling FSYNC can improve IO performance.
In AnTuTu IO Test: Enabled: 350-400 Disable: 540-560
But disabling FSYNC can cause losing data!! It is at your own risk!!
Check the TIPS part to get how to disable it.
12/02/2012 Update: CoCore v3.9Beta1
This is BETA version, at #344 post.
12/02/2012 Update: CoCore v3.8.6rc
ASoC/ab8500: Use another gain mode in order to fix the terrible audio issue.
Sched: Reduce the latency of CFS Scheduler
PS.
The dyn_fsync will casue screen lag when you turn off the screen and there is a heavy io load.
If there isnt any heavy io load,it goes normally.
If you hate this,see the Tips part (#2 post) to get HOW TO disable dyn_fsync.
12/01/2012 Update: CoCore v3.8rc
CpuFreq: Tweaked the freq table of PegasusQ
Blcok: Updated BFQv1 -> BFQr2-1,Fixed the latency of BFQ issue. (BFQv5 is incompatible with Linux 2.6.35)
Sched: Tuned the patamerters of CFS scheduler (Use ThunderBolt's)
Sched_features: Enable Fair_Sleepers,Disable HRTICK
Mali: L2 cache max reads -> 48kb,Fix the mem leak issue.
NET: Set WestWood+ as default CONFIG
fs/sync: Added Dynamic FSync Control
(Improve IO performance greatly.When the screen is on,fsync is off.When the screen is off,fsync is on.)
ASoc/ab8500: Fixed the FMRadio volume balance issue. (Thanks @shut_down)
MISC: Removed a TON of JUNK!!!,And added a workaround to flash kernel quickly.
PS.
The benchmark screenshot is in the #304 post.
How to disable DYN_FSYNC? Check the TIPS part. (#2 post)
What is the flash kernel workaround?
In TWRP,use the Terminal fucntion,SELECT the folderr which has a kernel named "kernel.bin.md5",Start the Terminal,
And just type "fkernel"(No quotes),it will flash the kernel.bin.md5 automatically.
And i found that V(R) is a good io scheduler too.
The BFS CPU Scheduler is incompatible with our kernel.I am about to introduce this in the JellyBean kernel.
11/25/2012 Update: CoCore v3.7
RamDisk/TWRP: Added a temporary workaround to mount emmc(internal memory)
Block: SIO io scheduler updated. (2012 version) (Thanks @hafidzduddin)
CpuFreq: Fixed the name issues of governors (SetCPU cannot tune the parameters of governors, now fixed)
CpuFreq: Added LagFree, BrazilianWax, InteractiveX, MinMax and SavagedZen governors
(New governors havent been tested fully!If unsure, PegasusQ is recommended.)
I have tweaked the freq tables of most governors.
Mali: L2 cache max reads: 48kb -> 44kb , FPS increases (1-8fps) in simple scenes.
(Reserved 4kb for buffering, perhaps it will fix the sudden lag in games)
Sched: Fix SAMSUNG source code errors
Sched: Added AutoGroup Scheduler v4
Net/Sched: Re-changed the scheduler of net
android/logger: Reduced the logger size
ASoc/ab8500: Headset Volume adjusted, Dynamic Range enhanced! (i recommend using PowerAMP/RockBox)
PM(PowerManagement): Added a new feature, Operating Performance Point (OPP) Layer library
MISC: Disabled something useless(for faster boot),
Added GenLock API, MM&DMA hacked,
Added a new feature DM_CACHE,
more GCC optimizations in MakeFile
PS.
Dont use high volume to listen to music over 1 hour, it it not good for your ears.
Just reduce some volume.And i havent gained the speaker volume, dont worry.
The TWRP has some grapics issues when entering the emmc folder(it happends soemtimes, not always),
if it happended just tap back button and enter again.
(Some guys required this becaues them havent an external sdcard! )
And about the SetCPU issues. If you cannot tweak the parameters of some governors,
go to /sys/devices/system/cpu/cpufreq/(governor_name)/, you can tweak them here.
Make a script to tweak them quickly.
I think there is no point in updating to 2.6.35.14, because it updates a lot of useless drivers.
11/18/2012 Update: CoCore v3.6
Block: Added anticipatory io scheduler
CpuFreq: Added HotPlug and SmartAss governors
CpuFreq: Tweaked SmartAss and SmartAssV2 freqtable in order to match our device
Kernel: Adjusted many parameters
Lernel: Built with optimized compiler options
Sched: Added Fair_Sleepers feature,
disabled Gentle_Fair_Sleepers feature,
enabled HRTICK feature
MM: Increased Min readahead 16k -> 32k
JHash: Added JHash v3 speed tweak
Mali: Use another timestamp mode
ab8500/asoc: Headset volume gain boosted! (Sounds perfectly.My ears will be satisfied with i9070+Edifier H850. )
11/11/2012 Update: CoCore v3.5
Kernel: Revert LZO compression ( LZO is the fastest, but it makes kernel largest )
Kernel: Removed some bad tweaks
Kernel: Compile with Linaro GCC 4.4.5 ( The final version of Linaro GCC 4.4 series )
Ramdisk: For power saving, cifs.ko and smbfs.ko will not be loaded by default
Block: SIO, V(R) and Deadline io scheduler tweaked ( Better IO throughput )
FS: EXT2, EXT3 and EXT4 speed up
JHash: Updated to JHash v3
Sched: Enabled HRTICK
RCU: Added and use JRCU
TCP: Change TCP_Config to VENO ( Faster on wireless network ), and enabled HSTCP ( High-speed TCP )
NET: Net schedulers tweaked, in order to work with VENO config
NET: Introduce u64_stats_sync infrastructure
MM: Added vzalloc() and vzalloc_node() helpers
MM: Added and use SLQB memory allocator
MM: Added fudgeswap
SYNC: Added synchronization framework
BCM4330(WLAN): Enabled PM_FAST mode in standby
CGroup: Enabled FREEZER feature
PS. And many misc tweaks.
And i added some modules in /lib.
I tweaked mali parameters again (MEM -> 48MB OSMEM -> 8MB).
Because i find that when the memory is too big, it feels lag.
According to my test, in simple scence, fps increases (1-2fps); in complex scence, fps reduces (1-2fps).
But UI is faster in low frequencies! ( i often use signle core at 800Mhz )
10/28/2012 Update: CoCore v3.1
Mali: Fixed the fps issue.
RCU: Use Tiny-PREEMPT RCU (To reduce memory footprint, and feel more smooth)
Kernel: Removed some bad tweaks.
10/28/2012 Update: CoCore v3.0
Bug Fixed: Rolled back to old ramdisk (TWRP 2.2.1) in order to fix wifi hotspot issue.
MM: Increased sdcard max read ahead to 2048kb. (It's nice to work with my class-4 sdcard)
FS: Added AUFS,AutoFS4 support.
FS: Improved a bit perfromance of ext4.
RCU: Added Tiny-PREEMPT RCU.
RCU: Boosted. (Prefered real-time response)
CFS: Boosted.
Log: Reduced the log buffer size.
TCP: Enabled some features, optimized.
Net: Removed some schedulers.
Kernel: Removed some bad tweaks.
CGroup: Boosted.
CGroup: Added timer slack subsystem feature.
CpuIdle: ApDeepSleep(State6) worked! (Experimental,enable by yourself. Default is State5.)
LIB/CRC32: Added optimized CRC32 algorithm.
And lots of misc tweaks.
10/23/2012 Experimental Update
CpuIdle: State6( ApDeepSleep ) works!! Added "ARM_OFF" to State5!!
10/21/2012 Small Update
Update: TWRP 2.3.1.1 ( Thanks! @diego-ch )
Mali: Increase OS memory for buffer ( 8M -> 16M )
init.d: Make it as service
LIB: Add memcopy macoros and functions
ARM: Add optimized AES and SHA1 routines
ARM: Add optimized SHA1 implementations ( boot faster )
ARM: Enable ICache feature
ARM: Enable BPredict feature
ARM: VFP hard+neon float flag
ARM: JIT network Compiler ( experimental )
CPUIDLE: Add a custom sleep state ( state6,experimental )
Kernel: Use LZMA compresstion ( boot faster )
Kernel: Add XZ compresstion support
CFS: Tweaked
Revert: Gentle_Fair_Sleepers ( for smooth UI )
Compatible with JetMOD now
( Old versions downloads )
*** These have j4fs bug! ***
CoCore v3.1 http://d-h.st/1Q5
CoCore v3.5 http://d-h.st/qKY
CoCore v3.6 http://d-h.st/wvi
CoCore v3.7 http://d-h.st/48k
CoCore v3.8rc http://d-h.st/Eui
CoCore v3.8.6rc http://d-h.st/XEf
( Thanks )
Thanks to everyone who helped me.
Special Thanks:
@diego-ch
@varun.chitre15
@hafidzduddin
@shut_down
@hackbob
@Adi_Pat
@JackStow
The source code is available on my github now.
If there are any issues, please report.
And if you like my work, Press THANKS Button Please. It encourages me.
( Tips )
1. For performance, please remove libGLES_android.so in /system/lib/egl to disable weak CPU rendering.
2. Flash your kernel quickly via Ternimal.
Creat a new file (named `ddkernel`) with RootExplorer.
Write these codes:
Code:
#!/system/bin/sh
source=`busybox realpath kernel.bin.md5`;
echo "DD: Flashing $source";
busybox dd if=kernel.bin.md5 of=/dev/block/mmcblk0p15;
Save , and set right permissions (0777), put it in /system/xbin
Now, you can `cd` to the folder where stores `kernel.bin.md5`, and use `ddkernel` command to flash kernel.
3. Mount your NTFS sdcard
Firstly, you need a binary called "ntfs-3g". Put this binary in /system/xbin
Open your terminal app.
Code:
mkdir sdcard-ntfs
ntfs-3g /dev/block/mmcblk1p1 /sdcard-ntfs
4. My sysctl.conf
Code:
vm.dirty_expire_centisecs=3000
vm.dirty_writeback_centisecs=500
vm.dirty_background_ratio=40
vm.dirty_ratio=80
vm.vfs_cache_pressure=1
vm.highmem_is_dirtyable=1
To use this file,you must have installed busybox,and put this file in /system/etc
Go to /system/etc/init.d/,create a new file(Any name you like),write this(Remember to set right permissions(rwxrwxrwx) of new file):
Code:
#!/system/bin/sh
busybox sysctl -p;
Now your sysctl.conf will be loaded automatically in every boot.
5. How to disable Dynamic FSync Control? (CoCore v3.8-v3.8.6 ONLY)
In your /system/etc/init.d/,create a new file
Code:
#!/system/bin/sh
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active;
Now,this function will be disabled in every boot.
6. How to Control the FSYNC? (CoCore v3.9+)
In your /system/etc/init.d/,create a new file(any name you like)
Code:
#!/system/bin/sh
# Disable FSYNC
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled;
# Enable FSYNC
#echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled;
Or you can control the FSYNC via terminal realtime.
Good work!
Just I have a request
Can you try this on JetMOD and tell me if Power menu options of Reboot, and Reboot recovery works?
I am planning to ship this kernel in next update of JetMOD
varun.chitre15 said:
Good work!
Just I have a request
Can you try this on JetMOD and tell me if Power menu options of Reboot, and Reboot recovery works?
I am planning to ship this kernel in next update of JetMOD
Click to expand...
Click to collapse
ok, i will try today.
Sent from my GT-I9070 using xda premium
Looks nice. Got the I9070 today. Will test it out soon.
Btw, which users are working on CM ? I would like to contribute. I have already forked hackbob's source. Will look into it sometime later.
Edit : Removed. Double post.
Shaaan said:
Looks nice. Got the I9070 today. Will test it out soon.
Btw, which users are working on CM ? I would like to contribute. I have already forked hackbob's source. Will look into it sometime later.
Click to expand...
Click to collapse
If i got it right, @diego-ch @hackbob @Adi_Pat are working on CM.
cocafe said:
If i got it right, @diego-ch @hackbob @Adi_Pat are working on CM.
Click to expand...
Click to collapse
Thanks.
Is there any known method to reset the binary counter ? Does triangle away work ?
Shaaan said:
Thanks.
Is there any known method to reset the binary counter ? Does triangle away work ?
Click to expand...
Click to collapse
No, there isn't. Triangle Away only works on ICS/JB
When get JB source code, we can have a try.
Sent from my GT-I9070 using xda premium
tnx allot dude, i`m sad that i am at the office and can`t test your kernel :|
I have made CWM. Should i include it in the boot image and flash ?
I dont see any zip which includes the .img format..
after flashing it by TWRP, it stuck on boot logo :S
i was using jetmob rom before, and need to restore the backup.. i'v tries twice, and same boot logo stuck..
JackStow said:
after flashing it by TWRP, it stuck on boot logo :S
i was using jetmob rom before, and need to restore the backup.. i'v tries twice, and same boot logo stuck..
Click to expand...
Click to collapse
Yes this is incompatible for JetMOD.
Wait for next update of JetMOD
Shaaan said:
I have made CWM. Should i include it in the boot image and flash ?
I dont see any zip which includes the .img format..
Click to expand...
Click to collapse
Great, You have made CWM for i9070?
i9070 kernel format is zImage, not boot.img.
You can fork the kernel repo of diego, replace the recovery files, and complie kernel.
Put it in dev thread.
We will test it.
Sent from my GT-I9070 using xda premium
JackStow said:
after flashing it by TWRP, it stuck on boot logo :S
i was using jetmob rom before, and need to restore the backup.. i'v tries twice, and same boot logo stuck..
Click to expand...
Click to collapse
Try to delete/rename the init.d folder in /system/etc.
Some scripts of JetMOD stuck booting.
Please report me if it works.
Sent from my GT-I9070 using xda premium
i have flashed your kernel and i am happy to see that drop of fps is gone, the rest is working splendit as well, tnx again
installing these kernel?
hi cocafe.
your custom bootanimation work?
in my kernel custom bootanimation loops never stop.
i use diego-ch ramdisk
im a user of galaxy ace 2
What is that CPU/b2r2 rendering?
Is that audio tweak included without flashing " optional scripts? If I do not want to enable "Deepest Sleep" and "Mount" from optional scripts zip, is it enough to delete them from the zip?
hafidzduddin said:
hi cocafe.
your custom bootanimation work?
in my kernel custom bootanimation loops never stop.
i use diego-ch ramdisk
im a user of galaxy ace 2
Click to expand...
Click to collapse
Yes, several weeks ago, i fixed that loop bug.
You can check the ramdisk of my kernel. There is a small workaround in post_boot.sh.
Here the method:
in init.ux500.post_boot.sh, write these code
# fix custom bootanimation loop
sleep 4;
bootani=`ps | grep bootanimation | cut -b 10-16`;
kill $bootani;
Sent from my GT-I9070 using xda premium
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.