Database Develop

Low Internal Memory - SMS Warning too

I was surprised to see my wife's N1 only had 20 MB of internal memory. She is running Enomther's Rom, which runs great.. I don't think the issue is tied to that.
She has hardly any apps on her phone, and rarely does anything other than work emails (Touchdown) and Facebook/Twitter.
Considering how little she has on the phone, and how little she does with it I, was just really shocked that she would have so little internal memory. She called me just now and stated she has a notification that she missed a text message because she did not have enough memory.
What the heck could be taking up so much memory?
What's the fix? There isn't really anything to delete (that I'm aware of)....
Search seemed helpess with "internal" and "memory" there were WAY too many posts. Please help if you can!

Browser cache might be huge, if she has many sites opened in many browser windows.
Her "not many" apps might be "many" enough for a phone with limited internal memory like Nexus - having ~200MB for apps, data and cache together.
There are exactly 3 solutions:
1) Keep browser in check. It's always a good practice.
2) Use native Froyo method and move apps to SD.
3) Use Apps2EXT method and move apps to SD. You can also move Dalvik-cache to /cache.

Hmm, she has MAYBE 10 apps?
I downloaded a cache cleaner and ran that, it removed maybe 8 MBs? That was this past weekend, and she got that message about low memory today. I doubt she has even opened the browser since then to be honest. Very light user.
I sent enomther a tweet, his reply was:
RT @enomther @CallipH need to implement either dalvik-cache-2-/cache or apps2ext in SpareParts (DataStorage options) ... sysdc-2-/cache is default on cm6
okay, so option 1 is to move dalvik cache to sd, which I think you do in Advanced > Amon's recovery, right? Any ill effects from doing this if I switch roms?..
Option 2, apps2ext... she does not have an ext partition and frankly surprised this is needed... is the nexus that low on memory? My Vibrant has 1.6 GBs. same question, any ill effects if moving to another rom with the apps on the ext? I did that a lot back in the day with the G1. I remember having some issues and having to do fix permissions a lot.
Thanks for all the help man.

Check, what's using the memory. Just go over the apps.
You can't do Dalvik-to-SD, because it requires EXT partition, which you don't have. You can do Dalvik-to-Cache.
There is no hassle in having apps on EXT whatsoever. The only hassle is getting them there.
ROM has nothing to do with application data usage either.

Have you tried wiping the Dalvik cache? Worth ago in case there's some built up crap I spose.

^^ thanks.
^ I did before flashing the rom. Will do it again.
I know it's relative, but how much internal memory would you expect someone to have when they just have about 10 apps?

Depends on the apps. I can count 2 - Google Earth and Motonav, for example - that take together 50MB of space without even counting the cache part. Another 4 apps like that, and you're out of memory (if you don't move them to SD using Froyo's method or old Apps2SD-EXT method).

There's also numerous games that are > 10MB, can easily add up.

I'm curious if Touchdown (Exchzange work email) is doing something funky... I know the apps on her phone and they are all very small. Thank you guys all for the posts.
I think I may format her card and partition it and move the cache to the ext partition and see what her memory looks like after that.
Any issues you guys can think of with that, or other ideas?

Download DiskUsage, and it will give you a good idea of what the problem is...
Sent from my Nexus One using XDA App

can we increase the size of /datadata on cm7 with a symlink?

throughout the time ive spent with my captivate i have seen more people saying they are having issues with this /datadata folder getting too full on the root of the cappy when running cm7 than anything else (except BLN but thats not a true issue as much as a feature request of many) and i was wondering if there was any way i could increase the size of /datadata? is there any way we could rally together and get the size increased by the cm team themselves? if this /datadata folder getting low on space hadnt caused most of the problems i have read of people encountering with cm7 i wouldnt have made this thread.
but basically what im talking about is this:
1. new cm7 user installs the rom
2. they comment about how awesome and smooth it runs and how its better than anything, and "how could i have waited so long for this" type statements
3. they install all their user apps, generally not even close to enough to fill up the phone's "internal storage"
4. they come to the cm7 nightly or rc threads and make a post about force closes, lag, performance complaints, market download issues, or whatever random problem the tiny /datadata folder has caused them to experience
5. 1-4 people tell them about the /datadata folder needing more room to wiggle in and everything is fine after that
if there was some way to increase this mysterious (and entirely too small) /datadata folder's size then we could stop the steps above at 3, and to my knowledge the system doesnt act the same way on samsung roms, therefore a developer for samsung knows how to make the /datadata location work differently, or better in some way. if there is a partition specifically for that folder then i would like to know how to make it larger without screwing up the rest of the phone (i.e. making caches too small can cause market issues and such nonsense)
does anybody else have any information to add to this? if so please let me know to update the OP because i would enjoy how clean the threads will be, how well cyanogen will work out of the box, and not having to relay the same information repeatedly because some just simply will not use the search function to find one of the dozens of users experiencing the same problems in the threads they are posting in.
I know there has to be some way because no other phone i have used has acted this way, and no other rom, thus it is a 100% fixable and do-able thing. if anybody can do it its those here on xda so i figured i would post this to try and get the development needed for the fix going strong.
I know very little about these things honestly, but i do know some and i shall contribute as much as i can

Shame, shame. You know better than posting something for Q&A in Development.

This sounds like something a bounty should be started for.
Sent from something from somewhere

Shell Script?
Would it be possible to create some kind of script that can run periodicly that can empty the /datadata folder?

n0r4d said:
Would it be possible to create some kind of script that can run periodicly that can empty the /datadata folder?
Click to expand...
Click to collapse
You can format datadata from CWM in recovery mode, so maybe tell the CM7 kernel to format it on startup... Just a thought.

[Q] Nexus one flash partition layout, lowest 63MB...

I've been trying to recover some space on my Nexus one and have been largely successful in doing so with a combination of tricks, but while looking at my partitions and tallying up the numbers something didn't seem to be adding up right; the unit is supposed to have 512MB flash, but I was coming up about 60MB short.
I found this thread which discusses the partition layout of the N1; the sizes they show all seem to match up well with what my device shows. Now, the hex address of the end of the last partion (user data) ends just a couple MB short of 512MB; the start of the first partion (misc) however seems to start over 60MB into the memory space... is there a reason for this, and if so what's occupying those lowest 63.75MB of flash space?

Baseband, AKA "radio", is what you're looking for. Unless you want your Nexus not to boot anymore, it's not advisable to try and repartition baseband space.
Instead of working hard and uselessly wasting effort, use A2SD or any other kind of linking to SD-mounted EXT partition. No matter what you try, Nexus doesn't have nearly enough internal space for any common use.

That answers my question, thank you.
As I mentioned in my original message, I was successful in freeing enough space on my device; a combination of moving apps and libraries (copy to system/lib and symlink back to original location) into the system partition and clearing out bulky or unnecessary apps has left me with over 60MB of free data space without even having to resort to fancy A2SD business (just normal android move to SD card). I was simply curious about what was filling in the remaining space on the flash chip and the radio pretty much fits the bill.

As someone with pretty average amount of user apps (a bit less than 100) and 700 MB user space taken, I can't see the point in doing what you mentioned for anything but pure fun. But if that suits you - I won't argue.

Well, by my app drawer I'm sitting at ~125 (44 purely in data, 34 moved to SD with standard android method, rest either native system or moved there) apps, and if my "puny" N1 can have 60MB free and not even need ext-style A2SD I'm not quite sure how the N1 doesn't have "nearly enough internal space for any common use". Seems to me the point (not "pure fun" as you dismissively imply) of doing what I've done is to able to keep using a pretty decent phone that still has more than enough storage space if you make the least bit of effort to manage it.
But hey, who am I to judge if you prefer to buy whatever latest phone the carriers tell you you should want every 12 months just so they can cram more bloated apps on it?
I appreciate the answer to my initial question about what's using the lowest block of flash storage (I was simply curious about what was using it - I couldn't find information if it was flash overprovisioning or some other low-level portion of the OS using it), but I don't really appreciate the unnecessary negative attitude and commentary for what was just a simple question. Thanks anyways.

I guess you didn't understand my point(s). I'll elaborate:
First and foremost, my point is this: N1 is a crap of a phone. Having it for over 1 year, and trying to adapt it to my wife for 3 or 4 months later on before giving up on it, taught me that this phone can't be dealt with by anyone who doesn't want to accept its touchscreen limitations. It was so refreshing having the phone (MT4G in my case) just react without fuss and not expecting it to crap out at any given time - not even mentioning the huge speed-up. The price of "upgrade" (selling the N1 and buying any previous-generation phone, like DHD/MT4G/DS/DZ) can be brought down to as low as $50, and the benefits are huge, I already wrote it a couple of times on the forum.
To the storage point (actually, several points):
N1's NAND is painfully slow, compared to anything, even to regular Class 2 SD card. You can try copying any large file from NAND to EXT and back, from NAND to NAND and from EXT to EXT and see what takes more time. You're likely to discover that A2SD actually adds performance instead of hurting it.
My app data (/data/data/*) alone takes roughly the same space as your whole internal /data storage has, so I guess the amount of apps alone isn't that meaningful of a measurement. I still call it a perfectly normal and average data usage - I don't have anything special installed, no heavy games that save 200+ MB of data on internal memory, just apps like Goggles, Flash, iGO and a couple of other big apps that aren't movable by normal means (and tend to crap the system out when they're forced to move). The problem in your approach is not even the one-time amount of work you had to invest to make that space, but the amount of work you'll have to invest to keep the phone running - moving system updates to /system upon every update, clearing browser cache, etc - generally, keeping things in constant check. Free time is something you learn to appreciate when you don't have enough, and more hassle-free setup is always preferred IMHO.
But again, different people have different needs, so while I can post my point of view - I don't argue with yours.

Thank you for elaborating, actually; it clarifies much that was not apparent in your earlier posts. This thread isn't really about the pros and cons of the N1 so all I'll say is that the advantages of the N1 (small size, OLED, build quality, tricolor trackball LED, etc..) still outweigh its manageable downsides for me, even compared to very modern handsets - so I'll stick with it until I can find a suitable upgrade that I'm happy with (is it so hard for HTC to make a <=4" qHD AMOLED? Seriously...).
Your point about the NAND being slow is interesting; this is something I hadn't heard and will have to benchmark; if it pans out it would be a point in favor of A2SD, but not really in favor of replacing the device over it
The upkeep I don't find that bad; Titanium backup makes integrating updated system apps a single touch for the batch, and I've only got a couple libraries symlinked into system that are unlikely to be frequently updated. With the space I've freed I shouldn't need to clear browser caches nearly as often - so it actually saves me time and frustration regularly for the one-time effort.
Thanks again for taking the time to reply and to clarify your points

If a2sd+ doesn't work for you you could do custom mtd partitions like I did using fireats custom mtd if u google it u will find it basically you can shrink ur system partition down to almost half because it is being wasted I mean whatever size u want to define it as. I'm using miui and my system partition that i defined is 120 mb (4 mbs are free just in case) and my cache partition is 15 mb. Now that leaves 301 mbs free for user data. I have 107 user apps installed about 10 games or so and I still have 120 mb free for user data for me that's more than enough. This way ur phone won't be buggy because u will only use the system partition for ur rom again I would suggest miui since it takes minimal space and is very smooth and stable with amazing battery life (I use tiamat kernel). Hope this helped
---------- Post added at 06:57 PM ---------- Previous post was at 06:52 PM ----------
Oh if u use a2sd in conjunction with custom mtd then u can have close to 750 mb of space available for user data given that ur sd ext partition is 512 mb (which was stable for me using 8gb card) that's basically rivaling new phone memory so don't just call the nexus one off just yet it can surprise anyone that knows how to play with it or stuck with it for 2years like me lol.

I've already been using root access with shell and titanium backup to move apps and libraries into the system partition without resizing it, so I'm already using the available space there. The only major difference is you've dramatically shrunk your cache partition from the default of (IIRC) 100MB down to 15MB; this seems like a pretty huge reduction, and I feel this would have performance implications, especially when running larger apps...
Other than that, if I find my current space as set up proves to be inadequate in the future (it seems just fine for now) then a2sd appears to be the best option for those who need even more additional space on a nexus one.

15 mb is more than enough for cache partition unless u plan to download huge 3d games and as we all know gaming isn't the reason that we have held on to nexus one for so long I haven't seen any app large enough to not install due to my partition size. I messed around with that too first I had it set at 5 mb but that made market force close every time then I set it at 10 was stable but large apps couldn't download and then I tried 15 and hasn't given me a single problem. Otherwise all that space is wasted so why not dedicate it to user data? With 20 mb partition u can download almost all games that can function on nexus one but since I'm not a big mobile gamer I stuck with 15 mb cache.

Most normal programs don't use /cache.
To fix your cache market issue:
Code:
su
busybox mv /cache/download /sd-ext/download
ln -s /sd-ext/download /cache/download
If you don't have a sd-ext you could use /sdcard/download instead. The directory will already exist if you've downloaded anything from the browser, so I just remove /cache/download before linking. I used to get package file invalid errors from this setup though...
Ti backup will also let you move stuff to /system and re-odex your rom instead of shrinking /system. Sure, everytime system stuff updates you need to click a few times, but unless space is real tight, it works fine. The re-odex-ed rom seems to boot faster for me than with external dalvik-cache, too, but that could just be me pretending. I've never busted out the stop-watch.
I like to keep apks on a2sd and put dalvik-cache on internal memory. It's kinda like raiding the two interfaces together to get the sum of the bandwidths of both when launching a program.
siberx: I'm sticking with the N1 until I find a decent phone that has been designed to fit in my pocket instead of sitting in a purse or on the bar too... I considered the glacier for a while, but, near as I can tell, the only benefits of going there are better touch screen and gpu.

I used firerat's mtd patch to rejigger my girlfriend's desire paritions to something more sensible (something like a 230mb system partition stock? ridiculous!) and that worked smashingly; the same trick against my N1 didn't go so well though. Seems like my Nexus with CM6.1 on it is still using the cache partition for dalvik at least partially, and I think shrinking it down to 20mb made it too small to boot right. Not a big deal anyways; I've got enough space to work with as is
I tried to do some benchmarks on my internal flash for comparsion, but the only decent benchmark I could find (without getting manual about it on command line) was Passmark's mobile benchmark; problem is they wan't 90MB free to run the internal memory benchmark, so my 60MB isn't cutting it for that
Anybody know of a decent benchmark that will bench both internal and SD read/write speeds that doesn't need such a huge chunk of free space?
ezdi: I considered for awhile buying a G2 for the faster CPU/GPU and improved touchscreen, but ultimately decided against it due to the extra weight and thickness (combined with the nexus' other advantages like OLED and tricolour LED). Eventually some manufacturer will figure out there's a still a market for compact high-end phones...

ezdi said:
siberx: I'm sticking with the N1 until I find a decent phone that has been designed to fit in my pocket instead of sitting in a purse or on the bar too... I considered the glacier for a while, but, near as I can tell, the only benefits of going there are better touch screen and gpu.
Click to expand...
Click to collapse
Better touch screen is a reason enough by itself.
GPU, much faster and bigger internal memory (both system and data), much faster and bigger RAM, and most of all - 90% HW-compatibility to one of the most popular devices in the world (DHD) - means staying updated and speedy with ROMs that fly where they crawl on Nexus (if they exist at all). Plus - all ROMs besides ICS are 100% functional, CM, MIUI, Sense 3/3.5, you name it. And if it's not enough, 20% hassle-free overclock is standard.
From quite satisfied Glacier owner.

[q] sd-ext s2e

Hello all. I have problem with my sd-ext. What i mean. It happend with 2 different ROMs. Yesterday with CM9 and today with Apocalypse. All works ok till i use S2E. I checked in S2E option Mount as ext4, reboot, checked move apps to sd-ext and all gone. No have them and system looks like after reinstal - fresh. Inn app manager apps are but only as browser.dolphin.firefox.opera... or com.sygic.aura. But they are invisible in drawer. What i am doing wrong. How to move safetly to sd-ext without that problems. Help!

try darktremors app2sd

But i want to know what heppend... It is S2E fault or sd-ext sth wrong?

Wojtys said:
But i want to know what heppend... It is S2E fault or sd-ext sth wrong?
Click to expand...
Click to collapse
I tried S2E today, and it did not work. Looks like undocumented rubbish to me.
I tried moving only the Dalvik cache, but after I activated that function and rebooted, all the settings but the last were greyed out, so I could not even undo what the piece of garbage had done.
Another point is that it has a setting allowing you to choose between ext3 and ext4. This is stupid, because the normal user cannot possibly know what to choose there. He cannot know whether his ext partition is ext3 or ext4, because the most common recovery, Clockworkmod, has no such choice in its SD card partitioning function. If the program itself cannot find out, how can the user? It is not even clear what the setting actually does.
So we keep wading through the idiot swamp, until somebody writes a usable program and documents it properly, if a really good program needs documentation at all.
My general advice is, look carefully at a program. Check its settings. Check its documentation for quality and completeness. As soon as you spot the first sign of madhouse style, drop it like a hot potato and look for something better. There are too many garbage programs around these days to waste our time with.
If you cannot find any that fulfills the minimal requirements for decent software, give up on the apps-to-ext idea. Buy a phone with more internal memory, if you have money to spare, or delete the programs you can do without.
The minimal requirement for an apps-to-sd program would be that it can cleanly move installed programs to the ext partition and back. Since you may have installed too many programs to move them all back, I would think that the program should help you to uninstall enough programs to make the rest fit, if you have to move them back.

hgmichna said:
I tried S2E today, and it did not work. Looks like undocumented rubbish to me.
I tried moving only the Dalvik cache, but after I activated that function and rebooted, all the settings but the last were greyed out, so I could not even undo what the piece of garbage had done.
Another point is that it has a setting allowing you to choose between ext3 and ext4. This is stupid, because the normal user cannot possibly know what to choose there. He cannot know whether his ext partition is ext3 or ext4, because the most common recovery, Clockworkmod, has no such choice in its SD card partitioning function. If the program itself cannot find out, how can the user? It is not even clear what the setting actually does.
So we keep wading through the idiot swamp, until somebody writes a usable program and documents it properly, if a really good program needs documentation at all.
My general advice is, look carefully at a program. Check its settings. Check its documentation for quality and completeness. As soon as you spot the first sign of madhouse style, drop it like a hot potato and look for something better. There are too many garbage programs around these days to waste our time with.
If you cannot find any that fulfills the minimal requirements for decent software, give up on the apps-to-ext idea. Buy a phone with more internal memory, if you have money to spare, or delete the programs you can do without.
The minimal requirement for an apps-to-sd program would be that it can cleanly move installed programs to the ext partition and back. Since you may have installed too many programs to move them all back, I would think that the program should help you to uninstall enough programs to make the rest fit, if you have to move them back.
Click to expand...
Click to collapse
Undocumented rubbish? What? The app or ur brain? You cant just call an app like that just because you cant make it work. Alot of users have been using it without problems.
Sent from my GT-S5830 using xda premium

Shadow xD said:
Undocumented rubbish? What? The app or ur brain? You cant just call an app like that just because you cant make it work. Alot of users have been using it without problems.
Click to expand...
Click to collapse
What exactly do you mean by, "make it work"?

S2e moves all non System apps to SD-ext. So, it will move itself to SD-ext aftwr reboot. This means the SD-ext won't be mounted at boot, and non System apps won't be accessible after boot (even if their shorcuts are there).
Simple solution for this problem; make s2e a system app before running it, and use some common sense before flaming a great app.
How to make it a System app? Move s2e to System/app and give rw, r, r permissions.

Why does the Link2SD application not link /data/data too?

From the Link2SD FAQ:
Link2SD does not link application's private data files that are located in /data/data directory, they remain in the internal storage. Thus each app you install will still have some data on the internal storage so you can still potentially fill up your internal storage even if you are moving all of your apps over.
Click to expand...
Click to collapse
Why is this the case? There are other Linking apps which do move /data/data files. Why would Link2SD not do this?
I wish to ask this before I go bothering the application author. I figure there is some well-known issue here which I am not aware of.
I may have to switch linking apps because my /data part is getting too full, mostly due to Google's crappy maps and browser apps, which are horrifically fat.

Data Linking ?
jmomo said:
From the Link2SD FAQ:
Why is this the case? There are other Linking apps which do move /data/data files. Why would Link2SD not do this?
I wish to ask this before I go bothering the application author. I figure there is some well-known issue here which I am not aware of.
I may have to switch linking apps because my /data part is getting too full, mostly due to Google's crappy maps and browser apps, which are horrifically fat.
Click to expand...
Click to collapse
I too have this issue, and am now running low on internal space (mainly due to the huge data\data folder) ...
Can you tell me the name(s) of the other apps that provide linking the data folder ?

I believe app data isn't moved, because it will make your phone laggy as hell. Guess the dev chose for finding more space, but not at the cost of speed.

tommert38 said:
I believe app data isn't moved, because it will make your phone laggy as hell. Guess the dev chose for finding more space, but not at the cost of speed.
Click to expand...
Click to collapse
This makes no sense at all. In many cases, newer SD cards are FASTER than the internal flash on older phones.
Please don't guess wildly about stuff you don't understand.

d_bizzzz said:
I too have this issue, and am now running low on internal space (mainly due to the huge data\data folder) ...
Can you tell me the name(s) of the other apps that provide linking the data folder ?
Click to expand...
Click to collapse
S2E does it, but from what I've seen, it's only for Cyanogen.

jmomo said:
This makes no sense at all. In many cases, newer SD cards are FASTER than the internal flash on older phones.
Please don't guess wildly about stuff you don't understand.
Click to expand...
Click to collapse
Sustained write/read speeds don't tell the whole story, as you may know (probably not). You probably believe the more megapixels a camera sensor has, the better? Also, the phone must support those faster µSD cards. Seeing you've only been here for half a year and you've only contributed with a dozen posts, I can say for certain that you've never read any warnings for not moving app-data. It's not your fault.
Unfortunately, I noticed that all the new people coming here have no respect or decency and think they know everything already. Guess what: you don't know **** . So, like I already said before, drop the attitude.

Respectfully, you are simply wrong.
Modern SD cards are faster than the internal flash on older phones, which are the phones that need apps like Link2SD. I don't know about more modern phones.
http://forum.xda-developers.com/showthread.php?t=934087
Bonnie++ is the best way, that I know of, to benchmark a flash storage devices, but it's not for noobs
http://forum.xda-developers.com/showthread.php?t=1169910
I remember running bonnie++ against my Nexus One and a cheap 16GB card about a year ago when that above post was made and my SD card was faster than the internal flash in almost every way, and that was then.
Yes, my post count is low. XDA Devs is full of loud noobs who think writing a java app or rooting a phone makes them a leet technical resource. I've been writing software and managing unix systems for over a decade.

Well, sir, you go ahead and put your app-data on your µSD . Benchmarks are for [random word].
Did I also mention that somehow some new members are bragging about what they have achieved and are capable of, while they haven't made themselves useful in any way? If not, now I did.

Is there still no possibility to move also the data folder (e.g of games)? Most of my applications are rather small and most space is taken by the game data folders.

tommert38 is correct here.
Because there is no guarantee, that if your sdcard is fast, it'a also faster than your internal flash. There are more dependies than only the speed of the card. What are the specs of the nexus one sd-reader? This could be an popotentially barrier.
At least: Which size supports the nexus one for sd-cards?

I agree with the OP about this. If it is a worry about the speed, i'm sure mr. bulent akpinar can at least provide an option in the app to enable/disable saving /data/data to the link2sd partition. everybody happy!
here's a link to the original link2sd thread http://forum.xda-developers.com/showthread.php?t=919326 maybe the app author can take note of it as a suggestion for future updates

One other benefit of not placing /data/data on the SD card is for the case if your sd-ext partition fails to mount for some reason (e.g. failing a file system check). If /data/data was on the SD card, then most of your application settings will be gone, including for builtin apps like the launcher. It will look very similar to a factory reset.
With /data/data on internal storage, your settings will be still be visible in this scenario and it will only be the downloaded apps that disappear. This should be somewhat easier to recover from.

RealCrogge said:
Is there still no possibility to move also the data folder (e.g of games)? Most of my applications are rather small and most space is taken by the game data folders.
Click to expand...
Click to collapse
Consider all the risks and if you are willing to take them you might find this thread usefull. Just be sure you know what you are doing

LINK2SD v3.4.1 - No links data/data
apologies for posting to an aged thread, but just today LINK2SD has been updated to include linking of the /data/data
I'm already enjoying the new found space made available, it seems to work very well so far ...

d_bizzzz said:
apologies for posting to an aged thread, but just today LINK2SD has been updated to include linking of the /data/data
I'm already enjoying the new found space made available, it seems to work very well so far ...
Click to expand...
Click to collapse
May I ask you if you noticed a lag or performance slow down? I also love link2sd but I fear to upgrade to the latest version cause I don't want to compromise the reliability of my system, which so far, has been excellent.
I have read that moving the /data files could slow down the phone or cause overheating of the sd card. Actually I have a class 10 ultra II Sandisk.
Thanks for any report and opinion.

ik8vwa said:
May I ask you if you noticed a lag or performance slow down? I also love link2sd but I fear to upgrade to the latest version cause I don't want to compromise the reliability of my system, which so far, has been excellent.
I have read that moving the /data files could slow down the phone or cause overheating of the sd card. Actually I have a class 10 ultra II Sandisk.
Thanks for any report and opinion.
Click to expand...
Click to collapse
I haven't done any benchtesting or anything but haven't noticed any slowdown or battery drain what-so-ever.
My phone runs just as good as before.
I only link my game apps to SD because I expect one day the SD card will fail (like most media storage devices) and most of my essential apps are un-linked and stored on the internal phone mem.

d_bizzzz said:
I haven't done any benchtesting or anything but haven't noticed any slowdown or battery drain what-so-ever.
My phone runs just as good as before.
I only link my game apps to SD because I expect one day the SD card will fail (like most media storage devices) and most of my essential apps are un-linked and stored on the internal phone mem.
Click to expand...
Click to collapse
Thanks, I have linked all my apps and it is now almost an year. I was very curious about the possibility to move the data too but was a bit on the standby, because if you check on the play store, there are some complaints. Now, I don't know what to do, maybe I'll give it a try.
Thanks for your kind reply.

ik8vwa said:
Thanks, I have linked all my apps and it is now almost an year. I was very curious about the possibility to move the data too but was a bit on the standby, because if you check on the play store, there are some complaints. Now, I don't know what to do, maybe I'll give it a try.
Thanks for your kind reply.
Click to expand...
Click to collapse
I guess some reviews may be on different phone models.
All I can advise is check the gppd & bad reviews and the phone model. Also to have a titanium backup of your older link2SD so you can roll back if needbe.
Worth just linking a few & see how it goes.
No complaints on my Galaxy S3, works fine & has done for the past 2 years

d_bizzzz said:
I guess some reviews may be on different phone models.
All I can advise is check the gppd & bad reviews and the phone model. Also to have a titanium backup of your older link2SD so you can roll back if needbe.
Worth just linking a few & see how it goes.
No complaints on my Galaxy S3, works fine & has done for the past 2 years
Click to expand...
Click to collapse
Well I downloaded the new version (I have the plus option) but I don't understand how to move the data to sd since in the options it is specified that only future installs will be moved (if I flag the option).

Back to the original question. I use Mounts2SD for my Nexus One. I check to move Apps, Data, Dalvik, and Libraries. The rest I leave alone. I have no problems with space with this set-up. Speed is decent, I think the issues I have are probably related to the various custom ROMs I've been using but I can't be 100% sure.