Related
I have searched all over and couldn't find any answers, so hopefully this isn't a repeat thread.
I just purchased the HTC desire 816 and upgraded to it. I activated it, and set everything up, Saturday. Sunday after trying to load xposed onto it, it froze on the boot screen.
I managed to restore it from fastboot, and got it updated to lollipop.
Now for the problem, and what I have tried:
The phone will not see bluetooth devices at all.
First I tried simply a factory reset, which allowed it to see my smart watch and start to connect to it. Part way through the setup of my watch, it lost it's connection.
Next I tried a wipe and restore to full stock, this did not allow me to see any bluetooth devices.
Then I tried rooting, cwm, and putting kitkat back on the phone. I still couldn't see bluetooth, and now I am trying to upgrade back to lollipop.
I am at a loss as to what may be the problem, but I need it to work with bluetooth.
I have tested it with both my LG G smartwatch, and a gemline bluetooth speaker.
OK, so a little update here. I did a full stock & root flash last night.
The wifi began working, and Bluetooth was connected to my smartwatch.
This morning, wifi is still working and bluetooth can't see any devices.
On a side note, I am trying to figure out what version of xposed to install on my phone.
tenchu98 said:
OK, so a little update here. I did a full stock & root flash last night.
The wifi began working, and Bluetooth was connected to my smartwatch.
This morning, wifi is still working and bluetooth can't see any devices.
On a side note, I am trying to figure out what version of xposed to install on my phone.
Click to expand...
Click to collapse
If you're on 5.0 lollipop then 21. If you're on CM 12.1 (5.1) then 22. I have this same device and carrier and haven't had any issues like you're describing other than a few Bluetooth dropouts every once in a while. Good luck.
http://forum.xda-developers.com/showthread.php?t=3034811
thoctor said:
If you're on 5.0 lollipop then 21. If you're on CM 12.1 (5.1) then 22. I have this same device and carrier and haven't had any issues like you're describing other than a few Bluetooth dropouts every once in a while. Good luck.
http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
I went back to full stock, and relocked the bootloader, because HTC said that it was an issue with the bootloader being unlocked. I doubted them, and it turns out I was right to doubt. The issue isn't fixed, and I seem to have narrowed it down to the searching function. My HTC can't see any discoverable items.
I have a gemline speaker, which has NFC to pair Bluetooth built-in, and my phone is unable to see it when I try to use NFC enabled pairing.
I am suspicious that somewhere along the lines the bluetooth files became corrupted in system. I have been trying to find a way to put the original ones back on, but haven't been able to find a way. I really want to get this working, and remove root.
Why do I not want root, because my kids enjoy pokemon go and it won't run on root anymore.
tenchu98 said:
I went back to full stock, and relocked the bootloader, because HTC said that it was an issue with the bootloader being unlocked. I doubted them, and it turns out I was right to doubt. The issue isn't fixed, and I seem to have narrowed it down to the searching function. My HTC can't see any discoverable items.
I have a gemline speaker, which has NFC to pair Bluetooth built-in, and my phone is unable to see it when I try to use NFC enabled pairing.
Click to expand...
Click to collapse
Yeah, that's a load of crap so you were right to question that. My bootloader stays unlocked and I don't have any Bluetooth issues other than the ones noted for running CM custom roms and the headset dropouts. I have 3 different Bluetooth devices linked to my phone and no issues pairing any others either.
I am suspicious that somewhere along the lines the bluetooth files became corrupted in system. I have been trying to find a way to put the original ones back on, but haven't been able to find a way. I really want to get this working, and remove root.
Why do I not want root, because my kids enjoy pokemon go and it won't run on root anymore.
Click to expand...
Click to collapse
You could find and flash back your stock recovery and then find either the stock RUU file or the stock Rom.zip file and flash back to stock. I understand about root. It's getting to the point my next device will probably stay stock but I'm having my fun now.
thoctor said:
Yeah, that's a load of crap so you were right to question that. My bootloader stays unlocked and I don't have any Bluetooth issues other than the ones noted for running CM custom roms and the headset dropouts. I have 3 different Bluetooth devices linked to my phone and no issues pairing any others either.
You could find and flash back your stock recovery and then find either the stock RUU file or the stock Rom.zip file and flash back to stock. I understand about root. It's getting to the point my next device will probably stay stock but I'm having my fun now.
Click to expand...
Click to collapse
I did this once already, I am thinking that my next step will be to manually copy the bluetooth related files from the system image into system using root
then flash unsupersu.zip
So I hav replace every bluetooth related file I can think of, and even deleted some file suggested online, and my phone still doesn't see other devices. When I put my phone on my NFc enabled speaker it acts like it is going to pair, but then says "unable to pair gemline speaker".
I am beginning to become frustrated.
Hi guys,
I've got a little problem.
I'm on OP3 OpenBeta 11 (actually i'm using multirom and I've got this problem with all the rom that I've tried, OB10 OB11 Oxygen 4.02, cm14 in the last 2 days).
Two days ago I took my father car (Kia Sportage) and I connected with the bluetooth in order to use spotify and the phone call. I'm used to do so everyday in my car (Kia Rio) without any problem.
In the evening I had flashed as secondary Freedom 2.4 and the phone simply won't boot, so I delete it from recovery and all seems fine on the other roms.
Until the day after, phone call via bluetooth became buggy and mute, I cannot hear and I cannot be heard, although Spotify and other music/video app work fine.
I've tried to flash new rom, to use other bluetooth device, but the calls remain always mute.
So before I completely restore the device, is there some magic firmware which could help me? Like wifi firmware, radio firmware or something like that, which could be corrupted by freedom rom?
Thank you for wasting your time for this!!
The media streaming from the phones to some in car audios was messed up since nougat (both on open betas and stable releases). Any rom using those bases would probably have the same issue.
But, since today, it seems fixed in Open Beta 12.
I was posting about it on reddit earlier:
https://www.reddit.com/r/oneplus/comments/5wu6in/open_beta_12_released/ded2peg/
btw, I understand this was not the answer you were looking for as you're trying not to flash an entire rom again, but from my experience with nougat roms so far, it's really the best thing you could do right now: flash Open Beta 12. BT working flawlessly and way smoother than any previous beta too...
Just for info:
The ROM doesn't resolve the problem (I couldn't call, but media were working fine). I had to delete all, now is working with every rom, right now I'm on OB12
Thank you for your answer
So I can't connect my phone to the car bluetooth connection in my car. It's ONLY a custom ROM problem. If I use FreedomOS or stock it works fine. I have changed to literally every firmware in existence, still no fix. I can connect to some devices, but I also have problems with Android Wear.
This is a big deal as I bought this phone for a custom ROM. Anybody know what's the fix?
I have read more threads about this, but nobody ever seems to have an answer that isn't "flash xyz firmware ZIP in TWRP" which I've already tried. Please, anybody willing to help, please do!
So you can't pair your phone i assume?. If so I had the same problem.
It was a real issue in earlier aosp roms but now alls I do is clean flash the rom, set up and connect my BT and then if using a theme it goes on last!!!!.
No, it pairs fine, but then never connects as a phone. Only media works. I never dirty flash roms, so that's not the issue at all.
I will try this, then report back. Haven't tried this yet.
Which option in the toolkit should I use? There seems to be no options to revert stock specifically. You mean the OP3 Unified Toolkit, or is there specifically a "unbrick tool"?
Tried it. Not fixed. Used 4.1.3 zip after the reflash of stock using the Qualcomm tool. Should I try a 6.0.1 zip like 3.2.8 OOS or something?
I have built several custom ROMs with a BT fix that gets rid of the "no phone" issue. This sounds like the same issue I had so this should work.
Hello everybody,
I am experiecing a bluetooth issue on Android Nougat 7.0 (I tryed exactly on versions EQL1 and EQD1).
The first time the device turns on, the bluetooth works fine. Then, after a reboot, I can't turn bluetooth on any more.
If I go through a factory reset I will get the bluetooth working again, till next reboot.
On Android Marshmallow 6.0.1 bluetooth works just fine...
I would like to know if I am the only one experiecing this issue as I didn't find any thread about it.
Can someone help me please?
My cell phone does not sound or even in the microphone.
Microphone is muted.
I plugged in my JBL Bluetooth headset, and it was also without audio and microphone. I restarted the phone, with the JBL turned on via Bluetooth, the phone's sound came back, but the microphone didn't.
If I restart again, without JBL connected via bluetooth, the problem of no audio comes back, and the microphone is not sounding.
I think the problem has to do with software, not hardware.
In view, I often restart the phone, and sometimes come back.
Just yesterday, I restarted the phone, and out of nowhere, the microphone and the audio came back. It lasted a day, and it got bad again.
The headset by the type C adapter also does not recognize in the phone.
I put the headset on, the headset icon does not appear on the taskbar, let alone sound on the headset or microphone.
Is it a MIUI bug? Should I keep flashing Miui through Xiaomi Flash until the bug goes away?
My current MIUI is Miui Global 10.4.1 (10.4.1.0) PCAMIXM.
Mikado Ryugamine said:
Can someone help me please?
My cell phone does not sound or even in the microphone.
Microphone is muted.
I plugged in my JBL Bluetooth headset, and it was also without audio and microphone. I restarted the phone, with the JBL turned on via Bluetooth, the phone's sound came back, but the microphone didn't.
If I restart again, without JBL connected via bluetooth, the problem of no audio comes back, and the microphone is not sounding.
I think the problem has to do with software, not hardware.
In view, I often restart the phone, and sometimes come back.
Just yesterday, I restarted the phone, and out of nowhere, the microphone and the audio came back. It lasted a day, and it got bad again.
The headset by the type C adapter also does not recognize in the phone.
I put the headset on, the headset icon does not appear on the taskbar, let alone sound on the headset or microphone.
Is it a MIUI bug? Should I keep flashing Miui through Xiaomi Flash until the bug goes away?
My current MIUI is Miui Global 10.4.1 (10.4.1.0) PCAMIXM.
Click to expand...
Click to collapse
Probably a bug with your firmware.
Try to do a clean install of the rom or a factory reset to the phone.
I had a bug with my Wi-Fi with my Mi6 for over a year. Between Global stable, xiaomi eu beta and STABLE, my wifi was always dropping, sometimes more than others. Now it's fix. Probably magic.
I had problems with xiaomi roms that what fixed it was flashing the same zip over and over again until it started working. Not even flashing the phone back to stock fixed it.
Always backup your stuff before doing a factory reset.
Sent from my MI 6 using Tapatalk
XiCO FiR3 said:
Probably a bug with your firmware.
Try to do a clean install of the rom or a factory reset to the phone.
I had a bug with my Wi-Fi with my Mi6 for over a year. Between Global stable, xiaomi eu beta and STABLE, my wifi was always dropping, sometimes more than others. Now it's fix. Probably magic.
I had problems with xiaomi roms that what fixed it was flashing the same zip over and over again until it started working. Not even flashing the phone back to stock fixed it.
Always backup your stuff before doing a factory reset.
Sent from my MI 6 using Tapatalk
Click to expand...
Click to collapse
I just reset it, still nothing, turned the microphone back on once the ROM installation was over, and then the microphone is muted again.
I upgraded from the phone itself, in the system update tab, and located the internal memory.
I don't know if so, the installation is less clean, is it?
For Xiaomi Mi Flash, it only works if Xiaomi has the bootloader unlocked, mine is locked.
To unlock the bootloader, also only if it's in developer ROM, I was in stable.
What do you think?
Now I'm in the developer ROM, better unlock the bootloader, and try to re-rom via Xiaomi Mi Flash or install TWRP, and go there?
Will this make the installation cleaner?
I am still confident that the problem is firmware, not hardware really.
The newest vantom kernel might be the cause?
Shiw Liang said:
The newest vantom kernel might be the cause?
Click to expand...
Click to collapse
I was thinking this, I'll pass this kernel to see what happens:
https://forum.xda-developers.com/mi-6/development/kernel-loveroriented-kernel-t3863778
How did you do ? I'm stuck in the same situation. I have tried to flash stock rom, flash another rom, but still no sound and no microphone
baoprokute1234 said:
How did you do ? I'm stuck in the same situation. I have tried to flash stock rom, flash another rom, but still no sound and no microphone
Click to expand...
Click to collapse
Friend, I couldn't solve it so far. I do not know what else to do!
Already blinked stock rom, both by twrp, both by Xiaomi Flash. I installed Line OS rom, thinking that maybe out of stock could solve, and nothing.
And so far, I don't know if the problem really is software or hardware.
Thinking it was hardware, I bought the charging plate that comes with the microphone capsule days ago, I changed the part, thinking it could be the capsule, but the problem still persists.
baoprokute1234 said:
How did you do ? I'm stuck in the same situation. I have tried to flash stock rom, flash another rom, but still no sound and no microphone
Click to expand...
Click to collapse
How did your problem start?
Do you remember?
My, I do not even remember how it started, I already have this problem, a few months ago.
I tried to contact Xiaomi Global too, to no avail, they only recommended I do, what I had already done, factory reset, and etc ...
baoprokute1234 said:
How did you do ? I'm stuck in the same situation. I have tried to flash stock rom, flash another rom, but still no sound and no microphone
Click to expand...
Click to collapse
It would be nice if someone else, experienced in Xiaomi phones and the firmware / software issues of the phone, could help us.
I don't think people see much of the help tab topics around here.
I'm thinking of sending a private message to members who always post rom's here on XDA.
Can you solve the problems you encountered? I also encountered the same problem as you.
I know this thread is bit old, just to try to give some piece of mind for the ones searching out there (like me)
I have not solved the problem, there is no audio output in anyway, neither the microphone works.
After long time i taken my Xiaomi Mi 6 and flashed Lineage OS on it (lineage-19.1-20221013-nightly-sagit-signed) and using adb logcat to check the logstream from the device, i get the following messages:
11-09 00:04:35.233 28971 29014 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19
11-09 00:04:35.233 28971 29014 W AudioManager: updateAudioPortCache: listAudioPorts failed
11-09 00:04:35.280 1338 2414 E AudioSystem-JNI: Command failed for android_media_AudioSystem_initStreamVolume: -19
11-09 00:04:35.281 1338 2414 E AS.AudioService: Failed to initStreamVolume (1) for stream 11
11-09 00:04:35.281 1338 2414 E AS.AudioService: VSS(): initStreamVolume failed with 1 will retry
Click to expand...
Click to collapse
This lines repeat a lot of times, so I dig into Android Code Search to checkout what is the -19 code. Per def in the source code, -19 is the ENODEV constant, saying "/* No such device */".
As this constant is used everywhere in the source code, I need more time to isolate and found out where this error relates to the Audio System.
I still can't determine if it's a software problem or a reporting from the software that the hardware is faulty. I will update this message as i discover more.
filipe_x3 said:
I know this thread is bit old, just to try to give some piece of mind for the ones searching out there (like me)
I have not solved the problem, there is no audio output in anyway, neither the microphone works.
After long time i taken my Xiaomi Mi 6 and flashed Lineage OS on it (lineage-19.1-20221013-nightly-sagit-signed) and using adb logcat to check the logstream from the device, i get the following messages:
This lines repeat a lot of times, so I dig into Android Code Search to checkout what is the -19 code. Per def in the source code, -19 is the ENODEV constant, saying "/* No such device */".
As this constant is used everywhere in the source code, I need more time to isolate and found out where this error relates to the Audio System.
I still can't determine if it's a software problem or a reporting from the software that the hardware is faulty. I will update this message as i discover more.
Click to expand...
Click to collapse
Have you found anything? I'm having the same problem, is it actually a hardware issue or is it software?