Kikat - Wasser Firmware for Beelink R89

[manero]

This message is for you Oualid2013

[clarkss12]

[QUOTE=Oualid2013;264975]

Connect the OTC USB to your PC. Open the case and short to pins with tweezers and then plug in the electric. Then click the Firmware button in Android Tool to pick your new firmware. Then click Upgrade
[ATTACH=CONFIG]9540[/ATTACH][ATTACH=CONFIG]9538[/ATTACH][/QUO

With Androidtool 2.3 say

loading firmware failed
ty for help

Your S89H is an Amlogic CPU not RK3288, are you trying to install the wrong firmware?

Edit, that was for Qualid , sorry.

[no_spam_for_me]

Right, 1.0.3 doesn't exist at rk3288... only at s802 (or rk3188)
But now I see Oualid2013 had posted at the correct thread http://www.freaktab.com/showthread.p...l=1#post264726

[ChiefWiggum]

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?

@HUI91, Wasser
I have the same Problems. Also tested different cables and lenghts. With 110k4 stock firmware there is no Problem. But I would have the better optimized Wasser firmware. hope it is possible to fix that. TV is Philips 42" 42PFL7404H/12. Thanks.

[kalrez]

Wasser could you please add the functionality for the Tronsmart R28 remote control back into this firmware build or could someone point me in the right direction on how to do it? I've spent a few hours on Google and can't seem to find the location where remote control files are held in the file system and how to get them loaded.

Same Here I have tried Both Wasser & Finless Roms both kill the Tronsmart R28 stock remote. Have gone back to the FActory stock Firmware with the older Rom for now to get back the Remote function.

Wondering if Tronsmart has dropped support, they have not released a new update. Alex at the Tronmart Forum has disappeared. Guess i should have gotten the Beelink.

[ChiefWiggum]

Yes, that is a bit strange. But I think we're a bit closer now to finding the real problem...

I noticed that I don't actually need to use the USB ethernet adapter, it just needs to plugged in, while I still use the built-in ethernet interface. With this configuration I also don't get any stutters under SPMC.

What I did was the following:
- Disable WiFi and Ethernet under Android settings.
- Have the USB ethernet adapter plugged in to a USB port on your R28.
- Verify that an eth1 device exists for the USB adapter and for the built-in ethernet (/system/xbin/ifconfig -a with busybox). None should have an IP address at this stage.
- Run netcfg eth0 dhcp (or configure the interface manually with /system/xbin/ifconfig and /system/xbin/route from busybox).
- Verify with /system/xbin/ifconfig that an IP address was assigned to eth0 and that eth1 is still without an IP address.
- Proceed to mount your SMB share with cifs (if that's what you're using).
- Check that there is no WiFi or Ethernet connected icon.

The trick here is that the Android framework + applications doesn't see any available connected network, but on the kernel level your network interface is configured and you are connected.

Now apps like Google Play will fail because it doesn't see any network connection. However, if you mounted an SMB share over cifs in one of the previous steps, SPMC will still be able to use that.

At this stage videos should play under SPMC without the stutters (that's my experience at least).

My theory is that there is some process that requires network connectivity that wakes up every few minutes to do something, and this is what's causing the stutters. When it doesn't have network connectivity it doesn't have anything to do and video playback is therefore unaffected (although thinking about it now, it doesn't completely explain why videos from a USB stick also play well with the network on...).

I would appreciate it if something can reproduce this just to confirm what I'm seeing.

I 've tested it. All my video-material (1080p, 720p) is played over a 1GBit Lan and a powerfull GBit NAS, GBit Switch, Cat.6 Patch-Cables.
I set all Adapters down. wlan0 started itself. Went to android settings where ethernet is off and wlan on. I switched all off. Then i used a terminal and put all in you wrote. i set eth0 to dhcp and left all other down.
local net and browser are running. play-store not. no stutters.
after a reboot i checked if it all is still running.
Now all is off, eth0 on, stutters are back.
but play-store is also working. usb-to-ethernet adapter is still in an usb port (backside). i have tested on beelink stock firmware 111k4 and spmc 13.4.0.

I will stay at the solution with the external eth1 activated and an init.d script at boot time...

[vanzylst]

I 've tested it. All my video-material (1080p, 720p) is played over a 1GBit Lan and a powerfull GBit NAS, GBit Switch, Cat.6 Patch-Cables.
I set all Adapters down. wlan0 started itself. Went to android settings where ethernet is off and wlan on. I switched all off. Then i used a terminal and put all in you wrote. i set eth0 to dhcp and left all other down.
local net and browser are running. play-store not. no stutters.
after a reboot i checked if it all is still running.
Now all is off, eth0 on, stutters are back.
but play-store is also working. usb-to-ethernet adapter is still in an usb port (backside). i have tested on beelink stock firmware 111k4 and spmc 13.4.0.

I will stay at the solution with the external eth1 activated and an init.d script at boot time...

Thanks for the confirmation.

What I've got now which works for me without stutters is the following:
1. Ethernet USB adapter plugged in (eth1)
2. WiFi enabled via Android Settings.
3. Ethernet disabled via Android Settings.
4. The following init.d config (configure the builtin ethernet eth0 from the command line using dhcp, make sure eth0 is used to communicate with my media server over SMB since I've got WiFi on as well):
netcfg eth0 dhcp
/system/xbin/route add -host 192.168.0.110 dev eth0
mount -o remount,rw /
mkdir /mnt/cifs
mount -o remount,ro /
su --mount-master -c mount -rw -o username=xxx,password=xxx -t cifs //192.168.0.110/media

With this I've got WiFi for general internet connectivity (working Play Store, etc.), and I use the built-in Ethernet for connecting via SMB to my media server.

The USB ethernet adapter is therefore only used to confuse Android so that it doesn't see that the Ethernet network is actually up when it's configured from the command line (looks like an Android bug to me that it doesn't correctly detect when you have multiple Ethernet adapters...)

Either way, not a proper fix to the micro-stutter problem but it works well as a workaround assuming you've got a spare USB ethernet adapter lying around

[ChiefWiggum]

Thanks for the confirmation.

What I've got now which works for me without stutters is the following:
1. Ethernet USB adapter plugged in (eth1)
2. WiFi enabled via Android Settings.
3. Ethernet disabled via Android Settings.
4. The following init.d config (configure the builtin ethernet eth0 from the command line using dhcp, make sure eth0 is used to communicate with my media server over SMB since I've got WiFi on as well):
netcfg eth0 dhcp
/system/xbin/route add -host 192.168.0.110 dev eth0
mount -o remount,rw /
mkdir /mnt/cifs
mount -o remount,ro /
su --mount-master -c mount -rw -o username=xxx,password=xxx -t cifs //192.168.0.110/media

With this I've got WiFi for general internet connectivity (working Play Store, etc.), and I use the built-in Ethernet for connecting via SMB to my media server.

The USB ethernet adapter is therefore only used to confuse Android so that it doesn't see that the Ethernet network is actually up when it's configured from the command line (looks like an Android bug to me that it doesn't correctly detect when you have multiple Ethernet adapters...)

Either way, not a proper fix to the micro-stutter problem but it works well as a workaround assuming you've got a spare USB ethernet adapter lying around

Your solution combines both worlds, nice.
Is the eth1 up or down in your configuration?

I tried it.
command "route add -host 192.168.0.110 dev eth0" didn't work. terminal said "invalid parameter".
i could "route add default gw [GATEWAY] dev eth0" but this isn't the same.
second problem was, that i think my files were streamed over wlan0. besides stutters now i had buffering problems. i saw this while playing a movie.
how do you get streaming only over dev eth0 and prevent from doing it over interface wlan0? both adapters know the devices in lan 198.168.x.x
and how do you automate the config in init.d to work? i use "init.d scripts support" from ryo software.
i'm searching for erreors. perhaps you can give me some hints.

thanks.

[gffmac]

Your solution combines both worlds, nice.
Is the eth1 up or down in your configuration?

I tried it.
command "route add -host 192.168.0.110 dev eth0" didn't work. terminal said "invalid parameter".
i could "route add default gw [GATEWAY] dev eth0" but this isn't the same.
second problem was, that i think my files were streamed over wlan0. besides stutters now i had buffering problems. i saw this while playing a movie.
how do you get streaming only over dev eth0 and prevent from doing it over interface wlan0? both adapters know the devices in lan 198.168.x.x
and how do you automate the config in init.d to work? i use "init.d scripts support" from ryo software.
i'm searching for erreors. perhaps you can give me some hints.

thanks.

This is what I did to get everything working over eth0:

enable wifi and join network then reboot with ethernet disabled in settings and with usb-ethernet adapter attached but ethernet wire attached to internal socket

on bootup
ensure you have joined your wireless network - ethernet should be disabled

(Make sure busybox is installed from playstore)

then do:
adb shell
su
export PATH=/system/xbin:$PATH
netcfg eth0 dhcp (freeze? ctrl-c and redo Previous commands)
/system/xbin/route add -host 192.168.1.51 dev eth0

now disable wifi in android settings (ethernet should say disabled) and everything works perfect (smb/playstore, stutterfree smb playback etc)

check data transference with = ifconfig -a to make sure streaming is going through eth0



Also: I have the xposed framework 'Fake Wifi Connection' installed with everything set to fake the connection to wifi - update this when installing new apps

I did notice Spotify keeps trying to enable wifi which brings back the stutters, not noticed any other apps do that yet.

[ChiefWiggum]

@gffmac:
command "adb shell" says "device not found"
all other commands were successfull.
solution is not working at the moment, i'm testing...

[gffmac]

@gffmac: ok, thanks i try it.

Eth1 is just attached with no cable in.

[vanzylst]

Your solution combines both worlds, nice.
Is the eth1 up or down in your configuration?

I tried it.
command "route add -host 192.168.0.110 dev eth0" didn't work. terminal said "invalid parameter".
i could "route add default gw [GATEWAY] dev eth0" but this isn't the same.
second problem was, that i think my files were streamed over wlan0. besides stutters now i had buffering problems. i saw this while playing a movie.
how do you get streaming only over dev eth0 and prevent from doing it over interface wlan0? both adapters know the devices in lan 198.168.x.x
and how do you automate the config in init.d to work? i use "init.d scripts support" from ryo software.
i'm searching for erreors. perhaps you can give me some hints.

thanks.

You need busybox installed for the proper route command. Then you can do /system/xbin/route add -host x.x.x.x dev eth0 (or do export PATH=/system/xbin:$PATH and then just run route)

Built-in route doesn't work:
root@manta:/ # /system/bin/route add -host 192.168.0.110 dev eth0
Invalid argument

Busybox route command works:
22|root@manta:/ # /system/xbin/route add -host 192.168.0.110 dev eth0
route: SIOCADDRT: File exists

To automate it, I've got the following script in /etc/init.d
130|root@manta:/ # cat /etc/init.d/setup
#!/system/bin/sh
netcfg eth0 dhcp
/system/xbin/route add -host 192.168.0.110 dev eth0
mount -o remount,rw /
mkdir /mnt/cifs
mount -o remount,ro /
su --mount-master -c mount -rw -o username=xxx,password=xxx -t cifs //192.168.0.110/media /mnt/cifs

root@manta:/ # ls -l /etc/init.d/setup
-rwxrwxrwx 1 0 0 751 Jan 1 20:30 /etc/init.d/setup

I also had to install universal init.d from the Play Store to get it to work for me:

https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=en

[Henkdevries]

I locked the cpu freq at 1800mhz when streaming a hd movie/show -> less stutter (still there a bit)
you can do this with the app "Tasker"

I hope there will be a proper fix soon though...

[reeso3000]

First of all great rom Wasser thanks very much

Just a couple of this:

1) I was wondering if anyone has had an issue with wifi display with this rom - it recognises my lg g3 and states connected but on my phone miracast shows connecting but never changes to connected and the screen is never displayed on the tv (this worked fine with stock)

2)I can't seem to get droidmote server working - it crashes once I press "stop" to change it to "Started" (app opens ok and can change settings etc) was reading it could be down to a uinput.ko file missing - have checked the location and there isn't one present, I am planning on flashing the stock rom and see if I can grab it from there but was wondering if anyone has noticed this and weather that would work?

Thanks

[Hui91]

Log: green screen error on Philips TV

@HUI91, Wasser
I have the same Problems. Also tested different cables and lenghts. With 110k4 stock firmware there is no Problem. But I would have the better optimized Wasser firmware. hope it is possible to fix that. TV is Philips 42" 42PFL7404H/12. Thanks.

Wasser, Mo123
Please if you can have a look at this log: https://www.dropbox.com/s/qeijhnvrke...49-51.txt?dl=0

I couldn't upload it here due to the size. I hope it make sense for your eyes. It happened near the end of the log, in the last 1-2 minutes.

Many thanks for your support!