PBP random reboot default Debian
So do anyone of you have the same problem it happens not so often
but it happens..
I'm. wondering if its not rk3399 problem becouse I own an android tv box with the same soc and there happens too quaite often

Hi, just as a heads-up, you might want to reconsider the packaging a bit for future versions.

I've received my brave-heart edition and the plastic shroud where the phone is mounted inside the box has some breakage after shipping.

No qualms from me, I don't think anything else is damaged and that's what beta-runs are for, but you might want to iterate on the material for future versions.

Hey guys,

Just wanted to create a new thread to confirm the information I have received about my PinePhone.

I ordered on Jan 7 2020 and received an email that day with my order number.

I have received nothing since.

In my other thread we discovered that there are other people in the same situation. Several who ordered in January, and some who ordered right back in November.

We got information that "about 80 PinePhones were left in the warehouse due to a problem with mailing labels not being printed". These were apparently all ordered after January 5 2020.

I also got an official response from a support ticket I sent to Pine:

"Please to inform you that the PinePhone ordered at January 2020, is estimate to be dispatch at around mid/end of February.

Also, we will provide the tracking number once available."


So my phone has not been shipped and won't be until mid/end of February, so arrival won't be before mid-March. No reason was given, officially they were supposed to be shipped in January and now that has slipped to the end of February with no notice.

This is disappointing to say the least as otherwise Pine have been so impressive to me.

So I can only assume that if you haven't received any update after your order confirmation email, then you won't receive your PinePhone until March now.

Don't get me wrong I'm still a huge supporter of Pine, and I really hope the PinePhone succeeds in changing hearts and minds about the possibility of a popular Linux phone in the coming years. I really do wish them all the best, though I have been burnt here somewhat.

My advice to them would be simple, be 100% transparent and clear about shipping, even when delays are present. I know in China/Hong Kong things are a little on edge right now with the virus. I also know Chinese New Year is clearly a very important time, and so work might be less of a priority. The right thing to do would have been to confirm on Jan 24th, that X amount of PinePhones still had not been shipped due to reason X or Y (they have this info clearly, or could do an easy database lookup), and would not be until late Feb. I would have been sad but I would accepted that mistakes happen. This week of no information is just frustrating, and entirely unneccessary.

I was going to order a PineBook, but now I've decided to wait until my PinePhone has arrived, trust has been lost slightly.

But anyway, I just want to confirm I'm still a big fan, and I'm not mad, just gutted that's all! I'm a software dev/tinkerer and was looking forward to being 'the first' to do something on the PinePhone. Now others will get a 2 month headstart on me.

I am Manjaro KDE on my Pinebook Pro and I can't for the life of me get it to connect to the Enterprise network at the school I teach at. I know it's something on the software because I am able to connect to the network when using chromium on the same machine.  It looks like it hangs at "setting network address.". I have tried deleting and manually re adding the network. I have tried restarting. I have fiddled with all sorts of the network settings, but I know I have them correct because my phone and the same device connects with these settings.  I have tried reinstalling wpa_supplicant. I have tried adding the network with some command line tool, but it didn't support PEAP. I've exhausted all that I know and all I can find out from Google. Any help is welcome.

I want to make sure I'm not cooking my board. I'd also like to ensure its getting enough power.

With raspberry pi:

My new pinebook pro worked well when I first used it on Monday (except for the trackpad, but I hadn't done the firmware update yet).
I used it to connect to my desktop via remmina & enjoyed the experience.
Then I closed the lid & left it in my backpack (assuming it would go hibernate/suspend), the next morning it was off and would not turn on anymore.
I assumed the battery had drained so I connect the charger (DC wall-plug, not USB). The red LED next to the charger input lighted up.
I left it charging all afternoon and occasionally tried to turn it on. But it wouldn't even after a couple of hours.
After a couple of hours the red indicator LED stopped lighting up (someone on the irc told me later that indicates full battery - Initially I thought my battery did not charge).


So far I tried a bunch of stuff that was suggested in the forum, or the wiki, but so far nothing has made the device turn on or show any indications of life (leds, screen) when pressing power:

1. remove battery while power plug connected (in case battery had completely drained), wait 5 seconds, reconnect, wait 20 min then press power. Tried this four times total.
2. try if powers up with battery unplugged, DC-plug connected and bypass cable closed -> except high high pitch noise for a few seconds nothing happen
3. checked for loose connections of emmc, daugtherboard, flipped emmc/sd switch.
4. tried to boot from sd (mrfixit2001 image), with emmc/sd switch toggled on or off.
5. hit reset button.
6. flashed emmc via emmc-sd-adapter directly from my laptop with bionic lxde image via dd & tried to boot that.

Thankful for any suggestions.

If you install this package on Manjaro as required by some qemu+wine x86 tutorials on rpi, you will break your system and have to recover through chroot.

If you tend to follow RPI tutorials, or attempt to, to accomplish things, this one can have some bad consequences.
I'm not familiar with it so obviously as a rule don't run stuff if you don't know what it does, but I have been doing that a lot on PBP. It somehow made the system act like every binary was the wrong architecture, so not even basic commands like ls, cd, etc worked immediately after install.

Hi,

I'm playing with my Pinephone for few days. I'm mainly trying Ubuntu Touch for now.

I have not found a better place to ask questions so I do it here.

I have a problem with wifi which, for some reason, stops working.
Once it has stopped working, the only solution I've found is to reflash the SD card. Then, it works again untill it stops again.
When the wifi is not functionnal, ifconfig shows only loopback interface.
Any workaround ?
Maybe a console command to reinit software ?

Regards,
Nicolas

greetings,

included is a kernel build script, and dependencies debian-based systems (and you can modify for other systems easily... ).

this fetches the tsys/manjaro *v5.7* branch from the manjaro git, applies a config of your choice, preps, builds, and debianizes a custom kernel. build time is about 90min for the pbp, or ?min via crossbuilding. (for me is ~10min.)

you can also choose any branch in the manjaro git by changing the VAR.

enjoy!


SCRIPT
script now part of pbp-tools. see other forum thread for details.
https://github.com/xmixahlx/pbp-tools
https://forum.pine64.org/showthread.php?tid=10190

What should be done when Chromium ask to upgrade? Ignore notification and wait for apt update to show new version?