Latest Boinc for Android is working on my 2012 Nexus 7 (Nvidia Tegra chipset)
using Android 5.1.1 O.K
He doesn't mention what Boinc version he's having this problem on, is it
Android 5 compatible?
When did it work? Before or after upgrading to Android 5?
Claggy
Date: Sat, 18 Jul 2015
If I transfer that output to a different browser it comes out better:
pi@raspberrypi ~ $ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 57.60
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32
lpae evtstrm
CPU implementer : 0x41
Forwarding on joshaay's email.
I assume it was Boinc 7.4.41, and it was from the Google Play store.
Claggy
Date: Sun, 19 Jul 2015 15:13:31 -0400
Subject: Re: FW: [boinc_dev] BOINC on Android 5.1.1
From: joshaa...@gmail.com
To: stephen.macla...@hotmail.com
I just downloaded this app
On the Raspberry Pi Model B running Raspbian Wheezy:
pi@raspberrypi ~ $ cat /proc/cpuinfo
processor : 0
model name : ARMv6-compatible processor rev 7 (v6l)
Features : swp half thumb fastmult vfp edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xb76
CPU
Filip:
Are there any clues in stdoutdae.txt or stderrdae.txt?
(I'm not sure how to view these on Android but I think there's a way).
-- David
On 18-Jul-2015 4:27 PM, Filip Rydlo wrote:
Yeah, David.
This has happened to me for 3 times now on Android 5.1.1 (phone:
*OnePlus One*)
BOINC is installed in the data directory of the internal memory, not
the SD card.
It cannot be moved there either.
Perhaps something for an overhaul of BOINC on Android, make sure the
log files are in an accessible place without requiring that the user
roots his device.
-- Jord van der Elst.
If they are in the SD card, they can be more easily accessed by
connecting the phone to a computer via USB, or (obviously) by putting
the SD card itself in a computer.
--
Nicolás
2015-07-19 15:21 GMT-03:00 Jord van der Elst els...@gmail.com:
Not easy to find those files, as they are in the
Stephen:
Thanks. It looks like the /proc/cpuinfo format changed at some point,
and we weren't parsing the model name correctly for ARM.
I checked in changes that will parse the /proc/cpuinfo examples you sent.
Hopefully this will also work on recent Android.
Rom, can you please test this on
Not easy to find those files, as they are in the BOINC directory.
They live for me in Android 4.2 at
root/sdcard/data/user/0/edu.berkeley.boinc/client/ and can be reached
with an application such as X-plore
(https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplorehl=en).
You're
On Android (i.e. Linux) BOINC gets CPU info by parsing /proc/cpuinfo.
Maybe the format of this has changed.
Can someone who's seeing this problem please post the contents of /proc/cpuinfo
on their device?
Thanks -- David
On 19-Jul-2015 6:09 AM, Stephen Maclagan wrote:
The reason I'm posting
On my Quad Core Raspberry Pi running Raspbian Wheezy:
pi@raspberrypi ~ $ cat /proc/cpuinfoprocessor : 0model name : ARMv7
Processor rev 5 (v7l)BogoMIPS : 57.60Features : half thumb fastmult vfp edsp
neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer :
0x41CPU
11 matches
Mail list logo
