Related
Hi!
I have been trying a couple of locksreens, but somehow I realized, I don't need them at all, when I turn on my phone, I want full functionality, not just a lockscreen.
So I found "Nolock" on the market, which is almost perfect, only problem is that it unlocks with hardware buttons as well. Perfect solution would be to only unlock with a tap on the turned off screen, which cannot be delivered in any other way but your finger(e.g: in your pocket it shouldn't work, thanks to the capacitive touchscreen), and hardware buttons wouldn't react.
Is it possible somehow?
I can't belive nobody is interested!
Bump!
you will need a willing developer to use the source code from NoLock then add the features you want to it
i'm using NoLock as well, it works perfect the way it is
i want to be able to read my stuff as soon as i wake up the phone
Well, no lock developer tells it's not possible to disable volume buttons. I wonder if this problem could be solved at all.
Does it not pushed on in your pocket? This is my only fear about this app.
nope, not at all, never had it turn on, on its own
AllGamer said:
nope, not at all, never had it turn on, on its own
Click to expand...
Click to collapse
Thanks, so I give it a try!
So, I downloaded and launched it perfectly... everything so far i tried is working fine except the lock screen... Some times when i press the Cancel key the button lights lid up but there is nothing on the screen and sometimes it appear the lock screen but nothing happen....
Do someone have any solution to this...
Thank you.
I have the same problem. I have been reading that possibly going back to an older kernel / roofs fixes this problem but have not seen and confirmed reports.
Can anyone confirm this and what version?
Thanks
Same problem at me. Both builds are running very fine for some tine but after that are running slow.I don't know why. Maybe is somehow related with the lockscreen problem?
I have this problem as well i get lucky if i manage to move passt the lock screen and the OS runs really slow it takes like 20 seconds just to open the app screen and the app screen laggs like no to morrow how come so menny ppls can get it to run just fine but i cant it makes me sad face
+1 one for me... I have got a TOPA100, it's almost impossible to wake up the device, sometimes the lockscreen is visible, but it's impossible to move the unlock slider. Usually I need about 10 times and something around 5 Minutes to wake up the device.
Same problem here, would be great if this can be fixed...
RaZz0r12 said:
I have this problem as well i get lucky if i manage to move passt the lock screen and the OS runs really slow it takes like 20 seconds just to open the app screen and the app screen laggs like no to morrow how come so menny ppls can get it to run just fine but i cant it makes me sad face
Click to expand...
Click to collapse
For me it's the same and the battery runs only for one hour, I think a (system?)process is running with 100% CPU time. I am new to android, so I don't know where to look.
Same here on an AT&T Pure. Sure would love to get this fixed however I'm reasonably noob to the Android world (not completely novice to linux in general, and I have successfully flashed my AT&T TyTN II thanks to this site.) Fixing this would be a huge help!
Thanks
More specifically on my device I encounter. The following:
- Turn screen off via end button.
- Turn on screen via call button.
HW button lights come on for a few seconds then cut themselves off.
Screen does not turn on at this point.
- Turn on screen via call button again
- Screen comes on with HW button lights
about half the time screen is unresponsive and will not all me to unlock with swipe of finger
Other times will accept input and unlock to the home screen
When unresponsive repeating entire process above will likely allow me to unlock successfully.
Thanks!
Sent from my AT&T Pure using XDA App
same
my screen never wakes up
end up using soft reset to windows mobile
(it could be something to do with startup??)
This started happening about two weeks ago. During a call when I pulled the phone away from my face in order to press the end call button, the screen did to wake up. I could not end the call. This has been happening quite regularly now. The screen simply does not turn on after or during a call. Even if the other person ends the call from his side, the screen on my phone does not start.
I was using the stable version of the official CM7 at that time so I flashed the rom again. Since that did not work, I did a clean installation of Mebitek's CM7 without restoring any backups. But I am still having the problem. I am now using the power button to end the call like a handicap person would.
I think something might be wrong with the proximity sensor or my battery. Since, I have absolutely no expertise of how the phone functions, I seek help from you guys. Please give me some suggestions.
try changing the proximity delay
Flash new rom.
dheeraj (dhlalit11) said:
try changing the proximity delay
Click to expand...
Click to collapse
Even i face the same issue, i have tried flashing many roms and even tried installing the Samsung official gingerbread firmware with the odin software.It is still the same, display does not wake up after the call. any solutions pls.....
AW: Screen not waking up after call ends or during call.
Do u use a screen protector? I heard some might cause problems with proximity sensor.
Screen protector and wakelock
Masrepus said:
Do u use a screen protector? I heard some might cause problems with proximity sensor.
Click to expand...
Click to collapse
I used to have this same problem. The problem seems to be a combination of the screen protector/case getting in the way of the ambient light sensor and therefore not allowing the phone to accurately measure ambient light, and the phone going into some sort of sleep mode. I usually wipe my ambient light sensor off, and adjust my silicone case to allow the light to come in, but the thing that solved the problem for me permenantly was running the small app called wakelock to keep the system from going into complete standby. I am sure that this solution affects battery life, but I still get 10-12 hours between charges which is enough for me.
This thread talks about a similar problem, and this is where I got the idea to try this fix for our problem: http://forum.xda-developers.com/showthread.php?t=1491223
rodjoo said:
No no no guys.. don't bother with reflashing and stuff, that's not the problem.. I had the same problem and I googled it for months until I've learned its a Samsung wifi hardware related problem and mostly Galaxy devices are affected. Something is wrong when phone goes in standby. It continues to work but you can't wake it and you have to reinsert battery to get it on again.
The solution is to install a tiny app called Wake Lock, it's there on market.. it keeps phone awake even when you lock screen. My phone doesn't shut off anymore and I can finally rely on it. I don't have to think anymore and check all the time if the phone is off and if I'm going to miss a call...
The alternative is to turn off wifi before you lock screen but I think that most of us need wifi on all the time to get mails and messages on time
Click to expand...
Click to collapse
Galaxy mini doesn't have ambient light sensor.
My mistake
yackovsky said:
Galaxy mini doesn't have ambient light sensor.
Click to expand...
Click to collapse
I am of course mistaken. It is the proximity sensor that is malfunctioning due to the screen protector and case.
dheeraj (dhlalit11) said:
try changing the proximity delay
Click to expand...
Click to collapse
Where to locate that setting?
I have tested OK Google to respond to my commands , from sleep, for the past few days. with positive results.
Ok Google, responds when screen is off /sleep mode.
If your data is on, it will return a result eg Weather report, time eg.
I have tested it with lock screen.
Fingerprint, Pin working fine.
Also no lockscreen, working fine.
However it cannot turn screen on
As Google, is enabled in my Edge Lighting settings
when i say Ok Google, my Edge Lighting "lights up " and Ok Google will respond to my command.
( See screenshot.)
On my previous handsets Ok Google only worked
when screen was on.Never from sleep /screen off.
Any alternative info, results ?
but what ?
this is good news.
Ok Google works, but....
if screen can turn on, it would be 100 %
Best scenario will be to try youself and see what your results is.?
Same or otherwise?
As in past,
Xda members using Samsung devices
eg Note 5 or S8 etc could not get Ok to wake from
sleep /off. Samsung restricted ?
I posted OK Google results as there's
been a few threads on older to current devices
try to get Ok Google to wake/respond, from sleep.
Odd. My Note 8 screen will turn on and unlock when I say "OK Google". I've only tested this at home though, and I have Smart Lock keep my phone bypass fingerprint/PIN at home. Will try later somewhere else.
Wait, I just noticed on Smart Lock setting that there's a section for "OK Google detection". Maybe you have yours turned off? Say "Smart Lock" to Bixby or go to Settings>Lock Screen and Security>Smart Lock>Trusted Voice>OK Google detection and turn on the two options there ("say 'OK Google' at any time" and "Trusted Voice")
I've been using Bixby and everything seems to work OK and if she has a hiccup I help her with it (trying to build my pay points lol) but yeah try with Bixby and see if there is a difference
willcor said:
I have tested OK Google to respond to my commands , from sleep, for the past few days. with positive results.
Ok Google, responds when screen is off /sleep mode.
If your data is on, it will return a result eg Weather report, time eg.
I have tested it with lock screen.
Fingerprint, Pin working fine.
Also no lockscreen, working fine.
However it cannot turn screen on
As Google, is enabled in my Edge Lighting settings
when i say Ok Google, my Edge Lighting "lights up " and Ok Google will respond to my command.
( See screenshot.)
On my previous handsets Ok Google only worked
when screen was on.Never from sleep /screen off.
Any alternative info, results ?
Click to expand...
Click to collapse
is this with the stock launcher?
danon.brown said:
is this with the stock launcher?
Click to expand...
Click to collapse
I'm using Nova Prime.
However, i switched over to stock launcher, TouchWiz /Samsung Experience, and it was working fine.
As stated in previous threads (in past) you could not
wake device with Ok Google.
Yes with the Note 4 or previously you could.
With Note 5 etc it was suddenly not possible.
(Samsung ?)
harveydent said:
Odd. My Note 8 screen will turn on and unlock when I say "OK Google". I've only tested this at home though, and I have Smart Lock keep my phone bypass fingerprint/PIN at home. Will try later somewhere else.
Wait, I just noticed on Smart Lock setting that there's a section for "OK Google detection". Maybe you have yours turned off? Say "Smart Lock" to Bixby or go to Settings>Lock Screen and Security>Smart Lock>Trusted Voice>OK Google detection and turn on the two options there ("say 'OK Google' at any time" and "Trusted Voice")
Click to expand...
Click to collapse
Yes , when i tested it Smart Lock was off/not enabled ,but configured .
I don't use lockscreen ,
as phone is in a case .So Smart Lock won't work
OK Google wake up ,
works overall without lock screen or lock screen with Smart lock enable or not .
Point is ,
that you could not wake OK Google from sleep ( Samsung restricted ?)
Question is ,
what did Samsung do ,that Ok Google works .?
or did Samsung "slip up "/ bug ,that it works.?
and this( not turning screen on ) is the reason why it works fine , but does not/.cannot,turn screen on ?
Maybe later Samsung restricts it again .?
willcor said:
Yes , when i tested it Smart Lock was off/not enabled ,but configured .
I don't use lockscreen ,
as phone is in a case .So Smart Lock won't work
OK Google wake up ,
works overall without lock screen or lock screen with Smart lock enable or not .
Point is ,
that you could not wake OK Google from sleep ( Samsung restricted ?)
Question is ,
what did Samsung do ,that Ok Google works .?
or did Samsung "slip up "/ bug ,that it works.?
and this( not turning screen on ) is the reason why it works fine , but does not/.cannot,turn screen on ?
Maybe later Samsung restricts it again .?
Click to expand...
Click to collapse
there is an option in the Google settings "Say ok Google anytime"
danon.brown said:
there is an option in the Google settings "Say ok Google anytime"
Click to expand...
Click to collapse
Yes, all my settings are correct.
The option you refer to, I'm aware of, it's enable.
My take on Ok Google waking screen, (which
it had never over past years done) , is Samsung
restricted it in favour of S voice and now with Bixby.
However somewhere they let it "slip" and Ok Google
wakes up from sleep.
My take on this us if Samsung realizes
it, they will again restict Ok Google wake up.
Even though on other handset brands, Ok
Google wakeup works fine.
Just on Samsung phones i believe it's a issue.?
Otherwise my Ok Google and Google Assistant and Bixby is working 100 %.
No other issues with them.
I don't understand what your problem is. You're saying it is waking up but not waking up in some circumstances? Samsung hasn't restricted anything on this phone (Note 8) as far as I can tell. I'm able to get my screen to unlock from sleep by saying "Okay Google." The phone unlocks and the screen turns on and goes to the Assistant app as expected.
What exactly is wrong on your end?
This is also on my s7,s8. I don't think it's note 8 specific.
Sent from my SM-N950U using Tapatalk
When I say Ok Google...all I get is a buzz...then a buzz after my command...but no other results.
SiNJiN76 said:
When I say Ok Google...all I get is a buzz...then a buzz after my command...but no other results.
Click to expand...
Click to collapse
You may have to clear cache of the Google app and set it up again. I had to do that after I installed Nova and turned on the hotword button.
Sent from my SM-N950U using Tapatalk
danon.brown said:
You may have to clear cache of the Google app and set it up again. I had to do that after I installed Nova and turned on the hotword button.
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Nice! That worked. Prior to it...I guess if I unlocked the phone real quick, it would give me the answer. But now it just does it with the screen off. Thanks. :good: Now is there a way to get a chime instead of a buzz?
After setting up voice and resetting data. Google assistant was reset and setup. Now the Screen turns on when I say OK Google. Ok. Worked Once.
I just wish it would by pass my pin and or fingerprint but I understand anyone that may sound like me could say ok Google and get into my phone....but it would be dope if I say ok Google and it bypasses locks because it knows my voice specifically
peacey8 said:
I don't understand what your problem is. You're saying it is waking up but not waking up in some circumstances? Samsung hasn't restricted anything on this phone (Note 8) as far as I can tell. I'm able to get my screen to unlock from sleep by saying "Okay Google." The phone unlocks and the screen turns on and goes to the Assistant app as expected.
What exactly is wrong on your end?
Click to expand...
Click to collapse
I'm not just talking about Note 8.
The past few years, on on previous Samsung
devices, you could not wake Ok Google from
sleep.
There were quite a few threads (over the years) discussing this issue and how to "fix" issues.
It was obvious from previous thread discussions that Samsung had something to do with phone not able to wake from sleep. (Restricted?)
Otherwise Ok Google worked fine.
I can recall the last Samsung device, that could do this
eg. waking from sleep and responding to commands, was my Note 4.
In my case with Note 8, Ok Google works fine, waking from sleep and responding to commands..
However my screen lights up, but does not turn screen on.
Screen stays black, but Ok Google working fine.
I'm looking to see if other members have a similar
issue /experience, with Ok Google waking etc, but not turning screen on.?
On your side,
it seems like you got no issues with
Ok Google turning screen on.
danon.brown said:
This is also on my s7,s8. I don't think it's note 8 specific.
Click to expand...
Click to collapse
Yes i agree.
It's not just Note 8.
I had this issues since Note 5 days.
This is why i maintain Samsung
had something to do with it (over the years)
Maybe as result of Knox and security issues.,who knows?
But now on Note 8,
Ok Google is able to wake from sleep again.
willcor said:
I'm not just talking about Note 8.
The past few years, on on previous Samsung
devices, you could not wake Ok Google from
sleep.
There were quite a few threads (over the years) discussing this issue and how to "fix" issues.
It was obvious from previous thread discussions that Samsung had something to do with phone not able to wake from sleep. (Restricted?)
Otherwise Ok Google worked fine.
I can recall the last Samsung device, that could do this
eg. waking from sleep and responding to commands, was my Note 4.
In my case with Note 8, Ok Google works fine, waking from sleep and responding to commands..
However my screen lights up, but does not turn screen on.
Screen stays black, but Ok Google working fine.
I'm looking to see if other members have a similar
issue /experience, with Ok Google waking etc, but not turning screen on.?
On your side,
it seems like you got no issues with
Ok Google turning screen on.
Click to expand...
Click to collapse
Try clearing the cache of the Google app and setting it up again.
Sent from my SM-N950U using Tapatalk
Strange thing is happening recent to me...
Namely, while using headphones while talking on the phone, the unit gets unlocked while in pocket and problems arise with spontaneous keys getting activated.
If even cannot be explicitly locked by pressing the power button.
Have not found a solution to this problem, and it's strange why the proximity sensor does not work in pocket.
Cannot remember whether this was previously, or is it since last ROM upgrade.
Anyone having same problem?
tomsag said:
Strange thing is happening recent to me...
Namely, while using headphones while talking on the phone, the unit gets unlocked while in pocket and problems arise with spontaneous keys getting activated.
If even cannot be explicitly locked by pressing the power button.
Have not found a solution to this problem, and it's strange why the proximity sensor does not work in pocket.
Cannot remember whether this was previously, or is it since last ROM upgrade.
Anyone having same problem?
Click to expand...
Click to collapse
Yep I have the same thing... Today my pocket took 9599295 pictures and movies.. also when I'm a bit sweat my pocket dial random numbers. I've noticed that when screen is touched and disnt recognize fingerprint then whole lockscreen shows up and its easy way to random open dial or camera... Its rly anoying, because I dont want to hide phone screen outside of the skin. (Its easier to break screen if I hit something with my leg.)
Dunno why it doesnt use proximity sensor to recognize that phone is in the pocket like every other brand... :/
Do you have the double tap to wake up activated?
I had this problem a while ago and it was the double tap that played all kinds of tricks calling emergency and taking pictures in my pocket! Disable double tap to wake up screen and the problem goes away.
Disable the fingerprint icon on when the screen if off.
Gokh said:
Disable the fingerprint icon on when the screen if off.
Click to expand...
Click to collapse
Tried everything but the problem is eventually still there. Actually I've found a bug, namely the display will wake up once touched several times near the center of the fingerprint reader. Try it yourself.
Not nice - cannot avoid to happen it sometimes even if all options are disabled.
tomsag said:
Tried everything but the problem is eventually still there. Actually I've found a bug, namely the display will wake up once touched several times near the center of the fingerprint reader. Try it yourself.
Not nice - cannot avoid to happen it sometimes even if all options are disabled.
Click to expand...
Click to collapse
I didn't have this problem. If I try now and touch the part with the scanner, doesn’t have to be just the centre of the scanner, rapidly around ten times the lock screen will turn on, but nothing happens when I touch the shortcuts. Perhaps they are disabled, so the only thing that happens if the scanner is touched again is that the numpad to unlock with pin appears.
This is not good as it may severely affect battery life if it happens a lot. This clearly must be a bug!
gerhard_wa said:
I didn't have this problem. If I try now and touch the part with the scanner, doesn’t have to be just the centre of the scanner, rapidly around ten times the lock screen will turn on, but nothing happens when I touch the shortcuts. Perhaps they are disabled, so the only thing that happens if the scanner is touched again is that the numpad to unlock with pin appears.
This is not good as it may severely affect battery life if it happens a lot. This clearly must be a bug!
Click to expand...
Click to collapse
Even worse, since it is happening all the time while on a call via BT and my phone is in the pocket. I am now thinking about to switch over to my old MI8...
Cannot understand why the keyboard is not disabled in the pocket. Seems so easy to do it but it's as it seems on.
tomsag said:
Even worse, since it is happening all the time while on a call via BT and my phone is in the pocket. I am now thinking about to switch over to my old MI8...
Cannot understand why the keyboard is not disabled in the pocket. Seems so easy to do it but it's as it seems on.
Click to expand...
Click to collapse
My only solution was to buy a flip case. At first, I disabled the fingerprint reader by removing all fingerprints and setting up face recognition, but this didn’t fix the problem you are talking about. I don’t really like flip cases, but the Nillkin QIN Smartcase is rather good.
So now I ‘m eagerly awaiting a fix from Xiaomi so I can strip the Mi9 again!
Gokh said:
Disable the fingerprint icon on when the screen if off.
Click to expand...
Click to collapse
Where can the fingerprint icon be disabled? Thank's.
j4dotcc said:
Where can the fingerprint icon be disabled? Thank's.
Click to expand...
Click to collapse
Disabling the fingerprint icon has no effect on the problem we are talking about here. The only way to make the problem go away is to remove all the stored fingerprints thus disabling the use of fingerprints all together. This will shut off the fingerprint sensor doing away with this problem in a crude way.
If you really are looking for a setting, please use the search function at the top of the settings.
gerhard_wa said:
Disabling the fingerprint icon has no effect on the problem we are talking about here. The only way to make the problem go away is to remove all the stored fingerprints thus disabling the use of fingerprints all together. This will shut off the fingerprint sensor doing away with this problem in a crude way.
If you really are looking for a setting, please use the search function at the top of the settings.
Click to expand...
Click to collapse
Thanks for the prompt reply. I don't have the problem and just wanted to know where I can disable the fingerprint icon. Thanks again.
New uppdate out that include Pocket Mode. MIUI-V10.2.27.0PFAEUXM EEA version.