| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,701
» Latest member: Stunnned
» Forum threads: 16,260
» Forum posts: 117,189
Full Statistics
|
| Latest Threads |
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: Stunnned
6 hours ago
» Replies: 2
» Views: 162
|
Volumio (PINE A64-LTS / S...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: kapqa
Yesterday, 02:02 AM
» Replies: 8
» Views: 15,541
|
Reinstallation Arch Linux...
Forum: General Discussion on PineTab
Last Post: rth
11-22-2025, 08:25 PM
» Replies: 1
» Views: 217
|
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: brb78
11-20-2025, 04:15 PM
» Replies: 0
» Views: 122
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
11-20-2025, 09:04 AM
» Replies: 5
» Views: 618
|
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 184
|
How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 482
|
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,184
|
Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
11-18-2025, 12:48 AM
» Replies: 0
» Views: 110
|
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
11-17-2025, 07:49 AM
» Replies: 0
» Views: 106
|
|
|
| Luajit in the AUR, loss of aarch64 support |
|
Posted by: tophneal - 02-12-2020, 12:25 PM - Forum: Linux on Pinebook Pro
- No Replies
|
 |
Recently (yesterday) an update for luajit went to the AUR which dropped support for aarch64 (in some way or another.) This has been keeping people from being able to install GIMP. For anyone using Manjaro/Arch, I've uploaded the pkg of luajit-git that I have on my system from late December 2019. Install it before trying GIMP, and your GIMP install should be good. Just remember to ignore luajit-git's request to update (it won't update, it'll just stand in the way of other updates.)
[link removed]
I'll leave this up until aarch64 is back in luajit.
An option for luajit-git has been added to Manjaro community, that will now install.
|
|
|
|
| my pinephone battery is dead :/ |
|
Posted by: emptyfortress - 02-12-2020, 11:17 AM - Forum: PinePhone Hardware
- Replies (7)
|
 |
Pretty much what the title said, dead as in 0v on the multimeter
what happened was I was testing Ubuntu Touch, had the bug where the wifi drops and can't be raised again. I didn't know yet you could turn the chip off and on again by hand so I shut the phone down (via the UT power button menu IIRC), the battery was over 90% charged according to the charge UI. That was a few days ago, when I picked the phone again yesterday, oops
Not sure it's relevant but I should also mention that when I first got the pinephone it wouldn't recognize the battery (it booted fine when hooked to a charger), I have since read people mentioning having problem with adhesive residue on the pins or the battery being wrongly sitted so I assume that's what happened (it resolved itself after a few sd card swaps, I imagine I ended up putting the battery in the correct position).
could it be the wifi chip not being shutdown properly that drained the battery flat despite the phone being off?
question number 2, shouldn't this have triggered some sort of overdischarge protection circuitry?
|
|
|
|
| Texting works (But...) |
|
Posted by: Zweitaktmotor - 02-12-2020, 06:21 AM - Forum: PostmarketOS on PinePhone
- Replies (7)
|
|
As indicated in the notes for the latest build, I am able to receive texts and reply to them.
However, I am not able to initiate a new chat. neither a number typed in manually nort one taken from the Contacts list is recognised.
Still, quite happy that we have a useful function now (other, such as the camera bor sound recorder are still merely placeholders).
|
|
|
|
| wasp-bootloader: a robust SoftDevice bootloader for PineTime |
|
Posted by: danielt - 02-12-2020, 04:58 AM - Forum: Development Discussion on PineTime
- Replies (3)
|
 |
I got chatting on pinetime IRC channel (and the many bridged rooms using other protocols) yesterday evening and the discussion swung round to bootloaders... as I think all PineTime chats must eventually do ;-). So... having been encouraged to discuss the bootloader separately from the MicroPython stuff in the other thread let me summarize what I've been doing.
The very first thing I did when I got my PineTime was extend an existing bootloader to allow me to develop without relying on SWD. In other words I wanted my watch to be capable of BLE OTA updates *and* robust enough that it was difficult (although not impossible) for a broken application to lock me out of my watch.
https://github.com/daniel-thompson/wasp-bootloader
This is derived from the Adafruit nRF52 bootloader used on some of their feather boards.
The main changes are:
- It uses the PineTime display rather than LEDs to share status with the user
- It shows a nice pine logo as a splash screen ;-)
- It preconfigures the watchdog timer with a fairly generous (5 second) timeout
- It automatically enters OTA DFU mode on a watchdog reset
It is designed to pair with a special WDT feeding routine in the application. In C-ish pseudo-code it would look like the below. Note that writing button_tamper_check_ok() is a work-in-progress. It is very hard to tamper check on an nRF52 because the pin control is decentralized; we have to tour most of the peripherals and check it hasn't tried to "steal" pin 13 or pin 15 (for now I have just been careful when writing code to activate a new peripheral):
Code: void feed_wdt(void) {
if (button_tamper_check_ok() && !button_pressed())
nrf_wdt_reload_request_set(0);
}
The recommendation is to setup a periodic interrupt (for a 5 second timeout this needs to be roughly every second) in the application and feed the watchdog from it. Normally it is not a great idea to feed a WDT exclusively from an interrupt (unless it implements a soft watchdog) but because the button press can be used to inhibit the feeding of the watchdog then this essentially implements a long-press reset instead of a traditional watchdog.
The bootloader should work well for any SoftDevice based application providing the version numbers align (currently using S132 6.1.1). In principle it can also support other applications but the SoftDevice uses so much FLASH I think it would not be very practical. Various people on the chat caught me up on the discussions at FOSDEM and a bootloader needs to get a lot more sophisticated if we are to support OTA updates where the payload can use an "arbitrary" BLE stack.
However if you are already using SoftDevice this bootloader should work well... to use it all you have to do is relink you application with the flash size set 24K shorter.
At present the only missing robustness feature (that I have thought off) is providing deep sleep support. At present it is easy for an application to enter deep sleep without setting up a suitable wake up source. If that happens the WDT gets disabled and, worse, the system will use so little power that I suspect it could take over a month for battery to run out and make it possible to reboot the watch. Note that I don't think it is practical to prevent the app from sleeping but we can provide a bootloader service to set up a deep sleep in a safe and well tested way so the application can use that instead.
[Use this direct link if the forum video embedding doesn't work for you: https://www.youtube.com/watch?v=W0CmqOnl4jk ]
|
|
|
|
| Request for a favor |
|
Posted by: as400 - 02-12-2020, 12:44 AM - Forum: Pinebook Pro Hardware and Accessories
- Replies (2)
|
 |
I'm trying to come up with some idea of better cooling for pbp.
For this I need some measurments. I know that the CPU itself is 20x20mm. But I need the exact measurment for this bulge which is on CPU.
So if you have your pbp open or planning to open it - please measure the bulge for me 
Thanks in advance.
|
|
|
|
|
