tricky getting past the install stage, screen goes dark ,and off ,several presses of the on/off will sometimes bring it back, risky setting a lock code ,screen changes before you get the code entered.
 but the general operation ,is very smooth ,and i would say improved a lot.
i did not put a sim in it.
if not for the screen blacking out and jumpy unlock screen , looks almost like a daily driver, (assuming the modem/phone works)
.
anyone else try it.?

< tried two downloads, the second seemed a little better, but still had something going on >

Games can be launched from command line but emulationstation crashes on load (x connection broken error) and the virtual keyboard map is pretty random. Anyway, here's a blurrycam video showing it in action.


  quake3a.jpg (Size: 183.37 KB / Downloads: 961)

I like the idea of the pine book pro but was looking for something a bit different. I though it could be called computer 64 abbreviated to C-64  . Anyways the concept would be similar to the pinebook pro but rather a mini arm computer for use with linix or BSD though I am thinking alot of Arch Arm Linux using the Arch Packman to native arm compile tarballs. Now as for the project aspect of the board would be to use for open source projects for things such as making a wifi router or a Media server or Media TV box etc with the supportive hardware to do so. That would require things such as multi connect for wifi board and ethernet switches. Also hard drive supports etc. The basis of the idea is that native arm programs run very well on Arm hardware but suck at running X86 on arm. With Arch the packages could be compiled for arm.

tl;dr: Does a Pine64 eMMC writer work with a non-Pine64 eMMC module?


I just purchased an eMMC module for my Odroid C2 and a USB2.0 eMMC writer from Ameridroid:

https://ameridroid.com/products/emmc-mod...ux-red-box
https://ameridroid.com/products/usb-2-0-...ule-writer

Nowhere in that listing does it state the writer is Pine64, but the packaging it arrives in is thusly branded.
The module works. It ships with a Hardkernel build of Ubuntu 18.04 on it, and my C2 can boot it OK.
I tried asking Ameridroid if they had any hints to make this work, but all I got back was "you can RMA it, but if it's working there will be a 25% restock fee".

So my question is: Are these parts even compatible? I thought eMMC was fairly standard, especially since the connector fits.

Hello,

I am trying to build a system based on buildroot for the Rock64. It appears that the Ethernet driver is not insmod

# lsmod
Module                  Size  Used by    Not tainted
ipv6                  425984 16 [permanent]

Could someone please help me with reference from other distributions that has a working ethernet driver source & the init.d scripts that load all the kernel modules for the Rock64.

Thanks,
-Michael.

Hey folks,
What does it mean when the red charge indicator on the side of the PBP is blinking?

Because the batterie auf my PP was 'grown' after one week using I have contacted the support. After a long conversion / discussion I have bought a new one from Amazon as the support ream has told me:

----------------------However, you may purchase the replacement battery from any online market(Amazon) which is same model with Samsung J7(2015).


---------------------
But the J7 batterie is more than 1mm bigger as the original one. Now I'm still can't use my PinePhone.

What a bad support !!!!!!!!!!!!!!!!!!!!! Never again !!!!!!!!!!!!!!!!!!!!!!

I will preface the post with this - I am a wireless engineer and have nearly all of my devices using wireless. My PBpro wireless issues have nothing to do with the network environment.

So I purchased the Pinebook Pro in Nov of last year, receiving it in late Jan. Aside from all the hoops you have to jump through with updates, etc. to get it to a point of being useful, followed by more updates to get the trackpad working correctly, it is now a pretty nice machine.

However, there remains one HUGE problem with it that I have not been able to remedy. The wireless does not work consistently; it always disconnects then appears to connect, yet cannot resolve any domain names, cannot ping, etc. Starting a ping to some site or constantly refreshing the browser eventually gets it connected again, but only for short periods of time. From what I can determine, this device has extremely poor receive sensitivity. There is nearly nowhere in my home where I can go and not get at least around -48dBm RSSI, and yet the PBpro is in the -65 range (still good, but not accurate in my environment) within 10 feet LOS to an AP.

Something else I notice is that when I see a successful reassociation on my controller, it isn't reflected on the PBpro; dmesg shows that it is associated, however I have stop / restart ping or completely refresh my browser to get comms working again.

Can anyone point me in the right direction to get this working and to stay working? I have run the updater; I also did find some posts about issues on a WPA2 network (which mine is), but seemed inconclusive.

Any feedback / help will be greatly appreciated. Thx!

Are the current limits to purchasing multiple Pinebook Pro laptops intentional? or some kind of left over default from the pre-order / initial run period?

It seems weird that I cant buy multiple Pinebook Pro laptops, but because its just a regular item, I could just pay for that one, and order another one, and since I was thinking of buying 3 of them, I'd end up paying half the cost of a Pinebook Pro in shipping (3*$33) ... /end-of-silly-example.

But yeah, I was looking to buy 2, and was surprised to find I couldn't.

Is there a reason for this?

Hi All

Thanks in advance for any advice. I am trying to bootstrap my own Debian install on my Pinephone and after alot of faffing and false starts I finally managed to boot a kernel I had build into a Debian install I had bootstrapped, cos why wouldn't you on FOSS phone!

The last hurdle I came across was the boot.scr script not being run by u-boot on my image, I had copied the one from the Debian+Phosh image and then updated the entries to point to my kernel/initramfs. There are some non-text bytes at the beginning of the file which I think is might be the reason its not booting (checksum/hash maybe) but once I had restored the original and copied my kernel/initramfs files to the to the names used in the boot.scr it booted without issue.

So, the question! How do I generate my own boot.scr correctly?

Thanks Again

hk135