yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Compact Android Development] zoltaaaan:
I still have a problem, where my third party touchscreen freezes quite regularly. The display freezes, when mobile internet is enabled, but there is no signal or the signal is lost. It never unfreezes on it's own, you always have to switch it off with the red button.

Therefore, I tried to read this file to give you the info, but it says "Permission denied"

I am not quite sure how to enter a root shell. I tried the command

./adb.exe root

but there was no noticable reaction to that.

When I try to run

cat /sys/devices/mdss_dsi_panel/panel_id

I get the same result before and after the root command.
[Xperia Z1 Compact Android Development] MSe1969:
Have you enabled root? (Developer settings)

'adb root' will only give you root when you have allowed it before.
[Xperia Z1 Compact Android Development] MSe1969:
New builds with September ASB patches

Hi all,

new builds (Sec. String 2019-09-05) available for download (also offered through OTA update):

A. Standard build

https://www.androidfilehost.com/?fid=1899786940962582142

B. hardened microG build

https://www.androidfilehost.com/?fid=1899786940962582143

Happy flashing - regards, M.
[Xperia Z1 Compact Android Development] JIJOK:
cool, new update thanx !

ps : I know this is not the right place but no answer on the other side, Am I the only one who can't reboot to TWRP with latest magisk manager (224) ?

ps2 : only can boot with buttons
[Xperia Z1 Compact Android Development] MSe1969:
Not using magisk with this build myself, so can't answer
[Xperia Z1 Compact Android Development] jho55:
I have magisk installed and I can reboot to TWRP. Also using v224.
[Xperia Z1 Compact Android Development] esemef:
How do we know what one is being used?

Is it possible to switch between them easily?
[Xperia Z1 Compact Android Development] 115ek:
It depends on the android version you used when encrypting the device.

The easiest way to switch would be taking a backup, formatting /data, restoring backup and encrypt with LOS 15 again.

However - encryption on our device isn't that safe as the bootloader is unlocked. Persons knowing what they do can brute force your key. Long keys help to keep them out for a bit longer...

Anyway: to prevent snoopy people from accessing your peronal data (or thiefs.. whatever) the encryption should be sufficient I think. So I'd always advise you to encrypt.

And always keep in mind: nothing is secure.
[Xperia Z1 Compact Android Development] esemef:
What if I don't remember?

---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------

What if I don't remember? Is there a file or command that would say?
[Xperia Z1 Compact Android Development] MSe1969:
No idea - but I would not worry too much. Having a long password is more important than the Android release, which was used to encrypt the device.

If you insist on having the encryption with the latest Android version, do as advised by [MENTION=8036586]115ek[/MENTION] :

Make a nandroid backup with TWRP, backup your internal storage(!), format the /data partition (this will also wipe the internal storage, that's why you must back it up before), restore your backup and the internal storage and then encrypt again.

If you ask me, not worth the effort - rather get used to a longer, nontrivial password instead of a four-digit PIN, or even a pattern nonsense, that brings more security.
[Xperia Z1 Compact Android Development] esemef:
is anyone else getting ERR_CONNECTION_REFUSED with Browser? It happens on wifi or data, it doesn't seem to be a connectivity issue.
[Xperia Z1 Compact Android Development] MSe1969:
Could you please provide some more details? Which build variant, which URL, etc.?

Not having any issues on my side
[Xperia Z1 Compact Android Development] esemef:
Latest standard build, it happens with every single url. It was happening with the previous build as well.

It started on 24th September. I updated to the latest to see if it fixed it but it did not.
[Xperia Z1 Compact Android Development] MSe1969:
Is it only happening with the Browser app or all apps on the phone?

A couple of options to try:

- Boot into recovery and wipe cache & dalvik (that does never harm)

- If only the Browser app: Check the data usage option of the Browser app (Settings - Apps), to see, whether Internet access is still allowed, alternatively clear the Browser app data

- If all apps: Make a backup with TWRP and perform a factory reset to see whether it works again. If not - something is wrong with your device, if yes, you need to think about how to initialize your device (either start from scratch or restore your backup and do an individual backup of the apps of your choice with adb or titanium backup)

- I assume you do not use any custom kernel or fancy magisk or xposed modules?
[Xperia Z1 Compact Android Development] esemef:
Thanks. This was it. I have no idea how all those got disabled.
[Xperia Z1 Compact Android Development] MSe1969:
New builds with October ASB

Hi all,

new builds are available for download having the 2019-10-05 security string:

A. Standard LineageOS 15.1

https://www.androidfilehost.com/?fid=1899786940962608878

- System Webview on 77.0.3865.92

B. Security hardened microG build

https://www.androidfilehost.com/?fid=1899786940962608877

- Bromite Webview on 77.0.3865.104

- AuroraStore updated to 3.1.3

In the course of today, the updater app will propose you an OTA update accordingly (if you are at least on the respective August build of this ROM).

Regards, M.
[Xperia Z1 Compact Android Development] MSe1969:
New builds with November 2019 ASB patches

New builds available with November 2019 ASB patches (sec. string 2019-11-05):

A. Standard variant

https://androidfilehost.com/?fid=4349826312261626355

B. Hardened microG build variant

https://androidfilehost.com/?fid=4349826312261626354

- Updated Bromite SystemWebview to 78.0.3904.72

OTA updates will be offered from within the ROM (Updater app), if you are at least on the August build of this ROM.

Regards - M.
[Xperia Z1 Compact Android Development] JIJOK:
nice update, but some "problem" here, download works good, also restart to recovery, install too but when the phone keep on the boot lineage screen forever. I force turn off and then restart normally. I am using twrp 3.2.3-1 , could the recovry version be the problem or something else ?
[Xperia Z1 Compact Android Development] MSe1969:
I also have TWRP 3.2.3-1, and to really make sure, I have downgraded to my October build and did the OTA update, all went perfectly fine!

So can't tell you more - just a hint: BE PATIENT after an update, the first boot indeed takes long; of course I don't know how long you have waited, before you have decided to force turn off. Maybe there indeed was an issue, so glad it finally worked out for you - just in general, don't "panic" if the boot animation is there for even several minutes.
[Xperia Z1 Compact Android Development] maciej03:
I changed to this rom build with MicroG from LineageOS 14.1 by munjeni.

- Wifi works fine only with disabled Captive portal mode

- GPS is broken. 0 satellites found. I tried back to stock, and flash again. And change #NTP server gps_debug.conf. It still doesn't work
[Xperia Z1 Compact Android Development] 115ek:
Step 1: RTFM (in this case the OP)

which leads to step number 2: Create a bug report we can deal with or your post will be ignored.

Concerning captive portal mode [MENTION=7929484]MSe1969[/MENTION] is the right one to ask.

Concerning GPS: install SatStat, run it, wait for gps and share a screenshot (like this one).

But in any case: Create a proper bugreport or we can't help. What was the scenario? What apps did you use? What settings? Exact error? And of course: Logs!
[Xperia Z1 Compact Android Development] maciej03:
Ok. Every app maps is inaccurate as the location only works from the cellular network.

I attach a screenshot and hope a good log.
[Xperia Z1 Compact Android Development] 115ek:
From your screenshot I'd guess you are inside a building. (correct me if I'm wrong).

GPS inside buildings isn't a good idea - especially with older devices. Can you test it outside again (or at least near a window...).

Line of sight between satellites and smartphone is always a good idea.

I think this should already fix the problem.

Concerning your log: Please share the complete log (if the first thing still doesn't help) you get with

adb logcat -b all > log.txt

If you've got security concerns you can also send it via PM [MENTION=7929484]MSe1969[/MENTION] or to me.
[Xperia Z1 Compact Android Development] JIJOK:
This are my gps device only if you are curious

1st image : satstat --- 2 : gpstest ----- 3 : osmand

about 2 mins to get working gps and also using global optimized gps file replacer from magisk

Question : Can I manually update rom from twrp ? download zip, boot on twrp, flash ..... done ? or need to wipe ?
[Xperia Z1 Compact Android Development] MSe1969:
New builds with December 2019 ASB patches

New builds available with December 2019 ASB patches (sec. string 2019-12-05):

A. Standard variant

https://www.androidfilehost.com/?fid=4349826312261654448

- Updated System Webview 78.0.3904.96

B. Hardened microG build variant

https://www.androidfilehost.com/?fid=4349826312261654447

- Updated Bromite SystemWebview to 78.0.3904.119

- Updated AuroraStore to 3.1.5

OTA updates will be offered soon from within the ROM (Updater app), if you are at least on the August build of this ROM.

Regards - M.
[Xperia Z1 Compact Android Development] zoltaaaan:
Hey, your post is from a while back. But the problems occured every now and then and now I started to look into it again.

cat /sys/devices/mdss_dsi_panel/panel_id

result: auo novatek 720p cmd

The system info:

Recovery: TWRP 3.2.3-1

LineageOS-Version: 15.1-20191110-UNOFFICIAL-signed-amami

Kernel:3.4.0-g27406e978f59-45979-g7f017131843f (gcc version 4.9.x 20150123 (prerelease) (GCC))

Build: lineage_amami-userdebug 8.1.0 OPM7.181205.001

Right now, there is another more urgent matter. I set the phone up completly new a few days ago. I flashed the TWRP version 3.2.3-1 and installed the Lineage version with OTA updates. The phone worked fine and I configured Android and installed an OTA update. I used the SD card as internal storage.

As of today, the phone did not recognise the SD card. Apps do not work anymore and it is a big problem.

The SD card is somehow corrupted. There are two partitions on the card. A small one (16 MB, exFAT) and a big one (59,46 GB, unknown format). The phone cannot recognize the card and windows is not able to format the card as well.

Attached are some logfiles.

Edit: I tried to install catlog, to log what happens, when the screen freezes next time. The app crashes instantly. I attached the logcat from during catlog crashing as well: View attachment catlog_crash.log
[Xperia Z1 Compact Android Development] MSe1969:
Hi

in regards to your SD-card issue:

You have used the "adoptable storage" feature of Android and formatted your SD in a way to become part of your internal memory. Whilst this is a cool feature on the one-hand side, it has some really serious drawbacks - this article here gives a good overview (it starts with the drawbacks, so no need to read through everything). You are exactly in that situation, and as you said, your SD card is somehow corrupted - and that means, unfortunately, you need to do a factory reset . . .

In regards to the panel_id - let me search a little bit... I'll get back to you on that.
[Xperia Z1 Compact Android Development] zoltaaaan:
Well, I took the card out of the phone and put another one in. The new card (slower and less capacity) is formatted as external for now. I wil read the article later, thank you.

I can give you another logcat from during the screen freeze and restart. But also later today or maybe tomorrow.
[Xperia Z1 Compact Android Development] MSe1969:
Not necessary with the logs - as you said yourself, the card has issues, and it used to work before - so there is no mistake in the ROM, and thus nothing I could do - the system simply cannot access certain files necessary to operate or where it expects them and now goes crazy about it. Nothing significantly else is what the logs indicate (did not go through them in much detail, tbh, but roughly that's it).

As far as I understood the article, an adopted SD card does really logically become part of the /data partition and not "only" part of the area below the symlink /data/sdcard - therefore your system will most probably continue to be lunatic, even after you have put another SD card in - that depends, which pieces of the entire /data partition are physically on the corrupted SD - therefore I am afraid, you will have to factory reset...
[Xperia Z1 Compact Android Development] zoltaaaan:
Sorry for the confusion. The issue with the SD card is new and just happened after I set the phone up with new recovery and new version of the rom. To be honest it does work normally right now. The installation was only a few days old, when the SD card stopped working. The system is not behaving wrong right now.

Do you think a factory reset with the broken SD card inside will also fix the SD card? I was completly puzzled that it isn't even possible to format the SD card in windows right know or completly kill it with some other software. I do not need to save any contents, but I want to use the fresh SD card again.

There was a separate issue. The older issue with the touchscreen and the frozen device. Today I reproduced the freeze. The phone freezes, when it has no mobile internet AND there is user input on the touchscreen. It reproduces so exactly, that when you are in a train and loose your connection every now and then, you have to avoid touching the screen to avoid freezing. When you touch it when it has no mobile internet, it freezes.

And today I made a logcat and froze the phone.

That was the issue, where you wanted to know my touch panel ID for.

I did not manage to get a kernel log, but maybe the rest helps.
[Xperia Z1 Compact Android Development] marsa47:
IFAIK the screen freeze is related to non-original screens (drivers issue). I have one Z1c with non-original screen (cheap repair) and one in original condition. The one with the changed screen freezes if the screen is ON and the network connection goes to 2G mode (e.g. bad reception). If the connection mode cycles with the screen OFF, there is no problem. But if you use the phone in that exact moment, it will freeze and you can only hard reset it.
[Xperia Z1 Compact Android Development] MSe1969:
Just to let you know: I have the same result, so my idea will not lead to anywhere, in my cm-12.1 thread, we had a kernel issue a while back which was based on different hardware components, but that is not the case for your device. I though to look into that direction, but wrong path obviously, hence "Sorry, no idea"
[Xperia Z1 Compact Android Development] zoltaaaan:
I don't know where I read it, but somewhere I read something about a driver for after market displays. That idea sounds odd to me, since aftermarket displays includes different panels. Is there some kind of generic touchscreen driver, which might work better than the stock driver?
[Xperia Z1 Compact Android Development] zoltaaaan:
You have the same result to this query, but you have a stock touchscreen?

Maybe that is the problem. Shouldn't the phone know, there is another panel built in? Maybe then it would handle it differently? I am just making assumption here, I have no idea about Android Development.

But this should be a problem for a lot of people, right? People who put in a new touchscreen in an old phone should be also those people who install custom roms to it. (making assumptions again) Does anyone know, if that general problem is present for various devices?
[Xperia Z1 Compact Android Development] MSe1969:
The issue, which we've had in the cm-12.1 thread back in 2017, was based on the fact that the Z1c indeed was produced with different hardware components and we had solved it. So I simply thought if there was another component, there was the possibility to look at the fix again and adapt. But as said, that won't go...

Usually, replacing HW components should not cause issues, but obviously it does in your case...
[Xperia Z1 Compact Android Development] 115ek:
There are indeed different firmwares for different panels.

I just checked /system from latest stock (actually for a different thing...) and stumbled over system/etc/touch_fw_update.sh (appended it)

And there are different firmware binaries called touch_module_id_0x4d.img, touch_module_id_0x4e.img, touch_module_id_0x5d.img, touch_module_id_0x45.img, touch_module_id_0x48.img, touch_module_id_0x53.img and touch_module_id_0x54.img under system/etc/firmware

It seems we already ship them - however there's no update script. Maybe there's an other way to determine what to load (directly in kernel driver?).

I hadn't got time to investigate it further. Just wanted to share my findings. Feel free to dig into it :good:
[Xperia Z1 Compact Android Development] rkha:
Thanks a lot for an excellent ROM! Really brought life back to the Z1C :)

Has anyone gotten Netflix to run with this ROM? Installing from Play Store works, but cannot open as it says the device is not supported. It then links to a website where you can download an older version of the app (https://help.netflix.com/en/node/57688) - however that won't start either since its for Android 4.4 to 7.1.2. I've tried various versions from APKMirror as well with no success. I guess the problem is Netflix is blocking Amami no matter the Android version?
[Xperia Z1 Compact Android Development] MSe1969:
Thanks for the positive feedback.

Regarding Netflix, seems that your theory indeed applies.

:eek:

I could not believe it and tried first to manually download the older version 7.31 (this solved a similar issue on my OP3T with Netflix, which is my main device) and afterwards also the "compatibility" app on the Netflix page.

But it seems that the "experts" at Netflix use the device fingerprint to connect to the Netflix server, to perform a device database lookup to decide - independent from the real technical situation - that the app can't run and then let the app simply refuse to start. HOW STUPID IS THAT???

I am speechless - not only about the lack of Android knowledge, but the effort to implement such a solution...

As said, seems to be the case - maybe there is some Magisk or Xposed module to spoof a different device?
[Xperia Z1 Compact Android Development] MSe1969:
New builds with January 2020 ASB patches

Another month, here we go - security string 2020-01-05 :

A. Standard build

https://www.androidfilehost.com/?fid=4349826312261701394

- System Webview on 79.0.3945.116

B. hardened microG variant

https://www.androidfilehost.com/?fid=4349826312261701393

- Bromite Webview on 79.0.3945.107

- Updated AuroraStore to 3.1.7

- Updated AuroraServices to 1.0.5

Updates are also directly offered in the Updater app (Settings => System => About Phone => Updates)

Regards, M.
[Xperia Z1 Compact Android Development] MSe1969:
LineageOS 16.0 Test build

Hi all,

I have created a LineageOS 16.0 test build for the build flavor B (Security hardened microG build), which can be downloaded here:

https://androidfilehost.com/?fid=4349826312261715473

(In fact, the equivalent LineageOS 16.0 build, which fits to build flavor A and could be "dirty-flashed" over the build variant A (of this thread) is this build )

If you have encrypted the /data partition using a cm-14.1 ROM, as recommended in the OP, the LineageOS 16.0 build won't be able to decrypt, independently of whether you clean-flash or dirty-flash - dirty-flashing works by the way, but you need to follow the below steps:

Update TWRP to the version from this thread

Make a nandroid backup with TWRP and make a backup of the Internal memory (both steps are important, don't skip them!)

Your device is not encrypted or you have encrypted it using

LineageOS 15.1

? => Easy: Dirty-flash (or clean-flash) the LineageOS 16.0 test build and all good.

Your device has been encrypted with a cm-14.1 build? Or you are already in the situation that the LineageOS 16.0 build tells you it can't decrypt? => Follow the steps below exactly as described.

Boot into TWRP and

format

the /data partition

Reboot into TWRP

Install the last LineageOS 15.1 (favor B) build and boot into an empty system (don't restore anything,yet)

Encrypt the device now - it'll take only a couple of seconds until the device reboots - wait for the reboot to finish

Restore now the Internal Memory and reboot to TWRP

if you want to "dirty-flash", restore the nandroid backup now and afterwards, still in TWRP,

flash the LineageOS 16.0 build => done, finally

Please feedback, how it went - thanks

M.
[Xperia Z1 Compact Android Development] jho55:
[MENTION=7929484]MSe1969[/MENTION]: Should not your post be in the LOS 16.0 thread? Just wondering. :)
[Xperia Z1 Compact Android Development] MSe1969:
I wrote it here to talk to the current LineageOS 15.1 users. [MENTION=8036586]115ek[/MENTION] and I plan to stop the L15.1 builds and to continue in [MENTION=8036586]115ek[/MENTION]'s L16.0 thread with the additional microG variant, as L16.0 runs now smooth and stable, also for the Z1c. But before officially announcing, I would like to get some testing feedback.
[Xperia Z1 Compact Android Development] Yokurt815:
Clean installation went fine. MicroG settings also done.

More info to follow. But might take some time. This is only the old "backup" device...
[Xperia Z1 Compact Android Development] jho55:
Currently I prefer the 8.1 version because I like the ui a little bit more than 9.0 and I do not see any real differences between both. But I can understand that it is maybe too much work for you guys to keep everything update. Maybe I need to check out 9 or 10(which i tested on my 2nd backup z1c and I liked it).
[Xperia Z1 Compact Android Development] 115ek:
Is there still interest in running netflix on the Z1 compact? I just enabled it on a Lineage 16.0 test build but it should be easy to bring it to 15.1 as well.

Maybe we can ship it together with february ASB's. [MENTION=7929484]MSe1969[/MENTION] you need to pick this topic. However I haven't got resources to test it on 15.1 atm as I'm busy with 16 and 17. But if there are some series junkies among us we should consider this option.

15.1 will be dropped by the LOS team as soon as 17.1 comes out. And this will happen soon. For us it's a lot easier to depend on work already done by a lot of other volunteers. Else you have to do everything on your own (like [MENTION=7929484]MSe1969[/MENTION] with his 12.1).

And I don't see a good reason for supporting 3 different versions at once.

But if you really want to stay: just do it. Sources are available and you can build on your own if you like to :)
[Xperia Z1 Compact Android Development] MSe1969:
Cool! Works perfectly, just did a little test - yes, will be part of Feb. 2020 ASB release.
[Xperia Z1 Compact Android Development] MSe1969:
New Builds with February 2020 ASB

Hi all,

new builds with the February 2020 ASB updates are available and already offered via the updater app:

A. Standard LineageOS 15.1

https://sourceforge.net/projects/li...20200209-UNOFFICIAL-signed-amami.zip/download

B. Security hardened microG build

https://sourceforge.net/projects/li...8-UNOFFICIAL-microG-signed-amami.zip/download

ASB Security string 2020-02-05

Replaced DRM lib (fixes issues with Netflix)

Standard flavor: System Webview on 79.0.3945.136

microG flavor: Bromite Webview on 79.0.3945.139

microG flavor: Updated AuroraStore to 3.1.8

Regards, M.
[Xperia Z1 Compact Android Development] jho55:
[MENTION=7929484]MSe1969[/MENTION]: Are the DRM lib fixes only in the microG build?
[Xperia Z1 Compact Android Development] MSe1969:
No, in both build variants.
[Xperia Z1 Compact Android Development] rkha:
Great! Thanks [MENTION=8036586]115ek[/MENTION] and [MENTION=7929484]MSe1969[/MENTION]! Will try the OTA update and test Netflix