Write Errors in /storage/emulated/0/Android after system upgrade - LineageOS News & Discussion

Hello World,
I recently upgraded my Samsung Galaxy Note Pro 12.2 (P900) from CM (Android 5.x) to LineageOS (Android 7.1.2).
The upgrade itself seemed to run fine, but now I get strange write errors with Apps that write into /storage/emulated/0/Android.
I verified that all files and dirs under /data/media/0 have the correct permissions and that they belong to media_rw:media_rw. Yet under /storage/emulated/0/Android there are some files and directories that have plain wrong ownership (root) and even some of those apps whose Android dirs seem to have the correct ownership produce write access errors (despite the owner having write permissions).
I am at my wits end here, since I do not know where the fuse mounted /storage/emulated/0/Android dir gets its permission settings and ownership from - and on top of that the offending dirs don't even show any settings that should prevent them from writing in there.

Similar issue here
Hey, did u ever figure this issue out? I'm having a similar issue on my Galaxy Tab 3 7.0. I'm running lineage 14.1, flashed a few things (gapps, SuperSU update, & bootanimation). I tried clearing and reflashing those with known working versions and even doing a clean install of the whole ROM. No luck tho. Please let me know if you have a solution. Thank you.

Related

[Q] Cache folder shows 100% usage

Hello all,
I actually have an Acer S120 but I figured I would give it a try anyway as it seems to be an Android issue rather than device specific. I recently tried to update my phone to 2.3.4 using Gingerounay 2.0 (made by Vache over at MoDaCo). Anyway it seems that after flashing, I am no longer able to download apps from the market, which is caused by my Cache folder "thinking" it is 100% full. I have tried to clear this folder through recovery, through fastboot, adb & through ES File explorer on the phone itself but i'm not getting any results. The only folder/file that is showing up is the lost+found folder but there are no files within this directory. I am able to successfully clear out the lost+found directory but still my cache reflects 100% usage.
I am really not sure what to do at this point and I'm hoping someone here has some ideas to help me out.
Thanks in advance.
Are you sure the access rights are correct?
The folder should be r/w and have rwxrwx--- (or 770) new files created there should have access: rw-rw-rw (or 666) or at least; that is the behavior on my Acer Liquid E (Android 2.2)
Thanks for the reply. I have already sent my phone back for service and they ended up replacing the entire board. I tried everything to clear it and apparently it was a H/W issue...hopefully no one else runs into the same problem.
Oddly enough; only problem I had due to the full/corrupted cache was that I couldn't download apps from the market. I was able to install from my SD card though.
FYI for this thread. If anyone else experiences this problem; its a hardware problem. My phone was sent back to Acer and they had to replace the board to fix the issue. Hopefully no one else encounters this!

[Q] Is it possible to change the status of the internal memory?

Hi folks ,
I tablet Samsung Tab 10.1 4 CM-T530. For him, there are still only 3 test versions TWRP. So, when i* restoring the backup, the changing status of internal memory. Before the restore* was sdcard / 0, and then becomes sdcard / legacy. This causes big problems when downloading media files from the Internet.
Maybe someone knows what is the cause:
1. The TWRP not working correctly
2. The android OS 4.4.x and nothing done about it
3. it can be easily fixed and no problem ?
Please help me .
repey6 said:
Hi folks ,
I tablet Samsung Tab 10.1 4 CM-T530. For him, there are still only 3 test versions TWRP. So, when i* restoring the backup, the changing status of internal memory. Before the restore* was sdcard / 0, and then becomes sdcard / legacy. This causes big problems when downloading media files from the Internet.
Maybe someone knows what is the cause:
1. The TWRP not working correctly
2. The android OS 4.4.x and nothing done about it
3. it can be easily fixed and no problem ?
Please help me .
Click to expand...
Click to collapse
According to the forum 4pda reason is not functioning correctly TWRP. Thank you all .

[Q] SDCard Blank or Unsupported Filesystem

sorry for posting this same question a second time, but im unable to find where the first post went in regards to this subject.
I have a samsung galaxy s5 (sm-g900f) that has been rooted and is running the new Alliance ROM. well even before i installed this ROM my phone would tell me that the SDCard was blank or Unsupported file system. i've tried using 2 different sdcards (a 2GB & 16GB) but both give me the same result on my phone, they work perfectly fine on my old LG & XTE tho. i've used the SDFix app as well as trying to manually edit the platform.xml file and neither of these methods have worked for me. is there something else that i can try to do so i can access my sdcard again?

[Q] - HELP - Creating a hosts file crashes my Note 4

Hi all,
I have been using my rooted Note 4 SM-N910F for 2 months now (Kitkat v4.4.4 installed + TWRP latest version).
I have rooted it in order, among others, to re-install AdAway because I can't live without it.
About 4 days ago, I had the surprise to see that adds were back in apps.
I fired up AdAway which collected new updates (it was set to automatic checking before) and when trying to install the hosts file, the phone suddenly rebooted.
Now, every time I try to add a hosts file in System/etc, the phone reboots and the file is not created. I have tried creating a "host" file.. it's working and as soon as I try to rename it to "hosts", it crashes and reboot.
Has anyone experienced the same behavior ?
What I can dot to debug this ?
I'm opened to any test you can ask me to do.
Thanks in advance
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck

Unrestricted access to my memory card - is that possible?

Hi all,
First of all - forgive me if the subject has been up before - I did a bit of searching, but could't really find much about the subject.
I'm generally very pleased with the Mi A1 (my 4th "main" android phone after HTC Desire, SGS3 & OPO) but one thing that is giving me a bit of grief is this thing with access to my sd card, more precisely with copying content to the card by using different apps like root explorer, dropbox, dropsync pro etc.
Two very common actions in my usage are:
- Start an ftp-server on the phone and push new episodes of whatever tv-series I'm watching for the moment from computer to phone
- Open root explorer in my phone and copy stuff from my Dropbox folder to my phone (and back)
Neither of these actions can be done in my A1 (stock Oreo). The phone actually give the appearance of giving me the option to choose the sd-card but when trying to actually transfer something there it get's stuck before finishing or just return an error when trying.
So my question is - to get back to actually having rights to transfer stuff to my SD card without any problems, which of the below options would be the "easiest":
1. Does this work if I downgrade to Nougat?
2. Would rooting be enough if I stay on Oreo?
3. Can I transfer more freely with LOS 15.x?
4. Other options?
I actually found one thread mentioning this as a problem in stock Oreo so I know I'm not alone with the problem.
Thanks in advance,
/gosa
Hi,
Found this when searching Google for solutions this problem.
At the moment my only way of getting files onto the memory card is to download them to the internal storage and then using "Stock" file manager to copy them to the memory card... A bit to many steps if you ask me.
I was thinking that rooting might solve it but haven't gotten around to it yet.
hi
gosa said:
Hi all,
First of all - forgive me if the subject has been up before - I did a bit of searching, but could't really find much about the subject.
I'm generally very pleased with the Mi A1 (my 4th "main" android phone after HTC Desire, SGS3 & OPO) but one thing that is giving me a bit of grief is this thing with access to my sd card, more precisely with copying content to the card by using different apps like root explorer, dropbox, dropsync pro etc.
Two very common actions in my usage are:
- Start an ftp-server on the phone and push new episodes of whatever tv-series I'm watching for the moment from computer to phone
- Open root explorer in my phone and copy stuff from my Dropbox folder to my phone (and back)
Neither of these actions can be done in my A1 (stock Oreo). The phone actually give the appearance of giving me the option to choose the sd-card but when trying to actually transfer something there it get's stuck before finishing or just return an error when trying.
So my question is - to get back to actually having rights to transfer stuff to my SD card without any problems, which of the below options would be the "easiest":
1. Does this work if I downgrade to Nougat?
2. Would rooting be enough if I stay on Oreo?
3. Can I transfer more freely with LOS 15.x?
4. Other options?
I actually found one thread mentioning this as a problem in stock Oreo so I know I'm not alone with the problem.
Thanks in advance,
/gosa
Click to expand...
Click to collapse
Here one more with the same problem. I have the My A1 in ROM Stock Oreo 8 with root via magisk, and it is tedious and annoying not to be able to write to the external SD. I use ADM, apps for downloads Torrent, Solid Explorer.
Having Root I had the opportunity to try several possible solutions. Here some of them (note: none worked, nor resolved) I expose them in case someone else wants to try, possibly something will work for them.
Root ??????
SDFix: KitKat Writable MicroSD. (Developed by NextApp)
Magisk Modules??????
App Systemizer
ExSDCard Access Enabler
Xposed ??????
Marshmallow SD fix
KitKat SD Card Full Access (Caution: gives many errors in OS)
Handle External Storage
One way to take it with Solid Explore (it's more visual than the Stock Explorer):
* Solid Explorer, to paste or write to SD, always go to Root / mnt / media_RW / SD Card
As I mentioned. None of the above worked for me.
The only way to solve the problem momentarily is to download and use the apps all in the internal memory, with the stock file explorer moving the files to the external SD in a step later.
If someone can give light to this problem or a possible solution I will be very grateful.
*(sorry for my English)
Have you tried binding folder/creating softlink
Could you explain how it is done? Or inform about the subject.
Just got 8.1 and the problem is gone.

Categories

Resources