Two hours ago I installed the new nightly (20171114) and flashed the boot image. It went smooth altogether and no new reboots until now. The security date is 5. October 2017 still.
1 Like
Yes, the security update was not done in lineage yet.
Chris
1 Like
You mean LOS is still vulnerable to KRACK?
2 Likes
Ah, so patch level isn’t descriptive.
i feel good (20 characters)
Why not opening a new topic for CVE questions? This is about random reboots.
Chris
4 Likes
Thanks! This is a nice and clean one to analyze, great! 
and this is with the boot.img I gave you, correct? You reflashed boot after the upgrade?
Chris
Yeah, sigh. Seems this doesn’t fix it then
Chris
1 Like
As far as I know, until now only @StevenHachel reported one reboot with your latest build, and that crash - again - seems to be related to the Apple router in his office. As long as nobody else will post another unrelated reboot, I believe that your intensive effort to fix the WiFi issue of @StevenHachel might have fixed another problem, possibly some memory corruption, and your hard work has been worth while so far.
Indeed, thank you very, very much for your commitment, it is very appreciated! 
Please, keep it up!
2 Likes
Exactly, the restart took place in the office with the Apple router.
Steven
1 Like
If you can imagine memory issues, it might be worth considering doing a memory test. Seems like there is a port of memtester for Android (needs self-compiling), maybe this could be worth a try?:
2 Likes
@chrmhoffmann, I’ve installed yesterday’s LOS build (together with your boot_rollback.img) today in the morning. Haven’t seen a reboot since (but to be honest, I haven’t found the time to use the phone very much today). But no reboot so far is good news imho. So, thanks for the image, I’ll keep you updated
2 Likes
Still without random reboots today! Not even a single one, all day long.
So, 
from my side
Thanks, @chrmhoffmann!
2 Likes
For me it is also very stable. Unless I use my (Apple) WLAN on work, it crashes at some point.
With your bootimage the Bluetooth does not work anymore, right?
2 Likes
Correct Bluetooth is broken with your special boot image as I need to revert stuff on the device tree.
Chris
2 Likes
So, unfortunately, as there have been reports of random reboots, I decided to roll-back kernel. SIGH
Big breath…
Kernel is now still
- CAF merged rb1.15 also for prima (wifi)
- alarm timers remerged
- seccomp enabled
- f2fs capable
- latest fairphone kernel merged
What is gone: linux stable merge (kernel reports again 3.4.0), linux common merges.
I think I have to go through all CVEs again to see what is not fixed 
This hopefully will reduce device reboots.
Chris
7 Likes