• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][osprey] The Android Open Source Project 8.1

Search This thread

Selmak

Senior Member
Jul 7, 2010
267
65
So out of curiosity is there a release schedule for this rom, or just as the dev has time? I'm really liking it so far. It runs very smooth. So I'm very much looking forward to seeing how things progress, and really there isn't much to work out. I'm having the same issues as everyone else. GPS status won't lock. I haven't tried to use Google maps for navigation yet. I haven't had any luck with video with any camera I've tried, including footej. Here is one you may not have come across. I have any Anymote. It's an rf blaster that sits on my coffee table, and connects to the universal remote control Anymote app on my phone. Well the app can't see the Anymote device. I'll keep trying to reset it, and hopefully I can get it to work. It's possible it isn't related to the rom at all, but I think it is as it worked perfectly with my last rom. On the plus side a lot of things work so much better on this rom than my old one, and it runs so much smoother.
 

KrisM22

Senior Member
Sep 12, 2010
3,963
1,321
many ways to guide, many ways to heal
So out of curiosity is there a release schedule for this rom, or just as the dev has time? I'm really liking it so far. It runs very smooth. So I'm very much looking forward to seeing how things progress, and really there isn't much to work out. I'm having the same issues as everyone else. GPS status won't lock. I haven't tried to use Google maps for navigation yet. I haven't had any luck with video with any camera I've tried, including footej. Here is one you may not have come across. I have any Anymote. It's an rf blaster that sits on my coffee table, and connects to the universal remote control Anymote app on my phone. Well the app can't see the Anymote device. I'll keep trying to reset it, and hopefully I can get it to work. It's possible it isn't related to the rom at all, but I think it is as it worked perfectly with my last rom. On the plus side a lot of things work so much better on this rom than my old one, and it runs so much smoother.

No schedule! When the dev has time. Yes, it is a nice ROM. I use it. Footej works., Also cameraFi2,
GPS lock works - just gotta play with it. True on all 8.x at this point .
Google Maps works fine for most folks with high accuracy anyway.
Don't use live wallpaper - the Osprey doesn't have enough power - gets laggy.
 
Last edited:

Selmak

Senior Member
Jul 7, 2010
267
65
One more thing I thought of that would be really nice. I'd love to see the charging light be put to use. I got kind of spoiled with the old Cyanogenmod rom I ran for the last year. I got used to the light being on when charging. I'd love to see that on by default. I don't even care if I can't turn it off. No need to add anything in the menu for it. Just turn the thing on. :)
 

KrisM22

Senior Member
Sep 12, 2010
3,963
1,321
many ways to guide, many ways to heal
One more thing I thought of that would be really nice. I'd love to see the charging light be put to use. I got kind of spoiled with the old Cyanogenmod rom I ran for the last year. I got used to the light being on when charging. I'd love to see that on by default. I don't even care if I can't turn it off. No need to add anything in the menu for it. Just turn the thing on. :)

That's a CyanogenMod/LineageOS thing - don't know if that will be coming along.
 

Extralars

Senior Member
Nov 8, 2016
109
48
Moto G4 Plus
One more thing I thought of that would be really nice. I'd love to see the charging light be put to use. I got kind of spoiled with the old Cyanogenmod rom I ran for the last year. I got used to the light being on when charging. I'd love to see that on by default. I don't even care if I can't turn it off. No need to add anything in the menu for it. Just turn the thing on. :)
I don't like it at all, som I'm happy it is turned off. :)

---------- Post added at 15:45 ---------- Previous post was at 15:41 ----------

I have a minor issue: I paired my Moto G with my iPhone 5s (ME435KS/A), for file transfer, and so far, so good. But on my iPhone the status continued to be unconnected. So I couldn't send files from my Moto G to my iPhone. Perhaps the problem lies in iOS 11.2.1 (15C153), but anyway, I thought I should mention it.
 

KrisM22

Senior Member
Sep 12, 2010
3,963
1,321
many ways to guide, many ways to heal
I have a minor issue: I paired my Moto G with my iPhone 5s (ME435KS/A), for file transfer, and so far, so good. But on my iPhone the status continued to be unconnected. So I couldn't send files from my Moto G to my iPhone. Perhaps the problem lies in iOS 11.2.1 (15C153), but anyway, I thought I should mention it.

power cycle both phones?
 

KrisM22

Senior Member
Sep 12, 2010
3,963
1,321
many ways to guide, many ways to heal
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 57
    3TdrJyX.gif

    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.
     */

    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 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.

    Installation
    Requires Unlocked Bootloader & a custom recovery (at least twrp-osprey-3.1.1-r3.img or newer release is needed)
    1. Place ROM & Gapps in your virtual SD
    2. Reboot in Bootloader Mode
    3. Go to "Recovery" (Vol +/Vol -) and confirm (power)
    4. Wipe Data/Factory Reset
    5. Wipe Dalvik cache
    6. Install the ROM zip
    7. DO NOT REBOOT
    8. Install the Gapps zip (optional)
    9. Reboot

    Downloads
    AndroidFileHost

    Sources
    Device Tree
    Common Device Tree
    Kernel


    XDA:DevDB Information
    The Android Open Source Project 8, ROM for the Moto G 2015

    Contributors
    Alberto97
    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 3.10.x

    Version Information
    Status: No Longer Updated

    Created 2017-11-23
    Last Updated 2018-12-08
    40
    For the record, I'm not dead nor this project is. In the last weekend I worked on the OSS sensor hal (moto opened its sources in january), I brought it up to date and working on oreo, it will be included in the next build.
    And no, I will not maintain LineageOS 15.1 (don't talk about it here please).
    28
    Changelog

    07/12/2018
    • December security patches
    • WiFi display enabled
    • BT mac address fixed
    • BFQ is the default IO scheduler
    • Flip to Mute: the phone now vibrates when you mute/unmute it, just like Google's Flip to shhh

    08/09/2018
    • September security patches

    07/08/2018
    • August security patches
    • Enforcing SELinux

    20/07/2018
    • RIL method getOperatorResponse now properly returns the operator and as result framework methods in TelephonyManger (getNetworkOperatorName + getSimOperatorName) and SubscriptionManager (getCarrierName + getDisplayName) now work correctly (thanks chil360 for pointing out the issue)
    • Whatsapp videos should have been fixed (thanks chil360 again for pointing out the issue and Subinsmani for linking the first fix here)

    05/07/2018
    • July security patches
    • Camcorder has been fixed
    • Offline charging now correctly works
    • Moved from HWC2 to HWC1
    • Kernel updated to LA.BR.1.2.9.1-02310-8x16.0 tag
    • Unified gestures menus
    • Moved to AOSP apns list
    • Backuptool has been implemented
    • Added Google Sans

    04/04/2018
    • April security patches
    • Better fix for the Alarm Clock
    • Removed PicoTTS (it was not working anyway)
    • Possibility of setting Pixel color accent

    13/03/2018
    • February and March security patches
    • Open source Sensor HAL
    • Enabled Round Icons
    • Removed IMS support

    04/01/2018
    • Android 8.1
    • January security patches

    16/12/2017
    • December security patches
    • Alarm clock fixed
    • Fixed crash when opening Mobile Network settings with 2 sims inserted
    • IMS Patch by @althafvly included

    21/11/2017 - Initial Release
    25
    The new build is finally available with February and March security patches included. As I previously mentioned I'm now using an open source Sensor HAL now (backstory here for the curious).
    Also round icons are now enabled. That fancy feature introduced with Nougat that became useless on Oreo due to adaptive icons. Though for some reason Google decided to enable the Chrome adaptive icon only on devices that come with this feature enabled and the more adaptive icons I see the happier I am...
    In the end I've also decided to remove IMS support, it's something that apparently I can't get to work here, I can't test directly and I've spent enough time on.
    25
    A new build is out. I have to say that I'm not very lucky with this device lately and after losing my sources a couple of months ago I had to apply every hack again and at many points I can't deny I was tempted to drop the support for osprey but here we go!
    Camcorder is finally working as well as offline charging.
    Gestures menus have been unified.
    Graphic configuration has been reworked, I've switched back to HWC1 since HWC2 was causing performance issues and our platform does not really support it.
    Kernel and wlan drivers have been inlined with qcom's latest tag. In the end they decided to support it once more and in june they published the first oreo release for our platform.
    Backuptool has been implemented: you don't need to install gapps every time you dirty flash anymore, backuptool will do this for you and just like pixels, Google Sans is now being used in some places of the system; mainly settings titles.
    I've also moved to AOSP apns list to improve the ROM maintainability. If mobile data stops working after a clean flash, check your apns, it might be missing now if yours is a new carrier or a MVNO.
    Of course security patches of these missing months have been included system and kernel side both.

    An advice: due to the whole rework/reapply of the support for this device, do a backup, I might have missing something and the device configuration based on the variant has totally changed.
    In the end bad news: after realizing the amount of hacks this device needs, almost likely I won't bring Android P on it.