As the thread says, I would like to have an alternativ eto this horrible built in keyboard on my 14" Pinebook.
I'm an i3 user on the pinebook and this keyboard is just awful
It often does not recognize keystrokes and the spacebar is pretty much broken.

I was told to ask tllim if he ever comes back online in the irc, but I haven't got the chance to do so.
So, is there a way to replace the keyboard with a better alternative?

I have seen conflicting information about the speed for the DRAM. The forum lists the speed as 1866MHz (actual clock of 933MHz), while the Pine store lists the speed as 1600MHz (actual clock of 800MHz). So which is it? Also what is the clock frequency of the GPU?

Edit: Update from MrFixIt2001 - December 2021: There is now a new retro-gaming OS available - RCADE. The older recalbox releases are now archived and outdated. Click this link to read about RCADE.... Click this link to download the latest release.

Edit: 02/05/2018  There is now a Recalbox image available for the Rock64 (in Alpha at the time of writing). Click this link to download the image and learn more.

Edit: 10/11/2017  If you intend to use the Rock64 for retro-gaming there now is a dedicated Lakka build available for download. Will update this thread further as other retro-gaming releases become available. 


N.B.The results and impressions below are based on a pre-production Rock64 2GB with eMMC and on an early Android TV build, so the performance may differ on production units and/or newer software iterations available at launch (and beyond). 

There are many other (and considerably more useful) use-cases for the upcoming Rock64 than playing old video games, but there is no denying that the application of such boards for retrogaming has a huge following in the broader SBC community. I feel that the R64 will be a strong contender in this respect, offering a better price-to-performance value than its immediate competition and significantly better performance than the popular alternative. 

At the time of writing, the Linux image has yet some way to go, so I will not be reviewing the performance of emulation on Linux. But to calm those of you reading this post and wanting to play on Linux - I already played Mariokart64 using Mupen64 on Retroarch in an early Linux build and the game ran well. I will revisit this thread as Linux image(s) mature a bit or when an official Emulationstation or Lakka build gets released.

Onto testing; all results are from an R64 equipped with 2GB of RAM and eMMC. I used Ayufan’s latest (0.1.8) Android 7.1 TV image with a wireless Xbox 360, an 8Bitdo Pro (in wired mode) and a wired PS3 controller. All controllers worked well in the ATV GUI and in Retroarch; to be more specific the wired PS3 and 8Bitdo (I'm waiting for compatible BT dongle) controllers worked perfectly out-of-the-box, but the Xbox360 controller required some setting up in Retroarch. As for testing, I left all the settings in the respective Retroarch cores at default values for the sake of consistency and having a baseline for comparing the board against other offerings on the market.

Before I go onto describe my initial experience, let me get this out of the way; the R64 will run NES, Master System, SNES, Megadrive, Final Burn Alpha , Mame, (ended up testing these emulators - see below), Amiga, etc., games (as well as homebrew games and ports such as Cave Story - which I highly recommend - as well as Doom or Quake) flawlessly, so there is no need for me to review performance of the respective Retroarch cores. To this end, I will say that I ran popular SNES and Genesis games as well as some ports without any issues and didn’t experience any slowdowns even with overlays and shaders spec'd out to my liking.

Now, the three systems I was particularly interested in: Nintendo 64 (ParaLLEI N64), Playstation 1 (PCSX ReARMed) and Playstation Portable aka. PSP (PPSSPP). Out of the games which I tested (and own on original consoles) Playstation games ran completely flawless on stock core settings. In fact, they ran so well that I bumped the resolution up and added some nice scanlines and a softening (hq2x shader) shader and saw no impact on performance. There were some missing textures in cutscenes while playing Metal Gear Solid - so in my matrix (see below) I market the performance as Good rather than Flawless. That said, the game itself ran flawlessly. All things considered I feel comfortable saying that PSX games will run either flawlessly or near-perfectly on the R64.



Onto Nintendo64. Quick note, I had some issues with Mupen64Plus - an emulation core known to deliver better performance than ParaLLEI N64 (the core I use in this review) on other SBCs - so I may end up re-running the N64 games after I figure out what the problem is. In contrast to PSX, Nintendo 64 emulation is a bit of a mixed bag. Mario Kart 64 and Super Mario 64 both ran pretty much flawlessly with only minor slowdowns or oddities now-and-again, while Perfect Dark and Golden Eye were playable at best. I was able to crank up the resolution on Mario Kart 64 and Super Mario 64 somewhat, but adding softening shaders made the games chug more than I am willing to accept. Thankfully, adding scanlines had a much less noticeable impact on performance, so if scanlines are your thing then you are good to go.



Lastly I tried out two PSP games - God of War: Chains of Olympus and Soul Calibur: Broken Destiny. While God of War:CoO was a complete slideshow, Soul Calibur was playable albeit with a few slowdowns. The thing that gave it away was sound, which was crackling during slowdowns. Perhaps with some tinkering you could get some PSP games to a near-perfect state; sadly, I know too little about this emulator to say with certainty how well PSP games will run on the R64.  

[Edit] I was asked to try out FBA and MAME and report on the performance. In short, it works really well. I played a couple of my favourite arcade games and as expected they ran without any issues. In FBA you can apply a virtual overclock ( you are not actually overclocking the board - it 'pretends' to overclock the arcade machine) and this resulted in smooth gameplay in games that famously chug - such as for instance the Metal Slug series. I noticed that Retroarch 'smudges' 2D games by forcibly applying bileniar filtering, which is probably not an issue if you sit across the room from a big screen but its terrible if you sit up-close to the screen. Thankfully, It can be turned off in video settings. Shaders were a bit of hit-and-miss. Some of the sharders I expected to perform well  -such as crt-pi or ntsc-color - rendered the games unplayable. I don't know why this is, but its something to be aware of.
I have updated the matrix table below accordingly of course. 



Summing it up; if you wish to play retro games from the early and late 90’s (or earlier) then the R64 is a solid board for this particular purpose. It offers better performance (by a fair margin) than the most popular option on the market and a comparable retrogaming experience to its direct competition but at a lower price-point. One last remark, it is perfectly plausible that the R64 would offer better performance with standalone emulators in android or while running a dedicated Linux retrogaming build like RetroPie, so do take the results for what they are - an early look at the capabilities of this system. 

Below you will find a matrix (Xalius likes matrices so I felt obliged to provide one) of the tested games and their respective performance.

If there are any other games you’d like me to run do let me know!

Hi


I have used pine64.org pages a couple of years with F-Secure Safe Browsing Protection program.
No problems.

But today F-Secure Safe do not allow access to pine64.org web pages.
Without Browsing Protection access is allowed.

Is it only me how had this gain problem?

Br: Kaarme42

Hi

I wonder why

SKU: R64-PB-POWER Categories: Pinebook, ROCK64

power supply input voltage are between  110V-220V AC
In europe the common voltage is 230V AC
Is it really only 220V AC ?

I trying to look at picture in store but the picture are not so clear.
Is there any approvals like UL,  TUV or SGS ?
CE is not real approvals :-)


BR: Kaarme42

?Hi,

Could somebody please explain me, wether it is possible to decode multiple H.264/265 streams in RK3328 hardware at the same time?
I would like to play four 1080p H.264 videos on 4K video-screen, kind of video-surveillance system.

Hi all,

I got the Pine64 2GB version. I am wondering if there is any way to have Netflix play in HD resolution.

Thnx in advance for your answer!

See Post #4 for key module pics & analysis.

The 14" Pinebook keyboard misses keypresses if you're a very fast typist. 

This issue is a mechanical problem, not apparently electrical and occurs because fast keypresses will from time to time 'hit' on the corners of the keys. If the keys are pressed distinctly in the center of the key the misses are not apparent.

Also, hunt&peck typists will likely not have this issue either;  for the reason stated above.

The Pinebook prototype does not have this issue because the mechanism under the keytop is slightly larger;  the keybutton has a 'further' key-travel just by a tiny bit;  just enough that full key travel occurs regardless of where the key is pressed (center or corner) !

The downside of the prototype keyboard is that there is a noticeable 'gap' around the key;  and the keyboard is NOT sealed.  Consequently, dust can get into the keyboard and gum it up.  The newer keyboard was designed for less key-travel (and less dust) but which unfortunately resulted in missing keypresses. 

I was planning initially (for the purposes of electrical testing) of swapping out the lower case assembly (containing the prototype keyboard and trackpad) with the lower case on my pre release Pinebook.  This has shown to be not practical. The prototype keyboard is plastic riveted into the lower case, and the lower case is quite a bit larger than the 14" lower case mold-- significantly.  The lower prototype case is 349.25mm wide, and 231.78mm deep. The trackpad is white and is significantly larger too; 74.6mm x 103.19mm.  The only practical way to test the prototype keyboard with my 14" pre release Pinebook is to run an FFC cable extension assembly (with connectors) across the table to the running Pinebook.  

This test is probably better suited to the laboratory, frankly, but I am game for trying it if I can find the right adapter and extension;  will keep you posted on that !

The only other difference I can 'see' is that the prototype keyboard has the unimportant dreaded Microsoft Windows logo on the menu key (third from the left, bottom row). All things being equal, I can see why the hardware developers chose the present keyboard over the 'Microsoft' keyboard with dust openings!  Unfortunately, the released keyboard & case did not undergo sufficient pre release product testing.

Notes:   user's list:
sample case 1

Hi there. I have queued for BTO for long time and received my coupon email on
2nd June but it went to my spam folder and I didn't notice it after its expiry. 
I have sent an email to support and open a ticket as well (#1406) but so far I have not received any response.
Is it possible to renew my coupon so I won't need to wait for few more months?

Please do not update SudoSu in the A7.1 image as it breaks the installation. 

You can permanently prevent SudoSu from nagging you about updating by following these steps: 

1. Open the Google Play Store, go to Menu -> Settings.
   
2. Tap on the "Auto-update apps" and select one of the two "Auto-update apps" options to enable it.
   
3. Go back, then go to "My apps" section, locate the app you want (e.g. anti-virus app that you mentioned) and tap on it once.
   
4. Now tap the Menu button and the first option should be the "Auto-update." Ensure the checkmark is present for this app.
   
5. For all other apps that you have installed, you will need to follow steps 3 and 4, but this time disable the "Auto-update" setting by unchecking it.