@circ no, it seems it isn't an easy task. Please see https://forums.ubports.com/topic/1206/what-are-the-changes-in-releases

@marathon2422 guess we should have read the info on the app upgrade

This is unfortunate. Thank you for your swift response!

Thanks for your help. So, I will install a pi vpn and hole.

@pulsar33 @dad_and_alive now ti has only the a) feature, but feel free to report an issue on its github page to add these features

done! work nicely

It has nothing to do with pulse-audio. It is the hybris module for pulse-audio, which is maintained by the Sailfish (Jolla) developers. For this feature to work, that module must have the support. My suggestion would be to take your issue upstream to them.

I am seeing the same as @Marathon2422 and @3arn0wl on my Nexus 4 (mako, 2018-W48) on the RC channel. I recall seeing this behavior in the past as well, but the timer goes off after the correct amount of time. (So the alarm in the picture went off 57 seconds after I took the screenshot) [image: 1543355463299-screenshot20181127_174836132-resized.png]

https://wiki.archlinux.org/index.php/bluetooth#Pairing => bluetoothctl can be a very nice tool for debugging BT problems. You can pair/unpair and interrogate devices etc. I would give it a try whenever there are BT problems.

@minkiu said in Is it possible to flash from TWRP (with .zip file)?: While I managed to get adb working, once it boots into fastboot it just won't detect it I had something similar on opensuse with the AppImage installer (would affect deb as well AFAIK). And the cause there was that I had adb and fastboot in /usr/local/bin. But when run with sudo (explicitly starting the installer with sudo or letting the installer use sudo internally), /usr/local/bin is not in the $PATH. And the command to detect if the phone is in fastboot mode ignores the custom paths you can specify so that doesn't help either. So it might be worth a try to either place/softlink adb and fastboot in /usr/bin or adjust your system-wide sudo config to also include /usr/local/bin (or wherever you have installed adb/fastboot).

@bf you're welcome

@ckonstantinos I found RR-N-v5.8.5-20171212-m86 worked very well. never tried dual boot. much prefer Ubports now ,, it is becoming a much more polished/smoother OS, and more apps as the days go by

@marc_aurel https://forums.ubports.com/topic/1676/development-testers-for-anbox/125 Just for info this is the main anbox thread.

I'm replying to myself here to stay within the confines of this topic - but I've been beating my head against the wall on this one... Basically, my ongoing issue with convergence on the Meizu Pro 5 (on 16.04/devel) is the "fuzzy" resolution using aethercast - and I know that it's purely down to the resolution being set in aethercast/src/ac/basesourcemediamanager.cpp to 720p and not 1080p. I scavenged an old laptop today, installed Ubuntu on it (I'm an Arch Linux user by default) and was trying to cross-compile a UBports xenial version of aethercast to upgrade the output resolution to 1080, as per this patch: https://launchpadlibrarian.net/267505693/p1.diff However, try as I might, I can't past these errors during cross-compiling: Get:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease [247 kB] Err:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 I've tried importing those keys - goodness me, I have - but to no avail. So, in a big shout out to @mardy (who is maintaining ubports/aethercast), is there any chance that you might be able to add these three lines to the code and recompile in the near future? The patch worked wonderfully on 15.04 and I briefly (before moving to 16.04/devel) had a crystal clear 1920x1080 UT desktop on my external monitor. Or is there an excellent reason that the 1080 isn't included by default? It seems a little odd, as almost all external monitors are at least 1920x1080 now - as I mentioned before, I had to trawl through our department's old IT storeroom to find a ten-year old monitor with a native 720p resolution - which is seemingly the only way to have crystal clear resolution using aethercast in 16.04/devel! I really appreciate that @mardy does so much for the community already - and I know that there's likely so many more important issues to deal with - but it seems a simple change to the code and would make for a wonderful early Christmas present. Or a late Thanksgiving one for any North Americans on the site

It seems, that UBports is a diva It seems, that the installation has been successfull, after I hold my FP2 in the hand and watched "her" installing. [image: 1543074408861-20181124_164233-resized.jpg]

@advocatux Many thanks for your support.

@ellypsis yes, as only a few repos have been moved for now, I suppose the people doing the move are still thinking about the best way to communicate it. On the other hand, in the main page of every repo moved there's a warning. You can see an example of that at https://github.com/ubports/music-app ("Moved to GitLab https://gitlab.com/ubports/app-dev/mu…")

@cunotj no, you aren't missing anything. For device models like yours it's better to use https://open-store.io/app/com.ubuntu.developer.majster-pl.utorch

@lakotaubp @Marathon2422 thanks for your help. This morning, I tried several things like selected a provider in the APN settings, and then the phone was able to connect to a network. So now it works well! Very cool! Last think: it cannot receive mms without data on, which is also the case with my BQ E5. It worked with the Firefox OS and previously with Ubuntu Touch at the really beginning. Do you know why? With 50Mo per month, I use to let the data off, but in this case, I don't know if someone send to me a mms, no notification, nothing, nada...