Related
I used to do this all the time on my TyTN 2, but I still haven't been able to get it working on my N1. I use GPS to navigate on my bike, where I can't plug it in to charge and there is no cradle. I keep my phone in my pocket, and listen to the directions in one ear on my headphones. It was pretty easy to turn off the screen of my WM and keep the GPS running, keeping the battery use down. On my N1, I haven't found any way to kill the screen without killing the GPS app. This makes it impractical for navigating around Jakarta, where I might kill my battery sitting in traffic with the screen on. Is there any way to turn off the screen without locking everything up?
Thanks for your help.
this annoys me too, and i both love it and hate it. currently there is no way you can do this without altering the maps code. the onPause obviously seems to be programmed to suspend the GPS signal when activity loses focus, and nothing short of changing that code i imagine would fix this issue.
though i do commend google for how they set android up to function this way, its different and novel, but i dont ALWAYS necessarily like it, like this situatino in particular.
I don't understand the problem. I turn the screen off all the time.
I don't have a car dock, so I start navigation and place the phone on the seat beside me, I turn the screen off to save battery and then just listen to the directions all the way to my destination.
Never had a problem.
And I've used the My Tracks program to track my mountain hikes, screen off and in my pocket.
Both ways worked both before and after I rooted and installed CyanogenMod.
Clarkster said:
I don't understand the problem. I turn the screen off all the time.
I don't have a car dock, so I start navigation and place the phone on the seat beside me, I turn the screen off to save battery and then just listen to the directions all the way to my destination.
Never had a problem.
And I've used the My Tracks program to track my mountain hikes, screen off and in my pocket.
Both ways worked both before and after I rooted and installed CyanogenMod.
Click to expand...
Click to collapse
weird everytime i've turned off the screen i believe the GPS disconnects, which can be seen as soon as the screen is turned back on and it reaquires the lock. even in maps if it briefly lsoes foreground focus the GPS signal stops. perhaps i never tested enough during actual navigation, but i thought this is what happened to me. hmmm
Well, try Navigation and My Tracks. I've gotten some pretty detailed longer (3-5 hour) hikes mapped. The screen was off the whole time.
And I've probably used Navigation with the screen off at least 10 times. And some trips over 30 minutes. It always told me when to turn at the right time.
The GPS turns off if maps isn't in focus and I'm glad. It would kill your battery if it ran all the time. But it caches your location and automatically turns GPS on when you open the app.
But if you start navigating the only way to get it to stop is by hitting Menu-Exit Navigation. Locking your screen is okay. I do it all the time.
Sent from my HTC Glacier using XDA App
Sounds like it isn't a system level problem then.
Navigation will lock the GPS on for you so turning it off isn't a problem.
The same with My Tracks then too.
So to the OP, if the program you are using is not forcing the GPS to stay on when the screen is off, you could try contacting the developer and asking for that option.
Ok I just tested this and I was wrong, when the screen is off the lock stays in tact completely and same accuracy. So if does indeed work. This was tested running navigation in maps.
I guess I should mention that I'm using igo. It was the first program I found with offline maps available for Indonesia. When I turn the screen off, it definitely loses its lock and has to search again when the screen comes back on. So, it sounds like switching programs should solve my problem. Is that right?
Edit: just opened navigation, and it says it's not available here yet. I might just have too bring my WM with me when I need navigation on a ride. Oh, well; by this time next year I should be back in the states where features aren't geographically blocked. Thanks for your help.
Sent from my Nexus One using Tapatalk
ill_dawg said:
I guess I should mention that I'm using igo. It was the first program I found with offline maps available for Indonesia. When I turn the screen off, it definitely loses its lock and has to search again when the screen comes back on. So, it sounds like switching programs should solve my problem. Is that right?
Edit: just opened navigation, and it says it's not available here yet. I might just have too bring my WM with me when I need navigation on a ride. Oh, well; by this time next year I should be back in the states where features aren't geographically blocked. Thanks for your help.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
yeah it seems to depend on how the developer coded the app you're using. google maps navigation seems to leave the GPS on with the screen off. the app you are using must not, but maybe you could contact the developer and ask them to change this?
Good morning. I have been having a particular, repeated issue since the last google maps update (7.0.2). Whenever I get into my truck I put my One in the OEM dock and it goes into "car" mode. Overall I love this app and find it incredibly efficient at doing its job.
However, since the last update from Google maps (which is also pretty indredible) I have been having a very specific error, that I believe is related to HTC's car mode. If I start navigation though the car dashboard and some event happens that pulls it from navi to the dashboard (i.e. a call comes in or a message) then when I return to navigation it again asks me to select the destination and I have to hit start. This will cause a "maps stopped working" error about 75% of the time.
What I believe is happening is that maps is already navigating but when in car mode you have to click on the "navigation" icon to get back to it, and it tries to launch another instance or over itself. This will also happen if I start navigation while not docked (i.e. walking to my truck) and docking, then launching the app. Also, maps is the one app that actually leaves car mode (you can see the system tray and then navigate to other non car mode apps) and I believe this is the root of the issue.
Since the car mode is (I believe) part of Sense, this would seem to be something specific to this. I thought there would be lots of inquiries into this but could find none. Thoughts?
I'm getting this too. It's deeply annoying and quite dangerous when going down the motorway. Considering going back to previous version.
Sent from my HTC One using xda app-developers app
It's an issue with the new Maps app. It sucks balls. I have those issues and I don't have the car dock.
Take a call or something else then when you try to go back to nav by selecting it from the notification panel, it does nothing or crashes or takes you to regular map and have to restart your route.
I hate it. It's pretty but so buggy. I reloaded the old version.
Sent from my HTC One
HTC car mode and Google maps
I am also having same problem. UN installed update and gone back to the much better old version
I've had my new Seat Leon for a week now and have been using Android Auto a little in this time. I really like it but it seems buggy. For example when using maps, the images will freeze, only updating every couple of minutes. When you are trying to follow an on screen map while travelling at 60mph, this can be very annoying. The other bug I seem to have is that my car seems picky when connecting to my phone (Nexus 5) sometimes. It will say 'not compatible' and will refuse to connect. The only way to solve these two issues is to restart my phone and sometimes to also toggle the USB debugging check box.
Is there anywhere to report bugs to Google? I'd like to help the community in ironing out these issues.
nimdy said:
Is there anywhere to report bugs to Google? I'd like to help the community in ironing out these issues.
Click to expand...
Click to collapse
Open the Android Auto app.
Tap the 3 dots at top right.
Select "Help & Feedback" and then select Feedback at the bottom.
I'm honestly not sure it will help too much though. There are no idle employees waiting for problem reports who spring into action at a new report.
But if Google sees 100 reports of Problem X, it might move X a bit higher in their priority list.
The freeze problem is actually new to Android Auto, and it started for me on July 31th. Google changed something server-side because even two clean installs didn't solve the issue, and it was working flawlessy until that day. No solutions found so far, had to switch to an iPhone to navigate. Read my report here:
http://forums.androidcentral.com/as...-5-android-auto-lags-when-using-gps-maps.html
themcfly said:
The freeze problem is actually new to Android Auto, and it started for me on July 31th. Google changed something server-side because even two clean installs didn't solve the issue, and it was working flawlessy until that day. No solutions found so far, had to switch to an iPhone to navigate. Read my report here:
http://forums.androidcentral.com/as...-5-android-auto-lags-when-using-gps-maps.html
Click to expand...
Click to collapse
That seems to be the same issue I'm getting. But strangely this isn't happening all the time. The pattern seems to be when I connect the phone to the car, set up the Google maps navigation, stop and disconnect the phone (for example getting lunch on my way into work), then connect again and continue the navigation. When connecting for the second time I get the issue whereby the refreshing doesn't seem to happen. As you say in your other forum post, this seems to update when you touch the screen.
Hopefully if this bug has only appeared in the last few days, hopefully someone will spot it and report back to get a fix. I've written a brief feedback note saying that I have found a bug and am interested to help them get it fixed!
I see a lot of people having problems with certain phones. I have Note Edge and never a problem. My wife has a s6 and used to have problems about 10 minutes into a drive (Black Screen, no control, most other probs mentioned here). Read somewhere if you load the "Android Auto App" on the phone first and then plug in. She has never had a problem Since. Something happens on App load that is not happening on "Auto Launch on detection" (My gut feeling is something to do with bluetooth). Just wanted to pass it along for those people having issues. I am sure google will fix at some point but give it a try and see if it solves your issues. It did ours.
nimdy said:
That seems to be the same issue I'm getting. But strangely this isn't happening all the time. The pattern seems to be when I connect the phone to the car, set up the Google maps navigation, stop and disconnect the phone (for example getting lunch on my way into work), then connect again and continue the navigation. When connecting for the second time I get the issue whereby the refreshing doesn't seem to happen. As you say in your other forum post, this seems to update when you touch the screen.
Hopefully if this bug has only appeared in the last few days, hopefully someone will spot it and report back to get a fix. I've written a brief feedback note saying that I have found a bug and am interested to help them get it fixed!
Click to expand...
Click to collapse
BPryde said:
My gut feeling is something to do with bluetooth.
Click to expand...
Click to collapse
Yes! If something fails with Bluetooth, then the AA connection disconnects. I hope Google fix this soon.
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
fredphoesh said:
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
Click to expand...
Click to collapse
they broke ok google about a year ago, very sad.
SOLUTION!
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
fredphoesh said:
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
Click to expand...
Click to collapse
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
I had this problem, disabled Bixby, works properly now.
Sent from my SM-N950U using Tapatalk
Liface said:
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
Click to expand...
Click to collapse
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Mine get borked every time I toggle between power saving modes. I like to use Extreme power saver for overnight and Medium mode at work.
Medium mode straight up breaks OK Google. Not sure if this is by design or a bug, but it just will not hear me.
Coming out of either mode (and extreme is the worst) and neither "Hi Bixby" or "OK Google" work until I do another full reboot. Sometimes I have to reboot then go back into Google voice setting to switch the option back on manually. If I try to do this before the reboot the option is greyed out and I can't move it. Sometimes just the reboot is enough.
It's random as hell and extremely annoying. I have submitted the bug to Samsung via the feature in the Samsung Members app, but that was over two weeks ago and has seen no response.
Interesting post. My wife's OK Google voice doesn't work but mine does. Both USA T MO version. With works I'm referring to having the Google widget on home screen and saying the sentence OK Google. Mine responds and hers doesn't. With screen ON.
Sent from my SM-N950U using Tapatalk
fredphoesh said:
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Click to expand...
Click to collapse
That's not it, I rarely use battery saving mode and this happens 100% of the time.
Ok google for me just does not work.
Anyone get a fix for this?
"Ok Google" works when screen is on, but if I say it while the screen is off, it makes the noise and I get edge lighting indicating it's listening, however it doesn't respond and when I manually turn on the screen assistant is open saying "can't reach Google at the moment."
Power saving mode is off, tried disabling Bixby, clearing cache, nothing.
Hellothere37 said:
clearing cache, nothing.
Click to expand...
Click to collapse
so clearing cache of Google app and rebooting did not help at all?
bizarre, that fixed it for me...
I have a UK version.
I'd phone Samsung!
I'm frustrated too because I can't figure out how to use it while in power saving mode. I thought I added it correctly in the optimized battery usage apps (disabled google, ok google enrollment and voice assitant there). I can't see it as an option to select under unmonitored apps. Any idea what I'm missing?
Thanks for any help
This is strange to hear. Mine has worked flawlessly, as good as my pixel XL. Screen off and locked or not. I say ok Google, phone unlocks, and then I ask it whatever. Only thing ive done is disabled bixby by way of BK disabler.
Sent from my SM-N950U using Tapatalk
May be coincidental but I have not the slightest problem, and yeah, I uninstalled the Bixter. One thing I have read somewhere or other is that the OK Goog command is also subject to the level you set for Bix. In other words with sensitivity turned down for Bix it's also turned down for Goog. I never tested that one but might be worth looking at...
gingi999 said:
they broke ok google about a year ago, very sad.
Click to expand...
Click to collapse
So two things I wanted to mention the first one was my old phone case actually covered one of the microphone holes. Meaning the cut-out wasn't there so I used a drill and made a hole and it fixed part of the problem.
I have to be honest with you the Note 8 solved all the OK Google problems that I was having the past. For example the lockscreen didn't used to work and it works now I mean it was really a piece of trash with my Galaxy S7 Edge and now I can't imagine living without it.
Having problems like the first post where google assistant/ok google is non responsive all around. I've noticed that if I clear cache and data it falls back to just "ok google" and it work all the time. If I activate the google assitant with ok google it fails immediately. Who can fix this?
Looking around is there a GPS problem with the mi 8
Nope.
There was a permission related google maps issue. Workarounds were either uninstalling google maps updates / installing an old version via apk or revoking google location access, and then starting google maps again and allowing location access again.
There is. I have issue with GPS. Not Google maps. No App that uses GPS is getting coordinates some time. And when that happens, compass is non functional. It is frozen on some angle, no matter what i do. Also gravity Sensor (for fliping screen, on YouTube for example) is non functional. And when i try to reboot phone freeze on Black screen and i must force reboot by holding powerbutton for 10 seconds.
Yeah that's not a general issue or known bug.... somethings wrong on your device.
But it is software Bug on mine device. Right after reboot everything works as expected. After some time (3 to 5 days) it goes bad. I have the phone for around one month. I didnt do any mods only updated everything to latest version. So i think it is bug.
Search around, there's a couple things you can try.
.) Edit/fix agps settings
.) Fix google maps through revoking google location access
.) if all else fails factory reset
*edit*
https://forum.xda-developers.com/mi-8/help/issue-mi-8-gps-t3822926/page9 read this thread backwards
It is very rare. First time i have noticed it when i started waze and for 5 minutes it doesnt showed movement and i was going 130km/h. After quick reboot with powerbutton hold sorted it. Then in 3 days i couldnt rotate YouTube video. And i had a little time so i looked it up, and compass showed 349 degrees no matter what direction phone was pointed. And i also checked GPS test App, and 0 satellites were available. That all was week ago. Now everything is working fine. And i also noticed one small problem. When phone switch from 4G of home provider to roaming 2g or 3g data wont work. I need to activate airplane mode for a while, then it register again in roaming network and it works fine.