Develop Bugs

[Q] JB can't see files on the SD card?

Next JB problem: When I installed stock JB, I did a wiped data/cache, but when I booted up, I could see that all the folders were still there in Root Explorer as well as Airdroid. But, Android can't see them. What I mean is, if I open up Gallery, it claims I have no pictures stored on the device, despite actually having hundreds of pictures in several folders. Quickpic sees them just fine, but Gallery doesn't. I'd rather use Gallery because it can find pics from Picasa, which saves a ton of space on the phone.
How do I get my phone to see the folders that are still there?
I updated to Bigxie's ROM, but that didn't resolve it (not that I necessarily expected it to).

sorry, can't really help, as it worked for me without problem from the beginning.
maybe it just takes some time until media scan was operated? or are you using any filters like the .nomedia-manager?

No .nomedia files. If I plug in a USB port to connect it to my PC, it only shows a few empty folders, nowhere near all that are there. There's a Pictures folder, but it's empty, even though my Pictures folder actually has a bunch of files and folder s in it. It's like it's looking at some other partition or something.

That happens to me... i fix it by restoring my previos rom backup, and then doind a dirty flash of the JB Rom (only Dalvik and Cache wipe)

Same here .. no media file in gallery so I flash my old rom...
Sent from my Galaxy Nexus using XDA Premium App

Raisone said:
That happens to me... i fix it by restoring my previos rom backup, and then doind a dirty flash of the JB Rom (only Dalvik and Cache wipe)
Click to expand...
Click to collapse
That sounds like a good solution, except whatever it is that's preventing me from finding my media files is also preventing me from accessing my Nandroid backup.
E:Unknown volume for path [/emmc/clockworkmod/backup/2012-06-28.00.32.22]
Cat't mount backup path
result was NULL. message is: assert failed:
restore_rom("/emmc/clockworkmod/backup/2012-06-28.00.32.22". "boot", "system", "data", "cache", "sd-ext")
I:using /data/media, no /sdcard found.

Might have to do with the sdcard being linked to another folder in storage
KJW979 said:
Didn't see mentioned in here but over at rootzwiki is being mentioned that the reason some can't wipe and return to a previous rom might have to do with JB adding a new folder named storage. If go into root explorer or similar right below folder Sd there is a storage folder if opened brings up another folder named sd, seems to be a duplicate sd folder. I can't remember ever seeing it on any previous rom's. Also nobody sure consequences if deleted. Personally not much knowledge, just passing along.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse

I'll have to remember that for next time. I gave up and did a factory wipe from Galaxy Nexus Tools, and am in the process of restoring my Nandroid, then I'll do a 'dirty' JB upgrade from there and hope it doesn't do the same thing twice. If it does, I'll just stick to ICS.

NeoMagus said:
Might have to do with the sdcard being linked to another folder in storage
Click to expand...
Click to collapse
Just saw that, thank you for your post. It's weird, though, is it mirroring the SD card? I've got my SD card almost full, and if it duplicated it I would have gone way over.

I decided not to take any more chances now that I'm back to ICS. I'll wait for the official release. I don't think Google Now and the smoothness make up for the loss of themes and customization.
Sent from a connected, sensor-laden supercomputer that fits in my pocket

Did anyone find a way to fix this without a reflash?

Archpope said:
Next JB problem: When I installed stock JB, I did a wiped data/cache, but when I booted up, I could see that all the folders were still there in Root Explorer as well as Airdroid. But, Android can't see them. What I mean is, if I open up Gallery, it claims I have no pictures stored on the device, despite actually having hundreds of pictures in several folders. Quickpic sees them just fine, but Gallery doesn't. I'd rather use Gallery because it can find pics from Picasa, which saves a ton of space on the phone.
How do I get my phone to see the folders that are still there?
I updated to Bigxie's ROM, but that didn't resolve it (not that I necessarily expected it to).
Click to expand...
Click to collapse
Where did you find a Galaxy Nexus with a SD card slot?

[MOD] Xoom: symlink /system/apps to /data for GApps on CM10-based ROMs (11/28 update)

Disclaimer: This mod is provided as is. I am not responsible for you or your actions, I can barely handle myself most days. This will probably kill your dog and frame your spouse, so if your not feeling up for it, maybe sit this out.
What is this?
This addresses the lack of space on the /system partition that has been forcing people to compromise on GApps packages, and generally be subjected to wonky behavior.
How do I install it?
First you must make a nandroid. This is a flashable zip that you apply in recovery *in between* flashing cm10 and GApps. *NOTE* There are -NO- GApps in this download. This is just a shim to make room for them!
How does this work?
It's mostly edify, with a shell script that shouldn't have been necessary, but I got impatient, and hell, it works.
What it does is it will create folder on your /data partition called /data/system.app.
It makes sure that the permissions match the original.
Then it will migrate the *entire* contents of the traditional /system/app folder into the new folder, also preserving the owners, permissions and attributes of files
Finally, it deletes the original, and creates a symlink in its place, so that anything that tries to read, or write, to that folder, will end up on the /data partition.
You can now install a full GApps package, and you'll have a lofty 25MB or so to spare!
Is it safe?
I have tested this on my 4G Stingray using CM10 nightlies and Rogue Recovery as both a clean flash and an upgrade. It works under that configuration. See "Before you download" below for currently known issues.
Is this only for the Stingray?
Yes and no. Yes, I only have that one device that suffers the partition issue, and on which to test this. No, I don't see why it couldn't work for at least one other device. But still probably don't try it unless you really know what you're doing.
Why did you make this?
I wanted to solved this problem, and now it's my gift to you all! Enjoy!
Can I incorporate this in my ROM or on my website or at my grandmother's bingo party?
Knock yourselves out. I hope this ends up being super helpful for everybody.
Something broke and it's all your fault!
Before you download!
Make a nandroid! This is twice that I'm telling you, so I mean it!
As of right now, if you were to factory reset your device, it would be necessary to restore or reflash from recovery. Do not factory reset if you apply this mod! (Thanks runandhide05!)
This mod does not work with TWRP recovery at the moment (But I'm working on it). (Thanks dodgefan67!)
Face unlock currently fails to install. I am working to address this.
Some future version will use addon.d so that you don't have to flash this every time. This will be implemented once the above issues have been dealt with.
The zip file was updated on 11/28 to fix an issue where the shell script had windows-style line endings, causing it not to run in TWRP and possibly some other recoveries.
The download:
http://www.tangerinepulsar.com/files/cm10-xoom-system-symlink-mod-signed.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

the only problem i see here is that you have no way to backup you rom, well, if you run a backup it will say its successful, but you have nothing to get /data/system.app backed up and re symlinked when you restore, and if you preform a factory reset you will loose all of your system apps,
you should look at how EOS symlinks there gapps data at /data/ you have to include addon.d scripts so that if you run a backup it will backup your new folder too, otherwise problems may/will happen.
edit:
for example for the /usr/srec stuff ( google now hotword and talk back files) you have to do something like this
Code:
. /tmp/backuptool.functions
list_files() {
cat <<EOF
EOF
}
case "$1" in
backup)
list_files | while read FILE DUMMY; do
backup_file $S/$FILE
done
;;
restore)
list_files | while read FILE REPLACEMENT; do
R=""
[ -n "$REPLACEMENT" ] && R="$S/$REPLACEMENT"
[ -f "$C/$S/$FILE" ] && restore_file $S/$FILE $R
done
ln -s /data/eos-srec /system/usr/srec
;;
pre-backup)
# Stub
;;
post-backup)
# Stub
;;
pre-restore)
# Stub
;;
post-restore)
# Stub
;;
esac

runandhide05 said:
the only problem i see here is that you have no way to backup you rom, well, if you run a backup it will say its successful, but you have nothing to get /data/system.app backed up and re symlinked when you restore, and if you preform a factory reset you will loose all of your system apps,
you should look at how EOS symlinks there gapps data at /data/ you have to include addon.d scripts so that if you run a backup it will backup your new folder too, otherwise problems may/will happen.
Click to expand...
Click to collapse
I'll definitely look at incorporating this approach, thanks!
At the time I didn't think that backups were that big of a deal so long as you backed up both system and data, all of the symlinks would still be intact. I did write the edify script in such a way that it allows for an existing /system.app folder to already be there and will re-symlink it. But there are always times when you want to restore one and not the other, or switch ROMs without losing data, and this doesn't handle that at all. I definitely agree that a factory reset would trash you pretty badly, it's not a scenario that I accounted for in any way.
Thanks for the nudge in the right direction, I'll keep working on this.

Thanks for workings on this, very exciting news.

I'll start cranking out eos test builds soon. Then I'll take a look at what kind of gapps solutions are available. One thing for sure is it will be a bare bones package. That means anything that can be acquired from the Store will be.

this is good news indeed. i will try this out on my wifi xoom in the next day or two
i understand about doing a factory reset, but if i just update from one nightly to another (dirty flash) i would have to run this each time as well, correct?

dodgefan67 said:
this is good news indeed. i will try this out on my wifi xoom in the next day or two
i understand about doing a factory reset, but if i just update from one nightly to another (dirty flash) i would have to run this each time as well, correct?
Click to expand...
Click to collapse
You should not have to.
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
You should not have to.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
doesn't the script actually move the contents of /system/apps though? installing a new version would put apps there right? and overwrite the symlinks?

dodgefan67 said:
doesn't the script actually move the contents of /system/apps though? installing a new version would put apps there right? and overwrite the symlinks?
Click to expand...
Click to collapse
Well it depends on how/if he updated it.
But if its the same as earlier then ya you will need to reflash.
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
You should not have to.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
dodgefan67 said:
this is good news indeed. i will try this out on my wifi xoom in the next day or two
i understand about doing a factory reset, but if i just update from one nightly to another (dirty flash) i would have to run this each time as well, correct?
Click to expand...
Click to collapse
runandhide05 said:
Well it depends on how/if he updated it.
But if its the same as earlier then ya you will need to reflash.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I haven't released an update yet. Please reflash per the current instructions. I'll make it obvious when the script has changed.

ok, i used CM10 stable from 11/13/2012 and the official GApps JB package from 10/11/2012
flashed CM10
flashed this mod
flashed gapps
on first boot, i did not get any google account sign on screens, went straight to homescreen, no play store or any google apps installed
reflashed gapps and rebooted and this time i got the play store and google search, but that's it. is there more to gapps? i think they took out gmail, but would expect more for a 90meg file. never really looked at this, i have been using the EOS version of gapps with Zigackly's rom
by the way, according to TB i have 29.4mb left on /system and that is before i remove the other stuff i dont want. so it seems to have worked on a MZ604 wifi device
i will use it this way for a couple of days, restoring some apps and installing things and changing settings and see how it goes. then i will update to a nightly and see how that goes
so far so good

dodgefan67 said:
ok, i used CM10 stable from 11/13/2012 and the official GApps JB package from 10/11/2012
flashed CM10
flashed this mod
flashed gapps
on first boot, i did not get any google account sign on screens, went straight to homescreen, no play store or any google apps installed
reflashed gapps and rebooted and this time i got the play store and google search, but that's it. is there more to gapps? i think they took out gmail, but would expect more for a 90meg file. never really looked at this, i have been using the EOS version of gapps with Zigackly's rom
by the way, according to TB i have 29.4mb left on /system and that is before i remove the other stuff i dont want. so it seems to have worked on a MZ604 wifi device
i will use it this way for a couple of days, restoring some apps and installing things and changing settings and see how it goes. then i will update to a nightly and see how that goes
so far so good
Click to expand...
Click to collapse
I'm a little perturbed about the way that first flash went. If you experience that again, will you please post the log from /cache/recovery prior to the re-flash? I want to make sure that there's not some scenario that I'm not handling properly with just one flash.
BTW, Did you flash it all from recovery or did you use something like ROM Manager or ROM Toolbox to script the recovery actions? Just so I cover my bases.

oscillot said:
I'm a little perturbed about the way that first flash went. If you experience that again, will you please post the log from /cache/recovery prior to the re-flash? I want to make sure that there's not some scenario that I'm not handling properly with just one flash.
BTW, Did you flash it all from recovery or did you use something like ROM Manager or ROM Toolbox to script the recovery actions? Just so I cover my bases.
Click to expand...
Click to collapse
i will do it again and get you the log file. i'm using twrp and did it all from there. i even did each zip one at a time even though twrp lets you do multiple ones in one go

good news and bad, i got the log file but i had to dump it to a plain text file so it is hard to read, but if you search for symlink-mod you will find the section where your mod starts and right after that is where i flashed gapps ***edit***never mind about the formatting, i clicked the attachment below using Chrome and it came up fine
i was able to duplicate my issue. i wiped everything three times and installed a different rom and different gapps package and everything was fine. then i wiped three more times and installed cm10 stable, your mod, then the official jb gapps, rebooted and same thing. no google apps installed. this log file is from right after the first reboot
then i went back and flashed gapps again, rebooted and have the play store
i can put CWM on it and try it with that recovery if you want

Here is the problem, u can not have anything in the /system/app folder.. Nothing at all, so the problem lays that if you try to flash a ROM, then the sy link it will copy everything in system/app to data, remove the directory (system/app) then link it to the new directory in /data. Then you are trying to flash gapps which tries to put stuff in /system/app which that directory does not exist so its going to create it. Which will undo the symlink or will not be able to flash anything to /app.
So for the sy link to work u must flash both rom and gapps, which is where the problem of limited space cause now u won't get all your files over to the /system because not enough room. So to fix this you can do one of several things, one of which would be...
Change the gapps package to where the system apps flash to the new /data directory created by the sysmlink.
So if the new directory is /data/sysapp/ open the gapp package and take all the system/app/ and move it to a new folder on the root of the zip called data then in there create a folder called sysapp and put all the /system/app/ content in there. And remember to update the updater script for the resource "data" "/data" and that "should" fix it
Sent from my Galaxy Nexus using Tapatalk 2

dodgefan67 said:
good news and bad, i got the log file but i had to dump it to a plain text file so it is hard to read, but if you search for symlink-mod you will find the section where your mod starts and right after that is where i flashed gapps ***edit***never mind about the formatting, i clicked the attachment below using Chrome and it came up fine
i was able to duplicate my issue. i wiped everything three times and installed a different rom and different gapps package and everything was fine. then i wiped three more times and installed cm10 stable, your mod, then the official jb gapps, rebooted and same thing. no google apps installed. this log file is from right after the first reboot
then i went back and flashed gapps again, rebooted and have the play store
i can put CWM on it and try it with that recovery if you want
Click to expand...
Click to collapse
Okay, I see a couple of things that are downright strange. To start off, the reason it looks like a flat text file is because the line-breaks are unix-style ('\n') and windows apps generally don't show linebreaks unless they have a carriage return preceding a newline character ('\r\n'). Open files from android in Notepad++ and they'll render much more nicely. Turn on viewing end of line characters and you'll see the difference between the Windows and Unix styles of newlines.
In practice, these are invisible control characters that don't visibly render, except in so far as their introduction of a line-break. '\r' and '\n' are aliases of them used in programming. They are actually the hex values 0A and 0D. But, since they are also characters, unexpected ones will have some kind of effect.
On lines 4066-4067 I see an error in the copy.sh: "/tmp/copy.sh: line 2: '\r' : not found"
There is a stray carriage return in the middle of this log file. There should be none. Line 2 in that file is BLANK. The source *should* have a single unix-newline '\n' and nothing else. I would bet that busybox is trying to interpret it and as a result, the shell script never runs. Nothing is getting copied out of /system/app.
I checked the zip I uploaded, and sure enough, the shell script has windows-style line endings. Oops. I've replaced it with a version that does not, but is identical other than that. So that part is fixed. Not sure why it works in CWM and not in TWRP, as far as I'm concerned, it shouldn't have worked in either. They must have slightly different busybox binaries is all that I can think.
The other issue is that both the deletion of /system/app and the subsequent symlinking both claim to have worked. However it's clear that /system/app was not deleted because if it were, you wouldn't have booted correctly. The symlink couldn't have worked either because you can't symlink a location that has files in it. So what in the world happened here? I'm kind of not sure, especially since those steps each returned 0, or else we wouldn't have gotten the success messages.
The wrinkle that you got *no* gapps after a flash is even stranger. But There is one more bit of interest here. I see an error message on line 4135 "cp: target '/system/app' is not a directory". At this point, this is the gapps trying to install face-unlock. I went ahead and looked in my own log files and here's what I found: "cp: target '/system/app' is not a directory." I never used it, but further inspection confirms, no portion of the face-unlock is installed using my mod, and the reason is the syntax of the gapps install-optional.sh: "cp -a /tmp/face/* /system/". Because /system/app is a symlink, you cannot copy the folder /tmp/face/app over it successfully.
This begs the question, how is it displaying the properties of being both a symlink and NOT a symlink?
I'm going to work on these issues, and I'll probably flash TWRP and test against it as well and try to come up with some answers and a one-size-fits-all solution. In the mean time, I would appreciate it if you could confirm whether you have a /data/system.app directory, and if so, what the contents are. I have a hunch that you'll find the gapp apks (minus face-unlock) in that directory, but none of the system apps. I'm not sure how that would be possible, or what it means, but it makes the most sense from where I'm standing. In the meantime, I'm going to add some notes to the main post.
I'll hopefully get some of this figured out by this weekend.

oscillot said:
Okay, I see a couple of things that are downright strange. To start off, the reason it looks like a flat text file is because the line-breaks are unix-style ('\n') and windows apps generally don't show linebreaks unless they have a carriage return preceding a newline character ('\r\n'). Open files from android in Notepad++ and they'll render much more nicely. Turn on viewing end of line characters and you'll see the difference between the Windows and Unix styles of newlines.
In practice, these are invisible control characters that don't visibly render, except in so far as their introduction of a line-break. '\r' and '\n' are aliases of them used in programming. They are actually the hex values 0A and 0D. But, since they are also characters, unexpected ones will have some kind of effect.
On lines 4066-4067 I see an error in the copy.sh: "/tmp/copy.sh: line 2: '\r' : not found"
There is a stray carriage return in the middle of this log file. There should be none. Line 2 in that file is BLANK. The source *should* have a single unix-newline '\n' and nothing else. I would bet that busybox is trying to interpret it and as a result, the shell script never runs. Nothing is getting copied out of /system/app.
I checked the zip I uploaded, and sure enough, the shell script has windows-style line endings. Oops. I've replaced it with a version that does not, but is identical other than that. So that part is fixed. Not sure why it works in CWM and not in TWRP, as far as I'm concerned, it shouldn't have worked in either. They must have slightly different busybox binaries is all that I can think.
The other issue is that both the deletion of /system/app and the subsequent symlinking both claim to have worked. However it's clear that /system/app was not deleted because if it were, you wouldn't have booted correctly. The symlink couldn't have worked either because you can't symlink a location that has files in it. So what in the world happened here? I'm kind of not sure, especially since those steps each returned 0, or else we wouldn't have gotten the success messages.
The wrinkle that you got *no* gapps after a flash is even stranger. But There is one more bit of interest here. I see an error message on line 4135 "cp: target '/system/app' is not a directory". At this point, this is the gapps trying to install face-unlock. I went ahead and looked in my own log files and here's what I found: "cp: target '/system/app' is not a directory." I never used it, but further inspection confirms, no portion of the face-unlock is installed using my mod, and the reason is the syntax of the gapps install-optional.sh: "cp -a /tmp/face/* /system/". Because /system/app is a symlink, you cannot copy the folder /tmp/face/app over it successfully.
This begs the question, how is it displaying the properties of being both a symlink and NOT a symlink?
I'm going to work on these issues, and I'll probably flash TWRP and test against it as well and try to come up with some answers and a one-size-fits-all solution. In the mean time, I would appreciate it if you could confirm whether you have a /data/system.app directory, and if so, what the contents are. I have a hunch that you'll find the gapp apks (minus face-unlock) in that directory, but none of the system apps. I'm not sure how that would be possible, or what it means, but it makes the most sense from where I'm standing. In the meantime, I'm going to add some notes to the main post.
I'll hopefully get some of this figured out by this weekend.
Click to expand...
Click to collapse
Any new news on this?

A little update on what I tried on my MZ-601 Everest. Any feedback will be welcome
Basically what I did was:
1. Trimmed down the CM10 Stable a little (132MB vs the original 141MB) by removing mainly the wallpapers.
2. Flashed the modified CM10 Stable zip (after a full wipe - factory plus cache).
3. Modified the Mod Script to point to "/data/system/app" (just to satisfy my OCD ) then flashed the zip. On first try it aborted with Status 7 on "Fixing permissions" so I had to manually create the directory "/data/system/app" after which the flash was successful.
4. Modified the GApps package (GApps from 11th Oct) by:
a. Removing the "optional" directory, install script and removing the relevant lines from "updater-script",
b. Moving the "/system/app" directory to "/data/system" and
c. Modifying the "updater-script" to reflect the change.
5. Flashed the GApps zip package which went uneventfully.
6. I now have 51.4MB free in "/system" according to Titanium Backup
PS: I am including the modified "Mod Script" and "updater-script" from GApps package if anyone else wants to try it. Of course you mileage may vary and I cannot claim any responsibility for any loss of data that may occur
UPDATE: Tried it with the CM10.1 nightlies and it works flawlessly. Flashed the nightly over the last nightly, flashed this script then the official gpaps and rebooted. All the settings and customizations retained! Still have some 56MB left in /system

NFS: MW issue with data when switching Roms

I have been trying for the life of me to figure out the way, or if it's possible to keep progress from the game when updating or switching roms. As of now, Titanium Backup doesn't work, or does saving the data/game files and transferring them. Once you try to do either, it says that your unauthorized. Then you have to start fresh and re-download the 2 million gig game and files. I contacted firemonkey and they said rooted devices aren't supported. Don't remember seeing that on play, and it should be. Regardless, I paid for the game.....why am I not authorized to continue progress, and forced to start over from scratch when the newest version of pie is out? There has to be a way to keep progress....?:fingers-crossed:

I'm not sure how much this will help you but maybe it will be what you are looking for:
I recently had a problem where NFS:WM would crash on startup, and apparently the only thing to do (according to firemonkey) is just clear data and lose all progress. Having almost completed everything, I wasn't having any of that.
I'm not rooted but do have my bootloader unlocked so that I can fastboot TWRP to do backups, which also happens to give me root access when booted into TWRP. I made a backup and looked through it to try and and a problem. No luck there, but I did figure out that the game progress is stored in a single file. No config data or anything as far as I can tell, just the progress. So I cleared the data, ran the game through the first level, then copied that old progress file over the new one and I had it back up and going with all progress intact. It's basically a clean install, and since all of the config data is still part of the new install, it didn't cause me any problems.
I did download all of the game data again ultimately, however. But an earlier test of saving "/sdcard/Android/data/com.ea.games.nfs13_na/" and putting it back to avoid the download did work, although it could have been a fluke.
Anyway the file in question is "/data/data/com.ea.games.nfs13_na/files/var/nfstr_save.sb". Just save that one file, install the game from scratch otherwise, run it the first time, then copy that saved progress file over the new one. Assuming that there isn't anything else going on that I didn't find, that should solve your problem.

mtrs said:
I'm not sure how much this will help you but maybe it will be what you are looking for:
I recently had a problem where NFS:WM would crash on startup, and apparently the only thing to do (according to firemonkey) is just clear data and lose all progress. Having almost completed everything, I wasn't having any of that.
I'm not rooted but do have my bootloader unlocked so that I can fastboot TWRP to do backups, which also happens to give me root access when booted into TWRP. I made a backup and looked through it to try and and a problem. No luck there, but I did figure out that the game progress is stored in a single file. No config data or anything as far as I can tell, just the progress. So I cleared the data, ran the game through the first level, then copied that old progress file over the new one and I had it back up and going with all progress intact. It's basically a clean install, and since all of the config data is still part of the new install, it didn't cause me any problems.
I did download all of the game data again ultimately, however. But an earlier test of saving "/sdcard/Android/data/com.ea.games.nfs13_na/" and putting it back to avoid the download did work, although it could have been a fluke.
Anyway the file in question is "/data/data/com.ea.games.nfs13_na/files/var/nfstr_save.sb". Just save that one file, install the game from scratch otherwise, run it the first time, then copy that saved progress file over the new one. Assuming that there isn't anything else going on that I didn't find, that should solve your problem.
Click to expand...
Click to collapse
Awesome. I'll give this a try. :good:

I use MyBackup Pro. I backed up the data and apk from my Nexus and transfered it to me Evo LTE. I restored the apk and data. It does prompt me to reinstall the other game data, which is fine with me. I found if I tried to copy it from one device to the other it would cause the game to crash randomly
Sent from my Nexus 7 using Tapatalk 2

most likely because of the device id (which is the id you see when you type "adb devices" in a command prompt). it's supposed to stay constant in the lifetime of the device (except for factory reset)

[Q] Storage Space Running Out, Insufficient storage, my phone trying to screw me?

So...
I've had this problem for a while now, getting worse from day to day. I've asked about this before, but it wasnt solved.
Basically my phone is taking up data in the background. Probably updating, downloading something. Its so bad, that if i dont turn off data on the go, my 1.5GB are used in a day. Sync is turned off at all times
And another side effect of that is, that all that data probably has to be stored somewhere. So Im getting the storage space running out error. Kinda annoying cause I cant use gmail, Cant install any apps(insufficient storage available) etc.
I really have no idea where all that data is(after searching through all the folders for a while now)..
I'm on the latest AOKP Milestone(4.2)
Thanks!

There are a couple things I recommend doing in your position. First thing I would do would be to get an app that allows for more informative breakdown of what is using the storage. Something like diskusage should do the trick. This will allow you to see exactly where data is going, opposed to "misc" Perhaps this will show exactly what is taking up the storage, since you are rooted perhaps backups are the problem.
If that doesn't tell you what you want to know, or if you think an app may be using data behind the scenes then the next step I would do is to use some sort of data usage monitor. The built in one may suffice, settings > data usage. If not there may be better apps out there, although to be honest I have zero experience with those.

cupfulloflol said:
There are a couple things I recommend doing in your position. First thing I would do would be to get an app that allows for more informative breakdown of what is using the storage. Something like diskusage should do the trick. This will allow you to see exactly where data is going, opposed to "misc" Perhaps this will show exactly what is taking up the storage, since you are rooted perhaps backups are the problem.
If that doesn't tell you what you want to know, or if you think an app may be using data behind the scenes then the next step I would do is to use some sort of data usage monitor. The built in one may suffice, settings > data usage. If not there may be better apps out there, although to be honest I have zero experience with those.
Click to expand...
Click to collapse
Uploaded a pic what diskusage says. When i hit media it only opens the file manager and directs me to sd storage
BTW this what Onavo says has been consuming data this month:
Market Downloader - 800MB mobile, 2.4Gb Wifi, all in background - and no, i didnt download anything from the play store on the go and hardly anything on wifi - havent updated my apps in weeks b/c of missing storage
Android OS + Others - 530MB mobile and a whooping 12GB on Wifi! All in Background too.

Timoooo said:
Uploaded a pic what diskusage says. When i hit media it only opens the file manager and directs me to sd storage
Click to expand...
Click to collapse
It looks like you have some nested 0 folders in that pic. Perhaps cleaning that up will clear up some space. Side note, if you haven't updated your custom recovery in a long time it may not be a bad time to look into that.
BTW this what Onavo says has been consuming data this month:
Market Downloader - 800MB mobile, 2.4Gb Wifi, all in background - and no, i didnt download anything from the play store on the go and hardly anything on wifi - havent updated my apps in weeks b/c of missing storage
Android OS + Others - 530MB mobile and a whooping 12GB on Wifi! All in Background too.
Click to expand...
Click to collapse
If I were in your situation, I would probably just get a clean start. This also would get rid of the nesting problem I mentioned above.
- I would make a backup of my current setup, probably just using Titanium Backup.
- Backup everything I want to keep from my phone to my PC, going through the 0 folders.
- Use fastboot to flash factory images, allowing it to wipe everything in the process. The .bat file should do this automatically.
- Use fastboot to install a recent custom recovery.
- Push the sdcard backup from my PC to my phone.
From here you have a couple options, root and reinstall Titanium backup and restore some of your apps (no system data) or go back into custom ROMs. You could flash AOKP again, or pick a different ROM.
A bit heavy handed, but I think that would be the least time consuming option considering the problem(s).

cupfulloflol said:
It looks like you have some nested 0 folders in that pic. Perhaps cleaning that up will clear up some space. Side note, if you haven't updated your custom recovery in a long time it may not be a bad time to look into that.
Click to expand...
Click to collapse
Yeah I noticed that like half a year ago, had no idea why that happened. At one point I felt like everytime I flashed a new rom a new 0 folder appeared.. How does that happen?
cupfulloflol said:
If I were in your situation, I would probably just get a clean start. This also would get rid of the nesting problem I mentioned above.
- I would make a backup of my current setup, probably just using Titanium Backup.
- Backup everything I want to keep from my phone to my PC, going through the 0 folders.
- Use fastboot to flash factory images, allowing it to wipe everything in the process. The .bat file should do this automatically.
- Use fastboot to install a recent custom recovery.
- Push the sdcard backup from my PC to my phone.
From here you have a couple options, root and reinstall Titanium backup and restore some of your apps (no system data) or go back into custom ROMs. You could flash AOKP again, or pick a different ROM.
A bit heavy handed, but I think that would be the least time consuming option considering the problem(s).
Click to expand...
Click to collapse
I was actually thinking about a clean start, googleing how to wipe everything and I read that thats kinda not possbile. But thanks for those steps, I'll do that when I have time!
Thanks

Timoooo said:
Yeah I noticed that like half a year ago, had no idea why that happened. At one point I felt like everytime I flashed a new rom a new 0 folder appeared.. How does that happen?
Click to expand...
Click to collapse
Basically when 4.2 came out, it brought along multi-user functionality. Custom recoveries at the time, when wiping and installing ended up creating the nesting problem. Recoveries then were updated, which doesn't create a bunch of /0 folders (one existing is correct). This was a super common problem about a year ago when 4.2 came to be. There were hundreds of threads about this problem, with more detailed info about what happens, why, and how to fix it. Wiping everything is one of the solutions, and since this isn't your only problem, this would probably be the recommended solution.
I was actually thinking about a clean start, googleing how to wipe everything and I read that thats kinda not possbile. But thanks for those steps, I'll do that when I have time!
Thanks
Click to expand...
Click to collapse
I am not sure where you read that a wiping everything isn't possible, but whoever said that is all sorts of wrong. There are multiple ways to wipe things.

Just did what you said and it looks like everything worked! Everything is deleted, I have almost 13 gigs of free space, rooted my phone again and I'll probably install aokp or paranoid in a couple days.
No 0 Folders anymore and I'm sure as hell hoping that my data consumption will be fine now. I'll keep you updated on that in a few weeks again, but thanks for the help!

looks good thanks bud

Link2SD & CM11: Optimal Strategies

I am super-curious if & how anyone here is using Link2SD successfully with CM11 (on the Epic 4G, specifically).
I've tried scouring these forums, and the Internet in general, to figure out the best way to get this to work...
But everything that I've tried, it all seems to be working great, only up until the first time that the phone reboots, then it all goes to hell.
I am wondering if there are any extra steps to follow, specifically for the Epic 4G, or any particular pitfalls known to avoid?
That's why I wanted to ask here, specifically to Epic 4G users...
If you are getting Link2SD to work well with CM11, then please chime in here, and can you explain how you got it all set up and working well?
(I feel like this is the one last thing that if I could conquer it, then I could really continue to get a lot of life out of this phone... as it stands, it seems too risky to put much faith in Link2SD, because if the phone happens to spontaneously reboot while I'm out running around, then I'm screwed because so many apps just disappear, and then it's a pain to re-download, re-install, and re-setup each of them...)
Thanks in advance for any help,
AS

I am using Link2SD on my Epic 4G with CM11 with some success. I just did a reboot, and as usual lost any icons that had links created in Link2SD, so I go to the app locker & re-add them to my home screen. This is typical of what happens on a reboot for me. One thing I did notice is that it takes a minute or so for the deleted app icons to show up in the app locker again, so if you are reinstalling them, it may be a matter of waiting for them to show back up. Also on occasion(not this time), Link2SD will prompt me about a problem with the links and then prompt me to reinitiate the partition or something to that affect. Once I do that and it reboots, the app icons are still gone, so I just re-add them. Anyway, I know its not a perfect solution, but with this device its better than running out of RAM. One last thing, needless to say, I only create links for enough apps to free up enough RAM to keep my Epic working properly.

I've finally got a system going that seems to work for me, and so I thought I'd share some things.
I'm on CM11 (as of today, cm-11-20140602-NIGHTLY-epicmtd.zip) and I'm using Link2SD.
HERE'S A "GOTCHA" THAT HAD ME PULLING MY HAIR OUT FOR AT LEAST A DAY OR TWO:
Link2SD was having problems mounting the 2nd partition - it would just say "Mount script cannot be created." or something like that (not a very helpful error message), no matter how many times I rebooted and tried again. What I *finally* figured out (somehow), was that this error was being caused by /system being completely full. When I went and deleted a few things from /system (such as goofy wallpapers or that 'Apollo' app that I never use), then Link2SD was able to successfully create the script, and then I'd reboot and could use the 2nd partition successfully.
It's still a little aggravating that any reboot of the phone will cause all of my "Linked" apps to disappear - I've played with this until I am blue in the face, and have resigned myself to accepting that this is just "how it is" (?) - but I'm now using Titanium Backup as my workaround.
STEPS I TAKE WHEN THE PHONE REBOOTS:
1) Go into Link2Sd and make sure the 2nd partition is usable, otherwise recreate mount scripts (deleting wallpapers/Apollo if necessary)
2) Under Link2SD's "More" menu, perform the following:
a) Clean up the 2nd partition
b) Clean up the dalvik-cache
c) Clear all app caches
3) Restore apps from Titanium Backup
a) starting with Facebook app (the biggest hog) and then immediately go and make Facebook a "Linked" app again
b) restore a few more apps (to internal/phone), then go and shuffle those over to "Linked" apps via Link2SD
c) (repeat step 'b' until all apps are restored and "Linked" via Link2SD
^ This is the only way I've been able to get this to work for me... but now I can put about as many apps on the phone as I'll ever possibly need, and I have to say everything is running pretty smoothly now - but if anyone can see a better way, or how to improve what I'm doing, then I'm all ears... please let me (us) know.
Thanks!

Apex launcher doesn't lose the icons. I can free about 66MB of system space by swapping the launcher, deleting CM wallpapers, live wallpaper and Google keyboard.
I verified link2SD plus was not working properly but free link2SD works as advertised. For me, just installing the plus version will break the working functions of the free version. The free version scripts, links and launcher icons survive reboots. The plus version continually lost mount and wouldn't properly clean up the second partition and was not copying the lib files and placing them in the second partition.
Edit: per the developer's request, after verifying free link2SD was setup and surviving reboots, I added plus link2SD and rebooted: OK so far. Next I linked a file with plus version; OK until reboot. The application was not found except in directories. Dalvik cache cleanup finds the dex link and file in second partition as unneeded files. Had to manually delete all the files and links for the broken application and reinstall it. Also had to uninstall plus link2SD to properly link again. Sent the results back to developer.
Sent from my SPH-D700 using Tapatalk
Edit: 6/20/2014; link2SD 3.4.8 fixed the reboot issue for the link2SD Plus version for me. Sent email to developer to thank him for the fix.
See post #8.

Update on my last entry:
I emailed the link2SD developer and got a reply asking me to check the plus version again. In my reply back I linked him to this thread.
Another tip to add for nightly flashers that use link2SD and modify the zip prior to flashing: pull the mount script, 11link2SD, found at /system/etc/init.d and move it same location on zip before flashing. If retaining data, ie: dirty flashing; the mount securely retains your apps after flashing new nightly. Just checked with free version of link2SD: works.
Sent from my SPH-D700 using Tapatalk

Arson Smith said:
I am super-curious if & how anyone here is using Link2SD successfully with CM11 (on the Epic 4G, specifically).
I've tried scouring these forums, and the Internet in general, to figure out the best way to get this to work...
But everything that I've tried, it all seems to be working great, only up until the first time that the phone reboots, then it all goes to hell.
I am wondering if there are any extra steps to follow, specifically for the Epic 4G, or any particular pitfalls known to avoid?
That's why I wanted to ask here, specifically to Epic 4G users...
If you are getting Link2SD to work well with CM11, then please chime in here, and can you explain how you got it all set up and working well?
(I feel like this is the one last thing that if I could conquer it, then I could really continue to get a lot of life out of this phone... as it stands, it seems too risky to put much faith in Link2SD, because if the phone happens to spontaneously reboot while I'm out running around, then I'm screwed because so many apps just disappear, and then it's a pain to re-download, re-install, and re-setup each of them...)
Thanks in advance for any help,
AS
Click to expand...
Click to collapse
I'm using link2SD for all minus 16gb internal android device. Here is what i do in epic 4g, currently on CM11 20140523, use 20131209 gapps. I just write the part involved link2sd :
1. Buy atleast 16gb microSD and class 10 is a must, make 2nd partition (usually about 4gb - 6gb) as ext2 - ext4 (depends on the OS).
2. Device rooted, install titanium backup & root explorer 3.1.3 (make sure the root explorer working). Uninstall system apk (one of the launcher, whisper push, terminal emulator (I prefer use better terminal emulator, install as user app), CM filemanager, etc - still more that can be uninstalled for more space in system.
3. install link2SD, pick ext2 - ext4 (depends), dont restart yet. go to setting, uncheck everything then restart.
4. After back to launcher, open root explorer, go to root/data/, check app & dalvik-cache folder, press copy. Go to sdext2 folder, delete lost&found folder (usually there), and paste. So the app & dalvik-cache folder is there now (you could copy data/data folder too if you really want maximum extra space in internal, but in epic 4g i didn't copy data folder because it's enough space).
5. At the sdext2 folder, long press app folder, select "link to this folder", go to root/data/, press "create link" - "yes". Then go to sdext2 folder again, long press dalvik-cache folder, select "link to this folder", go to root/data/, press "create link" - "yes". Do the same if you copy data/data folder to sdext2 folder.
6. Reboot. Done. Then installing others app or restore with titanium backup.
I hope this is useful. Some Screenshot attached.

Hello
Thanks for that solution.
I`m searching for this solution since 1-2 weeks.
I had the same Problem on xcover 2 Link2SD.
Now it`s clear i have installt Link2SD and works perfect for just 3-4 days then i upgrade to Link2SD plus and then it happend like the Threat above.
I`m wondering that Lin2SD works perfectly on CM11 and if you go to Link2SD plus for money and this don`t work.
Free works perfectly and paid work not.
I have go back and everything its fine.
I hope the autor will fix the problem then i go back to plus.
Thank Thanks Thanks works fine!
regards marle.m

Good news! It appears the link2SD version 3.4.8 released today has a bug fix to survive reboots for linked apps when linking with link2SD plus version.
So far, I've only linked one app with plus version enabled and it survived one reboot. Then Ⓘ linked the data folder and rebooted again which also survived the reboot.
Looks like plus version is fully functional; I'll update if it fails some time later.
Sent from my SPH-D700 using Tapatalk

Finally had a chance to sit down and mess with this...
Yeah! Success! Freeing up space in /system worked.
Next question...Will I have to remove the bloat prior to flashing from now on? ie no more CyanDelta easy flashing
Anyone have any Scripting-Fu to come up with an automated method of stripping out said bloat?
thx sno

Snoshrk said:
Finally had a chance to sit down and mess with this...
Yeah! Success! Freeing up space in /system worked.
Next question...Will I have to remove the bloat prior to flashing from now on? ie no more CyanDelta easy flashing
Anyone have any Scripting-Fu to come up with an automated method of stripping out said bloat?
thx sno
Click to expand...
Click to collapse
I was thinking the gapps could be modified at the updater-script to remove some system bloat. Then remove some bloat from that as well. Most remove their own bloat choices so maybe a diy tut would be more useful?
I agree, the script would make the nightly flashing easier.
Sent from my SPH-D700 using Tapatalk

Just realized that if using Link2SD Plus to multi link all folders of an app to sdext2 after a clean install is still broken, if using intended method. Apps linked this way are missing after reboot.
Working on a safer suggested method that focuses more on removing apps from Gapps but also removing some other system apps after flashing a nightly that requires no modification of the nightly zip on a computer. Have to focus on linking only a minimum amount of apps with free Link2SD considered less risky to move, like larger stand alone apps, not needed tools.
I've got a working script and method that works but the risks to be avoided need to be detailed along with the tut to script and tool your own modified Gapps that minimizes the flash to flashing the nightly as-is and then flashing a custom Gapps that includes preferred launcher and restore methods.
Removing CMWallpapers, Apollo music and Trebuchet launcher. Substituting blacked out Google play. Replacing removed apps with Apex beta test launcher for test group, blacked out Pandora (these will be installed at /data partition where they can be easily uninstalled or updated) I use my own borrowed wallpaper.
Along with the removed bloat from Gapps, this frees a bit more than 40 MB of system space.
Sent from my SPH-D700 using Tapatalk

UPDATE: the latest version of Link2SD (3.5.2) has "fixed the bug that causes linked apps disappear on reboot when internal data is linked".
So... if you've also ponied up the buck or two for Link2SD Plus (as I have), then this finally works again like you'd always hoped it would.
I just loaded a bazillion apps back on the phone, and have been able to reboot multiple times without losing them.
The only time I "lost" them for a moment was after flashing to the latest CM11 nightly, but then doing the "Recreate mount scripts" and reboot brought them right back, with no other shenanigans necessary.
(Just wanted to let people know, because this is such a relief to me now....)
HURRAY!

OK I'm trying this again. Reboots are fine as long as I don't select quick or soft reboots; I lose mount, linked apps not installed.
Now need to try the clean install of nightly.

Snoshrk said:
Finally had a chance to sit down and mess with this...
Yeah! Success! Freeing up space in /system worked.
Next question...Will I have to remove the bloat prior to flashing from now on? ie no more CyanDelta easy flashing
Anyone have any Scripting-Fu to come up with an automated method of stripping out said bloat?
thx sno
Click to expand...
Click to collapse
One possible solution:

more scripts to limit steps
Another possible solution (click link)