I had a quick search through the posts and found some folk with questions about their SD card and extra space, however...
The question I have is, what is the best practice for installing applications on Winmo devices?
I understand that some applications that boot at start-up need to be on the device because the SD card may be started late on in the boot up process.
In general though, is it better to install applications to the device and fill the device memory with applications while keeping files on the SD card, or am I just as well installing them on the SD card?
I ask only because today I have been made aware of a potential issue with my Blackstone / SD card and recent updates from HTC.
Thanks for any comments, if there is a better place for my question please let me know what to do to move / remove my thread.
internal is faster
internal is lost at hardresets and of cause flashing
external is disabled when the device is suspented so
today screen running programs are best left in the internal
Related
Okay XDA tenured- please be gentle. I ve searched, but can not find specific answers to my questions. I ordered a 16gb class 6 (currently have class 2), but would appreciate information before making the changes.
1.) Is it possible to leave current apps on the device memory, then set up for apps to SD and then future apps will go to the card?
2) Based on question 1) if it works, when I update future apps on the device, I am guessing they would then uninstall from the device and then install to card?
3) Would it be best for performance to leave all cache on the device memory? Seems like the system would be faster then.
4) What is the meg space difference leaving all cache or moving it?
5) When changing over to apps to SD, is it not kind of like the same constrained system as an iPhone (Plenty of intitial space, but no ability for external storage)? Point being, if all the apps are on the card and you want to listen to or view media on a seperate card, you would not be able to, since the apps are on the "device" card. This is the whole point to my first question. Unless you can copy the app directory path on the card to another card and use as is- just like the card already installed too...
1: Yes, if you follow my tutorial, it has you copy the existing apps to the sd card and if you use my app, the checkbox tells it to do that as well.
2: No apps will be on your device. There's no way to have a hybrid here, it's either all apps on the sd card or none(not actually true but would be a pain in the ass to make symlinks for each app individually and I don't know of anyone who cared enough to actually try it)
3: I have all apps and caches on the sd card and it is running just as smoothly as normal(and with a class 2 sd card!) There might be some slowdown but it's imperceptible to me.
4: With the cache on device it'll vary depending on what apps you have and how often you use them. With everything moved the memory on the device seems to stay permanently at 72-73MB. That said, moving the normal cache(dalvik-cache seems to be ok) is pretty unstable and I wouldn't suggest it unless you really know what you're doing.
5: Yes, unfortunately this whole process relies on the system not knowing the apps are on the sd card so it's pretty strongly tied to one. That said, you could probably get away with different sd cards as long as they also have an ext2 partition with the app, app-private, etc. directories in it. You'd probably have to reboot when switching sd cards but it should be possible(interestingly you could use this to get different settings depending on what sd card you have in)
Thanks!
So basically we have an iPhone in regards to being stuck to device memory and no option for external storage beyond what is on the card.
I guess there are pros and cons to either set-up. App hounds would prefer apps2sd and media hounds may prefer leaving things alone.
If you are an app and media hound, you are kind of stuck juggling media from the card.
Yep. Although as I was talking about, you could theoretically move each app independently and set up symlinks in the /data/app directory for each app, pointing to where it is on the sd card and leave the ones you want on the phone as they are, but that doesn't sound particularly fun.
With apps to sd, is it possible to install certain apps on the phones memory?
A) Wrong forum
B) Why would you want to?
But I suppose if you REALLY wanted to, it'd be as simple as ejecting your SD card (as long as phone doesn't freak out) and installing whatever you need, and then reinserting. I do believe that should work, or at least it has worked in the past.
rockdevourer said:
A) Wrong forum
B) Why would you want to?
But I suppose if you REALLY wanted to, it'd be as simple as ejecting your SD card (as long as phone doesn't freak out) and installing whatever you need, and then reinserting. I do believe that should work, or at least it has worked in the past.
Click to expand...
Click to collapse
Pulling your SD card while your phone is still on is very stupid especially if your using Swap or Apps 2 SD and besides even if it did install on your phone's memory Apps 2 SD will automatically move it from the phones memory to your SD card.
just thought that some programs that run all the time may run more reliably from the internal memory vs external sd card.
sorry misread the question. if you have apps to sd... currently they are built into the roms to install on startup....so anytime you restart on one of these roms you will move the app you moved to internal to the sd. there maybe some command to protect it from the move but i'm not aware.
the answer to your question is : yes it possible with tmpfs
but
it won't change nothing
we are talking about what ? 1mb max app size ?
Pull then push to /system/app. Wrong forum.
What im.l0ltn said will work fine, but like others asked, why? You won't see much improvement unless you are using a low class sd. I have tried installing a few apps to internal memory but didn't see enough of a noticable performance boost. And if you are using a class 6 sd you will actually slow things down by putting them on internal mem. So you're better off leaving them on SD and saving the trouble of reinstalling every time you install a new rom. It gets to be more trouble than it's worth.
Can you please help a noob figure out where this post belongs?
I make no pretense to being a developer, and I was very hesitant to join XDA, but these are questions concerning modding which I have not found answers to, despite posting to a number of other Android forums, so I was forced to "raise my sights."
I have an LG Optimus Fuel L34C (KitKat). I am an Android noob but I have a history with Linux, so I know just enough about what goes on behind the KitKat curtain to make me dangerous. So yes, I also care about the journey. And I'm already heavily invested in this quest, so despite my lack of expertise, I'm willing to do the leg work to make it happen.
My one saving grace is I have a backup fetish. And I want to continue to make Nandroid backups even when the L34C's puny internal storage (1790 MB usable) is maxed out (or nearly so). But I don't want to resort to backups to the cloud because 1) it offends my inner geek that I have to rely on someone else for backup support, and 2) as a delusional paranoid, the concept of "the cloud" gives me the willies.
I'm using TWRP Manager (Root) for Nandroid backups now, but TWRP only can write to the internal SD. Which means that once internal storage is about half full, there's no longer enough space remaining for any more Nandroids. And a bare bones installation with just enough additional apps installed to perform the Nandroid already takes up about 700 MB. So there's no chance of any further Nandroid backups after downloading or installing just two or three hundred more MB.
So my primary goal is to be able to write Nandroid backups to the external SD card (or, pipe dream, to write them to USB). If this also allows me to install apps or store other (internal) data on the external card, so much the better.
I just bought a second L34C because the WiFi on the original L34C pooped the bed. So now I have a new and unmodded L34C to experiment on. I had (towel) rooted the old phone, write-enabled the external SD card and installed the TeamWin open recovery image v2.8. And I replaced the OE 4GB external SD card with a 16GB class 4 card, partitioned half in Fat32 and half in Ext3.
The primary obstacle was that I could never get the second partition on the 16GB card to mount, which prevented me even from experimenting with symlinks. I also installed the latest version of Link2SD, but when I tried to use it to move an app that Link2SD labeled as movable, I got this:
!Failure
App2SD is not supported by your device. Because your device has a primary external storage which is emulated from the internal storage. You can link the app in order to move its files to the SD card.
Click to expand...
Click to collapse
Dunno why it's blaming Apps2SD unless Link2 is built around Apps2.
Curiously, I installed Aparted, too, and it was able to access (and process) the 2nd partition, even though it wasn't mounted. I've not heard this definitively but I'm led to believe this is down to the L34C's lack of support for init.d. So I downloaded a copy of daishi4u's custom boot image, which includes support for init.d, but the old phone crapped out before I could try it.
So with background in place, and a spanking new L34C in hand, on to the questions.
#1. With the current state of L34C/KitKat development, is what I'm asking even possible? Once the internal SD card has got too crowded for a Nandroid, is there a solution that will allow me to continue making local Nandroid backups? In particular, I'm thinking there might be another Nandroid backup app that I am unaware of that can write its backups to some location other than the internal SD card.
If this already has been accomplished (and is documented online), please just point me to the details and I'll get out of your hair.
2. I picked daishi4u's custom boot image because the reputation of daishi4u's work is known to me, and because it offered init.d support. If you think another boot image is preferable, please enlighten me.
3. Is Link2SD's problem with the L34C truly the emulated storage? I ask because I know developers typically code apps to make a best guess as to the cause of an error, but despite their best efforts, an app still is liable to be exposed to unanticipated conditions, resulting in a problem that might be beyond the scope of their programming to understand and enunciate.
4. Is the lack of init.d support in fact what prevents an L34C mounting additional partitions on the external SD card? Or am I barking up the wrong tree?
5.a. I found a post in another forum that was near three years old stating that the extra partition on an Android external SD card must be no more than 2GB, and preferably just 1GB. If this ever was true, is it still the case for KitKat? And what is the source of the limitation?
5.b. If there is a 2GB partition limit, is there a limit to how many 2GB partitions can be externally mounted? A Nandroid backup of a heavily configured L34C could take up most of 2GB, so it would be especially useful work-around if there were one (additional) partition for the Nandroid and a second (or third, or fourth, ...) for moving apps and random data off the internal SD.
6. Which app(s) would you suggest I try for moving apps/data/folders to the external SD? There are so many available, and I have not been able to find any comparisons/contrasts of their relative merits, so I would appreciate your recommendations to avoid having to resort to the 'shotgun' approach. This is presuming I'm able to get more than one partition on the external SD card to mount.
I've not lost sight of the fact that some of these apps do not require a second partition on the SD card (creating something functionally akin to an iSCSI partition on it?), but I'm not counting on finding a solution in one of them.
Thank you for taking the time to read my long-winded post.
Well personally I don't keep more than one nandroid on my phone but what you may wish to do is transfer them to your pc for safe keeping and not have to worry about it. You could also try inserting your sd card into your pc and manually transferring the nandroids from your pc to your sd card afterwards. It may work.
Now with regards to the sd card write protection issue, I could not locate anything for your device in particular but if you register you can ask your question here and someone may be able to help you.
So I bought this Sony Experia Z3 (D6600) Just over a week ago, and was immediately unimpressed with the way
kitkat handled the SD card. ( I forked out for a 64gb card as I was intending to store all my games and media on it )
So after a lot of reading about workarounds, and trying out programs from the play store I came to the conclusion
that it wasn't possible to acheieve what I wanted due to security issues google had implemented with kitkat.
My understanding at this point was that lollipop addressed the issue and allowed installations to be moved to the
external SD Card again, so I have now got a version of lollipop running and rooted. However, when you install a game
or app it still installs some to the primary storage and then moves a portion of it to the external SD card. So currently after
having only installed four or five games I have 2.9gb free on my device memory and 58.3 gb free on the external card.
Kinda defeats the object doesn't it !! Even with everything moved to external card it is going to fill up soon.
So what I am asking (And to be honest I am really surprised I am having to ask it, and it's not something that can't be
set up by the user) Is please please does anyone know I can change my default storage from the phones storage to the
SD card. ( i.e. Swap sdcard for sdcard1 ) So as I do not have to worry about the device filling up so early in life.
I know there is no vold.fdstab or whatever it is anymore, but other than that I have no further info with achieving this on
lollipop. Is there a different file I can alter to swap it, or is a case of needing a different kernel flashed or something?
Any info would really really be welcomed !!
Many thanks in advance
Hello all,
It seems that nowadays all vendors decide to go with the approach to have a virtual SD card that uses an emulated filesystem to make us feel happy in case we do not have a real SD card. I honestly do not understand the reasoning behind this so I am reaching out to you to let me know what you think the reason is.
For now I can see the following pros and cons of this approach:
Pros:
Have SD card support in case you do not have a real one and you have an app that requires it.
Cons:
You no longer can move applications to external SD card on most devices (all that I have tried).
The application data (obb) that is essentially the largest thing an app can offer goes directly to the internal SD card and you can not move it to the external SD card.
You are now even restricted by what you can write on the external SD card because if not there is a security issue. That's also a thing that I do not understand that is conveniently not explained and just implemented.
Your CPU cycles are used to process the data yet once more just so that you can have the luxury of an emulated file system.
The fuse filesystem in most devices lacks some basic features like links.
Essentially the internal SD card seems like a Huge hack to me. Why is that? Even just the name gives it all away. "Internal SD card". That is not an SD card. It's not even a separate flash chip. Not even a separate partition on most devices. There is times where this is just a folder in your userdata partition made to look like an SD card by the magic of fuse.
The only reason I could find for this monstrosity is that there is some kind of compatibility issue with some apps in case you do not have an SD card and so that's why they came up with this.
So please let me know what the big idea that I seem to be missing here is as to why this humongous hack is needed. Thanks in advance!
Cheers,
Sakis