Development [ROM][Unofficial][pdx215][13] Lineage 20 - 2023-03-21

[Sakuu]

Yes Sony Xperia 1 III has gone official and I believe it should be more stable than than March 30th version, since it is unofficial and does not contains all changes merged from March 30th to May 10th in official build with May security patch.

I am currently using the official build and for me it feels smoother and it did get rid of the notification about build using public keys on each reboot.

Edit: Sony Xperia 5 III is also official https://download.lineageos.org/devices/pdx215/changes.

wrong link lmao https://download.lineageos.org/devices/pdx214/changes

 

[sieghartRM]

wrong link lmao https://download.lineageos.org/devices/pdx214/changes

Yeah, I linked in incorrect link (thanks to my browser showing wrong link) thanks for posting correct one.

 

[steveglowplunk]

Been using this rom for a while now and most things are working fine so far. However, there are a few strange quirks here and there so I'd like to ask if anyone has the same issues too.
Do note that I have kirisakura kernel, magisk and LSPosed installed.

1. Screen colour calibration through "settings - display - LiveDisplay" resets on reboot
2. When using 120 hz screen refresh rate (settings - display - smooth display), the minimum screen brightness allowed is slightly lower than that of 60 hz, which makes the screen display a purple tint on lowest brightness (likely an OLED screen quirk). It would be great to make the minimum brightness allowed the same as that of 60 hz.
3. "Double" tap to wake (settings - display - tap to wake) actually takes like a dozen taps to wake the phone after screen off for a while (not sure how long to trigger this glitch, works fine if you double tap shortly after locking the phone)
4. Home long press action (settings - buttons - home long press action) does nothing (although likely to be a problem on LineageOS's side). Also, the long press time on back button is way too short (it used to be 2 seconds on LineageOS 15.1). It's ever slightly irritating since I use back button long press to kill foreground apps, and the short delay makes it easy to accidentally trigger the kill.

Update:
Problem 4 is fixed on official LOS 20, version 20230510-nightly.

Home long press action now works on official version 20230510-nightly, on a fresh install.
As for the other problems, they remain unfixed.

Edit:
The point about minimum screen brightness seems to have been fixed too, though it's really is fixed by automatically switching to 60 hz on low brightness.

 

[kevinmcmurtrie]

Sweet! I see an official LOS!
Does anyone know if this fixes (or enables fixing) crippled carrier features? My biggest complaint about the XQ-BC62 is no VoWiFi and effectively disabled 5G on T-Mobile (SA/NSA settings are reversed for all but NR41).

 

[DrDrag0n]

Sweet! I see an official LOS!
Does anyone know if this fixes (or enables fixing) crippled carrier features? My biggest complaint about the XQ-BC62 is no VoWiFi and effectively disabled 5G on T-Mobile (SA/NSA settings are reversed for all but NR41).

Yip 5g + VOLTE & VOWIFI are enabled on custom roms. I'm using them now

 

[steveglowplunk]

Sorry to keep bugging this thread but there's another small problem.
Notification light brightness (settings - notifications - notification light - brightness levels) does not seem to actually apply when there are real notifications (like emails or messaging apps notifications). Or is it the expected behaviour that notification lights go on full brightness regardless of the brightness settings when "choose colours automatically" is on?
I would really like to be able to limit the brightness of the notification LED light, since it's way too bright by default.

 

[kevinmcmurtrie]

Yip 5g + VOLTE & VOWIFI are enabled on custom roms. I'm using them now

They're definitely not working on my phone (XQ-BC62). WiFi calling can be turned on but it can't be used. 5G still doesn't work. The only change is that the phone no longer lies about having 5G.

I've been trying to fix the Qualcomm config but can't get QPST working in a Windows VM. I'm probably just installing malware.

Edit: I found Sony's MBN file and it's clearly incorrect for North America T-Mobile.

 

[kevinmcmurtrie]

I've been using LineageOS for on a XQ-BC62 a week now and it's good!

Broken stock, broken in LineageOs:

• 5G crippled in MBN files
• VoWiFi on T-Mobile
• USB 3 data unstable (probably chipset)

Broken in LineageOs, works stock:

• Google Wallet (Google's fault)
• Two-level notification LED (dim color for charge state + brighter blink for notifications)
• Notification LED and lock screen notification brightness don't follow ambient light
• MicroSD card shows corrupted after using it in a computer

Fixed in LineageOs, broken stock:

• LTE/5G indicator
• Screen brightness following ambient light
• Lock screen notification content
• Fingerprint, touchscreen, and UX stability while phone is in hand

 

[steveglowplunk]

I've been using LineageOS for on a XQ-BC62 a week now and it's good!

Broken stock, broken in LineageOs:

• 5G crippled in MBN files
• VoWiFi on T-Mobile
• USB 3 data unstable (probably chipset)

Broken in LineageOs, works stock:

• Google Wallet (Google's fault)
• Two-level notification LED (dim color for charge state + brighter blink for notifications)
• Notification LED and lock screen notification brightness don't follow ambient light
• MicroSD card shows corrupted after using it in a computer

Fixed in LineageOs, broken stock:

• LTE/5G indicator
• Screen brightness following ambient light
• Lock screen notification content
• Fingerprint, touchscreen, and UX stability while phone is in hand

What do you mean by the point "Two-level notification LED"? In my situation, I can dim the charging lights but the notification lights remain at full brightness regardless of settings, which is annoying.
Also, micro sd card works for me after using it on a Windows pc and even an ipad (yes) through a usb reader. Although I have the card formated in exfat.

 

[kevinmcmurtrie]

What do you mean by the point "Two-level notification LED"? In my situation, I can dim the charging lights but the notification lights remain at full brightness regardless of settings, which is annoying.
Also, micro sd card works for me after using it on a Windows pc and even an ipad (yes) through a usb reader. Although I have the card formated in exfat.

When charged, the notification LED had a slight green glow and then pulsed more brightly for a notification. Both followed ambient light. I seem to be able to turn down the charging LED intensity in LineageOS but the others only support full-on or full-off of an LED color. Notifications were always FUBAR in stock so the imperfections in LineageOS are still a huge improvement.

LineageOS claimed that the microSD card was corrupted coming off stock. Two more times it claimed the microSD card was corrupted after using it in a Linux computer. Nothing else can detect corruption so I don't know why it's complaining. Logcat showed a permissions error right before it failed to mount. Maybe it can't fix that weird file that looks like an improvised transaction log? There's 600+ GB on my card so I'm scared to try taking it out again. This phone has an intermittent USB 3 interface so that means slowly repopulating it with USB 2 or CIFS/Ethernet. It takes a day. I can't find a spare card at the moment - I always find a use for them.

 

[steveglowplunk]

Been using this rom for a while now and most things are working fine so far. However, there are a few strange quirks here and there so I'd like to ask if anyone has the same issues too.
Do note that I have kirisakura kernel, magisk and LSPosed installed.

1. Screen colour calibration through "settings - display - LiveDisplay" resets on reboot
2. When using 120 hz screen refresh rate (settings - display - smooth display), the minimum screen brightness allowed is slightly lower than that of 60 hz, which makes the screen display a purple tint on lowest brightness (likely an OLED screen quirk). It would be great to make the minimum brightness allowed the same as that of 60 hz.
3. "Double" tap to wake (settings - display - tap to wake) actually takes like a dozen taps to wake the phone after screen off for a while (not sure how long to trigger this glitch, works fine if you double tap shortly after locking the phone)
4. Home long press action (settings - buttons - home long press action) does nothing (although likely to be a problem on LineageOS's side). Also, the long press time on back button is way too short (it used to be 2 seconds on LineageOS 15.1). It's ever slightly irritating since I use back button long press to kill foreground apps, and the short delay makes it easy to accidentally trigger the kill.

Update:
Problem 4 is fixed on official LOS 20, version 20230510-nightly.

I now might have an idea as to why home long press action doesn't work.
If you disabled "hold home for assistant" through settings - system - gestures - system navigation - 3-button navigation - hold home for assistant, home long press action in the buttons settings won't work.
I might have disabled this setting in my previous installtion without realising it. So it's my mistake after all.

 

[Andrew Lin]

Has anyone made photography pro work here? Thanks!

 

[clfbbn]

Has anyone made photography pro work here? Thanks!

Xperia Camera - Google Drive

drive.google.com

 

[Andrew Lin]

Thanks a lot!
I wonder if it's possible to make Dolby Atmos work too The speakers just don't sound as full as stock with Dolby

 

[clfbbn]

Thanks a lot!
I wonder if it's possible to make Dolby Atmos work too The speakers just don't sound as full as stock with Dolby

Sadly this will not be supported

 

[redroseblackrose]

Xperia Camera - Google Drive

drive.google.com

Really appriciated! That has removed the last pain-point for me and it feels amazing that I'm able to use LOS without any compromises (from my perspective)! I will donate to lineage since you said you don't want any but really I'm so happy and thankful for your work!

I'm a bit new to such modding, might I ask how you did to get the apk, and to get it to install, use the shutter button etc.? Is it possible/will you upload new apks if sony ever updates their apps? Actually for example it seems like photography pro was updated last on 13 june (version 1.5.1.A.1.0) according to apkmirror..

Second question: Since this is official now, where should one report bugs one finds using the device? Is it here: https://gitlab.com/LineageOS/issues/android tagged with pdx215 or do you prefer somewhere else?

Can we regard this as a thread about the official LOS version now?

 

[Poluvagon hopper]

Hi! I'm flashing latest version Lineage OS from XQ-BC52.
Flashing without errors, bootloader unlocked, adb-debugging "on", drivers installed, and have some problem:
1. Internal memory 110 GB, but not 256 GB.
2. Display brightness level changed without control me (brighter, dimmer), when automatically brightness disabled.
3. Without Gapps some apps working incorrect.
4. App messages can't delete message.
Good luck and Thanks!)

 

[ilukin]

Hi!
I want to try LinageOS 20 on my XQ-BC72, and I want to save the opportunity to return to stock if something will go wrong. But I can not find any information about it. Should I backup existing firmware or I can download it with XperiFirm and flash it? Is there an instruction somewhere to how to return stock ROM after LinageOS or other custom firmware?

3. Without Gapps some apps working incorrect.
4. App messages can't delete message.

3. Can you tell which apps are working incorrect, and what does it look like? Did you try microG or just clean LineageOS?
4. What did you mean? You can not delete SMS or any messengers can not delete their messages?

 

[UsernameNotRecognized]

Hi!
I want to try LinageOS 20 on my XQ-BC72, and I want to save the opportunity to return to stock if something will go wrong. But I can not find any information about it. Should I backup existing firmware or I can download it with XperiFirm and flash it? Is there an instruction somewhere to how to return stock ROM after LinageOS or other custom firmware?


3. Can you tell which apps are working incorrect, and what does it look like? Did you try microG or just clean LineageOS?
4. What did you mean? You can not delete SMS or any messengers can not delete their messages?

You don't need to do anything.
By far the easiest way is to use emma to flash back stock.
Then lock bootloader and let the internal updater do it's thing.
Depending on what emma offers for you to install and what you've selected you will be running an outdated version of android. The older the more updates you need, but this is (at worst) about 10 reboots and it won't make your device unusable or anything.

 

[Poluvagon hopper]

Hi!
I want to try LinageOS 20 on my XQ-BC72, and I want to save the opportunity to return to stock if something will go wrong. But I can not find any information about it. Should I backup existing firmware or I can download it with XperiFirm and flash it? Is there an instruction somewhere to how to return stock ROM after LinageOS or other custom firmware?


3. Can you tell which apps are working incorrect, and what does it look like? Did you try microG or just clean LineageOS?
4. What did you mean? You can not delete SMS or any messengers can not delete their messages?

Just flashing stock with Flashtool, downloading OS with XperyFirm. You can find instructions in other themes Sony Xperia, they all +- the same.
3. In my phone incorrect worked app "Bolt" (taxi), he need Google Maps.
4. I not written log error sending messagea, I just flashing back stock