Thread: [SailfishOS] [Announce] Rockpool - Pebble daemon for Sailfish
View Single Post
ruff is offline ruff
2016-07-17 , 09:05
Posts: 207 | Thanked: 482 times | Joined on Mar 2016
#455
The only difference I found between android and rockpool is that rockpool spams with phone progress messages while android just switches states. So if pebble internally lacks state machine implementation - such flood may cause it to hang/crash/reset
Eg. this is android session
Code:
Canceled:
I> 0016002104e48b9d12xxxxxxxxxxxxxxxxxxx
H< 0005002102e48b9d12
E> 0005002109e48b9d12

Answered:
I> 0016002104de290d48xxxxxxxxxxxxxxxxxxx
S> 0005002108de290d48
E> 0005002109de290d48
And this is rockpool
Code:
Canceled:
PhoneEndpoint> "045cd90b8dxxxxxxxxxxxxxx" 
PhoneEndpoint< "025cd90b8d" 
PhoneEndpoint> "095cd90b8d" 
PhoneEndpoint> "095cd90b8d" 

Answered:
PhoneEndpoint> "044e5bf8f8xxxxxxxxxxxxx" 
PhoneEndpoint> "084e5bf8f8" 
PhoneEndpoint> "084e5bf8f8" 
PhoneEndpoint> "084e5bf8f8" 
PhoneEndpoint> "094e5bf8f8"
So need to implement internal state machine in endpoint. Which means it would not support concurrent calls. Otherwise with dynamic call list - that list will be trashed with garbage over time.
Or actually state track could be implemented in platform which has visibility on active calls, so can clean up the mess.
Last edited by ruff; 2016-07-17 at 09:14.
 

The Following 4 Users Say Thank You to ruff For This Useful Post: