[axbmcuser]

@Thomas_AR

Found the reason: On Android, opening the webbrowser via python has to be done using an Android specific way.

I'll rework some of the Trailer button(s) skin settings while at it and change some code for the trailer search.

Will let you know when there are changes you could test on a new version.
Don't know when i'll finish it since i'm very on/off with development at the moment.
But i think it'll be between a few weeks to winter time at the lastest. :-)

[Thomas_AR]

@axbmcuser

That's great news. Count on me for testing.
Thank you
Thomas

[axbmcuser]

@Thomas_AR

Please do some testing on Android & new Kodi 21+ skin version 6.7.42 when you find the time.
Please test both "default browser" and also "custom browser" which let's you choose between 3 common and typical values on Android.

Thanks & cheers

[axbmcuser]

New releases Kodi versions 21-22 are now online (17-20 will be following)

Code:

6.7.42 (2024-10-31)

Optimized default scrolling duration for textbox (Increased duration. Mostly affects Text Viewer dialogs)

My Skin:

Reworked "Trailer" and "Trailer Search" button options
"Trailer Search method" "Open in Web Browser" functionality has been reworked and also is now supported on Android (Beta, tbc)

Minor improvements for wall view label variables (Now identical for all wall views)

Language strings and text formatting improvements

Textures:

Further refinements to DefaultAddonInputstream.png, DefaultAddSource.png, DefaultMusicRecentlyAdded.png, DefaultRecentlyAddedEpisodes.png, DefaultRecentlyAddedMovies.png, DefaultRecentlyAddedMusicVideos.png, GoFullscreen.png

Slightly improved DefaultAddonsRecentlyUpdated.png and DefaultAddonsUpdates.png (smaller dots)

[axbmcuser]

@Thomas_AR

Hmm. Just got my hand on a random FireTV with Kodi 21 and opening the Browser does not work on this despite the new code.
Maybe you'll get the same results. Keep me posted.

Will investigate further.

[Thomas_AR]

@axbmcuser

Thank you for the update.
The option "default browser" isn't working.
Chosing custom browser "Chrome" works perfect.

Thanks

[axbmcuser]

@Thomas_AR

Oh. That's very interesting to know.
I'll see what i can do with that info and more testing on a Fire TV device.

Well, i guess. If you're fine with Chrome it's good that it's working with that for now. :-)

Would it be possible for you to install firefox and test if that one is also working with Custom Browser & Firefox option?

Still would like to find out why the other options don't work as expected. We'll see.

[Thomas_AR]

@axbmcuser

I will install Firefox and let you know.

P.S.
Firefox working flawless.

There seems to be a little glitch.
In order to see the TRAILER SEARCH button in the skin, first the TRAILER button has also to be activated. Reloading the skin, will show both buttons. Than deactivate the TRAILER button, to see only the TRAILER SEARCH button.

[axbmcuser]

@Thomas_AR

topic 1)
Thanks for the Firefox test with seemingly working results. That's helpful.
I think android application IDs like "com.android.browser" might only work on some devices.
With the latest information i think it might be best to offer a few common IDs to choose from (like it's already the case now) and also make it possible to enter a user defined application ID for the countless browsers and variants there are on android. This should then cover every possibility.

topic 2)
I couldn't exactly reproduce what you described, but i can confirm that i have missed to add the visibility condition for the "Trailer Search" button which is hideable since the discussed recent update. I'll add the condition - this might fix what you have described in one go.

[axbmcuser]

@Thomas_AR

I just releaed version 6.7.43 - you'll want to have a look again into the settings since i switched the custom browser option around for Android.

To achieve the same result as before, you'll have to change back to "Default Browser" and then select "com.android.chrome" in the list (now the 2nd option in the preset browser list)


Also, "Custom Browser" now adds the possbility to enter a custom ID.

You could contribute some more testing if you try that one, too, maybe by entereing IDs like

com.sec.android.app.sbrowser
(which might be Samsungs default web browser?)

you could also try the identical ID that chrome has in the preset-list:

com.android.chrome
(just to confirm the custom ID feature works at all if the Samsung test does not work)

[Thomas_AR]

@axbmcuser

I make it short.
Everything including custom ID, tested with Samsung Browser, is working perfect.

One more thing.
Is it possible to skin the player itself?
Missing the function, like in VLC, double click (touch) right jump's the video 10 sec forward, double click (touch) left moves the video 10 sec back.
It's hard to scroll the video forward or back with the small progress bar.

Thanks

[axbmcuser]

@Thomas_AR

Browser:

Thanks for the testing.
I also did some testing on a Fire TV finding out and verifiying the ID for the Amazon Fire TV default browser (Silk).
I will release another version with a total number of 8 preset Android browser IDs (including the Samsung) and i will also keep the custom ID option which seems to work fine for any further browser variants a user might need one day.
With that next release we will be done with the browser stuff, i think. :-)


Touch 10sec Skip :

Do you really mean "skin the player" in any sense of a visual change?
What you describe sounds more like functional only. Just asking to be sure.

First thing coming to mind:

I don't have real experience with touch-use of Kodi.
I would suspect it has some touch gesture compatbility in the Kodi keymaps?
I looked at the touchscreen.xml keymaps which seems to have a mapped "swipe right" to "StepForward" and "swipe left" to "StepBack" when being in fullscreen video.
Side note: I'm a big fan of having Kodis video skip steps set to "-30 sec, -10 sec, 10 sec, 30 sec" which would lead to a quick swipe left or right to a +-10 sec jump.
Is this gesture already working?

I understand you described an exact left/right half double click, but let's clarify the above first.

Cheers


Edit:
I got my hand on some old Android phone to also install Kodi there so i can verify what we might be talking about.

[axbmcuser]

@Thomas_AR

Further side question:
- Am i correct, your Samsung phone quite a bit wider than 16:9 aspect ratio? (my test device is too)
- Am i correct to assume that this means, that the skin triggers the ultra-wide-screen changes i implemented months ago, meaning: The skin is displayed without stretching, but you have a left and right black area while the skin is kept at a 16:9 ratio?
(Besides when switching to fullscreen video of course - this can be zoome to true fullscreen without black areas)


Very interesting to see and feel how Kodi works with touch gestures. Never checked it out until now.

[Thomas_AR]

@axbmcuser

I was just looking for a touch solution to jump 10 sec forward or backwards in a video. Using this mostly when skipping intros of a movies or series.
I will check out the "Vídeo Skip Steps" function. Was aware of this.

The aspect ratio of my phone is 19.5:9.
Your skin covers the screen up to the edge of the front camera circle , meaning having a black space there. The other side is fully covered.

[Thomas_AR]

@axbmcuser

Have you seen this?
https://forum.kodi.tv/showthread.php?tid=375016