I've read quite a few comments that the Nexus 4 does have HD Voice, but could anyone confirm whether or not this is the case on 4.4.2 (stock)?
Me and the other half are both on 3 (UK), which supports the feature. I'm using a Nexus 5, and her a Moto G at the minute whilst I'm replacing the USB socket on the Nexus 4. At the minute, we both get the HD voice feature when calling each other, but the minute either I or her use the Nexus 4 it's just a standard call. I've seen a few reports and posts from around the time the phone came out confirming it did, but nothing more recently. I did see a very slight mention that it's been removed from the latest software but nothing to back it up and no follow up on it. So when I've replaced the socket I'm going to have a go putting 4.2 on there and seeing if it works then. I guess if it does it confirms it's been removed from the latest firmware and I'll have a look at custom roms, and if not I've either got a hardware issue or something else is amiss.
Related
Hi.
I'm new to Nexus 7 and after a short time using it I began experiencing some strange issue with the it. While surfing the web over WiFi (note that I'm using the first Nexus 7 with WiFi only) after a short time glitching lines appear on the screen (as shown on the image attached) and some loud white noise coming from the speaker. It's stuck like this for about 30 seconds and then reboots. After reboot, everything seems normal, till it comes again. It takes 15-30 minutes of surfing and I believe the time depends on the intensity of surfing. Seems like WiFi modem somehow affects the GFX driver.
Note that I was first running android 4.1.1 and recently updated to 4.2. Updated didn't fix the problem. I've rooted the device with "Nexus 7 root toolkit v.1.5". Note sure if the rooting affected it somehow, as I rooted the device on second or third day of use.
Anyone have an idea of what could be wrong or how I might fix it? Or it's HW issue and I should turn it to Google?
Thanks!
So I'm the first and only one with such problem???:silly:
I could be wrong here but that seems like more of a hardware(warranty) kind of issue. However, I had the speaker issue after flashing a custom ROM (sparks linario 4.2.1) and I had the speaker issue (along with a host of other bugs buts that's beside the point). I flashed stock and unrooted and the problem was fixed... I know it might not help your case but I thought ide let you know. Its possible the toolkit caused the issues and flashing back to stock and rooting with another method may solve your issue (that's what I would try). But if you end up sending it in under warranty for god sakes, unroot and relock your bootloader first! Otherwise Google probably won't honor your warranty.
Good luck friend.
Sent from my Nexus 7 using xda app-developers app
Does anyone else experience the sleep of death bug (akin to what happened with Netflix) after having connected your HDTV through Slimport for a short while? It seems to happen regardless of what I'm doing on my phone, just having it connected for a short moment will cause it.
This is on stock Android 4.3 (JWR66V), whereas it was working just fine for me on 4.2. My phone is rooted, but there's nothing running that requires root access while this problem occurs.
Also, I'm using the "official" Slimport adapter, i.e. the only one that existed for quite a while.
Would hate having to send my phone back in, but alas that's what I'll do if it's just affecting me.
I've the same issues since 4.3 Everything was fine before with 4.2.2. When i unplug slimport from nexus4 i cant activate display anymore.
This hapepns sometimes after cahring, too.
So i think your device is ok, just an 4.3 fault like many other bugs
Thanks for the reply. So I'm not completely alone with this!
But I do find it odd that I could not find any existing discussion of this topic elsewhere on the net.. are there just not that many people making use of the HDMI feature or is the majority of people simply unaffected by this problem?
I'm not sure. I've the same issue with charging. I misspelled this on my first post. Same situation, unplug charging cable and i can't activate the display. I found a workaround for this issue, I unplug it only when the display is on. The latest OTA doesn't fix it. Maybe we should create a bug report on googles bug tracker.
There is a thread about this issue in Googles mobile support forum. You should post there, too. So maybe we get more attention about this serious problem. I can't post links yet, search for: "After 4.3 Android updated, the Nexus 4 always shuts off randomly !!! HELP!!!"
I'm having this issue with my Nexus 7 II. Very annoying, can't watch a movie without it disconnecting. Any fix for this?
Currently not, I hope that Kitkat will fix this
I'm having the same problem on 4.4
Does anyone know how to fix this?
Thanks in advance
Same here on 4.4 but it only happens when my photo is low on charge.
E.G when there's low charge slimport works o.k but when I unplug it the phone dies and requires me to push the power button for 10 seconds to get the photo to work again.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Maybe we should dump Logcat to get the reason why it dies. It tried it several times but with no luck. When i received System log ouputs via adb, the phone doesn't die.
Gesendet von meinem Nexus 4 mit Tapatalk
was found a solution for this problem?
I gather many people are having connection issues with their Android Wear devices.
Is this just a Note 3 issue?
Has anyone managed to get a stable connection using Lollipop?
Yes, my Note 3 with Lollipop (tested many ROMs, even the Note 4 ports) has this issue, and it's not only with Android Wear, but with several other Bluetooth LE devices. I've heard mixed explanations: some say it's something with Lollipop itself, affecting many phones (unless the manufacturer added patches to solve the issue), and Google solved it with Lollipop 5.1; others say it's something only with Samsung's Lollipop ROMs. The latter may be true, as @civato apparently solved the issue tweaking the kernel.
Some people say their phones don't have this issue, but I suspect it's because they haven't put their BTLE devices under the failing scenarios. I have a very easy test case:
1) Pair your Android Wear watch with your phone, using the Android Wear app. Make sure the watch is communicating with the phone.
2) Create a situation where your watch loses connection with your phone (e.g. walk away with the watch, put it in a Faraday cage etc.). But make sure it stays that way for some time, say 10-30 minutes (sometimes it happens as soon as it's out of range).
3) Notice that even though the watch is disconnected (the "no cloud" icon is shown), the Android Wear app on the phone will show it as "connected". Now even if you bring the watch close to the phone again, it will not reconnect automatically.
The same thing happens with other BTLE devices. Other symptoms include frequently disconnects / reconnects, even when the device is in range.
Mine has paired but refuses to connect now. I'll try Civ kernel.
Is there a Lollipop Civ kernel lol
Some problem here with my Sony Smartwatch. The new XEO Update don't fix the Bluetooth problems complete. Is any fix released to fix the Bluetooth Connection problems?
I had all sorts of problems on both the leaked Lollipop and the official Lollipop. It was driving me insane with its constant disconnections/reconnections and then just disconnecting until Bluetooth was cycled. It made the watch useless!!!
I then tried Dark Lords N4 port (v1.5). Boom! All working perfectly. No more issues at all and reconnects if i move out of range seamlessly.
Same problem, Note 3 XEO with Sony SW3. So maybe for now there is only way - root with knox 0x1 and N4 port ROM...
Had a few issues after getting Lollipop but nothing compared to the issues I got when Android Wear updated (on Friday I think it was).
My Moto 360 just wasn't wanting to connect, tried rebooting phone, then the watch, but didn't help. In the end I factory rest my watch and its been fine since.
Vince
Yep, bluetooth all over the shop...Headset and Moto 360.
I also have a lot of problems with Sony SW3 and Note 3. Not only I have inconstant BT connection, but also weird management of incoming phone calls: watch notifies phone calls that appear on the teleohone only 3 or 4 seconds later (that's a huge time).
Anaother issue: I have also tried to decline a phone call with the Smartwatch but the telephone went on ringing.
Inviato dal mio SM-N9005 utilizzando Tapatalk
Hi
Just got a new S Cover with wireless charging for my Note 3. The charging and NFC work quite well.
Phone unlocking by flipping the cover works perfectly. I can also accept or reject calls using S View.
The problem is with the idle S View mode. On the bottom where the camera, missed calls (if there are any) and (I presume) settings buttons are there is some sort of overlay stating "Open the Cover" which doesn't let me use the buttons.
The phone is N9005 Note 3 running official 5.0 OTA update.
Couldn't find anything resembling this so I hope you guys can help.
I have previously used non-wireless S Cover whilst still on Android 4.4 and it worked fine.
I haven't tried to use that with Lollipop because it wasn't compatible wireless charging and it seemed more important to me.
Not sure if that is important, might try to find it and try if that works.
Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
codeman05 said:
Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
Click to expand...
Click to collapse
It's a problem at the source code. It's says it's been fixed on Developer N preview 3. So when N is released publicly it should be fixed. Or you can join the beta program. I have preview 3 running now and it's pretty solid. I don't use bluetooth audio though, so I can't say if it is indeed fixed. If you do try it be sure to enable OEM unlocking in Android dev settings just to be sure you can save your device should anything happen. Also check the list of supported apps so if any app you rely isn't supported you can decide from there.
Sent from my Nexus 6P using XDA-Developers mobile app
Gizmoe said:
It's a problem at the source code. It's says it's been fixed on Developer N preview 3. So when N is released publicly it should be fixed. Or you can join the beta program. I have preview 3 running now and it's pretty solid. I don't use bluetooth audio though, so I can't say if it is indeed fixed. If you do try it be sure to enable OEM unlocking in Android dev settings just to be sure you can save your device should anything happen. Also check the list of supported apps so if any app you rely isn't supported you can decide from there.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Gotcha, that's what I was afraid of. Will checkout the N Preview, thanks!
codeman05 said:
Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
Click to expand...
Click to collapse
Hey! I just found this post. I have had the same issue on my 6P since receiving it in November. I was stock until just a few days ago, now just running 6.0.1 and xposed. The issue fixed itself right after I wiped and rooted, but is now back. This is odd because booting my phone into safe mode didn't fix the issue, so I'm thinking it's not caused by a specific app, although I'm yet to try it.
Since you mentioned you don't use other bluetooth devices, this problem ONLY exists for me in my car audio, a 2015 Chevy Cruze.
If you don't mind me asking, what car are you driving?
Shocknoble said:
Hey! I just found this post. I have had the same issue on my 6P since receiving it in November. I was stock until just a few days ago, now just running 6.0.1 and xposed. The issue fixed itself right after I wiped and rooted, but is now back. This is odd because booting my phone into safe mode didn't fix the issue, so I'm thinking it's not caused by a specific app, although I'm yet to try it.
Since you mentioned you don't use other bluetooth devices, this problem ONLY exists for me in my car audio, a 2015 Chevy Cruze.
If you don't mind me asking, what car are you driving?
Click to expand...
Click to collapse
I have the exact same problem with my 2015 Chevy Volt nav / stereo system. I never noticed this issue until I updated to the Android N release a few days ago. It always happens when I turn on the screen. I rooted and went back to Android M, but the issue is still there. I'm guessing that's because my phone now has the latest baseband and radios instead of the older ones that did not have this Bluetooth problem. If you guys come up with a fix let me know. I'm thinking of flashing the Android M radios to see if that's the problem since I'm now running a custom Android M based ROM anyway. I tested the phone with my wife's 2016 Mazda CX5 and it has none of this screen on stuttering garbage.
UPDATE: I went ahead rooted, installed Pure Nexus ROM (6.0.1-20160821), installed ElementalX-N6P-1.21 kernel, flashed bootloader-angler-angler-03.54.img and radio-angler-angler-03.61.img from angler-mtc20f-factory-d62de11e.tgz, and after all that the issue is still there! What a complete waste of time. What I'm guessing might be the problem is I switched to Sprint on July 2016. Before that I was on T-Mobile and I never had this screen on stuttering issue. It seems there might be some type of interference here and it's possible it is a hardware design flaw since Google has not been able to fix the issue for quite some time. As of now I've switched to my LG G5 phone which has no Bluetooth issues with my Chevy Volt. If I don't find a fix soon I'll probably sell the Nexus 6P and wait for the newer Nexus devices.
FWIW, I have the same issue with my 2014 Chevy Cruze and my HTC 10. Ran across this thread while hunting down a solution (unsuccessfully, this far).
macmanui said:
FWIW, I have the same issue with my 2014 Chevy Cruze and my HTC 10. Ran across this thread while hunting down a solution (unsuccessfully, this far).
Click to expand...
Click to collapse
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
I have found a somewhat reliable fix - PLEASE tell me it works for you all as well.
Hopefully we are all familiar with the problem: A Nexus 6P ( Or whatever is the issue for you) is paired with my 2015 Chevy Cruze that I use to stream audio while commuting. The audio is more or less fine until the screen turns off/I lock the phone. Once I unlock the phone or a notification wakes the screen up, the audio stutters over my car speakers until I turn the screen back off, or 6-8 seconds has passed. This doesn't happen with any other device I own when paired to my car, and my phone doesn't have the same issue when paired with any other bluetooth receiver. I am on a rooted but otherwise stock 6P running 7.0.
I do not use my car for messages, only music/podcasts and phonecalls. I went into the bluetooth settings while driving ( I do not recommend you do this while your car is in motion) and noticed the stuttering was consistent the entire time I had the menu open. This prompted me to assume it must have something to do with the phone making other bluetooth actions while connected to my car, that my car didn't like.
I clicked on the gear for settings next to my car in the bluetooth paired devices list, which pops up the menu that lets you change the name of the device, and what it is used for. My options are: 'Phone Audio', 'Media Audio', 'Contact Sharing', and 'Message Access'. I denied message access to my car the last time it prompted me, but the last two on the list were still checked. I unchecked both of them, reset my phone, and crossed my fingers.
It works. It freaking works. It's not 100% and if I flip the screen on and off over and over again it'll still get a little wonky, but I no longer cringe when I have to unlock my car in the phone.
Will the rest of you give this a shot and let me know if you have similar luck? Best wishes!
Josh
---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------
mhajii210 said:
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
Click to expand...
Click to collapse
You're totally right. I discovered this on my own right about the same time you did apparently and I wanted to make sure it lasted before I made a post here. You deserve all the credit, I'm just so happy it's fixed. Now, I am curious if it'll still stutter a bit if you turn your screen on and off really quickly a few times?
---------- Post added at 01:50 PM ---------- Previous post was at 01:50 PM ----------
mhajii210 said:
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
Click to expand...
Click to collapse
You're totally right. I discovered this on my own right about the same time you did apparently and I wanted to make sure it lasted before I made a post here. You deserve all the credit, I'm just so happy it's fixed. Now, I am curious if it'll still stutter a bit if you turn your screen on and off really quickly a few times?
Seems that GM vehicles are a common denominator too! I have the stuttering with my 6P int my Holden Cruze. Didn't have the issue with my old Nexus 6 and don't have the issue with the 6P when making calls over BT. I haven't listened to as great deal of music from the 6P over BT except in the car so can't really compare there.
It's interesting to read a comment that it was going to be fixed in M preview 3 but even now in Marshmallow release the issue is still there.
Hi, been suffering with a stutter in my Mercedes every 20mins with a 5X on 7.0. Again, seems a common problem with Mercs. I tried EVERYTHING to fix this for months, including full phone wipes and flashes.
I just fixed my issue entirely, not sure if it will work for you guys, but I believe it is an issue with the BT bandwidth that the car is able to cope with. I turned off Phone Book and SMS Message Access services and my issue is gone. I think the phone is maxing the bandwidth with A2DP and as soon as a sync is requested for phone book or message = the problem arises.
Pica_Man said:
Hi, been suffering with a stutter in my Mercedes every 20mins with a 5X on 7.0. Again, seems a common problem with Mercs. I tried EVERYTHING to fix this for months, including full phone wipes and flashes.
I just fixed my issue entirely, not sure if it will work for you guys, but I believe it is an issue with the BT bandwidth that the car is able to cope with. I turned off Phone Book and SMS Message Access services and my issue is gone. I think the phone is maxing the bandwidth with A2DP and as soon as a sync is requested for phone book or message = the problem arises.
Click to expand...
Click to collapse
Interesting. It certainly does feel like a bandwidth issue. I have a Moto360 and has tried turning that off but hadn't thought of turning phone functions off. I don't really want to do that either but will try it to confirm.
I turned off phonebook and SMS but it made no difference to me at all.
I have noticed a Terrible shutter from my device when paired to a portable BT speaker. at times the only fix is to turn the speaker off then back on. it is horrid.