I am having connection issues with the Pixel 4 XL and the August WiFi SmartLock (4th gen). This lock uses both WiFI and Bluetooth to detect your proximity to home for the "auto unlock" feature.
The WiFI connectivity is OK, but the Bluetooth connection is very flaky. August support just offers their standard suggestions to clear the app cache/memory, switch BT off/on, restart the phone, power cycle and recalibrate the lock. This sometimes works for a while and then the BT connectivity begins to fail again.
There must be others with Pixel 4 and August Smartlock. Has anyone else had this problem and found a solution?
JWadle said:
I am having connection issues with the Pixel 4 XL and the August WiFi SmartLock (4th gen). This lock uses both WiFI and Bluetooth to detect your proximity to home for the "auto unlock" feature.
The WiFI connectivity is OK, but the Bluetooth connection is very flaky. August support just offers their standard suggestions to clear the app cache/memory, switch BT off/on, restart the phone, power cycle and recalibrate the lock. This sometimes works for a while and then the BT connectivity begins to fail again.
There must be others with Pixel 4 and August Smartlock. Has anyone else had this problem and found a solution?
Click to expand...
Click to collapse
So I have an August Smartlock 3rd gen with connect. My issue with the auto unlock is that if the phone hasn't been rebooted after a while, the auto unlock will trigger (based on location) but will hang forever trying to unlock the door, and eventually fail. I am able to connect to my lock and manually unlock the door without any issues while it's trying to auto unlock. My solution that I've found is that if you reboot your phone every 2-3 days or so, auto unlock should work flawlessly. My brother who has a Pixel 3 XL has the same issue and rebooting for him every so often works. It's honestly an annoying fix.
I went through a long email chain with August and they basically said they'd take note of it. I know clearing app data also works, but it's temporary and way more annoying to re-sign in and set up auto unlock than just rebooting the phone.
Let me know if just rebooting it every so often actually works for you as well.
Related
Hello everyone.
I just wanted to get your attention on a major Android OS (Kitkat) bug in the interaction between Wifi -> Advanced -> Wifi Always Scan and the Location Service. Clearly the bug doesn't happen every time, but sometimes it does, and obviously I'm talking about stock rom / kernel / no root / locked bootloader.
Althought I can't prove it, this might also be the cause of the current GPS / Navigation issues, currently being reported here.
What makes me link this to that issue? Because when Wifi Always Scan bugs out, it prevents my phone to acquire a location even from the 3g network.
That would explain why in that thread many people report that they could navigate with Device Only, which doesn't use 3g or wifi for location, but they had major issues with High Accuracy, which uses all three sources.
Please take a minute to star the issue so that Google will hopefully fix it faster.
https://code.google.com/p/android/issues/detail?id=64597
Thank you,
TD
Just turn it off, all it does is waste battery anyway
Sent from my Nexus 5 using Tapatalk
Ben36 said:
Just turn it off, all it does is waste battery anyway
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for your useful contribution.
It doesn't waste battery, it saves it. It enables to use the wifi location using a lower power state of the wifi chip compared to actually turned on wifi (which is also more accurate by miles than 3g location, works indoors in clubs where there is no 3g or gps signal, and not as battery expensive as gps location).
Also, people use that option for many things, I for one use it in MANY Tasker tasks flawlessly, whether the alternative (wifi periodic toggle and polling) would rape my battery.
Wifi automatically Turned off. Built in feature?
I kept my wifi on, and the had not used it basically just left the device in the room and had run off.
When I retured, the wifi was on in the power control widget but the wifi signal indicator icon in the notifications bar was absent.
is this normal/intended?
My wifi / internet connection is weak but continuous and my device is about ten to twelve feet away from the modem / router.
Can anybody help?
Although I have not a Nexus 5, my problem seems to be the same. I'll tell you if perhaps serve as any indication.
In my HTC EVO 3D, I've been running since the summer with CM10.2 (Android v4.3.1) with location mode set to "Network & WiFi" and "WiFi Always Scan ON". During this time the location was very accurate, location history left a fairly detailed trace. In Google Maps, was located immediately, as in Google+. If activated the GPS, even better. Summarizing, 0 issues with the location.
On January 1, I decided to upgrade to CM11 (Android v4.4.2), I set my location mode to "Battery Saving" & "Wifi Scan Always ON". During the first 10 days everything was perfect, the location history trail was so detailed as CM10.2 and battery consumption a little better. Google Maps and Google+ also positioned themselves almost immediately. Suddenly, on January 11 the location seems to stop of using WiFi networks and began guided only by the Network Cells (being rather more vague). Also when for some reason failed to position (being out of range of Network Cell), the phone started to not enter Deep Sleep Mode and the battery started to discharge at high speed. Google Maps, Google+, 1Weather ... were unable to obtain the current location or showed the last known location of hours before. Rebooting the phone sometimes temporarily solved the problem, but sometimes not.
I tried to change the placement options; abroad, with "high accuracy" mode, the location worked well, but indoors the GPS was not able to find satellites (logical) and still the same problems. I enabled and I disabled the location, nothing. Factory reset, no change.
To rule out a hardware failure, I returned CM10.2. Everything about the location worked smoothly... Return to CM11, again the same problems.
In short, my impression is that this is a software bug, as in versions prior to v4.4 Android location "Network & WiFi" + "Scan Always ON WiFi" works correctly. Moreover, not only occurs in the Nexus 5.
I have marked with a star your ticket.
I'll keept testing.
I get this problem when I use tether with WiFi always scan enabled.
When I disabled tethering, I have to manually enable WiFi to fix the location reporting issue.
With WiFi scanning not enabled, I do not get this problem
Sent from my Nexus 5 using XDA Premium 4 mobile app
I think I have similar problem and I really hope smbody can help me.
On my stock nexus 5(4.4.2) wifi location don't work in google maps and ingress, when I turn it on instead of gps location.
But in other apps wifi location works( yandex.maps, 4square)
Only reboot helps
Hello again.
I just updated Google Maps to version 7.6.0 and Google Play Services to version 4.2.39 and all the problems I had with the location are gone, everything is okay again, as it did in CM10.2. So it looks like it is confirmed that it was a software bug.
Sorry, I know this post is quite stale, but I came across it doing a search about this very same problem I've seen on my LG G4 (stock). I have a Tasker task that uses WiFi near state and I use the "Allow Wifi scanning..." option in my Advanced WiFi settings. Whenever I would use WiFi tethering and then later turn it off, I noticed my Tasker task would not detect the WiFi networks it was supposed to. If I turn the "Allow scanning" option of and back on, or just turn on WiFi altogether, it starts working again.
So, after more than a year and a half, and on a newer version of Android and it still doesn't work right. Who knows; maybe it's a Tasker problem.
-SR-
Hey guys, I just received my Note 5 today. But it's weird that my WiFi connectivity has issues. When I typed my passcode for WiFi, it was unable to connect and always flashing WiFi page. After couple seconds, it showed identification error(I'm sure that passcode is correct). It even cannot connect to WiFi without passcode. Any ideas?
I've had the exact same issues when I reset my phone. And I've done that a lot lately while trying to find out the issue with the 10sec unlock lag - which I seemed to have narrowed down to Android Wear and my LG G watch (possible Bluetooth issues)
To bypass the issue you have, I end up setting up the phone using 4G, then reconnecting wifi and it works...
What version N920I do you have? 32gb or 64gb?
Hi, I'm new here so forgive me if I do something wrong^^
First of all, I have a Moto G 2014, Dual Sim which is running on 5.1.1, to be more specific, this ROM. I was using this ROM for about 4 months already so that shouldn't be the issue. My problem is that after my phone connects to the internet, usually using H+. The connection to the internet is working perfectly fine, but after a while of not using the phone it loses the connection. It still tells me that it got a strong H+ connection, but nothing (browser, apps, anything) is able to connect to the internet. Enabling & disabling airplane mode usually fixes the problem. From time to time it also happens, usually when I lost some sort of wifi connection (regardless if I disabled wifi or I got out of range) it happens that it shows full connectivity but with an exclamation mark. This only goes away if I reboot or enable & disable airplane mode again.
Is this issue known/is there any solution to
I have been experiencing the exact same thing as of lately. I thought it was a byproduct of downgrading from (Stock) Marshmallow to (Stock) Lollipop (yes! it's happening even on stock ROM) where at times the WiFi losses connectivity when the phone had been sleeping for awhile...even though I have the "Keep WiFi on during sleep" option on under WiFi's advanced settings. I had no idea that it also happens with data connections ! ...as I don't use it (too expensive for me), now I'm uncertain what could be the cause. I can see how this would be an inconvenience if you use a lot of social media apps as I sometimes do not get my WhatsApp messages when this happens and sometimes I don't even receive my Hangouts messages until I open the app manually.
It's strange, at times when my phone sleeps for awhile and it losses connectivity and I wake it, it will reconnect just fine and other times it just goes into this state where it reconnects with full signal strength but with an exclamation mark next to the WiFi icon in the notification bar. When this happens, no matter what I try it stays in this state, I tried turning off WiFi and turning it back on, also forgetting the network and entering the info and reconnecting to it but none of that works. I didn't know that turning on and off airplane mode can help....I'll have to try that one, rebooting the phone was the only solution I found which is just inconvenient and somewhat annoying.
I too, am interested in a proper solution. I don't know why the phone ignores the "Keep WiFi on during sleep" option or why at times it connects but have not internet access! It should be noted that it's not a problem with the network, It's not due to an incorrect password or anything like that as I am the one that administers those things and when it happens other WiFi devices such as my Tablet PC, Laptop etc can connect and access the internet just fine and it only happens sometimes on the phone (Moto G 2014). This doesn't seem to happen in Marshmallow...but I hate Marshmallow and I can't remember having this issue on Lollipop post Marshmallow update (how I wish I had never tried out Marshmallow!!!), which is why I thought it was related to downgrading, .......did you downgrade ?
My carrier recently supported voice calls for the device, previously i could only have data. Now my phone is able to acess the internet even when my data option is off.
Sometimes when it does accept to turn off my data, and i want to reconnect to the internet again, i have to put my phone into airplane mode then back again for it to pick my data connection.
And sometimes my fingerprint scanner just spases out amd doesn't immediately recognise both fingers added, only after several tries.
Am on the june 2018 security update
Very peculiar problem, anyone with a solution?
So my accesspoint now supports WPA3 in beta.
This seems to work great with my apple products but I have some issues using wpa3 with my Pixel 4 XL.
At first I had to delete the WiFi and reenter the passphrase to get WPA3 working.
Then after a few hours the phone disconnects and asks for the passphrase again but can't connect. Keeps asking for passphrase again and again. I have to disable and enable WiFi to get it working again. This happens every few hours.
For me this looks more like a pixel related problem then a problem related to my access point, isn't it? But with WPA2 everything works fine.
Anyone else out there running WPA3 personal with Pixel 4/XL experiencing problems?
Doenerbude said:
So my accesspoint now supports WPA3 in beta.
This seems to work great with my apple products but I have some issues using wpa3 with my Pixel 4 XL.
At first I had to delete the WiFi and reenter the passphrase to get WPA3 working.
Then after a few hours the phone disconnects and asks for the passphrase again but can't connect. Keeps asking for passphrase again and again. I have to disable and enable WiFi to get it working again. This happens every few hours.
For me this looks more like a pixel related problem then a problem related to my access point, isn't it? But with WPA2 everything works fine.
Anyone else out there running WPA3 personal with Pixel 4/XL experiencing problems?
Click to expand...
Click to collapse
I know late answer but better as none.
I just activate WPA3 on my AVM Repeater 3000 and i have the same problems.
I needed to delete the passphrase and connect again
because before that the phone didn't change to WPA3.
And when the connection going away unexpectly i must deactivate and activate the wlan once.
I don't know whether this happens so often as by you because i'm running wpa3 since an hour (round about).
And well i have a few hickups in wpa2, too. So i can't say whether this is wpa3 specific.
I know that doesn't help you really but well at least you are not the only one with that problem.
Nice to see I'm not the only one experiencing these problems.
Have you reported the problem to AVM?
Doenerbude said:
Have you reported the problem to AVM?
Click to expand...
Click to collapse
Not yet.
One thing to try is in your WiFi profile > Advanced > Privacy = Use device MAC.
SpookyTunes said:
One thing to try is in your WiFi profile > Advanced > Privacy = Use device MAC.
Click to expand...
Click to collapse
I already do this because i'm using MAC whitelisting.
The issues with WPA3 and FRITZ!Box router/ap seems to be fixed with March Update and/or latest beta/"Labor" firmware for Fritz ?
@dhacke can you confirm this?
Doenerbude said:
The issues with WPA3 and FRITZ!Box router/ap seems to be fixed with March Update and/or latest beta/"Labor" firmware for Fritz ?
@dhacke can you confirm this?
Click to expand...
Click to collapse
Wow they are fast. I wrote to them at monday and now they have already a labor update?!
Great. I will install the labor update on my wlan repeater on Sunday and report back.
@Doenerbude
today i installed the new labor update on my fritz repeater 3000 and sadly it doesn't help.
My connection aborts are so high as before. I'm back on wpa2 again.
I have issues with WPA3 as well. I switched it on the Google Nest WiFi and whilst my Chromebook doesn't face any issues, my Pixel 4XL is randomly disconnecting from the network.
I've also noticed that when I walk in my apartment, it doesn't connect automatically. I have to switch off the WiFi on the phone and switch it back on to connect to the WiFi network.
This issue does not appear when WPA3 is switched off. I initially thought it's a poor implementation on the Nest WiFi but perhaps not?
mkouk said:
I have issues with WPA3 as well. I switched it on the Google Nest WiFi and whilst my Chromebook doesn't face any issues, my Pixel 4XL is randomly disconnecting from the network.
I've also noticed that when I walk in my apartment, it doesn't connect automatically. I have to switch off the WiFi on the phone and switch it back on to connect to the WiFi network.
This issue does not appear when WPA3 is switched off. I initially thought it's a poor implementation on the Nest WiFi but perhaps not?
Click to expand...
Click to collapse
I believe meanwhile the implementation in our phone is the problem. That would explain why the problem occurs on different wpa3 router/aps.
As far as i know the pixel 4 xl isn't a wifi6 certified device and only wifi6 certfified devices are required to support wpa3.
That could explain the bad implementation.