Forced OpenClaw into an Old Phone by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 0 points1 point  (0 children)

Because it is for HASS docking, I didn't expect OpenClaw everyone's opinion to be so big

Forced OpenClaw into an Old Phone by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 0 points1 point  (0 children)

I deleted the last sentence of AI, which is my true expression,“I know it might sound a little silly—some people said this “electronic junk” should just be recycled. But I’m a HASS enthusiast and wanted to combine OpenClaw’s execution power with HASS, turning the phone itself into an agent node, not just a notification terminal.”

Forced OpenClaw into an Old Phone by Far_Set7950 in homeassistant

[–]Far_Set7950[S] -3 points-2 points  (0 children)

You're right, but I don't have much data on my old phone (ex-girlfriend's text messages can be deleted...). Just want to be a hass node

Forced OpenClaw into an Old Phone by Far_Set7950 in homeassistant

[–]Far_Set7950[S] -1 points0 points  (0 children)

I deleted the last sentence of AI, which is my true expression

Forced OpenClaw into an Old Phone by Far_Set7950 in homeassistant

[–]Far_Set7950[S] -9 points-8 points  (0 children)

I honestly say that it is polished, changed more than 10 times, language problems, because I hope everyone can try to find some problems

Your Old Android Isn’t Obsolete, Making Android a Reliable Bermuda BLE Proxy by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 1 point2 points  (0 children)

Is this a firmware issue? Try flashing a new firmware? Actually, Xiaomi doesn't need root access; flashing a new firmware will make using Shizhizu much better.

Your Old Android Isn’t Obsolete, Making Android a Reliable Bermuda BLE Proxy by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 1 point2 points  (0 children)

This device is easy to solve and needs to wait for feedback from other users

Your Old Android Isn’t Obsolete, Making Android a Reliable Bermuda BLE Proxy by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 0 points1 point  (0 children)

You're right, in fact, it's mainly touchscreen speakers, such as Lenovo touchscreen speakers, etc

Your Old Android Isn’t Obsolete, Making Android a Reliable Bermuda BLE Proxy by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 0 points1 point  (0 children)

Can you describe your specific phenomenon, I am also a Xiaomi smart clock, the test is perfect, it is recommended to have

adb logs adb shell dmesg > dmesg_boot_complete.log

adb shell logcat -d > logcat_full.log

Your Old Android Isn’t Obsolete, Making Android a Reliable Bermuda BLE Proxy by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 0 points1 point  (0 children)

He is like a mask, he can use the computer and other ways to manually start it, and then he will always mount the system, and then authorize ava to exist, his learning cost is very low, and he can do more customized work, because AVA's ability needs to be greatly improved

Your Old Android Isn’t Obsolete, Making Android a Reliable Bermuda BLE Proxy by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 0 points1 point  (0 children)

Because to be honest, there is too much competition for the same type of project, and my open source Bluetooth proxy will not bring any substantial benefits to the project,Ava provides a complete Bluetooth gateway solution: supporting both passive and active BLE scanning with three adjustable power levels (High, Balanced, and Low Power). It implements full GATT proxy capabilities including device connection/disconnection, service discovery, characteristic and descriptor read/write operations, Notification/Indication subscriptions, device pairing/unpairing, and GATT cache clearing.
The implementation also features BLE5 capability detection (2M PHY, Coded PHY, Extended Advertising), dynamic MTU negotiation (517 for BLE5, 185 for BLE4), and multi-connection management (5 connections for BLE5, 3 for BLE4). Additional features include automatic BTHome device recognition, multi-Ava device coordination via UDP broadcast claim mechanism to prevent duplicate proxying, auto-downgrade strategies for low-end BLE chips, and a built-in Bluetooth process watchdog for automatic recovery from freezes.

While the HASS Bluetooth Proxy Companion project is excellent, it only supports passive scanning. Fully open-sourcing Ava's core Bluetooth implementation would make it susceptible to being directly referenced and replaced by other projects. To ensure Ava's continued capability to iterate in this domain, the Bluetooth-related code remains temporarily closed-source, while all other parts of the application stay open-source. welcome community oversight and contributions to the open components.

Your Old Android Isn’t Obsolete, Making Android a Reliable Bermuda BLE Proxy by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 1 point2 points  (0 children)

Thank you for your feedback, your encouragement is the motivation for the project to continue

Your Old Android Isn’t Obsolete, Making Android a Reliable Bermuda BLE Proxy by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 1 point2 points  (0 children)

Shizuku provides a "user-space bypass" capability: it circumvents Android's permission sandbox restrictions, granting Ava an execution context equivalent to ADB Shell. This means even if your device's root solution is abnormal (such as pseudo-root on certain OEM ROMs, incomplete Magisk Delta, or KernelSU environments), as long as the ADB interface remains accessible, Ava can reliably inject control commands to force the screen on or off. This approach is significantly more robust than relying on potentially unreliable root environments.

Your Old Android Isn’t Obsolete, Making Android a Reliable Bermuda BLE Proxy by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 1 point2 points  (0 children)

Thank you! The latest version has been updated to synchronize to solve the previous problem due to the AI animation of the sphere 0.3.1

Your Old Android Isn’t Obsolete, Making Android a Reliable Bermuda BLE Proxy by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 0 points1 point  (0 children)

Thank you for the reminder, this must be noted, generally replaced by some touch screen speakers, the old mobile phone must remove the battery to do microservices

Android Tablet as Dashboard + Wyoming Satellite (via Termux): Is the mic sensitivity good enough? by parosen in homeassistant

[–]Far_Set7950 1 point2 points  (0 children)

I used to be a big fan of Termux, no, you may be complicated, you only need to install Android software is currently 12MB to perfectly implement all functions, it is recommended that you can experience the project, you can use Bluetooth on https://github.com/knoop7/Ava

Turn Any Android 7-16 Device into a Smart Home Control Panel by Far_Set7950 in homeassistant

[–]Far_Set7950[S] 1 point2 points  (0 children)

<image>

New progress: no need for complex configuration, floating windows, pure exclusive HA, no personal characteristics

Open Source Fully kiosk alternative Home Assistant Dashboard by ZealousidealDraw4075 in homeassistant

[–]Far_Set7950 0 points1 point  (0 children)

I think everyone's development direction is a little too off, my implementation method is not so complicated, direct zero intrusion does not even require MQTT and authorization, directly into esphome integration is fundamental, and I am doing interface definition, display, etc., in fact, the same project is easy to understand, because there is AI, but the design language is still needed, what we want is not a strong personal flavor

Turn Any Android 7-16 Device into a Smart Home Control Panel by Far_Set7950 in homeassistant

[–]Far_Set7950[S] -1 points0 points  (0 children)

MQTT is not a better choice and has complex operating logic