Jolla C2 first time use instructions

How many People are we, who has the Problem with the never ending spin on correct lock code?

Please like this post, who has this Problem, so we can count how many unusable Jolla C2 devices are in the wild…

26 Likes

I was aware that speeding things up may cause device to be still “under construction” but completly unusable device?

Don’t get me wrong, Im still looking forward for better future for Jolla C2, but I wonder how could all this obvious problems be missed and devices shipped like this. No one from Jolla tried to booting new device?

5 Likes

The big problem is the lack of recovery image. All these problems would most probably be solved if we could just do factory reset.

7 Likes

How about a short poll - like after every update?

  • My C2 is unusable due to THE BUG
  • My C2 is not affected by this bug

0 voters

I do not want to specify the bug - I guess everyone who is affected knows what bug is meant in this poll

3 Likes

The Problem is IMHO not the security code. Something get wrong with encryption.
After i was ready with the wizard - the phone worked, but no WLAN. I restarted the phone second time and got an error: “Error with encryption” Wizard started second time (what never should happened) and after second reboot - i got this never ending spinning wheel.

5 Likes

There are multiple symptoms to the bug. Not all who have encryption problems, end up with a spinning wheel. Mine, for example, is worse. I cannot even insert a security code.

1 Like

I received my phone before this thread was created and the experience was

  1. First I connected it to the charger (because there were earlier reports that batteries had run out during first boot)
  2. The battery was at 34% (or something in that ballpark, don’t remember the exact figure)
  3. Several hours later the battery was still at 34%
  4. I disconnected the charger
  5. I connected the charger again, now it showed 99% immediately. I concluded that the charging display does not update automatically, but now the the battery would be full enough
  6. Booted the device. I had no extra SIM handy so without SIM. Charger still connected to be on the safe side
  7. First boot worked nicely. I chose a 6 digit security code after having read previous warnings. There was a button to go online and register accounts. That button was dead, so I selected “skip” in that phase. Tutorial went nicely (not that I would have really needed it after 10 years of Sailfish usage :slight_smile: )
  8. Saw that the Bluetooth icon was on. I hardly ever use BT, so went to settings in order to disable it. The BT settings page was blank, so I skipped that
  9. Tried to turn on WLAN. The WLAN page said there was a networking error and advised to restart the device
  10. Restarted the device. It went to first boot procedure again. To be on the safe side I used the same security code as before. Encrypting user data reported “failed” and the connect button did still not work, but otherwise the device continued to work nicely
  11. Went to WLAN settings again. Same error, advice to restart.
  12. Restarted a 2nd time. Now it did not go to first boot, but after entering the security code I got a never ending spinner.
  13. Disconnected the charger
  14. Restarted a 3rd time. Endless spinner again after entering security code.
  15. Restarted again. Intentionally entered an incorrect security code. It replies “incorrect” immediately. Correct security code leads to endless spinner again.

In that phase I run out of time and put the phone to the drawer and have not touched it since.

Reading reports above it seems be to be de-facto bricked. Let’s see whether we will get a recovery procedure without sending it in. Well, I did not expect a mature product, so I can’t say I would be really disappointed. Just less lucky than with my previous Jolla/Xperia phones :frowning:

The device is in Tampere, if you need a piece for your debugging I will be happy to take a bike trip to Polttimonkatu.

9 Likes

Hi all, I just wanted to confirm that I received my phone today and I followed the instructions at the top of this thread and had no issues whatsoever. I immediately plugged it into power, although it still had 48% battery remaining. I then started the first installation wizard and picked a 6-digit code, followed by the connection to my Wifi and the login to my Jolla account which both worked fine.

I must say that I was a bit nervous before the first boot up of the phone as I have read other users experiencing major problems during the setup. So I am very glad that I can report no issues on my end. And I was also already able to download and install the first software update. :slightly_smiling_face:

Greetings from a very happy Jolla phone user in Germany <3

6 Likes

it is not mandatory right. the first time i did skip it, the second time i thought: oh why not for the sake of good old times.
once you are in it, there is no canceling
however the problem in the end starts with the language selection on the second boot, after an from my point of view finished installation

1 Like

@Jolla maybe the instructions should be extended with ‘have sim card’ inserted ?
just wondering if that would help
or enable dev mode and use usb tethering in case wifi fails

not sure if that would have helped, just asking

1 Like

I am somewaht sure, that inserting the SIM card triggered the issue inthat my case. The device reboot multiple without one.

The USB lan cable adapter would have been a better try to get an internet connection, in hindsight ^^’

Do you have a plan to boot it up in some hours or days? Or do you want to wait with it until Jolla gives new instructions?

I received my C2 today. It was off, battery level at 57%. I charged it to 92% and then started it.
I assigned a 5-digit PIN code.
I connected the C2 to the hotspot of my XA2, but according to the WiFi details, the C2 only had a limited connection and could not connect to the store or the internet.
I then switched the mobile network on the XA2 to prefer 2G and changed the primary DNS server in the WiFi connection on the C2 to 8.8.8.8.
After that, I had an unrestricted connection to the internet and was able to set up my account for the Jolla store.
After that I switched the mobile connection on the XA2 back to prefer 4G.
I then downloaded and installed the update to 5.0.0.21.
The restart and installation of the update went without any problems.
I then installed the Jolla apps and Android app support.

4 Likes

As I have only once booted up the phone and as it is working without the SIM and by the Wlan my plan is not to try to restart it until Jolla gives some additional insttuction.

1 Like

You misread my post. I had no sim in, so when wlan failed, you are in shit

Got my phone!
Worked so far…but since the upgrade, the orientation is stuck to landscape…any idea why?

Thanks everybody to share experience!

Orientation for me is stuck right after reboot until first lock of device then starts working normally (but in portrait though)

1 Like

Same here, plugged my device into charger. This turned the device on to the language selection, where ic could accept. However a few seconds later, it turned off again due to low battery :frowning: I kept it charging for a while, but when i turn it on now, i only get the unresponsive touch language screen.

i did not yet try a usb c mouse input to bypass this, has anybody tried this and succeeded in a bootable state afterwards?

Non-working touchscreen on first boot is not 100% guaranteed brick afaict, you could try rebooting, if wlan fails it’s pretty much over it seems

1 Like

Some comments on unresponsive touchscreen.

  1. First time, it happened during start of tutorial when it asked for swipe from left or right. Not working, but surprisingly swipe from bottom to up worked and finished that step.
  2. Second time, when it demonstrated Gallery, swipe left to right again not to work. After a lot of swiping everywhere, again surprisingly swipe left to right worked when it was on bottom area, just over the text that ask for this swipe.
  3. After updating to 5.0.21, PIN was not able to enter. In that case, I was brave enough to force reboot by pressing power button for some seconds. The phone already rebooted twice during the process so I was reasoning that the third one could not be so bad. It was OK, after reboot, touchscreen become responsive again. Maybe, it is good that you wait for 5-10 minutes if needed to reboot during update process, you never know if phone is still not processing in the background regardless of what you see on the screen (waiting for PIN).
1 Like