Bug 539 – MCC and MNC interchanged

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 539 - MCC and MNC interchanged

Summary:

MCC and MNC interchanged

Status:	CLOSED INVALID

Product:	PySide Mobility
Classification:	Unclassified
Component:	SystemInfo
Version:	0.1.0
Platform:	Other Other

Importance:	P3 major
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-12-09 10:38 EET by dom
Modified:	2011-01-21 15:44 EET (History)
CC List:	8 users (show)

See Also:

Attachments
Code that reproduces the error on N900 running Maemo PR1.3 and pyside 1.0.0beta1 (1.36 KB, text/x-python) 2010-12-09 10:38 EET, dom	Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description dom 2010-12-09 10:38:32 EET

Created attachment 173 [details]
Code that reproduces the error on N900 running Maemo PR1.3 and pyside
1.0.0beta1

QSystemNetworkInfo provides the following methods:
+ currentMobileCountryCode()
+ currentMobileNetworkCode()

At first these methods return correct values. In my case MCC: 232 and MNC: 1
When a network session via mobile internet is opened via session.open() or
manually, the SIGNALS currentMobileCountryCodeChanged( mcc ) and
currentMobileNetworkCodeChanged( mnc ) are called. But they seem to have
interchanged their values. 

result:
+ currentMobileCountryCode: 1
+ currentMobileNetworkCode: 232

A dbus-call returns the correct MCC (232) and MNC (1).

Comment 1 Matti Airas 2010-12-09 11:48:38 EET

Thanks for the bug.

Reading the description, I wonder whether this might be an upstream bug? In any
case, prioritizing P3 - this will probably fixed during the next sprint (we've
a separate track for Mobility bugs, so this won't have to wait until all PySide
P3 bugs are fixed).

Comment 2 dom 2010-12-09 15:02:48 EET

Hi Matti!

After having had a closer look, I also think that this is an upstream bug. I
have already filed a bug report:
http://bugreports.qt.nokia.com/browse/QTMOBILITY-845

Comment 3 Matti Airas 2010-12-10 04:49:43 EET

... and it appear the upstream bug has already been fixed. Impressive speed
they have, I admit.

I'm resolving this bug as INVALID (since this wasn't a PySide issue after all).
Thanks a lot for reporting it here and in the upstream! Let's hope the N900
QtMobility packages will get updated soon.

Comment 4 dom 2010-12-10 06:20:33 EET

Indeed, their speed is very impressive!

And the solution was quite simple:
http://qt.gitorious.org/qt-mobility/qt-mobility/commit/5939ae8a3fa0fca96b93db8b3e437656f974487c?diffmode=inline

Comment 5 renato filho 2011-01-21 15:44:43 EET

release beta4