Related
I have routed my HTC One X, afterwaeds my audio is failing.
I have tryed to run function audio test, but it will not complete the test, and restart the phone.
If I plug my headset to the phone, the audio wirks normally.
The issue is about all the audio on the phone, exept the alarm and ringtone.
If I try to chose a ring or alarmtone, the phone will freeze and restart.
Can anyone please help me...?
Yours sincerely, Piet
Try a factory reset.
Electrostatic King said:
Try a factory reset.
Click to expand...
Click to collapse
Factory reset is not possible, when the phone is rooted.
pietmomberg said:
Factory reset is not possible, when the phone is rooted.
Click to expand...
Click to collapse
Where did you read that?
pietmomberg said:
I have routed my HTC One X, afterwaeds my audio is failing.
I have tryed to run function audio test, but it will not complete the test, and restart the phone.
If I plug my headset to the phone, the audio wirks normally.
The issue is about all the audio on the phone, exept the alarm and ringtone.
If I try to chose a ring or alarmtone, the phone will freeze and restart.
Can anyone please help me...?
Yours sincerely, Piet
Click to expand...
Click to collapse
Had similar problems, turned out that i flashed wrong boot.img, flashed the right one and everything worked fine.
Electrostatic King said:
Where did you read that?
Click to expand...
Click to collapse
I have ClockworkMod installed, so I can only restore the backups made in ClockworkMod.
Shailak said:
Had similar problems, turned out that i flashed wrong boot.img, flashed the right one and everything worked fine.
Click to expand...
Click to collapse
The flash file I used was a img file sent from HTCdev.
pietmomberg said:
The flash file I used was a img file sent from HTCdev.
Click to expand...
Click to collapse
Go for a factory reset via settings - storage. Then see if it works or not.
If not, you might as well go for hard factory reset.. But keep in mind to backup data and take care of other stuff.
This is a problem, as already mentioned, with the flashed boot.img. Flash a good one and everything will be fine. Happened to me too.
Yesterday I answered a phone call while playing the Family Guy Game (The Quest For Stuff) and using my 3G. As usual, the game had stopped when the phone call rang but the music from the game kept playing in the backgound while I was talking with the other person. The phone was very slow during this whole process (starting a little bit before the first phone call).
After hanging up the phone, I tried many times to call the other person to no avail. Tried to call other people and even emergency numbers. VoIP still works, headphones/speakers also works and the other person can listen to me when I call. Seems to me to be a software problem rather than hardware.
Here is what I have tried so far:
- Rollback to previous CM version;
- Wipe data/Clear Cache/Reinstall phone dialer;
- Uninstall the game+data, uninstall the dialer and reinstall it;
- Boot phone into safe mode.
I am using 11-20140607-NIGHTLY-n7100 on Samsung Galaxy Note II N7100.
I am running out of options here and I would really appreciate some help.
Togatheone said:
Yesterday I answered a phone call while playing the Family Guy Game (The Quest For Stuff) and using my 3G. As usual, the game had stopped when the phone call rang but the music from the game kept playing in the backgound while I was talking with the other person. The phone was very slow during this whole process (starting a little bit before the first phone call).
After hanging up the phone, I tried many times to call the other person to no avail. Tried to call other people and even emergency numbers. VoIP still works, headphones/speakers also works and the other person can listen to me when I call. Seems to me to be a software problem rather than hardware.
Here is what I have tried so far:
- Rollback to previous CM version;
- Wipe data/Clear Cache/Reinstall phone dialer;
- Uninstall the game+data, uninstall the dialer and reinstall it;
- Boot phone into safe mode.
I am using 11-20140607-NIGHTLY-n7100 on Samsung Galaxy Note II N7100.
I am running out of options here and I would really appreciate some help.
Click to expand...
Click to collapse
Might be missing drivers.
There's an app on Play Sore', named 'Volume Booster+', give a try with that.
m.b.jikre said:
Might be missing drivers.
There's an app on Play Sore', named 'Volume Booster+', give a try with that.
Click to expand...
Click to collapse
I'll give it a try then. But how could a driver be missing in my case?
Togatheone said:
I'll give it a try then. But how could a driver be missing in my case?
Click to expand...
Click to collapse
I said 'Might be!'.
Because I had also got this problem.
have you muted all sounds? unmute your phone and up the volume and then reboot your phone.
m.b.jikre said:
I said 'Might be!'.
Because I had also got this problem.
Click to expand...
Click to collapse
I see. Even installing the app it didn't work. I had to resort for a factory reset + complete wipe of the phone =/ But thanks for the help!
weebeast said:
have you muted all sounds? unmute your phone and up the volume and then reboot your phone.
Click to expand...
Click to collapse
Tried that to. No luck though.
Togatheone said:
I see. Even installing the app it didn't work. I had to resort for a factory reset + complete wipe of the phone =/ But thanks for the help!
Click to expand...
Click to collapse
With this one https://play.google.com/store/apps/details?id=wait.what.volumebooster ,or anything else?
If yes then its your hardware problem.
Are you saying a factory reset didn't work, nor a clean install of cm?
If so, return to a stock rom (match your bootloader to decide which stock rom - at least 4.1.2 and no higher if you aren't knoxed yet). Twice on two phones I've have issues with cm where a stock rom flash and then return to cm was the only solution I could find.
EmptyArea said:
Are you saying a factory reset didn't work, nor a clean install of cm?
If so, return to a stock rom (match your bootloader to decide which stock rom - at least 4.1.2 and no higher if you aren't knoxed yet). Twice on two phones I've have issues with cm where a stock rom flash and then return to cm was the only solution I could find.
Click to expand...
Click to collapse
I did the factory reset and it worked. And today (again) the same bug happened right after launching the Family Guy game. I am trying other solutions before doing a factory reset again.
m.b.jikre said:
With this one https://play.google.com/store/apps/details?id=wait.what.volumebooster ,or anything else?
If yes then its your hardware problem.
Click to expand...
Click to collapse
Tried the app and yet again, it didn't work. And it is not hardware, since the speaker still works.
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Taran3105 said:
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Click to expand...
Click to collapse
Also the volume keys are not working.
no brothers both the capacitive buttons and volume rockers work flawlessly on 4.1.0
all is working for me :-/
Working fine for me.
Working fine for me. Seems like a temp issue or a wrong flash to me. You can try wiping system and flash full zip. If you are fully stock, i would advise to perform a factory reset.
Taran3105 said:
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Click to expand...
Click to collapse
Sounds like a firmware issue. I suggest a full reflash.
I did a clean flash 4.0.3&4.1.0 OTA. Sometimes pulling down the notifications doesn't darken the background.
Clean flash ..stop making up bs posts
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
croques said:
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
Click to expand...
Click to collapse
As i have been saying repeatedly, the OTAs from OnePlus suck.
Clean flash the full ROM.
andrneumann said:
I did a clean flash 4.0.3&4.1.0 OTA. Sometimes pulling down the notifications doesn't darken the background.
Click to expand...
Click to collapse
Please PM me if you ever find a fix for this.. it forced me to use another ROM
Never call it Touch ID... This is not Apple.
works fine here clean flash
azaidi said:
Please PM me if you ever find a fix for this.. it forced me to use another ROM
Click to expand...
Click to collapse
Clean flashed again, now with OOS full zip 4.1.0, same thing. Pulling down notifications not always darken the rest of the screen. Still looking for a fix.
Factory reset solved the problem.
croques said:
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
Click to expand...
Click to collapse
I could never do that
andrneumann said:
Clean flashed again, now with OOS full zip 4.1.0, same thing. Pulling down notifications not always darken the rest of the screen. Still looking for a fix.
Click to expand...
Click to collapse
Did u find anything?
having the same issue
guess very few are having this issue (not many reported)
Anyone who's shortcut to for example a document on the home screen doesn't work anymore?
I already deleted the shortcut and made a new one, but still doesn't work
Ronak Chandak said:
Did u find anything?
having the same issue
guess very few are having this issue (not many reported)
Click to expand...
Click to collapse
I have the same issue...
I´m using the latest firmware available for oneplus 3 and the volume on call is low! Using whatsapp the volume is good.
I´ve instaled and existing fix and the problem is solved but everytime that oneplus launch an firmware update I need to root the phone and install the fix!
Anyone with the same problem?
romaolp said:
I´m using the latest firmware available for oneplus 3 and the volume on call is low! Using whatsapp the volume is good.
I´ve instaled and existing fix and the problem is solved but everytime that oneplus launch an firmware update I need to root the phone and install the fix!
Anyone with the same problem?
Click to expand...
Click to collapse
I have the same. Which fix do you installed?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
sakarya1980 said:
I have the same. Which fix do you installed?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
I use this fix https://androidfilehost.com/?fid=673368273298967516 - TWRP-OxygenOS-Low-InCall-Volume-Fix.zip
But in every update that is launched by oneplus you need to install it.
romaolp said:
I use this fix https://androidfilehost.com/?fid=673368273298967516 - TWRP-OxygenOS-Low-InCall-Volume-Fix.zip
But in every update that is launched by oneplus you need to install it.
Click to expand...
Click to collapse
Does this fix still work? I need to find a solution to the low volume when using the earpiece on the latest OxygenOS (5.0.1) with Oreo 8.0. I thought was a configuration issue, so tried a factory reset but the issue continues.
If I try this, when installing TWRP recovery, the device will lose all data, right? or this will not be the case?
pulsorock said:
Does this fix still work? I need to find a solution to the low volume when using the earpiece on the latest OxygenOS (5.0.1) with Oreo 8.0. I thought was a configuration issue, so tried a factory reset but the issue continues.
If I try this, when installing TWRP recovery, the device will lose all data, right? or this will not be the case?
Click to expand...
Click to collapse
Unlocking bootloader or wiping internal storage will result in loss of data. Mere flashing TWRP, if your bootloader is unlocked already, will not affect your data.
tnsmani said:
Unlocking bootloader or wiping internal storage will result in loss of data. Mere flashing TWRP, if your bootloader is unlocked already, will not affect your data.
Click to expand...
Click to collapse
Thank you @tnsmani. Yes, I just remembered that. I don't recall unlocking the bootloader on this device before.
So, can anyone using OxygenOS with Oreo 8.0 confirm if this patch works, I could go ahead and try it. It would suck going to the steps and wiping everything for it not to resolve the low volume issue.
Thanks!
Low volume in custom roms using nos
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Code:
/system/vendor/etc/mixer_paths_tasha.xml
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
davide136 said:
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Code:
/system/vendor/etc/mixer_paths_tasha.xml
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
Click to expand...
Click to collapse
I OEM unlocked my OP3 and then flashed TWRP (3.2.1-0). After flashing, I rebooted into recovery to make sure TWRP was installed. Then I rebooted the system. After booting system, it went back to stock recovery (when I checked again).
Tried again flashing TWRP and flashing your attached zip file immediately before rebooting the system again. Still, very low volume on call and it also went back to stock recovery again. How can I avoid this? Is it goes back to stock recovery does it means the patched file will be overwritten?
When flashing TWRP, do I need to "allow system modifications" the first time TWRP is flashed? I read that will cause a boot loop. I really don't need root, just need to be able to have the volume louder.
Thanks!
Does it give you any error during flash of the zip?
pulsorock said:
I OEM unlocked my OP3 and then flashed TWRP (3.2.1-0). After flashing, I rebooted into recovery to make sure TWRP was installed. Then I rebooted the system. After booting system, it went back to stock recovery (when I checked again).
Tried again flashing TWRP and flashing your attached zip file immediately before rebooting the system again. Still, very low volume on call and it also went back to stock recovery again. How can I avoid this? Is it goes back to stock recovery does it means the patched file will be overwritten?
When flashing TWRP, do I need to "allow system modifications" the first time TWRP is flashed? I read that will cause a boot loop. I really don't need root, just need to be able to have the volume louder.
Thanks!
Click to expand...
Click to collapse
After flashing twrp.. Reboot into recovery and root your phone
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Is there a similar file for low loudpeaker volume fix?
davide136 said:
Does it give you any error during flash of the zip?
Click to expand...
Click to collapse
No, no error at all. Everything looks like it worked fine. just after reboot system, it seems it did nothing the patch. Then when rebooting recovery, it was reverted to stock.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
drfox96 said:
After flashing twrp.. Reboot into recovery and root your phone
Click to expand...
Click to collapse
So rooting is required to avoid twrp being replaced by stock recovery again?
pulsorock said:
No, no error at all. Everything looks like it worked fine. just after reboot system, it seems it did nothing the patch. Then when rebooting recovery, it was reverted to stock.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
So rooting is required to avoid twrp being replaced by stock recovery again?
Click to expand...
Click to collapse
Yes
davide136 said:
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
Click to expand...
Click to collapse
Hi, I tried your fix on Open Beta Experience ROM 8.0. The volume issue was sorted but it broke the wake up system. I use face unlock and the moment I click any button, it wakes up my screen and looks for my face. After this patch, don't know how but phone stopped waking up. I had to use my fingerprint to unlock the phone. No other button was waking up the phone. Also the phone started getting hot and there was a tremendous amount of lag. I had to reflash the original OS to get it back to normal.
Know why ?
phrozenwire said:
Hi, I tried your fix on Open Beta Experience ROM 8.0. The volume issue was sorted but it broke the wake up system. I use face unlock and the moment I click any button, it wakes up my screen and looks for my face. After this patch, don't know how but phone stopped waking up. I had to use my fingerprint to unlock the phone. No other button was waking up the phone. Also the phone started getting hot and there was a tremendous amount of lag. I had to reflash the original OS to get it back to normal.
Know why ?
Click to expand...
Click to collapse
I can tell you that i tested with my phone and this never happened, considering that's not touching any file but this "/system/vendor/etc/mixer_paths_tasha.xml", I think it's something else causing what happened to your phone. Did you flash something else? Otherwise i'll take it down
amg_driver said:
i took a look in this file/fix.
my advice: dont flash this. imo the values are set too high and this fix could damage the hardware. as davide136 said "almost broke my ear"...
Encloused my fix created for latest NOS (Oreo).
But should work on other roms as well (if path to mixer_paths_tasha.xml is /system/vendor/etc/)
Try "88-fix". If it's a bit too low for you than flash "90-fix" - as filename suggets, its 2db louder.
Click to expand...
Click to collapse
Is it Oneplus 3T compatible?
Thank you for your work!
Hello everyone, i want to clarify something, it was never a software issue.it's just DUST, believe me.
After trying all the mods and flashable zips and increasing the values, it only increase the volume but it becomes like a walkie talkie and not clear at all. So i decided to open the phone and it's very simple you can watch a video, nothing very dagerous.
Remove the 2 screws and the sim tray, carefully try to rise the screen with a credit card from the lower part of the phone.
Disconnect the battery, remove the 8 screws and remember their placement( there is one hidden screw middle left under the white stick)
Remove the signal cable and screen and extentions ones, and carefully unclip the motherboard from the top middle and try to rise it, slowly
I advice to put some ductape on the camera lenses so no dust can go in
Remove your speaker
You'll find it clean and be surprised, but the remove the black mesh a'd then you'll be shocked.
Clean the black one with alcohol and then use alcohol+toothbrush to clean the speaker grill on the phone
Clean it till you can see light through it and when you blow on it air can pass through
Reassemble your phone and connect the battery at lassst you dont provoke a shortcut when you screw or something and VOILAAA
i have oneplus 3 which is working on oos 4.0.2 but no sounds
it worked fine on oos 3.1.2 only once & no mic speaker error but now restarting on oos 3.1.2
i tried mega unbrick thread
all guides regarding bootloop & dm veriety guides too
if do dirty update through adb or through OTA i m facing mic & speaker error issue
with clean update mobile again start restarting problem at welcome screen & automatically boots into recovery
tried custom firmwares too & having mic speaker issue
can someone help me to solve my problem
wbr
Mobile Smoker
Have you tried any custom rom? I had same problem on my older device Lenovo p2 and custom rom helped me to solve the problem but I reinstalled different roms 1000 times and it fixed my problem. Even on stock rom
Tried custom roms too but on custom roms facing mic & speaker error u can say no sound at all
Hello..I recently flashed havoc is on my OP3.I am having issue with screen wake up..when I double tap still it won't wake up and even while pressing the power button..just capacitive button lights appear. After pressing power button for 4-5 times it sometimes wakes up..please anyone suggest me the problem.
Is there no expert here who can guide me?
..::Mobile Smoker::.. said:
Is there no expert here who can guide me?
Click to expand...
Click to collapse
WARNING: I am no expert but since you threw a challenge, I can not resist.
Install TWRP latest official, wipe system, data (if possible internal storage also), Dalvic and cache. Flash OOS 5.0.6, no Magisk or any other apps. Boot and check. You would have lost TWRP but if everything is ok, it can be flashed later.
tnsmani said:
WARNING: I am no expert but since you threw a challenge, I can not resist.
Install TWRP latest official, wipe system, data (if possible internal storage also), Dalvic and cache. Flash OOS 5.0.6, no Magisk or any other apps. Boot and check. You would have lost TWRP but if everything is ok, it can be flashed later.
Click to expand...
Click to collapse
Really appreciated that someone finally offered a different try
Give me 10 minutes i m gonna be back with result
Btw
Thanks in advance
..::Mobile Smoker::.. said:
Really appropriated that someone finally offered a different try
Give me 10 minutes i m gonna be back with result
Btw
Thanks in advance
Click to expand...
Click to collapse
Click the thanks button.
Am waiting for your report.
After erase all partitions via twrp
I installed full OOS & rebooted system
On setup screen phone showed factory resetting & restarts in recovery mode automatically
Same thing happened when i tried to format all three options inside official recovery
I dont have any personal data in it i just wanted to boot my mobile in working condition with working speaker & mic
tnsmani said:
Click the thanks button.
Am waiting for your report.
Click to expand...
Click to collapse
Anyother solution bro?
Do not wipe system image, only system! Or just use the Factory reset option in TWRP instead of selecting any partitons manually.
..::Mobile Smoker::.. said:
Anyother solution bro?
Click to expand...
Click to collapse
Use the Mega Unbrick Guide Method 2. Follow the instructions meticulously, don't skip any step. Boot into OOS 3.x.x and check. If everything is working, don't upgrade or flash any other ROM including OOS immediately. Hopefully, your issue should be solved.
emuandco said:
Do not wipe system image, only system! Or just use the Factory reset option in TWRP instead of selecting any partitons manually.
Click to expand...
Click to collapse
I did as u said but on first boot showed
Factory Data Reset
Restarting
tnsmani said:
Use the Mega Unbrick Guide Method 2. Follow the instructions meticulously, don't skip any step. Boot into OOS 3.x.x and check. If everything is working, don't upgrade or flash any other ROM including OOS immediately. Hopefully, your issue should be solved.
Click to expand...
Click to collapse
After unbrick full zip
I am having same factory data reset Restarting
Issue
Ryt now only 4.0.2 oos can boot up my OP3 A3003 fully ( But having mic & speaker error)
If you can fix audio problem on oos 4.0.2 OOS will be ok with me i dont want oreo or anything
I just want my mobile back in working condition
Thanx in advance
..::Mobile Smoker::.. said:
After unbrick full zip
I am having same factory data reset Restarting
Issue
Ryt now only 4.0.2 oos can boot up my OP3 A3003 fully ( But having mic & speaker error)
If you can fix audio problem on oos 4.0.2 OOS will be ok with me i dont want oreo or anything
I just want my mobile back in working condition
Thanx in advance
Click to expand...
Click to collapse
After booting up in 4.0.2, connect ear/head phones and check whether they work. If they do, then it is not a ROM/software problem. By speaker do you mean the earpiece or the regular speaker of the phone?
Have you checked the mic and speaker ports for possible blocks?
I am running out of ideas.
tnsmani said:
After booting up in 4.0.2, connect ear/head phones and check whether they work. If they do, then it is not a ROM/software problem. By speaker do you mean the earpiece or the regular speaker of the phone?
Have you checked the mic and speaker ports for possible blocks?
I am running out of ideas.
Click to expand...
Click to collapse
Non of any audio working checked my attached pics these are failed test of mic & speakers
I installed magisk audio modules too but no audio
& ryt now my OP3 is on 4.0.2 & working without audio
I m gonna be crazy
..::Mobile Smoker::.. said:
Non of any audio working checked my attached pics these are failed test of mic & speakers
I installed magisk audio modules too but no audio
& ryt now my OP3 is on 4.0.2 & working without audio
I m gonna be crazy
Click to expand...
Click to collapse
Final attempt: check the headphone/earphone port since normally when you plug them in, the built-in mic and speaker connections are disabled. Your device's port may be stuck in that position.
tnsmani said:
Final attempt: check the headphone/earphone port since normally when you plug them in, the built-in mic and speaker connections are disabled. Your device's port may be stuck in that position.
Click to expand...
Click to collapse
I tried with headphone no change
Even with bluetooth no audio at all
..::Mobile Smoker::.. said:
I tried with headphone no change
Even with bluetooth no audio at all
Click to expand...
Click to collapse
In that case, most likely a replacement of the daughter board is required ie. hardware error.
tnsmani said:
In that case, most likely a replacement of the daughter board is required ie. hardware error.
Click to expand...
Click to collapse
One my op3 booted in OOS 3.1.2 & audio was perfect
So i dont think so it has hardware problem