In the OS category there is a topic about background location that may be interesting for your GPS issue.
On the other hand, I think nobody would had though about disabling the volume buttons. You may want to use them for your headphones even with the phone locked.
Posts made by aimar
-
RE: tweaking UT a few ways...
-
RE: Focal/20.04 is out for quite a while now. You still use Xenial/16.04? I would like to know what stops you from upgrading?
I am happily still using a BQ E4.5 so there is no other option.
-
RE: Call for testing: background location updates
Why have I been downvoted?
I was just reporting an initial weird behaviour, but finally a succesfull performance. -
RE: Call for testing: background location updates
Hi @AmauryDBZ. Sorry, I am not a developer, so I cannot provide any hint. I usually use a trial and error approach. You can try uninstalling the package and reinstalling it again.
Actually for me, the first time it was not properly installed because I lost the wifi connection. I tried again and although I had some doubts (see posts above) it works.
My phone requires some time to connect to the satelites, but once it is done, Activity Tracker followed me. -
RE: Call for testing: background location updates
It works.
I tried it with Activity Tracker and records my position with the phone locked.
During the first try, the location switch turned off automatically whenever I turned it on. But now the switch and me seem to have achieved an understanding.
Thank you very much for such a useful feature. -
RE: Call for testing: background location updates
I think ubuntu-location-service-bin is not properly installed.
Just some questions. I see the following packages upgraded:
biometryd-bin libbiometry1 qml-module-biometryd
Why do we need biometry stuff?
This ones were downgraded:
libubuntu-location-service3 qtubuntu-sensors ubuntu-location-service-bin unity8 unity8-common unity8-private unity8-schemas
@mardy you mentioned Lorimi, but I still see unity. Is it all right? I understood this change was for xenial devices.
I hope I do not miss anything with the downgrade. -
RE: Call for testing: background location updates
Wow! How did I miss this feature? I have seen the last post and realize that it was available two years ago.
Well, BQ E4.5 OTA 25. I have just installed it, but I am not very confident it will work. I get some errors that make me suspect:ubuntu-location-service-bin#####] W: No sandbox user '_apt' on the system, can not drop privileges E: Sub-process /usr/bin/dpkg returned an error code (1) ERROR:ubports-qa:Failed to run 'apt full-upgrade'. See the output above for details. mount: / is busy WARNING:ubports-qa:Failed to remount root filesystem read-only. WARNING:ubports-qa:Please consider rebooting your device.
I have rebooted the phone. This weelend I will test the background data adquisition.
-
RE: How can I edit file in /etc folder on UT 20.04 (Focal)?
Does not
sudo nano /etc/deviceinfo/devices/halium.yaml
work?
Or usingchmod
does not help? -
RE: BQ Aquarius M10 FHD that had Ubuntu 16.04 won't boot
@Daryl There was an issue some time ago with OTA-25 and BQ devices. The behaviour was similar to what you described. The solution was to press power button and volume - together for up to 15 seconds. Maybe you have to retry a couple of times.
If that does not help, you can double check the files you used because be aware that there are two BQ Aquarius M10, HD and FHD.
-
RE: MicroSD read only OTA25?
Well, actually I had not used "Pictures" but the translation to my language. It seems that for saving in the SD card, "Pictures" is mandatory.
Maybe I am wrong but at least now I can save wherever I want to. -
RE: MicroSD read only OTA25?
I found that the file ~/.config/user-dirs.dirs contains the default folders. So I edited it and restored the missing default home folders, e.g.,
XDG_PICTURES_DIR="$HOME/"
toXDG_PICTURES_DIR="$HOME/Pictures"
.
Now I can save the photos in the device. The problem with the read only SD card persists. I have tried with a brand new SD card with no luck. -
RE: MicroSD read only OTA25?
I have reälized that the Pictures folder I have just created in the home folder lacks the custom icon overlaying the folder icon.
Maybe that is the reason why the captures failed.
Even the screenshots are not saved (they do not however show any error alert).
I think camera app is not recognizing the /home/Pictures folder as valid.
Any ideas to solve it?
Thank you. -
RE: MicroSD read only OTA25?
It was quite annoying to open the terminal and launch the command each time I wanted to take a photo or save a file in the SD card, so I formated the SD card.
I have created symlinks for all the folders in the home folder towards the SD card. It is a 128 MB card, I have to take advantage of it.
However, although the problem is solved (the SD card is not read only now; I can write on it), the camera app keeps complaining stating that the SD card is read only. I removed the Pictures folder symlink and tried to save the photos on a fresh Pictures folder of the device's home folder. But every time I take a photo I get a "failed" error.
Has anyone faced a similar issue? -
RE: OTA25 - BQ E4.5 does not boot
@Flohack maybe I did not explain it clearly. My device is now booting properly without any fix.
I do not need to reinstall it.
I thought it may be an interesting information to those who are still struggling with the boot isuue.
Thank you anyway. -
RE: OTA25 - BQ E4.5 does not boot
@rugby but mine is not stuck anymore during booting.
Can you try restarting the device (without turning it off) and check if afterwards you can turn it off and boot it correctly on the first try?
If you are succesful we may provide to the devs valuable information about the cause of this failure. -
RE: MicroSD read only OTA25?
I realize that from time to time, maybe when the phone goes to sleep, the microSD card becomes read only again.
I use the mentioned command and I can create/delete again files in it. -
RE: OTA25 - BQ E4.5 does not boot
I know I marked the topic as solved but I have an important update. Good news, although I do not know how to explain it.
Now I can boot without any problem. The boot issue has fixed itself. Why? How? Currently I am not sure.
Since the update issue, I did not turn off the phone. I was just lazy and I did not want to use the workaround of booting it twice.
Simultaneously (and I do not know if it is related to OTA 25, but maybe), I had some issues with my microSD card that started to mount as read only file system.
At the time I did not want to turn off the phone to boot it again or extract the card, so I just restarted the phone. Several times indeed, because I did not know what to do to fix the card issue, extracting the card, without extracting the card, etc.
I know it is not a precise procedure. I cannot recall what did I exactly do. But restarting the phone is the only thing I guess might have some influence.
Now I can turn off the phone and boot it correctly again on the first try
Can anybody try it? -
MicroSD read only OTA25?
I do not want to blame OTA25. I do not want to be a pain in the ass. I cannot corfirm OTA25 is the cause, but by the time I updated (BQ E4.5 stable) my microSD card started mounting automatically as a read only file system.
First I noticed the camera complaining about the impossibility of saving the pictures in the card. Afterwards I realized that Syncthing was not syncing and OSM ScoutServer also complained.
I shutdown, reboot, restart, detach the card and insert again without any luck.
Finally, this command in the terminal did the trick:sudo mount --options remount,rw /dev/mmcblk1
/dev/mmcblk1 is the path to the card found by fdisk -l
Currently the issue is solved although I have to run the command each time I restart the device. Because now, I do not know why or how, I can boot without any trouble even with OTA25.
I would like to know how can I make this rw persistent.
Besides, does anybody have a similar issue since updating? -
RE: nextcloud
In case it helps for narrowing down the issue, it works for me on 16.04/xenial on a BQ E4.5.
-
RE: WIFI connection to eduroam
In case it helps narrow down the issue, it works for me on 16.04/xenial on a BQ E4.5.