[SOLVED] mmcqd cause big lag after a reboot - XPERIA X10 Q&A, Help & Troubleshooting

Hello,
Since the beginning, I have lot of problem after a reboot of my x10i :
-> lag 5 minutes after my phone has started
-> the lag lasts 7-8 minutes then, everything is ok
I saw that mmcqd use lot of cpu when the lag happened.
On google, mmcqd is a daemon use to write on internal sd.
When I removed my sd, everything is ok.
Can we do something to reduce this cpu use ?
My phone is rooted, with firmware kx10 R2B001 here http://forum.xda-developers.com/showthread.php?t=913610
baseband .58
Thanks

This may help.
http://old.nabble.com/mmcqd-uses-a-large-amount-of-cpu-td23768078.html

thank you, I'm trying right now with this script ;-)
[edit]
not work for me, trying in a terminal to just unmount my sdcard and, nothing works.
Here, this i s what I do :
umount /sdcard
mount -t vfat -o async /dev/block//vold/179:1 /sdcard
Click to expand...
Click to collapse
the mount point was find by making a cat /proc/mounts.
If someone have any idea ?
Thanks

Finally, I've found the problem.....after 3 weeks !!!!
It was my sdcard : a 16gb class 4 from PNY.
I put the original 8Gb class 2with all my data (game/photo/video) and everything is good ;-)
I found this by installing OSMonitor app from the market, we can see the message system and saw lot of problems like :
-> fat_get_cluster : invalid cluster
-> FAT : filesystem error (dev mmcblk0p1)
And now, my LOST.DIR is empty. Before, it was plenty of file in less than a hour !!
Problem solved ;-)

You Made My Day
My Galaxy Note N7000 was slow for a couple of days now - stopping every few minutes, not waking up, getting stuck in lockscreen....
I took out the 16GB SD-Card and made a fsck on my Linux Computer. No Messages about repairing the filesystem but now, afterwards, my phone works flawlessly - perhaps even better than it did for weeks now.
I'd never have guessed in that direction, because I just installed a new Custom ROM an would have blamed it for a loooong time.
Thank you, man!
ripp2003 said:
Finally, I've found the problem.....after 3 weeks !!!!
It was my sdcard : a 16gb class 4 from PNY.
I put the original 8Gb class 2with all my data (game/photo/video) and everything is good
I found this by installing OSMonitor app from the market, we can see the message system and saw lot of problems like :
-> fat_get_cluster : invalid cluster
-> FAT : filesystem error (dev mmcblk0p1)
And now, my LOST.DIR is empty. Before, it was plenty of file in less than a hour !!
Problem solved
Click to expand...
Click to collapse

For what it's worth, to anyone searching for the same issue. It took me months to bother looking into my lag when I found mmcqd consistently using at the top three of "top". This thread was a great help but my "/sdcard" was actually an internal MMC partition and not removable per se so I couldn't plug it into a PC.
I did the following:
1. Reboot into TWRP
2. Load up adb shell
3. check the dev path for /data with "mount"
4. unmount /data using TWRP's mount menu
5. ran e2fsck against the dev path from step 3
- it found errors, inconsistencies between the primary and backup superblocks.
6. ran e2fsck against /system and /cache (steps 3,4,5 again), they came back clean; ran again with e2fsck -f on all three devices to be sure
7. reboot system
8. profit!
My partitions are all ext4 as shown by mount, but you could try fsck.exfat or fsck.f2fs depending on your distro.
I really wish PA would do periodic fsck's on boot, the way any good Linux OS would.

Related

[Q] Data2ext enable but inactive after crash

Hello,
I'm using the Blayo 0.7 ROM with data2ext enabled for some time now and I nerver had any problem till now.
Yesterday my phone shutdown and I had to take off the battery and then put it back in so the phone would start.
The phone started but I lost all my configuration (wallpaper...), i thought maybe data2ext disabled itself. So I tried to enable it with adb shell but the following message appeared:
"data2ext is already enabled but not active"
I checked the mounted partitions and /data is mounted on /dev/block/mtdblock5
Everything is fine with my SD card: the FAT32 partition is still working and I can mount the ext2 partition to a TEMP folder.
I tried to disable data2ext and enable it but it didn't solve the problem.
Do you have any idea how I could correct this ?
Thanks
(sorry if it's not clear but I'm french and my english could be better )
theres a simple way to correct it: buy a new SD card
i have the same problem a few months ago... my phone crashes, all data lost. my phone doesnt read the card, my pc doesnt read the card.
The problem is that my card seam to be OK.
I still have access to the SDcard on the phone and on my computer.
The only thing is that the EXT2 partition is not mounted on /data.
But i can access that partition...
maybe wipe ur phone and try it again....?
You should manually fsck that ext2 partition.
Sent from my HTC Legend
stiffmast3r => If I can do it another way, that'd be cool
BalY0 => fsck ? directly from the phone ?
is there a boot log file anywhere so I can see what is wrong ?
Thx for your answer anyway
Yeah directly. Just use e2fsck via adb shell or some term app. Google it if you don't know how to use it.
Sent from my HTC Legend
I found fsck.ext2 on your ROM. It corrected some Errors on the partition and now it WORKS !
Thank you man, you rock !
I will now backup my app and upgrade to B0.8.4
nice....
well, im going to buy a new SD when i had that problem
jokin.......
BlaY0 said:
Yeah directly. Just use e2fsck via adb shell or some term app. Google it if you don't know how to use it.
Sent from my HTC Legend
Click to expand...
Click to collapse
hello. I don't know exactly what you mean "use e2fsck via adb shell"... I'm new to android and I came across the same problem with goodvampire...
did you mean type e2fsck in adb shell? any options or arguments needed????
type "e2fsck --help" to find out which arguments you need. And of course google it.

Will not charge pass 96% and internal is 1.84gb not 16gb help me please

I ordered a tablet off of eBay. It already has VEGAn-TAB 2.2
batterie will not charge pass 96%.
Also the internal drive is 1.84gb and it's not showing up as 16gb
Well I can't figure out what the hell is going on. Do i need to install a another rom? Or is something going on with a batterie?
The battery level issue is common. Please do a forum search and you will find answers. And the 16 GB is the sdcard1 capacity, not the internal drive one.
ravenv12 said:
I ordered a tablet off of eBay. It already has VEGAn-TAB 2.2
batterie will not charge pass 96%.
Also the internal drive is 1.84gb and it's not showing up as 16gb
Well I can't figure out what the hell is going on. Do i need to install a another rom? Or is something going on with a batterie?
Click to expand...
Click to collapse
The battery not saying it's charging past 96% is a common issue. It is in fact charging to 100%, but it's not registering as such. Charge the battery until the light turns green, then reboot into clockworkmod recovery and wipe the battery stats; this should fix that issue.
The internal 1.84gb (labelled as /data) is just a small partition of the 16gb of total internal storage. The rest of the internal 16gb is there as /sdcard. /sdcard2 is for the external microsd card, if you have one.
Tablet will not boot now after i wipe the battery stats lol. It's coming up with Magic Value Mismatch on the boot screen. I do know some about clockwork because I use it on my Nook color that I had to root. So I just spent $260 on the tablet that I have to fix or something is going on with it .
I did a search , I'm guessing I will need to NVFlash
ravenv12 said:
Tablet will not boot now after i wipe the battery stats lol. It's coming up with Magic Value Mismatch on the boot screen. I did not mess with anything clockwork . I do know some about clockwork because I use it on my Nook color that I had to root. So I just spent $260 on the tablet that I have to fix or something is going on with it .
I did a search , I'm guessing I will need to NVFlash
Click to expand...
Click to collapse
Yeah, NVFlash should fix it; I don't know if there's an easier way to get it working again. One question, how did you wipe the battery stats without using clockworkmod? That could've caused the problem. I've wiped the battery stats through CWM several times on several different ROMs (including VEGAn TAB 5.1.1) and never had any problems. If you can still get into CWM, it might be worth wiping the battery stats from there and see if that fixes the problem. If it doesn't, a full data wipe/factory reset in CWM might be worth a shot.
I meant to say I did use clockwork to reset the batterie stats. a but I have a problem now after installing NVFlash installed good,
but every time I installed clockwork there's no options to install rom I've tried doing it a couple times.
I figured out how to get clockwork working but the batterie is still having issue.
ravenv12 said:
I meant to say I did use clockwork to reset the batterie stats. a but I have a problem now after installing NVFlash installed good,
but every time I installed clockwork there's no options to install rom I've tried doing it a couple times.
Click to expand...
Click to collapse
The option is under "install zip from sdcard", then "choose zip from sdcard". If you don't see that, are you sure you installed the correct version of CWM? Everything you need (including the only version of CWM that works well on the gtab) can be found in this post: http://forum.xda-developers.com/showthread.php?t=865245.
ravenv12 said:
I figured out how to get clockwork working but the batterie is still having issue.
Click to expand...
Click to collapse
I'd say try wiping the battery stats, but I'm afraid the same thing will happen as happened the first time you tried that.
Here's what I found in another forum from member xmr405o:
"I didn't reset my battery stats. I let the battery drain until it shut off by itself, then plugged my gtab until green fully charged light and then that's when I turned it on...then boom 100% and my battery indicator was more accurate."
I have tried the reset couple times already. It also was messing up in the stock version. Everything is running correctly. Except batterie stats
CWM is running right. I have VEGAn GE back on it. But the battery stats are still messed up. I am draining the battery .
ravenv12 said:
Tablet will not boot now after i wipe the battery stats lol. It's coming up with Magic Value Mismatch on the boot screen. I do know some about clockwork because I use it on my Nook color that I had to root. So I just spent $260 on the tablet that I have to fix or something is going on with it .
I did a search , I'm guessing I will need to NVFlash
Click to expand...
Click to collapse
You're using the wrong version of CWM. The Gtablet has issues with all newer versions; it's something about the filesystem. Look for the 0.8 version posted on the forums here, the one modified by Bekkit (assuming you have a 1.1 bootloader).
The battery only going to 96% (or to 104% for some people) is a hardware problem. Wiping battery stats is not going to fix things.
I've tried out the other methods that the people on the board have suggested, and I can say that they a) either don't work or b) they work unreliably.
I have a small post on the kernel battery driver implementation which goes into some of the reasons why this is a hardware problem, here:
http://forum.xda-developers.com/showpost.php?p=13542018&postcount=44
rajeevvp said:
The battery only going to 96% (or to 104% for some people) is a hardware problem. Wiping battery stats is not going to fix things.
I've tried out the other methods that the people on the board have suggested, and I can say that they a) either don't work or b) they work unreliably.
I have a small post on the kernel battery driver implementation which goes into some of the reasons why this is a hardware problem, here:
http://forum.xda-developers.com/showpost.php?p=13542018&postcount=44
Click to expand...
Click to collapse
Interesting. Good to know. I've tried wiping the battery stats, running the tablet until it's dead, then charging it until the green light comes on to fix this problem and it has worked, but it's true that it works unreliably (i.e. it works sometimes, but not always or it works at first, but then reverts to not charging past 96%). I assumed the problem had to do with the battery not being calibrated; I didn't realize that the relative state of charge readings from the hardware were inherently so imprecise.
raphenucleus said:
The internal 1.84gb (labelled as /sdcard) is just a small partition of the 16gb of total internal storage. The rest of the internal 16gb is there as your system memory (everything other than /sdcard or /sdcard2). /sdcard2 is for the external microsd card, if you have one.
Click to expand...
Click to collapse
That is not quite accurate. A quick FYI might be helpful here:
The gTablet can have up to 2 SD cards, one internal--ie built into the board--and one external, which the user can purchase and insert into the MicroSD card slot.
The Linux kernel understands these 2 SD cards as follows:
/dev/block/mmcblk3 - this is the internal SD card device, which is always present.
/dev/block/mmcblk2 - this is the external SD card device, if you have it.
The internal SD card is 16GB (unformatted) in size. ViewSonic's ROM, and all the other 3rd party ROMs for the gTablet, (generally) create 2 partitions on this internal SD card. The partitions have certain standard sizes, are formatted as 2 different filesystems, and are mounted at specific places depending on the ROM.
Code:
Internal SD card (raw ie. unformatted sizes):
Partition # Linux device name Size Mounted at Filesystem type
1 /dev/block/mmcblk3p1 ~14GB /mnt/sdcard VFAT
/mnt/emmc
2 /dev/block/mmcblk3p2 ~2GB /data ext3
Froyo-based ROMs, like ViewSonic's default, TnT-Lite and VEGAn-5.1.1 mount the first partition at /sdcard (or /mnt/sdcard--both are the same, one is a symlink to the other). The Gingerbread-based ROMs like CyanogenMod mount the same partition at /mnt/emmc (or, /emmc). VEGAn-Ginger is an exception--it uses the Froyo convention.
If you have an external SD card, it, usually, will have just 1 partition on it and it will be formatted as VFAT (aka FAT32). If this SD card has another partition on it and it is formatted as ext3, then we will have this situation (at least on CyanogenMod 7.x):
Code:
External SD card:
Partition # Linux device name Size Mounted at Filesystem type
1 /dev/block/mmcblk2p1 [I]n1[/I]GB /mnt/sdcard2 VFAT
/mnt/sdcard
2 /dev/block/mmcblk2p2 [I]n2[/I]GB /sd-ext ext3
The Froyo convention for the first (or only) partition on the second SD card is /mnt/sdcard2. In GB ROMs, that partition is mounted at /mnt/sdcard. I'm not sure what Froyo-based ROMs do to the second partition on the external SD card, but, CyanogenMod--a GB-based ROM--mounts it under /sd-ext.
2 partitions at most, on the 2 SD cards, are what the ROMs all like. You can have more partitions, but, the automounter program--vold--won't like it and the extra partitions will not appear under Settings > Storage for easy mounting and unmounting. You'll have to resort to the command line for that. (In fact, I don't even know how the partitions will be assigned to the limited no. of standard mount points when you have more than the standard no. of partitions on the SD cards.)
The same caveats hold for non-standard filesystem types. Vold likes VFAT, ext3 and ext4 (maybe even ext2) filesystems because it can sanity check these partitions using the default fs checker programs supplied with the ROMs. Other filesystems, it can't check before mounting and so it will ignore them--even if the kernel supports the filesystems (through loadable modules).
The other partitions on the gTablet, /system, /cache, ... are all on a NAND flash chip on the system board. These have a different filesystem on them called yaffs2, and they show up as a different class of devices: /dev/block/mtdblockn. The nvflash program only operates on these directly-accessible NAND flash chips. Therefore, it cannot erase any data on any of the SD cards. You must use ClockworkMod's menu options to wipe or partition SD cards.
You can, of course, also use the command line. For example, to completely wipe the internal SD card, you can boot into CWM, connect to it using adb and then type
Code:
busybox dd if=/dev/zero of=/dev/block/mmcblk3
at the prompt, or, you can wipe only the second partition of the external SD card with:
Code:
busybox dd if=/dev/zero of=/dev/block/mmcblk2p2
In fact, if you're very brave, you can even run the same commands while in Android--after unmounting the filesystems. (Don't mess with /data, though, while the system is running.)
rajeevvp said:
That is not quite accurate. A quick FYI might be helpful here:
Click to expand...
Click to collapse
While it may not be completely accurate, I was just trying to give a quick simple explanation to the OP that the full 16gb of his internal storage was there and why he thought there was only 1.84gb.
No problem. But, you should correct your first reply to the OP. The 1.84 GB partition on the internal microSD card is /data, and not /sdcard. The rest of the disk space on that SD card is what's actually mounted under /sdcard.
The /data is there for a reason. When you install 3rd party apps, the .apks and their required files are (usually, if you haven't directed otherwise) stored in /data ("On the phone", so to speak). When you "move to SD card" the .apks get transferred to /sdcard.
On phones, /data is also on the NAND flash chip, which has a limited size. This is why you have scripts like apps2sd on phones which move apps from /data and into a SD card partition. Since our /data is already on a SD card, and it is ~2GB in size, we don't need hacks like that.
rajeevvp said:
No problem. But, you should correct your first reply to the OP. The 1.84 GB partition on the internal microSD card is /data, and not /sdcard. The rest of the disk space on that SD card is what's actually mounted under /sdcard.
Click to expand...
Click to collapse
Oh sorry, you're absolutely right. I'll change that.

Swap External_SD with Internal SD (WIP, need help)

There is a sizable thread over i9003 forum about editing vold.fstab to swap internal with external sd. I guess they were more desperate as i9003 comes with very small internal storage. But even our "16GB" isn't enough for many of us.
I'm on 2.3.5, and I've tried editing the file using vim, and have failed miserably each and every time.
Unfortunately, the fstab file for i9003 differs quite a bit from the one for i9100. Here are what I've noticed:
i9003:
mount_deep
mbr_policy
i9100:
format_option
otg subsection
They also have different sysfs path and mount point.
Any knowledgeable person/people wanna jump in and make the magic happen?
does no one else see the value in this?
Sure I do
For instance I applied the idea from ownwhere (here) but in the most simple way just to test it.
I tested it with the gameloft dir.
So first I moved /sdcard/gameloft/ to /sdcard/external_sd/gameloft/
Then I created back an empty folder /sdcard/gameloft/
and then I mounted the external_sd/gameloft dir in it with :
mount --bind /sdcard/external_sd/gameloft/ /sdcard/gameloft/
I used Script Manager free version from market to run this script at boot time (added a baaad sleep 60 at the top of it to wait for the system to finish the storages checks).
And this works for me. It will help me to wait for a true external_sd / internal_storage swap mod...
I hope it will also help other people here in the same way as it did for me
sirnono said:
Sure I do
For instance I applied the idea from ownwhere (here) but in the most simple way just to test it.
I tested it with the gameloft dir.
So first I moved /sdcard/gameloft/ to /sdcard/external_sd/gameloft/
Then I created back an empty folder /sdcard/gameloft/
and then I mounted the external_sd/gameloft dir in it with :
mount --bind /sdcard/external_sd/gameloft/ /sdcard/gameloft/
I used Script Manager free version from market to run this script at boot time (added a baaad sleep 60 at the top of it to wait for the system to finish the storages checks).
And this works for me. It will help me to wait for a true external_sd / internal_storage swap mod...
I hope it will also help other people here in the same way as it did for me
Click to expand...
Click to collapse
But you'd have to unmount every time you want to use usb storage, no?
I think I've tried all realistic combination/possibility of editing the vold.fstab file given my very limited knowledge. My conclusion is, someone with knowledge needs to try this
ln -s /sdcard/external_sd/gameloft /sdcard/gameloft ?
samaral said:
ln -s /sdcard/external_sd/gameloft /sdcard/gameloft ?
Click to expand...
Click to collapse
Nope, doesn't work. Does symlink even work on FAT?
g2tl said:
But you'd have to unmount every time you want to use usb storage, no?
I think I've tried all realistic combination/possibility of editing the vold.fstab file given my very limited knowledge. My conclusion is, someone with knowledge needs to try this
Click to expand...
Click to collapse
Hello
Yes I need to do this if i want to use usb storage on desktop computer with the default system option.
But you can use apps like multi mount sd-card lite (free on market) to mount sd-card(s) on desktop computers and keep them mounted on the phone (read-only).
This way I didn't get any mounting problems but I didn't test very much so perhaps this can lead to mounting errors later on.
Maybe you have already tried this ?
I get massive slowdonws when copying large files with that widget.
Sent from my GT-I9100 using XDA App

[Solved] Mounting ext. sdcard folders to int. sdcard

Hi folks,
As you know, the Sony media and video player didn't show the mp3 and videos on the external SD card in his library.
Now my idea was to mount folders of the external sdcard into folders on the internal sdcard.
Solution:
I created a script for mounting photo, video and music folders from ext. sdcard to the corresponding folders on the int. sdcard. After successful tests, I implemented init.d support on my Tablet S for a 'autostart' solution at boot time and moved the script to 'init.d' folder. For me it works great and fulfilled my requirements 100%.
Enclosed the content of my 'automount' script:
#!/system/bin/sh
# need sleep 75 for right timing maybe you can reduce it to 30
sleep 75
mount -o bind /mnt/sdcard2/Music /mnt/sdcard/Music
mount -o bind /mnt/sdcard2/Video /mnt/sdcard/VIDEO
mount -o bind /mnt/sdcard2/Fotos /mnt/sdcard/Pictures
Click to expand...
Click to collapse
Here you can find my [HOW_TO] for init.d support:
http://forum.xda-developers.com/showthread.php?t=1505340
P.S.: If it do not work for you, try to increase the sleep value. If you have a 'fresh' system 30 should be enough ... if you use two or three widgets 'sleep 75' could be ok ... and so on ...
I hope that someone has the technical knowhow how to do this, that would be great to access extra memory
also one interesting thing in build.prop:
Code:
ro.separated.external.storage=true
Would you try what happened if you change to "false"?
I found the same entry ... but do not know what it mean.
Saw the same thing myself, but don't have an SD card with me, so I wont get to try till I get home.
But I guess the change of the mount point in the /etc/svold.fstab is particularly promising. I still waiting for a rating of a expert. No one here?
Changed that line in true, rebooted.
Openend up Poweramp and this had to scan my folders again.
Sd Card still there and working but nothing more I think.
Can't really see if there's anything changed.
I tried:
Removing nosdcard from ro.build.characteristics
Changing ro.external.storage.removable to true
Changing ro.separated.external.storage to false
I haven't been able to see any difference.
Things I looked at:
The stock video player won't recognize videos on my SD card.
Videos on SD card will play if I navigate to them using Root Explorer
I can move apps to SD card using Titanium Backup, and play them from the SD card.
Anyone have some tips on what else I can look for?
50% Solution
Hi guys,
I tried a other way (and more secure) from a hint in an other forum.
If you use the following command with adb or a app like "scripter" on your tablet,
you will mount the external card into the internal, but step by step:
1. create a new folder /external_sd under /mnt/scard/
e.g. with adb shell : mkdir -p /mnt/sdcard/external_sd
2. then mount the /mnt/sdcard2 to this folder
e.g. with adb shell: mount -o bind /mnt/sdcard2 /mnt/sdcard/external_sd
3. now it is done and if you now refresh your media library, you will find all your media stuff on your media player.
Unfortunately you have to do the same after a reboot or switch off/on.
I am a little bit afraid to add this command line in init.rc or something else.
Do one of you have a proposal how we can make it permanent, without a risk?
obicom said:
Hi guys,
I tried a other way (and more secure) from a hint in an other forum.
If you use the following command with adb or a app like "scripter" on your tablet,
you will mount the external card into the internal, but step by step:
1. create a new folder /external_sd under /mnt/scard/
e.g. with adb shell : mkdir -p /mnt/sdcard/external_sd
2. then mount the /mnt/sdcard2 to this folder
e.g. with adb shell: mount -o bind /mnt/sdcard2 /mnt/sdcard/external_sd
3. now it is done and if you now refresh your media library, you will find all your media stuff on your media player.
Unfortunately you have to do the same after a reboot or switch off/on.
I am a little bit afraid to add this command line in init.rc or something else.
Do one of you have a proposal how we can make it permanent, without a risk?
Click to expand...
Click to collapse
I will check it for you if you want but after work, evening
These are good news
I am sure for you it is a "child's play", but I think helpful for all of us.
Please let me know if I can test something ...
THANKS IN ADVANCE !
-- Edit --
Maybe we can add this command to rescan media files after mount command:
mount -o bind /mnt/sdcard2 /mnt/sdcard/external_sd
pm enable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
Click to expand...
Click to collapse
50%...............phew, getting closer, keep up the good work chaps.
http://www.androidtablets.net/forum...cation-discussion-post-root-2.html#post149151
Maybe this helps?
Good find there. Wonder if the Vizio is similar to the Sony.
Link2SD
If you want app data to be moved to external sd Link2Sd works but with a few extra steps only. Here is how I manage this on mine.
Installed Link2SD on tablet.
Formatted external card (in my case a 32GB microsd in an SD adapter) on my laptop using EASEUS to have to PRIMARY partitions 1st in FAT32 and second in EXT3 formats.
At first Link2SD does not recognise any ext partition present and if I try to recreate mounting script on it telling it EXT3 format it says something like could not do, directory does not exist or similar.
Then after a reboot Link2sd warning pops up saying the sd card was not mounted at boot and therefore the system did not load apps on it. You have an option to recreate a mounting script (which I did not need to do as did it already previously) and the quick reboot option (which is different from the regular reboot in the way that it only restarts the android interface not the whole hardware) - so I do this reboot and after everything starts you can see the extra partition and use it.
So currently quick reboot is needed after every total shutdown of the tablet - thankfully I almost never shut down the tablet completely unless run out of battery completely or some other rare reason or testing like this one.
Also note that quick reboot sometimes gives a close/wait warning just after it is done - I always chose wait and everything seemed ok after that.
Make sure you give Link2sd superuser permission. I decided to leave out Lib out of the app data I link because I noticed that if I move data back to internal storage link2SD shows that libs are unlinked already/ I know there is an option in link2sd to relink libs at boot but I was not able to confirm if it works and they tend to take little space internally anyway.
Regarding extra partition size I tried less than 1GB and ca 14Gb. With bigger than 1GB partition it seems to recognise its size in link2sd but once you move more than 1gb data to it does not reflect the increase above 1gb but still seems to make the apps I moved before and after that work still.
I wonder if multi mount widget could help when combined with link2SD somehow. My guess best solution would be to make android mount external card early in its boot.
Hope it helps
I tried today several things ....
@ps3taker
that sound a little bit more complicated then my solution with app scripter and the mount command.
I tried today several things to get a "autostart" solution but unfortunately without success:
- App "autostart (root)" don't work on Tablet S
- Change in svold.fstab need sd card eject and insert to be mounted after rboot
- Change in vold.fstab need sd card eject and insert to be mounted after reboot
- Add mount command in init.goldfish.sh don't work
- Startup script tweaks can't work, no "/system/bin/playlogosnow" on Tablet S
(http://forum.xda-developers.com/showthread.php?t=813309)
Someone additional ideas for a autostart option for the mount command?
-- Edit --
I did a little bit more investigations and find out, that after a reboot it needs a short time before the internal sd card is ready to use. Therefore it is senseless to search a solution during boot time. I guess this is the reason why the change in svold.fstab and vold.fstab didn't work.
That means we need a "autostart" App, as a Widget or a Virus scanner that mount the device and rescan the medias. Who is willing and to do that for us?
just create an init.d script and symlink the ext_sd folder to the desired folder on sdcard...
check if this device has:
/system/etc/install-recovery.sh
if it doesnt then check if the /init.rc (or other init.*.rc) files contain the text "install-recovery.sh"
if the text exists then just create the file /system/etc/install-recovery.sh which has the following at the top:
Code:
#!/system/bin/sh
followed by the symlink/bind code
and save file and give it 777 permission (chmod 777 /system/etc/install-recovery.sh)
that should automatically run the desired commands at each boot...
if the above is not possible then just create a GScipt script and execute it at startup
DooMLoRD said:
just create an init.d script and symlink the ext_sd folder to the desired folder on sdcard...
Click to expand...
Click to collapse
Hi DooMLoRD,
symlink will not work - because of fat32 sdcard! We've got to use mount -o bind, it works without problem, about autorun thing - thanks - i've got to try it
br
condi
@DooMLoRD & Condi
I did exactly this in my tests before, with the "install-recovery.sh".
The file "/system/etc/install-recovery.sh" don't exist but the the "init.rc" files contains the text "install-recovery.sh".
So I created the file "/system/etc/install-recovery.sh" with the commands:
#!/system/bin/sh
mount -o bind /mnt/sdcard2 /mnt/sdcard/external_sd
Click to expand...
Click to collapse
and give it 777 permission but unfortunately it dosen't work.
I guess the reason is the timing problem, that sdcard mount is not ready in this moment. I will try tomorrow add first the mount command for "/mnt/sdcard" in this file and will see what will happen.
Keep you informed.
thank you all for trying.
Could you please summarise what works currently please.
a) Do you manage to link apps to external sd as in rooted gingerbread?
b) or is it just for showing external sd media in the native player in a separate subfolder or something similar
c) do you manage to swap around external and internal sds, i.e. mnt\sdcard is now external as on gingebread and mnt\sdcard2 is the built-in/internal one
I think all of the above is useful but would like to know what's the initial plan.

[Q] Error mounting CD card via Link2SD

(Title of this should read SD card, not CD card)
I have read & tried every suggested method I've found on here & in web searches without success. I think the main reason may be the phone model.
I have a Huawei U8652, from Consumer Cellular (NOT AT&T Version) which I was able to root. I partitioned the SD card via mini-tool partition wizard using FAT32 Primary for both the Main & Ext2 partitions. However, when I open Links2SD I get the prompt to select the partition 2 which I choose ext2, then I get the "mount script error. mount: invalid argument". Sometimes it is busy/not available.
As I said I have tried EVERY single suggested method & each has a step that won't work or is not applicable to this phone.
Does anyone have any experience with a Consumer Cellular version of the Huawei U8652?
The end game is to remove bloatware & move apps to the SD card to remove the 'low storage' error that I got after downloading literally 1 app. (facebook). The phone is 2 weeks old. It has now been rooted with superuser & Link2SD installed successfully but I am still not seeing any free space.
Any help is greatly appreciated. I would be embarrassed to admit how many hours have been spent on this up to this point....
Thanks!

Categories

Resources