Xenial Mate (Pinebook) 20170505 (MD5: 93bcaf2d33aabf34691ec7b94ead50d3)

Release Notes:
1. This build is base on 0.4.0: jenkins-linux-build-pine-a64-44
2. Added packages: aisleriot, gnomine, gnome-sudoku, emacs, nano, vim, geany, scratch, gcc, htop, smplayer, smtube, mplayer, libvdpau, gimp
3. Fixed left USB port as host
4. Login Credential
Username: pine64
Password: pine64

Known Issues:
1. HDMI output not working yet.
2. Auto detect headphone not working yet.  Currently the audio will output to both speaker and headphone.

Is the SPI flash programmed at the factory with necessary boot code, or is that just there for us to use in our own applications? It looks like the PINE64 has an EMMC instead of a SPI flash and Linux-SunXI wiki says SPI-flash has a lower boot priority than SD-Card, so I'm assuming it's presently unused.

If it's available for us to use without breaking the boot process, we're thinking we might store device specific calibration values there rather than on the SD-Card. Has anyone played around with the SPI flash yet? From the above SunXI page I get the feeling that drives might not yet be in the kernel.

I saw a article regarding google HOME and PI: https://www.engadget.com/amp/2017/05/04/...ompetitor/

 Has anyone tried doing it on pine64 board? If so, i would like to know. Thanks!

Does the production Pinebook include a BMA223 accelerometer on the onboard I2C bus, as mentioned on the linux-sunxi list back in February?

if so, anyone done anything fun with it?

curious what it would be used for in a machine w/ no spinning disks 

Any guesses how long we'd be waiting if we signed up now?

I've found some disagreement between the Pinouts document (v1.0) and the schematics  for the SOPINE (v0.9) and the SOPINE Baseboard (v0.9). Usually the two Schematics agree, but not always. Some of these errors are quite serious and I suspect the Pinouts was an early document that wasn't fully updated after the final schematic materialized.

I did not list times where the Schematics called a pin "PC3" and the pinout called it "PC3_FUNCTION". But I did list times where it's pretty clear the same function is just being called by different names (ex LCD-PWM vs PL10-S_PWM)

Since I couldn't figure out how to do table layout on this forum, here's a Google Sheet with the discrepancies:
SOPINE Pin Descrepencies

For those who hate google, I've also attached screenshots.
   

   

Hi,

 I have to attach some custom LCDs with Pine64+ Board.

Please guide me how to do it. Where to change driver details.

Regards,

Hi,
I'm working on Ubuntu Xenial 16.04. I've installed Firefox 52.0.2 32bit, and it Worked fine.
However, for HTML5, I've made a test and he got me I haven't support for x264, x265 and dolby audio formats.

Since NetFlix has enabled streaming through HTML5 for Linux, even for Firefox, I want to know how can I enable this formats.

I've installed gstreamer1, x264 and other stuff, but nothing for gstreamer1-plugins-ffmpeg. Does I need to reinstall firefox, after I've installed gstreamer1 and x264?

I had installed Android 6.0 running properly but yesterday I changed the TV and did not show nothing on TV, I put the Pine64 where I was continuing, with the same problem. I have reinstalled Android using the app and it still does not work.

I just started playing with my Pine64 again, and I'm looking at including its temperature information in my home-grown graphing system. I found that it seems like mostly valid data in the /sys/class/thermal/thermal_zone0/temp file, but I noticed that it has zero digits of precision. It's currently reporting 36C idling on my desk, and if I run "stress --cpu 4" for a few seconds, it shoots up to about 80C within 10 seconds, so I can assume it's measuring real data.

Is integer precision the best I'm going to get? My RPis are reporting to about 3 decimals of precision. It's not a big deal, but an integer graph is pretty boring.