@EmileDW See https://doc-snapshots.qt.io/qt6-dev/android.html "Android 6.0 or later (API level 23 or higher)"

If you want to connect for particular signal, first define the function in QML and use Connections object or <id>.signalName.connect(..) to connect with particular handler.

OK found a solution, for those interested, it's based on the fact that maybe the root item can't access the handle but the handle on the other hand can access the root item. So I created a binding between handle's state and slider's state : Slider { anchors { fill: parent margins: 10; } id: slider value: 0.5 style : SliderStyle { groove: Rectangle { id: background /* ... */ } handle: Rectangle { id: handle /* ... */ opacity: 0.0 // Bind slider's state and handle's state state: slider.state == "hovered" ? "hovered" : "" states : [ State { name: "hovered" PropertyChanges { target: handle ; opacity: 1.0 } } ] } } MouseArea { anchors.fill: parent hoverEnabled: true onEntered: { slider.state = "hovered" } onExited: { slider.state = "" } } states: [ State { name: "hovered" } ] }

Ok. Thanks.

@Ajith_P_V Yes that is right, you don't need to add the physical device. That was really just an extra option in case that was convenient to you later on : ) Have a look at creating kits for cross compiling in the qt docs if you can find it! - there are quite a few bits of info out there that may fill in the gaps I have left. I only gave the general steps required.

ok found the solution: in my .pro i hat a typo: target.files = config.conf .... // wrong _____________^_________ this needs to be: target.files += config.conf // right _____________^_________ also I hade multiple installation-targets and did not add target to installs in every build configuration. so for those who run in the same problem: be sure you add target to INSTALLS, target.files is already filled with your compilation output. use += not = to add other files