Feedback on Jolla C2

After few hours of fiddling with the phone, I noticed there are few things that needs solving.

  • Round corners in the display causes problems on several places in the OS.
  • Camera notch causes prolems with Web-browser when browsing in landscape mode (same with the round corners)
  • Some apps keeps freezing, usually it’s the Jolla store or some other app that is using data connection.
  • The phone is somewhat slow, comparing with Sony Xperia 10 III
  • OS itself does not take use of the wider display, like number input or other input could use bigger/wider buttons

Hardware is pretty low quality.

  • Display low resolution, backlight leaks very badly, viewing angles bad
  • Slow CPU
  • Very heavy phone
  • Protective casing has sharp corners, molding defects, covers the display edges so it’s hard to swipe from left or right. Pretty useless IMHO.
8 Likes

Is SFOS on C2 a castrated version?
edit: or is this only because it’s an unfinished beta version and will it get full functionality later?

I don’t believe its meant to be castrated. Its almost certainly an unfinished product, probably released before it was robust enough, and requiring many fixes and updates in the future to get it to ‘Sailfish OS as its meant to be’.

In my experience its always better to undersell and overdeliver, rather than to oversell and underdeliver.

1 Like

Sadly, I think this phrase, ‘Sailfish OS as its meant to be’, will come back to haunt Jolla.

2 Likes

It seems at least a number of C2s are being shipped to customers whilst powered up. If shipping involves air freight then this is a complete no-no and against international air freight regulations due to the fire risk. All devices must be powered down before shipping (perhaps something for @Jolla to look into).

However, that aside, this may mean that some C2 batteries are near empty when the customer receives their phone and starts to set it up. Perhaps, because these phones are then shutting down, maybe not cleanly, during this process (e.g. The encryption process), this could be the cause of bricked phones?

Maybe all C2 customers, when receiving their phones, should put then on charge for a few hours before first trying to use them?

6 Likes

My C2 arrived in an off state with a battery level around 50%. I was cautious due to failure reports here, so charged it before attempting setup. This worked without a hitch. I then immediately updated to SailfishOS to 5.0.0.21, which also went well.

I didn’t get home screen rotation to work initially, but did after a reboot. Could be a problem between keyboard and chair, but it prompted me to run the CSD tool, which revealed a couple of failing hardware tests. (I have reported those on the forum.)

The phone came in a very nice box - also an interesting way to publish source code :wink:

I appreciate the lack of charger and cheap earphones, that would only serve to increase e-waste. Also appreciate the flyer with a greeting to the community.

The phone looks nice and feels pretty well made. It’s also big! Maybe not compared to what I see other people carry, but compared to my preference and previous devices. I’m sure I will get used to it, though.

Three hardware features are notably missing. A camera button would have been nice, but wouldn’t make a huge difference when the app takes several seconds to start anyway.

I think I will miss the fingerprint reader and/or NFC capability more. Fingerprint is a useful shortcut when you have a long Unlock code. A U2F or FIDO2 hardware key (Yubikey) could be used for quick unlock within a sudo-like time window, but I’m worried about wearing out a USB port that is difficult to replace. That’s when NFC would have been handy.

Another convenient solution would be to have a long encryption passphrase separate from a shorter unlock code:

And speaking of encryption, why not LUKS2 on new devices?

[Edit to add link to failure reports]

8 Likes

Thank you for the detailed und objective report.
Mine is still in germany :slight_smile:

It is my understanding that it went a bit like that.

There were known issues when
the hardware was ready to be flashed.

Instead of delaying shipping again for some time to get an image with fixes included, it was decided to flash and ship as-is, and deliver an OTA update containing the fixes more or less in parallel. A ‘same-day-patch’ if you will.

Which is what we’re seeing today.

Personally I like this approach.
Granted it could have been communicated much more clearly.

That being said, we don’t know what the ‘known issues’ mentioned above were exactly. Some of the things people are reporting were likely not yet known issues at the point when this decision was made.

2 Likes

Just received my C2 yesterday. I went through the initial wizard. Everything completed successfully. After that I installed the latest 5.0.0.21 update. The update also completed successfully. Everything seems to be working, except for the camera video recording.

3 Likes

Agree, especially info how to reflash the device by computer including publishing a working flash image. At the moment, customers don’t even know how to reflash the device. OTA update helps nothing if one doesn’t come over the language selection and device stucks.

So question is:

  1. how to set C2 into flash mode
  2. Software and operation process on Linux, Mac and Windows
  3. working image for initial setup and network connection to load future updates.
1 Like

Now, take this with a ** big grain of salt** because I may be very wrong here.

But AFAICS most SFOS devices come with their recovery image right on the device.

Try:

devel-su
ls /boot

and you should see hybris-recovery.img.

One should be able to copy this off the device and use it as recovery image. Of course that needs a booting device in the first place! :slight_smile:

And we will still need to know how to get into fastboot mode, but I’m sure that info is out there somewhere in Turkish for the Reeder S Pro Max.

Again, I might be wrong here, better wait for official info by Jolla. But someone adventurous might want to try.

9 Likes

I tried the C2 for one day, as a replacement for my Xperia X plus.
It is a good experience so far, with a few issues.
I like the UI, the addition of the App Support button on the menu bar is really convenient.
Using the command line, I was able to install storeman and my usual apps from here with no issue.
The issue I have are the following:

  • Issue with sending SMS, it worked at first when I switched to 3G preferred, but failed later on. In the end, my phone lost the SIM card and the network entry menu, I had to remove my sim card.
  • Issue with App support, MicroG is not recognized by other apps (Spoof permission is enabled on both SFOS and the android setting of this app)
  • Still no usable GPS location unfortunately.
  • I am not able to play / pause music with button on my jack headset

Nice device overall for the price, I think I will love it :slight_smile:

6 Likes

Thanks @nephros for this hint! So I’ll hurry to copy this recovery image from phone to computer, just for the case…

edit: went fine! Have the image on computer now.

Found something on YouTube - it involved holding one of the volume buttons while powering on. Tried both - neither did anything.

1 Like

What about /home (Käyttäjän tiedostot)?

Can you try to do a df -h ; df -i from the terminal?

Does it also say no space or inodes left?

1 Like

Mind you there are two takes on this method, while holding the correct volume button make sure you try both methods:

1 - use the powerbutton to power on
OR
2 - insert a usb cable to power on

I’m stating this so obvious because I’ve flashed at least 40 phones of different manufacturers over 20 years, and in many brands only method 1 or 2 works, but they are usually not mutually exclusive depending on brand.

1 Like

Tried that too. No dice.

(I have a working device, just trying to investigate a bit).

2 Likes

Disk usage overall.

Here is link to df -i printout
df -i
Here is link to df -h printout
df -h
Expires in a week.

Looks like all the goodies came along :grinning:
C2_root

Yesterdays failed upgrade attempt broke something.
C2 cannot download the update any more and hangs in “Waiting for connection”, when trying to fetch update package. #pkcon refresh also hangs.

Otherwise I can open browser and go browsing network (as long as I don’t need to type anything :grinning:)

On-screen keyboard has stopped working or does not come visible. Cannot write in browser or Notes.

Luckily I can now concentrate on admiring the beautiful sharp foto’s that the camera takes. :slightly_smiling_face:

Update 29.10.2024.

  • On-screen keyboard magically returned next day. Now I can write in browser and apps.
  • Package manager(s) are sort of offline. Updating OS with settings is impossible, because update UI cannot download update package, instead update is hang in “Waiting connection” until timeout.
  • Package manager pkcon cannot install anything, propably because it also cannot find any server or update repositories or something.
  • Jolla store and Openrepos cannot install anything and do not recognise any installed apps.
  • Installed apps cannot be uninstalled from app grid.

So my phone is in kind of Kiosk mode. I can use it, but cannot make software changes :grinning:

Waiting (patiently) instructions from Jollyboys to learn how to reflash Sailfish OS. :pray:

Update 1.11.2024
I caved in and send service application to Jolla zendesk and eventually send phone to Jollyboys for repairing (=ReFlashing)…

3 Likes

I have the same issue. My C2 starts, i can enter my security code, but than… wait… wait… wait… watch the turning wheel. But nothing happens. A factory reset would prob. help, but it is not supported, which is very hard for me to beleive.

2 Likes