If you enable traces it may give us some clue as to what is happening.
extern UINT32 blecm_configFlag ;
blecm_configFlag |= BLECM_DBGUART_LOG | BLECM_DBGUART_LOG_L2CAP | BLECM_DBGUART_LOG_SMP;
currently I'm working to another task, because I was locked on this.
I'll try a comparison with Walk trough application behaviour.
If also in this case there are not notification, then I'll send you the log.
Thank you for support
we restarted working on that issue and we found sources of problem:
1) Notification subscription is not synchronous and there is no callback confirming that subscription had success. For that reason if APP subscrives to several notifications only last request has success, others are overwritten. Note that function immediately returns success, but operation is not yet done.
Solution: software delay after subscription.
2) Even solving problem1 ther is a 7 characteristics subscription limit into this OS. If APP subscrives to more of 7 notifications simply last subscriptions have no effect.
Regarding problem 2:
Does anyone know if this 7 notification limit is related to a single service or if it's a global limit?
In first case I coult split mi service in several services, each with less than 7 characteristics with notification.
Sorry, we don't know the notification limit on Android.