I've had my Pinephone for some weeks now, and I'm trying to solve one important nagging issue. 

The Broadband modem will just die and not come back up. I'm suspecting that it may be a weak or absent carrier signal but, I have very little to go on.

I'm not finding any  mmcli commands that would allow me to reboot the modem. 

When this happens, it's as if the device is gone, or has been completely unmounted and mmcli fails as there is no device and my only recourse is to reboot the system.

What would be the best approach to:

• Discover and remount the device if necessary
  
• Cycle the modem on if not active
  

After many failed experiments, I finally have a working version of moonlight running on my Pinebook Pro.

I messed with a lot of packages, so if I missed something, it's likely a new version of SDL (per this topic: https://github.com/moonlight-stream/moon...issues/509). Other than that, these PKGBUILD files and patches should make working versions of FFMpeg, linux kernel, and moonlight.

BIG NOTE: I did not generate checksums for these patch files. I'm providing these patches and PKGBUILD files with the intent of someone more knowledgeable and familiar with development on this platform to clean them up and potentially include them in future "official" releases.

I'll be looking at this thread periodically to answer questions.

https://github.com/danschdatsci/pbp-moonlight

I have decided to cancel my pinephone order because of financial problems, the sales team did not respond to my emails so instead I have contacted the support team. The support team said that they cancelled the shipping of my phone but that I would have to wait for the sales team to contact me for a refund. The sales team just blanks me. Now I am at a spot where I will not get my phone because it won't be shipped to me nor will I get a refund for it. If someone here is capable of helping me please do so.

Hi!

Yesterday, I rebooted my PBP and it did not boot again. The green power led is not on.

I have 2 power supplies, and I see that the red light is not lit with the one I used yesterday. I have created a support ticket for this defective power supply.
So it could be I drained the battery to 0%.
I plugged the PBP all the night to recharge the battery.

I tried to unplug the battery and use the bypass cable, long press on the power button, press the reset button, but no success.

I tried to boot a SD card but no success too.

Before this state, the OS on the eMMC and on the SDCard were working fine (Gentoo like all my PC and other ARM servers).

I don't have the official debug cable, but I can make one with a USB FTDI cable and a hacked jack cable.  Or do you have any reference I can use instead? or wait until it's available on the Pine Store?

I did NOT flash the SPI nor U-BOOT, they are working and I don't want to brick the boot process. I only did a repartition on the existing Manjaro, keeping the start offset of the first partition.

What operation can I do to unbrick it?

Thank you very much!

Kind regards,
Xavier

Hi guys - 
I haven't been able to use texting for about 2 weeks now - it worked when I first got it for about 10 days, and now it won't send or receive. I'm using plasma-mobile and the default app is "spacebar". I tried uninstalling it and reinstalling it, what else can I try? I don't use a data plan - I plug the sim into my samsung s4, and texting works just fine, so it's not my carrier. 

Let me know what I should try, thank you!

Hello,

I broke my Arch system on my Pinephone with an incomplete update. Now I can't boot from eMMC, the loading screen roll forever.

I tried to flash Jumpdrive to SSD card. But my Pinephone won't boot to SSD card, it start Arch from eMMC anyway.

There is a solution to repair my Pinephone ? If i can chroot or something it could be nice...

Thank you !

Was delivered today, so far not so good, plagued with intermittent issues,  

Half the start ups end with this



lots of times the content is compacted into half the screen, many boxes extend beyond the screen, did get a new phone number on a TP sim,

first couple of calls out would not hang up, calls do come in, when it remains working, I've let it sit and when picked it back up a no modem message was on the screen, 

Other small annoyances as well

Trying to access what OS is looking the best from here, difficult to gauge so far

any tips appreciated no plans to give up yet 

I'm trying to get Talos working on my oldish Rock64 board. The PCB says, "ROCK64 V2.0 2017." The Talos devs have a distribution for ROCK64, and one of their engineers says he's got it running on a ROCK64 board. His says "V3 2019." His works, mine doesn't. But mine works just fine when it's running Ubuntu.

According to my packet sniffer, my ROCK64 never sends a DHCPDISCOVER packet. But it seems like the ROCK64 thinks it sent one, and it's waiting for a reply that never comes.

Does it seem likely that there's a hardware or firmware difference between V2 and V3 that's preventing the Talos Linux kernel from talking to the ethernet? Or does it seem more likely that I've messed up my network somehow?

I'm attaching two excerpts from the console log running Talos.

Attached Files

  dmesg1.txt (Size: 1.68 KB / Downloads: 410)
  dmesg2.txt (Size: 1.03 KB / Downloads: 399)

My keyboard is misaligned. nobody seems to know how to fix it including pine64 now that its out of warranty. so now I have a 150 dollar paper weight. As far as i know, nobody can service the pinephone. So now i'm in a creek without a paddle.

Anyone have any experiences (bad or good) with the IP67 rated water resistance of the Pinetime?

I'm used to not taking off my Galaxy Watch Active for pool/shower activities. I figure the Pinetime is ok for shower use or washing hands with sink water....but swimming probably not unless you're just using it at the side of the pool with a nice frosty beverage and not doing any kind of diving down underwater with it.  1 meter is not very deep.

I have 3 of em, so I guess if I did kill it I still have a Plan B and C watch.