Hi,
I have a very annoying problem with the navigation with Google maps on my Huawei Watch in combination with my Xperia Z3. When I open maps without navigating somewhere, the map shows my location and is scrolling more or less in real-time.
As soon as I start navigating, the map does not show my location in real-time anymore. Every 10 seconds the map gets updated and in between nothing happens or moves.
Is do not expect this to be a feature so I suppose something is not working properly.
I have already tried to factory reset the watch and re-sync apps. Did not help. Maps on the smartphone is working flawlessly.
Does anybody else have this problem?
I think it just work that way. Annoying.
Wysłane z mojego HTC One M9 przy użyciu Tapatalka
SpoOokY1983 said:
Hi,
I have a very annoying problem with the navigation with Google maps on my Huawei Watch in combination with my Xperia Z3. When I open maps without navigating somewhere, the map shows my location and is scrolling more or less in real-time.
As soon as I start navigating, the map does not show my location in real-time anymore. Every 10 seconds the map gets updated and in between nothing happens or moves.
Is do not expect this to be a feature so I suppose something is not working properly.
I have already tried to factory reset the watch and re-sync apps. Did not help. Maps on the smartphone is working flawlessly.
Does anybody else have this problem?
Click to expand...
Click to collapse
Just a thought, have you tried using the android app 1.3? I know calls are delayed with the 1.4 app update and have read that 1.3apk will work. I personally haven't tried it, but it's worth a shot. Check to see if the apk will work below...
http://www.apkmirror.com/apk/google-inc/android-wear/
SpoOokY1983 said:
Hi,
I have a very annoying problem with the navigation with Google maps on my Huawei Watch in combination with my Xperia Z3. When I open maps without navigating somewhere, the map shows my location and is scrolling more or less in real-time.
As soon as I start navigating, the map does not show my location in real-time anymore. Every 10 seconds the map gets updated and in between nothing happens or moves.
Is do not expect this to be a feature so I suppose something is not working properly.
I have already tried to factory reset the watch and re-sync apps. Did not help. Maps on the smartphone is working flawlessly.
Does anybody else have this problem?
Click to expand...
Click to collapse
As far as I know navigation on watch is depending on two factors:
1. Bluetooth connection between phone and watch
2. The position of the phone becoause the gps function is performed by the phone, not the watch.
So, please try to keep your phone in a good position to "see" the sky AND close to your watch.
My Watch is lagging everywhere..
Force close 2/3 times a day..
every day at least 1 time is not reconnecting to the phone..
Any clue?
sartan said:
My Watch is lagging everywhere..
Force close 2/3 times a day..
every day at least 1 time is not reconnecting to the phone..
Any clue?
Click to expand...
Click to collapse
1.Factory reset your watch
2.check to have the latest version of android wear installed on your phone and watch
3. Is your watch heating?
calinormy said:
1.Factory reset your watch
2.check to have the latest version of android wear installed on your phone and watch
3. Is your watch heating?
Click to expand...
Click to collapse
No is not heating..
I try the reset..
sartan said:
My Watch is lagging everywhere..
Force close 2/3 times a day..
every day at least 1 time is not reconnecting to the phone..
Any clue?
Click to expand...
Click to collapse
I have the same problem!
I cant even use maps on my huawei watch because it rotates all the time.
I have tried everything but cannot get maps to work smooth in navigation mode. I will wait for firmware 1.4. Hope it will fix it.
It just does not work. commands are not communicated on time to be aware about direction. For car it is useless. Maybe if you walk it is fast enough, but i don't find it useful.
Related
I've been experiencing issues with the gps for a while. For starters, it takes a long time for the turn by turn navigation to start. Just the other day it kept repeating the same street even though I was no where near that street.
I use Google maps, I removed the att navigation, and I'm using the deodexed rom. fyi.
Anyone else experiencing issues?
Sent from my Xperia Codec
Bump
Sent from my Xperia GX
Auggy99 said:
Bump
Sent from my Xperia GX
Click to expand...
Click to collapse
So, i'm assuming your Ion is rooted? With stock GB on my Ion, i had some very strange gps related stuff happening for the first few days i owned it. I was constantly losing the ability to go into compass mode in google maps, and once that happened...it would not regain gps signal, it would just constantly 'seek' with the blinking icon. If i didn't mess with it for a few hours, it would come back for a bit...but then get lost again. It wasn't just maps, my tracks app wouldn't get a lock either. However, it was always related to when compass mode simply stopped working.
I dug around a little and found people claiming that the orientation sensors can interfere with gps connectivity, and any compass app will reset that within the phone when you install them. Sounded gimmicky, but it worked (i just downloaded the first free compass i found), and i haven't had a single problem since with GB...and after the ics update so far.
But if you rooted your phone, and it was working fine before, that could be the culprit...and i don't have feedback for that yet, as i haven't rooted yet.
So you just installed a random compass app and the navigation worked?
Sent from my Xperia
I've had the zenwatch for almost 2 weeks and i will be keeping it. That being said here is a heads up, i found that using the app facer to make watch faces and using wear mini launcher together causes a good bit of lag when performing any action on the watch. to remedy this issue i downlaoded watch maker and low behold the lag went away. so if anyone is haven a lag issue check into what apps you are use to make your watch faces and also what launcher u have choosen. hope you guys find this helpfull .
So, did you uninstall wear mini launcher ?
tonyguy2000 said:
So, did you uninstall wear mini launcher ?
Click to expand...
Click to collapse
no i switched to watch maker it works better with min launcher
I've actually had this happen a number of times and I'm not sure why. It doesn't seem to have a consistent cause. Usually it'll be when I install a new app or something, but it's happened other times as well, but it doesn't happen consistently with one app or another. For me, the lag shows up as the screen basically being frozen without being able to control anything. Eventually, it will unfreeze and I'll usually see the mini-launcher screen, but even a restart with the back button won't solve the freeze.
For me, it was worse when I had Mini Launcher installed, but it still happens occasionally without it. I no longer have either Facer or Watchmaker installed, either. I'm using the Weather Watch Face, though. I wonder if it has something to do with watch faces in general?
When I was using Mini Launcher, apps would almost never launch the first time I tapped on them. It would go back to the watch face and freeze for a few seconds, and force me to go back to Mini Launch and tap again. Without Mini Launcher, this still happens occasionally from the built-in Start... item, but much less frequently.
I have all 3 installed and it doesn't seem to lag too bad. I guess I don't interact with it the same as I would with a phone so it doesn't bother me at all. Whenever I get a card it interacts with it seamlessly, that's about as much as I need it to do
xmeatizmurderx said:
I have all 3 installed and it doesn't seem to lag too bad. I guess I don't interact with it the same as I would with a phone so it doesn't bother me at all. Whenever I get a card it interacts with it seamlessly, that's about as much as I need it to do
Click to expand...
Click to collapse
Interacting with cards hasn't been a problem for me, either, it's launching an app that's not already running that seems to be the issue. Sometimes (or almost every time for me with Mini Launcher), the new app doesn't come to the foreground, and the watch appears to hang for several seconds. It then has to be launched a second time to become visible.
I've definitely seen it lag like that. Hopefully it's just a software issue with android wear being so new and updates will help fix that. It's got plenty of processor and ram torrun the tiny apps no problem
I noticed a considerable amount of lag while using mini launcher. To the point that I didn't even want to show off the watch to other people because it made it seem terrible. Major difference since uninstalling, lag free now. I also use Watch Maker and a few Play Store watchfaces with no lag issues.
Wish we could move the start menu to the first selection on the tap screen instead of the last, then I really wouldn't care about a separate launcher.
1+ for deleting mini launcher. I like the app but its so dam laggy. As far as Watch Maker app works at times for me so I deleted that as well. I was using Facer until I ran into Intellicom which seems to be very easy to use and no change in my battery life.
I think this is more of a symptom of using a single core A7 processor. I imagine all of the governors and IO schedules are set up for battery life so that probably doesn't help either. It might just be coincidence that you are running something while a background task is also running.
I have had my M9 for just over a week and have been unable to use sat nav apps, because they crash randomly while I'm driving.
When I have used sat nav without having the phone connected to power at the same time then it has worked fine.
I was wondering if anyone else has noticed the same issue, could it be down to overheating perhaps..?? I can't think of any other reason why having the phone powered would affect the running of sat nav apps.
addancrah said:
I have had my M9 for just over a week and have been unable to use sat nav apps, because they crash randomly while I'm driving.
When I have used sat nav without having the phone connected to power at the same time then it has worked fine.
I was wondering if anyone else has noticed the same issue, could it be down to overheating perhaps..?? I can't think of any other reason why having the phone powered would affect the running of sat nav apps.
Click to expand...
Click to collapse
My M8 was doing this. I even cleared the data on Google Maps but still maps would randomly do "unfortunately, maps has stopped" while driving. My M9 seems to be working fine so far, though. I am not sure what caused it but I bet it is the same thing.
addancrah said:
I have had my M9 for just over a week and have been unable to use sat nav apps, because they crash randomly while I'm driving.
When I have used sat nav without having the phone connected to power at the same time then it has worked fine.
I was wondering if anyone else has noticed the same issue, could it be down to overheating perhaps..?? I can't think of any other reason why having the phone powered would affect the running of sat nav apps.
Click to expand...
Click to collapse
uninstall the google maps app from settings(uninstall updates) you will now have the factory version of this app, now download the latest google maps, the current version is 9.8.0 , get this one, not the x86 one. ive put the link down there . hope i helped
http://www.apkmirror.com/apk/google-inc/maps/maps-9-8-0-android-4-3-android-apk-download/
Sadly, it's not just google maps, it's any navigation app - Waze, Sygic etc..
addancrah said:
Sadly, it's not just google maps, it's any navigation app - Waze, Sygic etc..
Click to expand...
Click to collapse
Some people commented on the latest Android System Webview update that it has fixed their app crashes with the M8. You might try updating that if possible. Otherwise I'm not sure what would cause that to happen even after clearing the app data. Strange issue.
I've been using Ghostrace with a Polar H7 and Jaybird Bluebud X headphones. While running and listening to offline Google Play music, about 30-40 minutes into my run, the songs start to get cut short and a new one starts, then, eventually, everything freezes and I have to reset by holding the button. My ghostrace logs are recovered and I am able to get all my stats, but they are broken and not very useful. Also, doing this 3-4 times during a long run is REALLY counter productive. My songs, even from the beginning of a run, seem to not finish completely before it moves on to the next one. It is rather annoying when you are expecting your song to continue and it just stops mid way and a new one starts.
I've done a factory reset and re-downloaded all my music and it still seems to be happening. A
Any suggestions?
Getting worse now. Can only run about 10-15 minutes and it starts to happen and then freezes. Factory reset watch. Cleared cache on phone and redownloaded and installed everything. Still happening.
Hi, just trying to figure out whats causing this bug, though yours sounds different in that you have to reset. I've seen other reports of it just resetting on its own.
Anyway, what version of Ghostracer do you have? You can see on the watch, on the 3rd page down. Just wanting to find out if its a new problem I've created or if its something to do with the google play update the last month.
Cheers
Craig
cjkiller said:
Hi, just trying to figure out whats causing this bug, though yours sounds different in that you have to reset. I've seen other reports of it just resetting on its own.
Anyway, what version of Ghostracer do you have? You can see on the watch, on the 3rd page down. Just wanting to find out if its a new problem I've created or if its something to do with the google play update the last month.
Cheers
Craig
Click to expand...
Click to collapse
0.9.2
Don't really have a problem with Ghostracer. It seems to work fine. It appears to be a bluetooth issue (leaning this way since I started experiencing issues transferring files from my phone occasionally) or google play music issue since many times I haven't been using Ghostracer when the issue occurs.
Is it possible that sweat is the culprit? I have heard of people having problems with sweat during their runs messing up their SW3 - that's because although the SW3 is water-resistant, that applies to fresh water only, not salt-water like sweat. Try running with a sweat band under your watch and see if that solves the problem.
Colinmb said:
0.9.2
Don't really have a problem with Ghostracer. It seems to work fine. It appears to be a bluetooth issue (leaning this way since I started experiencing issues transferring files from my phone occasionally) or google play music issue since many times I haven't been using Ghostracer when the issue occurs.
Click to expand...
Click to collapse
Thanks for your info Colinmb, I was going crazy thinking I had broken something in the latest beta. So it looks like its a bluetooth problem created in the last update of the wear app/google play update, which came out around the 7th of November I think. Might make a post on the Sony site, see if anyone cares.
Problem solved with latest Google Play Services update.
Hi guys,
has anyone tried to use Shazam on the watch? It's not working for me. The app starts and I also get the Shazam animation, but it never identifies a song though the same song is quickly identified by the phone app.
I'm not quite sure how the animation should look like on the watch, but on the phone you can see the beat as spikes in the "spinning detection animation". (I hope you know what I mean)
On the watch the animation just spins but without any spikes. This made me wonder, if there is a problem with the microphone as it seems the app does not get any sound from the mic at all.
The mic itself is working fine for "Ok google" commands, so the hardware should be okay. This was the case before and after the recent update (LC43B).
Any thoughts?
Okay, it's working with the latest update of Shazam. ?
Gesendet von meinem SM-N910F mit Tapatalk
Shazam is not working for me ... on MEC23L and latest shazam update. sigh...
stoneule said:
Shazam is not working for me ... on MEC23L and latest shazam update. sigh...
Click to expand...
Click to collapse
Nor me
I have the problem again with the MEC23L update. However it's not the microphone or audio connection, that causes the problem.
When Shazam on my watch tries to recognize a song it always gives up with an error message saying it was unable to tag the song, but if I open Shazam on my mobile phone later on, I can see that the song is in the list of tagged songs, so it actually did work.
It seems that the feedback from the smartphone app to the watch is somehow not working properly anymore.
Please also check this on your phone.
I'm the original poster of this thread, but I don't know if it was the same problem with the old firmware as I did not check my phone for tagged songs back then. Is there anyone here who has no problems with Shazam?
I already tried to re-install Shazam on the mobile (and watch), but that did not solve the issue.
foo said:
I have the problem again with the MEC23L update. However it's not the microphone or audio connection, that causes the problem.
When Shazam on my watch tries to recognize a song it always gives up with an error message saying it was unable to tag the song, but if I open Shazam on my mobile phone later on, I can see that the song is in the list of tagged songs, so it actually did work.
It seems that the feedback from the smartphone app to the watch is somehow not working properly anymore.
Please also check this on your phone.
I'm the original poster of this thread, but I don't know if it was the same problem with the old firmware as I did not check my phone for tagged songs back then. Is there anyone here who has no problems with Shazam?
I already tried to re-install Shazam on the mobile (and watch), but that did not solve the issue.
Click to expand...
Click to collapse
True, i checked and the song is tagged and it is shown on the phone app, but for some reason it shows as failed on the watch
Guys if you are on update 1.4 go into your permissions section and under Shazam enable microphone and storage. Mine were disabled and thats why it didnt work for me. After I enabled them Shazam is working again.
deanesn said:
Guys if you are on update 1.4 go into your permissions section and under Shazam enable microphone and storage. Mine were disabled and thats why it didnt work for me. After I enabled them Shazam is working again.
Click to expand...
Click to collapse
The permission for memory storage was disabled for Shazam on my watch, but unfortunately enabling access did not solve the issue for me.But as you got it working, I'll try to re-install it and take care about the permissions before the first start.
I wonder why the permissions were disabled in the first place.
wollyka said:
True, i checked and the song is tagged and it is shown on the phone app, but for some reason it shows as failed on the watch
Click to expand...
Click to collapse
Ok it appears you are correct. Strange, that the songs are not showing up on the watch
foo said:
The permission for memory storage was disabled for Shazam on my watch, but unfortunately enabling access did not solve the issue for me.But as you got it working, I'll try to re-install it and take care about the permissions before the first start.
I wonder why the permissions were disabled in the first place.
Click to expand...
Click to collapse
Rebooted my watch and now back in the same boat with the one exception. The watch app stays open for like good amount of time and it will just close out but the tags show up under my shazam on the phone app. So it is kind of working just dont get confirmation of the tag on the watch.
This is still an issue for me ... Anyone else?
Sent from my SHIELD Tablet using Tapatalk
stoneule said:
This is still an issue for me ... Anyone else?
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
still an issue, I can't get shazam to pick up songs at the moment.
Shazam app updated yesterday and it appears to have fixed the issue with my watch.
I can finally tag songs from my Huawei watch
Can confirm, Shazam is working again.