[ROM][10.0][XZ2c] Pixel Experience for Xperia XZ2 compact (apollo) [AOSP][2020/02/21]

fastbooking

Senior Member
May 24, 2015
209
162
0
Toulouse


PixelExperience for the Sony Xperia XZ2 Compact apollo

What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)

Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device

Based on Android 10.0


Whats working?
Wifi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration


Known issues
Sony Open Devices bug tracker

DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website (Xperia XZ2 Compact Single Sim)
Download from Pixel Experience website (Xperia XZ2 Compact Dual Sim)

Flash instructions and special recovery coming on Monday 24/02/2020

Donate
Liked my work? Give me a beer

Translation
Help with project translation

Stay tuned
Our Telegram channel
Sony Specified Telegram channel
Our blog

 
Last edited:

fastbooking

Senior Member
May 24, 2015
209
162
0
Toulouse
Hello. What about Tama/Akari? Does it stable on XZ2? What about bugs or work/not work things? Sorry for bad eng.
Hey ! I think the thread you're searching is this one : https://forum.xda-developers.com/xp...om-pixel-experience-xperia-xz2-akari-t4054671

Anyway, to answer your question, it's pretty much stable, I have users testing it and it seem to be rock solid, I'm working hard with the Sony Open Devices on new features and great performance optimizations.
 

teostar

Senior Member
May 30, 2013
297
54
58
Flash instructions and special recovery coming on Monday 24/02/2020


[/LEFT]
Where is the instructions?
Noob to flashing on Xperia. Coming from oneplus where everything is pretty straightforward, I'm not very confident trying unlocking the bootloader on my xz2.

Also I've read conflicting accounts of drm issues if you try to go back stock. Is there any truth to this?
 
Mar 26, 2020
9
6
0
Does not work for me...

go check this website
I followed the instructions on the website but it does not work for me.
I get stuck in a bootloop where at first I see a message saying that the bootloader is onulocked and cannot verify the device, then the Sony logo for a few times.
After what I get a red warning saying that my device is corrupt and will poweroff in 5 seconds.

I used Kernel 4.14 v5a Tama binaries and tried with the Pixel Experience Plus build from March 30, 2020 and the normal Pixel Experience build from the same date.
My XZ2C is a Dual-SIM one, Revision 6.
I verified that I had the right build (H8324) and verified that I had correctly downloaded the files.
I tried flashing the binaries only on "oem" the first time and another time with "oem_a" + "oem_b".

Maybe I'm doing something wrong or I forgot to flash some file.
I'm worried about the "Invalid sparse file format at header magi" message, I don't know if it may somewhat be the issue.
(I am able to flash and boot from the latest stock ROM without any trouble)

Code:
>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [  0.005s]
writing 'vbmeta'...
OKAY [  0.003s]
finished. total time: 0.011s

>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (65536 KB)...
OKAY [  1.943s]
writing 'boot'...
OKAY [  0.376s]
finished. total time: 2.321s

>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (8192 KB)...
OKAY [  0.254s]
writing 'dtbo'...
OKAY [  0.050s]
finished. total time: 0.306s

>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [  0.249s]
sending sparse 'system' (759566 KB)...
OKAY [ 24.189s]
writing 'system'...
OKAY [  0.003s]
sending sparse 'system' (724540 KB)...
OKAY [ 23.036s]
writing 'system'...
OKAY [  0.002s]
sending sparse 'system' (738077 KB)...
OKAY [ 23.506s]
writing 'system'...
OKAY [  0.002s]
sending sparse 'system' (62664 KB)...
OKAY [145.908s]
writing 'system'...
OKAY [  0.003s]
finished. total time: 216.907s

>fastboot flash vendor vendor.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'vendor' (55600 KB)...
OKAY [  1.747s]
writing 'vendor'...
OKAY [  0.003s]
finished. total time: 1.755s

>fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_tama.img
target reported max download size of 805306368 bytes
sending 'oem' (320708 KB)...
OKAY [  9.513s]
writing 'oem'...
OKAY [  9.232s]
finished. total time: 18.748s
 

duke864

New member
Mar 7, 2006
3
0
0
Hi,

I flashed the binaries "SW_binaries_for_Xperia_Android_10.0.7.1_r1_v4c_tama" on oem_a and oem_b. This works fine.

Greets Duke
 
Mar 26, 2020
9
6
0
I flashed the binaries "SW_binaries_for_Xperia_Android_10.0.7.1_r1_v4c_tama" on oem_a and oem_b. This works fine.
Seems not to work even if I'm using this version of the binaries, I still have the same issue.
(tested with oem_a and oem_b with the binaries version you advised me and with the March 30, 2020 build of regular Pixel Experience, following the flashing instructions from the website)
There's definetly something that I'm either doing wrong, a file or step which is missing in my case.
I also heard about a bootloader bug or some kind of security, maybe it's messing up with my installation...
I would be glad to have a tutorial from someone who has succeeded with the latest version :)
 
Last edited:

logan123456

Member
Mar 21, 2020
34
1
8
Did you have this issue

Hi,

I flashed the binaries "SW_binaries_for_Xperia_Android_10.0.7.1_r1_v4c_tama" on oem_a and oem_b. This works fine.

Greets Duke
did you have any battery problems in pixel experience like not accurate battery percentage

---------- Post added at 04:01 AM ---------- Previous post was at 03:58 AM ----------

Seems not to work even if I'm using this version of the binaries, I still have the same issue.
(tested with oem_a and oem_b with the binaries version you advised me and with the March 30, 2020 build of regular Pixel Experience, following the flashing instructions from the website)
There's definetly something that I'm either doing wrong, a file or step which is missing in my case.
I also heard about a bootloader bug or some kind of security, maybe it's messing up with my installation...
I would be glad to have a tutorial from someone who has succeeded with the latest version :)
maybe try formatting your phone completely and try again

---------- Post added at 04:12 AM ---------- Previous post was at 04:01 AM ----------

I followed the instructions on the website but it does not work for me.
I get stuck in a bootloop where at first I see a message saying that the bootloader is onulocked and cannot verify the device, then the Sony logo for a few times.
After what I get a red warning saying that my device is corrupt and will poweroff in 5 seconds.

I used Kernel 4.14 v5a Tama binaries and tried with the Pixel Experience Plus build from March 30, 2020 and the normal Pixel Experience build from the same date.
My XZ2C is a Dual-SIM one, Revision 6.
I verified that I had the right build (H8324) and verified that I had correctly downloaded the files.
I tried flashing the binaries only on "oem" the first time and another time with "oem_a" + "oem_b".

Maybe I'm doing something wrong or I forgot to flash some file.
I'm worried about the "Invalid sparse file format at header magi" message, I don't know if it may somewhat be the issue.
(I am able to flash and boot from the latest stock ROM without any trouble)

Code:
>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [  0.005s]
writing 'vbmeta'...
OKAY [  0.003s]
finished. total time: 0.011s

>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (65536 KB)...
OKAY [  1.943s]
writing 'boot'...
OKAY [  0.376s]
finished. total time: 2.321s

>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (8192 KB)...
OKAY [  0.254s]
writing 'dtbo'...
OKAY [  0.050s]
finished. total time: 0.306s

>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [  0.249s]
sending sparse 'system' (759566 KB)...
OKAY [ 24.189s]
writing 'system'...
OKAY [  0.003s]
sending sparse 'system' (724540 KB)...
OKAY [ 23.036s]
writing 'system'...
OKAY [  0.002s]
sending sparse 'system' (738077 KB)...
OKAY [ 23.506s]
writing 'system'...
OKAY [  0.002s]
sending sparse 'system' (62664 KB)...
OKAY [145.908s]
writing 'system'...
OKAY [  0.003s]
finished. total time: 216.907s

>fastboot flash vendor vendor.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'vendor' (55600 KB)...
OKAY [  1.747s]
writing 'vendor'...
OKAY [  0.003s]
finished. total time: 1.755s

>fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_tama.img
target reported max download size of 805306368 bytes
sending 'oem' (320708 KB)...
OKAY [  9.513s]
writing 'oem'...
OKAY [  9.232s]
finished. total time: 18.748s
i am not sure if you are supposed flash it on both slots fastboot flash oem_a
fastboot flash oem_b
 
Mar 26, 2020
9
6
0
It works !

I finally managed to install the ROM yesterday using differents instructions.
Here is how I did it if you are struggling to install like me at the beginning (or maybe there was just a fix in between, I don't know).

Before doing anything, the usual, you might want to take some precautions: do backups and remove the SD card from your device before loosing anything. What follows is going to format your internal storage.
Please respond if anything is wrong in here of if you have some details to add.
My installation was done from Android 10 stock 52.1.A.0.618. You can install it from a program called "Emma" from Sony.

You will first need to extract "payload.bin" from the .zip ROM file you have downloaded (Pixel Experience).
You will then need to use a program called "payload dumper" to get the files you'll be installing with fastboot afterwards from the payload.bin you just extracted. (expect around 6GB of files)

You will also need to extract "SW_binaries.img" from the most recent binaries .zip, which you can download on Sony's website.

In your command prompt you will need to do the following:

Code:
> fastboot flash boot boot.img
> fastboot flash dtbo dtbo.img
> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
> fastboot flash system system.img
> fastboot flash vendor vendor.img
> fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
> fastboot flash oem_b SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
Some things to keep in mind and which I would have liked to be aware of :
If you can't use --disable-verity and/or --disable-verification, try to launch your terminal from the folder of your most recent platform tools. It seems like they don't exist in some adb installers.
Flashing the files to your phone may take a long while to start. Just be patient.
You may see a "Invalid sparse file format at header magi" message at some point. I am not sure what it means (tell me if you know) but I got it and my phone is working just fine right now.
If you see a Google logo after the Sony logo, it means you probably succeeded.
After installing, my phone bootlooped two times. It then showed me a menu where I could format some data. I did it and after that it took a while to boot the first time but finally worked.

Here are the builds I am currently testing on my Xperia XZ2 Compact (H8324 REV6):
PixelExperience_h8324-10.0-20200511-0435-OFFICIAL.zip
SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img

I will try to tell you about the bugs and issues I may face in the next few days, but right now the ROM is feeling way snappier than Sony's stock Android 10 ROM in my opinion and the animations are gorgeous.
 

Attachments

Last edited:

Longranger32

New member
Mar 30, 2020
2
0
0
I finally managed to install the ROM yesterday using differents instructions.
Here is how I did it if you are struggling to install like me at the beginning (or maybe there was just a fix in between, I don't know).

Before doing anything, the usual, you might want to take some precautions: do backups and remove the SD card from your device before loosing anything. What follows is going to format your internal storage.
Please respond if anything is wrong in here of if you have some details to add.
My installation was done from Android 10 stock 52.1.A.0.618. You can install it from a program called "Emma" from Sony.

You will first need to extract "payload.bin" from the .zip ROM file you have downloaded (Pixel Experience).
You will then need to use a program called "payload dumper" to get the files you'll be installing with fastboot afterwards from the payload.bin you just extracted. (expect around 6GB of files)

You will also need to extract "SW_binaries.img" from the most recent binaries .zip, which you can download on Sony's website.

In your command prompt you will need to do the following:

Code:
> fastboot flash boot boot.img
> fastboot flash dtbo dtbo.img
> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
> fastboot flash system system.img
> fastboot flash vendor vendor.img
> fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
> fastboot flash oem_b SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
Some things to keep in mind and which I would have liked to be aware of :
If you can't use --disable-verity and/or --disable-verification, try to launch your terminal from the folder of your most recent platform tools. It seems like they don't exist in some adb installers.
Flashing the files to your phone may take a long while to start. Just be patient.
You may see a "Invalid sparse file format at header magi" message at some point. I am not sure what it means (tell me if you know) but I got it and my phone is working just fine right now.
If you see a Google logo after the Sony logo, it means you probably succeeded.
After installing, my phone bootlooped two times. It then showed me a menu where I could format some data. I did it and after that it took a while to boot the first time but finally worked.

Here are the builds I am currently testing on my Xperia XZ2 Compact (H8324 REV6):
PixelExperience_h8324-10.0-20200511-0435-OFFICIAL.zip
SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img

I will try to tell you about the bugs and issues I may face in the next few days, but right now the ROM is feeling way snappier than Sony's stock Android 10 ROM in my opinion and the animations are gorgeous.
please give the review about the performance for gaming use
i would like to change to use PE but still not sure if this form can significantly boost the performance on xz2c for gaming than the stock rom official
because since the android 10 on official stock rom, i feel it drop down the performance for gaming. it makes me struggle alot of time
 
Mar 26, 2020
9
6
0
Gaming performance

3D performance:
I used 3D Mark Sling Shot extreme in the hope that you will find what performance you can expect by running this ROM and binaries:
- PixelExperience_h8324-10.0-20200511-0435-OFFICIAL
- SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama

Stock Android for comparison: https://benchmarks.ul.com/en/hardware/phone/Sony+Xperia+XZ2+Compact+review
(You can test your device if you have stock Android to compare the results)
The scores presented here are averaged from 5 runs and are pretty much the same as what is in the database. There should not be a huge performance difference in games.

OpenGL ES 3.1:
Overall: 4,167.4 (~1% lower)
Graphics: 5,125 (=)
Physics: 2,522.6 (-24%)

Vulkan:
Overall: 3,973.2 (=)
Graphics: 4,664 (-5%)
Physics: 2,620 (+11%)

Detailled scores for the 5 runs:

Run 01:
Open GL ES 3.1
Overall score: 4,161
Graphics score: 5,149
Physics score: 2,490

Vulkan
Overall score 4,047
Graphics score: 4,664
Physics score: 2,767
----------
Run 02:
Open GL ES 3.1
Overall score: 4,250
Graphics score: 5,124
Physics score: 2,661

Vulkan
Overall score: 4,018
Graphics score: 4,668
Physics score: 2,701
----------
Run 03:
Open GL ES 3.1
Overall score: 4,093
Graphics score: 5,120
Physics score: 2,404

Vulkan
Overall score: 3,968
Graphics score: 4,679
Physics score: 2,591
----------
Run 04:
Open GL ES 3.1
Overall score: 4,094
Graphics score: 5,107
Physics score: 2,417

Vulkan
Overall score: 3,851
Graphics score: 4,657
Physics score: 2,398
----------
Run 05:
Open GL ES 3.1
Overall score: 4,239
Graphics score: 5,125
Physics score: 2,641

Vulkan
Overall score: 3,980
Graphics score: 4,652
Physics score: 2,643