Related
okay, i've tried and looked for a similar issue but so far i can't find anything related.
I have a sandisk microsd ultrahc card 16gb.
the card itself works extremely well, both in my device when using the stock / custom samsung based roms,
Didn't really notice this untill i tried out android 4.3, at wich i thought first could be a bug in the rom, the settings kept fc'ing the moment i opened up the storage part, and a com.android.media kept fc'ing the moment i attached the usb cable.
as i thought 4.3 was the culprit i flashed 4.2.2 wich also had similar issues up until the moment i removed the card from my device and restarted, everything worked smoothly afterwards.
I've tried using exfat / fat32 both with cluster of 4096 and 8192 and neither of those helped in any way. Turns out that both TWRP and CWM (yes i tried it in both) also can't seem to mount the sd-card.
Is there any workaround for this issue? or do i have to get myself another sd-card?
I think it's the ROMs man messing things up...i tried android 4.3 yesterday and my whole android directory changed like I had to go into a folder called 0/0/0/my android files. to reach my files etc couldn't mount from sdcard couldn't copy things across from pc...I just flashed back my original stock firmware and everything is good..... android 4.3 is pretty messed up..give it time to mature still very buggy
Sent from my GT-N7105 using Tapatalk 2
The messed up folder i should get used to thoug its because of the multiple user profiles things are getting a bit messy.
Its something they added in 4.2.2 i believe
Best way to do it is to flash the rom and afterwards copy back everything to the sdcard.
Didn't have any issues with another sd card i still had laying around but that thing even thoug class 4 doesn't get more than 1mbps transfer speed.
Sent from my GT-N7105 using xda premium
if the sdcard works on your pc with directly like by using an mmc adapter or sdcard to USB converter then your card is ok if it just didn't work on the phone it has to be a software issue our maybe the hardware mmc port is faulty??!
Sent from my GT-N7105 using Tapatalk 4
thats just it, the sd card works like a charm untill i upgrade to 4.2.2 or 4.3. however both recoveries can't mount the sd-card either.
its not one of those black ones that goes to class 10, but an ultra hdsc class 1 so might be something related to not being able to work properly with anything higher than class 10
nope....the class issue has nothing to do with software.....that's purely the job off the chip electronics/hardware.... I would say a combination of your recoveries and ROMs like I had the same issue once the custom recoveries maybe can't point to the location/ section of the memory card...try changing to different version of the recovery...maybe that could help but be sure the recovery is supported on your device...these are risky issues...so only do it at your own risk
Sent from my GT-N7105 using Tapatalk 4
i've tried several versions of CWM both touch and normal, also philz (yesterday but touch didn't work as it should so won't stick with that one) and TWRP but none of them could mount/find the external_sd, the only think properly working with that sd card is the stock samsung and custom roms based on stock.
(not particulary fond of TWRP, i like the layout and how it works, i just don't like the backups of that recovery, can't copy them to my computer, the extensions keep giving me an error and they are located on the phone's storage)
the sd card couldn't be found in my sensation xe neither i remembered just now after i stopped using the 4.0 stock rom and switched to custom roms, at the time i didn't really see a connection and thought my sd card just didn't want to work properly in my sensation anymore, But having the same issues, and using another sd-card in the phone worked again. Used the ultra sd card in my tabled and because i didn't use that one anymore and someone in my family needed a 16gb one for tomtom europe i gave my good one away )
gonna get myself a new sd-card this afternoon as the 8gb i had laying around isn't getting higher transfer speeds then 1mbps at most even if its a class 4. a shop nearby has a class 10, 16gb for 13 euro's so reckon thats not a bad deal, might even go for the class 10 32gb for 26 euro's if they have it in stock.
I have a 64gig card and had similar problems. With phils recovery it only works when formatted fat32. Think that exfat is not supported. With stock kernel it mounts exfat with any other kernel i tried it would only mount fat32. I think samsung kernel has support for exfat and others dont. So it might not be adroid related but kernel related.
Grumps said:
I have a 64gig card and had similar problems. With phils recovery it only works when formatted fat32. Think that exfat is not supported. With stock kernel it mounts exfat with any other kernel i tried it would only mount fat32. I think samsung kernel has support for exfat and others dont. So it might not be adroid related but kernel related.
Click to expand...
Click to collapse
weird thing is though, even when formatted to fat32 and not exfat, android 4.2 and 4.3 will not recognise my card, also the recoveries i only get an error when i want to mount my sd-card
my tablet which is running an aosp version of android 4.0 or 4.1 (can't quite remember) could handle the sd-card just fine, while both my phones have issues with it.
solved it by buying myself a new sd card, ^^ now i can at least safely backup to my external card instead of the internal memory.
OK my problem is I have the tab 3 10.1 with a 64gb micro SD card in it and the only way to root is to put a smaller SD card in because for some reason it can't read the 64gb micro SD card and when I want to make a backup in cwm it says it can't mount the 64gb micro SD card but if I use anything smaller everything works fine so my question is, is there a work around or some way to Make my tab 3 mount the micro SD because I'd like to install other roms and stuff but I'm not going to I till I can make a backup first. Also with the 64gb card in my tab 3 everything else works like watching videos stored on the SD or music on the SD, anyways any help with this issue would be much appreciated.
Sent from my GT-P5210 using xda app-developers app
you MIGHT have better luck if you format the SD card in some other file system. Other than that I'm not sure
You could buy an 8 gig one and swap it too
DopeShow said:
OK my problem is I have the tab 3 10.1 with a 64gb micro SD card in it and the only way to root is to put a smaller SD card in because for some reason it can't read the 64gb micro SD card and when I want to make a backup in cwm it says it can't mount the 64gb micro SD card but if I use anything smaller everything works fine so my question is, is there a work around or some way to Make my tab 3 mount the micro SD because I'd like to install other roms and stuff but I'm not going to I till I can make a backup first. Also with the 64gb card in my tab 3 everything else works like watching videos stored on the SD or music on the SD, anyways any help with this issue would be much appreciated.
Sent from my GT-P5210 using xda app-developers app
Click to expand...
Click to collapse
Have you tried both recoveries? CWM and TWRP if neither work you may have to format to fat32.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Yes I've tried every recovery out there and with cwm it does this count down from 10 that says connecting then after it gets to 1 it says aborted because it cannot mount the micro SD and yes its formated to fat32 and I've tried exfat and every other format nothing works, and in my first post when I said I couldn't root from the micro SD I mean by going into cwm and loading zip file from there it does the same thing and says it can't connect, that's why everytime I root my device this way I have to borrow a 32gb micro SD and everything works fine
Sent from my GT-P5210 using xda app-developers app
Same problem with my 64g card. MY 16g works great. Cant seem to get the 64g formatted in either my phone or the Tab3. I can sometimes get the Tab3 to recognize the card and it will show the files on the memory card but once I go into recovery there is nothing there.
My 64gb card is recognized while the device is in regular running mode like I can go into settings and then storage and see the card there and how much space is used and free the Only time the card doesn't work right is when I'm in recovery mode because for some reason in recovery mode the system says it can't mount it and that is my whole problem, I need a way to fix it so my 64gb card can be mounted and used while in recovery mode.
Sent from my GT-P5210 using xda app-developers app
It's either a recovery issue or a driver/kernel/bootloader issue, a case that the Tab 3 10.1 development is far from being active.
It looks like it can't allocate space that exceeds 32GiB.
Also wrong thread.
Trying formating your SD card on the computer to fat32 or extfat .
Sent from my GT-I9505 using XDA Premium 4 mobile app
I've already done that and the card works fine example in the device it only stops working in cwm recovery saying it can't be mounted
Sent from my GT-P5210 using XDA Premium ANDROID Developer's App
Thread cleaned of off topic posting and unnecessary non-related junk.
(yes, we can do this)
Any more silly ridiculous junk posted, and this thread will be closed permanently.
If the OP wants to keep this in open forums, we cannot prevent this and welcome the debate, as it seems fitting.
Cheers
MD
My thoughts...
Running the tab in normal mode allows the 64gb card to be read. However, if you start in CWM or TWRP recovery, you are no longer in the "normal" mode and the tab does not recognize the 64gb card. In recovery mode, it is possible that the memory allocations are limited where as in normal mode, 64gb is OK.
In this case, for rooting, maybe you should load the root file on internal memory and not the memory card. I use 4gb cards and neither CWM or TWRP could work with them. I think the issue is in the recovery programs and not the Tab, save for memory limitations set by the base firmware.
Again, JMHO and I may be way out in left field here.
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
GorillaPimp said:
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
Click to expand...
Click to collapse
yes ive tried multiple recovery's and they all do the same thing and cannot read the 64gb micro sd and yes I have my sd formatted to fat32 and I am on windows on my laptop but I can format the micro sd to ext3 or 4 but my question is, if I do that and its formatted to ext3 will I still be able to access my tablets drive space through my laptop like I can now with it being on fat32, because if I cant then that would be pointless for me to do because then I wouldn't be able to add and take things off my sd while its in my tablet., also I said in my first post that this problem doesn't happen using a smaller micro sd like 32 or smaller it only happens with the 64gb, so it has to do with the size some how
GorillaPimp said:
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
Click to expand...
Click to collapse
also IDK if you know this but there isn't many recovery's out there for the galaxy tab 3 10.1 the only one I use is bindroid_cwm_p5210_santos10wifi and even with this recovery it has a slight lag to it when using it.
hoi board
i have made a clean install of the latest CM13 nightly to my serranoltexx
all went fine exept CM13 claims my sd card is corrupted:
Corrupted SD Card
SD Card is corrupt. Touch to fix it.
- i can use the sd card in TWRP
- i can use the sd card in CM11
- i can use the sd card in CM12.1
- i can use the sd card in my PC
no errors there.
it is a 32GB microSDHC CLASS10 card formatted with exFAT
so my question is: how can i tell the CM13 that the card is okay and
let the rom use it as usual?
some more info to help getting qualified answers:
- formatting the card IS NOT AN OPTION!
- I DO NOT WANT TO ADOPT THE CARD!!!
more more information:
- is it correct that MM/CM13 only supports fat32 or vfat on external storage?
EDiT: sd card is working as usual for me since 2016-01-02 nightly!
Not necessarily. What filesystem do you have on it? It could be that I need to add selinux policies for nonstandard filesystems. MM is a ***** now regarding security, so some tweaking might be required.
more additional infos
arco68 said:
Not necessarily. What filesystem do you have on it? It could be that I need to add selinux policies for nonstandard filesystems.
Click to expand...
Click to collapse
it is exFAT
i added the info also in the first post.
arco68 said:
MM is a ***** now regarding security, so some tweaking might be required.
Click to expand...
Click to collapse
sounds somehow familiar.
Should be fixed in next nightly.
roger that!
i will report back.
thx 4 the efforts :good:
Same issue with my jflexx samsung galaxy s4 international.
I had to roll back to cm12.1 as a result.
well...
i am quite curious.
browsed the git some seconds ago and i have the feeling
there is a discussion if VOLD or FUSE handles the exfat volumes
on external sd cards and should it be on vendor (CM13) or
device (android_device_samsung_msm8930-common) level.
also i think that it is not so easy to get something like that
realized at vendor (CM13) level, what seems to be preferred...:fingers-crossed:
i stay curious though :silly:
post scriptum: 129 views to this topic is a huge number, i searched like crazy before i opened this!
a new hope!
Code:
Change 126277 - Merged
cm: sepolicy: fix denials for external storage
Change-Id: I784a859671c69370cab0118a88a5fb0190352af9
CyanogenMod/android_vendor_cm
http://review.cyanogenmod.org/#/c/126277/
:victory:
@arco
is this somewhat of a frozen hell?
Sometimes complaining do help. [emoji14]
roger that!
well done dev!:good:
issue solved ...
i flashed the 2016-01-02 nightly an sd card is working as usual. :silly:
I've never been able to get my 64GB SDXC card to merge. When I do try, it hangs and get some sort of error then I have to use a program on PC to be able to identify my card and reformat it. Tried every system format you can think of...... I'm going mad with this lol
I have the same false notification but on AOSP 6.0, Can anyone tell me what I must change.
Samsung N5110
Hi, I am having the same issue reported above with the latest nightly of cyanogenMod 13. Are you able to explain how to solve the issue.
Thanks
I've had this issue tons on CM13 but never found a solution. Often a reboot fixes it. The mSD always works fine in a PC or from TWRP but CM just says it's corrupted.
Tried reformatting before, usually fixes the issue temporarily. Seems to trigger again eventually, possibly with a new build - so it could be TWRP or update related. Usually happens on boot, sometimes spontaneously. Might see if I can get a catlog but given how random it is, might be tough.
Pretty certain this is an issue with CM. Not had this on stock, had it with two different devices both on CM. Pretty sure its happened with multiple mSDs. Could be exFAT related?
What about supporting f2fs too? I get tons of messages in CM13 regarding a corrupted sdcard, but the card is regularly mounted by a userinit.sh script and is working ok. I also notice a drop in performance, with some short freezes, just before the system display one message for each f2fs partition on external sdcard.
droident said:
I've had this issue tons on CM13 but never found a solution. Often a reboot fixes it. The mSD always works fine in a PC or from TWRP but CM just says it's corrupted.
Tried reformatting before, usually fixes the issue temporarily. Seems to trigger again eventually, possibly with a new build - so it could be TWRP or update related. Usually happens on boot, sometimes spontaneously. Might see if I can get a catlog but given how random it is, might be tough.
Pretty certain this is an issue with CM. Not had this on stock, had it with two different devices both on CM. Pretty sure its happened with multiple mSDs. Could be exFAT related?
Click to expand...
Click to collapse
Thanks for your information. I like others have this issue on with 128 GB exFAT formatted card (using SDFormatter tool). Everything works fine (TRWP, and Windows 7 PC) without issue over multiple boots to and from my phone except that CM is reporting (incorrectly) that my SDXC card is corrupted. Formatting inside of CM13 does NOT solve the problem and actually never completes - CM hangs at 20% completed for my card and never moves forward - so it's hung - except that it doesn't do a Force Close. Every single reboot that I've tried with CM 13 or CM 13 based ROMs (like RR) respond with the same incorrect error message. No problems with CM12 based ROMs. Have also tried the XDA FixExtSD thread and that doesn't help at all either - after correctly saving (on my PC) and using TWRP to install the ZIP file (which TWRP sees fine) - still reboot system in CM with same error - it doesn't go away for me. To me this is a bug in CM13. I'm giving up on CM13 based ROMs (for now) and going back to CM12 where I can using my SD card as an external storage medium.
well...
almost a year later i can resume: it does not get better at all!
i am on 4.4.4 [2016-02] and have to admit, that neither CM12.x nor CM13
can offer the same reliability as CM11.
sadly.
jrchester said:
Thanks for your information. I like others have this issue on with 128 GB exFAT formatted card (using SDFormatter tool). Everything works fine (TRWP, and Windows 7 PC) without issue over multiple boots to and from my phone except that CM is reporting (incorrectly) that my SDXC card is corrupted. Formatting inside of CM13 does NOT solve the problem and actually never completes - CM hangs at 20% completed for my card and never moves forward - so it's hung - except that it doesn't do a Force Close. Every single reboot that I've tried with CM 13 or CM 13 based ROMs (like RR) respond with the same incorrect error message. No problems with CM12 based ROMs. Have also tried the XDA FixExtSD thread and that doesn't help at all either - after correctly saving (on my PC) and using TWRP to install the ZIP file (which TWRP sees fine) - still reboot system in CM with same error - it doesn't go away for me. To me this is a bug in CM13. I'm giving up on CM13 based ROMs (for now) and going back to CM12 where I can using my SD card as an external storage medium.
Click to expand...
Click to collapse
I formatted the card to EXT4 and it's improved things massively. No more hanging/crawling transfers and no more surprise unmounts - just really quick bug-free transfers between the internal and external. Been using for a couple of weeks now.
This has led me to one conclusion: exFAT support in CM is horrible. It should either be fixed or dropped entirely.
PS. Mine is also 128GB. I was toying with sending the card back until I switched over to EXT4.
droident said:
I formatted the card to EXT4 and it's improved things massively. No more hanging/crawling transfers and no more surprise unmounts - just really quick bug-free transfers between the internal and external. Been using for a couple of weeks now.
This has led me to one conclusion: exFAT support in CM is horrible. It should either be fixed or dropped entirely.
PS. Mine is also 128GB. I was toying with sending the card back until I switched over to EXT4.
Click to expand...
Click to collapse
Excellent tip. I will try EXT4 then. Possible issue with Win7 exchange, but I'll try Paragon's ExtFS for that. I have MiniTool Partition Wizard for the EXT4 partitioning. For data on my 128GB SDXC card, I have large collection of music flac and wav files and some other misc jpg photos, and of course I want to store ROMs and TWRP backups etc on the same card. I will report my findings later in a couple of days. I'm hoping that it works for me too, because I really would like CM13 or ROM based on CM13 (like latest RR). I'm trying it on my NOS (New Old Stock) LG G3 - which is new for me. Thanks again -
Hello all,
I have HTC 10 already rooted with TWRP and SuperSU running Stock Android 7.0.
I'm happy with Stock room but most probably I'll install LinageOS.
I have options and questions in my head to reconsider:
Restricted SD card access - I agree with it (after what I red just recently), but my idea was to use advantage of 128GB (fast one) card and store various app data to it. I was used to "full SD card access". I was thinking just format it as adopted but It would get wiped after ROM reset (which shouldn't happened that often once I'm settled down). But how is going to be SD card access on TWRP backup and recovery?
I red somewhere splitting SD card but it seems not necessary.
I don't know yet but how does LinageOS 14.1 handle SD card?
I would love to here there is simple solution for SD card for Android 7.0 (is it Nugat?...) or LinageOS 14.1. Because I have tried SDfix but didn't work because Error information - "no groups specified in WRITE_EXTERNAL_STORAGE".
What solution wold you recommend? What options do I have?
BTW: Also I have in plan to start setup with ElementalX Kernel to get more functionality possibly?...
EDIT:
Should I use App2SD/Link2SD maybe?
Hi all,
I'm using an LG Nexus 5X with a custom ROM (LineageOS 15.1)
Device Background (upgrade path etc)
I upgraded from LineageOS 14.x via recovery.
Appart from initial trouble with the wizard (couldn't switch apps via recents or get notifications until editing some properties manually), and an occaisional hang on the google screen between restarts (boot to recovery and reboot typically solves it), all is working well.
On Lineage 14 I had to perform some unantural acts to get OTG working. Whilst I could mount with root, the fusemounted sdcard (and SELinux I suspect) was preventing anything other than root writing (and even reading) the contents of my flash drive.
After a lot of fussing about, I got OTG working by simply running:
Code:
sm set-force-adoptable true
Note however that I was NOT using the device as internal storage. It was a simple NTFS system.
After the upgrade to Lineage 15, I can no longer use OTG (neither my NTFS drive or my Fat32 drive).
I've not modified the drive between last I used it on Lineage 14, but when I plug it in, I get a message saying the usb drive is "corrupted" - and the phone offers to format it. I don't want to format it to Fat32. exFAT is fine. Really extfs would be ideal, but I'm not going to limit my files to 4GB size just because of android.
I don't believe this is a Lineage issue. Android has historically been cagy about allowing external storage to be mounted, so my hunch is some new permissions/security model in oreo.
Posting mainly as all other posts on the net tell you to reformat. I know for a fact this is not necessary (because of working on Lineage 14).
EDIT: Please do let me know if you've figured how to have OTG devices connected correctly. MiExplorer etc work, but it's not the same. With OTG working properly, I don't need root and all apps (that support OTG of course) work.
EDIT2: so my drive was formatted to exFAT not NTFS. The moral of the story:
Format as NTFS if you want plug'n'play support on Android 8. Haven't tried extfs. exFAT definitely didn't work though.
exFAT is patent encumbered. Not all manufacturers have paid the patent fees to be able to use it.