T-R42 - wasser firmware - JB Android 4.2.2

[Herzie]

Herzie,

Short Answer No ...

I use the Home button on my USB air mouse/keyboard or On My Remote that came with the unit ..

Look into Keyboard Layouts and make sure Your Home key is set to go home ...

Mine works Fine ...

Michael T.

Problem is tha I got sick and tired of the melee airmouse so I switched to a regular USB mouse, so now I don't have a home button Well guess that's just part of the "fun"

[wasser]

Hello wasser,
THANK YOU SO MUCH !!! The lapdock works fine now with 1366x768 resolution.
Could you please patch it for the K-R72, too.

I've done some gpio dumps for you, in case you havn't enough.
(Its the whole dmesg output)


Is there anything else I can do to support you ?


Greetings from Saarland,
Gerry

Hi Gerry,

i uploaded some oc kernels for t-r42 and k-r42. The kernel has other fix for 1366x768. Could you please check if it still works for you?

thanks

[limecat]

Hi Wasser

I flashed the 1704 ddr720 kernel and the 'power button causes reboot' seems to be solved. At least, have not experienced it anymore.

Antutu stability test very constant at around 70 to 73. Antutu benchmark 17'745

I also get the overlay setting now in build.prop! It really is 1080p regardless of setting it to 1 or 0. The only difference is that in one case the software is fooled into thinking that it's running at 720p!!

Great job!

LC

[Kruikenzeiker]

Issues

Hi,

I updated my T-R42 with the wasser firmware version 1.2.3 but I have the following issues:

- The RKRemoteControl app on my Android Smartphone cannot find the T-R42 anymore. This was working with the stock firmware.
- When starting a 720P movie in XBMC, the screen is stuttering (this was also a problem when using stock firmware). Also when I play the same movie outside XBMC with DicePlayer it also stutters (this wasn't a problem with the stock firmware)
- In the opening post of this thread I see a list of kernels. What is the difference between all, and which one do I need to use.

Can anybody help me with these issue. Thanks!

[limecat]

Hi,

I updated my T-R42 with the wasser firmware version 1.2.3 but I have the following issues:

- The RKRemoteControl app on my Android Smartphone cannot find the T-R42 anymore. This was working with the stock firmware.
- When starting a 720P movie in XBMC, the screen is stuttering (this was also a problem when using stock firmware). Also when I play the same movie outside XBMC with DicePlayer it also stutters (this wasn't a problem with the stock firmware)
- In the opening post of this thread I see a list of kernels. What is the difference between all, and which one do I need to use.

Can anybody help me with these issue. Thanks!

You need an app installed called ehomemediacenter in order for RKRemote to work. It's on the stock firmware, but not on Wasser's custom firmware. I think you can find it on Aptoide. Once you have it installed and working then use Titanium backup to store it so you can easily reinstall it next time you are flashing.

I take it all your 720p movies stutter? Perhaps check your sound output in Android settings. Also try playing with MX player with the custom h/w+ enabled. I have had a few downloaded movies that did not play in XBMC, but perfectly in MX.

The kernels at the top are all overclocked with different CPU and memory timings. No need to use any of those, but if you do you may experience an unexpected crash on the higher ones. The RK3188 chip is normally running at 1.6GHz and overclocking it will push it higher, and might overheat it! So be careful.

[wapvirus]

Hi can someone test this please add the following line to your build prop

media.stagefright.enable-player=1

This fixes the Video play back in JustXBMC using default player rather than external MX ect..
Now plays full 1080p videos no stutter for me

Instructions
1: Install a Build Prop editor from play-store Build Prop Editor
2: Back-up your existing build.prop
3: Add the line above to your build prop
4: Reboot and now your video play back should be smooth in 1080p/720p videos using xbmc default player

[michael2t]

Hello Wapvirus,

Repost:

>
>media.stagefright.enable-player=1
>media.stagefright.enable-http=1
>
>this will enable stagefright as default OS media handler as a player and for http requests.

This will help the browser and the Video player ....

Thanks for The Post Wapvirus ...

Michael T.

[darkavengerpl]

Wasser i have a question for you.
In your standard rom, processor is set to 1,6 Ghz or different ?!?
Some people set processor down (under clock) to achieve low temperatures.
How it is with your roms ?

P.S. Sorry for my weak English.

[genom]

Yeah, overclocking!
Thumbs up
Dankeschön B-)

Edit : thumbs down
1704 kernel @1.4 max
1800 kernel makes min max only 1,2ghz?!?
please help

[wasser]

Yeah, overclocking!
Thumbs up
Dankeschön B-)

Edit : thumbs down
1704 kernel @1.4 max
1800 kernel makes min max only 1,2ghz?!?
please help

the fre depends on the cpu load, if you want your box running with max freq just do:

echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

[darkavengerpl]

But with the permament oc cpu you will fried up your tv box...

[wapvirus]

But with the permament oc cpu you will fried up your tv box...

Yes i agree you would need to replace the heatsink and use a cooling fan

[klibido]

Hi, I've tried out the newest firmware (several reinstalls) and had some problems with the latest one 1.2.3. I checked everthing with 1.2.0 too and none but the first of the problems occured. No OC kernels used.

1. USB devices do not show up in the settings' storage tab. I can access them via the File Explorer or MX Player, but not through the android GUI.

2. CWM doesn't seem to work by default, the standard recover did show up every time. I had to setup it on my own.

3. AV out does not work on my very old tv (röhre), green images full of artefacts.

4. The screen often gets black for the blink of an eye.

5. Sometimes the power button does not respond properly.

I hope this feedback helps, keep up the good work. Guess I'll stick to 1.2.0.

[Herzie]

Hi, I've tried out the newest firmware (several reinstalls) and had some problems with the latest one 1.2.3. I checked everthing with 1.2.0 too and none but the first of the problems occured. No OC kernels used.

1. USB devices do not show up in the settings' storage tab. I can access them via the File Explorer or MX Player, but not through the android GUI.

2. CWM doesn't seem to work by default, the standard recover did show up every time. I had to setup it on my own.

3. AV out does not work on my very old tv (röhre), green images full of artefacts.

4. The screen often gets black for the blink of an eye.

5. Sometimes the power button does not respond properly.

I hope this feedback helps, keep up the good work. Guess I'll stick to 1.2.0.

I get no. 4 quite often. It's completely blank for about a second.

[wapvirus]

Hi, I've tried out the newest firmware (several reinstalls) and had some problems with the latest one 1.2.3. I checked everthing with 1.2.0 too and none but the first of the problems occured. No OC kernels used.

1. USB devices do not show up in the settings' storage tab. I can access them via the File Explorer or MX Player, but not through the android GUI.

2. CWM doesn't seem to work by default, the standard recover did show up every time. I had to setup it on my own.

3. AV out does not work on my very old tv (röhre), green images full of artefacts.

4. The screen often gets black for the blink of an eye.

5. Sometimes the power button does not respond properly.

I hope this feedback helps, keep up the good work. Guess I'll stick to 1.2.0.

clockwork recover was not included as it not working wasser is trying to fix it as for av out did you set up correctly mine works you need to set up pal/nstc depending on your country and tv
screen going blank i have not noticed but i am getting audio cut out through hdmi also power button is trying to be fixed apart from that it's a rock solid build for me