Fix handling of startup_timer_expired
1. The startup_timer needs to be less than 3 sec to allow the wakelock to be held by the stack and needs to be less than the BLE_START_TIMEOUT of framework. 2. On expiry of startup_timer, just abort as there is no proper recovery steps here. Bug: 129394377 Change-Id: I1a397bab5c88fe7ef8ccbc369897903ee5d0a36a
Loading
Please register or sign in to comment