| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,964
» Latest member: gesav72643
» Forum threads: 16,334
» Forum posts: 117,438
Full Statistics
|
| Latest Threads |
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
Yesterday, 08:44 AM
» Replies: 0
» Views: 52
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,514
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 124
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 70
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 215,687
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 119
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 185
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,019
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 894
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 575
|
|
|
| RockPro64 Debian xrdb -- problem connecting |
|
Posted by: emarsh - 05-19-2022, 09:55 AM - Forum: General Discussion on ROCKPRO64
- No Replies
|
 |
Hi all: I did a search on xrdb for this group and came up empty before I posted. Did a cursory search of other groups in PINE64. I did find some information. I have installed xrdb and tigervnc. I tried xrdb with windows10 remtoe desktop connection was not successful. I have a RockPro64 with Debian installation. I installed everything about 3 days ago, so my guess is that I have the latest Rockpro64 version of Debian installed.
If there is previous post on how to configure Debian + RockPro64 and use windows 10 to remote log into rockpro64 please direct me to the post. My guess is many of you are doing this, and I am just not configuring things correctly.
The error messages I get are :
sending login info to session manager, please wait...
login successful for display 11
VNC started connecting
VNC connecting to 127.0.0.1 5911
VNC error - problem connection
some problem
Thanks in advance, and please excuse me if I missed an answer to this post already.
|
|
|
|
| [Sold] PBP for sale |
|
Posted by: midnightcheese - 05-18-2022, 08:37 PM - Forum: General Discussion on Pinebook Pro
- No Replies
|
 |
Hi everyone, I'm putting my ANSI PineBook Pro up for sale.
- Perfect working condition
- Excellent cosmetic condition
- Only lightly used
- Fresh install of Manjaro Mate
- Clean
- The only thing missing is the power adapter. (The adapter was DoA but USB-C charging works fine.)
- Asking $200 which includes UPS shipping
- PayPal
- Prefer to ship US only
Love the machine, but I just don't use it that often. It should find a home that will find some solid use.
PM me if you're interested and we can get everything set. Thanks!
|
|
|
|
| MMS via Verizon quit working |
|
Posted by: treebeard - 05-18-2022, 03:06 PM - Forum: Mobian on PinePhone
- Replies (4)
|
 |
I've got an PinePhone (Evergreen) running Mobian Bookworm. I got MMS messaging working in February after installing chatty v0.6.0-1 and it was fine until on or shortly before March 12 2022. The messages seem to be retrieved and queued in ~/.mms/modemmanager/ but they don't get processed further and make their way into chatty anymore.
I've also got a Ting SIM with service via T-Mobile/Dish and MMS works fine with that. I've switched SIMS back-and forth several times and the symptoms are persistent - Verizon always fails now and Ting works.
Here is the log for a 2nd attempt at processing a message:
Code: May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:process_request_queue() service 0x55ab13be70
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:process_request_queue() location http://63.55.64.151/servlets/mms?message-id=2105824508BB00007650000201
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:resolve_host() No active proxy
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:resolve_host_systemd() resolve_host_systemd
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:resolve_host_systemd() systemd-resolved host ip: 63.55.64.151
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:resolve_host() Using URI for request: http://63.55.64.151/servlets/mms?message-id=2105824508BB00007650000201
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:create_new_web_message() host: 63.55.64.151, port: -1
May 18 15:09:09 pine mmsdtng[5933]: GSocketClient: Starting new address enumeration
May 18 15:09:09 pine mmsdtng[5933]: GSocketClient: Address enumeration succeeded
May 18 15:09:09 pine mmsdtng[5933]: GSocketClient: Starting TCP connection attempt
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:soupmessage_network_event_cb() Socket 11 Binding to wwx0225d3683889 length 15
May 18 15:09:09 pine mmsdtng[5933]: ../src/service.c:soupmessage_network_event_cb() Socket is bound to wwx0225d3683889
May 18 15:09:10 pine mmsdtng[5933]: GSocketClient: TCP connection successful
May 18 15:09:10 pine mmsdtng[5933]: GSocketClient: Starting application layer connection
May 18 15:09:10 pine mmsdtng[5933]: GSocketClient: Connection successful!
May 18 15:10:10 pine mmsdtng[5933]: Fail to get data (http status = 007)
May 18 15:10:10 pine mmsdtng[5933]: ../src/service.c:on_message_done() status: 007
May 18 15:10:10 pine mmsdtng[5933]: ../src/service.c:on_message_done() data size = 0
May 18 15:10:10 pine mmsdtng[5933]: ../src/service.c:on_message_done() request->result_cb=0x557625fdc0 vs. retrieve_conf=0x557625fdc0/send_conf=0x557625a180/notify_resp=0x557625cf64
May 18 15:10:10 pine mmsdtng[5933]: Fail to get data (http status = 007)
May 18 15:10:10 pine mmsdtng[5933]: ../src/service.c:on_message_done() On attempt 2
May 18 15:10:10 pine mmsdtng[5933]: ../src/service.c:on_message_done() Requeued Message
May 18 15:10:14 pine mmsdtng[5933]: ../src/service.c:service_retry_process_request_queue() Retrying Queue
After the "Connection successful!" message there should be some communication happening but instead I seem to get a timeout after one minute. My MMS config has CarrierMMSC=http://mms.vtext.com/servlets/mms and MMS_APN=vzwinternet.
I've tried a varety of config changes in case this had something to do with DNS, and cleared nftables rules in case the firewall was interfering. No joy.
Does anyone have a clue what's going on here? Is there anyone for whom MMS & Verizon is working?
Edit 1: I have done regular dist-upgrades, including a couple days ago, and the symptoms don't seem to change.
|
|
|
|
| Might there be a UV Radiation issue? |
|
Posted by: jojuma - 05-18-2022, 01:38 PM - Forum: General Discussion on PineTime
- Replies (3)
|
 |
Hello,
hopefully this does not sound too weird.
I purchased a 3 pack of sealed Pinetimes shortly after it became available.
Last summer, I noticed horizontal stripes under the display and asked here what that might be and where it came from. We didn't find an explanation but others having this phenomenon themselves.
![[Image: uc?export=view&id=1k7Ey7IrWaGI7H5WsBtkpqgnRhUAm377b]](https://drive.google.com/uc?export=view&id=1k7Ey7IrWaGI7H5WsBtkpqgnRhUAm377b)
Since I got a 3 pack, I used the second watch after some time because I found those stripes annoying. Summer was over by then.
Everything was perfectly fine for months until summer started a short time ago. After having been outside for one or two sunny days, my second Pinetime suddenly also had exactly those stripes.
Now I came along thinking of some UV radiation issue.
Is that nonsense or might there be a connection?
Best regards
|
|
|
|
| kb151 2-0015: Charger read failed - MCU returned 0xff |
|
Posted by: as365n4 - 05-18-2022, 03:49 AM - Forum: PinePhone Hardware
- Replies (5)
|
 |
PinePhone 1.2 - Linux mobian 5.15-sunxi64
I just recently reflashed my PinePhone with Tow-Boot and the mobian-installer-pinephone-phosh-20220508 and since then the keyboard battery is not being charged.
The fully charged battery was completly drained and remains at 0%, in Gnome Settings --> Power under Devices kb151 is listed with 0% charge and the Powersupply app has the Keyboard Case listed as well with Capacity 0%, Voltage 2.601V, Status flickering between Discharging and Charging (0.02W) and Health Good.
demsg returns --> kb151 2-0015: Charger read failed - MCU returned 0xff
Before the switch to Tow-Boot / Mobian I had U-Boot / Mobian and the battery in the keyboard case was working just fine.
It was keeping my phone charged and was a nice companion as it extended the usable life of the phone to a fine 24hrs.
Since the switch to Tow-Boot / Mobian, the once full battery in the keyboard case was completly drained by the phone, but never recharged.
As soon as I plug in the power supply it starts charging the phone (charge current alternates between 1.2A and 1.7A) once the phone battery is charged it stops charging (charge current drops to 0.3A) and the keyboard case battery remains at 0% charge, i.e. it does not charge the beyboard case battery.
Power is connected directly to the keyboard case and the top-right corner of the keyboard case gets warm indicating that the electronics inside seems to be working.
Any ideas on how to get the keyboard case battery back to working order?
I do updates on a daily basis via apt, so should have the latest version of mobian and software, and I am using the PinePower 120W Desktop Power Supply to charge the phone.
|
|
|
|
| Pinephone won't boot from SD card |
|
Posted by: arkadione - 05-18-2022, 01:32 AM - Forum: PinePhone Hardware
- Replies (3)
|
 |
Pinephone won't boot from the SD card.
I put in Tow Boot formatted SD card and turned it on.
The flashlight turns on and the phone doesn't turn on.
I flashed the Tow Boot image with Etcher and also with dd.
I just got this phone yesterday so I'm not sure if this is a hardware problem and I should contact Pine64 support.
I am downloading a PostmarketOS bootable image to try that out.
Any suggestions? Anyone experienced this?
Update for anyone else experiencing this problem:
- my phone, PP, can boot from SD card with the postmarketOS so it isn't a hardware problem
|
|
|
|
| Model A Baseboard source file seems corrupt. |
|
Posted by: sgatz - 05-17-2022, 09:15 AM - Forum: P64-LTS / SOPINE Hardware, Accessories and POT
- No Replies
|
 |
I am working on a new baseboard for the SOPINE. I want to use the original source file as a sanity-check, especially as I intend to support the Pine64 EMMC module on our board. I downloaded the .tar archive file that is posted at the Wiki page. This archive contains one .brd file. This file seems encrypted with SafeNET.
I have tried to import this file using recent versions of Altium, OrCAD, Cadence, and Eagle. All of these say that the .brd file is corrupt in one way or another.
I need a file that imports to Altium. Altium requires an ASCII file, so the extension should be .alg I think. If we can only get a binary file (.brd), then please post one that works or tell me what I'm doing wrong.
Thanks in advance.
|
|
|
|
|