Related
I am curious if anyone is currently working on getting CM (or any custom ROM) working for our devices. I'm not trying to bug anyone or get an ETA, but I was thinking about attempting to port CM with their tutorial.
If anyone is working on porting a ROM, or has any tips for me I'd love to talk. Thanks.
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
jmiller99 said:
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
Click to expand...
Click to collapse
I have only built unofficial builds before, but hopefully since we have source and other Huawei devices with CM, it should be fairly easy.
If you haven't built CM for a device that it's already been ported to, I'd recommend doing that before you attempt to port it.
Good luck. I'll post any progress I make.
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
I'm *trying* to get CM 12.1 to work for our device, but I've never ported before so don't expect anything soon
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
It's still early. The fact that Huawei makes bootloader unlock codes available and has provided the amount of source code for the kernel that they have has allowed development here to happen much more rapidly than many devices do (particularly devices that lie out side of "volume" interest -- like an S5 or S6). I'm pretty optimistic.
The flip side is that life is so busy for me at the moment that it makes patience pretty easy (as in, if a stable cm13 suddenly became available I still would take my sweet time in getting around to flashing it). If I had more time on my hands it would probably be different.
Yes lets see how long we need to wait !
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Bandit Development said:
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Click to expand...
Click to collapse
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
deadman96385 said:
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
Click to expand...
Click to collapse
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Name it kiwi .it sounds really great ! Moreover i dont what others are thinking on naming this device ,but kiwi is maximum minds .Go for it !
Bandit Development said:
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Click to expand...
Click to collapse
https://github.com/Huawei-Kiwi
deadman96385 said:
https://github.com/Huawei-Kiwi
Click to expand...
Click to collapse
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Bandit Development said:
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Click to expand...
Click to collapse
That cm tree was just to build cm recovery we are still in the very early stages of a full cm tree.
Does anyone know if a cyanogenmod rom for mipad 2 is available?
Envoyé de mon Mi-4c en utilisant Tapatalk
+ 1
Dear Developers and Hackers of XDA,
I just bought this tablet. I looked around on the MIUI forum for MI Pad 2 and see that there are ways to root a developer MIUI ROM for this tablet. I also see that there are also instructions to unlock the bootloader and install a custom recovery. I am big fan of Cyanogemod and am hoping to have it on the tablet. Has anybody tried and/succeeded to port Cyanogenmod to this tablet?
Hoping for the best
Sincerely
dspati
Hi dEvasEnApati I'm in your situation! I hope to recive news as soon as possible because i want to install cyano!
Xda dev have you got some news?
Hi,
Following the instructions from the miui forum I managed to unlock the bootloader, root , install TWRP and AOSP rom. I was wondering what are the requirements to have a cyanogen mod for it? Are there CMs for devices with intel x86_64 hardware?
I'll get my mipad 2 soon! I think in a week or two then I'll Start heavy development on it ? i think of aosp is possible cm will be possible too :] I'll keep u guys updated
Hi Nailyouh,
Thank you very much for doing this!
Maybe this may help: As paul_ro21 mentioned, a working AOSP rom, which was most probably developed by Xiaomi is available on the miui forums. I have it on my mi pad 2 as well and it's working fine. I am looking forward to a CM rom for this tablet and I will be happy to help with testing!
Sincerely
dspati
Nailyouh said:
I'll get my mipad 2 soon! I think in a week or two then I'll Start heavy development on it �� i think of aosp is possible cm will be possible too :] I'll keep u guys updated
Click to expand...
Click to collapse
Nailyouh said:
I'll get my mipad 2 soon! I think in a week or two then I'll Start heavy development on it �� i think of aosp is possible cm will be possible too :] I'll keep u guys updated
Click to expand...
Click to collapse
Waiting for your work on CM
Im too tired with stupid MIUI on this awesome tablet :
Stupid ram management, it has 2gb ram but it cannot run multi-tasking !
Im facing a big Problem i was not aware about..the Kernel of the MiPad2 is not open source so we are pretty f**ed by xiaomi. In fact the Kernel source has to be released but xiaomi don't care about Copyright infringements. I regret the decision buying this Tab. I like the Dualboot thingy and the aosp Rom runs smooth as butter but without the source we'll stuck on 5.1.1. really sad if you ask me, the Tablet is really beautyful and I love the outstanding Display. I'll try to figure around with the kernel from the aosp Rom next week I'll keep u informend and will make a thread if I suceed.
Cheers
Naily
Nailyouh said:
Im facing a big Problem i was not aware about..the Kernel of the MiPad2 is not open source so we are pretty f**ed by xiaomi. In fact the Kernel source has to be released but xiaomi don't care about Copyright infringements. I regret the decision buying this Tab. I like the Dualboot thingy and the aosp Rom runs smooth as butter but without the source we'll stuck on 5.1.1. really sad if you ask me, the Tablet is really beautyful and I love the outstanding Display. I'll try to figure around with the kernel from the aosp Rom next week I'll keep u informend and will make a thread if I suceed.
Cheers
Naily
Click to expand...
Click to collapse
Too sad, I know this will happens becoz Xiaomi released just some models ( Mi4 ... )
Hope You will find a way to solve this
The hardware is awesome, but the OS is SUCK !
Any news?
any news?
@Vihru there is some progress in the MIUI forums, I'm using MIRU 7 and currently waiting MIRU 8 to finish downloading. It's like a whole new tablet, amazing what they've done with it
Remix 2.0: http://en.miui.com/thread-329758-1-1.html
MIRU 7: http://en.miui.com/thread-325531-1-1.html
MIRU 8: http://en.miui.com/thread-353077-1-1.html
If anyone on MI Forum as registered, please assist here:
http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=424803&pid=7862023
See if I gave him all correct links and processes..
vdbhb59 said:
If anyone on MI Forum as registered, please assist here:
http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=424803&pid=7862023
See if I gave him all correct links and processes..
Click to expand...
Click to collapse
Is this good news for you:
http://en.miui.com/thread-411400-1-1.html
CyanogenMod 13 x86 6.0.1 on MiPad 2 Intel x5 z-8500
xposed will work too. Right now the audio is under construction (not working, yet).
Xiaomi added kernel souces for Mi Pad 2
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/latte-l-oss
datorprofessor said:
Is this good news for you:
http://en.miui.com/thread-411400-1-1.html
CyanogenMod 13 x86 6.0.1 on MiPad 2 Intel x5 z-8500
xposed will work too. Right now the audio is under construction (not working, yet).
Click to expand...
Click to collapse
Thanks mate.
Checking it.
Kernel source is out (github)
Nailyouh said:
Im facing a big Problem i was not aware about..the Kernel of the MiPad2 is not open source so we are pretty f**ed by xiaomi. In fact the Kernel source has to be released but xiaomi don't care about Copyright infringements. I regret the decision buying this Tab. I like the Dualboot thingy and the aosp Rom runs smooth as butter but without the source we'll stuck on 5.1.1. really sad if you ask me, the Tablet is really beautyful and I love the outstanding Display. I'll try to figure around with the kernel from the aosp Rom next week I'll keep u informend and will make a thread if I suceed.
Cheers
Naily
Click to expand...
Click to collapse
Kernel source is now out on github. Any thoughts about it?
Hi all,
Now that CM is dead (RIP) and official Lineage OS for the Wileyfox Swift 2 has not yet happened, i've been looking into other alternative OS's that are compatible with the Wileyfox Swift 2 [marmite].
However i'm not seeing any that are compatible for this device (Resurrection Remix, Dirty Unicorn, LineageOS (yet) and wondered if anyone has had any experience with any other custom OS's that they know are compatible?
Thanks
There are none because there is no source code for this device. You must be patient and wait until Wileyfox releases (Before the end of this month?!) the promised Android 7.1 update, and hope they also release the source code with it.
I did several modifications to stock CyanogenOS 13.1 version for myself, but I found not worth it sharing that, since we're going to receive the new update really really soon. If the update is a disaster, or they do a OnePlus (release the update on the 31st, late in the night before the end of the month, and full of bugs), I'll consider sharing it. But until then, just wait for it.
Thanks for the update. :good::good:
linuxct said:
since we're going to receive the new update really really soon.
Click to expand...
Click to collapse
I live in hope. :fingers-crossed:
linuxct said:
There are none because there is no source code for this device. You must be patient and wait until Wileyfox releases (Before the end of this month?!) the promised Android 7.1 update, and hope they also release the source code with it.
I did several modifications to stock CyanogenOS 13.1 version for myself, but I found not worth it sharing that, since we're going to receive the new update really really soon. If the update is a disaster, or they do a OnePlus (release the update on the 31st, late in the night before the end of the month, and full of bugs), I'll consider sharing it. But until then, just wait for it.
Click to expand...
Click to collapse
Thats not true there is maybe not a source code but the chips inside the device (and drivers) are also used in other devices wich are so you can make roms for this device.
There are no roms because this phone isn't used by many peaple yet or the community isnt big at the moment for this device but we can port roms from the xiaomi redmi 3s for instance
draakwars said:
Thats not true there is maybe not a source code but the chips inside the device (and drivers) are also used in other devices wich are so you can make roms for this device.
There are no roms because this phone isn't used by many peaple yet or the community isnt big at the moment for this device but we can port roms from the xiaomi redmi 3s for instance
Click to expand...
Click to collapse
WTF? Do you think that by having same CPU means we should have the very same source code? I know there's source code for the SD430 in codeaurora, and that Xiaomi released sources for land, but that doesn't mean anything. It'd require a lot of dirty and unnecessary stuff to get it working here (it's not only about the CPU, right?), and since Wileyfox is REQUIRED to release the source code (all OEMs are) we can avoid it by just waiting patiently. From there, building Lineage will be easier, but hey, if anyone wants to do the hard job, use land-m source code and try to port it, is free to do so! :laugh:
linuxct said:
Wileyfox is REQUIRED to release the source code
Click to expand...
Click to collapse
Manufacturers need to release kernel source as it's under a GPL license, but Android itself is under the Apache License 2.0 and manufacturers are not required to release any source code. In fact the vast majority of manufacturers do not release any of their internal Android code.
And having kernel source does not magically allow you to make custom ROMs. In fact you shouldn't even need the manufacturers kernel source unless they are using some obscure hardware.
flibblesan said:
Manufacturers need to release kernel source as it's under a GPL license, but Android itself is under the Apache License 2.0 and manufacturers are not required to release any source code. In fact the vast majority of manufacturers do not release any of their internal Android code.
And having kernel source does not magically allow you to make custom ROMs. In fact you shouldn't even need the manufacturers kernel source unless they are using some obscure hardware.
Click to expand...
Click to collapse
I know, but it's better having and working with it, isn't it? I know we will need to bring up a device tree, and that it's not that easy, but starting out of a good base is better than mixing sources from other phones, at least that's my opinion.
The kernel sources are already available for a long time (slowpokes?): https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937
BeYkeRYkt said:
The kernel sources are already available for a long time (slowpokes?): https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937
Click to expand...
Click to collapse
Oops. You made my day man. I swear I wasn't able to find that, I had no idea they published it already, they didn't mention it on social media, and whenever I asked them on the support chat they were like "Sorry, we don't have that".
linuxct said:
Oops. You made my day man. I swear I wasn't able to find that, I had no idea they published it already, they didn't mention it on social media, and whenever I asked them on the support chat they were like "Sorry, we don't have that".
Click to expand...
Click to collapse
Because I do not think that the public (where most users are not geeks, probably) will be interested in the post that the developers have released the source code of the kernel. Or someone beforehand, before closing Cyanogen Inc, released the source code for the kernel. And support is usually not answered to such questions, because they do not have such information.
But in any case you need the information you need to find in all available ways.
I have the idea for an unified build from quite some time, but only now I'm trying to bring it to life.
Looking at LineageOS github and gerrit you can see that other devices (klte, m8) have the same stupid amount of variants, but they have merged them into one device repo.. So why can't this happen for the Note4?
Following their steps I've created an unified android_device_samsung_trlte (that includes SM-N910F/trltexx, SM-N910G/trltedt, SM-N910T/trltetmo, SM-N910W8/trltecan, SM-N910P/trltespr, SM-N910R4/trlteusc and SM-N910V/trltevzw), this proprietary_vendor_samsung and added this commit to the android_device_samsung_trlte-common that I'm currently using.
For now I'm able to use those repos to build a LineageOS-14.1 build that boots up, but w/o sim and camera being recognized.. For what I've tested (on trltexx) wifi and (strangely) bluetooth are working. Something is probably wrong with specific device blobs not being recognized/used properly.
It needs some work but I think this is a good base to start with.
trltexx/trltedt blobs are from here;
trltetmo/trltecan blobs are from here;
trltespr/trlteusc blobs are from here;
trltevzw is using trltespr blobs for now (there are no guaranteed working blobs repos for it at the moment, the only (WIP) way is to establish which are needed and extract them from hsbadr's builds).
The kernel is the same that I'm using for the not unified builds (android_kernel_samsung_trlte), at the moment testing if the klte's way of using the international variant defconfig works for us too.. other options are to add something like this commit to remove the need of a variant defconfig or merge the different defconfigs into one and use that instead.
Source:
unified_android_device_samsung_trlte
unified_android_device_samsung_trlte-common
unified_proprietary_vendor_samsung
android_kernel_samsung_trlte
I was going to share this anyway, but I'm sharing it now (even if there are still major problems) because I have a very limited free time where I can work on it, so, maybe, someone of you will join/fork/clone this project and help me out, finalizing it earlier and better (the support of experienced developers is needed and much appreciated).
I'm now going to mention the SeniorMembers/RecognizedContributors/RecognizedDevelopers that, maybe, have interest in this project.
@fattire @hsbadr @SaintZ93 @SferaDev @TheBr0ken @ZION959
If you get it to work, @_mone, I'll switch my daily builds to this unified one.
On a related matter, there seems to be a typo in the name of one of your repos: unified_andorid_device_samsung_trlte.
Let me also add @lilferraro to the list of devs, as I use his device tree to build for trltespr.
I built this and it boots, with the same issues you have (no SIM detected, camera is busted). Took a bunch of of logs. Getprop shows ro.build.fingerprint is trltetmo (which is right), ro.bootimage.build.fingerprint is trlte. Wifi and bluetooth are working. Mediaserver/libcameraservice service crashes repeatedly. I agree with you that having a unified tree for the entire Note 4 line is the way to go. I tried manually copying the blobs from /system/blobs/tmo/ to /system/lib and /system/vendor/lib but it didn't help.
what proprietary blobs did you use for sprint?
All device trees for the note 4 pie builds are up at
GitHub.com/tripLr-dev
User forum at Telegram
https://t.me/triplr_dev_users
Thanks to @_mone
And @ripee
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
tigerpro357 said:
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
Click to expand...
Click to collapse
Let us know what you need
Source code
GitHub.com/triplr-dev
Contact me on telegram t.me/telegram to get you in touch with testers and developers. .
I am EXTREMELY interested in a touch port.
Thanks
Also GitHub.com/underscoremone for all the older stuff
I actually have my work on github already, I am also on telegram in the ubports groups, and if you would like to help my repo is probably the best place to start (unless you prefer duplicating work) I only have sensors and the stylus left for hardware (both of which I have been trying to get working) the stylus is an issue on the ubports side but I dont understand the code enough for mir. I haven't had a chance to test the unified repo yet, but I will once I have a few minutes to actually do it.
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
tripLr said:
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
Click to expand...
Click to collapse
I agree, as all I really see on xda as far as Ubuntu Touch goes is prebuilt downloads which is good for letting people try it, but when I started I initially looked into xda but found no help. I do hope to see that change in the future though
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
doubledragon5 said:
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
Click to expand...
Click to collapse
Same here
We have several developers for note 4 snapdragon and exynos
T.me/triplr_dev_users
See you there
Roms
Tiny.cc/triplr
Tiny.cc/ripee
And many links in XDA for ROM threads
Post comments in XDA, and bug reports and logs in telegram
Android 10 in progress
Thanks @_mone
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.
Kernel source code for Mi Note 10/Mi CC9 Pro is now available on GitHub.
<https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tucana-p-oss>
thanks
Nice! I will try to play around with building a rom... Hope I won't brick my phone.
h8Aramex said:
Nice! I will try to play around with building a rom... Hope I won't brick my phone.
Click to expand...
Click to collapse
Did you make any progress?
iSonik said:
Did you make any progress?
Click to expand...
Click to collapse
I spent quite some time on it but sadly the kernel source is just one tiny bit of the recipe.
You need a device AND vendor tree as well, and as far as I can tell you just can't rip them out of a device or anything. They just magically "appear" online. Ie.: I think someone leaks them... I don't know. I tried to talk with devs, tried various forums and communities but no dice. Wish I had a solution, I am afraid the next Android 10 update won't be too good for this device either - other people who received the Android 10 updates for Xiaomi are already complaining.
h8Aramex said:
I spent quite some time on it but sadly the kernel source is just one tiny bit of the recipe.
You need a device AND vendor tree as well, and as far as I can tell you just can't rip them out of a device or anything. They just magically "appear" online. Ie.: I think someone leaks them... I don't know. I tried to talk with devs, tried various forums and communities but no dice. Wish I had a solution, I am afraid the next Android 10 update won't be too good for this device either - other people who received the Android 10 updates for Xiaomi are already complaining.
Click to expand...
Click to collapse
So did you try compiling a custom Kernel? Also we could, instead of using the device Tree, try to Port PHHusons GSI to our device. i already started with that, trying to create overlay and so on. Alot of thinks are already working with that LOS build.
So my idea is to debloat a GSi ( so only things needed for Mi Note 10 are included) and then also using a custom kernel