Debian + MATE MrFixit version 2.0
Kernel: Linux Debian-Desktop 4.4.213 #1 SMP Fri Feb 7 13:03:55 EST 2020 aarch64 GNU/Linux

While playing an mp3 with mplayer through the internal speakers, I had the system freeze so hard that I had to take the back cover off & push the reset switch to get it to reboot.
For the next incremental hardware tweak, how about adding a hard power switch in a more accessible location?

The last thing it wrote to the logs:

Hi All: Here's my new article that explains how we may access PineTime's SPI Flash with Mynewt OS. 

We'll be using SPI Flash in the MCUBoot Bootloader for storing the old firmware, so that MCUBoot can roll back to the old firmware if the new firmware doesn't start.

Configure Mynewt for SPI Flash on PineTime Smart Watch (nRF52)

Hi,

I have a RPro64 with both WiFi and wired Internet. (WiFi via the Pine64 add-on.)  However, I have a weird network performance issue.  When the system is online via Ethernet, it responds instantly via SSH on my local LAN as one would expect. (Ping times are <1 MS on my local LAN.)

However, once I unplug the Ethernet cable either while online or after a reboot, ping times collapse and range from 5 milliseconds to over 4000 milliseconds.  This also affects SSH which becomes very unresponsive. (e.g. I type a key and the letter does not appear for a bit.)  The RPro64 is online and reachable, but very very slow.

I am trying to decide what is going and welcome any feedback.  In case it matters, I am running Ayufun's 0.9.14 stable Ubuntu minimal release.

TIA.

My trackpad mostly works pretty well, but occasionally gets into a weird state---the cursor moves randomly when I lift my finger off the pad, and taps are registered at random (even with no hands on the computer) or (more recently) no taps are registered at all. No useful information from journalctl or dmesg.

But: a reboot resolves the issue.

So I'm wondering if there's some way to powercycle the trackpad, or to reload the drivers, or anything that might help with the issue above, without a complete reboot.

Ideas?

This is on Manjaro, release 20.05

Hey all,
    I've scanned the forums and haven't seen this mentioned before, but apologies in advance if it has.
    I've flashed a distro to my eMMC flash and it's working great with one exception. Cold booting with a non-bootable (no OS installed) flash drive doesn't seem to work.
     In the past, booting from an SD card, I would insert the SD card, re-insert the battery and press+hold the power button for several seconds and I see the usual boot sequence starting; within a few seconds the status LED would cycle through it's colors and then I'd see a brief flash from the bootloader on commandline before my OS of choice's boot logo, etc...
     Now that I've installed to eMMC, when I power up with a non-bootable SD card inserted, none of the above occurs, not even the status LED cycle, which leads me to believe this is a hardware/firmware issue more than OS/software.
     From what I've read in the wiki, the firmware is set to scan the SD card before attempting to boot from onboard memory.  I've checked the drives I'm using and they are not flagged as bootable in gparted, so I'm wondering if the firmware isn't checking for a boot flag, but just the mere presence of an SD card?

     This isn't a terribly urgent issue for me, but I was wondering if others have experienced this as well. Perhaps it's only on the Braveheart edition? If so, does anyone know when PCB 1.2 will be available in the Pinephone store?
     Thanks in advance!

One of the most important things for me to get working is an e-mail client.

I installed Dekko 2 and received an update yesterday but still have the same problems:

I cannot set up an account! As soon as I get to the IMAP setup screen, I can select an input field but my input is not recognised, the field stays empty.

Any suggestions?

In another thread we discussed using desktop apps in Libertine (such as Thunderbird, for instance), but this is not working yet either.

I installed Manjaro KDE onto my eMMC from the SD card using the DD method. Almost straight away I was notified that updates were available via the desktop icon, I updated and all was good. I then used my Pinebook Pro as normal, however I did not see the update icon offer any updates, so I would open the software updater and check only to be told that my system was up to date.
I saw that version 20.04 was available. I checked and found out that I was on version 20.03, so I ran the software update and it told me that my machine was up to date. I then dowloaded (via anotherPC) and reinstalled Manjaro, this time version 20.04 and again was informed via the update icon that there were updates available. I got an error telling me that one of the updates could not dowload as a file already existed, solved by renaming the file and running the update again. 
So I am now running Manjaro KDE 20.04 but my question is how come 20.03 did not update? 
Thanks in advance

Hi All,

I am interested in understanding risk associated with designs using the SOPINE module.

We are evaluating replacements for a prototype H5 design.  

- What is Pine's relationship with Allwinner and what guarantees, or volumes, are in place to mitigate risk on A64 SoCs?
- Production schedules around SOPINE module/quarterly volumes

Happy to discuss more, share volumes, or move conversation to another medium.

Thank you all for all your hard work and time.

Best,
matt

Hello all, 

I posted about this issue over on the official UBports forum too, just thought I'd post here too in case anyone else is having the issue. 

I have been testing Ubuntu Touch on my BraveHeart Pinephone for the last couple of months and have been loving it so far, making plans for some things I'm thinking about building. 

Needless to say, I was excited about the OTA-12 update, bringing with it the CRUST battery management and actual OTA updates instead of having to re-flash my SD card every time there is a new release. Well, when OTA-12 was released the other night, I downloaded it as quick as I could, and flashed it onto my microSD card, inserted it into my Pinephone. 

For a few minutes, it might boot normally. I can usually get into the actual operating system for a few minutes, but it will always reset itself and end up going into a sort of bootloop between the Pine64 splash screen and the Ubuntu Touch loading screen. If it doesn't bootloop, it will just go into a blank, black screen until restarted again. I tried re-flashing it, using a few different SD cards and adapters, to no avail. 

When I was able to boot into the system, I tried checking for updates on each release channel, but haven't seen any new updates be pushed since then. 

Is anyone else having this issue? If you were having this issue, how did you go about fixing it? 

Cheers everyone, and hope you're all well!

Dear all,

It's been a little more than 3 months since I started hacking a Debian image for the PinePhone, by (manually) adding new software and fixing bugs step by step. Others have joined me in this effort, and a small team has gathered and did a great job at allowing the PinePhone to be used as a daily driver, at least as long as you don't have extravagant expectations such as "decent battery life" or "working camera"

We keep moving on as we're announcing the Mobian project, aimed at bringing Debian to mobile devices with as much upstream components as possible. We're focusing first on the PinePhone of course, but we plan to extend support to other devices, the next ones on the list being Purism's Librem5 and the PineTab (that is, as soon as we gets our hands on these )

Still, Mobian is not a distribution, but only an overlay to Debian, bringing you instant access to tons of existing packages, while making things easier for us as we try to keep as few custom packages as possible. This means working with the goal of upstreaming almost all of our work to Debian, and this is already going on quite well, as the base phosh packages (phoc, phosh, squeekboard and a few others) should reach the archive soon, and work on bringing phone-specific apps (such as calls and chatty) to Debian is well under way.

With this focus change in mind, we spent the last few weeks creating an infrastructure for the project, both to ease our work as developers, and to provide better user-facing services. The Mobian project now has:

• its own website
  
• a public Matrix channel
  
• a dedicated Gitlab group, including:
  • a project-wide issue tracker
    
  • a revamped (and mostly under construction atm) Wiki