Re: Idea of a voice mail application
Marco Trevisan (Treviño) ha scritto: Pietro m0nt0 Montorfano ha scritto: In italy the caller will pay for the call but the recipient no, as a recipient if the caller will leave the message on the carrier message box (don't know how to translate, pardon) i have to call it and listen the messages in a slw and bad way, paying for the call. Well, yes! But now the caller can avoid to pay to leave a message to the carrier (he has just to stop the call). With a local answer machine he couldn't! yes but usually if the caller is calling you it's in his plan to pay the phone call, so if you can use the voice mail application on your phone it's up to you. So it doesn't matter the costs and who is paying as i've understood the prices are different for every operator and even for every country so the only thing that should be useful is would you like an app like that? For me the answer is YS :D (actually i don't have time to develop it but i can help a little bit) Bye Pietro ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Virtual QWERTY Keyboards to be used with Fingers...
On Sat, 01 Mar 2008 08:47:31 +0100 Karsten Ensinger [EMAIL PROTECTED] babbled: Sorry to jump into the thread this late, but I am wondering if you already examined the following Wiki-Link? We had a very extensive discussion about text input running on the community list several months ago. Nearly all proposals were documented on the following Wiki: http://wiki.openmoko.org/wiki/Wishlist:Text_Input My personal favourites are the Quickwriting (there is even a java demo available) and another text input (although it seems to be another implementation of this more moko-like implementation: http://www.micropp.se/openmoko/splash.html ). If I remember correctly, all participants of the discussion came to the conclusion, that a regular qwerty keyboard is not sufficient no matter how clever you pimp it, due to restriction of precision of finger typing and lack of screen space. i disagree. reality of the qtopia predictive keyboard and actual use of it disagrees. talk and theory is fine - actual code that works is disagreeing. users of that code are disagreeing. An intelligent input prediction (e.g. T9) sucks, when one is using different languages regularly (you always have to remember switching to the right dictionary BEFORE typing). ( Not everyone on this planet is using english in day to day conversations. ;-) ) sure - but t9 is ambiguous. it REQUIRES a lookup or multi-press (turn t9 off) to be useful. i was talking of an error correction system that uses dictionaries. if you use a stylus the error correction never needs to take place - if you use a finger it will be needed. but it doesn't predict. it corrects - much like a spell checker does. different from t9. the other keyboard entry methods there are much harder to learn to use. you add a barrier of entry for many people. if others wish to pursue these funky keyboard entries - please do. i don't intend to to start with. i intend todo a qwerty style keyboard with multiple configurable layouts (eg qwerty, then a numberpad entry - u can have a more complicated terminal hacker entry etc.) as for dictionaries - that's part of life i guess. anyone is free to work on another keyboard if they want. in the end the proof is in the pudding. who will go and actually write code. you can have all the ideas in the world, but he who puts them into code and makes them usable by others wins :) so don't stop- please, work on alternate input methods. i am going with the one i have seen work, demonstrated live on a Neo and used. They also suck if ones vocabulary is much more advanced than the one which is implemented (and I personally do not want to adjust my vocabulary to fit the needs of the input system). thats why dictionaries can be added to, imported, words learnt automatically and added, etc. etc. :) Just my 2 cents. Regards Karsten ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Carsten Haitzler (The Rasterman) [EMAIL PROTECTED] ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Virtual QWERTY Keyboards to be used with Fingers...
On 3/1/08 Carsten Haitzler (The Rasterman) wrote: On Sat, 01 Mar 2008 08:47:31 +0100 Karsten Ensinger [EMAIL PROTECTED] babbled: Sorry to jump into the thread this late, but I am wondering if you already examined the following Wiki-Link? We had a very extensive discussion about text input running on the community list several months ago. Nearly all proposals were documented on the following Wiki: http://wiki.openmoko.org/wiki/Wishlist:Text_Input My personal favourites are the Quickwriting (there is even a java demo available) and another text input (although it seems to be another implementation of this more moko-like implementation: http://www.micropp.se/openmoko/splash.html ). If I remember correctly, all participants of the discussion came to the conclusion, that a regular qwerty keyboard is not sufficient no matter how clever you pimp it, due to restriction of precision of finger typing and lack of screen space. i disagree. reality of the qtopia predictive keyboard and actual use of it disagrees. talk and theory is fine - actual code that works is disagreeing. users of that code are disagreeing. I have to agree with Raster here. Trolltech did an amazing job on their QWERTY (onscreen) keypad. I highly recommend you trying it out on the Neo if you haven't already. Personally, I think it's the best touchpanel keyboard on the market now. Bar none. Sean ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Virtual QWERTY Keyboards to be used with Fingers...
Sean Moss-Pultz wrote: On 3/1/08 Carsten Haitzler (The Rasterman) wrote: On Sat, 01 Mar 2008 08:47:31 +0100 Karsten Ensinger [EMAIL PROTECTED] babbled: If I remember correctly, all participants of the discussion came to the conclusion, that a regular qwerty keyboard is not sufficient no matter how clever you pimp it, due to restriction of precision of finger typing and lack of screen space. i disagree. reality of the qtopia predictive keyboard and actual use of it disagrees. talk and theory is fine - actual code that works is disagreeing. users of that code are disagreeing. I have to agree with Raster here. Trolltech did an amazing job on their QWERTY (onscreen) keypad. I highly recommend you trying it out on the Neo if you haven't already. Personally, I think it's the best touchpanel keyboard on the market now. Bar none. Sean I am afraid, I have to admit that I have NOT tried the Trolltech stuff at all. Maybe because I thought I would deceive the openmoko movement by trying other stuff on the Neo. ;-) I will give it a try until next weekend and will change my mind if it is as cool as you claim. Regards ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Idea of a voice mail application
On 29 Feb 2008, at 17:34, Marco Trevisan (Treviño) wrote: siaPeter Trapp ha scritto: Hi everybody, I thought about the possibility of a voice mail installed on the neo. The idea is to let the application decide if you are reachable for the caller or not. The decision will be done on profiles (time, who is calling, what to do (let it ring or answer directly) ). Eg: Saturday 10:00pm and your boss is calling (and you have a signal) Neo is aware that it is weekend and who is calling. It just turns on the voice mail... Dear Boss, actually it is weekend and I just don't want to get some work right now. Sorry, my neo will not even inform me that you've called. So don't try again later. It would not help until Monday 9am! Have a nice weekend --- without the possibility to leave a message ;) I would like this feature also, and really I assumed it would become a commonplace usage on OpenMoko. Cool, but your caller will pay for this.. So maybe it won't be so happy :P Stuff the caller. I carry a mobile phone so I can make outgoing calls when I'm away from home, not so I can be interrupted in the middle of a conversation. If someone is calling me they assume that they're going to incur the cost of a call, anyway, so I don't see that the cost of a call to voicemail is a large imposition (it is probably better than me answering my phone to say stuff you, at least). Stroller. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Problem trying to build qemu-local using MokoMakefile
Hi, Trying to run make qemu-local, I got the following message, some lines after Please wait, programming the NAND flash... -8---8---8---8---8-- neo_vib_switch: Vibrator stopped. neo_bl_switch: LCD Backlight now on. qemu: fatal: Trying to execute code outside RAM or ROM at 0x -8---8---8---8---8-- (More detailed trace can be found here: http://pastebin.com/m239ade67) Any idea? Thanks in advance. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GTA02 Battery Capacity (Was: Re: More about the GTA02)
Andy Green ha scritto: Depends on what you're doing with it... is the backlight on all the time... making a call... I can't give you a straight answer because I didn't examine this yet. Instead I spent all my time around power consumption looking to optimize suspend current since that can involve circuit changes. That's reasonable... Btw I know that the neo is more a computer than a phone, so its power compsumation depends much on what you're doing with it; btw let's consider it only just as a phone, and so I'm curious about the two standard values that generally vendors claim: standby time and conversation time. For suspended time with GSM modem off we have the consumption down to ~2mA and I expect that will improve further by software changes, so on a 1200mAh battery like we ship maybe it can last 20 days (unverified!) doing nothing at the moment. With GSM modem on in suspend maybe 5 days Ok, 5 days of standby time is quite good, but could it be greater? I've heard that the iPhone, for example, has a standby-time really much long... Whatever the figure is for usage time it will change by a factor of 5 or 10 depending if you run the GSM transmitter, wifi, CPU is always busy, GPS, and the worst suspect the backlight, so you need to define exactly what you do with the device during this usage to get a meaningful figure. Of course... Btw I think that my average day usage will be something like: GSM always working, wifi for about 1 or 2 hours, some sms (1 or 2) and calls (about half hour). In such conditions, do you have an idea about how much will the neo stay up? I'm also figuring another usage-way while traveling using both the GSM on standby and the GPS up (with a maps software): any idea about this? Bye -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Virtual QWERTY Keyboards to be used with Fingers...
Karsten Ensinger ha scritto: I am afraid, I have to admit that I have NOT tried the Trolltech stuff at all. Maybe because I thought I would deceive the openmoko movement by trying other stuff on the Neo. ;-) I will give it a try until next weekend and will change my mind if it is as cool as you claim. Ok, we're waiting for your report...! -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Virtual QWERTY Keyboards to be used with Fingers...
On 3/1/08, Sean Moss-Pultz [EMAIL PROTECTED] wrote: On 3/1/08 Carsten Haitzler (The Rasterman) wrote: On Sat, 01 Mar 2008 08:47:31 +0100 Karsten Ensinger [EMAIL PROTECTED] babbled: Sorry to jump into the thread this late, but I am wondering if you already examined the following Wiki-Link? We had a very extensive discussion about text input running on the community list several months ago. Nearly all proposals were documented on the following Wiki: http://wiki.openmoko.org/wiki/Wishlist:Text_Input My personal favourites are the Quickwriting (there is even a java demo available) and another text input (although it seems to be another implementation of this more moko-like implementation: http://www.micropp.se/openmoko/splash.html ). If I remember correctly, all participants of the discussion came to the conclusion, that a regular qwerty keyboard is not sufficient no matter how clever you pimp it, due to restriction of precision of finger typing and lack of screen space. i disagree. reality of the qtopia predictive keyboard and actual use of it disagrees. talk and theory is fine - actual code that works is disagreeing. users of that code are disagreeing. I have to agree with Raster here. Trolltech did an amazing job on their QWERTY (onscreen) keypad. I highly recommend you trying it out on the Neo if you haven't already. Personally, I think it's the best touchpanel keyboard on the market now. Bar none. Sean Maybe it is. I still hate it and any other form of predictive text input I have used so far. That doesn't mean I want to prevent anyone else from having it. I can understand that some people are happy with it and it would probably be a good idea to use it as the default input method. What I want is an alternative I can very easily switch to. We don't want the perfect input method because it probably doesn't exist. Let's agree on disagreeing and try to figure out a base set of alternative input mechanisms that should be included in Openmoko as well as making it easy for the user to install more of them. Some options I can think of that would find an audience: -Predictive QWERTY, maybe with different prediction modes (dictionary, closeness, combination, none) -Multitap 3*4 standard phone layout (maybe with optional prediction if patent issues can be avoided) -Dasher -A sliding method. My favorite, even though I never used one and don't really know which of the ideas floating around will be the best one. The next thing to consider is size. There are basically two options: -Use about 1/3 of the screen so that the running program is still visible. The problem with this is that the space is very small and some of the methods above would not work at this size or only work with a stylus. -Use pretty much the whole screen while inputting something and close the input method afterwards. This worked very well on my Palm device for two thumb landscape QWERTY input but that screen was twice as big as the Neo's. It is my prefered way of doing input because I don't need to see the program while typing. I only need to see about two lines of the text I last typed. For all methods where this makes sense, both sizes should be available. Last, let me describe my imaginary perfect input method: The input area is divided in 3*3 squares. A letter is written by starting on a defined square and moving over one square to end in a 3rd square. So every letter is a combination of 3 adjacent squares drawn in the right direction. Now here is what makes this fast and thus great: If the next letter you want to draw starts on the square you just ended on, you simply continue your slide and add two squares. This way, many letter combinations and even whole words could be written in one continuos sliding motion. There are 44 possible combinations (if I counted right) which should be plenty if we plan for a shift-combination and a numbers/special characters-combination. The character layout shouldn't follow any alphabet or QWERTY logic but instead be entirely based on language. The reason is that it would require learning from the ground up anyway so it should be as fast as possible once you have learned it. The small version for only taking up 1/3 of the screen would be perfect in 2*5 which would also result in 44 combinations (again, if I counted them right...). Feedback and actual implementation of this would be very welcome! In fact, I offer 30 Paypal €uros to the first person to make this work on my Neo (meaning it has to come with simple installation instructions). Ortwin ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Virtual QWERTY Keyboards to be used with Fingers...
On 3/1/08, Ortwin Regel [EMAIL PROTECTED] wrote: On 3/1/08, Sean Moss-Pultz [EMAIL PROTECTED] wrote: On 3/1/08 Carsten Haitzler (The Rasterman) wrote: On Sat, 01 Mar 2008 08:47:31 +0100 Karsten Ensinger [EMAIL PROTECTED] babbled: Sorry to jump into the thread this late, but I am wondering if you already examined the following Wiki-Link? We had a very extensive discussion about text input running on the community list several months ago. Nearly all proposals were documented on the following Wiki: http://wiki.openmoko.org/wiki/Wishlist:Text_Input My personal favourites are the Quickwriting (there is even a java demo available) and another text input (although it seems to be another implementation of this more moko-like implementation: http://www.micropp.se/openmoko/splash.html ). If I remember correctly, all participants of the discussion came to the conclusion, that a regular qwerty keyboard is not sufficient no matter how clever you pimp it, due to restriction of precision of finger typing and lack of screen space. i disagree. reality of the qtopia predictive keyboard and actual use of it disagrees. talk and theory is fine - actual code that works is disagreeing. users of that code are disagreeing. I have to agree with Raster here. Trolltech did an amazing job on their QWERTY (onscreen) keypad. I highly recommend you trying it out on the Neo if you haven't already. Personally, I think it's the best touchpanel keyboard on the market now. Bar none. Sean Maybe it is. I still hate it and any other form of predictive text input I have used so far. That doesn't mean I want to prevent anyone else from having it. I can understand that some people are happy with it and it would probably be a good idea to use it as the default input method. What I want is an alternative I can very easily switch to. We don't want the perfect input method because it probably doesn't exist. Let's agree on disagreeing and try to figure out a base set of alternative input mechanisms that should be included in Openmoko as well as making it easy for the user to install more of them. Some options I can think of that would find an audience: -Predictive QWERTY, maybe with different prediction modes (dictionary, closeness, combination, none) -Multitap 3*4 standard phone layout (maybe with optional prediction if patent issues can be avoided) -Dasher -A sliding method. My favorite, even though I never used one and don't really know which of the ideas floating around will be the best one. The next thing to consider is size. There are basically two options: -Use about 1/3 of the screen so that the running program is still visible. The problem with this is that the space is very small and some of the methods above would not work at this size or only work with a stylus. -Use pretty much the whole screen while inputting something and close the input method afterwards. This worked very well on my Palm device for two thumb landscape QWERTY input but that screen was twice as big as the Neo's. It is my prefered way of doing input because I don't need to see the program while typing. I only need to see about two lines of the text I last typed. For all methods where this makes sense, both sizes should be available. Last, let me describe my imaginary perfect input method: The input area is divided in 3*3 squares. A letter is written by starting on a defined square and moving over one square to end in a 3rd square. So every letter is a combination of 3 adjacent squares drawn in the right direction. Now here is what makes this fast and thus great: If the next letter you want to draw starts on the square you just ended on, you simply continue your slide and add two squares. This way, many letter combinations and even whole words could be written in one continuos sliding motion. There are 44 possible combinations (if I counted right) which should be plenty if we plan for a shift-combination and a numbers/special characters-combination. The character layout shouldn't follow any alphabet or QWERTY logic but instead be entirely based on language. The reason is that it would require learning from the ground up anyway so it should be as fast as possible once you have learned it. The small version for only taking up 1/3 of the screen would be perfect in 2*5 which would also result in 44 combinations (again, if I counted them right...). Feedback and actual implementation of this would be very welcome! In fact, I offer 30 Paypal €uros to the first person to make this work on my Neo (meaning it has to come with simple installation instructions). Ortwin Well, so I can't count. If you consider that valid 3 square motions are also moving to another square and then moving back to the old one (which I didn't above) you end up with 68 for 3*3 and 70 for 2*5. However, it might make
Re: freedom
*About Peermeta* Peermeta is a pioneer in Web 2.0 enabled software platforms for intelligent end points utilizing mobile broadband infrastructure. The Peermeta solution enables mobile access to Any Content, on Any Device, on Any Network, at Any Time. Peermeta provides a method for tapping into the breadth of distributed heterogeneous content, extending control over consumable content to users for personalization and sharing among social networks and enhancing today's mobile network capabilities and end-user experiences to help drive mainstream adoption. The company was founded in January 2007 and is backed by venture capital firms Sigma Partners and Kepha Partners. For more information, please visit www.peermeta.com. Should OpenMoko be a better choice than PeerMeta ??? Can OpenMoko be the OS for WiMax CPEs ??? ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GTA02 Battery Capacity (Was: Re: More about the GTA02)
Andy I do hope you will put as much as you can back into GTA01, as I have real hopes now of using mine regularly. thanks clare On Sun, 2 Mar 2008, Andy Green wrote: I think we will improve this a small amount in kernel updates we already know we can do, but how much I don't know. We already know we waste current with bad GPIO levels in suspend and can fix them (I have a list here to do). Also I derated these estimates somewhat just in case since I did not verify them. So I expect we exceed this figure soon. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GTA02 Battery Capacity (Was: Re: More about the GTA02)
On Sun, 2008-03-02 at 13:21 +1100, clare wrote: Andy I do hope you will put as much as you can back into GTA01, as I have real hopes now of using mine regularly. +1 from me too :) -Tim thanks clare On Sun, 2 Mar 2008, Andy Green wrote: I think we will improve this a small amount in kernel updates we already know we can do, but how much I don't know. We already know we waste current with bad GPIO levels in suspend and can fix them (I have a list here to do). Also I derated these estimates somewhat just in case since I did not verify them. So I expect we exceed this figure soon. ___ 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
Re: Virtual QWERTY Keyboards to be used with Fingers...
On Sat, 01 Mar 2008 21:10:14 +0100 Marco Trevisan (Treviño) [EMAIL PROTECTED] babbled: Carsten Haitzler (The Rasterman) ha scritto: thats why dictionaries can be added to, imported, words learnt automatically and added, etc. etc. :) I had also an idea about this... What about a dictionary-sharing using internet? I mean a kind of repository of dictionaries that users could integrate using their personal dictionaries that they've generated using the phone itself. The process of submission could be also automatized but - of course - there are some privacy isses that should be considered! sure. i see no reason that over time such things could not be done. -- Carsten Haitzler (The Rasterman) [EMAIL PROTECTED] ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Idea of a voice mail application
On 29 Feb 2008, at 17:34, Marco Trevisan (Trevio) wrote: siaPeter Trapp ha scritto: Hi everybody, I thought about the possibility of a voice mail installed on the neo. The idea is to let the application decide if you are reachable for the caller or not. The decision will be done on profiles (time, who is calling, what to do (let it ring or answer directly) ). Eg: Saturday 10:00pm and your boss is calling (and you have a signal) Neo is aware that it is "weekend" and who is calling. It just turns on the voice mail... Dear Boss, actually it is weekend and I just don't want to get some work right now. Sorry, my neo will not even inform me that you've called. So don't try again later. It would not help until Monday 9am! Have a nice weekend --- without the possibility to leave a message ;) I would like this feature also, and really I assumed it would become a commonplace usage on OpenMoko. Cool, but your caller will pay for this.. So maybe it won't be so happy :P Stuff the caller. I carry a mobile phone so I can make outgoing calls when I'm away from home, not so I can be interrupted in the middle of a conversation. If someone is calling me they assume that they're going to incur the cost of a call, anyway, so I don't see that the cost of a call to voicemail is a large imposition (it is probably better than me answering my phone to say "stuff you", at least). Stroller. In the USA, the originator of the call is irrelevant. It charges against your plan minutes regardless of whether you are making or receiving a cellular call. So if software on your phone is picking up the line and your phone itself is acting as the answering machine, it will use up your minutes as well as costing the caller minutes. Actually, if they're using a landline and you are a local call for them, it won't cost the caller anything, while it uses your minutes regardless. The exception is that often if the caller and the recipient are both on the same network, neither is charged. I know that's true of T-Mobile. Another issue is that this function will only work if your phone is both turned on and in service. Of course, maybe this functionality is only needed in that situation anyway (e.g. you are in service and want to receive calls from certain people and not certain others.) That said, I still think it's an extremely useful function for the phone to have by virtue of its power and flexibility. If it could do things like give different outgoing messages based on who's calling, or forward the incoming message (maybe even send to email?), or automatically send a text message and that kind of thing, it would be really cool. The suggestions of real-time screening (like you can do with a home answering machine) and sending calls from specific numbers (or all but specific numbers) directly to the provider's system voicemail are great too. Mark ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Idea of a voice mail application
And people just accept paying for incoming connections?! I still can't get over how US phone contracts work... O.o On 3/2/08, Mark Haury [EMAIL PROTECTED] wrote: On 29 Feb 2008, at 17:34, Marco Trevisan (Treviño) wrote: siaPeter Trapp ha scritto: Hi everybody, I thought about the possibility of a voice mail installed on the neo. The idea is to let the application decide if you are reachable for the caller or not. The decision will be done on profiles (time, who is calling, what to do (let it ring or answer directly) ). Eg: Saturday 10:00pm and your boss is calling (and you have a signal) Neo is aware that it is weekend and who is calling. It just turns on the voice mail... Dear Boss, actually it is weekend and I just don't want to get some work right now. Sorry, my neo will not even inform me that you've called. So don't try again later. It would not help until Monday 9am! Have a nice weekend --- without the possibility to leave a message ;) I would like this feature also, and really I assumed it would become a commonplace usage on OpenMoko. Cool, but your caller will pay for this.. So maybe it won't be so happy :P Stuff the caller. I carry a mobile phone so I can make outgoing calls when I'm away from home, not so I can be interrupted in the middle of a conversation. If someone is calling me they assume that they're going to incur the cost of a call, anyway, so I don't see that the cost of a call to voicemail is a large imposition (it is probably better than me answering my phone to say stuff you, at least). Stroller. In the USA, the originator of the call is irrelevant. It charges against your plan minutes regardless of whether you are making or receiving a cellular call. So if software on your phone is picking up the line and your phone itself is acting as the answering machine, it will use up your minutes as well as costing the caller minutes. Actually, if they're using a landline and you are a local call for them, it won't cost the caller anything, while it uses your minutes regardless. The exception is that often if the caller and the recipient are both on the same network, neither is charged. I know that's true of T-Mobile. Another issue is that this function will only work if your phone is both turned on and in service. Of course, maybe this functionality is only needed in that situation anyway (e.g. you are in service and want to receive calls from certain people and not certain others.) That said, I still think it's an extremely useful function for the phone to have by virtue of its power and flexibility. If it could do things like give different outgoing messages based on who's calling, or forward the incoming message (maybe even send to email?), or automatically send a text message and that kind of thing, it would be really cool. The suggestions of real-time screening (like you can do with a home answering machine) and sending calls from specific numbers (or all but specific numbers) directly to the provider's system voicemail are great too. Mark ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: About ipkg on Openmoko
After I did these steps , I can ping outside IP successfully! But when $ ipkg update , it still failed like previous what should I do to make my Openmoko download ipkg update ? or I can only copy the file and update locally 2008/2/29, Marcin Juszkiewicz [EMAIL PROTECTED]: Dnia Friday 29 of February 2008, Xiangfu Liu napisał: #!/bin/sh echo ...ip address 192.168.0.200 ifconfig usb0 192.168.0.200 echo ...ip forward echo 1 /proc/sys/net/ipv4/ip_forward modprobe iptable_nat iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE maybe work http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ describe simple automation for it. -- JID: hrw-jabber.org OpenEmbedded developer/consultant I do not fear computers. I fear the lack of them. -- Isaac Asimov ___ 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
