Implemented advanced settings screen (buffering and HTTP settings)

[bitlinker]

Hi! Please take a look at this implementation of additional network settings screen. It allows to configure ExoPlayer's streaming buffers size and to add aditional parameters to HTTP requests: User-Agent and other header values (some streaming hosts require specific values)

Also please note the fixes at PlayerViewModel:46 and PlayerViewModel:52. The settings repo is "preheated" here, but it seems not enough: When the player is created PlayerActivity.kt:288, the settings are not available yet and default ones are used! I know that runBlocking() is ugly, but can't find better solution here. It shouldn't actually block the thread since the preferences flow should already have value available.

[anilbeesetti]

Hey @bitlinker can you fix linting by running the following cmd in terminal ./gradlew ktlintFormat

[bitlinker]

Hey @bitlinker can you fix linting by running the following cmd in terminal ./gradlew ktlintFormat

Done

[anilbeesetti]

Hey @bitlinker, thanks for the pull request. I couldn't play local videos now. I believe it's because we're setting DefaultHttpDataSource as the default data source for ExoPlayer. We should only set the DefaultHttpDataSource if the URI is a network URI. And I think we should rename network settings screen to advanced settings screen, What do you think?

[bitlinker]

Hey @bitlinker, thanks for the pull request. I couldn't play local videos now. I believe it's because we're setting DefaultHttpDataSource as the default data source for ExoPlayer. We should only set the DefaultHttpDataSource if the URI is a network URI. And I think we should rename network settings screen to advanced settings screen, What do you think?

Hey @anilbeesetti, sorry I didn't checked the local videos last time. Yes, the issue was with the data source configuration - the DefaultDataSource.Factory is responsible for selecting required data sources based on URI scheme, but DefaultHttpDataSource.Factory was used instead. It is working now for both local and network streams.

I agree, advanced settings is more suitable name here, since buffer configurations are applied to local videos too. Renamed it.

[bitlinker]

Fixed ktlint =)

[SerpentDash]

Any updates on this one? This could be a good starting point for future improvements, such as allowing developers to pass HTTP headers in Intents.

Would love to pass headers like referer or UA in Intent to allow steaming some specific websites (as already said, some of them needs "special treatment" to work properly).