![]() |
Re: Sailfish now on 1.0 (Jolla MWC announcement)
I don't recall reading that the update was going to be "early" this week, just this week. I won't search in twitter as I may crash it ;-)
As to questions about why would we support Jolla: well, in my case I live in a "supported" country (the best supported country is Finland so far, maybe Portugal soon), but I can still say that you kind of support these movements now or never. There are 3 main new things that came out recently: FF OS, Ubuntu Touch, Sailfish - I like the latter the most, hence I support it. Then again, 400€ won't put me in a financial problem right now. Yes, I didn't say Tizen as they already have tons of funding behind them, so it doesn't really count. You can support that one when it's fully matured, if it ever does. Samsung has lots of money for not doing things properly for decades and continuing not doing so, so there you go ;-) |
Re: Sailfish now on 1.0 (Jolla MWC announcement)
Quote:
|
Re: Sailfish now on 1.0 (Jolla MWC announcement)
Quote:
|
Re: Sailfish now on 1.0 (Jolla MWC announcement)
Quote:
I take the liberty of assigning a very low value to any rant along the lines of "you know nothing of development!" prompted just by raising concerns & disappointment about late delivery or other issues which affect the product user. Stuff is late now and again - it happens - but it is certainly a valid reason for a client to be disappointed, doubly so if communication is poor. Quote:
Quote:
Of course: Jolla's clients are hobbyists and mournful Finns, so this doesn't necessarily apply to them. Quote:
Quote:
|
Re: Sailfish now on 1.0 (Jolla MWC announcement)
Quote:
Quote:
I tried the radio switcher, and sure enough I get '4G', but the internet doesn't work. To be quite honest, I haven't mustered the energy to go looking into why that is yet. My understanding is that Rogers uses the same 2600MHz as Bell, and I get the '4G' so presumably it's simply a config issue somewhere rather than a radio problem. |
Re: Sailfish now on 1.0 (Jolla MWC announcement)
1 Attachment(s)
Fits fine it seems
|
Re: Sailfish now on 1.0 (Jolla MWC announcement)
Quote:
I'll try switching off WiFi and report back. |
Re: Sailfish now on 1.0 (Jolla MWC announcement)
Obviously there was a reason why Nokia never announced update dates. Software can always get delayed. Anyway, the update should be worth the wait and I'd rather have a smooth update than a bricked device.
|
Re: Sailfish now on 1.0 (Jolla MWC announcement)
Quote:
As to why this is problematic, well, there's a combination of a few things going on. (YMMV, I'm summarising things from memory and I didn't actively work on this much myself) Problem number one is that connectivity is a little more resource intensive than it needs to be right now. That's already fixed in the pending update. Problem number two is that peeking toggles the connection indicators on the homescreen, which causes a cascade of effects to mess around with touch interaction: - peeking toggles the connection indicator on the homescreen - this causes a bunch of synchronous dbus traffic, and disk writes - this blocks the GUI thread of the homescreen for a little too long - this causes evdev's kernel-side ring buffer to overflow, causing touch state to get lost in an undefined, bad place when the GUI thread finally does resume. The situation should be improving with (near) future updates. |
Re: Sailfish now on 1.0 (Jolla MWC announcement)
Wasn't this update scheduled for 14th. Its not 14th yet so sit tight or create a countdown.
|
| All times are GMT. The time now is 03:32. |
vBulletin® Version 3.8.8