• 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

rahul9999

Senior Member
  • Like
Reactions: mr._.nobody

scattey

Senior Member
May 17, 2016
57
7
can anybody plzz help me by telling me what are the bugs present in this rom apart from camcorder
and what is permissive linux can plzz help me understand it
thanks in advance:)

When SELinux is in permissive mode, it is off. It should be on for security. SELinux stops apps from accessing and doing things they're not supposed to. Your phone is less secure in permissive mode.
 

mr._.nobody

Senior Member
Oct 4, 2017
144
15
When SELinux is in permissive mode, it is off. It should be on for security. SELinux stops apps from accessing and doing things they're not supposed to. Your phone is less secure in permissive mode.

Thanks a lot:)

---------- Post added at 02:16 PM ---------- Previous post was at 02:16 PM ----------


Thanks mate :)
 

Airtornado

Member
Jan 9, 2011
14
3
Moscow
Not having seen a pic of the error report

log.

01-24 10:49:03.709 W/ProcStatsManager(30370): No process com.android.fmradio/1000 for service com.android.fmradio.FmService

01-24 10:49:03.825 W/ProcStatsManager(30370): No process com.android.fmradio/1000 for service com.android.fmradio.FmService

01-24 10:49:10.315 E/AndroidRuntime(30419): at com.android.fmradio.FmService.openDevice(FmService.java:576)

01-24 10:49:10.315 E/AndroidRuntime(30419): at com.android.fmradio.FmService.onCreate(FmService.java:1298)
 

Attachments

  • Screenshot_20180124-105856.jpg
    Screenshot_20180124-105856.jpg
    77.2 KB · Views: 969

KrisM22

Senior Member
Sep 12, 2010
3,963
1,321
many ways to guide, many ways to heal
log.

01-24 10:49:03.709 W/ProcStatsManager(30370): No process com.android.fmradio/1000 for service com.android.fmradio.FmService

01-24 10:49:03.825 W/ProcStatsManager(30370): No process com.android.fmradio/1000 for service com.android.fmradio.FmService

01-24 10:49:10.315 E/AndroidRuntime(30419): at com.android.fmradio.FmService.openDevice(FmService.java:576)

01-24 10:49:10.315 E/AndroidRuntime(30419): at com.android.fmradio.FmService.onCreate(FmService.java:1298)

Thanks - okay, I'll back off on blaming the apk extractor and blame it on 8.1 - let's see what it's like in the next release or 2... 8.1 is still very very young and I have to keep reminding myself that google (the company that writes all this code... :) ) has been unsuccessful in getting it to run well on its own devices, like Pixels and Nexi.

---------- Post added at 05:52 AM ---------- Previous post was at 05:51 AM ----------

I can`t send video made on Fotej camera via WhatsApp.

Again, gotta wait for 8.1 to mature - it's just not there, and won't be until they straighten out this camera business. Will it ever??? I don't know... :(
 

Subinsmani

Senior Member
Nov 18, 2016
1,704
3,521
26
Delhi, Trivandrum
log.

01-24 10:49:03.709 W/ProcStatsManager(30370): No process com.android.fmradio/1000 for service com.android.fmradio.FmService

01-24 10:49:03.825 W/ProcStatsManager(30370): No process com.android.fmradio/1000 for service com.android.fmradio.FmService

01-24 10:49:10.315 E/AndroidRuntime(30419): at com.android.fmradio.FmService.openDevice(FmService.java:576)

01-24 10:49:10.315 E/AndroidRuntime(30419): at com.android.fmradio.FmService.onCreate(FmService.java:1298)
how u install the radio app....
if u install radio by apk then this will not work.. it will force close...
because u need to add radio required lib also to run that service..

Sent from my MotoG3 using Tapatalk
 

pio80

Senior Member
Apr 28, 2015
153
34
Hi ,
I am looking around...and thinking..
Sorry but I have to ask:
Why devs are starting something and never release the final version?
What's the point of starting any project? - (for example) like this?
 

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.