Repository navigation
Ship the stub in the tizen5 package too, under the same gates (#105, #17) - #123
Merged
Merged
Conversation
…oo, under the same gates (issue 105, issue 17) The AU7200 runs Overscan with the stub in (issue 105), and whether a set lets an app map a library of its own is a property of the firmware, not of the Tizen version: the Q80 on 5.5 refused every location, Patrick's RU7020 on 5.0 has no wall at all, the AU7200 on 6.0 allows res/. So a 5.x set with the engine wall and not the mapping one has nothing to gain from the ladder passing unless the tizen5 package carries the stub. It now does, from Overscan6/res/ via a TizenTpkUserIncludeFiles item into res/, where EngineStub looks. Both signatures cover it. EngineStub's gates are unchanged: never loaded unless the engine has already failed on this install, withheld after two launches that did not come back with it in. On the Q80 this is one recorded refusal and the same screen.
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
1 participant
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.
The AU7200 runs Overscan with the stub in, and the thing that decided it, whether the firmware lets an app execute-map a library of its own, is per firmware and not per Tizen version: the Q80 on 5.5 refused every location, the RU7020 on 5.0 has no wall at all, the AU7200 on 6.0 allows
res/. A 5.x set with the engine wall and not the mapping one would pass the ladder and still get nothing, because only the tizen6 package carried the stub.Overscan5now ships the same file (Overscan6/res/libprivileged-service-client.so, one committed copy) into itsres/with aTizenTpkUserIncludeFilesitem. Checked in the built tpk:res/libprivileged-service-client.sois in the file list and in bothsignature1.xmlandauthor-signature.xml.EngineStubis unchanged, gates included: never loaded unless the engine has already failed on this install, withheld after two launches that did not come back with it in. On the Q80 it is one recorded refusal (engine stub: refused ... failed to map segment) and the same failure screen.CLAUDE.md and INTERNALS say which package carries what and why, and the Q80 section has a postscript.