I just flashed a new rom on my evo and my question is do i need to flash apps2sd or can i just install the app so i can install apps on the sd card
I could be wrong but in order for ap2sd to work the update-script has to be changed to enable ap2sd.
chevy454 said:
I just flashed a new rom on my evo and my question is do i need to flash apps2sd or can i just install the app so i can install apps on the sd card
Click to expand...
Click to collapse
If the ROM has apps2sd built-in, you should be able to just partition your SD card and have it start working automatically. If the ROM includes an older version (like Fresh 3.3.0.1 does), you may wish to flash the new version of apps2sd before you start using it.
If the ROM doesn't have apps2sd support, it takes more than just flashing apps2sd to get it working.
im using myn's two point two rom
I made the change from a touchwiz rom to cm10 but am having some issues including call echo/recption issues. I thought i read once that it is recommended to format internal sd card before flashing a non touchwiz rom. If this will help CM10 become less buggy, what steps do i need to take in order to format internal sd using CWM without risking bricking? Thanks
Hi, I just flashed my Galaxy S3 with FrostyJB ROM v11.2.2. After the flash, SD card cannot be mounted anymore. I have a 64GB SD card in there. I then flash the kernel with stock kernel, and SD card can be mounted again.
Since this ROM is built using a custom kernel, I'm assuming the optimization is build around that kernel. So is it better to revert back to a previous version of the ROM altogether, or format the SD card with FAT32 and see if it works with the custom kernel, or it doesn't really matter having the stock kernel with this particular ROM?
Thank you for your help.
munchee said:
Hi, I just flashed my Galaxy S3 with FrostyJB ROM v11.2.2. After the flash, SD card cannot be mounted anymore. I have a 64GB SD card in there. I then flash the kernel with stock kernel, and SD card can be mounted again.
Since this ROM is built using a custom kernel, I'm assuming the optimization is build around that kernel. So is it better to revert back to a previous version of the ROM altogether, or format the SD card with FAT32 and see if it works with the custom kernel, or it doesn't really matter having the stock kernel with this particular ROM?
Thank you for your help.
Click to expand...
Click to collapse
Mine is working... I suggest re-formatting your SD card from within Frosty.
tvinhas said:
Mine is working... I suggest re-formatting your SD card from within Frosty.
Click to expand...
Click to collapse
Thanks tvinhas, but that's not the issue.
I played around more on it yesterday, and here's what I have:
FrostyJB v11.2.2 uses ktoonsez kernel, which seemed to incompatible with exFAT greater than 32GB (or perhaps just incompatible with exFAT altogether, not sure). I tried different combination and this works:
* FrostyJB ROM V11.2.2, with stock kernel
* FrostyJB ROM V11.2.2 with ktoonsez kernel, but must format SD card with FAT32
But regardless, I found another issue with this ROM version, so I decided to revert back to V11.2.1. I found that this ROM for some reason broke my USB connection. ADB and KIES won't work anymore, though windows recognizes the phone when I plugged it in and was able to read the storage. I uses KIES to sync my calendar with outlook, and I disable my KIES air. Rather than mocking around with it more, I decided to restore my nandroid.
Thanks for the help
Frosty V11.2.1 is my favorite and most stable ROM to date. I had issues with my 8gb FAT32 SD card on V11.2.2 so I went back. I was having some other issues as well but they might not have been due to the new version. I can't express enough how much I appreciate you developers taking the time to do this for the community.
UALPOW said:
Frosty V11.2.1 is my favorite and most stable ROM to date. I had issues with my 8gb FAT32 SD card on V11.2.2 so I went back. I was having some other issues as well but they might not have been due to the new version. I can't express enough how much I appreciate you developers taking the time to do this for the community.
Click to expand...
Click to collapse
Totally agree, this is my favorite ROM, and it is amazing. Can't thank all the people enough in spending time developing and debugging this.
Hi, I have been using C-rom for N7100 and it worked fine for about a week. My sdcard that is formated as exfat was recognized right away using the included kernel.
Suddenly it stopped recognizing the sd card. I thought maybe the SD card broke, but it was recognized in recovery and all my files were there.
I read that maybe changing the kernel, and tried with AGNI kernel, which it says it support exfat, but it didnt work.
Then read somewhere that the C-Rom was outdated and it was fixed on newer roms, and tried to install a paranoid android 4.45 rom (fresh install), but the sd card didnt appear again. I thought all newer AOSP roms have exfat support.
For last I restored a touchwiz rom I had before changing to c-rom and the sd card work without issues.
My question is, why the sd card suddenly stopped working in AOSP and why i couldn't fix it re-installing kernels or roms? and how can I fix it, if it happens again?
Thanks in advance
Hello.
Please I need your help.
in stock rom I can't access to my external memory card.
I've tried several.
with AOSP or CM based rom I have no problems.
it drives me crazy.:silly:
nvm.
problem solved.