Re: GPS vs. TDOA (was Re: release date)
Andrew, I used both Garmin Ique and Cellphone based-GPS. I can give you hard examples why no corporation that does service calls at this moment would even consider cell-based GPS. I visit customers all over the US and Canada. Out of the 50 or so visits there were about 20 with no cellphone coverage in remote areas where sawmills are located. On the contrary, my Garmin GPS worked flawlessly everywhere. You have no idea what a PITA it is to get to an airport in the middle of the night, with the cell-gps guiding you out of the city and then just dies when you get rural. Furthermore, in order to solve the problem, you will have to carry 3 or four simcards from different carriers since the coverage maps are different for different areas. If you stick to urban areas here in the USA, fine cell-based gps works fine. If you do corporate time critical traveling and service just get a REAL gps such as Garmin or what the FIC NEO will be able to have. If you want to lose money in the services industry here in the US...go ahead use a cellphone to guide you. Been there done that, late or lost every time. AGAIN: I would at this moment not mind to get a Fic Neo if it can make calls and receive calls and it will be nice to get the software upgrades and see it evolve. I just cannot buy the APPLE I-Phone. It is a dead end FIC NEO lookalike , however nice it is. The Iphone is a nice city phone gizmo, not a real business assistant . The FIC has a real chance to become a real travel assistant, but you have to get the basic phones in our hands as soon as the hardware is the final version, else you will make FIC miss the buss. If it receives call dials, have an address book and the hardware is finalized...get it out! Andrew Becherer wrote: On 5/19/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I think you guys need to get this out asap. The only reason I do not buy the iphone right now is because it does not have GPS. I think my question is why is everybody freaking out about the iPhone not having GPS? It will report location as close as 30 meters, usually within 100 meters and almost always within 300 meters. This accuracy is good enough for most applications. Even better cellular TDOA is accurate inside building as well as outside buildings (which in my experience GPS is not). Are location detection services like TruePosition's U-TDOA (used by Cingular and T-Mobile in the USA) not available internationally? So why is GPS the killer functionality the Neo has over the iPhone? (note: I understand why the OpenMoko development platform is better than the iPhone. I'm just talking about GPS vs. carrier provided location detection.) ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: information efficient text enty using dasher
Hi, I'm one of the Dasher developers, and am also interested in hacking on OpenMoko. So, getting Dasher going is fairly likely. This pretty much means that you have to stare at the display all the time when inputting text. Yes, this is the main difference between Dasher and T9. However, the comments about needing a lot of screen resolution or CPU aren't so true -- we did Dasher on the iPaq seven years ago at full-speed and using 150x150 resolution, and it works great. The reason we get away with not so much resolution is that you're only really ever being asked to choose between five or so probable letters at each turn, and it doesn't take much screen space to show those, and you can predict whereabouts you're headed by knowing the alphabetic order of which character comes next. Sure - in theory, dasher may approach arithmetic coding in terms of information input. (I'm not sure what you mean by approach -- Dasher *is* an arithmetic coder, and matches the information-theoretic efficiency of one in terms of bits/input to characters/output.) But unless you can do the coding in your head, you've got to stare at the screen, making it less useful for environments where you've got vibration, sunlight, walking down the street, or less likely for a phone, if you're blind. Yes, but the Neo doesn't have a keyboard, and doesn't have keys for T9 that you can use without looking at the screen, so I don't think this is a useful criticism. Dasher's very tolerant of vibration and mistakes, unlike T9 on a touchscreen -- it's much like driving a car, in that if you oversteer or understeer you just correct yourself later, because it's all about navigation and where you end up. We can type easily over 20wpm on the iPaq with a touchscreen and stylus. Thanks! - Chris. -- Chris Ball [EMAIL PROTECTED] One Laptop per Child ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GPS vs. TDOA (was Re: release date)
So why is GPS the killer functionality the Neo has over the iPhone? I just came back from presenting OpenMoko at a BoF session at Where 2.0, and the overwhelming opinion there was that access to the raw GPS data that is unavailable on all other GPS platforms is what sets OpenMoko apart. There was no question of comparison to iPhone or other GPS-enabled platforms. These are the people thinking about future location-aware devices and applications. Existing GPS-aware devices are still narrow in their perspective of why you might want this information, and allow access (in varying degrees) only within this view. The frustration in this community is that if you want the raw data for other uses, you can't get it. Mind you, I'm no expert in this field. I barely know what I'm talking about, so my understanding and my conveyence of this to you may be inaccurate and is no doubt incomplete. But there was no doubting the interest, and the clear understanding that to the Where 2.0 crowd OpenMoko presents opportunities that are completely unavailable elsewhere unless they build their own (e.g. SVHMPC). I hope some of those people join this list soon and will correct me. Michael ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: information efficient text enty using dasher
Thank you for this post chris, nice to know, that dasher was running on a so old and slow device already. I'm see the things like you do: Touchscreen means you always have to stare at the device for making inputs. Like I said - I had a nokia 7710 before and it was nearby impossible to use it blind. Even if you had a fullscreen T9-keyboad with huge keys you had to check the display, because you cannot feel which key you are pressing. I also like the driving a car comparison :) 2007/5/30, Chris Ball [EMAIL PROTECTED]: Hi, I'm one of the Dasher developers, and am also interested in hacking on OpenMoko. So, getting Dasher going is fairly likely. This pretty much means that you have to stare at the display all the time when inputting text. Yes, this is the main difference between Dasher and T9. However, the comments about needing a lot of screen resolution or CPU aren't so true -- we did Dasher on the iPaq seven years ago at full-speed and using 150x150 resolution, and it works great. The reason we get away with not so much resolution is that you're only really ever being asked to choose between five or so probable letters at each turn, and it doesn't take much screen space to show those, and you can predict whereabouts you're headed by knowing the alphabetic order of which character comes next. Sure - in theory, dasher may approach arithmetic coding in terms of information input. (I'm not sure what you mean by approach -- Dasher *is* an arithmetic coder, and matches the information-theoretic efficiency of one in terms of bits/input to characters/output.) But unless you can do the coding in your head, you've got to stare at the screen, making it less useful for environments where you've got vibration, sunlight, walking down the street, or less likely for a phone, if you're blind. Yes, but the Neo doesn't have a keyboard, and doesn't have keys for T9 that you can use without looking at the screen, so I don't think this is a useful criticism. Dasher's very tolerant of vibration and mistakes, unlike T9 on a touchscreen -- it's much like driving a car, in that if you oversteer or understeer you just correct yourself later, because it's all about navigation and where you end up. We can type easily over 20wpm on the iPaq with a touchscreen and stylus. Thanks! - Chris. -- Chris Ball [EMAIL PROTECTED] One Laptop per Child ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Any updates?? now that we have passed the original date for the second test production run.
I am still waiting on baited breathe for news. I know that the original test run that was slated for a couple weeks ago got pushed back, but what about the second run that was supposed to happen. How did the run go (if there has been a run yet). More problems? What about the phase 1+ specs?? Basically, any news?? ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: information efficient text enty using dasher
There's always the multipress key input method: http://www.robocal.com/prod/robocal/robodicto.php It's low-tech, and works on all phones, since the logic is in the server. I admit it's a bit tedious, but, ... Ted Gilchrist On 5/31/07, Thomas Gstädtner [EMAIL PROTECTED] wrote: Thank you for this post chris, nice to know, that dasher was running on a so old and slow device already. I'm see the things like you do: Touchscreen means you always have to stare at the device for making inputs. Like I said - I had a nokia 7710 before and it was nearby impossible to use it blind. Even if you had a fullscreen T9-keyboad with huge keys you had to check the display, because you cannot feel which key you are pressing. I also like the driving a car comparison :) 2007/5/30, Chris Ball [EMAIL PROTECTED]: Hi, I'm one of the Dasher developers, and am also interested in hacking on OpenMoko. So, getting Dasher going is fairly likely. This pretty much means that you have to stare at the display all the time when inputting text. Yes, this is the main difference between Dasher and T9. However, the comments about needing a lot of screen resolution or CPU aren't so true -- we did Dasher on the iPaq seven years ago at full-speed and using 150x150 resolution, and it works great. The reason we get away with not so much resolution is that you're only really ever being asked to choose between five or so probable letters at each turn, and it doesn't take much screen space to show those, and you can predict whereabouts you're headed by knowing the alphabetic order of which character comes next. Sure - in theory, dasher may approach arithmetic coding in terms of information input. (I'm not sure what you mean by approach -- Dasher *is* an arithmetic coder, and matches the information-theoretic efficiency of one in terms of bits/input to characters/output.) But unless you can do the coding in your head, you've got to stare at the screen, making it less useful for environments where you've got vibration, sunlight, walking down the street, or less likely for a phone, if you're blind. Yes, but the Neo doesn't have a keyboard, and doesn't have keys for T9 that you can use without looking at the screen, so I don't think this is a useful criticism. Dasher's very tolerant of vibration and mistakes, unlike T9 on a touchscreen -- it's much like driving a car, in that if you oversteer or understeer you just correct yourself later, because it's all about navigation and where you end up. We can type easily over 20wpm on the iPaq with a touchscreen and stylus. Thanks! - Chris. -- Chris Ball [EMAIL PROTECTED] One Laptop per Child ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Botcast Network: http://www.botcastnetwork.com ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: information efficient text enty using dasher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 And it's completely not relevant, as the Neo needs an input method that works for local apps ;) Andreas Ted Gilchrist wrote: There's always the multipress key input method: http://www.robocal.com/prod/robocal/robodicto.php It's low-tech, and works on all phones, since the logic is in the server. I admit it's a bit tedious, but, ... Ted Gilchrist On 5/31/07, *Thomas Gstädtner* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Thank you for this post chris, nice to know, that dasher was running on a so old and slow device already. I'm see the things like you do: Touchscreen means you always have to stare at the device for making inputs. Like I said - I had a nokia 7710 before and it was nearby impossible to use it blind. Even if you had a fullscreen T9-keyboad with huge keys you had to check the display, because you cannot feel which key you are pressing. I also like the driving a car comparison :) 2007/5/30, Chris Ball [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Hi, I'm one of the Dasher developers, and am also interested in hacking on OpenMoko. So, getting Dasher going is fairly likely. This pretty much means that you have to stare at the display all the time when inputting text. Yes, this is the main difference between Dasher and T9. However, the comments about needing a lot of screen resolution or CPU aren't so true -- we did Dasher on the iPaq seven years ago at full-speed and using 150x150 resolution, and it works great. The reason we get away with not so much resolution is that you're only really ever being asked to choose between five or so probable letters at each turn, and it doesn't take much screen space to show those, and you can predict whereabouts you're headed by knowing the alphabetic order of which character comes next. Sure - in theory, dasher may approach arithmetic coding in terms of information input. (I'm not sure what you mean by approach -- Dasher *is* an arithmetic coder, and matches the information-theoretic efficiency of one in terms of bits/input to characters/output.) But unless you can do the coding in your head, you've got to stare at the screen, making it less useful for environments where you've got vibration, sunlight, walking down the street, or less likely for a phone, if you're blind. Yes, but the Neo doesn't have a keyboard, and doesn't have keys for T9 that you can use without looking at the screen, so I don't think this is a useful criticism. Dasher's very tolerant of vibration and mistakes, unlike T9 on a touchscreen -- it's much like driving a car, in that if you oversteer or understeer you just correct yourself later, because it's all about navigation and where you end up. We can type easily over 20wpm on the iPaq with a touchscreen and stylus. Thanks! - Chris. -- Chris Ball [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] One Laptop per Child ___ OpenMoko community mailing list community@lists.openmoko.org mailto:community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org mailto:community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Botcast Network: http://www.botcastnetwork.com ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGXxTLHJdudm4KnO0RAv7XAKC91ayYJcdRXsfYdAxHTRNQKsKXcgCgyE8Z GkKS6RV3tVh+HXord4O1e2E= =H7/e -END PGP SIGNATURE- ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: information efficient text enty using dasher
I gotta say that I just tried the Dasher applet and after just a little bit of practice was humming along. I am very excited that this may (will g) be available on openMoko. On 5/29/07, Chris Ball [EMAIL PROTECTED] wrote: Hi, I'm one of the Dasher developers, and am also interested in hacking on OpenMoko. So, getting Dasher going is fairly likely. This pretty much means that you have to stare at the display all the time when inputting text. Yes, this is the main difference between Dasher and T9. However, the comments about needing a lot of screen resolution or CPU aren't so true -- we did Dasher on the iPaq seven years ago at full-speed and using 150x150 resolution, and it works great. The reason we get away with not so much resolution is that you're only really ever being asked to choose between five or so probable letters at each turn, and it doesn't take much screen space to show those, and you can predict whereabouts you're headed by knowing the alphabetic order of which character comes next. Sure - in theory, dasher may approach arithmetic coding in terms of information input. (I'm not sure what you mean by approach -- Dasher *is* an arithmetic coder, and matches the information-theoretic efficiency of one in terms of bits/input to characters/output.) But unless you can do the coding in your head, you've got to stare at the screen, making it less useful for environments where you've got vibration, sunlight, walking down the street, or less likely for a phone, if you're blind. Yes, but the Neo doesn't have a keyboard, and doesn't have keys for T9 that you can use without looking at the screen, so I don't think this is a useful criticism. Dasher's very tolerant of vibration and mistakes, unlike T9 on a touchscreen -- it's much like driving a car, in that if you oversteer or understeer you just correct yourself later, because it's all about navigation and where you end up. We can type easily over 20wpm on the iPaq with a touchscreen and stylus. Thanks! - Chris. -- Chris Ball [EMAIL PROTECTED] One Laptop per Child ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
