Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,191
» Latest member: Nambo
» Forum threads: 16,380
» Forum posts: 117,589

Full Statistics

Latest Threads
Hello, I am a new member ...
Forum: General
Last Post: WhiteRabbit0
08-20-2026, 12:17 PM
» Replies: 0
» Views: 64
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: ahegarosib97
08-20-2026, 08:45 AM
» Replies: 2
» Views: 1,932
RAM-free SBCs with SODIMM...
Forum: General
Last Post: anchor
08-20-2026, 08:21 AM
» Replies: 0
» Views: 47
Default password
Forum: PineTab Hardware
Last Post: dissimilar_goose
08-20-2026, 05:02 AM
» Replies: 0
» Views: 68
New SlateOS features
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-17-2026, 07:47 PM
» Replies: 0
» Views: 140
SlateOS for PineTime
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-17-2026, 07:33 PM
» Replies: 2
» Views: 376
How to install Android on...
Forum: General
Last Post: winpkr
08-14-2026, 01:36 AM
» Replies: 2
» Views: 3,674
Newbie questions
Forum: General Discussion on PineTime
Last Post: TouchuvGrey
08-13-2026, 08:09 PM
» Replies: 0
» Views: 238
Beta test Signal Desktop ...
Forum: News
Last Post: as365n4
08-11-2026, 08:57 AM
» Replies: 0
» Views: 239
SlateOS
Forum: General Discussion on PineTime
Last Post: highjumpman
08-10-2026, 07:17 AM
» Replies: 0
» Views: 276

 
  SSH brute force attacks
Posted by: user641 - 06-19-2022, 04:53 AM - Forum: Mobian on PinePhone - Replies (13)

Hello,

If I setup a SSH connection simply using the password, with a numerical passwordof 8 digits it will be very easily crackable right? If I let port 22 open on the pine phone, and I connect to another wifi than my lan, or to 4g, will my device be vulnerable to brute force attacks?


  RTC battery holder options
Posted by: GreyLinux - 06-19-2022, 02:47 AM - Forum: General Discussion on ROCKPRO64 - Replies (2)

Hi , all


I didn't originally purchase an RTC battery holder with my Rockpro64 , honestly not knowing the benefit of having one. Now I would like to get one , however to purchase the one fro the pine store incurs a courier charge of £30 in the UK.
I thought I would be able to find loads of alternative options for such a simple device on ebay or amazon ( although of course I would rather get one from the pine store ) , but it seems a replaceable RTC battery holder is a rare thing.

does anyone know of anywhere I can get an alternative, or possibly know the name of the connector so I can "DIY" a standard AAA holder and add the connector ?

thanks in advance


  install debian on pbp
Posted by: jsch - 06-19-2022, 02:29 AM - Forum: Linux on Pinebook Pro - Replies (7)

Hello

I would like to create a how-to file. If there is a usb-ethernet adapter available, then the steps could look like this:

source files
bullseye

Code:
wget http://http.us.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/firmware.pinebook-pro-rk3399.img.gz
wget http://http.us.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/partition.img.gz


bookworm
Code:
wget http://http.us.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/SD-card-images/firmware.pinebook-pro-rk3399.img.gz
wget http://http.us.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/SD-card-images/partition.img.gz

create img file
Code:
zcat firmware.pinebook-pro-rk3399.img.gz partition.img.gz  > complete_pbp_image.img

write installer on micro-SD
identify device name of micro-SD
Code:
lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
...
sdd      8:48   1   7.4G  0 disk
└─sdd1   8:49   1 130.5M  0 part

write to micro-SD
Code:
sudo dd if=complete_pbp_image.img of=/dev/sdd bs=4k status=progress oflag=sync

boot pbp from micro-SD
boot and install on eMMC

firmware
add non-free
Code:
sudo sed --in-place -e 's/ main$/ main non-free/' /etc/apt/sources.list

install
Code:
sudo apt-get update
sudo apt-get install firmware-brcm80211 firmware-misc-nonfree raspi-firmware
  • firmware-brcm80211 holds some wifi firmware -- is this required?
  • raspi-firmware holds brcmfmac43456-sdio.bin
  • firmware-misc-nonfree holds rockchip firmware


If no usb-ethernet adapter is available, what are the necessary steps?
Would it suffice to download them, copy them to an usb stick and mount the latter on pbp?


  45Eur Taxes for ~100Eur shipment to Germany
Posted by: hoijui - 06-19-2022, 01:28 AM - Forum: Shipment Related Discussion - No Replies

... is what I have to pay now (after receiving the parcel).
just wanted to mention it for documentation


  No audio from HDMI with usb-c adapter
Posted by: rfm83 - 06-18-2022, 09:52 PM - Forum: General Discussion on Pinebook Pro - Replies (5)

I'm unable to play audio through an HDMI cable connected to an LG TV using a usb-c adapter from QGeeM. Video works fine.
I've tried both pulse audio and pipewire. I'm running Manjaro.

Does anyone else have this issue?


  Any fix for bluetooth crash when entering pairing password?
Posted by: kk22 - 06-18-2022, 07:51 PM - Forum: Mobian on PinePhone - No Replies

This has been an issue I've noticed for ~1 year: if entering a password to pair with a bluetooth device, the password entry dialog will crash almost as soon as it displays, and the selected device will be lost while the phone scans for available bluetooth devices again.

The fact that this apparent issue hasn't been fixed for so long tells me this may just be something specific to my installation. Is there a fix for this?


Question Open box, upgrade, dead watch?
Posted by: ahaplesshappenstance - 06-18-2022, 07:18 PM - Forum: General Discussion on PineTime - Replies (5)

Hi all,

Received my first 2 sealed PineTimes today. One I was able to open, sync to, upgrade and is operating happily (it is SO COOL!)

The second however:
Powered on when I placed it into the cradle to charge (from PC USB port). I connected to it, began the upgrade process (Infinitime 1.6 -> Infinitime 1.9), and got called away. Returned hours later, grabbed the cradle+PineTime from the computer and began commute home. But: I cannot wake the screen. The device appears dead - screen is black/no backlighting, and unresponsive (I've tried holding the button for durations ranging from a single click to >60 seconds; no apparent change in state).

Did I somehow break it? Is there a timeout to successfully completing InfiniTime upgrades? Is it a DOA unit?
I tried searching online (although not yet in the Discord chats) but didn't find anything related to this sort of problem.

Any advice please is welcomed, thanks


  Can't connect to cellular network
Posted by: phytocube - 06-18-2022, 05:20 PM - Forum: General Discussion on PinePhone - No Replies

I have an Airvoice SIM card* I've been trying to get to connect, but it's not working. NetworkManager seems to detect it properly and lists the correct SIM ID and even reports that the carrier is AT&T. I've tried using both "reseller" (no quotes) and "NXTGENPHONE" (no quotes) as the APN, but it never successfully connects. Here is some of my journalctl output matching /modem/i:  

Failure mode 1: roaming-in-location-area-not-allowed

Code:
eg25-manager[2963]: GNSS assistance upload step (2/9): disabling GNSS engine through ModemManager                   
ModemManager[3180]: <info>  [modem0] simple connect started...                                                      
ModemManager[3180]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled                          
ModemManager[3180]: <info>  [modem0] simple connect state (5/8): register                                            ModemManager[3180]: <warn>  [modem0] network reject indication received                                             
ModemManager[3180]: <warn>  [modem0]   service domain: ps                                                           
ModemManager[3180]: <warn>  [modem0]   radio interface: umts                                                        
ModemManager[3180]: <warn>  [modem0]   reject cause: roaming-in-location-area-not-allowed                            ModemManager[3180]: <warn>  [modem0] network reject indication received                                   
ModemManager[3180]: <warn>  [modem0]   service domain: cs                                                           
ModemManager[3180]: <warn>  [modem0]   radio interface: umts                                                        
ModemManager[3180]: <warn>  [modem0]   reject cause: roaming-in-location-area-not-allowed                           
eg25-manager[2963]: Modem is up for 120 seconds and fully ready                                                     


Failure mode 2: no-suitable-cells-in-location-area
Code:
ModemManager[3180]: <info>  [modem0] simple connect started...                                                      
ModemManager[3180]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled                          
ModemManager[3180]: <info>  [modem0] simple connect state (5/8): register                                           
NetworkManager[3086]: <warn>  [1655592789.5434] modem-broadband[cdc-wdm0]: failed to connect modem: Network timeout 
ModemManager[3180]: <info>  [modem0] simple connect started...                                                      
ModemManager[3180]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled                          
ModemManager[3180]: <info>  [modem0] simple connect state (5/8): register                                           
ModemManager[3180]: <warn>  [modem0] network reject indication received                                             
ModemManager[3180]: <warn>  [modem0]   service domain: cs-ps                                                        
ModemManager[3180]: <warn>  [modem0]   radio interface: lte                            
ModemManager[3180]: <warn>  [modem0]   reject cause: no-suitable-cells-in-location-area                             


Failure mode 3: plmn-not-allowed
Code:
ModemManager[3180]: <info>  [modem0] simple connect started...
ModemManager[3180]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
ModemManager[3180]: <info>  [modem0] simple connect state (5/8): register
ModemManager[3180]: <warn>  [modem0] network reject indication received
ModemManager[3180]: <warn>  [modem0]   service domain: cs-ps
ModemManager[3180]: <warn>  [modem0]   radio interface: lte
ModemManager[3180]: <warn>  [modem0]   reject cause: plmn-not-allowed
ModemManager[3180]: <warn>  [modem0] network reject indication received
ModemManager[3180]: <warn>  [modem0]   service domain: cs-ps
ModemManager[3180]: <warn>  [modem0]   radio interface: lte
ModemManager[3180]: <warn>  [modem0]   reject cause: plmn-not-allowed
ModemManager[3180]: <warn>  [modem0] network reject indication received
ModemManager[3180]: <warn>  [modem0]   service domain: cs-ps
ModemManager[3180]: <warn>  [modem0]   radio interface: lte
ModemManager[3180]: <warn>  [modem0]   reject cause: plmn-not-allowed

Failure mode 4: No MCC/MNC or operator id:
Code:
ModemManager[3180]: <info>  [modem0] simple connect started...
ModemManager[3180]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
ModemManager[3180]: <info>  [modem0] simple connect state (5/8): register
ModemManager[3180]: <info>  [modem0] 3GPP registration state changed (idle -> searching)
ModemManager[3180]: <info>  [modem0] state changed (enabled -> searching)
ModemManager[3180]: <warn>  [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
ModemManager[3180]: <warn>  [modem0] couldn't load operator name: Current operator id is still unknown
NetworkManager[3086]: <info>  [1655594076.4347] modem["cdc-wdm0"]: modem state changed, 'enabled' --> 'searching' (reason: unknown)
modem-daemon[3725]: kf.modemmanagerqt: Unknown Mobile Country Code: 0
kscreenlocker_greet[3475]: kf.modemmanagerqt: Unknown Mobile Country Code: 0
plasmashell[3548]: kf.modemmanagerqt: Unknown Mobile Country Code: 0
ModemManager[3180]: <info>  [modem0] 3GPP registration state changed (searching -> idle)



  1. Do I need to issue modem commands manually to troubleshoot/fix this? I don't know how to do this, having relied on NM/MM so far; if it is, what's the best way to do this?
  2. Am I just not in the service area? I somewhat doubt this because I'm in a relatively densely populated area, but what I can understand from searching the reject causes suggests this might be the case. (I'm reluctant to switch to other providers mostly because I haven't found any prepaid plans less than 3x as expensive, but if it can't be avoided...)
* Compatibility unknown per the wiki

ADDENDUM:
Per this thread, it appears AT&T is no longer a viable carrier for PinePhones: https://forum.pine64.org/showthread.php?tid=15988


  apt-get update "The following signatures were invalid..."
Posted by: grump_fiddle_reinstall - 06-18-2022, 04:19 AM - Forum: Mobian on PinePhone - Replies (13)

From the terminal

"The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mobian-project.org bookworm InRelease: The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
W: Failed to fetch http://repo.mobian-project.org/dists/bookworm/InRelease  The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
W: Some index files failed to download. They have been ignored, or old ones used instead."


I remember having similar problems with other repos but cannot find the fix. Where can I find the new key?


  digitizer dead
Posted by: Uturn - 06-18-2022, 01:56 AM - Forum: PinePhone Hardware - Replies (1)

since quite a while, I realize my pinephone does not accept the letter Y on the onscreen keyboard. This happens in Manjaro Plasma mobile, and also in Postmarket OS SXMO. The screen is delaminating. Could this be a hardware related problem, or is it a software thing?