yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Compact Original Android Development] tomKater:
Hello,

I need some help.

I did the update 20210413 today with OTA system. Unfortunately, after the flash, the phone reboots in bootloop (the lineageos logo turn a while and after that it reboots in recovery mode, in twrp).

I tryied to flash manually the previous version (20210330), same behavior

It's not the first time I have this issue after update with OTA system. This time, I did a backup in twrp BEFORE update (boot, system and data). Strangely, when I do a restore with this backup, I'm in bootloop again (the difference is the bootloop is endless this time, no go back to recovery automatically).

Do you have a solution for me ? I would like to avoid flashing from scratch and setup again all my phone :(
[Xperia Z3 Compact Original Android Development] petefoth:
This occasionally happens to me when flashing the Z3C and other Sony devices. I can usually get round it by taking the following steps in TWRP:

Backup your data partition

Format - not just wipe - the data partition

Flash the new ROM - I usually do it by installing from SD card, but `adb sideload` should work too

Boot the phone and go through the setup wizard app, setting any screen pattern or PIN you had previously.

Restore the backup of your data partition

I hope that helps
[Xperia Z3 Compact Original Android Development] tomKater:
Thank you very much ! It was indeed the right procedure !

It saved me a lot of time. Thanks.
[Xperia Z3 Compact Original Android Development] marcogiannetta:
It's been a while since last time I did test a new Android version on this smartphone.

First of all, I'd like to thank you all maintainers for your effort and to congratulate for the great work done with this first build of lineage 18.1.

I did some basic testing (don't expect anything too accurate, since this is not my main device for a while) which I'll resume below:

Booting was fine and time is quite comparable with previous lineage versions

I succesfully installed a test build of OpenGapps (micro configuration of 20210130), which seems to work pretty well

account setup and sync works

WiFi working at both 2.4/5 GHz

Bluetooth working fine, I had no problems connecting to my bluetooth earbuds and listen to some music

NearbySharing is working like a charm and quite fast too

online charging is working at full speed (about 1800 mA with a quickcharge 3.0 wall charger)

MTP working

OTG works for both input devices (mouse, keyboard, etc..) or mass storage

camera is fully working (taking pictures with both front/rear cameras, taking videos, flash)

phone calls are working, but I believe that microphones are swapped, using the upper one as main, resulting in a low volume during calls

mobile data is stuck at EDGE for me, I couldn't get it to use LTE instead

audio is fine

video playback also seems to be fine (tested on youtube at 1080p)

chromecast works, in fact I did cast screen and youtube to a Google Nest Hub without any problem

the OS is overall responsive and snappy, even with gapps installed

screen rotation, accelerometer, gyroscope, proximity sensor, etc.. all fine

double tap to wake and other classic gestures are fine

I couldn't test hotspot since, as I said, I was stuck at 2G connection which was quite unresponsive

unfortunately I cannot test GPS or NFC neither

I hope I did not forget something important.

I'm going to keep this installed since it's really stable, so feel free to ask me for some other testing and I'll for sure try to do that as soon as I have some spare time :)
[Xperia Z3 Compact Original Android Development] Samare:
Thank you NeoArian and all other developers!

Your LineageOS 17.1 build really revived this small phone!

My previous experiences with installing unofficial builds were not as great as this one.

The only things I miss compared to stock Android 6 are the camera button full press to open the camera app (which by the way starts slower than on stock Android 6), the secondary mic noise suppression (which wasn't working anymore on mine anyway) and the service tests opened with the *#*#SERVICE#*#* code.

About this new LineageOS 18.1 (I used MindTheGapps-11.0.0-arm-20210412_124103), I didn't notice any problem compared to 17.1.

In fact, using Migrate to restore all apps and settings, I almost thought the update didn't work since it booted like usual.

For the other users, in addition to Migrate, I of course reinstalled Magisk, which doesn't work natively (even with the workaround of installing 20.4 first) on this new 18.1 build. The boot_patch.sh file has to be modified, I've attached a version of Magisk 22.1 with that file already modified (works at least on Z3C). NeoArian: is there any way to modify the builds so that they use init instead of init.real?

Pretty extensive "basic testing"!

- Phone calls were fine on 17.1, haven't checked yet on 18.1. UPDATE: still fine on 18.1

- LTE works here (at least band 1). I'll see if I can connect to different bands.

I don't know if it helps, but here's what modemcaps says:

Spoiler content hidden.

- Double tap to wake didn't work for me on stock Android 6 (at least when on deep sleep). It seems to work now which is an improvement.

- GPS works fine.

I'm using it from now on, so I'll report any problem.
[Xperia Z3 Compact Original Android Development] wtor68:
First thank you NeoArian and all other developers involved for your great work! I also did some short tests and found nothing which was not working. I worked with OpenGapps test build of 20210130. I tested:

- WLAN

- Bluethooth

- Mobil date

- phone call

- Camera/Video/flash light

- Audio and video playback

- normal usage like my los 17.1 daily driver

I used some configuration like i did on my los 17.1 daily driver and it looks really good! Unfortunately I cannot test GPS as my test device had an hardware problem here.

So really fine from my side here, only the test with Magisk to root the device didn't work. But this shouldn't be related to los 18.1. Hopefully Magisk will be functional sometimes later.

Thanks again!
[Xperia Z3 Compact Original Android Development] Aleomar30:
Hello

I just installed this ROM on my z3c, which has a faulty touch and I use it with a mouse.

The problem is that there is a kind of highlighting on the desktop icons and I don't know why (could it be because of the mouse?)

Thanks in advance !!
[Xperia Z3 Compact Original Android Development] pawloland:
Yes, it is because of a mouse. It has something to do with a scroll.
[Xperia Z3 Compact Original Android Development] marcypan:
Hello, I installed 18.1 yesterday (oh boy, it was hard and expensive - SIM Lock with 0 attempts) and I'm impressed. I didn't installed GApps as I can't found ARM pack (anyone help me plz 😁). I skipped LOS17.1 so I compare it to stock 6.0 and in my opinion it's noticably faster and battery lasts longer however maybe because I have no GApps.

Tested so far

- WiFi

- Mobile data

- Phone calls (calling and answering)

- Bluetooth (sending/receiving files, earphones, Xbox gamepad, keyboard)

- GPS (not so advanced tests, I'll test it later)

- Camera (photos, video in front and rear cams, flashlight)

- OTG (pendrives and mouse)

- Screenshots

- Receiving SMS, but not sending (inactive number)

- Charging using microUSB and magnetic connector

Not tested yet:

- Hotspot

- NFC

- Screen recording

- Screen mirroring

Found some visual bugs but not sure if it's LOS or Nova Launcher in beta channel so I'll check it and give info later.

I'm waiting for future builds for tests and hope they'll be [OFFICIAL]!
[Xperia Z3 Compact Original Android Development] Samare:
Since yesterday (still on 18.1), I have two kernel wakelocks preventing deep sleep:

- msm_serial_hs_dma

- BTLowPower

I used BBS with the adb shell settings put global hidden_api_policy 1 fix to check the wakelocks.
[Xperia Z3 Compact Original Android Development] Samare:
I don't think I wiped data which is why everything was already configured.

Maybe that or MindTheGapps explains the wakelocks.

I'll check it again later with the data wipe.

In the mean time, I went back to 17.1 (20210420) where everything is still fine.
[Xperia Z3 Compact Original Android Development] NeoArian:
Thanks to everyone for the really detailed testing (: I really appreciate it.

Regarding the BTLowPower wakelock, @J_C_D has fixed that on lineage-17.1 recently and at this time the lineage-18.1 branch was already forked. I will make sure to include the fix for lineage-18.1 with the next update.
[Xperia Z3 Compact Original Android Development] Samare:
I see that you merged it on April 5.

Didn't your 20210406 build already include it?
[Xperia Z3 Compact Original Android Development] wtor68:
Hello Samare,

i tried your fixed Magisk package for sony z3c but it doesn't install on my device with lineageos 18.1. If i click for install i got the error message that an error occurred at parsing the package. Is there anything to mind to get it installed?

Thanks!
[Xperia Z3 Compact Original Android Development] NeoArian:
If I recall correctly, I did not include that in the uploaded build.
[Xperia Z3 Compact Original Android Development] Samare:
I flashed it on TWRP after renaming it to .zip
[Xperia Z3 Compact Original Android Development] wtor68:
I already tried the TWRP way. Then the app is there but if i click on it, it asked: "upgrade to full magisk manager to finish the setup. Download and install?" I can only say 'cancel' which doesn't help or 'ok' but then i got he same error like before (error occurred at parsing the package). I don't know the problem here. It's only this package, other apk's install without problems.
[Xperia Z3 Compact Original Android Development] Samare:
I'm guessing the flashing finished with no error? Then you could try installing the same file (this time with the .apk extension) inside Android.
[Xperia Z3 Compact Original Android Development] wtor68:
Yes no flash error but same parser error afterwards at installing apk. Now i tried to install the apk by adb. Here i saw some kind of certificate error. So i fixed the apk by zipalign / apksigner and it installed without problems. Root is back now! But i don't know why it works on your side without this...
[Xperia Z3 Compact Original Android Development] Samare:
Indeed, since I modified it the signature wasn't valid anymore.

On 18.1 I didn't wipe data so the older version was already installed.
[Xperia Z3 Compact Original Android Development] Daedalus1979:
@NeoArian : will you start a New thread for 18.1? Or did i missed it?
[Xperia Z3 Compact Original Android Development] NeoArian:
I will create a new thread for 18.1 once it goes official. The current builds are "just" some test builds which I shared because they are in a really good shape already.
[Xperia Z3 Compact Original Android Development] NeoArian:
I will create a new thread for 18.1 once it goes official. The current builds are "just" some test builds which I shared because they are in a really good shape already
[Xperia Z3 Compact Original Android Development] deftonesforever:
TWRP for this please?
[Xperia Z3 Compact Original Android Development] 7ig3rsh4rk:
Revived my Z3c with LineageOS 17.1 a few days ago and I'm very pleased so far.

Nice to see that this great device still has community love and support.

But the current Lineage ROMs have a bug that prevent Netguard (an open source, no root VPN based Firewall) from running correctly and blocks all traffic if the VPN Service is active:

It seems the problem was fixed for some devices and partly for others but not in general.

@NeoArian Can you have a look if the fix can be ported to the Z3C?
[Xperia Z3 Compact Original Android Development] steve8x8:
After neglecting the phone for a couple of months, I finally rediscovered it in a drawer, even with some remaining charge. It was still running an older 17.1 version, and with 20210608 being the latest release, I decided to OTA upgrade.

After downloading, I gave my OK to boot into TWRP (3.3.1 from 2019) but that one didn't find the update automatically.

Is this expected behaviour, or did I miss something important? I found the file in /data/lineageos_updates eventually...

Also during installation, I couldn't spot any hint of GApps being adapted (but PlayStore is still there, so I won't worry) while Magisk (20.4) logs showed up... At the moment, a MagiskManager at 23.0 with Magisk left at 20.4 seems to pass SafetyNet tests, and I'm not eager to break the device. Could this cause any problems?
[Xperia Z3 Compact Original Android Development] 7ig3rsh4rk:
The problem still exists in latest 17.1-20210608 Nightly. Any updates?

And I encountered another bug. When I try to uninstall certain apps the package installer immediately closes and nothing happens (for example when trying to uninstall Whatsapp). But only a few apps are affected.

But it could also be a problem with open GAPPS since GAPPS replaces the AOSP package installer with the google one.

Encryption worked without a problem. First I thought something went wrong because the lineage boot animation was shown for a very long time (20-30 min) and then it rebooted into recovery. After wiping cache and dalvik the OS booted fast and without problems.
[Xperia Z3 Compact Original Android Development] NeoArian:
Yes, i will take a look into the kernel patches soon.

Please use the recommened lineage recovery, OTA is working fine with it. If the Playstore is still there you don't need to worry about having lost the gapps.

What kind of problems do you talk about with magisk?

I can not reproduce the issue about uninstalling apps on a build without gapps. Could you get a log of that?

I'm sorry about the screen timeout issue, but i currently don't have the time to look into it, the main focus lies on device specific issues and an official release of 18.1.
[Xperia Z3 Compact Original Android Development] steve8x8:
Sorry for the oversight, I had started with 16.0 and related files, and somehow missed that the link had been changed to reference an updated TWRP.

This is to confirm that, after updating the TWRP inside TWRP, the recent OTA went smoothly, thanks!

(Is there a specific reason why there are no updates in twrp.me anymore, with the device still listed as supported? Will there be another upgrade to 3.5.0 provided by someone?)
[Xperia Z3 Compact Original Android Development] 7ig3rsh4rk:
I tried to root with Magisk but after patching the boot.img and flashing it via fastboot or recovery the Magisk app still says "Installed: N/A". Is the boot.img variant nor working on the Z3c or did I miss something else?
[Xperia Z3 Compact Original Android Development] steve8x8:
For me, it worked using an older version of Magisk (20.4 or 21.2) for the first run, then gradually upgrade the MManager (and perhaps Magisk itself), not necessarily to 23.x though... (You've got to use the Hide off/on trick, reboot, and check for SafetyNet to identify the version you can live with.)
[Xperia Z3 Compact Original Android Development] Samare:
@NeoArian I've noticed with Kernel Adiutor that the CPU minimum frequency was set to 1574 MHz instead of 300, making the phone get hotter (and the battery draining faster) than it should when simply browsing a website.

Is it intended?
[Xperia Z3 Compact Original Android Development] 7ig3rsh4rk:
Thx, 20.4 is working. Manager App can be updated to the latest version 23 but Magisk itself is not working with a version > 20.4. At least for me.
[Xperia Z3 Compact Original Android Development] NeoArian:
I would shamelessly blame the google apps you installed. Try to report it to the one who made the gapps you used.

There are no updates at twrp.me because there is no active maintainer for z3c. I don't continue my twrp build either because lineage recovery does all that's needed.

That is not intended and i can not reproduce that. Are the frequencies stuck the whole time or just in specific cases?

From my z3c:

z3c:/ # cat sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
300000
z3c:/ # cat sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq
300000
[Xperia Z3 Compact Original Android Development] Samare:
Cores 0 and 3 are set to 300 MHz minimum and cores 1 and 2 to 1574 but disabled on low load.
[Xperia Z3 Compact Original Android Development] NeoArian:
LineageOS 18.1 became OFFICIAL for Xperia Z3 and Xperia Z3 Compact three days ago. This will mean there won't be new official 17.1 builds anymore and the next build will be 18.1! Once the build is available, i will close this thread and a new one will be created for 18.1.

It's correct that the cores are being shut down on low load. The cores are only enabled when they are needed and in that case they usually run at higher frequencies. That is pretty much inteded behaviour.
[Xperia Z3 Compact Original Android Development] Daedalus1979:
Sadly my z3c screen stopped working this morning, still I would like to thank neoarian for all the efforts you put into keeping the z3c alive. I used your work of art for at least since I can remember using my z3c. I briefly considered buying my 4th or 5th z3c, but decided to continue with a XZ2 compact. Have to figure out how to get Los on that phone yet.
[Xperia Z3 Compact Original Android Development] shadowstep:
THREAD LOCKED

Requested by OP.

Regards,

shadowstep

Forum Moderator
[Xperia Z3 Compact Original Android Development] iagash:
Connecting to 802.11r WLAN fails

Thanks a lot for bringing Lineage OS 17..1 to my beloved z3c.

I flashed it via sideload from lineage recovery over the installed lineage 16.0.

As far as I can see I have only found one thing that doesn't work, which is connecting to an 802.11r enabled WLAN. I have both 2.4GHz and 5GHz on 2 access points running openwrt with 802.11r (fast roaming). It worked well with lineage-16.0 on the z3c. Since the upgrade the z3c can't connect to the WLAN anymore.

If I switch off 802.11r on the AP the z3c connects fine with both 5GHz or 2.4GHz.
[Xperia Z3 Compact Original Android Development] KoMaSo:
Deepsleep

Hi Arian,

the BTLowPower was initialised in broadcom BT driver "android_kernel_sony_msm8974-lineage-17.1\drivers\bluetooth\bcm4339.c".

Sony has released open device kernel. There ist an more general driver https://github.com/sonyxperiadev/kernel/blob/aosp/LA.UM.7.1.r1/drivers/bluetooth/bcm43xx.c . There are no such wakelocks.

Is it possible to take this one or to remote wakelock from the driver?
[Xperia Z3 Compact Original Android Development] gangbgr:
Hello! I installed 17.1 and gaps and have Lineage logo bootloop. If I install CLEAN Lineage its boots normally, but no google on it. I tryed many combinations of builds gapps, ROMs, wipes with formatting but result in start of this message.

External installed google play crashes with all versions, I tryed several build google play SERVICES too. What I can do? I need google contacts and mail services.

Installed Lineage from SD card, because of USB faults. Last TWRP and last nighty build. I use beauty Lineage 17.1 but I need google services. Thank you!

And its not see 5G wifi, but its not first problem.
[Xperia Z3 Compact Original Android Development] KoMaSo:
It seems to bee that the wake lock will unlocked if the Bluetooth will go to sleep. But the whole device will not go to sleep until the wake lock is active. I think the wakelock is not nessesary today at this place.

---------- Post added at 09:42 PM ---------- Previous post was at 09:40 PM ----------

Please check if you have arm not arm64 and android 10 selected for download opengapps.
[Xperia Z3 Compact Original Android Development] typhoon_2099:
Can't believe I have a 6+ year old phone running Android 10! I seem to be running into issues after upgrading from LineageOS 16 though.

I've installed 17.1 over 16 and now I can't cast to my Chromecasts. Opening the menu in whatever app just brings up the Nearby Devices option, both Chromecasts in my house fail to appear in the menu. It was working fine on 16.

I also can't use a microphone in apps. Phone calls are fine but any app that uses the microphone fails to open it.

Keep up the great work!
[Xperia Z3 Compact Original Android Development] pawloland:
Hi everyone!

Today I've got time to test it and can confirm it worked, so if anyone is waiting with upgrade, you can use my instructions with TWRP, rather than adb sideloading, mentioned on los z3c wiki page.

First impressions are following:

Both cameras are working fine in Lineage camera app. [MENTION=7384824]mxperial[/MENTION] 's camera module with stock sony camera isn't working thought. More info here.

GPS isn't working form me - it finds satellites, but never catches any signal and doesn't fix (it didn't work for me on los 16, so no surprise on that field. I was hoping it would magically work again, after [MENTION=838709]Mr.Tom_Tom[/MENTION] 's fixes, but it haven't sadly).

On this version I can't see and use SIM Toolkit app (com.android.stk), with SIM card inserted, where on los 16 it was working.

Also, do you [MENTION=8746471]NeoArian[/MENTION] maybe know how to hide build number in QS panel? It looks for me like it shouldn't be there on official build :confused:

Cheers :)
[Xperia Z3 Compact Original Android Development] NeoArian:
The build number is shown in the status bar when you have the developer options enabled, that's intended and not a lineageos addition, it is the same on Google's pixel devices. If you disable the developer options the number will be hidden.
[Xperia Z3 Compact Original Android Development] wtor68:
I had the same problem with nano gapps from today (19.09). I also use Magisk, but i think it's not related. As i already installed another device some days before (also z3c) i used the gapps from this date (nano or pico from 09.09). With this it works without problems. Don't know the reason... may be it's worth a try.
[Xperia Z3 Compact Original Android Development] mes2k:
Wireless MAC changes after reboot

I have installed LOS 17.1 on my z3c over 16.0.

17.1 works fine after the first day of usage, but there is one anoying* thing: It seems the MAC address of the wireless interface is changing after reboot.

I currently see two possibilites what happens here:

Either the privacy settings of the wireless network is changing the MAC address on purpose. But the UI element for changing this setting is missing.

Or the hardware MAC address is not read correctly and some code is generating a random MAC while booting. I know that this behavior exists in LOS/drivers, since my Wileyfox Storm had exactly this issue for several months running LOS.

*This issue is anoying, because my router is sending an email for every new device in my network. Also settings that are connected with the device in my router will no longer apply after the phone reboots.
[Xperia Z3 Compact Original Android Development] iagash:
That might be possible. I found this in my logcat when trying to connect to an 802.11r enabled AP:

09-18 20:26:26.440 3336 4924 E WifiVendorHal: getFactoryMacAddress(l.1328) failed {.code = ERROR_NOT_SUPPORTED, .description = }
09-18 20:26:26.440 3336 4924 E WifiClientModeImpl: Fail to set factory MAC address. Factory MAC is null.
09-18 20:26:26.441 3336 4924 I WifiClientModeImpl: Connecting with 40:40:a7:33:42:23 as the mac address
[Xperia Z3 Compact Original Android Development] gangbgr:
Got it, thank you very much!
[Xperia Z3 Compact Original Android Development] hubert-bangol:
On a z3c with 6.0.1 stock ROM rooted, I made some search about that functionnality. These are the 4 processes launched after plugging the headphones:

With the aapks.com website, I find the two first packages. And I'm sure that the second one is the ANC I'm looking for, because under ACTIVITIES (https://aapks.com/apk/sound-enhancements/) there is:

So I download this package, but unfortunately it cannot be installed under Carbon Rom, there is an error message. :(

Maybe it is a system app, does anyone have a clue how to install, if possible of course ?