SAP: Avoid having multiple active SapServers instances
It turns out that the shutdown procedure can take along time,
which causes the race between shutting down and freeing resources,
and accepting a new connect request.
This fix waits for the shutdown procedure complete before allowing
a new incomming connection.
Additionally handling of serivce shutdown while connected - e.g.
BT off is fixed.
Messaghandler changed to use it's own thread, as during shutdown
the default messagehandler occationally stops handling messages.
By using a looper from a HandlerThread instance, this issue no
longer exists.
SAP: Fix below issues during internal testing
1. Remove wait for shutdown to complete on main
thread. Perform cleanup for handler and quit
looper from closeService running on worker
thread on first SHUTDOWN message.
Check and allow posting of SHUTDOWN message
only if later doesnt not already exists in
mSessionStatusHandler message queue.
2. Change timeout from 25 sec to 30 secs as
per the standards.
3. Add debug and verbose logs whereever needed.
Change-Id: I780e197350a4c265c15adfbcdf23f6dc4e184bd3
4 files changed