I'm a kind of a guy who wants atleast 250 apps on his phone which he actually had when he was on Kitkat (Link2SD linking did all the magic). After switching on to lollipop, the LP version of Link2SD is totally buggy and hardly works. Linked apps don't work, they force crash or show some other error. Link2SD is out of question and I think it's not getting any fixes because the dev says "v4 is is fully functional with LP" and v4.0.6 is already released but is still super duper buggy and it's working for no one, I'm not alone. I don't understand why does the dev still say it's "fully functional" when linked apps don't even work and neither do the mount scripts.
Anyways, link2sd is out of question now.
My query is, is there no way to "expand" the internal memory? I googled and found out some solutions like swapping internal and external memories (means internal would act as external and vice-versa, so if we have a 32GB card, system will see 32GB as internal and 2.1GB internal memory as external memory).
This appeared to be the best solution to all th problems of low internal memory and this is achieved by editing the /system/etc/vold.fstab file. But that file is not there at all on KK or LP! What the hell?! Why is Google "removing" "features" from the newer versions?!
Is there no way to swap?
nilanko said:
I'm a kind of a guy who wants atleast 250 apps on his phone which he actually had when he was on Kitkat (Link2SD linking did all the magic). After switching on to lollipop, the LP version of Link2SD is totally buggy and hardly works. Linked apps don't work, they force crash or show some other error. Link2SD is out of question and I think it's not getting any fixes because the dev says "v4 is is fully functional with LP" and v4.0.6 is already released but is still super duper buggy and it's working for no one, I'm not alone. I don't understand why does the dev still say it's "fully functional" when linked apps don't even work and neither do the mount scripts.
Anyways, link2sd is out of question now.
My query is, is there no way to "expand" the internal memory? I googled and found out some solutions like swapping internal and external memories (means internal would act as external and vice-versa, so if we have a 32GB card, system will see 32GB as internal and 2.1GB internal memory as external memory).
This appeared to be the best solution to all th problems of low internal memory and this is achieved by editing the /system/etc/vold.fstab file. But that file is not there at all on KK or LP! What the hell?! Why is Google "removing" "features" from the newer versions?!
Is there no way to swap?
Click to expand...
Click to collapse
XinternalSD is the only solution for you dude. I can confirm that it is working. It works flawlessly on lollipop, no issues at all.
I already use that but but apks, dex, lib, cache all go to internal only during installation.
I realised that even if I swap the internal (/mnt/emulated/0) and external (/mnt/media_rw/sdcard1), there still a magical "data" partition formatted in ext4 where everything goes-- dex, apks, libs, caches. So, that internal 2.17GB on Moto E which is free is actually shared by both the /mnt/emulated/0 and /data/ which is something I don't understand.
Can anybody explain how does this work? If I check in ES File explorer, 972MB of internal is shown as used up. When I open it and select all folder and files and see the properties, it shows 3 MB used up. This is so confusing.
Isn't there no way other than LINK2SD which would currently work and allow me to successfully link or directly install stuff to the second ext4 partition or SD card or *any* similar workaround? :'(
Android is so stupid :'( Why such a devastating limitation? :'(
Link2sd really works on lollipop also. After creating mount script for the first time reboot the phone , there will be a link2sd mount warning in the notifications after sometime , double click on it and choose the quick reboot option instead of recreating mount script. After quick reboot from the link2sd all the linked Apps will appear. You have to do this every time your phone boots .
Hit thanks If this helped you !
rkmiks said:
Link2sd really works on lollipop also. After creating mount script for the first time reboot the phone , there will be a link2sd mount warning in the notifications after sometime , double click on it and choose the quick reboot option instead of recreating mount script. After quick reboot from the link2sd all the linked Apps will appear. You have to do this every time your phone boots .
Hit thanks If this helped you !
Click to expand...
Click to collapse
It doesn't always work. Those apps which have lib files don't work after linking. Even if we don't link the lib files, it still doesn't work because the lib files kinda "vanish" and show 0 bytes after linking. And the apps either FC or complain about missing lib files.
nilanko said:
I realised that even if I swap the internal (/mnt/emulated/0) and external (/mnt/media_rw/sdcard1), there still a magical "data" partition formatted in ext4 where everything goes-- dex, apks, libs, caches. So, that internal 2.17GB on Moto E which is free is actually shared by both the /mnt/emulated/0 and /data/ which is something I don't understand.
Android is so stupid :'( Why such a devastating limitation? :'(
Click to expand...
Click to collapse
The internal 4GB is partitioned into /system, /data and internal sd.
/system is fixed and stores your ROM and system apps.
Back in the days /data/ used to be just like system. However now /data and internal sd are say dynamic. They grow as you install / copy stuff. This is much better than having fixed size partitions. This isn't a limitations instead consider it a flexibility.
All user apps are installed to /data by default which you cannot swap.
They don't seem to expand at all, for instance, /system/ which has a fixed size and once space is over, I can't copy anything to it!
nilanko said:
They don't seem to expand at all, for instance, /system/ which has a fixed size and once space is over, I can't copy anything to it!
Click to expand...
Click to collapse
Okay. Once again. /system/ is fixed in size for security reasons. You are not supposed to copy anything to it.
Its /data/ and internal sd that are dynamic.
Related
Hi,
I'm getting low on space message on my hero running VillainRom 6.1. Tried rebooting, still there. I've only tried to install one or 2 apps with the message there, so not sure if thats actually been affected.
settings-->sdcard & phone storage-->internal storage shows 14.83mb
quick system info shows:
sd card storage free 2.14gb
a2sd storage 249mb free (total 457mb)
system cache 129mb free
memory 37.35mb free
there doesn't seem to be any more processes running than usual - only around 3-4.
I do have quite a lot of apps, over 100, probably closer to 200, I havent counted.
btw thanks to everyone on this site, I'm new to flashing roms but having fun learning, and my phones definitely got a new lease of life.
use the apps2sd checker to make sure its working. If it is id say increase your partition from 512 to more
Just because the app is installed on the sd card (assuming its working properly) doesn't mean the davilk cache for the app has moved. unless you move this as well (which isn't really recommended) each time you install an app system memory will still go down a little.
Lennyuk said:
Just because the app is installed on the sd card (assuming its working properly) doesn't mean the davilk cache for the app has moved. unless you move this as well (which isn't really recommended) each time you install an app system memory will still go down a little.
Click to expand...
Click to collapse
http://4943922026776299669-a-180274...lcSrZUn2-7KkHiRo-ew0R2SEebAQ==&attredirects=0
u need this which is an update. copy this file into the root of the memory card and through the recovery image install it from "zip file from sdcard"
after that restart the phone and check your memory is should be 120mb
Indy_Hero said:
use the apps2sd checker to make sure its working. If it is id say increase your partition from 512 to more
Click to expand...
Click to collapse
thanks for the suggestion
a2sd check script says its working fine, also checked via adb shell.
This is what I then did to the partition size:
I copied SD card contents (both partitions) into ubuntu.
then I put SD back into phone and repartitioned using 1gb for ext2
then I copied back SD card contents from ubuntu.
I assumed this would work, but when I booted I was getting FC all the time. Bart backup sorted it out but I am still left wondering why this method of increasing partition size didnt work??
In any case quick system info shows a2sd has more space, but still got low space message.
qasi said:
...
u need this which is an update. copy this file into the root of the memory card and through the recovery image install it from "zip file from sdcard"
after that restart the phone and check your memory is should be 120mb
Click to expand...
Click to collapse
seems to have solved the problem!! thanks alot mate.
would you by any chance out of interest know why copying ext2 contents from sdcard as outlined above didnt work? - may have some future relevance if changing/upgrading roms.
Thanks again
neuro_99 said:
thanks for the suggestion
a2sd check script says its working fine, also checked via adb shell.
This is what I then did to the partition size:
I copied SD card contents (both partitions) into ubuntu.
then I put SD back into phone and repartitioned using 1gb for ext2
then I copied back SD card contents from ubuntu.
I assumed this would work, but when I booted I was getting FC all the time. Bart backup sorted it out but I am still left wondering why this method of increasing partition size didnt work??
In any case quick system info shows a2sd has more space, but still got low space message.
seems to have solved the problem!! thanks alot mate.
would you by any chance out of interest know why copying ext2 contents from sdcard as outlined above didnt work? - may have some future relevance if changing/upgrading roms.
Thanks again
Click to expand...
Click to collapse
this is because the ramon recovery image had been linked with ext2 with a 512mb partition and u selected 1gb. im not quite sure about that.
chnagin rom is quite simple beucase you have to is
1.backup using nandroid
2.make sure you wipe everything. (also battery and rotating settings)
3. Re partition your sdcard to hold 1 ext2 partition and last partition should be the rest in fat32
4. Flash the rom you want through "zip file from sd card"
5. Reboot.
im a newb so i dont have much knowledge but patching up problems that i had, so that i can help others.
it can be pain especailly rooting!!!
So thats how you would flash a rom, but what if you wanted to keep your a2sd apps? So you dont have to install them all over again in the new rom when you wiped everything.
I think I read somewhere that it should be possible to leave the contents of ext2 as it is, and that should carry forward to the next rom, but I havent been able to test it myself yet.
Ok after many hours tonight I have managed to put together a couple .zip files that will install a modified vold.fstab on your Nook Color. (I am a total n00b at this)
The EMMC of the Nook Color has a partition for the ROM and a 5 GB partition that's mostly if not completely unused. Presently, there aren't any 3rd-party managers to move apps to that unused partition, so I modified the vold.fstab and am now able to use that partition for apps, files, etc.
NC.SWAP.VOLD.ZIP swaps the way the SD and EMMC directories are mounted. By swapping the mount points, and renaming EMMC to SDCARD, your apps, etc., will install to the internal storage, vs. installing to your SDCARD. Your physical SDcard is automatically mounted as "EMMC."
This also means that the music player still finds files, you can move files to "EMMC," and you can still eject the SDcard ("EMMC"), put it back in and it still shows up automatically. Now your NC won't freak out if you pull the card out without unmounting it - all of the apps are on the actual EMMC. You'd just find the SDcard under /mnt/emmc instead of /mnt/sdcard.
Because this ZIP file maps the change at an OS level, when you boot to recovery, your NC sees SD as the SDcard, so no issues occur. When you boot into your ROM, the mount points are swapped and you'll have access to the renamed "SDCARD" (5 GB) on your NC.
Use CWR 3.0.1.0 to install the .zip and check out the results with File Manager.
Thanks go out to Clark008, luciferii and Cali^Gal from #nookcolor, Loonacy and Raymondull from #Cyanogenmod, and EpicFail1236 from XDA.
Sorry if this is a bit crude, it's my first script ever. I would be happy to get any advice on how to make this better!
EDIT: I have been looking into renaming the emmc mount to say SD-External or better yet making it mount as /mnt/sdcard/sd-ext. it might be possible, ill be looking into it as soon as I can got laid up for a bit.
"Because this ZIP file maps the change at an OS level, when you boot to recovery, your NC sees SD as the SDcard, so no issues occur. When you boot into your ROM, the mount points are swapped and you'll have access to the renamed "SDCARD" (5 GB) on your NC."
/\/\ That clarifies a lot compared to the brief orig post. Will likely be flashing it this weekend.
BTW, if this expands and you need this 2nd post just have a mod give it to you. Thanks again!
BRILLIANT. Will be definitely testing this later today. Can't wait to run SD Tools on this
Sent from my NookColor using Tapatalk
it works! interesting how it'll work out as to unmounting, flashing roms. but with emmc being useless this is fantastic.
Thank you for the effort and time place in this mod
Yeah. The whole point of this was to utilize the 5GB internal emmc and not waste it. The next step is to mod the CWM to mount emmc as /sdcard so you can flash your zips from where you download them to (usually /mnt/sdcard/download), which in this case, goes to your emmc. But CWM will mount your external sdcard instead. For the time being, we can just put the zips we need to flash to the external sdcard, ie. /mnt/emmc.
I don't know if anyone noticed it yet, but if you usb mount after the swap, the transfer speed is kind of slow (~1.5mbps). I don't know if this is due to the emmc or that the read ahead cache needs to be tweaked.
We're open to make this even better. Feel free to comment and provide feedback.
This sounds like a step in the right direction, however, what I would like to see would be merging the emmc with the internal storage. What I mean is this; right now, when I go into "Storage", I see an "SD card" (8gb), "Internal Storage" (0.92gb), and "/mnt/emmc" (5gb). Why can't we combine the .93 Internal and the 5gb emmc together to make a 5.92gb Internal storage and eliminate the emmc from teh storage area? I'm sure there is a reason that I'm not aware of, but it seems that this would be the same as just about every other device. I am pretty sure the ROM is running from the emmc partition, so that has to have something to do with it, but I don't see a purpose for 3 storage places. I keep getting errors when I try to download apps and I don't even have very many installed. I have had to move most of them to the SD card to make room and some apps don't like to be installed on the SD card.
Another option would be to swap the emmc with the Internal storage. Then we'd be using the 5gb and the .92 gb would be sitting there doing nothing instead. Again, I'm sure there are reasons for this, I'm just asking to learn.
I agree.. ideally having the emmc mount be part of the system would be ideal.
Calla969 said:
This sounds like a step in the right direction, however, what I would like to see would be merging the emmc with the internal storage. What I mean is this; right now, when I go into "Storage", I see an "SD card" (8gb), "Internal Storage" (0.92gb), and "/mnt/emmc" (5gb). Why can't we combine the .93 Internal and the 5gb emmc together to make a 5.92gb Internal storage and eliminate the emmc from teh storage area? I'm sure there is a reason that I'm not aware of, but it seems that this would be the same as just about every other device. I am pretty sure the ROM is running from the emmc partition, so that has to have something to do with it, but I don't see a purpose for 3 storage places. I keep getting errors when I try to download apps and I don't even have very many installed. I have had to move most of them to the SD card to make room and some apps don't like to be installed on the SD card.
Another option would be to swap the emmc with the Internal storage. Then we'd be using the 5gb and the .92 gb would be sitting there doing nothing instead. Again, I'm sure there are reasons for this, I'm just asking to learn.
Click to expand...
Click to collapse
i have no idea TBH but thats far beyond my ability. really it would be nice to symlink emmc to the SD card or the other way around. the issue is that you cant symlink with fat partitions :-/
This is neet. I don't know enough to comment, but it looks valuble for some people.
I just use my stock emmc for music storage and let apps sit on SD w/ videos.
WobbleTheHutt said:
i have no idea TBH but thats far beyond my ability. really it would be nice to symlink emmc to the SD card or the other way around. the issue is that you cant symlink with fat partitions :-/
Click to expand...
Click to collapse
No, but you can symlink to them. Why not set vold.fstab to mount the partitions onto other names and make symlinks named /sdcard -> /othername? That way, the symlinks can do their jobs or rearranging the namespace to suit our needs.
The ramfs isn't FAT32, is it?
I'm an old cmdline type, tricks like this are used all the time to fool software with stubborn opinions about filenames.
Dennis
Jiggity Janx said:
If this works as effectively as it sounds like it will it's gonna rock! With the multiple wifi/bluetooth file transfer options I can say bye bye to the need for an sd card!
EDIT: I think this thread is eerily quiet because of the popular advice written up HERE. Specifically #5...
IMO, with a great write up on the best ways to work with this, all of the things it will affect (positive and negative), and the proper words of warning then the individuals that take it upon themselves to modify their devices are the only ones that can be held responsible if it doesn't work out as they had hoped. They also have to understand that when they work outside the boundaries of an accepted "standard" that they are somewhat desolate and will need to come back into the fold before they can/will be helped...
Just my .02...
Click to expand...
Click to collapse
This may be slightly off topic, but I cannot for the life of me figure out what that post is complaining/ talking about, I have had no trouble bouncing between HC, CM7 and stock.
All you have to do is flash to stock and then worst case you force the boot failure and the nook resets its self automatically
The last few posts on that message are myself and another person who have had not trouble with that now the OP hasn't responded so i'm not sure what to make up that post.
Is it real and an actual issue?
Or did the poster overreact to something?
Can some one please explain it to me if I am wrong about something in using a EMMC version of HC?
chisleu said:
This is neet. I don't know enough to comment, but it looks valuble for some people.
I just use my stock emmc for music storage and let apps sit on SD w/ videos.
Click to expand...
Click to collapse
Seems neet to me also. Always interested in using both emmc and sd space.
@ chisleau - I like the concept of putting all my music on emmc. Do you use an option in CM7 to install or move all your apps to your SD card?
thinking out loud (and not actually doing it) -- but we know that /data is /dev/block/mmcblk0p6 and and the "media" or "emmc" is located at /dev/block/mmcblk0p8 -- can't we just repartition and merge the two?
minotauri said:
thinking out loud (and not actually doing it) -- but we know that /data is /dev/block/mmcblk0p6 and and the "media" or "emmc" is located at /dev/block/mmcblk0p8 -- can't we just repartition and merge the two?
Click to expand...
Click to collapse
We can repartition but don't do it for this Reason -#5 http://forum.xda-developers.com/showpost.php?p=12494638&postcount=1
http://forum.xda-developers.com/showpost.php?p=12494666&postcount=2
ROMs that follow proper packaging - This emmc swap mod is one of them. So we're fine for those who are still hesitating.
Clark008 said:
ROMs that follow proper packaging - This emmc swap mod is one of them. So we're fine for those who are still hesitating.
Click to expand...
Click to collapse
Yep, I was hesitating, but between your post above and the "Thanks" from fattire to the OP, that is all the encouragement I need to take the plunge.
A few questions, tho, if someone can help me to understand this better....
I guess until I saw the OP, I did not realize that all apps in CM7 are installed to the SD card, as when I look at my installed apps in App Mgr, they don't show as being on the SD card. Is this some sort of CM7 voodoo or are my apps really on the internal memory?
Right now, with CM7, I am using the EMMC partition to store my music, under "My Files/Music". Power Amp can see this folder and it will play all my music just fine from within that directory on the internal partition, so if I install this update, what will that do to the 5Gb of internal storage I have now and the music on it?
Also, if I do install this update, what will happen to the apps and their associated data that I already have installed? Is this best done on a fresh build or will everything (apps/data and music) be A-OK after the Swap update is applied?
Just want to know what I am getting into by applying this update, as I have things pretty stable right now. If I could roll with apps on internal and music on SD, I would be more than fine with that, as long as I don't lose any of my apps/data/music in the process. If this is just mere partition re-naming/re-pointing, then I suspect my assets will remain intact?
Thanks to all who collaborated on this project!
why can't the entire internal partitions be imaged?
i use dd all the time to backup my sd card installs in case a test kernel or nightly goes poorly- or to burn a fresh install for multiple people. I just pop in the sd card into my laptop and burn the image back to the sd card.
if this was possible i'd have no issues with running off internal entirely if i could just burn the img. and get everything back as stock, including important device identifiers incase those were erased.
Need undo
This did what it's supposed to do but it seems to be causing a problem with the way I'm booting from sd. Is there a way to undo this?
Bump since I found this useful. +1 for CWM sdcard/emmc swap to enable SDcard-less flashing goodness from ROM Manager.
Above the hood
Well today I intended to answer voyager's problem which was stated in the interactive data2sd thread located here http://forum.xda-developers.com/showthread.php?p=23744977#
and then i think that after i have gathered so much information from the other parts of the world into this little post it would be a waste if it is pushed away by regular posts in the thread. so, i opened this thread here in the general forum so all people with similar confusion can read about it.
YES, there are SO MANY WORDS TO READ. but in order to use a2sd+ or data2sd+ you MUST read them all
you will never know how frustrated i was when i was encountering the bootloop problem for the ENTIRE month.
my report thread - http://forum.xda-developers.com/showthread.php?t=1239063
my help-seeking in the darktremor thread which was answered by famous developer temasek - http://forum.xda-developers.com/showthread.php?p=17232233
my target was originally voyager the person but now its to all of you, please ignore my incorrect pronouns, if there are any
OH FINALLY i luckily found the very useful reference that i have read before!! after reading these you will understand everything
tobydjones said:
Some phones, eg the Desire, don't have enough internal memory (NAND). A2SD and other 'init.d scripts' fool Android into storing various things on the SD card instead of internal memory to free up space. They can move either apps, the Dalvik cache (a pre-compiled copy of each app) and/or app data. And they can move them to either the 1st (only) partition of the SD card (formatted as FAT or FAT32) or a 2nd partition of the SD card (formatted as ext3 or ext4).
As there's so many different scripts doing different things, I had to make a table to sort it all out. Please let me know if I've made any mistakes, or if you can answer any of my questions in italics.
script ................ apps . Dalvik . data .. comment
---------------------------------------------------------------------------------------------------------------
A2SD pre Froyo ........ SD ... int .... int ... Made to move app data to SD {or was it already ext?}
Froyo A2SD/"move to SD" SD<1>. int<9> . int ... Built in
Gingerbread A2SD ...... SD.... int .... <6> ... Built in. As Froyo but a bit more space.
apps2sd app (on market) ....................... App to make Froyo/Gingerbread "move to SD" easier, not a script
Force2SD (on market) .. ....................... As apps2sd + move system apps>SD {does apps2sd also do this?}
A2SD/AS2D+ (or apps2SD) ext<8> in/ex<2> int ... Various implementations<7> some move Dalvik (manual/auto)
Darktremor A2SD/DT-A2SD ext .. in/ex... int ... Move Dalvik. Used to be auto, now command line (or use A2SDGUI)
MIUI_Au PC-A2SD ....... ext .. ext .... int ... Allows android to boot if SD Card broken/removed. With logs
Link2SD (on market) ... ext .. ext .... <6> ... Moves apps individually
Sibere DATA2SD ........ ext .. ext .... ext<3>. Moves whole /data folder to ext for more space <4><5>
DATA2EXT .............. ext .. ext .... ext ... {another implementation of DATA2SD? how does it differ?}
data2whatever/DATA2WE . ext .. ext .... ext ... Can use ext2-4 plus variety of unusual filesystems eg B(RT?)FS
Notes:
<1> The SD card is mounted very late in the boot up process, so background apps and widgets won't work. Also apps on SD aren't available when SD card is used as a disk ('mounted')
<2> Dalvik on SD/ext may wear out SD card a bit quicker {not a big issue compared with int memory wearing out?}
<3> Data on ext wears out SD card faster because of data writes {how much of an issue is this?}
<4> Data2SD on Sense ROMS - possible corruption during battery pull or forced reboot
<5> Data2SD on ASOP ROMS - corruption when turning off phone due to unclean dismount {or is this fixed now?}
<6> GB doesn't move all of data, but does move app libs (/data/data/<appname>/Lib)
<7> There's a lot of confusion what AS2D, AS2D+ and apps2sd refer to, and the distinction between them, as those names been used for many things, including an app on the market! The + appeared after Froyo was released and often means the Dalvik cache can be moved (not always automatically)
<8> Unlike moving apps to SD, you can move widgets to ext, and apps are available when SD card is used as a disk
<9> If Dalvik cache is on int, number of apps is still limited as pre-compiled copy of each app held in cache
Updated 01/10/11. Thanks to rootSU, fllash & rmcsilva for corrections and additions
Click to expand...
Click to collapse
neoKushan said:
Ok, so here's the deal, in a very longwinded way that should hopefully explain everything and answer ALL questions.
You have an SD card in your phone and, a bit like normal PC Hard Drives, you can "partition" them (split them into two or more sections of different filesystems). Normally, your SD card is just one big FAT32 partition, which is fine for storing your pics, messages, emails, etc.
Now, other then your Phone's SD card, your phone will have its own internal flash memory (or "NAND") storage. Tradditionally with Android, you could only install applications to this NAND storage, you cannot install them onto your SD card. So if you have an empty 32GB SD card, but only 5Mb of internal phone storage, you still wont be able to install many apps, if any at all.
This was done to protect the apps from things like piracy - it's not easy to access the location where apps are installed on your phone's internal storage (normally impossible without root), so you can't for example buy an app, copy it, refund it, then install it again.
Still, this is no good for those of us who like to install lots and lots of apps, legitimately, as we run out of internal storage very quickly.
So Google came up with a way to install apps to the SD card. A folder is created called something like .android_secure and this stores (I believe) encrypted versions of applications, but there's a few catches:
1) Apps aren't automatically stored here, you have to manually "move" them
2) Not all apps are capable of being moved, in fact most apps aren't, the developer needs to update their app and allow it. Some apps aren't and wont be updated and some developers may not want to allow it for whatever reason.
3) Not all app data is moved, most of it is but some data is left on your phone so many people still run out of internal storage quickly.
4) You can force ALL apps to be moved to this area by default, but it breaks incompatible ones - such as Widgets, which are unable to load due to the SD card not being "prepared".
So that's Froyo's version. Before Froyo existed, some very clever people came up with a thing called "Apps2SD". Remember I said that your SD card normally is one big FAT32 partition? Well, Apps2SD works by having your SD card patitioned into TWO filesystems. A normal FAT32 partition for your usual stuff and a secondary "EXT" partition. EXT is just a filesystem, like FAT32 or NTFS, but it's the filesystem used by Android internally. The SD card is normally FAT32 because it's a "universal" filesystem, that just about any machine will be able to read, whereas EXT filesystems are generally Linux only, but I digress.
EXT has several different versions. The most common one you'll see is ext3. The main difference between ext2 and ext3 is "journaling", which is just a fancy way of saying that should an operation (such as copying, writing or reading) be interrupted unexpectedly (say, by you turning your phone off), then no data should be lost or corrupted. You know how when you turn your phone on, it says "preparing SD card"? It takes a few minutes, but what it's actually doing is checking that the FAT32 partition hasn't been damaged, because FAT does NOT have journaling. If you used a computer back in the Windows 98 days, you may remember that lovely blue "Scandisk" screen that had to run every time you didn't shut your computer down correctly - that's the same thing. But then Windows 2000/XP came along with NTFS, which also has journaling, meaning you had less chance of loosing data. But I digress once more.
So you have your SD card partitioned into EXT and FAT32. Generally it doesn't matter if it's ext3 or ext4, but you don't get any real advantage with ext4 over ext3 in this instance. Apps2SD then runs a special script on your phone which "symbolically links" the folder from your phone's internal storage where your apps are normally stored, to the ext partition on your SD card. A symbolic link is a bit like a shortcut for folders, except it's transparent to the OS: In other words, Android doesn't know that when it's installing it's apps to the internal phone storage, it's actually being stored on the SD card. This effectively boosts your internal phone memory from the previous 5mb that you had in my example above, up to whatever size you made the ext partition on your SD card (often 512Mb or 1Gb, but it depends on how many apps you install).
Plus, because it's "journaled", it doesn't need to be "prepared", meaning it's ready to go as soon as the phone starts - so your widgets and apps work immediately (unlike "forced" Froyo Apps2SD, where widgets disappear).
The catch with Apps2SD is that whatever space the ext partition takes up is taken away from the SD card. So if you have a 4Gb card (with something like 3.5Gb of actual storage) and you make a 512Mb ext partition, your SD card will "shrink" to 3Gb. The space isn't actually lost, it's just being used by the ext partition. If you reformat your card, you'll get it back.
Finally, there's a difference between "Apps2SD" and "Apps2SD+". Remember I said that your apps are stored on a special folder inside your Phone's NAND storage? Well, that was a bit of a lie. It's actually stored in TWO places. There's a second area which is called the Davlik Cache. You don't really need to worry about what this is for (Hint: IT's to do with the Java runetime your phone uses to run apps), all you need to know is that apps use it to store data, which also eats up internal phone memory. Apps2SD+ moves davlik cache to the ext partition on your SD card as well, freeing up even more space. Some people believe that this may come at the cost of performance, as the internal NAND memory should be faster than your SD card (Which is why you also get people arguing over which "class" SD card is better for Apps2SD - the logic being that a faster SD card means less impact from this move), but the truth of the matter is that your applications will be running from your Phone's RAM anyway, so performance isn't really impacted at all. Since most apps are only a few hundred Kb's in size, or a couple of MB at the most, it's a non-issue.
Finally, any recent version of Apps2SD/Apps2SD+ should work with an SD card that is or isn't formatted with an ext partition. It'll check for this partition when your phone first boots and if it's not there, just use internal phone storage.
Having an ext partition WITHOUT Apps2SD+ shouldn't cause any issues, either, so you can format your SD card whenever you're ready.
So in summary:
Apps2SD "fakes" your phone's internal memory and puts it all on a hidden section of your SD card.
Apps2SD+ pushes even more content to the SD card, freeing up even more space on the phone itself.
"Froyo" Apps2SD has various limitations that "old" apps2SD does not, but is much easier to handle as it doesn't involve any kind of "partitioning".
Click to expand...
Click to collapse
first, please consider the wording "app2sd+" used above can also be applied to "data2sd+" which should be the main purpose of this thread, because they are similar as they both use the sd-ext partition to store things. the only different is that app2sd+ only moves /data/app and dalvik cache but data2sd+ moves the entire /data partition
now based on my experience of how did i solve my bootloop problems even i install over 300 apps, is, not to integrate Froyo app2sd and app2sd+(or your data2sd+) then things will be fine.
as ive seen that voyager you have "moved all apps to sd" with froyo app2sd while you are TOGETHER using the script of app2sd+(or data2sd+). from the above explanation, your apps and data are now SHARED among /sd-ext and /sdcard/.android_secure which MAY lead to problems on our phones when it enters the process system after going through the bootanimation.
still remember the days and things we have discussed? it was in november when we first known each other i think my founding still applies to data2sd+
voyager20021 said:
For bootloops on Miks CM7 fist post he says
If you get bootloop or stuck at LG logo do next:
Sometimes Recovery can't format /system so you need to clear /system manually. You can do it with this zip (flash as always in recovery), or in mounts menu (clockworkmod recovery only), or with adb:
1. Mount /system in recovery.
2. adb shell rm -rf /system/*
You get 1 error. This is ok.
Will update if I found this bug.
Anyone tried that zip or adb fix? I am not so familiar with adb shell. The zip i think is incompatible or smth.
Franco, do you know if this has something to do with random reboots caused by moving too many apps to sd?
Click to expand...
Click to collapse
Miasmic said:
me.
that successfully wiped system partition and 2 months ago i did full wipe (including /system) and reinstall everything then do the same thing, and i got the same results - bootloop
please go to darktremor's main thread (nexus one dev forum) and scroll a few pages back, ive been yelling there for help and they did a lot to help me especially temasek(u know who? a famous n1 developer)....
but finally we got no conclusions trying everything, even switching to s2e had ****ed up my phone.
what solution i can tell is that
fk kernel + mik + dt a2sd script 2.7.5.2-1
+ apps staying on /EXT (shown "on phone")
= no problems
fk kernel + mik + dt a2sd script 2.7.5.2-1
+ apps staying partly on /EXT and partly on /android.secure (shown "on SD card")
= after booting (seen lockscreen) for about 3mins, the phone goes back to bootanimation and boot again
[im sure voyager is asking about this]
p.s. fk kernel + mik + dt 2.7.5.3 beta4
will result in LG logo stuck every 2 reboots. wipe /system no help.
hope my info is useful and yeah, take alook at the dt thread
until now the only solution is not to move apps partly to /android.secure
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
franciscofranco said:
Why move apps to sd card instead of /ext? doesn't make any sense............. No wonder **** happens...
Click to expand...
Click to collapse
Miasmic said:
Yea I agree with your point, moving the app only to /ext is apparently a safer method than dividing it into /ext and /android.secure
But however this method (using darktremor together with froyos a2sd feature) can save even more internal storage on our phones because darktremor doesn't move 100% of the "app" to /ext. Except "app data" , a small portion of "app" is also occupying the internal storage when using dartremor.
Say angry birds, despite its ~500kb /data size, when using darktremor, 18mb its "app" is moved to /ext while 2mb of it is staying in the internal storage. When using froyos a2sd feature, this 2mb is moved to /android.secure therefore even more internal space is free-ed.
According to the main darktremor thread, a user named bassmadrigal and even temasek himself, has stated that integrating darktremor "move to EXT" and froyos "move to FAT" does not produce any problems (at least on their nexus one) and can save even more space.
Well its not a problem for me as I only move 4 of my biggest apps to FAT and not having issues now.
I think voyagers attempting to move a lot of his apps (partly as they still partly stay at /ext) to /android.secure (as I tried before) and he got ****ed up like me before.
Hmmph I am not quite sure, voyager have you tried the same procedure (restore titanium and move them to FAT) without flashing Franco.kernel and only with the ROM (ans default kernel) and darktremor script installed? In that way we can see whether the "issue"(not at all but just an disadvantage of not supporting a feature) is about Franco's kernel or about our phones. cheers!!
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
franciscofranco said:
Just don't mess with the part that stays in the phone, if you do you're on your own, it's just too damn obvious to waste my time with it, sorry :/
Click to expand...
Click to collapse
Miasmic said:
yea, i definitely dont think it is of any priorities to request you to dig on this stuff and please dont, lol
was just telling my experiences to others and esp. voyager
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
yea, franco also said we shouldn't use the froyo app2sd function when we have already moved stuffs to the /sd-ext using app2sd+/data2sd+
therefore to prevent such abnormal behaviours on our phones we should treat our phones as Android 2.1 or before which does not have the capabilities to use froyo app2sd function to move things to /sdcard/.android_secure instead we should just let them be moved to the /ext partition.
i can confirm that yes there will still be decrease in internal storage because even you got data2sd+, there are something that cannot be moved from the internal storage to /sd-ext and we dont know what. JUST be fuxking sure that all your apps are stayed in "internal storage" (thats a way to fake the phone! you know) and they will be very safe in /sd-ext.
you may also like to install app2sd app but reverse the original concept of this app, i.e. to confirm NO APPS ARE EXISTING IN THE 2nd TAB (ON "SD CARD" with froyo function)
so, to test this out quickly, you may simply:
make proper partitions
wipe properly
flash rom
flash your a2sd+/data2sd+ script
boot phone
run the proper commands (for dt now i would dl a2sdgui and apply stuffs and let it reboot)
now restore titanium backup with INSTALL LOCATION set as "internal storage"
(in CM7 settings > application you may also choose "internal storage" to make sure everything is PURELY moved to /sd-ext instead of sharing among /sdcard/.android_secure with the froyo a2sd function) (however what i can tell you that this CM7 function is not working properly at least with my DT a2sd+ script therefore we have to double check whether it is in "INTERNAL STORAGE" when we install a new app) so now app2sd app came in handy remember is to reverse all apps to internal but not move them to so-called sd which was the original purpose of this app.
ok hope you understand what i meant and now you should not have bootloops
Under the hood
however, some users have reported that they have NO problems at all when they share their apps among /sd-ext and /sdcard/.android_secure. an example was bassmadrigal (located in the darktremor official thread)
maybe, it is phone specific. maybe, they have shared a less amount of apps as i myself can also confirm that the bootloop problems only occur if we SHARE A CERTAIN AMOUNT OF APPS among the two places.
and for your safety, at least to first eliminate the bootloops problems before doing any experiments, still follow the above and MOVE ALL OF THEM TO so-called "INTERNAL" (pure /sd-ext)
so you mean to say that keep all the apps in internal memeory and it will be safe in sd-ext with any a2d script rather than moving into sdcard?
There is one script i am tryingvhttp://forum.xda-developers.com/showthread.php?t=1342387. I dont have any script installed.But it is still giving me bootloops.
williamcharles said:
so you mean to say that keep all the apps in internal memeory and it will be safe in sd-ext with any a2d script rather than moving into sdcard?
There is one script i am tryingvhttp://forum.xda-developers.com/showthread.php?t=1342387. I dont have any script installed.But it is still giving me bootloops.
Click to expand...
Click to collapse
yes, the message i would like to bring is rather simple and easy but most of the users are confused about "move to ext" and "move to FAT" and the BUTTON in the application manager of our phones show "MOVE TO SD" which is moving PART of the app to SD-FAT (android.secure) so they are now SHARED and will produce PROBLEMS.
This important point is what most of the script developers have forgotten to warn their users.
Remember to check your settings and ROM/kernels/partitions/scripts compatibility with each other before regarding the script solely as the cause of any problematic behaviour (best way to prove is to see whether there are someone using the same combination without problems
then, install the script, and start installing apps only into "internal storage" (to fake your phone as they actually goes to /sd-ext) and NEVER EVER touch the button "Move to SD" in the application manager then you should be fine as said in my first post, double check they are in the internal storage after you have grabbed a new app from market it will be fine to move it back to "internal storage" as long as you havnt reboot the phone.
Miasmic said:
yes, the message i would like to bring is rather simple and easy but most of the users are confused about "move to ext" and "move to FAT" and the BUTTON in the application manager of our phones show "MOVE TO SD" which is moving PART of the app to SD-FAT (android.secure) so they are now SHARED and will produce PROBLEMS.
This important point is what most of the script developers have forgotten to warn their users.
Remember to check your settings and ROM/kernels/partitions/scripts compatibility with each other before regarding the script solely as the cause of any problematic behaviour (best way to prove is to see whether there are someone using the same combination without problems
then, install the script, and start installing apps only into "internal storage" (to fake your phone as they actually goes to /sd-ext) and NEVER EVER touch the button "Move to SD" in the application manager then you should be fine as said in my first post, double check they are in the internal storage after you have grabbed a new app from market it will be fine to move it back to "internal storage" as long as you havnt reboot the phone.
Click to expand...
Click to collapse
Miasmic said:
yes, the message i would like to bring is rather simple and easy but most of the users are confused about "move to ext" and "move to FAT" and the BUTTON in the application manager of our phones show "MOVE TO SD" which is moving PART of the app to SD-FAT (android.secure) so they are now SHARED and will produce PROBLEMS.
This important point is what most of the script developers have forgotten to warn their users.
Remember to check your settings and ROM/kernels/partitions/scripts compatibility with each other before regarding the script solely as the cause of any problematic behaviour (best way to prove is to see whether there are someone using the same combination without problems
then, install the script, and start installing apps only into "internal storage" (to fake your phone as they actually goes to /sd-ext) and NEVER EVER touch the button "Move to SD" in the application manager then you should be fine as said in my first post, double check they are in the internal storage after you have grabbed a new app from market it will be fine to move it back to "internal storage" as long as you havnt reboot the phone.
Click to expand...
Click to collapse
Much simpler explained. We'll have to test your theory. Only now i use ungaze's script which is something like "everything2sd". The button reading move to sd or move to internal has no influence at all. And still having bootloops at some point. Only now the sd ext is 2Gb max, though it never got to fill it without that damn bootloop.
Thanks again MIASMIC for addressing one of the biggest remaining problems which keep us away from having a PERFECT AND COMPLETE O1, now when we are close to having the stable official CM7 and official or not CM9 which will bring so many and awsome STABLE ROMs based on those 2.
i often have this problem: There is an app2sd-gui DT script included in the rom... and this automatically places apps to the fat partition on the sd card ..
now, i always partition my sdcards with a second ext4 partition and prefer to use that one as an sd-ext directory and use linking to place my apps and all the stuff on my sd.
This allows me to use virtually unlimited storage and keep my internal memory completely free... (i also have a htc wildfire with CM7 and this setup; there i have about 70 apps installed. the internal memory has about 10 MB in use with some files i really wanted to have there so they always start fast like go keyboard, go contacts ex and my ringtones / alarm sounds. All other files are on my 16 gb sd card)
With a lot of the roms i've been trying i just can't get this working on my galaxy ace... especially the ICS roms i can't see my EXT4 partition as /SD-EXT for some reason, but often it gets mounted as /System/SD and thus link2sd cannot use my second partition.
Especially if app2sd is builtin as a system app this seems to be a problem. Has anyone ideas on how i could get this working again with these roms?
BoGy1980 said:
i often have this problem: There is an app2sd-gui DT script included in the rom... and this automatically places apps to the fat partition on the sd card ..
now, i always partition my sdcards with a second ext4 partition and prefer to use that one as an sd-ext directory and use linking to place my apps and all the stuff on my sd.
This allows me to use virtually unlimited storage and keep my internal memory completely free... (i also have a htc wildfire with CM7 and this setup; there i have about 70 apps installed. the internal memory has about 10 MB in use with some files i really wanted to have there so they always start fast like go keyboard, go contacts ex and my ringtones / alarm sounds. All other files are on my 16 gb sd card)
With a lot of the roms i've been trying i just can't get this working on my galaxy ace... especially the ICS roms i can't see my EXT4 partition as /SD-EXT for some reason, but often it gets mounted as /System/SD and thus link2sd cannot use my second partition.
Especially if app2sd is builtin as a system app this seems to be a problem. Has anyone ideas on how i could get this working again with these roms?
Click to expand...
Click to collapse
You have to edit the a2sd-script wich should be located in /etc/init.d/
But using "Link2sd" would be much easier. It is a well structured app and the usage is simple, because the first time (when you open the app) you have to choose your partition and the mountscript will be created automatically.
You can get Link2SD from this xda-thread or the play store
BoGy1980 said:
i often have this problem: There is an app2sd-gui DT script included in the rom... and this automatically places apps to the fat partition on the sd card ..
now, i always partition my sdcards with a second ext4 partition and prefer to use that one as an sd-ext directory and use linking to place my apps and all the stuff on my sd.
This allows me to use virtually unlimited storage and keep my internal memory completely free... (i also have a htc wildfire with CM7 and this setup; there i have about 70 apps installed. the internal memory has about 10 MB in use with some files i really wanted to have there so they always start fast like go keyboard, go contacts ex and my ringtones / alarm sounds. All other files are on my 16 gb sd card)
With a lot of the roms i've been trying i just can't get this working on my galaxy ace... especially the ICS roms i can't see my EXT4 partition as /SD-EXT for some reason, but often it gets mounted as /System/SD and thus link2sd cannot use my second partition.
Especially if app2sd is builtin as a system app this seems to be a problem. Has anyone ideas on how i could get this working again with these roms?
Click to expand...
Click to collapse
sd-ext is for CYANOGENMOd only...in stock based rom's u wont find a sd-ext..so s2e wont work.... but charmingly link2sd works....
now if it isn't working what shall u do???
-- if it says mount script not created,, partiotion is busy,,,, reflash the rom or i tried flashing another rom on wich link2sd worked and then reflashing the rom u want... install link2sd apk.. choose ext4 partition reboot.... (it works u can switch from cm7 to stock it wont be a problem)
- if ur sd-ext partition is of ext3 type,,, still choose ext4 on link2sd partition type screen
Fly-High said:
You have to edit the a2sd-script wich should be located in /etc/init.d/
But using "Link2sd" would be much easier. It is a well structured app and the usage is simple, because the first time (when you open the app) you have to choose your partition and the mountscript will be created automatically.
Click to expand...
Click to collapse
I always try to use links2sd; but if app2sd(gui) is installed it won't work.
I'd like to edit the init.d 'mount' script, but i don't know how to open thiis since it always says it cannot be found when i try to open it for editing or even for reading.
(i'm trying to open it with an app that has SU rights like Total Commander)
i have some experience with android and installing custom roms ; but i don't have real experience with editing files in a live OS.
Or should i edit the files in the APK before installing it? (isn't this going to break the APK's CRC-key rendering the file unusableN)
I already thank you guys for reading and sharing your knowledge...
I found it
I could edit the mountsd file in the original ZIP (which is not a crc'ed APK )
then reflash my device.
I removed everything in the mountsd file except this;
Code:
#!/system/bin/sh
#
# mount ext partition from sd card
(so this is what's left)
then i installed S2E & Link2SD, i let link2sd initialize it's scripts and pataboom; i got access again after the next reboot of my device ... finally i have a galaxy ace with unlimited space (or at least kinda limitless compared to the 120mb you get)
i was so used to the big space since it worked like a shine on my htc wildfire (like 60+ apps and only a few mb in use by some apps i really wanted on the internal memory so they start up fast anytime (no interference when other apps are running/starting).
I really love link2sd since it allows you to put apps on external memory and still use the widgets/services/.... while app2sd can't do that
thx again for your help guys! (although i did a lot of fo the job myself too
Hi guys, so I've got this tablet for free with my new contract and I want to root it to play a bit with it . Do you guys have any idea how to do it ? I haven't managed to find any tutorials on the web .
Vonino Onyx QS root request
+1 on this issue.
I too have a Vonino Onyx QS tablet running on Android 4.4.2. The device is decent enough, but storage management is awful! Despite being advertised as an 8 GB tablet in terms of storage, the Onyx QS runs aground at about 900 MB of installed apps (including related data and cache) and starts yelling that there is "Insufficient storage available". This renders the tablet virtually unusable after installing just a few essential apps. Emails stop working, apps will no longer update and data-intensive apps such as Google Earth will simply refuse to run. The 32 GB external SD card I've added makes no difference. It's almost like the OS has no clue what to do with it.
I suck at Android. However, after a lot of digging for pieces of information I've come to undersand that these devices use separate partitions for the apps and other files. Some folks have also hinted towards the fact that the puny 0.9 GB app partition can be resized on a rooted device by means of a partition management app. Or apps could at least be moved to the SD card right before their installation (making use of an app such as Link2SD and, again, a rooted device).
This bring us full circle back to the OP's request: could someone please create and explain a rooting method for this tablet?
Just so you know, these are fresh screenshots of this fresh factory reset configuration. Thought it would fix the problem, but it didn't.
SilentGTX said:
Hi guys, so I've got this tablet for free with my new contract and I want to root it to play a bit with it . Do you guys have any idea how to do it ? I haven't managed to find any tutorials on the web .
Click to expand...
Click to collapse
Muravey said:
+1 on this issue.
I too have a Vonino Onyx QS tablet running on Android 4.4.2. The device is decent enough, but storage management is awful! Despite being advertised as an 8 GB tablet in terms of storage, the Onyx QS runs aground at about 900 MB of installed apps (including related data and cache) and starts yelling that there is "Insufficient storage available". This renders the tablet virtually unusable after installing just a few essential apps. Emails stop working, apps will no longer update and data-intensive apps such as Google Earth will simply refuse to run. The 32 GB external SD card I've added makes no difference. It's almost like the OS has no clue what to do with it.
I suck at Android. However, after a lot of digging for pieces of information I've come to undersand that these devices use separate partitions for the apps and other files. Some folks have also hinted towards the fact that the puny 0.9 GB app partition can be resized on a rooted device by means of a partition management app. Or apps could at least be moved to the SD card right before their installation (making use of an app such as Link2SD and, again, a rooted device).
This bring us full circle back to the OP's request: could someone please create and explain a rooting method for this tablet?
Just so you know, these are fresh screenshots of this fresh factory reset configuration. Thought it would fix the problem, but it didn't.
Click to expand...
Click to collapse
try with Kingo ROOT. You do it at you'r own risk.
Successful rooting of Vonino Onyx QS tablet
Paget96 said:
try with Kingo ROOT. You do it at you'r own risk.
Click to expand...
Click to collapse
Hi, Paget96! Thank you so much for the solution!
I'm writing this to let you, the OP and everybody else know that Kingo Root did it! I have succesfully rooted the tablet and the process itself was quick and merely a matter of installing the software on my PC, connecting the tablet via USB and clicking my way through.
Afterwards I installed Link2SD Plus to manage the transfer of apps from internal storage to the external SD card (32 GB in my case). The app is dirt cheap and truly what you need, because the free version does not allow you to move app data, only the app itself and its libraries. As I've come to know, data and cache build-up is what ends up killing storage space.
Before installing Link2SD however, one must prepare the SD card by means of a partitioning program. Highly recommend you do this via card reader on an actual PC. Use MiniTool Partition Wizard, it seems to be very popular these days. Delete whatever's already on the card and make two PRIMARY partitions: the first one will be FAT32 and will store the media you consume (like music, photos, videos etc.), while the second partition has to be ext4 (ext2 did not work for me on this tablet) and will hold the apps and their data. You can go ahead and name them "Media" and "Apps" respectively to avoid confusion. Remember: both must be primary partitions, the first one is FAT32 for media, the second is ext4 for apps. I made my app partition 10 GB big. Overkill, you say? Hey, I'm done with insufficient storage space errors, ok? :silly:
While you're at it, you might want to add a third partition for swap space to add more RAM to your device. There are tutorials for it on the web.
Once you're done formatting the card, reinstall it in the tablet, open up Link2SD and choose ext4 at the script mounting prompt. From there on, moving apps from internal to SD card space should be intuitive.
Prior to all this fiddling I suggest you perform a factory reset on your device so you can start clean. Can't tell you anythihg about custom ROMs or stuff like that because I didn't have a need for them. This thing works fine apart from that silly storage limitation.
Phew! I can finally enjoy using my tablet... :fingers-crossed:
Muravey said:
Hi, Paget96! Thank you so much for the solution!
I'm writing this to let you, the OP and everybody else know that Kingo Root did it! I have succesfully rooted the tablet and the process itself was quick and merely a matter of installing the software on my PC, connecting the tablet via USB and clicking my way through.
Afterwards I installed Link2SD Plus to manage the transfer of apps from internal storage to the external SD card (32 GB in my case). The app is dirt cheap and truly what you need, because the free version does not allow you to move app data, only the app itself and its libraries. As I've come to know, data and cache build-up is what ends up killing storage space.
Before installing Link2SD however, one must prepare the SD card by means of a partitioning program. Highly recommend you do this via card reader on an actual PC. Use MiniTool Partition Wizard, it seems to be very popular these days. Delete whatever's already on the card and make two PRIMARY partitions: the first one will be FAT32 and will store the media you consume (like music, photos, videos etc.), while the second partition has to be ext4 (ext2 did not work for me on this tablet) and will hold the apps and their data. You can go ahead and name them "Media" and "Apps" respectively to avoid confusion. Remember: both must be primary partitions, the first one is FAT32 for media, the second is ext4 for apps. I made my app partition 10 GB big. Overkill, you say? Hey, I'm done with insufficient storage space errors, ok? :silly:
While you're at it, you might want to add a third partition for swap space to add more RAM to your device. There are tutorials for it on the web.
Once you're done formatting the card, reinstall it in the tablet, open up Link2SD and choose ext4 at the script mounting prompt. From there on, moving apps from internal to SD card space should be intuitive.
Prior to all this fiddling I suggest you perform a factory reset on your device so you can start clean. Can't tell you anythihg about custom ROMs or stuff like that because I didn't have a need for them. This thing works fine apart from that silly storage limitation.
Phew! I can finally enjoy using my tablet... :fingers-crossed:
Click to expand...
Click to collapse
10gb is too big, you will broke your sd.
Better use 512mb.
Paget96 said:
10gb is too big, you will broke your sd.
Better use 512mb.
Click to expand...
Click to collapse
Could you expand on that one, please? Why am I at risk of ruining the SD card?
Muravey said:
Could you expand on that one, please? Why am I at risk of ruining the SD card?
Click to expand...
Click to collapse
Brcause sd work without stop, that is not good.
SD prob
Hi, i have the same tablet ... and i managed to root it ... but i cant manage to increse the storage . l've done the exact stepts ... installed micropartition deleted my sd card (2gb micro sd samasung) i did the first partition fat32 primary with a size of 800 gb and when i try to make the second one ext4 the program says that windows cant see the second partion on a removable device but i continuued anyways ,,, and created the second one with ext2 and then with ext4 as primary ... my windows and my tablet cant see the second partion ... need a little help ... thx
I heave installed the drivers, and nothing happens. Its not connecting to my pc. I changed the pc too. I heave the error: Unfortunately, Mobile data has stopped. I tryed to repair this with recovery -- Wipe data, factory reset. Not working.