Please dont flame me i have been searching for awhile, what is the trick to get the audio jack or bluetooth to work i read something that you can send all noises through one of the two? i looked everywhere even google and am having a hard time finding this fix? any help would be great
reeshmd23 said:
Please dont flame me i have been searching for awhile, what is the trick to get the audio jack or bluetooth to work i read something that you can send all noises through one of the two? i looked everywhere even google and am having a hard time finding this fix? any help would be great
Click to expand...
Click to collapse
Neither work.
The 3.5mm jack used to kinda work, but it would break all other audio. IIRC I directed someone on how to set it up, and it didn't work - so it seems that doesn't work anymore either.
BT never worked, but it is close to being fixed.
You can get an extUSB dongle off ebay for like $2 and use it - that does work, although it's far from flawless - some have reported severe sluggishness after unplugging it.
I picked up this and it works great:
http://www.amazon.com/gp/product/B001P0IFXI
killerz298 said:
I picked up this and it works great:
http://www.amazon.com/gp/product/B001P0IFXI
Click to expand...
Click to collapse
What is interesting is I have the same exact adapter and although it works great when using it, as arrrghhh mentioned as soon as I unplug it my Sprint TP2 gets extremely sluggish...that does not happen to you? I'm assuming you have a Sprint TP2? What kernel, RiL etc are you using?
pdawg17 said:
What is interesting is I have the same exact adapter and although it works great when using it, as arrrghhh mentioned as soon as I unplug it my Sprint TP2 gets extremely sluggish...that does not happen to you? I'm assuming you have a Sprint TP2? What kernel, RiL etc are you using?
Click to expand...
Click to collapse
It's a bug, I don't think any particular combination will resolve it - any kernel will either have the partially broken code that causes the sluggishness, or if you go far enough back the code will simply not be present, and it won't work at all.
Has anyone taken logs or narrowed down what is the cause of the sluggishness? I can't seem to find my extUSB dongle. It's a pretty minor issue I know, but I don't know if anyone has investigated it.
thanks for the replies looks like its better to wait. i have been trying out slingplayer on android and its better picture quality than the windows mobile one the headphone jack working would be just to awesome. thanks again guys
arrrghhh said:
It's a bug, I don't think any particular combination will resolve it - any kernel will either have the partially broken code that causes the sluggishness, or if you go far enough back the code will simply not be present, and it won't work at all.
Has anyone taken logs or narrowed down what is the cause of the sluggishness? I can't seem to find my extUSB dongle. It's a pretty minor issue I know, but I don't know if anyone has investigated it.
Click to expand...
Click to collapse
I wouldn't call it a "minor issue" - for me, this is the one issue that prevents me from using Froyo full time. I've gone back to the auto-build kernel, as that seems to avoid the sluggishness problem. But support for external audio via the USB dongle is still very troublesome. I never know when the audio will work and when it won't.
One fairly consistent failure is that connecting audio via the dongle seems to turn off the TP2's microphone.
When I get into the car, I put my phone into its holder and plug the audio into the car radio. That way, I can talk handsfree - the audio comes from the car speakers, and the phone's microphone picks up my voice very nicely from the driver's seat. But it only works in Windows - when I boot to Android, the mic gets disabled and no one can hear me when I call.
So it may be a minor issue to some, but to others of us it is the only thing forcing us back to Windows.
Rightfully, if I'm going to complain, I should jump in and try to help. But I'm swamped with other work at the moment, so I'll be lurking and hoping that someone is able to focus on this eventually. Sorry I can't do more.
Gilliland said:
I wouldn't call it a "minor issue" - for me, this is the one issue that prevents me from using Froyo full time. I've gone back to the auto-build kernel, as that seems to avoid the sluggishness problem. But support for external audio via the USB dongle is still very troublesome. I never know when the audio will work and when it won't.
Click to expand...
Click to collapse
Ok, so it's a big issue for you - and as much as I would love to have the 3.5mm jack working, it's certainly not earth-shattering like the RIL issues were. The main problem - there's only two RHOD's that have the 3.5mm jack. That's probably the #1 reason that it is not a higher priority - we're in the minority among Rhodium owners.
It'll get fixed eventually, there's just a lot of things being worked on - and a lot of our devs are spreading themselves too thin. We do need moar help, but it's not easy work!
arrrghhh said:
Ok, so it's a big issue for you - and as much as I would love to have the 3.5mm jack working, it's certainly not earth-shattering like the RIL issues were. The main problem - there's only two RHOD's that have the 3.5mm jack. That's probably the #1 reason that it is not a higher priority - we're in the minority among Rhodium owners.
It'll get fixed eventually, there's just a lot of things being worked on - and a lot of our devs are spreading themselves too thin. We do need moar help, but it's not easy work!
Click to expand...
Click to collapse
I understand and agree. Without a doubt, the RIL issues are more important.
For the record, I'm not talking about the 3.5mm jack on the phone - I know there isn't a lot of work being done there. I'm talking about using the USB port with a dongle. I'm still using a 3.5mm cord to connect to the car, but I'm connecting it via a dongle into the phone's USB port. I think that the USB connection for audio is common across all of these phones, right?
Gilliland said:
I understand and agree. Without a doubt, the RIL issues are more important.
For the record, I'm not talking about the 3.5mm jack on the phone - I know there isn't a lot of work being done there. I'm talking about using the USB port with a dongle. I'm still using a 3.5mm cord to connect to the car, but I'm connecting it via a dongle into the phone's USB port. I think that the USB connection for audio is common across all of these phones, right?
Click to expand...
Click to collapse
Oh, yes. That works - is it inconsistent? ACL wrote the kernel code for that, and it didn't get a lot of attention when he first wrote it... so he's kinda ignored it, I don't think anyone has specifically addressed issues related to it.
As I have asked before (perhaps in another thread) do we have logs of these situations?
If you're having audio routing issues, there's a lot of changes coming related to audio routing...
arrrghhh said:
Oh, yes. That works - is it inconsistent? ACL wrote the kernel code for that, and it didn't get a lot of attention when he first wrote it... so he's kinda ignored it, I don't think anyone has specifically addressed issues related to it.
As I have asked before (perhaps in another thread) do we have logs of these situations?
If you're having audio routing issues, there's a lot of changes coming related to audio routing...
Click to expand...
Click to collapse
As I reported above, plugging in an audio cable seems to disable the phone's microphone. So my typical usage (audio routed to the car stereo, mic active on the phone) isn't possible in Android (though it works fine in Windows).
There may also be other inconsistencies, but I'm too swamped with other work to be able to troubleshoot and log it. That's why I tend to lurk rather than post - I can't properly participate in the process as I'd like to.
I wish I could give you better info. You guys are doing amazing work, and I really can't expect you (or anyone) to worry about the external audio if it isn't important to you.
If I can find some spare time, I'll try to do some testing and logging. But I said the same thing two weeks ago, and it hasn't come true yet. Between my day job and trying to get this house on the market, I'm swamped.
Gilliland said:
As I reported above, plugging in an audio cable seems to disable the phone's microphone. So my typical usage (audio routed to the car stereo, mic active on the phone) isn't possible in Android (though it works fine in Windows).
There may also be other inconsistencies, but I'm too swamped with other work to be able to troubleshoot and log it. That's why I tend to lurk rather than post - I can't properly participate in the process as I'd like to.
I wish I could give you better info. You guys are doing amazing work, and I really can't expect you (or anyone) to worry about the external audio if it isn't important to you.
If I can find some spare time, I'll try to do some testing and logging. But I said the same thing two weeks ago, and it hasn't come true yet. Between my day job and trying to get this house on the market, I'm swamped.
Click to expand...
Click to collapse
Real life can be a real ***** sometimes .
I still haven't been able to find my dongle from my old RAPH, I might just have to break down and buy one to test with! ACL's been pretty busy too, I heard he bricked his phone the poor guy... I'm not sure if he got another one yet or not, NAND threads have been eerily quiet...
arrrghhh said:
Ok, so it's a big issue for you - and as much as I would love to have the 3.5mm jack working, it's certainly not earth-shattering like the RIL issues were. The main problem - there's only two RHOD's that have the 3.5mm jack. That's probably the #1 reason that it is not a higher priority - we're in the minority among Rhodium owners.
It'll get fixed eventually, there's just a lot of things being worked on - and a lot of our devs are spreading themselves too thin. We do need moar help, but it's not easy work!
Click to expand...
Click to collapse
I think even a larger minority among kernel-hacking devs... Do any of the kernel guys have 500s/400s?
Entropy512 said:
I think even a larger minority among kernel-hacking devs... Do any of the kernel guys have 500s/400s?
Click to expand...
Click to collapse
The guy that wrote the extUSB patch, ACL.
I think bzo has a 400 as well... To be honest, there's only a handful of active kernel devs. Some are more active than others as well .
I happen to have a RHOD500 and am particularly interested in getting this functionality working. I'm brand new to this smartphone/android scene and unfortunately I know ****all about how to do any of this. I do have some very rudimentary programming knowledge and a willingness to learn. If there is anything I can do to be of help in getting this feature working correctly, I'd be glad to help. Any suggestions on anything I could do to try to be of service?
SgtMac02 said:
I happen to have a RHOD500 and am particularly interested in getting this functionality working. I'm brand new to this smartphone/android scene and unfortunately I know ****all about how to do any of this. I do have some very rudimentary programming knowledge and a willingness to learn. If there is anything I can do to be of help in getting this feature working correctly, I'd be glad to help. Any suggestions on anything I could do to try to be of service?
Click to expand...
Click to collapse
With... the audio jack? It's all working now, other than the "advanced" feature headsets AFAIK.
SgtMac02 said:
I happen to have a RHOD500 and am particularly interested in getting this functionality working. I'm brand new to this smartphone/android scene and unfortunately I know ****all about how to do any of this. I do have some very rudimentary programming knowledge and a willingness to learn. If there is anything I can do to be of help in getting this feature working correctly, I'd be glad to help. Any suggestions on anything I could do to try to be of service?
Click to expand...
Click to collapse
http://forum.ppcgeeks.com/android-tp2/146375-mic-detection-3-5mm-rhodw-only.html
ACL is working on those advanced features arrrghhh mentioned. I don't know if you have both a extusb and 3.5mm headsets, or even if ACL needs more than just the one tester, but the above thread requests such testers. After that, ACL might be the one to talk to on aiding with 3.5mm code.
Thanks for the suggestion. I don't have any of that hardware he's looking to test. I got my RHOD500 second hand and the only headsets I'm using are standard headphones with no buttons or mic.
Related
Hi everyone. I, as many others, have been having an issue with my microphone cutting out during a phone call. I have a roooted Verizon Galaxy Nexus running the 4.0.4 leak, but it appears that for everyone who is having this issue it doesn't matter which ROM you're running or even if you're rooted or not.
[EDIT]: It per one of the posters below, this is not so much a "microphone" issue as it is an "outbound audio" issue. Unfortunately I can't edit the subject name to refer to this, but for me personally when I've been doing google searches on this issue the first word that came to mind anyway was the word "microphone" or "mic" anyway.[/EDIT]
People have been trying different things like flashing different radios, muting and unmuting, turning off voice privacy, etc., but it seems that nothing helps. Not even several hardware replacements or sim card replacements.
However, I did notice a pattern from different forums, etc. It seems that some people either have the problem all the time, or not at all, and it seems that some people reported that traveling to different metro regions affected whether or not they had the issue.
So I was curious to see if the pattern has to do with geographical location as an issue with Verizon's network, vs. hardware/software issues.
This poll has 50 possible answers, 1 for each state. Please answer this poll ONLY if you ARE experiencing this issue, and please only vote for your state if you live in the state's capital. For example, I live in the Denver metro area, so I would vote for Colorado. However, if I lived in Fort Collins or Grand Junction, I would NOT vote at all.
If you have traveled and visited another state's capital and have had this issue there, you can go ahead and vote for it as well.
It will be interesting to see if we have a lot of hits in certain major metro areas and none in others.
[EDIT2] Also, if you don't have the problem at all, go ahead and post a comment with your location. In fact, it would be interesting to see if people don't have the problem but others in the same city do. [/EDIT2]
Thanks!
I thought I had this issue just turns out my pinkie was covering the microphone its king of poor positioning watch, the way u hold the phone after changing the way I hold it no one complains they can't hear me
Sent from my Galaxy Nexus using XDA
TLDR: I kept having people telling me that I sounded like a robot.
Sent from my Galaxy Nexus using XDA
I had this problem on back to back to back phone calls this morning. Horrible.
Sent from my Galaxy Nexus using Tapatalk
My wife and I are both having the issue in Richmond, VA but I could only vote once for myself. She has reverted to an old droid x as she cant rely on the phone anymore.
Might be a little late, but maybe we should collect ZIP codes instead? Then we could use this tool: http://batchgeo.com/
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
I voted. I'm in South Carolina. I'm pretty sure it's NOT a regional problem though.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If holding the phone different worked for you, then you don't have the issue this is referring to. This issue can happen with a wired headset, Bluetooth headset, on speaker phone, which none of these would be affected by how you are holding the phone considering you aren't using the mic on the phone. The people on the other end hear a series of clicking sounds, then no audio.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
I had the same problem on my 2 rogers GNs(GSM version)
after I upgrade my baseband to i9250xxkk6, the problem gone
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
I'm in Raleigh, NC.
I got my phone on release day and noticed this problem a few days later. I've since replaced the phone, then the SIM card (a theory that it was SIM-card related was floated over at AF).
After changing the SIM card the problem seemed to go away for a couple of weeks, but it came back with a vengeance.
I hate the idea of getting a "refurb" from Verizon (I put refurb in quotes because, based on the FIVE refurb'ed Incredibles I had, I'm pretty sure they don't do anything except replace the glass if it's scratched), but I guess a functional refurb would be better than an aggravating semi-functional new phone.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Click to expand...
Click to collapse
I can't help but be reminded of Steve Jobs.... "You're holding it wrong!"
I'm glad your phone is working properly but, as others have noted, this is most definitely not the problem we're talking about.
gabe23 said:
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
Click to expand...
Click to collapse
Thanks for clarifying, I edited my original post, unfortunately I can't edit the subject name, but you're right, it's outbound audio and not mic. Thanks again!
adrynalyne said:
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
Click to expand...
Click to collapse
You're right, I was caught up in it at the moment and thought it would just be interesting to see how the issue maps out, but this little poll in no way is a troubleshooting tool, more of a type of infographic maybe?
The only fix is going to be a software update from el goog. can't wait for it!!!
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Flashing a new rom/radio does not help. I'm running nothing stock (leaked radios, CM9 Kang Nightly, Franco Nightly) and I still have this issue.
Good to know I'm not alone, Minnesota is currently winning! :-\ :-(
AnotherHiggins said:
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Click to expand...
Click to collapse
I was told the same thing by VZW support, but mid-march... which is NOW! I'm really getting sick of this. Ready for the fix and some info.
I have the same problem on the GSM version. Also Raleigh, NC.
It's a bit weird that all the decent ROMs are still on LJC, even after a few weeks with LK8 on the scene... Is there some valid reason for this, or is it simply because the GN2 development section is underwhelming compared to the GS3/etc?
Wifi issues, and until recently the inability to go back to older firmware mostly.
Interesting, I haven't seen any WiFi issues. Samsung devices always have crap radios, and LK8 seems on-par with the other releases.
Jellybomb, H20 and MIUI are great Roms and that's why they're on LK8. Hehe
Sent from my SPH-L900 using xda app-developers app
It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.
JellyBomb is great in function, but on every device I've ever used it on, the theming causes problems. Fonts covered, hidden, etc due to the blue. Guess I'll try it again.
Itchiee said:
It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.
Click to expand...
Click to collapse
This. And also simply because the devs don't want to work with a leak. Who would? Also I prefer few roms with less bugs than a variety with problems.
Sent from my SPH-L900 using xda premium
ScrapMaker said:
It's a bit weird that all the decent ROMs are still on LJC, even after a few weeks with LK8 on the scene... Is there some valid reason for this, or is it simply because the GN2 development section is underwhelming compared to the GS3/etc?
Click to expand...
Click to collapse
LJC works with fewer issues more often for more people than lk8. Many devs stick to it because of all the bugs that stem from lk8.
Sent from my SPH-L900 using Tapatalk HD
I know a lot of devs only upgrade to official releases and newer doesn't always equal better as well
-TeaM VeNuM Like A Boss
-Galaxy Note II Edition
Itchiee said:
It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.
Click to expand...
Click to collapse
Compared to my HTC Evo series (any of them,) I'd say it's pretty obvious all the radios are quite inferior. That's good information that this firmware might contribute to that though. Thanks!
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
The Chameleon bug played a big role I think in people avoiding upgrading to LK8. While it didn't seem to cause any real damage, it was annoying as hell not only for the user experiencing it, but also the devs and other members having to see issues and questions related to it constantly. The bug has been squished, but I think the fear still lingers lol
thunderwagn said:
The Chameleon bug played a big role I think in people avoiding upgrading to LK8. While it didn't seem to cause any real damage, it was annoying as hell not only for the user experiencing it, but also the devs and other members having to see issues and questions related to it constantly. The bug has been squished, but I think the fear still lingers lol
Click to expand...
Click to collapse
I was one of the early catchers of that bug, and was vocal about getting some dev involvement. At the time it was a permanent error, and a pain in the a$$, I had the choice of LJC with HFA/chameleon FC errors (permanent, no matter how it was wiped back to stock), or no wifi.
Thanks to Garwynn, EvilKoncepts, a pal that did testing for them (can't remember his name), there is now a verified fix for it. (Has to do with LK8 changing carrier partition).
So right, most devs don't want to mess with leaks for official releases.
I won't touch it, at least not for now. LK8 has some nice little features, but I'll hold out for a bit, hope a (better? official?) version gets posted by Sammy for SxTp to bring us.
personally i havent seen any "bugs" in lk8. i've never had wifi problems and most everyone who has ran ProjectROM hasnt either. if you build off a stable base the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.
t3project said:
... the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.
Click to expand...
Click to collapse
normally, I might agree with you, having seen most issues caused by user negligence/ignorance. and fixed by proper procedure being used to reapply a ROM/Odin a stock. but in my (and several others) case, this was on Stock rooted, with the SxTp Stock leak applied. Wifi died for no reason after aprox 24 hrs use. No amount of wiping/resetting to fact-default would fix it.
But going back to LJC did, while bringing other (well documented) problems with it.
t3project said:
personally i havent seen any "bugs" in lk8. i've never had wifi problems and most everyone who has ran ProjectROM hasnt either. if you build off a stable base the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.
Click to expand...
Click to collapse
The only real bug I've found in lk8 is the wifi issue, it seems to not like certain wifi frequencies or channels, as it will connect to some routers but won't connect to others. Could possibly be an issue with the wifi supp or wifi conf files. The other big issue is the carrier partition upgrade in lk8 causing issues when going back to ljc
I like to break stuff!
I try any and every new firmware update with the HOPES AND PRAYERS that Samsung will fix their effin' horrible Bluetooth stack... worst of any device I've ever used. CM10 fixes it, but right now that's not a viable option, especially since I like having the SPen...
I hate that when I have my headphones plugged in, sounds still blurt out the speaker... wtf?
When I'm in the car with the headphone jack connected to my aux port, and the BT set to hands-free to my OnStar, I have to yank the audio cable out while driving just to answer. Pretty stupid. HTC, Palm, Motorola, etc all have this figured out, but not Samsung. All their Android smartphones do this.
ScrapMaker said:
I try any and every new firmware update with the HOPES AND PRAYERS that Samsung will fix their effin' horrible Bluetooth stack... worst of any device I've ever used. CM10 fixes it, but right now that's not a viable option, especially since I like having the SPen...
I hate that when I have my headphones plugged in, sounds still blurt out the speaker... wtf?
When I'm in the car with the headphone jack connected to my aux port, and the BT set to hands-free to my OnStar, I have to yank the audio cable out while driving just to answer. Pretty stupid. HTC, Palm, Motorola, etc all have this figured out, but not Samsung. All their Android smartphones do this.
Click to expand...
Click to collapse
I don't have any issues with BT or audio over the 3.5mm jack. Although I don't have BT in my car I use a headset while I'm working and will have headphones on in the other ear and it switches back and forth just fine
I like to break stuff!
I've never once had that work properly with the stock firmware, or even custom ROMs, (aside from AOSP.) If I have BT attached to hands-free only device, and playing music over 3.5mm connection, it will continue to play over the 3.5mm despite having the BT attached. Maybe something changed in LK8 that I didn't pay attention to. This holds true for the S3, S2, and GN2 that I'm aware of.
ScrapMaker said:
I've never once had that work properly with the stock firmware, or even custom ROMs, (aside from AOSP.) If I have BT attached to hands-free only device, and playing music over 3.5mm connection, it will continue to play over the 3.5mm despite having the BT attached. Maybe something changed in LK8 that I didn't pay attention to. This holds true for the S3, S2, and GN2 that I'm aware of.
Click to expand...
Click to collapse
I'm using ljc. Was stock but I've been building my own rom off of the stock OTA and haven't even messed with anything BT or audio out related and have no issues. Maybe it has something to do with your BT device itself, perhaps it and the phone aren't communicating properly after its been idle for a while. I had an old Motorola BT headset that would go idle/sleep and never wake up unless I pressed a button on it so I'd have to answer the call with the phone then press the button on the headset to switch over
I like to break stuff!
I love nearly everything about my Verizon G'Nex, except for the fact that it sucks as a telephone. Voice quality is mediocre, at best, when the phone actually works. Meanwhile, my mic will typically mute itself in mid-conversation leading to "can you hear me?" and "you're hard to hear!" exchanges.
I have tried multiple ROM's and Radio's, including the latest stable CM and the latest stable AOKP. Each flash was clean, as I don't like taking chances with a dirty flash.
I have tried the app "SoundAbout," and the Wired Headset Detection setting is on "IGNORE Plug In/Out Detection (helps if phone is sending invalid plug in/out signals that shut off the speaker/mic)."
I have searched high and low on messageboards (XDA, Androidforums, etc.) to find a solution with no success. It seems that the problem either disappeared for most people and/or people have moved onto other phones. Literally, most threads and posts are from late 2011/early2012.
Issue happens whether I am home, away at work, or in a random parking lot somewhere. Contrary to popular belief, I don't think it is location-related, but rather, is hardware related.
I have 4G turned off.
Does ANYONE know if a fix exists?
On another related note, I am considering picking up a used SGIII from Swappa. I have to go the Used route since I want to keep my Unlimited Data Plan for as long as humanly possible. Does the SGIII have the same mic mute issues? Are there any other poweruser used phones that I should consider?
Comp625 said:
I love nearly everything about my Verizon G'Nex, except for the fact that it sucks as a telephone. Voice quality is mediocre, at best, when the phone actually works. Meanwhile, my mic will typically mute itself in mid-conversation leading to "can you hear me?" and "you're hard to hear!" exchanges.
I have tried multiple ROM's and Radio's, including the latest stable CM and the latest stable AOKP. Each flash was clean, as I don't like taking chances with a dirty flash.
I have tried the app "SoundAbout," and the Wired Headset Detection setting is on "IGNORE Plug In/Out Detection (helps if phone is sending invalid plug in/out signals that shut off the speaker/mic)."
I have searched high and low on messageboards (XDA, Androidforums, etc.) to find a solution with no success. It seems that the problem either disappeared for most people and/or people have moved onto other phones. Literally, most threads and posts are from late 2011/early2012.
Issue happens whether I am home, away at work, or in a random parking lot somewhere. Contrary to popular belief, I don't think it is location-related, but rather, is hardware related.
I have 4G turned off.
Does ANYONE know if a fix exists?
On another related note, I am considering picking up a used SGIII from Swappa. I have to go the Used route since I want to keep my Unlimited Data Plan for as long as humanly possible. Does the SGIII have the same mic mute issues? Are there any other poweruser used phones that I should consider?
Click to expand...
Click to collapse
No one, eh?
I had the problem when my Nexus was on 4.0. When I was updated to 4.2 (stock) the problem went away.
I'm assuming it had more to do with the radio updates then then ROM update.
Sent from my Galaxy Nexus using xda app-developers app
I'm on the latest CM which is 4.2.2, and it uses the latest radios, too.
The only other thing I can think of is that my headphone jack might be triggered due to tiny pieces of lint. However, the "SoundAbout" app should be ignoring the jack to begin with.
(Trust me, I'd rather keep the G'Nex rather than spending $300-$400 on a used SGS3, but that seems like the only option considering I can't hold phone conversations anymore).
Sent from my Galaxy Nexus using Tapatalk 2
Please pardon me if this has been asked before, or if it's really a very stupid question: Is it possible that simply rooting an otherwise stock HTC One M8, GPE, running Android 4.4.4, and installing TWRP and SuperSU, could cause bluetooth failures?
I ask because I heard that from a support tech whose company manufactures a bluetooth car kit I've installed, and the gadget in question intermittently fails to start up properly. I can pretty accurately predict the probability of a successful start up by knowing how long the vehicle's ignition key switch has been off. If it's been an hour or more the gadget will amost always start up properly, but if it's been less than ten minutes it'll almost always fail to start up properly. After it fails, I can just leave everything off for an hour and it'll work just fine, most of the time. It really doesn't seem logical to me that the phone could be implicated, given the strong correlation of off time to success probability, but the world is weird so I'm asking.
I've a bluetooth headset and a bluetooth OBD-II adapter that both work flawlessly with this phone.
Rooting the phone itself wouldn't affect bluetooth.
Changing to GPE 4.4.4 again shouldn't affect bluetooth in the manner you are talking about as it was made for that phone.
Bluetooth issues usually come up when problems exist in the ROM you are using.
I can't imagine the scenario you are talking about will have any issues.
Someone else might explain it better than me though.
Did the device work properly before you rooted?
As mentioned, simply rooting the device is unlikely to have cause such a problem. Bluetooth compatibility is complicated issue. The Bluetooth "standard" is not as standard as you would hope. Given the sheer number of possible device combinations, some combinations just don't play well together.
redpoint73 said:
Did the device work properly before you rooted?
Click to expand...
Click to collapse
The device in question being the car kit? If so, I can only say that the phone predates the car kit so I don't know. If the device in question is the phone, it's working fine even now with two different bluetooth headsets and a bluetooth OBD-II (automotive on-board diagnostics) adapter.
Frankly, I believe that the support drone is a charity case of some kind, maybe the sales manager's recalcitrant kid or something like that. He's obviously just making things up as he goes along, but the one thing he's said that I can't easily disprove is the line about rooting the phone somehow annoying the aftermarket car kit device hiding behind my vehicle instrument panel. When it comes to phones I'm just a clueless luser and won't pretend otherwise, but I figure there are plenty hereabout who are perfectly clueful.
Thanks!
HappyHeathen said:
The device in question being the car kit? If so, I can only say that the phone predates the car kit so I don't know. If the device in question is the phone, it's working fine even now with two different bluetooth headsets and a bluetooth OBD-II (automotive on-board diagnostics) adapter.
Click to expand...
Click to collapse
I was thinking whether the phone worked with the car kit before you rooted the phone. But as you just stated, the phone predates the car kit, so no way of knowing that. Somewhat a rhetorical question, really. I seriously doubt rooting would have any effect.
Support techs are probably just programmed to say such things. Once a phone is rooted, they have no way of knowing what you did to it, and if it might have affected something on the phone. But root itself is just a permission change, it isn't going to affect the functionality in itself.
Don't know if the Bluetooth stack for Sense ROMs or AOSP ROMs (CM11, SlimKat, etc.) are any different from GPE. You will need to convert the partition layout to flash a Sense ROM (and AOSP ROMs?).
redpoint73 said:
Don't know if the Bluetooth stack for Sense ROMs or AOSP ROMs (CM11, SlimKat, etc.) are any different from GPE. You will need to convert the partition layout to flash a Sense ROM (and AOSP ROMs?).
Click to expand...
Click to collapse
I'd rather remove the car kit and smash it with a sledgehammer than futz around with reflashing the phone with ROM images I don't otherwise need. The sledgehammer is already on standby. :laugh:
While Lineage O.S. seems to do most things as it should, there also seem to be some things that, for lack of a better way to put it, just don't seem to work. This could result from defective hardware, defective software, or defective user issues. This is intended to be a place to post inquiries about stuff that doesn't seem to work properly. If it is defective hardware, well, there's probably not much we can do for you here. Defective software? Perhaps the Lineage OS team or your app developer might see something here to put onto the to-do list. Defective user? A friendly: "Cool. Someone told me how to fix it without telling me I was a complete doofus" can go a long way to improve one's day, at least in my humble opinion.
Video in Stock Messages app doesn't work properly
On d2vzw (Verizon Galaxy S3) running OctOS 7.1.1 (LOS 14.1)
Pictures work fine, but when I try to record a video mms it freezes the camera, and when I receive a video mms from someone all I can play is the audio part. Pictures work fine; just the video has issues.
Would love to hear if others experience this as well or if I'm on the Crazy Train... :silly:
Device info ?
It seems likely that a lot of issues are going to be device specific, so it would be useful to include info such as what device you have and, if you aren't using the current LOS build, which one you are using. For instance, I've not had that particular problem on my LOS device(s), but one of my not yet changed devices did with the factory build (go figure). OEM supplied a new messaging app and the problem went away.
nezlek said:
. Defective software? Perhaps the Lineage OS team or your app developer might see something here to put onto the to-do list. .
Click to expand...
Click to collapse
I think this is to optimistic. Have you seen how restrictive devs are with bug reports? Maybe it's faster to start building LOS yourself.
kurtn said:
I think this is to optimistic. Have you seen how restrictive devs are with bug reports? Maybe it's faster to start building LOS yourself.
Click to expand...
Click to collapse
I do have to agree with you, but one can always hope. And if folks never make problems known at all, we can't expect others to be clairvoyant. :angel:
I also don't necessarily disagree with the restrictions. It is tough enough to expect people to work for you basically for free, let alone with absolutely no structure imposed on how to define their tasks.
Unfortunately, some issues just don't fall conveniently into the structure for bug reporting. I've been trying to observe ANY pattern to my LG tablet with 14.1 randomly dropping Wi-Fi connectivity despite every settings change one could make. It is an annoyance rather than a deal breaker since it only seems to drop the connection when idle (at least so far). There is also an annoying little glitch about randomly forgetting the wallpaper I've selected, but if those are the things I have to put up with to have something better than an unsupported 3-year old Kit Kat build on the device, I am willing to do so and hopefully one of these days those two little problems will get fixed. If someone who reads this says: "oh yeah, I had that problem, too, you just have to ....." all the better. If it takes coding skills, hopefully one of these days I will get there.