Quick capture issue after phone drop - Moto X Q&A

Hi!
After moto x dropped to the ground, and now has some issue with Quick capture in stock camera, it may triggered randomly, also if phone just stay on table, or it will not triggered when you shake phone constantly.
Alternate method, like tasker worked, but stock camera trigger not working correctly.
How can i test sensor or fix this issue? I do not want use tasker for trigger stock camera.

I'd start looking at the accelerometer and gyroscope. Not sure how you can test them though.

Try to testing accelerometer in some app, none ghost activity, if stay on table. Also if install and configure tasker for shaking action, they work fine.

any idea?

If i start google camera in photosphere mode focus point non-stop spinning, also this issue present in pano mode, quick capture gestures also not working, or have phantom activation.
All this issue after phone fall to the ground.
Is this accelerometer? How can i check and fix this?

Accelerometer is working fine, gyroscope is defected, i have many discussion about moto x gyro, but hasn't find answer, how to fix it.
When running google camera photosphere, it's always rotate, without stoping, also in pano mode. Any gyroscope testing apps crash if start in portrait mode, or has fast rotation in all direction in album mode.
How can i repair moto x gyroscope?

Related

Screen rotation

I'm experiencing a problem with the automatic screen rotation sometimes. Basically when rotating the phone from vertical to horizontal the screen doesn't follow the movement. The only way to solve this is to put the phone vertical again, wait few seconds and then rotate it. I've already tried the usual movements to try to help the accelerometers to capture the movement but nothing, even turning the phone vertical quickly doesn't work, it has to stay vertical for a few seconds.
Also it doesn't happen all the time, but only sometimes (I've noted this while watching videos on YouTube)
Anyone experiencing this? I'm on stock rom and i really hope it's software and not hardware related.
I think this might have something to do with moto action. Some of the actions piggy ride with the accelerometer so it might thinks you're about to do moto actions but fails to fulfill the conditions. Hence, it leaves you without any response/feedback.

Phone won't auto-rotate (doesn't seem like any G sensors are working at all)

So I flashed the latest global rom (stable) after playing around with the android 10 beta 3 for a few days, and now none of the motion sensors are working at all.
My bootloader is still un-locked, I've made sure to move every setting related to auto-rotate and nothing seems to work. (the phone won't even light up the finger print sensor when I pick the phone up, but it does light up after I touch the sensor)
I also tried the "CIT" menu, by spaming on the Kernel version on the settings, and the X, Y, Z values don't even show up for the magnetic sensor, gyroscope or the accelerometer.
Anyone have any idea how to fix this? Any feedback would be welcome, thanks in advance!

Proximity Sensor Issue

I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
jdock said:
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
Click to expand...
Click to collapse
Thanks mate, appreciate your feedback. Proximity sensor works fine on my phone during calls. Can't think of any reason why Samsung would intend it this way...
Proximity sensor issue here as well
I have the same problem. I put phone into test mode and it was bad compared to my wife's s9 search proximity sensor s20fe on YouTube and see others with issue
There is no fix. This is apparently the way AOD works now. I can't remember if it started with the S10s or S20s.
uggies said:
I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
Click to expand...
Click to collapse
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
No problems with Verizon S20 FE 5G UW
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
I just purchased the Samsung S20 FE 5G UW (how about we shorten this to FE UW?) with all updates AND a glass screen protector and have no touch/proximity issues.
FYI I bought it at the Costco kiosk for a few dollars less per month, no activation charges and a 90 day return policy.
the Galaxy S20 FE (5G) has no physiscal proximity sensor.
Insted it uses a combination of the front camera, touch screen and gyroscope.
I have tested the proximity issues, luckily for me there were ok...turn green. The only thing that drive me crazy is the touch screen issues which never been fixed even after updates. Oh well at least its better than before.
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
Mate great information here, really appreciate this.
Tested the Proximity sensor using *#0*#, I agree with your analysis. The proximity must be using electric reaction to detect if my ears are touching it or not. Covering it with a book does not trigger a proximity sensor... This explain why my screen keeps waking up in the pocket.
As much as this is annoying, there appears to be no way out Just have to let the phone face outside rather than my legs.
I also have the same issue, while on a phone call, the phone's screen goes on and off constantly and I can see the notification bar moving. Very annoying.
This is a terrible design by Samsung. The punch hole usually goes in the "Empty" part of the ear, so the screen stays mostly on.
I might just return the phone because of this issue, I don't see it getting fixed by a software update.
I have the exact opposite issue with the proximity sensor on my Samsung S20 plus running Android 10 - i.e. it works well by turning the screen off when my ear/cheek/face is very close to the proximity sensor during phone calls; whereas, when the phone's screen is locked and turned off, the proximity sensor is turned off as well. Control by hardware? Software/firmware? Don't know?! To turn the screen on without using the Power hardware button, I had to enable the "Double Tap" feature in Settings.
On earlier/other Android mobile devices - Samsung included - the proximity sensor is always on - whether the screen is on, off, or currently locked. When it's always on, you can be innovative and build a widget, for instance, to turn the screen on by "waving" your hand above the proximity sensor to interrupt the laser. I suspect new(er) Samsung mobile devices like S20 and Note20 variants might be using a "virtual" proximity sensor setup/combo for controlling the device's screen - and that really sucks!
To test if the proximity sensor is always activated on Samsung S20 and Note20 variants, I type *#77692# - which displayed a hardware screen to test proximity and light sensors. Note: if you type *#0*#, the proximity and light sensor options are absent from the hardware test screen.
Has anyone found any method - via codes even - to permanently turn on the proximity sensor, even when the screen is locked and turned off?
I searched through AOSP framework vanilla codes and couldn't see anything out of the ordinary regarding control of the proximity sensor. Samsung might be doing something dubious with their firmwares/hardwares though - well, at least, the S20 and Note20 variants are having issues with the proximity sensor setup.
P.S: Not sure if you guys are aware, but Samsung mobile devices with odd designation tends to be more problematic than their even-designated counterparts, like screen's burn-ins/shadows on Samsung S3 devices, light sensor fluctuation (which affects screen brightness control) on Samsung S5s, and now proximity problems with the S20s and Note20. Samsung S20 variants are in fact "S11" variants renamed. So the trend continues with Samsung always stuffing up their odd-designated device releases.

Pixel 4: deactivate the proximity sensor

Hello!
Is it possible to deactivate the proximity sensor? I know that ALL sensors can be deactivated in the quick setting panel, but I want just the proximity sensor to be deactivated, so the "always-on-screen", showing a clock and incoming messages, does also stay on when I put the phone into a transparent rain cover on my bike. Right now I need to push the on-button to be able to see the clock or other information, and that is something I'd rather avoid while riding.
Does anyone know a solution for this? An app or a patch maybe?
Nearly forgot to mention: the phone is running on LOS 18.1.
If you have root it's posible to do everything, though I am not sure how to help you...
What I know is that you will propably have to edit some tables on the system, maybe the system table. There is an app from the playstore that you can downlaod that allows you to modify some system tables(like global tables as well). Maybe if you play with that you may be able to deactivate the proximity sensor. The app is called SetEdit.
Hope this helps you, and in case it did, and you downlaod the app, could you please tell me if it is posible to modify the android properties table?
thx!
Thanks for your reply!
I should have been more precise when expressing my wish: I meant to switch the proximity sensor off while system is running and switch it back on later. The app that you pointed me to, reads as if the sensor will be deactivated at boot time and stay off until I reverse the change to the table and reboot again.
Basically, what I need, is an app that can switch the sensor off and on again without the need for rebooting in between, or an option in the system settings, that can be set within a profile: switching to profile A, which has proximity sensor on, switching to profile B, which has the sensor turned off, while all other sensors stay unchanged, would be a very good solution.
I don't know it that would be possible at all. On the other hand, there are "tasker apps", which can do "X if Y happens" or something like that. If such an app could "turn proxi sensor off when profile B is activated", that would also be a solution to my problem.
Do you know of any such app?
Oh. Yeah, that seems to be a very specific usage, and I don't believe you will find an app to disable the proximity sensor. Maybe you can develop that, it shouldn't be very hard, especially if you already have some knowledge of android development.
Good luck!
To my opinion the screen's on/off status should not always be determined by the proximity sensor, but by surrounding brightness instead, because the way it is now, you can not put the phone into a transparent cover, without the screen being switched off.
I agree that only a very few people will use transparent covers, and that the proximity sensor does have its advantages when holding the phone to your ear, but I also can imagine more situations where the screen wil be turned off by accident, when it rather should be kept on.
So, an option like
Code:
Use proximity sensor to turn off screen [ ]
Use light sensor to turn off screen [ ]
inside a system profile would be a great thing!

Proximity sensor problem

hi guys, i noticed that my phone's "lift to check" and "double tap to wake" aren't working sometimes, and the screen went black when i make a call. therefor i downloaded sensor test app and figure out those are caused by proximity sensor stopped working occasionally, especially when i take it out from my pocket, i had to restart my phone to make it works again.
i searched over the internet and tried all the ways but still no luck. Action taken included boot to safe mode, clear the cache of phone app/ google framework/ google services, android ambient and etc... and i also reset the app preference, download sensor calibration app, factory reset, yet, the problem still appear. i have used my phone for more than a year, and this issue was just suddenly poped out recently.
appreciated if anyone here could provide a solution. Thanks
rom: stock A13
root: no
bootloader: locked

Categories

Resources