adb over ethernet about h3droid HOT 18 OPEN

hi, usually you'd want to use ssh instead of adb ( installation of private keys is done via h3config (space bar at boot)). but you can also add to /data/rc.local
here's something that will set board serial and restart adbd in net mode on port 5555

#!/sbin/busybox sh

if [ -f /data/data/board ]
then
    echo -n $(cat /data/data/board) > /sys/class/android_usb/f_accessory/device/iSerial
else
    echo -n data_data_board > /sys/class/android_usb/f_accessory/device/iSerial
fi


setprop service.adb.tcp.port 5555
stop adbd
sleep 1
start adbd
sleep 1

scaa=/sys/class/android_usb/android0

echo 0         >$scaa/enable
echo 1f3a      >$scaa/idVendor
echo 1002      >$scaa/idProduct
echo 239       >$scaa/bDeviceClass
echo 2         >$scaa/bDeviceSubClass
echo 1         >$scaa/bDeviceProtocol
echo rndis,adb >$scaa/functions
echo 1         >$scaa/enable

echo 2 > /sys/bus/platform/devices/sunxi_usb_udc/otg_role

from h3droid.

i need set up touchscreen .and root but i dont see /data/rc.local I should create it?
how i load on boot if I create it?

from h3droid.

create /data/rc.local and add all sh script you need to run as root from here, it will be loaded once each boot

from h3droid.

btw. root enabler is also available via h3resc, please read what you can do with h3droid:
http://h3droid.com/faq
http://h3droid.com/h3resc

from h3droid.

also, you might need to tune config for your board (.fex) to make ethernet and other things work

from h3droid.

Hi guys, thanks for your help. With your tips I was able to enable the hid-multitouch driver and load adb at system startup.
The magic is done by creating rc.local being root and giving it 755 permissions, the system executes it when the system starts up. In case someone else needs this information.

however the app I need was developed for android 10 and it doesn't work.
my question is how complicated it would be to try to compile a more modern version of android for these allwinner H3.

is it possible at least?

The versions that I find are from Android 10 TV that does not have a touchscreen. i can't install magisk to be able to search for the driver within the system. i doubt it exists from what i've read

from h3droid.

there was android7 sdk, but it's not working that well. also there was a project for aosp 9/10 which works, but without media acceleration

from h3droid.

hello again -I continue trying to solve the touch panel issue for android 10 with kernel version 4.9.170.

I have managed to compile hid.multitouch.c in arm linux version
vermagic: 5.15.48-sunxi SMP mod_unload ARMv7 thumb2 p2v8
but the modules loaded in the android show
vermagic: 4.9.170 SMP preempt mod_unload modversions ARMv7 p2v8

can i do about it? the module does not load due to differences
and I couldn't find armbin with the same kernel version

Please help I've been on this issue for weeks.
and I refuse to believe that it is impossible to put a touchscreen on android tv 10.

from h3droid.

you can compile kernel with the options you need, just download it from https://kernel.org (you dont need to run it, compiling and then copying that module should be enough)

from h3droid.

hello kotc thanks for your interest in my problem.
yesterday I downloaded the kernel sources .4.9.170
try to compile a kernel for the first time.

but I have not been able to reach the desired vermagic
4.9.170 SMP preempt mod_unload modversions ARMv7 p2v8
I have only achieved this
4.9.170 SMP preempt ARMv7 p2v8

about this I could not find information "mod_unload modversions"
make menuconfig does not give me clear information

I'm in this for 24 hours and I haven't made it.

any other suggestion for this "mod_unload modversions" ?

from h3droid.

I succeeded. The options were somewhat hidden in menuconfig. The .ko shows the following
vermagic: 4.9.170 SMP preempt mod_unload modversions ARMv7 p2v8

I think I have taken a step further. I thought I had achieved it
but modprobe doesn't work. it reports that the file doesn't exist in modules.def

insmode reports no such file or directory .

I think that for android 10 these commands changed.

Is there anything known about this?

from h3droid.

you have to specify full path and file name for insmod, ie.: /some/path/filename.ko

from h3droid.

Hello again. I'm sorry to insist so much on this topic. But this is the only site where I've had some help. I hope I don't bother.

but the behavior of insmod and modprobe is very strange. If I try to insert an invalid module, it tells me a format error, but if I do it correctly, vermagic responds that it cannot find it.

Is there any extra security? Or is the file still wrong, regardless of whether vermagic looks the same as the loaded modules?

from h3droid.

what is the exact command and result? also, is anything showing in dmesg after the command?

from h3droid.

hello kotc. one more step.
but with busybox insmod I got more info and with demsg I complemented it

hid_multitouch: Unknown symbol __gnu_mcount_nc (err 0)
this is the next problem to overcome

from h3droid.

ftrace option was responsible for the __gnu_mcount_nc.
I managed to load the hid-multitouch module through insmod followed by the path .

but when connecting the touch panel, android restarts :(
I can not believe it.
I have read something about the configuration of touch pads. Also the dependencies.
But I don't know where else to look for information.

from h3droid.

hi again .i have this log form load module

[ 465.084914] hid_multitouch: no symbol version for module_layout
[ 465.112243] type=1400 audit(1657554968.345:161): avc: denied { module_load } for comm="insmod" path="/lib/modules/4.9.170/hid-multitouch.ko" dev="dm-0" ino=331 scontext=u:r:su:s0 tcontext=u:object_r:rootfs:s0 tclass=system permissive=1

This is from before connecting the panel. After connecting it I have not been able to recover anything.
does this help anything?

from h3droid.

those permission issues were partly the reason why h3droid didnt receive android7 update. sadly i can't help you much there

from h3droid.