I was wondering if anyone did test various supported distros (latest) on PBP and how they compare against each other? Battery, IO speed, UI responsiveness, WiFi speeds, memory usage, etc

I am still waiting on my machine to arrive. Are there any good benchmarks packages could be used to test and compare?

Hi -

My PBP arrived yesterday. Out of the box everything seemed to work. Battery discharged over night (I neglected to power off PBP, so today I plugged in the AC adapter. Battery began charging, and I left it to continue charging while I stepped away. A couple hours later, I return to see the battery has stopped charging, and remains in a discharging state whether the AC adapter is connected or not. I've tried power cycling the PBP but that hasn't resolved the issue. 

I just tested connecting to a USB-C dock and can confirm that PBP does draw power via USB-C, so it appears to just be the AC adapter. Any suggestions for how better to determine whether it's a faulty adapter or a problem with the port in the PBP?

Hi,

Fitness trackers such as the Fitbit Charge 2 feature a MEMS pressure sensor/barometer such as the ST LPS35HW. This is used to count positive floor increments and thus gives an estimation of elevation climbed throughout the day.

As an I understand it the PineTime does not have a barometer/pressure sensor.

It is possible a pressure sensor/barometer could be added in future versions of the PineTime?

In addition/alternatively, it is possible to interface with an external sensor such as a barometer via e.g. I²C/SPI using the PineTime Dev Kit? i.e. Are there any pins/contacts (GPIO etc.) exposed that would enable this?

Many thanks,

Arite.

I've read that there will be one hardware switch near the SD card slot that toggles serial acces.

I cannot find anything about hardware switches (such as those found on the Pinephone) for other built-in hardware, such as the microphone and cameras.
Is this correct?

If so, would the tablet still be functional if a user decices to remove the cameras and/or microphone? Are these parts modular or soldered onto the board?

Is it the strategy of Pine to allow others to create modules for the Pinetab? Or will only Pine offer these?

So I got my PBPro today, and (like many others) it had all of the kill switches enabled.

I know that pressing the kill-switch combo does something, but I have no idea how it works.  Is it some fancy ACPI magic? A special kernel module?

The most pressing question I have is: how can I tell if a particular kill-switch is currently active or not?

At the beginning of this year (2020), I read an article called Doing Things That Scale. This article put a lot of things into perspective for me.  Also related here is Solving the wrong problem.  (In fact, the author of Solving the Wrong Problem has a LOT of good articles; I recommend reading through his archives.)

These all seem like little things, but little things add up. They confuse and mislead people, causing them to make mistakes and waste their time and others'. And in a website, that wasted time is multiplied by multiple people, because rarely does a poor UI design choice affect just one person.

A Complete Waste of Space

This site makes terrible use of available space. Here's a (marked-up) screenshot of what I see what I click the "rules" link:



Here are some numbers for you:

NOTE: All of these numbers are 25% larger than nominal due to screen scaling, because I'm looking at this site on a 15.6" screen at 1920x1080.

• The actual display area for the page itself is 941px high (there's also 89px above for the tab list + address bar, and 50px below for my taskbar.)
  
  
• 274px of that height -- nearly 30% of the available screen space, and an excess of half a million pixels -- is space that communicates only one thing: That the website I'm on is related to PINE64.  It doesn't even communicate that this is the forums.
  
  
•  The actual useful information -- the word PINE64 -- is only 35px high, one eighth of this section.
  
  
• At 83px, the pinecone logo is over twice the size of the name. (Also, it's got a Raspberry Pi in its background, so it has poor contrast, especially at the top.)
  
  
• Next comes a 208px-high section.  That's over 20% of the available screen space.  That's right, we've now used up more than 50% of the available screen space.
  
  It gets better, though: this part can't be scrolled past.  This entire region is forced to be displayed on the screen at all times.  Therefore, at any given time, more than one fifth of the available screen space has been spent on this section.
  
  (EVEN BETTER: I discovered that this region interferes with the post editor under some circumstances. More on this later.)
  
  
• The blue area is 80px high, the black area is 40px high, the light-grey area is 48px high.
  
  
• Below that is 48px of blank space (I got tired of drawing arrows)
  
  
• Below that, the blue breadcrumb box (which has an inexplicable 1-pixel-thick green border) is 63px high.
  
  
• Then there's another 42px of blank space
  
  
• And a 43px "Thread Closed" indicator
  
  
• And finally a 70px thread title, before the rules start.
  
  
• Oh, I'm sorry, no.  Below that is 184px of mostly blank space.  At least I know a lot about the person who posted the rules.  And the date the rules were last updated.  Oh, wait, no I don't, that's when he joined.
  

• Get rid of the enormous image at the top.  Yes, it's very pretty, but it communicates no useful information.  Instantly reclaim nearly one third of the available display space!
  
  
• Drop the word "View" from "View New Posts" and "View Today's Posts".  That's implicit.  (The blue bar doesn't say "View Main Website" "View Rules" "View Getting Started" "View Wiki" "View News Blog" "View Help")
  
  
• Drop the word "Open" from "Open Buddy List".  Better yet, gather some statistics; find out how many people use this "Buddy List" feature at all.  It might be worth banishing to the submenu that pops up when you click your name.
  
  
• Drop the "User CP" link.  You can already access it from the dropdown menu when you click on your username in the black region.
  
  
• Drop the explicit "Private Messages". Or abbreviate it to "PM".
  
  
• Now the total horizontal space occupied by the blue, black, and grey areas is less than the total screen width.  They can thus be placed side-by-side.
  
  At this point, you should be able to fit the entire header region into 64px at the top of the screen.
  
  
• Eliminate the 38px of vertical padding in the "content" div
  
  
• The breadcrumb trail can be merged into the topic heading.
  
     (Also, I have no idea what that dropdown triangle next to the second "General" does.  It just displays a list of numbers.)
  
  
• The "Thread Closed" box can be moved down into the topic header.
  
  
• Also, it has much more padding than is needed.
  
     And it can be given a negative margin so the internal padding can overlaps with the padding of its containing box.
  
  (I've noticed a lot of poorly chosen margin/padding settings in the stylesheet.)
  
  
• That gravatar is 120x120 (150x150 with DPI scaling.) It's enormous and it doesn't need to be.
  
  
• Get rid of the useless padding around the author's name, description, and Yelp rating
  
  
• Cut the line spacing on the stats box from 1.4x to 1.1x, and put a negative margin so its internal padding overlaps the padding of the containing box.
  
  
• Get rid of the &nbsp; floats and the <br>
  
  
• Put a 4px margin-top on the main HTML table since we just deleted all the spacing in the last step
  
  

Hi, done a quick search but found nothing,
Installed the tor browser earlier and i get the error
"tor browser requires a cpu with SSE2 support, exiting"

Just wondered what the workaround is at the moment? if at all.
running manjaro at the moment like everyone else.

Any ideas would be good,
Thanks

Does anybody know a way to change the resolution from the default 1920x1080 to something like 1366x768? The KDE display manager only has the 1920x1080 option in the scroll bar.

I am using Manjaro and a few days ago updated u-boot to latest version. The instructions from pacman included some `dd` commands to run post install, and after running them and rebooting the machine I was no longer able to boot back up. Black screen, so I can't see any error message.

Did I brick my device? is it possible for me to fix it in any way other than full re-install of the OS?

Do I need to connect it to UART maybe to see what the error message is?

Thanks!