Greetings all,

I have been trying out the Linux phone I got recently (Librem 5) and noticed that generally apps are not so ready for the small screen...

I wonder if others using other Linux os's on Pinephone have noticed a similar problem or have any good workarounds?

As an example, there are several good Android calculators (Arity, open source on FDroid is my go to)
but on mobile Linux the most awesome calculators are bloaty or cut off on the small screen and don't work so well...
In fact I went through the options and listed out some of the problems - and linked bug reports, here:
https://howtotrainyourrobot.com/in-searc...pinephone/

I'm really used to the Ctrl modifier only applying to the single keystroke which follows it.  Instead, Ctrl behaves like a caps lock, staying applied until you click it again.  I'm sure that's great for some, but not me.

I've had a swing through the Squeekboard documentation, and but I really don't see anything in the config file to control this.  Has anybody addressed it?  TIA.

Attempting to enable the third mmc port in 4 bit mode with little progress.  I enabled it via dts & disabled the spi0 port which shares the same pins. The system comes up, sees the peripheral.. but thats about as far as I can get.  

I pulled off the RTK8189ES module and soldered my peripheral in its place and it works fine.

Some details...

dmesg log w/errors

[    1.377523] sunxi-mmc 1c11000.mmc: initialized, max. request size: 16384 KB
[    1.404182] mmc2: new high speed SDIO card at address 0001

[  17.998911] sunxi-mmc 1c11000.mmc: data error, sending stop command
[  18.005356] my_driver mmc2:0001:2: sdio readl failed -110


changes to sun8i-v3s.dtsi

mmc2: mmc@1c11000 {
  compatible = "allwinner,sun7i-a20-mmc";
  reg = <0x01c11000 0x1000>;
  clocks = <&ccu CLK_BUS_MMC2>,
  <&ccu CLK_MMC2>,
  <&ccu CLK_MMC2_OUTPUT>,
  <&ccu CLK_MMC2_SAMPLE>;
  clock-names = "ahb",
      "mmc",
      "output",
      "sample";
  resets = <&ccu RST_BUS_MMC2>;
  reset-names = "ahb";
  interrupts = <GIC_SPI 62 IRQ_TYPE_LEVEL_HIGH>;
  pinctrl-names = "default";
  pinctrl-0 = <&mmc2_pins>;
  status = "disabled";
  #address-cells = <1>;
  #size-cells = <0>;
};

mmc2_pins: mmc2-pins {
 pins = "PC0", "PC1", "PC3", "PC4",
        "PC5", "PC6";
  function = "mmc2";
  drive-strength = <30>;
  bias-pull-up;
};


changes to sun8i-s3-pinecube.dts

&mmc2 {
  vmmc-supply = <&reg_dcdc3>;
  bus-width = <4>;
  non-removable;
  status = "okay";
};

/* 
&spi0 {
   status = "okay";
   flash@0 {
  #address-cells = <1>;
  #size-cells = <1>;
  compatible = "winbond,w25q128", "jedec,spi-nor";
  reg = <0>;
  spi-max-frequency = <40000000>;
  };
};
*/

I have an early adopter version and the internal Bluetooth has never worked. Do I need to enable it or use a dongle? I have an old Dlink DBT 122 that's past its prime. 
Does anyone know of one that works with PineTab?

I got my Pinetime (sealed) yesterday and it was working great. The battery has been fine and I was connecting to Gadgetbridge ok, with an update of the default firmware to Infinitime 1.0. However, this morning, my phone has been unable to hold a connection to Gadgetbridge for more than 10 seconds. I tried to restart both the phone and watch but unsure how to restart the watch I accidentally factory reset it. However, I am still having trouble, even when forgetting and resetting the connection in Gadgetbridge, to maintain a connection long enough to do a firmware update OTA (this has been attempted with both my phone and my wife's phone, both Samsung S20FE running Gadgetbridge downloaded from F Droid). 

I am not sure if this is a hardware or software problem, but is there anything I could do to try to fix the connection.

Greeting to all,
I'm a newbie at this forum stuff.
I suggest for Arch Linux ARM on PinePhone for the community to create a slider for scaling.
The slider could be located under the volume-brightness sliders. I see that a 100% / 200% scaling has been created in settings / Display which is great but if there were graduations at least of say 10% that would be perfect. This could solve several issues with apps in the software community as each app can be custom set and thereby much easier to use.

I just want to know how to check or authenticate that the discover app is accessing the latest software available. Have done one update via discover when recieved the phone but nothing has been available since.
it appears the github stable branch has newer releases than what discover is showing https://github.com/manjaro-pinephone/pla...2105051237

Operating System: Manjaro-ARM
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Kernel Version: 5.11.16-1-MANJARO-ARM
OS-Type: 64
Processor: 4 ×
Memory: 2.9 GiB


sent this from my PP

Just got my Pinebook Pro. Used it for a while and now won't finish booting in to Monjaro. Just a cursor in the top left. I can ctrl-f4 and it kicks to a command line prompt. Is there a way to just reset the system back to initial factory?

I tried to do a sudo pacman -Syu and chose no for most of the update questions. Any issues with accepting the defaults of this with a new system?

This may sound like a silly question, but I can't figure out how to turn the pine phone beta off!

A short press on the power button blanks the screen but doesn't seem to be a proper sleep mode, in that battery drain continues apace - flat from fully charged in 6 hours, same as if it was on and being used. (as an aside is 6 hrs battery life typical?)

A (very) long press on the power button does seem to force an immediate shut-down (like disconnecting the battery would), but it is not a graceful power down, more of a crash and when you turn it on again it seems to take at least three or four soft reboots before it is stable - it self reboots continuously every few seconds after the screen wakes up and eventually might wake up or you might have to do another forced shut-down.

I haven't added anything to mine yet, so it is the default factory config, except it did propose a system update, which I accepted, when first powered on.

Does this sound like something is wrong? (it does to me). How can I get it (back?) into a more usable state?

What is the correct procedure for sleep and power off?

The top- bare gives a no- cellular icon
Settings do not have the "mobile" icon

From a terminal: