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
Related
Hi,
Recently I'm having a problem with the LED flash, whenever I try to use it either to take a photo or on the flashlight app, it makes a short flicker and then shuts down. In case I want to take a picture at night it is particularly annoying because the flash terminates before the picture is actually taken so everything comes out darkened.
I'm wondering if anyone else ever experienced this problem as well. I'm not sure this is a hardware problem like a busted flash, or maybe there some software bug making this happen.
Uri
uri.patish said:
Hi,
Recently I'm having a problem with the LED flash, whenever I try to use it either to take a photo or on the flashlight app, it makes a short flicker and then shuts down. In case I want to take a picture at night it is particularly annoying because the flash terminates before the picture is actually taken so everything comes out darkened.
I'm wondering if anyone else ever experienced this problem as well. I'm not sure this is a hardware problem like a busted flash, or maybe there some software bug making this happen.
Uri
Click to expand...
Click to collapse
I never had this issue.
Have you already tried to install the S2 Camera Update from Samsung Apps?
It tests if you need the firmware update for the S2 camera and installs it if needed.
Additionally you can test the flash "hardware" by using any of the flashlight apps from the Market. Just to check, if the LED works fine.
Good luck !
Thanks for the reply!
I will check Samsung camera app, though I think my firmware is up to date.
As for the torch app, I have tried using it and it shows the same kind of behavior.
The only thing that makes me think this is a software issue is that the ffash does turn on for fraction of a second.
Uri
i know, eh?
I am having the exact same problem.
the flash goes on for the metering, then flashes a few times quickly but never in sync with the shutter, it seems..
sometimes torch applications work but never for very long (if i turn it off, sometimes i can't turn it back on, i mean... rarely problems with it not staying on)
i've had a few pictures showing up with vertical bars (almost like multiple exposure times) when i've forced the flash on when it wasn't really needed.
Also being driven insane by this problem.
im having the same problem with my s3. Did you fix it?
any solutions?
mine is exactly the same. has anybody found the solution? would be glad to know. thanks
second day and already have many problems:
1. ringtone turned off vibration only. still have ringtone with incoming calls
2. making calls screen turned off once near ear. moving away from ear doesn't turn on the screen. try any button nothing works. have to turn off power to cut
3. smart stay isn't smart. screen still turned black even with bright environment
Am I unluckily with a faulty phone or they are known bugs? thanks
Not to sure mate
I have had NONE! of the problems that you have had, although i have had a few problems e.g. the turn to mute media stopped working and things like that, all i had to do was a restore and it is fine now, i was speaking to the people at the carphone warhouse (phone shop in the uk) they said they have only had 1 return since launch and that was because the screen wasnt big enough and they went for the note, i have also always found that samsung is happy to help you if you have a problem with your phone just give them a ring.
1: you need to explain exactly what you changed.
2: It's supposed to go off near ear because uses proximity sensor to save battery turning screen off.
3: Smartstay just doesn't work as well as it should do.
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.
Wondering if this happens to anyone else. Sometimes when there is an incoming phone call the screen remains turned off and there is no way to see who's calling or to answer the call. The power button does nothing. Basically, all you can do is wait for the call to go to voice mail, then wait another 30-40 seconds after which the phone finally responds to the power button and turns on. This drives me crazy. What good is the damn phone if you can't answer important phone calls? Interestingly, this was my biggest complain about the stupid iPhone 6, where a lot of times I would be getting a call and the screen would be frozen. Are the phones only for web browsing and facebooking now? Making and receiving phone calls is a secondary feature and no one complains if it doesn't work?
Second issue. Every phone I've had going back many years has had a proximity sensor, where during a call the screen goes dark once you hold the phone to your ear and wakes up once you move it. The V10 does NOT do that. The screen never wakes up by itself, I always have to hit the power button. Is this a "feature" or a bug?
First i noticed that whenever i chat with someone over messenger, it starts calling them randomly while i type.
I thought it's about messenger and i cleared the cache and reinstalled it. Problem is still occurring.
Later, i noticed in one game that screen does that touch again - on the very same spot as in messenger - somewhere in the top right corner (where's the call button in messenger).
I turned off the phone, waited 2-3 minutes and then turned it on. Problem is still occurring.
I started service "thing" (found on the internet what to type in the dial to activate it) and tested the touch screen, everything seems to be okay. So from my experience it seems it's not hardware problem. Do you have any suggestion or experience with this kind of problem? I wish i could fix my phone
And one more thing, it happens only when i'm touching the screen too, it wont do that when i leave it alone and just watch the display.