Pixel Watch 4 information #29842
robertkirkman
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Wear OS 6.1, 32-bit ARM Android 16 ROM with 64-bit ARM kernel and quad-core 64-bit ARM CPU with 2 GB of RAM
Has a tendency to always disconnect from WiFi by itself after a little while of being connected, even while being actively used, and to reconnect to WiFi every ~60 seconds it's necessary to go to the settings app and then touch the Connections sections and then it connects to WiFi, but there is an option in Developer Options to remain connected to WiFi while the charger is connected, and that works.
Some actions, tasks and visual effects make the device start running very slowly and the FPS of SurfaceFlinger visibly drops. Enabling the Developer Option "Show Taps", a cursor overlay for the touchscreen inputs, adds a significant and noticeable amount of input delay and FPS drops to the rendering that do not occur on more powerful devices.
If running something too intensive for too long, like GitHub in Firefox, the device will close all apps, turn off WiFi Debugging, and show a message saying "your watch has overheated, move it to a cooler place".
The SurfaceFlinger implementation does not have a App Switcher screen and does not appear to support multiple simultaneous windows on the screen in any way. Instead of an App Switcher screen, closing running apps can only be explicitly done through the UI at the "force stop" button. Termux does remain running in the background while other apps are on the screen.
Wireless debugging and scrcpy both work and most apps are square in scrcpy, while some are still circular, greatly powering up input and video practicality when developing on the device.
There is no USB port but there is a controversial rumor online that there might be four hidden USB port contacts underneath one of the edge flaps that might be possible to use to connect fastboot.
UNLIKE most other Android 16 ROMs, it does NOT appear to have a "disable child process restrictions" option in Developer Options. However, I believe that I was able to disable phantom process killing by using the ADB method:
Fennec F-Droid has a crash on startup:
Fennec F-Droid crash
However, Firefox from FFUpdater from F-Droid works.
UI images
F-Droid is extremely difficult, but possible to use.
termux-info:
Current plan: I will try to make a fork of Hacker's Keyboard with buttons moved into a semicircle shape so that Termux and Termux addons can be fully used with all keyboard buttons on circular screens
Beta Was this translation helpful? Give feedback.
All reactions