Database Users

[Q] Unlock screen using tasker?

Hi,
since I have finally gotten NFC on locked phone to work on 4.2.2 rooted stock ROM, I would like to add a task that unlocks my phone in combination with an NFC tag (which I placed in my car dock).
Unfortunately, I cannot get it to work, whatever tool I use.
- Security settings, especially "clear password" oder "keyguard/patternlock off" don't seem to have effects.
- Widgetlocker can be reached with an intent, but only brings me to the pin screen instead of the desktop.
- "Unlock Keyguard Ad" takes me to the desktop but still seems to keep some kind of keyguard in the background that pops open when I e.g. open tasker.
The problems with "clear password" might be connected to the fact that my device in encrypted ...
So, any idea how to automatically unlock an encrypted Nexus 4 with PIN on stock firmware?

Update: Don't know what went wrong the last time, but now "keyguard off" does have an effect: The same as "Unlock Keyguard Ad". I get to the desktop, I can start apps, but if if I select e.g. tasker from the system bar, I am prompted for the password. Cannot see a system here ...
Also, "clear password" now has an effect: It sets the PIN to empty, but I am still prompted ...

Same issue with password on encrypted device
I was thrilled to find this thread because I'm facing the same issue of having trouble disabling my lock screen with an encrypted device.
My excitement turned to disappointment when I realized it's been over six months with no response. Did you find a solution? Does anyone have any insight into the best way of preventing the need to enter a password on an encrypted device?

Can Lock-Screen be disabled by an App?

On my Note-2 (Android 4.1.2) I had two apps that worked properly to toggle (disable/re-enable) the Lock-Screen function. They are [SwitchPro Widget] and [Turn Off the Screen by Protoport]. This was handy: I would disable the security feature when I was safely at home, but enable it when I would go out to public places.
Sadly, neither of these work on the Note-3 (Android 4.3). I suspect the newer Android version prevents an App from disabling the Lock-Screen.
Does anyone know of an App that can toggle the Lock-Screen state on the Note-3 (Android 4.3)?

I have never been able to reliably do this with any app, even with Root access. In the end, I used Llama to set the password (or PIN) to empty when at home. That way I get a 'swipe' screen only. When out, I get a PIN. In my case, I even set it to something you just cannot set using Android, so it is even more secure (I believe).
Not ideal, but it works very reliably, and even without root.

Skeleton said:
On my Note-2 (Android I used.1.2) I had twocalled no lock apps that worked properly to toggle (disable/re-enable) the Lock-Screen function. They are [SwitchPro Widget] and [Turn Off the Screen by Protoport]. This was handy: I would disable the security feature when I was safely at home, but enable it when I would go out to public places.
Sadly, neither of these work on the Note-3 (Android 4.3). I suspect the newer Android version prevents an App from disabling the Lock-Screen.
Does anyone know of an App that can toggle the Lock-Screen state on the Note-3 (Android 4.3)?
Click to expand...
Click to collapse
Came across your thread and I remembered an app I used on my s3-.- called no lock in the play store so I tried it on my 900t and it works perfectly hour:good: this is what you where looking for..........

I use an app called automagic for it. It's also possible to disable the swipe to unlock screen which I do while connected to my car (Bluetooth)

Philly Jim said:
Came across your thread and I remembered an app I used on my s3-.- called no lock in the play store so I tried it on my 900t and it works perfectly hour:good: this is what you where looking for..........
Click to expand...
Click to collapse
Your mentioned app, "No Lock, by BoD" doesn't work on Android 4.3. That app hasn't been updated since Sep 2011.

Skeleton said:
Your mentioned app, "NoLock, by BoD" doesn't work on Android 4.3. That app hasn't been updated since Sep 2011.
Click to expand...
Click to collapse
Have you tried it, because ever since last night it has been working flawlessly for me and yes it's the same app that hasn't been updated since 2011........try it........

Philly Jim said:
Have you tried it, because ever since last night it has been working flawlessly for me and yes it's the same app that hasn't been updated since 2011........try it........
Click to expand...
Click to collapse
OK, I installed it again just now. Nope, it doesn't work "properly".
It does install. It does run and it does show the toggled states for the widget. I attempt to toggle it, then the widget shows the change. But, the Lock-Screen state remains in its pre-existing state.
In my case, I have Lock-Screen set for Pattern Lock. The setting also has the Lock-Screen (Pattern Lock) appear only if the screen is off for longer than, say 5 seconds. This Android feature works properly, despite the App. The Pattern Lock is not required when I power off-then-on in under the assigned time of 5 seconds. However, the Pattern Lock always appears after the assigned time, regardless of the use of this App.
What I want is the App to disable Pattern Lock while I am at home.
I notice that the App does not appear in the Android permissions, "Device Administrators". Then again, it doesn't show up on my Note-2 installation either, even though the App works on that device.
I would appreciate it if you can give me some insight on how I can get this App to work on my Note-3 ....
Thanks.

Further testing ...
The App (No Lock) does work in one condition: If the Lock-Screen state is set for Swipe-Lock, then the App works properly to enable/disable it.
However, when the Lock-Screen state is set for Pattern-Lock, then the App fails to truly enable/disable it. However, the App's widget does show an indicated change of state (it shows either pad lock open or closed) - but this is an illusion only.

Skeleton said:
Further testing ...
The App (No Lock) does work in one condition: If the Lock-Screen state is set for Swipe-Lock, then the App works properly to enable/disable it.
However, when the Lock-Screen state is set for Pattern-Lock, then the App fails to truly enable/disable it. However, the App's widget does show an indicated change of state (it shows either pad lock open or closed) - but this is an illusion only.
Click to expand...
Click to collapse
Yeah i just use it to totally Disable the Lock Screen , which it does for me with no issues , i never used any pin or pattern unlock , i did however see something mentioned about that when youu hit help after you hit the menu key , anyway sorry this didn't work for you , but i must thankyou for this thread because it tottaly works for me .....:good:

I use tasker for stuff like this. It works together with secure settings. My home zone is set up to work with cell tower id's. This works for me as my work place is far enough away. In Tasker (or llama or automagic or automateit pro) you can select secure settings as a plugin task. You then just select in secure settings what you want to toggle (swipe, pin or pattern). Some of them require root, though.

Questions regarding N preview

1. Can it be used as a daily driver ?
2. Does the N bootloader and radio work with and can boot existing marshmallow custom Roms and twrp 3
3 Will dirty flashing work ( earse data but leave data/media intact before flashing preview using fastboot)
4 What's wrong with twrp on N, I read some people saying that twrp asks a password or something. So pls tell me about it
Thanks

Here are all the known issues with Android N
Platform Issues
Performance and battery
System and app performance is known to be periodically slow / janky, and device may become occasionally unresponsive. These problems may become more acute with prolonged use.
Battery life may be regressed in this release for screen-on and screen-off use cases.
Dialer
Dialer app does not support Direct boot. This will be addressed later in N Developer Preview.
Voicemail playback does not work.
System UI
Some new or modified strings in the system UI are not translated to all languages.
Overview UI is still in development, and subject to change. For example, we intend to remove the timer that appears when the user switches between apps.
Settings controls and toggles may be slow or appear to be unresponsive.
Visual design of notifications is subject to change.
In the Gmail app, direct archiving of emails included in a notification bundle does not work properly.
Android for Work
Work Security Challenge
After migration to N, or after the user creates work profiles, work profiles can't create keys in the keystore until the user changes their pattern, PIN, or password, or sets up a Work Challenge.
In Direct boot mode, applying the passcode restrictions to the device causes the work profile to be unlocked, even though the device is locked. This makes the work profile accessible even though it should be protected by the device lock screen.
When the user enters a wrong password and pin, the system does not display any informational message; instead, it only clears the input field. This issue does not affect pattern or fingerprint input.
On a tablet, the background displayed with the work challenge is disproportionately small.
The version of Google Apps Device Policy that is bundled with N Developer Preview does not yet support the Work Profile Security Challenge feature. Developers should instead use TestDPC to test this feature.
Always On VPN
If Always On VPN mode is turned on, but VPN is not available, apps not specified as exceptions to the Always On policy connect over the ordinary network. Unless specified as exceptions to Always On VPN policy, apps should be offline if they have no VPN connection available.
When Always On mode is on, a VPN connection is not established after a device reboots into Direct boot mode, even after the user unlocks the secure lock screen.
Improved Contacts
Bluetooth PBAP/MAP devices do not display Caller ID for work contacts. The next release of Preview resolves this issue.
Work Mode
The Google Now Launcher does not display whether Work Mode is on or off. The Launcher also does not show app suspension state.
After the user turns Work Mode off and on, the system no longer shows Work profile app widgets, such as Calendar.
Suspend Packages
Device admins can suspend critical system packages, which may lead to unexpected behavior, such as placing calls despite the Telephone disabled dialog’s being displayed.
Other
The Settings app crashes on launch if DISALLOW_MOUNT_PHYSICAL_MEDIA is set to true when the user inserts physical media such as an SD card.
The DPM.setPackagesSuspended state does not persist when the user uninstalls and then reinstalls an app. Either the app should remain suspended after uninstall/reinstall, or suspended apps should not be uninstallable
The first check-in in a Work Profile takes several minutes to complete. This may cause the device to take longer than normal to be visible in the Play EMM API.
Notifications from Work Profile apps are not visible to notification listeners installed in the personal profile. As a result, the system does not display Notifications as expected.
The version of Google Apps Device Policy that is bundled with N Developer Preview does not yet support the Work Profile Security Challenge feature. Developers should instead use TestDPC to test this feature.
Keyboard
Bluetooth pairing between keyboards and Android devices may be unstable.
Video
Video playback may lag and show interruptions.
Wi-Fi
Wi-Fi has undergone some refactoring which may change API corner case behavior. Specifically, applications which attempt to connect to specific networks, or attempt to reconnect to networks should retest.
The legacy DHCP client has been removed from the platform. The only DHCP client that the platform supports is the DHCP client introduced in M.
Direct boot
NFC doesn't function until first unlock.
When a phone with Bluetooth enabled is restarted, Bluetooth does not turn on automatically. You must manually re-enable Bluetooth.
Under some circumstances, the default ringtone may not sound for phone calls and messages. This behavior is fixed in the next N Preview release, with one exception (and workaround):
On a device that is not freshly wiped--one that has been booted at least once since being set to direct boot mode--the default notification ringtone does not sound. The user can work around this issue by manually selecting a ringtone from Settings.
Direct boot is not enabled by default on devices running an N Developer Preview build. To enable direct boot for testing and development, go to Developer Options and tap Convert to File Encryption. In this dev preview, this requires a factory reset to repartition and reformat your device for File-based Encryption.
Picture-in-picture for Android TV
The PIP integration in the Recents UI is not finalized, and is subject to change.
The animation of the PIP window is not smooth. Future releases of the Preview will improve this.
Future releases of the Preview will improve upon the visual design and layout alignment of PIP.
Bug reports
Bug reports do not always complete successfully (as a workaround, sometimes they can still be accessed through the bug report document provider in internal storage).
Split-screen Multi-window
Apps may experience crashes and unexpected UI behavior when put into split-screen mode. These are app issues that must be fixed by the app developer.
When an app targets a version of the Android platform earlier than N, the App may not work with split-screen toast may appear multiple times.
Long-pressing the Overview button while using an app with a fixed orientation may produce unexpected app behavior.
Apps may flicker while resizing.
Animations are not yet final.
Input method
Google Keyboard unexpectedly falls back to the generic Google keyboard when Use system language, but Google Keyboard doesn’t support any of the languages selected in the system-language preferences. It should fall back to American English.
You can work around this problem by adding at least one language that Google Keyboard supports.
Accessibility
TalkBack exhibits issues with features including Notifications, Quick Settings Tiles and Multi-window display that may cause system crashing or lack of spoken feedback from TalkBack. Future releases of the preview will address these issues.

N has been pretty stable for me so far. Dark mode took a few taps to get it to turn on and a few slow downs in the camera app one time, but mostly pretty good. Way better than some custom ROMs (or even some stock ROMs on crappy phones) I've run back in the day.
Have a good one!

[GUIDE] Enable DT2S without entering in conflict with fingerprint unlock [NO ROOT]

How to enable DT2S without entering in conflict with fingerprint unlock​
Hi guys, i recently found a way to enable the DT2S (Double Tap To Sleep) feature on our Honor 8 without giving any administrator permission. As you probably know, when using any application for DT2W it requires the "Device Administrator" permission to immediately lock the screen, but apart the fact that this option could be potentially dangerous, giving administrator permission enables a security measure wich consists in PIN immission right after the screen has been locked (and you try to unlock it with fingerprint). But this method seems to work flawlessy, avoiding the nuisance to insert a PIN everytime the device gets unlocked. The process is quite easy and can be achieved without root, but there are some requirements that i'm going to list below:
You must use Nova Launcher Prime as home screen replacement
You must to be on Android Marshmallow 6.0 or Higher
​
1. Open the Nova Settings and select the "Gestures" option
1. Take a look at the arrow in the first attachment
2. Select the "Double Tap" option when shows up
2. Take a look at the arrow in the second attachment
3. Select the "Shortcut" tab on the right
3. Take a look at the arrow in the third attachment
4. Select the "Lock screen" option
4. Take a look at the arrow in the fourth attachment​
By following the steps above you'll be able to take advantage of the DT2S lock method without compromise the fingerprint unlock function. BTW i don't know if this is a functionality or a bug (i don't think it's a bug), the only thing i know is that it's working good with no problems, also after reboot and shutdown.​
PAY ATTENTION
I'm actually using the BETA 5.5 version of Nova, not tested with regular version​
Hope this post could help someone Enjoy!​

I use Nova Launcher to DT2S without Enable device admin or timeout. Just goto Guesture of Nova Settings, choice shortcut then select Screen Lock. All done
PS:
Ahhh, Your guide like me

blackbuffalo said:
I use Nova Launcher to DT2S without Enable device admin or timeout. Just goto Guesture of Nova Settings, choice shortcut then select Screen Lock. All done
PS:
Ahhh, Your guide like me
Click to expand...
Click to collapse
I didn't understand if the P.S line was sarcasm or not. However if you knew that, good, but not everyone knows that. If you just go in Gestures/Double tap/Nova/Lock screen it doesn't work because ask for admin permission, but if you go in Gestures/Double tap/Shortcuts/Lock screen that works. I just wrote this to help someone who didn't already figured this out

(Guide): How to enable custom launchers on Chinese ROM EMUI

Note: Please don't tell us how easy it is to change launchers in default apps, that has not been possible since EMUI 9 for chinese roms, see > https://forum.xda-developers.com/hu...i-9-removes-default-launcher-options-t3853441
WARNING:RECENT APPS MENU WILL STOP WORKING
All credits to Web1n on Github for figuring out this method.
Here is official guide in chinese
App download on Google Play
https://play.google.com/store/apps/details?id=web1n.stopapp&hl=zh
Steps:
(Note that this method needs to be repeated every restart)
- Install the custom launcher of your choice and ensure it is the only launcher installed other than Huawei home
- Install and setup adb on your computer
- Enable developer options on your phone
- Turn on adb debugging and adb in charge only mode
- Make sure your device is on usb charge only mode
- Install the app from link above
(note i am using a Samsung for screenshots as I don't want to mess up my main Huawei, but I got it working there through the same steps)
https://imgur.com/a/hYPkSiY
After installing app tap the right arrow until this page, tick the box to agree to TOS
https://imgur.com/a/2e3B2Vp
Tick second box
https://imgur.com/a/dKxEZwm
Tap right and you will be greeted with this home screen, tap the plus arrow
https://imgur.com/a/j1SzlFX
Tap second tab to look for system apps, find the app huawei home
https://imgur.com/a/3GgZfSA
Return to this screen, you will see the Huawei home icon, ensure it is greyed out, tap it if it is not so.
Done! Gesture navigation will no longer work but an app like fluid gestures work well enough, enable 3 button navigation in options and tap home to enjoy your new launcher. Your multotasking button has also just become useless...
Again, all credits goes to the developer

jalk44 said:
Note: Please don't tell us how easy it is to change launchers in default apps, that has not been possible since EMUI 9 for chinese roms, see > https://forum.xda-developers.com/hu...i-9-removes-default-launcher-options-t3853441
All credits to Web1n on Github for figuring out this method.
Here is official guide in chinese
App download on Google Play
https://play.google.com/store/apps/details?id=web1n.stopapp&hl=zh
Steps:
(Note that this method needs to be repeated every restart)
- Install the custom launcher of your choice and ensure it is the only launcher installed other than Huawei home
- Install and setup adb on your computer
- Enable developer options on your phone
- Turn on adb debugging and adb in charge only mode
- Make sure your device is on usb charge only mode
- Install the app from link above
(note i am using a Samsung for screenshots as I don't want to mess up my main Huawei, but I got it working there through the same steps)
https://imgur.com/a/hYPkSiY
After installing app tap the right arrow until this page, tick the box to agree to TOS
https://imgur.com/a/2e3B2Vp
Tick second box
https://imgur.com/a/dKxEZwm
Tap right and you will be greeted with this home screen, tap the plus arrow
https://imgur.com/a/j1SzlFX
Tap second tab to look for system apps, find the app huawei home
https://imgur.com/a/3GgZfSA
Return to this screen, you will see the Huawei home icon, ensure it is greyed out, tap it if it is not so.
Done! Gesture navigation will no longer work but an app like fluid gestures work well enough, enable 3 button navigation in options and tap home to enjoy your new launcher.
Again, all credits goes to the developer
Click to expand...
Click to collapse
Thank you :good:

Thank you. It works but recent app not work even if with 3 button navigation.

nhan1411 said:
Thank you. It works but recent app not work even if with 3 button navigation.
Click to expand...
Click to collapse
unfortunately yes, huawei even went to the step of removing old vertical overview menu so that the only overview menu in these buklds comes from the launcher

Recent apps stopped working for me when I updated to EMUI 10 then downgraded because of this and now it works on EMUI 9. Thanks for this, was going mad for 3 days because I couldn't disable the stock launcher even though my phone is rooted.

For those now missing Recents : Swiftly is a circular gesture activated app launcher with its own Recents :laugh:
I now have "Tap for Recents"
You can place Swiftly with a surface area (over where the middle icon would be on the dock) for activation on the bottom center. You can then tap or tap-hold for recents.
Make sure the middle position there on the dock is empty, so it doesn't have an app icon or folder. Make the rectangle big enough to activate Swiftly, but small enough not to overlap with selecting the input field of WhatsApp, Messenger, ...
In my Nova 5T I also lost swipe up for home (anyone else?) When I uninstalled the default launcher. So I use Fluid Natural Gestures for all of the bottom to swipe up for home.
The two overlay areas of these apps overlap but for me don't interfere with each other. You can also enable "immediate activation" in both for nice swift operation.
(I could choose between Nova and Default Launcher in Emui 10, I'm in Europe. But removed default because regularly it would switch back to Default Launcher)

Update: has stopped working
Feel free to still try as it seems to be different builds for everybody

.

Guys...i've done....but not with this method....

TheFastGT said:
Guys...i've done....but not with this method....
Click to expand...
Click to collapse
How have you done it then?