Feedback on Jolla C2

Devices
#460

A thread with title ‘Success / Failure Counter - Pleaase subscribe your experiencer’ maybe?

#461

I’m in the unlucky list, too.
Stuck in the safety code input screen at the moment. The phone turned off in the 1st power-on on the safety code input because the battery was too low. After recharging I was able to input the safety code by USB mouse, and could fiddle a little with the settings. Front and back cameras worked. :slight_smile: I couldn’t set up WIFI. I have no SIM card installed, that’s one thing I didn’t test yet. With no internet connection I haven’t been able to update the OS.

1 Like
#462

Every company has at least 1 shareholder. If a company is not profit oriented, should die cause it consumes resources without being efficient, or maybe you think they are in the Jesus business. Cheap money created alot of zombie companies.

#463

Reposting myself:

Good news, look at the second-to-last paragraph of the letter attached to @NikosAlexandris’ new, debugged C2 (to Finland and back in only 3 days):

“We’re working to deliver recovery mode via over-the-air software update.”

So it looks like once you get your C2 to work, any future bricks should be salvageable without sending it in for repair. At least, once said software update is out.

2 Likes
#464

owners: can you check the Pulseaudio version you have?

#465

UNDER DEVELOPMENT & to be updated

After having received a new device, this is the second experience with the new Jolla C2.

On the device itself

  • The camera lenses making the back side of the device non-flat isn’t great :expressionless:
  • It isn’t gigantic, I guess it depends on the person
  • In short without going to details… it’s not an Xperia-quality device.
  • Gets a bit warm when working continuously with various applications

Boot up :iphone: :on:

  • Pressing power-on and waiting… Doesn’t buzz / Shows Jolla C2 screen
  • Feels slow … ?

First time start-up :new:

  • The translated Ahoy! didn’t stay too long on-display!
  • In Greek it might be correct to literally say Απόπλους! but no-person would ever say this to really shout Ahoy!
  • 5-digit PIN entered twice, encryption completed.
  • Start-up felt somewhat slow.
  • Tutorial felt un-responsive. Made me think to connect again an external keyboard. How ever, it did work after quite some seconds. Is it sure that some well hidden sofware design bug doesn’t slow things down, overall, and makes a use think the screen is unresponsive ?

Start-up/s (after the first time)

  • The time to power on feels to be not the same all of the times and ranges from 3 to 5 seconds !
  • Boot-ups still feel somewhat slow.
  • A reboot might take 60 seconds !

Works :white_check_mark:

Hardware :gear: (it’s all software but okay !)

  • Connection to 2.5 GHz WLAN – could be faster !
  • Connection to 5 GHz WLAN – could be faster !
  • Connection to Bluetooth Headset
  • Connecting to a Linux-box via USB, mounting the Mass storage via MTP, copy-over files
  • With 4G
    • Calling (automatic Network settings)
  • With 3.5G
    • Calling + Receiving a call
    • Sending SMS

Software :feather:

  • Store … seems to work fine
  • Storeman becomes occasionally un-responsive (on/off-topic : misses useful sorting capability)
  • Gallery
  • People
  • Clock
  • Terminal
  • Calculator
  • Calendar
  • Browser
  • Notes

Android applications :robot:

  • Aurora Store
  • Some Android applications installed via Aurora Store (Secure connection) Quick-check*
  • Some Android applications that need a browser will run if DuckDuckGo is available :slight_smile:

Works sometimes :heavy_check_mark: :broken_heart:

  • With 4G
    • SMS sending
  • Camera via an Android app that required to take a photo ! Weird the native camera app does not work :expressionless:

Works yet is slow :heavy_check_mark: :turtle:

  • YouTube …might just have hit the wrong video … ?

Works but is so slow :heavy_check_mark: :turtle: :turtle: :turtle:

  • Swiping first time in the tutorial
  • Setting an ambiance
  • After launching quite a few apps, various native and non-native applications after some time feel slow / non-responsive, even after closing all apps. Restarting the Home screen didn’t help.

Does not work :no_entry:

Hard :gear:

  • Mobile internet connection
  • Receiving calls – however, after quite some seconds, a delayed incoming call screen appeared unexpectedly since the call was long before cancelled from the calling device !
  • With 4G
    • SMS sending + receiving
  • With 3.5G
    • SMS receiving

Soft :feather:

  • Camera

Android :robot:

  • Various Android applications :expressionless:
  • some banking app says it won’t work on jailbroken/rooted devices !
  • important “official” applications won’t run (i.e. post, train) not with the default browser at least !

Opinionated comments

  • 5G (other device/s) does provide better reception overall compared to 4G, it feels.
  • C2 looks promising !
  • C2, however, is not up to Xperia quality
  • Missing fingerprint isn’t just missing out some fancyness. It’s used to quickly verify banking actions, for example. Any other quick and safe way for it ?
  • Banking apps should really be working.
  • NFC missing : how can you quickly pay with your phone instead of tapping an NFC-supported device close to a POS ? Alternatives using a phone ?
6 Likes
#466

If you feel the translation could be better, you can suggest a change on the translation site over here: Translate | jolla-startupwizard | Greek | Sailfish OS Localisation

3 Likes
#467 
,---
| Sailfish OS 5.0.0.21 (Tampella)
'---

[defaultuser@JollaC2 ~]$ pulseaudio --version
pulseaudio 14.2+git9
3 Likes
#468

Would you like to test this Sailfish Community News, 24th October 2024 - Shipping - #31 by mal

2 Likes
#469

Paypal option is nowadays supported.

4 Likes
#470

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
#471

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…

#472

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
#473

Please read this as well. Yes, we do implement recovery but that does not help users who have suffered issues.

5 Likes
#474

“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 ?

#475

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.

#476

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

#477

Thank you for reporting.

1 Like
#478

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
#479

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