Harden T56 one-shot provisioning - #13
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
un-as Wi-Fi handoff with a DUMP-protected, nonce/path-bound receiver and private fsynced status protocol
Root cause
The factory T56 has no usable
un-as, and Android 5.1 does not reliably expose nested ordered-broadcast JSON. After registration, a single transient connection error also caused an otherwise valid config candidate to roll back immediately.
Validation
Acceptance scope
This proves safe recovery of the partially provisioned T56. It is not a pristine factory one-shot run, so Issue #6 and release promotion remain open pending clean bundle/release and remaining device-profile acceptance gates.