TECLAST T98 32GB new scatter file (user space and system enlargment)

[tonas]

Installed apps / widgets / launcher and settings..so far really enjoying the T98.
In performance commparison with my mi3 it feels on par / a bit slower on occasions..which is still quite fast.

Can't exchange my sim (micro sim in tab, normal in phone), so i haven't restored the backup.
Imei nr is same as it was before flashing.

Have one issue so far. Which seems to be caused by google launcher.
Really like the launcher, but with it, once in a while, i get a 'blurry screen' (random occasions, short interval)
There are horizontal lines all across the screen. Can't make out a single letter.
No reaction from touch. Have to hard- power off.
Changed it back to default, and so far haven't encountered it with the tui launcher.

Is this a known bug? Can't you use a different launcher then tui?

I top have thé random horizontal mines.
I have press the power button till it s power off.
I use the stock firmware.

[hocuspocus69]

If you are in Stock seem to be a faulty unit maybe underclocking gpu you can stabilize look at cube t9 forum seem the same

[hocuspocus69]

If you can publish some photo so i can look at it...no know bug at this time on teclast t98

[SlickRickNL]

Since yesterday it hasn't occured. If it does i post some pictures.

@tonas: how often does it happen to you?
Do you have the tablet a while?

If it is a faulty unit, will consider to send it back.

[hocuspocus69]

for instability random line...
if you are rooted you can try with root explorer to copy script in system\etc\init.d with permission 755 rwxr-xr-x
this is the script

https://drive.google.com/file/d/0B0Lfglunx7nsdVhETTdhUVVqbzA/view?usp=sharing

it downclock your tablet
all honour to devilz-wolit

[tonas]

It happens randomly once a day and not necessarily on heavy usage.

[hocuspocus69]

Photos to see similarity with t9!!!

[SlickRickNL]

Can confirm it happens randomly.

This morning it occured again.
Shortly after the first hard reboot, it happened a second time
See photo's.

Don't know if it resembles the t9 problem.
Downclock sounds legit, am now at work, will try it this evening, report back with results! Thanks.

[SlickRickNL]

Copied the file into the specified path and changed the permission.

[SlickRickNL]

Shortly after...
It was new that the system rebooted itself.

[devilz-wolit]

Read from here:

http://freaktab.com/forum/mtk-based-devices/mtk-tablets/21334-cube-t9-64bit-octacore-a53-4g-beast/page74

[SlickRickNL]

Thanks devilz!!
Hope the same script will work on T98. I'll try it tonight, report back!

[SlickRickNL]

- Copied the attached script (without .txt extension) to the tab.
- Downloaded ROM Toolbox Lite --> Scripter --> Imported the script --> set it to 'Set at boot'.
- Rebooted tablet.

Added Antutu scores before and after.

[SlickRickNL]

Sadly, still got problems with the deadlines.
First i set the script to boot through ROM Toolbox Lite.
That seem to work, for a couple of days Again got the deadlines.

Then i followed the first method (enable .init d) as described (http://www.theandroidhow.com/2014/06...n-android.html) and put the script in .init d folder.
So now i have both scripts / methods running. This morning again got deadlines.
(side note; seem to occur more often when i disconnect the phone from the charger)

Anyhow, really doubting if the (changed) script is correct. When i run it through ROM Toolbox Lite, it returned: permission denied.
Also got (fairly) the same Antutu scores as before..
Can anyone verify if the script i'm using is wrong / good, and what isn't working?
Thanks in advance..!

[hocuspocus69]

script seem correct some unnecessary lines for your problem but good for responsiveness
you'll try to remove
echo "deadline" > /sys/block/mmcblk0/queue/scheduler
chmod 444 /sys/block/mmcblk0/queue/scheduler
echo "1" > /sys/block/mmcblk0/queue/add_random
chmod 444 /sys/block/mmcblk0/queue/add_random
echo "1" > /sys/block/mmcblk0/queue/iostats
chmod 444 /sys/block/mmcblk0/queue/iostats
echo "0" > /sys/block/mmcblk0/queue/nomerges
chmod 444 /sys/block/mmcblk0/queue/nomerges
echo "0" > /sys/block/mmcblk0/queue/rotational
chmod 444 /sys/block/mmcblk0/queue/rotational
echo "1" > /sys/block/mmcblk0/queue/rq_affinity
chmod 444 /sys/block/mmcblk0/queue/rq_affinity
echo "4" > /sys/block/mmcblk0/queue/iosched/fifo_batch
chmod 444 /sys/block/mmcblk0/queue/iosched/fifo_batch
echo "1" > /sys/block/mmcblk0/queue/iosched/front_merges
chmod 444 /sys/block/mmcblk0/queue/iosched/front_merges
echo "500" > /sys/block/mmcblk0/queue/iosched/read_expire
chmod 444 /sys/block/mmcblk0/queue/iosched/read_expire
echo "3000" > /sys/block/mmcblk0/queue/iosched/write_expire
chmod 444 /sys/block/mmcblk0/queue/iosched/write_expire
echo "3" > /sys/block/mmcblk0/queue/iosched/writes_starved
chmod 444 /sys/block/mmcblk0/queue/iosched/writes_starved
those are only to limit problemsolve

change governor to powersave

echo "powersave" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

test if you have init.d support
root and busybox installed
remember to set permission RWX-RX-RX (755)

if nothing works
i'll think you have a faulty unit
good luck