Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,398
» Latest member: buffiano
» Forum threads: 16,167
» Forum posts: 116,768
Full Statistics
|
Latest Threads |
New Install, apps start b...
Forum: Mobian on PinePhone
Last Post: RT3
1 hour ago
» Replies: 0
» Views: 6
|
pinetab2 danctnix broken ...
Forum: PineTab Software
Last Post: acruhl
1 hour ago
» Replies: 0
» Views: 4
|
US Mobile, via T-Mobile, ...
Forum: General Discussion on PinePhone
Last Post: dchang0
1 hour ago
» Replies: 14
» Views: 10,648
|
many distros getting too ...
Forum: PinePhone Pro Software
Last Post: dchang0
1 hour ago
» Replies: 3
» Views: 69
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
3 hours ago
» Replies: 1
» Views: 48
|
Who remembers the Parall...
Forum: General
Last Post: paracpg
Today, 02:41 AM
» Replies: 9
» Views: 10,025
|
touchscreeh doesn't accep...
Forum: PinePhone Pro Hardware
Last Post: henrythemouse
Yesterday, 08:16 PM
» Replies: 9
» Views: 914
|
What's a good image to us...
Forum: Linux on Pinebook Pro
Last Post: Dendrocalamus64
Yesterday, 02:26 PM
» Replies: 39
» Views: 9,296
|
boot gets stuck shortly a...
Forum: Mobian on PinePhone
Last Post: demetemre
07-16-2025, 10:50 AM
» Replies: 10
» Views: 7,882
|
Cannot pay with credit ca...
Forum: General
Last Post: hannaconner
07-15-2025, 10:56 PM
» Replies: 0
» Views: 59
|
|
|
Horizontal lines appearing on Display in bright conditions |
Posted by: harrywoods - 12-12-2024, 09:20 PM - Forum: General Discussion on PineTime
- Replies (1)
|
 |
Recently, I’ve noticed that in bright environments, particularly when I’m outside, there are pairs of horizontal lines appearing on the screen. This happens regardless of whether the display is active or not.
The lines seem to be most prominent in the area around the analog watch face, which is also where I tend to touch the screen frequently. It’s quite distracting and affects the overall visual experience, making it difficult to use the device comfortably.
I’ve tried capturing a photo to show you what I’m seeing, but due to the reflective nature of the display glass, it was challenging to get a clear image. However, I hope that my description helps convey the issue.
Here are a few additional details:
This problem has been occurring for some time now, and I can’t pinpoint when it started.
The lines are visible only in bright light conditions; in dimmer environments, the display looks normal.
I’m curious if anyone else has experienced something similar or if this is a known issue with the device.
Could this be a hardware problem, or might it be related to the display technology itself? Any insights or suggestions on how to address this would be greatly appreciated.
|
|
|
Installing r2kaw and Tow-Boot to the SPI |
Posted by: ethical_haquer - 12-11-2024, 04:54 PM - Forum: PinePhone Pro Software
- Replies (10)
|
 |
I am trying to get r2kaw and Tow-Boot installed to the SPI of the PPP at the same time.
I can install Tow-Boot to the SPI, and I can install r2kaw to the SPI, but I haven't figured out how to have both on the SPI.
For installing Tow-Boot to the SPI, I can follow the Tow-Boot installation instructions for the PPP, under the "Installing to SPI (recommended)" section.
For installing rk2aw, I can follow the rk2aw installation instructions for the PPP, under the "Installation to SPI NOR flash" section.
Here is the relevant part of the rk2aw installation instructions:
Quote:Installation steps are:
1) Erase the SPI NOR flash compeltely and install rk2aw
# for RK3399:
./rk2aw-spi-flasher --erase-all --rk2aw rk2aw/debug.img.spi
# for other SoCs:
./rk2aw-spi-flasher --erase-all --rk2aw rk2aw/debug.img
2) Install U-Boot or other bootloader
a) U-Boot
./rk2aw-spi-flasher \
--uboot-spl u-boot-spl.bin \
--uboot-tpl u-boot-tpl.bin \
--uboot-itb u-boot.itb
(The above 3 files are normal build artifacts of U-Boot. You get them from
a regular defconfig U-Boot build for your board.)
b) Other bootloaders
./rk2aw-spi-flasher \
--spl levinboot-emmc.img
If flashing fallback bootloader add --replace-fallback to the above commands.
Although the instructions mention U-Boot and "other bootloaders", they don't directly mention Tow-Boot. So my first question was, what category does Tow-Boot fall under? U-Boot, since it's based off U-Boot, or "other bootloaders".
After downloading and extracting the "pine64-pinephonePro-2023.07-007.tar.xz" file from the latest Tow-Boot release, this is what I got:
Code: $ tree ./pine64-pinephonePro-2023.07-007
./pine64-pinephonePro-2023.07-007
├── binaries
│ ├── Tow-Boot.noenv.bin
│ └── Tow-Boot.spi.bin
├── config
│ ├── noenv.config
│ └── spi.config
├── shared.disk-image.img
└── spi.installer.img
3 directories, 6 files
So there aren't the three "u-boot-spl.bin", "u-boot-tpl.bin", and "u-boot.itb" files mentioned in the U-Boot instructions, nor are there Tow-Boot equivalents.
Next I tried using the "shared.disk-image.img" file for the "Other bootloaders" method:
Code: ./rk2aw-spi-flasher --spl shared.disk-image.img
...
ERROR: File shared.disk-image.img is too big for the buffer size 1048576
Then I tried with "spi.installer.img":
Code: ./rk2aw-spi-flasher --spl spi.installer.img
...
ERROR: File spi.installer.img is too big for the buffer size 1048576
That's what I've tried so far. Any tips would be appreciated!
TIA, ethical_haquer
|
|
|
Issues with Biktorgj Custom Modem Firmware |
Posted by: JadenSki - 12-11-2024, 04:32 PM - Forum: General Discussion of PinePhone Pro
- Replies (4)
|
 |
So I recently decided to install Biktorgj's Custom Modem Firmware on my ppp, as it said in the documentation, there is no reason not to, and only added benefit. I installed it using this guide. After the installation, everything seemed to work fine (eg. sms, calls...). I then tried to communicate with the modem using sms as is described here. My messages didn't send, however, and I never received any responses. I also discovered a weird bug where my audio and mic will completely stop working for calls. I cannot hear or be heard by the other phone. Also when I check my voicemail, I hear no audio either. I don't know for sure if the firmware is causing the issue or not, but, it didn't happen until after the installation. Rebooting does not seem to do anything, however, it will randomly start working again before it quits once again. Any insight or advice on these issues will be greatly appreciated. I am currently running the latest stable version of Mobian with Posh. Thanks in advance!
|
|
|
Mobian, Suspend, and Audio Playback |
Posted by: biketool - 12-11-2024, 12:56 AM - Forum: Mobian on PinePhone
- No Replies
|
 |
I have had a pocket linux device in use since around Y2k starting with a Sharp Zaurus SL-5500 on to an Openmoko, then the N900.
One of the most important purposes of these devices was to play audiobooks when driving, cycling, working, or riding public transportation.
On all other devices I was able to get at least 5-8 hours of audiobook playback minimum along with other uses of the device, even with the Openmoko which like the Pine devices didn't have a major corporate Linux lab supporting the effort.
The pinephone(and pro) under mobian gives me around 3 hours maximum as suspend also kills off audio playback.
This severely limits my use of the PP if I cannot provide external power.
I know there are several ways to except the hardware audio acceleration chip from suspend and buffer only the audio stream as well as waking only one of the smaller CPUs for a fraction of a second to do a disk read and reload the audio buffer.
I am not sure how it was done on the N900 but I am sure someone on the forum has better insight into a power saving way to keep a streaming audio app working even when the system is in suspend, even if it is a lower level system hack.
<edit>
For example I can go most of the day dropping to ~80% battery if I don't use my phone much, I can still reliably receive calls and SMS but have it set to suspend after 1 minute. Same Mobian Trixie install drops to 30-40% after 2 hours if I set suspend to 30 minutes but blank the screen so I can listen to an audiobook on the bus/train. Once the 30 minutes are up if I have not touched the phone the audio playback will stop and I have to restart the Cozy(flatpak install) audiobook app to get it's audio to work.
|
|
|
Booting Issues |
Posted by: Halfgreek - 12-10-2024, 08:13 AM - Forum: PineNote Software
- Replies (17)
|
 |
I just receved my new PineNote 2 days ago with Debian installed and was working well with it until I woke up yesterday and the device will not boot into anything, The display remains at "Booting..." or "PineNote is Booting" and i am unable to get to Uboot or anything to see what I can do to fix it. Any Suggestions?
|
|
|
pine64 gpio interrupts |
Posted by: fractal - 12-09-2024, 07:43 PM - Forum: General Discussion on PINE A64-LTS / SOPINE
- No Replies
|
 |
Not sure if this is a general question or a linux question but here goes.
I am coming back to a project after an extended interruption -- life got in the way of my play.
I have a number of GPS units running on a variety of hardware. The board I use for most of them is also allwiner based and run the same armbian as the pine64. But, I like pine64's as a general purpose board and have several on my desk so decided to track down why I couldn't get them to work the way I wanted last time.
That background information is not particularly normative but it offers some background. You don't need any special hardware to reproduce this issue.
My notes from many years ago says there was a post on IRC which confirmed we can not get interrupts from some of the GPIO banks. I can no longer find that reference but that seems to be true.
I can confirm that
Code: overlays=pps-gpio
param_pps_pin=PH9
in armbianEnv.txt works with dmesg containing
Code: [Mon Dec 9 23:58:56 2024] pps pps0: new PPS source pps@0.-1
[Mon Dec 9 23:58:56 2024] pps pps0: Registered IRQ 100 as PPS source
I can also confirm that
Code: overlays=pps-gpio
param_pps_pin=PC8
in armbianEnv.txt fails with dmesg containing
Code: [Tue Dec 10 00:04:25 2024] pps-gpio pps@0: failed to map GPIO to IRQ: -22
[Tue Dec 10 00:04:25 2024] pps-gpio: probe of pps@0 failed with error -22
I got as far as https://github.com/torvalds/linux/blob/m...pio.c#L175 returning -EINVAL (-22) where I found it using deprecated functions to get the interrupt so it might just be something to do with the pps-gpio client.
The board that pps-gpio likes has pin 12 of the pi2 bus going to gpio PA6 whereas the pine64 connects pin 12 to gpio PC8 -- different banks on controller 0.
Anyway, for the question - are GPIO's on bank C expected to be able to generate interrupts? If so, I'll queue further investigation. Otherwise I'll limit my selection to pins in the PH bank, or use the euler bus.
|
|
|
|