This is for developers, willing to contribute in for fixing Xposed on 64-bit Samsung devices.
If you're just a regular user, please don't post on this thread.
Now that deodexing Android 5.1 firmware is possible, I went on porting Xposed to Galaxy S6 Android 5.1 with almost the same procedures that I've done with Sammy's Android 5.0, but now with AArch64 compilation.
I managed to fix core-libart.jar to match AOSP's style until the point where Zygote completely dies without complaining which functions are missing or malfunctioning.
Seems like Samsung has played around ART runtime even more with 64-bit devices.
(PS, deodex'ed firmware without installing Xposed's new files boots just fine without issues)
Built with GCC 4.9:
Logcat - http://pastebin.com/WXvryB0m
Tombstone - http://pastebin.com/pKzb47nm
Sources are available at https://github.com/arter97/android_art/tree/samsung-lollipop-5.1 and
modified core-libart.jar is at http://www.arter97.com/browse/tmp/core-libart.jar
Re-building ART runtime completely with Clang compiler has revealed slight more debugging info.
Clang tombstone - http://pastebin.com/Ngemxy4H
Seems like somewhere between artAllocArrayFromCodeResolvedRosAllocInstrumented and BuildArgArrayFromObjectArray is causing boot issues.
oatdump can get somewhat debuggable info but I've yet to find a relation with the crash.
https://code.google.com/p/android/issues/detail?id=173420
@wanam also reported the almost same issue on Android 5.0 - https://github.com/rovo89/android_art/issues/9
This issue also made me think that it actually might be the Exynos 7420 issue itself, and Samsung has implemented a workaround just for it,
considering there're some AArch64 erratum fix commits - https://github.com/arter97/android_art/commit/d07021b38087ca0e385ebf46dd1b78239ed702b2 & https://github.com/arter97/android_art/commit/c5d9beb95d2c392820048ca42f582e4a50a9ca4d
I'm still working on how to fix this annoying issue.
If you have any ideas or tips, please let me know.
I'm having a hard time understanding if people can't see the very first paragraph on this thread.
No testers are needed.
arter97 said:
This is for developers, willing to contribute in for fixing Xposed on 64-bit Samsung devices.
If you're just a regular user, please don't post on this thread..
Click to expand...
Click to collapse
arter97 said:
I'm having a hard time understanding if people can't see the very first paragraph on this thread.
No testers are needed.
Click to expand...
Click to collapse
Mod Edit
Thread cleaned.
Please read people...
Thank you
malybru
Forum Moderator
@arter97 did you try the Cortex-A53 Erratum 843419 workaround in OatWriter? it is already included on the M previews, i tried to merge it with 5.1.1 sources but it seems it has some dependent commits.
wanam said:
@arter97 did you try the Cortex-A53 Erratum 843419 workaround in OatWriter? it is already included on the M previews, i tried to merge it with 5.1.1 sources but it seems it has some dependent commits.
Click to expand...
Click to collapse
No, I didn't saw that commit until now.
I'll try that later
wanam said:
@arter97 did you try the Cortex-A53 Erratum 843419 workaround in OatWriter? it is already included on the M previews, i tried to merge it with 5.1.1 sources but it seems it has some dependent commits.
Click to expand...
Click to collapse
I think grepping "64", "arm64", "AArch64", "Cortex" from Google's master branch's 'git log' might get us somewhere.
arter97 said:
I think grepping "64", "arm64", "AArch64", "Cortex" from Google's master branch's 'git log' might get us somewhere.
Click to expand...
Click to collapse
That's what I did, but I found only the two erratums 843419 and 835769 that seems related to Exynos, the first one was merged on the stock toolchain, but I'm not sure if there is any explicit option to enable the fix on the compilation.
wanam said:
That's what I did, but I found only the two erratums 843419 and 835769 that seems related to Exynos, the first one was merged on the stock toolchain, but I'm not sure if there is any explicit option to enable the fix on the compilation.
Click to expand...
Click to collapse
Merged to "toolchain"?
Sent from my SM-G920F using XDA Free mobile app
wanam said:
That's what I did, but I found only the two erratums 843419 and 835769 that seems related to Exynos, the first one was merged on the stock toolchain, but I'm not sure if there is any explicit option to enable the fix on the compilation.
Click to expand...
Click to collapse
Huh, ok, seems like Samsung is at least not using 843419.
I can't get any 843419 related fixes on built binaries.
I can't say the same thing as 835769 as its change is so minimal that it'll be hard to determine just from the binaries.
I'll try to enable 835769 later.
arter97 said:
Merged to "toolchain"?
Sent from my SM-G920F using XDA Free mobile app
Click to expand...
Click to collapse
I'm talking about this: https://android.googlesource.com/pl....9/+/6a20db030e486326e70968612662938d12d86a7b
wanam said:
I'm talking about this: https://android.googlesource.com/pl....9/+/6a20db030e486326e70968612662938d12d86a7b
Click to expand...
Click to collapse
https://gcc.gnu.org/ml/gcc-patches/2014-10/msg00906.html
Passing -mfix-cortex-a53-835769 enables that workaround for GCC. I'll also try that out later.
Another very interesting CyanogenMod Gerrit code review
http://review.cyanogenmod.org/#/c/103085/
It's a bit unfortunate that it seems it's actually quite common on AArch64.
http://www.slideshare.net/hidenorly/arm-cortex-a53-errata-on-andoid
Slide 8
Please note that ADRP is not used on L MR0 / MR1.
And then patches for 843419 are not needed.
Click to expand...
Click to collapse
Android 5.1 is MR1. So we can skip 843419
We're getting some progress here.
Finger crossed..
Nope. Dead end.
Those erratum commits still don't fix our issue.
More digging required.. GARR
@arter97 @wanam guys i guess u need @darkera13 maybe he can help u & join to urs for helping to fix Xposed for our S6 64 bit
Sent From My Awesome G920F Powered by EchoeRom
thereassaad said:
maybe he can help u & join to urs for helping to fix Xposed for our S6 64 bit
Sent From My Awesome G920F Powered by EchoeRom
Click to expand...
Click to collapse
lol.
Sent from my SM-G920F using XDA Free mobile app
arter97 said:
lol.
Sent from my SM-G920F using XDA Free mobile app
Click to expand...
Click to collapse
[emoji14]
Sent From My Awesome G920F Powered by EchoeRom
thereassaad said:
@arter97 @wanam guys i guess u need @darkera13 maybe he can help u & join to urs for helping to fix Xposed for our S6 64 bit
Sent From My Awesome G920F Powered by EchoeRom
Click to expand...
Click to collapse
I think we need someone with a good experience on binary analysis to decompile stock art libs and give us some hints about any specific commits used by Samsung.
Sent from my SM-N910C using Tapatalk
Related
This kernel will be kept simple and inline with stock and free from buzzfree stuff..as the aim is a stable day-to-day use kernel..this kernel is NOT for those who want to break records..as i do not believe and rely on benchmarks..(its me..)
Disclaimer:
i nor xda would be at fault if something weird beyond my test results happen to your phone..also this is not a benchmark kernel..if you like crunching numbers and breaking records go use another kernel..this is meant to save juice and be efficient and stable as a daily driver for Samsung based ROMS..
Features:
- Based on i9205/i9195 source from Samsung OSRC(Thanks for the borked source)
- Fixed a few things left by Samsung to be broken
- Simple and no fancy stuff thats gonna bork your phones..more stuff does not guarantee it's better..
- User voltage control from faux123 for Krait CPU's..
- EXFat support(by Samsung OSRC..)
- OC(if already stable)
- will populate more as things get stable
- Selinux permission is set from enforcing to permissive via ramdisk
- insecure boot image
- Disabled Rooting security measures implemented by Samsung..
Pre-requisites
- Install busybox via CWM or via Playstore before installing my kernel..this is to make sure init.d and also some scripts work properly..
Downloads here: Test build 5(ML1 Ramdisk)
My git: source
Credits:
- noone in particular but thanks to ALL the wonderful devs here in XDA..
If you like the builds please help me get a Soda/pay bills..or the least is just hit the Thanks Button..
one more in case..
uploading..
please report/feedback on any issue you might encounter..please do provide logs(last_kmsg, logcats, dmesg...etc..) so that i can shoot things out..i do not own the device yet and surely things can go wacky along the way..
TIA
kindly someone report if the build boots up..
What do you mean with those features?
- Fixed a few things left by Samsung to be broken
- Removed most of the crappy and buggy stuff..
- GPU Idling fix..
Click to expand...
Click to collapse
I cannot see them on your sources
Grarak said:
What do you mean with those features?
I cannot see them on your sources
Click to expand...
Click to collapse
will push them tomorrow(just have to know if the build boots or not)..samsung left an issue on the video drivers for ebook mode(scenario mode)..which can hinder compilation..why so curious?? you're the idol..
kairi_zeroblade said:
will push them tomorrow(just have to know if the build boots or not)..samsung left an issue on the video drivers for ebook mode(scenario mode)..which can hinder compilation..why so curious?? you're the idol..
Click to expand...
Click to collapse
I was curious how you described these features. If it's only an e book reader issue, you cannot call it remove crappy stuff by samsung.
Sent from my Galaxy Nexus using xda app-developers app
Grarak said:
I was curious how you described these features. If it's only an e book reader issue, you cannot call it remove crappy stuff by samsung.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
ok so if it bothers you then i will ninja edit it then..its just a general template i used on my previous OP..dont be so harsh on me..
update: edited it to "fit" your standards.. (what a way to welcome me here........now i can go to bed..and get my beauty sleep.. )
update: good morning guys!! any reports or comments if it boots up?? need feedbacks so i can start pushing more stuff..
I tried it on a I9200.
Device boots
No wifi
Lost root
For some reason, Google+ stopped working
Logcat attached.
Silesh.Nair said:
I tried it on a I9200.
Device boots
No wifi
Lost root
For some reason, Google+ stopped working
Logcat attached.
Click to expand...
Click to collapse
thanks will invetigate the logs provided..can you upload a stock image of the i9200 btw??so i can check if there are specific differences from the ramdisk of the i9200 from i9205..afaik aside from the LTE there should be other differences from them..
re: root it might have been because of the ramdisk i used..can you shift to Koush's superuser??chainfire's supersu has been finicky with my HTC 4.3 update but Koush's never had a glitch..
Thank you very much for the feedback!!
edit: get the SuperUser by Koush here
Stock MJ1 I9200 boot image attached. I'll let you know if I succeed to root.
Silesh.Nair said:
Stock MJ1 I9200 boot image attached. I'll let you know if I succeed to root.
Click to expand...
Click to collapse
can you pull me a last_kmsg from my kernel??it seems there is a hardware initialization issue..TIA
kairi_zeroblade said:
can you pull me a last_kmsg from my kernel??it seems there is a hardware initialization issue..TIA
Click to expand...
Click to collapse
Attached.
Silesh.Nair said:
Attached.
Click to expand...
Click to collapse
ok nailed down the culprit..will release a new test build in a few minutes thanks Silesh..it seems i was missing a few stuff..
kairi_zeroblade said:
update: new test build here OP updated as well
kindly test and provide feedback so i can push more stuff in..i have to do alot more maintaining also to my git..
Click to expand...
Click to collapse
I am testing my slimkat build. Will flash and let you know in an hour.
Silesh.Nair said:
I am testing my slimkat build. Will flash and let you know in an hour.
Click to expand...
Click to collapse
thank you it seems i made a minor derp..will fix it now..and upload a new kernel.
OK. When you upload, mention me so that I get a noification. Else I need to check the thread often.
Silesh.Nair said:
OK. When you upload, mention me so that I get a noification. Else I need to check the thread often.
Click to expand...
Click to collapse
update: get test build 3 here
kairi_zeroblade said:
update: get test build 3 here
Click to expand...
Click to collapse
Still no wifi. Root works, both SuperSU and Koush. Logs attached.
Silesh.Nair said:
Still no wifi. Root works, both SuperSU and Koush. Logs attached.
Click to expand...
Click to collapse
ok got it..will switch to the ML1 ramdisk you gave me..will post a new build in a few minutes..
edit: it seems i was messing with the UCNA2 update with SELINUX..thats why i was borking things..i am now using the ML1 ramdisk..
@silesh
new build up..here
Galaxy S5 aka kltetmo Hybrid Kernel
What is a Hybrid?
Hybrid kernel means the core although still has the 3.4.0 kernel label, it has incorporated many advanced features available only on Linux 3.8+ and beyond. I have backported many of those advanced features for Linux 3.4, hence the name hybrid!
Here's the flashable zip file
[ GSM (Tmobile USA) ]
Stable Release:
http://faux.romhost.me/kltetmo/kk44/
Beta Release:
http://faux.romhost.me/kltetmo/beta
Change Log:
http://faux.romhost.me/kltetmo/kk44/changelog.txt
Source here:
https://github.com/faux123/Galaxy_S5
Join my Kernel G+ Community for latest greatest betas here:
https://plus.google.com/u/0/communities/100266563627035551841
reserved 1
rserved 2
reserved 3
Looks promising! I'll test and report back. :good:
EDIT: It seems like it borked my wifi. I can connect to open networks but I can't connect to my saved network.
Only for the T-mobile version? Or will it also work on the G900F model?
Now I'm going to HAVE! to buy this device
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Question to the dev or anyone that knows, how do we go about installing the kernel will it be before or after flashing a rom? thanks in advance
Sent from my SM-G900T using Tapatalk
kevinpag said:
It seems like it borked my wifi. I can connect to open networks but I can't connect to my saved network.
Click to expand...
Click to collapse
No issues with wifi here, everything working well for me so far.
After installing the ROM
Sent from my SM-G900P using xda app-developers app
Can I assume that this is compatible with Faux123 Kernel Enhancement Pro
?
if so - can you offer any suggestions for settings?
mocsab said:
Can I assume that this is compatible with Faux123 Kernel Enhancement Pro
?
if so - can you offer any suggestions for settings?
Click to expand...
Click to collapse
of course
faux123 said:
of course
Click to expand...
Click to collapse
Faux, do you think this kernel will work on the G900F?
I'm asking this because the G900F rom's are working on the G900T.
Attempting to set GPU governor to simple_ondemand (using kernel enhancement pro) causes my phone to crash and reboot.
Glad to see you here - and happy you are creating kernels for the TMO S5 - THANKS
You offer a link to a beta but there is no file there - was that intentional - or are you waiting to upload the beta until later?
You listed this kernel as OC/UV -but I don;t see a way to do that - is that coming in a future release? (I can certainly wait for it - just wondering if I am not seeing something I should be seeing...?)
I've pulled the trigger... and flashed this kernel on my G900F... And it's WORKING!! :laugh:
It's working very smooth & nice on my own rom (see my signature).
So you can also post this kernel on the G900F forums if you want more users faux!
edgarf28 said:
I've pulled the trigger... and flashed this kernel on my G900F... And it's WORKING!! :laugh:
It's working very smooth & nice on my own rom (see my signature).
So you can also post this kernel on the G900F forums if you want more users faux!
Click to expand...
Click to collapse
thank you for verification. What is G900F? which carrier/nation?
mocsab said:
Glad to see you here - and happy you are creating kernels for the TMO S5 - THANKS
You offer a link to a beta but there is no file there - was that intentional - or are you waiting to upload the beta until later?
You listed this kernel as OC/UV -but I don;t see a way to do that - is that coming in a future release? (I can certainly wait for it - just wondering if I am not seeing something I should be seeing...?)
Click to expand...
Click to collapse
yes, the simple_ondemand from Qualcomm is very derpy. It will require additional patching before it can work.
faux123 said:
thank you for verification. What is G900F? which carrier/nation?
Click to expand...
Click to collapse
It's the international model. (Unbranded Qualcomm variant)
The forums for this model are: http://forum.xda-developers.com/galaxy-s5
how will this kernel affect battery life? by that i mean, if i leave all settings stock, will it increase or decrease my battery life from stock kernel or be the same?
After compiling roms for some time now i decided to dabbled in the arts of kernel building and modding.
Ok now i am back and i present you Winxkernel for nougat 7.1.1 stock rom. This time i will be able to continue work and update
this kernel when new sources and patches come out for our device. I have made a new website and I have also created a Google+ community page for this kernel and anything else i decide to work on. please share around. even if you dont like my work, maybe someone else might. i know that i will never be able to create a kernel like the greatest devs eg, yank, nathan, frap and franco, but i will certainly hope to learn from them about anything they have to give and possibly lend a hand.
Here is the download link
XDA:DevDB Information
WinXkernel, Kernel for the Huawei Nexus 6P
Contributors
winxuser
Source Code: https://github.com/winxdroid/kernel_angler
Kernel Special Features:
Version Information
Status: Alpha
Created 2016-08-10
Last Updated 2016-12-30
02/01/17
Update zram, zmalloc and add zpool
updated adreno gpu drivers
added ardreno idler
http://winxdroid.byethost8.com/Nexus-6p.html
30/12/16:
updated linaro to 6.2
added BFQ
couple interactive patches
exfat support
fsync on/off support
latest patches from 3.10 common branch
updated ICE driver
16/12/16:
upstream to latest f2fs updates for 3.10
add saftey net bootloader check (doesnt work with december security patch )
franco sound control
live display driver
removed maple
fixed kcal ( you can now change settings )
01/12/16
add msmhotplug
KCAL driver
fiops scheduler
maple scheduler
f2fs data and cache support
30/11/16
Rebased source to clean angler with 3.10.104
A few camera updates from CAF
16/08/16:
Cleaned up source
Added KCAL support
Added F2FS support
updated linaro toolchains
10/08/16:
Used android-msm-angler-3.10-marshmallow-dr1.6-1 as base
Updated to 3.10.102
Used lastest Linaro GCC 6.1 update
i will add the new security patches in for the next build
Thanks bro
Brokerzhang said:
Thanks bro
Click to expand...
Click to collapse
no worries, this kernel will also be in a rom im going to work on
Thanks.
Will it work on DP5?
leots1234 said:
Thanks.
Will it work on DP5?
Click to expand...
Click to collapse
Don't think so. But you could always try,, make sure you backup your boot partition first.
leots1234 said:
Thanks.
Will it work on DP5?
Click to expand...
Click to collapse
A kernel for M will not work on N due to defconfig changes (camera and some sensors will most likely not work).
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Good job mate. Can't wait to try your rom+kernel combo.:silly:
Will have an update in a couple days, not going to be home and I don't have a remote connection to my computer so I can't do it while I'm not home lol.. I have redone the sources so it shows all commits of changes up to 3.10.102, I will add the vulnerabilities patches for the next version and add f2fs support and kcal driver support
Sent from my Nexus 6P using XDA-Developers mobile app
winxuser said:
Will have an update in a couple days, not going to be home and I don't have a remote connection to my computer so I can't do it while I'm not home lol.. I have redone the sources so it shows all commits of changes up to 3.10.102, I will add the vulnerabilities patches for the next version and add f2fs support and kcal driver support
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
kernel updated guys, if there is anything you want in this kernel let me know and ill try and add it
someone who has my kernel installed, or can quickly install it can you scan for vulnerabilities please, I know I patched one, just need to know the others. I'm not home and won't be for a fair few hours, and I'm currently running N and not M
Sent from my Nexus 6P using XDA-Developers mobile app
Hey winxuser, I see that you have moved on from the i9305. Have fun with the 6p, and N!
P.S. Why were you inactive for so long?
limjh16 said:
Hey winxuser, I see that you have moved on from the i9305. Have fun with the 6p, and N!
P.S. Why were you inactive for so long?
Click to expand...
Click to collapse
Yeah I moved away from the i9305 when my phone stopped working and I got my 6p.. and there wasn't much more I could do, I'm not that great of a developer to have been able to completely fix the radio issue. I know the radio issue is kinda fixed but I think that's a big dirty hack to use cm12.1 as a radio backup for radio to work... I have been active since but no one really needed me anymore over there..
Sent from my Nexus 6P using XDA-Developers mobile app
hey guys im back, after some time of just trying out other things which has made me frustrated hahaha.
so i am back with a new kernel for N dev preview 7.1.1 only, im currently on dev preview 2 and its working well. i have also finally after a long time created a new website for my development, and i have also created a google+ community which is here https://plus.google.com/communities/101442640267768818970
Very nice website. Trying out the nougat build right now.
Can someone please tell me how can I change to f2fs on dp2 ?!
NOTilyass said:
Can someone please tell me how can I change to f2fs on dp2 ?!
Click to expand...
Click to collapse
The New kernel doesn't support f2fs just yet, will add it in to the next version
NOTilyass said:
Can someone please tell me how can I change to f2fs on dp2 ?!
Click to expand...
Click to collapse
F2fs make a difference on the 6P? Only tried it on the OnePlus One.
This info is intended to go for all developers that want to start/continue development on Android 6.0 and up, but every user can contribute to this discussion too.
The main purpose of the discussion is to find the root cause of our issues due to the new patches upstream.
Click to expand...
Click to collapse
Please rate and comment, so this can be on top of the Discussion Forum, since this is vital for future development.
Click to expand...
Click to collapse
Basic introduction:
From November 09th of 2016 and up Android is trying to patch the framework sources with file descriptor testing (fd), which is causing the mentioned bootloops across our platforms.
More about what FDs are can be found here --> https://en.wikipedia.org/wiki/File_descriptor
Specifically I have seen issues arising to Samsung devices, since that OEM always makes its own workarounds on libraries and framework, without supporting AOSP.
Conflicting commit:
https://github.com/CyanogenMod/android_frameworks_base/commit/b8be33b0bedec211708c4525b9d3f3b4effb385c
Click to expand...
Click to collapse
ROM expected behaviour:
FDs should be recognized and closed properly.
Click to expand...
Click to collapse
ROM behaviour after patch:
An unknown FD stays open (fd==5), and causes the ROM to be stuck into a bootloop, due to Zygote crashing.
Click to expand...
Click to collapse
A workaround has been made know as FD Whitelisting Procedure.
FD Whitelisting example commit:
https://github.com/CyanogenMod/android_device_asus_msm8916-common/commit/6392867d973715a84b4fa76a191b4d4c6d2e5d14
Click to expand...
Click to collapse
I have reported it to CyanogenMod and they are working on it.
Workarounds by CyanogenMod: (currently WIP)
https://review.cyanogenmod.org/#/c/174077/3
https://github.com/Bauuuuu/frameworks_base/commit/04fe03b3a6183537eb87c31030822e2e77571945
Click to expand...
Click to collapse
It has been reported by @rovo89 (Xposed developer) also. You can check the GitHub conversation below.
You will find a very good explanation on mostly everything related.
Xposed workaround:
https://github.com/rovo89/XposedBridge/issues/129#issuecomment-261721656
Click to expand...
Click to collapse
Mentioning for help:
@jackeagle
@TheWhisp
@CTXz
@DJ_Steve
(Attached logcat after cherry-picking https://github.com/Bauuuuu/frameworks_base/commit/04fe03b3a6183537eb87c31030822e2e77571945)
Let me know your opinion by commenting below. Thank you for your time.
@Nick Verse Maybe this is useful, look at lines 26 to 32. system_server.te. I know almost nothing of development but give me a couple of words and I'll look for it .
Griasahi said:
@Nick Verse Maybe this is useful, look at lines 26 to 32. system_server.te. I know almost nothing of development but give me a couple of words and I'll look for it .
Click to expand...
Click to collapse
No problem Griasahi! This file is for SELinux policy. (one of the files that tell the OS what to allow, in short, during building)
Thanks for your effort.
Helpful for devs!
Deleted.
There's a new kernel working on our P10, it was made for Honor 9 and updated to make it work on P10.
Here is the link to the thread Proto8 Kernel
Everything is working, wifi, bluetooth, hotspot, just try it yourself! The kernel is stable and very fast.
FEATURES
- Compiled with Linaro AArch64 GCC 4.9 2017.01 (ARMv8,A53 Optimized)
- UV (UnderVolt) on both CPU Clusters and GPU for better efficiency (All thanks to @nutcasev1.5)
- Energy Aware Scheduling (EAS) with "Sched" CPU Governor
- Kirin Hotplug Flow
- Aggressive GPU Suspend on Low Frequencies
- Swap disabled
- Reduced Kernel Wakelocks
- Advanced TCP Algorithms with "Westwood" Default
- Reactivation of the "setenforce" command
- Wireguard VPN Support
All the credits to @JBolho and @nutcasev1.5 for their work (hit the Thanks button :good
Download link: [url]https://www.androidfilehost.com/?fid=11050483647474829090[/URL]
Latest version: Version 2.0R - 06.29.18
Major Milestone Update
- Upstreamed to 4.4.73
- New Optimal Timer Frequency - 156HZ Set as Default
- Go Tickless - Enable Full Dynticks System
- Power Efficient Workqueues can now be toggled
- Revert CPU DDR Link Enabling and other HiSi CPU Functions
- Keep Kirin Specific SMP Flow but move to ARM big.LITTLE CPUFreq Driver
- Reduce Kernel Max Wakelocks down by 90% relative to Stock
- Minor RAM and DevFreq Tweaks
- GPU Scene_Aware Tuned for Power Efficiency
- Minor Log Spam on CPU's Silenced
- Reduce Timeout to Stop Processes and Enter Sleep
- Optimized Sound Output Gains and Eliminate Rates below 16Khz
- Implement UKSM 0.1.2.6
- Upgrade SchedTune Boost to v3
- Major Update to Spectrum Profiles to accomodate new features as well
- Update Wireguard to 0.0.20180620
sfoot13 said:
There's a new kernel working on our P10, it was made for Honor 9, here's the link: https://forum.xda-developers.com/honor-9/development/kernel-proto8-kernel-t3780551
I installed it yesterday and the only thing that is not working is the wifi and bluetooth.
Click to expand...
Click to collapse
Hey man, glad you liked it, but at least you could mention the Developers and at least give me a heads-up like "Hey, can i share the thread on the P10 forums?"
Kind of taken by surprise here
Thanks for the support.
JBolho said:
Hey man, glad you liked it, but at least you could mention the Developers and at least give me a heads-up like "Hey, can i share the thread on the P10 forums?"
Kind of taken by surprise here
Thanks for the support.
Click to expand...
Click to collapse
I'm sorry bro., I was going to add the credits later, but it was a mistake not to ask you before, sorry. (I'll edit the thread now)
Your kernel is very fast :good:
sfoot13 said:
I'm sorry bro., I was going to add the credits later, but it was a mistake not to ask you before, sorry. (I'll edit the thread now)
Your kernel is very fast :good:
Click to expand...
Click to collapse
Thank you. And it's not just me, @nutcasev1.5 is also Developer of the kernel.
kernel without wifi and bluetooth is kind of useless.
DallasCZ said:
kernel without wifi and bluetooth is kind of useless.
Click to expand...
Click to collapse
Not for me.
JBolho said:
Thank you. And it's not just me, @nutcasev1.5 is also Developer of the kernel.
Click to expand...
Click to collapse
@JBolho Done, I added the credits bro.
I don't know if is possible to fix the wifi and bluetooth for our device, I know that it was made for Honor 9, so if it is not possible, don't worry bro, and thank you so much
sfoot13 said:
@JBolho Done, I added the credits bro.
I don't know if is possible to fix the wifi and bluetooth for our device, I know that it was made for Honor 9, so if it is not possible, don't worry bro, and thank you so much
Click to expand...
Click to collapse
It's possible that it's just a matter of drivers, I'll look into it when I have the chance, but no ETA of course.
JBolho said:
It's possible that it's just a matter of drivers, I'll look into it when I have the chance, but no ETA of course.
Click to expand...
Click to collapse
Yes! :laugh: :fingers-crossed:
Thank you so much, take your time, I never ask for ETA.
One question: You'll need the stock drivers? Because I was searching and their are placed into Vendor/lib/modules, so what if I backup my stock drivers, flash your kernel and restore my stock drivers... I'll see if it works
Update: It didn't worked
sfoot13 said:
Yes! :laugh: :fingers-crossed:
Thank you so much, take your time, I never ask for ETA.
One question: You'll need the stock drivers? Because I was searching and their are placed into Vendor/lib/modules, so what if I backup my stock drivers, flash your kernel and restore my stock drivers... I'll see if it works
Update: It didn't worked
Click to expand...
Click to collapse
The proper stuff needs to be compiled in the kernel, don't brick your device in anticipation
JBolho said:
The proper stuff needs to be compiled in the kernel, don't brick your device in anticipation
Click to expand...
Click to collapse
While I'm waiting, I'll keep using your kernel
Thank you so much for the support. :laugh:
sfoot13 said:
While I'm waiting, I'll keep using your kernel
Thank you so much for the support. :laugh:
Click to expand...
Click to collapse
You have a PM, check it out.
JBolho said:
You have a PM, check it out.
Click to expand...
Click to collapse
Thank you so much, I'll check it
As confirmed now by @sfoot13 this kernel is now fully compatible with the P10. Separate download link added on thread's OP because both devices require separate compiles.
Remeber this was originally designed for the Honor 9 but from now on it should continue to be 100% compatible with the P10 as all incompatibilities have been apparently solved.
All the thanks to @JBolho :good: he made it possible
Thank you all for giving us a Kernel
I hope you don't mind the question: So it uses another energy management, does that mean there is no 'scrollable widgets freeze' bug?
Yes I could unlock and try myself but it's my daily phone at the moment :-|
Swaddy said:
Thank you all for giving us a Kernel
I hope you don't mind the question: So it uses another energy management, does that mean there is no 'scrollable widgets freeze' bug?
Yes I could unlock and try myself but it's my daily phone at the moment :-|
Click to expand...
Click to collapse
If there's such a bug, I've never experienced it, and it's more likely a rom thing, not the kernel fault...
My device is the only one I have and I need it everyday, so... This is not some "alpha ultra experimental thing" that may or may not explode on your pocket, so don't worry
Unlocking the bootloader does force a factory reset though. It's a pain, i know...
I also never had problem with widgets on this kernel and also on stock kernel.
To the actual users: how this is compared with hyperkernel from p10 plus?
Kernel has been updated to v1.2R, new and tuned I/O and updated CPU drivers and Sched Gov.