We have moved to a new Sailfish OS Forum. Please start new discussions there.
92

[hotfix] Opt-in hotfix for connectivity in upcoming update 7 [not relevant]

asked 2014-06-09 16:06:07 +0300

Aard gravatar image

updated 2015-07-25 21:31:16 +0300

eric gravatar image

Update: we just released this to subscribers. (12.6., 14:20 EEST)

We've been working for a while on updating connman to a newer version (from 1.15 to 1.23). It will fix connectivity issues in some environments - but comes at a regression risk in some networks where the old one worked fine.

We used all the different networks available to us to identify and fix issues - but there's a lot more interesting network hardware out there, so we decided not to include it in update7, but make it available for community members as opt-in hotfix, which will be published the same week as the update, hoping that the new stack gets the toughest and widest audience for testing.

If you want to test the new connectivity stack please send an email with arbitrary content to connman-hotfix@jolla.com, making sure the From-Address used is the one matching your Jolla account. After processing your email (which may take a while) you should get an update notification and be able to install the hotfix like any regular update.

Please add new issues as answers to this post or for already known issues add a comment to the answer describing your issue. If you want to go back to the old connectivity stack just send an email to connman-hotfix-opt-out@jolla.com, after a while you'll get an update notification which will bring you back to the main update.

edit retag flag offensive reopen delete

The question has been closed for the following reason "question is not relevant or outdated" by chemist
close date 2014-09-21 17:48:02.092477

Comments

This is cool, but wouldn't it be cooler by following/unfollowing here or via store?

harry ( 2014-06-09 16:21:12 +0300 )edit
8

I think this is the appropriate way - if it was too easy to opt-in, inexperienced users might try it and break something.

nodevel ( 2014-06-09 16:24:13 +0300 )edit

would be better if one could hotswap between the versions, so i could test both in places that i dont visit all too often and have baf reception like my summer home in the middle of nowhere.

Whippler ( 2014-06-09 16:27:44 +0300 )edit
11

Does this version support WPA2-PSK/AES (and others) networks or do we need to install the patched wpa_supplicant again?

Alex ( 2014-06-09 16:34:29 +0300 )edit
8

To be clear, this only affects wifi and bluetooth? Not the normal GSM/LTE reception?

BonoNL ( 2014-06-09 16:37:44 +0300 )edit

23 Answers

Sort by » oldest newest most voted
1

answered 2014-07-03 23:55:48 +0300

SaimenSays gravatar image

Had some trouble with mobile connection. It gets lost and on settings page it is grayed out. It is only coming back when rebooting the phone. This is also not fixed with conman :(

I described it also in "Mobile data often gets lost"

edit flag offensive delete publish link more
1

answered 2014-07-02 18:07:44 +0300

midnightoil gravatar image

I opted in, but more than 24 hours later (and a couple of subsequent requests), still no update notification.

edit flag offensive delete publish link more

Comments

I think it took about 48h for me to receive an update notice, stay calm (a couple of subsequent requests? really? are you serious? just wait for it!), it is not like the world will come to an end - even care@ replies might take longer than 24h...

chemist ( 2014-07-03 01:54:52 +0300 )edit
1

answered 2014-06-23 13:24:24 +0300

oplii gravatar image

updated 2014-06-23 13:26:54 +0300

I have been using 1.0.7.18 hotfix since 12.6. Nothing major until today my mobile data connection (Saunalahti / Finland) caused reboot, twice.

I was using Mitakuuluu -app when my mobile connection got exclamation mark. So I went to Settings and tried to put Air Plane mode ON but Air Plane -mode did not activated. WLAN connection was active Mobile was inactive. Tried couple of times to put it on air plane mode but then whole phone rebooted.After boot, Mobile data connection was grey and WLAN was active (NOTE: WLAN was not connected to router, it was only active). So I had not internet connection so again tried to put phone to Air Plane -mode but again it did not activated it and again reboot happened when I tried to put air plane -mode couple of times.

edit flag offensive delete publish link more
10

answered 2014-06-17 13:30:47 +0300

cquence gravatar image

With 1.0.7.18 there are still problems when switching between WiFi and Mobile Data. Sometimes the phone decides to not connect to the known WiFi, sometimes the phone flashes both WiFi and Mobile Data network icons without being connected to either of those. Other times I tried to toggle the Flight mode in order to "reset" the connection settings when they got stuck and flight mode was not being enabled at all, I ended up with the Flight mode indicator flashing at the same rate that the Mobile Data icon was flashing along with the exclamation mark in it. (2G on an area with poor reception). In this scenario I was switching on WiFi, WiFi stayed on but did not bother to connect to the known WiFi that existed in the area. Rebooting the phone seems to cure these problems since the known WiFi gets detected immediately and the phone connects.

Also I didn't see any improvement in automatic switching when walking out of my house [WLAN] and a transition into Mobile Data is required. I still have to wake the phone and tap on the screen for it to refresh its state and realize that WLAN is no longer available and it should connect to the Mobile Data network.

Overall I think that there is a lot of work needed in handling the connection switch between WLAN and Mobile Data. I think its the major "broken" thing on the phone for a while. You cannot rely on the phone for data connections, you have many applications open and cannot be sure if you don't get notifications because there aren't any or because the phone simply has dropped the data connection in the background but still thinks [and the apps also] that it has an active data connection.

edit flag offensive delete publish link more
2

answered 2014-06-17 11:53:22 +0300

Maddis gravatar image

updated 2014-06-23 19:47:52 +0300

no bluetooth file transfer possible between symbian and jolla

Devices:

  • Nokia C7 with Nokia Belle Refresh (Symbian)

  • Jolla with Saapunki 1.0.7.18 (and 1.0.7.16!)

Bluetooth pairing works, but "send failed" appears on C7.

edit flag offensive delete publish link more

Comments

I must confirm this (on two different Jollas with 1.0.7.18). Same thing happens with receiving files from Nokia N9 and BlackBerry Z10.

nodevel ( 2014-06-22 04:30:21 +0300 )edit

The same happens between Jolla 1.0.7.18 and Android 4.4.2. Was working before the Jolla update.

Gaudi ( 2014-06-23 21:22:05 +0300 )edit

The same happens also with Android 4.4.3 (Nexus 7 (Mobile) "nakasig").

Maddis ( 2014-06-24 16:52:18 +0300 )edit
0

answered 2014-06-17 11:27:45 +0300

Maddis gravatar image

Still current: SMS-receiving-issue

edit flag offensive delete publish link more
1

answered 2014-06-16 21:40:48 +0300

attah gravatar image

My phone started acting up too.. No problem while at home, but when i went out and lost wifi.. something took a whole lot of cpu and audible started having a hard time playing. (It uses offline data for those who doesn't know). At work today it had an exclamation mark on the connectivity symbol (both wifi and cellular at different times) all day and e-mail sync was a bit so-so. Once i prodded it, it eventually synched though. It seems to not have gotten back at my home wifi either, and didn't until i rebooted. (i.e. disabling/enabling wifi and cellular from settings didn't help). This has never happened to me before.. So, are there any logs i can provide.. or how can i help otherwise?

edit flag offensive delete publish link more
15

answered 2014-06-16 20:43:01 +0300

updated 2014-07-15 18:08:21 +0300

nightmare gravatar image

Jolla definitely has a problem with DHCP renewal ... I just watched the DHCP log at home (2 hours lease time) and while all other devices correctly renewed their IP address, Jolla did not do so ...

The bad thing in addition is, that Jolla keeps using the (not renewed) IP address and is this way a potential threat to the network, as this generates the risk of duplicate IP.

EDIT: I tested the behaviour of Jolla on being active (screen on) or standby (screen off). Therefore I set the DHCP lease to T=600 sec and resetted firewall (DHCP server) and Jolla.

  • with screen on Jolla perfectly renewed it's IP lease after T/2
  • with screen off Jolla did not renew it's IP address at all, so it expired after T - activating the screen did not solve the problem, IP stayed expired, Jolla had to be rebooted

EDIT: see comments below, chances are high, that missing DHCP renewal is a consequence of failing layer 2 connection

Edit Nightmare 15.07.2014: same problem with 1.0.8.19!!

edit flag offensive delete publish link more

Comments

I'm not using DHCP, but RA at home and have the same problems. So there's either two issue here, or the issue is elsewhere and DHCP not renewing is merely a symptom of that..

WhyNotHugo ( 2014-06-18 05:15:26 +0300 )edit
2

@hobarrera Agreed, Jolla really seems to loose layer 2 connection, so potentially not even DHCP broadcast/unicast renewals are getting through. Also in my case IPv6 RA connection dies usually in the very moment also IPv4 dies.

Manankanchu ( 2014-06-18 10:44:59 +0300 )edit

@Manankanchu: I hand't thought about it being layer 2 (or lower?). I'll try disabling power-saving in my router and see if that's related (it's the only layer 2-issue I've had in the past). In my case, I have no IPv4, so I was unaware that both were lost at the same time.

WhyNotHugo ( 2014-06-18 11:44:31 +0300 )edit

Ok, so my router's wifi driver doesn't support disabling power-saving mode, so I can't try that to determine if it's the issue or not. If somebody can run a quick test on this, we might discard that option.

WhyNotHugo ( 2014-06-18 12:09:10 +0300 )edit

Tried to test power saving and wasted lot of time as this horrible Jolla WiFi shows to be connected on SSID1 (standalone Cisco office access point) while in fact it is connected to SSID2 (hotspot WiFi with Cisco WLC controller) where SSID2 is deactivated in Jolla GUI

Manankanchu ( 2014-06-18 15:32:39 +0300 )edit
0

answered 2014-06-15 10:45:20 +0300

miska gravatar image

Have some troubles - while connected to wifi, mobile internet is not disabled and actually I have default route set through mobile data and no default route for wifi. And the idnicator icon keeps switching between wifi and data. But can't reproduce it reliably although happend on multiple networks (home, McDonalds). Sometimes I end up with the correct state, sometimes with this error.

edit flag offensive delete publish link more

Comments

1

This happens because the mobile data connection does not get forcible disconnected when connecting to WLAN. Applications that keep open sockets and do not disconnect and reconnect when the default route changes will still use the old interface. The icon will alternate between WLAN and mobile data only when data is being transmitted over the mobile data link.

Toggle the mobile data enabled switch off then on again to force the mobile data connection to disconnect.

Aaron McCarthy ( 2014-06-16 04:58:01 +0300 )edit

good point about the socket. It might be a good idea to requestDisconnect at that point. Although I might be worried we miss some use cases where user would want mobile data connection as well (gps/location?), but I cannot think of any. connman currently has no way to migrate the sockets as in IEEE 802.21 MiH and would probably be too big for us to implement.

llornkcor ( 2014-06-16 22:36:54 +0300 )edit

Just tested this. Sometimes connman does the correct thing changing the default route, even with an open socket on mobile data. It can even keep playing/streaming!

llornkcor ( 2014-06-17 00:00:55 +0300 )edit
5

answered 2014-06-14 13:15:14 +0300

Ozymandias gravatar image

So far I have the feeling the hotfix handles wifi/mobile changes better, but today when I woke up Jolla claimed to be connected to my wifi, but the internet didn't work. When I turned off wifi, it started to signal "problem with connection" and didn't stop, no matter what I activated or deactivated, even with both mobile and wifi off it still said "problem with connection" every few seconds. After reboot it seems to work fine again.

edit flag offensive delete publish link more

Comments

The "problem with connection" loop happened to me yesterday in an underground garage where there was no cell signal. Instead of rebooting, I attempted turning the airplane mode on/off and it solved the problem.

incognito ( 2014-06-14 14:00:04 +0300 )edit

Just had the no connection loop again, after doing a reset of my router (maybe just a coincidence, but I noticed it ~30 minutes after that reset) Airplane mode did not help. Reboot did.

Ozymandias ( 2014-06-15 16:54:45 +0300 )edit
1

Woke up again to find that Jolla was "connected" to my Wifi but didn't have working internet. This time no connection error loop, simply de- and reactivating wifi worked.

Oh and I'm running suspend policy on "early", but it was on the charger, so that shouldn't make a difference anyway.

Ozymandias ( 2014-06-17 09:51:11 +0300 )edit

Question tools

Follow
33 followers

Stats

Asked: 2014-06-09 16:06:07 +0300

Seen: 9,749 times

Last updated: Sep 21 '14