@dobey At least WRT the Android-ish kernel underneath, networking is a capability which can be held back. It is not benign to hand out your networking stack to every app; they can use it to slave to a botnet, contribute to DDoS, track your location, pull down and try exploits after communicating your system's apparen config.

@CiberSheep An app loaded from the filesystem should not need "filesystem access". Similarly, an app using a web runtime should not need access to the network at large. I hope this is something which can be improved over time...

Why do most apps in the store need network access? I mean, a game like M vs. M? or Four in a Row 2? Tic Tac Toe? (But not the Mines game, yay!) If the app devs aren't, in general, going to restrain themselves, should we at least be looking at a standard system way to constrain permissions after the install?

@Djhg2000 said in PinePhone:

battery
"Not having a removable battery is a dealbreaker for me so the Librem 5..."

I just went to their own web site, and they clearly say the battery is serviceable/replaceable.
To be clear, you mean you want a phone with an externally removeable battery? Just
click off? I can't remember the last phone I owned which had that.

@dshimer I agree, I was off ubports for a bit because my wife's phone died and she needed (Android, sigh) a replacement quickly, thus a Nexus 5 was used up. But I presently laid hands on another, and here I am back with a daily driver again! This one was, hmmm, like $60, with everything including battery in good condition.

@PINE64 For shipping of batteries, I suggest that you fab a flashlight which uses the same battery. One switch, one LED, minimal plastic case. Then you can ship a battery within a device, national post office regs are satisfied, and the recipient can perhaps crack open the flashlight and use the battery elsewhere.

FWIW, I used pypi.org/project/notify2/ which uses the dbus, worked for my own notification app.

I have a bug unique to the Morph browser. I knew how to invoke the debugger under the old browser--what's the wisdom on this new one? TIA!

OTOH, I just today found a spare OTG USB cable in hand, and tried plugging in a mouse. Which worked very well--hats off to the UT folks.

@libremax said in Making Ubuntu Touch an easy choice:

The development of UT has to be embedded in a long time, several decades in the same way that GNU/Linux software emerged in the 70s and 90s and only became known to tens of millions of users in the 2000s.

No reason to be impatient only to show consistency and determination.

Well, I don't think Linus was doing his thing in the 70's, but otherwise I agree with your sentiment.

Many kept waiting for the thing or decision or Big Business which would make Linux win. But it really just kept being there, attracting enthusiasm and moving forward. It was just suddenly obvious and inevitable.

So I think the project is doing all the right things. Catch up with a shared SW base. Fix the abandoned browser. Over time adopt a new flagship and, yes, set some old supported devices aside (I'm already a little worried about the flawed binary blobs in my Nexus 5). Keep chipping away at what's missing, what's broken--software and docs. If you keep at it, odds are you'll run across things which will make UT stand out. Especially since the big players can make game changing mistakes (I'm watching Google's tensions with the EU and their increasing control of Google Apps with interest).