@mariogrip said in Move from Github to Gitlab?: Hello everyone! So, with the resent news about Microsoft buying Github https://www.theverge.com/2018/6/3/17422752/microsoft-github-acquisition-rumors the question have been raised to me if we should move to Gitlab. We will for sure talk about this in our Developer meeting today, so I decided to post this to see what the community things before making a decision. This has to be an Developer decision, but at the same time we do bug reporting on Github too so community input is extremely important. So please give your input on if we should move or not. To move to Gitlab will have no major drawbacks, we will only gain extra functions like direct CI on Gitlab. Gitlab has all the existing functions we use on Github. Gitlab is even opensource which is a big plus! (github is not opensource) Importing will also be no extra job, Gitlab has already automated tools to import everything from Github (issues, pr, wiki, repos etc). And for infrastructure using Gitlab is no problem plugins etc for Gitlab already exists (https://jenkins.io/doc/pipeline/steps/gitlab-plugin/) So from my side there is no reason to not use Gitlab. vote here: http://www.strawpoll.me/15829621 I myself strongly dislike this, and do not trust Microsoft, so I have moved all my personal things to gitlab! Also the irony asking someone to create a bug report for our project on a Microsoft platform is weird. What I still don't understand today is why they didn't make a real switch to open-sources. The fact that they changed to the e.v. club https://codeberg.org in this form

@Lakotaubp did it work? I've got a FP4 with 24.04-1 daily and would love to get VoLTE running.

@cibersheep Well I suppose this will need to be a one step at a time kind of thing. Once a half decent guide for one language is set up then surely it shouldn't be too much trouble for people to translate it later.

@applee Oh yes you're right. Now I see what it is... Thank you. So I confirm there's no kind of such a Led working on Redmi Note 7, UT OTA-16 Stable. Btw, there's no charge indicator on this device yet. Nothing's shown on the display when USB-C cable is plugged in, but battery does charge correctly anyway.

@Charly I can only see SD cards connected via USB, not in the internal reader

@moncon - No worries! Thank you so much for the detailed and encouraging response. I just ordered a CC for Christmas and will surely install Debian and UT now with your recommendation. By the way, I was running UBports UT on my Pixel 3a XL and digging it until the cell network modem died (FYI: The modem hardware had issues before UBports UT install). Anyway, hope my CC wasn't manufactured and assembled on a Friday Thanks again. Cheers!

The Indicator Upower now supports battery charging limit on MTK and other devices - don't forget to reinstall indicator if this feature didn't work in older releases.

@alan_g it sure is. Now that the issue is public though, it makes it even more important to release OTA13 to bring the patch to stable users.

Oh well, you will be successful.

@3arn0wl Well, it's not decision, is a recapitulation of the ideas we have been putting here but: we decide how we want it to work we are tied to «what is possible» to implement all in the case that we start implementing it

@flohack I have had the NetworkManager problem for a while - since ~202012 IIRC (can't remember the exact version - sorry), but the SSH and cellular problems are new.

@moem Thank you, after some time using i might say that it is quite awesome, yet to try sim card capabilities

@cpb I don't think that is feasible. The edge gestures are system gestures. In-app gestures are something the app can do if they want (but it can't be from the left/top/right edges, only the bottom. Changing to what you suggest would be untenable, requiring every app developer to change their apps, and a massive overhaul of the whole system.

@kugiigi Yeah, the dock works on Manjaro phosh for both usb mouse/keyboard and external display, so I know it's not the dock. I messed around with mounting the root filesystem as writable for a bit and apt installing a few things, as initially I was not able to get libertine to work, so I'm going to try flashing a fresh dev image and see if that helps at all.

@flohack I've successfully installed the OS on the Pixel 2. I'm getting a lot of touchscreen problems though, like double or ghost touches. Shutdown seems to really power off the device though.

@franzm You're welcome, I'm glad the gps is working, enjoy your new mobile with Ut. Regards...

@lakotaubp Sorted. The phone was not booting to recovery mode by pressing vol down and power. So tricked it by failing the upgrade from settings which took me to the recovery screen. The installer worked from there with wipe data and reflash partitions not selected. Data intact, now at OTA-23 and happy again Would the 'un-brick' my Volla X route be to go back to the stock software given above (on halium9) and then install the latest OTA from the installer with the 'flash partition' option selected?