Hi, I found Birdie on the Mobian wiki, so I've created a PKGBUILD

Birdie is quite rough, but it does the job, it's the best (only?) functioning alarm I'm aware of on phosh at the moment.

as my pinephone screen has the well known defect, I wanted to order a new screen at the store. But the screen does not seem to be available any more. Will the be available in the future again? (or will we be forced to become pinephone pro users?

Hello everyone,

Anyone else having problems with key presses registering?  I first noticed it with the backspace/delete button.  I press the button and it doesn't work every time.  It seems out of the keyboard rows, only the top row has this problem.  Here is an example, from the bottom row to the top row I will press a key ten times, here is the result:

[[[[[[[[[[  (10 registered, that's good)
mmmmmmmmmm (another 10 registered)
hhhhhhhhhh (another 10, nothing missed)
tttttttttt (10 again)
5555555 (7 times, three keypresses missed)

Other keys from the top row:

00000 (only half registered)
444444 (6 out of 10 registered).

Is there any easy fix I can do for this at home?  I really don't want to have to return it but I only have a 30 day window to do so.  Is super annoying as my password is made up of numbers for the initial log in screen when Mobian boots up.  When I'm in a terminal entering my password, I can't see the numbers that aren't registering so am getting the password wrong all the time.

Edit: I have just read the important thread about making the top row keys easier to press. I could live with this: it's the key presses not registering at all which is the problem.

The top number key row of the PinePhone keyboard is harder to press than the rest of the keys. By adding a 3D printed or paper shim to the keys however, you can fix this issue: https://avery.cafe/blog/a-quick-fix-for-...s-top-row/

I have 3D printed a couple hundred of these, enough for a few people. If anyone would like some, message me and I will send them free of charge in a envelope. I am from the US, so I can send them anywhere here, and I should be able to send them internationally as well, however I will have to first see if I can obtain international stamps.

I can make more of them later for just the cost of shipping (which is around $1-3 for the envelope + stamp) once I run out of this batch.

Any thoughts?

I am trying to set up a development environment on a PP64. So I'd like to use a powered USB3/C hub with a wired ethernet adapter and serial over USB. *Critically* I'd like the powered hub to also power the phone.

I've got 2 different powered hubs here. a) Startech and b) MacAlly. Both work fine as expected with ethernet and other USB devices. 

What is not happening is any battery charging activity on the PP64. In the case of a) the connection is USB C to USB C, with b) it is USB 3 type B (printer) to USB C.

The latter works to power a Raspberry Pi4 and provide a USB gadget.

I am mystified.

MTIA.

Greetings, i am a new users of this lovely little gadget and i have just one simple question.
how do i recieve notifications on my watch?, they dont seem to appear.
i have firmware 1.6.0
and im using a samsung galaxy s9 from the e foundation.
apologies if this has been asked before.

Hi guys! Finally I got my PinePhone beta edition
1)I cannot find where camera turns on.
2)Bluetooth is not activable

Thanks a lot)))

Probably SoC has ethernet, then it is good idea to make it easily accessable by pogo pins

So after struggling for a few hours through lots of attempts at updating my brand new Pinecil to IronOS 2.16 I thought id share my own experiences here and how I eventually figured it out. 

The first problem I ran into is that as of IronOS 2.16 the precompiled Pinecil version comes in .hex and .dfu formats. And of course, the official Pine64 updater does not support .hex or .dfu files, it's set up for .bin files only.

From here there are a few options. The first is that you can use the recommended dfu-util to flash the OS as well as do some other fancy features like a custom boot logo, but this requires Linux, and making a thumb drive to boot off of is something I'm frankly not qualified to explain. I hardly understand it myself and half the Linux OS seems to require a master's degree in wizardry to understand.

The second option was to convert the hexadecimal file to a binary file. There are many different methods out there to convert .hex to .bin and you should always do your own research before downloading random software. But for simplicity's sake, these instructions will assume you used the same program I did called Hex2Bin

1. Use the download link found at http://hex2bin.sourceforge.net/
   
2. After downloading you should end up with a file called [b]Hex2bin-2.5.tar.bz2[/b]
   
3. Using a .zip manager like 7.zip, extract it to get the Hex2bin-2.5 file
   
4. Download the Pinecil version of the official IronOS 2.16 software from https://github.com/Ralim/IronOS/releases
   
5. In the IronOS 2.16 file, you should find Pinecil_EN.hex or the equivalent for the language you wish to use.
   
6. Right-click and go Open with -> Choose another app -> Find another app on this PC -> navigate to the Hex2bin-2.5 file that you extracted -> bin -> releases -> Hex2bin
   
7. Now you should have a Pinecil_EN.bin version of the IronOS 2.16 software
   
8. Download the official Pine64 Pinecil software updater from https://github.com/pine64/pinecil-firmwa...r/releases
   
9. Run the program called pinecil_firmware_updater
   
10. Hold down the negative button on the Pinecil and plug it into your computer
    
11. Select custom firmware and navigate to the Pinecil_EN.bin file
    
12. Run the updater
    

Hi all

Using the wiki :
https://wiki.mobian-project.org/doku.php?id=waydroid

and all goes good until: debuild -us -uc
The following is the error reported.:

Quote:mobian@mobian:~/Waydroid-build/libglibutil$ debuild -us -uc
dpkg-buildpackage -us -uc -ui
dpkg-buildpackage: info: source package libglibutil
dpkg-buildpackage: info: source version 1.0.61
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Slava Monich <slava.monich@jolla.com>
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture arm64
fakeroot debian/rules clean
dh clean
dh: error: Compatibility levels before 7 are no longer supported (level 5 requested)
make: *** [debian/rules:16: clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui failed