Related
Here's a bit of info you may want on this project for how we do things differently:
CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Important Links:
Download Nightlies - We have a very in depth review system, so these should be considered stable.
Download Weeklies - These are built once a week on Monday.
Download GApps
Download SuperSU installer
Kernel Source
Interactive and Rolling Changelog
Bug Tracker
Instructions:
In the same recovery session, flash the following:
Flash rom
Flash GApps
Flash Superuser zip
Reboot
Thank you for choosing codefireXperiment,
Yippee! First AOSP build with fully functional IR Blaster! I use the HTC implementation so any IR control app must use the HTC IR api. I tested with this app.
http://forum.xda-developers.com/showthread.php?t=2271113
Blaster mode and Learn mode are fully functional and stable. This is the first non-Nexus device I've done AOSP on so bear with me for a bit. The build is rock solid stable and I dare any build to try and out-benchmark me ;D
one more for good measure
This is truly a wonderful suprise!!
This is truly a wonderful suprise!!
Welcome bigrush!
This sounds cool! Thanks for the hard work. Im gonna give this a shot tomorrow.
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Are the APN for ATT in this ROM or do I have to put them in myself
Sent from my HTC One using Tapatalk 2
Does cfx have the same janky animation and sluggishness of other AOSP roms for the One when compared against a Sense or GE ROM?
If anyone could fix aosp/optimize for device specific hw on non-nexus devices its you.
Sieze said:
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Click to expand...
Click to collapse
I'm getting this same error too. Anybody know what's up yet? Probably something simple lol
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
bigrushdog said:
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
Click to expand...
Click to collapse
im using CW touch 6.0.3.3
running a backup atm but once finished il flash TWRP and see if it works.
Ok. So it fails to flash on cw then?
bigrushdog said:
Ok. So it fails to flash on cw then?
Click to expand...
Click to collapse
yup. it flashed with out a hitch on TWRP...
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
bigrushdog said:
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
Click to expand...
Click to collapse
well initial response to laying my finger and moving it on the screen. amazing. i didnt think id feel or tell much a difference in response. but holy S#!7 so smooth and stuff happens when its supposed to aka as soon as i touch the icon its open...
(ノ^_^)ノ also the boot animation is pretty frickin sweet.
also the benchmark has me drooling.
Quadrant Standard: 6749
also im really frickin liking this ROM
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
bigrushdog said:
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
Click to expand...
Click to collapse
well hey credits due where its earned right? but yea im still crappin my pants at how there is absolutely no lag at my finger tip.
Hands down the best android experience ive ever had. i can trully feel the power of my device in my hand in all its glory.
Grab that IR app and program your TV man. Dude dropped source for the app so maybe I'll do some IR toggles or something
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
mikexmayhem said:
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
Click to expand...
Click to collapse
Flashed with twrp. Still gave error but said successful. After reboot everything looks just fine. Great ROM!
Working:
RIL
Audio
Display
Bluetooth
Wifi
Sensors
Camera
Fingerprint
Broken:
VoLTE?
I will release when I want to.
o.o this one fixes the display error for internal storage space!
kgptzac said:
o.o this one fixes the display error for internal storage space!
Click to expand...
Click to collapse
you sure you were using an SD card (and the phone detects it)?
Jus sayin', I'm not gonna test it for now
P650SE said:
Yay! I have never been so excited in my entire life! BTW, how do you guys know the bug for internal storage space has been fixed, or is that just purely speculation? You kinda make it sound like there's already a download available for people who want to beta test.
Click to expand...
Click to collapse
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
SilentEYE said:
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
Click to expand...
Click to collapse
I suppose you're right. Neither Nougat or Oreo have brought significant changes, they have both been 'minor' updates with subtle changes to improve certain aspects of the OS. The last major update to Android was Lollipop, when the entire appearance was drastically overhauled from previous versions. I'm only excited because we just have to take what we're given, and any update to update the appearance and usability of Android after an entire year is a refreshing change! Even though Nougat was only a small update, it feels unbearable to me when switching back to Marshmallow without the new quick settings swipe-down; the one before the entire notification area appears. So even the small features can make a lot of difference to the overall experience! I'm still really looking forward to seeing the changes made in Oreo for myself when it comes to the Axon 7.
SilentEYE said:
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
Click to expand...
Click to collapse
I don't get why people say this, honestly. Just because you didn't get a visual overhaul like you got from KitKat to Lollipop doesn't mean there weren't significant changes. Visually the OS is already at a level where there's no need for a major change (it has been "ready" since Lollipop, imo; Marshmallow, Nougat, and Oreo have all had small visual tweaks but have stuck to the Material language), and most of the tweaks work "under the hood." Oreo will bring Project Treble, which may just be the most significant change in Android in the last few years. It also brings improvements on the behavior of notifications and background services or apps. It's an incremental update, yes. But it's by no means a small update.
@Gases
We talked about excitement.
I mentioned the problems with the new OS updates, which brings maybe more security but also many problems to custom ROMs. Furthermore there are more problems in the first months. I don't need visual tweaks.
Project treble is mainly positive for stock ROMs. We will see, in which way custom ROMs can profit of this new feature.
Background battery eating apps are no problem on custom ROMs based on LOS, if you use the internal features or external apps. But again. It's nice to have already implemented.
Finally I am always thankful for all kind of ROMs and kernels devs provide to the community. And I was always someone who donated to say 'thank you'
@SilentEYE Will this thread be used for development progress or is it just a tease thread?
ethanscooter said:
@SilentEYE Will this thread be used for development progress or is it just a tease thread?
Click to expand...
Click to collapse
I am not the dev but this is probably more a promotion thread. Final builds will surely be on developement thread.
Some devs are working on oreo right now.
Let's wait and be thankful for their work.
Here is a small update about the situation. Since the most common stuff is working im going to release this rom in 1-3 days. But don't expect to much. This rom is still WIP.
Working now:
RIL(Calls, Sms)
Audio
Most of the stuff (NFC etc.)
Broken:
Camera
Fingerprint
VoLTE (Will be probably broken until we get new blobs)
OrdenKrieger said:
Here is a small update about the situation. Since the most common stuff is working im going to release this rom in 1-3 days. But don't expect to much. This rom is still WIP.
Working now:
RIL(Calls, Sms)
Audio
Most of the stuff (NFC etc.)
Broken:
Camera
Fingerprint
VoLTE (Will be probably broken until we get new blobs)
Click to expand...
Click to collapse
Does cellular data work?
ethanscooter said:
Does cellular data work?
Click to expand...
Click to collapse
Yas.
What about the speakers? Do they have the same problem as before the fix was found?
Teet1 said:
What about the speakers? Do they have the same problem as before the fix was found?
Click to expand...
Click to collapse
Probably since they just got audio to work and the ROM is very experimental.
Really looking forward to testing this when the first release is posted on the forums. I'm just hoping the camera and fingerprint sensor will be relatively simple to fix. Thanks for everything you've done so far!
Teet1 said:
What about the speakers? Do they have the same problem as before the fix was found?
Click to expand...
Click to collapse
ethanscooter said:
Probably since they just got audio to work and the ROM is very experimental.
Click to expand...
Click to collapse
Audio is working normal. Like on cm14.1 both speakers are working just fine.
yes.. you are the man!
hopefully cam and fingerprint will fixed soon.
thanks ordenkrieger and all others
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
WesTD said:
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
Click to expand...
Click to collapse
That would be nice and all, but I think the devs want mostly everything to work for those that prefer to have a stable build and etc.
WesTD said:
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
Click to expand...
Click to collapse
I was just looking over in the Nexus 6 forms and to overcome the camera issue for them they had to upgrade from 7.1.2 - 8.0 and then restart the phone. So there is hope especially since the Nexus 6 is a 32-bit phone and I'm pretty sure 8.0 was supposed to be 64-bit.
Hey Guys,
I'm using my z5c with 32.4.a.0.160. There are lots of issues even with disabling the movie creator app.
I wonder when will the final update come. Do you guys think our devices get android 8.0 ?
LOL. Nope. I think the current update (7.1.1) will be the last update. Android 8.0 is confirmed *not coming* to the Z5 line.
mceyhan4 said:
Hey Guys,
I'm using my z5c with 32.4.a.0.160. There are lots of issues even with disabling the movie creator app.
I wonder when will the final update come. Do you guys think our devices get android 8.0 ?
Click to expand...
Click to collapse
I have updated to .160 too and I don't have any issues, actually it's even better than 7.0 for me. I flashed an ftf, factory reset it and then flashed all my mods and it's been all good until now.
Also, there is a small chance we might get official 8.0 but i wouldn't count on it. It will only happen if a lot of Z5 series owners make a statement and demand the update. However, I don't count on that, judging on how things are developing.. Be sure though, there will be custom ROMS on 8.0
trax7 said:
I have updated to .160 too and I don't have any issues, actually it's even better than 7.0 for me. I flashed an ftf, factory reset it and then flashed all my mods and it's been all good until now.
Also, there is a small chance we might get official 8.0 but i wouldn't count on it. It will only happen if a lot of Z5 series owners make a statement and demand the update. However, I don't count on that, judging on how things are developing.. Be sure though, there will be custom ROMS on 8.0
Click to expand...
Click to collapse
Custom roms unless proven otherwise will also probably mean loss of some camera features, loss of active noise cancelling and stereo(binaural) recordings with sony earphones,
no more radio FM RDS tuner, etc.
Sadly, Count me out !
joexda75 said:
Custom roms unless proven otherwise will also probably mean loss of some camera features, loss of active noise cancelling and stereo(binaural) recordings with sony earphones,
no more radio FM RDS tuner, etc.
Sadly, Count me out !
Click to expand...
Click to collapse
We are from the old days, Sony is more developer friendly now and they release the kernel source and drivers. There is no reason why they should not work after some patching... The camera could be the casualty here though, you might be right.
Glassrom is here
Join the telegram group today! https://t.me/joinchat/DKbLAED4w6Dk-qd26SmDbw
For those who don't know glassrom is a small project run by me. It focuses on where lineage left off. There is a stronger focus on speed and security while not having too many features
Current features: removed a lot of debugging from lineageOS and optimised more aggressively
Odexed for faster boot time
Ran through stronger selinux checks by building in user mode (security)
Microg support
Full substratum support with optimisations for lineage. No more weird looking statusbar
Upstreamed kernel to linux-3.10.50
Archidroid optimizations
Pixel UI
All features seem to work. Please report bugs
Donate links: https://ko-fi.com/florian
Coffee helps me stay awake to code
Donations are appreciated but are not a requirement. Donations help support me and my work
XDA:DevDB Information
Glassrom-harpia, ROM for the Moto G4 Play
Contributors
anupritaisno1
Source Code: https://github.com/GlassROM-devices
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: lineageOS
Version Information
Status: Beta
Created 2017-10-11
Last Updated 2017-10-11
Download here https://srv1.botstack.host:8001/moto/harpia/glassrom-harpia-alpha1-signed.zip
anupritaisno1 said:
Download here https://srv1.botstack.host:8001/moto/harpia/glassrom-harpia-alpha1-signed.zip
Click to expand...
Click to collapse
Thanks for bringing another rom for our device!
We really appreciate it.
NovaKenn said:
Thanks for bringing another rom for our device!
We really appreciate it.
Click to expand...
Click to collapse
Ditto on the thanks!
Two issues that I usually have with custom ROMs are:
1. Not using GLONASS in the satellite based position computation.
2. Broken USB audio streaming.
How does your Glassrom fair in these areas?
FWIW I've been using microG since it became available and its predecessor software before that. I am pretty sure that my GLONASS and USB issues are unrelated to that.
n76 said:
Ditto on the thanks!
Two issues that I usually have with custom ROMs are:
1. Not using GLONASS in the satellite based position computation.
2. Broken USB audio streaming.
How does your Glassrom fair in these areas?
FWIW I've been using microG since it became available and its predecessor software before that. I am pretty sure that my GLONASS and USB issues are unrelated to that.
Click to expand...
Click to collapse
I have been able to reproduce the first issue on every device I've ever had with a custom ROM running
I don't think anything other than the Google devices has that working and a fix could be only possible by a manufacturer
As of now this issue affects oneplus and many other devices too
Audio through USB; that's a complicated topic
I don't have anything that connects by USB to test this. So even if it was broken the fix wouldn't be possible
The second reason, audio through the usb uses digital gain instead of analog gain (which really sucks) so why even use it?
anupritaisno1 said:
I have been able to reproduce the first issue on every device I've ever had with a custom ROM running
I don't think anything other than the Google devices has that working and a fix could be only possible by a manufacturer
As of now this issue affects oneplus and many other devices too
Audio through USB; that's a complicated topic
I don't have anything that connects by USB to test this. So even if it was broken the fix wouldn't be possible
The second reason, audio through the usb uses digital gain instead of analog gain (which really sucks) so why even use it?
Click to expand...
Click to collapse
Thank you for the confirmation on the GLONASS situation.
With respect to USB audio streaming, it is the only way I have of listening to the music on my phone through my car's sound system. Not worth getting a newer car just to fix that.
Not a big deal about digital gain, just set the phone to full volume and use the car's analog volume control to reduce it to a reasonable level.
The site is down. I can't download the rom
Ctafolla2 said:
The site is down. I can't download the rom
Click to expand...
Click to collapse
It seems he deleted the ROM :/
Hi guys currently builds aren't booting so I've stopped builds
I'll let you know when a new build is up
NovaKenn said:
Thanks for bringing another rom for our device!
We really appreciate it.
Click to expand...
Click to collapse
True, our device also deserves this, not just flagship phones
Guys I solved the bootloop issue
I'm currently out somewhere but when I get time I'll do a build
Stoped?
Ok so guys I found a new maintainer
Here's what happened: so my moto suddenly stopped working. Like it won't detect my son card at all, won't connect to any WiFi networks, hard reboots randomly, etc
Currently I have exams and so I have no time to get my device in for service
I'm the meantime I found a person who's willing to maintain this until I am back. His username is infinite something... I forgot but basically a build is coming out very soon
Ok guys just give me about 4 hours I'll get a harpia build out
New build is up
Many people here claim they "upstream" their kernel and how secure it is
I've looked through all of those kernels
Here's the simple truth: no kernel for the Moto g4 play is secure or even up to date with security patches
In fact the entire msm8916 family for Moto devices has totally messed up security, at least when it comes to kernel
anupritaisno1 said:
Many people here claim they "upstream" their kernel and how secure it is
I've looked through all of those kernels
Here's the simple truth: no kernel for the Moto g4 play is secure or even up to date with security patches
In fact the entire msm8916 family for Moto devices has totally messed up security, at least when it comes to kernel
Click to expand...
Click to collapse
what about yours??
Where is the link?
@ki said:
what about yours??
Click to expand...
Click to collapse
Nope not secure
NovaKenn said:
Where is the link?
Click to expand...
Click to collapse
https://srv1.botstack.host:8001/moto/harpia/haruhirom-stable.zip
I see los 16 has gone live for a few devices. Oddly enough the station klte has gotten it. I installed it on one of my s5s last night and just updated to the latest nightly. It runs excellent. But I wonder why the 6p wasn't included in this first round. Or the pixel XL. I know there are pie roms for the 6p I see them here but I also see the unoffical lineage 16 for the 6p hasn't had any progress at all thread is dead in the water. I hope that doesn't mean the 6p is being left out.
If it is can anyone tell me which one of the pie roms on xda are the most stable. The 6p is my wife's phone and she doesn't know how to deal with random issues. Los 15.1 was great for this phone I was hopping 16 would be too.
Keep it on Oreo for now. I have tried couple of Pie ROMs and they run pretty slow
Pretty sure there'll be official LOS16 for our devices. So waiting....
We just have to wait for a dev to pick it up and get it to spec for them to host it as official. I hope someone picks up the mantle as my Nexus 6P is still going strong and LineageOS 15.1 has been the best things to happen to it since I changed the battery.
stay on los 15.1/stock
current pie roms have major issues
nardow said:
stay on los 15.1/stock
current pie roms have major issues
Click to expand...
Click to collapse
Might want to specify why you have major issues, because this is misleading.
I've been on AICP 9.0 for a month and i have not had many, if any issues.
Lawlrus said:
Might want to specify why you have major issues, because this is misleading.
I've been on AICP 9.0 for a month and i have not had many, if any issues.
Click to expand...
Click to collapse
On the ROMs I tested, which were all based on Statix sources, I had these issues:
Battery life is a lot worse than stock/aosp/los;
Overall performance is worse than stock/aosp/los;
Phone gets hotter than in stock/aosp/los;
Camera doesn't work properly (sometimes it does, sometimes it doesn't);
I'm about to install AICP Pie and give it a go.
nardow said:
On the ROMs I tested, which were all based on Statix sources, I had these issues:
Battery life is a lot worse than stock/aosp/los;
Overall performance is worse than stock/aosp/los;
Phone gets hotter than in stock/aosp/los;
Camera doesn't work properly (sometimes it does, sometimes it doesn't);
I'm about to install AICP Pie and give it a go.
Click to expand...
Click to collapse
I can't really comment on those builds because im too lazy to wipe my entire phone to go to fbe, but aicp has been working great for me. Sure the battery life is worse than 8.1 which is to be expected, but I haven't thought it was too bad.
The aicp guys have done a bunch of kernel work, sadly their newest build doesn't have the most up-to-date kernel, but I ran it for a few days, and the kernel still runs well. But I feel like the next build after the 3-5 one will be even better, since they remembered to push the kernel work back in.
The only ROM I've had huge battery issues with was aosip because for some reason the small portion of the kernel has its min freq set to 1200 instead of 380 or whatever the norm is, and setting the min lower doesn't stick well.
One way I got around this was using one of the savageone's custom kernels. He put out two test kernels that have both ran well for me based off of the common used fbe source staticx, and fde which wsd based off neo's source. Both kernels run about the same for me and work on either encryption type.
Lawlrus said:
I can't really comment on those builds because im too lazy to wipe my entire phone to go to fbe, but aicp has been working great for me. Sure the battery life is worse than 8.1 which is to be expected, but I haven't thought it was too bad.
The aicp guys have done a bunch of kernel work, sadly their newest build doesn't have the most up-to-date kernel, but I ran it for a few days, and the kernel still runs well. But I feel like the next build after the 3-5 one will be even better, since they remembered to push the kernel work back in.
The only ROM I've had huge battery issues with was aosip because for some reason the small portion of the kernel has its min freq set to 1200 instead of 380 or whatever the norm is, and setting the min lower doesn't stick well.
One way I got around this was using one of the savageone's custom kernels. He put out two test kernels that have both ran well for me based off of the common used fbe source staticx, and fde which wsd based off neo's source. Both kernels run about the same for me and work on either encryption type.
Click to expand...
Click to collapse
thanks for the info on the aicp kernel. i'll wait for the next build to flash it. good to hear aicp is fde
mojorisin7178 said:
I see los 16 has gone live for a few devices. Oddly enough the station klte has gotten it. I installed it on one of my s5s last night and just updated to the latest nightly. It runs excellent. But I wonder why the 6p wasn't included in this first round. Or the pixel XL. I know there are pie roms for the 6p I see them here but I also see the unoffical lineage 16 for the 6p hasn't had any progress at all thread is dead in the water. I hope that doesn't mean the 6p is being left out.
If it is can anyone tell me which one of the pie roms on xda are the most stable. The 6p is my wife's phone and she doesn't know how to deal with random issues. Los 15.1 was great for this phone I was hopping 16 would be too.
Click to expand...
Click to collapse
It's definitely work in progress. I see a topic "angler-p" on LineageOS gerrit. So people are working on it.
https://review.lineageos.org/q/topic:angler-p
Waiting patiently with baited breath for L16 to hit N6P. It's a match made in heaven! :fingers-crossed:
Anyone have any news on this?
copong said:
Anyone have any news on this?
Click to expand...
Click to collapse
The official lineage 16 as it seems will not happen most likely, development seems to be dead.
sage of six paths said:
The official lineage 16 as it seems will not happen most likely, development seems to be dead.
Click to expand...
Click to collapse
Not true. Check the unofficial los16 thread. AndyYan is working on a new build
Sent from my Nexus 6P using XDA-Developers Legacy app
serdel_elo said:
Not true. Check the unofficial los16 thread. AndyYan is working on a new build
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
True dat, he should just change the thread name to official if his build is the official one, so people don't question about official build anymore.
And the new build is out
Sent from my Nexus 6P using XDA-Developers Legacy app
sage of six paths said:
True dat, he should just change the thread name to official if his build is the official one, so people don't question about official build anymore.
Click to expand...
Click to collapse
He isn't doing official builds. So why would they be called official?
Lawlrus said:
He isn't doing official builds. So why would they be called official?
Click to expand...
Click to collapse
Well as far as i'm concerned is it official or not, i don't really care, as long as it's good. He did say in one of his first post when he gave his first build something along the lines of this is a peek of the feature set of los 16 as it is official / feature complete. So does it make it official or not i do not know.
sage of six paths said:
Well as far as i'm concerned is it official or not, i don't really care, as long as it's good. He did say in one of his first post when he gave his first build something along the lines of this is a peek of the feature set of los 16 as it is official / feature complete. So does it make it official or not i do not know.
Click to expand...
Click to collapse
The los devs are very strict with how they run official builds, originally he had added the lock screen deals that would make it non official, since they have merged it, that would cover that, but he also messes with the kernels fstab thus making it non eligible.
I don't know all of the specifics of being a maintainer for them, but there are guidelines for the hals and blobs and **** they have to use as well.
Lawlrus said:
The los devs are very strict with how they run official builds, originally he had added the lock screen deals that would make it non official, since they have merged it, that would cover that, but he also messes with the kernels fstab thus making it non eligible.
I don't know all of the specifics of being a maintainer for them, but there are guidelines for the hals and blobs and **** they have to use as well.
Click to expand...
Click to collapse
Well i don't care all that much about that, tell it to the guy above who asked is there official rom or not lol. What i do care about is winxuser making that aosp nfc issue gone, and i'm waiting for the news form that department
darkriff said:
Keep it on Oreo for now. I have tried couple of Pie ROMs and they run pretty slow
Click to expand...
Click to collapse
agreeeed. Pie roms don't work well on the Nexus 6P. Oreo was the last stable operating system for the Nexus 6P, so of course pie roms won't work as well, and i've tried a lot of them.
To name a few: Pixel Experience, DotOS 3.0, StatixOS, AOSiP Pie Beta,[ Pie - 9.0.0_r37] AOSP , Ressurection Remix, AICP all these i've tried they all have this lagginess about them and they're not as snappy as the roms on Oreo ot stock Oreo for that matter.
And the brightness sucks on pie too.
I'm currently running LineageOS 15.1 runs like a dream on my Nexus 6P.
Not to take anything away from the developers of pie roms though, they're all doing fantastic jobs to keep our Nexus 6P's alive