Cannot mount Obb on Android KitKat 4.4 [36982898]

Fixed

Bug

[AOSP] assigned

[AOSP] Released

Status Update

No update yet.

Description

gh...@gmail.com

created issue #1

Nov 6, 2013 09:29PM

I am trying to mount my OBB as a filesystem on my Nexus 5 running Android KitKat . I use the following code

StorageManager.mountObb(XAPKS.filefullpath(context), null, new OnObbStateChangeListener(){
@Override
public void onObbStateChange(String path, int state){
switch (state){
case MOUNTED:
Log.e(LOG_TAG, "Obb mounted " + XAPKS.filefullpath(context));
break;
default:
Log.e(LOG_TAG, "Obb mounting errors " + XAPKS.filefullpath(context) + " | " + XAPKS.storageManagerErrorsHelper(state));
break;
}
}
});

XAPKS.filefullpath(context) returns "/storage/emulated/0/Android/obb/mypackage/main.version.mypackage.obb"

But Vold fails to mount my OBB with : "Unable to open /mnt/shell/emulated/obb/mypackage/main.version.mypackage.obb (Permission denied)"

Same code was working with Android 2.3 up to 4.3 .

My application uses android.permission.READ_EXTERNAL_STORAGE and android.permission.WRITE_EXTERNAL_STORAGE if it can be of any interest.

Comments

pi...@gmail.com <pi...@gmail.com> #2Nov 13, 2013 08:17PM

Can you provide the below requested information to better understand the issue:

Can you please test with latest library and update result here.

https://developer.android.com/topic/libraries/support-library/revisions.html

If possible please provide a complete sample application.

Expected output
What do you expect to occur?

Current output
What do you see instead?

ol...@gmail.com <ol...@gmail.com> #3Nov 14, 2013 02:47PM

This seems to be intended according to

https://issuetracker.google.com/74278849, the suggestion is to remove the extra logic to deliverResult() in onStartLoading().

js...@android.com <js...@android.com> #4Nov 15, 2013 09:19PM

Assigned to js...@android.com.

@gg..@google.com
Sample project is attached.

Steps to test:
1. Import, build and install apk
2. Notice "Number of 'onLoadFinished' calls: 1"
3. Click "Click me!" button to start Second Activity
4. Notice "Number of 'onLoadFinished' calls: 2"

EXPECTED: At stap 4 "Number of 'onLoadFinished' calls" should be 1.
ACTUAL: It's 2.

@ha...@gmail.com
That's not the solution because developers are not in control of all Loaders. For example CursorLoader from support libaray should be then fixed by google, not by developers.
And this is behavior change which is not documented, so suggestion on issuetracker is not good enough.

da...@gmail.com <da...@gmail.com> #5Nov 18, 2013 01:09PM

We have shared this with our engineering team and will update this issue with more information as it becomes available.

je...@gmail.com <je...@gmail.com> #6Nov 18, 2013 06:57PM

Do you have any news ?

da...@gmail.com <da...@gmail.com> #7Nov 19, 2013 09:38AM

@6 I think they changed the way it works, without much information about the change.
Try this solution I've written about (read the last part of the text too, as it talks about the changes) :

https://stackoverflow.com/a/22675607/878126

da...@gmail.com <da...@gmail.com> #8Nov 19, 2013 09:44AM

@7 Thank you for your information. I still get the error when orientation change

gi...@gmail.com <gi...@gmail.com> #9Nov 25, 2013 02:11PM

@8 I can't confirm. It works fine without any error .
Attached sample project, that "loads" content, and after 5 seconds returns a result, that will be returned on the current Activity.

da...@gmail.com <da...@gmail.com> #10Nov 25, 2013 02:21PM

OK I'll check it again. Thx a lot!

mi...@gmail.com <mi...@gmail.com> #11Dec 1, 2013 06:38PM

@9 Hello man, when orientation change the "onLoaderFinished" method, called again. Do you know how to stop calling this method?

ro...@gmail.com <ro...@gmail.com> #12Dec 4, 2013 01:25PM

@11 It is called only once after onCreate is called, just as intended.
The reason is that after you load something, you wish to use it. After orientation change, all is destroyed, but the result is still available, so you can use it.

If you don't want to use the result, either ignore it, or check whether the loader (if existing) has a result or not.
But this loses the whole point of using a loader. By using a loader, you are supposed to use its result, even after an orientation change.

da...@gmail.com <da...@gmail.com> #13Dec 4, 2013 03:00PM

Yep. I have two test Nexus 4's on which my app fails to work because of this problem.

ro...@gmail.com <ro...@gmail.com> #14Dec 4, 2013 06:05PM

Just a by-pass (though does not work for me as I require encryption) - Use a zip file instead of obb (renamed to obb) - this does not require mounting but can be read directly using ZipResourceFile. Zip file renamed as obb works well in KitKat.

Just a thought: We might as well use an encrtypted zip file - till this thing works (Perhaps zip4j library comes in handy?)

al...@gmail.com <al...@gmail.com> #15Dec 4, 2013 07:03PM

In my case, this functionality is needed to open html content which is stored in obb. Content is larger than 50Mb and I can't store it in Assets. I can't use zip format for obb file because WebView can't load resources from zip.
Now I shall rewrite my application because I shall choose entirely another way to deliver my application content for customers.
Any workarounds or suggestions will be very appreciated.

ol...@gmail.com <ol...@gmail.com> #16Dec 5, 2013 04:20PM

Same problem with Nexus 7 and Nexus 7 HD with 4.4.

ro...@gmail.com <ro...@gmail.com> #17Dec 5, 2013 11:59PM

Will this be solved in Kitkat 4.4.1 update?

te...@gmail.com <te...@gmail.com> #18Dec 6, 2013 09:35AM

I tried on Nexus 5 with kitkat 4.4.1 and this is fixed. Thank you Google!

da...@gmail.com <da...@gmail.com> #19Dec 6, 2013 09:37AM

Thanks for this information. I will see if the update is available for my Nexus 5.

js...@android.com <js...@android.com> #20Dec 6, 2013 07:02PM

Marked as fixed.

Yep, this is fixed with 4.4.1 :)

aj...@gmail.com <aj...@gmail.com> #21Dec 10, 2013 07:10AM

Hi Jeffrey,

Could you please point to the patch which solves this issue?

Thanks in advance

da...@gmail.com <da...@gmail.com> #22Dec 10, 2013 10:19AM

It's not a patch. It's a new release of the Android OS (4.4.1). To update, I followed the guide provided here:

http://betanews.com/2013/12/06/android-4-4-1-kitkat-now-available-heres-how-to-install-it/. I didn't want to wait for OTA update.

js...@android.com <js...@android.com> #23Dec 13, 2013 12:30AM

It was fixed by this change in platform/external/sepolicy:

Change-Id: I45d30ecabdf0bc8871f3dd67b5695ac909109d9a

ia...@gmail.com <ia...@gmail.com> #24Jan 6, 2014 07:17PM

Thanks for the fix! It would be great to get some love for this related bug too:

https://code.google.com/p/android/issues/detail?id=53878 (flakiness in the JOBB tool)

po...@gmail.com <po...@gmail.com> #25Mar 11, 2014 02:59AM

I am trying to mount an encrypted OBB on my Nexus 5 running Android 4.4.2
and return ERROR_COULD_NOT_MOUNT

Are there any workarounds of now ?

ma...@gmail.com <ma...@gmail.com> #26Aug 8, 2014 10:50AM

I still get COULD_NOT_MOUNT errors when trying to mount an encrypted obb. Same as described here:

http://stackoverflow.com/questions/14342068/how-to-mount-encrypted-apk-expansion-files

And I am on Android 4.4.4 with Nexus 4.

ma...@gmail.com <ma...@gmail.com> #27Aug 8, 2014 07:22PM

The issue might be fixed for unencrypted OBB, but it still does not work with encrypted OBB on Android 4.4.4.

jj...@gmail.com <jj...@gmail.com> #28Aug 14, 2014 07:24AM

I am from Holland and I also have the same problem, after reporting it I got the answer that it is also due to the fact that I am from abroad, so all I can do is wait.
I have a Samsung Tab S with 4.4 KitKat

sz...@gmail.com <sz...@gmail.com> #29Aug 15, 2015 03:08PM

[Comment deleted]

ci...@gmail.com <ci...@gmail.com> #30Oct 15, 2015 07:48PM

Up to Android SDK 21 it works, but I had again the same issue on ANDROID SDK 22!!!!

da...@gmail.com <da...@gmail.com> #31May 20, 2016 07:32AM

I find the reason for some obb file could not be mounted. There a random solt when make obb file, an hashkey generated by PBKDF2WithHmacSHA1. the hashkey from bytes convert to hex string has a bug. I submit a patch to project : platform/framwork/base.

https://android-review.googlesource.com/#/c/230280/