• 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

chief912

Member
Jan 27, 2018
29
3
I haven't tried out this rom I'm on Lineage os 15.1
I'm thinking of switching the rom Which is better Aosp extended or This one which is more smooth
like I play pubg and use my phobe alot which is better overall
To my experience, LineageOS has the better gaming performance than AOSP Extended. But I recommend this AOSP ROM for gaming. I play Mobile Legends at High Graphics and it works well. I don't know about the stability, customizations and and day-to-day use (compared to others)but for games I prefer this ROM.
 
Last edited:

Shreeram02

Senior Member
Jan 28, 2018
485
58
sirsi
Moto Z2 Force
Realme X50 Pro
To my experience, LineageOS has the better gaming performance than AOSP Extended. But I recommend this AOSP ROM for gaming. I play Mobile Legends at High Graphics and it works well. I don't know about the stability, customizations and and day-to-day use (compared to others)but for games I prefer this ROM.
I'm using lineage os i can play pubg without lags can i do the same with aosp
Ur talking about aosp by alberto or aosp extended
 

stonny20

Senior Member
Aug 29, 2017
140
38
Kochi
I know this is little of topic but how do u play pubg without lags?? When i open pubg it say my device is not supported. Do u use any tweak or do u have 2gb version?
For pubg the minimum requirement is 2gb ram. Even with 2gb variant pubg will start laggs after a game or two. Anyway our device is way to old for playing pubg:crying: It will lagg.
 
  • Like
Reactions: Shreeram02

Shreeram02

Senior Member
Jan 28, 2018
485
58
sirsi
Moto Z2 Force
Realme X50 Pro
I know this is little of topic but how do u play pubg without lags?? When i open pubg it say my device is not supported. Do u use any tweak or do u have 2gb version?
I have 2gb version
I daily play pubg almost 2-3hrs in my osprey I start playing pubg as soon as i come back from school and play till my battry goes off I almost play 2:30 hrs(5 matches)
I use gfx tool to reduce resolution to 540p
I used to play in 720p but it drains battery fast and now it is a lot better
 

Alberto97

Recognized Developer
Feb 6, 2012
976
7,828
23
No it will crash camcorder....
@Alberto97 sir u need this commit to fix whatsapp media related bug..

https://github.com/Subinsmani/andro...mmit/771548e15d4de5f37e582af8d00570861df80ac0

Sent from my MotoG3 using Tapatalk
Thank you very much for this :) I took another way in order to not break lux and harpia and I've released another build with the fix. I did not test it (I don't use whatsapp on osprey) but I'm confident it works since it is used on another 8916 device for exactly the same issue.
 

Subinsmani

Senior Member
Nov 18, 2016
1,704
3,527
26
Delhi, Trivandrum
Thank you very much for this :) I took another way in order to not break lux and harpia and I've released another build with the fix. I did not test it (I don't use whatsapp on osprey) but I'm confident it works since it is used on another 8916 device for exactly the same issue.
Wow gr8 sir...
And sir one more bug is there gps...
For reference u can look on chil360 commits.. he fixed that too...
Now he is looking for HDR issue..

Sent from my MotoG3 using Tapatalk
 

rahul9999

Senior Member
New build available with August security patches and SELinux is finally enforcing too. Now that P is out I don't know for how much time I'll be able to provide other builds but I hope at least for other two months.

Good to hear that :).. Just for your information some osprey devs already got P booted.. but still we need your support to fix all things.. hope you join us soon :eek:
 

jorge_613

Member
Dec 27, 2009
5
0
Hi , I install this rom in my moto g3 in doestn work the wifi hotspot, why? thanks.

---------- Post added at 07:04 AM ---------- Previous post was at 06:57 AM ----------

I cant hear the whatsapp voice note..why? how can I fixed?
 

jorge_613

Member
Dec 27, 2009
5
0
HEllo, How Can I do a downgrade to a version like Line AGe Os lineage-14.1-20180317-nightly-osprey-signed for example.
How Can I do a downgrade?


THanks.
 
Last edited:

Son Gok

New member
Jul 9, 2018
3
0
Whatsapp bug continues. Do not play videos. The whatsapp audio is also bugged .. It seems the biggest problem is in whatsapp. Browser does not play full screen video. Pardon my English.:)
 

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.