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

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

Search This thread

Psicovirus

Senior Member
Apr 29, 2017
103
11
Xiaomi Redmi Note 7
Yes, you can. You need to have titanium backup Pro version to make a twrp flashable zip of all user apps + data.

I can use that zip file in various versions of the OS or just the one of which I made the backup? if it is only the apps, I can do that? .ie: Use it in 8.0 then flash 8.1 and use it again as a quick config to be up and running in no time.
 

KrisM22

Senior Member
Sep 12, 2010
3,963
1,321
many ways to guide, many ways to heal
I can use that zip file in various versions of the OS or just the one of which I made the backup? if it is only the apps, I can do that? .ie: Use it in 8.0 then flash 8.1 and use it again as a quick config to be up and running in no time.

I wouldn't. Also realize that the stuff in the zip will quickly go out of date. I frequently turn on wifi, go to GP and update what needs to be updated, and then redo TBPro backups. Then when I flash I run a restore. takes care of most stuff. I don't know about going betwen 8.x and 7.x . Have to start over when switch to 64bit phone.
 

samir.saurav

Senior Member
Jun 28, 2012
326
88
Hyderabad
OnePlus 7T
I can use that zip file in various versions of the OS or just the one of which I made the backup? if it is only the apps, I can do that? .ie: Use it in 8.0 then flash 8.1 and use it again as a quick config to be up and running in no time.
When switch is major like nougat to oreo, i feel, you will face issues like FCs due to app compatability. Rest should be fine. I used to switch between roms based on same version without any issues. Good luck and please report back the outcome.
 

KrisM22

Senior Member
Sep 12, 2010
3,963
1,321
many ways to guide, many ways to heal
As I previously said I couldn't find it within the gapps file, but if you think you can here is a link the entire package.

https://www.dropbox.com/s/7s0rts32ku15gye/open_gapps-arm-8.0-micro-20171225.zip?dl=0

I couldn't find it. There are apps in googleplay that will extract/form an apk from an installed app so if it is still in your build you could try one of those. If I get time later I will do a temp flash and see if it's there.

EDIT this is an 8.0 gapps - can't be flashed with Alberto's 8.1 AOSP. (unless I hack it)

Nope not there - you got it from somewhere else.
 
Last edited:
  • Like
Reactions: Airtornado

Aptony

Senior Member
Dec 7, 2013
83
18
  • Like
Reactions: Airtornado

KrisM22

Senior Member
Sep 12, 2010
3,963
1,321
many ways to guide, many ways to heal
Seems like you flashed 8.0 ROM :D because there's Radio FM on these builds.

Anyways if you are on 8.1 ROM u can extract apk and libs from system/priv-app/Radio FM I'll be really grateful.

As I just said, I flashed it (after I hacked it to 8.1) and it's not there.

This is off topic - Ask at Q&A.
 
Last edited:
  • Like
Reactions: Airtornado

Selmak

Senior Member
Jul 7, 2010
267
65
OK as requested I managed to extract the FM Radio apk file using an app called APK Extractor from the Play Store. I've attached the file here for you. Let me know if it works.

To address the question that came up about the gapps package I posted being for 8.0 and not 8.1 that is because I am still on 8.0. I haven't had the time to deal with a clean flash to go to 8.1 yet, plus there seem to have been some regressions anyway. So I figured I'd just wait another cycle.

Oh and KrisM22 I'm sorry you went to all the trouble of flashing that gapps file I posted. I didn't think anyone would go that far. I only posted it to see if anyone could find the radio file in it. I wish I would have posted the FM radio file here faster now so you wouldn't have had to go through that.
 
Last edited:
  • Like
Reactions: Airtornado

Psicovirus

Senior Member
Apr 29, 2017
103
11
Xiaomi Redmi Note 7
To tell what it is now:

If you have an sd card reader stick it in there and let whatever OS you have tell you what it's formatted as.

Oddly, no app that I have tried will tell you the format in situ, so go to TWRP,
Wipe,
Advanced wipe,
check sdcard,
tap "repair or change file system,
and in the very faint printing you will see it is vfat.
NOW, CAREFULLY, left arrow yourself out of there so nothing is changed.

To format it in situ (plugged in to your phone):
Note: This is instrs for re-formatting an SDcard if I/O errors or space probs!:
Boot to ROM to back it up to PC first if there's stuff on it!!!
settings/storage/portable storage/3 dotts/storage settings/format.

Moral of story: always have several sd card readers and micro sdcard adapters handy!!! :)

Something I didn't quite understand, it should be vfat or fat32?

EDIT: Figured that out myself. I've done a clean flash, wiped everything, made sure the formats are correct and followed Kris's guide exactly as he said.

Lockscreen still sluggish and security backup screen showing negative free memory space, Ill attach an image.
After this I'm reverting to Nougat because this is my main phone.

Thanks for all friends!

https://drive.google.com/file/d/1R88MnWNjiPa0DzgFSACjI16L66BYW_Iv/view?usp=sharing
 
Last edited:

KrisM22

Senior Member
Sep 12, 2010
3,963
1,321
many ways to guide, many ways to heal
Something I didn't quite understand, it should be vfat or fat32?

EDIT: Figured that out myself. I've done a clean flash, wiped everything, made sure the formats are correct and followed Kris's guide exactly as he said.

Lockscreen still sluggish and security backup screen showing negative free memory space, Ill attach an image.
After this I'm reverting to Nougat because this is my main phone.

Thanks for all friends!

https://drive.google.com/file/d/1R88MnWNjiPa0DzgFSACjI16L66BYW_Iv/view?usp=sharing
ref vfat - maybe this will help:
https://stackoverflow.com/questions...ifference-between-vfat-and-fat32-file-systems
 

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.