Hi.
Im on Viper 800, a sense 6 based rom, 5.0.2, lollipop, firmware 7194012.
I flashed this sound mod - http://forum.xda-developers.com/showthread.php?t=2211163
In the description, my phone appears to be supported, along with the sense rom - M7 international.
After flashing, the result was this - great sound on speakers (as it should be), headset no longer recognized (sound only on speakers).
Ok, as I was doing always when facing this sort of problems, I restored a back-up version using TWRP. No matter how bad the software was messed up, this worked every time.
Not this time = the headset no longer recognized (sound only on speakers).
OK, I am writing an older back-up version = the same result.
Ok, maybe some scripts or libraries are corrupted, I am installing a NEW lollipop rom, after full wipe = the same result.
Ok, I am installing a fresh new rom, Kit Kat based = the same result.
The problem is that the automatic selection of speakers/headset is no longer functioning. I installed Soundabout apk, with allows you to manually route the sound on speakers or headset and it WORKS, but I cannot live with that - I want to repair this process in order to be automatic, as normal.
I need to understand wth is corrupted and how can I fix this...
Thank you in advance.
dabuHTC said:
Hi.
Im on Viper 800, a sense 6 based rom, 5.0.2, lollipop, firmware 7194012.
I flashed this sound mod - http://forum.xda-developers.com/showthread.php?t=2211163
In the description, my phone appears to be supported, along with the sense rom - M7 international.
After flashing, the result was this - great sound on speakers (as it should be), headset no longer recognized (sound only on speakers).
Ok, as I was doing always when facing this sort of problems, I restored a back-up version using TWRP. No matter how bad the software was messed up, this worked every time.
Not this time = the headset no longer recognized (sound only on speakers).
OK, I am writing an older back-up version = the same result.
Ok, maybe some scripts or libraries are corrupted, I am installing a NEW lollipop rom, after full wipe = the same result.
Ok, I am installing a fresh new rom, Kit Kat based = the same result.
The problem is that the automatic selection of speakers/headset is no longer functioning. I installed Soundabout apk, with allows you to manually route the sound on speakers or headset and it WORKS, but I cannot live with that - I want to repair this process in order to be automatic, as normal.
I need to understand wth is corrupted and how can I fix this...
Thank you in advance.
Click to expand...
Click to collapse
Afaik, sounds mod only make changes in the /system partition so restoring a nandroid backup or re-flashing the rom should fix any bug caused by the mod. Maybe its an hardware problem...
One thing that I love about Android is that no matter how deep was the **** I entered when flashing things, I never got stucked. Never, ever, and I had like 12 Android phones, rooting them all. Reading some tutorials, some topics, asking other guys.. I always solved the problems, by myself or with some help, without going to the service.
I fixed this. I wrote a fresh CM12, the result was the same (course), but out of despair, i pulled in/out the handset jack for SEVERAL times, while the music was playing and....it came back to its senses - the selection for sound output is automated again.
Thanks.
PS. It was software, not hardware - I explained above what happend when using Sound About.
The thread can be closed.
dabuHTC said:
I fixed this. I wrote a fresh CM12, the result was the same (course), but out of despair, i pulled in/out the handset jack for SEVERAL times, while the music was playing and....it came back to its senses - the selection for sound output is automated again.
Thanks.
PS. It was software, not hardware - I explained above what happend when using Sound About.
The thread can be closed.
Click to expand...
Click to collapse
Sounds more like an intermittent hardware problem. Flashing a new rom will wipe the sound mod from /system. Maybe there was some dirt in the jack and that pulling the plug in and out several time cleaned it. It might only be a coincidence if it happened after flashing that sound mod. Anyway glad to know its now fixed. :good:
Related
Hello, I just installed 5.0-3 and my Bluetooth is not working. I’m just wondering before I softbrick my phone again if this is what I should do to fix it.
I read on another forum post that I need to pull the boot.img out of the zip and flash it from fast boot. This was the trick on an HTC desire, but didn’t work so well for me last night.
Yesterday I tried this on my Sprint HTC ONE M7WLS stock root running 1.31.651.2, BT worked fine. Then I flashed 4.0-4and bluetooth did not work. It would pair, and when I would open my Motorola 720 running BT 2.1 EDR and hear this beep like it always would, but no audio would come through. If I switched in the middle of a test call to speaker audio would be fine. Switch back to BT and nothing.
I downloaded Insertcoin 5.0-3 thinking that might be what I need to fix the BT and I wanted the Sense 5.5 updates. Flashed it from TWRP 2.6.3.0, did the wipe from inside the insert coin installer and BT did not work. I did see the Sense 5.5 updates, but it was odd that the software version still said 4.0-4 even though I thought I selected full install and not update.
So fast forward I found on a thread that I needed to boot to the bootloader and run
Fastboot flash boot boot.img
This was to fix WiFi and BT errors. WiFi was working great for me, but not BT. This sent me into a boot loop (I think that’s what it’s called when just boots to the ROM’s splash screen and reboots). I had to sideload 5.0-3 several times before redownloading the ROM zip and sideloading it worked. It seemed like I would get the Sense crashes and I know the ROM just came out a few days ago so there might be some bugs.
I’ve read through the FAQ (http://forum.xda-developers.com/showthread.php?t=2228274 ) here which said disable the wifi, no go.
Another thread suggests fixing the permissions of the Bluetooth.apk, but an ls –lah shows rw-r--r—which is what this page (http://www.droidviews.com/how-to-setfix-file-permissions-on-android-devices-a-beginners-guide/ ) suggests are the correct permissions.
I’ve searched through this forum for Bluetooth and haven’t found anything else relevant, unless I’m missing something.
Anyway, before I go through that today is flashing the boot with the boot.img is the thing that I should be doing to fix my Bluetooth? Should I go back to 4.0-4 since it seemed more stable, though everything is 5.0-3 seems to be working well enough? Or should I buy a new headset because this one is possibly old and incompatible?
48 views, 0 replies. Thanks for all the help guys.
i think its a known bug that Baadnewz is currently working on. Get on his SVN updates to find the latest changes.
babymatteo said:
i think its a known bug that Baadnewz is currently working on. Get on his SVN updates to find the latest changes.
Click to expand...
Click to collapse
I didn't find it in the SVN info, but I do see on the 5.0-5 it says BT issues fixed. Thank you for the response.
Hello everyone,
my first time here. I am running into an issue where if I install a custom rom on my phone, I get no sound whatsoever. No sound from the speaker nor the earpiece. Also, related to having no sound, any app or anything I do relating to sound won't run or work on the phone strangely. (like Youtube for example, won't run)
Everything else works fine.
I tried multiple roms, and it all had the same issue. When I reverted back to the stock rom or the backup I made fortunately, I get sound but I am lost as to why I get no sound from my S3 device with a custom rom.
My Samsung Galaxy S3 device is model: SCH-R530U for US cellular. I hope I can find someone here who knows how to fix this issue =\.
Could it be that the Roms I installed don't have the sound drivers packaged? I made sure the Roms were compatible and all.
Thanks for the help!
Anyone have any idea? And I realized I posted in the wrong forum subsection. It should be in the regular troubleshooting one, not the I9305 troubleshooting one.
Also, when I revert back to my old stock, I somehow get all these random gapp errors. Not sure if thats because I installed a different gapp on the new custom rom and that could have affected the previous backup?
Hello,
I have a motorola G6 that after bad root get stuck on bootloop.
I flash the phone with two roms but the phone after flash dont have sound during calls, the earpice dont work even in loudspeaker, but the phone rings when is receving calls.
anyone already have this problem?
tanks
This question is probably in the wrong section but anyway...I did. I never checked the phone prior to rooting so I'm not sure if a "bad root" was the cause or not. However, I experienced the exact same problem as you. I was originally on build OPS27.82-19-4 so I reflashed stock OPS27.82-19-4 as described here. But I still had the same problem. On a whim I randomly flashed build OPS27.82-19-4 following the same instructions. The phone has been working great ever since (I have it rooted, xposed. etc...). Not sure why there was a problem, or if reflashing the newer build "fixed" it or not...but as I said, all is good now. FWIW, when I check the sim status in settings>about phone, the network section is blank. It was blank when I had problems too.
Perhaps this will help you..
PS When I reflashed the firmware, the phone would boot into fastboot mode, then when I selected "Start" it would boot to the OS. If you run into that, here is how it was fixed. See posts 5, 6, 7, & 8.
Good luck!
I had a similar problem, I did the root, TWRP, I ended up giving up and flash again on the stock of the bike G6 Play (Brazil) available here in XDA, to my surprise, he made and received calls normally, the speaker for music and connections of other applications (Whatsapp, Messenger, Hangouts, etc.), but it did not work for the rom dialer.
I thought I had a problem, it was when a system update appeared, I installed it and it worked again.
I figured it was some rom bug I installed.
Tanks for the help.
I solved the problem flashing the phone with flashrom.bat instead of put the comand one by one.
Many tanks
Multiredes said:
Tanks for the help.
I solved the problem flashing the phone with flashrom.bat instead of put the comand one by one.
Many tanks
Click to expand...
Click to collapse
That's because a custom rom or GSI does not have all the necessary files. 99.9% of the time, flashing stock will fix a problem.
i have following problem: i got a xz1c without original firmware. i have no backup with the Stock-Rom. I installed twrp and flashed lineageos16 lilac. everything works excepted the microphone and speaker during a call. That means: i can start the call, and it is ringing at the other person, but i can't hear anything. no connection ring and no voice. the other person can't hear me also. microphone and sound/loudspeaker works in all other apps (i tested music-player, voicemail, recorder). i tried different call apps. nothing works.
the big problem is: i can't switch back to firmware because it doesn't exist as backup. i can't flash other ROM, because this lineage version is the only one i can flash. RR, AOSP, etc. failed all during installation.
what can i try? Has anybody a backup from firmware of the g8441, i can try?
i tried with a lot different files, for example androidfilehost.com/?w=files&flid=274221
either the filelink is broken or the flash failed during flashing.
i get crazy :-/
p.s.: I'm no expert in flashing phones, so please be sorry if i don't understand everything or if i use wrong words for explaining
bluetit said:
what can i try?
Click to expand...
Click to collapse
Use EMMA to get you back to stock.
bluetit said:
i have following problem: i got a xz1c without original firmware. i have no backup with the Stock-Rom. I installed twrp and flashed lineageos16 lilac. everything works excepted the microphone and speaker during a call. That means: i can start the call, and it is ringing at the other person, but i can't hear anything. no connection ring and no voice. the other person can't hear me also. microphone and sound/loudspeaker works in all other apps (i tested music-player, voicemail, recorder). i tried different call apps. nothing works.
the big problem is: i can't switch back to firmware because it doesn't exist as backup. i can't flash other ROM, because this lineage version is the only one i can flash. RR, AOSP, etc. failed all during installation.
what can i try? Has anybody a backup from firmware of the g8441, i can try?
i tried with a lot different files, for example androidfilehost.com/?w=files&flid=274221
either the filelink is broken or the flash failed during flashing.
i get crazy :-/
p.s.: I'm no expert in flashing phones, so please be sorry if i don't understand everything or if i use wrong words for explaining
Click to expand...
Click to collapse
Hi!
Did u install Ainur Sauron and tweaked sauron.useroptions? If that's the case, look, under
"Experimental Qualcom only options",
did u set the option in line 82 "COMP=true" ?
I think, by removing the headphone compander from audio mixer s.th. goes wrong with routing to the right audio output channel, again.
Just from interest: perhaps u could check, if u have some pluggable headphones near u, if the left channel is a lot quieter?
Had this, I would call it "Xperia-Head-/Earphone issue", comin from Stock .228, after clean and fresh install of that unofficial one in LOS 16 1.0 (unofficial). I wondered, that after flash-routine, but before installing Ainur in Magisk, with my all-time-useroptions for sauron, still in internal memory (I didnt wiped internal memory, btw.) A friend was calling me, and everything was fine.
In the afternoon, after flashing Sauron, with this COMP-option set to true, same issue again. I had a few more options ticked, but that one seemed to make a lot more sense to me, not to be used with my XZ1c, again.
This will help u, perhaps.
U don't need to flash anything, if evreything is proper installed and working fine, except ur "Xperia-Head-/Earphone issue".
Greetz, brockn
First of all, I'm running MSM Xtended v9 dirty flashed from v5 which was clean flashed after Havoc OS Pie rom some time ago.
Okay so here is the problem as specific as possible.
At first, after doing an online call using headphones (Either via Whatsapp, Messanger, Discord) the mic would suddenly stop working, no voice input would be detected whether its Voice Notes, regular calls, google assistant or any other app that detects voice input. This was back on MSM Xtended v5, which was Clean flashed. The problem then persisted and turned into the mic doing the same thing even without the headphones, then onto doing it again for regular calls too, not just the online ones (so that means I have to reboot after every call). I thought it was a problem with my android version so I upgraded to v9, dirty flashed. I wanted to opt for a clean flash but I had some data on apps that couldn't be backed up at the time. Problem still remained and now the mic suddenly stops working after reboot for no reason without making any calls.
Obviously, as every developer recommends I thought to clean flash the rom again, and prepared myself to backup everything and lose that which I can't back up. Then while looking for a different rom, I noticed multiple people having the same problem for different ROMs, though all were Android 10 ROMs.
So I wanted to ask, is there any solution to this problem? It makes the device basically unusable without any mic, and I do understand that not everyone has the same problem but when I saw others having it I realized it might not be specific to my unit.
Anyone trying other Android 10 ROMs without this problem? Should I downgrade to Pie? Any help would be appreciated, please.
If you recommend downgrading please tell me how, as I seem to have forgotten and can't find the method online (it may be there but I haven't seen, I apologize if that's the case).
Thank you in advance.
Known issue on Android 10, most probably it is Gapps issue, so try Weeb Gapps if you don't need 'Hey Google' thing. Downgrading is not that hard on OnePlus 3T, just download OOS 9.0.6, backup your data to PC or OTG, wipe all and format data and flash OOS, that's it.