[Ended] E series widget -autostart w/o USB

[juusso]

virtual usb has hw conflict. this is known. I remember here was some solution, but what users did i can't find now.

[mm85]

could this cause the skype starting problems?

how can i disable virtual usb? Uncomment the following lines?

ln -s /dev/loop3 /tmp/loopnone
sync
chmod +x /mtd_rwcommon/widgets/user/SamyGO/data/busybox
/mtd_rwcommon/widgets/user/SamyGO/data/busybox losetup /tmp/loopnone /mtd_rwcommon/widgets/user/SamyGO/data/128mb.xfs
/mtd_rwcommon/widgets/user/SamyGO/data/busybox mount -o sync,exec /tmp/loopnone /mnt
/mtd_rwcommon/widgets/user/SamyGO/data/busybox --install -s /mnt/bin
sync

[mm85]

sorry - just uncomment the first line...

[mm85]

what are the steps to disable virtual usb?

[juusso]

check wiki for SamyGO All Extensions. Then you get more info about that stuff.

[greenhorn]

pls let us know if you find solution. I would like to have samygo and skype at the same time.

[fluffi444]

Regardig the camera issue with active samyGO:
viewtopic.php?t=6126
[HOW-TO] Restore no/black WebCam on ES7000/8000 with SamyGo

[juusso]

thanks fluffi, we need this on wiki...

[mm85]

Thanks unfortunatelly this does not fix Skype.
Now one Stupid question from a noob : why is the libSkype.so neede in the Samy Go widget? Shouldn't it be possible to remove the whole part (files, calls from Scripts) and start the SamyGo Widget manually in SmartHub.

Is there any special hacking inside the libSkype.so? Who can give me some details? I would like to dive lot more deeper in this part.

Thanks for any answer

[Lordbyte]

Thanks unfortunatelly this does not fix Skype.
Now one Stupid question from a noob : why is the libSkype.so neede in the Samy Go widget? Shouldn't it be possible to remove the whole part (files, calls from Scripts) and start the SamyGo Widget manually in SmartHub.
Is there any special hacking inside the libSkype.so? Who can give me some details? I would like to dive lot more deeper in this part.

Thanks for any answer

I have no real knowledge about this issue, but I have a theory that the libSkype.so is what you call an "attack-vector".
Clever reverse engineering have allowed for modifications to libSkype.so that allows libSkype.so to escape theTV?s sandbox,
and perform the actual modifications to the parent system effectively rooting the TV at boot-time.

Damd clever approach !