Hello lalenium,
You are running on a 1.5 Ghz Qualcomm Snapdragon CPU. It has 4 cores, each powered independently. You have 2 GB RAM and "up to 16GB" internal flash to serve as hard disk. Some of your results are valid, but most aren't.

Given this information, I assume that you are running into a problem caused by an imperfectly implemented board design. Too much heat without enough cooling; dropped bits when offloading RAM to flash; etc. I would try to simplify everything to keep from over-stressing your system. First, change your preferences to only run 1 thread instead of 4. Go to My Grid - Device Manager - (Selected Profile). Actually, you might as well select a named profile like HOME and start changing it. Switch it to Maximum Output so it will give the program whatever it needs, then switch the Maximum Output to Custom Profile so you can change individual settings and set it to only run on 25% of your cores (1 thread) and SAVE it. Also, I would change it to run 100% of the time plugged in and check the temperature. If it overheats, reset that value to 50% (1 second on, 1 second off) for cooling. This should minimize power drain, heating and program off-loading.

Run it this way and see if the results are better. If not, then something completely different is wrong, If all the results are VALID, then the problem has been identified. If that is the case, you might want to explore running 2 threads, but no more.

Lawrence

Hello lalenium,
Good luck! I forgot to say that "Leave Application in Memory" should be ON. After all, it will only take up a tiny part of 2 GB RAM and might save time and reduce memory-shuffling.

Lawrence

Hello lalenium,
Experience is showing that many mobile devices are really designed for 1 core. Maybe this will slowly change in the future.

Lawrence

Hello markop619,
Yes. Running only one work unit on a mobile device seems to solve many problems.

Lawrence

lalenium and markop619, some people that have trouble with Berkeley's version have luck with nativeBOINC and vice versa. You may want to give it a shot and see if it does any better. I couldn't tell you why there are sometimes mixed results. I could only guess it to be either the version of BOINC it is based on or just compatibility with certain devices. My older phones aren't supported by Berkeley and are forced to use nativeBOINC. My Bionic however runs both quite well. The differences on that phone are that BOINC "feels" smoother but seems to run my battery down quicker when the app is idle. nativeBOINC would sometimes restart my phone when shutting down the app. nativeBOINC also gave me more control over the device settings as well. Anyways, that is just a suggestion.