Status Update
Comments
ni...@google.com <ni...@google.com>
am...@gmail.com <am...@gmail.com> #2
We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
[Deleted User] <[Deleted User]> #3
tr...@gmail.com <tr...@gmail.com> #4
ni...@google.com <ni...@google.com>
of...@googlemail.com <of...@googlemail.com> #5
of...@googlemail.com <of...@googlemail.com> #6
ma...@gmail.com <ma...@gmail.com> #7
if this Issue is not Resolved Soon. I will (I dont Know) but i paid over 1500.00 for a Device and i cant Access the Stuff i want.... and Articles that i used back A.11 Days are now Denied Access... KB196422354
Android 13 is a Joke if it Prevents People from Technical Experence from Doing what they want heck thats what the Developer Mode was For. now you have Bricked us again...
ni...@google.com <ni...@google.com>
[Deleted User] <[Deleted User]> #9
ak...@gmail.com <ak...@gmail.com> #10
I can only support this if there is a way to fake the directory path that the app sees. That is, I need to be able to trick Chinese apps so that they can't tell the difference between me giving them a subfolder and them forcing me to give them access to all my files. Otherwise, this may threaten my physical safety when I travel.
I am the author of the other issue. I faced extreme trauma when my Chinese family compelled and coerced me to install the WeChat app. At that time WeChat closed itself on launch if it was not given the storage permission and my family kept pressuring me. Unlike the free world, China does not respect the freedom against search and seizure. Chinese companies can be forced to hand over any data to the Chinese government. Other Chinese apps mentioned in other issues are DJI and Insta360. What would happen if WeChat scanned a protest photo with my geolocation?
Back then I had Lineage AppOps and Xposed and was able to somehow restrict the storage permission. Today, those don't exist anymore. In the future I may be relying on solely how SAM keeps those apps in check. I have root so I love this feature, and do not hate it. I would rather Android remove the storage feature like earlier iOS than have a foreign government see my photos.
There is an alternative solution that both I and the power users above would accept. That would be to give me an option to trick any foreign app into thinking it was given any specified folder. Everyone else can then grant their backup and file managers access to their whole storage.
Description
- Relevant code to trigger the issue:
<?xml version="1.0" encoding="utf-8"?>
<android.support.constraint.ConstraintLayout
xmlns:android="
xmlns:app="
android:layout_width="match_parent"
android:layout_height="match_parent">
<android.support.constraint.Guideline
android:id="@+id/guideline_start"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:orientation="vertical"
app:layout_constraintGuide_begin="20dp"/>
<TextView
android:id="@+id/textView"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="TextView"
android:layout_marginStart="8dp"
app:layout_constraintStart_toEndOf="@+id/guideline_start"
app:layout_constraintTop_toTopOf="parent"
android:layout_marginTop="8dp"/>
</android.support.constraint.ConstraintLayout>
Guidelines don't behave as expected when layout direction is RTL. Fields for setting guideline position (layout_constraintGuide_begin, layout_constraintGuide_end) don't behave as start/end, rather as left/right. So it seems impossible to get the desired effect in this example. That being, on LTR layout guideline is 20dp from the left edge, and the text is to the right of the guideline (works correctly). On the RTL layout, guideline should be 20dp from the right edge, and the text to the left of the guideline (doesn't work like that).
Also, it doesn't make a difference if you set app:layout_constraintStart_toStartOf on the TextView (instead of "toEndOf").