[T-Mobile Galaxy Note 4 Android Development] Zaron DarkStar:
Awesome rom! Possible bug?

Hi, awesome rom! I do like the roms with theme controls and mods. However, I think I might be experiencing a bug, but I don't even know if it is caused by your rom or if is a combination of apps that I installed or what. I have tried everything I can think of and I need help fixing it. For some reason my mic/voice input stops working/being able to hear me after I make a call. It works just fine before that; I can use voice search and voice input on the keyboard and everything, but after I open the dialer and make a call, I try to do a voice search again and it's as if the mic is disabled. Nothing at all. It won't work again until I reboot the phone. Could the Viper4Android have anything to do with it maybe? I don't use it/haven't activated it. I got no clue. Even if it doesn't sound like something that would be caused by your rom, do you have any idea what might cause this behavior? I have read about people having a similar issue of the mic not working at all on 5.0 lollipop, but this is still 4.4 kitkat. Thanks in advance!

Update: I would say it is very likely an issue with the ROM, because I just restored my backup of my stock rooted ROM, and everything works perfectly. I can use voice input, make a phone call, hang up, and use voice input again. I would guess something having to do with the way the dialer relinquishes control of the mic is bugged in the ROM, probably caused by one of the various sound mods.

Update2: So I was looking through the system apps in Titanium backup trying to figure out which apps might cause a conflict, when I noticed something odd. Even though this ROM is based on ANK4, and many of the app packages are ANK4, the apps InCallUI, Phone, and Android System all have a package version ending in ANJ7. Is that intentional or correct?

Update3: Well it may not be the ROM after all. I just did a clean install and the voice input and dialer work correctly. It must be something I did after I installed the ROM. I guess I'll have to go through everything I did step by step to find out what I shouldn't do again.

Solution: Ok, so after painstakingly going through each step of my customization again and checking voice input each time, I think I found what I did that bugged this ROM. I don't like S Voice. I would rather just use Google Voice for everything. Samsung's TTS is crap compared to Google's. So in Titanium Backup, I freeze S Voice so I don't have to see it in my app drawer, and it won't suddenly try to take over voice input. If, after I do this, I launch the Google Search app and in settings enable audio history and "Ok Google" everywhere, the bug reappears. I can use voice input as much as I want until I place a call in the dialer. After I hang up and try to use voice input again, the phone can't hear me. How dependent is Google Voice on S Voice? Must I leave S Voice unfrozen for my phone to function properly with this ROM? If so, that's ok; all the other awesome features make it worth having to put up with S Voice being enabled. Under the stock ROM I can freeze S Voice or even uninstall it just fine and I don't encounter this bug.

I found another far more annoying trigger for this bug which I will cover in a new post; this post is large enough.