I have a Pine64 from the original Kickstarter (2016.) It boots from a 32GB SD card, which I've imaged from an Ubuntu16 Pine64 image file. 

I've created a full disk backup of this 32GB SD card using AOMEI Backupper, and then restored the entire disk to a new 64GB SD card. The restore is successful, and the disk looks OK, but the 64GB card won't boot. Putting it in the Pine64 and powering on simply remains at a black screen (the original SD boots as soon as I plug the Pine64 in. I don't have to press a "Start" button or anything.) 

I have also tried this with a 256 SD card, with the same results. 

I have tried copying the entire 32GB SD card with DD in linux, and restoring via DD. Same problem. 

What am I missing. Does the new disk have to have a boot sector activated or something?

I absolutely can't see the difference (see image for full details about the drive and copy)...



https://ibb.co/6rXMvv3 (If image link is broken)

   

Hi guys!
Does anyone know when new BXE-4-32 GPU drivers will be available for Linux Kernel 6.x?
Thanks for reply.

Hello,

I've been using the PinePhone regularly for about half a year. Calls and SMS have been reliable, with the notable exception of the following problem that I would like to understand, and hopefully solve:

If I send a SMS to a phone that's offline, the expected behaviour of any SMS service is that the message is temporarily stored by the carrier, and when the receiver phone is later brought online, it gets the message delivered. For some reason, this isn't the case for the messages I send from the PinePhone. Messages are delivered properly when the receiver is online, but they never reach their destination if it was offline at the time of sending.

I tried with two different carriers and both 3G and 4G networks for each: the problem is systematic with the PinePhone, while messages are delivered properly when the same SIM card is used in another phone. The problem also persisted across various upgrades of the modem firmware, including ADSP.

When logged in to my user account on my carrier's website, I can see that the messages were successfully sent.

To me, this looks like the PinePhone sends its messages together with some kind of metadata meaning "do not attempt later delivery, instead discard the message if the receiver is unreachable". Could anyone confirm this? Can it be changed and how? I couldn't find any information on that matter and to be honest I'm quite surprised to be the first one to bring this up.

Alpinelinux in QEMU

I have used the introduction from astr0baby and a few other internet sources and came up with a working solution to boot Alpinelinux in QEMU on the Pinebook Pro. The settings are relatively simple and should work with other target ISOs in a similar way. There is no graphics support, yet. The host distro used here is Manjaro. There might be some differences with other distros. Mind you, this describes how to run an arch64 ISO on an arch64 system.

Install Qemu and create a folder to keep all files together:

• maybe set your timezone
  
• you will be asked which drive you want to use: vda
  
• what kind of installation you want: sys
  

• add -accel kvm
  
• you can switch [backcolor=#f6f8fa]-cpu[/backcolor] to host
  

Quote:qemu-system-aarch64: kvm_init_vcpu: kvm_arch_init_vcpu failed (0): Invalid argument

okay, so my new PinePhone arrived, yay! and after a tricky challenge to get past the user registration screen, I am now ready to do some app development.  I have previous experience with iOS and Android, and currently playing around with Zig.  However I am new to Linux development, and from my brief bit of research I can see GUI options using SDL or GTK...  Do we currently have a 'getting started' as an App developer type resource?  maybe a template very basic GUI App? responding to orientation events, life cycle events etc, or is someone able to give me some pointers please?  Something low level like single header C libs linking into my Zig would be ideal.  i.e. I have no interest in giant frameworks with dependency hell.  Alternative approach would be something like a unikernal template with a framebuffer starting point?  I am open to suggestions

Hello, I've been using jabber with chatty, I like it's simple interface. But I have the problem that omemo encryption works not with all contacts and when the phone goes into ibernation encrypted messages are not unencrypted after unlocking the phone. Is there a way around?

Does anyone have a definite, exact, way to get the keyboard working for characters such as '|' which are on the front bevel of the function keys? Please.

There were various posts and threads I followed, which loaded the so-called "userland" driver, which I built, and which I know installed, since it disabled any functioning from the pine phone keyboard.

Some (or maybe all) of these posts come from people who may be smarter than myself. But can we have an exact , EXACT, set of steps? It's just surreal that we have instructions making crucial changes to the boot sequence etc., which also include steps such as "To save changes and close Nano, type CTRL-X, Y, and Enter."

I mean really, they are giving somewhat vague instructions about how to create daemons and drivers, and assuming that a person performing those would need exact keystrokes for how to save a file using nano???? Wow.

What makes PinePhone a phone? Because it will make Phone Calls and send Text Messages!

We’re porting Apache NuttX RTOS (Real-Time Operating System) to PinePhone. Today let’s turn NuttX into a Feature Phone…

1. Outgoing and Incoming Phone Calls over 4G

2. Send and receive SMS Text Messages

3. Why we prefer Encoded PDU Messages for SMS

4. Programming the 4G LTE Modem with Apache NuttX RTOS

5. Doing all these over UART vs USB


Read on for more...

NuttX RTOS for PinePhone: Phone Calls and Text Messages

I have connected the headphone-to-UART adapter to the PinePhone Pro, flipped the privacy switch #6 down and started the phone.




To my surprise, the only nessages I see are some sellected messages from the Linux kernel:

hi all,

Some weeks ago it suddenly came an issue on my PinePhone with calls. When I made a call, it rang the first tune, but later it hung up, simply it stopped calling. I use Mobian OS on it.

I've been searching for any sollution , but I can't find any. I've tried installing several OS, like PostmarketOS phosh, and Manjaro Plasma Mobile, even Postmarket Plasma Mobile. And on all of them it keeps the same issue. I've noticed that when I call on some mobile phones (always the same), it only rings the first tune and hangs up, but if I call on another mobile phones, it simply runs and makes the call ok. Calling to the landline it works fine too.

It is really strange, doesn't it? Should be a problem on the PinePhone itself?