We have moved to a new Sailfish OS Forum. Please start new discussions there.

Since 3.1.0, Setsiemen, Jolla Tablet gets too hot

asked 2019-09-03 00:53:31 +0300

cfgardiner gravatar image

updated 2019-10-30 10:54:01 +0300

Alex gravatar image

Since upgrading to 3.1.0 on the Jolla tablet, the device regularly gets too hot. So much so that a pop-up warning appears. This happens particlarly when a browser is used, both the native (almost completely useless) one and webcat (somewhat better). With the first upgrade the device would regularly just shutown while browsing. After a factor yreset und re-installation of all upgrades this seems to be begining again. Before the factory reset it seems to have gotten so hot that storage was damaged. An fsck before the reset recovered quite a number of orphaned blocks.

It is surprising that Jolla have managed to keep the Atom SW good for so long. Any embedded device with Atom that I ever had in my hands always had problems with temperature. But now it's broken on Jolla too, please fix.

edit retag flag offensive close delete



Confirmed! (thought it is only due to charging AND watching video in browser, but had never before)


peterleinchen ( 2019-09-03 10:25:27 +0300 )edit

The same happens to me. Plus, Jolla browser crashes a lot of time while using with Webcat at the same time

carmenfdezb ( 2019-09-08 20:31:06 +0300 )edit

Is this still an issue on Sailfish OS 3.2.0.x?

Alex ( 2019-10-30 10:50:13 +0300 )edit

Hej Alex,

currently my Jolla 1 doesn't show 3.2.0.x as being available. I did just see the release notes in the Questions page. Is this pre-release or already production? I'll check on my tablet in the course of the day.

cfgardiner ( 2019-10-30 11:56:39 +0300 )edit

Hej Alex, well, I've registered for developer updates and downloaded/installed 3.2.0.x

My first impression is that the tablet no longer does a thermal shutdown when using the browser. I'll try and find time to do some stresstesting in the coming days and report any issues.

However, all is still not well. Loading "duolingo.com" for instance still just displays a white page as somebody else commented here recently. Loading "spiegel.de" still stalls shortly before the page is rendered. Why can't the re-load icon be made available here at all times? Or if it is the horrible Spiegel advertising which is screwing things up, what is the problem in rendering the >90% of the page that has alreay been loaded?

Are we going to get significant browser improvements with 3.2.0 or we walking into the next five years with the same shitty browser implementation as we have had for the last five?

cfgardiner ( 2019-10-30 18:27:03 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2019-10-30 18:40:58 +0300

cfgardiner gravatar image

Just tried the developer release 3.2.0.x on the tablet, the thermal shutdown issue seems resolved. Played the "Nirmal Purja" video from the Guardian website which seems to be fluid and without problems. However, loading duolingo.com is still broken. Some of my other known problematic sites are under investigation.

@Jolla : Do we get a substantial improvement to the browser in this release? Or is the current shitty browser being perpetuated? The release notes for the browser are very thin indeed.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2019-09-03 00:53:31 +0300

Seen: 247 times

Last updated: Oct 30 '19