Hello,

As i have some bad experiences with bleeding edge sbc boards, i prefer asking a few things before ordering 


My utilization of the quartz would be pretty simple. I will use the rockpro64 premium aluminium case, with a nvme ssd into the u2 port to store some music files, and use it only to be a mpd music player with usb audio output. I would use a very light manjaro linux without graphical interface.

Also i didn't find in the documentation if the board support wake one lan. I want to use an app like duorem to power on / off the device remotely.


Thank you

Hello again!



Another dumb question!



Given my phone tends to get a lot of sun exposure, I've noticed plastic parts have become brittle.



I'm not to fussed by it given I can by spare parts and support Pine64's endeavors but is this a common experience? If so, perhaps this is something that can be taken on board when manufacturing future spare parts and/or the Pinephone Pro (obviously subject to, among other things, cost considerations).



Thanks again!

Hello,

Two dumb questions!

1. Is the screen and digitizer a combined unit or are they separate?

2. Does (1) in the document below do anything other than protect the screen?
https://files.pine64.org/doc/datasheet/p...%201.0.pdf

I'm asking this because my Braveheart has just started playing up. I have difficulty touching some parts on the lower part of the screen, namely the area where the '6', 'y', 'h' and 'n' keys are located. The fault is intermittent.

If the digitizer is separate and/or (1) handles touch input, I was hoping to disassemble the phone and try re-seat either of them before ordering a replacement screen.

Many thanks in advance!

Just updated everything to the newest packages, mouse worked fine before, now it does not work after update and reboot. i have booted twice, unplugged, plugged back, mouse does not work. only track pad works. this ius becoming extremely annoying  and frustrating, how do i get the mouse working again? Anyone know?

(11-10-2021, 04:16 PM)WEF Wrote: Just updated everything to the newest packages, mouse worked fine before, now it does not work after update and reboot. i have booted twice, unplugged, plugged back, mouse does not work. only track pad works. this ius becoming extremely annoying  and frustrating, how do i get the mouse working again? Anyone know?

Whom do I contact at the PinePhone Store for a phone which was lost during shipping by DHL?

Thank you

Has anyone managed to get any Amiga Emulator functioning outside of waydroid or anbox?
.
I suppose I could work through waydroid if needed, but I figured it wouldn't hurt to ask if anyone has beaten me to this.

Generally on these forums one can go to your CP or one's account and  view the posts and threads one has submitted to a discussion. Does this forum support that? Yesterday morning I posted a topic on my PinePhone which was shipped but now has been lost for over a week and I stated in this post until DHL or PinePhone resolves this issue no one should purchase anymore phones. This issue has been going on for many many months and is not resolved. I cannot find this post and appears to have been deleted.

Is mobian updating the 5.10 kernel with new patches or do we need to update/upgrade manually?
I have a bookworm install

1. Keep in mind that PinePhone components were originally not intended to use in mobile phones, so set your expectations accordingly.
2. PinePhone software has not reached even a "release candidate" level, so set your expectations accordingly.
3. The following reflects my experience. Your mileage may vary, so do not blame me if something goes wrong.
4. The PinePhone preloaded Plasma Mobile (PlaMo) operating system may be outdated, so it is good idea to do a fresh start. All information how to install is listed here.
5. Manjaro provides different PlaMo Development Pinephone Images to install. There are Development Pinephone unstable images which are based on KDE unstable branch and Plasma-Mobile "daily build" unstable images which are based on KDE stable branch. However - there could be from time to time several problems with these images (eg non-booting or something broken etc), so it is good idea to test them installing to the sd card.
6. At certain intervals Manjaro team is releasing Beta releases. If you want something that is close to "stable" to install to the eMMC, then I'd recommend to use these. The latest beta is Release Beta 14 and is located here. The announcement is here. Be prepared that for beta the updates are arriving less frequently as it has it's own updates channel.
7. While PlaMo software manager Discover has great potential, it seems that it is not ready yet. It does not list all software and from time to time may fail in some extent in software update. Instead Discover I'd recommend Manjaro commandline tool pacman. So for updates run in Terminal:

Hello!

I had recently purchased the dev kit package for the PineTime watch (one unsealed, one sealed) and have been having a lot of fun playing around with it. It's a new area for me and I've definitely learned a good deal from it!

With that being said, I want to stress that I'm by no means an expert with things like Bluetooth. I understand how it works and how to interact with it via code, but I couldn't tell you all the truly intricate details of it.

For reference, any tests or scenarios I mention below are using InfiniTime 1.6 with a custom app I had put on it to act as a simple remote control. I based the structure of the app off of the Music app's play/pause button implementation since that was essentially what I needed, just for a different use case that connects to my PC. It has been working perfectly fine and doing exactly what I expected in terms of functionality.

However, the one issue I've had is in regards to the Bluetooth cutting out more than I would've expected it to. There are times where I'm in direct line-of-sight of the adapter for my PC, standing approximately 12 - 15 or so feet from it, and it would start to get more latency and then typically disconnect. It would then reconnect intermittently until I got closer to the adapter, at which point it would be fine again. This would also happen if I was right below the adapter in my kitchen (maybe 7 or so feet, with only a few 2x4s separating the top of the kitchen from the floor above).

So, I tried the following to diagnose it:

• Connected to my phone instead of the PC adapter. Had the same results
  
• Tried a different PC adapter. Same results
  
• Tried using both the sealed and unsealed watches in the same situations described above. Had the same results for both in all cases
  

• Is wearing the watch supposed to affect connectivity? Like I said above, I understand that our bodies block signal, but it seems kind of bizarre that wearing the watch - one of the main functions of it - would decrease connectivity by such a noticeable amount, no?
  
• Does it really make sense that my slight bending of the antenna would've increased performance to such a noticeable degree?
  
• Is there just something else here that I'm overlooking, or other factors that are just making this a red herring?