Купить дорого или выжать максимум из китайского проектора HY-300 через ADB и реверс-инжиниринг прошивки

Купил портативный проектор HY-300 — оказался не самым "ярким" представителем. Через ADB и root добрался до прошивки, нашёл скрипт testgamma, который при каждой загрузке занижает яркость до 70%. Разобрался как работает gamma LUT в видеопроцессоре VOP, какие параметры реально влияют на картинку, а какие — пустышки. Пошаговая инструкция по выжиманию максимума из проектора.

https://habr.com/ru/articles/1013176/

#HY300 #проектор #Rockchip #RK3326 #ADB #gamma_LUT #яркость #Android_TV #reverse_engineering #testgamma

Несколько мобильных приложений в одном Appium‑проекте: как это можно организовать

Как тестировать несколько мобильных приложений в одном «Appium‑проекте». Показываю архитектуру фреймворка, запуск тестов через аннотации, потокобезопасный контекст и подключение новых приложений без дублирования кода.

https://habr.com/ru/articles/1010216/

#appium #java #android #adb #android_studio_emulator #allure #junit5 #selenide #mobile_testing #qa_automation

PS/2 ou ADB ?

Les deux prises se ressemblent terriblement, mais ne confondez pas l'ADB avec le PS/2 !

https://video.neliger.com/w/iCannjNfRZMrmQENkWYAqR

#ADB #PS2 #Apple #retro #retroTech #vintage #vintageTech #oldTech #retroComputing #PeerTube

PS/2 ou ADB ?

https://video.neliger.com/w/iCannjNfRZMrmQENkWYAqR

Pixel Watch 2 - Privacy Preserving Setup

I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

• Unpairing the Watch means factory resetting it.
• Every feature (literally everything) is google dependent (who would have thought.. i know)
• Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

After the watch was set up, i continued and:

• Deleted the user profile from which i connected the Watch
• Enabled wireless debugging
• Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
• Removed the Google account in the settings
• Cleared all Bluetooth preferences
• Enabled Bluetooth discovery
• Installed KDE Connect on it (not meant for WearOS but it does work barely)

The watch is now in a state where i can use it daily.

But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

Now comes the fun part.

I've created a basic Kotlin project with both a mobile and WearOS app.

I will implement features like:

• Notification sync
• Call notifications
• Media Player Control
• Weather (openweathermap)
• Heartrate monitoring
• Sleep tracking
• Do not Distrurb Sync
• Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
• And much more ..

The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

Cheers.

#privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

Ab September 2026 wird #Google auf #zertifizierten #Android Geräten das #Sideloading von #Apps einschränken/Blockieren!!!

Blockade nicht zertifizierter Apps:

Installation von APKs oder Apps aus #Drittquellen (z. B. #FDroid) wird standardmäßig unterbunden.

Betroffene Geräte:

Alle Android-Geräte mit #GoogleMobileServices (GMS)-Zertifizierung.

Technische Hürden:

Nutzer müssen ggf. manuelle Freigaben (z. B. über #ADB) vornehmen oder auf nicht zertifizierte Geräte ausweichen.

Ausnahme:

#Enterprise oder #Entwickler Modi könnten Umgehungen ermöglichen?!

Begründung:

Google verweist auf #Sicherheitsrisiken durch #Malware, Kritiker sehen darin eine #Marktbeherrschung zugunsten des #PlayStores !

Folgen:

Alternative #AppStores und #OpenSource Projekte verlieren an Zugänglichkeit.

#linux #bigtech #BigTec #fuckgoogle #alphabet #customrom #lineageos #grapheneos #gms #stockandroid #socialmedia #mastodon #freedom

https://keepandroidopen.org/de/

Github Awesome (@GithubAwesome)

droidclaw는 오래된 안드로이드 폰을 AI 에이전트로 전환해 목표를 수행하도록 만드는 프로젝트/도구. 화면을 읽고 추론한 뒤 ADB를 통해 탭·타이핑·스와이프를 실행해 작업을 완료하므로 별도 API 없이 설치된 앱만으로 자동화 가능.

https://x.com/GithubAwesome/status/2027336446370074767

#droidclaw #android #agents #adb #automation