hi, im trying to set up Linux (Beta) on my rockpro64, my Chromium OS version is 76.0.3809.52 (official build) (32 bit). I am following the steps of the url: https://support.google.com/chromebook/an...?hl=es-419 but step 5 is never executed.

i restart my rockpro, and im check that my virtual machine is up to date, but always when i select check for update Under 'cros-termina', I always get the same message  'Status - Component not updated'

Is there any way to fix this bug?

Regards, and thank you very much

I have been experiencing the exact problem detailed in the PinePhone FAQ: voice calling and outgoing SMS work fine, but incoming SMS is spotty, at best.  (The instructions given in the FAQ regarding deleting old messages has no effect.)  I'd say that only about 10% of received SMS messages are coming through.

Using mmcli with AT-commands I've been able to determine that the Quectel modem IS receiving all the SMS messages, but for some reason they are not being picked up by the chat app in the UI.  It seems as though either the modem is not passing the incoming SMS to the USB bus as it should--unlikely, I'd say--or, more likely, the Phosh chat app isn't picking them up from the USB.

To be specific, using AT+CMGR at the command line, I can see the messages, but only in hexadecimal.  When I send a test-text to the PinePhone, within 30 seconds I can verify that the modem has received the message using AT+CMGL, which displays the time-stamp of the message, yet no message shows up in "Chats."  I have verified that the relevant modem defaults are correct.  E.g., AT+CNMI=2,1,0,0,0.

Any info to help resolve this issue would be greatly appreciated.

My PinePhone details:
Hardware v1.2b
Manjaro-Phosh-beta4
Quectel firmware v01.002.07

Thanks,
Jay

I read the KDE convergence package 32/3GB page in the store, didn't see anything mentioned, the latest mainboard is still the 1.2b? The 1.2b is also what will be restocked when mainboards become available I gather later this month?
thanks
https://pine64.com/product/pinephone-com...46c16e2e66

edit: sorry, I have looked at the wiki hardware section before, I guess anything as major as a change to the board would be listed there
https://wiki.pine64.org/wiki/PinePhone#H..._revisions

I recently got my 3GB/32GB MAINBOARD - "special offer for BraveHeart and UBPorts owners"

Please note, I have read the discussions wrt anx7688
(e.g. https://forum.pine64.org/showthread.php?tid=12506 ) prior to submission. It might be related, but not overlapping.

If anyone could suggest e.g. how to re-write the possible wrong flashed fw for gc2145 (or whatever might be the actual problem) I would be happy to try it out as I am kind of stuck right now. The support team extended the warranty for some time for me to be able to try to resolve these issues.

I replaced the motherboard, installed Manjaro on eMMC, could boot, also Manjaro and postmarket can boot from SD. All worked fine incl. wifi etc. However, the anx7688 firmware step failed (anx7688-fw.bin downloaded ok, 32752 bytes,  and copied to /lib/firmware/; timeout during writing according to dmesg, just as others have experienced in separate thread; I did try postmarket and manjaro, recent and older, with usb charging on and off, from eMMC and from SD).


However, on top of that, AFTER the anx7688-attempts suddenly WIFI does NOT work anymore and BLUETOOTH adapter is not found at all (if I understand it correctly). This wifi/bluetooth error is the same for all 3 bootable OSes I have - for which it worked flawlessly until my anx7688 update mess. I even tried re-flashing the eMMC-firmware with an older postmarketOS version, still no WIFI.

I have triple-checked the mainboard connectors. I even replaced the motherboard with the old (ubports) mainboard and when using that, wifi etc works fine just as expected.

In dmesg I can find errors related to writing the anx7688-fw.bin. Furthermore, there are other types of errors related to gc2145-init.bin, Goodix_917S_cfg.bin,  platform regulatory.db - might it be some problem writing the firmware?

dmesg (cut outs) which (at least for me) looks like related to possible errors:

...
[    0.931868] hub 5-0:1.0: USB hub found
[    0.931918] hub 5-0:1.0: 1 port detected
[    0.933920] input: gpio-vibrator as /devices/platform/vibrator/input/input2
[    1.036223] Goodix-TS 1-005d: ID 917S, version: 0200
[    1.039915] Goodix-TS 1-005d: Direct firmware load for goodix_917S_cfg.bin failed with error -2
[    1.045448] sun50i-a64-pinctrl 1c20800.pinctrl: supply vcc-pe not found, using dummy regulator
[    1.046393] input: Goodix Capacitive TouchScreen as /devices/platform/soc/1c2ac00.i2c/i2c-1/1-005d/input/input3

...
[    6.676581] Bluetooth: Core ver 2.22
[    6.676760] NET: Registered protocol family 31
[    6.676765] Bluetooth: HCI device and connection manager initialized
[    6.676796] Bluetooth: HCI socket layer initialized
[    6.676806] Bluetooth: L2CAP socket layer initialized
[    6.676832] Bluetooth: SCO socket layer initialized

[    6.683059] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    6.687264] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    6.687281] cfg80211: failed to load regulatory.db
[    6.695279] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[    6.698914] sun4i-drm display-engine: [drm] fb0: sun4i-drmdrmfb frame buffer device

[    6.721740] Bluetooth: HCI UART driver ver 2.3
[    6.721767] Bluetooth: HCI UART protocol H4 registered
[    6.721862] Bluetooth: HCI UART protocol LL registered
[    6.721929] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    6.722326] Bluetooth: HCI UART protocol Broadcom registered
[    6.722453] dw-apb-uart 1c28400.serial: failed to request DMA
[    6.726313] sun6i-mipi-dsi 1ca0000.dsi: Attached device xbd599

...
[  24.390254] modem-power serial1-0: Your modem has an outdated firmware. Latest know version is EG25GGBR07A08M2G_01.002.07. Consider updating.
...
[  25.997612] sun6i-csi 1cb0000.csi: Direct firmware load for gc2145-init.bin failed with error -2
[  25.997654] gc2145 4-003c: Failed to read firmware gc2145-init.bin, continuing anyway...
...
[  30.871035] sun6i-csi 1cb0000.csi: Direct firmware load for gc2145-init.bin failed with error -2
[  30.871049] gc2145 4-003c: Failed to read firmware gc2145-init.bin, continuing anyway...
...several such fails...


This is what happens when I try to flash anx7688:

[  123.277492] anx7688 1-0028: cable removed
[  123.295868] anx7688 1-0028: power disabled
[  123.296173] anx7688 1-0028: setting vbus_in current limit to 500000 mA
[  123.296445] anx7688 1-0028: disabling vbus_in power path
[  123.296580] anx7688 1-0028: enabling USB BC 1.2 detection
[  123.343891] anx7688 1-0028: power enabled
[  123.445847] anx7688 1-0028: eeprom wr 10 02 00 26 02 19 fb 00 00 00 00 00 02 02 57 90 72
[  123.447429] anx7688 1-0028: eeprom wr 20 05 e4 f0 a3 e0 44 02 f0 e0 54 fd f0 12 76 65 02
[  123.457601] anx7688 1-0028: timeout waiting for eeprom
[  123.479855] anx7688 1-0028: power disabled
[  123.481039] anx7688 1-0028: BC 1.2 result: SDP
[  123.481071] anx7688 1-0028: cable inserted
[  123.527908] anx7688 1-0028: power enabled

I can open SD card in a file manager and also copy, paste, delete, etc., but cannot directly play a song from it, I need to copy the song file and paste it to the internal memory, and then play it.

I have the 1.2b Manjaro edition phone.  I'm finding that ethernet through the convergence dock works if I am not plugging in the power cable at the same time.  


I have seen a lot of mention of HDMI issues when power is applied, but that seemed a product of using the more modern PD power supplies.  Mine is just a simple 5V/2.1A power supply, so that shouldn't be the issue.  

I also found the same issue in Mobian.  So it appears this may be a Deban issue.

If anyone has insight, I'd appreciate it!

I'm attempting to try out Arch from a version of mid November running from my SDCard.  (That's the version from the multi-boot image.)  I can't even get to the first step of updating, because I can't get the keyboard to show itself.  The icon is in the bottom right, but clicking on it or on any text box is failing to bring it up.  Anyone have thoughts?

I'm on 1.2b, the Manjaro editon.  (The Manjaro install in the emmc is running fine.)

I just researched and ordered a microSD card and SD to micro adapter for my laptop so I can flash and install OS's for Pinephone. In reading through the wiki and elsewhere I also read about flashing the eMMc, which I gather happens from putting what's needed on the microSD which you then put in the phone.

However, I also read about "usb to emmc" adapter, and see one offered in the Pine Store. This would seem to imply a removable eMMc drive that you mess with when removed from the phone. Where is it? I see the 2 card slots, but I don't see anything else removable. I've done google image search, but don't see anything like that in the phone. I've never owned an eMMc. I thought there might be an arrow pointing to it in the wiki.
thanks

Forgive me if this has been asked, but I'm surprised to find that search on this forum is coming up with nothing.  

After an update of Mobian, I am finding ethernet only works when power is not applied to the dock. You can't charge and use ethernet at the same time. This is not one of these fancy new power supplies. It's only 5V/2.1A. Anyone have a work-around?

Oh, and I'm on 1.2b (Manjaro edition), booting off of SDcard.

Edit: When I say "the dock" I'm referring to the Convergence Dock, that comes with the PinePhone.

Since alarms set up with GNOME Clocks can't yet wake up the device from suspend, I wrote a small alarm app exploring how to set up systemd timers that wake up the system through the interal RTC device.

For now there is just one alarm available and not recurring but this is just an UI issue, not a limitation of the systemd timers.

You can install it through "make install" on any OS that has systemd or, for Mobian, use the binary packages linked in the README: 

https://gitlab.gnome.org/kailueke/wake-mobile


Eventually GNOME Clocks will be able to wake the device, too, but this is still in development and requires an approach of making the necessary Linux capabilities available to regular users.
I worked around this limitation in my app by using a setuid binary that can only write out a drop-in unit file for the systemd timer.