Hey all,
 
I just installed Manjaro Alpha2 on an SD Card on the Pinephone but once it finished installing it is asking me for a passcode but I have no idea what that could be. I was never given the opportunity to enter a username and password as it just went to the screen to enter a passcode. I tried 1234 but it fails.

Anybody have any ideas to offer?

Thank you in advance!


Solved!

It was 123456. Then I was able to get in and change it through the terminal.

Results: ubports/2020-08-20

Conclusion: This build was an improvement from the last. Still not a ready.

Notes: I got reports that this build did not function very well, but I have had a different experience. It seemed to test alright.  Let me know what your thoughts are. I will be adding 3g phone and text tests in the next few days to break out for a little more clarity.

It's been a while, and it seems like the only design files available on the wiki are still just the schematic (which has wiring information, but not mechanical layout) and the PCB silkscreens (which only give the positions of components, not tracks).

I've been scheming now and then about various hardware modifications to the device, especially using the extra internal USB lines that are available on the USB hub chip, but all of them would really benefit from being able to know where the tracks are. Would it be possible to add those copper layer design files to the wiki as well?

Dear folks,

my Pinebook won't charge any more; there doesn't seem to be anything wrong with the charger brick though. I followed the advice on this forum for battery problems but that only made things worse but I did discover that indeed its the charger circuit.

For the battery reset, i had to unplug the battery cable while the mains was on but this instantly gave a power loss to the machine so no power was arriving from the power cable and it was just running on fumes so to say of the little that was still in the battery although it showed 0% power. The situation is now that it runs on the fumes but at the same time reports there is no battery :-S

Is this charger part replaceable and what PCB is it? The USB connector on the PCB with the power plug and the SDcard is in working order so i doubt its the cabling between the PCBs. Can I order a new side PCB or do I need to replace the main PCB?

With regards,
Reinoud Zandijk

Dear folks,

my Pinebook won't charge any more; there doesn't seem to be anything wrong with the charger brick though. I followed the advice on this forum for battery problems but that only made things worse but I did discover that indeed its the charger circuit.

For the battery reset, i had to unplug the battery cable while the mains was on but this instantly gave a power loss to the machine so no power was arriving from the power cable and it was just running on fumes so to say of the little that was still in the battery although it showed 0% power. The situation is now that it runs on the fumes but at the same time reports there is no battery :-S

Is this charger part replaceable and what PCB is it? The USB connector on the PCB with the power plug and the SDcard is in working order so i doubt its the cabling between the PCBs. Can I order a new side PCB or do I need to replace the main PCB?

With regards,
Reinoud Zandijk

I miss a PineTime which is more powerful and has a Linux operating system. Shouldn t this be feasable? There are already such watches available. The Ticwatch Pro for instance has 1 GB of Ram:

https://www.amazon.de/Ticwatch-Pro-gesch...B082Y2Q1LG

and runs android wear. Linux can run on Android wear:

https://www.reddit.com/r/AndroidWear/com...roid_wear/

but what is missing is an easy to use user interface. Make a real Linux Pinetime which is more powerful. All components are available.

Does anybody in this forum use Zotero too?

I have been using Zotero on my PBP with 'zotero-arm-bin' package from AUR, but the recent kernel update broke the software.

I am not exactly familiar enough with Linux to change the contents of the package. I would appreciate any help about this issue.

When I try to start the program, I get the following error message.

-----
XPCOMGlueLoad error for file /usr/lib/zotero/libxul.so:
libstartup-notification-1.so.0: cannot open shared object file: No such file or directory
Couldn't load XPCOM.

-----

Hello all, didn't see a forum for this product, sorry if this is the wrong place.

I saw the 7" touch screen panel on the site here:
https://store.pine64.org/product/7-lcd-t...een-panel/

I recently installed a samsung tablet in the dashboard of my car but in the heat it would go into thermal shutdown mode, and the glass eventually got so hot that the glue melted and the button slid back inside the case.

Is this LCD a glass surface like a 'standard' tablet or is it something else? I'd like to use it with a RockPro64 in the dash of my car with Android if possible.

One additional question, the description says:
Note: Only stock Android OS build for this LCD panel available for ROCKPro64 board.

Verifying that this is saying this panel will only function with the ROCKPro64 with a stock Android OS? If so, which ones? If anyone has any advice for what LCD touchscreen to get I'd love to hear your advice.

Thank you very much in advance!

Results: mobian/2020-08-19

Conclusion: This OS is coming along nicely. Looking at the results I will be following up with the tester to ensure that camera functionality is effective. This at the moment is the closest candidate to making the pinephone a daily driver. (out of our testing group)

Notes: Speakerphone was awful, tons of feedback. Mic was a touch sensitive during calls. Calls were clear otherwise.

(Using AT&T sim).

Soon to begin testing data and hotspot.

Results: ubports/2020-08-19

Build number: Dev-157
Conclusion: This build has been no bueno.  Move along.

Notes:
This guy has been a problem since startup. Not a clue what is going on. Texts stopped working, SMS stopped working. Calls stopped working. I'm going to image my device with a fresh build and execute the tests again. But ultimately not impressed with this build. Camera works ok though.

Today I am also going to begin testing against boost mobile as well as t-mobile. (both US)  I will note any discrepancies in the results. 

Is anyone else experiencing issues with this build?