REPRODUCIBILITY: yes
OS VERSION: latest
HARDWARE: Jolla Phone 2026
UI LANGUAGE: English
REGRESSION:
Phone ran out of battery last night. While doing so it beeped loud enough to wake me. Inserted a charger and fell back to sleep. No alarm woke me, and when turning it on it went into a boot loop that persists also after having pulled and reconnected the battery. At boot the Jolla logo is seen, after a few seconds the screen flashes brightly and then it resets.
As I connected it up again to verify whether it was the Jolla or Sailfish logo that was seen during boot it now started up fully. The difference is that the battery had now been disconnected for much longer (15 minutes, vs 30 seconds).
I had a similar problem with OS .17.
The phone switched off overnight because the ‘battery was flat’.
The 10 per cent threshold is – unfortunately – not set by default.
After plugging in the charger, the phone started up – which, unfortunately, almost all phones do these days.
It froze after I entered the PIN.
I waited until the phone was at around 30 per cent, performed a hard power-off, and switched it on again; subjectively, the boot process took a little longer with the charger connected.
My guess is that it was an incomplete shutdown.
Your tips should be added to the FAQ, imho.
No idea who can update them.
Unfortunately this did not have as happy of an ending as I initially thought.
After having had the battery out, while the phone worked I noticed that entering my security code had a “lag” to it before the phone continued, as if verifying the code suddenly needed more time than before. That in itself wasn’t an issue - but the next thing I noticed was that the phone immediately shut down/reset if I inserted a charger. This was the same regardless of which charger, or whether it was a dedicated charger or a USB-data cable. It was not possible to both charge and have the phone active at the same time.
I also noticed that after having charged, the security code never verified the next startup - it just sat there spinning forever. A forced reset worked to get back to the now-laggier verification and I could get into the phone.
These issues are unfortunately serious enough that I cannot continue using the Jolla as my daily driver and I’ve had to revert to my previous phone. If anyone from Jolla is interested in debugging feel free to reach out - you can be as technical as you like in what my next steps here could be.