The FCC has ruled on Net Neutrality! That and much more news is covered by Jordan when he reviews all the important stories from this week. Included in this week's news is the announcement of the Pebble Time Kickstarter and be sure to stay tuned for even more mobile world congress announcements! That's not all that's covered in today's video! Jordan talks about the other videos released this week on XDA TV. XDA TV Producer TK released an Xposed Tuesday...
Use your Google Voice account with iDialer dialpad
First released back in September 2008 by XDA member supbro, iDialer v0.53 provides the functionality to call from your Google Voice account direct from the dialpad on your Windows Mobile device. The dialpad is a clone of the much loved iPhone dialer and is fully skinnable.
Compatible with QVGA, VGA, HVGA and WVGA (upscaled) on touchscreen and non touchscreen devices (pocketpc and smartphones), iDialer is compatible with WM6 ,6.1 and 6.5. At the time of writing, compatibility with WM6.5.3. is still to be confirmed.
When placing an outgoing call, iDialer will ask which service you wish to use – however I suspect that most would use their Google Voice account if they have one.
iDialer relies on the built-in default dialer or Google Voice to place the call using a callback method. Once the call is made, iDialer closes down and an incoming call is received from your Google Voice number, which when answered connects to the recipient. Your actual phone call occurs over your phone network and the data network (so not VoIP).
Other features include copy & paste, dialling ‘p’ and ‘w’ in phone numbers from iContact (supbro’s affiliated contact manager app), long press ‘1’ for voicemail, other speed-dials 2-9. 911 calls are always forced to use the built-in dialer.
iDialer is best used with iContact and GreenButton (both applications were developed by supbro and integrate superbly with iDialer). Without iContact, you will need to either remember the numbers that you wish to dial or copy and paste from the default contacts application. GreenButton maps your hardkey call button to call up iDialer, rather than the default dialpad. Unfortunately if you are a fan of Mobile Shell, then GreenButton will not work for you – in which case AEButton (Plus) is a good alternative to map the hardkey yourself. In order for iContact to communicate with iDialer, both applications must be installed to the same memory – either Storage Card or device memory.
Number format display can be updated via the registry or via supbro’s CabGen app which will update the registry for you. Dialpad tone volume too has it’s own registry key and can be modified to ‘0’ if you like a silent dialpad or you can install supbro’s mute keypad.cab.
For those of you looking for a fully integrated dialer, then iDialer unfortunately is not for you – ultimately it is a dialpad (it has no TAPI functionality built in) with no additional in-call features (the default dialer takes over), or built in SMS capability for Google Voice. Supbro has planned for in-call features to be developed in version 1.0 although the last update was way back in September 2009. In addition smartdialling is not supported, neither is video calling, nor USSD messages.
Check out the application thread for more info.
Want something on the XDA Portal? Send us a tip!
Google announced today that it will be bringing ads to the Play Store, and while that will surely annoy the majority of us, it isn't the only thing that sucks about the Play Store. From the lack of clear communication with developers to ridiculous restrictions, there are a handful of very annoying things about Google's approach. Let us know what bugs you the most about the Play Store.
Smartwatches still have a lot of growing up to do. Not too long ago the latest Canalys figures revealed a rather disappointing outcome for 2014, something we covered with the ultimate conclusion that, once again, smartwatches had no year. The direction of smartwatches is unclear to even the biggest OEMs, and with every new option there seems to be polarizing dissonances from what people and OEMs want and what they both think they want. We've documented many of the reasons as to...