🇬🇧 🇩🇪 Random reboots with (official) Lineage OS?

I can give you more details about the router on Monday. :grin:

1 Like

Does it still crash with newest boot.img?

I also have router with 2.4 and 5 GhZ and that doesn’t seem to cause any issue.


1 Like

IPv4 or IPv6?
DHCP or static?

I had a reboot as well but not since the latest firmware update. Applied a piece of paper on the battery, maybe that fixes it.

1 Like

I will report to you on Monday. had a reboot on Friday with the new image as soon as I am connected to the apple router.

1 Like

@chrmhoffmann Shouldn’t we just open a bug report for the random reboots on the official LineageOS bugtracker to collect logs and discuss the proceeding?

1 Like

That would not help. There’s only me working on FP2.


I know you are the only maintainer of the FP2. I proposed it for having a central place to collect the logs instead of having them spread around in the forum. (If you count the logs from snevas’ releases) I mean the bug tracker is intended to serve for such kind of purposes.
On the other hand I don’t want to force you to use it.


I know your inquiry is not addressed to me, but if you want to know my opinion:

For now it seems that the bug reports do not provide (enough) details to file this bug (router model, protocol, etc.). I have been speculating if this could be a WLAN handshake issue, but I do not have a proof either.

Lots of different bugs causing reboots have been reported in the tracker, without any specific details. Usually these are the kind of bugs which cannot be reproduced, although of course there are exceptions, too…

My suggestion is: Let us wait until @StevenHachel provides some useful information, then maybe @chrmhoffmann will test and find out something which can be reported in the tracker.

We have the lineage bug tracker on fairphone. I’d prefer to use that for the moment.



Good morning,
still have no answer from our admin … have to wait a bit.
But this morning I had a reboot, without a WLAN and without SDCard. Have the file uploaded.

I really have the feeling that my hardware is broken …

1 Like

In this case I think you may be right. Looks like corrupted memory to me:

mdss_set_rgb: mdss_set_rgb: r=32768 g=316dle kernÿÿÿÿ
 £ RQ Unable to hantual addel paging request at vir00, qcomress 0pgd = e2ff8000

Nevertheless the investigation of a possible WLAN issue (in conjunction with corporate Apple WiFi) should be continued. Should you have any information from your administrator, please forward them. I have a feeling that your company might use a protocol, namely 802.11r, which could be the culprit…

I have had a number of reboots since moving over to LOS. I’m not rooted through or know how to get the logs.

I’ve had problems on LTE/3G and Wifi. I’ve noticed the phone reboots a number of times when charging (often when it gets to 90+ charged).

I’ve reformatted my SD, but still have issues

I currently have a broken mic, but I doubt that has anything to do with it.

Edit: Just read “LOS” in the thread subject, but it happens with Open OS, too:

1 Like
  • AirPort Express 802.11n (2. Generation), Model A1392
  • 2.4GHz and 5GHz
  • IPv4
  • static

sorry that it took so long.


1 Like

Never mind, thank you for the information. :slight_smile:

So you do not use DHCP in the company?

But yes, but this router hangs on a network hub in our office and has a static IP. We basically use DHCP already.

1 Like

It would be good to know if other Android phones within your WLAN are affected as well, just to rule out some Airport specific settings (for Mac, iPhone & Co.).

The two Samsung devices of my colleagues with Android 5 are not affected. But the Fairphone is generally a bit more sensitive. :slight_smile:


What I know so far is:

It seems the built-in MSM8974 SoC already supports the 802.11a protocol as well, but the technical specification of the Fairphone 2 does not mention it. (Maybe some related code is not prepared to support it.)

The AirPort Express router in your office could be configured to use the protocols 802.11n and 802.11a, the latter one usually used for the 5 GHz band.

Now, my assumption is:

The current builds of Lineage OS for FP2 might contain 802.11a support, so the OS tries to seek for and communicate with 5 GHz networks over 802.11a. But some “FP2 stock code” (firmware?) probably cannot cope with this protocol, yet, and the OS is left behind with some “garbage” that cannot be processed and - even worse - corrupts the runtime environment. In such unexpected situations the OS shuts down and restarts itself immediately as the only way out of this misery. (I know, just speculating…)

As far as I have seen from your log files, there are (at least) two WLAN’s available in your office, and I expect one to be in the 2.4 GHz and the other one in the 5 GHz band. Your phone seems to connect to the 2.4 GHz network via 802.11n just fine. On the other hand, the WLAN clients connecting to the 5 GHz network in your office probably do this over 802.11a. (Again, just speculating…)

Let us wait for @chrmhoffmann what he is thinking about as the maintainer. Maybe there are some traces of the 802.11a protocol left in the Lineage OS builds for FP2 now, and everything related to 802.11a has to be vanished completely…