Hi, i've faced op7 pro sensor's frustrating issue , screen lights while im in a call , when listening to voice notes , etc..
after 7 hours of trials , simply i found a solution , it's a lifesaver
the solution is to download Proximity Sensor Reset/Fix (+Overrider service) app from playstore , skip the first step , second step put your phone to your ear and press next , third step Keep it out of your ear and press next, you're done , restart your phone & keep the app installed so the saved parameter keeps loading whenever you restart your phone , now try to make a call or listen to a voice note and press thanks button :good:
I tried this before on my OP7 and it didn't help.
KhaledMohamed26 said:
Hi, i've faced op7 pro sensor's frustrating issue , screen lights while im in a call , when listening to voice notes , etc..
after 7 hours of trials , simply i found a solution , it's a lifesaver
the solution is to download Proximity Sensor Reset/Fix (+Overrider service) app from playstore , skip the first step , second step put your phone to your ear and press next , third step Keep it out of your ear and press next, you're done , restart your phone & keep the app installed so the saved parameter keeps loading whenever you restart your phone , now try to make a call or listen to a voice note and press thanks button :good:
Click to expand...
Click to collapse
Work perfectly now thanks but I made all the steps and rebooted the phone.
KhaledMohamed26 said:
Hi, i've faced op7 pro sensor's frustrating issue , screen lights while im in a call , when listening to voice notes , etc..
after 7 hours of trials , simply i found a solution , it's a lifesaver
the solution is to download Proximity Sensor Reset/Fix (+Overrider service) app from playstore , skip the first step , second step put your phone to your ear and press next , third step Keep it out of your ear and press next, you're done , restart your phone & keep the app installed so the saved parameter keeps loading whenever you restart your phone , now try to make a call or listen to a voice note and press thanks button :good:
Click to expand...
Click to collapse
I can confirm this works, thx (Y)
ok.. too early to report back.. will keep it installed and see if it works.
Proximity sensor was indeed a headache in OP7pro
The phone need to be rooted right? I tried covering the sensor, but the app doesn't seem to be registering any action.
GalosSide said:
The phone need to be rooted right? I tried covering the sensor, but the app doesn't seem to be registering any action.
Click to expand...
Click to collapse
I set it without root, and it works with no problem here !
Just flash that persist image in fastboot and all will be solved
Hi, which persist image is this and is this just a simple flash via fastboot? Will I lose recovery when doing so? Any other precautions to take?
thznutz87 said:
Just flash that persist image in fastboot and all will be solved
Click to expand...
Click to collapse
amirage said:
Hi, which persist image is this and is this just a simple flash via fastboot? Will I lose recovery when doing so? Any other precautions to take?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/help/request-stock-persist-img-t4093885
Fastboot flash persist persist.img
KhaledMohamed26 said:
Hi, i've faced op7 pro sensor's frustrating issue , screen lights while im in a call , when listening to voice notes , etc..
after 7 hours of trials , simply i found a solution , it's a lifesaver
the solution is to download Proximity Sensor Reset/Fix (+Overrider service) app from playstore , skip the first step , second step put your phone to your ear and press next , third step Keep it out of your ear and press next, you're done , restart your phone & keep the app installed so the saved parameter keeps loading whenever you restart your phone , now try to make a call or listen to a voice note and press thanks button :good:
Click to expand...
Click to collapse
Hi,
Wouldn't it better to provide the application link ?
solid.snake said:
Hi,
Wouldn't it better to provide the application link ?
Click to expand...
Click to collapse
Are you that bored that you had to make such a comment on a thread 6 months old?
And if you're still so lazy to actually look for the apk, here you go. https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
hallo dare said:
Are you that bored that you had to make such a comment on a thread 6 months old?
And if you're still so lazy to actually look for the apk, here you go. https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
Click to expand...
Click to collapse
Thanks, but no, Im not lazy, just head to Playstore and hit for "proximity sensor reset" and you tell me then.
Are you that bored that you had to make such a comment on a thread 6 months old? >> Indeed
solid.snake said:
Thanks, but no, Im not lazy, just head to Playstore and hit for "proximity sensor reset" and you tell me then.
Are you that bored that you had to make such a comment on a thread 6 months old? >> Indeed
Click to expand...
Click to collapse
Funny that i was able to find it no problem based on the exact wording of the OP. Bye
Gotta love the non-toxic spirit of these forums. Heartwarming.
@OP thanks a lot. Tried this on the OP7T Pro and it actuallz worked. Do I have to keep the app installed though?
Edit: interestingly enough, this wiped my entire keyboard config (florisboard).
Related
Hello,
I got this magnificent device a week ago and I experienced a problem it has with vibrating.
When I put it on vibration mode it vibrate but when I put it on a regular mode (sound & vibration) the device doesn't vibrate when I got a call,
I checked at the system settings and the vibration is on full power,
please help me with the problem cause it is really frustrating.
By the way I'm using nova launcher and android 4.0.3.
10x
dugthegun said:
Hello,
I got this magnificent device a week ago and I experienced a problem it has with vibrating.
When I put it on vibration mode it vibrate but when I put it on a regular mode (sound & vibration) the device doesn't vibrate when I got a call,
I checked at the system settings and the vibration is on full power,
please help me with the problem cause it is really frustrating.
By the way I'm using nova launcher and android 4.0.3.
10x
Click to expand...
Click to collapse
Yeah that's a bug in the leaked version of ICS and roms based on that. You can go ahead to play store (android market) and install this app - volume ace - https://play.google.com/store/apps/...xLDEsIml0LmJyYWluY3Jhc2gudm9sdW1lYWNlZnJlZSJd
And in its profile just put the phone in ringing and vibration mode. Now the phone will ring and vibrate simultaneously!!
Hit thanks if it helped!
It didn't help,
the program only let's you control the audio power,
the only thing about vibration the program has is the option to put the phone on silent&vibration mode.
thanks anyway..
It works. Check the attached screenshot. Enable the options highlighted and just restart the phone and restart the volume ace and see if the options you selected are still showing as selected (doesn't get revert to default). Now whenever a call comes the phone will ring and vibrate
It helped !
where do I hit thanks? I cant find it..
Oh..
It worked.. You win 1 thanks and 4 internets!!!
Glad it worked for you both !!
Enjoy your Note
Cheers!!
Still no vibration
Hi,
your solution did not work for me. Can anyone help me, I miss about half of my calls because of this..
I am running on Rocketrom with Hydracore kernel.
Thanks
have you tried a different kernel?
Still not working
nokiamodeln91 said:
have you tried a different kernel?
Click to expand...
Click to collapse
Yes, I have, I was on Abyss kernel before switching to Hydracore. I did not work back then either.
I got results when doing:
echo 1000 > /sys/.../vibrator/enable
Otherwise, nothing.
Can anyone upload the symlinker function, ortell me where to get it ? If I can find out what is being called py apps when trying to vibrate, I may symlink it to beforementioned /sys/.../vibrator/enable.
Regards from Switzerland
vibration dont work
I just install this ROM : Ultimate_N7000_LSC_JB_4.1.2_v5.1 , and vibration dont work at all.
Any suggestion ????
Hi people, I got my phone today, and as you do, you set it up how you like it, I set it to keep the home, back and settings keys to light all the time, and it did. I did a OTA up software update, and now, even though ive put it to keep keys lit at all time, it still goes off after a few seconds?any one else had this problem?
OrionCarl said:
Hi people, I got my phone today, and as you do, you set it up how you like it, I set it to keep the home, back and settings keys to light all the time, and it did. I did a OTA up software update, and now, even though ive put it to keep keys lit at all time, it still goes off after a few seconds?any one else had this problem?
Click to expand...
Click to collapse
Got my phone today with 10d on it. Almost immediately got an update to 10f and exactly the same - the front key lights always turn off after what I believe to be 1.5 seconds, no matter how I set it
Hm...same here. Lights turn off after 2-3 sec.
Sent from my LG-P880 using xda app-developers app
mali_veseljak said:
Hm...same here. Lights turn off after 2-3 sec.
Click to expand...
Click to collapse
Going to raise this with LG Tech Support once their e-mail contact page is back up and running
lol >> it is fun to say that the light for front keys turn off after 1.5 or 2 seconds
You can make it long from the setting and HERE THE PROCEDURE ..
PLEASE GO TO ( Settings > Power saver > Front key light ) there is Gear button beside it >> press it and change the period of time ..
Don't forget to press on Thanks button if I help you Guys
Best regards,
ozeer said:
lol >> it is fun to say that the light for front keys turn off after 1.5 or 2 seconds
You can make it long from the setting and HERE THE PROCEDURE ..
PLEASE GO TO ( Settings > Power saver > Front key light ) there is Gear button beside it >> press it and change the period of time ..
Don't forget to press on Thanks button if I help you Guys
Best regards,
Click to expand...
Click to collapse
Not exactly, no. That setting gives you the option of '1.5 seconds' or 'Always off' and only applies to how the lights work during Power-Save mode, not normally.
Nice try to make us look stupid though :banghead:
SimonTS said:
Not exactly, no. That setting gives you the option of '1.5 seconds' or 'Always off' and only applies to how the lights work during Power-Save mode, not normally.
Nice try to make us look stupid though :banghead:
Click to expand...
Click to collapse
lol >> I am sorry , but I like kidding with anyone ..
Yes , you're right with that the option for the light of front keys is 1.5 or off
_______________________________________________________________________
I found the solution for that now
Please GO TO ( Settings > Display > Front Key Light ) >> there is option is that " Always On "
Please try that and replay .. I am waiting
Best regards,
ozeer said:
lol >> I am sorry , but I like kidding with anyone ..
Yes , you're right with that the option for the light of front keys is 1.5 or off
_______________________________________________________________________
I found the solution for that now
Please GO TO ( Settings > Display > Front Key Light ) >> there is option is that " Always On "
Please try that and replay .. I am waiting
Best regards,
Click to expand...
Click to collapse
I'm not sure if you are intentionally trolling or just stupid.
It is quite clearly stated that setting to 'Always On' makes no difference at all.
Do you have v10f on your phone? Do you even have this type of phone?
Calling all owners. Is there anyone out there?
OK, so I have raised this with LG Tech Support and they are telling me that it is an "Isolated Issue". Here is the copy of my emails with them;-
ME: I purchased this phone yesterday in the UK. I immediately got an OTA update to v10f. With this version there appears to be a bug. The "Front key light" setting doesn't change anything. I want to set it to "Always On" so that the lights are on whenever the screen is, but the button lights still go out after about 2 seconds.
This appears to be a software problem as other people on the forums have reported the same issue.
Click to expand...
Click to collapse
THEM: Based on the information you have provided me with, and after reading through your query, I would recommend that this is a standard setting on the handset unfortunatly unless in use the LED lights will power down, if you touch the LED lights they should illuminate again but unfortunatly there isnt a setting that you can change. Unfortunatly we are unable to do anything here at LG currently but we will raise this as a issue and you will have to wait for another update or bug fix if this is a software issue.
Click to expand...
Click to collapse
ME: This is definitely NOT a standard setting. Under software v10d this worked perfectly - as long as the screen was on, the buttons were lit up. The setting has the option of "Always On" and the fact that it doesn't work means that something is broken in the code. I have looked on XDA-Developers.com and found that I am far from the only person with this problem. There is also a partial solution which may point to the problem;-
"EDIT: OMG, changing the content of this file to 1 did fix it instantly! I'm not sure, if this app caused this behavior to happen but if anyone has the same issue, the exact location of the file is:
/sys/devices/platform/button-backlight/leds/button-backlight/br_maintain_on
EDIT 2: the file will be set to Ɔ' on each reboot, even with read-only permissions and when this app is not installed. It looks like this could be a firmware bug?
Maybe this will help - but at the moment I am seriously considering returning my phone and getting something by a different manufacturer as this is more than just annoying. Having those buttons flick off so quickly is a real nightmare when you are actually using the phone.
Click to expand...
Click to collapse
THEM: Based on the information you have provided me with, and after reading through your query, I would recommend that this appears to be a islolated issue, as said before i will raise a Voice Of Customer which means that i will be raising this issue to head office and they will read this and look into the case. Unfortunalty i must inform you that your handset is covered by LG for 12 months under warrenty but you will fully void this by changing the codeing or altering the data inside the handset in anyway, this will also mean that the LG engineers will not repair this as it will be deemed as rooted.
Click to expand...
Click to collapse
Can anyone out there confirm that they are running v10f and that the screen buttons work correctly for them. It would be interesting to tie this down and see if it is a problem with all v10f versions, if it is location specific, or if it maybe only effects certain batches of the phones.
---------- EDIT -----------
Thanks to this post by k1337Ultra, it appears that this can be fixed by disabling and then re-enabling the Automatic Brightness. Hope this helps others - very annoying though to find the solution buried in a totally irrelevant thread
---------- EDIT 2 -----------
And it works after a reboot as well. Yippee!!!!!
Good news for that you have fixed your problem .. Don't blame me with that because I am using V10C firmware and it is superb with no problem on LED buttons
Best regards,
ozeer said:
Good news for that you have fixed your problem .. Don't blame me with that because I am using V10C firmware and it is superb with no problem on LED buttons
Best regards,
Click to expand...
Click to collapse
Thanks - it would also have been helpful if you had either;-
1) mentioned that you were using an old version of software
2) actually read the OP and my post, realised that we were talking about a problem only in the latest version, and realised that posting would be fairly pointless.
its nice to see im not the only one that has the issue!! similar to you, if I enable the auto brightness the buttons stay lit fine, soon as I put it back, it goes back to going off after a few seconds!very annoying given they are not real buttons so can be a pain to find, grrrrr!
OrionCarl said:
its nice to see im not the only one that has the issue!! similar to you, if I enable the auto brightness the buttons stay lit fine, soon as I put it back, it goes back to going off after a few seconds!very annoying given they are not real buttons so can be a pain to find, grrrrr!
Click to expand...
Click to collapse
I am following it up with LG Tech Support and will post back here if they actually tell me anything useful.
ok simon, doubt you will you get any sense out of them, their backup isnt up to much sadly! good luck
It's just to inform that the keys light are working like they should in V10G
Sent from my LG-P880 using xda app-developers app
RuedasLocas said:
It's just to inform that the keys light are working like they should in V10G
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
cool, cheers for that!! have to wait untill it comes here by the looks of it!:good:
The new official V10H Firmware solves this bug also
Go to System\usr\idc and open file clear_ped.idc with a text editor
look for the line
#Pressure
touch.pressure.scale=0.2
I changed to 0.1, save and close,
Secondly go to System\usr\idc and open file clearpad.idc
look for the line touch.filter.level = 2
I changed the level = 2 to level = 4
Reboot and enjoy.
My touchscreen now works flawlessly and I hope this fix works for others please test and report back your findings.
Remember to hit thanks if I helped you in any way.
You can try other settings, You can change the 4 , from 1-7 1 being most sensitive, not always best and 7 being the least. Each device will be different and vary in results. I wouldn't recommend going to 7 though as your touchscreen might become unresponsive.
I found 4 was the best on my handset,. Good luck.
I did that and I think it's a bit better now...
Sent from my C6903 using Tapatalk
How would I do this? I got a rooted xperia z1 but not sure what to do next.
Cheers
Dark-Skript said:
How would I do this? I got a rooted xperia z1 but not sure what to do next.
Cheers
Click to expand...
Click to collapse
You need a file manager such as Astro Manager, then just follow the instructions given here... go to System\usr\idc in the file manager.
TagEHeuer said:
You need a file manager such as Astro Manager, then just follow the instructions given here... go to System\usr\idc in the file manager.
Click to expand...
Click to collapse
After trying to edit the file it refuses to save. I have tried 2 different file managers now, Is it read only or something?
What Rom and Kernel are you on
Dark-Skript said:
After trying to edit the file it refuses to save. I have tried 2 different file managers now, Is it read only or something?
Click to expand...
Click to collapse
What Rom and Kernel are you on, I think some 4.3 ROMs still have an issue with the system being read only, I'm by no means a dev and you would need to read about this on whatever ROM you have thread, once you gain access to system being read, write you will have no issue saving.
Try other settings
ArashMiniStar said:
I did that and I think it's a bit better now...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
You can try other settings, You can change the 4 , from 1-7 1 being most sensitive, not always best and 7 being the least. Each device will be different and vary in results. I wouldn't recommend going to 7 though as your touchscreen might become unresponsive.
I found 4 was the best on my handset,. Good luck.
Dark-Skript said:
After trying to edit the file it refuses to save. I have tried 2 different file managers now, Is it read only or something?
Click to expand...
Click to collapse
I'm sorry I'm really not sure why it's like that, as other post said depending on your ROM, it's best to contact the developer who made it. If you're using stock, then reply to me and I'll try and help further
TagEHeuer said:
I'm sorry I'm really not sure why it's like that, as other post said depending on your ROM, it's best to contact the developer who made it. If you're using stock, then reply to me and I'll try and help further
Click to expand...
Click to collapse
Well i thought id give CyanogenMod a shot, but bricked my phone haha.. I did not mind if the camera was not working as long as I could use the rest of the things.. Anyway whats happened is the Screen backlight is on but its on a grey screen
I can't turn the phone off to enter recovery mode either.
Dark-Skript said:
Well i thought id give CyanogenMod a shot, but bricked my phone haha.. I did not mind if the camera was not working as long as I could use the rest of the things.. Anyway whats happened is the Screen backlight is on but its on a grey screen
I can't turn the phone off to enter recovery mode either.
Click to expand...
Click to collapse
Try pressing and holding power button and volume up until it vibrates 3 times, after you've rebooted the phone.
If that doesn't work:
Best thing to do is link it up to PCCompanion and reset the phone to all it's factory settings. Try that?
Edit, best we talk here: http://forum.xda-developers.com/showthread.php?p=49018376#post49018376
TagEHeuer said:
Try pressing and holding power button and volume up until it vibrates 3 times, after you've rebooted the phone.
If that doesn't work:
Best thing to do is link it up to PCCompanion and reset the phone to all it's factory settings. Try that?
Edit, best we talk here: http://forum.xda-developers.com/showthread.php?p=49018376#post49018376
Click to expand...
Click to collapse
Thank you soo much, for all the help. This fixed the issue!!
Dark-Skript said:
Thank you soo much, for all the help. This fixed the issue!!
Click to expand...
Click to collapse
It's a pleasure, always happy to help.
Hello guys! I came here to show you this video:
[Search Youtube for XPERIA Z1 タッチ切れ再現法 The method of reproduce] Sorry, new users can't post links it seems. But please check the video out.
I wanted to ask if any of you could give a reasonable explanation of it. If this is a software issue - how could it be reproduced in such a manner, by touching the metal frame of the phone? The video shows it pretty well. I also managed to reproduce the bug like this on my Z1. It has been in service for about 20 days now. I am worried that they might just 'mask' a hardware issue with software filtering. My initial assumption is that this is due to bad grounding? Why else would human contact trigger it? You can see it can be reproduced on-demand like this.
Thanks for reading! I hope someone can explain it.
Actually,you don't have to touch the metal frame!
Just put Z1 on a desk,wait for 30 seconds,touch screen and the bug will happen !
水攸月羽 said:
Actually,you don't have to touch the metal frame!
Just put Z1 on a desk,wait for 30 seconds,touch screen and the bug will happen !
Click to expand...
Click to collapse
Agree.
eclyptos said:
Agree.
Click to expand...
Click to collapse
video demonstrates that a touch is being registered when touching the frame. It's kinda weird since why did the screen reacted to the touched frame. I have done that also and it's the same with me. But even after touching the frame and screen registered the touch, still screen fails to produce a continuous touch.
Sometimes it produces phantom touches which can be the cause of the random zooming and highlighting when browsing
Also tried changing the touch filter and failed to save. I think it needs root access
Im also facing such issue like I touched in sketch app & locked phone with other finger.Unlocked it while keeping the finger at same spot,then scolling the finger missed the touch
Also after playing GTA SA for about 30 min the touch sometimes stop responding.Any solutions
I tried above method but nothing works.I don't want to give this phone as I got it in replacement regarding yellow hue issue.
One issue after another emerges
Sent from my C6902 using XDA Premium 4 mobile app
RISHI RAJ said:
Im also facing such issue like I touched in sketch app & locked phone with other finger.Unlocked it while keeping the finger at same spot,then scolling the finger missed the touch
Also after playing GTA SA for about 30 min the touch sometimes stop responding.Any solutions
I tried above method but nothing works.I don't want to give this phone as I got it in replacement regarding yellow hue issue.
One issue after another emerges
Sent from my C6902 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is really a widespread problem across the globe. even Z1s owners are plagued by this problem and most likely even the z1 compact.
@Banwell13 I've not tried this as my touchscreen problem seems to have fixed itself? Strange.
But i'll definitely be keeping this thread in mind if it re-occurs.
Thanks for your efforts m8, appreciate it.
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
水攸月羽 said:
Actually,you don't have to touch the metal frame!
Just put Z1 on a desk,wait for 30 seconds,touch screen and the bug will happen !
Click to expand...
Click to collapse
Think what he ment was if you hold the frame then the issue doesn't occur, well that's what happens on mine at least, putting it down on a desk usually makes the bug show it's face. Holding the frame fixes it.
@dladz, @brapicoco, Guys, we said this 20 times, the issue don't show on our devices in the same mode.
hi guys,
I'm working on CM-11-20140606-NIGHTLY.
currently I'm facing two problems:
1- when i plug my headset, if anyone calls ringing be in the headset it self, so if i'm not beside my note i'll never hear it.
i didn't face this issue in stock rom as ringing works with both mobile itself and headset at the same time.
so, is there any way i can follow to make it act as stock rom??
2- some times when i press home button to use it, soft buttons lightened but screen still black and no way to make mobile works again unless i restart it.
3- on stock rom i used to install xposed installer and apply "enable call recording" and was working flawlessly by replacing add button by record, now it doesn't work and need it sometimes.
any suggestions?
NaAZoOR said:
hi guys,
I'm working on CM-11-20140606-NIGHTLY.
currently I'm facing two problems:
1- when i plug my headset, if anyone calls ringing be in the headset it self, so if i'm not beside my note i'll never hear it.
i didn't face this issue in stock rom as ringing works with both mobile itself and headset at the same time.
so, is there any way i can follow to make it act as stock rom??
2- some times when i press home button to use it, soft buttons lightened but screen still black and no way to make mobile works again unless i restart it.
3- on stock rom i used to install xposed installer and apply "enable call recording" and was working flawlessly by replacing add button by record, now it doesn't work and need it sometimes.
any suggestions?
Click to expand...
Click to collapse
Hey there! Let's see:
1. I really have no idea what could be happening...try asking on the CM11-Nightlies Discussion forum or the devs at the Development thread.
2. Are you sure the screen STAYS black?? On my phone, I get the black screen with softkeys lighting up, but display turns on after a good 10 second lag...
3. What exactly is the problem here? Is the record button not displaying? Does the module support KitKat?
Try disabling the module>reboot>re-enable>reboot. If that doesn't help, uninstall and re-install the entire Xposed Framework.
Xposed-related problems don't usually get support but you can ask at the discussion thread linked above.
The Dork Knight Rises said:
Hey there! Let's see:
1. I really have no idea what could be happening...try asking on the CM11-Nightlies Discussion forum or the devs at the Development thread.
2. Are you sure the screen STAYS black?? On my phone, I get the black screen with softkeys lighting up, but display turns on after a good 10 second lag...
3. What exactly is the problem here? Is the record button not displaying? Does the module support KitKat?
Try disabling the module>reboot>re-enable>reboot. If that doesn't help, uninstall and re-install the entire Xposed Framework.
Xposed-related problems don't usually get support but you can ask at the discussion thread linked above.
Click to expand...
Click to collapse
1- I'll check above links, thanks.
2- may be i didn't wait for a whole 10 seconds, usually i restart it after a press or two.
will wait and check.
3- probably module isn't compatible as it was updated 25-7-2013.
I've tried uninstall and reinstall both module and Xposed framework.
many thanks for your interest.
NaAZoOR said:
1- I'll check above links, thanks.
2- may be i didn't wait for a whole 10 seconds, usually i restart it after a press or two.
will wait and check.
3- probably module isn't compatible as it was updated 25-7-2013.
I've tried uninstall and reinstall both module and Xposed framework.
many thanks for your interest.
Click to expand...
Click to collapse
You're welcome(though you COULD just hit the Thanks button next time, yknow )
And yeah, try waiting for a few seconds for the black screen problem...I'm pretty sure we're having the same problem...
everytime i try to make or answer a call my phone turns off
even in apps like facebook messenger or whatsapp
i have no idea what may be causing this to happen (i have the newest version of system)
already tried to restore it to factory settings but that haven't helped
i hope that someone here knows what to do
thanks in advance
wosgos said:
everytime i try to make or answer a call my phone turns off
even in apps like facebook messenger or whatsapp
i have no idea what may be causing this to happen (i have the newest version of system)
already tried to restore it to factory settings but that haven't helped
i hope that someone here knows what to do
thanks in advance
Click to expand...
Click to collapse
Hello. I had a problem like that. There are several possibilities.the sensor window and can be scratched. At each call this is black screen. You have to wait for the person to hang up for your screen to work. You have dropped your phone and your sensor has moved. Or you just had a dust at the sensor. If you have to change the screen it is possible that at the level of the sensor there is a transparent or slightly black film. You scratch a little and it must work. I hope I helped you