yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] MarcusMaximus04@gmail.com:
How did you find that it installed to internal memory? If the amount of space on the internal memory goes down, it could be due to the cache.
[G1 Android Development] MarcusMaximus04@gmail.com:
The newest script(put up yesterday afternoon) should solve such problems with protected apps.

That aside, to be fair, look through the posts and compare them with, say, those from my old tutorial or my app, or any of the other tutorials. There's been a grand total of about 2 reports of boot looping and that was when I very first put this up(it was due to me writing the script in windows which has funky newline characters) compared to pretty much every other post on those threads. The point with this one hasn't been that it'll be totally hassle free(though it seems to be moving in that direction) or that there wouldn't be bugs and hiccups along the way but, rather, that it wouldn't totally break people's phones.

For your other arguments: No, a wipe will not delete apps from the sd card, since in recovery mode the ext2 partition isn't mounted and my script hasn't been run.

Also, it will not delete symlinks from within the /data/data directory. It will only delete specific symlinks from the /data directory(including the sd card), namely: app, app-private or dalvik-cache. The reason for this is that having those symlinks is precisely what this method is getting rid of and, if someone mistakingly runs the original appstosd app or tries to set up an old method after doing this one, will cause a boot loop every time if they are on the sd card.

Hopefully this is enlightening, and addresses your concerns.

EDIT: Also to be fair, a huge proportion of these posts have been either answering the same questions over and over again(why did internal storage go back to being normal comes to mind) or walking someone through a series of steps to try to solve their problem, with replies back and forth.
[G1 Android Development] LucidREM:
so .. when you typed:

#ls -l /system/intmem/app

what was the output??
[G1 Android Development] AsaSpades:
Ok since my last post got overlooked obv mayb this 1 wont. I tried to do this and it didnt work so I wiped my phone, and reinstalled all my apps, they are on the internal memory because I only have around 24mb left. Im going to try again, so can I delete the system/sd folders and start with this tutorial from scratch? I had the previous apps to is this ok?
[G1 Android Development] sandshrimp:
What new script? are you referring to the new AppstoSD2 app on the market?
[G1 Android Development] jikei:
which way should the phone report it now? SD storage or internal? (I asked yesterday after you put up the new script)....

Seems to be working perfect for me. except I did notice when I go into Settings/Apps/Manage Apps the phone kind of ... freezes and freaks out (Loading screen sits there with the circle REALLY REALLY slow) and goes dim and moving the trackball or hitting the menu key doesn't bring it bright again. It goes dark if I don't touch it but if you look at the screen you can just barely make out the image, the Android screen faintly comes up dim, then comes back bright and the phone comes back, but it really really does not want me to go in there. Might be related to my previous question (SD space or internal space?)

Had to reinstall like two protected apps (one went online, the other was just completely borked), but the other 8 or so are working fine.
[G1 Android Development] MarcusMaximus04@gmail.com:
First sorry about overlooking your post. I had been working all night on the new appstosd2 sdcard partitioner and it got buried.

You certainly can. In your case that sounds like it's probably the best option since you've already reinstalled all the apps.
[G1 Android Development] MarcusMaximus04@gmail.com:
No, I replaced the script on the first post here yesterday at about 3 or 4pm PT. It's in the a2sd.zip
[G1 Android Development] MarcusMaximus04@gmail.com:
Let's see... at this point it should be showing the ext2 partition again. Sorry for all the back and forth, I changed it one way to fix the wallpaper issue but that created the issue with the protected apps so I had to backtrack. Everything should be working now.
[G1 Android Development] ctecamp:
Available Storage

I asked this question before, but I don't think it was ever answered.

Will the available memory pointing to the sd card give any false sense of wealth, is it possible for the internal memory to become loaded with data and bring things to a halt?

Point being I now can't see how the internal memory is being used up by data cache.

ctecamp@gmail.com

Rooted Black G1 JF1.5

a2sd2 Openhome
[G1 Android Development] overground:
No, the a2sd.zip at the bottom of the first post of this thread. Also, if you really are using Dude's 0.94 as your sig says, this method shouldn't work at all. If you upgrade to Dude's 1.1a, the files in the previously mentioned a2sd.zip are already included in this build.

@ Marcus: I know you're busy doing other things, but much of this confusion may be alleviated if you consider the suggestions I PM'd you yesterday. I know it's a pain, but hopefully it'll pay off in the long run. :)
[G1 Android Development] MarcusMaximus04@gmail.com:
It certainly could be a problem. I know The Dude is working on changing the phone storage menu for his ROMs so that it will show both. In the mean time you can use "busybox df -h" and see what it shows for /system/intmem, which is the internal memory. I'll also see if I can whip up a display in appstosd2 that'll show how much memory is available both on the ext2 partition and on the internal memory(should be easy, already did something similar for the partitioner).
[G1 Android Development] MarcusMaximus04@gmail.com:
Right, will do so now. Got a little caught up in the partitioner in appstosd2 so forgot all about this post for a little bit(just kidding, I could never forget about you guys)
[G1 Android Development] borodin1:
@ Marcuss

Agh.... you've already answered, just as I was going to delete that post. Please don't take offense and don't get discouraged...The post wasn't directed at you or anyone else, I just HAD to let some steam out. Please accept my sincere appology for doing it in the wrong place. Now, back to the topic

I finally got to re-doing the whole thing this morning. I re-read Dude's instructions (since I'm staying on his build), re-formated my SD, flashed clean copy of Dude's 1.1a and ran AppsToSd 2 from Market (yes, I purchased) for both apps and dalvik-cache. I was going to hit you up on Gtalk but I figured 5am would fall into crazy hours category so I did not.

Here's where I am now:

30+ apps

55 Mb available

No problems changing wallpaper

Protected apps crash everytime.

I assume (and I know what that does) that Dude did not update your script yet, however him and you work together so 1.2 will include your latest script and I will be able to flash it without wipe and everything will work as intended.

Awesome job Marcus and thank you for following up with everybody, I get less support from paid developers most of the time.
[G1 Android Development] AsaSpades:
Thanks, I got it, and it says 644mb free, is th@ what its supposed 2 b?
[G1 Android Development] MarcusMaximus04@gmail.com:
No worries, it was a good chance for me to address those concerns which are probably help by a large number of people reading this, and will lead to a better understanding for everyone. It's true that The Dude does not have my most updated script but 1.2 probably will. Since he's on vacation right now, I've deemed that I shouldn't bug him until after he gets back.

If you want, you could replace /system/bin/a2sd.sh in his ROM with the current one here. I did that just 20 minutes ago :D, and now have working wallpaper and working paid apps.

Note that this will delete /system/sd/data if you've put it there(had to do it to get wallpaper working) and replace it with a symlink(of all things!) to the internal memory. Not to worry though, this has none of the stability problems of the original appstosd since it's from the sd card to the internal memory instead of the other way around.

Also, if you want to move the data caches for any specific app, you can move just that app's cache to the sd card and then set up a symlink(arg... this is why I would never do that) from /system/intmem/data/(cache to move) to /system/sd/(new cache location).
[G1 Android Development] MarcusMaximus04@gmail.com:
Yep, it now shows the ext2 space rather than the internal memory. If you want to view internal memory for now you can go to terminal emulator and do this:

su

busybox df -h

and see what it says next to /system/intmem. I will also try to build this into appstosd2 in the near future.
[G1 Android Development] AsaSpades:
Thanks, btw great job with this
[G1 Android Development] overground:
If one were to put specific caches on sd, is having those caches on the ext2 partition better than putting them on the fat32 part? Unless I'm mistaken, you can put them on either using sym-links. Or does it not make much of a difference?
[G1 Android Development] sandshrimp:
I downloaded and installed the new files as shown here using Terminal Emulator

su

mount -o remount,rw /dev/block/mtdblock3 /system

cp /sdcard/init.rc /data/

cp /sdcard/a2sd.sh /data/

Then I rebooted and ran appstoSD2.

Still not working. Am I doing something wrong
[G1 Android Development] overground:
Which ROM are you running?
[G1 Android Development] MarcusMaximus04@gmail.com:
I don't believe FAT32 will work since it doesn't support file permissions. Even if it does, I'm not sure you'd want them there since that means any rogue app could look through your browsing data, possibly finding credit card numbers, etc depending what you use the browser for.
[G1 Android Development] sandshrimp:
Dude 1.1a loaded.
[G1 Android Development] overground:
Thanks for the answer. I remember now that before I had apps2sd, I used symlinks to move my caches to fat (browser, market, street view, etc.), but what you said about privacy issues is an immense argument not to do that again. I'm learning.
[G1 Android Development] MarcusMaximus04@gmail.com:
Yep, it's the same reason I stopped looking into using an ext2 image file on the FAT32 partition rather than having a second partition. It sounded perfect until I thought of that, and I didn't want to be responsible for introducing that major of a security hole.
[G1 Android Development] MarcusMaximus04@gmail.com:
That's why, the Dude's ROM reads the a2sd.sh file from /system/bin. So if you want to replace it in his you'll have to do:

su

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

rm /system/bin/a2sd.sh

cp /sdcard/a2sd.sh /system/bin/

reboot

EDIT: The above is exactly what I did about 2 hours ago to get it working.

ANOTHER EDIT: The servers are back to a non-ridiculously slow speed, yay!
[G1 Android Development] overground:
Wait for confirmation from Marcus before running these, I'm no expert, but this is what worked for me.

I'm not sure which specific problem you're having, but I believe on Dude's rom the file a2sd.sh should go to /system/bin/, instead of /data/ so your command would be:

cp /sdcard/a2sd.sh /system/bin/

In addition I would run:

cd /data/

rm a2sd.sh

I had to do this because Market started crashing by leaving it there.

Reboot phone
[G1 Android Development] MarcusMaximus04@gmail.com:
No worries, I preemptively confirmed :cool:
[G1 Android Development] overground:
Well, dammit, Marcus. My phone is darn near perfect now, which saddens me a little. What the hell am I gonna do now? Play with all these apps I've never opened? lol. Oh well, I guess it's time to screw something up so I can fix it.

Amidst all the problems, this post is just to say "thank you" for helping make this phone what it should have been out of the box. Peace, love in Bobby Sherman!
[G1 Android Development] sandshrimp:
It worked. This really should be posted in the first post and should be released via Dude.

Thanks
[G1 Android Development] MarcusMaximus04@gmail.com:
Will add it in right now. Also, The Dude's on vacation this week so no updates from him.

EDIT: Oh, and I'm glad it worked too :D
[G1 Android Development] serialtoon:
Hello MarcusMaximus! I really liked this method for apps2sd you have created. I never cared for the whole apps 2 sd thing but now that i purchased a 4gb Class 6 card i went ahead and followed your steps. So far everything is working the way it should. Although i have quite a few questions for you. Ready? :-D

1. What would happen if i reformat my phone and install another Android build? Would i lose everything and have to run the commands again? Or do they "stick" across all builds?

2. How would i go about "undo-ing" it?

3. What is private-app and dalvik? I only moved over the apps portion. I have had zero problems. But what advantage would i have in moving over the those to directories?

4. Thanks :-p
[G1 Android Development] MarcusMaximus04@gmail.com:
1: That depends on what build you move to. JF builds will require repeating this process if you do a wipe. The Dude's ROMs have this process built in so there's not even a need to follow the tutorial the first time.

2: To undo it in a JF ROM, just do this in terminal emulator:

su
rm /data/a2sd.sh
rm /data/init.rc
reboot

or if you just want to get rid of having apps on the sd card, just reformat your sd card to having 1 FAT32 partition and it'll be back to being just like it would be without appstosd.

3: app-private stores the copy protected apps and dalvik-cache is where the OS stores information about all your apps. Both of these seem pretty stable to move and dalvik-cache usually is about 30MB or so. app-private's size depends how many copy protected apps you have installed.

4: You're welcome. :)
[G1 Android Development] serialtoon:
Sweet, thanks Maximus! Looks like moving the app private isnt really needed for me cause i have like 2 apps i paid for and i think that over a gig is enough room for apps so moving dalvik is something i need either. But you have been an enormous help. Thanks so much for everything you do around here.
[G1 Android Development] persiansown:
I had data, app-private, app, and dalvik-cache on my SD card. I updated to this newer version of the script and lost all my settings. Is there anyway to get them back?
[G1 Android Development] MarcusMaximus04@gmail.com:
No on the settings, as noted in the first post if you have "data" on your ext2 partition, it deletes it. The reason for this is that having it there messes up the wallpaper changer and it has to be replaced with a symlink. Also, it's terribly unstable and can cause major problems if left there long enough(boot looping, etc).
[G1 Android Development] c_low29:
just to address the issue with the script reading the ext2 partition space instead of internal there is a free widget on the market that reads internal memory
[G1 Android Development] persiansown:
Oh ok. Thats fine, not a big issue. If you could make that more explicit in the first post of the thread, that would be great for other people. I wish I hadn't lost my place in blockbreaker :o oh well. Thanks for all your great work!
[G1 Android Development] MarcusMaximus04@gmail.com:
Does it work with this? It seems like it'd have the same problem as the sd & internal storage menu. Haven't tried it though.

EDIT: just tried it and indeed it does have the same problem. No worries, though, I'm gonna make appstosd2 display the correct internal memory and ext2 memory available. I might even make it have a widget associated with it that shows both... we'll see.
[G1 Android Development] grivad:
Hmm.. so I had this working perfect before the wallpaper fix, except I had data and dalvik-cache on the SD.. today I went through a giant hassle, including wiping my phone, trying to move data and dalvik-cache back to internal memory.

I did the wipe, fixed my SD/data dir using fsck, removed it, applied the new scripts from the first post, restarted.. all of my old apps appear in the apps tab, however, when I go to the market they appear as not installed (Free/Purchased instead of Installed). Weird. I was showing that intmem was at about 34.5 megs free (busybox df -h).

I tried restarting, and un/re-installing some, and noticed that both intmem and unionfs were dropping by some meggage.. unionfs dropping as expected but intmem still dwindling. I attributed this to dalvik-cache, which was now on my internal memory, getting some stuff about the newly installed apps. I used AppstoSD (from the market, paid) to move dalvik-cache to the SD, restart, then check my mem again and intmem has dropped to about 9-something free. Huh??

I also check and see that /system/dalvik-cache still has stuff in it, but /system/sd/dalvik-cache has stuff in it too.. can I erase the /system/dalvik-cache contents now? What happened to the 20-someodd megs of intmem that disappeared after moving the dalvik-cache using AppstoSD?
[G1 Android Development] MarcusMaximus04@gmail.com:
Hmm odd behavior. At any rate, yes, deleting the files in /system/intmem/dalvik-cache should be ok at this point. Did you keep the checkbox checked in appstosd2?
[G1 Android Development] grivad:
Thanks for the quick response! Oops. ; ) Disregard the funny memory stuff...

But in the Market the apps all still say Free/Purchased instead of Installed... is that going to be an issue for updates..?
[G1 Android Development] MarcusMaximus04@gmail.com:
Ya, it won't show up updates(atrackdog will though, since it searches based on actual apps rather than just what's on your market cache), so to track them you should probably go through your app list and press install for all of em(or, as mentioned use atrackdog).
[G1 Android Development] JAWheat411:
Ok quick question. So I am running AppstoSd 1.1 on my G1. I have dudes latest build 1.1a. I was updating my programs and seen a newest AppstoSD ...1.5. I was thinking I might run into problems if I try to run the newest AppstoSD. From the first post I see this

So what do I need to do? Do I have to move apps back to phone? I don't think I have the room. I see some commands...but I have had my share of boot loops with Dudes, I don't want it to happen again lol.
[G1 Android Development] MarcusMaximus04@gmail.com:
Heh, don't worry so much! The new appstosd2 v1.5 just adds a partitioner that runs if there's no ext2 partition. (I just finished 1.6 that makes the partitioner better and adds a display of free internal and external space) And for updating the script, just run those commands, there's no need to move apps back to internal memory.
[G1 Android Development] mrmonto:
Copy apps from one sd to larger sd card

Does anyone know how to copy the apps from one sd card (ext2 partiton) to another sd card (ext2 partion) with windows xp? I currently have a 2G sd and want to move my apps to it, but I know I'm going to need to get a larger sd card soon. Should I just wait till I get the larger card or is there an easy way to move the apps to another sd with windows xp? Any info you could pass along would be great. Thanks!:confused:
[G1 Android Development] LucidREM:
yep .. use linux
[G1 Android Development] malaeus:
aww man, this new update to the code for JF 1.5 just KILLED my phone...

it severed the connection between my card and the phone. all my apps are stranded, and all i moved was apps, no private apps, no cache, no other data. just apps, and not even all of my apps moved. yet it deleted the ones i had on internal memory.

what happened!?

will slax work?
[G1 Android Development] malaeus:
sorry, double post.
[G1 Android Development] mrmonto:
Thanks Captain Obvious! Anybody else have any ideas regarding windows xp?
[G1 Android Development] malaeus:
thats why i was asking about slax. you can just put that on a USB drive and run it on your PC. im sure there is a way to do that with other distributions of linux, but slax just seems to be easier to put together for a non-programmer.
[G1 Android Development] MarcusMaximus04@gmail.com:
...? Well that shouldn't happen. What does "busybox df -h" show when typed in the terminal? And where did you put the script?
[G1 Android Development] andonnguyen:
While updating from script to script, I found that the connection between apps and their link to the phone were severed, and many of the apps would "break" and require a reinstallation, or would lead to a force close after a short period of time. Since the apps already reside in the ext2 partition, this shouldnt happen, but it seems to happen a majority of the time.
[G1 Android Development] swaney:
is my phone supposed to reboot everytime i move apps to sd?
[G1 Android Development] BSDADON:
Finally got around to putting the new a2sd.sh on my phone. Fixed and working fine (so far):D
[G1 Android Development] andonnguyen:
Are you using the apps2sd2 application?
[G1 Android Development] BSDADON:
If you are using apps2sd 2 then yes it is, I don't think the first version did that
[G1 Android Development] swaney:
yes.. i did.. but idk if it wrked.. ill keep tryin
[G1 Android Development] BSDADON:
the newest version of the app shows internal space and the ext2 space on it. check that and see what it says

or try this in terminal emulator and look at system/sd and system/intmem

su
busybox df -h
[G1 Android Development] swaney:
everything keeps force closing :(
[G1 Android Development] lbcoder:
Had a little try with ext2 as the first partition... it barfed, so that's out until I or someone else fixes and rebuilds the part that makes it dependent on vfat.

Little question for ya. It says in your instructions the following:

What is the reason for remounting /system? Only reason I can think of for remounting /system is if you are intending to write to there, but you're writing to /data only....
[G1 Android Development] malaeus:
script was placed at the root of /sdcard (the fat32)

and busybox thing says :

Filesystem Mounted on

tmpfs /dev

tmpfs /sqlite_stmt_journals

/dev/block/mtdblock3 /system

/dev/block/loop0 /system/modules

/dev/block/loop1 /system/xbin

/dev/block/mtdblock5 /data

/dev/block/mtdblock4 /cache

/dev/block/mtdblock2 /system/sd

/dev/block//void/179:1

/sdcard

/dev/block/mtdblock5 /system/intmem

unionfs /data

#

do you need the space used and free etc as well?
[G1 Android Development] MarcusMaximus04@gmail.com:
It says mtdblock2 next to /system/sd??? Wtf.. You restarted and the problem's still there? Also you did the "cp /sdcard/a2sd.sh /data/" right? Finally, which ROM is this on?

Edit: not saying wtf at you, just at the problem in general. I've never seen something as random as mtdblock2 get mounted at /system/sd, and my script doesn't even touch the mounting of /system/sd.
[G1 Android Development] swaney:
i got it too wrk
[G1 Android Development] malaeus:
i have restarted many times (not too quick in succession though, i let it come all the way up before i restart again)

the problem seemed to fix itself somewhat when i ran the script again, double and triple checking for typos, but it still gives me cascading force closing unless i manage to get it to boot to android home, then while in the middle of force close window popups, i press the home button and launch ahome immediately after launching android default home.

i did the cp /sdcard/a2sd.sh /data/ just fine. no errors.

and i have only followed this tutorial for apps to SD, i have not tried any other method (i.e. symlink) only the unionfs method in this thread.

i am running JF 1.50 (no other mod on top of it [i.e.] lucidrems scripts) however i AM using a ported theme from RC33, the glosssuite theme by MOONSPOON, ported version, his official 1.5 release is still in the works.

see this here

i have NOT sent private-apps NOR dalvik-cache to my SD card, ONLY standard apps.

it seems that i have some serious problems with electronics, i treat them no differently than anyone else would, however i always end up with the strangest errors. even things that aren't supposed to be able to happen. it is rather odd, and very aggravating.

thank you very much for all your help.