+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: General Discussion on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=112)
+--- Thread: Default OS update log (/showthread.php?tid=7830)
RE: Default OS update log - GLSRacer - 11-24-2019
I just updated to 1.5 and now I have issues with an intermittent faint static sound from the speakers anytime there is audio present in a browser window, even if the audio is muted. I have tried several restarts (due to updating the trackpad firmware) and the issue persists. Also, any word on when we might see a fix for screen tearing in videos? Not a huge deal just wondered if the issue was on anyone's radar.
RE: Default OS update log - jiyong - 11-24-2019
I also updated to 1.5 and can confirm the faint high pitched sound from the speakers when a program "activates" sound (even when not playing anything).
Looks like the update improved compatibility with my USB-C hub. USB memory sticks work again.
Just one question, the default font doesn't support unicode.
Any recommendations for a font that does support unicode?
Update edit: I'm not sure if it was the trackpad firmware upgrade, or the 1.5 update, but you can left click by using two finger tap. Now you can avoid that noisy click. :-)
RE: Default OS update log - ryannshit - 11-24-2019
Does anyone have instructions on how to get this update?
sudo: /usr/bin/update_widevine.sh: command not found
Why does this have to be so painful?
How the heck does one run this update?
sudo /usr/bin/update_widevine.sh
sudo: /usr/bin/update_widevine.sh: command not found
RE: Default OS update log - Watercourse - 11-24-2019
(11-24-2019, 05:55 PM)ryannshit Wrote: Does anyone have instructions on how to get this update?
sudo: /usr/bin/update_widevine.sh: command not found
Why does this have to be so painful?
How the heck does one run this update?
sudo /usr/bin/update_widevine.sh
sudo: /usr/bin/update_widevine.sh: command not found
have you tried:
sudo apt update && sudo apt dist-upgrade
?
RE: Default OS update log - GLSRacer - 11-24-2019
If you are using the rock account then there will be a shortcut on the right side of the taskbar near the system time. Double click the round icon and enter the root password in the CLI window when it comes up.
RE: Default OS update log - pfeerick - 11-25-2019
(11-24-2019, 05:55 PM)ryannshit Wrote: Does anyone have instructions on how to get this update?
sudo: /usr/bin/update_widevine.sh: command not found
Why does this have to be so painful?
How the heck does one run this update?
sudo /usr/bin/update_widevine.sh
sudo: /usr/bin/update_widevine.sh: command not found
Are you sure that's the right path? Judging from ayufan's build, it looks like it should be:
Code:
/usr/local/sbin/update_widevine.shWorth double checking...
RE: Default OS update log - Luke - 11-25-2019
In first post I included quick instructions on how to change default 'rock' user and associated home directory to desired username.
Also included a performance fix for FireFox.
RE: Default OS update log - ryannshit - 11-25-2019
Thanks all.. After catching up on the updates I am able to boot to sd.
Default OS (updated to 1.5) won's suspend - sjk - 11-30-2019
Hi Just received my PineBookPro yesterday, and initial impressions are good. Updated using the supplied script to 1.5 without any issues.
My first hiccup is that suspend does not seem to be working. Hitting the power button and clicking suspend, cause it to sleep for a second, and then immediately wake up. Also closing the lid, does not seem to do anything, as I can still see the screen lit between the halves of the clamshell.
Thanks,
Scott.
RE: Default OS (updated to 1.5) won's suspend - tuxor - 11-30-2019
(11-30-2019, 08:46 AM)sjk Wrote: Hi Just received my PineBookPro yesterday, and initial impressions are good. Updated using the supplied script to 1.5 without any issues.
My first hiccup is that suspend does not seem to be working. Hitting the power button and clicking suspend, cause it to sleep for a second, and then immediately wake up. Also closing the lid, does not seem to do anything, as I can still see the screen lit between the halves of the clamshell.
Thanks,
Scott.
I am experiencing this too and fiddled around with it a bit but I could only get suspend to work once per boot. I don't have the logs handy right now, but there were some problems with systemd-suspend trying to put the eMMC back so sleep because they get a wakeup call from somewhere.