Thank you so much for looking into this for us. It works great now.
[ROM][13][XZ2C][OFFICIAL] LineageOS 20.0
- Thread starter dtrunk90
- Start date
Hi mate,
I've been trying & hoping to get the XZ2 Compact (dual SIM H8324) work with VoLTE in Australia.
The phone was originally bought in Europe and when updated to the official Telefonica/O2 Central Europe Android 10 firmware, VoLTE did work on O2 in Czech Republic.
I am now back in Australia and my current carrier, Vodafone AU, is to switch off all 3G services by the end of this year, so without VoLTE capability, the phone will not be of much use here.
It is a pity because I like the smaller format of this phone and with the LOS 20.0 upgrade, it works better than many newer models.
You did mention elsewhere that you extracted all the available firmwares and those were included in one of the LOS 19 nightlies.
So this is probably a long shot, but there appears to be a lone Australian firmware available via Xperifirm, called H8324_Customized AU_52.1.A.3.49-R4C
Is there any way to find out whether this may have the necessary config files for any of the Australian carriers? Or have you already included it in the LOS ROM?
Thanks a lot for all your work!
I've been trying & hoping to get the XZ2 Compact (dual SIM H8324) work with VoLTE in Australia.
The phone was originally bought in Europe and when updated to the official Telefonica/O2 Central Europe Android 10 firmware, VoLTE did work on O2 in Czech Republic.
I am now back in Australia and my current carrier, Vodafone AU, is to switch off all 3G services by the end of this year, so without VoLTE capability, the phone will not be of much use here.
It is a pity because I like the smaller format of this phone and with the LOS 20.0 upgrade, it works better than many newer models.
You did mention elsewhere that you extracted all the available firmwares and those were included in one of the LOS 19 nightlies.
So this is probably a long shot, but there appears to be a lone Australian firmware available via Xperifirm, called H8324_Customized AU_52.1.A.3.49-R4C
Is there any way to find out whether this may have the necessary config files for any of the Australian carriers? Or have you already included it in the LOS ROM?
Thanks a lot for all your work!
Hey, should be already included. Please check the modem config notification against https://github.com/LineageOS/android_device_sony_tama-common/tree/lineage-20/modem-config
If the folder exists.
Also make sure the AU stock firmware was flashed before installing LOS since these modem configs only have a reference to the actual mbn file which is part of the firmware which is not shipped with LOS. That's the reason you have to flash stock 10 before.
Thanks for all that!
So just to make sure I understand you correctly:
Are you saying that the possible reason why I cannot get VoLTE to work now is because when I upgraded the phone to the official Android 10 (before loading LOS 19.1 on it), it was the 'wrong' region (i.e. O2/Central Europe)?
If this is so, then do I need to restore the phone back to original via flashing the AU/Custom firmware, and then load LOS 20.0?
I guess doing that would require wiping the phone and starting from scratch?
I don't suppose there is any way of finding out just what, if any, VoLTE settings the AU/Custom firmware may include, before going through the full reset?
Thanks again mate - your ongoing assistance to people like me is greatly appreciated!
There's a modem config notification with an SXX number. With that you can check if that folder exists in the github repository. If that's the case the reason for missing VoLTE probably is that you were on the wrong stock rom (region). So, yes starting from scratch with the correct AU region should solve your issue. But it's not a 100% guarantee since there are providers who added VoLTE support after the latest stock rom was released by sony and that mbn file is either not existent or it doesn't contain the VoLTE support. In that case there's nothing I could do unfortunately.
Relating to my previous posted issue with mobile data connection I gave it another try with the actual LOS20 build (20230127) and tried to generate some details about the differences. Not sure if this could provide some new input but I'm willing to help finding the root cause. As you can see both roms are using the default modem file but while LOS20 shows a enabled 3g connection in the quick settings it's not connected.
Hi, one little problem: I need adoptable storage (let's not debate why, but I do).
With LOS 18 I would do the following in adb shell:
sm set-force-adoptable true
And format the SD as adoptable storage and all's well.
However, this doesn't work for 19 and 20; the format will go to 20% and then the phone will reboot and then goes into reboot loop until I physically eject the SD card.
Apparently it tries to restart the format after reboot and keeps crashing.
A workaround I've been using since 19 is to install 18, format adoptable storage and then upgrade to 19, because 19 will work fine with the adoptable storage then.
I was hoping this would be fixed in 20 but it hasn't, maybe you can take a look?
This is in logcat just before reboot:
This is apparently truncated. If it helps at all, how would I get the entire trace?
Also, this appears to be unrelated, but while looking through the log I noticed some other exceptions, see the attached file. Surely that's not supposed to happen?
Now, I have zero experience with Android, but I took a peek in gpiolib.c, and it seems to me the invalid GPIO may indicate some memory issue somewhere (uninitialised, corrupted, etc.) that causes the "-517" to be picked up. It's supposed to be unsigned.
Additionally, in general the log has hundreds of messages about commands and operations that are failing in some way (files that don't exist, mounts that fail, mkdirs/create file failing b/c of read-only filesystem etc.). Is that normal? It seems like a needless waste of resources, which probably has a bigger impact on the xz2c as it's an older phone at this point.
With LOS 18 I would do the following in adb shell:
sm set-force-adoptable true
And format the SD as adoptable storage and all's well.
However, this doesn't work for 19 and 20; the format will go to 20% and then the phone will reboot and then goes into reboot loop until I physically eject the SD card.
Apparently it tries to restart the format after reboot and keeps crashing.
A workaround I've been using since 19 is to install 18, format adoptable storage and then upgrade to 19, because 19 will work fine with the adoptable storage then.
I was hoping this would be fixed in 20 but it hasn't, maybe you can take a look?
This is in logcat just before reboot:
Code:
01-24 21:31:31.990 0 0 I F2FS-fs (dm-0): Found nat_bits in checkpoint
01-24 21:31:32.119 0 0 I F2FS-fs (dm-0): Mounted with checkpoint version = 60b9a912
01-24 21:31:32.125 0 0 W init : DM_DEV_STATUS failed for system: No such device or address
01-24 21:31:32.125 0 0 W init : DM_DEV_STATUS failed for vroot: No such device or address
01-24 21:31:32.134 0 0 I selinux : SELinux: Skipping restorecon on directory(/mnt/expand/d8deae77-554b-4175-ab14-8ce492d3782c)
01-24 21:31:32.134 0 0 I selinux :
01-24 21:31:32.174 4276 4393 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: StorageManagerService
01-24 21:31:32.174 4276 4393 E AndroidRuntime: java.lang.RuntimeException: android.os.ServiceSpecificException: (code 0)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at com.android.server.StorageManagerService.prepareUserStorageInternal(StorageManagerService.java:3423)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at com.android.server.StorageManagerService.prepareUserStorageIfNeeded(StorageManagerService.java:3384)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at com.android.server.StorageManagerService.onVolumeStateChangedAsync(StorageManagerService.java:1748)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at com.android.server.StorageManagerService.-$$Nest$monVolumeStateChangedAsync(Unknown Source:0)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at com.android.server.StorageManagerService$StorageManagerServiceHandler.handleMessage(StorageManagerService.java:870)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: Caused by: android.os.ServiceSpecificException: (code 0)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:3025)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:2995)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2978)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2920)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at android.os.IVold$Stub$Proxy.prepareUserStorage(IVold.java:2230)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: at com.android.server.StorageManagerService.prepareUserStorageInternal(StorageManagerService.java:3398)
01-24 21:31:32.174 4276 4393 E AndroidRuntime: ... 8 moreThis is apparently truncated. If it helps at all, how would I get the entire trace?
Also, this appears to be unrelated, but while looking through the log I noticed some other exceptions, see the attached file. Surely that's not supposed to happen?
Now, I have zero experience with Android, but I took a peek in gpiolib.c, and it seems to me the invalid GPIO may indicate some memory issue somewhere (uninitialised, corrupted, etc.) that causes the "-517" to be picked up. It's supposed to be unsigned.
Additionally, in general the log has hundreds of messages about commands and operations that are failing in some way (files that don't exist, mounts that fail, mkdirs/create file failing b/c of read-only filesystem etc.). Is that normal? It seems like a needless waste of resources, which probably has a bigger impact on the xz2c as it's an older phone at this point.
Last edited:
which stock fw you were on? maybe the beforementioned UK fw is not the right one for you. Check if there's one for austria or probably try the one from germany. but which is confusing for me is that with same stock fw it worked on LOS19? if so, that's weird. maybe you could send the output from "adb logcat" while enabling/disabling mobile data. only the last part when you started enabling/disabling mobile data please.
I didn't tried the magisk modules tbh and i will abandon them because i don't have enough time and there are still issues on all of the modules. for the camera resolution there's https://issuetracker.google.com/issues/162121234 so if this is the reason why you want the sony camera app it might be better to wait for google to fix their CameraX library. Then, hopefully, Aparture will have the right resolution too.
Btw there's no need to build the modules yourself. There are built zip files already.
The sony camera app works as magisk module under LOS20.
But as @wtor68 already wrote, Open Camera offers the full resolution.
I always flashed H8324_Customized CE1_1313-3194_52.1.A.3.49_R2C which should be the correct one for Austria. Isn't it?
I will give it a new try on weekend and send you the logcat afterwards.
Do you also need LOS19 logcat for reference?
To check correct stock rom i'm using Sony Emma Flash Tool. It'll show you available firmwares for your model and region. Mine is UK but flashed CE1 and everything is working without any issue.
Do you guys know of any good cheap bluetooth device which supports hd audio? unfortunately i only have a jbl charge 4 here which doesn't support it. can be a used one, it's just for testing. also for future bringups. probably something around 30-40€ or cheaper.
I recently bought some wireless earbuds for jogging. Used they are around 40-60€ at least where I am located. Model is Jabra Elite 7 Active. The lower series (3, 4,..) are also widely available, though I don't know if they support hd audio.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
yes, i have the exact same issue. it started some weeks ago. i always thought it was due to a paypal app update. i can't see something useful in the logs either. But I'll check it more deeply.
EDIT: Since we can use the paypal website instead of the app in the meantime i'm considering this as a low priority issue.11
The # sign at the beginning of a conf file means it's commented out and has no effect. Please follow the instructions exactly by replacing the whole file content with the fingerprint code snippet from first post.1
No, my daily driver isn't rooted. See 1st post on how to pass SafetyNet and hide root.1
Looks like PayPal fixed their crash. For me the app is working again. -
9
About LineageOSCode:#include <std_disclaimer.h> /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
LineageOS is a free, community built, aftermarket firmware distribution of Android 13.x (T),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : https://lineageos.org/
About LineageOS Legal : https://lineageos.org/legal/
Important Information
1. This ROM will never work with any versions of Google Camera (GCam)!
2. You need to flash Stock Android 10 before flashing this ROM.
Downloads Links
LineageOS 20.0:
Official builds: Link
Google Applications (optional):
MindTheGapps: https://wiki.lineageos.org/gapps
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
Please refer to the official installation guide at https://wiki.lineageos.org/devices/xz2c
Pass SafetyNet
Some apps like banking/payment apps or games require to pass SafetyNet.
There are 2 options:
Option 1: Without Root
1. Download the latest release of ih8sn here.
2. Replace the content of system/etc/ih8sn.conf inside the zip file with:
3. Install the zip file through recovery.Code:BUILD_FINGERPRINT=Sony/H8324/H8324:8.0.0/51.1.A.3.159/620448843:user/release-keys
Option 2: With Root
1. Install latest Magisk APK through recovery.
2. Install Universal SafetyNet Fix as Magisk module.
3. Install MagiskHide Props Config as Magisk module.
4. Run the following command either in ADB shell or a Terminal emulator app like Termux after running su to set a certified fingerprint:
5. Enable Zygisk and deny list and add some Apps to the deny list to hide rooting status.Code:props
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with Logcat for example
Also thanks to:
Olivier
Sjll
The LineageOS Team
The CyanogenMod Team
Everyone involved in working and testing
XDA
evDB Information
Lineage 20.0 for Xperia XZ2 Compact, ROM for the Xperia XZ2 Compact
Contributors
dtrunk90
Source Code: https://github.com/LineageOS
Donation
https://paypal.me/dtrunk90
ROM OS Version: Android 13
ROM Kernel: Linux 4.9
ROM Firmware Required: Official Android 10.0 firmware
Based On: LineageOS
Version Information
Status: Stable
Created 2022-10-23
Last Updated 2022-12-194
Yes, should get the first official build in some days: https://review.lineageos.org/c/LineageOS/hudson/+/3467562One thing worth noting for the build: vibration (haptic feedback) feels a lot weaker than it should be; otherwise, it's pretty effecient and stable enough for daily use.
