HTML5 KERNEL
"Low overhead, light and the way of the future" - sultanxda
(he wasn't referring to this but whatever)
This Kernel aims to be as simple as possible with only useful added features, you may request for features and we will consider them.
Features:
Compiled with GCC (cuz clang sucks)
Removed unnecessary bloat
Reduced power consumption
Improved zRAM and memory management
Upstreamed to the latest Linux 4.9 stable (based off ALS)
First kernel with touchscreen in TWRP fixed
Some cool patches
A lot of less cool patches
Magisk support
Westwood+ is now the default tcp algorithm
Brickported Backported patches from Sony, CAF and others
refer to the source for the rest I am lazy
TLDR:
It's better than stock and the best custom kernel out there (arguable)
Links:
Downloads
Telegram group
note: the zip is a flashable anykernel zip.
XDA:DevDB Information
HTML5 Kernel, Kernel for the Google Pixel 3 XL
Contributors
_LLJY, ab123321
Source Code: https://github.com/bluecross-dev/kernel_msm-4.9
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 210
Stable Release Date: 2019-11-15
Created 2018-11-08
Last Updated 2019-11-15
Thanks for this, I wonder if this kernel fixes the touch issues when flashing TWRP.
WTF? How many times are you going to post this?
spotmark said:
WTF? How many times are you going to post this?
Click to expand...
Click to collapse
i'm terribly sorry XDA derped HARD
_LLJY said:
i'm terribly sorry XDA derped HARD
Click to expand...
Click to collapse
I'm just busting on you, too. All of a sudden is what like, whoa.
First run on this kernel. Stock settings. Hard to compare right now. November stock factory image appears to have been better on battery than the September images in my opinion.
Typical work day on LTE.
You actually did it, you absolute madman!!
Auto flashed in Franco - lost root. No problem.
Thank you for developing and fingers crossed it fixes our memory management problems.
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
Auto flashed in Franco - lost root. No problem.
Thank you for developing and fingers crossed it fixes our memory management problems.
Click to expand...
Click to collapse
Auto flash but don't reboot. Then flash magisk from mm and reboot.
Sent from my crosshatch using XDA Labs
option to disable fsync please?
testing now
i have 20 apps opened with no re-draws but i think the re-draws happen once the screen is a sleep for a while and wakes back up.
Feels snappy and running ALL my apps while listening to podcast. Nice....
Sent from my Pixel 3 XL using Tapatalk
ok so ive re-created the scenario and can confirm that re-draws only happen after the phone has been asleep for sometime - like the RAM is being cleared or something @ idle/sleep?
Does the touch/TWRP work with kernel
Sent from my Pixel 3 XL using Tapatalk
Update will come later today with
Code:
-Wireguard support
-November patch stuff
-whatever else I decide to add
virtyx said:
option to disable fsync please?
testing now
i have 20 apps opened with no re-draws but i think the re-draws happen once the screen is a sleep for a while and wakes back up.
Click to expand...
Click to collapse
no.
Heck, Pixel 3 already has the fastest storage I/O performance among all Android phones, why would you need to mess up with fsync?
ab123321 said:
no.
Heck, Pixel 3 already has the fastest storage I/O performance among all Android phones, why would you need to mess up with fsync?
Click to expand...
Click to collapse
useless feature, just like journaling and barriers.
and i like being given the option to disable things i dont believe i need on my phone.
booted twrp temporarily... flashed the zip, rebooted, device is corrupted and won't boot up.
What now?
masri1987 said:
booted twrp temporarily... flashed the zip, rebooted, device is corrupted and won't boot up.
What now?
Click to expand...
Click to collapse
Try to only flash boot.img from the factory image or reflash factory image with -w removed. ( removing -w makes you keep your data)
That should help.
If that is not working you may have to reflash the factory image without -w removed. That will erase userdata.
virtyx said:
useless feature, just like journaling and barriers.
and i like being given the option to disable things i dont believe i need on my phone.
Click to expand...
Click to collapse
journaling isn't useless in the slightest bit, disabling fsync WILL lead to data corruption, however the phone can fix it by itself most of the time. I still wouldn't disable it personally.
_LLJY said:
journaling isn't useless in the slightest bit, disabling fsync WILL lead to data corruption, however the phone can fix it by itself most of the time. I still wouldn't disable it personally.
Click to expand...
Click to collapse
afaik journalling is useless for battery backed devices (just like barriers) the chances of any corruption happening is almost 0 unless somehow a hard restart happens you might lose some data
As for fsync, again I know it caused issues on other phones, but I always have it disabled and run e2fsck routinely to check for any anomalies and it always returns ok.
Again if hard restart occurs there is a massive chance it will cause corruption, but I've never had a hard restart, let alone one that wasnt my fault.
For many the performance increase from disabling fsync isn't worth the risk
As for journalling, from what I can tell the pixel 3xl doesn't have any journalling going on, check proc/mounts, only metadata partition has journalling.
Related
Hello guys just wanted you bring to your attention the Exceed Kernel built by @kairi_zeroblade for us Verizon users, check out the thread here:
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post69474753
#######PLEASE FLASH KERNEL FROM INTERNAL STORAGE AND MAKE SURE THAT "SYSTEM" IS CHECKED UNDER "MOUNT" OPTIONS IN TWRP###########
#######All builds are based on the supersu 2.76 boot.img if you have supersu 2.78 and above, you will probably run into app permissions issues!!!##########
The Exceed 4F "V" varient is based on verizons latest PG2 kernel. It has been highly optimized by Kairi_zeroblade and includes:
All of the latest note 4 kernel sources so you have all of the most current fixes and optimizations from Samsung
Wakelock fixes
Exploit fixes
Ramdisk optimizations
GPU calibrations
It is compatible with note 7/s7 ports and stock TW Roms
Fully SELinux permissive(helps with installing viper4android and other mods)
And much more that I can't remember!
Kairi_zeroblade has all of the kernel settings pre tuned for amazing battery life and fast stable performace.
It is NOT recommended that you adjust the kernel settings EXCEPT for the ones available in Synapse.
Just flash and enjoy!
Do not forget to also flash the latest gpu drivers here:
https://drive.google.com/file/d/0B_3BNlXOVtO5bHp2MS12b291TjQ/view
These are based on the most current 805 adreno source (ph4 sprint I believe)
///////This kernel may give you the Volte and cloud (wifi calling) icons in the notification bar) see post 3 for my tip to disable Volte
Any questions or feedback, please post in the original Exceed thread^^^:good::good:
Side note........
///Kari_zeroblade does not like to add experimental features because they risk breaking the stability and battery life on the kernel. He keeps it simple and highly optimized. If there is a performance benefit you can be sure he will try to incorporate it though
Post#2 changelogs
Post#3 Volte icon
Post#4 UnderVolt/UnderAmp
######## BUILD 4M #######
2/2/17
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post70357447
Camera Improvements
Updated to the latest DPL2 source
SETCPU partially implemented(should give nice battery life improvements.)
Built in anykernel format so that should solve Supersu issues:good:
######## BUILD 4K ########
12/4/16
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post69924893
New Nightlies guys!!
As promised I did bring a solution to the fts_wakelock and some security updates from Google..
Grab the test builds for your device here
#######PLEASE FLASH KERNEL FROM INTERNAL STORAGE AND MAKE SURE THAT "SYSTEM" IS CHECKED UNDER "MOUNT" OPTIONS IN TWRP BEFORE YOU FLASH###########
#######All builds are based on the supersu 2.76 boot.img if you have supersu 2.78 and above, you will probably run into app permissions issues!!!##########
Thank you, and for your issues, just attach a log on your post and we will see what we can do for you.. :good:
Another Thanks to those who helped me get my build laptop fixed.. Merry Christmas to you..
######## BUILD 4F ########
Kairi_zeroblade:
Grab it from here
FG = is for F and G variants
V = is for Verizon
T = is for TMobile version
P = is for Sprint version
As promised, these builds can now be flashed on both NOTE 7 ports floating around here and at the same time with STOCK rom's too..if you ever find any issues do report with logs..else as usual I don't give a damn..I don't know why you're using a stock source compiled kernel with nothing and yet scores are lower than usual stock samsung kernel and you're like an Angry Bird jumping happily, when you have this project to "help and improve" (just my 2 cents) which has shown great potential (and worth IMHO)..
I'm sure you're aware you only now have a handful of devs supporting your device and if in the process you loose them all due to users being disrespectful and uncooperative then its your loss and not ours..
F Variants wifi needs testing though the necessary measures to make it work are already in place and has been checked..
Some patches to fix some Exploits were already added in, same thing goes with some upstream fixes from Google and CAF..Ondemand crashing is also been fixed (in my case) as I have tried to replicate the issue and grabbed something to ponder on..
Again for those who are supporting the project, Thank you very much!!
######## BUILD 4E ########
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post69363834
kairi_zeroblade said:
This test is specifically for the Verizon Note 4 running stock MM (latest, I forgot the build..lol) as this uses the updated ramdisk from that OTA update..this build also uses the Verizon Samsung Config so this is the proper kernel for your variant..please make sure you are on the latest MM Bootloader and Baseband for things to properly work (though @joemill tested this out and he had no issues to report)..this build also incorporates important kernel updates from the DPH2 (if I remember it right!!) from the N910P (Sprint, which will be supported once I get the laptop fixed, thanks to @joemill again for the boot.img dump)..I'll also include a GPU driver update package from the same update..
Enough with the chit-chat let the games for Verizon begin..
Grab the build here..
and GPU Drivers here..
Thank you very much to those who take time to read and enjoy my posts..
Click to expand...
Click to collapse
The kernel is based on the latest Verizon build PG2 I believe. As long as your bootloader is unlocked and on PD1 PD3 or PG2 (any marshmallow Verizon bootloader) then this should work for you
If you are still on 5.1.1 lollipop follow this guide to upgrade:
http://forum.xda-developers.com/not...firmware-safe-upgrade-to-marshmallow-t3402727
This kernel was tested on the latest paulpizz rom release.
I personally do not use VoLTE or WiFi calling and have never activated them or set them up on my phone. I never had either the cloud icon or the VoLTE icon with Paulpizz kernel, or Oscar kernel. When I flashed exceed the VoLTE icon appeared even though it is not enabled in the settings, "advanced calling" section.
I BELIEVE that those icons appear from flashing a modified kernel, more specifically a selinux permissive kernel(since this is the only kernel I've found that is permissive). Jasmine rom 6 had the icons appear with its selinux permissive kernel so in version 7 he left the kernel selinux enforceing.
Since I do not use VoLTE I went to others.Xml in the system/csc folder and edited this line:
<CscFeature_IMS_EnableVoLTE>TRUE</CscFeature_IMS_EnableVoLTE
To
<CscFeature_IMS_EnableVoLTE>FALSE</CscFeature_IMS_EnableVoLTE
Now the VoLTE icon is gone! and the 4glte icon is gray when connected to wifi instead of white all the time(I believe this means that 4glte radio is In a power save mode when not needed because you have a WiFi connection, also this improved my battery life quite a bit)
I personally would much prefer a kernel like exceed that has far better battery life and a selinux permissive kernel(so you can easy install vipers Android mods) even if it displays those icons.
I haven't had time to do anymore research but I would ask other verizon kernel developers(Paulpizz or Oscar since kari_zeroblade doesn't have a Verizon phone to test on) if there is a trick to remove those icons or if it is truly because the kernel is selinux permissive.
I would not mess around with any settings in kernel auditor or other kernel tweaking apps EXCEPT for synapse.
(Don't bother under clocking. The phone barely ever hits those top frequencys and when it does its better to complete the process fast and quick rather then hanging at a lower clock speed for a longer time. )
Undervolt and under amp in the synapse app can help your phone run cooler which will keep it from throttling cpu and gpu.
I personally run -45 uv and -12ua with zero issues in stability. If you undervolt you should always under amp to compensate for the drop in voltage. If you go to low your phone will just become unstable and probably lock up or reboot.
EVERY time you boot you will need to re apply those settings for safety.
Reserved~
The Synapse app days No UCI?
"Crack flashing is better than crack smoking"
Matthenson20 said:
The Synapse app days No UCI?
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
Did you flash from your internal storage or external sd card? Also make sure that "system" is checked under the "mount" menu in TWRP
If it doesn't install then send us a twrp log after you make the attempt to flash the kerenl.
joemill said:
Did you flash from your internal storage or external sd card? Also make sure that "system" is checked under the "mount" menu in TWRP
If it doesn't install then send us a twrp log after you make the attempt to flash the kerenl.
Click to expand...
Click to collapse
Did all that, had synapse installed and did tweaks to voltages and amps, had a random reboot then synapse quit working
Will this work with N7 ports on? I'm running Chevy 2.7.3 build based on N5 port I believe
"Crack flashing is better than crack smoking"
Matthenson20 said:
Did all that, had synapse installed and did tweaks to voltages and amps, had a random reboot then synapse quit working
Will this work with N7 ports on? I'm running Chevy 2.7.3 build based on N5 port I believe
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
That's strange. The reboot could be because you under volt or under amp too much. How far did you adjust them?
It should work with all ports but you might be the first person to test on that rom my friend. L
joemill said:
That's strange. The reboot could be because you under volt or under amp too much. How far did you adjust them?
It should work with all ports but you might be the first person to test on that rom my friend. L
Click to expand...
Click to collapse
I'll retry, I went -40 and -12, I'll try 30 and 8
"Crack flashing is better than crack smoking"
Matthenson20 said:
I'll retry, I went -40 and -12, I'll try 30 and 8
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
Every phone is going to be different, some may not undervolt at all, don't worry too much if it doesn't. It will not save very much battery life at all and will only make the phone run slightly cooler. The kernel should run really cool and have great battery life by default
joemill said:
Every phone is going to be different, some may not undervolt at all, don't worry too much if it doesn't. It will not save very much battery life at all and will only make the phone run slightly cooler. The kernel should run really cool and have great battery life by default
Click to expand...
Click to collapse
Yes probably my fault, saw a new kernel abs started foaming at the mouth lol, going to reflash tonight and give it a go, will report in 24 hrs and let thread know
"Crack flashing is better than crack smoking"
Matthenson20 said:
Yes probably my fault, saw a new kernel abs started foaming at the mouth lol, going to reflash tonight and give it a go, will report in 24 hrs and let thread know
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
Haha I don't blame you. It's hard to resist the temptation to tweak. Just flash let it settle and enjoy
joemill said:
I.
Since I do not use VoLTE I went to others.Xml in the system/csc folder and edited this line:
<CscFeature_IMS_EnableVoLTE>TRUE</CscFeature_IMS_EnableVoLTE
To
<CscFeature_IMS_EnableVoLTE>FALSE</CscFeature_IMS_EnableVoLTE
Now the VoLTE icon is gone! and the 4glte icon is grayed out
Click to expand...
Click to collapse
I'm sorry for the off topic comment, but thank you for this fix. I've been looking for a way to gray out that 4g icon while connected to wifi for awhile. :good: @joemill
kevintm78 said:
I'm sorry for the off topic comment, but thank you for this fix. I've been looking for a way to gray out that 4g icon while connected to wifi for awhile. :good: @joemill
Click to expand...
Click to collapse
I think the battery life is better with it disabled too
Still a no go in Chevy's 2.7.3 build. Must be because it's a Note 5 port, Synapse app just says no UCI. I installed from phone memory with system mounted. Cleared caches and everything
"Crack flashing is better than crack smoking"
I have been using this kernel successfully for the last week on the Note4 Grace Note7 based ROM v2. It has not had any crashes, or problems that I have been able to notice. I have not tweaked any of the kernel settings in the synapse app.
I have not specifically paid attention to the battery life after flashing, as I have not underclocked yet.
Is there an undervolt and underclock baseline that all Note 4s should be safe to start at?
Thanks.
signupstuffid said:
I have been using this kernel successfully for the last week on the Note4 Grace Note7 based ROM v2. It has not had any crashes, or problems that I have been able to notice. I have not tweaked any of the kernel settings in the synapse app.
I have not specifically paid attention to the battery life after flashing, as I have not underclocked yet.
Is there an undervolt and underclock baseline that all Note 4s should be safe to start at?
Thanks.
Click to expand...
Click to collapse
Don't bother under clocking. The phone barely ever hits those top speeds and when it does its better to complete the process fast and quick rather then at a lower clock speed.
You can adjust the undervolt and under amp though, this will help your phone run a little cooler so it shouldn't throttle the cpu as quickly. It will not really help battery life though and you need to manually set it again after each boot.
Start with -45 under volt and -12 under amp (you need to under amp to compensate for the under volt) if the phone runs smooth (no lag or reboots for a few hours) then push it a little more.
You won't do any damage to the phone. If you push it too far it will just reboot and you'll be on default exceed settings.
I hope this isn't too dumb of a question, but I was wondering if I should flash the gpu drivers on my verizon Note 4. Thank you
dhplap said:
I hope this isn't too dumb of a question, but I was wondering if I should flash the gpu drivers on my verizon Note 4. Thank you
Click to expand...
Click to collapse
Yes they should work on all Note 4s. I run it on mine
Thunderoar Kernel For SM-T113
(Tab 3 Lite 7.0 Wifi)
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, corrupted partition, nuclear disasters
* Please do some research before using this mod!
* YOU are choosing to make these modifications,
* If you point the finger at me for messing up your device, I will laugh at you.
Features:
Overclocked
Deferred Timer for KSM
USB Fast Charge
Arch Power
Frandom
Powersuspend for battery life/saving
QuickWakeup for battery life/saving
Dynamic Sync Control
Fsync control on/off
Voltage Tweak
NVS hibernate driver
Multicore Power Saving
Schedule workqueues on awake CPUs to save power
CPU Boost
Adaptive Low Memory Killer
Software CRC control toggle
Gentle Fair Sleepers toggle
and so on...
CPU Hotplug:
AutoSMP
Added CPU governors:
Sprdemand
Conservative
Ondemand
Userspace
Powersave
Interactive
Performance
and so on...
Planned Update
-nothing i guess (but u can suggest somethin to me that possible)
Bugs(s)
-No MORE BUG!
Custom kernel Installation:
Download the kernel from here
Choose the tar.md5 if flashing from odin
Choose the zip files if flashing from custom recovery
Choose the latest version
Odin Instruction:
Open any version of odin
Choose your tar.md5 file from AP Tab
And Start
Custom Recovery Instruction:
Reboot into recovery if usin zip files (recommended to make a nandroid)
Flash the kernel zip
Reboot and enjoy!
Stock kernel Installation:
Download the stock kernel from here
Enter recovery mode, choose install, choose install image,
and then go to the directory of your downloaded stock kernel
choose it and then check mark on the boot circle.
And then flash it
Notes:
20/12/2107
Kernel Update!!
Thunderoar-Kernel 5.0 Codenamed "Angel Beats!"
Fix all issues regarding MTP not working
and random reboot, is this a comeback? xD, i don't know xD
It appears that my kernel uses a lot more memory than i expected,
Possibily some problem with memory patch in the kernel source
The workaround for this problem is you have to increase your disksize
In the kernel adiutor, if it stays at 300mb, it will not enough and cause a problem
Which is stuck or complete crash of device. Recommended size is 500mb or more if
you encountered it again and set swappiness into 60
XDAevDB Information
Thunderoar Kernel, Kernel for the Samsung Galaxy Tab 3 7.0
Contributors
@Thunderoar
Credits:
@Osm0sis-For the Anykernel2
@stathis95194-For the stock kernel
Github:
Kernel source
Version Information
Status: Stable
Current Stable Version: Angel Beats! || 5.0
Stable Release Date: 2017-12-24
Created 2016-12-26
Last Updated 2017-12-24
Press the "Thanks" button if you appreciate my work or if i helped you
Changelog:
V5.0 Codenamed "Angel Beats!" (2017-12-24)
+Kernel upstream version 3.10.17->3.10.108
+Gpu update
+Fix MTP
+CPU Frequency change 200MHz upto 1.5GHz
+Entropy Update
+Multicore Power Saving
+CPU Boost
+Arch Power
+Power Suspend
+Quickwakeup
+Read-ahead set to 512kB
+Adaptive Low Memory Killer
+Software CRC control
+Gentle Fair Sleepers
+Fsync On/Off
+Built from scratch and fixed random reboot
+Dynamic Fsync
-Removed Obselete Cpu Governor
-Removed Obselete I/O Scheduler
-Removed UKSM and use normal KSM
V4.1.1 update (2017-7-5)
+Fix some devices not booting
+New CPU Hotplug: AutoSMP
V4.1 update (2017-7-3)
+Just another update for stability
V4.0 update (2017-7-3)
+No more Reboot or similar effect - Tested
+Linux kernel downgraded into 3.10.32 temporarily because rebuilt from scratch
+Auto cpu boost on input without predefined frequency
+UKSM(Ultra Kernel Samepage Merging)
+LZ4 Z-RAM - Faster Memory
+Asynchronous Fsync -Faster storage management
+USB Fast Charge are back
-Removed cpu governor: OndemandX, Zzmoove, Scary *Temporary*
V3.4 update (2017-6-22)
+The most stable kernel that i've ever built
+Linux Kernel 3.10.44
+No more frequent reboot or similar effect
+Bug fixes
V3.3 update (2017-6-17)
+Linux Kernel 3.10.40
+Properly fix the bug that mentioned on the v3.2 update and lower the risk of instability
+A bunch of cpu governor
*Hotplug
*Lionheart
*Reworked version of intelliactive
*Ondemandplus
*OndemandX
*Hyper
*Zzmoove
*Nightmare
*Wheatley
*Badass
*Scary
*All of them are properly functioning and tuned for compatibility
and if you want the hotplug features, use the hotplug governor provided
+Bug Fixes
-Adaptive cpu governor removed parmanently
V3.2 update (2017-6-8)
+Update: Linux Kernel 3.10.37
+Update: Using the latest Anykernel2 zip
+Update: Minimum frequency change into 254MHz and also voltage change for nice battery lasting
+Update: cpu-boost set to 765MHz and running for 3 seconds when touch detected
+Update: Set CFQ as default scheduler
+Fix: Bug that cause long running app either in the background or foreground to freeze/lagging/reboot etc.
+Fix: Bug that cause the device to reboot randomly
+Fix: Bug that cause the graphic being not working/properly lagging or some sort
+Fix: Bug that cause the device to reboot or freeze when standby
+Fix: Bug that causing the kernel to working improperly/lagging/rebooting/unstable after a while
+Bug fixes
V3.1 update (2017-5-7)
+CPU Frequency minimum change -> 384MHz
+Fix Frequency bug stuck at 768MHz
+Faster charging
V3.0 update (2017-5-7)
+Kernel version updated from 3.10.22 - > 3.10.26
+Using updated Anykernel zip
+Frequency: changed into 1600Mhz and minimum is 386Mhz
+GPU: function updated
+Deferred Timer working as it is
+LZ4 compression
+"Schedule workqueues on awake CPUs to save power" are back
+Remove conflict between Samsung touch booster and my CPU-Boost so you can actually set the amount you want
for boost
+Sync threshold for cpu-boost are not set
+I/O scheduler default to deadline
+Fsync are on by default
+TCP Congestion Algorithm set default to Westwood which is the fastest for network usage
+Additional TCP Congestion Algorithm are added
+Additional tweak to make the kernel faster
+Camera Fix!!!
+MTP Function (unconfirmed)
+A whole lot of bug fixes
-sprdemand governor
-Fastcharge (for now)
V2.8 update (2017-1-31)
+Frequency: changed into 1660Mhz and minimum is 580Mhz
+Cpu-boost: defined stable values
+Less OS tearing
+Fastcharge updated
+Audio functionality improved
+Voltage: change for low-power use
+Many bug fixes
+Selinux: updated
-Automatic Cpu Hotplug: removed for better stability but with little to no battery drainage but you still can deactivate the cores through Kernel Adiutor
-Sprdemand: removed
V2.6.1-MR1 update (2017-1-1)
*Note:This is maintenance release therefore some features may temporarily unavailable
Add: cpu-boost currently disabled but provided as an option
Add: voltage change
Add: frequency change from 386Mhz to 1600Mhz for more stable
FIx: serious bug that causing switching off mobile data make it freeze/crash
Fix: bug that causing the device freezing/crash throughout all my kernel update release
V2.6 (2016/12/27)
+Initial release
After flashing all apps start to crash.
Jimbus369 said:
After flashing all apps start to crash.
Click to expand...
Click to collapse
Quick note on the crashing apps.
T113XXU0APE2: Does not have this issue
T113XXU0APH5: When I use this ROM, than indeed everything goes bananas after booting up the tablet.
Before flashing the kernel I advice to disable all unnecessary services and with that I mean everything with Samsung in the name and also all of the google apps you don't use. It seems that com.google.process.gapps is causing a crash chain reaction so do disable this services as first. I'm using lucky Patcher for disabling services and for those who are unfamiliar with this my advice is to not uninstall an app but first disable it and later when you are satisfied you than may safely uninstall the unwanted app/service.
Bugs
Camera doesn't working
My apps continue to crash in the latest version Also after a Dalvik wipe.
Build: T113XXU0APH5
Jimbus369 said:
My apps continue to crash in the latest version Also after a Dalvik wipe.
Build: T113XXU0APH5
Click to expand...
Click to collapse
All the app?
Thunderoar said:
All the app?
Click to expand...
Click to collapse
Yes, all apps.
This is extremely exciting and can't wait to try it out!
Build T113XXU0APA5
Will let you know how it goes....
Wanted to ask (not that it's a huge deal) is there init.d support in this kernel?
If so do I need to do anything special to enable it?
Going to go ahead with it anyway and see what happens!
Thunderoar said:
* If you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Better start laughing, 'cause my finger's pointing directly at you! And also twitching slightly out of frustration!
....Nah, it's all good. :highfive: I screwed things up all on my own by getting flash-happy. :crying:
On the plus side: It worked GREAT! :highfive: Thanks so much for putting this together for us tiny-tab users, you did a great job.
Not only did Byron (my T113's name) run smoother and faster than I've seen yet (yay!), but suddenly Mounts2SD had no issues whatsoever. Up till now it's been a supreme struggle to get /sd-ext to mount properly, to be used properly, etc. etc. - but after flashing this kernel, on first boot boom, everything just worked. Without changing anything I'd already done.
Should have just left it the way it was, eh? But noooo, I had to go "try something else" and made a stupid mistake somewhere, and now no combination of ROM / kernel / nandroid backup (meticulously organized and annotated) is booting up. I even lost TWRP for a little bit.... As penance for my sin of wanting "more", I've gotta dig up Odin, go back to stock, and start from scratch.
SO! QUESTION FOR YOU! (OR ANYBODY REALLY....)
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Not going to wait for an answer/s before moving ahead, but any response here will serve as documentation for myself and others in future!
(How don't we have a smiley for "pointing finger"? There's at least TWO in Unicode but I'm too lazy to go get it right now....)
PushyPhoenix said:
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
Click to expand...
Click to collapse
Yes, it will revert itself to its normal condition such as stock rom, stock kernel and everything
PushyPhoenix said:
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Click to expand...
Click to collapse
The kernel is in the md5 file or in the zip file, named boot.img
That's awesome to know, and came to the same conclusion when stock setup started asking personal questions and wanted a wifi password. Rooting it this very moment, though if I'd waited *just* a little longer I wouldn't have to. Wow you're fast!
That boot.img file info will come in handy when I screw up on any ROM, thanks! This one is going ASAP into a safe and accessible place for "just in case"....
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Feel free to point me elsewhere to learn more about how these things work, I've followed a lot of guides but want to understand the "why" as well.
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
That's awesome to know, and came to the same conclusion when stock setup started asking personal questions and wanted a wifi password. Rooting it this very moment, though if I'd waited *just* a little longer I wouldn't have to. Wow you're fast!
That boot.img file info will come in handy when I screw up on any ROM, thanks! This one is going ASAP into a safe and accessible place for "just in case"....
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Feel free to point me elsewhere to learn more about how these things work, I've followed a lot of guides but want to understand the "why" as well.
Click to expand...
Click to collapse
I do believe that when flashing a boot.img through TWRP with the image flasher, the file needs to say boot.img I may be wrong but I had issues before when I changed the name of the file to keep track of which one it was....lol... I have since started putting the boot.img files in their own folders with the appropriate name on the folder.
By the way, great to see development on this tablet. I am going to be testing this kernel in a personal build and see if I can squeeze as much out of it as I can get. So thank you dev.. Awesome work and greatly appreciated. : )
glockman4519 said:
I do believe that when flashing a boot.img through TWRP with the image flasher, the file needs to say boot.img I may be wrong but I had issues before when I changed the name of the file to keep track of which one it was....lol... I have since started putting the boot.img files in their own folders with the appropriate name on the folder.
Click to expand...
Click to collapse
That's a great idea... Ugh, adding another folder to the folder full of folders on my computer frightens me. But if that's what it takes!
Sent from my SM-G900W8 using XDA Labs
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
Thunderoar said:
Yes, it will revert itself to its normal condition such as stock rom, stock kernel and everything
Click to expand...
Click to collapse
So I've run into a bit of a problem. Tried outFyrestone ROM and i love it, but it's based on PH5 firmware and doesn't play nice with your wonderful kernel. Which means my sd-ext is broken...
I know you're very busy (and I haven't a clue what kind of work is required), but wondered if you know when we can expect to see an update?
Thanks so much for all your hard work!
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
That's a great idea... Ugh, adding another folder to the folder full of folders on my computer frightens me. But if that's what it takes!
Sent from my SM-G900W8 using XDA Labs
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
I get it, it clutters things s bit. But I am one who like an organized setup anyways so adding more folders is common for me. It may not be everyone's cup of tea so to speak.
But on my PC and in my external SD , on my tablet, I have a folder named tab "what ever", then inside there are folders named mods, ROMs, kernels and then gaops. In the kernel folder I have sub folders for just this reason and those folders will have the kernel name on it and then inside will be the standard "boot.img"..
It works for me and above all, works for TWRP.
Click to expand...
Click to collapse
First of all, sincere thanks for replying; this advice may help others as well
glockman4519 said:
PushyPhoenix said:
Ugh, adding another folder to the folder full of folders on my computer frightens me.
Click to expand...
Click to collapse
I get it, it clutters things s bit.
Click to expand...
Click to collapse
My apologies for not being more clear on what exactly 'frightens' me about this idea. There have been times when I've backed things up this way and couldn't get into them again because of the number of characters in the path and file name - they were just too long!
Mind you, this was tens of years ago on WinXP and it never occurred to me to try finding a fix.
But on my PC and in my external SD , on my tablet, I have a folder named tab "what ever", then inside there are folders named mods, ROMs, kernels and then gaops. In the kernel folder I have sub folders for just this reason and those folders will have the kernel name on it and then inside will be the standard "boot.img"..
Click to expand...
Click to collapse
That's a fantastic system, very similar to the one I'm now using, and will add new folders as you've suggested. Hopefully reading this will benefit those who are new to this world so they don't wind up with folders full of mysterious files and untagged backups for various devices, that made perfect sense at the time. (Like the one folder for my first few devices, which now looks like gobbledygook....)
Lollipop ROM for T113 (Samsung Tab 3 lite "7 wifi-only)
Topic:
Lollipop ROM for T113 (Samsung Tab 3 lite "7 wifi-only)
Is there any lollipop/marsmallow/Nougat ä ROM that works in my T113 (Samsung tab 3 lite "7)? This device runs natively Android 4.4.4, but I Really need Android 5 or higher! Lollipop would do just fine.. I took a look at most popular custom roms to this device, but most were 4.x.x.. And nothing for t113! And all of those were to T221 or so, in the list they're were few supporting T110/T111, but now T113. Does those work in this T113? Isn't it just same device?
Please tell me if you have any idea of rom with Android 5 or newer that works in this T113!
It would be awesome to have Lollipop-Slimrom or Resurrection remix with Android 5/6/7..
Even Stock Lollipop would be adequate, android 4 lacks important features...
There's many roms to this device, but they are for T2XX or T110/T111... Does any of those run in t113?
I have already rooted this tablet and installed TWRP.
Thank you so much for help in advance! Any information that gets me closer to have Lollipop or newer is very very much appreciated!
Sincerely,
tatu-o aka. mlc
PushyPhoenix;[email protected] said:
SO! QUESTION FOR YOU! (OR ANYBODY REALLY....)
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Click to expand...
Click to collapse
1.Yep
2.The stock kernel is in the md5 file which is boot.img, the md5 file I mentioned is in the stock rom
I guess I double answered this question, my bad :silly:
PushyPhoenix said:
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Click to expand...
Click to collapse
It varies, sometimes when flashing thing through adb or recovery with filename had a space in it, it would not detect it cuz the name is spaced and separated and it didn't recognize it as a file cuz the file extension doesn't connected to the name cuz it separated/spaced.
Thunderoar said:
I guess I double answered this question, my bad :silly:
Click to expand...
Click to collapse
Hahaa, thought it sounded familiar! No problem, better to get the answer multiple times than not get an answer at all.
---------- Post added 01-29-2017 at 12:01 AM ---------- Previous post was 01-28-2017 at 11:59 PM ----------
Thunderoar said:
It varies, sometimes when flashing thing through adb or recovery with filename had a space in it, it would not detect it cuz the name is spaced and separated and it didn't recognize it as a file cuz the file extension doesn't connected to the name cuz it separated/spaced.
Click to expand...
Click to collapse
Good to know! I've had so many issues over the years, with spaces in filenames, that any renames for files like this get an underscore or dash instead of spaces. Helps in lots of other ways, too.
Veno Kernel for Huawei HI6250 devices
Note: I'm waiting for Huawei to release new kernel sources with Nougat, until then I'll focus on fixing any bugs people find. New features will come with Linux 4.1.
The goalTo provide better battery life and more smoothness to your everyday experience, but without sacrificing one in the name of the other (so no +smooth/-battery tweaks and vice versa).
Maybe some extra features? I don't know, I hate unnecessary bloat that provides nothing to everyday user (or even developer).
Okay, so what's in?
Based on latest Huawei VNS sources from January 2017
Turns out newest sources are unstable, I rebased the kernel on 2016 release
Patched to 3.10.105 upstream
Built using Linaro 6.3 toolchain
DM Verity disabled
UKSM 0.1.2.6 (backported from Linux 4.0)
BFQ I/O scheduler
ROW I/O scheduler
Thunderplug hotplugging driver*
Dynamic Fsync
AnyKernel2 package! Compatible with any ROM except stock newer than B336.
For full list of changes see here.
* - Thunderplug is out for now, as it made the device unstable
Installation
Make sure you have TWRP installed
Create backup of your current boot
Flash the zip package (it will modify your boot instead of flashing entire boot.img)
Reboot and enjoy! Look below for how to use additional features
THAT'S A LOT OF CHANGES, BUT I HAVE NO IDEA WHAT I'M READINGA quick ELI5 then:
Patched to 3.10.105 upstream
Newer source = less bugs and better kernel in general.
Built using Linaro 6.3 toolchain
Kernel has extra ARM optimizations and phone is faster/has better battery life.
DM Verity disabled
Big brother won't know that you have fiddled with root.
UKSM
More free RAM and less CPU load, so MORE RAM, PERFORMANCE AND BATTERY LIFE.
BFQ I/O scheduler
ROW I/O scheduler Schedulers
With default settings phone will run smoothly even when you're playing FLAC music, compressing 10 archives of 5GB of music and banging your gf (I can't actually know that)
Dynamic Fsync
When you're using the phone, it cares more about your smooth experience than writing data to disk, so the system seems more responsive.
AnyKernel2 package
Can install on top of anything, Huawei is upgrading to kernel 4.1 with EMUI5 though, so flashing might be going backwards (this is 3.10), at least until they release new sources.
DOWNLOAD AND SOURCE
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Source code:
https://github.com/Avsky/kernel_hi6250_vns (unstable sources)
https://github.com/Avsky/android_kernel_huawei_hi6250_nem
Latest release: 2017-05-22
Download: https://www.androidfilehost.com/?w=files&flid=161384
20170406
Rebased on older, more stable Huawei sources (from 2016, everything else is the same)
Removed some of the debugging stuff from the kernel
Enabled Huawei hotplugging driver (it appears to only control big cores tho?)
20170405
UKSM patched to v0.1.2.6 again
Enabled/Disabled a lot of stuff in defconfig
Disabled mostly debugging stuff, which should result in slightly faster kernel.
Enabled a lot of USB drivers (so most stuff should work with Host Mode, if anyone ever uses that)
Enabled some missing Huawei code from older kernel sources, which I believe caused lowmem killer to go haywire, causing heavy apps to randomly close (I tested this one a bit, apps like Snapchat seem to no longer close, can never be sure)
20170404 - BUGFIX attempt
Rolled UKSM back to v0.1.2.3, should help with apps closing without any error
20170330
Removed Thunderplug, as it was causing freezes and bootloops (Huawei HMP doesn't like to have cores offline apparently), system should be stable now
Hotplugging will most likely return, with different driver or when Huawei releases 4.1 kernel sources.
My birthday release, yay, have a stable kernel everyone
20170329
Fix multiple lcd_notify calls
Protect against some hotplug race conditions
Run Thunderplug in per-core mode by default (gotta save the energy!)
Dynamic Fsync (ported to lcd_notify)
Fixes to backported UKSM (possibly fixes binder errors, apps not opening until reboot)
20170325
Initial release
Works with LineageOS 14.1?
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
Or nougat not supported?
RazOne said:
Works with LineageOS 14.1?
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
Or nougat not supported?
Click to expand...
Click to collapse
Yes, I'm running it on LOS 14.1 right now.
If somebody could test it on stock and EMUI5 ROMs (just for the heck of it, keep backup) I'd be grateful.
Sent from my VNS-L21 using Tapatalk
Installed succesfully on L31 running Resurrection Remix nougat. I will try for a few days and report back feedback
Will try it on EMUI 5 as soon as I have time.. very happy to see our device is getting devs' attention, keep up the good work!
Good afternoon. Your modification will work on EMUI 4 ?
thank you
upd.: on EMUI 4 it worked
http://cs5-1.4pda.to/9967169/Screenshot_2017-03-26-14-54-33.png?e28279d161430a29fd16f793d314a066
Hello
I have tested on vns-l31c636b361 (nougat), it does not start blocking your device is booting now ....
(I think I forgot the root)
I will re-try with but I get it with dload c636b170.
New try, l31c636b170 (emui 4) + twrp meticulus, ok :good:
Flashed it more than a day ago, working great on LineageOS 14 (VNS-L31), yet to find any issues...
Wat does it really do haha? Saw "whats in" but dont really know what that means hahaha.
Are you planning to add other CPU/ GPU governors?
uspy said:
Are you planning to add other CPU/ GPU governors?
Click to expand...
Click to collapse
It's something I'd like to do at some point, but there are very few governors which are properly adapted to octacore devices and none so far worked out of the box with Huawei kernel. I'm keeping my eye mostly on ElementalX and Impulse, but they'll need changes to even compile.
For now stick with interactive, next release with thunderplug enabled by default will bring better battery life.
Sent from my VNS-L21 using Tapatalk
It's really nice to hear that you are working on it. Thanks for your reply.
20170329 release
New release is out! Note that I wasn't running on a new build for very long, so issues might still surface, keep a watch on this thread.
Changes:
Fix multiple lcd_notify calls
lcd_notifier call was implemented in wrong section of Huawei LCD driver, oops.
Protect against some hotplug race conditions
Stability fixes mostly, based on ThunderZap kernels.
Run Thunderplug in per-core mode by default (gotta save the energy!)
Due to how scheduling works in Huawei kernel, it might keep one or two big cores up after heavy load, but should be fine once the screen is turned off.
Dynamic Fsync (ported to lcd_notify)
I moved Dynamic Fsync (thanks faux123) to lcd_notify to avoid kernel bloat from powersuspend or earlysuspend (which are not present in the kernel).
Fixes to backported UKSM (possibly fixes binder errors, apps not opening until reboot)
My derp in commiting changes might have caused critical fail in Android Binder, which resulted in random reboots and new apps not opening. Tell me if anyone encounters it.
Overall this release should bring much better battery life and smoothness to the system (mostly thanks to dyn fsync).
Download: https://www.androidfilehost.com/?fid=673368273298943375
Settings crash, dialer crashes when dialing any number after flashing latest release.
Anyway to unflash, or fix this? I didn't do a twrp backup prior to this, but I did do a cache/dalvik wipe after flashing.
Will a factory reset fix this? Or maybe just wipe /system in twrp?
I'm running stock b170 on vnsl21, meticulus twrp, rooted with magisk. I also have systemless xposed installed, maybe there's a conflict?
zgomot said:
Settings crash, dialer crashes when dialing any number after flashing latest release.
Anyway to unflash, or fix this? I didn't do a twrp backup prior to this, but I did do a cache/dalvik wipe after flashing.
Will a factory reset fix this? Or maybe just wipe /system in twrp?
I'm running stock b170 on vnsl21, meticulus twrp, rooted with magisk.
Click to expand...
Click to collapse
Ask someone for stock boot.img or extract it from huawei image.
Also logs, I need logs.
Avsky0 said:
Ask someone for stock boot.img or extract it from huawei image.
Also logs, I need logs.
Click to expand...
Click to collapse
So then, would a fastboot flash boot boot.img work to uninstall the kernel?
edit: I was just about to instal catlog to provide logs, while going for another round of dalvik/cache wipe and guess what - it seems everything is ok now. Will keep you posted if any issues arise.
zgomot said:
So then, would a fastboot flash boot boot.img work to uninstall the kernel?
Click to expand...
Click to collapse
Yes, that's how you flash kernel images. Also keep backup next time.
Sent from my VNS-L21 using Tapatalk
Also a question if I may. Would this kernel provide any benefits over the stock one if I don't install Kernel Adiutor and change any of the settings - basically just flash it and forget it?
edit: 2 questions if you could be so kind as to indulge me.
Does this modify haptic feedback? As it seems to me - either that or I'm crazy - that keyboard haptic feedback is different after flashing this. It's weaker and a little strange (?), however, navbar haptic feedback and other vibrations seem to be the same as with the stock kernel.
Thanks for your time
further edit for feedback: The fingerprint sensor is a bit iffy now. It's considerably slower sometimes, and generally slower and doesn't always vibrate on unlock, like 9/10 times it doesn't vibrate.
I flashed today's build and I noticed that only one core was active, and I can't turn on more than 4 cores so I can basically use 2 little and 2 big cores. Is this as it should be expected?
This development of RACER KERNEL for Pixel is suspended for a while. I should start after Chainfire comes up with a good root solution for O with Pixel.
XDA:DevDB Information
RACER PIXEL SAILFISH KERNEL, Kernel for the Google Pixel
Contributors
rachanta
Kernel Special Features: [3.18.52] [EAS] [SCHEDUTIL GOV] [TC-Linaro 6.3.1]
Version Information
Status: Testing
Created 2017-04-21
Last Updated 2017-05-26
Reserved
Reserved
Racer_pxs_20170421
RACER_PXS_20170421
Source Code
@MikeChannon the job is done. Thank you for your patience.
This is my base kernel for now It has O Preview 1 code (which has 7.1.2_MR2.1 merged in) + Linux 3.18.36 to 3.18.49
Do please let me know how it works for you.
safetynet patched? Does magisk work with it?
rohitece06 said:
safetynet patched? Does magisk work with it?
Click to expand...
Click to collapse
@rohitece06:
You can try magisk and let me know. Kernel is stable and stock. I haven't done anything specific about safety net, so no. I am new to Pixel. Pl point me to safetynet patches if possible.
rachanta said:
@rohitece06:
You can try magisk and let me know. Kernel is stable and stock. I haven't done anything specific about safety net, so no. I am new to Pixel. Pl point me to safetynet patches if possible.
Click to expand...
Click to collapse
I installed it on pixeldust rom and it broke the rom. dialer app disappeared. hangout stopped working. android auto started to force close.
I dont know how to patch a kernel for safetynet
rohitece06 said:
I installed it on pixeldust rom and it broke the rom. dialer app disappeared. hangout stopped working. android auto started to force close.
I dont know how to patch a kernel for safetynet
Click to expand...
Click to collapse
It runs fine with stock o preview. Its my daily driver. I'll see what pixeldust ROM is and figure out if it can be supported.
FYI kernel boots fine for me on 7.1.2 stock. Nice job!
RACER_PXS_20170423
Source Code
Runs beautifully with 7.1.2_MR2.1 Stock ROM
Mistake
Mistake
Mistake again
Oops
RACER_PXS_20170514
Changelog
Source Code
Features
Tool Chain: GCC-Linaro-6.3.1-2017.02-x86_64_aarch64-linux-gnu
OS Used to build : Ubuntu 17.04
Edit: Link refreshed with new build. I had two random reboots in quick succession after running for a while. Code simplified further. (c-picks trimmed from franco to flar level)
I have limited use with this kernel but my immediate impression is good. Apps and transitions seem to be a touch quicker. Everything is very smooth. Thanks for your work!
devilsadidas said:
I have limited use with this kernel but my immediate impression is good. Apps and transitions seem to be a touch quicker. Everything is very smooth. Thanks for your work!
Click to expand...
Click to collapse
Do let me know if you have reboots. MR2 has some scheduler commits, most of which I have excluded. I have kept scheduler largely at mr1-eas level in latest build. I am trying my best to cause stress to the phone and induce a reboot.
rachanta said:
Do let me know if you have reboots. MR2 has some scheduler commits, most of which I have excluded. I have kept scheduler largely at mr1-eas level in latest build. I am trying my best to cause stress to the phone and induce a reboot.
Click to expand...
Click to collapse
I havnt seen anything negative yet. Will let you know. Are you trying to stress your phone in test builds or trying to stress any phone with the newest release??
rachanta said:
Do let me know if you have reboots. MR2 has some scheduler commits, most of which I have excluded. I have kept scheduler largely at mr1-eas level in latest build. I am trying my best to cause stress to the phone and induce a reboot.
Click to expand...
Click to collapse
Still have random reboots
Klaa5 said:
Still have random reboots
Click to expand...
Click to collapse
An log or during which activity? I had a huge problem of data corruption and had to wipe the phone trying out a modded thermal conf, but none in normal use.
rachanta said:
An log or during which activity? I had a huge problem of data corruption and had to wipe the phone trying out a modded thermal conf, but none in normal use.
Click to expand...
Click to collapse
Mine is running smooth so far. Nice kernel! Stock may 7 1.2
Rebased build - the new starting point
RACER_PXS_20170518
Changelog
Source Code
All discussions will now be held in the Pixel XL thread as the kernel is fully unified!
Reserved
You may notice the feature list is a little bare. I wanted to get a nice solid base formed first then add features in as requested. Please read the thread before requesting a feature; if it is already present, just press thanks.
In theory, this should work on P as I have merged the source in. I have only tested on Oreo though.
Feel free to join Telegram for beta builds and hanging out https://t.me/joinchat/C1UAJ0OCAoJtDRo-hhkjhw
That's awesome
I think today or tomorrow, depending on my commitments, I'll flash P dp2 with this kernel and report if it's working or not.
Many thanks!
Yes, I confirm it's working perfectly with P, also using magisk 16.4, everything's fine :good:
TENN3R said:
Yes, I confirm it's working perfectly with P, also using magisk 16.4, everything's fine :good:
Click to expand...
Click to collapse
Would you mind share your TWRP version and your flash procedure? I flashed the kernel with boot_twrp 3.2.1-2 and then magisk 16.4, got bootloop.
Thanks.
Queentus said:
Would you mind share your TWRP version and your flash procedure? I flashed the kernel with boot_twrp 3.2.1-2 and then magisk 16.4, got bootloop.
Thanks.
Click to expand...
Click to collapse
Of course. First, you have to start with a clean install. A lot of people are experiencing bootloops with a dirty flash.
So first flash factory image performing wipe. Don't set a lockscreen, I got data unable to decrypt on latest twrp 3.2.1-2 (in oreo worked).
Then fastboot boot twrp. You can choose to flash or just boot twrp, your choice.
If you want to flash twrp:
- flash twrp zip
- reboot recovery
- flash Flash kernel
- flash magisk 16.4 (16.0 stable doesn't work on P)
If you don't want twrp to stick, just:
- flash Flash kernel
- flash magisk 16.4
Reboot. Done.
Thanks @nathanchance ! Been reading your thread in the Marlin section and I'm glad you're adding kcal. Just updated to Android P yesterday and will flash yours when I can.
I have a question though, I flashed some kernels on Android P, clean flash the factory image in-between every time. Some of them every time you reboot you'll be greeted with a message that says to contact my device manufacturer because there's an internal issue. You could press ok and the mess goes away.this happens precisely before the Android beta message pops up when system loads. So some kernels has that error message and some doesn't, does flash kernel act this way?
Arju said:
Thanks @nathanchance ! Been reading your thread in the Marlin section and I'm glad you're adding kcal. Just updated to Android P yesterday and will flash yours when I can.
I have a question though, I flashed some kernels on Android P, clean flash the factory image in-between every time. Some of them every time you reboot you'll be greeted with a message that says to contact my device manufacturer because there's an internal issue. You could press ok and the mess goes away.this happens precisely before the Android beta message pops up when system loads. So some kernels has that error message and some doesn't, does flash kernel act this way?
Click to expand...
Click to collapse
Fortunately this doesn't, only beta popup :good:
TENN3R said:
Fortunately this doesn't, only beta popup :good:
Click to expand...
Click to collapse
Thank you for the answer ?
Arju said:
Thanks @nathanchance ! Been reading your thread in the Marlin section and I'm glad you're adding kcal. Just updated to Android P yesterday and will flash yours when I can.
I have a question though, I flashed some kernels on Android P, clean flash the factory image in-between every time. Some of them every time you reboot you'll be greeted with a message that says to contact my device manufacturer because there's an internal issue. You could press ok and the mess goes away.this happens precisely before the Android beta message pops up when system loads. So some kernels has that error message and some doesn't, does flash kernel act this way?
Click to expand...
Click to collapse
My guess is other kernels are universally disabling verity; I only disable verity on custom ROMs: https://github.com/nathanchance/AnyKernel2/blob/marlin-flash-8.1.0/anykernel.sh#L64-L80
Good, thanks
Update!
Remember any and all bug reports need to include logs and clear steps to reproduce (see the info in the OP). You should also know what version it started with. If you want to be a tester and get builds before they are released here or just hangout, feel free to stop by Telegram!
Short changelog
Add the following features:
Backlight dimmer
Color control
HBM
Sound control
USB fast charging
Wake gestures
Wakelock blocking
Add kernel hardening from CopperheadOS
Convert several systems to use power efficient workqueues
Add upstream CFQ improvements
Some small performance/power savings commits
WireGuard snapshot 0.0.20180513
Downloads
Primary: http://nchancellor.net/downloads/kernels/marlin/8.1.0/stable/
Mirror: https://github.com/nathanchance/fk-zips
Commits
Kernel: https://github.com/nathanchance/marlin/commits/oreo-m4
Here's my SOT using this kernel on Android P. Browsed the web/social media, YouTube, watched latest episode of fear the walking dead and some other stuff, so medium usage I would say. I'm really happy with this kernel. Sorry for the language being in Swedish but I'm sure you'll recognize what's SOT and what's not, which is 3h 46min with 50% battery left.
Arju said:
Here's my SOT using this kernel on Android P. Browsed the web/social media, YouTube, watched latest episode of fear the walking dead and some other stuff, so medium usage I would say. I'm really happy with this kernel. Sorry for the language being in Swedish but I'm sure you'll recognize what's SOT and what's not, which is 3h 46min with 50% battery left.
Click to expand...
Click to collapse
Getting similar results here, about 2 hours chrome, 1 hour YouTube and the rest juice ssh. Got about 6hr total which is great for me. Great work @nathanchance!
Hi, thnx for the great kernel. Runs great on P dp2.
Would it be possible to implement double tap 2 sleep along with the rest already existing wake gestures? TIA
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
Hi, thnx for the great kernel. Runs great on P dp2.
Would it be possible to implement double tap 2 sleep along with the rest already existing wake gestures? TIA
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
I have never heard of double tap to sleep being a kernel feature.
nathanchance said:
I have never heard of double tap to sleep being a kernel feature.
Click to expand...
Click to collapse
Damn, never mind. Misread myself on another thread, sorry about that:silly:
Thnx for you're reply.
Cheers
Sent from my Google Pixel using XDA Labs
Final stats. Really pleased with how smooth this kernel runs and that the device doesn't run hot. The SOT is awesome especially considering that this is the Sailfish.
Arju said:
Final stats. Really pleased with how smooth this kernel runs and that the device doesn't run hot. The SOT is awesome especially considering that this is the Sailfish.
Click to expand...
Click to collapse
Those are some impressive stats! Question - did you change any of the kernel settings?