• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][addison] Android Open Source Project 9

Search This thread

Alberto97

Recognized Developer
Feb 6, 2012
976
7,828
23
Added to the previous shared folder.
I don't have Dropbox installed btw, but this seems to be just the same name for something different
Indeed, dropbox is a folder where crashes and various logs gets recorded for debugging puropses.
Anyway there's definitely a serious issue going on here. It seems like a kernel issue or some sort of hardware fault but I can say no more, every kernel log in dropbox is truncated. I can only see the end of the stack trace that makes them useless :(
If you can get a full kernel log I'd gladly look at it but I'm not sure this is a problem I'm able to fix. In sys/fs/pstore there are 2 files named "console" and "dmesg" if they're not outdated they might help as well.
If it is a kernel problem it seems a bit weird this is the only case of crashes and freezes going on for minutes though.
Have you ever tried to completely format data (I mean including internal storage) and restoring everything without using nandroid backups? If it's a mmc issue I think that could help at least for a while.
 

Fábio Ferreira

Senior Member
Nov 9, 2014
148
46
Indeed, dropbox is a folder where crashes and various logs gets recorded for debugging puropses.
Anyway there's definitely a serious issue going on here. It seems like a kernel issue or some sort of hardware fault but I can say no more, every kernel log in dropbox is truncated. I can only see the end of the stack trace that makes them useless :(
If you can get a full kernel log I'd gladly look at it but I'm not sure this is a problem I'm able to fix. In sys/fs/pstore there are 2 files named "console" and "dmesg" if they're not outdated they might help as well.
If it is a kernel problem it seems a bit weird this is the only case of crashes and freezes going on for minutes though.
Have you ever tried to completely format data (I mean including internal storage) and restoring everything without using nandroid backups? If it's a mmc issue I think that could help at least for a while.
Once again, uploaded to same folder.
How would I go about to get a full kernel log?
I've previously completely formatted it, not this time, but I can try again.
I normally don't use nandroid backups to restore, I let Google do all the work. Only thing I restore manually is Nova launcher backup.

Edit: one of the files seems to be truncated once again
 
Last edited:

Alberto97

Recognized Developer
Feb 6, 2012
976
7,828
23
Once again, uploaded to same folder.
How would I go about to get a full kernel log?
I've previously completely formatted it, not this time, but I can try again.
I normally don't use nandroid backups to restore, I let Google do all the work. Only thing I restore manually is Nova launcher backup.

Edit: one of the files seems to be truncated once again
Thanks, the log is truncated again in fact.
I think at this point the only way is through adb: connect the device when it acts normal, make sure adb recognize it, type adb logcat -b > log.txt kernel in the terminal, wait for it to go crazy again and let it stabilize again, Press Ctrl + C in the terminal and disconnect the device. I'm not sure if this is feasable though but on-device buffers are too small, also I believe the format thing won't help you then.
 
  • Like
Reactions: e.sxph

Fábio Ferreira

Senior Member
Nov 9, 2014
148
46
Thanks, the log is truncated again in fact.
I think at this point the only way is through adb: connect the device when it acts normal, make sure adb recognize it, type adb logcat -b > log.txt kernel in the terminal, wait for it to go crazy again and let it stabilize again, Press Ctrl + C in the terminal and disconnect the device. I'm not sure if this is feasable though but on-device buffers are too small, also I believe the format thing won't help you then.

Sure, I'll try.
My cable is kinda loose, so it may take a while to get it without disconnecting ?.
Thank you, I'll give you a heads up once I get it.
 
  • Like
Reactions: e.sxph

e.sxph

Member
Jan 10, 2018
12
15
1. I can't do anything about that
2. I see, it only seem to work in arm64 mode, possibly because I took a library built for an arm64 device. I can only disable video stabilization (or at least try) until we have one from Moto Z2 Play


Thanks, would you mind attaching/sending me a pm with your /data/system/dropbox folder and /data/tombstones folder?


Did you hit "yes" to this? (see attached screenshot)


Yes, I agree, it's not low enough when you're in a dark room, it will be lowered with the next build. I actually lost a setting that does exactly this when I took Pixel 2 brightness configuration and no, you can't tune it by a system property.



Yeah I hit the yes button, but hahaha problem solved I had to re flashed it again, and said no, thank you!!!
Everything is working great as I said before :D, I also enabled the API CAMERA 2 along with the Google camera and pictures look awesome! So happy with your ROM it is also my first ROM change hahaha nice work
 

aiseno

Member
Mar 14, 2013
47
9
I just flash this rom. And this is my first day with it as daily driver. For say, it's stable enough. Back button is still visible in the homescreen. And pixel launcher keep crashing and I can't uninstall it. Overall thank you so much Alberto, you're the man!

Sent from my XT1635-02 using Tapatalk
 

rdsj

Senior Member
Sep 10, 2017
86
29
I just flash this rom. And this is my first day with it as daily driver. For say, it's stable enough. Back button is still visible in the homescreen. And pixel launcher keep crashing and I can't uninstall it. Overall thank you so much Alberto, you're the man!

To skip pixel launcher on your gapps install make a gapps-config.txt file in the same folder as your gapps zip and simply type:
PixelLauncher

I would like to say to Alberto that the 1080p and 720p video is broken on moto camera again on a fresh install of the Dec 22 build.
 

aiseno

Member
Mar 14, 2013
47
9
To skip pixel launcher on your gapps install make a gapps-config.txt file in the same folder as your gapps zip and simply type:
PixelLauncher

I would like to say to Alberto that the 1080p and 720p video is broken on moto camera again on a fresh install of the Dec 22 build.
If I reflash gapps did I lose data?

Sent from my XT1635-02 using Tapatalk
 

AgEnT_aVi_99

Senior Member
May 22, 2016
84
25
A question for to Any Indian/Jio user, is anyone facing 4G VoLTE issue after flashing the 22nd build? I can't seem to get any incoming and outgoing VoLTE calls from the Jio sim (in 1st sim slot) although data is working normally. Tried re-flashing and restarting but the issue is still there!!
 

Alberto97

Recognized Developer
Feb 6, 2012
976
7,828
23
I might have found the root cause of lags and slowdowns on 64bit builds (thanks to @fablebreton), another one is up in the AFH folder, let me know about it please, it looks already better here but I don't count alone.
Actually the last 32bit build should have been affected as well since this is caused by a kernel side boot time optimization that has been ported to arm with the latest kernel rebase. Basically this optimization had to be disabled at runtime but it did not.
Included in the latest build there also is a fix for the bootanimation crash.
Sorry about the 32/64bit builds confusion of the last days but I don't really have another way to test this :(
 
Last edited:

tomy1802

Senior Member
Sep 17, 2016
140
56
Buenos Aires
I might have found the root cause of lags and slowdowns on 64bit builds (thanks to @fablebreton), another one is up in the AFH folder, let me know about it please, it looks already better here but I don't count alone.
Actually the last 32bit build should have been affected as well since this is caused by a kernel side boot time optimization that has been ported to arm with the latest kernel rebase. Basically this optimization had to be disabled at runtime but it did not.
Included in the latest build there also is a fix for the bootanimation crash.
Sorry about the 32/64bit builds confusion of the last days but I don't really have another way to test this :(

So the new build you uploaded is 64 bits?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 91
    android-p-clear-bg-with-shadow-%25401ximage1.png

    Code:
    /*
     * 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.
     */
    Moto Mods are not supported, fork my sources and add the support yourself if this is so important to 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

    Installation
    1. Place ROM & Gapps in your virtual SD
    2. Reboot in Bootloader Mode
    3. Go to "Recovery" (Vol +/Vol -) and confirm (power)
    4. Wipe system if you're coming from a different Android version
    5. Wipe Data (only if you come from a different ROM/Android version, not required while updating)
    6. Wipe Dalvik cache
    7. Install the ROM zip
    8. DO NOT REBOOT
    9. Install the Gapps zip (optional)
    10. 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-06
    38
    Changelog

    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

    28/12/2018
    • Lags and slowdowns have been fixed
    • Bootanimation does not crash anymore

    22/12/2018
    • exFAT support for sdcards
    • Rebased kernel on the top of Moto pie sources
    • Now using stable f2fs kernel sources instead of Moto's fork

    09/12/2018
    • IMS related stability issues should have been fixed now

    07/12/2018
    • December security patches
    • Low speaker volume is now fixed
    • Proprietary stacks have been upgraded to pie
    • BFQ is the default IO scheduler
    • Enforcing selinux
    • Flip to Mute: the phone now vibrates when you mute/unmute it, just like Google's Flip to shhh

    10/11/2018
    • November security patches
    • IMS is possibly working now
    • 4K video recording is now available on AOSP an third party cameras
    • 1080p and 720p video recording on Moto Camera is now fixed
    • Camera2 APIs are now working
    • Prima wlan update to LA.UM.7.6.r1-03400-89xx.0 CAF release

    03/10/2018
    • October security patches
    • Reboot to recovery is now working
    • Wifi - BT crash fix from the experimental build included
    • Moto kernel patches from 28.85-13 release included
    • Blobs updated to OPNS27.76-12-22-9 moto release
    • Added some padding between mobile signal groups (before - after)

    15/09/2018
    • September security patches
    • Flashlight now works in DND mode too
    • Rebased kernel (again) on the top of qcom pie sources

    26/08/2018
    • Auto brightness fixed
    • Encryption support implemented
    • Removed wifi display support (reason here)
    • Added Google Sans font
    • MAC address is properly set now
    • Added missing F2FS moto changes in kernel rebase

    15/08/2018
    • Initial Release
    30
    New 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 evening :)
    28
    June 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.
    23
    October 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.