36 users now with bricked phones.
Interesing stats. ~34 bricked devices and only 34 people voted on [Release notes] Tampella 5.0.0.21 for Jolla C2 while managing to upgrade one way or another … definitely missing positive feedback since it should be in the 100’s indeed.
There is no way to get reliable data with polls in middle of long threads, most will miss it, but the 1.8% estimations are surely wrong, more like 5-20% but it’s all just guestimations, only jolla will know the exact number (and it also will be approximate as some c2’s will just join a collection of never unpacked j1/jc/jt on a shelf), but it is definitely not a minor mishap
Fun with swap partition at the C2. This is a screenshot shortly after booting up the device. No other application opened then crest. The system feels laggy because of it swaps without using the RAM.
9 Likes
The next issue is the device encryption during boot. Sometimes the screen did not respond. So you have to poweroff the device and hope for the next boot.
Well, maybe not everybody who upgrades votes on Jolla’s poll - I never have. And there’s little point counting the users with no problems as they’re fine and need nothing fixing do they?
But if you want to check my counting, these are the users who have reported bricked phones across the three threads mentioned above.
j24
speactra
oliverapps
corho
RXShorty
Nordbourgh2
kraemera
ioanna.papadopoulos
pawel.spoon
minnist
econdebachs
Allstar12345
sviscapi
explit
razcampagne
marcogreggi
ugeuder
NikosAlexandris
mjun
Ahtisilli
eson
adrian.duermueller
Pauly47
WilliePre
temone
ljimonad4iks
archon
Dr.Recor
DenHerder
coldways
AsinineMonkey
ryks82
hopey
naokysatoh
ThijssjihT
robertcata73
Even in the unlikely event that all 1,000 C2 phones have been delivered and, even more unlikely bearing in mind what has happened so far, the setup went fine for the remaining 964 of them, that’s still a total failure rate of nearly 4%!
EDIT: We can now add to the list:
n900
xneo
Ulrik676
Hemuli
jeschwarz
mbrazi_1
francescodb
Ride92
marcoferrigno
kalesaa
josef.macko
sneevus (got further than most with this problem but has no networking and possible corrupt filesystem)
oiliviosu
thahne
david.b
hekkup (situation similar to sneevus but now unusable)
erichiardone
Roggerrooster
Henuka
Aurelienlefo
cartron
calinutzzz
Xavier_OM
epninety
treeman
croqueteer
nerfiaux
emchella
danield
affe_null
which brings the current total of users reporting bricked phones on the above mentioned threads to 66.
16 Likes
And that’s 1000 coupons, some people bought that with PayPal and can’t buy the device with it, some just haven’t bothered yet, it’s almost guranteed double digits (that is assuming shipping out is done, but no new ‘got my tracking number!’ posts suggests that)
1 Like
I am still waiting my tracking number. My order was #1651
1 Like
Yeah, the only sane thing to do would be delay that, no point in shipping bricks
Edit: and for more speculation, judgning by the order number not even half has shipped, so assuming a bunch still in transit the number is probably closer to 20% rather than 10
1 Like
I had an idea now. If someone has a usb-c to RJ45 adapter one could connect the phone via a LAN-cable to the router. I have one and tested that on the xperia 10V or 10ii and it just worked. Don’t know if the c2 has usb host mode though.
Jolla knows exactly about the successful activated C2 phones, out of the logs on their server.
Jolla knows exactly the number of phones shipped until now.
Jolla doesn’t know exactly how long it lasts until they arrive.
Unknown is only the number of people who simply wait what will happen now and/or don’t respond.
Which gives 0 information for devices bought as collector pieces to finish j1/jc/jt collection, who knows if they have wlan working if they were never even unpacked, but yes, they get much more detailed data than any polls can give us
Did not work for me. Seems that networking is broken in that state.
I am happy to see that Tuta’s mail and calendar apps now work in Sailfish OS 5.0.0.21 (and ESR 91).
add me also could not connect to internet (wlan) resulted in spinning wheel of death. Great
Mine has arrived with 70% battery charge, I fully charged it first. Initial setup and upgrade run smoothly. One thing I find discouraging is the performance of C2 compared to 10 III. Many operations take far too long to start resulting in a spinning circle and often failing to start, eg add a Nextcloud account, or login from the “SFOS forum” app.
Is that because of SFOS v5 or weak h/w specs?
1 Like
There are issues with 3g/4g/wifi connectivity, I only managed to get nextcloud added on 3g in the end, sfos forum viewer requires reboot after install for login to work, nothing new here, weird thing is even with working nextcloud account the backups would not get recognized, had to manually copy latest one to sd card and rename from …tar.gz to …tar and then it worked finally
UI seemed super slow due to 100gb+ of data on sdcard, some android indexer is going ham on that, after disabling android app support UI speed seems fine, but still bit slower than xiii
1 Like
I expect most of the s/w issues to be fixed in the next few releases, but I do not know if h/w is capable enough. On the positive side, the camera seems to be better than xiii, including power consumption too. I think I will keep using my xiii for the time being.
Yeah, until they fix incoming calls and outgoing sms when on prefer 4g (not even volte) it’s a sadly non-daily-driver (I mean if you have 3g in your country it can work as at least those seem fine, but who knows if it’s 100% or the 1-2 test calls/sms I made were lucky, it needs time that’s for sure)
2 Likes
Another one. Add me to the list