| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Android Support Forum
Thread: Probable improvement for the Android application |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
timur.gilmanov
Cruncher Joined: Dec 9, 2013 Post Count: 1 Status: Offline Project Badges: 
|
hi there to all.
Probably this issue already had been discussed by someone. what I have to propose - I think it is possible to add another one check-box for the Android application preferences - To compute while being in on charge despite of battery level. For example - you just came back to home and put your device to charge. It was a hard day and finally the battery level on your device is 20%. Being connected to charger charged will increase the battery level up to 90% and eventually it starts to compute, but the time interval from 20% to 90% might take up to 2-3 hours and that time is spent ineffectively (no computations during this period). If your device is allowed to compute while the charger is connected despite of battery level then processor time will be used more effectively. Eventually, in the morning a user will have an Android device with fully charged battery and the GRID Project will gain huge additional amount of computations. sorry for my English )) - it is not my native language |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Welcome to WCG.
Think you can lower the % of Battery charge at which computing may start [when on charger]. Yes / No? Would that help? As was found, some chargers are not up to keeping the battery at 90%. Soon as computing starts the battery start draining faster than charger can deliver. Not sure if this is a case of single/multicore devices. Maybe a multicore device being allowed to only compute on 1 core may allow to keep up with the BOINC draw on battery. Whilst, the other feature requested is being able to compute on charger when the battery is not in the device. Not heard much from the BOINC for Android front what the standings are. |
||
|
|
Panther-X
Cruncher Joined: Nov 12, 2013 Post Count: 27 Status: Offline Project Badges: 
|
My Samsung Galaxy S3 with 4 CPUs would cause invalid results and I found that using only 2 CPUs generates an occasional invalid result. The battery could charge to 100% even when using all 4 CPUs.
----------------------------------------On the other hand, my HTC One X+ couldn't get above 90% charge level with 4 CPUs or 3 CPUs crunching. It was only when I configured it for 2 CPUs that I can maintain a 100% battery charge. Also, using 2 CPUs as opposed to 3 or 4 generated an occasional error but surprisingly, the time taken to crunch each task has increased by a few hours. Not sure why that is. Swapping the USB Cable between the cells didn't produce any difference (HTC One X+ still can't be 100% charged with 3 or 4 CPUs crunching). I guess that it might be a slightly more complex picture as to why some cells charge or not.  |
||
|
|
noderaser
Senior Cruncher United States Joined: Jun 6, 2006 Post Count: 297 Status: Offline Project Badges: 
|
Are Android devices taking their preferences from the projects yet, or is it still local-only?
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi noderaser,
I have not heard of any change. There is a lot of work on the server going on in the background intended to enable different sized work units for phones and PCs, so I suspect it will be some time before other changes are made. Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Are Android devices taking their preferences from the projects yet, or is it still local-only? IIRC the Berkeley devs started on web enabling Android profiles, then reversed it out as too complex. The only way to config is on the device. ** The unrelated is, that something was in the development to set up more locations, or make it free [any name you like] to create by the user [WCG is the only one where you still can, by accident, -unsupported- but condoned]. These locations will not work outside WCG, are sure confusing heck if these devices are attached to multiple project. edit: ** more definitely, the devs ripped any global_prefs web profile controlled functionality out of the Android client. [Edit 1 times, last edit by Former Member at Dec 12, 2013 8:33:47 AM] |
||
|
|
alderaan
Cruncher Joined: Jan 2, 2013 Post Count: 5 Status: Offline Project Badges:
|
I think that changing battery level to a lower value is not an option because then you have to remember to rise it again when you unplug the device (every single day), so I agree that a "force compute while charging" check should be added and it should be unchecked by default (as SekeRob said there are devices which are not able to recharge and compute at the same time).
----------------------------------------Greets. [Edit 2 times, last edit by alderaan at Dec 13, 2013 8:54:32 AM] |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
alderaan, to make the reference complete "...when more than 1 core is computing, on multicore devices". Don't know about single core devices with chargers not keeping up. One volunteer reported their client was constantly flipping between on and of... going over 90%, dropping below 90% and above. Did seem to remember some wrote that you could lower the percent from when computing could be started. You don't have to remember, because BOINC will stop when unplugged [there's a computing while unplugged option too, from reading, but have no Android to be able to talk hands-on... just the wiki references: http://boinc.berkeley.edu/w/?title=Special%3A...;search=android&go=Go ]. And a bunch of screenshots of the interface:
https://www.google.it/search?q=BOINC+for+Andr...5&bih=569&dpr=1.2 One screenshot, about the 6th in the series, that shows you can change the charge percent when computing can start AND the battery temp ;>) https://play.google.com/store/apps/details?id=edu.berkeley.boinc I'll add this one to the Start Here FAQ series... almost very complete... missing an image of the event log view. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Is somebody reading our forums... is somebody passing the message? A few things checked on on 'chargers' for android... just 2 minutes ago:
----------------------------------------android: added charger type preference. - fix layout size of leglevel dialog - refector preference code, more readable - add charger type preference (ac vs usb vs wireless vs battery) Clearly the client is still in a state of WIP and as uplinger noted v.v. an Oya?, work is underway to get non-battery containing devices or devices without a battery at all to also be allowed to crunch. Not sure how many watts a Computer USB can output to keep the smartphone battery up at an high enough level to crunch. Noticed that if I stick my phone in to charge through the laptop, the wall-socket meter goes up by 6 Watts/hr consumption. Edit: And another checkin, but that was 22 hours ago: android: support for stationary devices - detect whether battery is present, - if not, skip checks for battery heat, battery level and charger status - by sending positive dummy data to the client - remove category Power from preferences - code to detect wired internet connection, treat as wifi - refactor DeviceStatus class, to have detection code in edu.berkeley.boinc.client rather than .rpc [Edit 1 times, last edit by Former Member at Dec 13, 2013 2:00:13 PM] |
||
|
|
noderaser
Senior Cruncher United States Joined: Jun 6, 2006 Post Count: 297 Status: Offline Project Badges:
|
These issues are not exclusive to WCG... They have been brought up on the Android beta forum already.
---------------------------------------- |
||
|
|
|