[EOL][SODP][ROM][OmniROM][XZ2, XZ2C, XZ3] OmniROM 9.0.0_r47 [UNofficial] [Stable]

[MartinX3]

The 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!

• Official site
• Unofficial site

#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 OmniROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)

This ROM build will always mainly based on OmniROM Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level and the OEM binary got fully implemented, if there is no need for a critical hotfix.

Preview Picures:

• https://forum.xda-developers.com/showpost.php?p=78856251&postcount=2
• https://forum.xda-developers.com/showpost.php?p=78856492&postcount=4
• https://forum.xda-developers.com/showpost.php?p=79450402&postcount=443
• https://forum.xda-developers.com/showpost.php?p=79460796&postcount=456

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) Bootloader issue needs to get fixed to make custom roms bootable on slot B.
• fastboot & adb
  • https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
  • https://wiki.lineageos.org/adb_fastboot_guide.html
  • https://developer.android.com/studio/releases/platform-tools
• 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/

for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release

Known Bugs:

• Camera is under development.
• [TAMA] [AKATSUKI] [CRITICAL??] Speakers clipping and distortion

Bugtracker:

• SODP Bugtracker -> If you think the problem is in SODP
• OmniROM Bugtracker -> If you think the problem is in OmniROM
• My Bugtracker -> If you think the problem is in my implementation

Bugreport:

• A bugreport needs logcat, dmesg and a way to reproduce the issue.
• 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
• @oshmoun for his device tree portings
• @dhacke thank your for providing a download server
• And the OmniROM developers!
• And many thanks to the few donators!

A telegram group for technical SODP stuff:

Sony Open Devices Project Chat for devs

https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub

t.me

XDA:DevDB Information
OmniROM, ROM for the Xperia XZ2

Contributors
MartinX3, Sony, oshmoun, OmniROM
Source Code: https://github.com/omnirom/

ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: OmniROM

Version Information
Status: No Longer Updated
Current Stable Version: 9
Stable Release Date: 2019-08-10

Created 2019-02-07
Last Updated 2020-10-23

 

[MartinX3]

Download & Installation

Download:

• https://androidfilehost.com/?w=devices&uid=11410963190603893035
• https://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
  • Unzip the *.gz files with 7-zip or Linux.
• GCAM (Need GAPPS, but improves the camera a lot):
  • I usually use the newest Arnova's GCAM

Installation:

1. fastboot flash boot boot.img
2. fastboot flash dtbo dtbo.img
3. fastboot flash vbmeta vbmeta.img
4. fastboot flash system system.img
5. fastboot flash vendor vendor.img
6. fastboot flash oem oem_*.img
7. (Optional, but mandatory on first boot) fastboot flash userdata userdata.img -> will factory reset the device.
8. (Mandatory on dual sim devices) Dual Sim Patcher
9. (Optional) https://opengapps.org/ or MicroG

In case of touch issues on the XZ2 compact:

1. Download (try the v10 zip first, if it doesn't work try v9 or v8)
2. fastboot flash boot boot.img
3. fastboot flash vendor vendor.img
4. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. (Mandatory on dual sim devices) Dual Sim Patcher
6. If your system apps did loose their permissions (sadly that happens sometime after flashing a boot.img again -> AOSP bug which is maybe fixed in 10.0)
   1. fastboot flash userdata userdata.img (Flashing the boot.img may
   2. (Optional) https://opengapps.org/ or MicroG

 

[MartinX3]

News

05.01.2020

i thought pushing a maintenance update would be a good idea.
Sadly it wasn't achievable.
I tried to simply rebuild the old sodp sync with the newest omnirom, also synced the newest sodp stuff wit the newest omnirom.
But that every time resulted into
1. Installing gapps on a fresh system let the device crash into twrp with the message "set_policy_failed:/data/cache/"
2. Upgrading from the previous version resulted into "no web views detected". The webview is needed for some apps to render their content. Without that they would simply crash.
Regardless if the gapps, aosp or bromite webview was installed, none was listed and the logcat throws errors.
3. The audio doesn't route anymore to a connected usb audio 3.5mm adapter.
4. There may be more bugs, but i am too frustrated to with the already occurring bugs and invested hours/days.

Lets look optimistically into the future of android 10.0, kernel 4.14 and which custom roms can be build on it.

12.10.2019

https://gerrit.omnirom.org/#/q/topic:asb_2019-09+(status:open+or+status:merged)
https://gerrit.omnirom.org/#/q/topic:asb_2019-10+(status:open+or+status:merged)

omnirom 9 may be deprecated, but it seems that they backport security fixes.
Soooo, we get still security updates.

On the other side i got insulted (called a stupid idiot), warned, kicked and banned at once for asking about the security commits and saying that the insulter has a low emphatic intelligence.
I look if i will continue distributing stuff for this toxic community administration.

04.10.2019

it's official announced by the omnirom boss.
Omnirom 9 reached end of life and is now deprecated.
Omnirom 10 for xz2, xz2c, xz3 will come after the sony aosp builds with q and kernel 4.14 are stable enough.

07.09.2019

dear xz2 compact owners with not working touch.
It seems that we fixed the problem
https://github.com/sonyxperiadev/bug_tracker/issues/351
the code needs to to get refactored and merged into sodp, before i can release new builds.
But anyway, i'm on vacation & studying for exams, so don't expect builds earlier than end of september/october.

To test it
apollo_v8.zip

fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

28.08.2019

someone may have seen that in september comes a sodp switch to
1. Android 10 (queen cake)
2. Kernel 4.14 (using 4.9 at the moment)
i won't switch asap to the new stuff and wait until it proofs enough stability to act as a daily driver.
Maybe it is stable directly right release (i don't think it) or it may take ~1-5 months.
(and i don't know how fast omnirom switches to q.)

26.08.2019

september no new release
reason -> vacation + university exams

11.08.2019

omnirom 9.0.0_r47
august security patch
new glove mode

12.07.2019

omnirom 9.0.0_r44.
July security patch.

11.06.2019

omnirom 9.0.0_r40.
June security patch.

31.05.2019

omnirom with may 2019 security patch level.
Newer, faster, more stable, oemv9 support.
Also i'll only push files to the single sim device section.
The dual sim device section will get a file with a hint to look into the single sim section.
There is also the twrp dual sim patcher. Without it the single sim firmware won't work on a dual sim phone.
That'll save bandwith and server storage.

I linked the patcher on the first page, but use my uploaded v4alpha patcher instead.
It contains my complete overhaul of the patcher and the current v3 in the xda thread doesn't work on tama.
I already made a pull request and the author just needs to merge my changes.
https://git.ix5.org/felix/dualsim-patcher/pulls/3

19.05.2019

reworked the thread page

14.05.2019

http://www.dhsfileserver.de/ftp/martinx3/ thank you @dhacke for the second download server

02.05.2019

i heard that oemv9 will support the hexagon snapdragon processor.
- longer battery life
- faster device
- real hdr plus for our tama camera

22.04.2019

oemv8 (camera) support!
Removed buildin twrp.
Twrp needs to get build as -eng, not as -userdebug.
And we got now a working "fastboot boot twrp.img".

22.04.2019

attached oemv8 images at the post
https://forum.xda-developers.com/showpost.php?p=78856251&postcount=2

it is only a current snapshot of the camera development.
Expect further improvements with the upcoming oem blobs.

Ps: Oemv8 compatible builds are getting compiled after i released the oemv8 sonyaosp builds.

07.04.2019

bug & feature tracker
https://github.com/martinx3sandroiddevelopment/bug_tracker

02.04.2019

omnirom 9.0.0_35.
April security patch.
Needs oemv7 blobs.
Improved stability and fixed bugs.
Now with integrated twrp.
Hopefully fixed ril crash with manually merged upstream code from sony aosp sodp.

31.03.2019

omnirom 9.0.0_34.
March security patch.
Needs oemv7 blobs.
Improved stability and fixed bugs.
Now with integrated twrp.

22.02.2019

updated the rom for the sony oem v6 with updated camera hal!
(beta release, has still a crash with exposure, they are not finished with their work. Don't expect stock like photos "now".)

10.02.2019

february security update release.

07.02.2019

finaly xda fixed their blocking website bug and i was able to create this new xdadev project.
First release from 01. February 2019

 

[MartinX3]

Screenshots

Screenshots

 

[twistedddx]

Always great devoted work from you!

You have a small typo in your post:
The stock firmware updates doesn't not update your "android"

Should read
The stock firmware updates doesn't just update your "android"

 

[MartinX3]

Always great devoted work from you!

You have a small typo in your post:
The stock firmware updates doesn't not update your "android"

Should read
The stock firmware updates doesn't just update your "android"

xD Thank you

 

[niaboc79]

Great job [emoji6]

How is battery life?

Any lag after a few days if use?

Envoyé de mon H8266 en utilisant Tapatalk

 

[MartinX3]

Great job [emoji6]

How is battery life?

Any lag after a few days if use?

Envoyé de mon H8266 en utilisant Tapatalk

Thank you

The only thing I see so far is the missing camera.

And the phone uses a bit more energy I thing, but I need to test that.

 

[MartinX3]

Together with the sony team we did a great step.
Now we support the exFAT file system on sdcards.

(There still needs work to be done in the sepolicy, will take a bit before code gets merged for my next release build)

PS:
ext4 support for sdcards, too.

 

[Haldi4803]

Hooo i see interactive governor in the screenshots?
AOSP does not use EAS or does only OMNI rom not use EAS?

 

[MartinX3]

Hooo i see interactive governor in the screenshots?
AOSP does not use EAS or does only OMNI rom not use EAS?

erm, maybe the added EAS stuff last month. Hmm.
I asked some devs now.

Edit:
Interactive is used.
And there is no EAS.

 

[MartinX3]

Deleted

 

[xFirefly93]

erm, maybe the added EAS stuff last month. Hmm.
I asked some devs now.

Edit:
Interactive is used.
And there is no EAS.

So old HMP is used by Sony for their SD845 devices, or is this "workaround" only applied upon their official shared AOSP sources and blobs?

Could in that case explain the increased power consumption, becausr HMP is a leeching sucker compared to Energy Aware Scheduling / EAS.

 

[MartinX3]

So old HMP is used by Sony for their SD845 devices, or is this "workaround" only applied upon their official shared AOSP sources and blobs?

Could in that case explain the increased power consumption, becausr HMP is a leeching sucker compared to Energy Aware Scheduling / EAS.

I ask them if there are EAS plans.

Edit:
No plans, seems they don't like it.

Edit1:
Seems that with the other stuff in the kernel the EAS would lead into a battery drain.
And that the AOSP is battery optimized without it.

Ediit2:
They don't hate EAS.
It was just a decision at a time where other parameters lead to this decision.
Maybe they switch to EAS in the future.

Edit3:
EAM Energy Models are needed.
And because it's very hard to get one EAS may never get implemented.

 

[dhacke]

@MartinX3

When do you plan to release the Omnirom build with the february 2019 patch?

 

[MartinX3]

@MartinX3

When do you plan to release the Omnirom build with the february 2019 patch?

The February patch level required a rebuild of my build cache.
It's at 20% since an hour.
I am sure I can upload the stuff this evening.

 

[dhacke]

The February patch level required a rebuild of my build cache.
It's at 20% since an hour.
I am sure I can upload the stuff this evening.

Thx for the info.

 

[MartinX3]

Thx for the info.

You're welcome. Feel free to ask.

 

[dhacke]

@MartinX3

Besides of the security patch are there any other fixes in the new upcoming build?

 

[MartinX3]

@MartinX3

Besides of the security patch are there any other fixes in the new upcoming build?

It has a build in changelog app.