| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,111
» Latest member: p789betbiz
» Forum threads: 16,362
» Forum posts: 117,533
Full Statistics
|
| Latest Threads |
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
Yesterday, 05:22 PM
» Replies: 2
» Views: 151
|
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
07-05-2026, 11:02 AM
» Replies: 0
» Views: 76
|
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,032
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 239
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 130
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,597
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,209
|
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 276
|
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 195
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,669
|
|
|
| No Voice or Text on Inland Cellular (non-MVNO) but Internet Data Works! |
|
Posted by: calinb - 11-13-2020, 02:01 PM - Forum: General Discussion on PinePhone
- Replies (14)
|
 |
I have an Inland Cellular SIM card. Inland is NOT an MVNO and Inland owns the only towers and provides the only cellular service in my part of rural Idaho, US. I really wanted PinePhone to work and I'm very disappointed. (I will give up mobile phones entirely rather than use a spy phone, even though the telecom networks still spy on those of us using PinePhones.)
I hope someone here has a few ideas or suggestions that will help me.
My PinePhone receives an Inland 4G signal and Internet data works, but voice and SMS text are completely non-functional (inbound and outbound). The Inland tech was very helpful and even loaned a Samsung phone to me that, of course, works reliably on their network. I use the loaner phone to check SIM settings, signal strength, and functionality. (I appreciate the "hometown" feel and personal support of this carrier, compared to my previous dealings with Verizon, AT&T and a couple of their MVNOs. The tech was very interested in my PinePhone too!
I also tried my old, no longer subscribed Verizon SIM card some miles away where Verizon towers are visible. It too produced a good 4G signal bar indication, but I have no idea whether or not Verizon would work because the subscription has expired. Guess I could have tried calling 911!
The Inland tech told me that Inland does not support VoLTE but they are working on it. The following Inland frequency and band specs are posted at https://www.signalbooster.com/pages/what-are-the-cellular-frequencies-of-cell-phone-carriers-in-usa-canada.
Inland Cellular
3G Frequencies / Wavelengths
3G : 835 - 845 MHz, Block B Band 2 (CDMA2000). 880 - 890 MHz, Block B Band 2 (CDMA2000).
4G, LTE, 5G frequencies / Wavelengths
4G : 800 MHz ESMR, Band 26 (LTE700). 1900 MHz PCS, Band 25 (LTE700). 2.5 GHz BRS/ EBS, Band 41 (TD-LTE700/ LTE Advanced).
The following PinePhone specs are summarized in the wiki: https://wiki.pine64.org/wiki/PinePhone#Specifications
Communication: G25-G
LTE: B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41 WCDMA: B1, B2, B4, B5, B6, B8, B19 GSM: 850, 900, 1800, 1900 (MHz)
Though I'm a retired electrical and computer engineer, I find cellular freq / band and modulation specs to be baffling. Are these Inland and PinePhone specs compatible? What is the difference between CDMA and WCDMA?
I tried Manjaro Phosh (I updated to Beta2 level using pacman) and I also tried UBports Ubuntu Touch (Lomiri) and Mobian (Phosh) from the p-boot build and multi bootloader. Actually, I tried all the OS images on the p-boot SD but only Ubuntu and Mobian worked to check or set the APN and establish a connection. They worked far better than Manjora Beta2, in fact.
Manjaro Beta2, updated from OEM and booted from eMMC, was barely usable to set the APN and connect to the Inland network, because the Manjaro Beta2 cellular settings are unstable. I never figured out how I sometimes managed to get a connection (accompanied by Internet data) and Manjaro always required a lot of setting, resetting, and turning the modem off and on. Sadly, the effort was always lost at each reboot.
But these OS configuration utility issue are subjects for other bug reports and p-boot Mobian and Ubuntu seem reliable enough to test any suggestions forum members might prescribe!
My next step will probably be to download the factory test image and boot it from an SD card. Factory-loaded Manjaro build with testing utility. Maybe the test utilities will detect something wrong with my hardware.
Although I was mostly a hardware and signal integrity engineer before I retired, I did a lot of low level programming (boot ROMS, device drivers, diagnostics) during my career and a good deal of it was for *NIX operating systems. I'd very much like to solve this partial, but critical, Inland non-functionality (Internet data IS working). Hopefully I'll then find the spare time to contribute to this project as a developer. (I'm actually busier than ever in retirement on this old rural Idaho homestead!)
Thanks so much for reading and thanks for any help that you may be able to provide to me!
-Cal
|
|
|
|
| General getting started |
|
Posted by: James Good - 11-13-2020, 01:14 PM - Forum: Linux on Pinebook Pro
- Replies (10)
|
 |
It almost seems that starting just after I received my PineBook Pro in the second quarter of 2020, it has be plagued with log-in and password problems. At present, I am trying to reinstall the current version of the Manjaro operating system on the laptop. It will boot and get to the login screen, then the first problem arrives: the USERNAME is correct, but the PASSWORD always seems to fail. Earlier, can't remember exactly when, there were some instructions on how to find and/or reset the initial passwords that are set during the first boot process. I remember seeing, and using, those instructions once. But right now, I can't remember the key combinations required to interrupt the boot process and get badk into the install process. Any help would be welcome.
Thank you.
James Good
|
|
|
|
| No OS will boot on new mainboard |
|
Posted by: rohtua - 11-13-2020, 12:26 PM - Forum: PinePhone Software
- Replies (4)
|
 |
Hi I have one of the original UBPorts edition phones. Today I received a new main board (the 3gb version) . However whatever I do I can't get anything other than jumpdrive to boot on it. I've tried the latest builds of Manjaro and UBPorts. I've read that there needs to be a patch applied before some OSes will boot with the 3gb ram version but given Manjaro is the OS that comes with the 3gb edition pinephone and the UBports edition should have the patch in the latest update im not sure where I'm going wrong?
The eMMC shows up on my desktop when jump drive is running and after I've flashed the image to the eMMC I can see the partitions on the eMMC but its just not booting. No lights nothing. Any help would be appreciated.
|
|
|
|
| App navigation and PC to Phone how to questions Also charging |
|
Posted by: nbh - 11-13-2020, 11:52 AM - Forum: Manjaro on PinePhone
- Replies (7)
|
 |
Well done! I like it. It's not the daily driver - yet; but it has tremendous upside.
How to navigate around putty an applications in general when they dont present the keyboard with tab, esc, alt, etc?
Meanwhile, the usb dock worked with a keyboard that had a wireless mouse (that's one port and cisco usb console cable was in the other port) The dock's hdmi to a TV also worked. More to come.
How to get Linux PC <==> Manjaro Pine when attached. For example to load music into Lolly Pop?
Would life be better with a Manjaro VM?
It came with a red blah blah blah cable... can I use my iPhone wall plug to charge my pine?
|
|
|
|
| Minor design fault in case |
|
Posted by: SocialNetworkingWasAMistake - 11-13-2020, 11:51 AM - Forum: PinePhone Hardware
- Replies (4)
|
 |
Hey, I've just noticed a crack in the middle-right of my Pinephone's case from repeatedly removing and replacing it. Might be good to redesign it in such a way that there isn't too much stress on the right side of the case when you do that.
It's no biggie tho, now I get to try my hand at printing my own.
|
|
|
|
| Geary segfault & invalid locale |
|
Posted by: marcih - 11-13-2020, 08:33 AM - Forum: Manjaro on PinePhone
- Replies (2)
|
 |
I don't think these two are related but this is how I discovered the locale issue. I tried regenerating locale with "locale-gen" but no dice, could be improperly configured locales when builiding glibc (I remember having a similar issue on my Gentoo install a few years ago). I have no idea what I could do to try and fix the Geary segfault.
Code: [manjaro@manjaro-arm ~]$ geary
*[wrn] 15:27:17.0698 Gtk:Locale not supported by C library.
Using the fallback 'C' locale.
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
*[wrn] 15:27:19.0987 folks:backend-store.vala:435: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
![crt] 15:27:20.0155 Gtk:Error building template class 'ApplicationMainWindow' for an instance of type 'ApplicationMainWindow': Unknown internal child: action_area
Segmentation fault (core dumped)
[manjaro@manjaro-arm ~]$ localectl status
System Locale: LANG=en_US.UTF-8
VC Keymap: n/a
X11 Layout: n/a
[manjaro@manjaro-arm ~]$ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=C.UTF-8
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_PAPER="C.UTF-8"
LC_NAME="C.UTF-8"
LC_ADDRESS="C.UTF-8"
LC_TELEPHONE="C.UTF-8"
LC_MEASUREMENT="C.UTF-8"
LC_IDENTIFICATION="C.UTF-8"
LC_ALL=
[manjaro@manjaro-arm ~]$ locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
POSIX
cs_CZ.utf8
da_DK.utf8
de_AT.utf8
de_DE.utf8
en_GB.utf8
en_US.utf8
es_ES.utf8
es_MX.utf8
fr_BE.utf8
fr_FR.utf8
it_IT.utf8
ro_RO.utf8
ru_RU.utf8
ru_UA.utf8
sk_SK.utf8
sv_FI.utf8
sv_SE.utf8
tr_CY.utf8
tr_TR.utf8
zh_CN.utf8
zh_HK.utf8
zh_SG.utf8
zh_TW.utf8
[manjaro@manjaro-arm ~]$ cat /etc/locale.conf
LANG=en_US.UTF-8
Anybody else come across this?
|
|
|
|
| squeekboard not fired for sim unlock when booting |
|
Posted by: cafe - 11-13-2020, 06:05 AM - Forum: Mobian on PinePhone
- Replies (5)
|
 |
When booting with a SIM card, the sim unlock screen pops up on top of the main unlock screen, but with no keyboard firing up.
One needs to cancel the sim unlock, "main-unlock" the device by entering password, and then, tap on the top bar to open the sim-unlock screen again. Which is quite annoying.
Does anyone experience the same, and/or has figured a way to get the keyboard functionning directly on boot with a SIM card inserted ?
|
|
|
|
an OS Update is being offered on "Software" - should I do the update? |
|
Posted by: kern707 - 11-13-2020, 01:04 AM - Forum: Manjaro on PinePhone
- Replies (5)
|
 |
Hello everyone,
Yesterday, in the late afternoon, I have gotten on my PinePhone Manjaro's "Software" application a notification that an OS update is available.
I did not download it yet, after reading some comments here and there that the update is fragile and even bricks the phone.
Should I do the update?
Additionally, a suggestion (I hope somebody from the Manjaro-arm team is reading here):
It would be super useful, if when releasing an OS update, a relatively detailed description will be added.
I mean, "performance and security improvements" is good to be used at the first line of the description, but it does not contain enough info for an OS update IMHO.
Well - sure, it is impossible and unnecessary to mention every single file or lib that is being updates / replaced / removed etc.. but I'd say it is quite important to also include important details such as:
1. if the kernel is being updated (and to which version exactly)
2. if any core library is being updated (incl. versions etc.. as well)
3. if any important feature of the phone is being updated (e.g. "Screen lock functionality improved", or "xxx was replaced by yyy" etc..)
My 2 cents 
And once again, a big thank you to the manjaro-arm team, for working relentlessly on improving Manjaro for the PinePhone, I feel that it has huge potential and I that we are not too far away from having a phone that has an almost acceptable stability to be used as a daily driver.
* I would like to mention, that even though I do it anonymously (and wish to keep it that way) - those of you who can, please donate to the Manjaro-arm team, you can donate as low as $1 / €1. those guys are working on this project using their own free time, the least we can do is support the costs of the basic test equipment, hosting, etc..
I have used this link: https://opencollective.com/manjaro-arm/donate (I am in Europe)
|
|
|
|
| Main Board Swap: Camera connector problems |
|
Posted by: tyha - 11-12-2020, 10:02 PM - Forum: PinePhone Hardware
- Replies (5)
|
 |
Hoping there is someone that can shed some light on these connectors for the cameras. I popped off the hinge (on a braveheart edition) to remove the ribbon connector, but I'm having problems getting it to clamp back down on the new main board revision.
In the video with Martign Braam installing a new board, he conveniently has the cameras preinstalled yet this is the part that I'm having the only problems with, and of course that is the part the factory did for him (probably because it's a pain).
They appear to be just hinged and not the ones you have to flip then slide it in to lock but I'm putting a lot of force and it has started to flake off some of the plastic so I'm afraid of going further.
Video for reference: https://www.youtube.com/watch?v=5GbMoZ_zuZs
EDIT:
Looks like the camera connector will not have an audible click when it is pivoted down. After pushing the ribbon all the way in (make sure to do this) with the clamp up, begin to push the clamp part down and it will cause a "ratchet" motion when you reach about 45 degrees with the clamp. After which it will continue to push the ribbon down without snapping into place and it will impart pressure down to keep the ribbon connected... at least that is what I'm guessing as i haven't been able to get mine to turn on. My board might be DOA. I'm not getting the screen on yet with the factory image still on there or the jumpdrive image loaded onto an SD card. Anyone else have a dead replacement board?
|
|
|
|
|