Hi all--
I'm sorry in advance for the confusion I might have. I'm an extreme noob when it comes to this platform, and I'm not that great when it comes to Windows either...
Basically I was surprised to see that the external SD Card is used so much by CGM7 and is required for so much. For instance, all downloads HAVE to go to the external card. In addition: I don't know if this has anything to do with operating system, but all saved documents from basically any productivity program seems to save here by default as well.
So here are my questions:
Is there anyway to alter where things are downloaded to by the built in browser? I'd prefer that internal memory (EMMC, right?) be used... Does the default location for app installation handle this?
What exactly uses the external card by default?
Using the built-in file browser, why does it not want me to move items from internal to external storage? Why can I only copy and paste them?
I thought CWM was suppose to look on the external SD card when I use "Install zip from SD card." Instead, it looks at whatever is marked as the internal SD card. Why's that?
Thanks for your help and suggestions. I am using a gTablet, and I couldn't find a more appropriate forum for this question...
scyld said:
So here are my questions:
1. Is there anyway to alter where things are downloaded to by the built in browser? I'd prefer that internal memory (EMMC, right?) be used.
Click to expand...
Click to collapse
There is a thread just for this at the forum.cyanogenmod.com and also here:
http://forum.xda-developers.com/showthread.php?t=1028305
The last link in the first post does what you want. However, read my warnings if you do switch SD cards using that method:
http://forum.xda-developers.com/showpost.php?p=13569415&postcount=26
2. What exactly uses the external card by default?
Click to expand...
Click to collapse
Is the question what will use the external SD card, or what is using the external SD card. If it is the latter, Settings > Applications > Manage applications & Storage use has that info.
3. Using the built-in file browser, why does it not want me to move items from internal to external storage? Why can I only copy and paste them?
Click to expand...
Click to collapse
You can move them in the default File Manager. Keep your finger on the filename until a menu pops up. There is a "Move" choice.
4. I thought CWM was suppose to look on the external SD card when I use "Install zip from SD card." Instead, it looks at whatever is marked as the internal SD card. Why's that?
Click to expand...
Click to collapse
I will have to look into this, but I guess what SD card it uses depends on whether you have an external SD card in the slot or not.
The version of CWM I use, which is Clockworkmod Recovery v2.5.1.3, will use the external SD card by default when installing stuff or when making backups and when restoring, if it detects an external SD card. If one is not detected, then it will use the internal SD card instead for all its actions. See the blog post on the front page of http://bekit.net
rajeevvp said:
There is a thread just for this at the forum.cyanogenmod.com and also here:
http://forum.xda-developers.com/showthread.php?t=1028305
The last link in the first post does what you want. However, read my warnings if you do switch SD cards using that method:
http://forum.xda-developers.com/showpost.php?p=13569415&postcount=26
Click to expand...
Click to collapse
Yep, that's exactly the file I flashed in order to switch what SD card was labelled as "EMMC." Hmm, I suppose I could just move all my apps from the phone to "the external SD card"...
Is the question what will use the external SD card, or what is using the external SD card. If it is the latter, Settings > Applications > Manage applications & Storage use has that info.
Click to expand...
Click to collapse
Thanks.
You can move them in the default File Manager. Keep your finger on the filename until a menu pops up. There is a "Move" choice.
Click to expand...
Click to collapse
Pardon, I should have explained: when I do use the default File Manager's "Move" command, I get the message "Could Not Move File" whenever I try to move the file from one storage to the other.
I just downloaded Root Explorer, and it allows me to do this. However, I'm a little worried that it has Super User status, making me worried that I might accidentally do something bad with my clumsy fingers. But I suppose that's why I have CWM backing up my tablet.
Speaking of CWM...
I will have to look into this, but I guess what SD card it uses depends on whether you have an external SD card in the slot or not.
The version of CWM I use, which is Clockworkmod Recovery v2.5.1.3, will use the external SD card by default when installing stuff or when making backups and when restoring, if it detects an external SD card. If one is not detected, then it will use the internal SD card instead for all its actions. See the blog post on the front page of http://bekit.net
Click to expand...
Click to collapse
Interesting, thanks. I unfortunately do not remember which version of CWM I use, but I think it is not this one. I should check it out.
scyld said:
Yep, that's exactly the file I flashed in order to switch what SD card was labelled as "EMMC." Hmm, I suppose I could just move all my apps from the phone to "the external SD card"...
Click to expand...
Click to collapse
Here's my /system/etc/vold.fstab in its entirely. With this, my tablet uses the internal SD card as the default for storage.
Code:
## Vold 2.0 NVIDIA Harmony fstab
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
#dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.3/mmc_host/mmc0 /devices/platform/tegra-sdhci.3/mmc_host/mmc1
# dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
# dev_mount emmc /mnt/emmc auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount emmc /mnt/emmc auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
Pardon, I should have explained: when I do use the default File Manager's "Move" command, I get the message "Could Not Move File" whenever I try to move the file from one storage to the other.
I just downloaded Root Explorer, and it allows me to do this.
Click to expand...
Click to collapse
Ah, OK. The reason for the difference is due to the way the move is actually implemented in File Manager and Root Explorer.
I had an idea about why File Manager couldn't move files across filesystems, and to confirm my suspicion I attached strace to a running File Manager:
Code:
$ su
# strace -e rename -p `pidof org.openintents.filemanager`
Process 28466 attached - interrupt to quit
[I]lots of irrelevant output omitted[/I]
rename("/mnt/sdcard/Kernel/Pershoot/lib-2632.40_gb.tar.gz", "/data/local/tmp/lib-2632.40_gb.tar.gz") = -1 EXDEV (Cross-device link)
[I]more irrelevant output omitted[/I]
File Manager calls the rename() system call to move the lib-2632.40_gb.tar.gz file, which, as the spec says, will fail in this case. The program is then supposed to do the move the old-fashioned way if rename() returns an EXDEV error: copy file1 to file2 by reading bytes from file1 and writing bytes into file2; then delete file1 if the copy is successful.
But, File Manager doesn't perform this very basic fallback step. It throws up its hands at the first error and spits out the error message you got. And, it's not just File Manager. The system mv command (if you have it) in /system/bin also exhibits the same dumb behaviour. The busybox mv is more robust. (You should actually report this as a bug to the File Manager people.)
Which brings us to Root Explorer. I got curious about it after the experiment with File Manager. RE handles cross-device moves just fine. What's more, it also moves entire directory trees across devices. Having written directory tree-moving programs before, I know that this is a non-trivial bit of programming. So, I ran strace on Root Explorer to see how it handled things, and the result made me laugh.
Code:
$ su
# strace -f -e execve `pidof com.speedsoftware.rootexplorer`
Process 3602 attached with 12 threads - interrupt to quit
[I]lots of irrelevant output omitted[/I]
10893 execve("/system/xbin/busybox", ["busybox"..., "cp"..., "-pr"..., "/sdcard/Kernel/Pershoot/lib-2632"..., "/data/local/tmp/lib-2632.40_gb.t"...], [/* 19 vars */] <unfinished ...>
10893 <... execve resumed> ) = 0
10914 execve("/system/xbin/rm", ["rm"..., "-r"..., "/sdcard/Kernel/Pershoot/lib-2632"...], [/* 19 vars */] <unfinished ...>
10914 <... execve resumed> ) = 0
[I]more irrelevant output omitted[/I]
Root Explorer is also taking the easy way out: It's actually using busybox to do (almost) all of its work.
I suspected this when I compiled a new version of busybox a few days ago to test out a new compiler toolchain. I moved the newly compiled busybox into /system/xbin without properly testing it first, and discovered that most of the commands died with segfault errors.
I re-uploaded the working version of busybox back onto the tablet in /mnt/sdcard/download, and then went into Root Explorer to move this busybox into /system/xbin, and RE started force closing on every action. Once I had managed to replace busybox through other means, RE started working fine again. At that time, I didn't look at the issue too closely--I thought it was just another example of the random lossage that Android exhibits from time to time. Now I know why.
Instead of moving all applications to SD card with app2sd, I want to move only selected applications.
Because I don't want to move my launcher, soft keyboard and dialer application to SD and make them unavaliable on boot if my SD card has problem or not inserted.
The idea behind is same, linking to SD card's second partition but differs in two ways.
One, instead of linking /data/app folder (that means moving all applications), you can select the applications that you want to move.
Two, it's an application which means has a user interface. You can manage your applications, create or remove links with just few clicks.
It also provides native apps2sd features on Android 2.2 and higher. Plus, it can move any non-protected user apps to SD card (force move), with batch moving capability.
That feature uses Android's standard SD-card installation feature and does not require a second partition. It can break some apps if they are not meant to be moved to the SD card (Such as Widgets).
Features:
- Create and remove link for apk, dex and lib files of the applications you select
- Automatically link newly installed apps
- Move any user apps to SD even though the app does not support moving to SD (for Android 2.2 and higher)
- Shows the apps that support moving to SD with native apps2sd (for Android 2.2 and higher)
- Set the default install location of the apps; auto, internal, or external (for Android 2.2 and higher)
- Batch link, unlink, reinstall, uninstall, "move to SD", "move to phone" functions (multi-select mode)
- Uninstall system applications
- Freeze and un-freeze system and users applications
- Convert system apps into user apps
- Convert user apps into system apps
- Integrate "Updated" system apps into system (ROM)
- Clear data and cache of the application
- Clear all apps cache at once (1-tap cache cleaner without being root)
- List applications, show detailed size information and link status
- Sort and filter applications
- Search applications by name
- Display available space information of internal storage, SD card and SD card 2nd partition
What you need for linking applications:
- root permission
- a second partition on your SD card. You should have two partitions on SD card and both should be primary
The first FAT partition is your standard SD card storage. The second partition is used for application files and can be ext2, ext3, ext4 or FAT32.
ext4 is the latest ext format but several ROMs have issues with it while fewer have issues with ext3 and ext2. FAT works on all ROMs.
I use free "MiniTool Partition Wizard Home Edition" (windows application) for this.
You can create the second partition without repartitioning, formatting or deleting your existing partition with this tool. Connect your SD card to PC with a card reader or phone itself and make it visible as a drive. Open Minitool select this drive and resize down FAT partition, you will see an unallocated area at the end of the card. Create ext2, ext3 or FAT32 partition in that area (create as primary, not logical), click apply. Unplug from the PC and reboot the phone. (To be on the safe side backup your SD card data before starting)[/LIST]- That's all. Just install Link2SD, it will do all necessary. No need to copy files or run scripts.*
* Some phones lack the ext2, ext3 or ext4 file system support and you may get mount errors like "no such device", "invalid argument". These phones need a matching ext2.ko or ext3.ko modules and even some additional modules to be able to mount.
Using FAT32 on the second partition will eleminate such problems, because FAT32 is supported on all phones.
How it works:
Link2SD mounts the second partition of your SD card as /data/sdext2 and makes OS mounts it at boot time.
When you select an application and press "Create Link" button you can select which files of the application will be linked and moved to SD card. Apk, dex and lib files can be moved and you can select all three or any two of three or even only one of them.
Depending on what you select, Link2SD moves apk file, dalvik-cache (.dex) file and lib files (.so) to SD card's second partition and creates symbolic links in original directories.
Note: On Android 1.6 and 2.1, shortcut and the widget of the app should be re-added to homescreen if you move the apk file.
Can I remove the links and put application files back to phone?
Yes, just click on application that is linked and press "Remove Link" button. You can select which files of the application will be unlinked and moved back to internal storage.
Then, Link2SD removes the symbolic links and moves the files you selected to original directories.
What happens if I uninstall or update a linked application?
If you uninstall a linked application apk, dex and lib files will be automatically deleted from the SD card by Link2SD.
If you update a linked application new apk, dex and lib files will be placed in the internal memory at first and then they will be automatically relinked by Link2SD in the background.
You don't have to manually relink after updating applications.
Note: Since the app is linked again, On Android 1.6 and 2.1, shortcut and the widget of the app should be re-added to homescreen if the apk file is linked
Some points
- System applications should not be linked to SD card. Link2SD does not allow these applications to be linked.
- When you connect your phone to PC as mass storage, Android unmounts FAT partition but the second partition remains mounted. Therefore linked applications are not affected and can be run without problems.
- Link2SD does not move application's private data directory; it moves apk, dex (dalvik-cache) and lib files
UPDATE:
2.1.2
- fixed crash if too many apps (400+) are installed on some devices
- improved app search (use "contains" instead of "start with" and higlight the matching characters)
- updated translations
2.1.1
- some fixes and tweaks
- added Croatian language
- updated translations
2.1
- added "relink all application files" feature to scan 2nd partition and relink all the files (can be used when changing or updating the ROM)
- added "relink dex files at boot" option
- changed multi-select UI
- added batch freeze/unfreeze
- added size info of /system and /cache partitions to "Storage info"
- fixed bug in converting system apps into user apps and vice versa
- added Persian language
- updated translations
- some fixes and UI tweaks
2.0.4
- fixed relink lib bug introduced in 2.0.3
- added Catalan and Macedonian translations
- updated some translations
2.0.3
- fixed force close at startup on some devices
- updated translations
2.0.2
- fixed bug in obtaining root access on some devices
- updated translations
2.0.1
- added the ability to convert system apps into user apps
- added the ability to convert user apps into system apps
- added "Updated" mark to show if the app has been install as an update to a system (built-in) app
- added "Updated" filter option
- added the ability to integrate "Updated" system apps into system
- fixed freeze/unfreeze bug on some ICS devices
- improved ICS compatibility
- optimized link/unlink/move operations and speed improvements
- some fixes and UI tweaks
1.9.13
- added an option to change language in application settings
- fixed bug in "Storage info" that displays incorrect values if the partition is >1GB on some devices
1.9.12
- changed a2sd checking
1.9.11
- fixed "Mount warning" issue on some devices that do not have operational init scripts to mount 2nd partition at boot, e.g. new Samsung Gingerbread roms
** if you have this problem run "Recreate mount scripts" from the menu after installing the new version of Link2SD
- added Basque translation
- some fixes and tweaks
1.9.10
- fixed some issues on Android 4.0 (Ice Cream Sandwich)
- added Greek and Slovenian translations
- updated some translations
- some minor fixes and tweaks
1.9.9
- fixed bug in recognizing the second partition on some devices
- updated some translations
1.9.8
- fixed bug in setting install location option
- updated some translations
1.9.7
- moved filter and sort functions from menu to title bar
- added an indicator icon which shows the apps that can be moved to SD with native apps2sd (a small icon in upper right corner, for Android 2.2 and higher)
- added "Movable" filter option which lists the apps that support moving to SD with native apps2sd (for Android 2.2 and higher)
- added "Clear data" to clear user data from the app
- added "Clear cache" to clear the app cache
- added "Cache size" sort option
- added ability to clear cache on all apps at once
- added "View in Market" for applications
- added an option to turn "auto link notification" off
- added Dutch, Serbian, Indonesian, Vietnamese translation
- fixed bug in recognizing the 2nd partition on some devices
- updated some translations
- some minor fixes and tweaks
1.9.6
- added Japanese, Chinese Simplified, French, Arabic, Bulgarian, Czech translation
- updated some translations
- added "Translation Credits" to the About page
1.9.5
- fixed freeze/unfreeze bug on some devices
- added Chinese Traditional, German, Hungarian, Italian, Polish, Portuguese, Portuguese Brazilian, Russian, Slovak, Spanish, Thai, Ukrainian translation
- added an option to use English language instead of system language
1.9.4
- added ability to freeze and unfreeze the user and system applications
- added "Frozen" filter option
- added ability to search applications by name, activated from the menu or search button
- some minor fixes and tweaks
1.9.3
- added "Recreate mount scripts" menu to recreate mount scripts manually when you change fs type or rom
- fixed bugs in "Quick reboot" and setting "Install location" on some devices
- some minor fixes and tweaks
1.9.2:
- added "Dex size" and "Total size" sort options
- some bugfixes
1.9.1:
- fixed FC on some devices
1.9.0:
- added native apps2sd function with batch capability (for Android 2.2 and higher)
** moves any user apps to SD even though the app does not support moving to SD
- added option to set the default install location of the apps; auto, internal, or external (for Android 2.2 and higher)
- added workaround for Roms that do not have install-recovery.sh and init.d scripts to mount 2nd partition at boot, e.g. new Samsung GB roms
** mounts after system finishes booting and you need to perform 'Quick reboot'
- new and safer 'Quick reboot' method
- added context menu to app list (activated on a long press)
- added option for automatic relinking of library files at boot
- added "on SD card" and "on internal" filter options
- added applications count to the title
- some UI changes
1.8.0
- changed the method for determining external storage to support devices that have more than one external storage (MMC and SD)
- added ability to uninstall system applications
- added batch (multi-select) reinstalling
- added batch (multi-select) uninstalling
- added "Relink library files" menu which relinks all the lib files that get unlinked after reboot
- removed "Market Fix" menu
- added "fast scroll thumb" option to quickly scroll through the app list
- added "Data size" to sort options
- some bugfixes
1.7.0
- added batch linking and unlinking (multi-select mode)
- some bugfixes
1.6.2
- fixed force close on application startup on some devices
1.6.1
- added horizontal screen orientation support
- added "Link dalvik-cache files" menu back
- improved loading and scrolling performance of the app list
- added cache size to app list
- fixed "Storage Info" bug on Android 2.3
- better CM7 support
Known issue:
* library files get unlinked after reboot on Android 2.3 and sometimes on 2.1 and 2.2. (PackageManager unpacks all native libraries from the apk files at boot)
1.6.0
- added option to link library (.so) files along with apk and dex files
- added automatic linking option for the new installed apps
- added ability to link/unlink apk, dex and lib files separately
- added '->' linked indicator to Apk, Dex and Lib labels
- added lib file size and link status information
- added lib size to sort options
- some bugfixes
1.5.5
- changed link creation, reboot is not required on Android 1.6 and 2.1 anymore
1.5.4
- added notification to status bar for automatic re-linking after app update
- added "reboot required" notification to status bar after linking app on Android 1.6 and 2.1
- some bugfixes
1.5.3
- changed menu name from "Quick Restart" to "Quick Reboot"
1.5.2
- added "Quick Restart" menu, cuts boot time
- added "Clean up the dalvik-cache" menu
- added "Clean up the 2nd partition" menu
- added ability to link updated system apps (that are located in /data/app)
- optimized refreshing of the app list after linking
- changed App2sd checking
- added support in detecting and mounting the second partition for some roms
- some bugfixes
1.5.1
- fixed background message
1.5.0
- added ext3, ext4 and FAT32 support for the second partition of SD card
- added refresh menu
- added "Not Linked" filter option
- changed App2sd checking
- added support in linking protected (/data/app-private) apps
- added support in detecting and mounting the second partition for some roms
- some bugfixes
1.4.2
- disabled automatic Market status fix after linking
1.4.1
- added option to link dalvik-cache (.dex) files along with apk files
- added automatic re-linking after app upgrade
- added automatic deleting from SD card after app uninstall
- added "Reinstall" button
- added "Link dalvik-cache files" menu which links dex files of all existing linked applications all at once
- added automatic Market status fix after linking
- better froyo support
- added dex file size and link status information
1.3.1
- added support in detecting and mounting ext2 partition for some roms
- some minor bugfixes
1.3.0
- added uninstall feature which deletes apk file also from ext2 for linked apps
- added launch and manage buttons
- added detailed size information of applications
- added support in detecting and mounting ext2 partition for some roms
- some minor bugfixes
1.2.1
- added info message to show which applications have been repaired after "Market Fix"
1.2.0
- added "Market Fix" feature to repair missing Market applications
- added support in detecting and mounting ext2 partition for some roms
- removed "ext2 found" info message at startup
- some minor bugfixes
1.0.5
- added support for some roms which install-recovery.sh is not operational
- added ext2.ko module installation on boot (if exists) for Motorola phones
1.0.4
- changed mount method at startup to be much safer
- some minor bugfixes
1.0.3
- initial release:good:
awesome app..very useful..!
what? are u the developer of link2sd? "BULENT AKPINAR" ??
this one https://play.google.com/store/apps/...?t=W251bGwsMSwxLDEsImNvbS5idWFrLkxpbmsyU0QiXQ.. ???
Never ever. Have you already looked at this?
http://forum.xda-developers.com/showthread.php?t=919326
Gesendet von meinem MT11i mit Tapatalk 2
motorazrv3 said:
Never ever. Have you already looked at this?
http://forum.xda-developers.com/showthread.php?t=919326
Gesendet von meinem MT11i mit Tapatalk 2
Click to expand...
Click to collapse
just another copycat . . what a shame! :/
eewwww i have been usin this app since ages with fat32 partition on my card..!!
Now who is this :|
Sent from my MT15i using xda app-developers app
Which is the best extension to use for an AOSP ROM? was using Sony stock ROM with ext4, now shifted to an AOSP ROM, and the partition doesnt seem to work
Abhilesh7 said:
Which is the best extension to use for an AOSP ROM? was using Sony stock ROM with ext4, now shifted to an AOSP ROM, and the partition doesnt seem to work
Click to expand...
Click to collapse
fat32 is usually supported by almost all roms .
I have a problem when the SD card is partitioned with more that one partition and if is enabled the MSC transfer mode (mass storage mode):
The latest files (e.g. camera pictures) and/or folders are not displayed on PC
This behavior is not visible when the MTP transfer mode is used for connectivity. I'm using the MSC mode for systems compatibilities (Windows / Linux / MAC OS) and my phone.
I tested with three cards (Silicon power, Kingmax and a non name one).
My phone is: MT15i, Android 4.0.4, firmware 4.1.B.0.587, kernel 2.6.32.9-pref
I partitioned:
- first partition - primary partition with fat32 format; (partition size = SD size - 1,5 GB for second partion)
- second partition - primary partition with ext2 (only this format is recognized by my kernel) also I tried and fat32, but I have same problem (maximum 1,5 GB)
I made partitions using:
- GParted - from a live CD and from an Ubuntu 12.04;
- MiniTool Partition Wizard Home Edition 7.6.1 - from my Windows 7 PC;
- DiskUtility from a MAC OS.
The results are the same: the latest files or folders from SD card don't appear on the PC.
Scenario:
1. open the phone;
2. take one picture: DSC_0001.jpg;
3. connect to PC, DSC_0001.jpg is visible on the attached card;
4. disconnect the phone from PC;
5. take another picture DSC_0002.jpg;
6. connect again the phone to PC, only DSC_0001.jpg is visible.
7. reboot the phone (shutdown then power on);
8. connect the phone to the PC: DSC_0001.jpg and DSC_0002.jpg are both visible.
9. take a third picture DSC_0003.jpg;
10. connect the phone to the PC, only first two images are vizible (DSC_0001.jpg and DSC_0002.jpg)
...
After each reboot all files / folders are showed correctly when the phone is connected for the first time.
All this time, the files are stored and displayed correctly on the phone using a file explorer or an album program.
Also, if I'm reading the SD card using an external card reader, all files and folders appear ok.
Anyone have any idea what could be wrong in my case?
What else informations could be helpful?
I attached some files from my phone (/ and /etc/)
Thank you for your time!
Later edit
A possible fix is to install a custom or an original rom. Actually this fixed my issue until I installed again Link2SD with partition mount script.
I installed: [ROM]=- Xperia Ultimate HD™ 2.0.3 -= [ Stable like a Rock ] & [ Best User Interface ] after that I was able to attach my phone using MSC mode multiple times and I can access latest files / folders.
ciubexx said:
I have a problem when the SD card is partitioned with more that one partition and if is enabled the MSC transfer mode (mass storage mode):
The latest files (e.g. camera pictures) and/or folders are not displayed on PC
This behavior is not visible when the MTP transfer mode is used for connectivity. I'm using the MSC mode for systems compatibilities (Windows / Linux / MAC OS) and my phone.
I tested with three cards (Silicon power, Kingmax and a non name one).
My phone is: MT15i, Android 4.0.4, firmware 4.1.B.0.587, kernel 2.6.32.9-pref
I partitioned:
- first partition - primary partition with fat32 format; (partition size = SD size - 1,5 GB for second partion)
- second partition - primary partition with ext2 (only this format is recognized by my kernel) also I tried and fat32, but I have same problem (maximum 1,5 GB)
I made partitions using:
- GParted - from a live CD and from an Ubuntu 12.04;
- MiniTool Partition Wizard Home Edition 7.6.1 - from my Windows 7 PC;
- DiskUtility from a MAC OS.
The results are the same: the latest files or folders from SD card don't appear on the PC.
Scenario:
1. open the phone;
2. take one picture: DSC_0001.jpg;
3. connect to PC, DSC_0001.jpg is visible on the attached card;
4. disconnect the phone from PC;
5. take another picture DSC_0002.jpg;
6. connect again the phone to PC, only DSC_0001.jpg is visible.
7. reboot the phone (shutdown then power on);
8. connect the phone to the PC: DSC_0001.jpg and DSC_0002.jpg are both visible.
9. take a third picture DSC_0003.jpg;
10. connect the phone to the PC, only first two images are vizible (DSC_0001.jpg and DSC_0002.jpg)
...
After each reboot all files / folders are showed correctly when the phone is connected for the first time.
All this time, the files are stored and displayed correctly on the phone using a file explorer or an album program.
Also, if I'm reading the SD card using an external card reader, all files and folders appear ok.
Anyone have any idea what could be wrong in my case?
What else informations could be helpful?
I attached some files from my phone (/ and /etc/)
Thank you for your time!
Click to expand...
Click to collapse
open your link2sd, on 1st time it will ask you to choose mount script which kind of partition you use
after that reboot your phone.. open link2sd if it show same dialogue like 1st time open link2sd reboot go to cwm and mount your sd-ext
hmm... did you link your galery?? if yes unlink it
sorry my bad english
motorazrv3 said:
Never ever. Have you already looked at this?
http://forum.xda-developers.com/showthread.php?t=919326
Gesendet von meinem MT11i mit Tapatalk 2
Click to expand...
Click to collapse
which file system(Fat 32,ext2 etc) should be proper to use with MT11i
Thank you for your answer.
Actually my problems is visible only when I attach my phone second time to PC, after a restart.
Opening the Link2SD I'm not asked to enable the mount script, because this script is already installed and running ok, I guess, because the second partition (/data/sdext2) appear on Link2SD -> Storage Info (see attached image).
Also I'm able to navigate through that linked folder (/data/sdext2/)
The behavior is like first time when I connect my phone to the PC, on the phone is created a 'cache' from where, on second / third / ... time are provided same informations (files and folders are same like on first connection).
I'm suspecting one of scripts: init.semc.rc or init.usbmode.sh (these files are recreated at start up / booting)
I'm not sure if I'm right.
Answering to aakash43
Try for first time to create two partitions with following formats:
- first partition: fat32
- second partition: ext2
More informations you can found here on the official page: Link2SD - Description - What you need for linking applications. ( link2sd.info/description)
If second partition is not mounted try to format to fat32. It is indicated to use a unix file format (ext4, ext3 or ext2) but depends by your phone kernel. In my case the phone (Neo - MT15i with latest firmware) was not able to recognize ext4 or ext3 format.
I want to know that Creating second partition in sd card will delete the data present in sdcard.
Answering to aakash43
Depends what program you use to make partitions.
For example I used, on Windows, the MiniTool Partition Wizard Home Edition 7.6.1
I resized first partition and I added on the remaining space a second partition. I did not lost any file from first partition, but to be sure copy all files to PC, be careful to get hidden files and folders also.
But for a safe partitioning process, back-up all files and folders (including hidden files and folders) to PC first.
And delete all existing partitions and recreate new partitions. Remember, all partitions should be primary and visible.
ciubexx said:
Answering to aakash43
Depends what program you use to make partitions.
For example I used, on Windows, the MiniTool Partition Wizard Home Edition 7.6.1
I resized first partition and I added on the remaining space a second partition. I did not lost any file from first partition, but to be sure copy all files to PC, be careful to get hidden files and folders also.
But for a safe partitioning process, back-up all files and folders (including hidden files and folders) to PC first.
And delete all existing partitions and recreate new partitions. Remember, all partitions should be primary and visible.
Click to expand...
Click to collapse
Great info! :good:
workaround for my MSC issue
I figured it out a workaround in my case, for the issue detailed on previous page at post #9.
It is important to have your phone rooted!
I flashed with a clean firmware (4.1.B.0.587) my phone (MT15i), I rooted my phone and I placed a customized rom: [ROM]=- Xperia Ultimate HD™ 2.0.3 -= [ Stable like a Rock ] & [ Best User Interface ]
I opened the phone and I let it to install and configure all applications.
I rebooted twice to be sure all configurations are made properly.
I turned off my phone, I removed the SD card and I partitioned the card using my laptop card reader.
I partitioned using the MiniTool Partition Wizard Home Edition 7.6.1 on mine Windows 7 machine:
1. I deleted all partitions from my card (previously I had some partitions);
2. I created at the end of the card one primary partition with ext2 file system format; (previously I tested others formats ext3 and ext4, but seems to not be recognized these formats)
3. on the remaining space I created another primary partition with FAT32 file system format.
Like on below image:
I placed formated card into the phone and I turned on.
I modified the file: /system/etc/vold.fstab
I replaced:
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
with:
Code:
dev_mount sdcard /mnt/sdcard 1 /devices/platform/msm_sdcc.4/mmc_host/mmc1
Format is:
Code:
Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
To found that solution I made some tests after each modification on /system/etc/vold.fstab I rebooted my phone. And I checked to see if the /mnt/sdcard is mounted properly.
I modified the file on PC and after each time I pushed modified file to the phone:
Code:
adb push vold.fstab /system/etc/vold.fstab
(you should have the terminal on the current folder where is your modified file)
Then, with my phone connected to PC I tried to mount the second partition to /data/sdext2/ folder.
Open a terminal and add below commands:
Code:
>adb shell
$su -
Your terminal should look like (this is in Windows):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\ciubex>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su -
su -
[email protected]:/ #
This folder was not on my phone, so I created: #mkdir /data/sdext2/
On PC terminal I tried to mount the partition using the command:
Code:
mount -t ext2 -o rw /dev/block/mmcblk0p2 /data/sdext2
After each mount attempt you can check if the partition is mounted by using df command, the terminal should show like:
Code:
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 169.9M 76.0K 169.9M 4096
/mnt/asec 169.9M 0.0K 169.9M 4096
/mnt/obb 169.9M 0.0K 169.9M 4096
/system 312.5M 310.7M 1.8M 4096
/data 380.0M 140.0M 240.0M 4096
/cache 101.5M 1.3M 100.2M 4096
/system/vendor 133.5M 92.1M 41.4M 4096
[b]/data/sdext2 1.4G 82.6M 1.3G 1024[/b]
[email protected]:/ $
If your second partition is mounted properly, you can proceed to install Link2SD.
I installed Link2SD, I let the software to generate mount script /system/etc/install-recovery.sh.
I don't rebooted, but I modified generated file by removing the line:
Code:
I let only the mounting:
Code:
mount -t ext2 -o rw /dev/block/mmcblk0p2 /data/sdext2 1>>$LOG 2>>$LOG
Be careful to have an empty last line.
To exit from terminal, use commad: exit
After that I rebooted my phone.
Now I do not have any more problems with my latest created files or folders on the phone, when I connect the phone to PC using MSC protocol.
I attached an archive with modified files (vold.fstab and install-recovery.sh).
i used cwm recovery of lupus kernel and it partitioned my mc into fat32,ext3 n its running flawlessly
when I try to create partition using mini tool partition wizard the unlocated space does not increase above 304 MB plz help
Steps to make partitions
I really don't know what's wrong in your case, is your card empty? It is your card full and remaining empty space is 304MB?
But let suppose you have inserted a formatted card into a card reader with a single partition and want to have two partitions.
Method 1:
resize existing partition and create a second one:
- right click on partition
- select 'Move/Resize'
- click on right side of the partition image from 'Size And Location'
- move the border on left side to desired partition size
- click on 'Ok'
- now on the disks images should appear resized partition and an unallocated space at the end of the card
- right click on the Unallocated space
- select 'Create'
- on the Warning message press 'Yes' (Warning message: The new created partition cannot be used in WIndows....)
- on the 'Create New Partition' dialog window chose:
--- Create As: Primary
--- File System: Ext2
--- Press 'OK' button
- Now, your card is ready for modifications: Press Apply.
Method 2:
in that case the entire card is erased and partition(s) is (are) deleted firstly and created from beginning
- right click on partition or on each partition from card and select 'Delete'
- when entire card appear as Unallocated
- let create second partition at the end
- right click on Unallocated space and select 'Create'
- resize the partition image from 'Size And Location' by clicking on the left side and moving the left border to the right until the new partition have desired size
- select:
--- Create As: Primary
--- File System: Ext2
--- Press 'OK'
- now will create first partition
- right click on the Unallocated space
- select 'Create'
- on the Warning message press 'Yes' (Warning message: The new created partition cannot be used in WIndows....)
- on the 'Create New Partition' dialog window chose:
--- Create As: Primary
--- File System: FAT32
--- Press 'OK' button
- Now, your card is ready for modifications: Press Apply.
That's all.
This is the one I used ^^
I created a ext3 partition on the sd card, I selected what I want to moved or not.
And now, all new apps are installed on the sd card automatically.
Works great , thanks.
Hi people!
This App allows you to create some kind of shortcuts to your data files in ext-sd when they should be in internal memory. For instance, game data files, GPS maps,... It is very useful when you need to have huge amounts of data in Sola's tiny internal memory.
Check it out here:
http://www.mediafire.com/?q6hb5yvgea2z67d
http://forum.xda-developers.com/showthread.php?t=1410262
Features:
* Requires ROOT !
* Aimed at specific functionality and features (not idiot-proof)
* You can create any number of Data -> Target directory pairs, mount them manually or choose to mount them on system boot (checkbox does that).
* On/Off switch controls whole mount-on-boot function.
* Diskette icon indicates if mount operation was successful, by taping it You can mount/umount entry.
* Icon changes if application is using mounted entry
* DirectoryBind can tell what application is using this entry (tap at entry in use)
* Long tap on entry (disabled) brings edit/delete window
* App auto umount all entries on USB connected and remount after USB disconnected (for now via BroadcardReceiver UMS_CONNECTED / UMS_DISCONNECTED)
* App shows notification and vibrates if auto umount on USB fails
* If mounting all checked entries (ex. on boot) app is waiting specified time (def. 60 sec) if data directory is not available (happens sometimes at boot)
* Tested sucessfully with GTA III, NDrive, Tomtom,...
Hit thanks if you like.
And don't forget to also thank slig (thread above).
Regards
It will also help you to store your gameloft / ea games in your ext card.
Sent from my MT27i using xda premium
Divaksh said:
It will also help you to store your gameloft / ea games in your ext card.
Sent from my MT27i using xda premium
Click to expand...
Click to collapse
Indeed.
It helps you to store in an external card everything (or at least almost everything) that needs to be in the internal storage.
JohnnyCarlos said:
Hi people!
This App allows you to create some kind of shortcuts to your data files in ext-sd when they should be in internal memory. For instance, game data files, GPS maps,... It is very useful when you need to have huge amounts of data in Sola's tiny internal memory.
Check it out here:
http://www.mediafire.com/?q6hb5yvgea2z67d
http://forum.xda-developers.com/showthread.php?t=1410262
Features:
* Requires ROOT !
* Aimed at specific functionality and features (not idiot-proof)
* You can create any number of Data -> Target directory pairs, mount them manually or choose to mount them on system boot (checkbox does that).
* On/Off switch controls whole mount-on-boot function.
* Diskette icon indicates if mount operation was successful, by taping it You can mount/umount entry.
* Icon changes if application is using mounted entry
* DirectoryBind can tell what application is using this entry (tap at entry in use)
* Long tap on entry (disabled) brings edit/delete window
* App auto umount all entries on USB connected and remount after USB disconnected (for now via BroadcardReceiver UMS_CONNECTED / UMS_DISCONNECTED)
* App shows notification and vibrates if auto umount on USB fails
* If mounting all checked entries (ex. on boot) app is waiting specified time (def. 60 sec) if data directory is not available (happens sometimes at boot)
* Tested sucessfully with GTA III, NDrive, Tomtom,...
Hit thanks if you like.
And don't forget to also thank slig (thread above).
Regards
Click to expand...
Click to collapse
It's a useful tool but lacks of utility, everytime it FC the links disapear and the data get mess :crying:
chenaou said:
It's a useful tool but lacks of utility, everytime it FC the links disapear and the data get mess :crying:
Click to expand...
Click to collapse
It happened to me once.
Now I solved it by making a backup of the binds. So, from now on, when it crashes (did not happen again) I simply restore the backup and it is fine again
Greetings!
First, this message will be rather long, for which I apologize. I am providing headings that allow whomever is interested to skip to whatever is relevant to them.
About the device:
It is one of two Eken GC10X tablets, purchased from Micro Center a while back dirt cheap. The second one is 6000 miles away in Europe. . . .
It is currently running Android 4.2.2
Its firmware revision is v2.0patch1
Its kernel version is 3.4.39+, dated Friday, October 18th, 2013, at 18:11:40 CST
Its build number is wing_k70-eng 4.2.2 JDQ39 20131028 test-keys
It comes pre-rooted by default. All that needs to be done is to install a terminal program and pay attention to certain paths.
About me:
I have been messing with computers, programming, and operating systems since the time of "wood burning computers"
I know my hosts file from my fstab, I have run various flavors of both Linux and Windows in both client and server configurations, and I know that both man pages and a good search engine Are Your Friends. (which is how I came to be here!)
Issue:
Since this Eken tablet comes with a bare minimum of internal memory, I was researching ways to mitigate this. I found an article that mentioned a workaround:
Copy everything in root to a large external SD card
Transpose the settings for the internal and external memory in the /etc/vold.fstab file
Save and Reboot
The result of this is a tablet that - regardless of the presence or absence of any external SD card - always boots as if it had never been booted before, (returns to "first-boot / out-of-box" setup). Any installed apps are gone and the "internal" memory - which is about 1-2 gigs - shows absolutely full. In addition to all that, I cannot do anything with the ADB port since it requires setting the "USB Debugging" flag, which gets reset on reboot. (i.e. The ADB interface is not available.
Examining the vold.fstab shows that the original setup of that file has been returned after I did a nuke-and-reboot.
I can reboot and re-install a terminal program and advanced file manager. (X-plore is my favorite)
I see three possible solutions:
Find the reason why it's booting like this and fix it.
Find a compatible firmware release for this tablet and re-flash it - if possible - from an external SD card.[/INDENT]
Do some kind of "nandroid" backup from the other Eken GC10X tablet I have and copy it to this one. Unfortunately it's 6000 miles away and I won't be able to get to it until sometime after January 2019. In addition, I cannot access the device via the ADB port.
Research I have done:
gsmhosting's allwinner forums
This site claims to have a (ahem!), "modified" version of the firmware, which I have downloaded.
The androidmtk site
This site has the "PhoenixCard" software which alleges that it can be used to create external SD card images of firmware files that can:
Install firmware from the SD card to the device.
Allow you to run the firmware from the SD card to verify it. It should be noted that MalwareBytes flags the updater.exe file because it attempts to download from a known Trojan site. Renaming the extension, (exe.bad), solves that problem.
I have not tried re-flashing any firmware version, though I have tried running the firmware from SD, which doesn't work.
Can someone help me with suggestions on how to return this tablet to normal?
Thanks in advance for any help you can provide!
Solution:
I guess it's "umpteenth time's the charm!" :highfive:
Having done considerable research, (with everything pointing to an issue with the busybox file being in the wrong place), I decided to revisit this, did a little more digging and ultimately found a solution.
Since nothing irritates me more than someone posting "I fixed it!" without telling everyone else HOW they fixed it, here are the steps I used to solve this problem.
Please be careful. You will be mucking around with your tablet's/phone's root file system in ways that can be fatal if you're not paying attention. It's not that difficult but you DO have to PAY ATTENTION to what you're doing.
TO-DO:
Instead of copying the busybox file, it should really be a symlink to /sbin/busybox.
If anyone figures out a way to create a symlink in Android that actually works, I'd like to know.
Here it is:
Pre-requisites:
The device MUST be rooted for this to work. I cannot help you with advice on how to root individual devices. This Eken tablet comes rooted by default.
Download off-line from Android Archives, (using a different system), an early version of X-plore, which is an excellent file manager.
Load X-plore onto a thumb-drive or a micro-SD card, (I used a micro-SD), and then install the SD card / thumb drive into the tablet you're trying to fix.
Steps to solve the problem:
First, go to Settings => Security and enable "unknown sources"
Open your device's file manager
Find the copy of X-plore you downloaded, and tap it to begin the off-line installation process.
Once it installs, open it and go to the "configuration" menu. This is within the three-dot menu drop-down in the upper right-hand corner.
Select:
* (near the top) Show hidden files => select the check-box. (optional)
* Root Access => Superuser + mount writable (this allows you to change permissions to permit writing the root filesystem)
* (scroll down) Dark mode => select the check-box. (this is a personal preference; IMHO it makes it easier to read.)
* Exit configuration by using the "back" button or back arrow in the upper left corner.
* You should now see two columns representing two views of the device's file-system.
On the left side, open the "Root" filesystem, also labeled with a "/"
Scroll down and find the "/sbin" folder and open it by tapping on it.
* You may, or may not, see several folders and files. You are looking for the file "busybox"
* If you don't see it there, you may have to "find" it using the magnifying glass icon in the center row of icons.
* Open the "find" dialog and replace the "*.*" with "busybox" and then select "OK".
* (assuming you found it), tap at the right-hand edge of the row with the file-name to "select" it - a big check-mark will appear there.
Go to the right-hand side list now. Find and open:
* Root (/) like you did before.
* system
* bin
* At the top of that column, you should see a folder icon, followed by "/system/bin"
Look to see if there is a file named "busybox" there. (In my case, it was missing - which is the problem)
(assuming it's missing)
Collapse the "bin" folder by tapping on it - it might take a couple of taps.
Touch-and-hold the "bin" folder until a long list appears. Scroll down to the bottom of that list and select "permissions"
Within the permissions dialog, there are three columns: Read, Write, and Execute.
* There should be three selected boxes under "Read".
* There should be ONE selected box, the top one, under "Write"
* There should be three selected boxes under "Execute"
* Directly below the last box under "Read", the box labeled "Recursive" should NOT be selected.
* To the far right of "Recursive" should be a note that reads "Mode: 755"
Under the heading "Write", select the other two boxes so that all three are selected. The word "Mode" should now be followed by "777" Close the permissions dialog by selecting "OK".
Verify the following:
* The arrow at the top of the center column is pointing to the right. If it is not pointing to the right, tap it until it points toward the right-hand column.
* The file "busybox" on the left-hand pane has a check-mark next to it and no other files are selected.
* The "bin" folder on the right-hand side has been collapsed and is selected by being a darker black with NO check-mark.
* The top of that column shows the folder icon and "/system/bin" as the selected path.
Copy the "busybox" file into the /system/bin folder by doing the following:
* Tap the "copy" icon in the center column - it will look like two pieces of paper stacked together.
* Verify that the dialog that opens:
* Just below the top right it says "busybox" (the file you're copying)
* Under that, "Copy to"
* Under that, a folder icon and then "/system/bin".
* Under that, the selection "Move mode (delete source files) is NOT selected!
* Tap "OK" to copy the file to /system/bin. Once the copy is done, the dialog will close.
Tap "bin" on the right hand side to open it if it does not open by itself.
Verify that "busybox" appears in both the left and right hand panes.
Press and hold the "busybox" file until the list dialog re-appears.
* Select "permissions".
* Verify that all three "Read" permissions are set, only the top "Write" permission is set, and all three "Execute" permissions are set. (You may have to clear the bottom two "Write" check-boxes.)
* Verify the "Mode" is set to "755"
* Close the permissions dialog by tapping "OK"
Collapse the "bin" folder by tapping on it.
Long-press the "bin" folder, select "permissions", and set the permissions of the bin folder to "755" the way you did for the busybox file above.
Return to the "Configuration" menu by following the steps at the beginning and select "Superuser" or "Normal User" instead of "Superuser + mount writable" to prevent accidental changes in the future.
At this point, you should be able to close and re-open X-plore and verify that "busybox" actually exists within /system/bin. If it does, you can reboot and your should be good to go.
If it's not there, re-trace the steps I listed above, paying particular attention to the "Superuser" setting in "configuration" and the various file permissions.
If you're still having trouble, post a reply below and I will try to provide what help I can.
Thanks for your patience and I hope this helps others who were puzzling with this as long as I was.