New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nearby doesnt seem to be working again with beacons again? #882

Open
craigahunter opened this Issue Jan 18, 2017 · 67 comments

Comments

Projects
None yet
@craigahunter

craigahunter commented Jan 18, 2017

Hi, I am wondering if the Nearby using beacons has been disabled again. I have reset the Android phone (lollipop) back to factory state after it is not picking anything up. It does show during a scan that bluetooth beacons are recognised but no notifications appear. I have even used a new beacon with a new secure URL and still nothing.

I know a few months ago Nearby was disabled and I am thinking this may have been done again. It seems to work so consistently on Apple devices but is very much hit and miss on Android. I think this will be a big point that prevents consumer uptake if its going to be so inconsistent.
Please advise if you can, kind regards Craig

@oninross

This comment has been minimized.

Show comment
Hide comment
@oninross

oninross Feb 2, 2017

Experiencing the same thing also. I swipe down and I dont see any notifications of nearby beacons.

I just noticed this. #880

oninross commented Feb 2, 2017

Experiencing the same thing also. I swipe down and I dont see any notifications of nearby beacons.

I just noticed this. #880

@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Feb 2, 2017

Contributor

Sorry, that was an old warning that was supposed to be taken down. Things are working fine and that page has been updated.

Contributor

scottjenson commented Feb 2, 2017

Sorry, that was an old warning that was supposed to be taken down. Things are working fine and that page has been updated.

@oninross

This comment has been minimized.

Show comment
Hide comment
@oninross

oninross Feb 2, 2017

Hi @scottjenson, I am not seeing anything on my notifications drawer. It was working a few weeks back until I wanted to do a check today. I have my locations and bluetooth enabled, the Nearby icon lights up but no notifications. Here is a screen shot. What did I miss now?

screenshot_20170202-180256

oninross commented Feb 2, 2017

Hi @scottjenson, I am not seeing anything on my notifications drawer. It was working a few weeks back until I wanted to do a check today. I have my locations and bluetooth enabled, the Nearby icon lights up but no notifications. Here is a screen shot. What did I miss now?

screenshot_20170202-180256

@craigahunter

This comment has been minimized.

Show comment
Hide comment
@craigahunter

craigahunter Feb 2, 2017

Hi @scottjenson the physical web (used via google) still works although sporadically and I have to reset at times. The nearby however has not worked at all in quite some time. As I stated above I have reset the phone, installed any updates but it simply does'nt show anything. I've never had any problems with IOS but my android phone is very inconsistent. The device is picking up beacon signals when I scan with bluetooth only so the device is fine that way...just no nearby! Thanks

craigahunter commented Feb 2, 2017

Hi @scottjenson the physical web (used via google) still works although sporadically and I have to reset at times. The nearby however has not worked at all in quite some time. As I stated above I have reset the phone, installed any updates but it simply does'nt show anything. I've never had any problems with IOS but my android phone is very inconsistent. The device is picking up beacon signals when I scan with bluetooth only so the device is fine that way...just no nearby! Thanks

@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Feb 3, 2017

Contributor
Contributor

scottjenson commented Feb 3, 2017

@oninross

This comment has been minimized.

Show comment
Hide comment
@oninross

oninross Feb 4, 2017

Hi @scottjenson,

I did your tests, yes I am seeing the list with no problem. I checked Google Play Services and the version is what you said. I have woken up my phone a few times with no avail. 95% of the time the notification does not show up.

oninross commented Feb 4, 2017

Hi @scottjenson,

I did your tests, yes I am seeing the list with no problem. I checked Google Play Services and the version is what you said. I have woken up my phone a few times with no avail. 95% of the time the notification does not show up.

@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Feb 4, 2017

Contributor

Would you mind sending me the short url you are testing?

Contributor

scottjenson commented Feb 4, 2017

Would you mind sending me the short url you are testing?

@oninross

This comment has been minimized.

Show comment
Hide comment
@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Feb 4, 2017

Contributor
Contributor

scottjenson commented Feb 4, 2017

@oninross

This comment has been minimized.

Show comment
Hide comment
@oninross

oninross Feb 4, 2017

it is showing up in the list view. i go to setting > google > nearbly, i see the list. just not in the notifications drawer

oninross commented Feb 4, 2017

it is showing up in the list view. i go to setting > google > nearbly, i see the list. just not in the notifications drawer

@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Feb 4, 2017

Contributor

I just programed my own beacon to http://bitly.com/beacon01 and confirmed that it is showing up in the list view but not notifications. I'm exploring why that is. One thing you can do as a potential workaround is to change the URL redirector to https://cbrbus.com.au/busstop/3410 (or something similar) to just test out a different URL

One trick I use is to just add a parameter onto the end (like &x) but that seems to break your server.

Scott

Contributor

scottjenson commented Feb 4, 2017

I just programed my own beacon to http://bitly.com/beacon01 and confirmed that it is showing up in the list view but not notifications. I'm exploring why that is. One thing you can do as a potential workaround is to change the URL redirector to https://cbrbus.com.au/busstop/3410 (or something similar) to just test out a different URL

One trick I use is to just add a parameter onto the end (like &x) but that seems to break your server.

Scott

@oninross

This comment has been minimized.

Show comment
Hide comment
@oninross

oninross Feb 4, 2017

@scottjenson thanks for the information. I will try the parameter for now.

Just a clarification, doesnt beacons hold only a number of characters for the URL? That is why it is suggested to use a URL shortener. I may have misunderstood it.

oninross commented Feb 4, 2017

@scottjenson thanks for the information. I will try the parameter for now.

Just a clarification, doesnt beacons hold only a number of characters for the URL? That is why it is suggested to use a URL shortener. I may have misunderstood it.

@oninross

This comment has been minimized.

Show comment
Hide comment
@oninross

oninross Feb 4, 2017

@scottjenson by the way, I just remembered that the parameter method did pose some issues for me before. Instead of hardcoding the variables in the html, I initially used the query params method (for more flexibility). However, after a while, nearby couldnt detect it anymore.

In addition to the said issue, this might pose a bigger issue if the beacons go live long term. If initially the beacons are working fine then a few weeks or months down the line the beacons are not discoverable.

oninross commented Feb 4, 2017

@scottjenson by the way, I just remembered that the parameter method did pose some issues for me before. Instead of hardcoding the variables in the html, I initially used the query params method (for more flexibility). However, after a while, nearby couldnt detect it anymore.

In addition to the said issue, this might pose a bigger issue if the beacons go live long term. If initially the beacons are working fine then a few weeks or months down the line the beacons are not discoverable.

@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Feb 4, 2017

Contributor

It's only the final URL that matters, I was suggesting you add a parm to the final crbus.com. I was just suggestion you change the redirected URL to a new one.

Contributor

scottjenson commented Feb 4, 2017

It's only the final URL that matters, I was suggesting you add a parm to the final crbus.com. I was just suggestion you change the redirected URL to a new one.

@oninross

This comment has been minimized.

Show comment
Hide comment
@oninross

oninross Feb 4, 2017

@scottjenson okies. thank you so much for your help :) Really appreciate it

oninross commented Feb 4, 2017

@scottjenson okies. thank you so much for your help :) Really appreciate it

@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Feb 4, 2017

Contributor

I've confirmed that your beacon is being lowered and not notifying. I'm looking into why this is. Can you confirm a few things for me?
Is this beacon live or are you just debugging at this point?
Are there many folks that might be near this beacon?

This will provide valuable feedback to the ratings team, thanks,

Scott

Contributor

scottjenson commented Feb 4, 2017

I've confirmed that your beacon is being lowered and not notifying. I'm looking into why this is. Can you confirm a few things for me?
Is this beacon live or are you just debugging at this point?
Are there many folks that might be near this beacon?

This will provide valuable feedback to the ratings team, thanks,

Scott

@oninross

This comment has been minimized.

Show comment
Hide comment
@oninross

oninross Feb 4, 2017

@scottjenson for this project, it is not yet live. We are about to push this for research and data gathering as soon as our material is ready to use.

FYI, I changed my URL shortener and added the parameter for safety. So far so good :) will keep you posted if i see any problems.

oninross commented Feb 4, 2017

@scottjenson for this project, it is not yet live. We are about to push this for research and data gathering as soon as our material is ready to use.

FYI, I changed my URL shortener and added the parameter for safety. So far so good :) will keep you posted if i see any problems.

@ferencbrachmann

This comment has been minimized.

Show comment
Hide comment
@ferencbrachmann

ferencbrachmann Feb 4, 2017

@scottjenson I can confirm the same thing happened to one of my personal pages @ b3m.it/B2000038

ferencbrachmann commented Feb 4, 2017

@scottjenson I can confirm the same thing happened to one of my personal pages @ b3m.it/B2000038

@shailesh17mar

This comment has been minimized.

Show comment
Hide comment
@shailesh17mar

shailesh17mar Feb 5, 2017

@scottjenson Same here, yesterday our messages suddenly stopped sending messages. They were working perfectly fine day before that.
When you say 'your beacon was lowered' could you shed some more light on it? Are there some guidelines that we should follow.

shailesh17mar commented Feb 5, 2017

@scottjenson Same here, yesterday our messages suddenly stopped sending messages. They were working perfectly fine day before that.
When you say 'your beacon was lowered' could you shed some more light on it? Are there some guidelines that we should follow.

@craigahunter

This comment has been minimized.

Show comment
Hide comment
@craigahunter

craigahunter Feb 9, 2017

Hi Scott, sorry for the late reply i have been away. I have tried it on my particular device and its not working. I have switched nearby on and off but still nothing. It isn't even populating the list using Google settings like you suggested. The device uses Android 6.0.1 I have checked google play services settings and the device is using version 8.7.03 (no options are active to allow me to disable, update, or force stop). My main concern is the consistency of operation between devices if I am to introduce aspects of the physical web to business's so just ironing out the problems so to speak. Thanks again.

craigahunter commented Feb 9, 2017

Hi Scott, sorry for the late reply i have been away. I have tried it on my particular device and its not working. I have switched nearby on and off but still nothing. It isn't even populating the list using Google settings like you suggested. The device uses Android 6.0.1 I have checked google play services settings and the device is using version 8.7.03 (no options are active to allow me to disable, update, or force stop). My main concern is the consistency of operation between devices if I am to introduce aspects of the physical web to business's so just ironing out the problems so to speak. Thanks again.

@adriancretu

This comment has been minimized.

Show comment
Hide comment
@adriancretu

adriancretu Feb 9, 2017

GPS 8.7.03 is one year old; way before Nearby was introduced, you'll need v10.0.84 or newer.

adriancretu commented Feb 9, 2017

GPS 8.7.03 is one year old; way before Nearby was introduced, you'll need v10.0.84 or newer.

@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Feb 9, 2017

Contributor

Thank you Adrian, that is correct. We totally appreciate not all devices have the latest software, but Nearby has been active nearly 6 months now, the number of devices with it is growing quickly.

Contributor

scottjenson commented Feb 9, 2017

Thank you Adrian, that is correct. We totally appreciate not all devices have the latest software, but Nearby has been active nearly 6 months now, the number of devices with it is growing quickly.

@mcizol

This comment has been minimized.

Show comment
Hide comment
@mcizol

mcizol Feb 10, 2017

Same issue with Huawei P8 Lite 2017, Android 7
Google Play Services version: 10.2.98

I found a short-term solution, which may not work in some devices because of disabled "force stop" button..

  • force stop google play services
  • then refresh nearby app and you will see again the beacons around you.

mcizol commented Feb 10, 2017

Same issue with Huawei P8 Lite 2017, Android 7
Google Play Services version: 10.2.98

I found a short-term solution, which may not work in some devices because of disabled "force stop" button..

  • force stop google play services
  • then refresh nearby app and you will see again the beacons around you.
@Chri82

This comment has been minimized.

Show comment
Hide comment
@Chri82

Chri82 Feb 18, 2017

Notifications of my beacons do not appear. Only when I go into "Settings" => "Google" => "Nearby" finally found the link and suddenly appears also in the pull-down notifications

Chri82 commented Feb 18, 2017

Notifications of my beacons do not appear. Only when I go into "Settings" => "Google" => "Nearby" finally found the link and suddenly appears also in the pull-down notifications

@chetstriker

This comment has been minimized.

Show comment
Hide comment
@chetstriker

chetstriker Feb 18, 2017

Device: Pixel XL
Google Play Services: 10.2.98
Android 7.1.2 BETA
I've recently stopped receiving beacon notifications in the notification drop down. If i click the "nearby" button it shows up, but not in the notification bar by itself anymore, this possibly might have stopped working after receiving the last android 7.1.2 BETA update but can't verify.
The "notify you when links are available" option is selected along with "nearby links available". I also tried to use "clear data" and have rebooted a few times.
Google play services showing "force close" grayed out, so that test isn't an option.
Would love to know if there is anything else I can try to get this to work again since I'm doing a demonstration of an app utilizing beacons in a couple of days.

chetstriker commented Feb 18, 2017

Device: Pixel XL
Google Play Services: 10.2.98
Android 7.1.2 BETA
I've recently stopped receiving beacon notifications in the notification drop down. If i click the "nearby" button it shows up, but not in the notification bar by itself anymore, this possibly might have stopped working after receiving the last android 7.1.2 BETA update but can't verify.
The "notify you when links are available" option is selected along with "nearby links available". I also tried to use "clear data" and have rebooted a few times.
Google play services showing "force close" grayed out, so that test isn't an option.
Would love to know if there is anything else I can try to get this to work again since I'm doing a demonstration of an app utilizing beacons in a couple of days.

@stelliot

This comment has been minimized.

Show comment
Hide comment
@stelliot

stelliot Feb 23, 2017

I have the same problem with notification drop down after re-installing and my Samsung S6. Before the re-install it worked fine. I can see the beacons in the nearby app.

Current versions which doesn't work

Google Play Services: 10.2.98
Android: 6.0.1

stelliot commented Feb 23, 2017

I have the same problem with notification drop down after re-installing and my Samsung S6. Before the re-install it worked fine. I can see the beacons in the nearby app.

Current versions which doesn't work

Google Play Services: 10.2.98
Android: 6.0.1

@thejohanmagnusson

This comment has been minimized.

Show comment
Hide comment
@thejohanmagnusson

thejohanmagnusson Feb 26, 2017

I have stopped receiving notifications for beacons since a couple of days ago. This is on three different devices.

Device: Nexus 5X (two phones)
Google Play Services: 10.2.98
Android 7.1.1

Device: Nexus 6P
Google Play Services: 10.2.98
Android 7.1.2 BETA (Didn't get notifications on 7.1.1 either, upgraded yesterday)

Location and Bluetooth is on and nearby is set to show notifications for beacons on all devices.

I can see the the preview in the nearby app on all devices.
For some reason the nearby icon in the quick settings show as disabled, if I go to edit the quick settings nearby shows as enabled if I have just been in the nearby app, otherwise it's shows as disabled here also.

thejohanmagnusson commented Feb 26, 2017

I have stopped receiving notifications for beacons since a couple of days ago. This is on three different devices.

Device: Nexus 5X (two phones)
Google Play Services: 10.2.98
Android 7.1.1

Device: Nexus 6P
Google Play Services: 10.2.98
Android 7.1.2 BETA (Didn't get notifications on 7.1.1 either, upgraded yesterday)

Location and Bluetooth is on and nearby is set to show notifications for beacons on all devices.

I can see the the preview in the nearby app on all devices.
For some reason the nearby icon in the quick settings show as disabled, if I go to edit the quick settings nearby shows as enabled if I have just been in the nearby app, otherwise it's shows as disabled here also.

@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Mar 15, 2017

Contributor

At this point, things should be working with the latest GPS. keep in mind that Nearby monitors notifications and if no one clicks on them, they will eventually stop creating notifications. So we strongly recommend that you test with a debug URL that you can use until you go live.

If your beacon shows up in the listview you're 99% of the way there. Most of the time, the notification doesn't show up because you haven't power cycled your phone. The scan only happens when you wake up.

Contributor

scottjenson commented Mar 15, 2017

At this point, things should be working with the latest GPS. keep in mind that Nearby monitors notifications and if no one clicks on them, they will eventually stop creating notifications. So we strongly recommend that you test with a debug URL that you can use until you go live.

If your beacon shows up in the listview you're 99% of the way there. Most of the time, the notification doesn't show up because you haven't power cycled your phone. The scan only happens when you wake up.

@oninross

This comment has been minimized.

Show comment
Hide comment
@oninross

oninross Mar 15, 2017

Hi @scottjenson, do you mean that if the notification link isnt clicked for some time, it just doensnt show up anymore? That is my case now. I managed to broadcast a url in a beacon and im picking it up. But i didnt want to click it as i was enjoying just seeing that notification (yeah im weird). But now i have to go to Nearby just to see the link.

oninross commented Mar 15, 2017

Hi @scottjenson, do you mean that if the notification link isnt clicked for some time, it just doensnt show up anymore? That is my case now. I managed to broadcast a url in a beacon and im picking it up. But i didnt want to click it as i was enjoying just seeing that notification (yeah im weird). But now i have to go to Nearby just to see the link.

@thejohanmagnusson

This comment has been minimized.

Show comment
Hide comment
@thejohanmagnusson

thejohanmagnusson Mar 16, 2017

@scottjenson what is the time period for witch a notification stops being shown if no one clicks it? Feels as this can happen quite easy with beacons in remote areas were a interaction isn't expected to happen very often or like now when beacons are a very new thing, people aren't used to it and will less likely click these notifications.

My main use of beacons is for interaction with virtual functions in remote places and these will be clicked extremely seldom. A bit concerned that this de-notification could potentially ruin the whole experience and product since the user will not find it unless they explicitly search for itwith the nearby app.

thejohanmagnusson commented Mar 16, 2017

@scottjenson what is the time period for witch a notification stops being shown if no one clicks it? Feels as this can happen quite easy with beacons in remote areas were a interaction isn't expected to happen very often or like now when beacons are a very new thing, people aren't used to it and will less likely click these notifications.

My main use of beacons is for interaction with virtual functions in remote places and these will be clicked extremely seldom. A bit concerned that this de-notification could potentially ruin the whole experience and product since the user will not find it unless they explicitly search for itwith the nearby app.

@adriancretu

This comment has been minimized.

Show comment
Hide comment
@adriancretu

adriancretu Mar 16, 2017

Wait, so besides the fact that they are very difficult to even be noticed, now the notifications stop appearing all-together if not previously clicked, by other people? I really feel like there's a great need for some protocol or mechanism to allow users to actually be notified when something they want to see is nearby, instead of digging desperately through the multitude of steps and flows. Sure, let's make an app, but then why use PW in the first place?

adriancretu commented Mar 16, 2017

Wait, so besides the fact that they are very difficult to even be noticed, now the notifications stop appearing all-together if not previously clicked, by other people? I really feel like there's a great need for some protocol or mechanism to allow users to actually be notified when something they want to see is nearby, instead of digging desperately through the multitude of steps and flows. Sure, let's make an app, but then why use PW in the first place?

@holgermertens

This comment has been minimized.

Show comment
Hide comment
@holgermertens

holgermertens Mar 19, 2017

Same here:

Most URLs are fine. But:
There is one beacon URL, that Nearby did't show as notification. But it is shown if I let Nearby scan for beacons.
The URL is also shown in the physical web app and there also as notification.
The URL also pass the validator:
https://beaufortfrancois.github.io/sandbox/physical-web/url-validator/
Confused.

holgermertens commented Mar 19, 2017

Same here:

Most URLs are fine. But:
There is one beacon URL, that Nearby did't show as notification. But it is shown if I let Nearby scan for beacons.
The URL is also shown in the physical web app and there also as notification.
The URL also pass the validator:
https://beaufortfrancois.github.io/sandbox/physical-web/url-validator/
Confused.

@mjanke67

This comment has been minimized.

Show comment
Hide comment
@mjanke67

mjanke67 Apr 11, 2017

I am seeing several issues described within this thread. I will comment that we have always been able to see Nearby Notifications within the drawer and Nearby app, but have (since 6.0) had issue getting Nearby Notifications within the Lock Screen and Status Bar. If you can see a Nearby Notifications within the Nearby app, but not within the drawer, the most likely cause is that Nearby has scaled down Notification triggers due to the screen being ON for awhile. Lock and then unlock the screen to boost Nearby's triggering of Nearby Notifications within the drawer.

A work around to getting Nearby Notifications in the Lock Screen and Status bar (works in 6.x.x only) is to set or enable Google Play Services (GPS) - App Notifications "Set as priority".

For Android 7.0+ devices (all that we have tested .... about 6), there is no way to see Nearby Notifications outside of the drawer (if the screen was recently unlocked or the device awoken) or the Nearby app itself. We cannot find a way to get Notifications within the Lock Screen or Status Bar. Within another Google group (https://groups.google.com/forum/#!topic/physical-web-discuss/GX4uBO57Reg), a Google resource suggests that the way GPS initiates notifications has not changed (with MIN notification priority). This resource suggests that the way notifications are handled within the Lock Screen and Status Bar in 7.0+ is different. It is for this reason, that we no longer see Nearby Notifications in these UI components. For us - this is critical as we do not expect users to look for notifications within the drawer or Nearby app. We expect the phone to NOTIFY them when a beacon is received. It would be awesome if Scott Jenson could help with this issue as it is (we believe) critical to the adoption of Nearby and our products that leverage Nearby.

mjanke67 commented Apr 11, 2017

I am seeing several issues described within this thread. I will comment that we have always been able to see Nearby Notifications within the drawer and Nearby app, but have (since 6.0) had issue getting Nearby Notifications within the Lock Screen and Status Bar. If you can see a Nearby Notifications within the Nearby app, but not within the drawer, the most likely cause is that Nearby has scaled down Notification triggers due to the screen being ON for awhile. Lock and then unlock the screen to boost Nearby's triggering of Nearby Notifications within the drawer.

A work around to getting Nearby Notifications in the Lock Screen and Status bar (works in 6.x.x only) is to set or enable Google Play Services (GPS) - App Notifications "Set as priority".

For Android 7.0+ devices (all that we have tested .... about 6), there is no way to see Nearby Notifications outside of the drawer (if the screen was recently unlocked or the device awoken) or the Nearby app itself. We cannot find a way to get Notifications within the Lock Screen or Status Bar. Within another Google group (https://groups.google.com/forum/#!topic/physical-web-discuss/GX4uBO57Reg), a Google resource suggests that the way GPS initiates notifications has not changed (with MIN notification priority). This resource suggests that the way notifications are handled within the Lock Screen and Status Bar in 7.0+ is different. It is for this reason, that we no longer see Nearby Notifications in these UI components. For us - this is critical as we do not expect users to look for notifications within the drawer or Nearby app. We expect the phone to NOTIFY them when a beacon is received. It would be awesome if Scott Jenson could help with this issue as it is (we believe) critical to the adoption of Nearby and our products that leverage Nearby.

@mjanke67

This comment has been minimized.

Show comment
Hide comment
@mjanke67

mjanke67 Apr 12, 2017

I dug further to better understand Google's thinking on this matter and came across this interesting Scott Jenson interview on Youtube: https://www.youtube.com/watch?v=UbL7j7mvM9A

It is pretty clear in this interview that Google's intention for the Physical Web user experience is that users will walk into a space and look for Physical Web objects (including beacons) that are "Nearby" by dropping their Notification Drawer. They can then view and select Nearby Notifications. The implication is that the Status Bar / Notification Bar / Notification Area (too many labels for the same UI element) will not change to Notify the user when a Physical Web object has been scanned. And, of course, the Lock Screen will not Notify the user of any objects that have been scanned.

I suggest that this approach will only work when the Physical Web has been adopted by retailers, system integrators and others to an extent where many users are aware of the Physical Web and how it works and will expect Physical Web objects to be Nearby. Otherwise - why would they go looking for them and how would they know were to look for them on their Android devices. In the interview - it is clear that Google is taking the long view on Physical Web adoption and do not wish to alienate users by sending them too many notifications (i.e. when there are many Physical Web objects scannable nearby). I can understand their apprehension and I respect their desire to keep users happy. I also believe that their approach is feasible IF users (someday) understand how the Physical Web works and are able to view Nearby Notifications frequently within their drawer (otherwise why look). I would suggest that until that level of Physical Web adoption occurs, users simply won't drop their drawers to check for scanned Nearby objects. Ultimately, the Physical Web adoption may never grow because it has been setup for future and not current levels of adoption. To address this - it is key that users retain their ability to view Nearby Notifications in both the Status Bar and Lock screen. To ensure that users don't get offended by too many notifications, disable their display within the Lock Screen by default but give them the ability to enable notifications on the Lock Screen if they so desire. This same control (or another) could be used to enable display of an icon within the Status Bar when a notification has been added to the drawer. With this level of control in place, interested users can be shown or taught how to get notified by Physical Web objects. Disinterested users will leave Status Bar and Lock Screen notifications disabled (their default state) and will be unaffected.

Another key point that I would raise is that Nearby Notifications did exist within the original deployment of Nearby within Google Play Services (GPS) and were removed without warning after my company and others built product around the Nearby featureset. Removing original service features without discussion or warning is (choosing my words carefully) - very very uncool.

The last point that I think is worth mentioning is that the GPS notification controls (the controls on the "APP NOTIFICATIONS" configuration screen for GPS) are currently very misleading. The "On lock screen" control shows "Show content" even though GPS notifications are handled in a non-standard way and are blocked from this screen. Moreover, when viewing the Nearby Notifications within the Nearby app, they are always shown as "Muted" regardless of whether the user mutes, or unmutes these notifications. I have attached a couple of screen caps showing these misleading elements.
image
image

I hope that a conversation around how Nearby Notifications are handled within Android can occur and that Google is not set on the current approach.

Feedback from others with a vested interest in this topic can only help.

mjanke67 commented Apr 12, 2017

I dug further to better understand Google's thinking on this matter and came across this interesting Scott Jenson interview on Youtube: https://www.youtube.com/watch?v=UbL7j7mvM9A

It is pretty clear in this interview that Google's intention for the Physical Web user experience is that users will walk into a space and look for Physical Web objects (including beacons) that are "Nearby" by dropping their Notification Drawer. They can then view and select Nearby Notifications. The implication is that the Status Bar / Notification Bar / Notification Area (too many labels for the same UI element) will not change to Notify the user when a Physical Web object has been scanned. And, of course, the Lock Screen will not Notify the user of any objects that have been scanned.

I suggest that this approach will only work when the Physical Web has been adopted by retailers, system integrators and others to an extent where many users are aware of the Physical Web and how it works and will expect Physical Web objects to be Nearby. Otherwise - why would they go looking for them and how would they know were to look for them on their Android devices. In the interview - it is clear that Google is taking the long view on Physical Web adoption and do not wish to alienate users by sending them too many notifications (i.e. when there are many Physical Web objects scannable nearby). I can understand their apprehension and I respect their desire to keep users happy. I also believe that their approach is feasible IF users (someday) understand how the Physical Web works and are able to view Nearby Notifications frequently within their drawer (otherwise why look). I would suggest that until that level of Physical Web adoption occurs, users simply won't drop their drawers to check for scanned Nearby objects. Ultimately, the Physical Web adoption may never grow because it has been setup for future and not current levels of adoption. To address this - it is key that users retain their ability to view Nearby Notifications in both the Status Bar and Lock screen. To ensure that users don't get offended by too many notifications, disable their display within the Lock Screen by default but give them the ability to enable notifications on the Lock Screen if they so desire. This same control (or another) could be used to enable display of an icon within the Status Bar when a notification has been added to the drawer. With this level of control in place, interested users can be shown or taught how to get notified by Physical Web objects. Disinterested users will leave Status Bar and Lock Screen notifications disabled (their default state) and will be unaffected.

Another key point that I would raise is that Nearby Notifications did exist within the original deployment of Nearby within Google Play Services (GPS) and were removed without warning after my company and others built product around the Nearby featureset. Removing original service features without discussion or warning is (choosing my words carefully) - very very uncool.

The last point that I think is worth mentioning is that the GPS notification controls (the controls on the "APP NOTIFICATIONS" configuration screen for GPS) are currently very misleading. The "On lock screen" control shows "Show content" even though GPS notifications are handled in a non-standard way and are blocked from this screen. Moreover, when viewing the Nearby Notifications within the Nearby app, they are always shown as "Muted" regardless of whether the user mutes, or unmutes these notifications. I have attached a couple of screen caps showing these misleading elements.
image
image

I hope that a conversation around how Nearby Notifications are handled within Android can occur and that Google is not set on the current approach.

Feedback from others with a vested interest in this topic can only help.

@montelco

This comment has been minimized.

Show comment
Hide comment
@montelco

montelco Apr 12, 2017

@scottjenson I'm quite concerned by the direction of things. My company has put a lot of time and effort into making a platform for small businesses to spread awareness through the power of the Physical Web. I've found that users on Samsung devices are spotty at best with regard to notifications. Could you shed some light on how exactly the service determines how URLs are squashed? If a device is rather low to no traffic, will it just stop? How then would someone discover it? I can't help but to feel a bit concerned by this.

montelco commented Apr 12, 2017

@scottjenson I'm quite concerned by the direction of things. My company has put a lot of time and effort into making a platform for small businesses to spread awareness through the power of the Physical Web. I've found that users on Samsung devices are spotty at best with regard to notifications. Could you shed some light on how exactly the service determines how URLs are squashed? If a device is rather low to no traffic, will it just stop? How then would someone discover it? I can't help but to feel a bit concerned by this.

@curryrussell

This comment has been minimized.

Show comment
Hide comment
@curryrussell

curryrussell Aug 17, 2017

It FULLY appears that all notifications have completely stopped in Android again. Is anyone else seeing this? Or is your working?

It shows up in Nearby, just not in the notifications area.

curryrussell commented Aug 17, 2017

It FULLY appears that all notifications have completely stopped in Android again. Is anyone else seeing this? Or is your working?

It shows up in Nearby, just not in the notifications area.

@ferencbrachmann

This comment has been minimized.

Show comment
Hide comment
@ferencbrachmann

ferencbrachmann Aug 17, 2017

Works here. Although occasionally we experience quite similar issues.

ferencbrachmann commented Aug 17, 2017

Works here. Although occasionally we experience quite similar issues.

@limooi

This comment has been minimized.

Show comment
Hide comment
@limooi

limooi Aug 17, 2017

Mine's working here as well. Android 6.0.1

limooi commented Aug 17, 2017

Mine's working here as well. Android 6.0.1

@mjanke67

This comment has been minimized.

Show comment
Hide comment
@mjanke67

mjanke67 Aug 17, 2017

We have given up on the Physical Web. It no longer functions as a meaningful mechanism for notifying users that web content is available nearby.

We now support nearby notification for users using our own iOS and Android background apps (launched by beacons). This provides for a level playing field between iOS and Android, makes for simple user opt-in (everybody knows how to install and app quickly and painlessly) and gives us far better control of notifications. They show up everywhere along with audio and vibration ... even on the Always On Display on some phones including Samsung Galaxy S*.

mjanke67 commented Aug 17, 2017

We have given up on the Physical Web. It no longer functions as a meaningful mechanism for notifying users that web content is available nearby.

We now support nearby notification for users using our own iOS and Android background apps (launched by beacons). This provides for a level playing field between iOS and Android, makes for simple user opt-in (everybody knows how to install and app quickly and painlessly) and gives us far better control of notifications. They show up everywhere along with audio and vibration ... even on the Always On Display on some phones including Samsung Galaxy S*.

@craigahunter

This comment has been minimized.

Show comment
Hide comment
@craigahunter

craigahunter Aug 23, 2017

HI @scottjenson ive noted you've been a bit quite on the subject of the physical web lately. It's understandable that your a very busy guy so I respect that. As there are a few poeple still putting their time and other resources into this is it safe to say that the physical web is still progressing as their are a few people on here who seem to be giving up over a few issues.....or are you looking into these issues and ways of maybe addressing them. The main issues seems to be:

  1. Inconsistency with it working on devices
  2. Adoption of the physical web and the "dropping off" of undiscovered or unused beacon links (I would expect this to be a large amount at this stage and therefore counter intuitive . Could we please receive an update or some comments on your feelings about these issues at the moment. Thanks again

craigahunter commented Aug 23, 2017

HI @scottjenson ive noted you've been a bit quite on the subject of the physical web lately. It's understandable that your a very busy guy so I respect that. As there are a few poeple still putting their time and other resources into this is it safe to say that the physical web is still progressing as their are a few people on here who seem to be giving up over a few issues.....or are you looking into these issues and ways of maybe addressing them. The main issues seems to be:

  1. Inconsistency with it working on devices
  2. Adoption of the physical web and the "dropping off" of undiscovered or unused beacon links (I would expect this to be a large amount at this stage and therefore counter intuitive . Could we please receive an update or some comments on your feelings about these issues at the moment. Thanks again
@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Aug 28, 2017

Contributor

Sorry for my silence but I'm no longer working on the Chrome team and no longer working on the Physical Web project. This was obviously a big passion of mine and it's frustrating that i can no longer support you folks. I've always said that the Physical Web could only work if it was an open standard supported by many players. I strongly hope others continue with the Physical Web. The Eddystone standard isn't going anywhere and you can still find beacon URLs through Android Nearby.

Contributor

scottjenson commented Aug 28, 2017

Sorry for my silence but I'm no longer working on the Chrome team and no longer working on the Physical Web project. This was obviously a big passion of mine and it's frustrating that i can no longer support you folks. I've always said that the Physical Web could only work if it was an open standard supported by many players. I strongly hope others continue with the Physical Web. The Eddystone standard isn't going anywhere and you can still find beacon URLs through Android Nearby.

@craigahunter

This comment has been minimized.

Show comment
Hide comment
@craigahunter

craigahunter Aug 28, 2017

craigahunter commented Aug 28, 2017

@scottjenson

This comment has been minimized.

Show comment
Hide comment
@scottjenson

scottjenson Sep 18, 2017

Contributor

Chrome should have specified many months ago their intended direction on the Physical Web. While I can't speak for them any more, everyone in this community has pretty much figured out that it's clearly not a high priority item for them.

I've always said that the Physical Web project was 'free like the air' type of project. It was setup so that it could continue even if Google dropped support. So I do hope people understand that any Eddystone beacon can broadcast any URL and any scanner can find it. There is nothing stopping anyone from building experiments/research/products on top of this.

Of course, the value of using URLs (instead of fixed IDs tied to only your database) is that it encourages an inter-operable space. Most single projects won't likely get this value if they are just a 'one off' type of approach. What will really help is if a group of projects feel like having a common shared way to describe objects.

I still feel strongly in this approach, especially in AR and IoT use cases and will personally continue to explore this space.

Contributor

scottjenson commented Sep 18, 2017

Chrome should have specified many months ago their intended direction on the Physical Web. While I can't speak for them any more, everyone in this community has pretty much figured out that it's clearly not a high priority item for them.

I've always said that the Physical Web project was 'free like the air' type of project. It was setup so that it could continue even if Google dropped support. So I do hope people understand that any Eddystone beacon can broadcast any URL and any scanner can find it. There is nothing stopping anyone from building experiments/research/products on top of this.

Of course, the value of using URLs (instead of fixed IDs tied to only your database) is that it encourages an inter-operable space. Most single projects won't likely get this value if they are just a 'one off' type of approach. What will really help is if a group of projects feel like having a common shared way to describe objects.

I still feel strongly in this approach, especially in AR and IoT use cases and will personally continue to explore this space.

@oninross

This comment has been minimized.

Show comment
Hide comment
@oninross

oninross Sep 18, 2017

Hi @scottjenson, I tried finding any news or update about this. Couldn't find it :(

oninross commented Sep 18, 2017

Hi @scottjenson, I tried finding any news or update about this. Couldn't find it :(

@Himen007

This comment has been minimized.

Show comment
Hide comment
@Himen007

Himen007 Sep 20, 2017

Hi @scottjenson ,

We are developing a proximity marketing webpanel using Eddystone UID which is interacting with the google dashboard. We registered the Eddystone UID beacons from our panel to google dashboard with message and URL. So far it was working fine and we are able to get the near by notification in all our smart phone's near by app as well as in notification bar.

But suddenly we are now facing an issue like we are able to discover the URL and message for all the registered Eddystone UID beacons in near by app. but somehow the notification is not generated in the notification bar for all the Eddystone UID. We checked in different forum but we are not getting any help from that.

Can you please suggested what could be the issue.

Thanks,
Himen

Himen007 commented Sep 20, 2017

Hi @scottjenson ,

We are developing a proximity marketing webpanel using Eddystone UID which is interacting with the google dashboard. We registered the Eddystone UID beacons from our panel to google dashboard with message and URL. So far it was working fine and we are able to get the near by notification in all our smart phone's near by app as well as in notification bar.

But suddenly we are now facing an issue like we are able to discover the URL and message for all the registered Eddystone UID beacons in near by app. but somehow the notification is not generated in the notification bar for all the Eddystone UID. We checked in different forum but we are not getting any help from that.

Can you please suggested what could be the issue.

Thanks,
Himen

@dipbiswas

This comment has been minimized.

Show comment
Hide comment
@dipbiswas

dipbiswas Sep 26, 2017

Hi @Himen007,

Were you able to make these work? I am facing the exact same behavior as you described for the last few days. I had around 100 beacons in 1 project and they stopped showing up in the notification bar since a week.

I created a new project and added a beacon. It shows up both in the nearby app and in the notification bar. The ones in the older project show up only in the nearby app but not in the notification bar.

Like others in the group here, my use case is to show them in the notification bar.

dipbiswas commented Sep 26, 2017

Hi @Himen007,

Were you able to make these work? I am facing the exact same behavior as you described for the last few days. I had around 100 beacons in 1 project and they stopped showing up in the notification bar since a week.

I created a new project and added a beacon. It shows up both in the nearby app and in the notification bar. The ones in the older project show up only in the nearby app but not in the notification bar.

Like others in the group here, my use case is to show them in the notification bar.

@ferencbrachmann

This comment has been minimized.

Show comment
Hide comment
@ferencbrachmann

ferencbrachmann Sep 26, 2017

@dipbiswas Do you use URL shortener?

ferencbrachmann commented Sep 26, 2017

@dipbiswas Do you use URL shortener?

@dipbiswas

This comment has been minimized.

Show comment
Hide comment
@dipbiswas

dipbiswas Sep 26, 2017

@ferencbrachmann, Yes. We use EddystoneUID and some of these beacons use URL shorteners.

dipbiswas commented Sep 26, 2017

@ferencbrachmann, Yes. We use EddystoneUID and some of these beacons use URL shorteners.

@ferencbrachmann

This comment has been minimized.

Show comment
Hide comment
@ferencbrachmann

ferencbrachmann Sep 26, 2017

Do you have your own shortener or use some existing service?

ferencbrachmann commented Sep 26, 2017

Do you have your own shortener or use some existing service?

@dipbiswas

This comment has been minimized.

Show comment
Hide comment
@dipbiswas

dipbiswas Sep 26, 2017

dipbiswas commented Sep 26, 2017

@dipbiswas

This comment has been minimized.

Show comment
Hide comment
@dipbiswas

dipbiswas Sep 26, 2017

dipbiswas commented Sep 26, 2017

@dipbiswas

This comment has been minimized.

Show comment
Hide comment
@dipbiswas

dipbiswas Sep 26, 2017

  • still NOT showing up.

dipbiswas commented Sep 26, 2017

  • still NOT showing up.
@Himen007

This comment has been minimized.

Show comment
Hide comment
@Himen007

Himen007 Sep 27, 2017

Hi @dipbiswas,

No we are still not getting any solution. we follow the same steps as you done like creating a new project and added all the beacon into that project. and delete the old beacon from old project and also delete the project from google console.

Hope we can get some more info from @scottjenson.

Thanks,
Himen

Himen007 commented Sep 27, 2017

Hi @dipbiswas,

No we are still not getting any solution. we follow the same steps as you done like creating a new project and added all the beacon into that project. and delete the old beacon from old project and also delete the project from google console.

Hope we can get some more info from @scottjenson.

Thanks,
Himen

@craigahunter

This comment has been minimized.

Show comment
Hide comment
@craigahunter

craigahunter Sep 27, 2017

craigahunter commented Sep 27, 2017

@koenschauwaert

This comment has been minimized.

Show comment
Hide comment
@koenschauwaert

koenschauwaert Sep 28, 2017

@oninross

I have verified your link in:
https://beaufortfrancois.github.io/sandbox/physical-web/url-validator/
and it seems to be a validate link.

But as far as I know Google Nearby only works with HTTPS links.
Could you please use the goo.gl shortener? This one uses the HTTPS protocol.
I have had some sort of the same issue with my URL.

koenschauwaert commented Sep 28, 2017

@oninross

I have verified your link in:
https://beaufortfrancois.github.io/sandbox/physical-web/url-validator/
and it seems to be a validate link.

But as far as I know Google Nearby only works with HTTPS links.
Could you please use the goo.gl shortener? This one uses the HTTPS protocol.
I have had some sort of the same issue with my URL.

@cgslaughter

This comment has been minimized.

Show comment
Hide comment
@cgslaughter

cgslaughter Oct 12, 2017

This problem comes and goes for us. Currently trying to setup 20 beacons. For two days we have setup the beacons the same way we have been, Beacon Tools see them on my Pixel and my Nexus 5, but Nearby on my Pixel will not see it, nor is it seen by Nexus 5. Sometimes it comes down to needing to send the URLs through the Physical Web Validator a few times and somehow that magically can start to make them work. (Some sort of caching issue on Google's backend?)

We use goo.gl, all urls are HTTPS.
Tried updates to the phones
Turning tons of settings on and off
Different devices, about 10 of them

It all points to an issue on the backend as far as we can tell. It is hard to use something that only works sometimes.

cgslaughter commented Oct 12, 2017

This problem comes and goes for us. Currently trying to setup 20 beacons. For two days we have setup the beacons the same way we have been, Beacon Tools see them on my Pixel and my Nexus 5, but Nearby on my Pixel will not see it, nor is it seen by Nexus 5. Sometimes it comes down to needing to send the URLs through the Physical Web Validator a few times and somehow that magically can start to make them work. (Some sort of caching issue on Google's backend?)

We use goo.gl, all urls are HTTPS.
Tried updates to the phones
Turning tons of settings on and off
Different devices, about 10 of them

It all points to an issue on the backend as far as we can tell. It is hard to use something that only works sometimes.

@craigahunter

This comment has been minimized.

Show comment
Hide comment
@craigahunter

craigahunter Oct 12, 2017

craigahunter commented Oct 12, 2017

@MarkCasiano

This comment has been minimized.

Show comment
Hide comment
@MarkCasiano

MarkCasiano Oct 12, 2017

MarkCasiano commented Oct 12, 2017

@mmocny

This comment has been minimized.

Show comment
Hide comment
@mmocny

mmocny Oct 12, 2017

Collaborator

Interesting observations. To me this hints at scanning issues? Are you able to detect the beacon using a bluetooth scanning tool, or even just the Nearby list?

Even that test isn't a fair test, since using a high powered foreground scan can change the test results of the low power background scan, but it may give some clues.

Collaborator

mmocny commented Oct 12, 2017

Interesting observations. To me this hints at scanning issues? Are you able to detect the beacon using a bluetooth scanning tool, or even just the Nearby list?

Even that test isn't a fair test, since using a high powered foreground scan can change the test results of the low power background scan, but it may give some clues.

@cgslaughter

This comment has been minimized.

Show comment
Hide comment
@cgslaughter

cgslaughter Oct 13, 2017

I am able to detect the beacons with other scanning tools no problem.

I tried MarkCasiano's and craigahunter's observations to see if that would make a difference for us, but it did not.

cgslaughter commented Oct 13, 2017

I am able to detect the beacons with other scanning tools no problem.

I tried MarkCasiano's and craigahunter's observations to see if that would make a difference for us, but it did not.

@MarkCasiano

This comment has been minimized.

Show comment
Hide comment
@MarkCasiano

MarkCasiano Oct 13, 2017

MarkCasiano commented Oct 13, 2017

@craigahunter

This comment has been minimized.

Show comment
Hide comment
@craigahunter

craigahunter Oct 13, 2017

craigahunter commented Oct 13, 2017

@Moreiq

This comment has been minimized.

Show comment
Hide comment
@Moreiq

Moreiq Nov 4, 2017

It seems that nearby notification are sporadic and do not follow any logic if not used via an APP.

Moreiq commented Nov 4, 2017

It seems that nearby notification are sporadic and do not follow any logic if not used via an APP.

@santoshbadabade

This comment has been minimized.

Show comment
Hide comment
@santoshbadabade

santoshbadabade Dec 1, 2017

Hello everyone,
I am working with Eddystone url notification working fine.
but after 2min that notification will be not show in notifiaction bar. I am using the SAMB11 controller.
and another is when show notification that time no sound come or no vibration. user dont undestand the that eddystone url is come.

santosh

santoshbadabade commented Dec 1, 2017

Hello everyone,
I am working with Eddystone url notification working fine.
but after 2min that notification will be not show in notifiaction bar. I am using the SAMB11 controller.
and another is when show notification that time no sound come or no vibration. user dont undestand the that eddystone url is come.

santosh

@hulkco

This comment has been minimized.

Show comment
Hide comment
@hulkco

hulkco Apr 6, 2018

Hello everyone, I am working with EddyStone URL, and I have found that notices for URLs with the "HTTP" protocol are simply not shown, only those that have "HTTPS", even if they are masked under a URL shortener.

hulkco commented Apr 6, 2018

Hello everyone, I am working with EddyStone URL, and I have found that notices for URLs with the "HTTP" protocol are simply not shown, only those that have "HTTPS", even if they are masked under a URL shortener.

@ferencbrachmann

This comment has been minimized.

Show comment
Hide comment
@ferencbrachmann

ferencbrachmann Apr 6, 2018

@hulkco Please read this: http://blog.beeem.co/2018/02/the-ultimate-nearby-notification-troubleshooting-guide/

The end URL (and all resources on it as well!) requires HTTPS exclusively.

ferencbrachmann commented Apr 6, 2018

@hulkco Please read this: http://blog.beeem.co/2018/02/the-ultimate-nearby-notification-troubleshooting-guide/

The end URL (and all resources on it as well!) requires HTTPS exclusively.

@hulkco

This comment has been minimized.

Show comment
Hide comment
@hulkco

hulkco Apr 6, 2018

Thanks @ferencbrachmann, with this article it is more clear to me how to configure the beacons !!

hulkco commented Apr 6, 2018

Thanks @ferencbrachmann, with this article it is more clear to me how to configure the beacons !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment