search

NordicSemiconductor / Nordic-Thingy52-FW

Nordic Thingy:52 software development kit. This kit is designed to assist users in developing their own custom firmware for Thingy. Please see http://www.nordicsemi.com/thingy for the latest news and software releases.
Other
210 stars 133 forks source link

Does not work #20

Open ImmortalBuka opened 6 years ago

ImmortalBuka commented 6 years ago

Thingy disconnected after discovering serices

koffes commented 6 years ago

Hi! Great if you can provide some more detail. Did it disconnect from your PC or a mobile phone? Does it happen every time? Do you know what version of the firmware you are using?

ImmortalBuka commented 6 years ago

From phone (honor 7lite, android 7.0), when i use thingy app, web app, nrf connect mobile app. It happens every time. i tried with 2.0.1 and 1.0.0 fw versions.

koffes commented 6 years ago

If you are able to upgrade, use the newest firmware (at time of writing this is 2.1.0 on Thingy:52). Also make sure that nRF Connect is completely shut down when using the Thingy app. After a phone reboot, does the same thing happen? Are you able to test with another phone or PC/tablet?

ImmortalBuka commented 6 years ago

2.1.0 doesn't work too. After phone reboot it works, but once, until first disconnect.

koffes commented 6 years ago

Since this happens inn all three apps and it works after a phone reboot this seems like the issue is phone related. We have tested Thingy:52 with a wide array of phones and have not seen this issue.

koffes commented 6 years ago

Perhaps some phone logs can help us find out more. I'd recommend you post a detailed question on https://devzone.nordicsemi.com/questions/ where we can assist you further.

ImmortalBuka commented 6 years ago

m_ui :INFO:BLE connected m_ui :INFO:Mode: BLE_UIS_LED_MODE_BREATHE m_ble :INFO:on_ble_evt: BLE_GAP_EVT_CONNECTED main :INFO:Thingy_ble_evt_connected m_ble :INFO:on_conn_params_evt: BLE_CONN_PARAMS_EVT_SUCCEEDED main :INFO:Voltage: 4110 V, Charge: 92 %, Event type: 0 m_ble :INFO:on_conn_params_evt: BLE_CONN_PARAMS_EVT_SUCCEEDED advbeacon...:INFO:app_beacon_on_sys_evt: 5 advbeacon...:INFO:app_beacon_on_sys_evt: 5 advbeacon...:INFO:app_beacon_on_sys_evt: 5 m_ui :INFO:BLE disonnected m_ui :INFO:Mode: BLE_UIS_LED_MODE_BREATHE m_ble :INFO:on_ble_evt: BLE_GAP_EVT_DISCONNECTED. Reason: 0x8

joakimtoe commented 6 years ago

Hi! How long does it stay connected before it disconnects? Could this be an issue with connection parameters? What connection parameters do you use?

Best regards, Joakim

ImmortalBuka commented 6 years ago

i think, it caused by (ex)change MTU size