Develop Bugs

Unified kernel for msm8974 devices

Unified kernel for msm8974 devices
hi all
we are cooking 1 kernel for all msm8974 devices for all custom roms
Source
https://github.com/sonyxperiadev/kernel
feel free to fork, joyn and push back
XDA:DevDB Information
Unified kernel for msm8974 devices, Kernel for the Sony Xperia Z3
Contributors
jerpelea, Kali-
Kernel Special Features:
Version Information
Status: Testing
Created 2014-10-31
Last Updated 2014-10-31

new guides published
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/

kernel is rebased
z3 platform (shinano) added to kernel
https://github.com/sonyxperiadev/kernel/
status
z1 - boots
z2 - boots
z3 - boots
yukon - boots
feel free to push fixes

jerpelea said:
kernel is rebased
z3 platform (shinano) added to kernel
https://github.com/sonyxperiadev/kernel/commits/aosp/LNX.LA.3.5.1-01110-8x74.0
status
z1 - bringup in progress
z2 - boots
z3 - boots
feel free to push fixes
Click to expand...
Click to collapse
Cool, thanks! Any love for the Z3C?

Can we do this for the T-Mobile Z3? I thought the boot loader is not able to be unlocked. If it is unlockable, I will get this device tomorrow.

Brilliant news, thanks for this. Now hope has grown for custom Roms coming sooner! Cheers
Sent from my D6603 using XDA Free mobile app

asianflavor said:
Can we do this for the T-Mobile Z3? I thought the boot loader is not able to be unlocked. If it is unlockable, I will get this device tomorrow.
Click to expand...
Click to collapse
I am 99% certain the T-Mobile Z3 will not be unlockable. Not very "un-carrier" of them.
HOWEVER:
For the first time in North American history, in addition to being available via carriers, a Sony flagship is being offered unlocked in a timely fashion in North America. If you're in the USA (which, since you're asking about T-Mo USA, I assume you are), you can get a SIM-unlocked (and hence bootloader-unlockable) Z3 at http://store.sony.com/xperia-z3-lte...atid-All-Unlocked-Phones?vva_ColorCode=FFFFFF

I'd love to get a pure AOSP build going on my Z3 Compact

Entropy512 said:
I am 99% certain the T-Mobile Z3 will not be unlockable. Not very "un-carrier" of them.
HOWEVER:
For the first time in North American history, in addition to being available via carriers, a Sony flagship is being offered unlocked in a timely fashion in North America. If you're in the USA (which, since you're asking about T-Mo USA, I assume you are), you can get a SIM-unlocked (and hence bootloader-unlockable) Z3 at http://store.sony.com/xperia-z3-lte...atid-All-Unlocked-Phones?vva_ColorCode=FFFFFF
Click to expand...
Click to collapse
Hi @Entropy512, if I well remember you are a senior dev (omni and in the past CM maintainer for SGS3 intl)?
How do you judge the information given by Sony to develop AOSP?
Why are the Original Android dev forum so empty in your opinion for this beast?
Sent from my Nexus 10 using Tapatalk

and the ball continues rolling
http://developer.sonymobile.com/2014/11/06/android-5-0-xperia-z3-running-aosp/
br
J

jerpelea said:
and the ball continues rolling
http://developer.sonymobile.com/2014/11/06/android-5-0-xperia-z3-running-aosp/
br
J
Click to expand...
Click to collapse
Add Z3 Compact support please I'll be your test guinea pig. How different would it be from the Z3 build besides the ram and screen everything else is the same correct?

del

iBuzman said:
Thx, I'm about to build Z3 AOSP rom following new guide, just need Z3 device binaries
appreciate the support given that allows us to do this :good: :good: :good:
Click to expand...
Click to collapse
please stay tuned and binaries will come
br
J

sry - didn't mean to edit after you quoted - I misread earlier post and thought z3 binaries were available already (and I got confused when the shinano git page instructions linked to a dead page ).

jerpelea said:
hi all
we are cooking 1 kernel for all msm8974 devices for all custom roms
Source
https://github.com/sonyxperiadev/kernel
feel free to fork, joyn and push back
XDA:DevDB Information
Unified kernel for msm8974 devices, Kernel for the Sony Xperia Z3
Contributors
jerpelea, Kali-
Kernel Special Features:
Version Information
Status: Testing
Created 2014-10-31
Last Updated 2014-10-31
Click to expand...
Click to collapse
Hi there i have a fix required to allow inline building with cm type roms, how do I push a fix, just git push?

Entropy512 said:
I am 99% certain the T-Mobile Z3 will not be unlockable. Not very "un-carrier" of them.
HOWEVER:
For the first time in North American history, in addition to being available via carriers, a Sony flagship is being offered unlocked in a timely fashion in North America. If you're in the USA (which, since you're asking about T-Mo USA, I assume you are), you can get a SIM-unlocked (and hence bootloader-unlockable) Z3 at http://store.sony.com/xperia-z3-lte...atid-All-Unlocked-Phones?vva_ColorCode=FFFFFF
Click to expand...
Click to collapse
Thanks, I didn't think you could unlock the T-mo version. Would love to buy the unlockable one from Sony but I have a wife that override that decision...lol. But made my decision on jumping to the Nexus 6 much easier. Thanks for the info!

nycbjr said:
Hi there i have a fix required to allow inline building with cm type roms, how do I push a fix, just git push?
Click to expand...
Click to collapse
you fork on your git
commit the change and then submit a push request from git interface
br
J

jerpelea said:
please stay tuned and binaries will come
br
J
Click to expand...
Click to collapse
now that lg g3 has lollipop would be nice to get our Z3 back up to the top of the news reports with aosp binaries update ~ I've got repos sync'd, patches applied, and device page bookmarked for periodical checking ✌

What toolchain are you guys using to compile the kernel of https://github.com/sonyxperiadev/kernel ?
could anyone compile a kernel with as modules and share the hid-sony.ko and hid-dr.ko module files?
I think that would help to have Remote Play PS4 in non Z3 and Z2 devices.
the option to compile those 2 modules as separate modules is in menuconfig > Device Drivers > HID Devices > Special HID Drivers and then
M in DragonRise Inc. game controller
M in Sony PS3 Controller
it would be much appreciated.
I would even pay if someone can share me those 2 files from the Z3 kernel source (or Z3 phone) as I tried to compile the kerel to get those files but I'm failing like a mother****er

use http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
kernel compile guide and you can succesfully compile it
br
J
MyPeople said:
What toolchain are you guys using to compile the kernel of https://github.com/sonyxperiadev/kernel ?
could anyone compile a kernel with as modules and share the hid-sony.ko and hid-dr.ko module files?
I think that would help to have Remote Play PS4 in non Z3 and Z2 devices.
the option to compile those 2 modules as separate modules is in menuconfig > Device Drivers > HID Devices > Special HID Drivers and then
M in DragonRise Inc. game controller
M in Sony PS3 Controller
it would be much appreciated.
I would even pay if someone can share me those 2 files from the Z3 kernel source (or Z3 phone) as I tried to compile the kerel to get those files but I'm failing like a mother****er
Click to expand...
Click to collapse

Android Wear 2.0 for SmartWatch 3 port progress Thread & Creation of OSS project

Hello,
As some people heard, i really try to get Android Wear 2.0 for our beloved SmartWatch 3.
And it's possible, sources, device trees, all exist to build a working own compiled Android Wear 2.0.
So this thread tells about the current process of the port
PROGRESS
Code:
Repo synced
First build finished (not buildable yet due no blobs included
GAPPS Porting in progress
Fixed to 99% the device tree
Updating Blobs to M1D64T in progress
Using own Device tree
SOURCES
Device Tree for tetra:
https://github.com/Sony-SmartWatch-3-OSS/android_device_tree_tetra_eng_prerelease
Device Kernel for tetra (unmodified):
https://android.googlesource.com/kernel/bcm/+/android-wear-6.0.1_r0.99
(we can use MM kernel on Nougat too, maybe some patches needed but that's okay)
Prebuilts/Blobs for tetra:
https://github.com/Sony-SmartWatch-3-OSS/vendor_prebuilts_tetra
For Discussions go to this thread please: https://forum.xda-developers.com/smartwatch-3/general/companion-thread-android-wear-2-0-t3565693
If you want to help me on this project, write to me via telegram: https://t.me/PDesire

I need that so much any ETA ?
By the way keep up the good work !

Nice to see someone is working on this :victory:
Sent from my Sony Xperia Z5 using XDA Labs

Thanks for your job.
Enviado desde mi Redmi Note 3 mediante Tapatalk

great!!! thanks

Dear PDesire,,
My support can be only moral..... :crying:
And I hoping good news soon from you
Thx again for your great hard work :good:

thankx you great hard work and good luck my friend

I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Certain components of Android (and therefore Wear) come from third parties and have licenses which require the source code to be made available (e.g. the Linux kernel). The components made available via the AOSP repositories for releases like Wear are, afaik, the components which have that type of license.
Wear is a release which has taken the same path as Honeycomb. I can understand that for open source fans and people looking to tinker with a working system it’s somewhat disappointing to see, but those are the choices Google has made.
Click to expand...
Click to collapse
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.

drakonizer said:
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
Click to expand...
Click to collapse
Yeah I've seen these, and already fixed. Patch comes soon.
Things for WLAN and BT for example are on google repo too and if a library or something is missing we can use it from M1D64T
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
Click to expand...
Click to collapse
Lel then I can't understand why the build is working xD at least I am building in time and already 14% finished
I know some libs we have to grab from the Marshmallow FW but that shouldn't be a big deal
At least we also need some things from Preview 2 so we can get our AW 2.0 Preview 2 working
So I try my best to grab much from source and if required also from FW, but all in all its possible for our SmartWatch 3 to get Android Wear 2.0
Your PDesire

but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?

xpatze85x said:
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
Click to expand...
Click to collapse
Because there aren't any sources of the final version.

@PDesire :
You're the man...keep up a good work ???

Hey @PDesire , any news? I'm sooooo hyped!!!

Thank bro I hope

Thanks for this!

So current status is:
Code:
Repo synced
First Test build stopped to fix things on device tree
Expected in future:
Code:
Blobs dump
Fully fixed Device tree
Creating vendor for tetra
Adding overlays for framework to device tree
Some mix with armv7-a-neon generic
Gapps Dump
Expected in far future:
Code:
Creating an OSS project for tetra (like sonyxperiadev but for tetra)
So guys I will do more tomorrow as I am awake already from Friday 7AM - 3AM Saturday (right now GMT +1) and working on it and I need my sleep xD
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Your PDesire

PDesire said:
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Click to expand...
Click to collapse
And I can confirm my donation is coming when a working build is ready, and I suppose others are coming, isn't it guys? ???

Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app

Neo Cortex said:
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. That'll only work on an official firmware, unfortunately...

Thank you very much, hope you will finish it without problems~!

[ROM] [7.1.2] [UNOFFICIAL] [NON-DEV] LineageOS 14.1 Xperia M

Since the Xperia M aka nicki is no longer maintained I decided to start my own build and I thought I share it with the community.
Full Disclosure: I am not a developer. If there are bugs in any build, I cannot solve them. So always do a backup before flashing.
Also if you do not know how to flash: leave it be. I will not help with flashing problems.
I will try to keep it up-to-date.
You can download it here: https://drive.google.com/file/d/0B7J1cVOauuana0l0NG1GWmE1aWc/view?usp=sharing
Android: 7.1.2
Security Patches: May 2017

Komapatient said:
Since the Xperia M aka nicki is no longer maintained I decided to start my own build and I thought I share it with the community.
Full Disclosure: I am not a developer. If there are bugs in any build, I cannot solve them. So do always a backup before flashing.
Also if you do not know how to flash: leave it be. I will not help with flashing problems.
I will try to keep it up-to-date.
You can download it here: https://drive.google.com/file/d/0B7J1cVOauuana0l0NG1GWmE1aWc/view?usp=sharing
Click to expand...
Click to collapse
Thank you bro for sharing and keeping the device alive ?
Btw you should consider posting this in android development forum so that people know abt it

Adarsh Dubey said:
Btw you should consider posting this in android development forum so that people know abt it
Click to expand...
Click to collapse
I intentionally posted not in the development section, since I am not developing but only building.

Komapatient said:
I intentionally posted not in the development section, since I am not developing but only building.
Click to expand...
Click to collapse
Bro you shouldn't post it in original development but you can post it in Android development as you are building the rom for the device and many of the people port roms they also don't develop nor fix bugs but post it in Android development as they are building the rom for the device

sir @Komapatient , can you please share the source kernel or ROM?

Nicklas Van Dam said:
sir @Komapatient , can you please share the source kernel or ROM?
Click to expand...
Click to collapse
Hi,
I don't understand your request. I pulled the sources from LinOS Git. There is nothing done on the source.

Komapatient said:
Hi,
I don't understand your request. I pulled the sources from LinOS Git. There is nothing done on the source.
Click to expand...
Click to collapse
Ok, it's neccesary for now. Can you please to keep update on this ROM?

Komapatient said:
Since the Xperia M aka nicki is no longer maintained I decided to start my own build and I thought I share it with the community.
Full Disclosure: I am not a developer. If there are bugs in any build, I cannot solve them. So always do a backup before flashing.
Also if you do not know how to flash: leave it be. I will not help with flashing problems.
I will try to keep it up-to-date.
You can download it here: https://drive.google.com/file/d/0B7J1cVOauuana0l0NG1GWmE1aWc/view?usp=sharing
Android: 7.1.2
Security Patches: May 2017
Click to expand...
Click to collapse
So basically you're keeping the ROM updated with latest changes from lineage OS source code , I mean bug fixes and security patches etc.

matrixex said:
So basically you're keeping the ROM updated with latest changes from lineage OS source code , I mean bug fixes and security patches etc.
Click to expand...
Click to collapse
Yes. As a courtesy to the people who cannot compile their own ROM and to give s.th. back to the community who helped me a lot of times.

Hi @Komapatient,
Glad to see you once again around here, think we last talked when you were using the Xperia V on LineageOS.
Happy to see nicki is not fully dead and that its users can benefit from newer builds.
However there's a big concern here, I pushed the Nicki official removal for two important reasons :
- Device sources are no longer updated. If there's no real issue it's fine, but might appear.
> Issues like autobrightness flashing in a weird way upon device wake/unlock is among the biggest issue fixed / wip since the changes stopped.
> Checked in my huashan sources to find common relevant things for nicki, I just pushed an overlay cleanup and fix for MMS non-Data use.
- Kernel sources are highly outdated. To put this in a easy way, we can judge the security status
> to be around December 2016 and February 2017. Therefore the security version you share here is only the ROM sources,
> though a good portion of the security patches are actually to be worked upon for each kernel.
You can find our internal CVEs vulnerabilities tracker concerning the nicki 8x27 kernel here : https://cve.lineageos.org/android_kernel_sony_msm8x27
Someone should at some point stand up and start looking at them one by one,
fixing the ones related to the kernel version by cherry-picking, testing then pushing to gerrit.
You can take my sony_msm8960t kernel as reference if you wish, only the most recent CVEs are a work in progress,
and you should therefore easily see which CVEs concern your 3.4 kernel and find the commits in my history.
I'd gladly merge commits uploaded to gerrit if they are valid and properly authored / clean.
Hope this makes the current status of Nicki a bit more clear.
Bye.

@AdrianDC
Thank you for your clarification. The kernel sources are indeed a bummer, but as my coding skills are below zero. Sadly I am not able to help here out.

Komapatient said:
@AdrianDC
Thank you for your clarification. The kernel sources are indeed a bummer, but as my coding skills are below zero. Sadly I am not able to help here out.
Click to expand...
Click to collapse
Trying to "steal" my commits from sony_msm8960t would be a good start,
you can also check the commits tags on Gerrit to see the CVE 20xx-xxxx related numbers
when the information was set as topic, helps clearing the list too.
Since the work is already done on our side, it shouldn't be a giant work to do,
and would be a good place to start with + bring back some security updates to the device.

Please try to update this rom

please try update this rom, ,

[ROM][7.1.2][UNOFFICIAL] LineageOS with OMS patch for Xperia M (nicki/c1905)

Hello everyone. I decide to build my unofficial builds for Sony Xperia M (C1905/NICKI) device since official builds stops.
Main differences comparing with offiicial LineageOS:
Integrated OMS patch with LineageSubstratum project. Before that, i used LineageOMS project, but author decide to freeze development. Currently only clean Lineage 14.1 will be builded. Latest rom with LineageSubstratum - lineage-14.1-20171126_103228-UNOFFICIAL-nicki-loms
Removed 2 apps: Snap (due to video recording bug) and Camera2 (due to sdcard save problem). Replaced with OpenCamera
Warning! These builds incompatible with last official build for Xperia M lineage-14.1-20170427-nightly-nicki-signed and requires full system/data/cache wipe.
Building is performed from time to time or weekly based. So check & download my build host recently! BTW, all builds checked manually by me on my phone, so be sure - no invalid roms.
Download roms: lineageos.do2.pw
Explanation of filenames:
-los.zip - clean LineageOS build
-loms.zip - with LineageSubstratum patches
-nicklas.zip - with F2FS patches and Mimori kernel
builds before 24.08.2017 are with LineageOMS patches
Flash this for dual sim models (c2004/c2005),
Flash this for standart LOS root.
If you need - Opengapps arm 7.1 (pico recommended)
Device: sources
Kernel: sources - original LOS nicki kernel
Vendor: blobs - from the TheMuppets repo
Build manifest (with LineageSubstratum): here
Build manifest (with LineageOMS): here
Build manifest (without LineageOMS): here
Build manifest (with F2FS patches and Mimori kernel): here
Big thanks for LineageOS, LineageOMS, LineageSubstratum, Nicklas Van Dam for updated device tree, The Muppets for blobs. And all testers for reasonable replies

droncheg said:
Hello everyone. I decide to build my unofficial builds for Sony Xperia M (C1905/NICKI) device since official builds stops. Then i decide integrate great OMS thing with LineageOMS project.
So, it's a clean LOS with a little flavor of OMS for fully working Substratum
Building is performed from time to time, so check my build store recently!
host: lineageos.do2.pw
latest: lineage-14.1-20170524-UNOFFICIAL-nicki
Click to expand...
Click to collapse
Thanks for OMS support ?

Have someone who install this rom. How works?
For author: Please upload screenshots and changelog.

Sorry, has no permissions to attach or include links due to my newbie status here.
Changelog is the LOS+LineageOMS summary changes at build time, so read them for changes.

Thanks for the rom. will try it shortly. Btw can you please move this thread to android development section?

hhjadeja007 said:
Btw can you please move this thread to android development section?
Click to expand...
Click to collapse
All i can do is spam here up to 10 posts, then i will have necessary rights =)

Sad to hear that

Just flashed today.
Great rom but not able to detect sim card. Using c2004. Thanks for the rom

hhjadeja007 said:
not able to detect sim card. Using c2004
Click to expand...
Click to collapse
As all dual sim models - you must flash this for working sim.

where we can download your ROM bro?

Nicklas Van Dam said:
where we can download your ROM bro?
Click to expand...
Click to collapse
lineageos.do2.pw

Camera app crashes while selecting video recording mode

hhjadeja007 said:
Camera app crashes while selecting video recording mode
Click to expand...
Click to collapse
Yep, thats known bug with com.cyanogenmod.snap application. Any other camera app record video without bugs. I recommend Open Camera (net.sourceforge.opencamera) from F-Droid.

It might be heard stupid...but how can I change the battery circle to percentage? There was always this choise in other roms but I cannot find it here.
By the way,I installed it yesterday paired with hana kernel,overclocked to 1350...it is really fast (for its age)! No overheating issues just one random restart.I do not know if it is the rom or the kernel,I will find out in the future.I do not have a sim inside (it is just a back up phone).I installed apps,browsed the internet, browsed in phone files etc.It is good.Concerning speed >Antutu bench stock ~19500,overclocked bench ~24500.

jokeris said:
but how can I change the battery circle to percentage?
Click to expand...
Click to collapse
Settings, Status bar, Battery status style, Text
And yes, C1905 feel perfect himself at 1.4 GHz overclock, but i use NUI kernel

Added screenshots & links

droncheg said:
Added screenshots & links
Click to expand...
Click to collapse
Great sir :good: , can you give a source link for device,kernel and vendor that you are using it?

One request, can you add pixel like animation effect in navigation bar?

Nope =)

Big update for this firmware! Replaced kernel to modded HanaKernel (limit max_cpu_freq to 1458MHz, min_cpu_freq to 192MHz - for stability at boot stage), replace Snap to Camera2 (Snap is useless in video recording at this device), replaced my phone blobs to blobs from TheMuppets repo. Latest build is here

[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 9.0.0_r46 [Stable]

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
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.
Preview Picures:
https://forum.xda-developers.com/showpost.php?p=77635765&postcount=2
https://forum.xda-developers.com/showpost.php?p=78870686&postcount=436
https://forum.xda-developers.com/showpost.php?p=79450390&postcount=619
https://forum.xda-developers.com/showpost.php?p=79460850&postcount=624
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/
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
Click to expand...
Click to collapse
Known Bugs:
Camera is under development.
[TAMA] [AKATSUKI] [CRITICAL??] Speakers clipping and distortion
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
@nasko_spasko
@laoli0913
@twistedddx
@dhacke thank your for providing a download server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
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
AOSP, ROM for the Xperia XZ2
Contributors
MartinX3, Sony
Source Code: https://github.com/SonyAosp
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 9
Stable Release Date: 2019-08-08
Created 2018-09-16
Last Updated 2020-10-23

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:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash oem oem_*.img
(Optional, but mandatory on first boot) fastboot flash userdata userdata.img -> will factory reset the device.
(Mandatory on dual sim devices) Dual Sim Patcher
(Optional) https://opengapps.org/ or MicroG

News
05.01.2020
this rom is now officially end of life like the omnirom.
Future development happens only on android 10.0 with kernel 4.14.
Of course this doesn't automatically make this rom unusable.
Click to expand...
Click to collapse
27.10.2019
sonyaosp 9.0.0_r46
august security patch
newest sync with sodp code.
Fixed not working touch for the few xz2 (compact) users with tcm touch chip.
(i don't know why the tcm chip got rarely used in the xz2 & xz2 compact hardware).
Ps: The new security updates are only happening on android 10 and require backporting to 9 from developers who know what they are doing to avoid any new (security) bugs.
We sadly don't have this capacity.
Click to expand...
Click to collapse
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
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
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 sonyaosp switches to q.)
Click to expand...
Click to collapse
26.08.2019
september no new release
reason -> vacation + university exams
Click to expand...
Click to collapse
08.08.2019
sonyaosp 9.0.0_r46
august security patch
new glove mode
Click to expand...
Click to collapse
12.07.2019
sonyaosp 9.0.0_r44
july security patch
Click to expand...
Click to collapse
16.06.2019
sonyaosp with june 2019 security patch level.
Click to expand...
Click to collapse
31.05.2019
sonyaosp 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
Click to expand...
Click to collapse
19.05.2019
reworked the thread page
Click to expand...
Click to collapse
14.05.2019
http://www.dhsfileserver.de/ftp/martinx3/ thank you @dhacke for the second download server
Click to expand...
Click to collapse
11.05.2019
next build will hopefully contain the open source chromium browser cherry-picked from omnirom.
(if i didn't it wrong, the builds are at
out/target/product/{devicename}/obj/apps/chromium_intermediates/
and
out/target/product/{devicename}/system/app/chromium/chromium.apk)
so we have at least one browser build in and this should also fix maybe happening webview bug.
Thank you @murrofx and @hingbong for your bugreports!
The next build is on hold (like omnirom and aosp twrp) until we get a new prebuild kernel (prebuild kernels usually ensure that the kernel is working and buildable).
https://github.com/sonyxperiadev/vendor-sony-kernel/tree/aosp/le.um.2.3.2.r1.4
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
22.04.2019
oemv8 (camera) support!
Click to expand...
Click to collapse
22.04.2019
attached oemv8 images at the post
https://forum.xda-developers.com/showpost.php?p=77635765&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.
Click to expand...
Click to collapse
12.04.2019
9.0.0_r35 april security update
much fixes
oemv7 support
you should be able to try aosp 10.0 q gsi's with it!
Click to expand...
Click to collapse
07.04.2019
bug & feature tracker
https://github.com/martinx3sandroiddevelopment/bug_tracker
Click to expand...
Click to collapse
21.02.2019
updated the rom for the probably tomorrow released 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".)
Click to expand...
Click to collapse
10.02.2019
february 2019 patch level
switch from sony aosp to sonyaosp.
Sony aosp = sonyaosp + additional fixes (like exfat sdcard support)
sonyaosp = aosp + device support fixes for xperias
i excluded the gapps with a bit work and investigation!
Click to expand...
Click to collapse
17.01.2019
january 2019 patch level
Click to expand...
Click to collapse
09.01.2019
moved to android file host.
Added builds for every supported device.
Click to expand...
Click to collapse
22.12.2018
added the xz3 (akatsuki).
Camera still not feature complete.
Please search or report bugs in the bug tracker.
Twrp will follow.
Click to expand...
Click to collapse
29.11.2018
first android 9.0 build.
added the xz2c (apollo).
Should be stable enough for stable use.
Please search or report bugs in the bug tracker.
Click to expand...
Click to collapse
12.10.2018
new build with fixed bugs.
including the fixed display damaging bug.
May may maaaaaaaaay you get graphical/display issues, you should deactivate your device asap with (vol up + power)
Click to expand...
Click to collapse
24.09.2018
build "2018-09-14_15:00+2:00":
Switched back to oem vendor img for android 8.1.
The oem vendor 9.0 img shouldn't be used.
Click to expand...
Click to collapse
16.09.2018
first release of the unstable, bugfull build.
Click to expand...
Click to collapse

Deleted. Reason: wrong thread.

Anyone that has AOSP installed can do me a Favor and run a MicroSD Speed Test?
I.E Androbench and in Settings switch target partition to MicroSD folder.

Haldi4803 said:
Anyone that has AOSP installed can do me a Favor and run a MicroSD Speed Test?
I.E Androbench and in Settings switch target partition to MicroSD folder.
Click to expand...
Click to collapse
The sdcard Support is still missing.
(Look at the bug list)

24.09.2018
Build "2018-09-14_15:00+2:00":
Switched back to OEM vendor img for Android 8.1.
The OEM vendor 9.0 img shouldn't be used.
Click to expand...
Click to collapse

https://github.com/sonyxperiadev/bug_tracker/issues/169#issuecomment-424278920
PLEASE DON'T FLASH TAMA WITH THE CURRENT KERNEL
My Akari's display got permanently damaged.
I repeat, DO NOT FLASH.
Click to expand...
Click to collapse
I planned a new build on thuesday with the new kernel fixes.
But now I will wait.

The AOSP 4.9 kernel is now stable enough to get prebuild by sony.
(Which is inside my TWRP builds)
Nice.
https://github.com/sonyxperiadev/vendor-sony-kernel/tree/aosp/LE.UM.2.3.2.r1.4
My next AOSP ROM will probably get nice fixes. (Should still be tested and confirmed).
But he still need to confirm if the hardware damaging bug got really fixed or only by a workaround.
https://github.com/sonyxperiadev/bug_tracker/issues/166#issuecomment-425406778

HI every1 !
Does any1 know why I am unable to find any Xperia XZ2 rom in the web at all ?
I hate the feeling I can't use Gcam at all because of Cam2 API is not supported .

margee82 said:
HI every1 !
Does any1 know why I am unable to find any Xperia XZ2 rom in the web at all ?
I hate the feeling I can't use Gcam at all because of Cam2 API is not supported .
Click to expand...
Click to collapse
Do you mean Custom ROMs?
The XZ2 was introduced with a brand new kernel.
It took months make it compatible with AOSP to create custom ROMs and even since the compatibility stock update in September, the aosp support needs more work.
After that and my TWRP starts working, the custom creation will start.

Probably I make a new build with synced sources in 3 weeks.
Then the user github user kholk will be back from his 15 days vacation.
(He mentioned the display damage but and created the workaround).

Status Update!
https://github.com/sonyxperiadev/kernel/pull/1688#issuecomment-428714128
kholk said:
MSM8956 Loire stability not impacted by the upstream updates. @oshmoun never saw stability issues due to that.
Tone testing can be started since this platform is stable.
Tama testing will happen soon, after display issues get solved.
Display Issues = The Big Hardware Damaging Bug!
Yoshino, Nile on hold due to stability issues to be solved.
Click to expand...
Click to collapse
Display issues = The Big Hardware Damaging Bug!

It seems that I will make a new AOSP Build this week.
The Sony Developers made a rampage in the XZ2 Bug List on Github and closed important bugs, including the display damaging bug.

MartinX3 said:
It seems that I will make a new AOSP Build this week.
The Sony Developers made a rampage in the XZ2 Bug List on Github and closed important bugs, including the display damaging bug.
Click to expand...
Click to collapse
Are you aware that sony released new binaries for 8.1 ?
im curious what the binary brings for 8.1 roms

hary232 said:
Are you aware that sony released new binaries for 8.1 ?
im curious what the binary brings for 8.1 roms
Click to expand...
Click to collapse
Yeahr and switched to 8.1.0r47
That are the AOSP hardware drivers

MartinX3 said:
Yeahr and switched to 8.1.0r47
That are the AOSP hardware drivers
Click to expand...
Click to collapse
cool. i assume you are planning to release a build soon then (after the build error gets fixed by sony, of course)?

hary232 said:
cool. i assume you are planning to release a build soon then (after the build error gets fixed by sony, of course)?
Click to expand...
Click to collapse
Yes
You saw my reported build error?

MartinX3 said:
Yes
You saw my reported build error?
Click to expand...
Click to collapse
yes! i really look forward for DRS functionality.
i'm monitoring the github from time to time. still not pulling the trigger to unlock the bl tho.
At any case, thank you for your hard work so far.

hary232 said:
yes! i really look forward for DRS functionality.
i'm monitoring the github from time to time. still not pulling the trigger to unlock the bl tho.
At any case, thank you for your hard work so far.
Click to expand...
Click to collapse
Thank you
After storm released the DRMfix (after I gave him the ok) you can use your stock firmware like you had never unlocked the BL