I believe the enable line of the LPW5210B5F  in the USB +5 supply should have been wired back to VBUSEN on the AXP803. The way it is wired now, if you hit the power off button it leaves the +5V on when on battery supply. This will drain the battery while the unit is off. If enable had been wired to VBUSEN the AXP803 would have been able to shut off the +5V supply when powering off.  This should be a programmable choice since when on AC power you want to leave the USB +5V on so that a mouse/keyboard can be used to wake the device up.

Hi,
I've been on summer holidays and meanwhile i received my Huion Digital drawing tablet.
On Ubuntu 16.04 it is detected and ready to run in no more than 2-3 minutes.
I tried to install given DEB package from Digimend on Pine64 ( Digimend GitHub ) and also to make manual install from source with SU rights. For this procedure it is needed kernel version 6 and upper as I could understand from their description how to install drivers
In both ways drivers looks like are installed properly (no error reported) but device is still not detected.

When I try to list if device it gives only ID with numbers of it:

Here is list of lsusb -v and what I get for this device:
Bus 003 Device 002: ID 256c:006e  
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x256c 
  idProduct          0x006e 
  bcdDevice            0.00
  iManufacturer           5 
  iProduct                6 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           59
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      2 Mouse
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     177
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               2
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      2 Mouse
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     161
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               2

Looks like something I am missing so if anyone can help making proper installation , good.

My plans is to complete circle and to make Pine64 drawing machine for my daughter using GIMP and TuxPaint as basic drawing programs and Huion tablet for drawing device.

Waiting for your help.
Regards,

Will this Lcd work on Pine64 2GB board ,since the store seems unable to get more in stock ?
see link below

https://www.amazon.com/interface-Capacitive-Raspberry-Pi-BeagleBone/dp/B015E7O9C8/ref=pd_sim_sbs_147_4?ie=UTF8&dpID=51HSxlXVi-L&dpSrc=sims&preST=_AC_UL160_SR160%2C160_&psc=1&refRID=352V35WFXDFDPR2QW427

Does anyone have a working sys_config.fex? None of the ones in the downloads seems to be for the Pine64. Most are for the Allwinner dev boards. The closest one I have will come up to an Android command prompt but I can't get HDMI going.

I am trying to put together a working Android build and then I will push it up to www.gitlabs.com (not github, gitlabs accepts large repos).

Once we get a working build into git it will be possible for people to start fixing things. But without being able to rebuild the OS nobody can make any fixes.

I finally got to experience my Pine64+ yesterday with Android built in. Evrything works fine until I just can't download any apps in Google Play Store. Can somebody help me? Is it a bug or is it me just unplugging the usb cord whenever I've done using without properly turn it off?

Hi everyone, this is my first post and it is a question.

What is the schematics on this button?

https://shop.pine64.com/collections/acce...off-switch

I want a power button but this is to small for what I want so I need to know this ones internal workings. I am going to get a big user friendly thumb sized button to place on a wooden box.

I am trying some things from the RHEL Performance Tuning Guide on the Pine atm, especially interested in assigning IRQ to different CPUs (like mmc/sdcard and GbE for example) instead of having them all on CPU0, but also other things...

https://access.redhat.com/documentation/...ing_Guide/

So if someone has already tried different things I would be interested to hear about your results and experiences, or just start tweaking as well... maybe we can find some
tweaks that the Pine can benefit from...

OK - so I booted up one of my Pine64+ 2GB boards into Android Lollipop 5.1.1 for LCD touchpanel...

Wifi works - tick
Bluetooth starts - tick
Ethernet works - tick
LCD Panel+touch works - tick
Battery charges - tick
Battery powers pine - UNTICK!

What gives?

I watched its progress charging up an 8000 mAh battery - once charged I pulled the DC in out and it shut off!

Battery definitely connected to the 3 pin PH connector.  Obviously gets a charge through to the battery - why can't I power my pine with the battery?  What's the point in charging it if it won't power the board?  What am I doing wrong?

Hi all,

I've gotten the Pine64 media board up and running with the latest image and all seems to be working well aside from being unable to power on the device with the remote control and that Play store issue (though the work-around of trying to add the Google account gets me around that).  I've installed Kodi on it and it's an amazing app! 

I've got a USB drive connected to the Pine and am able to play all files with no issues.  However, I'd like to be able to add/delete files to the USB drive from my Windows machine - is that possible?  Meaning, can I get the USB drive that's connected to the Pine to show up as a network share on my Windows machine since they're all on the same network?  

I've looked online and found the app "Files drag and drop" but though it says it detects the Pine, A) it doesn't display a list of files on the drive, and B) even though I try to copy a test file, I get authentication errors.

Would anyone have any other suggestions?

Hello all,

I am quite a bit frustrated. Just received my Pine64 and began to study how to put it to work. Got two different MicroSD card (16GB and 64GB) and downloaded the images of Android OS and Remix OS. But when I went to burn the images, the things started to get out of the tracks.
In both cards, and using different OS, I was not able to burn any of the images until now (after two days trying). In all cases the error that occurs is related to the size of the image, that does not match with the size of the card. I searched for help on the web and I found that it is possible to shrink the image file. But I must confess that its not something simple for newbies and for windows users, that it's my case. 
Can anyone help me with this issue? 

Sincerely

Hbtr