-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
piccap cant get root status after update #61
Comments
Hey, try to reset your echo '{"priority":150,"backend":"auto","address":"127.0.0.1","port":19400,"width":320
,"height":180,"quirks":0,"fps":0,"vsync":false,"autostart":true,"nogui":false,"novideo":false,"uibackend":"auto"}' > /media/developer/apps/usr/palm/services/org.webosbrew.piccap.service/config.json |
Hi there, I am experiencing the same issue. Can you provide me with the steps to delete the json file ? |
Got the same promlem. |
Hello, got the same error here, but found an answer. There is a typo here: piccap/frontend/js/servicecalls.js Line 58 in e81f361
According to the source from webosbrew, instead of I was able to change the file through the terminal, rebooted the tv and it worked. EDIT: If someone wants to live change it, there are 2 instances to replace in the same line. |
this sounds
This sounds interesting, man. can you specify which files need to be changed, and where to find them? or you can also share the line of code that makes the changes. Also, are you saying that if the changes are made whiles piccap is not running, only 1 file needs to be changed, and that becomes 2 files whiles piccap is running? |
Sure, it's the one located in
I wasn't that smart, I just updated the servicecalls.js and restarted. Piccap doesn't seem to be autorestarting on mi tv, nor picking up the saved config, but it's working after a manual restart. It's progress, I guess. |
you're wrong. Everything is correct in the program code. Here is a similar one for you in another project |
Yeah, probably. I just posted what I found and what worked for me. Do you know what the root cause of this issue is? I'm happy to help testing any new fix. |
I have the same problem |
solved (I uninstalled 4.2>>reboot TV>>reinstalled 4.2 and piccap was able to get root. see post under this) Same there. Calling PicCap Service zu get root status HBChannel exec failed! Code: undefined |
I had the same issue, unable to get root. I uninstalled 4.2>>reboot TV>>reinstalled 4.2 and piccap was able to get root. |
Hey guys, |
@TBSniller may I ask the list of old files that we need to delete? Because I tried that and the issue is still present, there is an eternal loop trying to get root status. |
Did you uninstall them reboot TV? |
@matiaspirovanovarela
But you should not delete them manually before uninstalling your app. I don't know which sideaffect this would have. |
@silfa718 yes, I even tried installing 0.4.2, rebooting, uninstalling, rebooting and installing 0.4.2 again. @TBSniller I found the following with everything uninstalled. Should I delete them just in case?
Just in case, these are my specs: TV model | LG TV UJ6560 |
@matiaspirovanovarela: You can definitely try it. Think you know it, but just in case: Keep in mind to only delete piccap related files. Deleting the ones from other apps might destroy their permissions. |
And if this also doesn't helped try the following:
These will giving PicCap root permissions |
Thank you both. I just did this:
Should I try editing the config file instead of step 5?
|
Intresting, sounds like service is crashing due to autostart. Can you redo your steps to get a working PicCap again. After that don't activate autostart, more do another reboot and check if PicCap is running after this reboot without autostart |
Of course. Here are the steps:
I tried again but this time without changing any quirk. This time it seems to avoid the loop. Even activating the autostart works. |
Does PicCap work for you without autostart feature? Is your capture working? |
Yes, I need the quirks but at least it's capturing. |
Alright, then it might be related to this: webosbrew/hyperion-webos#99 |
I don't have it enable (I disabled it some time ago to test if that could help) |
Small update, I changed the config to have |
If you are using wrong quirks, that aren't suitable for your TV you can expect crashes. |
Here you are: piccap_log.txt |
I think you will have to enable QUIRK_DILE_VT_NO_FREEZE_CAPTURE. Can you enable, save and try again? Make sure you are saving while PicCap was working, as saving function calls hyperion-webos, which should not have crashed beforehand |
I was able to enable the option, save and reboot just fine. Still need to start it manually. |
Can you provide logs please? |
Sure. When I started it again today, it stopped working, it was all black. I had to rollback the quirk by editing the config file. So, I started with PicCap working, without autostart and no quirks. I just activated |
Hi there... Im having the same issue with piccap. Can you please tell me how did you unistall piccap and them installed it again? Did you use Telnet or SSH command line? Thanks! |
same issue here, anybody can help us? Thanks! |
@silfa718 can you please tell us how to uninstall Piccap? |
uninstall piccap: |
@menotuu: This worked for me. Thank you! |
I had a running system and it was so boring that I tried to update homebrew channel from 0.5.0 to 0.5.1 and piccap from 0.2.3 to 0.4.2 (argh)
now piccap cant get root status and service cant be started. hbchannel exec failed!
I removed piccap and homebrew channel and rooted tv again. I never made an tv firmware update.
its still the same. homebrew channel says root status: ok.
ssh is working, so I think piccap have a big problem with my tv. I dont know how to solve the problem.
the problem is old, i read here about a same thing, but it should be fixed in 0.4.1.
I removed piccap 0.4.2 and installed 0.2.3 - all working fine!
I updated to 0.4.1 - same fault: calling Piccap-Service to get root-status
Board type | M19_DVB
Hardware ID | HE_DTV_W19H_AFADABAA
Product ID | OLED65B97LA
webOS TV version | 05.20.06
Software Version | 4.9.5-6
The text was updated successfully, but these errors were encountered: