[ROM][10][OFFICIAL] Lineage OS 17.1

DD3Boh

Recognized Developer
Feb 16, 2017
305
1,332
93
Voghera
Well, this is a bummer. I wonder why this fact is not mentioned in the "Not working" section. I'm not trying to blame anyone, obviously, this is a free project, and I deeply respect the people who are working on it, but the statement “all bugs are fixed” is a misleading information, imo.
I guess we aren't writing it mostly because almost no device writes about such things like WFD. Indeed right now wifi display isn't a native AOSP feature like it was earlier and we need caf additions for that. So it isn't technically broken as of AOSP.

This doesn't absolutely mean that I won't try to fix this just as soon as I get time, because I will together with updating blobs from new caf 8996 releases :)
 

m4f1050

Senior Member
Apr 20, 2007
1,980
206
0
So is this being worked on still? I noticed nightly builds, but what are the differences? Any bugfixes on each? What's the best build to use so far?
Is this 64-bit? When I wen to download OpenGAPPS it defaults to ARM64... Thanks.

EDIT: Wow, I messed up BIG time. I ran Android P, Erfan's Pixel Rom for over a year without issues. I installed this to get microSD card because I read "no known bugs" and I have no microSD card still. Should've kept my old ROM, worked perfect.... Meh...
 
Last edited:

704T3X

Member
Oct 6, 2016
31
3
0
hi guys. can u plz help me?? whenever i try to install a gsi rom like aosp i keep facing a boot loop. and it doesn't even matter if i try out different gsi roms, I'm gonna end up with a boot loop.
1. i am flashing system image with trebilized twrp
2. i tried installing fresh os (wiping everything then installing the system image)
3. i tried installing the rom while i had the los installed
plz help me I'm tired of hours trying
plz erfan u have any ideas? (haji mnm iranam toro khoda ye komaki kon :crying: )
AND WHAT IS THE BEST ROM FOR MOTO Z PERFORMANCE WISE?
 

feiks

Senior Member
Aug 7, 2011
71
14
0
EDIT: Wow, I messed up BIG time...
Yes, sir, yes, you did mess something up somewhere. I held out for first couple of months before transitioning from los 15 and have been a happy user ever since with no issues ( not even occasional random reboot. Yes, mirroring doesn't work, but this has always been the case for non nexus/google devices for every release's first year or so ).

I can't thank the devs enough for still supporting this now 3 year old device with it's dwindling user base which wasn't so big to begin with.
 

m4f1050

Senior Member
Apr 20, 2007
1,980
206
0
Yes, sir, yes, you did mess something up somewhere. I held out for first couple of months before transitioning from los 15 and have been a happy user ever since with no issues ( not even occasional random reboot. Yes, mirroring doesn't work, but this has always been the case for non nexus/google devices for every release's first year or so ).

I can't thank the devs enough for still supporting this now 3 year old device with it's dwindling user base which wasn't so big to begin with.
What I meant was I should've stayed on ERFAN's ppp4. I haven't seen any advantage running LOS 16 yet... I would like to have a working microSD card, that's all... Don't care about Moto mods since I don't use them or would want to carry them around... :)
 
Last edited:

Armacedo

New member
Jun 10, 2019
2
0
0
Audio messaging doesn't work for any app that I tested (Telegram, Whatsapp nor Facebook Messenger), getting back to stock rom. I'll try again once is stabler.
 

hacker-tobi

Member
Sep 22, 2017
44
17
0
Hi,

i have a strange problem. I am running LOS 16 on Moto Z since its official release and update usually once a week without problems.
But since 9th of may i always ran into a boot loop when try to upgrade.
The system boot begins normally, it asks for decryption passphrase as usual and after that it tries to boot for apx 5 mins showing boot animation.
After that it restarts and got back into boot loader.
Only when i wipe data LOS with version after 9th of May (i have in here only the version from 16th of May) boots as normal.

What i have tried:

-run fsck on data partition from TWRP - doesnt help
-wiped cache and dalvik - doesnt help
-wiped cache, system, dalvik leaving data intact - doesnt help
-re-installed also superSU - doesnt help
-tried booting multiple times - doesnt help.
-remove Android folder on /sdcard and /external_sd from TWRP - doesnt help
-wipe data: LOS boots, but this should be last option because all the apps and settings needs to be restored (and i dont use google, so no backup in the cloud).
-tried version from 16th of may and also from 10th of june (didnt have time in the mean time) - doesnt help
-wiped everything, install LOS16 newer version, boot once (successfully until here) and then go back into recovery and restore only data - doesnt help

So there must be some change between the versions from 9th of may and 16th of may which causes the problem in combination with my data partition.

the system itself is LOS16 with superSU, no other system apps (only the ones brought with OS itself), a few root apps (Titanium Backup, File Explorer,...).
Data is encrypted and free of errors.
Recovery is TWRP.

-How i can see where the problem is?
-is it possible to see the boot progress messages, e.g. from a connected pc?
-What were the changes between 9th of May and 16th of May?
(changelog from lineageoslog doesnt go back so far)

reguards,

tobias
 

double-gee

Member
Nov 29, 2014
42
5
28
Hallo Erfan, would it be possible to provide a zip file similar to your "encryptionfix.zip"
Why do we still need to install the encryptionfix in twrp after each update?
Can't the fix be included in the los-image itself?
New users will be overstrained when they can't decrypt on Android boot.
 

ischninet

Senior Member
May 1, 2016
66
8
0
why has the OEM partion 0 bytes after installing lineage 16?
why can the oem partion not be mounted during phone start?
why does the phone not start, if I replace the 0 bytes oem partition with an" oem partition backup" from a previous Resurrection backup?

---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------

After installing Lineage 16 again (and the encryption fix from erfan, the phone was able to boot again but the oem parion is back to 0 bytes and not readable during phone start
Any one any idea?

---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------

Hi 704T3X,
I had this issue as well with one device. After using the app "Bluetooth Pair" everything was back to normal

---------- Post added at 05:32 PM ---------- Previous post was at 05:19 PM ----------

I would give a **** about this oem partition but its the reason that I cann not do an adb backup directly to the pc. It stops when it cannot read this oem. When doing a backup to my usb stick, the problem does not occur.
 

joebarnickle

Member
Jun 5, 2013
34
10
28
mobile network issue

In fact me and some other users have problems with mobile network (some apps can't connect proper to network) it would be nice if anybody could provide a solution.
Apart from that this rom is working perfect.
 

engr.lefty

Member
Feb 8, 2017
14
1
3
Can someone please help with my problem? I cannot boot to twrp recovery anymore after i flashed LOS 16June 8 build. Whenever i try to go to recovery, it was only stuck at TWRP screen. I tried to reflash twrp because maybe something is wrong but didnt suceed. I attach a photo below trying to reflash twrp. Please help me, thank you
 

Attachments

  • Like
Reactions: chwl

anyone23

Member
Nov 11, 2014
37
10
0
I have installed this rom on my dad's Moto Z however now the device keeps crashing randomly every few hours. I have attached the logs I could find.

Is there anything I can do about it? It's a pretty slim system with LOS 16, su addon, open gapps pico and just a hand full of apps. The LOS version is from late May however...

Edit: Added the *ramoops logs as requested in OP.
 

Attachments

Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone