I had same audio issue with my Pro5 also. I think it's just another POS from china. Some phones are ok and some not.

My problem occurred in Android and UT/UB

This may come late, but deleted imeis can be restored quite simply in Android, hopefully in UB too in near future. I formatted them from my bq 4.5 an this is how i got them back. Should work with other phones too.

Open dialer and type: * #* #13646633#* #* (NO SPACE between * and #, This forum makes them italic if written together)
Click: Connectivity
Click: CDS Information
Click: Radio Information
Click: Phone 1
Type: AT +EGMR=1,7,"NEW IMEI1 HERE"
Click: SEND AT COMMAND
If OK was was reported, then go back and choose Phone 2 (If you have 2 sim phone)
Type: AT +EGMR=1,10,"NEW IMEI2 HERE"

After that reboot phone and sim should now work.

IMEI numbers can be checked with dialler command: *#06#

IMEI numbers can be found from sticker in phone or box or even from old phone. If imei from other phone is being used, then that phone should not be used at same time.

Looks like this annoying bug is still present. It's been since first release. Not sure about Ota2 i skipped that.

@bruno said in BQ Aquaris M10 HD won't turn on [solved]:

h am android package cause BQ don't provide an ubuntu package for the HD edition anymore. Afterwards i could reflash the device back to UT by using the UBPorts installer!
Now i'm glad to have a running device and i stricktly avoid to power it down...
Btw: after reflashing to android the battery power was only 1%. This after shutdown only 48h before. So the shutdown was defintly incomplete and the device drained the battery strongly.
My question now: is this a BQ problem? Or is it a UT bug?

I think your battery was drained just in time when you plugged it in. When that happened to me i could not connect it to my computer. Your reflash was most likely not necessary.

Bug is with UT. Never happened to me when i used Android.

That has happened to me also. I thought it was bricked, but after few days battery had drained and it started working again. I believe you are having the same issue, it did not shut down completely.

Let it be for few days and try power button again. Put it in freezer to hasten battery drain.

@marathon2422 said in M10 Lightning & battery splash screen when i plug it in my computer:

Are you going from Android to Ubuntu touch and then to ubports,
When using BQ flashtool ,it will give this fault,try rebooting your PC,clearing the flashtool and starting again , reinstall the USB tolls supplied by BQ, do everything including hitting the download button then,,,,,plug in your device in a turned off condition ( sound on in PC and listen to what it is doing)

I've used bq flash tool plenty and this is the first time it failed. It has always worked flawlessly. And it's working now as you can read from above message. Problem was probably in the tablet.

Perhaps battery charge controller malfunctioned and caused that lightning screen error, but it was fixed when battery drained a bit?

Well, i took my laptop and used bq flashtool to install latest Android 2.6.2 and it flashed without problems.

https://www.bq.com/en/support/aquaris-m10/support-sheet?ssess=5a9bb41e25914&sorigin=productList

After that i returned to my desktop computer and now the lightning on battery image is gone and flashtool can perform memory test without problems. I have no idea what caused that yesterday and only difference was that battery charge dropped from 98% to 96%.

Guess i'll stick with this Android till 16.04 is out. Hopefully that wifi problem and loads of other bugs are gone when that is released.

@marathon2422 said in M10 Lightning & battery splash screen when i plug it in my computer:

@andromeda try TWRP,use that to wipe, then try flashtool, reboot your PC also before flashtool

If i wipe tablet with TWRP that destroys Android and if i cant flash anything into this anymore it's pretty much bricked. Now i at least have Android 5.1 in it.

I fear this is the end of this tablet. I have never seen that splash screen before and all those flashes UT > Android was done within 1 hour at the same computer, so nothing changed in this computer either and reboot didn't fix anything.

Did my M10 FHD broke? I went to quest to see whether last original UT would work with wifi autoconnect and it sure did not. Then i flashed Android 5.1 into it and wifi works like a charm with it. But now when i plug it in my computer splash screen appears for few seconds with drained battery and lightning on top of it. Not sure what that is supposed to mean other than broken battery or improper charger voltage, but after that it shows battery stage @98% and continues to charge.

Because of that i cannot flash my tablet anymore. bq flashtool gives me error:
" BROM ERROR : S_COM_PORT_OPEN_FAIL (1013)"

Ubports installer doesn't even recognize the device and manual install does nothing, but enter fastboot.

I tried with several cables and different ports, but no luck. Files can be browsed so datalink should be fine.

I had same audio issue with my Pro5 also. I think it's just another POS from china. Some phones are ok and some not.

My problem occurred in Android and UT/UB

I've made tens of Web Apps with Web App generator. Can i copy them to pc and back again somehow?

I need to try and reinstall UB for my M10 to see if it fixes the issues i'm having, but would hate to remake all of those all over again.

@lakota said in M10 FHD randomly boots up when plugged in charger:

@andromeda I'm running the dev channel (15.04 r61) without issue on m10 fhd. So be brave and give them a trycan't be any worse can it !

I have this version on my tablet and i thought that this bug was gone, but no. Today it rebooted itself once more while charging...

Perhaps this bug and that no wifi autoconnect is related to that possible nvram failure i got during flashing to UBports?

Guess it's gonna be flash back to shitty Android if there are no solutions.

My M10 is also losing wifi password. It didn't so it back in the OTA2 and with Android it worked fine. Now with latest OTA3 stable and with DEV builds it keeps forgetting it. Did the flashing to UB ruin my Nvram? Can it be fixed?