Related
I was on a trip yesterday and I noticed that when I turned on flight mode, it also turned off Bluetooth. I have a bluetooth GPS receiver that I use with my Alpline but wasn't able to in the plane because when I turned off my phone it also killed my Bluetooth.
:?: Is there a simple way to turn of JUST the phone radio, but leave the bluetooth up? My XDA II allowed me to turn off the phone's radio and leave bluetooth up. It just looks like bluetooth, WiFi and Phone have all just been lumped into Flight mode. Is there a system tweak or even a utility? I would be ok with either. Just found this annnoying. Thanks in advance for answering my question.
genghis said:
I was on a trip yesterday and I noticed that when I turned on flight mode, it also turned off Bluetooth. I have a bluetooth GPS receiver that I use with my Alpline but wasn't able to in the plane because when I turned off my phone it also killed my Bluetooth.
:?: Is there a simple way to turn of JUST the phone radio, but leave the bluetooth up? My XDA II allowed me to turn off the phone's radio and leave bluetooth up. It just looks like bluetooth, WiFi and Phone have all just been lumped into Flight mode. Is there a system tweak or even a utility? I would be ok with either. Just found this annnoying. Thanks in advance for answering my question.
Click to expand...
Click to collapse
There's no way that I know to have flight mode on and still be able to use bluetooth, wifi or gprs on the XDAIIi.
I also know that you can on the XDAIIs.
Actually there is.
Check this thread : http://forum.xda-developers.com/viewtopic.php?t=36788&highlight=flight+mode
The interesting part is :
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\FlightMode]
"IsFMCheckEnable"=dword:00000000
"WarningMsg"="Please turn Flight Mode off first"
Change "IsFMCheckEnable"=dword:00000001 to "IsFMCheckEnable"=dword:00000000
It allows you to use WiFi and Bluetooth while in flight mode. I found about this only minutes ago, and I'm sure glad I did
Cheerio !
I'm pretty sure that on flights it is illegal to use any form of wireless transmission hence BT & WiFi turning off at the same time as GSM. This is because they are all in the microwave band and can allegedly interfere with aircraft instruments.
If all else fails, turn flight mode on, turn BT on, the phone part will ask for a PIN which you must enabled this, select cancel and the phone part will turn off again leaving the BT active.
Thank you Mr_Smoke!
That App Radio Off works GREAT! I knew there had to be a simple fix.
:arrow: Bluetooth interference with instruments debunked:
http://www.bluetooth.com/NR/rdonlyr...7E/0/Aircraft_Safety_Report_for_Bluetooth.pdf
:!: Good article where they tested a 727 and 747 with bluetooth devices. They state that both UHF and VHF had a VERY remote chance of interference, but that the threshold would drop off before the device could emit enough power to actually interfere. Communications devices on aircraft have all been shielded and tested to higher energy levels than a simple BT signal from a PDA could push out. The only cavet is that use is prohibited during critical phase of flight (take off and landing) which is when the airlines currently make you turn off your devices.
I love using a BT GPS receiver (I put it up to the window and close the window shade to hold it in place) with Pocket Earth.
http://www.bluepointstudios.com/www/?fuseaction=product.poe
Its a VERY sweet program to show you where you are, direction you are headed, speed, and estimated time to your arrival. The only thing I wish that program had was altitude information which I emailed them as a suggestion for their next revision to their software.
pug said:
If all else fails, turn flight mode on, turn BT on, the phone part will ask for a PIN which you must enabled this, select cancel and the phone part will turn off again leaving the BT active.
Click to expand...
Click to collapse
You sure about this Pug? The message says that only emergency calls can be made until the pin is entered, that would suggest that the phone is still functional.
Or is this different to the message/routine at start up?
On a far more important note, I hear your looking at jumping ship to an Universal - what are we going to do without you? :wink:
Tom
No need to worry, the missus is having the Alpine for Tomtom etc. A bit of a waste know but it' too big for her for everyday use. I'll still be looking about here in the Alpine section, don't want to let my fans down now.
Hello folks,
in the new Android 2.0 there's a limit on Bluetooth: you can't enable DISCOVERABLE mode without passing through an Android dialogbox and only for a limited period of time (max 300 seconds): SHAME!!! This means that for DUN connections (or similar) the user should press YES every 300 secs (on Droid probably there's a bug, only 120 secs are allowed).
The problem could be found on the GIT at line 758: the application requires the WRITE_SECURE_SETTINGS permission to run the setScanMode method, unfortunately not available at user level.
Solution> The easiest solution is changing WRITE_SECURE_SETTINGS to BLUETOOTH_ADMIN_PERM, as it should be.
Hope this could be fixed for homebrew roms.
Cheers
PS - I do my apologies for the double post.
That doesn't even make sense. Android 1.5/1.6 only allows discoverable for a short amount of time as well, but once two devices are paired, neither device needs to be discoverable anymore -- they already know about each other.
outZider said:
That doesn't even make sense. Android 1.5/1.6 only allows discoverable for a short amount of time as well, but once two devices are paired, neither device needs to be discoverable anymore -- they already know about each other.
Click to expand...
Click to collapse
That's true, but you don't need to press YES into a ****ty dialogbox. If your application already have a proprietary dialogbox, then with Android 2.0 you have to press a button TWICE!!!
Finally, what if a user want to make a service ALWAYS available, without enabling discovery mode every 2 minutes???
Cheers
outZider said:
That doesn't even make sense. Android 1.5/1.6 only allows discoverable for a short amount of time as well, but once two devices are paired, neither device needs to be discoverable anymore -- they already know about each other.
Click to expand...
Click to collapse
I agree with outZider.
You don't need to keep the device discoverable once you have paired it to your pc (for example) to establish a dialup connection.
You only need to ENABLE bluetooth on both devices.
I dont know, if i understand something wrong, but i used pdanet with bluetooth yesterday. the connection was stable over more than an hour. i have a german milestone.
if its right, what was said here, that wouldnt be possible?
Like others said, I really don't see the issue. I'm pretty sure the limit on 1.6 is 120 seconds, anyway -- more than enough time to pair your devices.
Besides, I know very little about Bluetooth technology, but I'm sure that CONSTANTLY transmitting a Bluetooth signal in a "discoverable" way would kill the battery. I might be wrong, but I'm sure there's a reason behind the limit.
jay652 said:
Like others said, I really don't see the issue. I'm pretty sure the limit on 1.6 is 120 seconds, anyway -- more than enough time to pair your devices.
Besides, I know very little about Bluetooth technology, but I'm sure that CONSTANTLY transmitting a Bluetooth signal in a "discoverable" way would kill the battery. I might be wrong, but I'm sure there's a reason behind the limit.
Click to expand...
Click to collapse
its really a security issue. bluetooth isnt the most secure transmission method out.
bluetooth discoverable mode
Hi,
I am doing an app that requires the android phone to be on discoverable mode for a long time. However, the public APIs I have looked at only allow me to have up to 300 seconds and my app cannot set the bluetooth to be on discoverable mode. I do not want the user to have to click "YES" each time the dialog comes up to make the phone discoverable. I saw that you suggest us to changed the WRITE_SECURE SETTINGS to BLUETOOTH_ADMIN_PERM but this would mean I have to obtain the private APIs and altering its codes, right? Has this problem ever been solved? Is there anyway around this problem?
Thank you.
AndroidTeam5
Hello all!
I must say, this watch is a very nice toy to play with and very handy in meetings! I have used the watch for a few days now, but I (only) have 2 issues to be solved which I cannot seem to find the answer yet:
1. The watch is connected to my phone OK (all notifications come through all the time). However, when I say "OK google" and then for instance "show me my steps" or "show me the weather", it will go to a screen saying me the connection is offline (white logo on blue background on the top of the screen). When I dismiss that message, I see that my connection is still OK! Weird .... this happens to me practically 80-90% of the times .... on a very rare occasion it succeeds to show me the info I want. By the way, my internet connection is OK at that time.
2. I have my phone also connected with BT to my Volvo V40 (2013). However, with the watch also on BT, the carkit of my Volvo is now almost useless as the voice is completely messed up (from the caller to me, and from me to the caller), sounds very intermittend or something. It seems like the BT connection is not happy with having 2 devices to be connected at the same time. My phone is an iNew V3 ... could it be something with BT profiles or versions?
I have already tried to reset the watch, re-install wear on my phone, deleted the dalvik cache (phone), un-installed apps, but no luck. Anybody have a clue on the above?
Maybe your Wifi/3G connexion is in sleeping mode and is too long to unsleep ? the watch can not connect so quickly ?
You sound like having BT reception issues on the phone. This behaviour might be triggered by the bluetooth interface itself (on the phone - bad design) or by bad drivers (also on the phone) or by interferences from the wifi module. Is your wifi on all the time?
Regular wifi is on 2.4GHz, the same frequency as BT. Wifi, however, uses more Rx/Tx power compared to BT so, under certain bad antenna designs, WiFi can just mess-up BT.
On my phone (Z1C) is the other way around: having BT ON will cause bad performance on 2.4GHz WiFi .... so I just stopped using the 2.4 band for WiFi.
Give it a try, Worst case scenario: use another phone.
Hi guys,
Thanks for the reply. About the first idea ... well if I have my phone on the charger and already switched on, it still happens. So there I assume the 3G / wifi connection is already on and this issue will not be due to the delay of switching the data connection on. Am I right?
Second option: my wifi is switched on all the time, you are right. I will try to experiment a little bit with it, let's see if that will make a difference. And, changing the phone ... hmmm well that would be a very high impact of course. My iNew V3 actually works very well ...
I am still a bit struggling with accepting it is my phone causing this issue ... only with the voice regocognition I have this issue ... with all other commands and apps the connection is OK! Only with the "OK google" option it says "offline" ... and immediately (I do not see the colored circle). To me it looks more like a but in the software or something, but after 3 resets of the device I also cannot believe that ...
Any more options? Thanks!
Troxelke said:
Hi guys,
Thanks for the reply. About the first idea ... well if I have my phone on the charger and already switched on, it still happens. So there I assume the 3G / wifi connection is already on and this issue will not be due to the delay of switching the data connection on. Am I right?
Second option: my wifi is switched on all the time, you are right. I will try to experiment a little bit with it, let's see if that will make a difference. And, changing the phone ... hmmm well that would be a very high impact of course. My iNew V3 actually works very well ...
I am still a bit struggling with accepting it is my phone causing this issue ... only with the voice regocognition I have this issue ... with all other commands and apps the connection is OK! Only with the "OK google" option it says "offline" ... and immediately (I do not see the colored circle). To me it looks more like a but in the software or something, but after 3 resets of the device I also cannot believe that ...
Any more options? Thanks!
Click to expand...
Click to collapse
Update: i tried several things with the WIFI / BT settings and on/off, but no luck. I have forwarded the above issues to Google, maybe they can help me out. I will keep you informed ... in the meantime anybody else some useful tips? Thanks!!!
Troxelke said:
Hello all!
I must say, this watch is a very nice toy to play with and very handy in meetings! I have used the watch for a few days now, but I (only) have 2 issues to be solved which I cannot seem to find the answer yet:
1. The watch is connected to my phone OK (all notifications come through all the time). However, when I say "OK google" and then for instance "show me my steps" or "show me the weather", it will go to a screen saying me the connection is offline (white logo on blue background on the top of the screen). When I dismiss that message, I see that my connection is still OK! Weird .... this happens to me practically 80-90% of the times .... on a very rare occasion it succeeds to show me the info I want. By the way, my internet connection is OK at that time.
2. I have my phone also connected with BT to my Volvo V40 (2013). However, with the watch also on BT, the carkit of my Volvo is now almost useless as the voice is completely messed up (from the caller to me, and from me to the caller), sounds very intermittend or something. It seems like the BT connection is not happy with having 2 devices to be connected at the same time. My phone is an iNew V3 ... could it be something with BT profiles or versions?
I have already tried to reset the watch, re-install wear on my phone, deleted the dalvik cache (phone), un-installed apps, but no luck. Anybody have a clue on the above?
Click to expand...
Click to collapse
which phone are you using? are you on custom rom or kernel?
doki81 said:
which phone are you using? are you on custom rom or kernel?
Click to expand...
Click to collapse
I am using a iNew V3 on KitKat with the 1.13 official version (however from needrom). Would that be the issue?
Troxelke said:
I am using a iNew V3 on KitKat with the 1.13 official version (however from needrom). Would that be the issue?
Click to expand...
Click to collapse
try to pair your watch with your friend phone and to check this is not a problem coming from your phone. sometimes certain kernel do have issue with some of the bluetooth device.
Hello everyone. Sorry for my English, because I am using a translator. I decided to write this post, because it happened to me the same trouble and I found her cause. In anticipation of its Nexus 6, I decided to temporarily buy fairly cheap option LG G60 (X135). When watch came to me, I noticed the same problem. I then tried to connect them to the Moto G (1st generation), and there is the same. but by chance, in the evening, in my hands was LG G90 and I connected watch to this phone. Everything works without any problem. it turns out that despite the declared characteristics (Bluetooth 4.0) in all devices, it works quite differently everywhere. I hope with Nexus no problems.
Hi all, after opening this thread I tried several things and have some new insights:
- new update (5.0.1) solved my issue with going "offline" after a voice command. Now it works perfectly! But only if I am not connected to my carkit.
- if my watch is connected and try to use the carkit the sound is still bad. So I would like to have my watch disconnected if my carkit connects:
-- this could be done by only allowing 1 device to pair with my phone and prioritize carkit to be first and watch to be second.
-- this could be done by actively unpairing the watch if I receive a call (and connect when call is over).
The first option would be the most reliable and most simple. I tried to find an app that restricts only having 1 pairing and having a prioritize option ... but I cannot find such app. People any options?
Thanks!
Hi guys, in response of the above, the app TRIGGER might do the job, but it seems closing the Android Wear app or disconnect via Bluetooth does NOT disconnect your watch! Has anybody succeeded in using TRIGGER to disconnect / connect the watch with a automatic job?
Hello All,
Looking for a solution to the title. Need to make my phone turn on WiFi HotSpot when it connects to the Bluetooth in my car. I tried this with Tasker and a guide I found online, but it fails and says error executing action: WiFi Tether.
Any suggestions?
Thanks!
OP, I've tried to replicate the problem and it seems that the app doesn't have the proper permissions. Although all app permissions are enabled in the app settings, I think it's missing an additional permission. See screenshot below. You might want to contact support for the app to get the issue resolved.
As for a work around, it may be possible to do what you want with NFC stickers.
failure_2_win said:
OP, I've tried to replicate the problem and it seems that the app doesn't have the proper permissions. Although all app permissions are enabled in the app settings, I think it's missing an additional permission. See screenshot below. You might want to contact support for the app to get the issue resolved.
As for a work around, it may be possible to do what you want with NFC stickers.
Click to expand...
Click to collapse
Yep, same thing I was getting. None of the automation apps for this particular scenario that exist on the Play Store work either. SecureSettings plugin for Tasker also will not enable WiFi Hotspot. Seems to be by design. I'm just going to go the NFC route since there is a particular spot I put my phone in the car every time. Thanks for the reply!
VirusZer0 said:
Yep, same thing I was getting. None of the automation apps for this particular scenario that exist on the Play Store work either. SecureSettings plugin for Tasker also will not enable WiFi Hotspot. Seems to be by design. I'm just going to go the NFC route since there is a particular spot I put my phone in the car every time. Thanks for the reply!
Click to expand...
Click to collapse
NFC will not turn on WiFi Tether it's an issue with the app not requesting the permission or Something with the Samsung Software. I had an LG G6 and it was working fine. The way I resolved my issue I use autoinput. Now it's working fine. see the attached:
llaugerm said:
NFC will not turn on WiFi Tether it's an issue with the app not requesting the permission or Something with the Samsung Software. I had an LG G6 and it was working fine. The way I resolved my issue I use autoinput. Now it's working fine. see the attached:
Click to expand...
Click to collapse
Oh boy, looks tough. I'll mess with it and see what I can do. Would I still be able to get it to run this task when it detects that I connected to the BT in my car?
Thanks!
VirusZer0 said:
Oh boy, looks tough. I'll mess with it and see what I can do. Would I still be able to get it to run this task when it detects that I connected to the BT in my car?
Thanks!
Click to expand...
Click to collapse
Yes. That would be the trigger. I have that on mine because I have an android headunit that like to have connected to the internet since I run waze, pandora and some other apps that require internet.
llaugerm said:
Yes. That would be the trigger. I have that on mine because I have an android headunit that like to have connected to the internet since I run waze, pandora and some other apps that require internet.
Click to expand...
Click to collapse
Sounds like the same implementation I have. Thanks for the help! So I would set the profile in tasker, and then the task would be what I put in AutoInput, right?
Thanks again!
VirusZer0 said:
Sounds like the same implementation I have. Thanks for the help! So I would set the profile in tasker, and then the task would be what I put in AutoInput, right?
Thanks again!
Click to expand...
Click to collapse
I did it backward this time. I created the task first and then I create the profile. I use the state connect to BT to trigger the profile. Also it's very important that you enable smart lock, so your car BT can disable the lock screen and autoinput can do the job. You would need to buy the full version of autoinput since the lite version won't work.
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.