HI,

I've flashed SFOS on my BH Pinephone yesterday, using the flash-it.sh script as instructed by the PinePhone Software Releases page on the wiki. I'm really impressed with how snappy and smooth this OS runs on the pinephone.

The device boots into the lockscreen, and from there I can edge swipe down or op, opening the settings or the camera. Swiping from the left or from the right, however, has no effect, and as such I am unable to move the lockscreen and start using the rest of the OS.

I know there's nothing wrong with my screen. as when the config is slider is down, I can close it by swiping from the left or the right. I've also never had any touchscreen problems with Manjaro.

Has anyone else had this issue? Is there anything that can be done about it?

Thanks!

I don't know if it is feasible,   but instead of going through the carrier,  could we have an app that allows our phone to answer when

we choose to let the call go to voicemail....  ?

If we are out of cell range, or our phone is turned off it  'could'  still go to the carriers servers....

or if you are like me, I just do not set up voicemail on the carriers servers.

 *  But cutting out the middleman sounds good to me.

I wonder if there is a way to go sans stock battery? Not to replace the battery with a compatible alternative but to modify the phone to complement a different type of system. New to the forum, haven't really perused the place BUT-- I find it interesting that when I plug the phone to, say, a computer without a battery (though I assume off an external battery it may act similarly) two things happen:

a. It's lighter, duh. But instantly lighter in a way that is oddly exciting to me?
b. It's faster. Not that I've measured it...

I'm assuming the apps run smoother because the, as I humbly perceive, power-hungry modem necessitates the battery, and so no modem to compete with the CPU, RAM, etc. (at least using postmarketOS with sxmo). However, from reading another post on power management in /sys, the USB power settings could potentially be tweaked to power the modem? And if so, we could technically use whatever battery we want, so long as we can find a way to mount it to our bodies in a totally natural, cyborg way. jk, but no, I'm serious.

I do not understand why the board, cpu, the screen, everything gets power except the modem? To which, with space regained used once by the battery one could hypothetically mod peripherals where the battery currently lay?

But seriously, if I could get my unit to be this light and this fast and do cellular (with totally cool wrist straps that contain batteries, think about it) the phone would be instantly more usable as a daily driver and rather unique to boot.

So, my grand OP question is: can the pinephone modem be charged off an external source via USB without modding the battery pins with a dummy?

At the very least, if the setup could work with just the charge from the dock, the pinephone could be used as a neat terminal with lower latency much like that raspberry 4 keyboard, if of course, you mount keys to it (in the gap where the battery no longer needs to exist.) External battery power would make the lifetime of the thing effectively endless.

tldr: USB power without the battery powers the phone's components except for the modem. Why come and how to innovate?

Hello community, does anyone know whether they will be selling the Pinebook Pro with custom specs in the future? Like more memory or disk capacity.

Does anyone know how to make an external display work in TwisterOS (which is based on Armbian)? The external display works in Manjaro, but not TwisterOS. Here is the only offending line I could find in dmesg:

[  10.658203] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] *ERROR* Enable dp failed -19

I have attached the rest of dmesg's output, in case that is useful info.

Thanks!

Attached Files

  dmesgoutput.txt (Size: 55.19 KB / Downloads: 467)

If anyone wants to try sxmo on Debian, I made a small script that should at least get the basics working. Run this script from phosh or ssh after setting up an internet connection on Mobian ( I used ...phosh-20210516.img.gz ). It's based on an existing script to install sxmo on arch. 

Numerous things still do not work. Wifi and (allmost) all on screen input (lisgd and svkbd) work without issues. OTG works, but screen hast to be set up manually. Most apps from the apps list work, but scripts that need sfeed do not. Sound doesn't really work. If you want to have sound, use pulseaudio from the terminal. Suspend doesn't work. Bluetooth is untested. The camera works, because megapixels just works. Modem is untested and most likely doesn't quite work. I want to get sound and suspend (sleep) to work next. 

I'm also not sure how long this script will continue to work, since sxmo is moving to tinydm and wayland.

FydeOS sounds really cool (and probably would be a great backup OS if something I need to use doesn't work in Linux on the PBP yet), but I would really like to read FydeOS' privacy policy to know what data it is collecting on me before trying it. I looked on their English website, but I couldn't find a privacy policy anywhere. Could someone please share a link to it?

I have created a go library and a daemon to interact with the InfiniTime firmware on Linux. These were created in about a week, so I don't know how good they are. If anyone is interested, here they are:

Daemon: https://gitea.arsenm.dev/Arsen6331/itd
Library: https://gitea.arsenm.dev/Arsen6331/infinitime

This was also posted on reddit: https://www.reddit.com/r/PINE64official/...nfinitime/

Hi,

I just got my PineTime and it's amazing!  I installed Siglo on my laptop and was able to pair and update the firmware to 1.3.

I also installed Gadgetbridge on a Motorola Ace and it doesn't see the PineTime.  I followed the Gadgetbridge configuration instructions here.

Any ideas or suggestions?

A few months back I received my ROCKPro64 (4GB, v2.1) with aluminum case, RTC coin- battery holder, and 5A power supply. Everything is assembled and looks to run okay, most of the time. Except the board experiences an intermittent problem where the power button sometimes fails to start the machine, requiring several presses before any electrical activity. Other times it works like a charm. This can happen no matter which micro SD card is inserted, or even when I try a power-on with an empty reader. The button itself looks to be mechanically sound since the operating system never fails trap a shutdown press. I've since tried several different Linux distros on verified cards with no difference. Before giving my ROCKPro64 an unplanned early retirement, I was advised to register on the forums in case this has been solved. I've gone through the search facility but the hits didn't match my problem exactly.