Note 3 - Air Command - Touch unresponsive - Galaxy Note 3 Q&A, Help & Troubleshooting

Hello,
I've tried searching for this issue but didn't find the same issue, although there were issues where finger touch didn't work but s-pen did.
I have a Note-3 and got a recent patch update from Samsung after the release of 5.0. I believe from then on, the below issue started occurring.
At any screen, if i remove s-pen, the 'air command' comes up and the screen goes completely unresponsive to finger as well as s-pen. After few seconds, i get a pop-up saying "Process system isn't responding, Do you want to close it". I'm able to touch 'wait' or 'ok' but no matter which option i choose, within 3 second the phone does a quick reboot. in that 3 seconds the screen is still unresponsive to touch.
If i leave the s-pen out while reboot, everything is fine until i press the button on the s-pen to bring the 'air command'. If i change the option under 'detachment options' to any thing other than 'air command' the phone is normal while removing the s-pen and i can use s-pen until i press the button on the s-pen to bring 'air command'.
Note: I've not rooted this phone since 5.0 got released/installed.
Any ideas people?
Regards,
Rubert.

Hi, thank you for using XDA Assist. The best place to ask questions about your device in it's specific forum here, http://forum.xda-developers.com/galaxy-note-3 I'm going to ask a moderator to move this question to, http://forum.xda-developers.com/galaxy-note-3/help

jd1639 said:
Hi, thank you for using XDA Assist. The best place to ask questions about your device in it's specific forum here, http://forum.xda-developers.com/galaxy-note-3 I'm going to ask a moderator to move this question to, http://forum.xda-developers.com/galaxy-note-3/help
Click to expand...
Click to collapse
Thanks a lot mate.

Delete

rubertjack said:
Hello,
I've tried searching for this issue but didn't find the same issue, although there were issues where finger touch didn't work but s-pen did.
I have a Note-3 and got a recent patch update from Samsung after the release of 5.0. I believe from then on, the below issue started occurring...
...Note: I've not rooted this phone since 5.0 got released/installed.
Any ideas people?
Regards,
Rubert.
Click to expand...
Click to collapse
You could try clearing the Data/cache for anything in Apps that looks like it belongs to the SPen - I haven't used TW Stock for some time so can't check the options.

Journyman16 said:
You could try clearing the Data/cache for anything in Apps that looks like it belongs to the SPen - I haven't used TW Stock for some time so can't check the options.
Click to expand...
Click to collapse
Forgot to mention in the original post. I've actually did a factory reset and still the problem persists.

rubertjack said:
Forgot to mention in the original post. I've actually did a factory reset and still the problem persists.
Click to expand...
Click to collapse
You probably won't like this but go CM and buy the SPenCommand app - works great! (sorry - I'm not big on Sammy ROM's but you might try Alliance...?)

I would love to use CM. But unfortunately my phone is n900 and still there are no aosp roms. I don't want and like to use modified stock rom.

rubertjack said:
I would love to use CM. But unfortunately my phone is n900 and still there are no aosp roms. I don't want and like to use modified stock rom.
Click to expand...
Click to collapse
Before I started on Temasek's CM ROMs I was using Alliance - stock/modded ROM. You could give it a try and see if it helps?

Journyman16 said:
Before I started on Temasek's CM ROMs I was using Alliance - stock/modded ROM. You could give it a try and see if it helps?
Click to expand...
Click to collapse
I shall give it a try. just wondering, are you guys aware of any good and working aosp roms out there for n-900 exynos?

rubertjack said:
I shall give it a try. just wondering, are you guys aware of any good and working aosp roms out there for n-900 exynos?
Click to expand...
Click to collapse
You could try on the cyanogen site. Or do a search at the parent forum Galaxy Note 3

There's a Q&A thread for Dr.Ketan's ROM for n900 - try in there for a link to the ROM? http://forum.xda-developers.com/galaxy-note-3/help/qa-k14-dr-ketan-custom-control-rom-t2914663 Not sure if it's AOSP or not but Dr.Ketan seems to know what he's doing from other threads I have seen.

As of now only CM team is building beta ROM for n900. Per my findings, many failed because of the octa core and too many issues. Will wait for CM to release an official one. I too hate Sammy. poor DPI.

Related

[Q]mod's in stock rom.

Good afternoon.
last night I decided to flash the rom pacman and I met some pretty annoying bug, and I was able to understand several rom (all?) is a concern for
fc and various bug. but since the stock rom is a smooth copy, I decided to stay in stock rom and to add various mod's. concern is that I have not yet figured out how to switch to full screen in a stock rom (yes I know it's heavy, but we all go through from the galaxy and I have to relearn everything) .
So here are my some applications:
1: how to pass in true full screen (and not transparent bar) IN STOCK ROM.
2: could you tell me where I can find a theme add a stock rom, which is already well on root
3: to change the color of the screen with the Franco kernel that doije do exactly ... thank you very much for you patience and hand made for your precious help ...;-p
Did you hear about Q&A section? ?? If not, check this
https://www.youtube.com/watch?v=JmvCpR45LKA&feature=youtube_gdata_player
and you, you are a mortal antipathy ...
to be as I know, its not the first question to be asked here ...
alessa said:
and you, you are a mortal antipathy ...
to be as I know, its not the first question to be asked here ...
Click to expand...
Click to collapse
Not first and not last.... Thanks to Noobs
Close or move please.
and how to move?
alessa said:
and how to move?
Click to expand...
Click to collapse
Ask for it. Each section have a moderators. They will do it for you.
Sent from my GT-I9305 using xda app-developers app

Mako Android L B4 causing problems?

Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
ilum90 said:
Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
Click to expand...
Click to collapse
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Rohit02 said:
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Click to expand...
Click to collapse
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
ilum90 said:
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
Click to expand...
Click to collapse
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Rohit02 said:
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Click to expand...
Click to collapse
At first, i installed another rom like paranoid 4.45 20140729 and it didnt work, it got worse.
When i would make a call, the screen would turn off and couldnt get to back on and it does but not even for a sec so it kept remaining wit a screen off but the call was still going.
The next step i tried AOSP build 12 rom, with same kernel and it also didnt work. Same as before when i had CM 11.
I just installed CM 11 rom with hellscore b55 CM anykernel and it does the same thing.
My only next step based on your opinion is trying AOSP rom with hellscore kernel (not the CM version).
Is there anything else i can try if the aosp wit hellscore kernel doesnt work?
could you indicate me where to get the stock kit kat because i see versions of them and im not sure if their stock or not.
is it also possible to use stock with hellscore kernel?
Much appreciate for all the help you have given me so far.
Same problem with simple AOSP with hellscore b55 anykernel.
Any other ideas?
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
RolF2 said:
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
Click to expand...
Click to collapse
I can't believe it! After all this time, blaming on the software so hard and for the last resort I actually did dissembled my N4 to check the sensors and everything but did nothing. But dude, you solved the mystery! Everything is working perfectly now. I can't appreciate how thankful I am. Many thanks

[Q] Request - Volume rocker wake up on stock Android 5.0.1 LRX22C

Hi all,
I tried researching on every thread possible, but couldnt find an answer. Thats why i am starting this thread.
I am on stock android 5.0.1 LRX22X rooted. I tried using VolumeOpen.apk, but it doesnt work on latest Android L version.
I dont want to use any custom ROMs, want to stay with the Stock version. Please suggest a solution for volume button wakeup, as my power button has become very flimsy.
Many Thanks
sulaimanz said:
Hi all,
I tried researching on every thread possible, but couldnt find an answer. Thats why i am starting this thread.
I am on stock android 5.0.1 LRX22X rooted. I tried using VolumeOpen.apk, but it doesnt work on latest Android L version.
I dont want to use any custom ROMs, want to stay with the Stock version. Please suggest a solution for volume button wakeup, as my power button has become very flimsy.
Many Thanks
Click to expand...
Click to collapse
i was searching for the same thing a few days ago. the only thing i could find is simple aosp rom. it is essentially stock with a few mods. go to the thread and decide for your self. i jumped to simple aosp and i am never going back to stock untill xposed comes out!
+1 for this request
[GS] said:
+1 for this request
Click to expand...
Click to collapse
+1.......
[GS] said:
+1 for this request
Click to expand...
Click to collapse
+1 I'd like that too!
Any idea some method to compile?, you can try making

all custom roms sucks...as much you gain from them you loose more

I tried every rom posible and all have the biggest bug ever ...at least for me it is but nobody is talking about ...there is something i don't know ? there is no need to be mean to my question but why all roms have this problem with keeping the playstore apps updated ...why the apps revert to previous versions and why this is hapening only to custom roms ?.. if then i ask you what is the use of custom roms? ...
these days even a five years child can root install a custom cwm , a custom kernel a viper4 sound mod and debloat a original stock rom
Lol.
I haven't experience anything like that, in any Roms i have flashed.
Throw your s4 and buy some updated android device.
Sent from my GT-I9505 using Tapatalk
1. You opened a thread in wrong place Kiddo
2. be gratefull for what you have , youre problem is very original UNIC maybe congrats for being UNIC
3. Some moder delete this
What kind of gapps are you running? I've been using opengapps for every custom ROM I've used and had no issue what so ever.
Sent from my GT-I9505 using Tapatalk
stafiejulien said:
I tried every rom posible and all have the biggest bug ever ...at least for me it is but nobody is talking about ...there is something i don't know ? there is no need to be mean to my question but why all roms have this problem with keeping the playstore apps updated ...why the apps revert to previous versions and why this is hapening only to custom roms ?.. if then i ask you what is the use of custom roms? ...
Click to expand...
Click to collapse
maybe you are not clever enough
stafiejulien said:
I tried every rom posible and all have the biggest bug ever ...at least for me it is but nobody is talking about ...there is something i don't know ? there is no need to be mean to my question but why all roms have this problem with keeping the playstore apps updated ...why the apps revert to previous versions and why this is hapening only to custom roms ?.. if then i ask you what is the use of custom roms? ...
Click to expand...
Click to collapse
a custom rom is exactly what it says it is, a customised version of the original android operating system that somebody has, in their own precious time, played around with to try & give us something a little different for this ageing device. Chances are that if you went out tomorrow & bought an S7 edge & fired it up you would have to update some gapps, whichever you may use. I think you need to take a deep breath & have a little more appreciation & understanding for the things that go on here. If a 5 yr old is able to do what you claim then maybe you should turn your hand to contributing to the community................... but thats just my opinion......no offence intended
Is this guy for real? Apps simply don't revert to previous version after you update them. There's a simple setting in the playstore that allows auto update of your installed apps to the latest version when they become available. And is this how you lose from custom Roms? Lololololol I thought your device blew up or melted.
Buy an IPhone and explain us how cool is it. You'll enjoy it, for sure
Pls close delete this thread its useless.
Sent from my GT-I9505 using Tapatalk
droidblitz said:
Lol.
I haven't experience anything like that, in any Roms i have flashed.
Throw your s4 and buy some updated android device.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
The problem isn't the phone, it's the user.
Just close this.
scanferr said:
The problem isn't the phone, it's the user.
Just close this.
Click to expand...
Click to collapse
+1
and dude who started thread. It is simple. Don't use custom roms...
Sent from my S4 via NSA's wifi
Believe it or not, but I have seen similar behavior with some of my apps.
I update it dl today and tomorrow I have to update again, but there doesn't seem to be any changes in the changelog.
But this happens rarely.
So I believe the OP exaggerates. This also started happening only recently, so it's either something related to the new Android updates - which means older ROMs (5.1 and below) should be safe - or something related to gapps.
To everyone who asked for this thread to be closed and/or brought up the fact it's in the wrong place, why did you not click on the little triangle at the bottom left of the post and report it? Mods can't do anything about it if they don't know there is an issue.
As to the OP, I actually tried keeping an Android 2.3.3 ROM's Google apps up to date - one of the features of the ROM I offered. To do that I didn't include anything but the Play Store. Today, such a task would be difficult. If you like, you can download a GApps package from OpenGApps on a daily basis and flash it yourself.
GDReaper said:
Believe it or not, but I have seen similar behavior with some of my apps.
I update it dl today and tomorrow I have to update again, but there doesn't seem to be any changes in the changelog.
But this happens rarely.
So I believe the OP exaggerates. This also started happening only recently, so it's either something related to the new Android updates - which means older ROMs (5.1 and below) should be safe - or something related to gapps.
Click to expand...
Click to collapse
This ^^^
Strephon Alkhalikoi said:
To everyone who asked for this thread to be closed and/or brought up the fact it's in the wrong place, why did you not click on the little triangle at the bottom left of the post and report it? Mods can't do anything about it if they don't know there is an issue.
Click to expand...
Click to collapse
And this one ^^^
@OP, please be carefully when you start a thread. Development is for development not for discussions and questions.
Thread closed,
Razvan
Forum Moderator

Phone rings when called but unable to answer

Hopefully this is the correct forum, if not please let me know.
I have tried a couple custom stock XT1575 ROMs. Everything installs great except when my phone is called, the dialer
won't open. I hear my phone ring or vibrate depending on what it is using, just nothing comes up to allow me to answer
it. The latest custom stock ROM I installed today is moto_x_pure_edition_custom_stock_x1575_mphs24.107-58-1_v1-odexed.
Has this happened to anyone else, is it a known problem with the custom stock ROMs? Any help is appreciated. I can't
use the phone so it's just sitting in a corner.
Have you tried puretrue rom . I have flashed 3 roms 2 custom stock Rom and one nexus rom.But never faced this issue . Maybe clean install will help you.
azzammalik said:
Have you tried puretrue rom . I have flashed 3 roms 2 custom stock Rom and one nexus rom.But never faced this issue . Maybe clean install will help you.
Click to expand...
Click to collapse
Every time I've installed the ROM, everything was wiped first, including the install I did earlier today.
I've tried a few other ROMs from here, didn't quite like them (not sure if the one you mentioned is one I tried) so wanted to use the custom default Motorola ROM which I liked. They are rooted and have super user. If you know the link to that ROM you mentioned, I don't mind looking into it. Thanks
Go to Settings > Apps > Gear icon > Default Apps > Select 'Telephone' for Phone
Can't believe this is still a thing! This is an old *ss small issue which has been discussed over and over again!
Now with this Help thread open I hope people will learn!
ban.codrut said:
Can't believe this is still a thing! This is an old *ss small issue which has been discussed over and over again!
Now with this Help thread open I hope people will learn!
Click to expand...
Click to collapse
Yes, I understand it's been around a while. I've searched for answers and all the suggestions have not made a difference for me. I have also searched a little on here using different terms but could not find anything either. If you know the answer, can you assist? I understand you may have seen this a few times but not everyone has, like me. I just want to know the fix, is that so bad?
davidrocher said:
Go to Settings > Apps > Gear icon > Default Apps > Select 'Telephone' for Phone
Click to expand...
Click to collapse
I've already attempted that, didn't help. Tried a new dialer app, didn't make a difference either. Made sure it was the default and that notifications were on for the app also. Thanks
michont said:
Yes, I understand it's been around a while. I've searched for answers and all the suggestions have not made a difference for me. I have also searched a little on here using different terms but could not find anything either. If you know the answer, can you assist? I understand you may have seen this a few times but not everyone has, like me. I just want to know the fix, is that so bad?
Click to expand...
Click to collapse
Your described issue seems just the usual "no default phone app selected" , which solution is to just set one. If something else is going on I can't help, I've never encountered other root issues to this (not by experience not by reading). Sorry!
But we could go through this and try troubleshooting.
You are using a custom stock so probably already got root permission.
1) Install logcat or matlog
2) start recording and call your phone right away using a second phone while leaving the screen on
(try upping the screen time to 5 minutes let's say, this way there is no loginfo we are not interested in there beside the call intent)
3) After that, hangup and stop recording the log then share a link to the file here (file ! Don't paste in pls)
Let's hope there is a debug warning or error which will tell us what's actually going on!
On the other side of thing, you do have a XT1575 right ? Or you are using XT1575 Ron on XT1572 ? Not a biggie but quit relevant for modem file!
In the morning I'll give it a look, now I'm heading to bed (2AM here)
michont said:
Every time I've installed the ROM, everything was wiped first, including the install I did earlier today.
I've tried a few other ROMs from here, didn't quite like them (not sure if the one you mentioned is one I tried) so wanted to use the custom default Motorola ROM which I liked. They are rooted and have super user. If you know the link to that ROM you mentioned, I don't mind looking into it. Thanks
Click to expand...
Click to collapse
Hope you have already solved this problem. But if you are still facing same issue then this is perfect rom if you want to stay close to stock.
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
ban.codrut said:
Your described issue seems just the usual "no default phone app selected" , which solution is to just set one. If something else is going on I can't help, I've never encountered other root issues to this (not by experience not by reading). Sorry!
But we could go through this and try troubleshooting.
You are using a custom stock so probably already got root permission.
1) Install logcat or matlog
2) start recording and call your phone right away using a second phone while leaving the screen on
(try upping the screen time to 5 minutes let's say, this way there is no loginfo we are not interested in there beside the call intent)
3) After that, hangup and stop recording the log then share a link to the file here (file ! Don't paste in pls)
Let's hope there is a debug warning or error which will tell us what's actually going on!
On the other side of thing, you do have a XT1575 right ? Or you are using XT1575 Ron on XT1572 ? Not a biggie but quit relevant for modem file!
In the morning I'll give it a look, now I'm heading to bed (2AM here)
Click to expand...
Click to collapse
Thanks, just got home from work myself. I am using the XT1575. The default phone app is chosen. I'll see what I can
do about the logging suggestions you mentioned. I may not get to that today as I have a few things to do before
heading into work.
azzammalik said:
Hope you have already solved this problem. But if you are still facing same issue then this is perfect rom if you want to stay close to stock.
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
Click to expand...
Click to collapse
Thank you, I'll download now.
Thanks for the assist all of you. I decided to install the TruPureXMM-2.9 ROM and so far I'm liking it. It has a few quirks but the dialer works
from the get go which is the main thing. Those ROMs from the other Moto style installs must have something inherently wrong designed
in them not to work right from the start.

Categories

Resources