I have not got mine yet. Still eagerly reading these experiences. @WilliePre there is a mention that SIM card was not inserted when the phone became locked. Do we have experience if inserting the SIM card could affect somehow the first boot?
I received mine yesterday (DHL driver did his job) and here’s what I experienced:
- it took about one week for delivery
- phone was turned off and charged at 50% when I opened the box
- didn’t insert any SIM and charged the device to 100% before initial boot
- at initial boot I set a 6 digit numeric device lock
- touchscreen worked fine entering the digits
- WiFi was connected to 2.4 GHz access point
- I noticed that 2.4 GHz reception is much weaker on C2 compared to Xperia 10 II
- I had to change rooms and stay next to my access point for good RX/TX
- Android app took quite long for installation until I found out about the weak 2.4 GHz receptions (2 MBit/s rate!)
- I didn’t reboot the device and continued with recent 5.0.0.21 OS update download
- after OS update had been downloaded I restarted the device for the first time
- device unlock screen accepted my 6 digit code and OS upgrade starts as expected
- upgrade went fine, no touchscreen issues before and after the update
The bigger screen estate is something you need to get used to but once you brain had been adopted to this format it’s quite strange to look back on the smaller Xperia 10 screen. However, looking at the C2 screen I realized that Sony’s 21:9 format had been always something that didn’t fit for SailfishOS or even stock Android. It’s too small and too long and the more I look at C2 screen the more it annoys me going back to 10 II because of it.
The build quality of the C2 device is top notch and feels quite premium in your hands. However, some UI stuff needs to be fixed for the notch and rounded screen corners but these are minor issues. I hope that Jolla, given access to the underlying vendor blobs, can improve the usage of the Mali GPU to get less stutter when scrolling lager lists or webpages.
Now, for the first release of SailfishOS on the new Reeder hardware I think the future looks bright!
I keep my fingers crossed for all fellow sailors that run into device lock issues that there will be some hotfix for you real soon.
16 Likes
I suspect that somehow some of the phones was turned on just before or even during the delivery and that discharged the battery. Any file operation is dangerous with empty battery, especially encryption process which influences whole partition at once.
Note that this is my guess which to me seems to fit the facts. But I might be very wrong.
4 Likes
@Jolla This might be a clue to what happened to me and others. I do not have a 2.4 GHz access point. My WiFi is 5 GHz exclusive. 2.4 GHz is turned of.
Don’t know if it helps, but it might be a clue.
The 808 was way better!
I had “Networking not available” (same as my PinePhone), not no networks found. And I have both 2.4 and 5 GHz (Zyxel VDSL) in the same room.
1 Like
Do you have some exact cases? Browser is known case, and earlier reported here refresh rate developer tool label and homescreen launcher hint were fixed already.
The question is: why were the phones packaged and sent having been powered on?
Sorry to say this, but this is a serious quality control failure…
3 Likes
Depends on a real reason. There might be a strange bug or misconfiguration somewhere. Phone could power on during transport. Or almost anything else. I don’t dare to speculate. Especially as I might be totally wrong anyway.
We’ll see what the participants will say.
I’ll add that I understand as an electronic engineer. In such a new process where there is a lot of new variables it’s very human to miss something in a hurry. And we can read here how impatient many of us are.
3 Likes
I beg to differ, Reeder is not a new manufacturer, they should follow their normal process after flashing Android.
I think the risk here is more related to ways of working and quality controls from Reeder may not match other brands. I for example never heard of reeder until buying the C2.
1 Like
Remenber the well known bug that’s not possible to power off the Sony’s in a normal way (at least the X10, the 10-2 and 10-3 i don’t know), but one has to press and hold PWR + Vol UP until the vibrator comes 3 times. Otherwise the device will reboot immediately. This bug is not fixed until 4.5.0.24. Maybe this bug still persists and also on C2. @Jolla ?
Did someone look up the uptime of the phone to check if this was the case?
AFAIK the flashing is carried out by Jolla itself.
If that’s the case I seriously hope Jolla comes forward and even if not “standard procedure” they show with a way to fix the bricks at home rather than having no solution…
that being said I’m happy to be still waiting for my phone, I now know what set up conditions caused issues so I can try my best to not mess it up.
Still the case on my xperia 10
Pretty bad for the battery 
1 Like
Same situation for me. It is supposed to arrive today.
I will plug it, wait until full charge, light some candles, pray to all the saints I know and…hope for the best.
3 Likes
Seems like we need to open some books and find some extra saints just in case 
, I’m quite concerned about breaking it without really doing anything too unusual.
1 Like
FYI for anyone receiving C2 in upcoming days/hours, Jolla posted first-time instruction based on the feedback from this thread: Jolla C2 first time use instructions
6 Likes
Here’s my feedback: I received the phone already last Thursday but didn’t have much time to test it in very detail.
Generally, I have a relatively positive experience. Especially it came as very nicely packaged phone, similar to the C1 and I received it with about 50% charge.
The build quality is amazing from the lock and feel, it feels perhaps better than the Xperia’s and to my opinion even better compared to the Samsungs S20/23, I had to use from work. What I miss is the notification LED and fingerprint reader but we knew it was left out in the C2. The Privacy from Finland text near the camera side is barely visible but I guess laser engravings are challenging, so when you look very closely you can read it. The tiny loudspeaker is far away from Samsung build quality but it’s okay. Very positive is that C2 allows two SIM cards and one mircoSD in parallel, also there is a 3.5-headphone jack which I appreciate.
The silicone cover and screen guard protector are great and attaching those were easy thanks for those! When attaching the cover one needs to take care that the three camera wholes are actually placed in correctly to avoid collecting dust.
To SailfishOS 5:
- No issues when setting up and first time starting the phone.
- C2 recognized both SIM cards and my old LUKS encrypted microSD.
- Restored all data from Xperia 10 plus backup.
- Enabled Android app support, however sometimes Android app-support crashed while using an Android app.
I managed to install some SFOS and Android apps, noticed also that F-Droid and Aurora didn’t show up when installing them via Jolla store. After reading this thread, I proceeded to update to 5.0.0.21 (around 600 MB of size) which went fine but I couldn’t spot any improvements. I don’t know if the „not showing up Android apps from Jolla store was fixed” but probably it was.
The more serious issue for 4G calling still persists. CSD testing shows a failure for SIM testing (invalid card identifier) but that’s the only error I noticed in CSD. For me this means that for my Telia (FI), SIM calling works, call receiving not in 4G network but in 2G; my second Vodaphone (DE) SIM both works here despite being in roaming network. This is interesting but was already reported here. Swapping SIMs didn’t change anything.
Camara picture taking works well, video not at all and camera freezes. I installed Aperture and Open Camera Android apps and image quality as well as video recording works great. The keyboard has no text prediction. This section is missing entirely in comparison to SFOS 4.6.x. I would like to know why.
Some important apps like Chum repo are installable but doesn’t appear on app grid, MeeCast, PureMaps, MicroTube, … not installable which is sad. However MeeCast can be installed from JollaStore but there is an issue that it doesn’t save the location. Some adaptation might be needed for C2. I’d like to get MeeCast also into the events but this trick that worked on my Xperia’s doesn’t work on C2.
Bluetooth pairing, audio and sharing works well. I don’t know about BLE as I have no device to test it. Initial GPS connection I got very fast using high accuracy. This seems a lot quicker than compared to the Xperias. Internet sharing works also nicely and as well the switch between networks. So far, I have not noticed an issue connecting to 2.4 or 5 GHz Wifi networks. Also, from those few days of playing around I noticed that battery life is excellent even though I wasn’t able to install SystemDataScope yet.
To sum up, mostly I’m impressed considering what a great job Jollyboys managed to achieved. I guess we know that things aren’t perfect out of the box and Jolla isn’t Samsung nor Apple thus we haven’t paid our money to the golden cage gatekeepers. We voted for privacy and common community approach. I hope the glitches regarding 4G calling, video recording and predictive text input could be fixed soon. I feel sorry for the ones that had received their C2s discharged and with encryption issue.
If I have more time for testing, I’ll be happy to report more.
PS: I managed to install Chum gui installer (using SFOS 4.6.0.15 for repository in Chum settings) and MeeCast from there as well. C2 is progressing
20 Likes
Glad I use a community port for a phone that costed me 80 euros and not one that came bricked in the box. 
In all seriousness this is very unfortunate to see, it’s a very midrange phone being sold to the community for a high price. Not the predecessor to the Jolla C that our community deserves, but I hope people who bought them and found them bricked will be able to get them fixed easily.
I remember hearing users having to send their Jolla Phone back to get reflashed if it was found to be bricked. I hope that won’t be the case again.
4 Likes
Could you please try to enter 00000 (5 zeros) as that’s the default encryption password that will be changed as a first step of the Startup Wizard. This 00000 is not visible anywhere in the user interface.
6 Likes