[ROM][8.1.0][UNOFFICIAL] LineageOS 15.1 for ZE520KL/ZE552KL

[T M L]

Thanks you, everything excepts phone calls is working

Were you able to fix it? The play store link doesn't seem to fix it in my case.
Did you flash stock oreo before flashing the rom?

 

[Syahid M.]

Were you able to fix it? The play store link doesn't seem to fix it in my case.
Did you flash stock oreo before flashing the rom?

recovery bootloop can be fixed by flashing stock raw oreo image, used to get this problem and fixed it

Sent from my ASUS_Z012D using Tapatalk

 

[tropcontent]

Were you able to fix it? The play store link doesn't seem to fix it in my case.
Did you flash stock oreo before flashing the rom?

Hello
I flashed stocked oreo then I went back to the asus version ! I'm now waiting the 5Z to comes out

 

[T M L]

Hello
I flashed stocked oreo then I went back to the asus version ! I'm now waiting the 5Z to comes out

Too bad. Thanks anyway

---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------

recovery bootloop can be fixed by flashing stock raw oreo image, used to get this problem and fixed it

Fixed the bootloop or phone?

 

[EggyFrima]

Too bad. Thanks anyway

---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------


Fixed the bootloop or phone?

by flashing stock oreo it solved bootloop to recovery

 

[sontranngoc]

by flashing stock oreo it solved bootloop to recovery

Noo. Flash stock recovery and then flash latest version of twrp again to fix bootloop. @T M L

---------- Post added at 06:31 AM ---------- Previous post was at 06:30 AM ----------

by flashing stock oreo it solved bootloop to recovery

Noo flash stock recovery and then flash latest version of twrp again to fix boot loop

 

[T M L]

The network seems unstable. The signal strength varies even if the device is not moved

 

[SmackwaterJack]

First, let me say I'm very happy to have found this ROM and I'm really liking it so far. Thank you for your efforts!!

I think I've found a bug. I'm using your latest ROM and set a PIN for lock screen and encryption. It seems like the startup/encryption PIN isn't changing or removing when the lock screen PIN is changed or removed.

0. Upon setting up the device, I set a lockscreen PIN of 1234 and said yes to requiring a PIN on startup.
1. I then set set the security to None (which should in tandem remove the lockscreen PIN and revert to the default encryption password) and restarted. I was prompted for a PIN to start Android and 1234 worked.
2. I then re-enabled the lockscreen PIN with 5678 and restarted.
3. I was prompted for a PIN to startup, and 5678 did not work. 1234 worked.
4. I then changed to a lockscreen password, said yes to require it on startup, set it to "password" and restarted.
5. I I was prompted for a PIN to startup, and only 1234 worked. I then had to enter "password" on the lockscreen to use the device.

I can probably remove the password by wiping my user data. Which I'll probably do later tonight.

Please let me know if you're able to fix this and if I can give you any other information. I haven't looked at logcat yet so I don't know if keyguard is producing any errors, but I'll check that later as well.

Thanks!

 

[XcutionerX]

I had the same problem... But I no longer have it... Not sure how, but here are the things i did.
1) installed advanced kernel
2) installed XenonHD (automatically removes resets the kernel obviously)
(Started noticing it (startup pin in between boot) was no longer there but I remember it being there on XenonHD, maybe cause I set secure boot up to off during first boot?)
3) Back on lineage without any mods (Magisk, Advanced kernel) and the startup thing is no longer there...
Not sure if this helps...

---------- Post added at 05:23 AM ---------- Previous post was at 05:19 AM ----------

First, let me say I'm very happy to have found this ROM and I'm really liking it so far. Thank you for your efforts!!

I think I've found a bug. I'm using your latest ROM and set a PIN for lock screen and encryption. It seems like the startup/encryption PIN isn't changing or removing when the lock screen PIN is changed or removed.

0. Upon setting up the device, I set a lockscreen PIN of 1234 and said yes to requiring a PIN on startup.
1. I then set set the security to None (which should in tandem remove the lockscreen PIN and revert to the default encryption password) and restarted. I was prompted for a PIN to start Android and 1234 worked.
2. I then re-enabled the lockscreen PIN with 5678 and restarted.
3. I was prompted for a PIN to startup, and 5678 did not work. 1234 worked.
4. I then changed to a lockscreen password, said yes to require it on startup, set it to "password" and restarted.
5. I I was prompted for a PIN to startup, and only 1234 worked. I then had to enter "password" on the lockscreen to use the device.

I can probably remove the password by wiping my user data. Which I'll probably do later tonight.

Please let me know if you're able to fix this and if I can give you any other information. I haven't looked at logcat yet so I don't know if keyguard is producing any errors, but I'll check that later as well.

Thanks!

I had the same problem... But I no longer have it... Not sure how, but here are the things i did.
1) installed advanced kernel
2) installed XenonHD (automatically removes resets the kernel obviously)
(Started noticing it (startup pin in between boot) was no longer there but I remember it being there on XenonHD, maybe cause I set secure boot up to off during first boot?)
3) Back on lineage without any mods (Magisk, Advanced kernel) and the startup thing is no longer there...
Not sure if this helps...

---------- Post added at 05:23 AM ---------- Previous post was at 05:23 AM ----------

First, let me say I'm very happy to have found this ROM and I'm really liking it so far. Thank you for your efforts!!

I think I've found a bug. I'm using your latest ROM and set a PIN for lock screen and encryption. It seems like the startup/encryption PIN isn't changing or removing when the lock screen PIN is changed or removed.

0. Upon setting up the device, I set a lockscreen PIN of 1234 and said yes to requiring a PIN on startup.
1. I then set set the security to None (which should in tandem remove the lockscreen PIN and revert to the default encryption password) and restarted. I was prompted for a PIN to start Android and 1234 worked.
2. I then re-enabled the lockscreen PIN with 5678 and restarted.
3. I was prompted for a PIN to startup, and 5678 did not work. 1234 worked.
4. I then changed to a lockscreen password, said yes to require it on startup, set it to "password" and restarted.
5. I I was prompted for a PIN to startup, and only 1234 worked. I then had to enter "password" on the lockscreen to use the device.

I can probably remove the password by wiping my user data. Which I'll probably do later tonight.

Please let me know if you're able to fix this and if I can give you any other information. I haven't looked at logcat yet so I don't know if keyguard is producing any errors, but I'll check that later as well.

Thanks!

I had the same problem... But I no longer have it... Not sure how, but here are the things i did.
1) installed advanced kernel
2) installed XenonHD (automatically removes resets the kernel obviously)
(Started noticing it (startup pin in between boot) was no longer there but I remember it being there on XenonHD, maybe cause I set secure boot up to off during first boot?)
3) Back on lineage without any mods (Magisk, Advanced kernel) and the startup thing is no longer there...
Not sure if this helps...

 

[stark_br]

Just noticed that camera doesn't save pics zoomed in... It gets only on normal view area
Anyone else?

 

[Saktis_STi]

Just noticed that camera doesn't save pics zoomed in... It gets only on normal view area
Anyone else?

Yep, I am having the same issue too

 

[m0bileb0y]

Just noticed that camera doesn't save pics zoomed in... It gets only on normal view area
Anyone else?

I'm using latest carbom rom and doesn't save it either, i've tested. Didn't know this bug...

 

[stark_br]

I'm using latest carbom rom and doesn't save it either, i've tested. Didn't know this bug...

forgot to mention that this issue happens with the asus camera apk provided by planet9.
with google camera it works fine

 

[m0bileb0y]

forgot to mention that this issue happens with the asus camera apk provided by planet9.
with google camera it works fine

Yes, i use the same...

 

[planet9]

LineageOS build 2018-05-10 is up!

Please note that with this build 4K recording stopped working on Asus Camera. 1080p60fps recording started working instead.
Updated Asus Camera apks can be found here: https://drive.google.com/open?id=1_4ID3AiPLEGQkxm4WgjWVpFswImiv284
Changes:

• Improved speakerphone sound quality.
• Doubled wifi performance on 40MHz wide 2.4GHz networks and enabled TDLS.
• Removed KCal. (LiveDisplay now offers this functionality.)
• Properly enabled the Vulkan API.
• Fixed 5GHz hotspot option sometimes not selectable.
• MTP should now report the proper phone model.
• Updated vendor blobs to WW_15.0410.1803.55.
• Update to Android 8.1.0_r26, security patch level May 5, 2018.
• Rebased and cleaned up the kernel.
• Updated kernel to Linux 3.18.108, CAF-Tag LA.UM.6.6.r1-08300-89xx.0
  Thanks to @makorn645:
• Improved model detection.
• Updated media configs from mido.
• Improved wifi battery savings.
• Defined gmsclient-id.
• Properly detect single-sim devices.
• Added modem build date assertion.
• More SEPolicy rules. (Still permissive due to some missig rules.)
• Updated build fingerprint.

 

[stark_br]

Everything seems fine, tks!

 

[Sultan2304]

Guys. Please give me a link for telegram channel. The old one is no more correct

 

[Saktis_STi]

Guys. Please give me a link for telegram channel. The old one is no more correct

MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward

 

[Syahid M.]

Please note that with this build 4K recording stopped working on Asus Camera. 1080p60fps recording started working instead.
Updated Asus Camera apks can be found here: https://drive.google.com/open?id=1_4ID3AiPLEGQkxm4WgjWVpFswImiv284
Changes:

• Improved speakerphone sound quality.
• Doubled wifi performance on 40MHz wide 2.4GHz networks and enabled TDLS.
• Removed KCal. (LiveDisplay now offers this functionality.)
• Properly enabled the Vulkan API.
• Fixed 5GHz hotspot option sometimes not selectable.
• MTP should now report the proper phone model.
• Updated vendor blobs to WW_15.0410.1803.55.
• Update to Android 8.1.0_r26, security patch level May 5, 2018.
• Rebased and cleaned up the kernel.
• Updated kernel to Linux 3.18.108, CAF-Tag LA.UM.6.6.r1-08300-89xx.0
  Thanks to @makorn645:
• Improved model detection.
• Updated media configs from mido.
• Improved wifi battery savings.
• Defined gmsclient-id.
• Properly detect single-sim devices.
• Added modem build date assertion.
• More SEPolicy rules. (Still permissive due to some missig rules.)
• Updated build fingerprint.

this one is leaving a question for me, what is this fingerprint update?

Sent from my Z012DB using Tapatalk

 

[ra_si]

this one is leaving a question for me, what is this fingerprint update?

Sent from my Z012DB using Tapatalk

.........