| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,205
» Latest member: Karen68
» Forum threads: 16,384
» Forum posts: 117,596
Full Statistics
|
| Latest Threads |
Hardware Feature Suggesti...
Forum: Quartz64 Hardware and Accessories
Last Post: Independent Researcher
Yesterday, 07:19 PM
» Replies: 0
» Views: 34
|
Single-board computers an...
Forum: General
Last Post: Spaker
08-29-2026, 08:12 PM
» Replies: 0
» Views: 70
|
Pinephone visibly losing ...
Forum: General Discussion on PinePhone
Last Post: baptx
08-29-2026, 11:18 AM
» Replies: 9
» Views: 8,383
|
Fixing the Quartz64 USB3 ...
Forum: Quartz64 Tutorials
Last Post: mig
08-28-2026, 01:32 AM
» Replies: 1
» Views: 12,775
|
Pinecil as a Pocket-Sized...
Forum: General
Last Post: Arsen
08-27-2026, 09:15 AM
» Replies: 0
» Views: 130
|
SlateOS feedback needed!
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-24-2026, 08:00 AM
» Replies: 0
» Views: 197
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: Nambo
08-23-2026, 12:17 AM
» Replies: 18
» Views: 13,634
|
Hello, I am a new member ...
Forum: General
Last Post: WhiteRabbit0
08-20-2026, 12:17 PM
» Replies: 0
» Views: 397
|
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: ahegarosib97
08-20-2026, 08:45 AM
» Replies: 2
» Views: 2,043
|
RAM-free SBCs with SODIMM...
Forum: General
Last Post: anchor
08-20-2026, 08:21 AM
» Replies: 0
» Views: 176
|
|
|
| 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?
|
|
|
|
| New to PinePhone - one basic question |
|
Posted by: Mike X - 07-15-2020, 06:31 PM - Forum: General Discussion on PinePhone
- Replies (2)
|
|
(My apologies in advance if I've posted this in the wrong forum. I think this is the right one, but...)
I just found out about the PinePhone and I'd love to try one and see what it's like.
My main question is "Can the PinePhone run android apps?" Is there some way to do that?
(I realize this probably isn't a straight yes or no answer to this and that it's probably been asked a thousand times. I searched the forum a bit but couldn't find a clear discussion on this, so I'm sorry if this is an oft-repeated question.)
If the answer is just plain 'no', that'll tell me something and I can go from there.
If the answer is 'yes' or 'sort of yes' or 'maybe' or 'it depends', then great- anything you can tell me along those lines would be welcome, or maybe point me to some discussion threads here that I can read through.
Thank you in advance.
|
|
|
|
| My Daily Manual QA |
|
Posted by: plainenough - 07-15-2020, 05:28 PM - Forum: UBPorts on PinePhone
- Replies (40)
|
|
For a few weeks now I have been running through some simple QA on my pinephone. Things to note:
I am running on the development channel.
I only test after a successful OTA update.
I have limited my scope to what I consider requirements for a daily driver. (SMS, Calls, general sound quality, wifi, clock accuracy, etc. etc.)
Here are my results for today:
Wifi: seems fairly stable after reboot.
Boot time: No noticeable difference compared to day before. (~1 minute)
SMS in: Works as expected
SMS out: Works as expected
Calls out: Call failed
Calls in: Connects. no audio either direction. (iphone and android)
Camera front: Black screen
Camera back: Black screen
Loud speaker: distorted audio from web browser
Noticeable issues:
Lockscreen wakes up without notification or interaction periodically (3-5 times per hour)
Lockscreen clock lags behind until unlock then corrects itself (over the course of the day by over an hour)
LED stays engaged after hitting the lock button multiple times. Requires another click or a full unlock to disable LED.
After hours of idle phone unable to send texts or receive calls until reboot. (warm reboot)
Results of manual QA: Fail.
Phone not ready to trial daily driver.
If you would like to see more simple manual tests, or if you test something different feel free to post your reports.
|
|
|
|
|
