Most of my ARM Android tasks are invalid

Guy
Guy
Joined: 20 Jan 06
Posts: 25
Credit: 58110033
RAC: 241293
Topic 230357

Hello,

Most of my ARM Android tasks are invalid and marked "Completed, validation inconclusive" or "Completed, marked as invalid".

It's Android 13 on a Samsung A34-5G phone.

I have no idea what the problem is.  Any help would be appreciated.

Thanks.

Snowball101
Snowball101
Joined: 22 Feb 23
Posts: 32
Credit: 2701588
RAC: 25493

Same problem here. No idea

Same problem here. No idea why.

Link
Link
Joined: 15 Mar 20
Posts: 101
Credit: 828583
RAC: 11129

Snowball101 wrote:Same

Snowball101 wrote:
Same problem here. No idea why.

It's the v1.51 (ASIMDPIE_1X) application, which your Android is running and which does not seem to validate well against the older (1.3x-1.4x) versions as well as against the newer ones, in particular the v1.7x Intel GPU versions.

I had similar issue on my Android device, which was however using the v1.47 (NEON) application, it often failed to validate against v.1.5x-1.7x, my solution was moving it with an app_info.xml to BRP4G, where it validates without any issues against the x86 CPU apps. I repoted it here.

No idea if that's a solution for you, you'll need to download one of the v1.4x applications first as your won't validate against the 1.33, I can help you with the app_info.xml if necessary. Your device also needs to be rooted for this.

.

Snowball101
Snowball101
Joined: 22 Feb 23
Posts: 32
Credit: 2701588
RAC: 25493

I am fairly new to rooting

I am fairly new to rooting though, and the communists from the mainland pressured Xiaomi (My phone manufacturer) to restrict unlocking the bootloader. Now one would have to pass a full-blown test to unlock the bootloader. Disgusting and ridiculous.

On the other hand, I could just try to look into task information and terminate those tasks which have other architecture CPUs/OSes running in the same workunit. Saves me jumping through geopolitical hoops.

Thanks for your help though!  

mikey
mikey
Joined: 22 Jan 05
Posts: 12069
Credit: 1834324605
RAC: 17298

Snowball101 wrote: I am

Snowball101 wrote:

I am fairly new to rooting though, and the communists from the mainland pressured Xiaomi (My phone manufacturer) to restrict unlocking the bootloader. Now one would have to pass a full-blown test to unlock the bootloader. Disgusting and ridiculous.

On the other hand, I could just try to look into task information and terminate those tasks which have other architecture CPUs/OSes running in the same workunit. Saves me jumping through geopolitical hoops.

Thanks for your help though!  

I have no clue if this is helpful or not BUT...I run 3 Raspberry Pi's running the Sidock short tasks with no problem, so maybe if you tried a different project it might help avoid the "hoops" of checking every single task to see if it's worth running or not. There are other Boinc Projects that have Arm tasks as well but I don't know them off the top of my head. but this page is a start, it's from 2024:

https://boinc.berkeley.edu/projects.php

Here is another website that shows every app at every Boinc Project, if you click on the word "Short" at the top of one of the columns you can see the aarch and arm ones.

https://stats6.free-dc.org/apps

Link
Link
Joined: 15 Mar 20
Posts: 101
Credit: 828583
RAC: 11129

Snowball101 wrote:I could

Snowball101 wrote:
I could just try to look into task information and terminate those tasks which have other architecture CPUs/OSes running in the same workunit.

No idea what the full-blown test is, but this definitely won't work as you can't check what other devices are running a WU before it's validated. Like this one for example. So if rooting isn't possible, moving that phone to another project like suggested by MIKEY might be the the best solution until Einstein@home staff finds the time to fix this validation mess in BRP4, the valid:invalid ratio for BRP4 is insane compared to BRP4G, lots of computing time is wasted.

.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.