Oh great ! ...:/ in ruined my installation in hopeing to getting an app to overlock the O-Droid , BIG MISSTAKE. And ...it can not be recovered, beause in 1 year i didn´t thinking of a backup this thing.
Great ! Now it´s Android again and NativeBOINC , easly to clock :D
Oh great ! ...:/ in ruined my installation in hopeing to getting an app to overlock the O-Droid , BIG MISSTAKE. And ...it can not be recovered, beause in 1 year i didn´t thinking of a backup this thing.
Great ! Now it´s Android again and NativeBOINC , easly to clock :D
Sorry for that, maybe I should write the discription a little bit more clear.
But maybe you can stick with linux and use the "orginal"-1.47NEON_Beta? Not shure if it's boosts performance much. But there is maybe less overhead when using Linux instead of Android. And it's better administrable, specialy for a headless configuration.
Quote:
It cannot, because the U3 has not an AARch64 Architecture (ARMv8). Currently only the C2 from Hardkernel can run this. The Pine64 should also be compatible.
The Raspberry Pi 3 is missing the right OS, I think.
Yes you are right with that, with only one little exception: It's not a generic-AARCH64-Application, it's special compiled for Cortex-A53. So devices with a Cortex-A57 or A72 might be not working.
The Pine64 should work fine. But the RAM-Reqirements are higher than the standart-BRP-App. Need's ~204MB per Task, it maybe fit into the 1GB-Version of the Pine64. But I would recomment the 2GB-version.
But maybe you can stick with linux and use the "orginal"-1.47NEON_Beta?
Too late, i have had to make a backup before, but i doesn`t. Somethings different with the new apt-get installation of boinc, sorry i get always computation errors , can´t continue on Lubuntu 14.xx.xx.
Edit:
btw the Ubuntu 16.xx image is interesting, i am getting this for the C1 and try it on the U3, and see whats happening...
Oh great ! ...:/ in ruined my
)
Oh great ! ...:/ in ruined my installation in hopeing to getting an app to overlock the O-Droid , BIG MISSTAKE. And ...it can not be recovered, beause in 1 year i didn´t thinking of a backup this thing.
Great ! Now it´s Android again and NativeBOINC , easly to clock :D
RE: Oh great ! ...:/ in
)
Sorry for that, maybe I should write the discription a little bit more clear.
But maybe you can stick with linux and use the "orginal"-1.47NEON_Beta? Not shure if it's boosts performance much. But there is maybe less overhead when using Linux instead of Android. And it's better administrable, specialy for a headless configuration.
Yes you are right with that, with only one little exception: It's not a generic-AARCH64-Application, it's special compiled for Cortex-A53. So devices with a Cortex-A57 or A72 might be not working.
The Pine64 should work fine. But the RAM-Reqirements are higher than the standart-BRP-App. Need's ~204MB per Task, it maybe fit into the 1GB-Version of the Pine64. But I would recomment the 2GB-version.
RE: But maybe you can stick
)
Too late, i have had to make a backup before, but i doesn`t. Somethings different with the new apt-get installation of boinc, sorry i get always computation errors , can´t continue on Lubuntu 14.xx.xx.
Edit:
btw the Ubuntu 16.xx image is interesting, i am getting this for the C1 and try it on the U3, and see whats happening...
Ok, there is already a Ux image ...
http://de.eu.odroid.in/ubuntu_14.04lts/
but not for 16.xx
That DID IT !!! Running again NEON BETA workunits....cheers !
RE: Yes you are right with
)
aha, a little hope for me and my u3 :D, i will edit...
I tested the application on a
)
I tested the application on a Pine64 2GB as well (Allwinner A64, 4 x 1.15GHz), average run time is around 20500 seconds...
https://einsteinathome.org/host/12429932/tasks