Jolla C2 stuck on 2.5G after 2G test in CSD-Tool

Bug Reports
1

REPRODUCIBILITY: First timer for me
OSVERSION: 5.0.0.77
HARDWARE: Jolla C2 - s19mps - s19mps - 1.0.0.59 - aarch64
UI LANGUAGE: Deutsch (user: de_DE, os: de_DE.utf8)
REGRESSION: not specified

DESCRIPTION:

Jolla C2 stuck on 2.5G after 2G test in CSD-Tool.

PRECONDITIONS:

Jolla C2 on 4G.

STEPS TO REPRODUCE:

  1. Open CSD-Tool
  2. Test 2G
  3. Jolla C2 stuck in 2.5G

EXPECTED RESULTS:

It turned back to 4G after testing 2G.

ACTUAL RESULTS:

Jolla C2 stays in 2.5G also after:

  • Choosing 4G-Test again in CSD-Tool (doesn’t work anymore and fail)

  • Turning Networkmode from 4G to 2G and back to 4G in Mobile Network-Prefs

  • Turning Flight-Mode on, wait 10 minutes and turn off again

  • Perform “systemctl restart ofono”

  • Rebooting 3 times

  • Restarting Network in Jolla-Tools

  • Using Trick 1-3 from: Resetting oFono Settings | Sailfish OS Documentation

  • Put in other SIM-Card from other Carrier → also 2.5G

  • CellMon shows only GSM as technology although i didn’t change location while testing

MODIFICATIONS:

  • Patchmanager: yes
  • OpenRepos: yes
  • Chum: yes
  • Other: none specified

ADDITIONAL INFORMATION:

Device Owner User: defaultuser
Home Encryption: enabled

the initial version of this bug report was created using Bugger 0.9.17+git1
1 Like
2

Even after rebooting! that’s some bug. Tried switching it off and on again (I’m serious, it’s not the same as a “soft” reboot)?

PS: so you’re stuck on 2.5G now. How do you know it’s reproducible then?

3

Tested it also in SIM-Slot #2 but card is not recognized there and slot isn’t recognized at all by the system. It seems there is a serious-configuration-error. I never use/test SIM-Slot #2 before, but usually after start both SIM-Slots were displayed in SIM-Configuration even if SIM-Slot #2 is disabled. This i not the case anymore and i cannot turn on SIM-Slot #2 there.

So are there hacking-tricks left?
I didn’t want to reflash the C2.

4

Thats a fair point, i corrected it.

5

Maybe clear the modem state:

# backup just in case
dd if=/dev/disk/by-partlabel/l_runtimenv1 of=runtimenv1.bin
dd if=/dev/disk/by-partlabel/l_runtimenv2 of=runtimenv2.bin
# wipe partitions
dd if=/dev/zero of=/dev/disk/by-partlabel/l_runtimenv1
dd if=/dev/zero of=/dev/disk/by-partlabel/l_runtimenv2
reboot
2 Likes
6 
dd: error writing '/dev/disk/by-partlabel/l_runtimenv2': No space left on device
4097+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.165615 seconds, 12.1MB/s
[root@JollaC2 defaultuser]# reboot
Read from remote host *****: Connection reset by peer
Connection to **** closed.
client_loop: send disconnect: Broken pipe
❯ cd /dev/disk
❯ ls
by-diskseq  by-id  by-label  by-loop-inode  by-loop-ref  by-partuuid  by-path  by-uuid

“by-partlabel” doesn’t exists, so what to choose?

7

Be careful here, the phone disconnected after reboot and you are running commands on your computer. But as you can see above, dd already wrote 2MB to the partition successfully. Is the modem still stuck in 2.5G?

8

Yes, still on 2.5G. I tested also another carrier SIM (Telekom) to sort out Cell-Problems with same result.

9

So where store SailfishOS the current configuration for SIM-Card?

Or which config is modified by CSD-Tool to stuck on 2G?

I can’t find anything about it in the forum.

Also weird is: Modem count: 1 (expected: 2)

So is there a way to reinstall only the modem-driver?

10

Honestly I don’t think reinstalling the “driver” is going to help here (and that’s not what @affe_null 's commands do either).

The No space left on device error is to be expected and probably doesn’t mean anything.

11

If clearing both l_runtimenv1 and l_runtimenv2 at the same time doesn’t help, the only remaining thing I can think of is something left by the HAL in /data, but if you try to delete files there, be prepared to reflash in case the phone stops booting.

1 Like
12

A reflash to newest Version 5.0.0.77 fixed it, 4G is back.

4 Likes