Hello Sailors
Today came C2. Order #1633 (sold unit 633?)
At first wlan was not working but after booting started working
Downloading Tampella. Not yet any sim cards in.
So far on lucky side
2 Likes
Got another brick here. Wheel of death when entering security code.
I have the same problem with other applications. Waiting usually helps…
1 Like
I assume the orientation issue? And do you have the same problem with recording video?
No, no orientation problem.
Video recording freezes.
Other applications often freeze too.
Sound output is also missing in some apps.
I assume that these problems will be solved with the next update.
Please do not download and install a Storeman RPM file manually, unless you want to test a Storeman pre-release (this is the only purpose Storeman’s RPM files offered at GitHub have): Storeman’s self-updating will not work, i.e. you will not be notified about newer Storeman releases and cannot download and install them using Storeman.
I have an idea for a workaround in Storeman’s spec file to alleviate this, but you will need to install a newer, future Storeman release first for Storeman’s self-updating to work when Storeman was manually installed.
[Storeman] installer does not support beta releases and since this isn’t even a beta it’s not working as expected.
This is no longer true when using Storeman Installer ≥ 2.2.6 on SailfishOS ≥ 4.6.0, because it utilises SSU’s new release string RPM macros introduced by SailfishOS 4.6.0. Before that this was impossible to achieve: Actually the statement “installer does not support beta releases” was never true, it was Jolla’s SSU and SailfishOS-OBS making it impossible to support cBeta and EA releases of SailfishOS by the Installers for Storeman and the SailfishOS:Chum GUI app.
I plan to update the instructions when I have some time for that.
Yes, I was a bit slow to configure Storeman’s download repository at SailfishOS-OBS for SailfishOS 5.0 (I did that after 5.0.0.21 was released), because nobody filed an issue at GitHub (and I usually do not read FSO-threads about the Jolla C2, because I do not have one), but since then Storeman Installer ≥ 2.2.6 should be working fine on any SailfishOS 5.0.x.y release including 5.0.0.5 (but I suggest to update SailfishOS first after successfully executing Jolla’s initial setup dialogues).
TL;DR
If you have downloaded and installed a Storeman RPM file manually, and you do not fully comprehend or want to avoid the implications not using the Storeman Installer has, please remove (“uninstall”) Storeman (e.g. by executing devel-su pkcon remove harbour-storeman) and use the Storeman Installer.
P.S.: If you experience issues with Storeman or its Installer, please do file an issue at the corresponding GitHub repository.
P.P.S.: See also my follow-up messages Feedback on Jolla C2 - #605 by olf and Feedback on Jolla C2 - #607 by olf.
2 Likes
I have the same problem. Applications are failing to start. I do experience freezes and lags from time to time. I am not sure if that is an error related to the device or just not mature software (second option would not be a problem, software can be updated). I also experienced the non responsive touchscreen during the boot (entering decryption key). That can be “fixed” with another reboot.
What do I really expect from @Jolla is a public available overview which all collected issues. Also a little statement like “please contact Zendesk for returning the device (link to zendesk)”, “we are aware about that problem and we will try to fix that in the next update” for each kind of issue. Right now we need to read long threads and do not have clear answers to every open question.
Do not get me wrong. I am happy that Jolla sell another device and probably it is not even their fault. On the other side the communication could be really improved. Jolla really needs to work on that as well. Even if it is just a list with an entry “Problem acknowledged, we are investigating it”.
A list could be look like that:
| Problem | Status (Acknowledge|Fixed|Fixed in the next update) | Related forum posts | Recommendation |
Another point is that I am disappointed with the quality of the cover. The holes in the cover are not milled out properly, so that the charging cable, for example, does not fit in. Too bad. I think the quality control should needs to be improved a lot.
Let’s hope everything will be fixed and we can enjoy our new devices.
2 Likes
Could it be that there is a significant lag / delay / slow-down overall that feels like the screen is non-responsive at all ? In my (second) experience (few posts above this one) I note that the first time going through the tutorial and the moment to “test” swiping, the screen felt unresponsive. Maybe it’s just that things are racing against each other, some messy start-up sequence that doesn’t things flow snappy.
?
@Systematics hoping is one thing. Good programming and proper QA is what we mostly need now.
1 Like
All what can be fixed by an reboot living in software.
“or just not mature software”
Here is the communication from Jolla very clear: the currrent OS is in a heavy development state. Usually such a version is not shown to a user because users love to discuss trivialities but not the current point of development.
But the next release candidate will coming. The Jolla people working hard to finish an EA (early access) release if you know what that is (I think so of course).
Yes, I am aware of it that is a development device. Irrespective of this, however, we have several problems with the device. At the moment we (the users) are not sure whether it has to do with the hardware or just the software. We need to clarify this. And for doing that, we need to collect the issues and get an acknowledgement.
C2 h/w specs are not great, do not expect SFOS improvements to hide that. I know it’s early days but there is no comparison C2 vs xiii.
2 Likes
(Would be nice if you link to the source of the communication you mention.)
1 Like
If the hardware wouldn’t be fit at all, it wouldn’t be in our hands today. It was tested, of course, in early stages. Just not with SFOS 5. Of course, it’s a moderate device but it would be also unrealistic to think of it as a very poor and nevertheless selected as a community device. Once SFOS 5 matures, it’ll be okay I guess.
2 Likes
If the hardware is not sufficient then it shouldn’t be classed as a reference device, my understanding is this phone should be everything Jolla has identified to be required for a phone run Sailfish exactly as it’s programmed to be. Of course not right now, but the effort should be to optimise every single bit out of it.
Would be a pretty large reputation damage if the premise was not true.
3 Likes
@pmelas
What’s the base of your expection about the hardware spec’s? An announcement from Jolla? Thanks if you have you a link for me.
@econdebachs
“be classed as a reference device”
I can remember me on “a reference device for developing”. When the SDK for SFOS 5 is out I will test it. For now the C2 looks fine for developing.
see the last Community news from last week: Sailfish Community News, 24th October 2024 - Shipping. In the text the current SFOS 5 version is called “RC2”, just a candidate:
Sailfish 5.0 release has been on CBeta for two weeks. In practise, there’s a second release candidate (RC2) available and this 5.0.0.21 looks like the first update candidate for the Jolla C2 devices. Rolling out to the early access subscribers would likely happen with third release candidate – let’s see how it goes but this is the current thinking.
3 Likes
I agree on the difference of specifications. But that does not mean the C2 will not run as expected on a daily basis. It is clear that SFOS5 is a major refactoring of the software. Those familiar to such processes can understand what it means and what it looks like, most of the times, in the beginning. It’s a prototype, in many ways ! Those who are not familiar with the term and the work around it, are right in their way to think differently. But they can at least give a good read of the early announcement/s of the device, for example : Jolla C2 Community Phone deliveries and think of it as a food-preparation-process that is not in the very beginning but surely not ready to serve.
4 Likes
I think these first “versions” should not be considered as RCs. They are just in-between development phases. A release candidate should have at minimum :
- Working phone : calling and receiving calls with any G (2, 3/3.5, 4 and 5 which the phone unfortunately doesn’t have :-|)
- Functional messaging : sending and receiving SMSes
- Functional internet connection : WiFi (2.4GHz or/and 5GHz) + Mobile internet
- Basic native applications + some basic Android applications (like another internet browser for example)
1 Like
Even better, if it’s the reference device for development all the effort should be to improve the system to demonstrate what can be achieved with it, is not just a toy, is a showcase.
I can see the C2 being the device Jolla takes to shows, to try to get customers and corporate contracts, it’s gotta be bulletproof at some point to get any credibility.
Of course my comment is only in hindsight - and does not help with the currently sent out devices. I was alluding to the fact that recently, since Android 11 I think, there is no separate recovery partition and there’s a turning point in the boot image init code that initializes either normal boot or recovery boot. That is now just disabled in hybris boot, if I understand this correctly.
With the current state of C2 / Unisoc, not being able to enter fastboot mode as an user, triggering that boot recovery codepath (and implementing it) at init time could have helped.
3 Likes