Well, this issue bugged me for months now and it looks like there is a workaround.
Problem:
Proximity sensor not functioning during calls - Screen will go black and won't restore until the call ends and with a few power button clicks.
If you tried - Blowing at the sensor, Fixing apps, Opening the device and cleaning the sensor, Creating a bolder separation between the two receptors of the sensor, sending it for repair, Running ADB shell Auto + Manual Calibration - and it all failed, I hope the next workaround solution will help you.
Unless you have a defective hardware/software, doing a manual calibration of the proximity sensor should solve any problem with it. Follow this tutorial - How to Perform Proximity Sensor Calibration on any Samsung Phone .
For me though, it never worked.
When I did the commands:
Code:
cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal
cat /sys/devices/virtual/sensors/proximity_sensor/state
They both returned a value of '0' (Zero). Which mean I couldn't do any calibration.
I tried so many times but always got '0'.
I saw a few comments from users on threads and tutorials who had this problem and no one seemed to have an answer.
Now, i'm not a debugger savvy but here is what I did which seem to have solved this:
Make sure you run the ADB shell from a pc and not directly on your mobile., You'll want to use copy&paste with your mouse for this.
Run the auto calibration first from the tutorial above.
Now make a call on your phone - this will force the sensor to go into a live mode.
While your phone is calling - run the manual calibration codes.
You should now have different number/s other than 0. Write them down.
You can hang up now
Keep following the tutorial with the number/s you have.
.
I hope this helps. :highfive:
I have a Galaxy S3, i9300 - CM11.
Xolusia said:
Well, this issue bugged me for months now and it looks like there is a workaround.
Problem:
Proximity sensor not functioning during calls - Screen will go black and won't restore until the call ends and with a few power button clicks.
If you tried - Blowing at the sensor, Fixing apps, Opening the device and cleaning the sensor, Creating a bolder separation between the two receptors of the sensor, sending it for repair, Running ADB shell Auto + Manual Calibration - and it all failed, I hope the next workaround solution will help you.
Unless you have a defective hardware/software, doing a manual calibration of the proximity sensor should solve any problem with it. Follow this tutorial - How to Perform Proximity Sensor Calibration on any Samsung Phone .
For me though, it never worked.
When I did the commands:
Code:
cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal
cat /sys/devices/virtual/sensors/proximity_sensor/state
They both returned a value of '0' (Zero). Which mean I couldn't do any calibration.
I tried so many times but always got '0'.
I saw a few comments from users on threads and tutorials who had this problem and no one seemed to have an answer.
Now, i'm not a debugger savvy but here is what I did which seem to have solved this:
Make sure you run the ADB shell from a pc and not directly on your mobile., You'll want to use copy&paste with your mouse for this.
Run the auto calibration first from the tutorial above.
Now make a call on your phone - this will force the sensor to go into a live mode.
While your phone is calling - run the manual calibration codes.
You should now have different number/s other than 0. Write them down.
You can hang up now
Keep following the tutorial with the number/s you have.
.
I hope this helps. :highfive:
I have a Galaxy S3, i9300 - CM11.
Click to expand...
Click to collapse
Hi, I saw your thread and have similar problem. offset and normal state returns 0. After doing your steps I recieved 0 in offset but 67 in normal state when in call. Followed the tutorial as you describe adding the numbers converting to hex etc but my sensor do still not work.
After calibration according to your guide:
Out of call: It reports 36 in offset and 0 in normal state.
In call: It reports 36 in offset and 31 in normal state
Any ideas ?
Turwaithion said:
Hi, I saw your thread and have similar problem. offset and normal state returns 0. After doing your steps I recieved 0 in offset but 67 in normal state when in call. Followed the tutorial as you describe adding the numbers converting to hex etc but my sensor do still not work.
After calibration according to your guide:
Out of call: It reports 36 in offset and 0 in normal state.
In call: It reports 36 in offset and 31 in normal state
Any ideas ?
Click to expand...
Click to collapse
Have you flashed a stock firmware via odin?.
Beamed in by telepathy.
got the Hardware Info app it is called VIDEOCON ALPS X301
I'm thinking of putting a software ROM on the phone and saw this section "slim roms".
It's a pretty low end device and lags like hell when I load Facebook in browser (I have 5000 friends, which is probably why). Can't find specs on this device anywhere either.
One thing that bugs me is the proximity sensor does not work correctly. For example, if I'm in a call where it requires interaction (such as pressing 1 for this or 2 for that) when I remove it from my ear I have to press power to to turn the screen back on, navigate through 3-4 different menus (it's quirky too) and get back to the dialpad to press my choice.
I'm looking for a suggestion of a useful slim rom to reduce memory usage and possibly alleviate the problem with the hardware proximity sensor.
Thanks
this phone does not have a proximity sensor
Settings accessibility enable power button ends call and then disable it that's the only solution I found for the problem
kinesis said:
got the Hardware Info app it is called VIDEOCON ALPS X301
I'm thinking of putting a software ROM on the phone and saw this section "slim roms".
It's a pretty low end device and lags like hell when I load Facebook in browser (I have 5000 friends, which is probably why). Can't find specs on this device anywhere either.
One thing that bugs me is the proximity sensor does not work correctly. For example, if I'm in a call where it requires interaction (such as pressing 1 for this or 2 for that) when I remove it from my ear I have to press power to to turn the screen back on, navigate through 3-4 different menus (it's quirky too) and get back to the dialpad to press my choice.
I'm looking for a suggestion of a useful slim rom to reduce memory usage and possibly alleviate the problem with the hardware proximity sensor.
Thanks
Click to expand...
Click to collapse
Unfortunately, you aren't going to find much info unless you produce it yourself for that UMX brand. Budget Mobile no longer offer phone service and you'd have to unlock the phone on another carrier [which can be done nowadays luckily].
So back to the Galaxy Alpha-known problem after updating to 5.0.2 (may occur earlier):
Symptoms sometimes hang before rebooting which also hangs. (This much is lost rank)
Frequency: can be manifested periodically from once a week to once a day.
Workaround: turn off unlocking fingerprint
Now proven reasons, to be exact, that does not help, and checked up on my machine:
Problem married board - I replaced the basic service fee to the new - the symptoms were.
Problem Fingerprint Module - I replaced the fingerprint service - Problem remained.
Problem to be updated. - I have frequently different update 5.0.2 with a full reset and wipe. - Problem remained.
Problem in registering more than one print (2-3 imprint) - now is a new scanner and registered one print - hang 2 per day 15% charge for 16 hours (at least at the same I use to 18 hours 40% ostaettsa) saved wireless charging  in auto output and not in this case.
Interesting facts about problemme:
Entering knox via fingerprint (one member) does not freeze. Perhaps because periodically rather than continuously sitting in knox, and because of this it does not manifest itself. But the fact is that when you use to unlock the screen print - hangs apparatus using to enter knox not Wisnu. Perhaps you need razyasnit that podvisanie is not in the moment of release, while using all sorts of other applications, for example calls the camera, etc.
4.4.4 The second point on this crash was seen once every 3 months and on 5.0.2 I unlock when activated by fingerprint hangs on average once every 2 days.
Deadlock: Materinka scanner replaced - that is in fact a new phone .... - means no hardware Problem. Software updated not once - it means not software.
Conclusion: The mean initial miscalculation, engineering or something - but then why there are those who use the scanner to unlock 5.0.2 and it all ok ???? !!!
Sorry for my translation.
I have a rooted/unlocked Photon Q with a partially functional display. The initial warning "Your phone has been unlocked" comes up fine. When I put it in bootloader mode, the fast boot messages appear fine. On regular boot the screen is either black or on one occasion showed some randomly scattered pixels. Booting into recovery (TWRP) results in a black screen. In all cases adb/fastboot are able to properly communicate with the phone. I was able to test if the screen was on or off using adb commands, as well as turn it on/off. The commands did register and showed the screen correctly or or off though this was not reflected in the visual screen output. When toggling on/off state I saw some activity - it almost looked like the brightness was set to 0, but I verified that with adb as well and even set it to 100 to be sure with no change in the display behavior.
So my suspect is the graphics card, but it must be just some video modes given that fastboot diagnostic and initial warning can be displayed. I am about to replace the motherboard, but I am just curious about what exactly is wrong (and if by chance it can be fixed without replacing the motherboard). I also looked around for documentation on the video modes of the Photon Q graphics adapter, but could not find anything relevant - if somebody could point me to the right source this would be appreciated.
I would not mind writing some C code to poke around on the low level, but it would be nice to start from some sample code rather than from scratch.
Hi all.
The LCD of my A52s is broken. Android 12
I wanted to make an Backup but I cant access the files unless the display is unlocked.
I have registered a pattern and a Fingerprint.
Tried to use fingerprint : vibrating but not working
Tried Samsung Find my mobile to unlock screen : Not working, says "Remote unlocking is deactivated"
What are my options if there are any?
Dont want to root it.
Thank you in advance.
//edit :
Not sure if USB Debugging is enabled.
Otg usb adapter and a mouse
joke19 said:
Otg usb adapter and a mouse
Click to expand...
Click to collapse
The LCD is broken, not the glass :/ Its just black with some lines if activated. I cant see anything on the display at all
Fseggl84 said:
The LCD is broken, not the glass :/ Its just black with some lines if activated. I cant see anything on the display at all
Click to expand...
Click to collapse
Sorry
Mouses are relative positioning things. That makes life more difficult.
A digitizer pad would be better, but those too do a bit of panning.
You want an absolute pointer device.
I had an old hardware project that I just updated and used to debug some media commands.
It uses a serial port from a desktop that feeds a µC that is a peripheral to an Android over OTG.
So you can put absolute positioned clicks into an unrooted, non-ADB device.
But it seems to have a bug now. I have to look into it.
Dumb question: Do you need to swipe to enter your password or can you just click?
Renate said:
Mouses are relative positioning things. That makes life more difficult.
A digitizer pad would be better, but those too do a bit of panning.
You want an absolute pointer device.
I had an old hardware project that I just updated and used to debug some media commands.
It uses a serial port from a desktop that feeds a µC that is a peripheral to an Android over OTG.
So you can put absolute positioned clicks into an unrooted, non-ADB device.
But it seems to have a bug now. I have to look into it.
Dumb question: Do you need to swipe to enter your password or can you just click?
Click to expand...
Click to collapse
By password you mean the pattern to unlock? Its swiping.
Fseggl84 said:
By password you mean the pattern to unlock? Its swiping.
Click to expand...
Click to collapse
Yeah, I've never used it so I didn't know if you could just tap the dots in succession along the path.
Not a big deal or difference, if I could just get the HID report descriptor working.
Edit: Ah, got it working. Android doesn't seem to like it when a USB peripheral is a keyboard, consumer control, mouse and digitizer.
So I took the mouse out.
Did I guess your swipe pattern?
Do the swipe dots appear in your login screen centered exactly vertically?
Renate said:
Yeah, I've never used it so I didn't know if you could just tap the dots in succession along the path.
Not a big deal or difference, if I could just get the HID report descriptor working.
Edit: Ah, got it working. Android doesn't seem to like it when a USB peripheral is a keyboard, consumer control, mouse and digitizer.
So I took the mouse out.
Did I guess your swipe pattern?
Do the swipe dots appear in your login screen centered exactly vertically?
Click to expand...
Click to collapse
It looks like this =)
Thats not my display by the way.
When I try to use the fingerprint, it vibrates but the phone does not recognize it.
It's kind of pesky that the aspect ratio, the vertical position and the scale of the layout are all a bit variable.
At least the aspect ratio is a solid number. Height in pixels/Width in pixels. I make yours to be 2.18?
Too bad you didn't try to do this when your display was working!
My setup works fine, but that isn't really going to help you any at this stage.
I was thinking of getting a separate Android to use as the "digitizer" but that means getting a Linux USB HID gadget working.
That looks like a bunch of work and moreover it's not universal for any Android.
So, I don't know that this is going anywhere. It's even possible your device locks out USB OTG when you're not logged in.
That's easy enough to check, just use a OTG adapter and a USB device with a LED, flash drive, mouse, keyboard...
If you can borrow a Wacom tablet from someone that might operate in absolute coordinates.
The problem is, it can operate in relative mode too and without the Wacom software installed you won't be able to switch it.
The last Wacom I had just plugged into Windows and operated as relative.
https://support.wacom.com/hc/en-us/articles/1500006340122-What-is-Absolute-Positioning-
Unless you have an ATMega32u4 and a UART I don't know what we can do.
The Raspberry Pi 0W could do this too, but I'd have to write all the code for it.
Renate said:
It's kind of pesky that the aspect ratio, the vertical position and the scale of the layout are all a bit variable.
At least the aspect ratio is a solid number. Height in pixels/Width in pixels. I make yours to be 2.18?
Too bad you didn't try to do this when your display was working!
My setup works fine, but that isn't really going to help you any at this stage.
I was thinking of getting a separate Android to use as the "digitizer" but that means getting a Linux USB HID gadget working.
That looks like a bunch of work and moreover it's not universal for any Android.
So, I don't know that this is going anywhere. It's even possible your device locks out USB OTG when you're not logged in.
That's easy enough to check, just use a OTG adapter and a USB device with a LED, flash drive, mouse, keyboard...
If you can borrow a Wacom tablet from someone that might operate in absolute coordinates.
The problem is, it can operate in relative mode too and without the Wacom software installed you won't be able to switch it.
The last Wacom I had just plugged into Windows and operated as relative.
https://support.wacom.com/hc/en-us/articles/1500006340122-What-is-Absolute-Positioning-
Unless you have an ATMega32u4 and a UART I don't know what we can do.
The Raspberry Pi 0W could do this too, but I'd have to write all the code for it.
Click to expand...
Click to collapse
I really appreciate the time and thoughts you put into this problem.
But -> "no backup no sympathy"
I was my fault not doing a regular Backup and so I guess the data is gone. I might just let samsung change the display and hope they wont reset the device.
It's too bad you're not local. This would be a piece of cake.
It's actually so much fun watching this thing login.
I wrote a cleaned-up Windows program for this. Now the command is:
Code:
C:\>swiper /c3 /a2 /y0.683 /u 791364
The "password" uses the position of the digits on the keypad.
Unfortunately I've never done a deep dive into the whole encryption of /data
Is there a TWRP that can decrypt? Does that require swiping too?
I dunno, I might be able to mail you a RPi0 with code on it.
Still, if you didn't leave ADB on, it will be a big pain to enable it.
You could also buy a replacement screen and just connect it up floppy-wise without removing the old screen.
Sometimes the most simple ideas are the best.
We used cling film on the same model and painted dots on the film where the pattern is.
Put that cling film on my phone and swiped my pattern. After a few tries it unlocked.
Using my fingerprint wasn possible.
Oh! I thought that the touch screen itself was non-responsive.
I had presumed that you had unlocked it enough times that you could unlock it without looking.
In any case, I've had fun with this. My new secret unlock pattern is:
This has maximal pointyness and requires coordination to swipe between the dots without catching the wrong ones.
If they only gave us a choice of 4x4 or 5x5 we could come up with a pattern that a human couldn't do!