I’m thinking that this might be a good phone for my wife, but I’m concerned about limited memory for apps when 5.0/Lollipop comes along.
My understanding is that Motorola brought back the ability to move apps to SD memory with 4.4 for this phone. My understanding is that you can’t move apps to SD memory when using ART, and that ART is the default runtime for 5.0.
Has anyone heard if there is going to be any way to move apps to SD with 5.0 for this phone?
It's not possible to move apps to sd when you select ART runtime in KK from developers Options as it's in beta stage. We don't know about the ART from Final Lollipop build which will not be beta ART like in KK
Related
Ok so after reading about the limitation on kit kat regarding sd card, i got really confused being a newbie in technical aspects so i was hoping people here can shed a light on my questions:
1. Is the touchscreen issue fixed on kitkat?
2. If i update right now to kitkat, will all my pictures and mp3 saved in sd card be still readable and playable? Or will they be gone? Some people reported breaking sd card after updating.
3. Can i still download music and use file comando(never ised that app before) to move files to sd card?
4. If i use stock camera, images are still saved in sd right?
5. If i have an app moved to sd, and updated the app after updting to kitkat, will i still lose my saved files?
6. Does this limitation mean that we can no longer download files bigger than the internal memory of the phone? Isnt that going to make our xperia z1 useless if you have big apps and only have like 2g internal memory left??
7. I read something about apps can still write on your sd if they make a private folder but i dont understand it. So does this mean we can still download files directly to sd if the app supported kitkat?
Those are some of the questions i have for now. Please please someone answer me cause im really confused.. Thank you.
Search the forum...all questions will be answered if you put a little effort to it
Sent from my C6903 using XDA Premium 4 mobile app
1. It was fixed already in .136 4.3, if you still have problems go via Warranty.
2. Yes, with some specific applications.
3. No, you have to get root.
4. I think so.
5. How did you moved the apps to SD? it was never possible from 4.2.2.
6. Ask Google.
7. You are will not be allowed to write to SD until you get Root and modified system to do it. Search on Z1 section, is there.
Best answer for all your question is: Do not Update to KK.
I've been having problems with deleting and editing files on my SD card. I was really hoping this would be fixed when upgrading to Lollipop but I'm having the same issues.
I'm using JetAudio Player which has the ability to edit MP3 tags and delete files/folders from the app directly. I've never been able to do it. I contacted the dev and he said to remove all the files, reset the device reopen the app, etc. Just setting everything back to zero. It didn't do anything. Then he suggested I try with the Google Play Music app and it's the same thing! I can't delete music that's on my SD card from that app either.
I've tried formatting it to NTFS (which the Z3c didn't even recognize as valid formatting) FAT32 from my computer and as exfat from the phone itself and none of it made a difference.
I have successfully deleted files on the SD card from ES file explorer after it prompted me for the root SD folder.
Has anyone had these issues before?
Have you tried http://click.xda-developers.com/api...play.google.com/store/apps/d...evasque.fmount
Sent from my D5803 using Tapatalk
---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------
Pants sorry bad link
Look for SD fix nextapp on the playstore
Sent from my D5803 using Tapatalk
I'd rather not root it since I've had to send it back and I don't want to void my warranty...
Are you talking about the limitation introduced by Google since KitKat - external SD isn't writable by user apps, only by system apps?
Google fixed that in Lollipop, that's why I'm asking. I'm running Lollipop and an official Google app can't write to my SD card.
I can move apps to my SD card, but Google Play Music can't delete files on my SD card.
Google didn't "fix that", there's a different API now that allows doing a large part of what KitKat totally prevented. However, this API needs to be utilized by the app - old apps that didn't get updated specifically for Lollipop with support for this new API will get blocked just the same as in KitKat. This is why ES Explorer asked for the root of SD card.
My guess is that the apps you use aren't updated, including Google's own.
Jack_R1 said:
Google didn't "fix that", there's a different API now that allows doing a large part of what KitKat totally prevented. However, this API needs to be utilized by the app - old apps that didn't get updated specifically for Lollipop with support for this new API will get blocked just the same as in KitKat. This is why ES Explorer asked for the root of SD card.
My guess is that the apps you use aren't updated, including Google's own.
Click to expand...
Click to collapse
I am aware that Lollipop uses a different API for this. With all respect, I'd be really surprised if google didn't update their own app with this. Can anyone with a stock Lollipop Z3 Compact check if they can delete songs from the Play Music app?
Facing Similar Issues.
I am unable to update album art or edit metadata of song files on the SD card of my Xperia Z3 compact. I have tried the Walkman app and also another app called MusiXmatch. Both show a message that we they can't edit the files. My previous phone Xperia Z faced no such problems on Jelly Bean. Isn't there any cure for this problem without rooting.
I'm looking to help my mum's moto g 2014, she can't install any app updates and is having constant problems because their Moto G 2014 is out of available space, and none of the apps which are using the most amount of space will move to an SD card.
To help fix this I was looking at installing a Marshmallow based ROM that could use an SD card as internal storage, however having read on here for a little bit it seems like they're all a bit too experimental to expose to a non-geek. Does anyone have any specific suggestions before I just start trying different stuff? If it helps at all it was bought unlocked in the UK, I don't have anymore details right now as I live in the US and won't be over till next week.
1.If it is rooted, use link2sd to move all the internal apps (even the ones occupying large space) to ur sd card, the app will move everything including app data and obb to the sd card
... 2.The aosp build of marshmallow is said to be working in single sim moto g2 devices (I have a dual sim and so ril doesn't work) , take a nandroid backup and flash aosp m and check it, or if you want to be on the safer side use link2sd app
3. Use system App remover to remove unwanted system Apps which are not used eg Google Books, google music player (use another player that use lesser space) etc .. /requires Root /
Hi to all Devs here.. I just am planning to update to OF3 Lollipop from NG3 Kitkat.
I have all the files needed from Muniz ri's post. Am just worried if it will work better than Kitkat.
I would like to ask if Xposed Framework is working on OF3?..
Will OBB on SD work on Lollipop? If not, is there any other option for me to do this?
My phone's storage is only 16GB and i have a 64GB MicroSD.. I put all my OBB and Data on SD Card..
Is DVFS still working on Lollipop? If yes, is there a way to disable it?..
I'm a Gamer and i would not want lag whie playing games.
Will I have problems having full access to The SDCard?.. On KitKat i used KitKat SD Card Full Access module
to overcome this problem..
Hope someone helps and answers my questions...
Thank You...
This is not the q&a section, please post in the correct section.
Sent from my SAMSUNG-SM-G900A using Tapatalk
muttfy21 said:
Hi to all Devs here.. I just am planning to update to OF3 Lollipop from NG3 Kitkat.
I have all the files needed from Muniz ri's post. Am just worried if it will work better than Kitkat.
I would like to ask if Xposed Framework is working on OF3?..
Will OBB on SD work on Lollipop? If not, is there any other option for me to do this?
My phone's storage is only 16GB and i have a 64GB MicroSD.. I put all my OBB and Data on SD Card..
Is DVFS still working on Lollipop? If yes, is there a way to disable it?..
I'm a Gamer and i would not want lag whie playing games.
Will I have problems having full access to The SDCard?.. On KitKat i used KitKat SD Card Full Access module
to overcome this problem..
Hope someone helps and answers my questions...
Thank You...
Click to expand...
Click to collapse
SORRY..
So the CM 13 snapshot came out for a while so I decided to give it a try. Every thing went well until I realized the "move apps to sd card" option is missing. After doing some research on Google, it is said that going to "Settings > Apps > [The app you wish to move] > Storage > Change > SD Card" will do it. But unfortunately I can't see the "Change" button in CM 13 on an app that can be moved to sd card on CM 12 previously. Is it a feature that CM 13 removed or there's a fix for it? Please don't tell me to use that fancy "adoptive storage" thing. I do not trust the reliability of my sd card. And also I was using the latest snapshot of CM 13 (20161220). Thanks.
steveglowplunk said:
So the CM 13 snapshot came out for a while so I decided to give it a try. Every thing went well until I realized the "move apps to sd card" option is missing. After doing some research on Google, it is said that going to "Settings > Apps > [The app you wish to move] > Storage > Change > SD Card" will do it. But unfortunately I can't see the "Change" button in CM 13 on an app that can be moved to sd card on CM 12 previously. Is it a feature that CM 13 removed or there's a fix for it? Please don't tell me to use that fancy "adoptive storage" thing. I do not trust the reliability of my sd card. And also I was using the latest snapshot of CM 13 (20161220). Thanks.
Click to expand...
Click to collapse
Link2SD works perfectly in Cm13. I recommend the Pro Version. Affordable and has great features. Way better than the deprecated Move2SD you're looking for.
Kaffeetrinker said:
Link2SD works perfectly in Cm13. I recommend the Pro Version. Affordable and has great features. Way better than the deprecated Move2SD you're looking for.
Click to expand...
Click to collapse
Thanks for replying. But I want to see if there's any solution that doesn't require a third party app first. I was asking if the built-in move to sd card function which was present in CM 12 and previous android versions is still in CM 13 (screenshot in attachment).
steveglowplunk said:
Thanks for replying. But I want to see if there's any solution that doesn't require a third party app first. I was asking if the built-in move to sd card function which was present in CM 12 and previous android versions is still in CM 13 (screenshot in attachment).
Click to expand...
Click to collapse
I'm sorry,l. When I said deprecated, I actually meant abandoned. The feature does not exist anymore in CM13. It caused too many problems. And it was slow.
Few developers liked this feature, few developers set the "allow Move2SD flag" in their apps, so Google removed the Mobe2SD feature in JB or ICS (don't remember exactly).
CM ignored these flags until CM12 and just continued the Move2SD feature ignoring Googles decision. But that's stopped in CM13.
If you do not want to use a third party app, you can link the apps manually to the SD. But that's not worth it, it's just too much work.
Afaik, there really is no other feasible option than a 3rd party app to get more out of your storage.
I'm sorry, but that's the way it is...
Maybe you want to do it the way I do it:
I use the merged storage feature and save each and every important file via Syncthing. That way, I don't have to fear losing what's on the SD in case it gets corrupted.
If I had to change the SD, I could restore all data automatically.
But I can't move my apps either, only user files!
Merged Storage COULD, but WON'T let you move apps to your SD.
Now, there is a "allow Move2MergedStorage flag". No developer sets it, CM doesn't ignore the flag like it ignored the "allow Move2Sd flag". Afaik, there is no Xposed module circumventing this (so far).
I got a little bit off topic, so let there be summary
- Classic Move2SD
Dead!
- Move2MergedStorage:
Won't move apps because developers don't like their apps to be put onto SD. CM doesn't ignore this anymore.
- Xposed Module that enables Move2MergedStorage by forcing CM to ignore the regarding flag:
Possible, but doesn't exist (yet).
- Link2SD (or similar 3rd party app)
Seems to be your only option if you want to move apps onto your SD.
Kaffeetrinker said:
I'm sorry,l. When I said deprecated, I actually meant abandoned. The feature does not exist anymore in CM13. It caused too many problems. And it was slow.
Few developers liked this feature, few developers set the "allow Move2SD flag" in their apps, so Google removed the Mobe2SD feature in JB or ICS (don't remember exactly).
CM ignored these flags until CM12 and just continued the Move2SD feature ignoring Googles decision. But that's stopped in CM13.
If you do not want to use a third party app, you can link the apps manually to the SD. But that's not worth it, it's just too much work.
Afaik, there really is no other feasible option than a 3rd party app to get more out of your storage.
I'm sorry, but that's the way it is...
Maybe you want to do it the way I do it:
I use the merged storage feature and save each and every important file via Syncthing. That way, I don't have to fear losing what's on the SD in case it gets corrupted.
If I had to change the SD, I could restore all data automatically.
But I can't move my apps either, only user files!
Merged Storage COULD, but WON'T let you move apps to your SD.
Now, there is a "allow Move2MergedStorage flag". No developer sets it, CM doesn't ignore the flag like it ignored the "allow Move2Sd flag". Afaik, there is no Xposed module circumventing this (so far).
I got a little bit off topic, so let there be summary
- Classic Move2SD
Dead!
- Move2MergedStorage:
Won't move apps because developers don't like their apps to be put onto SD. CM doesn't ignore this anymore.
- Xposed Module that enables Move2MergedStorage by forcing CM to ignore the regarding flag:
Possible, but doesn't exist (yet).
- Link2SD (or similar 3rd party app)
Seems to be your only option if you want to move apps onto your SD.
Click to expand...
Click to collapse
Thanks for clearing up the ideas, finally the reason why such feature wasn't included in stock JB is uncovered. Looks like I'll have to stay on CM 12 forever or use Link2SD which I have a not so good experience with because it caused bootloops when I was on stock JB with root.
But it's odd because the stock lollipop rom for newer xperia phones have that classic move to sd card feature too...
steveglowplunk said:
But it's odd because the stock lollipop rom for newer xperia phones have that classic move to sd card feature too...
Click to expand...
Click to collapse
Just googled a bit, some manufacturers reenabled the Move2SD feature in 4.4 or 5.0 for phones with little storage. Just like CM did.
Nevertheless, the other facts still apply. You can't move Apps to your SD without Link2SD.
Exceptions: Merged Storage; tiny apps that have the allow flag can be moved. But the ones that are huge can almost never be moved in CM13. No allow flag, no built-in moving.
Kaffeetrinker said:
Just googled a bit, some manufacturers reenabled the Move2SD feature in 4.4 or 5.0 for phones with little storage. Just like CM did.
Nevertheless, the other facts still apply. You can't move Apps to your SD without Link2SD.
Exceptions: Merged Storage; tiny apps that have the allow flag can be moved. But the ones that are huge can almost never be moved in CM13. No allow flag, no built-in moving.
Click to expand...
Click to collapse
I am guessing the "merged storage" means the new "adaptive storage" introduced in marshmallow?
steveglowplunk said:
I am guessing the "merged storage" means the new "adaptive storage" introduced in marshmallow?
Click to expand...
Click to collapse
Yeah, exactly. Adoptable Storage actually is the correct term.