Database Users

standardizing sd internal and external wording

I wonder if we could could come to an understanding on language use for this device.
SDCARD = /SDCARD but is actually internal. On other devices it is of coarse external. This of coarse creates some confusion when making comon statements like "place file in root of sd"
I'm sure Asus has some reason for doing things this way. Though it seems backward to me.
Could we agree to call /SDCARD as SDI
And to call /Removable as SDE
If someone has a better idea feel free.
Regards
Ty.

I think SDI and SDE are more confusing, as in most Linux distros the SATA hard disks are labeled as sda, sdb, etc. The current naming scheme is fine as is, with removable storage available in the clearly marked "Removable" folder that gets created.
The reason for the distinction between the "sd card" and the rest of the internal storage is so that you can still read and modify the contents, because unless you root the device, the default permissions are set up so that the regular user cannot modify vital system components on the internal storage. This is has been the standard since the days of the G1, where with such little internal storage the intention was that the user would never have the ability to mess with it and risk breaking or overfilling it, and instead all of their personal data would reside on the removable SD card. Today's Android devices now possess enough storage to safely store user data internally, but the main principle remains the same, and therefore the nomenclature remains unchanged. Renaming the folder would probably break a lot of applications that depend on the ability to store data to /sdcard, so it's best not to touch it.

i guess a newbie wouldn't always get it, but the use of the nouns "sd" and "sdcard" will always refer to the external sdcard, specifically /Removable/microsd. whenever anyone wants to refer to internal storage, they would refer to it by path /sdcard exactly.
but you're right. a newbie reading it wouldn't always get it.
I don't need a signature.

finalhit said:
i guess a newbie wouldn't always get it, but the use of the nouns "sd" and "sdcard" will always refer to the external sdcard, specifically /Removable/microsd. whenever anyone wants to refer to internal storage, they would refer to it by path /sdcard exactly..
Click to expand...
Click to collapse
Totally agree - if someone tells me to put something on the SD card, to me that means unequivocally the physical SD card, not internal memory.
Regards,
Dave

Great feedback. I apreciate the clarification.
I didn't want to suggest changing the code or any other part of android. Just the reference.
When i see comments in posts that read put this file in root of sd i am left with unnecessary ambiguity. First thought would be put it on the external but after looking at possible options i quickly see there is also a location on this device called /sdcard . Ambiguous
So all i am saying is when it comes to this device, if we want to suggest putting files in root of sd we specify the location in a non ambiguous manner
IE: put file in root of sd (SDE)
Or
Put file in root of sd (/externl)
I've got 5 bucks that says 99% of people who buy this device are more noob than I.
That's all.
Ty

If someone is writing a tutorial where you would need to store files on external storage, I can't think of many instances where it would make a difference where you put the files, so long as you yourself can remember where they went. For instance, if you're told to put a .apk file on a SD card for installation later, the OS won't care where you put it, you just have to know where it is when you're looking for it later to install. The instances where it does matter whether you're storing data to /sdcard or /Removable are almost always when dealing with applications that need an extra folder outside of the internal storage for additional data, mostly for maintaining compatibility with older Android devices. Everything else like photos, videos, music, etc. can be stored anywhere within /sdcard or /Removable, and the OS can read it just the same.
When writing tutorials, you just have to be sure to make the distinction between /sdcard and /Removable, because that's a set of folders that any newbie will see and recognize when browsing through the Android file system. Simply referring to them as the internal SD and external SD can be confusing too, since that's not how they appear in the file manager. At work when troubleshooting issues with Windows 7, I deal with users every day that get tripped up if I ask them to open the Start menu or an Explorer window, because neither of them are labeled as Start or Explorer. Instead, for the Start menu I have to tell them to click on the blue orb in the lower left hand corner, and for Explorer I have to tell them to single click on Computer in the Start menu, or double click on the Computer icon on the desktop. Newbies don't know the OS, which means they don't know anything except what they can see on the screen. Anybody trying to write for newbies should always write tutorials based completely on how things appear exactly on the screen.

The joys of UNIX filesystem. It is different from windows. No need to tie thing down to physical location concepts such as disks (c:, d: , ????). I suspect if one is rooted they could alias the /sdcard to internalMemory or /InTablet.
Sent from my Transformer TF101 using Tapatalk

Would like to re-iterate this.
Just got a new device, (SGS2), it also has an internal and an external SD.
But the difference here is that the SGS2 always mounts the internal as /sdcard
Really don't like the fragmentation.
I still can't believe the ASUS sometimes mounts internal as /sdcard and sometimes external as /sdcard
It's just ****ing messy.
Ty.

Cool story bro
Sent from my Desire HD using XDA App

[Q] In simple terms, how to access/use storage on CM7 SD

I have spent the last week reading and searching the forums in an attempt to find out how to be able to access and use the empty space left on a CM7 boot sd. Some of the posts were confusing and others seemed to be targeted to those who are already very familiar with the file structures of these systems. The only paritioning experience I have is dividing a boot drive before putting on XP. I am using a Sandisk 8gb and it looks like there is about 5 gig free. Win XP is the os I am running.
So the questions I have are:
1) In simple terms, exactly what has to be done to a boot CM7 SD card to be able to use the empty space for books, mp3, etc? On the recommendations I read in different threads, I downloaded easus partition master, gnome partition editor, and minitool partition wizard. They all pretty much do the same of being able to display the 4 partitions, but what do with the programs then?
In the near future I would like to get a 16g or 32g and wouldn't want all of that space going to waste.
2) Is it possible to have it so that the NC stock boot can read the books downloaded in CM7? I have not been able to find where CM7 stores books.
Thanks to all whose work helped me get to this point. The NC is a fascinating piece of hardware.

Hey! Using the remaining storage on your SD card is quite easy. Just download and install this program on your NC. http://forum.xda-developers.com/showthread.php?t=952456 open the program and select the 4th partition to be mounted. Now when you plug your nook into the PC, the partition which holds media etc. Will be mounted you can now transfer mp3's, roms for Emulators etc.
As for #2, Your cm7 books should be on the previously mentioned partition, which is the 4th.
Sent from my ADR6300 using XDA Premium App

Imbroglio said:
I have spent the last week reading and searching the forums in an attempt to find out how to be able to access and use the empty space left on a CM7 boot sd. Some of the posts were confusing and others seemed to be targeted to those who are already very familiar with the file structures of these systems. The only paritioning experience I have is dividing a boot drive before putting on XP. I am using a Sandisk 8gb and it looks like there is about 5 gig free. Win XP is the os I am running.
Click to expand...
Click to collapse
5G sounds about right for the /sdcard partition. The rest of the partitions on an 8G card are /boot, /system, and /data. Use Root Explorer to poke around; you can tell when you jump partitions because the used/free numbers at the top will change.
/boot is not normally mounted.
The root filesystem is in-memory and is initialized from /boot/uRamdisk by default.
So the questions I have are:
1) In simple terms, exactly what has to be done to a boot CM7 SD card to be able to use the empty space for books, mp3, etc? On the recommendations I read in different threads, I downloaded easus partition master, gnome partition editor, and minitool partition wizard. They all pretty much do the same of being able to display the 4 partitions, but what do with the programs then?
In the near future I would like to get a 16g or 32g and wouldn't want all of that space going to waste.
Click to expand...
Click to collapse
The original instructions in the size-agnostic install thread detail what happens to various sizes of card; for anything above 2G /sdcard gets all the extra.
Any apps that use /sdcard for storage will use this space. App-specific config data and small databases are generally in /data unless instructed otherwise (I'm using less than 300M of my /data partition as yet). The app info or permissions will often give clues; if the permission for "read and write SD card" is requested or required, the app can or must use this space. Some apps (like BeyondPod) will always use /sdcard.
So, your space isn't wasted, it's just unused until you fill it.
2) Is it possible to have it so that the NC stock boot can read the books downloaded in CM7? I have not been able to find where CM7 stores books.
Click to expand...
Click to collapse
The CM7 SD boot cleverly uses the built-in memory for both /cache and (at least some) media storage; the "media" stock partition pre-1.2 is mounted as /emmc; I don't know how the SD boot uses the newer partitions. The NC app stores books in "/emmc/B&N Downloads/Books" and magazines in ".../Magazines". You can move your music files to "/emmc/My Files/Music" and the stock music player will automagically find them there, freeing up even more space in your SD. This partition is mounted the same for emmc-booted NCs, making an easier transition if you get to that point (it took me months to decide to go ahead and do it, and I'm happy with the choice). Other apps may look there, or can be told to look there, but since it's a new-ish Android "feature" (convention, really), it's not universal.
When you use USB mounting by plugging your charger cable into your PC's USB socket, by default the two "drives" mounted are /sdcard (named "CM7 SDCARD") and /emmc ("MyNookColor"), so you can use your PC to explore, backup, and move files back & forth to experiment. Both partitions are FAT32, so all PCs should be able to handle them. Remember to tell the PC to unmount them in software before unplugging the cable, like any thumb drive.
Thanks to all whose work helped me get to this point. The NC is a fascinating piece of hardware.
Click to expand...
Click to collapse
It is, isn't it? I haven't regretted buying one for a minute.

Thank you for posting the reply on the APP nook/cm7 file system.
Unfortunately, it still doesn't address HOW to sideload (DRAG AND DROP) books on the utilizing the empty portion of a CM7 SD card.
1. I put the SD card into an reader.
2. Windows xp detects the card.
3. I pull up windows explorer.
4. It only displays the "root" directory. Yes, I can drag and drop into the "my documents" folder but this partition only contains about 300 meg total storage.
5. It does not display the other partitions, thus I cannot drag and drop anything into the 5g partition.
Yes, I can drag and drop on the NC onboard storage, but not the CM7 SD card. Is the remaining 5 gigs only allocated for APP storage?
Now after 2 weeks searching this site and seeing numerous recommendations for software but not what to do with it or cryptic posts assuming that one already is very familiar with the android os, I am pulling my hair out over this. The only post I found that directly and simply addressed the issue requires that I reformat the SD with SDformatter to allow for full storage access but then I have install CM7 all over again.
I downloaded NookColorUMS-0.3b.apk using Opera, but that is all it did. I had to search again and it mentioned something about ADB (no idea what that is) which had to be installed. Aparently that doesn't work alone and it lead to another link to more required software - the Android SDK and then came a long list of more steps just to install that.
Hopefully, if I ever figure this out, I will write a simple to understand post that new NC CM7 people like me can understand.

Try this: unplug the charger cable from the "n"-shaped brick. Plug the cable into a USB port on your computer. Plug the other end into the NC as usual.
Tap the button(s) that pop up on the NC to allow USB mounting.
Two new drives show up on the PC. These are /emmc and /sdcard, but they'll have different names on the PC. Use Windoze Explorer to drag and drop. I might suggest /sdcard/download as a first try, but feel free to drop copies in multiple directories in order to experiment. Adobe Reader looks all over for its docs.
When you're done, click on the PC tray thing to release BOTH drives from the PC.
Poke around with your reader to find these files. Some readers might be better at looking around than others.
Let us know how you get along!
Sent from my NookColor using XDA Premium App

So once you download the NookColorUMS.apk, use the file explorer on your nook, go to the 'download' folder and click on this file. It will open up and ask you if you can install the program. Click yes and let it install.
When you are done with that, open the program and mount the partition of interest(i think its 4 as a previous poster stated). Now when you plug your nook into your computer that partition will mount. There should be 4 partitions if you are using the CM7 on SD card.
You should be able to now drag and drop files on that partition. Just make sure you unmount properly as I have run into problems if you just unplug it.
extremepizza
Imbroglio said:
Thank you for posting the reply on the APP nook/cm7 file system.
Unfortunately, it still doesn't address HOW to sideload (DRAG AND DROP) books on the utilizing the empty portion of a CM7 SD card.
1. I put the SD card into an reader.
2. Windows xp detects the card.
3. I pull up windows explorer.
4. It only displays the "root" directory. Yes, I can drag and drop into the "my documents" folder but this partition only contains about 300 meg total storage.
5. It does not display the other partitions, thus I cannot drag and drop anything into the 5g partition.
Yes, I can drag and drop on the NC onboard storage, but not the CM7 SD card. Is the remaining 5 gigs only allocated for APP storage?
Now after 2 weeks searching this site and seeing numerous recommendations for software but not what to do with it or cryptic posts assuming that one already is very familiar with the android os, I am pulling my hair out over this. The only post I found that directly and simply addressed the issue requires that I reformat the SD with SDformatter to allow for full storage access but then I have install CM7 all over again.
I downloaded NookColorUMS-0.3b.apk using Opera, but that is all it did. I had to search again and it mentioned something about ADB (no idea what that is) which had to be installed. Aparently that doesn't work alone and it lead to another link to more required software - the Android SDK and then came a long list of more steps just to install that.
Hopefully, if I ever figure this out, I will write a simple to understand post that new NC CM7 people like me can understand.
Click to expand...
Click to collapse

I am using Racks Phiremod/Honeycomb dual boot image but I don't see why this method would not work for your install. Rather than messing with mounting partitions and all that whenever I want to put something on the SD Card partition I will just plug my nook into the computer, copy and paste whatever file I need onto the nook's internal memory, and then use root explorer to cut and paste the file from the internal memory to the SD Card partition.

my emmc and sd card both show up and writable drives. I use stuff that I need faster access to in there, since the mount time is faster than the SD card.

obb files to external

I did search and with the google searches I've done, can't really figure it out so thought might ask here.
When I moved applications to external sd card, i didn't realize it didn't move the application data itself (inside obb folder), which is in the android device's internal memory. So basically, I have the application (i guess equivalent to .exe for windows) on the external sd card, but the beef of it (the applicatin's data) is still on the internal memory and using up the device's memory....how can I move the data (obb folder) to external, remove it from interernal to free up space, and have it boot up / work on the android device?
i'm not advance geek so need a dummy explination

You didn't provide details of how you moved the app or even what app we are talking about. So it's impossible to give targeted advice. Which is unfortunate since you want a dumbed down, simple answer. Which can't be done without knowing those crucial details.
You can use one of the Play store apps to move the app. I'm sure that some of them would move the app data as well. Or change the app data path (folder) in the app's settings. Or reinstall the app. Or alias the current internal data location to the external card with a symbolic link. Or any number of other ways.
The simplest options there would be trying some of the Play store apps that assist in moving programs to the external data card. And if that doesn't work for some reason, then reinstall your app.
Good luck.
.

fffft said:
You didn't provide details of how you moved the app or even what app we are talking about. So it's impossible to give targeted advice. Which is unfortunate since you want a dumbed down, simple answer. Which can't be done without knowing those crucial details.
You can use one of the Play store apps to move the app. I'm sure that some of them would move the app data as well. Or change the app data path (folder) in the app's settings. Or reinstall the app. Or alias the current internal data location to the external card with a symbolic link. Or any number of other ways.
The simplest options there would be trying some of the Play store apps that assist in moving programs to the external data card. And if that doesn't work for some reason, then reinstall your app.
Good luck.
.
Click to expand...
Click to collapse
Only thing I've done was root it then moved the application (move to sd card) via settings >> Application Manager. i want to do it for all apps but it's mainly due to games taking up lots of space. Reinstallng won't help cause everything that's obb just direct itsself to the internal storage, nothing i installed even gives me the option to install data into external, just only has a install button and it installs to internal memory

I'm not going to sort all of that out. It can be done if you look into the details.
The best advice that I can offer is to consider installing a custom S5 ROM like Phoenix. It has a setup option to swap the SD cards. That would mean that all of your apps that automatically install and live on the internal memory.. would actually end up on the external card. And it works perfectly.. because the apps think that they are on the internal card even though they aren't.
The source script could also be applied to your existing configuration, but doing so would not fit inside your stipulation for a simple answer.
.

by the way...
fffft said:
I'm not going to sort all of that out. It can be done if you look into the details.
The best advice that I can offer is to consider installing a custom S5 ROM like Phoenix. It has a setup option to swap the SD cards. That would mean that all of your apps that automatically install and live on the internal memory.. would actually end up on the external card. And it works perfectly.. because the apps think that they are on the internal card even though they aren't.
The source script could also be applied to your existing configuration, but doing so would not fit inside your stipulation for a simple answer.
.
Click to expand...
Click to collapse
fffft, one question here: Would it be possible to format the whole external SD card with ext4? So it would be quite simple to copy such files manually within a shell and set a softlink to the moved files? I don't understand why android stays with that fat drived file systems were softlinks are not working. Is there any reason for? So all data2SD apps have to work with specific *mounts*. I can't believe that this is fast and stable.

brachypelma said:
fffft, one question here: Would it be possible to format the whole external SD card with ext4? So it would be quite simple to copy such files manually within a shell and set a softlink to the moved files?
Click to expand...
Click to collapse
That won't work unless you do a lot more prep work. The file system isn't invisible, the OS would have to interact differently with ext4 than ExFAT. The OS would balk the first time it tried to follow a symbolic link and didn't find the ExFAT structure it expects.
To make that work, you'd need to mount the card yourself, manage permissions and hide the file attributes i.e. permissions from the void manager and other housekeeping tasks. Android expects to find a case insensitive and permissionless FS. Otherwise, void will report errors to the volume manager and the OS won't recognize your card. All of which is to say that this is a more distant outlier to the requirement for a simple solution. So you'd be generating fatal errors the first time the OS tried to follow a symbolic link to your ext4 files.
So yeah you can shoehorn an ext4 card into the system with enough work. But it isn't as simple as you believe. So back to my suggestions that the OP either install a custom ROM that does what he wants or that he looks at the script that I linked him to. Or perhaps migrate to CM 11, where native support for ext4 and NTFS have been added.
.

Set external SD card to default install location [HELP]

Hi, my problem is with the phone of my girlfriend. Now have external 64GB SD, because internal storage is full. I used Android SDK and all the instructions for set default storage for install APP the new SD Card, you know, with the command adb shell pm set-install-location 2. And no error, i try get-install-location and report 2. But googe play only try to install in the internal storage.
I think the problem is with the system of the emulated storaged or something, but i tried many APP, many solutions, and i cant fix this, i search in google and others locations, have 30 tabs in firefox open with information, but i cant found the solution for this
Samsung Galaxy NOTE 4 (910F)
Android 5.1.1 (Of samsung of course)
Rooted
The vold.stab is:
dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
PLEASE, help me! thanks

I tried dismounting and mounting the SD, touching the vold.stab file, but do not get any results.
Can anybody help me?

Go back to stock, upgrade to 6.0.1. Then see if this helps-
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
The article is for S7, but see if you can have that working in the N4 - just have a backup of everything (int SD, ext SD, full backup in recovery).

ph03n!x said:
Go back to stock, upgrade to 6.0.1. Then see if this helps-
The article is for S7, but see if you can have that working in the N4 - just have a backup of everything (int SD, ext SD, full backup in recovery).
Click to expand...
Click to collapse
Thanks, for the moment 6.0.1 is not released in Orange (confirmation date has passed and still not have it, I assume that is in the offing). When have 6.0.1 i try you solution, thanks.

ph03n!x said:
Go back to stock, upgrade to 6.0.1. Then see if this helps-
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
The article is for S7, but see if you can have that working in the N4 - just have a backup of everything (int SD, ext SD, full backup in recovery).
Click to expand...
Click to collapse
I tried this in my phone. While the command itself worked after a bit of a tweak, the storage situation was pathetic - the phone showed the External SD as a part of the overall storage, but did not save files to it. Instead, it started saving files to the actual internal SD Card, resulting in space running out pretty soon. The External SD card was just there, and there was no way to migrate the files from the internal storage to the adoptable storage.

I just got a new Note 4 (this is the 3rd one I'm using since the first release in 2014) and I also want to adopt external memory card as my internal space bcos the 16Gg duos version is just too small and app to SD comes with a lot of hassles. After a lot of search for different solutions (which I tried out by the way but didn't work) I came across this thread for another phone entirely but it resolved my issue: https://forum.xda-developers.com/galaxy-tab-s/general/patch-adoptable-storage-enabler-t3460478.
The only downside is that I can't pop out my card (128Gg Samsung) and plug into my PC but I can still explore it directly from the phone itself.
I've been using the phone for 3 days and it runs smoothly, I hope that solves your problem too.

So there are two parts to the adoptable storage. The first part is the partitioned SD card and mounting the partition. Simple to be done via root essentials or the command line.
The other part is the actual menu entry on an app in application manager for moving it to the second partition. IIRC samsung does not have this support built in. So you need to flash something to replace that manager bit. In my experience with an on5 (like less than 1GB free on internal storage out of the box), adoptable wasn't really worth it, too much stuff still on internal storage. As not every app will allow you to move it to that second partition. It requires both system support and app support.
What I did there was to use the app apps2sd. Same idea, second partition on SD card. But it doesn't show up in settings -> storage. You manage where the apps go via that app. I use the link feature which places a symbolic link in the internal storage and moves all the actual files to that sd card partition.

Will Rickards said:
So there are two parts to the adoptable storage. The first part is the partitioned SD card and mounting the partition. Simple to be done via root essentials or the command line.
The other part is the actual menu entry on an app in application manager for moving it to the second partition. IIRC samsung does not have this support built in. So you need to flash something to replace that manager bit. In my experience with an on5 (like less than 1GB free on internal storage out of the box), adoptable wasn't really worth it, too much stuff still on internal storage. As not every app will allow you to move it to that second partition. It requires both system support and app support.
What I did there was to use the app apps2sd. Same idea, second partition on SD card. But it doesn't show up in settings -> storage. You manage where the apps go via that app. I use the link feature which places a symbolic link in the internal storage and moves all the actual files to that sd card partition.
Click to expand...
Click to collapse
I've been using apps2sd fot about a year and it comes with it headache too, sometimes the apps wouldn't find the external data (usually games with a lot of data) and it'll start downloading it again into the internal memory, so I usually find myself having to force stop the app, delink and relink the data on the memory card to fix the bind. I also didn't bother to partition my SD card since I can explore it on the PC with my phone connected. What this solution ( https://forum.xda-developers.com/galaxy-tab-s/general/patch-adoptable-storage-enabler-t3460478 ) does is to flash back the option to use the SD card as internal memory that Samsung removed from the phones and it works seamlessly on all Samsung phones with rooted stock OS.

Link2SD or similar - SM-G360T

I've spent the last two days looking around online for different ways to use my SD card as internal storage in my phone. I was able to successfully root, but Link2SD, Int2Ext, and other apps have been unsuccessful, always with the same problem. Unable to mount. I've tried partitioning as ext2, 3, and 4, with no luck. USB debugging is enabled, as well as SU access on boot. I've checked every forum I could find (not many) regarding different ways to use an SD card as internal storage, but always get this same error. I've also tried searching for fixes to the "unable to mount" error, with no luck.
I'm feeling really stuck now. I feel like it should be much easier to use external storage this way, especially using android.
Does anyone have any experience/ideas that might help? (Besides buying a new phone.)

BarefootFlash said:
I've spent the last two days looking around online for different ways to use my SD card as internal storage in my phone. I was able to successfully root, but Link2SD, Int2Ext, and other apps have been unsuccessful, always with the same problem. Unable to mount. I've tried partitioning as ext2, 3, and 4, with no luck. USB debugging is enabled, as well as SU access on boot. I've checked every forum I could find (not many) regarding different ways to use an SD card as internal storage, but always get this same error. I've also tried searching for fixes to the "unable to mount" error, with no luck.
I'm feeling really stuck now. I feel like it should be much easier to use external storage this way, especially using android.
Does anyone have any experience/ideas that might help? (Besides buying a new phone.)
Click to expand...
Click to collapse
Yes. This is quite the problem for this device, as there is not really very much internal space. I tried all the same things that you did when I first got the device too. The problem is that the internal SD is emulated, which confuses apps like Link2SD and makes them think that the emulated internal SD(/storage/emulated/0/), which is an emulated mirror of the actual internal SD(/storage/sdcard0/), is actually the external, so you will get messages like, "No need to move the items as they are the same location." You would need to disable the internal SD emulation in order to ever hope to move your apps and/or system stuff to the external. This was actually done by someone for my last device, the LG L70. This guy made a flashable file that disabled the emulated internal SD, which allowed you to do whatever you wanted with your internal and external space.
http://androidforums.com/threads/di...oid-lollipop-and-partition-table-tool.921136/
In the meantime though, you can try and clear space in other ways. If you have the Xposed Framework installed(recommended), then you can use some Xposed modules to move some stuff to your external SD. More info on installing Xposed here:
https://forum.xda-developers.com/showpost.php?p=67909185&postcount=393
Some modules you can try which I use and I can say actually work on this device are:
- Downloads2SD: Allows you to change the default download locations for videos, music, pictures you take or download and other miscellaneous downloads so that they automatically go to the external. Actually does save a lot of space and time.
- Obb on SD: This is handy if you play games that take up a lot of space. It moves the sometimes huge Obb data folder for those to the external.
(NOTE: Both of these will also require you to install and run an app from the Play Store called SDFix by NextApp first.)
You can also flash SlimPickins rom, which is a completely debloated rom that takes up a lot less internal space:
https://forum.xda-developers.com/ga...rom-slimpickins-stock-rooted-bloated-t3250883
For more info on debloating and creating more space on this device you can also check out this old debloating thread I made too here:
https://forum.xda-developers.com/ga...oating-sm-g360t1-sm-g360t-easy-guide-t3260136
You can also search the Play Store for light alternatives to your current apps. A great example of one I use now is called "Swipe". It's a super light Facebook app that looks and functions exactly the same, but cuts off about 300mbs+ of the space taken up by the original.
In short though, there is really no other way right now to clear up space on the SM-G360T/SM-G360T1. Hope this helps!

bogarty said:
Yes. This is quite the problem for this device, as there is not really very much internal space. I tried all the same things that you did when I first got the device too. The problem is that the internal SD is emulated, which confuses apps like Link2SD and makes them think that the emulated internal SD(/storage/emulated/0/), which is an emulated mirror of the actual internal SD(/storage/sdcard0/), is actually the external, so you will get messages like, "No need to move the items as they are the same location." You would need to disable the internal SD emulation in order to ever hope to move your apps and/or system stuff to the external. This was actually done by someone for my last device, the LG L70. This guy made a flashable file that disabled the emulated internal SD, which allowed you to do whatever you wanted with your internal and external space.
http://androidforums.com/threads/di...oid-lollipop-and-partition-table-tool.921136/
In the meantime though, you can try and clear space in other ways. If you have the Xposed Framework installed(recommended), then you can use some Xposed modules to move some stuff to your external SD. More info on installing Xposed here:
https://forum.xda-developers.com/showpost.php?p=67909185&postcount=393
Some modules you can try which I use and I can say actually work on this device are:
- Downloads2SD: Allows you to change the default download locations for videos, music, pictures you take or download and other miscellaneous downloads so that they automatically go to the external. Actually does save a lot of space and time.
- Obb on SD: This is handy if you play games that take up a lot of space. It moves the sometimes huge Obb data folder for those to the external.
(NOTE: Both of these will also require you to install and run an app from the Play Store called SDFix by NextApp first.)
You can also flash SlimPickins rom, which is a completely debloated rom that takes up a lot less internal space:
https://forum.xda-developers.com/ga...rom-slimpickins-stock-rooted-bloated-t3250883
For more info on debloating and creating more space on this device you can also check out this old debloating thread I made too here:
https://forum.xda-developers.com/ga...oating-sm-g360t1-sm-g360t-easy-guide-t3260136
You can also search the Play Store for light alternatives to your current apps. A great example of one I use now is called "Swipe". It's a super light Facebook app that looks and functions exactly the same, but cuts off about 300mbs+ of the space taken up by the original.
In short though, there is really no other way right now to clear up space on the SM-G360T/SM-G360T1. Hope this helps!
Click to expand...
Click to collapse
Hi,
I have a Core PrimeSM-G361F with pre-rooted firmware and I am successfully using Link2SD.
Did you format and create two partitions on your internal microSD? I think this is necessary. Check out this tutorial:
https://awanstuff.wordpress.com/201...ink2sd-in-any-android-phone-with-screenshots/