K-R42 - wasser firmware - JB Android 4.2.2

[riogrande75]

Small problems on EKB311B

Thx for the new FW.
I flashed my brand new EKB311B (was stock fw) with wasser 1.2.5 (new rev. kernel 720).
Unfortunately the color led of the power button remains red now (before it turned blue when device was on), WiFi cannot be activated but i use eth only and the stock IR remote does not get recognized.

Everything else so far is ok and very fast.

Any ideas what could be wrong?

[no_spam_for_me]

EKB311B => I think this means with BlueTooth... if yes, it use another wifi-chip and so on...

[franckleroy]

1. you can change the lcd density, the boot-720p.img lcd density 160 and boot-1080p.img 240.
just flash the correct boot image

2. you cannot reduce it. It's hardcoded in the firmware.

OK

but I am used to set density to 200...

Franck

[no_spam_for_me]

OK

but I am used to set density to 200...

Franck

adb shell
cd /system
ls -al build.prop
-rw-r--r-- root root 3033 xxxxxxxx build.prop


adb pull /system/build.prop build.prop

Than edit with << notepad++ >> and save
"""
video.use.overlay 0
ro.sf.lcd_density 240
"""

adb remount -oremount,rw /
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb remount -oremount,ro /
adb reboot

[Dr_Bunsen]

passthrough support in xbmc

Is SPDIF passthrough in xbmc supported in 1.2.5? I don't see it mentioned in the change history?

[wasser]

Is SPDIF passthrough in xbmc supported in 1.2.5? I don't see it mentioned in the change history?

it should work in 1.2.5

[wasser]

OK

but I am used to set density to 200...

Franck

It's in default.prop on boot.img you have to change it.

[108mob]

Tried loading this on my q7 box and just dosent boot red light stays lit wish we can have our model supported thanks wasser

[wasser]

Tried loading this on my q7 box and just dosent boot red light stays lit wish we can have our model supported thanks wasser

i can only support models which i have. This model isn't supported yet.

sorry for bad new!

wasser

[108mob]

i can only support models which i have. This model isn't supported yet.

sorry for bad new!

wasser

thank you anyway !

[bluesmanuk]

I tried 1.2.5 1080p on the old version box and overall I am very impressed.

I did find that I had frequent lockups for between 10 and 20 seconds when navigating around.

I am now going to try the 720p kernel nut need my memory refreshing about something.

When flashing the 720p Boot and Kernel, can I do it over the top of what I have now or will I need to erase idb and start from scratch?

Great work wasser

[franckleroy]

adb shell
cd /system
ls -al build.prop
-rw-r--r-- root root 3033 xxxxxxxx build.prop


adb pull /system/build.prop build.prop

Than edit with << notepad++ >> and save
"""
video.use.overlay 0
ro.sf.lcd_density 240
"""

adb remount -oremount,rw /
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb remount -oremount,ro /
adb reboot

Thanks ! I know how to change build.prop.
The problem is that is this release, change of density in prop file is not taken into account by the firmware.
So I use an app called LCDdensity that change density but the settings doesnot resist to a power off/power on.


Franck.

[franckleroy]

It's in default.prop on boot.img you have to change it.

thanks ! I'll try it.

Franck

--edit

franck@ks361053:~/rk3188$ ./split_bootimg.pl boot-1080p.img
Android Magic not found in boot-1080p.img. Giving up.

failed ...

[wasser]

thanks ! I'll try it.

Franck

--edit

franck@ks361053:~/rk3188$ ./split_bootimg.pl boot-1080p.img
Android Magic not found in boot-1080p.img. Giving up.

failed ...

the boot.img doesn't include embeded kernel. So it doesn't work with split_bootimg.pl.
you have to use:

mount boot.img /mnt/boot

wasser

[wasser]

I tried 1.2.5 1080p on the old version box and overall I am very impressed.

I did find that I had frequent lockups for between 10 and 20 seconds when navigating around.

I am now going to try the 720p kernel nut need my memory refreshing about something.

When flashing the 720p Boot and Kernel, can I do it over the top of what I have now or will I need to erase idb and start from scratch?

Great work wasser

it's expected that after the first boot frequent lockups appear because many installation processes still running in the background at the first boot.