Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 28,032
» Latest member: apache
» Forum threads: 15,651
» Forum posts: 114,406
Full Statistics
|
Latest Threads |
bes2600 driver
Forum: PineTab Hardware
Last Post: diederik
Today, 08:13 AM
» Replies: 53
» Views: 11,870
|
Bluetooth Handsfree Bount...
Forum: General Discussion on PinePhone
Last Post: JohnA
Yesterday, 08:51 PM
» Replies: 14
» Views: 1,042
|
Right hand mouse click on...
Forum: PineTab Software
Last Post: oiyounutter
Yesterday, 05:02 PM
» Replies: 0
» Views: 19
|
PineTab2 corrupted EMMC
Forum: PineTab Software
Last Post: oiyounutter
Yesterday, 04:56 PM
» Replies: 5
» Views: 859
|
irradium (based on crux l...
Forum: Linux on Quartz64
Last Post: mara
Yesterday, 12:53 PM
» Replies: 0
» Views: 27
|
PinePhone only turns on s...
Forum: PinePhone Pro Hardware
Last Post: zvavybir
Yesterday, 12:19 PM
» Replies: 1
» Views: 87
|
Reboot ending with INFINI...
Forum: General Discussion on PineTime
Last Post: plainsman
03-26-2024, 07:24 AM
» Replies: 0
» Views: 49
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
03-25-2024, 12:12 PM
» Replies: 1
» Views: 345
|
signal for pinefon
Forum: Mobian on PinePhone
Last Post: Pavlos1
03-25-2024, 09:25 AM
» Replies: 2
» Views: 131
|
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: anonymous
03-25-2024, 09:07 AM
» Replies: 15
» Views: 1,516
|
|
|
UBoot in updates - Has boot sequence changed? |
Posted by: tckosvic - 02-13-2022, 07:14 PM - Forum: General Discussion of PinePhone Pro
- Replies (2)
|
|
manjaro-phosh ----- As I noticed, the latest updates of this afternoon included UBoot files. Does anyone know whether system boot sequence has changed in any manner due to these updates?
Another question -- where do you see what the new updates were and what was their intention to accomplish?
Also -- do new updates move your system to one of the development release levels or a new "beta XX" release level?
thanks for any input? Particularly interested in what was changed in boot and perhaps charging logic. That really need some attention. Costing me and probably alot of other people many hours.
thanks, tom kosvic
|
|
|
External Antenna port daily driver on Verizon |
Posted by: Billthompson - 02-13-2022, 05:20 PM - Forum: PinePhone Hardware
- Replies (6)
|
|
Hey guys, just found the Pine phone!!! Never knew they existed as an ubuntu user for years.
Does anyone know how I can install an external antenna port for voice and data?
The purpose of this would be to move the emissions away from user and gain decibels. No passive antenna boosters. Our old Samsung S4's have R1 and R2 ports in the back we have been plugging into with an adapter to fme and wilson antenna. Its awesome, when not plugged in the phone uses internal antennas like everyone else when plugged in it moves signal away from user with an appreciable gain in range and performance. Sadly Verizon is shutting down voice on anything below a samsung S5. Nothing I can find newer than s4 has such a feature.
https://www.telcoantennas.com.au/patch-l...-galaxy-s4
I have seen posts here of guys installing external gps antenna, and would love to hear any thoughts on accomplishing this. Perhaps a pigtail wired in and a custom case? new antenna conectors?
Thank you so much!
|
|
|
keyboard and usb ports not working |
Posted by: User 24565 - 02-13-2022, 12:44 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (3)
|
|
Hi there,
Looking to see if there are any troubleshooting ideas i've missed.
I have a pinebook pro where I turn it on and the os loads but the keyboard and usb ports aren't working. Originally they worked but over time it seemed like it would take longer and longer for the keyboard to start working, after a while I had to wait a few minutes for any keys to function.
Now, only the power button works. I can have it sit all day and the keyboard or usb ports don't work, thus I can't even try an external keyboard. This is both on battery and plugged in.
I've tried loading different distros on sd card, took the back off and reattached the keyboard cable. I can't see any signs of damage anywhere.
Any suggestions?
Right now i feel like it's done.
thanks
|
|
|
troubleshooting Chatty / modem? no SMS outbound |
Posted by: vap0rtranz - 02-13-2022, 11:26 AM - Forum: General Discussion on PinePhone
- Replies (5)
|
|
Any pointers on troubleshooting a modem that keeps unregistering?
I switched to USMobile SIM and cannot send SMS / MMS. SMS & MMS _inbound_ does work (Yes, MMS in Chatty! ) and calls _do_ work inbound & outbound (voice is loud & clear!).
Just SMS / MMS outbound is NOT working. And when I try outbound, the modem goes back to "Unregistered", searching, and re-registers; but the "sent" SMS is never received ... logs make it sound like the modem is being rejected.
When I put this USMobile SIM into my daily driver (a MotoG8 running stock Android), everything works. So it's not a borked SIM.
One odd thing: my Moto8G modem detects this SIM's cellular network as "T-Mobile", but the APN & MMSC details in Android do indeed match USMobile's website for Androids. Those APN & MMSC details are what I have setup in Mobian Bookworm.
I've put ModemManager into debug mode but don't really know what to look for ... and perhaps debug is overkill. Did I miss something obvious in setting up USMobile?
Logs that repeat are below that have rejects in them:
Code: Feb 13 10:07:12 mobian ModemManager[604]: <info> [modem0] power state updated: on
Feb 13 10:07:12 mobian eg25manager[505]: Response: [+QIND: SMS DONE]
Feb 13 10:07:12 mobian eg25manager[505]: Executed soft sleep sequence
Feb 13 10:07:13 mobian ModemManager[604]: <info> [modem0] 3GPP registration state changed (unknown -> searching)
Feb 13 10:07:13 mobian ModemManager[604]: <warn> [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
Feb 13 10:07:13 mobian ModemManager[604]: <warn> [modem0] couldn't load operator name: Current operator id is still unknown
Feb 13 10:07:13 mobian ModemManager[604]: <info> [modem0] state changed (enabling -> searching)
Feb 13 10:07:13 mobian mmsdtng[2272]: ../plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 5 New State: 7, Reason: 1
Feb 13 10:07:13 mobian mmsdtng[2272]: ../plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 7
Feb 13 10:07:13 mobian mmsdtng[2272]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
Feb 13 10:07:13 mobian mmsdtng[2272]: ../plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
Feb 13 10:07:13 mobian mmsdtng[2272]: ../src/service.c:mms_service_set_bearer_handler() service 0x55928f13d0 handler 0x5568a66820
Feb 13 10:07:13 mobian NetworkManager[500]: <info> [1644768433.5067] modem["cdc-wdm0"]: modem state changed, 'enabling' --> 'searching' (reason: user-requested)
Feb 13 10:07:52 mobian ModemManager[604]: <info> [modem0] 3GPP registration state changed (searching -> idle)
Feb 13 10:07:52 mobian ModemManager[604]: <info> [modem0] state changed (searching -> enabled)
Feb 13 10:07:52 mobian NetworkManager[500]: <info> [1644768472.1250] modem["cdc-wdm0"]: modem state changed, 'searching' --> 'enabled' (reason: unknown)
Feb 13 10:07:52 mobian mmsdtng[2272]: ../plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 7 New State: 6, Reason: 0
Feb 13 10:07:52 mobian mmsdtng[2272]: ../plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 6
Feb 13 10:07:52 mobian ModemManager[604]: <warn> [modem0] network reject indication received
Feb 13 10:07:52 mobian mmsdtng[2272]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
Feb 13 10:07:52 mobian ModemManager[604]: <warn> [modem0] service domain: ps
Feb 13 10:07:52 mobian mmsdtng[2272]: ../plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
Feb 13 10:07:52 mobian ModemManager[604]: <warn> [modem0] radio interface: lte
Feb 13 10:07:52 mobian mmsdtng[2272]: ../src/service.c:mms_service_set_bearer_handler() service 0x55928f13d0 handler 0x5568a66820
Feb 13 10:07:52 mobian ModemManager[604]: <warn> [modem0] reject cause: ps-services-in-location-area-not-allowed
Feb 13 10:07:52 mobian ModemManager[604]: <warn> [modem0] network reject indication received
Feb 13 10:07:52 mobian ModemManager[604]: <warn> [modem0] service domain: ps
Feb 13 10:07:52 mobian ModemManager[604]: <warn> [modem0] radio interface: lte
Feb 13 10:07:52 mobian ModemManager[604]: <warn> [modem0] reject cause: ps-services-in-location-area-not-allowed
Feb 13 10:07:53 mobian ModemManager[604]: <warn> [modem0] network reject indication received
Feb 13 10:07:53 mobian ModemManager[604]: <warn> [modem0] service domain: cs-ps
Feb 13 10:07:53 mobian ModemManager[604]: <warn> [modem0] radio interface: lte
Feb 13 10:07:53 mobian ModemManager[604]: <warn> [modem0] reject cause: plmn-not-allowed
Feb 13 10:07:53 mobian ModemManager[604]: <warn> [modem0] network reject indication received
Feb 13 10:07:53 mobian ModemManager[604]: <warn> [modem0] service domain: cs-ps
Feb 13 10:07:53 mobian ModemManager[604]: <warn> [modem0] radio interface: lte
Feb 13 10:07:53 mobian ModemManager[604]: <warn> [modem0] reject cause: roaming-in-location-area-not-allowed
Feb 13 10:07:54 mobian ModemManager[604]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Feb 13 10:07:54 mobian ModemManager[604]: <info> [modem0] 3GPP registration state changed (registering -> home)
Feb 13 10:07:54 mobian ModemManager[604]: <info> [modem0] state changed (enabled -> registered)
Feb 13 10:07:55 mobian mmsdtng[2272]: ../plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 6 New State: 8, Reason: 0
Feb 13 10:07:55 mobian mmsdtng[2272]: ../plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 8
Feb 13 10:07:55 mobian mmsdtng[2272]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
Feb 13 10:07:55 mobian mmsdtng[2272]: ../plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
Feb 13 10:07:55 mobian mmsdtng[2272]: ../src/service.c:mms_service_set_bearer_handler() service 0x55928f13d0 handler 0x5568a66820
Feb 13 10:08:47 mobian NetworkManager[500]: <info> [1644768527.4008] modem["cdc-wdm0"]: modem state changed, 'enabled' --> 'searching' (reason: unknown)
Feb 13 10:08:49 mobian ModemManager[604]: <warn> [modem0] network reject indication received
Feb 13 10:08:49 mobian ModemManager[604]: <warn> [modem0] service domain: cs-ps
Feb 13 10:08:49 mobian ModemManager[604]: <warn> [modem0] radio interface: lte
Feb 13 10:08:49 mobian ModemManager[604]: <warn> [modem0] reject cause: plmn-not-allowed
|
|
|
|