(28th Sep, 2014 08:23 PM)Biasio95 Wrote: [ -> ] (28th Sep, 2014 03:37 PM)rikardo1979 Wrote: [ -> ]hey guys,
for you having a problems with CEC, refresh rate switching and GUI artefacts, there is a fix thanks to guys from git
http://goo.gl/fdzo1z
But how can I modify that file?
you would need to SSH in or you can use soft such as WinSCP and edit the
Code:
/home/xbian/.xbmc/userdata/advancedsettings.xml
(28th Sep, 2014 03:37 PM)rikardo1979 Wrote: [ -> ]hey guys,
for you having a problems with CEC, refresh rate switching and GUI artefacts, there is a fix thanks to guys from git
http://goo.gl/fdzo1z
Will this fix be included in a future update?
(28th Sep, 2014 08:54 PM)rikardo1979 Wrote: [ -> ] (28th Sep, 2014 08:23 PM)Biasio95 Wrote: [ -> ] (28th Sep, 2014 03:37 PM)rikardo1979 Wrote: [ -> ]hey guys,
for you having a problems with CEC, refresh rate switching and GUI artefacts, there is a fix thanks to guys from git
http://goo.gl/fdzo1z
But how can I modify that file?
you would need to SSH in or you can use soft such as WinSCP and edit the
Code:
/home/xbian/.xbmc/userdata/advancedsettings.xml
Thanks, I did it
I only didn't knew where to find the file
I confirm that it worked, now it's just perfect
(28th Sep, 2014 10:47 PM)starous Wrote: [ -> ] (28th Sep, 2014 03:37 PM)rikardo1979 Wrote: [ -> ]hey guys,
for you having a problems with CEC, refresh rate switching and GUI artefacts, there is a fix thanks to guys from git
http://goo.gl/fdzo1z
Will this fix be included in a future update?
for sure
but as usual don't ask for ETA
Tested the latest RC3. Worked flawlessly with one exception: My remote can no longer access the context menu. Here is a comparison between RC2 (XBMC 13.1) and RC3 (XBMC 13.2):
Code:
00:22:09 T:3039068704 NOTICE: Starting XBMC (13.1 Git:20140604-84725b0). Platform: ARM Linux 32-bit
[...]
21:00:31 T:3039068704 DEBUG: LIRC: Update - NEW at 1824829:000000037ff07bf0 00 KEY_CONTEXT_MENU mceusb (KEY_CONTEXT_MENU)
21:00:31 T:3039068704 DEBUG: OnKey: 229 (0xe5) pressed, action is ContextMenu
Code:
19:32:05 T:3037962240 NOTICE: Starting XBMC (13.2 Git:20140912-4ecca7f). Platform: ARM Linux 32-bit
[...]
21:00:46 T:3037962240 DEBUG: LIRC: Update - NEW at 5320959:000000037ff07bf0 00 KEY_CONTEXT_MENU mceusb (KEY_CONTEXT_MENU)
With RC3 there OnKey response message is missing though the button has apparently been received. Seems to be an XBMC issue...
Has anyone else observed such behavior? Any ideas on how to further diagnose this or a workaround?
Update: With a CEC remote on RC3 (XBMC 13.2) the context menu key works:
Code:
20:59:49 T:3037831168 NOTICE: Starting XBMC (13.2 Git:20140912-4ecca7f). Platform: ARM Linux 32-bit
[...]
23:02:33 T:2933425216 DEBUG: PushCecKeypress - received key e5 duration 0
23:02:33 T:3037831168 DEBUG: OnKey: 229 (0xe5) pressed, action is ContextMenu
So the above problem persists: The context menu is button not processed for a remote connected via LIRC.
(30th Sep, 2014 02:05 AM)Oliver.O Wrote: [ -> ]Has anyone else observed such behavior? Any ideas on how to further diagnose this or a workaround?
As the signal is received, maybe the mapping in XBMC has changed?
Try if you can configure the context menu button via the addon/program "Keymap Editor".
My IR remote out-of-box is close to unusable. With that I can setup everything perfectly easy
RC3 keeps disconnecting my ssh connection before I can do anything after logging in. What could be the reason? this is on a fresh RC3 install on B+ Pi.
(1st Oct, 2014 03:42 PM)agent5150 Wrote: [ -> ]RC3 keeps disconnecting my ssh connection before I can do anything after logging in. What could be the reason? this is on a fresh RC3 install on B+ Pi.
long time back I was having exact same issue on my RPi. I have the wired network connection and it was disconnecting just straight after XBMC starts.
I took me almost two weeks to find out the cause was a cable from PSU. I have very stable 2.1A PSU but I need longer cable and at that time I havent have any other than cable from Amazon Kindle, so I was using it. And that was the cause, After I bought good quality cable issue was resolved.
So my recommendation, try different PSU/cable
After the last few days of use I have to let you know that my wifi is still not working constantly.
Sometimes Xbian won't pull the correct IP address via DHCP from my router and so wifi won't work.
This is my result when trying to restart my wifi (ifdown / ifup):
[
attachment=363]
Xbian won't recognize the DHCP offer sent by my router but then it takes some IP and says it's connected.
It's also showing the IP inside the system info but as I said, it's not really connected and it's even not the correct IP.
In this case the .101 address is already assigned to my girlfriends laptop.
When Xbian is trying to connect, my router delivers following output:
Code:
10/01/2014 19:21:54 sending OFFER to 192.168.2.100
10/01/2014 19:21:38 sending OFFER to 192.168.2.100
10/01/2014 19:21:22 sending OFFER to 192.168.2.100
[...]
and it already do list xbian.private as DHCP client on 192.168.2.100.
Seems that there is some problem around the DHCP handshake.
Any help / ideas?
(1st Oct, 2014 04:57 PM)rikardo1979 Wrote: [ -> ] (1st Oct, 2014 03:42 PM)agent5150 Wrote: [ -> ]RC3 keeps disconnecting my ssh connection before I can do anything after logging in. What could be the reason? this is on a fresh RC3 install on B+ Pi.
long time back I was having exact same issue on my RPi. I have the wired network connection and it was disconnecting just straight after XBMC starts.
I took me almost two weeks to find out the cause was a cable from PSU. I have very stable 2.1A PSU but I need longer cable and at that time I havent have any other than cable from Amazon Kindle, so I was using it. And that was the cause, After I bought good quality cable issue was resolved.
So my recommendation, try different PSU/cable
Thanks. I will try it. but doubt its the cable as it was working fine with model B Pi.
UPDATE: tried new cable, ssh still disconnects in less than 15 seconds after connection. Tried new PSU .. same result. This is driving me crazy. I can;t do jack with this B+ Pi.. also noticed android remote app yatse is also having connectivity issue with this Pi. RC3 on B+ needs work.
UPDATE 2: Was using putty.exe file. Downloaded putty installer. After installing it on my windows laptop, SSH connection to B+ PI running RC3 is not disconnecting. wierd.. but fixed
UPDATE 3: Nope.. celebrated too early.. still disconnecting... arrrrggghhhh.
(2nd Oct, 2014 10:25 AM)agent5150 Wrote: [ -> ] (1st Oct, 2014 04:57 PM)rikardo1979 Wrote: [ -> ] (1st Oct, 2014 03:42 PM)agent5150 Wrote: [ -> ]RC3 keeps disconnecting my ssh connection before I can do anything after logging in. What could be the reason? this is on a fresh RC3 install on B+ Pi.
long time back I was having exact same issue on my RPi. I have the wired network connection and it was disconnecting just straight after XBMC starts.
I took me almost two weeks to find out the cause was a cable from PSU. I have very stable 2.1A PSU but I need longer cable and at that time I havent have any other than cable from Amazon Kindle, so I was using it. And that was the cause, After I bought good quality cable issue was resolved.
So my recommendation, try different PSU/cable
Thanks. I will try it. but doubt its the cable as it was working fine with model B Pi.
UPDATE: tried new cable, ssh still disconnects in less than 15 seconds after connection. Tried new PSU .. same result. This is driving me crazy. I can;t do jack with this B+ Pi.. also noticed android remote app yatse is also having connectivity issue with this Pi. RC3 on B+ needs work.
UPDATE 2: Was using putty.exe file. Downloaded putty installer. After installing it on my windows laptop, SSH connection to B+ PI running RC3 is not disconnecting. wierd.. but fixed
UPDATE 3: Nope.. celebrated too early.. still disconnecting... arrrrggghhhh.
haven't asked yet, but are you cable or wireless ?
(2nd Oct, 2014 05:04 AM)CurlyMo Wrote: [ -> ]What adapter?
Realtek Semiconductor Corp. RTL8188SU 802.11n WLAN Adapter
Code:
xbian@xbian ~ $ lsmod
Module Size Used by
fuse 67641 3
nfsd 200831 2
joydev 8033 0
hid_logitech_dj 8058 0
r8712u 146232 0
frandom 3555 1
vchiq 192710 2
Today it's working great again. I can reconnect, reboot and everything - Xbian gets the correct IP everytime.
It's kind of strange because it seems to be a random problem.... (Because I didn't change anything.)
As I said, it's not the first time this problem occurs from nowhere. But for now the DHCP handshake is fine again:
Code:
10/02/2014 12:26:57 sending OFFER to 192.168.2.100
10/02/2014 12:26:57 sending ACK to 192.168.2.100
(2nd Oct, 2014 04:22 PM)rikardo1979 Wrote: [ -> ] (2nd Oct, 2014 10:25 AM)agent5150 Wrote: [ -> ] (1st Oct, 2014 04:57 PM)rikardo1979 Wrote: [ -> ] (1st Oct, 2014 03:42 PM)agent5150 Wrote: [ -> ]RC3 keeps disconnecting my ssh connection before I can do anything after logging in. What could be the reason? this is on a fresh RC3 install on B+ Pi.
long time back I was having exact same issue on my RPi. I have the wired network connection and it was disconnecting just straight after XBMC starts.
I took me almost two weeks to find out the cause was a cable from PSU. I have very stable 2.1A PSU but I need longer cable and at that time I havent have any other than cable from Amazon Kindle, so I was using it. And that was the cause, After I bought good quality cable issue was resolved.
So my recommendation, try different PSU/cable
Thanks. I will try it. but doubt its the cable as it was working fine with model B Pi.
UPDATE: tried new cable, ssh still disconnects in less than 15 seconds after connection. Tried new PSU .. same result. This is driving me crazy. I can;t do jack with this B+ Pi.. also noticed android remote app yatse is also having connectivity issue with this Pi. RC3 on B+ needs work.
UPDATE 2: Was using putty.exe file. Downloaded putty installer. After installing it on my windows laptop, SSH connection to B+ PI running RC3 is not disconnecting. wierd.. but fixed
UPDATE 3: Nope.. celebrated too early.. still disconnecting... arrrrggghhhh.
haven't asked yet, but are you cable or wireless ?
I am cable. ie wired LAN.
When ssh disconnects it refuses new connections and my android app stops connecting to this Pi as well. Reboot fixes it until next ssh disconnect.
(2nd Oct, 2014 09:58 PM)agent5150 Wrote: [ -> ] (2nd Oct, 2014 04:22 PM)rikardo1979 Wrote: [ -> ] (2nd Oct, 2014 10:25 AM)agent5150 Wrote: [ -> ] (1st Oct, 2014 04:57 PM)rikardo1979 Wrote: [ -> ] (1st Oct, 2014 03:42 PM)agent5150 Wrote: [ -> ]RC3 keeps disconnecting my ssh connection before I can do anything after logging in. What could be the reason? this is on a fresh RC3 install on B+ Pi.
long time back I was having exact same issue on my RPi. I have the wired network connection and it was disconnecting just straight after XBMC starts.
I took me almost two weeks to find out the cause was a cable from PSU. I have very stable 2.1A PSU but I need longer cable and at that time I havent have any other than cable from Amazon Kindle, so I was using it. And that was the cause, After I bought good quality cable issue was resolved.
So my recommendation, try different PSU/cable
Thanks. I will try it. but doubt its the cable as it was working fine with model B Pi.
UPDATE: tried new cable, ssh still disconnects in less than 15 seconds after connection. Tried new PSU .. same result. This is driving me crazy. I can;t do jack with this B+ Pi.. also noticed android remote app yatse is also having connectivity issue with this Pi. RC3 on B+ needs work.
UPDATE 2: Was using putty.exe file. Downloaded putty installer. After installing it on my windows laptop, SSH connection to B+ PI running RC3 is not disconnecting. wierd.. but fixed
UPDATE 3: Nope.. celebrated too early.. still disconnecting... arrrrggghhhh.
haven't asked yet, but are you cable or wireless ?
I am cable. ie wired LAN.
When ssh disconnects it refuses new connections and my android app stops connecting to this Pi as well. Reboot fixes it until next ssh disconnect.
what is the rating of your PSU? I still think you have an issue there. test the power on the test pins on RPi, instruction on their site