search

crownstone / bluenet

Bluenet is the in-house firmware on Crownstone hardware. Functions: switching, dimming, energy monitoring, presence detection, indoor localization, switchcraft.
https://crownstone.rocks
91 stars 62 forks source link

Samsung S5 "within range" functionality stops working #31

Closed mrquincle closed 5 years ago

mrquincle commented 7 years ago

A Samsung S5 smartphone stops with the functionality that is about getting in and out of range.

There might be several reasons:

AlexDM0 commented 7 years ago

Does it work only once in the background (turns off but does not turn on again)? iOS had this issue and that's now fixed in the app.

On Mon, Jan 9, 2017 at 9:13 PM, Anne van Rossum notifications@github.com wrote:

A Samsung S5 smartphone stops with the functionality that is about getting in and out of range.

  • On (immediately)
  • Off (after 2 minutes)

There might be several reasons:

  • Somehow a certain sleep mode (dozing, app standby) might put the app in such a state that it doesn't perform certain functionality, be it scanning, be it connecting: https://developer.android.com/ training/monitoring-device-state/doze-standby.html https://developer.android.com/training/monitoring-device-state/doze-standby.html
  • The service that is running in the background stops.
  • The service that is running in the background stops and restarts, but it doesn't restart the complete app.
  • The Android OS turns off certain BLE functionality if it feels like it.
  • There is some kind of BLE error that is triggered rarely and screws up the connection state in the app.
  • There is a connection set up with a Crownstone that is not disconnected.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/crownstone/bluenet/issues/31, or mute the thread https://github.com/notifications/unsubscribe-auth/AFHWTcWgL7BUl_ilM4mMaHrlHoWjYjJsks5rQpTTgaJpZM4LerbR .

mrquincle commented 7 years ago

It rarely responds to anything.

I propose some kind of mechanical construction where a Faraday box is placed on top of a smartphone once every 5 minutes, so in an hour there should be 12 x 2 switches in a connected light and in a working day there should be 24 x 8 events. Then the reliability can be assessed a bit.

vliedel commented 7 years ago

With the foreground service, I have never seen the service being killed yet. What does happen though, is that bluetooth scanning spits an error and simply stops working (similar to https://code.google.com/p/android/issues/detail?id=173991), this is often accompanied by connect error 257. People seem to advice to simply turn off and on bluetooth programmatically, but i'm trying to find the error in the hci log first.

mrquincle commented 5 years ago

This will be changed (and very likely solved) with the next firmware update that will have the Crownstone scan for broadcasting devices rather than the phone scan for broadcasting Crownstones.