Related
Hi,
As OnePlus is not updating anymore Onyx since last november I'm considering installing a custom rom.
For now my choices are on AOKP and Lineage OS.
I want something light but secure.
I don't need billions of features.
Does anyone has experienced both roms on Onyx and could give some feedbacks ?
Thanks a lot !
Regards,
Lineage is simply no go.
I think GZR are most stable ones.
There is a minimal feature build of jdc available on afh you can try that, imo it is the best nougat based rom for onyx at the moment(may change once pa hits the market).
Try Tesla from the thread here if you are looking fir stable 7.1.2 ROM
W!ld said:
Lineage is simply no go.
I think GZR are most stable ones.
There is a minimal feature build of jdc available on afh you can try that, imo it is the best nougat based rom for onyx at the moment(may change once pa hits the market).
Click to expand...
Click to collapse
I will have a look at GZR.
I never heard about it before.
What's wrong about LineageOS ?
Big Update The King SultanXda Might support onyx.
So whenever his N based rom is out it will be the most stable and complete rom for onyx(he is the best dev out there).
I use XenonHD: fast and stable, ok for daily use, no bugs, tristate ok, updated near monthly. About 4h of SOT.
I red that there's network issues with most of N roms for Onyx.
Is it true and anyone has experienced it with GZR?
Sultan is great but...
W!ld said:
Big Update The King SultanXda Might support onyx.
So whenever his N based rom is out it will be the most stable and complete rom for onyx(he is the best dev out there).
Click to expand...
Click to collapse
I'd rather get Tutorials from Sultan than wait for him to develop OPX ROM - I appreciate he is just trying to survive like everyone else.
He's great but I have to be able to understand & do for myself. I can't afford ISP but would pay SultanXda to put out Tutorial Videos using OnePlus X as an example device, so I could learn from him.
Can't wait for anyone, its too dependent better to learn for myself & teach others so they can be independent too.
I went back to OOS 3.1.4 there are too many apps I don't use on it but I like OOS Style just wish I could remove unwanted google apps get security updates on it at least
Fstop said:
I'd rather get Tutorials from Sultan than wait for him to develop OPX ROM - I appreciate he is just trying to survive like everyone else.
He's great but I have to be able to understand & do for myself. I can't afford ISP but would pay SultanXda to put out Tutorial Videos using OnePlus X as an example device, so I could learn from him.
Can't wait for anyone, its too dependent better to learn for myself & teach others so they can be independent too.
I went back to OOS 3.1.4 there are too many apps I don't use on it but I like OOS Style just wish I could remove unwanted google apps get security updates on it at least
Click to expand...
Click to collapse
Sultan's overbooked...
Someone is going to cook a Sultans's lost within a few weeks.
You will have a basis if you want to work on it...
Hoops, here in fact !!
Anyone has tried aokp nougat nightlies? Are they stable enough to be used as daily driver?
Hi friends and dear developers..
I've been in this community since many years. I've been using Sony phones and then xiaomi phones.
> I've always seen that there are most kernels developed only for Cyanogen(now Lineage) based ROMs.
I accept that Lineage based ROMS are much much better in terms of performance and fluidity, and I love many roms out there.
But I always see xiaomi users get back to MIUI one day or another, since it has it own advantages, especially looks.
So my real query is, why don't we concentrate atleast a little on kernels for MIUI roms as well??
So friends, kindly share your views and suggestions, so that developers might take a look into this.
Love you all for your valuable time and knowledge. :good::highfive:
ashok weird said:
Hi friends and dear developers..
I've been in this community since many years. I've been using Sony phones and then xiaomi phones.
> I've always seen that there are most kernels developed only for Cyanogen(now Lineage) based ROMs.
I accept that Lineage based ROMS are much much better in terms of performance and fluidity, and I love many roms out there.
But I always see xiaomi users get back to MIUI one day or another, since it has it own advantages, especially looks.
So my real query is, why don't we concentrate atleast a little on kernels for MIUI roms as well??
So friends, kindly share your views and suggestions, so that developers might take a look into this.
Love you all for your valuable time and knowledge. :good::highfive:
Click to expand...
Click to collapse
MIUI is outdated most of us using XDA only use custom ROMs,take me for an example I used MIUI in my redmi 3s only initial 3~5 months after that when I heard xioami won't upgrade redmi 3s to nougat ,I switched to custom ROM since then I never gone back to MIUI ,heck I even forgot I'm using xiaomi device.
There is bunch of up-to-date Oreo custom ROMs available for our device,as for MIUI it only stuck in Android marshmallow with April 2017 security patch which is one year old.so do u really think developers should care about MIUI?if normal users don't want to use MIUI ,then why should developers waste their time to create kernel,which nobody gonna use? Besides kernel development for our device is generally not that great compared to santoni and other redmi devices,so yeah this my opinion on this matter,if in future xiaomi decided to upgrade all devices to up-to-date Android(which I doubt),I'm sure developers will create more kernels for MIUI,even then custom ROMs will always dominate.
As for themes,since you're not new here,you at least heard about substratum theme engine/OMS give it a try,it's better than MIUI theming.
If you really want to stick to MIUI (official or custom Marshmallow based) you can use PerXepted kernel by Nichcream : https://forum.xda-developers.com/xiaomi-redmi-3s/development/kernel-perxepted-16-aug-t3657329
It is excellent.
SMR96 said:
MIUI is outdated most of us using XDA only use custom ROMs,take me for an example I used MIUI in my redmi 3s only initial 3~5 months after that when I heard xioami won't upgrade redmi 3s to nougat ,I switched to custom ROM since then I never gone back to MIUI ,heck I even forgot I'm using xiaomi device.
There is bunch of up-to-date Oreo custom ROMs available for our device,as for MIUI it only stuck in Android marshmallow with April 2017 security patch which is one year old.so do u really think developers should care about MIUI?if normal users don't want to use MIUI ,then why should developers waste their time to create kernel,which nobody gonna use? Besides kernel development for our device is generally not that great compared to santoni and other redmi devices,so yeah this my opinion on this matter,if in future xiaomi decided to upgrade all devices to up-to-date Android(which I doubt),I'm sure developers will create more kernels for MIUI,even then custom ROMs will always dominate.
As for themes,since you're not new here,you at least heard about substratum theme engine/OMS give it a try,it's better than MIUI theming.
Click to expand...
Click to collapse
Thank you for your detailed explanation. And i totally agree with you buddy.. Except the fact that there are end users who still love MIUI (even though android version isn't updated and yes it sucks very much)..
And yes I have used substratum theme engine, its really great though
Manzing said:
If you really want to stick to MIUI (official or custom Marshmallow based) you can use PerXepted kernel by Nichcream : https://forum.xda-developers.com/xiaomi-redmi-3s/development/kernel-perxepted-16-aug-t3657329
It is excellent.
Click to expand...
Click to collapse
Yeah bro I have used it already.. It haven't been updated since long... And I hope it won't be updated anymore....
Because like SMR96 bro said, miui isn't updated (in terms of android version or security patch). Hence developers won't take much interest in updating kernel for an outdated ROM
ashok weird said:
Yeah bro I have used it already.. It haven't been updated since long... And I hope it won't be updated anymore....
Because like SMR96 bro said, miui isn't updated (in terms of android version or security patch). Hence developers won't take much interest in updating kernel for an outdated ROM
Click to expand...
Click to collapse
It has been updated in january 2018, this is not so bad. The real problem is due to MIUI security patch level, april 2017 is not acceptable.
But sadly, nobody tried to add new security patch to MIUI.
Since everyone kept asking and I myself wanted it, I decided to start this project. The main reason why I didn't do it earlier was because I needed Asus to release the Oreo build already so I could get the required files. So for now I leave you with this, hope I made your day a bit better and have a great day!
Note: the build you see here is just so I could get the compiler working.
Sweet!! Looking forward to seeing the progress on this.
Nice. Do you think the build will have camera quality issues though?
kekley said:
Nice. Do you think the build will have camera quality issues though?
Click to expand...
Click to collapse
We'll see once I get a debuggable build running. I hope it's smooth sailing, but I can't guarantee anything.
First build?
Is this the first build?
If you want tester I am always available.
Naman Vashishth said:
Is this the first build?
If you want tester I am always available.
Click to expand...
Click to collapse
Nice to hear that you want to test the rom, but unfortunately I still don't have a flashable build. I try to work on it whenever I can to get one out as soon as possible. Do keep in mind I do this in my free time when I'm not busy with school. When I do get a debuggable build out, I'll let this forum know so I can get some testers to test it out (other than myself).
+)KEV1N(+ you are a savior , please help us get rid this sick twisted ASUS stock firmware , it's a mess in every aspect , heat, poor battery life, muffled sound via headphones, enormous amount of services running in the background (loses 20% overnight), complete failure in both firmware and kernel wise cause they massively overclocked that S625 , i can live with a rom without the main camera app , OpenCam will do just fine , just take care of that power consumption please cause on paper it should deliver 12-16h SOT , it's 5000mah with s625 and AMOLED screen for god sake !
Thank you in advance for your effort.
Kevin,
Thanks so much for taking on this project!
Not many have the skills or time to do a project like this. I think I can speak for all Z3Z owners when I say that your work will not go unappreciated.
I am simply observing the work of the gentlemen, let us continue in this to create a lineage.
rinampa said:
I am simply observing the work of the gentlemen, let us continue in this to create a lineage.
Click to expand...
Click to collapse
It is a slow process, especially since this is my daily driver. I just came back from holidays back home and now I'll continue to work on it whenever I get the chance. I'll get a working test build running eventually. Can't guarantee when, just know that as a new developer it'll take time to fix things and put them in place since porting is also not easiest of projects.
I visit this thread multiple times a day, it gives me hope)
Thank u Sir
I'm grateful that you are working on this project.
Take your time & carry on.
I want do downgrade form Oreo to MM, Q: will i need to extract recovery.img form MM zip and flash it separately or the stock Oreo recovery will work with all raw asus builds ?
Build# : ww-11.41.87.2 this is the latest MM update before Nougat update, i'm a little confused cause every build has it's own method so any advice for the safest fastest way to :
1-Downgrade to MM from Oreo
2-Flash Magisk to root and install greenify , viper4android cause i'm done with this Oreo.
3-Do i need to unlock the bootloader ?
4-Do i need twrp to flash migisk?
5-Does twrp work with all versions of android ?
3-What are the cons of this procedure if a custom ROM would fall from heaven and i would want to flash it after i flash MM?
sam.fisher190 said:
I want do downgrade form Oreo to MM, Q: will i need to extract recovery.img form MM zip and flash it separately or the stock Oreo recovery will work with all raw asus builds ?
Build# : ww-11.41.87.2 this is the latest MM update before Nougat update, i'm a little confused cause every build has it's own method so any advice for the safest fastest way to :
1-Downgrade to MM from Oreo
2-Flash Magisk to root and install greenify , viper4android cause i'm done with this Oreo.
3-Do i need to unlock the bootloader ?
4-Do i need twrp to flash migisk?
5-Does twrp work with all versions of android ?
3-What are the cons of this procedure if a custom ROM would fall from heaven and i would want to flash it after i flash MM?
Click to expand...
Click to collapse
Guess what !!!
https://forum.xda-developers.com/ze...nbrick-flash-stock-mm-asus-zenfone-3-t3840702
Its more than 100days now since this "little something" post.
Is there any progress dear KEVIN?
or shall I switch to some other device?
Aditya Tiple said:
Its more than 100days now since this "little something" post.
Is there any progress dear KEVIN?
or shall I switch to some other device?
Click to expand...
Click to collapse
I started at the end of my school year a couple of months back. I had a month-long hiatus in July due to me going back to my family back home. I came back in August and am working on it as a side project. Naman's helping me with this right now and so far we got till the boot animation. And then you have those times when we fix something and you go one step back. It's a slow process since the two of us aren't like 24/7 busy on the project. I usually work on it during weekends, but lately I've been needing my phone more and more since I'm very very busy with other priorities. Again, this is a side project I'm doing because I like coding and I like learning new things. So, I can't say for certainty when we can get a release out, but I work eagerly every time hoping it gets past the boot animation or even gets there if I fix something.
I hope this clears out any misconceptions you may have of me and this project. Have a further great day sir
It's nice to hear from you.
That's d very reason I visit this thread.
Keep ur good work going.
Keep us updating.
All d best
Hello mate, you know the whole world is waiting for this build from xda to 4pda to every other android community so what's the news my friend? can you post the bugs maybe we can help with some of them and learn about the Lineage route you chose.
The midterm examination is about to start and you'll be too busy with the study!
My full appreciation to your work.
Instead of quenching our thirst, op made it worse... Shame no developer decided to code for this device.
Mrkblo said:
Instead of quenching our thirst, op made it worse... Shame no developer decided to code for this device.
Click to expand...
Click to collapse
There is a developer who is willing to port lineage if people will crowdfund the purchase of a Z3Z for them.
https://forum.xda-developers.com/zenfone-3-zoom/help/search-developer-custom-rom-t3793680/page2
Will we get android pie roms?
i am really interested in the pixel experience.
I was a mtk user and a porter ...can i port other pie rom like xiaomi note 4's with same kernel version ?
i am new so treat me like a noob:good:
mona356 said:
Will we get android pie roms?
i am really interested in the pixel experience.
I was a mtk user and a porter ...can i port other pie rom like xiaomi note 4's with same kernel version ?
i am new so treat me like a noob:good:
Click to expand...
Click to collapse
I'm very sad to see R5+ development is currently dead. I was hoping someone would build a Pixel Experience or any AOSP based ROM for our device but even the oreo roms are dead or finalized already. So i don't think people have anymore interest in R5+..
bdogan1912 said:
I'm very sad to see R5+ development is currently dead. I was hoping someone would build a Pixel Experience or any AOSP based ROM for our device but even the oreo roms are dead or finalized already. So i don't think people have anymore interest in R5+..
Click to expand...
Click to collapse
The real problem is lack of updated Oreo kernel sources (how much less Pie). This means, for example, that certain display panels (eg, ebbg) cannot be supported by custom ROMs (you might have to go back to Nougat kernels for that).
Why not write to Xiaomi to release up-to-date Oreo kernel sources for vince in the first instance? If enough people make a fuss, perhaps something will happen ...
DarthJabba9 said:
The real problem is lack of updated Oreo kernel sources (how much less Pie). This means, for example, that certain display panels (eg, ebbg) cannot be supported by custom ROMs (you might have to go back to Nougat kernels for that).
Why not write to Xiaomi to release up-to-date Oreo kernel sources for vince in the first instance? If enough people make a fuss, perhaps something will happen ...
Click to expand...
Click to collapse
Xiaomi however isn't listening their customers. A big example is ARB system which absolutely destroys devices. So i guess we are gonna stay dead until something shows up..
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