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

Hi:

I have a new Rock64. So far I am 0/2 in terms of getting OSes to boot. First I tried DietPi (DietPi_ROCK64-ARMv8-Bullseye.7z) . Followed directions, unzipped OS, flashed with Etcher.  It never booted just had a flashing red light. Next I tried one of the recommended Ambian (Armbian_22.08.8_Rock64_jammy_current_5.15.74_xfce_desktop). This was one actually booted into the command line but once I made a user and tried to get the desktop going it crapped out on me. I just ended up with a black screen with a flashing white cursor in upper left hand corner. Both these issues seem to be in the forums/online but with no apparent solutions. The Rock64 DietPi thread goes back years ago.  So if anyone has recently successfully installed and run one of the recommended OSes in the getting started guide for the Rock64 please let me know. Any help would be greatly appreciated.

Matt

The timing may be coincidental, but after upgrading bookworm today I find that every MMS I receive takes several (2-20) minutes to process.  A common factor is that I'm seeing "GSocketClient: Address enumeration completed (out of addresses)" in the log from mmsd-tng.  Each time this happens, there is a 1 minute timeout and it happens multiple times for every MMS.

Is anyone else seeing this after a very recent upgrade?

mmsd-tng did get upgraded from 1.11-1 to 1.12-1 but I've tried reverting to the old version with no effect.  My carrier is Ting (T-Mobile) but don't know if that's relevant.

With PinePhone Pro Manjaro Plasma Mobile OS, Beta 13, I cannot hear nor be heard on the other line (outgoing call).

Settings for audio:  Settings > Audio >

- Playback Devices > Port:  Internal Speaker -- Profile:  Make a phone call
- Recording Devices > Port: Internal Microphone -- Profile: Make a phone call.

I have tried these steps:

$ sudo pacman -Sy pulseaudio pulseaudio-alsa pulseaudio-bluetooth
$ sudo pacman -Rs pipewire-alsa pipewire-pulse

and a reboot; no avail.

Tried the PinePhone Pro with Mobian, and the same results I do get.

Anything else I should be looking into?