Yes you’re right. Just tested 4G → 3G myself first time and it drops down to 2.5G (Telia) 
Thank you @Jolla. You sent me a phone with a non working OS.
Can’t get pass my, as always, 6 digits PIN, after first reboot.
- Boot up went fine.
- Language selection fine.
- PIN input fine.
- WLAN setup didn’t work, so skipped that.
- Nocked out tutorial.
- WLAN again, touch screen not responding.
- Reboot.
- Here I am, cant get pass security code.
All I can do is shut down.
There better be a way to reflash…
Another one exactly the same as many…
12 Likes
Exactly the same as mine…
Can’t believe this failed so badly, so quick 
4 Likes
How many times have you tried?
I have this sometimes on the X10iii, but code is accepted after 1-3 reboots.
2 Likes
How about 10-15?
1 Like
There actually was an quick error message on first reboot. Something about encryption not working.
I finally got mine. No serious issues yet.
I only had to disable and reenable the SIM to be recognized. Much of the setup and tests still to do!
1 Like
Genuine question here, worse case scenario I assume customer rights still apply for a beta product? I suppose they could not refuse to take back a defective item if indeed some of them just brick?
I bought one a few years ago. Amazing device. Browser doesn’t work, only mobile functions on 2G, that’s it.
They do still apply. The product has to work as advertised, and therefore the basis on which it was purchased. If it was indeed advertised as a beta product at the time you placed the order (i.e. and not afterwards) then you should expect some smaller things not to work initially, but even in this case it would still need to have basic functionality working reasonably well. As a customer buying a consumer product (a phone) you can expect that the basics were properly tested by Jolla, and therefore working out of the box as advertised, prior to them making it available for sale.
1 Like
Almost exactly same experience for me.
On top of those, device gets stuck on lock screen after inputting security code (9-digit code) It does shutdown from power button.
Also said some issue related to encryption on that boot when I noticed that wizard started again.
1 Like
Yes, exactly same for me.
I have no idea, but knowing Jolla, I doubt that they would.
1 Like
To find a solution in peace, @Jolla should reveal how to reflash the device, then find the bugs and publish a new flashing image.
8 Likes
Ideally, the images should be available in the Jolla Downloads, but that’s up to Jolla to upload 'em. Until then, there’s only waiting.
1 Like
If I’m not totally wrong, manufacturer are flashing multiple units at the time, and yeaa… things can go wrong. It might be that we are the unlucky ones, that got what we in Sweden call a ‘Monday Copy’.
1 Like
Well, we could open a ticket at Jolla help desk, but I suggest we wait until Jolla crew tell us what to do. Maybe monday…
I’m pretty sure someone sees this.
1 Like
Jolla should probably stop shipping any further C2’s until they know what the problem is and how to fix it. It will be far cheaper for them, and a better experience for their customers, if they fix the product at source rather than have to deal with returns if that is later found to be necessary.
If these problems are widespread, and due to a serious/basic bug(s) in SFOS 5.0 and/or hardware adapdation of the Reeder phone, rather than an isolated fault in the production line process, then its likely that the C2 was released too early without proper testing.
4 Likes
Yes… but we usually call it QC (Quality Control). 
Precisely. Patience is a virtue after all, and considering that changelogs for new release of 5.0 is out, image will be out in short order I’d imagine.