Thanks for the info! Do you know if there are any plans to support pulling the incoming number in the future?
On Apr 17, 11:57 am, "Megha Joshi" <[EMAIL PROTECTED]> wrote: > On Wed, Apr 16, 2008 at 3:54 PM, callingshotgun <[EMAIL PROTECTED]> > wrote: > > > > > > > Hey all- I've just now started ripping into building Android apps, > > and it's a lot of fun- But as extensive as the API documentation is, > > there are a couple things that I can't quite tell if they're possible > > or not, and I'd really like to utilize them for a some personal > > projects. > > > 1- Is there a way to programmatically retrieve the number of an > > incoming call? I saw information on how to react to the event, but > > there was nothing in there that gave the actual phone number. This > > may have been thought of before, but I was thinking about using the > > incoming phone number to cross-ref with an online db of telemarketer > > phone numbers, and maybe have the phone blink the background red or > > something as a way of warning. Really simple idea, could probably rig > > it up via jabber (to a bot on a webserver that could handle the more > > complex interactions with the database and just fire bac a result)- > > But I'm missing that one critical component- The actual phone number. > > You cannot retrieve the incoming call number. > > > > > 2- I've been fooling around with an alternate keyboard layout- Sort > > of a mobile DVORAK for traditional 12-key keypads. The idea on this > > one would be to do away with the "abc,def,ghi" system and come up with > > a mapping that minimizes the ungodly wait between letters when you > > have to type, for instance, "fed", and the cursor has to blink a > > couple times before moving to the next position. Android seems like > > an ideal match for this, if I could just somehow swap out the system > > keymapping with my own- But the documentation on keycharactermap > > doesn't really give any pointers on how to create my own. Is this > > possible/undocumented? Or is it something that Android hasn't/won't > > open up to developers via the SDK? > > You may want to use an input method. This is the thing that gets the '2' > keypress and tries to figure out if it's an A, B or C. The one for the > qwerty key is very simple -- it uses the key character map. We have basic > support for that now, via the InputMethod interface > <http://code.google.com/android/reference/android/text/method/InputMet...>, > but we don't have support -- yet -- for supplying them system wide. Right > now it has to be built into each app. > > > > > Much appreciated:) > > > -Alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
