4.6.0.15 (not 4.6.0.25)!
P.S.: Please pay much attention to provide correct advice, otherwise such advice may be outright evil, because it frustrates newbies and may result in broken installations (not in this specific case, because 4.6.0.25 is luckily just invalid).
Hey olf nice that you are here to help, but maybe you can tell me how I can get chum installed and started under the C2 … The storeman installed chum, but I get no app starter, when I try via shell to start it, it claims that it has not the proper start parameters and I can’t find any documented start parameters … I tried also to install just the rpm from github, but same result … Can youmaybe help me?
Can you start chum from command line?
maybe you need change also the chum repo version in the repository (inside /etc/ssu/ssu.ini) to get chum installed correctly.
its linux, guys! Use command line!
Done.
Also done, implemented by Storeman 0.7.1 and 0.7.2-release2. Mind that I accidentally broke exactly this new feature in Storeman 0.7.2-release1.
Storeman Installer works fine now on any SailfishOS release (≥ 3.1.0, that is) and should continue to do so with future SailfishOS releases (e.g. 5.0.0.x, 5.1.0.y etc.).
Thus, as originally stated:
No, you installed the SailfishOS:Chum Installer from OpenRepos by the help of Storeman.
The SailfishOS:Chum Installer fails, because the SailfishOS:Chum community repository is not ready for SailfishOS 5.0 yet, as you can see in its log-file (RTFM) and its systemd-journal entries.
… I tried also to install just the rpm from github, but same result …
If you pick the right one, that should work.
Can youmaybe help me?
As Storeman / Storeman Installer and the SailfishOS:Chum GUI application / its Installer do work as advertised in their corresponding documentation (i.e. absolutely fine now for Storeman / Storeman Installer and with a manual workaround for the SailfishOS:Chum GUI application) I will mute this thread for me, because I do not own an Jolla C2.
Additionally, all questions here WRT these two topics were answered by me in this discussion thread, even though these answers were already provided in the corresponding documentation.
Actually I perceive asking here at FSO, because it is easier than following web-links and reading documentation first, as quite rude!
If you have read the documentation exhaustively and you either do not comprehend the documentation (which would constitute a flaw of that documentation) or are convinced that a technical issue exists (which must be reproducible), please file a proper bug report at the correct location (i.e. at the issue tracker of the appropriate GitHub repository), as advised in the documentation.
In general, chatter in this forum (usually just “does not work for me”) is never a proper bug report for a third party software developer (i.e. ≠ Jolla).
I hope that experienced FSO and SailfishOS users will provide newbies with a link to answers already provided at FSO and / or (even better) the appropriate user documentation at OpenRepos.
Thanks!
P.S.: Please bear in mind that the current SailfishOS releases for the Jolla C2 have the status of what is usually called a “cBeta (closed / community beta)” release by Jolla, i.e. a “early beta” (“EA (early access)” releases are the betas after the cBeta releases and before the first “GA (general availability)” release of a SailfishOS release X.Y.0).
Furthermore, the current batch of Jolla C2 phones was explicitly advertised as being developer devices, hence it is not at all surprising that many things do not work. Yes, the phrase “SailfishOS as it is meant to be” is laughable, but that is a dire tradition of Jolla marketing communications; I assume they meant “We hope that we will be able to deliver a SailfishOS experience as it is meant to be on the Jolla C2 in the future” (i.e. “soon™” in Jolla’s parlance).
Yesterday the C2 arrived. It had 80% battery. I plugged the charger in and after a few hours I tapped twice on the screen to see if the battery was full. Setting up went smooth, I sat close to our router. I choose English. Wifi is ok.
Not everything works as it should be (apps from Aurora and F-Droid don’t show up, the pulley menu doesn’t have a push, no incoming calls, etc.) but I expect all this will be solved in the future. I did not yet install Sailfish 5.
To my amazement the browser had Google as default (For years I use Qwant or Duckduckgo). There is no list of search engines other than the big four. The thumbnails are new. In search (Bing) the text is small while I had set the text in setting on huge.
For me the C2 is a set back, not because of the omissions in the OS, that are expected to be temporarily, but because of the hardware:
the sides of the C2 hurt my fingers so I cannot hold it longer than one or two minutes and the other nuisance is the sound. The sound is not suitable for persons with damaged hearing like me. Hearing aids don’t make the sound better, on the contrary. I realise how lucky I was/am with the text adaptation, the rounded sides and the excellent sound of the XA2 and XA2 plus.
This is why I want to return the C2 on my cost. Or someone else in the community is interested?
There are some solutions to your issues:
Setting the network to lower then 4G resolve calls ability. At least before VoLTE packages apear.
DDG apears in the choice after first visit of their homepage.
Apps do show after upgrade to 5.0.0.21, as none reported contrary AFAIK. Reboot might help too.
Maybe the apps do show but in my case i can`t install any of them. I get ‘invalid apk file’ error.
I’ve returned mine today, unpopular opinion to follow:
If we were in 2015, Microsoft just cancelled Windows Phone and Jolla was the only good alternative then I would have kept it, but truth is, it was far too niche and limited for me and that’s fine, I accept the fact I’ve relied too much in the giants and that’s my fault but I’ve got far too many apps I use daily and I kind of need them now.
However I do struggle to see how long term this will be viable, we rely so much in our mobile phones, from Banks, to home appliances, even our cars need an app to do stuff!
I wish everyone that bought the C2 smooth sailing and that glitches and issues reported get resolved so everyone ends with the device they wanted.
Cheerio!
It would have been better if Jolla had partnered with Gigaset. This would make devices more expensive of course, but also more comfortable (rounded edges, not too big) and definitely more sustainable.
Yes the GS290 was very fine! Unfortunately mine broke abt. a year ago.
I know, ‘rebooting heals all wounds.’ 
I have done it so many times.
I didn’t also like C2 dimensions, it is too big and too heavy. It is community phone i will play with it. But I will still use my Xperia 10 lll as a daily driver. I like Sonys size. It’s very good to my hands. Sailfish also is working on it quite well. Maybe I will buy next Xperia 10 iV.
Offtopic: I’m wandering how big and heavy phones are these days. I have thought technique should go on. I haven’t been phone shops couple of years and I was very surprised of big and heavy phones.
Hi olf and sorry for bothering you with my problems, but I aldo want to give you a big thanks that you replied to my questions. Yes I’m not a native Enhlish speaker and maybe I didn’t understand your documentation or not have seen that you already figured out something for SFOS 5, now I know and I can just apologize if my questions infuriated you.
I keep finding feedback topics in the Forum. This was my feedback posted earlier this week.
This is the feedback topic about the C2 phones, the topic you linked was a call to fill a survey Jolla set up couple of months before the release of the C2. I don’t know why they haven’t closed that topic yet.
Indeed, I got a new one. Well, I also returned practically a New one back – opened and used for a short period till it was locked.
Received my C2 a couple of days ago; setting it up was a no-brainer and I migrated all my stuff from my old Xperia XA 2 with no issues.
Overall the device feels great and I’m actually pretty happy with its dimensions although I always considered myself a smaller-phone kind of person. It’s much easier to hit certain links and buttons in the browser now, and of course more space for app icons and video.
It’s still quite hard to find suitable cases and accessoires for the Reeder S19 format.
Some of the known issues affect me as well (touch screen not working on boot) but my main issue right now is that I have to explictly switch networks for making mobile internet and making/receiving calls work respectively, which is quite tedious.
Sending SMS/MMS does not work. To be fair, this is most likely related to my mobile provider issuing new SIM cards for 5G as I’m getting the same behavior on Xperia XA 2 with this very SIM.
One more thing: A number of apps have not made the switch to arm64 yet, and hence you won’t find those in the Jolla Store. The good news that I found forks for most of them, so have a look at openrepos, download the latest .rpm, devel-su and pkcon install-local.