I made this account to adrress the issue here, as ive not seen someone realy give an answer before apart from 'restart your device' or 'turn air command on'
The story s short: one day it worked, the other day i updated the tab to 4.2 and then it stopped working... i went back to 4.1 and it still didnt work, so now im stuck without being able to open the menu, nor can i use the button related features.
Ive tested my s pen on other note, and it works perfectly too, so im sure it has to do with my device.
Any help, ideas or well... anything???
Thanks in advance
jpkillerage said:
I made this account to adrress the issue here, as ive not seen someone realy give an answer before apart from 'restart your device' or 'turn air command on'
The story s short: one day it worked, the other day i updated the tab to 4.2 and then it stopped working... i went back to 4.1 and it still didnt work, so now im stuck without being able to open the menu, nor can i use the button related features.
Ive tested my s pen on other note, and it works perfectly too, so im sure it has to do with my device.
Any help, ideas or well... anything???
Thanks in advance
Click to expand...
Click to collapse
Some more info: i checked and in 4.1 theres no air command option now (if there ever was). Cant remember if there was such an option in 4.2, but i guess there was...
Maybe i somehiw turned it off, then it dssapeared then when i went back to 4.1 i lost the option to actually turn it on??????
See if you have Spen settings under System
Sent from my GT-N5110 using Tapatalk
mankand007 said:
See if you have Spen settings under System
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
There was is Air Command in Note 8.0. Air command was introduced with Note 3.0
however, if you mean the "quick command" then you press the button on pen and drag from bottom of screen towards top.
and that should bring out the panel for you.
S pen not working
I have an Note 8 N5120. I have also lost access to my pen. The pen itself works fine on my Note 2. It is possible that it was related to the latest update to version 4.2.2. I do not have any idea how to get access back. I am probably going to do a factory reset but I didn't really want to lose my level in Candy Crush . Rooting is another possibility and of course it could be the proximity sensor hardware in the device. If anyone else has run into this and then fixed it please let us know.
intelliriffer said:
There was is Air Command in Note 8.0. Air command was introduced with Note 3.0
however, if you mean the "quick command" then you press the button on pen and drag from bottom of screen towards top.
and that should bring out the panel for you.
Click to expand...
Click to collapse
what I meant was trying to bring up to the menu by touching the button On The spen.
I rooted my girlfriend's S3 with no problems. I can install a TW rom and everything works as expected. If I installed a ASOP rom, when a call is made or received the screen turns off. If you pull the phone away from your ear the screen stays off. I've browsed around the forums, but have not found anything to resolve the issue. Any ideas of what might cause this on ASOP roms ?
Thanks in advance,
Richard
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
You could test the proximity sensor response. It might be flaky?
I use this app,
https://play.google.com/store/apps/details?id=com.tbs.activity
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
audit13 said:
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
Click to expand...
Click to collapse
The only time it has been an issue is with ASOP roms. If I use a TW rom, there is an option to leave the screen on during a call. This is what I clicked to get the screen on during calls. However, with ASOP roms there is not an option for this. I don't think it's the proximity sensor since the screen stays on with calls on a TW rom. I forgot to mention that the ASOP was KK rom, but I have the same phone different cell provider and do not have this issue. I think I tried a JB rom with the same effect.
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
audit13 said:
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
Click to expand...
Click to collapse
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
riche1 said:
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
Click to expand...
Click to collapse
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
audit13 said:
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
Click to expand...
Click to collapse
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
riche1 said:
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
Click to expand...
Click to collapse
Without making any changes to the stock TW ROM dialer settings, does the screen go black when you place the phone next to your ear and come back on when you move it away from your ear?
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
riche1 said:
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
Click to expand...
Click to collapse
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
audit13 said:
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
Click to expand...
Click to collapse
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
riche1 said:
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
Click to expand...
Click to collapse
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
audit13 said:
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
Click to expand...
Click to collapse
she said it was not a problem until the phone was updated to 4.3 through ATT software update. This was way before I rooted the phone. The same thing started with her sister's phone. So.. I'm stumped as to what the problem could be. I rooted it because I thought CM11 might fix the issue and that was not the case. I don't know how I can go about fixing it. I don't want to take a chance in bricking the phone.
Has anyone been able to integrate the S5 anti call interruption
Mini screen.
I hate when driving using gps or recording my daughter's
Graduation and someone calls and compleatly takes over.
Please help.
NWWADD said:
Has anyone been able to integrate the S5 anti call interruption
Mini screen.
I hate when driving using gps or recording my daughter's
Graduation and someone calls and compleatly takes over.
Please help.
Click to expand...
Click to collapse
You know theres a "Incoming calls" selection in blocking mode? Just turn blocking mode on when you dont want to be interrupted
I don't want to disable calls from coming in to the phone I just don't want them taking over the phone completely.
whatever you're in
the Galaxy s5 has a pop up screen that overlay any app your in.
NWWADD said:
I don't want to disable calls from coming in to the phone I just don't want them taking over the phone completely.
whatever you're in
the Galaxy s5 has a pop up screen that overlay any app your in.
Click to expand...
Click to collapse
So I forgot about a mod I came across in the International forums that actually enables it. Some people were claiming it worked great, few others said it was kinda buggy, Its actually really simple to do by decompiling the secphone and making a few changes. Itll only take like 5 minutes to do so if you want to post a copy of your secphone.apk I'll hook it up and you can try it out for yourself. Youre gonna have to be atleast rooted tho
hie guys , i have a galaxy note 10+ n975f/ds which got cracked recently ,now only the s pen works fully but i cannot use the touchscreen . a few days ago i noticed that if i make a phone call , i am able to fully use the device touchscreen without any issues but as soon the phone call drops , only the s pen works and the touchscreen stops working . so i am wondering if there is a hack or anyone willing to help me to make the device think i am using my s pen and make it activate the touchscreen or maybe to spoof a fake call all the time and make the device thinks i am making a phone call so that the touch starts working just like how it works when i am making a call . my device is rooted with magisk and on android 11 binary 7 . please help
cliffordmoyo said:
hie guys , i have a galaxy note 10+ n975f/ds which got cracked recently ,now only the s pen works fully but i cannot use the touchscreen . a few days ago i noticed that if i make a phone call , i am able to fully use the device touchscreen without any issues but as soon the phone call drops , only the s pen works and the touchscreen stops working . so i am wondering if there is a hack or anyone willing to help me to make the device think i am using my s pen and make it activate the touchscreen or maybe to spoof a fake call all the time and make the device thinks i am making a phone call so that the touch starts working just like how it works when i am making a call . my device is rooted with magisk and on android 11 binary 7 . please help
Click to expand...
Click to collapse
Don't have a hack for you, but you may be able to determine if your lack of touch ability is due to the screen thinking there is a constant press happening.
In developer options turn on "show taps" & or "pointer location"
nope there is no constant pressing when i enable show touches , im very sure the touchscreen is broken because when i dial *#0*# and select touch option to test the touch screen only a super small area on the botton part works and there are some chips missing, i can even see the RGB colours poking through the area that has some chips missing. but when making a call the whole device responds to touch . any exposed module/s that can make me access my device's sensors ,maybe i might find a workaround lol