If I cannot get any support or sufficient support in this forum, where can I get some regarding Pinephone Pro Audio ?

The audio and phone calls issue is plaguing many users, including my self.  Rendering the phone useless, to be tested as a "daily driver".

I had been battling this audio calls issue for a month, to get Pinephone Pro to behave like a "phone", and no avail.

Is there a sub-forum that deals with this major blow-back against the hardware I am trying to adapt, and others too?  Is there a unified section that gives some better idea if the issue is related to Pulseaudio, Wirepipe, modem settings.. etc...

I do not think I am the only one who is dealing with this, and not much I can find as a solution.

I have been trying many steps that I find scattered in this forum. and throughout the internet, and non works. 

Do I have to be part of a club to get the insider solutions ? Not all of us into Telegram, Matrix and so forth.. it would be better if in egalitarian fashion that knowledge is spread and preserved for ALL to utilize and contribute to.

We do learn from the learned, when they give us attention, and so forth, things begin to flow...

Would it be possible to create a Sticky or a sub-forum to deal with this major issue with Pinephone Pro adaptation as a "phone" and perhaps, for a better run as being a "daily driver" , when the AUDIO CALLS are existing?

Thanx

Hi!

I want to establish usb network between desktop and PBP.

On pinephone I can connect usb-c side of the usb a-c cable to the pinephone, usb-a side to a desktop and it works just fine, all necessary modules are loaded automatically (pmos 6.0.2 kernel), usb0 interface appears on both sides and i can establish networking.

But the same doesn't work with pinebook pro: when using the same cable and desktop to connect to nothing happens: no modules loaded, no usb0 interfaces appear, kernel is similar (pmos 6.0.2). Loading all necessary modules manually (usbnet, cdc-ether, etc…) doesn't help. lsusb doesn't change after plugging in the usb-c cable.

To rule out software problem I also tried Manjaro, still can't establish usb network and lsusb output is unchanged as well.

I found the following comment:
https://forum.pine64.org/showthread.php?...9#pid86259

Quote:the Pinebook Pro does not support USB C alternate mode, HDMI video.

I recently bought a car which has one of those radios you plug your phone into (Apple Carplay and Android Auto). I've found it useful to connect my iPhone to it for media control and navigation, mainly as an excuse to not have to mount my phone somewhere accessible and deal with lock screens etc.

I don't know a lot about how this technology works, but just as a baseline, will it ever be possible to use a Pinephone for this? Is it possible now? What level (if any) of hardware integration is required?

I would like to buy a Pinecil v2. I want to use the 6.2 ohm version but I am not using conical tips, I only use hoof/chisel tips.
Are you planning to release a 6.2 ohm version of something like the TS-BC2?

I am currently holding off buying the Pincecil v2 because I want to order an asortment of 6.2 ohm tips with it.

Hi,

I would like to send an integer number from a flutter app on adnroid to pinetime, but don't know how to use the ble service.

I've already managed to develop a flutter app on my android device that sends a notification to pinetime.
I've also managed to flash a new application to pinetime.

Now, I want to send an integer message (not a notification) to my new app.

What will be the best way to do so? and do you have any example code to share?

THanks,
RAz

Hello,

I have PinePhone (3GB variant) with Pine''s convergence docking bar. It worked fine for a while, though there were some occasional bugs (e.g. usb-c power don't work or docking bar no longer recognized and pinephone reboot is needed for bar to work again). But later eth port, hdmi and usb-c ceased to work at all: the phone is no longer charged via bar's usb-c, eth port is not visible (leds are down, no eth device created) and HDMI output no longer works. Both USB-A ports still work fine (I can connect mouse/keyborad/USB flash to the pinephone) and USB-C seems to provide power to the USB-A devices (e.g. usb mouse diode is turned on when I connect it to the docking bar with power plugged in into usb-c port while disconnected from the pinephone).

First I though this is some software bug, but reverting to older kernel where it worked doesn't help. Then I updated ANX7688 firmware from Megi's tree, but the bug is still here. It is possible that there is physical damage to the docking station, because I carried it often in the backpack, but there is no visible damage on the bar or its cable.

Have anyone encountered similar problem? Maybe this is a known issue I'm struggling about.
Any thoughts?

How convergence docking bar casing can be opened safely? Looks like it has some internal hatches, but I'm not sure. I want to examine internals for some obvious problem like broken circuit soldering.

1: Open Network Manager and select the hotspot connection from the menu 

2: Under the Wi-Fi menu tab in the MTU field enter the number 1428

3: Save and reconnect

Hello members of the pine64 users community,

my order of a "Pinephone Beta Convergence" I made recently is still in progress. I'm also thinking about to buy some additional parts.
I have watched many different reviews with a lot of different opinions and complaints.
But none of them really answered the question if the performance problems could be solved with a GPU Driver which would support Hardware Acceleration of the GPU or if the limits of the Allwinner A64 with the MALI-400MP2 are already reached out with the available drivers.
Indirect people express this way that the A64 with its 40nm structure could have been the the wrong choice for a mobild device because it had a to low performance in general or would get to hot / consumt to much power per performance for that use case.
Additionally I read in this forum something about issues with a decreasing display functionality / destruction related to higher system temperatures and do Both seems to be a problem of manufacturing quality or the use of 2nd class batches.
I would be very happy to get some of your opinions about these things.

Thank your very much.

Just update my pp a few minutes ago and now it's stucked at arch penguim loading forever

Hi.
I'm using a Quartz64 -A SBC and QUARTZ64_SDK_android11.tar.gz.

SDK link:
http://files.pine64.org/SDK/Quartz64/QUA...d11.tar.gz

These are the steps that I took:
$ source build/envsetup.sh
$ lunch
$ 26 (rk3566_rgo-userdebug)
$ ./build.sh -UCKAu

However, unlike the image in the link below, it does not boot.

Test pre-build image:
- Quartz64_model-A_20210604_stock_android11_emmcboot.img
- Quartz64_model-A_dd_20210604_stock_android11_emmcboot-16GB.img.gz

Is the content of the link the only way?
Or do you need another additional method?
Android SDK for RK3566 - PINE64