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
.
Second all of this.
The key aspect that differentiated the Jolla JP-1 and Jolla C from the other official devices was working “Doubletap to wake”.
I think there have been screen issues on all other devices that prevented enabling doubletap to wake.
Sooo, now that the C2 is “missing” a fingerprint sensor, do we have working doubletap to wake for convenient wake and unlock?
No, a fingerprint sensor was not part of the offer of this development reference device. But maybe we will see more fancy Reeder devices with all the toppings missed
I am missing the notification LED, unfortunately Sony has also removed it in later models.
Two SIM cards and a slot for microSD is definitely a plus.
I am still not happy with the size of the C2 (it is a bit better without the bumper cover, but still to large to fit my pocket) and I plan to use the Xperia 10 V 8GB version as my next device.
The browser is able to display more content, but unfortunately, it still crashes a lot more - and I am not even using the C2 as my daily driver.
Personally, I think the Sony 10 series is the better phone hardware wise. It cost roughly the same (in its newest, not yet supported version, but without the sailfish license, this comes on top), but has better hardware specs.
No, only the fake double tap that you get if you enable the LPM screen (the one where the screen shows the clock when you take it out of your pocket, where you can then double-tap to ‘fully’ wake the phone). Edit: this.
I am, in fact, using it as a 7 inch tablet now. Hopefully true Jolla x Reeder tablets will be on the menu in the future - the good thing is that they wouldn’t require any work on telephony like VoLTE or 5G, they ‘just’ need a hardware adaptation.
I can confirm that commands to enable LPM screen work just fine on C2.
I had some issues with enabling mce-tools on Sony 10 III (described here), but on C2
pkcon install mce-tools
works as expected
So, it’s been a couple of weeks since taking delivery of the C2. After charging the phone and powering up I was immediately notified of an update - downloaded and updated successfully.
First impressions -
Compared to the Sony, the screen colours are washed out and not as vivid.
I was constantly getting hang ups when using the Pully Menus, strangely enough installing a 256Gb memory card fixed that. Coincidence?
Some Store apps need updating - Meecast won’t save it’s settings. You have to set up locations again after a restart or shut down and can’t seem to get the events widget working at all.
I can install the ChumGUI Installer but there’s no icon, even after a restart.
Second OS update installed fine.
App Support seems to be integrated better IMO.
Haven’t tried a SIM Card yet, that’s the next stage once I transfer/set up contacts and accounts.
I’m not a wizard at SailfishOS, not as much as you lot, but I’ll give feedback and I get by with it and prefer it over Android or iOS.
Early days for SailfishOS 5 and I’m willing to accept that it’s buggy and needs more work.
Pulley hang ups: workaround turn off vibrating.
Install Chum directly.
There are many other bugs and workarunds discovered here in this forum.
Today in the middle of call C2 rebooted.
It seems that my C2 first screen password asking do not response(touch screen not working) every second time
One thing I noticed today is that proximity sensor on C2 stops working after every reboot (in CSD tool it is not passing the test). What helps is
devel-su
systemctl restart sensorfwd
It’s funny cause it is very similar to this old issue. This is a little annoying since I use LPM screen, which needs proximity sensor to work
I wanted to give some positive feedback on C2. I have a direct comparison with XA2 Plus and XP 10 mk2 which I currently own. Generally the phone is well built and gives nice first impression. The screen is on par with XA2 Plus despite lower specs (lower PPI) it looks really nice. You can’t really tell its 720p. 10 mk2 on the other hand has more vivid colors, but that’s obvious because of the amoled.
Nice thing about C2 is a proper scaling of the sailfish UI - you can see more information despite lower resolution. Note this does not apply to android apps, even when scaling is set to lowest possible value, it could be smaller - but that’s just my opinion.
I am rather a small phone guy and was afraid how big the C2 is, but after a few days I got used to it. It is comfortable to hold in hand and write messages, which on the 10mk2 was really a pain due to its width. Right now I think the 10mk2 is too small.
The C2 is noticeably faster on 5.0.0.29 than both XA2 Plus and 10mk2. Scrolling through menus feels really smooth. The amount of RAM seems like a huge improvement - I got no OOM at all, which on 10mk2 is very frequent and sometimes you can’t really multitask two applications, because the one on the background gets killed. The browser crashed once but I think that was not OOM related.
Even with the known bugs C2 is very usable for me and I started using it as a main phone. It is a really nice phone and after the software matures it could be one of the best sailfish phones.
About the things I noticed and weren’t reported earlier:
- Bluetooth Hands Free during phone calls does not work - I will try to investigate further and file a bug report.
- Browser had high CPU/MEM usage which led to instability of the whole system and significant drop in FPS. That occurred only when I was playing with the system BEFORE restoring backup. After restoring backup the problem is gone, the browser is fast and its CPU/MEM usage seems to be on a normal levels.
EDIT:
After two days I cannot reproduce those problems. Bluetooth hands free is working great and the same with the browser - even after clearing the profile it just works perfect.