Posts made by rbarclay

Hi folks,

I seem to remember that in the past there was an app called "Bluetooth File Transfer", and I could select "share via Bluetooth" in other apps if I had that installed.

Now I'm on 20.04 (on a Volla 22), and there's no more "Bluetooth" app in OpenStore, and no more "share via Bluetooth" in other apps.
All while I'm perfectly able to BT-pair with other devices via system settings. But no more BT sending nor receiving files.

Have I missed something?

Grateful for any hints.

cheers,
rbarclay

Hi there,

for the last couple weeks there's an update available in OpenStore for "Fahrplan" (public transport route planner), 2.0.33-4 to 2.0.33-4-focal, but it's not installable (see attached screenshot).
I also tried removing the currently installed version (2.0.33-4), incl. clearing Cache/App Data/Config via UT Tweak Tool, and reinstalling, but end up with the exact same problem (2.0.33-4 installed, update to 2.0.33-4-focal available but not installable).

Phone is a Volla 22, I'm on the 16.04-dev channel.

Any hints?

I'd be especially interested in how I could try the update in a shell so I could maybe see a bit more details than just "exit code 7"

Kind regards,
rb

@Schlicki2808 - thank you!

@Keneda syncthing sounds interesting for keeping some files/folders, well, synchronized between different computers (and I might just use it for keeping my pictures automagically synced to my desktop), it's not what I need from a "real" backup solution - especially keeping old backups around and so on.
And I tested that rsync'ing ~phablet into BackupPC works, so I'm good wrt. that.

Hi everyone!

The pictures taken with the main camera are pretty damn bad and blurred, worse than ones taken with the front ("selfie") camera, even when set to 48MP.

Here's two pics for comparison:

• https://ibb.co/kxMc3Pb (main cam)
• https://ibb.co/FHk5TnH (selfie cam)

Is this normal behaviour for UT on a Volla 22? Because if it is, the main camera is basically useless.

Any hints/tips would be very, very, very much appreciated.

Kind regards,
rb

Ok, I can answer my first question myself: yes, backing up /home/phablet/ is enough for all the normal data, incl. SMS, contacts etc. Even all the 2FA entries in Authenticator survived.

(Got a new phone (Volla 22) today, installed all the apps, rebooted, dumped a tarball of /home/phablet from the old phone (FP2), rebooted again just for the sake of completeness and et voila.)

Hi everyone,

I've included my UT phone into my normal backup setup (BackupPC), which bascially just rsyncs over ~phablet daily & automatically.
To have rsyncd automatically starting up, I remounted / read/write temporarily so I could edit /etc/default/rsync.

Questions now:

• is backing up ~phablet enough, or are there other files I should include (note that I don't mind reinstalling OS+apps should I need new hardware, I just care about data like pictures, SMS and especially contacts)
• is just remounting / read/write the intended way to edit etc-files?
• will my edited /etc/default/rsync survive OS updates/-upgrades?

Or am I doing it completely&utterly wrong, and there's a much better way for doing automatic backups?

Grateful for any hints,
rbarclay

@gt This probably happened with an update on Dec. 28th (it says "Ubuntu touch Version 3" in System Settings -> Updates) for me. OTA-7 didn't fix the issue, but it also didn't cause it.

@flohack Yes, please

@flohack Ah, sorry, the usual confusion about 2- and 3-letter acronyms (I probably see to many references to "UX" etc. at work ).

Also I'm not on any messenger. I vastly prefer having all my conversations in one central place, and for historical (and work-related) reasons that's email.

@flohack Mine self-identifies as "bacon", FWIW.

There's only 4 occurrences of that file on the whole filesystem, and all of them are symlinks to /persist:

root@ubuntu-phablet:~# find / -name WCNSS_qcom_cfg.ini 2>/dev/null | xargs ls -l
lrw-r--r--. 1 root root 27 Dec 31 22:51 /android/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini -> /persist/WCNSS_qcom_cfg.ini
lrw-r--r--. 1 root root 27 Dec 31 22:51 /android/system/etc/wifi/WCNSS_qcom_cfg.ini -> /persist/WCNSS_qcom_cfg.ini
lrw-r--r--. 1 root root 27 Dec 31 22:51 /var/lib/lxc/android/rootfs/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini -> /persist/WCNSS_qcom_cfg.ini
lrw-r--r--. 1 root root 27 Dec 31 22:51 /var/lib/lxc/android/rootfs/system/etc/wifi/WCNSS_qcom_cfg.ini -> /persist/WCNSS_qcom_cfg.ini

Anyway, I've now grabbed a random instance (first Google hit) of that file from github, dropped it in /persist and now have WLAN again. Only problem now is that it won't remember WPA2 passphrases over reboots, but I can live with that.

Thanks for the help, @Flohack !

@flohack I have no idea what you mean with "UT", but I'm a veteran *n?x sysadmin, and in Vienna/AT. If I can help with stuff, I will.

@flohack /persist is mounted (well, it's a symlinl to /android/persist, which is mounted):

phablet@ubuntu-phablet:~$ mount | grep persist
/dev/mmcblk0p15 on /android/persist type ext4 (rw,nosuid,nodev,relatime,nomblk_io_submit,nodelalloc,errors=panic,data=ordered)
/dev/mmcblk0p15 on /var/lib/lxc/android/rootfs/persist type ext4 (rw,nosuid,nodev,relatime,nomblk_io_submit,nodelalloc,errors=panic,data=ordered)
phablet@ubuntu-phablet:~$ ls -l / | grep persist
lrwxrwxrwx 1 root root 16 Jan 28 1970 persist -> /android/persist

Also, there's various stuff in /persist:

phablet@ubuntu-phablet:~$ sudo ls -la /persist/
total 52
drwxrwx--x. 8 system system 4096 May 8 1970 .
drwxrwxrwt 9 root root 180 May 2 1970 ..
drwxrwx---. 2 1002 bluetooth 4096 May 8 1970 bluetooth
-rw-------. 1 1002 bluetooth 9 Aug 25 1970 .bt_nv.bin
drwx------. 5 system system 4096 Dec 31 2013 data
drwx------. 2 root root 4096 Jan 1 1970 lost+found
drwxrwx---. 2 system system 4096 May 8 1970 properties
drwxrwxr-x. 2 system root 4096 May 8 1970 sensors
-rwx------. 1 root root 15360 May 31 2016 sns.reg
drwxr-xr-x. 6 root root 4096 May 27 2015 usf

Just not that "magic" WCNSS_qcom_cfg.ini.

@lakotaubp That didn't fix the issue (reset, no change, rebooted, still no change).

Hi there,

since the last OTA-6 update I have no more WLAN on my OPO. The switch to turn it off/on in Settings->Wifi isn't there, either.

Looking at dmesg/syslog, I see lots of
[ 616.320112] wlan: loading driver v3.8.20.24
[ 616.341167] wlan: [903:F :HDD] hdd_parse_config_ini: request_firmware failed -2
[ 616.353362] wlan: [903:F :HDD] hdd_wlan_startup: error parsing wlan/prima/WCNSS_qcom_cfg.ini
[ 616.353518] wlan: [903:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
[ 616.368188] wlan: driver load failure

For testing, I forced the update to OTA-7, but the problem still persists.

Looking around the FS, the parsing error gets clear:

root@ubuntu-phablet:~# find / -name WCNSS_qcom_cfg.ini 2>/dev/null
/android/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
/android/system/etc/wifi/WCNSS_qcom_cfg.ini
/var/lib/lxc/android/rootfs/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
/var/lib/lxc/android/rootfs/system/etc/wifi/WCNSS_qcom_cfg.ini
root@ubuntu-phablet:~# ls -l /android/system/etc/firmware/wlan/prima/WCNSS_qcom_ cfg.ini
lrw-r--r--. 1 root root 27 Dec 31 22:51 /android/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini -> /persist/WCNSS_qcom_cfg.ini
root@ubuntu-phablet:~# ls -l /persist/WCNSS_qcom_cfg.ini
ls: cannot access '/persist/WCNSS_qcom_cfg.ini': No such file or directory

Any hints?

cheers+thanks in advance,
rbarclay