Testing for HTC magic

by Mattaku Betsujin » Sat, 07 Mar 2009 02:19:05 GMT

Sponsored Links
 I am getting user feedback for my app "closes a lot on HTC magic, one star"

Are there any HTC magics out there? Will it be able to get an SDK/emulator
for it?



Testing for HTC magic

by Justin Allen Jaynes » Sat, 07 Mar 2009 09:13:03 GMT

 The emulator doesn't simulate any specific phone.  Just a generic one.  
Your application *should* run the same on an HTC magic as on a TMobile 
G1 because the hardware is very similar.  The whole intention of Android 
is to separate the application layer sufficiently from the hardware so 
that your app will run equally well on any android device.  So, although 
there are possible reasons it might not work well on a Magic, it's far 
more likely misbehaving because of either 1) the users particular phone 
setup (too many other running apps, etc), or 2) it's misbehaving on most 
actual physical phones.  If it's reason 1, you just got bad luck that 
they left a poor review.  If it's reason 2, you should investigate and 
fix it.

If at all possible, you should get an actual G1 (or Magic when it 
becomes publicly available in your area) and install and test the app.  
And although a DEV phone would be better than the emulator, the DEV 
phone ships with a different configuration than what end users have on 
their phones.  So an actual phone from a phone company would be the 
absolute best way to test.  The Android Platform which gets installed 
onto these phones by cellular phone companies is customized as they 
choose (which is one reason Android is open source).  For this reason, 
the emulator will never be exactly the same as the real world.



Sponsored Links

Testing for HTC magic

by Mariano Kamp » Sat, 07 Mar 2009 16:27:37 GMT

 And as it is not releases it might still be buggy.

I also got an error report regarding the Magic and he also mentioned
problems with Twitroid.

Both complaints are not about "Forced Close", but about GUI problems. Very


Testing for HTC magic

by Romain Guy » Sat, 07 Mar 2009 16:31:31 GMT

 However is using this device might simply be running Cupcake, which is
far from being complete and ready.

Note that apps that rely on private APIs/resources may/will run into
problems with Cupcake.

Romain Guy
Android framework engineer

Note: please don't send private questions to me, as I don't have time
to provide private support.  All such questions should be posted on
public forums, where I and others can see and answer them


Testing for HTC magic

by Mariano Kamp » Sat, 07 Mar 2009 16:43:49 GMT

 Sure, that's what I meant with "still buggy". In my case, NewsRob, I can say
though that I don't use any private API.

I have to add though that I never verified the bug myself, so it might be
totally unrelated to the Magic or not a bug at all.

But for the twidroid problem he also posted a screenshot though:

Anyway, I'd mark it up as suspicious behavior for the time being. The user
is willing to show the problem to me in person. As he lives 300 kms apart
from me I would need to have something else in the area to go there, but
when I do I'll take my logcat with me and feedback here then.


Testing for HTC magic

by Al Sutton » Sat, 07 Mar 2009 16:57:15 GMT

 ne of the problem is the HTC magic has been doing the rounds since 
early Feb when Cupcake was still way off being finished, so it's easily
possible that the device they're using is running flakey firmware.

The first hits AndAppStore saw from Magics' was on the 5th of Feb, and
since the 18th of feb there has been a steady stream hits from them, all
showing Cupcake as the firmware (1.5).

It might be worth putting up a note somewhere saying if you're using a
Magic it's a pre-release product so bugs may be with the firmware and
not necessarily with the app.


Mariano Kamp wrote:


* Written an Android App? - List it at http://andappstore.com/ *

Funky Android Limited is registered in England & Wales with the
company number 6741909. The registered head office is Kemp House,
152-160 City Road, London, EC1V 2NX, UK.

The views expressed in this email are those of the author and not
necessarily those of Funky Android Limited, it's associates, or it's


Other Threads

1. Local Storage for webview


First, sorry for my bad English level.

I have a problem with the local storage for a webview which may
display an HTML5 app, but the test.html file informs me that local
storage is'nt supported by my browser...

Please take a look at my code :

package com.test.HelloWebView;

import android.app.Activity;
import android.content.Context;
import android.os.Bundle;
import android.util.Log;
import android.view.KeyEvent;
import android.webkit.WebChromeClient;
import android.webkit.WebSettings;
import android.webkit.WebStorage;
import android.webkit.WebView;
import android.webkit.WebViewClient;

public class HelloWebView extends Activity {

        WebView webview;

    public void onCreate(Bundle savedInstanceState) {

        webview = (WebView) findViewById(R.id.webview);
        webview.setWebViewClient(new HelloWebViewClient());
        WebSettings settings = webview.getSettings();
        String databasePath =
        settings.setDatabasePath(databasePath); //"/data/data/
        webview.setWebChromeClient(new WebChromeClient() {
            public void onExceededDatabaseQuota(String url, String
databaseIdentifier, long currentQuota, long estimatedSize,
                        long totalUsedQuota, WebStorage.QuotaUpdater
quotaUpdater) {
                quotaUpdater.updateQuota(5 * 1024 * 1024);

    public boolean onKeyDown(int keyCode, KeyEvent event) {
        if ((keyCode == KeyEvent.KEYCODE_BACK) && webview.canGoBack())
            return true;
        return super.onKeyDown(keyCode, event);

    private class HelloWebViewClient extends WebViewClient {
        public boolean shouldOverrideUrlLoading(WebView view, String
url) {
            return true;




2. I keep on getting 401 when sending msg to C2DM server

1. Have you registered your sender email to send messages here?
2. And have you waited about 24 hours to be activated? There is a
latency to activate your account.
3. Is your sender email that you registered the device with the same
email you registered with in #1? It should be.


3. New to android

4. In-app billing and Google Checkout setup

5. web app-problems with buttons

6. Pointers to open source android apps developed as a web-service

7. EditText in Honeycomb