I received my pinebook 14 inch yesterday. It came with 3 half-dead black pixel on white background on original Xeinial Mate image ship. It is really not big deal. I just ran script to upgrade kernel, u-boot, and system to get rid of flicker backlight brightness problem. I started noticed noise random green pixel when I plugged power. Blue, green, and gray background are affected. Unplugged power will stop noise random green pixel in Armbian 5.32 image but Xeinial Mate 0.6.2 will not… just slowly continue in battery mode until sleep and wake up.
I am not only one. There is other person who have same problem as mine but he don’t mention power supply plug-in. Here’s link https://forum.pine64.org/showthread.php?tid=4843 That video is exently same problem as mine.
Sadly, Armbian 5.32 image caused my laptop got permanent 4th dead green pixel. It is worse nightmare than half-dead black pixel. I decided stop using Armbian image to come back Xeinial Mate 0.6.2. here's image https://drive.google.com/open?id=0B9ywmn...mR4bzhoUlE My eyes see green
Here are images I used
1. Original Xeinial Mate. (I am sure it is 0.5.2.)w
2. Upgraded Xeinial Mate 0.6.2 or 0.7.10-105, I think. I lost tracking again.
3. Stretch Minimal 0.7.10-105
4. Armbian 5.32
Now, I am using Xeinial Mate 0.6.2 on eMMc. (linux pinebook 3.10.105-bsp-1.2-ayufan-77 #1 SMP PREEMPT Sun July 7 12:09: UTC 2017 arcg64 GNU/Linux) I am trying redownload Xeinial Mate 0.5.2-59 for SD card now. I’ll update it later.
P.S. I opened ticket support for just in case. maybe they send replacements board (and screen if they can) if USB adapter as power supply still caused problem.
EDIT: Downgraded Xeinial Mate 0.5.2. There are no longer noise random green pixel when i plugged power supply but backlight brightness flickering made me triggered mad until turn off auto reduce backlight brightness on power management for battery mode or upgrade 0.6.2. i have no choice. Just disabled auto reduce backlight brightness. I played wallpaper background with blue. No problem at all. Thanks to guy at IRC for tips. I thinking get screen replacement due to permanent 4th dead green pixel. Im updating ticket support.
Also, I really like Armbian because chrome performance and good modified XFCE and preinstalled programs. but I must stay away from Armbian 5.32 or upgrade Xeinial Mate 0.6.2 to avoid noise random green pixel problem. Keep in Armbian 5.32 and Xeinial Mate 0.5.2 still uses 56hz refresh rate. Xeinial Mate 0.6.2 uses 63hz. I think it is power management software problem, not refresh rate. Right now, I wanted report bug software but where? Let me know thanks.
Although it might not act like it, this should be considered a beta build. !!You are responsible for your own choices from this point forward. Please read the instructions and understand them before continuing!!
Then, using the Pine64 Installer, select Image, then browse to the downloaded img.gz file, and select that.
Select the proper SDcard location, followed by the Flash button. Then wait for it to flash and validate.
Finally, insert the SDcard back into the A64+, and power on. You should see a few seconds of black screen leading into the boot animation.
Confirmed Working:
Wifi
BT
video playback
Substratum
Root
Bunches of other stuff .
HDMI video @1080p and HDMI audio
Not Working:
SuperSU will update, but not boot afterwards, so just don’t update.
Whatever I missed in my testing
Setup Instructions:
After the bootanimation completes, you will see a Android Starting progress bar on the screen. For speed sake, let’s wait till that finishes doing it’s thing. Then swipe down from the top, and select WiFi, and connect to your network.
Next, swipe down from the top status bar again, and you should see a dialog asking to setup a backup account. Select that, and sign into your Google account.
Finally, hit the Home button, and select your launcher (Select Google Now launcher for the traditional Android UI, or select Taskbar for the more desktop like, Freeform Windows based UI)
I am trying to build Android kernel for Rock64.
I got the kernel from https://github.com/rock64-android/kernel.
But I am not sure which kernel config to use.
The arch/arm64/configs directory has
defconfig
rockchip_defconfig
rockchip_smp_noughat_defconfig
Telnet or ssh to rock64 linux system, when the data is large, such as dmesg or alsamixer, telnet or ssh will be stuck. This looks like a kernel bug, but I don't know how to fix it.
So, first, thank you for accepting me in the forum. Just by reading around, I have learned allot. I am no techie but have a bit of background in computers... Just enough to get me in trouble! Well, enough of that! I have a couple of questions for our esteemed knowledgable crew here that I cant seem to find a way through or around. After having my Pinebook for a couple of months, I am no go on these.
1-Printer drivers. I use a Brother mfc 255cw which has a linux driver on their web site, BUT, will not install because "wrong architecture". Any way around that, or through that? No other generic seems to work at all. Thoughts?
2. Do we have any idea of additional software will become available through the software boutique? It starts, it runs, but nothing is there. From what I read that might change soon? Can I get software for the Pinebook any other way?
3. Pinebook seems jumpy, hesitates, especially via internet work. I am on a fast connect wifi that does not act that way on other computers. Any ideas how that might be addressed?
I have run sudo apt updates && sudo apt upgrades to make sure I am up to date...
Any suggestions on the above is greatly appreciated.
This is a follow-up to the "dead Alt keys issue" on my Pinebook; the corner pin(12) of the 8051 is bent, which resulted in dead Alt keys (both of them); neither one send scancodes from my keyboard.
What I did to get full functionality (including AltGr key) is to connect a usb numeric keypad to the Pinebook, and then use xmodmap (part of the x11-xserver-utils package) to remap the keysym(s) kp_left and kp_right and kp_begin to Alt_L and Alt_R and Control_R!
I did not have xmodmap installed on my xenial-i3 image, so I had to install it with :
sudo apt install x11-xserver-utils
1) the first step is to build an xmodmap file of the current mapping :
xmodmap -pke >xmodmap_original
The file is human readable... study it.
2) second step is to copy the original file, and then edit the copy :
3) save the changes file and then activate your new xmodmap with :
xmodmap ~/xmodmap_changes
Congratulations ! The keypad left and right are now Alt_L and Alt_R !
Notes:
You can check the new keysym(s) with the tool xev. xev can be used to check your entire keyboard, and mouse; it will report the scancode (keycode) and keysym for all keys including the numeric keypad.
This only works in x11. What we're doing here is to set a different keysym in x11 for a given scancode. So, in x11, in the above example, scancode(s) 64 and 108 now do nothing in x11; and the scancode(s) 83 and 85 now take on new meaning(s) ... new keysyms !
The kp_begin (keypad 5) has been remapped as Control_R ; interesting because the Pinebook doesn't even have a Control_R !
The changes are lost with reboot; unless, the xmodmap is executed at startup in rc.local, or as a systemd service one-shot !
I was planning on using my ROCK64 as an OpenVPN server, Torrent server and a Air Video (iOS) server to stream to iOS clients and basically operate the unit in headless mode.
But since I have a big fat 4K TV it would be a shame to let the HDMI port not go to use. Are there software packages that would allow me to view the content my Air Video server streams to iOS clients? I have to install the proper codecs on the SBC in order for this to work, so I asssume I should be able to send the content to the HDMI port. I've used predecessors of Kodi on other servers. Are there similar options available for the Rock? What about infrared options so I can control the thing with my universal remote?
Looking for a bit of advice, have just got a Pine64 starter kit and have put it together, however the power supply doesn't
have the slot on pieces for the plug part that goes in the mains socket, does anyone know if this is normal as there didn't
seem to be room left in the box for it :-)
![[Image: qGAeJ3y.png]](http://i.imgur.com/qGAeJ3y.png)
![[Image: nzsZTTY.png]](http://i.imgur.com/nzsZTTY.png)
