1321559 - Can't move Nightly to internal storage on Android 7.1

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: General, defect)

Description

[Judah Richardson]

Attachment: logcat

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20161201030205

Steps to reproduce:

- Check to ensure sufficient internal storage by going to Settings -> Storage.
- Go to App Info for Nightly.
- Under Storage, tap Change to change storage used from external (adopted) SD card to shared internal storage.
- Tap Internal Shared Storage.
- Tap Move


Actual results:

"Not enough storage space" toast error message appears.

I've attached a logcat for the steps above.


Expected results:

The app should have been moved to internal storage. 

Uninstalling and reinstalling Nightly doesn't fix the problem either.

I know this isn't a problem with the OS for several reasons:
- I have at least 2GB of free internal space for apps (see attached screenshot Android Storage.png)
- Nightly consumes 2 orders of magnitude less space than the above (see attached screenshot Nightly Storage.png)
- I'm able to download and install other apps to internal storage and move them back and forth between the internal storage and the adopted SD card.

Comment 1

[Judah Richardson]

Attachment: Storage screenshot

Comment 2

[Judah Richardson]

Attachment: Nightly storage

Comment 3

[Richard Newman [:rnewman]]

2-01 08:55:26.521 I/cp      (  319): cp terminated by exit(1)
12-01 08:55:26.521 E/installd(  319): Failed copying /mnt/expand/a5c38f45-e0f3-44e8-bf1b-9f861988109a/user/0/org.mozilla.fennec to /data/data with status 1
12-01 08:55:26.598 D/KP2AAF  ( 3751): OnAccEvent
12-01 08:55:26.598 D/KP2AAF  ( 3751): event: 2048, package = com.android.settings
12-01 08:55:26.598 D/KP2AAF  ( 3751): no com.android.systemui
12-01 08:55:26.602 D/KP2AAF  ( 3751): Cancel notif
12-01 08:55:26.904 W/PackageManager(  782): Failed to move app
12-01 08:55:26.904 W/PackageManager(  782): com.android.internal.os.InstallerConnection$InstallerException: Failed to execute move_complete_app [a5c38f45-e0f3-44e8-bf1b-9f861988109a, null, org.mozilla.fennec, org.mozilla.fennec-1, 10231, default, 23]: -1
12-01 08:55:26.904 W/PackageManager(  782): 	at com.android.internal.os.InstallerConnection.execute(InstallerConnection.java:131)
12-01 08:55:26.904 W/PackageManager(  782): 	at com.android.server.pm.Installer.moveCompleteApp(Installer.java:115)
12-01 08:55:26.904 W/PackageManager(  782): 	at com.android.server.pm.PackageManagerService$MoveInstallArgs.copyApk(PackageManagerService.java:13970)
12-01 08:55:26.904 W/PackageManager(  782): 	at com.android.server.pm.PackageManagerService$InstallParams.handleStartCopy(PackageManagerService.java:13205)

possibly due to one of

12-01 08:55:24.543 I/cp      (  319): cp: chown '/mnt/expand/a5c38f45-e0f3-44e8-bf1b-9f861988109a/user/0/org.mozilla.fennec/lib': No such file or directory
12-01 08:55:24.715 I/cp      (  319): cp: chown '/mnt/expand/a5c38f45-e0f3-44e8-bf1b-9f861988109a/user/0/org.mozilla.fennec/files/mozilla/pkpky6bl.default/lock': No such file or directory


This does look like Android simply screwing up the copy, perhaps not expecting some of the stuff we store on disk.

Comment 4

[Richard Newman [:rnewman]]

tracking? just in case this is reproducible on other Android 7.1 devices with SD cards.

Comment 5

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Sorina,
Could you check if it happens on older android versions?

Comment 6

[Sorina Florean [:sflorean]]

Hello and sorry for delay here,

Tested with HTC Desire 820 (Android 6.0.1) and Huawei MediaPad M2 (Android 5.1.1) and wasn't able to reproduce this issue with latest Nightly (54.0a1 - 2017-02-05). I was able to change from external storage to internal, and from internal to external storage.

Comment 7

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

actually we need a test on android 7.1 running on devices other than Pixel. 
But seems it's not doable at this moment.

Comment 8

[James Willcox (:snorp) ([e-mail]) (he/him)]

Not sure there is anything we can do here, as this seems to be an Android bug.

Comment 9

[Judah Richardson]

Apparently fixed. Not sure if a new Nightly or Android build did the trick.