Related
Will Xiaomi release kernel sources fully for this smartphone & therefore able to have active rom development (including Android M 6.0 roms) in the near future ?
(Kernel sources for the Xiaomi Mi3 & Mi4 were released very late and not in full and are the reason I believe that many Lollipop roms for these devices are not stable).
I think it depends on whether the device goes international. They were quick to release the sources for the Mi4i, and that is the only phone they officially sell internationally. That said, at least it uses the most common SOC of 2015.
Does it help that it has the same soc as the nexus 5x?
ermacwins said:
Does it help that it has the same soc as the nexus 5x?
Click to expand...
Click to collapse
It helps a little bit maybe, but the problem is all the other stuff inside the phone is different. You still need proper sources from Xiaomi.
M.
Do Xiaomi devices have root "built-in" ?
I'm interested in ROM development, too, but for the first months having root would be enough.
Giocarro said:
Do Xiaomi devices have root "built-in" ?
I'm interested in ROM development, too, but for the first months having root would be enough.
Click to expand...
Click to collapse
I have seen a guide on MIUI forum: "How to flash TWRP Recovery and Super Su(Root) on Xiaomi Mi4C"
Having access to kernel will also mean ir blaster will work on custom roms?
ermacwins said:
Having access to kernel will also mean ir blaster will work on custom roms?
Click to expand...
Click to collapse
Don't count on that. Many device that have kernel source and ir blasters still don't work on aosp based roms. Due to all the drivers for the hardware being closed sourced.
zelendel said:
Don't count on that. Many device that have kernel source and ir blasters still don't work on aosp based roms. Due to all the drivers for the hardware being closed sourced.
Click to expand...
Click to collapse
When we say kernel source, is that pertaining to the soc?
ermacwins said:
When we say kernel source, is that pertaining to the soc?
Click to expand...
Click to collapse
The kernel covers all aspects of the device in one form or another.
zelendel said:
The kernel covers all aspects of the device in one form or another.
Click to expand...
Click to collapse
Let's say xiaomi is taking long to release their kernel source but the source for nexus 5x soc is out, would that be enough for aosp rom?
ermacwins said:
Let's say xiaomi is taking long to release their kernel source but the source for nexus 5x soc is out, would that be enough for aosp rom?
Click to expand...
Click to collapse
No it won't. You will also need the device tree for this device. It's not how long it takes for them to release it that I would be worried about. It's if the source is complete and not broken like they are known to release. They have a habit of release broken source to force users to use miui. If you look at other devices from this OEM it takes months some times a year before they release it and when they do it is broken and devs have to take weeks to get it even remotely working. Then there are still bugs that are never fixed.
zelendel said:
No it won't. You will also need the device tree for this device. It's not how long it takes for them to release it that I would be worried about. It's if the source is complete and not broken like they are known to release. They have a habit of release broken source to force users to use miui. If you look at other devices from this OEM it takes months some times a year before they release it and when they do it is broken and devs have to take weeks to get it even remotely working. Then there are still bugs that are never fixed.
Click to expand...
Click to collapse
So having an aosp based rom as a daily driver is out of the question?
ermacwins said:
So having an aosp based rom as a daily driver is out of the question?
Click to expand...
Click to collapse
isn't the Broken OS ROM by TS Team AOSP based ?
Of interest:
[News] Mi 3/4/Note Kernel Source Code Released! Next to Be, Mi Note PRO, Mi 4c/S:
http://en.miui.com/thread-235127-1-1.html
Don't sceptical, I reconstruct Redmi 2 kernel source without any help from Xiaomi. They released Redmi 2 kernel source for KitKat when my device already run "fully open source" and almost bug free Marshmallow :laugh:
Mi 8/Mi 8 Explorer Edition/Poco F1 Same Branch
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/dipper-o-oss
najjurocks619 said:
Mi 8/Mi 8 Explorer Edition/Poco F1 Same Branch
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/dipper-o-oss
Click to expand...
Click to collapse
Blimey! That's a very good sign!
Hopefully they're intact and usable
thesoupthief said:
Blimey! That's a very good sign!
Hopefully they're intact and usable
Click to expand...
Click to collapse
Indeed, Hoping for great future and development for this device, The cheapest SD 845 yet.
isnt this a security lapse
prabaharanaece said:
isnt this a security lapse
Click to expand...
Click to collapse
Lol are you joking? Xiaomi have themselves released the kernel sources. How does that make it a security lapse when they themselves announced this during the phone launch?
Great news! Hope to see LineageOS soon for this phone.
kishore1998 said:
Lol are you joking? Xiaomi have themselves released the kernel sources. How does that make it a security lapse when they themselves announced this during the phone launch?
Click to expand...
Click to collapse
It is rather a question from me, I know mi released the codes but question is can it be used by someone for hacking this phone. I guess it would be more easier for the hackers now.
prabaharanaece said:
It is rather a question from me, I know mi released the codes but question is can it be used by someone for hacking this phone. I guess it would be more easier for the hackers now.
Click to expand...
Click to collapse
POCO F1 is not the only phone with it's kernel source released. You will find kernel sources released for many phones by different brands (Sony, Samsung, LG, OnePlus and so many more). The purpose of releasing the source is to accommodate custom ROM and Kernel development by developer community (like XDA) and find out vulnerability (if any) in the process. Any vulnerability found is usually patched in updates. Yes the source can be used to compile a kernel or ROM with malicious code or an app which'd try to exploit the vulnerability but it will only affect those who'd install any such app/kernel/ROM. Now any flashaholic you'd meet will tell you how they'd only install apps from trusted sources and flash ROMs/Kernels available on XDA etc. In nutshell, I don't think trying to hack a phone using kernel source is worth it as it targets very limited people who are cautious enough on what to install on their phones making it more difficult to hack. Any developer can enlighten you more on the issue as I might be totally wrong on the issue too.
P.S. It's because of such source code releases that community like XDA is thriving.
prabaharanaece said:
isnt this a security lapse
Click to expand...
Click to collapse
All linux based kernels are open source
Also it is mandatory for OEMs to release kernel sources per GPL license rules.
I got my phone today, waiting for some awesome development..
Thank you everyone for comments :good:. I got my phone today as well
Will only buy it if any rom(i wish for Omni) is built from sources(not ported rom) and officially supports Treble <3
Otherwise simply useless phone for me :X
Would suggest the same for others too
xuser_ said:
Will only buy it if any rom(i wish for Omni) is built from sources(not ported rom) and officially supports Treble <3
Otherwise simply useless phone for me :X
Would suggest the same for others too
Click to expand...
Click to collapse
All roms are build from aosp and other sources, this is not 2012 where ported roms exists here. What are you talking about? Also, the phone is launched with 8.1 so it officially supports treble out of the box. You high or what?
Btw: good to see early release of kernel source but on the other hand, the unlocking of bootloader showing me 30 days (720hours). How will I live for 30 days using MIUI?
Hello,
I'm developing my own android rom from sources right now. That also works so far. I get a complete ROM at the end. Unfortunately the security patch level is not up to date. How can I integrate the patches from the Android Bulletins into my ROM ?
Many thanks for your help
markus789 said:
Hello,
I'm developing my own android rom from sources right now. That also works so far. I get a complete ROM at the end. Unfortunately the security patch level is not up to date. How can I integrate the patches from the Android Bulletins into my ROM ?
Many thanks for your help
Click to expand...
Click to collapse
If it's ABC rom this question would be best asked in the forum above yours. here
Bryanx86 said:
If it's ABC rom this question would be best asked in the forum above yours. here
Click to expand...
Click to collapse
No, it's no ABC rom. It's an AOSP rom. I build it with the sources of AOSP and build an generic Image.
Are there any AOSP support for this phone? Also is there a telegram group
iXanza said:
Are there any AOSP support for this phone? Also is there a telegram group
Click to expand...
Click to collapse
Yes aosp. no tg for that. Some are familiar with Resurrection Remix for op7T and all the other roms I built for it. Building a device tree rn.
FullOfHell said:
Yes aosp. no tg for that. Some are familiar with Resurrection Remix for op7T and all the other roms I built for it. Building a device tree rn.
Click to expand...
Click to collapse
Are you going to build for the 8T??
I was going through various posts and thought NO devs / builders bought the phone.. fingers crossed, if you do and need a tester shout out
TrOjAn
FullOfHell said:
Yes aosp. no tg for that. Some are familiar with Resurrection Remix for op7T and all the other roms I built for it. Building a device tree rn.
Click to expand...
Click to collapse
Thank you for this update.
FullOfHell said:
Yes aosp. no tg for that. Some are familiar with Resurrection Remix for op7T and all the other roms I built for it. Building a device tree rn.
Click to expand...
Click to collapse
All eyes on you. Hope we see TWRP quickly
Good to hear the possibility! cheers
Is there a reason this phone seems rather unpopular in terms of development? The Nord is only a little older and had tons of ROMs to choose from. Is it because the 8T was released with Android 11 maybe?
bemymonkey said:
Is there a reason this phone seems rather unpopular in terms of development? The Nord is only a little older and had tons of ROMs to choose from. Is it because the 8T was released with Android 11 maybe?
Click to expand...
Click to collapse
From what I've read and experienced, it can take a few months for the development to boom for most new phones.
Looks like Pixel Experience 11 was just posted. Things are moving forward, woohoo!
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- Make a backup of your important files
2 - Unlock bootloader with this guide
3 - Flash the TWRP, link here
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package ARM64 > 7.1 > Micro and below: visit OpenGAPPS
If during the gapps flash it gives you an error then in the TWRP terminal or on the adb shell you have to execute this command: "mkdir /tmp/bin"
Download:
Releases · XRedCubeX/android_device_meizu_m5c
Contribute to XRedCubeX/android_device_meizu_m5c development by creating an account on GitHub.
github.com
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
NOT Working:
Camera
Hotspot
Offline Charging
Special Thanks
LineageOS
Moyster for device trees
Device Tree:https://github.com/XRedCubeX/android_device_meizu_m5c
Vendor Tree: https://github.com/XRedCubeX/android_vendor_meizu_m5c
Assim que possível, irei testar!
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
thiagosousa777 said:
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
Click to expand...
Click to collapse
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
XRed_CubeX said:
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
Click to expand...
Click to collapse
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
thiagosousa777 said:
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
Click to expand...
Click to collapse
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
XRed_CubeX said:
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
Click to expand...
Click to collapse
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
thiagosousa777 said:
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
Click to expand...
Click to collapse
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
XRed_CubeX said:
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
Click to expand...
Click to collapse
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them, don't you?
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
thiagosousa777 said:
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them.
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
Click to expand...
Click to collapse
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
XRed_CubeX said:
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
Click to expand...
Click to collapse
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
thiagosousa777 said:
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
Click to expand...
Click to collapse
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
XRed_CubeX said:
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
Click to expand...
Click to collapse
Thanks for the clarification! It is a shame that Meizu does this (I wonder if they are not violating the terms of the Linux GPL license by distributing the kernel without publishing the modifications made to the source code).
Anyway, if a solution to this kernel problem related to the touch screen comes up, please let me know. In the meantime I'll keep reading Halium's documentation until a solution comes along, or until I get a compatible phone.
Great work!
Hello. I've been testing this ROM on my M5c and love it. The ROM is very good, fluid, lightweight... the only problem is that the camera doesn't work, as well as the cellular network data. Congratulations for the excellent work.
The ROM will no longer receive bugfixes?
pls compile
publish a release