Hi, I used to own a G1 but have got a hero (and I am proud). I always used A2SD with G1 because of the shocking storage, however I have been getting away with the amount on this for sometime now, Until recently, though, when apps have been getting bigger (20+mb for raging thunder).
Is the Hero the same as the G1, or am I able to remove the memory card that has A2SD (while the phone is switched off, i don't mind), put a different memory card in, and view images from that memory card (i put my digital camera card into phone often to send images) obviously with none of my apps installed, and then switch the phone off, put the original memory card back in, and carry on using apps like normal?
PS this is on VillainRom 4
Thanks
Bump..Anyone?
Can anyone help withthis? A simple Yes/No would do
Thanks
Considering how Apps2SD works (basic symlinks), as long as you have an ext partition with the appropriate folders on both cards (at the same place, number-wise), you should be fine.
I would imagine the boot process probes /data/app and /data/app-private at some point - you just need to make sure those exist (even if they're empty).
If you've moved dalvik-cache as well, you will experience slowdowns when you switch cards.
tucka20 said:
Can anyone help withthis? A simple Yes/No would do
Thanks
Click to expand...
Click to collapse
#
Why don't you just try it? Seems a lot simpler way of finding out to me!
Regards,
Dave
Here's a related issue.
Obviously with the OS relying on the ext partition, you shouldn't remove the sd card while the phone is on & certainly not while it's mounted (unless you want filing system corruption), but in my naivety I thought it would be ok to power down, remove the card & power back up. So similar to the situation the OP is asking about, only with no card, rather than a new card, present on the reboot.
Clearly your apps on the card are not going to work as they're gone & you might get some complaints as /data/app now links to a non existent directory, but I assumed:
1) Most things would work.
2) More importantly, I assumed if I then powered down, replaced the card & rebooted, I'd be back to where I started with fully working apps.
1) Turns out to be true.
2) Doesn't. After replacing the card I found most (though not all) apps resident on the card would force close at some point, often sooner than later. I ended up having to reinstall them.
Can anyone explain why/how this happens? I can only guess that when the phone was run without the card present, it changed the missing apps user data or dalvik cache in a way that broke them once they are brought back. Trouble is, I can't see what mechanism would result in such behaviour.
have you tried wiping the dalvik-cache before booting up after reinserting the card?
kendong2 said:
have you tried wiping the dalvik-cache before booting up after reinserting the card?
Click to expand...
Click to collapse
If you mean me, no. This was shortly after i got my phone & I was less comfortable experimenting. Plus at the time I didn't have a nandroid backup & reinstalling twenty odd apps put me off
I'll give it a try shortly though. First as you suggest, & if that isn't enough, I'll try wiping the cache when the card is first removed too.
[Edit:] Nope, wiping Dalvik cache doesn't help at all. It seems if you attempt to run an Android install which utilises apps2sd without the sdcard present, something gets changed in the existing partitions on internal flash (other than the Dalvik cache) such that when the system is subsequently booted with the card present, app installs will have been corrupted leading to force closures & the need to remove/reinstall those apps.
Seems a shame. I'd have preferred an atomic means of relocating apps to sd, such that removal of the card means the system behaves as if the app had never been installed, with normal behaviour once the card is replaced. Ah well.
At least I used the chance to revert my ext4 partition to ext3 to avoid having to use tune2fs everytime I want to run a nandroid backup.
BTW For the record I should make clear this was all tested on a gsm Hero running MCR 3.2 with Amon Ra's RA-hero-v1.6.2 recovery.
Ha! Painful memories. Found this out the hard way as well. Wish I'd read more about how A2SD works (symlinks). In fact I wanted to swap while phone was on.
cauli said:
[Edit:] Nope, wiping Dalvik cache doesn't help at all. It seems if you attempt to run an Android install which utilises apps2sd without the sdcard present, something gets changed in the existing partitions on internal flash (other than the Dalvik cache) such that when the system is subsequently booted with the card present, app installs will have been corrupted leading to force closures & the need to remove/reinstall those apps.
Click to expand...
Click to collapse
I tried wiping Dalvik cache as well as ext repair. Nothing helped.
cauli said:
Seems a shame. I'd have preferred an atomic means of relocating apps to sd, such that removal of the card means the system behaves as if the app had never been installed, with normal behaviour once the card is replaced. Ah well.
Click to expand...
Click to collapse
Agreed, serious "flaw" in the A2SD way of things.
cauli said:
At least I used the chance to revert my ext4 partition to ext3 to avoid having to use tune2fs everytime I want to run a nandroid backup.
Click to expand...
Click to collapse
I used to employ ext4 for the /sd partition, then I read ext3/4 wear out your SD memory much quicker, because they are journaling filesystems (see http://en.wikipedia.org/wiki/Ext2), so I used the opportunity to repartition and stick with ext2.
cauli said:
BTW For the record I should make clear this was all tested on a gsm Hero running MCR 3.2 with Amon Ra's RA-hero-v1.6.2 recovery.
Click to expand...
Click to collapse
When I had this happen, I too was on MCR 3.2, with Amon RA 1.6.2 or possibly 1.5.2 or 1.5.3.1.
Related
Hi,
Recently rooted my hero after losing impatience waiting 6 months for htc to get their finger out.
Used cronosdroid and now using villianrom 10.2 final but will no doubt try out modaco in some point too.
Anyway, I would like to know if it is possible to save and run my apps from the sdcard?
I hear this will be possible using 2.2 but have heard that something called a2sd allows this functionality also?
If so, could anyone point me in the right direction to get a total noobs guide to installing and using a2sd and how I would then go about deleting the apps from the phone's internal memory and just running them from the sd card?
Many thanks for any help and advice you are able to share,
Cheers.
So you have already installed Amon Ra 1.6.2 yeah?
Check out BTDAG's guide in my signature,... The apps2sd bit is about half way down the 1st post, in grey writing.
I downloaded something called quick system info from the market and it says that a2sd is there giving me 457mb total and 423mb free.
I went through that long drawn out procedure (as a result of being on t-mobile uk) and used amon ra and created a gold card etc.
My Problem is, I dont know how to "use" this a2sd functionality.
I want to basically download from the market and save to the sdcard and run the apps from the sdcard and am unsure how to do this?
It doesn't do it automatically as I get to the usual memory low message after downloading 50-100 apps, so presumably the apps are still saving to the phones internal memory.
Basically, I want to know how to save and run from the sdcard and delete from the phones memory if thats possible as I think is the whole point of a2sd?
dazzer1975 said:
I downloaded something called quick system info from the market and it says that a2sd is there giving me 457mb total and 423mb free.
I went through that long drawn out procedure (as a result of being on t-mobile uk) and used amon ra and created a gold card etc.
My Problem is, I dont know how to "use" this a2sd functionality.
I want to basically download from the market and save to the sdcard and run the apps from the sdcard and am unsure how to do this?
It doesn't do it automatically as I get to the usual memory low message after downloading 50-100 apps, so presumably the apps are still saving to the phones internal memory.
Basically, I want to know how to save and run from the sdcard and delete from the phones memory if thats possible as I think is the whole point of a2sd?
Click to expand...
Click to collapse
If you followed my guide correctly it will be working. You can check that with the other script in my guide. If you're still running out of memory it is because the dalvik is still stored on the SD card.
Ok,.. So you need to be using a custom ROM with apps2sd enabled. Then once that is on your phone, you just need to partition the SD (like it says in the guide)... thats it!
btdag said:
If you followed my guide correctly it will be working. You can check that with the other script in my guide. If you're still running out of memory it is because the dalvik is still stored on the SD card.
Click to expand...
Click to collapse
How do I move the dalvik to the phones internal memory?
I presume I followed the guide correctly as i've come from t-mobile touch g2 on 1.5 and am now using 2.1 villain rom and cronos rom before that but am still running out of memory, even with partitioning my sd card.
presumably then its the dalvik located on the sd card?
dazzer1975 said:
How do I move the dalvik to the phones internal memory?
I presume I followed the guide correctly as i've come from t-mobile touch g2 on 1.5 and am now using 2.1 villain rom and cronos rom before that but am still running out of memory, even with partitioning my sd card.
presumably then its the dalvik located on the sd card?
Click to expand...
Click to collapse
yeah thats because you didn't flash either Dalvik Cache to the SD card or Dalvik-Cache to /cache thats why your phone still taking internal memory .. try this for solution :- http://www.villainrom.co.uk/wiki/index.php?title=Apps2SD
Hope it Helps
wicked cheers for that mate!!!!
Hi all,
I searched long and hard for an answer to this one, but I can't make heads or tails of it. It started when I noticed that any apps I installed wouldn't stay through reboots, and any uninstalled apps came right back. So I tried reflashing Flashback 7.0 and 7.2, but the apps were still there. It does look like 7.2 installed correctly, although the apps were still there.
Then I tried flashing several different roms (TnT, Cyanogen, Vegantab, stock), but they wouldn't boot. Flashing back to Flashback allowed the tablet to boot, but the data was still there.
I tried manually formatting /data through cwm, but I got the lovely "Error formatting /data" message. Doing the normal cwm data wipe and repartition (4096,0 and 2048,0) didn't do anything either. I tried NVFlashing back to stock 4349, no good. I tried Flashback loaded with cwm 3.0.2.8 and the stock 1.2 recovery, but no avail. I blew away the partition table and nvflashed, no good. I tried pulling the battery, no good. I tried flashing the FORMAT utility, still stuck with this data. No matter what I do, it will only boot after installing Flashback 7, and then it retains the state it was in before going wonky.
The tablet works more-or-less for every app currently installed, apps load fine, all hardware appears to work fine, but once it's rebooted everything goes back to how it was when it went belly-up.
This has gotten the better of me, I'm hoping there's some nuance that you brilliant folk know of that I'm missing. Thank you for your time.
Both /data & /sdcard reside on the internal sd and are not touched by nvflash or by installing a new rom (all of which go on the internal nand (not sdcard). There are serveral ways to clear them. You can clear /data by doing a "factory/data reset" & repartitioning in CWM wll destroy/recreate both /data & /sdcard (so make sure you backup anything you want to save on /sdcard before you repartition). The standard repartition is 2048,0, but in some situations it is benefitial to repartition to 4096, 0 & then immediately repartition back to 2048,0.
After installing a new rom you should always do a factory/data reset, wipe cache & wipe dalvik to clear out data/installs from the prior rom.
Al
Thanks Al,
I forgot to mention, I've already repartitioned several different times, going up to 4096,0 then down to 2048,0 as I've seen recommended elsewhere. The wipe data/factory reset option also doesn't seem to be affecting the data staying put.
I remember a person with a similar situation. I believe rajeevvp had the person do some testng & it came out (in that case) to be a bad internal sd. He developed a way to use the external sdcard as the internal sd. I'll see if I can find the post or you can PM him.
Al
See this post http://forum.xda-developers.com/showthread.php?t=1156200 and specifically post #44 Guide to swap internal and external SD card assignments on the ViewSonic gTablet for users with partly-functional internal SD cards.
Al
Looks like the same issue all around. Thank a million, here's to hoping it works.
Get me a dmesg output first.
Second, since you're on the 1.2 bootloader branch, don't flash the custom CWM zip file which is only for bl 1.1. Just skip that step (step 1). The rest of the steps are bootloader-independent. Step 1. is only for letting you make backups and restores using the external SD card instead of the internal one.
Third, I'd like to see the results of the test commands given in the thread that aabbondanza posted above.
Finally, for CWM 3.x and higher, I have another (and easier) technique that I think will work for backups and restores, but, I never tested as I didn't want to change bootloaders. Let me know if you're willing to be a guinea pig for testing this.
rajeevvp, the result of the test directory/file creation on /data and /sdcard were similar to the other poster, with the directories and files not being retained after unmount or reboot.
The results of the test commands are attached. Thanks again for all your help. Additionally, of course I'm willing to be a guinea pig for anything you've got in mind.
sktsswth said:
rajeevvp, the result of the test directory/file creation on /data and /sdcard were similar to the other poster, with the directories and files not being retained after unmount or reboot.
Click to expand...
Click to collapse
From the dmesg1.txt file I see that you have the non-standard internal SD card make that seems to cause this sort of problem:
<6>[ 10.001007] mmc2: new high speed SDHC card at address aaaa
<6>[ 10.007139] mmcblk3: mmc2:aaaa SE16G 14.8 GiB
<6>[ 10.011722] mmcblk3: p1 p2
Click to expand...
Click to collapse
You can either return the tablet to VS or try my workaround hack along with a new CWM for 1.2-based bootloaders (soon).
Either way, I'd like to continue this discussion further in this thread.
rajeevvp said:
From the dmesg1.txt file I see that you have the non-standard internal SD card make that seems to cause this sort of problem:
You can either return the tablet to VS or try my workaround hack along with a new CWM for 1.2-based bootloaders (soon).
Either way, I'd like to continue this discussion further in this thread.
Click to expand...
Click to collapse
Since some of these tablets are showing up with different internal sd cards than most of us, is it possible that when we are having these people nvflash back to stock, that the bct's config of these new chips would be different & we are causing the problem by flashing the incorrect bct back to the device? Would it be safer to modify our nvflashes to read & use the user's bct when nvflashing back to stock?
I've been searching and reading various answers on the subject on different phones, but I wanted to know what worked best for Aria owners.
I've done the following:
1. using Cyanogen 7.1.0 factory reset the phone.
2. formatted the SD card to have a fat partition, ext partition and swap partition.
3. installed s2e and moved the checked the apps, private apps and dalvik cache to sd.
4. checked the 'Internal' on the storage location in the application settings.
5. Installed apps everything worked fine for a couple of days.
I've rebooted the phone today and all the apps I've installed on the SD card are gone, they don't appear in the drawer. Also all of their icons are switched to generic android icons.
I've read on different forums it's got to do with the launched running before the SD card is mounted on boot. some recommend moving back the apps to the SD, but I can't do that since I've got no access to S2E, and I have to use the SD card anyway since phone memory is so small. Also many of the threads were old so I've thought something may have been changed on new Android versions.
Is there any way to solve this? I don't have access to the market so I can't install anything from it.
I'd suggest moving only application and dalvik cache (not private apps) to see if it makes a difference.
Is your partition formatted as ext3 or ext4? Are you using the "mount as ext4" option in S2E?
partition formatted as ext3 and I've used mount as ext4.
is it preferable to format it to ext4?
how can private apps can cause a problem here?
I've now wiped the phone, re installed Cyanogen and Google apps.
CaptainMaki said:
how can private apps can cause a problem here?
Click to expand...
Click to collapse
I don't think it's the cause, but I'm just trying to eliminate anything that is different from the way I've set it up on my phone since I don't have that problem.
Personally I use an ext3 partition without the "mount as ext4" setting enabled. Perhaps that setting is causing your problems.
did you install the rom, apps and the s2e, or you install the rom, s2e and then started installing apps?
are you using the default adwlauncher or did you switched to a different launcher?
When I do a clean install I install apps before and after enabling S2E. It doesn't make a difference.
I've used several different launchers (including ADW EX) but not the built-in one.
do you enable in settings - Cyanogenmod settings - applications the following:
allow application moving - checked
install location - I select internal instead of automatic.
"Allow application moving" unchecked. That setting only makes it possible to move any application to the FAT32 partition, which you shouldn't be using at all.
Are you manually moving applications to SD card in application settings or something?
Maybe that's were the problem is. and you have the setting of install location on "Automatic" or on "Internal" ?
Please read this post where I explain the proper way to set up S2E when using it to move applications: http://forum.xda-developers.com/showpost.php?p=21667779&postcount=5
When you are selecting "move to SD" from the applications settings, you are moving the application to the FAT32 partition, which is NOT what you want. On its own, this wouldn't cause any applications to stop working though. However, since you enabled the "Allow application moving" setting, that forces the phone to allow you to move any app to the FAT32 partition, even if that app does not support it. When you move apps to the FAT32 partition that don't support it, those apps will stop working.
thx for the explanation.
If I'm setting up the s2e before installing any app, I can skip step no 4 as I understand it.
is there a real difference in performance/compatibility to the file system on the ext partition? I see threads here that mention that ext4 work without any problem.
should I format the card to ext2/ext3 or ext4 ?
CaptainMaki said:
thx for the explanation.
If I'm setting up the s2e before installing any app, I can skip step no 4 as I understand it.
is there a real difference in performance/compatibility to the file system on the ext partition? I see threads here that mention that ext4 work without any problem.
should I format the card to ext2/ext3 or ext4 ?
Click to expand...
Click to collapse
ext4 should work fine. I only suggested moving to ext3 because you were having problems, but it sounds like that was unrelated.
Ok. I've formatted the card with gparted, wiped the phone, but no matter what I did S2E didn't show the Ext partition. I've finally used rom manager to partition the card and it worked fine.
I've checked the setting as you've recommended, and so far it seems fine. I'll have to wait and see if it doesn't shows up again after several more reboots.
CaptainMaki said:
I've rebooted the phone today and all the apps I've installed on the SD card are gone, they don't appear in the drawer. Also all of their icons are switched to generic android icons.
Click to expand...
Click to collapse
same with me after installing battery script that wipe the Dalvik Cache
i thought that was the problem
i did reinstall everything and still waiting to see
read the entire thread, my problem was completely solved.
I am having this issue also - I goofed and checked the 'mount as ext4' for an ext3 partition. Now I can't see any apps, including the S2E app to uncheck it or the Play store app to download another copy so I can fix it.
Any suggestions how to correct? I can't even boot into recovery mode to reflash at the moment...
Using CM7.2.0RC1 on an HTC Incredible.
What about reflashing recovery through fastboot?
Sent from my Liberty using xda premium
drenze said:
Any suggestions how to correct? I can't even boot into recovery mode to reflash at the moment...
Click to expand...
Click to collapse
Boot to recovery with SD card removed, and/or reformat the ext partition of the SD card from a computer.
Fast Boot option may be the culprit
I see folks here are deep into ext3/ext4 partitions and such (or at least you were a few months ago), and I hope it all works out great for you.
Just in case, here is a simple little fix that really helped me, without resorting to all the partitioning and reinstallation going on here.
Also, for what it's worth, I used ROM Manager Pro to auto-format the special "ext" partition on my sdcard when it was pristine, and since then have used Titanium Backup Pro to move apps to SD AFTER installing via Google Play Store or very occasionally side-installing .apk files.
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: http://forum.xda-developers.com/showthread.php?t=1873670
(I am copying this post to other relevant threads, but will not post anything further elsewhere -- only there. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
I cant still solve this :'(
in my s2e :Application,Private apps are checked! Im using ext3..
Install location is also on internal.. pls help :'((
Device Info:
- Droid X2
- 2.3.4
- CyanogenMod 10
- Patched BSR
Whenever I go into BSR to wipe my dalvik-cache, I always get an error right when I click it.
Code:
E: Can't mount /dev/block/mmcblk0p2
(File exists)
This has never necessarily caused any problems, since it still wipes it (I can verify because once I reboot, it rebuilds it). But should I do something to fix this? I've read that formating your SD and sd-ext are ways to fix it if they aren't partitioned correctly (like in FAT32 or something).
Should I format/partition them, and if so, what is the best way to do it and what settings/options should I make if needed? (PLEASE be specific and clear)!
Thanks - any questions feel free to ask!
I don't see it helping it does that on my droid x also.
appl3mac said:
I don't see it helping it does that on my droid x also.
Click to expand...
Click to collapse
I eventually did it anyways. I formatted my Internal, External. I also partitioned my External to include a 512M sd-ext. After doing this, I no longer get an error (but that error didn't cause any problems anyways). I think the error is just because it looks for a sd-ext partition, but I could be wrong.
Formatting and Partitioning wall all done through BSR.
IAreKyleW00t said:
I eventually did it anyways. I formatted my Internal, External. I also partitioned my External to include a 512M sd-ext. After doing this, I no longer get an error (but that error didn't cause any problems anyways). I think the error is just because it looks for a sd-ext partition, but I could be wrong.
Formatting and Partitioning wall all done through BSR.
Click to expand...
Click to collapse
Well that's good to know I loose hard drives buy trying to partition them so I stick to what works. Can't afford many more.
I get that error now too when wiping dalvik. I was wondering what it was about. As long as it doesn't present a problem I can live with it.
Sent from my JB'd X2
Re-format internal/external
IAreKyleW00t said:
I eventually did it anyways. I formatted my Internal, External. I also partitioned my External to include a 512M sd-ext. After doing this, I no longer get an error (but that error didn't cause any problems anyways). I think the error is just because it looks for a sd-ext partition, but I could be wrong.
Formatting and Partitioning wall all done through BSR.
Click to expand...
Click to collapse
I have been giving some thought to re-formatting both my internal and external cards also.
My X2 is extremely unstable on CM10. Most apps FC after a few seconds.
Kyle - any chance you could walk me through this process? Especially the sd-ext partition?
I assume once I have completed re-formatting I can BSR to 2.3.4 and flash away. Correct?
fambaus said:
I have been giving some thought to re-formatting both my internal and external cards also.
My X2 is extremely unstable on CM10. Most apps FC after a few seconds.
Kyle - any chance you could walk me through this process? Especially the sd-ext partition?
I assume once I have completed re-formatting I can BSR to 2.3.4 and flash away. Correct?
Click to expand...
Click to collapse
I hope you aren't thinking that formatting all that will fix the apps force closing. Because there are apps that just wont work on CM10 for us because our phone doesn't have the necessary stuff to run them. Unless its happening to every app. Usually I only have the problem of all apps force closing if I didnt do a data reset and wipe all cache
jsgraphicart said:
I hope you aren't thinking that formatting all that will fix the apps force closing. Because there are apps that just wont work on CM10 for us because our phone doesn't have the necessary stuff to run them. Unless its happening to every app. Usually I only have the problem of all apps force closing if I didnt do a data reset and wipe all cache
Click to expand...
Click to collapse
That is exactly why I was thinking of doing this.
I did SBF back to 2,3.4. Wiped data and cache and flashed CM10.
Just about every app seems to FC on me including stock browser and stock email client.
Reading through the thread it seems hit or missing for everyone so I thought the reformat might elinimate whatever is causing the issue/
Thank you.
fambaus said:
That is exactly why I was thinking of doing this.
I did SBF back to 2,3.4. Wiped data and cache and flashed CM10.
Just about every app seems to FC on me including stock browser and stock email client.
Reading through the thread it seems hit or missing for everyone so I thought the reformat might elinimate whatever is causing the issue/
Thank you.
Click to expand...
Click to collapse
The stock email and gmail do force close. There is nothing we can do about it. I have had very little force closes in the stock browser though. Facebook has also been said to force close. This is a quote from dragonzkillers OP:
"Some ICS/JB Apps Will Crash: This is noticeable on Chrome for example. This is because our drivers don't have External OES Textures. Basically that means when the apps want to draw using them (such as with Chrome's tab preview) the app will crash. This is the same problem on CM9/ICS. There is nothing we can do."
The best thing to do is just to find alternatives to those apps. There are many in the Play Store that dont force close.
fambaus said:
I have been giving some thought to re-formatting both my internal and external cards also.
My X2 is extremely unstable on CM10. Most apps FC after a few seconds.
Kyle - any chance you could walk me through this process? Especially the sd-ext partition?
I assume once I have completed re-formatting I can BSR to 2.3.4 and flash away. Correct?
Click to expand...
Click to collapse
Yeah sure, it's really easy! (I'm trying to remember the exact option names, so some might be a bit off), but jsgraphicart is right, it won't just fix all your problems - but I just found it nice to clean it all out and such. I've never had issues with the stock browser though... I use Gmail for my email app, stock browser and almost stock everything else. Stock Camera, Gallery, etc. They barely FC on me.
1. Backup all the data you need from your Internal and External SD. (it will ALL be wiped, so make sure you get everything!)
2. To be safe I wiped Data, Cache and Davlik-cache (I was reflashing CM10 - to be safe, but not yet).
3. Go to Mounts and format both the Internal and External SD's.
4. Go into "Advanced" and go to "Partition External Storage".
5. For sd-ext size choose whatever size you want (READ BOTTOM OF THIS POST). Set 0 for swap.
6. Flash CM10, Gapps and reboot. ALL DONE!
When choosing sd-ext size, this is the amount of your External SD that will be used as Internal Storage. So if you choose 256MB, you will lose 256MB of space on your External SD but gain 256MB on your internal storage. Any size will be fine, personally I choose 512MB because I put all my backups on my Internal Storage and tend to use that more than External - but most people say 128MB minimum is good. It's more of a personal preference. (Don't mess with swap, it's not worth it. SWAP is basically formatting part of your SD to be used as RAM, but it's not really worth it from what I've seen).
PS: I got the Galaxy Nexus. It feels so nice to be free from all these troubles with a locked Bootloader. I still got my DX2, so I'll be doing some modifications and whatnot to it. Hopefully I can still help out around this part of the forums... lol.
Hi. My phone was bootlooping this morning, I decided to wipe data (I had a backup of /data) reflash, and carry on. However, I accidently confused the factory reset option in TWRP with the one in the bootloader, and clicked the bootloader one. This wiped my internal sd card. I tried to use things like Undelete from play, but it only works on the external sd. I've been trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1994705) to regain my data, but I don't know what the name of the /data partition is (for example, for the galnex, it's mmcblk0p12). Does anyone know A. what the name of the partition is for the evo, or B. an easier/different way to recover my files? Thanks in advance for any assitance.
/data is mmcblk0p37 according to steelh over in this thread
roids87 said:
/data is mmcblk0p37 according to steelh over in this thread
Click to expand...
Click to collapse
awesome. however, is /data the same as internal sd card?
Va1ha1a said:
awesome. however, is /data the same as internal sd card?
Click to expand...
Click to collapse
I am not sure. You could try and use the Mount Point Swapper and see if undelete will work then. I'm just tossing out some ideas. I've never actually tried to recover anything.
I'm gonna necrobump that first thread you linked to and see if anyone knows. I'll also try mount point swapper.
Edit: I've tried everything. mount point swapper caused bootloops, the guide i mentioned earlier created .raw files with nothing inside, etc. The upside is that I didn't have my roms, photos, or music on the internal. I can't remember. What else does android normally store there?
Va1ha1a said:
I can't remember. What else does android normally store there?
Click to expand...
Click to collapse
Usually not much, random app data, downloads, photos, music(depending on settings). You may get a warning in Titanium Backup(if you use it) about a different android id, you can restore your old id, or keep your new one. I have yet to see any issues. I've restored old id's and kept new is's without issues.
roids87 said:
Usually not much, random app data, downloads, photos, music(depending on settings). You may get a warning in Titanium Backup(if you use it) about a different android id, you can restore your old id, or keep your new one. I have yet to see any issues. I've restored old id's and kept new is's without issues.
Click to expand...
Click to collapse
Thanks, I don't think I had anything of massive importance on there (at least not that I can remember)