[JDCTeam][8.0.0][BETA][01 Dec] The Android Open Source Project OREO

Search This thread

smeroni68

Inactive Recognized Contributor
Jan 23, 2011
4,455
11,020
Milano
JDC_aosp8_0.png

Oreo_1_update.jpg


The Android Open Source Project Oreo
Brought to you by Jflte DevConnection Team

Code:
#include <std_disclaimer.h>

/*
 * Your warranty is now void.
 *
 * We're 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 us for messing up your device, we will laugh at you.
 *
 */


What is AOSP?
AOSP is Android as Google publish without other modifications. More or less AOSP is the Nexus devices stock rom without gapps. Anyway to get a working system we ported some changes from Cyanogenmod/LineageOS and CodeAurora repos.
Please do not ask for features to be added because we're not going to add more to keep this ROM small, fast and pure.


JDCTeam
In alphabetical order:


Screenshots:

Screenshot_20170905-225148.png
Info800.png


WHAT'S STILL BROKEN:
  • VOLTE
  • OTAUpdates
  • BT Audio playback
  • DT2W not working (Use Kernel Adiutor to enable it)
  • Screen recording and mirroring not working

WHAT'S WORKING:
  • Camera and flashlight through API2 and OSS Hal (tested also with GCamera 5.1.018 porting)
  • Audio/Video/Media
  • RIL
  • Sensors
  • GPS
  • WiFi
  • Data connection
  • Magisk root and SafetyNet (check in ADDON section for Magisk v14.5)
  • USB Connection
  • Substratum (certified)
  • Fingerprint
  • SMS
  • LatinIME
  • ConfigPanel
  • Button lights
  • NFC
  • BT
  • CNE --> From Marlin, needs test
  • Audiopolicymanager
  • CALLS
  • Wired Headsets


Download
ROM builds are hosted on ROMHUT or Here


Installation

Important note's before installation:

  • This rom is a BETA VERSION and IS SUITABLE TO BE USED AS DAYLY DRIVER; DO ANYWAY A FULL NANDROID BACKUP of previous version for safety.
  • This rom is based on O qcom drivers and blobs. Download and install the latest tested firmware package you can find HERE, that contain only the latest tested firmware (flash in TWRP recovery, at your own risk).
  • In case of use of F2FS file system, please upgrade to latest TWRP based on Android N code (TWRP v3.1.1-x). This will avoid problems to apply Magisk root during Magisk flash (in case you install it).

Clean install:
  1. Download the ROM from the link above
  2. Download Opengapps ARM64 package for Android 8.0
  3. Put the zip files on your SDCard
  4. Reboot in Recovery
  5. Wipe Data / Factory Reset
  6. Optional: convert to F2FS
  7. Select "Install zip from SDCard"
  8. Choose AOSP ROM zip file
  9. Choose GApps zip file
  10. Flash
  11. Reboot system

Sources
GitHub


Social
Google+: JDCTeam Community
YouTube: JDCTeam TV


Credits
  • JDCTeam
  • LinageOS
  • Google
  • MI5Devs
  • TeamSubstratum
  • PureNexus
  • RenderBroken

Special thanks:


XDA:DevDB Information
AOSP 8.0.0 for Xiaomi Mi5, ROM for the Xiaomi Mi 5

Contributors
smeroni68, -+BB+-
Source Code: https://github.com/AOSP-JF-MM

ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: AOSP

Version Information
Status: Beta
Current Beta Version: Beta 2
Beta Release Date: 2017-12-01

Created 2017-09-05
Last Updated 2018-03-12
 
Last edited:

masterlo3

Senior Member
May 3, 2014
625
184
Maybe it's just me but I'm getting better batterylife on Oreo. Boot is faster than Nougat too.
Nice build
 

Top Liked Posts

  • There are no posts matching your filters.
  • 88
    JDC_aosp8_0.png

    Oreo_1_update.jpg


    The Android Open Source Project Oreo
    Brought to you by Jflte DevConnection Team

    Code:
    #include <std_disclaimer.h>
    
    /*
     * Your warranty is now void.
     *
     * We're 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 us for messing up your device, we will laugh at you.
     *
     */


    What is AOSP?
    AOSP is Android as Google publish without other modifications. More or less AOSP is the Nexus devices stock rom without gapps. Anyway to get a working system we ported some changes from Cyanogenmod/LineageOS and CodeAurora repos.
    Please do not ask for features to be added because we're not going to add more to keep this ROM small, fast and pure.


    JDCTeam
    In alphabetical order:


    Screenshots:

    Screenshot_20170905-225148.png
    Info800.png


    WHAT'S STILL BROKEN:
    • VOLTE
    • OTAUpdates
    • BT Audio playback
    • DT2W not working (Use Kernel Adiutor to enable it)
    • Screen recording and mirroring not working

    WHAT'S WORKING:
    • Camera and flashlight through API2 and OSS Hal (tested also with GCamera 5.1.018 porting)
    • Audio/Video/Media
    • RIL
    • Sensors
    • GPS
    • WiFi
    • Data connection
    • Magisk root and SafetyNet (check in ADDON section for Magisk v14.5)
    • USB Connection
    • Substratum (certified)
    • Fingerprint
    • SMS
    • LatinIME
    • ConfigPanel
    • Button lights
    • NFC
    • BT
    • CNE --> From Marlin, needs test
    • Audiopolicymanager
    • CALLS
    • Wired Headsets


    Download
    ROM builds are hosted on ROMHUT or Here


    Installation

    Important note's before installation:

    • This rom is a BETA VERSION and IS SUITABLE TO BE USED AS DAYLY DRIVER; DO ANYWAY A FULL NANDROID BACKUP of previous version for safety.
    • This rom is based on O qcom drivers and blobs. Download and install the latest tested firmware package you can find HERE, that contain only the latest tested firmware (flash in TWRP recovery, at your own risk).
    • In case of use of F2FS file system, please upgrade to latest TWRP based on Android N code (TWRP v3.1.1-x). This will avoid problems to apply Magisk root during Magisk flash (in case you install it).

    Clean install:
    1. Download the ROM from the link above
    2. Download Opengapps ARM64 package for Android 8.0
    3. Put the zip files on your SDCard
    4. Reboot in Recovery
    5. Wipe Data / Factory Reset
    6. Optional: convert to F2FS
    7. Select "Install zip from SDCard"
    8. Choose AOSP ROM zip file
    9. Choose GApps zip file
    10. Flash
    11. Reboot system

    Sources
    GitHub


    Social
    Google+: JDCTeam Community
    YouTube: JDCTeam TV


    Credits
    • JDCTeam
    • LinageOS
    • Google
    • MI5Devs
    • TeamSubstratum
    • PureNexus
    • RenderBroken

    Special thanks:


    XDA:DevDB Information
    AOSP 8.0.0 for Xiaomi Mi5, ROM for the Xiaomi Mi 5

    Contributors
    smeroni68, -+BB+-
    Source Code: https://github.com/AOSP-JF-MM

    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 3.x
    Based On: AOSP

    Version Information
    Status: Beta
    Current Beta Version: Beta 2
    Beta Release Date: 2017-12-01

    Created 2017-09-05
    Last Updated 2018-03-12
    51
    ALPHA 2 is online... STILL camera broken...

    Hi Guys,
    as advised, we are releasing a new update of the rom, but still with camera not working.

    Here the status, of the build:


    #### ALPHA 2 (20170927)

    * WHAT'S BROKEN:
    * Camera/Flash completely not working
    * Home does not wake up device (missing code)
    * VOLTE
    * BT Audio streaming

    * WHAT'S WORKING:
    * Audio/Video/Media
    * RIL
    * Sensors
    * GPS
    * WiFi
    * Data connection
    * Magisk SafetyNet
    * USB Connection
    * Substratum (needs root)
    * Fingerprint
    * SMS
    * LatinIME
    * ConfigPanel
    * Clock app
    * Button lights
    * Nfc
    * BT
    * CNE --> From Marlin, needs test
    * Audiopolicymanager
    * CALLS
    * Wired Headsets

    It's STILL a preview version.

    Direct link to download: https://romhut.com/versions/jdcteam_jdc_gemini-8-0-0-20170927-alpha-eas-alpha-2

    From this build, OTAUpdates detect on request if a new version is available for download.

    Enjoy!
    30
    Hi guys, time for a new update for 8.1 DP, here's the link: https://www.androidfilehost.com/?fid=817906626617944989

    Patched with november security updates :)

    Also camera is fully fixed now, no more need to wait a few seconds when user start camera app :)
    This will be hopefully the last "unofficial release", next one will be official with updated OP (still some things to fix :) )

    @-+BB+-, could you tell which branch is used in your ROM for kernel build from android_kernel_xiaomi_msm8996?

    Currently lineage-15.0 is 3 commits behind of cm-14.1 branch, however when trying to flash SafetyNet kernel (based on cm-14.1), the device does not boot and goes into fastboot mode after a while...

    I'm wondering what's the reason for this.

    Anyway, great ROM! [emoji846]

    Sent from my Xiaomi Mi5 using Tapatalk

    Sure, this is the branch: https://github.com/AOSP-JF-MM/platform_kernel_xiaomi_msm8996/tree/aosp-8.1-test
    Defconfig: https://github.com/AOSP-JF-MM/platf...test/arch/arm64/configs/aosp_gemini_defconfig
    You may need to partially revert this: https://github.com/AOSP-JF-MM/platf...8b286ab#diff-a65cd02f60e5768b325501aa7bdcce66 because adds EAS and remove HMP support, unless you want to add EAS support on LOS Ramdisk
    29
    Treble gemini progression... versioned_vndk!!

    Hi guys,
    we have some news about this project... are you curious?

    Well, today @sir mordred has finally built the first version (only for internal use and testing... so do NOT ask for ETA) of VERSIONED VNDK TREBLE for our device!!

    For who has time to read a bit more, here I'll report some info from devs!!

    What's versioned_vndk?

    It's simply a superior version of full-treble implementation which has been introduced by Google in 8.0 Oreo.

    Even if the full-treble implementation was supposed to isolate system (framework) and vendor implementation (HALs), vendor modules can still access system modules (as fallback mechanism), but with versioned_vndk Google applied strict rules to full-treble implementation that no module which is labeled as vendor module can access to system modules and vice versa.

    Android's dynamic linker is responsable to do this isolation/restriction as described in google's treble docs, so its just an updated treble implementation which applies full-restriction/isolation rule between system modules and vendor modules (libs,executables etc.), hence its superior version of full-treble implementation, and for reference versioned_vndk is not enabled neither in 8.0 nor 8.1 (Oreo-mr1) by default but as per google's treble documentation, enabling of versioned_vndk is recommended to OEMs on Oreo-mr1 and it has been clearly stated that it will be enforced on android P.

    On versioned_vndk enabled builds, vendor image's treble-version (ro.vendor.vndk.version) is 27 and vendor image is using new subset of vndk-sp modules which are just an intermediate compatibility libs between system layer and vendor layer, and from the latest public AOSP sources, Google enabled versioned_vndk support for their Pixel 2 series phones (wahoo family) and didn't enable it for their fully-trebelized Pixel 1 series (Marlin and Sailfish) and with ongoing development which we are doing for Mi5 as JDCTeam we removed dozens of vendor <=> system dependencies (we are calling them as violation since as we said earlier, no vendor modules should access/depend system modules and vice versa, as per the versioned_vndk rule) we have now compiled and booted fine a build with versioned_vndk enabled, and we partially achieved versioned_vndk support for Mi5.

    Now, our configuration (system, vendor and kernel) are configured against versioned_vndk changes/support and it booted fine, well why we call it as "partially"? Since we have a lots of closed source proprietary libs, unfortunatly a lots of them depend/link to system modules (violations! As per versioned_vndk rule) and since we dont have source for them, removing these dependency/linkage without breaking functionality requires really hard work... but thanx to our hexedit skilled devs we succesfully eliminated lots of violations and we have now a small number of violations left to fix, and since we still have these violations we temporarily disabled runtime-restriction (isolation) via BOARD_VNDK_RUNTIME_DISABLE as google suggested to OEMs in here https://source.android.com/devices/architecture/vndk/linker-namespace in case of some violations which need to be resolved.

    Hope you enjoy the reading over here!! ;)
    27
    MI5 32/64GB searching for development...

    Hi guys,
    we started underground some experimentations regarding a new project that involve a new developer.
    I'm searching/asking if someone has a MI5 32 or 64GB in good conditions and fully forking (a phone without issues to be clear) to buy at a friendly price (via paypal possibly).

    This project hasn't been announced yet, but unofficially we are working to develop a full treble support for the Mi5... now you can understand why we need a spare phone to play with.

    I hope that who is reading this post and has a spare phone not more used, can PM me to let us check the availability of it (and a friendly selling price).

    As I wrote, it is only for development, so if I bought a spare phone is my personal money that I spent... we do not gain money from our JDCTeam roms... so you are advised to avoid to offer a phone at 150 euro... sincerely, I'll not spend so much money to test and experiment.

    To all guys that will read, thanks for helping finding a solution and possibly not so far from Italy...

    Best Regards to all

    smeroni68 - JDCTeam

    EDIT: Needed one also for Turkey country... is for developer...

    EDIT2: For Italy already found a spare phone... need only for Turkey...