Kikat - Wasser Firmware for Beelink R89

[FunThomas]

remove apps from homescreen

Hi,

could someone please tell me how to remove apps from the homescreen ?
I tried to with my connected wireless mouse and clicked longer but normally i know there is an X in the upper window to move the icon there and then its removed from homescreen. but here i cant delete it.

moving the selection to the app-icon and clicking "del" on keyboard does also not work

Its bad if flashify is on homescreen and my kids will flash my box

best regards,
Thomas

[Gormar]

@FunThomas. It's a shame but Luncher3 doesn't display "X" and other symbols when you drag application shortcuts. But they are where they suppose to be: in the middle of screen just bellow system notification bar. When you drag app icon there and hit that point that will change its color to red.

[bloodgnome]

NEW - Wasser Firmware V2.0.3 for Beelink R89/Tronsmart R28

Hi,

could someone please tell me how to remove apps from the homescreen ?
I tried to with my connected wireless mouse and clicked longer but normally i know there is an X in the upper window to move the icon there and then its removed from homescreen. but here i cant delete it.

moving the selection to the app-icon and clicking "del" on keyboard does also not work

Its bad if flashify is on homescreen and my kids will flash my box

best regards,
Thomas

just use a different launcher. Like google now or nova launcher...

Sent from my THL 5000

[Hui91]

blue-green screen issue: Who has Phillips TV?

Yes it goes back to normal for a while, then happens again. I tried with 2 HDMI-HDMI cables.

Wasser,

I have checked it with 2 other TVs, it happened only on the Philips which is identical to mine. Is there anyway to find out the issue? Maybe HDMI-CEC? or some other changes since 110k4? Please help me, I really like your ROM's wifi update, it improves wifi from 36-40 to 50-52 Mbits.

Many thanks man, and happy Xmas!

UPDATE: tested on 3 TV, 2 cables: 2 phillips TV had the issue. After a bit research I came upon "HDMI handshake problem" is that fixable in the firmware please?

[wolfheart79]

Hi,

could someone please tell me how to remove apps from the homescreen ?
I tried to with my connected wireless mouse and clicked longer but normally i know there is an X in the upper window to move the icon there and then its removed from homescreen. but here i cant delete it.

moving the selection to the app-icon and clicking "del" on keyboard does also not work

Its bad if flashify is on homescreen and my kids will flash my box

best regards,
Thomas

Try to activate google search in desktop settings and the remove button function like normal .I don't now why have this connection , but work the remove

[FunThomas]

Hi,
is it possible to enable developer menu in this nice rom ?

is it possible to change the launcher and enable widgets ?

best regards,
Thomas

[Gilgamesh]

NEW - Wasser Firmware V2.0.3 for Beelink R89/Tronsmart R28

Hi,
is it possible to enable developer menu in this nice rom ?

is it possible to change the launcher and enable widgets ?

best regards,
Thomas

yes of course, it's the same with the phone you have to click a few times on the build number I think to enable developer menu...

Tapatalked from my GALAXY S5

[vanzylst]

Thanks Gormar, I think you found the problem

I've got the R28 Meta and the micro stutters were starting to get annoying...

I did a few tests with SPMC:
- In one terminal I did:
tail -f /mnt/internal_sd/Android/data/com.semperpax.spmc/files/.xbmc/temp/xbmc.log
- In another terminal I did:
while sleep 1; do date; top -b|head; done

Almost every single time SPMC dropped or skipped frames, there was a kworker process jumping to about 20% CPU. It looks like this causes everything else to stop for that moment.

To work around the issue I did the following:
a. Disabled the ex4 journal on all the filesystems where I could: tune2fs -O ^has_journal /dev/block/mmcblk0p8 (same for 10, 11, and 12). Unfortunately, I can only do this for the partitions where /system and /metadata is mounted and not for /cache and /userdata. For the others I get the following:
# tune2fs -O ^has_journal /dev/block/platform/ff0f0000.rksdmmc/by-name/cache
tune2fs 1.41.14 (22-Dec-2010)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
# e2fsck /dev/block/platform/ff0f0000.rksdmmc/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/platform/ff0f0000.rksdmmc/by-name/cache
Filesystem mounted or opened exclusively by another program?

b. I did mount -o remount,commit=3600,data=writeback,noatime,nodirat ime on all the ext4 filesystems as well. Note that data=writeback doesn't take effect with the remount option, so it should probably be set at boot time.

The result of all this is that I can play ~30Mbps BR rips over SMB with zero frame drops or skips. Previously I would get drops and skips every 1-3 minutes.

PS I'm running the Finless 1.2 ROM, not Wasser, but the same will probably apply in that case.

PPS Maybe someone can build a version of firmware with the journal disabled on all filesystems.

@ICU. Hold your horses for a moment . I've just found something strange. There are writes to disk quite often because jbd2 process is updating EXT4 jurnal and sometime kworker is hiking along repeatedly every 5-6 seconds. These operations doesn't generate too much data because only 4kB (8 sectors) is written for each but if we have 30-40 similar events in one second and factor poor IO performance of this device eMMC then it isn't funny.

<7>[12447.539933] jbd2/mmcblk0p13(128): WRITE block 12891048 on mmcblk0p13 (8 sectors)
<7>[12447.539943] jbd2/mmcblk0p13(128): WRITE block 12891056 on mmcblk0p13 (8 sectors)<7>[12447.539950] jbd2/mmcblk0p13(128): WRITE block 12891064 on mmcblk0p13 (8 sectors)
<7>[12447.539956] jbd2/mmcblk0p13(128): WRITE block 12891072 on mmcblk0p13 (8 sectors)
<7>[12447.539962] jbd2/mmcblk0p13(128): WRITE block 12891080 on mmcblk0p13 (8 sectors)
<7>[12447.539968] jbd2/mmcblk0p13(128): WRITE block 12891088 on mmcblk0p13 (8 sectors)
<7>[12447.539974] jbd2/mmcblk0p13(128): WRITE block 12891096 on mmcblk0p13 (8 sectors)
<7>[12447.539980] jbd2/mmcblk0p13(128): WRITE block 12891104 on mmcblk0p13 (8 sectors)
<7>[12447.541830] jbd2/mmcblk0p13(128): WRITE block 12891112 on mmcblk0p13 (8 sectors)
<7>[12447.557419] Thread-98(13661): WRITE block 14509552 on mmcblk0p13 (8 sectors)
<7>[12447.558230] Thread-98(13661): WRITE block 14509560 on mmcblk0p13 (8 sectors)
<7>[12447.558245] Thread-98(13661): WRITE block 525280 on mmcblk0p13 (8 sectors)
<7>[12447.558257] Thread-98(13661): WRITE block 525296 on mmcblk0p13 (8 sectors)
<7>[12447.560543] Thread-98(13661): WRITE block 14509552 on mmcblk0p13 (8 sectors)
<7>[12447.670099] kworker/u8:1(12837): WRITE block 12583000 on mmcblk0p13 (8 sectors)
<7>[12447.670119] kworker/u8:1(12837): WRITE block 12583040 on mmcblk0p13 (8 sectors)
<7>[12447.670129] kworker/u8:1(12837): WRITE block 12583576 on mmcblk0p13 (8 sectors)
<7>[12447.670139] kworker/u8:1(12837): WRITE block 12583592 on mmcblk0p13 (8 sectors)
<7>[12447.670150] kworker/u8:1(12837): WRITE block 12583760 on mmcblk0p13 (8 sectors)
<7>[12447.670165] kworker/u8:1(12837): WRITE block 12583880 on mmcblk0p13 (8 sectors)
<7>[12447.670174] kworker/u8:1(12837): WRITE block 12649248 on mmcblk0p13 (8 sectors)
<7>[12447.670183] kworker/u8:1(12837): WRITE block 20971528 on mmcblk0p13 (8 sectors)
<7>[12447.670192] kworker/u8:1(12837): WRITE block 20971576 on mmcblk0p13 (8 sectors)
<7>[12447.670202] kworker/u8:1(12837): WRITE block 20971648 on mmcblk0p13 (8 sectors)
<7>[12447.670212] kworker/u8:1(12837): WRITE block 20971872 on mmcblk0p13 (8 sectors)
<7>[12447.670221] kworker/u8:1(12837): WRITE block 20971896 on mmcblk0p13 (8 sectors)
<7>[12447.670231] kworker/u8:1(12837): WRITE block 20972144 on mmcblk0p13 (8 sectors)
<7>[12447.670244] kworker/u8:1(12837): WRITE block 21038240 on mmcblk0p13 (8 sectors)
<7>[12447.670253] kworker/u8:1(12837): WRITE block 21038248 on mmcblk0p13 (8 sectors)
<7>[12447.670262] kworker/u8:1(12837): WRITE block 21038296 on mmcblk0p13 (8 sectors)
<7>[12447.670280] kworker/u8:1(12837): WRITE block 0 on mmcblk0p13 (8 sectors)
<7>[12447.670289] kworker/u8:1(12837): WRITE block 8 on mmcblk0p13 (8 sectors)
<7>[12447.670297] kworker/u8:1(12837): WRITE block 8388736 on mmcblk0p13 (8 sectors)
<7>[12447.670325] kworker/u8:1(12837): WRITE block 8388752 on mmcblk0p13 (8 sectors)
<7>[12447.670336] kworker/u8:1(12837): WRITE block 8388960 on mmcblk0p13 (8 sectors)
<7>[12447.670346] kworker/u8:1(12837): WRITE block 8389600 on mmcblk0p13 (8 sectors)
<7>[12447.670356] kworker/u8:1(12837): WRITE block 8391976 on mmcblk0p13 (8 sectors)
<7>[12447.670365] kworker/u8:1(12837): WRITE block 8399648 on mmcblk0p13 (8 sectors)
<7>[12447.670374] kworker/u8:1(12837): WRITE block 8399656 on mmcblk0p13 (8 sectors)
<7>[12447.670382] kworker/u8:1(12837): WRITE block 8455024 on mmcblk0p13 (8 sectors)
<7>[12447.670391] kworker/u8:1(12837): WRITE block 8456672 on mmcblk0p13 (8 sectors)
<7>[12447.670402] kworker/u8:1(12837): WRITE block 12582936 on mmcblk0p13 (8 sectors)
<7>[12448.654973] kworker/u8:3(13334): WRITE block 22871632 on mmcblk0p13 (72 sectors)

To log these operation in debug messages (dmesg) you should enable debug in VM for block_dumps, like that:
echo "1" > /proc/sys/vm/block_dump
Disable:
echo "0" > /proc/sys/vm/block_dump

Tomorow I will check if my old BOX have similar behavior. Maybe this device is salvageable

[Gormar]

Vote against EXT4 journaling .

Vanzylst,
Thanks for that raport. I wasn't able to disable EXT4 journaling on working partitions but I think that feature isn't necessary on these device especialy because they are quite stable. I can't remember right now any spontanous reboot besides the one when I set DDR OC to 696MHz @ 1,3V and system rebooted while playing Shadowrun: Returns. And in case of data corruption we can always flash system a new .

[gffmac]

We need a nice little script to set all this on bootup.

[gaetanolip]

NEW - Wasser Firmware V2.0.3 for Beelink R89

Maybe http://forum.xda-developers.com/show...9#post17330919

Sent from my LG-D802 using Forum Fiend v1.2.14.

[Gormar]

Maybe http://forum.xda-developers.com/show...9#post17330919

Thx for this find. But these files need some modification especially in regard to partition names.

[crazymark]

Sorry....

I've UBOX 2gb/8Gb and i want to try wasser 2.0.3 firmware. I've read works on my media center, right?
Now i've finless 1.2 but using lan and XBMC modified for RK3288, my video go jerky. Using stock player the videos work little good than XBMC but i've jerky too.

For this problem I want try wasser 2.0.3 firmware.
For install i'can use Factory Tool procedure like point 3 of this thread?

http://www.freaktab.com/showthread.p...-Tools-release

Thanks at all, expecially at wasser!!

[wasser]

Thanks Gormar, I think you found the problem

I've got the R28 Meta and the micro stutters were starting to get annoying...

I did a few tests with SPMC:
- In one terminal I did:
tail -f /mnt/internal_sd/Android/data/com.semperpax.spmc/files/.xbmc/temp/xbmc.log
- In another terminal I did:
while sleep 1; do date; top -b|head; done

Almost every single time SPMC dropped or skipped frames, there was a kworker process jumping to about 20% CPU. It looks like this causes everything else to stop for that moment.

To work around the issue I did the following:
a. Disabled the ex4 journal on all the filesystems where I could: tune2fs -O ^has_journal /dev/block/mmcblk0p8 (same for 10, 11, and 12). Unfortunately, I can only do this for the partitions where /system and /metadata is mounted and not for /cache and /userdata. For the others I get the following:
# tune2fs -O ^has_journal /dev/block/platform/ff0f0000.rksdmmc/by-name/cache
tune2fs 1.41.14 (22-Dec-2010)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
# e2fsck /dev/block/platform/ff0f0000.rksdmmc/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/platform/ff0f0000.rksdmmc/by-name/cache
Filesystem mounted or opened exclusively by another program?

b. I did mount -o remount,commit=3600,data=writeback,noatime,nodirat ime on all the ext4 filesystems as well. Note that data=writeback doesn't take effect with the remount option, so it should probably be set at boot time.

The result of all this is that I can play ~30Mbps BR rips over SMB with zero frame drops or skips. Previously I would get drops and skips every 1-3 minutes.

PS I'm running the Finless 1.2 ROM, not Wasser, but the same will probably apply in that case.

PPS Maybe someone can build a version of firmware with the journal disabled on all filesystems.

can someone please confirm "disable journal" fixes micro stutters?
i can add this fix in next firmware release if it really fixes micro stutters

Wasser

[gffmac]

Re: NEW - Wasser Firmware V2.0.3 for Beelink R89/Tronsmart R28

can someone please confirm "disable journal" fixes micro stutters?
i can add this fix in next firmware release if it really fixes micro stutters

Wasser

I would love to test this out, is there a zip you can prepare that I can flash from recovery to disable journaling?

Sent from my One using Tapatalk