[ROM][SNAPSHOT][7.1.2] AOSP Nougat for Xperia SP

Search This thread

acimgaara

New member
Feb 6, 2017
1
0
hello guys,
my friend's phone xperia sp c5303
before wipe, have cwm recovery > root n install to extended aosp, but forget to install opengapps,
now it dont have cwm recovery, just have android recovery,
how to fix it,? seem phone not rooted
ive tried many way to root it but it can stand long time at bootloader
tq
 

Torontus

Senior Member
Aug 25, 2017
97
22
Almada, Setúbal
hello guys,
my friend's phone xperia sp c5303
before wipe, have cwm recovery > root n install to extended aosp, but forget to install opengapps,
now it dont have cwm recovery, just have android recovery,
how to fix it,? seem phone not rooted
ive tried many way to root it but it can stand long time at bootloader
tq

Just flash, with flashtool on windows, a new recovery. Twrp recommended. Then use bootbridge elf from AdrianDC to get root on Nougat.
And you are good to go.

https://forum.xda-developers.com/crossdevice-dev/sony/mod-boot-bridge-sony-elf-t3506883
 
Last edited:

globe79

Senior Member
Apr 1, 2013
68
33
Sony Xperia SP
Moto G
1. Read a lot about BlueBorn vulnerability... hope you'll incorporate a fix it in your future releases of Nougat and Oreo AOSP.

2. When I go to Developer options->Select USB Configuration, whatever I chose MTP (...) stays highlighted (running your 7.1.2 20170802.162849 build).

3. Music apk suc*s - it's ugly dark text on dark background. I know you are trying to be as close to AOSP as possible.

4. I'm unable to record calls anymore (I moved from stock 4.3, where both sides could have been recorded) with ACR or similar apps. Only microphone can be used as a source to record one side of a call - I think is an issue/design of Androids since 6.0.

5. When I manually search for network, networks are listed without their bands (2G, 3G, LTE/4G) next to the network name. You see some of them tripled and don't know what tho choose. It's OK until you roam and the roaming contract doesn't cover all bands.

Other than that perfect! Keep on posting forever!

Happy HuaShan user! :)
 
  • Like
Reactions: AdrianDC

Siyaset

Member
May 1, 2016
8
2
26
Neftçala
No root

Hi i want root. This rom is good very fast because there is not root. İ want active root but i cannot it. İ am very tired help me please
 

akimester

Senior Member
Apr 3, 2014
149
28
Budapest
hi all !
i have a little(?) trouble with this ROM.
Simply it doenst work !

By TWRP 3.1.1.0 it installs successfully ,but finally the ROM does not starts !
After the Sony logo the android animation starts and goes and goes, nothing more. After ~20 mins and nearly 6 clean installs i give it up.
Some tech things :

C5302
UBL
Dalvik/Cache,System,Data wiped all the times.
Partitions are EXT4 ,except Cache (or Data,i dont remember).Its F2FS.
Tried to install it with latest OpenGapps ,Bootbridge(SuperSU,later Magisk ,by the description),Helium V51 and of course only the AOSP Nougat.
Unsuccessfully.

Who can help me ? Any idea ? :(
 
Last edited:

NyQuilXT

Senior Member
Jan 15, 2016
180
353
Hi,
I currently have the 14.1 -20171227-NIGHTLY-huashan installed. Can you please give me instructions to install the Android 8.0 Oreo on my handset, as I'm unable to install it. Thanks.
I may ask you, if you are able to read the first post?!? ...of the corresponding oreo thread...
 
Last edited:

hannor

Senior Member
Nov 30, 2015
73
48
Budapest
Dear Adrian, I tested this ROM's (latest, 31 Dec 2017) wireless screen also (as I did with 7.1 Lineage). It does not work - finds my wireless projector, but cannot connect to it.
 

hannor

Senior Member
Nov 30, 2015
73
48
Budapest
In this case, the rule is to send the logcat so that the OP gets acquainted with the specific problem.
Dear ze7zez, I needed screen cast (wireless display) urgently, so I downgraded to CM 13, where wireless screen mirroring works perfectly - hence, I won't be able to send logcat. But I suspect screen cast does not work in the Android 7 ROMs for SP at all, not only with my wireless projector - I hope someone can prove me wrong!
 

ze7zez

Senior Member
Aug 24, 2012
2,749
1,343
Kraków
nz.geoview.info
Dear ze7zez, I needed screen cast (wireless display) urgently, so I downgraded to CM 13, where wireless screen mirroring works perfectly - hence, I won't be able to send logcat. But I suspect screen cast does not work in the Android 7 ROMs for SP at all, not only with my wireless projector - I hope someone can prove me wrong!

I suspected you had the will to cooperate and want to get involved in the development of ROM through feedback.
Returning to CM13 will not be a problem after performing a backup ROM via TWRP.
Once you have done this, install android 7.1.2 and connect to the projector, and then dump logcat to the file.
I think nothing is difficult about it?
 

hannor

Senior Member
Nov 30, 2015
73
48
Budapest
I suspected you had the will to cooperate and want to get involved in the development of ROM through feedback. Returning to CM13 will not be a problem after performing a backup ROM via TWRP. Once you have done this, install android 7.1.2 and connect to the projector, and then dump logcat to the file. I think nothing is difficult about it?
It is not difficult at all, I'll do it asap. However, I do think it is a general screen cast problem, so if Adrian fixes screen cast in this ROM for ANY device, it will work with my projector, too. Btw, are you also a developer for this ROM?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 110
    android_nougat-300x288.png

    Code:
    #include <std_disclaimer.h>
    /*
     * 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.
     */


    Downloads Links
    AOSP 7.x Nougat (Unlocked Bootloader) :
    Xperia SP (Huashan) - 7.1.2 : https://mega.nz/#F!LtNjDKBQ!YdZPyZghv07Tp2J8EgxcfQ

    Google Applications (optional) :
    OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
    Information : Flash the GApps before the first boot. If not, a clean flash is recommended.

    Recommended Recovery (optional) :
    TWRP 3.0 : http://forum.xda-developers.com/xpe...t/recovery-twrp-3-0-0-touch-recovery-t3309938

    Informations and references :
    Kernel CVEs : Security patches status https://cve.lineageos.org/android_kernel_sony_msm8960t
    About AOSP : Repositories available on https://android.googlesource.com/


    Flashing and updating
    AOSP clean install :
    - (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
    - (Optional) Wipe the data & cache (Backup to make sure not to lose data)
    - Flash the AOSP ROM zip from the Recovery
    - (Optional) Flash the GApps to have the Google Applications
    - (Optional) Every additional zip you want to flash
    - Reboot

    AOSP update / upgrade :
    - (Information) Don't wipe anything unless you want to
    - Flash the latest AOSP ROM zip from the Recovery
    - (Optional) Flash the GApps if you want to, otherwise preserved.
    - (Optional) Every additional zip you want to flash
    - Reboot


    About the builds


    Issues and reports
    - Report issues only if you use the ROM kernel
    - If an additional mod is installed, make sure it's unrelated, and mention it
    - Make sure the issue wasn't discussed earlier in the threads
    - Share a log of the error with CatLog for example


    Q&A - FAQ
    Q : Is root access included into AOSP ?
    A : No but you can now root with my Boot Bridge and a superuser tool.

    Q : Is the ROM suited for daily usage ?
    A : Yes completely. OpenGApps recommended.

    Q : I see errors during the installation, is it normal ?
    A : If it is E:unknown command [log] , ignore it for now

    Q : Where can I change the Quick Tiles and Status Bar ?
    A : Long press the Settings icon in the notifications drawer.
    > You will have access to the SystemUI Tuner from Marshmallow.

    Q : The AOSP Keyboard does not support swipe gestures ?
    A : Unfortunately the sources for swipe gestures are not available
    and Google still requires their prebuilt library to be there for AOSP Keyboard.
    Download the following libjni_latinimegoogle.so API 23 from OpenGApps
    and push it to /system/lib/libjni_latinimegoogle.so using root access,
    or use my one-time install zips : https://mega.nz/#F!ThEAkCRa!byhSwuoTbf6lnC1JxgKrig.​


    AOSP available for Huashan also thanks to :
    - Google AOSP
    - The LineageOS Team
    - CodeAurora Forums
    - The CyanogenMod Team​


    XDA:DevDB Information
    AOSP Nougat 7.1.2, ROM for the Sony Xperia SP

    Contributors
    Adrian DC
    Source Code: https://android.googlesource.com/

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.4.x
    Based On: AOSP

    Version Information
    Status: Snapshot

    Created 2016-08-27
    Last Updated 2020-08-15
    72
    Reserved

    FEATURES AND ISSUES
    Code:
    - Boot : Ok
    - GApps : OpenGApps Micro Ok
    - Partitions (Data, Cache) : Ext4 supported
    - Dual Recovery : Ok (see below)
    - WiFi : Ok (real SONY MAC address)
    - Bluetooth : Ok (real SONY MAC address)
    - WiFi Hotspot : Ok (2.4GHz and 5GHz)
    - RIL - Phone - Data : Ok
    - GPS : Ok
    - Camera : Ok
    - Camcorder : Ok
    - Lights : Ok, regular AOSP lights support
    - MicroSD : Ok, only Ext4 support missing from AOSP
    - Accelerometer : Ok
    - Compass : Ok
    - Gyroscope : Ok
    - AOSP sensors : Ok
    - FM Radio : Ok
    - Vibrator : Ok
    - Microphone : Ok
    - Audio & external audio : Ok
    - Bluetooth audio : Ok
    - NFC : Ok
    - Kernel : Ok
    - Graphics : Ok
    - 3D Rendering : Ok
    - Clock : Ok (RTC real hardware clock, in TWRP recovery too)
    - Powered-off alarm : Ok
    - Offline Charging : Ok
    - Encryption : Status unknown
    - SEPolicies : Fully enforced


    IMPORTANT FEATURES TO KNOW
    • Boot sequence : Once the LEDs light up :
      - Press Volume - to open CyanogenRecovery,
      - Press Volume + to open the FOTA recovery (TWRP usually) if available
    • Powered-off alarm : When you have set an alarm
      - If you power down the device, it will wake automatically 5 minutes before
      - If you let the device charge offline, it will automatically reboot 5 minutes before
    • Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
    • Force reboot : You can reset the device by holding Power and Volume+ 5 seconds
    63
    As quite a few already know since months by looking at my public projects on GitHub,
    I have been working on the yet-to-be named and -to-be-redesigned AOSP Master since March / April.

    Unlike what users expect, the Master development branch of Android AOSP is related to hardware and sources cleanups, while the features and UI changes are kept internal by Google until the official release we just had.

    Working since all these weeks on Master (and O Preview 1/2/3/4) was meant to prepare the field for almost everything Huashan 8960t would potentially need.

    For instance, O requires multiple changes to the kernel for what is called hwbinder and vndbinder support, used by the userspace for the hardware services and all Android O hidl changes (Google these if you are interested, some of the notions are accessible to even non-developer readers). All these changes either match our code or needed backporting to 3.4(.113) 8960 kernels. I kept all these public and they are now on Gerrit (Sony 8960t).

    Basically, between April and July, my AOSP Master was fully working on the Xperia SP and the Xperia T, with tests on the Xperia TX and V too.

    One of the biggest time waste of this project was a very strong visual glitch of the display composition, which ended up coming from the libhwui changes involving graphics EGL capabilities. This will affect probably most devices of this generations, most likely using Flo Adreno binaries from M.
    I invite interested devs to read my details in my EGL property commit in Huashan sources.

    To finish on Master, Bluetooth stopped working properly despite my initial temporary workaround to increase timeouts (the new AOSP Bluetooth HAL is massively different) and WiFi broke last month too, and I haven't taken / did not have time to fix it yet. Everything else was fine and used as daily.

    Another major and personal motivation was to start the sepolicies fully clean. Detached from QCOM ones this time, I've progressively rebuilt the sepolicy rules as strictly as possible, with specific labelling and in order to match common policies as much as possible, in order to be close to Google Marlin device sepolicies standards. The device was running enforced over the last month and only minor changes to the commits will maybe be done now.


    Now... You skipped the first part and came here.
    As others noticed by spying on my GitHub again, we started unifying our personal works on AOSP last week to prepare the next iteration of LineageOS. This helped us working very quickly on our basis upon release of O.
    Obviously nothing or barely nothing feature related is done yet, hardware support is the priority. Please do not request ETAs or features randomly on the forum or else, further information will be shared when there is actually information to be shared.


    Finally the last part you'll skip to because of the pictures.... I've been rebasing my AOSP Master changes to the Oreo release 8.0.0 (r3 for Pixel), and progressively fixed new code / hardware support changes done by the release.
    This night (4am...) was spent attempting to complete the boot on Huashan.
    Along an issue of 1 change I did for master sepolicies that broke the initialization (anticipation back-fired), the multiple new hardware HALs needed to be properly selected and compiled to match the requirements and complete the boot without display EGL crashes or audio failures.

    The Oreo UI therefore fully booted. More work will be needed to bring back all features inline with my Master builds and to fix remaining things to do.
    Please do not request for ETAs there too. It will be done once possible on evenings.

    attachment.php


    PS: As I have been asked a few times, I confirm my Music Lights Effects with the Xperia SP's lights bar
    (presented in https://forum.xda-developers.com/showpost.php?p=73049970&postcount=399)
    will be working on 8.0.0 too, as it already was working on Master.

    Huashan remains undefeated and a challenging good no-so-old device.
    56
    Reserved

    Recent branches commits

    Changes log
    • 31/12 : New release on Android 7.1.2_r36 sources (October CVE patches)
    • 02/08 : Updated device sources, Lights Effects minor fix
    • 14/07 : New release on Android 7.1.2_r24 sources (July CVE patches) & Initial Music Lights Effects release (About)
    • 01/07 : Updated kernel vulnerabilities patches, fixes and external storage for Camera2
    • 18/06 : New release on Android 7.1.2_r17 sources (June CVE patches / Pixel) & Jelly Browser updates
    • 12/05 : Updated kernel vulnerabilities patches, improved Jelly Browser app
    • 02/05 : New release on Android 7.1.2_r8 sources (May patches / Pixel) & Camera2 fixes
    • 26/04 : New release with updated and unified AOSP 7.1.2 / LineageOS device sources
    • 13/03 : New release on Android 7.1.1_r25 sources (March CVE patches / Pixel)
    • 07/02 : New release on Android 7.1.1_r20 sources (February CVE patches / Pixel)
    • 29/01 : Updated device sources, fixed AOSP Recovery build
    • 07/01 : New release on Android 7.1.1_r9 sources (January CVE patches)
    • 30/12 : Updated device sources, restored Double power to Camera option
    • 13/12 : New release on Android 7.1.1_r6 sources
    • 09/12 : Updated device sources, tethering kernel support added for AOSP 7.1.1
    • 07/12 : New release on Android 7.1.1_r4 sources (About)
    • 25/11 : Some Pixel colours and round icons, Downloads play/pause, minor fixes (About)
    • 16/11 : Google SetupWizard fixes, minor improvements, dexopt disabled (About)
    • 12/11 : Original RIL, USSD fixed, cleanups, Android 7.1.0_r7 (About)
    • 29/10 : Sources improvements and working camcorder (About)
    • 24/10 : Updated release for Huashan, Android 7.1.0_r4 (About)
    • 17/10 : Updated release for Huashan, Android 7.0.0_r14 (About)
    • 28/08 : Initial release for Huashan, Android 7.0.0_r1

    Original AOSP 7.1 sources with following relevant additions
    • Huashan device tree, kernel and vendor
    • Bionic: Support for SHIMs (Camera)
    • Build: Backup tool full support (GApps)
    • NFC: Proper support & removed log spam
    • Toybox: Support for init_sony boot selection
    • AV: Camera support for Nougat
    • AV: Initial camcorder partial support
    • Camera2: Fixes for wrongly rotated photos and improvements
    • Screenshots: Fix MTP list updates
    • Settings: Remove Google system updates
    • UI: Add reboot option to power menu
    • UI: Various efficiency improvements and fixes
    • UI: Some Pixel designs like NavBar and colours
    • Downloads: Add the ability to Play/Pause
    • Telephony: Support for older RIL layers
    • Telephony: Provide default networks APNs from CM
    • Audio: 8960 adapted HAL and FM support
    • FM: Fully implemented with AOSP FM Radio
    • Music: Minor fix to permissions
    • Settings: Minor visual rendering improvements
    • Healthd: Support for Huashan offline charger
    • Core: Disabled flash_recovery service from AOSP
    • Sepolicies: Minimal changes and fully enforced ROM

    Current local manifest
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- https://android.googlesource.com/platform/manifest -->
    <manifest>
    
      <!-- See https://github.com/AdrianDC/aosp_development_sony8960 -->
    
    </manifest>
    50
    Huashan-Music-Lights-Effects.jpg

    Quite an important announcement today.

    Two years after my initial implementations of the Xperia SP (Huashan) LEDs hardware controllers
    (AS3665 and AS3677, unique to this device because of the LEDs bar), I present to you the project I have been wishing to complete since then.

    My open-source LibLights for Huashan's LEDs handles all normal lights (notifications and display backlight),
    and flashing lights (blink) with the advanced sequencer program from the AS3665.
    Unlike most devices, this sequencer is a programmable input for calculations,
    registers comparisons and outputs to each LED for current / brightness renderings.

    The final step that never worked up until now, knowing I had that sequencer written and detailed since 2 years,
    was the music lights effects done on the LEDs bar as Sony once did on Stock 4.3.
    As music lights effects are done through hardware and not software, meaning the audio directly controls
    the LED controller through a specific wire input, the music effects do not add performance lags or permanent update events.

    The missing part were the audio routes : connecting the real audio output to the AS3665 input.
    Two weeks ago I went back to Stock 4.3 and progressively got into it through newly built kernel, repacked original Stock image without signature,
    and step by step went into the audio routes to identify the required audio mixer configurations needed for my changes to work.

    Implemented for AOSP-based and LineageOS-based ROMs, my Music Lights Effects for Huashan are not bound to any ROM changes.
    That's the biggest point I worked on here when the technical side was ready, as I did not wish to add specific code to the framework related to only one device,
    and hence make it also fully compatible with my Android AOSP releases without porting our Lights improvements from LineageOS.

    Lights Effects are implemented in what we call DeviceSettings, just like done since more than a year for Ambient Display specific gestures.
    I provide an option to enable / disable the effects, a choice on the audio gain to adapt the AS3665 input to your wishes,
    an optional dependency on the device being awake (to allow the music effects even locked) and a final one to always use effects while awake.


    photo_2017-07-15_19-32-43_zpszqlqsglt.jpg~original
    photo_2017-07-15_19-32-57_zps0gobfz8g.jpg~original



    Preview and presentation video :



    There are four layers to my implementation :

    • LightsEffectsService (in DeviceSettings) listens media player events and triggers lights_effects through the "sys.lights_effects_value" property
    • init rules trigger lights_effects events on property "sys.lights_effects_gain" or sys.lights_effects_value" changes
    • Binary lights_effects is the new executable extension of my liblights and handles the audio configuration, audio routes and kernel music mode.
    • Kernel lights_effects is a new driver input that controls the AS3665, configures the music mode and properly blocks normal actions // keep them updated.

    All related sources changes are available under this topic : https://review.lineageos.org/#/q/topic:huashan_lights_effects


    Initial public release on AOSP July Release (including the new CVEs and updates) :

    photo_2017-07-15_19-32-51_zpseanbzqwf.jpg~original