Related
After installing Radio 2.05.00.06.11 (dinc_ota.zip), my handset speaker audio disappears. Speakerphone and bluetooth work fine, but no luck with the internal speaker.
Heres the kicker:
Once I restore the 1.0 Radio, the internal speaker starts working again.
After lots of searching, this seems to be a very intermittent problem. I've only found two other people experiencing the same issue. Unfortunately I have not found a solution.
Does anybody have any idea as to what my next step should be to try and solve this?
Thanks!
I have the same problem...
heega1 said:
After installing Radio 2.05.00.06.11 (dinc_ota.zip), my handset speaker audio disappears. Speakerphone and bluetooth work fine, but no luck with the internal speaker.
Heres the kicker:
Once I restore the 1.0 Radio, the internal speaker starts working again.
After lots of searching, this seems to be a very intermittent problem. I've only found two other people experiencing the same issue. Unfortunately I have not found a solution.
Does anybody have any idea as to what my next step should be to try and solve this?
Thanks!
Click to expand...
Click to collapse
Try downloading a fresh copy of the update and running it again?
It's working just fine for too many people for it to be a problem with the update itself.
douger1957 said:
Try downloading a fresh copy of the update and running it again?
It's working just fine for too many people for it to be a problem with the update itself.
Click to expand...
Click to collapse
updating the radio twice will brick the phone! same one that is.
zeke1988 said:
updating the radio twice will brick the phone! same one that is.
Click to expand...
Click to collapse
not exactly. but, this radio isnt a image, its a patch. and a double patch is not the same thing... there is no error checking. dont do it!
I've tried re-installing the update 3 times from three sources. At first I thought it was the Froyo update so I went back to my nand backup and that didn't help, but once I downgraded the baseband it magically started working again.
So I tried it again. Re-downloading all the tools and packages. Only for it to happen again right after the Radio update. So I reverted back, cleared everything to factory, did a fresh install, then did the upgrade once more.... Still same problem.
Since it is such an intermittent issue, I'm thinking that maybe the hardware is to blame. The particular handset that I have is a warranty replacement from Verizon (blown speakers on first one). Maybe that has something to do with it.
Anyone have any other theories?
Thanks!
So I'm stumped. It's a pretty straightforward process, and I can't see where I'm going wrong.
Next Step: Warranty Replacement. We'll see if that helps. I'll be sure to record the serial number and other details of the phone before I send it back. Maybe we can find a pattern.
It will be a couple days before the new phone arrives. If you have something I can try, please suggest away!
Thanks!
I am having the exact same problem. I have tried both 2.x radios and both have the same effect. I want to use froyo but the only way to is to use speakerphone or a plugged in headset. I tried to take it in yesterday but the tech at verizonwireless told me to wait it out until 2.2 comes out to see if that fixes my problems. ( went in stock told them I was having the problem on stock radio) final problem being is when official does come out and it kills my headset speaker is it going to be too late to root my phone knowing the replacement I get will already be loaded with the new software.
Chicken and Egg
Unfortunately, unrEVOked has not developed a S-ON patch. This means that you will either have to take stock 2.2 which will be unrootable -or- you will patch forever, have S-OFF, get stock 2.2 and not be able to return the phone if the problem doesn't clear up.
Please keep that in mind when making your decision.
The replacement phone worked...
Not sure what the problem was, but it confirms my method for installing 2.2 wasn't flawed..
Thanks for all your help!
-j
I am trying to get verizon to send me a new one. They are not being very helpful right now. They said the audio issue is a software issue that should be fixed with the new update but might send me a new phone due to number of dropped calls. I have to stop in store tomorrow
Hello! I have very annoying problem with my Desire - microphone doesn't work. Voice Recorder records just white noise and other people can't hear me.
Phone was rooted more than a month ago. Since then, I was satisfied user of RCMixHD. The last changes I've done (on Sunday) were: update system to v0.12 and radio to 32.49.00.32U_5.11.05.27. I don't call very often, so I noticed the problem yesterday.
I've started solving problem by restoring backup - it hasn't helped. Next I have wiped data, reverted to standard ROM, reset factory data etc. and it also hasn't helped. Next step was downgrading radio to recommended 32.48.00.32u_5.10.05.30 and other older versions. This hasn't helped too. I have tried many times (between the changes) recording voice - sometimes I could hear the recording (with white noise of course) but very quietly.
Today I have unrooted the phone using RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe. Microphone still doesn't work.
Maybe, someone more experienced than me can help? Thanks in advance for any suggestions.
PS Phone isn't branded. I've got it since June.
The same here
I have unbranded Desire and facing the same problems and no solution found yet. I contacted HTC and they said that since I used unofficial ROM the waranty is voided and I should pay to get it fixed.
Did you find any solution? Thanks!
medomedo said:
I have unbranded Desire and facing the same problems and no solution found yet. I contacted HTC and they said that since I used unofficial ROM the waranty is voided and I should pay to get it fixed.
Did you find any solution? Thanks!
Click to expand...
Click to collapse
Yes run a RUU and don't tell HTC that you rooted your devices.
Thanks TheGhost1233 for the tip!
but I am still would like to find a software solution. I am not sure if its hw problem.
If you revert to stock and the problem is still there it's a hardware problem.
Thanks alot man, I am now reverting to UUR. If the problem persists I will send it to service and tell them that I used a modified ROM if they ask me because in this case I am to be blamed :-(
I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?
gasburger said:
I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?
Click to expand...
Click to collapse
Same problem. Did you solve this problem?
Has anyone found a permanent solution to this? Or at least a reason? My op 5t also stops responding randomly to the touch. This is really bad.
I also have this problem as well. It seems that many users have this issue. OnePlus should take a close look at it
I have been having this issue for more than 6 months. The problem came after one update during android Oreo if not mistaken (Which update i can't remember)
For my phone, the screen will be unresponsive during the below occasions:
1. After rebooting the phone, touchscreen is unresponsive for up to a minute
2. When browsing pictures in gallery
3. When taking picture using portrait mode
4. When google play is updating apps
5. When google photo is backing up photos.
I am also doubting if is a hardware or software issue, because it only happened in some occasion previously for my case. Tried wipe and install stable/open beta a few times, same thing.
After the latest open beta update, it got even worst, other than the above occasions, the screen start to stop working randomly (be it watching a youtube video or using chrome), its getting annoying as i need to restart my phone a few times a day.
I saw alot of people having this issue, but has yet to raise concern of OnePlus.
I've recently had the same problem, I was still running Lineage 15.1 and had not updated my firmware in months because the official builds switched to 16, then suddenly 2 weeks ago the touch screen stops responding while I was actually using it. Reboots didn't help, clearing cache and flashing lineage didn't help. In the end I somehow got it to work again by flashing the last open beta - but even then it didn't work right after flashing it, I had to leave it over night then it mysteriously started responding again in the morning.
I've just had it happen again and I have tried removing the screen protector and completely discharging the battery as some people on the oneplus forum have reported this helps, but it did not work for me. I really can't be bothered going through the whole process of re-flashing open beta then flashing back to lineage and installing all my apps an restoring my data again, but the only other option at this point is to try take it apart to check the screen is still connected to the motherboard properly....
solution
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,
karyy said:
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,
Click to expand...
Click to collapse
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie
Facing same issue..
I have a similar issue too..
It started several months ago, when the screen used to randomly stop working, a quick hard reboot usually solved the issue.
But about a month ago, the screen stopped responding altogether and any amount of reboot did not work. So too the device to Oneplus service, there they flashed it to 9.0.7, and the screen started working again, and continued working for a few more hours, until it stopped responding again.
Tried flashing several times using the unbricking tool, but all efforts in vain.
Finally after a month or so, I bought a new phone, and today I just wanted to see if anything has changed on OP5T, and to my surprise, the touch screen started working again.
So this time I enabled USB Debugging, permanently enabled OTG, so that even if the screen stops working, I can use an external keyboard/mouse.
But OP5T is no longer my primary device, and hence I have moved on to a different manufacturer, as I saw absolutely no point in buying another Oneplus and god knows what will happen a year down the line...
Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.
chandle-stick said:
Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.
Click to expand...
Click to collapse
I had the problem. Had to send it back to OnePlus. They replaced the cpu under warrenty. Call 0neplus.
i have this problem on LineageOS 16, in stock is good
k-ninja said:
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie
Click to expand...
Click to collapse
I was just searching this issue online. I'm currently facing it as well.
Rebooting the phone makes it go away. I face this issue while charging the phone via official dash charger.
I'm running stock Oxygen OS 5.1.7 running Oreo 8.1.0. I faced this issue 6-8 months ago as well. I cleared 7gb free space in my phone then it started working fine then. My device is 64GB variant. I never updated to Android Pie.
This is a major problem in OnePlus 5 and 5t. I've seen many posts on both XDA and official oneplus forums but found no guaranteed solution so far. I was thinking of flashing custom kernel but then saw here that people are still facing this issue in custom ROMs.
I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.
k-ninja said:
I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.
Click to expand...
Click to collapse
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95
archz2 said:
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95
Click to expand...
Click to collapse
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
archz2 said:
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I'm not running OOS now, but I have had the issue occur while I was. I am just re-flashing OOS to get the touchscreen to work again, but actually I can't even get the setup wizard to work once the phone boots (hangs on the "just a sec" screen), so I am usually flashing another custom ROM once the screen works again. I managed to get to about 6 hours of normal usage last night before the screen stopped responding again - after fighting with the phone all day and most times not getting much past installing magisk modules.
I am starting to think the problem is related to either Magisk, or the riru kernel hooking modules necessary for Xprivacylua (which is mandatory to install IMO) - I had been using the YAHFA module mostly but yesterday I tried Sandhook to see if it made any difference - that was when I managed to get to 6 hours instead of 30 minutes, but it was also when I went back to Magisk 19.3 instead of installing 20.2. Now that I think back, I am wondering if it was upgrading Magisk from 19.x to 20.x that made the issue resurface after a couple of months without it.... Can't remember for certain, but it seems like the most plausible explanation. I tried flashing Magisk uninstaller this time when the screen stopped, but it didn't help - only reflashing back to stock works (sometimes it even takes a few goes). Whatever the problem is, it seems like it is tripping some hardware related switch which only gets reset when installing stock FW.
the other thought I had was that perhaps the hooking framework is getting in the way - like it intercepts the screen touches before they are processed, but it bugs out for some reason and they never get passed on to the OS. I don't know enough about how it works honestly, or any idea how to go about debugging such a weird problem, so no way to look into it.
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
I'm close to my wits end here. IF the problem turns out to be magisk related, it's pretty much new phone time - I doubt even if I logged a bug report it will get looked at any time soon much less resovled, and I simply refuse to run an android phone without xprivacylua.
k-ninja said:
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
Click to expand...
Click to collapse
Edexposed is for Pie ROMS as there's been no development for Pie from official developer for xposed. Chances are you were running xposed only on Oreo 8.1.0.
Today I flashed Franco Kernel on my phone, been running smooth so far. I used to get non-responsiveness while dash charging specifically. Let's see how it goes. Will keep you updated.
Bugger it... I managed to get to 4 days or so after flashing back to LOS 16.1 / Magisk 19.3 / Edxposed YAFHA / Franco kernel, but it has just crapped out on me again.
This time I has tried a slowly-slowly approach, at first running just the stock OS and apps for a few hours, then gradually started installing magisk, riru, edexposed, then finally xprivacylua - Didn't have any problems up to there. Then I installed pico gapps, and used the Play store to do a fresh install of Mobius Final Fantasy instead of restoring from Titanium backup (this game is actually the only real reason I need gapps at all :-/). Mobius is a PITA because its like a 5Gb download, so it takes a long time to reinstall rather than restore from TB. Anyway it seemed like it was working ok for a few days after the fresh install but I just picked up the phone as couldn't unlock it. I have noticed that often the problem does occur while I am playing the game and I have wondered if there is something about it which makes it more likely to trigger, but it can't be the only thing as it happens even during the setup wizard sometimes.... bloody infuriating.
Anyway... not sure what to do now. Really CBF going through the back-to-stock dance again. Meh.
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?
Hey there,
in all my years using/modding android phones I was never this lost on finding the issue.
My Oneplus 5t was unlocked, had latest blue_spark TWRP 3.40 recovery and stock oos 10.0.0 with the blue spark kernel and magisk installed. I just upgraded to the 8t and wanted to revert my phone back to stock. So I made a nandroid backup in TWRP and used the unbrick tool to get the phone in the fastest way possible fully wiped back to stock.
(https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 OOS 5.1.7).
Well after my phone was fully stock I was already kinda suspicious about it not finding any OTA updates and manually installed the latest oos 10.0.1 update. First it seemed like everything was working just fine but then I realised that the camera is not starting anymore and gives me the error "Error starting camera" ("Fehler beim Öffnen der Kamera). Since then I have tried everything possible for 2 days but I still am unable to fix the issue.
Everything I tried.
1. deleting camera app data/cache and phone cache in stock recovery
2.factory resetting the phone
3.Using the latest 9.0.11 unbrick tool from this thread https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890
-with this my wifi was not working but the camera was working again
- and this also showed me (while using mobile data) that there is a ota update available (oos 10.0.1)
- after updating my wifi was working and the camera was not working
4.Using at least 7 or 8 different unbrick versions (still from this thread here https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890)
- here I noticed that as soon as I had a android version below 9 it would not show me available ota updates and would not even let me manually update but camera and wifi was working
5. unlocking the bootloader, flashing twrp 3.40 and restoring my nandroid backup
- camera is not working
So as you guys can see I am really close on losing my mind with this phone and I would appreciate any help you can give me :fingers-crossed:
// looks like I need to send in my phone to Oneplus
//Oneplus "certified" service in poland was unable (my guess is they did not even bother) to find the issue and quoted a 300€ repair bill for changing the mainboard ^^