Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check browser capabilities in standby mode #6

Open
4 tasks done
capital-G opened this issue Feb 18, 2022 · 7 comments
Open
4 tasks done

Check browser capabilities in standby mode #6

capital-G opened this issue Feb 18, 2022 · 7 comments
Assignees
Labels
concept a place for meta discussion

Comments

@capital-G
Copy link
Member

capital-G commented Feb 18, 2022

Currently it is unclear if for iOS/Android

  • the browser still receives webRTC on standby
  • sends GPS on standby
  • under which cases the OS just closes down the browser
  • are tab switches allowed?

Please extend :)

@capital-G capital-G added the concept a place for meta discussion label Feb 18, 2022
@capital-G capital-G added this to the Level 3 milestone Feb 18, 2022
@vin-ni
Copy link
Member

vin-ni commented Mar 17, 2022

I will be testing gps throughput in a custom environment with a quick node server and socketIO connection.
What about the webrtc testing? Should i just play the demo and play around to see if stream turns off in some cases?

Interesting stuff will be continuing the stream from the control center after listening to some music or getting a call.

@vin-ni vin-ni removed this from the Level 3 - dynamic streaming milestone Nov 8, 2022
@vin-ni vin-ni added this to the MVP Ralph III milestone Jan 14, 2023
@capital-G capital-G modified the milestones: MVP Ralph III, Drifter May 10, 2023
@capital-G
Copy link
Member Author

@vin-ni will do a check with standby and gps transmissions and update of stream variables

@capital-G capital-G modified the milestones: Drifter, MLB 3 May 31, 2023
@capital-G
Copy link
Member Author

Lets create a script which logs all GPS variables

@capital-G
Copy link
Member Author

Some research today

Screen on

Number of events that are received on the server - latitude and longitude is transferred individually

image

No dropouts

image

Every 1 to 2 seconds we receive an update.

image

It takes around 30s to get really accurate results (yscale is log!)

image

Heading seems sometimes reliable - have in mind that the skips occur on the 360 to 0 crossover, unwrapping them reveals this

image

Unwrapping the values reveals that they are indeed useful.

image

Plotting the long/lat on a map results in this nice plot

image

Which is much more accurate than I would have thought.

@vin-ni
Copy link
Member

vin-ni commented Jul 5, 2023

Amazing!
Yes, we're using the "accurate" flag for gps I believe.

@capital-G
Copy link
Member Author

Sadly GPS does not work/update if the screen is locked :/

So microphone and GPS is not working if the screen is locked.
This could probably be circumvented through a native app.

image

image

The first half is completely missing, I turned the screen on for the 2nd half

image

@capital-G
Copy link
Member Author

ToDo @vin-ni

@vin-ni vin-ni removed this from the MLB 3 milestone Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
concept a place for meta discussion
Projects
None yet
Development

No branches or pull requests

2 participants