Problems with the "Click/tap to start OpenWebRX" prompt on Android mobile devices? [fixed in v1.261]
Is anyone having problems not being able to get past the "Click/tap to start OpenWebRX" prompt that should appear on mobile devices and some pc browsers? I've had a report of this being broken for about 5 days on Android. But I don't yet know any specifics about Android OS version, mobile device type, mobile browser type, etc. The only thing I know is that the reporter said Kiwis worked fine using pc Firefox & Chrome. So that rules out local networking problems.
Thanks.
Thanks.
Comments
PCs, both Linux and Windows fine.
Has this broken recently or has it never worked on this phone? Has it worked on an older Android version on this phone?
Sorry for all the questions, but without them it's extremely difficult for me to guess what might be going on. Thanks.
I'm not certain that it ever worked on this particular phone. I think it has previously but not sure which phone I was using.
Must find another browser to try and load it onto phone. Late here so must QRT until tomorrow.
Refresh of the URL got me back to "Click to start" with no interaction again. Waited 2 minutes and "click to start" disappeared and back to control panel w/o custom image. Can collapse/enlarge control panel. Can move decoded/rx frequency. no WF and no audio.
RX operates and looks normal on PC/browser and is serving several rx's of remote WSPR.
Is the phone fairly recent or a good few years old?
The only Android device I have here runs 4.4, which by now is ancient (and the Kiwi stuff runs fine on it). So I guess I need to buy the cheapest tablet I can find running 8.x to do some debugging.
Ron
KA7U
The page does run just fine on an older Kindle Fire, Sept 2018 5.6.2.0 with a "Silk" browser. Waiting for an update to 5.3.6.4. If it stops running when that's installed I'll let you know.
Ron
KA7U
Kindle updated to 5.3.6.4 with Silk continues to work fine.
Ron
KA7U
I was able to replicate the issue using a new, but highly underpowered Lenovo Tab E7 tablet running Android 8.1.0 ("Go" version). I had to change a Javascript algorithm to not be so demanding (cpu cycles needed within a realtime constraint). This is very odd because the previous Kiwi version ran just fine on an old Huawei T1 7.0 tablet running Android 4.4.2 and a fairly recent version of Firefox. So this is probably not a mobile browser problem.
Amusingly, I noticed in general Android 4 on the Huawei was much more responsive than Android 8 on the Lenovo. The two devices use very similar processors (quad core 1.2 vs 1.3 GHz ARM A7).