I just tried to make a purchase and the site didn't have the usual $12 shipping to EU option for Poland, but if I switch to Germany it is there. If I switch to Czech Republic there is no shipping option at all.
All 3 countries are in EU and are bordering each other. Cost to ship from China to Poland/Germany is pretty much the same
So what happened there? Is this a mistake that will be corrected?
I went out of my way recommending pine64 sbc boards to my various developer friends and now it seems there is viable shipping option from pine64 store to Poland anymore for cheap items. It is really disappointing.
What kind of connection does the monitor take so I could look up screens by name of connection it would plug in to, or does anyone have a suggested alternative that might work?
Why use Plebian? Simply put, it doesn't try to be overly quirky. We use Debian's kernel package. If I get hit by a blimp tomorrow and die, you'll still get kernel updates through Debian's regular channels.
Most importantly, these aren't bespoke artisanally hand-crafted images, but the output of an automated pipeline. You, yes you, can fork the repository and make your own with your adjustments to the debos recipes.
Consider these images to be in a "Beta" phase for now, they're generally ready for you to use but at some point you might need to do manual intervention if we end up deciding we want a third party repository after all. If and when it comes to that, I'll let you know.
I'm new to pine64 I recently purchased a pine phone pro and have mobian on internal flash storage and Kali Nethunter Pro on an SD card. Everything seems to be working fine minus a few tools but I know there are likely a few wrinkles that need to be ironed out software wise. The one thing I'm kinda bummed about is I can't seem to get monitor mode and packet injection working on my internal wireless card I've read that they're working on the original pine phone but I can't seem to find any info on the subject for the pro model. Also I can't get any external wireless adapters to work either it shows that they are being read in the kernel via dmesg and lsusb but they don't show up as devices when I use iwconfig so I'm kinda confused as to why they aren't working. Am I doing something wrong or am I missing something? My external wireless adapter is Ralink rt2870/rt3070. If anyone more experienced with these devices could point me in the right direction it would be much appreciated thank you! Happy new year!
At the moment, the wiki gives brief coverage of the official cases, loose fitting styles, and one line about the OtterBox uniVERSE Case for the Samsung Galaxy XCover Pro. I'd like to assemble more info about compatible cases utilizing a snug fit.
I've started by finding other phones with similar dimensions to the PinePhone, which has been relatively easy to do. However, even with a close height/width/depth match, there are still the issues of different size, shape and placement of various phone features, along with any nuances of particular cases. This is where reports from the trials of other people are especially useful. Unfortunately, I'm not finding many.
If you have tried to repurpose a snug-fit case to a Pinephone, please say so here! In particular, please identify the phone model(s) your case was marketed for, whether you made any modifications, and what "works" and what doesn't. Thanks!
Last night I fired up my PineTab after not having used it in some time. After having solved apt-get update "The following signatures were invalid..." Mobian had a ton (a little over a 1000) updates to install, after that was done I entered the reboot command.
Since then the only sign of life is the occasional clicking of the camera's when holding the power button (from 2-3 up to 10s), other than that nothing happens. No error, nothing.
Besides reflashing Mobian, are there any ways of figuring out why Mobian won't boot?
i have concluded at this point that this bug is in two parts, powersaving part and frequency change part. practically all gnu/linux distributions and plasma and phosh are affected.
powersaving part seems to be more straightforward and more rare. this can be avoided by following.
however, in my situtation, frequency bug happens only in 1.2a hardware version and not in 1.2b. so i don't rule out possible hardware problem in 1.2a version or my specfic individual phone.
if you tech savvy enough and you have pinephone regular. could you test frequency part of this bug and say your hardware version (1.2 1.2a 1.2b etc). you only set powersaving part, then run glxgears in user interfaces without auto suspend, sreenlocks and screen saving. then run following script in background.
Code:
while true
do echo 432000000 > /sys/class/devfreq/1c40000.gpu/min_freq
echo 432000000 > /sys/class/devfreq/1c40000.gpu/max_freq
echo 312000000 > /sys/class/devfreq/1c40000.gpu/max_freq
done
generic copy paste:
Code:
# udev rule. this prevent flipping frames bug
# example file location /lib/udev/rules.d/98-preventflippingbug.rules
# powersaving part
KERNEL=="1c40000.gpu", SUBSYSTEM=="platform", DRIVER=="lima", ATTR{power/autosuspend_delay_ms}="-1"
KERNEL=="1c40000.gpu", SUBSYSTEM=="platform", DRIVER=="lima", ATTR{power/control}="on"
# frequency part, may not be needed
KERNEL=="1c40000.gpu", SUBSYSTEM=="devfreq", ATTR{min_freq}="432000000"
KERNEL=="1c40000.gpu", SUBSYSTEM=="devfreq", ATTR{max_freq}="432000000"
