About the device: PinePhone:
Perhaps you’re in a line of work where security is a must, or a hard-core Linux enthusiast, or perhaps you’ve just got enough of Android and iOS and you’re ready for something else – the PinePhone may be the next Phone for you. Powered by the same Quad-Core ARM Cortex A53 64-Bit SOC used in our popular PINE A64 Single Board Computer, the PinePhone runs mainline Linux as well as anything else you’ll get it to run.
The purpose of the PinePhone isn’t only to deliver a functioning Linux phone to end-users, but also to actively create a market for such a device, as well as to support existing and well established Linux-on-Phone projects. All major Linux Phone-oriented projects, as well as other FOSS OS’, are represented on the PinePhone and developers work together on our platform to bring support this this community driven device.
How to install:
Download the image/xz file from the download location. Verify that the download completed successfully.
After that, install Etcher (sudo pacman -S etcher if on Manjaro) and burn the to an SD card (8 GB or larger).
The PinePhone should recognize the SD card as a bootable device and boot from it.
The premade users are:
User: manjaro
Password: 123456
The alpha3-20200906 is booting slower than alpha2 i tried previously. The power LED stays lit much longer before it turns off and the loading starts properly. The wifi and BT icons take longer to appear on the unlocking screen after boot. When i shut down the phone it won’t react when doing a long press to start it again, only the second long press starts the phone, it is almost as if it would still be on after shutdown, and the first long press force shuts it down. And finally after restart (instead of shutdown) the bluetooth adapter was not found. These worked normally in alpha2.
Same here, it is often like a game when it boots or not. And the problem with mobile data persists.
For ensuring an cold reboot I normally take the battery out for some seconds, reinsert and press on/off key for 4 seconds. Mostly Manjaro starts at least 20 or 30 seconds later.
did you try alpha3 (the first image) ? I’m wondering if i should test if the weird behavior is due to the kernel or firmware update in the second image.
Several hours after shutting down the phone it remained hot. I had to take out the battery to cool it down. I’ve never experienced such a weird thing with alpha 2.
With a workaround from gitlab I can activate mobile data stable. But phone calls are missed if phone is on deep sleep. It wakes up, but lasts 25-30 seconds to recive the call. All callers give up trying to reach me if there is no answer for such a long time. And the most problematic issue is that even the call log has no information about the missed call. So You have also no chance for calling back. You know not WHO has tried to call You.
i reflashed alpha2-20200822 and updated using pacman, and it did not gain the problems of alpha3
perl, man etc. complain about locales, running locale complains about several not found errors, solution was to export LC_ALL in .bashrc. I don’t know why this is so because i already have it defined in /etc/locale.conf
Do you mean something more with sleep than the display being off? In that state it seems to be working correctly the few calls i have received. I have not tried making a call yet. There was however a static buzz in the background during received call.
can you link the workaround from gitlab you mentioned?
This is also the case for me in Mobian and the unofficial Arch project.
Here’s what worked for me:
Setup your APN and enable mobile data. Wait for the “4G” status icon to go away.
Open up a terminal.
Run nmcli c and find the NAME that matches the name you gave your APN settings.
Run nmcli c edit <NAME> (e.g., nmcli c edit keepgo )
Type remove gsm.network-id
Type save
Type q
Run nmcli c up <NAME> (e.g., nmcli c up keepgo )
I discovered this after seeing that setting up a connection manually (via nmcli/mmcli) worked fine and comparing the settings.
The description for gsm.network-id states that it is used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible. The modem bearer settings should ensure that the device is not roaming if you didn’t enable it in GNOME Settings, but don’t yell at me if you get a large phone bill . My SIM requires that I be roaming.
This isn’t a Manjaro issue specifically, but I’m not sure what the root problem is or where to report this.
With newest updates from yesterday and today the phone also in sleep mode answers to an incoming call after 5-6 seconds! I will make more investigations about this… but at first sight this looks phantastic
