Related
Touchscreen Issue: This thing has been persistent from the very beginning. After struggling for months, it has been mostly fixed with the last update. But double tap to wake is still a 50/50 chance, most of the time it's 4 taps to wake.
WiFi Issue: I have come across may complaint across internet about wifi issue for LG G4, ppl suggested several solutions but none really worked. Wifi connection suddenly drops, and also takes a considerable amount of time when waking up from sleep. It gets very annoying when I am on a voip or hangout call.
No it's not my router or my phone. Because it's the same on my home and work network, where other devices just work fine. Also I don't have any of those issues on CM12.1 rom. CM is quite nice on LG G4 but having to be using it on CM is not an option, as I lose the camera.
Besides I didn't pay the money to purchase a flagship device to use it on a different rom.
So, that's it. LG better fixes it on the Marshmallow, otherwise Good Bye LG.
Update: The WiFi is much better since I uninstalled Xposed. I am guessing that some xposed module had something to do with it. Can anybody confirm?
No change in the double tap to unlock though. Funny thing is that it works perfectly with CM.
Sorry to hear you are still having issues with your device. My only issue is the double tap to wake/sleep, but its something that I can live with. I never had an issue with wifi on any network, work/home/neighbors, ever.
Have you tried any of the roms supplied by our great devs or are you on stock?
esjames said:
Sorry to hear you are still having issues with your device. My only issue is the double tap to wake/sleep, but its something that I can live with. I never had an issue with wifi on any network, work/home/neighbors, ever.
Have you tried any of the roms supplied by our great devs or are you on stock?
Click to expand...
Click to collapse
I tried stock rooted debloated, also stock-based xtreme rom. Always having these issues.
Hmm..... Thats weird, My G4 has been runing good since I first purchased it in september..... Guess I got lucky.
I feel the ops pain, because I've had the WiFi issues a few times, and the tap to wake is 50/50 at best. I'm also growing tired of waiting for updates from LG or Tmo.
The poor 5GHz wifi support kills me. Only device in the household that has that issue. Other than that, though, I've been pretty happy with the G4.
I purchased my G4 a month ago and don't have those issues. Double tap works fine and my phone uses 5g WiFi at home. I wish you luck op.
As far as the WiFi is concerned, I have the same problem. Using WiFI Analyzer, I can see that all available wireless networks near me drop to 0 every minute or so, and then start back up. My wife also has a G4, and her device does not do that. I'm wondering if there was either a bad batch of WiFi radio chips, or poor connections to the mainboard for a group of these.
I think the tap to wake issue is because of that other stupid "feature" that I'm sure not a single person uses.
You know the one where when the screen is off, you swipe down from the top of the screen and it shows the clock? My phone often mistakes my taps to wake as swipes and tries to activate that instead (I can tell because the notification led comes on when that is activated).
Is there any way to turn that thing off? It is completely useless. It would be one thing if it showed the notifications but no it just shows the clock
aptalca said:
I think the tap to wake issue is because of that other stupid "feature" that I'm sure not a single person uses.
You know the one where when the screen is off, you swipe down from the top of the screen and it shows the clock? My phone often mistakes my taps to wake as swipes and tries to activate that instead (I can tell because the notification led comes on when that is activated).
Is there any way to turn that thing off? It is completely useless. It would be one thing if it showed the notifications but no it just shows the clock
Click to expand...
Click to collapse
I agree with you on... that is probably the case. A completely useless feature, which also doesn't work half the time.
suhridkhan said:
Touchscreen Issue: This thing has been persistent from the very beginning. After struggling for months, it has been mostly fixed with the last update. But double tap to wake is still a 50/50 chance, most of the time it's 4 taps to wake.
WiFi Issue: I have come across may complaint across internet about wifi issue for LG G4, ppl suggested several solutions but none really worked. Wifi connection suddenly drops, and also takes a considerable amount of time when waking up from sleep. It gets very annoying when I am on a voip or hangout call.
No it's not my router or my phone. Because it's the same on my home and work network, where other devices just work fine. Also I don't have any of those issues on CM12.1 rom. CM is quite nice on LG G4 but having to be using it on CM is not an option, as I lose the camera.
Besides I didn't pay the money to purchase a flagship device to use it on a different rom.
So, that's it. LG better fixes it on the Marshmallow, otherwise Good Bye LG.
Click to expand...
Click to collapse
Not sure if you seen in the g4 dev section there is a flashable zip for a camera now. I'll never go back stock.
It's your phone... Those problems don't exist for everyone.
Sent from my LG-H811 using Tapatalk
Video recording not working after rooting.
Someone help please! I after rooting my LG G4 h811. My video recording stopped working. My snapchat videos will also not load. I what is the problem and what is can I do to fix this?
Crispy0707 said:
Someone help please! I after rooting my LG G4 h811. My video recording stopped working. My snapchat videos will also not load. I what is the problem and what is can I do to fix this?
Click to expand...
Click to collapse
Did you just root, or are you using other apps that uses root access? Did you uninstall or delete any system app?
It's very unlikely that rooting would break the camera. Try unrooting.. Super Su has the option to unroot in its settings. If doesn't work you may have to do a factory reset.
suhridkhan said:
Did you just root, or are you using other apps that uses root access? Did you uninstall or delete any system app?
It's very unlikely that rooting would break the camera. Try unrooting.. Super Su has the option to unroot in its settings. If doesn't work you may have to do a factory reset.
Click to expand...
Click to collapse
I rooted and installed wtrp, the first app I opened was snapchat and I was not able to open video snaps or make my own. I thought it was the app being supervised and I didn't check the camera app recording. I later installed apps for root like xposed installer to obtain snapprefs, but the problem continued to appear. After the download of a few apps and mods for root. I downloaded instagram and I was still not able to record videos. Finally I opened the camera and it was the same problem. I unrooted my phone and the video recording is working. I will root again and only test the camera app after root and after each app and mod I added before. I did try the factory reset and no luck.
Crispy0707 said:
I rooted and installed wtrp, the first app I opened was snapchat and I was not able to open video snaps or make my own. I thought it was the app being supervised and I didn't check the camera app recording. I later installed apps for root like xposed installer to obtain snapprefs, but the problem continued to appear. After the download of a few apps and mods for root. I downloaded instagram and I was still not able to record videos. Finally I opened the camera and it was the same problem. I unrooted my phone and the video recording is working. I will root again and only test the camera app after root and after each app and mod I added before. I did try the factory reset and no luck.
Click to expand...
Click to collapse
Since you already got twrp up and running, I can try MicroMod777's stock rooted debloated rom.
Never had problems with my H811 even installed different ROMs from LP to MM and back. Never had hardware issues.
My only problem with the h811 is the stupid gps not shutting off and killing the battery, fixed by app ops
I'm stock everything and my notifications have basically just stopped working out of no where. I've tried every solution there is on the web to fix it except a factory reset - is this what it comes down to? Do I have to factory reset every few months just to keep the phone running normally? That's not really ideal.
partylikeaninjastar said:
It's your phone... Those problems don't exist for everyone.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
this
I sometimes get the warning, no face detected, regardless of the light I am in. It once suggested I restart if I get this problem. Is it just my device?
ekerbuddyeker said:
I sometimes get the warning, no face detected, regardless of the light I am in. It once suggested I restart if I get this problem. Is it just my device?
Click to expand...
Click to collapse
I'm leaving this here to assist others. From a search: Turns out it is from a conflict with WhatsApp. If you have this problem, remove the permission for WhatsApp to access the camera, then return it when it next asks. It fixed it.
Update. It's not WhatsApp. Still having intermittent issues. Anyone have ideas?
Same here. Yesterday out of 20 tries it worked once. I am close to say that their implementation of face unlock is utterly crap. It works badly most the time, no matter what lighting situation my face is in.
EDIT: After I wrote this I tried it again, same problem: "No face detected".....
I let the phone sit at the same position and didnt move, rebooted and it worked. This must be some kind of bug.
I think it's related to a 3rd party app
Agreed, I have no problems.
ekerbuddyeker said:
I think it's related to a 3rd party app
Click to expand...
Click to collapse
hmm, the questions is what app? I have installed quite a bunch....
I don't have much problem with it, as long as it's decent light.
Sent from my SM-N950U using Tapatalk
Good afternoon,
I have had a Nokia 8 for a few weeks now and have now found that my microphone only works during calls. While I'm on the phone everything works normally but in all other apps nothing happens, e.g. in Whatsapp you only hear a short crack when you hear a voice message and then nothing, although you have said something (see attachment), also other apps that use the microphone like the Google Home App or a guitar vocal app don't work. Of course the permissions are set correctly for all apps but apparently this has no effect (see attachment). I've already written with Nokia Support, but after 14 mails about permissions, emptying caches and doing softresets they couldn't help me. Finally I was told to wait for the next Android update and hope that my problem was fixed there, or I should send my phone back to the dealer. My hope now is that one of you has an idea what could be the cause of the problem.
Thank you for your time!
- Joeigel
Attachments:
picload.org/view/dclcpodg/screenshot_20181201-165257.png.html
picload.org/view/dclcpodr/screenshot_20181201-165237.png.html
Audio Message from Whatsapp:
instaud.io/30ZI
Hello to everyone there,
I have next problem on my Nokia 8:
When somebody calls me or when I call someone on viber, I turn on speakers and other side can't hear me. Also when I put it on video call the same issue conitnuous to take. Regular GSM calls or viber VoIp calls works great as well as video calls with headphones.
I open ticket to a viber about this problem, and they told me I need to contact my manufacturer.
Yesterday I installed an Android pie from beta labs, but the problem still exists. How do you think the problem is hardware?
ratola said:
Hello to everyone there,
I have next problem on my Nokia 8:
When somebody calls me or when I call someone on viber, I turn on speakers and other side can't hear me. Also when I put it on video call the same issue conitnuous to take. Regular GSM calls or viber VoIp calls works great as well as video calls with headphones.
I open ticket to a viber about this problem, and they told me I need to contact my manufacturer.
Yesterday I installed an Android pie from beta labs, but the problem still exists. How do you think the problem is hardware?
Click to expand...
Click to collapse
Hi ratola,
you can dial *#*#372733#*#* for a hidden FQC test menu, here you can test each mic seperated, i guess in your case it's the second mic in the top-speaker.
- Joeigel
Joeigel27 said:
Good afternoon,
I have had a Nokia 8 for a few weeks now and have now found that my microphone only works during calls. While I'm on the phone everything works normally but in all other apps nothing happens, e.g. in Whatsapp you only hear a short crack when you hear a voice message and then nothing, although you have said something (see attachment), also other apps that use the microphone like the Google Home App or a guitar vocal app don't work. Of course the permissions are set correctly for all apps but apparently this has no effect (see attachment). I've already written with Nokia Support, but after 14 mails about permissions, emptying caches and doing softresets they couldn't help me. Finally I was told to wait for the next Android update and hope that my problem was fixed there, or I should send my phone back to the dealer. My hope now is that one of you has an idea what could be the cause of the problem.
Thank you for your time!
- Joeigel
Attachments:
picload.org/view/dclcpodg/screenshot_20181201-165257.png.html
picload.org/view/dclcpodr/screenshot_20181201-165237.png.html
Audio Message from Whatsapp:
instaud.io/30ZI
Click to expand...
Click to collapse
Hi Joeigel, unfortunately I have the same issue (and story regarding contacting support). The only way I can make calls via for instance WhatsApp is by using a handfree headset, or setting it to speaker-mode.
Waiting for the Android 9 release, if this isn't fixed with it, I'll send it in for warranty.
I do have another issue with the phone, and that's when I unlock my phone using the fingerprint scanner, 1 out of 4 times or so, the phone enables split screenmode. Do you (or someone else here) have similar experiences. It's quite annoying.
Update: Installed Pie, and no improvement. Issues still persists. Returning the phone today.
Sorry for the late response, my phone is also on it's way back to GB...
Joeigel27 said:
Sorry for the late response, my phone is also on it's way back to GB...
Click to expand...
Click to collapse
Ok, just got an update from the repair-center, they replaced a part and it should work OK now. Curious to see what they did and if it's resolved. Have to wait until it's shipped back. But keep us also posted about your progress
Off-topic: another issue I sometimes experience is when I unlock my phone with fingerprint, it sometimes switches automatically to the split-screen mode. It happens quite often and it's a bit annoying. Did you experience something similar with your Nokia?
odyon said:
Ok, just got an update from the repair-center, they replaced a part and it should work OK now. Curious to see what they did and if it's resolved. Have to wait until it's shipped back. But keep us also posted about your progress
Off-topic: another issue I sometimes experience is when I unlock my phone with fingerprint, it sometimes switches automatically to the split-screen mode. It happens quite often and it's a bit annoying. Did you experience something similar with your Nokia?
Click to expand...
Click to collapse
I didn't experienced something like this. Did they send it back to you yet? Maybe they fixed both... ^^'
Microphone issue here too.
Internal mic on front facing camera is the culprit. I noticed a few weeks back that my 'ok google' hotwords were no longer working. This became a problem after I installed the december security patch. I rolled back to the november security patch and this did temporarily fix the issue, after I had gone through the initial setup of the phone, my 'ok google' hotwords worked, until i went to use the camera to see if the issue still existed... unfortunately it does. Contemplating rolling back to july to see if the issue is resolved, or trying to move forward and installing pie.
nagesco said:
Microphone issue here too.
Internal mic on front facing camera is the culprit. I noticed a few weeks back that my 'ok google' hotwords were no longer working. This became a problem after I installed the december security patch. I rolled back to the november security patch and this did temporarily fix the issue, after I had gone through the initial setup of the phone, my 'ok google' hotwords worked, until i went to use the camera to see if the issue still existed... unfortunately it does. Contemplating rolling back to july to see if the issue is resolved, or trying to move forward and installing pie.
Click to expand...
Click to collapse
Could any up or downgrade fix it?
Joeigel27 said:
Could any up or downgrade fix it?
Click to expand...
Click to collapse
I've tried going up or down, I have oreo and pie on each of my A/B partitions and it does nothing. When i downgraded to oreo it worked for awhile but updating the google app or some sort of background service broke it again. Its definately mic 3 that has a fault, it has background interference noise when i do the test, it also occurs when recording video with the front facing mic on camera, the problem with the mic never goes away, after up/downgrading, I can't say whether this is related since it works prior to updating. rolling back/disabling doesn't solve the problem for the apps. Microphone/earpiece holes are clean and undamaged.
nagesco said:
I've tried going up or down, I have oreo and pie on each of my A/B partitions and it does nothing. When i downgraded to oreo it worked for awhile but updating the google app or some sort of background service broke it again. Its definately mic 3 that has a fault, it has background interference noise when i do the test, it also occurs when recording video with the front facing mic on camera, the problem with the mic never goes away, after up/downgrading, I can't say whether this is related since it works prior to updating. rolling back/disabling doesn't solve the problem for the apps. Microphone/earpiece holes are clean and undamaged.
Click to expand...
Click to collapse
After further testing of this issue, the 'OK Google' issue is still present, if I want to ask google assistant 'ok google' the microphone barely picks up anything or even my question, practically screaming into the microphone is the only way to activate it, this matches with the results on my google activity, listening to my recordings of my queries shows evidence that the microphone sensitivity is way too low.
HOWEVER, when using google assistant by means of pressing the microphone and then asking the question, the result is clear and understandable and doesn't suffer from volume issues, I can't pinpoint if this is an issue with the Nokia specifically, it is not a problem with any other application that uses the microphone.
Having the same issue with Mic 3. It means I can't use it in speakerphone mode during calls or in Skype. It doesn't prevent me from using the Google assistant though.
My smartphone was sent in and repaired (complete motorboard replaced). During the time it was gone Android 9 came out, so I'm not sure if it was the repair or the software update.
But it works again without any problems
Kind regards
Joeigel
So here's a wierd one. Have a SM-N960U1 on Android 9. Everything's been fine but as of last Friday every time it pairs with a Bluetooth device (headphones, car, etc.) it starts calling itself? I re-paired all devices, turned BT off and back on, restarted phone, etc., but this behavior persists. Music is also terrible during this time, but realized by accident when I press Device Care widget to optimize phone the BT device announces 'Call Ending', and music again sounds great. However there's no record of any outgoing call in Phone App. I didn't realize what # was being called until I got in my car and saw it was dialing itself, but again, this phantom call does not show up in Recent Calls history? Any ideas?
Ugh... Same
Same man. Just letting you know you're not alone and following for a resolution.
smart lock on?
Removed all trusted devices from smart lock and it still happened.
Did a support Chat with Samsung, they recommended a soft reset (Vol dn + Power, similar to a Battery pull) which solved it temporarily when I turned on Bluetooth but since then the bug continues. No new updates or setup changes I'm aware of before this started happening. They also suggested running in safe mode and disabling Apps one at a time to see if the issue can be isolated (aren't these supposed to 'be' smartphones? Evidently there's no log of what it's doing) Will try that or another Chat session when I get some time again.
Ive been having this issue for a week or so as well. Every time I get in my car, I have to end the call. Its got to be a software update that caused the issue.
I'm thinking now it could be related to Bixby. I don't use it (remapped to google assistant & flashlight on long press using bxActions) but I recall I allowed it to update recently in case it gets better in the future.
Same issue here ... Sprint Note 9 on Pie ... Bluetooth headphones even has issues. I have to make a phone call and end it to be able to control volume from the headset (changing it from in-call audio to media audio).
Yup, those are the symptoms. Bluetooth headphones sound terrible and has no device control until the 'phantom' call that starts on it's own is manually ended.
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
ogretech said:
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
Click to expand...
Click to collapse
Awesome tip!
I use Ring Central App for keeping up with work phone messages. A few days ago started the phone in safe mode and had no BT issue, then back in 'un-safe' mode at first it didn't happen but cycling the headphones on and off it did occur again so I was faced with narrowing it down to which App. After reading your post I went into RC Phone settings, Mobile App Settings, Default Launching, and turned off 'Call From Android Dialer' since I don't use that feature and so far no issue!
Thanks for the tip, hopefully this setting change continues to solve this.
Still good after a couple days and weekly auto phone restart (Sat @ 3:00 AM). So nice not to have to end a phantom call that interrupts the stereo after 10 seconds every time I start the car.
Thanks again for the RC Phone tip.
You guys are definitely not alone. I unfortunately do not use the ring central app so I am not sure what is causing it for me...
I'm on the note 10 and have only had this problem pop up recently out of nowhere... I have no idea what could be my problem as I do not have RC Phone installed on my phone
Possible Solution
Hey, I posted a few days ago about having this same problem and not being a user of ring central. I got to thinking and tested this out. The Voxer app was the issue for me. I uninstalled this app and I haven't had any problems since. I am not sure about why the most recent Voxer update caused my phone to start doing this but I hope this helps someone else.
Possible Solution
Some may have tried this. Let me know.
My wife has Honda Hands Free 2016. In the past 30 days it started this same freaky behavior as all of you list.
She has a Samsung s9+.
She also has had Voxer installed on her phone and has had for many years. I will have to check to see if a recent update hit.
But, this is what seems to work for me at this point........
Told Honda Hands Free to completely forget her s9+. Then disabled blue tooth on the s9+.
Turn Entire Honda car off.
Turn Honda back on, told it to connect to my Samsung phone SM-J320A. Verified Honda was connecting properly to my SM-320A with no issues. All good with no freaky behavior. As info Voxer is not installed on my SM-320A.
Turned bluetooth back on s9+ then added the Samsung s9+ back to Honda Hands Free and told it to completely forget my SM-320A.
So far this has stopped the freaky behavior. If it comes back I will update here and then I will try uninstalling Voxer.
Anyone had this problem? The setting is toggled in the menu, it makes a noise on key press, but the call recipient doesn't seem to receive it.
Had this problem with my last handset (P20 Pro), and now realise I have the same issue again.
I will contact Pixel support tomorrow when they're open again, and currently on a slow web chat with Vodafone.
Just tried a few things, appears that they do work on ear piece, but not when on loudspeaker. Vodafone suggests the phone is faulty. I'll speak to Pixel support tomorrow.
If anyone has a few minutes spare, could you see if you have an issue with this?
mushtafa said:
Just tried a few things, appears that they do work on ear piece, but not when on loudspeaker. Vodafone suggests the phone is faulty. I'll speak to Pixel support tomorrow.
If anyone has a few minutes spare, could you see if you have an issue with this?
Click to expand...
Click to collapse
Has the same issue and came up with the same results. Speakerphone caused it to fail. I think the tone is being heard and picked up at the same time maybe. Switching to ear piece solved it.
Seems a very odd 'bug'. Wonder if there is a fix for it?
Used the Pixel support chat thing today.
I was told to force stop the phone app, uninstall all updates, and clear the cache from the app.
Install update for Phone app from Play Store, reboot phone and test.
Tried it twice and working at the moment.
Might help someone out.
After having this issue for over a year, I finally found a (so far) permanent fix. Update/change your APN settings on the phone. I am a T-Mobile customer so I went to the site to get the correct settings. I added a new one and everything has been going well.
I'd tried every fix I could find via googling, but nothing stuck longer than a day. It's been over a week and I'm still working. I hope this helps someone because this was the worst issue to have in this current video meeting era.