GSM not working

[elhennig]

Since the upgrade of Feb 13th GSM only registers eventually when I restart frameworkd and phonefsod. After a reboot it usually does not register.

When I am lucky enough to get the GSM subsystem registered and I place a call, it terminates after a short moment, leaving no errors in the logfile (so far I did not use DEBUG logging.

[TAsn]

So please try using DEBUG and give us some logs (frameworkd and phonefsod logs)
If you can, also please provide your frameworkd, phonefsod and libframeworkd-glib versions.

[elhennig]

Versions:
frameworkd - 1:0.9.5.9+gitr1726+e3d6339c5d69e0791c4633f86363159e56126075-r2.4
frameworkd-config-shr - 0.9.5.9+gitr1743+b388de7f9f72839bd7e30102039a4262c194f453-245+d96ffd9e3f4d15455a427fa531672f76bd46409c-r7.4
libframeworkd-glib0 - 1:0.0.1+gitr132+95cc69d068a9015edcd9363a941cbf2f39114925-r0.4
libframeworkd-phonegui-efl-theme-neo - 0.2-45902+gitr221+1cc80e26a4558dfc2268b349d9a1f468e515bcfb-r2.4
libframeworkd-phonegui-efl0 - 0.0.3+gitr849+9d7ca1cecb93022e5b890cd87756ac6f072710ca-r35.4
libframeworkd-phonegui0 - 0.0.2+gitr849+9d7ca1cecb93022e5b890cd87756ac6f072710ca-r10.4
phonefsod - 0.0.0+gitr179+5f1a715f83da1485435137aff2db9bf4a7ab121c-r4.4

Logs follow later...

[elhennig]

Believe it or not: I tried to reproduce this error by rebooting several times and the error occured. Then I change the loglevel of frameworkd and phonefsod to DEBUG and the problem was gone. Even changing back the loglevel to INFO did not reproduce the errorneous behaviour.

The only remaining problem with GSM functionality is that the call window disappears from time to time. I do not know how to reproduce this, however.

I guess the best would be, to close this ticket, if the problem occurs again I would reopen it, if that's ok...

[TAsn]

I think this is best, as for closing window: sounds like the same issue that causes messages to close, should investigate more.

[elhennig]

I guess this is the same problem, as I have when running a stripped kernel, when GSM does not register either. This is probably an upstream error in FSO.

I attach the debug logs in a minute...

[TAsn]

closed dupe #960

[elhennig]

Some more info: I figured now that the PIN dialogue does to open, when the FR suspends during the registering process of the GSM subsystem. If the freerunner is connected to USB or the charger, the registering works well.

[Q-Master]

Log of the same issue at mine.

[elhennig]

Again some more info:

With some more reboots I found out, that stopping frameworkd, killing the remaining fsousaged processes and restarting frameworkd lets GSM register correctly.

[Hardy]

Replying to elhennig:

Again some more info:

With some more reboots I found out, that stopping frameworkd, killing the remaining fsousaged processes and restarting frameworkd lets GSM register correctly.

Wouldnt work on my moko

it seems pin-entry will popup randomely, (i rebootet 8 times and it only appears 2 times of it)

[TAsn]

After some investigation, it's an fso race, please open in freesmartphone.org.

[TAsn]

Bah, upstream.