@PINE64: You guys are amazing! I think the transparency, how you develop the pinephone, and how you took all the different communities with you on your path, it is quite exemplary.
Well, that seems to me quite unfair. Volla invests money and time in that device/project. If everyone would buy a Gigaset GS290 because its cheaper than, no company/startup will try to bring another device to UT again. We should hope that they succeed instead that Volla will be able to start another project with UT someday and other companies/start-up will follow.
there is one thing which seems to me a little inconsistent and in convenient.
If you want to go "back" e.g. in settings, you have to reach somehow the "back"-button across the screen.
In my opinion the ui would be more convenient, if you could just swipe from left to right to go back - especially if you use your phone with just one hand.
@Stefano I hope that. It would be a reward as well for the hard work they have done and the time they have invested.
I think the Xperia X port is worked on more than a year now. Thats quite a lot of time he put in it I imagine.
I learn python at the moment. Maybe a can participate with some apps someday.
@DansLeRuSH Well, thats acutally known. Gigasets manufactures in Germany with a high degree of automation. ~ 60% automation. ~ 40 % manual labour without typical assembly lines.
Does Jolla upstream their drivers and stuff? I'm guessing that would help.
Did you look here?
I dont think you need LOS or TWRP support. The vollaphone guys - I think - did it without as well. You should talk to them.
Furthermore Ubports work on Halium 10 as far as I know while Xperia 10 ii & iii run on Android11.
That's huge! - at least for me. I look for a successor of my Xperia X (with SFOS) for about a year. Vollaphone, Opo6, FP 3+, Xperia 10 ii but none them really convinced me to retire my Xx.
I never have thought about spending 800 € for phone. For this one I would.
@flohack I don't know whats the "right" or more sustainable way.
KDE has dropped halium. Mobian I think just want to support mainline devices. How do they want to engage this issue?
There are some people who work on mainlining the OP6(T). I think this device would be a great device for the next years. SoMainline work on mainlining Sony devices. Wouldn't that be an alternative?
every new Android version comes with a lot of changed and new stuff, and it gets harder with every version to make clean builds.
If it gets harder, which I assume you also notice in working/coding hours, is halium sustainable concept for the future?
I am quite curious how many they have sold in total.
And : not everyone has 350€ to put in a phone.
Well, you can buy another device and put UT on it. Why it has to be the GS290?
They have spent time to build VollaOS, an UT and SFOS port. Why do people except often that other people should work for free?
I think it's great (for UBports) that you can a device, which already runs UT - without flashing etc... There are people out there, who don't want to get into that stuff.
And what's actually important for me. I want to have a device which gets supported properly. Most ports never get "finished" or abandoned at some time.
I look for a new device quite some time and for me one of the most important reason for the decision is how well a device will be supported. Therefore, there are at the moment just 2 options. VollaPhone or Xperia II with SFOS.
Its just sad, what people are willing to do, just to save some bucks.
@pavelprosto For me the Python isn't the part I am worried about. There are lots of books about python. What's still vague for me is what comes, when you have written the python file(s)? You get lost very fast ... Qt, qml, pyQt, QtQuick, pyOtherSide ...
I know there are lots of YouTube tutorials about Qt / qml, but what I have noticed is, that there mostly unstructured and for me personally not very helpful.
Your examples on the other hand are very helpful because you can see how - a not very complicated - qml file looks like. When I start with qml I will most likely need them for my app.