Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

HW accelerated Android testing

Open
  • Is something wrong?
#92 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, github-actions, kotlin
Domain
ci-cd, mobile, testing

Research direction

Start with the repository's CI configuration and identify the Android end-to-end testing job. Review the linked GitHub Actions hardware-acceleration guidance and add the KVM permissions step when larger runners become available; done means the job uses hardware acceleration and the end-to-end tests run successfully.

Written by the indexing model from the issue text.

Description

ci

Mentioned by @ShootingKing-AM here: https://github.com/ActivityWatch/aw-android/pull/85#issuecomment-1441898719

Just a note for much faster e2e testing on github actions - github.blog/changelog/2023-02-23-hardware-accelerated-android-virtualization-on-actions-windows-and-linux-larger-hosted-runners

All we'd need is to enable large runners, and add this to the CI config:

      - name: Enable KVM group perms
        run: |
            echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' | sudo tee /etc/udev/rules.d/99-kvm4all.rules
            sudo udevadm control --reload-rules
            sudo udevadm trigger --name-match=kvm

However, we don't have the GitHub plan required to enable large runners, which are a beta feature. Trying to apply for the beta gives me this:

image

So, we'll have to wait for now.

Dominant language
Kotlin
Stars
270
Forks
57
Avg merge
20h 32m
Merged PRs (30d)
38

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ActivityWatch/aw-android

All issues in ActivityWatch/aw-android

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.