I updated my Mobian installation today and found some differences. "Kings Cross" or "Terminal" is now "Console". The on-screen keyboard is different, with black characters on a white background, though at first glance the layout appears to be the same.

Most disconcerting though is there is now an orange exclamation point in the cellular indicator. Calls seem to be working normally though. (Could it be because I have mobile data disabled in Settings?) This displayed immediately after rebooting the phone subsequent to the updates.

I have just bought a second hand pine beta. It has mobian on. I do not have the passphrase. And if I do manage to get it can I just install my sim from my Android phone? Otherwise what are my options? Thanks.

Hello,

I recently installed tow-boot to get wake-from-suspend working, and I saw that it was supposed to make flashing to emmc possible as well.

I followed the instructions on the wiki, flashing once from an SD card boot of mobian, and another time from my desktop by booting the pinephone pro as a usb mass storage device. Both times when I try to reboot I get a red light, and then an amber light, repeat.

I used dd every time. I flashed the *.img file from the latest Mobian weekly build.

Before flashing I saw some people claim that mobian will work on emmc after installing tow-boot, but is it possible that it still doesn't for some devices? Is it maybe the version of mobian that I'm using? Something else maybe?

Thanks for reading.

• Fractional scaling for Wayland (Once you've ran the command below in the terminal, simply head into the display settings and try some of the scaling options - 150% works fine for me, depending on the quality of your eyesight you may want to try different options).
  gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"
  

• Enable legacy extensions not optimised for Gnome 42 yet (As Gnome 42 is a brand new release, obviously some extensions haven't been updated with official support yet, although they still work despite this).
  gsettings set org.gnome.shell disable-extension-version-validation "true"
  

• Maximized by Default (Maximise application window on launch).
  
• Maximize to Next Workspace (When an app is launched with the above extension, move it to its own workspace - simulating Androids recent apps switching experience when switching between apps).
  
• Desktop Cube (Adds swipe gesture from multiple locations on screen to switch between work-spaces).
  
• Dash to Dock (Enabled to force the dock to be visible at the bottom of the screen permanently).
  
• Notification Centre (Separates the notification centre from the calendar drop down in the top bar to divide them both into slimmer alternatives).
  
• Hide Activities Button (Frees up more space in the top bar/status bar).
  
• Remove App Menu (frees up more space in the top bar/status bar).
  
• Clock Left (Stops the clock from pushing the system icons off screen if you're showing the clock with the date included, etc...).
  
• Autohide Battery (Hides the battery status info from the top bar when the battery is full).
  

• The 'quick tap power button' functionality doesn't work currently so you can not turn your screen off without powering down the whole device.
  
• The 'on screen keyboard' is not very well optimised for this device form factor and often certain characters are completely cut off from the screen and so you need a physical keyboard for the time being. Or at least until we manage to get the Phosh keyboard to work in Gnome.
  
• The 'GDM Login screen' ideally would be adapted to be better suited to phone screens. Although it is usable, I just think that it would be nice to have the pin entry UI always visible on that screen and no need to tap the user account before being able to enter the pin/password. Although as it's Linux, the pin entry screen would probably still need the button to choose between X11 & Wayland - for now at least until X11 is no longer relevant in Linux).
  

What can we do to get the Pine phones recognized as a "White Listed Device"  ?

* Pure Talk recently stopped their data services on my test lines,   <Customer service implied it was "AT&T requirement". >
>>  their data had been working pretty good.

* AT&T PrePaid is my long term main number, their talk/text works perfect, but their data has been crap,
 >> Since 2 smart phones Before my first Pine phone.

    

Can Pine64 apply for a listing ?

what is the proper way to restore the PineTime state after flashing it using SWD flasher? 

i noticed, that while flashing a pinetime-app (e.g. "pinetime-app-1.9.0.hex" or "bin" one) leads to the state where the InfiniTime works, 
but the PineTime can't reboots or be updated with OTA package with companion app: the OTA-update is transferring OK, InfiniTime dsplays "Image OK", but no reboot and installation happens.

I'm currently trying to install Snaps, with the objective of installing AnBox so that I can run a couple of Android apps on my Pinephone. I'm running Manjaro ARM w/ Phosh.

I'm keen to read about other users' experiences installing snaps and AnBox and any issues arising with apps used thereafter. I've hit an impasse installing Snaps, as I've just posted in another thread.

Thanks in advance. 

I'm trying to install Snaps on my Pinephone running Manjaro ARM w/ Phosh, following the official installation directions for Arch Linux, here: https://snapcraft.io/docs/installing-snap-on-arch-linux

I've hit an impasse, with the message "Pacman is currently in use, please wait." repeating on the terminal screen.

The last command I entered was...

Hello All,
I am running InfiniTime
FW 1.8.0
HW 1.0.0
all had been going well with the watch since I got it until today when the touch screen stopped working. I have been running 1.8.0 since Feb 21. I have tried rebooting by holding the power button, I tried installing the 1.9.0 version on InfiniTime hoping that would reset things but the touch screen still is not working. The power button still works and I can still connect it to Gadgetbridge.  It is a sealed watch so I have no access to the internals.  My current plan is to let the battery die and see if that will reset anything.  Please let me know if you have any recommendations and I will post again if anything changes.

Used 24 *7, mainly for writing, no phonecalls, 3g, wifi. Or is it better to switch to #phosh for this purpose?