Active Topics
-
Maemo repository (8)
to Community by Maemish - 6 hrs, 13 mins ago -
Porting apps to Leste (44)
to Maemo 7 / Leste by norayr - 10 hrs, 46 mins ago -
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 3 days, 8 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 4 days, 6 hrs ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 4 days, 6 hrs ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 4 days, 11 hrs ago - more...
 |
|
2010-11-14
, 22:36
|
|
Posts: 79 |
Thanked: 47 times |
Joined on Oct 2010
@ Devon, UK
|
#22
|
So something still is not reset to factory defaults when rootfs and eMMC are flashed?
I very much doubt your carrier will be able to help you debug this issue as it is evident this is a local problem with your handset or SIM: "resp_sim_get_parameters(): sim parameters could not be read rc:-1"
In your position (having re-flashed, etc) I would:
1) Thoroughly clean the contacts of the SIM and SIM holder with isopropyl alcohol (or a similar solvent that evaporates leaving no residue).
2) Request a new SIM from the carrier.
3) Return the phone to Nokia for repair.
Good luck!
| The Following User Says Thank You to sutaburosu For This Useful Post: | ||
|
|
2010-11-14
, 22:41
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#23
|
Originally Posted by sutaburosu
I have done both those. No help.
Use the menu in the Settings application. There you will find options to "Restore original settings" and "Clear device".
And phone can read the SIM card, because it asks the PIN code and also syslog gets the correct IMSI-number:
Nov 14 22:45:49 Nokia-N900 osso_startup_wizard[1036]: GLIB DEBUG default - Replied IMSI: XXXXXXXXXXXXXXX
Wouldn't the PIN code request, reply and confirmation fail also if there would be a problem with contacts?
|
|
2010-11-14
, 22:48
|
|
Posts: 79 |
Thanked: 47 times |
Joined on Oct 2010
@ Devon, UK
|
#24
|
Originally Posted by zimon
I don't know enough about SIM's electrical interface to say for sure, but it's possible that a different communication speed / protocol / voltage is negotiated after the PIN is verified.
Wouldn't the PIN code request, reply and confirmation fail also if there would be a problem with contacts?
The error message in your logs is very clear about communication failing with the SIM.
|
|
2010-11-15
, 00:16
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#25
|
The syslogs before are from PR1.2
Since then I flashed rootfs and eMMC with PR1.3 images (using Linux flasher). The syslog errors and notes are somewhat different, so the new syslog after somewhat clear state are attached.
After the firmware upgrade, I installing syslogd, and ssh deb-packages and set up USB networking so I can debug easily.
There is now everything what has been in syslog, except I have changed IMEI and IMSI codes to "MYIMEIMYIMEI" and "MYCURRENTIMSI".
The system has been booted 8 times after syslogd package was installed (used bluetooth to get it in):
In the first boot there was no SIM card yet in the device. The time was set to be correct in the first boot seen in syslog.
09:13 -> 21:14
In the second boot, one sees there has not been any SIM in the device before that:
Then the device asks SIM PIN, gets it right every time and tries to connect to the GSM network, fails.
Also in the couple of the boot sessions and in the last, I try manually to seach GSM networks and try to connect to my own, which fails with a note: "no access".
I even tried to fiddle with call forwarding settings and SIM phone book with another phone (N95), but still N900 complains about those:
(And I remind, two different SIM cards with different operators than mine works with this N900, just last week. So it is only with this one operator when SIM card support somehow got broken out of the blue two weeks ago after working fine 3 months.)
So if someone sees in this new fresh (PR1.3) log file something
revealing, I'd love to hear/read.
I guess all those csd system messages should show "rc:0" and not "rc:-1" or "rc:3" ?
Since then I flashed rootfs and eMMC with PR1.3 images (using Linux flasher). The syslog errors and notes are somewhat different, so the new syslog after somewhat clear state are attached.
After the firmware upgrade, I installing syslogd, and ssh deb-packages and set up USB networking so I can debug easily.
There is now everything what has been in syslog, except I have changed IMEI and IMSI codes to "MYIMEIMYIMEI" and "MYCURRENTIMSI".
The system has been booted 8 times after syslogd package was installed (used bluetooth to get it in):
Code:
$ grep "syslogd" /tmp/syslog_2010-11-15.txt | wc
8 56 504
09:13 -> 21:14
In the second boot, one sees there has not been any SIM in the device before that:
Code:
Nov 14 21:15:41 Nokia-N900 osso_startup_wizard[1034]: GLIB DEBUG default - Replied IMSI: 244MYCURRENTIMSI Nov 14 21:15:41 Nokia-N900 osso_startup_wizard[1034]: GLIB DEBUG default - Collected informations to decide whether to show GUI: mFirstTimeRun 1 mDateTimeUnset 0 mSimPresent 1 mCurrentSimId 244MYCURRENTIMSI mChangedSettings 0 mIsPinValid 1 mSettingsChangedBefore 0 mSimSeenBefore 0 mLastValidSimId mChangedWithoutPinBefore 0
Also in the couple of the boot sessions and in the last, I try manually to seach GSM networks and try to connect to my own, which fails with a note: "no access".
I even tried to fiddle with call forwarding settings and SIM phone book with another phone (N95), but still N900 complains about those:
Code:
Nov 14 21:15:41 Nokia-N900 bluetoothd[915]: SIM.Phonebook.read failed with error 1001 ... Nov 14 22:23:02 Nokia-N900 controlpanel[1916]: Error in cellular_settings_get_call_forwarding_cb() while fetching call forwarding: 1 Nov 14 22:23:02 Nokia-N900 controlpanel[1916]: connui_cell_net_divert_check_reply(): Error in call: GSM SS NOT AVAILABLE
So if someone sees in this new fresh (PR1.3) log file something
revealing, I'd love to hear/read.
I guess all those csd system messages should show "rc:0" and not "rc:-1" or "rc:3" ?
|
|
2010-11-15
, 01:29
|
|
Posts: 79 |
Thanked: 47 times |
Joined on Oct 2010
@ Devon, UK
|
#26
|
OK, I've read through the logs of your first three boots (up until 22:46). I'm really not sure what the problem might be.
You're still getting errors about communication with the SIM, but I don't think these are the root cause but merely a symptom. Likewise I don't think cleaning your SIM will help; the problem seems to be elsewhere.
I recant my earlier statement about your carrier not being able to help. Perhaps you should consult them to see what they can add. I too could believe your N900's IMEI has been banned on their network. It's worth asking them again; perhaps their customer services database isn't yet in synch with the production database.
It would be nice to know exactly what rc:4 indicates in this message: "cellular: csd[758]: ISI_SMS .790557> ind_reg_status(): Net registration (ind) status:0 rc:4". I'm having trouble finding that message in the various sources I've consulted on maemo.gitorious.org. I can't find anything on bugs.maemo.org that seems relevant.
I'm not sure, but conventionally negative return codes are rarely a good sign. It's late and I must sleep. If I have time tomorrow I'll install syslog to see what results I get.
As the SIM works in your N95 you might try deleting all stored contacts and SMSs. This is just grasping at straws though, based on where the majority of your errors are reported.
One other thing to try would be forcing a 2G connection, rather than dual or 3G mode.
You're still getting errors about communication with the SIM, but I don't think these are the root cause but merely a symptom. Likewise I don't think cleaning your SIM will help; the problem seems to be elsewhere.
I recant my earlier statement about your carrier not being able to help. Perhaps you should consult them to see what they can add. I too could believe your N900's IMEI has been banned on their network. It's worth asking them again; perhaps their customer services database isn't yet in synch with the production database.
It would be nice to know exactly what rc:4 indicates in this message: "cellular: csd[758]: ISI_SMS .790557> ind_reg_status(): Net registration (ind) status:0 rc:4". I'm having trouble finding that message in the various sources I've consulted on maemo.gitorious.org. I can't find anything on bugs.maemo.org that seems relevant.
I guess all those csd system messages should show "rc:0" and not "rc:-1" or "rc:3" ?
As the SIM works in your N95 you might try deleting all stored contacts and SMSs. This is just grasping at straws though, based on where the majority of your errors are reported.
One other thing to try would be forcing a 2G connection, rather than dual or 3G mode.
| The Following User Says Thank You to sutaburosu For This Useful Post: | ||
|
|
2010-11-15
, 15:50
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#27
|
I got status code 6 today, when I manually tried to connect to my own GSM operator's network. I wonder what 6 means?
Is there dbus-commands (CLI) which can be used to make the same as with Setup application/Phone, manually search GSM networks, list them, and then try to connect one of them?
Code:
Nokia-N900:~# SIM_check.sh dbus-send --system --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_sim_status method return sender=:1.19 -> dest=:1.172 reply_serial=2 uint32 1 int32 0 dbus-send --system --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_registration_status method return sender=:1.19 -> dest=:1.173 reply_serial=2 byte 6 uint16 903 uint32 972 uint32 12 uint32 244 byte 0 byte 5 int32 0 dbus-send --system --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_signal_strength method return sender=:1.19 -> dest=:1.174 reply_serial=2 byte 0 byte 0 int32 0
|
|
2010-11-15
, 16:17
|
|
Posts: 79 |
Thanked: 47 times |
Joined on Oct 2010
@ Devon, UK
|
#28
|
Originally Posted by zimon
The lack of output from dbus-monitor whilst performing those actions suggests there aren't.
Are there dbus-commands (CLI) which can be used to make the same as with Setup application/Phone, manually search GSM networks, list them, and then try to connect one of them?
| The Following User Says Thank You to sutaburosu For This Useful Post: | ||
|
|
2010-11-15
, 16:40
|
|
Posts: 79 |
Thanked: 47 times |
Joined on Oct 2010
@ Devon, UK
|
#29
|
FYI, when I register to my SIM's home network I get:
cellular: csd[803]: ISI_SMS .584106> ind_reg_status(): Net registration (ind) status:1 rc:0
However when I try to register to a network to which I'm not allowed to roam I get what you were seeing yesterday:
cellular: csd[803]: ISI_SMS .670837> ind_reg_status(): Net registration (ind) status:0 rc:4
I think you should take this up with your carrier again.
cellular: csd[803]: ISI_SMS .584106> ind_reg_status(): Net registration (ind) status:1 rc:0
However when I try to register to a network to which I'm not allowed to roam I get what you were seeing yesterday:
cellular: csd[803]: ISI_SMS .670837> ind_reg_status(): Net registration (ind) status:0 rc:4
I think you should take this up with your carrier again.
|
|
2010-11-15
, 16:41
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#30
|
OT: A Moderator could transfer all my messages and replys to them to this thread instead:
SIM card registration failed
My problem is not that N900 does not recognize SIM card, but fails to register it to the GSM network. Sorry to be in this thread in the first place, but Addre Klapper here suggested those dbus-commands which I think could had helped abit.
SIM card registration failed
My problem is not that N900 does not recognize SIM card, but fails to register it to the GSM network. Sorry to be in this thread in the first place, but Addre Klapper here suggested those dbus-commands which I think could had helped abit.
I guess you cannot see any GSM networks either if you go to Setup/Phone/Manual_networks?
Yes, seems like my problem is not exactly "SIM card not recognized", but rather "SIM card registration failed".
I would understand, if my phone's IMEI would be black-listed with this one and only operator, and not with the other two different GSM network operators. But technical support said it is not black listed and usually black listing in my country goes to all 3 GSM-operators.
Neither it could be operator locked, as it works with other two GSM operators which are competitors with each others and with the third my own operator as well.