Just wanted to share this experience with everyone here at Pine64. I think this might be very important. Recently I had some problems with my PinePhone on March 1st. The date is important because on this day I could no longer make any phone calls or even make phone calls. I thought it was a software issue, but long story short it appears to be a hardware issue, the modem to be exact.. My rationale for this is because ATT (the carrier I use) shut down all 3g by the end of February, thus for me the problem started exactly on March 1st. Also, I discussed the issue with the ATT reps and their IT department. The IT checked everyone...all was perfectly fine on their end. The reps provided me a new sim card and I got the same results, could not make/receive phone calls (no internet either). The IMEI checks out ok in their database, but upon further inspection they notice that the VoLTE was set to "false". Meaning I would not be able to make/receive phone calls (or internet). Yet strangely enough I can receive text messages. They tried putting in two new sim cards, same result. They put my sim card into the latest iPhone and suddenly the iPhone could NOT make phone calls either. It was using the IMEI from my PinePhone. Then they changed my sim card in the iPhone to match the IMEI from the iPhone and suddenly it could make phone calls. The sim card with the iPhone IMEI number was then placed into my PinePhone and then suddenly my PinePhone could make phone calls! idk, PinePhone users may start having a lot of problems as the other carriers start phasing out 3g and replacing it with new 4g/5g tech. In my opinion I think Pine64 needs to update their hardware for better compatibility. Eventually 3g will be gone and there may be a lot of PinePhone users with no cell service. Could become a huge problem. But perhaps other carriers who already dropped 3g, will fair better with PinePhone...can't confirm that.

I'm using the Manjaro ARM Beta, not sure which version.  I wanted to be able to compile code on my phone so I tried to install some packages:




  1) autoconf  2) automake  3) binutils  4) bison  5) fakeroot  6) file  7) findutils  8) flex  9) gawk  10) gcc  11) gettext  12) grep  13) groff  14) gzip  15) libtool  16) m4

  17) make  18) pacman  19) patch  20) pkgconf  21) sed  22) sudo  23) texinfo  24) which




I don't have a copy of the output of what happened, but it failed.  Now when I boot I get the Manjaro logo for a while and then (this is transcribed from tiny text and probably has errors):




[    0.216425] lima 1c40000.gpu: dev_pm_opp_set_regulators: no regulator (null) found: -19

[    1.871112] kb151 2-0015: KB151 was not detected on the bus (-6)




Is there any way to recover from this?




I'm not completely certain which version of the beta this is.  I installed it a few months ago and used software update a few times.  I have an image of the root filesystem to recover files, but unfortunately I don't have a Linux machine I can use to change anything directly on the card.

I have Verizon and I put my sim card in and it makes calls and texts perfect. Data does not work though, I assume it is a settings issue. Does someone have the apn setting or whatever it's called for Verizon.

I have a RockPro64 running Ubuntu 4.4.190-1233-rockchip-ayufan-gd3f1be0ed310. It boots from emmc and has a hard disk attached via SATA.

After working fine for a long time, since last week the hard disk doesn't seem to be recognized. It doesn't show up in `fdisk -l` for example and isn't mounted anymore.

If I plug it into another laptop the drive mounts and is visible so I don't think it's dead. dmesg contains `PCIe link training gen 1 timeout!` which may be related and the last time it successfully mounted the linux-firmware package was updated via apt from 1.187.25 to 1.187.26. The older version no longer seems to be available to rollback to so unsure if related.

Anybody seen this before or know what to do here?

Prolly not, but I am a bit flummoxed at this point and could use some help sorting out the phone.

The problems started from minute one, the batter connector protective tab was partially attached to the coating inside the back of the phone and peeled a little patch off when I opened.
On boot I got the welcome screen, but like @Jetpac , I ran into the orientation problem, a scroll problem and a no timezone choices. Like him I solved with an external keyboards and in one case a good guess on what info was needed to finish setting up.

So, that got me started and I got to setting up the phone, nothing special, just adding a few programs, tweaking a few settings as far as theme and timezone, and upon returning to the desktop, I found I didn't have an app drawer any more. Odd, but I figured a reboot would do the trick, so the phone turned off...

And won't turn on again. I do sometimes get the light and vibration of a boot, but it doesn't go beyond that. I did try the reset button on the back, and the phone turned on, the indicator light was lit, but nothing displayed on the screen.

I've tried starting it with and without it being plugged in, tried an external display, and nothing.


I'm not really sure where to go from here, as a lack of a display makes it a bit tricky to interact with the phone.

I admit to being a noob.  I am pretty good at researching before asking a question, and I follow directions well, but I am limited in my ability to troubleshoot on my own. 

Has anyone on Manjaro (Phosh, but that shouldn't matter) switched to the userspace driver (ppkb-i2c) for the keyboard case?  If so, can you post how you did it?

I was hoping maybe I could just use the instructions for Arch starting at step 3:

https://forum.pine64.org/showthread.php?tid=16156

Unfortunately, I can't even get out the  gate because Manjaro Arm does  not seem to have a mkscr command (The boot.txt file says at the top to run "pp-uboot-mkscr" but that fails to with a "command not found" message. and there is no ".scr" file with a similar name on the boot directory).  There is a boot.scr file in the boot directory, and, yes, I am in that directory when issuing the commands.

Any help from someone using Manjaro Arm would be appreciated.

TIA

I just loaded Kodi after a few months, I just want to let everyone know about the progress that has been made.
Firslty Kodi is firstly a complete UI for DIY TV-box multimedia Linux distros, it is also an app for desktop OSs and mobile Linux and Android distros, it is an ultra flexible platform for streaming and other plugins and easily re-configured with easy to edit UI skins.
There is now a touch 'back' button in the Estouchy UI skin making the Phosh keyboard superfluous.
The latest build for Mobian has a new and quite good custom UI 'skin' which works well as long as you are not touching near the phosh keyboard touch area.
Some of the plugins I tried crashed when they worked in earlier builds but it can stream video and search in other plugins.

I recommend installing and playing with it, I have not tested it but I suspect you will still need your charge cable as in the past Kodi, like VLC, used a battery quickly though it has a quite universal playback codec library so it is rare to find unsupported media.  I have not found much media that the totem player would even play so I have no way to compare battery savings if any.

There is still plenty of work to be done on the easy to hack skin and possibly deeper issues but I can see the effort that has been put into this app.

If your install does not have the Estouchy skin(I experimented with several mobile tweaked skins a few months ago so not sure if this is me or Mobian) you find it by clicking the settings 'gear' - Interface - Skin - Skin
I am not sure how much of the upgrades are the Estouchy skin and how much is Mobian tweaks.

I have a new PinePhone, with a new SIM card, and the modem won't connect. The carrier assures me the SIM card is activated. (I went through 5 or 6 support people and I believe the last one actually knew what he was doing.)

The phone came with Manjaro installed. I'm looking at the Cellular Network section of the Settings app, sometimes I see a SIM 1, sometimes SIM 2, I've even seen SIM 4. If I select SIM 1 (or whatever number) and go to Select Network Operator it says "Current operator: none". If I hit the Scan For Networks button, I get one of these messages:

  Scanning networks failed: Object does not exist at path "/org/freedesktop/ModemManager1/Modem/1"
  Scanning networks failed: Cannot scan networks: not enabled yet

I suppose the first one is because the number keeps changing.

When I hit View Modem Details, I see an Enable Modem button and a Force Modem Restart button. I have tried both of those a few times, and they don't do anything as far as I can tell. I have rebooted the phone a few times also.

I suspected a command line equivalent of the Enable Modem button might give me better feedback, so I tried this: `mmcli -m 2 -e` and it said

  error: couldn't enable the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition'

And that, I guess, is the root problem. But I don't know what an invalid transition is so I can't troubleshoot any further without a hint.

Hello Good People,

Pine phone newbie here (altough I've been on Linux with my laptop for a couple of years). I've noticed the wifi disconnects after a while and it takes many attempts entering the password over and over to get it re-connected. Bit annoying. Any remedy? Any help appreciated.

Best

Matt

Are there any distros that suspend(sleep) work on. I carried my phone the last couple days as my only phone. It was great for everything except the battery. Even with the keyboard case and battery in that fully charged and the phone fully charged I barely made it through the work day without it going dead.