Announce: Material Skin

[slartibartfast]

> When pressing Material's "(i)" button to show biography, album review,
> and lyrics in 23 tabs I call MAI directly. But, if you use context menu
> for a track, or an album, and select the "More" entry then it will
> invoke "trackinfo", or "albuminfo" - and its the LMS menus from these
> that also have an "Album review" entry. Accessing via "More" (accoding
> to slartibartfast) works, but directly calling MAI fails.

Ok, slartibartfast - could you please send me the requests for the "MAI
direct" mode?

Another log when accessing
More info/Album information/Album review
from the context menu of a track. This works.

[mherger]

Announce: Material Skin

> Another log when accessing
> More info/Album information/Album review
> from the context menu of a track. This works.

Is the track artist EC, while the album artist is Derek? In one case EC
is what the plugin would look for, in the other (success?) case it's Derek.

[slartibartfast]

> Another log when accessing
> More info/Album information/Album review
> from the context menu of a track. This works.

Is the track artist EC, while the album artist is Derek? In one case EC
is what the plugin would look for, in the other (success?) case it's Derek.

Album artist is Eric Clapton
Track artist is Derek And The Dominos

Sent from my Pixel 3a using Tapatalk

[mherger]

Announce: Material Skin

>>> Another log when accessing
>>> More info/Album information/Album review
>>> from the context menu of a track. This works.
>>
>> Is the track artist EC, while the album artist is Derek? In one case EC
>> is what the plugin would look for, in the other (success?) case it's
>> Derek.
>
> Album artist is Eric Clapton
> Track artist is Derek And The Dominos

Or this, yes. The problem here is that AllMusic listst things for one of
them, but not the other. It's hard for me to get this sorted out.

[slartibartfast]

>>> Another log when accessing
>>> More info/Album information/Album review
>>> from the context menu of a track. This works.
>>
>> Is the track artist EC, while the album artist is Derek? In one case EC
>> is what the plugin would look for, in the other (success?) case it's
>> Derek.
>
> Album artist is Eric Clapton
> Track artist is Derek And The Dominos

Or this, yes. The problem here is that AllMusic listst things for one of
them, but not the other. It's hard for me to get this sorted out.

Would removing the Album Artist and having both Eric Clapton and Derek And The Dominos as Track Artists work better?

Sent from my Pixel 3a using Tapatalk

[cpd73]

Or this, yes. The problem here is that AllMusic listst things for one of
them, but not the other. It's hard for me to get this sorted out.

Would it help if Material passed the artist_id and track_id parameters when making the albumreview call? (Won't help 'More' from album entry) My thinking is that if the current album_id call fails you coudl use the details from track_id to try again?

If so, should I also pass album_id and track_id when requesting biographies?

[mherger]

Announce: Material Skin

> Would removing the Album Artist and having both Eric Clapton and Derek
> And The Dominos as Track Artists work better?

You tell me :-). I don't know.

[mherger]

Announce: Material Skin

> Would it help if Material passed the artist_id and track_id parameters
> when making the albumreview call? (Won't help 'More' from album entry)

Not without me adding more logic to the already convoluted lookup code...

[cpd73]

> Would it help if Material passed the artist_id and track_id parameters
> when making the albumreview call? (Won't help 'More' from album entry)

Not without me adding more logic to the already convoluted lookup code...

I was more thinking that if track_id was passed then you could use the same logic as for when the album review is looked up via the "More" menu.

[slartibartfast]

> Would removing the Album Artist and having both Eric Clapton and Derek
> And The Dominos as Track Artists work better?

You tell me :-). I don't know.

It does work. I should have done that in the first place.

Sent from my Pixel 3a using Tapatalk

[BoxOfCables]

Is this runnnig after the app has been added to homescreen? Try editing material.manifest and change the "display" setting to "standalone" (this will be the default in 2.6.3) You can find material.manifest in the "MaterialSkin/HTML/material/html" folder wihing your LMS's plugins folder.

[Edit] Also, as a work-around you can use the Material APK (search for LMS on f-droid, or CORE32 on google play). This is a simple WebView wrapper that adds a few extras (such as server auto-disover, hardware volume keys, etc).

I'm getting the same issue, whether the manifest is set to "fullscreen" or "standalone" it launches fullscreen (after add to home screen) but the first touch causes the phone top-bar to appear. Note that it's not the browser "chrome" showing up - it's the Android system (the bar that shows the battery, signal etc.).

The browser height then goes wrong, so the top and bottom UI elements are off screen. After two seconds the phone returns to fullscreen and again any touch action causes the top bar to appear again.

This happens with Chrome and Edge, FireFox isn't honouring the fullscreen at all. I'm on Android 11 on a Pixel 4a.

Thanks for making the skin, it's made such an improvement. I take my hat off to you

[cpd73]

I'm getting the same issue, whether the manifest is set to "fullscreen" or "standalone" it launches fullscreen

You might need to clear Chrome's cache - not sure if it cache's the contents of the manifest or not. However, "standalone" should show Android's top statusbar and botton navigation controls. If these are not being shown, then Material is not being run standalone but fullscreen. I have checked, and the manifest 100% states "standalone" now, so there is nothing more Material can do.

[BoxOfCables]

You might need to clear Chrome's cache - not sure if it cache's the contents of the manifest or not. However, "standalone" should show Android's top statusbar and botton navigation controls. If these are not being shown, then Material is not being run standalone but fullscreen. I have checked, and the manifest 100% states "standalone" now, so there is nothing more Material can do.

It appears as though it does cache the manifest, I assumed that would be read new when adding to the homepage. It does now work using "standalone".

Thank you for your help.

[slartibartfast]

It appears as though it does cache the manifest, I assumed that would be read new when adding to the homepage. It does now work using "standalone".

Thank you for your help.

How did you clear the cache? I tried with Kiwi browser clearing both history and app cache in Android settings and still see the same issue

Sent from my Pixel 3a using Tapatalk

[BoxOfCables]

How did you clear the cache? I tried with Kiwi browser clearing both history and app cache in Android settings and still see the same issue

Sent from my Pixel 3a using Tapatalk

I used Chrome, tap the dots beside the address bar > settings > privacy and security > clear browsing data > tick the "cached images and files" and click the button. Reload the material page, add to home screen and it should work.