Patreon is one of the methods to donate that is given on the ubports.com donation page. According to Patreon, 158 patrons are giving $US 1,148 per month to the UBPorts Foundation. Sure, that's not going to pay a salary, but, to me, it is a significant amount of money toward running servers and infrastructure. However, I don't know if that's true, because I don't know what the operating costs are. I am blindly donating because I want to be supportive, not because I am trying to pay an amount that I think the software is worth to me. What are the operating costs? If that was clear, maybe more people would be likely to donate. A graphic popped into my head: a thermometer where the level in red is the annual cost, and the red turns green from the bottom up as donations come in.

The question of charging a fee for FOSS is an old one. It cannot be easily answered. There's a lot of philosophical debate about it in the history of FOSS. To me, FOSS is one of the greatest accomplishments of humanity. A shining knight standing to face the history of industrial economies. I'm just saying that charging money doesn't just slowly smother UBPorts. It's no longer FOSS. It doesn't matter if you charge $US 10 or $US 1,000. It's no longer part of this amazing community of altruistic creators.

Do you want a fee to use Linux? Wikipedia? Every forum and website you use to troubleshoot the problem with that driver that doesn't quite work right in Linux in the latest new bare hardware you bought? When someone posts a solution to a problem in a forum, they do not charge money. They are freely giving their intellectual property. This is all part of this network economy that the Internet is enabling. To me, UBPorts is my best hope for a phone in this economy. I will do what I can to voluntarily give of my time and money.

@beta-break
The core app list includes calendar, but not contacts. The list described here includes Morph, which is not a core app, but does not include an email client, such as dekko.

I realize that there's a lot of work planned here (like, VoLTE), but I think that contacts and an email client should be added. Also, the list of core apps should be re-evaluated?

Thank you!

Finally, I've received the right phone. It is from Southwest Distributors, via Swappa. I should have followed the recommendation of the UBports site and gone there first. I could tell right away because one of the first steps after powering it up is asking about a SIM and giving the option for an eSIM. Verizon models don't offer that.

@kugiigi Two of the Motorola phones I've had use serveral acceleration gestures. For the flashlight it is two hacking motions. Two wrist twists opens the camera.

I'm now on my fourth Pixel 3a from Amazon or Ebay. Every vendor has send me the wrong phone. Wrong model, wrong size (I already bought case and screen protector separately), Verizon-locked, unknown vendor locked. The one I have now is the wrong color, although I don't care about that. From Ebay, it's supposed to be "Factory unlocked". I tell vendors that I want that, plus OEM unlocking. This time, I was able to put my Google Fi SIM card (that I use in a Google Nexus 4) in and activate it. That works, but the OEM unlocking is greyed out. I can't downgrade Android to 9 (step 1).

I haven't been able to find out the model of this (Regulatory Label is blank). I tell vendors that I want a G020G, following the advice elsewhere in the forum, but I can't determine that that is what I have. I'm waiting for a call back from Google to see if they will unlock it or tell me what the phone's status is.

I can't see that it supports eSIM, but from what I read it is supposed to. There's no eSIM IMEI listed or other evidence of it. Is this a clue as to what the phone is?

Thanks for any info you can provide me.

Did you recently buy it? Can you return it? I went through 4 phones from Amazon, Ebay and the site that the UBports buy link goes to, before I got one that was OEM unlockable. Others here have had similar experience. Sellers might not understand what it means. Try to find seller who will check that or at least give you the IMEI number so that you can contact Google Fi support to find out if it was originally sold in Google Store. Those are unlockable.

I already support through Patreon. I encourage that approach. Maybe more visibility for that? As much as I don't like paying middle-businesses, and I personally think Patreon takes too large of a percentage, there they are.

I'm open to other voluntary ways of giving money.

Okay, this is a dumb question that I haven't been able to answer for years. I've used a Nexus 4 for some years, usually in the dev channel. I never notice that an OTA has arrived. I guess that's because they are only relevant in the stable channel. I'm probably wrong about that. You see, I'm ignorant of a lot about OTAs. How do I know which OTA I'm on and how do I see that I have received one? I can't find answers here, Wiki, general web searches. Sorry to bother with such a trivial question.

I'm interested in exploring working on this, so that CardDAV can be configured via the system-settings and more. I don't see it under the system-settings-online-accounts repository in Github. I've run Mobian on my Pinephone and all the usual Nextcloud services are available in the settings there. I guess the code, even the language, could be pretty different in this case between Mobian and UT. Still, I'd like to explore that. TIA.

@tonton_ Thank you for this work.

LINMOB says that there are improvements to CardDAV. I wonder if they are referring to your work here?

https://linmob.net/weekly-update-23-2024/

No one has another way to check if QT6 is installed?

p.s. I ask this because when I reinstall without wiping, all the apps I've installed are still there.

@wally
If I do a reinstall of 2.x daily (on a phone that is in list 2.) using the installer in order to get the QT 6 Beta AND I do not select the option to wipe, will it preserve the current 1.x version of Morph?

Are there libraries that I can look for using a shell to verify getting the 2.0 Beta (or its daily equivalent)?

Thank you.

Okay, I am going to run 1.x RC on my OnePlus N10, run the gsettings command as above, and wait for notification that 2.x is available.

If our phone is on list 2., how will we know when the new 2.0 is available? By staying on the 1.x RC channel? I’ve been assuming that the upgrade to 2.x will require a reinstall using the installer with a wipe because the partition size changes.

@pparent
I haven’t been able to install 2.x. That error and the log shows it runs out of disk space

Yes, it is in the list of phones that have to be fixed in order to remove it from the list of that will not receive updates. The n10 maintainer has just fixed it.

I’m optimistic that the n10 will start getting 2.x updates installable through the standard installer. Hopefully soon.

@wouterx
This is an aside, but there are a number of phones that do not have enough space to install 24.04-2.x. Would your yaml change work for them? I wonder. Where is that yaml file? How did you decide on that new partition size? Where does it take the space from to make that partition larger? Thank you.

@gpatel-fr
That depends on the phone model, right?

Or is there a way to reset my Oneplus N10 back to a configuration that would let me install 2.x? Ideally without having to reinstall Android.

It doesn't work for me. I haven't been able to install it on my Pixel 3a or Oneplus N10. Both fail the automatic update that occurs after the install when using the installer. Both run out of disk space. 1.x installs fine.

@arubislander
I bought this phone because I'd read about patches for MMS available through the QA Telegram channel. So i originally installed 2.x over Android. I immediately had out-of-space issues when i tried to install the MMS patches. Lionel said in Telegram that they routinely remove unneeded packages in order to make space under 2.x for QA tests.That shouldn't be necessary in order to contribute to QA.

So, there is a known problem with space. My guess is it needs to be expanded. I just saw fredl talk about porting Halium 12 to Pixel 3a and expand the size of root. This looks like a general issue.

There should be a mechanism in the installer or while running UT to free up space. Reinstalling Android and the UT again is a burdensome method. Anyway, that would just get me back to where I started, running 2.x without enough space to do QA.