Although it retails at $419, just over double the Pinebook Pro, I think it would still be considered a fairly affordable laptop. It seems aimed less at tinkerers, and more at people who want a fairly nice Linux ultraportable that's ready to go out of the box. It seems to have some fairly nice features for the price, including:
Built for Linux
Intel Management Engine disabled
Firmware updates through LVFS
Full metal case
11.6" 1920x1080 IPS semi-matte screen
8 GB RAM, 240 GB SSD
Intel Pentium N4200 quad core
Dimensions: 0.53" x 11.1" x 7.5", 2.54 pounds (the Pinebook Pro is a little wider but thinner, and a few ounces heavier)
I think either one would look professional in a work meeting. Anyone care to hazard the relative power of the N4200 vs the RK3399?
We are using rock64 v2 for a big roll out in every part of the world in our product. Our product runs 365x24x7 and we have some questions about long term stability of rock64 hardware.
Our hardware configuration: Rock64 (2GB) with Forsee eMMC and Bluetooth Dongle (StarTek) and rock64 recommended wifi dongle and with some other USB interfaces.
1. We would like to know what is the max number of days the rock64 ran with some applications are running with max of 2 cores are being used at all times without rebooting/shutting down and powering up?
2. If we run continuously, is it tend to slow down the processing?
3. Do we need to take any precautions to run this hardware 365x24x7?
We have some observations (not concrete), but we would like to know what is the capacity of the rock64 to run 365x24x7.
I'm a big fan of i3wm and I'm hoping to try it out on the phone, curious if anyone has tried it yet. I think a special approach to using the i3 shortcuts in a touch capacity would be needed to make it worthwhile, but that might not be too difficult. Any other thoughts on tiling window managers?
On my PBP, Chromium crashes every time I try to go to settings if I'm not running it as a superuser. So I cannot enter my Google Passpharse to sync all my bookmarks.
It works fine if I run "sudo chromium-browser", but that seems to use a different profile. The passphrase takes there, but when I go back on as a regular user, it's not synced.
I really don't want to run chromium as a super user every time. Any thoughts on how to fix this?
I tried to compile librespot for the rock64 unfortunately it throws me an error that it can't be compiled :
------------------
= note: /tmp/cargo-installPJfUds/release/build/byteorder-e6b6a6b0fb32eb88/build_script_build-e6b6a6b0fb32eb88.build_script_build.d7wzi3u7-cgu.0.rcgu.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
error: aborting due to previous error
error: could not compile `byteorder`.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `librespot v0.1.0`, intermediate artifacts can be found at `/tmp/cargo-installPJfUds`
---------------
I haven't figured out would the problem might be (noob programmer, so to say). I also tried to install the raspberry binary which caused the system to overload - so that didn't work either.
Good news:
I found a project that ported the lib into java :
https://github.com/librespot-org/librespot-java
.... and it works (nearly) perfect. Just install java, set the option mixerSearchKeywords = "default" int the config.toml file .... that's it
By accident I put inverse polarity at rockpro64 and these chips near power supply were burnt, can anybody send me the parts names so as to try to replace them?
The internal speakers are secured to the palm rest with adhesive. Additionally there is adhesive on the foam attached to the speakers facing the bottom magnesium cover.
When disassembling the bottom cover from the palm rest the speakers pull off the palm rest, sticking to the bottom cover. Although this is not a huge problem, this exercises the speaker wires more than I like.
The solution I devised way to apply plastic wrap (common food wrap, not cellophane) to the foam on the speakers. I then used a pair of scissors to trim the plastic wrap around the outer perimeter of the foam. Then I carefully cut a slit within the inner perimeter of the foam and then used the scissors to trim the plastic wrap within the inner perimeter of the foam.
This prevents the speakers from attaching to the bottom magnesium case. They remain attached to the palm rest and the speaker wires remain undisturbed when the bottom case is removed from the palm rest.
The sound quality of the speakers remains the same as before the fix, but in full disclosure I have old man ears with specific frequency impairment in one ear. My good ear can not discern any difference.
Update: 17 DEC 2019:
This has been an effective solution. To improve the adhesion of the speakers to the palm rest assembly I used a dab of silicon adhesive under each speaker.
![[Image: EKtvqVoXUAEeWXY?format=jpg&name=4096x4096]](https://pbs.twimg.com/media/EKtvqVoXUAEeWXY?format=jpg&name=4096x4096)