Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,120
» Latest member: benstoke
» Forum threads: 16,364
» Forum posts: 117,537

Full Statistics

Latest Threads
Real women, real desire, ...
Forum: General
Last Post: Spaker
Today, 01:04 AM
» Replies: 0
» Views: 31
Weatherproof case build
Forum: Enclosures
Last Post: ltorsini
07-07-2026, 07:01 PM
» Replies: 12
» Views: 38,525
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: PinePhoneProUser
07-07-2026, 04:47 PM
» Replies: 16
» Views: 11,083
pinecil v2 dosent negotia...
Forum: General Discussion on Pinecil
Last Post: moses
07-07-2026, 07:28 AM
» Replies: 0
» Views: 97
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
07-06-2026, 05:22 PM
» Replies: 2
» Views: 263
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
07-05-2026, 11:02 AM
» Replies: 0
» Views: 138
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,099
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 338
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 190
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,640

 
Information About the Pinebook - What to expect
Posted by: Luke - 03-27-2017, 06:01 AM - Forum: General Discussion on Pinebook - Replies (149)

Hello Everyone!

Now that we have a Pinebook forum I figured I'll post here and share some information with the community and use this as an opportunity to set the expectations about the device straight. A few days ago tllim received the finalised PCBs and the protective cases which the Pinebook will ship in. Once both the PCB and protective cases get green-lit, we expect BTO orders to start going out.  EDIT 1: The Pinebook site with a BTO section is now up on the Pine shop and the packaging is going though drop-tests. EDIT 8: Looks like the first BTO emails have gone out Smile 

NB: We are aware of issues with the BSP Linux image that shipped with the Pinebook. To find out more please read this thread

You will be able to install new OS images using the Pine64 Installer available under Software & SDK tab here

Edit 9: There is a wide variety of OS images for the Pinebook availble. To view them all please visit the Pinebook Wiki site. Other popular sources for cutting-edge and pre-release OS images includes ayufan's github

     
In the Picture first batch of Pinebook

Hardware

The Pinebook esthetics have changed slightly from the prototypes that were circulated to developers at the beginning of the year. Out of the two screen-size variants, the 14” has undergone a more significant change. The current 14” design is slimmer and sleeker than the prototype, with smaller bezels around the LCD screen and a sturdier construction. Both the 11” and 14” units now also come with a black multi-touch trackpad. EDIT 7 Here are some new pictures courtesy of ayufan (NB other production units DO NOT have the win key).  

Both units come equipped with a 1366x768 TN panel which is, subjectively speaking,  surprisingly good with decent colors and good brightness. The viewing angles are what you’d expect, although horizontal color distortion is on par with other TN LCDs I’ve seen on low-to-mid range laptops. It is also worth mentioning that no thermal issues such as overheating have been reported (even under load) on either the 11” and 14” pre-production units (there is a large heatsink covering much of the PCB). 

The Pinebook comes with 16GB of eMMC memory installed. The module is user-replaceable and in time, you’ll be able to buy higher capacity eMMC modules  EDIT 8: larger eMMC modules are available in the Pine store if you feel like you’re running short on space. I don’t have a production unit so I haven’t had a chance to test the read and write speeds on a production unit, but on the developer unit we saw read speeds up to 80MB/s and write speeds up to 40MB/s. 

You’ll also be getting 2x USB 2.0 ports, a microphone, a mini HDMI, 3.5mm 4-pin headset jack, two downward firing speakers, a 0.3 MPx (640x480) webcam and a Micro SD card slot. The webcam is nothing to write home about but it works and does the job in well-lit rooms. The speakers are a bit tinny, but even at full volume they sound clear without crackles or distortions.  

The Pinebook comes with a 10000mAH battery and charges using a 5V 3A DC adapter.  Depending on the usage scenario and OS the battery will last for roughly up to 6 hrs of continuous useEDIT 2: It appears that we have been using incorrect battery settings - the run-time may be longer than we initially suspected. The use of LPDDR3 RAM in the production units can also help greatly with stand-by time. 

EDIT 3: We recently had a user join the IRC and inquire about keyboard layout on the Pinebook. In a later post in this thread I wrote "(...) the keyboard is really the highlight here, with solid feeling keys that have a good travel distance (...)", but now I realise said nothing about the actual layout, which some of you may care about. Disclosure I know nothing about keyboards BUT to me is seems like the 14" is closer to a standard North American keyboard but doesn't have a right ctrl, and the 11" keyboard 'is kind-of as if a US and a UK keyboard had a baby'. The 11" has a 'flat' enter key and a short left shift. Xalius believes its "(...) the layout most of those universal Android keyboards come with". If keyboard layout is something that is very important to you then study the image of both units posted by pgmy64 a few posts down. For your convenience, here is a direct link to wiki explaining various keyboard layouts so you can compare Pinebook layouts against your local standard. 

EDIT 4: Some of you have asked about GPIO and UART on the Pinebook. While there are no GPIO pins on the Pinebook PCB, you will be able to use a PADI as described by Marcus in this thread if you wish to use your Pinebook  for tinkering. As for UART, it is accessible via the headphone jack.  

Software

The Pinebook is able to boot from both eMMC and Micro SD. To install software to the internal eMMC a SD card based installation scheme can be used. Currently pre-production units are running Android, BSP based Linux and mainline Linux images. EDIT 5: Production units ship with BSP Linux. A likelihood also exists that other OS’ will ship for the Pinebook in the future. 

At launch, you can expect to have full support for Android on your unit. Ayufan’s pre-release build of Android 7.1 with split-screen works really well for multitasking (in the image you can see a chat app running on the right and youtube on the left simultaneously). 

As of today, many features of the BSP Linux work on the Pinebook. Ayufan, Xalius and members of the Pine team are still working to overcome some remaining challenges to have BSP Linux working at its best on the Pinebook. It will largely be up to the community to help further develop and improve the BSP Linux experience on the device. 

Some of you will also be excited to hear that mainline Linux is also running on the Pinebook. It’s still early days, and as you’d expect many features are missing or not functioning correctly, but thanks to Icenowy and Xalius an early build of mainline Linux for the Pinebook has already been tested. If you are interested in following the progress on mainline Linux development I encourage you to check out Sunxi Linux Wiki  and their IRC Logs.

(EDIT 6) Payments, Shipping and Customs

First BTO e-mails should start going out soon (as of the time of writing - April 5th 2017). Here are some details about payments, shipping and handling. 

Shipping will be considerably quicker than in the case of Pine A64 boards - you can expect to have your Pinebook sitting on your desk within 5 days or so from the moment your payment is accepted its shipped out. With your BTO you'll also be given an option to purchase extras for your Pinebook such as: additional power cables, USB 2.0 to Ethernet 10/100Mbps dongle, Mini HDMI to HDMI adapter. 

Payments will be collected exclusively using paypal

Pinebooks ship from Hong Kong and shipping costs depend on where you live, but here are some estimates:

US: ~$28
EU: ~$35
CA: ~$32

Shipping costs are expected to fluctuate dependently on the number of shipped units. 
You may also have to pay a customs fee - custom fees differ from country to country so I won't offer estimates. 

Expectations

I think that it's fair to say you are getting a lot for the asking price. If you are looking for a device in a convenient laptop form-factor that you wish to tinker with, then I feel it is safe to say the Pinebook is the right device for you - in particular if you are a developer or tinkerer who is willing to document, share and give back to the community. This is also especially true for those of you who wish to run Linux on the device, since Linux is by-and-large a community undertaking.  

I don’t wish to discourage anyone from getting a Pinebook, as it is a good piece of hardware,  but if you are looking for a device to replace for your current work or school laptop then perhaps it’s wise to look elsewhere. 

I will make sure to update this post on a need-be basis. 


-Luke-


Sad Enable Mic on 3.5 jack port
Posted by: saro - 03-27-2017, 02:55 AM - Forum: Pine A64 Hardware, Accessories and POT - Replies (14)

Hi boys,
I'd followed the guide reported at enable audio on jack instead hdmi
and now I can hear the sound by the headset, but I don't understand
why I can't record by the mic.

Can you help me please?
Tnanks in advance.


  is it possible to connect 2 Ethernet port to SOPINE module?
Posted by: eddylai - 03-27-2017, 12:20 AM - Forum: P64-LTS / SOPINE Hardware, Accessories and POT - Replies (2)

is it possible to connect 2 Ethernet port to SOPINE module? (100Mbps or 1000Mbps)
my target requirement will be 2 NIC  and 4 Serial ports


  WiFi Packet Loss and Slow Speed PineA64 Debian 8
Posted by: Stymied - 03-26-2017, 12:34 AM - Forum: Pine A64 Hardware, Accessories and POT - Replies (2)

Hi, I have a Pine64 with Debian 8. Bought last July, finally getting around to setting it up as a fileserver. Installed x11vnc so that I don't need to keep it near a monitor.

I have the Wi-Fi/Bluetooth module and the backup battery installed. I am able to connect to my home Wi-Fi network, but the connection is pretty unstable and when I check it by pinging out to www.yahoo.com I get at least 30% packet loss and ping times from 400-2500 ms. When I ssh in from another machine, I get a lot of lag in between typing characters. It's incredibly slow and unreliable.

My home network is fine, at least from the point of view of all the other machines. I can happily SSH around, I get good upload and download speeds, and ping to www.yahoo.com takes less than 100 ms.

I have the antenna for the Wi-Fi module attached to the inside top of the wooden case, so I don't think it's a signal problem. The Wi-Fi icon shows 53% signal strength; not great, but shouldn't be this bad.

What's likely to be the problem? What should I check?


  Z-Wave - Full and Low Power Inclusion mode
Posted by: B34N - 03-25-2017, 02:24 PM - Forum: POT modules - Replies (1)

I have a Pine64 with the Pine US Z-wave module running openHAB2. I'm finally starting to move my z-wave network over from my old and dying Aeon Z-Stick. Some of my z-wave devices do not seem to support Network Inclusion mode and need a controller to be in directly reachable. Am I out of luck if I cannot bring my Pine64 in range of these devices? Or is there a method to have a secondary controller that I can bring close to these devices for pairing?

If I'm better off just buying a new removable z-wave controller stick and scrapping my Pine64 then please let me know.

Thank you,
B34N


  PINE A64(+) and Pinebook related topic
Posted by: pineadmin - 03-23-2017, 11:32 PM - Forum: General Discussion on Pinebook - No Replies

For PINE A64(+) and Pinebook related topic, please post it under PINE A64(+) forum and use the +PINEBOOK thread subject prefix to indicate that the thread/topic is also related to Pinebook.


  LCD touchscreen
Posted by: stephen fleming - 03-23-2017, 03:26 PM - Forum: P64-LTS / SOPINE Hardware, Accessories and POT - Replies (10)

Is it possible to use the LCD touchscreen with the SOPINE board using Linux? The reason why I ask, is that I was looking at a recent thread:
https://forum.pine64.org/showthread.php?tid=1183&page=7
Jessica Spongekipper posted

Code:
/boot/uEnv.txt looking like:    

   console=ttyS0,115200n8
   selinux=permissive
   optargs=enforcing=0 cma=384M no_console_suspend
   kernel_filename=kernel
   initrd_filename=ramdisk.img
   hardware=sun50iw1p1

   # Uncomment to enable LCD screen
   fdt_filename_prefix=pine64/sun50i-a64-lcd-
When i opened the same file running the version of Ubuntu for the SOPINE, this is what I saw:
Code:
console=tty0 console=ttyS0,115200n8 no_console_suspend
kernel_filename=pine64/Image
initrd_filename=initrd.img
ethaddr=ba:88:8e:64:aa:78 fsck.repair=yes
pine64_model=pine64-so
The line to enable the LCD was not there. Is it located in another file?


Question Pine64 cannot boot
Posted by: jamiechang917 - 03-23-2017, 08:30 AM - Forum: Linux on Pine A64(+) - Replies (6)

My Pine64+(2GB) cannot boot with any linux image,but it can boot with android image,I use 5V2.5A power supply unit and 30 cm usb cable.


  PINE A64(+) and SOPINE related topic
Posted by: pineadmin - 03-22-2017, 10:28 AM - Forum: General Discussion on PINE A64-LTS / SOPINE - No Replies

For PINE A64(+) and SOPINE related topic, please post it under PINE A64(+) forum and use the +SOPINE thread subject prefix to indicate that the thread/topic is also related to SOPINE.


  Turn your Pine64 into a music server with mpd
Posted by: JulianM - 03-22-2017, 06:47 AM - Forum: Pine A64 Projects, Ideas and Tutorials - Replies (2)

Hi together!

This topic is structured into a few categories.
• Prepare your Pine64
• Installing and setup MPD
• Fix sound problems with alsamixer
• Installing und setup Samba
• Control your MPD via IR remote control
• My own setup





» Prepare your Pine64

What do you need?
- Pine64 board.
- Speakers via audiojack.
- Install the latest Ubuntu image by longsleep.

What you'll get?
- A music server which can be controlled via Windows, Linux and Android.


First of all:
Download the latest Ubuntu image by longsleep.
Overview of all Ubuntu images powered by longsleep

I downloaded the following image:
xenial-pine64-bspkernel-20161218-1

After you have downloaded and burned the image on your micro sdcard you need to apply some pre requirements.



If you just downloaded the Ubuntu image you have to resize the partitions of your microsd card.
Just enter this command:
Code:
resize_rootfs.sh



Next step: Update the software of Pine64.
Code:
pine64_fix_whatever.sh
pine64_update_kernel.sh
pine64_update_uboot.sh
apt-get update
apt-get upgrade



Ok, all pre requirements are given now.




» Installing und setup MPD

Let's install mpd!
Code:
apt-get install mpc mpd
mpc (Music Player Command, client) is a command line program to manage mpd (Music Player Daemon, server).



Fix permissions of mpd directories:
Code:
chmod 770 /var/lib/mpd/music/ /var/lib/mpd/playlists/
chown -R mpd:audio /var/lib/mpd/music/ /var/lib/mpd/playlists/



Apply my config for mpd:
Code:
cat <<EOF >/etc/mpd.conf
music_directory      "/var/lib/mpd/music"
playlist_directory   "/var/lib/mpd/playlists"
db_file              "/var/lib/mpd/tag_cache"
log_file             "/var/log/mpd/mpd.log"
pid_file             "/run/mpd/pid"
state_file           "/var/lib/mpd/state"
sticker_file         "/var/lib/mpd/sticker.sql"
user                 "mpd"
port                 "6600"
log_level            "verbose"
restore_paused       "yes"
auto_update          "yes"
auto_update_depth    "3"
filesystem_charset   "UTF-8"
id3v1_encoding       "UTF-8"

input {
    plugin          "curl"
}

audio_output {
    type            "alsa"
    name            "My ALSA Device"
    mixer_type      "software"
}
EOF
The configuration of mpd is done.



Now activate audio output via 3.5 audiojack!
But please note:
The 3.5 audiojack will be the default device for all audio output with these configs!
Code:
cat <<EOF >/etc/modules-load.d/pine64-audiojack.conf
sunxi_codec
sunxi_i2s
sunxi_sndcodec
EOF
Code:
cat <<EOF >/etc/asound.conf
pcm.!default {
       type plug slave {
               pcm "hw:1,0"
               }
}

ctl.!default {
       type hw
       card 1
}
EOF



Reboot your Pine64 to apply changes of sound cards.
Code:
reboot



Just copy all your music files into the following directory:
Code:
/var/lib/mpd/music
I'll explain how to copy files from your Windows machine easily to your mpd server at the end of this post!



Take note that ownerships are correct!
If not, apply them.
Code:
chown -R mpd:audio /var/lib/mpd/music/



Update the music database of mpd with mpc.
Code:
mpc update



Alright, you're done!

Feel free to manage your mpd server with different mpd clients!
These are my favourites:
• Linux & Windows: Gnome Music Player Client
• Android: MPD ControlDroid MPD Client





» Fix sound problems with alsamixer

Normally there should be no problems with sound if you are using the latest Ubuntu image by longsleep.
So, you are advised to check the following settings in alsamixer.
Code:
alsamixer
Code:
Unmute "Headphone" with toogling "m"
Set "ADCL Mux" to "DMIC".
Set "ADCR Mux" to "DMIC".
Set "AIF1 DAC timeslot 0 volume" to 85.
Set "AIF1IN0L Mux" to "AIF1_DA0L".
Set "AIFIN0R Mux" to "AIF1_DA0R".
Unmute "DACL Mixer ADCL" with toogling "m"
Unmute "DACL Mixer AIF1DA0L" with toogling "m"
Unmute "DARC Micer ADCR" with toogling "m"
Unmute "DACR Mixer AIFDA0R" with toogling "m"
Set "digital volume" to "0".
Set "headphone volume" to "75".





» Installing und setup Samba

How to copy your files from your Windows machine to your Pine64 - Use SFTP or... Let's install Samba!

Code:
apt-get install samba-common samba



Create a Samba user to manage your files:
Code:
smbpasswd -a mpd
Just set a password for mpd user.



Apply my config to login via Samba with mpd user:
Code:
cat <<EOF >/etc/samba/smb.conf
[global]
workgroup = WORKGROUP
server string = Samba Server %v
security = user
dns proxy = no

[mpd]
path = /var/lib/mpd
valid users = mpd
force user = mpd
force group = audio
create mask = 0660
directory mask = 0770
browsable = yes
writable = yes
EOF



Restart Samba.
Code:
/etc/init.d/samba restart
Now you are able to copy your music very easily from Windows to your Pine64.



Just add a "Network ressource" on Windows with the following path:
Code:
\\ip-address-of-pine64\mpd
Username: mpd
Password: You have choosen it with "smbpasswd -a mpd"



[Image: mpdbsufd.png]




» Control your MPD via IR remote control

Control your MPD server with the official IR remote control by Pine64!


You need to install "keybinder", to re-mapping the keys of your IR remote control to execute commands.
Code:
apt-get install unzip gcc make
cd ~
mkdir keybinder
cd keybinder
wget https://github.com/elopez/keybinder/archive/master.zip
unzip master.zip
cd keybinder-master/
make
make install
cd ~
rm -r ~/keybinder



Use "evtest" to determine the event input of IR receiver:
Code:
apt-get install evtest
evtest
Choose the event number with "sunxi_ir_recv".
The event number depends of the plugged in usb devices!!!



Code:
root@pine64:~# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      sunxi-keyboard
/dev/input/event1:      axp81x-supplyer
/dev/input/event2:      sunxi-ths
/dev/input/event3:      audiocodec sunxi Audio Jack
/dev/input/event4:      sunxi_ir_recv
/dev/input/event5:      MCE IR Keyboard/Mouse (sunxi-rc-recv)



Now press a few buttons on your IR remote control.
You should see some entries like...
Code:
Testing ... (interrupt to exit)
Event: time 1490184760.781095, type 4 (EV_MSC), code 4 (MSC_SCAN), value 40400d
Event: time 1490184760.781095, type 1 (EV_KEY), code 13 (KEY_EQUAL), value 1
Event: time 1490184760.781095, -------------- SYN_REPORT ------------
Event: time 1490184761.023186, type 1 (EV_KEY), code 13 (KEY_EQUAL), value 0
Event: time 1490184761.023186, -------------- SYN_REPORT ------------
Event: time 1490184761.793386, type 4 (EV_MSC), code 4 (MSC_SCAN), value 404010
Event: time 1490184761.793386, type 1 (EV_KEY), code 16 (KEY_Q), value 1
Event: time 1490184761.793386, -------------- SYN_REPORT ------------
Event: time 1490184762.043188, type 1 (EV_KEY), code 16 (KEY_Q), value 0
Event: time 1490184762.043188, -------------- SYN_REPORT ------------
Event: time 1490184762.734733, type 4 (EV_MSC), code 4 (MSC_SCAN), value 404011
Event: time 1490184762.734733, type 1 (EV_KEY), code 17 (KEY_W), value 1
Event: time 1490184762.734733, -------------- SYN_REPORT ------------
Event: time 1490184762.983185, type 1 (EV_KEY), code 17 (KEY_W), value 0
Event: time 1490184762.983185, -------------- SYN_REPORT ------------
Event: time 1490184763.508206, type 4 (EV_MSC), code 4 (MSC_SCAN), value 40400e
Event: time 1490184763.508206, type 1 (EV_KEY), code 14 (KEY_BACKSPACE), value 1
Event: time 1490184763.508206, -------------- SYN_REPORT ------------
Event: time 1490184763.753183, type 1 (EV_KEY), code 14 (KEY_BACKSPACE), value 0
Event: time 1490184763.753183, -------------- SYN_REPORT ------------
Event: time 1490184764.026059, type 4 (EV_MSC), code 4 (MSC_SCAN), value 40400b
Event: time 1490184764.026059, type 1 (EV_KEY), code 11 (KEY_0), value 1
Event: time 1490184764.026059, -------------- SYN_REPORT ------------
Event: time 1490184764.273206, type 1 (EV_KEY), code 11 (KEY_0), value 0
Event: time 1490184764.273206, -------------- SYN_REPORT ------------



Now we can work with keybinder
Code:
keybinder /dev/input/eventX
X depends on the event number of your IR receiver!!!
You got the number by evtest.



Feel free to apply my config or create your own.
Code:
cat <<EOF >/etc/keybinder.conf
24,mpc volume +10   # Set the volume +10
23,mpc volume -10   # Reduce the volume -10
16,mpc prev         # Play previous track
17,mpc next         # Play next track
13,mpc toggle       # Play/Pause playback
69,mpc random       # De-/Activate random playback
77,shutdown -h now  # Shutdown the Pine64
EOF

[Image: ir_remote_controlwkus1.png]



Start keybinder automatically on boot.
Code:
(crontab -l ; echo "@reboot /usr/bin/screen -dmS keybinder /usr/local/bin/keybinder /dev/input/eventX")| crontab -
X depends on the event number of your IR receiver!!!




» My own setup

[Image: img_20170312_101912a4uj7.jpg] [Image: img_20170311_1211430aubd.jpg]  [Image: img_20170311_164216hwux7.jpg] [Image: img_20170311_212653b3uyo.jpg] [Image: img_20170311_212802wauce.jpg]
[Image: img_20170311_192506etu6v.jpg] [Image: img_20170312_1337249cu2d.jpg]


Have fun with it Smile


Best regards
Julian