Funny thing happened on the way to making a call...
Using the latest (as of 7/18) release version, I tried to enter and address book entry for my other phone. Was a bit difficult, but I thought I had succeeded. After getting it entered, I tried to dial using that entry. What happened, instead, was that it used one of the SIM card addresses for 411 and dialed IT instead. The call log, however, showed a completely BLANK phone number. Sure am glad I didn't have a 911 in the SIM card... I'm hoping to get back to looking at the source code soon, but I'm still trying to the the whole thing to compile without errors (Using MokoMakefile.) Makes it mostly through (after about 10 hours) but stops about 4200 of 4500 (approximately.) I scrupulously checked to make sure I've done all of the steps used for setting up from the Wiki. How reliably has the source tree been as for being in a compilable state throughout? I remember back with OE on the Zaurus days, it seemed that about 9 out of 10 days I tried it, something trivial was broken. Stuff checked in that didn't compile or dependencies that didn't get updated. Still, things are progressing nicely. This will be a awesome device when the software reaches maturity. My neice has stolen my second FR so she can show her friends a phone that noone else can get. She's suffering through some of the warts and thorns at the moment, but she is patient (at least reasonably patient for a 15 year old...) I wish I could contribute more (I'm planning to do a couple of python applets that will temporarily allow me to do some Wifi and GPRS setups until the 'real' thing comes down the pike. I'll post a link when they are ready.) -Gary ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Funny thing happened on the way to making a call...
This was from a clean reflash of the kernel and rootfs. I tried a opkg update/upgrade, but nothing was more recent. -Gary [EMAIL PROTECTED] wrote: On Fri, Jul 18, 2008 at 02:29:33PM -0700, Gary Oliver spake thusly: Using the latest (as of 7/18) release version, I tried to enter and How are you upgrading versions? Do you flash or use opkg? I am trying to upgrade with opkg and something always goes wrong. Last night I started an opkg upgrade and next thing I know my phone is off and unresponsive. I had to take out the battery to reboot it. I am also still unclear on flashing vs opkg uprade. What's the difference? If opkg works they would seem to do the same thing. One time I tried opkg upgrade I even saw it writing a kernel to flash. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found!
Tried the GPS last night with SD card in place - have yet to try it without... Initial fix, with 9 satellites in constellation, 6 about -140dBm, took 11 minutes. After that, tracking was good and it even worked 'mostly' in my house. (I have most of my living area covered with solar panels, so there's this big 'screen' that blocks most GPS signal, but it DID work with 4 satellites remaining in the constellation.) One this I did do, though, was to tweek what I believe is described as the external antenna connector. It appeared to not be completely connected or seated, so I twisted it about 10 degrees and reseated it. I will try it this evening without the SD card. However, I agree with a previous poster, that if this doesn't work reliably WITH the SD, then I've bought something I can't really use. I absolutely do NOT want to start adding external antennas to this thing in order to get basic functionality. -Gary Christoph Anton Mitterer wrote: Hi. I can only partly confirm this With SD card removed,... I took 291 s (in my first tests) from inside a building but on the window. If I'm not at the windows but deeper (2m from the window away) inside the building,.. it seems that I still don't get a fix. Anyway,... I had it before (with SD card inserted) that I got a fix in 4 mins,.. ok this happened only once. However,.. I think even 291 s is to much,.. other devices like TomTom are worlds better... And I've read in this thread, that people got a fix 30 s . Was this from a cold start? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Shipping notice received for 1445
I received my shipping notice today (at 1700 PDT) with expected delivery on Monday, July 14. Looks like I'll get my second phone first since the Pacific Northwest group buy hasn't heard its slot yet. It's a good thing it isn't coming this week. I have too much stuff to do and I know I wouldn't get ANY of it done if the FR arrived tomorrow :-) Finally! -Gary ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem compiling openmoko with MokoMakefile
Mark Chandler wrote: Gary Oliver wrote: I've been trying to get the openmoko build (using the super Makefile) to go for the last few days without complete success. ... I had the same problem today. Rod W. let me know that there's now a fix in place for it. a make update brought in the changes and the subsequent build completed ok. My make openmoko-devel-image has cruised past that former roadblock. Thanks! -Gary ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Problem compiling openmoko with MokoMakefile
I've been trying to get the openmoko build (using the super Makefile) to go for the last few days without complete success. I believe I've followed the instructions with respect to the system requirements, and the build DOES get through about 12 hours of work (about 400meg has been downloaded and the build directory contains about 5 Gb before failing, so it seems to be quite well along. The failure comes at: NOTE: package gtk+-directfb-2.10.9-r0: task do_fetch: completed NOTE: package gtk+-directfb-2.10.9-r0: task do_unpack: started NOTE: Unpacking /home/go/Projects/openmoko/sources/gtk+-2.10.9.tar.bz2 to /home/go/Projects/openmoko/build/tmp/work/armv4t-linux/gtk+-directfb-2.10.9-r0/ NOTE: package gtk+-directfb-2.10.9-r0: task do_unpack: completed NOTE: package gtk+-directfb-2.10.9-r0: task do_patch: started NOTE: Applying patch 'no-xwc.patch' ERROR: Error in executing: /home/go/Projects/openmoko/openembedded/packages/gtk+/gtk+-directfb_2.10.9.bb ERROR: Exception:exceptions.IOError Message:[Errno 2] No such file or directory: '/home/go/Projects/openmoko/openembedded/packages/gtk+/files/./no-xwc.patch' Which appears to be a failure to apply a patchfile no-xwc.patch which doesn't seem to be part of the source tree at this point. The files directory contains only migration.patch. Has anyone else seen this, and if so, what bit of detail in the instructions did I fail to notice that's causing this? FYI I have tried building from complete scratch a number of times (blowing away everything except the Makefile) in hopes that I'd simply polluted my local tree somehow. Didn't fix it. A quick google for this file netted me several different variations, so am not quite sure what no-xwc patches are required for OE/OpenMoko. Am running a fairly stock Debian testing system on an 32 bit AMD platform. No apparent shortage of disk space. Thanks for any help, Gary ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
