As the title says, the keyboard is only drawing tiny amounts of power, regardless if it has a phone in it, if it's on, and of the constant current sysfs setting.

I did plug the phone in while docked before I read the warning, did I fry the charging chip?

Got stuck on building infinitime on my own computer. The following procedure worked well for version 1.9 but not 1.10
I used a win10 64bit computer. I installed Microsoft visual studio code and docker on my computer.
Here is what I have tried:
1. use github desktop app to make a clone of the infinitime code.
2. under github app choose the master branch tagged 1.10
3. then use the visual studio code to open the infinitime folder.
4. wait for visual studio code to run docker container, then opened an terminal
5. with root account
apt-get install npm
npm install lv_font_conv
6. runs the create_build_open_ocd.sh
 /workspaces/InfiniTime$ cmake -G 'Unix Makefiles' -DCMAKE_BUILD_TYPE=Release -DUSE_OPENOCD=1 -DARM_NONE_EABI_TOOLCHAIN_PATH=/opt/gcc-arm-none-eabi-9-2020-q2-update -DNRF5_SDK_PATH=/opt/nRF5_SDK_15.3.0_59ac345 -S . -Bbuild
7. cd build
8 make -j pinetime-app
Then it gives error:
[ 42%] Built target lvgl
[ 63%] Built target nimble
(Stripping trailing CRs from patch; use --binary to disable.)
patching file jetbrains_mono_bold_20.c
patching file jetbrains_mono_bold_20.c
patch: **** malformed patch at line 3:

Traceback (most recent call last):
  File "/workspaces/InfiniTime/src/displayapp/fonts/generate.py", line 75, in <module>
    main()
  File "/workspaces/InfiniTime/src/displayapp/fonts/generate.py", line 70, in main
    subprocess.check_call(['/usr/bin/env', 'patch', name+'.c', patch])
  File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/env', 'patch', 'jetbrains_mono_bold_20.c', 'jetbrains_mono_bold_20.c_M.patch']' returned non-zero exit status 2.
make[3]: *** [src/displayapp/fonts/CMakeFiles/infinitime_fonts_jetbrains_mono_bold_20.dir/build.make:73: src/displayapp/fonts/jetbrains_mono_bold_20.c] Error 1
make[3]: *** Deleting file 'src/displayapp/fonts/jetbrains_mono_bold_20.c'
make[2]: *** [CMakeFiles/Makefile2:590: src/displayapp/fonts/CMakeFiles/infinitime_fonts_jetbrains_mono_bold_20.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:286: src/CMakeFiles/pinetime-app.dir/rule] Error 2
make: *** [Makefile:189: pinetime-app] Error 2

Greetings folks,
After reading plenty of issues related to sound and phone I thought I might suggest a possible solution for Pine64 staff to consider. Since Android devices work excellent as phones but not so great as data devices whereas PinePhone works excellent with data but not so great as a phone ... why not marry the two together? Is it possible to have a PinePhone flashed from the factory with a dedicated Chat/Phone system separate from any o.s.? Further to this a system that can boot from the dedicated phone app with no other o.s. on the eMMC card? In doing so people can flash whatever o.s. they wish BUT the phone/chat system are already there preinstalled by factory and unaffected by any o.s. except where an address book is created in any Linux o.s. This way the phone will always work regardless and the sound system also dedicated to phone/chat. On the PPP we can flash tow boot to the SPI chip which I have done so I am suggesting something similar to that. So instead of a rolling update that destroys (potentially sometimes) the usability of the device a dedicated system unaffected by any update except where a flash update is released to the phone if required.
Just a suggestion to consider.

I have created a guide on how to get Minecraft (Java Edition) working on the Pinebook Pro:
https://gist.github.com/riscygeek/714b78...500d30da88

After a recent update (Manjaro plasma), the display has stopped working on early boot, for example during initramfs.

My boot.txt has not changed.

It comes back on during the normal bootup.

Does anyone know how to get it working again? It's causing me major headaches, typing into nothing and hoping things will work.

Edit: I'm not sure what exactly fixed this but I'm getting the display on the current version

Hello everyone, I have a small problem I wanted to change os on my Pinephone but Emmc na is displayed more when I use BalenaEtcher or Gparted and the phone does not want to start anymore someone would have a solution please

Hello everybody,

I am trying to make a fresh install on my Pinephone, but it results in a device that is not booting anymore. I am flashing mobian-installer-pinephone-phosh-20220621.img to eMMC and the installation works as usual. After the installation I run apt update and apt upgrade and get this message in the status bar:

Low Disk Space on "Filesystem root"
The volume "Filesystem root" has only
166.3 MB disk space remaining.

The update process shows a littlebit later: No more disk space available.

Ahoj,

when will the Pinecil be available again?

On the Pinecil's page in the pine64 online shop it shows "Out of stock", while on this availability page it shows that there should be some available.

I want to place a bigger order at pine64.com, and one of the pieces I want to order is the Pinecil.

I want to order all in one batch to save on shipping costs. (Or, can I order it now and get it shipped to me when it is available again, without extra shipping fee?)

Regards!

---

Update 2022-10-18: It is available, version 2, here.

Hi,
I noticed that Megi (i.e. Ondřej Jirman at https://xnux.eu/log/#069) has recently been working on calibrating the IMX258 sensor.
But is it Pine's plan to have people calibrate at home like he is doing, instead of calibrating at the factory?
There's a reason why companies like Foxconn calibrate every sensor at the factory: It's because every single sensor is slightly different.
Without special equipment, there is no reliable way to calibrate a color Bayer sensor at home.
Now, if Pine had used a grayscale (B&W) sensor then maybe calibration would be possible, but they didn't.
So what then is the actual plan once Megi is done?
Will his code be used at the factory?
If yes, will each person who buys a PinephonePro receive a file containing calibration info for the phone?
Megi points out that unlike other phones, the Pinephones don't include an EEPROM to store calibration parameters, so it will have to be in a file somewhere.
And how will people who have already bought the phone get theirs calibrated?

Hi,

I am from HK and would like to pre-order the Pinebook Pro. However, I cannot find "Hong Kong" in the Country list. Is it possible to ship to HK?

Thanks