Frankly the scale of this suggests not a QA fail, but something much more sinister (pushing cheaper licensed chips/hw that works well enough on android and noone notices?), enough tin foil hatting for now, good night
I got my C2 today. I never visited this forum before I switched on the device. Chuck it down to excitement?!
Anyway, I booted the device after hooking it up to a charger and I made it all the way to network setup in the initial setup-wizard-thing before it froze. I just restarted it (held down the power button until it switched off, and then switched it on again) and skipped network setup. This got me to the login screen.
After logging in I managed to get the network-setup to work. I updated to the latest Sailfish and then put a SIM into the phone. After that it was a whole lot of random freezing apps until I fiddled a little with network settings.
On my phone the WLAN connection randomly dies, claiming my WLAN has limited connectivity. The WLAN coverage on the C2 is much worse than on any other phone in the house, so it could simply be a matter of bad coverage (on the C2 device), causing network to become unstable.
But then there´s the matter of no network access for any Android app through 4G.
We´ll have plenty bugs to figure out on this device for sure…
Anyway; if you guys with the frozen phones can try to:
Skip network setup during initial setup.
Then set up WLAN in an area with a good WiFi signal.
Then plug in the SIM.
This is just a thought, as this is what made my device stop being “stupid” and randomly freeze up… It has been reltively stable for like… six hours now. A new personal best! 
1 Like
Received the C2 today and started reading the forum again before starting the phone for the first time. Glad I did. I got a bit worried after reading about all the first boot problems and bricked phones.
I connected it to a charger first and it started charging without booting. Charge was 41%.
It didn’t show a LED charge indicator when charging or fully charged. Is this correct?
What I noticed during charging with the phone off, you can still see the big square with the percentage when the screen is off when you shine a bright light at the screen. So, only the backlighting is turned off during charging when the phone is off. Also only now the old-fashioned double tap on the screen to wake-up the phone works, like with the original Jolla. But not when the phone is booted up. (Still miss this handy feature)
After fully charged I booted the phone and everything went well the first time. Also connecting to my home wifi and performing the OS update to 5.0.0.21.
No SIM tested yet.
3 Likes
Correct or not is hard to say but there is no LED.
We had opened support cases in Zendesk regarding the issues we face (one phone doesn’t respond to touch input for the initial language selection, the other phone has the incorrect PIN/decryption bug). Response for both issues: Return to Jolla for a replacement or get the money back. The response came in below 2 workdays and was proficient.
3 Likes
Ironically, most modern Android phones now have tap-to-wake (either on by default or as an option)… Except the Sony phones.
At least on Sailfish on the Xperia 10 series you can run the following commands in the terminal:
mcetool --set-low-power-mode=enabled
mcetool --set-ps-on-demand=disabled
which will show you the clock and the weather on a dim black background when you take the device out of your pocket or when you wave your hand over the proximity sensor. This technically wakes up the screen, allowing you to then double-tap to view the lock screen. It’s not the same as the real tap-to-wake, but I find it’s close enough, because most of the times when you want to use it, the device is indeed in your pocket.
I’m still waiting for my C2, so I can’t check, but I suppose the same commands should also still work.
9 Likes
That’s unfortunate. The old Jolla had one (if I remember correctly) and my XA2 has one. Very convenient to see from a distance if the phone is still charging or fully charged. Now you have to take a guess or actively light up the screen to see the charge state.
How much that influences battery life?
Not at all! Well, every time you take your phone out of your pocket, the screen turns out for a couple of seconds, so I suppose it technically decreases battery life, but it’s completely negligible. Maybe it will have a slightly higher (but still negligible) impact on regular LCD screens, but on the Xperia 10 series’ OLED screens, it only turns on a few hundred pixels.
2 Likes
Works like always. Install mce-tools via pkcon and then enable the low power mode. So can confim it works
4 Likes
It also works on the XZ2 Compact Community Port, but i disabled it, because the last Kernel-Update from Sony which they used for this Port leads to a flickering low-power display at minimum brightness. (this is related to “Sony Logo flickers at startup” on XZ2 Compact at github).
1 Like
I opened a support case on Zendesk (Service and support request - General).
My case is that touch input doesn’t work at startup, when I select the language.
Impossible to continue. I tried to restart several times with or without SIM.
I am very sad, I hope they can help me 
2 Likes
Add me to the list, although I seem to have Schrodinger’s brick.
I have it alive after second boot, but it looked like it tried to re-encrypt on startup and now it has inconsistent access to it’s own storage. Currently keeping it alive on the off chance it can be saved.
Experience:
Arrived with 50% power, put on charge
Booted, added 5+ security code, completed setup
Networking wasn’t functioning, device recommended reboot, rebooted
Asked for passcode on boot, informed that encryption had failed
OS appears usable, but networking still non-functional and recommending reboot
Bluetooth controls locked up on access
Developer tools don’t install so can’t terminal anything
Torch works
Disk fun:
Screenshots do not appear in gallery, but do appear in PC when connected
Media files added to storage by PC do not show up in ringtone selector
Browser can’t read /home (or a lot of other things)
Store app complains with classic “Critical problem with app registry”
If anyone has any other ideas on questions to ask it, fire away.
Otherwise I’m gonna slap a Zendesk ticket in.
4 Likes
Schrodinger’s brick 
That is so cool!
4 Likes
C2 = S’s cat number 2?
4 Likes
Solution for all of us with a problem PIN lock loop is thera reflashnig with 5.0.0.21, because all of problematic devecise was with 5.0.0.5, and now we can wait for publishing factory image from Jolla, correctly in shop.jolla.com/downloads like as others devcies befor, isnt?
Mine is in superposition right now…
Like quantum particle…
But you cannot determine it’s state as the circle rotates…
4 Likes
Jolla doesn’t offer installable images for the Jolla-branded devices (and apparently there is no functional recovery mode on the C2 anyway). If the C2 doesn’t work properly, you need to return it because you won’t be able to make it work.
1 Like
Thats ridiculous, why is a shipped with bad firmware, and now i must pay shippint back to Finland, thats great with Jolla, so professional access, respect in sarcastic
2 Likes
You will get your shipping costs back. 
3 Likes