@Sander I hadn't tried that! THANKS

Hello I've managed to send a file using Bluetooth. First to get bluetooth running again, I've reset the device. After this, bluetooth service worked again normally. As advised by @gpatel-fr, I've installed bt-obex using crackle. crackle install bluez-tools I've then opened 3 Terminal tabs to run these tasks in parallel: Terminal 1 # To find the Android phone receiving the file bluetoothctl scan on # Find and copy the MAC address of the Android bluetooth adapter to paste it in terminal 3 Terminal 2 # Start the obexd tool /usr/libexec/bluetooth/obexd Terminal 3 # Make sure that the Android bluetooth device is discoverable # Send the file with bt-obex bt-obex -p [MAC address of the Android bluetooth adapter] /tmp/test-bluetooth.txt On the Android device, make sure that you accept receiving the file from the Ubuntu Touch device and check that the content is sucessfully received.

@Merlu said in Flashing firmware takes an eternity: stuck at the step "flashing firmware" since hours. I take it that 'hours' means literally more than 120 minutes. If it is the case, I'd say that it's abnormally long, yes. It could maybe mean that the download from Internet crashed (network glitch), or that after a successful download the transfer via USB crashed. IMO the #1 probable culprit for this last problem could be a low quality USB cable. In both cases you'd probably expect a good error message, but the installer is not that polished to have faultless (!) error reporting. @Merlu said in Flashing firmware takes an eternity: Is there a risk to brick my phone if i interrupt the process? Possibly but if you are stuck since 3 hours, I don't think there is much else you can do. Normally the low-level firmware, that allows for the phone to be flashed, is not touched by the process, so even if the phone don't start after that, you can try again to flash it, possibly with a better quality USB cable. That's exactly what happened to me when I installed UT.

@Merlu maybe you could give a try to what I advised you in your first thread: https://forums.ubports.com/post/91928 that is, retry the installation with another USB cable.

@bhdouglass One thing that I'm missing in the new site compared to the old one, as a developer, is to be able to have an overview of the stats of all your apps as once.

I honestly don't understand most of these thing. I don't know what NDK is But may I know what's the advantage of this? Would it have better performance? Also, I assume this can only be used on Android devices and not mainline?

@viko As has been said, dtbo.img is generally not needed. If the port doesn't boot, the issue is more like due to other reasons. Feel free to check the porting docs I linked you in Telegram.

I get an error with msmdownloadtool, something about package not beeing present...

hi everyone, I'm not new on the community (2 years ago) but I update my informations : I recently acquired phones to 'taste' OS : samsung galaxy SII : I descovered LineageOS with him... but too old for alternative OS... so, back to android. sony xperia X : I start ubuntu touch with it. actualy my daily device. oneplus6 : actualy on mobian. For the moment, I'm not able to go back... and re-install recovery. asus max pro m1 : actualy, more or less 'bricked' : the fastboot mode seems broken, and indicate error. It boot on twrp welcome screen... sony xperia Z5 compact : actualy a backup phone, one lineageOS... but available for 'crash tests'

Happy New Year! I hit the 1GB upload limit in GitLab, therefore there were no build for some time. The images in the artifacts.zip file are now bzip2 compressed, which brings me under the upload limit again. (I did not yet update the install instructions.) I made the following changes: I disabled a bunch of options which collects performance data and/or collect debug data The kernel is now built as optimized for performance, and tuned for Cortex A53 I turned the met driver ("MediaTek Embedded Technology") into an option, and turned it of. The met driver collects data which requires mostly proprietary tools to read I fixed all warnings from the device tree compiler I also spent a lot of time trying to get a 4.19 kernel to run. So far with no result - it boots but then crashes. The motivation here is that systemd requires at least a 4.15 kernel to support all features. Have fun, Kai

I don't know if the subject is already actual... but, as nobody (more competent than me - means most people on this forum) answer, i try to : Personnly, i meet not this on my device. do you try to activate (& change) the PIN on the android device and go back to the ut one ? if don't works, do you try to re-install UT on your device ? does it can come from your opeator : pearaps some of them considere UT device not as phone ? (but as objects or 4G box). So they could treats it differently.

i use to have the same good feeling on 16.04 realise. but i don't found it on 20.04 (ota-10 & 11). my batterie was old so... i change it, but i can't re-found the same feeling. I don't know the reason. But do you feel it too ? pearaps it comes from my phone...

@maahymot Not that I know of, but I also do not own the Mi A1.