I tried several ways to put the sim card in the l lower slot. 
First, I pushed it all the way in and as a result the card almost completely disappeared in the slot, but the phone didn't recognise it. It was very difficult to take it out, I had to use a needle to force it out. It took me quite some time to take it out. I am afraid I damage the simcard. 
What is the proper way of putting the simcard in the slot?
Thanks a lot.

Hi everyone,

I just got my phone in the mail and got PostmarketOS up and running. The phone is not detecting any telco access points. My Android phone does. Any ideas?

Cheers,

Pinoideae

Good morning everyone,



I'm new here and I ended up there following the beauty of the Pinebook.

I was looking for infos about how to buy a Pinebook, but I couldn't find any new about it. I only found infos about Pinebook Pro, PinePhone, PineTime and PineTab... Is there a way to know if Pinebook 11" is still available or it has ended?


Thanks in advance.

Had to take it apart again after the sd card got trapped again. when reassembling one of the securing magnets at the bottom dislodged and got in the way as I was snapping it closed. so now the screens cracked. will replacements ever be made available?

This is for those making distros
It is most annoying when blkmmcX "jumps" around, there is NO consistency
This really pisses me off, and I am sure, confuses many people (myself included)
So, we could follow uboot, mmc0 is first device found, mmc1 next, in bootrom order I think
OR
make symlinks. /dev/emmc -> emmc (whatever it is),,,, /dev/sd  ......
A bit of a problem if device is absent maybe???

It, after all, is only an edit of dtb, well dts, in alias section
It would be so much more easy giving advice,
and, with a desktop, for most, /dev/sda is the boot drive, and maybe no other
until a flash is inserted

I have UT on my eMMC and multiple distros on different SD cards including a newer UT so i can use it with expanded memory. For some reason, regardless of what SD card i put in, about 40% of the time it will bpot from eMMC and the other 60% it boots feom the intended SD card. My understanding is it should only boot from SD if one is present, but thats not my experience. Sort of like flipping a coin each time i boot.

just in case it helps anyone, I couldn't find a way to open the sd slot cover on mine. A bit of stray glue seem seems to have got onto the inside just there. After taking the back off and removing the excess glue it's now operable, however the alignment of the slot and the case makes it really difficult to insert and remove cards. Is this typical of others experience? I'm just wondering if I haven't put the back on properly.

OG thread for the PinePhone: https://forum.pine64.org/showthread.php?tid=10507

Latest builds can be downloaded here: https://github.com/dreemurrs-embedded/Pi...h/releases

Discussion Channels:

• Discord: https://discord.gg/AvtdRJ3 (#archlinux-pinephone)
  
• Matrix: #archlinux-pinephone:kde.org
  
• Telegram: @archlinux_pinephone
  

Hi,
I'm trying to troubleshoot an unusable PPB I've just received.  I've read here:

Quote:The Pinebook Pro is capable of booting from eMMC, USB 2.0, USB 3.0, or an SD card. It cannot boot from USB-C. The boot order of the hard-coded ROM of its RK3399 SoC is: SPI NOR, eMMC, SD, USB OTG.

Hi all.

After sharing the same experience that @EverythingIsInput @tiagoespinha @Eight Bit @Abandoned Brain @axel and no doubt countless others have had. I joyously unboxed my shiny new Pinebook Pro a couple weeks back, spent a delicious evening enjoying that new laptop glow, closed the lid and went to bed happy.

Only to wake the next day to find in utter dismay that the battery was totally dead. Utterly. Drained. Had to do a full recharge cycle, which, even with the barrel plug takes quite a long time.

Lather, rinse, repeat until I checked here and figured out that sleep / resume just doesn't work and that many others have felt this pain.

So I went on a bit of a quest to try to understand the problem and see if I could discern a fix or at least a usable work-around.

So let's start with:

The (Kinda Sorta) Good

At least now I understand the problem

First, I tracked down Strit, the Manjaro-ARM release manager who was incredibly helpful, informing me that he'd heard that the bug was actually a bug in the Trusted Firmware, and that he'd heard this on the Pinebook Discord/Matrix.

So, I went there and started asking around, and @CrystalGamma said that he understood the issue, but that he's working another project, and if the fix isn't in in about a month when his project completes, he'll dive in and help make that happen. He mentioned that @theotherjimmy had been the one working the fix but that he hadn't been around in about a month.

At that point @theotherjimmy popped up and very helpfully explained that yes, he's been stuck on the latest suspend/resume bug but in fact there are actually *4* related bugs that would need to be solved before end users can get this to work.

He also explained that the bug is in RockChip's vendor code and that he likely wouldn't have time for it for a while since his employer has him working other issues.

They both pointed out that the Git repository containing the firmware is here
but CrystalGamma pointed out that debugging these issues requires the audio jack to USB adapter from the Pine store, but also that this adapter *appears* to have the wrong voltage (5v as opposed to 3 and change volts) and as a result could damage your Pinebook Pro if you try to use it, so there goes any thoughts I had about trying to fix this myself

The Bad

So, the bottom line is, for us end users, we essentially should abandon any hope that suspend/resume as we know and expect it will work anytime soon on the Pinebook Pro. We're talking at *least* months. Possibly longer.

Ultimately, Pine64 made it very clear that we were buying into an open source experiment here, not a polished product, so I bear no ill will against them in this, but I can't lie - I'm extremely disappointed. This situation diminishes the usefulness of the PBPro for me tremendously  - it means I have to shut down and power up from cold boot every single time I want to use the laptop.

At least, for the moment, I have figured out a really UGLY work around that makes me incredibly sad but at least keeps me from forgetting and draining my battery every time I walk away from the laptop for the day.

The (Very) Ugly

So, what I have done in order to semi-mitigate the situation is to configure KDE to shut the laptop down whenever the lid is closed. To say this isn't ideal is the understatement of the century, but what else am I going to do?

In order to do this, click the Manjaro button in the lower left or hit the Pine logo key on your laptop, and type "Energy Saving".

This will bring up a dialog with three 'tabs': "AC Power", "Battery" and "Low Battery".

Under "Button Events" I simply changed "Sleep" to "Shut down" for each of these categories, and that seems to the needful and at least keep the laptop from bleeding out overnight when its lid is closed.

In Closing - Just To Be Perfectly Clear

I knew I was taking a risk when I bought this laptop. Pine said in no uncertain terms that it was selling these at cost and that returns were only allowed for drop dead problems like a totally DOA unit.

I also recognize that this entire venture is an experiment in the spirit of open source - let's take some high value low cost hardware, assemble it in innovative ways and see what the community does with it.

All the people I spoke to about this were incredibly friendly, helpful and forthright. They've all poured blood, sweat and tears into this project and others, and I would ask that anyone who uses this to contact them please treat them with the utmost respect and deference.

I can't lie, I'm disappointed in a number of ways, but I continue to be on board with the experiment and will keep trying to use this hardware until I come to the conclusion that I am absolutely unable to do so.