I don't know whether it's just my unit, or Tow-Boot and Arch Linux ARM, but it tends to happen that I plug in my PPP to charge over USB and it won't charge until I re-insert the battery.

Yes, I suspended in the meantime, and I was made aware in the #pinephone Matrix that it causes the battery level to be incorrect.

Is this a known issue? Does it indicate a hardware fault?

Hi!
I have bought a Rock64 for running Netbsd and downloaded pre-built, bootable 10.0 image from https://nycdn.netbsd.org/pub/arm/ for this board.
Then I verify, gunzip and dd the .img file to sd/emmc, insert card and power on. I get a green power light a red st.by and a white pwr light and that's it. Ive done this the exact same on pinebook pro and rpi3b many times with no issues. Just works. I also tried the "daily" but no noticable difference.

I have successfully booted an image from armbian just to verify the hw is working.

Even tried the 9.4 image so now i'm running out of ideas. Btw also tried the dd u-boot to sd but it should not be necessary with these images as far as I know...

Anyone using these images who could help me out here?

I have a pinebook pro with a rather old version of u-boot on it (it says U-Boot 2017.09-04094-g969502b-dirty), and I was thinking it would probably be a good idea to update it.

What version/versions are known to work, and are there binary releases available to download, or should I compile it myself?

Hello,

I am evaluating if PineTime would be a good idea for my 7 year old son. He might have some light ASD.

• He gets reassured by knowing the current time (24h format or analog, not AM/PM)  
  
•  I'd like him to receive a notification for specific moments in time when he should be doing something, repeating for day of week.  
  
•  An agenda view and some notes would also be good, he really needs some knowledge over his own life.
  
•  If I could attach small pictures or specific noises to the notifications and agenda, that would be great.
  
• I want only the minimum of distractions, no games, etc..  
  
• He also tends to freeze/daydream and forget where he is.  I wonder if the step detector could detect this and make a noice to pull him back to reality
  
• I'd like this in Dutch/Flemish
  

My second battery went poofed.  That is two batteries in 16 months.  The original battery lasted
11 months.  No PP for 1 month.  The second "Samsung clone" battery lasted 4 months. 

The second battery acted up a month ago.  I tried moved (recharging PP) from old power strip to
a surge protector and thought that solved the problem.  Now battery is dying.

The first battery, I did USB charging for awhile.  Thought it was too slow and moved to the old
power strip.  Battery lasted longer, but still died.

-----

Can you share your experience in recharging PP?  Does surge protector helps?  Or slow USB charging
is best?  Or what?  Any tip on recharging PP so that battery lasts longer?

Burning a battery every 1/2 year is not pleasant.

Thank in advanced for your story.

Sheng-Chieh

I find it odd that there are essentially *zero* good and affordable solutions for push-to-talk systems.  Everyone just accepts crappy FRS quality since there's not really anything better available.

It would be amazing to have a simple dedicated device with a speaker, mic, 3.5mm port, a tiny display and menu button, and a push-to-talk key.

It could come out of the box preprogrammed with a few ESP-NOW based channels, and then allow you to add RTP multicast paging on a proper WiFi network(Which seems to be what the expensive SIP phones use).

The ESP32 can handle Opus compression, so there should be enough bandwidth for a few repeater hops.

If it was 18650 powered it should be able to last all day, so you could just leave a few around as repeaters, one hop is probably enough for 90% of things FRS is actually good for.


The same hardware could also connect to a smart voice assistant server, act as a wireless media streaming target, or be a wireless doorbell beeper for home assistant.


I've seen a bunch of projects like this, but nothing available as a mass produced, ready to use device.

Hi All, I've ran through this tut https://wiki.pine64.org/wiki/Ox64 and flashed my board. Along the way I enabled the i2c options in the buildroot menu but I don't see "/dev/i2c-0 " when booted. I also don't see i2c kernal msgs (not sure if there should be?). i2ctools is installed.
Wondering if anyone knows what the next step is from there? Is there a device tree that needs to be updated?
Thanks

I'm sure everybody has heard about the backdoor built into xz version.
All my computers are xz version 5.4.5
I just checked my Pine Phone Pro for xz version and it is 5.6.1
5.6.0. and up are infected.
heads up folks because that is the infected version.
I found this on Arch Linux Phosh.
Check your phones immediately because as I understand this your phone can be remotely accessed.
To check your version in a terminal type xz --version

Does anyone have any binaries atinout for mobian on pinephone 1.2?

https://atinout.sourceforge.net/ does not have precompiled binaries for debian/mobian and attempting to compile from source results in a segmentation fault error.

Had my Pinebuds for a year. Along with my other pine stuff I am pretty happy.
However I only use the SuperANC setting because the other two settings (ANC and Ambient) sound pretty terrible, really bassy and mushy. With SuperANC they sound pretty good.
The SuperANC is very quiet though compared to the other two. 
Clearly the hardware is capable of delivering really good sound, but it isn't quiet there.
I am wondering if there has been any work on the firmware to try out different sounds. I can't really see any relevant work in the github, but them I am not really familiar with this project.

Thanks.