That's already done... each computer that joins a project recieves an unique id on that particular project (different on each project)

Will Boinc update itself to newer versions when they are available?

I don't think so. Version 7.2.8 is available in the Google Play Store, if your BOINC is still 7.2.7, it doesn't update itself.

And will the project list update itself as more projects becomes availabe?

Yes, that one will update itself.

I saw you mentioned The skynet pogs as an arm project but it wasn't in the projects list.

That's because 7.2.7 was built before SkynetPOGs was added.

By the way, there's also an Android FAQ that is updated quite regularly.

The added lines won't change, and it doesn't make the use of BOINC any slower. So there's really no need to rewrite the file. It's easy as well for if you ever just want to enable any debug lines, then you only have to change a zero for a one, not have to figure out how to spell words and make sure the lines have the correct end tags or not.

Plus as soon as you add a file again through the exclusive apps option, they'll all be back.

SIV says there way of giving numbers to the GPU's are correct.

Well, when the developer for that application says his way is the only correct way, then that must be it. Case solved. Why bother to ask?

But here's the thing, SIV can use an OS specific API to do all the hard work of polling the videocard for it, whereas BOINC needs to be showing the same numbers when compiled on Windows, Linux, FreeBSD or OSX, and where applicable and supported. It cannot rely on an OS specific API. It will also have the detect Nvidia GPUs, AMD GPUs and Intel GPUs and put them in a certain order, these being 1 - compute capability, 2 - software version, 3 - available memory and 4 - speed.

Only after those 4 have been ascertained, will BOINC give out numbers for GPUs and show that in the start-up messages. And they'll be the same numbers whether you run Windows, Linux, OSX or FreeBSD. Easy, huh? :-)

That's not new in v7.0.64 - for some time now, the Manager (and I think it is a Manager thing, not the core client) has created a fully-populated template for cc_config.xml in alphabetical order, every time you use the GUI tool for adding an exclusive application.

It's a very useful feature, IMHO.

You can post in your thread ad nauseum, but without specific data there is nothing that we can see or do about any of it. Your problem, you have to explain in detail what you see, what you think you should see, where it differs from the last test you did. There's nothing in it that I can send to the developers either, as they'll just request debug logs and such, things that you neglect to give.

So you really have to do better than this. If not in text, then use pictures. Use Photobucket, Imageshack or TinyPic to store the image and give an URL or IMG to the image.

Since you're choosing to run development versions of BOINC, I also want to remind you of the disclaimer and reminder to alpha testers:

Disclaimer
On development versions of BOINC:
- Expect parts of it to be broken, or in the least to work in a different way than you are used to.
- Expect work failures, deadline misses and losing all your accumulated work in progress, or not getting credit for your work due to unknown and unforeseen circumstances.
- Only use it when you are willing to participate in the Alpha test program and do not mind sending (bug) reports in to the developers on the email list specially assigned for this purpose.
- Due to the OpenCL detection, your screen may flicker or turn off temporarily. This is normal.


REMINDER TO ALL ALPHA TESTERS:
It's far easier for the developers to fix problems when you send message logs with the appropriate flags set. The main flags are:

<cpu_sched_debug>: problems involving the choice of applications to run.
<work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much).
<rr_simulation>: problems involving jobs being run in high-priority mode.
<sched_op_debug>: problems involving scheduler operations and other low level information.

Use these flags from the cc_config.xml file.

Report any problems you get with it to the Alpha email list. This list needs registration. When sending logs or other attachments, make sure to CC David, Rom, or Charlie separately, since the email list will drop attachments!

Reporting bugs on this forum or any project's forum isn't very productive as the developers simply do not have time to scour through all forums looking for posts with your bug reports in them. While it may happen that we - other volunteers - forward your problem to them, history has shown it is quite difficult being the middle man in this when more information is needed from you. Hence why it's better for all concerned that you report the problem directly to the developers, who will come back directly to you when they need more information or better logs or to tell you that they've checked in a fix for the specific problem.