Related
I've looked at all relevant threads in the Xoom forums and on the web but still can't find the solution to my problem so I'm hoping one of you guys can help me.
I have:
1.Motorola Xoom US WiFi(But bought in Singapore, MZ604)
2.Working DIYed USB Host Cable(I plugged my DHD into the microUSB end and a normal USB-USB cable at the other then plugged into my computer
3.Sandisk ThumbDrive, Kingston ThumbDrive, FAT32
4.Microsoft USB Mouse
I'm running the awesomely win Tiamat ROM(thanks) as well as the kernel which I was told worked from the this thread(Tiamat 1.4.2), I have the USB Watcher OTG app too. But not only can I not mount or use any USB device, the devices do not light up. there appears to be no power flowing to the devices.
A little help please
Thanks for reading this post
BTW After flashing the 1.4.4 Kernel my WiFi refused to work so I downgraded.
When you searched other threads, you missed a very relevant one. In this section, exactly 12 posts below yours, is a similar thread with this post:
"I'm not sure if its a power problem or the unusual way the built-in Sandisk software mounts the drive (it mounts as a "cd drive" in Windows); but Sandisks are problematic.
If you can, please try another thumb drive just to be sure. Preferably, one with no lights (to minimize power requirements) and not a Sandisk or Kingston, which both use proprietary built-in software upon insertion into PC usb ports."
Secondly, you should not have flashed another Tiamat kernel. 1.4.4 is included in the Tiamat 1.0 ROM. BRD stated that in the OP of that thread. You may want to reflash the Tiamat 1.0 ROM again. Then you will not need to flash any other kernel.
I'm sorry if I was not clear, but my sandisk or Kingston appears to be of the type which does not have the annoying U3 thing(the thing mentioned that causes the thumbdrive to mount as a cd drive.) I reflashed the 1.4.4 kernel just to be sure it's there(oh and I did reflash the ROM), and got a error what prevented WiFi from working. And none of the USB devices I tried(including the kingston with no lights) worked. I think there's no power, so I'm looking for help here. Anyway thanks for reading my long post, sorry if I'm annoying.
tlkh said:
I'm sorry if I was not clear, but my sandisk or Kingston appears to be of the type which does not have the annoying U3 thing(the thing mentioned that causes the thumbdrive to mount as a cd drive.) I reflashed the 1.4.4 kernel just to be sure it's there(oh and I did reflash the ROM), and got a error what prevented WiFi from working. And none of the USB devices I tried(including the kingston with no lights) worked. I think there's no power, so I'm looking for help here. Anyway thanks for reading my long post, sorry if I'm annoying.
Click to expand...
Click to collapse
If your wifi is not working, I would recommend reflashing the ROM. USB drive connection has been problematic. See this thread > http://forum.xda-developers.com/showthread.php?t=1068999
I usually connect devices through a hub on a stock unrooted xoom wifi running 3.1. Without the hub I've found usb mice work without external power (provided by the hub) but flash drives do not. For troubleshooting maybe try connecting through an externally powered hub to see if you don't meet the power requirements.
Honestly though, since the flash drive's light doesn't even come on it sounds like the xoom is not recognizing that it should be a host which hints to me that there's something wrong with the cable. The way you tested it doesn't sound like it tests the OTG part of the cable (the 5th pin) because the PC will be the host either way. I just bought Motorola's Camera Connection Kit off of amazon. I figured for long term use it's better than a home made one anyway. I'd post the link but I don't have enough posts yet...just search Motorola Camera Connection Kit on amazon if you're interested.
Hi all, I've been waiting and searching around seeing if I was able to find any kind of fix or something for some time now but it's beginning to get to me far too much.
My problem is when I had the HTC Aria I used to have the audio stored on my phone and plug it into my car's USB connection and the headunit would search the device and find all audio to play through the headunit which I was then able to use my controls on the steering wheel. After some time I bought the Samsung Galaxy S2 (l9100) and to my excitement received the whopping 16GB internal storage as a bonus, so I filled that. And heres where my problem comes in, I cant seem to make my headunit search the internal storage and play all that music, It will only search the SD card (external).
Now from reading all over the internet I've been led to believe by any posts that relate somewhat to this that it wont be possible for this to work, what frustrates me though is that it is possible. I've rooted and flashed various custom ROM's to my device (VillianROM first, Cyanogenmod Nightlies second and now MIUI yesterday). I have successfully had the headunit read my internal (newer and more songs) upon connection twice that I can recall now, I think the first time was after first connection to the car after the cyanogenmod flash and today when I first connected it again. Which led me to believe that it was working and then was just applying a new theme on my phone while hanging at a friends then was taking another friend home and plugged it in and back to only reading from my SD card (external - old crap music) and can't figure out why it has worked twice if it is not possible.
The reason why I am determined to figure this out is due to 16 GB internal storage and only 1 GB external storage and I wish to use my phone to its full potential.
While I'm at it, I guess I should mention my other problem which adds to my determination to get the USB connection working with my car. The USB connection is a much clearer & louder playback (Higher quality) then the AUX (current alternative) and to be safer while driving by using my steering controls.
But since flashing to Cyanogenmod and MIUI (cannot recall whether I had this problem on VillainROM) I've noticed the volume in headset mode (when I have something plugged into the headphone jack - ie, AUX, etc) and I begin turning up the volume from quietest to loudest it get notably louder each press until halfway or a press before halfway and then does not become any louder, which I also think may be making the audio less clear and loud when connected via AUX to my car.
Thanks in advance to anyone whom contributes.
I am usually stubborn enough to sort problems out myself, but for the first time I am asking for help on a community forum.
Anyone have any idea what I'm talking about?
If you need to know anything else don't hesitate to ask.
CM7 volume is a known issues or least it was last time I checked.
Try turning on/off usb debugging is my best guess.
Done that, today at some point it randomly read my internal storage and right now I'm constantly reconnecting it with no success.
The frustration continues as it is obviously possible but appears to have a mind of its own.
With my little knowledge when it comes to android and their platform, is it possible it could be there mount priority of the storage or the internal having something stored on it such as an app that could be in use by the phone which could be preventing the drive from being read?
what the hell... I have the exact OPPOSITE problem.
With my headunit its been only mounting the internal storage, but most of my music I put them in the external since I got a 32gb card!
Could it be mounting the smaller sized storage first? =P
-EDIT-
Actually it should be easier to do it the way you want it to (i.e mount internal only)
just unmount the sd card via the android settings -> storage -> unmount
and once it is unmounted, connect the usb to the car.
The catch is of course if you wanna use the external again you have to manually mount it via the settings.
more info but no real help
I have seen a very similar problem and I feel like I can reproduce it.
I've got a 2010 Hyundai Tucson - it has a USB/aux port in the dash console and can accept anything that can be mounted as flash media, flash drives, ipods, etc can all play back music using the Nav display to browse and playback files from the device.
The stereo plays back music perfectly through both my wife's old and new phones. An original MyTouch 3g and a MyTouch 4g. She's had no problem mounting and reading the files from her internal storage. She can playback music on her phone, the car even remembers her place and resumes where she stopped a song.
I, on the other hand, cannot easily get the car to playback files from my older or newer phone. I started with the original android, the HTC Dream/TMobile G1 then later upgraded to a Samsung Galaxy S 3g/TMob Vibrant. What's the difference? I've run modded android OS on my phones and my wife has not. I had been running CM5 and later CM6 on the G1/Dream until I retired it. Lately I've been using a MIUI mod, Lithium 360, on the Vibrant.
When I plug in to the USB on the car, the phone gives me the mount prompt and the car begins searching for files. Eventually both fail to make any progress.
I've tried many fixes including turning on/off USB debugging, I've tried wiping Dalvik cache, Wiping regular cache, I believe I even did a factory reset, flash zip, full re-install on a road trip just to see if I could get the car to read my files. What I did discover is that the problem is simply not hardware related. I could boot to recovery and use clockwork to mount USB storage. Files were seen instantly and played back fine. However, this doesn't do me any good as I can't really use the device for anything else (safety first ) and not to mention that there's no way I want to run the phone with the screen on for hours. I know there are simple workarounds here. But carrying an aux/patch cable is an extra hassle, and since my phone can hold enough data for my average means, I often don't remember to bring a flash drive with me everywhere. Besides, the USB cable in the dash does double duty, charging while giving access to files.
To be fair, I've only used CM based mods (according to wikipedia, MIUI is somewhat based on Cyanogen) on my phone and have not tried out any other android software. I don't know if that's a connection or not, but it's the only lead I have right now. There's got to be something different about the USB settings in the OS itself compared to stock Android. Is there an apk file one could flash and test somehow?
---------- Post added at 04:56 AM ---------- Previous post was at 04:49 AM ----------
http://forum.xda-developers.com/showthread.php?t=617333&highlight=car+stereo
This thread is above seems to be describing the same problem. This however appears to be an aftermarket stereo.
[Q] After mounting it *immediately* dismounts
Connecting to a Samsung TV (USB debugging ON and clicked on USB Storage until it turns from green to orange) and then browsing USB (Menu => USB device) it mounts the USB ("Android 11GB" which is presumably the internal SD) and then dismounts within a second and restarts initializing. An ordinary USB stick (single file system) does mount.
Is this because the Galaxy S2 mounts two file systems at a time and the TV cannot handle this. Is there an app which only mounts ONE filesystem on the Galaxy ?
My Sensation is could not be recognized by a computer, even in hboot, i tried a few computers, none of them worked. But then when I try plugging it through a usb hub, it magically worked! albeit it works quite slow as it complains about not being USB 2.0, etc. Now this is really work, the phone can only be recognized when plugged via a hub, anyone knows what might be causing this?
PS, I tried another cable, both worked on my DHD perfectly but same problem with Sensation.
EDIT: I tried a usb 2.0 hub and it doesnt work, i think my phone's usb 2.0 is messed up.
Anyone knows of a firmware i should try flashing that would probably fix this?
it seems like even it gets connected to usb 1.0 hub, large file trasnfer(eg: a new rom) would still still halt halfway.
Tried a third cable and I am now starting to wonder if it is hardware related, i would off order a usb connector module off ebay, or send it to get fixed, but i wanna make sure it isnt software related...
btw, anyone knows how much technical skill would i need to replace the module? if it doesnt require soldering i am pretty confident to do it, i mean i had replaced the earpiece on my dhd before, now that was easy!
You have to pick the option to connect sdcard. If sense then drop down menu and pick disk drive if cm7 then turn on USB
Try to install HTC sync as well
Having a problem getting USB tethering to work on my computer running Windows 7 64-bit. My htc Droid Incredible (Verizon) has Linaro Optimized CM9 (which, by the way, is running very nicely so far). I connected it to the computer and enable tethering on the phone, and heard some Plug and Play connection noises, but when it went to load drivers it said that the RNDIS driver could not be found.
Checking Device Manager, I don't see any new network adapter that references the phone. I do see an Android ADB Interface listed under Android Phones, but there is a yellow exclamation on RNDIS, of course.
Have tried the following, based on suggestions I got on some other forums:
1) Loaded the latest version of HTC Sync to get drivers installed...no go, same issue listed in Device Manager. If I actually launch HTC Sync, it says that no phone is connected.
2) Tried an HBOOT driver from the unrevoked root wiki ... still nothing.
3) Tried installing--in Device Manager--some (but not all) of the different Microsoft RNDIS drivers that are available, but the install does not succeed. Usually says that it could not start the device, or something like that.
I'm really here, though, because someone just stated the following:
"The ROM may be your problem... since cm9 is not officially supported on the incredible...the ROM is a port from another phone, so that could be the cause of your problem... I'd make a nandroid of your current setup and try wired tethering with the official cm7 ROM."
Sounds plausible, I guess, but I would have thought that there would have been something here about this (if there was, I couldn't find it). I also have the nagging suspicion that the issue is on the computer and not the phone. So before I go backing up and changing ROMs, can anyone please confirm or refute as to whether this particular ROM would "break" USB tethering as described above?
Thanks in advance!
Mike
P.S. Wireless hotspot tethering works just fine, by the way. But I would like to be able to tether via USB cable as well.
P.P.S. Tried to post this in the pertinent thread started by mamarley, but I think I'm prohibited from doing so because I am brand new to the forum.
Kang-A-rom
What is it?
a kang of purity rom with a few added functions. It is based on the hard work of others and no credit to me is implied, other than merging and building. All sources are available at:
https://github.com/lostdeveloper
Features:
* Full dac support, on boot, hot plug, volume control
*OC of CPU and GPU
*OTG while charging, fastcharging
*support for most dvbt tuners including the newer r820t tuners.
*automatic mounting of ntfs and exfat storage drives with read and write support
*easycap support, plug n play (requires carcam app)
*firm sleep
*wakelock blocker
*usb/bluetooth tethering (unconfirmed)
*more, and more coming....
Kangarom V2 03/09/2014
Changes:
*plug and play any easycap device (needs carcam app, and one model also needs firmware)
*added support in ramdisk and frameworks/base for USB tethering and bluetooth tethering. I have no way to test this, it needs testing, and I need logcats with any issues. I am completely unsure If I have everything here.
*included dashclock and simple explorer, both open source and useful, while not consuming a lot of space
*Wakelock Blocker, selectively prevent certain wakelocks to save battery
*all purity rom updates from DariosF
Download
http://d-h.st/qOT
________________________________________________________________________________________
Older Changelogs and
Downloads:
Kangarom v1, initial release
http://d-h.st/QXB
_____________________________________________________________________________
other info:
-some models of easycap may also require a firmware to function properly. These firmwares must be obtained by the end user and cannot be included by me for legal reasons. However, they can be downloaded freely from proper sources.
-use of dvbt tuners requires a script to load the needed modules and set up for chrulri's droidtv app.
-firm sleep, and dac on boot require crue's powermanager app to set options for firm sleep, fixed install mode, and fastcharge in hostmode
**The latest version of crue's app may be found here:
http://forum.xda-developers.com/showpost.php?p=50265682&postcount=411
Credit is his, so hit his thanks button.
More INFo about this can be found in my kernel thread, as well as links to the source code used for this:
http://forum.xda-developers.com/showthread.php?t=2558717
Im working on a tilapia build.....not yet.
feel free to ask any questions... Im not too concerned about hardcore dev stuff only. Anything that helps others find answers works for me.
reserved
one more.
would be cool if you could post more information for the dvbt driver
i used mine on usb rom as radio with wavesink and this driver: https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro&hl=de
do i need the driver app now or only wavesink? or wavesink and a script?
EDIT:
and should i flash your kernel over the rom or is includet?
Awesome. Going to try this out right away. Thanks.
michiil said:
would be cool if you could post more information for the dvbt driver
i used mine on usb rom as radio with wavesink and this driver: https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro&hl=de
do i need the driver app now or only wavesink? or wavesink and a script?
EDIT:
and should i flash your kernel over the rom or is includet?
Click to expand...
Click to collapse
Yea....I wanted to get the build up for you all, but I need to set up the OP properly just really busy. Kernel is included already...... dvbt will work as it use to with sdrtouch and other radio apps that use the userpace driver. To watch tv youll need to use a script to insmod the right modules....again ill link to the exact post when I have time, just search my kernel thread for r820t you will find it.
While these modules are loaded, your radio app wont work....it depends on that userspace driver and it wont have a device to "drive" because it is already loaded at the kernel level. So, the solution is a "load" script for kernel modules, then watch tv, then, an "unload" script...... and now your radio app will work again.
I will seriously fill those first three posts will all the needed info, but Im swamped right now with work. All the info is there in the kernel thread for now just need to search.....sorry.
Flashed this and worked right out of the bag, no need for external OTG apps. Ran PAGAPPS mini modular and is perfect for my needs. This came just in time as I'm getting my DAC in the mail tomorrow and plan on putting this in the dash of my car very soon thereafter. Thanks for all your hard work!
The only thing I think would be awesome is if you could incorporate volume buttons on the nav bar. I've never used Timur's rom but saw some videos and saw he had those. If not it'll be easy enough to get by. Thanks again!
sreister said:
Flashed this and worked right out of the bag, no need for external OTG apps. Ran PAGAPPS mini modular and is perfect for my needs. This came just in time as I'm getting my DAC in the mail tomorrow and plan on putting this in the dash of my car very soon thereafter. Thanks for all your hard work!
The only thing I think would be awesome is if you could incorporate volume buttons on the nav bar. I've never used Timur's rom but saw some videos and saw he had those. If not it'll be easy enough to get by. Thanks again!
Click to expand...
Click to collapse
Yes, its kindve on the list......sort of. The new kitkat framework only supports five total buttons on the navbar. Purity allows you to add two more already, but due to framework limitations I think it will be difficult to do this in a stable way. I was browsing around and i noticed that carbon ROM has a more involved navbar framework where you can set the navbar to launch volume control via "slim shortcuts." I got excited and thought it just needed to be cherry picked but....... I downloaded carbon ROM to try it and when i set it up the systemui crashed and repeatedly crashed until I rebooted. Once rebooted it once again crashed, I had to re flash the ROM and the same thing happened, so no go. This behavior is what I read should be expected if you try anything other than a menu button or a search button, or keyboard cursors on the kitkat navbar. In other words, any other button type would need to be fully implemented into the framework, no shortcuts. Im still researching this.....as time permits
The more likely scenario involves the quick launch shortcuts. With this ROM you can set up the home button for three on screen shortcuts via long-pressing the home button. If you download a volume control app, not a widget, an app, then you could use this quick launch method to access it. Or, you can already set it to open up settings>sound with the activity picker. I use "slider widget" for now.....simple desktop widget for volume control.
Super super suuuppperrrr silly question, but this is 4.4.2 right?
ZenInsight said:
Super super suuuppperrrr silly question, but this is 4.4.2 right?
Click to expand...
Click to collapse
Absolute latest from Google, yes.
This works pretty good on my in dash nexus 7. Couple of issues though... I use Bluetooth tethering from my phone, the tablet will connect but I have no internet connection. Also, I use an external microphone for voice commands, but it doesn't work on this ROM. I normally use AOKP ROM with Timur's kernel, this disables the internal mic and allows me to hook my external mic directly to the inputs of my Behringer UCA202 DAC. Also, the easycap issue that you've already mentioned in your kernel thread. Good work so far!
Sent from my SGH-I747 using xda app-developers app
And it goes in as the daily driver. Thanks for your efforts.
Sent from my SM-N900T using Tapatalk
gregthomas129 said:
This works pretty good on my in dash nexus 7. Couple of issues though... I use Bluetooth tethering from my phone, the tablet will connect but I have no internet connection. Also, I use an external microphone for voice commands, but it doesn't work on this ROM. I normally use AOKP ROM with Timur's kernel, this disables the internal mic and allows me to hook my external mic directly to the inputs of my Behringer UCA202 DAC. Also, the easycap issue that you've already mentioned in your kernel thread. Good work so far!
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did not know about the external mic in usbrom.... Im not sure how easy it will be to figure out, but usb tethering and bluetooth tethering I can kang from cm11....
Ive got a fix for easycap devices as well..... if tilapia build tests well then ill try the tethering thing next.
redeyedjedi said:
I did not know about the external mic in usbrom.... Im not sure how easy it will be to figure out, but usb tethering and bluetooth tethering I can kang from cm11....
Ive got a fix for easycap devices as well..... if tilapia build tests well then ill try the tethering thing next.
Click to expand...
Click to collapse
Its actually a combination of Timur's kernel and AOKP ROM, not USBrom. So I guess the kernel is what makes it work because if I run plain AOKP and the kernel that comes with it, then it operates the same as your ROM does... internal mic works, DAC inputs do not. I install AOKP and then Timur's kernel over top of it. Not really sure if it was intended that way but its the only way I've been able to get the DAC inputs to work. I'm more than happy to do any testing you need... I'd love to see an in car useable 4.4 rom as I'm sure a lot of the other "android in car" crowd would too!
Sent from my SGH-I747 using xda app-developers app
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Kuchar09 said:
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I noticed this too. I installed Stickmount and it seemed to work OK after that.
Sent from my SGH-I747 using xda app-developers app
Kuchar09 said:
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hmmmm..…...does it remount for you after deep sleep?? Or do you have to replug after that too?
I guess I'll add this to the list. I'll go test this out. I think we could use the jellybean vold if it mounts on boot.
redeyedjedi said:
Hmmmm..…...does it remount for you after deep sleep?? Or do you have to replug after that too?
I guess I'll add this to the list. I'll go test this out. I think we could use the jellybean vold if it mounts on boot.
Click to expand...
Click to collapse
Haven't tried deep sleep but I just tried booting it up and it didn't show so I unplugged power for my y-charge cable let the screen turn off then reconnect power and the the flash drive showed up in the file system. So this isn't a huge issue just looks like a little something might be missing.
Sent from my Galaxy Nexus using xda app-developers app
does this kernel extend otg+charge functionality to properly sense charging after boot (exactly as plugging in a wall charger)?
I've tried several kernels and they all have the same behavior in that they do not show a charging battery, (only in the pull down notification). this makes Tasker unable to know that power is actually plugged in.
issue is described here in relation to USB Accessory Charger
http://2dindroid.wordpress.com/2013/09/01/more-notes-on-usb-otg-charging-nexus-7-2013/
http://en.wikipedia.org/wiki/USB_OTG#OTG_micro_plugs
EDIT: just realized i was linked here from the Nexus 2013 forum.. ignore the question.
This is not directly rom related but since I assume most people here are doing a fixed install I will ask here.
So during the average commute I am running waze, torque, and Spotify.
I can't seem to catch my tablet up on the charging. During the drive it just slowly goes down while (maybe 1% over a hour). I am using a startech powered USB hub with a powered otg cable going to the tablet. The power side of the otg is plugged into the hub which should provide ample power to charge the nexus.
Is it possible for the nexus to draw more than it is capable of charging? Should I be focusing on my charging selection? Anyone else having a similar issue?
Can anyone tell me an accurate way to measure the draw being used by the tablet and the charging current?
My next option is a hardwired 3amp charger with a toggle switch that will either route the power to a source that is only on when the car is running and the other side of the switch will route it directly to a lead I have coming from the battery (attempt to get ahead while I am grocery shopping or times when I am only out of the car for an hour or so.)
Sent from my SM-N900T using Tapatalk