| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,952
» Latest member: Aruz508
» Forum threads: 16,335
» Forum posts: 117,437
Full Statistics
|
| Latest Threads |
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
Today, 08:37 AM
» Replies: 106
» Views: 214,980
|
Ibotta Referral Program [...
Forum: Pinebook Pro Hardware and Accessories
Last Post: rex9090k
Today, 05:24 AM
» Replies: 0
» Views: 42
|
Ibotta Deal for New Users...
Forum: Android on Pinebook Pro
Last Post: rex9090k
Today, 05:23 AM
» Replies: 0
» Views: 33
|
Ibotta Promo Code Today [...
Forum: Getting Started
Last Post: rex9090k
Today, 05:23 AM
» Replies: 0
» Views: 35
|
Ibotta Invite Offer [ZVFT...
Forum: PineNote Hardware
Last Post: rex9090k
Today, 05:22 AM
» Replies: 0
» Views: 33
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
Yesterday, 05:16 PM
» Replies: 0
» Views: 46
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 114
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
03-28-2026, 01:01 PM
» Replies: 17
» Views: 8,401
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 1,981
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 871
|
|
|
| Unable to login due to the password change |
|
Posted by: pine_usr - 07-23-2020, 04:31 PM - Forum: UBPorts on PinePhone
- Replies (9)
|
 |
Hello everyone,
I just have a quick question. Just got my new Pine64 UBports edition phone and after booting the phone first time I was prompted to enter a screen lock pin, which I did and chose 4 digits pin. After I boot into the UBPorts system, played around, opened terminal and went ahead and changed password for the main user by passwd command. After a while the screen was locked and in order to unlock it, you get a prompt to enter password. The initial 4 digit pin is not accepted, since I changed password. But, there is no way to enter new password (letters and digits) as the prompt only has digits option. There is no way to enter a new password which contains letters. I wasn't aware that the new password for the user will also apply as a screen unlock PIN. Now, I am stuck with no way to enter the system and need to reset it. What is the fastest way to factory reset UBports without full reinstall? Pressing Up Volume + Power Button get me "Installing update" screen which never disappear. In regular Androind phone you login to a bootloader and just factory reset system. Could anyone suggest how to factory reset UT system instead of full reinstall? Also, why screen lock pin is the same as a user password?
Thank you.
|
|
|
|
| Cannot unlock pinephone |
|
Posted by: hb. - 07-23-2020, 03:05 PM - Forum: UBPorts on PinePhone
- Replies (4)
|
 |
This is embarrassing to relate, but when my new pinephone arrived today I entered a numeric passcode when prompted in setup. A short time later I changed my password from the CLI to something with letters in it.
Now, at the lockscreen I am prompted with a numeric keypad, but - as my password is not simply numeric - I cannot unlock.
I have not been able to access the phone via ssh (I am not sure of the IP address), and UBports installer does not recognize the phone when I plug it into my computers USB port. I can access the phone via telnet ($ telnet 172.16.42.1) but from that interface I cannot do much ("sudo: not found", "su: not found", "passwd: not found", etc.) and so cannot change my login password.
My next plan is to try and boot from an SD card. But if anyone has advice on how to access the phone to change the password (I know what the login password is I am just unable to type it at the lockscreen!), or to wipe and restore to factory presets without logging in, that seems much easier.
Many thanks!
|
|
|
|
| USB OTG issue |
|
Posted by: Ididntknowwhatnametochoose - 07-23-2020, 01:27 PM - Forum: Mobian on PinePhone
- Replies (2)
|
 |
So it's been my 3rd day with my Pinephone CE and I've found out a lot of stuff.
I just did the VCONN Switch removal surgery in the jankiest way imaginable since I don't have a reflow workstation at home. So far I got the phone to recognize that something was plugged in and it even charges for a brief moment from my PD power supply. After a bit of prodding around I saw that it spat out an error message:
Code: anx7688 0-0028: boot firmware load failed (you may need to flash FW to anx7688 first)
Heck it even shows in the lines before that that it got the IRQ and even enabled power for a brief moment.
So my question now is how could I fix this? Is there an easy script to flash the firmware to this chip? I hope I didn't rip through a trace on the Board.
The device I'm trying to use is a combined USB-hub with USB-PD input and HDMI out. So kinda like the dongle from the convergence pack but different.
|
|
|
|
| My Daily Manual QA |
|
Posted by: plainenough - 07-23-2020, 12:45 PM - Forum: Mobian on PinePhone
- Replies (54)
|
 |
I will be preforming some basic QA against the nightly build.
build image: mobian-pinephone-20200723.img.gz
I have limited my scope to what I consider requirements for a daily driver. (SMS, 4G Calls, general sound quality, wifi, clock accuracy, etc. etc.)
Wifi: seems fairly stable after reboot. --------------------------------------------------------------------------------------------------------------------------------------------------- PASS
Boot time: Changed reboot from simple restart to battery out cold boot. (~ 1m 15s) ------------------------------------------------------------------------------------------ PASS
SMS in: Works as expected after cold boot --------------------------------------------------------------------------------------------------------------------------------------------- PASS
SMS out: Works as expected after cold boot ------------------------------------------------------------------------------------------------------------------------------------------- PASS
Calls out: Call connects, full audio, speaker works. ----------------------------------------------------------------------------------------------------------------------------------- PASS
Calls in: Connects. Call connects, full audio (iphone and android) ------------------------------------------------------------------------------------------------------------------ PASS
Camera front: Unable to figure out how to switch to front camera ----------------------------------------------------------------------------------------------------------------- FAIL
Camera back: Super Laggy ---------------------------------------------------------------------------------------------------------------------------------------------------------------- FAIL
Loud speaker: opening video in web browser crashed the UI ---------------------------------------------------------------------------------------------------------------------- FAIL
Build stability: Unstable
Notes: Laggy interface on boot or application start. Firefox app crashed the desktop (not the phone). Camera, super laggy.
Results: Not a suitable candidate for daily driver.
|
|
|
|
| How to improve Bluetooth audio quality |
|
Posted by: CyberSeb - 07-23-2020, 12:18 PM - Forum: Mobian on PinePhone
- Replies (6)
|
 |
Hi all,
after almost losing my faith in humanity in a time when the mobile world is dominated by two [...], there still seems to be a glimmer of hope. MANY thanks to all who were involved in the development of the PinePhone, and especially to those who were engaged in the creation of the various Linux distributions. For me a dream has come true.
Mobian is so great! What I'm not satisfied with is Bluetooth A2DP audio performance. In the default configuration, the sound stutters and after some time the Bluetooth stack reduces the data rate -- hoping to deliver stutter-free audio. I don't expect true HiFi on the go, but I'm no fan of stuttering and compressy-rattling mids either.
After doing some research, I've found various ways to fix this:
1. Increase the priority of PulseAudio
2. Increase the buffer size of the encoder
3. Install other codec modues and increase minimum allowed bitpool
In detail:
1. Increase the priority of PulseAudio
Basically follow the instructions from here: https://wiki.ubuntuusers.de/PulseAudio/#...t-erhoehen
In /etc/pulse/daemon.conf, add:
Code: high-priority = yes
rlimit-nice = 31
nice-level = -11
realtime-scheduling = ye
rlimit-rtprio = 9
realtime-priority = 9
In /etc/security/limits.conf, add:
Code: mobian - nice -11
mobian - rtprio 99
Reboot the PinePhone. The PulseAudio daemon should now run with a niceness of -11 (use the 'top' command to verify this).
2. Increase the buffer size of the encoder
Here's a script that increases the audio buffer. Connect the Bluetooth headphones, then run the script.
Code: # based on https://askubuntu.com/a/1207648 and https://askubuntu.com/a/171165
BLUEZCARD=`pactl list cards short | egrep -o bluez.*[[:space:]]`
pactl set-port-latency-offset $BLUEZCARD headset-output 100000
sudo service bluetooth restart
pactl list | grep -Pzo '.*bluez_card(.*\n)*'
Steps 1 and 2 together should already dramatically reduce the stuttering.
3. Install other codec modues and increase minimum allowed bitpool
To get rid of the low data rates, follow the instructions here: https://github.com/EHfive/pulseaudio-modules-bt. This should also give you AptX support, but I have not tried this (don't have a compatible set). Some notes:
Install the required minimum packages:
Code: sudo apt install libpulse-dev git cmake libdbus-1-dev libsbc-dev libavcodec-dev libltdl-dev libbluetooth-dev
Also install libpulse-dev, otherwise the backup of the original modules will fail. When running these commands, take them apart first. I mean, instead of directly executing
MODDIR=`pkg-config --variable=modlibexecdir libpulse`
fist try to run
pkg-config --variable=modlibexecdir libpulse
to see if that works.
Pull the sources and do the install mode "A. build for PulseAudio releases (e.g., v12.0, v12.2, etc.)". This worked for me.
Edit /etc/pulse/default.pa to configure everything.
In contrast to what's on the GitHub page, look for "discover", as there is already an entry for the module "module-bluetooth-disvover".
Code: .ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover a2dp_config="sbc_min_bp=53 sbc_max_bp=53"
.endif
Play around with the parameters "sbc_min_bp" and "sbc_max_bp". To test if the new module is working, set both values to e.g. 2. Then run
pulseaudio -k; pulseaudio --start
Reconnect your headset and listen to some music. This setting should give a very low quality, but now you know it's working. Then try to find the highest possible values where the payback does not yet stutter. For me, around 36-38 seems to work (EDIT: 53, the maximum value, also works fine for me). If you're happy with the result, you can remove the "sbc_max_bp" option.
I haven't messed around with the other options. I would love to hear about experiences and settings.
All the best,
Sebastian
|
|
|
|
| Mobian |
|
Posted by: jesica - 07-23-2020, 12:13 PM - Forum: Mobian on PinePhone
- Replies (4)
|
 |
Hey all
I installed Mobian on my PinePhone and loved it
2 errors
when my phone is in idle mode my screen keeps popping up the date and time, can I switch it of to save battery?
The big issue I have is that when I play music on is, my volume buttons dont work, I can switch my music lower or higher, does anyone has a fix on it please
Regards
|
|
|
|
| not enough free space in /var/cache/apt/archives |
|
Posted by: HLing - 07-23-2020, 11:04 AM - Forum: Mobian on PinePhone
- Replies (7)
|
 |
I keep putting off asking for help, have been looking on line for a solution to the various messages of "not enough disk space in file system root.." that comes up on my phone. I have attempted to resize when I use Jumpdrive and then the disk utility or gparted on my desktop, but one time I think I wiped the wrong partition, and then despite reading and reading, I just don't have a clear idea of how to go about increasing the root file system without wiping everything. I have the 7-17-20 image flashed to the EMMC. I'm now unable to update due to not enough free space in /var/cache/apt/archives for the 92.6MB of archives.
Your help would be appreciated. I apologize for asking what must seem elementary to you all....
|
|
|
|
| Earpiece emits static |
|
Posted by: User 18618 - 07-23-2020, 09:58 AM - Forum: PinePhone Hardware
- Replies (4)
|
 |
For reference, I am using a Braveheart with Mobian
Does anyone else suffer from the earpiece emitting static (at full volume?)
Curious if this is caused by the hardware, software, or potential water ingress.
|
|
|
|
| Caught between a Rock and a Hard place ! |
|
Posted by: GreyLinux - 07-23-2020, 09:36 AM - Forum: General
- Replies (4)
|
 |
Hi all,
I thought I would start a thread to help me decide whether to purchase a Rockpro64 or wait for the upcoming Hardrock64. I started a thread in the Rockpro64 section of the forum to decide whether I was asking a little to much of the SBC to host all the services , I would like and after a bit of discussion away from the forum, I think the Rockchip RK3399 SOC with Mali T860 MP4 GPU will more than meet my needs .
That being said I cant decide between the 2 devices which hold this chip and GPU, essentially the main objective is to have OpenMediaVault run as the main contender on the board with the other services in docker.
The rockpro64 with NAS case , PCI-e to Dual SATA-II Interface Card and 2 SSD's more than suits this need, but with the smaller form factor of the Hardrock64 and the minimal difference in speed over usb 3.0 to sata cable, compared to the PCI-e card is really enticing .
The Hardrock64 would provide me with a smaller form factor overall which is brilliant but the lack of a case and fan setup steers me back towards the Rockpro64 setup .
So I turn to the wisdom and opinions of the community to help me win the battle between the 2 contenders .
thanks in advance
|
|
|
|
|