"Error 133 occurred" when try to connect to the beacon

[laurijamsa]

When using Samsung Galaxy S7 Edge, error 133 shows up every time. Galaxy S5 connects successfully sometimes, but not always. This happens with your HEX file: https://github.com/NordicSemiconductor/nrf5-sdk-for-eddystone/blob/master/hex/nrf5_sdk_for_eddystone_v0.5.hex

I get the same result with both HWs: PCA10040 and our open-source sensor beacon platform: http://ruuvitag.com

[roshanrajaratnam]

Hi we will try to look in to this tomorrow. Have you tried turning on/off your Bluetooth on the edge?

[laurijamsa]

Yes I have. No help.

[roshanrajaratnam]

@laurijamsa currently im testing with a Galaxy S7 and it seems to keep happening too often on samsung s7 particularly. S5 seems to be much better on establishing the connection. However this is not the case with Nexus devices. I will debug more and get back to you on this.

[laurijamsa]

Please also note that I was having similar problems (GATT error if I recall correctly) with nRF Toolbox (DFU OTA) & S7 Edge. S5 is working fine. DFU OTA is working with S7 Edge + Master Control Panel, but not with Toolbox.

I didn't create an issue (yet) but I can create one if you ask me to. Seems that there are some unresolved ones (why's that?), but no new ones: https://github.com/NordicSemiconductor/Android-nRF-Toolbox/issues

[roshanrajaratnam]

Yeah we had done a lot of digging on this and the only reason we could come up with is that this is an issue related to the android bluetooth stack since 4.3. I've just looked it up and there is an issue on the android but is a very Generic error with very little explanation as to what the real cause is or could be.

But there is another work around if it helps you and that would be to go in to application manager >> >> Bluetooth share (if not visible enable show system apps from the options menu) >> and clear data and this should help you to connect to the beacon as this just worked for me.

[roshanrajaratnam]

@laurijamsa have you had any success with this issue?

[laurijamsa]

@roshanrajaratnam Now I have connected successfully using S7 Edge. However, it still fails almost every time.

BTW, not sure if the parameters should be configurable already or is it TBD? If I modify a Tx power for example, it doesn't save the new value. And URL is static. Why is this?

[roshanrajaratnam]

@laurijamsa I am currently looking more in to the 133 error. Parameters are configurable except for the advanced characteristics as they are not supported in the firmware yet.

The Tx power is configurable and if you look in to broadcast capabilities it lists the Tx powers that are supported by the firmware. it is configurable with the values listed there....but it's my bad and there will be a new feature release pretty soon with a drop down so that it lists the supported Tx powers in a drop down menu to be configured. :)

What do you mean by the URL is static? The URL that's currently there on the firmware is just the Nordic Semiconductor URL but you can configure it to anything you want.

You can configure any slot in to any frame type you wish. In case you want to configure it in to a URL beacon simply pick the URL frame type from the drop down. You can put in your own URL which should be less than 18 bytes and if not you can use the shorten URL feature to put in a shortened URL.

I'm testing it on my end it seems to be working right now. Let me know how it goes!

[laurijamsa]

Oh, I just didn't know how to use the app correctly. The URL modification seems to work without problems. Good work!

[roshanrajaratnam]

that sounds good! :) and that's a cool beacon!

[laurijamsa]

Thanks! We are working hard to make it available soon :)

[laurijamsa]

I made some tests with the new hex file you released an hour ago:

https://github.com/NordicSemiconductor/nrf5-sdk-for-eddystone/blob/master/hex/nrf5_sdk_for_eddystone_v0.6.hex

and so far haven't seen Error 133 with S7 Edge. Connects every time. Nice!

[roshanrajaratnam]

This is good news! we have added a line to update the connection parameters so the android device will try to fit in to the connection parameters of the firmware application. This was something happening mainly on Samsung devices so I guess I will close this issue and on a separate note I would like to have a play around with your ruuvitag if possible. Also just to let you know there is a new version released with the Tx power fix and let us know how it goes!