Related
Hi there.
I am pretty new here & didn't read up on billboards yet, but I had something very strange happening to me yesterday. The phone automatically downloaded a 'Google Voice Search'-update and since it's installed, I keep encountering problems.
The most annoying one - the camera doesn't work anymore. If I click on the icon, the screen just turns black and remains like that until I either hit the HOME button - or if I wait long enough - I get an Force close-popup.
Furthermore, after calls, the screen also turn dark sometimes, but turn back on after a while. Other that that, everything works fine as before.
Am I the only one?
Does anyone know whether it's update-related or whether it's just a coincidence. Everything else works fine, so I doubt it's something else.
Is there a way to reinstall the camera app without having to flash the phone. As I said, I am a newy & don't want to end up with a brick.
The malfunction started only yesterday after the auto-update. I am on a Spanish GSM network, but I guess that's not of much relevance. The phone is running Gingerbread 2.3.4.
Tks for any suggestions.
t.
OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?
I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.
I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification
disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...
Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.
I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.
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
This happened to me yesterday and that was completely by mistake. I had the marshmallow update for sometime now and not experienced any major issues other than the random heating (while charging) and some drains at times.
The major issue occurred to me yesterday, when my mutli-window function got disabled by some how and then the phone did not respond to any of my finger touches anywhere on the screen. I have a password lock screen and that too stopped working because the touch response system was not usable. After a struggle for many hours and one sleepless night, the next morning, when I was just thinking of sending the phone to the service center; it just came to my mind and I tried out the SPen and that was working just fine. :victory:
So, using SPen I unlocked my phone and tried to understand what changed. As I normally enable a few functions on my phone, it easily came to my notice that the multi-window function was disabled. So, again using the SPen I enabled it and Voila!! the finger touch started working back.
This is pretty crazy and never experienced this before the marshmallow update.
PS: Even the backlit hard buttons ( left one, home, back right ) had stopped working for me for that instance.
Anyone has any clue on it?
Did you do a reset after the upgrade?
donalgodon said:
Did you do a reset after the upgrade?
Click to expand...
Click to collapse
Yes, as I said the upgrade was not the issue, the issue is disabling "multi-windows" made the phone unusable for sometime till I enabled it back and it started working fine. The issue is something with that "multi-window" on marshmallow update.
I don't intend to go back to older version now.
vaibhavgaikwad said:
Yes, as I said the upgrade was not the issue, the issue is disabling "multi-windows" made the phone unusable for sometime till I enabled it back and it started working fine. The issue is something with that "multi-window" on marshmallow update.
I don't intend to go back to older version now.
Click to expand...
Click to collapse
With all due respect, there's no way to know if the "upgrade was not the issue" unless you actually did a wipe/reset to rule out the crud remaining particularly between major version number leaps.
I tested what you described as the cause of your problem on my wiped/reset device and the problem is not happening for me. Enabling and disabling multi-window causes no issues in my case.
IT might be worth doing a wipe/reset if you haven't. (It's not clear from your response if you have or not done so).
donalgodon said:
With all due respect, there's no way to know if the "upgrade was not the issue" unless you actually did a wipe/reset to rule out the crud remaining particularly between major version number leaps.
I tested what you described as the cause of your problem on my wiped/reset device and the problem is not happening for me. Enabling and disabling multi-window causes no issues in my case.
IT might be worth doing a wipe/reset if you haven't. (It's not clear from your response if you have or not done so).
Click to expand...
Click to collapse
I think I have been more clear and transparent, if you says the multi-window is not an issue then it may be something else which I am not aware of. Though I know that over that particular day nothing new was installed on my phone (so I doubt it can be other software).
Why I am sure its the marshmallow update is because the older version I had tried disabling the mutli-window and the phone worked well, only with the marshmallow update the phone got weird (that too with that multi-window disabled) and enabling the multi-window made it work, so that's my point.
To answer you question on "Did I do a reset", the answer is no I did not, I rebooted (and shut) it couple of times thinking its overloaded but it did not change my situation. Only after I realized that SPen was working fine I could unlock the phone and enable the mutli-window and there after it started responding well to my finger touches too. It's working good today as I write this response. I can once again disable mutli-windows and check if it goes weird again. Let me know if you want me to do that?
Regards.
I recognize that doing a reset can be a pain, but it's probably worth it in the long term. It's up to you, but if it were me, I'd do a reset and start fresh.
When you make major version leaps, the chances of problems increases dramatically over point releases. (i.e. going from 5.x to 6.x is bigger than going from 5.0 to 5.1)
I don't know what might have happened, but this morning, I tried to connect my Phone to WiFi, and for some reason, it wouldn't. The WiFi toggle button that you see when you pull down the Notification Bar, now that WiFi button keeps turning on and off constantly. The time it takes between each toggle (on to off or off to on) is just about 0.5 - 1 sec. This is crazy. I can't connect to my WiFi.
I googled for solutions, no luck. I hard reset my Phone, no luck still. I wiped Partition Cache too. I entered into the Safe Mode, the same behavior happened. It's weird. It's like my Phone is possessed or something. A virus maybe?
Any input would be much appreciated. My phone is running the latest Firmware from T-mobile. And I got the update maybe 1-2 weeks ago and it had been working fine until this morning the issue started.
My phone just started doing this as well. Wifi keeps turning off and on. If I want to keep it off I have to restart my phone. If I want to use the wifi I have to manually toggle it from the wifi settings. Just weird it started doing this just recently. Maybe an app we both have installed?
I think I've found the issue. Sadly only after 3x reformatting the phone.
Go to Settings, Location, then click on Improve Accuracy, then turn off WiFi and Bluetooth Scanning (actually just the WiFi scanning would do the trick, but I decided to just turn off both of them). I suspect an update to one of Google system apps might have caused the phone's WiFi to behave weirdly like this. For the past 2-3 years I've had this phone, it had been fine with these two options turned on. It changed yesterday.
Let me know if this solution works for you.
febzz88 said:
I think I've found the issue. Sadly only after 3x reformatting the phone.
Go to Settings, Location, then click on Improve Accuracy, then turn off WiFi and Bluetooth Scanning (actually just the WiFi scanning would do the trick, but I decided to just turn off both of them). I suspect an update to one of Google system apps might have caused the phone's WiFi to behave weirdly like this. For the past 2-3 years I've had this phone, it had been fine with these two options turned on. It changed yesterday.
Let me know if this solution works for you.
Click to expand...
Click to collapse
Haha I was about to post this solution as well! Turning off the wifi in location accuracy fixed it. You're right about probably some Google app is causing this as this hadn't happened before yesterday. Sorry you had to format your phone to find this out...hopefully google or samsung can fix this from their end.
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
muzzy996 said:
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
Click to expand...
Click to collapse
I just uninstalled wear and same issue persist. Last app from Google that I did an update on was Google home...formally known as chromecast.
---------- Post added at 10:30 AM ---------- Previous post was at 10:04 AM ----------
I just uninstalled Google home and the issue went away.
I do have Google Home and Android Wear installed as well. I checked the Google Home App Play Store Page and someone commented there pointing out about the issue too.
febzz88 said:
I do have Google Home and Android Wear installed as well. I checked the Google Home App Play Store Page and someone commented there pointing out about the issue too.
Click to expand...
Click to collapse
Yup that was me leaving a comment haha
i have had exactly the same problem for a day or two. while disabling "location>improve accuracy>wifi scanning" stops the bug temporarily it doesn't really solve the problem. wifi scanning is an important location feature when navigating. in narrow streets or in buildings one usually does not have gps reception, also the wifi scanning technique for determining the devices location is usually faster and uses less battery than gps (how ironic).
this bug is extremely annoying. i am on an unbranded, unrooted s5 on 6.0.1 (g900f). i can not believe that this also happens with s7 and pixel phones, this is really ridiculous (see similar thread on androidcentral forum. can't post url because this is my first post). if anyone finds a permanent solution for this problem, please tell us!!!
androidschmandroid said:
i have had exactly the same problem for a day or two. while disabling "location>improve accuracy>wifi scanning" stops the bug temporarily it doesn't really solve the problem. wifi scanning is an important location feature when navigating. in narrow streets or in buildings one usually does not have gps reception, also the wifi scanning technique for determining the devices location is usually faster and uses less battery than gps (how ironic).
this bug is extremely annoying. i am on an unbranded, unrooted s5 on 6.0.1 (g900f). i can not believe that this also happens with s7 and pixel phones, this is really ridiculous (see similar thread on androidcentral forum. can't post url because this is my first post). if anyone finds a permanent solution for this problem, please tell us!!!
Click to expand...
Click to collapse
Do you have Google Home installed? After I uninstalled that the wifi issue stopped
alanmv567 said:
Do you have Google Home installed? After I uninstalled that the wifi issue stopped
Click to expand...
Click to collapse
no, i do not.
muzzy996 said:
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
Click to expand...
Click to collapse
Is it your GPS or the Compass? If it can still detect your location but when you use, for example, the Google Maps Navigation, it couldn't really detect where/which direction you're going then it's probably just a compass issue. All you need is some calibration.
I fixed my friend's phone compass issue (and she thought her GPS was broken too) last week. The easiest way to calibrate: just download the GPS Status app and tap on the Calibration option and follow the instruction there.
Always try to calibrate your compass first as the first possible fix whenever you think your GPS is starting to go crazy, it might help.
Go to location>improve location>unchecked wifi scanning. It just worked for me
Uninstalling android wear seems to have worked for me.
febzz88 said:
Is it your GPS or the Compass? If it can still detect your location but when you use, for example, the Google Maps Navigation, it couldn't really detect where/which direction you're going then it's probably just a compass issue. All you need is some calibration.
I fixed my friend's phone compass issue (and she thought her GPS was broken too) last week. The easiest way to calibrate: just download the GPS Status app and tap on the Calibration option and follow the instruction there.
Always try to calibrate your compass first as the first possible fix whenever you think your GPS is starting to go crazy, it might help.
Click to expand...
Click to collapse
Definitely not the compass, been through the calibration process. Attempted many fixes including special GPS settings and utilities. At times the phone can sit there with screen on for over 10 minutes without acquiring a single satellite. I'm thinking hardware issue, possibly contacts for the antenna. In any case, not relevant to this thread...
I rebooted into recovery and wiped both CACHE and this fixed the issue. I did not change any settings in any apps either.
DirtySant0 said:
I rebooted into recovery and wiped both CACHE and this fixed the issue. I did not change any settings in any apps either.
Click to expand...
Click to collapse
I had tried this prior to reformatting my phone and it didn't help. I then wiped the cache again and reformatted the phone; in fact I reformatted and cleared cache 3x because the issue kept coming back after I reinstalled apps again. This is weird, the situation and resolution vary a lot from one user to another. Then I simply turned off WiFi Scanning under Improve Accuracy in Location, and the issue went away.
WHEW! Uninstalling Wear and Home did it for me. For now, anyway. I "fixed" it this morning by toggling Ultra Power Saver on and off, and it worked all day until I came home from work. Then nothing helped until I found this thread. Changing GPS settings didn't do it for me, but I'm still on Lollipop so my location settings are a little different.
Thank you, Febzz and Alan!
Google home was the issue!!
Sent from my SM-N910T using Tapatalk
Changes in router's Wireless Security had caused it in my case
This is old thread but still I am posting this solution as it could be useful tip for someone in future.
I had this issue and was causing me real headache. I initially thought it was hardware failure of my phone but later I found reason is something else.
For some reason I had changed Wireless Security of my WiFi router from WPA2 Personal to something else (I guess WEP).
That was causing my phone (intex cloud 4g) often to turn on and off WiFi on its own. I changed the Wireless Security back to WPA2 Personal and phone is now back to normal (not turning WiFi on and off on its own)