[CLOSED]EOL [ROM][Unofficial][8.1.0][signed][OTA] LineageOS 15.1 for Xperia Z1 compact

[Hackmann]

Gapps: There are two build variants, the standard one and the microG one. And whilst you can think about Gapps for the standard one, this is a No-Go for the microG variant. I will however add a phrase like "For the standard variant, the following applies:" after the "Don't flash Gapps on microG variant."

As i understand it, GApps, in all its variants (pico, nano, micro, mini, etc), and MicroG are something entirely different. I'm not sure which i would call the "standard" one, they are simply two different options and i would be quite happy if other maintainers would offer the option with a "security hardened MicroG".

One necessary step to be able to use OTA updates from within the ROM is to update the TWRP recovery by installing TWRP 3.2.3-1 for amami.
IMPORTANT: BEFORE UPDATING TWRP, MAKE A 'NANDROID' BACKUP IN TWRP! - The first TWRP launch after updating TWRP will most probably perform a factory reset!

I've updated to this version a few weeks ago from within TWRP and then flashed the August build. No factory reset and no other issues so far.

 

[MSe1969]

As i understand it, GApps, in all its variants (pico, nano, micro, mini, etc), and MicroG are something entirely different. I'm not sure which i would call the "standard" one, they are simply two different options and i would be quite happy if other maintainers would offer the option with a "security hardened MicroG".

I call the one "standard", because it corresponds to the scope of "official" LineageOS builds. On that one, you can (but don't have to) flash GApps, whatever flavor you like (pico, nano, bloated, fully bloated, or contaminated ) - the other one with MicroG is more "special", but I fully agree with you that it would be desirable, if this became more common.

I've updated to this version a few weeks ago from within TWRP and than flashed the August build. No factory reset and no other issues so far.

Good to know, thanks - this happened to me however on both of my Z1c devices, so I thought to better raise a clear warning.

 

[Hackmann]

I can record 4k videos (not that i really need it), but when i use OpenCamera the Camera2 API seems to be missing. Is this normal?
I've read several threads about porting the original Sony noise reducing algorithms and other features, but they seem to be outdated. How much of those features have been incorporated in this build? Does it still makes sense to apply some of those mods on top of it and which one would be recommended for this build?

 

[zoltaaaan]

I remember something from my cm-12.1- thread, maybe it is related - but not sure:
Could you please do the following? Connect your phone via 'adb' and enter a root shell, where you enter the following command:

cat /sys/devices/mdss_dsi_panel/panel_id

Please post the result.

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.

 

[MSe1969]

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.

Have you enabled root? (Developer settings)
'adb root' will only give you root when you have allowed it before.

 

[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.

 

[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

 

[MSe1969]

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

Not using magisk with this build myself, so can't answer

 

[jho55]

I have magisk installed and I can reboot to TWRP. Also using v224.

 

[esemef]

One more thing: I recommend using a current encryption. Older methods tend to be weaker.

How do we know what one is being used?
Is it possible to switch between them easily?

 

[115ek]

How do we know what one is being used?
Is it possible to switch between them easily?

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.

 

[esemef]

It depends on the android version you used when encrypting the device.

What if I don't remember?

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

It depends on the android version you used when encrypting the device.

What if I don't remember? Is there a file or command that would say?

 

[MSe1969]

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?

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 @115ek :
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.

 

[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.

 

[MSe1969]

is anyone else getting ERR_CONNECTION_REFUSED with Browser? It happens on wifi or data, it doesn't seem to be a connectivity issue.

Could you please provide some more details? Which build variant, which URL, etc.?
Not having any issues on my side

 

[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.

 

[MSe1969]

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.

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?

 

[esemef]

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

Thanks. This was it. I have no idea how all those got disabled.

 

[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.

 

[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.