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
Related
I have noticed a couple of issues which seem to be limited to the focus.
First, the by default the "Anti-Shacking" setting on the camera is set to "off". and there is no way to change this for good. I have to change it every-time I start the camera.
Second, the screen seems to randomly dim and light back up. I don't know if its because i'm covering the light sensor or what. But it's annoying.
Has anyone else noticed these?
Does anyone else have others?
KonAitor said:
First, the by default the "Anti-Shacking" setting on the camera is set to "off". and there is no way to change this for good. I have to change it every-time I start the camera.
Click to expand...
Click to collapse
This was noted as an issue with the phone prior to it's release, and it's currently like that for everyone. None of the settings you change in the camera app will stay after closing it.
As for your brightness issue, it probably is a case of the sensor reacting to you blocking it. I have auto brightness turned off, but have experienced what you are describing on other phones when looking over the sensor (blocking light with my head) or when I have a finger placed over the sensor
I found a new issue with mine.
I have an old Belkin 3.5mm to caset adapter. I can plug it into the phone and the music will come out of my stereo beautifully.
However, after removing the converter (once or twice) i loose the ability to use the mic on the phone(shazam and voice commands don't work unless I use a headset or perform a soft reset).
Anyone have an idea why this is. Does the phone not support standard 3.5mm jack equipment, like headphones and earphones?
it works fine with me with the newer one i had, i don't know the brand, but I have noticed at times the phone seems to mute itself =\
KonAitor said:
I found a new issue with mine.
I have an old Belkin 3.5mm to caset adapter. I can plug it into the phone and the music will come out of my stereo beautifully.
However, after removing the converter (once or twice) i loose the ability to use the mic on the phone(shazam and voice commands don't work unless I use a headset or perform a soft reset).
Anyone have an idea why this is. Does the phone not support standard 3.5mm jack equipment, like headphones and earphones?
Click to expand...
Click to collapse
I've had this issue myself with the aux cable in my car. Plugging it in to listen to music works fine, after unplugging, I cannot use voice commands. I haven't purposely tried making a call afterwards, but I'm fairly certain I have received calls, unplugged it, and was able to talk normally. I'll test after work, but can confirm your issue on my end at least.
I called their support today. They ended up transferring me to the "Level 3" Support.
I told him about the camera and aux port issues. He said they were not aware of those, and even tested the camera issues on a new test unit.
Hopefully, now that they know about this, they will be able to implement a fix.
He seemed the most disturbed by the aux cable issue.
Sounds like the aux-cable issue is related to the jack thinking there is still something plugged into the jack. This is a semi-common issue on the fruit company's phones.
The headphone/headset detection works by sensing where ground is on the plug. Sometimes that sense gets "stuck"
A simple plug and unplug of any 3.5mm jack should unstick it.
*disclaimer: I don't have a Focus yet, but will this weekend.
liquidiq said:
Sounds like the aux-cable issue is related to the jack thinking there is still something plugged into the jack. This is a semi-common issue on the fruit company's phones.
The headphone/headset detection works by sensing where ground is on the plug. Sometimes that sense gets "stuck"
A simple plug and unplug of any 3.5mm jack should unstick it.
*disclaimer: I don't have a Focus yet, but will this weekend.
Click to expand...
Click to collapse
I am aware of what's happening. Both I and the tech agreed that there must be some short happening. This is more common with 3.5 jacks that are designed for more complex functions. Such as volume control, and Video out.
Interestingly enough, he checked to see if there was Video out with these phones as with other Galaxy S series. But he couldn't find anything in their docs .
KonAitor said:
I am aware of what's happening.
Click to expand...
Click to collapse
Sure didn't sound like it from your initial post, but I'm glad you've got it covered now.
liquidiq said:
Sure didn't sound like it from your initial post, but I'm glad you've got it covered now.
Click to expand...
Click to collapse
It's still an issue. Just because it happens on other devices does not mean it is acceptable. And Ive tried alot of remedies to fixing it without resets (like plugging in/out the headset or another cable).
KonAitor said:
It's still an issue. Just because it happens on other devices does not mean it is acceptable. And Ive tried alot of remedies to fixing it without resets (like plugging in/out the headset or another cable).
Click to expand...
Click to collapse
Oh I totally agree with you, it's definately an issue. I think you should exchange the phone for a new one, as I believe it's a manufacturing tolerance.
liquidiq said:
Oh I totally agree with you, it's definately an issue. I think you should exchange the phone for a new one, as I believe it's a manufacturing tolerance.
Click to expand...
Click to collapse
i too am having this issue...but after making a phone call then i can use voice commands again.
chizzwhizz said:
i too am having this issue...but after making a phone call then i can use voice commands again.
Click to expand...
Click to collapse
Interesting workaround. I will try that next time it happens.
Speaker click issue when screen off
Here's a new one, anyone else having this? When my phone screen is off, sometimes I notice a periodic static click coming from the handset speaker (I don't think it's the back speaker.)
It's not a single click, but more of a stutter, which stops immediately when I turn the phone on and it shows the lock screen.
It stops if you unlock the phone, use it, and turn it off again. It DOES NOT stop if you turn the phone on but don't unlock it, and turn it off again.
I actually noticed this myself for the first time today. It was rather annoying. I was in the middle of things and so just did a soft reset. Hopefully it won't happen again any time soon. First time hearing/noticing this in almost a month (got phone on 11/8).
McP
Anyone get the 3.5mm plug to work on the car dock / desk cradle after flashing DL30?
I thought the requirement was 2.2, but can't seem to get it to work.
It works
on both the car dock app and music app there is a phone icon. Click it. It will change the output from the phone to the dock.
Sent from my SCH-I500 using XDA App
It would be nice to have a toogle widget so that it wouldn't app dependent.
ibegary said:
it works
on both the car dock app and music app there is a phone icon. Click it. It will change the output from the phone to the dock.
Sent from my sch-i500 using xda app
Click to expand...
Click to collapse
*happy* *happy* *happy* *happy* *happy*
I can't find the icon. Does out only appear when the phone its in the dock? Can you use programs other than Music Player (such as Pandora, Listen, etc.)?
When you place the phone in the dock and the app launches (car dock or desk dock) select the icon. I would imagine once you have done this you can run another app (like pandora) and it should work
Sent from my SCH-I500 using XDA App
Kevin Gossett said:
When you place the phone in the dock and the app launches (car dock or desk dock) select the icon. I would imagine once you have done this you can run another app (like pandora) and it should work
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Anyone get the app to launch on dock when using Launcher Pro? Before a hit of the home key would launch the app, but now that doesnt seem to work. Anyone?
Kevin Gossett said:
When you place the phone in the dock and the app launches (car dock or desk dock) select the icon. I would imagine once you have done this you can run another app (like pandora) and it should work
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
That's correct. Once you select the icon in the car dock app, just go back to your home by hitting the back button and launch any other app and it should play through the dock. I confirmed with Pandora and SlingPlayer.
You wont see the icon on the car dock or music player unless it is actually docked.
Hope this helps.
I get the steering wheel icon in the notification bar but the app didn't launch. Does it show on the car dock app?
Edit: I was a delta alpha. I located said button in the car stock program. I was confused because the dock didn't automatically pop up like it did in previous versions. I had to start it while in the dock. My only complaint now is that I have to manually switch it every time.
Sent from my SCH-I500 using XDA App
Has anyone else noticed that the sound quality is severely degraded when running through the dock instead of a direct connection to the 3.5mm jack?
I mean I'm talking absolutely terrible audio quality. Am I the only one? Try connecting a decent pair of headphones directly to the phone and then to the dock, the difference will be very, very apparent.
Try turning down your media volume on the phone while in the dock and using an external amp to control the volume. This sort of thing happens when my internal Sirius radio volume is turned up to full and then run into into the car stero.
It worked fine...sound a bit degraded though, but never the less, it works. Now byebye carrying ipod around.
caesus said:
Has anyone else noticed that the sound quality is severely degraded when running through the dock instead of a direct connection to the 3.5mm jack?
I mean I'm talking absolutely terrible audio quality. Am I the only one? Try connecting a decent pair of headphones directly to the phone and then to the dock, the difference will be very, very apparent.
Click to expand...
Click to collapse
My Dock has a lot of static, even when I have no sound playing. When I remove the power, the static goes away until I plug the power back in. I have tried a USB cable and the same static happens. When I have the same speaker setup plugged into the headphone on the phone, no static. Does anyone else have this issue?
Yea, noticed that too. I thought it was my cable.
namoh21 said:
My Dock has a lot of static, even when I have no sound playing. When I remove the power, the static goes away until I plug the power back in. I have tried a USB cable and the same static happens. When I have the same speaker setup plugged into the headphone on the phone, no static. Does anyone else have this issue?
Click to expand...
Click to collapse
I have noticed this even without the dock, mine I believe is a whine related to the charging, as it always stopped if I removed the charger while connected to radio. Only way I found to reduce it was to set the phone volume to about 13 or so, so I wouldn't have to run the car stereo quite as high of a volume.
Picked up the Verizon car dock today and what a joy it is to finally be able to use it for audio. As previously stated, you must use the official Car Cradle app to activate the 3.5mm jack. Since the app is basically crap (Bing, Verizon Navigator), I use Custom Car Doc, which allows you to choose whatever apps you want listed. I put Car Cradle on there and am golden. Just use it to activate the jack, then back out and you can use Custom Car Doc normally.
As for audio quality, it sounds great to me. Many cars add audio interference when the phone is plugged into the cig lighter. Amazon carries several cures for this. I installed a Pyramid NS12 12 Amp InLine Noise Suppressor, which was $6 including shipping, and it did the trick on my Mazdaspeed3.
I got the cardock to work, but not the desk cradle. I think in the superclean it was removed. It has the ASOP desk , there is no speaker button.
I use Alarm Clock Plus for my home dock and it has the speaker button.
I didn't like the stock car dock app, so I was using Custom Car Home for a while. That didn't have the speaker button. Then I tried Google Car Home. I could activate the speaker by going into the stock Music app, bit not from the Google Car Home app itself.
I guess ill have to buckle down and try the stock Samsung app. They suck.
Sent from my SCH-I500 using XDA App
After using DL30 for a few days, I have to say, the car cradle and desktop cradle both gives soo much static....
At least the car is more barable, but the desk was not barable.
I posted a request in the Apps section for someone to 'de-bing' the stock Froyo app, no result yet. What I did find, however, is that you can activate the dock audio from *any* of the apps that support it. So, you can activate it directly from the music app if you want to use the Google car dock, or you can activate it from the Stock Car dock if you choose to swap out to the AOSP music player. Just don't pull move like me and replace BOTH with AOSP apps and then kick yourself when you have to restore lol.
I've checked high and low on the forums for something similar or a solution to my problem, but alas I can't find anything so I'm starting a thread.
As the title state's my phone rings people whenever an AUX jack is in, listening to music, or hooked up to a stereo. I've tried restoring to factory setting's also I've tried different headphones and stereo's but still no joy.
T-Mobile
HTC HD Desire HD.
Any help or suggestions would be appreciated.
Many thanks.
Flynn.
Hmm, maybe I've got a similar probelm, I use normal 3.5mm in-ear headphones with my Desire HD and they are able to make strange things, if I gently move the jack, sometimes my phones starts a call to the latest called person, sometimes it skips to the next song, sometimes the music is paused.
I think that has something to to with the default headset funcionality, but it would be great if there was a way to lock any function other than playing music if no multi-functional headset is plugged in.
You're going to think I'm nuts but I've tried everything.
It seems to go berserk when you do a screwing motion with the 3.5mm jack. It doesn't make any difference what headphones I use whether they've got any calling buttons on them or not they just go absolutely mental.
I will admit to doing the calling bug that increases the music volume when you hang up straight after making the call.
But I still can't get around it and it's VERY frustrating, especially in the car.
The same problem
Hey, i have the same problem. This morning i was listening to music on my way to school. And all of the sudden it went berserk, started calling, skipping. What to do?
That happens if the AUX wire passes a current (many times stray) back to the phone. The phone just reacts in the way it would if a button was pressed on one of those headphones having an in-line mic/button.
A lot of times this stray current comes because of static build-up. I'm sure you guys know how to get rid of that. If it's not because of static, it might be because of faulty wiring on the audio enhancement (not usually the case), or if the audio enhancement and the phone function at hugely different potential differences (also, usually not the case).
As far as mine is concerned, freeing it of static usually helps.
One way to quickly judge if it's static that's the problem is if the call/skip/whatever usually takes place the minute you plug it in.
ferrarihap said:
Hey, i have the same problem. This morning i was listening to music on my way to school. And all of the sudden it went berserk, started calling, skipping. What to do?
Click to expand...
Click to collapse
Search for an app on the market called "headset blocker"
NO luck
The above post helps,
However im testing the new ICS rom by Lord Clockan and twistedumbrella and there is no compatability for ICS. Wondering is anyone knows what part of the phone controls headset controls so i can mak an app to block it on 4.0?
Its a real pain as i cant play music at all,
random apps start playing music over other apps and music stops in others, skips tracks etc. SO frustrating.
Take out headphones
Blow into the jack hole
Plug back in headphones
Sorted till the next time crap builds up in there.
Sent from my Desire HD using xda premium
radixon said:
Search for an app on the market called "headset blocker"
Click to expand...
Click to collapse
did this work for any one else, it doesn't seem to be working for me
rakinisbat said:
did this work for any one else, it doesn't seem to be working for me
Click to expand...
Click to collapse
This should answer your question:
geinome said:
The above post helps,
[...]
Click to expand...
Click to collapse
I have the same problem. And its realy anoyeing me . Cant listen to music at all anymore on my desire HD...
I have that problem for a while now. The blwoing inside technik did work for a while, but doesent anymore.
That headset blocker would be amazing if it would be working on ICS. Im on the LordMod Beta to.
@geinome would be amazing if you could make an app to fix that. But honestly i have no idea were in the sistem that headset control is located. Hope you can find it.
Found a Fix. Hope it helps you guys to.
I found an other App, that did solfe the problem for me eaven on ICS. The App Headset Interceptor is meant to let you choos, which Music App should receve the signal coming from the remote on the headset. But if you dont choose any from the Apps to get the signal, none dose and so none is cousing problems
Would love to post you guys the link to the market, but cant couse i dont have anouth post yet. But im sure i can sind it yourself
I hope this is solving the problem with the unwanted calls to. Couse i never had that problem, i cant test that.
you dont need any apps
you just need a needle to clean up the pocket lint inside the 3.55 jack.
for me it's usually enough to unplug the jack and plug it in again and all works well for the next month or so.
Sometimes , when I plug headphones, or any auxiliary audio jack, a "microphone" icon appears on the upper bar on the screen, and then at the first instance of any noise it randomly dials someone from my recent call list. I usually catch it in time to end the call before it even rings, but not always. This is SO aggravating as very frequently I use my phone to listen to music either in my car or while exercising/working with headphones.
I've had this ongoing problem since release date and it seems to be random in frequency. Sometimes it happens every time I plug a jack in, then sometimes it goes a whole month without happening. The only way I've found to eliminate the "microphone" icon and prevent the phone from calling out is to stop my music, go to settings, other, voice command, and then uncheck the "enable voice command" box. It seems that inserting headphones automatically re-enables this against my will. I thought installing some of the updates or various roms would have helped, but nothing helped. I'm back to using the latest stock rom and because of my irritation with this phone have just about given up on doing any more to it.
Is there any way for me to permanently delete voice command? I never use it and unfortunately the only threads I can find on here deal with people asking the opposite.
Any advice would be appreciated.
If you're on an Android ROM try downloading Titanium Backup from the market and deleting the voice applications if you don't use any of them.
SecretStash said:
Sometimes , when I plug headphones, or any auxiliary audio jack, a "microphone" icon appears on the upper bar on the screen, and then at the first instance of any noise it randomly dials someone from my recent call list. I usually catch it in time to end the call before it even rings, but not always. This is SO aggravating as very frequently I use my phone to listen to music either in my car or while exercising/working with headphones.
I've had this ongoing problem since release date and it seems to be random in frequency. Sometimes it happens every time I plug a jack in, then sometimes it goes a whole month without happening. The only way I've found to eliminate the "microphone" icon and prevent the phone from calling out is to stop my music, go to settings, other, voice command, and then uncheck the "enable voice command" box. It seems that inserting headphones automatically re-enables this against my will. I thought installing some of the updates or various roms would have helped, but nothing helped. I'm back to using the latest stock rom and because of my irritation with this phone have just about given up on doing any more to it.
Is there any way for me to permanently delete voice command? I never use it and unfortunately the only threads I can find on here deal with people asking the opposite.
Any advice would be appreciated.
Click to expand...
Click to collapse
hd2 is a headphone button enabled phone ....so pluging in some jacks can cause the effect of the button to trigger on itself
Also on occasions fluff into audio port means the jack just does not drop right in
pull the battery and with a pin and torch check its clear, be gentle with the pin
I have many different heaphones/earbuds that I use with this phone and none of them give me a problem on the latest official HD2 Rom for T-Mobile
1. the original earbud set that came with it
2. Old (like 10 years old) Sony over the ear headphones (best sounding by far in this group and 6ft cord makes excellent antenna for FM radio)
3. phillips earbuds
4. Rocketfish earbuds (Crappiest but has long cord for antenna)
5. Phillips behind the neck heaphones (second best sounding)
6. Sony earbuds (these things rock for earbuds)
7. Phillips earphones
8. Skullcandy earbuds (offers the best fit out of all of them in the ear types)
If I have any gripes about using headphones it has to be that HTC put the jack on the wrong end of the phone.....
i couldnt find the place to ask this question, but would it still be wise to buy HTC HD2 instead of Motorola Defy? my budget is something around 17,000 INR. Pls guys help, im so confused bout buying the phone, personally i like the design of both Defy & HD2 and as i have read HD2 is better phone configuration wise and regarding flashing with custom roms but isn't it a bit outdated now?
Thanks for the replys. I'm considering filing an insurance claim on my device to see if they can fix it as I already suspected that the headphone jack itself may be the culprit. Since the hd2 is discontinued, if they can't replace/repair it, then I'm pretty sure they'll hook me up with the current gen htc handset for tmobile (evo?)
Still though. If anyone could tell me how to deactivate, or delete from the device/registry, Voice Command, it would save me a lot of trouble. I've only 3 months left until I get an upgrade anyway.
Cross posting from the CM7 Epic forum to get more exposure and see if there is anyone NOT experiencing this problem and also maybe see if this extends beyond CM7 to regular Epic GB users. Here is the original thread I created.
Here is the post:
The Issue: When the phone is placed into the Samsung Car Dock, and then subsequently a hands free BT call is placed, the audio quality over the hands free is terrible and unusable.
I have been experiencing this issue since I started using CM back in October, and it was only today that I finally (and accidentally) discovered the action that causes it to happen. For the longest time I thought the problem somehow centered on switching from playing A2DP audio (which always sounds just fine) to the phone call, though I couldn't repeat this consistently, as sometimes I could get a call with good quality, but most of the time, even with freezing Music so it didn't start automatically when BT/car dock were connect, calls just sounded horrible.
Today, all that changed and I figure out that no matter what the state of A2DP music is, as long as the call is placed/received BEFORE the USB connector of the car dock is slid in to place, the audio quality is just fine. If you put the phone in the dock and engage the USB connector and then place/receive a call, you run into my aforementioned issue. I tested to see if this was related to the Car Home app, and running the app and placing a call out of the car dock was just fine as well. You can place a call, and then plug in the car dock and everything is OK that way too.
So something has to happen when the car dock is physically connected to the phone that messes with the audio. Can someone attempt to repeat this problem so I know it is ultimately not someting weird with my car/head unit/whatever. I don't believe it is because I didn't experience this issue before I switched to CM7.
Click to expand...
Click to collapse
Bump on this topic, no one else notice this? Can people try this out and see what happens, even if you don't normally use the device that way?