Who will bring this low-end OS to our device? First?
I was gonna ask the same question. Android GO is going to be the best way to put Android O on the moto e 2.
Android Go will be more stable and lag free. It'll reduce the need to use RAM heavy OS like the newer CM Builds. I hope they release the source and builds soon so that someone can port it to Condor.
Yes I know that our device is low end it really need this type of ROM but Don't expect this ROM any time soon before Q2 2018, as this project is expected to release by 2018. So be patient and wait for Android O.
After reading into details: GO will be a flavour of O. You can get a similar setup with existing custom ROMs and microG. Only GO feature i haven't seen yet: Restriction of recents to four apps.
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance
someone can port that? it could be good see R5+ with Miui 10 Pie ROM.
And why would you need it? Just to have Pie easter egg and 9.0 displayed when you enter "About phone"? MIUI is heavily modified framework, and as long as there is no official 9.0 update from Xiaomi (which imo is not going to happen, looking at the past few months of suspended global beta) there is no need for additional work that would bring new bugs and problems on top of the existing ones. Pie MIUI is basically the same as on Oreo anyway.
But, if you just need to flash your "About phone" tab to friends and others with 9.0, go to build.prop and change some things...
tl,dr: not worth the hassle
For the same reason that a personal create a custom rom aosp pie... To add another possibility and keep the update process alive for the R5+.
andrexp31 said:
For the same reason that a personal create a custom rom aosp pie... To add another possibility and keep the update process alive for the R5+.
Click to expand...
Click to collapse
That's the point - you need open source code (AOSP - Android Open Source Project). All these ROMs came because Xiaomi released kernel code for Vince, and some nice devs got their hands around it. MIUI is very much not open source. This device might get semi-stable Android Q or whatever comes after Pie, but don't expect anything fancy. In Xiaomi ecosystem, this device has probably EOL tag already. Enjoy what you already have, there is sooo much to choose from.
For quite a while now I've been making LineageOS 15.1 ROMs for the Axon 7.
I think Android 8.1 is still a very capable Android version and there's still support (without using different solutions) for Xposed and some other things. So far I'm still pretty happy with it, but as there are absolutely no fixes and so on in the source anymore and every month one has to hope that it still gets the latest security update, I wanted to ask you guys if you'd still like to see further updates on this ROM (hopefully with more security updates), or if there is any other ROM that is based on Android 9, as Android 10/LineageOS 17.1 isn't ready yet and probably will take a bit more time till it can be a Daily Driver.
The advantage of Android 9/LineageOS 16 is that the source is still being updated (and not only device specific) and that it gets Security Updates much earlier.
So, I guess a Poll would help here...
Due to overwhelming demand I will continue with the 15.1 builds for now. :silly:
I'd love to see a ROM that supports signature spoofing :good:
Anyways, thanks for the work you've done here
Which kernel version has the Nord 2 ? I am asking because i want know about the status of the GKI kernel implementation.
https://source.android.com/devices/architecture/kernel/generic-kernel-image
Hi @ALX3K,
As you can see here: https://github.com/OnePlusOSS/android_kernel_oneplus_mt6893/blob/oneplus/MT6893_R_11.0/Makefile#L2
It have 4.14.186 (Petit Gorille).
Greetings,
Wow how did you find it?
I thought because of merger with color os and in preperation to android 12 (oxygenos 12) there would use the newer kernel 4.19 or 5.4. Its even recommended from the android developers.
Maybe in oos12 we get a newer kernel would be interessting to know. I still cosider to buy a Nord 2 to play for some months with it. But now not sure. Example like this shows us why the merger of color os and oxygenos make sense. More developers and so on.
ALX3K said:
Wow how did you find it?
I thought because of merger with color os and in preperation to android 12 (oxygenos 12) there would use the newer kernel 4.19 or 5.4. Its even recommended from the android developers.
Maybe in oos12 we get a newer kernel would be interessting to know. I still cosider to buy a Nord 2 to play for some months with it. But now not sure. Example like this shows us why the merger of color os and oxygenos make sense. More developers and so on.
Click to expand...
Click to collapse
Because 1+ is GPL complain.
About the kernel version, I dont think the new change in 1+ with the merge with ColorOS in Android 12 will bring new kernel version, because that come from MTK BSP, and normally, QCOM and MTK only bump the minor version code, like 4.14.XXX only.