Froyo Move to SD Card Reboots

[Guest slm020]

Does anyone else have the same problem as me?

Some of my apps have enabled the Move to SD Card button within the settings menu, however when I press it the phone does a quick reboot and the app is still located in internal memory. Do I need to partition the SD Card or create a directory?

Also, trying to trouble shoot, when I press Move to SD Card with no SD Card the phone comes back with an error saying not enough space and doesn't reboot the phone.

Thanks for any help!

[Guest ludo218]

I just tried with a game and it worked well. I haven't created any folder or partition on my card. I noticed that there is a folder ".android_secure" on SD, but it seems empty (according to ES File Expore... I haven't tried to read the card on my computer)

[Guest iserlohn]

Does anyone else have the same problem as me?

Some of my apps have enabled the Move to SD Card button within the settings menu, however when I press it the phone does a quick reboot and the app is still located in internal memory. Do I need to partition the SD Card or create a directory?

Also, trying to trouble shoot, when I press Move to SD Card with no SD Card the phone comes back with an error saying not enough space and doesn't reboot the phone.

Thanks for any help!

This happened to me as well. I ended up backing all my apps+appdata up with Titanium backup and then did a full wipe. I then restored all my apps and app data (but not system data). Now everything works fine.

[Guest j1mmy g88]

ive only been able to put one app onto sd card so far, nothing else seems to go over??? am i missing something

[Guest slm020]

Yep, a full wipe worked for me too.

Only apps that have been designed by the programmer to be installed on the SD will be able to be moved. Expect an influx of updates as this is incorporated into a lot of the apps in the market.

[Guest Karolis]

I think this might be related. Every time when I try to install Neocore, it restarts my phone.

[Guest innov8ion]

My Nexus One w/ Froyo reboots when I try to update SpeedX 3D 1.1.7 (Froyo Update). Methinks it could be the partitions I've set up per: http://androidandme.com/2009/08/news/how-t...ndroid-apps2sd/. Although I'm not sure because an earlier poster suggested it worked after he performed a "full wipe." Does a full wipe include the SD card? Does it reset the SD card partition?

In any case, SpeedX support advises me to take out the SD card and install. That is said to work...

Edited May 25, 2010 by innov8ion

[Guest Joemun2002]

Does anyone else have the same problem as me?

Some of my apps have enabled the Move to SD Card button within the settings menu, however when I press it the phone does a quick reboot and the app is still located in internal memory. Do I need to partition the SD Card or create a directory?

Also, trying to trouble shoot, when I press Move to SD Card with no SD Card the phone comes back with an error saying not enough space and doesn't reboot the phone.

Thanks for any help!

Actually I think is no need to partition your SD............As I search from the site, there has a method to enable your apps to SD card.

Please enter the following in the cmd.

adb shell

pm setInstallLocation 2

It's work perfectly on my Froyo..........

Hope it can help

[Guest Droid800]

I just tried with a game and it worked well. I haven't created any folder or partition on my card. I noticed that there is a folder ".android_secure" on SD, but it seems empty (according to ES File Expore... I haven't tried to read the card on my computer)

That's how Google has worked out the piracy issue with apps being on the SD card. I'm sure someone will figure out how to get them off, but average users will never be able to see them.

[Guest dmesg]

Does anyone else have the same problem as me?

I have exactly the same problem. My FRF50 installation was an upgrade from CM5.0.6 without a wipe. I guess some leftovers cause such behavior.

So far all my attempts to figure out what's wrong were useless.

And I don't want to do a full wipe (not before official 2.2 or Froyo-based CM is out).

Edited June 28, 2010 by dmesg

[Guest dmesg]

I'm still trying to find a solution that does not include wiping, so far to no avail.

The problem is related to ASEC_CREATE permission not granted to com.android.defcontainer. When trying to move/install anything to SD card, the following crash occurs:

I/ActivityManager( 83): Start proc com.android.defcontainer for service com.android.defcontainer/.DefaultContainerService: pid=1087 uid=10153 gids={1015, 2001}

I/PackageHelper( 1087): Size of container 2 MB 16015 bytes

W/dalvikvm( 83): threadid=11: thread exiting with uncaught exception (group=0x4001d7f0)

E/AndroidRuntime( 83): *** FATAL EXCEPTION IN SYSTEM PROCESS: PackageManager

E/AndroidRuntime( 83): java.lang.SecurityException: Requires android.permission.ASEC_CREATE permission

E/AndroidRuntime( 83): at android.os.Parcel.readException(Parcel.java:1247)

E/AndroidRuntime( 83): at android.os.Parcel.readException(Parcel.java:1235)

E/AndroidRuntime( 83): at com.android.internal.app.IMediaContainerService$Stub$Proxy.copyResourceToContainer(IMediaContainerService.java:164)

E/AndroidRuntime( 83): at com.android.server.PackageManagerService$SdInstallArgs.copyApk(PackageManagerService.java:5341)

E/AndroidRuntime( 83): at com.android.server.PackageManagerService$MoveParams.handleStartCopy(PackageManagerService.java:5010)

E/AndroidRuntime( 83): at com.android.server.PackageManagerService$HandlerParams.startCopy(PackageManagerService.java:4815)

...

At boot I see the following messages:

W/PackageManager( 84): Not granting permission android.permission.ASEC_ACCESS to package com.android.defcontainer (protectionLevel=2 flags=0xbe45)

W/PackageManager( 84): Not granting permission android.permission.ASEC_CREATE to package com.android.defcontainer (protectionLevel=2 flags=0xbe45)

W/PackageManager( 84): Not granting permission android.permission.ASEC_DESTROY to package com.android.defcontainer (protectionLevel=2 flags=0xbe45)

W/PackageManager( 84): Not granting permission android.permission.ASEC_MOUNT_UNMOUNT to package com.android.defcontainer (protectionLevel=2 flags=0xbe45)

Unfortunately I can't find any human-readable place where these permissions can be granted (platform.xml doesn't seem to help, but maybe I'm doing it wrong).

I would appreciate any clues how they can be granted to particular application or user/group (which in this case are app_153/1015, not some known user/group. Or alternatively how defcontainer can be assigned a different uid/gid.

Thanks.