Gallery & other apps not able to read USB Storage - Nexus S Q&A, Help & Troubleshooting

NS4G
So i was running burns' CM10 and everything was perfect. I recently flashed Jellybro and Baked. Both roms are unable to access the usb storage via certain apps. Gallery cant read anything and settings like reading the usb storage for ringtones are unable to access it, although solid explorer is able to access the usb storage just fine. I flashed back to my burns nandroid and it is still able to read usb storage. nothings wrong there, but these other roms cant. Two different ones, dont know what the deal is. Any help?

I'm having the same issue here. I did a lot of reading today and heard a lot about the whole /storage/sdcard0 thing. Maybe that's part of it? Would love to know if there's something we can do for a temporary fix or if we're just kind of stuck for now. I'm running euroskank's jellybro.

Update on my situation: everything is back to normal now. The only thing that changed for me since was ROM Manager got an update. Changelog mentioned something about .nomedia files being place in wrong places.

So you just updated ROM manager? Not your recovery?

Yah, just the market update for Rom manager. Dunno what that changed, but now my gallery is working and play music finds songs.

Alright. I'm going to try that with those two roms I was using. I normally uninstall ROM manager haha. So thank you for the update and hopeful fix.

karnoff said:
Alright. I'm going to try that with those two roms I was using. I normally uninstall ROM manager haha. So thank you for the update and hopeful fix.
Click to expand...
Click to collapse
well the update of rom manager worked on blackbean but not on jellybro...
trying a manual delete

Related

[Q] can someone help me please

ok here goes.......
I've updated to d107, im using noob's new rom, everything is fine EXCEPT I cant for the life of me get rid of the ****ing asphalt demo. I have root manager, root explorer, titanium, everything (licensed versions also if that even matters) and everytime I try to delete/remove and reboot that simple bastard is still there. I mount as r/w in two of the above mentioned programs and still nothing....is there something that im missing or something else that i should be doing? it just figures, I can re-install this that and the other rom,update,removed apps etc without any kind of problem ive seen mentioned on here, but when it comes to that demo (my now arch nemesis) I cant remove it!!! thanks for the help everybody.
specialk0324 said:
ok here goes.......
I've updated to d107, im using noob's new rom, everything is fine EXCEPT I cant for the life of me get rid of the ****ing asphalt demo. I have root manager, root explorer, titanium, everything (licensed versions also if that even matters) and everytime I try to delete/remove and reboot that simple bastard is still there. I mount as r/w in two of the above mentioned programs and still nothing....is there something that im missing or something else that i should be doing? it just figures, I can re-install this that and the other rom,update,removed apps etc without any kind of problem ive seen mentioned on here, but when it comes to that demo (my now arch nemesis) I cant remove it!!! thanks for the help everybody.
Click to expand...
Click to collapse
no need to mount....just use root manager and delete the apk and odex if it is present....cannot remember if it is......should be gone...I have removed it numerous times already...belive me it works...
ok thanks man, I'll give it another try...cant figure out for the life of me why this isnt working....I know that i'm surely missing something so simple.
on another note, flyers huh?.....kidding they had a hell of run last year. being from pittsbugh i love the penguins. hopefully we can win another one
i have no idea!!!
tried exactly what you said and its still there - went into titanium looked at properties of app - said only this: libasphault5.co
looked for it in corresponding folder and no luck.....I may have missed a step or uninstalled it incorrectly? still working on it
wow pretty stupid on my part - over complicating as usual.....all fixed - thanks again!

[Q] [ROM] Clemsyn's Ultimate 6 ROM missing "My Cloud"?

I know that this would be better served in his thread, but I'm a newby to posting althought I got one of the first Transformers, but I have just installed Clemsyn's new Ultimate and "My Cloud" seems to be missing. Just wondeing if anyone else has had this issue.
I have formatted everyting and of course formatted my external SD card in the process which of course had my titanium backup.. but I digress..
Anybody else have this issue.
FYI I'm sure this is just me and Clemsyn's Roms are the best in my opinion.. They make this thing fly.
I just did a factory reset and then re-installed a fresh download of his ROM so I'm now thinking it's just not me but that it's supposed to be gone? I really liked that Asus was including that..
Any clarification would be greatly appreciated.
Thanks.
Open the stock zip up and look for the apk in /system. Pull the APK and put it on the TF and install it
Thank you very much for the quick response..
I downloaded the firmware and of course it hasn't been broken down so that you can edit it so I was unable to get to a /system folder.
Downloaded prime 1.9.1 and saw the .apk located there.
I enabled side loading to install it and when I try I get the blurb screen that says it's going to modify stuff and then I get
X Application not installed.
Any ideas? I PM'ed Clemsyn and haven't heard back yet, but I can only think this was excluded by accident as I wasn't able for find a reference for it.
Any ideas on how I can get it installed?
Thanks again.
Ha.. Saying that you have to install that APK made this seem WAY more complicated than it is. You simply have to drop it into the App folder and reboot the device... So easy to do that I'm actually ashamed I had an issue with it. ;-)
FYI a You Tube video showed the very simple steps.
Thanks ;-)

[Q] Samsung Infuse Gingerbread 2.3.6 update caused camera and music player problems.

I recently updated my Samsung Infuse to the fairly new Gingerbread 2.3.6 update. It was a modded version I think, my brother applied it for me, it was suppose to come rooted (why I believe it's modded.) When I open my camera, it says, "camera failed" and I have to restart my phone to get it to work, which I shouldn't have to do. When I try to play my music it says something along the lines of 'music player cannot play this type of file' (i will post exactly what it says when I find out.) When I do restart phone it works fine for a few hours but then messes up again. I have had my Samsung Infuse since December, and had problems with the first one I had, it would say the Sim was inactive and it had a dead pixel (as does this one but I don't mind where it's at) and had it replaced and this is the first problem with this one. Please help me I would really appreciate it. Thanks in advance!!
How long ago was it updated, and can you find out for sure what rom was used to update the phone? I've used all of the stock based Gingerbread roms on here, and have never had any of the problems you describe.
Get us a little more information, though, and maybe we can help you troubleshoot. The camera problem sounds hardware related if you are in fact on a stock Gingerbread rom. Also, what type of music file are you trying to play?
My brother said it was just the stock rom with root added. It was applied just yesterday, and the music file are all MP3, And everything works perfectly fine after a reboot.
Sounds like something wasn't done right. Here's what I would do, because something is corrupt.
Back up all music files, etc. to your computer.
Go to this link for the package that I put together (It's nothing fancy, just the exact bits from Samsung / AT&T for UCLB3 Gingerbread with root added.):
http://forum.xda-developers.com/showthread.php?t=1613523
Reinstall the package. After you follow ALL of the instructions there, including the ones for wiping user data and cache, let the phone boot.
Go to settings / sd card and phone storage / Format USB storage. Let it format.
If you've kept music files on the external sd card, format both the internal sd and the external sd. Be sure that you've saved anything you want to keep to your computer, because this will wipe these partitions clean.
After that, go to settings / privacy / factory data reset / reset phone and reset the phone to factory defaults.
Put your music and other files back on the phone.
I can't do a reset yet. I wait a little while to see if it fixes over time, if not, then I will do all that. Thanks for the help. I know you probably won't wait for that long, because it will be around a week or two, so thank you.
Could well be that he installed Dman's rooted stock Rom but didn't follow the instructions completely. After you install the rom, you need to flash the stock kernel. Here's his post: http://forum.xda-developers.com/showpost.php?p=22775901&postcount=1
Does that sound like it could be the problem? You talk about music playback - I don't know the extent to which that could be a problem. Anyway, just a thought. Check in with other people here before you go flashing your kernel!

[Q] "Lost root" after busybox upgrade - Cannot r/w to / !

[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
If only you have working CWM installed. You could just flash this Superuser3.0.7.
Ah, but the plot thickens. I had superuser on there. I even uninstalled and reinstalled it. No dice.
Update: I said fuggit and did a factory reset. However, my wifi is still not fully connecting to my network although it has no problem finding it. I don't have a recovery image on the external SD and unless i get the network working, will have to wait until tomorrow to get a working microsd->usb adapter to put it on there.
I CAN still get into CWM, thank god.
Current rom is stock 8.6.6.19
Razorclaw gives an error when trying to root.
Also, when trying to moust USB from the recovery menu. it fails, saying "E:unable to upen ums lunfile (no such file or directory).
I am hoping this will magically get fixed after re-installing stock from the SD card ... and that my device isn't somehow crippled.
Sorry for the massive details, but more data = better.
It will magically get fixed
I recommend you flash any Totally stock ota. Then upgrade to the latest OTA, then use my tool PERI (or another) to install recovery and root. Then you should be all fixed up.
Well, it looks like I did get things back on track, but oddly enough, neither of the standard OR modified for root stock ROMs would work. One just wouldn't install, another failed halfway through. MD5s checked out and everything. I had put Revolver 4 beta on there sort of as a "just in case", and that one installed fine (and I was pleased when it displayed "installing Busybox symlinks").
Phew. CLose close call. Now to deal with the bull**** of setting stuff back up again.
However, the question remains: I'm assuming this whole thing happened because of the busybox update and me accidentally installing it to /bin instead of /xbin, and I think it "cleaned up" its own symlinks or something.
I'm not saying don't update your busybox, although I'm sticking with what works and **** upgrading anymore, just be careful...
Thanks for the help!
Recently I used the busybox installer to update my busybox version and it went through great... but after reboot it reverted back to the old version.. And I never touch it since.. don't want to take the hassle further..
There are certain 'plague' versions of busybox that simply don't work. I'd find that list of working BBs and STICK with one that's good. I'm still on 1.63 or someat like that.
Mangraa said:
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
Click to expand...
Click to collapse
You may have been hit with a bug I introduced.
There was a bug with version 8.0 of my application.
There is not an issue with Busybox V1.20.1.
I apologize for this bug, the application symlinked all applets to Busybox and on some devices there are applets which are unique to the device and should not be replaced by those offered by Busybox.
A simple way to fix this is to simply reflash your rom. You do not need to wipe or clear any data. This will fix the issue and you can update Busybox normally with my application as long as it is version 8.1 or higher.
I apologize for the frustration I have caused, please let me know if I can do anything to help you further. I am trying to find people who were affected to see if I can help rectify the situation.
yeah me too
I guess I should have done a more recent backup. I tell you, there is a reason i have 38 updates waiting, everytime I start going through them, boom blows up in my face

[Q] two storage locations maybe?

I don't even have any idea how to search for this or even ask about it. I'll try!
Okay, so after having trouble with 4.2.2, I decided to flash an older rom. I had some problems with wifi logo turning white and not being able to connect to Google, so I searched for a new gapps to flash. I was having computer trouble, so I downloaded it onto my phone, it saved to the downloads folder. I also had noticed none of my other files were in there, which kinda freaked me out, but the same amount of space was being used on my internal memory (I don't have a SD card). Anyway, I went to go flash it with twrp and went to downloads and saw all my OLD files, which didn't include the new gapps download. So, I went to root explorer after rebooting and moved the gapps to my root folder, then restarted to recovery and it's not there. The only thing I can think of is when I'm in recovery, it just says sdcard, when I'm in the system, it says sdcard0.
Does anyone know what's going on and maybe something I can search for? This is weird. My files are clearly there and I just can't access them... even with full root access!
Sorry if this didn't make a lot of sense, I have no idea what's going on at all and I'm also kinda tired. Hope you can help!
------ I found the answer here: androidforums .... /verizon-galaxy-nexus-all-things-root/649940-4-2-sdcard-sdcard-0-observation.html
My tired brain finally kicked in and I searched sdcard0 and figured it out. Now, I guess I have to move stuff so I can use the old os. I'm only not deleting the post because it might helps someone. And I'm sure modifying links isn't allowed but I can't link with less than 10 posts and I wanna make sure people get the answer, so... yeah... Add com in the middle.

Categories

Resources