Have a look for any errors in the console tab of your browser's developer tools. By 'menu entry' I assume you mean an item in the browse view? Note that for release builds I split the Javascript in two - to speed page loads. The fist has just enough to show the UI, but the handler for clicks in the browse view is loaded just after the UI javascript. This has the effect that for the 1st few milliseconds clicks will not work - and you will see an error about this if you click too soon. However, after the full javascript is loaded there should be no errors. I only mention so that when you look for errors in the console tab, you will see the one about browseClick - it can be ignored.
Results 6,661 to 6,670 of 7126
Thread: Announce: Material Skin
-
2021-02-28, 03:27 #6661
- Join Date
- Mar 2017
- Posts
- 2,740
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
-
2021-02-28, 03:28 #6662
- Join Date
- Dec 2016
- Location
- Scotland
- Posts
- 60
-
2021-02-28, 03:28 #6663
- Join Date
- Nov 2012
- Location
- UK, Nottinghamshire
- Posts
- 380
-
2021-02-28, 03:49 #6664
-
2021-02-28, 03:50 #6665
- Join Date
- Jun 2020
- Location
- UK
- Posts
- 30
I suspect that many users are not aware of the APK. It's not widely publicised in the documentation so casual users probably don't realise it exists. Shame as it is excellent
-
2021-02-28, 04:24 #6666
- Join Date
- Nov 2009
- Location
- DUS
- Posts
- 914
APK:
I am not using apps/apk's that are not on the Play Store.
And why should I!?!? MS looks and feels like an app with Android/Chrome
in full screen mode and the bookmark icon on the homescreen.
Badge:
If understood it correctly the badge is shown if the PWA (web app) is not getting
validated by Chrome. A comment over at stackoverflow mentioned using Chrome Lighthouse
to help making a PWA compliant. Not sure though if this would be the same context or subject.
-
2021-02-28, 04:42 #6667
- Join Date
- Jan 2010
- Location
- Hertfordshire
- Posts
- 6,614
-
2021-02-28, 04:46 #6668
- Join Date
- Nov 2012
- Location
- UK, Nottinghamshire
- Posts
- 380
-
2021-02-28, 04:57 #6669
- Join Date
- Nov 2012
- Location
- UK, Nottinghamshire
- Posts
- 380
3x Squeezebox Touch, 4x Squeezebox Radio, Squeezelite (RPi 3B with HiFiBerry DAC+Pro on OSMC), Material Skin Apk, Squeeze Commander, Logitech Media Server Version: 8.2.0 with Material Skin (Docker in DS218+)
-
2021-02-28, 06:12 #6670
- Join Date
- Mar 2017
- Posts
- 2,740
And that is fair enough, can't say I blame you - using random APKs from unknown sources is not good idea. However, f-droid is a well known source of opensource apps.
Material is opensource, so please feel welcome to investigate how to resolve this - help is always appreciated. I am not a web developer, and this is by far the biggest Javascript app I have developed. From my, limited, understanding to be a complete PWA a site (e.g. Material) needs to be served over HTTPS and use 'service workers'. LMS, however, is HTTP only. As its HTTP, Chrome also shows an insecure site warning when you enter text (as the text is sent unencrypted to LMS). Chrome will even show this warning for a HTTPS site if it were using a self-signed certificate.
An alternative method is to load Material in the 'Fully kiosk' browser. If you then use an alternative launcher, such as Nova, you can change the icon, and label, of FullKiosk to be LMS. This will allow you to have a more integrated app.Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.