JacobLinCool / JacobLinCool/particeps

Restore the full blocking API 37 host harness after the preview emulator renderer fix

Open
#33 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## Scope

Track the quarantined full host-orchestrated lane on the Android API 37 `google_apis_ps16k` x86_64 revision 5 preview image. The product compatibility gate remains blocking.

## Exact quarantined platform signature

A failed full host-harness run may be classified as the known emulator infrastructure defect only when its evidence contains all of:

- `mapper.ranchu.so`
- `SurfaceFlinger` process identity
- `Assertion failed: !rcEnc->featureInfo()->hasReadColorBufferDma`

Any Particeps App, VPN, `libgojni`, native, instrumentation, or test assertion failure remains blocking even if the platform signature is also present.

## Blocking API 37 evidence retained

- compile and APK installation
- 16 KiB runtime page size on system image revision 5 or newer
- manifest and Android 17 permission contracts
- source-built native library load
- storage instrumentation that does not invoke system task snapshots
- release verification of all four ABIs and 16 KiB ELF alignment

The API 34 lane continues to block on the full functional, VPN, TCP/UDP/DNS, throughput, lifecycle, kill/reboot, package, permission, and competing-VPN harness.

## Exit criteria

Restore the API 37 full host harness as an unconditional blocking gate after a newer `google_apis_ps16k` image no longer reproduces the exact renderer assertion. Remove the classifier/quarantine and obtain a complete passing run without modifying SystemUI, framework overlays, system server, or the system image.

## Prior evidence

Revision 5 failures reproduced on the stock preview emulator while Particeps assertions remained absent. Previous attempts to mutate SystemUI/framework state are intentionally being removed because they make the environment less representative of participant devices.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by locating the API 37 full host harness and its renderer classifier/quarantine, then compare it with the API 34 blocking lane. Done means a newer google_apis_ps16k image no longer produces the exact signature and the restored API 37 harness completes without the quarantine or system-image changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.