Database Info

Developers - Merging Your Working Device

If you are a developer, and wish to have a device merged into Omni, here is the current "temporary" process to use. There are 2 ways to do this - make your tree available on github (or a similar service), or request a new git tree be created, and submit it to gerrit.
1) Get your device working. There's plenty of help available in #omnirom on Freenode if you need assistance. An AOSP device tree is probably the best place to get started.
2) Set up your device to use the OmniROM "custom" build type, rather than full/aosp. More information will follow on this step - check device/samsung/manta or device/lge/mako for an example.
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
4) Come to #omni on Freenode, and have a chat to one of the core developers (they are listed at the top of the user list) - they will be able to help you get your device merged
Please note, in order to add a new device, we will require a maintainer on an ongoing basis for it, to ensure someone is able to investigate bugs that users report on a device. Without this, we unfortunately cannot enable nightly builds for a device.

will a cm kernel tree work for the most part with just a few changes?

azoller1 said:
will a cm kernel tree work for the most part with just a few changes?
Click to expand...
Click to collapse
yes - of course it must be 10.2 (4.3)
most likly it will work even unchanged

pulser_g2 said:
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
Click to expand...
Click to collapse
Along these lines, do NOT remove copyright attributions of a changed file. You may ADD copyrights to a header, but do NOT remove anything.
maxwen said:
yes - of course it must be 10.2 (4.3)
most likly it will work even unchanged
Click to expand...
Click to collapse
Most likely kernel change will be that reverting out that MDP sync point mess used by CM's AOSP+CAF frankendisplay. Can't link to it from my current location.

I have everything device sided transformed to Omni (m7ul,m7-common,and msm8960) and have exactly this problem now. Builds fine but Stucks after a few secs booting and hard reboots. Already looked into kmsg with maxwen but now we need to find what's causing it...
Reverted some stuff (MDP) kernel sided but haven't succeeded so far. Would be appreciated if u point us there when u back on a pc
noNeedForAsig

TF300T
OK here goes..
For the Asus Transformer TF300T the kernel forked from the CyanogenMod github:
https://github.com/scanno/android_kernel_asus_tf300t/tree/android-4.3
And the device tree, modified to get OmniROM to finish the build and get a bootable result:
https://github.com/scanno/android_device_asus_tf300t/tree/android-4.3
Hopefully it will be added to the OmniROM github.

n3ocort3x said:
I have everything device sided transformed to Omni (m7ul,m7-common,and msm8960) and have exactly this problem now. Builds fine but Stucks after a few secs booting and hard reboots. Already looked into kmsg with maxwen but now we need to find what's causing it...
Reverted some stuff (MDP) kernel sided but haven't succeeded so far. Would be appreciated if u point us there when u back on a pc
noNeedForAsig
Click to expand...
Click to collapse
I'm thinking for m7ul it would be https://github.com/CyanogenMod/android_kernel_htc_m7/commit/f2efb02581110747711c8b17f31f38fc3ed5dd1a
Don't want to hijack the thread though, so we can probably discuss this elsewhere

@Grarak Maybe you should post your edited device tree for Omni Rom =)
Sent From my i9500 With ☆★Crash Rom★☆

AL_IRAQI said:
@Grarak Maybe you should post your edited device tree for Omni Rom =)
Sent From my i9500 With ☆★Crash Rom★☆
Click to expand...
Click to collapse
Already on my github
https://github.com/Grarak/android_device_samsung_i9500
kernel tree
https://github.com/Grarak/android_kernel_samsung_exynos5410
proprietary
https://github.com/Grarak/proprietary_vendor_samsung
exynos 5410 repos:
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5410
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5-insignal
https://github.com/intervigilium/android_hardware_samsung_slsi_openmax
pretty much ^^

I'd like to maintain for l900 and i605 (Sprint and Verizon Galaxy Note 2).
device trees
https://github.com/omnirom-slickrick/android_device_samsung_l900 (sprint tree)
https://github.com/omnirom-slickrick/android_device_samsung_i605 (vzw tree)
https://github.com/omnirom-slickrick/android_device_samsung_t0lte (note 2 common tree)
https://github.com/omnirom-slickrick/android_device_samsung_smdk4412-common (same as tree on omnirom github but actually more updated and device settings added back)
kernel
https://github.com/omnirom-slickrick/android_kernel_samsung_smdk4412 (just have needed device settings commits added back in)

thracky said:
I'm thinking for m7ul it would be https://github.com/CyanogenMod/android_kernel_htc_m7/commit/f2efb02581110747711c8b17f31f38fc3ed5dd1a
Don't want to hijack the thread though, so we can probably discuss this elsewhere
Click to expand...
Click to collapse
we already making progress but it needs more work to be done.. at least we are now in system with working wifi, and display but modem doesent work.. something for tomorrow, and i dont want to hijack this thread too sorry if my question was in the wrong section but i thought i mention it because of the post above mine. nevermind i cann offer to maintain m7ul as already discussed with maxwen and oin IRC but a lot of work needs to be done:
here are my sources, device trees are usable but kernel needs more work as said above:
device trees:
https://github.com/n3ocort3x/android_device_htc_m7ul
https://github.com/n3ocort3x/android_device_htc_m7-common
https://github.com/n3ocort3x/android_device_htc_msm8960-common
kernel: its a modified one but its no problem to bring it back to stock features and will push as soon asap the modem stuff is sorted out
https://github.com/n3ocort3x/android_kernel_htc_m7
EDIT modem fixed, only BT left

@sykomaniac , look at first post and become a maintainer

pulser_g2 said:
If you are a developer, and wish to have a device merged into Omni, here is the current "temporary" process to use. There are 2 ways to do this - make your tree available on github (or a similar service), or request a new git tree be created, and submit it to gerrit.
1) Get your device working. There's plenty of help available in #omnirom on Freenode if you need assistance. An AOSP device tree is probably the best place to get started.
2) Set up your device to use the OmniROM "custom" build type, rather than full/aosp. More information will follow on this step - check device/samsung/manta or device/lge/mako for an example.
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
4) Post a link here to the device tree (and kernel repository) for review, and tell us what device it is (give model numbers and board names and as many details as possible )
Click to expand...
Click to collapse
We have quite a few things that aren't working like bluetooth, camera is buggy, H/W vsync, gps, and fm radio.
https://github.com/SeannyM/android_device_samsung_kylessopen
https://github.com/SeannyM/ba2x-kernel
gt-s7560m with quadband gsm and 850/1900/2100 WCDMA/UTMS
We have a MSM7227a cpu armv7 clocked at 1008mhz stock.
645mb of usable ram
4gb of storage with 1.7 usable
233 dpi 800x480 4inch screen
Adreno 200 enhanced
5mp camera 1.3 front facing
hopefully we can get something official
single sim

Gtab2 10.1 Wifi & 3G (p5110 & p5100)
There you have my device tree for omni
p5110 :
https://github.com/sevenup30/android_device_samsung_p5110
p5100:
https://github.com/sevenup30/android_device_samsung_p5100
omap4-common (had to edit it cuz of duplicate libion entry):
https://github.com/sevenup30/android_device_samsung_omap4-common
other dependencies required from CM & Themuppets
kernel :
https://github.com/CyanogenMod/android_kernel_samsung_espresso10
samsung proprietary:
https://github.com/TheMuppets/proprietary_vendor_samsung
samsung hardware:
https://github.com/CyanogenMod/android_hardware_samsung
apps samsung service:
https://github.com/CyanogenMod/android_packages_apps_SamsungServiceMode
Everything is working (sound / wifi / bluetooth / video playback) BUT!
I must edit build.prop by hand to get sound working until omni build process take care of "product_build_prop_overrides" into custom_XXXX.mk
see:
http://forum.xda-developers.com/showthread.php?t=2484747

Original Samsung Galaxy Note
Samsung n7000 initial bringup:
Modified CM n7000 device: https://github.com/chasmodo/android_device_samsung_n7000/tree/android-4.3
Modified CM galaxys2-common: https://github.com/chasmodo/android_device_samsung_galaxys2-common/tree/android-4.3
CM smdk4412 kernel: https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/tree/cm-10.2
Samsung proprietary stuff: https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-10.2
Samsung hardware tree untouched from OmniRom.
Device info:
Board platform - exynos4
SOC - exynos4210
Board name - smdk4210
Kernel specifics - unified kernel and recovery
It compiles fine using the repos listed above, but throws up a kernel assert error when flashing the Rom. Several compilers for different devices complained about it in the 'All the answers' thread. The way out of this is to flash a CM10.2 kernel immediately after the Rom flash aborts, then Omni boots up fine.
What works:
1. telephony
2. mms
3. WiFi
4. GPS
What doesn't work:
1. data
2. bluetooth turns off as soon as you turn it on
3. both sdcards are invisible from Android; all your stuff is there when you drop into recovery, though
4. Settings/Storage FC when tapped - see #3
5. Performance options also FC
6. Notification drawer cannot be pulled down
Camera cannot be tested because it shuts down as soon as you start it, saying: "No external storage available" - again, see #3

Galaxy Note II / N7100 (International)
Samsung Galaxy Note II / N7100 Bring up details.
I have a working build of the Omni rom for the N7100. Below are the details on what is working and not working. i have been using it for the last 2 days, so far not crashes or reboots all seems to be working fine. i cherry picked a few commits and included it into my build
Working :
WIFI
DATA -3G & 2G
Telephony & MMS & SMS
GPS
Sound
Camera (Both Front and Back)
SD card
Performance control
Notification drawer & Lights
Multi-Window
roadrunner
Not Working :
BT
Backlights(if i install a custom kernel then the lights work)
Device Tree for N7100 - https://github.com/tilaksidduram/device_samsung_n7100
Device smdk4412-common - https://github.com/tilaksidduram/android_device_samsung_smdk4412-common
smdk-4412 Kernel (3.0.100) - https://github.com/CyanogenMod/android_kernel_samsung_smdk4412
samsung hardware - https://github.com/CyanogenMod/android_hardware_samsung

DEVICE: GT-N7100
sources
https://www.github.com/UtkarshGupta/android_device_samsung_n7100
https://www.github.com/omnirom/android_device_samsung_smdk4412-common
https://www.github.com/omnirom/android_hardware_samsung
https://www.github.com/omnirom/android_kernel_samsung_smdk4412
https://www.github.com/TheMuppets/proprietary_vendor_samsung

Is anyone else working on d2att/d2can (Galaxy S3 I747)? I'm not overly familiar with ROM development, but I can compile CM10.2 for this device just fine, and I'm slowly working on getting Omni to compile for it as well. If someone more experienced than I is already working on it though, I'll probably just let them do it.
If I am the only one, expect some newb-ish questions in the near future.

dstruct2k said:
Is anyone else working on d2att/d2can (Galaxy S3 I747)? I'm not overly familiar with ROM development, but I can compile CM10.2 for this device just fine, and I'm slowly working on getting Omni to compile for it as well. If someone more experienced than I is already working on it though, I'll probably just let them do it.
If I am the only one, expect some newb-ish questions in the near future.
Click to expand...
Click to collapse
I think a few are... There has been chat of it in the IRC channels.

Device name: LG Optimus 4X HD
Codename: P880
Board name: X3
Chipset: Tegra 3 AP33
Everything works, except button backlight.
https://github.com/Adam77Root/android_device_lge_p880
https://github.com/Adam77Root/android_kernel_lge_x3
https://github.com/TheMuppets/proprietary_vendor_lge

[UNOFFICIAL][ROM][10.0/9.0] LineageOS 17.1/16.0 [violet][Q/PIE]

Introduction
A spinoff thread from the previously-supported-official thread by Atman.
This thread will contain my unofficial builds for violet. On the 16.0 version, the only real fix (so far...) have been the fingerprint scanner sepolicy denials. I aim to do monthly/bimonthly builds to keep up to date with security patches, as so far I haven't encountered any other issues (let me know).
On the 17.1 version, I have slowly figured out how to make it work, but it is highly experimental.
The 16.0 ROM is stable (I use it as my daily driver).
If you find any bugs, please do take screenshots, give a way for me to replicate it on my device, and send a logcat. If you're super smart, use a logcat and filter for the keyword so I don't have to do even more digging
Please don't tell me to use PE/Mokee commits.
Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Flash instructions
Same as usual:
Reboot to fastboot and flash recovery with fastboot (You have to use the TWRP linked below. Other versions likely won't boot.)
Reboot to recovery TWRP
Wipe to format data, wipe again to wipe system and cache (not necessary if you're updating, only if you're switching ROMs)
Flash firmware (ADB sideload) (this step is dated. The newer builds have a higher target firmware so you should try to flash without the firmware first, then flash the firmware if the ROM doesn't work.)
Flash the ROM (sideload)
Flash GApps, Magisk, etc. as necessary
Done
Downloads (16.0) (STABLE)
Firmware (Dated firwmare)
Recovery (TWRP)
11-Jun-2021 build (with 05-May-2021 security patch), and MD5 Digest
For previous builds see below
Downloads (17.1)
Here's the 17.1 ROM. Here's the md5 hash. It has the March security patch.
It currently does not boot. If you would like to try and help with development, flash the ROM, and then flash the Chinese Q firmware on top of it (this can be downloaded from xiaomifirmwareupdater). Be warned that there is a risk that the newest android keymaster may re-encrypt your device, which in the worst case may require you to format data and/or reflash recovery and/or flash a fastboot MIUI rom. So, it's a bit risky, but likely won't be an issue.
Credits, Sources, etc.
Too many to mention. Atman Shah for getting this device supported earlier last year. ThE_MarD (Marc Bougoin) for other help. Various other names I've seen - Bruno Martins, Weikai Kong, Wang Han... all of the Lineage dev team. I'm sure I'm missing many people who have been involved in the project. I am new, and very much a latecomer to all of this.
Device Tree: https://gitlab.com/mzha/android_device_xiaomi_violet
Kernel Tree: https://gitlab.com/mzha/android_kernel_xiaomi_violet
Other things see my gitlab: https://gitlab.com/mzha
A telegram group to discuss development for 16.0/17.1: t.me/lineageos_violet
Previous builds
07-Nov-2020 (incl. Oct-2020 security patch), with 07-Nov-2020 MD5 Hash
13-Jul-2020 (incl. Jul-2020 security patch), with 13-Jul-2020 MD5 Hash
11-May-2020 (incl. May-2020 security patch), with 11-May-2020 MD5 Hash

Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?

e2vinay said:
Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?
Click to expand...
Click to collapse
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time

hcnulma said:
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time
Click to expand...
Click to collapse
That's great
by any chance will you consider adding signature spoofing support? that would be really great. it would help many users go for microG instead of gapps
I completely understand you're starter.
great work. good luck.
Thank you

e2vinay said:
will you consider adding signature spoofing support?
Click to expand...
Click to collapse
No, but there are a few alternatives:
Merge the changes from this RFC and build it
Download the spoofer from https://download.lineage.microg.org/violet/, or get the (ed)Xposed module, or other possibilities...

Will be official Lineage Os?

Can we expect los 17 soon?

himanshu fulmali said:
Can we expect los 17 soon?
Click to expand...
Click to collapse
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.

Heyyo @hcnulma good to see you got your thread up and going!
As for 17.1? You can work with your current kernel and cherry-pick the fixes that other maintainers of violet are using and same for the device tree and vendor blobs.
As an example, LeEco msm8996 devives are using kernel source code from Marshmallow just rebased on a CAF Q Tag for our kernel since we never got anything newer...
Even once Xiaomi release their kernel source code for Android 10? It would probably take quite a bit of work to shave it down to what you specifically need and then importing it on top of a fresh CAF tag for the kernel or even more work to try and inplement it into uour current kernel.
To get official builds of LOS 16.0 going again for violet you would need to show that you are capable of fixing any major bugs that arise as well.
https://wiki.lineageos.org/submitting_device.html
anywho, hope this information helps bud!

hcnulma said:
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.
Click to expand...
Click to collapse
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom

Thank you. If he is stable enough I will use it to build RR PIE

Zjh0094 said:
Thank you. If he is stable enough I will use it to build RR PIE
Click to expand...
Click to collapse
It's definitely stable...
prajwal2001 said:
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom
Click to expand...
Click to collapse
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.

Request to create group for discussion in Telegram

hcnulma said:
It's definitely stable...
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
as every ROM uses the same device tree
and you won't be making pe instead of lineage as the same device tree and kernel are used in every Q ROM except EvoX which uses crimson kernel

hcnulma said:
It's definitely stable...
Click to expand...
Click to collapse
Thanks. I will use it as my benchmark to build RR pie.
---------- Post added 15th February 2020 at 12:03 AM ---------- Previous post was 14th February 2020 at 11:57 PM ----------
hcnulma said:
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
/quick/la/msm-4.14

prajwal2001 said:
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
Click to expand...
Click to collapse
It is precisely the device tree that I'm worried about. From experience, PE has a lot of platform-specific stuff that Lineage doesn't (and the same the other way), and also from trying to figure out the fix to 16.0 I realised there's a lot of context/definition differences between the two device trees. I'd still give it a look, but I suspect it might be easier to just modify the current 16.0 device tree.
RupeshRN said:
Request to create group for discussion in Telegram
Click to expand...
Click to collapse
https://t.me/lineageos_violet.
Zjh0094 said:
/quick/la/msm-4.14
Click to expand...
Click to collapse
Yeah I already figured it was msm-4.14. Have already cloned it but am also considering cherrypicking changes that other devs have done to their kernel trees from 16.0 -> 17.1 as opposed to starting with the CAF kernel. A work in progress.

Sir I'm noob but mokee dev released android 10 and i think mokee and los are pretty same, will he not help you if you contact him?

An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.

An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.

Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Here's the 17.1 ROM. Here's the md5 hash. Needless to say, it's very experimental, not stable in the least (expect to get past boot maybe 70% of the time) - I'm getting very mixed results when experimenting myself. Nevertheless, try it out, see what you get. Install it the same way as usual. Keen to get as many eyes on this as possible

Custom rom for Note 10 / Note 10 lite - I seek guidance/help

Hello,
I'd like to get into android ROM development. But I will need help/guidance.
I've managed to build lineageos for curtana using xiaomi kernel and malachite device tree and vendor files. Don't know it it actually works as I don't have the device
.
So as I said I'd like to learn it, but as android is big I am still kinda lost in it. I know i can create something that already is, but that is not useful to the others, so that's why I am thinking about these 2 devices xiaomi note 10 or note 10 lite as they don't have any roms yet.
So if there is anyone who will be able to help and guide me through the process of getting device tree, vendor files and using (xiaomi) kernel putting it all together, I will be more than happy to buy one of those devices and go and create and support some lineageos, aosp and or pixel experience roms.
Thanks

Gajdalf said:
Hello,
I'd like to get into android ROM development. But I will need help/guidance.
I've managed to build lineageos for curtana using xiaomi kernel and malachite device tree and vendor files. Don't know it it actually works as I don't have the device
.
So as I said I'd like to learn it, but as android is big I am still kinda lost in it. I know i can create something that already is, but that is not useful to the others, so that's why I am thinking about these 2 devices xiaomi note 10 or note 10 lite as they don't have any roms yet.
So if there is anyone who will be able to help and guide me through the process of getting device tree, vendor files and using (xiaomi) kernel putting it all together, I will be more than happy to buy one of those devices and go and create and support some lineageos, aosp and or pixel experience roms.
Thanks
Click to expand...
Click to collapse
The problem is that there are no working trees yet. The only thing which is not working is the display. the display is just dead

[rom][aosp][grouper-tilapia][ua]android-8

Hello guys This is AOSP unlegacy android build.
It is a android version-8 (TESTING) .
Sources-
Source code- https://github.com/Unlegacy-Android/android
device- https://github.com/Unlegacy-Android/android_device_asus_grouper/tree/aosp-8.1
kernel- https://github.com/Unlegacy-Android/android_kernel_nvidia_tegra3
vendor - https://github.com/Unlegacy-Android/proprietary_vendor_nvidia/tree/aosp-8.1
Sorry links might be broken or removed
Issues
no camera
does not function with Gapps
no proper otg support
Thanks
@unlegacy android team
@Ziyan
@aosp
Status-testing
This security patches dupes and is faked
****disclaimer
Im not responsible for any kind of damage to device
If you point your finger at us we'll laugh at you
Guys I have got 2021 security patch level at the first flash and at the second flash I found it 2018. Just comment me your security patches.
Works on tilapia and grouper
download Link https://drive.google.com/file/d/10VaRPsRlJTsnKXLkmOiwpcD9pQP9wZNW/view?usp=sharing

Thank you!
I will use it!
edit:How did you write local_manifests?
Also, did you use the Tegra3 hardware tree?

Hey guys how is this rom

few__ said:
Thank you!
I will use it!
edit:How did you write local_manifests?
Also, did you use the Tegra3 hardware tree?
Click to expand...
Click to collapse
Yup I used the normal repo commands (I don't remember properly as I started compiling it 1.5 year ago)
SORRY for if any wrong sources aye!

Hi
Is ROM better than @ud4's 8.1.0 ROM? I currently have @ud4's and there an issue where some apps (like RedReader, Magisk Manager stable, Play Store, etc...) won't launch; they just show a blank screen. Does this ROM also have that issue?
Thanks

[ROM] [UNOFFICIAL] LineageOS 14 for Meizu M5C [MT6737m]

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