Hi all,
I've just received the PineTime.
I thought is was a 'stand alone' watch and only now I'm realizing that I need to set it using an APP.
I read some infos but I've some problems to understand wich is the right APP I need to install on my desktop (Ubuntu LTS 20.04)

And if I can install an APP on my Vollaphone22 (VollaOS or Ubuntu Touch).

Would anyone be so kind as to give me some suggestions?
Thanks in advance

Marco (Italy)

Hi,

I have bought 2 Pine A64+ from Ibood last week.
One of the boards has some trouble with the ethernet connection.

Everything worked just fine, but after 1 day, the network connection was dropped and my board was not accessible anymore.

This is my setup:
Serial number : 410640172333
OS : DietPi
Installed software : Webmin, docker, docker-compose

I have tried a new microsd card with a fresh installation of DietPi, but at the installation the system is complaining that there is no internet connection.
I also switched the microsd card with the one that works on the other board.
I have tried a different switch, network cabel, power supply, DHCP / static ip.
Switched the network speed to 100.
But nothing did the trick.

My network contoller (Unifi) says there is a device connected, but the device is not accesible

Ibood says i have to take contact by this forum.

So my question is, what can i do to make everything work again.

Kind regards,

Jelle

I have a 2022 Pinebook Pro. I used dd to write an OS image to an SD card, in my case NetBSD which I sourced from here:

http://nycdn.netbsd.org/pub/arm/netbsd-9/

Last time I ran NetBSD was years ago, on a different architecture. When I reboot the power led blinks and then nothing happens. Maybe I'm missing something obvious.

After searching I found this post:

https://forum.pine64.org/showthread.php?...#pid113987

To wit:

Quote:The version of Manjaru that comes pre-installed on the 2022 Pinebooks Pro, includes a U-boot that does not allow booting from micro-SD card.

The ways to resolve this are
1) replace the U-boot on the eMMC with a different one, or possibly Tow-boot
2) wipe out the eMMC and install a different operating system on it.
3) install Tow-boot to SPI ROM (I do not actually recommend this, but it can be done, apparently).
4) disable the eMMC 

Hi there, I have a NAS shared with NFS. That works for my rock64 and 2 other computers in the network. But now I updated to 10.0.3. Now I can't get my NFS shares to work. I have put ubuntu on my rock and my shares work again. The two other computers have no problems with the NFS shares. So only Libreelec 10.0.3 is having a problem getting connected to my NAS using NFS. (There is network).

So I hope someone here can help.
Pit

Hi,

Got a screen issues, that comes up in different ways.

Before my Pinebook Pro boots the OS, if I tilt the screen I sometimes get a bunch of garbled characters on the screen and the screen goes black (but still on).

Other times it'll boot normally and if I so much as touch the laptop it'll cut out.

Yet sometimes (and this strange), it'll boot normally, I can tilt the screen, move the laptop etc and nothing will go wrong.

Any ideas where to begin here? Some loose connector?

Thanks,

Twig

Hi guys!

So I saw this entry in the blog:

Quote:[*]Starting with kernel 5.19 PinePhone Pro’s cameras will work with Megapixels

Quote:Linux danctnix 6.0.2-3-danctnix #1 SMP PREEMPT_DYNAMIC Sat Oct 22 03:23:48 UTC 2022 aarch64 GNU/Linux

Quote:pdate_state()
initializing camera
MPDevice: MEDIA_IOC_SETUP_LINK error 22, Invalid argument
MPDevice: MEDIA_IOC_SETUP_LINK error 22, Invalid argument
MPCamera: VIDIOC_SUBDEV_S_FRAME_INTERVAL error 25, Inappropriate ioctl for device
Failed to get display configuration: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
Initialized OpenGL ES 3.1
MPCamera: VIDIOC_STREAMON error 67, Link has been severed
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
Segmentation fault (core dumped)

Hi,

I am unable to output any sound from jack. I tried different headphones, including Samsung smartphone earpiece (told to be compatible, according to a pine64 forum).
Tried dozens of tips and tricks found here (with alsa, amixer, alsamixer, pulseaudio), but no success.

Finally, i traced dmesg during headphone plug-in and plug-out, and what I found was intriging :

This is what I get when plugging IN :

[ 3517.655643] jack: irq plug-out
[ 3517.663413] jack: irq plug-in
[ 3517.696086] jack: irq plug-out
[ 3517.762223] jack: plug-out reported

=> so the headphone is reported being plugged out, when I plug it in.

This is what I get when plugging OUT :

[ 3532.479203] jack: irq plug-in
[ 3532.487846] jack: irq plug-out
[ 3532.496029] jack: irq plug-in

=> the headphone is reported being plugged in when I plug it out.

Strange... Can this be the source of my problem ? 


More information :

root@DietPi:~# aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: sun50ia64audio [sun50i-a64-audio], device 0: 1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0 [1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sun9ihdmi [sun9i-hdmi], device 0: SUN9I-HDMI PCM i2s-hifi-0 [SUN9I-HDMI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


Any idea ?

Thanks

I was trying setup the online account for Google so that I could access my address book, email and calendar but the keyboard doesn't work for typing in the user information. I tried copy and paste but then the Google login tells me "This browser or app may not be secure". This works on my desktop and was working before on the PinePhone Pro. I'm using Manjaro BTW.

Anyone have a workaround?

I've purchased a PinePhone Pro Explorer recently. 
Several places scattered across the web are discussing if the phone is really open source.
What I'm looking for is some clarity as to the claim of "Open Source" to my device.

Just tried out the LoRa backplane with this driver: https://codeberg.org/JF002/pinedio-lora-driver

To get it working, I had to change /dev/i2c-2 to /dev/i2c-3 in apps/pinephone-communicator/main.cpp

The pinephone-communicator connected to the LoRa module successfully and I could send messages. Unfortunately, I couldn't test receiving, as I don't have a second device.