I wanted to know if it was possible to develop a Rock64 Portable Console, with a controller inside of it like this:

Hey 

I wanted to suggest a design change for the next generation:

only screws on the bottom nothing to click in

Sorry if this has been posted in other threads.  I looked but I didn't find anything recent.  I am looking at possibly purchasing this for Android TV.  I was wondering using the stock android image if Netflix works, and if so will it work in 4k?  Also has anyone been able to use Youtube TV with it?

Thanks

Hey,

just bought this sound POT (https://www.pine64.org/?product=pine64-s...-pot-board) and unfortunatelly I am unable to detect. Tried Volumio (latest and the 2017-05-11 image), Tried Base Xenial image without any success.

Apparently, the board has ES9023 chip, but I don't even know whether the board was detected or not. aplay -l does not list it, any other commands how to detect it, are unknown to me.

If you have any directions, where to look at, please let me know. I am trying to build simple music box (like Volumio) with this hardware.

Thank you in advance...

Hi all,

I'm just testing a few linux builds on my new rock64.

The ayufan all have rock64/rock64 as default user but I want to login as root. How can I do this?

Many thanks

Good news everyone. We got a stall at FOSDEM 2018 which is taking place on the 3rd and 4th of February 2018 in Brussels.
If you are already attending or live in the vicinity of the AW building. We will be showing off existing and upcoming products. And yes, there will be beer and swag ...

Did someone manage to disable Serial Console to free up the UART for other another purpose?

I am a new member and want to change OS's on my Pine64 LTS. I have Android 6.0 flashed to my eMMC module and want to update to Android 7.0 that I have loaded onto a micro SD card from the Pine 64 Installer GitHub webpage. Is this possible to do and what would be the procedure?

The 6.0 version was my first install, and the GitHub flash from the micro SD accommodated the whole transfer process to the eMMC module automatically.

Last item...I am still experimenting with all the possibilities and am wondering if there are any downsides to this update? Android 6.0 is working perfectly.

Hi All,

I'm having issues getting the AXP803 to complete its BC Detection routine. Basically it hangs because the BC_status bit in Register 2C never changes from 1 to 0, indicating the detection is complete.

On the Pine A64, the USB data connections (D+ and D-) are connected to both the AXP803 (DP and DM) and the A64 (USB0). I'm concerned that the connections to the A64 is affecting the BC Detection routine.

Do either the AXP803 or A64 need to be configured a certain way while running this routine? There are a lot of control registers in the AXP803, but the documentation isn't very clear.

Any help would be greatly appreciated.

Thanks,

Phillip

OK, I suppose I have a setting problem somewhere, but I don't see it. My Pinebook running Ubuntu (up to date) is doing something weird with file timestamps. I noticed it when copying files to and from another computer running Win10.

Here are the symptoms:

I created a text file on my PB, saved it, and copied it to a USB drive. PB tells me the timestamp on the USB copy matches the file on the PB, and both are what you would expect for a file just created and saved - close to PB system time reported. Then I moved the thumb drive to my HP and inspected the file. Windows Explorer tells me the timestamp is 8 hours into the future! Then I edited the file and saved it under another name on the HP and copied back to the thumb drive. Both the copy on my HP and the USB drive agree with each other and properly reflect system clock. I move the drive back to the PB. Now PB tells me the new file reads 8 hours earlier than its system clock. System clocks on both machines report the same time and date.

Another clue to what is going on is any file edited on the PB and copied to a USB drive will cause my Win10 machine to claim there is a problem with the drive and wants me to authorize a scan to repair. If I tell it to do so, though it reports no problem found, something changes as I can remove and re-insert the drive and it doesn't cause a repeat of the warning - unless the PB modifies the file.

Is this a bug in Ubuntu? Is there some setting somewhere in Ubuntu that I need to change?