English

Reboots by running OsmAnd navigation on a charging LOS Fairphone2

Have you already filed a request to Fairphone for a device exchange?

My household now has two FP2s, mine is an older one with an AB SoC and my wife’s is from a newer batch with an AA SoC. The first one she got delivered overheated instantaneously followed by a reboot, it had to be returned and exchanged. The new device still reboots about twice per week, but we’ll see how it develops after installation of the latest modem firmware.

I never had any reboots while charging and navigating with OsmAnd. My phone reboots rather spontaneously while doing literally nothing once a month. :no_mouth:

1 Like

I tend to believe it is the combination of both.
I have an older SoC AB version by the way.

I have used OSMand and also Navmii with Lollipop. Navmii is fine so far.
OSMand seems to be quite resource hungry and demanding. It drains the battery quick and while charging and navigating the phone gets hot as hell. I did not have any reboots yet, but this heat increase could lead to any kind of strange behaviour of the entire device.

Other phones maybe can take this high core temperature but as it looks FP2 comes to a limit.

I didn’t. In the last time I have had reboots only at this special condition, and I don’t have the impression, that the Fairphone devs have time to care for such special requirements. They won’t ride a bike to collect experiences at it.

1 Like

Probably you are right with the Osmand high power demand. The battery never charged completely with running Osmand, neither at the bike, nor at a car. Even when charging and running Osmand at the car the Phone lost charge.
But in my case the device temperature should not have been crucial: The phone is sitting on the bikes handlebar without any extra cover and the outside temperature has been around -2° C with strong wind force 6 - 9, quite uncomfortable to do a ride. At the test yesterday with the Galaxy I have had light winds and temperature between +5° to +10° C, nice to ride a bike.

Well, you know, that low temperatures can get on the battery quite a lot?
-2°C plus heavy wind means really low temperatures.
That might very well be a reason for failure and reboots. Don’t underestimate 7°C in temperature difference. And then add the wind and possible differences in design to it, that might keep the battery of the Samsung warm.

Here’s an article from a german daily, reporting on a DEKRA test of pedelc batteries:


"Lithium-Ion battery: The reason batteries hate the cold"

Die ideale Temperatur für den Gebrauch eines Lithium-Ionen-Akkus liegt bei ungefähr 20 Grad. Je kälter es wird, desto träger werden die Ionen. Irgendwann verweigert der Akku den Dienst vollkommen. Wann das passiert, ist von Akku zu Akku verschieden, weil nicht alle Hersteller die gleichen Materialien verwenden. Ansehen kann man es einem Akku jedenfalls nicht. „Die Zusammensetzung des Elektrolyts ist ein gut ­gehütetes Geheimnis der Hersteller“, sagt Andreas Richter.
:uk: (my own translation)
The ideal temperature for using lithium-ion batteries lies around 20°C. The colder it gets, the more inert the ions turn. At some point the battery will stop working completely. When that happens, differs from battery to battery, as not all manufacturers are using the same materials. There’s no way to know what battery you got. “The electrolytes composition is a well kept secret of the manufacturers” says Andreas Richter.

Yes, I know.
I wrote about the low temperatures to state, that the last reboots I suffered aren’t caused by (to) high processor temperatures. It also wasn’t caused by low battery voltage. The battery is charged continuesly by a hub dynamo via an extra buffer battery. Directly after the reboots there was enough battery charge at the phone and I could start Osmand again and it was working properly, for some time (fifteen minutes or more).
Last summer I have got the same reboot effects with outside temperatures between 15 and 25°C.

For me high or low temperatures don’t seem to be a cause for my reboots.

Sorry if you mentioned this somewhere and I don’t recall or saw it, but for reference if others want to check the problem out … Is your performance profile set to “Efficiency” already? …

I thought the “Limit maximum CPU power” effect of this setting should be worth some attention in cases of overheating and reboots.

Thank you, you are right, I didn’t mention it:
I have set the performance profiles
at the FP2 on ‘Power save’ and
at the Galaxy on ‘Balanced’.

1 Like

Interesting. Last year when I drove to Italy for my holidays I had the phone navigating and charging at medium brightness for the whole ride (around nine hours) without discharging. It rather charged, therefore power consumption was lower than power input.

I guess there are far too many factors to consider why your phone behaves this way. I’m sorry that you have to part ways with your Fairphone for this reason but I can absolutely understand your decision.

1 Like

There is an update for the Android ‘Forumslader’ app, version 1.4.180626:
It contains a fix for crash after establishing Bluetooth connection.

Hi, I have reboots while using OsmAnd in cars. Even when not charging the phone. Even with LineageOS 15.1.

I kept a LineageOS 14.1 up to date before that and it worsen in the last 2 to 3 months.

I just installed Logcat Reader to constantly dump logs in a files and will provide some logcat here.

Regarding performance settings, I experienced that OsmAnd was enable to reroute live after a mistake if using the most powersaving profile, so I was using the balanced one. I’ll try the “Rapid” one for the coming days, and may try the “Most performance” one after that.

[24h later, no reboots so far, after 2x20 minutes usage of OsmAnd ; I wanted to share some hope about this performance profile tweak]

I also have reboots with OsmAnd but also with Sygic GPS Navigation.
I just have GPS enabled during the reboots, and nothing else : no bluetooth, no GSM, ni wifi…
I had the issue with LineageOS 14.1 and now I’m under 15.1 : the issue is still there as described by the topic author.
In my case I always found the FP2 very hot during reboot. It’s look like a hardware protection such we can find on laptop with burning CPU :slight_smile:

This w-e, 2x2h of OsmAnd.

I got a reboot after the 1st 2h trip guided by OsmAnd, a few minutes after I ended the session (cause I was arrived). I lost that log because Logcat Reader app is loosing logs when the phone reboots. So I now capture my logcats this way:

I got another no-GPS reboot the day after.

And then a reboot during OsmAnd guiding (with VLC music in background). The phone cut the music, becoming unresponsive for a few second, and then reboots (I suspect some kind of watch dog software impatient to reboot at the 1st sign of slowness).

And a last one captured also.

20180826.logcat.txt.xz.ttf (79.0 KB)
20180926-02.logcat.txt.xz.ttf (314.2 KB)
20180826-03.logcat.txt.xz.ttf (126.8 KB)

The files are XZ compressed texts, appended with a .ttf extension because of surprisingly naïve limitation of this forum about allowed extensions in uploads.

I hope those files will be usable by @chrmhoffmann :slight_smile: for instance. Please correct me if I’m doing something wrong in the process.

Can you grab /proc/last_kmsg after reboot?

Chris

Here is the last one:
20180827_last_kmsg.txt.ttf (113.8 KB)

So you like to share your very favoured true type fonts here with us…:smiley:

1 Like

I also have reboots while using GPS apps in car, same as @siltaar under LineageOS 14.1 and 15.1.

Mostly I use “Blitzer.de” speedlimit warning (standalone, no other apps activly running),
but also “Here WeGo” navigation, charging was allways necassary.

And the “running time” of navigation doesn’t matter, sometimes the FP2 reboots after 10min, sometimes after 2hours.

I changed the power adapter (12V/USB) from cheap to powerful, so I can exclude the cause of a weak (or changing) power consumption.

@chrmhoffmann here is my last_kmsg at pastebin from the last navigation/gps-reboot with a kernel panic :fearful:

I’m concerned not having had any feedback from posted logs since 4 months, nor any improvement while updating LineageOS. Even with recent updates, the phone still reboot twice a day and too many times by trips while using OSMand to rely on it.

It can also reboot while writing an SMS in Silence, for what I notice.

Contrary to what I wrote before, changing the Parameters->Battery->Power efficiency switch don’t change anything.

I wonder if switching back to FPOOS would allow for a reliable phone again. I think I’ll try.

Oh yes please let us know if FPOOS solve the issue or not !

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.