platform_frameworks_base VS scrcpy

Also the commit was made to AOSP not any Pixel specific Android fork.

The code is in AOSP: https://github.com/aosp-mirror/platform_frameworks_base/commit/ecbed81c3a331f2f0458923cc7e744c85ece96da

>Their fix included a similarly large refactor

Their change is hardly a big refactor. This includes all the new code, all the parameter changes everywhere the function is used, and two additional test cases. This is a tiny change.

>12 changed files with 102 additions and 26 deletions. [1]

https://github.com/aosp-mirror/platform_frameworks_base/comm...

windowmanagerimpl

This seems to be an android 12 thing, cause AccessibilityServiceInfo in master branch doesn't define the isAccessibilityTool() function (since added in API 31) and attrs.xml doesn't define which you can get with android-31-2 sdk sources after setting compileSdkVersion=31 in android studio so that it can be used as android:isAccessibilityTool="true" in accessibility-service metadata file. The AccessibilityServiceInfo is currently just a stub class for sdk 31. Since you have android 12, maybe you have noticed the notifications already.

Shell have the following permissions: https://github.com/aosp-mirror/platform_frameworks_base/blob/master/packages/Shell/AndroidManifest.xml

First, we instantiate the ArrayAdapter by passing 3 arguments: context, layout and the array of data. We passed this for the Context as it represents the current activity. We chose simple_list_item_1 for the layout, which just contains a single TextView. And here we assume that there is an ArrayList called students containing a series of student names, which was passed as our 3rd argument.

So android gets the forced density value by calling getForcedDisplayDensityForUserLocked() which gets the system secure setting DISPLAY_DENSITY_FORCED. If the setting is unset, then android ignores it. According to this commit as mentioned here, android now writes secure settings to /data/system/users/0/settings_secure.xml for user 0 instead of a database. So all that is needed is to open that file in recovery and delete the entry for the key display_density_forced, save and reboot.

https://github.com/aosp-mirror/platform_frameworks_base/commit/66c7ea91b413c9d812047288efb343c16b23d865#diff-d0d0f287428f1314466cce035e6ae3a1

There's also https://github.com/Genymobile/scrcpy which works for any Android, not just Samsung

How did you manage that? I mean, what's the app name? Maybe srcpy can help you: https://github.com/Genymobile/scrcpy

GitHub - Genymobile/scrcpy: Display and control your Android device

Needs android 11 tho https://github.com/Genymobile/scrcpy/blob/master/doc/audio.md

View and control the watch from the PC with scrcpy (only Wear OS 3).