[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 10.0.0 [STABLE]
- Thread starter MartinX3
- Start date
Or just use twrp [emoji14]thank u, i found my problem and test other rom.
Happy~~~~
Hello guys ! Half-newbie here!
I need to knew which gapps should I flash for XZ3 (H8416). Arm? Arm64? X86? X86_64?? And which size preferably?
Edit : found it ! Arm64
Please excuse my newbieness but TWRP sodp or TWRP stock. And how do i root ? Magisk or SuperSU ?
I need to knew which gapps should I flash for XZ3 (H8416). Arm? Arm64? X86? X86_64?? And which size preferably?
Edit : found it ! Arm64
Please excuse my newbieness but TWRP sodp or TWRP stock. And how do i root ? Magisk or SuperSU ?
Last edited:
@MartinX3
Hello I've just installed the rom (a looonng story, but I succeeded) , I do have network signal but no internet... I have installed the right internet parameters provided by the network provider
What should I do to fix this ? It should have displayed LTE or H+ next to signal bar but nothing
Merry Xmas by the way
Hello I've just installed the rom (a looonng story, but I succeeded) , I do have network signal but no internet... I have installed the right internet parameters provided by the network provider
What should I do to fix this ? It should have displayed LTE or H+ next to signal bar but nothing
Merry Xmas by the way
A hint is in the thread title.
Magisk.
Please try AOSP 11.
Or maybe you got some issues with your provider.
I switched to Lineage OS 17.1. Maybe the issue was the Sony Binaries I flashed (I flashed the last version).
But I was wondering how could I get rid of the glitches appearing here and there while locking the screen or watching videos on Youtube, or swiping pictures on Google Photos...
Graphic drivers compatibility issues ???
It happens on all the roms I tried (PixelExperience 10, Sony AOSP 10, and Lineage 17.1 android 10)
And by the way, last time, I tried Magisk, It messed up with the boot (bootloop) so please tell if I have to do anything else after flashing Magisk via TWRP...
Thanks in advance.
Sadly I can't help you with this
I don't get tearing or bootloops with magisk after following my instructions on my XZ2.
Maybe there is an issue ticket on github about the tearing
It's not screen tearing. There are stripes of screen noise appearing randomly when the system squeezes the GPU (video playback, games., Etc..). I've never seen them on Stock Rom, even when playing heavy games. Now just a simple swiping image is enough to cause that. Maybe my device is getting old...
If it happen in stock lineageOS or stock ROM out of nowhere, then it might be.
Or you just achieved to trigger a bug I'm unable to.
But maybe you'll find a matching issue ticket on the issue thread linked on the first page here.
And the development continues in the AOSP 11 thread.
Last edited:
I installed it according to the instructions without recovery. I launched it and it didn’t turn on. I downloaded Tama for Android 10 for September. I installed it. It started, but after a couple of minutes the robots itself turns off and goes into recovery to reset the data. And so on all the time.
Similar threads
- Poll
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
16https://developer.sony.com/develop/open-devices/latest-updates
OEMv2 got released
Added camera, sound calibration, sensors. Also fixed keymaster and Adreno.
The ROM also got stability updates and enhancements.
The next release I will publish will contain a better camera and fixes against the sound issues (compared to my android 9.0 builds with kernel 4.9).
The XZ2, XZ2c & XZ3 are on a good way thanks to the Sony Open Devices Developers (Volunteers and Sony Employees).15The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Code:#include <std_disclaimer.h> /* * * We are 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. * */
This is the AOSP ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
- Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime)
- fastboot & adb
- Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
- For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
Bugtracker:
- SODP Bugtracker -> If you think the problem is in SODP
- My Bugtracker -> If you think the problem is in my implementation
Bugreport:
- A bugreport needs
and a way to reproduce the issue.Code:
logcat -b all - A crash of the system requires the content of the /sys/fs/pstore folder as bug report
- Be aware that a second reboot erases this folder
- A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
- You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
- To rescue a not responding phone:
- VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
- VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
- VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
- @jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
- @dhacke for providing a download server
- @Raphos for the initial installation manual without a recovery system, after I switched to OTA zips.
- @kgvarunkanth for the jenkins build server
- And many thanks to the few donators!
A telegram group for technical SODP stuff:
XDA:DevDB Information
AOSP, ROM for the Xperia XZ2
Contributors
MartinX3, Sony, SonyAOSP
Source Code: https://github.com/sonyxperiadev
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 10
Created 2019-09-29
Last Updated 2020-10-239Ok, now using it as my daily driver, as far no issues. Lacking suport for night light mode aka yellow screen and ambient display on proximity and accelerometer. Also no Widevine support then no Netflix., the only drawback for me. And GPay do not pass the security test, supposedly due to selinux or something else.
LDAC is not working correctly, stuttering audio on every single codec except SBC at 44.1 KHz. KCal is broken.
Installation procedure:
- Install the ROM as per OP's guide
- Install Magisk Manager 7.4.0
- Copy boot.img to the device via mtp at e.g. /sdcard or /sdcard/downloads
- Install magisk via magisk manager, chose Manually patch image and select the previously copied boot.img
- The resulted magisk-patched.img has to be copied back to pc
- flash magisk-patched.img via fastboot
- download lastest opengapps beta nano for android 10 (nothing more than 250 Mb)
- Copy opengapps.zip to the device via mtp
- Install FK Kernel Manager
- In FK chose Flasher, uncheck the Reboot after flashing
- Chose Manual Flasher and pick your opengapps.zip
- Once flashed go to System settings - System - Reset - Factory reset aka wype everything
- Wait for the first boot and perform a normal setup with your google account
- Profit!
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
https://sourceforge.net/projects/op...ps-arm64-10.0-nano-20191209-BETA.zip/download
https://play.google.com/store/apps/details?id=com.franco.kernel
Good luck and keep looking at what you're doing, be ready to use Emma flasher and got your data lost.
Disclaimer: everything at your own risk7Download & Installation
Download ROM:
Download Drivers:
- OEM (Tama) binaries
- Please use the the OEM build which came before my last release, unless otherwise written.
GCAM Camera App:
- Suggested GCams But GCAM's aren't usable at the moment until a camera hardware resource budget bug got fixed in the OEM binary blob.
Installation with a recovery:
- fastboot flash oem_a oem_*.img
- fastboot flash oem_b oem_*.img
- Flash the ROM in a recovery
- Reboot into recovery just to make sure you're on the new slot
- OpenGapps
- Dual Sim Patcher
- (In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
- Extract the payload.bin from the .zip file
- Extract the .img files with the Playload Dumper
- fastboot flash boot_a boot.img
- fastboot flash boot_b boot.img
- fastboot flash dtbo_a dtbo.img
- fastboot flash dtbo_b dtbo.img
- fastboot flash system_a system.img
- fastboot flash system_b system.img
- fastboot flash vbmeta_a vbmeta.img
- fastboot flash vbmeta_b vbmeta.img
- fastboot flash vendor_a vendor.img
- fastboot flash vendor_b vendor.img
- fastboot -w (Wipes your internal storage and the userdata)
- Continue with the normal installation
5Is there changelog for the new oem?
Yes, the new OEMv2c fixes the incall audio
Currently I'm compiling the new release with every fix and optimization in the open source part made since last release + dezember security patch level.
