| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,705
» Latest member: Sheo
» Forum threads: 16,261
» Forum posts: 117,195
Full Statistics
|
| Latest Threads |
Quill OS for the PineNote
Forum: PineNote Software
Last Post: JhonSmith
9 hours ago
» Replies: 1
» Views: 70
|
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: biketool
10 hours ago
» Replies: 3
» Views: 176
|
auto-owning the SD card i...
Forum: PineTab Software
Last Post: biketool
Yesterday, 04:16 AM
» Replies: 1
» Views: 385
|
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: Stunnned
11-24-2025, 01:27 PM
» Replies: 2
» Views: 196
|
Volumio (PINE A64-LTS / S...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: kapqa
11-23-2025, 02:02 AM
» Replies: 8
» Views: 15,548
|
Reinstallation Arch Linux...
Forum: General Discussion on PineTab
Last Post: rth
11-22-2025, 08:25 PM
» Replies: 1
» Views: 236
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
11-20-2025, 09:04 AM
» Replies: 5
» Views: 642
|
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 222
|
How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 496
|
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,201
|
|
|
| USB-C Dock and HDMI, revison 1.2 (Modded) |
|
Posted by: Ersatz - 07-16-2020, 01:06 PM - Forum: Mobian on PinePhone
- Replies (5)
|
 |
*Edit* Please see https://wiki.mobian-project.org/doku.php?id=mods
Update ANX chip firmware https://xnux.eu/devices/feature/anx7688.html
Note: this should be run as root user and not through sudo
*This line is important. Note 2: Clone the repository rather than directly downloading the .bin file. For some reason, directly downloading it does not give you the correct image and errors on the “echo” command.
*Original Post*
I have been testing out a USB-C dock for a couple days now. USB device work (mouse, flash drives), SD-card reader, and power deliver all work. However, I can not get a monitor to detect the HDMI signal, dmesg shows when HDMI is plugged in an detected. Has anyone successfully used display out on Mobian? I am hitting a wall troubleshooting this, and have ruled out the dock itself.
Unplugged HDMI: anx7688 0-0028: dp state changed to 0x00
Plugged in HDMI: anx7688 0-0028: dp state changed to 0x03
Note to anyone wondering my phone is hardware modded (switches removed)
|
|
|
|
| Pine Store should accept Zip+4 |
|
Posted by: Mark53 - 07-16-2020, 12:03 PM - Forum: General
- Replies (1)
|
|
I ordered a Pinephone yesterday and used my zip code with the extra 4 digits (the USPS calls this ZIP+4). Zip+4 codes have 5 digits for the regular zip code, followed by a hyphen, then a 4 digit extension. When I entered my zip code in the pattern 12345-6789, the hyphen was removed in the backend and my confirmation email showed a zip code with a pattern of 123456789.
Fortunately sales@pine64.org took care of this very quickly and fixed the zip code, but it should be a simple fix to allow hyphens in this field so we can use a more specific address. Is there any reason not to allow this character?
|
|
|
|
| I/O errors from SD card slot? (Manjaro, kernel 5.7) |
|
Posted by: zackw - 07-16-2020, 07:31 AM - Forum: General Discussion on Pinebook Pro
- Replies (5)
|
|
I'm getting I/O errors from some, but not all, attempts to use the SD card slot in my PBP. `badblocks -w /dev/mmcblk1` completes without error, and `fdisk` is also happy, but when I attempt to run `mkfs.ext4` or `cryptsetup luksFormat` on the (single, whole-disk) partition, the operation fails and I see errors like this in dmesg:
Code: blk_update_request: I/O error, dev mmcblk1, sector 2120 op 0x1:(WRITE) flags 0x8800 phys_seg 255 prio class 0
blk_update_request: I/O error, dev mmcblk1, sector 2128 op 0x1:(WRITE) flags 0x8800 phys_seg 254 prio class 0
blk_update_request: I/O error, dev mmcblk1, sector 2117 op 0x1:(WRITE) flags 0x8800 phys_seg 255 prio class 0
blk_update_request: I/O error, dev mmcblk1, sector 2127 op 0x1:(WRITE) flags 0x8800 phys_seg 255 prio class 0
(Only one error occurred per attempt to format the partition.)
I put the card into a different computer and was able to create a filesystem successfully, so I don't think the card itself is at fault. However, when I put the formatted card back into the PBP and tried to mount the filesystem or to run e2fsck on it, I got more of the same errors, just with different sector numbers and flags:
Code: blk_update_request: I/O error, dev mmcblk1, sector 8301 op 0x1:(WRITE) flags 0x8800 phys_seg 251 prio class 0
blk_update_request: I/O error, dev mmcblk1, sector 40960 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
blk_update_request: I/O error, dev mmcblk1, sector 59023360 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
This is a 2019-batch PBP, so it shipped with MrFixit's modified Debian, and the card slot was working fine with that kernel; I only started seeing problems after I reflashed the internal storage with Manjaro. So right now I'm inclined to suspect a kernel bug. Anyone else seeing similar problems? Workarounds? Debugging advice?
|
|
|
|
| Status update 2020-07-16 |
|
Posted by: a-wai - 07-16-2020, 05:29 AM - Forum: Mobian on PinePhone
- Replies (12)
|
|
Hi all,
Things continue to move on quite quickly, so I guess it's time for a new status/progress update (I'll try to post those on a monthly basis).
Over the past month we added or improved a whole bunch of exciting features: - Thermal management is now working, decreasing the CPU frequency under intensive load so your phone doesn't get too hot (and the "Usage" app now properly reports temperature)
- Latest crust build greatly improves battery life (now ~20hrs idle with the modem on)
- Updated phoc & phosh which bring in lots of improvements, including automatic scaling for apps which would otherwise overflow the display (enabled by default for Calendar, Maps & Geary)
- Camera and flashlight are supported out of the box
- Driver for the ANX7688 USB-C controller is now included in the kernel build (requires a HW fix to be able to actually use USB-C peripherals)
- More mobile-friendly software have been packaged for Mobian (not all are installed by default, but they're just an "apt install" away):
- Cawbird (Twitter client)
- Flashlight
- GNOME Metronome
- Pinhole (Camera app)
- Tootle (Mastodon client)
All of these features are available in today's image, which has been promoted to a new "reference" release (I dare not say "stable" at this stage, even though I happily use my PinePhone as a daily driver).
The community has done a great job at improving the project's wiki, and things keep getting better. 
Many thanks to everyone involved!
You can also follow Mobian on Twitter now, where we'll share news of software development as well as other news related to the larger PinePhone community.
Finally, we're always looking for contributors and developers as the team is still quite small and we're not short of items on our TODO-list! Please reach out to me if you'd be willing to help out
As always, the latest image can be downloaded from our server.
Enjoy!
|
|
|
|
| RAM: 2GB vs 3GB |
|
Posted by: jtagcat - 07-16-2020, 04:03 AM - Forum: General Discussion on PinePhone
- Replies (6)
|
|
On other phones, paying for 4GB vs 6GB or 6GB vs 8GB is not really worth it.
I'm not interested in desktop computing (giving the dock away to someone's storage), but I would be running quite significant tracking.
As the Pinephone probably isn't optimized as much as it could be. Would it be worth it on getting an extra GB of RAM for 60$? I don't have the biggest wallet, so it's somewhat of a significant amount, but simultaneously I don't want to have a phone I'm not going to use because it's constantly out of RAM and having to use swap.
|
|
|
|
| Privacy switches not persistent |
|
Posted by: yawnoc - 07-16-2020, 12:01 AM - Forum: General Discussion on Pinebook Pro
- No Replies
|
|
I have noticed that if I enable the privacy switches for microphone (Pine + F10) or camera (Pine + F12) and leave them for 2 weeks or so, they lose their state and revert to being disabled. Does this mean I have buggy keyboard firmware flash memory?
Also I have noticed the following:
- Activation/deactivation happens instantly rather than 3 seconds after pressing the required key combinations
- When the camera (Pine + F12) privacy switch is enabled, there is a high-pitch whining sound (not from the speakers; maybe a stray capacitance thing?)
Anyone else experience these?
This is on a Pinebook Pro ordered in Nov 2019 and delivered Jan 2020.
(Haven't yet tested the Wi-Fi privacy switch --- too scared I'll run into trouble trying to reactivate internet.)
|
|
|
|
| Pinebook Pro sometimes Does not boot up correctly |
|
Posted by: decisivedove - 07-15-2020, 08:50 PM - Forum: Linux on Pinebook Pro
- Replies (2)
|
|
Hi,
I recently installed Arch Linux on my Pinebook Pro. /dev/mmcblk2p1 is my boot partition and p2 is my root partition. The problem is that sometimes Linux cannot detect /dev/mmcblk2p2. Sometimes, it works fine. Here is the output:
Quote::: running early hook [udev]
Starting version 245.6-8-arch
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/mmcblk2p2 ...
ERROR: device '/dev/mmcblk2p2' not found. Skipping fsck.
:: mounting '/dev/mmcblk2p2' on real root
mount: /new_root: special device /dev/mmcblk2p2 does not exist.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#
It was working fine a while ago, it only happens sometimes. Using UUID on the extlinux config also results in the same.
I had recently soft bricked my PBP and had to switch off the emmc but it is fixed now, if that is relevant.
Apparently running:
Quote:echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/bind
As suggested by randomuser987987 in the thread Pinebook Pro dead after updating u-boot works in getting the partition to show in /dev. The question is will the changes persist forever?
(07-15-2020, 08:50 PM)decisivedove Wrote: Hi,
I recently installed Arch Linux on my Pinebook Pro. /dev/mmcblk2p1 is my boot partition and p2 is my root partition. The problem is that sometimes Linux cannot detect /dev/mmcblk2p2. Sometimes, it works fine. Here is the output:
Quote::: running early hook [udev]
Starting version 245.6-8-arch
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/mmcblk2p2 ...
ERROR: device '/dev/mmcblk2p2' not found. Skipping fsck.
:: mounting '/dev/mmcblk2p2' on real root
mount: /new_root: special device /dev/mmcblk2p2 does not exist.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#
It was working fine a while ago, it only happens sometimes. Using UUID on the extlinux config also results in the same.
I had recently soft bricked my PBP and had to switch off the emmc but it is fixed now, if that is relevant.
Apparently running:
Quote:echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/bind
As suggested by randomuser987987 in the thread Pinebook Pro dead after updating u-boot works in getting the partition to show in /dev. The question is will the changes persist forever? It turns out that the changes do not persist. It only works when it wants to. Is there any way to make these changes persist permanently?
|
|
|
|
|
