[Jolind]

Anyone but me having problems with the official iOS remote app and latest version (12020)? Primary controls like select, stop and arrows work but the menu and info buttons does not work. Is it just me or is it a common problem?

[Ned Scott]

Anyone but me having problems with the official iOS remote app and latest version (12020)? Primary controls like select, stop and arrows work but the menu and info buttons does not work. Is it just me or is it a common problem?

Known issue. Updates are coming for the official remotes.

[dijkx]

Hi,

OpenELEC Development build (r12220):
http://sources.openelec.tv/tmp/image/ope...20.tar.bz2

to update a older build without reinstalling see:
http://wiki.openelec.tv/index.php?title=...g_OpenELEC

Please also read http://sources.openelec.tv/tmp/image/ope..._FIRST.txt for general notes about our development builds.

After releasing our OpenELEC-2.0 build based on XBMC Eden the development for OpenELEC-3.0 has started which will officiall support RaspberryPi builds.
We have merged now our work on OpenELEC-3.0 in our master branch because of this and the releasing there was not much updates the last time.

This are the changes:

• updated XBMC to the last and greatest XBMC master checkout, including the latest changes from Gimli, many thanks! :-)
  
• updated firmware, kernel patches and BCM librarys *
  
• various other improvenments, fixes and package updates.
  

With this build we have update the latest bootloaderfiles to support 512MB RPi's (see: http://www.raspberrypi.org/phpBB3/viewto...25#p198079 and http://www.raspberrypi.org/phpBB3/viewto...25#p198247. This also also includes the following changes:

• on creating a fresh SD-Card a default config.txt will be installed which allocates 128MB GPU memory on 256MB and 512MB Raspberry's
  
• on updating there will be checked if a config.txt exist, if not the default config.txt will be installed
  
• if a config.txt with a uncommented variable 'gpu_mem' variable already exist nothing will be changed
  
• if a config.txt without a 'gpu_mem' variable exist our default config.txt will be installed and will be enhanced with your old config.txt. your old config.txt will be backed up to config.txt.bk.
  

Please backup your old config.txt in the case you dont find your license codes anymore before you install this update

After the update please check your /flash/config.txt byself and report back any issues. Please report back if this update work like excepted on 256MB and 512MB Raspberry's

because XBMC now supports officially RPi and PVR please use XBMC's Trac (http://trac.xbmc.org/) to report XBMC bugs and OpenELEC's github issue tracker (https://github.com/OpenELEC/OpenELEC.tv/issues) for OS related issues and feature/driver requests.

Aspect ratio of my portrait pictures is wrong in this version if I install OpenELEC-RPi.arm-devel-20120930151812-r12026 , my pictures look right again.
Pictures look very squased in the new version. Version OpenELEC-RPi.arm-devel-20121019015509-r12196 is also wrong.
Both in slideshow and normal mode they are wrong.

[Wanderlei]

can anyone confirm if they have a pi v512 working with openelec? I get the following error on the splash screen

Code:

***Error in prepare_sysroot: mount_common: Could not mount /Flash/SYSTEM ***

i have checked the md5s. this is occurring for me on all versions i have tried.

Pleased to say this has now gone and I have a working openelec thanks to the latest dev version

I was getting a similar problem before with corruption from over clocking on 512mb boards, except it was happen to the linux partition. It is still happens r11220, on my 512mb board. Some apparently have problem if core-freq is overclocked causing corruption. There was some fixes to the start,elf but it happens with some boards.


256mb
gpu_mem=128
arm_freq=899
sdram_freq=449
core_freq=349

512mb
gpu_mem=256
arm_freq=900
sdram_freq=450

[azraleus]

Hello,
I've noticed that after updating to 12020 my zd1211-based wifi dongle no longer works.

I have similar issue with my TP-LINK wifi dongle TL-WN721N. After updating to r12220 from r12196 dongle's led don't even blink.

Code:

root /var/log # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
root /var/log # lsmod
Module                  Size  Used by
ath9k_htc              52865  0
ath9k_common            1652  1 ath9k_htc
ath9k_hw              348187  2 ath9k_common,ath9k_htc
ath                    13919  3 ath9k_hw,ath9k_common,ath9k_htc

There are also problems with "Official XBMC Remote" for Android. I cannot send text entry, youtube plugin fails when sending url to xbmc, and java errors appears often.

[Wanderlei]

Yeah my wifi has gone too, dosnt even blink.

Model: Asus N10

[Trixster]

Just tested my new 512mb pi with 12220. The extra memory seems to make a big difference to the responsiveness of the GUI and especially when calling up movie info and fanart. Everything just seems a bit slicker. Good stuff!

[jaromanda]

my wifi is "gone" too ... actually BOTH my wifis

One needs 8192cu.ko
Other needs r8712cu.ko

(I think I got those numbers right .. not at home at the moment)

I got a message SOMEWHERE saying "unsupported wifi device" or "wifi device is unsupported" ... 99% sure it was in xbmc.log ... I'm guessing it's an openelec problem rather than xbmc, as latest xbian works with my wifi dongles

[Wanderlei]

With 254mb vs 512mb.

I think a 256mb with higher overclock beats 512mb board. Most of the extra memory is just sitting there unused.

[rbej]

if you want to get rid of the upscale, you will have to compile it from source.
follow the compile guide and let it compile after it is done goto the sources/xbmc folder uncompress the xbmc tar.xz
In file xbmc/windowing/egl/WinEGLPlatformRaspberryPI.cpp and change limits in the ClampToGUIDisplayLimits function to 1920x1080 instead of 1280x720.
compress the folder again and change the md5
remove the .stamp/xbmc from the rpi build dir
compile again, should take like 5 mins everything is allready copiled, it will only compile the file changed.
install on the SD

Btw they could allow to define that limit in a configuration somewhere, so that the user could change it. If that message when changing view modes is right...

Very Thanks!!. Working perfect!!.

Build r12223 with GUI 1080p

http://netload.in/dateidrWlSdf9Ld/r12223gui1080.zip.htm

Update Instruction:

http://openelec.tv/installation/updating

After update, please delete guisettings.xml and reboot Rpi.

EXPERIMENTAL VERSION. USE AT YOUR OWN RISK!!. NO SUPPORT FROM XBMC TEAM!!.

[gimli]

if you want to get rid of the upscale, you will have to compile it from source.
follow the compile guide and let it compile after it is done goto the sources/xbmc folder uncompress the xbmc tar.xz
In file xbmc/windowing/egl/WinEGLPlatformRaspberryPI.cpp and change limits in the ClampToGUIDisplayLimits function to 1920x1080 instead of 1280x720.
compress the folder again and change the md5
remove the .stamp/xbmc from the rpi build dir
compile again, should take like 5 mins everything is allready copiled, it will only compile the file changed.
install on the SD

Btw they could allow to define that limit in a configuration somewhere, so that the user could change it. If that message when changing view modes is right...

Very Thanks!!. Working perfect!!.

Build r12223 with GUI 1080p

http://netload.in/dateidrWlSdf9Ld/r12223gui1080.zip.htm

Update Instruction:

http://openelec.tv/installation/updating

After update, please delete guisettings.xml and reboot Rpi.

Don't complain about OMX errors, i'm going to ignore them when patched sources are used.

[rbej]

I understand. Im add:

EXPERIMENTAL VERSION!!. USE AT YOUR OWN RISK!!. NO SUPPORT FROM XBMC TEAM!!.

[caravela]

I understand. Im add:

EXPERIMENTAL VERSION!!. USE AT YOUR OWN RISK!!. NO SUPPORT FROM XBMC TEAM!!.

you should increase the gpu mem to avoid those omx errors

[Trixster]

For 512mb boards which is likely to be the most optimal setup, a GPU/ARM split of 128/384 or 256/256?

[caravela]

For 512mb boards which is likely to be the most optimal setup, a GPU/ARM split of 128/384 or 256/256?

that depends on what you use your pi for, if you just run Xbmc 256/256 or 128/384 should be fine. if you are gonna have services running like uPnP, webserver, transmission, samba i would recommend the 128/384. Again just depend how much stuff you have running, more stuff more ram for the system

EDIT:just tried 128, 192 and 256 by bare observation i couldn't see any difference