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?
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
Hi all,
Here is the thread about Phh-Treble for Android 10.0, codename Quack.
The goal of Phh-Treble for Android 10.0 is the same as for Android 8.0, 8.1, and 9.0: Bring latest AOSP to the maximum number of devices running Google-certified Treble[1], with full hardware support.
You can download latest release at https://github.com/phhusson/treble_experimentations/releases
Which variant do I pick
To know which variant to download, use https://play.google.com/store/apps/details?id=tk.hack5.treblecheck . Don't use other Treble Check apps, they'll give erronous informations.
And then, you're free to choose between vanilla and gapps variant.
What works?
On some devices, everything. They are still not the majority though.
What you can expect on the majority of devices?
It should boot successfully on pretty much all devices with Google-certified Treble. [1]
Most features should work on the majority of devices out-of-the-box: RIL, WiFi, brightness control, buttons, gestures, ...
However, many devices still have issues with hardware video decoding and camera.
Is device XXX supported?
If it's a Google-certified Treble, yes it is. Unlike Google's GSI, Treble devices supported, there is no exception.
There might be bugs of course, but if you help me, I'll fix them!
Which vendor to use?
1. Always use your actual device's vendor
2. Always use OEM unmodified vendor, not some custom vendor
3. This includes boot.img. boot.img and vendor MUST BE the same version.
4. If you're on an Android 8.0 vendor, you'll need to stick to vendors with Security Patch Level before April 2019 (that's a bug of my GSI)
Enjoy!
[1] How do I know my device is Google-certified Treble?
Well it's easy, if your device has first been released with Oreo or more recent, and it has google apps, it has a Google-certified Treble.
Please note that this means only the vendor provided by the OEM is certified, not the one from device-specific ROM.
No comments?
Deleted
mewcatchew said:
No comments?
Click to expand...
Click to collapse
... yeah ... - I found that odd, too. Though the interest in this phone seems pretty scant.
I think it has more to do with the fact that this is more of a spam/general post about Treble with no real information about our devices. Just "go figure out out, dum dum" mentality. Same with this guy's other post in here.
Can we expect Lineage OS to be released for realme X3? I have a feeling that it is one of the phones that can really benefit from lineage OS as despite having excellent specifications it is bogged down by terrible software support by realme?
jaidosajh said:
Can we expect Lineage OS to be released for realme X3? I have a feeling that it is one of the phones that can really benefit from lineage OS as despite having excellent specifications it is bogged down by terrible software support by realme?
Click to expand...
Click to collapse
There is no way to know if or when any device will get any kind of custom ROMs. That is a matter of whether someone with the knowledge to create custom ROMs owns one of those devices or not and whether or not they choose to build a ROM for that device and that is only "if" the stock source code has been made available to the public. If the stock source code has not been made available to the public, custom ROMs cannot be built for the device because stock source code is required in the building process.
The short answer is you will just have to wait and see or take it upon yourself to try building LineageOS for your device for yourself. Trying to build it yourself might get you there faster because you might be in for a long wait if you wait for someone else to do it or may never happen at all.
THANKS
LOAZIT said:
THANKS
Click to expand...
Click to collapse
Because they usually build and release new versions each day because they are always patching and optimizing the code or adding new features, they are typically called "nightly builds" or "nightlies". Once the nightly build passes testing phase it is released as a RC(respective candidate) build or Official ROM once they reach a certain critical point of development. Since it is a continous daily process of building, testing and releasing and since there is always a build in each stage of development each day, there is always a new tested nightly or RC build being released from the last stage of development almost daily.
cool
do you know when lineage os with the next version of android needs to be released?
LOAZIT said:
cool
do you know when lineage os with the next version of android needs to be released?
Click to expand...
Click to collapse
Here at XDA, a lot of times, newer versions of android are available to the developers here before it is released to the public and the community here gets a taste of ROMs made from the new versions before everyone else in the world does. When this happens depends on when Google decides to release beta releases of the new versions. It is more a matter of what and when Google does things than it is a matter of when and what XDA does.