Since this problem with security code / encryption affects a lot of us I think the wisest thing to do now is to open ticket on zendesk, as already pointed out by @eson
I think currently this is the best way to make this problem more “visible” to jolla. Browsing through countless posts on forum over many topics might not yield good (or fast) results.
Also, if we are prompted to return our devices - zendesk is the best channel to do that so we (and jolla) can track each case individually.
Just received 2 devices. One was powered on at 33% and showed the language selection menu. During unpacking (getting the phone out of the bag) we inadvertently swiped left two times and thus have automatically set up the device. Maybe that can happen during packaging and delivery too? Could that explain the unknown encryption codes?
The other phone had a completely empty battery.
Restore Data from XA2 (4.6) Backup
First boot trouble (solved with USB mice)
password not restored (email account)
Data (4G)
Sending Calling
Receiving Calling (Orange France)
Receiving SMS
Sending SMS (Orange France)
DTMF not working on call
Wifi on 2,4 Ghz at 54 Mb/s only, not negotiate on 5 Ghz
predictive keyboard not working
no fingerprint sensor 
no improvement for the browser
I’ve been using Sailfish since the release of the J1, I support the initiative, but now I really don’t see the evolution, and I’m getting tired of not having working basic features (like a working browser).
At this time this is not usable. And less usable than my old XA2. I switch back to XA2 on Sailfish 4.6 for daily use.
Android support not tested yet, not necessary because C2 is not usable at this time.
That has nothing to do with the C2; it has always been so, and it’s on purpose. Account passwords are not included in backups.
I also have some bluetooth disconnect, usually after a few minute of usage. Android App and native one are both subject to those disconnections.
Rebooting the speaker and reconnecting via the bluetooth menu work, even though this is a bit annoying.
The device arrived today.
I immediately put it to charge because I read the post about the first launch.
When I put it on the charger, it turned on by itself and the language selection started.
The first setup took place without selecting the Wi-Fi network. I read that this was a problem for many people, I was also forced to move on because there was no way to select the network.
As a precaution, I went into the settings. Here, I tried to take all the safety measures so that the device does not shut down. Turning on developer mode was unsuccessful, bluetooth and SIM operations did not work either. At that point, I already guessed that I was walking in similar shoes as the others. (for them, the Wi-Fi network selection was the point that failed).
Since every step seemed to fail, after a bit of thinking I thought the best thing to do was to leave it on the charger and reboot the device to see if it would boot. It turned on, I entered my code, but the loading screen spins non-stop, I think it’s completely stuck.
Presumably, I am also one of those to whom the device was sent in the very first round, and this may be one of the reasons why I noticed a similar error to the first commenters.
I am confident that it can be fixed without sending it back, I will try to follow all the steps I receive from Jolla in the future.
I wonder if there is a way to download an image of the SFOS version for the C2, load it onto an SD card and then start the boot and installation process from there?
I was able to set up my Jolla Phone but after a restart my C2 hangs after entering my security code (the wheel spins but nothing happens). I have no access to my phone, a factory reset does not work
My 2 cents:
)A nice device for developing!
I run in 1 mess:
I have exactly the same problem with my device. The wheel spins but I can’t access the system. In the meantime, I read several older posts related to encryption, the “boot disk” would be of interest to me as well.
Got mine today. Ordered a phone got a tablet. Even so it looks quite nice, It is reaaaaaally huge and heavy. Build quality seems to be good so far. Anyway I’m already missing a fingerprint sensor.
I got it with just 21% battery load. Anyway, setup went fine and after I loaded it to 80% I updated to 5.0.0.21, which as well worked flawless. Will have a closer look at it the next days. I doubt it will be my daily driver. It is simply too big for me. But nice to have a spare phone and a toy to play with until there is a fully functional version for my Xperia 10 V.
It arrived with nothing missing or broken. Charged it to ~80%, then turned it on and proceeded with setup (note, I didn’t put SIM in yet). Connected to 5GHz WiFi just fine, and setup went without any hiccup. Updated also without problem. So far, Chum is not installable as it’s probably missing repository for Sailfish 5.x. Phone is slightly bigger than my work phone (moto e32s), and that one is already big enough 
Hello All,
got the C2 a couple days ago.
Phone worked fine until upgrade of the OS.
After upgrading the OS to v5.0.0.21 the android app support died and I experience the same issue the I had with android support on my previous Xperia X10.
Here is the mentioned android app support issure.
Only adjustment that was made was turning on the android dev options and the touch visualization…
My turn,
No typo? For me the last update is 5.0.0.21.
Yes, sorry, my bad. 5.0.0.21 meant.
I received it on Monday after DHL went 'round Europe to get it to me.
It was shut down, 50% percent, plugged it in and the charging ‘act dead’ screen started, then I think I had to power on for the language selection. Lucky me, touchscreen worked, wifi worked, enabling developer mode worked. I made a copy of the recovery partition…
As others have tried already, I didn’t find a way to trigger fastboot mode. Recovery mode might be disabled because it is a soft boot into the same kernel nowadays, but no power/volume/USB combinations helped me.
The device is bigger than my Xiaomi Mi Note, however, without the rubber case, it is comparable with that one (with the case). But it is also lighter and thinner, and I really appreciate the flat screen (as opposed to the rounded Xiaomi one).
The build quality is very good, my intuition says that this was a device to show off, from the outside It is also a smudge magnet 
The rest of the hardware is pretty mediocre, but the screen is bright enough, sharp enough (one zooming homescreen animation shows a bit antialiasing flicker and that’s all) so I am happy. Camera is mediocre, vibration is alright, but speaker is tinny. Also, lack of other peripherals as known.
I’m trying to post some semi-darkness IPS comparisons with Xperia 10 mark1. You will notice diagonal shots are the worst - that is the reality of these displays.
All pictures are with the same 1/20 exposure F4 same lens etc.
Now from the bottom, there was some computer monitors light when turned them off, notice that C2 lowers the brightness. So, bottom, full dark vs some ambient light:
(the Xperia might have still caught a ligth from another room, but you get the dimming difference)
Bonus picture: Xperia 10, Zenfone 8, Mi Note 10, Jolla C2
What do you think, should a new topic be started for those whose device gets stuck after entering the security code? If so, which line should we start on?
1:1 my story
Hi,
I got my C2 today. After setup I updated to latest OTA 5.0.0.21.
There is a problem with Camera application.
I get a test pattern when I open it:
I can not take pictures or record videos.
Any idea what could be the issue?
Thanks!
Looks like the gstreamer-droid plugin got blacklisted. Try removing the ~/.cache/gstreamer-1.0 dir (or move it aside) and restart camera
