Crash/poweroff after entering SIM PIN - maemo.org

Active Topics

Porting apps to Leste (40)
to Maemo 7 / Leste by Maemish - 1 day, 20 hrs ago
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 6 days ago
more...

Thread Tools

PaulePanter	2021-05-02 , 07:01
Posts: 22 \| Thanked: 18 times \| Joined on Mar 2021	#1

Dear Maemo community,

Since yesterday afternoon after no problems for several months, when the phone shut itself down (I assumed due to empty battery), it shuts itself down every time after entering the SIM PIN. It starts when I take out the SIM or abort the SIM PIN entering dialog, but then trying to activate the SIM by entering the SIM PIN, it crashes/shuts down.

Have you ever heard of such a problem?

I am going to try to find some logs, but I am out of ideas.

1. O₂ Germany changed something.
2. After connecting the SIM, it tries to receive some data (SMS?), which crashes the phone.

Thanks,

PaulePanter

Quote & Reply |

The Following User Says Thank You to PaulePanter For This Useful Post:
juiceme

PaulePanter	2021-05-02 , 07:50
Posts: 22 \| Thanked: 18 times \| Joined on Mar 2021	#2

Dear Maemo community,

Connecting the device over USB to a laptop, and enabling SDK mode, it didn’t crash after entering the PIN. No idea why.

Nothing related in `/var/log/pasms.log`. Here are the message before entering the PIN, and nothing related afterward.

Code:

[2021-05-02T08:29:58] void PACustomization::loadXml(): 
Server to be used: "PROD"
Phone number: ""
Is my-nokia country: false
MCC = "0"
[2021-05-02T08:29:58] void PhoneActivation::subscribe(CherrySmsEngine::SignupInfo, QString): 
[2021-05-02T08:29:58] void PhoneActivation::smsSendFinished(bool, QString): success = "false"
[2021-05-02T08:29:58] void PhoneActivation::smsSendFinished(bool, QString): error reason: sms_msg_new_txt_message failed

Thanks,

PaulePanter

Quote & Reply |

The Following 2 Users Say Thank You to PaulePanter For This Useful Post:
hhbbap, juiceme

PaulePanter	2021-05-02 , 07:53
Posts: 22 \| Thanked: 18 times \| Joined on Mar 2021	#3

Dear Maemo community,

And here the messages before a crash from `/var/log/syslog`:

Code:

May  2 05:22:12 (2021) nped[1244]: i2c_write: Remote I/O error
May  2 05:22:15 (2021) cellular: ssc[706]: Emitting: compatible state tablet_state
May  2 05:22:15 (2021) cellular: ssc[706]: Emitting: RequestedMode=Deferred PinQueryActive=false
May  2 05:22:15 (2021) bluetoothd[1751]: Bluetooth deamon 4.91
May  2 05:22:15 (2021) bluetoothd[1751]: Starting SDP server
May  2 05:22:15 (2021) bluetoothd[1751]: Excluding (conf) network
May  2 05:22:15 (2021) bluetoothd[1751]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
May  2 05:22:15 (2021) bluetoothd[1751]: Listening for HCI events on hci0
May  2 05:22:15 (2021) icd2 0.213.4+0m8[1757]: icd2 version 0.213.4+0m8 starting
May  2 05:22:15 (2021) icd2 0.213.4+0m8[1757]: GLIB DEBUG default - conn_settings_get_bool():value not set
May  2 05:22:16 (2021) bluetoothd[1751]: HCI dev 0 up
May  2 05:22:16 (2021) bluetoothd[1751]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
May  2 05:22:16 (2021) bluetoothd[1751]: Could not get the contents of DMI chassis type
May  2 05:22:16 (2021) bluetoothd[1751]: Adapter /org/bluez/1751/hci0 has been enabled
May  2 05:22:16 (2021) bluetoothd[1751]: Endpoint registered: sender=:1.15 path=/MediaEndpoint/HFPAG
May  2 05:22:16 (2021) bluetoothd[1751]: Endpoint registered: sender=:1.15 path=/MediaEndpoint/A2DPSource
May  2 05:22:16 (2021) bluetoothd[1751]: HCI dev 0 down
May  2 05:22:16 (2021) bluetoothd[1751]: Adapter /org/bluez/1751/hci0 has been disabled
May  2 05:22:18 (2021) rapper[1795]: GLIB MESSAGE default - 'org.freedesktop.Telepathy.MissionControl5' activated
May  2 05:22:18 (2021) obexd[1792]: obexd daemon 0.42
May  2 05:22:18 (2021) icd2 0.213.4+0m8[1757]: connectivity UI service 'com.nokia.icd_ui' started
May  2 05:22:18 (2021) obexd[1792]: Ignoring irmc
May  2 05:22:18 (2021) obexd[1792]: Ignoring syncevolution
May  2 05:22:20 (2021) conndlgs[940]: QFile::at: Cannot set file position 0
May  2 05:22:22 (2021) meegofeedbackd: MfXListener: Could not get _NET_WM_WINDOW_TYPE property for window ID 0x00200001
May  2 05:22:22 (2021) cellular: csd[646]: com.nokia.csd.simatk: isi_simatk_set_uid_registered:379 UI daemon registration changed: new value = 1
May  2 05:22:22 (2021) applifed[942]: reset memnotify
May  2 05:22:22 (2021) applifed[942]: go to wait cpu state
May  2 05:22:22 (2021) applauncherd[854]: Daemon: Exited boot mode.
May  2 05:22:26 (2021) applifed[942]: 'Com.Nokia.Telephony.CallUi' got registered with pid '1898'..
May  2 05:22:29 (2021) applifed[942]: 'com.nokia.telephony.callhistory' got registered with pid '1909'..
May  2 05:22:41 (2021) applifed[942]: 'com.nokia.Messaging' got registered with pid '1995'..
May  2 05:22:49 (2021) applifed[942]: 'com.nokia.fenix' got registered with pid '2018'..
May  2 05:22:52 (2021) applifed[942]: 'com.nokia.contacts' got registered with pid '2025'..
May  2 05:22:57 (2021) applifed[942]: 'com.nokia.Calendar' got registered with pid '2037'..
May  2 05:23:00 (2021) cellular: ssc[706]: Emitting: compatible state tablet_state
May  2 05:23:00 (2021) cellular: ssc[706]: Emitting: PinQueryActive=true
May  2 05:23:01 (2021) applifed[942]: 'com.nokia.browser' got registered with pid '2052'..
May  2 05:23:04 (2021) applifed[942]: 'com.nokia.maemo.CameraService' got registered with pid '2065'..
May  2 05:23:04 (2021) applifed[942]: Application 'com.nokia.maemo.CameraService' released from prestarted state, count=1
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GStreamer - gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GStreamer - gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GStreamer - gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GLib-GObject - g_object_unref: assertion `G_IS_OBJECT (object)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GLib-GObject - g_object_unref: assertion `G_IS_OBJECT (object)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GStreamer - gst_element_get_static_pad: assertion `GST_IS_ELEMENT (element)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GStreamer - gst_element_get_static_pad: assertion `GST_IS_ELEMENT (element)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GStreamer - gst_object_unref: assertion `object != NULL' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GStreamer - gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GStreamer - gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GStreamer - gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GStreamer - gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GLib-GObject - g_object_unref: assertion `G_IS_OBJECT (object)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GLib-GObject - g_object_unref: assertion `G_IS_OBJECT (object)' failed
May  2 05:23:05 (2021) camera[2065]: GLIB CRITICAL ** GLib-GObject - g_object_unref: assertion `G_IS_OBJECT (object)' failed
May  2 05:23:06 (2021) cellular: ssc[706]: Emitting: compatible state tablet_state
May  2 05:23:06 (2021) cellular: ssc[706]: Emitting: PinQueryActive=false
May  2 05:23:06 (2021) cellular: csd[646]: ISI_SIM: New SIM status SIM_OK(1)
May  2 05:23:06 (2021) cellular: ssc[706]: SIM IMSI=262072007986812
May  2 05:23:06 (2021) cellular: ssc[706]: SIM HPLMN=262.07
May  2 05:23:06 (2021) cellular: ssc[706]: Emitting: compatible state sim_ready
May  2 05:23:06 (2021) cellular: ssc[706]: Emitting: ModemState=Ready SimState=Ready IMEISV=357923042451452.40 HPLMN=262.07
May  2 05:23:06 (2021) cellular: ssc[706]: Emitting: IMSI=262072007986812
May  2 05:23:07 (2021) cellular: ssc[706]: Emitting: ModemState=Normal
May  2 05:23:07 (2021) cellular: ssc[706]: Emitting: compatible state activation_pending
May  2 05:23:07 (2021) cellular: ssc[706]: Emitting: NetState=Pending
May  2 05:23:07 (2021) cellular: ssc[706]: Emitting: compatible state activation_pending
May  2 05:23:07 (2021) cellular: ssc[706]: Emitting: RequestedMode=Active MTCState=MTC_NORMAL
May  2 05:23:07 (2021) cellular: csd[646]: com.nokia.csd.CSNet: ERROR Cell info query failed: Internal modem communication error
May  2 05:23:08 (2021) usetimed: WARNING Unknown radio technology: -1
May  2 05:23:08 (2021) cellular: csd[646]: com.nokia.csd.simatk: simatk_dbus_emit_set_up_menu: Validating title string - result: 1
May  2 05:23:08 (2021) cellular: csd[646]: com.nokia.csd.simatk: simatk_ui_resp:497 Sending ATK_UI_RESP with response 0
May  2 05:23:08 (2021) camera[2065]: GLIB CRITICAL ** GLib-GObject - g_object_unref: assertion `G_IS_OBJECT (object)' failed
May  2 05:23:08 (2021) camera[2065]: GLIB CRITICAL ** GLib-GObject - g_object_unref: assertion `G_IS_OBJECT (object)' failed
Ma[    0.000000] Initializing cgroup subsys cpu

Thanks,

PaulePanter

Quote & Reply |

The Following User Says Thank You to PaulePanter For This Useful Post:
juiceme

	peterleinchen	2021-05-02 , 08:11
	Posts: 4,118 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#4

Not 100% sure but I think so.
The connection to a cellular network (as well as receiving/initiating a call) will need more power for a short period of time (Leistungsspitze / power peak). And I guess your battery is quite old?
I had this iirc with a battery that else worked fine, still long enough but let the phone shut down in such scenario.
Please try the same with a connected charger...

--edit
ah, I did not see your other answers. So self tested already.
Your battery is worn out and cannot give enough power juice for such peaks anymore.

__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature

Quote & Reply |

The Following User Says Thank You to peterleinchen For This Useful Post:
juiceme

PaulePanter	2021-05-02 , 12:35
Posts: 22 \| Thanked: 18 times \| Joined on Mar 2021	#5

Dear Maemo community,

Indeed it seems battery related. Disconnecting the charger after it connected to the O₂ network, I had problems again doing a call, and it lost connection to the mobile network, and after a few reconnects reste. No problems with a charger connected.

As there does not seem to be a way to fix a worn-out battery, I guess, I have to retire the phone or think about replacing the battery (found some offer for 24 €), but I guess it’s not worth it.

Thanks,

PaulePanter

Quote & Reply |

The Following User Says Thank You to PaulePanter For This Useful Post:
juiceme

aspergerguy	2021-05-02 , 14:46
Posts: 807 \| Thanked: 1,589 times \| Joined on Aug 2014	#6

Originally Posted by PaulePanter

I guess, I have to retire the phone or think about replacing the battery (found some offer for 24 €), but I guess it’s not worth it.

Unfortunately bit of a lottery with batteries now as last originals manufactured about 2013/14. Presumably your N9 16GB not 64GB? As UK based prior to Brexit I would have stepped in before with offer of working Jolla phone or to take N9 off your hands.

Lack of batteries is just another reason why I haven't updated my "Sticky - Re-commissioning N9 in 2015" together with the fact older eyes necessitate me enlarging screen icons and font size.

Quote & Reply |

The Following 2 Users Say Thank You to aspergerguy For This Useful Post:
juiceme, peterleinchen

	nonsuch	2021-05-04 , 06:41
	Posts: 584 \| Thanked: 1,550 times \| Joined on Sep 2019	#7

I can confirm that SIM cards sometimes (esp. when initialising I guess) draw a lot of power.

New battery:
https://www.polarcell.de/en/Article?s=n900
I got the slightly more expensive one.

__________________
N900 in 2020
SFOS in 2021

Quote & Reply |

The Following 3 Users Say Thank You to nonsuch For This Useful Post:
juiceme, peterleinchen, pichlo

	pichlo	2021-05-06 , 11:01
	Posts: 6,447 \| Thanked: 20,981 times \| Joined on Sep 2012 @ UK	#8

Originally Posted by nonsuch

I can confirm that SIM cards sometimes (esp. when initialising I guess) draw a lot of power.

I am not sure it is the SIM card as such. More like, a device with a SIM card inserted tries to register with the network. Using the cellular radio is what draws a lot of power.

Fun story I may have mentioned before. I had a Palm phone with a battery that lasted 9-10 days between charges. I did not bother to pack a charger when I was going away for just a week. My main usage pattern was texting and using apps (like games) that did not use the radio. Hardly ever any phone calls.

When the battery started getting old, I did not notice any change at all. It would still last the same 9-10 between charges, with the same usage pattern. The only change I noticed was that the voice in phone calls became distorted, due to the aforementioned power drain by the cell radio. Evenually it got to the stage when my phone rebooted when it received a call with the battery indicator below 90%. Replacing the battery fixed the problem.

The moral of the story is, do not trust the battery indicator. It may look like your battery is OK. The device may even behave like the battery is OK (see my 9-10 days between charges). But the battery may be already knackered. The OP's definitely looks that way.

__________________
Русский военный корабль, иди нахуй!

Quote & Reply |

The Following 2 Users Say Thank You to pichlo For This Useful Post:
juiceme, peterleinchen

PaulePanter	2021-05-25 , 17:51
Posts: 22 \| Thanked: 18 times \| Joined on Mar 2021	#9

Dear Maemo community,

Thank you for all the replies with great input.

As an update, the problem vanished again, and I am able to enter the PIN and do calls without the plugged in charger. I know, this observation does not prove anything, and I keep in mind, that the phone stops working at any time and I should at least always carry a charger with me.

Thanks,

PaulePanter

Quote & Reply |

The Following 2 Users Say Thank You to PaulePanter For This Useful Post:
juiceme, pichlo

« Previous Thread | Next Thread »

Forum Jump

All times are GMT. The time now is 17:45.

Active Topics

Porting apps to Leste (40)

The N900 is now 15 years old! (9)