hi, so ive been attempting to setup the pinetime watchface simulator using the tutorial (https://lupyuen.github.io/pinetime-rust-mynewt/articles/simulator#enable-github-pages) and have come across multiple problems which i have been able to fix. The most recent problem i have encountered is with 'Build LVGL for webassembly'. it gives me this super long log(hence the pastebin link) which i dont understand what is wrong or what its even trying to do. i am rather new to this so i apologize if i dont really know what i am doing. i really want to learn how to make a custom watch face so help would be greatly appreciated!

Build LVGL for Webassembly link: https://pastebin.com/YTDwep5C

Hi all, I'm trying to connect my bluetooth headphones for audio and bluetooth keyboard for typing, but it seems like I must choose one or the other. When I have the headphones connected, nothing gets typed by my keyboard. When I have my keyboard working, my headphones don't show up as an audio output. Is this a known limitation or is there a fix? They both work fine exclusively.

I am using a UBPorts Community Edition PinePhone with the desolder USB C fix and running Manjaro Plasma 20210801 with all updates performed through Discover.

Thank you!

Nemo mobile is back after some time in the wilderness looking for a new base OS...which turns out to be Manjaro. In the process it has moved even further away from sailfishos, while still sharing some UI and navigation.
You can download images from https://img.nemomobile.net/ or from https://github.com/jmlich/nemo-images/releases.
Read the blogs at https://nemomobile.net/ for more info; telegram group: https://t.me/NemoMobile
Currently working: see the list at https://nemomobile.net/pages/status-matrix/
Apps can be installed using pacman or flatpak but may not scale well.
Overall Nemo is currently at the level many of the other OSs were at when the pinephone came out, but has the advantage that it's a real mobile OS, not a hacked desktop. Development will hopefully be much quicker as solutions are borrowed from the other OSs.

Greeting,

I remember that in January to be surprised that the led did absolutely nothing when booting up after replacing the board from an UBports version to the 3GB replacement version. I even thought that I broke the board all together because without a boot image and with no led feedback there is no visible difference between a dead phone and a phone that is perfectly fine but has not boot image. 
Since everything else worked fine in different images, I assumed some minor differences between the board revisions were to blame for lack of feedback from the led. 
Now, I tried to find out what is going on and I can not find the culprit. I never got anything out of the sxmo led scripts, but now I installed the factorytest v0.64.0 and still nothing when I press [RGB Led]. 

Is the led broken? Did I do something wrong during installation?

Cheers

When the PineNote was announced I immediately started dreaming of what a UI could look like.

In my understanding the use case of the PineNote is so different from the PinePhone that the current GUI initiatives for mobile aren't applicable even if they could be made to work with the hardware. Instead I think the main focus should be reducing input latency as much as humanly possible. One way to do this is to not use gray scale as it (as I've understood it) requires multiple screen updates. Watching similar proprietary products flicker their way through the UI is not what I wish for this device. One alternative to grayscale is using dithering, and I think the screen has enough resolution to make this look good.

To give an example of what this could look like I sketched together two mockups of what a home screen and a note app could look like. They are both in the right resolution and uses only black and white. I've here used the Floyd–Steinberg dithering algorithm.

I'm generally excited for this, I've been researching ways to possibly modify reMarkable for my purposes, but it seems that PineNote would be a better fit!  Just wanted to share some thoughts and ideas on PineNote. 

I would love to be able to;

1. Have an interface that is built around the pencil experience.
- It seems current UIX is kind of clunky (for these types of devices), and built around an experience that was mouse first and pencil interaction an after thought.

2. Collaboratively Edit/Comment/Modify Documents, Spread Sheets, Diagrams, Drawings, and Slides.
- I want to be productive, as well as consume content.
- I want to be able to draw and present (securely) in near real time.
- I want others to be able to draw and help modify the documents I'm working on.

3. A Modem isn't a MUST, but at least some type of network comms would be.
- Tethering Comes to mind.
- I don't want to be dependent on plugging into a computer to get updates.

4. Be a good e-Reader (and e-Writer)
- Interfaces w/ All the popular "libraries" out there (Library/Amazon/etc).
- Be able to author eBooks as well, or somehow leverage the device as a format validator (e.g., see how my newly created eBook displays/works).

5. Be a good SSH Terminal
- Most of my job revolves around SSH Terminals.
- Maybe have the ability to also connect an external monitor/keyboard/mouse?

6. Device Security
- Have a TPM or a protected space to store my private keys (ARM Secure Extensions?).
- Be able to manage it via MDM, or some other type of enterprise management tool.
- On-Device Encryption.  Maybe integrate some type of labeling system for DLP as well.

7. NFC/UWB
- Be able to control devices (or issue commands) to other devices that are very near.
- To start a conference (a few flicks of a magic pen, and my document is now on a screen)
- To share content (^^)
- To locate my lost tablet! (kids are hiding it again).
- To use it as a finder of my other things.

My pinephone gets stuck in a sort of loop of having me enter my password, then the screen flashes a few times and kicks me back to the lockscreen. It only does this while not receiving power. If it is plugged in and getting power everything works fine. If it is plugged in while I am using it then I unplug it, it turns off. The battery percentage also moves around quite a bit. It changes by a few percent more right when I unplug, then shows over 10 percent more when unplugged and on lockscreen. It is completely up to date as of today, running Manjaro with KDE Plasma. 
Any and all help is appreciated 

When I first pair and get my Pinetime (running InfiniTime 1.3.0) it works great. Even if I have a disconnect from getting too far away from the phone it will reconnect as it should. The problem is that if I leave it disconnected for a while, like overnight if it's charging or I'm just not using it for a day or two, it will not reconnect no matter what I try.

The only way I can get it working again is to delete the device in gadgetbridge, reflash InfinitTime then it will connect again. Well actually, just now I was able to get it to reconnect just after removing it in gangetbridge and adding it back without reflashing. That hadn't worked the previous attempts because gadgetbridge would appear to freeze for a while and I was killing it. As you can imagine reflashing the firmware every time it's disconnected for more than a few minutes gets rather annoying .

Anyone else having issues with Infintime not reconnecting to gadgetbridge?

Hi,

After only a few months (4-5) of light usage, not every single day, the display cable seem to have given up.
The problem leads to a very dim screen, black screen at certain positions and a flicker of about 5-10 Hz at very low brightness settings.

So to me it's clear that there's an issue with the cable, as moving the cable around will turn the screen of. I've also re-seated the display connection.

But why would it flicker on low settings and why is the brightness much lower at max settings than before? Does anyone know how the display communication work on the pbp? ..or in general?

I uploaded a video of the problem, with some commentary:
https://odysee.com/pinebookpro-broken-di...nVsNWCMr51


So.. Has anyone disassembled the display unit? It's easy enough to remove from the base but it doesn't really offer any more access to the cable. I really don't want to buy a whole new display just because of a broken cable.


Thanks! And I love the project and the machine as a whole, I just didn't want to waste your time with that in the beginning of the post

Has anyone tried switching from Bullseye to Bookworm yet? Just curious how unstable it actually is right now but have also been using Mobian as a daily driver so didn't want to jump over myself then have everything get messed up.