Linux - MobileThis forum is for the discussion of all topics relating to Mobile Linux. This includes Android, Tizen, Sailfish OS, Replicant, Ubuntu Touch, webOS, and other similar projects and products.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can someone help me understand how 'droid KitKat dances with files and folders?
I recently received and applied the KitKat (v4.4.2 AT&T) update over the air. Previously, I was using JellyBean (v4.3.1 AT&T). After the update, I'm having all sorts of troubles
my content does not go where it used to go during download, save attachment &c
all sorts of folders have appeared on the phone for apps that already had folders elsewhere
apps cannot find content in the old folders
the 'camera' and 'gallery' app have serious troubles. (eg -- I now have three folders named "camera" that get used for new pix in a random way.)
the file picker seems blind to parts of the /storage/ folder tree
apps can't seem to write my SD card
Don't get me wrong, I am thrilled with a lot that is much better with KitKit. I believe there is a method to this madness. I hope my LQ colleagues can help me sort out my confusion.
I assume you have an external SD card to increase storage. Write access by applications to external storage is now not permitted under KitKat except for applications that came installed by the device manufacturer or that are otherwise authorized by the device manufacturer. You can still store data to external storage and applications can access that data but only authorized apps can write to external storage. That's probably accounts for the problems you are experiencing.
On my tablet, I still have the option to move some, but not all, applications to external storage which can free up space on the limited internal storage. But the only way to get write access back is to root the device. If you google around on the internet you will find lots of people complaining about this change which was supposedly done for security reasons. You will also find instructions on exactly what system changes you have to make on rooted devices to restore write access.
i have a gingerbread era galaxy-s2 (which runs unnamed rom). old android fones had a normal file tree and would mount as regular usb flash drives when connected to a pc.
there is a weird filesystem emulation that is created on newer versions of android (and cyanogenmod for that matter) which makes it confusing as to where everything is (such as downloads/nandroid backups/...). a program like file-expert mite reveal parts of the hidden file system and help make things more evident -- i am still confused how to navigate my nexus-7.
i think their intention is to obfuscate it so much that people forget about local storage in favor of their cloud services.
...
i think their intention is to obfuscate it so much that people forget about local storage in favor of their cloud services
... and I hear there are plans to squash the SD card feature like that fruit-named phone OS ...
{COMMENTARY}
As a long time Linux power user and an Android user since early Gingerbread, I don't understand why Android discarded so many of the existing *nix file system features, especially those in a LAN environment.
I'm not asking for NFS or SAMBA support, but the *nix file system has power in the way and end-user can tailor things in ways that make sense to them rather than having someone else's organization imposed. Given that I have a phone and tablet that are most often used as a pair, would it be too much to have something like 'rsync'? The cloud-storage apps move things from device to cloud and back taking all sorts of time and requiring a data path (cell or wifi). I used to be able to sync two Palm-OS™ folders across the room. What is so wrong with that idea?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.