Hi everyone.
I'm the developer of the 75Hz display overclock for Mi 9T. I'm working on a better / cleaner way to enable this mod, however, with sadness, I discovered that the kernel source code for Davinci (K20 / Mi 9T) is fundamentally broken. The section I'm talking about is the device tree, an important component which is used to control peripherals on boot. The source code provided by Xiaomi, once compiled, produces a binary that doesn't contain the information necessary to manage the Samsung display. This results in a boot with black screen. If you really desire a future for the custom development of this device, it's important to raise the matter to Xiaomi itself, in a public manner.
Let me know what you think of this and if you had a similar experience after compilation of the kernel source.
Thanks
# Edit: update
https://forum.xda-developers.com/showpost.php?p=79961451&postcount=6
That's sad to hear, planning to buy they mi9t in a couple of weeks ill be sure to compile the kernel and check if the issue is still present by then.
Thanks for bringing this up
we need to make know to xiaomi then
We as a community Need to step up and use social network to let Xiaomi know
Time to join our hands.
Made a breakthrough:
Unpacked dtbo.img from global firmware 10.3.6. Decoded the .dtb into .dts. Taken the 13 .dts relevant to the device (check Makefile). Re-encoded and repacked in a new, smaller dtbo.img.
I flashed this new dtbo.img through fastboot, booting successfully the device.
By taking the .dts provided by Xiaomi in the Mi 9T / K20 repo and compiling them, then packing them into a dtbo.img, and then flashing said .img through fastboot causes an unsuccessfull boot and a black screen.
So, I took the first .dts (from the source) and compared it to the correspondent .dts (from the decoded global firmware) and got this interesting diff (green one is the one working, red one is from the source that doesn't work):
https://pastebin.com/wNu0mVy0
So, there is obviously something wrong going on.
Zenkrey said:
Made a breakthrough:
Unpacked dtbo.img from global firmware 10.3.6. Decoded the .dtb into .dts. Taken the 13 .dts relevant to the device (check Makefile). Re-encoded and repacked in a new, smaller dtbo.img.
I flashed this new dtbo.img through fastboot, booting successfully the device.
So, there is obviously something wrong going on.
Click to expand...
Click to collapse
Have you tried taking the decoded .dts files and placing them in the kernel source tree to see if it builds a working kernel? (Or is that irrelevant, is it only used for building the dtbo.img?)
flubba86 said:
Have you tried taking the decoded .dts files and placing them in the kernel source tree to see if it builds a working kernel? (Or is that irrelevant, is it only used for building the dtbo.img?)
Click to expand...
Click to collapse
They would compile, of course, but that is not the best way to fix the issue. The problem, here, are the wrong commands used to control the display.
How this can be reported to mi team. i tried to post on mi community using mi community app. But other should also bring this forward.
manan001 said:
How this can be reported to mi team. i tried to post on mi community using mi community app. But other should also bring this forward.
Click to expand...
Click to collapse
Twitter
I tweeted looping mi team how they fix it soon.
https://twitter.com/mananbhatt86/status/1156039695807074305?s=20
manan001 said:
I tweeted looping mi team how they fix it soon.
Click to expand...
Click to collapse
give me a link to your tweet to retweet it.
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/issues/1116 give like here
Dev Dezigns said:
give me a link to your tweet to retweet it.
Click to expand...
Click to collapse
https://twitter.com/mananbhatt86/status/1156039695807074305?s=20
Is kernel source fixed?
Thank you so much for raising awareness
Related
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source（PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.
As there is no interest nor popularity on this device to stimulate a healthy developer community, I have decided to look into ROM building and what is required. I have followed this three part video in explaining how to build Lineage OS from source to a device. I have made it to part two where I download the Lineage OS source code to my Linux work-space. Where I get stuck is adding the source to the ROM. The question now is How do I attach the Lineage OS source code to the kernel source code for this device?
Information sources...
Part 1 https://www.youtube.com/watch?v=iZmjOlUq_3c&t=1s
Part 2 https://www.youtube.com/watch?v=MGI3NSJFtKA
Part 3 https://www.youtube.com/watch?v=AJCgOHtli64&t=153s
Current Kernel source code from Asus https://www.asus.com/ca-en/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
Just ordered one. I've never built Lineage OS either, but maybe we can work together to figure it out.
I have the lineage OS sorce code ready to compile on my system. I just need to know how to add the nesary kernel with it. Any ideas?
Any progress?
Sent from my [device_name] using XDA-Developers Legacy app
Nope! Unless you have anything to contribute.
someaguy said:
As there is no interest nor popularity on this device to stimulate a healthy developer community, I have decided to look into ROM building and what is required. I have followed this three part video in explaining how to build Lineage OS from source to a device. I have made it to part two where I download the Lineage OS source code to my Linux work-space. Where I get stuck is adding the source to the ROM. The question now is How do I attach the Lineage OS source code to the kernel source code for this device?
Click to expand...
Click to collapse
I also looked into building Lineage, seems like it's going to be more than I'm willing to commit to, so I'll share what I found in hopes that it will help you or anyone else move forward with this.
I found this restored CM wiki page on the subject: fat-tire.github.io/porting-intro.html (Sorry, can't make it clickable since I'm new)
The gist seems to be that you need to make three directories in the lineage source (note z01kd appears to be the codename for the Zenfone 4 based on the build.prop file I pulled from my phone)
device/asus/z01kd - Device file tree
kernel/asus/z01kd - Kernel
vendor/asus/z01kd - Proprietary blobs
In the above CM guide, it says to use ./build/tools/device/mkvendor.sh to generate the Device file tree from a boot.img file extracted from an update.zip (from Asus) or extracted from the phone, but that didn't work with the version I was trying to do (15.1), mkvendor.sh wasn't there at all. So I explored option #2 which was to fork an existing device file tree repo from a similar device and tweak it for the device you want to port and I found that the Zenfone Max Pro M1 (X00TD) (github.com/LineageOS/android_device_asus_X00TD) is the closest lineage supported device that we could copy from (at least that I could find). It looks like you might even be able to use the same kernel as that device (github.com/LineageOS/android_kernel_asus_sdm660) because the SOCs are pretty close (Snapdragon 630 vs Snapdragon 636), but you may need to use the stock kernel that you linked to in your original post, not sure.
There's a part in the lineage docs about building from source (only for supported devices) (wiki.lineageos.org/devices/X00TD/build#extract-proprietary-blobs) about extracting proprietary blobs (wiki.lineageos.org/extracting_blobs_from_zips.html) for the vendor/asus/z01kd folder. It said that you could use a lineage update.zip, but I was able to do it with the Asus update.zip. Don't know if that will work or not, but it seems like the only option since the Zenfone 4 doesn't have a lineage update.zip to pull proprietary blobs from.
And that's about as far as I got
Once you have those three folders set up and properly configured you should in theory be able to build it.
Update 9/3/2018
I just found the device file tree and kernel for Zenfone 4 that @shakalaca used to build TWRP. Looks like there are some different naming conventions from what lineage would expect (omni_Z01K.mk vs lineage.mk), but a lot of the stuff looks to be the same (eg BoardConfig.mk) and the files that do have a different name look like they're roughly equivalent.
github.com/TeamWin/android_device_asus_Z01K - Zenfone 4 TWRP device file tree
github.com/shakalaca/android_kernel_asus_ze554kl - Zenfone 4 TWRP kernel
Between these and the above X00TD device file tree and kernel links, we should be able to get pretty close to a working config.
What if you compile what you have and see if it boots on your device?
someaguy said:
What if you compile what you have and see if it boots on your device?
Click to expand...
Click to collapse
Sorry...I already deleted the environment I had set up, to reclaim the 50+ GB of disk space.
If it's any consolation, I never made it far enough for it to build successfully.
I am trying to build Lineage OS too
In this guide(https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763)
It says we need three files(device tree,kernel,vendor) to build it.
We have kernel and device tree from github(https://github.com/TeamWin/android_device_asus_Z01K)
but we still need vendor from our device,and the commend under this guide(https://www.isthnew.com/archives/build-lineageos.html) says that we can get vendor files by running "extract-files.sh".
But where can we find that?
(Sorry for my bad English
rol.
try to look here.https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
I have tried that CLT project,but it didn't work
Maybe use this?
https://forum.xda-developers.com/axon-7/development/tool-party-v0-1-vendor-partition-t3831517
hello again peeps,
ive been gently banging my head around these past few days because i keep walking into knowledge pockets and nothing i can find, in the form of help or internet information, is filling in these holes. i originally planned to take my oneplus device and obtain the source code for oxygenos so i could build and customise it. this seems to have become a dead end so now i just want to build stock android via AOSP, but i dont understand what software i need to get the AOSP working on any device, so far i understand that you need 3 components; 1) Kernel 2) Vendor files (if any) 3) "Proprietary binaries".
The problems are, i have no idea how to obtain these "proprietary binaries", i have no idea where to put any 3 of them in the downloaded android source tree (after repo sync), and i dont know if thats all the information i need to atleast build and flash a stock image onto any phone. i think i have the kernel files i need on OnePlusOSS github and there is a vendor.img in the OTA update files, and a directory in my phone. if anybody could please guide me in the right direction, it'd be very cool. i just want to get started and have some fun.
0
Seppppx said:
You can't customize Oxygen Os as the source code doesn't exist for that. (It's not required for companies to publish that.)
What phone do you have? You already might have the required trees to build AOSP (or at least LineageOS)
You need
1. A Device Tree
2. The kernel (you can use the prebuilt kernel if you really want)
3. The proprietary vendor blobs located in the vendor partition.
You will probably have to download the aosp-caf source code instead of aosp for it to be more easy.
https://www.youtube.com/channel/UCnGqG_jyyXmTzdamBpKfeHA
This is a great channel about Android building and has about everything you need to know.
Click to expand...
Click to collapse
thank you for every inch of text in your reply. I have a oneplus 8. Ah right, so the vendor folder CONTAINS the proprietary binaries/blobs.
it seems safest for me to use the kernel in the manufacturers github for the first flash as i want to be careful with making changes. may i ask what "aosp-caf" is? or can i find out using the resource you provided? thank you again.
my new understanding is, you need; 1) android source (e.g android-10-r5) 2) kernel 3) proprietary blobs. this helps a lot and is a lot clearer. the last issue i have is with knowing where to put the kernel and the blobs. i think if i am not mistaken you put the blobs in a vendor folder after the build? i am unsure with the kernel. i am going to definitely check this guy out. your time means a lot to me.
I have a Mi 10S where I really want to have an AOSP-like ROM installed. However, this model was only released in China so there isn't a corresponding board here at XDA where I can find some decent ones off the shelf. I am personally familiar with programming so I think it would be a good idea to port one myself. I choose Pixel Experience because it's popular and it has quite some documentation.
To my knowledge to port a ROM I need both a base ROM and the source code for the new ROM. I now have in hand a fastboot image of Mi 10S's official MIUI. Furthermore, Xiaomi seems to be open-sourcing its kernel source code and device tree (which I suppose is good news?) On the Pixel Experience end, I follow the guide on their website and cloned and initialized their repo. It seems that all I need then is to create a device configuration for PE's build system, but I don't know where to start.
I do know that PE has a port for Mi 11X (alioth), which uses the same CPU as my phone. Interestingly both models seem also to be sharing the same device tree and kernel (in the same branch on Xiaomi's github repo). I suppose then I can copy Mi 11X's device configuration for PE and tinker with it a bit. However, the structure of Pixel Experience's device configuration doesn't really resemble the device tree I see on Xiaomi's website (I suppose either of them is "non-standard"?), so I am stuck not doing what to do next. Any suggestions?
Well did you tried a generic system image
Generic system images | Android Open Source Project
source.android.com
I have the same problem. I don't know where to begin after I created build environment as per Pixel Experience build tutorial.
Anyone can shed some light?
Null Pointer Exception said:
I have a Mi 10S where I really want to have an AOSP-like ROM installed. However, this model was only released in China so there isn't a corresponding board here at XDA where I can find some decent ones off the shelf. I am personally familiar with programming so I think it would be a good idea to port one myself. I choose Pixel Experience because it's popular and it has quite some documentation.
To my knowledge to port a ROM I need both a base ROM and the source code for the new ROM. I now have in hand a fastboot image of Mi 10S's official MIUI. Furthermore, Xiaomi seems to be open-sourcing its kernel source code and device tree (which I suppose is good news?) On the Pixel Experience end, I follow the guide on their website and cloned and initialized their repo. It seems that all I need then is to create a device configuration for PE's build system, but I don't know where to start.
I do know that PE has a port for Mi 11X (alioth), which uses the same CPU as my phone. Interestingly both models seem also to be sharing the same device tree and kernel (in the same branch on Xiaomi's github repo). I suppose then I can copy Mi 11X's device configuration for PE and tinker with it a bit. However, the structure of Pixel Experience's device configuration doesn't really resemble the device tree I see on Xiaomi's website (I suppose either of them is "non-standard"?), so I am stuck not doing what to do next. Any suggestions?
Click to expand...
Click to collapse
I have a version shared by the Chinese. However, it has a fingerprint error
Hey Realme GT 2 Pro fam,
Guess what, realme released the Android 13 kernel and vendor sources for GT 2 Pro
Kernel source: https://github.com/realme-kernel-opensource/realme_gt2pro-AndroidT-kernel-source
Vendor Source: https://github.com/realme-kernel-opensource/realme_gt2pro-AndroidT-vendor-source
This should help us get a decent custom rom and recovery
Is this complete?
kkffiirr said:
Is this complete?
Click to expand...
Click to collapse
It appears so from the looks of it. Haven't had a chance to compile. Hopefully any devs can get us started with custom roms and recoveries.
Will anyone risk developing anything for this device with all the restrictions OPPO put in place for MSM flash tool?
Maybe we get some custom kernels for battery life improvement, I am hyped
dick_vigarista said:
Will anyone risk developing anything for this device with all the restrictions OPPO put in place for MSM flash tool?
Click to expand...
Click to collapse
This
and
is gt2pro getting sold in india?
because my impressions since being a flashoholic is:
98% of custom rom/stuff/kernel comes from indian pro dudes
ChillDuder said:
This
and
is gt2pro getting sold in india?
because my impressions since being a flashoholic is:
98% of custom rom/stuff/kernel comes from indian pro dudes
Click to expand...
Click to collapse
the gt neo 2 got some dev love
Finally!
Hopefully someone can make the factory rom better. Would be nice if someone could remove the bloatware and remove the thermal throttling. Android 13 c.08 cant run wildlife stress test because the phone force closes it and givese warningw that its tok hot. Not to mention games like Apex and Genshin Impact are also loosing fps after a few minute due to throttling.
Hi,
I have tried to compile the kernel but have come across an issue.
I have reported this to Realme github as an issue and hope they get back to us as soon as possible to resolve this.
I have linked the issue in this message incase someone knows a solution:
N/A · Issue #1 · realme-kernel-opensource/realme_gt2-AndroidT-kernel-source
N/A
github.com
Shaky156 said:
Hi,
I have tried to compile the kernel but have come across an issue.
I have reported this to Realme github as an issue and hope they get back to us as soon as possible to resolve this.
I have linked the issue in this message incase someone knows a solution:
N/A · Issue #1 · realme-kernel-opensource/realme_gt2-AndroidT-kernel-source
N/A
github.com
Click to expand...
Click to collapse
Did you compile for GT 2 Pro? The issue which you've filled is for GT 2 and not for GT 2 Pro.
GitHub - realme-kernel-opensource/realme_gt2pro-AndroidT-kernel-source
Contribute to realme-kernel-opensource/realme_gt2pro-AndroidT-kernel-source development by creating an account on GitHub.
github.com
Israel_Tom said:
Did you compile for GT 2 Pro? The issue which you've filled is for GT 2 and not for GT 2 Pro.
GitHub - realme-kernel-opensource/realme_gt2pro-AndroidT-kernel-source
Contribute to realme-kernel-opensource/realme_gt2pro-AndroidT-kernel-source development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thanks, I have now reported this in the correct kernel source code repo:
Kernel source code failing to clean and compile · Issue #1 · realme-kernel-opensource/realme_gt2pro-AndroidT-kernel-source
Hi, Running "make clean", "make mrproper" or "make distclean" results in the following error: scripts/Makefile.clean:15: drivers/power/oplus/v1/adapter_ic/Makefile: Not a directory make[5]: *** No ...
github.com
I have partially resolved the issue by changing toolchains. I now receive the following error when compiling:
"error, forbidden warning: page_alloc.c:7843:27"
Anyone have any ideas?
Hi,
I have compiled the kernel, unsure if it boots ( I dont have time to test this yet ).
I have attached the kernel image (requires packing into a boot.img).
If testing, try fastboot boot boot.img. DO NOT FLASH THIS KERNEL!!!
Edit: Tested and its not working