Hello everybody,
I am already 4 days new proud owner of PineTime . After some playing with firmware updates, flashing wasp-os and solving bug with hanging bootloader in version 0.8.2, I finally have my PineTime updated to InfiniTime 0.9.0 - I used binary packages from https://github.com/daniel-thompson/wasp-.../350930611 (for other newbies like me: you can download it after logging into github...) which I found on this great video: www.youtube.com/watch?v=lPasAt1LJmo

After that, I started to try changing boot image and to compile my own Infinitime binary - for this first try only with changed day and month names to my native language (czech). And I'm hanging already 2 days on uploading new firmware, which seems to be uploaded correctly, but make no changes on my PineTime  .

I surely don't want to use SWD cable connection, when there is working OTA way with nRF Connect - I don't have JTAG programmer, but for the worst case I can use my Raspberry Pi, but I thing, that it will be more pain, than with DFU.

Can somebody of you help me with this way? I will be glad to write than some beginners tutorial into wiki, to help others make this first step...

My (not working) way:
1) I'm using Ubuntu 20.04 PC and Android Phone, PineTime from last batch with opened flash and firmware as written above.
2) used tutorials are https://github.com/JF002/Pinetime/blob/m.../README.md and https://github.com/JF002/Pinetime/blob/d...Program.md (and many others :-))
3) compiler is package arm-none-eabi from Ubuntu 20.04 repository, nRF-SDK is installed is copied (unzipped) into my home directory, last version SDK_17.0.2_d674dde
4) image is converted using https://www.digole.com/tools/PicturetoC_...verter.php - PNG, 240x240px, changed only hex data in file  bootloader/boot_graphics.h
5) changed constants of day and month names in file src/libs/lvgl/src/lv_objx/lv_calendar.c
6) on root of git data directory: cmake -DNRF5_SDK_PATH=/home/lookin/sandbox/nRF5_SDK_17.0.2_d674dde/ -DUSE_JLINK=0 -DARM_NONE_EABI_TOOLCHAIN_PATH=/usr/ -DUSE_OPENOCD=1
7) on the same directory "make -j" - everything compiled ok
8) mcuboot/scripts/imgtool.py create --align 4 --version 1.0.0 --header-size 32 --slot-size 475136 --pad-header src/pinetime-app-0.9.0.bin imageA.bin
9) mcuboot/scripts/imgtool.py create --align 4 --version 1.0.0 --header-size 32 --slot-size 475136 --pad-header src/pinetime-graphics-0.9.0.bin imageB.bin
10) ~/.local/bin/adafruit-nrfutil dfu genpkg --dev-type 0x0052 --application imageA.bin dfu-imgA.zip
11) ~/.local/bin/adafruit-nrfutil dfu genpkg --dev-type 0x0052 --application imageB.bin dfu-imgB.zip
12) with nRF Connect I upload boot image: dfu-imgB.zip - everything is ok, 100 % pass, "image ok", PineTime is rebooting and starts with old "PineTime" picture 
13) also imageA.zip is completly loaded, after "image ok" label is device rebooting, hangs for a while on PineTime logo reboots once more and start old app...

I will be thankfull for all ideas, what am I doing wrong...

Hae a nice day
Lukas

I've got some questions about the pinephone's deep sleep (using crust) that I'm struggling to find answers to.

Firstly, how can I tell when/if the device goes into deep sleep, or if a distro even uses it?

Secondly, how is it activated? Is it done automatically as part of normal suspend-to-ram, or is it its own thing?

Last, are there any notable differences in how the device can be woken up from deep sleep compared to normal sleep? Mostly thinking of timers/alarms, but I can test those myself if I know the answers to the earlier questions.

Any information/documentation is appreciated

im having issues with the wifi on my pine64 LTS, im using android 6.0,
it gets a weak signal and randomly drops the connection, im unsure if its a software or hardware issue, i have swapped out both the antenna and the module with a spare and seem to be having the same issue, when it sometimes connects it says there is no internet but sometimes it still works anyway, has any 1 else had similar issues and know of a solution?
could the pine board or a tablet speaker cause interference with the signal, or does is sound like its a hardware issue?

Hi Community!

I've been enjoying the Pine64 products a lot, and I had not have any problems with them, until the Pinephone Manjaro Edition, so I contacted support a week ago, but I didn't received any answer yet. Is there anyone with the same problem?

I assume they are very busy, I only want to know how long I have to wait until I make another ticket...

Thanks very much!

Hi,

I received my PinePhone with a preinstalled version of Manjaro.
I do not like this OS, I' used to work on Debian.

The received phone does not work correctly: I changed the user and it is impossible to set the date and time correctly and this does not sync with the internet time.

Main failures:

- The pacman grafic software the 2/3 of the times installs not working software
- Terminal: impossible to use a lot of normal terminal sofwtares, impossible to use different installers than pacman
- Manjaro is a very low compatibility with other linux softwares 
- Manjaro offers very few softwtares, often they do not work properly
- Manjaro offers very few way of setting and personalizations
- Difficult to adapt windows to the screen
- Battery runs out of energy very quickly
- System is very slow
- It bugs

Conclusions: Manjaro is very bad, I would not suggest it at all!

Do any of you have any suggestion?
Is it possible to solve any of the problems listed?

Thanks!

Does anyone changed the screen of the PinePhone recently?

My PinePhone screen broke a month ago, i received the new one 2 days ago and immediatly changed it.
I had no particuar problems but after rebooting i noticed both cameras weren't working anymore.
Megapixel app on Mobian says "Error opening the video device" and if i try to swicth from the back one to the front one the app closes.
I don't know what happened, i didn't touched them, i just dismounted the main board following the video from Martijn Braam, the cameras remained in their places, of course there were no reasons for me to detach them from the main board.
I tried to detach them sereval times checking the connectors, they look perfectly connected.
I tried with different OS to be sure it's not a software problem, even checked the pins in the back to be sure they weren't in the disabled position, and also moved them in the disabled position, rebooted the system to check if something changed but no luck at all.

Is it possible they got briked somehow? I really don't understand.

The speakers in (at least some) Pinebook Pro are out-of-phase.  If your audio level seems low, this is probably the cause.  I just corrected this on mine, and I strongly encourage everyone to do this.  Don't wait for a software band-aid for this hardware problem; that is bad practice.

Of course, you need to remove the bottom of the PBP, and follow all the precautions that normally go with that.  Next it's a matter of unplugging the speaker connection from the mainboard.  Note the order the wires on the plug are in.  Then, mercilessly tear the red and white wires out of the plug.  Pull them out by lifting them from the plug, not by pulling in the direction the plug inserts.  Swap the positions of the red and white wires, and press them back into the connector with a small flat blade screwdriver.  Plug the connector back in. reassemble the PBP, and enjoy better audio.

Don't know if this is the right place to start. Former developer with notes on Manjaro on Pinephone64 3GB. Running beta1-20201104 on micro sd card1) Calls work but volume is low reported by other party on call 2) Have external headset: sound great on music over web when selected as sound output. 3) External headset not recognized as sound input/output during phone calls when headset selected as sound input/output. 4) When running beta2-2020114 on eMMC card, Firefox crashes scrolling on large web pages: higher frame rate in combination with very fast network IO at this site appears to crash Firefox within seconds. Great product. Looking forward to ongoing improvements.

I've noticed the Wifi sometimes doesn't working right.  I first noticed this with the Manjaro ARM 5.9.8 kernel.

When the wifi is "bad", it still works, can connect to a network, send and receive packets, etc.  But the packetloss is about 7% or more, which is really bad.  Very noticeable with ssh as there are constant hangs.  Web browsing one might just think it's slower than normal.  When the wifi isn't in this bad state, packetloss is effectively 0%.

There appears to be something that happens when the wifi chip is initialized that causes this.  When this happens the Wifi MAC address is different.  Good state, I get one address.  Bad state, it's another address.

Here's some the kernel log messages when it's GOOD.

I recently purchased a RockPro64 & Roshambo case, and I installed Batocera Linux on it and enabled the case, everything seems to work but the RoshamboPro kit seems to have a problem when inserting the SSD on the board. 

When I insert the SSD into the board, the unit behaves erratically, some of the behaviors I have witnessed include USB panel in front of the unit stops responding, fan stops, SSD is recognized momentarily, top buttons (Power/Reset) stop working and sometimes the LED 706 inside the unit will blink. After removing the SSD, the system behaves normally.
 
I have rules out a problem with the SSD (It works fine when connecting to other machine) or with the RockPro64 USB3 (when I connect the SSD directly outside the case, it works), but I don't know if it is a problem with the cable connecting the RockPro64 to the board or the Roshambo board itself.

Anyone has experienced similar issues? Any known workaround? 

Thanks