Air command not showing up, hover not working as well - Galaxy Note 3 Q&A, Help & Troubleshooting

Hello there I would like to ask did any body ever face air command not working after rooting it(android version: 4.4)?
Situation:
1. Clicked the s pen button but air command not popping up
2. Pulled s pen out and heard the sound but air command not showing up
3. Hovered finger on lock screen but nothing happens
4. It happens oftenly
5. I have to click the power key to sleep the phone and click again to wake it then the s pen working again
Do anybody know why it happens
It's quite annoying when I want to use s pen but not working
Sent from my SM-N9005 using XDA Premium 4 mobile app

Related

Track pad to wake up phone

I've seen a lot of people saying they wish that clicking the track pad would wake the phone up. I agree.
From what I've found, the track pad click will wake the phone up as long as no lock is enabled. Can anyone else confirm this? I.E. no pattern or pin unlock enabled, just the green "slide to unlock" bar.
Thanks.
Sent from my T-Mobile G2
That doesn't work for me, or anyone else from what I hear
Sent from my T-Mobile G2 using XDA App
Nope, the trackpad doesn't work at all. Only when pressing the power button or sliding the QWERTY keyboard out.
I wish there was another way, like hitting the track pad button. I hate having to hit the power button cause they placed it in such an odd spot and it's not raised enough. It's fine when I'm gripping the phone closed but when I have the keyboard open and it goes back into lock, then it's a problem for me.
If your keyboard is slid open and the device locks than you can hit any button on the keyboard to unlock it
Sent from my T-Mobile G2 using XDA App
ekoulak said:
If your keyboard is slid open and the device locks than you can hit any button on the keyboard to unlock it
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Much appreciated, thanks.
last night it worked for me 15 - 16 times in a row, this was while the phone was charging (tethered to my laptop, pdanet connected)
this afternoon, at the office, i couldn't get the trackpad to work at all
tonite, back tethered to my laptop and charging, and it works 5 times in a row
only other item - i do have No Lock installed and lock disabled
PS - took it off the tether and it woke the screen, but inconsistently, connected it back to the laptop, and bingo - trackpad is waking the screen up consistently - go figure
Well this is weird. It was working for me 20 minutes ago repeatedly... now it won't. Hmmmm
P.s. I too am upset that htc switched the power/lock button to the top right as opposed to top left -.-
Sent from my T-Mobile G2

Air Command Stopped Working!

Air Command has stopped working for me. It won't trigger when I pull the s pen out (yes, it's selected to pop up when the s pen is pulled out) and won't appear when the button on the s pen is pressed.
Was playing around with buzz launcher but the phone is back to where it was when Air Command was working. Any ideas what could be causing this? Haven't changed any of the s pen settings.
Thanks!
Ditto, doesn't work for me either! Can someone please give any advice?
Fixed it. Go to settings-gestures-click air command.
Sent from my SM-N900V using Tapatalk now Free

Screen & Home button don't function

After installing Kitkat on Note 3 lte I noticed that the screen freezes and doesn't respond to finger touch. Also the Home button doesn't respond to finger pressing. I have to use S-Pen instead. After a few minutes the note 3 becomes normal... Could it be the Kirk rom that causes it... I'm open to all suggestions except taking it to the service center because of warranty void.. Thanks in advance...
Sent from my SM-N9005 using xda app-developers app

[Q] Touch screen acting out.

I cant seem to able to press stuff before the phone decides press everything around it. I get "ghost" touches randomly and mostly when there is a notification windows pops up ie. high noise level warning for music etc. it takes me a lot of tries to actually be able to press ok or cancel. any ideas?
Check you haven't got air view or touch sensitivity enabled.
Sent from my iPad using Tapatalk
I also find myself having to click apps a few times for it to recognize my touch...
Sent from my SM-G900P using Tapatalk
None of them enabled I don't know what to do..

Pin/pattern often needed to unlock?

EDIT: dkotoric has realised this is due to using the double tap to sleep function on some launchers. Locking your device with that prevents the fingerprint scanner from allowing access for some reason.
So today was my first full day with the 6P. It's a truly great device.
A whole bunch of times though when I've come to unlock the device I've had to put in my pattern because it won't accept the fingerprint scanner.
The icon at the bottom of the lock screen that should be a fingerprint is just a lock symbol. If I then lock the phone again and reunlock it works as expected.
Not sure if this is a software bug or some setting I've got wrong. Can't see a pattern for when it does it though. I've switched 'require pattern on restart' off which has made no difference.
Sent from my Nexus 6P using Tapatalk
Josh98 said:
So today was my first full day with the 6P. It's a truly great device.
A whole bunch of times though when I've come to unlock the device I've had to put in my pattern because it won't accept the fingerprint scanner.
The icon at the bottom of the lock screen that should be a fingerprint is just a lock symbol. If I then lock the phone again and reunlock it works as expected.
Not sure if this is a software bug or some setting I've got wrong. Can't see a pattern for when it does it though. I've switched 'require pattern on restart' off which has made no difference.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I've experienced that on one occasion today. That was after no occurrence in a full day's use yesterday. I put it down to slightly incorrect/incomplete/inaccurate finger print scans when it's set up.
Had no issues yet, used it for 2 days.
I have a pin set for after a reboot and it will ask for pin if I accidentally use pthe power button to switch on.
So far my finger print has not failed once o. My two index fingers.
I set up my finger print with a central / top end / bottom end / left edge / right edge and its worked fine
Been super accurate for me
Sent from my Nexus 6P using Tapatalk
I recommend using your main finger on different angles rather than using 5 different fingers when setting it up. ?
Sent from my HTC One_M8 using Tapatalk
I've setup each index finger once and it hasn't skippes a beat. I'd setup your finger again and this time move your finger around after every press to get different angles.
Sent from my Nexus 6P using Tapatalk
I haven't had any issues whatsoever. You could setup each index finger as 2-3 different fingers if you want to improve accuracy too.
Still waiting on my 6P, but I do have the 5X. Installed all of my usual apps when I received the phone. Set up fingerprint scanner. For the life of me couldn't figure out what the heck was going on. Every time I would unlock the phone it would go to PIN screen. I had read all of the reviews on how fantastic the FPS was. Started to get really annoyed. In fact I did a factory reset to see if this would help. This time I didnt install apps just set up FPS. Worked flawlessly. Installed apps again and what do you know stopped working again. Then it hit me, I have an app called ScreenOFF. Basically I could touch the screen and it would turn the screen off without hitting the power button. Uninstalled app and FPS worked perfectly. SO, be careful if you have any of these types of app as it seems it screws up the ability to bypass lock screen
It seems to have sorted itself over night. Hasn't done it so far today. Thanks guys.
Sent from my Nexus 6P using Tapatalk
what I notice is I use lock app and apex launcher so I have it set up to double tap on screen to lock the device. If I lock the device using this method I can no longer unlock the device with my fingerprint. I have to use the lock pattern. Then I have to lock the phone again via power button in order to use fingerprint scanner?
dkotoric said:
what I notice is I use lock app and apex launcher so I have it set up to double tap on screen to lock the device. If I lock the device using this method I can no longer unlock the device with my fingerprint. I have to use the lock pattern. Then I have to lock the phone again via power button in order to use fingerprint scanner?
Click to expand...
Click to collapse
Holy **** you're right yeah that's been my issue the whole time doing the same with Action Launcher. Been so used to using it it didn't occur to me that's the cause. That's annoying.
Sent from my Nexus 6P using Tapatalk
Josh98 said:
Holy **** you're right yeah that's been my issue the whole time doing the same with Action Launcher. Been so used to using it it didn't occur to me that's the cause. That's annoying.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I have your issue but I am not using any sort of double tap to lock apps. also I am using google now launcher.
Yea this happens when you use a third party app or launcher to lock the device via a double tap on the home screen. I set up a gesture in Nova Launcher to lock the device via a double tap on the homescreen and when I do I cannot unlock the phone via Imprint. There is just a lock symbol instead of the Imprint symbol and the only way to unlock it is using the pin. It seems that right now the only way to use Imprint to unlock the device is when you lock the device using the power/sleep button. Using any 3rd party software without root access to lock the device will only let you unlock the device via the pin instead of Imprint.
EDIT: Everything works fine with root access. If you grant the app performing the screen lock root access then you will be able to lock the screen with say a gesture like double tapping the home screen and then you will still be able to unlock the device via Imprint.
I had this issue as well where my 6P would ask for my pin after using the fingerprint scanner. It would do this many times per day.
What I have found to stop this from happening is removing the administrator rights from all the apps that uses it to lock the screen. It seems that the phone will ask for a pin when a 3rd party app locks the screen.
So I'll just rely on Android locking the screen on its own vs entering the pin so many times a day along with the fingerprint scanner.
guitar1238751 said:
Yea this happens when you use a third party app or launcher to lock the device via a double tap on the home screen. I set up a gesture in Nova Launcher to lock the device via a double tap on the homescreen and when I do I cannot unlock the phone via Imprint. There is just a lock symbol instead of the Imprint symbol and the only way to unlock it is using the pin. It seems that right now the only way to use Imprint to unlock the device is when you lock the device using the power/sleep button. Using any 3rd party software without root access to lock the device will only let you unlock the device via the pin instead of Imprint.
EDIT: Everything works fine with root access. If you grant the app performing the screen lock root access then you will be able to lock the screen with say a gesture like double tapping the home screen and then you will still be able to unlock the device via Imprint.
Click to expand...
Click to collapse
Are you just using nova as far as root access? I'm so used to just having greenify lock the screen, but I'm having this issue
Akomack said:
Are you just using nova as far as root access? I'm so used to just having greenify lock the screen, but I'm having this issue
Click to expand...
Click to collapse
I'm actually using loads of root apps including Greenify. (Though I'm not using greenify anymore) Everything is working fine. Are you having the issue when locking via a greenify gesture? I didn't even know Greenify had a screen locking gesture lol. Or do you mean the Imprint issue occurs after Greenify puts the device to sleep automatically?
guitar1238751 said:
I'm actually using loads of root apps including Greenify. (Though I'm not using greenify anymore) Everything is working fine. Are you having the issue when locking via a greenify gesture? I didn't even know Greenify had a screen locking gesture lol. Or do you mean the Imprint issue occurs after Greenify puts the device to sleep automatically?
Click to expand...
Click to collapse
Greenify has a widget that will hibernate and shut the screen off. I ended up finding this app that will shut the screen off and allow me to use the fingerprint to wake/unlock the device. :good:
So far, the only 3rd party app that I've found that can shut the screen off without root and without needing the pin again is Gravity Screen https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree&hl=en
It has a few widgets that you can link your double tap homescreen gesture to. Specifically, I'm using Lightning Launcher and link the double tap to the "Off" shortcut. The other shortcuts will lock the phone and then you'll need the pin again instead of just the fingerprint.
However, I think the way this app accomplishes this is to first blank the screen off with just a black overlay and then set the screen timeout to around 10seconds (it sets it right back to whatever you had before by the time you wake the screen again). So far, I haven't had a problem with this since the app also has "in pocket protection" in which it will keep the screen from turning back on if the proximity sensor is covered. So if you double tap to sleep but then put it in your pocket before the 10 seconds is up, it won't turn it back on. If you have it sitting on your desk, you can double tap to sleep, but then tap again on the black screen within the first 10 seconds to see the navigation keys again. This also has the weird side effect of not being able to use the fingerprint reader during those 10 seconds, because technically the screen is still on. This was a little unsettling at first since I couldn't figure out why the fingerprint reader wasn't vibrating when I thought the screen was "off". To me, it's not that big of a deal so it's fine with me.

Categories

Resources