I had recently purchased the dev kit package for the PineTime watch (one unsealed, one sealed) and have been having a lot of fun playing around with it. It's a new area for me and I've definitely learned a good deal from it!
With that being said, I want to stress that I'm by no means an expert with things like Bluetooth. I understand how it works and how to interact with it via code, but I couldn't tell you all the truly intricate details of it.
For reference, any tests or scenarios I mention below are using InfiniTime 1.6 with a custom app I had put on it to act as a simple remote control. I based the structure of the app off of the Music app's play/pause button implementation since that was essentially what I needed, just for a different use case that connects to my PC. It has been working perfectly fine and doing exactly what I expected in terms of functionality.
However, the one issue I've had is in regards to the Bluetooth cutting out more than I would've expected it to. There are times where I'm in direct line-of-sight of the adapter for my PC, standing approximately 12 - 15 or so feet from it, and it would start to get more latency and then typically disconnect. It would then reconnect intermittently until I got closer to the adapter, at which point it would be fine again. This would also happen if I was right below the adapter in my kitchen (maybe 7 or so feet, with only a few 2x4s separating the top of the kitchen from the floor above).
So, I tried the following to diagnose it:
Connected to my phone instead of the PC adapter. Had the same results
Tried a different PC adapter. Same results
Tried using both the sealed and unsealed watches in the same situations described above. Had the same results for both in all cases
At this point I wasn't too sure what to think. I know that the connectivity varies on every device and some devices just have shorter ranges, so maybe that was just a limitation. Then, for some reason (I don't really even remember why I thought this), I figured "I've been wearing the watch in all these tests. What if I just hold it by the strap?"
I walked over to one of the places that I had these issues at and held the watch by the strap, and noted that there was barely - if any - latency. I moved my hand around holding the watch (lifting it up, moving it down, further away, closer, etc); still no issues. I figured this may just be a lucky fluke, so I tried other places I had issues at and to my surprise, still had no problems.
To see if I had finally lost my mind, I took the other watch and tried the same tests. I had the same results when holding it from the strap: no notable issues.Then, I took the watch, and laid it over my arm (didn't strap it on, just laid it down), and suddenly the connection died off.
I repeated the above experiment several times, with both watches, and every time I had the same results. Whenever I put the watch on my wrist, the connectivity would be cut off to a pretty extreme amount. I know that Bluetooth can't travel through water, and given that we're just walking, talking water sacs, it does add up that my body blocking the watch would reduce signal.
As another experiment, I bent the end of the Bluetooth antenna in my dev watch upwards a bit so that it was more vertical inside the case. My main reasoning was (rather simply) that antennas typically seem to point vertically from their base, so I have nothing to lose by trying that here. To my surprise, this actually seemed to reduce the issues I had while wearing the watch by a significant amount; not a complete fix, but certainly much better. Conversely, the sealed watch still had issues where the dev watch no longer did.
So with all that out of the way, my main questions:
Is wearing the watch supposed to affect connectivity? Like I said above, I understand that our bodies block signal, but it seems kind of bizarre that wearing the watch - one of the main functions of it - would decrease connectivity by such a noticeable amount, no?
Does it really make sense that my slight bending of the antenna would've increased performance to such a noticeable degree?
Is there just something else here that I'm overlooking, or other factors that are just making this a red herring?
I also apologize if this is the wrong sub-forum. I figured since after all my tests it seemed hardware related, I would ask here.
All expected things were working fine with pinephone. A pacman update borked my pinephone and it wouldn't boot. I installed fresh current img to phone main memory (not sd card) as below:.
"Manjaro-ARM-plasma-mobile-pinephone-20111108.img.xz". Install was uneventful. I did a pacman system update after the flash install that added some items.
I use a Consumer Cellular sim card. Worked fine in past 6 months.
Testing of the new install shows that I can text outward, receive texts inward. Incoming voice calls are received.
Outbound calls, however, do not work. PhoneBook and Phone app both say " Unable to make a call at this moment". But this has been hours and is not a temporary Consumer Cellular system problem as I have an android phone working with the same carrier.
My sim card data shows in Settings -> Cellular Networks -> Sim card and data looks right.
Never had a phone problem (lots of others) before. Any ideas, anyone?
I may reinstall the older img file where all was working if I can't get a fix going to see if something got gliched in update.
after writing this I realised that the introduction is quite long; for the actual question you can hop to the last paragraph.
I naively used ssh to connect my phone to the computer, until I recently found out that this is apparently very insecure.
So now I am trying to harden the system by
-excluding IPv6 adresses (done)
-changing the port (yet to be done)
-using a key instead of a password (yet to be done; there's a brief manual in the wiki, but I could not do it, so I will have to look for more foolproof resources)
-installing fail2ban
After installing fail2ban (which is supposed to block IP adresses which fail to enter a correct password for more than x times) I noticed that it did not work: I could enter as many wrong passwords as I pleased and still log in. I finally found out that the reason was that the file /var/log/auth.log was missing and that I could solve the problem by installing rsyslog.
Was it a bad idea to install rsyslog? I'm asking because I guess that the devs had a reason to leave it out. Could it maybe drain the battery, quickly use up a lot of disk space or do anyting else that would be undesired on a pinephone?
I've been doing searching on this forum, and I haven't found many good answers. One or two threads closed, some others not really answering. Here's my question:
PineBook Pro -> USB C adapter -> HDMI -> LG 43Un700-B
Resolution at 1920x1080 is supported on the external LG monitor
Problem: The monitor itself frequently suggests that I switch to 3840x2160
Question: Is this theoretically possible with PBP?
Datum: When I attempt this, I get a KDE error "Outputs could not be saved due to error"
USB C to HDMI adapter:
CableCreation 5-in-1 USB C Adapter with 4K HDMI
Log file snippet:
[ 17.761] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 4107.965] (--) modeset(0): HDMI max TMDS frequency 300000KHz
[ 35899.567] (II) modeset(0): Allocate new frame buffer 3840x1080 stride
[ 35899.701] (EE) event0 - HAILUCK CO.,LTD USB KEYBOARD: client bug: event processing lagging behind by 138ms, your system is too slo
w
[ 35925.629] (EE) client bug: timer event8 debounce: scheduled expiry is in the past (-14ms), your system is too slow
[ 35925.629] (EE) client bug: timer event8 debounce short: scheduled expiry is in the past (-27ms), your system is too slow
[
I'm selling my Pinetab which I bought with the backlit keyboard , its an brilliant device from pine64 , but unfortunately I haven't been able to give it the proper attention it deserves. I had hoped to contribute back to the project, but life has taken an alternative direction and I find myself getting busier and busier .
I would prefer to sell in the UK only, so if your interested please DM me .
I'm looking for £100 +postage (but I'm sure an offer can be made) for it as its barely been used.
I have just received my pinecil but I can't get it to work - I get an X !! on the screen (not sure if the photo is viewable here) - I am using an OMARS power pack with 45W PD capability.
thanks,
PrimeOS is originally an Android-x86 based OS that provide desktop like experience on x86 based devices with top of the line features like Multi-Window, taskbar and Deca-pro Key mapping tool for playing games. Few weeks ago we received our Pinebook 1080p unit and started our work to port PrimeOS 0.5.0 to Pinebook.
Feature Highlights:
Multiple features to give a desktop experience like start menu, taskbar, etc.
Multi-window support with maximize, minimize, close, resize, etc.
Option to disable multi-window for any app in case you need.
General keyboard shortcuts like alt + tab, alt + f4, win + d etc.
Close to AOSP experience with only necessary desktop features.
Taskbar with the ability to pin apps, show notifications, and system icons.
Decapro key mapping tool to play games with keyboard and mouse (Press F10).
Built in Google apps.
INSTALLATION STEPS:
Download the PrimeOS SD-card image from our FORUM.
Insert sdcard into a card reader and flash the image using Etcher.
Put the sdcard into Pinebook and boot up.
Note: You will need a very good SD Card with atleast 8GB of space to have the best experience.
KNOWN BUGS:
Colors in camera is not good.
Chrome Browser crashes.
! WE HAVE ONLY TESTED THIS IMAGE ON THE 1080P PINEBOOK !
! Report to us if you find any more bugs !
PrimeOS for Pinebook is based on LineageOS 14.1 and it wouldn't have been possible without the work Ayufan and Alexandre(/e/) and we would like to thank them for their valuable work.
Please do not mirror without permission.
Consider donating on Ko-Fi to us to keep this awesome project up and running.
Hello, I bought last week a pinetime, I got a confirmation email but no info about when it will be shipped. i would like at least an aproiximate idea, like next month, 6 months...