[ROM][addison] Android Open Source Project 9
- Thread starter Alberto97
- Start date
someone who has the Chinese variant (xt1635-03) managed to activate NFC?
when I try to activate, the shiwt turns blue, but it does not activate, if it opens again, it is disabled.
When closing and opening again, the option is gone
when I try to activate, the shiwt turns blue, but it does not activate, if it opens again, it is disabled.
When closing and opening again, the option is gone
Last edited:
someone who has the Chinese variant (xt1635-03) managed to activate NFC?
when I try to activate, the shiwt turns blue, but it does not activate, if it opens again, it is disabled.
When closing and opening again, the option is gone
Working fine for me, you might want to revert to stock Motorola RETCN Oreo ROM before installing TWRP and this AOSP ROM
Last edited:
MOD EDIT: ENGLISH TRANSLATION ADDED AS USER VIOLATED FORUM RULES #4
Buenas tardes. I just wanted to thank you for this tutorial.
In less than 10 minutes I managed to install Android 9.0 on my Moto Z Play from 2017.
I have it for a long time and I started to have problems with the consumption of the battery.
I went from 8.0 to 6.0 because they say it is a global Oreo glitch on this device and it greatly improved performance.
We will see how it works with 9.0 and the minimum GAAPS installed.
Thank you in advance and greetings from CABA Bs As Argentina.
ORIGINAL POST PRESERVED BELOW
Buenas tardes. Simplemente quería agradecerte por este tutorial.
En menos de 10 minutos logré instalar Android 9.0 en mi Moto Z Play del 2017.
Lo tengo hace mucho y comencé a tener problemas con el consumo de la bateria.
Pasé de 8.0 a 6.0 porque dicen que es una falla global de Oreo en este dispositivo y mejoró mucho el rendimiento.
Veremos como funciona con 9.0 y las mínimas GAAPS instaladas.
Desde ya muchas gracias y saludos desde CABA Bs As Argentina.
Buenas tardes. I just wanted to thank you for this tutorial.
In less than 10 minutes I managed to install Android 9.0 on my Moto Z Play from 2017.
I have it for a long time and I started to have problems with the consumption of the battery.
I went from 8.0 to 6.0 because they say it is a global Oreo glitch on this device and it greatly improved performance.
We will see how it works with 9.0 and the minimum GAAPS installed.
Thank you in advance and greetings from CABA Bs As Argentina.
ORIGINAL POST PRESERVED BELOW
Buenas tardes. Simplemente quería agradecerte por este tutorial.
En menos de 10 minutos logré instalar Android 9.0 en mi Moto Z Play del 2017.
Lo tengo hace mucho y comencé a tener problemas con el consumo de la bateria.
Pasé de 8.0 a 6.0 porque dicen que es una falla global de Oreo en este dispositivo y mejoró mucho el rendimiento.
Veremos como funciona con 9.0 y las mínimas GAAPS instaladas.
Desde ya muchas gracias y saludos desde CABA Bs As Argentina.
Last edited by a moderator:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
91
Moto Mods are not supported, fork my sources and add the support yourself if this is so important to youCode:/* * 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 this ROM * 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. */
AOSP is Android as Google release without other modifications, similar to Pixel/Nexus stock rom but without gapps.
Features such as Chop Chop, Double Twist, Fingerprint sleep and Ambient display gestures are kept.
Google does not release an AOSP Browser anymore since Marshmallow, thus there isn't a default browser. If I find the time I might port and revamp it in the future.
Working
- Audio playback
- RIL (Calls, SMS, Data)
- Wifi
- Bluetooth
- Hotspot
- Video Playback
- LED Notifications
- Camera
- GPS
- NFC
- Biometric sensor
- Night Mode
Not Working/Bugs
- -
Camera2 APIs disclaimer
If you decide to enable Camera2 APIs, be aware that in certain conditions photos and videos quality might be extremely low.
This happens because Motorola on our device officially supports only the old camera apis.
For this reason old camera apis are currently enabled by default.
Preconditions
- Unlocked bootloader
- TWRP (3.2.1 or newer)
- Oreo modem and bootloader
Installation
- Place ROM & Gapps in your virtual SD
- Reboot in Bootloader Mode
- Go to "Recovery" (Vol +/Vol -) and confirm (power)
- Wipe system if you're coming from a different Android version
- Wipe Data (only if you come from a different ROM/Android version, not required while updating)
- Wipe Dalvik cache
- Install the ROM zip
- DO NOT REBOOT
- Install the Gapps zip (optional)
- Reboot
Downloads
arm builds
arm64 builds(No more supported)
Sources
Device Tree
Kernel
Sensor HAL
XDA:DevDB Information
Android Open source Project 9, ROM for the Moto Z Play
Contributors
Alberto97
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: No Longer Updated
Created 2018-08-15
Last Updated 2020-01-0638Changelog
09/08/2019
- August security patches
- Enabled IMS carrier settings in Brazil as per latest stock oreo (you still need to insert yourself the IMS apn)
- Android for Work Profiles should work properly now
02/07/2019
- July security patches
09/06/2019
- June (and May) security patches
- Vibration intensity is now adjustable on three levels from accessibility settings
- Occasional crashes at boot/bootloops caused by the sensor hal are now fixed
- Exposed through sysfs some SD infos (SD status register + speed class + uhs speed grade) and internal storage health
05/04/2019
- April security patches
- Fixed adopted storage
09/03/2019
- March security patches
- Device now goes in deep sleep mode when using Always on Display
09/02/2019
- February security patches
- Device correctly boots when setting pin/password/pattern *at boot* now
19/01/2019
- January security patches
- Device specific gestures entry points in Settings have been reworked to be consistent with the rest of UI
- LZ4 kernel-side improvements from Pixel 2 kernel
- Back to Moto's F2FS kernel sources
- Video stablization is now working
---- From now on all builds will be 32bit, wipe data is required if you're updating on the top of a 2018 build ----
Old ARM64 builds changelog
30New build with encryption support and fixed auto brightness released.
If we're lucky enough the issue where connecting a smartwatch breaks wifi was related to a wrong wlan MAC address (that has been fixed) otherwise I need at least a kernel log and a logcat to see what's going on (I suspect that could be a kernel issue).
I'm also afraid I have bad news for miracast/wifi display users. It seems that Google removed its "media side" support in P (commit here). For some reason UI is still there and the same seems to be for connectivity related stuff. I don't know if this is a mistake (but it does not seem so) or if they're just going to reimplement it later (I hope so). The only thing I know is that it can't work in the current state, for this reason I disabled the feature so that nobody is going to face this horrible crash.
Now, this this has already been reported but I want to clarify it. For some absurd reason enabling "do not disturb" breaks flashlight. In particular as soon as you enable this mode, chop chop gesture immediatedly breaks while the flashlight tile might take a while (but you can verify this by enabling "do not disturb" and rebooting, in this case flashlight tile is always broken). I did not have time to check what's happening yet, but it does not seem to be a device specific issue or if it is, it is affecting many other devices too. All this just to say: be careful!
There are less relevant changes too, check them out in the second post and good evening28June security patches are out. I've been busy on other side projects and of course I also got sick but there's more.
In the last months the battery of my device has started swelling and now it looks quite bad. Sending the phone to a service center is not an option for me.
I'd just change the battery myself but I don't think it's a good idea heating up a swollen battery especially without proper tools so I'm just stopping the development on this device.
However I see there still are many people (relatively speaking, considering the popularity of this device) that rely on AOSP. For this reason I'll keep releasing monthly security patches, at least until Q is out.
Though because of this situation I don't know if I'll be able to test them/all of them.
Talking about the latest relase, I wasn't able to fix or workaround in any way the issue with camera that is throwing many devices into a bootloop (the fix in the changelog is about another issue which is present in the latest oreo stock build as well but it rarerly causes a bootloop) but at least that's "fixable" by forcing a reboot by holding the power button.
AOSP vibration intensity control on three levels as it works on Pixel devices has been enabled. It might not be ideal for those who looks for an accurate customization but it's something.
Also some informations about SD and internal storage health have been exposed by sysfs. Most of them are not direcly human readable but some apps might want to show them (it's not like I'm working on one).
That's all, mainly bad news but that's all.23October security patches are out along with other fixes and upstram updates. Among the other things moto improved the volume up/assistant triggering detection on headsets (there were cases where pressing vol+ triggered the assistant instead of raising the volume). They also provided 64 bit configuration for all the devices that came with 3.18 kernel. This because the Motorola one got switched to 64bit mode in the last minute. I don't expect to see official 64 bit builds for older devices, it's not in their style and that would mean testing and fixing everything again but at least we have an official configuration, tested on another SD625 sure, still better than nothing (mine wasn't so that much different though ).
I'll try to include the VoLTE fix later but, again I can't test it , I can't guarantee it will work on the first shot.
For any other issue, please include logs, I can do nothing otherwise.
