Samba/Skype 2.0.1 firmware issue

[nmou88]

Ok ... I wanted to buy a new webcam but just before I reconsidered the fact that the device was working good and I didnt want to spend my money for nothing so I ended up with another solution that might work : reinstalling the firmware ...

I did it right now and surprise ! Samba server reworked !
Server name is "Android-759A5C" not "LOCALHOST" and I can access it, I hope it will stay like this ...
But bad side : skype still wont work with the cam 
I'm sad and think that the only thing I can do is to wait for next firmware or buy another webcam model more compatible with the q10 pro ... I will see

[nmou88]

Ok I just bought logitech c270 webcam that is supposed to be a supported peripheral but bad news ... IT STILL DOESNT WORK ! 
Really disappointed, I think there is only the other solution then : wait for next firmware for skype ... anyway ... I will wait

Edit : I tested again and discover something, the webcam works if I make first an audio call then activate video during the call  Im a bit satisfied, it's better than nothing while waiting for the next firmware ...
Between, I have another question (Im sorry) about skype: during video conversation , it seems that skype zoom in the webcam image (maybe to fit on the screen or something) ... Is there a way to disable this and please, answer me because I'm waiting for your reply

[nmou88]

?

[nmou88]

No one 
Aditionnally, samba server bugged again 

[futeko.com]

Your experience is not typical and neither of the problems you're having are easily explainable. Hence the lack of replies.

If you continue to have these issues I suggest installing the Android 5.1 firmware. It may help with webcam compatibility and possibly with the LAN problem (although I think this is more likely a problem with your network).

[nmou88]

With the previous 2.0.0 firmware, I didnt have those problem that appeared in 2.0.1 ... So I dont think for samba problem that my network is in question, I also changed my internet router by a new one and it doesnt solve issues so the network is definitely not the problem, something more that prove that : there is none dhcp or samba share problem with no one of other devices (windows or android or ios)
Same for skype, there was no problem with 2.0.0

Anyway, If you telling me that, I see only one solution like I told before : wait for 2.0.2 firmware ... (If it's his name  )

[nmou88]

This is my router : https://assistance.orange.fr/equipement/livebox-et-modems/livebox-play-sagemcom#fiche_presentation
Sagemcom

[nmou88]

New 2.0.3 firmware is out and I installed it to see if it fixed my problems ... Well, it did but there was new ones 
So I was bored with this and tought I will always get new problems with android 7 firmwares
That's why I decided to test android 5 1.1.0 firmware and surprisely all the bugs went away ! DHCP is working now correctly (it was never with android 7) and samba server is up and skype works perfectly ... Between it's not that perfect, I have a little problem with 1.1.0 that I had before (localisation was the problem at this time) : the box wont turn off so I have always to plug off the power cable and plug on again, I dont know if there is a fix for this ...
Anyway, I will try to find a fix for this little problem but now I'm more satisfied with android 5 firmware then android 7 : )

[Mount81]

Between it's not that perfect, I have a little problem with 1.1.0 that I had before (localisation was the problem at this time) : the box wont turn off so I have always to plug off the power cable and plug on again, I dont know if there is a fix for this ...
Anyway, I will try to find a fix for this little problem but now I'm more satisfied with android 5 firmware then android 7 : )

I have a similar issue here with 1.0.9 fw, tho' it's with turning on the device. Sometimes -it happens randomly, or just couldn't find out what causes it- it fails to power ON. I press the power button on the remote, that lights on the Q10 Pro indicates that it has been powered up, but nothing happens on the TV screen (No Signal).  After it fails to respond to the remote, and have to plug in out and in again from the power socket. The next boot up was always successful.

I have 1.0.9 installed almost since it came out, and in the beginning there was no such an issue, but started to occur in the last few week more often.

Tho' I can't remember if I had any hangs during powering OFF...

[futeko.com]

Are these on/off problems only using the Rii airmouse? If so they are fixed in FW 2.0.3 and later.

The standard IR remote should have no problems turning box on/off using any firmware.

[nmou88]

Are these on/off problems only using the Rii airmouse? If so they are fixed in FW 2.0.3 and later.

The standard IR remote should have no problems turning box on/off using any firmware.

It won't turn off even with original IR remote ... Between it turns on normally with no problem for me

[tmihai20]

I had no problems turning my Q10 Pro off with original remote on any firmware up to 2.0.1. A friend that fixes electronic devices fixed my middle button on the original remote, I do not have the issues I had before, with remote not responding to commands as before. But the fact that it does not turn off with any remote may not be caused by a faulty button. I used both official and pcristi's firmware.

[nmou88]

Like I said, I had this problem before and it was not related to remote
Look here : http://www.futeko.com/newforum/index.php?topic=1499.msg12189#msg12189
Now it's the same problem but I dont know if google maps is the cause (I dont think so) and I dont think the remote is the problem ...

[Mount81]

Are these on/off problems only using the Rii airmouse? If so they are fixed in FW 2.0.3 and later.

The standard IR remote should have no problems turning box on/off using any firmware.

No it's with the original IR remote and it's not that it's not receiving the IR signal (or something like that), rather  -as I have written- it's lightning up the LEDs on the front panel, but the device won't boot at all. Only plugging out from the power socket and back a again would help to "reset", and on the second attempt powering on it usually will boot normally as expected. Ok, I have repeated here my hole post this time, but please read next time the post accurately before hinting a response.