Google Maps says the Phone needs to cool down for 3d view

Hello there,

i bought a FP5 2 weeks ago.
Up until now no issues.
For the last 2 days when using google maps via Android Auto, google maps normally displays small 3d objects if it has the data to display buildings.

After a few minutes of driving the messages pops up “The phone must cool down to continue 3d view” and removes the 3d objects from the map.

When touching the phone, its moderately warm (nothing i would guess indicates overheating), The phone is not charging, Playing some games also does not indicate any overheating issues.

Anyone an Idea what that could be? I mean my 6 year old Onplus7T could do it without issues.

1 Like

Is everything up to date? When searching for “Device needs to cool down” I can find a few threads which are all 2-3 years old and they indicate that the issue was with Maps and should have been resolved in the meantime.

Yes everything is on latest.

Ok,after driving yesterday evening. So the google maps app tells me the “Layer 3d buildings will be deactivated until the phone cools down”

This happens aspprox 15min into driving. Phone ist medicore warm i would say.

How to tackle this?

Are you using the screen in the car or on the phone?

Actually this has never happened to my FP4.

But I also regularly have issues with Android car when I use car sharing in different cars. I think sometimes also the car is the part that needs an update. Can you check if this is the case?

I use only the screen of the car. I actually never updated a car firmware.
I have to look if that’s even possible outside a workshop

It’s probably just a wild guess, but somehow this reminds me a bit of the issue with the FP4 that randomly dimmed the screen when exposed to the sun. Which turned out to be some kind of overheating in the sense that one of the many internal thermal measurements of the phone exceeded a threshold that probably was just too low. In fact this could be reproduced by playing certain games for a few minutes and the phone didn’t feel overly warm/hot when the problem occurred.

Back then, somebody was able to find the measurement that caused the issue: Random Screen dimming (while brightness slider stays at 100%) after A12 update - #291 by LukeSkywalker

Ultimately this had to be fixed by an update. So if this case would turn out to be a similar case, I think the Fairphone support would have to be involved.
But I’m aware that response times of the support aren’t good enough, though.

2 Likes

I downloaded Aida 64 to have a look at what the temperature sensors sat.

There are a lot and it seems not all are used. But what is obvious after a few seconds is that 2 sensors are going wild.

pm7250b-ibat-lvl0 and pm7250b-ibat-lvl0.

While everything else is stable there toggle wild between +20 and +75 degrees

From a quick look into the schematics I think they have to make with something around the battery (the name indicates this, too). Search for pm7250 to find it. Maybe it helps to remove and put back the battery?

Ok I had a look at the schematics and the IC.
It’s a power management IC. Most probably it regulates the battery charge current dependant of temperature as a safety measure.

As it toggles so rapidly I guess either the IC raises flags about the temperature in form of interrupts or the main cou core is polling the temperature constantly and sometimes sees the high values.

So for me this is a defective chip.

Removing battery and restarting didn’t change anything.

I installed AIDA64 v2.08 on my FP5 and it didn’t show your mentioned sensors, see the attached screenshot.

Only a pm7250b_tz is shown, the values are going from 33-39°C.

This is how it looks on my phone. So question is why my Aida displays these sensors. And if android is using them or if they are false values.
I caught them when they where at max scale.

My Aida is also 2.08

Interesting. If I connect my charger both values disappear from Aida (but only the values) if I restart the entries for those sensors vanish completely and look like the posted ones from the previous poster

I disconnect the charger they reappear.

So now I have to test if I simultaneously charge the phone in the car the problem persists.

2 Likes