yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Compact Original Android Development] pawloland:
Don't know if it is just los bug or is it only related to this rom, but i discovered that expanded desktop doesn't work properly while using splitscreen.

On picture 1 it is shown how splitscreen works normally.

On picture 2 it is shown how splitscreen works with expanded desktop option turned on. It doesn't hide nav bar and status bar. Status bar's background is being set to transparent and nav bar stays black. I think this option should make nav and status bar completly invisible and accesible only by swiping up for nav bar and down for status bar.

On picture 3 it is shown how expanded desktop works without splitscreen, basicly as it should.

Hope that you [MENTION=8746471]NeoArian[/MENTION] can take a look on it. I know that there are problems which are more important, but our beloved z3c has only 4,6 inch screen, so this small space which is covered by status and nav bar could be very useful while being in splitscreen mode:o

Also i don't have lastest version of rom (i have 16.0-20190109-UNOFFICIAL-z3c) flashed so i don't know if problem occures in newer versions of rom but if no one pointed it previously i thought that this bug wasn't fixed yet (if it is even bug, not just how the things should work).
[Xperia Z3 Compact Original Android Development] moelle11:
Thank you for the ROM!

Nice that someone is interested in our old device. I use the ROM from 05.03. Unfortunately, the restart loop with and without SD card. With card this was formatted and set up in Pie.
[Xperia Z3 Compact Original Android Development] NeoArian:
Good Morning everyone :)

I just installed Instagram for testing today and noticed that AudioFX crashes, also the app doesn't even correctly open for us right now. After removing it instagram video playback seems to be fixed, it is playing videos since 15 minutes now on my device! Until i will upload the next build (march security patches, will try to fix SDCard stuff) you can just remove /system/priv-app/AudioFX

Have a nice Saturday!

EDIT: playing still fine after 25 minutes, if someone could confirm it I would mark it as fixed :)

Edit2:

I can't reproduce the issue with SDCard's I can format it to internal storage and reboot, no problems. Same when formatting it as portable SDCard. Could someone facing this tell me a way to reproduce it?
[Xperia Z3 Compact Original Android Development] okij:
I can't tell for LineageOS 16.0, but on CarbonROM 9.0 the problem is that SD cards which are formatted to exFAT file system make the Z3c reboot.

So you have to format the SD card to exFAT on a PC and then try to use it on the phone.

Formatting it as portable SD card on the phone most likely uses FAT32 file system, which works well, but doesn't support files > 4 GB in size.
[Xperia Z3 Compact Original Android Development] ArmanSh:
I can't install it on my Z3 compact. I was able to avoid error 7 by modifying the updater script and removing the first condition. However, it ends with E1001. I have tried TWRP 3.1.1 and unofficial 3.2.0; I got the same error.
[Xperia Z3 Compact Original Android Development] NeoArian:
Are you sure that you downloaded the z3c build? I also publish lineage 16 builds for my Xiaomi mi 6 at sourceforge.
[Xperia Z3 Compact Original Android Development] ArmanSh:
I used the link you provided in the first post and downloaded this file: lineage-16.0-20190305-UNOFFICIAL-z3c.zip
[Xperia Z3 Compact Original Android Development] ArmanSh:
Which TWRP version do you use? Can you share the link? Maybe it's a special version? Also, previously, I had used Carbon ROM. Can it be the cause? I wipe the phone every time before installing a ROM.
[Xperia Z3 Compact Original Android Development] okij:
Possible fix for exFAT issue

About the exFAT issue: In https://github.com/z3c-pie/android_device_sony_msm8974-common/blob/lineage-16.0/BoardConfigCommon.mk currently there is

TARGET_EXFAT_DRIVER := exfat

I think that since you are using the sdFAT driver for exFAT, you have to set this line to

TARGET_EXFAT_DRIVER := sdfat

I've seen this change in several other repos, e.g. here (see commit from Mar 28, 2018). Maybe some of the other commits in this link are also necessary to make exFAT work (I don't know, since I'm not a dev. ;))

[MENTION=3816568]Myself5[/MENTION]: I tagged you because there's the same issue on CarbonROM 7. 0. I hope that this information is useful for fixing exFAT on Pie.
[Xperia Z3 Compact Original Android Development] NeoArian:
This flag is dropped in pie, the kernel config is enough.

That is not the fix anyway, I haven't got it working yet.
[Xperia Z3 Compact Original Android Development] okij:
Hm, maybe this flag then has to be fully removed from BoardConfigCommon.mk, like in https://review.lineageos.org/c/LineageOS/android_device_xiaomi_msm8996-common/+/236751, because otherwise it interferes with the kernel config?

Or maybe one of the other commits from https://review.lineageos.org/q/status:merged+branch:lineage-16.0+exfat is useful?

Just trying to help. :)
[Xperia Z3 Compact Original Android Development] stefandoesinger:
stefandoesinger

I improved the screen lock situation by adding execute / directory open permissions to /data/system_de/0/spblob as root and re-setting the lock key. Now the phone no longer loops attempting to restart the lock screen. The lock screen shows up and the pin can be entered, but the unlock is not successful. I'll keep investigating.
[Xperia Z3 Compact Original Android Development] stefandoesinger:
stefandoesinger

After accidentally breaking something I wiped the data and created the spblob directory with proper permissions before setting the PIN the first time. Somewhere in my experiments I also created a 0000000000000000.handle file and <id>.weaver file because logcat complained being unable to open those. <id> is a hex number that matches the .pwd, .spblob, etc files created in this folder when setting a pin.

Other directories with similarly broken permissions are recent_images, recent_tasks, shortcut_service and snapshots in /data/system_ce/0. I set the permissions of those to 720 as well before setting the screen lock.

I don't know which of those parts was responsible, but now I have a correctly working lock screen. I assume phone encryption will also work because it was fine even when the lock screen suffered from lockscreen looping, but I haven't verified that yet because I have to fill up my battery again before the system will let me encrypt the phone.
[Xperia Z3 Compact Original Android Development] ArmanSh:
I tried the new release lineage-16.0-20190311-UNOFFICIAL-z3c.zip.

I didn't get an error 7 or E1001. It was installed without any problem. :)

However, the OS itself is highly unstable - I tried it alone, with MindTheGapps-9.0.0-arm-20190216_211054.zip or open_gapps-arm-9.0-pico-20190310.zip.

I got stuck in the repeated loop of booting-crashing. There wasn't one time that I could even see the first look of the OS. :(

I know how difficult it must be to fix issues concerning an OS and I'm grateful for all the hard works that are done for it.

Hopefully, I could use the next release.
[Xperia Z3 Compact Original Android Development] NeoArian:
To fix your issue you have to disconnect your as exfat formatted sdcard. Apart from this it is pretty stable.
[Xperia Z3 Compact Original Android Development] ArmanSh:
I appreciate your answer. Do you mean during the boot? Or I can't ever use my sdcard? My Stock Rom formatted it for the first time. How can I use it? Does formatting as NTFS help?
[Xperia Z3 Compact Original Android Development] NeoArian:
You can't use an sdcard with exfat at the current state, you can format it as fat32 for example.
[Xperia Z3 Compact Original Android Development] ArmanSh:
Fat32 causes problem with files larger than 4 GB. Also, I use a 128 GB sdcard and Fat32 may cause other problems. Is it possible that it will be fixed in a future release? Thanks for your help.
[Xperia Z3 Compact Original Android Development] stefandoesinger:
After playing with the phone for a few days the 20190311 build seems to be working well. I do not see any obvious issue with battery life, bluetooth audio is stable (Connected to a Denon receiver), Wifi is stable, GPS works. I don't have an SD card in my phone though. The camera button works for taking pictures in the stock camera app. I'd love to have it open the camera app like the vendor ROM does, but haven't found a way to set this up. The lockscreen is stable after applying my fixes mentioned earlier and phone encryption works too. (Ok, it says it is working, I haven't looked at the raw disk to see if it is actually encrypted.)

The issues mentioned throughout the thread that I can confirm are the status LED and video recording.

I would love to have a way to re-lock the bootloader to protect my data from a cold boot attack, but as far as my research goes this won't work unless I have a sony-signed kernel. The disk encryption mitigates that problem though.
[Xperia Z3 Compact Original Android Development] juniofdm:
i am test MHL this week, but very happy know work fine!!!

Bluetooth Apt-x HD job fine too!

And system run smooth.

Very very thanks a all developers! :good::good::good::good:
[Xperia Z3 Compact Original Android Development] ArmanSh:
I removed the sdcard after flashing the OS and Gapps. This ROM is fascinating. I really love it.

However, in addition to the exFat format of my sdcard, it couldn't detect any wifi network (2.4 GHz and 5 GHz). This seems to be caused by a problem with wifi certificates which I also faced in every other custom ROM I used. Fixing this issue requires installing Magisk which caused GUI failure.

Hopefully, I'll be able to use it in a few months.

You are doing a great job. :good:
[Xperia Z3 Compact Original Android Development] NeoArian:
Sorry to hear this, what problem do you face with magisk? I use magisk just fine.
[Xperia Z3 Compact Original Android Development] ArmanSh:
I flashed the OS and Gapps. Then I installed Magisk manager. After downloading the appropriate version, I entered recovery mode and fashed the Magisk.

After booting the OS, the screen turned into black and remained for a few seconds. Then the android lock screen appeared for less than a second, then the screen turned into the black again for a few seconds. Afterward, it became visible for less than a second and then became black again. This loop continues in a way that I have no control over it. I only could turn off the phone by pressing the power top and volume up keys.
[Xperia Z3 Compact Original Android Development] stefandoesinger:
That's not a Magisk issue. That's the lock screen loop that manifests itself the first time you reboot after setting a lock pattern / pin / password. See my posts #102 and #103 in this thread for a workaround you can apply.
[Xperia Z3 Compact Original Android Development] NeoArian:
[MENTION=4916555]okij[/MENTION] do you know wether the exfat problem exists since the first pie builds? I mean the really old ones before 12th February
[Xperia Z3 Compact Original Android Development] okij:
No, so far I just tried [MENTION=3816568]Myself5[/MENTION]'s cr-7.0 build from 03-02, but I'm also closely following your thread and saw that it's a common issue.

Have there been mayor changes since 12th Feb. which could have introduced the exFAT bug?
[Xperia Z3 Compact Original Android Development] NeoArian:
I am not sure but since then we use then o_tmpfile Backport kernel side and iirc there were no people complaining about before.
[Xperia Z3 Compact Original Android Development] okij:
Yes, iirc the issue hasn't been discussed before March (I also just searched for keywords "exfat", "sd card" and "reboot" on this thread which gives no results before March).

Of course it could be just a coincidence (in case the first users didn't use exFAT formatted cards), but it would be worth investigating further.
[Xperia Z3 Compact Original Android Development] NeoArian:
I will just compile the kernel without the Backport and test it :D

Edit : that doesn't seem to be the problem.
[Xperia Z3 Compact Original Android Development] pawloland:
Can confirm, everything plays smoothly now:victory:
[Xperia Z3 Compact Original Android Development] ArmanSh:
Thanks for your answer. You were right. I had absolutely forgotten that it required screen lock during the initial setup. However, because of the wifi regional issue, I had to restore my phone to 8.1.

https://xdaforums.com/xperia-z2/development/help-trying-to-solve-wifi-region-issue-t3898676
[Xperia Z3 Compact Original Android Development] Smearedbyshit:
Wifi issue android pie on Z3C

Everyone who has trouble with WiFi (5ghz).

I solved this problem with installation magisk mogule - "wifi bolding (Qualcomm) by simonsmh"

Now wifi works good as stock rom (sry for bad eng).
[Xperia Z3 Compact Original Android Development] pawloland:
Has anyone noticed on his z3c problem with charging after updating their rom to lastest version? I used to have about 1200/1400 mA input but nowadays i noticed i have even bellow 500mA input before my battery lavel reaches 60%. After it reaches 61% it immidieadly increases up to around 1400mA and after a while it again dropps down to about 500mA. I used ampere app from playstore to see those digits. Is it just mine problem caused by potentially faulty phone or does someone also has it?

I look forward for respond from someone:confused:
[Xperia Z3 Compact Original Android Development] ArmanSh:
Didn't work for me. Wifi can't detect any of available networks (Neither 2.4 nor 5 GHz).
[Xperia Z3 Compact Original Android Development] minixperia:
In my phone WiFi 5Ghz work without any problem
[Xperia Z3 Compact Original Android Development] stefandoesinger:
I get about 800 mA charge speed at ~80%. I don't remember how much I got on the stock rom, but I vaguely remember that it usually did not go about 1000mA.

This is using the magnetic wire charging. My micro-USB port is usually covered by tape because my display is peeling off, like on many other z3c phones :(
[Xperia Z3 Compact Original Android Development] pawloland:
Another strange thing is that in dev options it shows phone has only 1,9GB of ram memmory but as far as i remember z3c has 2GB. Is it just visual glitch or 100MB of ram is never used on this rom?
[Xperia Z3 Compact Original Android Development] dhemker:
This might be caused by the fact that mobile phone manufacturers (in general nearly all memory manufacturers) specify their sizes to the base 1000, not 1024 as it should be (then it says GiB instead of GB). So 2 GB of RAM are actually approx. 1907 MiB.

Best

Dennis
[Xperia Z3 Compact Original Android Development] stefandoesinger:
stefandoesinger

I don't think that's the case here. I have never seen RAM chips that were not powers of two. I suspect that some memory is reserved for the baseband / modem and other hardware. The stock firmware probably patches the value up in the UI.

This is from the free command on LOS 16:

z3c:/ $ free
total used free shared buffers
Mem: 1860300800 1512398848 347901952 0 36020224
-/+ buffers/cache: 1476378624 383922176
Swap: 533409792 70930432 462479360

Would be interesting to compare to stock - the value in question is the Mem/total one.
[Xperia Z3 Compact Original Android Development] TamarindoJuice:
Any news about the notification led?
[Xperia Z3 Compact Original Android Development] NeoArian:
I did a couple of tests but had no success yet.

Anyway I would like to ask whether you all are interested into signed builds?

You can read about it here : https://source.android.com/devices/tech/ota/sign_builds

When you come from an unsigned (test-keys) build you would have to format data in order to get the build with my set of release-keys to work. If you don't want to format data i would provide a small zip to "prepare" for the new keys in order to flash without formatting data.

For my Xiaomi Mi 6 I have started signed builds at the beginning of this week and after the initial test I would be ready to start signed z3c builds. So I would love to hear what you think about it!

Also I want to announce that I have added OTA support into the last build. However if we decide to go signed I would skip one OTA because it can't be flashed as usual.

Have a nice day and get well soon to me :D
[Xperia Z3 Compact Original Android Development] stefandoesinger:
stefandoesinger

I noticed that the LED turns on for a short moment on boot. My quick guess was that the kernel can turn it on and off, but it isn't advertised correctly to the Android userspace.

An unrelated question: I noticed the Kernel is quite old (3.4), whereas other Android 8 devices I have already run 4.x series kernels. Is this because we're stuck with binary blobs from Sony that work only with whatever kernel is in the stock firmware?

Count me in :) . Personally I don't care if I have to wipe and re-setup my phone.
[Xperia Z3 Compact Original Android Development] NeoArian:
This is true, the lights HAL doesn't correctly handle the LED. You can manage the LED manually with editing the the brightness file in /sys/class/leds/led:rgb_{red/green/blue}/brightness.

Yes, we are stuck into 3.4 because of Sony's release. Upstreaming this old kernel to 3.4.113 would be such a pain (many conflicts...) it wouldn't be worth it. Doing a mainline update would require further forward porting Sony's changes which can't be done easily. If I recall correctly we use 3.4 instead of 3.10 because of Sony's DRM system prevents the use of the original camera blobs on not original ROMs which gets worked around somehow by using the older kernel release.

Great!
[Xperia Z3 Compact Original Android Development] pawloland:
Screen mirroring desn't work. Phone restars itself after taping on device shown on list. I hope you [MENTION=8746471]NeoArian[/MENTION] can take a look on that :)
[Xperia Z3 Compact Original Android Development] NeoArian:
I already have a fix in my eyes :D Just need some time to test it.
[Xperia Z3 Compact Original Android Development] NeoArian:
Good evening, since some weeks I noticed that when I call with my z3c the other end can't hear me, even though there haven't been changed to it so far, it might be caused by some tests by me, can anyone confirm that it is broken on his phone or works please?

I can't wipe my data right now just based on a guess because my father uses the phone as daily...

Have a nice day!
[Xperia Z3 Compact Original Android Development] pawloland:
16020190311 UNOFFICIAL-z3c everything works fine
[Xperia Z3 Compact Original Android Development] NeoArian:
Thank you very much!

I have pushed an OTA today, anyone received it? :D

While testing OTA i have regonised that [MENTION=5900960]ShadowElite[/MENTION] missed the misc mount in his TWRP so i have recompiled it with the mount added (commit)

I will upload it later.

Which TWRP are you using these days?

New added is GloveMode, maybe also known as high touch sensitivity mode (commit).
[Xperia Z3 Compact Original Android Development] pawloland:
I didn't on 16020190311 UNOFFICIAL-z3c. Do I have to manualy update into newest version of rom to recieve OTA updates?
[Xperia Z3 Compact Original Android Development] NeoArian:
If in Settings -> system -> Updater no Update is visible you have to update manually or open a shell and type as su "setprop lineage.updater.uri https://raw.githubusercontent.com/ArianK16a/OTA/lineage/z3c.json" and it will show in Updater.
[Xperia Z3 Compact Original Android Development] stefandoesinger:
With this the update showed up for me on lineage-16.0-20190316-UNOFFICIAL-z3c. Without this intervention it said no update found. I'll try to download and install it later.

Your first post still says "Last Updated 2019-01-19". You may want to change it :) . Can you also provide a quick summary of the changes?

Wrt calling, it works fine for me on 20190316. I do not call much though because I am currently in Tanzania and use the z3c as my secondary phone with my home SIM. I did test calling before I came here though and it worked.
[Xperia Z3 Compact Original Android Development] stefandoesinger:
I let the auto-updater download the 20190324 build. Everything worked fine up to the point where TWRP tried to install it. My data partition is encrypted, and apparently TWRP can't unlock Android 8+ data even with the correct password.

So I copied the build to the external SD card and installed it from there. Now it is booting up fine. I see that AudioFX is still in it, so I deleted it manually.

One question about the bootloader: As far as I understand the forum posts, if I re-lock the bootloader it will validate the boot image on every boot, not just when I try to flash it with flashmode or fastboot. So if I relock, both LOS and TWRP won't boot any more. Is my understanding correct, or does a locked bootloader only guard against flashing images that aren't signed by Sony and boot them fine once they are on the phone?
[Xperia Z3 Compact Original Android Development] NeoArian:
Good morning, here is my twrp build!

It is based on [MENTION=5900960]ShadowElite[/MENTION] 's TWRP with some small modifications for OTA. I haven't tested how it works with password or pin, i don't have a screen security.

Have a nice day!
[Xperia Z3 Compact Original Android Development] pawloland:
After updating by OTA with new recovery.img which you uploaded, I still have an option to update my system, even though I have previously done this and have newest version. Is it common with los16 or it should't be like this? I attach ss (it says me to download update because i deleted zip file after update but before that, it had said to install update which was downloaded).
[Xperia Z3 Compact Original Android Development] pawloland:
I forgot to add attachmen:silly:
[Xperia Z3 Compact Original Android Development] minixperia:
Usually i have this problem sometime when I use google assistant, and usually after restart it work..

After flash the recovery, the system not start, go directly in recovery mode I have to re flash the ROM without wipe and then it start,

OTA update not showed, I have currently the build 20190316
[Xperia Z3 Compact Original Android Development] stefandoesinger:
I see the same behavior. No idea if it is behaving as intended. It feel wrong to me, but I won't lose much sleep over it.

---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------

See post #140
[Xperia Z3 Compact Original Android Development] minixperia:
OK now I can see the OTA update, i have download it but it not complete the preparing file for update, it reach 40% and then the system crash and go in recovery, and it not do anything when it is in recovery..

I will export the update and then i update manually, but I don't know the export location of the update,

if anyone knows the export location of the update please tell me, because I can't re-download the rom

( I tink it export the update on "/data/lineageos_update/")
[Xperia Z3 Compact Original Android Development] dhemker:
[MENTION=9792732]stefandoesinger[/MENTION]

Relocking the bootloader after flashing some custom ROM usually results in something softbrick like. So you have to flash an official Sony ROM after relocking.
[Xperia Z3 Compact Original Android Development] pawloland:
1. To update your system without any problem, by taping on install button in updater menu in settings you have to flash recovery.img first. It was provided some posts above by NeoArian.

2. The file path is correct.
[Xperia Z3 Compact Original Android Development] minixperia:
I have do all, but when tap to install it start to prepare to install the update and at 40% crash the system..

Now I have do the update manually
[Xperia Z3 Compact Original Android Development] pawloland:
What is your current version of rom? I also had some issues so all i have done was at first

-restoring twrp backup which i had made before messing around things connected with ota

-Flashed new recovery

-after restart i typed command from post nr #140 in su shell from google play

-restarted once again

-Checked for updates (the update have shown on the list)

-Downloaded update and installed it throught updater menu (it has took me into recovery in which all magic has happened)

-i have ended up with updated system