Just wondered if anyone has got the display going from MicroPython.

So far I've spent most of my time on PineTime hacking together a bootloader robust enough to allow me to stick the back on (albeit with something I could undo in an emergency). Nothing too fancy... just getting the bootloader and app cooperate to turn the user button into a watchdog enforced long press reset button.

I've been using MicroPython with a BLE REPL as a test payload and the next step is to get something on the display so I just wondered if someone is ahead of me there and already has this going in Python? Once the back is on I'd like to at least see the time!

Does anyone know if a PCI soundcard (more specifically the ASUS Xonar DX) will be recognized and work soundcard on the RckPro64?

The speakers in the pbp could use, well, a subwoofer maybe.  I don't know where you'd put one.  To look at the picture they look like ordinary small speakers like you might find in a radio.  Recent advances like neodymium magnets have made big sound from a small space possible, but they're best used in some environment designed for them, not just stuck in there.  Some plastic or fiberglass housing, I remember it's important that sound waves coming off the front of the speaker not reach the back and cause interference and partial cancellation.  A cardboard box is better than nothing with bigger speakers.  There is software like qspeakers for trying to optimize designs, not that I've tried it.

What about cell phone speakers?  They aren't very big but some can belt out those ringtones, which are often music clips.  Seems like there must be some surplus ones around since there are millions of cell phones.

 (January 18, 2019)

   So Brave Heart Edition of the Pine phone started shipping yesterday.

      Have  'YOU'   received Your shipping notice yet ?

    I was in the Crowd waiting when they opened the door on this bout of orders.

     I guess the store is probably closed for the weekend (?)  I hope to hear something soon.

January 25, 2020

When I attempt to track my Brave Heart :

It still has the same old statement that it has "arrived in Switzerland" !

5 Days and not even an update !

GRRrrrr Wish it was DHL

Asendia SUX

I'm trying to build a couple of kernel modules for the Pinebook Pro but haven't been able to find the kernel headers.  Are there debs of these anywhere?

(I suspect this will be fixed with the mainline kernel work moving to 5.x but I haven't yet found the specific 4.4.207 fork used on the Pinebook Pro.)

I'm using the default linux image and have updated everything.

After a while of use, the wifi stops working, requiring me to either `ifconfig wlan0 up` or, if that doesn't work, reboot the machine.

If I have it plugged into AC power with the supplied power adapter, I only get maybe 10 minutes of watching fullscreen 720p youtube before the wifi goes out.

If it's on battery, I get longer, maybe a half hour or more before it fails.

I checked the syslog and I see a bunch of wifi-related errors when this happens - lots of assert failures, mismatched lengths etc, then finally a note saying the chip has hanged and it shuts off the wifi.

Does this happen to anyone else? Is this the expected behavior or did I get a bad one?

A snippet from my syslog when this happened:

Hi PineTime Fans: I have modified OpenOCD to run on Raspberry Pi using the faster SPI interface (31 MHz!) instead of the old GPIO Bit Banging.  If this works, we should be able to flash AND debug PineTime firmware with VSCode on Raspberry Pi!

But I need your help to test this modified version of OpenOCD.  (Test instructions are in the article below)  If it's tested OK, I'll publish the steps to debug PineTime firmware on VSCode.  Please lemme know if it works. Thanks! :-)


OpenOCD on Raspberry Pi: Better with SWD on SPI

The steps below worked for me in getting Amazon Prime Video working in firefox. I'm assuming they'll also enable Netflix, but who knows. It's possible some subset of these instructions is enough, but I'm just going to spew out everything I did before it started working. If someone else wants to figure out what subset of these steps is needed to get it working, be my guest.

I've basically borrowed liberally from this how-to:
https://www.reddit.com/r/firefox/comment...plugin_to/


..and borrowed values as needed from the widevine files on my Windows desktop machine. Not all of this may be necessary. e.g., Rather than put in the incorrect version number for widevine (I have no idea what version is on my system), I'm just using 0. Likewise, x-cdm-codecs is taken from my windows machine so it could be completely wrong for the platform..

Steps:

1. Make sure widevine is up-to-date and working in chromium on your PBP, because we're going to 'borrow' those libs.
2. Figure out what your mozilla profile directory is (aboutupport, see "Profile Folder")
3. Open a terminal and change to that directory.
4. mkdir -p gmp-widevinecdm/0/ && cd gmp-widevinecdm/0/
5. cp /usr/lib/chromium-browser/libwidevinecdm* .
6. create a file called manifest.json, and fill it with:

{
    "name": "WidevineCdm",
    "description": "Widevine Content Decryption Module",
    "version": "0",
    "x-cdm-module-versions": "4",
    "x-cdm-interface-versions": "10",
    "x-cdm-host-versions": "10",
    "x-cdm-codecs": "vp8,vp9.0,avc1",
    "x-cdm-persistent-license-support": true
}

7. Open firefox, and open about:config. Create the following entries:

media.gmp-widevinecdm.version - string - "0"
media.gmp-widevinecdm.visible - bool - true
media.gmp-widevinecdm.enabled - bool - false

and then change the following already-existing entries:

media.eme.enabled - true
media.eme.encrypted-media-encryption-scheme.enabled - true


8. Open about:addons. You should now see an entry for Widevine. Click on the drop down on the right, and select Always enabled.

The kernel is compiled for aarch64 but all the os related software appears to be armhf (the 32bit instruction set on arm). Was this intentional?

Also, is there a way to switch all the software to use arm64?

Thanks

I shut my Pinebook Pro off a week or so ago,  (real busy working time right now, no time to play)
Went to power her back up this evening, as I've three days off,  and wanted to start playing,  and the battery is dead, dead, dead.

Is there a parasitic power drain when the machine is powered off?
If so,  is there any way to defeat it?


One of the main reasons for a PineBook pro for me is battery life.  I've got four different laptops, two phones, and it's a pita to keep them all 'topped up', so I'd like to be able to power it down, and not worry about the battery for a week, or so.


I've only drained the battery once,  and have re-charged it from ~40% once since getting it, if that matters. 
running the default oldstable debian.

Thanks. It's a great device, and I'm hoping to make it my 'daily driver' soon.