Hello
Im xda forum user sience many years but on this account im new (lost my old one). I remember flashing pda's, nokias and other ancient hardware , not an expert but quite experienced user. I had some break with flashing, tempering with soft and settings because of lack in time and other hobbies(3d designing, automatics, 3d printing, milling, programming plc's, and many others) i like to do things, if i want something, i ask "can i do it myself?". this is how i made telescope tracking the moon with camera attached to it. Anyway back to the point.
I came back to xda beecause of Xiaomi Mi 10t which i bought last year. It worked fine for half a year then 1st issue occured:
- when i was browsing internet phone went black and tried to reboot but couldnt boot into android. So i said to myself "broken soft time to flash new rom" couldnt do that because motherboard was fried and phone couldn't communicate to pc. fastboot didnt work etc. It went back on varranty, they replaced motherboard with new one.
It shouldnt be bad ive got new phone xD, wrong.
At work im cnc programmer/sometimes operator so i listen a lot of audiobooks, music. After 2 months of using "new phone" i experienced some stuttering on bluetooth headset, sometimes no audio. nothing that turning on/off bluetooth cant fix. I also used wire headphones when bt out of battery. That sound problems wasnt realy an issue for me.
Some time later i run out of battery couldnt make it to charger in 30 sec xD it died. Ive put it on charge to 100% then turned on at night. I belive in that time it auto upgraded itself and rebooted - lights woke me up. There was strange thing because i couldnt hear sound at logo which was present before. i assumed it was disabled at options and went back to sleep.
When i woke up i was checking what the damn thing done i was shocked because i couldnt hear any sound.
Symptoms:
- tried to call my wife, couldnt hear her and she couldnt hear me, messanger same
- no audio at youtube, video worked
- no notification sound
- xcom2 (game) crash on startup
- camera in video mode - crash suddenly
- netflix crash
Then i tried the bt headset, same thing as above. it could pair but no audio. strange thing was that i could hear messenger call when my wife was trying to call me, so i assumed software problem not hardware. tried wire headphones same result it was recognized as headphones, icon present, bt off.
Tried different things:
- phone restart (didnt help)
- wipe cache, factory reset, (didnt help)
- tempering with sound notification settings and rebooting (didnt help)
- safe mode (sound not working)
- upgrading software (no luck)
- factory reset (no luck)
- switching sim card then restart (no luck)
Then i went to quick settings toolbar there was suspicious thing: bell was wobbling as well dnd icon but not turned on just wobble once when quick toolbar rolled out. i hid it and rolled out again icons stood still. So i restarted phone and same thing occured - first roll out gray icons wobble, second roll stood still (no blue - not turned on on both attempts). Then i started to tempering with sound and notifications options dnd and silance settings included.
- turning on/off random settings, rebooting system many times, suddenly ive heard sound at booting logo. Ok so everything was fine, had sounds working properly: notification, yt, messenger, camera in video mode eaven xcom2 was working - everything was fine. Untill i decided to restart phone to chceck if it stays that way - it didnt. After reboot again i had no sounds. tried tempering with settings again, after many attempts sound came back. Now i didnt want to restart the damn thing. i left it on for 2 weeks without restart and sound was on no issues except stuttering (i could live with it). then i had some issues when somebody or i called someone - sometimes i couldnt hear them sometimes i couldnt be heard (turning on off speaker/mic while i was on line helped, sometimes not). angry i swithed to old phone to use it as phone (which mi 10t was not at the moment not eaven a tablet).
Started to tempering with settings again sometimes i had sounds sometimes not but always temporary. after many attempts of factory reset putting the localisation and other startup settings i decided to set voice recognition from google assistant eaven i couldnt hear sound at boot logo, surprised the dots were jumping when i talked it came back alive !!! after full startup settings sound and mic was working - untill restart. tried to do few factoryresets/startup settings without voice - no sound. then i did it few times with voice recognition from google assistant - it worked every time, surprised i assumed there was something chewing in settings between miui and google assistant.
It stayed that way for a month. everytime that i had sound problem, factory reset and setting voice recognition solve it. Untill i decided to update google assistant when restarted the "voice recognition method" didnt work. only random tempering with dnd/silent sound settings and many factory restarts helped.
I found out that when u want to restart phone to get sound back, pushing vol- button hundreds times before restart eaven the volume is on bottom and silent mode/dnd is on and then just after miui starts pushing many times vol+ and disabling dnd/silent helps - but that is just workaround not solving problem.
Angry at damn mi 10t tried different things:
- unlocked bootloader
- flashed many official eu roms,
- downgrading and upgrading
sometimes i had sound but after tempering with settings never on startup. i sticked to android 11 roms in that time.
then:
- tried chinese android 11 roms (no luck)
- tried eu, chinese android 10 roms (no luck sometimes black screen - but after switching to android 11 i could use phone again)
- tried eu/chinese android 12 roms (never worked always black screen and backlight when switching to android 11 system worked - no sound)
All those roms were official and fastboot and i was always using miflash, when downgrading i simply deleted or rem two lines from "flash_all.bat":
rem fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
rem fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
- installed twrp
- wiped repaired data partition if needed
- every flash attempt was after full wipe/factory reset
- tried many different apps like toggle dnd/silance
- tried to repair system with tools like ccleaner and others
- tried wipe/clear cache on every possible app eaven those hidden 300+ apps
- found some solution with build.prop:
fix sound
build.prob remove
ro.config.media_vol_steps=30
ro.config.vc_call_vol_steps=14
but couldnt find those in my file maby different phone soft
- installed magisk and tried addons
* GSI Audio Stutter Fix - Mi NOTE 10 Lite (toco)
* Audio-Modification-Library_v4_0
* Magisk-Sound+ (2.2.0)
No luck im out of options right now but will still try untill i decide it is hardware maby hotair gun at qualcom? Can u guys suggest something else or maby i missed some options done it wrong? Heard about deleting all *.nomedia file but didnt chceck it yet and dont know if i got them. Usually using MIUI 12.5.8 or different eu 12.5 because 13 never worked and most 12.0 12.1 bootloop or not working. phone M2007J3SY rom usually RJDEUXM. If u gos any solution please write.
Ty for reading this elaborate, ill make it done or burn it xD
Uzul
Ps. bt headset still pairing but usbc/jack headset not recognized - no headset icon.
Uzul Warthlokkur said:
Hello
Im xda forum user sience many years but on this account im new (lost my old one). I remember flashing pda's, nokias and other ancient hardware , not an expert but quite experienced user. I had some break with flashing, tempering with soft and settings because of lack in time and other hobbies(3d designing, automatics, 3d printing, milling, programming plc's, and many others) i like to do things, if i want something, i ask "can i do it myself?". this is how i made telescope tracking the moon with camera attached to it. Anyway back to the point.
I came back to xda beecause of Xiaomi Mi 10t which i bought last year. It worked fine for half a year then 1st issue occured:
- when i was browsing internet phone went black and tried to reboot but couldnt boot into android. So i said to myself "broken soft time to flash new rom" couldnt do that because motherboard was fried and phone couldn't communicate to pc. fastboot didnt work etc. It went back on varranty, they replaced motherboard with new one.
It shouldnt be bad ive got new phone xD, wrong.
At work im cnc programmer/sometimes operator so i listen a lot of audiobooks, music. After 2 months of using "new phone" i experienced some stuttering on bluetooth headset, sometimes no audio. nothing that turning on/off bluetooth cant fix. I also used wire headphones when bt out of battery. That sound problems wasnt realy an issue for me.
Some time later i run out of battery couldnt make it to charger in 30 sec xD it died. Ive put it on charge to 100% then turned on at night. I belive in that time it auto upgraded itself and rebooted - lights woke me up. There was strange thing because i couldnt hear sound at logo which was present before. i assumed it was disabled at options and went back to sleep.
When i woke up i was checking what the damn thing done i was shocked because i couldnt hear any sound.
Symptoms:
- tried to call my wife, couldnt hear her and she couldnt hear me, messanger same
- no audio at youtube, video worked
- no notification sound
- xcom2 (game) crash on startup
- camera in video mode - crash suddenly
- netflix crash
Then i tried the bt headset, same thing as above. it could pair but no audio. strange thing was that i could hear messenger call when my wife was trying to call me, so i assumed software problem not hardware. tried wire headphones same result it was recognized as headphones, icon present, bt off.
Tried different things:
- phone restart (didnt help)
- wipe cache, factory reset, (didnt help)
- tempering with sound notification settings and rebooting (didnt help)
- safe mode (sound not working)
- upgrading software (no luck)
- factory reset (no luck)
- switching sim card then restart (no luck)
Then i went to quick settings toolbar there was suspicious thing: bell was wobbling as well dnd icon but not turned on just wobble once when quick toolbar rolled out. i hid it and rolled out again icons stood still. So i restarted phone and same thing occured - first roll out gray icons wobble, second roll stood still (no blue - not turned on on both attempts). Then i started to tempering with sound and notifications options dnd and silance settings included.
- turning on/off random settings, rebooting system many times, suddenly ive heard sound at booting logo. Ok so everything was fine, had sounds working properly: notification, yt, messenger, camera in video mode eaven xcom2 was working - everything was fine. Untill i decided to restart phone to chceck if it stays that way - it didnt. After reboot again i had no sounds. tried tempering with settings again, after many attempts sound came back. Now i didnt want to restart the damn thing. i left it on for 2 weeks without restart and sound was on no issues except stuttering (i could live with it). then i had some issues when somebody or i called someone - sometimes i couldnt hear them sometimes i couldnt be heard (turning on off speaker/mic while i was on line helped, sometimes not). angry i swithed to old phone to use it as phone (which mi 10t was not at the moment not eaven a tablet).
Started to tempering with settings again sometimes i had sounds sometimes not but always temporary. after many attempts of factory reset putting the localisation and other startup settings i decided to set voice recognition from google assistant eaven i couldnt hear sound at boot logo, surprised the dots were jumping when i talked it came back alive !!! after full startup settings sound and mic was working - untill restart. tried to do few factoryresets/startup settings without voice - no sound. then i did it few times with voice recognition from google assistant - it worked every time, surprised i assumed there was something chewing in settings between miui and google assistant.
It stayed that way for a month. everytime that i had sound problem, factory reset and setting voice recognition solve it. Untill i decided to update google assistant when restarted the "voice recognition method" didnt work. only random tempering with dnd/silent sound settings and many factory restarts helped.
I found out that when u want to restart phone to get sound back, pushing vol- button hundreds times before restart eaven the volume is on bottom and silent mode/dnd is on and then just after miui starts pushing many times vol+ and disabling dnd/silent helps - but that is just workaround not solving problem.
Angry at damn mi 10t tried different things:
- unlocked bootloader
- flashed many official eu roms,
- downgrading and upgrading
sometimes i had sound but after tempering with settings never on startup. i sticked to android 11 roms in that time.
then:
- tried chinese android 11 roms (no luck)
- tried eu, chinese android 10 roms (no luck sometimes black screen - but after switching to android 11 i could use phone again)
- tried eu/chinese android 12 roms (never worked always black screen and backlight when switching to android 11 system worked - no sound)
All those roms were official and fastboot and i was always using miflash, when downgrading i simply deleted or rem two lines from "flash_all.bat":
rem fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
rem fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
- installed twrp
- wiped repaired data partition if needed
- every flash attempt was after full wipe/factory reset
- tried many different apps like toggle dnd/silance
- tried to repair system with tools like ccleaner and others
- tried wipe/clear cache on every possible app eaven those hidden 300+ apps
- found some solution with build.prop:
fix sound
build.prob remove
ro.config.media_vol_steps=30
ro.config.vc_call_vol_steps=14
but couldnt find those in my file maby different phone soft
- installed magisk and tried addons
* GSI Audio Stutter Fix - Mi NOTE 10 Lite (toco)
* Audio-Modification-Library_v4_0
* Magisk-Sound+ (2.2.0)
No luck im out of options right now but will still try untill i decide it is hardware maby hotair gun at qualcom? Can u guys suggest something else or maby i missed some options done it wrong? Heard about deleting all *.nomedia file but didnt chceck it yet and dont know if i got them. Usually using MIUI 12.5.8 or different eu 12.5 because 13 never worked and most 12.0 12.1 bootloop or not working. phone M2007J3SY rom usually RJDEUXM. If u gos any solution please write.
Ty for reading this elaborate, ill make it done or burn it xD
Uzul
Ps. bt headset still pairing but usbc/jack headset not recognized - no headset icon.
Click to expand...
Click to collapse
If you're on miui based rom tap several times on kernel version and test the main speaker. If it doesn't work take the phone to service center.
zaqm said:
If you're on miui based rom tap several times on kernel version and test the main speaker. If it doesn't work take the phone to service center.
Click to expand...
Click to collapse
thats not true i belive it is software based issue, read what i wrote about google assistant before update. i could somehow unlock sound and mic using voice recognition setting on startup after factory reset. without it speaker mic tests failed after "voice recognition workaround" it passed flawlesly and everything worked fine. so when audio worked cit menu all test passed after reboot mic fail and speakers fail. when workaround it passed again. it could be qualcom chip fault(reballing or hotair gun on chip if somehow tin connections are not good or cold soldier, but that doesnt explain how i manage to make it work(if chip failed) by setting the voice recognition in google assistant) but it is not only this phone issue most ppl report this after miui update and reboot, same as me and on different phones mostly on miui 12.5.
Sorry for a messy response i hope it is readable, too many thoughts in my head, and my english is a bit rusty
Edit 1 Anyway ty for your response because of that ill try to downgrade google assistant to version the "workaround" worked or eaven get rid of that spying thing from cell phone. what i have seen eaven when im fasboot flashing roms the google soft stays at the same version. so it is maby on different partition not affected by flashing as well as settings for it. dunno right now didnt do that things for a long time and my knowledge is outdated in that matter 6 years a long time sience i tempered in roms and partitions. maby it is pointless because chinese roms do not use google apps but what if broken settings affect chinese roms as well - who knows.
Ps. maby my monologue help others and myself to clear my mind and get correct conclusions ill update u guys and myself
Ps. 2 service center is last resort when ill totaly give up, eaven then ill first try to get my hands on service MiFlash where there is more options, maby total wipe and setting new partitions without leftovers from prewious roms and settings.
Ps. 3 Im not the kind of person who just go to service center. i like problems and solving it by myself thats how knowledge goes from. i like to know how all is made how aluminum is extruded how electronics work, how to build this and that. knowledge is my goal and then using it to achive goals which i set myself.
Ps. 4 this is similar problem to mine but without elaborate :
Sound Issue: No internal speaker/No microphone/No sound by bluetooth
Hi guys, Im here to speak about my mi 10t who got some sound/mic issue. Everything was working good but one day, the phone muted himself on stock Rom. When i tried to use the tap recorder, the app said "verify if an app is using the microphone...
forum.xda-developers.com
Hey Man I have a really similar issue to yours
It's seems there's No proper solution for this issue
I tried contacting several devs but even they couldn't solve it
The log will say
9717 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19
9717 W AudioManager: updateAudioPortCache: listAudioPorts failed
I tried all the thing that you did
This actually happened after I was updating a rom of fw 13.0.6.0 EEA to 13 13.0.8.0 EEA
At first I thought this was one of the minor problems which would get fixed by clean flashing or installing stock rom But it seems that it even messes with the xiaomi activation thingy that you won't be able to connect to the Wi-Fi in the activation process.
cyb3rvirgin said:
Hey Man I have a really similar issue to yours
It's seems there's No proper solution for this issue
I tried contacting several devs but even they couldn't solve it
The log will say
9717 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19
9717 W AudioManager: updateAudioPortCache: listAudioPorts failed
I tried all the thing that you did
This actually happened after I was updating a rom of fw 13.0.6.0 EEA to 13 13.0.8.0 EEA
At first I thought this was one of the minor problems which would get fixed by clean flashing or installing stock rom But it seems that it even messes with the xiaomi activation thingy that you won't be able to connect to the Wi-Fi in the activation process.
Click to expand...
Click to collapse
mine happened after updated itself to 12.5.8. today i tried deleting *.nomedia files from root it didnt help. then i tried to boot into MIUI Rescue System (vol+, vol- and power button at the same time) tried to update device by wifi, here is what i got: "couldnt find updates MIUI-V12.5.11.0.RJDEUXM (N/A) -> ??" when system is on ive got notification that there is 13.0.8 update. tried this from android always black screen and backlight after update, sometimes bootloop. fixed bootloop with twrp but same black screen and backlight just without bootloop. will try something different. as soon as i will know more about present androids ill try to chceck system files and scripts in java json xml right now im not familiar with it that much. right now ill try to downgrade google apps (especially google assistant itself and releted apps) maby uninstall all of it if possible.
When I changed from stock rom to Lineage OS, it was a bit annoying, first I was getting an error on the sim card screen, that was just one time, but then I realized that there was no sound, I did not find any solution and trying to try other roms like Pixel Experience and Xiaomi.Eu, I accidentally found the solution, which was deleting the Dalvik Cache, I returned to Lineage OS and no longer received errors and the volume worked perfectly (to this day I only have an error related to multitasking but it's ok it's tolerable)
Greetings and sorry for my enlish
Puruixa said:
When I changed from stock rom to Lineage OS, it was a bit annoying, first I was getting an error on the sim card screen, that was just one time, but then I realized that there was no sound, I did not find any solution and trying to try other roms like Pixel Experience and Xiaomi.Eu, I accidentally found the solution, which was deleting the Dalvik Cache, I returned to Lineage OS and no longer received errors and the volume worked perfectly (to this day I only have an error related to multitasking but it's ok it's tolerable)
Greetings and sorry for my enlish
Click to expand...
Click to collapse
dalvik was deleted many times but never tried lineage os. ill try to boot to twrp from fastboot, wipe everything and then install lineage or xiaomi.eu then wipe dalvik and wipe under stock recovery which i never did like that (i mean two step wipe). maby this will help.
today i tried viper4android and it returned abnormal status of driver aswell on legacy mode.
what warries me right now is te issue with wire headphones the icon is not present anymore so i may broke some more xD. eaven with sound problems i had wire headphones recognized icon present - it is another known issue with xiaomi devices. im experiencing more and more bugs some of them fixed some not.
good for me that i like this kind of problems and solving them is like a hobby and another phone is used as phome, mi 10t is playground right now xD
Good luck with it
Anything turn out from this investigation? I am having the same issue (Chinese version of OP8P) and don't have OG firmware to go back; to the software within which the drivers are usable.
I had exactly the same problem you describe. I tried flashing both stock roms and custom roms but it didn't work. I tried everything but only today I find the solution:
after installing a new kernel https://forum.xda-developers.com/t/kernel-overclocked-no-gravity-2023-02-26-protonclang.4531497/ and cleaning the dalvik cache, the sounds are back
MicheleRoar said:
I had exactly the same problem you describe. I tried flashing both stock roms and custom roms but it didn't work. I tried everything but only today I find the solution:
after installing a new kernel https://forum.xda-developers.com/t/kernel-overclocked-no-gravity-2023-02-26-protonclang.4531497/ and cleaning the dalvik cache, the sounds are back
Click to expand...
Click to collapse
Excuse me, how did you clean the dalvik cache if twrp is not compatible with mi10T? (unable to mount storage problem) Thanks in advance
I also have the same problem. Did you find a solution?
Related
Hi all,
i've been using ARHD Roms since a few months and never had any serious issues with that (except proximity sensor fail ..) but now i'am a bit clueless.
Since flashing ARHD 6.1 (using SuperWipe first, no other Mods, everything was fine after flashing) and using it a few days i noticed two things:
First: Random Force close of different apps. I saw that even SuperUser app does FC every single time. Cleared cache - fine.
Second: I noticed that i somehow pressed 2 or more keys at the same time (i can reproduce it now - hold "power" button and shortpress "home"-button) and did a "screenshot" out of the box (in the ARHD FAQ-Thread is an info which says it does not work without modifications/3rd party tools) and - now it comes - ecaxtly since this day my power menu doesn't work anymore.
Long-pressing doesnt work, i can even hold it for 20 seconds and nothing happens until i stop pressing, then the screen goes off but no power menu appears - so the hardware of the button is fine, i still can power on the phone as well
Tried rebooting several times, even flashed ARHD 6.1 again (checksum is fine) but the issue still exists... everytime i'd like to reboot i need to use rom manager and boot in recovery or remove battery.
Is this a known bug? found nothing via search function :/
You can try this post:
http://forum.xda-developers.com/showpost.php?p=17623012&postcount=51332
Thanks, enabling the Secure Credentials fixed the problem. Unfortunately only until reboot, then the box isn't ticked anymore and i've to enable it again - but thanks anyway, i can live with that for now.
Strange issue ... i wondered why not more useres experiencing it, my phone is "stock" arhd 6.1 without any mods or somehting like that ...
I can confirm that his happends to me alot too.
On the same rom.
Still no solutions other than Secure credentials?
Same situation here. Although I update to 6.1.5 the problem still happens. Any idea rather than secure credential ?
Hi all,
I've been having quite a few problems with my month-old HTC 10, specifically with the camera (and the WLAN coverage, but at least that's working somewhat!) I finally unpacked it last week and have spent the whole week since attempting to fix the "Camera has stopped/Unable to connect to camera" problem. The selfie camera, however, is perfect and can be used in other apps, but attempting to switch to the camera on the back results in a freeze/force close. Considering I decided on the HTC 10 because of the camera quality, I'm a bit disappointed so far. A google search reveal a number of people having the same problem, but no real solution. Here's what I've done so far:
- Set up phone, comes with Nougat 7.0. Camera works at first, though seems to have problems with the auto focus. Camera app then updates overnight and stops working. Clear data/cache, remove updates, hard reset - no good. Flashlight does not work either, simply says "loading..." and stays like this indefinitely until closed.
- Factory reset, no change. Switch to safe mode, no change. Decided to unlock bootloader and install custom ROM after hearing that would fix it (I know, I know...I should have just sent it back at this point). Install Viper 5.10 + root with magisk, camera and flashlight still not working. Safe mode, not working. Full wipe in TWRP, RUU back to stock firmware (CID: HTC_034, flashed 2.41.401.3 signed firmware). Set up phone again on stock firmware, still no change in camera or flashlight.
- Install LeeDroid 10 3.7.0 custom ROM, root with magisk. I get a breakthrough here; turning off "OK Google" in settings gets the camera and flashlight working again! Still have the "laser autofocus blocked" issue, but I figure I'll deal with that later. Backed up with TiBu.
- Next day, decide to use a ROM that includes the latest security patches (got a bit annoyed waiting for HTC to push out the European updates, still on 1st January patch) so went for Resurrection Remix. Wipe, clean install etc. Camera stops working again, no change in safe mode. Wipe, clean flash back to LeeDroid, camera is no longer working, in normal mode or safe mode.
- Went through a bunch of custom ROMs at this point; ICE, Dirty Unicorns, LineageOS, then decided to try RR, LeeDroid and Viper again - camera still not working in normal mode or safe mode. With the ROMs that required GApps, used every package in both Open GApps and Dynamic GApps to install. No change to camera, Google Camera was unable to start as well.
- Flashed upgraded RUU (2.41.401.4 signed firmware) and went through the process of wipe/clean install custom ROM/test camera with all the above custom ROMs in normal mode and safe mode. No change in camera, though the ROMs were all excellently made
At this point I'm pretty stumped If it was a hardware problem, why did it work when I first installed LeeDroid, but not after? It's not been mishandled, it's just been sitting on my desk since I got it. The fact that it doesn't work in safe mode would suggest to me that ,maybe, a camera driver has been deleted somewhere along the way? I also tried a load of other methods I found on various message boards; flash it with no SD card inserted, flash without SIM card installed, etc. but absolutely nothing works.
Third party camera apps also don't work; most simply crash on starting. Open Camera says "Unable to access camera. Maybe being used by another app?", so I tried removing the permissions of all apps that had access to the camera except the camera itself - no change. Deleted cache/data/preferences of all apps - no change.
Finally, I had a look at the HTC diagnostics test using *#*# 3424 #*#* on the dialler - the camera test doesn't even show up! :crying:
I've run out of things to try at this point, so I'm posting this here to see if anyone can possibly shed some light on this very strange situation. Is there something I can do to fix it? Or should I start begging Amazon to give me a refund? Unfortunately I'm a week outside their 30 day return window...lesson learned for next time; if in doubt, send it back!
Oops, meant to post this in the Q and A forum. Don't want to spam a duplicate, is it possible to move it over?
Hardware issue. Contact HTC for a replacement. sounds like it may just not be connected. I had one with no working vibration notification, the motor would turn on, you could hear it, but the phone wouldn't vibrate. Got it replaced ASAP! I recommend you do the same!
FinnMacKool said:
Hi all,
I've been having quite a few problems with my month-old HTC 10, specifically with the camera (and the WLAN coverage, but at least that's working somewhat!) I finally unpacked it last week and have spent the whole week since attempting to fix the "Camera has stopped/Unable to connect to camera" problem. The selfie camera, however, is perfect and can be used in other apps, but attempting to switch to the camera on the back results in a freeze/force close. Considering I decided on the HTC 10 because of the camera quality, I'm a bit disappointed so far. A google search reveal a number of people having the same problem, but no real solution. Here's what I've done so far:
- !
Click to expand...
Click to collapse
Same issue here. The only thing that works for me (so far) is flashing back to a Marshmallow rom. HTC has been completely silent on this issue in terms of actually fixing the problem. They know the problem is there for only a small number of us and so aren't going to do anything about it. Fine. This was my first and will be my LAST htc phone. Buh bye htc, you'll never get another dime from me.
Did you fix the issue, coz i have the same in my HTC 10
Hi
follow my post in anildsouza73 blog..I will show how to fix it if someone really spoiled it...have a good day..
from yesterday morning the problem appeared to me. Initially, the difficulty in focusing, then rebooting the impossibility of opening the camera app and the flashlight. I found on Youtube the videos that showed the same problem. Is there a solution today?
Hi all
I found if I cleared my flashlight cache and then the camera cache, soft reset phone I could get the camera working again. Only problem now is the autofocus is not working properly. Any ideas for that?
Same problem. Focus stopped working, then I cannot launch camera app. Anyone found a solution?
Hi All, my redmi 5a auto rotate doesn't work, I don't know why but I've experienced a tragedy that maybe connected with this problem.
I use AOSP Extended ROM for Rolex in my Redmi 5A Device, as long as I use it I don't have any problem, but yesterday I've tried to restore my kernel into this ROM Stock Kernel ( I Use Direwolf Unified Before, Many Times I Try Other Kernel Also But And Never Had Such A Tragedy) After I Restored the original kernel, then I wipe my dalvik and cache as usual, BUT, Suddenly The Boot animation Stucked before it show's the AEX Logo, So I Think It Was A Bootloop Simple Problem, Than I Reinstalled My AOSP Extended OS, Than Something Happened, Even Since The First Boot It's Stucked At The Same Point, Than I Tried To Re-flash it again, and after that it still like that, so I was thinking that my External Memory Data Was Corrupted, So I Tried To Copy The File Directly From My PC To My USB OTG (I copied same AOSP ROM) than I reflash it but it still like before, than i start thinking if this ROM file (in my PC and SD card) is corrupted, so I tried to install PE ROM, But The Result Is Still Same As Before, Stucked At Boot Animation Than Forced Shutdown.
Well after that I think my device is get a serious problem such as hard brick or soft brick, than I tried to do clean flash to MIUI 10 Fastboot ROM With My PC, BUT the time elapsed is more long than usually (About 20 minute) waiting for booting and finally my device is normal, so I immediately install TWRP Custom Recovery (3.2.3-1 by FenFern) And Installing AOSP ROM Again (I Swear I Love This ROM) Everything seems normal no problem, restoring app, rooting, personalization, and etc.
Well the problem with auto rotate is coming when I see some funny videos on YouTube, my devices ONLY CAN ROTATE TO THE LEFT, AND CAN'T ROTATE AUTOMATICALLY AND CAN'T ROTATE TO THE RIGHT SIDE, I tried many game's app and watching some anime's in video player, Even If I Switch to auto rotate mode.
hi, you might have corrupted the persist partittion. check in other thread persist related issue. you can get a solution there. by the way does the other sensors working?
SandipS said:
hi, you might have corrupted the persist partittion. check in other thread persist related issue. you can get a solution there. by the way does the other sensors working?
Click to expand...
Click to collapse
Well yeah it's working, except the auto rotate
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?
EDIT: Apparently this was a result of using the wrong setting for enabling hotspot in PropsConfig. Because all that stuff was set during bootup, deleting apps wouldn't change the situation. Setting worked fine on my Pixel XL, but not here. Changed the setting and all is well.
--------------------------
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Might be quicker and easier to back up your required files and just factory reset.
Texan1 said:
Might be quicker and easier to back up your required files and just factory reset.
Click to expand...
Click to collapse
*sigh* I kinda made this post to avoid that step.
somethingsomethingroot said:
*sigh* I kinda made this post to avoid that step.
Click to expand...
Click to collapse
I know, it's just that it sounds like you've already disabled some things that could be causing it, which hasn't helped. If it was me, with something like constant reboots, I'd want to start fresh just to make sure they are eliminated for good
somethingsomethingroot said:
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Click to expand...
Click to collapse
I've seen reports of "random" (=not intentional) reboots after
+ booting up the phone
+ using the FP scanner
+ making videos or shooting photo
+ doing a firmware update (I've seen both reports of ppl that "officially" OTAed & used manual flashing)
+ doing nothing
+ doing something
Some were able to fix their issues by factory resetting, some needed replacement devices. Some reported that even after a factory reset, the issue still persisted, but they were able to fix it by NOT using a backup via cable, some reported that even the Google Drive backup "corrupted" their phone (fix after setting up everything by hand from scratch). Some even reported their issues to get fixed via a software update.
So it seems to be connected to hardware (= replacement device) and/or software simultaneously (=fix via reset).
Strange this is since there are also numerous reports of Samsung owners that upgraded to A12 about random reboots. So it might even be something Android 12 related, or it's just Samsung also implementing similar bugs without it being A12 related (unlikely, since the reports seem to be centered around people using the new A12 update).
I also had the random reboot problem (~ 6 times a day, when doing nothing, it just rebooted when the phone layed on the table in idle). I wasn't able to fix it via a reset, so I got a replacement device.
I also have the "random" reboot problem on my Pixel 3 since upgrading to Android 12 (never had any issues all the years I've been using that phone), so that issue is clearly caused by A12, but I haven't troubleshot it/ tried to solve it, since I don't actively use the phone currently.
Aside from trying a factory reset and minding the backup issue (especially backups that you got from phones that did NOT have Android 12), there is not much more that you can do (ofc you could also use the Pixel repair/android flash tool to do a "clean" install of Android on your phone). Next step would be to contact Google.