Related
I have exchange policies through company email, which are quite strict. I am happy with that. Only problem I have now, is that I have to put in the PIN to unlock every time my screen wakes up. Formerly in WM6.5 (HD2) I could unlock only with swipe in the first 30minutes, and after 30minutes of inactivity, I had to provide the pin.
Can I do this now as well ? Is there a difference on the S II between unlock screen and PIN unlock ? In the settings I cannot find this option; are there solutions for that (other lockscreen apps e.g.) who do accept that ?
Hi,
I would suggest you download the manual for the phone.
in the mean time:-
Go to settings/location and security/change screen lock
there you can disable screen lock, set a pattern for unlock, set a pin or password.
Then go to settings/display/screen time out and change the time it takes to lock
Hope this helps
Txs, I see now that also exchange policy has greyed out the pattern option. So I cannot disable the pin unlock and cannot put in pattern ... Unfortunately so ...
oh coroparate phones eh?
MattRob said:
Txs, I see now that also exchange policy has greyed out the pattern option. So I cannot disable the pin unlock and cannot put in pattern ... Unfortunately so ...
Click to expand...
Click to collapse
I use touchdown for exchange app, and the pin is needed only for the app not the phone.
Sent from my GT-I9100 using XDA Premium App
MattRob said:
I have exchange policies through company email, which are quite strict. I am happy with that. Only problem I have now, is that I have to put in the PIN to unlock every time my screen wakes up. Formerly in WM6.5 (HD2) I could unlock only with swipe in the first 30minutes, and after 30minutes of inactivity, I had to provide the pin.
Can I do this now as well ? Is there a difference on the S II between unlock screen and PIN unlock ? In the settings I cannot find this option; are there solutions for that (other lockscreen apps e.g.) who do accept that ?
Click to expand...
Click to collapse
This is what I am using on my Captivate to overcome the same issue, http://forum.xda-developers.com/showthread.php?t=848564, I know we are not on the same phone but I am pretty sure the "fix" can be done on the email.apk for your phone.
Basically you need to tell the native email app to tell Exchange that it is using a PIN when in actuality it is not. If it is too complicated for you to do yourself, Fenny is pretty cool about doing it for you, just send him a copy of the email.apk you are using.
Looks like there is already an email.apk for you found here http://forum.xda-developers.com/showpost.php?p=13413332&postcount=1533
If i am using the original ROM on Galaxy S2 for United Kingdom, would this email.apk still work or do i need an updated file ? What are the chances of administrator finding it out ?
The touch of HTC One is so wrongly caliberated that touching anywhere on the screen answers the call (results in unwilling answer of calls when taking the phone out of pocket) or the emergency number 911 gets dialled from lock screen when the phone is in pocket...
Just now I got a call from the Sheriff's department about a 911 call made from my phone
Been using since it came out and has never happened to me. I'm going with user error on this one.
Sent from my HTC One using xda premium
CraigP17 said:
Been using since it came out and has never happened to me. I'm going with user error on this one.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
This. I even have home to wake enabled and it's never done this.
Sent from my HTC One using xda premium
CraigP17 said:
Been using since it came out and has never happened to me. I'm going with user error on this one.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Never has happened to me. This is obviously user error. What a waste of a thread.
Sent from my HTC One using xda premium
i can actually attest that this can happen cause it happened to me as well with my HTC One. I got a random call from the police department that my phone dialed the emergency number, all while my phone was in my back pants pocket
Definitely not a stupid thread. My friend has had a one for a few weeks now, and he keeps on complaining about how often he calls 911 from his pocket...
Maybe try disabling apps that causes the screen to turn on like some notifications. If it still occurs, try showing it to an AT&T rep. They should replace it.
Sent from the "ONE" phone for me
Please enter a valid message
I did it 5 times in one day. I used to have no lock screen with just a password but now I have both and almost all notifications that turn the screen on are disabled. So far so good.
martyagt4 said:
If you have nothing to add, then why bother to reply. Seems a waste of time for you, since you have such important things to attend to. Since you think personal attacks are ok, how about you go back down into moms basement and clean up you room, mmkay?
This has never been an issue with any other phone I've owned, but it's happened twice to me now. I couldn't care less, and I don't consider it user error.
Click to expand...
Click to collapse
Even if that was actually a personal attack that doesn't make it okay for you to do it
Sent from my HTC One using Tapatalk 4 Beta
I feel your pain, OP. Although I haven't had this issue with my One yet, I've dialed 911 from my pocket twice so far with my Galaxy S4. I turned off the "increase screen sensitivity" option, so hopefully it doesn't happen again. Either way, I think I'm just somehow bumping the "emergency dialer" thing from inside my pocket with the pattern lock set-up. Maybe you're inadvertently doing the same.
Ironically enough, a few minutes after being reprimanded by them for my latest 911 pocket call, 911 accidentally returned the favor and dialed my number by mistake
Yes this happened a few times to me using the stock ROM 4.1, however this issue can be resolved several ways (this list is NOT all inclusive):
tbalden's kernal has the following:
Pocket Wake Protection (prevents phone from waking accidentally in your pocket, when it contacts skin through textile)
A new lock screen (Halo Locker, Holo Locker)
A new ROM, Google edition is harder to get to actually dialing 911.
Also noticed on the stock kernal and ROM the hotter the phone got in my pocket the easier it was to dial 911.....and this article was pretty funny.
martyagt4 said:
If you have nothing to add, then why bother to reply. Seems a waste of time for you, since you have such important things to attend to. Since you think personal attacks are ok, how about you go back down into moms basement and clean up you room, mmkay?
This has never been an issue with any other phone I've owned, but it's happened twice to me now. I couldn't care less, and I don't consider it user error.
Click to expand...
Click to collapse
This isn't a support group, making a thread like this won't solve anything for you chief
Sent from my HTC One using xda premium
Solved by doing the following :
Disable screen lock by selecting none from settings > security > screen lock
Select no lock screen from settings > personalize > lock screen style
Install Magiclocker main from app store abd enable pattern or pin in it for security lock screen
I don't even know how to call 911 from the lock screen without unlocking, so I doubt my pocket knows (unless it's smarter than me ). Can someone tell me how?
sa.guly10 said:
Solved by doing the following :
Disable screen lock by selecting none from settings > security > screen lock
Select no lock screen from settings > personalize > lock screen style
Install Magiclocker main from app store abd enable pattern or pin in it for security lock screen
Click to expand...
Click to collapse
3rd party lock screen apps tend to drain a lot battery.
Sent from the "ONE" phone for me
I use WidgetLocker so I haven't had a problem with accidentally calling 911. I do hate the incoming call screens, though, and have accidentally answered more than a few calls I did not want to take. The screen with the regular buttons on the bottom is fine but the one with the sliders is horrible. I can hit decline and it'll still answer. :-\ also, like you said, just taking it out of my pocket will answer the call. I tried ultimate call screen but it didn't always work well for me.
Sent from my HTC One using xda premium
https://play.google.com/store/apps/details?id=net.nanabit.callconfirm&hl=en - This will help with outgoing calls.
As for incoming calls, I also use Widgetlocker and it can display when a call comes in (you have to unlock to answer).
It happened to me...and Police Dept. called me...This is definitely not a good thing...How can we avoid ?
Simba501 said:
https://play.google.com/store/apps/details?id=net.nanabit.callconfirm&hl=en - This will help with outgoing calls.
As for incoming calls, I also use Widgetlocker and it can display when a call comes in (you have to unlock to answer).
Click to expand...
Click to collapse
I didn't even notice that you could do that with widgetlocker, thanks for the info!
Sent from my HTC One using xda premium
Coming from Samsung here, so this feature is very new for me.
Does the knock to wake feature work if you're set on pattern lock? Or does it only work when you have knock code set as your security?
Reason I ask is because I initially had the knock code set as security, then changed to pattern after I set Android Pay. BUT, knock to wake has been working for me the past two days (even with the pattern lock ON)...until 2 hours ago.
Now the only way I can knock wake the device (or even access the second screen) is either to set the security as Knock Code, or press the power button.
Is this behavior normal? I found it weird that the second screen is untouchable with the pattern lock ON.
Knock On will work everytime regardless of your lock screen setting (double tap on the center of the screen to wake device up into lock screen).
Knock Code, however, need to be set to unlock your device, the pattern is of your choice.
Android Pay doesn't accept a knock code as a security measure. I was using it, then was forced to switch to pin after setting up Pay.
Ryu Kenshin said:
Knock On will work everytime regardless of your lock screen setting (double tap on the center of the screen to wake device up into lock screen).
Knock Code, however, need to be set to unlock your device, the pattern is of your choice.
Click to expand...
Click to collapse
ok so correct me if I'm wrong: regardless of your security settings, KNOCK ON will work to wake the device up. Yes?
In that case, something has gone wrong with mine as I can only do knock on when Knock Code is set. Even worse, the second screen shortcuts are only accessible in that mode as well.
I think I just encountered a similar if not the same problem but I'm not sure if it's an app or if it coincides with something I accidentally tapped in the hidden menu last night.
I had been using pattern unlock since I got the phone on friday and double tap to wake the screen was working fine along side fingerprint unlock, now double tapping doesn't work and the second screen does not respond when locked.
EDIT: I just tried knock pattern and it allowed me to wake the screen but the moment I switched back to pattern it stopped responding to screen wake tapping.
mastarpete said:
I think I just encountered a similar if not the same problem but I'm not sure if it's an app or if it coincides with something I accidentally tapped in the hidden menu last night.
I had been using pattern unlock since I got the phone on friday and double tap to wake the screen was working fine along side fingerprint unlock, now double tapping doesn't work and the second screen does not respond when locked.
EDIT: I just tried knock pattern and it allowed me to wake the screen but the moment I switched back to pattern it stopped responding to screen wake tapping.
Click to expand...
Click to collapse
sorry to hear about that, seems like you have exactly what I had. Knock on just stopped working out of nowhere.
Good news is, I did a factory reset and it fixed the issue. Albeit, without access to Titanium Backup, it's quite a chore right now to redo all of my setups. Trying LG Backup now just in case.
Give factory reset a try and hopefully it'll solve your issue as well.
baymon said:
sorry to hear about that, seems like you have exactly what I had. Knock on just stopped working out of nowhere.
Good news is, I did a factory reset and it fixed the issue. Albeit, without access to Titanium Backup, it's quite a chore right now to redo all of my setups. Trying LG Backup now just in case.
Give factory reset a try and hopefully it'll solve your issue as well.
Click to expand...
Click to collapse
Yeah I was kind of afraid I'd have to reset already, barely a week in, lol!
Thanks for letting me know a reset worked, hopefully it doesn't happen again.
I think @knifedroid had the answer. AndroidPay doesn't allow you to use knock. I have the same issue as well...well i guess it's not an issue...it's a feature.
Sent from my LG-H901 using Tapatalk
KwestJones said:
I think @knifedroid had the answer. AndroidPay doesn't allow you to use knock. I have the same issue as well...well i guess it's not an issue...it's a feature.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Knock Code is a security method, Knock On is a feature that LG implemented at kernel level to wake up/turn off the device. The issue that we've been having is with the Knock On not functioning anymore.
Long story short the reset restored Knock On (wake).
Long version, I gave the LG Bridge software a shot to do a backup to the PC.
It let me backup just about everything including apps and data, including Humblebundle apps and stock homescreen layouts, so it's probably as close to tatanium as you ca get.
I Haven't gone through updates yet but so far Knock On is still working after a restore, I'll edit if that changes. *crossing fingers*
oh man I'm glad i came to peek this section for this, as i feel like i tapped something wrong in the hidden menu as well. i might wait a little bit to do a reset and see if someone finds out a way to keep the KnockON thing running when screen is off.
joachim123 said:
oh man I'm glad i came to peek this section for this, as i feel like i tapped something wrong in the hidden menu as well. i might wait a little bit to do a reset and see if someone finds out a way to keep the KnockON thing running when screen is off.
Click to expand...
Click to collapse
hey someone on another thread said that deleting all the fingerprints solved his Knock ON issues. Can you try this out?
baymon said:
hey someone on another thread said that deleting all the fingerprints solved his Knock ON issues. Can you try this out?
Click to expand...
Click to collapse
Just tried it, no luck. Both knock on and off are still not working.
The issue started for me last night after going to the hidden menu and enabling Fast Dormancy. Disabling it again doesn't help. I guess just avoid the hidden menu is the takeaway here.
Sent from my LG-H901 using XDA Free mobile app
pakraider said:
Just tried it, no luck. Both knock on and off are still not working.
The issue started for me last night after going to the hidden menu and enabling Fast Dormancy. Disabling it again doesn't help. I guess just avoid the hidden menu is the takeaway here.
Sent from my LG-H901 using XDA Free mobile app
Click to expand...
Click to collapse
ok, sorry bud. Hard reset did the trick for me, but it'll be good to know what caused this and what can we do to solve it.
Now that you mentioned it, I think my issue started after I was playing around with hidden menu as well. Although I didn't recall changing anything.
baymon said:
ok, sorry bud. Hard reset did the trick for me, but it'll be good to know what caused this and what can we do to solve it.
Now that you mentioned it, I think my issue started after I was playing around with hidden menu as well. Although I didn't recall changing anything.
Click to expand...
Click to collapse
Yeah, tbh it sounds like a software bug by LG. Just going to the hidden menu seems enough to break the knock on/off. Makes you wonder what else might be getting messed up too that we haven't noticed.
p.s. this thread is why XDA is awesome.. everyone thinking 'omg what happened?' only to see others in exactly the same boat.
This makes sense. I think my knock on stopped working after using the hidden menu to look at the dB on the LTE signal.
Sent from my SM-N900T using Tapatalk
So in this case of resetting, would I be able to just grab the system img and flash it without actually doing a hard reset? I don't want to have to set up everything, again.(i had forgotten it was going to reset when I unlocked the BL)
Just confirmed it. Knock on breaks when you try to enter the ims settings menu inside the hidden settings menu. It crashes, then knock on stops.
Sent from my SM-N900T using Tapatalk
I am having an issue where it is grayed out and stating something else has an administrator lock. Any idea on what's holding it up?
Sent from my LG-H901 using XDA Free mobile app
MacMitten said:
I am having an issue where it is grayed out and stating something else has an administrator lock. Any idea on what's holding it up?
Sent from my LG-H901 using XDA Free mobile app
Click to expand...
Click to collapse
That looks like you are in the android pay security options. If so, android doesn't think that knock is secure enough for androidpay. Don't think there is anything we can do about it yet.
If you decide to use android pay you cannot use KnockOn pattern unlock to open your phone.
Sent from my LG-H901 using Tapatalk
Just as the title reads. Updates the fingerprint with cool animation.
Thanks for the information about the new firmware update for the new Bold-N1!
After comparing this new Bold-N1 with the BLU-XI+ (with 6GB of RAM), which I also have, I have noticed that apparently due to the low 4GB of internal RAM... That most negative and annoying thing when using this new BOLD-N1 is its bad management of it's RAM Memory, which BOLD should urgently solve in an upcoming update, because there are other similar phones with also 4GB of RAM that handle this memory much better when running several applications at the same time.
So I expected BOLD to do something to improve, the handling of the RAM in the BOLD-N1 ...
Apart of Updating the fingerprint with cool animations, Do you know if there any other fixes or enhancements?
I just wanted to add that it lost root with this update, but was able to flash my old modified boot image with no negative effects. I thought it might cause a boot loop, but it works fine.
im not currently on the stock rom, so i cannot do it. Has anyone managed to copy the update file, before it being installed?
Ok I asked and got a response. Here is the update package.
https://android.googleapis.com/pack.../404ed8bd09ac64e1c9a1252713be24abff463f81.zip
Possible warning
Not confirmed yet. But it is possible this update is changing the preloader , making sp-flash tool no longer connect without signed images.
Someone who has already installed the update, can you confirm if flash tool still allows flashing?
Fingerprint scanner activating on picking up the phone
Anyone know if there's a way to disable the fingerprint scanner activating any time I pick up the phone now? Never did that before the update, it's pretty annoying. Already have lift to wake turned off, but that doesn't fix it. Went through every setting and didn't see a way to fix it.
paulson64 said:
Anyone know if there's a way to disable the fingerprint scanner activating any time I pick up the phone now? Never did that before the update, it's pretty annoying. Already have lift to wake turned off, but that doesn't fix it. Went through every setting and didn't see a way to fix it.
Click to expand...
Click to collapse
Pretty sure that would be under the "lift to wake option" found in settings->Intelligent Assistance->Lift to wake
See if the switch is set on and toggle it off. Mine isn't and my scanner doesn't activate when picking up
no99sqrd said:
Pretty sure that would be under the "lift to wake option" found in settings->Intelligent Assistance->Lift to wake
See if the switch is set on and toggle it off. Mine isn't and my scanner doesn't activate when picking up
Click to expand...
Click to collapse
Nope, that isn't it. That's off now, and was off before the update, and this only started happening after the update.
paulson64 said:
Nope, that isn't it. That's off now, and was off before the update, and this only started happening after the update.
Click to expand...
Click to collapse
weird - I'm not having that problem
Apart of the Security Update and adding some cool Animations to the On-Screen Fingerprint Scanner...
I have also noticed that after the updating we are now able to turn ON or OFF Adaptive Brightness directly from the slide down menu.
paulson64 said:
Anyone know if there's a way to disable the fingerprint scanner activating any time I pick up the phone now? Never did that before the update, it's pretty annoying. Already have lift to wake turned off, but that doesn't fix it. Went through every setting and didn't see a way to fix it.
Click to expand...
Click to collapse
Please, anyone? This seems to really be killing my battery life, I'm getting down to 10 percent now, when before the update I would be down to about 40-50 percent with the same amount and time of use after this update.
I just updated my bold n1 with the new security patch and I don't know if this was available before hand, but I noticed that the fingerprint reader now appears on the bottom of the screen just by lifting the phone up. I don't remember it doing that before.
paulson64 said:
Please, anyone? This seems to really be killing my battery life, I'm getting down to 10 percent now, when before the update I would be down to about 40-50 percent with the same amount and time of use after this update.
Click to expand...
Click to collapse
lol so I've seen ur post and never understood what u were saying and this is for all of us for ignoring u sorry lol so to fix ur problem u actually have to press lift to wake to get ur phone the way u want it I just turned mine off for the first time and it acts like u describe in ur post soooo basically just turn the lift to wake option on but I actually like the way u have it no battery drain for me
Anyone else experiencing this? Less than 10 seconds after I fingerprint unlock, sometimes the screen will go black while I'm reading a message or whatever. Other times it seems to be triggered by a touch action, like pressing on an icon or clearing a notification.
I found no setting that explains it. Screen timeout is set to 1 minute. I don't have any third party lockscreen or display related apps. It's been happening for as long as I can remember with this phone, and I thought the January update might fix it but it persisted through. Faulty proximity sensor maybe? I'm starting to contemplate warranty servicing.
Glaux said:
Anyone else experiencing this? Less than 10 seconds after I fingerprint unlock, sometimes the screen will go black while I'm reading a message or whatever. Other times it seems to be triggered by a touch action, like pressing on an icon or clearing a notification.
I found no setting that explains it. Screen timeout is set to 1 minute. I don't have any third party lockscreen or display related apps. It's been happening for as long as I can remember with this phone, and I thought the January update might fix it but it persisted through. Faulty proximity sensor maybe? I'm starting to contemplate warranty servicing.
Click to expand...
Click to collapse
I think it's A12. On the P5 you could look at the device and it would stay on when doing something. The feature, although there is a setting on/off, does not work any longer. I never had it on the P6 shipped with A12 but on the P5 my wife has the same problems since updating. So perhaps a proximity update will fix it but if all else is working the replacement will almost guaranteed be worse.
Glaux said:
Anyone else experiencing this? Less than 10 seconds after I fingerprint unlock, sometimes the screen will go black while I'm reading a message or whatever. Other times it seems to be triggered by a touch action, like pressing on an icon or clearing a notification.
I found no setting that explains it. Screen timeout is set to 1 minute. I don't have any third party lockscreen or display related apps. It's been happening for as long as I can remember with this phone, and I thought the January update might fix it but it persisted through. Faulty proximity sensor maybe? I'm starting to contemplate warranty servicing.
Click to expand...
Click to collapse
Are you using a custom kernel or have had a custom kernel installed in the past?
If so, you will need to try a factory reset and complete full stock image.
bobby janow said:
I think it's A12. On the P5 you could look at the device and it would stay on when doing something. The feature, although there is a setting on/off, does not work any longer. I never had it on the P6 shipped with A12 but on the P5 my wife has the same problems since updating. So perhaps a proximity update will fix it but if all else is working the replacement will almost guaranteed be worse.
Click to expand...
Click to collapse
I saw that setting but I don't see how it's relevant. Even without that setting, the display should not turn off on its own before 1 minute of inactivity.
vandyman said:
Are you using a custom kernel or have had a custom kernel installed in the past?
If so, you will need to try a factory reset and complete full stock image.
Click to expand...
Click to collapse
No. I didn't do any modding beyond bootloader unlock and root with Magisk. I flashed the January factory image a few days ago and rerooted, but as I said the problem started long before that.
Glaux said:
I saw that setting but I don't see how it's relevant. Even without that setting, the display should not turn off on its own before 1 minute of inactivity.
No. I didn't do any modding beyond bootloader unlock and root with Magisk. I flashed the January factory image a few days ago and rerooted, but as I said the problem started long before that.
Click to expand...
Click to collapse
I didn't realize you were rooted, I usually don't read signatures. Have you unrooted and tested? Other than that I'm not rooted so perhaps someone can help you out. Maybe change the title of the thread so rooted folks will jump in with suggestions. Good luck.
Looks like the issue might have come from the launcher I use, Smart Launcher. Specifically a setting called "Smart Screen Off" that's not working as intended. I turned that off and so far I can't reproduce the issue.