I am written a python script to control my fan with pwm. The script is inspirated by shell script from the armbian forum.
You can set the pwm period and duty_cycle.

The script monitoring cpu and all disks an activate the fan when required.

https://github.com/mh-superbox/pwm-fan-control

period
The total period of the PWM signal (read/write). Value is in nanoseconds and is the sum of the active and inactive time of the PWM.

duty_cycle
The active time of the PWM signal (read/write). Value is in nanoseconds and must be less than the period.

More info about pwm: https://www.kernel.org/doc/Documentation/pwm.txt

No mms (messages with attachments) transmittals that I can get going.  My system is stock, as received, but updated plasma-manjaro. Have Consumer Cellarular sim card that is same card as used in my android. where MMS works fine. This card worked on Pinephone for SMS and no MMS. Do not think sim card is cause.

Spacebar app allows setting up message with attachment.  It allows sending of message, shows message and attachment as sent except for small icon that looks like an error, but it is not received.  Neither the text part of the message nor the text is received.

Chatty app still does nothing.  Does not open up for a message and doesn't open up Settings.
  
Any one with any better luck?  Any other app to look at?  


tom kosvic

Didn't think this would work, but it does! Just wanted to share

Attached Files

Thumbnail(s)
   

Hello,

I'm in Germany and ordered the PP Keyboard (together with some other stuff) on january 1st.
It still hasn't arrived. Looking at the tracking information it has arrived in Germany, but since january 19th nothing else happened.
Are people from Germany here who already got their keyboards?
Is there an issue?
What can I do, if nothing happens any more?

Thanks in advance

OK - fairly trivial but has got a smile on my face.

My only internet connection is tethering from my PinePhone(s). I just noticed my desktop package manager update was running close to 60Mbps download on my PinePhone Pro - historically it was more like 40Mbps on the original PinePhone. I guess this is another benefit of the faster CPU   

I did try a Speedtest which, while impressive, is single threaded and not quite as exciting as arch/pacman which I have running 4 threads!

Watch is on Infinitime 1.8.0. PinePhone is Mobian.

Previously (with same version of InfiniTime) I was able to pair with passcode, and talk to the watch using itd. It would lose the connection after a (short) while, and fail to reconnect (even though the phone was in range and not suspended).

However now, I can't get it to pair at all. This is what happens:

0. Start bluetoothctl
1. Make sure InfiniTime is not in bluetoothctl list of devices and that info [mac] does not show it paired.
2. Exit bluetoothctl
3. Reboot watch
4. Toggle bluetooth off and then on again on the PinePhone
5. Start bluetoothctl
6. wake watch up with side button
7. in bluetoothctl: scan on
8. in bluetoothctl: pair [mac]

I get:

[bluetooth]# pair [MAC]
Attempting to pair with [MAC]
[CHG] Device [MAC] Connected: yes
[CHG] Device [MAC] Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled


Sometimes I will get the passcode prompt, and the passcode displayed on the watch. But even when typing in the passcode, I get the above. Often the above will happen before I finish typing the passcode.

Any ideas for how to get the watch paired? (And ideally, to keep the connection stable.. I see scripts for reconnecting after suspend, but that's not my issue. I'm using the keyboard w/battery, so the phone is never in suspend.)

EDIT: If I do connect first instead of pair, it connects. Then I can pair successfully, with the passcode. After that, I mark trust on. However, the connection drops a minute later. It seems to be oscillating between Connected: yes and Connected: no.

EDIT 2: Logs have this:
Feb 04 15:28:28 mobian itd[1647]: 3:28PM FTL Error connecting to InfiniTime error=le-connection-abort-by-local

-john

Please help me to figure out what is going on with the system time of my Pinephone. I noticed that both system and hardware clocks run too slow for some unknown reason. For example, I could see that NTPD adjusts the clock every several hours.

I wrote a script collecting 3 kind of times: the network time (from time.nist.gov), the system time and the rtc (hwclock) time. Then I did:

1) Stop ntpd
2) Run this script  for about a day on my desktop PC and on a Pinephone (Pinephone was in a suspend most of the time)
3) Collect the data and plot the results this renderer

The results are:

Vertical axis is the time difference, in seconds
Horizontal axis is the running time of my script, in minutes
The blue and orange lines show the difference between remote (time.nist.gov) and local clocks: system and hwclock.


As we may see, the clock skew tend to increase quickly on a pinephone.

The question is - why, and how to fix.

Note, that it is unlikely a known "year 2115" problem, because I can see both errata and the correction patch applied to the kernel.
Note2, I did stop NTPD, so I can't explain right now why the pinephone time difference became zero at 450th minute of the measurement. Maybe there is other agent which does the correction, besides ntpd.

I use Megi's kernel 5.13.7, Crust fw is 0.4, the os is MobileNixos.

I believe it is a hardware/firmware problem. Let me know if there is a better place to post it.

Is the gnome-podcasts coming to the Debian repos soon? I feel really bad using flatpaks, or is there an alternative to using another app? I tried gpodder but it is not mobile friendly and I had to download each episode than play it iwth another app, not very practical...

To adapt the pinephone keyboard, I will need to use the equivalent of xev for wayland ie wev, or the version available on AUR is not suitable for arm64. Is it difficult to adapt the pkgbuild to compile compatible with aarch64?

Anyone else have a KB that seems to be connected properly (input received, charge passed to "main" battery, "kb151" detected in power submenu of gnome-setting) but that insists on reporting it is always at 0% charge, even when there is no external power connected and the main battery continues to charge up (presumably off the not-0% KB battery)?

on Arch/Phosh