Develop Bugs

[Q] Problem with installing apps to SD

Hi ,
My phone is kaiser i have froyo 2.2.2 and i install it to flash not with haret method. I install system to nand and data to sd partition but apps doesn't go to my sd card they are installing on internal memory (even they downloading to internal memory ). When i go to applications and click move to sd card then i see information that sd card is removed.
I changed many times to data to ext2 and other options but same think.
Any ideas???
I downloaded my ROM from sourceforge
Sorry for my bad english.

kuba725 said:
Hi ,
My phone is kaiser i have froyo 2.2.2 and i install it to flash not with haret method. I install system to nand and data to sd partition but apps doesn't go to my sd card they are installing on internal memory (even they downloading to internal memory ). When i go to applications and click move to sd card then i see information that sd card is removed.
I changed many times to data to ext2 and other options but same think.
Any ideas???
I downloaded my ROM from sourceforge
Sorry for my bad english.
Click to expand...
Click to collapse
Your rom probably has Terminal installed, if not download it from market.
After you have it, open it, and run " mount " without the quotes. Paste the result or screenshot.

kuba725 said:
Hi ,
My phone is kaiser i have froyo 2.2.2 and i install it to flash not with haret method. I install system to nand and data to sd partition but apps doesn't go to my sd card they are installing on internal memory (even they downloading to internal memory ). When i go to applications and click move to sd card then i see information that sd card is removed.
I changed many times to data to ext2 and other options but same think.
Any ideas???
I downloaded my ROM from sourceforge
Sorry for my bad english.
Click to expand...
Click to collapse
You have data to sd partition. I don't know if anyone has ever gotten that configuration to work with the option to move apps to SD, and I don't know any advantage in doing so.
If, on the other hand, you had data on NAND, you would want to be able to move apps to SD. I think scooter got that to work once, but I have never had success. I have tried many times. Something about the way we mount /sdcard versus /mnt/sdcard, I think, but not sure.

daedric said:
Your rom probably has Terminal installed, if not download it from market.
After you have it, open it, and run " mount " without the quotes. Paste the result or screenshot.
Click to expand...
Click to collapse
I can't mount in terminal i have only this
$ export PATH =/data/local/bin:$PATH
$
SD card is in.
ohhh sory i must write mount .....

I have this in terminal :
$ export PATH=/data/local/bin: $PATH
$mount
rootfs on / type rootfs (rw)
proc on / proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
/dev/block/mmcb1k0p1 on /sdcard type vfat (rw,noatime,nodiratime, fmask=0000, dmask=0000,allow_utime=0022,codepage=cp437 , iocharset=iso8859-1,shortname=nixed,utf8,flush,errors=remount-ro)
/dev/block/mtdblock2 on /system type yaffs2 (ro,nodev,relatime)
/dev/block/mtdblock3 on /data type yaffs2 (rw,nodev,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
tmpfs on /sqlite_stmt_journalist type tmpfs (rw,relatime,size=4096k)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuct1 type cgroup (rw,relatime,cpu)
/dev/block/mtdblock2 on /bin/su type yaffs2 (ro,nodev,relatime)
$

n2rjt said:
You have data to sd partition. I don't know if anyone has ever gotten that configuration to work with the option to move apps to SD, and I don't know any advantage in doing so.
If, on the other hand, you had data on NAND, you would want to be able to move apps to SD. I think scooter got that to work once, but I have never had success. I have tried many times. Something about the way we mount /sdcard versus /mnt/sdcard, I think, but not sure.
Click to expand...
Click to collapse
You say that i will be able to move apps to SD when data will be on Nand but i have this same issue that when i go to aplications and i click move to SD then i see information "SD card removed" (this information not always show up) then when i go to my apps i dont see this application . One time this have succes to transport it on sd and one time dont have succes

kuba725 said:
I have this in terminal :
$ export PATH=/data/local/bin: $PATH
$mount
rootfs on / type rootfs (rw)
proc on / proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
/dev/block/mmcb1k0p1 on /sdcard type vfat (rw,noatime,nodiratime, fmask=0000, dmask=0000,allow_utime=0022,codepage=cp437 , iocharset=iso8859-1,shortname=nixed,utf8,flush,errors=remount-ro)
/dev/block/mtdblock2 on /system type yaffs2 (ro,nodev,relatime)
/dev/block/mtdblock3 on /data type yaffs2 (rw,nodev,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
tmpfs on /sqlite_stmt_journalist type tmpfs (rw,relatime,size=4096k)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuct1 type cgroup (rw,relatime,cpu)
/dev/block/mtdblock2 on /bin/su type yaffs2 (ro,nodev,relatime)
$
Click to expand...
Click to collapse
Okay, now you are running with data on yaffs (which is NAND). Now you have the problem that all or most of us have. When I try to move an app to SD, it sometimes appears to work. Then, I reboot, and the app is gone.
Can we pool our knowledge and figure out how to make this feature work?

I like kaiser but he is was not created for android and i think that i will buy new phone , mayby SAMSUNG I5700 he have android 2.1 and 800 mhz is good and he has a lot of support from XDA

Kaiser was not made for android. But then again, no device was. Take the HD2, made for Winmobile 6.5 IIRC, is running W7, Android, and probably Maemo and Ubuntu and what not.
The problem with porting Android to kaiser is, first we don't have the support of google or a major provider, like HTC or Motorola.
Second, we're working blind here, we're trying to guess or find/hack many things...
Still, to take a device Announced in July 2007, with 128mb RAM, 256 rom, MSM7200 400Mhz with a Adreno 130 GPU and make it work with android, it's a damn good achievement.
Don't be sad it doesn't work oh so well, be glad it works better than windows mobile.

daedric said:
Kaiser was not made for android. But then again, no device was. Take the HD2, made for Winmobile 6.5 IIRC, is running W7, Android, and probably Maemo and Ubuntu and what not.
The problem with porting Android to kaiser is, first we don't have the support of google or a major provider, like HTC or Motorola.
Second, we're working blind here, we're trying to guess or find/hack many things...
Still, to take a device Announced in July 2007, with 128mb RAM, 256 rom, MSM7200 400Mhz with a Adreno 130 GPU and make it work with android, it's a damn good achievement.
Don't be sad it doesn't work oh so well, be glad it works better than windows mobile.
Click to expand...
Click to collapse
I don't think that kaiser is bad phone is very good but i need some new stuff
I don't have too much money, for me HD2 is best phone ever but is too expensive.
Hmmm Maybe you know some cheap phone better than the Samsung I5700???

Symlinks on 101 G9

i tried to make a symlink on my archos but when i tried it gave Function not implemented.
is there a way to implement this function?
Gr.Roymar

roymar said:
i tried to make a symlink on my archos but when i tried it gave Function not implemented.
is there a way to implement this function?
Gr.Roymar
Click to expand...
Click to collapse
Hi
Where are you trying to create these symlinks?
On the A101S you cannot create symlinks in /mnt/sdcard because this is a vfat partition which does not a support symlinking, you also won't be able to make link in /mnt/storage ; /mnt/data ; /storage ; /sdcard ; This is because these are mounted by the sdcard service which is designed to provide a windows friendly fat view onto the file system.
Creating links anywhere else shouldn't be a problem ( depending on the filesystems you are using )
Hope tjhat helps.

trevd said:
Hi
Where are you trying to create these symlinks?
On the A101S you cannot create symlinks in /mnt/sdcard because this is a vfat partition which does not a support symlinking, you also won't be able to make link in /mnt/storage ; /mnt/data ; /storage ; /sdcard ; This is because these are mounted by the sdcard service which is designed to provide a windows friendly fat view onto the file system.
Creating links anywhere else shouldn't be a problem ( depending on the filesystems you are using )
Hope tjhat helps.
Click to expand...
Click to collapse
Thanx for you're answer.
i was indeed trying to make a symlink in /storage because of de maps of the sygic navigator take a lot of room
Greetz Roymar

roymar said:
Thanx for you're answer.
i was indeed trying to make a symlink in /storage because of de maps of the sygic navigator take a lot of room
Greetz Roymar
Click to expand...
Click to collapse
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect off "symlinking" an external directory in the /storage
Cheers

trevd said:
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect on "symlinked" an external directory in the /storage
Cheers
Click to expand...
Click to collapse
That's a great solution, thank you for the effort
a thanx for you

trevd said:
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect off "symlinking" an external directory in the /storage
Cheers
Click to expand...
Click to collapse
I have archos G9 101 Turbo 250GB HDD
i try with this solution but cant true
app install to internal memory

acasilver said:
I have archos G9 101 Turbo 250GB HDD
i try with this solution but cant true
app install to internal memory
Click to expand...
Click to collapse
I would expect that to be case, This apply's to the SD Versions only, It should be fairly trivial however to change the new location to an hard disk partition. Can run the following adb command and post the output here, then i'll see if I can point you in the right direction :good:
Code:
adb shell mount
Thanks

trevd said:
I would expect that to be case, This apply's to the SD Versions only, It should be fairly trivial however to change the new location to an hard disk partition. Can run the following adb command and post the output here, then i'll see if I can point you in the right direction :good:
Code:
adb shell mount
Thanks
Click to expand...
Click to collapse
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Enable_SDE>adb shell mount
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,relatime 0 0
devtmpfs /dev devtmpfs rw,relatime,size=455588k,nr_inodes=113897,mode=755 0 0
/dev/mmcblk0p2 /mnt/system ext4 rw,noexec,noatime,user_xattr,barrier=1,data=orde
red 0 0
/dev/loop0 / squashfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
usbfs /proc/bus/usb usbfs rw,relatime,devuid=1000,busuid=1000,listuid=1000 0 0
tmpfs /tmp tmpfs rw,relatime,mode=775,gid=1000 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /mnt/rawfs rawfs rw,relatime 0 0
/dev/block/mmcblk0p2 /mnt/system ext4 rw,nosuid,noexec,noatime,user_xattr,barrie
r=1,data=ordered 0 0
/dev/block/mmcblk0p4 /data ext4 rw,nosuid,noatime,user_xattr,barrier=1,data=orde
red,noauto_da_alloc 0 0
/dev/fuse /mnt/nand fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1015,def
ault_permissions,allow_other 0 0
/dev/block/vold/8:1 /mnt/storage ext4 rw,nosuid,nodev,noexec,noatime,nodiratime,
fmode=0664,dmode=0775,uid=1000,gid=1015,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/8:1 /mnt/secure/asec ext4 rw,nosuid,nodev,noexec,noatime,nodirat
ime,fmode=0664,dmode=0775,uid=1000,gid=1015,user_xattr,barrier=1,data=ordered 0
0
tmpfs /mnt/storage/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
C:\Enable_SDE>

doesn't work on CM10.1
Hello,
Thank you for your methods!
I used your method 2 on Blue ROM (4.0.4) with success but I just put the CyanogenMod 10.1 and it doesn't work anymore, here is the command line I put on my script for CM10.1 :
mount -o bind /storage/sdcard1/Android /sdcard/Android
It only works on ADB command from the PC, if I try on Terminal emulator on the tablet I have no error but no effect.
Do you have a solution please?

pourmadeesse said:
Hello,
Thank you for your methods!
I used your method 2 on Blue ROM (4.0.4) with success but I just put the CyanogenMod 10.1 and it doesn't work anymore, here is the command line I put on my script for CM10.1 :
mount -o bind /storage/sdcard1/Android /sdcard/Android
It only works on ADB command from the PC, if I try on Terminal emulator on the tablet I have no error but no effect.
Do you have a solution please?
Click to expand...
Click to collapse
Yeah that sounds about right, it's because the /storage directory on 4.2.2 ( CM 10.1 ) is just a "virtual directory" the real data is /data/media/0 try changing your bind to there, You can probably just get away with a symlink especially if you're external sdcard is in ext4... I'll have to have a play with that!! :good:

Thank you, it works from Terminal Emulator!
An another linked question :
I restored my Gameloft games (Ice Age Village, MIB,... and Rayman) from Titanium Backup as usually but this time I have problem once I put this symlinks, it tells me I need to download datas I select Yes or ok but I have an error and I can't play, I precise it's only with CM10.1 with symlinks, I did it many time with 4.0.4 with no problem

pourmadeesse said:
Thank you, it works from Terminal Emulator!
An another linked question :
I restored my Gameloft games (Ice Age Village, MIB,... and Rayman) from Titanium Backup as usually but this time I have problem once I put this symlinks, it tells me I need to download datas I select Yes or ok but I have an error and I can't play, I precise it's only with CM10.1 with symlinks, I did it many time with 4.0.4 with no problem
Click to expand...
Click to collapse
Hmm, Maybe the Symlink method is no good for you in this particular instance. Just to be clear are you saying you used "mount --bind" or did you go with a symlink using the "ln -s" command... At a wild guess I'd be inclined to thing it maybe be some anti-piracy measure in Gamesloft Games or it could be a permissions issue.
Just a little tip for you. If you're going to ask questions you're going have to bring folks more than "I've got an error" That's doesn't tell anyone anything really.... What does the error say? for starters. The more info you have the better. Then the people who want to help can help and you get to play you're games a whole lot sooner :good: Winners All round :silly:

trevd said:
Hmm, Maybe the Symlink method is no good for you in this particular instance. Just to be clear are you saying you used "mount --bind" or did you go with a symlink using the "ln -s" command... At a wild guess I'd be inclined to thing it maybe be some anti-piracy measure in Gamesloft Games or it could be a permissions issue.
Click to expand...
Click to collapse
I did this command :
Code:
mount -o bind /storage/sdcard1 /data/media/0
My goal is to get "data" and "obb" at least on the sdcard instead of internal memory, am I doing the right thing?
Just a little tip for you. If you're going to ask questions you're going have to bring folks more than "I've got an error" That's doesn't tell anyone anything really.... What does the error say? for starters. The more info you have the better. Then the people who want to help can help and you get to play you're games a whole lot sooner :good: Winners All round :silly:
Click to expand...
Click to collapse
You're allright, here is some two screenshot of MIB without symlinks :
If first ask for additionnal files, I select Yes and it starts downloading.
But, if I run the mount command, after the first screenshot asking additionnal datas, I get this message (and screenshot doesn't work, "Couldn't capture screenshot. Couldn'tsave screenshot. Storage may be in use.") : "A problem occured and the download could not be completed successfully. Do you want to restart the download? An unstable network may cause problems when downloading." I select Yes but additionnal datas message and the same message bootloop. It seems it's a storage problem...
For Rayman, it starts without problem without symlink and I get a "Download error, please make sure you are connected to Internet and try again later" with mount command. Of course I'm connected...
Hope you can help me

Nobody knows what is the problem with symlinks and CM10.1 ?

CWM can't mount SD

I just rooted my phone and installed CWM. When I try to install a zip from SD it says "E: can't mount SD" i've tried everything (manually mount SD card and format external card from CWM and phone and nothing happened!) does anybody now a solution? can I installa a ROM from internal memory? i guess i can't...
thanks a lot!

http://www.youtube.com/watch?v=JmvCpR45LKA

sswb27 said:
http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I checked other posts and no solution for me...
thanks anyway

Download rom manger from play store and use it to update CWM.

sswb27 said:
Download rom manger from play store and use it to update CWM.
Click to expand...
Click to collapse
Thanks. I have updated it but the problem persists

Have you tried twrp recovery? If nothing else use internal storage.

Your SD card is most likely formatted in exFAT filesystem. This is a MS proprietary format that requires licensed drivers to mount. As of now there are no custom recoveries that can mount exFAT.
There are a few options:
1) Re-format the card to FAT32 and do backup.
2) Get a smaller (8-16gb) card to use for backups and keep in FAT32 format.
3*) Partition larger card (32-64gb) with multiple partition types. ex. 40gb exFAT/24gb FAT32. *Please note that I have not tried this nor seen it done but just an idea I wanted to try out to see if it was feasible. I may have time to give it a shot later today and if so I'll update this post.

dasgh said:
Your SD card is most likely formatted in exFAT filesystem. This is a MS proprietary format that requires licensed drivers to mount. As of now there are no custom recoveries that can mount exFAT.
There are a few options:
1) Re-format the card to FAT32 and do backup.
2) Get a smaller (8-16gb) card to use for backups and keep in FAT32 format.
3*) Partition larger card (32-64gb) with multiple partition types. ex. 40gb exFAT/24gb FAT32. *Please note that I have not tried this nor seen it done but just an idea I wanted to try out to see if it was feasible. I may have time to give it a shot later today and if so I'll update this post.
Click to expand...
Click to collapse
Do not partition a 64 GB micro SD to FAT32. Performance will be awful because of the way the mem blocks are sized.
Also, your internal SD is exFAT... that is read by the recovery perfectly fine.
I would say save yourself some trouble and just find a ROM kernel combo that supports exFAT micro SD. Your 64 GB will work flawlessly and performance will not take a hit.

maybe post in correct forum for more replys, just sayin

Just for anyones future reference:
This is from stock JB GS3.
Below you can see the various partitions file system types. Mostly ext4 and various ramfs types. At the bottom you can see the external storage as exfat.
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:97 /storage/extSdCard exfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 0 0
I currently understand the recovery image to work as below. Someone please correct me if it's incorrect.
While the kernel does support exfat the "interpreter" (driver) and custom recovery image can not talk to each other. The exfat driver can only be called/read if you know which system calls to use and how to interpret its response. The custom recovery image does not know how to utilize the exfat driver.

Please read forum rules before posting
Development is ONLY for developers to post release threads
Questions go in Q&A
Thread moved

sdcard - hardware or software limitation

Hello all
i have been reading this forum for a while and seen users discussing limitation of space/size. For that reason they use sd cards - 32 or 64 etc. I would like to know when they say device support upto 64 sdcard what does it mean? is it hardware limitation or software limitation?
I hope my question is not stupid. Just want to clarify.

both, methinks

The answer is it depends. I can't speak from the device side, since I'm not going to open up my tablet.
SD -> pre-formatted FAT.
SDHC -> pre-formatted FAT32
SDXC -> pre-formatted exFAT or FAT32.
Officially / legally to support exFAT, you must get a license from Microsoft.
Most devices support FAT32 but not exFAT.
Windows (at least XP) won't format things to FAT32 over a certain size, 32GB if I remember correctly.
exFAT has the advantage that it has higher limits, such as storing files over 4GB - 1 byte, which might be desirable for many 64GB / UHS-I card users as the emphasis is pretty much on recording a real time stream of full HD video and you don't always want to start a new file every couple gigs.
To further complicate matters the Android ROM (e.g. TouchWiz) does not support mounting all file systems the kernel is capable of supporting. So for example, most devices can mount FAT formatted cards but not ext4 formatted, despite the internal memory using ext4!
These are software issues.
In order to use certain "Newer" features of modern SD cards: you need to have hardware support for additional pins and signalling, including any 'reassigned' pins. Pins, as in those things on the end of the card that you plug in. An example of said newer hardware features are things like Ultra High Speed (UHS) for faster transfer rates. Some hardware may also be physically capable of these features but be loaded with firmware that does not support these features or is lacking some necessarily licensing data to enable the associated behaviour.
Our device supports the following file systems:
Code:
$ cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev binfmt_misc
nodev debugfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext2
ext3
ext4
nodev ramfs
vfat
msdos
nodev ecryptfs
nodev fuse
fuseblk
nodev fusectl
exfat
$
So all Microsoft FAT should work unless the ROM gets modded to reject!

What can you use to format a 64GB device to FAT32? I thought that wasn't possible.
Also, anyone know of an OTG cable that will actually support a 64GB SDXC device? Most of them max out at 32GB, but it sure would be nice to go higher with an OTG device.
mudge

I assume that the mounter code is the same for USB media as for card slots.
iCurmudgeon said:
What can you use to format a 64GB device to FAT32? I thought that wasn't possible.
Click to expand...
Click to collapse
Just stick it in a Linux or BSD machine and use mkfs with the right options for fat. Probably -t vfat -F32 or something like that.
Sent from my GT-N5110 using Tapatalk 4

Invalid argument error when mounting /dev/block/sda1

I'm trying to follow this post: https://forum.xda-developers.com/showpost.php?p=59166089&postcount=124 to try to get link2sd up and running, I've followed the instructions until I encountered an issue:
mount -t ext4 /dev/block/sda1 /storage/usb
mount: '/dev/block/sda1'->'/storage/usb': Invalid argument
Click to expand...
Click to collapse
The device's name is valid, I've even tried umounting the usb drive in /storage, but it still gives me that error. Have I missed something? The post is quite old and some things might have changed since then.

/system/bin/mount -t ext4 /dev/block/sda1 /storage/usb

Child's Play said:
/system/bin/mount -t ext4 /dev/block/sda1 /storage/usb
Click to expand...
Click to collapse
same thing. I've run fsck on the usb drive, just to be sure, but it seems to work perfectly well.

dictorclef said:
same thing. I've run fsck on the usb drive, just to be sure, but it seems to work perfectly well.
Click to expand...
Click to collapse
Do
ls -l /dev/block/sda1
ls -l /storage/usb
to make sure both exist.

dcarvil said:
Do
ls -l /dev/block/sda1
ls -l /storage/usb
to make sure both exist.
Click to expand...
Click to collapse
they do
ls -l /dev/block/sda1
brw------- 1 root root 8, 1 1969-12-31 19:00 /dev/block/sda1
ls -l /storage/usb
total 0
Click to expand...
Click to collapse

Should have tried this already:
/system/bin/mount -vt ext4 /dev/block/sda1 /storage/usb
mount: '/dev/block/sda1'->'/storage/usb': Invalid argument
try '/dev/block/sda1' type 'ext4' on '/storage/usb'
Click to expand...
Click to collapse
It's as if it doesn't see ext4 in the command. I wonder if it could be a bug with this magisk module? https://forum.xda-developers.com/fire-tv/development/magisk-amazon-firetv4k-ntfs-f2fs-ext4-t3991981

dictorclef said:
Should have tried this already:
It's as if it doesn't see ext4 in the command. I wonder if it could be a bug with this magisk module? https://forum.xda-developers.com/fire-tv/development/magisk-amazon-firetv4k-ntfs-f2fs-ext4-t3991981
Click to expand...
Click to collapse
Did you read note 3 at that link?
"Note 3: Some EXT4 drives may fail to mount,most likely this is because e2fsck it's failing to check for errors. In the next version i will try to add a newer version of e2fsck.However, formatting to EXT4 directly on the device will fix the issue."
You can do "cat /proc/filesystems" to make sure you have ext4 support (should NOT have "nodev" before ext4), but you still may need to format the USB drive on your firestick.

dcarvil said:
Did you read note 3 at that link?
"Note 3: Some EXT4 drives may fail to mount,most likely this is because e2fsck it's failing to check for errors. In the next version i will try to add a newer version of e2fsck.However, formatting to EXT4 directly on the device will fix the issue."
You can do "cat /proc/filesystems" to make sure you have ext4 support (should NOT have "nodev" before ext4), but you still may need to format the USB drive on your firestick.
Click to expand...
Click to collapse
Device does have ext4 support:
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev ramfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev configfs
nodev debugfs
nodev tracefs
nodev sockfs
nodev pipefs
nodev devpts
ext3
ext2
ext4
vfat
msdos
iso9660
fuseblk
nodev fuse
nodev fusectl
nodev selinuxfs
nodev functionfs
Click to expand...
Click to collapse
And I did try to format the drive using aparted on my firestick, still no luck.

I think I might actually be an idiot, /dev/block/sda1 was already mounted to /mnt/media_rw/[a bunch of numbers and letters]. Unmounted it and it will now mount where I want. Link2sd detects the partition just fine.