@3arn0wl said in Recommended speaker I could plug in to my Meizu MX4?:

Any speaker plugged into your earphone socket should work... there are ones available which include an amplifier (for more volume) and those that don't... The ones with amplifiers are a bit heavier and bulkier...
I'm just wondering why the phone's speaker isn't working...?

I'm not 100% sure why it's stopped working, but the phone stopped giving audible notifications over about a 2 week period. I had replaced the battery about a couple of week earlier. One of my friends pointed out that the case wasn't on properly when he looked at it, and that it did look like there was a lot of pressure on some parts. I'm now guessing that I'd messed up putting the new battery in and I've physically damaged the phone.

Thanks for that. Ideally I'm looking for something small as I'm going to have it plugged in quite a lot. It doesn't need to be massively loud, as I can always plug it in to my normal speakers when I'm at home 🙂

@cj_c I have a work around.

If on filling in the account details and pressing <next> Dekko returns to the same screen do not back out as this deletes the new account information entered. Instead restart the phone.

If you entered the information correctly then your mail will be there when go back into Dekko. If the account details were not correct, you have the opportunity to edit the account.

Similarly if the validation hangs, simply restart the phone.

The lack of feedback from Dekko when configuring an account has already been raised as an issue.

@Ingo same as you on Nexus 5.

@kristatos I don't remember the precise details, but I think the update got published too early... I think it needs OTA-10 for it to work, or something.

It's working again. I don't know what was the problem but I solved it this way:

Installed an old 15.04 UT-Image with the SP_Flashtool After that the phone was able to start again Upgrade from 15.04 to 16.04 (OTA-9) with the latest ubports-installer Device was still able to start

After that everything seems fine again

Thanks for helping.

@advocatux said in What's the situation with blue light filtering on Ubuntu Touch?:

@Opolork wrong answer! You need to keep testing and improving UT until 4 a.m. at least 😆

Far too late for an extreme early bird like me. 😉 🐦

Bootloader cannot be locked on any existing device so far as I know.

@thilov Yea today it works great thanks.

Glad to have flashed an OPO from OTA 9 to edge for the first time thanks to the 0.2.3-beta installer that worked very well for me.

Even happy to have been able to experience my first crash and reboot after 5 minutes !! ☺

@Lakotaubp said in Possible to put custom text on lock screen?:

@Opolork Circle Message from the Openstore used to do it. haven't used it in awhile

Thank you, Lakotaubp. That's exactly what I wanted. 🙂

Just a little update:
dmesg -w output is:

[ 5021.594797] usb 1-12: new high-speed USB device number 14 using xhci_hcd [ 5021.743209] usb 1-12: New USB device found, idVendor=2a47, idProduct=201d, bcdDevice=ff.ff [ 5021.743213] usb 1-12: New USB device strings: Mfr=2, Product=3, SerialNumber=4 [ 5021.743216] usb 1-12: Product: Aquaris_M10_HD [ 5021.743219] usb 1-12: Manufacturer: Ubuntu [ 5021.743221] usb 1-12: SerialNumber: FC074240

MTP works fine. I can transfer files no problem.
On my old homeserver running debian buster, adb works (somewhat). I need to try plugging it in a couple of times sometimes. Similar to the installation trouble on the M10.

Thought I'd leave this here for future reference. There is definetly something wrong with the M10 that causes these weird problems though. Thanksfully it has OTG, so I can hook my keyboard up to it.

If a developer wants to maybe try finding out more about the issue, I am up for helping with testing/troubleshooting.

@flowbee kudos! Enjoy your new UT device!!

🎉 🎉 🎉

🙂 So pleased to read that you're all sorted, @NexionTech

@advocatux Oh, I'm very sorry. Thanks for your reminder!👌

Sorry! "etc" is an abbreviation of the word "etcetera".

Yes, I knew, thanks

Btw you can find the latest Android official stock ROM for Nexus 5 at https://developers.google.com/android/images#hammerhead

@Ingo Thank you for the ideas. This happens at random when the phone is switched on with screen off and I switch on the screen. Then, the colored noise can persist even after reboot.
Because of this pattern, I didn't identify any app as the troublemaker.
Thank you for the fairphone community map.

Since following 'https://support.fairphone.com/hc/en-us/articles/115001041206-Troubleshoot-your-Fairphone-2-issue > Display > My display shows a pixel image (coloured noise)' leads to the exact picture of my screen, I suppose this is most probably a known hardware issue.
I followed the instructions on @advocatux link, which means opening and cleaning every inner parts of the phone.
It works again but it has already been doing working - colored noise - working loops so I will keep you informed.

@dobey said in Security of data and passwords when phone is lost/stolen:

This is only true if the bootloader is already unlocked, or the device has a bug where unlocking the bootloader does not perform a system reset and destroy all data. Newer devices do not necessarily require "authorization" either, but just have a more complex process where you have to also set an option from within the booted Android system.

You're right. Completely forgot that unlocking forced a wipe. Thanks for the correction.

Newer devices do not necessarily require "authorization" either, but just have a more complex process where you have to also set an option from within the booted Android system.

Yes, that process is what I'm referring to when I say unlocking must be authorized from within the stock OS before it can be done to newer devices. (i.e., "must be flagged as unlockable from within developer settings" in the earlier post. I probably should have added the word "manually" before "flagged" to make that clear.)

@arubislander Thanks for your input. I guess if I'm patient, the problem will soon be fixed.