Hi
I wish to have the following setup:
1) When Headphone is not connected :
a) WidgetLocker is Enabled.
b) Pin is enabled.
2) When headphone is connected:
a) Widgetlocker is disabled
b) Pin is disabled.
The reason I want this setup is because, when I connect headphone I mostly use PowerAmp and I prefer it's Lockscreen. If WL is not disabled, then I have to pass through 2 lockscreens (PowerAmp's and WL's).
Now here is the issue,it's working perfectly....only for a certain period of time. That is when I connect headphones, the Pin and WL are disabled. But after a minute or so, WidgetLocker's lockscreen comes back. However the Pin Never comes back, so the setting is fine.
Here is the condition I have made:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please let me know, what I'm doing wrong. Why does the WL Lockscreen comes back after few minutes.
Bump:thumbup:
Sent from my Samsung Galaxy S3
Similar issue...
I'm actually using a VZW SGS3 (I535); though, I don't think this problem is specific to the S3. I have a Tasker widget that toggles widgetlocker on/off. I also have a Tasker profile that turns off widgetlocker when I'm using any one of my media apps. The profile turns widgetlocker back on when the media app is no longer in the foreground, unless I already set my widget to have widgetlocker off, in which case it stays off.
Both of these items work fine, but over a period of time, Widgetlocker seems to take it upon itself to turn back on. When that happens, the variable I use in my widget to specify the widgetlocker state that I have requested, it says "off"; however widgetlocker has definitely turned itself back on. I have to toggler my widget to "on", then back "off" again to re-disable Widgetlocker.
At first, I used the disable/enable states to control Widgetlocker. Then, I figured that disabling it was allowing it to be killed by Android and it was then restarting and resetting itself. So, to fix that, I decided to use suspend/resume states to control Widgetlocker. I did this because I read that suspending Widgetlocker keeps it active, but it doesn't lock the screen. This didn't help. The issue persisted.
At this point, I have still not found a solution. I had the same problem on an older phone mode (I think it was my Droid 3 and maybe even my OG Droid). In those cases, the stock lockscreen would re-enable itself as well. With the SGS3, I was able to completely turn of the stock lockscreen by selecting "None" in the phones lockscreen chooser menu. I was hoping that being able to do that would somehow help with this other issue, but it does not.
By the way, before going to Widgetlocker on the SGS3, I tried doing all of this with the stock lockscreen. The behavior was exacly the same. Disabling the lockscreen will work for a while, but eventually, it will re-enable itself.
I wish someone could figure out this issue.
-SR-
Hey fellas, I was too having this issue but I have now solved it!
Download the secure settings plugin for tasker and use pacdkage manager to disable widgetlocker in a task!
re-enable widgetlocker
damonsmith666 said:
Hey fellas, I was too having this issue but I have now solved it!
Download the secure settings plugin for tasker and use pacdkage manager to disable widgetlocker in a task!
Click to expand...
Click to collapse
Probably an obvious thing - but how do you "re-enable" widgetlocker (with secure settings) ... e.g., when you "leave home/safe zone"?
Thanks!
hellmag said:
Probably an obvious thing - but how do you "re-enable" widgetlocker (with secure settings) ... e.g., when you "leave home/safe zone"?
Thanks!
Click to expand...
Click to collapse
I cant remember now to be honest but I am sure it is just the reverse of disabling it!
Related
I wrote a little App that locks the Device using WMs built-in password lock.
I didn't like the behaviour of this lock so I decided to set this to 24 hours and lock manually.
You need Windows Mobile 6 since the aygshell.dll is only available there.
Features:
Lock (and I mean really lock, not starting the lock settings like some other apps do)
Suspend after Lock depending on certain circumstances
Registry (can be set in Settings app)
Commandline Parameters ("suspend" / "nosuspend")
AppToDate support
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just to have a screenshot.
This is just the settings app. The actual locker does not have any UI. It just locks.
This is a brilliant, brilliant app but you might miss what it actually does so I'll explain again.
It uses the built-in password lock but it means that you can normally turn it on without requiring a password. Then when you want to (say if you think someone might try using it) then you can run this app and it will show the password screen when you turn it on. You leave it to require password after 24 hours but you can get by most of the time not using it at all.
I have been looking for exactly this functionality for a very long time. Thank-you.
Thanks for the clear explanation.
thanks mate simple app but very handy
slow23 said:
I wrote a little App that locks the Device using WMs built-in password lock.
I didn't like the behaviour of this lock so I decided to set this to 24 hours and lock manually.
You need Windows Mobile 6 since the aygshell.dll is only available there.
Features:
Lock (and I mean really lock, not starting the lock settings like some other apps do)
Suspend after Lock depending on certain circumstances
Registry (can be set in Settings app)
Commandline Parameters ("suspend" / "nosuspend")
AppToDate support
Just to have a screenshot.
This is just the settings app. The actual locker does not have any UI. It just locks.
Click to expand...
Click to collapse
Thank you very much. Good working in my Polaris (HTC Touch Cruise)
slow23 said:
I wrote a little App that locks the Device using WMs built-in password lock.
I didn't like the behaviour of this lock so I decided to set this to 24 hours and lock manually.
You need Windows Mobile 6 since the aygshell.dll is only available there.
Features:
<snipped>..
Click to expand...
Click to collapse
A very useful program!
Would it be possible to provide also the integration in the Today screen, so that one can activate the lock quickly and easily?
Thank you!
xmdan said:
A very useful program!
Would it be possible to provide also the integration in the Today screen, so that one can activate the lock quickly and easily?
Click to expand...
Click to collapse
Thank you!
I would recommend you use any launcher you want and integrate a Button to launch it, because a separate Today Plugin would be too much in my opinion!
Thing is like a runway light at an airport. Tasker doesn't seem to be able to do it in stock form. No idea if secure settings could do it. Anyone have any ideas?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I don't know, but +1 I was thinking the same thing.
This would have to be manual every night but it would work. Settings>led>check boxes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sammy Galaxy S3 using Tapatalk 2
Yeah that isn't gonna fly. I have tasker automating a night mode. I guess its a feature the tasked devs will need to add in. Right now I just a it it face down on my nightstand. Not a huge deal to leave it facedown.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Maybe you could at least make it one touch off and one touch on by using a NFC tag and NFC Task Launcher and Tasker...maybe
I figured out how to do it using tasker, but you need root. I also need to do some more testing, but this should work in most cases.
Some background: when a notification comes in, the system sets the file led_pattern in /sys/devices/virtual/sec/led to something non-zero. 3 is a slow blinking blue light, 1 is solid red, I forget what the others are now. When the screen is turned on, this is reset to zero, and when the screen is turned off, if the notification bar hasn't been opened (and the program with the notification hasn't been opened) the value is reset to something non-zero. So, I created a simple task to change the value back to zero:
Create a new task, then select Script>Shell. Enter the following command:
echo 0 > /sys/devices/virtual/sec/led/led_pattern
Check the 'Use Root' box
Then your task is done. I'd try it once to make sure you have accepted whatever superuser popups (you'll need to always allow this for it to work on its own).
Now create a profile, and for the context select Event>UI>Notification. You may need to check tasker on the accessibility menu if you haven't already (it will prompt you if necessary). Add whatever other contexts you want (I have a variable that's set when I turn on my nighttime menu that I check for so the light will blink during the day but not at night). If you don't add other contexts this will always block your light, so make sure you've done some check to block it only at night.
Disclaimer: I haven't extensively tested this. There are a few quirks I've found so far:
1) If you receive a google voice text, the light instantly turns purplish normally. On my phone it will come on for a split second before tasker can kill it.
2) If you receive a notification which is blocked with this profile/task, and then turn on the screen but don't do anything to clear the notification the light will turn on when the screen is turned off again. This is also true if the notification comes in when you have the screen on and you turn it off before clearing it. You might be able to fix this by adding some variables to the profile/checking for screen on/off, but I mostly just want it to automatically turn off the light when I'm asleep so I'm happy with this so far.
3) I haven't tested this overnight, I guess it's possible that the phone will run a check and turn the notification back on at some point. I'll test it tonight and see if anything weird come up.
4) I've only tested this blocking gmail and google voice. It's possible that some other notification would toggle one of the other led variables and this won't help.
If you have any issues with this please let me know and I'll see what I can figure out. If this has helped you please click thanks; I'm new here and could use some street cred.
EDIT: You can solve problem 2 by creating a new Profile with context State>Display>Display State set to Off, and adding in the other secondary (ie night time) contexts. Call the same task you called for the first profile.
EDIT: Oops, forgot to mention, this is on a Verizon Galaxy S3, I assume it's the same for the other carriers, but I have no way of testing it.
Hi, got HAM2. Very impressed. Wish it had Qi, but aside really good.
Q: How do I turn off power button instant lock?
Android always has this option, but for some reason I can't find it in settings!
In my MT2-L05 EMUI3.0 it's in Settings/Security/Power button instantly locks.
Settings > Security
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ScoobSTi said:
Settings > Security
Click to expand...
Click to collapse
No matter the option I choose it still locks immediately after hitting the power button. This option is only if the phone goes to sleep itself after 30 seconds or whatever you have your sleep set to.. I'm looking for a work around for the power button. xposed forms here we go!.. any help from anyone would be helpful
superbass311 said:
No matter the option I choose it still locks immediately after hitting the power button. This option is only if the phone goes to sleep itself after 30 seconds or whatever you have your sleep set to.. I'm looking for a work around for the power button. xposed forms here we go!.. any help from anyone would be helpful
Click to expand...
Click to collapse
Wow, I just tried it myself and I get the same problem. Good job, Huawei...
Ya... and I'm having a hard time finding a module. any help would be appreciated
My HAM2 doesn't have this problem. I have the Delayed Lock app from the play store which modifies the locking though. I've also frozen the hwunlock lock screen since it was interfering.
Sent from my MT2L03 using Tapatalk
@arcadesdude your the man that app works great... glad to see you also still sporting the HAM2. problem solved
superbass311 said:
@arcadesdude your the man that app works great... glad to see you also still sporting the HAM2. problem solved
Click to expand...
Click to collapse
Happy to hear. Also if you want to clean up the notification, the Delayed Lock app can still run if you hide it's notification (long press on it then uncheck show notifications), it still works fine and the Notification bar is clean. Mine is set to auto lock after about 20 mins from when I turn off my screen and I also created a shortcut on my home screen to instantly lock it and turn off the screen (have to set wake to lock mode in the settings of the app). If you want to a shortcut like that you can do this in Nova Launcher (or something similar in other launchers). Long press and empty space on the homescreen. Choose shortcuts then delayed lock shortcuts then Lock now (which also turns off the screen).
HAM(2) on Bro!
First of all, video:
https://www.youtube.com/watch?v=9axQHQ8ZXLU
Solution is not from android programmer, rather geek
Hi there... so, i was pretty dissapointed with lack of S-View functionality on CM13, S4 Mini. It was great feature, that was doing really good job with magnetic cover.
If you tried to do something with it, you probably experienced some problems with magnetic sensor (or you were smarter than me). It prevented to turn on screen with power button on any custom lockscreen from market, that was better than cm's stock one. In terms of 'better' i have in mind a lockscreen... that has f*** clock in right spot for case's window I was trying to bring it back with various results, but finally i achieved (i think) the best possible solution, turning lockscreen into S-View screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What it does right: showing time and basic info about battery, calls, msgs, next alarm, notifications (from gmail, fb messeger - that part is actually very customizable).
What it doesn't do at all: doesn't let you pick up calls, turn off your alarm via window and do any stuff that requiers touching via window. Magnetic sensor basicaly turns off that feature when case is closed. Showing info about playing track is not worth activating (because of space).
So, we need xposed installed and then download module: http://repo.xposed.info/module/com.ssrdroide.lockscreenwidgets
And the widget we are gonna use is dashclock: https://play.google.com/store/apps/details?id=net.nurik.roman.dashclock (or you can use more advanced alternative: https://play.google.com/store/apps/details?id=com.kk.widget)
Step 1. First thing you wanna do is to configure widget the way you want - download some extensions for it (like battery info). I highly recommend to use DashNotifer to get notifications from custom apps like fb messenger (https://play.google.com/store/apps/details?id=com.umang.dashnotifier It's already there in KK Widgets). Test it on your homescreen for now and find configuration that suits you.
Step 2. will be add widget to lockscreen via xposed module. This configuration (http://i.imgur.com/iiJMK7w.png) will keep your widget in case's window, when owner info will be out of it on same time. There is also something to mention - if you will not turn off notifications on lockscreen they will move your widget little higher (depending on number of notifications).
So... 1. If you wanna keep your notifications on lockscreen, set container 'y' translation to something around -150. Widget will stay in window regardless number of notifications.
2. If you wanna remove notifications for that cause, set container 'y' translation to -175. Widget will be in perfect spot for the whole time.
That works for standard DPI.
And that's it. It works perfectly with magnetic sensor.
For better effect you can change your wallpaper to black (worth it). That's however will change when you will listen to music, you can turn this option off or use this xposed module to paint it black for good: http://repo.xposed.info/module/com.generalbrus.brightlockscreen
Another thing is alarm. It happens that Timely has clock in perfect spot when activated and can be controlled with physical buttons
I'm super happy with result. It's not exactly what you could achieve with real S-View, but it does good job
If you have better solutions share it in thread!
Hi folks,
I'm wondering if anyone has a solution to this: Immediately following applying the June update, I noticed certain apps (crucially, Angry Birds2) were being closed in the background as soon as I switch to other apps. Previously, I could have AB2 open, go do other things on the phone, come back half an hour, and AB2 would still be open. Now, even brief switches to other apps results in it being closed.
Figuring it had been switched to a higher level of battery optimization, I checked the AB2 app and made sure it was still Unrestricted (it is).
Battery Saver is off.
Adaptive Battery is on, but it was before the update too.
What other settings do I need to monkey with to fix this?
Thanks in advance!
Developer options>standby apps, check bucket state of app. It should be active.
If that's the case disable all global power management. If disabled all buckets show as active and their state can't be altered.
Google global power management never worked right. Turn all that junk off.
Deal with power hogs on a case by case basis instead. In settings individual apps can be set to not run in background without invoking global power management.
blackhawk said:
Developer options>standby apps, check bucket state of app. It should be active.
If that's the case disable all global power management. If disabled all buckets show as active and their state can't be altered.
Google global power management never worked right. Turn all that junk off.
Deal with power hogs on a case by case basis instead. In settings individual apps can be set to not run in background without invoking global power management.
Click to expand...
Click to collapse
For AB2 it shows "exempted" and is grayed out. What does that mean? Meanwhile I'm turning off Adaptive power. Anything else I need to turn off, while I'm at it?
Frankenscript said:
For AB2 it shows "exempted" and is grayed out. What does that mean? Meanwhile I'm turning off Adaptive power. Anything else I need to turn off, while I'm at it?
Click to expand...
Click to collapse
Exempted? More like KIA Erratic behavior is typically what it causes on my Samsung's.
In power management the only thing I enable would be fast charging if you want that.
Not familiar with Pixel settings but they are similar as it's a Google Android based subsystem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sadly all similar settings are now turned off and the phone has been rebooted. AB2 still closes nearly instantly when I switch to another app. Sigh.
Frankenscript said:
Sadly all similar settings are now turned off and the phone has been rebooted. AB2 still closes nearly instantly when I switch to another app. Sigh.
Click to expand...
Click to collapse
Try clearing app cache.
More drastically delete data or reinstall it.
It may be the app itself is no longer compatible now and needs an update.
On a Samsung my first choice would be to clear the system cache found on the boot menu. I've been told Pixel's don't have this option.
Personally I avoid all OTA updates as they can and do break things. Pie and above are fairly secure if you don't do stupid things.