Just copied the latest image to my SD card and it booted up well.

However, be careful with the brightness control. ,If you move the slider completely to the left, the screen will go black and you cannot bring the brightness back up.

Fortunately, a reboot helps, but perhaps the developers should know this and adjust the minimum setting only to a very, very dim brightness.

There seems to be no app to do it under phosh. 

I tried date from the terminal but I got EPERM. Date said: 'date: can't set date: Operation not permitted.

After the first hour or so of playing w/ different OS images, the exposed RF-shield (under the battery cover) gets quite hot. I'm was pretty sure this shield only covered the EG25, so flipped the modem kill-switch to off. It's still getting quite hot... so I've got two questions (one of which I can probably answer from the schematics):

1) Does the RF-shield act as a heat-sink for both the modem *and* the SOC?
2) What does the modem kill-switch actually do to the modem? Place in reset? Physically remove power?

EDIT: Took a me a bit to realize that the symbol for the killswitches is split through-out. SW1-A is the 2-pins for the modem kill-switch, and looks like it is intended to cut power at the Q1500 power mosfet. Has anyone confirmed that the EG25 does not draw unwanted power when disabled?

Would anyone be interested in porting Tizen OS to the PinePhone? ( Samsung has sold some Z phones with it).  Tizen also runs Samsung TV's and Samsung Galaxy Watch Active 2 (with LTE).


Proting Guide: https://wiki.tizen.org/Tizen_3.0_Porting_Guide

Source Code: https://source.tizen.org/

Developer site: https://developer.tizen.org/

Main: https://www.tizen.org/

I downloaded ubports from here: https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ (Chose .img.gz under "Latest Successful")

Extracted to default .img file

put on sd card using:

My pinephone arrived today but as far as I can tell the touchscreen is not working.  It boots to the factory test screen but none of the buttons respond to my taps.  I don't have a large enough microSD card here at work to try another OS, but I'm assuming if it doesn't work with the test image, I won't have much luck with anything else either.

(02-11-2020, 12:59 PM)ksbex Wrote: My pinephone arrived today but as far as I can tell the touchscreen is not working.  It boots to the factory test screen but none of the buttons respond to my taps.  I don't have a large enough microSD card here at work to try another OS, but I'm assuming if it doesn't work with the test image, I won't have much luck with anything else either.

Hey everybody, 

I have the pinebook pro with the standard os that ships with it. 

I have a strange problem. when I am at home, I can stay connected to wifi without really noticing any issues. 

At work, I connect to Eduroam (https://en.wikipedia.org/wiki/Eduroam) and it works just fine for a few minutes. But then it starts to drop the connection -- sometimes it shows up as connected but  is actually not. I can then reconnect but keep having trouble until I reboot the machine. 


I went through the suggestions on the pinebook pro wiki (https://wiki.pine64.org/index.php/Pinebo...iFi_issues) but nothing worked so far. 

Has anyone else experience this problem? 
Does anyone connect to Eduroam without any problem ?

Edit:
Have been at a different institute today and had no issues with Eduroam at all. So it seems to be a local issue.

Update:
Switched to Manjaro: Wifi issues with eduroam are still there. However, it seems to work fine when using a wifi-dongle.

Hi!

I'm researching and developing hardware for Virgo.  

https://virgo.org/about/

Our end-goal hardware-wise is an open source mobile phone, and I wanted to follow up with you guys about the PinePhone.  

I'm curious if any of the hardware on the PinePhone is open source?  

For example, the PCB design, case, display, or anything else for that matter.


Thanks!

-Jacob 

PS: I really love the idea of phone as dev platform for mobile Linux, and I plan to pick up a PinePhone as soon as the next batch is available.

If this happens to you, something to try, costs little

This fairly serious, I just spent 2-3 hours to narrow it down
So, I thought I had broke it, the power button did nothing, removed q4os SD, still nothing
For some reason, I tried holding power 15 sec, nothing, thought try longer (and 20+ is right)
Then a short push and started right up, hmm, hmm
Put q4os back in, reboot, same senario (dead power button, hold 20+s, then works (q4os out))
Tried with nothing in SD slot, worked OK, tried with debian bullseye, worked OK,
tried with manjaro, worked OK (reboot worked, after shutdown restarts normally)
Checked 1st 16M, diff and cmp they vary quite a bit,
downloaded a stock mrfixit and updated, 1st 16 match (aside from mbr) (with emmc)
So q4os has some problem with uboot? or ibdloader?
I never did get q4os booted
why the 20 second push????
--edit-- SOLVED
turned out to be wrong card, identical (appearance) card hiding nearby
I wish there was a way to mark cards, that doesn't rub off or gum up SD slot

I installed postmarkOS on an SDcard.

First issue, probably a bug with postmarkOS.

When you first boot it does not bring up the password screen. However, after some minutes of inactivity, it brings up the time/date display and then you need to enter the password.

Where should I submit bug reports?

If I can figure it out I will submit a patch.