The output of vivaldi:gpu
Everything works. However watching Youtube videos in the browser causes the cpu temp to go sky high. Normally the cpu temp on my pi400 is between 35-50, watching a youtube video for just 10 minutes and it jumped to 70.
So yes opengl works with the proper flags but it also causes the PI to go nuts.
Neither Chromium nor Firefox cause the same issue.
Better off not messing with the flags.
@bpz Thanks a bunch! I'm running 64-bit Armbian on a Pinebook Pro. I couldn't figure out how to resolve the ELFCLASS error. Following your instructions though made the install as smooth as can be, no dependencies problems. I appreciate you saving my sanity.
For 64-bit, download and install the packages yourself, changing armhf to arm64 in the URL. 64-bit is not supported in the repo, but they packages exist. Here are some steps: Install 64-bit Vivaldi on 64-bit Pi
@Toni2021Berlin In Vivaldi Cam and Mic is only activated if you allow it by webpage request. This mode is Ask for permission.
You can disable Mic and Cam by default.
Open Settings→ Webpages
Set Mic to Disable
Set Cam to Disable
@bpz Please collect as much information on your findings on this issue and file a bug report:
I doubt a lot of other users will be able to reproduce on this specific hardware 😉
I've got one more update. Further testing on my end showed that only Firefox was picking up v4l2loopback devices, all chromium-based browsers that I tried were only showing devices corresponding to physical cameras. However, v4l2loopback has the following argument:
parm: exclusive_caps:whether to announce OUTPUT/CAPTURE capabilities exclusively or not (array of bool)
Setting this to 1 makes it only advertise one of the two capabilities at a time, depending on whether any input data is available, and that seems to be enough for Vivaldi (and other chromium-based browsers) to consider the loopback devices usable.
hi @ScottN, any news on this..? did you end up using the app?
my problem is more related to animation at the moment, videos seems to play fine on chromium but the idea was to trigger some animations, sliding cards and things like that with a sensor, it works ok but tearing is really really annoying... did you really had animations playing with no tearing in default chromium?
also tried pi3d with some planes so to write textures directly to gpu, it's a lot better on the tearing side but also less practical and flexible than just having html files... have not tried to let the thing run for a few hours either
thanks for any new info..!