[Soeiro02]

Indeed, it stays stable when I replace with the original one.

Indeed, I'm a bit tired of all these installs

Just hope that RP makes its magic and finds a solution.

[NunoF]

Still having the same issue with your latest file, RP

[patria o muerte]

Hi RP,
could you include your latest librtmp.so in Spmc version?
http://spmc.semperpax.com/
thanks

[RedPenguin]

Wow I can't win right now with the RasPi, LoL.

Even the "go-to" fallback method of attempting to compile a file on the device itself, is getting me no where.

Normally that takes most errors out of compiling vs a cross-compiler.

I am still working on it, just not exactly sure what was broken.

[Mabs]

Hi RP,
could you include your latest librtmp.so in Spmc version?
http://spmc.semperpax.com/
thanks

Try this APK:

Code:

https://www.mediafire.com/?ha7ej7jsh8sapr7

I have made it just by your request.

You have to backup your SPMC addon folder just to be safe.
The folder location depends on the device, but is something like this:

.../Android/data/org.xbmc.xbmc

(For official XBMC)

The Minix version is something like this:
.../Android/data/hk.minix.xbmc

For SPMC I'm not sure but it can be this:

.../Android/data/com.semperpax.spmc

If you are trying to install on top of your actual SPMC, its possible you get an error.
In that case, you have to make backup of that folder above and uninstall your previous SPMC installation.

After that you can install my altered version (I only updated librtmp. nothing more. no tweaks) and restore the backup to original location.

You should run SPMC once and quit before restoring backup. Its safer.
Please give update if it worked for you.

[RedPenguin]

ATTN PI Users:

I have apparently finally fixed the RasPi file (OpenELEC users please also tell me your experiences, hopefully this release doesn't explode your XBMCs, if so I will have to perhaps release two builds):

http://www.mediafire.com/download/bfqls3...brtmp.so.0

The smaller file size does seem to be correct in this case.

The original is around 101KiB while mine is 125KiB.

Rasbian/RaspBMC must have updated a lot of libraries and when you compile against them now, there must be way less overhead, is the only thing I can picture as to the smaller file size.

I was able to remake the gnutoolchains.com RasPi toolchain using files from my only a month old RaspBMC and this time it not only did not crash XBMC RaspBMC release but it also played a jan jua stream, so I know it's using the latest build.

[Mabs]

RP, my own RaspBMC was stable with the 30.08 file and i just updated to the above 03.08 version.

Still stable. Rock solid and with streams (even the hard ones) working as normal.

[RedPenguin]

RP, my own RaspBMC was stable with the 30.08 file and i just updated to the above 03.08 version.

Still stable. Rock solid and with streams (even the hard ones) working as normal.

Nice.

I attempted to do it with the latest "beta", from the RaspBMC Test Builds post, but any add-ons like LiveStreams, LiveStreamsPro, etc seem to explode or cease to function in the very latest build.

[Soeiro02]

Sorry RP Same behaviour.

I changed the file, made sudo reboot and it stuck on the blue (restart shortly) screen, with a ": \ is busy" message in the lower left corner. So I powered off/on, accessed System Info menu and...reboot.

[Mabs]

Another bad news: doesn't work with Milhouse's build r19161 (02 setember)
It doesnt reboot the pi, but tried a certain stream and it didn't work. It simply stood there. No error, no stream.

I replaced by the 30.08 version and the same stream worked flawlessly.

[RedPenguin]

Sorry RP Same behaviour.

I changed the file, made sudo reboot and it stuck on the blue (restart shortly) screen, with a ": \ is busy" message in the lower left corner. So I powered off/on, accessed System Info menu and...reboot.

You def are running RaspBMC not OpenELEC r?

Also if RaspBMC, you are making sure the file is owned by user:group pi : pi and permissions 644 correct?

I did the above and cannot produce any crashes with the stable/release XBMC.

[Soeiro02]

I'm running Raspbmc, permissions 644, but owner/group is root/root, just like the original file. Does it make a difference? Want me to try with pi/pi?

[RedPenguin]

I'm running Raspbmc, permissions 644, but owner/group is root/root, just like the original file. Does it make a difference? Want me to try with pi/pi?

I would try with pi/pi. For some reason by default that's what my Pi was set to.

If that does not work, please post your xbmc.log, using http://wiki.xbmc.org/?title=Log_file if you aren't sure how.

[Soeiro02]

Just changed the ownership and group and sudo reboot. For some reason, with the updated librtmp files, this command never works...it hangs on the blue screen. Let me power off and I'll send you the log in a sec.

Noticed that all the files inside "System" folder (the one that contains librtmp file) are also root/root.

EDIT: Here's the log file
http://xbmclogs.com/show.php?id=285170

[RedPenguin]

Just changed the ownership and group and sudo reboot. For some reason, with the updated librtmp files, this command never works...it hangs on the blue screen. Let me power off and I'll send you the log in a sec.

Noticed that all the files inside "System" folder (the one that contains librtmp file) are also root/root.

Is your RaspBMC an old install or a fairly fresh install?

I am thinking there is maybe a diff for some reason.

Mine is fresh and all system xbmc files are owned by pi/pi.

Both librtmp.so and librtmp.so.0 are.