With official support, the company offers money back or repair.
In addition, they open service moments for the community.
Don’t complain about having to do it yourself. If you want warranty like with any other company, open a support ticket like with any other company.
Feedback regarding camera in the browser:
Camera in browser works, but selecting a camera is cumbersome. You get to select between “Droid Front camera”, “Droid Rear camera”, “Droid Rear camera”, “Droid Rear camera”, and “Droid Rear camera”. One of these four is the normal, one is macro, one is fish eye… one is ??? Don’t know which is which!
I just configured my C2. It looks like everything worked - first boot, connecting to WLAN, logging into Jolla account, going through the tutorial. The biggest lag came during the tutorial, which showed how to unlock the phone (swipe left, swipe right) - I think it may be because the phone was downloading apps (in the background) that were marked for installation during the first power-up.
Then I downloaded the update from 5.0.0.5 to 5.0.0.21 and enabled developer mode.
At first sight, everything works - WLAN, Bluetooth, Camera, Audio recording. The only thing I didn’t check was the SIM card.
The phone came to me on Monday, so after reading all the forum posts I had a slight stress
I think the answer is obvious, select the droid rear camera! See that’s the kind of qwerks and bugs I expected not the being unable to unlock it.
The final read camera seems to be the macro cam, that’s what I needed in this case anyway
Also, the camera list exposed to the web page itself seems to be just base64-encoded strings without any human readable meaning.
This is exact what Jolla offers when you contact them over Zendesk.
Of course, sending the bricked device back, when you have waited for it so long is very disappointing, but at the moment better solution doesn’t exist (or could not be offered by Jolla).
And of course, many of us know, how to reflash device, when there are clear instructions and right Software-Parts.
But it is like it is. Lets hope Jolla will reflash our devices and send them back fast, so we can enjoy SF5!
It’s not about me, but about the policy of Jolla as a company and of course about the future of the OS, about how to make it attractive and viable. Giving money back or returning the purchase for repair is a normal legal procedure.
C2. Arrived yesterday, opened box, language screen was on! Put on charge and left it as found overnight. In morning selected english uk, set 6 digit pin, set pw for hot spot (my 10 III) even though home wifi visible. Continued without problem including tutorial. Went to system and update. Downloaded Tampella …21. Took a long time! During this got ‘unable install android app support’ Skipped backup. Installed update …21, ok.
Changed to home wifi. Ok. No sim yet.
Installed app support from Store, now ok.
Noted Aurora not on app grid but my app page shows installed.
First boot, same. Reinstalled Aurora again, same but then after long delay icon appeared on app grid.
Installed Fdroid ok and that gave updates to Fdroid and Aurora. Ok.
Continued various settings.
No finger print sensor is disappointing.
Believe me: You are lucky. No fingerprint is the smallest problem atm.
Add me also to the list. It is very sad that there is no possibility to do an hardware reset.
You are quite right about publicly traded companies limited by shares - it is all about the money. And you are right that there are other types of company models - companies can be set up and limited by guarantee, or they can be set up as community interest companies (and there also other specialist models across different countries) - but the vast majority of them are companies limited by shares.
Even very small, private (i.e. not publicly traded) companies set up in this way have shareholders. My own law firm is a private limited liability company. There are just two shareholders - myself and one other, and we only have one share each (and therefore each own 50% of the company).
Jolla is such a company, and if you look back to between, I think 2018 to 2023, the Russian telecoms giant Rostelcom was the largest shareholder in Jolla’s holding company. A lot of the hiatus in Jolla’s progress in those later years was when it was trying to restructure to get a more balanced shareholding, and therefore ownership structure, to gain more control over its future. So, even in the case of Jolla, its the shareholders that call the shots - and when they put in large amounts of investment (as Rostelcom did) they do this looking for (a) some control over the direction of the company they are investing in, and (b) a return on their investment - whether this be financial or of another form.
I don’t think this is specifically a C2 problem - I get the same thing on my Xperia 10 iii running the latest 4.6 release when trying to access the camera from a web browser - so I think it is just a bug in SFOS generally which has yet to be addressed.
Could somebody with the right level of forum authority split my post out into its own thread please?
I’m still adding people to the list who have the bricked phone problem when they ask me to, or when I come across posts from them saying that they have this problem, so a split out list will be more obvious and easily accessible and may help Jolla identify who is affected by this issue (maybe so that they can proactively contact them either with advice or to tell them how to organise the return of their devices by raising a ticket on Zendesk).
Thanks in advance.
A thread with title ‘Success / Failure Counter - Pleaase subscribe your experiencer’ maybe?
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. 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.
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.
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.
owners: can you check the Pulseaudio version you have?
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
- 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
- Pressing power-on and waiting… Doesn’t buzz / Shows Jolla C2 screen
- Feels slow … ?
First time start-up
- 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
Hardware (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
- 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
- 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
Works sometimes
- With 4G
- SMS sending
- Camera via an Android app that required to take a photo ! Weird the native camera app does not work
Works yet is slow
- YouTube …might just have hit the wrong video … ?
Works but is so slow
- 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
Hard
- 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
- Camera
Android
- Various Android applications
- 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
- …
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