App will not Install/Move to SD Card on HTC Desire HD

by lloyd1949 » Fri, 03 Dec 2010 00:53:10 GMT

Sponsored Links
 Hi Folks:

A user of my app has reported the following:

Phone: HTC Desire HD with Android 2.2 with lots of room on the card.
Android version 2.2
Baseband version: 12.28b.60.140eU_26.03.02.26_M
Kernal version
ht-ker...@and18-2 #1
Tue Oct 26 15:58:17 CST 2010
Build number: 1.35.762.2 CL277020 release-keys
Software number: 1.35.762.2
Browser version: WebKit 3.1

My App is set up to be installed to the SD Card if possible via my use
of the "preferExternal" setting in the manifest file and is installed
on the SD card for many of my users. However this is the second time
that someone with the HTC Desire has reported that they cannot get my
app to be installed or moved to the SD Card.

Can anyone shed some light on what might be happening here?



Re: App will not Install/Move to SD Card on HTC Desire HD

by Valery » Fri, 20 May 2011 09:30:35 GMT

 Our users reporting same problems, same devices: HTC Desire, HTC Legend
There can be some bug or restriction with HTC devices that blocks apps to 
moving to SD card.
Did your app use Google C2DM service, for example? 
Did your app contains some broadcast receivers or services?


Sponsored Links

Other Threads

1. dmtracedump doesn't work

I was searching for profiling Android application and found traceview
and dmtracedump on android website

I followed the instruction in webpage to create a trace file and
succeed open it using traceview.
But when I try the dmtracedump tool. I got stuck.

I already install graphviz on my computer and dot commond works fine.
Then every time I type in command
"dmtracedump -g test.png mytrace.trace" or
"dmtracedump mytrace.trace"
the program just got stuck and nothing got out.

Is there anything wrong ?

Can someone helps?

Thanks a lot


2. When the wakup lock is released in AlarmManager?

Hi all,
I am using AlarmManager to schedule a repeated action which starts a

PendingIntent mAlarmSender = PendingIntent.getService(context, 0, new
Intent(context, MyAndroidService.class), 0);
firstRunMills, interval, mAlarmSender);

I saw the following paragraph in AlarmManager's document:
The Alarm Manager holds a CPU wake lock as long as the alarm
receiver's onReceive() method is executing. This guarantees that the
phone will not sleep until you have finished handling the broadcast.
Once onReceive() returns, the Alarm Manager releases this wake lock.
This means that the phone will in some cases sleep as soon as your
onReceive() method completes. If your alarm receiver called
Context.startService(), it is possible that the phone will sleep
before the requested service is launched. To prevent this, your
BroadcastReceiver and Service will need to implement a separate wake
lock policy to ensure that the phone continues running until the
service becomes available.

But it looks that the CPU wake lock can only be applied to pending
intents created by PendingIntent.getBroadcast. I am wondering when the
wake up lock is be released if the PendingIntent is an service. Does
anyone has insight into this?

Thank you in advance!!


3. get link quality value of a bluetooth connection

4. Watch a particular folder

5. Is there a way to clear DNS Cache in Android

6. RealPlayer Final

7. audio record emulator : setAudioSource failed