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

Search This thread

fastbooking

Senior Member
May 24, 2015
231
164
Toulouse

GtwTyCR.png

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
231
164
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
327
57
Sony Xperia 5 III
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?
 

logan123456

Member
Mar 21, 2020
40
3
Not Good

Doesnt charge properly and the camera takes pink photos
Which kernel would you recommend for this rom
 
Mar 26, 2020
9
6
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
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
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
40
3
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
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

  • Screenshot_20200525-114429.png
    Screenshot_20200525-114429.png
    131.7 KB · Views: 286
  • Screenshot_20200525-114833.png
    Screenshot_20200525-114833.png
    178.4 KB · Views: 283
Last edited:

Longranger32

New member
Mar 30, 2020
2
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
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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6

    GtwTyCR.png

    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

    3
    Camera, video recording and related

    As of Binaries v7:

    Stills:
    RAW (.dng) support for both back and front cameras.

    Back camera:
    Definition is different from stock and varies depending on the photo mode:
    17.1Mpx (5,472 x 3,104, 16:9) in RAW (.dng) (The number of pixels with .dng is not shown the same in Google Photos and Image Glass)
    15.9Mpx (5,312 x 2,988, 16:9) in JPEG mode

    It is not the 19.1Mpx (5,056 x 3,792, 4:3) maximal stock definition.
    From my searches, the IMX400 sensor is natively 5,520 x 3,840 (19.2 Mpx), but it is a multi-aspect sensor.
    The maximum definition in 4:3 mode is 5,056 x 3,792 (19Mpx) while it is 5,504 x 3,096 (17Mpx) in 16:9 mode.
    So maybe only the 4:3 mode of the sensor neeeds to be either implemented or enabled since basically every pixel in 16:9 mode is usable on RAW.
    It is not a killer for me since I now have .dng that is way better for me than the JPEG I used to edit with in stock Android, but it is something you should be aware of.

    Front camera:
    Not much to say, except that it has the exact same definition as stock (1944 x 2592, 4:3). It can also shoot in RAW and all the pixels are usable in both JPEG or DNG mode.

    ISO range (back camera only):
    Not the same as what you used to have in stock. You used to have 40 to 3,200 ISO accessible in stock Android.
    Now, you have 100 to 12,000 ISO.

    Auto-focus (back camera only):
    You will miss the nice auto-focus you had in stock Android.
    The autofocus is dumb and may struggle even on non-moving objects sometimes. It can definetly be a handicap when taking photos everyday.
    It is also much slower than stock, but maybe because of other limitations in the camera implementation.

    Exposure/Shutter (back camera only):
    The shutter does not set by default to 1/60s or 1/50, nor even 1/30s which are acceptable to shoot photos and video (to some extent), but will go down to 1/15s most of the time in auto mode in case of "low light".
    The exposure changes and transitions faster compared to stock or fades less.
    The shutter is not working optimally, because of some sort of camera limitation.

    Flash:
    The light (torch/flash) is bright as hell compared to what it used to be on stock Android.
    You now have a nice torch to use everyday with its good brightness.
    It seems to heat up pretty fast though and must use a lot more power, so I would not use it for a large amounts of time.

    Filtering:
    There are now some more filtering options. Whether you like them or not will depend or your taste, but you have a bit more options.

    White balance:
    Some more options and presets too.

    Video:
    DO NOT LEAVE STOCK ANDROID YET IF VIDEO IS IMPORTANT TO YOU

    The XZ2C camera in video has a lot of potential and I have been able to record some gorgeous images in a lot of scenarios.
    You can disable denoiser and most other filterings to preserve detail or just keep the denoiser to get less compression artefacting and a better image overall in low light scenarios. You can get the encoder to go as high as 120Mbit/s HEVC in 4K and get a pretty good looking image at the end.

    You could record at a steady 30 Frames per second in 4K with fixed exposure/ISO in stock Android, no frame drop whatsoever. I think this is the most important thing.
    But what you get here is 15/20 Frames per second no matter what definition or frame rate you choose, even in manual mode (fixed exposure/ISO).
    Because of this and the other issues (mainly the autofocus and exposure), I think that it is a sensor compatibility issue rather than an encoder issue.

    The camera image preview is limited to 15/20FPS in both photo and video mode, which could explain a lot of things:
    There has to be a link between the preview frame rate, the default 1/15s shutter, in part why the autofocus is so slow, and the fact that the camera cannot record video higher than 15/20FPS.
    The sensor refresh rate or some sensor setting absolutely neeeds to be changed in order to get at least 30 frames per second.
    It does not matter to me at all if video is a little bit cropped.
    I usually crop my videos or zoom a tiny bit at the end or when recording anyways. 30FPS is more important to me right now.
    I even wish to have 60FPS 4K video too but I don't know if it is possible to get it with this sensor. Maybe 60FPS 1440p is doable if 4K is not.
    There is no slow-motion video yet (240FPS 1080p, 960FPS 720p/1080p) but i wish to see it too someday. Being able to get working slow-motion without filtering and a higher bitrate than stock would look gorgeous.
    1
    Any screenshots or install instructions? :)
    1
    Let's talk about the battery...

    like severe battery drain
    if there was a problem how did you fix it
    Oh yeah, that kind of battery percentage bugs. I have them too and it remembers me a lot of the Galaxy Trend I had 6 years back.
    There is definetly some weird behaviour going on here. The battery meter stays flat for large amounts of time before finally dropping immediately at some point. (see screenshots)
    It can also shutdown itself during night because it thinks the battery is dead. (airplane mode and with battery saver)
    I did not see an improvement over Stock Android 10 yet since it slowly drains battery at all times, even during night time, in airplane mode and with battery saver ON.
    You can still use your phone for a decent amount of time though and use it like you would otherwise, but you will need to have a power bank or a plug near you if you don't want too much issues.

    [v7 EDIT]:
    The issue is still here. I also found out in between that the voltage meter actually does not correspond to the charge percentage. The voltage meter seems to be accurate but in that case, the interpretation of that voltage is wrong or buggy, which leads to percentage bugs. Battery percentage when charging is very weird. You may see a super duper fast charging on a slow USB port (500mA) because it will reach the percentage it should be having at that voltage despite almost not charging in a few minutes.

    If you want to know your "true" charge level or, like me, not "overcharge" your phone, use HWMonitor or any other app that will tell you the battery voltage. Do not even try and just guess by looking at what the battery curve looks like. It does not mean anything since the numbers are somewhat random.
    1
    Audio:

    As of:
    - PixelExperience_h8324-10.0-20200511-0435-OFFICIAL
    - SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama

    Music playback:
    May be impossible if your phone falls asleep. It will start by struggling, leading the music to stop at some point.
    Plays back normally again if your wake it/turn the screen on soon enough; otherwise the music is paused and your device may be hang for a bit.
    The issue persists after rebooting.

    How to reproduce it: play music and put your phone to sleep manually, or let it sleep by itself. It will occur in a few seconds in most cases but sometimes it won't occur if listening on the phone's speaker.
    It actually mostly concerns Bluetooth audio playback. You won't be able to listen to music from your phone in your car or with your wireless headphones in almost every case.

    Speakers:
    Speakers saturate or get distorted easily.
    If you try to play music in the background trough the Newpipe YouTube client, it seems to have the same issues as Bluetooth playback.
    Maybe some apps have a harder time playing back audio in sleep mode than others.

    USB Audio:
    I did not test USB Audio yet and am waiting for some device to test it.

    [v8 EDIT] : Bluetooth Audio is now working great and AptX works. You can playback audio in background without issues now. The speakers seems to have been improved too.