Related
Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.
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?
Hello everybody.
I have an issue with the Poco F3 regarding signal and networking.
After the last update to MIUI 12.5 and later MIUI 13, my phone was having issues making and receiving calls and also using mobile data.
Before those updates, I had no issues whatsoever.
I unlocked my bootloader and decided to try a custom rom, thinking it will solve this issue but nothing has changed.
I have "no service" in areas were many other phones (xiaomi and cheap ones at that etc) have at least 4g. Other times, while I do have service, I can't make or receive calls and even if I can, it's dropping after the first minute or so. Trying to use mobile data is a mess too, working rarely and most of the times I get that exclamation mark and cannot access the internet. It's starting to cause issues at work.
Note, that I use the phone with dual sims from different carriers and the issue is the same. I tried using only a single SIM thinking it might have something to do with dual sims but nothing.
I tried everything, from factory reset, to reseting network settings, airplane mode for 30seconds, custom roms, custom apns etc etc.
The sims work as they should on a poco m3 that I also own, but on the F3 the issue remains.
Now, the issue is much work with android 12, both with MIUI and custom rom (using PixelOS at the moment).
Do you think it is a hardware issue? Should I try an android 11 custom rom and see if the issue is fixed? Is there anything else I should try?
It's driving me crazy and since it's causing work related issues I am thinking of just getting a new phone at this point.
Thanks in advance.
crashpoum99 said:
Hello everybody.
I have an issue with the Poco F3 regarding signal and networking.
After the last update to MIUI 12.5 and later MIUI 13, my phone was having issues making and receiving calls and also using mobile data.
Before those updates, I had no issues whatsoever.
I unlocked my bootloader and decided to try a custom rom, thinking it will solve this issue but nothing has changed.
I have "no service" in areas were many other phones (xiaomi and cheap ones at that etc) have at least 4g. Other times, while I do have service, I can't make or receive calls and even if I can, it's dropping after the first minute or so. Trying to use mobile data is a mess too, working rarely and most of the times I get that exclamation mark and cannot access the internet. It's starting to cause issues at work.
Note, that I use the phone with dual sims from different carriers and the issue is the same. I tried using only a single SIM thinking it might have something to do with dual sims but nothing.
I tried everything, from factory reset, to reseting network settings, airplane mode for 30seconds, custom roms, custom apns etc etc.
The sims work as they should on a poco m3 that I also own, but on the F3 the issue remains.
Now, the issue is much work with android 12, both with MIUI and custom rom (using PixelOS at the moment).
Do you think it is a hardware issue? Should I try an android 11 custom rom and see if the issue is fixed? Is there anything else I should try?
It's driving me crazy and since it's causing work related issues I am thinking of just getting a new phone at this point.
Thanks in advance.
Click to expand...
Click to collapse
Rollback miui first to any android 11 version, see if the issue remains.
Then if you want you can flash custom roms and such... Your firmware got updated to android 12 when you upgraded miui , installing custom ROM won't downgrade it that's why you want to rollback miui
Thank you for your reply.
I need some time to do this proccess since I am practically 24/7 on call, but I will surely give it a shot when I get the chance.
Just a question though. Is it something common with this phone? A quick google search shows it happens with android 12 on the oneplus phones, but I got nothing for the poco f3.
Some time ago, with a similar issue, all I had to do was flash a kernel and it got fixed. Do you think there is a chance it is kernel related?
crashpoum99 said:
Thank you for your reply.
I need some time to do this proccess since I am practically 24/7 on call, but I will surely give it a shot when I get the chance.
Just a question though. Is it something common with this phone? A quick google search shows it happens with android 12 on the oneplus phones, but I got nothing for the poco f3.
Some time ago, with a similar issue, all I had to do was flash a kernel and it got fixed. Do you think there is a chance it is kernel related?
Click to expand...
Click to collapse
No idea... I don't think kernel houses firmware components tho , they live in their own separate partition
You can use DSU Sideloader. This allows you to boot into Android 11 and check Cell-connectivity & Wi-Fi, without touching your Main OS.
Basically, you download the Android 11 GSI, extract the "system.img", set up the app (either through Root or ADB), select "system.img" and Install.
That app utilizes Android's DSU feature, but lets you install any GSI you feed it.
Android has a built-in 'DSU Loader' in Developer Options, but it only lets you install the Android 12 and Android 13 Beta GSI, not older ones like Android 11. ^^
Note: GSI's don't work on Xiaomi.eu Custom ROM. May also not work on other Custom ROMs. ^^
cyanGalaxy said:
You can use DSU Sideloader. This allows you to boot into Android 11 and check Cell-connectivity & Wi-Fi, without touching your Main OS.
Basically, you download the Android 11 GSI, extract the "system.img", set up the app (either through Root or ADB), select "system.img" and Install.
That app utilizes Android's DSU feature, but lets you install any GSI you feed it.
Android has a built-in 'DSU Loader' in Developer Options, but it only lets you install the Android 12 and Android 13 Beta GSI, not older ones like Android 11. ^^
Note: GSI's don't work on Xiaomi.eu Custom ROM. May also not work on other Custom ROMs. ^^
Click to expand...
Click to collapse
That's a cool feature and thank you so much for the reply.
However, when trying it, I get stuck on the Poco logo and then straight to recovery. So I guess it doesn't work on the rom I am using.
Rebooting back to system from TWRP works as it should, so there are no further issues.
Tried the two official images from google, and the result is exactly the same.
crashpoum99 said:
That's a cool feature and thank you so much for the reply.
However, when trying it, I get stuck on the Poco logo and then straight to recovery. So I guess it doesn't work on the rom I am using.
Rebooting back to system from TWRP works as it should, so there are no further issues.
Tried the two official images from google, and the result is exactly the same.
Click to expand...
Click to collapse
Hm, I don't know.
You just need an unlocked bootloader (in most cases apparently).
When it didn't work for me, it was solely because of the Custom ROM Xiaomi.eu. Doesn't work at all there.
You're on Stock MIUI, I think, and it should work there normally. For me it does.
cyanGalaxy said:
Hm, I don't know.
You just need an unlocked bootloader (in most cases apparently).
When it didn't work for me, it was solely because of the Custom ROM Xiaomi.eu. Doesn't work at all there.
You're on Stock MIUI, I think, and it should work there normally. For me it does.
Click to expand...
Click to collapse
That's all true I guess.
But as I stated, I am on the PixelOS custom rom at the moment.
Just to see if the issue was MIUI specific, turning out it isn't.
I will return to MIUI 12.5 when I get the chance regardless.
crashpoum99 said:
That's all true I guess.
But as I stated, I am on the PixelOS custom rom at the moment.
Just to see if the issue was MIUI specific, turning out it isn't.
I will return to MIUI 12.5 when I get the chance regardless.
Click to expand...
Click to collapse
Did you ever get the signal problem solved?
narmak said:
Did you ever get the signal problem solved?
Click to expand...
Click to collapse
No, not at all unfortunately. Tried everything, even downgrading and switching around custom roms.
I figure it's a hardware issue and have since swapped my sim to my older Mi 9 Lite and use that device only for calls and data hotspot.
If, however, you have some solution to propose I will gladly give it a shot!
Hi, I also got myself the Poco F3 in June 2022.
Some days ago (~end of September) it started having little to no signal in places that I usually had good signal coverage.
I use 2 SIMs. I tried any combination of SIM as well as single SIMs.
Signal is bad and even if the indicator shows signal with severals bars, calls are not going out nor can I receive calls.
MIUI is
I thought of resetting the phone but after reading this thread I prefer to return the phone as long as it is still stock rather than wasting my time.
There are several posts about this issue on Amazon as well.
Same thing happening to me. This is a good smartphone but sadly, it wasn't just me that is having the same issue.
Same here. Simcard works fine in my Mi 8 and iPhone 7. Went back from LineageOS to MIUI, but MIUI tells me the Simcard "can't be activated" and doesnt get signal at all. With my Mi 8 i have 4G coverage.
I do have the exact same problem.
Tried different roms A11+A12, MIUI+Custom, even opened it up to check if the antenna cable was loose.
Has anybody fixed that problem?
did you manage to fix it? I had the same problem in pixelOs and now I want to install pixel experience but it worries me
gurripato said:
did you manage to fix it? I had the same problem in pixelOs and now I want to install pixel experience but it worries me
Click to expand...
Click to collapse
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Xblade234 said:
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Click to expand...
Click to collapse
Thanks for the hint. I will try it myself and report then...
I'm on the latest xiaomi.eu weekly beta and I do sometimes have a signal, but it's really unstable.
Xblade234 said:
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Click to expand...
Click to collapse
Are you using 5G or LTE data plan?
Xblade234 said:
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Click to expand...
Click to collapse
Problem is still there...
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?
Hi everyone,
I have an unmodified Xiaomi 10T lite MIUI Global 13.0.8.0 (SJSEUXM) Stable stock rom. The problem is that it's developed a very strange issue where ALL incoming calls show as UNKNOWN. Just to be clear, the numbers coming through are not being withheld.
Here's the even more strange issue - A few days ago, I decided to factory reset it and when it loaded up for the very first time and the setup goes through standard questions such as asking for WIFI, google apps info - If I don't complete these standard details and get someone to call me, then the incoming numbers are coming through fine, but as soon as I continue the setup, entering my WIFI, google login/apps info, it ends up back with the same issue of incoming numbers showing as unknown. I tried to factory reset it several times to be sure it's not a one-off issue, but same problem again and again. To be 100% sure that it was nothing to do with the simcard or my way of setting up, I used a different backup phone and setup everything on there just fine without any issues at all.
This has led me to believe that there is something wrong or corrupt with the rom and I believe a reflash should resolve this issue.
So I have the following question:-
Is it possible wipe out any cache/data of the current rom that will clear everything?
If the answer to the above is no, how can I flash the current stock rom with another copy of the latest stock rom?.
If I have to flash another rom, how I can do this and would this require the bootloader to be unlocked?
Thanks very much for all your help.
wowandroid
Sorry, I've not had a reply, so I'm BUMPING this thread.
Thanks