Database Info

MHL adapter and signal loss

I am using clean ROM 4.0 DE and when I try to use my MHL adapter I lose signal on my phone everytime. Not only do I lose signal but when I try to just display a movie that I have on my phone, it freezes and wont play. I checked to see if the movie paused but it didn't. I can do everything else (as long as a data connection isn't required). I have not tried via wifi but that really doesn't matter much cause I don't have wifi where I am lookign to use MHL. Is this a ROM issue or a known issue with the HOX and MHL. I had the same issue on r113 or the Nocturnal ROM as well.

Is it an OEM HTC MHL adaptor? Or a third party brand?
Sent from my GT-N700 using Tapatalk 2

Third party from amazon
Sent from my Nocturnal HOX

I get a really grainy, probably only 850x480 picture on mine. Same with my Evo 3D. Both are running ICS. The 3D was full 720/1080p out before updating.

Sorry to hear that. I just got this yesterday. And it really works! Sadly landscape mode doesn't work properly on cyanogenmod 9 so I went back to ARHD and have the full screen landscape setup. Good thing about this adapter is that It already has an HDMI cable builtin you can even pair it with this dock(btw I bought 2)..1 for work and 1 when at home.

JamesR913 said:
I am using clean ROM 4.0 DE and when I try to use my MHL adapter I lose signal on my phone everytime. Not only do I lose signal but when I try to just display a movie that I have on my phone, it freezes and wont play. I checked to see if the movie paused but it didn't. I can do everything else (as long as a data connection isn't required). I have not tried via wifi but that really doesn't matter much cause I don't have wifi where I am lookign to use MHL. Is this a ROM issue or a known issue with the HOX and MHL. I had the same issue on r113 or the Nocturnal ROM as well.
Click to expand...
Click to collapse
I'm using a 3rd party MHL adapter from MONOprice, about $10. I had this issue and realized it was due to the One X's screen timeout. I set power settings to display on always when charged, and it works fine. Try it.

Does anyone else feel like Kit Kat is a very buggy OS and not ready for release?

I love my new nexus 5. The hardware is amazing. But it stops there. Kit Kat is complete junk. Keeps on crashing. Things like YouTube doesn't even work correctly. My signal keeps dropping. So many features missing. It just feels like Google rushed in making the latest version. Anyone else feel this way?
Sent from my Nexus 5 using XDA Premium 4 mobile app

Nope. Everything works smooth and fast for me
Sent from my Nexus 5 using Tapatalk

99% of the time all is good BUT you know this is a NEXUS device?! We are the beta testers. There will be issues.

nope.. nexus 5 plus kitkat make the killer android experience..

Everything works well to me, no problems, i think that it's definitely better than JB 4.3.
I come from a Gnex.

I've actually found that apps like Facebook and anything that requires scrolling really works much more smoothly on the Nexus 5. In terms of the OS, I must say I haven't really enountered any bugs myself, apart from Google Services using up 30% of my battery.. but I think I have fixed that now. I am really happy, and so is my 41 year old mother that has one too :silly:

I've had none of those problems.

I too have yet to find a bug. I admit that I do expect bugs, but not really found one yet,.

everything very nice here thank you

My only issue with Kit Kat and the Nexus 5 has been with Location Reporting - other than that Kit Kat feels slick and polished. Haven't experienced anything you of the issues you complained about.

Overall it's been great. Very fast and smooth.
YouTube and Google Now are the only things giving me problems so far. Google Now is worse on KitKat for me.

No issues so far

I've no problems so far. It has captured bug reports at times, but for what I never checked. Feels like an upgrade to jelly bean for me.

Ben36 said:
Nope. Everything works smooth and fast for me
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Try doing a force media scan. I bet the process will crash...
Try changing radio bands via *#*#4636*#*# under phone information menu. i bet i will crash...
try selecting an mp3 as alarm ring-tone.. using the app best alarm you cant were as before with jelly bean you could...
try watching netflix without earbuds... you can barely hear it..!
the phone over heats when using wireless charging pads.
exchange processes crash all the time
spontaneous reboots galore
speakerphone sound just sucks
colors are washed out...
if its true that this is a phone for beta testers, the Google shouldn't market it for the main stream buyers like me. i just want a nice phone (hardware wise this phone is) that works...
returning the Nexus 5 today and going back to Samsung even if it costs double the money. My galaxy s2 lasted me around 3 years and cant complain about it...

jzsax1 said:
Try doing a force media scan. I bet the process will crash...- Never had to do this before
Try changing radio bands via *#*#4636*#*# under phone information menu. i bet i will crash... - That's been broken since 4.1 IIRC
try selecting an mp3 as alarm ring-tone.. using the app best alarm you cant were as before with jelly bean you could... - Using Sleep as Android I can select an mp3 just fine. Seems that app hasn't been optimized for 4.4. That isn't the phones fault.
try watching netflix without earbuds... you can barely hear it..! - No issues here
the phone over heats when using wireless charging pads. - Never used one
exchange processes crash all the time - I've had no crashes
spontaneous reboots galore - Never even had one random reboot.
speakerphone sound just sucks - Speaker is perfectly fine on my end. Coming from an S3, it's a huge step up
colors are washed out... - No, they're not. They're a more accurate reproduction than AMOLED panels or other oversaturated displays.
if its true that this is a phone for beta testers, the Google shouldn't market it for the main stream buyers like me. i just want a nice phone (hardware wise this phone is) that works...
returning the Nexus 5 today and going back to Samsung even if it costs double the money. My galaxy s2 lasted me around 3 years and cant complain about it...
Click to expand...
Click to collapse
Responses in bold. Maybe you should re flash the stock image and see if that fixes any of your problems. I have literally had NONE of the problems you mentioned. And this screen destroys the S3s in every single way.
piratefinn said:
I've no problems so far. It has captured bug reports at times, but for what I never checked. Feels like an upgrade to jelly bean for me.
Click to expand...
Click to collapse
That happens when you push vol up + vol down + power at the same time. There are a lot of issues with cases making this happen. Still trying to find a way to disable it.

ive had force closes. but whatever. it's a very nice phone.

No issue for now whit stock rom, very few FC with custom rom, fine by me

Not at all. Polar opposite. It's the most polished android os yet imo
NX5

Well, my issues are:
a) Screen wakes for no apparent reason from time to time. Cannot pinpoint a trigger.
b) Google Services using plenty of battery, as well as just last night, on airplane mode, 11% 'Device Idle' usgae in 7 hours.
c) Sound on video recordings is EFFED.
Other than these, overall I am happy. I am confident updates will fix these.

jzsax1 said:
Try doing a force media scan. I bet the process will crash...
Try changing radio bands via *#*#4636*#*# under phone information menu. i bet i will crash...
try selecting an mp3 as alarm ring-tone.. using the app best alarm you cant were as before with jelly bean you could...
try watching netflix without earbuds... you can barely hear it..!
the phone over heats when using wireless charging pads.
exchange processes crash all the time
spontaneous reboots galore
speakerphone sound just sucks
colors are washed out...
if its true that this is a phone for beta testers, the Google shouldn't market it for the main stream buyers like me. i just want a nice phone (hardware wise this phone is) that works...
returning the Nexus 5 today and going back to Samsung even if it costs double the money. My galaxy s2 lasted me around 3 years and cant complain about it...
Click to expand...
Click to collapse
not for beta testers per se... but nexus started as development phones and kinda a guide for manufacturers. samsung never followed that guide which has made the development communities rather frustrated, but why should they, samsung make cpu's that do more per clock cycle than the competition, unless you buy a usa phone where they just use the same processors as the competition.
samsung makes fantastic hardware. if i had an i9100 with nfc i'd be using it today with it's low res screen and all. perfect phone. not too big, and basically defined all phones after it, from nfc, to usb OTG, to mhl. it was a great phone then they went all crazy with the rom on the s3 and s4.
even the samsung nexus phones weren't quite what their own line were.
the nexus brand is a bare feature set that manufacturers can work from. and lg makes a pretty piss poor build quality (opinion, some say the same about samsung, those people are wrong of coarse ), but i like the feature set without it getting gimmicky (but s-beam is cool, makes more sense to use wifi with nfc being more of a trigger, android beam seems like they missed out on something pretty obvious.) it's not a bad phone but not a ground breaking device either. the screen does wash out with viewing angle more than some other lcd type screens but for $350 did you expect pixel density as well as a high qulity panel? and maybe you are used to amoled, i am, but i think the nexus screen looks as it should. the phone is delicate, the camera firmware needs work.. these are all true things. but some of what you describe is probably cause for an RMA. the speaker, that's a build defect. not all of them are like that and mine is as loud as any phone i ever owned (louder actually but i never had a "one") so there are 2 things you can cross out because they may take it under warranty. my phone doesn't over heat on my samsung Qi charger, it work perfectly, there is slight heating but that is expected for putting an inductive coil on osmetihng that contains metal parts... no overheating on mine, just comfortable warmth.... are you using a cheap charger? there is a communication standard that is part of QI and the phone regulates the transmitter output with feedback, it's possible that some of the cheap chargers aren't following the Qi standards. as far as the alarm app not working, well it's a new os, interfaces change, things break, deal with it untill the market place catches up. that's like upgrading windows and the printer stops working... if the phone reboots it may be a hardware defect, you should RMA the phone or i'm sure someone will buy it from you.

Prospective new s3 user here - root, tethering, ROM on 4.4.2?

I'm currently on a Moto x (2013), coming from a Galaxy Nexus. I switched because I needed a faster phone, and the GN hardware is just too dated. The moto x seemed perfect, until I found out I can't tether, root, or unlock the bootloader to save my life.
That being said, I'm in the market for a Verizon S3, which will likely already have 4.4.2 installed. My main concern is root access and native hotspot tethering (unlimited data). The following are what I have found thus far:
1) root: http://www.andromods.com/root-unlock/sch-i535-vzw-galaxy-s3-kitkat-rooted-nc1-ota.html
2) tethering: https://www.youtube.com/watch?v=PxBRrsucdLo <---- the guy who created the vid doesn't have VZN, so was hoping someone here can verify if that works.
3) bootloader: I found nothing on unlocking a VZN bootloader, but this is the least of my concerns
4) ROM: http://forum.xda-developers.com/gal...nt/rom-superliterom-v1-0-i535vrudne1-t2805797
My assumption was always that an unlocked bootloader was necessary to flash ROMs through custom recoveries. I'm unfamiliar with safestrap, but I'm all in for a bit of reading and enlightening.
Again, I don't necessarily need a custom ROM or bootloader. My main concerns are still tethering (main priority) and root access (second priority)
Thanks all, and I definitely appreciate any help at all!

rice923 said:
I'm currently on a Moto x (2013), coming from a Galaxy Nexus. I switched because I needed a faster phone, and the GN hardware is just too dated. The moto x seemed perfect, until I found out I can't tether, root, or unlock the bootloader to save my life.
That being said, I'm in the market for a Verizon S3, which will likely already have 4.4.2 installed. My main concern is root access and native hotspot tethering (unlimited data). The following are what I have found thus far:
1) root: http://www.andromods.com/root-unlock/sch-i535-vzw-galaxy-s3-kitkat-rooted-nc1-ota.html
2) tethering: https://www.youtube.com/watch?v=PxBRrsucdLo <---- the guy who created the vid doesn't have VZN, so was hoping someone here can verify if that works.
3) bootloader: I found nothing on unlocking a VZN bootloader, but this is the least of my concerns
4) ROM: http://forum.xda-developers.com/gal...nt/rom-superliterom-v1-0-i535vrudne1-t2805797
My assumption was always that an unlocked bootloader was necessary to flash ROMs through custom recoveries. I'm unfamiliar with safestrap, but I'm all in for a bit of reading and enlightening.
Again, I don't necessarily need a custom ROM or bootloader. My main concerns are still tethering (main priority) and root access (second priority)
Thanks all, and I definitely appreciate any help at all!
Click to expand...
Click to collapse
Root is still possible. Tethering *USED* to work on stock by using the FoxFi app. I haven't tested it in quite some time though. There's a limit for the free version, use it for testing though.
Sent from my SCH-I535 using XDA Free mobile app

I actually made the jump already. Sending this from my s3, boot loader unlocked, twrp, and running cm11.
Thoroughly enjoying this! Tether is flawless too

rice923 said:
I actually made the jump already. Sending this from my s3, boot loader unlocked, twrp, and running cm11.
Thoroughly enjoying this! Tether is flawless too
Click to expand...
Click to collapse
Do tell how. Especially if you did start with a Verizon galaxy s3 sgh-i535 that was not rooted and was running on stock Verizon Android 4.4.2

To clarify, I bought it set up this way. I knew clearly well that I wouldn't be able to get any of this with stock 4.4.2.
On the other hand though, the camera won't focus correctly when taking pics, and the charging is ridiculously slow. My only two complaints

rice923 said:
To clarify, I bought it set up this way. I knew clearly well that I wouldn't be able to get any of this with stock 4.4.2.
On the other hand though, the camera won't focus correctly when taking pics, and the charging is ridiculously slow. My only two complaints
Click to expand...
Click to collapse
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?

Rushead said:
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Click to expand...
Click to collapse
I remember seeing you around MWs FML thread! 5.0 is looking decent over there, so I'm very happy for them.
If you get the chance, I'd definitely recommend CM11. It make me feel like I'm running a nexus device again, except significantly faster than the gnex with a better camera.
Regarding the charging speed, I don't think it's a kernel issue. With the phone plugged in, I keep getting notifications that it's being disconnectedAnd reconnected spontaneously. I've done some reading and and it seems there is a bit of oxidation or hardware issue within the charging port. The port also requires soldering of the mother board to change. I've resorted to ordering some qi chargers[emoji106]
As for the camera, this seems to be an old issue of cm11. I flashed a camera fix zip, but to no avail. The focus issue seems to be problematic only at macro distances though. I can't find a fix besides touching to focus prior to taking macro shots

Rushead said:
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Click to expand...
Click to collapse
With 4.4.2 if that's what your referring to you can't change the kernel like those of us who are unlocked
From my CM11 S3

ShapesBlue said:
With 4.4.2 if that's what your referring to you can't change the kernel like those of us who are unlocked
From my CM11 S3
Click to expand...
Click to collapse
No, it's 4.1.2 I put her on Andy bonestock years ago and never touched it again.

Rushead said:
No, it's 4.1.2 I put her on Andy bonestock years ago and never touched it again.
Click to expand...
Click to collapse
Then yes there are several kernel options for fast charge. I know of lean kernel and ktoonsez off hand that are
From my CM11 S3

Don't want to start a new thread even though the title is irrelevant at this point, but was hoping someone could chime in regarding the camera auto focus issue. The camera focuses beautifully when I touch the screen, or when I allow it to autofocus. When I proceed to take the pic, it will try to focus again and take the pic right as it's completely blurry. This happens on both the stock CM11 camera and google camera.
I tried to flash the zip mentioned here http://forum.cyanogenmod.org/topic/85493-camera-wont-focus-cm11/ and nothing has improved.
Does anyone have any insight about this? These symptoms are identical to what many have mentioned in the thread above, so this is certainly not an isolated incident. Thoughts or input?

Who reads titles anyway?
I flashed Slim, and messed around with the camera a little, but I had wifi issues and am in the process of flashing cm11 11-09.
On Slim, the camera seemed to work fine. I took some "macro-esque" shots of text that came out pretty good (at least as good as the GNex, if not better).
I'll let you know how it fares with cm11...
So far, camera FCs on hitting the "No Thanks" button for location reporting.
OK, Camera is now functional (probably didn't wait long enough for the phone to settle on initial setup). The quality is mediocre. I'm still messing with it and will report back.

switching phones, want to keep/root the old Galaxy s3 as a lab/toy
Have an old Verizon Galaxy S3. Just got a new TMo Sony Xperia Z3 (which I am liking so far).
Will soon disconnect my Verizon service. Would like to root the S3 and use it wifi only as a experiment/toy thing, since there's no trade in value (cracked screen).
Possible? Cyanogenmod recommended?
I'm a total n00b at all this, and would steer totally clear of it for my main driver. But since I don't really NEED this phone anymore, thought this would be a safe way to dip my toes in. If I brick it in the process, no great loss.
Any advice or links would be much appreciated. Definitely want it to keep working as a wifi device and not brick once I cancel my Verizon service. Would be cool to be able to play with some of the fringier apps that require root. Those are my only requirements. Camera, cell service, etc all unnecessary. But do need wifi and don't want to create a big vulnerability to the rest of my home wifi network from this device once I'm done.
Thanks again!

evbb, depending on your current OS version, you might be able to root. If you are on the most current official OS, then you will likely just be staying with that.
Rushead, any update on how CM11 11-09 is going? If everything looks stable, I think I'll make the jump to that build.
Update about my charging times: The phone seems to charge at a normal rate if I use a 12V car charger made by Griffin (item does not specify amperage). I don't believe amperage has antying to do with my situation, as I've been yielding miserably slow charge times with the Nexus 7 (2.1 amp) charger. The phone is also very picky with cables. I've used 4 different AC adapters so far in different combinations with 4 different USB cables. I don't know what to think of my charging situation anymore...

When my wife had the phone it was extremely loose as far as cables went. I could use virtually any cable whereas my GNex is super picky.
I haven't had much time to mess with the camera yet. I'm using it as a WiFi device, too, so I can't comment on data, signal, etc. But so far it seems pretty stable. The battery drain is excessive imo. On standby for most of the day, battery was dead by 10pm. That's factory kernel.

For those looking for a decent tethering app there's one on sale, free on the Amazon app store. Easy Tether is the name of the app. It's free 11/14 & 11/15
http://www.amazon.com/s/ref=amb_lin...d_t=101&pf_rd_p=1973721462&pf_rd_i=2350149011
From my CM11 S3

rice923 said:
I've used 4 different AC adapters so far in different combinations with 4 different USB cables. I don't know what to think of my charging situation anymore...
Click to expand...
Click to collapse
You should try a very specific type of cable. The problem is the fact that you use a data cable at all. What I use is an aftermarket universal USB cable and it has the detachable tip for other phones. What this does is force the phone in "Charging (AC)" mode no matter what charger you use. Attached are 2 pictures to help identify exactly the kind of cable to solve your issue. I can charge my 7000 mah battery attached to my phone in 5 - 6 hours. A 2100 ah battery should be 1 - 2 hours with this.
Sent from my SCH-I535 using XDA Free mobile app

Some chargers identify as a USB hub rather than an AC adapter, and others do not. This is why on some chargers, it still charges slow. If ever the phone thinks it is on USB, it will not allow more than 650mah to pass through the cable. So even if you had a 10amp charger, it would not use that much if it identified as a hub.
Using the cable I mentioned removes the ability for any charger to send the identifier info to the phone. Reason? You are missing the data+/- cables that data is transmitted through. Only the +/-5v wires remain.
Sent from my SCH-I535 using XDA Free mobile app

But why would the phone have a constant disconnection and reconnection while being plugged in? That's the part that confuses me.
Regardless, I just received my qi charge in the mail! It's been pretty nice so far! I'm happy to answer any questions about it if anyone is interested

Rushead, wanted to give you a heads-up about the latest CM11 build I used. I clean flashed 11-15 and everything was great except for the camera, which consistently gave me a "cannot connect to camera" error. Otherwise, it seemed like a great build with some great options. I gave up and clean flashed 01-15. Camera is all great except for the autofocus issue mentioned before. GPS lock is great, and battery life is loads better than my GNex days.
Regarding my qi chargers, I am pulling a net positive charge of 315mA on my house charger (Nexus 7 2.1amp AC adapter). This is with the phone turned on, connected to Wi-Fi, screen off, and doing nothing.
My car qi charger is doing about the same. I ran the GPS with screen on (auto brightness) and the charger only charged the phone 3% in 2 hours with screen on and GPS running the whole time. I might switch the DC socket to the included one to see if I get better results.

Weak Bluetooth?

Anybody else experiencing a weak bluetooth connection with the S6? I'm losing the connection with my Garmin Vivosmart in places I've had no problem connecting with other devices. I'm curious about other's experiences on this as a search hasn't turned up much yet.

I have noticed this as well. I could walk pretty far away from my S4 before it would drop. With this S6, I only get a few feet away before audio gives out. Doesn't disconnect, just loses audio.
Also, random loss of audio from time to time, even when the phone is right next to my head.

Yeah I've noticed the same thing with my S6. At work I don't always keep my phone on me and with my M8 I could walk around the whole building without my G Watch disconnecting and with my S6 I can only get a few feet away before the connection drops.

Yes happening with my moto 360 it is annoying and hopefully will be fixed soon

Haven't had any disconnect issues, but for some reason connecting to my car stereo has been a nightmare. It takes like 5 tries before it actually connects.
Galaxy S6 (Verizon)

sd0070 said:
Haven't had any disconnect issues, but for some reason connecting to my car stereo has been a nightmare. It takes like 5 tries before it actually connects.
Galaxy S6 (Verizon)
Click to expand...
Click to collapse
I'm having issues with my car bluetooth too. It works fine initially, but every couple of days I have to delete my phone and re-pair it for it to connect again.

grim281 said:
I'm having issues with my car bluetooth too. It works fine initially, but every couple of days I have to delete my phone and re-pair it for it to connect again.
Click to expand...
Click to collapse
Same here, takes me 3 or 4 times to try to bluetooth sync with ford sync system. Yesterday it would sync then play for 30 seconds and pause play back. I don't know if its the phone or lollipop as alot of the problems I see are also happening on my nexus 9.

I'm getting sent a new one since I've been having these problems
Sent from my SM-G920V using XDA Free mobile app

sleightofhandus said:
Same here, takes me 3 or 4 times to try to bluetooth sync with ford sync system. Yesterday it would sync then play for 30 seconds and pause play back. I don't know if its the phone or lollipop as alot of the problems I see are also happening on my nexus 9.
Click to expand...
Click to collapse
I had Bluetooth issues on an old phone, and when I flashed different roms the issues were fixed. This leads me to believe that it's software related
Galaxy S6 (Verizon)

iowabowtech said:
Anybody else experiencing a weak bluetooth connection with the S6? I'm losing the connection with my Garmin Vivosmart in places I've had no problem connecting with other devices. I'm curious about other's experiences on this as a search hasn't turned up much yet.
Click to expand...
Click to collapse
Identical experience. With my S4 and my Nexus 9 I was able to literally get to the edge of my large yard before losing connection with my Vivosmart. Now I can't leave the room since getting my S6. I hope it's software and we can somehow change it, because it's ridiculously bad. I also have had to turn my BT off and back on three times this week because it would crash and refuse to talk to either my Vivosmart or my car. As soon as I toggle the BT on the phone it reconnects to everything. Seems to be triggered by starting my car (i.e. the BT car interface becomes available.) Never had either problem with the S4.

lilshooter said:
I'm getting sent a new one since I've been having these problems
Sent from my SM-G920V using XDA Free mobile app
Click to expand...
Click to collapse
Since so many people are having this problem, it's probably phone related and not just an isolated incident.

cybermage1 said:
Identical experience. With my S4 and my Nexus 9 I was able to literally get to the edge of my large yard before losing connection with my Vivosmart. Now I can't leave the room since getting my S6.
Click to expand...
Click to collapse
Yeah this is one of my only remaining complaints about the device. I can't use my Vivosmart for sleep tracking anymore...it disconnects/reconnects way too many times and the persistent vibes wake me up.
So honest question...let's assume it is fixable by software tweaks. What's the fix in that scenario? Reroute more power to bluetooth radio? Other?

iowabowtech said:
So honest question...let's assume it is fixable by software tweaks. What's the fix in that scenario? Reroute more power to bluetooth radio? Other?
Click to expand...
Click to collapse
Well I've seen a lot of threads online for other devices where an Android update affected bluetooth range. Obviously there's some sort of software control for this. I'm rooted, and I'm willing to try some things but I don't know where to begin. I'm not an OS / Kernel guy.

i wonder if its what it is connecting to as well as a problem with S6? i have the Motorola Buds headset and it has worked as expected giving me about 100 foot range when talking on it. i also have a 2013 Ram truck with Uconnect and have not had any issues and it connects right away and reads my text etc.. as it was doing with my Note 3 and ATIV.
i havent tried other devices but have a few like a speaker and will see as i use them if i have issues.

Haven't messed with Bluetooth that much on this phone, but I think wifi is a bit weak
Sent from my Verizon Galaxy S6 using XDA Free mobile app

I've had Bluetooth issues. Seems really short range.

Wifi is about the same as my LG G2, but BT is about half as far. I used to be able to get around 15m at work (lots of shelving) but now I'm lucky to get 5m before hearing static and starting to cut out. Sucks because BT is my main source of music at work.

Anybody had better luck after applying the new ota?

Bluetooth not working

Not sure if this is just my phone but bluetooth has not been working the last update of 7.1.2 and Android O the most recent version. When I toggle bluetooth it does not activate and i have tried clearing out the cache. Not sure if this is a software issue or possible related to hardware. I did have a good drop with my phone although nothing on the exterior appears damaged. Not sure if anyone else is experiencing the same thing.

Just RMAing the phone. It appears that it is only my phone doing it. Actually Google's customer service is really good. I'm glad I bought from them.
I had a Galaxy S4 from Samsung in 2013 and the battery ended up swelling and I called them for a replacement which they would not replace, but would thoughtfully sell me a new battery. Then they lost $5.3 billion from their Note 7 recall due to the battery and I was very happy and laughed.

Was this just the phone audio in your car by chance? I have a similar issue and have an open case with google about it.

marc.ientilucci said:
Was this just the phone audio in your car by chance? I have a similar issue and have an open case with google about it.
Click to expand...
Click to collapse
No it's definitely the phone. I have my Nexus 5x right now on 8.0 and it's working fine. Nothing wrong with the software.
I use Android auto as well and it's working fine. There's something wrong with the hardware component in the phone most likely. I have a 2017 Honda Civic
Did an RMA and sending it out.

mikeprius said:
No it's definitely the phone. I have my Nexus 5x right now on 8.0 and it's working fine. Nothing wrong with the software.
I use Android auto as well and it's working fine. There's something wrong with the hardware component in the phone most likely. I have a 2017 Honda Civic
Did an RMA and sending it out.
Click to expand...
Click to collapse
sorry - let me clarify my question. Was bluetooth media working and just not phone calls over bluetooth? I have a 2017 honda civic as well (LX version so a dumb head unit) and only having bluetooth phone call issues. I can play spotify and other stuff like youtube just fine.

marc.ientilucci said:
sorry - let me clarify my question. Was bluetooth media working and just not phone calls over bluetooth? I have a 2017 honda civic as well (LX version so a dumb head unit) and only having bluetooth phone call issues. I can play spotify and other stuff like youtube just fine.
Click to expand...
Click to collapse
No. Bluetooth would not activate at all so nothing worked. When i toggled the switch it would not turn on and scan for bluetooth. It appears that my situation was much significant as nothing worked. My replacement should be here tommorow. For your stock rooted set up did you just boot into TWRP then flash the latest SU ? Lately I've been running stock, so I don't know what the most recent form to root is for 8.0
Last time I rooted was like April or May of this year, but I just booted the TWRP image, flash TWRP, then flash SU

I've been stock rooted for some time but for the 8.0 update I rooted with SuperSU SRS3 via TWRP. Google had me actually grab a bug report and shoot it over to them along with information about the bluetooth radio manufacture of the car. I am cool with continuing to help them out. anyway, thanks for your feedback and i hope the new one works!

Got my new pixel replacement. It was the phone, I'm on the latest 7.1.2 update and it's working fine. The refurb looks brand new, you can tell it's a refurb by the charging port, but the rest of the phone is virtually new. No scratches on the glass or scuffs on the metal body. Compared to the current pixel I have with multiple long scratches along the front glass screen, even though it's a refurb its still in much better condition than my current Pixel.
I noticed my night light is super orange the screen is compared to my current Pixel. I think this is an issue related to earlier batches of the Pixel. It's just very orange with the night light but given the condition my current pixel is in, I'll still take it over my current one.