Hi guys,
I'm having a bit of an issue with my Nexus 4.
I'm on AOKP + Franco-kernel and everything was working great.
Today I've tried to install a game (Jetpack joyride) from the Play Store but the install failed, "not enough free space" error.
I've cleared the cache,dalvik cache and fixed permissions in TWRP but it didn't help.
Here's the output of the df command.
Code:
Filesystem Size Used Free Blksize
/dev 936.2M 32K 936.2M 4096
/mnt/secure 936.2M 0K 936.2M 4096
/mnt/asec 936.2M 0K 936.2M 4096
/mnt/obb 936.2M 0K 936.2M 4096
/system 827.8M 374.4M 453.4M 4096
/cache 551.7M 10.2M 541.6M 4096
/data 12.9G 2.2G 10.8G 4096
/persist 15.8M 4.2M 11.6M 4096
/firmware 64M 53.3M 10.7M 16384
/mnt/shell/emulated 12.9G 2.2G 10.8G 4096
/storage/emulated 936.2M 0K 936.2M 4096
/storage/emulated/0 12.9G 2.2G 10.8G 4096
/storage/emulated/0/Android/obb 12.9G 2.2G 10.8G 4096
/storage/emulated/legacy 12.9G 2.2G 10.8G 4096
/storage/emulated/legacy/Android/obb 12.9G 2.2G 10.8G 4096
I don't really see anything wrong so now I'm asking the experts.
Any ideas?
Thank you very much in advance.
Regards
I had this issue too on my old phone but with another app, poweramp.
The fix for me was:
Navigate to /Data/App folder
Search the app's .odex file and delete it
Try to install the app again
Dont know if this applies for this app too, but it helped me fix that same error.
Hope it helps you!
Worked like a charm!
Thank you!
Can you please explain why this works?
I more or less know what odex-files are but fail to see the relation between the odex file and the error I was getting.
Regards
Pihkal said:
Worked like a charm!
Thank you!
Can you please explain why this works?
I more or less know what odex-files are but fail to see the relation between the odex file and the error I was getting.
Regards
Click to expand...
Click to collapse
I had the same problem and im still not sure why an odex file prevent the app from installing...maybe it sees the odex file like folder like something...who knows...the problem is what you can do when this happents and you dont root your phone!!
pikachukaki said:
I had the same problem and im still not sure why an odex file prevent the app from installing...maybe it sees the odex file like folder like something...who knows...the problem is what you can do when this happents and you dont root your phone!!
Click to expand...
Click to collapse
I'm no expert but I think it's possible to gain root access with adb shell in an unrooted phone or you can try to temp-root your phone with some app, remove the odex file, reboot and continue unrooted.
But I can be wrong, I'm no expert.
Regards
Glad its working again! And i have no idea why those two things produce the error, sorry ^^.
It doesn't really matter, I'm just curious.
You've solved my issue so I'm happy. :good:
Thanks again.
Regards
I'm no expert, but i'd like to say YOU ARE AWESOME. Giving needed information and asking what you actually did and asking for explanation. We need more people like you. KUDOS.
:laugh:
Thank you!
I know how it feels when people expect you to solve their issues without them giving you any useful information, I work as a End User Computing and Infrastructure Support guy in large multinational, sometimes it's very frustrating.
And some of the posts you guys get here on XDA (please help me, it doesn't work!!!!! PLEASE!) annoy the sh*t out of me.
Can you by any chance explain way the above mentioned fix works?
Because I still don't get it and Google isn't really helping...
Regards
The most logical assumption I could come up with is that because the odex file is still there it doesn't know what to do.
Here is an example
You already have testapp.apk installed
You update test app
It knows testapp.apk is already there so The new version is created as testapp-1.apk
Odexed system creates testapp-1.odex
Example 2 - your issue
You are fresh installing testapp
It checks for testapp.apk
Its not there
App is installed as testapp.apk
Odexed system creates testapp.odex
Installer fails as testapp.odex already exists
System reports as out of space because it couldn't create testapp.odex
This is the way I would see it happening.
The installer won't be able to handle an already existing file because the file shouldn't exist. So it will report it as the only thing it knows how.
If it can't create the file then the memory must be full
Sent from my Nexus 4 using xda app-developers app
Thank you for explaining it in a way that even an idiot (me) can understand.
That actually makes sense to me.
But why doesn't it delete the odex file when you uninstall the apk?
I've also noticed that only a few of my installed apps have an odex file, generally speaking only the larger apps (games) have them.
If I understand correctly odex files allow apps to launch faster and consume less space, so what decides when an odex file should be created?
Sorry for going offtopic,
The odex file should be deleted when the app was uninstalled. I have had this issue a few times on 2 different devices so I can only assume it's an android bug.
About the odex files. usually you will only get them on an odexed ROM. Like stock
I only use deodexed so I'm not sure if you can run a deodexed file on an odexed ROM.
But here is the theory anyway.
Having odex is apparently slightly faster than not.
But having deodex is much better for modifications.
Odex = .odex files with apps
Deodex = recompiled into classes.dex which is then merged into the apk itself.
The most likely thing that I can think of that would cause this behavior is if when you had the app installed previously.
You used an app like luckypatcher to make modifications to the app.
So say the app was deodexed (there was originally no .odex file)
You make a change with lucky patcher.
The changes are stored in a .odex file
You then decide you don't want the app and uninstall it.
As that odex file was not created by the app it will not be removed. And such when you try to reinstall it it fails.
Sent from my Nexus 4 using xda app-developers app
It all makes sense to me now.
I probably shouldn't say this but I actually did mess around with lucky patcher on 2 FREE games just to see what would happen.
Nothing really happened so I uninstalled it, I didn't know it created the odex files.
So now everythings falls in to place and I've learned my issue was caused by my own stupidity.
Thank you very much for solving my issue,answering my questions and making me a little less dumb.
Regards
PS: I don't condone piracy.
Pihkal said:
It all makes sense to me now.
I probably shouldn't say this but I actually did mess around with lucky patcher on 2 FREE games just to see what would happen.
Nothing really happened so I uninstalled it, I didn't know it created the odex files.
So now everythings falls in to place and I've learned my issue was caused by my own stupidity.
Thank you very much for solving my issue,answering my questions and making me a little less dumb.
Regards
PS: I don't condone piracy.
Click to expand...
Click to collapse
I flashed the stock deodexed 4.3 yesterday and power amp started behaving weird as it didn't allow me to view my library - all songs etc but only showed the folder view. So I uninstalled power amp and tried to reinstall but I am getting the same error as OP although I have around 7 GB memory free. I tried the above solutions too but nothing seems to work.
Any thoughts? Should I post this issue on power amp on play store?
siddroid said:
I flashed the stock deodexed 4.3 yesterday and power amp started behaving weird as it didn't allow me to view my library - all songs etc but only showed the folder view. So I uninstalled power amp and tried to reinstall but I am getting the same error as OP although I have around 7 GB memory free. I tried the above solutions too but nothing seems to work.
Any thoughts? Should I post this issue on power amp on play store?
Click to expand...
Click to collapse
Poweramp is still not stable on 4.3
Sent from my Nexus 4 using xda premium
Related
Or visa-versa.
I can never seem to get this to work. I back up angry birds with TB, but if I make the backup while running a AOSP rom and then try to restore it after switching to a sense rom, then angry birds FC's or refuses to run or other such nonsense. The reverse is also true, backups from sense rom's don't work on AOSP rom's.
Anyone else experience this? Is there a work around?
Never had that problem. Always works fine for me. Perhaps go into the preferences for TB and verify that the setting for migrating apps across different roms is checked.
Will check that out. Didn't gnow that setting existed.
Sent from my ADR6300 using Tapatalk
Ok, where is this setting? I can't find it!
Sent from my ADR6300 using Tapatalk
It's under Privacy in the Settings menu.
Sent from my ADR6300 using XDA App
Ok this is embarrassing. I still can't find it. Went through every setting I could find in TB and I don't see it. Can someone give me specific instructions please? Thanks.
Sent from my ADR6300 using Tapatalk
teookie said:
Or visa-versa.
I can never seem to get this to work. I back up angry birds with TB, but if I make the backup while running a AOSP rom and then try to restore it after switching to a sense rom, then angry birds FC's or refuses to run or other such nonsense. The reverse is also true, backups from sense rom's don't work on AOSP rom's.
Anyone else experience this? Is there a work around?
Click to expand...
Click to collapse
Yeah that happened to me trying to go from CM7 to SkyRaider 4.0. I haven't looked for a solution yet...
Preferences>Migrate System Data
DINC|CM7|INCREDIKERNEL
I went from Virtuous to CM6 before and used TB to restore and had no problems.
wildstang83 said:
Preferences>Migrate System Data
DINC|CM7|INCREDIKERNEL
Click to expand...
Click to collapse
Ok, that check box is greyed out for me. Is that because I have the free version?
Sent from my ADR6300 using Tapatalk
I found making a backup myself was best. If you copy and paste to your SD Card the following directories...
/data/data/com.rovio.angrybirds/
/data/data/com.rovio.angrybirdsrio/
/data/data/com.rovio.angrybirdsseasons/
You can paste them back later and get all your scores back.
NOTE: I strongly suggest making a new backup of these directories AFTER doing any upgrades to Angry Birds versions because I am sure the data has changed after the upgrade.
You must be rooted to make changes to those directories so if your not, I think there just might be some instructions here somewhere on how to root your device..
Last note: After pasting the directories back (Performing a RESTORE), you must modify the file permissions so Angry Birds can write do that DB file. Otherwise, as I learned the hard way, none of your new scores will get saved..
I am running Virtuous 3.2.0 but I do not think this effects where these folders are being stored.. (I think....)
Grrr. I'm having trouble with this too. I tried to do an adb pull on the data/data/com.rovio.angrybirds directory but it only pulled two files, and didn't preserve the folder structure.
I tried adb shell, and then
copy -r /data/data/com.rovio.angrybirds/* /sdcard/
but it says "can't create symlink..." ??? I don't know what this means
Any help copying these files/folders to my HDD or to the SD would be appreciated.
Yeah I'm rooted, and I did adb remount before trying the stuff above....
I used Root Explorer to copy the folders from /data/data to my SDCard/Angry Birds Backup. (I manually created that folder on my SDCard)
Beware that for some reason, Root Explorer kept building an extra sub folder when copying the files back (overwrite) to data/data/com.rovio.angrybirds... I ended up just copying the single file data/data/com.rovio.angrybirds/files/highscores.lua (for instance) over and that worked for me...
As to the symlink issue, I believe that is a permissions issue. Possibly that you do not either have permission to copy FROM the com.rovio.angrybirds directory or to your SDCard... (make sure you mounted your SDCard correctly) Not intended as a flame or derogatory remark about your skills..
(from searching xda-developers.com)
I KNOW you stated you did the adb remount but was it similar to this:??
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /data
when done, do
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /data
I am close to the limit of my "experstease" here so I dont want to send you down the wrong path or make something worse happen.
I hope this helps.
THANK YOU!
Finally got it working. Ended up buying root explorer and copying over just the highscores file and it works! This has removed my one major frustration with rooting and flashing rom's.
Thanks again for the help!
Sent from my ADR6300 using Tapatalk
False alarm, didn't work. I have all my previouse scores and can play the game, but completing a level with a new high score causes it to crash. :-( almost like it can't write to the highscores file properly or something.
-sigh- back to square one.
Sent from my ADR6300 using Tapatalk
teookie said:
False alarm, didn't work. I have all my previouse scores and can play the game, but completing a level with a new high score causes it to crash. :-( almost like it can't write to the highscores file properly or something.
-sigh- back to square one.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
When you did the copy did you check permissions... sounds like you may not be allowed to write to file.
Just a suggestion.
SoBBie
FAO stratosk and others.
I was not permitted to reply in the main dev thread, but I thought I'd share what I found that works for my Galaxy S.
Your original script worked perfectly apart from the changing ownership / group. For some reason on my rom, system.cache does not resolve into the correct UID / GID - which makes /cache eventually have a 'root' ownership and thus the market cannot access it.
The solution is to use
chown 1000:2001 /cache
chown -h 1000:2001 /cache
The second one changes the symlink as well as the target.
This has already been pointed out in a reply but it may have got lost amongst the others!
Will.
original thread - http://forum.xda-developers.com/showthread.php?t=1188972
torrentship said:
FAO stratosk and others.
I was not permitted to reply in the main dev thread, but I thought I'd share what I found that works for my Galaxy S.
Your original script worked perfectly apart from the changing ownership / group. For some reason on my rom, system.cache does not resolve into the correct UID / GID - which makes /cache eventually have a 'root' ownership and thus the market cannot access it.
The solution is to use
chown 1000:2001 /cache
chown -h 1000:2001 /cache
The second one changes the symlink as well as the target.
This has already been pointed out in a reply but it may have got lost amongst the others!
Will.
original thread - http://forum.xda-developers.com/showthread.php?t=1188972
Click to expand...
Click to collapse
Yeah, I had the same issue. Was surprised how it worked for others without changing the ownership.. I guess you were referring to my reply? ..
Btw, may I know why you can't post in the dev thread?
Hi,
I had seen someone make the same observation I did but I wondered if people had noticed because they were still saying the same thing; I thought it'd help saying it again but I get a feeling a lot of people probably don't know what symlinking is!
I'm surprised though as more and more games are over 30mb now. maybe done custom roms do this automatically?
I can't post in the dev forum because I would guess I don't have a high enough overall post-count.
will.
Sent from my GT-I9000 using XDA Premium App
I wonder how the "old" Market can download files larger then /cache partition, but the new one doesn't (version 3.0.27)? So Google could fix this using some other download location, if cache is small.
Cheers Everyone,
First off, thanks for opening this thread.
I've recently rooted my kindle and was very pleasantly surprised when I noticed a very familiar linux-like file system underneath. Now I'm eager to learn more.
Let me start from what I know (or think I know )
For custom bootloaders, the goto seems to be firefirefire
for recovery mini-os which is recommended? CWMR or TWRP
I hate to ask because I see it all over the forums, but the responses are all over the place. It looks like TWRP had a gui, and easier for backup/restore, but maybe CWMR... performs better?
Ok, let me get to the main questions, understanding android itself.
this all started when I discovered $adb shell
ok, when you install a new ROM it wipes /system from the devise and copies the /system from the zip, also it seems to append to the /data (assuming your rom zip came with applications). Does installing a rom do anything else? I see this file in my zip /META-INF/com/google/android/updater-script and update-binary. Does one of those automatically get run when you use the recovery loader to install a new ROM? Ok, looking at the contents of the file, it seems like it is the script run to install the ROM, it does lots of things like sets up simlinks, and sets permissions.
$ df
Filesystem Size Used Free Blksize
/dev 223M 32K 223M 4096
/mnt/asec 223M 0K 223M 4096
/mnt/obb 223M 0K 223M 4096
/system 503M 296M 207M 4096
/data 1G 76M 1G 4096
/dropbox 4M 1M 3M 1024
/cache 251M 4M 247M 4096
/mnt/sdcard 5G 15M 4G 4096
/mnt/secure/asec: Permission denied
$ echo $PATH
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
Now for some questions:
using adb shell, how do I get root permissions? Infact, what user am I when first start it? what editors are available? (vi?pico?ed? where?)
I looked around after installing modaco rom and I'm surprised to see some files like: TICameraCameraProperties.xml in /system/etc. it's full of camera stuff, i'm surprised to find that on my kindle since there is no camera on the devise. So my question is, with these custom rooms, are extra files littered all about, assuming they were used for other devices and just never removed when ported for the kindle? I'm surprised since modaco is based on stock 6.3.... maybe amazon added it in preparation for the next kindle?
Help me understand what's in the partitions
first, why don't I see /boot or /recovery?
next,
/dev ok, this is for the hardware, but why so big? seems like we could get by with just a few megs
/mnt/asec secure files? any example of this being used? Again, that's alotta space...
/mnt/obb no idea what this is... luv to make it smaller
/system os
/data apps and user files
/dropbox dropbox for what?
/cache assuming swap and paging
Another question, I assume when switching roms from diff android versions, like GB, HC, ICS, you need to wipe and install/reinstall your apps (in /data) since they will need versions specific to the android version you are running? or is each future android version assumed to be backwards compatible...?
Anyone who's taken a look "under the covers" probably has similar questions and I hope one of our more experiences brothers can shed some light on the above questions.
Many thanks to everyone who contributes,
Paul
To get root permissions for adb, type "adb root". If you're in adb shell just type "su". As far as editors go, none that I'm aware of. For that, your best bet would be to get the source. If it's just Android you are interested in then you can get the source from the Android website. If it's the Kindle Fire specifically then you should check out JackpotClavin's tutorial for building cm9 from source. Get your build environment set up, download the source, and then you'll have free reign to edit a huge majority of the files. Just be sure to have +-40Gb to use as your workspace.
The tutorial can be found here
http://forum.xda-developers.com/showthread.php?p=20844007
Depending on your level of programming experience, the rest should be easy to figure out on your own.
Sent from my Amazon Kindle Fire using xda premium
Thanks, I appreciate it! I'll take a look at tutorial in the morning.
Any word on those partition sizes? Seems like lots of wasted space, probably could shave off a half gig to add to /mnt/sdcard... Do you know if those partitions I mention ever fill up?
I don't mess with partitions at all. I've had bad experiences with it in the past so I tend to stay at a safe distance.
User eldarerathis has modded the bootloader to support dual-boot on the Fire so I would check with his thread first. http://forum.xda-developers.com/showthread.php?p=23634393
He seems to have a pretty good understanding of the separate partitions. You'll need a few more posts before you can post in that thread though.
Sent from my Amazon Kindle Fire using xda premium
For those getting an insufficient storage error in the Google play store or when side loading, which only affects specific apps (not all apps, which has been discussed elsewhere) the following may work for you.
The error is caused by application data folders, which you will have to delete and then reinstall the app. Steps to fix are below:
1) Uninstall the app in the app manager
2) Using your favorite file explorer with root access navigate to /Data/app-lib/
3) Find the folder, which corresponds to the package you have having issues with (for instance com.adobe.reader-1 for adobe reader) and delete it
4) Reinstall from the android market
5) OPTIONAL - restore backup of your data from titanium backup.
Hopefully this will prevent you needing to reflash the ROM and format storage, which i was about to do before rooting around in the app-lib folder and noticing the folders for uninstalled apps that I could not re-install were still there.
Dav_prime said:
For those getting an insufficient storage error in the Google play store or when side loading, which only affects specific apps (not all apps, which has been discussed elsewhere) the following may work for you.
The error is caused by application data folders, which you will have to delete and then reinstall the app. Steps to fix are below:
1) Uninstall the app in the app manager
2) Using your favorite file explorer with root access navigate to /Data/app-lib/
3) Find the folder, which corresponds to the package you have having issues with (for instance com.adobe.reader-1 for adobe reader) and delete it
4) Reinstall from the android market
5) OPTIONAL - restore backup of your data from titanium backup.
Hopefully this will prevent you needing to reflash the ROM and format storage, which i was about to do before rooting around in the app-lib folder and noticing the folders for uninstalled apps that I could not re-install were still there.
Click to expand...
Click to collapse
Many thanks , cause i,ve tried everyhting, lucky patcher, clear devil-cache, system-cache, clear market , everything, but this solutions was the only one that works. Now i can install the app
The real problem is a permissions issue. There's a more elegant solution which doesn't involve deleting a folder nor deinstalling an app.
a) With your favorite terminal program navigate to /data/app-lib (/data, not /Data, case is very important). I do this from my Linux box, accessing the phone remotely with the help of SSHDroid.
b) Then, do an "ls -la" to see the files inside this directory along with their permissions. In my case, I see this:
Code:
/data/data/berserker.android.apps.sshdroid/home # cd /data/app-lib
/data/app-lib # ls -la
total 1089
drwxrwx--x 135 system system 8192 Mar 26 17:11 .
drwxrwx--x 25 system system 4096 Mar 26 22:55 ..
drwxr-xr-x 2 system system 4096 Feb 18 17:28 ND.filter-1
drwxr-xr-x 2 system system 4096 Mar 4 17:20 aolmo.WifiCrackWLAN-1
drwxr-xr-x 2 system system 4096 Mar 26 08:06 at.sapps.applauncherdashclockextension-1
drwxr-xr-x 2 system system 4096 Feb 26 19:18 berserker.android.apps.ftpdroid-1
drwxr-xr-x 2 system system 4096 Mar 10 08:25 berserker.android.apps.sshdroid-1
drwxr-xr-x 2 system system 4096 Mar 10 08:26 berserker.android.apps.webdroid-1
...
drwxr-xr-x 2 system system 4096 Mar 21 22:55 pl.baggus.barometr-1
drwxr-xr-x 2 system system 4096 Mar 16 21:08 robj.any.dash-1
drwxr-xr-x 2 system system 4096 Mar 8 16:21 ru.gloom.SMSExtension-1
drwxr-xr-x 2 system system 4096 Mar 2 19:10 stericson.busybox-2
As you can see, every folder belongs to system:system and has the "drwxr-xr-x" permissions. If, for whatever reason, the folder corresponding to the non-working app looked different, the fix is easy:
1) If it had a different user or group, run this command:
Code:
chown -R system:system [I]name.of.the.folder[/I]
2) If it had different permissions, run this command:
Code:
chmod -R 755 [I]name.of.the.folder[/I]
That's it!
Of course, if the problem lies inside a folder other than /data/app-lib, just navigate to the corresponding folder
Also...
MOD EDIT @gregbradley
XDA RULES
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
Click to expand...
Click to collapse
This may work for some people, usually when there is a .odex file left over from some previous processes. For me it did not work, which is why I had to do it the way I posted in the OP.
Just clear data
None of the above worked for me. I saw on another site to go in the App Manager (Settings > Apps) and "clear data" for the troubled app(s). This worked for me.
Dav_prime said:
For those getting an insufficient storage error in the Google play store or when side loading, which only affects specific apps (not all apps, which has been discussed elsewhere) the following may work for you.
The error is caused by application data folders, which you will have to delete and then reinstall the app. Steps to fix are below:
1) Uninstall the app in the app manager
2) Using your favorite file explorer with root access navigate to /Data/app-lib/
3) Find the folder, which corresponds to the package you have having issues with (for instance com.adobe.reader-1 for adobe reader) and delete it
4) Reinstall from the android market
5) OPTIONAL - restore backup of your data from titanium backup.
Hopefully this will prevent you needing to reflash the ROM and format storage, which i was about to do before rooting around in the app-lib folder and noticing the folders for uninstalled apps that I could not re-install were still there.
Click to expand...
Click to collapse
well.... there's a problem for me, i open up /data, but /app-lib is missing
terrybear2k said:
well.... there's a problem for me, i open up /data, but /app-lib is missing
Click to expand...
Click to collapse
Which /data directory are you in? Did you navigate up to root first?
Good looks! Gonna try this next time I get a 'insufficient storage' message.
Dav_prime said:
Which /data directory are you in? Did you navigate up to root first?
Click to expand...
Click to collapse
i guess its root, the content is different from my sdcard's, (eg. acct, app-cache, cache, config, data, dev) with es file explorer. but then i use sd-maid, i can see the contents inside "data". guess es stopped 1/2 of the support for browsing root folders?? weird... but still, when using sd-maid the app-lib still missing. i can see "anr, app, app-asec, app-private, audio"
Dav_prime said:
Which /data directory are you in? Did you navigate up to root first?
Click to expand...
Click to collapse
I also do not have /data/app-lib, and I'm certain I nav'd up to root first. any suggestions would be most welcome. I'm unable to install *any* new app, either from Play, or as a side-load.
tia, RA
rrtid54 said:
I also do not have /data/app-lib, and I'm certain I nav'd up to root first. any suggestions would be most welcome. I'm unable to install *any* new app, either from Play, or as a side-load.
tia, RA
Click to expand...
Click to collapse
found a fix that worked for me, and others here:
http://forum.xda-developers.com/showpost.php?p=32155340&postcount=12
Yeah there are a lot of causes for these errors so this may not be the fix you need.
I have the app-lib folder on my nexus4 running stock 4.4.
What devices and roms are you running?
Dav_prime said:
Yeah there are a lot of causes for these errors so this may not be the fix you need.
I have the app-lib folder on my nexus4 running stock 4.4.
What devices and roms are you running?
Click to expand...
Click to collapse
thanks for the reply. device is a VZW Galaxy S3, rooted but stock ROM, 4.1.2. 'link2sd' worked to correct the problem.
be well, RA
I recently started having this problem with hangouts and Google drive, and I can't find the corresponding folders in my app-lib folder. Anyone know where google stores those files?
cliffyb said:
I recently started having this problem with hangouts and Google drive, and I can't find the corresponding folders in my app-lib folder. Anyone know where google stores those files?
Click to expand...
Click to collapse
Look in /system/app
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Look in /system/app
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I found the hangouts apk in /system/app/ but deleting that just uninstalls hangouts, and attempting to reinstall just gives me the insufficient space message again
cliffyb said:
I found the hangouts apk in /system/app/ but deleting that just uninstalls hangouts, and attempting to reinstall just gives me the insufficient space message again
Click to expand...
Click to collapse
I would try flashing the cache.img from the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
edmann
OK, thanks dav_prime. /data/app-lib worked like a charm. I used root explorer and instead of fishing through things I deleted the whole file. Reinstalled from play store no error message.
Dav_prime said:
For those getting an insufficient storage error in the Google play store or when side loading, which only affects specific apps (not all apps, which has been discussed elsewhere) the following may work for you.
The error is caused by application data folders, which you will have to delete and then reinstall the app. Steps to fix are below:
1) Uninstall the app in the app manager
2) Using your favorite file explorer with root access navigate to /Data/app-lib/
3) Find the folder, which corresponds to the package you have having issues with (for instance com.adobe.reader-1 for adobe reader) and delete it
4) Reinstall from the android market
5) OPTIONAL - restore backup of your data from titanium backup.
Hopefully this will prevent you needing to reflash the ROM and format storage, which i was about to do before rooting around in the app-lib folder and noticing the folders for uninstalled apps that I could not re-install were still there.
Click to expand...
Click to collapse
Thanks!
Dav_prime said:
For those getting an insufficient storage error in the Google play store or when side loading, which only affects specific apps (not all apps, which has been discussed elsewhere) the following may work for you.
The error is caused by application data folders, which you will have to delete and then reinstall the app. Steps to fix are below:
1) Uninstall the app in the app manager
2) Using your favorite file explorer with root access navigate to /Data/app-lib/
3) Find the folder, which corresponds to the package you have having issues with (for instance com.adobe.reader-1 for adobe reader) and delete it
4) Reinstall from the android market
5) OPTIONAL - restore backup of your data from titanium backup.
Hopefully this will prevent you needing to reflash the ROM and format storage, which i was about to do before rooting around in the app-lib folder and noticing the folders for uninstalled apps that I could not re-install were still there.
Click to expand...
Click to collapse
Very Helpful! Thanks a lot!
--Rafael
I'm wondering why some apps are installed in standard /data/app (where I can take a backup of my data partition), and some in /mnt/asec (where they're not backup up)??
Furthermore, is there a way to force android to install apps to /data/app, which is where I would rather have them installed? And is there an easy way to move already installed apps from /mnt/asec to /data/app ??
Thanks in advance, I really hope someone can help me out here. When flashing a new rom, it would be so much easier if all apps were located in /data/app !! Thanks
ameinild said:
I'm wondering why some apps are installed in standard /data/app (where I can take a backup of my data partition), and some in /mnt/asec (where they're not backup up)??
Furthermore, is there a way to force android to install apps to /data/app, which is where I would rather have them installed? And is there an easy way to move already installed apps from /mnt/asec to /data/app ??
Thanks in advance, I really hope someone can help me out here. When flashing a new rom, it would be so much easier if all apps were located in /data/app !! Thanks
Click to expand...
Click to collapse
So after looking around for a bit, I think that the /mnt/asec folder is related to apps with copy-protection/DRM. What I found in my /mnt/asec directory was folders of only my purchased games, which are most likely DRM protected. So the answer to your question is that the /mnt/asec folder is for copy-protection. I may be wrong though.
Someone please correct me if I'm wrong
vorbatello said:
So after looking around for a bit, I think that the /mnt/asec folder is related to apps with copy-protection/DRM. What I found in my /mnt/asec directory was folders of only my purchased games, which are most likely DRM protected. So the answer to your question is that the /mnt/asec folder is for copy-protection. I may be wrong though.
Someone please correct me if I'm wrong
Click to expand...
Click to collapse
I think you're right. I also read somewhere that this is an encrypted volume for paid apps. Now, the interesting thing would be to find a way to circumvent this encryption to force all apps to the /data/app folder
I'm looking further into this...
ameinild said:
I think you're right. I also read somewhere that this is an encrypted volume for paid apps. Now, the interesting thing would be to find a way to circumvent this encryption to force all apps to the /data/app folder
I'm looking further into this...
Click to expand...
Click to collapse
Paul O'Brien had already done this on the One so perhaps ask him...
Sent from my Nexus 4 using xda premium
EddyOS said:
Paul O'Brien had already done this on the One so perhaps ask him...
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for the help and constructive dialogue everyone. Because of this, I actually found Paul O'Brien's Xposed module which disables Play Store encryption, here:
http://www.modaco.com/topic/361776-xmod-disable-play-store-encryption-mntasec/
And I can confirm that this works exactly as expected on the Nexus 4!
So now I'm in the process of reinstalling my paid apps to /data/app, which enables me to take a complete backup of my data partition and restore it to any freshly installed ROM, paid apps included! :good:
Thanks for this!
It's a Google Thing...
Hi; Just started happening again with Jellybean.
I just use LINK2SD to decrypt and move them to the /data/* directory.
From there I can move them to the internal SD card or link to an External SD/TF card second partition.
Cheers,
BuBu