Hi there! I am trying to set up communication between an Attiny85 and my RockPro64 over UART (running Armbian, kernel `Linux rockpro64 5.7.15-rockchip64 #20.08 SMP PREEMPT Mon Aug 17 00:26:28 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux`). The issue is that I can't connect to the serial port:

• Battery positive - Attiny85 pin 8
  
• Battery negative - Attiny85 pin 4 - RockPro64 ground on GPIO pin 6
  
• Attiny85 pin 6 (PB1) - RockPro64 UART4_RX on GPIO pin 21 (connected through a 1K current-limiting resistor)
  
• UART4_TX is not connected because currently I only need unidirectional communication
  

I'm interested in supporting braille input on a PinePhone.  The datasheet contains a lot of useful-looking information on the hardware, but (of course) it says nothing about software APIs for the touch screen. Assuming that I'm running Linux (e.g., Mobian, pmOS), where should I look for this information?

Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.

Results: mobian/2020-08-27-Verizon.html
              mobian/2020-08-27-TMobile.html

[b]Conclusion: OS is not Ready for pinephone to be daily driver.

Notes: Today was an interesting testing day. MMS is still not working. The camera is still lagging. Call quality varied between TMobile and Verizon. Call quality of the microphone on TMobile was great. Clear, no echo, no problems. Call quality of the microphone on Verizon is very sensitive. Louder then necessary. It made the call experience very poor.

Now that I have recruited some help with Mobain from @AmazingNutria I am considering beginning some daily manual QA on this OS.

First I have a few questions:

1. Is this OS ready to even consider for a Release Candidate yet?
   
2. Has anyone seen any progress on this OS since they started tinkering with it?
   
3. How many features are available on the dev builds? 
   
4. Is this something people might look forward to?
   

Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.

Results: ubports/2020-08-27-TMobile
              ubports/2020-08-27-Verizon

Conclusion: This OS is not ready for the pinephone to become a daily driver.

Notes: Inbound texting still not working on Verizon. Issues with outbound 3G texts in TMobile. I have noticed that I am unable to change the MP rating of the camera. Since this feature is so new I don't think it is appropriate to introduce a test case around this. Didn't even attempt MMS. Speakerphone still not an option.

Known Issues:  4G calling is broken.
                          Locking issues.
                        
If you want to help contribute I suggest logging into gitlab and commenting on these issues. Also, ubports has forums that they read from separately. I find them hard to navigate personally.  But you have the information to help influence a change. That is all. 

So maybe I am missing something.  But where is the work being done? where are the change logs?  what is being worked on so we are not working on the same thing someone else is already addressing.


the WIKI for Pinephone Software Releases is a good resource but there should be links to the discussion pages / issue pages / change logs  etc...

there doesn't seem to be much going on here in the pine64 forums and everywhere else I look seems to be lacking in current information.
twitter, matrix and discord seem to be ok but even those are also lacking in actual development discussions.

do I need to be invited to a secret club to be involved?  

Some applications do not keep the screen on and the screensaver (or suspend) kicks in. (Video players such as mpv come to mind). In this case the little wrapper app “coffeine” comes in handy (source). Download the latest .deb file and install it with

Until OTA build 166 that is...
Maybe this is just a step towards reversing tje mirror image?

Hello All,

I got my hands on some 2GB A64+ boards and noticed there were no Fedora 32 or CentOS 8 images so I decided to throw some together.

These images are using the armbian 5.7.15 kernel and firmware. I have bundled them into rpms and installed them into the base images.

CentOS 8
CentOS8-Minimal-202008.0.pine64-plus.img.xz
CentOS8-Server-202008.0.pine64-plus.img.xz
Username: root
Password: centos

Fedora 32
Fedora32-Minimal-202008.0.pine64-plus.img.xz
Fedora32-Server-202008.0.pine64-plus.img.xz
Username: root
Password: fedora

Debating doing some with a desktop environment installed if any interest is shown. If you run into any issues, please post there here.

Cheers,
Mike

Okay Ubuntu touch devs. I've tested the field. Mobian, Arch, and Manjaro are way ahead on functionality. But UB touch is by far the nicest, snappiest, crisp distro for mobile. Once complete this will be my favorite! But with others achieving daily driver status, what gives? Some improvements in the last month for sure by i dont get the order of priorities. Most of our feedback here doesn't seem to be getting applied. Im sure one or 2 more OTAs could implement everything where the other distros have surpassed. Is it just that there's less activity from UT devs on this forum?