Since we had such an excellent turn-out in the ideas for lag-on-wake thread, resulting in a team effort to get the kernel bug identified and fixed, I figured we could do the same for the SD Card issues in the Viewsonic source code that result in some apps disappearing or being unable to install unless you unmount the internal SD card area before installation.
Rothnic does have a request into Viewsonic, since they seem to have addressed this issue between their two kernel builds but they neglected to release the patch for it.
But... that could take several days or several weeks to trickle through the bureaucratic food chain. I suspect this is a small change if we can isolate the area.
What I tried so far:
Just the dumb-obvious. There are three mmc drivers directories in the VS patch, mmc, mmc_orig, and mmc-new. The only one getting built is the mmc directory. I diffed the mmc and mmc-new files, and tried building the mmc-new driver instead, but didn't observe any difference in behavior with respect to the mounting issues (i.e. error -18 when I try to install Angry Birds from market). The diff between these driver file sets is quite small, and limited to a few files.
What I suspect:
There is an "install to SD card" option built-in to some apps. I suspect that the apps affected by this may be the ones that enable this option. Perhaps something to do with the loopback device Android tries to create on the SD card for external app storage (http://android-developers.blogspot.com/2010/07/apps-on-sd-card-details.html)?
Why this relates to the kernel:
Well, the issue doesn't occur with the latest kernel build from Tap N Tap and does with our kernels. There are user-space workarounds (unmounting SD card) and some of that may be workable into our ROMs, but I'd like to get a kernel that is a drop-in replacement for the stock kernels.
Consider the following patch which just enables some "stuff" in the kernel.
http://nv-tegra.nvidia.com/gitweb/?...it;h=555d0c0e5b9a86b5e291216d59406709b34480d6
For me clicking on the link you included yields a page not found...
rcgabriel said:
Since we had such an excellent turn-out in the ideas for lag-on-wake thread, resulting in a team effort to get the kernel bug identified and fixed, I figured we could do the same for the SD Card issues in the Viewsonic source code that result in some apps disappearing or being unable to install unless you unmount the internal SD card area before installation.
There is an "install to SD card" option built-in to some apps. I suspect that the apps affected by this may be the ones that enable this option. Perhaps something to do with the loopback device Android tries to create on the SD card for external app storage (http://android-developers.blogspot.com/2010/07/apps-on-sd-card-details.html)?
Click to expand...
Click to collapse
rcgabriel said:
some apps disappearing or being unable to install unless you unmount the internal SD card area before installation.
Click to expand...
Click to collapse
Is it possible to unmount the internal SD card area while running the OS? I've used the mount / unmount options in CWM, but have not found a way to unmount /sdcard inside the OS. Wouldn't this be like cutting off the branch you are standing on? I'm currently running TnT Lite 3.1.2. Thanks.
Just a thought, but how does a standard android system's mounting structure run? Isn't it something to the tune of some other root folder than /sdcard, and when an sdcard is inserted that gets mounted to /sdcard? Is there a reason we don't have our roms mounting in this way, and would this not improve compatibility with the android system and apps as a whole?
If the issue is that people would then have to have an sdcard for a lot of things, perhaps we put those to /sdcard2 and partition a gig or two slice of the internal storage to mount at /sdcard so the internal storage can abide both concerns..
Am I way off in just thinking the systems mounting structure might be better served to mirror a standard android system? Does it already and I'm just being dingy?
vsc said:
Consider the following patch which just enables some "stuff" in the kernel.
http://nv-tegra.nvidia.com/gitweb/?...it;h=555d0c0e5b9a86b5e291216d59406709b34480d6
For me clicking on the link you included yields a page not found...
Click to expand...
Click to collapse
Fixed that link, but yeah, that looks like a very promising patch, and it's just config file changes....
The question is whether the CONFIG_BLK_DEV and CONFIG_BLK_DEV_LOOP stuff is also dependent on other patches to the mmc driver or other kernel files.....
EDIT: I cherrypicked the relevant-seeming config file changed from that patch, rebuilt the kernel, and am testing it.
BINGO! Angry birds installs again without having to remount. More coming...
See config_patch attached for the specific changes I made. For kernel devs, just unzip this into your arch/arm/configs dir and patch -p0 < config_patch.
I figured...
The thing that I don't know is why does TnTLite not have issues. But this can't hurt. Post your config so we are working with the same configuration and I'll give it a try with TnTLite.
rcgabriel said:
Fixed that link, but yeah, that looks like a very promising patch, and it's just config file changes....
The question is whether the CONFIG_BLK_DEV and CONFIG_BLK_DEV_LOOP stuff is also dependent on other patches to the mmc driver or other kernel files.....
EDIT: I cherrypicked the relevant-seeming config file changed from that patch, rebuilt the kernel, and am testing it.
BINGO! Angry birds installs again without having to remount. More coming...
Click to expand...
Click to collapse
vsc said:
I figured...
The thing that I don't know is why does TnTLite not have issues. But this can't hurt. Post your config so we are working with the same configuration and I'll give it a try with TnTLite.
Click to expand...
Click to collapse
Config uploaded above. I included the crypto stuff because I believe the loopback block device that Android uses requires it, but everything may work without it. Not certain.
I think the crypto stuff is required.
rcgabriel said:
Config uploaded above. I included the crypto stuff because I believe the loopback block device that Android uses requires it, but everything may work without it. Not certain.
Click to expand...
Click to collapse
Very nice find guys.
Have now integrated this into my kernels posted in the lag-on-wake issue thread.
v12xke said:
Is it possible to unmount the internal SD card area while running the OS? I've used the mount / unmount options in CWM, but have not found a way to unmount /sdcard inside the OS. Wouldn't this be like cutting off the branch you are standing on? I'm currently running TnT Lite 3.1.2. Thanks.
Click to expand...
Click to collapse
I Have the same question...I dont run cwm
Posted an update for TnTLine on the other thread as well. My problem is when I reinstall AB and run it I have to force myself to get out of the game....
rcgabriel said:
Have now integrated this into my kernels posted in the lag-on-wake issue thread.
Click to expand...
Click to collapse
I think enabling twofish under crypto would fix this. Will build one later when I get home: )
Update:
I basically enabled two fish and others..The most important thing was to install Devmapper and Dev Crypt in the kernel to get it up and running..Consider this issue SOLVED.
OK got Angry Birds installed without unmounting SD. Will continue testing..Everything seems to be fine..I'm uploading..Please test...Just put clempatch.zip in your internal SD and install.
vsc said:
Posted an update for TnTLine on the other thread as well. My problem is when I reinstall AB and run it I have to force myself to get out of the game....
Click to expand...
Click to collapse
Try my fix above
Related
Hi everyone
I've been applying the SD fix with the V4 kernel, but now i'm wondering what exactly it is. In theory, could the SD fix be applied without it?
aciduzzo said:
Hi everyone
I've been applying the SD fix with the V4 kernel, but now i'm wondering what exactly it is. In theory, could the SD fix be applied without it?
Click to expand...
Click to collapse
Well the first question is a simple question without an easy answer.
The last question is easy, the answer is NO.
The Linux kernel is the software program which directly controls the hardware.
It contains low level software which drives the cellular radio receiver/transmitter, video and audio hardware, touchscreen, etc.
It also contains the software which implements the filesystem types, so that you can create/read/write files and directories on the storage chips, either SD-cards or built in the device.
The SD fix depends on writing the data in a different way than the old MSDOS FAT filesystem which is normally used on SD cards. It writes a Linux filesystem, either ext3 or ext4 (ext 2 would probably work too).
These ext3/4 drivers are not in the stock kernel program, so you need a different kernel.
I personally wouldn't use the fix, and wait one or two months for the official newer firmware of flash newer firmware. Newer versions of firmware have also almost no lag.
thanks very much for that tomtor!
I have updated ClockworkMod Recovery for the G Tablet to support the internal SD card a bit better.
There is now an advanced option to partition the internal SD card. This can come in handy when the internal partitions get hosed (which seems to happen on occasion with this device). To keep it close to stock you can select a 2048MB Data Partition and the remaining ~13GB will go to the internal SD card. You also have an option to format the internal SD card space as well as mount it as /emmc. You can still format the external SD card using the existing advanced option.
This recovery still uses the external SD card as its primary mount for actions (install ROM, backup, restore, etc.). However, the recovery is configured to “fall back” to the internal SD card for these actions if (and only if) there is no external SD card available to be mounted.
As always, credit to Koush for creating ClockworkMod Recovery in the first place.
----------------------
This is the current BETA release of the CyanogenMod 6.1 port for the G Tablet. There are still several issues, but it is far enough along that I use it as my daily system. Please review issues and post new ones as needed at the Issues page linked below. Feel free to leave feedback in the forum, but I may not be able to follow up on it. The best option is to catch me in #tegratab on Freenode IRC.
CyanogenMod 6.1 Beta4
CyanogenMod 6.1 Beta4 - MD5
ClockworkMod Recovery
My site: bekit.net post
gapps does work, but I probably should not release that here. Just make sure it is the MDPI variety and has an update-binary compatible with tegra.
*Note:
This version now matches the standards for SD card mounting on devices with both internal and external SD card space. This means that the external SD card slot now mounts to /mnt/sdcard (symlink /sdcard) and the internal space mounts to /mnt/emmc (symlink /emmc). The device properly recognizes the internal vs. external space and allows proper unmounting and handling of the external SD card. This also means that some apps (if they were coded poorly) will not recognize the internal SD space as available SD card space and will require you ti insert an external SD card. I will see if I can do something about the default apps (read: camera) that have this problem; other apps will need to be fixed by the developers.
Changelog:
CM6.1 Beta4:
Updated SD mappings for internal/external SD space to match standards (see note above)
Using latest available source from the CyanogenMod repo
Updated kernel to latest G Tablet version (still waiting on source so we can build our own)
Updated to the lasted drivers available for the G Tablet
Included updated libGLESv2 from nvidia (Angry Birds!)
Proper setup of CPU values - this allows the folio Flash APK to install properly
Matched fingerprint and device settings to latest G Tablet values
ClockworkMod Recovery 2.5.1.3 (2010.12.11):
Added options for managing the internal SD card
Using latest available source from the CyanogenMod repo
ClockworkMod Recovery 2.5.1.2 (2010.11.24):
Updated SD mappings to match standards (see note above)
Using latest available source from the CyanogenMod repo
Enjoy!
-Brint (bekit)
Nice may try it on one of the other g tabs I picked up today.
Thanks for all the work
Happy Thanksgiving to you too!!! and I will enjoy this for desert.
Works like a charm! We all love you! Now wish this damn camera would work right >_<
Awesome, Thank you for putting this together!
Do you know if it addresses the slowdown problem that was present in cmb2? (After using it for a while,browsing etc would slow down till you did a reset)
As usual amazing work. Everything is rock steady. Only things I added were Spare Parts to maximize some apps and a certain keyboard replacement that starts with S.
titanium backup is not seeing my internal sd card, is this a known issue? also i'm unable to mount sd or external sd to computer, the window closes when i try to. the rom seems to run smoothly though.
Thank you Bekit!
First time posting here in ages. Is there a trick to getting the audio working? No audio here, except for a freak accident. Not sure how or why it started working out of the blue, rebooted now it's gone again.
happy turkey day!
Crimton said:
titanium backup is not seeing my internal sd card, is this a known issue? also i'm unable to mount sd or external sd to computer, the window closes when i try to. the rom seems to run smoothly though.
Click to expand...
Click to collapse
Same here and Kobo wants /mnt/sdcard. I've uninstalled both and re-installed in case something changed with beta4 that they'd cached but it didn't change anything. I've found the Titanium Backup official support site (www.legendroid.com/forumdisplay.php?27-Titanium-Backup-Official-Support) but haven't done through it yet ... turkey'd almost ready so it may be a while. Folks out east (or north or anywhere that this isn't a holiday) may wanna check in there.
EDIT: Meant to thank you, bekit, for your work on this. Sorry, was distracted by the smell of nearly done turkey!
No SD card here as well. Do I need to install the newest recovery?
Will be kinda hard to download anything.
Thanks for this update! As with all releases, I will try this one out as well. It's great to have choices in firmware, and at this stage, these firmwares are really-REALLY nice.
Happy Thanksgiving to you, too!!!
puppyfarts said:
Thank you Bekit!
First time posting here in ages. Is there a trick to getting the audio working? No audio here, except for a freak accident, not sure how or why it started working out of the blue.
happy turkey day!
Click to expand...
Click to collapse
Try plugging/unplugging the headphones, has worked for me in the past.
Turbo4V said:
Try plugging/unplugging the headphones, has worked for me in the past.
Click to expand...
Click to collapse
Mind=BLOWN! Thanks!
I can't get the recovery installed. Can I get an update.zip?
I can't install anything from the market. I keep getting not enough room on card? I have internal card selected in CM settings.
I tried installing this, making sure to put on the new clockwork and clearing user data, and when I was all done and went to reboot I got "magic value mismatch" no matter what I did. I was able to get into nvrecovery but flashing the old clockwork wouldn't fix it. I finally gave up and flashed the stock image to get going again, blowing away my internal SD titanium backups. Not a huge loss, but if anyone else is thinking about trying this, copy anything important off the internal SD just in case.
*edit*
Whoops, scratch that, apparently the nvrecovery stock image install doesn't wipe the SD, everything was there when I was done and flashed Clockwork again.
This is running well and I am seeing very smooth scrolling in the browser. That has been my biggest complaint with the gtablet.
Spaztik said:
I tried installing this, making sure to put on the new clockwork and clearing user data, and when I was all done and went to reboot I got "magic value mismatch" no matter what I did. I was able to get into nvrecovery but flashing the old clockwork wouldn't fix it. I finally gave up and flashed the stock image to get going again, blowing away my internal SD titanium backups. Not a huge loss, but if anyone else is thinking about trying this, copy anything important off the internal SD just in case.
*edit*
Whoops, scratch that, apparently the nvrecovery stock image install doesn't wipe the SD, everything was there when I was done and flashed Clockwork again.
Click to expand...
Click to collapse
Same thing happened to me. "magic value mismatch" It's not to magic, lol. Off to NVflash I go. (lost everything).
flashed new cwm 2.5.1.2, then flashed beta4... mismatch lameness
anyone figure this out yet?
puppyfarts said:
Thank you Bekit!
First time posting here in ages. Is there a trick to getting the audio working? No audio here, except for a freak accident. Not sure how or why it started working out of the blue, rebooted now it's gone again.
happy turkey day!
Click to expand...
Click to collapse
Try pluging in headphones and then take them out.
Had the same exact problem.
(Oops... missed the fact that it was already answered!)
Thank you SO much! This is finally a usable ROM for this hardware-rich unit.
I have two questions:
1. Can anyone compile/provide a tun.ko file for this kernel? I would like to use VPN Connections on this device.
2. Is anyone else experiencing odd slowdowns after the device wakes up? When I first boot the device works smoothly. After the device is off and then turned back on, I sometimes experience an unbelievably laggy performance...
Thanks in advace!
Hi all,
I'm starting this thread because I didn't see something quite like what I was looking for to answer some questions I had about exFAT vs FAT32. The question is, essentially, which file system is best to use with this high-cap SD card? If this thread is redundant, please let me know and/or direct me to the appropriate thread.
The reason I started looking for information is because of strange storage symptoms I was experiencing after introducing a SanDisk 64GB Class 10 SD card to my Verizon Note3. I first noticed the symptoms after taking the NC4 OTA (first mistake, I know). Nonetheless, the symptoms were there. I eventually followed some instructions to install BajaROM (thanks @az_biker and @barrackOBAMA) since the issue of r/w to SD card was addressed in that ROM, and since I could use that ROM on the NC4 OTA base. However, the symtpoms persisted. One thing I noticed happened when I was re-installing apps on the new ROM. One, in particular, was MinecraftPE, purchased legit through the Play Store. I would install the app, and it would open and function correctly. Then, when I rebooted the device, the app would not run from the app drawer. The app would still be listed in Settings > Applications > Downloaded, but it was listed as 0.00MB installed. If I executed the app from the lingering icon, I got the message "App not installed on this device," which would open the Play Store to re-install the app. But the app wouldn't install at that point, since it was still registered as installed, per Settings > Applications. I had to uninstall from Settings, then reboot, then open Play Store to re-install. Ugh! I was able to get the app to install "correctly," though not as preferred (App2SD), by un-mounting the SD card prior to executing the install from Play Store.
One other major issue involved using the stock camera app and saving to SD. When the pic was snapped, and saved to SD, I could open the pic from the gallery link in the camera right then, and even share it. However, if I exited the camera app and opened the stock gallery app separately, the pic was listed as a broken link (or unreadable file?) and I could neither open it or share it or anything. The file was also defunct if I tried to access it from any file manager utility, stock or otherwise. The only "fix" I found for that was simply to save pics to internal storage. Again, ugh, that takes up space quickly.
I've read a lot of information about exFAT vs FAT32 and I've wondered whether the issue is that exFAT isn't a good functional match with Android in general or, in this case, even with custom ROMs. I do not, by any means, assert that I truly understand Android OS, file system/structure protocols, or anything of the sort. I read when I don't understand. I've read varying opinions about which SD card file structure is best overall to use with Android, and about which to use with high-cap SD cards. I see that ext3 is reliable and scalable, but that I'd need to use Linux to access it from off-device. That is a bit more awkward for me. I see that, overall, FAT32 is more reliable for use, and that there's no incompatibility with Windows. I don't really mind that file size is limited to 4GB, so I'm leaning that way.
Also, I found this on TeamWin website, which I found helpful (quoted & referenced). It explained what's what with exFAT (for me, anyway).:
"exFAT is an update to FAT32 file system and is commonly found on 64GB or larger sdcards. exFAT has a different and much more restrictive license compared to FAT32. Due to this restrictive license, we'll probably never see exFAT support in the Linux kernel. Many Android manufacturers (e.g. Samsung, HTC) have cross-licensing agreements with Microsoft that allow them to add exFAT support in Android, but that agreement doesn't mean that we're able to add exFAT support for your device in TWRP.
You can reformat your 64GB card to FAT32. You may need to remove the card from your device and use a computer to accomplish the reformat. You also may have to find and download a third party utility to format to FAT32 if you're using a Windows PC. The biggest downside to using FAT32 is that FAT32 doesn't support files larger than 4GB.
If you need a file system that can support files larger than 4GB and works in recovery, you pretty much have one choice: ext4. Unfortunately Android often doesn't handle ext4 formatted sdcards automatically. You'll probably have to mount the sdcard manually using a shell script, GScript (free app in the market), or an init.d type of script. You also won't be able to pop your sdcard into a Windows computer because Windows doesn't recognize the ext4 file system.
You're also welcome to try NTFS, but the majority of the time, NTFS will only mount as read-only in recovery. The Linux kernel doesn't have very good NTFS support either."
So that's a lot for a post. If you're still reading, thanks. I welcome any and all feedback or insight regarding my SD card "woes," or the issue(s) I presented. I'm definitely ok with learning and appreciate your time and help. Have a great rest of your day.
SscoootzZ :fingers-crossed:
I have my sandisk ultra 64gb formatted fat32. I do not need it to handle files larger then 4gb so no issues for me.
---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------
this is the program I used to format mine...
http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm
Still can't find any useful information on this. I had to do a simple edit to the vold.fstab on my HTC Evo 4G LTE to accomplish this. Now I look at the SGS5 vold.fstab and I know it will require either adding a line or editing another file as well...
I want to use my 64 GB SanDisk instead of the stock internal sd card...
ANYONE?
P.S. I don't want to use 3rd party apps (or anything that doesnt fully switch the internal and external sd card directory links) Somebody must've accomplished this on their SGS5 by now... (Using Sprint G900P towelrooted)
..
fffft said:
Then I'm skeptical that you ah, searched very hard. There are dozens of threads about this, it would be rather hard to miss all of them when actually making a search. I've answered this question myself three or four times myself. Unfortunately it didn't occur to you to tell us how you were searching, so we can't help improve your searches either.
As just one example of many, this script works great on the S5. It completely swaps the internal and external storage spaces and has also been incorporated into the Phoenix S5 custom ROM.
.
Click to expand...
Click to collapse
Cannot download it - it has been removed from d-h.st
..
fffft said:
What can I say? You are categorically wrong. I just tried and it downloads fine.
.
Click to expand...
Click to collapse
lol its back up now. Dunno why it was unavailable eariler.
After looking it over, the script is pretty ingenious... (linking the extSdCard dir to data/media/0) - I will try placing it in my init.d folder and rebooting later.
Had no luck with FolderMount so this should do the trick, thanks.
Hmm...
I had to create the system/etc/init.d folder and now it seems that the 11extsd2internalsd script is not being executed on reboot.
Anything I can do to enable the init.d folder to be recognized?
Running KOT49H.G900PVPU1AND2 - Android 4.4.2
Edit 1: Searched for init.d support and found I should add: busybox run-parts /system/etc/init.d/ (to the bottom of init.qcom.post_boot.sh - and make sure there is a blank line underneath it) - Gonna try and reboot now, let you know what happens.
http://forum.xda-developers.com/galaxy-s5/general/mod-how-to-add-init-d-write-to-external-t2814733
Edit 2: Well I got init.d support (it executed the script and created a data/int2externalsd folder with a .log file) but nothing changed as far as the mounts...
I'm pretty sure my sd card was fat32 but I guess I can try the exfat version to see if thats why its not working... Any thoughts?
Edit 3: Nope still nothing. Both scripts created a intSdCard and "empty" folder in the /data/media/0 (internal sd card) mount - as well as the same .log file
I didn't reformat my sd card prior to execution, but I really doubt that will fix anything... Unless this all truly stems from formatting my sd card I think I will give up for now.
I'm holding off on purchasing a 128 gb card until I can figure this out - I need some help from someone who uses this script and can tell me why its not changing the mounts for me.
Thanks in advance - zmag
tl;dr
The card is tested and good (results below), the card reader is good (tested by reinstalling 5.7.4).
So few other people are having this issue, what is going on with my phone?
--
I've read and read, but no matter what I try, I can't get my SD card to work.
Here's the details of how, and what, I installed on my Sprint S5.
I'm coming from Resurrection Remix 5.7.4 MM, (where the SD card worked fine, but did have a few issues with the camera (used open camera instead) and some post reboot oddness (shortcuts disappearing)).
I first formatted card using the windows software sdformatter to FAT32
copied files to SD card using a card reader plugged into PC.
Files copied
RR-N-v5.8.2-20170304-kltespr-Official.zip
open_gapps-arm-7.1-micro-20170327.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
TWRP 3.X
wiped dalvik/cache/system/data
then factory reset
added files to zip queue, Rom, then Gapps, then SU
Flashed
Phone boots fine, initial set up completes.
Tried a reinstall of apps using Ti Pro, but it failed, so started again and used google apps restore during boot. Issues with many apps. So started again, with a "fresh start" option during set up.
I took a few pictures.
I can view them immediately after taking, by pressing the previously taken image image inside the camera app.
Open default Gallery and get the error "No storage. No external storage available."
I installed a+ gallery and it is able to open the images just fine.
Default Files app can browse the SD card.
Aldiko will not download books, as it thinks there is no SD card installed
I've tried (and checking each time)
formatting in card as internal, then back to portable in phone.
Clearing the data/cache for the apps giving errors.
factory resetting
Wiping and formatting the card (on PC to FAT32), and starting again (several times).
Started from scratch again, with a brand new Sandisk card
Tried ZepherOS Zephyr-N Version (Viserion-6.1) Android 7.0
Wiping cache/dalvik only and rebooting
Same "No storage..." error, every time.
I tried ZephrOS. Right after install there is no file manager, but if I click the default app "downloads", I can navigate to the camera folder, then to the image. When I click on it, it opens the image, but still shows the same error "no storage..." even though I'm looking at the image behind the error window. :/
I'm running H2testw, but don't expect an issue, as the same error was on the previous card and the brand new card.
Can I go from 7.0/7.1 to a stock ROM without issues, if so which one?
Update:
SD card test result
Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 7.15 MByte/s
Reading speed: 15.7 MByte/s
H2testw v1.4
UPDATE #2:
I started fresh with a new install of RR 5.7.4 and the card does still have issues with some apps, but is working fine with others. Open camera works fine, and the gallery access the correct card in this ROM. Aldiko still fails as it's trying to download to /sdcard
Most apps are looking for /sdcard but I have /sdcard1
If it helps, it appears sdcard is symlinking to /storage/self/primary
Anyone able to help?
permissions issue? have you gone into the apps mgmt and set the permissions manually?
youdoofus said:
permissions issue? have you gone into the apps mgmt and set the permissions manually?
Click to expand...
Click to collapse
Thanks for the reply. Yes, settings>apps>settings>App permissions>Storage is turned on.
Aldiko, for example, is looking for /sdcard but it doesn't exist. I'm thinking a symlink might fix the issue? But am not familiar enough with Android under the hood, to know what other issues that might cause.
syco123 said:
Thanks for the reply. Yes, settings>apps>settings>App permissions>Storage is turned on.
Aldiko, for example, is looking for /sdcard but it doesn't exist. I'm thinking a symlink might fix the issue? But am not familiar enough with Android under the hood, to know what other issues that might cause.
Click to expand...
Click to collapse
im not familiar enough with the under the hood stuff to know what else coul be the issue either, @AthieN, Mr. guru thoughts?
youdoofus said:
im not familiar enough with the under the hood stuff to know what else coul be the issue either, @AthieN, Mr. guru thoughts?
Click to expand...
Click to collapse
What file system is the card formatted in? Try ext4 or exFAT.
AthieN said:
What file system is the card formatted in? Try ext4 or exFAT.
Click to expand...
Click to collapse
FAT32 this was recommend in most places I read. I thinks it's a paths issue. I'm not sure the format would make a difference to that, right?
syco123 said:
FAT32 this was recommend in most places I read. I thinks it's a paths issue. I'm not sure the format would make a difference to that, right?
Click to expand...
Click to collapse
A fresh install would resolve any path issues. The device can't read the card, which means that it's formatted incorrectly or is incompatible. How did you format it originally? On a computer? Go into the storage menu, and if it's detected, then try using the native Android option to reformat it. Back up your stuff first.
If that fails, try formatting it in recovery.
AthieN said:
A fresh install would resolve any path issues. The device can't read the card, which means that it's formatted incorrectly or is incompatible. How did you format it originally? On a computer? Go into the storage menu, and if it's detected, then try using the native Android option to reformat it. Back up your stuff first.
If that fails, try formatting it in recovery.
Click to expand...
Click to collapse
thanks for chiming in sir! your help is always appreciated
AthieN said:
A fresh install would resolve any path issues. The device can't read the card, which means that it's formatted incorrectly or is incompatible. How did you format it originally? On a computer? Go into the storage menu, and if it's detected, then try using the native Android option to reformat it. Back up your stuff first.
If that fails, try formatting it in recovery.
Click to expand...
Click to collapse
Thanks, I know the OP was long, but I hoped the details of what I'd already tried would be appreciated. I did several fresh installs trying to fix, and formatted every which way I could in phone and on a PC. Nothing has worked.
I've kind of given up on this and have decided to switch to Verizon. Sprint sucks so bad, after 10 years I've finally had enough, so I have to replace the phone anyway.
If you know of a decent phone to get, I'm looking for a recommendation in this thread, https://forum.xda-developers.com/android/help/switching-to-verizon-200-phone-t3588790
Thanks for your attention to my issue. Sorry it's left unresolved. I run my own business and just can't spend this much time fixing my phone.