Re: GPRS for FSO Milestone 2
C R McClenaghan schrieb: > I've been able to hack together the necessary ppp scripts to get GPRS > working on FSO Milestone 2 release. Cool! > I'll post something to the wiki if there's sufficient interest. It is, please do! Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: service with NorthState in NC
Michael Shiloh schrieb: > As I understand it, your cellphone network provider routinely updates > hardware and software in their system. As a result of this, occasionally > older SIM cards may not function. Unfortunately, this isn't the issue. Rather, both GTA01 and GTA02 have problems with a certain model of SIM cards (Gemplus 3G), which unfortunately is widely used. The bug is specific to the combination of TI Calypso (the GSM modem used in OM phones) and this Gemplus smartcard. My bet here is on some timing issue, possibly related to incorrect ATR parsing. Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: numptyphysics ipk
Steven ** schrieb: > That would be handy to be able to reset. How do you activate the > keyboard? I'm guessing you're using a different distro than me... You press the "querty" button on the top left. FSO-user here... Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Warranty after fix for GTA02 GPS rework for SD card interferenceissue
Al Johnson schrieb: > We only need to replace 1 of the 2 3D accels with a 3D gyro. I've not looked > at the size or cost of solid state gyros so I don't know how practical that > might be. Well, if this: http://www.invensense.com/products/idg_300.html had three axes instead of two, it would be suitable... it's designed for small size and low cost. All other gyros I've found so far are too big for a mobile phone application. Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Warranty after fix for GTA02 GPS rework for SD card interferenceissue
Vinc Duran schrieb: >> But... what are our chances GTA03 will have a 3D gyro? > Could the accelerometers be substituted for a 3d gyro? No, you need both accelerometer *and* gyro measurements for dead reckoning. Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Warranty after fix for GTA02 GPS rework for SD card interferenceissue
Brian Wilson schrieb: > See http://www.trimble.com/tms/placer450.aspx?dtID=overview > > They use a small gyroscope. [...] > If you are walking around and want a reasonable position the Kalman > filter would probably be easier to deal with. > Is there a mathematician in the house? I'm not a mathematician, but I think I have sufficiently understood Kalman filters and dead reckoning. A little known trick is to use ordinary integration with the strap-down equation given the accelerometer and gyro input, and have the Kalman filter model the error terms instead of the physical model state space. This way, you only have to update the Kalman filter every time you get a GPS fix, not every time you get a measurement from the other sensors. But... what are our chances GTA03 will have a 3D gyro? Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Importing contacts in FSO
Marco Trevisan (Treviño) schrieb: > Thanks for this, BTW during the past night I looked to the Zhone code > and I got that it was using only the sim, so I've "forced" it to use > only my phonebook hardcoding there my phonebook as shown in the "Fake > phonebook" code. What I'd like to do is merging these contacts with the > one saved on the SIM, so I'll be able to save new contacts (and view > them) too... Well, just execute both branches of the if...else in pyphone_contacts.prepare. Make sure you use unique reference numbers for the stuff you add yourself, e.g. start numbering at 1000, not at 1 as in the "Fake phonebook". Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Warranty after fix for GTA02 GPS rework for SD card interferenceissue
steve schrieb: > Amaybe when SD I/O occurs one could use the accelerometers to dead reckon? Dead reckoning without gyros is pretty hard. In theory, the two accelerometers are not mounted in the same place and thus could be used to derive rotation, but in practice they're pretty close to each other, and given the noise of measurement one is unlikely to derive a good rotation from them. Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Importing contacts in FSO
Marco Trevisan (Treviño) schrieb: > After the infos written about Qtopia/ASU and OM.GTK, how could I import > my contacts in FSO? Milestone II is so nice!! > > Maybe I should write a python script based on the zhone code or is there > already something for doing it? As far as I know, there's no import code yet. Be aware that currently FSO doesn't have a contacts database, it stores all the contacts on the SIM (which usually has limited capacity). The API for storing contacts is pretty simple at the moment. If you steal the dbus init code from zhone, adding contacts is done using: dbus_object.gsm_sim_iface.StoreEntry(reference, name, number) where reference indicates the slot on the SIM card in which to store the entry (between 0 and whatever the maximum for the card is). Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Where is FSO Milestone 2 for FreeRunner
Maciej Piechotka schrieb: > 1. On http://downloads.openmoko.org/framework/milestone2/ there is no jffs2 > image for FreeRunner. Is there any? There's a .jffs2.summary file, which is the one you're supposed to use. Summary is a jffs2 feature that improves performance. For more information, see http://www.inf.u-szeged.hu/jffs2/mount.php . > 2. Can I expect that I'll be notified by system if I'll recive an SMS or I > need > to wait on M3? There's no notification yet. The focus of M2 is on the framework APIs, the UI (zhone) only does a minimum, and is more to be understood as an example of using the API. Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
illume keyboard button (was Openmoko on Design)
Dear community and OM Powers That Be, I have read the "Openmoko on Design" thread with a certain alienation. I'll try to resist the temptation to pick up one of the many flame baits, but even after sleeping it over for a night, I feel inclined to comment on the issue here. First, I think that the complaints of users about "the phone should know when it expects keyboard input, and automatically bring up the keyboard" are right. The work going into this direction is correct. However, there are situations when a manual override is needed. The automatic detection could be wrong, for instance. But much more important: the user could be in a situation where keyboard input is theoretically possible, but not currently desired, because the keyboard is taking away screen real estate. This happened to me yesterday, when I was sitting in the train, and reading some code using the terminal application. So, in my opinion, the decision to remove the button is incorrect. Even more so, the strong reaction of the users should have been an indication that the decision was incorrect. It's always a good idea to listen to your users. It has been said that, since OpenMoko is an open project, the community has the chance to come up with a different solution. Now let's take a look at what the community (read: folks who actually write code instead of participating in lengthy discussions) did, the day the button was removed from illume: http://gitweb.openembedded.net/?p=org.openembedded.dev.git;a=blob;f=packages/openmoko-projects/illume/configure-keyboard.patch;h=589fe53f38afc59be95a13ed67a9f9d1fc452148;hb=HEAD They re-enabled the feature in their branch, and went on with their life. However, the patch stopped applying this morning, and I had to lock down illume to r170. Raster: if you could make the keyboard button a configuration option, as in the above patch, you'd make me and a couple of other people happy. Thanks in advance. Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
