Re: another GPS idea - speed-sensitive voicemail
This suggests that altitude might be something to check as well, though as someone else pointed out that's a little late to enable flight mode :) Why do you always think of planes when speaking of altitude? What about Mountain-climbing? Paragliding? Deltaplanes? Private Ultralight-Planes? Blimps? Altitude would also be cool for skiers: if it's increasing, leave phone calls in (i'm on the lift). If it's decreasing, block them (i'm skiing and don't want to be annyoed). All this features configurable on a per-contact-basis would be cool (don't let my wife call me when i'm skiing, ..) -- My corner of the web: http://ramsesoriginal.wordpress.com My dream, my world: http://abenu.wordpress.com ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: another GPS idea - speed-sensitive voicemail (Power usage)
While I do find most of the GPS based ideas intriguing I do have one comment. Power usage! I wonder if you have realised that the GPS consumes large quantities of current. (45 mW according to http://wiki.openmoko.org/wiki/Neo1973_Power_Management#Approximate_power_draw_of_various_subsystems) The 1200mAh battery will be drained in 1200mAh/(45mW/3.7V) = 98h ~= 4 days And this is for the GPS receiver alone and no power conversion losses, but GPS reception also requires CPU power.. If the CPU @ slow mode is 50mW and the GSM at idle is 30mW, then I would consider 45mW quite an addition power drain. It of course gets even worse if the GSM can wake the CPU from SYS_POWER_SLEEP http://wiki.openmoko.org/wiki/Neo1973_Power_Management#SYS_POWER_SLEEP Hence only the GSM has to be active? (plus some minor power drain for the CPU) That said I might actually still opt to have my standby time cut to 33-50% ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: another GPS idea - speed-sensitive voicemail (Power usage)
On 30 Jul 2007, at 16:45, Visti Andresen wrote: While I do find most of the GPS based ideas intriguing I do have one comment. Power usage! Then you simply have an update timer. Tell the phone to update it's position at a configurable time period, say every 5 minutes. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: another GPS idea - speed-sensitive voicemail (Power usage)
On Mon, 30 Jul 2007 16:59:51 +0100 Ian Stirling [EMAIL PROTECTED] wrote: Visti Andresen wrote: While I do find most of the GPS based ideas intriguing I do have one comment. Power usage! I wonder if you have realised that the GPS consumes large quantities of current. (45 mW according to http://wiki.openmoko.org/wiki/Neo1973_Power_Management#Approximate_power_draw_of_various_subsystems) The 1200mAh battery will be drained in 1200mAh/(45mW/3.7V) = 98h ~= 4 days And this is for the GPS receiver alone and no power conversion losses, but GPS reception also requires CPU power.. This is not quite correct. The GPS can be turned off and on. 45mW is for continuous positioning, 1s/45s will give completely fine positions, though not as accurate as if it was on for longer. If the 'Resume in under 1s' from sleep entry on the table at the front of the above page is done, then the numbers change again. If it takes 350mW for 1s to wake the device, and then 80mW for another second (CPU in slow mode and GPS on) that's 430mWs. One position per 45s, that's some 9mW average, or around 5% of the battery per day. It seems likely from the basic figures that this can be stretched to 1s wake every 3 minutes or so, for around 1.5%/day. After this, you need to wake up for more than a second to keep the position current, so after 3 minutes, the next halving in battery use might end up at 4 hours or so. This can also do bluetooth and WiFi polling of course (at a slight power cost) But does a GPS not require large amounts of time to get a new fix? Hot startup 12s, average Warm startup 38s, average Cold startup 60s, average (random data from http://www.alibaba.com/catalog/11694061/Bluetooth_GPS_Receiver.html) I must admit I don't know when one needs to reacquire the fix... Of course even a 38s/60s power consumption reduction would be quite noticeable, even if one has to switch to continues operation when moving (in order to notify me that I have to pickup groceries) ___ 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: another GPS idea - speed-sensitive voicemail (Power usage)
Visti Andresen wrote: On Mon, 30 Jul 2007 16:59:51 +0100 Ian Stirling [EMAIL PROTECTED] wrote: Visti Andresen wrote: While I do find most of the GPS based ideas intriguing I do have one comment. Power usage! I wonder if you have realised that the GPS consumes large quantities of current. (45 mW according to http://wiki.openmoko.org/wiki/Neo1973_Power_Management#Approximate_power_draw_of_various_subsystems) The 1200mAh battery will be drained in 1200mAh/(45mW/3.7V) = 98h ~= 4 days And this is for the GPS receiver alone and no power conversion losses, but GPS reception also requires CPU power.. This is not quite correct. The GPS can be turned off and on. 45mW is for continuous positioning, 1s/45s will give completely fine positions, though not as accurate as if it was on for longer. If the 'Resume in under 1s' from sleep entry on the table at the front of the above page is done, then the numbers change again. If it takes 350mW for 1s to wake the device, and then 80mW for another second (CPU in slow mode and GPS on) that's 430mWs. One position per 45s, that's some 9mW average, or around 5% of the battery per day. It seems likely from the basic figures that this can be stretched to 1s wake every 3 minutes or so, for around 1.5%/day. After this, you need to wake up for more than a second to keep the position current, so after 3 minutes, the next halving in battery use might end up at 4 hours or so. This can also do bluetooth and WiFi polling of course (at a slight power cost) But does a GPS not require large amounts of time to get a new fix? Look at the Hammerhead/Protocol page on the wiki. As a very brief recap, not if you have a sufficiently good knowledge of where the satellites are, and the local clock has not drifted by more than 1/3ms or so. (I'm involved in the reverse engineering of the GPS chip) ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: another GPS idea - speed-sensitive voicemail (Power usage)
On 30 Jul 2007, at 17:54, Visti Andresen wrote: But does a GPS not require large amounts of time to get a new fix? Hot startup 12s, average Warm startup 38s, average Cold startup 60s, average (random data from http://www.alibaba.com/catalog/11694061/ Bluetooth_GPS_Receiver.html) Depends if you have assistance from the cell network or not. It also depends on when you last obtained a fix. I don't see that 12 seconds would be too bad for location based services. 12 seconds after entering your workplace the phone mutes etc.. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: another GPS idea - speed-sensitive voicemail
You're confusing GSM (Global Systems Mobile) with the gsm codec in Asterisk. They have different meanings. The codecs used by your mobile phone are not the same as the gsm codec in Asterisk. Shachar Shemesh wrote: Ian Stirling wrote: There are 2 D/A, 2 A/D flexibly routed, and one D/A that is dedicated to the earpiece. About the only limitation is that you can't do things that would require more IO sources than are available. For example, playing stereo MP3, and acting as voicemail/answerphone may not be possible. (It'd have to drop to mono). Lost you there. You seem to suggest the following route for recording voice calls: 1. Call arrives compressed with a GSM codec 2. Phone decompresses codec 3. Phone moves uncompressed stream through D2A 4. Phone further moves stream through A2D 5. Phone compresses the resulting stream 6. Phone saves compressed stream, presumably to the flash Why not just do: 1. Call arrives compressed with a GSM codec 2. Phone saves compressed stream to flash I really don't see why the A/D infrastructure needs to be involved in voice recording at all. In fact, it seems that it should be easier for the phone to save the call than to play it to the speaker. Shachar P.S. Asterisk, for example, saves most of its recordings (pick up greeting, extension selection, voice mail greeting etc.) saved while compressed with GSM codec. As far as I understand things, if OpenMoko did that, playing a recording would involve getting it off the flash and dump it into the GSM line. Extremely light on CPU, and thus unintrusive. Sh. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Michael Welter Telecom Matters Corp. Denver, Colorado US +1.303.414.4980 [EMAIL PROTECTED] www.TelecomMatters.net ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: another GPS idea - speed-sensitive voicemail
Michael Welter wrote: You're confusing GSM (Global Systems Mobile) with the gsm codec in Asterisk. I find that highly likely. I'm pretty new to Asterisk. They have different meanings. The codecs used by your mobile phone are not the same as the gsm codec in Asterisk. But it does use some codec. Even if it's not the same one, there is a piece of software that can decompress it, and you can (probably) store pre-compressed message you just want to dump on the line. I realize this cannot be done due to licensing and other considerations. I'm just saying that the details may be wrong, but the principle stands. Shachar ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: another GPS idea - speed-sensitive voicemail
Shachar Shemesh wrote: Michael Welter wrote: You're confusing GSM (Global Systems Mobile) with the gsm codec in Asterisk. I find that highly likely. I'm pretty new to Asterisk. They have different meanings. The codecs used by your mobile phone are not the same as the gsm codec in Asterisk. But it does use some codec. Even if it's not the same one, there is a piece of software that can decompress it, and you can (probably) store pre-compressed message you just want to dump on the line. I realize this cannot be done due to licensing and other considerations. I'm just saying that the details may be wrong, but the principle stands. No, you can't. Because the modem does not give you the compressed data. It gives you an analog output. There is no way (published) to make it send out compressed data. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: another GPS idea - speed-sensitive voicemail
Mark, I love the idea! And maybe a feature like dumping the call to a BT headset device if present. I am curious, I assume there would be a config option or something, because how would it tell if you are the driver? A preference per contact could be used as well. ie. I don't mind if my family calls me while driving, but not Joe, Bob, or Steve. *I hate the fact that I cannot download or save my voicemail messages... I cannot with Verizon anyways. Developing a voicemail utility to save a voicemail locally when service is available but you are just ignoring calls would be quite nice.The ability to start recording at any time during a conversation could be useful as well. -Kyle On 7/28/07, Mark Eichin [EMAIL PROTECTED] wrote: Use case: When I'm walking around, I'll answer the phone. When I'm driving, I won't (one phonecall == two beers worth of distraction)... but am willing to pull over if the caller thinks it's important enough. I shouldn't have to *tell* the phone what mode I'm in: GPS can provide velocity information. If my speed is over 10mph, the phone should pick up, dump a pre-recorded explanation to the caller, and let them press 1 to interrupt the driver, or just wait a few seconds and leave voicemail. http://wiki.openmoko.org/wiki/Neo1973_Audio_Subsystem implies that call recording is possible, so the audio paths are there, right? If so, a lot of local voice-robot stuff is possible... (And if your thought is what if I'm a passenger - the answer is this feature is not for you, it's for me :-) (Also, if you're not an American, this feature probably isn't for you either :-) :-) ___ 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: another GPS idea - speed-sensitive voicemail
Mark Eichin wrote: Use case: When I'm walking around, I'll answer the phone. When I'm driving, I won't (one phonecall == two beers worth of distraction)... but am willing to pull over if the caller thinks it's important enough. I shouldn't have to *tell* the phone what mode I'm in: GPS can provide velocity information. If my speed is over 10mph, the phone should pick up, dump a pre-recorded explanation to the caller, and let them press 1 to interrupt the driver, or just wait a few seconds and leave voicemail. http://wiki.openmoko.org/wiki/Neo1973_Audio_Subsystem implies that call recording is possible, so the audio paths are there, right? If so, a lot of local voice-robot stuff is possible... Yes. See [[Category:Calling Features]] on the wiki. There are 2 D/A, 2 A/D flexibly routed, and one D/A that is dedicated to the earpiece. About the only limitation is that you can't do things that would require more IO sources than are available. For example, playing stereo MP3, and acting as voicemail/answerphone may not be possible. (It'd have to drop to mono). ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: another GPS idea - speed-sensitive voicemail
Mark Eichin wrote: Use case: When I'm walking around, I'll answer the phone. When I'm driving, I won't (one phonecall == two beers worth of distraction)... but am willing to pull over if the caller thinks it's important enough. I shouldn't have to *tell* the phone what mode I'm in: GPS can provide velocity information. If my speed is over 10mph, the phone should pick up, dump a pre-recorded explanation to the caller, and let them press 1 to interrupt the driver, or just wait a few seconds and leave voicemail. http://wiki.openmoko.org/wiki/Neo1973_Audio_Subsystem implies that call recording is possible, so the audio paths are there, right? If so, a lot of local voice-robot stuff is possible... Something like Asterix (don't know the full possibilities of Asterix though) (And if your thought is what if I'm a passenger - the answer is this feature is not for you, it's for me :-) (Also, if you're not an American, this feature probably isn't for you either :-) :-) In the Netherlands (and probably most of Europe) only handsfree calling is allowed while driving. (but if handsfree calling means driving dangerous, you can still be fined) ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: another GPS idea - speed-sensitive voicemail
On Saturday 28 July 2007 21:17, Eric van Horssen wrote: Something like Asterix (don't know the full possibilities of Asterix though) He was a character in popular French cartoon by Goscinny and Uderzo, he could do lots and lots of things... He probably would have used Asterisk if it had been around at the time. Andy ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: another GPS idea - speed-sensitive voicemail
Some friends at work and I were talking about a speed-sensitive configuration option, too--one that selects ringing profiles. For example, when you're at a speed greater than, say, 20 mph, more than likely you're in a noisy environment and you'd want your phone to ring slightly louder. When speeds reach 150 mph, it's a good bet you're in a plane (or Mario Andretti) and it's time to go to Flight mode (of course, this is quite a bit later than when they ask for phones to be turned off). Anyway, I am thinking there might be many uses for speed-based settings--enough to justify a speed-based 'cron' like utility? Perhaps... (my apologies to our non-American colleagues for being mired in english units) DSG -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Eichin Sent: Saturday, July 28, 2007 1:04 PM To: community@lists.openmoko.org Subject: another GPS idea - speed-sensitive voicemail Use case: When I'm walking around, I'll answer the phone. When I'm driving, I won't (one phonecall == two beers worth of distraction)... but am willing to pull over if the caller thinks it's important enough. I shouldn't have to *tell* the phone what mode I'm in: GPS can provide velocity information. If my speed is over 10mph, the phone should pick up, dump a pre-recorded explanation to the caller, and let them press 1 to interrupt the driver, or just wait a few seconds and leave voicemail. http://wiki.openmoko.org/wiki/Neo1973_Audio_Subsystem implies that call recording is possible, so the audio paths are there, right? If so, a lot of local voice-robot stuff is possible... (And if your thought is what if I'm a passenger - the answer is this feature is not for you, it's for me :-) (Also, if you're not an American, this feature probably isn't for you either :-) :-) ___ 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
