weird shutter noise when unlocking with knock knock - G3 Q&A, Help & Troubleshooting

I'm noticing a shutter noise when i tap in a wrong knock knock code , but it's not every time.
Anyone else getting the same? I checked and there are no photos being taken. I'm on an 855 UK model 16gb

mjb152 said:
I'm noticing a shutter noise when i tap in a wrong knock knock code , but it's not every time.
Anyone else getting the same? I checked and there are no photos being taken. I'm on an 855 UK model 16gb
Click to expand...
Click to collapse
Yeah I get the same.. It's just a denied tone I guess as the screen switches off (depending on your effect - I use Black Hole)

mjb152 said:
I'm noticing a shutter noise when i tap in a wrong knock knock code , but it's not every time.
Anyone else getting the same? I checked and there are no photos being taken. I'm on an 855 UK model 16gb
Click to expand...
Click to collapse
I had the same problem on my US Verizon G3. I tracked it down to AirDroid's "find my phone" feature. If you're still having this problem and use AirDroid, try turning that off in the app's settings menu.

It must be the Intruder feature.
If you've enabled Find Phone in AirDroid, then a photo will be automatically taken when someone tries but fails to unlock the device. After two consecutive failed attempts or if the device is not unlocked within 2 mins of the first failed attempt, the photo will be uploaded to your AirDroid account to help you find who's trying to unlock your device.

Related

[Q] Phone's camera stops recording after 10 minutes.

Hi guys, I'm having a problem with my xperia play when trying to record conferences.
My camera stops after 10 minutes of recording everytime, it even shows the timer backwards when it's the last minute, I was wondering if there is any way to lift this limitation.
I'm currently using the default camera application that comes with 2.3.4 North America generic ROM.
I got a 12GB memory card with around 3.2GB free and the video files take up to 400mb per 10 minutes, so the space shouldn't be a problem here.
Any help will be greatly appreciated, thanks!
Maybe your phones is going to sleep?
Have you tried disabling sleep timeout?
Masters2150 said:
Maybe your phones is going to sleep?
Have you tried disabling sleep timeout?
Click to expand...
Click to collapse
Hmm I wasn't aware that the phone had a sleep option, I can't seem to find it. Only time outs I could find if the screen display which is set to 30 seconds, so I guess that's not it.
Where can I find the options to disable the phone from sleeping?
Thanks.
Actually thats probably what I was thinking.
One thing you could try, when it gets close to 10 minutes, push a button on your phone, nothing to make it stop recording, maybe the settings button, just something to make sure it isn't a problem like this.
Masters2150 said:
Actually thats probably what I was thinking.
One thing you could try, when it gets close to 10 minutes, push a button on your phone, nothing to make it stop recording, maybe the settings button, just something to make sure it isn't a problem like this.
Click to expand...
Click to collapse
I did that and the phone responded perfectly, even changed some options while recording but it still stops at 10 minutes. The strange thing is when it gets to minute nine the counter changes backwards to count 1 minute in red numbers then it stops recording.
Maybe try a different phone app?
Sent from my R800i using XDA App

[Q] Server error occurred. Restart Camera.

The video camera function on my camera is no longer working and I’m not sure why. This phone is less than 5 weeks old and I have already taken videos with it. This upsets me because I have a 4 month old that I love to record especially when it comes to his firsts. The led flash light comes on when I push the video button, the screen switches and freezes. The message saying error prompts and when I close the camera, the led light will remain on until I reopen the camera. Hopefully you can help me figure this out, many thanks!
jacqueline robert said:
The video camera function on my camera is no longer working and I’m not sure why. This phone is less than 5 weeks old and I have already taken videos with it. This upsets me because I have a 4 month old that I love to record especially when it comes to his firsts. The led flash light comes on when I push the video button, the screen switches and freezes. The message saying error prompts and when I close the camera, the led light will remain on until I reopen the camera. Hopefully you can help me figure this out, many thanks!
Click to expand...
Click to collapse
Just a guess.. but you did in another posting say...
jacqueline robert said:
I install S5 Video App but it does not work properly in my note3. Can I use it in my device?
Click to expand...
Click to collapse
Which indicates you have been making changes to your phone related to video. Did you remove that or are you still using it.
Without knowing what your phone condition is in, it is very possible that other changes you have made is causing the problem as well...
Like...
jacqueline robert said:
Thanks For your Great Tutorial. It really helps me to update my Modem.
Click to expand...
Click to collapse
jacqueline robert said:
I think gravity box is better than other.
Click to expand...
Click to collapse
Most don't need to update their modem and if you installed software that modifies how your phone works, you might try turning them off or uninstalling them to see if they are the cause of your problems.
jacqueline robert said:
The video camera function on my camera is no longer working and I’m not sure why. This phone is less than 5 weeks old and I have already taken videos with it. This upsets me because I have a 4 month old that I love to record especially when it comes to his firsts. The led flash light comes on when I push the video button, the screen switches and freezes. The message saying error prompts and when I close the camera, the led light will remain on until I reopen the camera. Hopefully you can help me figure this out, many thanks!
Click to expand...
Click to collapse
ive also experiencing this SERVER ERROR OCCURED. RESTART CAMERA.. do you find a solution or did you fix it??? thnks..
Server error occurred. Restart Camera.
Same error on Galaxy A5.
Android 4.4.4
Tried: force stop, clean cache, clear data - problem repeatet!
Any help?
jacqueline robert said:
The video camera function on my camera is no longer working and I’m not sure why. This phone is less than 5 weeks old and I have already taken videos with it. This upsets me because I have a 4 month old that I love to record especially when it comes to his firsts. The led flash light comes on when I push the video button, the screen switches and freezes. The message saying error prompts and when I close the camera, the led light will remain on until I reopen the camera. Hopefully you can help me figure this out, many thanks!
Click to expand...
Click to collapse
u could try booting in safe mode and test if theres any app or tweak that is causing it. or u could enter Service / Test / Hidden functions by dialing *#0*# on your phone dialer and u gonna get to the service mode and check camera itself. also theres another one of those USSD codes that brings u to check the phone gadgets hardware /firmware version to see if it same as the camera app... u could also do a full factory restore from recovery screen if nothing else works remember to do a backup first @ titanium backup.. or if you have fair tech skills u could remove the back cover and remove the battery plate and check if tje battery connectors are in place im sure u could find a note 3 tear down video around.. i had the same problem but with the frontal camera and ended up been the camera was defective and replaced it and worked like charm
I know this thread is kinda old, but since it is on the first page on google's query, I'll post a solution here (found on another site).
The solution is to turn off the phone and remove battery for 10-20 seconds. This should resolve the issue.
Some users report that the issue occurs when you charge your phone via PC or laptop USB port. So, to avoid this, prefer original charger.
thanks
thank you for replying even if the post is old! it simply worked while i was about to sell my phone ! good thing i saw your reply first!
Did you ever find a fix?

Camera crashes when zooming

I got this issue lately when I try to zoom while recording video the camera app crashes and the recorded video is not saved (is corrupted and not playable). This used to work in the first week I got the phone, I remember using it at least once. I tried clearing data and cache for the app, but no joy.
Anybody else has this issue ?
For me it works just fine on Full Hd - 1080p and UHD - 2160p
This problem appears to be specific to the T-Mobile version. I asked around on Reddit to verify. I too have this same issue. Has anybody found a fix? I'm using the Google camera for right now as I don't need 4k video recording. Maybe a software reimage would help? It's possible they were shipped with a bad image on the device.
I had the same crash in my att device the first time I used it. Exactly the same . video and zoomed and I noticed it didn't refocus then it locked up.
Sent from my LG-D850 using XDA Free mobile app
ekerbuddyeker said:
I had the same crash in my att device the first time I used it. Exactly the same . video and zoomed and I noticed it didn't refocus then it locked up.
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Does it still happen? Were you able to fix it without using another camera app?
NexusWarrior said:
This problem appears to be specific to the T-Mobile version. I asked around on Reddit to verify. I too have this same issue. Has anybody found a fix? I'm using the Google camera for right now as I don't need 4k video recording. Maybe a software reimage would help? It's possible they were shipped with a bad image on the device.
Click to expand...
Click to collapse
My G3 is the D855 european version. It worked ok in the begining
maschenazi said:
My G3 is the D855 european version. It worked ok in the begining
Click to expand...
Click to collapse
I find it hard to believe this phone was even QA'd. Such a basic, useful function was broken out of the factory for almost everyone.
Mine works fine - I will admit I didn't try zoom when I first got it, and now I have updated the media xml files with the ones in this thread
http://forum.xda-developers.com/showthread.php?t=2778570
Not sure if that is making it work or not but works perfect for me.
If I get this same issue will just return my phone...this is crazy!
What I forgot to mention is that I have switched to ART. Could this be the cause ? Anyone with ART enabled on their G3 has this problem ?
Just to answer my own question, I switched back to davlik and still have this problem
I'm having the same issue. Mine is an AT&T LG G3 D850 not rooted and using ART. I was thinking about switching back to DAVLIK but seeing as you tried that and it didn't work for you.... I even restated the phone.
Unfortunately the v10e update doesn't fix this problem we're having
Have you reported it to LG yet ?
Sent from my LG-D855 using XDA Premium 4 mobile app
Solved
My G3 international version D855 had this problem ... i applied a hard reset and it works ... now it's fine with zooming while recording
I hope that may help
Its a bug in the LG Camera App. I just tried it on the LG camera app = crash, downloaded Google Camera = No crash on zoom while recording.
Edit: LG D850
Just got my G3 on Verizon about a week ago, same problem. Zooming in camera works fine but not with video. It did a few days ago, just noticed today that it doesn't work.
Edit: Tried the files that nest75068 suggested, didn't work for me and ended up making the Camera app crash even when trying to start a video. Google camera worked initially with video, crashed when I tried to switch to the front camera and now crashes on start. Focal also crashes when starting a video.
I'm having this on my unlocked UK (2GB) D855 variant. I've only noticed crashes while zooming while taking 4K video however.
Yesterday got a phone call from LG support. He said he was second line support, but I had to spend 5 minutes explaining to him what ART and Dalvik are and another 5 minutes trying to convince him that sending the phone to LG won't help. Disappointed, but no different from Samsung or HTC support in that respect.
If you have this problem please report it to LG, maybe if they have few more reports they will pull their finger out of their ass and do something about it.
I've called them and they couldn't help me either. I also asked them about there wireless charging stand that they announced along side the G3 announcement and where I could buy it... the person I talked to didn't know what I was talking about... they didn't even understand what PMA and Qi wireless charging was! I asked if they could connect me to someone who knew about there products and they said I had to call back to talk to someone else.... ?WHAT!?!?
I wasn't even aware you COULD zoom while doing video, but tried this at all resolutions except the slowmo and reproduced the bug.

Unable to make or take calls properly on CM11

Please refer to this post:
http://forum.xda-developers.com/showpost.php?p=62828995&postcount=1432
Has anyone gotten this problem? The person who posted this has been the only one having this problem. This can't be a rare thing, is it? Is everyone just dealing with this issue until it gets fixed?
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
AnotherContributor said:
One issue though I've been having is that when I'm making and receiving calls, sometimes the phone display goes black and will frankly not come back on. I press the App button and sometimes the display comes on, sends the call to the Status Bar, and the screen goes dark. So, I have to press the Application button again and draw down the menu to hang the call up. When I press the power button, the screen flashes on for maybe a quarter second then goes dark. It keeps doing that every time you press the power button. The worst case scenario that has happened a handful of times is that when I'm in a call, neither the power nor application button are responsive. When that happens, pretty much the only option is to power down the phone and reboot.
...
I'm not sure if I would be able to dial an extension with the way the phone is acting up. I feel like this was not an issue the first couple of weeks I had CM on the phone. Now, it seems to be happening with every call.
Click to expand...
Click to collapse
14th September 2015
samuraix21 said:
Hi, I have this issue. Were you able to fix this issue? You're the ONLY person that has posted this issue so I'm not sure if this is a rare hardware issue or everyone on this forum is somehow dealing with it until a fix comes up.
Click to expand...
Click to collapse
19th September 2015
hawk1500 said:
are people still experiencing the screen off during call problem? I am not talking about when you put it up to your face, but how the screen turns off and won't come back on?
Click to expand...
Click to collapse
20th September 2015
hawk1500 said:
Naw, no screen protector installed. tried the proximity sensor fix app as well as the xposed don't go to sleep during call module but it still does it.
Click to expand...
Click to collapse
20th September 2015
tonochito said:
i think that bugs should be listed more detailed:
front facing camera does not work well, if i want to take a selfie it crash. video camera also does not work equal it will crash. I had to install Google Camera and Open Camera in order to have both selfie and video options working, With Google Camera i take selfies and with Open Camera i record videos, As the guy talking about the scren off in calls is true, i don't have a screen protector and it has this behaivour, also as i mentioned there is kind of lag when i try to dial a number i have to do twice, it doesn't show up right away. The same goes when i am calling for example my carrier and i have to dial on the IVR i have to dial twice in order to get the dial keypad. I didn't have Google play crash.
Another thing that i notice was setting a wallpaper as screensaver does not fit in the middle or correctly i had to use Quick Pic and the option 768x1280 because with the stock gallery wallpapers are like aside of the middle
Click to expand...
Click to collapse
I think this issue needs some attention. I am having this problem as well (with and without screen protector). There are times that I need to enter extensions and codes during calls which has become impossible. I have two of these phones and they both behave this way. I recommend that people start posting screenshots of the app Proximity Sensor Finder which displays different distance numbers detected by the prox sensor. See my screenshot attachment which shows the proximity sensor always detecting a "covered" state of 0.0cm even when nothing is in front of the screen. Everyone should go try this and post their findings.
Other phones on CM11 were able to fix this problem in the past by adjusting the calibration which is unique for each phone, so I started searching around through the Fire Phone CM11 files and I found these:
/system/etc/permissions/android.hardware.sensor.proximity.xml
I could not discern anything of value from this .xml file.
/persist/sensor_calibration/SHCAL_DU20060142640727.csv
This file seemed promising. Its timestamp is back in 2014 so I assume that this comes straight from the original Fire Phone files. If this file is actively used to govern sensor behavior, I'm wondering if perhaps it is not being read correctly. It makes me wonder if there is a log out there somewhere that could shed more light on it. Anyways, you can open up that badboy in any spreadsheet to discover sensor IDs for a bunch of sensors along with calibration coefficients in the form of:
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=550.30
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=395.62
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=19262.26
You'll have to open it and analyze it in context of the other columns and other sensors. I've attached it (re-saved in xlsx format because .csv files are not permitted - if you don't trust my xlsx just retrieve the file from your phone). I highlighted the rows of interest. We could just mess with coefficient values, but without any guidance, it could just be a waste of time. Plus we don't know if this even governs the sensors or if it's just helpful documentation. If anyone has insight about this or even far fetched theories, please comment!
I'm thinking about doing a 'grep' on the entire file tree for some of these key words like SENSOR_ID=SI1143, SI1143, 4CCU1, COEFF0, SENSOR_TYPE=PROX etc etc - to see if any files use any of these terms. It may prove unfruitful due to the amount of compiled software that is no longer in text form. Any thoughts about any of this?
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
tonochito said:
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
Click to expand...
Click to collapse
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
jdmillard said:
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
Click to expand...
Click to collapse
i will give a shot, and post my result
In fact, it would be AWESOME if we could get someone (whose screen does behave perfectly during calls) to post their findings from Proximity Sensor Finder. If their screen works perfectly during calls and this app shows 0.0cm all the time for them too, then we can conclude that this app isn't functioning correctly and we know we need to find our root cause elsewhere.
tonochito said:
i will give a shot, and post my result
Click to expand...
Click to collapse
Available but why it doesn't work right?
tonochito said:
Available but why it doesn't work right?
Click to expand...
Click to collapse
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
jdmillard said:
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
Click to expand...
Click to collapse
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
tonochito said:
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
Click to expand...
Click to collapse
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
jdmillard said:
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
Click to expand...
Click to collapse
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
jdmillard said:
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
Click to expand...
Click to collapse
your welcome
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
KLit75 said:
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
Click to expand...
Click to collapse
I was lucky enough to have a good return policy on the glass screen protectors I recently got (for two Fire Phones). I'm returning them today and I've already ordered this as a replacement:
http://www.amazon.com/gp/product/B00WXY18WK?psc=1&redirect=true&ref_=od_aui_detailpages00
It has excellent reviews, decent price, very thin, and it is specifically mentioned many times in the reviews that there is a little cutout for the prox sensor (and you can see if if you look carefully at the pictures). I'm hoping that it will solve my black screen woes and protect my screen. There are reports from folks on these forums saying that there is still some strange behavior during calls (such as your example among others). I personally haven't encountered what you're describing, but I'll keep an eye out to see if I can be of any help.
jdmillard said:
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
14th September 2015
19th September 2015
20th September 2015
20th September 2015
Click to expand...
Click to collapse
Hi. I like to get back about this since I've been quoted on this.
For me, the glass protector screen that I brought from XtremeGuard was the issue my dad had when he tried to make or take calls. After I removed it, it was back to normal.
The persistent issues now, based on what my dad is telling me, is that sometimes after you dial in a number and call a person, you don't hear the ringing tone to know if it went through or not. My dad would freak out when someone on the other line said something since the ringing tone is not working.
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
hi
this is usually related to hardware composer.
cheers
superdragonpt said:
hi
this is usually related to hardware composer.
cheers
Click to expand...
Click to collapse
but why? does it matter with the bootloader, i mean i know the CM11 on the Fire phone still on beta with no NFC working and the camera too at least i am using Snap camera and everything works. But making calls is a bit annoying even i don't use the phone to make a lot of calls just for WhatsApp almost all the time

Unable to Answer or Reject Calls

Hello,
I have been struggling recently to answer or reject calls when given the swipe up or down option.
When its unlocked and I get the tap to answer or reject as a notification its fine.
I'm just wondering if anyone else had a similar issue or had found a fix.
I'm on the official firmware, running 8.1.0
I've experienced something similar too. Sometimes I find myself swiping over and over again just to get one call answered or rejecte I have no idea why it does that, or when, it seems to be random on mine
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
I've found you can swipe down from the top of the screen and can answer it from the notification menu instead.
Just takes longer.
cobben said:
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
Click to expand...
Click to collapse
Just after having written the above, the phone corrected itself.
Now I can answer calls on the first swipe.
Interesting . . .
Sometimes my phone will let me answer normally. most of the time however I have to use the notification bar.
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Yup, been having the same issue. Stock phone, no root. What's frustrating is there as no further updates.
iliais347 said:
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Click to expand...
Click to collapse
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
cobben said:
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
Click to expand...
Click to collapse
What i did is i added the google dialer app to my phone, then to game booster and set its fps to 40. Now i can answer the calls.

Categories

Resources