I've a kernel build with DWC2/3 drivers and dual-role support enabled. I'm unable to see any devices in /sys/class/udc. Is there anyone who has worked on this? As I understand I need:

CONFIG_USB_DWC3=y
CONFIG_USB_DWC3_DUAL_ROLE=y
CONFIG_USB_GADGET=y
CONFIG_USB_CONFIGFS=y
CONFIG_USB_ETH=y


I see two controllers:
# ls /sys/bus/platform/drivers/dwc3
bind  fe800000.usb  fe900000.usb  module  uevent  unbind

I'm not able to get any more information by inspecting that filesystem. For my config, I have:
# cat .config | grep USB_DWC3
CONFIG_USB_DWC3=m
# CONFIG_USB_DWC3_ULPI is not set
# CONFIG_USB_DWC3_HOST is not set
# CONFIG_USB_DWC3_GADGET is not set
CONFIG_USB_DWC3_DUAL_ROLE=y
CONFIG_USB_DWC3_HAPS=m
CONFIG_USB_DWC3_MESON_G12A=m
CONFIG_USB_DWC3_OF_SIMPLE=m


# cat .config | grep USB_GADGET
CONFIG_USB_GADGET=m
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
# CONFIG_USB_GADGET_DEBUG_FS is not set
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2
# CONFIG_USB_GADGET_XILINX is not set
CONFIG_USB_GADGETFS=m


# cat .config | grep USB_CONFIGFS
CONFIG_USB_CONFIGFS=m
CONFIG_USB_CONFIGFS_SERIAL=y
CONFIG_USB_CONFIGFS_ACM=y
CONFIG_USB_CONFIGFS_OBEX=y
CONFIG_USB_CONFIGFS_NCM=y
CONFIG_USB_CONFIGFS_ECM=y
CONFIG_USB_CONFIGFS_ECM_SUBSET=y
CONFIG_USB_CONFIGFS_RNDIS=y
CONFIG_USB_CONFIGFS_EEM=y
# CONFIG_USB_CONFIGFS_PHONET is not set
CONFIG_USB_CONFIGFS_MASS_STORAGE=y
CONFIG_USB_CONFIGFS_F_LB_SS=y
CONFIG_USB_CONFIGFS_F_FS=y
CONFIG_USB_CONFIGFS_F_UAC1=y
# CONFIG_USB_CONFIGFS_F_UAC1_LEGACY is not set
CONFIG_USB_CONFIGFS_F_UAC2=y
CONFIG_USB_CONFIGFS_F_MIDI=y
CONFIG_USB_CONFIGFS_F_HID=y
CONFIG_USB_CONFIGFS_F_UVC=y
CONFIG_USB_CONFIGFS_F_PRINTER=y

Hi everyone,

I received my pinephone a while ago however I didn't really have time to fiddle around with it.  I set a password for pmOS but I can't seem to remember it, or maybe I mistakenly touched a different number during password creation.

I bought a 128gb SD card from sandisk, flashed the pureOS image onto the SD using balena etcher ( I also tried with Mobian), but I cannot format the phone to factory settings. I cannot get past the lockscreen, I've seen posts where people have said to chroot, but I don't know how and I don't need any information that is on the phone. I just want to erase the old OS completely and make a new password for pureOS. There's a reset button behind the phone, but it does nothing.

During launch it says "PureOS for Pinephone" but...

As of right now, I am just stuck on the lockscreen of the phone.

Thanks!

Ok, got mine a few days ago and have spent a few hours with it.

BT worked out of the box, it was flawless; it paired instantly to a little portable BT keyboard.  Then updates broke it.

Now this is in dmesg:

I've tried installing several VOIP clients. So far all are incompatible with aarch64. Is there any available?

Hi all !

I am very pleased to have a Pinephone PMOS Convergence Edition and distro-hope since day 1, even if I think I'll settle on Mobian as it is the most stable of all.

But there is one thing that I didn't encounter anywhere else on this forum nor Reddit : the camera works with 1FPS as expected at this development stage, but there is a problem that I saw on every single os that as a camera software that is working (mainly Mobian, ArchARM and UBTouch) : preview and photos seems to have odd colors, greenish saturated.

I suppose it might be a software issue because that problem exists with the back and the front camera. I also tried to turn on and the hardware killswitches without success.

Could it be an hardware issue ?

Thanks to all !

not so long ago I got my pbpro.
with installed manjaro 20.03 kde.
I created a bootable USB stick with debian. and downloaded the latest image of Manjaro  XFCE 20.08.
Before flashing, I checked with the LSBLK command that emms is in mmcblk2. and copied DD.
after that everything worked.
Today I decided to return to where. Only now LSBLK returned me that emms is on mmcblk1. ok uploaded there.
after the end of the process, turned off the laptop. but it's frozen. 
I waited for a while and turned it off by holding the power button for 15 seconds.

after which the laptop will not turn on. the power-on indicator is neither red nor green. the screen does not show anything either.
only the cpu temperature is an indirect sign of operation. after a short press on the power supply after a short time, it becomes warm. after 15 pressing the power button it cools down quickly.

what will be the assumptions about what happened and what to do about it?

I'm not sure how much this will help us but here is a link with reading, maybe.  https://www.cnx-software.com/2020/09/18/...velopment/

Hi Folks

Got a pinetab for sale with keyboard and cable's. Moving house and just dont have time to mess about. 

£130.00  (i'll pay the shipping)  - UK only

Accept paypal only and happy to list on ebay, if preferred. 

PM if you have any questions 

Sun

I've just ordered my first pine64 product, a USD 199.99 phone.  The only payment method accepted by pine64 was PayPal.  Other users express their dissatisfaction with this in other threads on this forum.

I want to highlight a frequenly overlooked additional cost due to PayPal, if you pay in a non-USD currency.  PayPal uses its own currency rate to convert pine64's USD price.  My currency is Australian dollar, AUD.  PayPal's exchange rate was 4.4% worse than the fair rate.  This is how currency exchangers typically make money.  The fair rate is the representative mid-price (between bids and offers) by global currency traders, e.g. banks.  One data source of the fair market exchange rates is https://www.xe.com, but there are many others.

The total amount of my order was
USD 226.99 = USD 199.99 (phone) + USD 27.00 (shipping).
This total at the time of the purchase at fair exchange rate of 0.7299 USD/AUD should have equalled:
AUD 310.99 = USD 226.99 / 0.7299.  Instead, PayPal charged me
AUD 324.93 = USD 226.99 / 0.6986, quoting PayPal's exchange rate 0.6986 USD per 1 AUD.
Thus, I was forced by PayPal to overpay ~AUD 14 ~USD 10 for my order, a ~4.4% surcharge.  Not a huge amount, but it affects each non-USD payer every purchase!  I'd rather give this extra 4.4% to an open source project than to PayPal.

Pine64 is my favorite company these days thanks for the products they create and the way they do things.  Except for this unpleasant payment methods situation.  Cryptocurrencies seem like such a perfect fit for both Pine64 and its typical customers.  But of course other payment methods (credit cards, bank transfers, etc.) could be natural to have too, as suggested elsewhere on this forum.

I'd like to keep buying more of Pine64's great products without the sour feeling that each time I have to pay 4.4% extra to PayPal.  Bring better payment methods to us, Pine64!

I was interested to read in the September update about a PineTime manufacturing issue ("involved the memory protection, which was still enabled") that there are plans to fix.

I understood the memory protection is part of the APPROTECT register in the UICR flash page and can therefore be set or cleared by an OTA update. Certainly I was planning to update the wasp-reloader to ensure that it is capable of updating the UICR to ensure it will automatically clear the protection bits during an OTA update.

Does that sound right?