Develop Bugs

[Q] Wifi Calling Keeps Showing Up In Quick Settings

Normally I only have 5 Quick Settings icons enabled (Quick Memo, Wifi, Sound Profile, Data, and Bluetooth), however every time I reboot my phone, the Wifi Calling icon re-enables itself and pushes itself in between the Data and Bluetooth toggles, pushing Bluetooth off of the screen. I realize that it's easy to just go back into the 'Quick Settings' settings and un-tick Wifi Calling again, but it gets really annoying when I reboot multiple times a day. Does anyone know of a more permanent solution besides just un-ticking the box every time I reboot? If it helps, I am using the Gold edition G3 from Sprint and I'm rooted. This 'problem' has been going on since I got the phone.

Redpill42 said:
Normally I only have 5 Quick Settings icons enabled (Quick Memo, Wifi, Sound Profile, Data, and Bluetooth), however every time I reboot my phone, the Wifi Calling icon re-enables itself and pushes itself in between the Data and Bluetooth toggles, pushing Bluetooth off of the screen. I realize that it's easy to just go back into the 'Quick Settings' settings and un-tick Wifi Calling again, but it gets really annoying when I reboot multiple times a day. Does anyone know of a more permanent solution besides just un-ticking the box every time I reboot? If it helps, I am using the Gold edition G3 from Sprint and I'm rooted. This 'problem' has been going on since I got the phone.
Click to expand...
Click to collapse
Does the same on the 855 model with quick remote etc. It's an LG bug it seems (someone else has posted a similar thread iirc)

Redpill42 said:
Normally I only have 5 Quick Settings icons enabled (Quick Memo, Wifi, Sound Profile, Data, and Bluetooth), however every time I reboot my phone, the Wifi Calling icon re-enables itself and pushes itself in between the Data and Bluetooth toggles, pushing Bluetooth off of the screen. I realize that it's easy to just go back into the 'Quick Settings' settings and un-tick Wifi Calling again, but it gets really annoying when I reboot multiple times a day. Does anyone know of a more permanent solution besides just un-ticking the box every time I reboot? If it helps, I am using the Gold edition G3 from Sprint and I'm rooted. This 'problem' has been going on since I got the phone.
Click to expand...
Click to collapse
mine just started a few days ago.
bump for a fix

anyone?

Cover to mute

problem resolved

cover to mute
tonyguy2000 said:
problem resolved
Click to expand...
Click to collapse
Very curious what the issue was, and how it was resolved. I went the Asus Support chat route, and was supremely disappointed when they sent me to their website, had me do a reset, a reinstall of the Zenwatch Manager, then decided it must be a hardware issue, and told me it would need to be sent in to be serviced.
If cover to mute doesnt work, and the app wont save the selection when I click apply...but cover works for other features....why blame the watch hardware? Seems more likely to be a phone software issue than watch hardware.
Support had no clue. The watch is saying install android wear, the phone indicates that Zenwatch Manager requires and uses Android Wear configuration, and the guy is telling me I dont need to install Android Wear. Very frustrating half hour!

Not working for me either
I can't get incoming calls (Nexus 5, stock Lollipop 5.0.1) to mute using the feature either. Could it be related to the fact that I wear the watch on my right wrist?

nah, sounds like a hardware issue... send it in for service.
nah, sounds like a hardware issue... send it in for service.

Are you putting your palm ON the watch? That's what I have to do with my Moto 360.

cover to mute
What's odd, is cover with palm does work for other things....if you want to return to dismiss whatever is on screen, and return to the watch screen, so the cover function works! And the phone calls can be answered or dismissed from the watch with a right or left swipe. Its just that function in zenwatch manager.

Here was my solution
I had this problem too, and found a solution.
PROBLEM: On my phone, in the Zenwatch Manager app, under the "Cover to Mute" setting, I would tick the box next to "Incoming call", then "apply", but when I would go back into that setting, the box would be unticked.
SOLUTION:: On the WATCH, start FoneHelper (touch the clock to get the main menu--where it says "speak now" up top--scroll down and press the menu item "start", scroll and press "fonehelper). You will then have the option to toggl "Cover to Mute." I was able to enable the setting from that screen.
*Incidentally, when I do it that way, I can immediately see that choice reflected on my phone, in the Zenwatch Manager App. I still cannot use the Zenwatch Manager to enable this setting, but I've succesfully done it via my watch multiple times.
Hopefully this is helpful for someone else as well.

Confirmed resolution!
nlwclark said:
I had this problem too, and found a solution.
PROBLEM: On my phone, in the Zenwatch Manager app, under the "Cover to Mute" setting, I would tick the box next to "Incoming call", then "apply", but when I would go back into that setting, the box would be unticked.
SOLUTION:: On the WATCH, start FoneHelper (touch the clock to get the main menu--says "speak now" up top--scroll down and press the menu item "start", scroll and press "fonehelper). You will then have the option to toggl "Cover to Mute." I was able to enable the setting from that.
*Incidentally, when I do it that way, I can immediately see that choice reflected on my phone, in the Zenwatch Manager App. I still cannot use the Zenwatch Manager to enable this setting, but I've succesfully done it via my watch multiple times
Hopefully this is helpful for someone else as well.
Click to expand...
Click to collapse
That's it! Even Asus support was stumped, but that setting is the cause/solution!
Thanks for taking the time to provide such a well written response! Thanks again! +++

Thank you so much. Having the same problem and this totally fixed it for me!

On Nexus 5 and Android 5.1 installed this does not help. Problem is, that Watch put Phone into "Interrupt priority" state, which allows only important events to ring or vibrate. But this setting does not prevent ring or vibration, which is already in progress during the incoming call. I tried to use Takser app to set Silent mode on, ringer off, vibrate off, interrupt mode to None - but none of them helped. It can mute the ringer, but not the vibration. But then i figured out the solution. First, you need a rooted phone. Then create Tasker profile for variable set event "%INTERRUPT~priority". This will trigger event, when Watch will set the phone to "interrupt priority state". Create a task for this profile to just simulate pressing volume down key: select Button action to do this. This will completly mute the call.
Also, ASUS support told me, that this issue will be fixed in android 5.1.1 in the middle of may.

how disable "touch input blocked" warning. and other smart lock advise..

As the header says...
I use glasses, so...
I do not use any face recognition anymore but use my Lametric clock bluetooth to "smart" unlock.
Other smart unlocks do not seem to work properly; like trusted places.
Same with my note 9. Says it's not connected. ("Can't add device, be sure...") Yes I am sure it's nearby and it's paired
Voice unlock works reasonable but starts up the assistent.
If anybody has a hint to use other smart unlocking tools..
I use Google Wif
Idem Automateit.
Huib
Pfff how I miss the finger....

In order to get rid of the "Touch input is blocked" message you have to disable a display setting.
Open your device settings and go to the 'Display' menu. Scroll down a bit under 'Display' and find the setting that says 'Block accidental touches'. Disable that toggle and you shuold no longer see the message.

Pfff, that did it. some people know everything.
Thanks a lot!
Huib

I got this message in Note 9 and compared to behaviour of my wife's Note 9 whose phone was ok and found what's causing it.
Block accidental touches toggle made no difference for me.
Go to Accessibility then Dexterity and interaction and check if option for easy screen on is on. If it is, turn it off. Then it works as supposed.
In my case with this feature on, after covering the sensor, my screen would come on after about 30 seconds with said error. With it off, it turns off completely as I remember on my Note 8.

New Samsung settings and GPS

On android devices it was always possible to switch localisation services and GPS separately.
You could keep localisation services turned on (with wifi and phone) and turn off GPS to spare battery.
Now with android pie and new smasung settings it is all or nothing as there is onlys one setting :
I can turn on localisation and it turns on GPS
But if you turn it off, it disables everykind of localisation : GPS but also wiifi ...
Has anyone noticed this and is there a workaround ?

I'm not a fan of the always enabled GPS
I really do not like this at all. I have typically always kept GPS off as far back as Jellybean, favoring Locations battery saving mode, unless I needed navigation or something like that. GPS is power hungry and there's no reason to have to have it always enabled. I know Pie is supposed to help with battery usage and I honestly can't judge whether or not it really does yet as this is day two for me.
Pie is supposed to prevent apps from accessing sensors in the background but I've read that this doesn't apply to GPS so this whole thing is probably part of a marketing thing giving Google as well as app devs the ability to monetize ads based on specific location of us the users. Location is frequently wrong about where I am anyway, showing me a street over and even though I have WiFi and Bluetooth scanning enabled. As a result, my Safe Unlock no longer works when I'm home (only location I have enabled) which sucks. With Oreo I saw this somewhat often and only after I had been home for a while would the Safe Unlock work properly and I accepted this as a consequence of having Location in battery saving mode but now I'm not sure. I just no that with Pie, so far, Safe Unlock hasn't functioned once. My designated home WiFi that I'm on as I type should cause Safe Unlock to do it's thing but it's not. Maybe Location or Safe Unlock are broken. I have seen reports of both regarding Pie so I can't blame it in Samsung. I guess I'll have to try to figure out which of these features is broken.
I'm not sure if this is related to the Location issue but I also noticed that Samsung+ is not working for me. When I first tried to open it I got a notification that I need to have location enabled, I agreed (it was anyway), then I was shown a red screen with error or format codes that force closed faster than I could decipher it. This could be related or could have been broken in an update. Other than for ad purposes, and I don't recall seeing any other than Samsung ads in the Samsung app, I don't know why Samsung+ needs to access location services as it only works in the US and the network tells the app I'm in the US as well as the tower I'm accessing. I suppose it's another attempt to collect user info related to WiFi, Mac address and Bluetooth. I only got the "enable location" request the first couple of times I tried opening the app but the red error screen and FC both still occur. I tried to get a screenshot but I could only manage about half of the screen before it FC'd. I attached the partial pic. It's the bottom half of the screen. When it closes, the app window seems to slide up like when you close apps in the recents view. This brings up another complaint...Screenshot is slow to respond so events like this are next to impossible to capture. I'll have to get a camera out and try.

dronarg said:
On android devices it was always possible to switch localisation services and GPS separately.
You could keep localisation services turned on (with wifi and phone) and turn off GPS to spare battery.
Now with android pie and new smasung settings it is all or nothing as there is onlys one setting :
I can turn on localisation and it turns on GPS
But if you turn it off, it disables everykind of localisation : GPS but also wiifi ...
Has anyone noticed this and is there a workaround ?
Click to expand...
Click to collapse
Yes I noticed this. I use 'Tasker' app as a workaround. I set Location Mode to High Accuracy when using Navigation apps, and set to Battery Saving after closing the Navigation app. You can also just create a widget on home screen to toggle Location Mode to High Accuracy or Battery Saving.
I confirmed this setting by using 'Power Toggles' app widget. When the GPS toggle in widget is highlighted, it means on High Accuracy mode, if not highlighted it's on Battery Saving mode.

dronarg said:
On android devices it was always possible to switch localisation services and GPS separately.
You could keep localisation services turned on (with wifi and phone) and turn off GPS to spare battery.
Now with android pie and new smasung settings it is all or nothing as there is onlys one setting :
I can turn on localisation and it turns on GPS
But if you turn it off, it disables everykind of localisation : GPS but also wiifi ...
Has anyone noticed this and is there a workaround ?
Click to expand...
Click to collapse
I have yet to notice any adverse battery performance since I've been on pie and I've been on it since the start of the official betas. I was annoyed at first because I had always used battery save mode but really it's been a non issue for me.

OneUI - Disable Scanning for nearby Wifi/Bluetooth on S9?

Hi,
I just updated to OneUI on my S9 and was hoping someone could help me figure out how to disable the Google Play services notification that says that even though my wifi and bluetooth are disabled, my device will still continue to scan for them?
I cannot find anywhere to turn it off, and pressing the notification just makes a notification sound without opening any useful menu!
I suppose I can turn off notifications themselves, but I actually want my device to NOT scan for stuff.
Sorry if I posted in the wrong place, feel free to move.
Tried a search but nothing come up with scanning.
Thanks!

S9Droid said:
Hi,
I just updated to OneUI on my S9 and was hoping someone could help me figure out how to disable the Google Play services notification that says that even though my wifi and bluetooth are disabled, my device will still continue to scan for them?
I cannot find anywhere to turn it off, and pressing the notification just makes a notification sound without opening any useful menu!
I suppose I can turn off notifications themselves, but I actually want my device to NOT scan for stuff.
Sorry if I posted in the wrong place, feel free to move.
Tried a search but nothing come up with scanning.
Thanks!
Click to expand...
Click to collapse
Settings > Connections > Bluetooth > Improve Accuracy Settings (Text link under the writing at the bottom) > Turn off the WiFi & BT scanning

Thank you very much!

*Detection* said:
Settings > Connections > Bluetooth > Improve Accuracy Settings (Text link under the writing at the bottom) > Turn off the WiFi & BT scanning
Click to expand...
Click to collapse
Thank. Just updated to Android 9 on the Note 9 and would have never bloody found this. They hide it better with every update. heh.