Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2020/06/project-cpu-stats-v11.html
#project #CPUStats
DESCRIPTION
This project will give you the possibility to see the usage (%) of your CPU in real time, depending on the workload on each state.
Main features:
• Real-time usage
• Total CPU usage
• Per-core CPU usage
• Statusbar (text) or Overlay display.
The project is in an experimental state, so expect failures, or errors in the final calculations.
As I don't have a x86 device, the project will work but will propably not report correct values for CPU usage (regardless of the formula applied, containing errors or not), as the internal Kernel clock is measured in a different clock rate.
Notes:
- To use statusbar info style, AutoNotification will be required.
- Tasker is not the best way to monitor the CPU usage, as it runs on the main thread. So, use it at your own risk.
- Before setting up the project ('Setup' task) to allow it to show per-core usage, check if your device has a multi-core CPU. Otherwise, the project will fail to start.
CREDITS
@SmartPhoneLover
CHANGELOG
- New: Ability to get multicore usage for compatible devices. (scene and notification)
- Other: Unchecked root usage for Shell Code action that gets the CPU info from '/proc/stat' file, as it was not necessary. (The project works on non-rooted devices)
- Other: Changed scene type to 'Overlay', so it won't affect elements behind it.
- Other: Other small changes.
VERSION
v1.1
DESCRIPTION
This project will give you the possibility to see the usage (%) of your CPU in real time, depending on the workload on each state.
Main features:
• Real-time usage
• Total CPU usage
• Per-core CPU usage
• Statusbar (text) or Overlay display.
The project is in an experimental state, so expect failures, or errors in the final calculations.
As I don't have a x86 device, the project will work but will propably not report correct values for CPU usage (regardless of the formula applied, containing errors or not), as the internal Kernel clock is measured in a different clock rate.
Notes:
- To use statusbar info style, AutoNotification will be required.
- Tasker is not the best way to monitor the CPU usage, as it runs on the main thread. So, use it at your own risk.
- Before setting up the project ('Setup' task) to allow it to show per-core usage, check if your device has a multi-core CPU. Otherwise, the project will fail to start.
CREDITS
@SmartPhoneLover
CHANGELOG
- New: Ability to get multicore usage for compatible devices. (scene and notification)
- Other: Unchecked root usage for Shell Code action that gets the CPU info from '/proc/stat' file, as it was not necessary. (The project works on non-rooted devices)
- Other: Changed scene type to 'Overlay', so it won't affect elements behind it.
- Other: Other small changes.
VERSION
v1.1
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2020/06/project-vip-terminal-log-v10.html
#project #vip #TerminalLog
DESCRIPTION
This project aims to emulate the basic operation of apps like: Terminal or Termux, at least in the majority of commands and taking into account Tasker's own limitations, showing a command log report of its execution on the screen (stdout and stderr).
Notes:
- Avoid running cmds like 'logcat' (without params) or any cmd that runs indefinitely, because the project will probably get stuck. The Shell Code action is not adjusted to accept extra commands once it has been executed, by now.
- Some errors could be shown as normal STDOUT outputs, as they are not registered as 'Errors' actually. This is not a Tasker issue.
CREDITS
@SmartPhoneLover
VERSION
v1.0
DESCRIPTION
This project aims to emulate the basic operation of apps like: Terminal or Termux, at least in the majority of commands and taking into account Tasker's own limitations, showing a command log report of its execution on the screen (stdout and stderr).
Notes:
- Avoid running cmds like 'logcat' (without params) or any cmd that runs indefinitely, because the project will probably get stuck. The Shell Code action is not adjusted to accept extra commands once it has been executed, by now.
- Some errors could be shown as normal STDOUT outputs, as they are not registered as 'Errors' actually. This is not a Tasker issue.
CREDITS
@SmartPhoneLover
VERSION
v1.0
Tasker | ADVANCED (channel)
https://taskerprofilecenter.blogspot.com/2020/06/project-vip-terminal-log-v11.html
#project #vip #TerminalLog
DESCRIPTION
This project aims to emulate the basic operation of apps like: Terminal or Termux, at least in the majority of commands and taking into account Tasker's own limitations, showing a command log report of its execution on the screen (stdout and stderr).
Notes:
- Avoid running cmds like 'logcat' (without params) or any cmd that runs indefinitely, because the project will probably get stuck. The Shell Code action is not adjusted to accept extra commands once it has been executed, by now.
- Some errors could be shown as normal STDOUT outputs, as they are not registered as 'Errors' actually. This is not a Tasker issue.
CREDITS
@SmartPhoneLover
CHANGELOG
- New: Added '$' and '#' symbols for commands executed as user or root-user, respectively.
VERSION
v1.1
DESCRIPTION
This project aims to emulate the basic operation of apps like: Terminal or Termux, at least in the majority of commands and taking into account Tasker's own limitations, showing a command log report of its execution on the screen (stdout and stderr).
Notes:
- Avoid running cmds like 'logcat' (without params) or any cmd that runs indefinitely, because the project will probably get stuck. The Shell Code action is not adjusted to accept extra commands once it has been executed, by now.
- Some errors could be shown as normal STDOUT outputs, as they are not registered as 'Errors' actually. This is not a Tasker issue.
CREDITS
@SmartPhoneLover
CHANGELOG
- New: Added '$' and '#' symbols for commands executed as user or root-user, respectively.
VERSION
v1.1