New Android 14 Panel - How to create profile?

[davidcoulson]

ha-paneld version

0.9.7-rc2

Panel hardware

Other (state in description)

What happened?

I just got a new 5.5" Android 14 Panel to replace my super slow NSPanel Pro... It's similar to the SMT1019s I have with the rk3536 SOC.

Is there documentation or a process to identify how to create a profile for this device? it seems to be working with as a generic device, but obviously would like to get it as polished as possible.

No colored LEDs, no camera or proximity sensors,

Steps to reproduce

No response

Diagnostic dump (/diag)

ha-paneld diagnostics — 0.9.7-rc2 (build 613)
[captured] 2026-08-28T01:36:14.663348Z uptime=4h23m

[panel]
ha-paneld=0.9.7-rc2 (build 613)
Android=14 (API 34)
Firmware=P76S01-A14-SM55P-JD9365-720x1280-20260612-V0.01
Device=rockchip rk3576s_u (rk3576s_u)
CPU=8 cores · arm64-v8a · rk30board
RAM=3.8 GB total · 2.4 GB free
Storage=62.5 GB eMMC · 54.4 GB free (data)
Display=720×1280 px · logical 240 dpi
System WebView=com.google.android.webview 152.0.7977.64
HA Companion=not installed
MQTT state=connected · TCP/IPv4 · last-ok 52s ago · last-auth 11272s ago · auth-ok · family Automatic (next IPv4)
Security mode=Relaxed
Keep panel responsive=on · power locks held
Prevent idle dim=on · timeout never
Android dashboard lock=off
LED=none
Nav actions (a11y)=yes
Navbar=Off
Zigbee=none
Relays=none
Network ADB=active (5555) · external — not persisted by ha-paneld
Audio playback=idle
App database=2.5 MB used · 2.9 MB on disk · schema 14
Product version=1.0.0
State convergence=37 channels · 0 dirty · 0 in-flight · 15 unknown · ack 215/1 · pending none

[build] fingerprint=rockchip/rk3576_u/rk3576_u:14/UQ1A.240205.004.B1/eng.liu_li.20260613.110540:userdebug/release-keys
board=rk30sdk product=rk3576s_u hardware=rk30board abis=arm64-v8a
[boot-security] verified=orange flash=unlocked vbmeta=unknown build=userdebug debuggable=yes
[env] selinux=0 su=true write_settings=true a11y=true daemon=true shizuku=manager_missing evdev=stopped/none ledjni=false
[display-sizing] android_base_logical_dpi=240 current_logical_dpi=240 override_dpi=none font_scale=1.0 profile_recommended_dpi=? profile_recommended_font_scale=none
[renderer] mode=builtin state=rendered outcome=ok fault=none detail=none recovery=none transport=http address_family=automatic observed_age=3h7m
[storage-health] state=healthy pressure_state=healthy usable_bytes=54462423040 total_bytes=56104923136 used_percent=2.9275507463374133 database_bytes=2355200 wal_bytes=45352 sidecar_bytes=32768 page_size_bytes=4096 page_count=575 freelist_count=0 schema_version=14 quick_check=ok checked_at=1787869700829 failure=none
[power-safety] state=safe keep_awake=true wake_lock=true wifi_lock_required=true wifi_lock=true prevent_idle_dim=true screen_timeout_ms=2147483647 interactive=true power_source=ac plugged_mask=1 stay_on_mask=15 stay_on_effective=true device_idle=false doze_exempt=true screen_off=brightness_zero reasons=none
[sysfs] leds=[mmc2::] backlight=[backlight] devfreq=[27700000.npu, 27800000.gpu, 27d00000.vop, dmc]
[labels] ls: /dev/ledjni: No such file or directory u:object_r:sysfs:s0 /sys/class/backlight/backlight/ u:object_r:sysfs:s0 /sys/class/leds/mmc2::/
[hardware]
  inputs=[chsc_cap_touch (event0 dmcfreq ), rk805 pwrkey (event1 dmcfreq ), gsensor (event2 ), bt-powerkey (event3 dmcfreq ), adc-keys (event4 dmcfreq ), rockchip,multi-sound Headset (event5 )]
  i2c=[0-002e:chsc_cap_touch, 1-0023:rk806, 2-0015:gs_mxc6655xa, 2-0051:hym8563, 3-0010:es8388, 3-0032:ES7202_PDM_ADC_1, 4-003c:gc2145, 7-0024:ls_em3071x, 7-0038:aht20, i2c-0:rk3x-i2c, i2c-1:rk3x-i2c, i2c-2:rk3x-i2c, i2c-3:rk3x-i2c, i2c-4:rk3x-i2c, i2c-5:rk3x-i2c, i2c-6:rk3x-i2c, i2c-7:rk3x-i2c]
  iio=[]
  thermal=[cooling_device0:cpufreq-cpu0, cooling_device1:cpufreq-cpu4, cooling_device2:devfreq-dmc, cooling_device3:devfreq-27800000.gpu, cooling_device4:devfreq-27700000.npu, thermal_zone0:soc-thermal, thermal_zone1:bigcore-thermal, thermal_zone2:little-core-thermal, thermal_zone3:ddr-thermal, thermal_zone4:npu-thermal, thermal_zone5:gpu-thermal, thermal_zone6:test_battery]
  relays=[]
[packages] android=not installed minimal=not installed
[capabilities] Root (su)=ok | Shizuku enhanced access=none | Verified app update / screenshot / display=ok | Screen brightness=ok | Screen on/off=degraded | RGB LED=none | Hardware buttons=ok | Reboot / reload / launcher=ok

Home Assistant version

No response

Relevant logs

[maxlyth]

This is exactly the kind of panel the profile system is intended to support. The /diag is a useful start and shows a promising device: working root, network ADB and a userdebug Android 14 firmware.

Could you add a few more things?

• The exact product or purchase listing, plus any manufacturer product, support, manual or firmware-download pages you can find.
• The Generic device draft from the Profiles page. You can download it directly from http://<panel-ip>:8888/api/v1/profiles/device-draft; please review and redact it before posting.
• Redacted photos of the front, rear, ports and product label. Please hide serial numbers, MAC addresses, QR codes and licence IDs.
• How ADB and root were enabled, whether they survive a reboot, and whether the manufacturer provides a flashing or recovery tool.

An original manufacturer ROM or OTA download would be the best firmware source. If there is no public image, a selective root-assisted dump could still tell us a lot about the device tree, sensors, vendor services and control paths. Please do not attach a complete device dump publicly because it may include personal data and unique device identifiers. Once we have the partition layout, I can suggest a safe set of partitions and arrange a private transfer.

The diagnostic names several interesting hardware candidates, including gc2145, ls_em3071x, aht20, an accelerometer and several input devices. Those entries do not prove that every component is physically fitted or usable, so the next step after the device draft will be a few short, read-only tests for the sensors, buttons and backlight.

[davidcoulson]

Here's the product: https://www.aliexpress.us/item/3256809190421440.html - There are plenty of pics but if you want others LMK. I was able to get adb via the standard android settings and used Magisk to root it. I'll get you a private link to the firmware once the vendor sends it over.

These are the partitions it ships with, so LMK which ones you need:

% rkdeveloptool ppt
**********Partition Info(GPT)**********
NO  LBA       Name
00  00002000  security
01  00004000  uboot
02  00006000  trust
03  00008000  misc
04  0000A000  dtbo
05  0000C000  vbmeta
06  0000C800  boot
07  0002C800  recovery
08  0005C800  backup
09  0011C800  cache
10  001DC800  metadata
11  001FC800  frp
12  001FCC00  baseparameter
13  001FD400  super
14  00811400  userdata

Profile draft:

schema: 2
id: generic
version: 2.0.1
display_name: Unknown panel
soc_class: "?"
metadata:
  author: ha-paneld maintainers
  source: https://github.com/maxlyth/ha-paneld/blob/main/docs/architecture/device-profiles.md
  license: Apache-2.0
  maturity: verified
  tested_firmware: []
  limitations:
    - Unknown vendor hardware stays disabled until an exact profile is selected.
requires:
  min_core_version: 0.9.3
  drivers:
    - access.android-su
    - led.autodetect
    - screen.brightness-zero
match:
  # Empty matching is intentional: this is the safe fallback for unknown panels.
  priority: 0
  fallback: true
  any: []
platform:
  # Conservative defaults; unknown hardware must not assume privileged access.
  su_form: android
  app_can_su: true
  has_recents: true
hardware:
  led:
    mechanism: autodetect
    transfer: rk3576-four-bit
  screen_off: brightness-zero
  has_button_backlight: false
sensors:
  cht8305: false
  room_temp_offset_c: 0.0
identity:
  model_label_strategy: display-name
input:
  evdev_buttons: []
cpu: {}
display: {}
provisioning:
  software: {}
  display: {}
  packages: []
  recipes: []

[Orange-GT3]

Here's the product: https://www.aliexpress.us/item/3256809190421440.html

That is the same seller that I bought my 15.6" panel from.

[davidcoulson]

That is the same seller that I bought my 15.6" panel from.

I have one of those on the way. Any issues with it?

[Orange-GT3]

That is the same seller that I bought my 15.6" panel from.

I have one of those on the way. Any issues with it?

Mine is the older model, bought pre-September 2025, with Android 13. It's a little slow but otherwise great. I power it using PoE. The seller recently supplied me with a rooted firmware too.

[maxlyth]

This is enough to move the support investigation forward. The product listing, profile draft and partition map give me the device identity and layout I need, and the vendor firmware will be a better starting point than a dump taken from the live panel.

Once the vendor sends the firmware, a private link to the package exactly as supplied is best. I can inspect its boot, device-tree and system images, then come back with a profile proposal and only the hardware tests that cannot be answered from the firmware.

[davidcoulson]

@maxlyth - here's the firmware for the 5.5 panel.

https://drive.google.com/file/d/1BiEYPI1amVKZ2PfbRPF1B90Ioao2C4R2/view

I have a 15.6 panel coming later in the week so asked for that too. Same hardware, just bigger display.

[maxlyth]

I have archived the 5.5-inch firmware unchanged and completed the first inspection. It confirms the RK3576S/P76S01 board, Android 14, a PWM backlight, CHSC touch and the volume keys, so there is enough evidence for the base profile without guessing from the live panel.

The firmware also declares AHT20 climate, EM3071x light/proximity and GC2145 camera hardware. Those entries agree with the I2C devices in your /diag, but they can still be optional board parts. I have left them disabled until we run a short physical check.

I have prepared the import-only YC-SM55P profile and testing notes. The Android identity is the generic rk3576s_u, which is too broad for safe automatic matching, so this profile must be imported and selected manually.

Please wait for 0.9.7-rc3 before activating it. rc2 can roll an imported profile back during its restart; that fix is already on the rc3 line. Once rc3 is available, the first activation can confirm the remaining hardware. I would still compare the 15.6-inch firmware when it arrives before assuming it shares the same display and fitted parts.

[davidcoulson]

Thanks - I'll keep my eyes out for rc3.

It has neither a proximity sensor nor a camera. Not sure if it has a basic lux sensor, but will check it out once I can apply the profile.