Hello developers
So far I hadn't a reason to use Alexa or Google Assistant. As Motorcycler and owner of a new SENA 50R, which supports Headset-Speech-Commands ("Hi Sena" and "Hi Google") I found this technology after all practical. Especially on a motorbike where you can't touch a smartphone because this is in a tank bag and you wear gloves. But I have the same problem as many others here. As soon the display is turn off, then Google Assistant is no more responding. I tried to disable energy saver for this app, create a profile (which automatically trigger at connect with the headset) with disabled lock screen. Nothing helps. (the option "allow Bluetooth requests with device locked" is enabled). Apparently this has worked in the past.
What the hell make this for a sense. Why should I use speech commands if I have to press a key that the phone is at least at lock screen!???
Should this fix google itself or could the Lineage-Team correct this behaviour?
Thanks
Now I just tried it on a Samsung Galaxy S20 with Stock ROM. It works right away. Could it be a hardware restriction? (I'm using a Galaxy S6)
Related
I've searched a couple hours now and there is a demand for the "Ok google" detection while the screen is off and the phone is not charging. There ar multiple topics about this on different places:
http://forums.androidcentral.com/samsung-galaxy-s7/661999-ok-google-screen-off.html
https://www.reddit.com/r/GalaxyS7/comments/48uv2q/no_ok_google_while_screen_off/
https://forum.xda-developers.com/galaxy-s7/help/force-ok-google-t3396305
Most of these topics are created/commented by users, not devs. While there is the "fake charging" method described here (http://www.droidviews.com/force-ok-google-detection-screen-off/) it has many drawbacks and is a very ugly solution, mostly for older phones.
The S7 should have some hardware allowing it to "hear" in low power state while the screen is off, we can see that on the S Voice application, that works well but isn't nearly as good as Google Voice. Some google phones, like the Nexus and the Pixel, support this functionality.
I know this forum is full of phone devs, I'm a programmer myself. How could we make 'ok google' detection when the screen is off and the phone is not charging?
If you got the Google Assistant then you will be able to do that.
OrenGazala said:
If you got the Google Assistant then you will be able to do that.
Click to expand...
Click to collapse
I tried and no dice: screen off, no detection. (unless charging)
changing build.prop to pixel so the system thinks that we're using a pixel device which has that option ?
I have Google Assistant installed and it responds to "Ok Google" from lock screen being off and not charging??
I flashed the Google Assistant enabler onto my Galaxy S7 flat, running Nougat.
The one that doesn't require changing device ID to Pixel device or altering your language, or installing all the Beta Google apps. Works beautifully.
windowsdan4216 said:
I have Google Assistant installed and it responds to "Ok Google" from lock screen being off and not charging??
I flashed the Google Assistant enabler onto my Galaxy S7 flat, running Nougat.
The one that doesn't require changing device ID to Pixel device or altering your language, or installing all the Beta Google apps. Works beautifully.
Click to expand...
Click to collapse
download link ?
Sorry for late response:
https://forum.xda-developers.com/general/general/android-7-0-google-assistant-t3535257
This is the post. Just flash it using twrp and you get Full Google Assistant without any issues or having to change your device name or language etc
I tried flashing this but it does not work. Screen off = no detection unless charging.
raphadko said:
I tried flashing this but it does not work. Screen off = no detection unless charging.
Click to expand...
Click to collapse
I can confirm this. Still looking for a way to use it as I use my phone to do work while driving my bike a lot. Not very user friendly to wake my phone with a button press..
Hey guys !
I noticed that the Google assistant (Hey Google) doesn't work when the screen is off. Is this caused by some kind of hardware limitation or can it be fixed with an update ? The OnePlus 8 Pro for example (and many other phones) does offer the screen off Google Assistant.
Mines works while screen is off, use just have to select it in the settings options in google
That's weird. In my settings menu for the Google assistant I can activate "Hey Google" but the description says: "Say Hello Google while the screen is activated to activate the Google Assistant at any time"
And it works as stated in the description ( No Screen Off Assistant). My Region is Europe/Germany btw.
Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Vimes14 said:
Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Click to expand...
Click to collapse
.
I just tried it myself and turning over the phone definitely muted the incoming call (with the phone open or closed) Also the palm gesture worked (cover screen only) but that was slightly more difficult as you really have to cover the whole screen for a couple of seconds.
I also used AndroSensor (and another app) and noted the proximity sensor was present but wasn't showing a reading. Obviously it is working (and works when holding phone to ear by turning screen off for example).
So I am not sure why it's not working for you.
.
apprentice said:
.
So I am not sure why it's not working for you.
.
Click to expand...
Click to collapse
Thanks for checking.
Did some more testing, the flip gesture seems to be working for incoming calls with the Google Phone app, and alarms created by the Samsung Clock app, but not the Google Clock app or Calendar notifications. Using the Google Phone app once the call is established, then the screen does turn off when held close to a head when folded. So seems like the sensor is working, in some situations, which means it is probably software related, rather a hardware defect. I really don't want have to reconfigure my setup up again.
The Google Phone app also has a setting flip to mute, which was not set. So I flipped that to true.
I had previously written a Tasker profile to mute everything (enter Do Not Disturb) on a Pixel 3XL, before Google implemented it at the OS level, so I may try that here.
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
apprentice said:
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
Click to expand...
Click to collapse
I think the problem is that the Samsung implementation is to hook into a small subset of their applications to do a local mute, where as Google implementation just invoked Do Not Disturb, which meant every application would mute, assuming they are compliant. I think DND was slightly flakey on OS9, but from OS10 onwards it was rock steady.
To bring clarity to my local behaviour, I enabled my Tasker method that engaged DND when the phone is flipped. Works in both folded and unfolded configurations. As a bonus with Join, I have a method that automatically distributes DND to my other devices.
Hi all,
Recently got the watch 4 and this has been mind boggling me since the day i got it.
Is there any way to have Google Maps update the location on the watch with the screen of on the phone?
Navigation works fine, but as soon as i turn off the screen on the phone to put it my pocket, navigation stops updating on the watch. I guess it also stops updating on the phone as the screen is off.
I have tried several things, give location access at all time for maps on both phone and watch. Also removed any battery restrictions or power saving features for maps. Also checked the sleep lists in device care on the phone, but maps is nowhere to be found there at all and cant be added.
I did write with Samsung support and they did actually confirm that this is not a feature and that phone screen has to be on/phone unlocked for navigation to keep updating..
Is there any workaround for this at all?
Phone is a a52s 5g and it is already going mental sometimes in the pocket even when locked. God knows how many pocket screenshots I have of emergency dial with endless of numbers input.
Thats most likely a samsung/oneui problem rather than android's/watches fault.
Location updates perfectly (tho with a bit of delay) with my redmi note 7
Yes I believe so to, so maybe it was better to post this at the a52 forums. Just thought maybe someone was in the same boat as me here.
Been a happy xiaomi user for years, why did i jump on the galaxy bandwagon now
When I carry the Xperia in my pocket and then take it out, the phone is usually in flight mode or silent because the display somehow activates in the pocket, and since the status bar can be operated despite the lock screen, the quick settings activate themselves.
Is there any option that does not allow the status bar to be operated when the screen is locked?
Had already written to Sony support, but only received the statement that probably the distance sensor has an error.
But I can not imagine with the best will in the world because the phone otherwise works fine.
Translated with www.DeepL.com/Translator (free version)
it's an issu that othe use having too from what i red
u must be on Android 12 i think...i'm still on 11 and i'm not facing these problems and never had at all
There's an app called "Shouko" that enhances the 'prevent accidental touch' feature, as well as a few other really cool features. I was having this same issue until I tried the Shuoko app. [(https://github.com/ivaniskandar/shouko) github user ivaniskandar did a dope job on this] It says you have to grant some permissions "manually with ADB or root," so either way you need at least some know-how about command line and ADB (maybe also fastboot, if you go root). I had root, so I didn't have to mess with the ADB strategy, but it says there's a guide in the app.
I also had my camera turning on ALLLL the time taking pictures of my pocket, heating my phone, and kiiiilllliiiing my battery. I figured this was the camera button, but turned out to be Settings -> System -> Gestures -> quick launch camera. It hasn't happened once after turning that off.
as another layer of redundancy on top of what Lunalsmojo wrote, you can also turn phone so screen faces outwards, that way your skin isn't activating the capacitative touch screen.
Thanks for the info. I will try to keep the phone upside down in my pocket.
If that doesn't help, I'll install the Shouko tool and see if I can get it to work via ADB.
I haven't had the problem because I carry my phone in a holster.