Good afternoon, everyone! Can you simply connect your idle phone to @Acurast, leave it locked on the side, and expect it to continuously provide computing power? Wait—this isn’t as straightforward as it might seem. After carefully reviewing the official Processor 1.26.0 release notes, I discovered that both the Android Lite and Core versions at that time required foreground operation. The app can only sustain computational tasks while running in the foreground; once switched to the background or when the screen is locked, it stops sending heartbeats and processing task assignments. So even such a small action as locking the screen can disrupt your phone’s participation. Acurast does enable phones to join the computation network and earn $ACU incentives, including base Benchmark rewards and potential Staked Compute rewards for contributing pledged computing power. However, successful registration doesn’t guarantee ongoing compliance with operational requirements—and you certainly can’t assume that leaving your phone locked will automatically generate income. This behavior is clearly documented in Android Processor 1.26.0. Later versions, such as 1.27.2, addressed certain heartbeat issues during task execution, but as of the latest official release (1.28.0), the changelogs still do not explicitly state that the foreground requirement has been removed. I haven’t personally tested this behavior on the current version, so I can’t confirm whether all devices behave identically. If you’re planning to use an idle phone for this purpose, first verify your installed version against the latest operational requirements before deciding how to position your device. Remember: rewards matter, but so does device wear and tear—don’t end up damaging your battery in the process. #Acurast Official Version Notes: https://t.co/mi6O3Tfrtn https://t.co/V0ykswT9bd https://t.co/DnKD7pWbaq