Related
Hi fellows!
As some of you have seen in Humberto's P1000L/N Gingerbread thread, I'm building a Gingerbread kernel for these devices.
At the beginning, I thought that I'll just port the Overcome kernel to ours devices and I'll never touch on these files again.
But it turns out that it shouldn't be like that. So, to avoid mess with Humberto's thread, I decided to begin a new one.
Here are the current features of my Kernel, which was initially based on Overcome v3.3.1 kernel:
Main Features of latest stable version (20111029)
Kernel 2.6.35.14
Lagfree governor
Smoothass governor
SmartassV2 governor
BFQ IO scheduler version 2 (revision 1)
Conservative, Ondemand, Performance, Powersave, and Userspace governors from 3.1 kernel tree
Built with 2011.03 toolchain
TV SUPPORT (P1000L only)! (it is available if you flash the recently leaked P1000L gingerbread version: http://forum.xda-developers.com/showpost.php?p=17993125&postcount=355)
10-points multitouch driver
File Systems support: RFS/EXT{2,3,4}
Overclock (@1.6GHz) with these steps: 1.6ghz, 1.5ghz, 1.4ghz, 1.3ghz, 1.2ghz, 1ghz, 800mhz, 600mhz, 400mhz, 200mhz, 100mhz
Undervoltage
Touchscreen Undervolted (from 3.3V to 2.1V)
RAM Undervolted (1.8V to 1.7V)
ADC Unvervolted (3.3V to 3.0V)
Voodoo Sound v10
Built in CIFS/TUN/SlowWork support
Stochastic Fair Blue (SFB) Network Scheduler
V(R) Schedule, but SIO set as default.
Autogroup Scheduler
Asynchronous I/O Enabled (AIO)
Backlight Notifications
Humberos' Initramfs 20111102
Features that needed to be test (I'll appreciate any help):
BLN has problems
I'll appreciate any help or feedback!!
Link for download the latest stable version:
http://www.mediafire.com/?9ug8n71vgc5ik7u
md5sum zImage
0fce8943c0b950c05e0d5163cf662460 zImage
Source code:
https://github.com/ronisbr/GT-P1000LN-GB-Kernel
I would like to thanks:
The Overcome project
jdkoreclipse
koxudaxi
Humberos
Thanks,
Ronan
Changelog
20111105 UNSTABLE (http://www.mediafire.com/?13g5330zs209qn1)
md5sum zImage
21248e6f24a54a99947b248c33cad7b2 zImage
This is an UNSTABLE kernel, and we are expecting some functionality breakage! Again, some patches that I applied hasn't been tested in any other GT kernel yet...
Use tiny-shmem instead of full shmem implementation
Tiny shmem is an alternative implementation of shmem filesystem that uses RAMFS code instead TMPFS. It should be suitable for small system which doesn't have swap and doesn't need the advanced features that the full implementation has, e.g. the size limit control. By removing these unnecessary features, tiny-shmem should increase the performance.
For Galaxy TAB, swap isn't used and size limit isn't a necessary feature, so tiny-shmem should work well.
But it is just my guess! I really need help to test it...
Many performance tweaks in low killer memory
It should make memory manager better.
Enable CPU-supported unaligned access
Enable the option CONFIG_ALLOW_CPU_ALIGNMENT, since the Galaxy Tab P1000 has a Cortex-A8 based CPU.
Advanced ARM processors, such as the Cortex series and ARMv7-based CPUS are capable of performing unaligned accesses for many types of memory accesses. Typically, using a cpu-based alignment fixup is faster than doing such a fixup in software. For best performance on advanced CPUs.
20111029 STABLE (http://www.mediafire.com/?9ug8n71vgc5ik7u)
This version was made stable on 05-Nov-2011, since there weren't any bug reports.
md5sum zImage
0fce8943c0b950c05e0d5163cf662460 zImage
At this point, I decided to add more aggressive updates in my kernel.
I have searched the others gingerbread kernels for devices like GT to verify if there is anything that can be used here.
Conclusion: I found tons of things that can make our experience and overall stability better.
For this first time, I just added some of them and I'm willing you to test it and report anything weird that you find.
Update initramfs from Humberto's kernel
Update initramfs from Humberto's kernel. It now has:
- CwM recovery v5.1.2.6
- New su binary v3.0
Thanks to Humberos
Erase memory pages when they are freed
Should improve memory handle.
Thanks to renaudallard.
net: wireless: bcm4329: compile wifi driver with Os flag
Add -Os GCC optimization flag to compile wifi driver.
This approach was used in Galaxy S kernel, so it should be fine
in GT-P1000 also.
Thanks to zachariasmaladroit.
ashmem improvements
ashmem: fix deadlock when system is low on memory
ashmem: Add cache flush routines to ashmem (zachariasmaladroit)
cpuidle: menu: fixed wrapping timers at 4.294 seconds
If everything goes fine, I'm planning to add more and more patches at each update.
This way, it would be much easier to track possible regressions.
20111026 (http://www.mediafire.com/?7fv630kp5bu15ev)
Using 2011.03 toolchain again
It turns out that the problems regarding random reboots with 2011.03 toolchain is being caused by samsung modemctl driver. For some reason, it isn't compatible with the newer toolchain, so the solution was avoid the driver building and use a binary version that was built with 2009q03 toolchain.
After this, the new kernel built with 2011.03 toolchain doesn't appear to have the random reboots and problems of the old version.
Thanks to alterbridge86 and chib_cr!
20111025 (http://www.mediafire.com/?931h2ev795faztf)
Revert to 2009q3 toolchain
When the kernel was built with 2011.03 toolchain, some users are having random reboots, e.g. when the USB was plugged the TAB rebooted.
Thanks chib_cr!
20111024 (http://www.mediafire.com/?o8be3gs8dfb609u)
I want to thanks alterbridge86 and the Overcome project. Basically, every change was taken from his tree.
Tweak IO schedulers for flash based devices
Should bring some improvements.
ARM: dma-mapping: free allocated page if unable to map (Russell King)
Should kill some process getting stuck and holding the CPU from entering deep sleep, which result in battery drain.
Update smartass governor to version 2 (erasmux)
New version of smartass governor.
Tweak touchscreen sensitivity
Touchscreen sensitivity is improved.
Add compatibility for 2011.03 toolchain
This kernel is being built with 2011.03 toolchain, which should bring some improvements.
Update BFQ IO scheduler to version 2 (revision 1)
Thanks to koxudaxi
20111006 (http://www.mediafire.com/?ahqucc9h5vwgo8j)
Don't check module magic (by Koxudaxi)
This fix some boot loop issues after build the kernel under certain conditions.
Set Kernel version to 2.6.35.14
It turns out that Overcome kernel has already applied all kernel's patches up to 2.6.35.14, so the correct version was set in Makefile.
20111005 (http://www.mediafire.com/?zm5t2w82feqtjuy)
Change RAM voltage from 1.8V to 1.7V
Fix BLN
Although, it still has issues.
Change ADC voltage from 3.3V to 3.0V
Change LCD voltage from 3.3V to 2.1V
10-points multitouch driver
samsung_modemctl is being built now
Overcome kernel is using a pre-built samsung_modemctl driver, because it is avoiding kernel to be built correctly. Here, this issue doesn't happen, so this change was reverted.
20110923 (http://www.mediafire.com/?2e0565sc1sgqmqr)
Update governors set from 3.1 kernel tree
The following governors were updated using Linux 3.1 kernel
tree:
Conservative
Ondemand
Performance
Powersave
Userspace
20110916 (http://www.mediafire.com/?98y1xe2hhu1mrtr)
Added lagfree governor
Thanks to jdkoreclipse.
Added smoothass governor
Thanks to jdkoreclipse.
20110909 (http://www.mediafire.com/?92d7sz9e7niuz2z)
Initial commit
Overcome Gingerbread Kernel v3.3.1 with Samsung's
P1000L/N Gingerbread Kernel patches.
Reserved......
Downloading...
I'll give it a try!
chib_cr said:
Downloading...
I'll give it a try!
Click to expand...
Click to collapse
Thanks
Tell me what do you think (remember it is a Gingerbread kernel for P1000L/N devices!).
I'm looking for feedback, specially about the new governors...
Works great!
Can't set clock to 1600 Mhz (freezes), but at 1500Mhz it scores 2505 on Quadrant!!
So far smoothass working well...
Tested for about 10 min, so can't tell you much...
BTW: I',m running stock 2.3.3
Install
How to install this file to tab?
Spyma said:
How to install this file to tab?
Click to expand...
Click to collapse
If you have a P1000L/N tab with Gingerbread, you just need to restart it in download mode, unzip the file, and flash with heimdall:
heimdall flash --kernel zImage
But BE CAREFUL, if you don't know what you are doing, you can brick your tab!
ok thanks.
Just for your information, I have just build a kernel with swap support.
To test it, I created a swap partition on my sdcard.
It is working. Although, I haven't seen any improvements...
When I open too many programs (like 8), android memory manager still force-kill the apps, while I'm expecting that the programs should be transfer to swap memory and, just when it is full, that a program should be force killed.
Well, if anyone wants, I can upload a kernel with swap support, but, at this time, I think it is useless...
Ronis_BR said:
If you have a P1000L/N tab
Click to expand...
Click to collapse
I tried to find out the different models and how they equate to one another but Google sends me to everything but which is which model. I have according to my devices "about" a GT-P1000. But, how do I know which model is the L or N? Just to give you more info, I am using the T-Mobile flavor with the modem swap program with Kratos currently flashed.
Hi fellow,
P1000L/N are latin model, if you are using Overcome Kratos with default kernel, you probably have a P1000 device and my kernel isn't compatible.
But you can check it under configurations / about ... (the last menu option), it should have as model number GT-P1000.
Thanks,
Ronan
Hi fellows!!
I have just tested the recently leaked gingerbread version with my kernel and everything is working flawlessly, including TV!
I'll post more details...
Ronan
Ronis_BR said:
Hi fellows!!
I have just tested the recently leaked gingerbread version with my kernel and everything is working flawlessly, including TV!
I'll post more details...
Ronan
Click to expand...
Click to collapse
A leaked GB version for L/N or just L?
If it has TV support I think it is for the L version. But which is the GB version? 2.3.3, 2.3.4 or 2.3.5?
If ti is something better than 2.3.4 I'll try it on my P1000N.
hi could you post de tv app?
davioxx said:
hi could you post de tv app?
Click to expand...
Click to collapse
Just the TV app won't work. You will need the entire ROM and P1000L model.
santroph said:
A leaked GB version for L/N or just L?
If it has TV support I think it is for the L version. But which is the GB version? 2.3.3, 2.3.4 or 2.3.5?
If ti is something better than 2.3.4 I'll try it on my P1000N.
Click to expand...
Click to collapse
No, it is 2.3.3. Basically, it is P1000N version with TV support Nothing more...
Which voltage settings are you guys using ?
Sent from my GT-P1000L using xda premium
Tks, Ronis. Running your kernel for a few days now, all good. Using smoothass, smartass and lagfree, up to 1300 stable, -50mV on 1300 and -25 on the rest.
Cheers.
- Tapatalk - SGT-P1000N - Overcome Kratos -
Running this kernel as well, no issues so far! Thanks!
Sent from my GT-P1000L using Tapatalk
Disclaimer: I am not responsible for your broken phone , broken memory card, etc. All my kernels I test first on my own phones , and then upload here
If you like my works please do not forget donate to me(PayPal account you may find in my profile)
Very often people not read full description(then write me to email "device not start, help me" even in the middle of the night) therefore write here with giant words:
UNLOCKED BOOTLOADER REQUIRED OTHERWISE DEVICE CAN'T START WITH CUSTOM KERNEL (YOU GET USB LOGO PICTURE OR TO YOU THROW INTO RECOVERY OR BOOTLOADER)
I never add fake overclock and overclock, because for now(or forever) no method for real overclock and underclock
Random reboots for most users probably fixed in 16.04.2016 and higher
For max stability I recommend to use Interactive governor
Kernel features:
1) USB Mass Storage Support
2)
3) DT2W support (to activate it, you should install Zenmotion)
4) KVM support (Kernel Virtual machine for Intel)
5) Added support of init.d. scripts
6) Added support of exFAT file system for external sd card.
7) ZRAM is disabled for old versions, on version of December 6 and higher- ENABLED.
8) Added CD emulating feature
9) Added SWAP support(need create swap partition on sdcard)
10)
12) Add more governors and I/O schedulers
13) USB-HID mouse & keyboard function(required USB Keyboard app from GPhttps://play.google.com/store/apps/details?id=remote.hid.keyboard.client&hl=en)
14) Support joysticks (DragonRise, Inc ang others)
15) Add more TCP IPv4 congestion algorithms (May change via TricksterMod or Kernel Auditor apps)
16) Reduce min display backlight for autobrightness. For use min backlight level you should to use autobrightness and set it to the left
Deprecated features:
1. Overclock to 2000 Mhz (for A501CG only) and Overclock to 2400 Mhz (for A500CG only). Idea and work by @TheSSJ (it have been removed since 26.12.2015)
2. Based on Asus Zenfone 2 ZE551ML 2.20.40.44(more than 50%) + Asus Zenfone 6 3.24.40 sources
3. Underclock to 667 Mhz. Idea and work by @TheSSJ
4.Hotplug for all governors
5. Frandom Linux kernel generator
Note: This kernel will work on stock Lollipop firmware only like 3.24.40.87, 3.24.40.78 or 3.23.40.60 or 3.23.40.52
This kernel was created by BORETS24 So if you need more information you can pm to him.
How to flash this kernel:Method 1(via PC)Step 0:
Bootloader unlock is required for every custom rom. You can use this tool for unlock:
https://drive.google.com/file/d/0B-Fin8UxrD6PRU9MM1lQZkV0SG8/view
Step 1:
You should download files for flashing:
ADB v1.0.32: Download from Google Drive
Step2:
You should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash boot new_bootXX.XX.img
,where XX.XX- numbers after words "new_boot"
Step3:
Reboot to Android.
Method 2(through CWM/TWRP, without PC)1. Download Flashable ZIP archive on phone
2. Go to recovery mode
3. Click Install ZIP and choose this archive
4. Then reboot
Archieves You make take from this post http://forum.xda-developers.com/showpost.php?p=64640638&postcount=364(Thanks to @Don No 1)
How to install Zenmotion:(it needed for DT2W)1) Download this file (asus.hardware.touchgesture.double_tap.xml) :
https://drive.google.com/file/d/0B-Fin8UxrD6PWWRBT1gwak16Tnc/view?usp=sharing
2) Put this file into system/etc/permissions
Set file permissions. It is a 0644 rw- r-- r--
3) Reboot the phone
4) Find Zenmotion in the Settings and activate it.
(It will work if you flash this kernel)
Changelog:
25.10.2016
I not remember that I removed, let's start that I changed and added
USB Mass Storage mode
Removed few unstable governors
I started to compile with use Zenfone 2 source code for Marshmallow
Existed governors from 6.0.1 source
Removed lz4- caused bugs, drain battery, very slow interface
Added bootboost feature into ramdisk such as Zenfone 2
Now drain battery less and interface speed is high
12.06.2016
Reduce min display backlight brightness to 5(no need to set to 2, no difference between 5 and 2- I checked).For use min backlight level you should to use autobrightness and set it to the left
ZRAM now turn on automatically only for 1 Gb RAM devices, for 2 Gb it disabled by default
Return to "1 core per modules" CPU mode
Return Interactive Pro and Intel governors
Remove InteractiveX and Hotplug governors(sometime caused problems)
Replace WI-FI from module into kernel
03.06.2016
Full NTFS support for SD card
NTFS OTG full support by sibling Asus File Manager(read/write), from others file managers you can to see OTG NTFS devices, may see OTG NTFS devices from file chooser but you can't edit data. But you can edit platform.xml via NextAPP SDfix and can write on NTFS OTG devices with any apps
14.05.2016
Full ExFAT SDcard support such as stock kernel(Now you can see ExFAT sdcard in file chooser, can modified data even without Next APP SDfix)
Remove UKSM and disable KSM
16.04.2016
Fixed: restore signal after long dissapear
Fixed: random reboots in phone calls
Standart processor mode "2 cpus per module"
Remove Intel, Lagfree governors and FIFO scheduler(caused reboots)
Compile with standart GCC 4.9, remove -O3 optimization(unuseless, placebo effect)
Add idle from Linux 4.6
17.03.2016
LZ4 kernel compress
LZ4 zram compress/decompress
Remove Hotplug(caused reboots, overheats) driver and return Hotplug governor
Speed-up interface
More less battery drain
Compile with SaberMod 4.9.3
Others optimizations
05.03.2016
Added again hotplug driver but modified, cores not jumping, not dancing, strongly CPU0+CPU1 always online
Approximately 90% sibling source 3.24.40
Hybrid ramdisk from 87+60 firmware
Some changes in dt2w code
Fixed CD emulation
14.02.2016
Based on Asus Zenfone 2 ZE551ML 2.20.40(more than 50%) + Asus Zenfone 6 3.24.40 sources, remove hotplug driver, return Hotplug governor
06.02.2016
Hotpluging for all governors via MSM hotplug driver(I set 2 cores always online by default, you may tuning this driver via Kernel Auditor, point CPU Hotplug), possible fix the impossibility of restoring the network signal after a long stay outside the network, remove Hotplug governor(is no longer needed)
31.01.2016
Add Hotplug governor and set it by default, without load on CPU 1,2 or 3 cores will go to offline https://www.youtube.com/watch?v=WBbCBahSgrM&feature=youtu.be
30.01.2016
Remove hotplugging from Interactive governor again, add InteractiveX V2 governor with adaptation for Quad core devices( 1 phisical core= 2 threads CPU go to offline, when screen off)
27.01.2016
Interactive governor from Asus ZenPad S 8.0 with adding hotplugging(2 threads=1 core go to offline, when screen off), underclock to 533 MHz, many code and drivers from source Asus Zenfone 2 ZE500CL, Ofast optimization
19.01.2016
Add and turn on Ultra kernel samepage merging(UKSM) technology a place of KSM, underclock to 450 MHz, may be fixed all random reboots besides during long phone calls, when dt2w is on(or fix? I don't know)
16.01.2016
Use new source code 3.24.40
Tweak Interactive governor: hispeed_freq and touchboost_freq down to 1333 Mhz
09.01.2016
May be, fix all random reboots
04.01.2016
Fixed freezes and reboots on third-party governors, when connection speed faster than 20 Mbit/s, return hotplugging to Interactive governor, return Intel and Yankactive governors, some bug fixes
02.01/2016
Compile without Ofast optimization, removed Hotplugging from Interactive governor, removed Yankactive governor, may be, this actions fix random reboots.
31.12.2015
Compile without Ofast optimization, processor works now in '1 core per modules' mode, now disable 3 core(3 threads), when screen off, on Interactive governors, try at random fix reboots on all version of devices
28.12.2015
Try to fix reboots on 1 Gb RAM modifications(return stock process drivers)
28.12.2015
a)Change toolchan from stock GCC to SaberMod 4.8.5
b) Add Hotpluging to Interactive governor, when screen off
c) Add F2FS support
d) Fix some warnings during compilations
25.12.2015
Attempt to fix screen freeze or reboots during long phone calls: change process.c driver on modifity driver from Zenfone 2. Read about it here https://github.com/kirananto/ZENFONE2/commit/044ad3da5263ba256a59b517e96a272b4e3f19f6, Fix almost all warnings in proximiry/lightsensor driver "ISO C90 forbids mixed declarations and code" during compiling, remove "fake" overclock
23.12.2015
Fix freeze and reboots of device, when chaging governors and/or schedulers, add more TCP IPv4 congestion algorithms and set Westwood by defauls in place of stock Cubic
Add some joysticks support, now may use device as keyboard and mouse for PC, move KVM from kernel to modules
15.12.2015
Underclock to 316 MHz, add Adaptive, Yankactive(with Hotplugging implementation by @TheSSJ] ) and conservativeX governors
12.12.2015
Add if.bin into kernel, to attempt fix screen freezing, push also if.bin to system/etc/firmware and reboot phone.
if.bin
11.12.2015
1. Add frandom Linux kernel generator
2. Add Bioshock, Lagfree, lionheart, Wheatley governors
3. Add BFQ, SIO, SIOplus, FIFO, FIOPS, VR I/O schedulers
06.12.15
Add ZRam support
10.11.15
1. Add SWAP support
2. Kernel build with Ofast optimization.
Now I will upload new versions on Yandex Disk
https://yadi.sk/d/tBN8eYlVr3mVZ
XDA:DevDB Information
Custom Lollipop kernel for Zenfone 5 & Zenfone 6 by BORETS24(Intel only), Kernel for all devices (see above for details)
Contributors
tank0412, BORETS24
Source Code: https://github.com/BORETS24/Kernel-fo-Zenfone-6-by-BORETS24
Kernel Special Features:
Version Information
Status: Stable
Current Beta Version: 1.0
Created 2015-11-02
Last Updated 2016-10-25
Bugs:
Some users reported that they have random reboots or screen freezes after call.
This issue have not solved yet.
Btw @tank0412 did u tried contacting borets if he can update this kernel for rr rom [emoji14]
Sent from my ASUS_T00J using Tapatalk
no_name said:
Btw @tank0412 did u tried contacting borets if he can update this kernel for rr rom [emoji14]
Click to expand...
Click to collapse
Yeah. I drop him a line on 4PDA. It looks like he stoped developing because he do not have device and he can not fix freezes after call + random reboots.
Actually in his kernel there's no freeze btw I think if he can release source then someone may work on it to make it compatible with rr rom ?
Sent from my ASUS_T00J using Tapatalk
no_name said:
Actually in his kernel there's no freeze btw I think if he can release source then someone may work on it to make it compatible with rr rom
Sent from my ASUS_T00J using Tapatalk
Click to expand...
Click to collapse
But he did this yesterday
https://github.com/BORETS24/Kernel-fo-Zenfone-6-by-BORETS24
Wow great ?
Sent from my ASUS_T00J using Tapatalk
What apps can i use to underclock overclock this kernel?
geepee410 said:
What apps can i use to underclock overclock this kernel?
Click to expand...
Click to collapse
Kernel auditor.
But this kernel has a default underclock/overclock. (400mhz/2000Mhz)
tank0412 said:
Bugs:
Some users reported that they have random reboots or screen freezes after call.
This issue have not solved yet.
Click to expand...
Click to collapse
Hi mate I am using this custom kernel and dt2w and its in ON state for three days now and I can confirm I don't have any freezes or reboots.... I had flashed internal data, system and cache before installing, and also had first installed. 44. Version KitKat..... During installing KitKat I relocked boot loader and flashed stock recovery. Then I installed. 54 version then lollipop. 60 and finally. 78 lollipop.. After this i unlocked bootloader and flashed twrp... Then flashed custom kernel and zen motion, no lags [emoji2]. Only my phone wakes everytime when I am on 2G data enabled and WiFi off..
Sent from my ASUS_T00F using Tapatalk
tank0412 said:
But he did this yesterday
https://github.com/BORETS24/Kernel-fo-Zenfone-6-by-BORETS24
Click to expand...
Click to collapse
U should share this to Quanqanh
kunalshah912 said:
Hi mate I am using this custom kernel and dt2w and its in ON state for three days now and I can confirm I don't have any freezes or reboots.... I had flashed internal data, system and cache before installing, and also had first installed. 44. Version KitKat..... During installing KitKat I relocked boot loader and flashed stock recovery. Then I installed. 54 version then lollipop. 60 and finally. 78 lollipop.. After this i unlocked bootloader and flashed twrp... Then flashed custom kernel and zen motion, no lags [emoji2]. Only my phone wakes everytime when I am on 2G data enabled and WiFi off..
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
Hello there heheh i can see rr members here hahah
Yerp i am using it for 2 days, everything ok. Only screen freeze when temp high up to 42 degree.
Might be bootloader unlock. Later will try relock back and see wat will happen
Sent from my ASUS_T00J using XDA Forums
mshazrul82 said:
Hello there heheh i can see rr members here hahah
Yerp i am using it for 2 days, everything ok. Only screen freeze when temp high up to 42 degree.
Might be bootloader unlock. Later will try relock back and see wat will happen
Sent from my ASUS_T00J using XDA Forums
Click to expand...
Click to collapse
For relocking you need to install stock recovery
Sent from my ASUS_T00F using Tapatalk
@quanganh2627 if you interested in sources of borets kernel then you can see sources are released by him and one thing to tell you that in his kernel "no freeze after call" or any such type of bug,his kernel is supper smooth so maybe you can do something to make it work on our rr rom ?
Sent from my ASUS_T00J using Tapatalk
hey @tank0412 what new on update 2/11 ,sir ?
ChungVan said:
hey @tank0412 what new on update 2/11 ,sir ?
Click to expand...
Click to collapse
Nothing. i just created own topic for it on XDA.
Is this the same kernel that you post in the rr thread? @tank0412
myrul said:
Is this the same kernel that you post in the rr thread? @tank0412
Click to expand...
Click to collapse
Yeah, it is a same.
kunalshah912 said:
For relocking you need to install stock recovery
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
R u using stock .78 with dt2w kernel, if yes then what type of settings r u using as my battery is draining very fast and r u also using power saver? Please reply.
Thanks
tank0412 said:
Bugs:
Some users reported that they have random reboots or screen freezes after call.
This issue have not solved yet.
Click to expand...
Click to collapse
with this kernel , no random reboots or screen freezes after call.
i think it have only one problem was limited 3 minutes when call . after 3 minutes , the call will auto end
Note: This kernel will work on stock firmware2.20.40.184, 2.20.40.183, 2.20.40.178, 2.20.174, 2.20.40.168, 2.20.40.165, 2.20.40.164 and may be lower, also working on some stock-based ROMs(EchoeROM V3,for example).
Disclaimer: I am not responsible for your broken phone , broken memory card, etc. All my kernels I test first on my own phones , and then upload here
If you like my works please do not forget donate to me(PayPal account you may find in my profile)
Bootloader unlock is required for every custom rom, custom kernel, custom recovery. Unlock Tool here:http://forum.xda-developers.com/zenfone2/general/tool-one-click-bootloader-unlock-root-t3155884
Changelog:
03.06.2016
Full NTFS support for SD card
NTFS OTG full support by sibling Asus File Manager(read/write), from others file managers you can to see OTG NTFS devices, may see OTG NTFS devices from file chooser but you can't edit data. But you can edit platform.xml via NextAPP SDfix and can write on NTFS OTG devices
14.05.2016
Migration to newest source code from Zenfone Zoom ZX551ML from 20 april 2016
Ramdisk from 183 firmware
Some optimization in code
17.04.2016
Full support exFAT SDcard format, now you may write/delete/rename by standart method of Android 5
16.04.2016
Great game performance
Remove Hotplug driver
Remove -Ofast optimization(loud words-not take effects, placebo)
Remove optimization flag -march=silvermont(loud words, did not work on 3.10 kernels)
Remove touchboost from Interactive governor
Modified Interactive, Interactive Pro, Intel, Cyan governors: CPU2 and CPU3 turn off when screen off
Idle from Linux kernel 4.6
Gpu governor simple_ondemand from Linux kernel 4.6
Based on source code from Zenfone Zoom ZX551 from march 17
zram and kernel compression is LZ4
04.03.2016
Rework MSM Hotplug, now only CPU0+CPU1 online, no dancing CPUs.
For humor and proof that overclock in others kernels is fake added "overclock" to 5GHz
28.02.2016
Re-work MSM Hotplug. Now if load more than 79 but lower than 99- only another 1 core go to online(CPU2 or CPU3)) and processor working on 3 cores online, if load more than 99- CPU3 and CPU2 go to online together and processor working on all 4 cores online DO NOT set fast lane 99 and higher!!!
Made 12 thermal states for video adapter a place of 3. If on 457 MHz have overheating- freq go to 400 MHz, if overheating on 400- go to 355, if hot on 355-go to 320 MHz and so on. In stock kernel if overheating on 457 MHz- processor goes in 200 MHz and was lags in games
25.02.2016
Compile with new march=silvermont optimizationmarch=silvermont(thanks to @Dan_Jacques )
Tuning MSM hotplug for Zenfone 2: now interface faster, smoother even when min cpus online = 2. And maybe drain battery less.
Unlocked almost all hidden GPU frequencies. Now available gpu frequencies 106, 133,160,177 MHz(I think this NOT fake underclock). I made Kernel Auditor version for our GPU PowerVR 6430 (see screnshots here http://i10.pixs.ru/storage/5/8/1/Bezimyanni_7545670_20843581.png ) https://drive.google.com/file/d/0BxVRXQGBg4DTaThjQUtoRFBrdms/view?usp=sharing
21.02.2016
Based on Asus Zenfone Zoom source code
Fixed hotplug driver and tuning(Now drain battery much less and fixed charging: now no overheating)
Added Cyan governor
Changed Interactive governor to Interactive from Asus Zenfone Zoom
18.02.2016
Now 2 different versions: for ZE551ML and for ZE550ML, Tuning MSM Hotplug(2 cores always online, Fast Lane up to 150), added Interactive Pro governor and set by default
04.02.2016
Interactive governor by default, realtime Hotplugging now on any governors, on Interactive too(Extra CPU cores disabled without load) Idea and work @mrg666 . You may to set parameters of hotplug driver via Kernel Auditor, point "CPU Hotplug"
Remove Hotplug governor(no longer needed)
Kernel Features:
1.Based on Zenfone Zoom ZX551ML source
2. Add zram support in LZ4 format(no need to turn on it, if no problem with multitasking and never no need to turn on for devices with 4GB RAM), kernel compression LZ4 too
3. Adaptation InteractiveX V2 governor for quad core devices, I make that 2 cores go to offline, when screen off
4. Processor work in "1 cpu per module" mode a place of "2 cores per module"(4 independent cpus, not pair)
5. Ofast and march=silvermont(thanks @Dan_Jacques optimization with GCC 4.9
6. Init.d support. You should install BusyBox in /xbin folder/
7. SELinux Permissive
8. KVM support (Kernel Virtual machine for Intel)
9. Added SWAP support
10. USB-HID mouse & keyboard functions(required USB Keyboard app from GPhttps://play.google.com/store/apps/details?id=remote.hid.keyboard.client&hl=en)
11. Ultra kernel samepage merging(UKSM) a place of KSM. Disabled by default, if you want you may turn on it via Kernel auditor
12. Full auto brightness. I removed minimal level 15, now level 5
13. More governovs and I/O schedulers
14.Zram disabled
15. More TCP algorithms, Westwood by default
16. Unlocked GPU frequencies 106, 133, 160, 177 MHz
17. NTFS support for SD card and OTG
Deprecated features:
1.Hotplug governor by default. Extra CPU cores disabled without load(it have been removed sinse 04/02/2016)
2. For correct work on ZE550ML you should change DPI to 320, for example via init.d script(root required).
1). Before flash kernel, you should install BusyBox in xbin folder, then create init.d folder in system/etc and set 755 permissions on it.
2) Download dpi320.zip, then extract dpi320 file and put it in system/etc/init.d folder, check that on it set 755 permissions
https://yadi.sk/d/6hg6bDDioCNbT
3). You may flash kernel.
3. Interactive governor from Asus ZenPad S 8.0 by default with some tuning(for example, hi_speed freq = 1583 MHz) and hotplugging additions( 2 cores go to offline, when screen off) Idea and work by @TheSSJ
4. Realtime hotplugging for all governors. You may to set parameters of hotplug driver via Kernel Auditor, point "CPU Hotplug"
5. Interactive governor from Asus Zenfone Zoom by default with some tuning(for example, hi_speed freq = 1750 MHz), InteractiveX and Interactive Pro have hispeed_freq 1750 MHz too.
Step 1:
You should download files for flashing:
ADB v1.0.32: Download from Google Drive
IMG file with kernel:
03.02.2016 https://yadi.sk/d/FuJhWqc9oCLZy
04.02.2016 https://yadi.sk/d/PcDiDaumoJMb7
All versions from 18.02.2016 and higher will be here: https://drive.google.com/folderview?id=0BxVRXQGBg4DTSVV5Q19mSVUxQk0&usp=sharing
Step2:
You should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash boot bootXX.XX.img
,where XX.XX- numbers after word "boot"
Step3:
Reboot to Android.
Method 2( via TWRP, without PC)1. Download bootXX.XX.img
2. Go to recovery mode
3. Click Install, choose this bootXX.XX.img, choose boot partition and flash
4. Then reboot
Method 3(via Terminal Emulator, without PC)(root required)1. Download bootXX.XX.img and put it in root of internal memory
2. in command prompt write
Code:
su
dd if=/sdcard/bootXX.XX.img of=/dev/block/by-name/boot
reboot
And device started with custom boot.img
XDA:DevDB Information
Custom Lolipop Kernel for Asus Zenfone 2 ZE551ML/ZE550ML, Kernel for the Asus ZenFone 2
Contributors
BORETS24
Source Code: https://github.com/BORETS24/Kernel-for-Asus-Zenfone-2.git
Kernel Special Features:
Version Information
Status: Testing
Created 2016-02-02
Last Updated 2016-09-03
Nice work, especially the Hotplug features (maybe you should transfer your post under http://forum.xda-developers.com/zenfone2/development ?)
nazagan said:
maybe you should transfer your post under http://forum.xda-developers.com/zenfone2/development ?)
Click to expand...
Click to collapse
Maybe... How I can to do this?
Can you add flashable zip please? thank you.
serhangelgor said:
Can you add flashable zip please? thank you.
Click to expand...
Click to collapse
Why?
Method 2(through CWM/TWRP, without PC)
1. Download bootXX.XX.img
2. Go to recovery mode
3. Click Install, choose this bootXX.XX.img, choose boot partition
4. Then reboot
Or you can flash without PC and without custom revovery
Method 3(through Terminal Emulator, without PC)(root required)
1. Download bootXX.XX.img and put it in root of internal memory
2. in command prompt write
Code:
su
dd if=/sdcard/bootXX.XX.img of=/dev/block/by-name/boot
reboot
And device started with custom boot.img
BORETS24 said:
Why?
Method 2(through CWM/TWRP, without PC)
1. Download bootXX.XX.img
2. Go to recovery mode
3. Click Install, choose this bootXX.XX.img, choose boot partition
4. Then reboot
Or you can flash without PC and without custom revovery
Method 3(through Terminal Emulator, without PC)(root required)
1. Download bootXX.XX.img and put it in root of internal memory
2. in command prompt write
Code:
su
dd if=/sdcard/bootXX.XX.img of=/dev/block/by-name/boot
reboot
And device started with custom boot.img
Click to expand...
Click to collapse
hey bro, if you don't mind can I add up a few things for you?? it will reduce your work and since you are on kernel 3.10.20 you can try to use my direct jump patch to jump to kernel.org v3.10.94 here's the link https://github.com/Zenfone2-Dev/direct-kernel-patch
and nice work.
installed and opened only 1 core, its too good and battery life is amazing, thanks so much for this amazing work, can you add underclock feature? it will give more batterry life
serhangelgor said:
can you add underclock feature? it will give more batterry life
Click to expand...
Click to collapse
No, I don't want to add fake underclock. It give more interface freeze and nothing else besides placebo effect and boastfulness. I started to make kernel for zenfone 2 in july 2015 and using "underclock" some time- no different battery life between 500 and 250 MHz, I tried and 166 MHz and even 83 MHz- no effect besides slow and freeze interface.
say99 said:
hey bro, if you don't mind can I add up a few things for you?? it will reduce your work and since you are on kernel 3.10.20 you can try to use my direct jump patch to jump to kernel.org v3.10.94 here's the link https://github.com/Zenfone2-Dev/direct-kernel-patch
and nice work.
Click to expand...
Click to collapse
Thank you very much, may be apply this patch in future.
BORETS24 said:
Thank you very much, may be apply this patch in future.
Click to expand...
Click to collapse
made a pull request keep working and if you want you can switch to gcc 5.3.0 toolchain https://github.com/Zenfone2-Dev/x86_64-toolchain-GCC-5.3.0
BORETS24 said:
No, I don't want to add fake underclock. It give more interface freeze and nothing else besides placebo effect and boastfulness. I started to make kernel for zenfone 2 in july 2015 and using "underclock" some time- no different battery life between 500 and 250 MHz, I tried and 166 MHz and even 83 MHz- no effect besides slow and freeze interface.
Click to expand...
Click to collapse
BORETS24, can you add F2FS support? I feel the IO more smooth with it (in other phones there is a huge difference between ext4 and f2fs, like Moto G), but requires changes in kernel config file (easy) and a modified ramdisk with edited fstab (more complicated). There is an Project T version that includes a fstab with the needes changes [link=http://forum.xda-developers.com/zenfone2/development/project-t-custom-kernel-zenfone-2-t3150822/post64366155]here[/link] (but only boot with all /system /data / cache formatted in F2FS). With the correct lines, it's possible to make a mixed fstab, and supports both fs.
Changelog:
04.02.2016
Interactive governor by default, realtime Hotplugging now on any governors, on Interactive too(Extra CPU cores disabled without load), remove Hotplug governor(no longer needed)
BORETS24 said:
Changelog:
04.02.2016
Interactive governor by default, realtime Hotplugging now on any governors, on Interactive too(Extra CPU cores disabled without load), remove Hotplug governor(no longer needed)
Click to expand...
Click to collapse
hey bro, I can't find the commit for realtime hotplugging
Sent from my ASUS_Z00A using Tapatalk
Im using it, looks good, thanks
say99 said:
hey bro, I can't find the commit for realtime hotplugging
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
If will no critical bugs I will upload to Github, need time for test by users.
BORETS24 said:
If will no critical bugs I will upload to Github, need time for test by users.
Click to expand...
Click to collapse
just an advice : always upload up the commits and make two builds, test builds and stable builds, you can always revert the things you pushed to git
Sent from my ASUS_Z00A using Tapatalk
say99 said:
just an advice : always upload up the commits and make two builds, test builds and stable builds, you can always revert the things you pushed to git
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I'm just recently start to use Github, for me easier delete changes from sources on PC Ubuntu than from github before changes,I keep stable source in zip archieves, old school And I can't to know which version of boot.img is stable which is not. Will make two unstable build? Alone I can't test everything, all hope on users. If you don't want to wait, I may to say that use Autosmp hotplug driver...
BORETS24 said:
I'm just recently start to use Github, for me easier delete changes from sources on PC Ubuntu than from github before changes,I keep stable source in zip archieves, old school And I can't to know which version of boot.img is stable which is not. Will make two unstable build? Alone I can't test everything, all hope on users. If you don't want to wait, I may to say that use Autosmp hotplug driver...
Click to expand...
Click to collapse
haha I can understand maybe that's y I added up the build script. A single command and you get a flashable zip without any need to manage them and that command is ./buildzf2
and yeah I have changed the defconfig in script and made a pull request so just get a hold on that
Sent from my ASUS_Z00A using Tapatalk
Add to description of kernel:
You may to set parameters of hotplug driver via Kernel Auditor, point "CPU Hotplug"
I really love your works. You made a big update for this cpu. Can you make a undervolt for this kernel, master ?
This is a (lightly) modified, based on stock, kernel for the 1st gen Asus Zenwatch; repacked from the stock boot.img (by replacing zImage).
See the changelog below for changes from stock and between versions.
NOTE: This kernel is only for the MEC23S (Android Wear 1.4) build, and is still experimental. I have not tested this on the newest build (and it's likely not compatible), but I'll probably do a final build for the latest version as a sendoff.
To download the kernel, go to the Downloads tab at the top of the OP, and download the file (version)-ondemand.img.
I can provide a mirror if the DevDB download doesn't work for some people.
I'm not entirely sure what else I can test/add to this kernel (without needing root, since it's not flawless on this watch), so if anyone has some suggestions, I can try adding those things to the kernel, so for now, new builds will come as there are new features to add.
If you want to try out this kernel, I recommend that you try just booting it through fastboot first:
Code:
fastboot boot (version)-ondemand.img
If something goes wrong, I am also including the stock kernel (boot_original.img in the downloads tab).
If you decide that you want to flash the kernel, you need to unlock your bootloader first (it will wipe all your data, so backup first), then run this command:
Code:
fastboot flash boot (version)-ondemand.img
To check if the custom kernel actually loaded, run an ADB shell, and type:
Code:
uname -a
The kernel version number should have "(version)-ondemand" right after it.
Notes:
For now, I am mainly planning to test out features that I can add or modify on the kernel without compromising stability or battery life, and I will also be testing each build on my own Zenwatch.
If there is enough interest, I can try and add custom CPU governors or set a different included one as default, but since there's no way to change the governor without root, I'll need to upload separate kernel images for each new default governor.
Vibration intensity is pretty easy to increase, so if 3100 mV still feels a bit weak, I can try bumping it up a bit more, like to 3150 or 3200 mV (I don't want to risk raising it too much and damage hardware).
Building the kernel doesn't take too long, so if there are any bugs or features to be added, I can compile and upload a new kernel pretty quickly.
XDA:DevDB Information
Custom ZW Kernel, Kernel for the Asus ZenWatch
Contributors
itechnoguy
Source Code: https://github.com/iTechnoguy/zwkernel
Kernel Special Features:
Version Information
Status: Testing
Current Beta Version: v2
Beta Release Date: 2016-04-10
Created 2016-03-30
Last Updated 2016-04-10
Changelog:
v2 - 04-10-2016
Changes:
I/O Scheduler no-op added (and made default; stock kernel default was CFQ)
Compiled with Linaro GCC 4.9
Note: So far, ondemand is one of the only CPU governors other than performance that don't cause the Zenwatch to bootloop (including 3rd party governors), so for now, ondemand will remain the default (a couple of other governors, like interactive remain compiled in, but bootloop when made default)
v1 - 03-29-2016
Changes from stock kernel:
Uses the ondemand governor by default (instead of performance)
Slightly increased vibration strength (measured in mV; increased from 3000 to 3100 mV)
To-Do/Look into:
Implementing CPU (and IO schedulers?) governors without having to create a separate kernel image for each governor, meaning needing systemless root to avoid needing to reflash the system partition before an OTA
Possibly add init.d support so that scripts can change the governor on boot (without needing an app, which would probably be hard to use on the ZW's small screen)
Kernel-level support for disabling the default low-bit ambient mode (since build.prop edits don't work)
If you have the opportunity when you are looking around in there see if there is anything in the kernel that forces low bit ambient. I have tried changing the build.prop to turn it off as you would on other devices and it has not been successful.
hecksagon said:
If you have the opportunity when you are looking around in there see if there is anything in the kernel that forces low bit ambient. I have tried changing the build.prop to turn it off as you would on other devices and it has not been successful.
Click to expand...
Click to collapse
I'll look into it, but from what it looks like so far, it seems that low bit ambient mode isn't a kernel-level feature. I'll keep digging around though, and see if there is something within the kernel that controls it.
Maybe ability to disable 2 cores to increase battery life?
Sent from my SM-G925F using Tapatalk
macia10 said:
Maybe ability to disable 2 cores to increase battery life?
Click to expand...
Click to collapse
I can implement that; it's more of a ramdisk edit (as seen in tiny4579's discontinued kernel for this same watch).
I guess there's also the parameter CONFIG_NR_CPUS to set the max number of CPU cores (like setting maxcpus in the ramdisk), but on a kernel level. I'll take a look and test it out.
I've been testing a couple of builds with reduced cores, and I've been running into issues. Any dual core setup I've tried so far (either by limiting the CPUs within the kernel or just the ramdisk) seems to be unstable, causing the watch to reboot within a couple of minutes of finishing boot. I guess the ramdisk editing worked on a previous kernel/build of Android Wear, but it's causing some sort of instability on Marshmallow now.
I also tested with tri-core builds, but none of those even made it past the boot logo.
I have flashed the kernel and will run it for a few days to see if there is any battery improvment. As far as CPU goes maybe using a hotplugging governor is the way to go? Not sure if there are any modern ones out there but I recall back in the day before hotplugging was done with a stand alone module.
hecksagon said:
I have flashed the kernel and will run it for a few days to see if there is any battery improvment. As far as CPU goes maybe using a hotplugging governor is the way to go? Not sure if there are any modern ones out there but I recall back in the day before hotplugging was done with a stand alone module.
Click to expand...
Click to collapse
I've been watching the CPU usage using AIDA64, and it seems like most of the cores are inactive most of the time, so I think the kernel might already be using Qualcomm's built in hotplug driver.
I might have to add in a separate hotplugging governor, which shouldn't be too much of a problem, since the default CPU governors were just performance, ondemand, userspace, and conservative (interactive is also available, which I may make default next if a hotplug governor doesn't work well).
In terms of battery life, I noticed that ondemand does help increase idle/screen-off battery time, but screen-on time seems to be about the same as when using performance.
get about an extra day with ambient off and tap to wake. I'm at the end of day 2 with ~30% left.
I recall back when we had root that previous versions of the official software ran only single core on performance governor. I think the CPU was limited to like 800 or 1000 MHz too.
Yeah, the default max clock speed is set to roughly 787 MHz, and the minimum (in this kernel version) was at 300 MHz.
I think I may make the next build with interactive instead of ondemand, to see if interactive offers any better battery life, since hotplug governors basically refuse to compile with a newer kernel. I'm also considering making the new default minimum clock speed to 250 MHz (or lower, if it doesn't get unstable).
New build is up (v2), available on the DevDB Downloads tab (full name: v2-ondemand.img). See the second post for changes.
I just realized that my watch updated to Android Wear build MWD48B by itself, which also brings a new kernel (Asus posted the new sources a few days ago). I don't know if there's still interest in a modified kernel, but I can try building a new kernel with the updated sources (which may take a bit since I don't have access to my normal build system).
itechnoguy said:
I just realized that my watch updated to Android Wear build MWD48B by itself, which also brings a new kernel (Asus posted the new sources a few days ago). I don't know if there's still interest in a modified kernel, but I can try building a new kernel with the updated sources (which may take a bit since I don't have access to my normal build system).
Click to expand...
Click to collapse
col you have latest build already.
Partners watch has not recieved the update... But she has twrp and the OPs Kernel flashed so may be thats the reason..
Could someone confirm if going back to stock recovery on kernel will allow the update and proved instructions and downloads to restore them
lohtse said:
col you have latest build already.
Partners watch has not recieved the update... But she has twrp and the OPs Kernel flashed so may be thats the reason..
Could someone confirm if going back to stock recovery on kernel will allow the update and proved instructions and downloads to restore them
Click to expand...
Click to collapse
You'll have to restore the stock recovery to install the OTA update (I made a backup of the stock recovery from the last update here: https://drive.google.com/open?id=0B6eYQrCg9u-bUTA2d3dRdEZBbXM).
In terms of having the custom kernel flashed, I don't think that affects the update, because my Zenwatch stealth updated without me noticing (even though I had the kernel flashed), since I had the stock recovery installed, not TWRP.
I would love continued effort on a kernel but it doesn't look like this device has much life left here at XDA. If you don't personally believe you will benefit from your effort, don't make it for others.
hecksagon said:
I would love continued effort on a kernel but it doesn't look like this device has much life left here at XDA. If you don't personally believe you will benefit from your effort, don't make it for others.
Click to expand...
Click to collapse
I am considering doing one final kernel for this watch (no ETA, because I've been really busy lately), since it's very likely that Wear 1.5 will be the final update, so the kernel won't need updating past that (if it's stable, of course). It might not see much use, but it'll still be here for people that continue to use this watch past its official support life.
Due to the @MSFJarvis and @nathanchance being the unbeatable dynamic duo, I've decided to discontinue this kernel. At this point, our kernels are extremely similar, save ElectroUtil and a few misc commits. Rather than put time into a modified Flash kernel, I recommend y'all just try Flash (warning: its pretty good). ElectroUtil and my other changes will live on in the CarbonROM kernel, and will simply be added on top of flash kernel. Thanks for supporting this project while it was alive.
For those of you who have used my angler and (unreleased) ether kernels, then you already know how this works. Feel free to skip to the Instructions.
Electron kernel has a few goals that make it different from other kernels. These goals are to:
Be as light weight as possible
Improve battery while performing at least as well as stock
Be a flash-and-go kernel (recommended settings are defaults)
That being said, This is a flash and go kernel (If you install the Magisk Module), please do not tweak options unless you are an advanced user.
Electron does NOT have spectrum support yet, and I don't plan on adding it until twrp is semi stable.
Current Features:
Upstreamed to 4.4.108
Updated EAS
ElectroUtil governor (renamed schedutil for compatibility)
Maple I/O scheduler
Adreno Idler
GPU Display state awareness
KCAL Support
Wake Gesture support
State Notifier
Disabled FSync
Power-Efficient Workqueues
Wakelock blocker
Devfeq wake boosting
FP Scanner speedups
CAF CPUIdle Updates
GPU+CPU Undervolted
Zen Interactive Tunings
Optimized string routines
Many warnings fixed
Optimized strlen use
Compiled with DragonTC 4.0
Polly optimizations
Installation:
Download the Electron boot image
OPTIONAL: Patch with Magisk
Run "adb reboot bootloader"
Run "fastboot flash boot /path/to/Electron-boot.img"
RECOMMENDED: Download Electron Defaults zip
Install as a Magisk module by pressing the "+" in the modules menu
Reporting Bugs:
Please follow this guide by @The Flash . If reporting a crash/reboot, provide both a dmesg and ramoops. Otherwise, provide a logcat and dmesg. CLICK HERE
Download:
Boot Image
Magisk Module
I would like to thank all of the great people whose support and help that I've received and whose work I've referenced to make this kernel a reality: nathanchance(TheFlash), boeffla(andi-p), FranciscoFranco, RenderBroken, flar2, xanaxdroid, R3V3NT3CH, arter97, DespairFactor, neobuddy89, ZeroInfinity, and anyone I missed!
XDA:DevDB Information
Electron Kernel for Taimen, Kernel for the Google Pixel 2 XL
Contributors
frap129
Source Code: https://github.com/frap129/taimen
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v4
Stable Release Date: 2017-12-26
Created 2017-11-15
Last Updated 2018-02-08
In this post, I will add descriptions of my original kernel features for users and developers to reference.
ElectroUtil Governor:
ElectroUtil is a schedutil based CPU Frequency governor, taking some queues from pwrutilx by ZeroInfinity, but with an overall different frequency selection algorithm.
ElectroUtil is a hexacore-biased governor, meaning that all 4 Silver and the first 2 Gold cores are preferentially granted higher frequencies at lower utilizations than the last 2 Gold cores to prevent excess use of more Gold cores than necessary. ElectroUtil is also device state aware, forcing lower frequencies when the device is suspended. This is handled via 2 different mechanisms. The primary mechanism is the 'suspend_capacity_factor' tunable, which is used such that
max = capacity * (suspend_capacity_factor + 1) / suspend_capacity_factor
where 'max' is the divisor of the frequency calulation
algorithm. For example, a value of 10 for the capacity factor result in a frequency that is 1/10th lower when the device is suspended. The second mechanism is a hard limit, set by the tuneables {gold/silver}_suspend_max_freq. If the requested frequency is higher than than the respective suspend max, the max will not be exceded. For the last 2 Gold cores, this max is always the minimum frequency.
Maple I/O Scheduler:
Maple is based on the Zen and Simple I/O schedulers. It uses Zens first-come-first-serve style algorithm with separate read/write requests and improved former/latter request handling from SIO. Maple is biased towards handling asynchronous requests before synchronous, and read requests before write. While this can have negative aspects on write intensive tasks like file copying, it slightly improves UI responsiveness. Like chill, maple also has power saving features. When the device is asleep, maple increases the expiry time of requests so that it can handle them more slowly, causing less overhead.
More to come...
Reserved
Errors out when I try to install module, but the kernel itself runs smooth
crossen0 said:
Errors out when I try to install module, but the kernel itself runs smooth
Click to expand...
Click to collapse
Thats weird, it installed for me. Will look into it asap.
Here's what the error said:
Ah yes, feed my flashing hunger muhahahaha!!! Install of kernel and module went without issues. I have noticed the following repeated in logcat but I had to run out for a few so only posting the error until I return home. Every 10-15 lines in logcat contains the below at least once.
11-14 20:57:26.139 811 811 E [email protected]: Governor not supported by powerHAL, skipping
crossen0 said:
Here's what the error said:
Click to expand...
Click to collapse
That's the same exact error ive been getting with no matter what module i try to flash with magisk. just started after i unistalled viper4android and tried reinstalling it. Can't find a workaround with it just yet either
crossen0 said:
Here's what the error said:
Click to expand...
Click to collapse
Thats a device issue. Try rebooting and/ redownloading
123SIT said:
Ah yes, feed my flashing hunger muhahahaha!!! Install of kernel and module went without issues. I have noticed the following repeated in logcat but I had to run out for a few so only posting the error until I return home. Every 10-15 lines in logcat contains the below at least once.
11-14 20:57:26.139 811 811 E [email protected]: Governor not supported by powerHAL, skipping
Click to expand...
Click to collapse
I forgot that the governor is powerHAL dependant for EAS devices. I'll look for a workaround until twrp works (requires installing a custom powerHAL), but for now, performance and battery don't seem to be affected much
Do I need to rename the .zip?
Maybe I'm missing something here? I have rebooted several times redownloaded the zip.
crossen0 said:
Do I need to rename the .zip?
Maybe I'm missing something here? I have rebooted several times redownloaded the zip.
Click to expand...
Click to collapse
Did you make sure that the Kernel flashed correctly? First time I flashed it I was still on the previous FLash kernel. Had to do it one more time and it finally showed Electron kernel under sett/about. Then I installed the Magisk Module w/the defaults successfully by using + once in Modules menu.
https://drive.google.com/file/d/1lPda5zNtK0FUXswmIIDEvPAGry4wZqss/view?usp=sharing
an21281 said:
Did you make sure that the Kernel flashed correctly? First time I flashed it I was still on the previous FLash kernel. Had to do it one more time and it finally showed Electron kernel under sett/about. Then I installed the Magisk Module w/the defaults successfully.
Click to expand...
Click to collapse
I am on Electron v1
crossen0 said:
I am on Electron v1
Click to expand...
Click to collapse
Hmm, the only other thing I did was copy the Electron-defaults.zip to the MagiskManager folder before installing as a mudule...
an21281 said:
Hmm, the only other thing I did was copy the Electron-defaults.zip to the MagiskManager folder before installing as a mudule...
Click to expand...
Click to collapse
I tried moving it over to MagiskManager folder but it still fails.
Made a quick workaround for the powerHAL issue, will include in v2 (Should only be a couple days)
crossen0 said:
Do I need to rename the .zip?
Maybe I'm missing something here? I have rebooted several times redownloaded the zip.
Click to expand...
Click to collapse
Sounds like a magisk issue. Try completely remove magisk and manager.
Going to dive in!! But, ugh! I have to go back to 8.0? THE HORROR!!! LoL.. Onward!
Up and running fine!!! Just a quick question..maybe OT? Maybe not.. But would this script have any issues with the kernel being installed from here?
https://forum.xda-developers.com/pixel-2-xl/development/mod-pks-tuning-script-t3702834
Is this kernel compatible with the pixel 2?
JayTheNinja said:
Is this kernel compatible with the pixel 2?
Click to expand...
Click to collapse
Really?? Look 5 posts above yours!
Badger50 said:
Really?? Look 5 posts above yours!
Click to expand...
Click to collapse
No, this is XL only! If it was Pixel 2 compatible, it would be in the Pixel 2 forum.
JayTheNinja said:
Is this kernel compatible with the pixel 2?
Click to expand...
Click to collapse
But... its not
No idea why there's such a large number of pixel 2 users that hang out in the xl forum