[ROM][OFFICIAL][discovery][10] LineageOS 17.1

LuK1337

Recognized Developer
Jan 18, 2013
8,172
16,425
253


LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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 /proc/last_kmsg. (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][discovery][10] LineageOS 17.1, ROM for the Sony XA2 Ultra

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

ROM OS Version: Windows 8 Mobile

Version Information
Status: Testing

Created 2019-10-23
Last Updated 2020-04-01
 

LuK1337

Recognized Developer
Jan 18, 2013
8,172
16,425
253
[ 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=4349826312261769960 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?
 
Last edited:
Jul 25, 2019
45
26
28
Sourceforge under "beta" folder

---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------

Here's the link

https://sourceforge.net/projects/opengapps/files/arm64/

---------- Post added at 11:20 PM ---------- Previous post was at 11:17 PM ----------

Another thing I would like to mention is the "nano" packets was give me issues it would freeze when I tried typing the pin to the fingerprint part of the setup. I am running Pico now and I have had no issues?
 

appleknight

Senior Member
Mar 23, 2013
393
122
63
OK so far the only issue I've seen is not being able to set the dark mode to black, it just reverts back to normal dark mode, other than that no issues here! Great work man!

Update: If I try connecting to a public WiFi that requires a login, when I click "sign in to network" that function just crashes, however regular WiFi at home works great.
Also, expanded desktop crashes the settings app when you try going into it
I'll be able to send you a logcat when I get home(about 8hrs from now)
 
Last edited:

LuK1337

Recognized Developer
Jan 18, 2013
8,172
16,425
253
OK so far the only issue I've seen is not being able to set the dark mode to black, it just reverts back to normal dark mode, other than that no issues here! Great work man!

Update: If I try connecting to a public WiFi that requires a login, when I click "sign in to network" that function just crashes, however regular WiFi at home works great.
Also, expanded desktop crashes the settings app when you try going into it
I'll be able to send you a logcat when I get home(about 8hrs from now)
Don't bother sending a logcat for expanded desktop.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,172
16,425
253
Sorry for bothering, I'm just not really sure.
If I flashed recent Sony full stock 50.2 firmware with Newflasher, does it mean I am on both slots with it? :confused:
It depends how you flashed it. You can do `strings /dev/block/bootdevice/by-name/modem_* | grep Daily` in TWRP. If you see both dates starting with 2019 then you probably have some kind of 50.2 on both slots.
 

lonewolfbtown

Senior Member
Jun 28, 2017
245
62
38
Phoenix
I'm sure I either did something wrong or I misread but I currently have no fingerprint.
Also things I noticed which are not concerns
Exposed is wonky
Pin will crash ui and then give u blank unknown pin
Not important but substratum cause lag
Only things I've notice
 

razider

Member
Aug 5, 2013
22
0
0
Siemano.

My question is: what kind of gapps is recommended for this build?

Since it says its android 10 I thought it should be this one:

opengapps/files/arm64/beta/
But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28). Which one should I pick?
 

LuK1337

Recognized Developer
Jan 18, 2013
8,172
16,425
253
Siemano.

My question is: what kind of gapps is recommended for this build?

Since it says its android 10 I thought it should be this one:

opengapps/files/arm64/beta/
But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28). Which one should I pick?
>But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28).
re-boot twrp.
 

razider

Member
Aug 5, 2013
22
0
0
And the gapps should be arm64. Is that true?
When I tried to to install gapps for LOS 16.1 it said I should go with "arm", I'm assuming instead of arm64.

(I tried to reboot TWRP after flashing rom)
>But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28).
re-boot twrp.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,172
16,425
253
And the gapps should be arm64. Is that true?
When I tried to to install gapps for LOS 16.1 it said I should go with "arm", I'm assuming instead of arm64.

(I tried to reboot TWRP after flashing rom)
Something tells me that you didn't do it.

Install lineage, boot twrp again, install gapps.

Also yes, use ARM64.