[ROM][11] LineageOS 18.1 [OFFICIAL]

[House3272]

I had a similar issue while my XZ2c was running the stock OS, had to open the phone up to replace the microphone which then fixed it. It's worth replacing the battery during the process if the phone is opened up. If possible, I would try to temporarily reinstall the stock OS to try rule out any possible hardware failures before attempting to open the phone up though. It is very easy to ruin the display panel by poking the thin plastic sheet too far under the display. I've ruined 3 out of 5 display panels this way on various phones and had to buy replacements.

Nah my physical mic itself is fine. Recorder app works no problem.
I'm already needing to replace the display, so probs will look into the battery just in case thanks for tip.

But my issue turns out is with T-Mobile.
The stupid sim only works for like 15 seconds and it only works after I put it in my Xz1c, boot, then take it out and put it in Xz2c haha.
I thought the VoLTE problem is fixed in Lineage 18???

Anyone else using this rom with T-Mo in the US?

 

[zpunout]

Nah my physical mic itself is fine. Recorder app works no problem.
I'm already needing to replace the display, so probs will look into the battery just in case thanks for tip.

But my issue turns out is with T-Mobile.
The stupid sim only works for like 15 seconds and it only works after I put it in my Xz1c, boot, then take it out and put it in Xz2c haha.
I thought the VoLTE problem is fixed in Lineage 18???

Anyone else using this rom with T-Mo in the US?

There are two microphones. It's still possible one of them is not working despite the recorder app working. There's a handy app in the F-Droid repository called Fairphone Checkup which tests each microphone separately.

Can't comment on VoLTE as I have a budget carrier which drops back to WCDMA for calls.

 

[zpunout]

For anyone thinking of going to the S10e as your next compact phone: don't.

I just purchased one and promptly returned it. The battery life was atrocious. I was loosing a percentage of battery every few minutes just browsing the internet. I can't imagine getting through a normal day without having to charge it at least twice.

I might try and wait for the Android 6A as it's relatively compact and cheap and has a decent battery. Does anyone have any other suggestions for a compact phone?

Finally, apologies to the developer of this rom. Your work is amazing. I'll take these minor data issues over horrible battery life any day.

I'm off topic as this is an XZ2c thread, but my S10e battery is way better than the one you had. Nevertheless, I miss using my comfy XZ2c as a daily driver while I'm messing around with an unofficial LineageOS 19 on it and frequently performing factory resets.

 

[landsome]

I'm off topic as this is an XZ2c thread, but my S10e battery is way better than the one you had. Nevertheless, I miss using my comfy XZ2c as a daily driver while I'm messing around with an unofficial LineageOS 19 on it and frequently performing factory resets.

Same here. My S10e lasts one day of moderate use (and I always charge it to 85%). Plus it gets its monthly updates regularly and Samsung's A12 (much as I dislike OneUI in general) has the nice old regular quick tiles, not the atrocious bubbly design. It's a bit too large, but considerably lighter than the XZ2c, has a jack, a fast SD, generous memory, and takes very good - if oversaturated - photos.

 

[House3272]

There are two microphones. It's still possible one of them is not working despite the recorder app working. There's a handy app in the F-Droid repository called Fairphone Checkup which tests each microphone separately.

Can't comment on VoLTE as I have a budget carrier which drops back to WCDMA for calls.

Dude thanks!
Primary mic was in fact busted on that phone.
But thankfully all working fine on my second one.

T-Mobile still booting me off into Emergency Calls only mode for some reason, but at least the mic issue I know is separate now. Thanks.

 

[q4q9x]

is there any particular OpenGApps which is recommended for use with this ROM?

 

[landsome]

is there any particular OpenGApps which is recommended for use with this ROM?

Always used pico without issue.

 

[userx404]

Satusbar:

Anybody encounter similar alignment issue when enableing traffic monitor?
It seems to be always placed center aligned, irrelevant what other symboles are shown (right aligned)

(German UI)
Settings->System->Statusbar->Traffic Monitor

 

[DrTrax]

Have a question;

What are these DSUs and why are they only for Android 12 and 13 (according to Google own repository) :/

S3B1 is Android 12
TPBB is Android 13

 

[zpunout]

Satusbar:

View attachment 5632585

Anybody encounter similar alignment issue when enableing traffic monitor?
It seems to be always placed center aligned, irrelevant what other symboles are shown (right aligned)
View attachment 5632587
(German UI)
Settings->System->Statusbar->Traffic Monitor

Yes, this little quirk exists on various devices I've installed custom Android operating systems onto. It also happens on Android 12

 

[zpunout]

Have a question;

What are these DSUs and why are they only for Android 12 and 13 (according to Google own repository) :/

S3B1 is Android 12
TPBB is Android 13

View attachment 5632623

I learnt from here: https://developer.android.com/topic/dsu
that Dynamic System Updates is a feature to be able to install a Generic System Image, a generic Android operating system.
The GMS options in your screenshot are the versions which include Google's system services. The DSU Loader option is not only for the XZ2 Compact, but is also generally found in LineageOS across multiple devices and some other operating systems which support Treble. There are YouTube videos which show how it works.

 

[DrTrax]

So basically with LOS 18.1 (Android 11) I can "test" Android 12 and 13 from Google just for fun and then switch back to LOS without any kind of risk...

A feature from Google, not intended but also not blocked by Lineage OS because of reasons (?)

 

[userx404]

Hi @dtrunk90
Comming from 'lineage-18.1-20220603-nightly-xz2c' I ran into troubles with latest 'lineage-18.1-20220610-nightly-xz2c-signed.zip'.
The in-system-updater performed the update but after restart it could not boot properly.
This leads to recovery (18.1 20220610) asking for retry or factory reset.
If i want to install the zip manually within recovery the verification failed with message:
Package is for xz2c but expected H8324.
It looks like recovery got updated correctly but there are issues with the rom package.
I wonder because there are no differences listed at los changelog.

Now i have troubles to get my device back running without data loss.
- Tried to flash 0603 from sd zip and adb sideload on recovery 20220610
- Tried to flash 0603 from sd zip and adb sideload on recovery 20220603
but always ends at the recovery Try again or factory reset screen. :-(

 

[dtrunk90]

Hi @dtrunk90
Comming from 'lineage-18.1-20220603-nightly-xz2c' I ran into troubles with latest 'lineage-19.1-20220610-nightly-xz2c-signed.zip'.
The in-system-updater performed the update but after restart it could not boot properly.
This leads to recovery (18.1 20220610) asking for retry or factory reset.
If i want to install the zip manually within recovery the verification failed with message:
Package is for xz2c but expected H8324.
It looks like recovery got updated correctly but there are issues with the rom package.
I wonder because there are no differences listed at los changelog.

Now i have troubles to get my device back running without data loss.
- Tried to flash 0603 from sd zip and adb sideload on recovery 20220610
- Tried to flash 0603 from sd zip and adb sideload on recovery 20220603
but always ends at the recovery Try again or factory reset screen. :-(

The good thing on A/B devices is you could switch slots and get back to a running system. But since you already flashed stuff again this is not possible anymore because both A and B slots are broken now. You could try to enable ADB in recovery and make a backup of your data. We're official on 19.1 since today and there will be no more 18.1 builds anyway.

 

[FoobyKamikaze]

So I was able to buy a new XZ2C Rev2 H8314, my first smartphone. After two weeks of troubleshooting with Metro by T-Mobile in the USA it was only ever able to connect to their network twice on June 16th and 17th The first time I was on LineageOS 18 and after I completed the first call it was kicked back off. The second time was on the stock firmware which was Canada 52.0.A.11.32-R4B, never all but voice calls worked and was connected for about 7 hours until I turned off the phone to go to sleep and in the morning 0 bars and "emergency calls only". (that firmware seems to be the only version that I tested with full VoLTE enabled and toggle-able in the settings and service menu)

I tried Consumer Cellular with the stock Canada 52.0.A.11.32-R4B, and the phone instantly connected to the network but could not make calls. Attempting to do so resulted in immediate "call ended". I tried LineageOS again yesterday (6-10 build) using the most recent USA firmware on xperifirm, 52.1.A.3.137-R7C, but had the same issue with voice calls failing immediately with "call ended". I also saw a notification that said "slot0, modem configuration 28957.1, firmware file default ". I noticed something in this thread about adding modem configs so today I flashed the UK customized version which I had seen mentioned, 52.1.A3.49-R6C with the same result but the notification has changed to "slot0, modem configuration S263.1, firmware file default ". I have an old Iphone 6+ which does work fine with the SIM.

Is there something else that I am missing? I know I am out of my depth, had to figure out emma, xperifirm and newflash as well as unlocking the bootloader for lineageOS so I could have missed some step. I had issues with the google apps using the "mindthegapps" link as it would get stuck in a loop trying to copy files from an XZ2 Compact device without an option to say no, the Open GAPPs nano worked fine.

 

[dtrunk90]

So I was able to buy a new XZ2C Rev2 H8314, my first smartphone. After two weeks of troubleshooting with Metro by T-Mobile in the USA it was only ever able to connect to their network twice on June 16th and 17th The first time I was on LineageOS 18 and after I completed the first call it was kicked back off. The second time was on the stock firmware which was Canada 52.0.A.11.32-R4B, never all but voice calls worked and was connected for about 7 hours until I turned off the phone to go to sleep and in the morning 0 bars and "emergency calls only". (that firmware seems to be the only version that I tested with full VoLTE enabled and toggle-able in the settings and service menu)

I tried Consumer Cellular with the stock Canada 52.0.A.11.32-R4B, and the phone instantly connected to the network but could not make calls. Attempting to do so resulted in immediate "call ended". I tried LineageOS again yesterday (6-10 build) using the most recent USA firmware on xperifirm, 52.1.A.3.137-R7C, but had the same issue with voice calls failing immediately with "call ended". I also saw a notification that said "slot0, modem configuration 28957.1, firmware file default ". I noticed something in this thread about adding modem configs so today I flashed the UK customized version which I had seen mentioned, 52.1.A3.49-R6C with the same result but the notification has changed to "slot0, modem configuration S263.1, firmware file default ". I have an old Iphone 6+ which does work fine with the SIM.

Is there something else that I am missing? I know I am out of my depth, had to figure out emma, xperifirm and newflash as well as unlocking the bootloader for lineageOS so I could have missed some step. I had issues with the google apps using the "mindthegapps" link as it would get stuck in a loop trying to copy files from an XZ2 Compact device without an option to say no, the Open GAPPs nano worked fine.

Both S28957.1 and S263.1 configs are missing. I'll check later if i can fetch them from the stock firmwares so they're available with the next 19.1 build. 18.1 is not officially supported anymore.

 

[dtrunk90]

So I was able to buy a new XZ2C Rev2 H8314, my first smartphone. After two weeks of troubleshooting with Metro by T-Mobile in the USA it was only ever able to connect to their network twice on June 16th and 17th The first time I was on LineageOS 18 and after I completed the first call it was kicked back off. The second time was on the stock firmware which was Canada 52.0.A.11.32-R4B, never all but voice calls worked and was connected for about 7 hours until I turned off the phone to go to sleep and in the morning 0 bars and "emergency calls only". (that firmware seems to be the only version that I tested with full VoLTE enabled and toggle-able in the settings and service menu)

I tried Consumer Cellular with the stock Canada 52.0.A.11.32-R4B, and the phone instantly connected to the network but could not make calls. Attempting to do so resulted in immediate "call ended". I tried LineageOS again yesterday (6-10 build) using the most recent USA firmware on xperifirm, 52.1.A.3.137-R7C, but had the same issue with voice calls failing immediately with "call ended". I also saw a notification that said "slot0, modem configuration 28957.1, firmware file default ". I noticed something in this thread about adding modem configs so today I flashed the UK customized version which I had seen mentioned, 52.1.A3.49-R6C with the same result but the notification has changed to "slot0, modem configuration S263.1, firmware file default ". I have an old Iphone 6+ which does work fine with the SIM.

Is there something else that I am missing? I know I am out of my depth, had to figure out emma, xperifirm and newflash as well as unlocking the bootloader for lineageOS so I could have missed some step. I had issues with the google apps using the "mindthegapps" link as it would get stuck in a loop trying to copy files from an XZ2 Compact device without an option to say no, the Open GAPPs nano worked fine.

I've downloaded ALL 200+ latest tama (xz2, xz2c, xz2p, xz3) stock firmwares now and extracted all the modem configs out of them to add missing ones: https://review.lineageos.org/c/LineageOS/android_device_sony_tama-common/+/333483

But still, there was no S28957.1 and no S263.1.
I don't know where to get them from.
If you know how feel free to add them: https://wiki.lineageos.org/how-to/submitting-patches

 

[dtrunk90]

This thread is unwatched by me now since there are no more official 18.1 builds. Pls move over to the 19.1 thread. Thanks.

 

[landsome]

Hi! Any chance to find somewhere for download the last LOS18.1 build (and associated recovery)? Thanks.

 

[cuynu]

Hi! Any chance to find somewhere for download the last LOS18.1 build (and associated recovery)? Thanks.

.