jfaltis

I can observe the same behavior when using multiple monitors. @minhajsixybte Did you find a solution? @windwp Does this script work for you with multiple monitors?

I would suggest using a different string than '%' maybe even just 'fill', 'remaining' or a clever character representation. '%' could be used later on for percentage distribution if it...

@Rigellute I think it's difficult to implement the second solution since we would need to handle the authentication with spotify.com (username, password). Even if we reliably reconstruct the requests for...

@Rigellute That would be a nice solution but I don't know if it is possible to cancel io::stdin().read_line from the webserver thread when a GET request is received.

> If you end the call, what are you doing about the native dialler call > logs? Isn't the call recorded there? What is the architecture of your > app...

I wanted to test if the implementation of `backToForeground()` of the other library (https://github.com/doneservices/flutter_callkeep) can open the app when it was killed but I could not get it running in...

> I read up on the flag used to do this on the android native side, and the app needs to be running as it's moved up the activity stack....

Hi @aponski, I am doing all the initialization of callkeep in the onBackgroundMessage because doing it somewhere else did not properly work for me. ``` static Future onBackgroundMessage( Map message,...

@aponski I am happy to help you :) Yes I guess that is the only thing we have to figure out to make it work reliably on Android. But I...

> @jfaltis Here is a nice summary of what’s working regarding notifications on Android and iOS: [link](https://medium.com/@sylvainduch/firebase-messaging-catch-them-all-3f9c594734d7). On iOS I think the only way is to use voip notifications (Apple...