Hello team Pine64:

I hope that this small write-up has relevance and information that will help newcomers to the land of PBP who want to experiment with other operating softwares on the platform. I've been reading many horror stories of Pinebook Pro's that were damaged, or that the owner THINKS are damaged because they won't boot properly... after a user found themselves with an inoperable OS on their internal eMMC storage.

It seems that once a rookie user has an issue with their eMMC the first thing they do is open the laptop and flip the reset button next to the eMMC storage. This isn't always necessary. I wanted to go over how I reinstalled the original [or updated, if you have an older version of the PBP] Manjaro OS back onto the eMMC without opening the system. From what I can gather, you can certainly open the system and access the internals to get things done - and in some cases this needs to happen... but I'd be willing to bet that in most rookie scenerios, this isn't the case.

Furthermore, I'd like to state an easier way to experiment with other OSes rather than modifying the eMMC in the first place. Sure, if you have come across an OS build that you want to run in production, forever, I understand putting that on the eMMC... but I think people get into trouble with their PBP because they just want to play around, try to throw a new OS on the eMMC and don't have all the Linux knowledge needed to doso - ending in 'a boat anchor' or being upset with the hardware.... that did nothing wrong. It only does what we tell it to, and follows directions - even if the Pine64 'outline' isn't perfect. The proper way to play around with OSes is to burn them to an SDcard and boot it up; if anything fails or doesn't operate correctly, you just take it out and smile because you know the next boot will be your perfect Manjaro install on eMMC.

There is a whole list of OSes on the wiki:
https://wiki.pine64.org/index.php?title=..._Downloads

You can download any one of these, and I prefer to doso on a different system but you can certainly doso on the PBP and use dd if= of= to burn your SDcard, and use a software like Balena Etcher or any SDcard burner and burn the ISO to the SDcard. Just pop that SDcard in the slot of the PBP and go have fun... play with that OS, dig into it... mess it up even! [With the understanding that you leave the eMMC storage alone, and don't much with IT!] You can always simply pop that SDcard out and boot right back into your Manjaro build. Simple pimple.

Now, if you do happen to mess up the build on eMMC don't immediately grab a screwdriver and get all hardware happy and think that you're a Linux-ninja. It isn't necessary! [For most of us, anyway...] In fact, if you mess up the eMMC at all lets set the PBP to the side for a few minutes and settle down. Go over to the wiki, at the same link I posted above, and download the Manjaro ARM with KDE Plasma MicroSD and eMMC Boot Direct Download from Manjaro... unzip it, grab the .ISO and burn that to an SDcard... heck, you can even use dd if= of= if you just have to feel like a CLI rockstar. Boot from that Manjaro SDcard and update the system thru the dock, the pamac GUI software utility or by 'sudo pacman -Syyu'. Next install 'manjaro-arm-flasher' with pamac or pacman... run manjaro-arm-flasher. Select pinebook pro, KDE Plasma, 20.08 and mmcblk2.

Important: If you don't see mmcblk2, but rather boot1 or boot2 - don't select that! You can find more info at the thread link below, but since you should be doing this from an SDcard, I don't think you should see this:
https://forum.manjaro.org/t/manjaro-arm-flasher/26002

Anyway tho, if it does list boot1 or boot2 you need to unmount the eMMC before flashing! So long as you see mmcblk2 and select it, make sure you have ample battery charge and the laptop is plugged in, and click Start... let it do its thing.

When finished, you can shutdown. Take out the SDcard and when you reboot the Pinebook Pro you should have a copy of Manjaro ARM booting from eMMC with no SDcard inserted.

The Pinebook Pro is just as it comes from the factory. [At least if you have the newest PBP available.] Again, 'sudo pacman -Syyu' and your done.

Personally, I'd suggest keeping Manjaro ARM on the eMMC and play around with other OSes on SDcards... this ensures that you don't ever have to go deeper before you want to. You shouldn't HAVE to open the PBP or flip the eMMC switch unless you've already messed with things and now have a bigger problem to fix.

Even if so, don't give up... we can get your PBP back to factory settings with Manjaro ARM on the eMMC... these machines only do what we tell them to; and only respond to events that we create... so when you go deeper you just get further into a situation that is harder to back out of.

Remember you have a community here to help you; and I will, along with an army of other REAL Linux-rockstars. All we have to do is get you backed out of what you created. If you just follow these basic set of baseline rules, you'll never get there! If you find an OS that you just love, like I really like Armbian, we can put that OS on the eMMC... and you can still experiment with others, using SDcards! We just have to feed the computer the correct instructions - it WILL respond and function.

Anyway, I hope this long ass write-up helps someone so that they don't get down the rabbit hole. We got this...

Hi,

I have added the capability to decode QR codes within megapixels. If a QR code is founded, a special button changes its color and allow to view the data of the code, to copy it to the clipboard or to open the link.

This is more a Proof of Concept than a finished product. The interface needs to be improved and no check is done before creating a link (this might be a security risk).

You can find my work there: https://git.sr.ht/~antoines/megapixels

I need to contact the author of megapixels to see if he is interested in adding this kind of capability.

Antoine

Hi PineBooker's,

I bought the PBP relatively early when it came with a different version of Linux.  I've really enjoyed it for many things but couldn't quite get things working to make it fully capable for me.  I burnt the Manjaro Linux at that time to a microSD and tried that too.  It was not quite ready for me either.  Seven months later, I descided to give it a try again.  This weekend I installed Manjaro 20.08 on the eMMC disk and was up an running in no time.  Most everything I need is working great!

When I first got the PBP I searched for and bought the lowest profile accessories:

• A little, perfect size carrying case
  
• iLuv AUD Mini Bluetooth Speaker (never got working on PBP before this weekend)
  
• FENIFOX Flat Portable Bluetooth Mouse (I am not good at trackpads so I turn it off when working)
  

Opened my phone to check connectors (re issue https://forum.pine64.org/showthread.php?tid=10882).
Freed the inner frame around the edges only to discover that it is fused to the motherboard at an area next to the battery connectors.
https://www.flickr.com/photos/185472830@...ed-public/
Coincidently(?) this area is where the usb ribbon cable passes to the SOC. Presumably this could also relate to my usb issue? The frame sits normally flat so hasn't been distorted.
https://www.flickr.com/photos/185472830@...ed-public/
Is heating recommended to help removal? Otherwise removal might be destructive.

When trying to install the openstore https://open-store.io I get the following output

mobian@mobian:~/Downloads$ pkcon install-local --allow-untrusted openstore.openstore-team_3.2.1_armhf.click -v
11:59:39 PackageKit          Verbose debugging enabled (on console 1)
11:59:39 PackageKit          filter=(null), filters=0
11:59:39 PackageKit          adding state 0xaaaabf619ca0
11:59:39 PackageKit          doing install files
11:59:39 PackageKit          role now install-files
Installing files              [                        ] (0%)  11:59:39 PackageKit          notify::connected
                              [                        ] (0%)  11:59:39 PackageKit          using frontend dialog
11:59:39 PackageKit          using socket in /tmp/gpk-53_dbdadbae.socket
                              [=========================]       
Testing changes              [=========================]       
Finished                      [                        ] (0%)  11:59:40 PackageKit          remove state 0xaaaabf619ca0
                              [=========================]       
Fatal error: Could not find package(s)

Does anybody know what I am doing wrong?

Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.

Results: ubports/2020-09-28-TMobile

Conclusion: This OS is not ready for the device to become a daily driver.

Notes: Alright, after a couple weeks off, I was hoping for some different results. I guess not; Still open to the idea that the camera button is to reverse the image not switch to the 'selfie camera' if anyone can confirm either way I would appreciate it. Failed 4G outbound call still an issue. 3G outbound texting is still broken. No real Progress.

Issues:
4G outbound calls broken.
Phone gets stuck in a weird lock state when spamming power button.
Outbound SMS over 3g is broken.
Audio cuts out after "No Calls" error is handled on inbound/outbound calls. - Unable to replicate this one at this time, but it is still an issue.

I'm not booting from sd card. Tried copying and pasting the updat_sh in terminal after downloading the files but still not working. Am I doing something wrong.

My PBP makes a regular, intermittent, quiet but audible, whining/buzzing sound. It goes about 4 seconds on, 4 seconds off. I started noticing it today, but I'm not sure if it started today. It's irritating enough that I've been playing music to cover it up, but that's not an ideal long-term solution.

Any thoughts?

What is the pre order deadline for the Manjaro OS PinePhone date?

Simple question I know. But I can't seem to find an answer for it here?