Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,485
» Latest member: mintab
» Forum threads: 16,198
» Forum posts: 116,884

Full Statistics

Latest Threads
Giving away a Pinebook Pr...
Forum: Pinebook Hardware and Accessories
Last Post: alchemist
7 hours ago
» Replies: 1
» Views: 47
Armbian images available
Forum: Linux on RockPro64
Last Post: Shraunfnq
Yesterday, 10:16 AM
» Replies: 61
» Views: 114,490
Bare metal on Pinephone P...
Forum: PinePhone Pro Software
Last Post: alain
08-19-2025, 07:58 AM
» Replies: 0
» Views: 118
Seeking Contributors: Apa...
Forum: PinePhone Pro Software
Last Post: geometrylitegame12
08-19-2025, 01:38 AM
» Replies: 4
» Views: 4,022
Pinephone Pro wont boot t...
Forum: General Discussion of PinePhone Pro
Last Post: KC9UDX
08-18-2025, 06:15 PM
» Replies: 5
» Views: 320
PinePhone Pro discontinue...
Forum: General Discussion of PinePhone Pro
Last Post: Kevin Kofler
08-18-2025, 04:30 PM
» Replies: 8
» Views: 620
fixing the ppkb mainboard...
Forum: PinePhone Pro Accessories
Last Post: Jite
08-18-2025, 02:57 PM
» Replies: 2
» Views: 164
Are there plannes to crea...
Forum: PinePhone Pro Hardware
Last Post: biketool
08-18-2025, 04:12 AM
» Replies: 5
» Views: 1,037
Pinephone pro stuck while...
Forum: PinePhone Pro Hardware
Last Post: Supervisor
08-16-2025, 06:40 PM
» Replies: 2
» Views: 214
Compatible U.S. carriers ...
Forum: General Discussion on PinePhone
Last Post: Zebulon Walton
08-15-2025, 07:34 PM
» Replies: 2
» Views: 262

 
  Is it normal for the pinephone to "discharge" after fully charged on multiple OS?
Posted by: Shad190 - 05-10-2023, 05:12 AM - Forum: General Discussion on PinePhone - Replies (2)

I got a pinephone a few days ago and admittedly I haven't had many phones but this is something I've never encountered before. I've tried numerous OS and every single one has this problem. I've searched and couldn't find anything about how normal it is for a pinephone. If I unplug and plug the charger back in it will start charging again until it is full and the cycle repeats, I'm not sure how far until it starts charging again if it ever does but I've let it get as low as 70%. The fact that I have to unplug and plug the charger back in is also a bit concerning. On the OS it ships with (at least after I manually reinstalled it, I didn't check it as it came shipped), manjaro with plasma mobile it says health is 0% and the battery is unknown.


  New Pinephone is dead. eMMC, boot, hardware issues.
Posted by: Shane - 05-09-2023, 05:38 PM - Forum: General Discussion on PinePhone - Replies (4)

Brand new PinePhone received today (not pro.)
Would not boot out of the box. Stopped at KDE logo.
I wrote image to SDCard and booted the phone from it. No problem.
Once in the Pinephone I DD'd the same image to the emmc. It completed but when I rebooted, it was stuck in a boot loop. (Turn on, vibrate, turn off.)
I booted from the SDCard again and no problem.
Another flash to the emmc and the phone shutdown at some point. It was plugged into power and charging.
I then booted it again and tried to flash again. It crashed at a different point.

Now it won't turn on at all. It is black and has zero lights or response.
- On battery alone
- On battery + power
- On power alone

I think I destroyed my new Pinephone in less than an hour. 


  Country of manufacturing
Posted by: turmelus1 - 05-09-2023, 02:44 AM - Forum: General Discussion on PineTime - Replies (2)

I'm thinking about getting a pinetime but I'm wonderimg where they are made? Amazfit is a bit uncomfortable for me as it is a chinese company and I would also like to avoid anything made in China. Though amazfit gtr2 is a bit more tempting with having a mic and speakers. Is there any change there will be a pinetime 2 with mic/speaker/nfc in a near future?


Bug "bricked" my eMMC
Posted by: tigerbalm69 - 05-08-2023, 11:03 PM - Forum: PinePhone Pro Software - Replies (4)

Had many issues with the original Manjaro OS on my pppro, such as pgp keys not properly authenticating etc. after some long troubleshooting I decided to install a fresh image to my eMMC from an SDcard. During the flashing of the eMMC, the phone crashed, and the flashing was interrupted.
Now whenever I boot, it is IMPOSSIBLE to boot from SD card without bypassing eMMC with the RE button (I used to have tow-boot, which allowed me to use the volume down key and this no longer works) No matter my timing I never seem to be able to boot with the eMMC initialized. It never shows up in "lsblk" and therefore I cannot re-flash the drive to a complete install.

Quick note about tow-boot: it does seem to still exist as I get a brief blue flash before some kind of (what seems to be a) hard override of my input

I ran the dd command as per usual when the phone breaking crash happened, nothing fancy.

Anything I can do to access the eMMC from my computer?
Can I use a USB-C keyboard to boot the phone from SDcard? (I don't have one at my disposal so I haven't had the chance to try)
Any other ideas? Huh Huh Huh 

Thanks in advance to anyone with the knowledge to help me out of this mess


  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 RTOShttps://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 Smile


  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]

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.