Database Users

ext fomatted sd space in liberated Aria (eclair) doesn't show up in cyanogen 6.1.1

Hello everyone,
I recently got an HTC aria from AT&T.
After a few days I went ahead and rooted the phone.
At first I decided to try the liberated Aria (éclair) rom. It was a good experience. But just last night I decided to try another rom, so I went with Cyanogenmod 6.1.1.
While I was using liberated aria, I used rom manager to partition my sd card with the ext filesystem, so I could move some apps to it and open up some space from my phone's internal storage.
This space, while I never figured out how to move the apps, always showed in titanium backup.
With the move to Cyanogenmod 6.1.1, this partition doesn't show at all!, in fact my sd card is at 1.7 Gb!, it's like I lost an extra 0.25 Gb (which is the partition size I chose in rom manager before)... I tried partitioning in cyanogenmod with rom manager again, but then my sd card took another 0.25 Gb hit and went to 1.5 Gb!...
How do I get back to my 2Gb sdcard space? furthermore how I do partition the card such that I can extend my internal storage for apps?
Thanks
Andres

I use gparted on linux to do that. I'm not sure what OS you use, but there are live cds you could use.
But on gparted, you should be able to see all the partitions on the card and manage them as necessary.
In order to use the ext partition, you should darktremor's app2sd. Ext3 is the filesystem you should use, but ext2 works as well I believe.
Sent from my Aria - CM7 Build 2-4

thanks, I use Debian Squeeze on desktop and testing on laptop.
I just got gparted, but it says my external storage is only 1.7 Gb!
Like I said...the extra 0.25 Gb is no longer being mounted with the sdcard and it somewhere lost in the filesystem and/or apportioned to some obscure directory...

Hmmm... that is quite odd. I know some sd cards aren't actually what they state. My 8GB card only shows as 7.8GB for example.
Try formatting the whole card (Back up first!!) And see if it comes back somehow. I am not a sd card expert.
Sent from my Aria - CM7 Build 2-4

L551 said:
Try formatting the whole card (Back up first!!)
Click to expand...
Click to collapse
thats what i'd recommend.
when you installed cm6, did you do a wipe data? did you notice if it said it was wiping the ext partition? i'd guess cm6 isn't noticing the space because it was partitioned separately from the rom install.
backup your important data, format the card, and try repartitioning it again now that you've got cm6 installed.

well I'm not entirely sure why it worked this time, but I was able to fully format the card. Now I'm back to 2Gb (well, really 1.84 Gb, but that's right)
The problem I think was that I was formatting with Rom manager, and it was ignoring the extra unrecognized space. What I did different this time, is that I went into settings > sd card & storage > unmount sd card > format sd card > mount sd card > sucess!
So this successfully formatted the whole card.
Thanks for your pointers

Unfortunately trying to partition it again failed.
I tried gparted and it successfully formatted a part of the card with the ext3 filesystem (while leaving the rest as unallocated -- at least this is what gparted said). Unfortunately when mounting the sd card on my phone it complained that the card had been damaged. So I had to reformat it, undoing the previous partitioning.
Then I tried rom manager again, but the way it works is by going into recovery and partitioning the card there. Unfortunately, clockworkmod recovery showed a warning sign ( triangle with an exclamation mark in it) above an android and froze there...I had to pull the battery out to reboot my phone.
I guess my oldish version of gparted (0.7.0) doesn't like the YAF filesystem (YAFFS). So perhaps when it partitions the card, it screws up the existing YAFFS partition. I'll try to use gparted again to partition the card fully, 256 Mb ext3 as extra app storage and the rest, I guess ext3 as well.
Andres

I finally did get it to work on both R012 and FR008 (as well as CM6.1.1 and CM7)
I formatted the sdcard with gparted (chose a 512 Mb ext3 partition with 32 Mb Swap). Then from android's terminal emulator (as root) I typed
Code:
a2sd check
and it enabled apps2sd using darktremor just fine. It became aware of my ext3 partition.

Camera issue on RAFDROID HD 3.2.2

Everything on the ROM works great , however I'm having an issue getting the camera to work it keeps saying no sd card found ......
I'm not sure what the setup is suppose to be on the SD card,
I've tried fat32 primary then ext 3
then fat32 prim them fat 32 again
anyone help me out

Had a similar problem with another build which worked well but it couldn't find the SD where it(self) was installed.
I have tried 3.2.2 and the camera works fine so probably it is better to just reinstall the OS.
I don't understand why you had an ext3 partition I did use just a fat32 and it worked fine.
Paolo

it's my understanding that you should start with a nice clean format so format the whole sd card.
then get a partition program of your choice that can do what is needed.
move resize the first primary fat32 so that you have unallocated space of 1024. that space then needs to be assigned primary ext3. then format and that's what i did with my card and all seems fine.
then format and all should be good at least that's what i did with the partition program.
maybe your sd card isn't reading right i also read some cards were hit or miss on rafdroid.

I've tried different cards from different manu's still nothing tried formtaing differently same result, not sure what I'm missing

Not sure if you solved your problem. I had the same issue with SD RAFDROID 4.2 on a 16GB class4 SanDisk microSD card.
original partitions were:
FAT32 - 64K block size - primary
ext3
linuxswap
RAFDROID didn't detect an SD card when it came to camera and other operations that were SD dependant.
I used minitool and changed the partitions to a single FAT32 partition, with 32K bloxk size and set to primary and it worked like a charm ... this build is really good!
You may wanna backup the folders on your SD to your pc.

[Q] 64Gb EXT4 SD card not recognized

Hi,
I've recently formated my SD card from NTFS to EXT4 format, since, neither my pc or phone can detect it or re-format it.
My Note 3 is running CM11, and i've heard it should support EX4 format but it doesn't, i'm actually trying different ROM's to try to detect my SD card but since i've started, none has worked.
do you guys have any clue to help me?

Check whether shows up in Device Manager in Windows. Never looks like a problem with ROM

moneshaq said:
Hi,
I've recently formated my SD card from NTFS to EXT4 format, since, neither my pc or phone can detect it or re-format it.
My Note 3 is running CM11, and i've heard it should support EX4 format but it doesn't, i'm actually trying different ROM's to try to detect my SD card but since i've started, none has worked.
do you guys have any clue to help me?
Click to expand...
Click to collapse
It shouldn't be a Rom problem nor Kernel.
Something must be wrong with your sdCard.
Because my Note 3 N9005 detects exFat, Ntfs, Ufs, ext4 and few other format (*After Rooting*) hard drive without any issues.
I am on Stock kernel and Stock recovery.

moneshaq said:
Hi,
I've recently formated my SD card from NTFS to EXT4 format, since, neither my pc or phone can detect it or re-format it.
My Note 3 is running CM11, and i've heard it should support EX4 format but it doesn't, i'm actually trying different ROM's to try to detect my SD card but since i've started, none has worked.
do you guys have any clue to help me?
Click to expand...
Click to collapse
Note 3 support Ext4 format for internal partitions only, not for the external sdcard.
Remove your card from the phone and insert it directly to the PC (via Card Reader/Adapter) to reformat it.

The problem is that the SD Card have always worked for now more than a year, using the ExFat FileSystem.
i can't reformat it because windows don't detect it since it's ext4 FileSystem and my linux or Gparted live don't detect it as well. i'm using an external card reader (cheap i recognize it) but it has always worked as well and still work with another SD card or PSP card.
have to say i feel pretty ****ed up since i had my SD card full and my internal memory too all the time :crying:
-------------------------------------
i'm actually using S5 base / Note 4 style Tweaked ROM DEODEXED and it has detected my SD card, the problem is that it is detected as a 0,00 octet card and it can't be formatted, tried the command format with terminal but it isn't available on android.

Hi just a little up so we can remember me after holydays :fingers-crossed:

Did you try changing the filesystem in TWRP recovery?

Removable MicroSD card detected but not mounted

I have recently switched from the stock ROM (4.4.2) for my Samsung Galaxy S3 Neo+ to Cyanogen 11 (4.4.4 - I wiped data, system and cache partitions before doing this). I have a 64GB external sd card formatted to FAT32 which was working fine when using my stock ROM but Cyanogenmod will not mount it anywhere. It detects the presence of the removable sd card as I am offered to erase it in the storage section in the settings. However, there are no files under /external_sd or /storage/sdcard1.
Is there any way I can fix this and mount my external sd card?

I solved this by converting my external SD card from FAT32 to NTFS using MiniTool Partition Wizard.

Adoptable storage

Decided to start using this yesterday, was a sort of on the whim decision.
I have a 32 gig S7 and a 64 gig sd card, it is an expensive samsung SDHC EVO UHS card. (they cheaper now but was expensive when I purchased).
So previously I had internal memory which was the phone's internal storage, obviously this is not the full 32 gig as a chunk is partitioned off for OS usage.
SD card as portable storage formatted using exFAT
I noticed first when I installed superman rom I couldnt make /data F2FS, tkkg explained it is because alot of the scripts used to install the likes of magisk etc. do not support F2FS so my internal is ext4, but I managed to make the cache filesystem F2FS at least.
Likewise yesterday I discovered using the portable sdcard as F2FS is also not supported, the rom wont auto mount it and a notification appears saying its corrupted. Since I had already wiped the SD to change filesystem I decided to try adoptable storage, I enabled using the adb method and using the mixed mode so not the full sdcard is adoptable storage, in my case I chose a 50/50 split bearing in mind nandroid backups are huge, to do one single backup I need 12 gig free on the portable sdcard storage.
Interestingly I discovered the partition used for the adoptable storage is F2FS , it gets mounted under /mnt/expand/{some long random id}, I dont know the exact criteria for how parts of data get moved there but 1.8gig was utilised from the off.
Knowing its F2FS which is more resilient than exFAT, I have already moved titanium backups to the adoptable storage away from the portable sdcard storage and I plan to also move media to it as well that is currently on the portable storage.
My free space that is available for internal use is now moved from 13.6gig free out of max 25 gig to 36gig free out of a max 55gig.
I have one warning tho, I have already raised this on github to the TWRP dev's, from what I can see TWRP is not adoptable storage aware. The F2FS partition is not auto mounted in TWRP and I cannot even find a way to manually mount it (in the GUI), since some stuff from /data will get moved there it means when a nandroid backup is done parts of /data may be excluded that are sitting on the adoptable storage. Not a big deal if you doing a backup to test something, and then if you restore, its done close to when the backup is taken, but if the restore is done a long time after the backup the adoptable storage been out of sync might be an issue.
I welcome further thoughts from people.
update TWRP devs say it is supported but might be an issue with mixed mode which I will provide them more info on later.

attaching speed test
first sdcard is exfat second is f2fs Adoptable

I'm really confused what you are trying to show? Are you claiming that your sd card somehow becomes faster as adoptable storage?

I dont know if it is actually faster but it does benchmark faster probably due to using F2FS instead of exFAT.
The main reason I am preferring F2FS as it has more resilience than exFAT whilst still been fast.

Ok a little update, after my failed aatempt to upgrade to a 128 gig card, I restored the nandroid backup which I made before I first inserted the 128gig card.
Now the adopted storage is not been mounted by android, I wont be doing anything about this now as I have another 128 gig card arriving tommorow at which point I will need to setup mixed storage on that anyway, but it seems if you try to make another adoptable storage on new card, even if you have a nandroid backup, the previous adoptable storage is not preserved, suggesting the settings for it are not configurdd in a location that is included in nandroid backups.
I am not aware of a process that allows an already created adoptable storage partition to get remounted, I assume I would need to wipe the sd card again and rerun the commands to set it up which is not very user friendly.
It was running perfectly fine until I tried to make a new storage on my 128gig card, but is flawed if you are swapping out sd cards.

ok some clarification on the bench figures.
The red scard is the portable sdcard storage.
The yellow sdcard is actually the phone internal memory.
Internal memory is the adoptable storage.
So the F2FS isnt miles faster which makes sense as F2FS is supposed to be very close to exFAT in performance, faster than ext4 but not so much exFAT, however it has exFAT levels of performance with better data integrity mechanisms (exFAT has no safety mechanisms).
I found this out in two ways.
The internal memory test failed when I accidently left the bench folder read only in the adoptable storage.
I also added a custom location test of /sdcard which matched the yellow sdcard scores.
The question now is that is the slower write performance of a evo+ card going to be noticeable versus the internal storage speeds. So far indications seem no, also that by default my camera was writing to the sdcard anyway and has always worked fine.
It seems what goes on the mnt/expand or on /sdcard when device storage is specified is automatically decided by an algorithm.
Those who are want to use adoptable storage and have concerns over write speeds, there is pretty fast sdcards out there like the samsung pro which has 90mB writesm, but I think that card can only go up to 64gig in size.