I am an heavy user of mulit-user feature, however i recently got into a problem with file transfer in Android 10 roms
1) In Android 9, one can place the files in Android/obb folder and the same can be accessed by other user
2) However this behaviour is not working in Android 10.
3) Though MIUI have a feature to transfer files from second space to first space & vice versa
Anyone help in achieving the same in AOSP/Other roms, as this feature is preventing me from trying other roms. I want the files to be shared / transferred between users in multi-user environment.
Related
Hi All,
Just a quick general question, has Android 5.x (Lollipop) changed the filesystem paths in general...??
For as long as I can remember, most Android releases, both Internal and External locations have remained the same... I think one of the Android versions changed it ever so slightly, but can't remember which one.
However with Android 5.x (Lollipop), certainly with ours (and other devices I've seen trying to get Lollipop builds going). They all talk about having difficulties with accessing Internal and External, and now the paths are either...
\mnt\Emulated\SDcard\0\
\mnt\Media_RW\SD0
\mnt\SDCard\SDCard0
or variations of that, instead the usual paths.....
Is this the new way that Android 5.x has changed, or is it just a case of while people are trying to compile it, it will then return to the same locations as previous versions once all the bugs are out and its good to go....?
Thanks, Lister
Anyone...?
Is this the way forward now for Android 5.0 / Lollipop builds, that Google have changed the filesystem/paths....??
Or is this just while in development, alpha/beta, compiling modes, and when goes final... It will link back to the original locations where previous data currently is...? (same with recovery I believe, at moment).
Thanks, Lister
I'm confused, does Android 5.0 Emulate SD Cards now...??
Do we get a folder, within a folder within INTERNAL storage now?? Does this apply to just our device, or all devices...
It seems Google has changed the goal posts...??
The internal sdcard /storage/sdcard0 will show you the files inside the 0 folder
The full internal sdcard (with the 0 folder inside) will be mounted on /storage/oldsdcard0
Click to expand...
Click to collapse
I opted to encrypt the entire file system while running CM 13 and then switched over to L 14 on my T-810. Since doing that several months ago, however, I have multiple problems which forced me to put the tablet on the shelf as being wholly unusable. Posting in the L 14 thread has not led to any resolution, nor did I get any replies to questions posted in a couple of other non-Google OS threads. Installing various updates, reinstalling from scratch etc. have not resolved my problems.
My question is now: are there users on xda-developers.com who actually have encrypted the entire file system and where /everything/ works?
Myu problems, specifically, are:
- unable to play most, but not all mp3-/mp4-files using different players. Putting the same files on the external sdcard - not-encrypted - works fine.
- unable to open most, but not all, jpg-files in different view programs. Again, having the same files on the sd-card works fine.
- I also have problems accessing the external sdcard using the built-in file viewer whereas I am able to do so using Solid Explorer. This, however, may not have anything to do with encryption but to me not having fully understood changes to accessing the file system in Nougat.
Clearly there is something fundamentally borked related to encryption. Having the files on the unencrypted external sdcard is not a solution. Nor is the apparent new approach in Nougat where certain files can be encrypted, this is a huge security hole as has been discussed on the 'net.
My A5 2017 (A520F) is installed with the Samsung Firmware - Russian Nougat & rooted with Magisk 13.3.
A Brief Rant (Skip the red text, to move right to the issue):
My last Samsung was Galaxy S2 and so many years later, the new Samsung software has become so wannabe iPhone.
So difficult to access my own SD Card via WiFi Transfer and installing a simple theme seems impossible. Due to lack of stable Custom ROM I am sticking to the default firmware as I need the VoLTE (not stable in Lineage OS).
Can anyone please help with the following:
1. How to install a Theme downloaded from the internet? I downloaded Swift Black_10.7.apk but it down't show up in the Settings > Wallpaper & Themes. Installed Substratum too, but doesn't work either.
2. How to get write access to SD Card in WiFI Transfer? I can transfer data through USB on the SD, but when I try to transfer data through WiFI File Transfer, I get the message Sorry, this directory is not writable. Even In ES File explorer, the System or the Emulated folder does not get the Write access despite ticking the 'Write' box
Any solutions?
Got the same problem with WiFi File Transfer pro.
Redmi 5A, miui 9.6
Keith0222 said:
My A5 2017 (A520F) is installed with the Samsung Firmware - Russian Nougat & rooted with Magisk 13.3.
A Brief Rant(Skip the red text, to move right to the issue):
My last Samsung was Galaxy S2 and so many years later, the new Samsung software has become so wannabe iPhone.
So difficult to access my own SD Card via WiFi Transfer and installing a simple theme seems impossible. Due to lack of stable Custom ROM I am sticking to the default firmware as I need the VoLTE (not stable in Lineage OS).
Can anyone please help with the following:
1. How to install a Theme downloaded from the internet? I downloaded Swift Black_10.7.apk but it down't show up in the Settings > Wallpaper & Themes. Installed Substratum too, but doesn't work either.
2. How to get write access to SD Card in WiFI Transfer? I can transfer data through USB on the SD, but when I try to transfer data through WiFI File Transfer, I get the message Sorry, this directory is not writable. Even In ES File explorer, the System or the Emulated folder does not get the Write access despite ticking the 'Write' box
Any solutions?
Click to expand...
Click to collapse
Firstly u need to install any aosp based custom rom. Such as Resurrection Remix. Then install substratum. It works 1000%. I personally used it A520F in Oreo. Remember Substratum doesn't work any stock os. Thnks.
Sorry for my bad english. Cause english isn't my mother tongue.
Sorry for probably wrong-posting, but I need a solution _fast_!! Can anybody help me _please_?
I'm a Windows user, I don't really know much about Linux-based systems & thus am not able to interpret any logs or do Linux console commands and stuff... and the fbind readme / help isn't all that easy to understand for Linux-illiterates either. Problem:
I mounted a folder from my external SD card to my internal SD by adding the following line to the config.txt file:
from_to InternalFolder .externalfolder
This seems to _work_, my 'old' app (Maverick from Code Sector) now sees all map tile data that is actually on the external card within the internal folder & can access it.
However, after 2 days or so, the folder link suddenly seems to be 'gone' (internal folder shows as empty). Only solution is to reboot the phone, then all is back to normal again.
I already tried to turn off battery savings for the Magisk app and for Maverick, with had no effect.
Question: what could cause this 'disappearance' of an as it seems correctly bound folder? What could I do to keep such links 'alive' even when they are not used/accessed for a longer time? Is there an *easy way* to 'reset' fbind without rebooting the phone? Or did I forget an important command in the config.txt / should I add something beside the above line?
I'm running Android Marshmallow on a Samsung Galaxy S5 mini DuoS
Hi,
i have problems with file access under latest android 11 rooted firmware. I want to connect through ftp and want to backup files from internal storage and sdcard but with primitive ftpd and rooted access i can not see content in /storage/emulated/0 for me its empty :-(.
I have problems with a tasker task to move files from internal to external storage after the firmware update.
Is there any way to get access again with ftp for the full file system with root?
best regards,
Thomas
Hello,
I just want to know if it was a temporary problem or it's the same on Android 12 too ?
If not, how did you fix this problem please ?
Thank you
the problems exists still on the latest Android 12 version on S10e so still no solution yet :-(
My guess is that this isn't a problem with Android, but that your FTPd service doesn't have root access. If it doesn't have root access, it can't see the folder. If it's not "root aware" it won't be able to ask for root access either. That's my guess.
I'm not familiar with "primitive ftpd" so I don't know if it has this capability, maybe it does.
In the past, for remote access, I have used some file explorer apps that have root capability... those allowed me to remote into the phone. But that was a long time ago - these days I just connect from my phone to the network drive instead, and push files that way (instead of "pulling" from a remote server). This is safer since you aren't leaving an open FTP socket on the phone, which is a bad idea from a security standpoint.
till the last december update (this was an update i made maybe after about one year without updates) all access was fine and since then every access is impossible, its not only ftp, its tasker shell with root access too, worked before fine and now its horrible,
Samsung seems to break some folders, you can access the external sd card with /storage/emulated/[idforsdcard]/ but if you go one level up the folder /storage/emulated/ ist empty and does not show any subfolder, same if you are in /storage/emulated/0/Android and enter the data subfolder samsung takes you to /data
it is so strange what samsung does i don't understand
Thank you very much for your answer
Sorry for this ridiculous question, but even a factory reset can't help you regain access to all your folders ?
Precisely, I also see that Samsung is restricting its phones more and more so that we can't use many functions of our phones as before
I'm currently on Android 10, but with all that I hear, I'm afraid of Android 11 and Android 12
i have fresh installed VC6 Firmware (Android 12 March Update) with factory reset and all access problems still the same, so its the "scoped storage" feature and maybe some samsung addons what leads to this problems
if you want full access to your phone then Android 11 & 12 makes it hard to get and some apps are not optimized for this new scoped storage
FWIW, I have a non-rooted, pure stock phone. I can use FX to go to /storage/emulated/0 and see everything properly. I'm on A11, Snapdragon, S10+.
This implies your app is not being allowed to see the storage. This seems to confirm that it's an app issue - ie, the FTPd may not be able to deal with the new structures on A11/A12. As you noted, it might be this "Scoped Storage" feature... which the app is not able to work with?