Has anyone SSH'ed into the PinePhone through a USB cable on a Windows (7) machine? I was able to do it quite easily on my Linux computer so I know that it's something that can be done (at least on Linux), but trying to do it on Windows seems like a different beast.

The Pinephone shows up in Devices and Printers but it has a yellow exclamation mark. In Device Manager is shows up as a "CDC ECM" device again with a yellow exclamation mark. I'm guessing I would need a driver that that doesn't exist but I thought I would ask.

Edit: I've gotten it to work, unfortunately I'm too tired to explain how I did it right now.

I have made a webapp which is now installed on my frontpage with the rest of my apps.  I now want to remove this but I can't seem to find out how to do it.  Searching the forums didn't turn anything up.

Can anybody assist with this?

Thanks

Got the PinePhone BE yesterday and have a very annoying issue.
All of a sudden it started locking it self down after a few seconds of unplugging the charger.

It then shows the lock screen. If you enter the pin it will work for a few seconds and then the same happens again.
If plugging it in, the phone keeps working just fine.

For now i could only fix it by simply removing the lock screen command:

sudo mv /usr/lib/kscreenlocker_greet /usr/lib/kscreenlocker_greet.bak

But why is this happening???

Rockbox is no longer useful as a TV box because it is too slow so I tried running Armbian.

It does not boot though, even with Rockbox DTB from Recalbox. Any idea, why?

https://redirect.armbian.com/rock64/Focal_current_xfce

I had an old ZTE case ZTE ZMAX 2 Z958 Did a few snips  and , cuts  with a razor knife works fantastic, and is a very strong case for US 8.99 + 15 min of work .

Pics  https://imgur.com/a/squeOpC

Hi all
I have Mobian installed on a pinephone 64 and most things work fine for me as I don't really ask a phone to do that much.  I have Telegram up and running but have the following problem.

I can connect to Telegram via wifi (modem/router) at home where I have no mobile connection without an issue.  When I get into mobile range the connection will initially be fine and then without doing anything to the phone (I don't turn it off or even make a call) it will lost connectivity.  It will get into an endless cycle of trying to reconnect and no amount of restarting or whatever will help.  It is important to say that it will be initially be connected to the mobile network and works fine but then drops out.  If I leave it, not connected and trying to reconnect, and then drivehome and losing mobile coverage the phone automatically connects to the modem which it always does and then Telegram is fine again.

I've searched the forums in debian but I can't find anything addressing this issue.  Does anybody have similar experiences or a fix/suggestion for this?

Thanks for any help.

Hi

We are working on a SDMMC driver for RISC OS.

On my Pinebook Pro I get unexpected behavior , writing to card fails (CRC errors) , using internal dma IDMAC.
I don't know if it relates , but when trying out several linux distros, only debian worked. The default
installation on eMMC did work just fine.

So I like to know if this is a known issue on some PBP's or if it is a pure software issue.

Michael

I can't remember where I found the idea to credit/thank them.

The privacy switches, try flipping the headset/uart one.

Hi,
I just received my Beta PinePhone (convergence). It booted up just fine. Then when I applied the updater (for 324 updates) a reboot was required. After rebooting the phone gets stuck with the message 'Failed to read Who-Am-I register' and won't boot anymore. Volume up + Power also doesn't seems to boot to recovery mode.
What do I do ?

Sincere,
-nocargo

id | grep root || sudo $0
NUMBER=`cat /sys/module/stk3310/drivers/i2c\:stk3310/2-0048/iio\:device2/in_proximity_scale`
if [ $NUMBER = 0.100000 ]
then
  echo turning off
  echo 6.4 > /sys/module/stk3310/drivers/i2c\:stk3310/2-0048/iio\:device2/in_proximity_scale
else
  echo turning on
  echo 0.1 > /sys/module/stk3310/drivers/i2c\:stk3310/2-0048/iio\:device2/in_proximity_scale
fi

works for me under manjaro phosh, YMMV
if it doesnt work see if that "iio\:device2" became device 1 or 0 or ...