Develop Bugs

upgrading micro sd card

Hey guys I just wanted to ask u all a question bout upgrading sd cards on the Evo. I just purchased a Lexar 32gb class 10 sd card from Amazon. I still hav the stock 8gb card that has all my data....music,movies,music videos,custom roms,kernals amd so on. I hav heard that some people are having problems with changing their cards. So my question is what is the proper procedure to getting this transfer to be successful. Is it better to format new card thru windows or phone? Do I need to partition the new card? What is the easiest procedure to transfer my 8GB card stuff to my new 32gb card. The reason Im asking is I dont want to corrupt the new card in anyway...as u all kno they are NOT CHEAP!!! I just want the transition to workout smoothly with NO problems. Any advice wud b much appreciated. Thanks Yall!!! Evo runnin MikFroyo v4.61 w/ netarchy-toastmod-4.3.4-cfs-havs-more-nososbc...overclocked to 1152mhz.

Copy the contents of your current card onto your computer or an external drive. Shutdown your device. Remove your current card and replace it with your new card. Make sure your device supports the 32 GB size. Reboot your device. Many cards already come formatted, however, it wont hurt to reformat it to be sure. When your phone finish booting up, go to the SD card and phone storage setting within the menu. Select unmount SD card. After it unmounts, the option to format it will appear. Select format. When finished, select mount. Back out of that menu back to your homescreen. Connect your device via USB to your computer or external drive and transfer the items you copied to your newly formatted card. Reboot your device when you're finished. You can also format from your computer and from within recovery. Take your pick.
posting & replying via the XDA Premium app.

If am not wrong EVO supports max 16 GB and EVO Shift is 32 GB

^You're mistaken, the EVO does support the 32gb.
Says so on the HTC support page for EVO
Whew, you had me scared for a moment... I just ordered the same 32 gb microSD this morning. :]

I've been through 2 lexar 32gb cards. Within a matter of weeks to days, I was getting data corruption. Not sure if it's limited to the lexar class 10 cards, or any class 10. It would appear to function fine at first. At some point during the day i'd go to check my email and get a sd card mounted in read only mode message on the status bar. Rebooting would usually not help. Had to hook up the phone to the pc, mount the sd in recovery, then run a chkdsk. I'd typically get many many corrupted files.
Now mind you, i'm always careful to shutdown properly, only mount the sd when recovery. I've come to the conclusion that there is some incompatibility issue either due to the size, or perhaps lexar's ability to be downward compatible with the slower speed devices (I think the evo can only take advantage of up to class 6 devices).
Lets hope you have better luck than I did, but after multiple corrupted files, I'm back with the stock card, which has caused no issues at all (besides being low on space).

i have 32g patriot class 10 card and it works great for me. i just transfered my old sd card stuff onto my computer via the card adapter it came with. i inserted and formatted my new card into my phone. and transfered everything from my computer tomy phone via usb.

Ditto on the formatting with the phone. Since i am using ext, it had to be via the phone as I don't have the right tools to do it in windows.
FWIW, with the initial lexar card, there were no problems for nearly 3 weeks. With the replacement card they sent me, issues started showing up 2 days later. Could be my phone is less tolerant of media quality than others..

one thing you need to remember when copying the files, is to hit the option to see the the hidden files on your sd card, if you dont your phone will have glitches because it will be missing those files, because when they are hidden they dont get copied

Hate to hijack here but it's along the same lines.
If I don't listen to music or take a bunch of pictures what if any difference will I notice upgrading my class? Sorry I am coming from a Vibrant that had 14gigs internal and the sc card was purely optional.
I was thinking about just getting an 8 gig class 10 if it would make a difference.

pc to dupe sd card?
Could you just copy the sd card using an adaptor to your pc hard drive, then copy the files onto the larger sd card, again using the adapter in the pc. then install the new sd card into the phone? I am new, to this, i'm just askin.

blairan...I think you wud b safe to do that but u must format the new sd card first via phone(itself) or thru windows before any transfer of data is made. My question was simply that I hav read that many people hav had complaints bout corrupted files being present thru their new cards. Or problems with "read only" errors and not being able to access things on the card. If u are rooted and are running a custom ROM that allows Apps2sd to help free up internal memory on ur phone then u wud also need to partition the card as well to allow that. I just dont understand why their have been so many people having these problems with the 32g class 10 cards.

blairan...Im pretty sure u wud be safe to do that but if it is a new card u must make sure it is formatted first via phone itself or windows before u transfer anything to it. My question was simply I dont understand why so many people have complained bout corrupted files and or read-only errors on the 32g class 10 cards. Problems that seem to arise days or weeks later after installing new cards. I wud really like to get to the bottom of it and find out why.

blizzard1017 said:
Hate to hijack here but it's along the same lines.
If I don't listen to music or take a bunch of pictures what if any difference will I notice upgrading my class? Sorry I am coming from a Vibrant that had 14gigs internal and the sc card was purely optional.
I was thinking about just getting an 8 gig class 10 if it would make a difference.
Click to expand...
Click to collapse
If anything, you'd probably notice quicker loading from apps that you've moved to the SD card. But admittedly, video, music, and photos are the places you'd see the most tangible improvement.

Doug,
I've tried this several times (I think I'm up to double digits, now) on my rooted Evo running the stock ROM. After I transfer all the files and reboot, several apps are not installed and the phone says it has a low amount of space. I've tried restoring a Clockwork Mod backup as well and I get the same thing. I have everything backed up in Astro, but when I try to install the missing apps, the low memory issue prevents them from being installed. Should I remove all my apps and start over? Should I un-root my phone and do a factory reset? I'm so frustrated I'm about to do the latter.
I'm upgrading to a 32GB class 10 card and I just can't figure it out. Any thoughts?

jmattix said:
Doug,
I've tried this several times (I think I'm up to double digits, now) on my rooted Evo running the stock ROM. After I transfer all the files and reboot, several apps are not installed and the phone says it has a low amount of space. I've tried restoring a Clockwork Mod backup as well and I get the same thing. I have everything backed up in Astro, but when I try to install the missing apps, the low memory issue prevents them from being installed. Should I remove all my apps and start over? Should I un-root my phone and do a factory reset? I'm so frustrated I'm about to do the latter.
I'm upgrading to a 32GB class 10 card and I just can't figure it out. Any thoughts?
Click to expand...
Click to collapse
No, you do not need to unroot, but I do recommend you start from scratch. Since you already have the contents of your card backed up to your computer, go into recovery and re-partition and re-format your card. In amon_RA select "partition SD card" from the main menu. You will be prompted to set a size for 3 different things. Insert a zero each time. Doing so will allow you access to your entire card. Afterwards, copy the rom you want to use to the card via the MS-USB or the Mount USB option, if using ClockworkMod and flash it. Your paid apps will be listed in the Market after you've logged in with your credentials. Your unpaid apps will have to be redownloaded and reinstalled unless you have them backed up to Google's servers or backed up with Titanium Backup. Anyway, you will have a clean install of your rom, a clean install of your apps and a freshly formatted and partitioned SD card. If you still get the low memory error afterwards then I am assuming you have too many apps on your internal memory and thus, you will need to move many of them to your SD card to free up your internal memory. There are tutorials available to learn apps2sd. Anyway, I hope this helps you.
posting & replying via the XDA Premium app.

Thanks so much. I'll give it a try.

jmattix said:
Thanks so much. I'll give it a try.
Click to expand...
Click to collapse
You're very welcome. Enjoy the rest of your holiday...
posting & replying via the XDA Premium app.

Problems Formatting SD Card/Working In Phone

I seem to be having problems formatting my Sandisk 64GB MicroSDXC (Class 10) card in FAT32 & having it work in my AT&T Galaxy S3. The card comes preformatted in exFAT, and it works in the phone just fine that way. But, I heard it's best to format it in FAT32 due to some issues I saw about some people having some of their music files not show-up (if they have a rather large music collection, which I do - 85GB's worth!) in whatever music playing program they're using, so I'm attempting to format it with FAT32 to avoid that. Now, Windows 7 (x64) does NOT allow you to format drives via FAT32 (unless you go into DOS), so I've used a couple of different programs (Fast32Format, EASEUS PartiionMaster); I got a message on my Galaxy S3 saying my SD card was damaged or missing when I used Fast32Format); a bunch of services stopped working on the phone when I formatted it using EASEUS PartionMagic, and I even tried formatting it in NTFS (which I think that Android doesn't support) & got a message my SD card was blank and Android wouldn't even mount it!
What am I doing wrong? How can I format it in FAT32 and have it work in my Galaxy S3?!! Do I even really need to use FAT32 instead of exFAT?
Thanks,
Dennis

dmw_4814 said:
I seem to be having problems formatting my Sandisk 64GB MicroSDXC (Class 10) card in FAT32 & having it work in my AT&T Galaxy S3. The card comes preformatted in exFAT, and it works in the phone just fine that way. But, I heard it's best to format it in FAT32 due to some issues I saw about some people having some of their music files not show-up (if they have a rather large music collection, which I do - 85GB's worth!) in whatever music playing program they're using, so I'm attempting to format it with FAT32 to avoid that. Now, Windows 7 (x64) does NOT allow you to format drives via FAT32 (unless you go into DOS), so I've used a couple of different programs (Fast32Format, EASEUS PartiionMaster); I got a message on my Galaxy S3 saying my SD card was damaged or missing when I used Fast32Format); a bunch of services stopped working on the phone when I formatted it using EASEUS PartionMagic, and I even tried formatting it in NTFS (which I think that Android doesn't support) & got a message my SD card was blank and Android wouldn't even mount it!
What am I doing wrong? How can I format it in FAT32 and have it work in my Galaxy S3?!! Do I even really need to use FAT32 instead of exFAT?
Thanks,
Dennis
Click to expand...
Click to collapse
EaseUS worked fine for me - the one thing that screwed me up the first time is when you tell it to format it, you also have to tell it to apply it. And hopefully the "Fast32" was autocorrect - you should just be using FAT32 - and I don't think I changed the block size. HTH

alacrify said:
EaseUS worked fine for me - the one thing that screwed me up the first time is when you tell it to format it, you also have to tell it to apply it. And hopefully the "Fast32" was autocorrect - you should just be using FAT32 - and I don't think I changed the block size. HTH
Click to expand...
Click to collapse
I apologize for bringing up this old-ish thread, but I always see that every time someone makes a new thread, they get bombarded with "use the search feature", so uhh, I did .
I've got a Class 10 SanDisk Ultra 64GB MicroSD XC card, that refuses to work with my Galaxy S3. I've got CM10 on it, do you think that might be the issue? If so, how do you think I can rectify it (what format would work?)
I've used EaseUS to delete the partition, and recreate using FAT32, but no dice, still getting a "damaged card" notification. I can seemingly use the card fine on my PC and my Mac, but nothing on the phone.
Any help would be greatly greatly appreciated

Vaesar said:
I apologize for bringing up this old-ish thread, but I always see that every time someone makes a new thread, they get bombarded with "use the search feature", so uhh, I did .
I've got a Class 10 SanDisk Ultra 64GB MicroSD XC card, that refuses to work with my Galaxy S3. I've got CM10 on it, do you think that might be the issue? If so, how do you think I can rectify it (what format would work?)
I've used EaseUS to delete the partition, and recreate using FAT32, but no dice, still getting a "damaged card" notification. I can seemingly use the card fine on my PC and my Mac, but nothing on the phone.
Any help would be greatly greatly appreciated
Click to expand...
Click to collapse
Well, this is ominous given that I ordered this micoSD and it just shipped. I read lots of reviews on Amazon and those with S3 phones seemed to have no issues using card as is, although they didn't specify precisely which version of S3 they had. The S3 natively supports 64 GB, so I would think it would work out of the box, so to speak. A number of reviewers said they used this microSD in older phones that supposedly supported only up to 32 GB. They formatted in phone, getting something like 59 GB of usable space.
I'm using stock ROM with CWM on I747.

cm10
it is an cm10 issue

mrky said:
it is an cm10 issue
Click to expand...
Click to collapse
A more complete response...its a known issue with AOSP based JB ROM's. This is pulled from the AOKP FAQ, since it is an AOSP based ROM as well this should help you out.
Will my 64 gb sd card work? Except it works fine with a 64GB card. http://rootzwiki.com/topic/28124-doe...card-standard/ The SGSIII is the first phone to support exfatl, but the support is Kernel based, some people are having trouble with the replacement kernels and exfat support. The solution is to force it to format in FAT32. http://www.online-tech-tips.com/comp...ive-to-fat-32/ I know, because I've done it. --- Don't respond without actually doing research. I have no problem spoon feeding information, especially when the information you put out there can increase misinformation. The SGSII also supports a 64GB card as well. http://androidforums.com/samsung-gal...ing-sgsii.html naturefreak85l;
EDIT - Apparently the links are dead, but there a many methods to choose from to format and SD in FAT32.

Tab 3 10.1 help with 64gb micro sd

OK my problem is I have the tab 3 10.1 with a 64gb micro SD card in it and the only way to root is to put a smaller SD card in because for some reason it can't read the 64gb micro SD card and when I want to make a backup in cwm it says it can't mount the 64gb micro SD card but if I use anything smaller everything works fine so my question is, is there a work around or some way to Make my tab 3 mount the micro SD because I'd like to install other roms and stuff but I'm not going to I till I can make a backup first. Also with the 64gb card in my tab 3 everything else works like watching videos stored on the SD or music on the SD, anyways any help with this issue would be much appreciated.
Sent from my GT-P5210 using xda app-developers app

you MIGHT have better luck if you format the SD card in some other file system. Other than that I'm not sure
You could buy an 8 gig one and swap it too

DopeShow said:
OK my problem is I have the tab 3 10.1 with a 64gb micro SD card in it and the only way to root is to put a smaller SD card in because for some reason it can't read the 64gb micro SD card and when I want to make a backup in cwm it says it can't mount the 64gb micro SD card but if I use anything smaller everything works fine so my question is, is there a work around or some way to Make my tab 3 mount the micro SD because I'd like to install other roms and stuff but I'm not going to I till I can make a backup first. Also with the 64gb card in my tab 3 everything else works like watching videos stored on the SD or music on the SD, anyways any help with this issue would be much appreciated.
Sent from my GT-P5210 using xda app-developers app
Click to expand...
Click to collapse
Have you tried both recoveries? CWM and TWRP if neither work you may have to format to fat32.
Sent from my GT-I9505 using XDA Premium 4 mobile app

Yes I've tried every recovery out there and with cwm it does this count down from 10 that says connecting then after it gets to 1 it says aborted because it cannot mount the micro SD and yes its formated to fat32 and I've tried exfat and every other format nothing works, and in my first post when I said I couldn't root from the micro SD I mean by going into cwm and loading zip file from there it does the same thing and says it can't connect, that's why everytime I root my device this way I have to borrow a 32gb micro SD and everything works fine
Sent from my GT-P5210 using xda app-developers app

Same problem with my 64g card. MY 16g works great. Cant seem to get the 64g formatted in either my phone or the Tab3. I can sometimes get the Tab3 to recognize the card and it will show the files on the memory card but once I go into recovery there is nothing there.

My 64gb card is recognized while the device is in regular running mode like I can go into settings and then storage and see the card there and how much space is used and free the Only time the card doesn't work right is when I'm in recovery mode because for some reason in recovery mode the system says it can't mount it and that is my whole problem, I need a way to fix it so my 64gb card can be mounted and used while in recovery mode.
Sent from my GT-P5210 using xda app-developers app

It's either a recovery issue or a driver/kernel/bootloader issue, a case that the Tab 3 10.1 development is far from being active.
It looks like it can't allocate space that exceeds 32GiB.
Also wrong thread.

Trying formating your SD card on the computer to fat32 or extfat .
Sent from my GT-I9505 using XDA Premium 4 mobile app

I've already done that and the card works fine example in the device it only stops working in cwm recovery saying it can't be mounted
Sent from my GT-P5210 using XDA Premium ANDROID Developer's App

Thread cleaned of off topic posting and unnecessary non-related junk.
(yes, we can do this)
Any more silly ridiculous junk posted, and this thread will be closed permanently.
If the OP wants to keep this in open forums, we cannot prevent this and welcome the debate, as it seems fitting.
Cheers
MD

My thoughts...
Running the tab in normal mode allows the 64gb card to be read. However, if you start in CWM or TWRP recovery, you are no longer in the "normal" mode and the tab does not recognize the 64gb card. In recovery mode, it is possible that the memory allocations are limited where as in normal mode, 64gb is OK.
In this case, for rooting, maybe you should load the root file on internal memory and not the memory card. I use 4gb cards and neither CWM or TWRP could work with them. I think the issue is in the recovery programs and not the Tab, save for memory limitations set by the base firmware.
Again, JMHO and I may be way out in left field here.

TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.

GorillaPimp said:
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
Click to expand...
Click to collapse
yes ive tried multiple recovery's and they all do the same thing and cannot read the 64gb micro sd and yes I have my sd formatted to fat32 and I am on windows on my laptop but I can format the micro sd to ext3 or 4 but my question is, if I do that and its formatted to ext3 will I still be able to access my tablets drive space through my laptop like I can now with it being on fat32, because if I cant then that would be pointless for me to do because then I wouldn't be able to add and take things off my sd while its in my tablet., also I said in my first post that this problem doesn't happen using a smaller micro sd like 32 or smaller it only happens with the 64gb, so it has to do with the size some how

GorillaPimp said:
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
Click to expand...
Click to collapse
also IDK if you know this but there isn't many recovery's out there for the galaxy tab 3 10.1 the only one I use is bindroid_cwm_p5210_santos10wifi and even with this recovery it has a slight lag to it when using it.

Unable to move apps on SD Card after 6.0 update

Hello,
After upgrade and factory reset and micro-SD format, I am unable to move apps on the SD Card of my LG G4 H815.
I know that some can't be moved, but some can, and I am unable to move some games that before I was able to move, because I don't get that option. I also tried with a different micro-SD, although the card worked just fine before the upgrade.
I just don't get that options - I don't even get the option to format the external SD as phone memory, as I know it should do.
I wanted to post screenshots but I can't, because I'm a new member, so I'll try to explain:
- I go to Settings - Apps - choose a game - storage - there are only 2 options, clear data and clear cache
-I go to Storage - SD Card - settings - (here I have only Eject and Format, and if I choose Format, the only option I have is format as portable storage)
Did anyone faced a similar problem? I digged around bout couldn't find anything like this.
Thank you

I have the same problem, wen i upgrade to 6.0 i have some games with the option to choose were the data goes, less than 5.0 but i can move few.
I hard reset to stop batery drain and now i cant move any data from apps to SD card.

Same problem here! Even link2sd doesn't works...

Did you format your sd card as portable/external? How did you format your partitions and what formats when you tried link2sd?

Just tried it link2sd works for me using Fat32 on first partition and second one ext2. It had to reboot once but I guess it has something to do with my systemless root as it simply dissappeared and I had to reroot again.

The only option is portable in the format on the phone. I was under the impression under marshmallow you would be able to format either to portable or internal.

Just checked move 2 sd isnt showing up in options my guess it has something to do with the new internal/external feature, did not test with link2sd only linking tested and that works for me. I guess that you can only format as external is caused by stock rom. After all I have read internal seems not to be a good choice for mobiles with enough internal storage

Link2sd was formatted as ext4 that worked on lolly, but the big problem is I formatted as external (only choice) and the "move to sd" button does'nt appear at all! Maybe I should format all the sd as ext4? In a nutshell the 20B is using my sd as an otg storage, can read and write, but not considered by games and so (luckily the camera srill save pics and vids on sd).as far as I can see there is only thi thread and we are the only one thata have this problem!

I search about it and seems, LG dont implement 6.0 feature to use SD as internal memory if SD card have the minimal speed requirements

Try ext2 on second partition then it will work. I only have the problem that it wont mount at reboot, I always have to wait after complete boot and some time more until it recognizes second partition and mounts it. Perhaps an issue with systemless root (supersu 2.65beta) I am using but as long as no system apps are linked there is no problem with this (and I dont reboot often)

Ext4 on link2sd used to work, but in 6.0 (20b) it looks like I deleted a lot of "trash" so I was able to reatore all the app without link2sd and I would like not to use it, just to move app to mi samsung64gb sd to save other internal space for the future.I know it doesn't move the complete app, but one day maybe you will need even just 5mb...never say never....and one day you may need even just 5mb of internal memory...never say never... anyhow it store lictures in my sd, so I'm really afraid is about a limit of the rom or the memory card (I miss the format as internal memory too, while someone has that option on G4, am I wrong?) I have the classic silver 64gb samsung micro sd not the ultrafast version I used to make 4k vids on my old S5!

I personally bought link2sd as the old move 2 sd didnt work well with my samsung galaxy tab s, most apps crashed but using link2sd they worked (not all but most of them). As for SD card I have a sandisk ultra 128GB and no problem recording 4k to it, I use the mod with the highest bitrate from the forums here

alxtraxxx said:
I personally bought link2sd as the old move 2 sd didnt work well with my samsung galaxy tab s, most apps crashed but using link2sd they worked (not all but most of them). As for SD card I have a sandisk ultra 128GB and no problem recording 4k to it, I use the mod with the highest bitrate from the forums here
Click to expand...
Click to collapse
I was talnkig about my SD not to say if I can record or not 4k (we are off topic here), but just to say that is NOT the ultrafast that samsung requires for recording 4k video without modding.
I just mean that now I have a "Samsung MB-MP64D/EU Micro SD XC EVO, UHS-1, CLASS 10 orange/wite" not the "Samsung MB-MG64D/EU micro SDXC Pro 64Go Class 10 UHS-I silver".
The latter was required by samsung to record 4k video=superfaster compared to the hal priced one I have.So, MAYBE, the SD does the difference in Marshmallow, it detects the kid of SD and allow us to use it as internal memory and/or to move the apps on the sd without the Link2SD app (for the record, I used ext4 withou problem with lollypop, now Link2SD doesn't find the partition, I won't waste time trying other ext till my phone will be full).

Link2SD - Not Mounting 2nd Partition after over a month of it working fine

Have been using Link2SD now for over a month without any problem.
I have a 64 GB micro-SD card formatted with 2 partitions. One is the fat32 partition for storing my own stuff (accessible through file explorer), and the other is an ext2 partition that is meant for Link2SD to "link" apps to. Both partitions are roughly of equal size (though in hindsight I would have like to make the ext2 partition smaller). I formatted + partitioned the SD card using MiniTool partition wizard in Windows.
As of yesterday the 2nd partition is not being mounted any more. I get the error as in attached screenshot. This error comes after Link2SD asks me to select what the file format of the 2nd partition is.
Because of this, all of the apps that are linked to the SD card in some way are now showing as not installed on my device (most are games, but one is a magazine-reading app). An attempt at reinstalling 1 or 2 of these apps through google play results in an error saying something like "there was an error installing this app".
I tried to search the forums on this error but most people have similar issues only when they are ~starting~ with Link2SD. I haven't found anyone who has the issue like this after using Link2SD for a bit of time...
I am wondering if there is a workaround to this. It would be nice to get those apps back onto the device at the very least (I have 4 GB of space to spare...), and at the very best get everything back to working condition again.
(note: I started to notice that certain apps started naming the SD card as a bunch of symbols instead of "SD card" as they usually do.....not sure if this is related or not)

*bump*
Should mention that I"m running a rooted device with stock ROM (took out many of the built-in apps).
I am debating whether to unmount the SD (physically take it out), and reformat the 2nd partition to ext4 or FAT32 and try again with Link2SD
What I'm afraid of is losing all those apps and not being able to reinstall them again....(as I am already getting errors with this in Google Play)

bsquared938 said:
*bump*
Should mention that I"m running a rooted device with stock ROM (took out many of the built-in apps).
I am debating whether to unmount the SD (physically take it out), and reformat the 2nd partition to ext4 or FAT32 and try again with Link2SD
What I'm afraid of is losing all those apps and not being able to reinstall them again....(as I am already getting errors with this in Google Play)
Click to expand...
Click to collapse
I've been having issues with it for a while myself. Sometimes after a reboot, a whole lot of apps disappear. I give it another reboot and they come back, but it's a pain in the arse because then I need to manually go place them back onto my home screen.

mightbme said:
I've been having issues with it for a while myself. Sometimes after a reboot, a whole lot of apps disappear. I give it another reboot and they come back, but it's a pain in the arse because then I need to manually go place them back onto my home screen.
Click to expand...
Click to collapse
I have tried multiple reboots....no such luck.
I'm reading elsewhere that the culprit may be Link2SD itself. Have emailed the developer (hopefully they respond).
The ext2 partition on the card is officially or unofficially fried. I really can't see anything on it (tried several linux file system viewers). I guess I'll keep the card mounted (with half the space technically gone) until there happens to be some way to deal with this issue....

bsquared938 said:
I have tried multiple reboots....no such luck.
I'm reading elsewhere that the culprit may be Link2SD itself. Have emailed the developer (hopefully they respond).
The ext2 partition on the card is officially or unofficially fried. I really can't see anything on it (tried several linux file system viewers). I guess I'll keep the card mounted (with half the space technically gone) until there happens to be some way to deal with this issue....
Click to expand...
Click to collapse
I ended up using a new card and the problem disappeared.... I'm guessing that the problem is with your card. Good luck

mightbme said:
I ended up using a new card and the problem disappeared.... I'm guessing that the problem is with your card. Good luck
Click to expand...
Click to collapse
I tried Link2SD with 3 different SD cards.
One was a test (4 GB card or less, can't remember now), to make sure the program worked.
The other was an 8GB card. Which I eventually swapped out for...
...a 64 GB card.
I had manually partitioned the 8 and 64 GB cards prior to using them in Link2SD
I also re-partitioned the 64 GB card a 2nd time when Link2SD (and therefore my tablet itself) stopped seeing the 2nd partition on the 64 GB card.
This "breaking" problem came up on both the 8 GB and 64 GB cards.
So one of the following at fault: my tablet, 2 different SD cards, or the app itself.
I am inclined to believe it's Link2SD as the reviews on the app store say similar things to what my problem is.