yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] magur0:
No. I did a fresh install when LOS(13) was released and encryption was working... still running till today.

I also succeeded taking a nandroid-backup from LOS13 while it was decrypted in TWRP and restore this image to another device. On the restored device I enabled device encryption again - and it worked. I'm not 100% sure but I think it was LOS13-20170805-nightly.... maybe you give this one a try :fingers-crossed:
[Samsung Galaxy Nexus] osm0sis:
Rooted? I wonder if Magisk is interfering.. hmm.
[Samsung Galaxy Nexus] Android-Andi:
Anything on F2FS? Encryption doesn't work on f2fs if I am not wrong
[Samsung Galaxy Nexus] osm0sis:
Should be ext4 if I recall. I'll try unrooting, and if that fails, downgrading to 0805.
[Samsung Galaxy Nexus] nailyk:
Encryption was working fine with for me on f2fs.

IIRC we have a metadata partition so the -16kB length shouldn't be a problem.

Here you have an unsecure boot to get logs while encrypting/decrypting (probably 13.0 but could be 14.1).

Maguro take long time to encrypt (around 20 min) right after a wipe.

On z3 thread we have lot of troubles with magisk and co breaking some part of init scripts who can be the source of your troubles.
[Samsung Galaxy Nexus] hga89:
I just encrypted my hitherto-unencrypted second GN running L 13 from August 12th. It went fine and I could reboot without problems.
[Samsung Galaxy Nexus] osm0sis:
Must be Magisk. I'll try without it over the weekend.
[Samsung Galaxy Nexus] magur0:
I don't to magic with magisk (just use 'integrated' root)... so could be that this is cause!
[Samsung Galaxy Nexus] MrFlashGame:
Hello there,

after using the newest nightly for quite a lot of time I've found some bugs which I would like to report here (Sorry, the official LOS bugtracker is too confusing for me).

I use LOS with Magisk(Two modules: IOS10Emoji, Unified Hosts) and OpenGapps. All of the bugs I reportes here are reproducable on my device.

1. If I apply a theme with the Designer App the SystemUI crash almost everytime (Sometimes not but I dont understand why).

2. The screen doesn't turn off in idle. This also affects the Lockscreen (The screen becomes a little bit darker after a time but never turns completely off automatically).

3. This is not a bug but I wanted to report it here anyways: I think the point "Update CM Recovery" in the Developer Settings is obsolete.

Would be nice if a dev could look into this and fix this. I've attached a bug report. If you need any other info please let me know.

Greetings Nils :)
[Samsung Galaxy Nexus] nailyk:
AFAICT 3. is not a bug because lineage is provided with recovery. I guess if you tick it then OTA update you will loose twrp.

about 2. it is interesting because I have the same issue on z3/z3dual. Not all the time but looks like it happens if usb cable was unplugged while powering on/rebooting the device.

Can you confirm?

1. IIRC themes are not supported anymore on lineage because it was a cyanogenmod (r) mod.

Feel free to correct me.
[Samsung Galaxy Nexus] MrFlashGame:
Hello [MENTION=6979267]nailyk[/MENTION], as first thank you very much for your investigation. I didn't know that LOS still has its own recovery because I've never seen it on the official download page. But you are probably right there. I think we should at least rename this to LOS because CM is not the name of this ROM anymore. About 2: I can confirm that, I have just tested it. The screen has turned off now properly. About the CMTE stuff: I think it should be supported or removed, but this isn't a dealbraking bug and there is probabky no easy way to work around it so we should mayve just leave it as it.

Greetings Nils :)
[Samsung Galaxy Nexus] nailyk:
My bad, here is a 13.0 thread and was talking about 14.1.

In 14.1 looks like the translation have been changed:

jenkins@4638e1e340ef:~/packages/apps/Settings/res/values-en-rGB$ rgrep "update_recovery_title\|update_recovery_summary"
cm_strings.xml: <string name="update_recovery_title">Update recovery</string>
cm_strings.xml: <string name="update_recovery_summary">Update the built-in recovery with system updates</string>
[Samsung Galaxy Nexus] osm0sis:
Yup. After a couple of false starts, it worked once unrooted. :good:

Edit: Also can verify OTAs still don't work in [MENTION=5153662]Android-Andi[/MENTION]'s 3.1.1-1 recovery due to the uncrypted block map ORS command failing.
[Samsung Galaxy Nexus] hga89:
Spontaneous reboots when file system is encrypted

I have two GNs running L 13 with the file system encrypted and both reboot several times a day, both when not in use and also when in use. Has anyone else noted this problem?
[Samsung Galaxy Nexus] frusso3:
Hi guys, I'm still with 11 cm and I'm fine. I would like to install this lineage and I wanted to know: is it okay for every day? Any problems? Are the pictures good? Does USB otg work? I still twrp 2.8.7, do I have to update it? Thank you all
[Samsung Galaxy Nexus] bamtan2:
To stay "fine" you should not update. Updates are good when you want to have fun, or if there is a feature you are missing. I am using 5.1 and I have not updated because it works fine for me. There will be many changes if you update. The chance of having problems is higher than 0%. But many happy users are here.

Always use newest TWRP, just in case. In THIS case, yes, it is required :)
[Samsung Galaxy Nexus] frusso3:
Thanks for the sincere response, then I stay with cm11. I was undecided between this and 6.0 aosp
[Samsung Galaxy Nexus] hga89:
I have some more information on the crashes: although some of the crashes occur when the phone is /not/ being used, on other occasions it crashes when I am using firefox and the webpage might be complex or have problems loading. Might it be that the OS crashes when it encounters a particular low-memory situation?

Some of the crashes result in a "soft"(?) reboot and when the phone reboots it cannot connect to the phone service provider (and this can only be resolved with a hard reboot). Other crashes result in a "hard" reboot where I have to reenter the encryption password after which the phone finishes booting and does connect to the phone service provider. I speculate that when a "soft" reboot happens it does not initialize everything properly?
[Samsung Galaxy Nexus] GerardJ:
Spontaneous reboots

I do have this problem since updating with the last NIGHTLY (13.0.20171002-NIGHTLY-maguro). Reboots while the phone is inactive, about 3 or 4 times per 24 hours. It shows when I re-activate my phone out of sleeping condition, and have to enter the SIM card pin code.
[Samsung Galaxy Nexus] MrFlashGame:
Yep I have similar problems too, not with the SIM Unlock (I use normal PIN, maybe you should test this too), but sonetimes the phone soft reboots. And in some really rare cases it keeps stuck in the "Upgrading Android" Screen.
[Samsung Galaxy Nexus] nailyk:
On my latest 13.0 tries device stuck at 'upgrading android' if it is booted with charger.

Am not working on (maguro) 13.0 anymore but /proc/last_kmsg should be helpful to debug this.
[Samsung Galaxy Nexus] hga89:
You and I see this because the phone hangs: in your case asking for the SIM pin code, in my case asking for the encryption password. If the phones were not hanging for us, we would not be aware of these frequent crashes...
[Samsung Galaxy Nexus] hgmichna:
Random Reboots

In my experience, last_kmsg is singularly useless for debugging spontaneous reboots for more than one reason.

Google is just not interested in solving this widespread problem, otherwise they would add a log that is actually useful.
[Samsung Galaxy Nexus] GerardJ:
Spontaneous reboots

Agree. Once you are aware of these crashes, you can also see the effect in Settings - Battery, where the green graph shows the white interruptions.
[Samsung Galaxy Nexus] guest4711:
...or when displaying the uptime, either using terminal

maguro:/ $ uptime
19:10:24 up 7:31, 0 users, load average: 0.95, 1.01, 1.19
maguro:/ $

or via settings -- about phone -- status -- uptime.
[Samsung Galaxy Nexus] hga89:
Is L 13 for the GN still being developed and this bug might be fixed?
[Samsung Galaxy Nexus] GerardJ:
Spontaneous reboots

The problem persists, also after installing the latest 13.0-20171007-NIGHTLY-maguro.
[Samsung Galaxy Nexus] MrFlashGame:
Hey there, with the newest LOS nightly I have a little problem: When I install an App there is a big chance that there is no shortcut for the app (But sometimes it works anyways). And it doesn't matter from where I download it. Play Store, XDA Labs and APK, everywhere the same problem. The only way to start the app is over the Play Store. But the App itself works always fine. Does somebody know a way to recover the shortcuts (Maybe with a Terminal Command or so). I have btw no Launcher installed or so.

Regards, Nils
[Samsung Galaxy Nexus] bamtan2:
Maybe this is a bug with the latest build, or maybe it's something else.

Try the default launcher or Nova Launcher. Make sure to check the app drawer for you app. From there you can long-press and drag the app shortcut to the main screen. You can also see your list of apps from the apps section of the system settings.

Each launcher has a different setting for automatically creating home screen shortcuts when an app is installed. Check the launcher settings.
[Samsung Galaxy Nexus] MrFlashGame:
No it's not a Bug in LOS. I reset my phone (wipe data, system, internal storage, cache) and now everything works fine. I think I just broke something but IDK what. And for sure I checked App drawer. That was my problem that I had no chance to put the shortcut on my homescreen. But thanks a lot for your answer :)

Greetings Nils
[Samsung Galaxy Nexus] hga89:
Remaining bugs in L 13

[MENTION=6979267]nailyk[/MENTION] [MENTION=2633638]Ziyan[/MENTION]: Any possiblity that you may be able to take a look at the remaining bugs in L 13 for GN? As it is, its a huge step up from CM 10(?) that I used to run but there are still a few significant bugs left that affects use in major ways.

Thank you.
[Samsung Galaxy Nexus] bamtan2:
you will need to list the bugs for them to know what they are :(
[Samsung Galaxy Nexus] hga89:
That has already been done by me and by others in this thread so it should not be an issue.
[Samsung Galaxy Nexus] nailyk:
TBH I don't think someone will fix 13.0.

14.1 thread is open, omnirom N too.

IMHO if some dev have time for this device, he will work on O, not on M
[Samsung Galaxy Nexus] hga89:
That is very unfortunate since there are some issues that severely impacts it being used on a daily basis. I will stick my head out and say that while I appreciate the developers trying to make alternative versions of the OS available for a variety of devices, I have yet, in the five, six or so years I have been using CM/L, found a version of the OS that has progressed beyond a beta. Betas, of course, be of varying value to users, but is still a beta. I would personally much rather have a version of L 14 where everything works than yet another beta of a later version of the OS.

Sticking the head out even further, CM/L is really a hobbyist project for developers and end-users who like to tinker with their devices, never a replacement of the native OS. I am not familiar with other open-source versions of Android to say if it is true for them as well.
[Samsung Galaxy Nexus] nailyk:
But maintaining device is not the same as maintaining rom.

Lineage 13.0 (rom) still looks active but as my maguro is running N right now, I wont downgrade to M.

Also another problem is since Lineage don't publish rom keys anymore switch from custom lineage to official (and opposite) require a wipe.

All this things makes bug solving on multiples versions harder.

14.1 is tagged alpha cause not many feedback on it. Some people seems to be happy with it.

Edit: Not well read the first time (lack of vocabulary ;))

I agree with [MENTION=8010004]guest4711[/MENTION] and mostly stocks roms are not usable. Am using custom roms only on all my devices (not so much but a few anyway), first because of less EvilCorp.

It is really good to report issue, sadly the android world being what it is, maintainer do not decide what version they will work on.

Am working really hard on this ( https://review.choose-a.name/#/q/owner:"nailyk-fr+%3Cnailyk_git%40nailyk.fr%3E" ) but not for maguro as it is not my DD. Sorry for maguro users.

I have planned working on maguro as soon as N got officially merged, then O came up and The omnirom members told me the z3 will never get official N, need to bringup on oreo.

The plan remain unchanged.

FI difference between 'unofficial' roms and 'official' ones is (mostly) who build it.

</www.mylife.fr>
[Samsung Galaxy Nexus] guest4711:
So I don't understand why you don't stay on the stock version...

But I have never found a stock version with more than beta quality. All have bugs, some security related, some simply don't do what they are supposed to.
[Samsung Galaxy Nexus] hga89:
Thank you for your reply. It may be that stock ROMs are "unusable" from one perspective, however, it is generally expected that all features work on the ROM even though some users may not agree with what is included etc.

As for L 13 on GN, the most serious issue is the random reboots. Of course, there is no stock 7 for this phone but when official stock ROMs were released, such issues would be fixed or users would raise a ruckus.

You mentioned that L is not releasing keys so that is possible to switch between different releases - why would they not do that? Are they trying to make L even more irrelevant?

Last, when I download the "nightlies" which, of course, should be called "weeklies" since they are weekly not nightly, why are the zip files not signed, by L, I assume? Does it have to do with the above? Is this not a security risk?

Almost last, why spend time working on the L version of Oreo for GN if that also will never be finished? What's the point? Is this not a huge waste of time that would be better spent on something else (i.e., outside L)?

It is not hard to understand why CM failed as a commercial venture.
[Samsung Galaxy Nexus] runekock:
[MENTION=3443260]hga89[/MENTION]

CyanogenMod was not the same as Cyanogen Inc. CM and LOS have always been for hobbyists, like you said.

Since they do it for free, devs should always work on whatever they consider the most fun. For some, it is fun to provide value for users, for others to explore new territory. We users should be happy whatever we get.

I do consider it a failure of the commercial system that we have no official way of getting security updates beyond three years. Look at PCs where Microsoft provides ~10 years of updates (though not necessarily for drivers). Maybe a subscription model could be used?
[Samsung Galaxy Nexus] nailyk:
AFAICT so far reboot issue is fixed on 14.1
[Samsung Galaxy Nexus] bamtan2:
Last I heard, Andi and Ziyan preferred to work on Unlegacy ROM. Maybe try that instead of Lineage?
[Samsung Galaxy Nexus] hga89:
Maybe, I am, however, running L 14.1 on my Tab S2 with success so I am keen to stay in the same ecosystem.

---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------

I certainly did not get any security updates for three years when I bought my first Android tablet but I understand that this may be the case nowadays, although I suspect that may not be the case for all devices though.

I know that CM and Cyanogen, Inc. were different ventures but the latter built on the former even though the business plan was flawed from the very beginning. I can't say I feel sorry for the venture investors since they did not do their homework before investing.

My expectations are higher than yours, even a hobby project that is widely available is expected to work. Could it be that L wants to say "look at how many devices L is available for", never mind that state of what is available?
[Samsung Galaxy Nexus] nailyk:
IMHO this is getting out of topic too much.

L= lollipop (5), android version. As M=marshmallow(6), N=nougat(7), O=oreo (8). Different of Lineage/LAOS/LOS/LineageOS.
[Samsung Galaxy Nexus] hga89:
Got my versions mixed up a bit in earlier posts. I meant to ask why work on the L version of Nougat, i.e., L 14, when Oreo is around the corner? Will L Nougat not again be a version that does not progress beyond the beta stage?

How can you get any more than a small number of users on L if releases never go beyond beta? It would be interesting to know how the number of users of L on various devices has evolved over time.

I also found it perplexing that [MENTION=6979267]nailyk[/MENTION] stated that the maintainer do not decide which version they want to work on - could this be because L wants to say "look at how many devices L is available on"??
[Samsung Galaxy Nexus] bamtan2:
The people who make Lineage here on XDA are different than the people who make Lineage on the Lineage website. The people on XDA take the Lineage code and volunteer their time to work on it for the Lineage website people. There is no organization beyond this. If no one is here to work on our Lineage, then there is no Lineage here.

So you see, everything on this forum is because one person felt like doing it. There is no master plan. No CEO. People just come and go, donating time to the greater good, the way we donate money to guitar players on the street. ;)
[Samsung Galaxy Nexus] brandon88tube:
I would like to point out a bug that I've run into on the "lineage-13.0-20171021-nightly-maguro" build.

I'm unable to get a data connection no matter what I do in the settings. I've tried turning on/off the cellular data, turning on/off airplane mode, enabled data roaming, chose the network operator again, and reset the APN settings. After all of this and multiple reboots I still have a cellular state of "disconnected". :crying:
[Samsung Galaxy Nexus] GerardJ:
Spontaneous reboots

I have installed all the NIGHTLY's since the mentioned NIGHTLY, the latest being 13.0-20171028-NIGHTLY-maguro, but the problem with the spontaneous reboots still exists. I wonder how wide spread this problem is. Am considering to fall back to the 20171002 version, but - obviously - I do prefer to continue updating to the latest NIGHTLY.
[Samsung Galaxy Nexus] IL2:
On Paranoid Android 4.6-BETA6 reboots happen multiple times a day.
[Samsung Galaxy Nexus] hgmichna:
Random Reboots

Let me remind everyone that spontaneous reboots are a very widespread problem. Many users have them on many different phones and many different versions of Android. The reboots have more than one trigger, but they are apparently a deep-seated Android problem. Just google and you will see.

That said, it is still possible that LineageOS has its own reboot problems that make matters worse and that could be fixed. But I would not hold my breath.

There are different workarounds for different triggers. I know two and had already posted them here. But I have no universal solution.
[Samsung Galaxy Nexus] victoralexbr:
Stable (for me can change the status to Stable)

:)

after try several custom roms like slim7, slim6, unlegacy and omni (all of them with bugs or dont even boot)

LineageOS 13 is working great, with no problems with youtube app and fast with no lags or freezes.

Waiting the nougat version.

thanks guys for the great work you've been done.
[Samsung Galaxy Nexus] GerardJ:
Spontaneous reboots

Thanks for the feed back. Very much appreciated.

Still, prior to NIGHTLY 20171007, I didn't have any spontaneous reboot...
[Samsung Galaxy Nexus] hgmichna:
Random Reboots

I have had them all the time, with all LineageOS 13 versions. Sometimes the phone even auto-reboots just after booting.

The difference may be that I have a lot of apps on the phone, some of which require auto-start after boot.
[Samsung Galaxy Nexus] nailyk:
Does the 14.1 have the issue too?
[Samsung Galaxy Nexus] GerardJ:
Spontaneous reboots

Personally, I don't have experience with LineageOS 14.1. But I've had AOSP_7.1_tuna_2016_10_21 installed on my Nexus for a while. The LineageOS 14.1 is probably very close to the AOSP version. In principle, the AOSP version worked quite well; the only reason why I went for the LineageOS 13 was, that this ROM is frequently updated. The unofficial LineageOS 14.1 is also without any update sofar. Moreover, from the responses, I do understand that there is still a problem with GPS.

Once Ziyan switches his attention to LineageOS 14.1, I will most probably go for that ROM, spontaneous reboots or not...
[Samsung Galaxy Nexus] guest4711:
Yes, for me too. Especially when I synced calendars using myphone explorer...

After switching to DU in summer I had only one unwanted reboot.
[Samsung Galaxy Nexus] AMKhatri:
What build do you recommend for using as a daily driver?

https://download.lineageos.org/maguro
[Samsung Galaxy Nexus] hgmichna:
Stability of the nightlies

I recommend the latest LineageOS 13. Update from time to time, perhaps once a month, to get security and other updates.
[Samsung Galaxy Nexus] hga89:
Let me chime in and add that the latest version of L 13 for GN (on both my phones):

- Suffers from frequent random reboots. If your phone is encrypted, or require a PIN to use the SIM, the phone gets stuck at this step and is, until the additional information is entered, not useable.

- Often loses connection with my WiFi router and I have to manually reconnect.

- Sometimes on a reboot is not able to connect with the cellular network requiring another lengthy reboot.

- The OS often loses connection with the camera, a problem I thought had been fixed in an earlier release but apparently is back. To be able to use the camera requires a reboot (I did try an app that supposedly resets this connection but it did not work for me).

- At least on my two phones, I am no longer able to deposit checks by taking a photos of them since the bank app cannot focus on the check. I should add that this also does not work on my tablet running L 14.1, thus it could be a problem with the bank app but I have not been able to find anyone else complaining about this.

- The maintainer has stated that he is not fixing any bugs in the OS.

Pretty serious issues if you are planning to use your phone as a worktool and not as a toy.
[Samsung Galaxy Nexus] Bludwurst:
The latest official builds? Oh my!
[Samsung Galaxy Nexus] guest4711:
None of them. I'm satisfied with [MENTION=5010999]Voidz[/MENTION]-maguro's unofficial DU builds, see

https://androidfilehost.com/?w=files&flid=50101
[Samsung Galaxy Nexus] AMKhatri:
Cool. Thanks. I'll have a look. :good:

Any known issues that I should be aware of? I don't really care for the security updates :p

That's news to me. I'm gonna PM you so that there is no discussion of another ROM on this thread. Thanks :good:
[Samsung Galaxy Nexus] GerardJ:
Yesterday, I switched to LineageOS 14.1. Suddenly, I found a website showing LineageOS 14.1 versions for the maguro, which were frequently updated. I downloaded following file and installed it right away, together with the relevant GApps-pico version:

lineage-14.1-20171020-nailyk-maguro.zip

Sofar, it works perfectly. All functions appear to work fine. And, not a single spontaneous reboot!

Where did I find the mentioned file? Can't find the website again... (Would appreciate help, so I can make a favorite or a shortcut of it...
[Samsung Galaxy Nexus] runekock:
Is this one with CMA? Hint: look at available memory, if it is above 900MB, then CMA is in use.

CMA is great for the extra memory, but it is also the primary suspect of unstable camera, video playing, and general instability. ZeeLog has a version of LOS without CMA, and it has been recently updated.
[Samsung Galaxy Nexus] GerardJ:
LineageOS 14.1 for maguro

OK, My memory shows 673 MB in use, of a total of 0,97 GB. Average use 68%, Free 319 MB. So, presumably, this is the version with CMA.

Is the version without CMA from Zeelog that you are referring to: lineage-14.1-20171026_101908-UNOFFICIAL-tuna.zip ?

I found that one here: https://androidfilehost.com/?w=files&flid=157598&sort_by=date&sort_dir=DESC

I must say that all the LOS versions for tuna or maguro form pretty much of a labyrinth...
[Samsung Galaxy Nexus] Android-Andi:
IDK why there's always discussion about other roms. Can't we stay on topic here?