My wife's car radio has an auxiliary input we use to listen to audio from various devices, it works great for turn by turn, music or whatever from our phones. I don't have such an option in my vehicle but i do have in dash cd and cassette. Today i grabbed a cheap 3.5mm to cassette adapter from an auto parts store to get similar functionality in my vehicle. Every thing works as expected, except the HTC music player (the one you access from the home tabs).
When I play music through the player i hear about 1 sec of audio and then my phone restarts!. This does not happen with headphones or in my wifes car when plugged into the auxiliary input. This does not happen using TCPMP, Windows media player, bing, or talking on the phone. It only occurs using the htc player.
Just curious what could be causing this?
Tmous HTC HD2
Cookie Energy ROM
Radio 2.10.50.26
its probably getting a power spike back up the cable which is tripping out the phone.
On a pc, you can quite often cause the whole thing to lock up by pulling out the speaker jack if you have powered speakers.
No suggestions for a fix tho, sorry.
samsamuel said:
its probably getting a power spike back up the cable which is tripping out the phone.
On a pc, you can quite often cause the whole thing to lock up by pulling out the speaker jack if you have powered speakers.
No suggestions for a fix tho, sorry.
Click to expand...
Click to collapse
thanks for responding and I agree, although I didn't have a problem plugging into my pc mic or input. But wouldn't it happen in other players/apps too? And would plugging in the phone then inserting the cassette or vice-versa make a difference? Not really a big deal, as i won't be using the setup often, just got me thinking...
heh, who knows the whys and wherefores of these types of bugs, , try plugging it all together with the phone off, then power on last, see if it makes a difference, , just for testing purposes, see what happens.
Phones like this can be more sensitive to that type of thing in general (and PC's too), especially with regards to audio jacks. My suggestion would be to try a better quality cassette adapter. I suspect too that even if the one you have now didn't cause this problem, the audio played through it would have a noticible hum or hiss in the background.
I ride a Kawasaki Ninja, and it's become increasingly difficult to be able to have one ear listening to music lately (using my Vibrant as my MP3 player).
The issue:
While riding at speeds greater than 15-20mph, the button on my wired headset is activated by the wind constantly (both the stock wired headset that came with it, and my new Skull Candy ones). This causes my music to "sputter" the whole time I'm moving. I thought maybe it was just the stock headset, so I went and got a really nice set....and...same problem. Apparently, it has to do with the wind blowing into that mic/button area, and activating the button. Both headests normally work just fine, but that wind is causing an issue when riding...
What I'm looking for:
I'm looking for a way to disable the headset pickup/hangup/play/pause button. At the very least, just the play/pause part of it, but I haven't found any solution yet.
My music randomly pauses for no reason... I think the button is just broken.
I too would like to disable the button.
Bump
Ideas? Anyone? Getting desperate...
Try a diffrent music player, also dig aroung the settings in the app
Sent from my SGH-T959 using Tapatalk
There's an app called poweramp and it has an option to disable the button (I think) the app can be found in the Vibrant themes n apps thread
Sent from my SGH-T959 using XDA App
meldedchaoz said:
Ideas? Anyone? Getting desperate...
Click to expand...
Click to collapse
Put duct tape over that part of the headset?
Use earphones with no button? Like the ipod ones?
Looking for an actual fix...
Reasoning:
1) Using a headset without a button:
I don't want to have to carry around 2 headsets (one for music, one for phone)2) Using a different app:
I want to be able to use things like Pandora Radio, which only really plays out of one player.3) Duct tape:
I could just as easily pour super-glue into the button cavity...oh, wait...no
I like the new verizon car dock but when I make or receive a voice call through my factory bluetooth system (Dodge Nitro with factory nav system) the call quality is horrible. If I toggle from bluetooth to speaker phone back to bluetooth the call quality is fixed. Anyone else experienced this?
Sent from my SCH-I500 using XDA App
Have you tried the car home app from the Vibrant? I personally like that one better than the Mesmerize one. I'm curious if it has the same Bluetooth issue, but I have no Bluetooth system in my Jeep to try it out myself.
Sent from my SCH-I500 using XDA App
No I just turn my bluetooth on and let it do its things thing while paired to my trucks sound system. When I refer the verizon car dock I mean the "mount" that holds and charges the phone. Just making sure we are talking about the same thing...
Thx
Sent from my SCH-I500 using XDA App
Oh, sorry, I misunderstood. I thought you were referring to the application. I don't know why the dock mount itself would have anything to do with your Bluetooth quality though. As far as I know, the dock only provides charging and audio output capabilities. Do you also have the issue when your phone isn't plugged into the car dock and linked with your MyGig system? If so, you might need to make a warranty claim and get a replacement phone.
Sent from my SCH-I500 using XDA App
This "only" happens when the phone is in the car dock when the charger is slid down and into the phone.
I stopped my local verizon store this afternoon and tried another dock and it did the same thing.
The service rep said when the phone is put into the dock a magnet in the dock makes the phone go into car dock mode and adjust the speaker volume for hands free and nothing can be done about it without changing to a different brand of dock. I tore my dock completely apart... They're is no magnet anywhere. I am stumped.
Sent from my SCH-I500 using XDA App
I just want to discuss this here. I have been running the 7.2 rc1 through latest nightly. Most everything works well and it is snappy. The biggest issue I have is with the car dock. This Rom doesn't correctly adjust to dock insertion and removal. Add to this Bluetooth phone audio and it becomes a bit of a pain, at least for me.
Issues:
1) Remove phone from dock after it has lost power and the battery still thinks it is connected and charging. This issue requires either a reboot or a reinsertion and removal from a car dock that has 5V USB power.
2) Audio does not return to 3.5mm plug after call. Put phone into dock. Play music or nav and the audio plays over the 3.5 mm plug. Receive a call when connected to bt, phone audio cones over BT. Hang up call and sound routes to phone speaker. - does not revert to dock audio. The workaround is to un-dock and re-dock and the audiop appears back on the car dock plug.
3) On call. Turn on car, BT connnects, phone audio routes to BT ( I think). place phone in car dock and you have to go to 'phone' then find 'in call' then turn on speaker then turn on bluetooth and audio appears over BT. THe confounding issue is placing the phone in the dock right after it connects to BT or before it has negotiated this connection.
Also I ran into a problem with receiving a notificaton while I was taking a movie with the camera. It stopped the movie.
I was posting these issues to the atrix dev team, but that issues list seems to have gone dormant. I recently posted it to the CM7 list and am now trying to get all my logs in order b/c I was running the latest nightly. These problems with setting the default audio exist with every CM7.2 since RC1. It seems that the issue is the logic with the dock insertion.
1) It 'should' send all audio out the car dock, except the phone audio, when it is plugged into the car dock.
2) It should stop playback of any other app during a call and resume after the hang up
3) Phone BT should not affect this and should be a separate deal. This is how the CM7 appears to work as well. (at least this is how the stock rom works). The phone should be either speaker, handset or BT depending on if BT is connected or not. If BT is connected, default is BT. The problem I have seen is confusion when the phone is in the dock. BT is lit on the 'in call' screen, but audio is on the speaker and needs to be cycled through to bring it back to the appropriate device.
Am I the only one noticing this? I think I may go back to nottachtrix until this gets resolved. I use the dock all the time and this is getting bothersome, especially if there is a rom that deals with this correctly. I like CM7, but need it to work correctly with the car dock audio and charging.
Sent from my MB860 using xda app-developers app
keithspg said:
I just want to discuss this here. I have been running the 7.2 rc1 through latest nightly. Most everything works well and it is snappy. The biggest issue I have is with the car dock. This Rom doesn't correctly adjust to dock insertion and removal. Add to this Bluetooth phone audio and it becomes a bit of a pain, at least for me.
Issues:
1) Remove phone from dock after it has lost power and the battery still thinks it is connected and charging. This issue requires either a reboot or a reinsertion and removal from a car dock that has 5V USB power.
2) Audio does not return to 3.5mm plug after call. Put phone into dock. Play music or nav and the audio plays over the 3.5 mm plug. Receive a call when connected to bt, phone audio cones over BT. Hang up call and sound routes to phone speaker. - does not revert to dock audio. The workaround is to un-dock and re-dock and the audiop appears back on the car dock plug.
3) On call. Turn on car, BT connnects, phone audio routes to BT ( I think). place phone in car dock and you have to go to 'phone' then find 'in call' then turn on speaker then turn on bluetooth and audio appears over BT. THe confounding issue is placing the phone in the dock right after it connects to BT or before it has negotiated this connection.
Also I ran into a problem with receiving a notificaton while I was taking a movie with the camera. It stopped the movie.
I was posting these issues to the atrix dev team, but that issues list seems to have gone dormant. I recently posted it to the CM7 list and am now trying to get all my logs in order b/c I was running the latest nightly. These problems with setting the default audio exist with every CM7.2 since RC1. It seems that the issue is the logic with the dock insertion.
1) It 'should' send all audio out the car dock, except the phone audio, when it is plugged into the car dock.
2) It should stop playback of any other app during a call and resume after the hang up
3) Phone BT should not affect this and should be a separate deal. This is how the CM7 appears to work as well. (at least this is how the stock rom works). The phone should be either speaker, handset or BT depending on if BT is connected or not. If BT is connected, default is BT. The problem I have seen is confusion when the phone is in the dock. BT is lit on the 'in call' screen, but audio is on the speaker and needs to be cycled through to bring it back to the appropriate device.
Am I the only one noticing this? I think I may go back to nottachtrix until this gets resolved. I use the dock all the time and this is getting bothersome, especially if there is a rom that deals with this correctly. I like CM7, but need it to work correctly with the car dock audio and charging.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
This is a development thread, if ur not talking about development then do not post it. go post it in proper thread where people can actually get use out of ur post.
The main issue here is that nobody on the team has the car dock, so debugging this kind of issues is hard on itself, even more when the logs people post are incomplete. And even if we thought of a way to fix it, testing an idea takes hours or even days, because people do this stuff on their free time and can't be waiting 24/7 for you to test anything. I must say, the fact that audio can route to the dock as you can experience it today is an achievement on itself.
PS: I agree, this should be in general, not development.
Turl et al,
Thanks. I appreciate the replies. I also get that this is volunteer and 'in spare time'. If the admins want to move it to the General forum, that is fine. I posted it here as it seemed to be a bit more of a development question, probably wrongly so.
So, if no developer has a dock, can we see how much interest there is and see if we can get enough funds together for you to buy a dock? (paypal donate link?) Amazon has them for about 25.00 or so. I know a number of the moto and even the samsung devices have car docks. I would guess that the motorola branded docks work similarly, but do not know for sure. This may mean if it is cracked here, it may also be useful on other CM roms as well.
Would a comparison log of a blur based rom doing the same activities be helpful? There was a thread in the issues on the early (nov/dec 2011) CM rom under development and it seemed like it was resolved in an earlier rom or on its way to being resolved.
Also, are you implying that my logs that I committed to the CM or Atrix Dev Team issues list are incomplete? If so, I apologize and would like some guidance as to how I can make them complete.
Regards,
Keith
Have the flash issues been fixed on the stable CM7 build? If not, that's something else which needs work...
turl1 said:
The main issue here is that nobody on the team has the car dock, so debugging this kind of issues is hard on itself, even more when the logs people post are incomplete. And even if we thought of a way to fix it, testing an idea takes hours or even days, because people do this stuff on their free time and can't be waiting 24/7 for you to test anything. I must say, the fact that audio can route to the dock as you can experience it today is an achievement on itself.
PS: I agree, this should be in general, not development.
Click to expand...
Click to collapse
I moved to CM7.2 from OFW Blur on July 1st2012, and there are only 2 things are troubling me in this transition.
1. This dock problem.
2. The Blur calendar that used to detect conference code dialing
May have to go back to Blur :crying:
Chairsofter1138 said:
Have the flash issues been fixed on the stable CM7 build? If not, that's something else which needs work...
Click to expand...
Click to collapse
I saw this behavior yesterday on a web page. It loaded and I could interact, but then went all crazy. So, it appears it is 'still' here.
Could this be related to other kernel issues? I mentioned the dock issues which bother me most right now as I deal with these every day. There is also the laggy response when using the presto library. These have been purported to be kernel issues and are bothersome, but do not stop me from using the ROM.
Keith
keithspg said:
So, if no developer has a dock, can we see how much interest there is and see if we can get enough funds together for you to buy a dock? (paypal donate link?) Amazon has them for about 25.00 or so. I know a number of the moto and even the samsung devices have car docks. I would guess that the motorola branded docks work similarly, but do not know for sure. This may mean if it is cracked here, it may also be useful on other CM roms as well.
Click to expand...
Click to collapse
Personally I don't own a car, but the desktop dock with analog audio out might be a possibility to explore if the issue can be reproduced there and you guys want me to look at it. They cost quite a bit locally though (~100USD+); if somebody from .ar is reading this and wants to mail me theirs for a while, I'll gladly take it and return it when I'm done fixing the bug.
keithspg said:
Would a comparison log of a blur based rom doing the same activities be helpful? There was a thread in the issues on the early (nov/dec 2011) CM rom under development and it seemed like it was resolved in an earlier rom or on its way to being resolved.
Click to expand...
Click to collapse
We did that 'blind debugging' back on the day, that's why you can get audio today using the docks. Testing things, however, was really time consuming, and I really don't want to repeat the experience.
keithspg said:
Also, are you implying that my logs that I committed to the CM or Atrix Dev Team issues list are incomplete? If so, I apologize and would like some guidance as to how I can make them complete.
Click to expand...
Click to collapse
I saw your report at https://code.google.com/p/cyanogenmod/issues/detail?id=5605, the log posted is incomplete (you cannot see, for example, when you first docked the phone; the first lines are around halfway the call). Use logcat to get a full one, see http://wiki.cyanogenmod.com/wiki/Logcat#ADB_Logcat
You don't own a car.. where do you live?
Sent from my MB860 using Tapatalk 2
Turl,
I am not certain, but think that the desk dock is different from the car dock. I just took my car dock apart and it appears that there is a 1.9k resistor to ground on pin 4 (between pins 4 and 5). I am pretty sure this is what triggers the 'car dock mode' and sends the audio out the 3.5mm plug on the stock rom and the CM7.2 rom.
The 'dock detection' seems to work correctly for the CM7.2 rom b/c when the phone is plugged into the dock, the audio comes out the mini plug. The phone will switch from audio out to phone call on BT, seamlessly. The issue appears when the phone audio changes from phone call on BT back to audio out. The audio is not returned back to the 3.5mm plug but to the phone speaker. Whenever audio is coming out the phone speaker and the phone is then plugged into the dock, the mode switches to the 3.5mm plug for audio output. So, it appears that you have the 'detection' working but the logic as to where to route the audio is not persistent and should always go to the 3.5mm jack until the phone is removed from the dock.
Does this help at all or am I just repeating what you already know...
I will try to get a more complete log.
Thanks!
Keith
unforgivenmercy said:
You don't own a car.. where do you live?
Click to expand...
Click to collapse
I'm a student, I don't need a car. I pay my bus with a NFC card and quickly get anywhere for cheap
---------- Post added at 04:55 AM ---------- Previous post was at 04:44 AM ----------
keithspg said:
Turl,
I am not certain, but think that the desk dock is different from the car dock. I just took my car dock apart and it appears that there is a 1.9k resistor to ground on pin 4 (between pins 4 and 5). I am pretty sure this is what triggers the 'car dock mode' and sends the audio out the 3.5mm plug on the stock rom and the CM7.2 rom.
The 'dock detection' seems to work correctly for the CM7.2 rom b/c when the phone is plugged into the dock, the audio comes out the mini plug. The phone will switch from audio out to phone call on BT, seamlessly. The issue appears when the phone audio changes from phone call on BT back to audio out. The audio is not returned back to the 3.5mm plug but to the phone speaker. Whenever audio is coming out the phone speaker and the phone is then plugged into the dock, the mode switches to the 3.5mm plug for audio output. So, it appears that you have the 'detection' working but the logic as to where to route the audio is not persistent and should always go to the 3.5mm jack until the phone is removed from the dock.
Does this help at all or am I just repeating what you already know...
I will try to get a more complete log.
Thanks!
Keith
Click to expand...
Click to collapse
We pretty much all know the 'symptoms' by now; what we need is to figure out a) which transitions are the faulty ones, code wise (ex. from end of call to music mode) b) how to hook into the audio stack and watch for those transitions and c) enforce the right ones instead. That takes time, code and testing.
Thanks for the clarification. I was pretty certain I was making it simpler in my mind than it was.
I just submitted a log to the issues list which is similar. https://code.google.com/p/cyanogenmod/issues/detail?id=5669 I did not have an opportunity to re-do the music issue and collect a log. I'll do that in the next few days. The issue I posted is related in that an 'un-docking' event is not properly handled while in call and connected to BT. Man, this stuff is complicated...
Thanks for the help! Even though the car docks are $100.00 in Ar, you still may ask for donations to get you one. I have a hunch that this is similar to the Droid docks and the CM community would be grateful for those that use docks with their motos.
Keith
keithspg said:
I just want to discuss this here. I have been running the 7.2 rc1 through latest nightly. Most everything works well and it is snappy. The biggest issue I have is with the car dock. This Rom doesn't correctly adjust to dock insertion and removal. Add to this Bluetooth phone audio and it becomes a bit of a pain, at least for me.
Issues:
1) Remove phone from dock after it has lost power and the battery still thinks it is connected and charging. This issue requires either a reboot or a reinsertion and removal from a car dock that has 5V USB power.
2) Audio does not return to 3.5mm plug after call. Put phone into dock. Play music or nav and the audio plays over the 3.5 mm plug. Receive a call when connected to bt, phone audio cones over BT. Hang up call and sound routes to phone speaker. - does not revert to dock audio. The workaround is to un-dock and re-dock and the audiop appears back on the car dock plug.
3) On call. Turn on car, BT connnects, phone audio routes to BT ( I think). place phone in car dock and you have to go to 'phone' then find 'in call' then turn on speaker then turn on bluetooth and audio appears over BT. THe confounding issue is placing the phone in the dock right after it connects to BT or before it has negotiated this connection.
Also I ran into a problem with receiving a notificaton while I was taking a movie with the camera. It stopped the movie.
I was posting these issues to the atrix dev team, but that issues list seems to have gone dormant. I recently posted it to the CM7 list and am now trying to get all my logs in order b/c I was running the latest nightly. These problems with setting the default audio exist with every CM7.2 since RC1. It seems that the issue is the logic with the dock insertion.
1) It 'should' send all audio out the car dock, except the phone audio, when it is plugged into the car dock.
2) It should stop playback of any other app during a call and resume after the hang up
3) Phone BT should not affect this and should be a separate deal. This is how the CM7 appears to work as well. (at least this is how the stock rom works). The phone should be either speaker, handset or BT depending on if BT is connected or not. If BT is connected, default is BT. The problem I have seen is confusion when the phone is in the dock. BT is lit on the 'in call' screen, but audio is on the speaker and needs to be cycled through to bring it back to the appropriate device.
Am I the only one noticing this? I think I may go back to nottachtrix until this gets resolved. I use the dock all the time and this is getting bothersome, especially if there is a rom that deals with this correctly. I like CM7, but need it to work correctly with the car dock audio and charging.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I have been able to replicate all the above issues.
Lol man and the joys of being a student. I am surrounded by 3 universities and 2 community colleges so I know how that goes.
Sent from my MB860 using Tapatalk 2
re-loaded nottachtrix (blur rom with stock kernel). In addition to the dock issues, I can confirm that the presto libraryhttp://play.google.com/store/apps/details?id=com.aocate.presto&hl=en has a problem. This allows speed-up play back of podcasts in Beyond Pod and other podcasting software.
With CM7, I cannot select any point in the playback by sliding the playback bar. The UI is very laggy and will not respond, quickly, to touch input (play, stop, selecting a point in the playback). Once I re-loaded the nottachtrix with the stock kernel, these responses became instantaneous again. I exchanged emails with the developer a few months back and he seemed to think it was kernel related. I will grab a log and post this to the CM7 issues list when I re-load CM7. I just thought I'd post this here in the hopes that someone has also noticed this issue and would post this as a defect. I do not think this is Atrix related, but a general CM7.2 issue.
Keith
Still using Nottachtrix due to the dock and presto library problem. I am also curious about a comment that the dock works 'correctly' for CM9 (jokersax). Can anyone confirm this? I prefer using CM7.2, but the daily use of the car dock and presto library keep me away. I am considering buying a car dock here for 25.00 and sending it from the US to Turl in AR. Anyone else want to contribute to this effort?
Keith
still no one has car dock
i have two Atrix
can be a tester any time
Sent from my MB860 using xda premium
Yep, There is a defect logged against this as well as this thread, but Turl appears to be the only developer working on this for the Atrix and he does not have a car dock...
keithspg said:
Still using Nottachtrix due to the dock and presto library problem. I am also curious about a comment that the dock works 'correctly' for CM9 (jokersax). Can anyone confirm this? I prefer using CM7.2, but the daily use of the car dock and presto library keep me away. I am considering buying a car dock here for 25.00 and sending it from the US to Turl in AR. Anyone else want to contribute to this effort?
Keith
Click to expand...
Click to collapse
Car dock audio works perfectly in epinter cm10, used that for a week. Now back to CM7.2
I wish if a dev could make a fix for cm7.2 using epinter cm10, if that is possible.
Ditto