After repeated emails to Pine64, Kickstarter, and Backerkit with no sresponse except bot type emails I am considering legal action.  I pledged to a $89 package.  Received a tracking number that said the package had been delivered over a month ago and the shipping address for the tracking number was not MY address.

I am starting to think the whole thing is a scam.

Totally feed up!


Charles in AZ

   

Good morning from Rochester MN...

... this is my desk at the moment. SoC is a beautiful 40c with a sold 3v2 and fluctuating 4v86.

The 5v supply is a bit of a mystery. W/ usb receiver, fan, and LED lab running 4v86... with the fan and receiver unplugged 4v5-4v72 / short time after plugging the fan and receiver back in then 4v86 !

I'm using an older 2A PSU from my PI, so will report back when the new supply arrives.

marcus

Backer number #245. 7 weeks after the 4/28 CN tracking number was sent. Nothing received. The tracking numbers has show only up to 23rd of April. No response to my mails also.

I am currently investigating how the battery charger in the PMIC (AXP803) is supported by the software. Being a hardware guy I was working my way up from the bottom side of things, starting with the physical connection and the PMIC:

The battery seems to be connected to the PMIC via a load sensing (current sensing) shunt and the PMIC has a switch that connects the battery to the inputs of the voltage
regulators once certain conditions are met. There is also an input on the battery connector to attach a 10k NTC for monitoring the battery temperature. The PMIC contains a battery charger that charges the battery depending on what DC power source is available (USB/DC IN).

From the AXP803 Datasheet:

- Vbat charge target voltage = 4.2V typical
- Charge current can be set between 200 and 2800mA, 1200mA typical
- Trickle charge current is 10% of normal charge current

- There are two safety timers which can be programmed to limit regular/trickle charging after x minutes (480 min / 50min typical)
- Charging stops in CV mode if the normal charge current drops below 10% of the set charge current
- The NTC monitor has different trip points like cold fault, hot fault for operation and charging which can be programmed in the PMIC
- Battery isolation current is 40uA


- Turning on the PMIC happens by either applying USB/DC_IN or pushing the power button
- Turning off the PMIC happens by undervoltage lockout, fault condition, power button or software writes to a register
- The charger starts working once the voltage input from USB/DC_IN is between 4.1V and 7V

- Input to the regulators is automatically selected from Battery, DC_IN or USB
- USB/DC_IN are preferred over Battery
- If USB and DC_IN are not connected together, DC_IN is preferred over USB
- If USB/DC_IN drops below certain thresholds, Battery takes over
- Input can be controlled by registers

- The function of the charge LED can be controlled via registers

- The PMIC is connected to the A64 via a I2C interface

I have looked at the device tree file and it seems to contain some default setting for the PMIC (and the charger):

On receiving my battery today, I decided it was time to put the old cardboard case I made from the shipping box (great for initial testing) and move up to something with more space and stability.  Found my old Clear modem and decided it would work great.  Had to dremmel, sand, eyeball and tape but eventually I ended up with the following:

Due to not being able to find any right angle audio plugs I had to cut a hole for it to extend out of the case and back into where the speaker is housed.  After thinking about it I liked this idea as it allows me to still plug in headphones when I'm on the go.

I salvaged the old Clear antenna and used it instead of the provided one with the wifi/bt hat.  What do you know, I can now receive wifi from down the street.

Here are images of the other sides minus back as it is just a lot of clear info.  Will have to put a nice print out of something back there to finish out the mod.



Biggest problem I ran into is the 30 pin ribbon cable for the display was about an inch too short to have the display exactly centered so it is sitting lower then expected (and the black piece of tape covers the origonal slot the cable used).  After readjusting it several times everything fits and works.  

In the last pic you can see where I cut out part of the grill of what used to be the bottom of the modem so I can get easy access to the SD card for ease of changing.

Hope this gives some people ideas to work with.

I got my Pine from the official shop, it was to be shipped in Late May - June and I've been waiting since 5th of April..

102285870 this is my order number and I've seen that most of the orders that start with #102 has been already shipped..

This is not a complaint, but just FYI for anyone who wants to know. I've had zero issues with the Pine's USB ports.

According to my USB meter, I've seen the voltages of the USB 2 ports vary between 4.77 - 4.94V. Typically, 4.89 - 4.92V.

The amperage is 0.07 - 0.08A for the flash drives I've tested. 
For keyboard, mouse, or powered hard drive, it's 0.00A.
I don't have a working wifi dongle, yet...

Hi there,

Is it possible to configure Pine's behavior when it's powered with a battery?
Mine board turns off a usb port (maybe it even turns off ethernet can't check it exactly without working mouse  ).

Dzmitry

Hello there,

I have a pine64 with 2Gb Ram.
Also have two images from the latest build for Remix OS and Debian OS
My SD card is class 10 with 64Gb.

using win32diskimager i uploaded the remix os image to the Sd card.
I took more or less 10 minutes for the system to boot into remix with very slow operation if i tried to make something like open google play or something.

The same appened in Debian.
I even tried to update the system to see if there was something needing update, but this task when it doesn't give error takes ages.

What can I do to correct this?
is it a Pine64 error?

David

Hi, I just mounted the IR receiver that came with the basic Pine Remote on my board. After reading the User Manual and checking the schematics, I know now that the A64 has a dedicated IR receiver block that does low level decoding. According to http://linux-sunxi.org/IR there was legacy support for that for the other sunxi SoCs as a keyboard device and there is a newer driver for 4.x Linux. I had a look at the devicetree entries and it's there with the correct base address... Is this something we could enable in the 3.10.x kernel ?