Opened 3 years ago
Last modified 2 years ago
#26 assigned defect
Application tries to use wrong access point in some cases
| Reported by: | JayTay79 | Owned by: | sber |
|---|---|---|---|
| Priority: | minor | Milestone: | Future Release |
| Component: | Other | Version: | .5 |
| Keywords: | symbian | Cc: |
Description
As per this post (http://dev.nokia.wordpress.org/2010/02/11/hello-i-will-create-a-new-branch-for-0/#comment-46) I enter my blog settings and press save but the application stays at "fetching main page". It doesn't appear to initiate an internet connection nor does it use a connection if one is opened from another application first.
Change History (9)
comment:1 Changed 3 years ago by jokalli2
- Owner set to jokalli2
- Status changed from new to assigned
comment:2 Changed 3 years ago by jokalli2
Okay, now I checked the source code and the dialog "fetching main page" is raised after the network request is sent. So this sounds like an access point issue. What platform version are you using or what is your phone model? Do you have the default access point set in the settings and is it available?
comment:3 Changed 3 years ago by JayTay79
Interesting, I'm on an N97 MIni. My default access point in Web is "internet" which is the connection group of my home WLAN and then my 3G. The default in web feeds is 3G. I've just tried it at home and it's worked OK and connected using my WLAN. I'm not sure why the application didn't go to the 3G connection though....
comment:4 Changed 3 years ago by jokalli2
- Summary changed from Stuck at "Fetching main page" message after entering blog settings to Application tries to use wrong access point in some cases
Yes, it sounds like it is trying to use the WLAN access point, but cannot because the network is not in range.
I am unsure whether this bug is something that we should try to implement a solution for or whether we try to get Qt network access manager to select the access point properly.
But let's keep this in mind and see if Qt Mobility offers us more fine-grained control to access points. I'm also renaming the bug to be more descriptive.
comment:5 Changed 3 years ago by jokalli2
Access point handling should be fixed by Qt in their 4.7 release, which is going to be released in a couple of months. So this is likely to be in 0.7 time frame.
I don't think it is a good idea for us to do any workarounds for this, if this is going to be fixed soon.
comment:6 Changed 3 years ago by jokalli2
- Milestone changed from .6 to Future Release
comment:7 Changed 3 years ago by tmar
- Owner changed from jokalli2 to sber
comment:8 Changed 3 years ago by ahvenlam
- Priority changed from major to minor
Application uses now Qt Mobility Bearer Management API which will be part of Qt 4.7 also. I think it still might use WLAN which is out of range in some cases. If thats the case I think that should probably be fixed in Qt. Changing priority to minor because you can workaround the issue by setting your preferred access point as 1st priority in phone settings.
comment:9 Changed 2 years ago by daniloercoli
- Component changed from Symbian to Other
- Keywords symbian added

Thank you for opening the ticket. Is the behavior always the same, no matter what you enter to the URL field?