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
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.
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
I recently got my tab s7 sm-t870 for Christmas. I like it so far. I am trying to build TWRP and Lineage for it because only the 5g version is getting development. So i went and found out the source code for the wifi model is released by Samsung. I'm stuck on building a device tree from it though. I rooted the device so i can get the right blobs from it. If i were to succeed I will try to share it but I haven't used any file sharing sites so i don't know how that would work.
On second thought i should do twrp first before compiling Lineage but i still need a device tree
You might as well asked for the meaning of life...I doubt many will help with this. You maybe better off going to telegram and seeing if there is a dedicated forum, there maybe a dev there with more time or willingness
n0lan said:
I'm stuck on building a device tree from it though. I rooted the device so i can get the right blobs from it.
Click to expand...
Click to collapse
Have not done this before...
If I were to do this I would check out the github repositories of developers who are working on/publishing ROMs or recoveries for recent SAMSUNG devices.
Look what they use and from there find the equivalents for your tablet.
DHGE said:
Have not done this before...
If I were to do this I would check out the github repositories of developers who are working on/publishing ROMs or recoveries for recent SAMSUNG devices.
Look what they use and from there find the equivalents for your tablet.
Click to expand...
Click to collapse
hey i realized Ian has created a device tree for the s7 sm-t875 so i decided to clone it but when i lunch it complains that it doesn't exist in the config makefile. i'm getting so close but just need to figure out how to properly setup the files. I think the hard part is done finding something that would work. Do you have the knowledge of what I might be missing? This is the error
build/make/core/envsetup.mk:257: error: No config file found for TARGET_DEVICE gts7l.
Welp I just solved it it was just giving a different path in the BoardConfig.mk oops
You dont really lol.. samsung opensource is really just kernel source
elliwigy said:
You dont really lol.. samsung opensource is really just kernel source
Click to expand...
Click to collapse
wdym ??
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Well, I have the same phone. Couldn't find ROMs for it.
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Click to expand...
Click to collapse
look in this forum here, there are a couple floating around for it, I've made one, that I was able to fully flash to mine and has touch (Android 10. there's another that is 11 on here too by another poster), but as there are multiple display options out there it seems for how they were made, that is the sticking point, as not all will behave properly when booted into a recovery like mode it seems. I have tried installing it over bootloader and it will have touch then, but when flashed to recovery the touch never activates properly. So it all likely comes to that, as we'll need combine them in, properly applying proper checks for each display type and having it use the proper driver files, since can't load them all at once or it breaks things.
Working shrp for Borneo
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Click to expand...
Click to collapse
First place to start: twrpdtgen
Read the "readme"
Also check out:
[DEV]How to compile TWRP touch recovery
Device tree made from A10. Should still be relevant for A11.
Kernel for A10. Unfortunately I don't think Moto released the one for A11 yet. You can ask on their GitHub and devs might consider your request.
TWRP for A11. Touch is working.
Edit : here's a link for the device tree (in text) from A11
maybe this will work
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Click to expand...
Click to collapse
maybe this will help probably https://github.com/MotorolaMobilityLLC/kernel-msm
UPDATE: I have a telegram account where we are discussing how to make a custom lineage OS. I'm at the gathering stage and in the process of porting a device tree. For starters I want to start with lineage OS 18 because its the same android version the stock OS is, to be on the safe side, and that I've never done ROMS before.
Moto G Power 2021
I now have a device tree with the help of AOSPdtgen from the stock ROM from mirrors.lolinet: https://github.com/thebestofall007/android_device_motorola_borneo
I have started the build and got the first error:
https://imgur.com/a/XZoqy8B
I've looked this error up and they say it's because of the ram, but the error recurs at the same point. I have 16gb of swap, too.
thebestofall007 said:
I have started the build and got the first error:
https://imgur.com/a/XZoqy8B
I've looked this error up and they say it's because of the ram, but the error recurs at the same point. I have 16gb of swap, too.
Click to expand...
Click to collapse
you need alot of ram to build a rom for android 36GB of RAM or more will be beater to it wont crash
KILLFIREY1389 said:
you need alot of ram to build a rom for android 36GB of RAM or more will be beater to it wont crash
Click to expand...
Click to collapse
The error turned out to be entries in the proprietary-files.text file that needed to be deleted.
@thebestofall007 If you'll suceed. please take in consideration to build \e\ (aka deGoogled Lineage) too.
Here's a couple of interesting links that may help:
https://doc.e.foundation/support-topics/build-e
https://community.e.foundation/t/howto-building-e-roms-a-beginners-guide/26371
Last but not least, we've also suggested them (check here) to setup a "build (V)Machine" by modding this colab notebook to made it device agnostic:
https://github.com/viam1-dev/colab_lineage_build
Hope can "inspire" you.
Thanks in advance.
Does anyone have a complete list of sources so far? I have some experience in the past building ROMs for Android 5 and I wouldn't mind trying. I have a lot of computer resources to dedicate to building as well.
Device tree: https://github.com/thebestofall007/android_device_motorola_borneo-old
Does anyone know if there is a kernel source? I looked on the Moto github and couldn't find one. Is everyone using prebuilt for the time being? Also, do we need a vendor tree?
Thanks
Hello, So, I used to own a OnePlus 5t and I made the jump to Nord 2 because my 5t was not working.
Honestly, the stock rom is a complete disappointment. I can't use half of the apps without giving them permissions to location, contacts, phone, etc.
I mean why does camera need my location? The sad part is it won't work without it which is complete BS. Same goes for gestures and other features. like Why do these apps needs contact and phone access? I disabled most of the apps from adb and I am using Gcam for camera.
Sorry for the rant. Anyways, does anyone have any idea by when can we expect to have a custom rom for this phone?
There is some problem with kernel and oneplus just don't care about it. I think thats main problem right now. You can try GSI but there are some bugs.
USB make device panic on OnePlus Nord 2 5G OSS kernel · Issue #2 · OnePlusOSS/android_kernel_oneplus_mt6893
Hello, I noticied that USB were making kernel panic with the current source code released by OnePlus, it would be really usefull if that's fixed soon. Also, I request for MediaTek kernel modules an...
github.com
Until Oneplus don't release the full firmware it'll be difficult.
I've contacted the support though, and they say it will be published "soon"
Is this because its harder to make a custom rom for a mediatek soc? (or because mediatek wont release the firmware?)
8vasa8 said:
There is some problem with kernel and oneplus just don't care about it. I think thats main problem right now. You can try GSI but there are some bugs.
USB make device panic on OnePlus Nord 2 5G OSS kernel · Issue #2 · OnePlusOSS/android_kernel_oneplus_mt6893
Hello, I noticied that USB were making kernel panic with the current source code released by OnePlus, it would be really usefull if that's fixed soon. Also, I request for MediaTek kernel modules an...
github.com
Click to expand...
Click to collapse
Elixir Rom is there for OnePlus Nord 2