I am running Android 9 on a Galaxy Note 9. On several occasions while reading my text messages my phone will call the contact who's messaginges I was reading. This seems to happen mostly when I try to put my phone in my pocket after reading a text.
I am curious as to what could be causing this and if it can be turned off. I suspect it's some sort of gesture or accessibility feature I am accidentally activating, but it's getting quite annoying so whatever it is I want to turn it off. Any help identifying the source is appriciated.
Related
Has anyone had problems with their phone freezing/crashing randomly? Basically my phone would freeze or crash (a force close) when I sleep it too quickly.
Sometimes it's not even sleeping it, it's un-sleeping too. Or even navigating between applications.
When this happens I go in to my messages to type a text and all contacts' names disappear and only numbers show up. If I attempt to click on a text the text will not show up and the screen is just black. It will either take more than 3 minutes for the text to load, or it will not load at all. So I have to shut it down in order for it to work properly again.
My phone has not been rooted, I have not downloaded very many applications, maybe just 5. I haven't even used it to browse because I'm afraid I would have to turn it off and just reboot the whole thing. Does anyone have an idea what is wrong?
You better go get a new one.
use a task killer, maybe it would help you, It worked for me
I am on totally stock JB. Haptic feedback is all but gone on my device. When restarting the phone it will not save last volume/vibrate settings. Always defaults to ring only. Tried numerous volume locker apps with no luck. On reboot my folders are all black and blank for about 30 seconds. On Google now I can’t remove sport team cards. After selecting undesired card and selecting to remove it, it will disappear only to pop back up on restart. My last and most problematic issue is my texting issues(have had issue before JB update). My texts come out of order or are hugely slow/delayed. Sometimes I won't get texts until I text the person and then a bunch of old texts will come through (with hours late time stamps). I also tend to get the same text numerous times. Is this a phone issue, sprint network issue, sense or android issue? I'm guessing it's a sprint network issue. Any tips or tricks on how to fix any of these issues would be GREATLY appreciated. Thanks in advance.
connartist said:
I am on totally stock JB. Haptic feedback is all but gone on my device. When restarting the phone it will not save last volume/vibrate settings. Always defaults to ring only. Tried numerous volume locker apps with no luck. On reboot my folders are all black and blank for about 30 seconds. On Google now I can’t remove sport team cards. After selecting undesired card and selecting to remove it, it will disappear only to pop back up on restart. My last and most problematic issue is my texting issues(have had issue before JB update). My texts come out of order or are hugely slow/delayed. Sometimes I won't get texts until I text the person and then a bunch of old texts will come through (with hours late time stamps). I also tend to get the same text numerous times. Is this a phone issue, sprint network issue, sense or android issue? I'm guessing it's a sprint network issue. Any tips or tricks on how to fix any of these issues would be GREATLY appreciated. Thanks in advance.
Click to expand...
Click to collapse
haptic feedback low is by design. no idea about the vol/vib settings. folders could just be loading slower than on ICS. no idea about GNow. text issue are sprint. possible fix for text: from dialer...*#*#2432546#*#* hope this helps
Hard reset could fix it. But might be your last resort.
Sent from my EVO using xda app-developers app
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
bvz2000 said:
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
Click to expand...
Click to collapse
So several days have passed, and it appears to still be working. I suspect the sd card was the culprit. No idea why. But I am a happy camper again.
Straight to the problem: sometimes (and in a very unpredictable manner), when i have an incoming call, plenty of problems show their ugly face. First of all, i sometimes can't accept, or decline an incoming call, because the screen isn't responding to input. Sometimes i can go around this by pressing the on/off button twice, and that would enable the screen. But, sometimes even that doesn't work. The phone just keeps ringing until the caller eventually gives up. When that happens, the phone continues to function normally.
Another problem is constant vibrations i noticed in several occasions. Instead of vibrating in "pulses" or "waves", the phone just keeps vibrating constantly, which can be very annoying in combination with the problem mentioned in the first paragraph.
At first i though it's a bug in my ROM (CM9 port for legend), but have heard people experiencing the problem on other stock devices (Galaxy SII on stock ICS, for example). So it is not that rare, but to this day i haven't been able to find a solution.
Did anyone manage to solve this problem, or find any information as to how this can be avoided?
stane37 said:
Straight to the problem: sometimes (and in a very unpredictable manner), when i have an incoming call, plenty of problems show their ugly face. First of all, i sometimes can't accept, or decline an incoming call, because the screen isn't responding to input. Sometimes i can go around this by pressing the on/off button twice, and that would enable the screen. But, sometimes even that doesn't work. The phone just keeps ringing until the caller eventually gives up. When that happens, the phone continues to function normally.
Another problem is constant vibrations i noticed in several occasions. Instead of vibrating in "pulses" or "waves", the phone just keeps vibrating constantly, which can be very annoying in combination with the problem mentioned in the first paragraph.
At first i though it's a bug in my ROM (CM9 port for legend), but have heard people experiencing the problem on other stock devices (Galaxy SII on stock ICS, for example). So it is not that rare, but to this day i haven't been able to find a solution.
Did anyone manage to solve this problem, or find any information as to how this can be avoided?
Click to expand...
Click to collapse
I have the same problem with my phone. Any solution for this problem thx
Reflash, reflash, and if it happens again - reflash. The screen lock/unlock workaround was working about 90% of the time. I gave the phone to my father (clean new flash) and he didn't experience any issues with the rom so far.
Hi all, first of all... I am posting this here because I've discovered this "feature" via my S10, but it probably isn't necessarily a S10 feature. It just never happened with my S7 and my work iPhone doesn't replicate it either.
Right, so if you open a private message/conversation on Instagram and with your screen on, flip the phone with the screen facing down, it will start recording audio (you will notice a little vibration if you have vibrations activated).
The behaviour gets even weirder if you keep your phone facing down long enough before you turn it again... as the screen stays completely switched off but the app still records audio. It takes a few tries to turn the screen back on. However, if you turn the phone again shortly after the vibration, it will flash back on again.
Anybody noticed this before? Is quite unusual and I cannot really tell why this is even a feature... other than secretly recording a conversation?
Huh, just tried it and you are totally right. I'm guessing it's a bug. I never send direct messages on instagram but that definitely seems like it could be a big problem. I tried a quick google search and couldn't find anything about it either.
It's so you can put your phone up to your face (like if you had a phone call) it will record an audio message for you automatically. It's doing what it is supposed to but it does make sense to be a little bit worried about this. Instagram should implement some way to disable this feature.
Its like the same on whatsapp when you listening to an voice message and And tilt your phone in your hand as if you were on the phone it will be black too thats a stupid function in the s10