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

[ROM][OFFICIAL][pioneer][9] LineageOS 16.0

Search This thread

_Fidor_

Member
Dec 13, 2014
19
1
>1) update locked Sony firmware & Android to latest version
>2) unlock bootloader via developer.sony.com webpage
>3) flash LineageOS 16.0
>4) enjoy Netflix in FHD :)

That's exactly what i did on my XA2 Ultra. Just make sure it's on latest Android P before unlocking it. You can also confirm that it's still L1 on stock before moving to LineageOS.

So far so good - unlocking bootloader on latest XA2 Android keeps L1 Widevine. Next step - TA backup in TWRP :D
 

_Fidor_

Member
Dec 13, 2014
19
1
You won't lose L1 after flashing Lineage but if TA backup will make you feel better go for it.

I'm perfectly aware of it but as they say: "better safe than sorry" :)

Anyway long story short:
1) TWRP does not support TA backup - I had to:
Code:
# dd if=/dev/block/by-name/TA of=/sdcard/Download/TA.img                                                            
4096+0 records in
2) LineageOS 16.0 + OpenGapps + Magisk (Netflix is hidden from root):
- DRM info shows L1
- Netflix shows L3 (and limits playback to 960x540)

Do You have L1 in Netflix by any chance?
 

LuK1337

Recognized Developer
Jan 18, 2013
8,473
16,936
Samsung Galaxy S III I9300
Moto G 2014
I'm perfectly aware of it but as they say: "better safe than sorry" :)

Anyway long story short:
1) TWRP does not support TA backup - I had to:

2) LineageOS 16.0 + OpenGapps + Magisk (Netflix is hidden from root):
- DRM info shows L1
- Netflix shows L3 (and limits playback to 960x540)

Do You have L1 in Netflix by any chance?
I don't have Netflix.

EDIT: Now I do and sure enough it seems to cap at 540p on Lineage but if I go back to stock it's 1080p meaning it's solvable. I'll try to do something about it.
EDIT2: Should be working in next 16.0/17.1 builds. (Also you might want to clear netflix app data)
 
Last edited:

samhhmobil

Senior Member
May 25, 2017
349
187
Hamburg
Hi @LuK1337,

please excuse me, but it seems, there is another issue, this time in Bluetooth. (I'm new to the XA2, I bought it 2weeks ago brandnew, but I'm experienced with older CM/LOS since some years, and I like it.)

When connecting to my cars hands-free-equipment (built-in from factory, european Ford Focus of 2011), the bluetooth-connection is stable for media, contacts and phone. After a few amount of time — sometimes only a few seconds, sometimes more than five minutes — the phone connection is broken and will not reconnect, while bluetooth itself has a stable connection just only for media and contacts. When disconnecting bluetooth manually, and connecting again, phone is there again for seconds/minutes until the bad game begins newly.

I never did see that in earlier Versions of CM/LOS, they all the time did connect stable and flawlessly (CM12.1(M7), LOS14.1(M7, yuga), LOS15.1(Yuga)). What's different in this bluetooth version? Any idea to fix it?

Because I'm frequently long times on the road, it's an important feature to have it stable.

I've just now no log files, if you need, I'll try to catch it.

Thank you very much,
samhhmobil
 

LuK1337

Recognized Developer
Jan 18, 2013
8,473
16,936
Samsung Galaxy S III I9300
Moto G 2014
Hi @LuK1337,

please excuse me, but it seems, there is another issue, this time in Bluetooth. (I'm new to the XA2, I bought it 2weeks ago brandnew, but I'm experienced with older CM/LOS since some years, and I like it.)

When connecting to my cars hands-free-equipment (built-in from factory, european Ford Focus of 2011), the bluetooth-connection is stable for media, contacts and phone. After a few amount of time — sometimes only a few seconds, sometimes more than five minutes — the phone connection is broken and will not reconnect, while bluetooth itself has a stable connection just only for media and contacts. When disconnecting bluetooth manually, and connecting again, phone is there again for seconds/minutes until the bad game begins newly.

I never did see that in earlier Versions of CM/LOS, they all the time did connect stable and flawlessly (CM12.1(M7), LOS14.1(M7, yuga), LOS15.1(Yuga)). What's different in this bluetooth version? Any idea to fix it?

Because I'm frequently long times on the road, it's an important feature to have it stable.

I've just now no log files, if you need, I'll try to catch it.

Thank you very much,
samhhmobil

>What's different in this bluetooth version? Any idea to fix it?
No idea, don't expect me fixing BT issues tbh.
 

samhhmobil

Senior Member
May 25, 2017
349
187
Hamburg
Eh, try cast in next LineageOS update.
Hi LuK1337

what you've done with WiFi-Direct in build of March 2nd was great. It did work flawlessly.

But in one of the following builds something seems to be changed with WiFi (I cannot exactly remember since which build), but with 2.4GHz WiFi breaks down frequently, scans newly for networks and reconnects again. And this is with regular WiFi-Connections AND even with WiFi-Direct, so it's yet even unuseable (again) for cast streams.

Maybe it's not a big thing to figure out what was changed?

Thank you very much,
samhhmobil
 

LuK1337

Recognized Developer
Jan 18, 2013
8,473
16,936
Samsung Galaxy S III I9300
Moto G 2014
Hi LuK1337

what you've done with WiFi-Direct in build of March 2nd was great. It did work flawlessly.

But in one of the following builds something seems to be changed with WiFi (I cannot exactly remember since which build), but with 2.4GHz WiFi breaks down frequently, scans newly for networks and reconnects again. And this is with regular WiFi-Connections AND even with WiFi-Direct, so it's yet even unuseable (again) for cast streams.

Maybe it's not a big thing to figure out what was changed?

Thank you very much,
samhhmobil

I didn't do anything. Also it's 2020, you should move to 5GHz.
 

samhhmobil

Senior Member
May 25, 2017
349
187
Hamburg
I didn't do anything. Also it's 2020, you should move to 5GHz.
You're right, of course, but... the 5GHz net of the AVM FritzBox (7390 and very stable) reaches not further as 5m around... sigh

And even the Miracast Dongles I have are working only in this mode.

But your build from 2020-03-02 did work really great without any trouble! (...and now it doesn't, sigh)

samhhmobil
 

Top Liked Posts

  • There are no posts matching your filters.
  • 36
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    • Download the latest build and gapps
    • Boot to recovery
    • Flash the latest build
    • Boot to recovery again
    • Flash gapps
    • Reboot
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
     
    Did you--
    wipe:
     restore with titanium backup:
    reboot after having the issue:
     
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
     
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    XDA:DevDB Information
    [ROM][OFFICIAL][pioneer][9] LineageOS 16.0, ROM for the Sony Xperia XA2

    Contributors
    LuK1337
    Source Code: https://github.com/LineageOS

    ROM OS Version: Windows 8 Mobile
    ROM Kernel: Linux 4.x

    Version Information
    Status: Testing

    Created 2018-08-30
    Last Updated 2020-02-28
    14
    How to flash latest firmware

    [ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]

    However if you want to flash whole firmware package onto both slots, you can follow the guide below:

    1. Download latest firmware with XperiFirm.
    NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
    Code:
    for f in FILE_*; do unzip $f; done
    unzip boot.zip -d boot
    2. Go to the directory where the firmware got downloaded to and remove following files:
    - boot_X-FLASH-ALL-18AE_0x00.hash
    - boot_X-FLASH-ALL-18AE.sin
    - persist_X-FLASH-ALL-18AE_0x00.hash
    - persist_X-FLASH-ALL-18AE.sin
    - system_other_X-FLASH-ALL-18AE_0x00.hash
    - system_other_X-FLASH-ALL-18AE.sin
    - system_other_X-FLASH-ALL-9B8D_0x00.hash
    - system_X-FLASH-ALL-18AE_0x00.hash
    - system_X-FLASH-ALL-18AE.sin
    - system_X-FLASH-ALL-9B8D_0x00.hash
    - userdata_X-FLASH-CUST-18AE.sin
    - vendor_X-FLASH-ALL-18AE_0x00.hash
    - vendor_X-FLASH-ALL-18AE.sin
    - vendor_X-FLASH-ALL-9B8D_0x00.hash
    3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
    4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
    5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
    6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
    current-slot: _b
    Finished. Total time: 0.001s
    7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
    Setting current slot to 'a'...
    OKAY [ 0.012s]
    Finished. Total time: 0.014s
    or
    Setting current slot to 'b'...
    OKAY [ 0.012s]
    Finished. Total time: 0.014s
    8. Unplug usb cable and repeat steps: 3, 4
    9. Profit?
    7
    @Marteng69 here is what i did -> i was stucked on pie + flickering screen (model h3113):

    1. i used emma (https://developer.sony.com/develop/open-devices/get-started/flash-tool), just install and run it, boot your phone in flash mode (vol down + usb connect = green light). then the app will recognize your phone (assuming you have drivers installed) and give you phone info. on the right side download and flash offered firmware (at the moment there is the uk oreo one, download it and you'll have it in case it's replaced with pie). flash the complete firmware (the "Software Update Content Erase" image) and reboot after flashing completed

    2. boot the phone, let it boot up for a few minutes then turn it off with holding power + vol up for a few secs (let it vibrate 3 times to make sure it's off)

    3. then boot it in fastboot mode (vol up + usb connect = blue light) and then via cmd run "fastboot boot 1d66175c6ce8e04865d041cbcac8ba3013a02b1e.img" (please check your exact .img name)

    4. that's it, the phone should boot (normal looking) twrp and then reboot your phone and... say thanks to @LuK1337 ;)
    7
    Hello Luk,

    are you going to develop LineageOS 17 for this Device?

    Until 50.2.* kernel source is out I'm not planning to do anything.

    btw see https://talk.sonymobile.com/t5/Kernel/50-2-A-0-400-kernel-source/td-p/1390917 ^^
    6
    Yes, 2.4 works fine. I'm 100% sure that 5GHz used to work tho, but nevermind. At least now I have hotspot working lol

    ...yeah I booted some old ass kernel HEAD and it works there. Looks like i'm going to have fun time finding the change that broke it...

    EDIT: Should be working again in next builds ^.^