yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] moroi:
I installed the same build on Slot A and call works correctly both ways, so the problem is with Slot B.

Slot B was seriously trashed as I was trying to get LOS boot the phone for the first time; I had to format some of the not-to-be-touched partitions and copy the files over - something is still amiss there...

:crying:
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
You can try this and check if it makes B usable:

dd if=/dev/block/bootdevice/by-name/bluetooth_a of=/dev/block/bootdevice/by-name/bluetooth_b

dd if=/dev/block/bootdevice/by-name/dsp_b of=/dev/block/bootdevice/by-name/dsp_b

dd if=/dev/block/bootdevice/by-name/modem_a of=/dev/block/bootdevice/by-name/modem_b
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] SGS3_0:
both sim work fine :good:

What is your--

LineageOS version: lineage-15.1-20180810-UNOFFICIAL-pioneer

LineageOS Download url: https://drive.google.com/open?id=1FwuuxwNci0Uc1iVfd0fbHIXirIBDWSyr

Gapps version:non

Did you--

wipe: clean install +format Data

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

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

I've issue with advanced settings navbar: additional buttons from the left and right - they are untouchable...I can touch only a triangle or a square, but not additional buttons, although they are drawn in their places :rolleyes:
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] moroi:
yeah, calls are working on slot B now!
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] perriinn:
Help please - Key error

Hoping someone here can help me figure out what I have missed. I just got my XA2 (H3123) so I could run an Official Lineage build instead of random other unofficial ones for other devices.

I am getting the "error 18: kDownloadPayloadPubKeyVerificationError". I am using Luk1337's linked TWRP from 'https://androidfilehost.com/?fid=5862345805528057397' although I have tried the official one also and using the instructions 'https://wiki.lineageos.org/devices/pioneer/install'. (by the way Luk1337, you are amazing with the amount of work you have done here and I am glad you were able to get another device)

After reading through this whole thread, I decided to try some of the older versions (back to 20180710) and they all give the same error thinking that the majority of people seem to have had this installed for some time and hoped an older version may have been signed differently. I have tried the whole process 10+ times now, varying things like the ROM version, using adb sideload or twrp install, etc.. and nothing seems to make a difference.

I am not new to using ROMS/root but have never run into key problems like this or used an A/B system. I am going to do some more research on how the A/B works to see if I can identify something I missed there, but other than that I am at a loss at this point.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
>After reading through this whole thread

whoa, you read the whole thread but you skipped #2 post of it. Impressive.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
You should be able to just fastboot boot twrp from #2 post and adb sideload lineage. Do not /install/ TWRP.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] perriinn:
I should not have stated it that way, I am not installing it but running it from fastboot as per the listed instructions. Still getting the error, also tried loading the img while having the A partition active and then with the B partition active.

I am also using the twrp from post #2 but have tried the official one also.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] moroi:
I'm not an expert by any measure, but I'd like to share my hard won experience:

- TWRP (as LuK1337 said, just boot from it, don't try to install) writes to the opposite (inactive) slot when you install the LOS zip, but writes to the current slot when you install gapps (open_gapps in my case). It also marks the inactive slot to become active on the next reboot. As a consequence of this, see below

-you have to reboot to TWRP (not into LOS!) in between installing LOS and gapps; the install document mentions not rebooting until you install all the low level stuff you need, but for an A/B phone you have to - just make sure to not boot into the new LOS install, but into the TWRP still.

Of course, if you don't need gapps or other extras, the above doesn't help that much. I do need a few apps that can be found only in the G store, though.

Good luck!
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
https://www.androidfilehost.com/?fid=3700668719832241496 try this image.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] moroi:
Hi, this one (twrp-3.2.3-0-pioneer-lineage.img) doesn't boot for me - it gets stuck showing the logo screen. (checksum was good)

Official twrp-3.2.3 works though, as I used it to install my unofficial LOS build last week.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
Aww, I set wrong SPL. This image should be fine ~ https://www.androidfilehost.com/?fid=3700668719832241508
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] moroi:
this one works :good:
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] perriinn:
Worked for me too, got me past the loading error. Thank you!!!
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
Can more people confirm that dual SIM is working properly on /latest/ official build as [MENTION=5777799]SGS3_0[/MENTION] claims it works on his own builds?
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] moroi:
20180814-official

Hi,

I installed the 20180814-official build on my H4113, and wanted to report it is looking good so far. It is a clean install (as I was coming from my unofficial build) +open_gapps.

what I was able to test:

-phone call audio works

-phone call audio using the included head set works; there is some crackling and hissing, though

-recording a call works in both above cases, but when using the head set the crackles and hissing are recorded stronger than they were in reality. Makes the recording barely useable

-fast charging works (provided you have the right adapter)

-camera works both for taking pictures and video

-GPS works

-wifi works, both 2.4 and 5 GHz

-mp3's play

-fingerprint works

about the crackling and hissing when using the head set, someone else should try as well, maybe I'm too close to the mic, or something? I'm not using it normally, except for listening to music, and that is not crackling and hissing...

I can't test the second SIM slot unless I get hold of a new one, sorry.

By the way, the second SIM/sdcard slot seems to have something inside to fill the space; that would need to be removed before adding an SD/SIM, correct?
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] perriinn:
I may have found a way to do this without the install of gapps since my plan was to not use it. After I successfully got the newest img installed with gapps the normal way, I went to the trial and error of setup for the way I had initially planned.

I installed the image and then switched to the non-active partition and then rebooted to bootloader. I then loaded back into twrp and went straight to reboot to system and it worked. I did end up with force closes and it looping through reboot (not as much a boot loop since it was rebooting after loading into the lineage setup) but that was fixed with formatting data then a factory wipe.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] struct_t:
Just wanted to note that I successfully updated to the August 14th build via the LineageOS updater. I did not have to wipe data as suspected when switching from SW to HW keystore. Both A and B boot and work fine.

There is an issue in the newer build where attempting to switch my overall OS accent colour in "Style" crashes settings, but it's not a big deal.

Thanks again for your dedication and hard work, [MENTION=5075128]LuK1337[/MENTION]!
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] SGS3_0:
i've same issue what was with you - can't hear anything, just silence

I had same problem early in build 20180718

How fix it?

LuK can u make hot fix for this trouble?(patch?)
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] moroi:
Try to install 20180814 on the other slot and see if it works there. If it does, then you can fix the broken slot by copying the partitions over.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
logcat?
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] struct_t:
Sure, you got it - https://pastebin.com/zz0DFVCz

I think there's a missing resource somewhere, too.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
For some reason overlay manager service isn't starting. You aren't using any funny system mods are you?
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] SGS3_0:
Yes, it works on the other slot. In 1st time active was slot A. Now system in slot B. Audio calls are working now. Some problem with slot A. :confused:
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] struct_t:
Nope, no system mods at all. I also haven't rooted and probably won't need to, either. The only stuff I have that qualifies as anything close to 'overlay' is Night Screen, which is a non-privileged screen dimmer, and it happens regardless of whether night screen is running or not.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] felixborn:
Restore lineage 15.1 on XA2 with TWRP

Hi folks,

i have tried to restore the installed builds 20180710 and 20180814 with twrp-3.2.1-1 - twrp-3.2.3-0 (also the twrp*-lineage.img variants). I restored boot, system and data (tried also boot, system, and data wiped) - but in all combinations lineage is booting forever (logo is moving in infinity).

Is this a problem with twrp or lineage? Is there a workflow for a successful restore?

thanks,

Felix
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] SGS3_0:
OS: lineage-15.1-20180814

reinstall to slot B

GAPPS: MindTheGapps-8.1.0-arm64-20180808

root: Magisk 16.7

Problem:

I just put the phone on the table and went to the kitchen. Then I went back and saw a black screen of smartphone. I tried to unlock ... It does not unlock, only reboot helps. Or it's unlocking with a long(very long) delay. After unlocking the screen (if it happens) - lags... the interface freezes, applications lag behind or do not work. The touches are duplicated (sigle tap = doulble \ multiple tap) ... I used this rom for a couple of days. Everything was fine, and now it's broken ...

Logcat attached.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
Your gapps exploded.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] SGS3_0:
Ok, I'll reinstall LOS and install OpenGapps...

but they work normaly wth other builds...
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
Use mindthegapps.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] silverbluep:
After you do the flash with twrp, did you select boot into recovery? Or did you do regular boot? Once I booted into recovery from TWRP, and then rebooted regularly from the LOS recovery it was ok for me.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] felixborn:
thanks for your advise.

I have tested it. Again infinity boot.

Booting from the restored system to recovery works, but than booting from the LOS recovery to system shows the error.

regards Felix
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] Svrmirac:
I updated too, with no issues.

Can't confirm that changing accent colour crashes anything.

Thanks, [MENTION=5075128]LuK1337[/MENTION] and [MENTION=9324958]struct_t[/MENTION] for letting us know.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] logg84:
Just for curiosity, what camera app are you using ? System One or other?
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] struct_t:
No problem. I've tried a bunch of stuff - cleared cache on Lineage Settlings Storage, Lineage System Settings, and data/cache on the theme packagdsy themselves. I also can't switch my dark mode to "dark" instead of "black", that crashes too. It's not a big deal for me, I figure it'll sort itself out eventually.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] koenvds:
[Q

The 3 important issues that are still troubling me :

Calls are silent. On 2018-07-10, 2018-07-31, 2018-08-14, when calling voicemail, I don't get any sound on earpiece, speaker, earphones or even recording. logcat doesn't look to issue messages specific to the time I try calling.

Needless to say, I'm particularly troubled by the first issue. But for the rest, this is nevertheless a very good and promising ROM for such a recent device.[/QUOTE]

I have the same problem on my H3113 . Everything works fine ( fingerprint , deep sleep , audio ,...)

So I have moved back to stock .
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] moroi:
TWRP flashes the LOS ROM to the opposite (that is, inactive) slot, and then reconfigures it to be the active one upon reboot.

the second dd command in that post had a mistake: dsp_b -> dsp_b - it was writing it onto itself; should have been dsp_a -> dsp_b;

I had the same silent calls issue (both ways, could neither hear or be heard) and they were fixed by dd-ing the dsp_a to dsp_b and modem_a to modem_b. Do note that I established in advance that the A slot was working correctly first.

I had this, too. I do use gapps, which until today I thought was the culprit (or at least the interaction between LOS and gapps).

What I'm doing now is skip the wizard/initial setup altogether (leaving the swipe as the unlock method), then go to settings, configuring all things except the security part; only then I tackle the security and pin.

I noticed that if you see the LOS logo on the screen when you type the pin, that is going to crash and leave you with a set, but unknown pin. If you don't see the LOS logo on the screen when you type the pin, that is the working one. It's like having two set of applications/libraries for the same thing (which makes sense for me as the gapps is supposed to replace some low-level part of the OS, including the wizard); it's like the the wrong one gets called during the wizard :confused:

Hope that helps, for certain it has been the most frustrating part for me.

that is ok I think. It's still encrypted, going by what I have read somewhere.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] Dan Smith:
Thank you for this useful information! This "automagic" behaviour was very confusing to me, although indeed suitable for most uses. I do hope future versions of TWRP could be more verbose about this.

But I'm starting to getting used to and even appreciating this dual-boot functionality.

Yes, I noticed as well that dsp_b was meant to be replaced by dsp_a in this example. Anyway, given the explanation above, it could explain in hindsight all my troubles installing LineageOS in the first place as it was actually performed on system B ! So this manipulation was indeed useful to me.

As for the mute phone problem, I tried for now getting the dsp and modem device block files by installing latest AOSP for H3113 and copying the device files to my LineageOS partition from TWRP, but this still didn't solve it (but neither did it break anything).

Thank to your explanations, I took the courage to try it again after rebooting the phone once everything else was configured, and it worked indeed!

I still find this strange regarding the experience I had with my former Z3 Compact on CyanogenMod/CarbonROM, which was always asking for the device PIN to decrypt data before even the OS began booting.

However it is clear in TWRP that the data partition is now encrypted with the PIN I gave, so I think it does the job of protecting my personal data.

So, in my case, that only leaves the mute phone problem. Any other source of device block files or suggestions for this very annoying issue would be welcome.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
>As for the mute phone problem, I tried for now getting the dsp and modem device block files by installing latest AOSP for H3113 and copying the device files to my LineageOS partition from TWRP, but this still didn't solve it (but neither did it break anything).

just run this:

dd if=/dev/block/bootdevice/by-name/dsp_a of=/dev/block/bootdevice/by-name/dsp_b

dd if=/dev/block/bootdevice/by-name/bluetooth_a of=/dev/block/bootdevice/by-name/bluetooth_b

dd if=/dev/block/bootdevice/by-name/modem_a of=/dev/block/bootdevice/by-name/modem_b

>I still find this strange regarding the experience I had with my former Z3 Compact on CyanogenMod/CarbonROM, which was always asking for the device PIN to decrypt data before even the OS began booting.

>However it is clear in TWRP that the data partition is now encrypted with the PIN I gave, so I think it does the job of protecting my personal data.

https://developer.android.com/training/articles/direct-boot
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] Dan Smith:
I did it already, first my on system as it was (after several tries of installing LineageOS), and then after installing AOSP for H3113 on partition A, and in both cases it did not solve the problem on my device.

I am therefore looking for other sources for working dsp, bluetooth and modem block device files like these. Is there any convenient way of getting them, other than reinstalling stock firmware ?

That was very informative, and does explain why encryption unlocking is not asked anymore during startup, as the decryption is being performed later. Thanks !
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] moroi:
I came to the realization that the battery doesn't last a day given just light usage. l think this is odd as the battery looks impressive on paper (3300mA).

this is the time line for me (official 20180814 + gapps, no other funky stuff):

1:00 - battery 100% phone pulled out of charger as I went to bed.

9:00 - battery was 89%, after sitting idle for about 8 hours; wifi was on, but home wifi signal is strong, so I don't see why that much current was gone.

17:30 - battery was 20% after some light browser usage sessions. We had some friends coming over, so for the most part of the day the phone sat idle, except for some news browsing in the morning and in the afternoon.

All in all, in about 16 hours the battery was down 80%; I think this is excessive. I have obviously google store installed, but only 3 apps, none which would normally run continuously in the background: bitwarden (password manager), protonmail client (it doesn't run in the background, I have to check email by myself), and a banking app.

I have also installed FDroid, and a larger number of apps from there, but nothing stands out.

If I check the battery status, there is about 1h30m of screen time, 4% of current consumed by the browser (fennec) and about 4% by google services (I know, quite a lot for something I haven't clicked on myself). The rest is missing; seems to suggest the OS simply ran very inefficiently.

Note: I know that prior to official 20180718 the battery drainage was appalling: I got 25% used over night with official 20180710; but then it improved, however, I never kept count by how much and if this 20180814 is a regression or this is just the way it behaved before.

What are your experiences related to battery usage on the recent official LOS releases?
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] silverbluep:
I'm on 20180710 and my battery lasts me almost 2 days. With no gapps installed mind you, but i have a number of apps (notably k9mail which runs in the background)
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] struct_t:
Indeed, the style issue sorted itself out after a reboot. Not sure what was going on, but all is well now.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] moroi:
I have identified an intermittent problem with the GPS functionality (using 20180814, but it did happen on earlier releases as well):

Normally I get a GPS lock within seconds and when it works is stable, I have no problems with it.

However, sometimes (it has happened a few times already) I enable position (I normally keep it disabled) and start the mapping app (OsmAnd~ from fdroid - I recommend) only to find that I get absolutely no lock; regardless how much I wait or how many times I restart the app, disable/enable position, it's not working.

When it happened the second time I installed a GPS testing app (GPSTest from fdroid - I recommend) and I could confirm that it wasn't actually seeing any satellite at all, nothing, absolutely blank, like the location was off.

(As a side note, I have an old Nexus 4 with a changed screen which is a known bad combination as it develops GPS issues (due to interference from the wireless antenna) and I can tell how it looks when it sort of manages to detect a few satellites but can't lock the position down for minutes, then when it finally gets a lock it loses it in 10 seconds, etc)

The XA2, on the occasions that it comes up "blind" can't detect one single satellite, absolutely nothing.

Then the next day, when I would use GPS again, it would work flawlessly, getting a lock within seconds even when not all the way out the house - go figure.

Today, after it happened to not work again, regardless how much I tried, I rebooted the phone. Guess what, after reboot, GPS worked perfectly.

Into the speculation territory, the most resonable deduction is that some Android software component that is tasked with running the GPS services crashes at some point, leaving me out of service until the phone is rebooted; I haven't seen any error during general phone utilisation or when I was trying to get the GPS to work.

What now? is this a known issue? can something be done? how does one go about troubleshooting that?...problem being that when you're out and about and you meet the issue you're not in the best position to get a logcat out of the device :)
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] Malizor:
Hi everyone,

I got my brand new XA2 today (H4113) and I would like to flash Lineage OS on it.

However the official install wiki says to backup the TA partition before unlocking the bootloader, but I can't manage to find any relevant procedure for the XA2.

What am I missing?
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
Don't bother doing that.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] Malizor:
Well, this means I won't be able to restore the device if it needs to be sent to warranty :(

But thanks anyway. I guess I will just go ahead and flash.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] sieghartRM:
Hello

If I flash this rom do I need disconnect usb cable from phone to power it on after it has been shut down?

I am asking because on Sony Xperia M2 Nougat Lineage OS I had to disconnect usb cable from phone to power it on after it has been shut down.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] LuK1337:
lol.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] sieghartRM:
Okay from your response, I asume there is no such bugs in this rom.
[Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other] struct_t:
In my experience, there is no reason to keep the TA area around for this phone. The camera quality is unchanged and Sony isn't likely to help you if your bootloader is unlocked anyway, regardless of DRM key status.

---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM ----------

Laugh away, but I have that exact phone sitting on my desk - I use it for streaming media - and I have to do that too! It's crazy. :)