I noticed today that when using a wired headset, after making the first call with it all audio stops working on calls both incoming and outgoing. When this happens there are no audio devices listed in the sound section of settings, everything is just greyed out. Rebooting the phone fixes it until you use the headset again. (This is Arch+Phosh running from an SD card, updated as of yesterday.)

How come i keep getting this error

andi@andi-Lenovo-Z50-70:~/Documents/flash-it-master$ bash ./flash-it.sh
Sailfish OS Pine64 device flasher V0.3.3
======================================

Which image do you want to flash?
1) PinePhone 1.0 (Development) device
2) PinePhone 1.1 (Brave Heart) or 1.2 (Community Editions) device
3) PineTab device
4) PineTab Dev device
5) Pinephone Pro
#? 1
Downloading images...
https://github.com/sailfish-on-dontbeevi...-pinephone
u-boot.zip          100%[===================>]  3.56M  4.15MB/s    in 0.9s   
u-boot-sunxi-with-s 100%[===================>] 740.44K  4.40MB/s    in 0.2s   
Root filesystem image download failed. Aborting.

Hey there,

anyone managed that ?
My Pine64 was taking dust in a box with an old debian distro on it.
Then I decided I could maybe use it if I could put an OpenBSD on it, to replace another machine I have.

Unfortunately it keeps hanging at different points in the install process and is left in such a way that I have to reflash everything again.

To reach that point I overcame the hurdle of using screen appropriately on my mac (found the best info here and here). In short identifying correctly the serial device to use )

Then I was able to check that that page (explaining how to do with an LTS version) applied easily enough to the Pine64+ if taking appropriate files (not those of the LTS )

And now, I'm kinda stuck and it's bugging me.

Note : I tried to follow the instructions from OpenBSD.org for the PIne64+ but did not quite understand, or they don't work
That paragraph of the arm64 install page :

I am a frequent user of Libreoffice and I have password protected documents. Although keyboard works on everything it doesn't on document passwords. I note the arrow key on the toolbar which indicates a keyboard however I look everywhere for a concealed keyboard and it is simply not there. I even tried searching out a keyboard to install as an alternative but no luck.

Has anyone else run into this issue and if so how did you solve it?

1) I like it  
 2.) it needs to open the back and remove the battery to reset when it goes to sleep . lets say the back cover is getting to be easier to remove now.
3) the software for the system wont update the system . Every time I start the phone it calls to update.
4) I can watch the battery level drop while the phone does nothing. in 15 minutes it dropped to 86% from 100% fully charged over night.
5) the time out controls sorta work. they seem to have their own vary in time. I can set the screen time out at 2 minutes and it might be early or later. and the power timer seems to go at the same time as the screen setting.
6) the volume is too low even on high and the ear jack sorta is not a good fit for mono or stereo jacks
7) it would help to have a basic operators manual even if it is always being updated. l
8) I like it because many of you have tried to put way too much into the project. and your going to fail. try making the best basic phone first then adding the real good stuff. after you get the solid phone. it will sell.
9) can the phone have an optical (air) gap to prevent hacking? your already sucking the power from the battery so lower the CPU and gap it.
10) i used to work with dos and win3.1 everyday was hell. restart restart. edit config and reg. take long walks and yell at the walls. this is not much different than  those days. I still like the phone. send me a patch to fix the system updater and fix having to take the battery out. those 2 really suc.

I've got a question regarding a cool RockPro64 4GB board I recently acquired (the previous owner ran it once, concluded it was too much hassle compared to a RPI4 and sent it to me. It worked fine at his place before sending it to me);

When powered the only thing it does, regardless of peripherals connected or storage present, is flash the white LED and one of the ethernet LEDs continuously at something around 2-3Hz. I tried many things; different microSD cards, different card readers, different distros. I also tried disabling the SPI flash by grounding the clock pin; also results in the same behavior. When powered during this behavior the 5V GPOI pin is a steady 5V but the 3.3V seems to be "flashing" together with the LEDs as well.

Finally I tried hooking up the UART2 slot to a usb->UART adapter in order to maybe get something out of the board in that way. Nothing was showing on the UART output, but when I looked back at the RockPro64 suddenly the LED flashing pattern had changed. The board was booting up!

It turns out that I can reliably and  turn on the board (from a powered but "blink-looping") state by connecting the UART pins to a powered UART USB controller, but nothing else! (rebooting always seems to work fine, so only starting from a turned off state is problematic) Connecting either of the UART pins (8 or 10) to ground or the 3.3V volt supply doesn't start it either. 

I updated the firmware via the armbian-config menu, but that doesn't seem to make a difference.


Does anyone have any idea what might be causing this behavior? Is some kind of memory corrupted perhaps? perhaps a somewhat faulty 3.3V circuit? a short? Visually the board seems fine.

Any help in diagnosing this odd behaviour is welcome! Thanks in advance

Hi
 I use the Pi os a lot. Is it possible to put it on a pine book pro.

What other Distribution option are there?

Thanks

Shanta

None of mentioned root passwords authenticated :
root, password, manjaro, 123456

I have access as regular user logging via Pin but
root credentials are missing ?

Just updated Mobian, rebooted, and now no audio on calls. I tried rebooting a few times and it's still the same. (I didn't do dist-upgrade or install held back packages.)

Anyone else experience this problem? I do have a working image backup from about 5 days ago that can be restored to the eMMC. However for now to make or receive calls I'm booting up on the Arch SD card I made up recently and will try updating Mobian again over the next several days to see if further updates fix the problem. (I don't want to re-image the eMMC on a regular basis since that will wear the flash memory. I've only done it once so far since owning the phone.)

This is an invitation for people to report on their experience getting audio to work on the pine phone pro during phone calls.   Please let us know the following:

  1.  Are you able to get audio to work during phone calls?
  2.  If not, what are the specific problems you are having?
  3.  If so:
         a.  what operating system are you using?
         b.  what updates/tweeks need to take place after installing the OS in order for audio to work?