If you have an SFOS existing installation on emmc you can upgrade to SF4.0 by running:
devel-su
ssu re 4.0.1.45
ssu ur
zypper ref
zypper dup
this runs fine, but there have been no developments in the last month, so no calls, sporadic sms and no camera. Also, SF4 is still new and buggy so it might be wiser to wait for the official release.
If you upgrade on an SD card it can take several hours.
Otherwise, if you create a new SF 3.4 image using the flash-it script it seems quite problematic, freezes very frequently requiring reboot.
I got my KDE Plasma edition pine phone in early February. Took me a day or two to open things up...
When I did I noticed I could not "x" out of applications, in order to exit from an application I had to either restart or shut down the phone.
(Just for the record: I alerted Pine to this issue at the support e-mail with photos of the original OS not working properly on February 5th, got an e-mail reply ( automated?) that if I needed to open a ticket...which I did last night...I was trying to avoid making a deal about something that I thought should be able to be fixed with an OS flash)
So I figured it was a bad OS flash, and downloaded the jump drive from the link kindly provided by Pine at the wiki page...
I flashed the phone with the latest release of KDE plasma Mobile...some things seemed "OK", The "x" at the bottom of the phone appeared, and my sim card worked ( yay) and the only problem was sending SMS that did not work. There were some issues...some lags some screen flicker as well at times, then a few days later while plugged in to charge the phone crashed....it would not start back up again...Wifi toggle switch was in the "off" position, mobile data was on...
Well that was enough of KDE Plasma for me , so I decided to flash the Feb 7th build of Mobian to the phone. Guess what, SAME ISSUE as originally came with the factory KDE Plasma! I could only open applications, not close them...very, very weird. No updates helped with this issue
any suggestions? I cant be sure if it's a hardware ( eMMC ?) or software issue...
I am encountering a issue with gnome-contacts.
Whenever I open a contact, there is no button showing next to the phone numbers, for calls or sms.
Next to the email addresses, I can see the button for sending an email (which works OK and open geary), but no buttons are showing next the the phone numbers.
I checked in /usr/share/applications/gnome-mimeapps.list, which did not have any
a few issues popped up after last nights updates.
1. sxmo_setpinebacklight segfults unless it is run with sudo, therefore adjustong brightness with the config menu or in xinitrc fails and just displays the default brightness of 750.
2. suspend and lock (screen off) both turn off the screen for a second or so and then turn it back on. it appears that suspend is completely broken
this is all ive noticed so far but its been a busy work week
Was running nextCloudPi on Armbian 21.02.1 stable, headless. Board: v3 w/ 4G
No issue for over a couple of months, 5A power, htop would indicate temps in the 36-45 range.
Today (2021-02-09) Installed the Armbian configuration utility and conducted an update on the board firmware.
Currently unable to complete a boot of the OS.
It appears to be having issues sometime after starting the Network manager.
A failure is flagged when attempting to start the network interfaces.
After either the starting of the Network Manager or the Setup of the zram based device zram2 messages similar to the following are generated:
BUG: spinlock suspected on CPU#0, armbian-hardwar/667
BUG: spinlock suspected on CPU#2, ln/670
lock: 0xffffffc0fec1c0, .magic: dead4ead, .owner: <none/-1, . .owner_cpu: -1
BUG: spinlock suspected on CPU#3, ln/679
lock: 0xffffffc0fec1c0, .magic: dead4ead, .owner: <none/-1, . .owner_cpu: -1
lock: 0xffffffc0fec1c0, .magic: dead4ead, .owner: <none/-1, . .owner_cpu: -1
BUG: spinlock suspected on CPU#1, migration/1/12
lock: 0xffffffc0fec1c0, .magic: dead4ead, .owner: <none/-1, . .owner_cpu: -1
I've got a pretty rough python3 script that I'm working on right now. It takes SMS and MMS messages from the PinePhone (Tested on PMos and Mobian) and bridges them to a Matrix server.
I've uninstalled chatty on my testing device as it also interacts directly with the modem.I did this because i think it'll cause problems if its running at the same time. I'm still pretty new to programming and definitely not a developer. Just a Linux admin who hates using his cellphone when I'm already at a keyboard. So far no one else has written anything so I have to.
If you're interested in helping me please let me know! I'd love to get someone who has experience to make this better.
Have you ever had a broken display manager and were annoyed by the fact that the cable to the external keyboard interferes with standing up your Pinephone upright or even lay perpendicular to the keyboard so you can read without holding your head in an uncomfortable position?
Not anymore! Just do this as root:
Code:
echo 1 > /sys/class/graphics/fbcon/rotate_all
I don't know if it can rotate a framebuffer. For me it doesn't so after you fix the broken it should start in portrait orientation.
Making it permanent:
WARNING! Here someone had issues after setting a smaller than native resolution. The gods know what rotating the display does.
Neither have I learned how uboot does things, so I cannot even test it on the Pinephone:
Code:
fbcon=rotate:3 # usb socket on the left
fbcon=rotate:1 # usb socket on the right
As in the pjsf thread (below), my Pinetab has a misfortune, he has a WiFi and Bluetooth radio. Is there or will there be a possibility of purchasing spare parts? It can be the radio module itself or the entire motherboard. I can replace it, but without the parts, I can't do anything.
after running well for 25 days more or less, my rockpro64 is unusable. All USB ports and ethernet port are not working. I tried with many images, Manjaro, armbian... to top it all sometimes the startup finish with a kernel panic message.
I'm pretty sure that this is a hardware failure. Has anyone a similar experience? I'm very disgusted, the rockpro64 only ran for 25 days more or less. I have had others SBC, like raspberry pi, in the same place for years without problems.
