I received the PinePhone keyboard today and it charges however it does not do anything else. I am using the Mobian CE Pinephone. It is up to date. I've tried depressing the power button on the keyboard and nothing except it will stop the onscreen cursor from blinking. By the symptoms I suspect the firmware but I am not a developer so megl's blog is greek to me. Where do I start?

Hi there,

I hope someone out there can help me.

I just fried the single-pin Type H barrel power connector (and adjacent standard USB port) by absentmindedly inserting my Chromebook charger (that has a very similar pin).  The popping sound and bright red flash from the USB port with a burning smell told me that something was wrong

The USB C socket seems ok so I can charge the device but it gives off a high pitched buzzing sound that I don't get when I use the Type H barrel lead. I also think it charges slower but that may be my imagination.  Is there a way of swapping out the charging part so I can fix the problem? It's not the end of the world just annoying that I did this so stupidly.

All help gratefully received,

Leapylee

I'm running ManjaroARM on my PBP. The OS is installed on the eMMC storage. I also have an SD card permanently installed for extra space. Both the eMMC and the SD card have DOS-format partition tables. The SD card is not bootable; the space reserved for a bootloader (in between the MBR and the partition) is zeroed. The SPI flash is blank.

This arrangement used to work fine, but ever since the most recent update to u-boot from Manjaro's official repositories, the laptop won't boot with the SD card present.  This is a complete console log:

While i'm trying to get to the bottom of the audio issues,

Since i turned it on for the first time, it "tics" or "clicks" when booting or occassionally throughout its operation..
Is this normal? It comes from the rear lower half of the phone...

Cheers

Hi Everyone.
I took delivery of my PinePhone (3GB/32GB) last week.

The installed Manjaro/KDE is great and yet I couldn' get any calls to complete/audio to be heard. I was using an EE sim and read that no-one has recorded any successes with them. I read on the wiki that calls were working with a "3" sim, so i got one and again no audio.

To clarify - The DIP switches are in the correct alignment (ive tried both positions to check this)
              - With both sims, the calls connect to another mobile and this can call, wake up and alert the PinePhone. JUST NO AUDIO on connection.
              - I have confirmed the mic and speaker work, by using the audio recorder to record my voice and YouTube videos play back.
              - I have tried sending and receiving calls with a wired headset/headphones with no audio received/heard.
              - I have installed in both SD card and eMMC: Manjaro with Phosh, Manjaro with KDE, Ubuntu Touch and Mobian.

As the same happens with every OS Distro, i'm tempted to say its not the sims. I "think" they should be working fine! And the Pinephone Wiki confirms they're working in several cases. This points me more towards a hardware problem. But then having confirmed the speaker and mic work, i'm stumped...

Any thoughts? Dud Pinephone or something else?

Regards

GrapeJuice

I need a pbp replacement board.  The store seems to be perpetually out of stock with no word on when they'll be available. Does anyone have one available shipping to the US?

I want to avoid wasting an entire pbp if possible. Hoping someone has a board to spare. If I can't get a pbp board, I'm willing to sell the rest of the pbp, minus emmc (and board since it's broken). 

Please dm me or reply to the thread. Thanks!

Hi.

I'm using Ubuntu (ayufan image) on a Rock64. I tried hibernate and pm-utils but I can't get the computer to hibernate. It runs the scripts and seems to halt but the SSH session doesn't close. When I tried power-cycling, the system has rebooted.

Is it possible to get this working? The board has 2GB of RAM, I think. Maybe that is a lot to write to a micro SD card.

Hello,

It seems the accelerometer is dead on my PineTime. I have left my watch with an empty battery on my desk for 2-3 months. When I recharged it, the accelerometer gave 0 all the time and the step counter is also stuck to 0. I have noticed it with InfiniTime (v1.7.1 and v1.8.0). I have also tested with Wasp-OS with the same result. Otherwise the watch works very well.

Is there anybody who is experiencing the same failure? I believe there is not much I can do to fix it. Any help welcomed.

Antoine

can someone tell me how to get proton vpn installed? please bare in mind I'm a tech moron.

Build Errors:

I am having a glitch, both of these packages are showing in the add/remove software "updates"

python2-cffi 1.15.0-1
python2-pycparser 2.21-1

I don't know where to start...

I have tried updating seperatly, but still get the same darn errors:
===================
Preparing...
Cloning python2-cffi build files...
Generating python2-cffi information...
Checking python2-cffi dependencies...
Cloning python2-pycparser build files...
Generating python2-pycparser information...
Checking python2-pycparser dependencies...
Synchronizing package databases...
Warning: libtool: local (2.4.6+44+gb9b44533-11) is newer than core (2.4.6+42+gb88cebd5-15)
Warning: xorg-xwayland: local (21.1.2.901-1) is newer than extra (21.1.2-1)
Resolving dependencies...
Checking inter-conflicts...

Building python2-pycparser...
==> Making package: python2-pycparser 2.21-1 (Sun 09 Jan 2022 05:57:31 AM PST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found python2-pycparser-2.21.tar.gz
==> Validating source files with sha512sums...
    python2-pycparser-2.21.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting python2-pycparser-2.21.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
running build
running build_py
creating build
creating build/lib
creating build/lib/pycparser
copying pycparser/c_ast.py -> build/lib/pycparser
copying pycparser/_ast_gen.py -> build/lib/pycparser
copying pycparser/__init__.py -> build/lib/pycparser
copying pycparser/ast_transforms.py -> build/lib/pycparser
copying pycparser/c_generator.py -> build/lib/pycparser
copying pycparser/_build_tables.py -> build/lib/pycparser
copying pycparser/c_lexer.py -> build/lib/pycparser
copying pycparser/plyparser.py -> build/lib/pycparser
copying pycparser/c_parser.py -> build/lib/pycparser
creating build/lib/pycparser/ply
copying pycparser/ply/lex.py -> build/lib/pycparser/ply
copying pycparser/ply/__init__.py -> build/lib/pycparser/ply
copying pycparser/ply/yacc.py -> build/lib/pycparser/ply
copying pycparser/ply/ctokens.py -> build/lib/pycparser/ply
copying pycparser/ply/ygen.py -> build/lib/pycparser/ply
copying pycparser/ply/cpp.py -> build/lib/pycparser/ply
copying pycparser/_c_ast.cfg -> build/lib/pycparser
==> Starting check()...
Generating LALR tables
WARNING: 79 shift/reduce conflicts
WARNING: 37 reduce/reduce conflicts
WARNING: reduce/reduce conflict in state 27 resolved using rule (type_specifier -> atomic_specifier)
WARNING: rejected rule (empty -> <empty>) in state 27
WARNING: reduce/reduce conflict in state 87 resolved using rule (type_specifier -> atomic_specifier)
WARNING: rejected rule (empty -> <empty>) in state 87
WARNING: reduce/reduce conflict in state 437 resolved using rule (statement -> pppragma_directive)
WARNING: rejected rule (empty -> <empty>) in state 437
.....F............................................................................................................................
======================================================================
FAIL: test_all_examples (tests.test_examples.TestExamplesSucceed)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/pamac-build-peter/python2-pycparser/src/pycparser-release_v2.21/tests/test_examples.py", line 29, in test_all_examples
    rc, 0, 'example "{}" failed with stdout =\n{}'.format(filename, stdout))
AssertionError: example "using_gcc_E_libc.py" failed with stdout =


----------------------------------------------------------------------
Ran 130 tests in 8.235s

FAILED (failures=1)
==> ERROR: A failure occurred in check().
    Aborting...