Related
I'm having a strange bug where when I use the gps and bluetooth for prolonged periods, the radio seems to shut off. This only happens when i'm driving from Oregon to California and I use the phone for music/audiobook and as a gps for time remaining in the trip.
I'm using Navigation for the gps and the standard play music for bluetooth music. I'm driving a Subaru and have never had this issue before. By the way, the phone gets 7 hours + for gps if the screen isn't kept on the entire time, much less if it is but still over 4 hours.
My xt890 is is not unlocked and is still completely stock. It also randomly shows a G where normally theres an edge symbol since I restrict my phone to edge because the Tmobile roll out hasn't happened in my area yet I don't think (Phone doesn't get 3g ever).
When the bug occurs the only method I've found that fixes it is to reboot the phone, airplane mode and back does not fix it. Though after the bug occurs once, it seems to happen more frequently. Could I be overheating something?
I experienced problems turning on gps on my RAZR-i twice in the last 2 weeks. I am using CoPilot live for navigation. In each case turning the phone completely off and waiting a few minutes solved the problem. In both cases I had the phone on (T mobile) and was using wifi for an extended period of time. I believe something is overheating. Don't think a HW problem, rather firmware reducing power to stay within the power budget (not enough for gps), but I am not 100% sure...
Sent from my NOOK using xda premium
Ok- yesterday the gps stopped working completely.
After doing a hard reset all problems are gone now.... clearly something got corrupted. Question is what app caused all my problems. Anyway, I am glad it was not an HW issue (imported it from GB to US)....
Sent from my XT890 using xda premium
I got my original Note 4 last Sunday. Since I use GPS navigation quite often, it is always one of the first things I check out when getting a new device. I found that it didn't hold a lock for long, it takes a long time to get a lock again, and when it does lock it's not accurate at all. I got an exchange today, and the same exact thing is happening with my new unit. A friend told me this would be the best place to come for help. She mentioned that rooting and custom romming might be the fix. I haven't rooted since my MyTouch 4G, and I've never used a rom. Can I get some help with that?
Also, I've tried waze instead of Google maps and that didn't help. And yes, high accuracy is turned on.
Thanks in advance!
Bump - any advice? On a different forum, someone mentioned downloading a GPS fix app from the Play Store. I did that, and I'll check it out on the way home from work. But ultimately I'd like a device with strong GPS natively. I'll try to exchange it one more time. I find it really weird that I'm the only one that seems to be having these problems!
pantlesspenguin said:
I got my original Note 4 last Sunday. Since I use GPS navigation quite often, it is always one of the first things I check out when getting a new device. I found that it didn't hold a lock for long, it takes a long time to get a lock again, and when it does lock it's not accurate at all. I got an exchange today, and the same exact thing is happening with my new unit. A friend told me this would be the best place to come for help. She mentioned that rooting and custom romming might be the fix. I haven't rooted since my MyTouch 4G, and I've never used a rom. Can I get some help with that?
Also, I've tried waze instead of Google maps and that didn't help. And yes, high accuracy is turned on.
Thanks in advance!
Click to expand...
Click to collapse
Did you try a full wipe
NOTE 4
BACARDILIMON said:
Did you try a full wipe
NOTE 4
Click to expand...
Click to collapse
Yes, on both devices.
Are you the same penguin from the a/c forums?
Sorry to hear you're still having gps issues with your replacement phone. Silly question, but is high accuracy mode selected in the location settings? Is wifi enabled?
Have you tried installing GPS Status? How many satellites can you lock onto?
DruHill said:
Are you the same penguin from the a/c forums?
Sorry to hear you're still having gps issues with your replacement phone. Silly question, but is high accuracy mode selected in the location settings? Is wifi enabled?
Have you tried installing GPS Status? How many satellites can you lock onto?
Click to expand...
Click to collapse
Yep, I'm the very same penguin . High accuracy mode is indeed enabled. I haven't tried it with wifi enabled, I usually disable it when I leave home to conserve battery life. I'll try keeping it enabled on my commute home tonight. I've installed GPS status and it locks on to like 13ish out of 20ish satellites (it fluctuates a bit) when I'm stationary so that's not a problem. I haven't tried seeing how many lock on when I'm driving since I don't want to fiddle with my phone that much when I'm on the road. I'm still trying to get one more replacement before my 14 days are up, but the day is approaching quickly, and none of the 7 or 8 stores in my immediate area ever have any in stock! I call every other day and I'm sure I'm driving the reps crazy lol.
I've had this same issue with my first Note 4 on TMo but replaced it last week and havent had any issues besides very occasionally having a slight hang after making a turn and the GPS not registering it for a few hundred feet.
On my first note 4 it would CONSTANTLY lose GPS signal and be wildly inaccurate (not recognizing my turns or the proper facing direction) but hopefully *knock on wood* its been fixed with my new phone. I know you've already exchanged it but...
If you find a fix, please post it here just in case
I had the same problem with the GPS, it was working only on wifi but not with the phone data. But after a full flash it is working fine again. Also, it was very laggy since the first day.
I had a thread around here for similar GPS issue.
I actually got a PM from someone called SamsungSupport.
Anyway I think this is a compass calibration issue.
I installed the GPS Status app and recalibrated the compass.
The next time I used it (yesterday), I didn't have any issues.
I don't know if it has resolved the problem and I'll keep monitoring it whenever I use GPS.
I got my second replacement yesterday, and it's even worse than my initial replacement!! It's as bad as my first device.
I chatted t-mo customer care today and they were of no help. They kept advising me to do the same troubleshooting issues I've already done. Then, I chatted Samsung care and the rep was A LOT more helpful than the previous Samsung rep I spoke with. Samsung has a remote app that you can download from the Play Store, and the Samsung rep can remote into your device and see what you're seeing. We couldn't do much at the time since I'm at work, but I'm set to chat them back right before I leave work. They're going to remote in with me and actually see the issue that I'm having while driving. HOPEFULLY a fix will come out of all this!!
Bump. I'm on my FOURTH replacement now, same issues. What is going on?? So far, I've:
Recalibrated the compass
Tightened the screws underneath the battery door (they seemed pretty tight anyway)
Samsung support reps haven't been able to work with me using the Smart Tutor (remote into my phone to see/manipulate what's on my screen) app. They always disconnect the session before I get on the road, or maybe the session just drops.
Factory resets
Clearing the cache
I got my firmware reflashed at a Samsung kiosk at Best Buy
Make sure high accuracy mode is enabled (these days I never take it off since I'm always fiddling with my GPS)
Tried a number of gps fix apps in the play store
They want me to send in the phone for repair, but I have this nagging feeling that they're going to turn it on, see that gps can indeed get a lock, and send it back. Plus, there's no guarantee that T-Mobile will have a smartphone loaner phone, since they say that those phones keep disappearing because there's only a $50 deposit, so people just take the phones (this is why we can't have nice things). Since no one else is reporting these issues, it's doubtful that Samsung is working on a software fix for it. I'm really REALLY enjoying this phone otherwise, but I NEED gps to work!!
Samsung Note 4 Issue with Waze
I just upgraded from the Note 3 to the Note 4 two days ago and I have the same issue. It took me a few hours but I figured what they have done. They have program the Note 4 for totally hands free driving and if you want to use a GPS program it will be the one they have. You have to activate CAR MODE and you will see and hear your Waze in the background come on line and start to work correctly. Then if you close their program quickly, you will see Waze running correctly for about 5 seconds and the go back to acting up without GPS signal. The GPS signal with high accuracy is tied to the CAR MODE.
TMOBILE will never offer a smartphone loaner as per policy. GPS works fine not sure what ur doing
BAD ASS NOTE 4 + BAD ASS GEAR S
Let me preface this by saying that after changing this setting and 20 hours later with multiple separations of phone and watch, I have yet to miss a notification and battery life is much much better. My specific problems were: Watch would randomly stop receiving notifications. I would realize this after a few hours go by without any notifications and pull my phone out and see what I've missed. This would happen despite the Wear app showing 'connected' status. Another issue I had was giving a voice command and after a few seconds the watch would return a 'disconnected'message, again the Wear app showed connected. All of this under known working network connections, whether Wi-Fi or cellular. I was also experiencing what I feel is short battery life at about 14 hours per day. I've had and used the watch for two weeks now and have restarted it many many times.
The following is the ONLY thing I have changed since the major improvement in performance. I don't have the depth of knowledge to prove or describe why this worked for me, and maybe it wasn't the cause, but I (knock wood) have a perfectly operating watch now with the battery life indicating about 2 days remaining at noon today.
Go to Settings> Bluetooth> and select the settings icon on your connected device. Then select 'connection access' and choose 'automatic'. Mine defaulted to 'always ask'.. I'm guessing this caused a hangup with the connection between Wear app and watch leading to my problems.
Edit: I'll add that my phone is an LG G2 on 4.4.2 , rooted and running xdabbeb's Rom.
Edit 2: I reset my watch, synced the watch via the Wear app on phone and NOT the Bluetooth screen and now I'm running strong after two days. Made sure automatic was checked as well.
Bugger
I don't have that option in my bluetooth settings
I don't have any problems with mine so far but just checked my settings and it was on always ask.
Could anyone confirm what it should be set as? I have changed mine to automatic anyways.
Thanks for the heads up.
Phil
Not seeing that option in Android 5.0.1 on my HTC One GE. But I have not been having any of the issues mentioned in the OP.
Sent from my Nexus 10 using Tapatalk
Here is a pic of the screen where you make selection. Always Ask is NOT what you want, which is what is pictured. Select Automatic. Sounds like this isn't available on Android 5.0 from what I see in responses so far.
I don't think I saw this option on any of the ROMs I ran, but there may be devices out there that have it and default to it, and this one would really break wear connectivity - so it may help someone someday.
I'm on 5.0, lg g3 and have both options.
Although i havnt had a problem with always ask and only switched it to automatic tonight.
Judging from the description, it will work as long as the watch stays connected, but a reconnect from the watch side would ask for confirmation (and could be possibly even silently denied under some circumstances).
Phone -> Watch = no problem
Watch -> Phone = problem
and it's possible (and likely) there are more connections going on than just the primary one, and if the connection is flaky there might be a dead one and a new one from either side...
you could just have been lucky, so far
My issues returned last night. I left my watch at home and went to dinner and out with friends, came back home after several hours. I left the watch in theater mode while I was out and over night. I woke up this morning, put watch on and realized the battery had tanked overnight and I was no longer receiving notifications, again, wear app showing connected. I looked at the battery graph for the watch and it is totally flat while I was out last night and appears to tank fast as soon as I got home and my phone was in proximity to the watch again. It's like it is constantly trying to handshake with the phone or something. The only thing that fixes this problem is a reboot of the Watch itself. I still think the connection setting was helpful because I have yet to see battery life like that or a solid link for that long. I would love to know what exactly is going on here. Bad hardware?
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
That's what I have also since I own the watch.
Stbrightman said:
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
Click to expand...
Click to collapse
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
mic18u said:
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
Click to expand...
Click to collapse
Nope, shows also when out of the box so without android debugging.
Just a normal operation notification
I just discovered another possible contributor to connectivity issues: I just tried to use my watch to voice dial and after multiple attempts I got the disconnected message. I took my phone out and Wear app says connected and I had full 4G signal. My phone is set with a pattern lock. After unlocking it and checking the above mentioned, I tried the watch again and it worked. Could locking your phone have something to do with these problems?
I 've had the Urbane for three weeks now, and I'm pretty pleased* with the watch except for a major problem:
I keep seeing that "cloud with a line through it" icon on top of the watch face way to often.
I'm actually looking at it right now - I'm at work, my Urbane is on my left wrist, and my phone is on the desk 20 centimeters away.
Since I haven't heard many others complaining about this, I'm suspecting the problem to be on the phone side - this is a "China phone", an Elephone P3000S (64bit, 3GB RAM) that I bought quickly as a cheap, but (on paper) good spec'd replacement for my broken Sony Z1 Compact.
But nevertheless, I thought I'd asked here if anyone else are experiencing the same?
I've factory reset the watch, I often reboot it, I reboot the phone even more often, and most of the time connection is re-established but lasts only for maybe 15 minutes up to several hours. I have disabled wifi on the watch to see if that improves things - initially I thought maybe it did (as long as I kept the phone nearby, of course), but after a while it seems it's not the case.
Anyone have any other tips? ...Before I replace the phone?
Thanks,
Christopher
*: of course I would prefer a brighter screen (when needed, i.e. outdoors), light sensor, better battery capacity, ...
Try to find out what Bluetooth version the phone has.
grenness said:
I 've had the Urbane for three weeks now, and I'm pretty pleased* with the watch except for a major problem:
I keep seeing that "cloud with a line through it" icon on top of the watch face way to often.
I'm actually looking at it right now - I'm at work, my Urbane is on my left wrist, and my phone is on the desk 20 centimeters away.
Since I haven't heard many others complaining about this, I'm suspecting the problem to be on the phone side - this is a "China phone", an Elephone P3000S (64bit, 3GB RAM) that I bought quickly as a cheap, but (on paper) good spec'd replacement for my broken Sony Z1 Compact.
But nevertheless, I thought I'd asked here if anyone else are experiencing the same?
I've factory reset the watch, I often reboot it, I reboot the phone even more often, and most of the time connection is re-established but lasts only for maybe 15 minutes up to several hours. I have disabled wifi on the watch to see if that improves things - initially I thought maybe it did (as long as I kept the phone nearby, of course), but after a while it seems it's not the case.
Anyone have any other tips? ...Before I replace the phone?
Thanks,
Christopher
*: of course I would prefer a brighter screen (when needed, i.e. outdoors), light sensor, better battery capacity, ...
Click to expand...
Click to collapse
ranf said:
Try to find out what Bluetooth version the phone has.
Click to expand...
Click to collapse
Guys,
Having the same problem as well..... I'm using a Nexus 6 with Bluetooth 4.1 which is also not so far away from my watch all the time..... Really don't know what's going on....
I don't have an Urbane watch (yet) but ran into this issue myself....I downgraded Android Wear on my phone back to 1..0.5 to fix my problem. To get the apk I am using now, see the link below. Before that, my watch would constantly disconnect from the phone for no reason. Best of luck to you all! The Urbane is the BEST looking smart watch out there IMO!
http://www.apkmirror.com/apk/google...roid-wear-1-0-5-1724356-android-apk-download/
Pietje_1985 said:
Guys,
Having the same problem as well..... I'm using a Nexus 6 with Bluetooth 4.1 which is also not so far away from my watch all the time..... Really don't know what's going on....
Click to expand...
Click to collapse
Same here. N6 running CM12.1. Bluetooth works perfectly with car, around home, other devices. I've tried every setting I can think of. Glad to hear I'm not the only one.
Have you tried enabling/disabling the wireless syncing option? I had similar initial issues, had to factory reset and I disabled Wireless Syncing (and deleted the cloud data).
I then setup the phone again and didn't enable wireless sync for a few hours so I knew the phone was setup and working only using Bluetooth.
I knew something was wrong as once the wireless Sync was disabled and the cloud info deleted, my watch said it had lost connection to the phone and I had to factory reset it (even through Bluetooth was enabled still).
I am having significantly more instances of Bluetooth disconnections on this watch that I did with the Moto 360. This especially occurs in my car while driving. I'd bet that the watch disconnects every 10 minutes or so in the car.
Same here ... I have an LG G3 running Lollipop with an LG Watch Urbane running v5.1.1 This is to replce my LG Watch R but these connectivity issues every 10 seconds is highly frustrating ... Looking forward to a permanent fix on this thread ...
I'm starting to see the same thing, no issue while both are on WiFi, but without WiFi my watch is constantly disconnecting. Normally rebooting the watch seems to fix the issue, but really hope this gets fixed soon.
If I get away from my phone watch disconnects, thats normal. But when I get close to phone again, it doesn't connect automatically, or connects too late. Is that normal? This is so annoying.
well im all good not had that at all i get about 25 foot then loose bt soon as im back in 25 foot im good
i have a edge
I have an SGS6 Edge and it is slow connecting. I've found it will connect instantly if I turn BT off and back on.
Has anyone tried using phones wifi terhering instead of bt connection? Maybe that extends the connection distance?
Seems like my problems are solved for the most part. Doesn't disconnect that often anymore. Could be because of recent update to Android 5.1.1 on my Nexus 6 and I factory resetted my urbane! Lookin' good now!!
How about you guys?
I have a Nexus 6P, and the disconnecting with my Urbane is beyond annoying. I'm starting to think that, despite the looks of the Urbane, the watch itself is a pile of poo.
Same issue here. Phone and watch constantly disconnect. If I walk 10 feet from my phone, it disconnects and doesn't reconnect when I come back within range of the bluetooth.
Pleased to report, though, that I went into Settings>Apps>Android Wear and cleared the cache and the phone has been reconnection pretty well. I have the LG V10 and the G3 before that and have found that you have the clear the cache on bluetooth connections every once in a while, and then things start to work smooth again.
Hope this helps someone out there.
I have been having the same problem since I got my new Nexus 6P. On my old phone, an Asus Zenfone 2, I would hardly ever lose connection. I might drop connection once a day. With my new phone, its about once an hour if I'm lucky. I just did a factory reset of both the phone and watch this evening, and so far it seems to have helped but I'm not going to call it fixed yet until I make a whole day without losing connection.
For what its worth, there are tons of people who are saying the BT on the N6P is boned, as well as a ton of people saying the same thing about the Urbane.
I have a Samsung Galaxy S6 and have both Bluetooth and Wifi connected to my LG Urbane however:-
If I go away from phone - within my own house AND well within Wifi range - it LOSES connections to BOTH Bluetooth and Wifi. (Bluetooth I can understand but how come it is losing connection to Wifi)?
Anyone got any answers please?
Anyone else experiencing GPS issues on the S23?
Sometimes it will work fine for a day, sometimes for a couple of hours. Then it stops.
Occasionally rebooting resolves the issue, but generally it doesn't. Yesterday I restarted and/or turned off/on 5 times without resolving. Some hours later, it just starts working again.
Looking at nmea loggers and GPS Test app, when it stops it either shows no data at all, or sometimes shows signal from just one or two and never finds any more so can't get position lock (other than network based). My old S20 right next to it will show 18-20 satellites at the same time and never faults.
I submitted a fault to Samsung. They said the uploaded system log showed nothing coming from GPS (fault was currently being exhibited) and phone will need to go back. This isn't always the case however, as sometimes it works OK.
Is there anything I can try before I send it off?
Have others had similar issues?
Try restarting in emergency mode (SOS) and do your tests.
If I were you, I would factory reset or even install firmware with Odin just to make sure everything is OK.
Send to Samsung is the last attempt.
Thanks for the suggestions. I'll give them a go and see what happens.
Calibrate your GPS in google maps. Tap your location and it had you move your phone around to increase its accuracy.