Hello everyone, I have a small problem I wanted to change os on my Pinephone but Emmc na is displayed more when I use BalenaEtcher or Gparted and the phone does not want to start anymore someone would have a solution please

Hello everybody,

I am trying to make a fresh install on my Pinephone, but it results in a device that is not booting anymore. I am flashing mobian-installer-pinephone-phosh-20220621.img to eMMC and the installation works as usual. After the installation I run apt update and apt upgrade and get this message in the status bar:

Low Disk Space on "Filesystem root"
The volume "Filesystem root" has only
166.3 MB disk space remaining.

The update process shows a littlebit later: No more disk space available.

Ahoj,

when will the Pinecil be available again?

On the Pinecil's page in the pine64 online shop it shows "Out of stock", while on this availability page it shows that there should be some available.

I want to place a bigger order at pine64.com, and one of the pieces I want to order is the Pinecil.

I want to order all in one batch to save on shipping costs. (Or, can I order it now and get it shipped to me when it is available again, without extra shipping fee?)

Regards!

---

Update 2022-10-18: It is available, version 2, here.

Hi,
I noticed that Megi (i.e. Ondřej Jirman at https://xnux.eu/log/#069) has recently been working on calibrating the IMX258 sensor.
But is it Pine's plan to have people calibrate at home like he is doing, instead of calibrating at the factory?
There's a reason why companies like Foxconn calibrate every sensor at the factory: It's because every single sensor is slightly different.
Without special equipment, there is no reliable way to calibrate a color Bayer sensor at home.
Now, if Pine had used a grayscale (B&W) sensor then maybe calibration would be possible, but they didn't.
So what then is the actual plan once Megi is done?
Will his code be used at the factory?
If yes, will each person who buys a PinephonePro receive a file containing calibration info for the phone?
Megi points out that unlike other phones, the Pinephones don't include an EEPROM to store calibration parameters, so it will have to be in a file somewhere.
And how will people who have already bought the phone get theirs calibrated?

Hi,

I am from HK and would like to pre-order the Pinebook Pro. However, I cannot find "Hong Kong" in the Country list. Is it possible to ship to HK?

Thanks

Almost every time I connect via minicom to ttyUSB1 to get gps messages all ttyUSB ports disappear from /dev and usually but not always reappear after minutes. Dmesg says this:
usb usb2-port1: disabled by hub (EMI?), re-enabling...
usb 2-1: USB disconnect, device number 3
option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
option 2-1:1.0: device disconnected
option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
option 2-1:1.1: device disconnected
option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
option 2-1:1.2: device disconnected
option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
option 2-1:1.3: device disconnected
qmi_wwan 2-1:1.4 wwan0: unregister 'qmi_wwan' usb-1c1b000.usb-1, WWAN/QMI device


rarely connection works and I can see NMEA messages.
can anybody help? thanks 

PS
I'm on Mobian Bookworm

i am trying to update archlinux dreemurrs 20220124 from distro demo image 2021-11-20 and i get error

 

Hi, 

I've been trying for 3 days to get an linux image to boot on my RockPro64 without any success. I followed the initial sticky forum message and ended up waiting a day for 0% downloaded from various servers. 

Then I found the latest daily images and used a boot installer by concatenating the FW and partition, and burning the img to an SD in linux with dd. I cant seem to get a new single partition SD card to boot, I only had success with an SD I had used with my Pi - that has 3 or 4 partitions on it.

Anyway the new May 2022 installer got to 100%, then I got a flashing cursor where I could type, rebooted and back to the installer again.  Also, has anyone actually got a RockPro64 to install Debian and boot to it in the last 3 months ? If so, was there anything you had to do apart from create the SD image, answers the installer questions and let it install ? 

For the serial UART output, I watch it with 115200 baud, and I can see the initial messages, then it starts outputting garbage. Any reason it switches like that ? Is the first part the rom/boot at 115200, and then does the baud rate change when its running the installer ? 

NOTICE:  BL31: Built : 23:34:19, May 13 2022
INFO:    GICv3 with legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    Maximum SPI INTID supported: 287
INFO:    plat_rockchip_pmu_init(1624): pd status 3e
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
WARNING: BL31: cortex_a53: CPU workaround for 1530924 was missing!
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9
⸮⸮⸮⸮⸮_O⸮bWWG⸮_GG_⸮f⸮⸮⸮G⸮c⸮"gGGG^gGG⸮⸮GoW_WW⸮O⸮WWF⸮_Ww⸮ݾ_⸮⸮⸮^⸮gW_gG_wo⸮GE⸮OOO}_fWWVGfDWFg_⸮FWF/⸮NFND⸮VgFFF⸮oWFGowFgoFGGF'O⸮⸮^____O⸮FG⸮gǮ⸮ϧDoOn⸮/F⸮F_fooW⸮NngDwDFFD_⸮FFogO⸮&G_FF_⸮WFFWnFFDWGFWFGFW⸮⸮W⸮FGGFGFFGGD⸮WFFFGDFFGGWF⸮FFDfFfDGWF⸮FWWF⸮FnW_ooGOFGw^Wo⸮n⸮v⸮FOFg_FnDNFF_g⸮_FOODWOOFO_"F⸮V⸮V⸮FV^GW.FgOV^D⸮⸮FVfOOD⸮W⸮O⸮OoG⸮MgFg⸮O~_g⸮⸮F/D_/F⸮g⸮e>⸮FWGF^GbFg_⸮FG⸮⸮F⸮G_F⸮⸮F\_FOf_G⸮nFO_bOOfF⸮⸮G_b__OF⸮_FGGF_⸮⸮VFDG⸮⸮GF⸮⸮FOFg⸮⸮FFGO_fF_F⸮⸮⸮⸮FW_O⸮DOWO7W⸮⸮oD⸮DFGFGD⸮O⸮WN/Fw⸮⸮F⸮G/o⸮w⸮wODG⸮wOGNF⸮⸮Wf_o⸮F_o^^/VF/⸮wFGwGwFGG⸮⸮FOF?FWGWWWWVWoWN"NG^gF"Vo"FW6o6oWG⸮W6ogV__R__VW⸮VOg⸮_7FO⸮_⸮f⸮⸮vWOFg'_nw⸮⸮⸮OnF⸮⸮V⸮⸮VFW_~⸮FG_⸮F&⸮nF⸮nFTGOn⸮⸮g⸮^G'N'O⸮G_⸮⸮GFOWNo>o"f7_oGF_⸮TgO⸮VoW⸮⸮G^F_^GN^⸮N__GFoOFGNF_⸮o⸮FGf_fWf_ofO⸮f⸮⸮dw⸮⸮gW_⸮⸮⸮⸮NGddOFnG⸮gVF⸮⸮FGOFGVWO^GOFWVOgFgOF⸮GnGFnF⸮GFGF⸮⸮g_g_⸮⸮oG_g_GV_w_wO⸮Gg⸮⸮VOvWG_WV_OOOTGoOGoO⸮GwGGLNWWVW⸮OvF^gT⸮WVG⸮O⸮G⸮⸮V⸮wFw⸮V⸮^⸮oG⸮⸮GVGOG⸮GWVOGN⸮wVB⸮VwOO⸮o⸮DG⸮GGBWf_oODGW⸮⸮GWFGGGWoOGTGdNoGG⸮D⸮NOOGFOGGWoFGoNf⸮NoGFgFogG⸮G⸮⸮'7⸮FfMOTogϯ_⸮FFFFFFF⸮FFFF⸮FDFF⸮⸮⸮FFFF⸮DF⸮FFFFFFFFFFFFnFF⸮>^FDFFNvFF~^F&N>FF⸮⸮vFF^F⸮NfffFF^FF⸮>D⸮^FFNvF&NFvNF&^Fv⸮tFF⸮F&F⸮⸮F.>ffFFF⸮vF&F⸮NFNG^F^FN⸮tN>FN⸮FNF⸮N⸮F⸮vff.⸮FG^FfFNN⸮F.fFv⸮F>F⸮f^FNFN^F>F^G⸮F&ff&f⸮F⸮⸮⸮lN⸮fNVfN&⸮fGf⸮N.⸮^vGv⸮v⸮GF⸮⸮f$⸮vG⸮N>^^⸮GVf⸮f⸮GG^⸮⸮n⸮NFFF⸮FFvFF⸮FFFF⸮FFFF⸮FFFFF⸮FFFFDFFDF⸮FFFFFFFFFFFFF^FFFFFFFFFFFFDFFFFFFFF⸮FFFF⸮FFFFFFFFFFFFFFFFFF
FFFF⸮FFFFF⸮FFfFF⸮FFF&⸮FFFDDFFFFFFFFFF⸮FFFFFF⸮FF⸮FFFvFFFFFFFFFF&FFFFFFFFFFFFFFFF⸮^FFFFFFFFFFFFFFFFFFFfFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF&FFFFFFFFFFFFFFFFDFFvFFFFFF^FFFFFFFDFFFFFFFFFFFFFFDFFFDFFF^_OwO&W_G.FFFFF.FFFFFFN⸮FFFFFFFFFF&FF⸮FFF⸮⸮F^FDd⸮FFFFFFf>FFFF&FFFF.FFFDF&OFNVF.^^GNfF⸮vV.⸮v

I have three Pinephones one phone is on stock firmware, one phone is the opensource firmware, and the other phone I flashed the open source firmware but returned it back to stock firmware. The phone I know is on stock firmware I know which one it is but I need to know which is on the opensource firmware and to know if the stock firmware took in the second phone. Is there an AT command or some other command to tell me what firmware I am on?

Of all the OS images available which is the most advanced in terms of power efficiency?

I worked on cellphones at Qualcomm for ~tens years.  I'm very interested in this topic