just an update: my battery went empty and after I booted the phone the indicator was back again. (problem gone) Not sure what solved it, maybe the toggle of the rotation lock switch in system settings followed by a reboot...

Hmm few comments: We did not change anything that I know that would make necessary these huge steps to get the db working again, I totally dont understand what happened here. Backup/Restore of my data worked when wiping several phones... BR

Hi,all, i am from china, i have an android pro5, i flash it,Now power by ubports ubuntu touch, It is my importance phone, i love it. it like a mini computer, very good! i hope ubports team continue develop Xenial on Meizu Pro5, Forgive my poor english, Thanks All!

I have been looking for something like this. Is there an official forum app out there that we can download either on out UBPorts or andriod devices?

What version of the OpenStore app do you have? Also can you access this api endpoint from your phone's browser? https://open.uappexplorer.com/api/apps

@wgarcia said in Flashlight/torch for Nexus 5: @vandys It works for me, I'm using the development channel in the Nexus 5 Interesting. Probably a permission problem, then. I'll check it out further when I can afford to have my phone interrupted. Thanks again.

That works, GREAT, thanks

Everything looks ok as far as I can tell. The part about not finding the "clickable.json" is just to let you know that it's falling back to autodetecting the project template (which doesn't matter as much when running clickable setup-lxd). You should be good to use clickable on your project now.

I changed mine from recovery just with :sudo ubuntu-device-flash --server=http://system-image.ubports.com --device=turbo --channel=15.04/devel Meizu Pro 5 all data and settings intact

@mlinodasilva I have not such a problem with sound, but other users reported that already. So yes a bug. You can still install some scopes from Canonical Ubuntu store. Maybe not all, but most yes.

@ITwrx I've fiddled around a bit with your script and another one by myself and found a few things: aa-exec /path/to/script.sh or exec /path/to/script.sh will only work (reliable) from the terminal app, at first it wouldn't work via adb. Just tested it again while writing this lines and now it works via adb shell as well however, exec will close the shell when your script is executed, aa-exec or bash your_script.sh will not. (This is just FYI, not related to your goal) If you include the line X-Ubuntu-Application-ID=my_script you can execute it via adb/terminal app using ubuntu-app-launch my_script and this has interestingly different errors when run from adb (WARNING **: Unable to find keyfile for application 'my_script') and terminal-app (WARNING **: Unable to start app 'my_script': Keyfile does not represent application type) respectively. I think this is the actual problem which is somehow related to the Glib key-value file parser. (the type=Application value in the desktop file AFAIK) i think it is somehow related to the Ubuntu-App-Launcher however with my skills this is as far as i can get.... After running the command ubuntu-app-launch my_script a second time (there is some magic going on that makes doing the exact same stuff multiple times have multiple results ;-D) the error changes both via adb and terminal to ** (process:16881): CRITICAL **: Error parsing manifest for package 'my': my does not exist in any database for user phablet ** (process:16881): WARNING **: Unable to start app 'my_script': AppID is empty I hope this may help you or others, if you find a solution how to make the app-launcher believe there is a correct keyfile or whatever the problem here is please let us know! Addendum I just wanted to say that either something with your script or with my phone (Nexus 4 on old Multirom Ubuntu Canoncial 15.04 r602) is strange. I tested with another script i called "skript" that had a similar .desktop file, only with the X-Ubuntu-Application-ID=skript and this always puts out the same error when trying to execute via ubuntu-app-launch skript (WARNING **: Unable to start app 'skript': Keyfile does not represent application type) but for your "my_script" that i placed in the exact same places as you described, the beahviour was on first try the same, then it changed to the error above which seems to indicate that the ubuntu-app-launcher doesn't get the "_" and than thinks the AppID (which is declared in the exact same way as for my skript.sh) is empty.... and if i change the X-Ubuntu-Application-ID=my_script to X-Ubuntu-Application-ID=myscript the "parsing manifest for package 'my'" error vanishes but it still thinks the AppID is empty (by the way, skript.sh is just: #!/bin/bash echo "simple test echo" and the .desktop file [Desktop Entry] Version=1.0 Name=Skript Exec=exec /bin/bash home/phablet/Documents/skript.sh Icon=home/phablet/Pictures/carrot.png Terminal=true Type=Application X-Ubuntu-Touch=true X-Ubuntu-Default-Department-ID=accesories X-Ubuntu-Application-ID=skript )

I managed to resolve this by using the Tweak tool to delete the local data

@Stefano said in No Internet Dependent Apps Work In Desktop Mode: @charlesforson Same on Meizu Pro 5 FRENCH Meme problème avec BQ M10, attends la mise à jour Ubports 16,04. Peut être que le problème sera résoluFRENCH ENGLISH Even problem with BQ M10, wait for the update Ubports 16,04. Maybe the problem will be solved

I had this exact problem this week. I know what caused it for me. I used Tweakgeek to delete de External drive app on my Nexus 5 because there is no SD slot on the Nexus 5 and I didn't want to see the icon anymore. My phone started to overheat and use battery like crazy. I restarted the phone and there was no more network indicator like in your screenshots. Also, for some reason all my unused space started to fill up (with error logs I bet). I updated from the legacy channel to OTA 1 and it didn't resolve the problem. I flashed the phone to OTA 1 and now it's resolved.

@nikhilbhalwankar Short answer: no Long answer: https://wiki.ubports.com/wiki/Release-Channels The Current Channels 15.04/stable This is the channel you should be on if you're unsure of which to pick. It's the slowest-moving and most vetted release channel. 15.04/rc This channel is a good mix between stability and bleeding edge. We will promote builds to rc from devel when they are possible candidates for stable. This channel should not break, but we can't promise as stable as stable. 15.04/devel This channel will break. If you're working on QA, this is the place to be. If you're trying to use your Ubuntu Touch device in your life, this is not the place to be. Nightly builds from our CI server get pushed straight into 15.04/devel. When they are deemed as candidates for Stable (which only happens after we enter a feature freeze), they are moved to 15.04/rc Again, we do not recommend 15.04/devel for everyday use.

@jumbs said in Use USB as serial port on OPO: Do I understand correctly, that compiling a Kernel with the required driver linked into the Kernel, means, compiling on seperate computer starting from source code, and loading a new ROM on the OPO? yes