I have a WiFi only galaxy tab and I was just wondering if I set up directions at my home on wifi, then go into navigation while on wifi, and then set off on the road connected to nothing, will the navigation still work?
Yes, your scenario will work. Only take care not to leave the navigation app pressing the back button.
Gotcha. I figured it will work, I figured Wi-Fi makes the route and then when im off wifi gps will just follow
Related
I have down loaded and am using two great cab files that I am now using on my Sprint TP. One is BT on/off, and the other is WIFI on/off. In particular I have mapped BT on/off to a soft key on my TF3d home screen (easier than having to take 3 steps to access comm manager) Quickly turn BT on and off (toggle).
Does any on know if there are any cabs out there that create a program icon to turn on, and turn off the Sprint data connection (toggle it on and off, like the sliding comm manager feature?
I would map it to another softkey on my TF3d home location. I am already aware of being able to terminate the data connection via the long press option quick list.
I like to turn off the connection, fairly quick after I use it to conserve battery.
I also posted this in the CDMA Threads
I have been using Google Navigation, which is a great app but which is a huge battery hog - particularly with the screen on.
(Lets assume for the moment I dont have a car charger available)
I understand that Google Nav can be used with the screen off, and the voice commands will still work. This helps significantly with the battery life.
At certain points I would like to actually see the map/screen, but in between can leave the screen off and follow voice commands.
Here is my question - currently if I turn off my screen by pressing the side power button, it should keep navigation voice directions active with the screen off (I think...correct?).
But when I press this button to turn it back on, it goes to my lock screen (in my case I use WidgetLocker). From there I would need to manually navigate back to the Navigator App. While driving, going through this series of steps is not ideal.
How can I set things up so that the screen times out or I switch it off with the power button, but that when re-activated it goes straight to the Navigation app screen with no needed intermediate steps?
I am on stock setup - not rooted.
Thanks.
lirong said:
I have been using Google Navigation, which is a great app but which is a huge battery hog - particularly with the screen on.
(Lets assume for the moment I dont have a car charger available)
I understand that Google Nav can be used with the screen off, and the voice commands will still work. This helps significantly with the battery life.
At certain points I would like to actually see the map/screen, but in between can leave the screen off and follow voice commands.
Here is my question - currently if I turn off my screen by pressing the side power button, it should keep navigation voice directions active with the screen off (I think...correct?).
But when I press this button to turn it back on, it goes to my lock screen (in my case I use WidgetLocker). From there I would need to manually navigate back to the Navigator App. While driving, going through this series of steps is not ideal.
How can I set things up so that the screen times out or I switch it off with the power button, but that when re-activated it goes straight to the Navigation app screen with no needed intermediate steps?
I am on stock setup - not rooted.
Thanks.
Click to expand...
Click to collapse
Try disabling Widget locker before entering navigation. See if you get the same results with the stock lock screen.
Sent from my SAMSUNG-SGH-I727 using xda premium
lirong said:
Here is my question - currently if I turn off my screen by pressing the side power button, it should keep navigation voice directions active with the screen off (I think...correct?).
But when I press this button to turn it back on, it goes to my lock screen (in my case I use WidgetLocker). From there I would need to manually navigate back to the Navigator App.
Click to expand...
Click to collapse
I use WidgetLocker.
If I turn the screen off using the power button, I still get voice commands.
If I turn the screen on, I get WidgetLocker and unlock it with the simple swipe, then I'm back at the GPS screen as if I'd never left it.
Hmmm that doesnt work for me. Could be because my WidgetLocker screen is covered with email, calendar, etc. So anywhere I try to swipe ends up taking me directly an app or an email, rather than just swiping off the screen...
Is there no way to set up so that for a particular app, lock screen / widget locker just dont activate so the phone goes from standby straight into the app?
CZ Eddie said:
I use WidgetLocker.
If I turn the screen off using the power button, I still get voice commands.
If I turn the screen on, I get WidgetLocker and unlock it with the simple swipe, then I'm back at the GPS screen as if I'd never left it.
Click to expand...
Click to collapse
You can configure widgetlocker to prevent clicks on those apps you have on the lockscreen
Sent from my SAMSUNG-SGH-I727 using xda premium
CZ Eddie said:
You can configure widgetlocker to prevent clicks on those apps you have on the lockscreen
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Thanks.
But most of the time I want that click through capability. I dont think I would want it to be off. I was just pointing out that this is the reason a simple swipe from that screen isnt feasible for me in getting straight back to Navigation...
Google Nav will overlay the built-in lock screen, but Widget Locker will show up. If you have a bunch of widgets that allow interaction you can try turning on the back button unlock in settings:
Settings->Buttons & Inputs->Back Button Unlock
You can then set the unlock delay to suit. That way you can unlock while in Nav without using the sliders.
This suggestion worked. Thanks very much for your help.
Thinking about it I guess if I had the space I could also add the Nav icon to WidgetLocker and get to it that way directly as well.
Appreciate everyone's input.
marvin02 said:
Google Nav will overlay the built-in lock screen, but Widget Locker will show up. If you have a bunch of widgets that allow interaction you can try turning on the back button unlock in settings:
Settings->Buttons & Inputs->Back Button Unlock
You can then set the unlock delay to suit. That way you can unlock while in Nav without using the sliders.
Click to expand...
Click to collapse
In order to connect my phone to an already paired device I have to drop the status bar, tap the BT icon then tap the desired device and then go back to the home screen. I find this quite annoying especially when I'm running errands and repeatedly enter and exit my car.
Why the stupid thing won't autoconnect is beyond me but what I'm looking for at this point is a shorter way such as setting up an anycut shortcut or something.
Any ideas?
crabapples said:
In order to connect my phone to an already paired device I have to drop the status bar, tap the BT icon then tap the desired device and then go back to the home screen. I find this quite annoying especially when I'm running errands and repeatedly enter and exit my car.
Why the stupid thing won't autoconnect is beyond me but what I'm looking for at this point is a shorter way such as setting up an anycut shortcut or something.
Any ideas?
Click to expand...
Click to collapse
This is getting very annoying. Can't imagine we are alone in this.
My GPS is in an always ON state, I have the power control widget on my home screen to confirm that.
However, sometimes, when I start Waze, it seems that GPS is not enabled, there's no gps icon on the top left. I will need to go to the home screen, toggle the gps Off then On using the Power Control, then go back to Waze, and then now I get the GPS icon on the top left.
Anyone experienced the same thing?
Nexus / Play Edition Devices - Keyguard => Home Button and Top of Screen Unresponsive
When I installed 5.1.1 on my Nexus 7 mounted in my car, I noticed a weird bug with Car Mode Control being activated - the home button would freeze up the screen, locking it on an all black screen, and the status bar along with another 10% from the top of the screen was unresponsive to touch. Now, I know there are issues with Nexus devices running Car Mode apps, but without reinventing the wheel (or at least having to code a ton more stuff into Tasker), it's the easiest way for me to send up accompanying things, like Car Home Ultra and activating tethering, etc.
But this is just obnoxious. I can barely get the search bar to work on Google Maps, I have to hit just the very bottom of the bar to get it to open up the recent searches and allow me to type, and most 3-dot menus cannot be hit anymore. When I got my Moto X Pure, I noticed the same thing was happening, so it wasn't A) the Nexus 7, B) Car Home Ultra, C) at one point I even considered it was Nova Launcher, but rather D) just being in Car Mode. The MXPE comes out of this state easily enough with doing a screen off and back on, but the N7 does not - I either have to disable wifi tethering which disables car mode on the N7 via a Tasker task, or restart it in some extreme cases. I have Car Home Ultra on my N7 but not my MXPE, so the suggestion that it has something to do with a bug in the home button override of Car Home Ultra doesn't hold water, unfortunately (thought of that as the culprit already too).
I think this may be a "safety feature" of Nexus / PE devices that if car mode is activated, you can touch certain things and go back home, but if I can't pull down the status bar, I can't set car mode off unless I turn off my car, which kills Bluetooth and my Tasker task to keep my phone in car mode when connected to the car's BT. NOT ideal for someone who drives 1,000+ miles per week for work and needs to check and send emails while I'm stopped waiting for my next assignment to start (insurance related career). I find it even more absurd that not only is the status bar blocked from access, but all apps just below that as well, including the search bar on Google Maps as I said already. How am I even supposed to search for the next destination without being able to access that bar easily?
===========================
TD;LR - Nexus and Play Edition devices don't like Car Mode being forced on them through apps that turn on car mode, it makes them unresponsive to certain parts of the screen and doesn't allow the home button to work, is there any way to enable car mode without having to build a Tasker task that does what car mode does for me?
===========================
EDIT - Figured it out.... I had Tasker setting Keyguard Off instead of using Secure Settings to clear password when connected to the car's Bluetooth as detailed here. I've read previously that setting the keyguard off has had adverse reactions inside Android, but I didn't connect the dots here, these are the issues that occur when you set keyguard off! So yes, using Secure Settings to clear password works much better and doesn't produce these crazy bugs.