Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,473
» Latest member: Samliams
» Forum threads: 16,196
» Forum posts: 116,875
Full Statistics
|
|
|
Number of PinePhone units sold/ordered so far |
Posted by: Dhanvanthri - 08-25-2021, 02:22 AM - Forum: General Discussion on PinePhone
- Replies (1)
|
 |
Hey guys,
I'm just trying to get a rough estimate of the number of devices (PinePhones) sold for some personal research, could someone please tell how many batches have been sold so far, and the approximate count of devices per batch? I would greatly appreciate it.
W.R.T. the same, I would love to talk to someone on the Pine team about the economics of selling a niche devices that requires coordinating global supply and logistics like this. I understand that the pinephone wasn't primarily intended to generate a profit, but rather, get the device into the hands of as many people as possible. However I'm still interested.
Thanks
|
|
|
Pinebook Pro Stopped Charging via USB-C |
Posted by: MickTheGeek - 08-24-2021, 01:30 PM - Forum: General Discussion on Pinebook Pro
- Replies (4)
|
 |
Hello everyone.
I'm having a problem with the charging on my PBP. A few days ago, all of s sudden the PBP stopped charging via the USB-C port. I was down to about 39% of charge so I decided to charge it overnight using the same `USB-C charger I have been using all along. When I checked the PBP in the morning, the charge was still at 39%. I have tried a different charge cable and still same results. The battery indicator on the PBP is indicating that it is charging, but the level never increases. Does anyone have any solutions or ideas? Any help is appreciated. Thanks.
/Michael Biel
|
|
|
Clean-slate flashing vs upgrading |
Posted by: 3x5co - 08-24-2021, 12:43 PM - Forum: Mobian on PinePhone
- Replies (8)
|
 |
I bought the UBports editions of the PinePhone, and around January of this year I flashed Mobian onto it. Since then, I've been upgrading packages regularly, and seen some improvements, but the phone doesn't seem to be getting any faster, and in fact it's running the battery down faster now than before.
Are there any benefits to flashing a new image, vs simply keeping the phone up-to-date?
|
|
|
Paste button does not work |
Posted by: Angle - 08-24-2021, 12:02 PM - Forum: Manjaro on PinePhone
- No Replies
|
 |
So I'm using a pineohone, with the pre-installed OS (Manjaro, I'm pretty sure). Right now I'm trying to set up Tootle, so I can use my mastodon account. Trouble is, I cannot get the paste button to work to enter the confirmation code. I can reliably bring up the prompt, by entering some text, highlighting it, and then tapping on it - but when I tap the paste button, nothing happens. I'm not sure if this is an issue with Tootlde, or Manjaro - I thiiink KDE plasma might be at fault? Not sure though. Anyway, is this a bug, or is there a setting I need to change somewhere, or is pasting just not as simple as tapping a button when I have something saved to keyboard...? I also cannot drag the cursor around text fields - it has that hanging indicator below, but when I try and tap and drag that to move the cursor, it does not work. This makes using text fields much, much harder. I'm also having issues with the keyboard not disappearing when I tap outside a text field, making it really hard if not impossible to use some apps - in this case, I'm really struggling with kmail.
|
|
|
What does an OTA Update look like |
Posted by: lsitongia - 08-24-2021, 10:20 AM - Forum: UBPorts on PinePhone
- No Replies
|
 |
I suppose this is an odd sort of question.
One thing I have never understood about OTA updates (I also run UBPorts on a Nexus 4 and have it configured for the devel channel), is how one sees them delivered. When I go into Settings and run Updates there is usually an update available (today is is 657). It installs via wifi. That's not an OTA, right? What does it look like to be notified of an OTA update?
|
|
|
Pinephone IMEI changing info: do you think its OK for a Wiki? |
Posted by: mikeb - 08-24-2021, 10:09 AM - Forum: PinePhone Hardware
- Replies (28)
|
 |
Dear friends, recently I have submitted the IMEI changing info to the PinePhone Wiki - see below! Unfortunately, we are having a disagreement with another Wiki contributor who has reverted my edits without having a prior discussion. My point of view:
Quote:Unfortunately, I noticed that "IMEI check and change" has been reverted for the reason "Illegal wiki contents removed". Please tell, "illegal" - in what country? I.e. PINE64 is a Hong Kong company, while a Pine64 wiki website is hosted in Slovakia, - and I can't any info that changing IMEI in either Hong Kong or Slovakia is illegal, or at least posting the "how-to" information about this. And what isn't forbidden - is allowed. For the majority of countries (not taking some totalitarian ones into account), changing IMEI is as legal as changing the MAC address which has been allowed to stay.
Since a "pinephone change imei" seems to be a popular Google request - it's even more popular than "pinephone change os"! - I'd like to preserve this information for the public usage. If, to be able to do that, I need to re-word/extend the warning about the possible legal issues (something like "please check the laws of your country before doing that") - please let me know.
At the same time I understand this advanced information is probably not suitable for the main PinePhone page. Please tell what's the more appropriate place in your opinion - PineModems, PinePhone_Software_Tweaks or PinePhone_FAQ#Modem ?
However, I didn't hear any valid reasoning in response: the only reply I got in regards to this - is:
Quote:Please don't re-add information regarding the IMEI on the wiki.
Personally I believe that information should be free - and, if someone would like to change IMEI of his PinePhone for privacy reasons, it's better if he/she learns this info from a trusted place such as PinePhone Wiki and with a warning accompanying this message. And you - do you believe that this information is OK for a Wiki?
Quote:== AT commands ==
A list of documented AT commands can be found in the document-link-here from Quectel. In example, to show the current IMEI number:
Code: sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=0,7
> EOF
cat ./out.txt # to see the IMEI
Also, there are certain undocumented AT commands. In example, to change the PinePhone IMEI number to a valid newIMEI one:
Code: sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=1,7,"newIMEI"
> EOF
cat ./out.txt # should output OK
Then use AT+EGMR=0,7 to see if IMEI has been changed successfully, - and, to see that IMEI change is persistent: shutdown a phone, remove a battery, press a power button to discharge the motherboard, put a battery back, turn on the phone and run AT+EGMR=0,7 again.
Such a command has to be approached with caution: although in the majority of countries changing IMEI by itself is not illegal (or at least not prosecuted unless you are doing something malicious using this capability), still a cellphone service provider may ban your IMEI and/or phone number if it sees two cellphones with the same IMEI being used simultaneously. So it should be done with common sense: in example, if you don't want your cellphone service provider (or the governmental/commercial entities it could be supplying with information) to know that you have replaced your old phone, you could change the IMEI of your PinePhone to be identical to your old phone's, just avoid using them simultaneously or at least don't connect them to the same provider.
Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website here.
|
|
|
PulseAudio: connection terminated/daemon killed |
Posted by: Zombie Feynman - 08-24-2021, 09:48 AM - Forum: Mobian on PinePhone
- No Replies
|
 |
When trying to play music, I'm getting "connection terminated" errors from PulseAudio. This happens with Clementine (my preferred player), Lollypop and VLC, and most likely others as well. This will either happen immediately, or after a few seconds of starting a track; either way, playback stops.
Digging through the system journal, I can see that PulseAudio is somehow getting killed: when triggering the bug, get the following from journalctl | grep -i pulse:
Code: Aug 24 17:22:10 mobian sm.puri.Phosh.desktop[3219]: 17:22:10.354 ERROR GstEnginePipeline:718 1 "../ext/pulse/pulsesink.c(1750): gst_pulseringbuffer_commit (): /GstPipeline:pipeline/GstBin:audiobin/GstAutoAudioSink:autoaudiosink-1/GstPulseSink:autoaudiosink-1-actual-sink-pulse"
Aug 24 17:22:10 mobian callaudiod[2082]: Error in PulseAudio context: Connection terminated
Aug 24 17:22:10 mobian systemd[660]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Aug 24 17:22:10 mobian sm.puri.Phosh.desktop[3219]: 17:22:10.367 ERROR GstEnginePipeline:718 1 "../ext/pulse/pulsesink.c(412): gst_pulsering_is_dead (): /GstPipeline:pipeline/GstBin:audiobin/GstAutoAudioSink:autoaudiosink-1/GstPulseSink:autoaudiosink-1-actual-sink-pulse"
Aug 24 17:22:10 mobian sm.puri.Phosh.desktop[3219]: 17:22:10.368 ERROR GstEnginePipeline:718 1 "../ext/pulse/pulsesink.c(412): gst_pulsering_is_dead (): /GstPipeline:pipeline/GstBin:audiobin/GstAutoAudioSink:autoaudiosink-1/GstPulseSink:autoaudiosink-1-actual-sink-pulse"
Aug 24 17:22:10 mobian sm.puri.Phosh.desktop[3219]: 17:22:10.369 ERROR GstEnginePipeline:718 1 "../ext/pulse/pulsesink.c(412): gst_pulsering_is_dead (): /GstPipeline:pipeline/GstBin:audiobin/GstAutoAudioSink:autoaudiosink-1/GstPulseSink:autoaudiosink-1-actual-sink-pulse"
Aug 24 17:22:10 mobian sm.puri.Phosh.desktop[3219]: 17:22:10.370 ERROR GstEnginePipeline:718 1 "../ext/pulse/pulsesink.c(412): gst_pulsering_is_dead (): /GstPipeline:pipeline/GstBin:audiobin/GstAutoAudioSink:autoaudiosink-1/GstPulseSink:autoaudiosink-1-actual-sink-pulse"
Aug 24 17:22:10 mobian systemd[660]: pulseaudio.service: Failed with result 'signal'.
Aug 24 17:22:10 mobian systemd[660]: pulseaudio.service: Consumed 1.265s CPU time.
Aug 24 17:22:10 mobian systemd[660]: pulseaudio.service: Scheduled restart job, restart counter is at 20.
Aug 24 17:22:10 mobian systemd[660]: pulseaudio.service: Consumed 1.265s CPU time.
Aug 24 17:22:10 mobian pulseaudio[3263]: Stale PID file, overwriting.
Aug 24 17:22:12 mobian sm.puri.Phosh.desktop[3219]: 17:22:12.023 ERROR GstEnginePipeline:718 2 "../ext/pulse/pulsesink.c(1750): gst_pulseringbuffer_commit (): /GstPipeline:pipeline/GstBin:audiobin/GstAutoAudioSink:autoaudiosink-19/GstPulseSink:autoaudiosink-19-actual-sink-pulse"
Aug 24 17:22:12 mobian callaudiod[2082]: Error in PulseAudio context: Connection terminated
Aug 24 17:22:12 mobian sm.puri.Phosh.desktop[3219]: 17:22:12.032 ERROR GstEnginePipeline:718 2 "../ext/pulse/pulsesink.c(412): gst_pulsering_is_dead (): /GstPipeline:pipeline/GstBin:audiobin/GstAutoAudioSink:autoaudiosink-19/GstPulseSink:autoaudiosink-19-actual-sink-pulse"
Aug 24 17:22:12 mobian sm.puri.Phosh.desktop[3219]: 17:22:12.037 ERROR GstEnginePipeline:718 2 "../ext/pulse/pulsesink.c(412): gst_pulsering_is_dead (): /GstPipeline:pipeline/GstBin:audiobin/GstAutoAudioSink:autoaudiosink-19/GstPulseSink:autoaudiosink-19-actual-sink-pulse"
Aug 24 17:22:12 mobian sm.puri.Phosh.desktop[3219]: 17:22:12.038 ERROR GstEnginePipeline:718 2 "../ext/pulse/pulsesink.c(412): gst_pulsering_is_dead (): /GstPipeline:pipeline/GstBin:audiobin/GstAutoAudioSink:autoaudiosink-19/GstPulseSink:autoaudiosink-19-actual-sink-pulse"
Aug 24 17:22:12 mobian systemd[660]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
Aug 24 17:22:12 mobian systemd[660]: pulseaudio.service: Failed with result 'signal'.
Aug 24 17:22:12 mobian systemd[660]: pulseaudio.service: Scheduled restart job, restart counter is at 21.
Aug 24 17:22:12 mobian pulseaudio[3279]: Stale PID file, overwriting.
Strangely, dmesg does not reveal any segfaults or OOM kills. When I run
Code: pulseaudio -k; pulseaudio -vvvv --log-target=/home/mobian/pa_`date +%s`.log
and trigger the fault, I get the following log: http://dpaste.com/897C89EQP. Strangely, it doesn't look like PA is killed here. When the problem is triggered, the repeated lines
Code: D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC0 is accessible: yes
D: [pulseaudio] module-udev-detect.c: Resuming all sinks and sources of card alsa_card.platform-sound.
are produced, and nothing else.
This does not happen with the audio from calls, nor, as far as I can tell, from videos played in Chromium.
At the moment, I can get VLC to work if I bypass PA altogether (env -i DISPLAY=:0 HOME=$HOME vlc does the trick), but I would of course like to get this fixed properly. Any pointers, anyone?
EDIT: issue persists after switching to Mobian Unstable. 
EDIT 2: problem also persists after disabling SHM, but I managed to get a better log by adding -vvvv in the systemd unit: http://dpaste.com/DA4XGCLR8
EDIT 3: also a crash with VLC: http://dpaste.com/8GREDS53M
EDIT 4 "fixed" by adding --realtime=no to the arguments in /usr/lib/systemd/user/pulseaudio.service.
|
|
|
Wi-Fi/Bluetooth for PINE64, Model: Sopine A64 |
Posted by: lamson - 08-24-2021, 08:17 AM - Forum: Getting Started
- No Replies
|
 |
I am new to the PINE64 world so please excuse me if I don’t make any sense.
I have a Sopine baseboard with the optional RTL8723BS wifi/bt module. The Sopine is flashed with an OpenWrt v.21.02-rc4 OS. I installed the driver for RTL8723BS along with its firmware. From here, I’d expect the Sopine to detect the Bluetooth through UART and WiFi through SDIO. However, the Sopine does not show any indication that it detects the wifi/bt module.
Using OpenWRT, How can I confirm that the Sopine detects the Wifi module with SDIO interface? Same with Bluetooth UART?
What is the device path related to /sys/devices/?
|
|
|
|