Hello. I would like to order a Pinecil V2 with a delivery to an address within China. Wrote an email to "Sales" 2 days ago, but no any response.
Anyone knows how I can manage with that?
For most of us on most PP distros install is as easy as that, desoite being built with a PP mobile GUI scaling look in non-mobile apps for the launcher. https://github.com/vagnum08/cpupower-gui
It makes tweaking CPU use pretty easy, back in the Nokia N900 days this was done more for performance ie:overclocking the CPU and GPU, but on Rockchip and Allwinner I feel like we are more interested in battery life.
With some experimentation I think we can come up with some great battery life saving while still having a phone awake enough to catch phone calls, you can put the GUI in favorites when mobile apps only is enabled to have quick access. I am enabling balanced mode and will give it a week or so of trial on my Rockchip CPU PPp daily driver phone.
What is nice is with a long press from the desktop you can choose presets without launching the app.
Now part of this was probably my fault, but I'm having some odd issues with the modem.
I got my Pinephone used from a friend, and when I tried to use my SIM card, it could recognize the SIM card was inserted and the towers it could connect to, but it would never be able to connect. So I thought "Okay it's a driver issue" so I went and used the script available at https://github.com/the-modem-distro/pinephone_modem_sdk but I was tired and didn't think to check the current firmware on the modem and that also didn't work. So then I thought to try to load all the old firmwares until it was fully updated, but now the modem still exists and TRIES to function (it'll show me the settings, the lack of bars, and that there's no SIM inserted or that there is inserted) but I can't see it with
Code:
lsusb
or
Code:
adb
and I'm wondering if it's irrecoverable or not?
I did try connecting the two plates on the back of the board to each other, but perhaps that didn't short them out. When I did that, the modem just disappeared and still didn't exist with any command.
There was a deleted thread today where I posted some crypto-currency services I have seen requested, let's contribute wish list items, I will try to edit every request into this top post.
The old(unfortunately deleted) Mobian app status/catalog pages on showed usable Bitcoin-Electrum and Monero official clients from flatpak( https://flathub.org/setup/Debian ). It would be useful for you all to post your use cases and what is working for you on any and all platforms mobile and desktop so the community can also suggest solutions. If you are looking to interact with online services for research or where your crypto is held in an account for you by some company(custodial wallet) it is usually easy enough to make a webapp for that sort of thing.
Between here, Reddit, and other forums I recall people wanting more non-custodial wallets and zero-trust p2p exchange services ie: litecoin-electrum, electrum-doge, WoWnero wowlet client, btc-xmr UnstoppableSwap, Havano-Reto XMR market, BTC Bisq market, Etherium, among other FOSS apps preferably with tweaked UIs for mobile though the Mobile Settings - Compositor can probably fix the scale to be useful.
It is useful to know is how we imagine we and other future users will want to actually use crypto on their PP; are we talking about buying coffee and pizza directly, through the gift card bridge, or bridging through bitpay, using a crypto wallet as a savings account, managing a mining farm, buying a used laptop on moneromarket.io, trading and investing on Kracken or robinhood, or... other? (I am not sure how I feel about the mentioned commercial services vs zero-trust FOSS solutions they are just possible usage examples)
I am running Mobian but all PP distros including libhybris such as Ubuntu-Touch are included.
When I flip the second kill switch on the pinephone I cannot get the WiFi or the bluetooth to turn off. Is this normal behaviour? Am I missing something?
it seems that by default only the internal I2C-controller of the DesignWare HDMI controller is enabled. However, it is known that this is sufficient to retrieve the EDID, but the internal I2C controller of the HDMI module is not suitable for full DDC support, see the discussion here:
it shows that the I2C-5 pins are even connected to the HDMI plug (search for HDMITX). So things are correctly setup in hardware, what is missing are the proper settings in the device tree. This can be cured by the attached device-tree overlay. The overlay
enables the controller for i2c-5 with the m1 pin configuration (see schematics for the board)
removes the respective pins from the pin-control entry of the HDMI controller to resolve conflicts
adds "ddc-i2c-bus = <&i2c5>;" to the hdmi controller section
Afterwards DDC just works, on Linux "ddcutil detect" will succeed and, e.g., "ddcui" can be used to control the settings with a GUI.
In an attempt to troubleshoot failing to get generic alpine linux to run on PA64-2G-LTS, I've tried to reduce the problem to the smallest steps that are legible to me.
When booting the kernel, I get "Bad ARM64 Image Magic" I can't figure out what this means, and why it is happening. Sources I have searched seem to be board specific, and found nothing on this board. I've arrived at a point where I cannot find a way to reason further about it, so thus I am reaching out.
I am currently loading the kernel and dtb manually at the uboot prompt:
- linux 5.14 from mainline (git:7d2a07b769330c34b4deabeed939325c77a7ec2f)
- u-boot v2024.10 from https://source.denx.de/u-boot/u-boot (git:f919c3a889f0ec7d63a48b5d0ed064386b0980bd)
- dtb from the u-boot build
- bl31.bin from PLAT=sun50i_a64 https://git.trustedfirmware.org/TF-A/tru...ware-a.git lts-v2.10.6 (git:f2aebf361050d69176d60016170291efa9e08a68)
- scp.bin from https://github.com/crust-firmware/crust 0.6 (git:ffe9f1ac9c675e6e67db9084bd19fbdeffd8e162)
- u-boot-sunxi-with-spl.bin written to offset 8k
- tried sd and emmc vfat single partition (whole disk) with
* boot/vmlinux
* boot/u-boot.dtb
Hello, I am rather new to sdc's. I have used Pi's for kipper but that is about it.
Got a second hand Rock64 yesterday. As far as I have been able to tell I need to jump pins 20 and 21 to bypass SPI-flash to boot from SD. Was not able to boot into debian. I ended up flashing the SD card with Armbian to try and install u-boot. I was able to boot onto the sd card with armbian. So I know the rock64 isn't bricked.
The dilema I currently see myself in is that I only have 1 sd card and I do not see how I would install an OS without having a second sd card and a usb sd card reader. Am I wrong? I am hoping to not have to go out and buy an extra sd card and reader I don't really want to buy an emmc module either.
I was planning to run the rock64 off the sd card. Would it be possible to achieve what I want with the serial console?
Hi there,
Been a quiet PBP user since july 2021, really love my pinebook and enjoy it (using manjaro).
Lately I have an issue with the power button.
Symptoms:
It seemed that it won't boot properly, despite no recent OS/FW updates and topped-up battery.
It would boot into a certain state where the LCD is lit up and a flashing '_' is flashing at top left corner, as expected.
Then, the flashing is halted, then continues until shutdown. The PBP reboots, ad infinitum.
From time to time it did load GUI to show the mouse pointer before resetting, rarely loading the login screen.
Another thing is that shutting down resulted in reboot. Long press on power button did shut it down for good though.
Lately otherwise it ususally make it into login without turning off.
Making a long story short, in the rare cases I managed to log in I got constant power-off dialogs popping at me.
That's a typical journal log I get on the machine (reverse order):
Code:
Oct 12 18:08:27 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:07:44 PinebookPro root[4904]: PowerButton pressed
Oct 12 18:07:44 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:07:28 PinebookPro root[4902]: PowerButton pressed
Oct 12 18:07:28 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:07:17 PinebookPro root[4897]: PowerButton pressed
Oct 12 18:07:17 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:06:44 PinebookPro root[4892]: PowerButton pressed
Oct 12 18:06:44 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:05:58 PinebookPro root[4879]: PowerButton pressed
Oct 12 18:05:58 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:05:26 PinebookPro root[4876]: PowerButton pressed
Oct 12 18:05:26 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:04:36 PinebookPro root[4873]: PowerButton pressed
Oct 12 18:04:36 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:03:28 PinebookPro root[4862]: PowerButton pressed
Oct 12 18:03:28 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:03:10 PinebookPro root[4859]: PowerButton pressed
Oct 12 18:03:10 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:02:56 PinebookPro root[4857]: PowerButton pressed
Oct 12 18:02:56 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:02:31 PinebookPro root[4855]: PowerButton pressed
Oct 12 18:02:31 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:02:07 PinebookPro root[4851]: PowerButton pressed
Oct 12 18:02:06 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:01:35 PinebookPro root[4844]: PowerButton pressed
Oct 12 18:01:35 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:00:57 PinebookPro root[4831]: PowerButton pressed
Oct 12 18:00:57 PinebookPro systemd-logind[520]: Power key pressed short.
Well you get the idea. That's really annoying.
I could probably remap the power button? But I do fear that the underlying condition will kill the power button altogether one day, and I wont be able to properly power the device on.
I took a look at the schematics. I guess that something is pulling the CPU power line, but not the PMIC one? Or is the PMIC less sensitive to that signal?
If it's the first issue that it's not a keyboard issue, and I have no clue what issue it is.
I might be able to sense the proper test points later, but I'd rather ask here first if anyone had such an issue or have any insight into this issue (I couldn't find such thing in the forum or elsewhere).
