Cube T9 64bit octacore A53 4G beast.

[fztt]

The question is do they even know about this problem?

According to my aliexpress seller, yes, he reported & even pointed them to this site & argued with them, but again, according to him, they claim mine is the "only case" and asked me to return it to china...

[devilz-wolit]

And 'now sure that changing the CPU governor stabilize the tablet. I wonder what is the default setting of my tablet. I restored my T9 to initial conditions (Stock 1.07 updated to 1.08 and root with TWRP) and verified this setting. With Andromizer Pro 4.3.2 result : interactive with all parameters equal to zero !! These settings depend on the ROM or not?

[fztt]

From rom toolbox pro...

[gixer]

I somehow messed up my wifi probably while opening my tab... I couldn't even get any signal from 20 feet.. Any suggestion would be really appreciated

[devilz-wolit]

From rom toolbox pro...

After two days i have two blocks very close in time.
I saw (CPU Z and others) that the CPU frequency is higher than 1.69 GHz (1.9 GHz peak). And it is this that makes the block. Would an app that would block this overclock.
Edius and Others has posted this at page 43 for version 1 of CPU and firmware 1.06.
But even the version 2 with firmware 1.04 has same problem.

[fztt]

Yup actually rom toolbox slider has always peak at 1865, ie, 1.9, even if you set maximum freq lower, by tweaking it to spend the least time on higher bands & scale up/down more gracefully, the reboots reduced massively... I had my first reboot yesterday after so long but was using it while charging so could be the heat... Since then still no reboots... I think for now I'll stop tweaking & start enjoying using it... I can tolerate once every few days but not a few times per day.

[devilz-wolit]

Yup actually rom toolbox slider has always peak at 1865, ie, 1.9, even if you set maximum freq lower, by tweaking it to spend the least time on higher bands & scale up/down more gracefully, the reboots reduced massively... I had my first reboot yesterday after so long but was using it while charging so could be the heat... Since then still no reboots... I think for now I'll stop tweaking & start enjoying using it... I can tolerate once every few days but not a few times per day.

I'm trying to use Xposed framework with Performance monitor profile.
This module allows the setting of all cores individually and their variation in a very simple way.


Update:
this solution is not valid.

[fztt]

Thanks for the update, I shall give it a try...

Update on my end - 1st crash after 9 days was when I was using while charging, it was very hot, since then, it's more than 24 hours, still ok...

Update: still up after almost 4 days so will keep using rom toolbox scripter... I hope xposed + performance profile works for you... I think very likely each of our defective units need different freq profiles & you have to keep tweaking until it works for you.

[devilz-wolit]

Update: still up after almost 4 days so will keep using rom toolbox scripter... I hope xposed + performance profile works for you... I think very likely each of our defective units need different freq profiles & you have to keep tweaking until it works for you.

The best solution is the script in init.d
I modified your script by entering all 8 cores CPU, the operating frequencies and the scheduler. As you say it comes to finding the best solution for more stability to the T9 until CUBE also will decide to release an update that fixes this problem. I tried to send the message to Cube also by the seller but so far no response.

[fztt]

The best solution is the script in init.d
I modified your script by entering all 8 cores CPU, the operating frequencies and the scheduler. As you say it comes to finding the best solution for more stability to the T9 until CUBE also will decide to release an update that fixes this problem. I tried to send the message to Cube also by the seller but so far no response.

Do you mind sharing your modified script? Thanks!

I have emailed cube support directly, also no response.

[hammerjoe]

I have reported a few bugs on their fb group page and the reply i get is to go to their download page to download the latest firmware which is 1.07.

[fztt]

That is their standard reply.

[devilz-wolit]

Do you mind sharing your modified script? Thanks!

I have emailed cube support directly, also no response.

in use: actual 2 days with no block

#!/system/bin/sh
echo "noop" > /sys/block/mmcblk0/queue/scheduler
chmod 444 /sys/block/mmcblk0/queue/scheduler

echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu5/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu5/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu6/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu6/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu7/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu7/cpufreq/scaling_governor

echo "20000 702000:60000 1170000:80000 1560000:120000" > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
echo "0" > /sys/devices/system/cpu/cpufreq/interactive/boost
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/boost
echo "60000" > /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration
echo "99" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo "14170000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo "60000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo "90 468000:40 702000:60 1417000:80" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo "60000 " > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/timer_rate
echo "80000" > /sys/devices/system/cpu/cpufreq/interactive/timer_slack
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/timer_slack

Next test

#!/system/bin/sh
echo "cfq" > /sys/block/mmcblk0/queue/scheduler
chmod 444 /sys/block/mmcblk0/queue/scheduler

echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu5/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu5/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu6/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu6/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu7/cpufreq/scaling_governor
chmod 444 /sys/devices/system/cpu/cpu7/cpufreq/scaling_governor

echo "20000 702000:60000 1170000:80000 1560000:120000" > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
echo "0" > /sys/devices/system/cpu/cpufreq/interactive/boost
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/boost
echo "60000" > /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration
echo "99" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo "14170000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo "60000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo "90 468000:40 702000:60 1417000:80" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo "60000 " > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/timer_rate
echo "80000" > /sys/devices/system/cpu/cpufreq/interactive/timer_slack
chmod 444 /sys/devices/system/cpu/cpufreq/interactive/timer_slack

For T9 the best scheduler should be "cfq"
My question is:
echo "20000 702000:60000 1170000:80000 1560000:120000"
o
echo "20000 702000:120000 1170000:80000 1560000:60000" ??

[devilz-wolit]

I have reported a few bugs on their fb group page and the reply i get is to go to their download page to download the latest firmware which is 1.07.

Technical assistance of Cube does not exist. They never say that there is a 1.8 OTA.
We have to get away alone

[fztt]

I think to prevent spikes to 1.9ghz, we need to set cpuinfo_max_freq, but so far I googled extensively & can't find anyone make successful attempt to make it stick in any device/rom.