Ok google was working beautifully when I got my phone, screen off etc.
Now it only works consistently when I am in the google now screen. I have turned s-voice on and off without any change.
I cant find any conflicts and was hoping someone would tell me the solution. I love google now and its always on capability.
Thanks!
Related
I installed Google Goggles from the Martket the other day.
Its loads but after going through the first couple of screens it disappears (I guess it minimizes as i dont get any force close message).
Is anyone else having the same issue or is it working for you?
Same issue here im afraid.
Rgds
Lok
It also happened to me, it worked fine until I upgraded it
Same here too.
It was working on mine originally but since I updated something it now fails as you describe.
I was messing about using it with a USB camera which worked fine btw.
I posted about this on Modaco and some ignorant tw**t posted a sarcy reply about why would I want to use it anyway with a front facing camera
Probably doesn't work unless you have a fake location set (like Google Earth).
Tried with fake my location running still not working!
Hello everyone. I've done a few searches on here but haven't found this exact problem. Relevant details without extra background info are in bold.
My wife and I each got an S4 with Sprint's recent BOGO promotion. My phone has had no issues. It came with MDL in the box, which I updated to MF9 via OTA, flashed TWRP via Heimdall in Linux, rooted, and installed the hotspot mod.
Her phone - completely stock MF9 and new from the store - has had problems, one of which I've so far been unable to fix. (How I wish it were mine. I develop for Android, but this is much more of a pain for her.) Hers already had MF9 at the store. It had the Google Services Framework/Core Apps runaway process issue with heat/battery drain from the start - which I fixed. However, it also has unresponsive sensors for ~3 seconds when receiving a call. It's almost as if there's some lag in activating the sensors. The phone is otherwise snappy with no other lag noted.
- Hard reset has been tried.
- The touchscreen is unresponsive during this time, though the display functions.
- The gesture for answering (when enabled) also does not work.
- We haven't tried enabling the home key to answer, but this will be next.
I've seen this before with Android a good while back. It was an inherent problem with Gingerbread on many phones. Haven't seen it pop up in Jellybean at all. In trying to diagnose, I've ensured that all bells and whistles are turned off. No air gestures are on.
We'd really like to get it working as it should. Has anyone else experienced this? Any advice?
Many thanks!
I believe this is more of a stock software issue. I have had the issue since day one.
When I turned off svoice and some of the other added features most of the lag disappeared. Svoice is pretty good at creating lag as far as ive seen.
Voice response seems to create th lag as it is awaiting a voice command from you.
This is what I have noticed anyway.
Sent from my SPH-L720 using xda app-developers app
I tried a few random compass apps and none of them seem to work (the needle does not point to a fixed direction as I walked around). I tried this with and without wifi/data/location. Can anyone confirm this?
I really like everything else about the phone and I would hate to RMA this just because of the compass.
case-sensitive said:
I tried a few random compass apps and none of them seem to work (the needle does not point to a fixed direction as I walked around). I tried this with and without wifi/data/location. Can anyone confirm this?
I really like everything else about the phone and I would hate to RMA this just because of the compass.
Click to expand...
Click to collapse
I also have troubles with the compass. Tried calibrating it a few times, as per the guidelines Google give out. However it just doesn't seem to want to stick!
Anyone else confirm the issue?
Sent from my Nexus 6P using Tapatalk
I'm also having issues with the compass. Doesn't work as a compass should. Turning around 180dg the phone makes north 180dg from where it was before.
copong said:
I'm also having issues with the compass. Doesn't work as a compass should. Turning around 180dg the phone makes north 180dg from where it was before.
Click to expand...
Click to collapse
I still haven't been able to solve this, not sure if it's a software or hardware issue?
I've just managed to fix it, it was a calibration issue but I fixed it with a different calibration routine as the one in google maps did nothing.
Installed https://play.google.com/store/apps/details?id=com.brothers.compass
Then press the menu button at the bottom right. That goes straight into calibration mode with instructions.
copong said:
I've just managed to fix it, it was a calibration issue but I fixed it with a different calibration routine as the one in google maps did nothing.
Installed https://play.google.com/store/apps/details?id=com.brothers.compass
Then press the menu button at the bottom right. That goes straight into calibration mode with instructions.
Click to expand...
Click to collapse
I've managed to get it to work for a while, but the calibration won't stick after reboot.
Sent from my Nexus 6P using Tapatalk
Damn, same here. Anyone else?
No issues here.
There is a discussion on Google's forum at https://productforums.google.com/forum/m/#!msg/nexus/SK7gbrV5MhU/X4OdqoheBQAJ. Seems the 5X is also having the same issue. Post your problem there to hopefully help get it sorted out quicker.
Sent from my Nexus 6P using Tapatalk
After I finally got the November security update tonight, some of my Play store apps needed updating too. (I'll get to the point in a minute, I promise) One of those apps was Google Maps. I opened it & tapped on the location icon (so the image will turn as I do) & a pop-up came up stating that my compass was not correct & to turn it in several directions in succession to fix it. It may pop up for you too.
If you do not see that, do this: It asks you to hold your phone upright screen facing you (while in Maps) & fan it towards you then away, towards you then away. Then turn it in the air like the 4H queen wave, just twisting your wrist. Then while still facing you, rotate it to the left & right, like you're going to bang the sides of the phone on a table. Do each motion 4 times.
After doing that, the compass is dead on! Unfortunately, it doesn't hold the calibration after shutting the screen off though & backing out of Maps but it's a start without installing an app to do the same thing.
copong said:
Damn, same here. Anyone else?
Click to expand...
Click to collapse
Yep me too. Thank god for XDA. I was thinking I was the only one with no compass (although a 5 minute drive showed navigation works fine). It isn't a deal breaker for me because...
Nearly everything else is just good on the money, great display but not natural white (bit like the old AMOLEDs from the Note 2 that I have) with no pink or yellow hues, great sound (except in calls, loudspeaker only uses bottom to play out the audio), superb fast and crisp camera especially the FFC (but bad stabilisation in videos), beautiful design esp in the frost finish, phenomenal imprint scanner, very good battery life seeing as I'm coming from the venerable Z3 (but it can vary wildly, rogue apps perhaps), excellent build quality as mine doesn't have any QC nicks or rattling noises (apart from the camera lens, which is par for the course), bluetooth works without cutting off via 'cupping', Maps is locked at 60fps for the first time in Android history (and uniquely on this Nexus only), charging is quick and I'm glad it is type C (very convenient).
so i recently replace my mtxp screen and everything was working perfectly until one day i was watching a youtube video and tried using my navbar buttons and they were unresponsive..did everything from rebooted..clear cache..reinstall rom...same problem..its like the bottom of the screen is unresponsive and only works when screen is locked...
anyone else with the same problem/solution?
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
Hi, I have switched on the "Show touches" feature in the Developer options to see whether the screen is detecting touches in the bottom area of the screen: it actually doesn't. It is not an issue on the lock screen though but it is for the navigation bar. So, it seems it is the hardware that is acting up, after all...
I have found a thread about this issue with a workaround to increase the height of the navigation bar by xposed: https://forum.xda-developers.com/moto-x-style/help/navigation-buttons-issue-t3497985
I'll try either that or by installing a custom ROM that has that option built in - e.g. AICP 12.1 (Android 7.1) seems to have such setting.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049
Same problem here - at least in my case also a hardware issue after replacing a broken screen. Thought (as many did) it was software because TWRP, lockscreen etc works, but if you actually try touching only the downmost parts of the TWRP or lockscreen buttons, it won't react. "Show touches" from developer tools also shows touches being registered only just above the normal navigation buttons.
Like the title says, hotword detection used to work great, but in recent months seems to have gotten broken. I'd say it only works 30-40% of the time, where it used to be 90-95%. Even when it does detect the hotword, it will frequently fail to do anything. It will make the sound acknowledging that it is listening, but nothing will come up on the screen.
I've attempted to retrain/delete the voice model, tried reflashing the stock image. I'm trying to determine if it's something specific to my phone, or if this is a wider issue with the current build of Android. Based on how it fails to do anything, I'm suspecting this is a software issue rather than a hardware issue.
I'm down for any suggestions. This is a feature I use a ton, and would love to get it working again.
On a side note, I used to be able to long press the phone button on my wired headphones to activate the okay Google feature, but around the same time this stopped working, I lost the ability to do that. Anyone know why?