ubports/device-google-tegu
2
0
Fork 0
Code Issues 5 Pull requests Projects Releases 1 Packages Wiki Activity Actions

kvm-perms and sensor/vibrator fixes #14

Merged
deusch merged 7 commits from kvm-perms into main 2026-05-19 12:14:33 +02:00
Conversation 0 Commits 7 Files changed 8 +55
deusch commented 2026-05-19 11:38:54 +02:00
Owner
Copy link

Closes #10.
Closes #12.

Closes #10. Closes #12.
update device hacks
All checks were successful
build-final / build-builder-image (push) Successful in 24s
Details
build-final / final-artifacts (push) Successful in 13m29s
Details
4a908843d8
 
and add phablet user to kvm group

Closes #10.
Closes #12.
only restart hfd-service
All checks were successful
build-final / build-builder-image (push) Successful in 21s
Details
build-final / final-artifacts (push) Successful in 13m31s
Details
8b2ba23812
overlay: disable hfd-service LEDs to fix boot crashes
All checks were successful
build-final / build-builder-image (push) Successful in 26s
Details
build-final / final-artifacts (push) Successful in 19m21s
Details
b763ae911d 
Enumerating LEDs (which we don't have for a notification status
indicator) may crash hfd-service during boot, leaving it failed until
the next reboot. Force the dummy LED backend via a systemd drop-in.

Based on 1d6ccc29
overlay: wait for AIDL vibrator HAL in hfd-service drop-in
All checks were successful
build-final / build-builder-image (push) Successful in 20s
Details
build-final / final-artifacts (push) Successful in 13m34s
Details
9070350696 
Move the vibrator-readiness wait out of device-hacks: instead of
restarting hfd-service after polling for the binder service, force
the AIDL backend and gate the unit's startup on the vendor vibrator
init service being running.

Based on 953ba806b6
overlay: fix bluebinder ExecStartPre for tegu BT HAL
All checks were successful
build-final / build-builder-image (push) Successful in 22s
Details
build-final / final-artifacts (push) Successful in 13m39s
Details
590ef3acfa 
bluebinder 1.0.19 already speaks AIDL and connects to tegu's
android.hardware.bluetooth.IBluetoothHci/default, but the bundled
bluebinder_wait.sh greps for "init.svc.*bluetooth*" and tegu's BT
HAL service is named bcmbtlinux (no "bluetooth" substring), so the
wait never completes and the service restart-loops.

Override ExecStartPre with a tegu-aware getprop poll on
init.svc.bcmbtlinux=running. Verified: hci0 is up after this and
bluebinder logs "Bluetooth binder initialized successfully".
overlay: wait for AIDL sensors HAL in sensorfwd drop-in
Some checks failed
build-final / build-builder-image (push) Successful in 22s
Details
build-final / final-artifacts (push) Has been cancelled
Details
40aede37d7 
sensorfwd has no internal retry: if it starts before
android.hardware.sensors-service-multihal is registered, every
adaptor invalidates ("HYBRIS CTL invalid sensor type", "state
changed to invalid") and sensors stay broken until a service
restart.

Gate startup on init.svc.vendor.sensors-hal-multihal=running,
mirroring the hfd-service and bluebinder drop-ins.
move comment
All checks were successful
build-final / build-builder-image (push) Successful in 21s
Details
build-final / final-artifacts (push) Successful in 14m35s
Details
16a2d16d02
deusch merged commit b630d42ea2 into main 2026-05-19 12:14:33 +02:00
deusch deleted branch kvm-perms 2026-05-19 12:14:33 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ubports/device-google-tegu!14
No description provided.