Posts made by Fuseteam

@CatWithUT hmmm no hub, not sure then what it could be

@CatWithUT said in BUG: USB-OTG Hard Crashes Phone:

@Fuseteam That is what beta tester are for

hah! fair. I stand corrected XD

@jojumaxx said in I am about to give up and leave:

There's Libertine and Snap support which don't help with the mobile experience. If I want to have a tablet or laptop, I use a tablet or laptop.
Convergence is good as a bonus, if the basis works. It's called Ubuntu Touch, but touchable is nothing. Don't forget, that this is about phones.

I am just a Linux user, but UT is the only system I encountered yet, that doesn't allow me to use a package manager freely. Everything would be perfect if that was possible...at least I guess so...

These two concerns contradict each other

on one hand you feel that snap support is missing the point, on the other hand you feel that install apps with apt would solve the app issue....

Just as apps installed with snaps are not "touchable", apps installed with apt are also not touchable. The snap support is meant to address the issue have with the inability to use apps.

If you have apps that would well on droidian via apt, packaging those as a snap would bring it over to ubuntu touch, that would be up to the developer of that app however.

It is the same with banking apps— we can't have banking apps, if the banks behind those apps don't port them over to ubuntu touch

The outdated browser is a big issue yes, there are multiple effort attempting to solve that, the current rebase to 24.04 might help eleviate that to some degree, alfred's mimi browser is a work in progress that will likely solve the issue aswell, once finished i suspect it'll replace morph altogether, there is also ufirefox which is PoC repackage of desktop firefox with all usability issues.

If Ubuntu Touch doesn't fit your usecase, but other mobile linux distros do— perhaps you could outline those usecases. I would be particularly interested what apps you find useful on droidian that you would like to see on ubuntu touch, perhaps we can get them installed with snap or maybe repackaged for the open store

The main idea here is: The OpenStore would not need to process the the payment, because it is done by multiple third parties (people who mine Litecoin or who have Litecoin nodes) and the OpenStore only provides an address and looks if there is anything transferred to that address. But the developer would probably need to take care of legal matters as taxes when he receives Litecoin to his wallet or later transfers them into "normal" money.

And just to be clear: Litecoin was chosen here as one of many possible solutions, because it works and is well established. I could have also chosen Bitcoin, but the confirmation times and the fees are lower with Litecoin.

The challenge here then becomes, if someone pays and wants a refund because they are not happy with what they get, where do they go? the first where they will go is the ubports foundation, then the openstore team, by the time they reach where they should be— the damage's already done.

@CatWithUT are you possibly connecting it with a dock of some sorts?

Also might be a bit early for the fairphone 5 xd

@ancientsounds said in USB-C headphones on OnePlus 6T:

Further progress, using Pulse Audio, especially pacmd

To switch audio output to the USB headphones:

pacmd load-module module-alsa-sink device=plughw:1,0

Most importantly, to switch back to the speakers when you're finished with headphones:

pacmd set-default-sink 1

this seems to work on the fp4 too

@fakeshell yeah no easy task, and we'll migrate to systemd anyway xd

@fakeshell snaps won't work, cause no systemd. Flatpak has no osk support atm, among other missing integrations including portal support

@applee the thing is some halium operating systems don't use ofono, they use modemmanager iirc xd

@applee ah i need to read more thanks. tho i still don't know if "aiming to standardize middleware to talk to android daemons" means it's a part of halium or not

@applee i'm fairly certain both the kernel and ofono are outside of halium, but i can't say that with absolute certainty. i agree the best way to understand it would be to try porting yes. i too wish i could make time for it

@applee thanks for the links, i've been following the groups as well, and now i found a short description on telegram that made it click for me:

Halium is basically custom version of Android build specifically to run services that speaks to Android hardware

edit: i just noticed i already posted that did that description not suffice?

edit2: ok so i found an (older) image of the diagram florian showed

my current understanding is that the bluebox is "halium" although in florian's diagram the bluebox is considerably larger hmm

@josele13

What kind of companies would be interested in an OS that doesn't have a locked bootloader or unencrypted phone rom?
In those companies will they see that UT is easier to use than android?
Do we have all the android options to be attractive?
Will these companies be able to use our country's banks or government apps?
Will the employees of these companies be able to make video calls?
Will they be able to talk from the car to another employee via bluetooth?
Will they be able to pay for food at the bar from their mobile phones?

yes these are important questions, but we must've forgo what we can do to make it more attractive
for example if there's a missing app, what can we do to convince the app developer or the company behind it to support Ubuntu Touch. if there's a missing functionality what can we do to fix it whether that's ourselves if we can program or by attracting a developers with the skills.

so rather than "what makes it attractive to companies?" the question becomes "what can we do to make it attractive to companies?" and by extension "what can we do to move Ubuntu Touch forward?"

@mardy niiice, thanks for your work i'll test it out too~ sadly my battery is rather old to be a reliable battery test and my touch screen isn't in the best state either but i'll be sure to report any other issues!

honestly i don't think we should only focus on what users can donate. there are more ways to contribute, as already mentioned, including volunteering to lessen the load on "the core team".

As Dalton mentioned in the last Q & A "i've seen the mentality change from 'what can we do together?' to 'what can the foundation do for me?'" "foundation" can also be replaced with "the core team" the meaning is the same. If we want to grow we need to adopt the mentality that brought us this far which is "What can we do together?" and there's more we can do that just technical things like contributing code or donating money, we can also promote the project and perhaps interest companies with the same value to become sponsors, like volla, smoose and pine64, or ways to collaborate on the system. The field of ways we can help is huge, let's utilize it!

@cliffcoggin hi, i'm way late but i found a nice short explaination of halium that finally made it click for me. i'm posting it here because perhaps @AppLee might find it usefull to add it to his short description:

"Halium is basically a custom version of Android build specifically to run services that speaks to Android hardware"

as these services make use of Android libraries halium also uses a wine-like "compatibility layer" to load those libraries in Linux called "libhybris"

as a closing note i would like to encourage you to not be discouraged when you feel like you don't understand much. i can tell you that few of the regular contributors understand the entire system completely. even the most knowlegable contributors started with zero understanding of the system, nay even the devs at canonical each "specialized" in specific parts of the os, while not knowing much about other part

@opolork do keep in mind that the hosts file is readonly for a reason. any changes will be lost after an ota update, uAdBlock know how to restore it changes, but it might become tedious for you to restore your changes

@dpitti wasn't the keyboard so large it covered your entire screen?

Hiya @keneda, i'm not sure if i understand your question.
i can only make assumptions

• if i assume you mean if i'm compiling "desktop applications" to make these clicks, i'm not. what i'm doing it using apt to download packages from the ubuntu repos, extracting them and the repackaging them as clicks, all using a bash script.
• if i assume you if it's possible to compile desktop apps from source to an usable ubuntu touch click, yes that's perfectly possible. we could perhaps do that to gtk itself, maybe that will fix the keyboard issue. i've been testing a couple of environment variables to see if it's some kind of path it's not reading correctly but so far i'm only hitting dead ends. but i'm trailing off, yes it is perfectly possible to recompile desktop apps and package them as a click, it could possibly even overcome some of the limitations i've encountered so far

ok i think i generalized the firefox repo to the limit;

• the meat of the builder is in builder.sh.
• the template files are placed in the correct location with the specific name while the environment for building is setup with prebuild.sh (hmmm maybe i can move that to build.sh)

• the package specific stuff are saved in pkg.d

• the actual package to build is specificied in clickable.json any package in the ubuntu repos can be specified, no command line apps tho those won't magically launch in the terminal (i ain't a magician sorry :P)
• package maintainer info can be set in manifest.json, the package name will be set with prebuild.sh
• apparmore permissions can be set in apparmor.json

Limitations:

• as mentioned earlier it needs to be unconfined due to needing xmir, as such only the xmir branch has an actual working click, the master branch would launch on wayland but this particular version has broken wayland support, if the package has wayland support confined may be possible
• any package which has an all package as a dependency will fail to build, cause i'm a noob
• no command line apps! we have crackle for that nudge nudge
• no touch (so far), no OSK (so far), no content hub, no media hub
• no per device scaling, currently scaling is set with the environment variable GDK_DPI_SCALE=2
• i have no idea how to handle the above 2
• i also have no idea how to handle settings schema's at all