yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] RuffBuster:
Going to test this on my slim based ROM for a couple of days to see if it makes a difference. Changing modems "seemed" to help but still suffer this issue though less often now.

Is this something to do with low power audio LPA? I remember Viper FX likes to disable this during the install process. Is this the same thing? Cheers.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] RuffBuster:
For me this doesn't work though I'm not using a cm build, I'm on a slim LP build.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
I'm no dev but will have a go at testing this, to mark out that section do I put speech marks " at the start and end of the section?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] RuffBuster:
No put a # at the beginning of each highlighted line. This is "commenting out".

#Line that will not run

Line that will run
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
Thanks to ruffbuster I was able to comment out the highlighted lines in the audio_policy.conf file. I have turned on ok Google detection, used Bluetooth and the voice recorder and made calls after each with no problems. So far the no sound issue hasn't happened. :D. I will continue testing it tomorrow and report back. Fingers crossed.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] arco68:
Remember to reboot after making the changes, or else they won't take effect.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
I edited the file and rebooted before testing :thumbup:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
I've been testing since yesterday and the no sound issue has not returned. I have used ok Google detection set up for all screens, used it to make calls etc. This would normally trigger the problem immediately but hasn't. I've been using Bluetooth which also triggers it but it hasn't. I've been using voice recorder and all fine. I have basically done everything I know that would trigger the issue and haven't had a single problem. This is an absolute first. I will carry on trying to break it today and update if anything changes.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] niedergerner:
I've tested it, too.

Edited the audio_policy.conf, reboot, activated the "OK Google"-detection, made a test call, everything all right. Then used "OK Google" and the stock voice recorder, and ta-da: no calling sound again :(

So i edited the audio_policy.conf again, disabled the "OK Google"-detection, rebooted my phone. No issues with calling sound so far :) (edit:...even after using Google voice search by tapping the mic icon)

I still think, that the deactivation of the "OK Google"-detection is the only a right way to solve this problem. Just my two cents.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
Did the changes you made to the audio_policy.conf file take? I tried editing it the first time and although it said it had saved the changes it hadn't. When I used the CM editor with the settings set to root mode the settings took.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] niedergerner:
Yes, i've edited it with CM Editor in root mode, too.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] 96DANGER96:
Thank you arco, just rebooted after have modified the file, will test and report! :)
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
I have had no problems with calls today despite doing everything I can to trigger it. With what I have been doing I would have definitely have had the problem by now.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
I notice in the 0713 nightly change log this entry

common: Don't include android.hardware.audio.low_latency.xml (android_device_samsung_msm8930-common)

Is that related to this problem? I only ask so that I know whether I need to edit the audio_policy.conf file again when I update to the 0713 nightly.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] GreenneeG:
what do you mean of " mark it out ?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
Put a # at the start of each of the lines highlighted. It's explained a few posts back.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] 96DANGER96:
See here changes from left to right: http://review.cyanogenmod.org/#/c/102870/3/audio/audio_policy.conf
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
Still haven't had the no sound issue. Everything working fine. I guess I will need to edit the audio_policy.conf file after installing each nightly?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] arco68:
Yes.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
Thanks for the fix. I can use my phone normally at last.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] 96DANGER96:
So, what is the problem? (For noobs) I want to share this fix in the OP

Inviato dal mio iPad utilizzando Tapatalk
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] arco68:
Apparently low latency audio might be problematic on msm8960/msm8930 devices, and it seems that it's not enabled in Samsung stock rom either.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
Is this fix likely to make it into a nightly as a permanent fix?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] GreenneeG:
I had this voice issue during calls when i was on F4K and K2WL ROMS .. this issue is very annoying you have to restart device every time it happens ..

now i've used bliss pop ROM for 2 weeks , until now I haven't faced this issue .. if it happens in future i'll let you know ..

btw : has anyone tried arco68's fix ?

is it fix the voice issue ?

and thanks all for reply me

by the way bliss rom audio/audio_policy.conf doesn't look like the one in your link
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] niedergerner:
Doesn't change anything for me. After using Google Search by voice activation (say "Ok Google") the issue returns immediately.

I'm on official CM Nightly 20150714 and Radio OCA1 .

Edit: new radio COE1 just released. I will test this later that day.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
It has worked for me with Cm12.1. Haven't had a single problem so far. Before this I couldn't use ok Google detection or voice recorder or Bluetooth headset without having to reboot in order to make calls. Have been using them all for a couple of days and so far so good.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] RuffBuster:
I've had this Google voice search issue on 2 different Lollipop ROMs. AICP latest and Tipsy latest. Going back and forth between Google voice search and the dialer causes me to lose sound on my dialer and Google voice no longer can hear me. After which if i keep trying to connect a call ”system" will crash and phone will lag to death with "system " crashing constantly.

I've tried different modems, gapps and installation methods. I9195 LTE here.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
I notice that there is a change for the next nightly to disable low latency. Thanks for all your hard work arco.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
Had my first no sound issue this morning after several days. I run using an app called run keeper which uses gps to track my route and I wear my phone in an armband and Bluetooth is on. I used to get the issue after running every time even with ok Google detection off. Today ok Google detection was on.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] 96DANGER96:
So, [MENTION=3044346]arco68[/MENTION] the fix is in the rom now?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] SilviuMik:
Yes

http://review.cyanogenmod.org/#/c/102870/

Gerrit Code Review

Change has been successfully merged into the git repository by Arne Coucheron Jul 15 9:48 PM
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
It appears so. I checked the audio_policy.conf file after updating and the lines that we had to comment out are no longer there.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] arco68:
So it didn't help after all?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
I've only had one incident in the last week so it's definitely made a huge difference. I will be running tomorrow so will see if the problem reoccurs. I suspect that having my phone on my arm with ok Google detection on for all screens may be the culprit. Maybe the constant wind noise jams things up. But removing low latency audio has fixed the problem in all other situations.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] RuffBuster:
I suffered problems with Google voice search with and without "OK Google" and the dialer on 3 different Lollipop 5.1.1 ROMs. I'm currently using Mokee ROM and haven't had one instance of this happening in the 3 days of the testing said ROM. Had a look at the audio conf files of the ROM and don't find any reference to "fast" within, thinking the devs removed this here. So maybe it does help? But removing these lines in the other ROMs I tested didn't help me with those other ROMs. Maybe it runs a little deeper? Though non of the ROMs I tried were CM.

On runs with the problem I can replicate the error by going back and fourth between making calls and voice search until eventually it will lose sound and/or crash "system" with a reboot being the only solution.

But yeah Mokee ROM all good so far after 3 days.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] davidmlondon:
No problem today after running with the phone. Calls worked fine :thumbup:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] 96DANGER96:
No problem at all for me. ALL WORKING :D
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] yeye.phone:
Nothing
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] mail@mstmail.nl:
Is not working on:

I9195 CM 12.1 last 12.1 nightly
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] all.rounder:
Just go to Google now and switch off OK Google wakeup .. On cm12.1 updates 2/03/2016 . works for gt i9500
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] ADR USR:
[/COLOR]

In i9192 did not work.

Just the fact of using Voice Search triggers the bug in calls. Not always immediately, but with absolute certainty, caused by Google Now. I'm still looking for solution. For now just I uninstalled Google Now and everything works well.

Interestingly, I get to make calls with voice command in google now and works. But shortly after the problems begin.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Zaionakoh:
in detail please

can some reply with a detail steps how to solve this issue.

Am not a developer and now really confused on what to do.

please help.

Am using SM-E500H.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] IronRoo:
Follow this but turn "ok google" off instead of on

https://support.google.com/websearch/answer/6031948?co=GENIE.Platform=Android&hl=en

Note: if this does not work you should go and ask on thread for your device, this thread is for S4 Mini only!
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Zaionakoh:
thanks. I was randomly looking for solutions. and I tried that, unfortunately it doesn't work.

I just installed samsung stock rom for the moment until a stable rom is out.

thanks.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] IronRoo:
OK, though the fix should have been merged as per above over a year ago so all newer ROM's should not have this issue, unless a recent change has broken the fix on your device....
[ZenFone 2 Q&A, Help & Troubleshooting] MagaroHeath:
Hi everyone,

I own a ZE500cl, and just wanted to encrypt it ( for security purpose :angel: )

I launched the procedure at 7:40 this morning, it is 12:33, and my phone is still stuck on the bootscreen

ASUS

[whirling thingy]

So I wondered what to do, just reboot it or wait a fex days with the phone loading ?

Have a nice day :)
[ZenFone 2 Q&A, Help & Troubleshooting] Bbox77:
Hi, sorry for this "up" but it might be useful for the others.

I just had this problem also. It is because some app are on the external SD card and it causes that bug.

If you're stuck on the Asus bootscreen just press the power button so your phone will reboot (still unencrypted) and move the app back to the internal memory.

Then you can encrypt again and it will work.
[Android] justys01:
Apologize in advance if i wrote this in not correct forum section.

So i was trying to install screen lock that galaxy phones have (unlocks like a bubble) and don't ask me how or why, i accidently deleted com.android.system from root>firmware. It crashed my phone and now it freezes while starting.

Is there a possibility to get that file where it need's to be or does anyone know where to download ROM because i cud not find it.:(
[Android] egames 2014:
I have same problem, i' ve tried XPOSED and now i have problems with GSM
[Galaxy S6 Q&A, Help & Troubleshooting] cpu2007:
Hi everyone

Having moved from the oneplus one to the s6, one of the things I can't find is user profiles.

on the oneplus one I could set different actions on a profile, for example if I select home profile,it would turn on wifi,turn off mobile data and disable screen lock, work profile would do the opposite.

Can I create profiles on the s6?

thanks
[Galaxy S6 Q&A, Help & Troubleshooting] EddyOS:
That's not available in the stock S6, it's a feature of CM12S
[Galaxy S6 Q&A, Help & Troubleshooting] cpu2007:
we're still talking about a device working under android os, is it there anything similar that can be achieved on the s6?

ps: I am using the xtrestolite rom
[Galaxy S6 Q&A, Help & Troubleshooting] krelvinaz:
Tasker and or trigger, might need root access though
[Ascend Mate 7 Q&A, Help & Troubleshooting] midodivel:
Help me plz fingerprint disapperd from setting I change to custom rom but not work to any one help me plz is there a way to install it manual:(
[Ascend Mate 7 Q&A, Help & Troubleshooting] drmodify:
is that a CM11 or CM12 ROM?? well I think the fingerprint scanner is not supported yet. Only the custom roms which are stock based are supported
[Ascend Mate 7 Q&A, Help & Troubleshooting] midodivel:
My mate doesn't flash stock Roms and I don't know the reason. But it flash h60_l12 ROM and i don't know how this happened !!! And when i try to flash stock update always fail . so I download this custom ROM :crying:
[Ascend Mate 7 Q&A, Help & Troubleshooting] midodivel:
When I try to flash another rom show me this message
[Ascend Mate 7 Q&A, Help & Troubleshooting] drmodify:
wow, that rom is for HONOR 6??!! That's why it wont work

You have to download the first stock release of the ROM then upgrade! It would be like 1gb or so ROM upgrades are like 400mb or less in size
[Ascend Mate 7 Q&A, Help & Troubleshooting] bubble_cat:
I found that the fingerprint ID settings is disappearing when you make a soft reboot

But it seems in your case that you tried something.. unexpected .. seriously
[ZenFone 2 General] aj7400:
Changelog..

1 Fix the issue that sometimes HDR mode resolution will have green line.

2 Improve the video recording quality.

3 Improve Power saver stability and fix WIFI connect state issue in advanced settings

4 Improve Auto Start Manager stability and fix the App continuous pushed notification issue after restricting its auto start

5 Fix notice shows up while the first message comes only issue

6 Improve signal bar stability for sim 2

7 Update phone APN version to 105.

8 Update Houdini 5.0.2

9 Fixed camera can not open sometimes when using zenflash

10 Improve volume of recording video will increase and decrease alternately.

11 Do not config Routing.Configure.HWCodec.Playback.Mixers.Headset when using FM.

12 Fixed some BLE device can not auto reconnect

13 Improve service stability

14 Improve modem stability from crash

15 Improve call stability

16 Quick Settings: Change "Reading Mode" button as "Bluelight filter"

17 Improve SysteM UI stability and modify Japanese strings

18 Improve lockscreen UI and stability

19 Fix Homescreen Wallpaper randomly lost previous settings and half black screen issue

20 Snap View: add reset Snap View password function

21 Fix Contacts search failure issue when default language was set as HK Chinese

22 Improve Auto start manager stability and fix FB broadcast issue

23 Improve Task Manager UI and rotation stability

24 Fix calculator stability issue and UI bug under Quick Memo App

25 Improve Launcher and Multi user stability from System and framework

26 Fix Google Voice incoming call source issue and the failure to change to Google Voice number

27 Fix the miss call issue when it is in multi-user mode.

28 Improve File Manager stability

29 Add ASUS ZenUI PC Suite

30 Fix all touch gestures to be enabled when change back to owner mode

31 Fix ASUS Browser issue

32 Fix the issue that Audio Wizard cannot be launched when turn off BT

33 3rd party app update

34 Update touch FW

35 Update JP IME ATOK to v 1.0.1

36 Modify Japanese strings in Power Saver App

37 Fixed turn on the camera must unlock by using zenmotion issue

38 Fixed an error message shows up after removing privacy mode and adding new user immediately issue.

39 Fixed wallpaper needs to have second clicks for reaction issue.

40 Fixed built-in browser features a new incognito window has no effect issue.

41 Fixed close contacts shows other programs issue.

42 Fixed built-in calendar Click settings will flash issue.

43 Fixed ringtones into vibrate mode when the camera is off camera sounds issue.

44 Fixed volume keys to adjust the ring abnormaliy issue.

45 Fixed wallpaper Figure has been broken issue.

46 Fixed after the system optimization, message management have stopped running issue.

47 Add Battery charging ready reminder feature.
[ZenFone 2 General] Archmage1809:
550 or 551?

Edited: Seen. 550 indeed. Updated.
[ZenFone 2 General] whynottoday:
Link please
[ZenFone 2 General] Archmage1809:
From OTA update

If you are using 550, go to Check Update.
[ZenFone 2 General] sirsomething:
If you have 551ML you also received the update
[ZenFone 2 General] gontie:
550ml updated and i see really 20% gain performance in games and the phone is also much more fluent.

screen rotation works also better.
[ZenFone 2 General] cangcan:
update size is so small.. i guess there's no changes in terms of battery life and android OS, basicay they focused on apps improvement and not on the rom improvement..kinda disappointed tho..but gonna update it anyway after flashable ota zip released by shaka..
[ZenFone 2 General] sirsomething:
Does this mean we get 5.0.2? If yes it should improve battery a little...
[ZenFone 2 General] knowledge@heart:
I just somewhere read on zentalk about the update being in 90 MBs

So i guess, this was just a leveler update

The ones who were on 2.18 got a 90MB update to 2.19 and

The ones already on 2.19 got a 29 MB update (eliminating the so called "instabilities") and a version number bump. I too got a 29MB update.

Asus is preparing for 2.20 release (I guess). And it needs everyone to be on the same version.
[ZenFone 2 General] TheSSJ:
No, libhoudini version was upgraded to version 5.0.2 (has nothing to do with the Android version). Libhoudini translates binaries made for ARM to x86 if I recall correctly
[ZenFone 2 General] knowledge@heart:
Houdini has been updated to 5.0.2.

FYI, Houdini is the x86 to ARM translator lib.
[ZenFone 2 General] cangcan:
agree..hopefully that beta testing OS gonna be released as soon as possible..either on 5.1.1 or M, couldnt be grateful anymore.. the rom is good enough already and asus has done a good job in optimizing 5.0 rom on zf2, but they will never get rid on this android OS bug unless they push higher version of lollipop..
[ZenFone 2 General] knowledge@heart:
Android M will take a lot of time. Even Google hasnt released M for its Nexus lineup.

The Maximum we can expect is 5.1.1.
[ZenFone 2 General] sirsomething:
Hum... That makes sense. Thank you
[ZenFone 2 General] klingklang76:
At last :)

Let's hope for a 5.1.1 update sooner than later now :fingers-crossed:
[ZenFone 2 General] yakub234go:
updated & flashed TWRP

guess the bootloader is fine
[ZenFone 2 General] john_petrucci:
Do you have update 2.19.40.20 and after unlock bootloader???
[ZenFone 2 General] yakub234go:
i have the latest update for my model(ZE550ML)
[ZenFone 2 General] john_petrucci:
Do you confirm with the last update (for model ZE550ML) unlock bootloader method worked fine??
[ZenFone 2 General] yakub234go:
I unlocked it when it was on the previous update & updated to the latest & then flashed TWRP

If u r asking me if the unlock method works on the latest update that I don't know
[ZenFone 2 General] stephtban:
I successfully updated from 2.19.40.18 to 2.19.40.20

My ZE551ML was bootloader unlocked when i did update. Here is what i have done:

1- full unroot (with SuperSU option)

2- uninstall busybox (with stericson app)

3- reboot

4- download OTA and apply it

5- root again, install busybox and twrp

6- enjoy :D

note 1: if you have xposed, uninstall it

note 2: unfreeze all bloat
[ZenFone 2 General] john_petrucci:
Thanks!

Well, You unlock with the previous update, after update OTA, Rooted and flash the recovery TWRP!!

is it correct?
[ZenFone 2 General] yakub234go:
Yes that's correct
[ZenFone 2 General] glock24:
I've experienced the camera problem with the green lines. Will try after upgrade.
[ZenFone 2 General] CenereZar:
twrp will be replaced after ota automatically?or i have to reflash original recovery and then update ?
[ZenFone 2 General] john_petrucci:
Please in the step 4, the update flash the original recovery ???
[ZenFone 2 General] luthfanos:
i've done with the unroot, but, i still can't apply the OTA, it says system update failed
[ZenFone 2 General] whynottoday:
i've done with the unroot, but, i still can't apply the OTA, it says system update failed

same issue for me
[ZenFone 2 General] cangcan:
did you mean that you flashed the ota zip file using twrp and it works?
[ZenFone 2 General] yakub234go:
Everything should be stock

If u r still facing problems then adb sideload ur current firmware then retry ota
[ZenFone 2 General] AaronICK:
Thank God! Now my update is successful after the first two failed attempts.

Lesson learned (since I rooted my phone)...

1. DO NOT REMOVE any system app nor bloatwares. Just freeze them.

2. If a new update arrives, unfreeze those apps first. All of them.

3. If you installed XPOSED, uninstall it first, then reboot (I have busybox installed but I did not uninstall it; update was successful).

4. Finally, unroot your phone via SuperSU, then reboot.

5. After reboot, that's the time to check for update. I don't know if this has some weight. But I suspect that if I check for system update while rooted, it will give me a failed system update later on even after unrooting. So in my case, if I get a news that a new firmware update is available, I will not check it while rooted. Perform an actual system update check after doing everything above.
[ZenFone 2 General] lordkonst:
In case anyone is wondering, I have updated successfully from 2.19.40.18 to 2.19.40.20.

I have unlocked bootloader and untethered TWRP.

Same as the previous update i uninstalled xposed framework and busybox and unrooted before update just to be sure.

Then run system update, downloaded it and it auto updated without a hitch.

So far everything seems good.
[ZenFone 2 General] stephtban:
Yes it will update within twrp and then overwrite it. You'll have to reflash it.
[ZenFone 2 General] oxydius7:
This update still allows the bootloader to be unlocked, just tested here. I guess ASUS unofficially supports custom development.
[ZenFone 2 General] hypertech:
http://www.asus-zenfone.com/p/fota-center.html
[ZenFone 2 General] mhp1995:
Okay guys i updated to the latest fw :cool: UN-ROOTING BEFORE APPLYING OTA IS NOT NECESSARY... here is what i did:

NOTE: ROOT SURVIVES OTA AND THERE ARE NO BOOTLOOPS ... BUT REMEMBER I USED THE LATEST 1 CLICK ROOT TOOL WHICH ALLOWS US TO APPLY OTA WITHOUT UN-ROOTING...IF U HAVE ROOTED YOUR PHONE VIA DIFFERENT METHOD U HAVE TO UN-ROOT FIRST......

1) Unfrozed all the frozen apps

2) Un-installed Xposed

3) Un-installed BusyBox

4) Applied OTA

5) And Voila i was on the latest firmware...