HTC Magic, is PhoneNumberUtils.PAUSE different?

by Alejandro » Mon, 27 Apr 2009 12:37:42 GMT

Sponsored Links
 I am getting reports that the in the HTC Magic the character that
represents the pause in a dial string is different than in the Google
build of cupcake. In the SDK 1.5 pre-release, the pause is given by a
','. Apparently, in the HTC magic, the pause is given by a 'p'.
Unfortunately, I don't currently have the means to test this. Does
anyone know if the PhoneNumberUtils.PAUSE member in the HTC magic
build reflects this change? Have any other functions in
PhoneNumberUtils changed in order to support this?

Thank you,


HTC Magic, is PhoneNumberUtils.PAUSE different?

by Alejandro » Thu, 25 Jun 2009 14:05:38 GMT

 The Rogers HTC Magic phone is using the 'p' as a pause, but it seems
they haven't changed the PhoneNumberUtils.PAUSE to reflect this. This
is rather unfortunate, because it makes the Rogers build non-standard
and my app breaks. I would hope in the future there are no more
deviations of the standard SDK, otherwise, developing for the Android
platform will become harder.



Sponsored Links

Other Threads

1. Design

This is mainly a design question :

My app connects to a server from where data is retrieved and presented
in a listview. Depending on user-selection different data is retreived
and filled in the list. A typical list item consists of a text string
of up to some 50 or 60 characters depending what the server returns.
Additionally, a small image icon is shown next to each string. The
server may return any number of items from 0 up to many hundred or
even thousands. It is possble to ask the server to iteratively return
subsets of the content. The images are actually links to http-
addresses, but I guess this still requires/allocates memory for the
listview by Android.

How do I design for efficiency and responsiveness, considering memory
Are there any generic guide lines on how many list items, Strings or
Bytes to keep in memory?

On the one hand I would like to have as many items in the list as
possible - from a users perspective *all* items returned from the
server would be expected. On the other, sending many queries to the
server makes the app slower. I am not sure how to handle this
situation since I do not have a feel for what android can handle in
terms of memory.

Any ideas would be of help.


2. Sensor and Compass APIDemo failing on emulator 1.5

I have been trying to use the OS->sensor and graphics->compass in the
APIDEMO (through emulator 1.5) by directly browsing through the menu
or through instrumentation, I have observed that for ensor and
compasstest the output is blank screen, but on virtual box the
output is proper. Also note that proper output is seen in case of 1.1

Is this a bug in emulator 1.5 ?


3. Intent filters: how do I know which action to use?

4. Reusable Spans

5. Animated GIF

6. Persisting app data (not preferences)

7. Hi everybody....