Hello,
I have just signed the petition "MediaTek: Source code for UMIDIGI Z PRO" and I wanted to ask you if you also participate.
Our goal is to collect 500 signatures and we need support for that. Here you can learn more about the petition:
http://chn.ge/2zPJrkU
Many Thanks!
Don't you have already a 8.1.2 fiber OS rom?
Why do you need source code?
You have started a fake rom thread in the past days. Why we should listen to you?
encol said:
Don't you have already a 8.1.2 fiber OS rom?
Why do you need source code?
You have started a fake rom thread in the past days. Why we should listen to you?
Click to expand...
Click to collapse
what's your problem because I have not yet uploaded Fiber OS .... first is a mod on lineage 14.1 and unofficial I'll upload it when I'm done
j4m35_d4ng3r said:
what's your problem because I have not yet uploaded Fiber OS .... first is a mod on lineage 14.1 and unofficial I'll upload it when I'm done
Click to expand...
Click to collapse
Our problem with you is that we don't believe you, because you seem to be an ignorant or an unconscious. You can't say that you have a ROM if you don't have it, and you don't have it because you can't have it, because to develop the ROM you need the Mediatek source code, which is not available.
So, can you explain what are you doing and how?
Interesting... He not explain, but i'll very happy if we get a great ROM in this Great Phone....
It's a fake.
Don't trust him
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!
Hi, everyone can link to me the stable build of lineageos 18.1 please? Because I'm too boring at the lineageos 17.1!Thank you
alprtewwqfr said:
Hi, everyone can link to me the stable build of lineageos 18.1 please? Because I'm too boring at the lineageos 17.1!Thank you
Click to expand...
Click to collapse
You are extremely cheeky. It literally takes 30 seconds to look up the downloads section on https://download.lineageos.org to see that there isn't one single 18.1 version even out yet.
And checking the ONE forum (where you are right now) for unofficial builds is just as easy and fast.
So in the future, please use your time more efficient by looking it up yourself and do not waste time creating a useless new thread. Thanks
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
My best regards. Please, does anyone know if any of the developers are working on ROM Resurrection Remix and Pixel Experience on Xiaomi 12??
Benoni1 said:
My best regards. Please, does anyone know if any of the developers are working on ROM Resurrection Remix and Pixel Experience on Xiaomi 12??
Click to expand...
Click to collapse
No kernel for the moment:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource
NOSS8 said:
Momentálně žádné jádro:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource
Click to expand...
Click to collapse
thenk you
NOSS8 said:
No kernel for the moment:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource
Click to expand...
Click to collapse
Ah, then is that the reason there are still no Custom Roms?
fgh11 said:
Ah, then is that the reason there are still no Custom Roms?
Click to expand...
Click to collapse
One of the reasons but does not really seem to be that since for the Xiaomi 11t pro code name vili also no kernel and yet a vanilla AOSP A13 has been published since 08/19.
255 / 5 000
Výsledky překladu
Nice day. This is how I am contacting the developers, if when the official android 13 is released, they could participate in the development of ROM Pixel Experience and Resurrection Remix for Xiaomi12. We will expand the park and the phone will be even more attractive. Thanks to the developers who will participate in this.
Ó.k.
NOSS8 said:
No kernel for the moment:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource
Click to expand...
Click to collapse
But what is this?
GitHub - MiCode/Xiaomi_Kernel_OpenSource at zeus-s-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
Huppers1 said:
But what is this?
GitHub - MiCode/Xiaomi_Kernel_OpenSource at zeus-s-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Xiaomi 12 code name CUPID not ZEUS.
NOSS8 said:
Xiaomi 12 code name CUPID not ZEUS.
Click to expand...
Click to collapse
You're totally right. Sorry. The information on the column "Device" cause confusion. How is possible have ZEUS kernel and not CUPID? Strange, no? Look, I'm just a enthusiasts tryna learn a little bit more with you guys!
Huppers1 said:
You're totally right. Sorry. The information on the column "Device" cause confusion. How is possible have ZEUS kernel and not CUPID? Strange, no? Look, I'm just a enthusiasts tryna learn a little bit more with you guys!
Click to expand...
Click to collapse
This does not seem important since there are roms in A13 while there is no kernel yet. (11 t pro).
The rom is based on extracted A13 firmware.
it is preferable for a developer to have the device, the price can be a brake.(12 pro).
Found this Lineage 19.1 rom on Github
https://github.com/arian-ota/ota/releases/tag/19.1-cupid-3b1402e4
https://raw.githubusercontent.com/arian-ota/changelog/lineage-19.1/cupid.txt
Lineage thread
https://forum.xda-developers.com/t/...cked-bootloader-test-lineageos.4443787/page-2
Guide
https://forum.xda-developers.com/t/guide-install-lineageos-19-1-with-gapps.4478873/