Related
Hi, I have a very weird problem with my N7100. When I put my finger or anything in front of my front camera, the toggle bar will disappear and the screen will be still and no response. This is really bothering especially when I am playing games. Cause I swipe my finger in front of my front camera unpurposely and the game will be interrupted. It looks like the front camera is active to detect anything in front it, and if there is any thing blocking front camera, the screen will be frozen up!
This problem start with my official system (Samsung Touchwiz) comes with N7100. So I rooted my phone and put alliencerom there, it comes back again....If you restart the system, it goes away for a while and will come back sometime. Really bothering, I have found out what is the trigger, I believe there is a trigger though.
So I don't know any N7100 user encountered the same problem? And any idea about getting rid of it?
Thanks so much!
Are Smart Stay/Smart Rotate and all the motion stuff turned off? If not try turning them off.
tuxonhtc said:
Are Smart Stay/Smart Rotate and all the motion stuff turned off? If not try turning them off.
Click to expand...
Click to collapse
I checked all those and they are off, I actually never turned them on. Today I found that after I use groove ip make a phone call. The problem will come up. I don't know exactly how.....
I test it a little and I found it is the function of Groove IP which freeze the screen when you are making a call. But somehow after you done with your call, the front camera just keeps doing so. I think there is something with screen rotation during the call.
Now I think problem solved by checking off "auto rotate" in Groove ip setting.
Thanks, XDAer.
Why does doubletap2wake randomly stop working? It has nothing to do with phone being idle, still doesn't work after movement, have to unlock to get it back to work again.
Is this because of deep sleep or power saving mode enabled in sense?
Is my M8 defective - is this a hardware issue?
Running ARHD and ElementalX 0.18. Had the same issue on stock kernel - can't remember if I had it on stock ROM but someone else told me he had the issue too on all ROMs.
This is a stupid question, but I have to ask: Are you sure that you are holding the phone vertically so that it is in portrait mode?
BrandonPrice31 said:
Why does doubletap2wake randomly stop working? It has nothing to do with phone being idle, still doesn't work after movement, have to unlock to get it back to work again.
Is this because of deep sleep or power saving mode enabled in sense?
Is my M8 defective - is this a hardware issue?
Running ARHD and ElementalX 0.18. Had the same issue on stock kernel - can't remember if I had it on stock ROM but someone else told me he had the issue too on all ROMs.
Click to expand...
Click to collapse
sometimes i notice that the double tap to wake won't work because i have some stuff on my screen or something that registers as a screen press. i'll have to wipe my screen down.
It's all in the finger action. One to wake the sensor at any corner of the phone, then 2 deliberate taps, not 2 quick taps, on the bottom half of the screen.
ashyx said:
It's all in the finger action. One to wake the sensor at any corner of the phone, then 2 deliberate taps, not 2 quick taps, on the bottom half of the screen.
Click to expand...
Click to collapse
I have this exact problem. At least 1-2 times a day, motion gestures will stop working and I have to use the power button to turn the screen on. I have tried everything when this happens (making certain phone is in portrait mode and held straight up, shaking the phone, tapping the corner of the phone before doing the gesture, etc.). I am well aware that the phone has to be moved before doing the gestures. This is my second HTC One M8 from T-Mobile. The first had scratches all over the back out of the box so I exchanged it. I don't recall this ever happening with the first phone. Maybe some app is messing things up? Could this be a hardware issue? I'm hoping it's a software issue.
mhajii210
Make sure you don't accidentally swipe up while the screen is off as this seems to lock the gestures out.
ashyx said:
Make sure you don't accidentally swipe up while the screen is off as this seems to lock the gestures out.
Click to expand...
Click to collapse
Really? I haven't heard that being mentioned before. It's possible I accidentally swipe up just a bit when I'm trying to DT2W. Has anyone else mentioned about accidentally swiping up while the screen is off and it locking the gestures out here on XDA?
mhajii210
I've noticed this as well, but only with the double tap(swipe up or to the side always works). I would say mine only does it about 2% of the time though so I haven't been too concerned about it.
Hi guys. I just wanted to report that I updated to the latest stock 4.4.4 OTA 4 days ago. I no longer have any problems with the gestures randomly not working (including DT2W of course). I'm a happy camper =D
mhajii210
Also make sure when you pick it up the meat of your thumb or other part of your hand is not touching the screen. I've caught myself doing that a few times.
Your title pretty much sounds like it is referring to my brother.
I am having this problem too with or without the dot view cover
Sometimes it does't wake up... it's like its in deep sleep like the OP is saying
Any help
two large speakers and some gabba techno should do it
Lol think the phone needs to be at a slight angle when using double tap. i have noticed before when my phone is flat on my desk at work and the screen has been off for a while, its seems to be in deep sleep mode, however when i pick it up, double tap works
It happens to me maybe a couple times a week. I reboot, fixed.
Poop happens is my explanation.
I wouldn't be very concerned. Things get screwy in the system every now and then, that's all.
Whenever it does that, I just rub my finger across the proximity sensor back and forth a few times and then try the double tap again and that always works.
Has anyone else noticed that when in a dark area, pressing the main button will turn on the screen but it will then automatically and immidiately turn off?
Several times I've gotten into a battle with the phone only to lose, turning it on and it turns off, then turning it on again and so on...
To compound the issue, in these situations it seems that double tap is signifigantly less responsive to activate the screen as well.
I'm pretty sure this phone is using some sort of facial recognition, it has smart stay doesnt it? I think it has gravity/accelerometer to turn on the screen when you pull it out of your pocket. In the back of my mind I'm thinking that since it cant see me it is shutting off but this doesnt seem consistent...
I'm running stock rom, rooted with twrp. Any ideas?
I have not experienced that. Did your G3 do that out of the box?
Sent from my LG-D851 using Tapatalk
Never heard of it. Screen is set to auto off in 30 seconds. Change it to 2 min and you should be good. If u running without a case then maybe the hand is touching the edges of screen this will also shut screen off in double tap.
BAD ASS G3
sublimaze said:
I have not experienced that. Did your G3 do that out of the box?
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
I didn't notice it until the last week or so. but I kind of feel like that was because I hadn't used the phone that much up until then. I didn't make any major changes to the phone immediately before I started noticing it either, I had already had it rooted for about a week. I feel like the stock rom does have some glitches to it.
The G3 does have a "smart screen" feature that detects your face (Settings > Display). Disable that and see if it helps.
I've not run into this in the dark but have when I try and use my arm band holder when running. The holder covers the ambient light sensor so the phone thinks it was accidentally turned on like in a pocket and shuts right off. Super annoying.
Noticed similar behavior when the phone is in my bike mount at night. Basically it's acting like the proximity sensor is covered. In my bike mount's case, it is covered by a clear screen cover, but normally that doesn't trigger the proximity sensor. But when it's very dark out (not under a street light etc.), it seems to think it's blocked and turns itself off. Annoying.
randyspants said:
I've not run into this in the dark but have when I try and use my arm band holder when running. The holder covers the ambient light sensor so the phone thinks it was accidentally turned on like in a pocket and shuts right off. Super annoying.
Click to expand...
Click to collapse
speedrabbit said:
Noticed similar behavior when the phone is in my bike mount at night. Basically it's acting like the proximity sensor is covered. In my bike mount's case, it is covered by a clear screen cover, but normally that doesn't trigger the proximity sensor. But when it's very dark out (not under a street light etc.), it seems to think it's blocked and turns itself off. Annoying.
Click to expand...
Click to collapse
Have you tried disabling smart stay as sublimaze recommended?
Apache0c said:
Have you tried disabling smart stay as sublimaze recommended?
Click to expand...
Click to collapse
Tried but remains the same... This was the only thread I found concerning this.
Ive had this issue too investigating now
Had that issue when I was using the lock screen face unlock. In the dark it didn't see my face and then it shut off. Setting is in lock screen section
Sent from my G3
gabrielshaste said:
Had that issue when I was using the lock screen face unlock. In the dark it didn't see my face and then it shut off. Setting is in lock screen section
Sent from my G3
Click to expand...
Click to collapse
Lol.
I have the same issue EVERY night. Why is that? It's very annoying
Same issue here
it seemed to resolve itself when I factory reset my phone
but after I got my apps reinstalled from my google backup it started again
so it seems like it's a software issue - not sure to which app it is related to
let me know if you find a fix - this is quite annoying
Me too. I've been facing this issue at night, when it's very dark.
Me and my buddy were in the car during a roadtrip and it was very dark, I mean like: No lights outside, no lights inside the car, the double tap feature didn't even work to begin with and whenever I tried to use the "Power Button" It would come on and then suddenly 'boom' Turn off, now this would happen a few times until it stays on. Weird...
I just experienced this myself, first time I've seen it happen in the 30 + G5's that I've sold. If it's in the dark it just doesn't turn on at all. I hope LG is fixing this. I'm about to Factory Reset it right now and hope for the best! Someone else mentioned that this is the only forum that is disccusing this issue. It must be a very few that are effected. I'm testing another one as we speak.
Has this issue been resolved? My friend's G3 also has this issue. Day time no problem. When it is dark the screen wont' stay on.
Same problem, no fix yet
Same problem here - Pointing it at any light and pressing the power button will turn it on. (As will plugging it into power). Tried tinkering with all sorts of settings (face recognition/auto dimming feature/etc) nothing worked. Tried factory reset, that didn't work either.
My issue started after i had my screen replaced (by a shady shop) who probably didn't do a good job of packing it back together....I'm going to see if I can have someone open it up and clean it out a bit..
I have the same issue on my G3. Even if you're under the covers in bed, the thing doesn't turn on until it gets light. It basically doesn't turn on in the dark through double tap and actually not even with the power button. It could become a safety hazard for someone in an emergency situation.
Nahdont said:
I have the same issue on my G3. Even if you're under the covers in bed, the thing doesn't turn on until it gets light. It basically doesn't turn on in the dark through double tap and actually not even with the power button. It could become a safety hazard for someone in an emergency situation.
Click to expand...
Click to collapse
I have also same problem. No solution yet.
Has anyone else had a screen rotation issue on their Note 4?
In almost all apps, rotating from portrait to landscape or landscape to portrait has a very long delay. Usually at least 10 seconds, and sometimes not at all unless I tap the phone on a hard surface, and then it rotates.
That might suggest a sensor problem, except for 2 things that do work:
1) In camera mode, the buttons rotate instantly when I rotate the phone
2) In GPS status, which indicates phone orientation, it registers the screen rotation as roll in the pitch/roll display, although the GPS status screen does not rotate correctly either.
These seem to confirm that the actual sensor is working ok.
I've tried safe mode, clearing cache, closing all open apps. Nothing changes in the behavior. I also tried turning off SmartStay, and changing display mode.
Some hits I found suggested turning off "smart screen rotation" on the S5, but that setting doesn't seem to exist on the Note 4.
Has anyone had this problem and found a solution?
Glen
and sometimes not at all unless I tap the phone on a hard surface, and then it rotates.
Click to expand...
Click to collapse
This is like a dead giveaway for a hardware problem.
Wow, 10 seconds is a looooonnnggg time for a screen rotation. I've never experienced this on my Note 4, so the only thing I can think of is talking to your carrier or Samsung themselves to ask about it. Sounds like a hardware failure to me.
Yeah, that does make it seem like a hardware problem. But like I said, the camera buttons rotate instantly every single time, with zero lag. That would seem to say the hardware is working, unless the camera uses a different sensor for rotation than the rest of the UI.
Also, my wife has the same issue with her Note 4. We got them at the same time, so maybe it's a problem with that batch.
Since we both have it, it seemed like it could be caused by some app we both have, but I thought booting in Safe Mode would eliminate that, as only stock apps run in Safe Mode.
I guess I could wipe the device completely and see if it resolves. If not, I'll take it in as a hardware problem.
After a full wipe and cache clear, it still has the same problem. I called Verizon, and they are shipping out a replacement phone.
Glen
After a few days of using this device i noticed that my screen turns on during phone calls. After doing some research it came out that the proximity sensor is not working properly when phone is being tilted to horizontal position with screen upwards. It just immediately shows that it is far away from any object even that it isn't. The fun fact is that when covering the sensor with my hand while phone is laying on his back doesnt switch it and rotating the phone to vertical position also does not make any effect like the sensor would be locked. Covering it again in that position makes it work.
Can anybody help me with this issue? It's very annoying for me and makes my phone unusable for making calls.
Edit: similar problem here https://forum.xda-developers.com/android/help/huawei-nova-5t-proximity-sensor-problem-t4136595
Same problem here...
here also
I am so lost. What do I do with the phone? What? When does it happen? (Also subscribing.)
Same here, and i notice i have also problems with whastapp and telegram audio notes.
Sometimes screen goes blank randomly and with no reason when i'm listening a audio note.
Hi. Its a well known problem. Its becouse the device has a ultrasonic sensor not like any other. Sensor like you already find out works only in vertical position of the phone. Its well described in the net how it works. Just search. In 4PDA in the section for our phone. But you need to know russian.
I found that thread and it seems that not everyone notices that... Not spending more time on reading this I found a workaround on my own: an app that keeps the screen disabled after first switching proximity sensor. Then you just need to use the power button if you want to use the phone.
Same problem here, it's very frustrating. I can turn the screen back off during a call once I see it's turned on by itself, but it keeps turning back on. I'm sick of muting calls and hanging up on people by pressing buttons when I'm on the phone.
What is the app that you are using @Spectre45?
Spectre45 said:
I found a workaround on my own: an app that keeps the screen disabled after first switching proximity sensor. Then you just need to use the power button if you want to use the phone.
Click to expand...
Click to collapse
Can you please tell us what app you are using?
kage00 said:
Can you please tell us what app you are using?
Click to expand...
Click to collapse
try proximity screen off or call proximity screen fix
LightSmok said:
try proximity screen off or call proximity screen fix
Click to expand...
Click to collapse
Thanks
Listen. There is no proximity sensor at all. The upper mic, speaker and the sensor for orientation are doing the job. When you pick a call the speaker is sending ultrasonic signal and if it locate your ear it dims the screen. Once it works it is working in all positions. But if you move your phone away only in horisontal position it will nit work untill you mive it in vertical again.
Edit: Experienced this issue too. Annoying.
Does using Xiaomi.EU fix this problem? This issue really gets on my nerves. I started daily driving this device (finally I was able to unlock) and I just cannot use it for calls, which is kinda ridiculous from a phone.
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
I was using the phone with cover provided by MI, upon removing that back cover I encounter no such issues.
h8Aramex said:
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
Click to expand...
Click to collapse
I didn't have any proximity issues on stock with google dialer. It's not google dialer, it's how you position your head against the earpiece. Sensor is ultrasonic, so it probably doesn't detect properly depending on the position people hold their phones in...
I have the same problem with my work phone - redmi note 9. Tried the app "proximity screen off" but MIUI keeps killing it no matter what i do to keep it alive. It seems that sensor is located on front top right side of the phone so sometimes it gets behind your ear if you are right handed (mine are pretty small) and then the muting starts. When using the phone with left hand - no problems at all.
I would love to have a working app to keep screen off during call.
h8Aramex said:
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
Click to expand...
Click to collapse
I also flashed EU rom and the problem persistes.