,---
| Sailfish OS 5.0.0.21 (Tampella)
'---
[defaultuser@JollaC2 ~]$ pulseaudio --version
pulseaudio 14.2+git9
3 Likes
Would you like to test this Sailfish Community News, 24th October 2024 - Shipping - #31 by mal
2 Likes
Paypal option is nowadays supported.
4 Likes
Rainemak. You’re popping up in the conversation not even mentioning the “bug” that affects almost 2/3 of the devices that company you work for just sold.
is some kind of factory reset or flashimg by the end user is evwn planned? Is something even? Flying to Finland to reflash the device you spend money for doesnt seem like a solution rather like a joke.
We want to support Jolla as best as we can, so please do the same. Support.
2 Likes
You can find the answer here in the forum. First there is the solution discussed often. Second you can read about a new solution: Jolla C2 first time use instructions - #136 by nthn
And third: have you a source for “almost 2/3 of the devices”.
There are many emotions on the way here about a pure technical topic…
There is a counter some way up. And i said almost 2/3
Wont be explaining myself as I fell I have the right to be angry.
And over the air update for a brick? How can I update over the air when Im stuck with endless spinning circle after entering a 6-digit code that I set?
1 Like
Please read this as well. Yes, we do implement recovery but that does not help users who have suffered issues.
5 Likes
“There is a counter some way up. And i said almost 2/3”
You mean this: Jolla C2 first time use instructions - #65 by JoOppen ?
I follow the forum on hourly basis, I did all the steps recommended to not brick the device but it wasn’t helpful. Couldnt even do the update on first boot as wifi nor mobile data wasnt working. The device I get was deemd to fail.
On arrival battery was flat, I connected it to wall charger. It charged for 2-3 minutes, boot itself up without any of my doing. Than told battery is flat and turned off.
I needed to wait for device to run fully flat again. This allowed me to do first boot. But It all went as I explaing at the start of this post.
Yes. And the number was changing. But why this is so important to you? Even if 1/3 of the devices were affected it is still bad. Very bad
Thank you for reporting.
1 Like
Maybe he means the list I am maintaining here:
The current number of reported bricked C2 phones on the forum is currently 53, although this is probably understated as some users suffering this problem will probably go directly to Jolla via Zendesk or whatever.
I have no idea what proportion of those C2’s that have been shipped, delivered and setup (or attempted to set up) this number represents as I do not have access to that information. What we do know is that a fair number of C2’s have been setup without this problem occurring at all.
At the current time Jolla have provided no update on why this issue occurs or what causes it. The current advice seems to be to return your bricked phone to Jolla for a replacement or a refund by logging a ticket on Zendesk (though this has not been widely publicised).
1 Like
Of course the update won’t fix the phones that are broken right now, but after sending your device in to get it fixed right now, which apparently doesn’t take very long, and after said update is out and you’ve installed it onto your device, you’ll be able to fix a non-booting device yourself without sending it in, as has previously always been the case.
Jolla messed up, we know. They’re also (actually) working overtime to fix it. Most people with a broken device will probably have it fixed before the last customers receive their C2. In fact, NikosAlexandris above got his device fixed and back in his hands in a shorter timespan than my post office has needed to decide which day they’d deliver mine (supposedly tomorrow).
5 Likes
I understand I should swnd the device in. The device that was late by few months. Shipping took almost two weeks so counting over, yet another month to get the device back and at this point no guarantees that it would even help. Sorry but Im loosing confidence for this device to turn out anything better than all the xperia’s. Sony devices are at least not a brick and far away better than community device and Sailfish “as its meant to be”
3 Likes
I agree with you, for such a niche product coming from such a small company and so reliant in the good work of the users, a root cause analysis should be well underway by now. And people who spent their hard earned money deserve at least a small explanation of what’s happened.
My advice to Jolla if it’s really aiming to conquer the automotive market (I’m a quality assurance engineer with iso 9001 and iatf auditing certificate) please work on your Quality Management System and communication, if a supplier did this where I work I honestly don’t think you’ll stand a chance to get any more work nominated.
5 Likes
Starting of programs and working with thems is very slow. If you are patient, most works finaly. It seems that accessing files could be a root cause. Hadn’t time for debugging. It is independent of the app or whether it is a native or an Android app.
e.g. sending pictures in Whatsapp needs sometimes several retries. In the first minute after Whatsapp starts, it says that it hasn’t enough disc space. When clicking on the message, the available space jumps from 0 to 108Gb.
Camera works, but sometimes it needs a minute or two after pressing the button. (it just hangs for some time).
My current hypothesis: SD card with BTRFS.
No, you shouldn’t just send it in. You should, as noted in many places, open a ticket at zendesk and wait for instructions. Which will tell you how to do.
2 Likes
This is what I mean but wrote in shortcut.
I would like to be assured that other side knows Im returning the device.
1 Like
Then do it! The sooner, the faster you will get a working device.
1 Like