hello i would to buy a pinephone do you an adress for france
thank you 
i would be happt to have some comments from frenc users too

Hi, my pinebook pro recently stopped working.

Symptoms:
1. when https://forum.pine64.org/member.phpbooting from built in memory, power led lights red and thats all - there is no image on the display (display does not turn on at all)
2. when booting from sd card with manjaro, pinebook turns on, power led starts red, but after some time turns green. Then i can toggle num lock/caps lock leds (works with both internal and external keyboard), but still - display is not enabled.

I've tried starting pinebook using either original adapter or usb c power adapter or with no external power - no luck.

Additionally I've tried to turn on pinebook with all internal plugs disconnected (excluding display and keyboard), but this changed nothing.

Before the notebook stopped working I've replaced default, old manjaro repositories with new and started update. The update failed to updated some things (cant remember which, but I don't remember it being anything important/system related). I can't remember exactly- I think after the update i managed to reboot the netbook, but something was not working so I decided to make clean install using SD card. I mange to boot into GUI from SD card, copy files from  /home to NVMe drive. Then i flashed manjaro installer onto sd card and installed the OS. It finished, but i couldn't boot OS (there were some glitches). I switched  sd cards (the same model) and repeated process with the second card.

At some point the display stopped turning on. 

I have soldered myself audio->uart adapter, switched internal uart switch, but i got no luck seeing any messages on the debug console (maybe i have to do something to enable debug output?)

Is there anything i can do to debug/repair the problem?

Thanks in advance for your help ;]

Hi,

Silly me. But I have been looking on https://www.pine64.org/pinebook-pro/ and https://wiki.pine64.org/index.php/Pinebo...wer_Supply but I find the details about the powersupply a bit vague.

The only info I could find was on https://store.pine64.org/?product=14%E2%...ember-2019 where it said: Power Supply included, comes with both US and EU plugs

But I would suggest a slghty more organised way of presenting the information in the store.

Regards, Hugo.

how long will it take when you do the cheap ship option

I just installed debian bullseye t'other day, with the 5.5 kernel and I love it, mostly.

One thing that surprised me, and concerns me, is cpu temps.

While playing music on youtube with a static image, (no moving graphics), and reading one of my forums, I saw temps hitting 67C.

That's absurdelly hot, Even my big Nvidia cards don't see temps like that.
Now, ambient temp is 80f, no sunlight, and the body of the pinebook is scalding hot.

I pulled out my marble dough making board, and put the pinebook on top of it on the rubber stand-offs, not much temp change. When I moved the pinebook pro so that half of the rubber washers are hanging over the side, (thus the magnesium case is directly touching the marble) temps drop to a much more reasonable 42-55C.

Is this normal? I don't remember temps like this with the stock debian oldstable the pinebook came with.

htop shows 1.97, 2.6, 3.70 for load averages, most of it is firefox.
I'm looking at temperatures with gkrellm and inxi -Fix. the other temperature sensor (whatever it is) only reads 18C.

https://youtu.be/nsArbdB_XUY

Is what I'm listening to, as you can see, it's just a single static image, I am using a USB DAC, HiFimeDIY Audio SA9023 USB Audio type: USB
because the stock soundcard and speakers, well, frankly, blow. Using an external DAC is so much better, it's worth lugging around, especially since I don't have to lug around a power supply.

Laptop is plugged in, at the moment.

TIA, for any information, suggestions.

Question is the title.

Thanks in advance!

So testing on multiple images (pmOS & debian) there is a new behavior showing up for me on my Pinephone where instead of the normal /dev/ttyUSB{1,2,3} showing up; instead now /dev/ttyS{0,2,3} shows up.

I can still see the modem is functional as I can `screen /dev/ttyS2 115200` and play around with `AT` commands; however modemmanager completely ignores /dev/ttyS* devices (there maybe a fix for mm by forcing it to use ttyS* and pointing it to the quectel plugin - but this shouldn't be needed...).

As well, booting up the factorytest image that the device shipped with and trying the modem test - it just shows "Waiting for modem" for a few minutes and then "Boot timeout".

The strange thing is this just started happening all of the sudden and things used to work fine and show up as ttyUSB* - only thing I can think of is maybe force shutting down messed something up (have a habit of just pulling battery out of phone to restart).

Anyone have an idea of how to debug/fix this?

After installing zram, my PBP still froze due to lack of memory, which required reboot.

So I installed Earlyoom, which kills the process it estimates abuse when memory is full.

Installation is very easy: just follow the download and compilation instructions.

You must install the git package to download and the base-devel meta-package to compile.

You can install go and cppcheck if you want to run the built-in self-tests. I don't know if it's usefull.

Earlyoom tries to guess what is the "right" process to kill. For me, this is always the youtube.com tab process of Chromium, which is a good decision because this page can use more than 1go (!) of memory. At the same time, it is not an important tab.

I also tested several memory limits before letting earlyoom go into action.

By default, earlyoom kills a process if available memory and free swap is less than 10%. I lowered this value to 2% for both without preventing earlyoom from working properly. For values less than 1%, the computer freezes before the intervention of earlyoom.

2% may be too low ( <=> 80 Mo for memory, 20 Mo for swap), but for now, earlyoom kill nasty process without problem with this value. If the computer freezes again, I will increase this value.

Thanks in advance for taking the time of reading this and possibly trying to help.

I recently got a 1 GB ROCK64, and I want to install DietPi on it. I have a 32 GB Class 10 micro SD card, a Realtek RTL8188EU Wi-FI USB dongle and a wireless keyboard + mouse combo, so up to this point I assume I'm properly equipped for the installation. The thing is I don't have any 1080p TVs or monitors (I live in Venezuela), but I do have an HDMI to VGA converter, which I'm planning to use with a 1280x1024 monitor. It also supports other resolutions, such as 800x600.

I already tried flashing the image to the micro SD card using Etcher, and the ROCK64 seems to boot up but no image appears on screen. I presume that it is booting up because the mouse turns on when I power the ROCK64.

Although I'm a Linux user, I'm completely new to the SBC world. Please, do keep that in mind.

I want to know how to change the resolution so I can proceed with the installation. I already tried Googling this issue, and even though there is comprehensive information on the subject, I couldn't find a specific solution for the ROCK64. I don't know which file I have to edit to change the resolution of the output.

I presume the issue is exclusively the output resolution, but I can't be sure. I hope someone more experienced can tell me what possibly could be wrong.

I have to add that all 3 lights of the board turn on and stay like that. I haven't tried leaving the board on for a while.

Disclaimer: I already posted this on the DietPi forum, but I haven't received an answer from them after a day. I figured that a ROCK64 forum was more likely to help me.

Has somebody an idea if it would be possible to solder-in some support for NFC?
(e.g.: so the watch could communicate with continuous glycaemia monitors like this, for which there is already opensource code available)