Related
This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13
Reserved
Edit 1:initial build didn't boot for me, no adb can't get log
Ok im gonna try it.
If you want, i can leave logcat for you
OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.
Ofc, it doesn't boot. And don't create threads without testing.
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.
Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought
Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar
Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.
Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha
You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.
Hello everyone,
the question and disscussion is:
Do we get Lineage OS support in the Future? it does not matter if unofficial or official, but what do you think?
I saw the LeEco le Max 2 get some unofficial support, so it could be that some Devs will try it.
It would be awesome *_*
I think the problem is, that the community isn't that big like for the le Max 2, but maybe it will get bigger in the future.
What do you think? :good:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
I think, it's not discussion, but it is a question. So, it should be in "QUESTIONS & ANSWERS". Le Max 2 have bigger community, because this phone is cheaper and cheapest Le Max 2 was for 180-200$. This mobile is older. Our Le Pro 3 have few months and in future it could have more community and ROMs like this.
corvus said:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
Click to expand...
Click to collapse
Wooow! Someone interested?
It would be awesome!
:fingers-crossed:
Who could we talk to in order to get official support?
I dont know, but to get official support there should be at first a stable unofficial lineage OS Version. I do not know much about creating ROMs but i hope someone does and will create a masterpiece for le pro 3
I hope so
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
corvus said:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
Click to expand...
Click to collapse
Hi Corvus,
I've been trying to build slim from the repo you forked, but it keeps telling me I have no recovery, and ends up erroring out. I tried on ubuntu 16.04 lts though, could be my issue. Gonna try your lineage 13 version.
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
Would be awesome. I will try your build!
Good project looking forward to
manuelbvb said:
Would be awesome. I will try your build!
Good project looking forward to
Click to expand...
Click to collapse
I'll edit a link to the thread I make with to-dos based off the source code I can see.
Here's where I'll post progress!: https://forum.xda-developers.com/le-pro3/development/progress-lineage-os-13-t3546126
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
Hi @jts2111,
No problem from my side. TS team shared with me the sources, I modified them for Lineage, and try to do some tweaks (already uploades) and have some more in local, but causes some problems, so I didn't upload them.
With this image I get more than 3 days of batt time and a sot of 8 hours, so it's good for me. My only concern is that I was not able to make Camera2 HAL working to get manual settings. But I have little time to test, so any help from this side is welcome.
Only one thing, please, share the code in a public repo so TS, me or any other developer can see it and work together.
Thanks
---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
robertzas said:
Hi Corvus,
I've been trying to build slim from the repo you forked, but it keeps telling me I have no recovery, and ends up erroring out. I tried on ubuntu 16.04 lts though, could be my issue. Gonna try your lineage 13 version.
Click to expand...
Click to collapse
For Slim, please use the fork from where I get the code. See it in github. It's TS source, so it should work.
corvus said:
Hi @jts2111,
No problem from my side. TS team shared with me the sources, I modified them for Lineage, and try to do some tweaks (already uploades) and have some more in local, but causes some problems, so I didn't upload them.
With this image I get more than 3 days of batt time and a sot of 8 hours, so it's good for me. My only concern is that I was not able to make Camera2 HAL working to get manual settings. But I have little time to test, so any help from this side is welcome.
Only one thing, please, share the code in a public repo so TS, me or any other developer can see it and work together.
Thanks
Click to expand...
Click to collapse
I forked your repo and shared it in my post. I'll work on what you mentioned. One of my top (long term) goals is complete CTS compatibility. With safetynet passed, there'd be nothing that would really pull you back to stock.
Definitely, I'm preparing the Kernel code after code to ensure we get a very clean and functional Kernel for the future, instead of just merging the one from LeEco with more than 80% of unneeded bits due to their other devices being at the same place (shameful).
This will get a ~30MB Kernel reduced to around 12MB and thus make custom ROMs perform a lot better and boot immensely faster after all.
I'd only need one sense of common attitude which is asking LeTV to keep the Kernel source up-to-date when they launch OTAs as well, I've seen some comments regarding their image stabilization fix at latest release (OTA) which is only possible at Kernel/blob level and thus if we want to have this feature working (at least partially) we need the source code "right off the bat" to get those fixes. Please, make pressure on their forums for 5.9 x720 Kernel source code and for nougat preview builds, I'd appreciate to even help with their own EUI for that matter, I'll see if I can get in touch with them concerning those points.
Do we have someone from China or someone with experience with Chinese so we can attach our discussions there?
I do hope they keep the open source up to date, but it seems they are doing the bare minimum to apply to Google's open source policy. I'm in the US, so I have the x727 with 1 SIM. We would need someone to test with a x720 as well.
@GalaticStryder, Leeco only will post the sources needed to avoid license problems with GPL, so dont wait much help from them. But we can ask...
@jts2111, I have a 720, so I can test your builds.
@jts2111
I received my X720 this week and I could also test your experimental build.
It would be nice to already start with a LineageOS custom ROM as first ROM to avoid a lot of reinstallation / reconfiguration of apps with other kind of custom ROMs.
Heya, I just got my hands on a J200H, and I get to keep it for a while.
As I was using it, I thought if there is any lineageos for it, and there is not.
Now it would be great if you guys point me where I can find Device tree, Kernel source, Vendor blobs for this device, so that I could start working on this device and add the repo to official lineageos server for build ( provided all things goes smoothly nearly one month is enough )
Also I saw some varients of this device, it would be great if you could add device models (the codes- like J200H) and their source codes too, I could try merging them into a universal source code and patch as universal makes less problem.
Thanks In advance! And any update will be posted here.
I doubt if the things mentioned are available.
But if the are really willing to do this than this can be useful .
Have a look a this
https://web.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
and this
https://forum.xda-developers.com/an...ow-to-create-device-tree-android-rom-t3498355
ad. said:
I doubt if the things mentioned are available.
But if the are really willing to do this than this can be useful .
Have a look a this
https://web.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
and this
https://forum.xda-developers.com/an...ow-to-create-device-tree-android-rom-t3498355
Click to expand...
Click to collapse
got em on samsungs website, but holy ****e their bandwidth....they are killing me.....
Just look at these download speed.... god no...
https://ibb.co/gnDQLQ
uts58 said:
got em on samsungs website
Click to expand...
Click to collapse
I don't know but I guess they are just kernel source .
Once downloaded you can know what is that actually.
@uts58 Are you still working on it????
Hello colleagues and friends
I am thinking about buying this phone but before that I would like to ask if anyone has information about the work on Costum rom for this device?
I've started reading about how to build Lineage OS for a new phone. I've never done that before, so don't hold your breath. Maybe I'll succeed, maybe I'll fail. I've ordered my phone almost a week ago, but it hasn't shipped yet. Custom ROMs generally only happen for popular phones, so while I hope developers will join in here, I'm not super optimistic.
No
And even if there was it would be very very very buggy
As Kernel sources are not released
maybe we are writing petitions to nubi with a request to make the sources for this model public
Lol! I went to help.redmagic.gg and opened a chat asking for the kernel source code. They asked me to be more specific, so I said that in order to build Lineage OS (and other ROMs thereafter) I would need the kernel source code for the Redmagic 8 pro. They said they have escalated my request, and I should watch my email. I give this a 0.05% chance of success.
jfsat said:
Lol! I went to help.redmagic.gg and opened a chat asking for the kernel source code. They asked me to be more specific, so I said that in order to build Lineage OS (and other ROMs thereafter) I would need the kernel source code for the Redmagic 8 pro. They said they have escalated my request, and I should watch my email. I give this a 0.05% chance of success.
Click to expand...
Click to collapse
Customer support is garbage. I am using the OS set to Hungarian. The language is not officially supported so most things are in English (which is ok for meg), except for 1 thing. The update page is displayed in Spanish for some weird reason. I reported this 3 years ago.
No fix in Red Magic OS as of yet.
Well, it didn't take RedMagic long to tell me no:
We would like to inform you that kernel source code has not been released now, once it is released we can provide it for you.
If you have any further questions, please do not hesitate to contact us back.
Click to expand...
Click to collapse
Let them know it will boost the sales like moto edge s pro did if redmagic 8 would be the first 8 gen 2 phone that allows to install custom rom.
Red magic 8 has unique design, useful cooling fan. It is a good phone but branding is not popular.
I also send a really long text maybe if enough people asking them, they will finally give up lol
jfsat said:
I've started reading about how to build Lineage OS for a new phone. I've never done that before, so don't hold your breath. Maybe I'll succeed, maybe I'll fail. I've ordered my phone almost a week ago, but it hasn't shipped yet. Custom ROMs generally only happen for popular phones, so while I hope developers will join in here, I'm not super optimistic.
Click to expand...
Click to collapse
I'd recommend going for Paranoid Android (PA) as it's CAF (basically Qualcomm patches to AOSP). It also was built for Asus Zenfone 9 (8+ Gen 1), so similar steps for RM8 Pro could probably be followed. Maybe you can ask someone from PA team (or the Zenfone 9 maintainer) for help.
Also asked support for kernel source code, but most likely we could use one from Qualcomm (but it's not public, unfortunately, so we need to register there somehow)
Can someone write such a request in English and post it here in the thread and provide a link where I can send it to anyone who wants to copy it and send it Thanks
What about the kernel source from s23 series ?
skycrow67 said:
What about the kernel source from s23 series ?
Click to expand...
Click to collapse
There are also OnePlus 11 kernel sources available, but they all might have different device trees (same GPIOs are used differently). In worst case scenario one could fry the phone.
AFAIK we could extract GPIO information from boot.img, but I'd wait for official source code to be released. They published 7s Pro sources, so there is a high chance that 8 Pro will be published as well (GPLv2 obliges them to do so, but who cares)
aaa.bbb111222 said:
There are also OnePlus 11 kernel sources available, but they all might have different device trees (same GPIOs are used differently). In worst case scenario one could fry the phone.
AFAIK we could extract GPIO information from boot.img, but I'd wait for official source code to be released. They published 7s Pro sources, so there is a high chance that 8 Pro will be published as well (GPLv2 obliges them to do so, but who cares)
Click to expand...
Click to collapse
Looks like the 7s Pro was released on July 11th, and the kernel source code was released on October 27th? So a 3.5 month gap maybe. The 8 Pro was released the last week of last year, right? So optimistically we're talking about mid-April?
jfsat said:
Looks like the 7s Pro was released on July 11th, and the kernel source code was released on October 27th? So a 3.5 month gap maybe. The 8 Pro was released the last week of last year, right? So optimistically we're talking about mid-April?
Click to expand...
Click to collapse
I hope so. Guys I swear when this phone is getting custom firmware I think this will be the best phone for the next years for a lot of people
[CLOSED] New MIUI port for Red Magic 8 Pro
This port of MIUI was recently released for the Red Magic 8 Pro, is anyone able to download or give it a try? http://b23.tv/IQtgRZ6 - Post http://b23.tv/j2OoBDG - Video I unfortunately am unable to as I don't have a CN phone number
forum.xda-developers.com
MIUI port from CN
I guess we are not getting kernel source code unless zte wants to release it somewhere in the future. Their support refuses to publish it (not that they have sources, but still), seems that this comes from their management.
BTW, there's a kernel for NX711J (Nubia Z50) here, maybe it could be used.
UPD: I just got an email from support. They finally agreed to provide source code, it will be uploaded soon. I'll publish a link as soon as I get it. No EDL package tho.
aaa.bbb111222 said:
I guess we are not getting kernel source code unless zte wants to release it somewhere in the future. Their support refuses to publish it (not that they have sources, but still), seems that this comes from their management.
BTW, there's a kernel for NX711J (Nubia Z50) here, maybe it could be used.
UPD: I just got an email from support. They finally agreed to provide source code, it will be uploaded soon. I'll publish a link as soon as I get it. No EDL package tho.
Click to expand...
Click to collapse
Ly bro
Now I propose to write a firehose public request for the edl package he can give too
Well, in my opinion, you should ask people who make costum rom to be interested in this model
StoneIsland said:
Now I propose to write a firehose public request for the edl package he can give too
Well, in my opinion, you should ask people who make costum rom to be interested in this model
Click to expand...
Click to collapse
We really need a custom ROM for this phone because the stock firmware is so Bad
(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Edit :
It's already released.
Now I hope the developers start creating fantastic roms for this beast phone
salahomer said:
(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Click to expand...
Click to collapse
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Edit: Cool! It's finally released!
JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Very soon, not now...so let us wait a few more days or weeks
JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
I see there are 7S and 6S kernels, but I don't see any custom ROMs for them, so idk if we will see any for this phone too.
The repo is now available, however, it's empty by the time of me posting this now. It took them two weeks just to create the repo, that's insane. Well, at least it finally happened. Waiting for sources to be uploaded, they probably have to use slow vpn or something to do that, so it might take quite a bit of time.
What can we do with the kernel source?
So it is here.
JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Edit :
It's already released, check again.
Now I hope the developers start creating a new fantastic roms for this beast phone
Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.
aaa.bbb111222 said:
Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.
Click to expand...
Click to collapse
So... What does that mean for new custom roms
gwenmillett said:
So... What does that mean for new custom roms
Click to expand...
Click to collapse
We're not gonna see them until someone writes these drivers or zte publishes them. Both are very unlikely, so...
Seems like they uploaded it again, on zips. I checked and it seems to contain several things inside the /drivers/nubia folder so we probably have now a full workable kernel source