Develop Bugs

NEXUS 7 2013 Big GPS SOFTWARE issue / no Fix

after a loooot of search on the internet and after reading all the older posts here i am desperate and i am opening here a thread. Thats my last hope that someone found a solution to this issue.
So 6 months ago i bought a nexus 7 2013 wifi for a car project. i wanted to use it as multimedia and navigation system. After i modified my car (see pic. / contact me in case of interesst or advices)
https://postimg.org/image/exyp7da37/
everything was nice i was happy with the result. The problem starts when i wanted to use the navigation...
The device cant find a satelite, searching for gps signal is the only message i see. 9/10 the gps cant find satelite. One or two times it found the signal after one hour or more..
My thoughts:
1. The case is causing this issues... the tablet charges wireless and is kept in place with magnets so i can remove it in a second.
I am trying with the "naked" tablet outside with directly sky view... no change.
2. The backcover is modified with 2 small metal plates in order to get magnetizied with the magnets installed in the car dush.
i tried an other backcover.. no change.
3. I tought it is a software issue.... i was using Cyanogenmod 13 with elemental X... installed the original software / Android 6. Without any other installations only GPS Status... still no signal.. I installed android 5.0.1 ... still no signal.
4. i used various of settings changes and apps ( GPS FIX, GPS Doctor, GPS Status) ... the gps android settings are the the most accurate level. Still no change..
created the data/gps/ folder with the permissions rwxrwxr-x. Still no change.
After all that and after reading that there are many people out there with the same problem i thought thats a hardware issue.
5. Thats why i bought an other one (used)... before buying it i made sure that the tablet will find a satelite in GPS Status... i went to the sellers house.. and it did (with wifi off). I went back home i tried again and it did... i was so happy.. i wiped my storage flashed CM13 with ElementalX again ... i opened the Nav App (Sygic)... Everything worked like a charm... i was so happy i finally have gps in my car. I visited a friend stayed there 5 hours went back home... Navi still works.
I took the tablet in my home and wanted to make a restart for some reason... After restarting , tablets gps was dead again... and still looking for a solution..
i am 100% it is a software issue. in case there is someone out there with a solution i would really appreciate it.

I'm kinda on the same boat.
My trusty Nexus 7 2013, that has been through a lot of display changes due to my clumsiness. Few days ago it decided to kick the GPS boat for reasons.
It used to work just fine, without any software tricks or anything. Used to work beautifully without wi-fi (even though I tethered from my phone, many times I travelled to places without connection) with a 8-10m precision.
Now it's spotty, taking from 2 to 280 seconds for the first fix, and precision floats between 10 and 150m (which is unbearable).
Using GPS Status & Toolbox, I can see the A-GPS does it part guiding the tablet on where are the sattelites at (I see around 22 sattelites), however the tablet has a real hard time connecting to them, most of the time staying at a solid 0 connections. My phone (Moto G5 Plus) connects within' seconds to the sattelites with pinpoint precision.
When the tablets manages to fix, it only connects to a couple (5 or 8 out of 22) sattelites, thus not so precise.
I am guessing the heat might have damaged something, but I'm not also 100% sure it ain't a software issue. I flashed the sole GPS fix, but it didn't help at all. I tried every software trick on the book, but nothing. I flashed several ROMs but it didn't make even a dent.
It seemingly gets better if I keep it connected for a good while. I tried letting it overnight with the GPS connected, and it worked fine the day after at any time (between 5 and 20m precision). However it was dead again the next day.
I couldn't find anything regarding a GPS antenna for this device, it's almost like it doesn't have one... I fiddled with the Wi-Fi antenna, which has 3 pins (one I guess is for bluetooth?), but it didn't help with GPS. Bluetooth (I use an OBD2 scanner that sends too many data per second, and I still can play music through bluetooth just fine) and Wi-Fi (Speeds and latency are optimal) are great.
I can't help but think this device doesn't have a GPS antenna, and whatever it uses for an antenna has failed or is now faulty.
Have you ever managed fixing yours?

Bluetooth turning off since NMF26U

Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.

I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.

nighcore said:
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
Click to expand...
Click to collapse
I also use a Huawei watch and the drive safe app. I'm gonna install an older version of the state farm app as it recently was updated now that I think of it.
Sent from my Pixel XL using Tapatalk

thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
FWIW: I've had no Bluetooth issues. Only things I use it for are connecting to my two cars for phone, and Android Auto (which uses USB and Bluetooth connection).

I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.

millerd79 said:
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
Click to expand...
Click to collapse
Ever since I got the Gear S3, my Bluetooth will restart every single time I disconnect my Bluetooth headphones. It also never routes calls through my headsets unless I go into Bluetooth settings and uncheck and then recheck the phone audio option of those headphones every time I reconnect them. I've tried maybe 6 different BT headsets and it's the same case with all of them.

I have been having this issue since NMF26U as well. NOF26V actually seems even worse. It doesn't go off immediately upon connection or disconnecting from my car, but then randomly wile the BT lite will disappear while it is disconnected from any devices. Toggling it back on works as does a reboot that comes back on with BT activated even though it was off when rebooting. Hard to believe after this many updates that BT issues continue to be an issue with this phone.

Probably background tasks are getting killed aggressively. Despite being "not battery optimized", my VPN app gets killed too, if I don't touch my phone for too long. E.g. at night. And yes, I'm facing Bluetooth issue too.

Strange, Bluetooth hasn't turned off since my first post. ?
Sent from my Pixel XL using Tapatalk

I've had this issue and I'm not on the latest firmware. It's happened twice now. Very random, a week between. Maybe it was an update with the Google app, I've noticed a bunch of updates recently

I am having the same issue. The only thing I use my bluetooth for is my car. I have to turn it back on everyday when I start my commute.

I think I found a work around....
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!

Kokopelligod75 said:
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Click to expand...
Click to collapse
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!

t3chfaith said:
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
Click to expand...
Click to collapse
Yeah I would be very curious if it works for you as well and hopefully it does. I was getting very frustrated with it but since I changed those settings it seems to be working fine now and I haven't really noticed any difference in battery performance either.... If you don't mind, keep me posted as I'm curious. Thanks!

Had the Bluetooth turn off on my XL before even entering my car (but I didn't see it happen except when I was about to get in the car and noticed no BT indicator). This was approximately an hour after a reboot and no BT devices had been paired though the indicator was on for some period after the reboot. Pretty hard to believe it was an optimization issue since I had run no apps after the reboot. While typing this, the BT icon disappeared again. Add this to getting a Verizon "Server Unreachable" error on my wife's Pixel yesterday and my XL this morning that both needed reboots to remedy. My frustration with this phone is pretty bad today. Both are unlocked BL, rooted with newest SU, running newest TWRP and newest Google version but otherwise stock. P.S. When you see about 4 Google play updates a day for about 2 weeks (with not very many apps installed other than the base) it is hard to guess what my be causing the issue. OK, rant over.

BT has definitely been a PITA since the latest security update. It's completely ruining the music experience on a car I bought days before the update came out. Since the update I constantly have to toggle bluetooth on then off again to get the phone to connect to the car. Then I have to open Google Play Music and start playback manually. This happens several times a day and is very annoying. Had not a single issue before the update.

I am having issues with Bluetooth disconnecting as well. Was bad on previous build but this most recent update, NOF26V build, is worse. I connect to my truck, watch, and speaker system in home and office. Happens randomly without notice. I have tried to test the "do not distrub" theory, after reboot, etc., so far I have not figured out a root cause or time.

Trying the optimized thing for the heck of it. I noticed that only share was listed and not MDI services. I wonder if that is only available on Google phones and not Verizon somehow or only shows if the BT is connected to the device, but I'm not in the car to check.

I too have a gear 3 frontier and since then I have to reconnect my pixels bluetooth, pretty much once everyday. very frustrating lol

Same BT problem
I have been having the same issue with BT switching itself off for about a week now. Never had any BT issues prior to that. Mine is a Verizon Pixel XL. I noticed it when it wouldn't connect to my car, but I quickly discovered that was because BT was off on the phone. I always leave BT on, so I knew something was funky and paid close attention after that. Once I turn it back on it connects to everything just fine and it stays on for the duration of me using it at that time. But when I go to use it the next time, it is off again. It can be a variable length of time in between when I use it, so I don't know how soon it turns off, but it has to be within just a few hours. This pattern suggests to me that something is turning it off, perhaps to save battery, if it goes without being used for a certain time period. I did not knowingly turn on any setting that does that, so it makes sense that an update changed something. I have not tried the workaround/fix mentioned above; I will do it and report back.

Does Oreo update fix all these issues ?

I got the phone on launch day from Three store. I've already had 3 replacements in store and got a 4th one RMA'd from Razer.
Dont know if its worth waiting for this update. Some people say its fixed most issues some say it hasn't.
Currently i get that auto screen dimming when gaming or on a app for like 5 minutes or so. Very frustrating since the screen is not so bright anyway and it goes down so much, I literally cannot see the screen content when I am outside.
On top of that I have this Bluetooth issue when I connect to a device, either car stereo or any device literally.. It connects and says its connected/paired successfully but when I play something, it plays from the phone speakers.
The only fix to this is I need to go back and delete the paired connection. go to app settings and delete Bluetooth share and Bluetooth midi service app data, restart phone, pair again.
If these two things are not fixed. I've got no more patience left, I'm just going to sell the phone.
Great idea of a phone it is with the loud speakers and 120Hz screen but software has been the worst I've used on a phone by far.
Any info from you guys regarding all this ?

The screen dimming while gaming issue happened to me once, but I was just covering the light sensor with my finger, so I just fliped the phone and never happened again

Well, sincerely I have been with this device for 1 day, I will see if it brings problems, although for now I have not found an anomaly.

alexaraz14 said:
I got the phone on launch day from Three store. I've already had 3 replacements in store and got a 4th one RMA'd from Razer.
Dont know if its worth waiting for this update. Some people say its fixed most issues some say it hasn't.
Currently i get that auto screen dimming when gaming or on a app for like 5 minutes or so. Very frustrating since the screen is not so bright anyway and it goes down so much, I literally cannot see the screen content when I am outside.
On top of that I have this Bluetooth issue when I connect to a device, either car stereo or any device literally.. It connects and says its connected/paired successfully but when I play something, it plays from the phone speakers.
The only fix to this is I need to go back and delete the paired connection. go to app settings and delete Bluetooth share and Bluetooth midi service app data, restart phone, pair again.
If these two things are not fixed. I've got no more patience left, I'm just going to sell the phone.
Great idea of a phone it is with the loud speakers and 120Hz screen but software has been the worst I've used on a phone by far.
Any info from you guys regarding all this ?
Click to expand...
Click to collapse
I haven't had those problems, but clicking the down arrow on the mobile data quick settings crashes, every so often my phone freezes and reboots (though less than Nougat), and there's the multitouch bug which gets fixed in the May security patch (which as far as i know is not out yet).

alexaraz14 said:
I got the phone on launch day from Three store. I've already had 3 replacements in store and got a 4th one RMA'd from Razer.
Dont know if its worth waiting for this update. Some people say its fixed most issues some say it hasn't.
Currently i get that auto screen dimming when gaming or on a app for like 5 minutes or so. Very frustrating since the screen is not so bright anyway and it goes down so much, I literally cannot see the screen content when I am outside.
On top of that I have this Bluetooth issue when I connect to a device, either car stereo or any device literally.. It connects and says its connected/paired successfully but when I play something, it plays from the phone speakers.
The only fix to this is I need to go back and delete the paired connection. go to app settings and delete Bluetooth share and Bluetooth midi service app data, restart phone, pair again.
If these two things are not fixed. I've got no more patience left, I'm just going to sell the phone.
Great idea of a phone it is with the loud speakers and 120Hz screen but software has been the worst I've used on a phone by far.
Any info from you guys regarding all this ?
Click to expand...
Click to collapse
The Bluetooth problem may be a problem with your cars radio and not the phone. I have a 2012 Scion TC and and tried connecting my Razer Phone, HTC 10 and an iPhone 8 and they all had similar connectivity issues where audio was just being routed through the phone.

waiflih said:
The screen dimming while gaming issue happened to me once, but I was just covering the light sensor with my finger, so I just fliped the phone and never happened again
Click to expand...
Click to collapse
The issue itself is nothing to do with covering the light sensor. I've read on here and on Razer Insider forum that it is heat/power related and that lowers the screen brightness because it consumes too much power. A lot of people get this problem and a lot dont know about it too.
ThatGuy94 said:
The Bluetooth problem may be a problem with your cars radio and not the phone. I have a 2012 Scion TC and and tried connecting my Razer Phone, HTC 10 and an iPhone 8 and they all had similar connectivity issues where audio was just being routed through the phone.
Click to expand...
Click to collapse
Its not my car radio. I've tried on 3 different car radio's and a Bluetooth portable speaker, I get this problem with literally every device i connect to. I still have not had a fix or a solution. Only thing Razer suggests every time is a factory reset which did not change anything.

This thing on max settings according to Ampere is pulling nearly 1.5amps from the battery with brightness at full and all settings maxed
Sent from my Phone using Tapatalk

Bluetooth disconnections and unpairing driving me to distraction

My issue seems to be different from others' as mine isn't just bluetooth losing its connection - it actually unpairs.
In my car (it has an Android Auto compatible infotainment system) it works fine for ages then fails to connect all of a sudden. Then after a while a message pops up on the car's screen saying "bluetooth pairing successful". The phone then asks me for contact sharing permissions. Of course it screws up the smart unlock feature as a result forcing me to set it up again.
On my Huawei watch 2 sport it loses connection and so the wear os app says the watch is disconnected. Bluetooth settings show the watch to be invisible and, as a result, smart unlock gets unconfigured and I have to set it up again. The watch battery discharges very quickly - probably constantly searching for the phone.
I reboot of both devices seems to fix it, for a while.
This is all since the Pie official update.
Does anyone have any fixes please?

gadgetgaz said:
My issue seems to be different from others' as mine isn't just bluetooth losing its connection - it actually unpairs.
In my car (it has an Android Auto compatible infotainment system) it works fine for ages then fails to connect all of a sudden. Then after a while a message pops up on the car's screen saying "bluetooth pairing successful". The phone then asks me for contact sharing permissions. Of course it screws up the smart unlock feature as a result forcing me to set it up again.
On my Huawei watch 2 sport it loses connection and so the wear os app says the watch is disconnected. Bluetooth settings show the watch to be invisible and, as a result, smart unlock gets unconfigured and I have to set it up again. The watch battery discharges very quickly - probably constantly searching for the phone.
I reboot of both devices seems to fix it, for a while.
This is all since the Pie official update.
Does anyone have any fixes please?
Click to expand...
Click to collapse
No fixes but same problems here

I'm having the same issue also very frequently with WiFi dropping all the time. These two reasons are linked from what I been told. Google telling me to RMA. The pain of that

Mine has done this with my Gear S3 watch since I first got the phone a few months ago, it had me seriously considering returning it for a while. Sometimes it would just disconnect from the bluetooth, but often it would unpair causing me to have to go through the whole set up process again. It did this on Android O, various DP builds of P but so far (touch wood) has been good with the latest version of the Samsung software and Android P.

I'm having the same issues as well and currently searching for answers.

Issues with new Pixel 3 connecting to car

So I've just switched back from IOS to Android and picked up a Pixel 3 XL with the 1-day sale. I tried setting up Android Auto though but I can't get it to work properly. I can connect and add my car (2017 Kia Niro), but after I try to select the Android Auto icon on the head unit it crashed and keeps flashing "Phone is not responding" and "Reading USB" over and over. On the phone, it still says connected to the car and shows the green notification bar suggesting Google Maps is in use.
I've tried using an older version of AA, but it gives an error unless I update. If I try to connect, not press the icon on the head unit and start playing Spotify, I get 1-2 seconds of audio through the car but then it crashes again. One time I got as far as launching and selecting the navigation tab until it crashed. I've briefly talked to Google support and they requested a bug report which I've sent. I also tried updating to the Q beta to see if that made any changes. I've used 5 different USB cables with no luck.
I didn't have any issues with Apple Carplay, and I also tried a very old Samsung phone (micro-USB) successfully so it shouldn't be the car causing the issue. Does anyone have any tips on what I should look at? I've done a factory reset, cleared all cars, toggled the AA setting on the head unit but nothing makes any difference. I'm pretty reliant on this functionality, so if it doesn't work I probably will be switching back to my iPhone.

Odd behavior. I've had a few issues with AA on my 3XL on Q beta 2 (patched), but none like that. I have a 2016 Chevy Malibu and most of the time when I plug it in I get video but no audio. Pressing play on Spotify does play, but no sound comes out. Disconnecting and reconnecting USB a few times fixes it. There are intermittent skips in the music where it cuts out for a second and comes back. The screen flashes black at times when a notification peeks on the screen like when the song changes. Overall it works, but Q beta brought some bugs. It was mostly OK on P. I believe the no audio started on beta 2.
Have you looked at the developer settings in AA to see if any toggles might help? I think you can go to About and tap the version 7 times, similar to enabling Dev Options by tapping build number in Android system settings.

fury683 said:
Odd behavior. I've had a few issues with AA on my 3XL on Q beta 2 (patched), but none like that. I have a 2016 Chevy Malibu and most of the time when I plug it in I get video but no audio. Pressing play on Spotify does play, but no sound comes out. Disconnecting and reconnecting USB a few times fixes it. There are intermittent skips in the music where it cuts out for a second and comes back. The screen flashes black at times when a notification peeks on the screen like when the song changes. Overall it works, but Q beta brought some bugs. It was mostly OK on P. I believe the no audio started on beta 2.
Have you looked at the developer settings in AA to see if any toggles might help? I think you can go to About and tap the version 7 times, similar to enabling Dev Options by tapping build number in Android system settings.
Click to expand...
Click to collapse
Thanks! I'll give that a shot when I go to my car later. I forgot about the AA dev options, it's been so long since I've used Android. Hopefully, if I do get it working I don't have the audio issues you mention by switching to Q else I guess I'll need to revert back to P.

I just received a new Subaru, and I couldn't get AA to open at all. After searching, a common denominator was the cable used to connect the phone (my car requires a usb connection). I tried 4 different cables before I got it to work.
The one that worked was an OTG cable, no longer available on Amazon.
Sent from my Pixel 3 XL using Tapatalk

princeplanet said:
I just received a new Subaru, and I couldn't get AA to open at all. After searching, a common denominator was the cable used to connect the phone (my car requires a usb connection). I tried 4 different cables before I got it to work.
The one that worked was an OTG cable, no longer available on Amazon.
Click to expand...
Click to collapse
I have 2 Subarus and had issues with AA until I figured out that I needed the head unit to come up, have the I agree screen dissappear, and then connect the phone. Works every time. Plugging the phone in before booting the head unit is hit or miss.
---------- Post added at 08:03 AM ---------- Previous post was at 08:01 AM ----------
wafflenator said:
Thanks! I'll give that a shot when I go to my car later. I forgot about the AA dev options, it's been so long since I've used Android. Hopefully, if I do get it working I don't have the audio issues you mention by switching to Q else I guess I'll need to revert back to P.
Click to expand...
Click to collapse
Try waiting for your cars head unit to come up before connecting the phone. Ideally bluetooth wilm be connected before you connect USB.

Well, turns out it was the cable. This was 4 old supposedly good cables from a few years ago, along with a new one from Best Buy. Picked up a new Insignia USB C cable where the reviews mentioned success with AA and it is working. Bit of a headache but good news.