• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 10.0.0 [STABLE]

Should I continue this project?

  • Yes, for the XZ2.

    Votes: 60 31.7%
  • Yes, for the XZ2C.

    Votes: 65 34.4%
  • Yes, for the XZ3.

    Votes: 62 32.8%
  • No.

    Votes: 2 1.1%

  • Total voters
    189
Search This thread

MartinX3

Recognized Contributor
Sep 14, 2014
5,850
2,912
Mars
martinx3.github.io
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!


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:
jerpelea said:
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

Bugtracker:

Bugreport:
  • A bugreport needs
    Code:
    logcat -b all
    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
  • @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-23
 
Last edited:

MartinX3

Recognized Contributor
Sep 14, 2014
5,850
2,912
Mars
martinx3.github.io
Download & 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:
  1. fastboot flash oem_a oem_*.img
  2. fastboot flash oem_b oem_*.img
  3. Flash the ROM in a recovery
  4. Reboot into recovery just to make sure you're on the new slot
  5. OpenGapps
  6. Dual Sim Patcher
  7. (In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Flash the ROM without a recovery:
  1. Extract the payload.bin from the .zip file
  2. Extract the .img files with the Playload Dumper
  3. fastboot flash boot_a boot.img
  4. fastboot flash boot_b boot.img
  5. fastboot flash dtbo_a dtbo.img
  6. fastboot flash dtbo_b dtbo.img
  7. fastboot flash system_a system.img
  8. fastboot flash system_b system.img
  9. fastboot flash vbmeta_a vbmeta.img
  10. fastboot flash vbmeta_b vbmeta.img
  11. fastboot flash vendor_a vendor.img
  12. fastboot flash vendor_b vendor.img
  13. fastboot -w (Wipes your internal storage and the userdata)
  14. Continue with the normal installation
 
Last edited:

MartinX3

Recognized Contributor
Sep 14, 2014
5,850
2,912
Mars
martinx3.github.io
News

01.10.2020
i end of life this project now
android 10.0.0_r41 (august security patch level) was the latest by google before android 11 got released.

18.08.2020
now android 10.0.0_r41
august security patch level
and any other sodp open source change since my last build

14.07.2020
now android 10.0.0_r40
july security patch level
oemv9 support
and any other sodp open source change since my last build


20.06.2020
oemv8 support
and any other sodp open source change since my last build

06.06.2020
now android 10.0.0_r39
june security patch level
oemv7 support
charger, battery, sleep fixes
and any other sodp open source change since my last build

11.05.2020
now android 10.0.0_r34
may security patch level
oemv6 support
and any other sodp open source change since my last build

ps: Camera is work in progress.

14.04.2020
now android 10.0.0_r33
april security patch level
oemv5 support
and any other sodp open source change since my last build

switched to:
  • zip files to flash
  • dual sim patcher instead of dual sim rom files
ps: Camera is work in progress.

18.03.2020
now android 10.0.0_r30
march security patch level
and any other sodp open source change since my last build

ps: Camera is work in progress.

01.03.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.


now android 10.0.0_r26
february security patch level
oemv4 -> camera & other improvements
and any other sodp open source change since my last build

ps: Camera is work in progress.

25.02.2020
need to take down the builds.
Oemv4 which comes tomorrow got some additional last minute changes today which needs a new rom compilation.

24.02.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.


now android 10.0.0_r26
febraury security patch level
oemv4 -> camera & volte & other improvements
and an other sodp open source change since my last build

ps: Camera is work in progress.
Oemv4 maybe comes tomorrow.

18.01.2020
now android 10.0.0_r21
january security patch level
oemv3 -> initial volte/vowifi support and better camera
and an other sodp open source change since my last build

and i renamed the thread from alpha to beta and removed the unstable marking.
(it seems the rom was already stable since the last build in december)

thanks going to the entire sony open devices team containing volunteers and sony employees.
Everyone who want to help with coding can use the link in the first post on the first page)

ps: Camera is work in progress.

11.12.2019
rebuild after the new oem v2c release with the newest code changes and december security update.
Oem change -> "fixed incall sound"

i switched now back to self build kernels instead of using the prebuild ones to include the newest changes.
(since the oem releases in the beginning of development are faster than usual to test, report, debug the update interval of the prebuild kernels is too slow; of course this will change after we move back to monthly oem updates)

looks like with oemv3a we will move into the beta status.
(and i think then i will remove the unstable marker. It is stable, too at the moment, but i don't want to remove the marker too early)

thanks going to the entire sony open devices team containing volunteers and sony employees.
Everyone who want to help with coding can use the link in the first post on the first page)

ps: Camera is work in progress.

30.11.2019
rebuild after the new oem v2b release with the newest code changes.
Adsp update and keymaster update in the closed source binaries.

Now the work in progress camera driver is usable, also the encryption, decryption and the lockscreen usage.
The xz3 should now be bootable, too.

Instead of building the kernel myself, i use now the prebuild and tested kernels by sodp.
The current one is 5 days old and doesn't include the newest stabilization update for the smd845, which is under internal testing.
But it is already pretested. :d

ps: Camera is work in progress.

24.11.2019
rebuild after the new oem v2a release with the newest code changes and android 10.0.0_r10 (november security level).
Providing now single and dual sim builds
many stability updates
added camera, sound calibration, sensors. Also fixed keymaster and adreno.
And other fixes and optimizations.

Ps: Camera is work in progress. Now since it is compatible with kernel 4.14 the further updates/upgrades will be made here.
Aaaaaand we (will) support 120fps and hdr out of the box.

04.10.2019
rebuild after the new oem v1c release with the newest code changes.

03.10.2019
rebuild after the new oem v1b release with the newest code changes.
Boot to android is possible since oemv1b.

02.10.2019
with the new oem v1b blobs the tama devices are bootable to android.

29.09.2019
first alpha rom for the xz2, xz2 compact, xz3.
It will be stuck at sony logo and reveal a full adb shell.
It is single sim, since having a working mobile network is not a priority right now. (too unstable rom).
 
Last edited:

ozamyatin

Member
Oct 23, 2016
37
23
Moscow
There has been an update of SW binaries today

UPDATE1
Managed to boot android 10 with SW binaries ver. 1b from 1st October after flashing vbmeta from twrp section with command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. Device: Dualsim akatsuki 9436

UPDATE2
Still very unstable - after booting and turning the screen off to sleep, the phone goes into recovery and asks to wipe data / factory reset. So it is basically unusable at this point.
 
Last edited:

dhacke

Senior Member
Nov 4, 2018
737
310
There has been an update of SW binaries today

UPDATE1
Managed to boot android 10 with SW binaries ver. 1b from 1st October after flashing vbmeta from twrp section with command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. Device: Dualsim akatsuki 9436

UPDATE2
Still very unstable - after booting and turning the screen off to sleep, the phone goes into recovery and asks to wipe data / factory reset. So it is basically unusable at this point.

But it least it boot once?
 
  • Like
Reactions: MartinX3

MartinX3

Recognized Contributor
Sep 14, 2014
5,850
2,912
Mars
martinx3.github.io
There has been an update of SW binaries today

UPDATE1
Managed to boot android 10 with SW binaries ver. 1b from 1st October after flashing vbmeta from twrp section with command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. Device: Dualsim akatsuki 9436

UPDATE2
Still very unstable - after booting and turning the screen off to sleep, the phone goes into recovery and asks to wipe data / factory reset. So it is basically unusable at this point.

Thank you for your test! :)

What's the crash log in the/sys/fs/pstore/ folder right after boot after the crash happened?
(A second boot after the crash would delete the pstore logs)
 

Mazurik

Member
Dec 4, 2018
14
2
The same thing...

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :)

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 and the OEM binary got fully implemented, if there is no need for a critical hotfix.

Bugtracker:

FAQ:


Installation:
  1. FASTBOOT
    1. fastboot flash boot boot.img
    2. fastboot flash dtbo dtbo.img
    3. fastboot flash system system.img
    4. fastboot flash vendor vendor.img
    5. fastboot flash oem oem_*.img (Tama (latest) -> https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-tama/
    6. (Optional, but mandatory on first boot) fastboot flash userdata userdata.img -> will factory reset the device.
  2. Reboot into SYSTEM

Download:

Thank you very much for your help, code contribution & testing! (Random order):
  • @jerpelea and the entire AOSP developers paid by and get inventory from the sony company and their volunteers coding this wonderful piece of software
  • @dhacke thank your for providing a download server
  • And many thanks to the few donators! :)

A telegram group for technical SODP stuff:
https://t.me/xda_tv

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: Alpha

Created 2019-09-29
Last Updated 2019-10-04

Was using your OmniROM version on my XZ2 (h8266) and had many problems, like the sound from dynamic or the speaker making a craking noise during the phone calls. Tried this ROM using the tama 10 img, and as you've said, the system booted as android but then stopped responding to any action, even after repeated restart. Basically it was working before going to sleep mode... btw camera wasn't booting at all. Hope you'll find the way to fix all of the bugs=)) Good luck to you!
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,850
2,912
Mars
martinx3.github.io
Was using your OmniROM version on my XZ2 (h8266) and had many problems, like the sound from dynamic or the speaker making a craking noise during the phone calls. Tried this ROM using the tama 10 img, and as you've said, the system booted as android but then stopped responding to any action, even after repeated restart. Basically it was working before going to sleep mode... btw camera wasn't booting at all. Hope you'll find the way to fix all of the bugs=)) Good luck to you!

Camera will be added in OEMv2 :)

Which problems you had aside from the work in progress camera and the cracking noise (which can be reduced by use the speakers limited at 70% max volume)?

The SODP team will fix them for sure :)
Thank you :)
We just need bug logs from random phone usage error with an instruction how to reproduce the bug.

This month was mainly to get the phone booted with Q and the new 4.14 kernel.
 

Mazurik

Member
Dec 4, 2018
14
2
Forgot to mention...

Camera will be added in OEMv2 :)

Which problems you had aside from the work in progress camera and the cracking noise (which can be reduced by use the speakers limited at 70% max volume)?

The SODP team will fix them for sure :)
Thank you :)
We just need bug logs from random phone usage error with an instruction how to reproduce the bug.

This month was mainly to get the phone booted with Q and the new 4.14 kernel.

Btw, when checked the phone model - instead XZ2 (h8266) - it was XZ3=)))

My friend, I need your advice! From your perspective, which custom ROM would work without bugs for XZ2 h8266 while waiting for your stable versions? Tried Existenz yesterday v10 for .151 and honestly feel it as not my kind of stuff, and liked OmniRom better=))) What about Lineage? its the only one I haven't tried before=) What ROM is your favorite?!
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,850
2,912
Mars
martinx3.github.io
Btw, when checked the phone model - instead XZ2 (h8266) - it was XZ3=)))



My friend, I need your advice! From your perspective, which custom ROM would work without bugs for XZ2 h8266 while waiting for your stable versions? Tried Existenz yesterday v10 for .151 and honestly feel it as not my kind of stuff, and liked OmniRom better=))) What about Lineage? its the only one I haven't tried before=) What ROM is your favorite?!
Aye I recommend OmniROM here
I use it as daily driver.
The SonyAOSP mostly gives you a plain AOSP experience

The LineageOS is outdated, but a newer SODP based one (by the SODP members) is om the todo list for the entire tama platform. :)

Be aware that the camera is not in a good state and the upcoming camera updates are only appearing on the upcoming OEMv2 (4.14 kernel) which is not stable enough for daily usage.
 

Mazurik

Member
Dec 4, 2018
14
2
Thx 4 u response=)

Aye I recommend OmniROM here
I use it as daily driver.
The SonyAOSP mostly gives you a plain AOSP experience

The LineageOS is outdated, but a newer SODP based one (by the SODP members) is om the todo list for the entire tama platform. :)

Be aware that the camera is not in a good state and the upcoming camera updates are only appearing on the upcoming OEMv2 (4.14 kernel) which is not stable enough for daily usage.

Thx a lot Bro :cool: I'll probably try to flash the OMNIrom again and hope that the bug with cracking sounds during the phone calls will disappear while keeping the dynamic around 70%. Before asking, I've checked your suggestions under OMNIrom not to rush for updating to 4.14 until its stabilisation=)
Thx a lot for your releases, hope you did well on your exams=)))
 
  • Like
Reactions: MartinX3

MartinX3

Recognized Contributor
Sep 14, 2014
5,850
2,912
Mars
martinx3.github.io
https://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). :D
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,850
2,912
Mars
martinx3.github.io
24.11.2019
Rebuild after the new OEM v2a release with the newest code changes and android 10.0.0_r10 (November security level).
Providing now Single and Dual Sim Builds
Many stability updates
Added camera, sound calibration, sensors. Also fixed keymaster and Adreno.
And other fixes and optimizations.

PS: Camera is work in progress. Now since it is compatible with kernel 4.14 the further updates/upgrades will be made here.
Aaaaaand we (will) support 120fps and HDR out of the box.
 
Last edited:

zhka

Senior Member
Nov 12, 2010
110
16
I think I bricked the phone with latest rom.
There was no problems after booting system, all worked fine.
Then some time later I noticed that can't wake up phone by pressing power button.
And now no one combination works for me (no effect, no led indication ): +/power, -/power, charging...
Sad :|
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    https://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). :D
    15
    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!


    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:
    jerpelea said:
    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

    Bugtracker:

    Bugreport:
    • A bugreport needs
      Code:
      logcat -b all
      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
    • @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-23
    9
    Ok, 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. :confused:
    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 risk
    7
    Download & 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:
    1. fastboot flash oem_a oem_*.img
    2. fastboot flash oem_b oem_*.img
    3. Flash the ROM in a recovery
    4. Reboot into recovery just to make sure you're on the new slot
    5. OpenGapps
    6. Dual Sim Patcher
    7. (In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

    Flash the ROM without a recovery:
    1. Extract the payload.bin from the .zip file
    2. Extract the .img files with the Playload Dumper
    3. fastboot flash boot_a boot.img
    4. fastboot flash boot_b boot.img
    5. fastboot flash dtbo_a dtbo.img
    6. fastboot flash dtbo_b dtbo.img
    7. fastboot flash system_a system.img
    8. fastboot flash system_b system.img
    9. fastboot flash vbmeta_a vbmeta.img
    10. fastboot flash vbmeta_b vbmeta.img
    11. fastboot flash vendor_a vendor.img
    12. fastboot flash vendor_b vendor.img
    13. fastboot -w (Wipes your internal storage and the userdata)
    14. Continue with the normal installation
    5
    Is there changelog for the new oem? :)

    Yes, the new OEMv2c fixes the incall audio :D

    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.