Related
Hi,
So as many of you already knew - I'm working on porting CM13 onto my NU3001.
I has it on my desk table, so I could work on it during my days. (I have another NR3001 installed in my car)
I already made some work for our unit SW. This is quick screenshots. Sources based on xdAuto and CM13. This is a very BETA and many things not working for now.on.
Why? : When I realize than CyanogenMod 13 (6.0.1) works on my Motorola XT1080 better than stock - I start thinking of porting CM13 to our device. And when I have spare set - I start porting.
How? : I took easiest way - try to do not modify kernel a lot, instead adopt bionic and other libraries for out 3.0.36+ kernel.
Currently working staff (it is very beginning):
1. Recovery TWRP 3.0.2
2. CM13 (LineAge OS) booting.
3. Graphics working (there is some blinking present).
4. Wifi working
5. Android audio working
6. Bonovo Radio working
4. Most of the rest is on the way (GPS, BT, rest of Bonovo apps)
UPDATE_1:
I decide to do not stuck with CM 13 and switch to AOSP N release (7.0) (mostly because on my daily job - we also going to Android N, so it should be more familiar to me now)
Currently working staff:
1. Recovery TWRP 3.0.2
2. SELinux needs to be carefully ported (kernel part), cause starting from 7.0 is can not be disabled (as I did for CM13 to easy port)
During this port I will try to minimize inpact to AOSP release, so any future updates should be much more easier.
For you to understanding of amount of needed work - kernel already has 100+ patches on top of xdauto release. Approximate left about 250-300 patches to revise/port.
Android 7.0 port abandoned because of bigger and bigger amount of work need to be done to port SELinux on top of our outdated kernel.
UPDATE2:
I setup review build environment, so who want to look at NOT-FULLY-WORKING CM13 could download sources and binaries. I do not provide instructions how to flash it, because who wants to look and contribute already know hot to flash, and who doesn't probably don't really want this NOT-FULLY-WORKING CM13
UPDATE3:
So I finally managed to get functional networking. So now Wifi working, internet working, display working.
I starting to port all necessary items. No more 'hard' showstoppers so far.
New build (I believe it is build number 5) should be ready in an our on build server, so I could test it more fully.
UPDATE4:
Cause CyanogenMod is no more maintained - switched to it's successor Lineage OS 13.0, starting from build 8
UPDATE5:
Build number 15 has working audio + radio
UPDATE6:
Most of Bonovo changes ported, new build 20 ready.
This build contains zip file which should be flashable via twrp, but I not test it this way.
Issues remaining so far(most noticeable to me):
1. Display flickering (my suspect is to vsync/fence mechanism slightly changed in Android 6.0, need to investigate)
2. HW Volume buttons not working on device
3. No audio In
UPDATE 7:
Starting from build 23 following images available:
cm_rk3188-ota-XX.zip - update to use via TWRP
nu3001-la-cm13-XX-userdebug.tar.gz - build image for flash via command line rkflashtool under linux (full or partial flash)
rkflash_nu3001-la-cm13-XX-userdebug.zip - Full image to be flashed via PC GUI RK Batch Tool.
kernel_nu3001-la-cm13-XX-userdebug.tar.gz - just kernel with debug symbols for debugging purposes.
To just download sources:
repo init -u https://gerrit.nc.org.ua/manifest -b nu3001_cm13
If you plan to contribute - login to Gerrit with GMail, push your SSH public key, choose login name and then do:
repo init -u ssh://<user>@gerrit.nc.org.ua:29418/manifest -b nu3001_cm13
Builds will be available on Jenkins build server (login also via GMail, PM for access grant on current project stage):
https://jenkins.nc.org.ua/
1.5 GB folder on MEGA
4 files
mega.nz
Please do not spoof this thread with questions like "When?", I will try to post updates regularly in this message.
This thread created is mostly to exchange experience with this build once it is published (issues, TODOs, etc)
**Reserved **
First!
Second! Lol
I'm not a developer so unfortunately I can't contribute, but hopefully those who can will.
At the very least I can beta test when its a little more complete.
Android port system less complicated than the application Bonovo.app and MCU. Good luck and patience.
Black're a legend !!
Your project is great !!! see Android 6.0 on Carpad would be great.
Thanks for the great effort you make for all
Woooow great !!
Good luck
nice one, i hope a very important feature:
"that can be use apps, which require android +4.4.4, like lollipop"
I say that because android auto "stand alone" coming soon, so if will be possible install this app in the radio, we have android auto pure, ( not automate that is awesome but is not the same like original ), and maybe mp3 stuttering from usb can be solved in this rom.
keep up work!
Thanks for the sneak peak, looks promising. I'll gladly help sponsor a new device if you happen to brick yours. I love this headunit and how far the community has gotten in supporting it.
I want to buy NU3001 now, is there any way to get it?
vivacious said:
I want to buy NU3001 now, is there any way to get it?
Click to expand...
Click to collapse
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
vivacious said:
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
Click to expand...
Click to collapse
I just put NU3001 to aliexpress search bar and found a lot of propositions, I think there should be available one.
Hi VBlack,
it's nice to know you're making progress on the new ROM CM13. All are rooting for you !! Your work would be wonderful !!
I have only one question:
With the ROM of XDAuto I found an annoying problem that occurs when i turn off and then relight the Carpad.
When the power back very often the Carpad car remains with black screen until i touch it with my finger.
I think the problem is somehow related to the USB ports.
Even with your ROM does this happen ?? When you turn on the car, the Carpad remains ever with black screen ??
Thank you!!
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
Nice to hear from you. Sure I will share. Current situation is next:
CM13 - no wifi (looks like netfilter from userspace not match netfilter from our outdated kernel), no selinux (completely disabled), and increased system partition to be able to add opengapps, twrp - works.
AOSP 7 - it is strongly rely on selinux, so i could not just disable it, and now I'm trying to merge new selinux with our old kernel...
So, i will upload CM13 in current state, and continue on aosp 7, if i fail with aosp 7 i will back to cm13. This is current plan.
Sent from my DROID MAXX using Tapatalk
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
I update first post with sources and build information
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
shatteredsilicon said:
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
Click to expand...
Click to collapse
No, we have kernel sources, but our kernel version 3.0.36 and looks like nobody release Android kernel 3.14 or 3.18 for rk3188. 3.14 and 3.18 mostly used in Android M and N. So combining Android M or N with such outdated kernel is not a trivial task. Because of this incompatibility we currently have all networks issue on this CM13 project.
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
shatteredsilicon said:
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
Click to expand...
Click to collapse
You'd be surprised how many phones in the market use old kernels (3.0 is not too old for Android - it is about 2-3years off from active development).. But true is that Android kernel despite it's version less vulnerable than Desktop one, and has many fixes included (it is does not increase kernel version, like mainline kernel). Because of this it is generally hard to say which security issue will be there for sure. But on the other hand Android N and Android M has SELinux enabled, and Android N could not have it disabled. It is dramatically increase overall security of the system. But for the most of traditional Android user kernel exploits does not produce many harm - it is not a corporate server with sensitive information. And many of them used to obtain root on bootloader locked systems.
So generally for what I have in mind:
1. If succeeded just with CM13 - I have disable SELinux there - it is will be not less secure than original 4.x release - just system/google components will be upgraded, which allow us use modern UI features from Android M, and also adds more compatibility with new applications revisions.
2. If succeeded with AOSP 7.0 - SELinux will be enabled there, so we will have security addition on top of old kernel, which actually will increase security alongside allowing UI features from Android N.
So in any case it is very nice to have.
Android experience relies heavily on Google's Play Services. The microG project creates an alternative to installing Gapps, which install and execute closed-source blobs on our phones. MicroG however requires a patch called "signature spoofing", which allows microG's apps to spoof themselves as Google Apps. LineageOS currently does not include the patch due to different opinions among the developers. (further information can be found here)
This makes microG installation difficult on LineageOS and other ROMs. Our ROM is a fork of LineageOS with just the necessary changes to have microG built-in. We ship weekly builds for all the LineageOS supported devices..
You can find us on https://lineage.microg.org
XDA:DevDB Information
LineageOS for microG, ROM for all devices (see above for details)
Contributors
Simon94, ncorna, n1zzo, LineageOS, MaR-V-iN
Source Code: https://github.com/lineageos4microg
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-11-06
Last Updated 2020-08-28
Would like to have build for Nexus 9 aka flounder
Awesome start! Good luck with that! Cheers! :fingers-crossed:
Is this the thread mentioned in the FAQ where one can request builds for other devices supported by LineageOS?
If so, I'd love to see a build for the LG G5 (aka h850), which is currently the only high-end device by a known manufacturer with a removable battery and high repairability (8/10 from Ifixit).
It's fully supported by LineageOS (https://wiki.lineageos.org/devices/h850) and I'd be willing to report any possible problems and help debug it if necessary.
Thanks in advance and awesome project!
Can you please add support for LG G4 (H815) as well?
The LineageOS for microG OTA infrastructure is based on https://github.com/julianxhokaxhiu/LineageOTA?
I'm mounting my own infrastructure and I want to know how to build it. Thanks.
Current device list which will be built tomorrow:
Code:
a6020,angler,armani,athene,bacon,bullhead,cancro,capricorn,cheeseburger,clark,condor,crackling,d855,
deb,dragon,falcon,flo,flounder,gemini,h815,h850,hammerhead,harpia,herolte,here2lte,hlte,i9100,
i9300,jfltexx,kenzo,klte,libra,lux,m8,mako,mido,oneplus2,oneplus3,onyx,osprey,otus,paella,pme,
serranoltexx,shamu,thea,titan,victara,wt88047,yuga,Z00L
Simon94 said:
Current device list which will be built tomorrow:
Code:
a6020,angler,armani,athene,bacon,bullhead,cancro,capricorn,cheeseburger,clark,condor,crackling,d855,
deb,dragon,falcon,flo,flounder,gemini,h815,h850,hammerhead,harpia,herolte,here2lte,hlte,i9100,
i9300,jfltexx,kenzo,klte,libra,lux,m8,mako,mido,oneplus2,oneplus3,onyx,osprey,otus,paella,pme,
serranoltexx,shamu,thea,titan,victara,wt88047,yuga,Z00L
Click to expand...
Click to collapse
Please, include piccolo!
DaniPhii said:
Please, include piccolo!
Click to expand...
Click to collapse
Done!
@Simon94 does it supports substratum ? and thanks for the modded lineage .
Microg.me is a really wonderful project , I have been using it for 3 days, but there are some things that annoy me. In particular, is it really necessary to implement it in every single build ?? I use an application with the same signature, so at each ota it is replaced by the fakestore and that's annoying . Also one ota per day is pretty excessive I think, especially for daily usage. Why not release an update at the same time as the official lineage ?
Please excuse me if the answers to my questions are obvious, I'm a bit new on microg.
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual
sandeep_7 said:
@Simon94 does it supports substratum ? and thanks for the modded lineage .
Click to expand...
Click to collapse
Same feature-set as LineageOS. If LOS supports substratum, we are supporting this aswell.
Silver_Defender said:
Microg.me is a really wonderful project , I have been using it for 3 days, but there are some things that annoy me. In particular, is it really necessary to implement it in every single build ?? I use an application with the same signature, so at each ota it is replaced by the fakestore and that's annoying . Also one ota per day is pretty excessive I think, especially for daily usage. Why not release an update at the same time as the official lineage ?
Please excuse me if the answers to my questions are obvious, I'm a bit new on microg.
Click to expand...
Click to collapse
Unfortunately we wont remove FakeStore since our goal is to provide a Google free ROM with a fully working ecosystem which requires having FakeStore installed. Sorry for that. What you could do is to write a script for OTA survival / - or removal and put it in the /system/addon.d directory. But we're not going to support this in any way.
Otherwise we can invite you to not use Play Store, but a replacement like Yalp Store.
We like to build as often as we can. Its up to you and your free choice. If you dont want to update on a daily basis, just dont do it
Best, Simon
MaStErB_1984 said:
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual
Click to expand...
Click to collapse
..
https://lineage.microg.org/#faq said:
Can you add support for my device? It is not supported by LineageOS though...
No, I'm sorry.
Click to expand...
Click to collapse
MaStErB_1984 said:
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual
Click to expand...
Click to collapse
There are several methods to get microg. Maybe you should start reading there https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047
My preferred method have been nanomod patcher and shadow53's zip.
I can't find my device in the download section!! Yu yunique (jalebi). As the site says that all the devices with official linegae os support will get this rom?? Pls provide for my device jalebi. Thanks in advance.
Shashank Varma said:
I can't find my device in the download section!! Yu yunique (jalebi). As the site says that all the devices with official linegae os support will get this rom?? Pls provide for my device jalebi. Thanks in advance.
Click to expand...
Click to collapse
Added in next build.
Simon94 said:
Added in next build.
Click to expand...
Click to collapse
Thank you!! Waiting for it
Hey there! I have an old first-gen Moto X as my main android device (ghost) and I'd love to take advantage of your awesome project! I tried to get the docker image up and running myself, but I keep getting random DNS failures in docker, which seem to get silently passed, which results in the build claiming to be successful, yet no builds show up in my "zips" folder when it completes. Only thing that I think needs changed from the default is the lineageOS branch (cm-13.0). Would it be too much trouble to add 'ghost' to your list of builds?
Thank you,
neutral
Can you add support for taoshan (Sony Xperia L)?
Has LOS support.
Thanks!
Moto g5 cedric?
[ROM][addison] Unofficial LineageOS 14.1
Moto Mods are not supported
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please check out the Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Working
Boots
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Video Playback
LED Notifications
NFC
Not Working/Bugs
–
Installation
1. Make sure you have a nougat bootloader and modem else TWRP denies the installation by throwing a message about the wrong bootloader. You can find a guide here: https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91
2. Requires Unlocked Bootloader & a custom recovery
3. Place ROM & Gapps (if applicable) in your virtual SD
4. Reboot in Bootloader Mode
5. Go to "Recovery" (Vol +/Vol -) and confirm (power)
6. Wipe Data/Factory Reset
7. Wipe Dalvik cache
8. Install the ROM zip
9. Install su for root. You can get the required file from here https://mirrorbits.lineageos.org/su/addonsu-14.1-arm-signed.zip
10. Install the Gapps zip (if applicable)
11. Reboot
Note
I have not built any of these ROMs myself, I'm simply just listing them for convenience sake. All credits go their rightful creators and to @Alberto97 for laying the groundwork for Moto Z Play development.
Downloads
@fablebreton's build: https://androidfilehost.com/?fid=817906626617950356 with november's security patch, built December 2nd.
@Shreps's build: https://moto.shreps.fr/?dir=Moto Z...29/ROM/Lineage with november's security patch, built December 9th.
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the Moto Z Play
Contributors
Mr_prfssnl, Alberto97, fablebreton, Shreps
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Version Information
Status: Beta
Created 2017-12-12
Last Updated 2017-12-12
I have used the first rom in your list and it is November patch too
Jagadhidh said:
I have used the first rom in your list and it is November patch too
Click to expand...
Click to collapse
Oops, sorry about that, I reported the information to him and made a mistake. All have November's patch indeed and Flashqueen's includes part of December's.
Ultramanoid said:
Oops, sorry about that, I reported the information to him and made a mistake. All have November's patch indeed and Flashqueen's includes part of December's.
Click to expand...
Click to collapse
I have changed the description accordingly ?
This might be of interest for users that come searching for unofficial Lineage builds.
The Lineage with MicroG project is still building for this device, and they do every couple of days, by the way. Actually nightlies.
XDA thread : https://forum.xda-developers.com/android/software/lineageos-microg-t3700997
Build downloads : https://download.lineage.microg.org/addison/
Edit : The last build as of this post is from December 11th, and declares a December security patch.
Ultramanoid said:
This might be of interest for users that come searching for unofficial Lineage builds.
The Lineage with MicroG project is still building for this device, and they do every couple of days, by the way. Actually nightlies.
XDA thread : https://forum.xda-developers.com/android/software/lineageos-microg-t3700997
Build downloads : https://download.lineage.microg.org/addison/
Click to expand...
Click to collapse
Can this Roms be dirty flashed over existing @Alberto97 nightlies from november?
Thats my biggest fear - to have to clean everything and reinstall the whole device....?
Can you provide a little help for this circumstance... i guess there are many user with the same issue.
Thank you!
Cheers
finfin82 said:
Can this Roms be dirty flashed over existing @Alberto97 nightlies from november?
Thats my biggest fear - to have to clean everything and reinstall the whole device....?
Can you provide a little help for this circumstance... i guess there are many user with the same issue.
Thank you!
Cheers
Click to expand...
Click to collapse
It was already answered a couple of times in the official thread ( where you also asked ), so please read the posts before yours there or at least search before asking, which is expected in the forum.
You can migrate from an official build to an unofficial, and vice versa, simply using the appropriate script ( before flashing the rom ) found here :
https://forum.xda-developers.com/showpost.php?p=70452245&postcount=2
Edit : Just make a backup in TWRP before proceeding, to be safe, and you can always restore that if you have any issues.
This is listed in the wrong section... this is why XDA has a section called: Moto Z Play ROMs, Kernels, Recoveries, & Other Development
They thought ahead.
https://forum.xda-developers.com/moto-z-play/development
Mr_prfssnl said:
[ROM][addison] Unofficial LineageOS 14.1
Moto Mods are not supported
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please check out the Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Working
Boots
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Video Playback
LED Notifications
NFC
Not Working/Bugs
–
Installation
1. Make sure you have a nougat bootloader and modem else TWRP denies the installation by throwing a message about the wrong bootloader. You can find a guide here: https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91
2. Requires Unlocked Bootloader & a custom recovery
3. Place ROM & Gapps (if applicable) in your virtual SD
4. Reboot in Bootloader Mode
5. Go to "Recovery" (Vol +/Vol -) and confirm (power)
6. Wipe Data/Factory Reset
7. Wipe Dalvik cache
8. Install the ROM zip
9. Install su for root. You can get the required file from here https://mirrorbits.lineageos.org/su/addonsu-14.1-arm-signed.zip
10. Install the Gapps zip (if applicable)
11. Reboot
Note
I have not built any of these ROMs myself, I'm simply just listing them for convenience sake. All credits go their rightful creators and to @Alberto97 for laying the groundwork for Moto Z Play development.
Downloads
@fablebreton's build: https://androidfilehost.com/?fid=817906626617950356 with november's security patch, built December 2nd.
@Shreps's build: https://moto.shreps.fr/?dir=Moto Z...29/ROM/Lineage with november's security patch, built December 9th.
@Flashqueen's build: https://mega.nz/#!VrwFCJxa!Fza8TlHFJ...Z9eCcRw5XZwZmA with november's security patch + part of December's security patch, built December 9th. Also has integrated root and UnifiedNlp support.
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the Moto Z Play
Contributors
Mr_prfssnl, Alberto97, fablebreton, Shreps, Flashqueen
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Version Information
Status: Beta
Created 2017-12-12
Last Updated 2017-12-12
Click to expand...
Click to collapse
Jimi Mack said:
This is listed in the wrong section... this is why XDA has a section called: Moto Z Play ROMs, Kernels, Recoveries, & Other Development
They thought ahead.
https://forum.xda-developers.com/moto-z-play/development
Click to expand...
Click to collapse
I tried placing the thread there but they moved it to this section, since I am not actually developing anything. I am merely listing the ROMs
Mr_prfssnl said:
I tried placing the thread there but they moved it to this section, since I am not actually developing anything. I am merely listing the ROMs
Click to expand...
Click to collapse
Odd being it is all formated as every other rom listed in that section.
---------- Post added at 07:14 PM ---------- Previous post was at 07:03 PM ----------
Ultramanoid said:
This might be of interest for users that come searching for unofficial Lineage builds.
The Lineage with MicroG project is still building for this device, and they do every couple of days, by the way. Actually nightlies.
XDA thread : https://forum.xda-developers.com/android/software/lineageos-microg-t3700997
Build downloads : https://download.lineage.microg.org/addison/
Click to expand...
Click to collapse
That looks interesting, thank you.
Mr_prfssnl said:
I tried placing the thread there but they moved it to this section, since I am not actually developing anything. I am merely listing the ROMs
Click to expand...
Click to collapse
Plenty of other people have opened threads where developers have later posted builds or applications, and those threads are naturally in development sections. I guess a listing only is a grey area and they're being strict but if developers eventually use this thread to post builds it'd be time to ask mods about moving it to development then.
Mr_prfssnl said:
[ROM][addison] Unofficial LineageOS 14.1
Downloads
@Flashqueen's build: https://mega.nz/#!VrwFCJxa!Fza8TlHFJ...Z9eCcRw5XZwZmA with november's security patch + part of December's security patch, built December 9th. Also has integrated root and UnifiedNlp support.
Click to expand...
Click to collapse
I'm sorry, but I managed to destroy my build tree due to an error
As I had no backup I've decided to move on and try AOSP 8. I hate to disappoint some of you but I can't provide builds anymore for the Z Play. So I'd suggest to move on to another of the provided builds. Thanks.
Flashqueen said:
I'm sorry, but I managed to destroy my build tree due to an error
As I had no backup I've decided to move on and try AOSP 8. I hate to disappoint some of you but I can't provide builds anymore for the Z Play. So I'd suggest to move on to another of the provided builds. Thanks.
Click to expand...
Click to collapse
Ouch. Any intention to look at Lineage 15 eventually ?
By the way, regarding the other builds, Shreps' link has changed, that build is now at :
https://moto.shreps.fr/?dir=Moto Z Play (addison)/ROM/Lineage
Ultramanoid said:
Ouch. Any intention to look at Lineage 15 eventually ?
By the way, regarding the other builds, Shreps' link has changed, that build is now at :
https://moto.shreps.fr/?dir=Moto Z Play (addison)/ROM/Lineage
Click to expand...
Click to collapse
Well, to be honest, I was so angry that I haven't yet tried to build up another source tree, which takes hours... So currently not. But if I will, I'll let you all know.
Flashqueen said:
I'm sorry, but I managed to destroy my build tree due to an error
As I had no backup I've decided to move on and try AOSP 8. I hate to disappoint some of you but I can't provide builds anymore for the Z Play. So I'd suggest to move on to another of the provided builds. Thanks.
Click to expand...
Click to collapse
I updated the thread. Thank you for your effort anyway
Is there any real difference between both releases?
Jimi Mack said:
Is there any real difference between both releases?
Click to expand...
Click to collapse
Shrep's build was done a week later, so a week's worth of Lineage commits and / or fixes over the older build.
I'm having a hard time flashing these Lineage OS ROMs. I'm running stock 7.1.1 prior to flashing 14.1, but I keep getting error 7. It says I have 0xC113 but I need 0xC105/106/107/112.
I've tried flashing just the bootloader from the latest 7.1.1 but I'm still stuck and it's driving me nuts.
What am I doing wrong?
Here's another unofficial build, but camera is now broken.
https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-lineageos-14-1-t3727440
Flashqueen's build remains the best fully functional one with at least up to most of December's patches ( even if it declares a November patch ) so at this point I'd still recommend it over anything else, other than getting a different, better supported device...
Edit : Lineage with MicroG support last put out a build December 17th, but those builds seem to be broken. I guess without a maintainer fixing things for the device, there's not much point in building as-is, see camera in the linked build above, for instance.
Ultramanoid said:
Here's another unofficial build, but camera is now broken.
https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-lineageos-14-1-t3727440
Flashqueen's build remains the best fully functional one with at least up to most of December's patches ( even if it declares a November patch ) so at this point I'd still recommend it over anything else, other than getting a different, better supported device...
Edit : Lineage with MicroG support last put out a build December 17th, but those builds seem to be broken. I guess without a maintainer fixing things for the device, there's not much point in building as-is, see camera in the linked build above, for instance.
Click to expand...
Click to collapse
Another good alternative to the above mentioned ROMs would be Mokee ROM. They actually support the device officially and it keeps getting updates on a daily basis. Although it is not actually Lineage it is in fact really close. It even comes with all of the Lineage features, wallpapers and apps by default. Another cool feature is that it comes with Xposed by default :victory:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 it
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
What is Project Treble
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition.
About
Weijianism did not build any verdor image of new version because he does not own this device. Although I am not familiar with android source and android build, I am very happy to learn it so that we natrium owners can use project treble.
So I message to Weijianism to know how to do it and have learnt it for a few weeks. Now I am trying to build vendors. Cause I still know a few about it, It is really very hard for me to solve problems in myself. So if you have any advice, please tell me or push you code in github. THANK YOU!
What is NOT WORKING
Camera
Let's test it together.
Download
ALPHA 0815 (boot.img + vendor.img)
How to
1. wipe everything using TWRP
2. flash boot.img + vendor.img
3. flash system.img
4. reboot to system
Sources
Kernel for msm8996 (lineage-15.1)
Configuration for natrium (lineage-15.1)
Configuration for msm8996 (lineage-15.1) (Minor patches)
Proprietary vendor (lineage-15.1) (Minor patches, forked from Weijianism , credits MZO)
XDA: DevDB Information
Project Treble for Mi 5s Plus
Contributors
Justin_hill
Weijianism
Thanks to
LineageOS
Mi 5s Plus devs
@Weijianism
ROM OS Version: 8.x Oreo
Rom Kernel: Linux 3.x
Version Information
Status: Testing
Created: 2018-08-13
Last Updated: 2018-08-16
Anyone try ?
Well, Bluetooth & Camera won't work on any gsi. Bluetooth service has been stopped. Can't connect to camera.
:c
Bluetooth working, but wifi is always dropping. did you take the drivers from los? also very laggy compared to old treble.
1. bootloop problem solved when using rr gsi. (code from hacker1024)
2. bluetooth service stoped problem solved.
QuiseShampe said:
Well, Bluetooth & Camera won't work on any gsi. Bluetooth service has been stopped. Can't connect to camera.
:c
Click to expand...
Click to collapse
The camera's problem seems very hard, I will try to use GCam later. Now I do have no idea about how to solve it.
You may help me solve it if you like!
pote2639 said:
Bluetooth working, but wifi is always dropping. did you take the drivers from los? also very laggy compared to old treble.
Click to expand...
Click to collapse
Yes, I used code and drivers from los totally.
And I really don't know what happened on your device cause you didn't tell me any useful information (such as what gsi and which version). I only find this kind of problem when using gsi of Android P Developer Preview.
justin_hill said:
Yes, I used code and drivers from los totally.
And I really don't know what happened on your device cause you didn't tell me any useful information (such as what gsi and which version). I only find this kind of problem when using gsi of Android P Developer Preview.
Click to expand...
Click to collapse
I used this version sgsi ones. Build PR1.
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
pote2639 said:
I used this version sgsi ones. Build PR1.
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
Click to expand...
Click to collapse
emm, maybe you should not use version of developer preview there is an experimental build of Android pie.
And I am so sorry that I would not like to spend time on version of developer preview.
justin_hill said:
emm, maybe you should not use version of developer preview there is an experimental build of Android pie.
And I am so sorry that I would not like to spend time on version of developer preview.
Click to expand...
Click to collapse
I guess I'll wait for android p stable sgsi build then.
Good day sir!
Is there any chance that this rom will be available to Mi 5s (Capricorn) soon?
rhp_engcoy said:
Good day sir!
Is there any chance that this rom will be available to Mi 5s (Capricorn) soon?
Click to expand...
Click to collapse
Hope for me get a new natrium and I'll do for capricorn and natrium too.
Ofc, as justin did for natrium already, I'm gonna just ship it on my custom ROMs projects, not separated things like capricorn should get it too.
@justin_hill
This is interesting, thanks for taking this up!
I'd like to mention that my last RR build has more recent vendor files than @Weijianism's treble builds.
I'm not sure why bluetooth only works with an RR GSI... That's weird. We need logs, of course.
I've never ported Project Treble to a device before, but I'm happy to help.
With the camera - I think this old branch of the kernel may work. I have no idea why, though.
P.S. I'm hacker1024 on GitHub.
theOriginalSuperl2 said:
@justin_hill
This is interesting, thanks for taking this up!
I'd like to mention that my last RR build has more recent vendor files than @Weijianism's treble builds.
I'm not sure why bluetooth only works with an RR GSI... That's weird. We need logs, of course.
I've never ported Project Treble to a device before, but I'm happy to help.
With the camera - I think this old branch of the kernel may work. I have no idea why, though.
P.S. I'm hacker1024 on GitHub.
Click to expand...
Click to collapse
Yeah, your code have inspired me a lot when I saw your repositories.
Maybe I fixed the bluetooth problem when I add back the libbtnv.so to /vendor/lib/ since it was deleted in this commit.
For the camera problem, I don't know how vendor module relates to kernel. But I will try it afterwards.
Actually I almost know nothing about lineage source code, system build skills and things like this. If you can help, it will be grateful!
any news on the development?
Crescendo Xenomorph said:
any news on the development?
Click to expand...
Click to collapse
About treble support I can tell that I'm gonna include in my ROMs, and maybe I'll give some vendor zips too, if @justin_hill doesn't care about that.
Crescendo Xenomorph said:
any news on the development?
Click to expand...
Click to collapse
Sorry, I am trying to do something about Treble for Android Pie, But there are still several problems unsolved. Cause I'm not familiar with those code, so maybe I can't solve it by myself. It will be so grateful if anyone can contribute to it.
So we will expect @Hlcpereira WORK, Thank you so much!
Hey, is the camera problem solved?
It can't be booting on any sgsi so what should i
do
I didn't find anything about it, so I came to share
Pixel Experience 10.0 Beta
Device: Redmi Note 4/4X (Mido)
By AryanKendare
Link from Last Build:
https://androidfilehost.com/?fid=1899786940962588662
Link from All Builds:
https://androidfilehost.com/?w=files&flid=284464
is there a thread link so we can share and discuss with the OP ?
Please, don't do this, let the developer share when it's ready
Do you have his permission to share his work?
Aryan will self release it when it's ready for everyone.
It's in testing phase & already in discussion in pixel experience 9.0 official thread.
Sent from my mido using XDA Labs
Waiting for official
well, it is available for download...why not...
tenssa said:
well, it is available for download...why not...
Click to expand...
Click to collapse
Waiting for some noobie crybabies
Sent from my mido using XDA Labs
It's available on telegram
PixelExperience Unofficial is here by @aryankedare
Changelog:
- Fixed VOLTE
- Fixed BT CALLS
- Fixed Most Of the Minor Bugs
*BUGS :
- FPS
- qcrilmsgtunnel fc
- magisk
Link:- https://www.androidfilehost.com/?fid=1899786940962589829
Note:
Please Consider Contributing to Server expenses which will help me to keep pe alive for mido
Join for bug report @Pixelexperiencemido
System-as-root will be send to all devs and testers
i read once that to install android 10 we need a different version recovery,coz with pie recovery it won't work
joe170 said:
i read once that to install android 10 we need a different version recovery,coz with pie recovery it won't work
Click to expand...
Click to collapse
Yeah.. but this ROM can install normally
xene10 said:
Yeah.. but this ROM can install normally
Click to expand...
Click to collapse
did u try it bro? or anyone ?
New look
The ROM was smooth but had some issues like Vote was not working and calls not working..... I installed it yesterday but I can't use is daily driver..
My TWRP 3.3.1-0 work fine with this, but sadly magisk doesn't work...
for now i don't have any bugs, only lock screen....it's hard to unlock, you have to swipe trough whole screen to unlock...is it even bug or normal thing on pixel phones?
edit, i tried calls and it works fine, for now i will use this rom daily and i'll keep watching for bugs
tenssa said:
My TWRP 3.3.1-0 work fine with this, but sadly magisk doesn't work...
for now i don't have any bugs, only lock screen....it's hard to unlock, you have to swipe trough whole screen to unlock...is it even bug or normal thing on pixel phones?
edit, i tried calls and it works fine, for now i will use this rom daily and i'll keep watching for bugs
Click to expand...
Click to collapse
No its not normal thing but when pixel experience pie version is released for mido last year it had the same problem.
tenssa said:
My TWRP 3.3.1-0 work fine with this, but sadly magisk doesn't work...
Click to expand...
Click to collapse
Try flashing the latest magisk 19.4 which apparently supports Android 10.
https://******************/magisk-beta
BUG: version PixelExperience_mido-10.0-20190920 (and all Android 10 beta builds before this):
If connect to LAN or WebCloud services (Google Drive, etc.) with X-plore file browser and run apk file from this cloud (copying to temp for running) then no installing app (apk) but runing as instalator in randomly apps in SmartPhone.
vrij said:
Try flashing the latest magisk 19.4 which apparently supports Android 10.
https://******************/magisk-beta
Click to expand...
Click to collapse
I have installed that version and it doesn't work either, the phone does not start
At the moment it is not possible to root
Magisk - I think it only supports a/b partitioning for Android 10, not A only on 19.4 build at the moment, so since we are an A only style device, Magisk Android 10 support isn't working yet
BUG: version PixelExperience_mido-10.0-20190920 (and all Android 10 beta builds before this):
If booting OS (after show bootlogo Pixel) quietly clicks (hardware sound) camera (as click if opening Camera app).
Maybe initialization?
In older versions (Pie) booting no camera clicks.