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

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

Search This thread

flexloop

New member
Jan 21, 2019
4
0
No Sim Card

Hi All-

I installed the latest release: lineage-15.1-20190120-nightly-pioneer-signed.zip on a stock XA2 and it can't see the SIM card.

I tried restarting a few times without any success. I have not installed gapps or anything else. I tried wiping the system with TWRP and sideloading again via TWRP with no changes in the symptom.

One clue may be that when I did the wipe I saw this message in red a few times in TWRP: Error "Failed to mount /firmware (Invalid Argument)"
Also, on first boot I get "Bluetooth keeps stopping" message constantly.

Any thoughts?
Thanks!
-Michael
 
Last edited:

Maciek666

Senior Member
May 29, 2016
59
12
Lublin
OnePlus 6
Hi, I have a problem. After updating the phone through the built-in updater, the top and bottom microphones do not work. When you try to make a phone call you can not hear me or the other person. Has anyone had such a problem and if there is any possibility of repairing it. Thank you for your reply.
 

wangenau

Member
Feb 20, 2015
42
124
Hi, I have a problem. After updating the phone through the built-in updater, the top and bottom microphones do not work. When you try to make a phone call you can not hear me or the other person. Has anyone had such a problem and if there is any possibility of repairing it. Thank you for your reply.

For me only one of the microphones does not work. Calling someone works, but if i try to speak to someone while i activate the loudspeaker, he cant hear me.
 

flexloop

New member
Jan 21, 2019
4
0
Hi All-

I installed the latest release: lineage-15.1-20190120-nightly-pioneer-signed.zip on a stock XA2 and it can't see the SIM card.

I tried restarting a few times without any success. I have not installed gapps or anything else. I tried wiping the system with TWRP and sideloading again via TWRP with no changes in the symptom.

One clue may be that when I did the wipe I saw this message in red a few times in TWRP: Error "Failed to mount /firmware (Invalid Argument)"
Also, on first boot I get "Bluetooth keeps stopping" message constantly.

Any thoughts?
Thanks!
-Michael

Ok. The problem appears to be fixed
By the way, this is an h3123.
What I did was restore to factory using flashtool/xperiferm more or less from this:
http://www.xperiablog.net/2016/03/12/install-xperia-marshmallow-using-flashtool-and-xperifirm-guide/

Then I wiped and flashed using twrp per the instructions in this thread.
Then I did the magical dd per this post:
https://forum.xda-developers.com/showpost.php?p=77379268&postcount=342
 

xperiaf

Senior Member
Dec 1, 2018
226
6
Hi All-

I installed the latest release: lineage-15.1-20190120-nightly-pioneer-signed.zip on a stock XA2 and it can't see the SIM card.

I tried restarting a few times without any success. I have not installed gapps or anything else. I tried wiping the system with TWRP and sideloading again via TWRP with no changes in the symptom.

One clue may be that when I did the wipe I saw this message in red a few times in TWRP: Error "Failed to mount /firmware (Invalid Argument)"
Also, on first boot I get "Bluetooth keeps stopping" message constantly.

Any thoughts?
Thanks!
-Michael

you can try to reflash a Stock rom first.

dont forget backing up your data.

Sent from my Sony Xperia XZ1 using XDA Labs
 

bantaman

New member
Jan 5, 2012
4
3
Hi All-

I installed the latest release: lineage-15.1-20190120-nightly-pioneer-signed.zip on a stock XA2 and it can't see the SIM card.

I tried restarting a few times without any success. I have not installed gapps or anything else. I tried wiping the system with TWRP and sideloading again via TWRP with no changes in the symptom.

One clue may be that when I did the wipe I saw this message in red a few times in TWRP: Error "Failed to mount /firmware (Invalid Argument)"
Also, on first boot I get "Bluetooth keeps stopping" message constantly.

Any thoughts?
Thanks!
-Michael

Same problem here. I had to roll it back to Jan 8 build to get it working again.

Strangely, when I was on the Jan 21 build, the SIM would periodically be recognized and then disappear again upon reboot. I did notice a discrepancy in the size of the builds. Jan 8 came in at 617 mb whereas Jan 21 comes in at 599.3 mb. Also noticed that the security patch level on Jan 8 build is Dec 2018 whereas Jan 21 contains the January patch. A little speculative, but just an observation.
 

flexloop

New member
Jan 21, 2019
4
0
Same problem here. I had to roll it back to Jan 8 build to get it working again.

Strangely, when I was on the Jan 21 build, the SIM would periodically be recognized and then disappear again upon reboot. I did notice a discrepancy in the size of the builds. Jan 8 came in at 617 mb whereas Jan 21 comes in at 599.3 mb. Also noticed that the security patch level on Jan 8 build is Dec 2018 whereas Jan 21 contains the January patch. A little speculative, but just an observation.

I thought I was out of the woods with the fixes above but I am missing calls and voicemails are taking a long time to show up.
 

kop316

Senior Member
Nov 9, 2013
76
20
github.com
So uhh ril should be working again in next build(s). Apparently killing sony-modem-switcher ended up triggering same race condition as I used to have in early 16.0 bringup stage so I just picked my fix from 16.0 and it's supposedly fixed.

So while this did fix the issue, I think there still is an issue with phone calls. I attempted to make and recieve a phone call. When I made a phone call the other party was able to get a phone call from, but I never got the "ringing" I expected to make sure that the call was going through. I was also unable to speak or hear anything from the caller.

In addition, when I recieved a call, it looked to connect, but I also was unable to speak or hear anything. The other party said it seemed like I just hung up on them.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,473
16,929
Samsung Galaxy S III I9300
Moto G 2014
So while this did fix the issue, I think there still is an issue with phone calls. I attempted to make and recieve a phone call. When I made a phone call the other party was able to get a phone call from, but I never got the "ringing" I expected to make sure that the call was going through. I was also unable to speak or hear anything from the caller.

In addition, when I recieved a call, it looked to connect, but I also was unable to speak or hear anything. The other party said it seemed like I just hung up on them.
That looks totally different from what I was experiencing. Something is weird on your end.
Try removing /system/app/ims/ims.apk maybe that's it?
 

kop316

Senior Member
Nov 9, 2013
76
20
github.com
That looks totally different from what I was experiencing. Something is weird on your end.
Try removing /system/app/ims/ims.apk maybe that's it?

Thank you for the quick reply!

I still have the issue.

I wiped my phone clean and reinstalled per the LineageOS wiki and tried calling. I attempted what you suggested, rebooted, and confirmed the ims.apk was gone and tried calling again. Both attempts had the same problem.

Edit: Nevermind. Phone calling seems to work fine now. Thank you for looking at it though. I think reinstalling then restarting another time worked.
 
Last edited:

ferlanero

Senior Member
Nov 4, 2008
288
103
León
www.ferlanero.com
Hello. I'm facing some problems with the last Lineage update with the proximity sensor, which is not working on calls, keeping the screen on. Is someone experiencing this issue? What can I do to avoid it? Thanks mates for all your hard work! I love Lineage on the XA2!

Code:
What is your--
LineageOS version: lineage-15.1-20190222-nightly-pioneer-signed
LineageOS Download url: [url]https://download.lineageos.org/pioneer[/url]
Gapps version: MindTheGapps-8.1.0-arm64-20180808_153856
 
Did you--
wipe: Yes
 restore with titanium backup: No
reboot after having the issue: Yes
 
Are you using--
a task killer: No
a non-stock kernel: No
other modifications: No other modifications
 
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: Proximity sensor is not working on calls, keeping the screen on while on a call.
 
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?