After i updated to froyo during the pre-release days its been taking a MUCH longer time to mount my sdcard to my desktop. It can take up to a minute or longer when in the past it only took a few seconds, just like any standard USB flash drive.
I tried formatting the sdcard via the phone, but when i click "unmount sdcard" it just says unmounting sdcard and it stays that way forever. I exit the screen and go back, and i have to press unmount sdcard again which delivers the same results. So for some reason i can no longer unmount my sdcard via the phone. So i tried mounting the sdcard to my desktop, backed it up, and formatted it via windows before copying back all my files and apps. I tried mounting the sdcard to my desktop again but it still takes forever to mount.
To ensure the sdcard isnt damaged, i took it out of the phone and plugged it into a card reader. Windows detected the sdcard immediately and behaves just like how its supposed to.
So whatever the problem is, it lies with the phone itself. I tried googling around for answers but found none. Any help would be appreciated.
Running stock N1 on FRF91.
BUMP
No one really? :/
You using apps2sd? If so, it has to do lots of mount/unmount work, one mount per program moved.
It makes it much slower to prepare the drive for the PC and to return it to the phone. Since going to apps2ext on Enom's rom it's as fast as it was on 2.1 before apps2sd.
khaytsus said:
You using apps2sd? If so, it has to do lots of mount/unmount work, one mount per program moved.
It makes it much slower to prepare the drive for the PC and to return it to the phone. Since going to apps2ext on Enom's rom it's as fast as it was on 2.1 before apps2sd.
Click to expand...
Click to collapse
Yeah i shifted 100MB+ of apps into sdcard, i have to if not i wont have any space in my internal memory. And all of that is causing it to slow down? So is there any work around to this?
The more the app on the sd, the slower the USB mount... the system look for all active/background apps installed on the sd and terminates them before mounting...
The workaround (the better solution, actually) is to use Apps2SD+ method (EXT3 partition for data) instead of regular Froyo Apps2SD.
Jack_R1 said:
The workaround (the better solution, actually) is to use Apps2SD+ method (EXT3 partition for data) instead of regular Froyo Apps2SD.
Click to expand...
Click to collapse
Damn but i need to root first right? So im pretty much screwed until my warranty is up. Because i'll definitely push more apps into my sdcard to free up space.
You need to root, and you can root without unlocking - which means preserving your warranty (not that it matters - phones with unlocked bootloaders are repeatedly reported as serviced with no charge, as long as they have known HW problems)
Jack_R1 said:
You need to root, and you can root without unlocking - which means preserving your warranty (not that it matters - phones with unlocked bootloaders are repeatedly reported as serviced with no charge, as long as they have known HW problems)
Click to expand...
Click to collapse
Ahh i see. Thats good to know, I'll take note of that. Thanks. Maybe i'll go check it out.
Related
subj: are you gonna include good old apps2sd in your 2.2-based custom roms, or are we stuck with the new fancy apps2fat?
thanks
I hope so the new apps2fat kinda sucks
-------------------------------------
Sent via the XDA Tapatalk App
why does it suck? surely its no real difference? both are stored on the sd card and im not sure I am right but you dont need the ext partition now?
am i missing something?
ryl3y said:
why does it suck? surely its no real difference? both are stored on the sd card and im not sure I am right but you dont need the ext partition now?
am i missing something?
Click to expand...
Click to collapse
As devs update their apps to take advantage of and work with the new features I think the offical way will be fine.
Only real drawback I can see right now tho as compared to the apps2sd we are used to is the fact the apps are now on the FAT32 partition. This means anything you have moved to SD will not be available while your phone is mounted to PC via USB cable. That's the biggest advantage to the "older method" with it's EXT partition, so you could mount your phone to pc and still use the apps that are on your sd card. This simply will not be possible with the official method.
gIMpSTa said:
As devs update their apps to take advantage of and work with the new features I think the offical way will be fine.
Only real drawback I can see right now tho as compared to the apps2sd we are used to is the fact the apps are now on the FAT32 partition. This means anything you have moved to SD will not be available while your phone is mounted to PC via USB cable. That's the biggest advantage to the "older method" with it's EXT partition, so you could mount your phone to pc and still use the apps that are on your sd card. This simply will not be possible with the official method.
Click to expand...
Click to collapse
this
AND for me the biggest advantage of app2sd was the ability to do a painless wipe (to change different roms for ex.). Im not sure it will work same way with fat.
So my phone got stuck at boot screen. Bell says I get full replacement, but I'm gonna lose all the data. I have the internal full of children opening gifts on Christmas.
Reading a million forums. Tried to learn enough to flash the firmware with odin. Tried flashing the stock JH2 back to phone. Phone boots to recovery and says problem mounting SD.
Can ADB be used to connect to phone in "Download mode" to Pull the media???
PLEASE PLEASE help?????
after odin is done the phone reboots to:
E:Can't mount /dev/block/mmcblk0p1
(no such file or derectory)
E:copy_dbdata_media: Can't mount SDCARD:\copy default media content failed
I'm still desperately trying to get my files. I've read about 1254 more threads. Found this one about flashing back to eclair...
http://forum.xda-developers.com/showthread.php?t=797302
So far I tried JH2, JL2, JM8 and still no luck. Anybody out there got any ideas?? links to help or compassionate remarks?
Phone no boot need remove files inside...is this really an impossibility??
Argh.... it never happens when the internal has useless data aye.
You tried flashing a firmware using all three files (PDA, modem, CSC) with repartition?
P.s. apologies if you have tried all this, just trying to establish a baseline
Sent from my GT-I9000 using XDA App
From what i understand the internal SD card has 2 main partitions. One that's about 2 gigs for Android OS and apps and the remainder of the card stores media and such. (I think that's correct) So I've tried carefully to just poke around the OS area of the SD card in hopes that I can get it to boot up just once to connect and get the pictures off it. I'm fairly sure that "re-partition" would erase the whole card.
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Hoodmin said:
From what i understand the internal SD card has 2 main partitions. One that's about 2 gigs for Android OS and apps and the remainder of the card stores media and such. (I think that's correct) So I've tried carefully to just poke around the OS area of the SD card in hopes that I can get it to boot up just once to connect and get the pictures off it. I'm fairly sure that "re-partition" would erase the whole card.
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Click to expand...
Click to collapse
Repartition only erases the 2GB portion, ive done several repartitions and it never touched my personal files on the internal SD
Hoodmin said:
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Click to expand...
Click to collapse
That won't work...the 'internal SD' is not a SD card in the traditional sense (standard, mini, micro) - it's a physical chip (IC) that's soldered on to the mainboard.
I haven't heard of anyone being able to pull data off a phone that's got the mmcblk0p1 failure. The best I've heard is of people repartitioning/formating the sd memory in order to get it working again - but of course, that would mean losing all data...sorry...
As what EarlZ said, repartition won't touch the part of the SD dedicated to user data. I've flashed via Odin countless of times and never once did my internal SD get wiped with a repartition so why not flash to something like JPU with repartition using 512 pit file?.
Edit: and reading the error seems to tell me it's a problem in the 2GB portion of the internal SD where the system and such get stored. So yes, do try a repartition. I guarantee you that your user data will be safe. The only time it would get wiped is if you actually choose to format that partition like how one does in Windows or through the settings. Odin flash won't do this most definitely.
If that fails...
Also take a look at this...
This guy seemed to have been lucky and got is supposed dead I9000m SGS working again. Here's his procedure:
http://forum.xda-developers.com/showthread.php?t=905975
Worth a shot.
Well hot damn them are some good replies. I was brave enough to try re-partition and a few mod roms like in the thread mention as well as a few thread techniques I read. I must have read about 4622 threads by now. Still no luck for me I really really appreciate the help.
Thinkin I might just go wrap up the kids christmas presents tonight while they sleep and just make em open them all again hahaha.
In the mean time I'll just keep readin and keep tryin. Learned a lot at least.
So....
Original problem = boot cycle
-I flash back to JH2 and at least to phone gets to recovery mode and i see the mmcblk0p1 error. progress
-try flashing to the newer JL2 and it goes back to boot cycle
-try flashing back to JH2 to get recover mode again and still boot cycle
-read a million forums about trying mod roms and other techniques and still boot cycle
-get encouraged that re-partition will only affect OS side of SD card and try a million things again. Still boot cycle
-decide to go back to the JK4 that i started on and seems to be the root of all evil and then BAM recovery mode returns and this time it even recognized the device
-any attempt to connect with device either with kies or windows explorer causes PC crash
-phone even recognized by ADB I "think" this program could be used to try and "pull" media from the device but that's just a guess and I don't know how to use it
-the error now is not mmcblk0p1 instead: E:Can't/b mount /devlock/stl10 which could mean something or could be just the same and it leads me to this thread: http://forum.xda-developers.com/showthread.php?t=788850
-try flash techniques in the thread and back to boot cycle
-try going back to the JK4 so I have recovery mode again and still boot cycle. progress gone
I'm gonna flash this damn thing again and again until the damn copper lights on fire
Wow i Admire you man.Listen i dont know much about ADB but i think i saw a post of someone that literally pushed files in his internal card with it,and i clearly remember him saying he could browse through his phone although its card was burned.If so then a single copy would be possible.Since i cant help more,you better start reading on how to use it and find basic commands for it.
I wish you the best man!!!!
Have you tried this kernel: http://forum.xda-developers.com/showthread.php?t=901772
I seem to be able to get that running on my dead GT-i9000M. It has a file browser so maybe you can see if your pictures are even there/accessible. Also has a USB Mass Storage option but it didn't seem to work for me.
However, phone is still dead and needs to go in for repairs/replacement.
OK so now I'm f&*#ed
Tried JP1 method from this stupid page
http://briefmobile.com/how-to-android-2-2-on-galaxy-s
and now I don't have download mode anymore.
somebody plz just shoot me
EDIT: Ok excuse this panic post. I still had connection to ADB and a simple "adb reboot download" command got me back.
Wow thank JDROM. This recovery mode really looks promising. I got the file manager working but I can't seem to find any directories with DCIM/ label or any media. Sure looks like this could help me somehow. Might only have half the SD mounted or something. I'll have to play around and read some more, but I gotta say this is the best progress I made in a while.
THanks SO much
Edit: Found in File manager to run partition manager and formating options show up. In here there is mounting options to /mnt/sdcard or /mnt/external_sd except when I try it returns the E:Can't mount /dev/block/mmcblk0p1 to /mnt/sdcard with parameters vfat(null) So hmmmm....
Edit: Also learned a bit more about ADB commands to possibly ""Adb pull /sdcard/DCIM"" if I ever get it mounted.
Well that's it for me. The quest is over. I admit defeat. Memories Lost. Game Over
That sucks man...i had a bunch of stuff on my phone that i lost when the internal died....mine took out the external sdcard i had in it too - so all my backups were destroyed as well!
Moral of story: Save important crap on something like dropbox!
Some dev should make a program that automatically syncs certain directories (like pictures, or backup folders) to dropbox. I'd donate for that.....
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Same problem!
i do have the EXACT same Problem!!!! Any solution jet?
Got a similar problem with my Galaxy Tab... Anyone found a solution yet?
friend of mine has a htc and uses a program called superwipe
http://forum.xda-developers.com/showthread.php?t=834812
dont know if it will work on the galaxy s though, but coukd be worth a read through the notes and posts
Wow . I have a similar problem. Although EVEN more troublesome.
Inaddition to all this
I cannot even DELETE the alarms taht i set before having this problem. I cannot Install the apps as well.
Uninstalling the ones - and they reappear the next time I boot.
Need Serious HELP on this.
My phone is restricted to ONLY making calls and sms. Thats all.
I have the *EXACT* same issue here. Only with a Sprint Galaxy Tab. My reboot is fresh and gives me "nothing" every time I boot no matter how much I configure. I can't write anything to the internal SD card or make any new folders.
jrhsu529 said:
I have the *EXACT* same issue here. Only with a Sprint Galaxy Tab. My reboot is fresh and gives me "nothing" every time I boot no matter how much I configure. I can't write anything to the internal SD card or make any new folders.
Click to expand...
Click to collapse
I have a different problem. My internal sd seems slow. Anyway, I must feel lucky.
If you look at page 15 of the following datasheet, you will notice that the moviNAND can be set in a "write-protect" mode:
http://web3032.sh1.magic2008.cn.m1.magic2008.cn/uFile/3032/201144131545503.pdf
See if you can read the CSD register data on your phone, and mingle with it.
Good luck.
Any one fix this
Any one fix this I have the same problem
Yesterday I gave the soluction, but someone deleted my post.
EDIT!!
Sorry, I wrong topic!!!! Sorry!!!!
superandroid2011 said:
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Click to expand...
Click to collapse
Looks like my problem as well
http://forum.xda-developers.com/showthread.php?t=2155644
To test quick go development->>launch tools->>bad behavior->>crash the system server.
Your device will reboot and you will have both in/ext sdcard (if its the same prob).
damgood said:
Looks like my problem as well
http://forum.xda-developers.com/showthread.php?t=2155644
To test quick go development->>launch tools->>bad behavior->>crash the system server.
Your device will reboot and you will have both in/ext sdcard (if its the same prob).
Click to expand...
Click to collapse
I have the same problem, cannot even use the phone as it FC any apps after boot. And no changes possible to the sdcard.
Have you found a solution yet?
DerBusisVoll said:
I have the same problem, cannot even use the phone as it FC any apps after boot. And no changes possible to the sdcard.
Have you found a solution yet?
Click to expand...
Click to collapse
Sorry - no - I had to start from scratch, my thougt was too many files on the ext card But I not sure and cannot recall - My phone is working good now. Only advice is to reinstall from scratch
I am also facing the same problem on my galaxy nexus after upgrading to KK using custom ROM. Any solution?
Does anybosy able to doanload the superwipe?
superandroid2011 said:
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Click to expand...
Click to collapse
Galaxy Tab 2 running on blisspop rom
I have to reboot every time this happens. The error message in mx player shows cannot write to internal sd..
Es xplorer cannot delete any item. Terminal emulator shows mount as read only
Any way to fix this?
Hello,
With the issues I was having with the CM 10.1 nightlies, much as I would like to stay, I decided to install the Minimoto 1.7 ROM into the second ROM slot (created with Safestrap 3.05). First, let me say "wow!" I never thought I would see this much speed and available RAM on my Droid 3. Thank you very much, thingonaspring.
For the most part, everything is working great *except* access to both the sdcard (internal) and sdcard-ext (external) storage areas. I read many posts in the Minimoto thread and searched around but nobody else appears to have encountered this which I find rather odd.
After the initial install and after reboots, these areas were still not accessible. I finally ran the terminal emulator and found that, for some unknown reason, they were *not* mounted. I *did* find the internal storage (/dev/block/emstorage) mounted at /ss but not at /mnt/sdcard. I became root using "su" and did the following:
# mount /dev/block/emstorage /mnt/sdcard
# mount /dev/block/mmcblk0p1 /mnt/sdcard-ext
Now I can access them along with all of the files I previously had there. The included file manager, when started, presents buttons for "Internal Storage" and "SD", but it still complains that internal storage is not mounted. It will allow me to access the SD card, though.
Under Settings->Storage Settings, everything under "Internal storage" and "SD card" says "unavailable" and both the mount and format buttons are grayed out. Yet, under the "Windows Media Sync" heading, I *can* choose between internal and SD *and* it even shows the correct available/total space values.
Why were these not mounted to begin with? Is mounting them manually an acceptable solution? If it is, where do I put this information so that it occurs at boot like it should (there is no /etc/fstab on Android)? Did I perhaps do something wrong when installing this ROM, maybe because I used ROM slot 2 instead of 1 (which still contains the most current CM 10.1 nightly)?
I really want to get this resolved because, so far, everything else appears to work wonderfully. Even 3g access, which I still haven't gotten working with CM 10.1.
--John Gruenenfelder
I've been running Minimoto for months and both /sdcard and /sdcard-ext are mounted at bootup for me, always, just like stock.
So, I wish I could tell you why, but I cannot.
I guess what I would do is start over. Reboot into Safestrap, remove that second slot and recreate it. Flash the ROM and restart the phone. Do not wipe data/factory reset after flashing the ROM or you will be missing some files (basically, some files required by the customized initial setup application.)
It seems to be fixed! See below for (perhaps) how...
Okay, I gave this a try. Rather than wiping ROM-slot-2, I had enough free space to create slot-3 and I reinstalled Minimoto 1.7 there. Also, this time I downloaded the zip file on my PC and transferred it over rather than downloading it directly onto the phone. Using the UNIX "cmp" tool told me the two files were identical, but I still used the "new" one. It installed fine and I did *not* perform a data wipe.
Unfortunately, same issue. When the device starts I can see the "Preparing XXX storage" messages appear in the notification bar for both internal and SD storage. There are no error messages, but it also did not actually do anything. Then, using the terminal emulator, I gave a long read through the dmesg output. I am more familiar with the kernel messages one sees when booting Linux on a PC, but I still did not see anything unusual.
So, back into Safestrap recovery. This time I tried something different. First, I noticed that the Safestrap file manager *can* see both storage areas and in the locations where they ought to be. This is not new, actually, it has always been the case. Second, I uplugged the USB cable. I have been using it for charging (of course), but at present it was plugged into my laptop and not into the wall charger. Depending on how the mounting occurrs and the exact mount order, I thought this might interfere. Thirrd, and finally, I used the "Fix Permissions" button available in Safestrap on ROM-slot-2 where I had first intalled Minimoto.
After doing these two changes I rebooted the device back into ROM-slot-2. Surprise! I once again saw the "Preparing" messages in the status bar except this time it really worked. The two storage locations are available where they should be and I an access the data just fine. Even the "Storage properties" screen in Settings shows both as mounted with the correct available/total space values given.
Since a plain reboot did not work previously, I have to assume one of the two changes I made fixed the problem, though, since I did both at the same time, I cannot be sure which fixed it.
Now I can get back to enjoying the impressivee speed from Minimoto while I wait to see if (or perhaps when) either the 3g or HW keyboard ALT-key issues are fixed in CM 10.1. Of course, given how much slower CM 10.1 operates (by virtue of using *much* more RAM than Minimoto), I think I might find it very difficult to switch.
--John Gruenenfelder
If you've been trying to hoot while plugged into your laptop I can see it causing issues as when usb mass storage is active, the device can no longer see the sd cards. That is why we have a separate data partition for apps and app data. So if the computer is trying to mount them and denies the phone the ability to mount then I could see issues arising
Sent from my XT860 using xda premium
Hello.
Its been a while and I've been using the SD as an internal memory for a while. While I love this feature there is a very weird thing with this feature that if you move an app to SD and if it gets an update, it gets moved back to the internal storage which is slightly inconvenient. However more inconvenient is the fact that all the app data gets lost in this updation procedure.
Would any kind soul suggest a workaround or a script to get around this annoying glitch? I mean I really love this feature but it obviously needs polish from Google.
Also another thing is while shifting these apps back to SD, it sometimes says not enough space (despite having lots of it). On the second try it shifts. Any idea what's up with this?
Thanks!
I am having the exact same issues and the same complain.
Being on a device having only 4GB of internal storage (that too only 2.28 GB usable) this "adopt as internal" feature in Marshmallow really came as a boon. However with these issues the whole idea becomes worthless.
I did a bit of search on Google about this feature. For nexus phones on marshmallow there is a "Migrate data" option to the SD card adopted as internal. However this is not available for our devices. It only shows up in the internal storage and lets you migrate from SD to internal? Grrrr....what good would that do?
Any kind of workaround would really help and convince me to keep this phone for another year maybe
I think you're getting confused. We too have the same option but this moving back to the internal storage on updation is something Google needs to address..
psiknight99 said:
I think you're getting confused. We too have the same option but this moving back to the internal storage on updation is something Google needs to address..
Click to expand...
Click to collapse
Since google's nexus phones lack sdcard slots, this feature was probably introduced keeping android one series phones
in mind, however there is so much confusion regarding it's objective at the moment,for it is only partial implementation of sdcard as internal memory. After updates I am aleardy down to 500mb space on internal storage, the point is if despite using sdcard as internal storage if my original storage space still runs out--what purpose does it serve then? I would have used link2sd otherwise,but this feature put me like many others in dilemma.
Yeah mate, really disappointing..
I have the exact same problem
What was google thinking before releasing this half finished feature
I hope there is an update soon to fix this problem
Some apps disappear after reboot
After moving apps to sd, apps like mxplayer, Microsoft word etc just disappear.
They are automatically uninstalled.
Can anyone confirm this??
Also it would be great if someone finds a workaround these problems
Yup Firefox disappears everytime I install it. So do many other apps..
psiknight99 said:
Yup Firefox disappears everytime I install it. So do many other apps..
Click to expand...
Click to collapse
This is so not cool man.
Whats the use of this feature if apps keep on disappearing
My observation is that the apps which directly get installed on SD card have these issues.
The apps that gets installed on internal first and then moved to SD, survives reboot.
Maybe app developers can make changes to their apps to support this functionality.
Clearly a half assed attempt from Google on this..I re-flashed my ROM and didn't chose the portable storage option. Link2sd doesn't work on Marshmallow yet so I'm just stuck with a typical 4GB internal memory crap phone.
psiknight99 said:
Clearly a half assed attempt from Google on this..I re-flashed my ROM and didn't chose the portable storage option. Link2sd doesn't work on Marshmallow yet so I'm just stuck with a typical 4GB internal memory crap phone.
Click to expand...
Click to collapse
I hope that from here on this feature will only improve.
Lets pray that bugs will be fixed soon, and google doesn't scarps this project like other projects.
I am still using it as phone storage.. well something is better than nothing
psiknight99 said:
Clearly a half assed attempt from Google on this..I re-flashed my ROM and didn't chose the portable storage option. Link2sd doesn't work on Marshmallow yet so I'm just stuck with a typical 4GB internal memory crap phone.
Click to expand...
Click to collapse
Make two partitions on your sd card, select portable storage option in Marshmallow, install apps2sd,it has all features of link2sd for free,I am using it myself.
same issue, app disappears or data gets lost or sometimes all apps start crashing untill reboot (when this happens cant modify/write anything on sd card, reboot fixes this though )
DarkAlvy said:
same issue, app disappears or data gets lost or sometimes all apps start crashing untill reboot (when this happens cant modify/write anything on sd card, reboot fixes this though )
Click to expand...
Click to collapse
Like I said before, simply use sdcard as portable(don't forget to make two partitions) and use apps2sd(it also has an inbuilt partitioning tool), this is by far the best setup as of now to overcome internal memory constraint
.
arshavin69 said:
Like I said before, simply use sdcard as portable(don't forget to make two partitions) and use apps2sd(it also has an inbuilt partitioning tool), this is by far the best setup as of now to overcome internal memory constraint
.
Click to expand...
Click to collapse
But i will have to root to do that right?
arshavin69 said:
Like I said before, simply use sdcard as portable(don't forget to make two partitions) and use apps2sd(it also has an inbuilt partitioning tool), this is by far the best setup as of now to overcome internal memory constraint
.
Click to expand...
Click to collapse
Hi @arshavin69,
I am trying to use app2sd as you explained, but I am stuck on 2nd partition mounting.
I created 2 partitions by Minitool Partition Manager (because app2sd internal partition manager cause app force close): 1st partitition fat32, 2nd partition ext4.
Once booted up, I choose "portable" and then I open app2sd: app2sd say 2nd partition is not mounted and ask to remount or recreate mount script.
If I try to remount I get an error: mounting /dev/block/vold/179:66 on /data/sdext2 failed No such file or directory.
If I try to recreate the mount script, app2sd ask to choose sd card 2nd partition and file system type.
I am choose /dev/block/mmcblk1p2 and ext4 file system, then app2sd ask to reboot.
After rebooting app2sd says again that 2nd partition is not mounted and ask to remount or recreate mount script.
Could you please explain steb by step what I have to do?
Thank you!
SOLVED dismissing the notification when the phone ask to choose the sd card mount (portable).
DarkAlvy said:
But i will have to root to do that right?
Click to expand...
Click to collapse
Of course!! You can't use even link2sd without root.
DarkAlvy said:
same issue, app disappears or data gets lost or sometimes all apps start crashing untill reboot (when this happens cant modify/write anything on sd card, reboot fixes this though )
Click to expand...
Click to collapse
if your apps disappear after reboot, just transfer them to internal storage and it won't disappear after that
6.0.1 has made this feature unusable.
after updating to 6.0.1 most of the apps cant be moved to external sd.
internal storage gets filled with google apps
this really sucks
abhijitkadam03 said:
After moving apps to sd, apps like mxplayer, Microsoft word etc just disappear.
They are automatically uninstalled.
Can anyone confirm this??
Click to expand...
Click to collapse
Exactly! This is the issue that I was facing.