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
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.
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
I have a new car and a new phone so it's hard to be sure.
I used the GNex for about 3 days with the new car and didn't see problems. Connected every time and sound was consistent
With the MotoX I am getting auto connected about 1/2 the time and a lot of stuttering on the bluetooth audio.
Same for others ?
Another question: When I connect bluetooth the volume always resets to about 80%. Can I change this setting anywhere ?
So it's not the car as I just had the same problems with my BT headphones. It also started playing through the speakers at one point even though the BT connection was still showing.
I use the Bluetooth calling feature with my truck. I haven't had any problems so far, but it's only been a few days. I will report back if I do have problems. I am running 4.4 with all OTAs.
My moto x after kitkat update bluetooth disconnects in middle and reconnects again in 5 seconds. Super annoying
sravanz said:
My moto x after kitkat update bluetooth disconnects in middle and reconnects again in 5 seconds. Super annoying
Click to expand...
Click to collapse
My HTC One did that with aosp kitkat. I haven't seen that on the X yet.
Moto X using Tapatalk
I've had pretty much the same experience with mine since the 4.4 update. I don't even bother listening to music over bluetooth now because it's so annoying with the constant stuttering. I'm hoping they fix it with the next update, whenever that comes. If not, I'll probably have to look into upgrading to a newer head unit. My GNex always worked great with this stereo's bluetooth.
I listened to Spotify Inmine yesterday, no problems. It even sent the song information to my car's display which it didn't do on my last phone.
I've been tethering my Nexus 7 using Bluetooth and had a lot of trouble getting it to connect the first time. But today was my first real use of it and the Internet connection on the Nexus 7 dropped part way through the trip. It was only being used to get traffic info for CoPilot, so I didn't notice right away when the connection was lost. A little troubleshooting got me nowhere, but then while driving the connection came back on its own.
Something happens with me
Sent from my Nexus 5 using XDA Premium 4 mobile app
No issues with bluetooth here. Pandora is streaming fine and Torque is talking to my OBD2 adapter as well (even both at the same time).
homemadehitshow said:
I have a new car and a new phone so it's hard to be sure.
I used the GNex for about 3 days with the new car and didn't see problems. Connected every time and sound was consistent
With the MotoX I am getting auto connected about 1/2 the time and a lot of stuttering on the bluetooth audio.
Same for others ?
Another question: When I connect bluetooth the volume always resets to about 80%. Can I change this setting anywhere ?
Click to expand...
Click to collapse
I use bluetooth daily and haven't experienced a disconnect or even a stutter with Google Play Music on 4.4. I chose the setting to resume music when driving is detected and now I don't even take out my phone when I get in my car. Music usually starts playing within 100' of driving. There is a mod to remove the audio warning; I haven't tried it yet, but I don't really have a problem with it either.
P!X3L said:
There is a mod to remove the audio warning; I haven't tried it yet, but I don't really have a problem with it either.
Click to expand...
Click to collapse
Samsung has the same thing on it's firmware, and while it was a PITA to find and fix, it can be done (fairly easily).
I've had some Bluetooth issues that I described here: http://forum.xda-developers.com/showthread.php?t=2562186
At least one other person mentioned their connection dropping repeatedly. My issue started with it only connecting to my hands free in my car, but but my separate A2DP audio receiver. If I tapped on the device in Bluetooth settings, it connected fine. I found an app called Bluetooth Auto Connect that has nice configuration options to do what I needed (connect to A2DP once General Motors connects), but it also plays nice with Tasker.
I did notice last night that my General Motors connection was starting and stopping repeatedly my entire drive home from work (~45 minutes). I noticed it at first when I would turn the screen on to thumb up a song on Pandora, and the "you're connected to a trusted device" message would flash. At first I thought it was just reminding me of that each time the screen came on (or manually unlocking when the screen turned on), but then noticed my radio was saying "Bluetooth Connected" every few minutes as well. I rarely actually talk on the phone, so it's not a huge deal, but as described in my post linked above, on Monday I got a call when I (thought I) was connected to my General Motors, but it wasn't. I answered the call and was talking on the handset when it connected to Bluetooth and then I was hands free.
I did also notice yesterday when I was listening to Pandora with wired headphones at my desk at work that it got started sputtering pretty bad after I got a text message and Active Display was "breathing". Not sure if the two are related, but it happened. I did get a few texts while driving home and didn't notice any skipping over Bluetooth then.
Interesting theory on the active display... I've often wondered if that was partially responsible for the stuttering issue I'm having, but I was under the impression that it is automatically disabled when the phone is in your pocket, or face down. I guess I have some more experimenting to do while I wait for the next update.
At least for me it would not be face down in the car so I'll keep an eye on that.
Can someone point me to where I can take care of the volume issue ?
OK figured it out and learned about Xpose. Very cool.
I'll see if this is what was actually my problem. My problem was that bluetooth audio level is always reset to 80% (or so) each time I use it.
Bluetooth in my car is awesome.
ATT kitkat with Toyota Venza
Before the update music streaming took 20 seconds to load, but now it works instantly.
Bluetooth has had half second "pauses" at random times... sometimes seems too coincide with the screen on or off, other times when the phone is doing nothing. Also before kit Kat Google music would show track number (but nothing else) now I've lost that too. Unrooted
Sent from my KFTHWI using Tapatalk 2
I experienced the pauses today when I overrode the volume warning. They kept occurring even after the volume was turned back down below 80%. I rebooted and started up some music without going over the volume suggestion and the skips were gone. If you're having trouble with the music or Bluetooth connection "skipping" try it out. Definitely tied to that volume warning somehow.
Interesting theory, I'll have to test it out. I have noticed that mine seems to do it at the same locations while I'm driving, and am starting to wonder if it is related to the handoff between towers.
Sent from my XT1060 using Tapatalk
Poor Audio over Bluetooth, Poor overall BT reception.
I thought it was my device and sent it back to google, they sent me a replacement and it has the same issue, if im streaming music to any device (Headphones, Speaker, Car Stereo) and cover the top of my phone its like im almost going out of range and the audio goes choppy or off, remove my hand and the audio returns to normal. Google said they have never heard of this issue before and are convinced a third device will solve the issue, i doubt it unless they have a revision 2 model.
Its not just audio, i have a watch that gets notification on the go, same thing, if the top gets covered my watch often says disconnected, take the phone out and within 20 seconds it reconnects.
Clearly there is an issue with BT on this phone, no software update (inc. N preview) addresses it, google seems unaware or uninterested in the problem, i would have addressed it a long time ago but i have been holding out for a fix before i realised how easy it is to replicate the problem.
I also have issue with it. I pair my headphones Phillips Tapster and all I hear is non-stop choppy sound(every few seconds a spike). In the beginning I thought my headphones were giving problems, but it is not the case, becase I have a few other Androids and all work fine. So it is the 6P.
Unfortunately I couldn't find a solution which I can share. I only can share what won't work in my experience:
- Factory reset(wipe);
- Return to stock if custom ROM is used;
- Changing ROMs;
- Killing all other apps except the one which uses the device currently;
- Switching off other communication services like wi-fi;
DJorgio said:
Poor Audio over Bluetooth, Poor overall BT reception.
I thought it was my device and sent it back to google, they sent me a replacement and it has the same issue, if im streaming music to any device (Headphones, Speaker, Car Stereo) and cover the top of my phone its like im almost going out of range and the audio goes choppy or off, remove my hand and the audio returns to normal. Google said they have never heard of this issue before and are convinced a third device will solve the issue, i doubt it unless they have a revision 2 model.
Its not just audio, i have a watch that gets notification on the go, same thing, if the top gets covered my watch often says disconnected, take the phone out and within 20 seconds it reconnects.
Clearly there is an issue with BT on this phone, no software update (inc. N preview) addresses it, google seems unaware or uninterested in the problem, i would have addressed it a long time ago but i have been holding out for a fix before i realised how easy it is to replicate the problem.
Click to expand...
Click to collapse
I can confirm this.
I get this as well. I can't put the phone in my pocket if I use Bluetooth headphones. I've tried different headphones, both factory M and N preview.
Mines not that bad. It used to stutter every minute or so but I turned off Bluetooth/WiFi scanning and fixed that problem. But now it just decided to start getting all staticy when the screen is turned on. Either by me text or phone calls. Haven't figured out why it's only happening at that time
r1nstang said:
Mines not that bad. It used to stutter every minute or so but I turned off Bluetooth/WiFi scanning and fixed that problem. But now it just decided to start getting all staticy when the screen is turned on. Either by me text or phone calls. Haven't figured out why it's only happening at that time
Click to expand...
Click to collapse
What happens when you cover the top of your phone with your hands, does the audio start cutting out?
DJorgio said:
What happens when you cover the top of your phone with your hands, does the audio start cutting out?
Click to expand...
Click to collapse
nothing happens at all. no change in sounds, no stuttering in play.
I did another FDR the other day. got everything installed again turned off wifi/bluetooth scanning and wifi itself (since im not at home) and works perfect. no skipping or stuttering at all. even the 5 seconds of stutter is gone when the screen turns on. hopefully it stays this way
running Ressurection remix m 5.6.9-20160614
I have the same problem on my car sound system (mazda 2 2016). I found a solution. I turn on the N6P bluetooth before turning on the car system (in my car it turns on when I turn on the car at the same time). When I have the N6P's bluetooth on before turning on the car I have a good conection at 100% of the times. When I forget to turn on the N6P's bluetooth before turning on the car I have a bad conection at 50% of the times.
I hope this could work on your sound systems.
DJorgio said:
Poor Audio over Bluetooth, Poor overall BT reception.
I thought it was my device and sent it back to google, they sent me a replacement and it has the same issue, if im streaming music to any device (Headphones, Speaker, Car Stereo) and cover the top of my phone its like im almost going out of range and the audio goes choppy or off, remove my hand and the audio returns to normal. Google said they have never heard of this issue before and are convinced a third device will solve the issue, i doubt it unless they have a revision 2 model.
Its not just audio, i have a watch that gets notification on the go, same thing, if the top gets covered my watch often says disconnected, take the phone out and within 20 seconds it reconnects.
Clearly there is an issue with BT on this phone, no software update (inc. N preview) addresses it, google seems unaware or uninterested in the problem, i would have addressed it a long time ago but i have been holding out for a fix before i realised how easy it is to replicate the problem.
Click to expand...
Click to collapse
I have tried 3 replacement phones and each time I speak with Google they inform me that they are not aware of any BT issue. Bull****! I can't wait to get rid of this phone. I have the same issues you have related to BT.
r1nstang said:
nothing happens at all. no change in sounds, no stuttering in play.
I did another FDR the other day. got everything installed again turned off wifi/bluetooth scanning and wifi itself (since im not at home) and works perfect. no skipping or stuttering at all. even the 5 seconds of stutter is gone when the screen turns on. hopefully it stays this way
running Ressurection remix m 5.6.9-20160614
Click to expand...
Click to collapse
Thanks, i tried fresh install of mentioned ROM and disabled scanning and the issue remains but glad to hear yours is ok now.
caalca said:
I have the same problem on my car sound system (mazda 2 2016). I found a solution. I turn on the N6P bluetooth before turning on the car system (in my car it turns on when I turn on the car at the same time). When I have the N6P's bluetooth on before turning on the car I have a good conection at 100% of the times. When I forget to turn on the N6P's bluetooth before turning on the car I have a bad conection at 50% of the times.
I hope this could work on your sound systems.
Click to expand...
Click to collapse
Thanks but i rarely turn off BT, its always available but i did go and try combinations of having it off or on pre connection and no difference, still my phone acts like the BT signal is too weak if i move around.
V4cc4r0 said:
I have tried 3 replacement phones and each time I speak with Google they inform me that they are not aware of any BT issue. Bull****! I can't wait to get rid of this phone. I have the same issues you have related to BT.
Click to expand...
Click to collapse
Thanks for confirming, im not holding any hope on the 3rd replacement either, I have had a lot of nexus devices over the years and this BT issue is unique and driving me nuts and really making me think twice about the new upcoming replacement in Q4, especially if its made by Huawei. Ive also noticed the chassis has started to buckle near the volume buttons.
well for some unknown reason the stutter when screen comes on came back. worked fine on bluetooth all weekend. then this morning i go to use my LG 850 BT headphones...and bam...stuttering. maybe LG pissed off Hauwei and they decided to cause issues with all LG items hahahaha
r1nstang said:
well for some unknown reason the stutter when screen comes on came back. worked fine on bluetooth all weekend. then this morning i go to use my LG 850 BT headphones...and bam...stuttering. maybe LG pissed off Hauwei and they decided to cause issues with all LG items hahahaha
Click to expand...
Click to collapse
Apparently all CM based ROMs has the stutter issue when screen is turned on when streaming, something to do with the AudioFX, im back on AOSP ROM, no issue with screen on but still have issue when covering the top of my phone or putting in my pocket. sux.
DJorgio said:
Apparently all CM based ROMs has the stutter issue when screen is turned on when streaming, something to do with the AudioFX, im back on AOSP ROM, no issue with screen on but still have issue when covering the top of my phone or putting in my pocket. sux.
Click to expand...
Click to collapse
thanks for that. i hadnt heard it was a CM issue. gonna install PA6.0 within the next couple days