It's probably a terrible idea to make this thread, but I feel like I should voice my thoughts. I'm imagining I'm going to get a lot of hate for this.
And please understand, I love the PinePhone, and I want nothing else but for it to succeed, but I don't like what I'm seeing on the software side right now.

I'm disheartened and concerned at the glacial pace of PinePhone software development, and I'm deeply surprised and disappointed that an actual Linux phone with shipping units isn't getting much, much more development love. A new SBC, sure, makes sense. Limited appeal. The first actual shipping Linux phone? Cmon.

I was always afraid that the PinePhone would end up as another poorly supported ARM board with half broken drivers. It's starting to look like that could turn out to be the fate of this device after all. Bringing back horrible memories of FriendlyARM SBCs.

I've wanted a phone that could run Linux since I was just 13 years old.
Now I have it, and call audio still cuts out, the phone won't always wake from sleep on incoming calls, I get duplicate texts out the wazoo, the screen flickers on wake among other issues, it's just tiring. I'm currently trapped on a months old kernel without proper wifi support because anything newer is unusable in multiple areas.
You'd expect progress to be visible, but with everything fixed, something else breaks.

I don't expect the UI to be polished, or for MMS to work, or for Anbox to run, or even for backlight control to work properly. I just think that after this many months, we should have the core functionality of a 2003 flip phone at a semi-stable place. Instead, I have to reset the modem several times a day because call audio will quit and outgoing calls disappear with no way to hang up, and some SMS messages just never arrive, ever.

I've done a small amount of work for the PinePhone, writing pplockd and patching kernel drivers until I get them usable in some cases, but I have contract work obligations and poor health, and I'm not too knowledgeable about the kernel's codebase or physical hardware interfaces, so it's hit and miss. I started writing a better calls app, then ran out of time to work on it.

I wonder if everyone else is having the same problem. A desire and ability to help but, no time or energy to do so? I suppose that's the curse of capitalism at work.

I wish Pine64 had the funds to hire one full-time experienced kernel developer, as that's what's really needed imho.

Thoughts?

I'm not sure how this happened. One night i was trying to figure out a way to fix the fact that the small font was bothering my eyes. I don't recall placing any changes that night. I woke up the next day to the increased screen. I would post a picture if i was on that box. Please any help would be so appreciated

After a recent update I have an app on the desktop called Image Magick. Looks like a cool retro app from windows 95. Anyway, I have no use for it personally and I cant find it or remove it from the software manager. I have tried both sudo apt remove and sudo apt purge, neither seem to work. The app is still functioning after removing / purging the imagemagick via the terminal. Even after a reboot. Looking for advice on how to remove it and also to surface the idea of a QOL improvement by allowing the user to remove apps similar to how its possible to mark an app for "favourites". Might be convenient if pressing and holding your finger on an app brings up an option to remove it.

Hi,

Can you verify what's wrong with my Rock64 - 1g:

If I flash with "u-boot-flash-spi-rock64.img.xz" - it boots LibreElec and other Linux distro BUT stops booting android (both from SD card). In this case, Linux boots from USB too.

If I flash with "u-boot-erase-spi-rock64.img.xz" - it boots Android 7, 8 & 9 BUT stops booting LibreElec (both from SD card).

What's the solution to boot both?

Thanks in advance.

I’m looking for a good open source forum software. Is the forum software of Pine64 open source, and can it be downloaded somewhere?

I just got my new PineTab.

I'd like to get gcc running from the shell.

pacman does not seem to be available.

any hints appreciated on how to more ahead.

I am currently using the Pinephone CE 3BG edition with the current Arch|Phosh build.  It is using Freedom (Shaw mobile) in Canada, and calls, SMS and data all work, despite having to reset and reboot regularly. However, once I move off the fairly limited Shaw cellular network the phone never roams over to another network, of which there are two big ones in Canada, Telus and Bell.

I know many people have to manually connect to their network so I don't know if I am being a little hopeful but....

Questions:
Is anyone using the pinephone on Telus or Bell and did you have to do anything to access the network?

Is roaming part of the modem's responsibilities? Or is this a current software limitation where roaming
information from the network provider is not being used or stored yet?

Is there a manual way to provide roaming information or configuration to the modem?

TIA
LF

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-10-06-TMobile.html
           

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


Notes: The ability to connect to a cell tower is not on this build. Error is No voice-capable modem available. Because of this all calls and texts fail. In other news the camera app (Megapixels) crashes immediately. We still got a long way to go.

Summary: 
Other than the limited info on the Wiki page, what are the plans for PineCube information? 

Detail:
Since the developer-edition PineCubes are apparently shipping (at least I have a tracking number), when will some dedicated information area be set up?  So far I don't see any resources other than the short Wiki page.  No Forum and no channels listed on any of the other chat groups (IRC, Discord, etc). 

The cube is a very different device from the other Pine offerings, so some detailed information up front would be very helpful, especially for a device that is " aimed solely for development purpose only and not a ready-to-use end product". 

If units are actually in shipping, it would be nice to have some useful centralized development info before they actually start showing  up on doorsteps.

Currently, the wiki page only describes getting and building the BSP, a process that I'm still trying to get to work (not finding the arm cc1, which is there, but I haven't found the right place to fix the paths in the ... very ... convoluted Android build system.  I'd really hoped there would be a pure-linux development path that didn't have to deal with an Android BSP, but I've learned to live with disappointment.

Hey guys just ordered the pinetime dev kit with standard shipping (no courier service) do you have a rough time of when it will come? and will i be able to stick the back of the watch on without using glue?