Related
Current release: Version 2.0 (stable) [09/06/2012]
SOURCE CODE: Available at GitHub
*WARNING PLEASE USE AT YOUR OWN RISK*
DISCLAIMER
FIRST OF ALL THIS IS NOT AN OFFICIAL KERNEL, IT IS NOT SUPPORTED BY OFFICIAL CM10 ROMS OR ANY PREVIEW ROMS.
ONCE YOU INSTALL THIS KERNEL YOU WILL NOT BE SUPPORTED IN THE CM10 / CM9 OFFICIAL/UNOFFICIAL DEVELOPMENT THREADS
OF ANY FORUM i.e XDA, SLATEDROID, etc.. THIS MEANS THAT YOU MUST NOT REPORT ANY ANDROID / CM BUGS TO THE ORIGINAL
COMMUNTIY THREADS FOR THE ROM YOU USE! YOU MAY HOWEVER REPORT ANY CM/ANDROID/KERNEL RELATED ISSUES TO THIS THREAD ONLY!
Click to expand...
Click to collapse
Features
CPU Overclocking up to 1500mHz (default is set at stock 1000mhz)
Stable GPU Overclock @ 450mhz (scales from 300 - 450)
Userspace CPU undervolting support
Brick prevention/precaution - disabled MMC_CAP_ERASE function from kernel
I/O Schedulers: BFQ, CFQ, SIO, DEADLINE, NOOP, V(R) (Default VR as of v1.3 - prior to 1.2 default = deadline)
Autogroup Scheduler patched to work with Android via User ID task grouping
CPU Governors: Lionheart, SavagedZen, Lazy, Scary, Intellidemand, LagFree, Wheatley, Lulzactive, SmartAssv2, Interactive, Ondemand, Powersave, Userspace, Performance (depending on ROM - interactive governor is usually set as default gov from userspace during init)
ARM libs from Linux 3.x (v2.0+)
Android Drivers from Linux 3.x (v2.0+)
Linux Security from Linux 3.x (v2.0+)
Cleancache + Zcache Support (v2.0+)
Working Zram - to enable see instructions below (v2.0+)
Fixed Video driver glitches (v1.4+)
Cleaned up tons dmesg errors and warnings (v2.0+)
Memory management fixes and patches from 3.x (v2.0+)
Alsa SoC Tiny HAL patch for better compatibility with Jelly Bean and ICS (reduces/eliminates popping sounds)
Plus various other improvements to kernel configuration and code.
Downloads: (if anyone experiences issues downloading from the androidfilehost mirrors please contact [email protected] to notify of outage as requested by afh admin, thanks!)
Current Stable:
Code:
[URL="http://goo.im/devs/godmachine81/a100_kernel/gm-a100-v2.0-signed.zip"]version 2.0[/URL]
Previous Releases:
Code:
[URL="http://beta.androidfilehost.com/?fid=9390062577138008066"]version 1.5[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-v1.3a-signed.zip"]version 1.3a[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-v1.2b-signed.zip"]version 1.2b[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.1-signed.zip"]version 1.1[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.0.1b-signed.zip"]version 1.0.1b[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.0.1-signed.zip"]version 1.0.1[/URL]
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/godmachine-a100-kernel-autogroup-v1.0-signed.zip"]version 1.0-pre[/URL]
Tools:
Code:
[URL="https://github.com/downloads/godmachine81/Acer-A100-JellyBean-Custom-Kernel/toggle-ag.sh"]toggle-ag[/URL] Tool to Enable/Disable Autogroup and check the status.
'toggle-ag' now included with kernel zip as of 1.3a and is located at /system/xbin/toggle-ag - You may run from a terminal or create Script Manager widgets for each of the script arguments:
Code:
toggle-ag status
toggle-ag on
toggle-ag off
toggle-ag help
Please remember that this script has to be ran as root if you plan to enable/disable autogroup, however you may run as regular user to check the status or get the help dialog.
Important info on toggle-ag script usage (from the script comments):
#**Please note that toggling back and forth the scheduler will
#produce undesired effects, as it takes the system a few minutes
#to switch the process scheduler each time effectively. Imagine
#all processes that run in the backround are rearranged each time
#you switch the process scheduler. In other words you shouldn't
#toggle back and forth to make comparisons as they WILL NOT be
#effective immediately!!
Click to expand...
Click to collapse
Goo Manager Support (NEW!)
You can now download my custom kernels, recovery, tweaks, etc from Goo Manager, available on the Play Store. Goo Manager is similar to ROM Manager, except it works very well with my release of TWRP 2.2.2.0.
First time use instructions:
Set Download path to: /sdcard/goomanager/ in "Settings" (This is important as the location on Android and TWRP need to both be exact same!)
Go back to the main screen in Goo Manager and click Browse Compatible Roms
Choose 'godmachine81'
For kernels choose a100_kernel (you are welcome to look around in my other directories)
Choose the release you wish to download
Choose 'begin download'
You will see a notification for 'Download Finished' - Tap on it
It will prompt you to Select Zip(s) to flash, you may choose more than 1!
After you have selected all the zips you want to flash, go to the option 'Order and flash selected' or if you want to add a zip from a custom location, choose the 'Add zip from another location option'
Once in the Order and flash menu, it is important that you set the order to flash in the proper order, when you are sure it is right, then click Flash (First time you use Goo Manager, it will prompt you that an OpenRecovery is needed, choose that you already have one)
After You click flash, the system will reboot to TWRP, flash your .zip files, and reboot back to android without any user interaction.
ZRAM
What is it?
Zram was developed so that systems with a limited amount of physical ram may allocate a percentage of that to a system swap device using compression. By compressing the data that is in the swap space you can fit more data into the same amount of ram. For example App#1 is consuming 500mb of a total 725mb ram, this leaves you with 225mb free. If you have Zram enabled then App#1 may begin to swap to the zram device, when doing this you will have an advantage, because any amount of data from App#1 that gets swapped out to Zram will be compressed meaning it is actually using less physical ram. So instead of only 225mb free of 725mb you may now end up with something more like 400mb free because data from App#1 is compressed in Zram, in this example thanks to compression you cut the 500mb memory usage of App#1 to 325mb. Zram should have a minimal impact on performance while giving you the benefit of fitting more data into the amount of physical ram your device has.
HOWTO
This kernel includes functional ZRAM support, however to take advantage of it you must enable it from userspace (Android). Cyanogen Mod has an option in Settings > Performance > Memory to enable Zram, however it doesn't properly work - I'm not sure exactly how it is coded in the cm sources, but when you enable zram it doesn't create the zram swap device like it should. To work around this I wrote the following flashable .zip files that contain a script to automatically create the zram swap device at boot, please download and flash the size you wish to allocate to zram:
Zram - 100MB (14% ram)
Zram - 150MB (20% ram)
Zram - 200MB (28% ram)
Zram - 250MB (34% ram)
Zram - 300MB (41% ram)
Zram - 350MB (~50% ram)
To Disable/Remove Zram
In the event that you want to disable Zram then just remove the file(s) at:
/system/etc/init.d/50zram-*
After the 50zram- file has been removed, just reboot your device and you will no longer have Zram enabled. To re-enable just reflash one of the above files.
Flash Back stock kernel?
For those who wanted it: stock-kernel-signed.zip click here to download the stock ICS Kernel - This is the Stock CM kernel from The Android_Device_Acer_A100 Prebuilts on github.
To cut down on general discussion in this thread please note that I have been in the Freenode IRC Dev channel a lot lately. server: irc.freenode.net channel: #iconia-dev - My IRC handle is godmachine81 Join me there for general discussion if you don't mind. Thanks!
Video of Kernel in action on CM10 (appologize for audio and poor quality)
*All references to the Xtreme releases has been removed due lack of time needed to maintain it aside from the stable releases - will update the thread when I Xtreme development gets back underway
ChangeLog:
2.0
Backport several bits mainline code from Linux 3.5 - including Security, ARM Libs, MM, and Android specifics
Zcache + Cleancache added
Ability to concatenate kernel cmdline configuration to Bootloader's cmdline without breaking compatibility with any bootloaders ( needed for zcache/cleancache to work)
Zram patches and updates
Clean up dmesg logs
Deadline IO Sched tweak (1:1 ratio writes/fifo) - VR remains default IOsched
CONFIG: turn off some verbose logging/debugging to reduce overhead, enabled Load Lens Correction Data to smooth out camera operation
TweakIO init script included by default to optimize disk read/write performance
Several other small patches and tweaks to underlying sources
1.6
Minor patches to sources and configuration
1.5
GPU voltage and frequency updates
Interactive governor updated from N7 grouper
Adjust frequency scaling per core for new interactive gov.
1.4
This release was a testing Xtreme release which has recently been removed due to lack of development
1.3a
Script: toggle-ag now included in zip, installs to /system/xbin/toggle-ag
Default IO Scheduler V(R)
Default CPU Governor Lulzactive
1.2b
Bug Fix release for 1.2 - BFQ randomly causing "black screen" issue immediately after boot animation, preventing full boot - reboot resolved issue in most cases, but comes back at random on boot - Setting default I/O scheduler to NOOP until BFQ issue is resolved.
1.2
Autogroup per UID instead of TTY task (huge improvement to autogroup on android)
Set BFQ as default I/O Scheduler
Allocator: Switch to SLUB from SLAB
Remove verbose debugging symbols
Set proper firmware/calibration paths for WiFi in configuration
1.1
Add userspace support for undervolting
GPU OC (400mHZ) on CPU OC > 1000mHZ
Fix "Recent Apps" bug - The glitchy behavior when loading an app cached in the "Recent Apps" menu. Pointed out by DarkNight
Tune SmartassV2 for better behavior and ideal freq set at 760mHZ
Add the following CPU Governors: Lionheart, SavagedZen, Lazy, Scary, Intellidemand, LagFree, Wheatley
Deprecated the non-autogroup release also known as (default)
various other improvements to CPU, voltage, video.
1.0.1b
Add SmartAssv2 CPU Governor
Fix LOCALVERSION
1.0.1
Patched MMC_CAP_ERASE as precautionary to avoid hard brick
1.0-pre
V(R) I/O scheduler Added
SIO I/O scheduler Added
Zram sources backported from 3.0 resolved compile issue
Alpha (First public download)
Overclock added: Min Freq: 216 Max Freq: 1504
CPU Governors: Lulzactive, Ondemand, Interactive, Conservative, Userspace, Performance, Powersave
IO Schedulers: Noop, Deadline, CFQ, BFQ
Autogroup or Default Kernel available
Patch for Tiny HAL - resolves popping in audio on JB/ICS
Click to expand...
Click to collapse
If you would like to help out with the continuance of kernel development for your Acer Iconia Tab A100 please consider a small donation to help out with bills, baby formula, wipes, diapers, etc. All donations are very appreciated by my family and I! Thanks
This kernel is pretty slick, tested a previous version of it, nothing but good things to say of it, hit thanks on your way to flash this.
Tapatalked from my Galaxy S II.
pio_masaki said:
This kernel is pretty slick, tested a previous version of it, nothing but good things to say of it, hit thanks on your way to flash this.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Same to all your projects pio_masaki! I always hit the "thanks" for you too buddy! BTW, the kernel you have been testing is the equivalent in the downloads section to the "default", you may want to take a stab at the "autogroup" kernel. I have been testing it with great responsiveness. Also added in SIO and tweaked some timings/voltages in the new downloads. Glad to hear you have had good results thus far
linuxsociety said:
Same to all your projects pio_masaki! I always hit the "thanks" for you too buddy! BTW, the kernel you have been testing is the equivalent in the downloads section to the "default", you may want to take a stab at the "autogroup" kernel. I have been testing it with great responsiveness. Also added in SIO and tweaked some timings/voltages in the new downloads. Glad to hear you have had good results thus far
Click to expand...
Click to collapse
Yup I have every intention of banging that new kernel, waiting a minute while I build yet another CM10 for further testing of the autobrightness levels, added a couple more slots into the array, should have it nailed this time.
pio_masaki said:
Yup I have every intention of banging that new kernel, waiting a minute while I build yet another CM10 for further testing of the autobrightness levels, added a couple more slots into the array, should have it nailed this time.
Click to expand...
Click to collapse
Was really curious to see how BFS performed with Jelly Bean /ICS either one, but i've not had any luck with getting BFS to run stable so I removed it from my kernel tree for the time being. If i can get a full port to the grouper tree with all our device sources, I'm pretty confident I can get a newer revision of BFS to working. From most of my experience with other devices and other x86 systems though, the BFS doesn't out perform Autogroup anyway, but its mostly just curiosity that makes me want to go through all the trouble of getting it working with tegra2. On another note, I'm not sure why but regardless of the kernel or configuration I use Jelly Bean seems to have a weaker performance in any benchmark than the same kernel/configuration used in ICS. I'm yet to figure out where the bottleneck is in JB. (testing with linpack, quadrant, antutu benchmark all produce lower scores than with ICS) The thing that is most important to me is the actual user experience and feel that you get and not some benchmark score.. I can say that JB is very smooth and the scores don't mean nothing if you don't look at them!!
Awesome kernel! Seems stable enough, audio also works
sent from my A1/500 Iconia slab of awsomeness
Every time I download the zip file and try to flash it I get a Failed message. I am using TWRP to flash with.
tidewaterns said:
Every time I download the zip file and try to flash it I get a Failed message. I am using TWRP to flash with.
Click to expand...
Click to collapse
download it again
tidewaterns said:
Every time I download the zip file and try to flash it I get a Failed message. I am using TWRP to flash with.
Click to expand...
Click to collapse
In TWRP do you have MD5 verification enabled? If you do then it should work after you turn that off, the zip file is signed with SignAPK.jar so it should work without any issues. I have personally flashed both to my device using TWRP. If you are using adb through TWRP to push the .zip then you shouldn't be pushing it to /sdcard/ in recovery the proper location for internal storage is /data/media/ so if you have pushed it to /sdcard/ in adb then it will exist in a directory where permissions aren't accurate for the loader. Push with adb to /data/media if in recovery, or push to /sdcard/ if pushing with adb while your tablet is booted to Android OS.
If for some reason the .zip files are corrupted on github for other users please let me know and I will recompile, recompress, resign, and reupload.. Thanks
Fransis88 said:
download it again
Click to expand...
Click to collapse
Francis88: I assume the zip files flashed ok for you? Anyone else having problems?
Mine works fine. Flashed with twrp. Of course, I cleared dalvik before I flashed. The rebooted. Works fine.
sent from my A1/500 Iconia slab of awsomeness
I really don't like flashing from internal, and twrp, at least 2.1.1, says sdcard for whatever one is mounted. Keep that in mind when flashing in twrp. I think 2.2 says sdc instead. Also in jellybean it goes to storage/sdcard0 for internal sdcard1 for external sdcards. You can probably still use the old paths but those are the correct paths for jellybean.
Tapatalked from my Galaxy S II.
I copy everything to my SD card. You can flash from it.
Actually, I've only ever flashed from internal once, it was jb gapps
sent from my A1/500 Iconia slab of awsomeness
das_webos_transformer said:
I copy everything to my SD card. You can flash from it.
Actually, I've only ever flashed from internal once, it was jb gapps
sent from my A1/500 Iconia slab of awsomeness
Click to expand...
Click to collapse
Well I'm not saying you can't its more of a personal call to never store stuff I don't want to lose on internal, especially since it gets wiped when I wipe for testing.
Tapatalked from my Galaxy S II.
I think there may be some confusion when I say "internal" and "/sdcard" Assuming that one doesn't have an external sdcard, then /sdcard would be internal storage while in android OS (meaning ICS, Gingerbread, Honeycomb, Jellybean, etc), and that same path would be /data/media while in TWRP/CWM (Recovery mode). I've never had my external sdcard (removable one) to mount at /sdcard or /mnt/sdcard on my a100 so I assumed it was safe to recommend flashing from there as I have never had any issues with it, but like I mentioned in the previous post, /sdcard is only your internal user storage while booted into Android OS and not while in Recovery, while in Recovery the symlink doesn't exist so the right location is /data/media..
If anyone isn't familiar with the hierarchical file system and the mount points for their device, then I strongly encourage them NOT to use experimental ROMS, Kernels, etc. including this one. The kernel is a very critical part of the software on the device, and without a working kernel, you WILL NOT have a working device. So if something happens that you don't have the original kernel backed up and a way to flash it, or a full backup that you can access from recovery, then testing experimental kernels is like playing with fire..
A soft brick is highly possible if you obtain: A) the wrong kernel for your device B) a corrupted download kernel -OR - C) An experimental kernel that may be misconfigured or contain "bad" source code. << All of these can be repaired easily from recovery if you have a known good version to restore from, but if you have trouble flashing one kernel that is known to flash successfully for others, then what happens when you get the Fail message when trying to restore your working kernel/system??
Hope nobody takes this the wrong way, just trying to look out for people before things go bad. Good luck..
pio_masaki said:
Well I'm not saying you can't its more of a personal call to never store stuff I don't want to lose on internal, especially since it gets wiped when I wipe for testing.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I have never had to wipe the internal user storage AKA /data/media & /sdcard while testing any build, Of course it would be very easy to mess things up and accidentally wipe it from recovery, but I've never ran into any issues needing my internal SD wiped (so far).
Pio_masaki you could be talking about something else by internal storage though? Like /system or / or somewhere other than /data/media, /mnt/sdcard[0-] ?
linuxsociety said:
I have never had to wipe the internal user storage AKA /data/media & /sdcard while testing any build, Of course it would be very easy to mess things up and accidentally wipe it from recovery, but I've never ran into any issues needing my internal SD wiped (so far).
Pio_masaki you could be talking about something else by internal storage though? Like /system or / or somewhere other than /data/media, /mnt/sdcard[0-] ?
Click to expand...
Click to collapse
No I mean internal SD. I fully wipe /data including /data/media. Occasionally I dd zero them all too.
Tapatalked from my Galaxy S II.
linuxsociety said:
In TWRP do you have MD5 verification enabled? If you do then it should work after you turn that off, the zip file is signed with SignAPK.jar so it should work without any issues. I have personally flashed both to my device using TWRP. If you are using adb through TWRP to push the .zip then you shouldn't be pushing it to /sdcard/ in recovery the proper location for internal storage is /data/media/ so if you have pushed it to /sdcard/ in adb then it will exist in a directory where permissions aren't accurate for the loader. Push with adb to /data/media if in recovery, or push to /sdcard/ if pushing with adb while your tablet is booted to Android OS.
If for some reason the .zip files are corrupted on github for other users please let me know and I will recompile, recompress, resign, and reupload.. Thanks
Click to expand...
Click to collapse
I do not have MD5 verification enabled. Every time I try to flash it gets to the Verifying partition sizes then I get a failed in red on the screen.
tidewaterns said:
I do not have MD5 verification enabled. Every time I try to flash it gets to the Verifying partition sizes then I get a failed in red on the screen.
Click to expand...
Click to collapse
I would redownload, that's usually a cause if everything else is good. Any error message, like status 7?
Tapatalked from my Galaxy S II.
I finally got it installed and I overclocked it to 1504 mhz . Thanks for your help!
Sent from my A100 using xda premium
update: 10-dec-2013 Dmore-kernel-rev03-BM.Tar or CWM version with 367 MB available RAM
Why this GB Kernel for our old I9000 device ?
Answer: I still use this old device and i developed a new DMORE 3.6 ROM (link);
So I take some time for build this kernel and now i finally condivided with you; After a year with Cyanogen Jellybean, I turned back with GB: I re-love the amoled bright screen, the stock Samnsung Camera performances, but above all , the low battery drain !!!
Of course, Performances are not equal to a Galaxy S2 or a younger devices but for all people that do not have the possibility to change phone, this my work could help them !!
I merged Stratosk, Hardcore, Mialwe git's repositories and the last official Samsung GB Kernel release (GB_Update3) for all roms based on stock JW5/6/7/8/9/B firmware;
I continued thier hard work with my little knowledge and skill and now i condivided it with you.
NOTE: This Dmore Galaxy S-i9000 kernel can used as base with your ROMs if you like.
I personally tested it with different devices using also other kernels;
OVERVIEW – DMORE.Kernel#rev03 GingerBread GT-I9000 Galaxy S Device
- Based on latest GB Samsung base kernel (GT-I9000_Opensource_GB_Update3)
- compatible with all Samsung GT-I9000 GB ROMS (JW5/6/7/8/9/B based firmware)
- support for RFS and EXT4 partitions
- autoROOT, init.d support, su binary
- OverClock using script with recovery (1000MHz default – range 1300/1200/1.128/1000 Mhz)
- User Voltage control for CPU and Core
- backlightnotification (use*BLN Control), VoodooSound10 (use*VoodooControl)
- some tweaks, Useless debugging removed.
- for ADB users: adb shell remount
- All stock features are supported
- Tweaked ramdisk: optimized mount options & VM settings
- Compiled with last Linaro gcc 4.7.4 toolchain optimized by Christopher83, flags opt (-O3)
- I/O scheduler SIO / BFQ / Deadline / NOOP (default*SIO)
- Read ahead tweaks (512Kb cache)
- CPU governor tweaks:Governors – SmartassV2 (default), Ondemand, Smoove
- Kernel compression mode GZIP
- ARM RWSEM optimization*
- Added optimized CRC32,AES,SHA1 algorithms*
- CWM v5.0.2.7 Semaphore Recovery
- 364 MB - 367 MB available RAM (download Dmore.Kernel-revxx-BM version for 367 Mb)
- Reworked cpufreq driver. cpu states 100-200-400-800-1000/1128/1200/1300.
- automatic cleaning of old "su" binary and busybox (if you coming from Semaphore or Chainfire)
- busybox 1.20.2r2 linusyang
- hardcore gamma and RGB profile
DEFAULTS
CPU 1000Ghz by default, SmartassV2, SIO 512Kb .
For change IO Scheduler, Cpu Gevernor and for manage OC/UV use System Tuner app from PlayStore
https://play.google.com/store/apps/details?id=ccc71.pmw&hl=en
INSTALL
(Dmore-Kernel-RevXX-CWM.zip for installation with ClockWorkMode or DMore-Kernel-RevXX.zip Odin/Heimdall)
Flash from recovery using CWM files or flash extracted zImage using*Heimdall*or flash downloaded TAR archive with Odin*
For change Cpu Freqency clock simply install DMore-Kernel-CPUXXXX.zip (XXXX = 1000,1128,1200,1300)
Personally i use 1200MHZ like Freq CPU
Tips & Tricks:
If you want change the Cpu Frequency manually, you can also using Adb shell commands instead DMore-Kernel-CPUXXXX.zip CWM file.
Simply type this commands on a DOS/Linux terminal shell
adb shell
su
mount –o remount, rw /system
echo 0 > /system/dmore-cpufreq.conf #cpu= 1000Mhz
reboot
(for clocks CPU 1128,1200,1300 use echo 1, echo 2, echo 3
echo 1 > /system/dmore-cpufreq.conf #cpu= 1128Mhz
echo 2 > /system/dmore-cpufreq.conf #cpu= 1200Mhz
echo 3 > /system/dmore-cpufreq.conf #cpu= 1300Mhz )
DOWNLOAD (changelog @ post #2)
Link here: http://goo.im/devs/dmore/gt-i9000/gb-i9000-kernel
SOURCES
Github repository: https://github.com/dmore70/kernel-GB-I9000
THANKS
Big thanks devlopers and especially*mailwe(midnight kernel), stratosk(Semaphore Kernel),*hardcore (SpeedMod Kernel) ,*supercurio*(Voodoo),*neldar*(BLN) and everybody else developing Open Source software, helping or reporting, Christopher83 for optimizated Linaro *cross compiler toolchains suitable for Samsung S Phone.
NOTE: next week , monday i'll published the new GB DMORE.ROM
10-dec-2013 Added more free available RAM (367 MB) ----> download DMore.Kernel-rev03-BM
Amazing, an updated GB kernel has been needed for so long. Can't wait to try new rom. Well done
Sent from my LG-E975 using XDA Premium 4 mobile app
A captivate version, pls
Welcome back David, I've used your old DMORE GB ROMs & they were really good! It is amazing that there are still devs out there which believe in good old GB for a good old phone!
Thank you & cheers!
Thank fron kernel friend
Well done David! :laugh:
Waiting for Your new Rom.
Cool , a new GB Kernel.
A few weeks ago, me and Fishears was having this discussion about how nice it would be to have a new updated GB kernel.
You just provided a solution.
This kernel is based on JWB kernel source right ?
Also , if you have the source on github, I would like to tweak some governors for the best performance, I used this setup when running GB.
nchc said:
Amazing, an updated GB kernel has been needed for so long. Can't wait to try new rom. Well done
Sent from my LG-E975 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For all people don't want wait until tomorrow for the tread ,following link where you can download the new DMORE3.6 ROMs + others useful my addons:silly: (simply install with CWM recovery)
Link: http://goo.im/devs/dmore/gt-i9000/DMORE3.6-NewRom
HoangTuBot said:
A captivate version, pls
Click to expand...
Click to collapse
Sorry , I have only Galaxy S devices in my hands
ts1506 said:
Cool , a new GB Kernel.
A few weeks ago, me and Fishears was having this discussion about how nice it would be to have a new updated GB kernel.
You just provided a solution.
This kernel based on JWB kernel source right ?
Also , if you have the source on github, I would like to tweak some governors for the best performance, I used this setup when running GB.
Click to expand...
Click to collapse
Yes kernel is based JW9-JWB kernel source; In this moment i'm uploading git repository;
Link here: https://github.com/dmore70/kernel-GB-I9000
I'm working for a new cpu-freq.c module where there are 5 different frequencies level (100-200-400-800-1000-1200MHZ) coming from CM10.1 github repository. Dmore-kernel rev03 use 4 different levels (stratosk kernel) , so it uses a higher battery drain; Actually I have a problem with /sys/devices/system/cpu/ directory governor interface , but i hope to solve it in the next days.
can i flash this over CM7 baseband i9000XXJVU
pryerlee said:
can i flash this over CM7 baseband i9000XXJVU
Click to expand...
Click to collapse
NO You can't
If you add fast charge support I'll kiss you
fishears said:
If you add fast charge support I'll kiss you
Click to expand...
Click to collapse
Ok I'll not add fast charge support :laugh::laugh: so you'll not kiss me.
The problem is only to have a little bit of free time for this my hobbies.
In any case if you suggest me some link where i can have more informations, I might try :silly:
davidmore said:
\
Sorry , I have only Galaxy S devices in my hands
\
Click to expand...
Click to collapse
I can be your tester
nice, I'm using Saurom right now, so this kernel will fit perfectly
How do I flash this with Odin? I don't see any .tar files in the download page
MIUI
I wish you could make a MIUI Gingerbread version or even better teach me how to do it my self
Could you made another version of your kernel with bigmem like in semaphore? (384.5MB - breaks 720p video recording, front camera pictures) I used to use this, when I was on GB.
midnight911 said:
Could you made another version of your kernel with bigmem like in semaphore? (384.5MB - breaks 720p video recording, front camera pictures) I used to use this, when I was on GB.
Click to expand...
Click to collapse
Added DMore.Kernel-rev03-BM.tar or CWM file
Here's Bigman(377MB - breaks 720p)
Here's more 3MB (364+3 = 367MB) - 720p video recording works
For 384 Mb i 'm searching on web the mach-aries.c good module
Ok... I've flashed this - DMore-Kernel-rev03-BM.tar - after reverting to stock rom from CM11 and now I am stuck in a bootloop... Any ideas?
LE: I reverted back to stock with Odin following this guide:
Step 1: Start Odin
Step 2:
a. Select PIT file as 's1_odin_20100513.pit'?
b. Select PDA file as 'PDA_DXJV9_Deodexed_Zipaligned.tar'?
c. Select PHONE file as 'PHONE_DXJV9.tar'?
d. Select CSC file as 'CSC_OLBJV9.tar'?
Step 3: Under Options: Check Re-partition, Check Auto Reboot and Check F. Reset Time
Step 4: Start the phone in the download mode
Step 5: Once ID:COM/phone is 'Added!!' click Start
Step 6: You will see a lot of red text after the flash is done, don't panic, just do a 'wipe data/factory reset' and reboot the device when done.
Step 7: Let the device boot all the way then turn it off.
Step 8: Re-enter Download Mode and re-flash only the CSC file [Step 2 d] without pit and without re-partition.
I had the files on my computer from previous revert. If anyone has the same issue and has trouble downloading all the files, just let me know.
Now, being back on stock I really want to try your KERNEL. Should I make sure of any steps before attempting to flash it with Odin as PDA? Thanks!
Hey Everyone,
I'm by no means a pro at kernel building but I've put lots of effort into these kernels so I thought I'd share them with you. The Uber kernel will always be updated to the latest Kernel version and will be overclocked to 1890 MHz or 1998 GHz (2 GHz) you decide which option you are willing to do. Unlike some of the other T-mobile Galaxy S II Hercules developers out there, I actually have a Galaxy S II and plan on having it until Summer 2014. This means that EVERY KERNEL I POST HAS BEEN TESTED AND IS WORKING although it might not be perfect (few things in life ever are).
Even though I don't post anything unless it works I still don't want to be liable for user errors. In other words, if you flash one of these Kernels your warranty is void and I AM NOT RESPONSIBLE for any data loss or bricked devices etc. A Clean install is ALWAYS recommended. That does not necessarily mean you can't install these kernels on you current build it just means that you might have problems if you do. Recently apps have been getting corrupted for whatever reason whether on Stock or AOSP and in most cases they cause RRs and SODs. If you find yourself in one of those situations a clean install is the easiest fix. If you want to try and save you apps then connect to you phone while in recovery using adb. Then type adb shell. Now once you are in that shell you can run this command to fix your apps "e2fsck -yfDC0 /dev/block/mmcblk0p25" it could take anywhere from a few minutes to an hour depending on the state of your apps.
[AOSP 4.4.x UBER KERNEL LINK]
UBER 4.1 - 1.89 GHz RELEASE for AOSP 4.4 KitKat
UBER 4.1 - 2 GHz RELEASE for AOSP 4.4 KitKat
All old Kernels can be found on Dev Host via this link (be careful you read file names and descriptions carefully if you choose to take a peek around) http://d-h.st/users/Cl3Kener/
Installation Instructions
**** IMPORTANT!!! USE TWRP 2.6.1.0+ for 4.4 kernels!!! Failure to do so may result in bootloops due to changes made to TWRP to accommodate SELinux in 4.4 ROMs (Links include flashable TWRP installation zips credits to meekrawb. Just flash them in your current recovery! ) ****
1. For best results a install these kernel after a fresh ROM install (although it still should work if you don't do that)
2. Reboot into recovery (MAKE SURE YOU USE THE RIGHT ONE!!! (See red print above))
3. Flash Kernel Zip
4. Reboot and let Settle for ~10 minutes
5. Install Trickster MOD from the App Store for access to all of the options.
6. Change the settings to something other than INTERACTIVE (Especially if you run it with BFQ it will give you the worst screen lag ever). Then enable "Set at Boot" and push the check mark button at the top right hand portion of the screen or else you will lose your configurations.
7. Enjoy!!!
Error Reporting
I am always open to hearing about your errors although just telling me something went wrong without giving me details does me absolutely no good. So here are my expectations if you do want to complain about something not working:
1. Please list the ROM you are using,
2. The IO scheduler you were using
3. The CPU governor you were using
4. The CPU frequency range (192/1080 etc)
5. What you have done to attempt to fix it.
6. If you were able to simulate it again using the same settings.
7. Anything else you think is applicable to the issue
I would also hope that you would consider trying some of the following things to fix your issue before you ever report it because most of these things will fix the problem without me even having to change a thing.
1) Fix file permissions using a program that does a thorough job. I recommend using the fix file permissions in ROM manager because it is the best I’ve seen. For the record, I don’t actually use ROM manager for anything other than fixing permissions. Please consider trying this first because it tends to fix most of the FC/RR/SOD errors you might have.
2) Make a backup and install a clean version of the ROM you are running and see if you are still experiencing those same errors. You may have corrupted files if you’ve been dirty flashing.
3) If that doesn’t solve it, redownload and reflash, maybe something got corrupted but it still managed to flash. This happens sometimes and I can cause you grief.
4) For advanced users pull a logcat. I know not everyone knows how to do this but you can learn if you check out this OP or other ones like it
SPECIAL THANKS TO:
Android88 - because he is awesome and encouraged me to create this thread!
Samsung - for the source code to build these Kernel (and for making the phone)
Ayysir - for his wonderful tutorial on making a bash script to build kernels and for helping me out all of the time with everything!
Elbermu - For Bringing Thermal and Sweep2Wake to Hercules and for the help!
Bmg002 - For his extensive work fixing/rewriting my init.d scripts
Gruntparty - For completely redoing/fixing the build.prop injector I use for my AOSP Kernels
I Am The Frost - For being my first and best tester on xda. He's debugged several issues in these kernels for me
UBER Kernel Repositories can be found at https://github.com/Cl3Kener/HERC-KERNELS and are properly labeled for your convenience (see the branches)
Informational Links
Here is a fantastic guide on "Innards" of Kernels
Optimizing Linaro Keychains
Building a Bash Script to make Kernels
JOIN MY GOOGLE COMMUNITY IF YOU WANT INSTANT UPDATES ON ANY OF ANDROID STUFF I DO.
Reserved!
XDA:DevDB Information
[KERNEL][AOSP 4.4.x][2GHz/1.89 GHz] UBER 4.1 | LINARO 4.7.4, a Kernel for the T-Mobile Samsung Galaxy S II
Contributors
Cl3Kener
Kernel Special Features:
Version Information
Status: Beta
Created 2013-12-02
Last Updated 2014-01-30
Changelogs
Changelogs
Changelog UBER 4.1 Release
- ONLY FOR ANDROID 4.4.2 CM 12/16 Nightlies and beyond!!!!
- Kernel Version 3.0.101 - Linaro 4.7.4 2013.12
- USB fastcharge
- MORE TCP Options "Veno as default
- Fsync toggle - disable for better performance but beware that if your phone crashes you will lose data.
- Overclocked CPU 1890 or 2GHz/ GPU 3D = 320 2D = 266
- IO Schedulers - cfq, bfq, row, noop, deadline, sio, vr, FIFO, and zen
- CPU Governors - intellidemand, interactivex, lazy, wheatley, smartass, badass, lionheart, minmax, fantasy, savagedzen, scary, HYPER and samsung.
- Frandom Lag Reducer
- Smaller sized kernel due to xz compression.
- CPU link - elbermu
- Sweep2wake - thanks dennis rassmann (@show-p1984) for his awesome code and elbermu for modifying it to fit this device!
- Thermal - thanks once again to dennis rassmann (@show-p1984) for his awesome code and elbermu for modifying it to fit this device!
- IO Booster
- CPU Power - Vincent Guittot
- Frontswap Support
- Google "Snappy" compression/decompression
- KGSL GPU Control - carvsdriver
Additional Info
Terminal commands to enable/change a kernel features if you are don't like kernel tuning apps
Fsync
To enable - echo 1 > /sys/module/sync/parameters/fsync_enabled
To disable - echo 0 > /sys/module/sync/parameters/fsync_enabled
USB Fast Charge
To enable - echo 1 > /sys/kernel/fast_charge/force_fast_charge
To disable - echo 0 > /sys/kernel/fast_charge/force_fast_charge
Set Thermal Values
Go to /sys/kernel/msm_thermal/conf/ in a root file browser and change the values
Set MPDecision Values
Go to /sys/kernel/msm_mpdecision/conf/ in root file browser and change the values
Disable CPU Link
echo 0 > /sys/kernel/cpu_gov_sync/force_cpu_gov_sync
Recommended CPU Govs by Category
For Performance
Performance Governor - Full OC
HYPER - full oc
Lionheart - full oc
For good battery life with decent performance use
Intellidemand
Interactivex
Ondemand
Samsung
Lazy
Moderately Conservative
Badass
Conservative
Wheatley (debatable could be in the above category)
Very Conservative
Powersave
SavageZen
not sufficient info? checkout out this op
Sweet! New kernel!
Sent from my SGH-M919 using Tapatalk
Sweet! Will try this out right now :good:
Flashed beautifully thanks @CI3kener
Sent from my SAMSUNG-SGH-T989 using Tapatalk
gotta love the uber, thank you kener
Sent from my SAMSUNG-SGH-T989
Thank You !
Will this work on alpha 3??
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
JNMM said:
Will this work on alpha 3??
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Yes ?
Sent from my SAMSUNG-SGH-T989 using Tapatalk
3 New Performance Boosters
Hey Everyone,
For those of you who haven't heard I've been using "Koding" as my new kernel build server. Space is very limited with my free account but if you'd like you can click here and signup to help me get more free space. You'll also find that you can learn how to code just about anything (java, html5, php, to name a few). Many developers and adding tutorials and sharing their projects so if you are interested in that stuff make sure to sign up!
I've made two nightlies this morning which need testing. For those of you who were around for my 4.3 you might recall that somewhere along the line there was suddenly a curious SD Card Mounting/Unmounting that would happen after unlocking the phone. I had made so many commits in such a short time frame that I was unsure which one caused the error. I've gone back and added my top three performance improving commits from the questionable series to see if any of these three commits caused the error (I certainly hope they did not, I really hope it was caused by the LZ4 compression and not the performance boosters). Let me know if you see any problems as you use these nightly kernels!!! Remember these are for 4.4 ONLY!!!
Here are the links!
UBER 1.89 GHz
UBER 2 GHz
Cheers!
Cl3Kener
just to let you know i have not been getting the sd card error on the 4.4 uber
Signed up on Koding maybe you can teach me a thing of two (^o^)
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Confirmed working on almites cm build
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
BETA2 For 12/16 CM Nightlies and Beyond
Hey Everyone!
Well Team Chopsticks finally got video working although from what I can tell all of the work was actually all done by our very own @bryan2894 who went and found the patches that fixed the video!!! Great work @bryan2894!!! Part of this video fix included the kernel so here is an updated kernel with the patch needed. This kernel will only have fixed video on CM 12/16 nightlies and beyond. I bet it might work with earlier but you might as well update if you are a CM user so what's the point?
Anyhow, enjoy the updates!
Cheers!
Cl3Kener
PS since I know someone will ask, This actually does work great with the 12-14 HellKat build since it also has working video because we grabbed the patches from CM before they were merged.
Sent from my SAMSUNG-SGH-T989
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
syan8182 said:
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
Click to expand...
Click to collapse
That stuff is nonsense. The latest TWRP in fact is much better for this phone and flashing this or any other ROM here IMHO. I tested both CWM and TWRP on more than one occasion and results were identical. For me TWRP is also much easier to get into when you have an issue with a new ROM booting and you need to get into recovery via the power & volume up buttons.
syan8182 said:
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
Click to expand...
Click to collapse
I've flashed CM11 (my builds) about 10 times in the last month and have been using TWRP 2.6.1.0 since Sept. without issue.
Just don't try to flash TWRP from within GooManager, either flash from recovery or use Odin (best).
Since the video recording is working now I moved to CM11 using the @Almite (Rom) and @Cl3Kener (Uber 2GHz kernel) and I can tel you this is solid Rock combination in performance and stability even those are still in Nightlies/Beta so thank you all for this amazing team work...
Is it possible to add the BLN notification (I know some don't like it but usually this the feature can be disabled)
Thanks
I want to create a thread about settings for every custom kernels on our S3 NEO with Lollipop Stock and CM11, CM12, stock 4.4.2 and 4.4.4 ROM.
If You are advanced or expert in the subject of krenels, parameters and features put to this thread Your settings.
This thread, I thnik, helps novice in search for the best settings to be the rom fast, stable and smooth.
So, please placing here and debate on settings the kernels.
Maybe for a CM11, CM12, CM12.1, CM13, stock 4.4.2 and 4.4.4 also 5.0.1 this settings works well, too.
Try and tell us
The Poll is only for stock TW 5.1.1 ROMs.
Thanks for Devs who made the kernels for S3 NEO:
- @sev3n1985
- @Renix63
- @LGaljo
- @nikita36078
- @oranaise2412
- if I forgot about someone - tell me.
Thanks to @gsstudios for giude about governors and I/O shedulers.
Thanks to Mike Barrett for video about Kernel Adiutor settings.
DELETED
Important - only for custom kernels
The phone must be rooted.
1. Before flash any new kernel do backup your rom, boot, recovery, preload and data ex. via recovery.
2. After flash the new kernel always do wipe cache and dalvik cache in recovery and next restart the phone. (restarts takes about 5min)
3. CPU frequencis and governours are important things in rom's speed.
4. CPU freq at 1593MHz may destabilized your phone - heating problem and sometimes random reboots.
5. If You want to OC CPU - have to turn off MPDecision Hotplug and select another one or nothing (MPD may do CPU freq not stable - is always good for only stock frequencis so from (192) 300 to 1401MHz).
6. Sometimes the new kernels have to root again via flash superSU update via recovery ex. like eMotion kernel.
7. Try any changes - don't be afraid - kernel not bite If so go wrong - always have backup
Good luck.
If anyone have another advices - feel free....
The difference between kernels with zRam and zSwap options:
- zRam is a kernel with virtual memory in Internal Memory your phone (compressed) for most users
- zSwap is a kernel for the SD card with swap partition for our phone ex. 512 or 1024 Mb, so if You have not swap partition in Your SD card - do not flash this kernel (no good resoults).
Heating and random reboots problem
This dependent of frequensic CPU and if is it so CPU max freq probably is set at 1593MHz.
If we to much OC our CPU's then our phones may have some lags and freezes or reboots (after call or in camera app).
So if you have this symptoms then you have to set CPU OC max to 1401MHz or 1497MHz.
If it no helps so maybe the kernel is wrong compiled with bad linux settings - and only change the kernel for another one.
Guide for CPU governors and I/O shedulers and others settings in Kernel Adiutor
Please read THIS - big thanks to @gsstudios for this gov guide.
Please watch THIS - thx to Mike Barrett for video about settings in Kernel Adiutor.
It's a good guides for everyone.
Only my conclusions
From my experience with OC CPU and use different kernels (in stock and CM series ROMs) the stable max freq CPU is at 1497MHz.
If You want better battery life select max CPU at 1401MHz or even 1300MHz - 1190MHz.
For better battery life You can try :
- Multicore Power Saving - ON
- CPU gov at Ondemand, Intelidemand, arteractive, inteliactive (without frequent lags)
- GPU gov set at conservative (in new Renix kernel) or msm-adreno-tz
- if you only listen to music then set Max Cores Screen Off at 1 CPU and max freq at 600 - 700 MHz - for media player is enaugh.
- Power Suspend Mode at LCD Panel or Hybrid.
My steps for install all things like rom, fixes, xposed, kernels, ect. :
1. Wipe system, data, cache and dalvik cache - no restart the phone
2. Flash any ROM - no restart the phone
3. Wipe cache and dalvik cache then restart the phone
4. Flash possibly another kernel ex. Renix's, eMotion's... I do it in this step 'couse sometimes after that We have to install ex. camera fix - again in Renix kernel or superSU in eMotion kernel
5. Flash any fix for the point ROM (like RIL, key fix, mixer fix, camera fix... others) then restart the phone
6. Flash superSU (if the rom has not rooted) and possibly busybox for advanced (change build.prop in Kernel Adiutor for example) then restart the phone next go into superSU ( the app install binary) next do settings and out - the same with busybox (have to install libs)
7. Install the xposed app next go to the recovery and flash xposed sdk22(Lollipop) (23 for MM) ex. v85 by wanam, next wipe cache and dalvik cache and restart the phone
8. That's all - in my phone works good, I did and do it by 2-3 years and no problem.
Remember - after wipe cache and dalvik cache the phone's booting time will take a 5-7min.
Thanks for this thread! ^-^
I think I'll post my stats too! I got a perfect balanced mix with 3.5 renix. But for now I wanted to try the new one with boeffla kernel sources ^-^
DELETED
DELETED
Nalas Thank you for the effort..Random restart problem issue ?.. Sory my english is poor
DELETED
nalas said:
Hello.
If you set CPU at 1497MHz or lower so no random reboots in I9301I.
I don't know how it look in I9300I.
So if someone can write abaut it so will be nice....
Click to expand...
Click to collapse
My device I9301Q..I try report the results
do you use xposed,grenify,powernap ?
DELETED
Make the explanations about kernel adiutor options plz. Ty
DELETED
Nalas no random reboots no lags and very very smoth my device thank you bro .
DELETED
DELETED
nalas said:
I'm happy to helped You bro.
What configaration You have ? at 1497MHz (pics) or 1305MHz (video) ? and what's kernel ?
It will be clarity for others.
If You can - edit Your post about above.. ? thx man.
Nice if it works in another phone
Greets
Click to expand...
Click to collapse
Device : I9301Q
Rom : Motion Rom 17.0
Kernel : Renix 3.7 zram
App : Kernel Adiutor Mod v9
Governor : Smartmax Maks 1305 Mhz,Multi core power saver disable wake up boost and hotplug boost disable
Hotplug : Msm hotplug not use Lazy hotplug
Gpu : Conservative and disable simple gpu,Adreno idler
Battery : Fast usb charge enable
I/o : İnternal fiops and 256 kb..External tripndroid 2048 kb
Ksm : Enable
Virtual Memory : Enable, Zram 100 mb
İnit d : Enable 99zram
Not use greenify,powernap..Damaging the system..Continuously restarts system
I have a I9301I and use Motion ROM 17.0 with eMotion kernel. Motion ROM 'as is' gave me frequent random reboots, so I tried Renix63 kernel. V2.0 fixed the random reboots, but LED lights stopped working. Later versions fixed this but introduced the problem of the phone freezing when responding to notifications and occasionally switched off the phone completely. I then tried eMotion ROM from sev3n1985. LEDs work, no random reboots, no freezes, no switch offs. It just works. nalas's second post in this thread has 20 screenshots of recommended tweaks to the Renix63 kernel. I prefer something that works out of the box.
nalas said:
4. CPU freq at 1593MHz may desabilized your phone - heating problem and sometimes random reboots.
5. If You want to OC CPU - have to turn off MPDecision Hotplug and select another one or nothing (MPD may do CPU freq not stable - is always good for only stock frequencis so from 300 to 1401MHz).
Heating and random reboots problem
This dependent of frequensic CPU and if is it so CPU max freq probably is set at 1593MHz.
If we to much OC our CPU's then our phones may have some lags and freezes or reboots (after call or in camera app).
So if you have this symptoms then you have to set CPU OC max to 1401MHz or 1497MHz.
From my experience with OC CPU and use different kernels (in stock and CM series ROMs) the stable max freq CPU is at 1497MHz.
If You want better battery life select max CPU at 1401MHz or even 1300MHz - 1344MHz.
Click to expand...
Click to collapse
With all due respect to nalas and Renix63 I don't understand the logic of producing a kernel that's overclocked to 1593MHz which then has to be reduced to 1401/1497 via Kernel Adiutor in order to prevent freezes or reboots.
Other users have had different experiences, so there there may be other factors to consider - variances in hardware, apps etc. - this is just my experience.
Apart from that - huge props to the devs here. If it were not for them I'd still be running TW 4.4.2.
Corbynista
DELETED
DELETED
I tested Ciro's rom but It was buggy for me (dialer does not appear but the phone call was running)
WiFi not working
SIM not working
I will try Motion Rom.
Cheers
Welcome To NegaLite HW+ Kernel!!!
I AM NOT RESPONSIBLE FOR ANY DAMAGES! Use At Your Own Risk!
This Also Voids Your Warranty!
Features:
F2FS Support(Module) - Big Thanks To r3pwn
GCC Uber 4.9.4 Toolchain
-o3 Optimized
Turbo 4x Zram(Module)
msm_hotplug
All Governors Boosted
CPU OC Up To 1.3 Ghz
GPU OC Up To 533MHz
FSB UC To 320MHz
Undervolted - 25mv Lower
All Cores Active
init.d Support
Configurable Tweak Scripts
Sysctl Tweaks
Memory Tweaks
Build.prop Tweaks
Busybox 1.27.0 Included
ADB Debugging Auto Enabled
Auto-Root Included
Kernel Adiutor 4 Wear App Included
Scripts Included In Source For Simple Compiling(Build The Kernel Yourself If You Want)
Custom Governors:
Darkness, Intelliactive, Intellidemand, InteractiveX, PegasusQ, Smartmax, ThunderX
Custom Schedulers:
VR, SIO, FIOPS, FIFO And ZEN
------------------------------------------------------------------------------------------------------------------------------
Downloads:
Nothing Needs To Be Done Prior To Flashing!!!
Just Do This:
1. Push Zip To /sdcard/ Via ADB
2. Flash zip In Recovery
3. Done (Enjoy!)
WEAR 1.5(Marshmallow)
negalite_kernel_HW_7eca452-1.5.zip - 1/12/2017
WEAR 2.0(Nougat) - Official Release Compatible
negalite_kernel_HW_dffc4c0-2.0.zip - 6/7/2017
Commit Log:
https://github.com/Negamann303/Huawei-W-1.5-2.0/commits/master
------------------------------------------------------------------------------------------------------------------------------
Source: Huawei-W-1.5-2.0
Boot Battery/Performance!!!
Advanced Users: (Optional)
You Can Have Pre-Configured Settings On Kernel Flash
Download One Of The Zips Below
Rename To bootperf.zip
Push To Your SDcard
Flash The Latest Kernel
Enjoy!
Nega's Tweaks:
battery_v6_bootperf.zip - Battery Save - 8/03/2016
performance_v6_bootperf.zip - Performance(See What This BadBoy Can Do!) - 8/03/2016
PablosMule_bootperf.zip - Pablo71 Has You Covered, Make Sure To Thank Him!
On The Fly Config Switching
Push bootperf.zip And The Flasher.zip Below To SDCard And Use Flasher In Recovery
BootPerf_Flasher.zip
Download link doesn't seem to be working...
bmg1001 said:
Download link doesn't seem to be working...
Click to expand...
Click to collapse
Fixed, thanks
Thanks for your efforts. Link is broken bro.
Huawei-Watch-3.10-mr1 is it lollipop-wear-release-1?
janjan said:
Thanks for your efforts. Link is broken bro.
Huawei-Watch-3.10-mr1 is it lollipop-wear-release-1?
Click to expand...
Click to collapse
It should be fixed. This kernel is for Marshmallow
This seems interesting. Could you explain how I move .zip files to and from Wear?
I'm rooted with TWRP on wear, but got no USB mount. How do I then move the files?
Thanks in advance
---------- Post added at 08:57 AM ---------- Previous post was at 08:32 AM ----------
Trying the pull command, but saying it's read only
Faspaiso said:
This seems interesting. Could you explain how I move .zip files to and from Wear?
I'm rooted with TWRP on wear, but got no USB mount. How do I then move the files?
Thanks in advance
---------- Post added at 08:57 AM ---------- Previous post was at 08:32 AM ----------
Trying the pull command, but saying it's read only
Click to expand...
Click to collapse
Worked here. This is the exact command I used: adb push C:\Users\bmg10\Downloads\negalite_kernel_HW_r99c9f93.zip /sdcard/
Did you set TWRP to allow system modifications?
bmg1001 said:
Worked here. This is the exact command I used: adb push C:\Users\bmg10\Downloads\negalite_kernel_HW_r99c9f93.zip /sdcard/
Did you set TWRP to allow system modifications?
Click to expand...
Click to collapse
Was just pushing from standard ADB. Not in TWRP. Suddenly it worked. But thanks
I currently run skin1980's MM kernel ... can I just flash this over it out should I wipe everything? thanks this looks awesome
pablo71 said:
I currently run skin1980's MM kernel ... can I just flash this over it out should I wipe everything? thanks this looks awesome
Click to expand...
Click to collapse
No prerequisites, just flash
Sent from my SM-G935P using Tapatalk
negamann303 said:
No prerequisites, just flash
Click to expand...
Click to collapse
awesome ... zip file loaded to sdcard and rebooting to recovery to flash here we go ... thanks
So far so good! Watch is running really fast and smooth and battery seems to be a bit better than what I got on Skin's kernel, but that might also be cause I factory reset my device when I flashed the kernel (since I was running Skin's kernel before). No issues like random reboots or crashes either. I haven't modified any kernel settings yet though.
Holy sh!t
Thanks!
This is the smoothest experience I have had on this watch so far and I've used all of the things!
loving this kernel to a high degree so far ... it was damn thoughtful of you to include kernel adiutor and make it flashable in recovery. the selection of governors, hotplug profiles and i/o schedulers is top notch (I'm no expert on these matters though I know just a small amount)
Early observations: on your stock settings both my watches don't like waking up on tilt to wake, they usually require a double-tilt to wake up and one watch even locked up and required a reboot BUT adjusting some settings fixed this instantly. I point out though that I did not do a factory reset or wipe any partitions or caches before installing this kernel. I just flashed and started having fun.
currently I'm getting VERY satisfactory performance with the cpu's frequency locked at 787mhz + interactiveX governor + intelliplug's eco-conservative profile + gpu freq max 320mhz with powersave governor + row i/o scheduler with 1024kb read ahead
so far this kernel is badass
pablo71 said:
loving this kernel to a high degree so far ...
Click to expand...
Click to collapse
I was wondering if all the Wear Shell and Tasker commands worked, sine I did not see that it was rooted. Thanks.
With the zram, should we see a reported higher amount of total ram available? What are others seeing?
Sent from my LG-D800 using Tapatalk
Sweet kernel need this for Android Wear 2.0 please dev
pmgnet said:
With the zram, should we see a reported higher amount of total ram available? What are others seeing?
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Thanks for making me realize zram wasn't enabled, will be in the next release tonight
eduardozeassesme said:
Sweet kernel need this for Android Wear 2.0 please dev
Click to expand...
Click to collapse
Once wear 2.0 is released, I will move up
Sent from my SM-G935P using Tapatalk
pablo71 said:
loving this kernel to a high degree so far ... it was damn thoughtful of you to include kernel adiutor and make it flashable in recovery. the selection of governors, hotplug profiles and i/o schedulers is top notch (I'm no expert on these matters though I know just a small amount)
Early observations: on your stock settings both my watches don't like waking up on tilt to wake, they usually require a double-tilt to wake up and one watch even locked up and required a reboot BUT adjusting some settings fixed this instantly. I point out though that I did not do a factory reset or wipe any partitions or caches before installing this kernel. I just flashed and started having fun.
currently I'm getting VERY satisfactory performance with the cpu's frequency locked at 787mhz + interactiveX governor + intelliplug's eco-conservative profile + gpu freq max 320mhz with powersave governor + row i/o scheduler with 1024kb read ahead
so far this kernel is badass
Click to expand...
Click to collapse
How can you get your watch rooted? I tried flash some supersu for wear but I cannot start the kernel adiutor.