1)
Message boards :
Android :
Weak Account Key
(Message 78575)
Posted 3 Jun 2017 by mirabilos Post: Hm, but that means if I do manage to edit the relevant files I could use it? I may just try that next time. (Fear the power of root! ☺ Did you know I’m the developer of what Android ships as /system/bin/sh? ☻) |
2)
Message boards :
BOINC Manager :
Weak Account Key
(Message 78574)
Posted 3 Jun 2017 by mirabilos Post: Can this _please_ be exposed to boincmgr (and Android)? I knew about the command-line attach method (writing a file seems to be even more cumbersome), but I’ve had systems where direct access was much more cumbersome (and it would also help the users who are not as computer-affine as I am). It’s really astonishing such a basic command is missing from boincmgr, especially as it seems to be “just” another API call. |
3)
Message boards :
Android :
Wrong hostname
(Message 78573)
Posted 3 Jun 2017 by mirabilos Post: But the devices *have* a “host”name. It just happens to not be retrievable using the DNS resolver. |
4)
Message boards :
Android :
Wrong hostname
(Message 78285)
Posted 26 May 2017 by mirabilos Post: But the hostname is “localhost”, not “android”, so clearly the client uses its own idea of a device name. (And yes, I can edit such files.) |
5)
Message boards :
Android :
Weak Account Key
(Message 78282)
Posted 26 May 2017 by mirabilos Post: How can I attach to projects using the Weak Account Key? |
6)
Message boards :
BOINC Manager :
Weak Account Key
(Message 78281)
Posted 26 May 2017 by mirabilos Post: How can I attach to a project using the Weak Account Key in boincmgr and, more importantly, the official Android client? |
7)
Message boards :
Android :
Wrong hostname
(Message 78130)
Posted 22 May 2017 by mirabilos Post: My device’s rooted and has a custom hostname (CyanogenMod already provides this facility, and I verified it with https://play.google.com/store/apps/details?id=com.tiranodroid.change.hostname&referrer=utm_source%3Ddroidwiki.de%26utm_medium%3Darticle-view%26utm_campaign%3Darticlelink that it’s indeed correct in the system properties. On WCG, the device turns out as just “android” (all-lowercase), on Enigma@HOME it’s “android_c753fa9d”, and in the event log, I have “reporting hostinfo os name: Android” but nothing about the hostname. How can this be corrected? One thing I notice is that /proc/sys/kernel/hostname contains “localhost” and my local PS1 has the device type “trltexx” instead of the chosen hostname… |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.