Hi,

any idea when would the Clusterboard be back in stock?

Thanks.

Hi

I am flashed the SPI with sigmaris's SPI, and I was unable to boot. So I used the erase image, and it still wouldn't boot. I'm expected my uart today, so I can view whats' going on.

However, I was wondering why it was letting me ping but not ssh. I have imaged a sata ssd with TwisterOS, and also on an sdcard, and neither boots. I think the SPI was flashed correctly (i'm probably wrong) so I am unsure why nothing is booting.

Earlier I was unable to ping at all, until I went through flashing again. So I probably skipped a step I imagine and now I've maybe bricked the rp64?

Thanks for any guidance

Fortunately I have a 2nd rp64, so I am hoping I waiting on this before I go through the hell of it again with the 2nd one

I put bad apple on the pinetime.

You can also watch it on odysee:
https://odysee.com/@TT-392:b/bad-apple-pinetime:8

Source code:
https://github.com/TT-392/pinetime-bad-apple
https://github.com/TT-392/Pinetime-bad-a...-processor

Greetings,

Would it be smart to isolate one or two of the cpus to be dedicated to a stable core functionality like receiving calls and the user interface? Has anyone tried?
I hope to achieve the following: A somewhat poorer performance for some multithreaded task but a rock-solid performance for some basic well-tested tasks that rarely misbehave (likely including htop to kill any misbehaving apps). This way one shouldn't worry about missing calls or having to reboot the phone when launching anbox or a poorly written website in firefox. Of course this wouldn't solve all problems, e.g. a misbehaving gps app could spam the modem so much that calls can't come thru. 
I imagine this could be done using something like taskset, isolcpus and cpusets, but I have absolutely no experience messing with this functionality. Is this already build-in (in a much smarter way) in some of the distros? 

Cheers

Hi folks. I've been Pinephoning since late 2020 and am pleased with the current stable release of Manjaro ARM w/ Phosh. I now consider this a reliable and practical daily driver and that wasn't the case in November of 2020.

One function of the Pinephone I'm yet to get full use from is the camera. Firstly, a bug report.

I have noticed that if by dipswitch setting, the user-facing camera is disabled, but the back camera is enabled, Megapixels stalls and fails to open. If both cameras are enabled by dipswitch, Megapixels opens and functions perfectly. I'm yet to try the reverse combination.

Also, has anyone successfully shot video using the camera on the Pinephone? If Megapixels allows for that, I haven't figured out how to switch from photo to video recording. Is there another video recording program anyone can recommend?

Thanks in advance. 

Hi there,
as my Pinephone mostly resides in the drawer and I'm not a dev, I thought it could serve a better purpose in the hands of someone else ;-)

Its the UBPorts Community edition, upgraded too the 3GB mainboard. Its in as-new condition, never left the house, actually never left my desk, I changed the UBPorts back cover in day one to a neutral one - so that's in new and unused condition - and it comes together with the original 2GB mainboard - so two boards included.

I used it just for keeping an eye on the progress of the different distros and it was fun playing around during boring lockdown days, but as I now had to return to normal office days I haven used the phone for weeks and so decided to sell it.

I don't want ridiculous money for it - would rathe prefer it gets in the hands of someone who brings UBPorts forward on this platform

I paid about £230 incl shipping for all (phone, 3GB mainboard, ...) so I'd dare to ask for £100 for the Pinephone with 3GB mainboard,  two back covers, protective silicone cover, and the original 2GB mainboard - both boards are flashed with UBPorts with free shipping in the UK - international shipping possible but you have to care and pay for taxes, shipping, fees, ... even to the EU it got quite complicated and expansive now after Brexit..

ask me for pics - viewing and pickup in person possible in Bristol UK

If interested send me a PM

Cheers,
Martin

recently I found Pure Maps does not work in Postmarket Plasma or in Postmarket sxmo. Are there any well working map / nav apps to be used in PostmarketOS?

I collected some bma421 driver from other project, only could read chip id but is not work

If write config file during initialization, error -5 encontered
If not write config file during initialization, no data from bma421

pinetime: zephyr based PineTime (gitee.com)  in [b]app[/b] /[b]drivers[/b] / [b]bma421[/b] / [b]zephyr[/b]

So I thought I would try out wasp-os on my pinetime. It was running the infinitime 1.0 bootloader and 1.2/1.3 OS.

I downloaded and unzipped the wasp-os-0.4.1 file from https://github.com/daniel-thompson/wasp-os/releases. I used nrfconnect to push the reloader-mcuboot.zip file from the build-pinetime folder to the pinetime. (I watched Daniel's YouTube video from November 2020 & followed the steps he outlined)

The watch rebooted and the pinecone changed from blue to white.

I reconnected nrfconnect with the pinetime and attempted to push the micropython.zip file to the pinetime, but it would get to 1% the watch would blink the pinecone is white with start and a white bluetooth symbol. I can reconnect (most of the time the phone & pinetime automatically connect), but I can't get past 1% and the cycle continues.

So I thought I would go back to infinitime by pushing the reloader-factory.zip, but the same thing happens - bluetooth disconnect, white pinecone, start-whitepinecone-whitebluetooth, whitepinecone-bluebluetooth.

How do I get my pinetime back?

Thanks.

Mark

Hi to all,

I've started to use PineTime for about 3weeks ago - I've bought dev-kit. Last week I've upgraded firmware to version 1.3 of InfiniTime. After firmware upgrade I've verified and it looked fine. Everything was working fine, until battery was completely discharged. I've used the same charger as before but watch doesn't seem to be starting. It's completely blank. Doesn't matter for how long I push the button nothing happens. I've tried second charger from the dev-kit, still no results. Any ideas what more I can do?
For firmware installation I've used nRF Connect from Play Store. As a companion app Gadgetbridge from F-Droid.