I have been playing around with ABMMini the last little while and have been ignoring a bug that keeps cropping up - at least my end.
STEPS TO REPRODUCE:
Step 1
Install ABMMini on your D: drive - see:
https://www.b4x.com/android/forum/t...-absolute-beginners-update-2022-09-08.117237/
Step 2
Leave everything asis - so when you run it it is listening on localhost:51042/template
Step 3
On an iPhone (mine is iPhone 7), launch Safari and set URL localhost:51042/template
If this does not work, work out localhost IP (e.g. 192.168.1.109) and set URL 192.168.1.109:51042/template
Everything should run as advertised.
Step 4
On an Android (mine is Pixel 3 running Android 12), launch Chrome then follow exact same steps as Step 3 re URL.
The server constantly cycles thru:
Connected
Waiting for value (115 ms)
Waiting for value (109 ms)
Waiting for value (103 ms)
Disconnected
null
null
Connected
Waiting for value (103 ms)
Waiting for value (110 ms)
Waiting for value (105 ms)
Disconnected
null
null
Connected
Waiting for value (104 ms)
Waiting for value (110 ms)
Waiting for value (105 ms)
Disconnected
null
null
Connected
Waiting for value (115 ms)
Waiting for value (110 ms)
Waiting for value (101 ms)
Disconnected
Step 5.
To stop this behaviour, on Android phone open another tab on Chrome then go back to original tab - now everything works as advertised.
I'd be interested in knowing if someone else can reproduce it on a different Android release.
STEPS TO REPRODUCE:
Step 1
Install ABMMini on your D: drive - see:
https://www.b4x.com/android/forum/t...-absolute-beginners-update-2022-09-08.117237/
Step 2
Leave everything asis - so when you run it it is listening on localhost:51042/template
Step 3
On an iPhone (mine is iPhone 7), launch Safari and set URL localhost:51042/template
If this does not work, work out localhost IP (e.g. 192.168.1.109) and set URL 192.168.1.109:51042/template
Everything should run as advertised.
Step 4
On an Android (mine is Pixel 3 running Android 12), launch Chrome then follow exact same steps as Step 3 re URL.
The server constantly cycles thru:
Connected
Waiting for value (115 ms)
Waiting for value (109 ms)
Waiting for value (103 ms)
Disconnected
null
null
Connected
Waiting for value (103 ms)
Waiting for value (110 ms)
Waiting for value (105 ms)
Disconnected
null
null
Connected
Waiting for value (104 ms)
Waiting for value (110 ms)
Waiting for value (105 ms)
Disconnected
null
null
Connected
Waiting for value (115 ms)
Waiting for value (110 ms)
Waiting for value (101 ms)
Disconnected
Step 5.
To stop this behaviour, on Android phone open another tab on Chrome then go back to original tab - now everything works as advertised.
I'd be interested in knowing if someone else can reproduce it on a different Android release.
Last edited: