Can I have head unit server to run always? - Android Auto General

Hi guys.
Im testing the apk to use android auto wireless (aagateway created by a another user. I take no credit for creating). Aagateway.apk needs Android auto head unit server to be on all the time, which I have to activate manually, which is quite annoying. I also tried automate.apk to make things happen automatic, when getting into the car, but doesnt work as intended. Is there a way to have the server not shutting down?. Hope I make myself clear enough

You can use the automate.apk to start (or stop) Hotspot and HeadUnit server by the SU (Shell command superuser).
Need Rooted the phone.

Related

[HOW-TO] Get 4g Hot Spot (Infrastructure) to work after MOD'ng

Ok,
So, I, along with a few others, pay for the Unlimited Mobile HotSpot and want this app to work as other (root) tethering apps only allow Ad-Hoc.
Here's what I did to get it to work on my Windows 7 x64 Computer as of just a few moments ago and I do plan to work on this issue to get this figured out.
I've discovered that the /data/misc/dhcp/udhcpd.conf file is what controls the DHCP addressing for the 4gMobileHotSpot App. Within this app, I discovered (in the Modded ROM (as of now, I have Gingervolt1.1)), that the "Option DNS" addresses were completely wrong. This was apparent from the get go as they were internal IP address starting with 192.168.x.x.
The steps to get this app working on Windows is:
0 - Be Rooted (Sorry, just had to point the obvious out in Step 0)
1 - Use the market and download/install the Text Edit (Paul Mach) App
2 - (TESTed and Working), Use AntTek (root) Explorer and navigate to:
/data/misc
3 - Long Press the udhcpd.conf file and select to open with the Text Edit App
4 - Change the 'option dns' from 192.168.x.x to 66.174.92.14 69.78.96.14 and save/exit
5* - In Windows, set the IPV4 Properties to:
Use Following Address:
IP Address: 192.168.1.5 (or anything in between start and end range in text file)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Use Following DNS server addresses:
Preferred DNS Server: 66.174.92.14
Alternate DNS Server: 69.78.96.14
6 - Start 4gHotSpot App
7 - Tell Windows to Connect and you should be connected.
NOTE: It is late and I know that this will become clearer as time goes on and since I have to work in the morning, this is the best I came up with in a few minutes after figuring out that the hang up was with this file, in which I knew it's been a DHCP issue all along. Why this file is changed with the Modded ROMs is beyond me and I doubt MT changed this, so likely it is something to do with the DE-odex or some other modification of this app and it's initialization. Just deleting the CONFIG file will only cause it to write a new one with the wrong values again.
For those who do use this app, it is known to stop responding at times and I am going to look into that. I'm thinking this is a DNS issue and will try some other DNS Servers (8.8.8.8 I believe is a Google public DNS)..
In the meantime, this is a start for anyone to add to this that has more DHCP/DNS/Network experience. I don't have another android device handy to test the connectivity, so will have to get that figured out.
Key point here is, is that the 4gHotSpot App gets corrupted with the Custom ROMs and for some reason sets up wrong DNS servers in the Config file.
Hope to see some thoughts, additions, fixes, to this problem with this being pointed out, from others. I will continue to work on it throughout this next week after work.
Last Note: The DNS server numbers came from the original Config prior to rooting/modding. Also, I do know that is it redundant to have them in the config file AND the Windows Properties. It's just that setting Windows to 192.168.1.1 (option router in the Config file) didn't work. Again, will work on cleaning this method up and simplifying.
-Cybie
Thought I would give this a try today after re-rooting. I had no luck getting connected with the 4g hotspot app.
On my phone the file was in /data/misc/dhcp/ and the values were already correct in the file.
I tried changing the dns to a public one and back - neither worked.
I tried moving the file to /data/misc and it didn't work.
My ipad seems to connect ok but hangs trying to lease an ip address. Reloaded v6 tot and upgraded to non-rooted gingerbread and the app works again.
Is it possible you changed something else?
I'm glad it's working for you. Wish I could get it working as this is the only thing keeping me stuck on a non-rooted phone.
displacedbuck said:
Thought I would give this a try today after re-rooting. I had no luck getting connected with the 4g hotspot app.
On my phone the file was in /data/misc/dhcp/ and the values were already correct in the file.
I tried changing the dns to a public one and back - neither worked.
I tried moving the file to /data/misc and it didn't work.
My ipad seems to connect ok but hangs trying to lease an ip address. Reloaded v6 tot and upgraded to non-rooted gingerbread and the app works again.
Is it possible you changed something else?
I'm glad it's working for you. Wish I could get it working as this is the only thing keeping me stuck on a non-rooted phone.
Click to expand...
Click to collapse
Ok, so here's what I did after reading your post:
1 - Corrected the path (Sorry, it was late and I missed that /dhcp portion of the path).
2 - Deleted "option router 192.168.1.1" from udhcpd.conf file
3 - Deleted "option dns x.x.x.x x.x.x.x" from udhcpd.conf file
Set Windows up with the Following:
Static IP : 192.168.1.2
Subnet : 255.255.255.0
Gateway : 192.168.1.1
DNS Servers : 4.2.2.1 & 4.2.2.2
That worked.
So, what I am seeing if I try to use DHCP on Windows is that the 4gHotSpot gives the computer 192.168.16.x addressing even though the config file is set to give out 192.168.1.x addresses (x=2 through 254). It also gives Windows 3 DNS servers that are local IP addresses and will never go anywhere.
What to do now? Figure out what is being changed with the Custom ROMs that is causing the app to act like that. In fact, it will act like that when I restore back to Stock GB Rooted via restore from backup in CWM, but I have yet to test deleting the config file and restarting 4gHotSpot to test. I will do that over the weekend as I don't have a lot of time I can have my phone down during week. But I do plan to up to the GingerVolt1.3 tonight.
As of right now, I am using my windows machine connected to the 4gHotSpot App to write this post. Also, I don't know about the iPhone/iPad and possible settings. If you can Force (Set a Static IP) then follow what I did up above, but you will also need to set the DNS servers and not sure you can do that on an Iphone/iPad.
The DNS Servers I listed are found on a public list and are also said to be Verizon DNS servers...
The other problem I found and is an issue with the app, is using auto b/g/n will cause the hotspot to lose connectivity. When in that mode, I connect at 65Mbps, but it drops down to 6Mbps and stalls and fluctuates. I set it to 'g' only and get a SOLID 54Mbps connection just like the tether apps.
SPEED TEST Results: 18.35 Mbps Down, 10.66 Mbps Up without a glitch.
Obviously this app works with DHCP addressing as STOCK. So, I will begin my Android Development with figuring out one of two things. Either get this app to work as it's supposed to, or create a root app with 'Infrastructure' based on whatever I can find in the coding for this app if I can figure out a way to decode it.
I personally hate the idea that you can't connect other android devices to AdHoc and also annoys me to have to manually connect Windows since it doesn't seem to have the ability to automatically connect to AdHoc Networks. Linux does perfectly fine with auto connect AdHoc, go figure. Android is Linux Based, yet can't AdHoc, but provides an AdHoc as an access point for other devices. weird, lol.
Let me know if any of this helps, but do know I am going to continue to figure this out. I'm sure de-odexing the app had something to do with it as I'm sure Verizon did their best to keep this app from being hacked for free HotSpot service.
-Cybie
Thanks for the detailed response.
I'm going to try again. I won't be able to try until tonight or tomorrow morning when I have time to play with it and roll back if necessary.
I'll let you know if it works or I find out anything else.
Before you install a ROM and have the app working, try connecting your computer and get the values (ip, dns, gateway, etc.) That the app dhcp assigns and post that. Rooting the phone alone shouldn't break the app either. By getting those values posted, would help and also save me from downgrading just for that purpose. Knowing that it works with without a mod is one thing,. So my focus is working on getting it to function with a modded ROM.
It's strange that i can get the app to work if i force the connecting device to values (static settings), but this doesn't help with certain devices and needs to connect via dhcp.
-Cybie
Sent from my VS910 4G using XDA App
from unrooted:
ip: 192.168.1.2
subnet: 255.255.255.0
router 192.168.1.1
dns 66.174.95.44, 69.78.96.14
search domains: local
Still haven't retried the root and may need to wait another day or so until I have some more time
displacedbuck said:
from unrooted:
ip: 192.168.1.2
subnet: 255.255.255.0
router 192.168.1.1
dns 66.174.95.44, 69.78.96.14
search domains: local
Still haven't retried the root and may need to wait another day or so until I have some more time
Click to expand...
Click to collapse
These number are from your connected device? What device are you connecting that give you such numbers? I'm not familiar with the iPad and how it displays connection details. Is that what that is from?
I'm still able to connect after updating to GingerVolt1.2 and manually installed 4gHotSpot app. I just got home with little time to work on this project for the night, so I will update what I can if any changes in getting things to work.
-Cybie
those numbers were from an ipad connected via dhcp.
I'll see if I can use a laptop at work today to see the values I get connecting from a laptop. Should be the same I would imagine.
I will retry rooting the stock rom tonight and see what happens.
displacedbuck said:
those numbers were from an ipad connected via dhcp.
I'll see if I can use a laptop at work today to see the values I get connecting from a laptop. Should be the same I would imagine.
I will retry rooting the stock rom tonight and see what happens.
Click to expand...
Click to collapse
Sounds good. Those numbers will help.
I will add, though, that someone posted a way to get the wifi tether to work with the Revolution, here in the forum. The problem, though, is that it's connection via 'n' mode, which would be great, except it drops out. If you try to download something that's fast (or going to speedtest sites), you will find that that happens and what everyone is complaining about the HotSpot app not working. All that needs to be done is changing it to 'g' only mode and a solid connection.
Anyhow, I will see if I can figure out how to get that app working on 'g' only mode also, and if I do, then I will just use that app instead. Otherwise, I plan to continue to figure out the 4gHotSpot App
-Cybie
Cybie,
Glad to see someone's tackling this...I don't suppose your work here could be applied in a way that would make this app work for those who don't pay for the mobile hotspot?
I am waiting on a replacement Revo to arrive in the mail, should be here tomorrow or Saturday. Any values I can pull that might be of use to you before I get happy with flashing roms, rooting, etc?
I find that the OpenDNS nameservers tend to work pretty well everywhere I use them, if you wanted to give them a try:
Primary: 208.67.222.222
Secondary: 208.67.220.220
jamRwoo said:
Cybie,
Glad to see someone's tackling this...I don't suppose your work here could be applied in a way that would make this app work for those who don't pay for the mobile hotspot?
I am waiting on a replacement Revo to arrive in the mail, should be here tomorrow or Saturday. Any values I can pull that might be of use to you before I get happy with flashing roms, rooting, etc?
I find that the OpenDNS nameservers tend to work pretty well everywhere I use them, if you wanted to give them a try:
Primary: 208.67.222.222
Secondary: 208.67.220.220
Click to expand...
Click to collapse
Sorry for the delay. Been working extra hours at work and haven't had the energy to do much with this past couple days.
Anyhow, no, I don't intend to try to get it working for those who do not pay. Why? There are apps out there for this and the only reason I was trying to get this to work properly was for the fact that it would be nice to have the proper connection for those who do pay. I say that because the HotSpot app actually has a faster wifi connection (using n mode) than the tether (root) apps out there, with the exception of the one posted at:
http://forum.xda-developers.com/showthread.php?t=1339150
Unfortunately I am having the same issue with the HotSpot and that app (using infrastructure mode) when connecting. They both to link up at 65Mbps. In fact, I got 72Mbps with the wifi Tether app from the link, but like the HotSpot app, I have issues with the connection dropping out using 'n' mode.
The HotSpot app will allow you to set it to 'g' only mode, though only get a 54Mbps link speed, but sustains a solid connection with no drop outs. Others say they don't have that issue, so it may just be my wifi adapter??? I am going to test it on my laptop, but if I remember, I did have that same issue with the laptop, so maybe it's just my phone??
Either way, I am going to be doing what I can to get 4gHotSpot to work correctly with rooted/modded ROMs. Strange thing is, rooted, it still works fine. After installed modded ROM, it fails to work. And if I restore back to factory rooted via CWM, it still doesn't work. You actually have to restored/flash back to total stock. After that, you can root with it working, but not after installing a ROM.
-Cybie
Any luck with the fix?
OK, so I read that your hotspot worked fine after rooting, but stopped with the ROM was changed.
I rooted my phone yesterday, using the one button method. I have not modified the phone beyond this change. As far as I can tell the only functionality problem I have is with the hotspot.
The tether method continues to work (as I am using it right now). The hotspot does make a wifi connection to my devices but there never is any received data from the network.
Please help, any ideas on what I should look at or change?
Thanks ahead of time.
Steve
ALTANertive said:
Any luck with the fix?
Click to expand...
Click to collapse
I've been doing testing. Please read below for some more of my findings.
sgschwend said:
OK, so I read that your hotspot worked fine after rooting, but stopped with the ROM was changed.
I rooted my phone yesterday, using the one button method. I have not modified the phone beyond this change. As far as I can tell the only functionality problem I have is with the hotspot.
The tether method continues to work (as I am using it right now). The hotspot does make a wifi connection to my devices but there never is any received data from the network.
Please help, any ideas on what I should look at or change?
Thanks ahead of time.
Steve
Click to expand...
Click to collapse
I've noticed something very strange with the HotSpot and Rooting.
If you root, the HotSpot continues to work. But, if you reboot after rooting, that's when the failures begin. So, I am thinking that the files are being overwritten. I've been able to test with clean root, root with tether app, and restore without root.
Without root, the HotSpot continues to work fine as I have been using it for the past two weeks as I need it for my new WiFi Tablet. There is the WiFi app the allows for Infrastructure, but that also allows devices to connect via N-Mode, where I have issues of the data dropping out. Forcing b/g only on my HotSpot app, I have very reliable service.
I am planning (after my trip) to root my phone, copy some DHCP files before ANYthing can be changed and before rebooting. Comparing these files and seeing if anything changes there. If so, that will allow me to create a simple app to restore these files back to stock, either automatically, or through 'starting' of the app.
I haven't forgotten about this issue and It's something that I am needing to figure out. The problem is time right now. For the past few months, I had to work a job in order to keep bills paid. That job took a lot of my hours I used to have to figure things out. I am going to be having limited time available, but do plan to work on it some more in the next few weeks, especially since i want my Tablet to work flawlessly with my phone, as that is my ONLY source of internet and I DO pay for the HotSpot service.
-Cybie
Thanks for the update.
Like you I also pay for the 4g hotspot. I jumped on it when they offered the unlimited for $30.
Now that I've tried the gingervolt rom and the supercharger script I don't think I can go back. It just feels like a totally different phone.
I haven't had as much need for it recently so I haven't tried one of the other tethering apps.
Thanks for plugging along on this.
Yes, thanks for looking at this.
Here is some more observations:
Using your set ip and other setting I can get the hotspot to work. Two of my devices are not able to set a fix address without rooting them. So they do connect but only my PC will download a web page.
Here is the address my Revo is setting on the other two devices: 192.168.16.30 and .31.
Ok, so here's an update to this issue.
I have tracked the problem down to a failure to write to the udhcpd.leases file within the /data/misc/dhcp folder.
So, I did some searches on the net about a few things, but there's not much information regarding the "paid" HotSpot feature vs the (Root) Tether Apps.
What I did comes across, though, is there seems to be some sort of issue with certain versions of busybox relating to the udhcpd.conf. I also found the file that gives the 192.168.16.x addresses. But, by the time I found it, the phone already goofed up the HotSpot app settings and things weren't working. So, next round of factory restoring via LGNPST/Tot, I will seek into that and see what I can find out.
It's weird that the 4g HotSpot app will work flawlessly on the initial boot (Rooted, ROM'd, and even OC'd). But, after a reboot of the phone (once or twice), it becomes corrupted and non-working. It's going to be related to some sort of permissions issue and some file that is able to be corrupted/changed with the root/superuser access. I had similar results with fresh restore and JUST root, so the ROM's have nothing to do with it as far as I am concerned at this point.
In case you might ask. I Refreshed phone to total stock, rooted, and then, all at one shot, installed Gingervolt 1.3, OC, and Hotspot before rooting phone. HotSpot worked fine until the next reboot, where it did work for a few minutes then Kaboom! Nodda.
If someone can access (pull) the /system/var/lib/misc/udhcpd.leases file from a fresh stock phone, or even first-time booted, rooted phone, I would appreciate that as this file may be something in question, but my file was already changed by the time I found it.
-Cybie
I love to help but mine isn't working either. Can you get me started on returning the phone back to stock? I did install a backup util, and ran it first thing after rooting. But I am guessing that wasn't soon enough.
I will take a look at the file I have, I will try the two viewers I have, not sure if they will work.
I did run a restore, and the hotspot did work afterwards. My signal is very weak -110 dBm right now so if you can tell me how to copy/view the file I can get it for you (I did check my tools and could find the file but could not view it, I tried to email it to myself but the encoder couldn't handle it).
By the way, are you aware of a bug in the hotspot, tethering. When you turn off the hot spot and start tethering the hotspot comes back on and tethering will not start. It take a phone power turn to fix it.
sgschwend said:
I love to help but mine isn't working either. Can you get me started on returning the phone back to stock? I did install a backup util, and ran it first thing after rooting. But I am guessing that wasn't soon enough.
I will take a look at the file I have, I will try the two viewers I have, not sure if they will work.
I did run a restore, and the hotspot did work afterwards. My signal is very weak -110 dBm right now so if you can tell me how to copy/view the file I can get it for you (I did check my tools and could find the file but could not view it, I tried to email it to myself but the encoder couldn't handle it).
Click to expand...
Click to collapse
EDIT: When you copy these files, Don't view them until you zip up a copy first. They could potentially get corrupted. not likely, but with the way it's going with this 'project', who knows.
adb pull /data/misc/dhcp datadhcp (This will copy files from phone to a created directory called datadhcp)
Also, and more importantly, this is what I am really wanting:
adb pull /system/var/lib/misc varmisc (copies to created varmisc folder)
AND
adb pull system/etc/dhcpcd dhcpcd (copied to dhcpcd folder)
The created folders and files will be in the same 'dos' directory you have adb in. You can use the folder in which the all in one root is from MT if you are wondering where to get that by any chance.
Those would be a big help in getting thing figured out. At least, if those are the culprits.
NOTE: In order to have non-corrupted files, these have to be pulled from a fresh restore via LGNPST / Tot method. A restore via nandroid backup will not work. those files, once corrupted, seem to remain so, even after a restore for some odd reason, unless you were lucky enough to not have them corrupted prior to backing up, which would likely mean you rooted, rebooted into recovery and backed up before rebooting into your phone.
By the way, are you aware of a bug in the hotspot, tethering. When you turn off the hot spot and start tethering the hotspot comes back on and tethering will not start. It take a phone power turn to fix it.
Click to expand...
Click to collapse
Please clarify on this. Are you referring to starting the 4gHotSpot, shutting it down, and then starting a (root) Tether App??? If so, I haven't really had that issue because once I have to use the root apps to tether with, that usually means my HotSpot won't work at that point. I will say, however, I have had an issue where the HotSpot didn't want to shut down. I just go into Services/App Management and force a shutdown instead of a reboot. A bit quicker....
-Cybie
I will take a run at copying this stuff later today.
On the hotspot bug. Even before rooting, or upgrading to GB there was this bug, and it is still there after GB.
Once the hotspot has been started and then the user shuts it down it appears to shut down. Then the tethering (the application that came with the phone) is initiated it looks like it is tethering but the hotspot icon comes on after the phone has finished tethering and indeed it is running that way too.
I tried this five time last night: Restored the hotspot both application and data (titanium app), installation part of the application would fail but T said it was complete. Launched the application and two of the five times the PC had the correct IP address, the other three times it had the corrupted ones. Also when the PC did come up correctly the second device's IP address was corrupted. So I may need to fiddle a bit to fine the uncorrupted files after restore.
Perhaps someone else could help with copies the files too?

OpenVPN on KitKat

So I haven't yet rooted my phone. That's next up on the list. I'm just wondering if (after rooting) if there will be a way to manually add a route when connecting via OpenVPN. The device connects perfectly to the server and the server pushes a route to my device. It's just that when I type 'ip route' in a terminal app on the Note, the pushed routes don't actually get added to the device's routing table. I've read many threads that don't really offer any solution.
I'm just hoping that I can create a Tasker or similar automated task that establishes the connection, manually adds the routes, and then packets start a flowing.
Any thoughts on OpenVPN on KitKat? Surely I'm not the only one stuck in this rut!
Any replies or thoughts are appreciated!
Sent from my Note 4 using the XDA app. Damn this thing's sweet!
EDIT: So I rooted the phone using ChainFire's method. It worked flawlessly. I connected to my VPN (which locally is 192.168.1.1/24). After connecting, I verified that the route didn't exist using a terminal command.
su
ip route
I saw nothing mentioning the 192 network. So, I added 'ip route add 192.168.1.0/24 dev tun0' and BAM I'm in business. (I ran netcfg to determine which interface my VPN was on -- I assumed tun0 but I did check!)
Hopefully this helps somebody as I've been tearing my hair out for a couple days over this thing. I did reboot and although the routes weren't there (they're evidently not persistent) the VPN still functioned as designed. I ran a DNS leak test and all of my requests were successfully being routed over the VPN -- and that was all I wanted! Cheers....

Completely remove/disable android auto?

Does anyone have a method for completely disabling or removing Android Auto? Every time I plug my phone in to charge in my wife's truck, it pops up and I have to say "no." I don't have the app installed and the required software will never land on my phone (stripped down Lineage OS install). Is there a system app I can remove or setting I can change that will make it stop popping up?
junk408 said:
Does anyone have a method for completely disabling or removing Android Auto? Every time I plug my phone in to charge in my wife's truck, it pops up and I have to say "no." I don't have the app installed and the required software will never land on my phone (stripped down Lineage OS install). Is there a system app I can remove or setting I can change that will make it stop popping up?
Click to expand...
Click to collapse
There should a setting in the radio to disable Android Auto. In my Ford it is under Android Auto settings.
My wife uses it, so doing that would increase the number of steps that I have to take. (Would have to toggle off while I'm driving and remember to toggle back on when done so she doesn't get annoyed.) I'm trying to figure out how to disable it entirely or block the intent that signals it to start.
junk408 said:
My wife uses it, so doing that would increase the number of steps that I have to take. (Would have to toggle off while I'm driving and remember to toggle back on when done so she doesn't get annoyed.) I'm trying to figure out how to disable it entirely or block the intent that signals it to start.
Click to expand...
Click to collapse
OK,
Sorry can't help on that
junk408 said:
Does anyone have a method for completely disabling or removing Android Auto? Every time I plug my phone in to charge in my wife's truck, it pops up and I have to say "no." I don't have the app installed and the required software will never land on my phone (stripped down Lineage OS install). Is there a system app I can remove or setting I can change that will make it stop popping up?
Click to expand...
Click to collapse
It shouldn't be starting should it? When I plug my sons phone in which doesn't have the AA app installed it doesn't start AA on head unit. When I plug my phone in it says something like AA device detected & AA on the head unit starts. So something must be wrong with trucks AA, I think, or maybe different car manufactures do things differently?
Are you sure you can't install app on your phone? If you could install the AA on your phone there is a rejected car list option, you can add your wife's truck there and it won't start… I guess (as I've never used that option)
Alternatively you could just use one of those cigarette lighter USB chargers… I have one of those as passengers are always running low on battery LOL.
Installing the app requires installing and enabling at least one other piece of software that is well known for being bad for privacy: Google. Putting that on my phone is a non starter for anything. It's worth trying to see if I can change that setting without having to install all the dependent software though.
Just wondering if you were able to solve this? I have the exact same issue. Crazy thing is that I had gotten rid fof the annoying Android Auto prompts but then the super helpful techs at Samsung screwed up my phone trying and failing to do something else. Now the prompts are back and I can't remember how I got rid of them in the first place.
what about a cable like this ? https://www.amazon.com/PortaPow-Micro-USB-Cable-Charging/dp/B0088HTYUE
Please help. I highly recommend nobody update Android phones! Android auto does not stop popping up and is extremely annoying. It doesn't work. And causes all kinds of delays and disrupt other applications that work fine. Anybody know how to get rid of the current Android auto that was updated today?
hate Android Auto said:
Please help. I highly recommend nobody update Android phones! Android auto does not stop popping up and is extremely annoying. It doesn't work. And causes all kinds of delays and disrupt other applications that work fine. Anybody know how to get rid of the current Android auto that was updated today?
Click to expand...
Click to collapse
So you are saying Android Auto was installed on your phone by default & you can't uninstall it? If you can't uninstall AA you could "freeze it" with an app, Google "freeze bloatware" there are a number of ways of doing this (even without root) depending on android version
But first is Bluetooth auto start turned off? Have you added car to reject list in settings?
If that doesn't work you can activate developer options & set USB Configuration to "charge only", though that might stop USB working how you want when connecting to something else. Or use the charge only cable as mentioned above.

automatically unlock phone when connected to car

The goal: if my phone is connected to my car (and the car is turned on), unlock it automatically.
I keep a spare phone in my car connected to Android Auto (and hidden) so I don't have to keep plugging in my more expensive phone daily. Since it is also connected to my carrier and google accounts, I lock the phone. I have SmartUnlock set to keep the phone unlocked when bluetooth is connected to my car. This works for keeping the phone unlocked once unlocked, but it does not unlock the phone. I still have to do that manually with my fingerprint or passkey. Any idea how to automatically unlock the phone when connected to the car (and the car is on)? If my car is broken into and the phone is stolen I want the phone to remain locked. I am going to take the risk that if the keys are present (thus the car is on and the phone is connected to bluetooth & via cable), it's ok to unlock the phone automatically. If someone steals my car with the phone, then I'm screwed. But I'll take that risk.
Basically here is the problem with the built-in auto-unlock (from official instructions):
Important: When you don't use your device for 4 hours, and after it restarts, you'll need to unlock it.
Which means almost every time I use my car!
I've also tried google assistant voice unlock, but that only works if I don't have another lock method in place, which is not safe.
In case it matters, the spare phone is a Moto X4 with Oreo, not rooted. I'm on Google Project Fi, which allows multiple data-only SIMs on the same account. I have my voice SIM in the Android Auto phone and a data-only SIM in my main phone that is not directly supported by Project Fi.
Maybe something like this ?
AutomateIt Pro - Automate tasks on your Android ( cant post links)
j0k3r5 said:
Maybe something like this ?
AutomateIt Pro - Automate tasks on your Android ( cant post links)
Click to expand...
Click to collapse
Sadly, unlocking the phone is not one of the supported actions of this app.
Did you consider a different approach? Like using AAGateway ( https://forum.xda-developers.com/ge...droid-3-0-proxy-gateway-android-auto-t3813163 ) for wireless AA connection?
It's the solution I use. I have an S4 mini running CM13 permanently connected to the car, only running AAGateway. No Google account and no other apps.
Using Automate scripts on both master and slave so AA connection starts automatically when I enter the car.
Android can do this already. Trusted Devices. Bt unlocks your phone when the trusted Bt device connects.
Sent from my SM-G930T using Tapatalk
m00n61 said:
Did you consider a different approach? Like using AAGateway ( https://forum.xda-developers.com/ge...droid-3-0-proxy-gateway-android-auto-t3813163 ) for wireless AA connection?
It's the solution I use. I have an S4 mini running CM13 permanently connected to the car, only running AAGateway. No Google account and no other apps.
Using Automate scripts on both master and slave so AA connection starts automatically when I enter the car.
Click to expand...
Click to collapse
That's intriguing, but it doesn't solve everything I need in the spare phone.
1. The spare phone acts as a spare - if I forget or lose my phone, I can grab the spare phone from the car. Happens about once per month.
2. My main phone is not Project Fi compatible, and thus only works on LTE, no voice. I can use Hangouts Dialer to manually dial numbers for VoLTE, but that doesn't work through Android Auto. My cheap spare phone is Project Fi compatible and can dial voice via Android Auto.
3. My main phone is rooted and thus there is a thing or two it can't do - if I need to do those things, I can grab the spare phone (though admittedly playing PokemonGo is the only thing falling into that category thus far).
So the spare phone stays - I just need it to auto-unlock when I turn on the car.
Did you solve this? I have exactly the same problem. I need to have my phone unlock automatically when linked to my car bt. Not just stay unlocked, but actually unlock when connected.
pwvandeursen said:
Did you solve this? I have exactly the same problem. I need to have my phone unlock automatically when linked to my car bt. Not just stay unlocked, but actually unlock when connected.
Click to expand...
Click to collapse
See the attached Tasker screenshots for how I do it. The swipe is just a swipe up to get to the password prompt screen and %PASSWORD is set as my unlock password. The steps you see there are triggered by BT Connected to my Mazda. You will need Tasker and the AutoInput plugin
Mibuix0r said:
See the attached Tasker screenshots for how I do it. The swipe is just a swipe up to get to the password prompt screen and %PASSWORD is set as my unlock password. The steps you see there are triggered by BT Connected to my Mazda. You will need Tasker and the AutoInput plugin
Click to expand...
Click to collapse
I configured it nearly the same now and my keyboard is gone after the task was running.
Did you find a way to set it back after the tasks stopped?
WebBuddha said:
I configured it nearly the same now and my keyboard is gone after the task was running.
Did you find a way to set it back after the tasks stopped?
Click to expand...
Click to collapse
No sure what you mean? My keyboard never disappeared? Make sure you have a default input mode selected in your Android settings maybe, Tasker plugins can sometimes clear that.
Mibuix0r said:
No sure what you mean? My keyboard never disappeared? Make sure you have a default input mode selected in your Android settings maybe, Tasker plugins can sometimes clear that.
Click to expand...
Click to collapse
Thanks for your fast reply.
That has happend, it has cleared the seetings for my default input method.
Maybe it was an one time issue. I'll try it again later.
Mibuix0r said:
See the attached Tasker screenshots for how I do it. The swipe is just a swipe up to get to the password prompt screen and %PASSWORD is set as my unlock password. The steps you see there are triggered by BT Connected to my Mazda. You will need Tasker and the AutoInput plugin
Click to expand...
Click to collapse
Thanks much! I will give this a try - once I use the car again often enough to keep the phone in it charged.
Mibuix0r said:
No sure what you mean? My keyboard never disappeared? Make sure you have a default input mode selected in your Android settings maybe, Tasker plugins can sometimes clear that.
Click to expand...
Click to collapse
The problem stays. If the profile runs, tasker will be set as default input method.
Is it possible to create an new task if the bluetooth connection get lost?
I've tried it with "Input" + "Choose Input Method" but I have no glue what has to be entered there.

How to get Tasker to *actually* connect/disconnect VPN?

I have a problem with my recently purchased Tasker app. I tried posting on the official Tasker forum (https://tasker.helprace.com/s1-general/problems/top) but after I would click submit, nothing would come up. If anyone knows how to get in contact with the developers other than leaving a negative review on the Play Store that would be much appreciated.
I have a Samsung Galaxy S9 (not rooted) running whatever the latest version OS (Pie I want to say?).
I have a simple Profile setup to Connect to VPN when Wifi is connected, and Disconnect from VPN when Wifi is disconnected (as an Exit task) using the OpenVPN Tasker Plugin.
On rare occasion, everything works as expected.
Unfortunately, the majority of the time, it will indeed recognize the correct state (Wifi Connected), however, it will not connect to the VPN. When I go into Tasker, I see the Profile is green text, and if I go to More>Run Log I can see that it says something to the extent of:
"Active 2 Wifi Connected" then "Start TaskService" then "Running 3 VPN Connect" then "OK 3.1 VPN Connect.com.ffrog8.openVpnTaskerPlugin\n***\n*!" then "ExitOK 3 VPN Connect" then "Stop TaskService" (this is all in reverse order, since I think the run log puts the newest events at the top, but this is how I read them from bottom up).
Tasker even says 1 Task running on the notification bar on my lock screen. However the VPN is not connected. If I go into Tasker, turn off that profile, then turn it on again (via the toggle switch on the right hand side), the VPN will connect as expected and the run log will say the same exact thing.
Likewise for the Exit Task - when I disconnect from the network Tasker seems to recognize the state just fine (evident in Run Log and notification icon in lock screen), however my VPN remains connected (well my guess is it must disconnect for a short period as I transition from Wifi to 4g).
I have tried waiting a while to see if it's just a time issue, but I could wait hours and it will never trigger one way or the other (VPN Connect or VPN Disconnect). I have tried different Wifi networks. The Wifi State Active = "Any". In Android Settings>Apps>Tasker>Battery the toggle for "Allow background activity" is set to on, Optimize Battery Usage is set to off. Likewise for OpenVpn Tasker Plugin.
*Joao or anyone have any ideas?
Many thanks.
Troubleshooting = Because a Piece of Code went
Sorry to say that it looks like I am the 1st reply, as I have no real training in coding or programming myself.
I too recently began to play with such though with the intent to install it on some family member's devices ? However, like you I have not been able to get my desired automation regular enough to share it. When I 1st downloaded Tasker (I think) it had something about a "community" to share & get help with as well as more.
Trying to be helpful I ran a quick search for the specific site & as usual, Google had to go overboard with the results. Still hoping this will help you sooner as they all focus on that particular program:
https://community.home-assistant.io/t/tutorial-using-the-new-auth-system-with-tasker/82423
Just wondering if all the changes to Android OS as a whole may also have an affect on something minor such as whatever we choose to do with "automation" programming? Have seen throughout various post's & news that sort of thing....
for any other poor soul with the same problem, I read a couple of obscure comments on the interweb that the OpenVPN plugin for Tasker is no longer functioning, and all must be run through the Open VPN Connect app (NOT Open VPN for Android app) using intents. I found a guide once, and am testing it now and will report back if it works more reliably. Thank you Lone wolf for your reply.
just to update the poor souls, using intents like I said seems to work more reliably in terms of connecting to VPN. The only problem is if you go out of wifi range, it disconnects, but then are back within wifi range quickly (like somewhere with bad wifi signal), it will not connect again for some reason.

Categories

Resources