Hi everybody,

No matter which image I use, the following film jerks under Kodi.

 R.E.D.2.Noch.aelter.Haerter.Besser.2013.GERMAN.DL.2160p.UHD.BluRay.HEVC-4K


  iMDB.............: https://www.imdb.com/title/tt1821694/                 
  Length: 116 min.                                                  
  Video: MPEG-H HEVC Video / 2160p / 23.976 fps / 16:9 / Main 10 Profile 5.1 High / 4:2:0 / 10 bits / HDR / BT.2020 /
  Audio: German / DTS-HD Master Audio / 7.1 / 48 kHz / 24-bit (DTS Core: 5.1 / 48 kHz / 1509 kbps / 24-bit)                                                                                            
  Audio: English / DTS-HD Master Audio / 7.1 / 48 kHz / 24-bit (DTS Core: 5.1 / 48 kHz / 1509 kbps / 24-bit)          
  Subtitle: German/English  Forced / German                                                                        
                                                          


With my Firetiv stick 4k no problem?

Does anybody know the reason? And which image I should use on rockpro64?

You will need:

Hardware:
1)     Usb type c cable, if you don’t have a type c cable you can also use an adapter
 
Software:
1)     Drivers if you hadn’t installed already:
files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip
2)     ADB files (platform tools) from Domo:
https://drive.google.com/file/d/1YAMZF0J...mDRpP/view
 
Ok let’s start:
 
1)     Go to settings/about tablet and tap build number at the end of the menu 7 times, this enables developer options on settings
2)     Verify that usb debugging is enabled on settings/developer options, if it’s on turn off and turn on again
3)     Restart device, wait for it to start…
4)     Connect usb to type c cable (adb only works on the usb type c port)
5)     Go to folder where you downloaded your Platform Tools, hold down the shift key and right click in a white portion inside the explorer window of the platform tools directory while still holding the shift key, select open command window here, wait for screen to open.
6)     Type:
 
adb devices
 
It will start running deamon and do device recognition, if you had already opened adb it will only show available devices, if device does not show verify you have usb debugging enabled and restart again and you have connected usb type c to your computer, not all cables will work if you repeat process and device is not recognized change cable, still not showing try in another usb port on your computer.
7)     Type:
 
adb shell
 
8)     Type:
 
wm size 1920x1080
 
type “exit” without quotations to exit adb shell, type exit again to exit adb
 
9)     Now you should have 1080 resolution, if you have OVERSCAN or Underscan fix inside android under settings/display/hdmi/screen zoom
 
That’s it, quick and easy, if you have questions comment bellow
 
Thanks to b0lshevik for sharing command and Domo for sharing platform tools.

Link to visual aid in the following video:
https://youtu.be/Fi5Rg0AoTkg

This is my very first post at the forum. I would like to use the PCI-E slot to mount a graphics card in my RP64. Is it possible? If so how do I get it working? Any help apprieciated.

That's what I am understanding from the Wiki - am I understanding correctly?

What I am trying to replace: mini-itx  I LINUX Mint, 3 drives and a noisy fan. 

Typical usage:

- Music/video streaming (youtube/SomaFM, etc)
- Browsing
- Darktable (photo editing)
- ebook server
- Libre Office
- email (Mailspring)
- watching video downloads
- Transmission torrent client
- VS Code (web sites)

Occasional/optional usage:

- video editing

Need to be able to:

- connect to 3 drives (USB?)
- connect to VT KEYBOARD
- do HDMI

Questions:

1 - is this possible with the RockPro64 in a small fanless case?
2 - is Linux Mint 19 running on this yet?

First get your hardware:

1)      Usb to type c cable, if you don’t have a usb to type c you can use an adapter
*usb 3 to usb 3 cable should work but I tried with mine and did not work
Cables are not created equal if procedure does not work after following instructions try with another one, I’ve got plenty of cables and procedure only worked with 2, if you can adb to your phone it should also work for this.

2)      A jumper to short out pins, if you do not have one you can use 2 sided female gpio cable to jump pins anything that can short the pins should work just be careful.

Software:

1)      Download Android Flash Tool:
files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip
 
2)      Download Drivers:
files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip
 
3)      Download Image for android I recommend this one it’s the one that has worked best for me:
files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz
--Unzip to get image you will burn, download comes zipped you need to unzip, remember where you put the image file and the name so you don’t get confused selecting unzipped download… better yet once unzipped just delete the zip file.
 
While you are at it might as well download Domos platform tools from here:
https://drive.google.com/file/d/1YAMZF0J...mDRpP/view
 
You can use minimal adb or any already installed adb, but Domo download has a set of packages we will need later to install google store, so might as well use this one.

Would recommend you keep all your downloads in a single separate folder for easier location of files.


Ok let’s Start!

1)      Install drivers from driver download, it’s an exe file that’s called DriverInstall
 
2)      Go to your downloads and run the exe file called AndroidTool from the file you downloaded
 
3)      Unplug your rp64 from power source and leave it like that, take out your microsd if you have one, make sure your emmc is plugged in correctly
 
4)      Short the pins with jumper (pins that need to be shorted are right next to the emmc)
 
5)      Open your Android Tool (yes this is step 2 repeated) make sure its open
 
6)      Connect your usb cable to computer and type C to rp64 (flashing only works on type c to my experience if you have found differently please comment bellow)
On Android Tool you should get Found One MASKROM Device
 
7)      Connect power again, wait for device description on android tool to recognize device
 
8)      Disconnect jumper, wait for device description on android tool to flicker
 
9)      Go to Android tool and Go to Upgrade Firmware on the top menu (flash will only work on MASKROM)
 
10)  Select firmware and select your unzipped image, be sure to have it unzipped and selected the right image burning the wrong image or burning an unzipped image can really be a headache to troubleshoot cause you might not know what went wrong.
 
If Flash doesn’t start then:
Unplug power, make sure there is no microsd card, put jumper back, make sure emmc is connected, take type c out wait for light to disappear and connect type c again, put power back in wait to see message in android tool flicker,  take of pin once device has been recognized and wait for android tool device flicker, take off jumper pin and try again. If after a few tries still not working try changing your cable.
 
If your issue is device not found this is most likely a driver issue, go to device manager find what rp64 appears as in device tree and try to add driver manually from the drivers folder you download,  if this doesn’t work just delete the driver, after that device should pop out again, driver issues can be very frustrating it might be reading as and adb device from a previous install or a manufacturer brand you made or as a phone (like sony, huawei piking it up) even then just delete driver from the device on device manager or add correct one, if this doesn’t work there are many videos on the internet explaining how to fix these kinds of issues they can be very particular so maybe post bellow and some can help you.
 
11)   If flash did not finish or gave an error flash again, its happened to me before eventually it will flash correctly. With any luck you got it right on the first time. Sometimes it even finished and didn’t work in my case, had to reflash.
 
12)   Finally connect as you normally would, without jumper…
 
13)   Wait a good 5 minutes and voila, Android at your service.
 
Once you get the hang of it process to flash should take around 5 to 10 min first time is the hardest because of trouble shooting and forgetfulness but after that it’s a breeze.

For Visual aid you can see video at the link bellow:
https://youtu.be/JBjWyajeZPw


If something remains unclear leave a comment to see if I can help you and further explain.

Hi: My Pineboard connects to an external monitor but my Pinebook which has the Pineboard as its motherboard does not. I'm using an adapter to connect the micro hdmi on the Pinebook to a standard hdmi cable that goes to the monitors. I read somewhere that a special cable from Pine64 is needed. Is this true and if so what is different? How much do one of these proprietary cables from Pine64 cost? Thanks

Hey all,

Posting here in hopes that I can get some guidance on where to turn next. Wanted a second opinion before I go ahead and attempt to get a replacement board, since the last one took close to a month to ship. 

Essentially, my RockPro64 just refuses to boot. I'm using the 64GB SD Card purchased from the Pine store, and have tried burning multiple distros to the card using multiple devices (a mac, PC, and linux machine) but no dice. When I plug in power, the lights on the Ethernet port light up, as well as the power light next to the DC input, but it looks like the USB ports get no power as my KB and mouse do not light up and I get no signal from HDMI. 

I then purchased a serial adapter CH340G to attempt to check the boot process of the board, however I can't seem to get any serial output from the board either (My steps for that detailed in a post here)

Apparently it is common that the SD Card slot on the boards ships broken, does it sound like that is the case? It looks like the board itself is getting power according to the lights on the ethernet port. 

Additionally, does it make sense that I would get no serial output even if the SD Card slot was broken? Will the board only begin outputting to the serial terminal if it has a functioning boot device? I was hoping even if the sd card slot was bad, I would at least see some errors in the serial console as it tried to boot.

Just looking for advice on what to do next/if it's worth debugging further or if I should begin the returns process?

Hello everyone,

I’m planning on making a series of how to videos on the rp64 including:

How to install google play store
How to adb on the rp64
Fix resolution and screen size
How to burn android image to emmc no adapter required
How to install images to sdcard
 
I’m working out of my phone so don’t expect high quality videos or audio, I only hope they are helpful and get the job done transferring the know how to address some of the issues I have personally experienced and make them friendly for the average joe that has no developer experience.
 
The intention is to make it easy for anyone to get the best experience of this board helping people that already have the board and by showing how easy things really are, also invite people that are looking around for an upgrade for their raspberry what this board can and cannot do.

If you are actually interested in any content in particular on how to achieve something atm have no order of launching videos so will take in consideration requests.
Link to the introduction video bellow, please don’t burn me on the audio/video quality, I’m just a noob working out of full ghetto hardware and software.

Intro video here: https://youtu.be/3uC3n3gfEk4

I've had my board going for a couple weeks 24/7 doing SETI calculations.  I just hit a milestone and thought I'd share my results:

Account stats:
Account Computers

Team Stats:
ARM