[ROM] LineageOS 17.1/18.1 UNOFFICIAL - (Update: 2022-05-05)

[Flamefire]

where/how do I get that log?

In PowerAmp: Settings -> audio - > advanced settings -> audio output detection protocol

 

[ortizjammet]

In PowerAmp: Settings -> audio - > advanced settings -> audio output detection protocol

https://imgur.com/a/yYltYdg

 

[Flamefire]

@ortizjammet is this correct now?

 

[jmbattle]

@Flamefire regarding your request, would a Japanese (Docomo) SO-02K variant be acceptable?
I live in Japan, so can probably pick-up a second hand device for a relatively low price.

 

[ortizjammet]

@ortizjammet is this correct now?
View attachment 5452237

yep, now thats perfect as a DAP.

how did you fix this? maybe i can make it work on other devices that didnt have working 24/192 on LOS yet it worked on stock rioms. is this a build.prop edit or something?

 

[Flamefire]

yep, now thats perfect as a DAP.

how did you fix this? maybe i can make it work on other devices that didnt have working 24/192 on LOS yet it worked on stock rioms. is this a build.prop edit or something?

Adjusted the audio_policy_configuration.xml.
However: Do you know if this worked on stock? Can't really see how it would have but TBH I did the modifications mostly by trial & error

 

[FFW]

Hi all, just a quick info from me and a question: As I already wrote I'm still using LOS 17.1/Android 10 as it allows using the Sony camera which Android 11 does not and the benefits of Android 11 compared to 10 are not worth the switch for me.
However with the recent release of Android 12 switching to that becomes worth it due to various improvements over those 2 versions.
However porting a new LOS to a that device isn't easy and requires quite some testing (and I can't even promise I'll succeed)
So in order to keep supporting multiple LOS/Android versions I'd need a spare device for testing.

Hence I'm asking if anyone would be able to donate an XZ1C to me for that. Maybe someone knows someone who has an unused phone, maybe with cracked screen but otherwise working or one which isn't used anymore. Again: I can't promise anything in exchange and I know the XZ1C is still such a good phone that prices aren't exactly low. So this is really meant as an outreach to the community in case anyone has somehow access to an unused phone which I can use for testing and see what I can do with that.
Of course you can tell me which LOS version you use yourself and I'll try and take a bit of extra effort to support that as long as I can.

Thank you all for your support and the nice words here which motivate me to put in that extra effort to provide you with a ROM that works on more than only my device and even one I don't even use myself!

sorry for the late reply. While I don't have a second XZ1 Compact, I have sent you a donation. Maybe that might help for buying one on Ebay or somewhere if you don't have one yet

 

[Flamefire]

sorry for the late reply. While I don't have a second XZ1 Compact, I have sent you a donation. Maybe that might help for buying one on Ebay or somewhere if you don't have one yet

Much appreciated! I might be getting one in the next couple of days hopefully (courtesy of @landsome), but donations are always welcome. Just had to spend a (low) 3 digit amount of €s to upgrade the build machine in preparation for LOS 19. But seems LOS itself isn't yet ready. So got time
But yeah, having a 2nd device I can e.g. revert to stock to compare reception or features would be very handy.

 

[babastutz]

Hello, hope you're all fine

I have some issues here.
I had lineage 18.1 (20210918) working well. I decided to install magisk and pico openGapps. Just for trying, curiosity

I installed Magisk 23. No problem here. All worked nicely.
Then, I went back to TWRP to flash openGapps (open_gapps-arm64-11.0-pico-20211111). Now, impossible to boot my system. The phone boots, gets to the lineage boot animation and reboot to TWRP.

Any ideas ? I don't know what to do.

TWRP : 3.5.2
Lineage 18.1-20210918
Magisk : 23
OpenGapps : open_gapps-arm64-11.0-pico-20211111

 

[Flamefire]

Hello, hope you're all fine

I have some issues here.
I had lineage 18.1 (20210918) working well. I decided to install magisk and pico openGapps. Just for trying, curiosity

I installed Magisk 23. No problem here. All worked nicely.
Then, I went back to TWRP to flash openGapps (open_gapps-arm64-11.0-pico-20211111). Now, impossible to boot my system. The phone boots, gets to the lineage boot animation and reboot to TWRP.

Any ideas ? I don't know what to do.

I had issues with magisk too, see the open issue in their github. So uninstall magisk. If that doesn't help, reflash the rom. If that doesn't help wipe system before flashing which gets rid of gapps too.
If you can get some log output (adb logcat) it would also help. Run the command on pc, plug the phone in and start it until it reboots. Hopefully there is some log info

 

[babastutz]

I had issues with magisk too, see the open issue in their github. So uninstall magisk. If that doesn't help, reflash the rom. If that doesn't help wipe system before flashing which gets rid of gapps too.
If you can get some log output (adb logcat) it would also help. Run the command on pc, plug the phone in and start it until it reboots. Hopefully there is some log info

Hello and thank you for your answer

Finally, I wiped system+cache+data, and installed only "lineage-18.1-20211019-UNOFFICIAL-lilac.zip". So my phone boot again. Great !!
But it seems that magisk, gapps and TWRP are gone. I can't explain for TWRP. Is it normal ? I tried to install it back but have issues with adb now. "device is offline" message...

What a great day hahaha!!

 

[jimmygumble]

Upgraded to lineage-18.1-20211019 build from previous version

Everything works well. Thanks for keeping 'er going!

 

[JDC2389]

Performance is amazing, having periodic signal issues and wifi calling/volte not working, the signal issues tend to happen when in low signal areas and more often when the screen is off. The wifi cuts off sometimes more rarely. Oh right, November security patches are out, update pretty please? <3

 

[Flamefire]

Updates will be there as soon as I got time. Likely in the next 2 days as usual

 

[ezdi]

Any chance you can update the APNs? On 17.1, the defaults for my carrier (T-Mobile US) include a bunch of irrelevant MVNOs, one of which includes a DUN profile so it can't be edited or deleted. Because that also claims to be an IMS profile, it was overriding the proper one. So the radio would just reset repeatedly if WiFi or LTE was available.

I eventually flashed this and got VoLTE working if I force a 3G connection first. I still end up with radio resetting if I lose signal or the only connection is WiFi (have never successfully established a VoWiFi connection). I totally understand if you want to minimize out-of-tree patches though.

I'm still trying to figure out why it requires the modem switcher in xperia parts and I have to do it manually if I lose signal. Could that be related to the bug you found? Unfortunately, needing to manually re-establish connection after going in a big building is kinda a deal killer...

 

[Flamefire]

Any chance you can update the APNs? On 17.1, the defaults for my carrier (T-Mobile US) include a bunch of irrelevant MVNOs, one of which includes a DUN profile so it can't be edited or deleted. Because that also claims to be an IMS profile, it was overriding the proper one. So the radio would just reset repeatedly if WiFi or LTE was available.

I eventually flashed this and got VoLTE working if I force a 3G connection first. I still end up with radio resetting if I lose signal or the only connection is WiFi (have never successfully established a VoWiFi connection). I totally understand if you want to minimize out-of-tree patches though.

Can you specify which profiles are invalid?

I can add those APNs. What is your MCC/MNC? https://android.googlesource.com/device/sample/+/refs/heads/master/etc/apns-full-conf.xml contains many entries fir T-Mobile US

 

[maarek7]

What is default camera here? Snap? Does anybody have an .apk file?

 

[ezdi]

Can you specify which profiles are invalid?

I can add those APNs. What is your MCC/MNC? https://android.googlesource.com/device/sample/+/refs/heads/master/etc/apns-full-conf.xml contains many entries fir T-Mobile US

I feel it was one of the Ting Data profiles. It looks like it could cause a problem, but I don't see IMS on it like I thought it did.

I thought it was 310/260, but now that I look, I'm not seeing anything in the diff that would explain why it isn't getting loaded any more.

So something in my report is wrong. Sorry, I will investigate more and take notes. Or I wonder if I somehow carried over something from Sony or there's something in that zip I installed that did more than just update the file.

 

[Flamefire]

Updates will be there as soon as I got time. Likely in the next 2 days as usual

Sorry guys the updates will take a bit longer after a very unpleasing experience with bootloops and the need for a partial reset of my phone during the tests of the latest update.
As I'm currently quite busy and really need my phone I got to be careful with experiments so either I find enough spare time to test it again to find the cause or I'll likely wait for the test phone which @landsome shipped 3 days ago, so it should be here anytime soon.

@ortizjammet and anyone who wants to play with HD audio:
I attached 2 files which you can try: 1 is the original (renamed as you can see) one the modified one I used to get PA to recognize HD audio. You can try those with:
-

adb root
adb shell mount -o remount,rw /vendor
adb push ./audio_policy_configuration.xml /vendor/etc/audio_policy_configuration.xml

Then reboot. To go back to original reflash LOS or repeat the above with the original file

 

[rez78]

Sorry guys the updates will take a bit longer after a very unpleasing experience with bootloops and the need for a partial reset of my phone during the tests of the latest update.
As I'm currently quite busy and really need my phone I got to be careful with experiments so either I find enough spare time to test it again to find the cause or I'll likely wait for the test phone which @landsome shipped 3 days ago, so it should be here anytime soon.

@ortizjammet and anyone who wants to play with HD audio:
I attached 2 files which you can try: 1 is the original (renamed as you can see) one the modified one I used to get PA to recognize HD audio. You can try those with:
-

adb root
adb shell mount -o remount,rw /vendor
adb push ./audio_policy_configuration.xml /vendor/etc/audio_policy_configuration.xml

Then reboot. To go back to original reflash LOS or repeat the above with the original file

But if i move this file with root explorer (my device is rooted) it will the same? Will work? Thanks