| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,005
» Latest member: Jeebies
» Forum threads: 16,338
» Forum posts: 117,450
Full Statistics
|
| Latest Threads |
Volumio (PINE A64-LTS / S...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: shinzuka
5 hours ago
» Replies: 9
» Views: 16,771
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
Yesterday, 07:07 AM
» Replies: 14
» Views: 15,159
|
Volumio 3 Pine A64+ unoff...
Forum: Linux on Pine A64(+)
Last Post: shinzuka
05-02-2026, 10:49 AM
» Replies: 0
» Views: 9
|
Mobian image for the Pine...
Forum: Mobian on PinePhone
Last Post: Korfou
04-27-2026, 09:57 AM
» Replies: 2
» Views: 282
|
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
04-18-2026, 10:08 AM
» Replies: 0
» Views: 230
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 19,726
|
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,147
|
my pinecil v2 is not work...
Forum: General Discussion on Pinecil
Last Post: jagrav
04-17-2026, 06:28 AM
» Replies: 0
» Views: 164
|
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,520
|
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 350
|
|
|
| Streaming video sites |
|
Posted by: tessa - 01-14-2023, 01:58 PM - Forum: Linux on Pinebook Pro
- Replies (1)
|
 |
Hi everyone,
I've been reading sites and trying fixes for a while and I've been able to get Disney+ and Netflix running in chromium-docker on Manjaro. So far, I haven't figured out how to get Amazon Prime or Paramount+ working. Has anyone had any success with these?
Thanks,
Tessa
|
|
|
|
| Roshambo 2023 |
|
Posted by: angeloweb - 01-13-2023, 10:45 PM - Forum: General Discussion on ROCKPRO64
- Replies (2)
|
 |
I saw the Roshambo case on the Pine64 store. Trying to understand components and assembly.
I see that a power supply and board are required - RockPro64 is recommended. It says that the ssd "cartridge" is optional. I see that the board comes with 2 or 4GB RAM, but doesn't seem to have storage.
From the site - "There is also an optional eMMC module (up to 128GB) and microSD slot for booting." If the ssd is optional and the eMMC is optional, how is the R-Cade system installed/stored?
Other than the case, board, power supply, and a couple of controllers, is there anything else I would need?
Thanks
|
|
|
|
| Mycroft/Picroft on Rockppro64 |
|
Posted by: misterc - 01-13-2023, 06:29 PM - Forum: RockPro64 Projects, Ideas and Tutorials
- No Replies
|
 |
I was playing with picroft on my old RPI3 + AIY Voicehat and it was just too slow for some functions, so considering the difficulty obtaining an RPI4 w/o selling limbs, I wanted to try getting it up and running on the RockPro.
One of the reasons I grabbed the RockPro was the "PI-2" gpio connector that is, more or less, compatible with the Rpi 40 pin. I was hoping to reuse the Voicehat (which provides a nice mic array and amplified speaker output).
Installing the Mycroft software was easy enough but I soon discovered that the driver that was written for the "googlevoicehat-soundcard" was, for some inane reason, held in the sound/soc/bcm area of the kernel and it's dts claimed it needed the RPI BCM processor (it's a dac/adc/amp combo it shouldn't be tied to a specific processor.
The driver is in Raspi but I don't think it was ever in mainline kernel, or if it was, it was dropped before Linux 5.
So, not being a kernel hacker, I've walked away from that idea.
I have ordered an inexpensive USB Speakerphone and will see how that works and update here.
|
|
|
|
| MMS sending stopped working |
|
Posted by: amindfv - 01-13-2023, 04:00 PM - Forum: General Discussion on PinePhone
- Replies (7)
|
 |
I've been mostly-happily using the PinePhone with Mobian for a long while (years), with MMS working pretty smoothly for a long time. Recently (last 5 days or so), MMS sending has completely stopped working.
- It didn't happen after making any big software change (apt upgrade, settings change, things like that).
- Group message sending and 1-on-1 media sending no longer works
- Group and media receiving still works totally fine
- Back when MMS sending was working, I noticed that after hitting "send" on an MMS message, the screen brightness would always change for a moment (something to do with power draw to the antenna?). Now when I try to send MMS that doesn't happen.
Any idea what the problem could be?
|
|
|
|
| PinePower USB-C ports dead |
|
Posted by: nbxmike - 01-13-2023, 11:58 AM - Forum: General
- Replies (1)
|
 |
I have two PinePower 120W desktop power supplies, both have lost the USB-C ports. No matter what is plugged in, the display reads 0 volts. I have check the end devices and the cables with other chargers, the cables and end devices work fine. I had previously charged the same devices with these PonePower supplies.
Judging from other messages, I am starting to get the impression something is defective with the USB-C port, does anyone have a fix?
Thanks
Mike
|
|
|
|
| [solved] Black screen at boot time |
|
Posted by: mdk - 01-13-2023, 03:33 AM - Forum: Mobian on PinePhone
- No Replies
|
 |
Today my phone went to a black screen after booting, it was just a filesystem issue easy to fix by running fsck maually.
I "blogged" about it in case it can help someone someday:
https://mdk.fr/blog/black-screen-at-boot...phone.html
But I though, why asking a user to fsck manually on a phone? Is there an option Mobian could enable to just do the fsck if needed? It's not that simple as it'll still ask the user to fix or not to fix, like:
Code: Block bitmap differences: -(392704--392976) -(1246016--1246019) -(1606912--1607056) -(1607776--1607792) -(1609536--1609552) -(1611200--1611216) -(1611360--1611376) -(1621504--1621907) -1722548 -(2034240--2034256) -(2036608--2036694) -(2039808--2043903) -(2054144--2054263) -(2058240--2060287) -(2061312--2061823) -(2230912--2230945) -2455149 -(2455162--2455163) -2455612 -(2556160--2556225) -(2556352--2556384) -(2556672--2556737) -(2556832--2556848) -(2556864--2556880) -(2562304--2562433) -(2563328--2563521) -(2563584--2563729) -(2570359--2570366) -(2761279--2761286) -(2790656--2790880) -(2790912--2791104) -(2792192--2792272) -(2792448--2792528) -(2795904--2795952) -(2796224--2796240) -(2796416--2796480) -(2796512--2796528) -(2798336--2798368) -(2799488--2799520) -(2800192--2800224) -(2800448--2800464) -(2800576--2800592) -(2801280--2801296) -(2802112--2802128) -(2802464--2802480) -(2803072--2803088) -(2803904--2803920) -(2807072--2807088) -(2807200--2807216) -(2829440--2829539) -(2980568--2980576) -(3067392--3067748) -(3080224--3080240) -(3080576--3080688) -3089408 -(3092480--3092800) -(3115264--3115300) -(3272704--3273637) -(3274752--3276799) -(3310432--3310448) -(3321247--3321253) -(3346048--3346084) -(3582208--3582353) -3794232 -3794237 -(3817472--3821567) -(3827712--3829759) -(3831808--3833855) -(3859377--3859385) -(3953152--3953281) -(3963799--3963808) -(3986432--3986786) -(4143872--4144034) -(4145408--4145570) -(4191232--4191556) -(4226823--4226825) -(4235200--4235216) -(4752448--4752464) -(4789960--4790091) -(4800710--4801025) -(4814071--4814080) -(4846254--4846409) -(4852416--4852465) -(4854432--4854448) -(4883456--4883729) -(5339966--5339967) -(5397760--5397872) -(5822464--5822579) -(5822976--5823280) -(6432960--6432992) -(6434688--6434768) -(6434784--6434800) -(6439936--6440447) -(6441472--6441490) -(6791680--6792191) -(6800832--6800867) -(6858368--6858400) -(7118729--7118736) -(7144448--7144480) -(7146432--7146448) -(7154432--7154609) -(7170048--7173750) -(7174144--7174400) -(7444480--7446527)
Fix<y>? yes
Free blocks count wrong for group #11 (15917, counted=16190).
Fix<y>? yes
Free blocks count wrong for group #38 (19424, counted=19428).
Fix<y>? yes
Free blocks count wrong for group #49 (24171, counted=24788).
Fix<y>? yes
Free blocks count wrong for group #52 (9990, counted=9991).
Fix<y>? yes
Free blocks count wrong for group #62 (16515, counted=23395).
Fix<y>? yes
Which I really never understood to be honest, as I'm not training myself to remember the inode number of each of my files, and even if I remembered, I don't imagine answering "no" here... Like "no no, I don't like this file anyway, it does not deserve to be fixed, keep it in its bad state on the filesystem, that'll teach him."
|
|
|
|
|