[GCC LINARO 4.7][Kexec-Enabled Multirom]COLOROS Samuk190's Kernel - ONE Android Development

Im not responsible for any damage to your phone
But i'm using this kernel as daily driver so its tested before release
Click to expand...
Click to collapse
It is optimized for battery savings in pmehra rom.
Click to expand...
Click to collapse
SAMUK190'S CUSTOM KERNEL Color OS MultiRom
Compatible Rom(ONLY):
Pmehra Color Os 2.1 (2.1.5i Final) (lollipop 5.0.1) : http://forum.xda-developers.com/oneplus-one/development/color-os-2-1-oneplus-one-rom-t3198594
Download Samuk190's Kernel Stable 3#( read more in the post)
https://mega.nz/#!N8NAmRhS!zUykrAM2VM3ffwMS0BAVmaBu8mXWFvSDSe2F0OlIKG8
ps: this is the first kernel made for oneplus color os rom, that is compatible with multirom ( i spent alot of time fixing errors, :silly
[old]
Download Samuk190's Custom Kernel Stable#1 : https://mega.nz/#!4oVgyJKZ!N17fAeVPdJOSyuP1dfx6kFY02pxKTRyHHyh36x-MgwQ
REBUILT stable#1 : https://mega.nz/#!8ksU2Kpa!a5n6tUogktz0uhp4qbG0wK-0BaEuNUda5ThihOKrhtg (same version, but a lighter version for people that have "bootloop stuck issue") (tested by myself) (same source, just removed some files)
Download Samuk190's Custom Kernel Stable#2
https://mega.nz/#!B8MFyIKb!vx0CAvC-bnV3PhnAUcW3I54w2R7Q6XG1CztXS6YxT2Q
Multi rom support, read more in the post for see how it works in my kernel. (tested, im using color os 2.1 from pmehra+ miui 7 x_s)
tip: you can flash a light rom(like miui) as secondary rom, to use NFC.
How to use multirom(internal ColorOS)
1.1CUSTOM KEXEC ENABLED[
What is?It's a half patch made by myself. you must flash COLOR OS in primary partition, and MUST reflash the kernel everytime you want go back to COLOR OS ( just use flashify in the secondary rom)
Advantages : Work's without bugs, Drivers are working good, and you don't need flash secondary rom kernel.
after flashing samuk190's kernel do this
Now lets make multirom work! #Method 1 (tested by myself)
Download MultiRom Manager
Install everything LESS KERNEL from multirom.
Now go to multirom menu, rebooting it.
Boot Internal ROM
Reboot
Install the rom you want , secondary, etc
Reboot to multirom select rom menu
Boot Secondary Roms(or any rom that is not internal)
If says "Kexec full patch need, blah blah, just enable no-kexec-workaround in twrp multirom"
After that , the phone will reboot to MultiRom Rom list menu
Boot secondary rom again, it will say : Booting with kexec or blah blah..
Profit!
To boot internal rom again(after booting secondary roms or any rom that is not internal)
Go to multirom boot and boot to your internal rom
It will redict to recovery due to the driver incompatibility bug.
Just flash boot.img in recovery(or with flashify inside the secondary rom)
Install > image > boot > samuk190'sboot.img
Inject current sector
Reboot and boot internal.
Easier way to make multirom work.
Download flashify app in your secondary rom
flash boot.img stable#2
reboot and boot internal rom
(do the same thing if you're on secondary rom again)
Instructions to flash kernel in fastboot :
turn your phone into fastboot mode.
do this at prompt(cmd)
fastboot flash boot (boot.img location).img
restart phone and wait.
About me
Hi, my name is Samuel! Im
Brazilian, and im new at the development and
i only have the OnePlus One.
Click to expand...
Click to collapse
What is Samuk190's Custom kernel for Color Os?
It's the kernel from pmehra with some bugs fixed, and some new features,slightly fast and the interactive governor back ( , big feature, it will have more features i promise )
Why you are working in this?
Alot of people complained of bad battery in color os 2.1 and some bugs.
Color os has the best drivers, best camera and sound, so it worth spend time at this project for a long time.
some devs don't like non-cm roms(because source incompatibility), so i'm decided to work with this.
With a better kernel, less lag, and fast phone.
It's for daily use!
What i'm working actually for this kernel :
Custom hotplug ( Missing compatible sources?)
Voltage Control(Problem with CPU_VOLTAGE_TABLE compatibility)
More CpuGovernors(every build i will add one any idea?)
NFC fix (hard to do, driver compatibility missing)
Maybe overclock? (hard to do, different kernel architecture, missing incompatibility with built source, need rework)
Custom Animation Boot(idk)
and alot of fixes that will impact in better battery optimizations
give your opinion
BEST configs for battery:
Battery configs :
ZzMoove min 300 max 840
Profile: 3 or 4
input boost > off
or input boost > 300 mhz
(Search in google for profile list, profile 3 is for battery yank extreme and 4 is for battery plus )
(dont forget to change zzmoove profile at kernel auditor)
Another good battery backup config>
cpu: conservative,min:300 max 840 mhz
cpu:smartmax,min 300 max 840mhz
Gpu : powersave
Changelog :
#Stable1
Fixed CpuFreq_interactive
added cpu interactive
Compiled with linaro 4.9.3 (fast)
Changelog stable #2:
Compiled with Google OFFICIAL NDK 4.7.3 ( better battery, no drains, same performance as 4.9.3)
KEXEC HARDBOOT SUPPORT (must be flashed in first partition) (better than nothing)
Smartmax governor
#Changelog Stable 3#
Added Zzmoove governor with 9 profiles(new!)
Added Adreno idler(200mhz when idle, so battery save)
Updated Adreno_Tz_Governor
4 cores online with low frequency is better than 1 core at high frequency, remember this.
Source:https://mega.nz/#!d4cgSR4R!w2fC5hp_jC8j3QkF-kvfMjGHNllXxPED8AZhQhiL9B8
Source#Stable2 and 3# included:here
screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks(sorry if i forgot someone):
@Lord Boeffla @pradeepsmehra
@acuicultor
@Andy1911
@DespairFactor

reserved

reserved2

Awesome. Keep up the good work bro. :good:

Could this kernel make the ROM compatible witj Multirom?

app kernel setting
which app you prefer to set the kernel?
UKM or KERNEL AUDITOR?

Your source code is missing. Do you want to upload every time 400mb? Github or Gitlab or something like that.
Sent from my A0001 using XDA-Developers mobile app

**** seems awsm ! gonna flash asap ! hope it gives me battery backup !

DerRomtester said:
Your source code is missing. Do you want to upload every time 400mb? Github or Gitlab or something like that.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Source code not missing, just unpack rar in linux (because if you unpack in windows as the windows is not case sensitive, the same files like xt_MARK.h and xt_mark.h will be replaced.)
i tried github, but it fails i will upload 400Mb everytime, no problem.
(but i will try upload to github again):laugh:

hyper_davide said:
which app you prefer to set the kernel?
UKM or KERNEL AUDITOR?
Click to expand...
Click to collapse
Kernel Auditor.
Ukm is good also, but i need release a version of ukm compatible with everything.

Richard20000321 said:
Could this kernel make the ROM compatible witj Multirom?
Click to expand...
Click to collapse
Yes, maybe in future. It's hard.
( i dont promise, but i will take this as a challenge )

Thanks for your wonderful work and effort, I see ur PM today, Sorry for that...
its joyful that u clear the blockage in compiling.
Color OS is amazing project and my first love in android world, but Oppo discontinued it because of so many developers got change and they mess-up everything.
if you need any help in future you can write me directly on my email.
[email protected]

samuk190 said:
Yes, maybe in future. It's hard.
( i dont promise, but i will take this as a challenge )
Click to expand...
Click to collapse
nice?good luck?

no flashable zip?

aliffaminuddin said:
no flashable zip?
Click to expand...
Click to collapse
no yet. just download flashable zip from another kernel,
and replace boot.img. then flash
or
in recovery you go to > flash > img > boot
and flash boot.img
I will make flashable zip in future.

samuk190 said:
Source code not missing, just unpack rar in linux (because if you unpack in windows as the windows is case sensitive, the same files like xt_MARK.h and xt_mark.h will be replaced.)
i tried github, but it fails i will upload 400Mb everytime, no problem.
(but i will try upload to github again):laugh:
Click to expand...
Click to collapse
Please give github or gitlab a try. Without it is impossible to follow your changes you did.

DerRomtester said:
Please give github or gitlab a try. Without it is impossible to follow your changes you did.
Click to expand...
Click to collapse
github problem with large files, so im trying github lfs, but lfs don't track all files.

is it fine that it takes time to reboot after installing this kernel?

samuk190 said:
github problem with large files, so im trying github lfs, but lfs don't track all files.
Click to expand...
Click to collapse
Does NFC work after flashing this kernel now?

Hey felow BR HUE... Please man, if you can do it, give us some Fast USB Charge Settings!
BTW thanks for working on Color OS!

Related

[RECOVERY][Codina] TWRP 3.1.1

TWRP
for
Samsung Galaxy Ace 2
aka Codina​
Sources
Device tree: https://github.com/ChronoMonochrome/android_device_samsung_codina/tree/omni-7.1
Recovery Source: github.com/ChronoMonochrome/android_bootable_recovery/tree/android-7.1
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation
1) before installation, make sure that you've installed chrono kernel (r5.2 version or up is required for TWRP 3.1.1)
2) flash zip file
Download
http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/recovery/TWRP
XDA:DevDB Information
TWRP for codina, Tool/Utility for the Samsung Galaxy Ace II
Contributors
ChronoMonochrome, SergeyL
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-05-22
Created 2015-04-18
Last Updated 2017-05-22
Reserved
Changelog:
22.05.2017
rebased to the CM14.1 device tree by SergeyL
updated to the latest omnirom 7.1 sources
removed a device-specific hack
increased the scrollbar width in the file manager
re-added an initial support for the dualboot feature
28.08.2015
updated to latest omnirom's 5.1 recovery source
fixed reboot sequence bug introduced in 2.8.7.0
adjusted brightness and disabled vibration intensity by default
reworked genfstab
19.04.2015
fixed not working taking screenshots (thanks @Epirex for hint)
removed using path to CPU temp as it doesn't work properly
16.04.2015
initial release
added /ramdisk partition to backup list
added path to CPU temperature interface (that doesn't work sometimes though )
Known bugs:
Report here if you have found any
About EXT4/F2FS
Whatever variants of filesystems on /cache, /data and /system (EXT4/F2FS) should work. However, only ext4 was tested by me. If you've encountered any issue with it, post here /ramdisk/twrp.fstab.
About installation on codinap
This installer should support codinap as well as codina. Otherwise report about it as I haven't tested installation on codinap.
Theme materialised
http://forum.xda-developers.com/galaxy-ace/ace-2-apps/twrp-materialised-t3066650
OMG @ChronoMonochrome you are doing a very good job for our device .As always many thanks!!!!
btw. later i upload new version of themes for TWRP
Edit: Themes Added
guys, is there someone, that for some reason prefer twrp?
I would hear..why, it amuses me, personally(backups, overall mgmt, you know ).
Is it matter of preference?
xo.en said:
twrp, cwm.. what's the difference...really(wrote by user of cwm).
(i mean for real, rom modding experience ),
i mean: allright, but this is clearly...matter of preference, not progress, yes?
Click to expand...
Click to collapse
Yep, this is matter of preference...
btw, guys, is there someone, that for some reason prefer twrp?
Click to expand...
Click to collapse
Not that I prefer TWRP or Philz(are we talking about philz?), I just wanted to get familiar with recovery building. Later, maybe I will be able to build ROMs (if it is possible on my machine). Even building recovery(with 4.4.4 sources) on x86 machine wasn't very easy, but at least it's possible. Some mess with default repos was needed.
I would hear..why, it amuses me, personally(backups, you know ).
Click to expand...
Click to collapse
What's wrong with backups?
ChronoMonochrome said:
What's wrong with backups?
Click to expand...
Click to collapse
Absolutely nothing..i lost my, uh, thought, sorry.
For us with cwm black screen it is very important to have TWRP for recovery.
A big thanks to Chrono for this
manthes said:
For us with cwm black screen it is very important to have TWRP for recovery.
A big thanks to Chrono for this
Click to expand...
Click to collapse
hm. i have not seen cwm blackscreen for year or so(s6d here), in old days only solution was to keep finger on screen in such cwm to see wtf is goin on.
Thing was related to kernel, idd, and definitely not to rom used, imho.
I have it all the time with CWM after cwm 5 or a version like that if i remember correctly. I dont know why. Maybe my s6d is more sensitive .
Before twrp it was a torture to test custom roms. However i think that TWRP is much more friendly.
And because we are just spamming right now i have to say that i test this recovery and it looks like that it is working fine (and it has better font)
manthes said:
And because we are just spamming right now i have to say that i test this recovery and it looks like that it is working fine (and it has better font)
Click to expand...
Click to collapse
..indeed, sorry for spam...it is good you found this fixed now anyway.
manthes said:
For us with cwm black screen it is very important to have TWRP for recovery.
A big thanks to Chrono for this
Click to expand...
Click to collapse
It's fixed on my Kernel and that from Chrono (latest Build).. at least on 20150405 it's 99,9% fixed .. just only one user of the whole world with s6d have still problems ..
btw: i've also s6d now, and even if i hardly OC that LCD.. i still don't have that blackscreen bug.. not on CM11 and not on cwm
ace2nutzer said:
It's fixed on my Kernel and that from Chrono (latest Build).. at least on 20150405 it's 99,9% fixed .. just only one user of the whole world with s6d have still problems ..
btw: i've also s6d now, and even if i hardly OC that LCD.. i still don't have that blackscreen bug.. not on CM11 and not on cwm
Click to expand...
Click to collapse
Sudden interest:
Tell me something: which settings of gov/i/o are used in twrp/cwm, where choice is taken from? Can we customize it? Or it is just some kind of lowlevel, generic thing?
xo.en said:
Sudden interest:
Tell me something: which settings of gov/i/o are used in twrp/cwm, where choice is taken from? Can we customize it? Or it is just some kind of lowlevel, generic thing?
Click to expand...
Click to collapse
Kernel defaults are used on early stage of system init(this is when ROM settings / init.d scripts aren't loaded). But since neither first nor second is used in recovery, there should another way to work around it. I've provided /ramdisk/00recovery that runs at very early stage (probably earliest possible). Almost same work does /ramdisk/00userinit , but it run only when you boot in system.
Uploaded new build
Changelog:
19.04.2014
fixed not working taking screenshots (thanks to Epirex for hint)
removed using path to CPU temp as it doesn't work properly
Click to expand...
Click to collapse
xo.en said:
Sudden interest:
Tell me something: which settings of gov/i/o are used in twrp/cwm, where choice is taken from? Can we customize it? Or it is just some kind of lowlevel, generic thing?
Click to expand...
Click to collapse
Yeah, i can only speak for my Kernel: I can set for every thing different Gov. I/O: CM, CWM, LPM (Offline-Charging) Also different LCD Brightness... and Different min. max CPU Freqs. and so on..
When i started to build the kernel for the first time, in CWM we had that config: (Default TC):
Performance Gov. (static 1Ghz !)
Brightness: 100%
Now it's running:
interactive, 400 - 800Mhz
Brightness 30% (also for offline charging, and CM bootlogo to save some power..)
EDIT: Nope, on my Kernel the User can only change Kernel tunables via init.d scripts ...(not for cwm and lpm)
ace2nutzer said:
Yeah, i can only speak for my Kernel
Click to expand...
Click to collapse
I dig you - so, lowlevel setting that is used in twrp/cwm relies entirely on kernel settings(set/edited before compiling)?
Recovery just uses settings made as default before compiling, yes? This is the point - can we affect this AFTER
I mean - recovery uses same thing that we see after firs boot(i.e. in performance control, chronokernel app, etc), right?
SO, now - can we, in example - add option to change lcd freq setting to cwm/twrp level anyhow, too?
Or this thing is related to different area(i mean - is kiosk mode(you know what i mean..i hope, here) able to manage such things?)?
Ok, post is edited to maximum possible clearity, no more edits...for now
xo.en said:
I dig you - so, lowlevel setting that is used in twrp/cwm relies entirely on kernel settings(set/edited before compiling)?
Click to expand...
Click to collapse
Yes. - in ramdisk, .. (boot.img)
Recovery just uses settings made as default before compiling, yes? This is the point
Click to expand...
Click to collapse
Yes
can we affect this AFTER
Click to expand...
Click to collapse
Nope, but if u use Chrono K. then yes.. because u can edit the recovery files .... just do inits ...
I mean - recovery uses same thing that we see after firs boot(i.e. in performance control, chronokernel app, etc), right?
Click to expand...
Click to collapse
Yes, but as i said, it's possibly to use different settings in recovery.. if it's writed as init on recovery files.. otherwise everything will run as kernel defaults ....
xo.en said:
SO, now - can we, in example - add option to change lcd freq setting to cwm/twrp level anyhow, too?
Or this thing is related to different area(i mean - is kiosk mode(you know what i mean..i hope, here) able to manage such things?)?
Click to expand...
Click to collapse
If you are talking about kernel defaults itself - then no, these values are hardcoded. However these values can be overriden by initramfs scripts (or by mentioned before script on /ramdisk). As I said it is only a matter of time, I mean it's only about when these scripts runs.
ChronoMonochrome said:
If you are talking about kernel defaults itself - then no, these values are hardcoded. However these values can be overriden by initramfs scripts (or by mentioned before script on /ramdisk). As I said it is only a matter of time, I mean it's only about when these scripts runs.
Click to expand...
Click to collapse
Till now, i can override what i want on cwm.. it works.... but the command need to write on the right file / place .. otherwise they are overwritten again by kernel... To check if it works or not, simply check with ADB
@ChronoMonochrome Why we need chrono kernel at first?
And can i use this on stock 4.1.2 with stock kernel? Because i always get blackscreen if i use temporary cwm.

[UKM for OP2] Install synapse and tune you kernel for your needs! [Works on CM13/HOS]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
Synapse is a kernel tweaking app developed by @AndreiLux that needs the Universal Kernel Manager (UKM) to work and it's developed by @apb_axel. It is one of the most complete choice for kernel management and it lets you fully unleash your kernel power, may it be battery saving, pure performance or a compromise between the two. You can find more information on UKM at this link: UKM xda thread
Screenshots:
What you need to download:
- Synapse
- UKM for Oneplus Two
- Busybox (i recommend this one) [N.B.: Busybox is not strictly required since there is an in-built busybox in UKM, but installing this updated one in my system has usually resolved stability issues with synapse]
- Root is required (use either SU 2.67 or later or in-built cm13 root)
Useful downloads:
View attachment Synapse.zip - flashable synapse that will install the app in /system
UKM uninstaller from official page
Useful links:
Official synapse/ukm thread
Official synapse google+
Instructions:
1. Download UKM from above link
2. Boot into recovery
3. Flash UKM
4. Reboot to system (no dalvik cache wiping required, but you can do it if you prefer)
5. Uninstall any kernel tweaking apps you might have (Kernel Adiutor, Ex Kernel Manager, Aero Kernel Control.....)
6. Install Busybox, open it and install busybox in system
7. Install Synapse
8. Launch Synapse
9. If you get "no UCI support detected" or synapse is not recognizing phone, just force close the app and re open or reboot the phone and you are good to go
10. Happy tweaking!
Click to expand...
Click to collapse
Protip:
If you want to be able to change cpu governors/frequencies you have to leave atleast one big core online in the hotplug section; once you have tweaked governors/frequencies, you can turn it off and restart synapse. You will have "Ssekbar error" but that's only because in MM/CM13 the phone is able to shut down all the big cores and if that happens the kernel tweaking apps are not able to change cpu values.
THANKS TO:
@AndreiLux for Synapse
@yarpiin for putting ukm together on opt
@ak for helping @yarpiin in his work
@apb_axel for starting UKM project
@benschhold for providing a good and stable custom kernel (actually the first working one for CM13)
@yarpiin again for his good kernel for cm13!
CONFIRMED TO WORK ON CM13/HOS, NOT TESTED YET ON OOS BUT SHOULD WORK, FEEL FREE TO TEST AND REPORT​
Disclaimer:
I am in no way responsible for any harm, damage, nuclear fission, universal big bang or you getting fired becaus alarm app didn't work that may occur to your device through the use of this app.
LIST OF CUSTOM KERNELS FOR OUR AMAZING ONEPLUS TWO
Kernels with built-in UKM (CM13):
Yarpiin Custom Kernel
Kernels without built-in UKM (CM13):
Benschhold cm13 kernel
N.B.: i'm putting in kernels still mantained and updated by developers and for latest versions of android only (MM); for anyone of you missing Boeffla kernel, i will include as soon as he develops new kernel for OOS 3 and cm13
Just in case
Just installed this. Upon installing busybox to system, and installing synapse.. Synapse did not recognize.. Restarted phone and then Synapse can be used.
Add in instructions: reboot phone after installing busybox to system
update: working great otherwise Now support for lower max cpu frequencies, only the input boost frequency. Hopefully kernel and synapse will support this ability
Is it possible to make it compatible with boeffla kernel on OOS??
Mohit31 said:
Is it possible to make it compatible with boeffla kernel on OOS??
Click to expand...
Click to collapse
It has been tested for cm13 only, but you can try it on oos with boeffla kernel and report if you had success
tlxxxsracer said:
update: working great otherwise Now support for lower max cpu frequencies, only the input boost frequency. Hopefully kernel and synapse will support this ability
Click to expand...
Click to collapse
Edit in instructions and added a protip section
Mohit31 said:
Is it possible to make it compatible with boeffla kernel on OOS??
Click to expand...
Click to collapse
I think it should work but might be buggy and also in Andis kernel there is more features than in CM 13 kernel im on CM 13 but will try to set OOS and see what can be done still as advised on Boeffla kernel Andis app is best to control his kernel
Awesome can confirm this is working on kingmercians hydrogen mm ROM with the stock kernel. Thanks. Also to the other users using boeffla there is no point in using boeffla and this its actually a bad idea just pick one
tlxxxsracer said:
Add in instructions: reboot phone after installing busybox to system
Click to expand...
Click to collapse
no, just swipe synapse away from recents and reload it, it'll work.
twist3d0n3 said:
no, just swipe synapse away from recents and reload it, it'll work.
Click to expand...
Click to collapse
Just to clarify there is builded in busybox into UKM and it use its own path , Ukm and synapse works regardless of busybox installed or not and regardless of busybox version installed
---------- Post added at 13:33 ---------- Previous post was at 13:31 ----------
And one more thing you have to be either on stock su provided by rom developer or latest supersu 2.67 older versions of su breaking UKM and make device unsupported error in synapse
yarpiin said:
Just to clarify there is builded in busybox into UKM and it use its own path , Ukm and synapse works regardless of busybox installed or not and regardless of busybox version installed
---------- Post added at 13:33 ---------- Previous post was at 13:31 ----------
And one more thing you have to be either on stock su provided by rom developer or latest supersu 2.67 older versions of su breaking UKM and make device unsupported error in synapse
Click to expand...
Click to collapse
I'll add in OP
Awesome work bro. I just love to use synapse for control kernel.
thanx .
As I mentioned on the BlissMallow thread, I had some problems getting UKM and Synapse to work properly with the latest ROM/Kernel (02-18/0.3).
Apparently this should work though, so I might have to give it another try.
Methroix said:
As I mentioned on the BlissMallow thread, I had some problems getting UKM and Synapse to work properly with the latest ROM/Kernel (02-18/0.3).
Apparently this should work though, so I might have to give it another try.
Click to expand...
Click to collapse
It is same zip what was your problem ?
Testing here with H2o skydragon, work perfect, great job
Sent from my ONE A2005 using Tapatalk
I'm unable to change the cpu governor ever since doing this.. I go back into kernel auditor and it doesnt even let me change the governor. Just shows a white box.
My phone will not go into deep sleep, whereas before it would
yarpiin said:
It is same zip what was your problem ?
Click to expand...
Click to collapse
I figured it was the same zip, so I've gone ahead and used the one I downloaded earlier.
I went through the same procedure as last time, apart from not clearing cache this time around.
This time it actually worked out!
I had to give the big cluster some time to cool down before I could tweak it, but this was the issue with AK's Kernel as well.
As to what went wrong the last time(s); I have no idea.
Thank you for bringing proper kernel management to CM13!
Happy that it worked
If i helped just it thanx
tlxxxsracer said:
I'm unable to change the cpu governor ever since doing this.. I go back into kernel auditor and it doesnt even let me change the governor. Just shows a white box.
My phone will not go into deep sleep, whereas before it would
Click to expand...
Click to collapse
Using two kernel management apps simultaneously is a recipe for possible disaster.
Flash UKM and install Synapse. Then uninstall or disable Kernel Adiutor.
Reboot and (possibly) rejoice.
Methroix said:
I figured it was the same zip, so I've gone ahead and used the one I downloaded earlier.
I went through the same procedure as last time, apart from not clearing cache this time around.
This time it actually worked out!
I had to give the big cluster some time to cool down before I could tweak it, but this was the issue with AK's Kernel as well.
As to what went wrong the last time(s); I have no idea.
Thank you for bringing proper kernel management to CM13!
Click to expand...
Click to collapse
Temp is not the issue but hotplug in cm13 all cores are hotplugged it means cpu 0 and 4 can be setted to offline and that make synapse to not pick up values from these two (they control scaling, govs and others).
Thats why ukm on boot triggers all 4cores online and they stay online until you change values in hotplug tab

[KERNEL][MM][DRM FIX] EliteKernel v3.4.33 [UB]

Elite Kernel
Unleash the beast
for Xperia Z3 Compact
First of all, I have spent a lot of hours on this project, trying to obtain the true power of this great device.
This Kernel is designed for optimize battery life and give more performance than stock kernel.
Features
Based on lastest sources, 23.5.A.1.291
DRM injection inside the Zip, you don't need flash DRM Fix, just kernel
OC up to 2,7Ghz
UC for better battery life
Optimized voltage tables and voltage control
Thunderplug v5.4, a load based hotplug and optimized for multi-core devices and it is very battery friendly with a great performance
IntelliThermal v2, a custom thermal control better than stock one
GPU overclock up to 657Mhz
Kcal control
More I/O schedulers like FIOPS, Zen, VR, BFQ...
init.d support
Power suspend driver v1.5
Build with UBERTC 4.9 and some optimizations
More stuff that I don't remember
ToDo
Add more governors
Share interactive governor tuned settings for battery and performance
More GPU optimizations
F2FS support
More battery life optimizations
Maybe Quick Chargue 2.0 support.
Maybe sound optimizations
Installation
Install my lastest TWRP (go here)
Make a backup of the partition System (MUST DO, because the kernel change some modules on system)
Select a version according to your needs. (See below)
If you have a TA partition backup:
Download EliteKernelZ3c-(current version).zip and extract the boot.img on your pc.
Use the ta_poc tool by munjeni with your TA partition backup.
Rename the new_boot.img to boot.img and replace it on the EliteKernelZ3c-(current version).zip
Boot on FOTAKernel recovery, with the phone power off, press at the same time power key and vol- until the phone vibrates.
Flash your EliteKernelZ3c-(current version).zip with the boot.img patched.
Enjoy!
Click to expand...
Click to collapse
If you don't have a TA partition backup (so you need DRM FIX):
Boot on FOTAKernel recovery, with the phone power off, press at the same time power key and vol- until the phone vibrates.
Flash EliteKernelZ3c_D-(current version).zip
Enjoy!
Click to expand...
Click to collapse
Usage with eXistenZ 5.6.5 (or similar Stock based ROMs) and Magisk
eXistenZ 5.6.5 includes a TWRP recovery inside the rom, and we don't need it since we have some options for recovery here, so for remove it download this file and flash it on recovery.
eXistenZ 5.6.5 also includes SuperSU on the rom and for correclty install magisk we need to remove it, so first of all update the SuperSU app on the Play Store, after go to the app and on settings there is an option for uninstall SuperSU and unroot the System, so tap it (Sometimes if it takes more of 3 mins, close the app and do it again), after that reboot the phone and done, SuperSU uninstalled.
Now the installation/upgrade of magisk using my kernel.
Download the lastest magisk zip and magisk uninstaller zip here, put they on SD card.
Reboot on recovery, uninstall magisk with the uninstaller zip if you have it, flash the kernel zip, flash magisk and reboot to system, and done, enjoy magisk.
Download
Z3c
Credits
@AndroPlus
@Myself5
@DooMLoRD
@pec0ra
@dorimanx
@faux123
@Doom Slayer a lot of thanks to this great dev
@dontbelive great dev and my Z3 tester
@BlackSoulxxx
@savoca
Source
https://github.com/ShadowElite117/Xperia-Z2-Z3
Changelog
v1
First release
Click to expand...
Click to collapse
v2
Based on new 23.5.A.1.291 sources
Click to expand...
Click to collapse
v3
Added missing conservative GPU Governor
Added Simple GPU algorithm
Added Adreno idler for battery saving
Added Fauxsound v3.6
More optimizations
Click to expand...
Click to collapse
v3.4.13
Kernel made from scratch, so no special features for now (Sorry guys I do this for a better kernel).
Implemented last_kmsg for a correct bug report.
Updated linux kernel version from 3.4.0 to 3.4.13 (Correclty done and free of strange bugs).
QC 2.0 enabled (don't expect miracles, it is limited on Z3 so it works with some QC 2.0 chargers)
Full compatibility with Magisk, eXistenZ and ta_poc tool.
Click to expand...
Click to collapse
v3.4.33
Updated linux kernel version from 3.4.13 to 3.4.33.
Enabled a kernel flag for try to enable Assertive Display on Z2 (It just give me logs that help me to know what is happening).
Dropped TWRP inside the kernel, since I have build newest TWRP for aries, for FOTAKernel partition. It has more features and it is more bug free than recovery inside the kernel.
Click to expand...
Click to collapse
FAQs
Q. How I can report a bug?
A. Give me a last_kmsg, tell me your ROM, if you have Magisk, Xposed Framework or similar things and describe me the problem.
Q. How I can contact you?
A. Please don't spam me with PMs, you can contact me on Telegram: ShadowElite117
This looks amazing, flashing now, thanks heaps!!!
I run slim 2.3, it based on 23.5.A.1.238. can I flash this kernel?
dddestiny said:
I run slim 2.3, it based on 23.5.A.1.238. can I flash this kernel?
Click to expand...
Click to collapse
Probably yes, since it is based on .575 and other kernels on this base work with .238.
Well guys how it is working on Z3c??
This is strange, guys...
Once we had no stock custom kernel - now we have three - which came out almost at the "same" time
@ShadowElite: Big thanks for this! Looks very prommissing! :good:
Especially build in DRM fix is nice as well as OC and UV.
I guess its time to move to MM
fluffi444 said:
This is strange, guys...
Once we had no stock custom kernel - now we have three - which came out almost at the "same" time
@ShadowElite: Big thanks for this! Looks very prommissing! :good:
Especially build in DRM fix is nice as well as OC and UV.
I guess its time to move to MM
Click to expand...
Click to collapse
Thanks, please feel free of test and report feedback
Finaly a reason to unlock my BL again
Testing in SLIMM 2.4 now doing very well and the performance is excellent the only problem I had is that I do not appear intellithermal in kernel auditor otherwise it's great and I threw AnTuTu score of 65884 xd thanks for your work
What does drm fix mean?can v unlock bootloader without loosing drm keys...
Edit-got wat it is.
One q...does this mean can use custom ROMs with camera quality as the stock?
subinsg said:
What does drm fix mean?can v unlock bootloader without loosing drm keys...
Edit-got wat it is.
One q...does this mean can use custom ROMs with camera quality as the stock?
Click to expand...
Click to collapse
It only works on stock based roms
Someone the same problem? Max Frequency is 2265, when I try to push it up it goes alone down to 2265. Don't know what to do? I tried the kernel auditor and some other tools. All the same?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Worked on slim rom .238
Cz this rom based on .575
Sorry for my bad english
alex20877 said:
Someone the same problem? Max Frequency is 2265, when I try to push it up it goes alone down to 2265. Don't know what to do? I tried the kernel auditor and some other tools. All the same?
Click to expand...
Click to collapse
For avoid bugs please make a clean installation
I made clean install and I have the same problem. It seams that frequency is lowered when the temperature increase
I flashed on 23.5.A.1.238_R5D_SLiMM_2.4 ROM and it isn't booting my device up now, what do i do?
Essyy786 said:
I flashed on 23.5.A.1.238_R5D_SLiMM_2.4 ROM and it isn't booting my device up now, what do i do?
Click to expand...
Click to collapse
If you can boot into recovery, try installing another kernel .
Essyy786 said:
I flashed on 23.5.A.1.238_R5D_SLiMM_2.4 ROM and it isn't booting my device up now, what do i do?
Click to expand...
Click to collapse
Is your bootloader unlocked?
Is IntelliThermal on kernel? Maybe I forget to enable it, please tell me

[KERNEL] [blu_spark r16 View 10] [8.1 EMUI / custom ROMs]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kernel features:
Build with custom toolchain Linaro GCC 4.9.4 2017.01
Full -O2 build with device and target flags enhanced, linaro build improvements, etc
Less is more: stockish builds from BKL-L04 EMUI8.1.0.107 source drop
Systemless installer (doesn't touch system/vendor partition, OTA friendly)
Removed some debug and logging options
ARM enhanced performance and battery patches
CVE security patches, general upstream and miscellaneous fixes
Several CPU Governors (blu_active modded own governor by default - fastlane mode available!)
cpu-boost CAF driver ported for kirin with some added improvements (Dynamic Stune Boost included)
No OC, use 300HZ base timer frequency
Enhanced TCP methods (westwood is default), Network and Wifi tweaks and updated drivers
Several I/O control tweaks, added schedulers FIOPS and ZEN v2 is default, tweaked and upstreamed filesystems (F2FS, ExFAT, NTFS, CIFS & NFS) (WIP)
Removed verify and doesn't force encryption, patched SafetyNet flags to pass CTS (WIP)
Stock thermal driver by default
Optimized crypto routines (WIP)
Swap and ZRAM off by default
Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel an FPR) (WIP)
Graphic stack fixes and reworked GPU driver
USB Fast Charge (USB mode up to 900mA with MTP on)
Battery/Notification LED control (WIP)
FS fsync toggle on/off
Wakelock blockers available
zx2c4's wireguard support
CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
init.d support (put your scripts in /system/su.d or /su.su.d [systemless SuperSU], /magisk/.core/post-fs-data.d [Magisk])
Compatible with Kernel Adiutor and others
DOWNLOAD KERNEL ZIP (No mirrors please)​
Warning: If you come from other kernel or have any issues, you should dirty flash your ROM before flashing blu_spark zip to avoid problems.
Reflash ROM -> if you want root flash SuperSU or Magisk (default, no plugins/modules) -> flash blu_spark.
If you are already rooted or upgrading between blu_spark versions, just flash the kernel zip. Also uninstall or clean data of any kernel control app you're using.
About bugs and troubleshoots: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock EMUI with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with modules, etc.
If you're using custom ROMs (including EMUI based ones) you're on your own. I'm only interested on debugging stuff in stock and stable EMUI.
Save the SOT and battery stats/screenshots for general threads, here we deal with development, not personal tastes and results.
Also don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" , no OT about OTAs, apps, ROM bugs, Recovery/TWRP troubleshoots and other userspace stuff. There's threads for it, use them.
Going back to stock: This kernel installer doesn't change your filesystem (systemless).
You can backup your ramdisk.img and kernel.img with TWRP before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
Honor View 10 development unit donated by Honor USA. Big shouts to them
Special thanks to @[email protected]_USA for being such a supportive person.
XDA:DevDB Information
blu_spark kernel for Honor View 10, Kernel for the Honor View 10
Contributors
eng.stk
Source Code: https://github.com/engstk/view10
Kernel Special Features: Powered by sparky
Version Information
Status: Stable
Current Stable Version: r16
Stable Release Date: 2018-05-31
Current Beta Version: r8
Beta Release Date: 2018-04-30
Created 2018-04-29
Last Updated 2019-11-29
blu_spark r8
All right crew!
blu_spark has made to Honor View 10!
First build is up :highfive:
Lot's of stuff merged in, we now have a nice and stable baseline to work with.
More of the usual missing goodies to come in future builds :fingers-crossed:
It was tested in L04 model with latest EMUI 8.1.0.105 so any other FW your results may vary.
To install you must use TWRP, @Pretoriano80 Unofficial TWRP is recommended.
You must have stock (or rooted) ramdisk and kernel before install.
blu_spark_r8-view10_66f0c4b.zip
build: use Linaro GCC 4.9.4-2017.01 for now
First kernel build with too much stuff to talk about, check git
ramdisk and installer changes to match View 10 stuff
Click to expand...
Click to collapse
Keep it real, keep it true, keep it blu :highfive:
Keep in mind: I will give no active support for custom ROMs (including EMUI based ones).
Meaning, if using anything besides stock and stable EMUI don't bother posting about it.
I am only interested on debugging stuff in stock and stable EMUI (with logs and reproducible steps to replicate the issue).
Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.
Also don't go spam and bug reporting on ROM threads if using this.
No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
nice glad to see linaro gcc was usable and was just something odd in my end... lol
for some odd reason on ubertc was usable as gcc fir me...
Nice job....
Does this support changing charging rate in KA?
Can i install this on BKL-L09 model?
kevp75 said:
nice glad to see linaro gcc was usable and was just something odd in my end... lol
for some odd reason on ubertc was usable as gcc fir me...
Click to expand...
Click to collapse
Yeah well try to check if you have any cruft or leftovers derping, I encountered similar situation when building.
venreddy said:
Nice job....
Does this support changing charging rate in KA?
Can i install this on BKL-L09 model?
Click to expand...
Click to collapse
No charge changes at the moment.
If fw is 8.1 should work, otherwise I don't know. Backup, try and let us know.
Sent from my blu_spark'd Honor View 10
eng.stk said:
Yeah well try to check if you have any cruft or leftovers derping, I encountered similar situation when building.
Click to expand...
Click to collapse
yeah, thought that too... did the same on fresh source download too tho
Got it to compile using Uber TC tho, so maybe I'll run with it and see what I can break LOL :laugh:
Woot
eng.stk said:
No charge changes at the moment.
If fw is 8.1 should work, otherwise I don't know. Backup, try and let us know.
Sent from my blu_spark'd Honor View 10
Click to expand...
Click to collapse
BKL-L09 is still with 8.0 emui.
I doubt this will work, but will try this later. It would not brick my phone right? Just need to back up stock kernel and fish it, if phone doesn't boot then flash backedup kernel. Right?
venreddy said:
BKL-L09 is still with 8.0 emui.
I doubt this will work, but will try this later. It would not brick my phone right? Just need to back up stock kernel and fish it, if phone doesn't boot then flash backedup kernel. Right?
Click to expand...
Click to collapse
backup both kernel and ramdisk
Rommco05 said:
Not bootnig on L09 LOS, stock kernel L04 don't boot too
Click to expand...
Click to collapse
fastboot flash your stock kernel.img and ramdisk.img
Rommco05 said:
Not bootnig on L09 LOS, stock kernel L04 don't boot too
edit: just telling
Click to expand...
Click to collapse
Thanks for testing. Hope Honor updates all the phones from all regions to Android 8.1 besides L04 devices :fingers-crossed:
Fragmentation is never good...
can i flash on BLA-L29 with emui 8 oreo 8.0?
fatalynx said:
can i flash on BLA-L29 with emui 8 oreo 8.0?
Click to expand...
Click to collapse
backup your ramdisk.img and kernel.img and tell us
(note, if you read the thread a little [like the couple posts above you], you'd see that it really only works on the US version, but, do what you want....)
Try to enable bonding mode inside defconfig, most of the new wifi driver support this option
scafroglia93 said:
Try to enable bonding mode inside defconfig, most of the new wifi driver support this option
Click to expand...
Click to collapse
I can checknit out, but some OEM don't enable that on 2.4G because it can introducr wifi issues with some APs.
Sent from my blu_spark'd Honor View 10
kevp75 said:
backup your ramdisk.img and kernel.img and tell us
(note, if you read the thread a little [like the couple posts above you], you'd see that it really only works on the US version, but, do what you want....)
Click to expand...
Click to collapse
will give it a shoot tq btw..
kevp75 said:
yeah, thought that too... did the same on fresh source download too tho
Got it to compile using Uber TC tho, so maybe I'll run with it and see what I can break LOL :laugh:
Click to expand...
Click to collapse
cross-compile is hardcoded in tzdriver/Makefile and will only use aarch64-linux-android-
https://github.com/UchihaDev/HyperPlus/commit/f04adc459eb60bcc1e22158ef6ae834e24929232
ajituchiha said:
cross-compile is hardcoded in tzdriver/Makefile and will only use aarch64-linux-android-
https://github.com/UchihaDev/HyperPlus/commit/f04adc459eb60bcc1e22158ef6ae834e24929232
Click to expand...
Click to collapse
Appreciate it mate.
Thanks for helping the noob compiler lol
fatalynx said:
will give it a shoot tq btw..
Click to expand...
Click to collapse
And already failed??
Sent from my HUAWEI BLA-L29 using XDA Labs
Tried on bkl-al20, cannot enter tne system.

[KERNEL][OP7/7PRO][18 SEP][ SkyDragon [OOS10]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Back again!
You may remember me from my SkyDragon roms/kernels and HolyDragon kernels for OP6/OP6T/OP3/N6/M8/M7/G3 among other devices. This is the latest sm8150 kernel+audio source from OnePlus. For now just some latency reductions and a couple listed features while I work on optimizing it. No plans for any overclocking cpu/gpu that slowly kill your phone. No plans to upstream anything as most of the time there's either no benefit at all or it performs worse than stock. I don't care about f2fs and recommend only ext4 as the stock filesystem. My only goal, as always, is to get the best performance *and* battery life out of our phone as possible. Kernel zip uses Anykernel3 by Osm0sis to install so no fear of losing root or ramdisk changes or anything.
~*~*Information*~*~
Flashable Kernel zip supports all OnePlus 7 and OnePlus 7 Pro(non-5G) devices running OOS Stable 10.x
Kernel source is based on official OnePlus 7/7Pro unified source code to ensure best performance
No user setup required - Optimal settings already applied
Compiled with Google Clang 9.0.5(r353983e) and gandalf02's aarch64-9.1 GCC
~*~*Features*~*~
250HZ Kernel
ExFat Support
No user clock-speed modifications
BBR TCP Congestion Profile (set as default
CRC Check Toggle-able (disabled by default)
Power Efficient Workqueue's Toggle (enabled)
Maple IO Scheduler (set as default)
Flar2's Wake Gesture support
KCAL
Boeffla Wakelock Blocker
Latest WireGuard Built-In
~*~*Credits and Thanks*~*~
xanaxdroid
SultanXDA/KernelToast
RandomBlame/Kelsirae
Pafcholini
MLucy
Flar2
MyFluxi
DespairFactor
FranciscoFranco
KDrag0n
Osm0sis
Mauronofrio
Joshuos
dabug123
~*~*Downloads*~*~
To Install :
Make sure bootloader is unlocked
Make sure you're on latest TWRP
Download this kernel zip
Reboot device to TWRP
Find this zip and install
Reboot to system and enjoy!
---
Could also copy zip or image to usb otg drive and flash in twrp
Do not flash with EXKM app
For Oneplus 7/7 Pro(Non 5G) and Oneplus 7T/7T Pro(Non 5G)
SDK_OP7TP_OOS10_RV.10.1
Flashable Zip
AFH
GDrive
--
Telegram Group
TG
Discord Server
Discord
~~~~~~~~~~~~~~~~~~~~~~~~
You can find changes(changelog) by looking at my posted source. You can also find my custom toolchain's, crosstool-ng, and other sources listed there. Any bug reports require logcats/dmesg, thanks!
~*~*Donations*~*~
If you want to donate to my coffee fund, I prefer any cryptocurrency over paypal but either is fine.
Donate with Coinpayments
or just use paypal, thanks!
XDA:DevDB Information
[KERNEL][OP7/7PRO][18 SEP][ SkyDragon [OOS10], Kernel for the OnePlus 7 Pro
Contributors
HolyAngel, Liam_Davenport, Imotep95
Source Code: https://gitlab.com/holyangel/OP7.git
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Current
Stable Release Date: 2019-05-23
Beta Release Date: 2019-05-21
Created 2019-05-21
Last Updated 2020-09-18
SkyDragon OOS Magisk Mod
Reserved
Reserved
Frequently Asked Questions
Before issues should be reported:
1. Rom needs to be clean flashed
2. No Xposed, AKT Profiles, Helix Engine, other magisk modules, or other mods, etc.
3. Do not restore any apps with TiBu or Swift or some other app restoring application
4. No Substratum themes installed
If you can still reproduce the issue you're having:
1. Logcat/logs must be provided with your report in order to receive any support.
2. I also need a full description of what happened, what you were doing when it happened, and a way to guarantee-ably reproduce the problem. If I or my testers cannot reproduce it, not only will it likely not get fixed, it likely isn't even an issue with the rom/kernel.
3. Screen record or picture of the issue is also helpful.
If you're not familiar with how to get logs, you can reference this great XDA Thread here.
If you can't give logs for errors or possible bugs, I literally cannot help you solve it.
Can't wait to try this out! Thanks!!
This could be a really dumb question, but could the zip be flashed in TWRP from a USB DRIVE..?
Or within an app like EX Kernel Manager?
reaper000 said:
This could be a really dumb question, but could the zip be flashed in TWRP from a USB DRIVE..?
Or within an app like EX Kernel Manager?
Click to expand...
Click to collapse
Not dumb at all, you could totally do either of those to flash it :good:
Wireguard support?
JedixJarf said:
Wireguard support?
Click to expand...
Click to collapse
No and won't be until they can pass a security audit. Says right on their site not to rely on their code until they do.
HolyAngel said:
No and won't be until they can pass a security audit. Says right on their site not to rely on their code until they do.
Click to expand...
Click to collapse
No problem thanks ?
Bacc at it again! Great job!
Excellent! I'm assuming Skydragon ROM eventually =).
SoullessMexican said:
Excellent! I'm assuming Skydragon ROM eventually =).
Click to expand...
Click to collapse
Yes will come when it's ready
Wouldn't you think that the CRC toggle is obsolete on any Oneplus device you support.
HolyAngel said:
CRC Check Toggle-able (disabled by default)
Click to expand...
Click to collapse
Hey buddy,
I was having a look at CRC check and what it does.
https://gitlab.com/HolyAngel/op7/commit/818f89d20f197ddf81aa2c8a40551b96173f2c2e
I've noticed your commit is in the mmc driver but given that we have UFS3.0 (not emmc 5.1) and that we don't have a micro SD slot, isn't this a worthless change because we will never be using mmc based storage?
Regards,
Ravi
Sent from my OnePlus7Pro using XDA Labs
Telegram Group
Are there any telegram groups for this kernel/rom?
@HolyAngel
Welcome & thank you.
@HolyAngel I flashed the kernel with EXM and after reboot it shows me a message: "There is an internal problem in your device. Please contact your manufacturer."
Hirs_E_Fruit said:
@HolyAngel I flashed the kernel with EXM and after reboot it shows me a message: "There is an internal problem in your device. Please contact your manufacturer."
Click to expand...
Click to collapse
If the same as on OP6, then you can dismiss it on each reboot. Last year it took a couple of weeks to figure out what caused it and it was subsequently addressed. It doesn't have any impact on the working of your phone.
Sent from my OnePlus7Pro using XDA Labs
rav101 said:
Hey buddy,
I was having a look at CRC check and what it does.
https://gitlab.com/HolyAngel/op7/commit/818f89d20f197ddf81aa2c8a40551b96173f2c2e
I've noticed your commit is in the mmc driver but given that we have UFS3.0 (not emmc 5.1) and that we don't have a micro SD slot, isn't this a worthless change because we will never be using mmc based storage?
Regards,
Ravi
Click to expand...
Click to collapse
Yeah most likely useless at the moment but the stock defconfig compiles the mmc driver anyways.
Hirs_E_Fruit said:
@HolyAngel I flashed the kernel with EXM and after reboot it shows me a message: "There is an internal problem in your device. Please contact your manufacturer."
Click to expand...
Click to collapse
Yes this is the message on boot listed in the op that will be fixed soon. Can safely ignore it.

Categories

Resources