@Flohack thanks, solved link to factory images - xda forums fastboot flash LOGO logo.bin

https://github.com/ubports/messaging-app/issues/136

@guru When traveling abroad, it makes sense in foreign towns between skyscrapers, in restaurants or on the subway.

While USSD GSM codes are universal: https://en.wikipedia.org/wiki/Unstructured_Supplementary_Service_Data these seem to just use a similar syntax but are not actually transmitted over the GSM network. Thus I agree that this probably can't work on UT unless specifically implemented.

I don't think there is currently a CalDAV task app. Maybe voice your support here: https://github.com/kugiigi/talaan-app/issues/17 @kugiigi

@doniks its just a .img file contained in a .gz just extract the .gz file and flash the resulting image onto a USB drive (or a harddrive depending on if you'd wanna install it as main os)

Hook up an external keyboard, that worked for me

@schouk IIRC you tried investigating the media hub and other ways to send the audio. Now it looks like "solving" the issue with bluetooth was achieved by degrading the audio quality to allow it to be more fluid... It was explained that when the phone is locked the processor is slower. Maybe the audio stream from spotify is too hard to decode in real time for the processor. Bluetooth is known to have a lower bitrate so the audio stream is lighter than the original one. My guess is that bluetooth requiring a lower bandwidth the processor is now able to process the audio stream in real time. Or maybe downgrading the stream is easier than processing it through the audio output... What I would try is to bufferize the stream to give some slack to the processor to produce a clean audio output. I hope this can help. [Edit] Maybe it's just RAM usage restricting the buffer size hence leading to those audio glitches

I sync the pictures (fotos or screenshots) to my FreeBSD laptop with: $ cd /home/guru/UbuntuPhone/rsyncedFromBQ $ rsync -rav phablet@192.168.2.102:Pictures . This is done by SSH over Wifi (works as well over USB tethering).

My g'ness... I just, barely remembered it... phew! So that's taken care of from a functional perspective.

@shapley Up near the start is a section on flashing twrp with fastboot then using that to reset/fix cache, system and data. After that just rerun the installer and all should be ok.

@Flohack thanks a lot for helping me open my eyes. I still don't understand the difference in vendor files but android_device_oneplus_bacon-1 seems indeed to be used for building the images.

Thank you @Ingo. I've added it to the code and it works. As this is the reboot approach I'd still leave the issue open as maybe someone might come up with the preferred refresh solution.

@normandc Thanks, this hack works for me

Was Android > 5.1 installed before? You might need to go back to stock Android from an older verison to get the cache partition right.

Was Android > 5.1 installed before? You might need to go back to stock Android from an older verison to get the cache partition right.

@dbosley No problem. All sorted.

@Lakotaubp Good to know, I’ll try that if it happens again. Thanks.

@Stefano Thank you for the advice. I'll try asap.