I've sent this to the smartphones-userland list and heard from Mickey.
He suspects that the CCWA command is causing a firmware crash in the
calypso. He has suggested taking it out of the list of commands to be
run after the modem registers with a cell, but as I understand it that
will disable call-waiting. I am running a custom fsogsmd with the CCWA
command disabled and for the first time in months GSM is stable for me
in SHR.
Are others experiencing my problem (loss of GSM after a few hours)? I'd
hate to (have Mickey) break call-waiting for everyone if this only
affects me.
Ben
On 10/25/2011 04:55 PM, Benjamin Deering wrote:
Here is my fsogsmd.log, it looks like everything goes wrong after here:
2011-10-21T01:31:52.451748Z [INFO] libfsotransport <0710:2>: SRC:
"+CGREG=2;+CGREG?;+CGREG=0" -> [ "+CGREG: 2,0", "OK" ]
2011-10-21T01:31:52.980430Z [WARN] libfsotransport <0710:3>: Timeout
while waiting for an answer to '+CCWA=1,1'
2011-10-21T01:31:52.992707Z [INFO] libfsotransport <0710:3>: SRC:
"+CCWA=1,1" -> [ "+CME ERROR: 512" ]
2011-10-21T01:31:52.996348Z [INFO] libfsotransport <0710:3>: URC: [
"+CME ERROR: 512" ]
2011-10-21T01:31:52.996800Z [WARN] TiCalypsoModem <4C>: No handler
for URC +CME ERROR w/ rhs 512, please report to Mickey
<[email protected]>
2011-10-21T01:31:53.010703Z [INFO] libfsotransport <0710:3>: SRC:
"+CSMS=1" -> [ "+CME ERROR: 512" ]
2011-10-21T01:31:53.014257Z [INFO] libfsotransport <0710:3>: URC: [
"+CME ERROR: 512" ]
The whole log is here:
http://jeepingben.homelinux.net/freerunner_packages/fsogsmd.log.
Hopefully I removed all the secret stuff. If not, please don't steal
my account info ;-)
Ben
On 10/25/2011 07:25 AM, Benjamin Deering wrote:
Thanks for the idea mrmoku,
I have see the problem when connected to usb as well, so that probably
also points away from battery. Lately I've noticed that sometimes the
freerunner will fail to suspend 5 or 6 times in a row. This was in
dmesg after that happened:
[ 1795.050000] jbt6k74 spi2.0: suspended
[ 1795.060000] glamo-mci glamo-mci.0: glamo_mci_set_ios: power down.
[ 1795.060000] pm_op(): platform_pm_suspend+0x0/0x64 returns -16
[ 1795.060000] PM: Device gta02-pm-gsm.0 failed to suspend: error -16
[ 1795.060000] PM: Some devices failed to suspend
I've moved /var/tmp off of volatile so I can get better logs.
Ben
On 10/25/2011 01:53 AM, Klaus 'mrmoku' Kurzmann wrote:
On Tue, 25 Oct 2011, Klaus 'mrmoku' Kurzmann wrote:
Hello Benjamin,
On Mon, 24 Oct 2011, Benjamin Deering wrote:
Hi List,
I've been having trouble with GSM under shr for several months now.
Using shr-u or shr-core I see GSM stop working within a few hours of
boot. It is rock solid under qtmoko, but I would rather be using
SHR.
When it stops working, the indicator on the top bar will either
revert to off, or say that I have coverage. The error message when
I try to make a call or connect to GPRS after it quits is not
consistent. I saw nothing interesting in the phoneuid or phonefsod
logs, but I can attach them once I see the problem again on my
latest install. I have deepsleep set to never and increasing the
resume timeout in fsogsmd.conf has no effect.
Both of my phones show the problem and both are running the moko11
gsm firmware.
Has anyone seen/solved a similar issue?
can you exclude it's the battery? Having that problem on two phones
(with two different batteries) makes that unlikely... But that
might be
one possible reason.
Gah, never mind... battery is still the same under QtMoko :-P
Thanks,
Ben
--
Klaus 'mrmoku' Kurzmann
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
