yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Android-Andi:
You can use it if you like because it has an updated interactive governor and slightly different bfq sheduler (didn't got much feedback, so it's not merged).

The bootloop issue should be solved on the official kernel.
[Samsung Galaxy Nexus] andifor:
I didn't have boot loops with the 20171126 version I used, but had stability issues. I'm happy to give the Xmas version a go :o)
[Samsung Galaxy Nexus] hga89:
Am I reading this right that the latest official L 13 from December 17 no longer randomly reboots? Have the problems with not reconnecting to WiFi and sometimes apparently not activating the phone network connection upon reboot also been resolved?
[Samsung Galaxy Nexus] Android-Andi:
No, you are reading my post wrong.

Again: Nothing besides the bootloop issue on some maguros has been fixed device side.

Rom Side Changes: December security bulletin fixes.
[Samsung Galaxy Nexus] hga89:
So the boot loop issue on /some/ maguros has been fixed and others still experience this? And, this is the latest official release of December 17, correct?
[Samsung Galaxy Nexus] Android-Andi:
Afaik every Sunday Jenkins compiles automated builds, means there's a Christmas build available
[Samsung Galaxy Nexus] hga89:
I understand that but the important questions I asked were:

- Whether my understanding is correct that some users still experience random rebooting?

- The second question was whether you were referring to the December 17 release?
[Samsung Galaxy Nexus] andifor:
Installed yesterday:

- LOS13 (20171224)

- AnyKernel (20171202)

=> No random reboots (so far), no annoying lags

This is not a thorough test, but I stick with this combination as my daily driver.

Thanks to whoever solved the random reboot problem! :o)
[Samsung Galaxy Nexus] Android-Andi:
Could be. In this case try my anykernel and tell if it makes a difference. BFQ is used by default and on most 3.0 kernel it wasn't working well enough. A solution could be to add some backports from a different kernel and use a different BFQ scheduler (that's what's added on AnyKernel)

Needed change merged on 3rd December, every build after that should be fine.
[Samsung Galaxy Nexus] Ziyan:
New build up:

- synced with the CM repos @ 03/10

- more userspace memory freed up (876mb available atm)

- fixed RIL crash after the other party ends the call (thanks to [MENTION=3390093]MWisBest[/MENTION])

To be honest, other than quickly checking if stuff works properly, I didn't test this build thoroughly, as we've mainly focused on OMAP4-AOSP, so report back if there are any new issues :)
[Samsung Galaxy Nexus] rohitchouhan07:
This is super good ..................876 Mb ram is more than awesome,even an msm device moto g has 888Mb ram.....

thanks a lot ziyan.
[Samsung Galaxy Nexus] MayuraDeSilva:
Thanks for the awesome ROM, [MENTION=2633638]Ziyan[/MENTION]!

Had the pleasure of trying this out and very pleased to say I'm impressed from the first use. Much better than other ROMs - including the Lollipop ROMs I've tried so far.

Only issue I've had was System UI crashing when I delete a tile.
[Samsung Galaxy Nexus] pluk64:
- mobile data not working at all (at least 3G was OK in previous build)

- sometimes I have problem with connecting my heart rate monitor and weight scale through Bluetooth (also in previous cm13 build). After reboot it connects successfully. Not a big issue for me.
[Samsung Galaxy Nexus] playitlouder:
Todays CM sources are broken. That's why 3g is broken.

The CM13 nightlies on the S3 don't have any 3g today, either.
[Samsung Galaxy Nexus] pino.bova:
Mobile data not working and system's app won't unistall (For example clock)
[Samsung Galaxy Nexus] E66666666:
I kept getting terrible performance and the SIM stopped getting detected after first boot.
[Samsung Galaxy Nexus] Ziyan:
That's just great. Of course they decide to break it when I decide to release a new build :mad:

EDIT: looks like they fixed it, new build on the way...

EDIT 2: new build up.
[Samsung Galaxy Nexus] pluk64:
looks same as before - no mobile data :(
[Samsung Galaxy Nexus] Zenroid:
Dirty flash over cm12 but unable to boot up for cm13 mar 11, may try to wipe the data partition later
[Samsung Galaxy Nexus] blackout23:
When I used the old build from Feburary my problem was that sometimes I had no data connection. I had to toggle on Airplane mode and then turn it off after a few seconds so that the phone reconnects. This usually fixed the problem until the connection was lost again after a few hours. Not sure why.
[Samsung Galaxy Nexus] Ziyan:
It seems to work fine for me after a clean install (I couldn't try dirty flashing). Can you double-check that your APN settings are correct?
[Samsung Galaxy Nexus] pluk64:
Yeah, I just dirty flashed. In APNs I had a message: "APN settings are not available for this user." So I tapped on "Reset to default" and it's working now! :)
[Samsung Galaxy Nexus] Oehr:
AWESOME! thanks! that fixed it for me as well. :D
[Samsung Galaxy Nexus] wyur:
[MENTION=2633638]Ziyan[/MENTION]

I just wanted to tell you that from these sources (today, March 13 2016) I was able to compile everything, including the Wireless and Ethernet USB drivers (not tested yet) without any issue of some sort. I think I'll be sticking with CM13 from now on, but I just wanted to report, in case someone else has this problem.

Original post where I reported the USB drivers compiling issues: http://xdaforums.com/showpost.php?p=65709726&postcount=3972

Some problems I have been having (using my build but with stock sources and proprietary files from your repo, feel free to ignore if you think it's not related):

- 5GHz WiFi not working (stuck at 'scanning nteworks')

- 2.4 GHz seems slower than usual (it seems I can get only 180 - 250 kB/s)

- Cannot play YouTube 720p videos at 60 frames per second, the image get stuck and I hear only audio. The image has some sort of 'focusing' effect. Videos at 720p with 30 frames per second and lower quality work, however when a video is paused I get the same focusing effect.
[Samsung Galaxy Nexus] Slendy:
Is there a function "Double tap to wake" ?
[Samsung Galaxy Nexus] 9Lukas5:
[MENTION=2633638]Ziyan[/MENTION] Don't know if anyone noticed it yet, but it seems rotation isn't working here, too.

I had that with the latest build for m7, too and did this:

http://review.cyanogenmod.org/#/c/136134/

After I found that:

http://review.cyanogenmod.org/#/c/135842/

L

Gesendet von meinem HTC One m7
[Samsung Galaxy Nexus] Vara83:
hello, same problem for me for no data connection, reset settings not works. I manually do APN settings but not works, what I must to do?
[Samsung Galaxy Nexus] 9Lukas5:
For me data connection is working fine ^^

Gesendet von meinem HTC One m7
[Samsung Galaxy Nexus] Vara83:
You do a dirty installation or hard wipe?
[Samsung Galaxy Nexus] hga89:
I need to stick with what is downloadable from the Lineage website since I do use both my maguros as working phones. I have neither time, nor inclinication, to futz around with special packages, potentially having to reinstall my software, customize the setup etc.

I will have to wait for other users to confirm that the "standard" downloadable Lineage upgrades of December 3rd and later work without random rebooting and with no new bugs introduced.
[Samsung Galaxy Nexus] Android-Andi:
A rom without bugs never existed - even stock ROMs have bugs ;)
[Samsung Galaxy Nexus] drakonianheart:
Hey people i am installing the las build but the phone stuck on "Preparing to start" "Starting apps..."

Any help here?
[Samsung Galaxy Nexus] hgmichna:
Boot problems

I have no real solution, but at least you can press the power button for 20 s to reboot and try again, so you don't have to remove the battery every time.

The power button trick has been part of LineageOS for a long time. It is not a hardware feature, so it works only when LineageOS is actually running.
[Samsung Galaxy Nexus] drakonianheart:
I will try using AnyKernel.
[Samsung Galaxy Nexus] drakonianheart:
Nothing is working.
[Samsung Galaxy Nexus] Android-Andi:
Clean flash?

What recovery you used?

What gapps?
[Samsung Galaxy Nexus] hga89:
Sure but that's not the point - due to random reboots, sometimes hangs when rebooting, usually not reconnecting to WiFi and sometimes not connecting to the cellular network, L 13 has not really been usable in real-life.
[Samsung Galaxy Nexus] drakonianheart:
Yes clean flash.

Recovery: TWRP 2.8.7

Gapps: pico ARM for 6.0

I Tryed Slim too and happended the same.

Preparing apps, then starting apps and nothing happend. If i press power for 20 second the phone freze.

I already have stock 4.1.2.
[Samsung Galaxy Nexus] Android-Andi:
Use twrp 3.x,

2.8.7 is from lollipop times and has problems on some gapps packages for 6.x an newer.
[Samsung Galaxy Nexus] drakonianheart:
using twrp 3.0 and i have same problem
[Samsung Galaxy Nexus] andifor:
Xmas build still works flawlessly! :o)

No random reboots, not hanging, lags or other problems. Well, beside the camera issue I have since 2 years...

Details:

- LOS13-20171224

- opengapps-pico-20171224

- AnyKernel-20171202

all flashed with twrp-3.2.1
[Samsung Galaxy Nexus] hga89:
Why did you install another kernel?
[Samsung Galaxy Nexus] andifor:
Due to post 1360 (https://xdaforums.com/showpost.php?p=74737557&postcount=1360)

Sounds reasonable to use some patched kernel. I don't know (read: I didn't test), whether AnyKernel has influence on stability.
[Samsung Galaxy Nexus] hga89:
OK, I am only interested in whether the L 13 updates that can be downloaded as one package will finally become stable and useable in daily use. Futzing around with other kernels I leave to hobbyists and users who do not really use their phone.
[Samsung Galaxy Nexus] bamtan2:
Unfortunately the people who make these ROMs are every software department in one person, and they do it on their free time only, so you may never get the quality level you expect from a professional for-profit project. :(
[Samsung Galaxy Nexus] andifor:
What do you know about me and how I use my phone?

You might consider buying a new phone, still supported by a manufacturer. If they fail you, you might blame them, as you see fit.

The Galaxy Nexus is more than 6 years old, Google (the manufacturer) has abandoned it since over 4 years and some great volunteers keep the OS alive and up to date (patch levels) for the last few years. Thanks to all, that helped me keeping my phone up and running! :o)
[Samsung Galaxy Nexus] Android-Andi:
I guess you don't know how community projects works. It's open source, if you feel it's unstable you can work on it too.

And yeah, blame people spending countless hours unpaid on such projects.

Why those changes aren't pushed I have on anykernel: user decide if it's an improvement or not - but only works if user test it. You should be happy user have a vote here too.

As a side note to my person: I've never learned any coding language at school, University or as education. I am working full-time in orthopedic. All I know I about Android I've learned here on XDA.
[Samsung Galaxy Nexus] hga89:
Half-finished projects have little value to users.
[Samsung Galaxy Nexus] guest4711:
[OT]

But people buy the products created in these unfinished projects like dieselmotor, microsoft windows or ICE-4, to name just a few...[/OT]
[Samsung Galaxy Nexus] andifor:
You're absolutely right. Feel free to use some other product.
[Samsung Galaxy Nexus] gld59:
How about you think this through. You're implying that the developers here, who do this stuff not for money but because they want to, and who provide you with an alternative which otherwise would not exist, are letting you down by not working hard enough. Really? :rolleyes:

Sure, I wish LineageOS was more stable on my GNex, but it's still a good enough product that I've delayed replacing the phone. I've bought a power bank in the hope of preventing a lot of rebooting next time the camera gets a solid workout, but if it doesn't have that preventative effect I'll just work within the limits I have to. If that sort of approach doesn't work for you, well, what andifor said.
[Samsung Galaxy Nexus] magur0:
BIG UP to all developers (@Android-Andi and all others!) keeping our nexus fresh! Let 2018 a

great year for all of us

! (excluding haters like [MENTION=3443260]hga89[/MENTION])
[Samsung Galaxy Nexus] hgmichna:
Quality

I don't think he's a hater. He is not entirely wrong. There are bugs and shortcomings, and these reduce the value. They hurt me too. It cannot be wrong to point that out.

You are, of course, also perfectly right. The programmers are under no obligation, and they don't have unlimited time to work for free.

I think it is a pity that there seems to be no business model in which everybody could pay a moderate price for the latest and greatest LineageOS version, so some programmers could make a living out of it or at least get some money for their time. I would gladly pay.

Donations don't cut it, because only few users donate and everybody else rides free.

But anyway, I'm glad that the Galaxy Nexus works as well as it does. One can always wish for more, but it is good enough already for many purposes.
[Samsung Galaxy Nexus] hga89:
There was agreement about a month or so ago that L 13 was not suitable for everyday use. Has this changed?

IOW:

- The phone no longer randomly reboots?

- When it reboots, it no longer sometimes gets stuck on Starting Apps requiring another reboot?

- When it reboots, it no longer sometimes is unable to connect to the mobile network requiring another reboot?

- The camera no longer fails to work requiring another reboot?

When the phone is rebooted, it may end up in another of the above scenarios requiring another reboot, and possibly yet another...
[Samsung Galaxy Nexus] guest4711:
[OT]

I don't know of any agreement to develop a bugfix version (e.g. you pay something to some developers and they give you another version}. But it would be a nice szenario.[/OT]
[Samsung Galaxy Nexus] andifor:
happy new year to hga89, too.

I don't care, if he has some other opinion. Everybody is entitled to an own opinion. I just hope, they are not stuck in a mood, where they are fixed on something and can't step back anymore and see the importance of something.

Sometimes, I'm stuck in some detail and I'm too fixated. If I step back, I see the importance, that it is a detail. I look left and right... all the other things, ways around. I just take some other path that makes me happy. (Sorry, I'm not native english, so my explanation might seem clumsy) :o)

---------- Post added at 05:03 PM ---------- Previous post was at 04:55 PM ----------

As I mentioned some post ago, I didn't have any random reboot after flashing AnyKernel. But I think you pointed out, you don't want to flash AnyKernel, even though this would be the solution (I think).

I still have issues with the camera though, since several month / years IIRC. But this doesn't bother me. As I only need it every other week or less. So I can go though a reset-power-off-power-on cycle. This might be different for you.

Again, my proposal: look for some other phone. Really. Some other phone might cheer you up. Fewer reboots, working camera, no additional flashing. No lurking on xda-developers to find out if something improved.
[Samsung Galaxy Nexus] hgmichna:
Auto-reboot

I have all of those too, except that I use Open Camera, and thought that the initial reboots happen because I have a lot of apps installed.

When I power up the phone, it either works fine from the start or it auto-reboots once or occasionally twice, or it requires a manual reboot because it does not recognize the SIM card. After these initial reboots it seems to be mostly stable and usable, though I admit that I use it only as a spare next to my primary phone.

I have always considered it a miracle that it is possible at all to run Android 7.1 on this old smartphone, so I have not complained much. But, of course, I would appreciate any improvement.
[Samsung Galaxy Nexus] andifor:
Well... did you try AnyKernel-2017-12-02-19-27-tuna? Any random reboot while using my phone is not acceptable for me. With AnyKernel, I didn't have any random reboot.

OK... the camera ;o) But the camera does not reboot my phone, it just doesn't work and I have to reboot my phone manually. So this does not count a random reboot.
[Samsung Galaxy Nexus] hgmichna:
AnyKernel

No, haven't tried AnyKernel. Whenever I find the time …

Thanks for the hint!
[Samsung Galaxy Nexus] bamtan2:
I think CMA implementation is still buggy and that is why the camera goes bad. Ziyan knows about this, but he is a busy professional developer now, so all we can do is cross our fingers :)
[Samsung Galaxy Nexus] hga89:
OK, maybe I should try AnyKernel since the reboots are unacceptable, a sometimes-not-working camera I can live with.

Let me make sure I understand how to do this before I try this on the first of my two phones:

- I am currently on L 13 from 2017-10-14, can I stay on this ROM?

- My phones are encrypted. Will installing AnyKernel affect the ability of TWRP to decrypt the contents?

- Do I download AnyKernel and install with TWRP, reboot and then ready to go?

- I assume this will not require a reinstallation of my apps at all?

- Will this affect the ability to download and install future releases of L13?

- Have you found any bugs that I did not mention?

Thanks!

---------- Post added at 09:14 PM ---------- Previous post was at 09:13 PM ----------

Not sure why you cut my sentence there since that is not what I said?
[Samsung Galaxy Nexus] Android-Andi:
yes

nothing changed in that direction

yes, it's only replacing the zImage and modules of your current boot.img

nothing changes here

No, you can always update like before. After update anykernel is gone.

And note: you only need to dirty flash your current Rom again to get rid of the anykernel.
[Samsung Galaxy Nexus] lantsem:
My GN began to hard freeze when charging with builds after November. It happens not on every charge and to power-off I need to pull out battery or long-press power button, so I think that no logs are usefull in my case. Also it can be some new hardware issue, not a kernel. But I tryed AnyKernel for one week and didn't got such freeze. After next update to fresh build I got such freeze after several days of use. I flashed AnyKernel back for now and I'm planning to use it at least a month, to get a more accurate information.
[Samsung Galaxy Nexus] hga89:
I have seen the same using the build from 20171014. Since I have two phones in daily use, I don't think it is a hardware issue.
[Samsung Galaxy Nexus] Android-Andi:
Like said a few times now: if you guys feel the AnyKernel is more stable we can submit the changes. Added changes have been used in the past on the old kernel but thought to be unneeded (not always backports really improve things) - you guys decide as I am out of XDA for a while and not really using my tuna. Leave some feedback in AnyKernel thread, I am checking there from time to time.
[Samsung Galaxy Nexus] osm0sis:
Since they report it starting in November and that's when the kernel changed, and I think your AnyKernel add-on has been reported by several as resolving the issues, I'd say definitely submit the changes. :)
[Samsung Galaxy Nexus] hga89:
Thank you for the information. I did install AnyKernel from 20171202 on one of the phones yesterday, sadly this phone randomly rebooted this morning whereas the other one still running the kernel from 20171014 has not yet rebooted during this entire time (random reboots are just that, random).

Thus, it seems AnyKernel has not fixed the random reboot problem...
[Samsung Galaxy Nexus] osm0sis:
Can you switch the I/O scheduler from bfq to cfq and see if that resolves it? I seem to recall it was pretty difficult getting the backported bfq to be stable on this device.
[Samsung Galaxy Nexus] hga89:
How do I do that? If there is a kernel I can install as easily as AnyKernel - and get rid of should I need to - I am willing to try it.

Since both phones are in daily use I do not want to jeopardize the ROM installation and app installation/configuration itself.
[Samsung Galaxy Nexus] osm0sis:
Do you want to help solve the problem you've been complaining about? If so, maybe you should be more open to helping test..

From Terminal Emulator:

su -c "cat /sys/block/mmcblk0/queue/scheduler"

will show you what the current scheduler is..

su -c "echo cfq > /sys/block/mmcblk0/queue/scheduler"

will change it to cfq.

It doesn't jeopardize anything, in fact it resets on every reboot.
[Samsung Galaxy Nexus] guest4711:
You may use a tool like Kernel Adiutor (Manage kernel parameters) - https://f-droid.org/app/com.nhellfire.kerneladiutor - for switching until next change or reboot or to apply it at every reboot if you don't like to mess with shell scripts or unix commands in terminal emulator.
[Samsung Galaxy Nexus] hga89:
Tried it on both phones, one running AnyKernel 20171202, one running the kernel from L13 20171014, both running bfq. Both phones locked up solid after executing the echo command above and had to be rebooted...
[Samsung Galaxy Nexus] osm0sis:
Yup, because bfq is buggy as ****. ;)
[Samsung Galaxy Nexus] Ziyan:
Unfortunately, this is a limitation of kernel 3.0 and bfq (switching from bfq to cfq after boot locks up the kernel). You need to edit build.prop (I think Kernel Adiutor has an interface for it), where you'll find sys.io.scheduler=bfq. Simply set it to cfq and reboot, it will work fine. :)
[Samsung Galaxy Nexus] guest4711:
Yes, KA includes an editor for build.prop.
[Samsung Galaxy Nexus] hga89:
Downloaded it and saw that the misspelling of auditor was not a typo...
[Samsung Galaxy Nexus] hga89:
OK, did that on the phone with AnyKernel - I'll report back tomorrow.
[Samsung Galaxy Nexus] guest4711:
[OT]

No, it's Latin. See e.g.

https://de.m.wikipedia.org/wiki/Adiutor[/OT]
[Samsung Galaxy Nexus] Adanedhil:
Yes, I have the same issues on the latest weekly build. Any ideas how to fix them?
[Samsung Galaxy Nexus] hga89:
Thank you, I (ass)u(me)d it was supposed to be auditor...
[Samsung Galaxy Nexus] hga89:
Sadly it did not help, still suffering from random reboots on the phone running AnyKernel and it is not possible to say whether they occur with the same frequency. I actually also changed the scheduler to cfq on the phone running the regular L 13 kernel and both phones continued to suffer from reboots...

Anything else I can try to assist in troubleshooting this?
[Samsung Galaxy Nexus] Ziyan:
Did you look at last_kmsg yet? Is anything in it that tells the reason?
[Samsung Galaxy Nexus] hga89:
Tried to open it in DroidEdit as root but not able to, nor with any other editor I have on the phone. I assume it is locked for writing but I ought to still be able to open it in read-only mode, or?
[Samsung Galaxy Nexus] bamtan2:
Search Google play store for "syslog", this is the logging tool I use. It lets you create a zip with many device logs in one step. It also lets you share to google drive, so you can make a folder for Android logs and just put them all there. It lets you name the file and write a short note file to be included in the zip. It also has a feature to (attempt to) anonymize log data. Give it a try!
[Samsung Galaxy Nexus] hga89:
OK, will do that. In the meantime I did 'cat /proc/last_kmsg > /sdcard/kmsg' in a root terminal window. The file is over 14400 lines long and ends with 'no errors detected' although the last bunch of lines are killing various processes due to low memory.

Is anyone interested in this file?
[Samsung Galaxy Nexus] hga89:
Do not all ROMs for the GN use the same kernel? IOW, is there any point in trying other kernels with L13?