I ordered my device around the 26th. Should I expect to see it during this batch? I've yet to receive a tracing number or anything even remotely resembling an update on the order.

Thanks shelldweller,
this board has been added to the assembly slarm64_build_kit

kernel
slarm64-current-aarch64-server-sopine-5.13.5-build-20210727.img.zst
slarm64-current-aarch64-server-sopine-5.13.5-build-20210727.img.zst.sha256

Hi, I can see usb device in the manage disks utility, but I can't access the device through dolphin. I can manually mount & access through console. 
Has anyone had this problem? Any suggestions appreciated. Thanks, straightwalker
SOLVED
more or less. The Disks utility recognizes a hot plugged usb and allows mounting and/or unmounting and offers options that can be edited.
If the drive is in when the PBP is booted, the Disk utility will mount it in /ROOT/mnt/usbname. If the drive is put in after the boot, the Disk utility mounts it in /ROOT/media/usrname/usbname (or maybe it has a "/run" in that path, I don't remember). In any case, Disks lists the path to the mounted usb drive, and you can access the contents using Dolphin (by beginning the path with ROOT).
There is probably a way to automate this, or make it less manual, but I couldn't figure it out. At least, you can access any drive you put in. If you are using the same usb drive each time (and you get the settings right), the process is automatic. It seems that you have to set up options for each new drive that you use.
I'm sure others can explain better ways. But it does work, even though an added device never appears on the Dolphin sidebar.

They very laggy USB-C port is a big issue for charging the phone (especially on a bicycle with dynamo or solar panel).

Is there any chance to solder a new port onto the phones pcb?
If yes, which parts would I need to buy?

https://www.ebay.com/sch/i.html?_from=R4...r&_sacat=0


Soldering I guess is somehow like this:
https://www.youtube.com/watch?v=e6TMxctCcxU

Any detailed walk-trough on how to open the phone and how to replace the port?

Cold I instead charge via pogo-pins with a 3d-printed custom case?

Hello

i am using Lenovo ThinkPad 40A9 dock for my daily driver Lenovo E595. I thought to test it with pinebook, but result was mixed, as i've described here.

Today i've returned to seek for rootcause, and what i came with, was this message

Jul 21 02:21:04 pinebook kernel: cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2

when dock was plugged.
I've started to connecting dots: firmware was present in /usr/lib/firmware, but yet somehow it was invisible for rockchipdrm module. After some tinkering, i've modified a file

[root@pinebook etc]# sdiff -s mkinitcpio.conf mkinitcpio.conf_20210730
FILES=(/usr/lib/firmware/rockchip/dptx.bin)       | FILES=()

regenerated my initrd and verified that file is actually included before rootfs gets mounted, so exactly when it's needed.
After reboot, somewhat success - no errors about missing firmware ,yet no image after connecting to dock, despite both plugs orientations

kernel says

[  26.816477] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] Not connected. Disabling cdn

Is there anything else that i can do/ mess with/ try? i really am into docking Pinebook to my existing dock, as i have already nicely set up my desk and buying another "maybye compatible one" is missing my point.

my kernel: 5.13.4-1-MANJARO-ARM, vanilla from repo (yet i don't see a problem to recompile if needed, Gentoo fan here ;d)

I have Manjaro on my Pinebook pro and have no luck with night light mode. I tried following all discussions in the forums here and on internet. I tried installing gnome with gdm in majaro. Also tried redshift. But nothing worked.

I appreciate, if anyone can help by providing exact steps to enable night mode?


thanks,

I ordered a pinephone earlier this month and knew it might take some time for the phone to arrive. I was ok with that. I did decide to use DHL for delivery - a little more expensive but from what I was reading worth the extra money for shipment to the USA. On June 23rd, I received a notice that that a tracking number was created but the package was not picked up. This status stayed this way until the 26th when I reached out to Pine's shipping department. I was told "they have issue of processing and will update us the status around July 28th". After reaching out to DHL, they had no record of my tracking number but asked me to get the pickup or dropoff confirmation number provided by DHL. After multiple attempts after multiple days, pine has yet to provide this number to assure that DHL had actually picked up the phone. On July 28th they finally admitted that DHL picked up the pallet that my package was on, and the palate went to New Zealand and I am to wait through August 2nd before there is any further status. They offered a different tracking number showing the package going to NZ but have yet to offer the original pickup of droppoff confirmation number so I could work with DHL. DHL is still denying they ever picked up my package and will refuse to work with me without the pickup or dropoff confirmation number given to Pine64 when they picked up the pallet with my package on it.

I paid extra for this???? Pine has no interest in helping me right this mistake. If anyone is reading this from Pine64, please assist me in getting my phone in a reasonable amount of time!!!! I am happy to give my tracking number and order number if requested.

PLEASE!

Thanks.

As it mentions above this was a bit of an adventure. Just a bit of background. I bought my first Rock64 4g a couple of years ago to run as a home automation server. It was pre RPI4 so was way ahead in it's league at the time.I installed Armbian and with the relevant OS updates it's been running 24/7 ever since without any problems.

Fast forward to today. I noticed over the last year interest was waning in this board. Community posts are down to a trickle. I managed to pick up five of these boards for a fraction of what I paid for my original purchase. Now that I needed an Android TV box I decided to give it a go and install Android 8.1 TV on an SD card as per the recommended install image https://files.pine64.org/os/ROCK64/andro...oot.img.xz . The following is how I went about it and the results that followed

I downloaded the image mentioned above.Instead of the recommended install procedure I extracted the downloaded image with Win7zip https://www.7-zip.org/download.html . It's a very stable file extraction utility and the extraction process went fine. I then used Win32 Disk Image https://win32diskimager.download/ to write the extracted image to the SD card. Once that was complete I popped the SD card into the Rock64 and powered it up and to my surprise after 10 minutes the Rock64 splash screen appeared followed shortly after by it the Android splash and finally the Actual Android GUI.

After configuring the usual locales and connecting to wired LAN via the ethernet port and attaching a mouse/keyboard I was ready to go. I started to notice that wired LAN was dropping packets and disconnecting and reconnectiing.After a quick search here with suggestions of changing to shorter ethernet cables, two pair cable instead of four to resolve Gigabit Ethernet resolution issues nothing worked. Of course I was lucky enough to have four other boards to swap in. Well I've discovered that two of the five boards have faulty ethernet connectors and one of them also faulty USB2 connectors. Also it looks like USB2 to external DAC is out owing to cracks and pops during playback.This behaviour is similar to that on the RPI3+ owing to conflict between ethernet and USB2 bus. Obviously I can't confirm this for sure on the Rock64 but I know I am experiencing this.

I finally settled on one board that boots with no issues.Full Gigabit ethernet, USB2 ports working fine. My next problem was low sound. I tried every possible option for sound out including USB to external DAC. You could barely hear a thing. Finally I stumbled on the ADB option to control sound output. I enabled the Developer option on the Rock64. I installed ADB for Linux on a Linux machine and from the Linux machine issued the adb connect command to connect both machines together. I finally found the command to increase the Rock64 built in audio output to maximum adb shell media volume --show --stream 3 --set 15 .I now had perfect audio via HDMI to an amp via coxial or in my case coaxial from TV to external DAC and analogue to the amplifier. Sound is now perfect.

This install did take a little longer than expected. What I have learnt is that it appears quite a lot of those Rock64 boards may have been faulty from day one and only I had spare boards to experiment with I'd never got Android working on my Rock64. I just did a basic outline here.If anyone planning on doing an Android install on the Rock64 has any questions ask away.

Hi guys,

I'm running Manjaro on my PBP. Loving the device so far. They keyboard is amazing (backlight would have been nice, but I'm not gonna niggle about a $200 laptop) and the screen is pretty WOW.

I'm able to play 1080p30 video in youtube, but 1080p60 video turns into 1080p12 (or thereabouts — tons of dropped frames) in youtube, mpv, and vlc.

I'm running the latest Manjaro.

Has anyone managed to figure out 60fps 1080 video? I believe none of the players I've tried support hardware decoding. Is there any trick to this, or is it just a limitation of the FLOSS video drivers?

Thanks!

Hello!

I received my Pinecil in the mail yesterday.

When turning it on for the first time the screen flashed a message No USB-PD IC detected.



When powered from DC5525 the Pinecil works, but it emits strange crackling noises from the rear end where the power connectors are located.

Has anyone here experienced anything similar?

Thank you in advance,
JS