On a Jolla Phone (5.2.0.17). Inserting USB causes crash and I cannot start device if USB is connected. The red led is on when USB is connected. When attempting to start the haptic response happens, but it does not start.
Tested with different chargers, all chargers and all USB connections cause crash & fail to start device -issue. I can telnet to the device when booting to recovery mode. Tested to change USB default mode to “Charge only” and other options (no change). Performed telnet wipe “Reset device…” (no change in weird behavior). Lifted battery, reinserted it and “Reset device…” (no change).
If USB is removed during booting of the device, but attached after the Jolla logo is seen, the device can (sometimes) start with an USB connected. In this case it charges but only to 56% (the device says it is full). After it begins to discharge, inserting USB will cause a crash.
When the device is successfully booted (USB attached in right moment) and proceeds to charge, and eventually shows a lightning symbol in top left (instead battery percentage)… In this state I can plug any USB without causing a crash. In this state, when I remove a USB charger it messages: “Unplug charger from power supply to save energy”. I can attach it to computer and the device ask which USB mode I want to use (and transfer files etc).
It is weird and feels inconsistent, sometimes it hangs up to “Enter security code” step or show a logo of a lightning box with a charger connected to it. Feel like it cannot handle battery charging.
I haven’t noticed anyone report this behavior. I can produce logs (a persistent log available below)
For what this is worth, my ageing Xperia 10ii also crashes occasionally when connecting to my PC, so it may not be specific to your new device or the Jolla2 in general.
Yes, I can. Should I share it here? I installed Battery Buddy and it shows “charger connected: no” but also “state: charging” (when boot succesful by installing charger after logo appears)
Please. Though the forum software might give you a hard time uploading it; You need to tar it into a tar.gz file, which needs to end in .targz.
And make sure that you first enable persistent logging, then reboot, then reproduce the issue, reboot, retrieve the whole journal. In other words, that the logs actually reflect the issue.
I enabled persistent logging and rebooted the device. It showed 56% of battery power after reboot and crashed when USB was inserted as now expected. I connected the USB to a computer during startup but the device got stuck at “Enter security code”.
I forced a reboot and successfully connected the USB to computer. Rerun the script and collected the log. The log should show both the “Enter security code” -hang up and hopefully reveal the battery issue.
Not being sure how to get the compressed log to a .targz I opened the file, and re-tarred the folder and renamed it without . in the middle of the name. Thank you for initiating with this issue.
Should I collect all of this information to the Bug Reports category? Some thread informed that issues should first be asked in this General category. I send the logs and narrative to Jolla Zendesk too.
I will now use the device until the battery runs out, perhaps this would somehow calibrate the device, and help the device recognize the battery. Battery Buddy application does not recognize the battery and says the charge is -1%.
Is this what the documentation asks for? Damn that’s a lot. Just looking at the journal for now.
Are you sure Fri 2026-08-28 8:59 is when the crash happened?
edit: it’s a lot for 3 minutes, and half of it seems to be [ohmd], a service that is present on my phone as well but does not take up so much:
# journalctl -b -u ohmd.service
-- Logs begin at Fri 2026-08-28 14:52:07 EEST, end at Sat 2026-08-29 18:48:14 EEST. --
Aug 29 12:26:53 Xperia10III systemd[1]: Starting ohm daemon for resource policy management...
Aug 29 12:26:53 Xperia10III systemd[1]: Started ohm daemon for resource policy management.
It’s a “daemon for resource policy management”, whatever that means.
I will replicate this process and observe the precise timing, after I’ve compleated the test of running the battery empty in use (in hopes this would somehow calibrate the device).
Yeah, thats 6MB of log data. I don’t know what is relevant for finding the problem… I think the “Enter security code” hangup issue is there and the crash & reboot happen right before that.
No stress! Thank you for the help in filing a bug report.
I learned about the Test tool CSD and run all the hardware tests. Everything else works but there is something wrong with the battery and the charging process (or both). 2 minutes after starting the device (after running battery dry as a test), it shows that the charging status is full at -1% and that battery temperature is -40°C.
As a test I used the device until the battery was empty (95 hours). After this the device no longer crashes on USB insert… But it does not start with USB attached (I have to insert USB after boot logo to use it) and it does not show battery % in the top menu. It behaves unexpectedly when inserting USB (sometimes showing Lightning Symbol, sometimes showing Lightning Symbol + attached cord). The top led is now white sometimes… Previously is was always red.
Camera Flash does not work either… But the Inari Blue cover works. Could this be a hardware or battery issue? (I tested to detach the battery and re-attached it but it did not change the behaviour)
Could this be a hardware or battery issue? (I tested to detach the battery and re-attached it but it did not change the behaviour)