Develop Bugs

audio jack

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.

For those with concerns about getting a Galaxy Nexus

Well, i took the plunge today, and went out and got one sim free. I had concerns that the gps would be a bit naff, and that there may be screen defects, or sluggishness and all the other commonly complained about things on here. However, in reality, non of these things were evident. It just goes to show that sometimes you can read too much and put yourself off buying a device on these fora. Which I nearly did. So, i'm really pleased with mine, screen is just great, gps is very good, not noticed a great deal of lag, just little hiccups here or there maybe, but that's it. Certainly nothing more than i got from my iphone 4 when it's ram was a bit pushed. So, if you think you might be put off, don't be, it's just great

+1 i have the same experience with my VZW GN. A hickup here and there, the AMOLED screen has the linen appearance with whites on low brightness, but overall I'm happy with it.
My colleague's did burn through a lot of battery this morning, but I just unlocked and rooted it for him so we will see if this was something he installed.

+1 excellent device
Sent from my Galaxy Nexus using xda premium

I disagree with the OP.
My Nexus while at first seemed great actually has a few issues that are making me second guess my decision to return my Razr.
1. When switching from Wifi to 3g/4g my data stops working. I have to switch to airplane mode then back to restore it.
2. The speaker phone is aweful. While in the car its completley useless. I spend half of my conversation repeating myself becuase the other person can't hear me. I did a comparison with my wife Incredible and it was night and day.
3. When typing on the keyboard I notice that they keys being registered are not the keys I am pressing. Not all the time but on average its worse than the razr. The upside of this is that the autocorrection of ICS fixes the mistakes so its a wash in the end but still annoying.
4. MTP file transfer fail often when transfering files. I ended up using a wifi ftp server to get my titanium backup files.
5. Audio breaks up when trying to stream over bluetooth. Worked flawlessly on my Razr.
The last two are not so much bugs as design limitations.
6. No SD slot...I mean really... why can't nexus phones have sd cards.
7. No voice search button with the rest of the "buttons"

This is kinda what i meant, these problems seem to be device specific. Generally, they are ok, but as was the case with the sgs2, the early batches seemed dubious and the software was full of bugs. If you are lucky tho, (as the majority will be). All will be fine.

Forgot about the bluetooth audio streaming issues. Updated my post with that as well.

So far I've had no problems with Bluetooth audio either. Although I have not tested it extensively. Only tried it out to check it.

trevoryour said:
Forgot about the bluetooth audio streaming issues. Updated my post with that as well.
Click to expand...
Click to collapse
Ooooh Please can you elaborate on this. BT/A2DP Streaming is essential for me.

Seems like ICS gets faster as you use it more. Also, most apps are not totally designed for ICS; Yet.

I would say I am more likely to share a bad experience post on the internet than a good one. I am sure there are a lot of people who are happy with their device that just don't feel the need to say so online.
I agree with the OP. You should always give something a go and if it don't work out there is usually a warranty.
Sent from my Galaxy Nexus using XDA App

I agree with the OP, most of my fears about the phone have not come to life. No problems with the signal, although if there is a fix, I hope that it will help when I am at work. zero ****ing bars..why is every place I work at built like a bomb shelter with no signals coming thru???
i have faith someone will make a bigger battery for this thing...

cenwesi said:
Ooooh Please can you elaborate on this. BT/A2DP Streaming is essential for me.
Click to expand...
Click to collapse
I tried streaming spotify over the bluetooth audio link in my Ford Sync and the audio stream kept breaking up as if the phone was really far away or something. I had seen this before with my Incredible when it first came out but a reboot usually fixed it. I rebooted the nexus and the problem remained.

I also agree with OP, this phone has been perfect before. I was espeically surprised with the GPS lock i was getting. with my Charge i had to go outside and stand still for like 30 seconds to a minute to get it to lock on, the Nexus locked on almost instantly sitting in my chair inside my house...

Clearly all of these issues are luck of the draw. My phone has had no such issues. I suppose some phones having these issues and others not might indicate lesser build quality, but even iPhones have hit and miss problems like this.
Sent from my Galaxy Nexus using XDA App

[Q] POLL: Verizon Galaxy Nexus In-Call Microphone Issue - Location Map

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.

Mic Mute/Cut Out Problem Still Exists!

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

Future of Pixel XL

Hey
So I'm pretty confident this is going to be my next phone most of the reviews have been favourable and Googles support in terms of updates ect is a big deciding factor.
Just wondering what this community's thoughts are in terms of community dev for the Pixel? I understand is very early days so far so please dont jump on me. I'm just curios if we are expecting this phone to have similar support here like the Nexus devices did? I'm a flash-a-holic however when I got my Note4 here in the UK, somehow I got the C (Exynos) variant where else almost every other Note4 I've seen here in the UK has been F (SD805) so I've missed out on a lot of Non-Samsung rom's for the last couple of years, before that I was spoiled for choice with my S3, and I'd very much like to get back to flashing several times a week playing around seeing what I like and what I don't like.
Anyway again, I know it's early days and it's hard to predict the future but some opinions are best guesses would be really helpful to make my decision and hopefully get what I want from my device this time....
Happy Pixeling

The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.

I haven't had any issues with my Pixel XL? Maybe because I haven't upgraded to 7.1.1?
Samsung phones are slow and sluggish as all getout IMO.

I have no bugs, great battery life, and the phone flies. Best out of the box experience I ever had. With that being said, I to, hope development picks up. Think with the dual partitions, and phones lack of availability is part of culprit. Once those two things straighten out, well this is a nexus except for the name

No bugs to report here. Everything has been flawless so far.
Development WILL pick up. The Nexus 5X sold at half the price of this phone and it still took a few months for development of truly custom ROMs and kernels to get into high gear.

I have been loving the phone. I got mine at launch and have had very little issues. Everything is fast and stable.

nabbed said:
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
Click to expand...
Click to collapse
I've had zero issues with mine on 7.1 or 7.1.1, have you tried a reset? I know 5 other people with the Pixel and they all love it and have had no problems.

nabbed said:
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
Click to expand...
Click to collapse
Sounds like you have a lemon. Had a black 32gb and upgraded to a silver 128gb because I had run out of space. Both had no issues. I'm actually amazed at the speed and smoothness of the overall user experience.
I had an LG V20 right before I traded in the 32 for the 128. It was very underwhelming. Although I appreciate the larger screen real estate, it's quality just wasn't on par with the Pixels. Colour uniformity issues and general graininess. Also found 2 dead pixels. As well, LG's skin over nougat felt very dated. The hardware, while impressive and very well put together, was very clunky. The Pixels hardware takes a backseat to the fantastic software.
Sent from my Pixel XL using Tapatalk

I am sorry to hear you are having so many problems. I have 128GB XL from the google store and do not have the problems you are having. I know that does not help you, just thought I would mention it.
nabbed said:
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
Click to expand...
Click to collapse

No bugs at all. Dunno what phones hes using

I haven't seen any bugs either, dnd works flawless, haven't had any issue with Bluetooth, nothing has force closed at all. I do notice my Nexus 6 had a tad bit better service at my house (~3-5dBm). But the funny thing is that my n6 always had higher cell standby use on my battery.

To make it short.
no bugs, great battery ( much better as my Angler ).
Great Device

Love this device. Just got it Tuesday. No bugs that I've seen yet. Went right to 7.1.1 after unboxing so I can't speak to 7.1. I've used bluetooth for car audio, a speaker in my apt, connection to my huawei watch, and wireless headphones for running and have yet to experience an issue with that. No problems on T-Mobile here in LA either. Dont' use DND so can't speak to that. But overall very happy with my purchase!

airmaxx23 said:
I've had zero issues with mine on 7.1 or 7.1.1, have you tried a reset? I know 5 other people with the Pixel and they all love it and have had no problems.
Click to expand...
Click to collapse
Well, you see, if you don't use features then there will be no problems with them.
Bluetooth - many people have reported that the phone would automatically connect to a bt car kit but it would be in the state of "Connected (no phone)." When you manually reconnect from the bt Settings menu it would work just fine. That's a bug. It may have something to do with a particular car kit, but I tried 3 - Motorola Roadster 2, Jabra Freeway, and a Jarbra Talk bt headset. All 3 started acting up this way after 7.1.1 update.
Do not disturb mode turn itself on occasionally during the day, even though it's set to turn on only at night hours. Someone has suggested that this particular bug had to do with an Android Wear smartwatch being connected, as this doesn't happen when the watch is disconnected. I wish they would fix that.
Project FI just straight up disconnects sometimes for no reason even though I have 3 partners in town US Cell, Sprint and T-Mob. So this bug is probably due to switching to a different carrier, even though US Cell has -60-80 dB signal strength everywhere, and in principle, the phone should stay connected to it all of the time.
And when I try to fix Bluetooth issues and play in the settings menu, Google Play Services sometimes just crashes. It's probably related to the bt bug.
None of these are major issues, but they are annoying, especially bt because I use it all of the time.

nabbed said:
Well, you see, if you don't use features then there will be no problems with them.
Bluetooth - many people reported that the phone will automatically connect to a bt car kit but it would be in the state of "Connected (no phone)." When manually reconnect from the bt Settings menu it would work just fine. That's a bug. It may have something to do with a particular car kit, but I tried 3 - Motorola Roadster 2, Jabra Freeway, and a Jarbra Talk bt headset. All 3 started acting up this way after 7.1.1 update.
Do not disturb mode turn itself on occasionally during the day, even though it's set to turn only at night hours. Someone has suggested that this particular bug has to do with an Android Wear smartwatch being connected, as this doesn't happen when the watch is disconnected. I wish they would fix that.
Project FI just straight up disconnects sometimes for no reason even though I have 3 partners in town US Cell, Sprint and T-Mob. So this bug is probably due to switching to a different carrier even though US Cell has -60-80 dB signal strength everywhere, and in principle, the phone should stay connected to it all of the time.
And when I try to fix Bluetooth issues and play in the settings menu, Google Play Services sometimes just crashes. It's probably related to the bt bug.
None of these are major issues, but they are annoying, especially bt because I use it all of the time.
Click to expand...
Click to collapse
I'm not seeing any of these issues. I use Bluetooth all day and my Moto 360 lives on my wrist. My T-Mobile signal in Boston is way better than it was with my 6p. I have never had dnd turn on by itself and I've had the phone since launch.

toknitup420 said:
I'm not seeing any of these issues. I use Bluetooth all day and my Moto 360 lives on my wrist. My T-Mobile signal in Boston is way better than it was with my 6p. I have never had dnd turn on by itself and I've had the phone since launch.
Click to expand...
Click to collapse
That's why they are bugs and not design decisions. They show up for some people but not others. Maybe it's a combination of apps or a combination of settings that are different between our phones. But all of these people who reported them, they aren't imagining these things. Please at least acknowledge that.

nabbed said:
Well, you see, if you don't use features then there will be no problems with them.
1. Bluetooth - many people have reported that the phone would automatically connect to a bt car kit but it would be in the state of "Connected (no phone)." When you manually reconnect from the bt Settings menu it would work just fine. That's a bug. It may have something to do with a particular car kit, but I tried 3 - Motorola Roadster 2, Jabra Freeway, and a Jarbra Talk bt headset. All 3 started acting up this way after 7.1.1 update.
2. Do not disturb mode turn itself on occasionally during the day, even though it's set to turn on only at night hours. Someone has suggested that this particular bug had to do with an Android Wear smartwatch being connected, as this doesn't happen when the watch is disconnected. I wish they would fix that.
3. Project FI just straight up disconnects sometimes for no reason even though I have 3 partners in town US Cell, Sprint and T-Mob. So this bug is probably due to switching to a different carrier, even though US Cell has -60-80 dB signal strength everywhere, and in principle, the phone should stay connected to it all of the time.
4. And when I try to fix Bluetooth issues and play in the settings menu, Google Play Services sometimes just crashes. It's probably related to the bt bug.
None of these are major issues, but they are annoying, especially bt because I use it all of the time.
Click to expand...
Click to collapse
1. Never had any B/T issues.
2. I have had that issue but it turned out to be the phone turning on in my pocket. Other things would turn on too like Flashlight and hot spot. My phone digitizer is just too sensitive. I can almost wave my hand over it to make selections. I also have a Huawei watch and dont feel this has any impact at all. I did chang to the Microsoft lock screen to minimize this (and its nicer than stock and works with fingerprints). But I dont consider my revision of your issue a bug. More like something is just too sensitive on my phone. Which you could turn down the sensitivity.
3. Dont know anything about that.
4. Yes, I can confirm I was doing something with connectivity in the Settings menu and it crashed. This happened on all versions since release. I dont quite recall what I was doing. But yes, I confirm this bug as well.

Well I'm glad I read this thread.
The "Do Not Disturb" bug has been bugging the heck out of me.
Never bothered to check if it was happening to anyone else.
"Someone has suggested that this particular bug had to do with an Android Wear smartwatch being connected"
No Andoid Wear here.
And I always disable the screen wake motion/tap features to prevent my phone screen from turning on when in my pocket. I hate it when that happens and then you notice flashlight through your pocket or pull your phone out and all sorts of freaking apps have opened up and are pissed.
Otherwise, other than lack of development and the huge chins on this phone and the sucky speaker it's been the best phone I've ever had.
Dirty Unicorns is prepping to drop their first XL ROM so my development issues will be resolved with that and the eventual release of Xposed for Nougat.

I seem to have kinda fixed the bt bug by doing something interwebs suggested, Reset Network Settings. I can now work the Jabra headset and will have to try and test the bt car kit tomorrow. But boy, is it simply buggy just trying to troubleshoot this thing! Multiple times after the reset, the bt headset would connect to the phone and be in the normal state "Connected" but would have the "phone audio" feature disabled in a radio button inside the bt device settings. And tapping on the radio button to enable it would do nothing! That was new, never seen that before.
Then I would click the bt on/off switch from the notification pulldown menu, until the thing got stuck in the on position. After a reboot, bt was actually off. I enabled it and finally bt was working.
I got sick of troubleshooting and testing it, so that's where I stopped.
---------- Post added at 06:55 PM ---------- Previous post was at 06:51 PM ----------
CZ Eddie said:
Otherwise, other than lack of development and the huge chins on this phone and the sucky speaker it's been the best phone I've ever had.
Click to expand...
Click to collapse
You should have seen Note 7. It was unlike any new phone before. I've had like 15 flagships on their release, and Note 7 was super special.
RIP!

nabbed said:
You should have seen Note 7. It was unlike any new phone before. I've had like 15 flagships on their release, and Note 7 was super special.
RIP!
Click to expand...
Click to collapse
Fugg Samsung and their lack of developer support and locked bootloaders.
I had every Samsung Superphone since the Galaxy Skyrocket and will never buy another one.
I do support Samsung otherwise though.
They employ thousands of people here in Austin, TX and are sinking Billions of dollars into the local economy. :good: