Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,422
» Latest member: fnosai
» Forum threads: 16,178
» Forum posts: 116,806
Full Statistics
|
Latest Threads |
booting is looping
Forum: PineNote Software
Last Post: jabi27
Today, 01:36 AM
» Replies: 2
» Views: 41
|
Can’t login to Linux
Forum: Linux on Pinebook Pro
Last Post: fnosai
Today, 12:30 AM
» Replies: 0
» Views: 52
|
* /lib64 is a symbolic li...
Forum: PineNote Software
Last Post: jabi27
Yesterday, 10:01 PM
» Replies: 2
» Views: 51
|
Invalid Signature by m-we...
Forum: PineNote Software
Last Post: Francus
07-25-2025, 05:26 AM
» Replies: 0
» Views: 61
|
Pinetab2 not starting
Forum: PineTab Hardware
Last Post: biketool
07-25-2025, 03:04 AM
» Replies: 12
» Views: 6,618
|
incorporate a multimeter ...
Forum: General
Last Post: angelaeng
07-24-2025, 10:41 PM
» Replies: 1
» Views: 291
|
invalid signatures
Forum: Getting Started
Last Post: Dendrocalamus64
07-24-2025, 08:35 PM
» Replies: 2
» Views: 224
|
Pinebook problem
Forum: General Discussion on Pinebook Pro
Last Post: mikehenson
07-24-2025, 07:28 AM
» Replies: 1
» Views: 103
|
? Introducing RoutineHero...
Forum: General Discussion on PineTime
Last Post: oscar-gardiazabal
07-24-2025, 03:25 AM
» Replies: 0
» Views: 74
|
pinetab2 danctnix broken ...
Forum: PineTab Software
Last Post: acruhl
07-23-2025, 06:27 PM
» Replies: 6
» Views: 313
|
|
|
Problem with wifi |
Posted by: kubussz - 04-02-2022, 12:57 PM - Forum: Mobian on PinePhone
- No Replies
|
 |
I have a problem with wifi. Disconnects after a minute and does not want to search for access points . It happened after some update. Anyone have this problem too?
|
|
|
Pinephone woon't stay registered |
Posted by: jhasler - 04-01-2022, 04:24 PM - Forum: Mobian on PinePhone
- Replies (10)
|
 |
Pinephone beta edition purchased last month. Installed Mobian and a Tracfone sim. Activated it successfully. I can occasionally complete a call but it always gets terminated within a minute or two. A typical log extract is included below.
Apr 01 17:05:03 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:05:03 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:05:03 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
Apr 01 17:05:04 mobian ModemManager[600]: <info> [modem0/call1] call state changed: dialing -> ringing-out (unknown)
Apr 01 17:05:05 mobian ModemManager[600]: <info> [modem0/call1] call state changed: ringing-out -> active (unknown)
Apr 01 17:05:07 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (home -> idle)
Apr 01 17:05:07 mobian ModemManager[600]: <info> [modem0] state changed (registered -> enabled)
Apr 01 17:05:07 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:05:07 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:05:07 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
Apr 01 17:05:55 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (home -> idle)
Apr 01 17:05:55 mobian ModemManager[600]: <info> [modem0] state changed (registered -> enabled)
Apr 01 17:05:55 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:05:55 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:05:55 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
Apr 01 17:05:58 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (home -> idle)
Apr 01 17:05:58 mobian ModemManager[600]: <info> [modem0] state changed (registered -> enabled)
Apr 01 17:05:58 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:05:58 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:05:58 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
Apr 01 17:06:00 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (home -> idle)
Apr 01 17:06:00 mobian ModemManager[600]: <info> [modem0] state changed (registered -> enabled)
Apr 01 17:06:00 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:06:00 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:06:00 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
Apr 01 17:06:19 mobian ModemManager[600]: <info> [modem0/call1] call state changed: active -> terminated (unknown)
Apr 01 17:06:29 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (home -> searching)
Apr 01 17:06:29 mobian ModemManager[600]: <info> [modem0] state changed (registered -> searching)
Apr 01 17:06:29 mobian ModemManager[600]: <warn> [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
Apr 01 17:06:29 mobian ModemManager[600]: <warn> [modem0] couldn't load operator name: Current operator id is still unknown
Apr 01 17:07:02 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (searching -> idle)
Apr 01 17:07:02 mobian ModemManager[600]: <info> [modem0] state changed (searching -> enabled)
Apr 01 17:07:02 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:07:02 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:07:02 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
|
|
|
Android 11 4k HDR |
Posted by: shaggy013 - 04-01-2022, 08:15 AM - Forum: Android on Quartz64
- Replies (6)
|
 |
Android 11.2
build with a more recent sdk for android 11
working
HDMI
4k
HDR
lan , wifi
sata (first format it through usb )
usb
ir ?
Playstore works so you can udate and add programs it is a older playstore so sure it updates but it works to normal update android
like youtube kodi etc included
added leanback launcher to have a little box experiece with the tablet build .
todo
cec ( it works in a box build , but i have no gtsv to make playstore work)
and some cosmetics to make it look nice
this is a gpt image wich you can flash for example with etcher on a sd or emmc
https://drive.google.com/file/d/1PughXW8...sp=sharing
minimal 16gb sd/emmc
i wanted to clean it up some more but somehow my clock runaway from my board , so i cannot update it right away but thought i should at least share it
|
|
|
Support response times |
Posted by: chuso - 04-01-2022, 04:53 AM - Forum: General
- Replies (5)
|
 |
Hi,
Does anyone know how long it usually takes to get a response from support?
I opened a support ticket 10 days ago and I haven't received any response yet.
|
|
|
Where do i check/post/report bugs/issues with the software? (or hardware?) |
Posted by: nande - 04-01-2022, 12:51 AM - Forum: General Discussion of PinePhone Pro
- Replies (4)
|
 |
Hello everyone,
I've read the forum rules (ofc i did ofc), and it mentions that bugs should be reported to the project repo (which makes sense to me).
I'd like to report the bugs that i find, and check the status of the ones reported (maybe what i find is already reported).
I have no idea where are those repos located. Can someone give me a url?
Im using manjaro+plasma on pinephone pro (and i love them (well im used to debian instead of manjaro, but so far is great)).
Thanks!
|
|
|
Pine64 as wireless audio device |
Posted by: S265 - 03-31-2022, 11:40 PM - Forum: General Discussion on PINE A64(+)
- Replies (3)
|
 |
Hi all, two out of three of my Pine64 devices are usefully employed. The Pinebook Pro gets most use. It runs the Manjaro kde desktop and has been a really useful tool for all sorts of things. Frequent updates come through from Manjaro - bringing improvements all the time.
The Rock64 works quietly away in the corner. It runs on Armbian Bullseye and has be very reliable, including periodic loss of power. It runs the postfix email server.
Anyway to the point. Pine64. I have seen frequent blogs and how-to's about using the Raspberry Pi for an Audio wireless connection to any speaker.
Can we use the Pine64 for this purpose. I would probably need a dac on it, and power supply. Has anyone done this? Do you see any problems?
The Pine64 is no cost while the Raspberry Pi would be an additional cost for this idea.
|
|
|
Not Bypassing the eMMC |
Posted by: meansbs - 03-31-2022, 06:42 PM - Forum: General Discussion of PinePhone Pro
- Replies (3)
|
 |
So far I've made no changes to my PinePhone Pro Explorer edition. I received it back in January, got super frustrated and shelved it until last week when I got it back out and started fiddling again.
On a surface level, I see, booting consists of:
Pressing the power button
6 seconds go by
Vibration for 1 second
Red light for 2 seconds
White light for 1 second
blank screen
boot screen
[ 0.232045] rockchip-usb2phy ff770000.syscon:usb2phy@e460: failed to create phy
[ 0.429706] imx258 1-001a: failed to read chip id 258
[ 0.745578] bootsplash: Failed to initialize.
Warning: /lib/modules/5.16.2-2-MANJARO-ARM/modules.devname not found - ignoring
Starting version 250.3-1-arch
ROOT_MNJRO: recovering journal
ROOT_MNJRO: Clearing blah, blah, blah, blah .....
Several places provide instructions for bypassing the eMMC by "hold the RE button underneath the cover for a few (or multiple) seconds, while powering on the device" and "holding it too long will cause the eMMC to not get initialized after the boot".
I have a PNY256 GB microSD card with postmarketOS flashed to it in the microSD slot under the back cover. I have verified the phone sees it by loading Manjaro and checking for /dev/mmc* and looking with the gnome disks utility. Gnome disks shows it as mmcblk1, partition 1 pmOS_boot, partition 2 pmOS_root, Partition Type Linux (Bootable).
I've pressed the RE button before, during and after the power button, the 6 second interval, the vibration, the red light, the white light, the blank screen and the boot screen. I've pressed the RE button it quickly, I've pressed it for a few seconds, I've pressed it for several seconds during all the various power on events.
Any of the combination described result in either the boot sequence freezing where it is, Manjaro booting normally, or I get dumped into an emergency shell. At no point have ever been able to boot from the microSD. I've also tried different operating systems on different SD cards.
What am I doing wrong? If someone could literally spell it out for me I'd be very appreciative.
Thanks.
|
|
|
|