Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,473
» Latest member: Samliams
» Forum threads: 16,196
» Forum posts: 116,880

Full Statistics

Latest Threads
Pinephone Pro wont boot t...
Forum: General Discussion of PinePhone Pro
Last Post: KC9UDX
5 hours ago
» Replies: 5
» Views: 198
PinePhone Pro discontinue...
Forum: General Discussion of PinePhone Pro
Last Post: Kevin Kofler
7 hours ago
» Replies: 8
» Views: 412
fixing the ppkb mainboard...
Forum: PinePhone Pro Accessories
Last Post: Jite
9 hours ago
» Replies: 2
» Views: 81
Are there plannes to crea...
Forum: PinePhone Pro Hardware
Last Post: biketool
Yesterday, 04:12 AM
» Replies: 5
» Views: 943
prototyping to help someo...
Forum: General
Last Post: Samliams
Yesterday, 02:22 AM
» Replies: 1
» Views: 121
Pinephone pro stuck while...
Forum: PinePhone Pro Hardware
Last Post: Supervisor
08-16-2025, 06:40 PM
» Replies: 2
» Views: 120
Compatible U.S. carriers ...
Forum: General Discussion on PinePhone
Last Post: Zebulon Walton
08-15-2025, 07:34 PM
» Replies: 2
» Views: 161
Long dialpad keypress to ...
Forum: Mobian on PinePhone
Last Post: Zebulon Walton
08-15-2025, 06:48 PM
» Replies: 3
» Views: 113
Password reset via u-boot...
Forum: PineNote Software
Last Post: lunnabae
08-13-2025, 01:17 AM
» Replies: 6
» Views: 1,773
incorporate a multimeter ...
Forum: General
Last Post: lalisa12
08-13-2025, 01:14 AM
» Replies: 2
» Views: 535

 
  keyboard charging fault, chip "most likely damaged", how to be sure?
Posted by: korakin - 10-01-2022, 07:39 AM - Forum: PinePhone Accessories - Replies (1)

The battery component of my pinephone keyboard is malfunctioning with symptoms described exactly in megi's FAQ, so I'm just quoting them here (emphasis mine):



Quote:Phone is not charging from the keyboard battery at all and keyboard power button does nothing

If
Code:
/sys/class/power_supply/ip5xxx-battery/uevent
does not become available, even when connecting the USB power supply to the keyboard, and is empty, that means that the charger chip is not responding, even when powered up. That means the chip is most likely damaged.
(source: https://xnux.eu/pinephone-keyboard/faq.html)




"most likely damaged", it says. Is there a known alternative possibility that I could test for, and possible ways to fix the unit?




I have had the keyboard for only a month and have barely used it. I was very aware that I should never charge it through the phone's USB-C socket and I am pretty sure I didn't. I did leave it connected to a charger via the keyboard's socket for a week once and maybe that's when the fault happened, although that still seems surprising to me.


  Article: Understanding PinePhone's Display (MIPI DSI)
Posted by: lupyuen - 10-01-2022, 05:58 AM - Forum: PinePhone Software - Replies (2)

How does PinePhone control its LCD Display? Let’s uncover all the secrets about PinePhone’s mysterious LCD Display and its MIPI Display Serial Interface…

1. What’s a MIPI Display Serial Interface (DSI)

2. What’s inside PinePhone’s LCD Display

3. How it’s similar to PineTime’s ST7789 Display Controller

4. One lane for Commands, but 4 lanes for Data!

5. Implications of a RAM-less Display Controller

6. What are PinePhone’s Display Engine (DE) and Timing Controller (TCON)

Check out the article here...

Understanding PinePhone's Display (MIPI DSI)


  Nemomobile in September 2022
Posted by: jmlich - 10-01-2022, 04:08 AM - Forum: Nemo Mobile on PinePhone - No Replies

Hi, here are news about Nemomobile in September:

- fixed UI orientation in desktop mode
- glacier dropped in postmarketOS
- music app rework
- moving to Qt 5.15.6
- webkit code style

https://twitter.com/xmlich02/status/1576113394712981505
https://blog.mlich.cz/2022/10/nemomobile...mber-2022/


  How are people finding the type-A USB 3.0 port?
Posted by: chris88233 - 09-30-2022, 07:02 PM - Forum: General Discussion on Pinebook Pro - Replies (1)

It appears that nearly all USB 3 supporting devices I try won't work on the type-A USB 3.0 port of the Pinebook Pro. I believe this is a power draw issue from what I've read, although it doesn't entirely match up with what I'm seeing.

  • TP-Link 1G Ethernet adapter - Left port: "Cannot enable. Maybe the USB cable is bad?". Right port: Works as a USB 2.0 device.
  • WD My Passport 2.5" spinning disk - Left port: Half-spins up, clicks, spins down, repeat. Right port: Works as a USB 2.0 device.
  • Inateck disk enclosure with SATA SSD disk - Left port: Works as a USB 2.0 device. Right port: Works as a USB 2.0 device.
  • Some generic SD card reader - Left port: Works as USB 3.0 device! Right port: Didn't bother trying.

The way I'm confirming the speed is with `lsusb -t -v`.

What's a little unexpected is that devices that appear to draw too much power for USB 3.0 will work  as USB 2.0. What's also unexpected is that something like a SATA SSD or ethernet adapter is drawing too much power for the PBP.


Does this match up with what other people are seeing? I have very few type-C devices, but is there the chance a type-C external drive is going to work better on the PBP? I know a suggestion is to use a powered USB hub, and I could get one, but that's a definite drag on portability.


This is on a Pinebook Pro which was shipped to me around August this year.

Thanks!


  Bootloader: SD card boot quirks
Posted by: crazyquark - 09-30-2022, 10:20 AM - Forum: Linux on Pinebook Pro - Replies (1)

Hello,

I am currently running Tow-Boot but I noticed similar behavior with U-Boot:
- If I reboot, and try to select boot from SD - it fails, sometimes it freezes or fails to detect the linux image
- If I power cycle - most of the times I can boot from SD.

With U-boot it was similar, after a reboot, only boot from emmc was possible. But if I powered off/on, it would boot from SD.

Is this intended behavior?


  Any chance of fixing the audio issues on the new batch PBP(it can't be just me...)
Posted by: crazyquark - 09-30-2022, 10:15 AM - Forum: Linux on Pinebook Pro - No Replies

Hello all,

Two issues with audio on PBP that I see no way out of:
- the audio jack: when plugging in headphones with a TRRS plug - the mic is not detected, only the speaker function(someone on discord told me it might be related to alsa ucm2 - maybe because there is only a "High fidelity audio" profile available or something like that?)
- The internal mic picks up a TON of noise, messing around with the controls in alsa can reduce the noise, make it almost functional. If the audio jack mic would work then this is almost a non-issue, I do not want to use the integrated mic anyway.

I tried a bunch of distros - armbian, manjaro, arch(still working on it), kali - none of them have a properly working audio system.

Am I missing something obvious? Could my audio jack just be poorly wired or something?

P.S.
Also the popping and the hissing of the audio.... that has been reported by other users as well. I dealt with it by disabling suspend and switching to headphones(even if disconnected).


  Webcam not working in Manjaro with Cheese, but works in Armbian
Posted by: petaramesh - 09-30-2022, 07:18 AM - Forum: Linux on Pinebook Pro - Replies (1)

Hello,

The Pinebook pro webcam doesn't work either in Cheese or Kamoso with the preinstalled Manjaro, and it's definitely not a privacy switch issue as replies all over this forum suggest.

It actually works with any of these :

mpv /dev/video4
vlc v4l2:///dev/video4
guvcview-qt -d /dev/video4

It also works with webcamoid - that needs to be built from AUR although.

And it also works in a Jitsi echo test in Vivaldi : https://janus.conf.meetecho.com/echotest.html

However, the Webcam works out-of-the-box with Cheese using either Armbian or Twister OS (Both based on Ubuntu LTS), so I wonder what library or helper might be missing in Manjaro to get it working.

I tried to search for a while, but to no avail so far.

Any clue would be much appreciated.


  You received an MMS, but it expired on: 1970-01-01 07:59
Posted by: SpaggettiCoder - 09-29-2022, 12:13 AM - Forum: Mobian on PinePhone - Replies (8)

Hi Mobian forum,

I'm trying to get my Pinephone into a state in which it suitable as a daily driver. I've updated to the latest version of Mobian and most things work most of the time (I do need to boot while the phone is plugged into the USB port to get the phone part working). The main blocker at the moment is that I can't receive MMS. I will send one to the phone but no joy, then after I reboot I get the message: You received an MMS, but it expired on: 1970-01-01 07:59

Any ideas?
This is with Telstra (Australia) and the UBPorts edition of the Pinephone.

SC


  WIll not power up
Posted by: Jester89 - 09-28-2022, 10:59 PM - Forum: Shipment Related Discussion - Replies (2)

Hello, this is my first time here. I received my Pine 64 a week ago and it powered up just fine. After getting familiar with the os that came with it I decided I wanted to try Mobian. After creating the jump drive and after installing the new os the battery had died. It was not charging in the phone so I bought an external battery charger and was able to fully charge the battery. I put the battery into the phone and it does not power up. Huh I am at a loss as to what to do next. I have been wanting this phone for a long time and now its a brick. Can any one advise me on how to get this phone working again?


  Is some u-boot required on the SPI for installing debian with the official installer?
Posted by: callegar - 09-27-2022, 03:55 PM - Forum: Linux on RockPro64 - Replies (1)

Hi,

https://wiki.pine64.org/wiki/ROCKPro64_Software_Release reports the possibility of installing debian on the ROCKPro64 using the Official Debian Installer via the installer image to be found at https://deb.debian.org/debian/dists/bull...rd-images/

I have verified that the installer image boots and does its job of downloading and installing stuff.  However, installing (at least installing on the EMMC) delivers a system incapable of booting.

I now wonder if this is because the official debian installer does not install a bootloader and expects a bootloader to be already present on the SPI.

If this is the case, the page at https://wiki.pine64.org/wiki/ROCKPro64_Software_Release shouild probably say so.

I have tried to install tow-boot on the SPI expecting it to be the best option for a general bootloader.  Unfortunately, It does not appear to work. After coming up, it hangs at

Code:
Booting using the fdt blob at 0x1f00000

It is unclear to me if this is a bug in tow-boot (also looking at https://github.com/Tow-Boot/Tow-Boot/issues/186).

If it is, what would be an appropriate uboot for running debian?