- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I install wiced android app in my smartphone, my android is 4.3 JWR66V.
I can use this app to connect with 20732 tag and get the exposed service from hello_sensor.
bletrace like this:
hello_sensor_timeout:140
bleprofile_connUp()
BLE_no_adv
BLE_idleconn:timer(3)
hello_sensor_connection_up: 98d6f7b62c9e 64
BLE_no_adv
profile:idletimer stopped
hello_sensor_timeout:141
But sometimes, my app can't get exposed service because these information appear in bletrace:
hello_sensor_timeout:115
bleprofile_connUp()
BLE_no_adv
BLE_idleconn:timer(3)
hello_sensor_connection_up: 98d6f7b62c9e 64
BLE_no_adv
profile:idletimer stopped
smp conn down
bleprofile_connDown()
bleprofile_connDown stop Idle Timer
hello_sensor_connection_down:98d6f7b62c9e handle:64
BLE_low_un_adv:timer(1)
ADV start: 000000000000
hello_sensor_timeout:116
what does cause the connection fragmentized? why connection was broken immediately after connection just established?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is really hard to say why connection goes down without the peer traces, or over the air traces. Can you please try to call emconinfo_getDiscReason in the connection_down callback. It might give us some clue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Does any one answer my question?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is really hard to say why connection goes down without the peer traces, or over the air traces. Can you please try to call emconinfo_getDiscReason in the connection_down callback. It might give us some clue.