Database Users

Accelerometer issue...HELP!!!

Hi there!
I've recently bought a Nexus 4 over at the Play Store and after a few minutes of opening i fell in love with it. Very nice, very good upgrade from Galaxy Nexus.
But also after a few minutes of using it i managed to find a problem....the accelerometer.
When i contacted Google they advised me to do a factory reset (like they always do) which i did. I made sure the Auto rotate under Settings is enabled and apps are updated.
After turning on & off and checking the Settings the auto rotate still doesn't work. This is for almost anything from viewing websites to Youtube to the music player, etc.
I have some questions please:
1. Is this a "common" complaint from majority of N4 users? (as testimonials would say online)
2. Is it worth going to an LG Repair Centre to have it fixed? And can it get fixed there?
3. Is there a software/ROM/patch i can download and install to "force enable" the accelerometer to auto rotate? If yes then can someone please tell me and explain to me how?
Shame the unit i got seems defective and it would take at least another week (or even more) if i return the thing to Google, shipment to & from base, processing of papers, shipping a replacement unit to me. etc.
Please help.
Thank You.

1. It's not a common complaint at all.
2. You should call Google and check the details of sending your device back, whether to a LG centre or a Google centre
3. You can try flashing one of the custom ROMs in the Development section but I doubt there's a problem with the stock ROM.
You should get the device replaced ASAP as it's probably a manufacturing defect.
Good luck

Anyone found a fix for chromecast

Yesterday I used my chromecast again. .... after using it when using notification shade a persistent error appears. ... only way to fix it is rebooting. Any ideas?
Enviado desde mi SM-P600 mediante Tapatalk

Can you elaborate some more? I'm not having any issues like yours so give some extra information please.

mantrajt said:
Yesterday I used my chromecast again. .... after using it when using notification shade a persistent error appears. ... only way to fix it is rebooting. Any ideas?
Enviado desde mi SM-P600 mediante Tapatalk
Click to expand...
Click to collapse
Seems a few of us are waiting for this to be fixed. Another forum member has sent their tablet back to samsung twice now hoping for a fix. This problem is apparent on my note pro as well, so I think we need sammy to push us a software fix

chgambini said:
Seems a few of us are waiting for this to be fixed. Another forum member has sent their tablet back to samsung twice now hoping for a fix. This problem is apparent on my note pro as well, so I think we need sammy to push us a software fix
Click to expand...
Click to collapse
Hope this doesn't take them soooo looooong
Enviado desde mi SM-P600 mediante Tapatalk

I wonder if the Samsung phones running 4.4 have this too or is it just the tablets? I know the 12 inch version has this issue too.
It's the primary reason I'm still running 4.3.

chgambini said:
I think we need sammy to push us a software fix
Click to expand...
Click to collapse
Not to be the bearer of bad news but if it's an isolated problem affecting a small percentage of users the likelihood of Samsung issuing an update for just this specific issue is pretty slim. I don't use Chromecast myself but I was at a friends house last night and tried it from my N10.1-14 running 4.4. I didn't have any issues and the notification panel didn't bork while I played with it during Chromecast playback. Since those with the issue didn't have it on 4.3 it's obviously a s/w compatibility issue or conflict. I'd try to narrow down what's unique on the Pro's and Note's running 4.4 that are having problems to find the ROM version/region, installed s/w, combination of s/w, configuration, or settings that are causing it. You guys huddling together to figure it out will be faster than waiting for a fix that may never come.

BarryH_GEG said:
Not to be the bearer of bad news but if it's an isolated problem affecting a small percentage of users the likelihood of Samsung issuing an update for just this specific issue is pretty slim. I don't use Chromecast myself but I was at a friends house last night and tried it from my N10.1-14 running 4.4. I didn't have any issues and the notification panel didn't bork while I played with it during Chromecast playback. Since those with the issue didn't have it on 4.3 it's obviously a s/w compatibility issue or conflict. I'd try to narrow down what's unique on the Pro's and Note's running 4.4 that are having problems to find the ROM version/region, installed s/w, combination of s/w, configuration, or settings that are causing it. You guys huddling together to figure it out will be faster than waiting for a fix that may never come.
Click to expand...
Click to collapse
I think the percentage is bigger than we think. I have tried all the floor models at my local best buy and they to mess up. I to doubt samsung will fix this. I am not sure how to isolate the problem. The note pro I have access to is completely stock, the stock wallpapers for lock and home screens have not even been changed. I have factory reset both devices and have not installed any app other than the pre-installed stuff. Calling samsung doesnt help, I have already read of other forum members sending their tablets in to just have them sent back without being "fixed". There are more than one thread about this throughout XDA and other sites.
I have owned my 2014 since nov 2013. I haven't changed anything on it other than the update to 4.4. Thats why I beleive it is the cause. The moment after the update was complete, the chromecast problem happened.
I will say again, chromecast works as always fof many, many apps. Listening to google play music and google play movies seems to be the biggest offenders. I have read that the Crackle app has problems too.
My 2014 and pro are bogh 32g US version purchased straight from samsung. Both have never been rooted.

chgambini said:
I think the percentage is bigger than we think.
Click to expand...
Click to collapse
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.

blinkingled said:
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.
Click to expand...
Click to collapse
I assume your using google play music/movies too

chgambini said:
I assume your using google play music/movies too
Click to expand...
Click to collapse
Pretty much anything that works with Chromecast crashes it. Twit Cast for Chromecast, Google Play Music and Videos, Chrome Beta, YouTube etc.

blinkingled said:
Pretty much anything that works with Chromecast crashes it. Twit Cast for Chromecast, Google Play Music and Videos, Chrome Beta, YouTube etc.
Click to expand...
Click to collapse
I can watch youtube and hbogo with no problems. Do you have the video playback issues as well? If I try to watch a video from g+ or a preview of a movie on google play, I will either get a black screen with audio only, or massive stuttering and lines while watching on the tablet in full screen.
I have sent feed back to Google on the music and movies apps. Lets see what kind of reply we get from them

blinkingled said:
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.
Click to expand...
Click to collapse
What regions does it affect? Obviously you're in the U.S. My working device is from Latin America. Do Chromecast's themselves come with a single version of s/w that's deployed identically worldwide? Google updates Chromecast. Was the Chromecast's firmware the same before and after the N10.1-14 started crashing? You need to figure out what the devices that aren't working have in common and that includes Chromecast itself. Does screen mirroring work by means other than Chromecast? You'd think if something was majorly wrong with the N10.1-14's video, networking, or s/w drivers screen mirroring would be borked consistently. Just some things to think about.
I'll give you an example. Some folks with the OG N10.1 reported importing PDF's crashed S Note. A bunch of us weren't having any issues. We found out that even though the OG 10.1 was only six months old at the time there were eight different versions of S Note installed depending on region. Two of the eight had the PDF problem. Therefore I'd be careful about making assumptions about how wide spread the issue is. Chromecast's pretty popular and I think there would be more "WTF?" posts if it was as widespread as some think it is.

SamsE=BarryH_GEG;52798927]What regions does it affect? Obviously you're in the U.S. My working device is from Latin America. Do Chromecast's themselves come with a single version of s/w that's deployed identically worldwide? Google updates Chromecast. Was the Chromecast's firmware the same before and after the N10.1-14 started crashing? You need to figure out what the devices that aren't working have in common and that includes Chromecast itself. Does screen mirroring work by means other than Chromecast? You'd think if something was majorly wrong with the N10.1-14's video, networking, or s/w drivers screen mirroring would be borked consistently. Just some things to think about.
I'll give you an example. Some folks with the OG N10.1 reported importing PDF's crashed S Note. A bunch of us weren't having any issues. We found out that even though the OG 10.1 was only six months old at the time there were eight different versions of S Note installed depending on region. Two of the eight had the PDF problem. Therefore I'd be careful about making assumptions about how wide spread the issue is. Chromecast's pretty popular and I think there would be more "WTF?" posts if it was as widespread as some think it is.[/QUOTE]
I have 2 chromecast in my house. Yes the are updated OTA directly from google. The firmware was the same before and after the update. My note 3 on 4.4 works perfectly with chromecast with the same version of google play music/movies and the ssme apps overall installed. Samsungs allsharecast will work on my tablets. The only devices I have that exhibit this behavior are the note 2014 and note pro. Both stock us version, both crash on play music/movies, both have random issues with video play back. The 2014 was fine before 4.4, so this leads me to believe the update is causing it. I did not try the pro until I had issues with the 2014 to see if it was the same so I cant say it was good or bad out of the box. The pro did rec an update right before the 2014 rec 4.4.

chgambini said:
I have 2 chromecast in my house. Yes the are updated OTA directly from google. The firmware was the same before and after the update. My note 3 on 4.4 works perfectly with chromecast with the same version of google play music/movies and the ssme apps overall installed. Samsungs allsharecast will work on my tablets. The only devices I have that exhibit this behavior are the note 2014 and note pro. Both stock us version, both crash on play music/movies, both have random issues with video play back. The 2014 was fine before 4.4, so this leads me to believe the update is causing it. I did not try the pro until I had issues with the 2014 to see if it was the same so I cant say it was good or bad out of the box. The pro did rec an update right before the 2014 rec 4.4.
Click to expand...
Click to collapse
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.

BarryH_GEG said:
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
Yes I have done a hard reset on both devices, skiping past adding any accounts and unchecking the restore app data box.
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
BarryH_GEG said:
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
No sdcard. I will try a hard reset again, unchecking all the google sync stuff. Got nothing to lose.......

Try downloading a free show or trailer in Samsung Hub Video. Does the issue occur with a Samsung app using Samsung-sourced content?

BarryH_GEG said:
Try downloading a free show or trailer in Samsung Hub Video. Does the issue occur with a Samsung app using Samsung-sourced content?
Click to expand...
Click to collapse
OK, hard reset, nothing installed, skipped past adding accounts. Went to settings, back up and reset unchecked restore apps data and added my Google account with all sync unchecked. Google music and movie still cause system.ui crash when touching the notification bar. Samsung hub plays fine. Samsung hub does use allsharecast to my Samsung TV and not the chromecast though

chgambini said:
OK, hard reset, nothing installed, skipped past adding accounts. Went to settings, back up and reset unchecked restore apps data aND added my Google account with all sync unchecked. Google music and movie still cause system.ui crash when touching the notification bar. Samsung hub plays fine. Samsung hub does use all casts hare to my Samsung TV and not the chrome cast though
Click to expand...
Click to collapse
Try turning off Chrome in Application Manager.

BarryH_GEG said:
Try turning off Chrome in Application Manager.
Click to expand...
Click to collapse
No change, still crashes

BarryH_GEG said:
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
That's an extensive and well thought out debugging list - thanks :good: (I had posted a message some time ago to gather info from people having and not having the issue - but I think we only got 2-3 uncertain data points.) But at this point I have tried everything in your post - reset, with and without SD, without restoring apps, with and without updates. It still crashes. And the ChromeCast firmware was last updated was in mid April when it didn't have an issue with 4.3 - so that doesn't seem to be a factor either.
About being in the US - I think OP's tablet is Latin American version if I am not mistaken. It's really a mystery at this point as to why some of them work.

Bluetooth problems, audio & Android Wear

Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!

Dan76 said:
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Click to expand...
Click to collapse
I sometimes have issues reconnecting to my bluetooth headset (fixed by repairing) but no issues when it is connected. And I have a moto 360 always connected that has no disconnection problems. I would go with a factory reset!

Dan76 said:
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Click to expand...
Click to collapse
I know this is several weeks old, but yes I have this issue, and have done everything imaginable to get rid of it, to no avail.
My phone pretty reliably connects to my 360 (or, currently, Pebble), but is almost useless in my car. Fine for phone calls, but audio works 1 time out of 5 at best, otherwise it just does thta jumpy skip thing.
I initially thought it was because of Android Wear -- connecting to the watch was using too much bandwidth and interfering with the ability to talk stream audio -- but a) it's ONLY aproblem in my car (and my wife's car, so it's not JUST my car), never to, like, a standalone bluetooth speaker, and b) I completely wiped my phone and didn't install Android Wear or pear with a watch at all, and the problem resurfaced. A clean wipe almost always results in reliable bluetooth for 2 or 3 days, and then it gets jumpy, which HAS to be a clue (some state or buffer being corrupted / filled?) but I haven't been able to figure out what it's clueing me into.
This thread dives into the potential Android Wear connection, but no real solution.
If anyone who HAS experienced this figures out a solution, I'd really love to hear it.

Not sure if this applies. However, I experienced this EXACT problem when streaming music over bluetooth. This problem only happened AFTER I made or received a call. Reboot is the only cure. This is with 6.0 stock with Feb update. I tried 2 phones with the same problem. Both were new out of the box. This FW is obviously defective. I'm not sure why others aren't reporting this issue. My search for a phone continues....

insanedc said:
Not sure if this applies. However, I experienced this EXACT problem when streaming music over bluetooth. This problem only happened AFTER I made or received a call. Reboot is the only cure. This is with 6.0 stock with Feb update. I tried 2 phones with the same problem. Both were new out of the box. This FW is obviously defective. I'm not sure why others aren't reporting this issue. My search for a phone continues....
Click to expand...
Click to collapse
I can usually toggle off Bluetooth then back on and it's okay, but sometimes it does require a restart. SUPER frustrating when you're driving! I'm glad I'm not the only one, I just wish we'd get more info on this and maybe someday a patch.

Bluetooth audio "stutter" on wake/unlock?

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.

Since Android 11 some apps stopped working in background

Hello,
Every time i am driving my car i am using Blitzer for speed cameras and Amigo for warnings on the speed limit. Since i updated the S10+ with Android 11 i have noticed that as soon the display goes dark, both apps stop working. With this, i mean they both lose GPS connection so i do not receive any warning. Did not have any problem before the update, now i do not know what to do. I've tried everything. They are both NOT battery optimized, with all permissions granted, an still nothing works. What is worse is that even the GPS connection is not so stable as before. It takes a lot more time to get a GPS signal although i did not change any setting.
Does anyone had the same problems?
Thanks in advance!
Later edit
So, for those interested, i have solved the problem for both apps.
For Amigo (by TomTom) the solution i have found it was switching the Location permission from "Only when it's in use" to app to "Always". It started working again in the background.
For Blitzer.de i have the solution by accident. The culprit was a Bixby routine that was suppose to start the app as soon as it was connecting to my car's bluetooth.
As soon as i started the app manually everything started to work again in the background.
I would like to point out again that both apps were working just fine until i have updated to Android 11.
Hope that my findings will help also someone else having similar problems.
Happy Easter !