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

[ROM][OFFICIAL][pioneer][11] LineageOS 18.1

Search This thread

Andy_2639

Member
Jun 11, 2020
21
8
Stuttgart
Sony Xperia XA2
After updating to lineage-18.1-20210429 (from lineage-18.1-20210422), I have working IMS registration which means working VoLTE and WiFi-Calling. Great! (H4113, provider: Aldi Talk / Telefonica Germany)

One small bug: In the menu *#*#4636#*#* - Phone information is an option "Mobile Radio Power". When I disable it, the button will switch to enabled again after a short time period - however, the mobile radio still is turned off. To re-enable mobile radio, I have to press the button twice (the first tap brings the button into disabled state, mobile radio keeps turned off; the second tap brings the button in enabled state and actually enables mobile radio).
 
  • Like
Reactions: Zocker1012

samhhmobil

Senior Member
May 25, 2017
346
186
Hamburg
Tho even if it worked it's best to avoid it.
Hmmmmm... OK. (Or not OK.)

So... Android 11 (LOS18.1) is useless on this device (for me).

fbind does not work anymore, due to Googles new "scoped storage policy", adoptable storage can be established, but all data there is corrupted, and just only 32GB of internal storage is much too less in 2021 and in the future.

With LOS17.1 that all did work without any issue. So I've to stay with LOS 17.1... (maybe there will be unofficial security updates in the future?), or throw the XA2 away... 😢

So long,...
samhhmobil
 

Andy_2639

Member
Jun 11, 2020
21
8
Stuttgart
Sony Xperia XA2
Since updating to lineage-18.1-20210429 (from lineage-18.1-20210422), I notice that in the menu *#*#4636#*#* - "Phone information" - "LTE Physical Channel Configuration" no information is displayed. It's just blank. Before the update, it showed something like json about the LTE connection.

Also, in the "network display" (s-meter, next to the battery icon in the status bar), I just see LTE. Before the update it switched between LTE and LTE+.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,465
16,906
Samsung Galaxy S III I9300
Moto G 2014
Since updating to lineage-18.1-20210429 (from lineage-18.1-20210422), I notice that in the menu *#*#4636#*#* - "Phone information" - "LTE Physical Channel Configuration" no information is displayed. It's just blank. Before the update, it showed something like json about the LTE connection.

Also, in the "network display" (s-meter, next to the battery icon in the status bar), I just see LTE. Before the update it switched between LTE and LTE+.
PhysicalChannelConfig is IRadio >= 1.2 and we reverted back to [email protected] so that setting data sub id works again.
 

Andy_2639

Member
Jun 11, 2020
21
8
Stuttgart
Sony Xperia XA2

Attachments

  • KxqasHrKS-OrSRPVRao3Pw_a37eb25444746d67a809a62e6682a1f1c59e30b0.jpg
    KxqasHrKS-OrSRPVRao3Pw_a37eb25444746d67a809a62e6682a1f1c59e30b0.jpg
    245.5 KB · Views: 31
  • wWHCautCR_uM8wE0T5FmLA_527fbb9cec42c6f43513ede0ff9dbff976ed91d7.jpg
    wWHCautCR_uM8wE0T5FmLA_527fbb9cec42c6f43513ede0ff9dbff976ed91d7.jpg
    233.5 KB · Views: 31

eichenbast

Member
Oct 15, 2018
19
2
Hello,

does somebody has experiences with adoptable/adopted storage with LOS 18.1 on XA2?

Installation via commandline/sm runs cleanly, migration of data works without any issue, but...

when accessing data in adopted storage, the files are there, with correct size, but unaccessible again, everything is "corrupted data".

Even Apps, that install to "SDcard" now, are "reset'ted" to initial state like new installation after every reboot. No app can read it's own actual configuration.

Adopted Storage is installed and working without any issue, but it's unuseable. Sigh.

What's to do?

Thanks for any hint,
samhhmobil
Depends from the apps you want to install: for example "Book Reader" works fine and exactly with adopted storage. The same with "MuPDF viewer". OsmAnd nearly good. Others do not save configuration like "AntennaPod" ore "Notepad" - that is annoying, but nothing new; I also had experienced that with other phones. (Use the XA2 without Gapps, no root (Magisk), F-droid).
 

mx82

Senior Member
Dec 9, 2011
109
21
I installed lineage-18.1-20210429 & lineage-18.1-20210513 via OTA update.
Everything works fine, but my GPS is still broken and the signal app does not support pictures > 2.1Megapixel.
Has anybody else the same problem?
 

Sekisouls

New member
May 22, 2021
2
0
Hi,
I have already install this update from lineage 17 to lineage 18 but i have notice that can't use camera app. Every time that try to open it, or try to open the torch to use flash phone, appear a notify that answer me that camera is in use by another app. I've tried to remove camera permissions from apps that use it, but it just doesn't make me remove permission from the settings app, so I guess the problem is here. Hope someone can help me solve or noticed this problem.

Thanks in advance to those who try to help me
 

XTN89

Member
Aug 14, 2013
18
1
I installed lineage-18.1-20210429 & lineage-18.1-20210513 via OTA update.
Everything works fine, but my GPS is still broken and the signal app does not support pictures > 2.1Megapixel.
Has anybody else the same problem?
I have the GPS problem since earlier versions of 18.1. I had hoped that once the official version comes out, this will be fixed. It wasn`t. I posted this issue here several times.
 

Andy_2639

Member
Jun 11, 2020
21
8
Stuttgart
Sony Xperia XA2
The camera app (org.lineageos.snap) crashes. I guess this happens when autofocus fails - e.g. due to really bad light conditions (too dark). I can reproduce it by putting the phone on a opaque surface and than taking a photo which should be completely black.

LineageOS 18.1-20210527-NIGHTLY-pioneer
Baseband 20200722_BY12O_Daily (H4113_Customized-DACHBLX_50.2.A.3.77-R5B)

The attached logcat shows for example:
Code:
05-30 14:28:18.134   720  5633 E mm-camera: <SENSOR><ERROR> imx300_pdaf_calculate_defocus: 332: PDAF calculate defocus, cur_res:0
05-30 14:28:18.764   720  5633 I chatty  : uid=1047(cameraserver) CAM_AF identical 6 lines
05-30 14:28:18.869   720  5633 E mm-camera: <SENSOR><ERROR> imx300_pdaf_calculate_defocus: 332: PDAF calculate defocus, cur_res:0
05-30 14:28:18.964   720  1381 E QCamera : <HAL><ERROR> waitAPIResult: 7752: Timed out waiting for API (23) result
05-30 14:28:18.965   720  5612 E QCamera : <HAL><ERROR> procEvtPrepareSnapshotState: 1811: Error!! cannot handle evt(24) in state(3)
05-30 14:28:18.965   720  1381 E QCamera : <HAL><ERROR> take_picture: 1006: pre_take_picture failed with ret = -38
05-30 14:28:18.966  5563  5609 E CAM_AndroidCameraManagerImpl: take picture failed.
05-30 14:28:18.967  5563  5609 E AndroidRuntime: FATAL EXCEPTION: Camera Handler Thread
05-30 14:28:18.967  5563  5609 E AndroidRuntime: Process: org.lineageos.snap, PID: 5563
05-30 14:28:18.967  5563  5609 E AndroidRuntime: java.lang.RuntimeException: takePicture failed
 

Attachments

  • logcat.zip
    20.7 KB · Views: 1
Last edited:

esemef

Senior Member
Aug 3, 2013
135
38
Thanks for the hard work, this seems to have fixed some of my issues.

Mobile data has not been working in 17.1 for ages & as I had also previously installed magisk and wasn't sure it uninstalled properly, I ended up using EMMA to reinstall the original firmware (twice so it went to both slots).

Then I followed https://wiki.lineageos.org/devices/pioneer/install using these files, which I think might be slightly different since the last time I did a fresh install (around 15.1)

copy-partitions-20210323_1922.zip
lineage-18.1-20210610-nightly-pioneer-signed.zip
MindTheGapps-11.0.0-arm64-20210412_124247.zip

(I did install lineageos, reboot to recovery, install gapps, install lineageos, reboot to recovery and install gapps to make sure both slots had it install as well)

I've spent the day re-installing everything, with just one banking app complaining about the device not being supported (which it just started complaining on 17.1 in the latest update as well).

Data seems to be working again, but I've only tested it with WiFi off & originally on 17.1 it would randomly work on some cell towers before giving up completely.
 

malerocks

Senior Member
Mar 6, 2018
437
103
Thanks for the hard work, this seems to have fixed some of my issues.

Mobile data has not been working in 17.1 for ages & as I had also previously installed magisk and wasn't sure it uninstalled properly, I ended up using EMMA to reinstall the original firmware (twice so it went to both slots).

Then I followed https://wiki.lineageos.org/devices/pioneer/install using these files, which I think might be slightly different since the last time I did a fresh install (around 15.1)

copy-partitions-20210323_1922.zip
lineage-18.1-20210610-nightly-pioneer-signed.zip
MindTheGapps-11.0.0-arm64-20210412_124247.zip

(I did install lineageos, reboot to recovery, install gapps, install lineageos, reboot to recovery and install gapps to make sure both slots had it install as well)

I've spent the day re-installing everything, with just one banking app complaining about the device not being supported (which it just started complaining on 17.1 in the latest update as well).

Data seems to be working again, but I've only tested it with WiFi off & originally on 17.1 it would randomly work on some cell towers before giving up completely.
Since 15.1 was the last time you did a fresh install, its not surprising you were having problems. Its generally recommended to do a fresh install every time there is a major version jump. Also, you don't need to install on both slots, but no harm done
 

Top Liked Posts

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


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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 :
    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:
    6
    @LuK1337 I just wanted to say thank you for your great work! Your work makes our phones live longer, and that's worth real money (donation is on it's way ;-))! I am really happy with how my phone works now. Usually you are only hearing from us when something is not working, which is probably not super motivating :)
    4
    [ 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. Reboot to recovery mode (both Lineage recovery and TWRP will work)
    6. Flash https://androidfilehost.com/?fid=4349826312261712574
    7. Profit?
    4
    As it's already tomorrow and a new build is released, I dare to give a hint:

    dead // 636865636b20746f6d6f72726f77203a5e29
    In the left (input) view, switch the format from binary to hexadecimal.
    3
    So I tried it and it seems to fix the issue. I had now two nights in which the phone charged properly without reboot, while before I had to reboot every evening to make it charge again.

    Please let me know if there is anything else I can do to help debugging!
    Let me know if it still works on April 13th.