Assigned
Status Update
Comments
ad...@google.com <ad...@google.com>
je...@google.com <je...@google.com>
sp...@google.com <sp...@google.com> #2
Information redacted by Android Beta Feedback.
fl...@obfusk.net <fl...@obfusk.net> #3
Could you please let me know if the issue here is the inner screen is not working and the outer is working fine?
sp...@google.com <sp...@google.com> #4
Is says more info needed? What else should I include? I'm so upset sorry
On Sat, Nov 16, 2024, 2:36 AM <buganizer-system@google.com> wrote:
On Sat, Nov 16, 2024, 2:36 AM <buganizer-system@google.com> wrote:
fl...@obfusk.net <fl...@obfusk.net> #6
sa...@google.com <sa...@google.com> #7
When I open my pixel fold the screen is on but everywhere I touch there is
no response. I usually have decent experiences being on beta testing but
that's usually with apps not OS but I gotta tell ya not being able to use
my fold like a tablet sucks and it did it all the sudden and then yesterday
for like 3 hours I couldn't even hear music and I guess it figured itself
out.
Please tell me your looking into the fold screen issue please ☹️
Thank you
On Sat, Nov 16, 2024, 6:57 AM <buganizer-system@google.com> wrote:
no response. I usually have decent experiences being on beta testing but
that's usually with apps not OS but I gotta tell ya not being able to use
my fold like a tablet sucks and it did it all the sudden and then yesterday
for like 3 hours I couldn't even hear music and I guess it figured itself
out.
Please tell me your looking into the fold screen issue please ☹️
Thank you
On Sat, Nov 16, 2024, 6:57 AM <buganizer-system@google.com> wrote:
sa...@google.com <sa...@google.com> #8
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
sa...@google.com <sa...@google.com> #9
Thank you for reporting this issue. We have a fix rolling out now.
Description
Unlike
apksigner
,signflinger
adds a 132-byte virtual entry at the start of every APK it signs with a v1 signature; I assume an emptyMANIFEST.IN
used to be here.This makes it much harder to create reproducible builds, as the signed and unsigned APK differ in more than just the v1 (JAR) signature files and APK Signing Block.
And it's not just the presence of the virtual entry itself: its presence also results in different ZIP alignment padding in the local header extra fields for .so files, which are aligned to 4096 bytes.
Other files just happen to be unaffected since 132 is a multiple of 4, but AFAIK the size would change if the deleted empty (apart from the
Manifest-Version: 1.0\r\nCreated-By: Android Gradle 7.1.3\r\nBuilt-By: Signflinger\r\n\r\n
header)MANIFEST.IN
contained a AGP version string of a different length.This does not happen when using
apksigner
, only when building a signed APK withsignflinger
(via Android Studio or a Gradle signing config).See alsohttps://github.com/obfusk/apksigcopier#what-about-apks-signed-by-gradlezipflingersignflinger-instead-of-apksigner