Device will not register because Hardware Id is empty (Android Chroot ENV)


#1

I am running Flytos in a chroot environment on Android and when doing intial setup I get the following error when trying to activate the license.

Device will not register because Hardware Id is empty

Any help on solving this issue would be great
Thanks in advance flytos community.


#2

May I know why you are trying to run FlytOS in an Android chroot environment?

I don’t think there is a way to bypass the error ‘Device will not register because Hardware Id is empty’. I would try to look into it though.


#3

Thanks for the response. I am running android for multiple reasons. 2nd gps and small battery for redundant gps location when flight computer is down. Also I am using Verizon 4G LTE for a L2TP/IPsec VPN Protocol for local network Ground Control communication over LTE.

In my experience I can not at all get L2TP/IPsec VPN Protocol working on Ubuntu.

You would think that the hardware id could be set manually in kernel or init. Any help is greatly appreciated.


#4

Okay well the web string lists my hardware when trying to register;

hwid=None&devtype=nvidiatk1&cpuname=Nvidia%20Jetson%20TK1&arch=arm32&hostos=None&mi=


#5

Sorry for the delay in response.

Can you please explain how did you install FlytOS in the android chroot environment?
Moreover, can you please run these commands:

lsblk
dmidecode

and share their output here.


#6

Thanks for the reply. I am running the chroot with super user rights in linux deploy (used the TX1 wget install script) all functions work just no device id so no flytos api only mavlink with Ground Control connection.

Let me re-flash my android build and post the output here.


#7

ubuntu@localhost:~$ sudo dmidecode

dmidecode 3.0

Scanning /dev/mem for entry point.

No SMBIOS nor DMI entry point found, sorry.

ubuntu@localhost:~$

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
└─sda1 8:1 0 111.8G 0 part / <–UBUNTU
loop0 7:0 0 96M 0 loop
mmcblk0rpmb 179:16 0 4M 0 disk
mmcblk0 179:0 0 14.7G 0 disk <-- ANDROID
├─mmcblk0p1 179:1 0 2.5M 0 part
├─mmcblk0p2 179:2 0 512K 0 part
├─mmcblk0p3 179:3 0 2M 0 part
├─mmcblk0p4 179:4 0 2M 0 part
├─mmcblk0p5 179:5 0 512K 0 part
├─mmcblk0p6 179:6 0 16M 0 part
├─mmcblk0p7 179:7 0 4M 0 part
├─mmcblk0p8 179:8 0 16M 0 part
├─mmcblk0p9 179:9 0 1.3G 0 part
├─mmcblk0p10 179:10 0 768M 0 part
├─mmcblk0p11 179:11 0 2M 0 part
├─mmcblk0p12 179:12 0 32M 0 part
├─mmcblk0p13 179:13 0 2M 0 part
├─mmcblk0p14 179:14 0 16M 0 part
├─mmcblk0p15 179:15 0 12.6G 0 part
└─mmcblk0p16 259:0 0 512K 0 part


#8

Some more info:

INFO in server [/flyt/flytos/flytcore/lib/python2.7/dist-packages/rostful/server.py:184]:
Starting Tornado server on 0.0.0.0:80

[ INFO] [1531880376.194287966]: VER: 1.1: Capabilities 0x000000000000e4ef
[ INFO] [1531880376.194572716]: VER: 1.1: Flight software: 010800ff (0000000096443B3C)
[ INFO] [1531880376.194731049]: VER: 1.1: Middleware software: 010800ff (0000000096443B3C)
[ INFO] [1531880376.194946049]: VER: 1.1: OS software: 071600ff (0000000000000000)
[ INFO] [1531880376.195143632]: VER: 1.1: Board hardware: 00000011
[ INFO] [1531880376.195300466]: VER: 1.1: VID/PID: 26ac:0011
[ INFO] [1531880376.195442466]: VER: 1.1: UID: 3137510730323635


#9

Hi @Matthew_Gorski,

sorry for the delayed response.

Can you please try out these calls:

lsblk --nodeps -o name,serial
cat /sys/block/sda/device/cid

In the meantime, I will try to find out a way to work in this environment and send you a custom FlytOS build.


#10

Thanks a million for the reply and assistance. I will post the results a bit later today.


#11

Okay well I am currently running my tegra-ubuntu 16.04 environment (not android) and here is the output:

ubuntu@tegra-ubuntu:~$ lsblk --nodeps -o name,serial
NAME SERIAL
sda 20CG01080040
mmcblk0rpmb
mmcblk0boot0
mmcblk0boot1
mmcblk0
ubuntu@tegra-ubuntu:~

/sys/block/mmcblk0/device/cid
1101003031364733300027376597a200

I will flash android 7.0 later today and post the same comand output from the ubuntu chroot same exact image as the above ubuntu 16.04 just in a chroot and on partition /dev/block/sda1


#12

Yeah, the command is known to work fine with Nvidia and other such supported boards.
Unfortunately, Android chroot have never been tested before.

Thanks for the patience.


#13

Sorry for the late reply I am flashing my android build now and i will post back results in a few min…


#14

Basically same output in android chroot with root permissions:

root@localhost:/# lsblk --nodeps -o name,serial
NAME SERIAL
sda
mmcblk0rpmb
mmcblk0
root@localhost:/# cat /sys/block/mmcblk0/device/cid
1101003031364733300027376597a200
root@localhost:/#


#15

Ive been thinking maybe this has to do with not being associated with the correct unix groups ie net video adm etc etc. Looking into that now…


#16

Can you please post output of this command:

findmnt -n -o SOURCE --target /flyt