4 ms·
I bought a PinePhone to use just as an SMS gateway‡. My requirements is about as minimal as they come: it needs to stay connected to the cell network, wakeup wh
by psanford 4y ago
I bought a PinePhone to use just as an SMS gateway‡. My requirements is about as minimal as they come: it needs to stay connected to the cell network, wakeup when a new SMS comes in, and run my little gateway server that is listening for dbus messages. It often fails to do this simple task.
It seems to not do a great job of staying connected to the cell network. And it also often doesn't wakeup for new SMS messages.
I thought buying dedicated hardware that is designed to send and receive SMS would be better than buying a raspberry pi and an lte dongle, but I now regret that decision.
I've not tried to use the PhinePhone as an actual phone, but from the little time I've been forced to interact with it, the UI is basically unusable. Its incredibly slow and unresponsive. Often times it will just lock up for no apparent reason. SSH'ing into the phone has been the only reliable way of interacting with it.
‡ For the handful of services that refuse to work with Google Voice.
- linmob 4y agoWhich OS are you using? Did you try biktorgj's Modem Firmware (and additionally, the various proprietary releases, to see which one works best with your carrier)?
- Inhibit 4y agoI replaced the Pine Phone for similar functions with an IoT router from GL.iNet (unfortunately also using a Quectel). OpenWRT as the OS. TMobile subsidiary as carrier. It has been marginally more stable though. It has 9 days of uptime so far. They claim to be getting T-Mob compliance certified. Although I'd check that if it's relevant.