Using AGPS - the GPS device suddenly seems to have got nuked!
Hi Folks, I'm having some problems with GPS on my freerunner. I had followed the steps in the wiki about using AGPS with assist-online and it had been working very well for me the last few weeks until now. Yesterday when I ran the python script as I usually do, I didn't get a fix for quite a while and tangogps showed me a red exclamation mark in the status bar. So I got home and put my frameworkd into debug mode and found the log full of messages like these: 2008.12.10 08:11:10 ogpsdDEBUGDiscarded data not UBX ',N*30\r\n$' 2008.12.10 08:11:10 ogpsdDEBUGDiscarded data not UBX 'G,,*48\r\n$GPGSA,A' 2008.12.10 08:11:10 ogpsdDEBUGDiscarded data not UBX ',0*79\r\n$GPGLL,,,' 2008.12.10 08:11:10 ogpsdDEBUGDiscarded data not UBX ',,,V,N*64\r\n$GPZDA,00' 2008.12.10 08:11:10 ogpsdDEBUGDiscarded data not UBX ',00*48\r' 2008.12.10 08:11:11 ogpsdDEBUGDiscarded data not UBX '\n$GPRMC,' 2008.12.10 08:11:11 ogpsdDEBUGDiscarded data not UBX '' It seems like valid data across lines, but something obviously went horribly wrong while writing the UBX data to the Antaris. I've tried power cycling the GPS chip as well as the device several times, also the all the kinds of resets available in the agpsui testing tool, running the assist online script again, writing a blank file of the same size to /dev/ttySAC1 - basically everything that I could think of from whats documented. I've even left it running for a couple of hours hoping the data would run out, but it's of no help. Is there any way I can fix this or am I stuck with a nuked GPS? Thanks in advance for any help. Regards, Carl ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
On Tue, 9 Dec 2008 11:31:51 -0800 (PST), GreyCardinal <[EMAIL PROTECTED]> wrote: > > No more ideas? > -- > View this message in context: > http://n2.nabble.com/Neo-due-2---NG---last-chance-tp1630257p1635415.html > Sent from the Openmoko Support mailing list archive at Nabble.com. While SSH'd into the blank FR, take a look in /sys/class/backlight/ and see what brightness is set to, and try to echo a different value to it. If it shows brightness already set to 100 or something and your display is unlighted I'd say it's likely your backlight is done, talk to OM or distributor about warranty. If you have no backlight when you boot up to NOR bootrom I'd say it's pretty certain already, but if you can SSH in and poke at the settings you can more readily assure yourself of that. Sorry I don't have more or better to offer, but I honestly think you're hit with a backlight failure at the hardware level. j -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
No more ideas? -- View this message in context: http://n2.nabble.com/Neo-due-2---NG---last-chance-tp1630257p1635415.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GSM no longer registers on GTA02 - how to troubleshoot?
I received the same behavior when I updated to the latest testing images. I revered to the old 2008.9 images and things are working again. On Tue, Dec 9, 2008 at 11:33 AM, Andy Green <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | Hi everybody, > | > | I have been using Freerunner as a daily phone for some months now, and > | yesterday it suddenly stopped registering the GSM network. It was > | working fine in the morning, sending/receiving SMS, making phone > | calls, etc., then in the afternoon suddenly the phone portion was > | completely dead. I restarted qpe (running Om2008.9) a few times, then > | rebooted the phone, pulled out the battery and SIM and reseated > | everything, etc., but got nowhere. When I got home, I reflashed a > | couple of known good kernel/rootfs combinations, but got nowhere. I > | even tried an FSO image, since it uses a different phoneserver, but it > | didn't work either. I put my SIM into my old dumbphone (which is a > | little bit broken, in that it only works on speakerphone) and it was > | able to register with no problems. > | > | How can I troubleshoot GSM registration to see at what point the > | process is failing? I would hate for this to be a hardware problem, > | but I don't know what to do when reflashing doesn't work. > | > | I do have another issue, which I don't think is related: my NAND > | u-boot seems to be borked. Whenever I boot the GTA02 without booting > | it from the NOR u-boot, I get a scrambled image on the screen and the > | device is frozen. Often, the scrambled image that appears is whatever > | was in the framebuffer right before powering off. If I boot into NOR > | u-boot, I can boot into the OS fine, but if I just try to turn it on > | without holding down the AUX button or try booting into NAND u-boot, I > | get a freeze. I've tried reflashing u-boot several times, but it > | doesn't help. I download u-boot from downloads.openmoko.org and the > | md5 sum of my u-boot image is 40b8f908649f78e7d70358239da96f98. Is > | this a known good image? Why would u-boot fail after reflashing? > > Your U-Boot environment can have some issue, that's why the problem > behaviour is so sticky. You are into trying to get a USB serial > connection on ttyACM0 on your host and meddling from there. > > About your main problem not much idea except confirm the SIM still works > on another phone I guess. > > - -Andy > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAkk+ne0ACgkQOjLpvpq7dMo0nwCeJFFUGrQUWaU9ENryQeq74ZEw > xC8AniEvrMspCUSAoOz+CF8D4XZRtewu > =kbxa > -END PGP SIGNATURE- > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- Paul Email - [EMAIL PROTECTED] There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GSM no longer registers on GTA02 - how to troubleshoot?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi everybody, | | I have been using Freerunner as a daily phone for some months now, and | yesterday it suddenly stopped registering the GSM network. It was | working fine in the morning, sending/receiving SMS, making phone | calls, etc., then in the afternoon suddenly the phone portion was | completely dead. I restarted qpe (running Om2008.9) a few times, then | rebooted the phone, pulled out the battery and SIM and reseated | everything, etc., but got nowhere. When I got home, I reflashed a | couple of known good kernel/rootfs combinations, but got nowhere. I | even tried an FSO image, since it uses a different phoneserver, but it | didn't work either. I put my SIM into my old dumbphone (which is a | little bit broken, in that it only works on speakerphone) and it was | able to register with no problems. | | How can I troubleshoot GSM registration to see at what point the | process is failing? I would hate for this to be a hardware problem, | but I don't know what to do when reflashing doesn't work. | | I do have another issue, which I don't think is related: my NAND | u-boot seems to be borked. Whenever I boot the GTA02 without booting | it from the NOR u-boot, I get a scrambled image on the screen and the | device is frozen. Often, the scrambled image that appears is whatever | was in the framebuffer right before powering off. If I boot into NOR | u-boot, I can boot into the OS fine, but if I just try to turn it on | without holding down the AUX button or try booting into NAND u-boot, I | get a freeze. I've tried reflashing u-boot several times, but it | doesn't help. I download u-boot from downloads.openmoko.org and the | md5 sum of my u-boot image is 40b8f908649f78e7d70358239da96f98. Is | this a known good image? Why would u-boot fail after reflashing? Your U-Boot environment can have some issue, that's why the problem behaviour is so sticky. You are into trying to get a USB serial connection on ttyACM0 on your host and meddling from there. About your main problem not much idea except confirm the SIM still works on another phone I guess. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk+ne0ACgkQOjLpvpq7dMo0nwCeJFFUGrQUWaU9ENryQeq74ZEw xC8AniEvrMspCUSAoOz+CF8D4XZRtewu =kbxa -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
GSM no longer registers on GTA02 - how to troubleshoot?
Hi everybody, I have been using Freerunner as a daily phone for some months now, and yesterday it suddenly stopped registering the GSM network. It was working fine in the morning, sending/receiving SMS, making phone calls, etc., then in the afternoon suddenly the phone portion was completely dead. I restarted qpe (running Om2008.9) a few times, then rebooted the phone, pulled out the battery and SIM and reseated everything, etc., but got nowhere. When I got home, I reflashed a couple of known good kernel/rootfs combinations, but got nowhere. I even tried an FSO image, since it uses a different phoneserver, but it didn't work either. I put my SIM into my old dumbphone (which is a little bit broken, in that it only works on speakerphone) and it was able to register with no problems. How can I troubleshoot GSM registration to see at what point the process is failing? I would hate for this to be a hardware problem, but I don't know what to do when reflashing doesn't work. I do have another issue, which I don't think is related: my NAND u-boot seems to be borked. Whenever I boot the GTA02 without booting it from the NOR u-boot, I get a scrambled image on the screen and the device is frozen. Often, the scrambled image that appears is whatever was in the framebuffer right before powering off. If I boot into NOR u-boot, I can boot into the OS fine, but if I just try to turn it on without holding down the AUX button or try booting into NAND u-boot, I get a freeze. I've tried reflashing u-boot several times, but it doesn't help. I download u-boot from downloads.openmoko.org and the md5 sum of my u-boot image is 40b8f908649f78e7d70358239da96f98. Is this a known good image? Why would u-boot fail after reflashing? Is there a way to wipe out my entire NAND and reflash everything, without a debug board? I know there is the lowlevel image, which apparently requires a debug board to flash. I have no idea how my u-boot got so screwed up or why restoring it doesn't help. Any advice on either of these two problems (more importantly, GSM registration) is much appreciated. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Testing build [OM 2008.x]
I apologize for the mix-up, I have updated the subject line. As to the dates of the test builds, The test builds affected would be from 12/1. On Tue, Dec 9, 2008 at 6:06 AM, Al Johnson <[EMAIL PROTECTED]> wrote: > On Tuesday 09 December 2008, Paul wrote: >> I have tried out the testing image several times installing it several >> ways, even flashing the latest image. >> >> Has anyone had any success with them? These images do not seem to be >> able to connect to the gsm network. > > Need to know which distro you're asking about as FSO, SHR and OM (2008.x) all > have testing images. Convention has it you should stick the distro(s) you're > asking about in the subject line. It also helps to use the date of the image > as the testing builds are updated daily, and breakages may only apply to > certain dates. > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- Paul Email - [EMAIL PROTECTED] There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Testing build
On Tuesday 09 December 2008, Paul wrote: > I have tried out the testing image several times installing it several > ways, even flashing the latest image. > > Has anyone had any success with them? These images do not seem to be > able to connect to the gsm network. Need to know which distro you're asking about as FSO, SHR and OM (2008.x) all have testing images. Convention has it you should stick the distro(s) you're asking about in the subject line. It also helps to use the date of the image as the testing builds are updated daily, and breakages may only apply to certain dates. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR] linphone without /usr/bin/linphone
On Tuesday 09 December 2008, Julien Cassignol wrote: > On Tue, Dec 9, 2008 at 1:32 AM, Joachim Ott <[EMAIL PROTECTED]> wrote: > > Yes, this install the commandline client. And the graphical client? When > > I click on the icon, it wants to execute linphone and not linphonec. > > None was built. Find a good one, or tell me what is the name of the bb > recipe for a good not CLI client, and I'll build it :-) linphone is a good lightweight client, but the bb version is rather out of date, and there's a dependency problem regarding libosip2 which needs to be a 2.x version. And we don't get the GUI. Someone had a working linphone 2.x with GUI, and patches to switch the alsa state for ringing and call pickup. Another option might be to use telepathy. This gives us a dbus API for IM and VoIP so we could add it directly to the voice and messaging GUIs. This cuts across the FSO call control interface somewhat though, as I understood that was intended to become a universal interface to voice calling methods. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR] linphone without /usr/bin/linphone
On Tue, Dec 9, 2008 at 1:32 AM, Joachim Ott <[EMAIL PROTECTED]> wrote: > Yes, this install the commandline client. And the graphical client? When I > click on the icon, it wants to execute linphone and not linphonec. None was built. Find a good one, or tell me what is the name of the bb recipe for a good not CLI client, and I'll build it :-) -- Julien Cassignol http://www.ainulindale.net ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: cu: Permission denied
luca pisani wrote: > Hello.. > I'm trying to change u-boot options for boot a larger kernel > (http://people.openmoko.org/sean_mcneil/uImage-android) > I'm doing (with neo in "flashing mode" Power+Aux): > > /bash-3.1$ su - > Password: > [EMAIL PROTECTED]:~# dmesg | tail > usbcore: registered new interface driver cdc_acm > drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for > USB modems and ISDN adapters > usb 3-1: new full speed USB device using uhci_hcd and address 4 > usb 3-1: configuration #1 chosen from 2 choices > drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It > is no modem. > cdc_acm 3-1:1.0: ttyACM0: USB ACM device > [EMAIL PROTECTED]:~# cu -l /dev/ttyACM0 > cu: creat (/var/lock/TMP000e56): Permission denied > cu: /dev/ttyACM0: Line in use > [EMAIL PROTECTED]:~# l /dev/ttyACM0 > crw-rw 1 root uucp 166, 0 2008-12-09 00:54 /dev/ttyACM0 > [EMAIL PROTECTED]:~# chown uucp.uucp /dev/ttyACM0 > [EMAIL PROTECTED]:~# l /dev/ttyACM0 > crw-rw 1 uucp uucp 166, 0 2008-12-09 00:54 /dev/ttyACM0 > [EMAIL PROTECTED]:~# cu -l /dev/ttyACM0 > cu: creat (/var/lock/TMP000e75): Permission denied > cu: /dev/ttyACM0: Line in use > sudo chown uucp.uucp /dev/ttyACM0 sudo cu -l /dev/ttyACM0 it's work for me. > /I was able to connect to u-boot in the past, I'm wondering what's > happening now? > > Bye Luca > PS: Before, I tryed Qi with no luck. > > > > > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: cu: Permission denied
> cu: creat (/var/lock/TMP000e75): Permission denied have a look at /var/lock/ -- anything unusual? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
