Over 100% Complete Android

Message boards : Number crunching : Over 100% Complete Android

To post messages, you must log in.

AuthorMessage
Wizard Fait

Send message
Joined: 5 Mar 06
Posts: 3
Credit: 66,181
RAC: 0
United States
Message 1364675 - Posted: 5 May 2013, 5:29:08 UTC

Firstly, I would like to apologize if this is the wrong section. There doesn't appear to be a section for Android, so I figured the Unix/Linux section would be the most closely relevant.

I have a current SETI@Home task on the Android version which is sitting around 529319802675154000000000000.000%. This is after about 24 hours of CPU time which has usually been enough to complete previous tasks.





If any other information would be beneficial to correcting this issue, please let me know.
ID: 1364675 · Report as offensive
Wizard Fait

Send message
Joined: 5 Mar 06
Posts: 3
Credit: 66,181
RAC: 0
United States
Message 1364679 - Posted: 5 May 2013, 5:44:20 UTC

This thread can be closed/deleted. Upon suspending other projects, then resuming them, it caused the percentage to return to a reasonable number.
ID: 1364679 · Report as offensive
rob smithProject Donor
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 13339
Credit: 155,084,162
RAC: 118,860
United Kingdom
Message 1364696 - Posted: 5 May 2013, 7:39:28 UTC

Moved from Q&A - I know some of you have been doing things with Android and may be interested Wizard Fait's progress
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1364696 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6111
Credit: 155,383,687
RAC: 50,535
United States
Message 1365117 - Posted: 6 May 2013, 13:15:56 UTC

I saw that a few times, but wasn't sure if it was my old phone or the app doing it. I restarted my phone or the app and after the next checkpoint it corrected itself.

However the author of the app(s) might still be monitoring this thread: Seti android app.

If not you could submit a bug report on their website.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!
ID: 1365117 · Report as offensive
Wizard Fait

Send message
Joined: 5 Mar 06
Posts: 3
Credit: 66,181
RAC: 0
United States
Message 1365269 - Posted: 6 May 2013, 21:13:13 UTC - in response to Message 1365117.  

Thank you very much! I have sent an email to the developer using the site given.
ID: 1365269 · Report as offensive
matszpk
Volunteer tester

Send message
Joined: 6 May 12
Posts: 27
Credit: 55,618
RAC: 0
Poland
Message 1365542 - Posted: 7 May 2013, 21:35:49 UTC
Last modified: 7 May 2013, 21:38:26 UTC

I encountered this same problem when I was testing SetiApp on HTC Wildfire S. Unfortunatelly I couldn't find bug. I captured 'weird' workunit and computed on my tablet (VFP and NEON code) and I didn't catch weird progress :( (and I got correct results). Tomorrow I will try to compute on HTC Wildfire S. Sorry :(.
May be this is bug in the Android (???). I dont know :(
ID: 1365542 · Report as offensive
Richard HaselgroveProject Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 11143
Credit: 83,914,320
RAC: 48,595
United Kingdom
Message 1365547 - Posted: 7 May 2013, 22:14:39 UTC - in response to Message 1365542.  

I encountered this same problem when I was testing SetiApp on HTC Wildfire S. Unfortunatelly I couldn't find bug. I captured 'weird' workunit and computed on my tablet (VFP and NEON code) and I didn't catch weird progress :( (and I got correct results). Tomorrow I will try to compute on HTC Wildfire S. Sorry :(.
May be this is bug in the Android (???). I dont know :(

The converse problem (elapsed time increasing, but progress %age remaining static) is well observed at SETI, but equally unsolved.

But the number in the image is too large to have been reached by gradual increments - that would have taken the age of several universes.

Most recent cases of outlandishly large numbers - from the NVidia GPU 'wacky memory' bug, to the extended-length WU names at this project - have turned out to be the result of storing 32-bit data in 64-bit memory locations, and failing to initialise or zero the most significant 32 bits of the variable.
ID: 1365547 · Report as offensive

Message boards : Number crunching : Over 100% Complete Android


 
©2016 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.