It has been my daily driver since Jolla1. I followed togetherJolla and this forum. Not techsavvy, only humble beta tester. I still love the OS, but I must say that after so many years it still is not a viable alternative because it isn’t stable and not everyone is able to flash etc.
Ideals are useful but some realism is also needed.
About ‘community’: this can refer to many different groups and organisation (religious, communal living groups, sects, etc.) The last decade or so it is often used by commercial institutions to attract supporters or customers.
Exactly, and this is the cause of confusion and disappointment.
Storeman:
I received my C2 in Switzerland. As always with customs fees.
Battery charge 40%, started C2, ran the tutorial, took the first steps and installed update 5.0.0.21. My C2 works so far, but often gets stuck (app doesn’t respond, wait or close).
Some app functions are missing.
There are no answers on sfos forum.
No audio output on the Kaffcountry radio app (Great Circle Media).
No audio output with the app Chime me big ben free.
Nevertheless, I’m slowly starting to enjoy my C2.
Try reboot. After that, audio worked for me…
I wouldn’t say Jolla is intransparent. Jolla only isn’t very reponsive. And though it would be better if Jolla was more responsive I am not blaming Jolla for the lack of responsiveness because of their limited resources.
I am super happy that I can use my Xperia 10 iii with SFOS as my daily driver with everything I need. This is nothing that is easily achieved and the community alone would not have gotten so far - look at UT
So Jolla and the community may be some sort of a symbiosis
My c2 phone started back to the “mothership”. Zendesk responded within 1 hour and provided the most correct alternatives possible in my opinion (someone else has already commented on this). I have great trust in the company, so I did not ask for a full refund, just to send a device after repair. My story was simple. Nokia n9 followed Jolla 1, then I used BlackBerry phones, but I got an AquaFish to have the Sailfish experience. Then came the Android line, unfortunately I only tried Sailfish OS Xperia devices. Now that my device started back up, I ordered an Xperia 10 III from a place near me to flash Sailfish on it. I did not lose my trust in the company. Although I did not want to return the c2 phone, after my letter written on the official bug reporting channel, I still felt that this was the best way for the c2 to be my faithful companion later. Because I really want it to be good and even if the beginning was unpleasant, I think it’s just a matter of time and it will mature. There needs to be an alternative in the mobile market. Not only because IOS or Android wouldn’t be good enough, but also because a different approach would move every part of the industry forward. Who would have thought at the time that the gesture-based control of WebOS or MeeGo would show the direction so much that a few years later it would become a basic feature on most smartphones? So I’m confident that when my phone comes back from Jolla, I’ll join the ranks of satisfied users. As my story progresses, I’ll share it with you.
No, no sound output even after a few restarts.
Yes via the website, but not via the app.
This.
After trying all the unisoc fastboot entering methods this is my conclusuon too: you need a host equipment.
This is very sad. Jolla should implement a recovery mode on volume up… Otherwise it is not sustainable. What happens with an unopened C2 after 2-3 years? You dont own it…
Thanks for info! Do I understand it right, no flashing via usb possible but special adapter necessary that connects to some gold plated pads on the pcb? Therefore necessary to open the device for flashing it? Or special proprietary usb adapter and program on computer?
that means, that the phone need to be opened.
i think its some kind of special USB C Cable with additional electronics, which puts the phone in the flash mode.
So there could be a chance to recreate such an adapter with Raspi or Arduino or by software emulation? The community needs this option at least to do development at home. Or simply buy such adapters if possible. What about a collective order?
Jolla surely would have it easier to get 50 or 100 such adapters from Reeder and distribute it to us than each of us alone.
There should be an easier way to flash, or at least wake the device in recovery mode as recovery image is there.
If not and it was done on purpose Ill start to loose my already shaken confidence in Jolla
Thats only what i think it could be. Maybe the reality looks absolutely different. We dont know yet.
But what we know:
Something prevent Jolla from sharing clear flash instructions and firmware files.
I hope some of our Finish friends like @JoshStrobl who will be in Helsinki for the “Flash orgy” can look how the reflash procedure looks like and what is needed…
The majority of companies don’t have shareholders. And a lot of companies with shares are not publicly traded. The risk of “it is all about money” is unavoidable for publicly traded companies, but very much avoidable for other companies.
I suspect otherwise, but, that something could also be time. Would you risks sending this powerful tool to customers without really testing it? Having repairable C2’s being send in is better than tinkered dead bricks being send in.
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.