On android, if I turn on airplane mode, the cell, bluetooth and wifi radios are turned off. When I turn off airplane mode, it only turns back on those radios that were on before it went into airplane mode.

Now for gnome settings and airplane mode. First off, airplane mode is not selectable itself. Instead, if I turn off wifi and bluetooth then the phone goes into airplane mode, turning off the cell radio in the process. This is not only counter intuitive, it's absolutely not what I want to happen. When I turn off airplane mode, it turns on all the radios.

Is there any way to completely and permanently disable airplane mode?

This might be kind of a rant, I just wanted to share.

So, I have been in the market for a fitness/smartwatch for a long time. A couple weeks ago, I gave up on waiting on the pinetime and bought a cheap one with good reviews on amazon, the Amazfit band5 or something like that.

Once it arrived, I turned it on and it wouldn't do anything. Opening the instructions, I discovered this thing is essentially a brick until you do the following:
-Bluetooth pair it with your iPhone or Android device.
-Install the Zepp app on this device
-Make a profile there so Zepp knows your name/age/birthday/weight/height and way more than I was comfortable giving.
-check for updates.

Only after all that was I able to use the darn thing. I felt kind of violated just trying to set this thing up. It works nice, battery life is amazing, but I don't trust it.

After using this data miner for about three days, The Pinetime was announced as ready for purchase! I immediately sat down at my PC and bought it, and it just arrived yesterday.To compare initial setup to the Amazfit band 5, I had to do the following for the Pinetime:

-research and find instructions to update firmware
-install GadgetBridge from the F-Droid app store
-pair Pinetime with my android phone
-go to the Infinitime github page and download the latest *DFU.zip file onto my phone
-just trying to open the zip folder from a file manager, Gadgetbridge knew what to do with it.
-try and fail to upload the firmware file to the pinetime about 6 times (connection drops for everything, including my phone screen going to sleep)
-profit.

Initial setup was way harder, and the user interface is not as pretty but I don't feel dirty trying to use it.

I now have a smartwatch that doesn't obviously mine my data for a 3rd party, and it actually does more. when paired to my phone, the previous watch would only work with big names (Spotify) for music streaming. This thing doesn't care what app I use for music, it worked just fine. Time will tell for accuracy of things like the pedometer though. had a busy weekend, but I intend to do some comparisons over the next few days.

May 2020 edition running Manjaro, will do fresh install via Manjaro ARM Installer
64 GB eMMC
barrel charger
I have never opened the back
no dead pixels
speakers work 
do not have original box, all else is like new.
$200 USD and includes shipping to continental USA via USPS.
Send email to edandjeanmcknight@gmail.com

have learned a lot re Linux and ARM, not using on a daily basis and ready for other projects.

I did an 'apt-get remove gnome-authenticator' and then installed the flatpak version.
Now I have two identical "lock" icons on the desktop.  One brings up the flatpak version 4.x and the other brings up the 3.x version.
I can find no remnants of gnome-authenticator via apt-get or 'dpkg -l' and yet the icon and the program remain.
Any idea how to get rid of the 3.x version?

Ok so when I go to wake the screen, about 1/5 of the time, nothing happens.  Just a black screen.  If I ignore it and leave it, the problem goes away and it will wake up just find later on. (Call it 10 min or more)

I've tried the last two nightly builds of Mobian.  Both are running into this issue for me.  One is on the SD card, the other flashed to eMMC.

Any suggestions?

I can't seem to get a usable download of the old stable Mobian version from mid March.  I just get the loooonnngg resizing message and permablack screen when I try that.  (3 separate downloads on 2 devices now)

Manjaro woke fine for me, but I wasn't a fan.

My PinePhone will boot from the eMMC, but will not boot from a MicroSD card that boots in another PinePhone.

I asked about this over in the software section, but am wondering if it could be a hardware problem. Here is a link to that post: https://forum.pine64.org/showthread.php?tid=13703

Before anyone asks, I have the card in the upper slot, I have made sure there is nothing visibly interfering with the card making contact, and I have tried three different cards. All three of the cards will boot in my friends Beta Edition PinePhone, but none of them will boot in my PinePhone.

When I attempt to boot I get a solid red notification LED and the phone never finishes booting.

I just tested booting with a MicroSD installed and no OS on the card. The phone booted to the eMMC as I would expect, and I was able to access the MicroSD card. Would this indicate an issue with the boot loader? If so, how do I re-flash the boot loader?

Thank you for any suggestions.

Timothy

If you recently ordered a PinePhone64 I highly suggest you order yourself a better SIM Card Extender.

Under no conditions should you even ATTEMPT to use the plastic one sent with the device. Iv personally verified it Will break the Sim Card Slot due to how the extender is designed (Cheap plastic, rough edges catch on prongs)

Thank you for reading my qustion. I did originally post this in the Manjaro forum.

Now have anyone tried to start a dock or some sort of additional launcher when the phone is docked or in "convergent mode"? What I'm looking for is some sort of quick way to start applications on the big- screen without touching the phone or moving the cursor and dragging my applications from the mobile- to the external screen. I have tried "lavalauncher"(https://sr.ht/~leon_plickat/LavaLauncher/), but that one just started, but did not register my touch, left or right clicks.

key- bindings could also work.

Any suggestions are appreciated.

I started charging with a USB-C PD capable battery bank at 17% battery on PostmarketOS.
The battery level was stuck at 17% for a few minutes before jumping to 50%.
Then it went to 30% and 39% after a few more minutes.

I suspect this is a voltage monitoring issue not a software issue.
Have anyone seen something similar?

Update: I made a while true loop to monitor battery charge level every second. I will report back later.

Update 2: Charge percentage incremented normally after the 40% mark. Currently stuck at 89% for the past hour.

When going to Settings > Mobile, I see "No WWAN Adapter Found. Make sure you have a Wireless Wan/Cellular deivce"

I live in Australia. Using a Telstra prepaid SIM card. The SIM card works in my other phone fine, so it's not the SIM card.

I had some trouble inserting the SIM card originally. First, I inserted it twice without the nano-micro sim converter (having gotten nano/micro sim sizes confused), which didn't work on Manjaro KDE (obviously). I then tried inserting it with the adapter 4 times, and it still didn't work. There was no real feedback on KDE, but I tried placing a call and receiving one from my other number, which didn't work. I should mention that Wi-Fi does work, so obviously the modem is functioning correctly. I've tried Plasma, Ubuntu Touch, and Mobian. Mobian is the only one of the three that actually has a section for mobile data (Plasma does have one, kinda, but it didn't work for me), which is progress.

I've checked the SIM card slot for damage, and all the pins seem to still be fine. A little surprising given how much of an ordeal it was to remove the SIM card after each failed attempt, but I'm thankful for it.

However, this message, "No WWAN Adapter Found. Make sure you have a Wireless Wan/Cellular device" leads me to believe that it can't detect the SIM tray component of the phone existing anymore? Or does this just mean that the SIM card is not detected?

It was difficult to insert the nano SIM into the slot with the micro SIM adapter. I've tried inserting the SIM card in various ways, but I settled on the one that the picture above the SIM/TF slot seems to suggest: the cutoff corner on the top left of the SIM/adapter, meaning that the SIM is on the bottom, not the top, of the adapter. Which obviously means that it falls out pretty easily. This did...not seem entirely right, but it matched the picture, so I went with it...

Everything else works fine. Wi-Fi works, if somewhat slow. Bluetooth is fine. Battery life is pretty good. Performance on Mobian Phosh is pretty great compared to Manjaro KDE (Ubuntu Touch was also pretty good, but had a weird issue where, whenever it would go into screensaver mode, I'd have to hard-power off the phone and turn it on again to get into it, so that was a no-go). Axolotl seemed to work on Ubuntu Touch (not on Manjaro KDE, couldn't even get the app to open). I was able to successfully attach the dock and thus the keyboard/mouse, which worked. Charging works. I tried plugging an ethernet cable into the dock, which...I don't know if that worked? There wasn't any feedback on the OS.

The only thing that doesn't work is, well, the thing that makes it a mobile phone. Cellular data has a clear slash through it in the top bar of Mobian.

I've tried installing the Modemmanger GUI, and it tells me "No devices found in system". Like it can't detect that the modem lives?

I tried going to King's Cross, typing in:

sudo systemctl enable modemmanager
sudo systemctl enable modem-manager
sudo systemctl stop ofono
sudo systemctl enable networkmanager

The result is the same: ".service could not be found".

I would have tried entering the APN, but because it doesn't detect a WWAN, there's no other options in settings, so I guess I can't do that.

Can anyone help me?