Enabling APPS2SD *after* installing apps to N1's own flash - Nexus One Q&A, Help & Troubleshooting

Assuming one installs some apps to N1's own, built-in flash and then decides to enable APPS2SD - will it work ?
Will it copy existing, installed apps to EXT* part on SD _or_ will run support both co-existing peacefully , where some launch from SD and some from N1's own flash ?

all my apps were present after enabling, but many would FC often. Painfully batch-reinstalled them all with titanium backup

Related

move apps to sd (please help)

ive got a 512mb ext4 partition running on cm5.0.5.2 and had a2sd enabled
is there any way i could transfer all my apps from the phone mem to sd without reinstalling them ?
Yes. I have app manager pro installed, free will work also. I like the pro cause it show the apps install in the menu. I back up all the unprotected app to sd. Then I went menu, install from there all the app I have install I just clicked install. As they install they move to the sd partition. The protected apps I just wait for a market update or manually do those.
thx buddy !!

Froyo with Apps2SD on Ext?

Well I tried Froyo and I've gone back to CM 5.0.6
Unfortunately there were just too many apps that are not SD enabled as yet. (I have 450 installed).
However, I don't think I particularly like the new Apps2SD method anyway as it stops certain apps and widgets working, I think the 'old - Ext' way is much user friendly.
Therefore - Is there any possibility that Apps2SD for Froyo could implement the old Ext2/3/4 way?

[Q] Lost apps on SD

After installing CM6 RC3 I have lost all my apps on the SD card, they did come back for a short time after a reboot but then disappeared again after another reboot. I cannot even uninstall them or reload them from the market as they just hang when I try to uninstall or re-install from the market.
When I look at application info, the apps on the SD just show "Computing" and nothing ever shows up.
Also, I am unable to mount the SD over USB.
I have gone back to stock ROM but I still have the issue.
I was using apps2SD but I made sure not to move any widgets or running apps.
I've tried booting into recovery to wipe data and cache but of course my recovery is broken.
If I missed this in the forums please give me a search that will give me results that are not too numerous to parse.
Thanks for any help.
There is no apps2SD support in CM6 or the stock rom, that's why you can't see them.
CM6 only support the FroYo apps on SD method right now, and they are working on a newer better apps2sd for future versions.
If you flash back to CM5, you might be able to see them, but I am not familiar with the old apps2SD method.
Then why did my apps show up in CM6? They were there and functioning fine, I think I must have messed with a setting somewhere.
FYI, I was able to restore my apps by deleting .android_secure from the SD card and then re-install Ti Backup and restore my apps.
Can someone explain how the app location setting in CM6 affects apps? I am thinking when I enabled this it screwed things up.
The .android_secure directory on the SD card is the 2.2 official apps to SD. So you probably were using that all along and something screwed up. That's why you could use them for a bit.

[Q] [Request] Need a way to boot 2nd partition (SDext) during boot time

Hi there,
So my N1 is rooted and has SuperOSR rom installed. The native app2sd that comes with the rom failed to work, so I disabled it and went back to the method I was using on CM7, Link2sd. I need a method to move apps/cache/lib files to sd-ext, as the tiny internal storage on the N1 is insufficient to hold even a 10th of the apps (and their data) that I have installed. And Link2sd has, at least in the past, been the perfect option to do so.
At first, all seemed well after installing and setting up Link2sd. Mount scripts were created with no problems, apps/cache/lib files all moved over to sd-ext without a hitch. Everything was going really well. Until I rebooted. Then, all hell broke loose.
The problem is this - for some reason, the second partition (sd-ext) is not being mounted during boot time. I'm not sure why, as this is exactly what the Link2sd mount scripts are supposed to accomplish. A Link2sd "mount warning" notice confirmed this problem, saying that "since 2nd partition was not mounted during boot time, linked apps will be invisible to the system until quick reboot". Indeed, every app that I had linked was not visible to the system, and most widgets on my homescreen showed only the message "problem displaying widget".
Luckily, a way to temporarily fix this is by simply quick-rebooting the rom. This will get the linked apps to show up again. But the problem is, widgets are still dead, input method gets reset (goes back from Swiftkey to native Android keyboard), and SMS gets reset back to the standard android SMS app. Of course, all of this can be changed back, but it takes time and effort to load each individual widget and restore each individual input/sms setting. It's really not practical every time you have to reboot your phone that you have to:
1. Quick-reboot the rom
2. Change input method back to Swiftkey
3. Manually restore every widget on your home screens
4. Change sms app back to Go sms.
So, my question is, how do I avoid having to do all this? I've already tried the "re-create mount scripts" option on Link2sd, but it doesn't matter. Still have the same errors upon rebooting phone every time. I'm pretty sure this means that the Link2sd mount scripts are either not being created correctly, or are being deleted every time the phone reboots. How do I fix this? Trying to get in contact with the developer of the app (bakpinar) has proven unsuccessful.
Does anyone know of any other scripts that I can flash/install that will successfully and consistently mount the 2nd partition (sd-ext) during boot time? I'm fairly certain that this is all I need, as everything else with Link2sd has been working correctly. Thanks in advance for any advice!
Ok, so since I haven't gotten any responses on this, I'm going to attempt two methods that i THINK might remedy this issue. The first one is this:
Method 1:
1. Full wipe and reinstall of SuperOSR rom
2. Format sd-ext to ext3 filesystem (found out that rom's native app2sd program wouldn't work due to my sd-ext partition being FAT32)
3. Enable rom's native apps2sd option upon booting.
4. Reboot
5. Install Link2sd from market, enable dex/lib file linking ONLY (native apps2sd program only moves app files, not dex or lib). Going to be interesting to see what link2sd says about the mounting scripts...
6. Reboot, collect results.
The 2nd method I'm going to try is this.
1. Full wipe and reinstall of SuperOSR rom.
2. Flash DTAPPS
3. Boot into ROM
4. Download and install test applications
5. Collect results
I'm not sure if either of these methods will work, however I know the 2nd method worked for CM. I will update a bit later as to which method (if any) fixed the issue. Sorry for the double post.
I commented to the ROM cook nelo360 a while back that there are some strange sd-ext mounting issues. If you look at the dmesg as it boots, it does post some strange error messages. Essentially, ext3 mounts as ext2, and ext4 mounts as ext3. Despite it not mounting as the proper format type, it still works.
Since the ROM is pulled off of AOSP, as CM is too, sort of, much of the same apps2sd apps probably work decently well.
Definitely need an ext3 or ext4 partition. As I'm understanding your post, that did not happen initially, and is crucial to many apps2ext to work, including the built-in one.
Really? Ext4 as 3 and ext3 as 2? Well that would explain why Link2sd was having issues. Hmm.
What I ended up doing was fully wiping the phone, flashing the rom, and then immediately afterwards flashing DTAPPS. Using the GUI interface found on the market, I moved apps to sd-ext and cache to sd-ext as well. The result has been mixed. While there was noticeably more space initially to install apps (something like 190mb internal), that space has declined at almost as fast a rate as when I had no apps2ext of any sort installed at all. This makes me think that while DTAPPS successfully moved some of the initially installed apps over to the sd-ext, it hasn't been moving any new ones i've installed or their cache files. I tried re-moving apps/cache with the gui interface and by using the old-fashioned terminal emulator method, but had no success. Still looking at about 100mb free space on internal. Considering that I only have about 1/4 of the apps installed that I usually have installed on my phone at any given time (I use A LOT of apps), it's become apparent that soon I am going to run out of space again.
As I can't find any method to fix this, I'm afraid I'm going to have to call it quits with this ROM and try something else. Which is a real shame, because stability-wise this ROM beats Cyanogenmod and other ROMS I've tried hands down, while not sacrificing many features. I guess for a user who doesn't use a lot of apps or need a lot of space for them, this ROM would be ideal. Unfortunately, I'm not that type of user.
One problem I've found is that with any automatic apps2sd/ext system is the control of what is actually on the SD vs. internal memory is hard to work out.
With the built in apps2sd, which you seem to have trouble with, not every app was transferred to ext. I found that with the built in system, my internal memory kept dropping until it hit 25 mb or so. However, it never really dropped below that. Everything I kept installing probably went to the ext partition. I installed a lot of apps, and it wasn't an issue. (But you're right, it may not be as many as you want).
I didn't have a great way to check this though. Root explorer showed both the data/apps/ folder and the sdcard/ext folder linked together, so it just listed everything together. I'd have loved a way to actually manually transfer whatever apps were on internal memory to ext, but never found an easy way to do so, or even to confirm what was in which directory.
So even though it looks like the internal memory is steadily and quickly dropping, if you continue to install, and have the two directories appropriately linked (sorry, I don't know what the difference between all the different kinds of scripting apps2sd are), I don't think you'll run out of space as quickly as you think you will.

Who are your usual suspects? apps that only FC after boot ICS - why?

Ok,
Thought I would start this thread. I have a few typical suspects that force close straight after boot and I suspect that it is a storage space error with CM. I am running CacheMate but this is only good for after the system has settled in and by this stage the apps that I am about to list have all settled down again.
- Titanium backup
- Android Market
- Ice Cream Sandwich Clock (its my favorite)
- Genie News Weather widget (used a lot)
- Messaging (only sometimes)
- Android Media Process....still, even after the so called "fixes for ICS.
I am begining to learn to live with it just for the shear benefits of ICS over Gingerbread.
I will be attempting a full pull of my SD card, wipe/format and repartition and installation of apps to SD with links2SD which seems to be much better than apps2SD that requires reinstallation of the app and then re -moving of the app to SD before the links in system will work again. Everytime I flash a new update to ROM any apps on SD that were moved no longer work...they ARE still there because when I go to re-install them after clicking on the app icon (a link basically) it pops up a notification "App not installed"...however when I go to "re-install the app it says asks if I would like to replace the application ? Grrr quite ****ty when you've done a full restore, can't get apps working and your re-installing old apks that you knew you had the latest installed from Market prior to flashing the ROM.
I have been doing a Nandroid backup of my whole system when ALL apps are restored but before moving the apps to SD. That way I can just restore data and then move to SD and I don't have to bugger around with re-installing a million and one apps THEN move to SD taking twice the time and usually killing my battery in the process.
The only issue with that is then the problem of user data being a snapshot, so if the last time I did a nandroid was 10 days ago and I want all the SMS (MMS is the key part here) then the snapshot (regardless of apps) is not good enough? Apps like SMS backup and restore don't offer restoring of MMS so thats crap too.
Anyways...what are other users experiencing and what are your ideas for possible fixes? I have shared mine
PS: Am about to try MyBackup Root

Categories

Resources