| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,665
» Latest member: Weston234
» Forum threads: 16,242
» Forum posts: 117,139
Full Statistics
|
| Latest Threads |
Wake up Call
Forum: General Discussion on PinePhone
Last Post: biketool
2 minutes ago
» Replies: 4
» Views: 167
|
How to add an homemade ap...
Forum: Mobian on PinePhone
Last Post: JChdeL
10 hours ago
» Replies: 3
» Views: 281
|
kivy app keeping focus wh...
Forum: Mobian on PinePhone
Last Post: JChdeL
10 hours ago
» Replies: 0
» Views: 20
|
Optimizing Battery Life o...
Forum: General Discussion on PinePhone
Last Post: earthworm
11 hours ago
» Replies: 0
» Views: 39
|
Has anyone installed Tris...
Forum: General
Last Post: RandB
Yesterday, 12:08 PM
» Replies: 1
» Views: 2,181
|
Xen hypervisor on Rock64
Forum: Linux on Rock64
Last Post: darkfader
Yesterday, 09:25 AM
» Replies: 6
» Views: 9,685
|
[Article] RISC-V Ox64 BL8...
Forum: General
Last Post: smithjohns
Yesterday, 12:54 AM
» Replies: 3
» Views: 9,467
|
Pinetab2s running DanctNI...
Forum: PineTab Software
Last Post: biketool
11-02-2025, 04:45 AM
» Replies: 0
» Views: 85
|
Open-Source Support for P...
Forum: General Discussion on PineTime
Last Post: euiccc2025
11-01-2025, 05:55 PM
» Replies: 2
» Views: 2,214
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
11-01-2025, 04:04 PM
» Replies: 11
» Views: 5,691
|
|
|
| When should new OS's like Genode & NuttX RTOS get their own PinePhone subforum? |
|
Posted by: PineFone - 05-08-2023, 07:06 PM - Forum: PinePhone Software
- Replies (1)
|
 |
I stumbled on posts about the micro-kernel Genode/Sculpt OS (about 14MB from the latest OS test): https://forum.pine64.org/showthread.php?tid=14780 and the mesh network expanding to feature phone NuttX RTOS: https://forum.pine64.org/showthread.php?tid=18196 a few months ago.
Occasionally I catch updates when checking the forum or getting updates when subscribing, but I miss related new threads unless I'm lucky enough to see them when they're on the front page of the sub forums before cycling off.
It would be great to see these OS's with their own dedicated PinePhone Software sub-forums to see all related threads in the same place to avoid missing out on interesting updates.
There are currently multiple OS's with subforums that haven't been updated in a few years so it begs the question why these two very active efforts that are posting regular progress updates still haven't gotten their own.
I read much more than I post on this forum and if I'm missing some existing etiquette for this sort of thing feel free to let know.
|
|
|
|
| new PinePhone upgrade issue |
|
Posted by: WhiteHexagon - 05-08-2023, 08:44 AM - Forum: Manjaro on PinePhone
- Replies (5)
|
 |
I followed the advice to do an upgrade on my newly received PinePhone(EU). Previously it was showing KDE plasma version 5.21.2, kernal: 5.11.3-1manjaro-arm.
'sudo pacman -Syu'
I had to plug in a physical keyboard to be able to type 'Y' at the various prompts for the upgrade. But now the process has stopped with a message that I cant fully read:
Code: "roken and unlocking is r"
"witch to a virtual termin"
"and execute the comm"
"oginctl unlock-session c'"
" back to the running ses"
I can't rotate to see more, only the above is shown. large white text on black background. Any advice please on what to do? I dont have the dock for an external monitor.
|
|
|
|
| PinePhone AND/OR PinePhone Pro Arch Complete Install and Setup |
|
Posted by: mikehenson - 05-07-2023, 10:06 PM - Forum: Arch Linux on PinePhone
- Replies (3)
|
 |
I have created multiple videos on setting up a PinePhone and/or PinePhone Pro with DanctNIX Arch Linux Arm.
PinePhone (1of5) - Flash DanctNIX Arch with Phosh
https://www.youtube.com/watch?v=XNF8zuIE...99&index=8
00:00 Intro
00:20 Insert SD card
01:00 Download jumpdrive
02:00 unzip jumpdrive
03:00 umount SD card
04:10 flash jumpdrive to SD card
05:50 remove SD from computer
06:30 Download Arch Linux
06:45 Turn off the phone
07:30 unzip Arch Linux
08:00 install Jumpdrive SD into phone
09:00 plug phone into computer
09:10 turn on the phone
09:45 umount the emmc
11:15 flash Arch Linux to emmc
12:45 turn off the phone
13:45 remove SD card
14:15 turn on the phone
15:30 Password 123456
PinePhone Pro (1of5) - Flash DanctNIX Arch with Phosh
https://www.youtube.com/watch?v=FBGVUq3D...99&index=3
00:00 Intro
00:20 Download image
01:05 uncompressed image
02:20 Turn on phone
03:30 unmount phone
04:25 dd the image
07:10 Reboot the phone
08:40 DONE!
PinePhone OR PinePhone Pro (2of5) - Phosh - Setup - Updates - Packages
https://www.youtube.com/watch?v=-nbUXABJ...99&index=4
00:00 Intro
00:25 enable ssh
02:38 Change password
03:45 remove "show all apps"
04:18 Screen Scaling
05:45 Update Arch
10:30 Remove unused packages
11:05 Mount Network drive
12:45 Packages
13:05 Install gedit
13:30 Install pcmanfm
15:40 Custom Packages
17:45 Install wayvnc-git
20:20 Install aspell aspell-en
20:40 Configure gedit (spell checker)
22:15 Install gnome-screenshot
23:15 Configure pcmanfm
28:00 Change desktop Icon
PinePhone OR PinePhone Pro (3of5) - Phosh - Setup - Syncthing - Squeekboard - Online Accounts
https://www.youtube.com/watch?v=esOT5PhC...99&index=5
00:00 install Syncthing
03:00 Start syncthing
03:55 Add network computer
04:48 Share the Downloads folder
06:10 add a syncthing desktop icon
10:30 G o o g l e account
12:30 Set key ring password
14:15 calendar sync
14:40 email sync
15:00 Local contacts and calendar sync with syncthing
16:00 Should have just restarted the phone...
19:00 install evolution to trouble shoot.
20:50 just restart the phone
21:30 update the squeekboard layout
PinePhone OR PinePhone Pro (4of5) - Phosh - Setup - Biktorgj - osmin - brave
https://www.youtube.com/watch?v=QgFtFzPh...99&index=6
00:00 Intro
00:10 Log into phone
00:28 install gnome-firmware
01:00 run gnome-firmware
01:00 run gnome-firmware
03:20 Fail, Run again
04:20 Downgrade again
05:55 Biktorgj is loaded
06:30 verify the ADSP version
08:00 ... Thinking
08:05 DanctNIX tweaks app
08:10 Power
09:05 Set a background image
11:45 install wrong app...
13:55 install phosh-mobile-settings
14:40 phosh-mobile-settings
15:45 set the calendar on lock screen
17:15 Looking for power profile to sync calendars...
22:30 PinePhone verse PinePhone Pro Power
24:30 phosh-ticket-box set the folder to look in
26:15 Restart phone to see new lock screen
28:00 install osmin - Navigation app
29:40 running osmin
31:00 Try to copy already downloaded maps...
32:30 install sayonara-player
32:45 run sayonara-player
38:15 running osmin again with maps
41:25 install brave - browser
42:30 run brave browser
PinePhone OR PinePhone Pro (5of5) - Phosh - Setup - Chatty - SIM Card - SMS - MMS - Bible
https://www.youtube.com/watch?v=i10sj2WK...99&index=7
00:00 ssh
01:20 Copy Chatty files to phone
02:30 All conversations are on Chatty
03:00 Pull SIM card out of OG PinePhone
04:15 Pull apart PinePhone Pro
05:50 Service???
07:00 It Works!!!
07:40 APN settings
09:30 4G data works
09:55 Test Chatty SMS
10:30 Test 4G data
11:45 APN again???
12:50 3rd time is the charm!
13:30 SMS setup EDIT: MMS setup
15:00 Test MMS
16:00 MMS work!
16:20 bible_gui (Bible App)
18:45 run bible_gui
19:20 Download bible translations
23:00 Add translation
24:00 "~/share/net.lugsole.bible_gui/translations"
25:30 Play the Bible
26:10 Remove unwanted "desktop" icons
27:30 LEAVE A COMMENT!!!
I have both a PinePhone and PinePhone Pro. Are there any videos you would like to see?
|
|
|
|
| Is Manjaro ARM a Rolling Release? |
|
Posted by: jojuma - 05-07-2023, 01:35 PM - Forum: Manjaro on PinePhone
- Replies (4)
|
 |
Hi,
a quick question about the KDE CE:
It runs Plasma Mobile based on Manjaro ARM which is based on Arch ARM which is based on Arch.
I hope, I'm right so far.
Arch is a Rolling Release as Arch ARM is, right?
The current Manjaro ARM release is numbered "23.02".
The fact, that there is a release number like that makes me think, it's versioned and not a rolling release.
If so, why?
I searched the web for an answer, but either I wasn't able to find/see it or it is that clear to everybody (but me), no answer is necessary...
Thanks for helping out
|
|
|
|
| Sanity check on spliced charger |
|
Posted by: jcun4128 - 05-06-2023, 07:04 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (12)
|
 |
I want to know if I'm going to burn my house down with what I've made lol.
![[Image: UPQhv5R.png]](https://i.imgur.com/UPQhv5R.png)
This is a hardware fix for the PBP not waking from sleep.
My intent is to just have it plugged in most of the time but this will have a python script running on pbp to check battery voltage eg. between 20-80% and then tell the charger to stop charging or to charge.
This whole thing works. I was just concerned with the temperatures... maybe there is an obvious reason you should not do this.
With a bench top power supply it pulls 5V at 2.58A when the battery is in 50% range... maybe it pulls more when battery is near 0%.
I measured 106F bottom of the PBP case and 122F on charger surface. It was 80F in the room (AC broken).
|
|
|
|
| Zephyr Backlight Examples for PineTime |
|
Posted by: lcj - 05-06-2023, 02:54 PM - Forum: Development Discussion on PineTime
- No Replies
|
 |
This is a very junior question but I am just trying to get the backlight going using Zephyr, VS Code (with nRF Connect for VS Code Add-In), the PineTime DevKit0 board in Zephyr, and a PineTime DK.
I am trying to figure out how to do the backlight from the button example (which replaced the board specific example). I have not been able to get it working. It uses code like this:
Code: static const struct gpio_dt_spec button = GPIO_DT_SPEC_GET_OR(SW0_NODE, gpios,
{0});
static struct gpio_callback button_cb_data;
/*
* The led0 devicetree alias is optional. If present, we'll use it
* to turn on the LED whenever the button is pressed.
*/
static struct gpio_dt_spec led = GPIO_DT_SPEC_GET_OR(DT_ALIAS(led0), gpios,
{0});
void button_pressed(const struct device *dev, struct gpio_callback *cb,
uint32_t pins)
{
printk("Button pressed at %" PRIu32 "\n", k_cycle_get_32());
}
void main(void)
{
int ret;
if (!device_is_ready(button.port)) {
printk("Error: button device %s is not ready\n",
button.port->name);
return;
}
ret = gpio_pin_configure_dt(&button, GPIO_INPUT);
if (ret != 0) {
printk("Error %d: failed to configure %s pin %d\n",
ret, button.port->name, button.pin);
return;
}
ret = gpio_pin_interrupt_configure_dt(&button,
GPIO_INT_EDGE_TO_ACTIVE);
if (ret != 0) {
printk("Error %d: failed to configure interrupt on %s pin %d\n",
ret, button.port->name, button.pin);
return;
}
...
}
These other examples:
pinetime-zephyr/main.c at master · najnesnaj/pinetime-zephyr · GitHub
[/url][url=https://github.com/albsod/pinetime-hypnos/blob/master/app/hypnos/src/backlight.c]pinetime-hypnos/backlight.c at master · albsod/pinetime-hypnos · GitHub
pinetime/backlight.c at develop · ck-telecom/pinetime · GitHub
Use code which looks like this:
Code: #if DT_NODE_HAS_STATUS(LED0_NODE, okay)
#define LED0 DT_GPIO_LABEL(LED0_NODE, gpios)
#define PIN DT_GPIO_PIN(LED0_NODE, gpios)
#define FLAGS DT_GPIO_FLAGS(LED0_NODE, gpios)
#endif
static void backlight_init(void)
{
const struct device *dev;
dev = device_get_binding(LED0);
/* If you have a backlight, set it up and turn it on here */
gpio_pin_configure(dev, PIN, GPIO_OUTPUT_ACTIVE | FLAGS);
gpio_pin_set(dev, PIN, 1);
}
or this:
Code: /* ********** ********** DEFINES ********** ********** ********** */
#define BACKLIGHT_PORT DT_GPIO_LABEL(DT_ALIAS(led1), gpios)
#define BACKLIGHT_1 DT_GPIO_PIN(DT_ALIAS(led0), gpios)
#define BACKLIGHT_2 DT_GPIO_PIN(DT_ALIAS(led1), gpios)
#define BACKLIGHT_3 DT_GPIO_PIN(DT_ALIAS(led2), gpios)
/* ********** ********** ********** ********** ********** */
/* ********** ********** VARIABLES AND STRUCTS ********** ********** */
static const struct device* backlight_dev;
static bool backlight_enabled = false;
/* ********** ********** ********** ********** ********** ********** */
/* ********** ********** FUNCTIONS ********** ********** */
void backlight_init()
{
backlight_dev = device_get_binding(BACKLIGHT_PORT);
gpio_pin_configure(backlight_dev, BACKLIGHT_1, GPIO_OUTPUT);
gpio_pin_configure(backlight_dev, BACKLIGHT_2, GPIO_OUTPUT);
gpio_pin_configure(backlight_dev, BACKLIGHT_3, GPIO_OUTPUT);
backlight_enable(true);
LOG_DBG("Backlight init: Done");
}
I guess my questions is should I try to use the GPIO_DT_SPEC_GET_OR syntax or DT_GPIO_PIN, DT_GPIO_LABEL, and DT_GPIO_FLAGS.
I'm really new at this, as you can probably tell. I might be mixing things up. Trying to figure out the GPIO to turn on/off the backlight and it seems like this commonly/historically used device* structure and the gpio_dt_spec from the examples.
|
|
|
|
Star64 |
|
Posted by: cpnetserver - 05-05-2023, 01:04 AM - Forum: General
- No Replies
|
 |
Hi guys!
Does anyone know when new BXE-4-32 GPU drivers will be available for Linux Kernel 6.x?
Thanks for reply.
|
|
|
|
| SMS not delivered if receiver offline at sending time |
|
Posted by: alpineduck - 05-03-2023, 05:48 PM - Forum: General Discussion on PinePhone
- Replies (14)
|
 |
Hello,
I've been using the PinePhone regularly for about half a year. Calls and SMS have been reliable, with the notable exception of the following problem that I would like to understand, and hopefully solve:
If I send a SMS to a phone that's offline, the expected behaviour of any SMS service is that the message is temporarily stored by the carrier, and when the receiver phone is later brought online, it gets the message delivered. For some reason, this isn't the case for the messages I send from the PinePhone. Messages are delivered properly when the receiver is online, but they never reach their destination if it was offline at the time of sending.
I tried with two different carriers and both 3G and 4G networks for each: the problem is systematic with the PinePhone, while messages are delivered properly when the same SIM card is used in another phone. The problem also persisted across various upgrades of the modem firmware, including ADSP.
When logged in to my user account on my carrier's website, I can see that the messages were successfully sent.
To me, this looks like the PinePhone sends its messages together with some kind of metadata meaning "do not attempt later delivery, instead discard the message if the receiver is unreachable". Could anyone confirm this? Can it be changed and how? I couldn't find any information on that matter and to be honest I'm quite surprised to be the first one to bring this up.
|
|
|
|
|