I've put up with the proximity sensor malfunctioning once i take or make a call, the touch screen not working [restarting it solves the problem, after i had the screen replaced due to complete failure to function, which seems to be evident of a software issue] and the UI keeps crashing. I know this isn't a very smart question, but would rooting to the right ROM solve all these bugs? These seem to be a software issue, but again; I'm nowhere close to an expert on this. Also, what I mean by the proximity sensor malfunctioning is that when the phone is in a call, the screen doesn't turn on even if it isn't close to my ear or anything else.
Related
So I've have been having this issue on and off with my phone I have the Rhod210 US T-mobile Touch Pro2 with the most recent Energy ROM and for a couple months now the screen will randomly change orientation and it will do it constantly even if the phone is closed and on a level area. I also have an issue where this will happen after the screen has been turned off, after a minute with the screen off the back light will come on and the orientation will keep flipping from Horizontal to Landscape over and over again.
I have an overclock set on this phone but I didn't have this issue until weeks after I had my overclock set
Anyone else having this problem? Is my phone broken?
Is there a fix for this that I don't know about?
Thanks in advance guys
Honestly, it sounds like a faulty G-Sensor. Flash a stock ROM and see if the problem persists.
I calibrate the G sensor and it still doesn't make a difference. It seems to just happen randomly and for a few minutes or sometimes a whole night.
You should flash a stock ROM to see whether this is a hardware issue or not. If it happens on a stock ROM with nothing installed, then it is hardware. If it does not happen, then you've got a problem with the software on whichever ROM you're currently using.
I know the proximity sensor is not functional with the Rhodium400. My wife and I are both running the newest version FRX 7.1 on the .27 kernel.
She had issues with Windows Mobile getting a data connection, and it would carry over to Android. So I dd a hard reset on Windows Mobile and started her Android from scratch (as it was having other slowness and issues also). Ever since then she tells me (and I have heard this in call) that every time she puts her cheek or face to the phone it will sound as if the call dropped but it doesn't drop really. She can't hear me and I can't hear her, but as soon as she takes her head away she and I can both hear again. This doesn't happen all the time, and is likely only happening when XDAndroid has not been rebooted in a few days.
I have not been able to confirm it by sitting right beside her and calling and confirming the problem, but I plan to do so tonight. At first I thought she was just muting me because she was ticked at me...don't ask , but she isn't smart enough to come up with something like this, because technically it sounds like the proximity sensor is mucking up the phone call which I thought was not possible from everything I have read. I even had her turn the power button off at the top to turn the screen off, to make sure she wasn't bumping any buttons. The way it looks, it almost sounds as if the phone is inadvertently trying to place another phone call and putting the first phone call on hold.
Has anyone else had this issue? Doe anyone think this is likely a proximity sensor issue, or have any advice for when I get home tonight and start playing with the phone?
Supposedly also this issue was going on with her in the car and the phone plugged into a car charger. She called me back with it not on the charger and it is not messing up anymore. I don't know if it is coincidence or not, since it wasn't always doing it to begin with.
Never heard of this, almost sounds like a hardware failure.
Run WinMo for a few days, see if you can recreate the problem there. If so, there's something going haywire with the physical hardware.
I get a situation kind of like this in Android, but not WinMo. Basically if I recieve a call it's about a 50/50 chance that this happens. I can't hear them and they can't hear me. There is no sound at all, like the speaker and mic don't even turn on. However, mine doesn't seem to have anything to do with the proximity sensor as it does it as soon as I hit the answer button and moving the phone away doesn't fix it. Also, it's only when recieving calls, outgoing calls work all the time.
I've had similar problems, but quite a bit in the past, making me think mine was software or settings. So don't discouraged!
My thinking is, since auto-mute to rear speaker/mic system is a 'feature', that maybe that system gets triggered. Check those settings, and that level/bubble calibration stuff.
Hi
I'm searching for anyone else having the same problem as me and other people that i've seen in Lenovo Forums
I'm having different problems, but the most important for me is the proximity sensor, because once I answered a phone call, it makes impossible to hang up because the display turns black and it doesn´t "wakes" until the phone call has ended. The same problem with audios in whatsapp.
Another problem is that Moto Actions like turn on the flashlight with a shake, and open the camera with a twist doesn´t work anymore. Plus, the vibrator started to fail, having an unusual behavior until it just stopped.
And the device is not recognized correctly in any computer I've tried, it just appears as "unknown device", and the device doesn't show the options that use to appear when connected to a computer, it just says "charging".
I want to think that all of them are software problems, and not hardware problems, because they all started after the june 2019 update, and, as I said, there are other people having the same problems, and I think it would be a big coincidence if all of us have the same problems with our hardware.
If any of you have had the same problems, could you tell me if you could find a way to fix it? Or, anyone has any idea how could I solve, at least the proximity sensor problem, it would be better if the device don't turn off the screen anymore during phone calls.
I've tried reinstalling the drivers in 3 different pc's, and any of them worked, but when I tried with another device (Moto z2 force) they all worked. I've done factory reset three times, and one hard reset, with no changes. Could someone help me?
Thanks for reading.
Well, sound like... simply failing phone ? RMA ?
emcom said:
Well, sound like... simply failing phone ? RMA ?
Click to expand...
Click to collapse
Do you think that? I've had this phone for a year and a half, and I've never had any issue, until the last update on june 2019.
Maybe is a coincidence and my phone started to fail just after the update, but to be sure, I want to know if there's someone else having the same issue, and maybe someone could fix it.
I've had these problems a few months ago too, but back then I was thinking it was related to a hardware problem cause I had to send my phone to fix the screen (broken glass) and after that I noticed that the moto actions wasn't working properly, as the flash light from the frontal camera and the most annoying of the problems, the proximity sensor that would stop working when I got a call or audios in whatsapp. All of these was solved a couple weeks ago tho, after I had to fix my screen again (yes, 2 times in 3 months, congrats), just days before the android pie was released, so I can't say exactly what fixed it
I have a weird issue with my A2 Lite.
I tried couple of ROMs so far and it's all the same.
When I receive a call and answer it, I bring the phone to my ear and I can see that display goes off - that's good. But, despite keeping the phone close to my ear, the flash light turns on, bt or even airplane mode so it disconnects the call, it changes the screen brightness or mutes the mic during the call. It's like touch sensor was alway on with display off, so I can't even see what I'm touching and switching.
I even went back to stock MIUI to be able to run system check with *#*#64...etc. and proximity sensor works fine.
My problem is similiar to this one: https://forum.xda-developers.com/mi-a2-lite/help/lockscreen-notification-sound-proximity-t3867872.
This drives me crazy!!!
Did anyone have this problem or knows some tricks to fix it (beside smashing the sh..t on the wall)?
I experience the same thing sometimes with stock rom
keyone72 said:
I experience the same thing sometimes with stock rom
Click to expand...
Click to collapse
That - I didn't expect...
But it has to do something with the Android or kernel maybe. How does it come, that screen is being turned off but not locked (meaning insensitive for touches)?
Weird...
And I'm almost sure, it wasn't like this before... before I installed one of custom ROMs (Arrow maybe). But since then I even went back to stock Pie, so if any firmware/kernel manipulation caused it, with stock - it should've fixed.
I'm starting to dislike daisies...
Hi guys,
Lately I've noticed that my fingerprint sensor does not work properly anymore.
Not sure if it's a hardware or software issue?
Though, the test HW for Fingerprint Sensor from Smart Doctor app reports Good status during all tests.
The behavior is strange and not consistent, most of the times it will work fine but from time to time I cannot unlock/wake the phone with the fingerprint sensor, it's not like the fingerprint is not recognized, it's more like putting the finger on the sensor and nothing happens (it doesn't vibrate like is reading it or not) . Not sure if is related to the phone being in standby for longer period, or I don't know ...
I'm more inclined to believe it's a software issue, and seems to have occurred lately after last update to Android 10 (v30f-EUR-xx, phone type LM-G710EM).
I've tried may method, deleting the finger prints and add them again , even did a factory reset but the issue seems to come back.
Do you guys have such issue?
Any idea how to diagnose this further?
dinoc said:
Hi guys,
Lately I've noticed that my fingerprint sensor does not work properly anymore.
Not sure if it's a hardware or software issue?
Though, the test HW for Fingerprint Sensor from Smart Doctor app reports Good status during all tests.
The behavior is strange and not consistent, most of the times it will work fine but from time to time I cannot unlock/wake the phone with the fingerprint sensor, it's not like the fingerprint is not recognized, it's more like putting the finger on the sensor and nothing happens (it doesn't vibrate like is reading it or not) . Not sure if is related to the phone being in standby for longer period, or I don't know ...
I'm more inclined to believe it's a software issue, and seems to have occurred lately after last update to Android 10 (v30f-EUR-xx, phone type LM-G710EM).
I've tried may method, deleting the finger prints and add them again , even did a factory reset but the issue seems to come back.
Do you guys have such issue?
Any idea how to diagnose this further?
Click to expand...
Click to collapse
Make sure your battery isn't swollen. A swollen battery will take out the fingerprint sensor first because it's right on top of the connection.
Hmm, interesting, from the outside I can't feel any difference, the back seem flat.
Exactly the same problem here. But if I check the sensor while it is not working I get a "sensor not respondong error".
Did you solve somehow?
Thank you