Since 3000 PinePhones are in production I'm pitching my idea of an open-source tracker device that you could attach to your valuables if they are lost ... eg keys, luggage etc.

Hi! I'm new to the SBC world, so please excuse my noobness.

I've tried multiple images on my new Rock64 and all of them, at some point, crash. The problem is that I can't see the error messages because a lot of information is output too fast. Is there a location where that information is logged? I tried checking kern.log and other logs in /var/log but coludn't find anything.

Hi

Just received my NVME adapter today and had and m.2 nvme to stick in.

I took the back cover off, put all the parts in (without folding the cable), put it back together and booted.

My PBP saw the drive, I opened Gparted, created an MSDOS partition table (didn't know which to choose as it was default) and formatted the entire drive as an EXT4, with the intention of having it mount on bootup for extra storage.

after formatting the drive, I tried to mount if with the following result

Hi ... I just received my PinePhone from the Developer batch ...

... it came in a nice transparent plastic case inside a paper envelope.  The telephone looks very nice (good work) ... however, there is no battery in it, neither a recharger, cables or any other accessory, just the phone.

Is that OK? ... just to clarify.


Anyway, I will dig deeply on this device to see how to make magic ;-) ...

Few of the problems to be described, with my Rock64 2GB equipped with SATA-to-USB adapter bought all from the official pine store.

First launch as a home server - hard drive (500GB 2.5') died after two or three months. OK - it wasn't new one, could happen.
The second launch with similar hard drive and death of hdd after three or four months.
I suspected the result of unreliable power plug, which makes me troubles too. It failed on delicate touch. There was no way to move rock64 at all when it was working.
I replaced the board's power socket using the one linked here on forum. Of course loosing any guarantee and possibility to sell this hardware someone else because of manual changes to hardware.
But, It didn't help. Thus I replaced the power plug and finally I have stable powering.

In the meantime I configured some old microPC as my home server and currently, while it's working very well, I'm trying to use my Rock64  at least as non-critical NAS.
I've connected 1TB 3.5' Hard Drive WD Green with additional 12V power.
This time with system on SD Card. Because there is too frequent problem with starting from external HDD after reboot. It's starting once per two/three attempts. So can't be rebooted remotely if needed.
After two or three days I observe hd related errors in dmesg. Smartctl reported me lack of connection to HDD.
Changed kernel from 5.0 to 4.4.
Aftet some minutes after boot, the LED on adapter is solid red all the time even though there is no disk activity, and this time again  after two/three days disk is failing in logs, smartctl also sent me email about terminated communication with disk.
I'm affraid that I'm going to loose third hard drive!

Just to conclude.
The idea of ARM based PC is interesting but there is a lot improvements to be done still. Apart of maybe particular sample's hardware problems there are also software related issue.

Hi PineTime Community: Here's my new article that explains how we may build Watch Apps in Rust for PineTime...

https://medium.com/@ly.lee/porting-druid...0efd167b07

I gather a call was received, but not sent yet?, using pastmarketOS. I think you can also send txts on pmOS?

Is that right? Do any of the available OSes (also Ubuntu Touch, LuneOS, Sailfish) have two-way call and/or txt capability? I get the impression the answer is no, but I don't know why it feels like that. Finding actual info is really hard! (Maybe just for me, but there it is.)

Also, pmOS has mobile data working. So if I'm using Signal, for instance, which uses data instead of the cellphone company, will the calls work?

Thanks to anyone who knows the answers or where to look for them!

Hi guys,

I hoping to get some assistance with my pinebook pro which no longer powers on.
I've been using the factory installed debian and thought i'd give manjaro a go.
I used the Manjaro-ARM-kde-plasma-pbpro-19.12.img.xz image and put it on my micro sd via etcher. After booting up on the micro sd the manjaro install continued (i chose user name, keyboard layout etc) then it rebooted
Since then I can't get my pinebook to power on with either the micro sd in or out (I was at least hoping debian would run without the micro sd).

I came across this thread but want to be I believe my situation is different (I thought I didn't write to eMMC)???

-update 1- since writing this post, I have been able to get the power light on (flashing, but nothing on screen).
-update 2- i've plugged in power and it boots now via debian. I will test further and report back
Many thanks

George

I am attempting to add a mk to OP-TEE/build for the pine64-lts.  I'm pretty far along but have some fairly sticky faults.  The first was the transition from ARM-TF to optee_os failed.  So I sent some emails off and focused on something I thought would be easier, booting Linux.  

What I've done is copied and modified the build script from qemu with concepts from other boards (poplar, rpi3) and brought in mainline u-boot.  U-boot is made aware of ARM-TF and the board readily boots the resulting .bin.  Next I wrote and compiled a boot.cmd:

Good day Gentlemen & Gentlewomen,

I can't get the Chromium to work with the hardware accelartion.
Usually I wouldn't bother but its impossible to play videos from netflix like that (at least not in fullscreen mode).

Chromium gives me a error like this:

• [12710:12710:1213/204638.585707:ERROR:gl_surface_egl.cc(1043)] : EGL display query failed with error EGL_SUCCESS
  
  
• [12710:12710:1213/204638.585948:ERROR:gl_surface_egl.cc(1057)] : eglInitialize Default failed with error EGL_BAD_DISPLAY
  
  
• [12710:12710:1213/204638.586005:ERROR:gl_initializer_x11.cc(156)] : GLSurfaceEGL::InitializeOneOff failed.
  
  
• GpuProcessHost: The GPU process exited with code 1024.