[ROM][OFFICIAL][pioneer][8.1] LineageOS 15.1

Search This thread

LuK1337

Recognized Developer
Jan 18, 2013
8,836
17,820
Samsung Galaxy S III I9300
Moto G 2014
2okPze5.png


LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), 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.

What's not working :
  • IMS
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][8.1] LineageOS 15.1, ROM for the Sony Xperia XA2

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

ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x

Version Information
Status: Testing

Created 2018-06-19
Last Updated 2019-11-01
 

LuK1337

Recognized Developer
Jan 18, 2013
8,836
17,820
Samsung Galaxy S III I9300
Moto G 2014
How to flash latest firmware

[ protip: Currently Lineage builds depend on latest 8.0 firmware (50.1.A.13.123), they will not boot up on 50.2.A.0.* or newer ]

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:
- kernel_X-FLASH-ALL-18AE_0x00.hash
- kernel_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?
 
Last edited:
G

GuestK00219

Guest
can't test right now but one question. it doesn't really matter at this stage but is it treble compatible? as you know stock rom is but it won't boot anything else

EDIT: what about vendor blobs? are they from stock rom or aosp? camera hal?
 
Last edited:

LuK1337

Recognized Developer
Jan 18, 2013
8,836
17,820
Samsung Galaxy S III I9300
Moto G 2014
can't test right now but one question. it doesn't really matter at this stage but is it treble compatible? as you know stock rom is but it won't boot anything else

EDIT: what about vendor blobs? are they from stock rom or aosp? camera hal?
All blobs are from stock ROM and it's somewhat treble compatible (I could probably make it better by getting rid of /init extensions but eh).
 

TRONTC

Member
Aug 23, 2015
7
0
PUNE
Happy to see development for this device. I don't have a spare phone at the moment so I will flash this once it becomes a bit more stable. Also could you comment on dual sim support. Mine is the H4133 (Hong Kong Version), hopefully there shouldn't be any major hiccups getting it to work. Thanks for porting LOS
 
Last edited:

LuK1337

Recognized Developer
Jan 18, 2013
8,836
17,820
Samsung Galaxy S III I9300
Moto G 2014
Happy to see development for this device. I don't have a spare phone at the moment so I will flash this once it becomes a bit more stable. Also could you comment on dual sim support. Mine is the H4133 (Hong Kong Version), hopefully there shouldn't be any major hiccups getting it to work. Thanks for porting LOS

>I will flash this once it becomes a bit more stable.
So never? I don't expect anything interesting happening with this device anytime soon so you're basically waiting for ~nothing~.

>Also could you comment on dual sim support.
Minimal support is there but it's untested as I only have single sim variant.
 
Last edited:
  • Like
Reactions: Meloferz

li0nh3art3d

Senior Member
Apr 22, 2016
456
134
Texas ?
Does this work on Discovery the same way pioneer TWRP works on Discovery, or probably not?

Also, has Xposed been tested with this ROM?
 

LuK1337

Recognized Developer
Jan 18, 2013
8,836
17,820
Samsung Galaxy S III I9300
Moto G 2014
Does this work on Discovery the same way pioneer TWRP works on Discovery, or probably not?

Also, has Xposed been tested with this ROM?

No, this build does not support discovery. It has a chance to boot on it but you won't have camera.
( There are untested trees in nile-dev @ gitlab if you want to build it on your own )
 
  • Like
Reactions: li0nh3art3d
G

GuestK00219

Guest
sorry, i really didn't mean to. i did it for myself and it wasn't worth creating new thread but i wanted to share. my mistake, i don't plan to make this support thread for my builds
 

LuK1337

Recognized Developer
Jan 18, 2013
8,836
17,820
Samsung Galaxy S III I9300
Moto G 2014
Several months ago I compiled AOSP for my device according to instructions on the Sony Open Devices website. The system could boot, but I could not change the volume during calls. I think H3123 and H3113 has different modems.

>but I could not change the volume during calls
That was an issue for all XA2 and XA2 Ultra devices on SOD, it had nothing to do with modem FYI.
 
Last edited:

LuK1337

Recognized Developer
Jan 18, 2013
8,836
17,820
Samsung Galaxy S III I9300
Moto G 2014
Just out of curiosity, anyone that flashed this ROM can you tell me what fingerprint sensor you have and if it works?

To check that you do `getprop ro.hardware.fingerprint` in adb shell or any terminal app. The output you should get is either "et516" or "fpc1035".
 

RRRex

Member
Jun 24, 2018
6
1
Just out of curiosity, anyone that flashed this ROM can you tell me what fingerprint sensor you have and if it works?

To check that you do `getprop ro.hardware.fingerprint` in adb shell or any terminal app. The output you should get is either "et516" or "fpc1035".

Hey man, thanks for the build and your hard work my device runs like butter compared to stock. Thank you so much amigo. fcp1035 on device h3123 fingerprint not working at the moment. Also no clock or music controls on lock screen. though, I don't know if that's just how lineage 15.1 is.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,836
17,820
Samsung Galaxy S III I9300
Moto G 2014
Hey man, thanks for the build and your hard work my device runs like butter compared to stock. Thank you so much amigo. fcp1035 on device h3123 fingerprint not working at the moment. Also no clock or music controls on lock screen. though, I don't know if that's just how lineage 15.1 is.

>fcp1035 on device h3123 fingerprint not working at the moment.
Can you add me on hangouts ([email protected]) / irc (#titandev @ freenode) / discord (LuK1337#3147)?

>Also no clock or music controls on lock screen. though, I don't know if that's just how lineage 15.1 is.
Uh, did you wipe data? That's just strange.
 
Last edited:

Top Liked Posts

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


    LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), 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.

    What's not working :
    • IMS
    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][8.1] LineageOS 15.1, ROM for the Sony Xperia XA2

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

    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 4.x

    Version Information
    Status: Testing

    Created 2018-06-19
    Last Updated 2019-11-01
    10
    ~ https://review.lineageos.org/218506 ~

    Starting from tuesday pioneer is officially supported device. Because official builds are signed with different key you'll have to wipe data before switching to them unless you feel smart enough to follow https://wiki.lineageos.org/signing_builds.html#using-a-script.

    Also since this change ~ https://review.lineageos.org/219073 you no longer have to care about firmware on slot 'B' :3
    10
    So here's what I did for now:
    - LA.UM.6.2.r1-10300-sdm660.0 -> merged,
    - Call recording -> merged @ https://review.lineageos.org/222506,
    - Power-off alarms -> doesn't work at all,
    - Headset mic -> fixed @ https://review.lineageos.org/223191,
    - HW keymaster×gatekeeper -> https://review.lineageos.org/223180 and https://review.lineageos.org/223184,
    - ANT+ -> won't work.

    I'll let you know when I decide to re-enable builds.
    8
    How to flash latest firmware

    [ protip: Currently Lineage builds depend on latest 8.0 firmware (50.1.A.13.123), they will not boot up on 50.2.A.0.* or newer ]

    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:
    - kernel_X-FLASH-ALL-18AE_0x00.hash
    - kernel_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?