yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] hga89:
I made the mistake of installing the latest L13 "nightly" for maguro, dated January 14th and it was a nightmare. Not only does it reboot randomly, like earlier versions, it also very, very frequently locks up solid requiring a reboot...

I would therefore like to go back to the October 14th build that I had previously installed but now I cannot find it on the 'net. The official L13 maguro download page only has the latest four builds with no information as to how or where find older builds. Does anyone know?

Just for fun, I looked at the other ROMs for the GN and the impression I get is that there is really no reason to install any of them, software missing, unstable etc. etc. However, before I declare any time spent on this device a lost cause I thought I would reinstall the October 14th build to regain some usability...
[Samsung Galaxy Nexus] osm0sis:
I found 1112 to be the last stable one, since it is the build directly preceding the kernel change. I can upload it for you if you'd like to try it.
[Samsung Galaxy Nexus] bamtan2:
Unfortunately that's a reality of software development. Nightly builds haven't been tested! You're the first tester! :) For most of my time with any device I'm trying to use stable, proven, months-old or years-old builds. I install new builds to help the developers test when they need help.

I don't know where to find the exact build you're looking for. Ideally the developers would notice which builds are stable and good, and call them release builds, and archive them permanently. But volunteer developers have a lot to do, so they might miss opportunities to do that.

Andi has some older builds here which I found on his website. The stability of these is unknown to me. https://androidfilehost.com/?w=files&flid=158480

Please note that dirty flashing sometimes messes stuff up. I've thought I was doing it right before and I still made some mistakes. My best results are always from nuking the device and starting from scratch.

You can also give zeelog's LOS 14 a try if you're wiping anyway! http://zeelogkang.blogspot.com/2017/05/lineageos-141-unofficial-712-gnex-tuna.html
[Samsung Galaxy Nexus] guest4711:
I use [MENTION=5010999]Voidz[/MENTION]-maguro's dirty unicorn for tuna since more than seven months. It's rock solid for me, not based on LOS, has it's own kernel, but runs well with [MENTION=5153662]Android-Andi[/MENTION]'s unikernel too.

The maintainer does not post on XDA anymore because his english is not so smooth, he said...

You'll find his ROMs on AFH: https://androidfilehost.com/?w=files&flid=50101
[Samsung Galaxy Nexus] hga89:
I'll take a look at it but are you saying that it does not suffer from random reboots at all? If so, can not his kernel be used together with L 13? Have you found any bugs?

In the meantime, without having to do a clean flash of a ROM, is there anywhere I can find official L 13 ROMs older than the last four or five on the official download site? I need to go back a few versions so I can avoid a clean flash...
[Samsung Galaxy Nexus] Android-Andi:
Wait for next build, I'll push some changes tomorrow evening to lineage kernel (if I find a few min after work).
[Samsung Galaxy Nexus] hga89:
By the way, they all seem to be for tuna whereas I have maguro?
[Samsung Galaxy Nexus] Android-Andi:
Tuna builds are unified: works on maguro, toro and toroplus at same time.
[Samsung Galaxy Nexus] guest4711:
I have a maguro, too. Tuna is the name for the unfied build for maguro, toro and toro+ (which all are tunas).

I don't think the problems are kernel related as DU run's with [MENTION=5153662]Android-Andi[/MENTION]'s very well while LOS and CM based builds run out of memory and reboot - I got reboots on them when synchronizing 400 contacts via MyPhoneExplorer to a local pc. With DU (Nougat) I don't have this problem - even with anykernel.

Now my husband is mainly using this phone. I did not hear of severe problems.
[Samsung Galaxy Nexus] hga89:
Can anyone else speak to the reliability and performance of DU, i.e. Dirty Unicorn?
[Samsung Galaxy Nexus] Android-Andi:
https://review.lineageos.org/#/q/status:merged+project:LineageOS/android_kernel_ti_omap4

We are now back inline with the old tuna kernel in biggest parts.

(Only 120 commits for it, lol)
[Samsung Galaxy Nexus] bamtan2:
Ouch! Thanks for the work. This means we all need to start testing it! :silly::cool:
[Samsung Galaxy Nexus] Android-Andi:
Yes and no. It's the changes from AnyKernel, as suggested.
[Samsung Galaxy Nexus] hga89:
Has anyone had time to try this release yet?

---------- Post added at 01:24 PM ---------- Previous post was at 01:19 PM ----------

Which release of DU are you running? This seems to be the latest one: du_tuna-v11.7.2-20171012-1954-UNOFFICIAL.zip.

---------- Post added at 01:29 PM ---------- Previous post was at 01:24 PM ----------

I just downloaded lineage-13.0-20171118-1246-UNOFFICIAL-maguro.zip which looks like the latest version, however, the MD5 checksum does not match...
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=3443260]hga89[/MENTION] I've not compiled a build. New official build get compiled on Jenkins automatically and will be available over OTA.
[Samsung Galaxy Nexus] hga89:
OK, OTA over-the-air? How do I find your latest version since it is not on the official lineage site?
[Samsung Galaxy Nexus] Android-Andi:
It is: https://jenkins.lineageos.org/job/android/9403/

https://mirrorbits.lineageos.org/fu...neage-13.0-20180121-nightly-maguro-signed.zip

https://jenkins.lineageos.org/job/android/9407/

https://mirrorbits.lineageos.org/full/toro/20180121/lineage-13.0-20180121-nightly-toro-signed.zip

https://jenkins.lineageos.org/job/android/9408/

https://mirrorbits.lineageos.org/fu...age-13.0-20180121-nightly-toroplus-signed.zip

---------- Post added at 07:53 PM ---------- Previous post was at 07:48 PM ----------

If there's still freezes or reboots it's unlikely that it's related to the new kernel. The new kernel is almost inline with the old kernel and tuna specific workarounds are added since the beginning.
[Samsung Galaxy Nexus] hga89:
In installed DU, rebooted and now it fails to decrypt my partition and wants me to do a factory reset...

By the way, it seems the phones with the latest official version of L13, as well as the version from 20171224, are running very hot - is the kernel sped up for some reason and the phones are overheating resulting in random lockups (not to mention reboots)??
[Samsung Galaxy Nexus] Android-Andi:
I'd suggest not mixing different roms here. If there's issues with clean flash on latest lineage13 we can discuss here. In the past GPU OC was allowed which now isn't. CPU speed hasn't changed.
[Samsung Galaxy Nexus] hga89:
I downloaded your latest drop and have installed it. However, zip signature verification does not work (just like with all the official L13 releases) - why is this feature not used?
[Samsung Galaxy Nexus] Android-Andi:
Not sure if TWRP supports sha256, but here it is https://mirrorbits.lineageos.org/fu...3.0-20180121-nightly-maguro-signed.zip?sha256

You'll need to have both, zip and the file to cross check (md5sum should work)

Edit:

Zip verification is a feature of TWRP, not a feature of custom ROMs ;)

TWRP is a own small system.
[Samsung Galaxy Nexus] bamtan2:
That was the first thing I noticed when I got to XDA. So it's normal. I've never seen that feature used LOL :)
[Samsung Galaxy Nexus] guest4711:
Yes, but the previous one (one week ago). Had neither the time nor the chance to update... (and my husband reported no problems which needed any updates).
[Samsung Galaxy Nexus] hga89:
Thank you for explaining. I will let you know tomorrow how the latest drop works but so far, so good... :)
[Samsung Galaxy Nexus] hga89:
I have now been running this latest drop on both my phones, one of which has been heavily exercised. On this phone, I have had two reboots, otherwise it has been very well behaved.

Thank you, a tremendous improvement!!! Could you elaborate a bit more on what has been changed? Perhaps we can even eliminate the last reason(s) for rebooting?

I would suggest the drops before this latest one be removed since they are unusable.
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=3443260]hga89[/MENTION] the issue from the past might be related to BFQ Scheduler which is used by default on Lineage13. BFQ for 3.0 kernel is known to cause trouble but in previous test it seemed to work good on the new kernel base and I've decided to use it instead a version not compatible for 3.0 kernel.

We are now using BFQ from 3.3 kernel - but therefore we needed a lot of backports which are merged now too.

CFQ was updated too.
[Samsung Galaxy Nexus] lantsem:
Already 2 weeks I no longer have hard freeze when charging. So it seemed to be really necessary.
[Samsung Galaxy Nexus] gld59:
I'm using the 20180121 build of LineageOS, so it's only half a week for me, but I can make a similar report - so far I've had no hard freeze on charging, and no unexpected reboots at all. I haven't had a chance to thrash the camera yet, but it's certainly looking like a "milestone" build. :)
[Samsung Galaxy Nexus] hga89:
Two weeks?? The latest drop was released four days ago, Jan 21, and the one prior to that was certainly not useable.
[Samsung Galaxy Nexus] lantsem:
This changes were in AnyKernel before that.
[Samsung Galaxy Nexus] hga89:
Really? That kernel kept crashing left and right for me when used with the L13 drops...

On another note, there are still a small number of random reboots even when using the drop from Jan 21. Is there any information we can collect to assist the developers in fixing these as well?
[Samsung Galaxy Nexus] bamtan2:
Try running this after it reboots: https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=en

Write into the text box some detail about what you were doing when it crashed. Then share the file to Google Drive, and create a folder for it. Then copy the share link to that folder from Google Drive. Then give that link to Andi to look at :)
[Samsung Galaxy Nexus] hga89:
Will do.
[Samsung Galaxy Nexus] Android-Andi:
New builds are up. https://androidfilehost.com/?w=files&flid=158480&sort_by=date&sort_dir=DESC

Switched to default libion, thx to [MENTION=2633638]Ziyan[/MENTION] and [MENTION=4473900]amaces[/MENTION] !

Note: don't flash any custom kernel on this build (also AnyKernel isn't compatible ATM)!

Flashing from my build to official or from offical lineage to my build requires a clean flash!
[Samsung Galaxy Nexus] hga89:
[MENTION=5153662]Android-Andi[/MENTION]

Even with the drop from January 21st, both my GNs randomly reboot albeit much less frequently than with earlier drops. On both phones, one very lightly used right now, it happens a couple of times per day, even when the phone is /not/ used.

I have three recent syslogs from the lightly-used phone but am not getting an account on Google Drive to upload them. Which free, and not requiring registration, service can be used?
[Samsung Galaxy Nexus] Android-Andi:
You can attach logs here.
[Samsung Galaxy Nexus] hga89:
Yes but zip files can only be up to 20 Mb in size. Do you need any other files beside last_kmsg?
[Samsung Galaxy Nexus] Android-Andi:
last_kmsg is fine, we'll let you know if we need other logs too after checking the log(s) you send to us
[Samsung Galaxy Nexus] hga89:
OK, here are three last_kmsg logs and I have the matching files saved as well.

Thank you for looking at them.
[Samsung Galaxy Nexus] madspeed:
been a way for a while, does this rom bypass carrier restrictions for usb tethering?
[Samsung Galaxy Nexus] kb8no:
Yes. All custom ROMs.
[Samsung Galaxy Nexus] madspeed:
Thank you, thought so but like I said it's been a while since I tinkered with android
[Samsung Galaxy Nexus] hga89:
There are some other long-standing problems with L13, including with the drop from Jan 21:

- Sometimes the boot process sometimes hangs at "starting apps" and never proceeds. A reboot is required.

- Sometimes the boot process never finishes and the green arc and animated circles just continue "forever". A reboot is required.

- Occasionally Trebuchet?? does not launch and you get a black display. The only solution is a reboot.

Are these known problems? I saw them even with the Oct drop.
[Samsung Galaxy Nexus] andifor:
I see them as well, but only if I reboot while charging. If I don't charge during a reboot, i don't have issues. Might be coincidence?
[Samsung Galaxy Nexus] hga89:
Let me see if that is true for me as well, could be.
[Samsung Galaxy Nexus] hga89:
I did some testing after random reboots etc. but for me they occur even when not charging.
[Samsung Galaxy Nexus] andifor:
Now I'm confused. In your reply, you talk about "reboots and charging", in the original message, you where talking about "hanging boot process".

My observation was about "hanging boot process and charging", not "reboots and charging".

Again: I installed the recent LOS (20180204) w/o AnyKernel and I have no issue at all.
[Samsung Galaxy Nexus] hga89:
I was referring to the same thing as you.
[Samsung Galaxy Nexus] hga89:
After several weeks of testing, I am sorry to say that the L13 drop of January 21 that I initially was enthusiastic about suffers from the very same bugs as the October drop I used to run:

- Random reboots.

- Sometimes getting stuck at "starting apps".

- Sometimes not booting Trebuchet completely resulting in a black screen or just the background wallpaper requiring a reboot.

- Sometimes not waking up when pressing the volume button requiring a reboot.

- Sometimes not connecting to the cellular network when booting requiring a reboot.

- Usually not reconnecting to the WiFi network when temporarily out of coverage area.

- Occasional hard lockups when running apps requiring a reboot.

- Often not connecting to the camera.

This is identical on two different GN units and the frequency of occurrence is about the similar with the January drop as the October drop.

Does anyone - using their phone to a significant extent - have a better experience with later drops of L13?
[Samsung Galaxy Nexus] bamtan2:
You found a lot of problems! I wish I could find the no-CMA build of anykernel that andi made so you could try that in case it might help. In lieu of that you could wipe everything and try Zeelog's unofficial LOS14, because it has a bunch of random changes, and you'd find if any of those changes helped.
[Samsung Galaxy Nexus] osm0sis:
Zeelogs is also non-CMA, so that'd be a start for him.
[Samsung Galaxy Nexus] gld59:
Sorry, my usage is usually very basic, despite this now being my only phone. I had hoped that 20180121 would be stable for me even when using the camera, but I discovered six days ago that wasn't the case - taking 80 photos at a festival caused lots of locking up and overheating (and pulling out the battery to stop it), though it settled down after a while. (The problems occured earlier on this time, whereas two and a half months ago using 20171112 it happened later in the day as the battery was running low.)

Because I rarely use the phone for anything other than calls & text, I can't really pick whether problems might be due to memory management or anything else - and because it's my only phone, I'm even more reluctant than you to debug things.
[Samsung Galaxy Nexus] rahimali:
Here and the build prior to that is here
[Samsung Galaxy Nexus] Android-Andi:
Could be Sundays nightly will be the last official Update.

If people are still interested in Lineage13 I can continue building unofficial builds from time to time after that - you'll only need to clean flash from official to unofficial build or someone creates a flashable migration zip (https://github.com/LineageOS/scripts/tree/master/key-migration - not sure if it works on Marshmallow)
[Samsung Galaxy Nexus] Bludwurst:
Why is that, if I may ask? Because of all the issues found? (I'm curious).
[Samsung Galaxy Nexus] Android-Andi:
There's not many devices left getting LineageOS 13, all 13.0 devices will be dropped as development stopped long time ago for 13.0 already.
[Samsung Galaxy Nexus] Bludwurst:
Ah. Makes sense.

No chance for official LOS14 builds, I presume?
[Samsung Galaxy Nexus] Android-Andi:
14.1 won't be supported forever too and I've Omni and Slim Nougat ROMs already, and don't forget UA which is our main project. There's some other reasons not needed to be discussed.

Zeelog is doing unofficial 14.1 builds already, people can use it if they like and he's always welcome to contribute.

And to remind: official and unofficial are tags only, they don't say anything about stability ;)

Back to Lineage13:

Our next big step is the default libion, once that's done I can provide a no CMA kernel again for people to check if it runs more stable - if it does we need to check further on CMA kernel builds to fix it.
[Samsung Galaxy Nexus] bamtan2:
LOS14 is already working unofficially, so someone just needs to volunteer to maintain it officially for the LOS project! I emailed zeelog to see if he'd help, but no response. And Andi is busy like he said. Time will tell!
[Samsung Galaxy Nexus] hga89:
I need official builds so I do not have to do a clean flash. Both my phones are in heavy use and do not have time for clean flashes, reinstalls of apps, configuration anew etc.

By the way, the Feb 4 drop suffers from the same frequent random reboots. I really cannot say I see any difference between the Jan and Feb drops compared to the Oct drop of last year. Right now, one of my phones locked up with a black screen from which I cannot awaken it. Reboot time...

Anyone not having any problems most likely: (1) is not using their phone very much, or (2) does not use encryption. If you don't use encryption any reboots might very well be silent since you will not be aware of them. When the data partition is encrypted you get to stare at the screen asking for the password until it then reboots.
[Samsung Galaxy Nexus] Android-Andi:
Like said already, official support ends soon (maybe after next nightly already) and no one can change that. In that case you should use your old build you found stable from last year.

It might also happen all official builds are removed public mid March because official builds get deleted automatically after 4 weeks. Jfyi: It's not me who's deciding that.
[Samsung Galaxy Nexus] hga89:
I don't think I ever had a stable build of L13 for GN, I believe I installed it around July 1 of last year and as far as I can remember it has always had a lot of problems.
[Samsung Galaxy Nexus] osm0sis:
Carbon ROM KitKat was nice and stable. Last ROM I used on my GN as a daily driver. Maybe [MENTION=1048318]zzpianoman[/MENTION] or someone still has an updated KitKat ROM you could use?
[Samsung Galaxy Nexus] rahimali:
The most updated KitKat ROMs available right now are Omni and Unlegacy Android.

Personally, I've settled on Dreams LP. Nice, smooth and stable!
[Samsung Galaxy Nexus] hga89:
If so, why can't L13 also be stable? I installed it in July of last year based on reviewing the posts in this thread and /importantly/ the very first page of this thread that suggests that the only bug is "speaker sounds"...
[Samsung Galaxy Nexus] bamtan2:
Well for one thing consider the amount of time and work and testing put in. There were probably more people here working on KK when it was popular! Unfortunately the "why" doesn't help the situation, because you need bodies instead ;)
[Samsung Galaxy Nexus] osm0sis:
Also CMA, judging from zeelog's comments on the matter, hence the suggestion you check out a non-CMA Marshmallow ROM.

So, you have your options, try non-CMA KitKat or try non-CMA Marshmallow.
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=4544860]osm0sis[/MENTION] he said he doesn't have time for a clean flash, also he wasn't able to test the AnyKernel.

Let's get back on topic here :)
[Samsung Galaxy Nexus] hga89:
I was not comparing with KK but with the other MM ROMs that supposedly are stable.
[Samsung Galaxy Nexus] bamtan2:
Software developer are not the best at writing documentation :P The ROMs aren't necessarily stable :P
[Samsung Galaxy Nexus] Android-Andi:
Uploaded some builds with the default libion and February security bulletin patches (those aren't in the weekly from today):

https://androidfilehost.com/?w=files&flid=158480&sort_by=date&sort_dir=DESC

Don't flash any custom kernel on it - it'll break camera and domx!
[Samsung Galaxy Nexus] hga89:
Oh, the other ROMs just mentioned, Omni and Unlegacy Android, are not stable either?
[Samsung Galaxy Nexus] Android-Andi:
Can't we stay on topic here?
[Samsung Galaxy Nexus] Android-Andi:
Fyi

https://www.androidpolice.com/2018/02/13/lineageos-13-based-android-marshmallow-now-discontinued/

https://github.com/LineageOS/hudson/commit/5ea1919c656de5d0c27ed00c1466b1e9b25e9141

Maybe we are able to get one last official build with the February security bulletin, but can't say for sure.

If everything goes bad: in mid March there's no build official available at lineageos for dropped devices - I'll grab them in case we need to mirror them somewhere else.
[Samsung Galaxy Nexus] gld59:
As long as whoever is responsible for that realises there were two in January, and doesn't leave out whatever was in 2018-01-05. :laugh:
[Samsung Galaxy Nexus] bamtan2:
The good news is that both LOS13 an LOS14 builds have worked equally well for me. I actually can't tell them apart :D :eek:
[Samsung Galaxy Nexus] Android-Andi:
Like mentioned: if there's anyone who likes to have unofficial updates , I can do.

But looking at the DL counter of some of the Roms I provide for tuna user it seems like I can save some space and a lot of time while removing tuna support from those less used ROMs.
[Samsung Galaxy Nexus] osm0sis:
Are the graphics in the Recents fixed on LOS14?
[Samsung Galaxy Nexus] bamtan2:
NOPE! You found one thing! :laugh: I zone them out I guess!
[Samsung Galaxy Nexus] osm0sis:
I wonder if the Android Go optimizations would fix that.. this is an old device after all.
[Samsung Galaxy Nexus] mirhl:
Android go switches are just to save memory.

I guess like maybe some of that may touch recent view, even potentially avoiding the garbled stuff.. But whatever graphical stuff that breaks it, is not going to be solved.
[Samsung Galaxy Nexus] osm0sis:
It flattens the Recents menu to make it easier to display. See here: https://www.xda-developers.com/android-oreo-android-go-low-ram-patcher/

Sounds like exactly the issue. Obviously we'd need Oreo to get the full benefit, but yeah. ;)
[Samsung Galaxy Nexus] bamtan2:
It will be good when someone assembles a list of every variable that changes in Android Go. Because we wouldn't want to apply ALL of them. Removing multiwindow for example would be self-defeating. The purpose of saving memory on useless things like log file sizes would be to empower useful features like multiwindow. :P Multiwindow works well on Galaxy Nexus, by the way! You can totally look something up with Chrome while you're watching a video in Youtube! It's not fast and the video might break because of CMA or whatever, but it works! ;)
[Samsung Galaxy Nexus] iYappi:
Can I flash it over "official" builds? Or should I perform a full wipe?
[Samsung Galaxy Nexus] Android-Andi:
Full wipe or use the migration files mentioned earlier.
[Samsung Galaxy Nexus] osm0sis:
Ooh yup, https://www.xda-developers.com/lineageos-15-android-oreo-go-edition-android-one/

Maybe Lineage doesn't need to die on the GN, maybe it just needs to skip 14 and switch to Go. ;)
[Samsung Galaxy Nexus] mirhl:
We already have?

And yes, removing multi-window is among what ro.config.low_ram does iirc (for a purpose).

Anyway, again, that isn't going to solve any underlying bug on the side of the graphics driver.
[Samsung Galaxy Nexus] hga89:
Isn't fixing the major existing bugs that I and other users have reported /much/ more important than playing around with "improvements"?

I have seen /no/ improvement in stability etc. since October and in fact, several of the drops released in December should /never/ even have been released, sadly, they were not either tagged as unusable so users would know to avoid them.