GUI Messages

Message boards : SETI@home Enhanced : GUI Messages
Message board moderation

To post messages, you must log in.

AuthorMessage
Jens
Volunteer tester

Send message
Joined: 2 Feb 07
Posts: 7
Credit: 11,914
RAC: 0
Germany
Message 48148 - Posted: 23 Nov 2013, 13:49:47 UTC

Hey there,
a few weeks ago I saw that finally there's a S@H-Client being worked on for Android devices. I've tried versions 7.21 and now 7.23. There were never any GUI messages no matter what verbose options I set. However now I got a bunch of messages. What do they mean and why do I get these messages although I've never got any before?

11-23 14:39:37.277 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:37.217 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:37.217 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:37.187 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:36.276 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:36.206 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:36.206 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:36.186 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:35.255 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:35.185 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:35.185 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:35.175 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:34.224 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:34.184 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:34.184 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:34.174 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:33.213 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:33.183 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:33.183 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:33.173 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:32.212 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:32.182 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:32.182 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:32.172 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:31.231 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:31.181 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:31.181 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:31.171 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:30.250 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:30.200 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:30.200 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:30.180 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:29.339 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:29.189 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:29.189 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:29.179 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:28.258 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:28.188 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:28.188 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:28.178 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:27.257 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:27.197 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:27.197 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:27.177 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:26.266 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:26.196 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:26.196 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:26.176 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:25.305 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:25.215 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:25.215 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:25.175 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:24.234 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:24.174 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:24.174 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:24.174 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:23.213 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:23.173 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:23.173 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:23.173 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:22.302 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:22.192 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:22.192 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:22.172 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:21.221 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:21.181 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:21.181 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
11-23 14:39:21.171 D/BOINC_GUI(27378): reportDeviceStatus()
11-23 14:39:20.220 V/BOINC_GUI(27378): setClientStatus: #results:1 #projects:1 #transfers:0 // computing: false30 - network: false20
11-23 14:39:20.180 D/BOINC_GUI(27378): readClientStatus(): screen on, get complete status
11-23 14:39:20.180 D/BOINC_GUI(27378): readClientStatus(): computation enabled: true
ID: 48148 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,440,339
RAC: 0
United Kingdom
Message 48149 - Posted: 23 Nov 2013, 14:00:45 UTC - in response to Message 48148.  
Last modified: 23 Nov 2013, 14:02:51 UTC

Hey there,
a few weeks ago I saw that finally there's a S@H-Client being worked on for Android devices. I've tried versions 7.21 and now 7.23. There were never any GUI messages no matter what verbose options I set. However now I got a bunch of messages. What do they mean and why do I get these messages although I've never got any before?

You're set the GUI log level to 5, reset it to 2 to get rid of these Debug messages, then watch the Client messages instead of the GUI messages.

Claggy
ID: 48149 · Report as offensive
Grumpy Swede
Volunteer tester
Avatar

Send message
Joined: 10 Mar 12
Posts: 1700
Credit: 13,216,373
RAC: 0
Sweden
Message 48150 - Posted: 23 Nov 2013, 14:02:36 UTC - in response to Message 48148.  
Last modified: 23 Nov 2013, 14:04:53 UTC

Same here. I never had any messages before from the BOINC client GUI Messages log on my Android device. No matter verbose option. I just checked now, and sure enough, there's all of a sudden some messages there. I've always been on log level 2 (default) and I still am. Despite that, the messages started coming today.

Not the same type as yours, but something about E/BOINC_GUI and Monitor status Update something, and java something.

I don't post this from the phone, so I can't paste the exact messages.
WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.
ID: 48150 · Report as offensive
Jens
Volunteer tester

Send message
Joined: 2 Feb 07
Posts: 7
Credit: 11,914
RAC: 0
Germany
Message 48151 - Posted: 23 Nov 2013, 14:47:54 UTC - in response to Message 48150.  

Well, if I set verbose mode below level 4, then these messages do indeed disappear. But like I said: When I set it to level 5 before I also never got messages - just like Sten-Arne.

@Sten-Arne: You can simply mail yourself all the messages by hitting the "options" or "context-menu"(or how is it called?) hardware-button on your phone while viewing the messages and then select "send via E-Mail"
ID: 48151 · Report as offensive
Grumpy Swede
Volunteer tester
Avatar

Send message
Joined: 10 Mar 12
Posts: 1700
Credit: 13,216,373
RAC: 0
Sweden
Message 48153 - Posted: 23 Nov 2013, 14:59:53 UTC - in response to Message 48151.  
Last modified: 23 Nov 2013, 15:00:19 UTC

Well, if I set verbose mode below level 4, then these messages do indeed disappear. But like I said: When I set it to level 5 before I also never got messages - just like Sten-Arne.

@Sten-Arne: You can simply mail yourself all the messages by hitting the "options" or "context-menu"(or how is it called?) hardware-button on your phone while viewing the messages and then select "send via E-Mail"


Yeah, I know. I was just being lazy Jens. After all, it's Saturday, one of few days when I don't HAVE to do anything. :-)

Anyhow, all of a sudden the GUI messages stopped coming. I never changed any log level settings, before or after. Must have been ET screwing with our phones remotely....
WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.
ID: 48153 · Report as offensive

Message boards : SETI@home Enhanced : GUI Messages


 
©2021 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.