Testing app beta v1.5 23/11/2020

Started by Richard Haselgrove, November 23, 2020, 05:04:16 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Richard Haselgrove

Thanks for the extra features - they make life here much easier. All seem to work as advertised.

But I still get that 'no WiFi' and I still haven't connected from either (Windows) BOINC Manager or boinccmd. BOINC for Android still detects the same IP address, and the tablet responds normally to a ping to that address. I'll try a Linux Manager next.

Edit - no, Linux couldn't connect either. Just sat there, saying 'connecting' - no error messge.

fred

Quote from: Richard Haselgrove on November 23, 2020, 05:04:16 PM
Thanks for the extra features - they make life here much easier. All seem to work as advertised.
Go to Gui setup.
Now disable "Allow External...." -> Message should be Connection:Disabled
Enable "Allow External...." -> Message should be Connection:Waiting
If not look for "DeviceStatus:isconnectedToWifi" in the error log, that is an error in the detection.


Richard Haselgrove

Will do, between tasks on the 7.16.3 - about 3 - 4 hours from now.

Richard Haselgrove

This is all I could get in the log:

19:38:22:Start BOINC (setDebug) for BoincTasks: V: 1.5 (5)
19:38:22:MainActivity:Ignore Battery Optimizations, permission granted
19:38:22:MainActivity:doBindService
19:38:22:Service: onCreate
19:38:22:Service:onStartCommand:Service Started
19:38:22:ERROR:RpcClient:openjava.io.IOException: Connection refused
19:38:22:Boinc:clientSetup: Starting the BOINC client
19:38:23:reporting hostinfo model name: samsung SM-T510 - SDK: 29 ABI: armeabi-v7a, os name: Android, os version: 10
19:39:46:MainActivity:doUnbindService


Connection toggles between 'Disabled' and 'No Wi-Fi' with the 'allow external' control.

fred

Quote from: Richard Haselgrove on November 24, 2020, 07:55:07 PM
This is all I could get in the log:

Connection toggles between 'Disabled' and 'No Wi-Fi' with the 'allow external' control.
V 1.6 adds a fallback WiFi detection and logs My Ip is: 2 IP addresses.

Richard Haselgrove

I see your second IP detection:
10:01:05:Start BOINC (setDebug) for BoincTasks: V: 1.6 (6)
10:01:05:MainActivity:Ignore Battery Optimizations, permission granted
10:01:05:MainActivity:doBindService
10:01:05:Service: onCreate
10:01:05:Service:onStartCommand:Service Started
10:01:05:ERROR:RpcClient:openjava.io.IOException: Connection refused
10:01:05:Boinc:clientSetup: Starting the BOINC client
10:01:07:reporting hostinfo model name: samsung SM-T510 - SDK: 29 ABI: armeabi-v7a, os name: Android, os version: 10
10:01:07:Service:boincStart: BOINC client started and authorized
10:01:07:Service:boincStart: My IP is: 192.168.173.185 - 192.168.173.185
10:11:37:MainActivity:Ignore Battery Optimizations, permission granted
10:11:37:MainActivity:doBindService
10:13:08:MainActivity:Ignore Battery Optimizations, permission granted
10:13:08:MainActivity:doBindService
10:13:24:MainActivity:doUnbindService
10:13:26:Service:onDestroy


IP address is right for my setup - all machines are on that subnet, DHCP managed.
Connection has reverted to constant 'No Wi-Fi' when the 'allow external' control is toggled - 'disabled' not shown.

fred

Quote from: Richard Haselgrove on November 25, 2020, 10:28:30 AM
I see your second IP detection:
And I see the first IP is correct after all.... that's puzzling.
The GUI setup in this version isn't working anymore.... I'm working on 1.7, adding more logging and fixing the bug.
I tested it with the BOINC Manager, no problems there.

fred


Richard Haselgrove

It's getting more chatty, but still doesn't like my WiFi:

17:19:07:Start BOINC (setDebug) for BoincTasks: V: 1.7 (7)
17:19:07:MainActivity:Ignore Battery Optimizations, permission granted
17:19:07:MainActivity:doBindService
17:19:07:Service: onCreate
17:19:07:Service:onStartCommand:Service Started
17:19:07:ERROR:RpcClient:openjava.io.IOException: Connection refused
17:19:07:Boinc:clientSetup: Starting the BOINC client
17:19:08:reporting hostinfo model name: samsung SM-T510 - SDK: 29 ABI: armeabi-v7a, os name: Android, os version: 10
17:19:08:Service:boincStart: BOINC client started and authorized
17:19:08:Service:boincStart: My IP is: 192.168.173.185 - 0.0.0.0
17:19:08:Gui:start: (WIFI_NOT_ALLOWED) IP: 192.168.173.185, Not allowed: 192.168.173.185
17:19:35:MainActivity:doUnbindService
17:19:37:Service:onDestroy

fred

Quote from: Richard Haselgrove on November 26, 2020, 05:29:14 PM
It's getting more chatty, but still doesn't like my WiFi:
I see, check the GUI setup. The WiFi IP doesn't match 192.168.173.185, maybe the wrong number or a space.
The logging shows 2 identical IP addresses, that's incorrect and rather misleading.

Richard Haselgrove

BREAKING NEWS!

I went back a step, and tried your previous suggestion. It started with

Connection:WiFi Ip address not allowed Ip: 192.168.173.185

I switched off external connections

Connection:Disabled

and back on

Connection:Waiting

and finally

Connection:With Ip: /192.168.173.26:60466

Remote machine says:

26/11/2020 17:37:44 |  | Starting BOINC client version 7.17.0 for arm-android-linux-gnu
26/11/2020 17:37:44 |  | This a development version of BOINC and may not function properly
26/11/2020 17:37:44 |  | log flags: file_xfer, sched_ops, task
26/11/2020 17:37:44 |  | Libraries: libcurl/7.62.0 OpenSSL/1.0.2s
26/11/2020 17:37:44 |  | Running as a daemon
26/11/2020 17:37:44 |  | Data directory: /data/data/com.efmer.boincforboinctasks/client
26/11/2020 17:37:44 |  | No usable GPUs found
26/11/2020 17:37:44 |  | Host name: exynos7904
26/11/2020 17:37:44 |  | Processor: 8 ARM ARMv8 Processor rev 4 (v8l) [Impl 0x41 Arch 8 Variant 0x0 Part 0xd03 Rev 4]
26/11/2020 17:37:44 |  | Using 4 CPUs
26/11/2020 17:37:44 |  | Processor features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt lpae evtstrm aes pmull sha1 sha2 crc32
26/11/2020 17:37:44 |  | OS: Android: 4.4.177-19577611
26/11/2020 17:37:44 |  | Memory: 1.85 GB physical, 1.25 GB virtual
26/11/2020 17:37:44 |  | Disk: 24.81 GB total, 20.25 GB free
26/11/2020 17:37:44 |  | Local time is UTC +0 hours
26/11/2020 17:37:44 |  | Config: report completed tasks immediately
26/11/2020 17:37:44 |  | Preferences:
26/11/2020 17:37:44 |  | max memory usage when active: 948.97 MB
26/11/2020 17:37:44 |  | max memory usage when idle: 948.97 MB
26/11/2020 17:37:44 |  | max disk usage: 20.15 GB
26/11/2020 17:37:44 |  | max CPUs used: 4
26/11/2020 17:37:44 |  | Android: don't compute while active
26/11/2020 17:37:44 |  | don't use GPU while active
26/11/2020 17:37:44 |  | suspend work if non-BOINC CPU load exceeds 50%
26/11/2020 17:37:44 |  | (to change preferences, visit a project web site or select Preferences in the Manager)
26/11/2020 17:37:44 |  | Setting up project and slot directories
26/11/2020 17:37:44 |  | Checking active tasks
26/11/2020 17:37:44 |  | Setting up GUI RPC socket
26/11/2020 17:37:44 |  | Checking presence of 0 project files
26/11/2020 17:37:44 |  | This computer is not attached to any projects
26/11/2020 17:37:44 |  | Suspending computation - on batteries
26/11/2020 17:37:44 |  | Suspending network activity - not connected to WiFi network
26/11/2020 17:37:46 |  | Resuming network activity


I need to do an orderly run down of the previous version, and then try attaching to a project - but looking good. Well done.

fred

Quote from: Richard Haselgrove on November 26, 2020, 05:45:16 PM
I need to do an orderly run down of the previous version, and then try attaching to a project - but looking good. Well done.
Thanks for testing, you did a great job catching interesting bugs.
There is one, that doesn't correctly retrieves the right allowed WiFi IP addresses at startup, but it works right after changing them.
I made a stupid copy paste error, easily to miss in a part that I trusted.

Richard Haselgrove

Look what I've got!



That's https://einsteinathome.org/host/12859350, attached via BOINC Manager. I still need to get used to it, but the key seems to be to do minimal setup - I emptied all the external IP fields (1, 2, 3, 4), and filled just one of the four WiFi addresses with the LAN subnet (192.168.173), and it listened straight away at startup - didn't need to disable and re-enable. BTW, the WiFi address fields are labelled 1, 2, 2, 2

fred

Quote from: Richard Haselgrove on November 27, 2020, 04:51:41 PM
Look what I've got!

didn't need to disable and re-enable

BTW, the WiFi address fields are labelled 1, 2, 2, 2
The 1,2,2,2 isn't only on the screen but in the code as well, causing interesting overwrites.
Any change you make results in a rebuild of the whole connection, so you do not use the disable, that was only for testing.

Maybe add a quick start screen in the manual. Like a screenshot and what to setup.

fred