Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with the 4th pin going to ground in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
MrStabby said:
Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with a 5th pin going high in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
Click to expand...
Click to collapse
I have this issue as well and have been trying to figure it out. Currently have something close for aosp roms, but going to take more time to figure out for sense. I have been looking into it.
Wow, I thought it was just me/my phone.
github said:
Wow, I thought it was just me/my phone.
Click to expand...
Click to collapse
nope we should start our own club. Busted ass usbport club. I looked into swaping the port out and soldering on a new one. But after I looked at this little tiny piece of hardware, I though a software edit will be easier. And it is you need some intense tools to pull off a good swap. its sooooo small.
lithid-cm said:
I have this issue as well and have been trying to figure it out. Currently have something close for aosp roms, but going to take more time to figure out for sense. I have been looking into it.
Click to expand...
Click to collapse
Thanks, I figured it's a common problem but it would be nice to find a good solution.
I haven't seen too much of a connection with particular roms causing the issue. When it was originally a big problem a few months back (before it stopped happening for me), it would act the same way on every rom I stuck on it.
However, I just switched from deck's aosp rom to Synergy not long before this started happening again, and the sense roms definitely make it much more of an apparent problem than the AOSP roms would.
Physically to stop the problem, I know it's related to the MicroUSB port and I may try disassembling it if it gets bad enough.
From another post on it: "It's pin 4, not 5 , 5 is ground in the usb cable, when pin 4 is grounded it puts the unit in dock mode."
I'd post a link to the pinout, but the system makes me too newb to post pin outs. (Just google kineteka microusb b)
The same thing happened to my phone yesterday and it is pissing me off. Will it eventually go away over time or is it a permanent issue. Meaning when it dries off will everything be ok. I'm thinking about taking it in since I have insurance and see if they will either fix it or swap it out. I'm going to wait a couple of days to make sure there is no moisture in there.
There is an app called NoDock that you can download to fix this. In my experience, it does not work with MikG (which is probably a Sense 2.1 compatibiltiy issue). I am running Deck now too, and so far no issue with the AOSP ROM. If there is an issue, I read on the NoDock market page that CM based ROMs have an option to disable, and thus NoDock is not needed in this case.
Hmm. I'd think an app could be written that would catch the intent and do nothing, as well as manually adjust car dock volume via the volume controls. Maybe. But I don't think any kernel-level edits are needed. Maybe a decent dev can write something like that for you (I couldn't). [Edit: looks like NoDock might be that app] Another thought that might be stupid: have you taken a can of compressed air to your USB port?
Also, just a friendly reminder, there isn't any development work posted here so instead of the development subforum, this really belongs in General, or maybe Q&A. As a general rule, new threads in this section are only for sharing work you've done. Not to pretend I'm a mod or anything, just wanted to warn you so you don't get flamed to death next time.
In sense roms might be able to check AndroidManifests for either
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_DOCK
or
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_MODE
Then remove the intent from the application, so that nothing would happen.
lithid-cm said:
In sense roms might be able to check AndroidManifests for either
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_DOCK
or
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_MODE
Then remove the intent from the application, so that nothing would happen.
Click to expand...
Click to collapse
I was definitely looking into this within the android.policy.jar but my developer knowledge is minimal compared to your expertise. I'm really hoping to not have to download any apps and I'm reluctant to go get an insurance claim until the new OTA has been rooted successfully. Anybody makes any move forward on this I would be glad to donate. This started happening to me when I was working out with my phone in an armband and some sweat most likely got into the charger port causing a short (my theory on what happened). If it is still going on by the time the OTA gets rooted, I'm going to go swap it out at the Sprint store.
mjhuffer said:
I was definitely looking into this within the android.policy.jar but my developer knowledge is minimal compared to your expertise. I'm really hoping to not have to download any apps and I'm reluctant to go get an insurance claim until the new OTA has been rooted successfully. Anybody makes any move forward on this I would be glad to donate. This started happening to me when I was working out with my phone in an armband and some sweat most likely got into the charger port causing a short (my theory on what happened). If it is still going on by the time the OTA gets rooted, I'm going to go swap it out at the Sprint store.
Click to expand...
Click to collapse
I am actually looking to buy a rooted one on ebay. Then use this one for deving. I really like the evo no reason to let it go yet.
lithid-cm said:
I am actually looking to buy a rooted one on ebay. Then use this one for deving. I really like the evo no reason to let it go yet.
Click to expand...
Click to collapse
I thought it was illegal to sell rooted phones period. Or is it only illegal to make extra profit just based on the fact that it is rooted. That isn't to say that someone will do it anyways. My brother, who is phone illiterate, just got a nexus s and I really like it. I heard that the GSM version will be the first phone to get ICS (ice cream sandwich) so that means the CDMA one will be next. I'm perfectly happy with my EVO except when dumb stuff like this happens. I hate myself for asking but you got any progress on the rooting of 4.24 and the newest Hboot. Has the source code for the new Hboot been released?
I had a similar problem however it was caused by me putting my phone in my car dock
I had to freeze/uninstall both car panel and dock mode for it to finally stop giving me a notification and blinking the screen on and off when I hit bumps
Soldering USB port
lithid-cm said:
nope we should start our own club. Busted ass usbport club. I looked into swaping the port out and soldering on a new one. But after I looked at this little tiny piece of hardware, I though a software edit will be easier. And it is you need some intense tools to pull off a good swap. its sooooo small.
Click to expand...
Click to collapse
Had the USB issue on mine too.
Usb port is anchored down to circuit board in 4 places, those solder joints get
loose and the trouble begins.
I used a regular soldering iron to heat up the solder and bring the port back against the circuit board tight, no more car-mode.
Ed
chile62 said:
Had the USB issue on mine too.
Usb port is anchored down to circuit board in 4 places, those solder joints get
loose and the trouble begins.
I used a regular soldering iron to heat up the solder and bring the port back against the circuit board tight, no more car-mode.
Ed
Click to expand...
Click to collapse
I appreciate the response and im looking into it myself but what exactly do those points have to do with the electronic conductivity of the port? Do they have something to do with the ground.
odd, i had this same problem, what fixed mine was flashing a new different nv, it stopped it almost immediately
MrStabby said:
Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with the 4th pin going to ground in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
Click to expand...
Click to collapse
loose usb port
mjhuffer said:
I appreciate the response and im looking into it myself but what exactly do those points have to do with the electronic conductivity of the port? Do they have something to do with the ground.
Click to expand...
Click to collapse
The 4 points only hold the usb plug on to the board, on the backside of the plug, is where the actual connections are being made. They are almost like spring loaded connections.
When the soldered points get weak, the usb gets pulled pulled away from the mother board and some of the pins will not make contact.
Ed
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect config_usb_accessory_detect and config_dock_accessory_detect support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
This is crazy mine an my girls phones are doing this we bought a charger off of eBay an that's when it started I tried titanium pro an froze car mode seems to work but just a bandaid
Sent from my PC36100 using XDA Premium App
sbradymobile said:
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect dock support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
Click to expand...
Click to collapse
Thanks man I'm going to wait for some dev to jump on this. Hopefully someone can create a .zip so you can flash it over any kernel. I would really just like the stock kernel with this option added in.
Heya guys
Im having a strange problem with my only 1 week old Transformer TF101. I was told, this would be the place to ask, so I really hope someone can assist me
I bought a Transformer as a HDMI-out multimedia solution for my TV and the first week everything worked like a charm. But suddenly, for no reason, it wont show on my LG 50" Plasma. I then tried it on my older Samsung in the bedroom and to my surprise there was no problems connecting the tablet, it showed right away.
I then figured, cable? So I took the cable from the bedroom, but with no succes. HDMI-in on TV then, i thought? But nope. Everything else shows connecting it with the TV's HDMI. PC etc.
I am currently sitting with tablet I cannot use for the purpose I bought it for. What to do? Any help, is very much appreciated!
Ps. my plasma tells that something is connected to the HDMi and even tries to connect, but the tablet does nothing and then the TV says "no signal".
There is no way to change any setting for hdmi on the tf, so I guess yor tv is the problem. Maybe you changed a setting? I only had a problem wit over- and underscan. Try looking into the tv menu... thats my guess
Sent from my Transformer TF101 using Tapatalk
towlie288 said:
There is no way to change any setting for hdmi on the tf, so I guess yor tv is the problem. Maybe you changed a setting? I only had a problem wit over- and underscan. Try looking into the tv menu... thats my guess
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I didnt change anything in the TV's menu and ive looked for settings that could have an influence, but non found. I had the tablet unplugged and when I plugged it to the HDMI the next day, it didnt work, after working 100% for almost a week.
Try a custom kernel. Last year the tf had trouble displaying on some TVs like Sony. About September or so an update came out that solved the issue. I'm guessing the stock kernel still has trouble with LG TVs.
goodintentions said:
Try a custom kernel. Last year the tf had trouble displaying on some TVs like Sony. About September or so an update came out that solved the issue. I'm guessing the stock kernel still has trouble with LG TVs.
Click to expand...
Click to collapse
But if it worked? And to be honest, I wouldn't want to have to flash a custom kernel just for simple HDMI out!
And that it works on the other TVs is also strange. I have a LG Monitor and have no problems...
You could just try reseting it to ensure that it's not something in the tablet. Or reset the TV?
So.... something strange has happened.
After not having worked for 2 days, it suddenly worked again. The tablet detects the connected HDMI cabel and the picture shows on the plasma instantly. Im like what the ****? I havent changed anything on neither the tablet or the TV. Dunno if I should be happy or worried, since id like for it to work, when I actually have to use it
I heard from someone that its better to use the HDMI/DVI, than the regular HDMI on the TV, im currently using. Can anyone confirm this?
I am using clean ROM 4.0 DE and when I try to use my MHL adapter I lose signal on my phone everytime. Not only do I lose signal but when I try to just display a movie that I have on my phone, it freezes and wont play. I checked to see if the movie paused but it didn't. I can do everything else (as long as a data connection isn't required). I have not tried via wifi but that really doesn't matter much cause I don't have wifi where I am lookign to use MHL. Is this a ROM issue or a known issue with the HOX and MHL. I had the same issue on r113 or the Nocturnal ROM as well.
Is it an OEM HTC MHL adaptor? Or a third party brand?
Sent from my GT-N700 using Tapatalk 2
Third party from amazon
Sent from my Nocturnal HOX
I get a really grainy, probably only 850x480 picture on mine. Same with my Evo 3D. Both are running ICS. The 3D was full 720/1080p out before updating.
Sorry to hear that. I just got this yesterday. And it really works! Sadly landscape mode doesn't work properly on cyanogenmod 9 so I went back to ARHD and have the full screen landscape setup. Good thing about this adapter is that It already has an HDMI cable builtin you can even pair it with this dock(btw I bought 2)..1 for work and 1 when at home.
JamesR913 said:
I am using clean ROM 4.0 DE and when I try to use my MHL adapter I lose signal on my phone everytime. Not only do I lose signal but when I try to just display a movie that I have on my phone, it freezes and wont play. I checked to see if the movie paused but it didn't. I can do everything else (as long as a data connection isn't required). I have not tried via wifi but that really doesn't matter much cause I don't have wifi where I am lookign to use MHL. Is this a ROM issue or a known issue with the HOX and MHL. I had the same issue on r113 or the Nocturnal ROM as well.
Click to expand...
Click to collapse
I'm using a 3rd party MHL adapter from MONOprice, about $10. I had this issue and realized it was due to the One X's screen timeout. I set power settings to display on always when charged, and it works fine. Try it.
Hi, so I've been ICS for a while now and I'm currently running Virtuous Infinity 1.35beta. A few days ago I stumbled upon my cable that I used to use when I was on Gingerbread for connecting the MT4GS to the tv. It's a 4 pole jack with a red, white and yellow on the other end. Ever since I came over to ICS, I haven't had much time to play with this, but when I wanted to watch a movie on the tv off my mt4gs, it did not work. The phone tells me something along the lines of "hdmi connected", but the screen on the tv just turns blue and does not show anything. The movie plays on the mt4gs without a problem. I'm posting this because all of the threads I found about similar issues are from 2011 or early 2012, i.e. long before we got the ICS.
Does anyone have any idea of how to get this to work properly? Or is reverting back to Gingerbread the only option of getting this to work?
I bought this phone to last me a while and I'd hate to lose a useful function like this, where you can always essentially have a movie player in your pocket.
Thank you for even the slightest input you can give me on this because I haven't been able to find anything on this issue on xda or google.
lubotron said:
Hi, so I've been ICS [...] A few days ago I stumbled upon my cable that I used to use when I was on Gingerbread for connecting the MT4GS to the tv. It's a 4 pole jack with a red, white and yellow on the other end. [...] The phone tells me something along the lines of "hdmi connected", but the screen on the tv just turns blue and does not show anything.
Click to expand...
Click to collapse
I saw the title to this thread in the forum list and it prompted me to find my cable. I'm going to have a few days coming up here where it will come in quite handy and I want to make sure the ROM I'm using is fully functional for my purposes. REALLY ticks me off how this phone seemed to be built only for Sense 3 Gingerbread. I think I'm going to quit supporting HTC over this BS.
So I finally find an ICS ROM that doesn't seem like it's crippled all to hell, and I saw this thread, and decided to try it. So far everything else I've needed seems to work, and I just went 12 hours with only 5% drop in battery (of course not touching the phone -- once I do it's like I lose a percent a minute) so it seems like a pretty decent ROM. But then I plug it into the tv, and just like you, I got "HDMI Connected" in the notebar, a blue screen on the tv (with black interleaved horizontal lines), and no other output. Also, there's no "TV Out" app or any kind of config that I can find.
I'm going to go hunting and if I catch anything I'll bring it back here...
http://forum.xda-developers.com/showthread.php?t=1484165
that's probably your best bet. just a warning, i'm pretty sure it drains battery quickly (which i guess kind of makes sense cuz of the name "brute force"). not sure if this is exactly what you're looking for, but it's a start!
anitgandhi said:
http://forum.xda-developers.com/showthread.php?t=1484165
that's probably your best bet. just a warning, i'm pretty sure it drains battery quickly (which i guess kind of makes sense cuz of the name "brute force"). not sure if this is exactly what you're looking for, but it's a start!
Click to expand...
Click to collapse
Anybody knows if tbalden released the source of this tvoutd binary? Would really love to work on this one if I could get hold of the source.
Riyal said:
Anybody knows if tbalden released the source of this tvoutd binary? Would really love to work on this one if I could get hold of the source.
Click to expand...
Click to collapse
I don't think he posted/released the source for the tv out app. Try sending him a PM. I'd be interested in helping you with this, if tv out via micro usb is even doable.
rumi409 said:
I don't think he posted/released the source for the tv out app. Try sending him a PM. I'd be interested in helping you with this, if tv out via micro usb is even doable.
Click to expand...
Click to collapse
Don't confuse tv-out (via 3.5mm 4-conductor phone plug) with MHL (via micro-USB connector/adapter) though...
...and I read in another xda thread that this phone may have the same
MHL chip that another phone had... Was it the sensation?
--
Sent from my Bulletproof HTC Swiss Army Doubleshot
All the guys who have examined it and worked hard on the subject have stated that it simply is not built in such a way as to do MHL. Blue IIRC was the guy who made the definitive statement.
Hastily spouted for your befuddlement
I tried dissecting the binary to extract as much information as I can have and I noticed that this daemon is hacking up the route of the hdmi to the headset passage and into the usb to the TV. I'm not really good into these technology as I am not even using HDMI lol! So unless there's a source code I can't continue development on this as I don't understand the process of this bruteforce hack.