I know I have to mount the external sd card as mass storage device so it is recognized by the car audio.
But some folders and artists /albums are visible in the car audio and some others are not.
But I do not know how to put them on the sd card so the car audio will always see them.
The file explorer in the phone sees them without any problem.
In the car I cannot see them whether I search on artist or just do a directory search.
Is it possible the audio codec of some of these files (although they are named with the .mp3 extension) is different than mpeg layer3 format? Or... maybe some of the filenames on the sdcard are longer than a certain length? (i.e. maybe the car deck has a path/filename character limit that it can read?). I suppose it could be many things.
I have seen mass storage mode not work very effectively on Sony devices (ZL, T) when connected to PC. It would list maybe half of the files that exist in a folder (maybe it times out or gives up?). Have you tried connecting via mass storage to a PC and verify that files aren't shown there either?
Related
I have a Kaiser and a car stereo (Blaupunkt Hamburg) with a USB port. The car stereo can read "Mass Storage Devices" - ie USB flash drives. However, HTC phones are Activesync not MSDs.
You can get software to run on your PPC, such as Softick Card Export, that turns the PPC into a MSD, but this locks the storage card, so other software (eg TomTom satnav) cannot run on the phone whilst the device is in MSD mode. I am not sure if this is a hardware limitation or a limitation of softick's software, they have not gotten back to me on that one.
So I got to thinking - is it possible to make a USB dongle that converts Activesync to MSD? It would have to wrap the protocols or something but I guess it is within the realms of feasability.
I just want a solution so that I can have TomTom running on my phone screen, but still browse the music stored on my phone's SD card on my car stereo head unit.
Any ideas?
Have you tried WM5torage? It's free and I believe it has an option to avoid locking the SD card.
So, just got my GN and loaded up some music on it and synced my Play library.
Drove to work this morning without any music because the USB mount options are for Media (MTP) or Camera (PTP) which, I guess, my Pioneer head unit cannot support. Is there a way to just have it mount as USB storage? I thought that Camera option would be the "old school" USB mount but I guess not.
The phone itself is stock - I have not made any modifications to kernel or rom yet.
wergeld said:
Is there a way to just have it mount as USB storage?
Click to expand...
Click to collapse
No. The Galaxy Nexus does not support USB mass storage mode. If your head unit can't do MTP or bluetooth, you're out of luck.
There are several threads on the topic you can search for if you want the details on why this is, but it basically comes down to the fact that the phone has no separate /sdcard storage inside - it's all one big chunk of flash memory and can't be mounted as mass storage because the phone is already using it (would be kind of like trying to plug a hard drive into two computers at once). Other phones with a real SD card or separate /sdcard storage (Nexus S) disconnect this from the phone so another device can mount it.
Hi,
MTP is starting to be a real pain for me. For all its benefits, its not as good as Mass Storage.
If I'd rather use my laptop to Edit MP3 Tags (as its much faster than using a touch screen), it seems I have to transfer all my music (copy) from my GNEX over to my computer, edit the tags, then copy them back over.
That to me is a real pain.
I could view the MP3's via my PC with the GNex connected, but if I try and do anything to them, I notice that its read only.
Anyway around that other than what I'm already doing? I really don't like offloading the mp3's just to edit and put them back again.
You might try mounting the internal phone storage via WebDAV. I use an app called "WebDAV server" to serve out my phone's storage via WebDAV and then use a program called "NetDrive" to mount the storage on my PC. The storage looks and acts like a Windows drive on the PC, though it is a bit slower than a mass storage mount would be. It gets around the limitations of the default media mounting.
would like to use nexus 7 2013 with my Line 6 Amplifi Amp Remote App, (larger screen easier to navigate etc.) without rooting
unfortunately the remote app for the amp does not see the music files i wish to access as part of my "Music Library" because they are on an otg usb stick. (it only sees the internal storage)
i have tried several different apps to bridge this but i'm either doing it wrong or it may just not be possible
you can symlink the folder you need to access to a link on the internal storage.
I have connected a usb-c enclosure with NVMe to my new P6Pro. Everything looks okay until I try to transfer certain files (and/or transfer a bunch of data). One that I keep having issues with is a TitaniumBackup file, about 200-300mb.
All my other Pixels (3XL, 4XL) transfer the file just fine. Transferring between a PC & the P6P works fine (both ADB & file share push from the PC).
At first I suspected that phone doesn't provide enough power to the OTG, but it's happening very consistently with certain files, which should take ~1sec to transfer at USB3 speeds...
Wondering if it's my device or a more common issue.
Interesting. I don't have any external NVMe adapters. I do use an "old" USB-C hub that includes a Micro SD slot, and I regularly copy my music from that to my P6P's internal storage, but none of these files are likely that big (it's funny calling anything less than many GB big, but I guess all music, even my preferred format FLAC files, are still reasonably sized). I transfer a total of ~400 GB of music. I don't have the same issue but very different enough circumstances, so I'm not revealing any very helpful information.
Seems like this has to do with .nomedia file handling
0-byte .nomedia is apparently invalid now -- and if encountered, something bad (like this) happens
Fry-kun said:
Seems like this has to do with .nomedia file handling
0-byte .nomedia is apparently invalid now -- and if encountered, something bad (like this) happens
Click to expand...
Click to collapse
Hmmm, I use .nomedia files extensively in all of my music's deep folder's structure, but I create them with an app that does it all at once and haven't copied those files to the source locations on my computer hard drive or the duplicate copy on Micro SD card. I'll set a reminder to run some experiments when I'm in front of the computer tomorrow and report back.
Of course, it could be specific to NVMe drives, or particular types/technology of NVMe drives, and I won't be able to confirm either of those through an adapter, anyway.
Okay, did some digging. First, back when I used to manually create .nomedia files (or use an old app to do so), they were of course zero-byte (empty) files. This app Nomedia, although slow, does work for me, and apparently creates the files with various small byte-lengths - the contents of which are merely the text of the path it put them in.
I also learned that they only seem to be necessary at a root level to completely exclude everything underneath it. I didn't remember that was the case. So I only have six .nomedia files in my 400GB+ of music files folder structure, and I'll just keep in mind never to create my own, or if I do, to always have something in the file so it's zero-byte length. I can only assume the developer for that app knew that zero-byte .nomedia files could cause some problems.