Languages

Menu
Sites
Language
Programmatically profile resource usage on TV?

Hi,

is anybody aware of a programmatic way to capture memory and CPU usage values of an app running on a TV?

I've worked with Tizen Studio and the Tizen SDK CLI for a long time but:

1. The Dynamic Analyzer tool that comes with Tizen Studio still seem to support only mobile and wearable devices, not TVs.
2. I couldn't find any SDB command to read those values from a device. Trying to run `sbd shell` with any command return a `closed` error message as the shell capability is disabled on the device.
3. I'm aware that Samsung TVs expose web APIs at `http://{deviceIp}:8001/api/v2/` but no official/full documentation of these APIs seems to exist online.

The application we're trying to analyze is a JavaScript application.

Thanks for any help,

-Diego

List

Responses

5 Replies
Gerald Boyle

It sounds like you're dealing with a situation where the sdb (Samsung Debug Bridge) shell is not available or has been disabled on your device. This can limit your ability to directly interact with the device’s filesystem or retrieve specific values using sdb commands. Here are a few potential workarounds:

  1. Verify Device Connection: Ensure that your device is properly connected and recognized by sdb. Use: sdb devices
  2. Check for Alternative Commands: Even if the shell is closed, other sdb commands might still be functional to confirm that the device is listed.
  3. Use ADB Commands: If the sdb shell is disabled but the device supports adb (Android Debug Bridge), you might be able to use adb commands. 
  4. Check Device Settings: Sometimes shell access is disabled due to security policies or settings on the device. Check if there are any developer options or security settings that might be affecting this.
  5. Use Device-Specific Tools: Some devices come with manufacturer-specific tools or interfaces for debugging and retrieving information. Check if there are any available for your device that might offer the functionality you're looking for.
  6. Consult Documentation or Support: If none of the above options work, referring to the device's documentation or reaching out to the manufacturer’s support might provide additional insights or alternatives.