Linssid would be a useful tool for wireless network survey (at least 2.4 GHz) but although it installs it aborts on an error when run, apparently a problem with connecting to the display. This then precipitates additional errors, however the inability to connect to the display seems to be the actual issue. (Linssid uses pkexec to run with root privileges.) This appears to be a generic problem running any program as root via pkexec or sudo , for example a similar error occurs running "pkexec nemo" or "sudo nemo". I'm really not very familiar with Wayland, is there a way around this?

Two manuals

1) T-mobile certification

2) MMS configuration

Attached Files

  EG25-T-mobile-certification.pdf (Size: 102.07 KB / Downloads: 1557)
  EG25-MMS.pdf (Size: 185.91 KB / Downloads: 849)

Hi!

I just received my delivery with two Pinetimes. One of them is acting up. When I first started it up it got stuck in a bootloop with white/green pinecone logo. I noticed that if I held down the button it would start with green, go to blue pinecone and finally red. I was not able to turn it off.

I let it sit for a few hours until the battery went dead and when I started it up it goes to a splash screen saying infinity time and then freezes. It is possible to hold the button to restart it, but it again hangs on the splash screen...

Suggestions? The other unit seems to be working fine...

Hi, love my pbp, Manjaro KDE plasma (last month download) on emmi. Cannot get it to boot from sd. I took off the back cover, switched the emmi off, and was able to boot an sd with Armbian Debian xfce 5. When I replaced cover and rebooted with the emmi switched back on, the sd was ignored again. So, the boot order does not begin with the spi, and then the sd, as stated in the documentation. I suppose that if the spi is blank, the system tries first the emmi and then the sd.
How do I get the sd first order? Isn't that how it is supposed to work? Install what you want on the fast memory and then try out different os's with the sd card, always able to revert to the emmi when the sd card is removed?
This should have an easy fix, but it seems to be a source of confusion to noobies (that's me). Thanks for advice.

I had a RockPro64 running on microSD just fine and forgot it was still turned on and tried to connect the eMMC to it. After popping out the microSD I noticed it wasn't booting on eMMC so plugged back in the microSD, however it no longer seems to boot fully on microSD anymore as well (e.g. my keyboard LEDs don't flash, no video output detected to TV).

Is it possible to brick the RockPro64 somehow by connecting a flashed eMMC while actively running off of microSD?

Is it possible to purchase replacement "scissor switch" mechanisms for the PBP keyboard (ANSI layout, if it matters)? These are the two tiny pieces of white plastic under each keycap.  They're not actually a switch, they are what holds the key in place while allowing it to move up and down.  I foolishly decided to rearrange the keycaps on my PBP to match a nonstandard layout, and now I have two keys that want to fall off because I broke their scissors.   I don't see this in the replacement parts section of the storefront, short of buying an entire keyboard, which seems wasteful.

jumpdrive software might be faulty (or my pinephone hardware)

this is quite preliminary view and when i get more information, i clarify what's going on. still it's headzup issue for some. i have pinephone hardware 1.2a.

i noticed that using jumdrive software, both 0.7 and 0.8, computer only saw 6GB intenal storage instead of 32GB. using telnet, then size was correct. this meant that flashing was not succesful.
https://github.com/dreemurrs-embedded/Ju...e/releases

i ended up installing o.s. to the memory card and after that i installed to the internal memory.

serious disclaimer, my pinephone could be faulty by hardware because i have some issues with gps as well.

Some conversation in IRC reminded me that I have been limiting my battery charging (on Android) to 68-70% for some time now, ever since I did some research that this probably extends battery life.

My question here is not to debate the merits of this (plenty discussions of that elsewhere) but rather, how to implement that on Debian (Mobian)?  The guy I was chatting with in IRC rattled off some stuff, but I did not catch nor understand most of it.  And they were not specific directions anyway (rather some generalities).

If no one knows offhand, I will eventually research it and post back what I find.

Maybe eventually I make some little app to handle the settings (see link in sig about making Phosh app in 10 min).  No promises.  

Hello due to travels I cannot ship anything to myself.

I have an a64+ I need to access serial console.

I am new to all this. But I am assuming that programmers such as you offer are not just for pine devices but are used in industrial applications? I'm in an area with many factories, and electronics parts providers. Can you give me some keywords and model numbers where I may be able to find an alternative to what you're selling here: https://pine64.com/product/pine64-usb-se...rogrammer/

Also I'd like to know does the "woodpecker ch340" also work with a64+?

Also I saw this post https://forum.pine64.org/showthread.php?tid=934

In the post he recommends this USB to Rs232 TTL Ch340g https://www.ebay.com/p/831651825?iid=221980597798 Would this work for my a64+?

Also he recommends FT232RL IC https://www.amazon.com/DSD-TECH-SH-U09F-...07K76Q2DX/ again would this work?

If you just tell me where I should look it would be very helpful. Once I had a bricked laptop after a bios upgrade and I was sent to a laundry machine repair facility who was able to provide me with a eprom flasher device... I just need help knowing where I should look for alternatives that I can purchase directly since I'm traveling. Thanks.

Since re-flashing Beta 11 to my eMMC, I've been unable to use my Pinephone cameras with the program Megapixels. This wasn't the case when I first received my Pinephone with the factory default OS and settings. The cameras worked fine out of the box. I didn't want those parts of the device working, so I switched them off for many months and thought nothing of it.

At the time of flashing to Beta 11, I still had the camera dip switches set to "off". Recently, I flicked the switch to "on" only to find that the Megapixels app doesn't work. When I try and open it, the desktop background screen shows, and that's it. No error messages or any other helpful prompts. 

I've tried reinstalling Megapixels without success.

Are there other packages that I should try reinstalling? I'm assuming this is a software/OS problem at this stage.