Develop Bugs

Autostart wireless upon boot?

How do i activate wireless automatically when it starts windows mobile 6? so i don't have to click around all the time.

Try enabling that option in Shap's Advanced Config

It seems, in my experience, that once I turn it on, it stays on. But it will have to reconnect after the screen goes off.
You might be able to use advanced config (I haven't tried) to enable wireless in standby.

you mean the program (attached image)?
Are you sure it's there? I must have missed it...
No whenever i turn the device off wlan is turned off upon booting it up.

Go to 'more settings'.

[Q] Can someone please help me with Tasker/lockscreen issues?

I have Googled this to death. Some sources say it can be done, some say not without root, some say not at all. I don't know what to think. I've tried so many things. I'm not a total noob, but I am certainly not as educated as you guys are about Android. I'm just learning. Please go easy on me. Also, I put this here because it seems, from my research, to be an issue with S2 and S3 phones, not Tasker itself. Please let me know, however, if you feel I should move it, Mods.
What I want to do is to disable the PIN lock on my phone when I'm at home on our wifi and in the car. No reason to unlock my phone every time I want to use it at home and I can't get voice commands to work consistently when it's locked in the van. With a teen driver watching my every move, I don't want to touch the phone.
Here are the details:
*I'm stock, unrooted
*I'd rather not root, because (unlike my Vibrant!) this phone works fine the way it is. That being said, I'd do it if it finally. Makes. This. Work!
*I've tried this with NFC tags and NFC Task Launcher
*I'm using Tasker
*I've tried it with and without Secure Settings
For the van, I always have it plugged in, so I think I can accomplish this by just setting the screen to not time out.
Home is the real issue. Sometimes I can get it to work, but it never *stays* working. I've tried turning my PIN Lock and all lockscreens off via my device settings and setting a task that triggers when I leave "HomeWifiName" to 1. Secure settings, configuration, set PIN 2. Secure Settings, configuration, keyguard enabled. It doesn't work at all. I've tried so many other variations of this I can't list them.
I wonder if I'm getting confused between the PIN and the keyguard. Is there a difference between the lockscreen and keyguard?
I'd really appreciate any advice you guys have for me.

If using the pin lockscreen, that is key guard in Tasker.
So key guard off = no lock screen at all. You don't need Secure Settings for this anymore. But you may need root.
Now, regarding your wifi near context, that doesn't work for me either. It's unreliable at best. Instead, use if connected to X wifi network as your context.
Let me know if you need any more help.

Aerowinder said:
If using the pin lockscreen, that is key guard in Tasker.
So key guard off = no lock screen at all. You don't need Secure Settings for this anymore. But you may need root.
Now, regarding your wifi near context, that doesn't work for me either. It's unreliable at best. Instead, use if connected to X wifi network as your context.
Let me know if you need any more help.
Click to expand...
Click to collapse
Thank you very much for this. I'd rather use connected not just near, so if I leave the house I'm protected.
If I do that, set it to keyguard off in Tasker while connected to our wifi, it works once or twice, but not consistently. I have the exit task to enable keyguard when I disconnect.
Am I missing something? Honestly the challenge of figuring this out has now become more important to me than actually getting it to work.

I had a profile that did this for a while, but I felt like it was a security risk. I just don't feel comfortable with that level of automation. But to each his/her own. When I typed the first post I was on my phone. On PC now so I can elaborate a bit.
New Profile > State > Net > Wifi Connected. I entered all 3 details; SSID, MAC, and IP. You can get it all right from the little scan applet that is already on your screen.
It's entry task will be Keyguard > Off
It's exit task will be Keyguard > On
So when you are connected to your home wifi, keyguard will be off. And when it disconnects, keyguard is turned back on. If this doesn't always work in this configuration, then it should be considered unreliable and not used. If this is the case, it's an issue with the app, not with your Tasker-fu. But with Tasker 4.0, you no longer need Secure Settings for a lot of things. Keyguard being one, GPS control being another big one.

Aerowinder said:
I had a profile that did this for a while, but I felt like it was a security risk. I just don't feel comfortable with that level of automation. But to each his/her own. When I typed the first post I was on my phone. On PC now so I can elaborate a bit.
New Profile > State > Net > Wifi Connected. I entered all 3 details; SSID, MAC, and IP. You can get it all right from the little scan applet that is already on your screen.
It's entry task will be Keyguard > Off
It's exit task will be Keyguard > On
So when you are connected to your home wifi, keyguard will be off. And when it disconnects, keyguard is turned back on. If this doesn't always work in this configuration, then it should be considered unreliable and not used. If this is the case, it's an issue with the app, not with your Tasker-fu. But with Tasker 4.0, you no longer need Secure Settings for a lot of things. Keyguard being one, GPS control being another big one.
Click to expand...
Click to collapse
I really appreciate the information, the concern, and your patience. I do think this is something I'm going to have to admit defeat on. I've tried everything I can think of and the lockscreen will not stay off. It's not really a big deal to hit a few numbers when I want to get into my phone or tablet. It also keeps small, curious people out. :laugh:
I've solved the issue for in the van. I just use an NFC tag on phone cradle in the van. Since my phone is always plugged in while I'm in the van, I just set the screen timeout for 30 minutes. Problem solved.
Good to know my Tasker-fu isn't in question. I have to admit that made me laugh.

[Q] Wifi staying on when screen turns off.

HI forumers
can you suggest any help?
When I have my device screen turned off, my wifi stays connected. So in the middle of the night, emails will sting "ping" out a sound.
I have selected in the settings to turn off Wifi when in sleep, and when i close my case cover, but it just doesnt.. Any ideas?
Thanks

Yeah that doesnt work for me either. I would try setting a wifi timer in wifi, adavanced settings and pick a time where you want wifi to be on during certain times of the day. Hope this helps!

Really?! not just me then? I was wondering if maybe a downloaded app is making this error happen.
Can anyone confirm that it does work for them?

Guys, Have you tried to untick "always autorized localisation search" in the advanced parameter of the wifi ?
Hope it could help.

Good idea, but I've just tried this and it didnt fix the problem..
Anyone else?
Or maybe someone knows an app that can do this?

Bluetooth off on a reboot?

I find it sort of ironic that every time I have to reboot/shut down the Honor 7x the Bluetooth doesn't turn on when I restart the phone. If I forget to manually do it, my watch doesn't sync, etc. etc. The irony is that the last few phones I had made it impossible to turn OFF Bluetooth, it always turned back on in a second or so.
Anyone else see this or know of a reason or fix?

I think I fixed this one, not an issue specific to Huawei or Honor apparrently...
While the setting seems to be in different places, it is called "Bluetooth Scanning" on the Honor 7x. The description says "Improve location by allowing system apps and services to detect Bluetooth devices at any time".
With that setting enabled, bluetooth would always be off on a reboot. Turning that setting off allows me to reboot without losing bluetooth.
On the Honor 7X I found it using the search box in the settings, using "scanning" as the search term. It is under "Security & Privacy", "Location Access", the three dot menu in the upper right "Scan settings".

Hmmmm....?
n9yty said:
I think I fixed this one, not an issue specific to Huawei or Honor apparrently...
While the setting seems to be in different places, it is called "Bluetooth Scanning" on the Honor 7x. The description says "Improve location by allowing system apps and services to detect Bluetooth devices at any time".
With that setting enabled, bluetooth would always be off on a reboot. Turning that setting off allows me to reboot without losing bluetooth.
On the Honor 7X I found it using the search box in the settings, using "scanning" as the search term. It is under "Security & Privacy", "Location Access", the three dot menu in the upper right "Scan settings".
Click to expand...
Click to collapse
First Of All.. Glad You Found A Solution That Worked For You...
But something else may be going on with your device.
Your post intrigued me... so I duplicated your situation.
Indeed, my setting under Security & Privacy / Location Access / 3 Dots / Scan Settings / Bluetooth Scanning was set to "Disable" by default since it's my first time there.
So... I did a Reboot and Power Off with the setting still Disabled... and my Bluetooth was still Enabled upon powering up.
But Also... After I "Enabled" Bluetooth Scanning, and did a Reboot and Power Off.. my Bluetooth was STILL enabled upon boot..
I just wanted to let you know, you may have other issues going on.. but hey, if you have it working to your satisfaction.. you're good.. :good:
P.S.
I don't know if you have rooted.. my device is completely stock..

Hello, i had a similar pb on my Honor 7 and a friend of me on P10 Lite. After "plane mode" or reboot the BT didn't power ON even if it was ON before.
I've tried this solution on my HONOR 7 and he tried on his P10 Lite... Now everything is working again. The BT will power ON if it was ON before the action.
So big TY !

NFC while screen is off, detect NFC tag loss

So I know some time ago, this functionality had been hacked using a combination of the NFC LockscreenOFF Xposed module and modification of the NFC apk. Base on what I can find in the forums, this last worked with Lollipop, but there seems to be little or no activity on this front since then.
I'm just wondering if anyone knows of a way to restore this functionality in Oreo, or if the discussion has ceased because there is a simpler, more obvious solution that I can't find.
Essentially, my goal is to have an NFC tag on my phone cradle in my car which facilitates Tasker profiles/tasks for using the phone in the car. My current setup *sorta* works. The tag sets a variable, and when the variable is set and the phone is plugged in, the profiles/tasks execute. When the phone is unplugged, the exit tasks execute, including clearing the variable set by the NFC tag.
The problem is that if I turn the screen off, the process repeats itself the next time I turn the screen on.
Ideally, the NFC tag would be detected even if the screen is off, the entry tasks would run, and the exit tasks would be triggered by the NFC tag being lost (phone removed from the cradle). Because the tag would still be detected when the screen is off, I wouldn't have to worry about the tasks executing again when I turn the screen on. I could skip the variable entirely and eliminate the "powered" condition for the profile.
Any insight on a solution for this would be much appreciated. If this is the wrong section, please point me in the right direction. I searched every applicable forum I could think of, so my apologies if I've overlooked something.
I'm running a Nexus 5X, stock Oreo 8.1, rooted with Magisk and running systemless Xposed. Tasker and Secure Settings are installed, if that matters.
Thanks in advance for any input.

Looking for this as well. Did you ever find a solution?