[EOL][SODP][ROM][LineageOS][XZ2, XZ2C, XZ3] LineageOS 17.1 [STABLE][UNofficial]

Should I continue this project?

  • Yes, for the XZ2.

    Votes: 59 33.1%
  • Yes, for the XZ2C.

    Votes: 64 36.0%
  • Yes, for the XZ3.

    Votes: 52 29.2%
  • No.

    Votes: 3 1.7%

  • Total voters
    178
Search This thread

MartinX3

Recognized Contributor
Sep 14, 2014
6,098
3,101
Mars
martinx3.github.io
@MartinX3

any word on if/when the display jankiness/lag may be addressed on apollo (xz2c)? this issue is severe enough for me that i cannot use this ROM, since it feels like a slower/worse device than my 2015-era z5c with android 7 :(

https://github.com/sonyxperiadev/bug_tracker/issues/603

I would ask it directly in the bug tracker, but as far as I know now the 4.19 kernel is under development.
If we get it, too, it will be more stable, since there is already Snapdragon 845 mainlined and older xperias than xz2 wouldn't be supported, which speeds up its development.
Otherwise we will get more 4.14 fixes after most 4.19 work is done.
Maybe after 4.19 the device gets mainlined into kernel.org which eases most things, but who knows.
 

rinigus

Senior Member
Nov 15, 2015
240
272
I presume the main attraction of Lineage for Android users would be OTAs provided via official channel. I could see it has been raised earlier (Feb 2020?) here, maybe something has changed with the respect of making it official?

Despite someone not liking Sony among LOS developers, what is the procedure for submission? Or is there some red flag that is impossible for Sony AOSP to cross and there is no point in submitting it?
 

Olivier

Recognized Developer / Retired Forum Moderator
Nov 6, 2011
2,664
6,940
I presume the main attraction of Lineage for Android users would be OTAs provided via official channel. I could see it has been raised earlier (Feb 2020?) here, maybe something has changed with the respect of making it official?
Both the Xperia XZ2 and the XZ2 Compact are now officially supported in Lineage, and will be getting builds/OTAs very soon. The device trees and the kernel however are not forked from SODP.
Despite someone not liking Sony among LOS developers
I can't really confirm this - we have supported many Sony devices in the past and still do.

what is the procedure for submission?
See the LineageOS wiki.
Or is there some red flag that is impossible for Sony AOSP to cross and there is no point in submitting it?
The device support requirements are pretty clear -- a quick look at the SODP bug tracker (broken emergency calls, camera issues, lags and WiFi/mobile data issues to name a few) suggests that the tama platform doesn't meet them unfortunately.
 
  • Like
Reactions: Danj1

leeoniya

Senior Member
Aug 15, 2010
113
10
@Olivier that's great news! (i think?)

> The device support requirements are pretty clear -- a quick look at the SODP bug tracker (broken emergency calls, camera issues, lags and WiFi/mobile data issues to name a few) suggests that the tama platform doesn't meet them unfortunately.

So, what's the practical result of this? While there are still issues, there have been many which have been fixed recently (LTE speed, idle battery drain, VoLTE, sound/bluetooth, etc.). Does not using/forking the SODP kernel mean that we're going to regress all the old issues plus still have the current issues as well, or just have a different assortment of issues? Or fewer issues? From what I understand the SODP volunteers have special access to Sony's internals, so they're better able to address things like hardware issues, or is the Lineage team just as capable?

thanks!
 

rinigus

Senior Member
Nov 15, 2015
240
272
Both the Xperia XZ2 and the XZ2 Compact are now officially supported in Lineage, and will be getting builds/OTAs very soon. The device trees and the kernel however are not forked from SODP..

Congratulations, this is surely good for users. As far as I understand, it is using stock ROM blobs then. In this respect would be good to distinguish STOCK and SODP versions.

I can't really confirm this - we have supported many Sony devices in the past and still do.

Great, then I guess we can just drop that :)


The device support requirements are pretty clear -- a quick look at the SODP bug tracker (broken emergency calls, camera issues, lags and WiFi/mobile data issues to name a few) suggests that the tama platform doesn't meet them unfortunately.

The question with the respect to that: when SODP gets these (and maybe others) bugs fixed and would fulfill all the requirements, how is it decided whether to keep stock-based or SODP-based ROM as official? Is it first-come, first-served or some other criteria are used to decide the official status?
 

Olivier

Recognized Developer / Retired Forum Moderator
Nov 6, 2011
2,664
6,940
Definitely.


So, what's the practical result of this? [...] Does not using/forking the SODP kernel mean that we're going to regress all the old issues plus still have the current issues as well, or just have a different assortment of issues? Or fewer issues?
We use the stock kernel and blobs (which work fine) -- just like pretty much all officially supported Lineage devices BTW.

From what I understand the SODP volunteers have special access to Sony's internals

Not really, only 1-2 people have special access to... things (which makes sense because they're Sony employees).
they're better able to address things like hardware issues [...]
Possible. Sony releases new software binaries on a regular basis (which is super convenient), and the SODP volunteers as you call them have achieved a lot and I highly respect them for their work.

Congratulations, this is surely good for users.
Thanks!

As far as I understand, it is using stock ROM blobs then.
Correct.

In this respect would be good to distinguish STOCK and SODP versions.
As far as I can tell, this is already done (see the title of this thread, for example). I find the [STOCK] tag a bit misleading and would prefer if it was only used for ROMs actually based on Stock (like eXistenZ for example).


The question with the respect to that: when SODP gets these (and maybe others) bugs fixed and would fulfill all the requirements, how is it decided whether to keep stock-based or SODP-based ROM as official? Is it first-come, first-served or some other criteria are used to decide the official status?
If we wanted to use SODP, we'd have to change the device trees and kernel "mid-cycle" - that's not something that should be done. In other words: Nothing's going to change in Lineage 17.1.
Would we consider it for Lineage 18 (Android R)? Probably not (if our trees still work fine) -- even if Lineage based on SODP was actually charter-compliant by that point: Camera quality would still be much better with the stock camera stack.
 
  • Like
Reactions: Danj1 and rinigus

rinigus

Senior Member
Nov 15, 2015
240
272
We use the stock kernel and blobs (which work fine) -- just like pretty much all officially supported Lineage devices BTW.
....

As far as I can tell, this is already done (see the title of this thread, for example). I find the [STOCK] tag a bit misleading and would prefer if it was only used for ROMs actually based on Stock (like eXistenZ for example).

Situation with Sony is somewhat different when you compare with the other manufacturers. I am not aware of any other manufacturer that makes separate efforts for stock and AOSP based roms with the separate teams working on it. So, while fair enough for other cases where Lineage is based on stock, for Sony it would be helpful to distinguish already in the title. Right now, as far as I could see, you just don't mention anything in the title regarding the origin (SODP vs STOCK) and let @MartinX3 to state that his version is based on SODP. On the other hand, it is different from eXistenZ as well.

TBH, no good solution comes up on having 3 versions SODP/STOCK-based LOS/STOCK eXistenZ. You at least do warn and state it in the thread that it is based on stock and we should not flash OEM binaries for SODP :) .

Anyway, good work and good luck with it!
 
  • Like
Reactions: Olivier

MartinX3

Recognized Contributor
Sep 14, 2014
6,098
3,101
Mars
martinx3.github.io
Is my SODP based LineageOS Port still needed or are the users moved to PixelExperience or the stock based LineageOS which both are official and receive OTA updates?
If yes, I will EOL the SODP based LineageOS port and focus on other stuff.
 
  • Like
Reactions: rinigus

rinigus

Senior Member
Nov 15, 2015
240
272
@MartinX3, good question. Cannot respond to it as a user, but, from developer POV, it seems logical to drop this and focus on other projects. The users could either choose SODP or STOCK based official solutions and then allow Android devs to focus on supporting those. But there is some time as probably new builds were expected after new blobs are released?
 

MartinX3

Recognized Contributor
Sep 14, 2014
6,098
3,101
Mars
martinx3.github.io
@MartinX3, good question. Cannot respond to it as a user, but, from developer POV, it seems logical to drop this and focus on other projects. The users could either choose SODP or STOCK based official solutions and then allow Android devs to focus on supporting those. But there is some time as probably new builds were expected after new blobs are released?

Yes, I think the same in the developer POV.
And yes. new OEM shouldn't work with an older LOS rom release.
 

maverick6664

Senior Member
Aug 18, 2017
86
17
Is my SODP based LineageOS Port still needed or are the users moved to PixelExperience or the stock based LineageOS which both are official and receive OTA updates?
If yes, I will EOL the SODP based LineageOS port and focus on other stuff.

hmmm...I want LineageOS, preferably based on SODP....

EDIT: I like LineageOS because it has wifi calling and funny features. OTOH Google has already released Android 11 beta and will release official Android 11 in some months. However there will be no official Android 11 for Xperia XZ2 series (remember, its support expired this spring)!! We will have to rely on SODP Android 11 for XZ2. So if we want to use LineageOS Android 11, this project must continue.
 
Last edited:
  • Like
Reactions: hostme

MartinX3

Recognized Contributor
Sep 14, 2014
6,098
3,101
Mars
martinx3.github.io
hmmm...I want LineageOS, preferably based on SODP....

EDIT: I like LineageOS because it has wifi calling and funny features. OTOH Google has already released Android 11 beta and will release official Android 11 in some months. However there will be no official Android 11 for Xperia XZ2 series (remember, its support expired this spring)!! We will have to rely on SODP Android 11 for XZ2. So if we want to use LineageOS Android 11, this project must continue.

We maybe get security updates on stock until (spring) 2021.

And I think the official lineageOS will move to Android 11 as well.
The only difference between sodp and stock is on stock the gcam will never work, stock contains more closed source and sodp has a higher/newer kernel version and probably kernel mainline support in 2021 (but probably without camera for some time).
 

Raphos

Senior Member
Jul 31, 2015
240
93
Elsass
So if we want to use LineageOS Android 11, this project must continue.

Hi,
I understand that Martin don't want to continue to develop this rom and spend a lot of time just for few users.
However his great work was not useless and he gives us the first LineageOS port.
If in the future the stock LineageOS rom is EOL, someone could build on Martin's work in order to maintain LOS for our smartphones :angel:
For example my old Z3 Compact gets LOS17 since october 2019...
 
  • Like
Reactions: MartinX3

MartinX3

Recognized Contributor
Sep 14, 2014
6,098
3,101
Mars
martinx3.github.io
Hi,
I understand that Martin don't want to continue to develop this rom and spend a lot of time just for few users.
However his great work was not useless and he gives us the first LineageOS port.
If in the future the stock LineageOS rom is EOL, someone could build on Martin's work in order to maintain LOS for our smartphones :angel:
For example my old Z3 Compact gets LOS17 since october 2019...

That for sure if the stock port may become EOL somewhere in the future and my device still lifes and probably we use the mainline kernel then (and all users would complain about a missing camera) or someone else does it with the SODP/stock sources :silly:
 

maverick6664

Senior Member
Aug 18, 2017
86
17
That for sure if the stock port may become EOL somewhere in the future and my device still lifes and probably we use the mainline kernel then (and all users would complain about a missing camera) or someone else does it with the SODP/stock sources :silly:

Missing camera is a big disadvantage.

I admit stock firmware is usually stable, but lineage/sodp is smarter and as I mentioned, Lineage comes with wifi calling. The only disadvantage is that Lineage's recovery is unreliable (I have difficulty installing dual-patch and Magisk), so Martin's twrp for sodp comes in handy. xz2 is a nice model; fast enough, good camera, display, durable battery and these days its price is surprisingly affordable (used H8266 is about $150 at ebay). I hope it will live longer than any other previous xperia's, even if 5G prevails (though I don't think it's in the near future. It's unnecessarily fast. I can't imagine watching HD streaming videos on a 5-6 inch smartphone or can't imagine other usages consuming much data. Usually we do it at home with a desktop with a large display which is cheaper than a 5G phone/connection.)

So I'll miss Lineage/sodp combi if Martin stops developing for xz2 series....:(

And to Martin, if you stop developing this, what project do you intend to do? Even a possibility is fine. Please.
 

TacoLoco

Senior Member
Nov 28, 2007
529
34
@MartinX3

As a user I would say don't stop but at the end it's up to you.. You put a lot of work in and I really appreciate this and I'm sure there are many others, some don't but fu**'em..

I consider your ROM as more clean as it has the clean AOSP base but from a enduser perspective atm Stock based LOS is the better choice (camera!), we all know that this is very hard work and I'm still not sure how far this can even go? If it won't get to a point where I could give the device to my girlfriend or mother (I mean the average user who simply want a device where everything is working) in the near future, I would "stop wasting my time" if I were you and maybe contribute to the other project as I think there is no competition between the two projects cause they are so different.

However you will decide I want to say thank you for the amazing work you've done bro!! :highfive::victory::good:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    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 LineageOS ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)

    This ROM build will always mainly based on Code from Sony AOSP & LineageOS 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
    LineageOS, ROM for the Xperia XZ2

    Contributors
    MartinX3, SODP Team
    Source Code: https://github.com/MartinX3-AndroidDevelopment-LineageOS/

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Latest Stock Firmware
    Based On: LineageOS

    Version Information
    Status:
    No Longer Updated
    Current Stable Version: 17.1

    Created 2020-02-02
    Last Updated 2020-10-23
    12
    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. Google Apps like Playstore
    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
    10
    Did you fullwipe your phone?
    The newest sodp twrp and the newest Los are working together
    I'm using it here

    Hi,
    After 2 fighting days with LOS, TWRP and my XZ2C dual sim, I finally achieved the installation :laugh:. Thank you Martin !

    This is what I did for, maybe it can help :
    Code:
    Create the .img files with payload dumper
    
    - Extract lineage-17.1-20200414-UNOFFICIAL-apollo_RoW.zip and put the payload.bin into payload_dumper folder
    - Generate the .img files 
    - In payload_dumper/output/ folder now, boot, dtbo, system, vbmeta and vendor.img
    
    Install stock .618 firmware with flashtool
    
    - Flash .618 stock firmware
    - Boot into .618 stock firmware
    - Activate developers options
    - Reboot into bootloader with adb reboot bootloader
    
    Wipe in fastboot mod
    
    - fastboot erase boot
    - fastboot erase cache
    - fastboot erase system
    - fastboot erase userdata
    
    Flash LOS .img  in fastboot mod
    
    - fastboot flash boot boot.img
    - fastboot flash dtbo dtbo.img
    - fastboot flash system system.img
    - fastboot flash vbmeta vbmeta.img
    - fastboot flash vendor vendor.img
    - fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_tama.img
    - fastboot reboot-bootloader
    
    Install TWRP from 2020-04-13_20-20-57_twrp_sodp_xz2c.tar.gz  in fastboot mod
    
    - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    - fastboot boot twrp-xz2c.img => enter into TWRP
    
    - flash sony-dualsim-patcher-v4.zip
    - reboot system
    8
    02.02.2020
    The first LineageOS 17.1 build based on the SODP device trees.
    My vanilla SODP release and LineageOS should share the same bugs.
    Plus bugs / missing features in LineageOS and bugs introduced by myself porting SODP to LineageOS :silly:

    Sadly I can't upload it at the moment to Android File Host.
    Their new "Stackpath" DDOS blocking solution banned me, because I tried to upload the ROM in 6 browser tabs. :silly:

    Fixed

    Have Fun!

    PS: Camera is work in progress.

    TWRP 10 is not ready, so I sadly can't start develop one for the XZ2, XZ2C, XZ3.
    https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
    That's the reason I include OpenGapps Pico for now.

    And to use Magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
    Maybe you need to deactivate vbmeta, which wasn't the case at my site.

    GCAM doesn't work with OEMv3.
    There is a library missing.
    7
    News

    24.08.2020
    since we have now an official lineageos based on stock, this rom would be double work.
    So i stop the los port.
    (sadly unless a dev owns a xz2p or xz3 these phones won't be supported in the official stock based lineageos)

    the only difference between the stock and sodp editions are:
    Sodp will get gcam support later and has camera2api level 3.
    Stock will never support gcam apps and has the limited stock camera2api level.
    Sodp uses a 4.14 kernel and probably get mainline support later.
    Stock uses the stock 4.9 kernel and will probably be there forever.
    Sodp targets to use as much open source as possible.

    And livedisplay doesn't work in my sodp version.

    Ps: After the september exams in the new semester i look for a rom replacement for the sake of diversity.
    It's good to have a choice and with the available official supported sodp based pixel experiment, we have a rom which sadly forces you to use the full gapps (google apps package).

    13.07.2020
    july security patch level
    oemv9c support
    and any other sodp open source changes since my last build

    18.06.2020
    june security patch level
    oemv8 support
    and any other sodp open source changes since my last build

    fixes for charger, battery, sleep (sideeffect working bluetooth audio) and more!

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

    ps: Camera is work in progress.

    Please flash gapps and the dual sim patcher again after applying an ota update.
    It seems that the ota zip replaces every partition and deletes the modifications (like gapps).
    Also it enforces avb heavily which prevents modifications like gapps from getting loaded.
    So i deactivated avb now.
    (but since the device bootloader can't be relocked the avb is not really useful anyway)

    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
    removed buildin gapps, since you can flash it now via twrp
    installing this rom as an update won't remove the installed gapps.


    ps: Camera is work in progress.


    09.03.2020
    march 2020 security update
    oemv4 -> camera & other improvements
    and any other lineageos / sodp open source changes since my last build

    ps: Camera is work in progress.

    Ps0:
    Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
    Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
    it will get activated in the next aosp release as well, if it makes no trouble.

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


    oemv4 -> camera & other improvements
    and any other lineageos / sodp open source changes since my last build

    ps: Camera is work in progress.

    Ps0:
    Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
    Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
    it will activated in the next aosp release as well, if it makes no trouble.

    29.02.2020
    added support for every sodp supported xperia https://github.com/martinx3-androiddevelopment-lineageos/
    (except the loire and tone platform which no one requested.)

    the oemv4 rom release will delay a bit.
    Was in the need to delete my build cache for aosp and lineageos.

    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.


    oemv4 -> camera & volte & other improvements
    and an other lineageos / sodp open source changes since my last build

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

    15.02.2020
    feburary security patch level
    fixed bugs, now my sony aosp release and this lineageos port should contain the same amount of bugs (aside from the stuff on the lineageos part).
    Switched from alpha to beta version.

    The only instability i found on my own xz2 is a crash at night in flightmode without charger.
    Anything else doesn't crash it here.
    Might be various reasons.
    If anyone has the same bug, please provide logs in my github issue tracker.
    (and please look if your logs contain more informations than my logs).

    02.02.2020
    the first lineageos 17.1 build based on the sodp device trees.
    My vanilla sodp release and lineageos should share the same bugs.
    Plus bugs / missing features in lineageos and bugs introduced by myself porting sodp to lineageos :silly:

    sadly i can't upload it at the moment to android file host.
    Their new "stackpath" ddos blocking solution banned me, because i tried to upload the rom in 6 browser tabs. :silly:

    fixed

    have fun!

    Ps: Camera is work in progress.

    Twrp 10 is not ready, so i sadly can't start develop one for the xz2, xz2c, xz3.
    https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
    that's the reason i include opengapps pico for now.

    And to use magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
    Maybe you need to deactivate vbmeta, which wasn't the case at my site.

    Gcam doesn't work with oemv3.
    There is a library missing.