Does anyone have any idea what "oem" stands for.

I keep getting login screen for oem and have no idea what the password could be.  

Won't let me go any further until I get it.

I needed to reflash an image of mobian from february 5th, I just noticed that there's a new repo from debian bookworm security, previously there was only the the bookworm main:
before:
deb http://deb.debian.org/debian bookworm main
now
deb http://deb.debian.org/debian bookworm main
deb http://security.debian.org/ bookworm-security main

I would like to know why, and if we users need to to something in regards to the coming debian freeze of bookworm, how to proceed? What's recomemed, stick with stable once it's released or stay in testing?

Hey. I'm playing around with some stuff on my pinebook and I've noticed that if I'm in a tty, or don't even have X installed at all, the screen still dims after a few minutes regardless of whether or not I'm plugged into power.  I will just be sitting at a command line typing something and the screen goes dark.

/sys/class/backlight/edp-backlight/brightness changes from 4096 to 2047.

If not X, what is controlling this and how do I prevent it?  Is there a kernel setting I can configure or something? 

I also don't want to force max brightness 100% of the time, I would still like to be able to control brightness manually

Thank you

I was promptly reminded to contribute this info
( to the Pinephone community,)
 after posting my success at
https://github.com/markqvist/Reticulum/discussions/229


Why is this relevant to Manjaro and Pinephone?

I bought a Mobian Pinephone when it came out.

After slogging my way through a number of distros
 I ended up nailing Manjaro Phosh into place and
 abandoned further attempts to find a better distro.

The struggle to keep Phosh running has gotten easier,
 thanks mostly to other people posting here for 
 the quiet folk like myself to read and benefit from.

I have simply been trying to keep a linux console access
 to do simple tasks, like checking on servers and whatnot.

My use case is for Zero participation in the Apple/Google prisons.
----------------

The idea of e2e mesh comms like Briar and FireChat 
 always seemed to be a natural for a linux phone
 instead of a "walled garden" like Android or iOS.
I have, yearly,
 watched for anything that would mesh on linux
 without wild joyrides of moving target suite-package development.


A few weeks ago I stumbled across a reference to Reticulum
 which not only aims at meshing over WiFi and Bluetooth
 but includes something I have years of work in hacking:
 data over radio modems.
I used serial stream data for monitoring various
 geophysical exploration data acquisition equipment
 along with maritime environmental data packets.
Across vast regions of jungle, mountain and shallow marine projects.
Building and running such meshes was bread-and-butter 

Along comes Reticulum which
 proposes to build long-arm meshes
 which could possibly sustain data flows across vast regions.

Reticulum is not an application orgy.
It is a protocol the rest us can build upon.
I hope it does not, as many such projects do,
 evolve into a "moving target" that requires mandatory updates
 on a monthly basis rendering users to holding abandonware.

It also looks like a 'holy grail' because it ditches the entire
 DNS-ICANN prison overlords.
That, almost in itself,
 raises interest toward integrating with global reach of things like i2p.

Anyways - Nomadnet installs and runs well enough 
 as "betaware" on PinePhone.

My personal bet is that without any lingering bloatware (Electron  ),
 it could be a screamer on Pinephone Pro,
 so I guess I need to buy one of those and test it.

Reticulum is very primitive at the moment
 but collecting interest+participation in a parabolic learning curve.

If you want something that should eventually put
 naked emperors like Telegram/Session/.etc/++ to shame,
 you might try this out and see where it is headed.
And you could be a part of it.

Visit the github because that is where most of the real interaction takes place:
start here:
https://github.com/markqvist/Reticulum/discussions/229

My perspective is that this is a welcome and timely development,
 in context of much of what is happening in the word today.

I got a pinephone in 2021, modem disappeared very frequently since the beginning, but I was thinking it was a software issue; no longer used up to this month. Now the modem doesn't appear at all when I try to phone or messaging.
The situation is similar to this post: https://forum.pine64.org/showthread.php?...#pid115981
Can someone please help me?

To reopen an old issue,

I want to use my purchased 7" LCD Touch Screen Panel https://pine64.com/product/7-lcd-touch-screen-panel/
with Linux (I like Fedora 37 but anything will do) on my purchased RockPro64.

For me, touchscreen functionality is optional.

Has anyone figured out in the last three years how to use this screen, with the provided ribbon cable, to display?

I am working on getting tow-boot to work on my PPP. I can get it installed, but when I boot it up afterwards it will turn the red LED on, and do the vibes thing, then turn yellow and four vibes, it waits a bit before flashing and vibrating like 10 times, then it seems to turn off. Holding down the up volume it acts similarly but turns the light blue first, before turning red and blinking.vibing a few times, pausing, then doing the ten vibe blink thing and turning off. If its on a charger, it just keeps looping that. If it's attached to a computer it never gets recognized, just loops like on a charger. I have gone through the tow-boot several times, watched videos, paid very close attention to detail and it does it every time. I erased the SPI before installing, and same thing. 

I just got the phone this weekend if that helps any. It was running ok with the default manjaro plasma, I did run manjaro phosh off an SD and attempted to install it to emmc, it took forever and I thought it failed/stalled but eventually it said it completed it. It would not boot off it though. In the meantime I was researching stuff and came across tow-boot as the thing to do to make swapping OSes easier so I went for it and here we are. 

Any ideas would be great. Thanks.

Apologies in advance if a tread is already covering my issue, I couldn't find my specific problem.

During calls (send or receive), the other end can't hear me. If I speak loudly into the microphone I can be heard, but very low.

-Pinephone Pro Explorer Edition
-This wasn't a problem during the first week I had the phone.
-I am in Canada
-I tried 4 carriers (Shaw, Koodo, Virgin and settled on Freedom when I found it was officially tested)
-Tried Manjaro, Postmaker, Kali, Mobian, Artch and same issue on all of them
-During the first week, I was pulling out the battery while the phone was running (did I damage it?)
-In the Sound options, configuring both input and output to "Make Phone Call" reverts it to original settings (Default, Play HiFi quality Music)
-When I bring up the volume during a call, "Internal Earpiece" is briefly displayed at the top with the volume
-I got this to work a few days ago on Mobian with a thread I found on installing Pipewire

I am on Manjaro Phosh beta28

Does anyone have any ideas?

Hi,

When I first plugged in my Rock Pro 64 it was quite happily using the HDMI port to a 4k monitor. I then switched to using eMMC rather than an SD card boot of Armbian, and at the same time I installed RDP so I could remote desktop from windows. But now when I use teh HDMI port I get a really bad fuzzy picture, and the monintor losses sync and goes black for a second then copmes back etc. What could this by ? Is the HDMI port broken ? I tried a different monitor, and cable but still the same.

hey all,

when I go to install any of the newer images (tried as far back as august) I get no volume on my microphone during calls. I recently came across this, https://github.com/the-modem-distro/pine...ETTINGS.md and found that the setting for the microphone volume was not in the alsa ucm config file at all. I wrote it in there, and it did fix the volume until the next reboot. as the phone was booting up there was an error on the screen saying that the audio file was corrupted or wrong, something like that. while the line I wrote didn't change the phone went back to no volume on the mic. 

is there anyway to get the volume settings to stick? 

if there's no way to fix this currently, does anyone know of an image that doesn't have this issue? I'm supposed to set up two phones this month, and need at least calls and texts to work

any help is greatly appreciated!

Edit: updated the phone today, and now the microphone works. it updated some things with pipewire.