I'm trying to install a package that requires the pamac command. At this time, I'm only interested in pamac. I have some familiarity with the existing "pacman" command.

I have tried several tutorials online to install pamac with no success. I can clone the git repository just fine, but get an error after the makepkg command.

Installed git:
sudo pacman -Syyu base-devel git

Created the directory:
mkdir pamac-aur

Listed the directories to confirm:
ls
(All of my directories appeared including the newly created pamac-aur directory)

Changed the directory:
cd pamac-aur

Listed the contents inside "pamac-aur"
ls
(pamac-aur is listed)

Changed into this directory:
cd pamac-aur

Listed the contents of this directory:
ls
(pamac.install and PKGBUILD are listed)

At the command prompt inside this directory, I typed "makepkg" and the process began. It listed some missing dependencies and the process ended with an error.

==> ERROR: Could not resolve all dependencies.

Did I miss something? Can I complete this process with the dependencies acquired automatically? Please correct or add to what I should do to complete the process. Thanks for the help.

(12-29-2021, 02:23 PM)tk1107 Wrote: I'm trying to install a package that requires the pamac command. At this time, I'm only interested in pamac. I have some familiarity with the existing "pacman" command.

I have tried several tutorials online to install pamac with no success. I can clone the git repository just fine, but get an error after the makepkg command.

Installed git:
sudo pacman -Syyu base-devel git

Created the directory:
mkdir pamac-aur

Listed the directories to confirm:
ls
(All of my directories appeared including the newly created pamac-aur directory)

Changed the directory:
cd pamac-aur

Listed the contents inside "pamac-aur"
ls
(pamac-aur is listed)

Changed into this directory:
cd pamac-aur

Listed the contents of this directory:
ls
(pamac.install and PKGBUILD are listed)

At the command prompt inside this directory, I typed "makepkg" and the process began. It listed some missing dependencies and the process ended with an error.

==> ERROR: Could not resolve all dependencies.

Did I miss something? Can I complete this process with the dependencies acquired automatically? Please correct or add to what I should do to complete the process. Thanks for the help.

Hello Forum!

So, my first post here.
Out of curiosity I just ordered a PineTime, just to give it a try.
(I had a smartwatch from Withings before, but all this "you have to use our cloud"-$4!7 was a showstopper.)

Anyway, expectations were low (would be unfair to compare a 30$ item with something >100-200).
Yet, I was curious to see what can be done with it, perhaps even see how to get some Qt-app running with it.

However, I seem to permanently run into problems to (re)connect the PineTime (FW v1.6.0) with any device - after it was succesfully paired before.


Tried the following:
- iPhone with inifinitime. Connected and worked - until disconnected i.e. BT turned off on the phone, or just left the house without phone
- Linux on a Thinkpad with amazfish (was a bit bumpy to get build, but got it working). Pinetime paired, and worked as expected, until - perhaps you can guess - until BT was turned off, or I just left the house without the TP.

And, it does always work again - once - when I do a soft reset (push the PineTime button for 8sec until Pine logo appears).

But, obviously then always all collected data such as heart rate and steps is lost.
This is pretty frustrating as it seems to be systematic:
Pair it. All looks fine, then go shopping and come back, and no way to get the data synced. Do a soft reset, loose all data. Looks fine... until the next time.
--

1. I am aware that the watch can only be connected to one device at a time. (The blue "Bluetooth-B" is not lit.)
   
2. Infinitime on the phone just doesn't seem to find it at all anymore - until I reset the PineTime. (tried already enable/disable auto-reconnect -> no diff.)
   
3. Amazfish does show the PineTime in the list (mac address is right), but doesn't want to reconnect. (Running the UI from the shell spits out a "connected", just before it says "disconnected" again. Unpairing and trying to repair also no success. - Until soft reset of the PineTime is done.)
   

the modem shows up in the gui (Arch Linux arm and Plasma Mobile with gdm intstead of lightdm) and with "mmcli -m any" but it shows always "failed" and "sim-missing"
 
please help

Hi,

I'm looking for an NVMe adapter to buy from someone based in Europe. Ordering it from pine store makes a little (to none) sense because the cost of the shipping is almost double the price of the adapter itself.

Anyone has a spare NVMe adapter to sell?

Thanks in advance.

Since a while my phone does not remain in standby: For some reason (without any messages coming in etc.) the screen switches itself on and either the lockscreen (with time, date, connections) is visible or the screen is black, but on (i.e. not switched off but displaying a black surface, as you can tell by the glow).

This of course drains huge amounts of energy and reduces the standby time from two days to a few hours.

Other than the power settings (Screen blank after two minutes, automatic suspend on) I have no idea where to look in order to fix it.

Ideas anyone?

I have a Pine64 UBports edition. I have a few questions I am willing to research on my own, but I am not sure exactly what I have in my hand. Is there a build number that I can look up, or some other way to determine what is in my phone, and what hardware and software is compatible?

As an example, my telecom carrier is going to shut off their 3G equipment very soon. I need to know if I have VoLTE enabled, or if I need to get a new phone.

Thank you for the help.
J.W.

NOTE: This may be a bit ranty, because frankly I'm frustrated. Please excuse that, no offense is intended.

Background/context:

I've been running Fedora with XFCE (big icons etc) on my PinePhone since around the beginning of the pandemic. Maybe April or May 2020? Not sure. I've been using it as a daily driver, patiently, fixing issues as they arrive, for that span of time.
I've had two PinePhones in that time, a Mobian CE and a Braveheart.

I've been building custom kernels based on megi's sources for the majority of that time. They're not really modified much, they just have things like btrfs as builtins, and my occasional patches for stability or compile fixes. My PinePhone Mobian currently runs kernel 5.15.11, the latest at time of writing.

I'm a programmer myself with a background in several systems languages and several scripting languages and cross-platform development, though mostly userland.

The last straw today was when I tried to play music in a lyft and the system hung because I dared try to play audio out of the 3.5mm jack.

Here we go.

We're now about to enter 2022, and I still have a miserable experience daily. It's a rare day indeed that my PinePhone doesn't seize up entirely at least once. It's not the RAM speed issue, that's fixed for me, I'm at 400 something Mhz. Hard lockups are usually caused by any one of: rtl8723cs wifi drivers, Goodix touchscreen related Xorg hangs/segfaults, sound card drivers, or just using more than a few hundred MB of data over wifi. I finally got Bluetooth working, but the audio performance is so bad that it pops and cracks constantly, making it unusable. Sometimes Pipewire (Fedora's pulseaudio replacement, and Pulseaudio before that) just randomly crashes with no explanation. Sometimes a phantom finger shows up and decides to hold down something on the screen so I can't use the screen at all.

What's become clear to me is that it's the drivers that are the issue, not the hardware, and for the mostpart, not the userland.

It seems to me that developers have patched just enough of the most common issues that it works fine for custom touchscreen GUIs that do exactly one very specific thing (which I can't stand, I want a real desktop with a virtual keyboard and window manager), but the vast majority of not-so-uncommon edge cases are ignored completely, meaning that anyone running a normal, non-phone-oriented OS and GUI will constantly hit them. If there are fixes/hacks in mainstream PinePhone distros, they are undocumented and/or out of date, because I sure as hell can't find them anywhere.

I don't blame the kernel developers who volunteered to work on the PinePhone, in fact people like (and especially in specific) megi are the only reason that things can work at all.

I blame the concept of expecting the community alone to entirely write the drivers for this hardware. I've been very, very patient, but I strongly believe that Pine needs to hire someone with a background in Linux driver development at least part-time to clean this mess up. (I'm tired of fixing other people's C, so don't look at me, at least right now)

I imagine most of the contributors are like me, programmers with a day job and not a lot of free time, so they try to get the bare minimum functioning, but they have no time to refine it or fix edge cases, or work on big refactors. The result? A bug riddled abortion that can barely boot to a desktop without emitting a mushroom cloud due to some bizarre edge case or race condition/deadlock in a kernel driver.

It's now in a situation where I"m scared to copy 200MB to my PinePhone over SSH because there's a 60% chance it will hard-lockup in the middle of the transfer. (that wifi issue has been happening since I got the first PinePhone, by the way)
Don't get me started on the call audio routing model. That should never have been an ALSA thing. That should have been a bitstream on some device node that was rendered by some userland app to the user's sound system.

Just thinking about how the thread icon should be a broken lightbulb.

I'm sorry guys, I'm tired, and I'm angry, and I'm deeply disappointed.

Please share thoughts, solutions, and similar experiences.

Hey all,

I'm trying to update my pinecil to the latest firmware, and when I downloaded it from either the pinecil repository or the ironOS repository, they both are hex files, which don't work with the pinecil software. How do I convert them to bin files or how do I flash them without converting? I think mine is the newer batch of pinecils because I ordered mine in November and mine just arrived today.

Hey folks, I just got my new pine time and I am impressed with the build quality for the price. I use a Pinephone as my daily driver and have since cut android from my life!

The pinephone connects proper and sends notifications but when the pinephone goes to sleep (suspend) the pinetime obviously looses connectivity which is to be expected, however when I wake my phone or get a message the pinetime does not reconnect with out me trying Siglo a bunch of times and messing around with the blue tooth toggle switch before it will re connect.

Is this a known issue or is this just something on my end?

Thanks in advanced.

I was really excited to finally see the Pinecil in stock, I had my wife order me one for christmas to replace my XIHAU one. 
I powered it up and it worked for all of 5 minutes before the top half of the screen failed, I only see the lower half of the screen display now.

Is this a common thing?