Related
Hi everybody,
I have rooted my M8 Dual Sim and according to SDFix disabled the limitations to use the SD card in my phone freely. Almost. Moving files around within ES File Explorer is no problem, neither copying files from PC to the card.
BUT: when I open a file on either the phone's memory or the card from the PC, the files open all write protected.
This is what drives me mad, I would like to open the files, write into them, and save them like in a normal environment. Does anybody know how to disable this write protection? Please help. Thank you.
Nobody misses usm on his m8???
maklein said:
Hi everybody,
I have rooted my M8 Dual Sim and according to SDFix disabled the limitations to use the SD card in my phone freely. Almost. Moving files around within ES File Explorer is no problem, neither copying files from PC to the card.
BUT: when I open a file on either the phone's memory or the card from the PC, the files open all write protected.
This is what drives me mad, I would like to open the files, write into them, and save them like in a normal environment. Does anybody know how to disable this write protection? Please help. Thank you.
Click to expand...
Click to collapse
I cannot believe this, 60 views and no answer?! C'MON guys, does nobody use his M8 Dual SIM as a portable HDD???
maklein said:
I cannot believe this, 60 views and no answer?! C'MON guys, does nobody use his M8 Dual SIM as a portable HDD???
Click to expand...
Click to collapse
Its been reported by users here that the SD fix apps don't work on the "regular" (single SIM) M8, so I assume the same is also true with the dual SIM. There is a custom kernel module that fixes the SD limitations, but again not sure if it works on the dual SIM, or if there is a corresponding mod/hack.
redpoint73 said:
Its been reported by users here that the SD fix apps don't work on the "regular" (single SIM) M8, so I assume the same is also true with the dual SIM. There is a custom kernel module that fixes the SD limitations, but again not sure if it works on the dual SIM, or if there is a corresponding mod/hack.
Click to expand...
Click to collapse
SDFix has been used only to check whether I gained access to my SD card. And, according to the possibility to move files freely, i gained full access. Only that my files opened from he PC are all write protected.
I can copy&move files from internal storage to SD card and viceversa, and I can copy and move file from PC to SD card and vicecersa. But the files located on SD card, when opened from the PC are always opened in write protected mode. WHY???
Regards
maklein said:
SDFix has been used only to check whether I gained access to my SD card. And, according to the possibility to move files freely, i gained full access. Only that my files opened from he PC are all write protected.
I can copy&move files from internal storage to SD card and viceversa, and I can copy and move file from PC to SD card and vicecersa. But the files located on SD card, when opened from the PC are always opened in write protected mode. WHY???
Regards
Click to expand...
Click to collapse
Almost seems like a permissions issue but I'm not sure if the device would automatically apply permissions that will have you only "read, write and execute" those files on the device itself and not on the PC. That's probably something that you'll have to "set" yourself.
All the files that I create, pictures that get taken etc all have it as "read and write" which is why we can view it on the pc, but in your case it almost seems like it saves it as "read-only" preventing you from making any other changes. BUT that's how it looks and it might not necessarily be the issue at hand
Change permissions?
BerndM14 said:
Almost seems like a permissions issue but I'm not sure if the device would automatically apply permissions that will have you only "read, write and execute" those files on the device itself and not on the PC. That's probably something that you'll have to "set" yourself.
All the files that I create, pictures that get taken etc all have it as "read and write" which is why we can view it on the pc, but in your case it almost seems like it saves it as "read-only" preventing you from making any other changes. BUT that's how it looks and it might not necessarily be the issue at hand
Click to expand...
Click to collapse
That makes sense, thanks BerndM. Any hint on how to chance permissions easily, without having to flash custom ROM?
To be more exact, I am talking only about doc(x), xls(x), txt files, nothing executable.
Truth is, only the windows explorer can handle the files, opening a word file and trying to save it directly from the program to the SD card isn't possible. But I guess you knew that already... I don't recall how it was with my last HTC (the HD2), but at least I could save an opened file in its original storage.
If you have a USB card reader, try to connect to your PC and format the card. I'd suggest FAT32 as its the most universal; although ExFAT should be supported by the M8 (but only really needed if you have huge files).
I've seen a number of folks on here have various read/write issues with the SD, even when the card works perfectly on other devices. The permissions issue is a logical conclusion, but might just be a wild goose chase. Reformatting the card sometimes solves the issue. Even using the phone to format the card doesn't solve the issue, when formatting on PC works.
redpoint73 said:
There is a custom kernel module that fixes the SD limitations
Click to expand...
Click to collapse
Actually, I'm mixing this up, the kernel module is to disable system write protection, not SD write protection. I'm having a brain fart on how to do the SD fix.
But as mentioned, this might not be the OP's issue anyway. At least, I don't think so based on the described symptoms.
Need relief from system write protection
redpoint73 said:
Actually, I'm mixing this up, the kernel module is to disable system write protection, not SD write protection. I'm having a brain fart on how to do the SD fix.
But as mentioned, this might not be the OP's issue anyway. At least, I don't think so based on the described symptoms.
Click to expand...
Click to collapse
Hi there, @redpoint73 if you could provide some guidance as how to get a hold of that insecure kernel, I'd certainly be grateful. A link would be a boon.
I'm trying, with no avail, to edit hostapd.conf (my hotspot configuration file). There are a few options on it that I can't switch on a GUI, like SSID Broadcast and 802.11n toggles. Also, my hotspot has a difficult time upholding the wakelock it needs to stay on without a data interruption at screen off. I don't know if Amplify (by Ryan Steckler aka "cryptyk") might be to blame, because I haven't told it (and isn't) restricting Wi-Fi related wakelocks at all.
Please check my signature below for any details you'd like to ponder. Good night.
furboom1240 said:
Hi there, @redpoint73 if you could provide some guidance as how to get a hold of that insecure kernel, I'd certainly be grateful. A link would be a boon.
Click to expand...
Click to collapse
I'm not at all familiar with the things you are trying to modify. But to remove the system write protection: http://forum.xda-developers.com/showthread.php?t=2701816
redpoint73 said:
I'm not at all familiar with the things you are trying to modify. But to remove the system write protection: http://forum.xda-developers.com/showthread.php?t=2701816
Click to expand...
Click to collapse
@redpoint73 it looks like the link on the OP's post for my phone is dead. Any other ideas (or more reliable links)?
Sent from my One M8 using XDA Free mobile app
furboom1240 said:
@redpoint73 it looks like the link on the OP's post for my phone is dead. Any other ideas (or more reliable links)?
Click to expand...
Click to collapse
Post to that thread, and see if the OP can re-post; or if another user can post it.
But I just noticed your are running CM11? Custom ROMs should already have this implemented, or not applicable in the first place (AOSP?).
redpoint73 said:
Post to that thread, and see if the OP can re-post; or if another user can post it.
But I just noticed your are running CM11? Custom ROMs should already have this implemented, or not applicable in the first place (AOSP?).
Click to expand...
Click to collapse
I thought so, too. But I will take your advice and post to the OP. Thanks.
Sent from my One M8 using XDA Free mobile app
I have the T-Mobile Galaxy Note 3. I was on stock and just took the OTA upgrade to Lollipop (N900TUVUFOB6). After doing this, I rooted the phone with CF Auto Root and installed TWRP 2.8.5.0. I have root access fine. I keep my apps backed up from Titanium Backup on my SD card. When I open up Titanium Backup it tells me the directory isn't writable. I am on the latest su binary / supersu and I have tried changing the mount namespace setting with no luck. Is there anything else I could try to fix it?
Did you install the SD card fix app?
I think there is an option on lollipop to authorize other apps to access directories that are not there own. That might be the problem.
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Thanks so much! I had to pick the option DocumentProvider storage and then select the directory through there. Working fine now.
Sorry. Meant Document provider not Directory provider. ?
Has anyone found a reason why TiBu now thinks the entire directory of dalvik cache is unnecessary when you run the clean up option?
Changing that to DocumentProvider storage solved my problem too sjancura, thanks!
Hi,
I spoke too soon... I am still having problem with using external SD card with titanium backup.
I changed the storage provider to DocumentProvider but I cannot 'save' that selection as it's grayed out - please see the screenshot.
I have tried changing name of ex SD card. At first I used SDFix apps which were able to help with similar problem in KitKat but haven't fixed the issue now in lollipop.
I had the same problem (Running Lollipop and TB) and I got it fixed by using one of the KitKat fixes. The one I used was "SDFix" by "NextApp, Inc." in the google play store.
dajomas said:
I had the same problem (Running Lollipop and TB) and I got it fixed by using one of the KitKat fixes. The one I used was "SDFix" by "NextApp, Inc." in the google play store.
Click to expand...
Click to collapse
Thanks...that worked for me too.
sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Hours of frustration brought to an end by that advice ... thanks mate ... you're a legend!
Hi,
I tried running SDFix, having run it in tbe past, prior to finding out this morsel of info on changing DP. However I still can't get it to save that location. Same greyed out directory like previous user posted.
Yeah I found that as well, changed it but could not "save" to that folder location (greyed out). Tried SDFix app, no change. Tried creating a new folder in TB, AND then using ESFile Explorer & neither would allow me to write to the extSD card. Rooted, stock Sprint Lollipop ROM.
I had that issue, worked it out. When you're browsing for a folder with the DocumentProvider select the root of the SD card, then it should close and return to the browser in Titanium Backup. Browse to the sub folder you want, you should be able to click the save button now.
Hi Ghosthree3,
Thanks so much for this. I'm going to give it a shot. My extSD card was used in the past on an earlier version of Android OS, whereby I could write to the extSD card just fine. Consequently there are prior backups on there. As such, I'm wondering if i should mount the phone, copy that folder off, delete that folder on the extSD card and then via TB create a "new" Titanium Backup folder and see if it then allows me to write. Note: I tried mounting the phone to my PC in an effort to create a folder on the extSD card and that method too, prevented me from creating a folder, hence my thought on getting what I have off of the device, and attempting writing a new folder per your directions. I wonder if my PC will allow me to erase that folder.....
Dopamin3 said:
I have the T-Mobile Galaxy Note 3. I was on stock and just took the OTA upgrade to Lollipop (N900TUVUFOB6). After doing this, I rooted the phone with CF Auto Root and installed TWRP 2.8.5.0. I have root access fine. I keep my apps backed up from Titanium Backup on my SD card. When I open up Titanium Backup it tells me the directory isn't writable. I am on the latest su binary / supersu and I have tried changing the mount namespace setting with no luck. Is there anything else I could try to fix it?
Click to expand...
Click to collapse
Install xposed and then use xinternalsd then configure it as u wish. This will fix the problem
Sent from my iris_X8 using XDA Free mobile app
sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Thank you!
Hi s j a n cu r a,
Thank you very much. Someone else posted that, but maybe i'm not selecting it properly. When I select Document Provider, I browse to "Open from SD card", scroll down to the "Titanium Backup" folder, hit "Select" the "Titanium Backups" that are there [at one time I had no issues writing to my EXT SD card], it then says, "Detect!" [External storage] and I select "Everywhere in External Storage". It finds 41 backups there, I select that "External Storage' radio button. That's where I seem to hit a wall. The "Use the current folder" appears to be greyed out. I'm left only with "Cancel". I think there is some deeper issue writing to ExtSD because with File Explorer I can't copy picture files from one folder to the other. That's what is giving me this feeling that something else is going on with write permission. Frustrating to say the least. My only recourse at this point is to use the internal SD, which does work.
Google lollipop external sdcard fix. There's an app in the play store.
Sent from my SM-N900T using Tapatalk
Dear All,
This is my desperate attempt after days of googled with a dead end.
Recently, out of nothing i have encountered a major error after years. It all of sudden. Bombarded with "google play service is stopped" then decide to reboot then never up again with "acore stopped working'' on the very first screen after samsung logo where you have unlock the screen.
I did wipe data/factory reset. All good. reinstalled all essentials. SuperSU and Rootchecker report im still rooted. Then noticed LINE app (by Naver) has a bizarre behavior. All image related operations is not working with message "Cant use SD card, please confirm SD card settings"
All other chat messengers all working flawlessly (BBM, Whatsapp, you name it) but this one. To be detailed, affected operations are downloading stickers, themes, chat image attachments, chat photos wont came out, trigger camera, attach/send photo..
Submit a ticket to Naver but returned with they have no support for rooted device.
Device detail:
N7100 4.4.2 (rooted)
SuperSU / Knox disabled
modified platform.xml (extsdcard write access)
Failed Attempts:
- format ext SD card from inside, issue still exist
- install / reinstall LINE app, issue still exist
any kind of idea/helps would greatly appreciated as most of my contacts and communication are mainly using this app. I hope you guys have knowledge to be shared for pinpoint the issue based on the error message above. I believe the solution can be a great value as there are currently none in the net.
Thanks
try to apply kitkat sdcard fix
click
I have the Xperia Z3 running on Lollipop.
Same issue, all apps such as whatsapp, fb, etc can access the SD card except for line.
The error message when trying to send a photo to someone in Line is "Can't use SD card. Please confirm SD card settings"
Reinstalled the app several times, unmounted and remounted the SD card, even moved the app to the SD card with the app itself still working fine. But still cannot send or receive photos or download stickers.
Also applied the suggested that sd card fix even though it wasn't really needed since all other apps can access the SD card just fine..anways it didn't help.
Any other ideas?
Oh yeah, even tried installing a Line version which was 6 months old - didn't help either.
mcdimm said:
Dear All,
This is my desperate attempt after days of googled with a dead end.
Recently, out of nothing i have encountered a major error after years. It all of sudden. Bombarded with "google play service is stopped" then decide to reboot then never up again with "acore stopped working'' on the very first screen after samsung logo where you have unlock the screen.
I did wipe data/factory reset. All good. reinstalled all essentials. SuperSU and Rootchecker report im still rooted. Then noticed LINE app (by Naver) has a bizarre behavior. All image related operations is not working with message "Cant use SD card, please confirm SD card settings"
All other chat messengers all working flawlessly (BBM, Whatsapp, you name it) but this one. To be detailed, affected operations are downloading stickers, themes, chat image attachments, chat photos wont came out, trigger camera, attach/send photo..
Submit a ticket to Naver but returned with they have no support for rooted device.
Device detail:
N7100 4.4.2 (rooted)
SuperSU / Knox disabled
modified platform.xml (extsdcard write access)
Failed Attempts:
- format ext SD card from inside, issue still exist
- install / reinstall LINE app, issue still exist
any kind of idea/helps would greatly appreciated as most of my contacts and communication are mainly using this app. I hope you guys have knowledge to be shared for pinpoint the issue based on the error message above. I believe the solution can be a great value as there are currently none in the net.
Thanks
Click to expand...
Click to collapse
I have the exact same issue after a full wipe and re-flashed custom ROM. The naver LINE app have the same issue as mentioned above. All other apps functions normal. Anyone found a solution to this yet?
HTC One M7
Vipeone sense-based ROM 9.0.0.
Hi. I've encountered a similar problem recently. The interesting thing is that my telephone does not have SD card at all. So my first thought was that the problem is in permissions or cache.
I checked the permissions - app had full access.
Then I cleared programm cache on my phone. both inner memory cache and telephone memory cache (at least that's what they are called in my native language)
After that I tried to upload the image, yet it gave another error. something like: "cannot perform the action now, try again later"
I was quite short on the inner memory on my phone (around 70 MBs free), and thought it can be the problem. I deleted the biggest app and was able to upload the screenshots again.
Probably worth mentioning: I did not reinstall the Line app.
My device:
Telephone called ImSmart C471. China at it's best. Assembled in Ukraine though, company called Impression.
Android 4.4.2
In the latest build, Line apk cant send photo from internal/sdcard..it said line cant use sdcard..?
i had the same problem when i moved to new phone ( Xiaomi Mi4 ). I solved that. Just find the application permission setting in application manager. Try to find permission to stroarge. Change the permission to allow. That's it. That worked for me.
where's the settings?
andrew_susanto said:
i had the same problem when i moved to new phone ( Xiaomi Mi4 ). I solved that. Just find the application permission setting in application manager. Try to find permission to stroarge. Change the permission to allow. That's it. That worked for me.
Click to expand...
Click to collapse
I can't find any setting for permission to storage from the application manager, is there any? did I overlooked?
Try updating the app in play store. I had the same issue but solved with the updated version.
I had the smale problem. I deleted some pictures and videos and then restarted the phone. Works like magic
I seem to have been at this for hours now. I finally got Xposed framework on my Tab S and Note 4 and decided to try Marshmallow SD fix
https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263/page29
and then EXT SD fix
https://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
In each case going to Titanium backup it just doesn't work - I get the same old "Folder is not writable" message for anything on the SD card.
Since many people are having success - I'm assuming this is because of the Samsung version of Xposed framework ?
I don't know but nothing I do seems to work.
Any suggestions / advice - has anyone got this to work on their tab s or note 4?
louiscar said:
I seem to have been at this for hours now. I finally got Xposed framework on my Tab S and Note 4 and decided to try Marshmallow SD fix
https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263/page29
and then EXT SD fix
https://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
In each case going to Titanium backup it just doesn't work - I get the same old "Folder is not writable" message for anything on the SD card.
Since many people are having success - I'm assuming this is because of the Samsung version of Xposed framework ?
I don't know but nothing I do seems to work.
Any suggestions / advice - has anyone got this to work on their tab s or note 4?
Click to expand...
Click to collapse
If it's lollipop you need the sdcard fix. If it's mm you just need to allow write permissions to the app.
ashyx said:
If it's lollipop you need the sdcard fix. If it's mm you just need to allow write permissions to the app.
Click to expand...
Click to collapse
I'm not sure I understand that. Are you talking about extsd or marshmallow fix ? Also there are no permissions to set other than the ones shown. For Titanium those are all set to on. Ie. Storage.
Is there a specific 'write' permission elsewhere that I've missed?
louiscar said:
I'm not sure I understand that. Are you talking about extsd or marshmallow fix ? Also there are no permissions to set other than the ones shown. For Titanium those are all set to on. Ie. Storage.
Is there a specific 'write' permission elsewhere that I've missed?
Click to expand...
Click to collapse
Any app that wishes to write to the external storage should show a dialog requesting permission to the ext sd after that it will have full write access.
Any app that doesn't isn't mm compatible.
Which folder path are you trying to use?
ashyx said:
Any app that wishes to write to the external storage should show a dialog requesting permission to the ext sd after that it will have full write access.
Any app that doesn't isn't mm compatible.
Which folder path are you trying to use?
Click to expand...
Click to collapse
The Titanium problem is fairly common. if all apps need to be was mm compatible then we wouldn't need a fix for the SD cards I would have thought.
But coming to Titanium itself I can select the old folder with is exsdcard/titaniumbackup but Titanium will tell me this has no write access but I can use it to read from and restore.
There is no location that Titanium will use or see on the extsdcard. What one has to do to is to copy the contents of your backup folder to the internal card then select that as the backup folder in Tba. Then you have elect to change the backup folder but choosing DocumentProvider storage. At this point you then have to create a folder - an existing folder is no good. Once created it will copy the contents of the internal folder to the extsdcard. Apart from the fact that this 'workaround' is much slower it is also inconvenient and any kind of change for whatever reason in the backup folder means that you can't just switch to the old one you have to go through the whole creation process.
As far as I am concerned this is why I wanted an SD card fix but I also understand to some point your view and it does make some sense. However it is confusing. When this nightmare started with Kitkat I understood that apps were allowed their own folder but couldn't affect or write to other folders. Also they were media folders only. This as I remember also affected file managers which then couldn't do their intended job.
With MM and without any fix Solid explorer can and does have full access to the sd card and can write in any folder from what I can see. Other apps seem to possibly access with documentprovider permissions - I'm not sure but many appear to have no problems but the pop up is very much like the documentprovider - choose a folder. So I am confused why Titanium has these problems and can understand a point of view that they haven't adapted as they should have perhaps but then I find it hard to believe that they wouldn't have done what they can with the features /tools they have for one of the most popular backup programs..
Either way, at the end of the day I was really hoping I could have got a fix which worked much like sdcard fix on Kitkat which stopped the nonsense and Google's insistence that they know best how we can and should use our SD cards.
And indeed for many people Marshmallow fix and or EXTSD appear to work for a lot of people in the way I was hoping - hence the creation of this thread because
1) it certainly doesn't for both my Samsung devices and
2) Many people with Samsungs (and some other devices) appear to be having the same difficulty.
I don't understand what has been done on MM to make it so difficult to overcome the problem but obviously it appears Google is just plain bloody minded and trying to make it more foolproof.
louiscar said:
The Titanium problem is fairly common. if all apps need to be was mm compatible then we wouldn't need a fix for the SD cards I would have thought.
But coming to Titanium itself I can select the old folder with is exsdcard/titaniumbackup but Titanium will tell me this has no write access but I can use it to read from and restore.
There is no location that Titanium will use or see on the extsdcard. What one has to do to is to copy the contents of your backup folder to the internal card then select that as the backup folder in Tba. Then you have elect to change the backup folder but choosing DocumentProvider storage. At this point you then have to create a folder - an existing folder is no good. Once created it will copy the contents of the internal folder to the extsdcard. Apart from the fact that this 'workaround' is much slower it is also inconvenient and any kind of change for whatever reason in the backup folder means that you can't just switch to the old one you have to go through the whole creation process.
As far as I am concerned this is why I wanted an SD card fix but I also understand to some point your view and it does make some sense. However it is confusing. When this nightmare started with Kitkat I understood that apps were allowed their own folder but couldn't affect or write to other folders. Also they were media folders only. This as I remember also affected file managers which then couldn't do their intended job.
With MM and without any fix Solid explorer can and does have full access to the sd card and can write in any folder from what I can see. Other apps seem to possibly access with documentprovider permissions - I'm not sure but many appear to have no problems but the pop up is very much like the documentprovider - choose a folder. So I am confused why Titanium has these problems and can understand a point of view that they haven't adapted as they should have perhaps but then I find it hard to believe that they wouldn't have done what they can with the features /tools they have for one of the most popular backup programs..
Either way, at the end of the day I was really hoping I could have got a fix which worked much like sdcard fix on Kitkat which stopped the nonsense and Google's insistence that they know best how we can and should use our SD cards.
And indeed for many people Marshmallow fix and or EXTSD appear to work for a lot of people in the way I was hoping - hence the creation of this thread because
1) it certainly doesn't for both my Samsung devices and
2) Many people with Samsungs (and some other devices) appear to be having the same difficulty.
I don't understand what has been done on MM to make it so difficult to overcome the problem but obviously it appears Google is just plain bloody minded and trying to make it more foolproof.
Click to expand...
Click to collapse
The fix for KitKat and lollipop isn't needed for MM because Google did in fact listen to people griping about the ext card restrictions.
MM will give full access to properly coded apps.
I have many different devices running MM and all gave write access to the ext sdcard including TB, which I use regularly.
However that doesn't mean to say I haven't had the issue you speak of. I may have even had it with TB.
The folder path I use in this case is mnt/media_rw/
This path is almost always accessible by apps and is the path I'm using right now for TB.
If that doesn't work try disabling 'mount namespace separation' in SuperSU settings then reboot also make sure your TB is up to date.
ashyx said:
The fix for KitKat and lollipop isn't needed for MM because Google did in fact listen to people griping about the ext card restrictions.
MM will give full access to properly coded apps.
Click to expand...
Click to collapse
Ok understood.
I'm guessing then that the so called Marshmallow fix via xposed is to get older apps which may not be updated to work
ashyx said:
I have many different devices running MM and all gave write access to the ext sdcard including TB, which I use regularly.
However that doesn't mean to say I haven't had the issue you speak of. I may have even had it with TB.
The folder path I use in this case is mnt/media_rw/
This path is almost always accessible by apps and is the path I'm using right now for TB.
Click to expand...
Click to collapse
Ok so now the plot thickens and I've no idea what is going on here. Tba says when I navigate to this folder [and I'm assuming that the choice when asked is "filesystem storage" and not "Filesystem storage - Media" (which only offers internal memory anyway)]
"This folder cannot be accessed"
and that is before getting to the external sd card which would be the number (F91E-D472) in my case. ie. mnt/media-rw
Needless to say - Solid explorer can see this and navigate to the sd card no problem.
This happens on both Note 4 and TAB s and I'm really curious now because something on my systems are different.
ashyx said:
If that doesn't work try disabling 'mount namespace separation' in SuperSU settings then reboot also make sure your TB is up to date.
Click to expand...
Click to collapse
Sure, namespace is unchecked - did that on both devices some time ago, and Tba is up to date.
Pretty damn confused now
louiscar said:
Ok understood.
I'm guessing then that the so called Marshmallow fix via xposed is to get older apps which may not be updated to work
Ok so now the plot thickens and I've no idea what is going on here. Tba says when I navigate to this folder [and I'm assuming that the choice when asked is "filesystem storage" and not "Filesystem storage - Media" (which only offers internal memory anyway)]
"This folder cannot be accessed"
and that is before getting to the external sd card which would be the number (F91E-D472) in my case. ie. mnt/media-rw
Needless to say - Solid explorer can see this and navigate to the sd card no problem.
This happens on both Note 4 and TAB s and I'm really curious now because something on my systems are different.
Sure, namespace is unchecked - did that on both devices some time ago, and Tba is up to date.
Pretty damn confused now
Click to expand...
Click to collapse
Have you tried placing the TB folder on your ext sdcard then used the detect button (whole device) in preferences to detect the folder and then select it under mnt/media_rw?
ashyx said:
Have you tried placing the TB folder on your ext sdcard then used the detect button (whole device) in preferences to detect the folder and then select it under mnt/media_rw?
Click to expand...
Click to collapse
This was the method I used as soon as I updated to MM and didn't notice the "this folder is not writable" message.
However, the option to choose mnt/media_rw isn't available. If I use Detect > whole device I'll be offered :
/storage/F91E-D472/Titaniumbackup
perhaps I'd see the other option under normal circumstances but Tba is not able to access that path so wouldn't find it in a search ... I guess
Aha! could this be the problem?
see post #15
https://forums.geforce.com/default/topic/917126/write-to-external-sd-restriction-in-marshmallow/
What is your sd card formatted as - mine is FAT32 so perhaps I need to go exfat?
..but then such links show that I'm certainly not alone - this one actually confirms that tb has this write problems and leads to the Documentprovider solution:
https://www.youtube.com/watch?v=GATqU1_xzqA
louiscar said:
Aha! could this be the problem?
see post #15
https://forums.geforce.com/default/topic/917126/write-to-external-sd-restriction-in-marshmallow/
What is your sd card formatted as - mine is FAT32 so perhaps I need to go exfat?
..but then such links show that I'm certainly not alone - this one actually confirms that tb has this write problems and leads to the Documentprovider solution:
Click to expand...
Click to collapse
ExFAT. Anything above 4gb should be ExFAT.
ashyx said:
ExFAT. Anything above 4gb should be ExFAT.
Click to expand...
Click to collapse
curiously I set permissions to 777 for the mnt/media_rw and titanium can go there but any further (even though I've done the same for the sdcard folder - nada!
and sadly after converting to exfat - mnt/media_rw .... "this folder cannot be accessed"
Not sure what else I can do.
Hi all,
I compiled AOSP Extended ROM v. 5.8 (Oreo) and I thought I would share it here as well.
All credit go to the maintainers of the s5mini device tree(s), to AOSPExtended Team and everyone else who contributed.
What does not work (so far):
- Video Recording
- FlipFlap
- Auto-detect APN (I had to manually set it)
- Call forwarding settings menu: Radio (gms/umts) stops working; needs reboot
- Background light for hardware buttons (fixed)
- NFC (Problem with menu/settings) (fixed)
Disclaimer:
* Your warranty is void when flashing this rom. *
* I am not responsible for bricked devices, dead SD cards or other problems. *
Download Link: AospExtended-v5.8-kminilte-20181111-1820-UNOFFICIAL.zip removed: (this ROM is quite old and missing security and other features. Use a Pie build: e.g. https://androidfilehost.com/?w=files&flid=64356&sort_by=date&sort_dir=DESC)
Note: This ROM should work on all Exynos based variants(G800F/M/Y), however I could only test on G800F.
Installation (GAPPS): (You know the drill...)
-Flash ROM with latest TWRP
-Flash OpenGAPPs
-Flash Magisk
Installation (Nanodroid):
-Flash ROM with latest TWRP
-Flash Magisk
-Flash Nanodroid
Created 2018-10-10
Last Updated 2018-10-25
Status Discontinued (sorry no more updates)
Updated ROM (resynced)
thx you for your hard work, i will try it.
Update
I updated the ROM again to include android-8.1.0_r48,
Security patch is now October 5th,
and I also included the AEX boot animation this time.
SD card is not accessible - unfortunately.
But great work, mate
Immortal rider said:
SD card is not accessible - unfortunately.
But great work, mate
Click to expand...
Click to collapse
Hello,
I just checked SD (external) storage and here it is accessible (I can create and delete files&folders). Do use it as internal storage?
you need to give permission for 3rd party apps like amaze (it did not work the first time)
mongo0 said:
Hello,
I just checked SD (external) storage and here it is accessible (I can create and delete files&folders). Do use it as internal storage?
you need to give permission for 3rd party apps like amaze (it did not work the first time)
Click to expand...
Click to collapse
Yes, I tried to use SD card as internal but also as external device.
I also confirm that folders can be created and files can be copied and erased.
But if I want to acces the external card with any APP (likt dict.cc) which needs access to external SD card, it says memory is not accessible.
Just give me a hint, how shall I give permission to 3rd party apps?
Do I set Memory access is in security section in the settings, because this does not work.
Or do I have to access any config file using a terminal?
Thx for your reply, mate.
Immortal rider said:
Yes, I tried to use SD card as internal but also as external device.
I also confirm that folders can be created and files can be copied and erased.
But if I want to acces the external card with any APP (likt dict.cc) which needs access to external SD card, it says memory is not accessible.
Just give me a hint, how shall I give permission to 3rd party apps?
Do I set Memory access is in security section in the settings, because this does not work.
Or do I have to access any config file using a terminal?
Thx for your reply, mate.
Click to expand...
Click to collapse
I'm thinking that dict.cc app is a broken or not fully supporting Oreo. It doesn't even start properly here..( all white or black screen, then, after a long time, a search bar that is not really working ) and 'dict.cc isn't responding' as well as 'GENERIC ERROR' something (at least on first start).
But, eventually I got it to change the directory: (changed Data Storage Location to /storage/3451-1301/). Even though dict.cc said it didn't work...
All the other apps I tried can also access sdcard:
I inserted SD card and started VLC and get this message:
'New external storage detected. Do you want VLC to add device sdcard1 to your medialibrary?'
VLC then can play the music stored on sdcard...
Also, I could access OSMand maps on sdcard I downloaded a long time ago under a different ROM
Anyway, I attached the screenshot with the instructions from Amaze how to grant access (Amaze opens the standard Files (explorer) to that). Maybe it helps...
edit:
Indeed, dict.cc fails to download to sdcard. But OSMand has no problems at all.
Update
Bugfix:
Background light for hw keys fixed (and configurable)
Other hw buttons (home, back, overview) now configurable
Other (probably) important bugfixes
mongo0 said:
I'm thinking that dict.cc app is a broken or not fully supporting Oreo. It doesn't even start properly here..( all white or black screen, then, after a long time, a search bar that is not really working ) and 'dict.cc isn't responding' as well as 'GENERIC ERROR' something (at least on first start).
But, eventually I got it to change the directory: (changed Data Storage Location to /storage/3451-1301/). Even though dict.cc said it didn't work...
All the other apps I tried can also access sdcard:
I inserted SD card and started VLC and get this message:
'New external storage detected. Do you want VLC to add device sdcard1 to your medialibrary?'
VLC then can play the music stored on sdcard...
Also, I could access OSMand maps on sdcard I downloaded a long time ago under a different ROM
Anyway, I attached the screenshot with the instructions from Amaze how to grant access (Amaze opens the standard Files (explorer) to that). Maybe it helps...
edit:
Indeed, dict.cc fails to download to sdcard. But OSMand has no problems at all.
Click to expand...
Click to collapse
G'day mongo0,
thx for the reply.
Will try it either today or tomorrow again.
Might be to say farewell to dict.cc.
Thx buddy for the great work
Installed last version and you are absolutely right.
Access to external SD card works fine except using dict.cc. dict.cc doesn't recognize SD card, for whatever reason.
everything works fine so far.
Single prob I am facing right now is, network connection via SIM card (as you have already written in the main post).
As said before, great work, buddy.
THX and greetz
Immortal rider
Google Camera
I have a problem, I can't install the google camera.
Someone can help me, please ?
Roger Pierrick said:
I have a problem, I can't install the google camera.
Someone can help me, please ?
Click to expand...
Click to collapse
Try Open Camera
Works perfectly with AOSPExtended.
Update (Bugfix)
NFC (somehow) fixed
Immortal rider said:
G'day mongo0,
thx for the reply.
Will try it either today or tomorrow again.
Might be to say farewell to dict.cc.
Thx buddy for the great work
Installed last version and you are absolutely right.
Access to external SD card works fine except using dict.cc. dict.cc doesn't recognize SD card, for whatever reason.
everything works fine so far.
Single prob I am facing right now is, network connection via SIM card (as you have already written in the main post).
As said before, great work, buddy.
THX and greetz
Immortal rider
Click to expand...
Click to collapse
Well, thanks for your feedback. It was also interesting for me to do all the rom compiling..
I probably won't update anymore since it looks like rev. 48 is the final one for Oreo, AEX seems to have stopped updating it, and (some of) the bugs are fixed.
hi; how long did it take you to rom installation ?
Because I wait since 1hour and nothing
Forumeuriste said:
hi; how long did it take you to rom installation ?
Because I wait since 1hour and nothing
Click to expand...
Click to collapse
That's definitely too long; it should only take 5-7 minutes...
Did you make full wipe (Dalvik/ART, Cache, System, Data(, Data on ext_sdcard)) with twrp-3.2.3-0-kminilte?
I found 2 issues:
1.)
Backup in WhatsApp is not working, same like in LineageOS 15.1:
https://forum.xda-developers.com/showpost.php?p=78126440&postcount=480
2.)
The display is flickering when dimmed
Great work @mongo0 :good:
Hey ScRe13
Thanks for your feedback.
I can confirm 1.), however I don't see any flickering.
There are some graphical glitches with apps based on apache cordova., apparently..
I did an update 2018-11-11 (resynced sources)
I might give a try to fix the storage issue too
I have testet 2018-11-11, but the chat backup in WhatsApp is still not working.
But the rest of you build is great:good: Incredible fast 8.1 on Samsung S5 mini
Hope you'll release frequent new builds with the current security updates.
Hello,i have installed the Magisk-v18.1. i have no Root