On device status screen shows static value for Cloud Account ID #81

Open
opened 2026-02-20 08:20:07 -05:00 by deekerman · 6 comments
Owner

Originally created by @jjeising on GitHub (Jan 28, 2025).

Originally assigned to: @ym on GitHub.

The on device status screen shows the Device ID and a Cloud Account ID. The device is not connected to the cloud and was never connected to the cloud. The cloud token in the config is empty.

I cannot find related code, in display.go only the Device ID seems to be set:

github.com/jetkvm/kvm@8ffe66a1bc/display.go (L83)

Other code related to the display seems to be not released as open source yet. Is this a left over default value or some other internal id?

Originally created by @jjeising on GitHub (Jan 28, 2025). Originally assigned to: @ym on GitHub. The on device status screen shows the Device ID and a _Cloud Account ID_. The device is not connected to the cloud and was never connected to the cloud. The cloud token in the config is empty. I cannot find related code, in `display.go` only the Device ID seems to be set: https://github.com/jetkvm/kvm/blob/8ffe66a1bc63b38c3eea44ec3f10c75ba00836c1/display.go#L83 Other code related to the display seems to be not released as open source yet. Is this a left over default value or some other internal id?
Author
Owner

@Nevexo commented on GitHub (Jan 28, 2025):

GetDeviceID() is defined in hw.go:

github.com/jetkvm/kvm@8ffe66a1bc/hw.go (L41)

The device ID is the serial number of the Rockchip application processor, so that's why you're seeing a value even if it hasn't registered with the cloud.

Other code related to the display seems to be not released as open source yet.

Yeah, the display is managed by jetkvm_native, which hasn't been opened sourced yet. Should be soon.

@Nevexo commented on GitHub (Jan 28, 2025): `GetDeviceID()` is defined in hw.go: https://github.com/jetkvm/kvm/blob/8ffe66a1bc63b38c3eea44ec3f10c75ba00836c1/hw.go#L41 The device ID is the serial number of the Rockchip application processor, so that's why you're seeing a value even if it hasn't registered with the cloud. > Other code related to the display seems to be not released as open source yet. Yeah, the display is managed by jetkvm_native, which hasn't been opened sourced yet. Should be soon.
Author
Owner

@jjeising commented on GitHub (Jan 28, 2025):

The device ID is the serial number of the Rockchip application processor, so that's why you're seeing a value even if it hasn't registered with the cloud.

I understand the device ID, it's the same that is used in the update and cloud register calls.

But the status screen shows two values:

Device ID
[…]

Cloud Account ID
12…dd
@jjeising commented on GitHub (Jan 28, 2025): > The device ID is the serial number of the Rockchip application processor, so that's why you're seeing a value even if it hasn't registered with the cloud. I understand the device ID, it's the same that is used in the update and cloud register calls. But the status screen shows two values: ``` Device ID […] Cloud Account ID 12…dd ```
Author
Owner

@Nevexo commented on GitHub (Jan 28, 2025):

Cloud Account ID
12…dd

Is it 12387612876312673dd?

Because if it is, then I guess it's just a default string

# strings jetkvm_native | grep 123
[...]
12387612876312673dd
@Nevexo commented on GitHub (Jan 28, 2025): > Cloud Account ID > 12…dd Is it `12387612876312673dd`? Because if it is, then I guess it's just a default string ``` # strings jetkvm_native | grep 123 [...] 12387612876312673dd ```
Author
Owner

@jjeising commented on GitHub (Jan 28, 2025):

Yes it is. Looks like it also has a descriptor ui_Status_Content_Cloud_Account_Id_Content_Label, but it is not set anywhere.

@jjeising commented on GitHub (Jan 28, 2025): Yes it is. Looks like it also has a descriptor `ui_Status_Content_Cloud_Account_Id_Content_Label`, but it is not set anywhere.
Author
Owner

@kashalls commented on GitHub (Jan 29, 2025):

Haha. That's funny to see. Hopefully by the time that code gets open sourced we can fix that.

@kashalls commented on GitHub (Jan 29, 2025): Haha. That's funny to see. Hopefully by the time that code gets open sourced we can fix that.
Author
Owner

@ym commented on GitHub (Jul 15, 2025):

We're aware of this issue and it will be fixed in the next major release.

@ym commented on GitHub (Jul 15, 2025): We're aware of this issue and it will be fixed in the next major release.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/kvm#81
No description provided.