Hi there, I recently fixed this problem wherein whenever I placed a call, through WhatsApp, Hike, Razer, etc., the person on the receiving end would not be able to hear me however if they called me, I could hear them perfectly. After some research on this problem, I found a solution which worked perfectly for me (I'm currently running CM11 latest build).
So first things first, install ES File Explorer or any other root explorer(I used CM's file explorer for this)
1. Browse to /system/
2. open build.prop with an editor
3. Search for two lines:
use.dedicated.device.for.voip=true
use.voice.path.for.pcm.voip=true
4. Change both of the above to ' =false '
5. It should now work
6. Don't forget to reboot!
For me, personally, by changing the 1st one to false worked for Hike, but for WhatsApp I had to change the second one to false also.
I was using Mokee Open Source (CM12/5.0.2) and that thing of no voice in whatsapp happened to me, the person in the other side just hear noises, but i clearly hear the person. I will flash back another CM12 rom and will try this, if it fix i will tell. Thanks.
@iG0tB00ts
Thanks a lot !!
Worked perfeclty. Thanks!
worked like a charm in Hyperdrive-OS 5.1. Thanks!
My build.prop doesn't have the first line. Only use.voice.path.for.pcm.voip
Would this work anyway?
Edit: Worked.
Couldnt find the lines
Well and what if i cannot find any of those 2 lines?
i ma using Cm12.1 for my Galaxy S2 i9100
Satfoun said:
Well and what if i cannot find any of those 2 lines?
i ma using Cm12.1 for my Galaxy S2 i9100
Click to expand...
Click to collapse
I too am on CM12.1 and like the previous user had said, there is
use.voice.path.for.pcm.voip
If there isn't try flashing another ROM maybe? Or search for similar lines and try changing them to false.
On Hyperdrive-os5.1 edited so.
use.voice.path.for.pcm.voip false
Work well thank you.
iG0tB00ts said:
I too am on CM12.1 and like the previous user had said, there is
use.voice.path.for.pcm.voip
If there isn't try flashing another ROM maybe? Or search for similar lines and try changing them to false.
Click to expand...
Click to collapse
No there isnt even that line....annnd i guess im fine with my current ROM i dnt want to flash another thnk u ^-^
There is no such line in cm 12.1
iG0tB00ts said:
Hi there, I recently fixed this problem wherein whenever I placed a call, through WhatsApp, Hike, Razer, etc., the person on the receiving end would not be able to hear me however if they called me, I could hear them perfectly. After some research on this problem, I found a solution which worked perfectly for me (I'm currently running CM11 latest build).
So first things first, install ES File Explorer or any other root explorer(I used CM's file explorer for this)
1. Browse to /system/
2. open build.prop with an editor
3. Search for two lines:
use.dedicated.device.for.viop=true
use.voice.path.for.pcm.voip=true
4. Change both of the above to ' =false '
5. It should now work
For me, personally, by changing the 1st one to false worked for Hike, but for WhatsApp I had to change the second one to false also.
Click to expand...
Click to collapse
Am using CM 11 M12 on LG e980 and I didnt see the lines in build.prop so I added them at the end. i saved and reboot, nothing happened, same problems, not hearing on whatapp nor viber.
Thanks a lot @opp
first line was not in my build.prop, but I changed the value for second one. now it's working
Not Working
Hi There am using Moto G and Cm12.1 I don't have that frdt line but I do have that second line and changed it to False as u said but Not working..........
iG0tB00ts said:
Hi there, I recently fixed this problem wherein whenever I placed a call, through WhatsApp, Hike, Razer, etc., the person on the receiving end would not be able to hear me however if they called me, I could hear them perfectly. After some research on this problem, I found a solution which worked perfectly for me (I'm currently running CM11 latest build).
So first things first, install ES File Explorer or any other root explorer(I used CM's file explorer for this)
1. Browse to /system/
2. open build.prop with an editor
3. Search for two lines:
use.dedicated.device.for.viop=true
use.voice.path.for.pcm.voip=true
4. Change both of the above to ' =false '
5. It should now work
For me, personally, by changing the 1st one to false worked for Hike, but for WhatsApp I had to change the second one to false also.
Click to expand...
Click to collapse
Hi my whatsapp-call is not working and apparently because of a voip setup error. I followed the instructions and went into the build.properties in edit mode. But the lines are not there...in fact nothing about voip. I have an LG P500 android 4.0.4 oxygen . Can you please help?
iG0tB00ts said:
use.dedicated.device.for.viop=true
Click to expand...
Click to collapse
i need to ask, is that a typo ?
saumil007 said:
There is no such line in cm 12.1
Click to expand...
Click to collapse
Add both the lines, with the fase value, and don't forget to *reboot*!
pedro scott said:
Am using CM 11 M12 on LG e980 and I didnt see the lines in build.prop so I added them at the end. i saved and reboot, nothing happened, same problems, not hearing on whatapp nor viber.
Click to expand...
Click to collapse
I'm not sure I can help you with that, you might have to ask the developer?
Rivu78905 said:
Hi There am using Moto G and Cm12.1 I don't have that frdt line but I do have that second line and changed it to False as u said but Not working..........
Click to expand...
Click to collapse
Add both the lines, change to false, and *reboot*
SUPhw said:
Hi my whatsapp-call is not working and apparently because of a voip setup error. I followed the instructions and went into the build.properties in edit mode. But the lines are not there...in fact nothing about voip. I have an LG P500 android 4.0.4 oxygen . Can you please help?
Click to expand...
Click to collapse
Try adding both the lines, change it to false, save, and *reboot*
Hastaloego said:
i need to ask, is that a typo ?
Click to expand...
Click to collapse
Haha yes thanks, corrected
iG0tB00ts said:
Haha yes thanks, corrected
Click to expand...
Click to collapse
strange that no one else seem to have noticed.. it even got false quoted here:
http://www.ibtimes.co.uk/how-fix-whatsapp-call-no-voice-error-receiver-cannot-hear-other-end-1493769
Hastaloego said:
strange that no one else seem to have noticed.. it even got false quoted here:
http://www.ibtimes.co.uk/how-fix-whatsapp-call-no-voice-error-receiver-cannot-hear-other-end-1493769
Click to expand...
Click to collapse
Oh, if you click the source link, it redirects here I'm honoured
Thank you for helping out. I added both lines. First with the ES editor and then a file editor but it refuses to save. Can you please advise.
Related
Im on stock froyo and rooted.
I was using Kirillos roms before and the proximity sensor was working fine. Now with the stock rom it works, but when i make a call, and when i finish the call the screen stays off for a 3-4 seconds and i cant end the call coz i dont see anything on the screen. Is there some file that i can modify so the sensor is more responsive or to change some time values?
vonuzu said:
Im on stock froyo and rooted.
I was using Kirillos roms before and the proximity sensor was working fine. Now with the stock rom it works, but when i make a call, and when i finish the call the screen stays off for a 3-4 seconds and i cant end the call coz i dont see anything on the screen. Is there some file that i can modify so the sensor is more responsive or to change some time values?
Click to expand...
Click to collapse
Open /system/build.prop via any root explorer in your galaxy 3, search for mot.proximity.delay and change its value to 150 so it should look like this:
mot.proximity.delay=150
save and reboot. Enjoy!
twinky444 said:
Open /system/build.prop via any root explorer in your galaxy 3, search for mot.proximity.delay and change its value to 150 so it should look like this:
mot.proximity.delay=150
save and reboot. Enjoy!
Click to expand...
Click to collapse
thanks for the reply, BUT ther is no such line in mu build.prop file
its in the attachment so you can see
vonuzu said:
thanks for the reply, BUT ther is no such line in mu build.prop file
its in the attachment so you can see
Click to expand...
Click to collapse
Just add that line to the end of build.prop.
And you must leave last line of build.prop empty.
Sent from my GT-I5800 using xda app-developers app
twinky444 said:
Just add that line to the end of build.prop.
And you must leave last line of build.prop empty.
Sent from my GT-I5800 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
I'm doing something wrong, or this just doesnt work for me.. I added the line at the end of the file, one line empty, and its still the same. I must wait for the other side to hung up coz my screen remains black. Its very annoying.
I thing i must flash some custom rom with the tweaks included. But on the custom roms the remote control apps like logmein and teamviewer dont work(kirillios).
Here is the build.prop in the attachment so you can see am i doing it right?
I did it!
With the help of rkoby13 So big thanks to him. rkoby13's words:
just try to extract build.prop from one of my rom version....i think v 2.5 will be the best and open build.prop and then copy Hercolubus tweaks to your build.prop.....set permissions and reboot....now it should be all fine..
Click to expand...
Click to collapse
vonuzu said:
I did it!
With the help of rkoby13 So big thanks to him. rkoby13's words:
Click to expand...
Click to collapse
i'm glad u made it mate, and you're welcome....
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Sent from my SGS-II powered by CM9
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Good day developers, can you help me, Im using STOCK ROM DXMA1 (deodexed). I want to modify my "TouchWiz30Launcher.apk", instead of 4 icon Column dock, I want to make it 5. I follow this guide somehow, http://forum.xda-developers.com/showthread.php?t=1668984 but it didn't help me. It made my "touchwiz30Launcher.apk" 5 docks but when I put the other application(last time it was 4 and now it turns 5, 4+1=5) on DOCK, the application disappear. Then I tried following this guide again, http://forum.xda-developers.com/showthread.php?t=1500230 although it is for Galaxy Ace, I think it is similar somehow with SGY (note: I only did was, PART II number 1 and 2.)Then the problem in my first try modifying the TouchWiz30Launcher.apk is similar with the second one. Guys if you know, can you help me with this problem or guide me or if there are some similar questions/forum post like this that had been answered, kindly post it? Help me please.
did you install it as a system app?
try removing the classes.dex from original to the modified one,
also was the app compiling process a success?
gee i had to trouble reading the text on that one
deathnotice01 said:
did you install it as a system app?
try removing the classes.dex from original to the modified one,
also was the app compiling process a success?
gee i had to trouble reading the text on that one
Click to expand...
Click to collapse
Yes, I install it as a system app sir, I also replace the classes.dex from the original to the modified one. I use apktool sir, and it was success.
Sorry for the bad grammar though.
3r41nl33n said:
Yes, I install it as a system app sir, I also replace the classes.dex from the original to the modified one. I use apktool sir, and it was success.
Sorry for the bad grammar though.
Click to expand...
Click to collapse
grammar's good and understandable,
what happened when installing?
do you have a logcat?
maybe a cert mismatch
did it force close in anyway?
No FC sir. It just the application icon disappear from the menu and it was irreversible. Thanks anyway, I solved my case. This thread should be close now.
3r41nl33n said:
No FC sir. It just the application icon disappear from the menu and it was irreversible. Thanks anyway, I solved my case. This thread should be close now.
Click to expand...
Click to collapse
what the main problem did you facing and how do you solved it?? ??
assphere said:
what the main problem did you facing and how do you solved it?? ??
Click to expand...
Click to collapse
HIHIHI. I just modify Mr. zalzondabuzz 5 docks bottomfrom here, http://forum.xda-developers.com/showthread.php?t=1958201 . I just decompile his/her work and i transfer all the png's because, I dont want the actual TouchWiz30Launcher to be modified, it's just like I want to make it 5 docks. and thats it. xD
Hello guys, I have a Samsung Galaxy Note 3 SM-N9005 device on which I installed CyanogenMOD from a tutorial I found on the Internet, but everytime I was going through my Setting > About I could see that it showed my device as an N9000 device. So now I was thinking to do a reinstall with the correct hltexx version but when I'm trying to install the cm-11-20140123-NIGHTLY-hltexx.zip It shows me an ERROR: 'This package is for "hltexx" devices; this is a "hlte".
What can I do to fix my phone? I have already formated everything and I'm just waiting for a solution. I searched already on google but I couldn't find anything.
Thank you in advance, I will try to reply instantly check back if you replied. I hope I didn't broke my device.
Sorry for my English.
nexussp said:
Hello guys, I have a Samsung Galaxy Note 3 SM-N9005 device on which I installed CyanogenMOD from a tutorial I found on the Internet, but everytime I was going through my Setting > About I could see that it showed my device as an N9000 device. So now I was thinking to do a reinstall with the correct hltexx version but when I'm trying to install the cm-11-20140123-NIGHTLY-hltexx.zip It shows me an ERROR: 'This package is for "hltexx" devices; this is a "hlte".
What can I do to fix my phone? I have already formated everything and I'm just waiting for a solution. I searched already on google but I couldn't find anything.
Thank you in advance, I will try to reply instantly check back if you replied. I hope I didn't broke my device.
Sorry for my English.
Click to expand...
Click to collapse
You need to edit your updater script.
OR
You can try one of the custom CM's we have HERE on XDA, that have all the CM features plus some extra's baked in
nexussp said:
Hello guys, I have a Samsung Galaxy Note 3 SM-N9005 device on which I installed CyanogenMOD from a tutorial I found on the Internet, but everytime I was going through my Setting > About I could see that it showed my device as an N9000 device. So now I was thinking to do a reinstall with the correct hltexx version but when I'm trying to install the cm-11-20140123-NIGHTLY-hltexx.zip It shows me an ERROR: 'This package is for "hltexx" devices; this is a "hlte".
What can I do to fix my phone? I have already formated everything and I'm just waiting for a solution. I searched already on google but I couldn't find anything.
Thank you in advance, I will try to reply instantly check back if you replied. I hope I didn't broke my device.
Sorry for my English.
Click to expand...
Click to collapse
common problem !
extract the updater-script from the cm archive. folder = \META-INF\com\google\android
open in texteditor, remove the first line and save the file. (first line is the device check.)
repack the file to the archive.
flash and enjoy !
radicalisto said:
You need to edit your updater script.
OR
You can try one of the custom CM's we have HERE on XDA, that have all the CM features plus some extra's baked in
Click to expand...
Click to collapse
Thank you! Wow, so many of them which should I try. For start I will try to edit my updater script and if it doesn't work I will try something from that huge list you gave me! Thank you again!
Thank you A.N.Droid. I can't find the updater-script in META-INF>com>google>android. The only thing I can find there is the: metadata and otacert file, maybe it's because I'm using Linux and I don't have the right Archive Manager.
Should I delete the third line in metadata?
post-build=samsung/hltetmo/hltetmo:4.3/JSS15J/N900TUVUBMI7:user/release-keys
post-timestamp=1390477424
pre-device=hltexx
Click to expand...
Click to collapse
nexussp said:
Thank you! Wow, so many of them which should I try. For start I will try to edit my updater script and if it doesn't work I will try something from that huge list you gave me! Thank you again!
Thank you A.N.Droid. I can't find the updater-script in META-INF>com>google>android. The only thing I can find there is the: metadata and otacert file, maybe it's because I'm using Linux and I don't have the right Archive Manager.
Should I delete the third line in metadata?
Click to expand...
Click to collapse
Remove the two xx
radicalisto said:
Remove the two xx
Click to expand...
Click to collapse
does this work too ? just wonderig...
@nexussp
you looked at the wrong folder(\META-INF\com\android). updater script is located at \META-INF\com\google\android
A.N.Droid said:
does this work too ? just wonderig...
@nexussp
you looked at the wrong folder(\META-INF\com\android). updater script is located at \META-INF\com\google\android
Click to expand...
Click to collapse
I just realized that. THANK YOU EVERYONE, my phone is fine and is working like a charm.
And removing the two xx from hltexx in metadata doesn't work.
If you guys want to try the latest feature of Android 7.1 I.e. The google assistant on your One plus Device so well now you Can.
Prerequisites:- Your phone running android 7.0
Latest google app 6.6.x.x (worked for me.)
Build.prop editor.(better use es FM)
Procedure: 1.Open Es FM
2.Grant all the root permissions and note that the system is set on r/w mode.
3.Go to root.
4.Open System----->Build.prop
5.Edit ro.product.model=Pixel XL and add the line below the model one.
ro.opa.eligible_device=true
(SEE ATTACHMENTS IF CONFUSING)
You r good to go now...Just go and install the latest google app from apk mirror and then clear the data of google app once...Reboot your device.
And voila you now have google assistant on your device.
Thanks to senior member @xda brianelv for this trick.
Thanks man! It's working great
Everything of Google Assistant works fine but...
I can't use the "OK GOOGLE", it doesnt store the voice and asks me every time to say " OK GGOGLE" thrice. Any way to fix it? I am on AICP Nougat ROM . Do anyone have the same problem? If no , tell me. Thanks!
shubhaemk said:
I can't use the "OK GOOGLE", it doesnt store the voice and asks me every time to say " OK GGOGLE" thrice. Any way to fix it? I am on AICP Nougat ROM . Do anyone have the same problem? If no , tell me. Thanks!
Click to expand...
Click to collapse
That's Currently not working with any of the phones but is expected to be fixed in the coming update.
Stumbled upon another workaround and got it working on my marshmallow rom dude... Used xposed and an older google app.
http://www.droidape.com/get-google-assistant-marshmallow-devices/#respond
Where did you get the google app (Version 6.6.x.x) from? I'm using Open Gapps 7.0, and the version is 6.5.x.x
krikz said:
Where did you get the google app (Version 6.6.x.x) from? I'm using Open Gapps 7.0, and the version is 6.5.x.x
Click to expand...
Click to collapse
6.6.x.x is the beta build IIRC
0rgoner said:
6.6.x.x is the beta build IIRC
Click to expand...
Click to collapse
Can you please help me with a link?
krikz said:
Can you please help me with a link?
Click to expand...
Click to collapse
http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
isnt it better to use Pixel instead of Pixel XL as Pixel has the same resolution and wont have any issues with PlayStore due resolution?
I've tried the settings as per instructions, but can't seem to get Google Assistant to appear. Wondering if i missed out any steps. Is there any particular sequence. Like Google App must be 6.6 upon editing Build.prop?
xtremez said:
I've tried the settings as per instructions, but can't seem to get Google Assistant to appear. Wondering if i missed out any steps. Is there any particular sequence. Like Google App must be 6.6 upon editing Build.prop?
Click to expand...
Click to collapse
Are you on Marshmallow? Or Nougat?
krikz said:
Are you on Marshmallow? Or Nougat?
Click to expand...
Click to collapse
I'm on Nougat. I also tried flashing some zip files from one of the threads which seemed to work for most, I also cleared all data from the Google app
xtremez said:
I'm on Nougat. I also tried flashing some zip files from one of the threads which seemed to work for most, I also cleared all data from the Google app
Click to expand...
Click to collapse
Just edit build prop it is perfect
princeflash said:
Just edit build prop it is perfect
Click to expand...
Click to collapse
Here's a screenshot of the build prop currently.. Looks about right
xtremez said:
Here's a screenshot of the build prop currently.. Looks about right
Click to expand...
Click to collapse
Check my screenshot and add the last line. Reboot then clear data.
princeflash said:
Check my screenshot and add the last line. Reboot then clear data.
Click to expand...
Click to collapse
I thought it doesn't make a difference where that line of code is placed? Nvm will try anyway!
xtremez said:
I thought it doesn't make a difference where that line of code is placed? Nvm will try anyway!
Click to expand...
Click to collapse
ro.opa.eligible_device=true
princeflash said:
ro.opa.eligible_device=true
Click to expand...
Click to collapse
Thanks for trying to help, I did change that to end of the line.. But no avail
Even after the changes in build.prop the assistant was not working. So i just made the google app into a system app and now it works. "OK Google" detection still doesn't work though i wonder whne it will be fixed
Hi guys,
I just received the Android Pie update notification. Before I accept it I want to be sure that AdHell works with it.
Thanks
Yeah
Adhell3 working perfect
Yes, just make sure you have the latest version of it and you should be fine.
Using latest adhell3 from github, working perfect on pie.
Can anyone help me get adhell back working? I had to renew my key now its asking for elm key, how do I generate a new one?
NvWatts said:
Can anyone help me get adhell back working? I had to renew my key now its asking for elm key, how do I generate a new one?
Click to expand...
Click to collapse
Check the first post in this thread at reddit -
https://www.reddit.com/r/Adhell/comments/av97nk/ah3_v311_lives_on/
liamR said:
Check the first post in this thread at reddit -
https://www.reddit.com/r/Adhell/comments/av97nk/ah3_v311_lives_on/
Click to expand...
Click to collapse
I get error code 102
Check the license type and that Reddit post.
rhadoo_ds said:
Check the license type and that Reddit post.
Click to expand...
Click to collapse
Where can I get the XML file edit to change name bc apK editor didnt work for me?
NvWatts said:
Where can I get the XML file edit to change name bc apK editor didnt work for me?
Click to expand...
Click to collapse
You need APK Editor Pro. Use it to edit the package name (3,8,9 letters) line 6 in AndroidManifest.xml (XML File Edit). Don't forget to save the edited file and then generate new apk.
I have tried to update the adhell code from github ... and it messed up the entire build process ... the dev swithched to knox 3.3, and i guess that might cause my issue ..
having same issues either it gives me a 201 error even after multiple code recreations anddifferent versions. or it just closes and reasks for klm and we repeat tried creating own...still no go......any help....i had and forgot to just renew, so i accidently got rid of to recreate new...ooopps on my end and now i am here.......helllppp lol
I use apk easy tool for pc to decompile citizen v apk and modify the app name then compile and works great. I was having issues with apk editor pro on phone.
Just installed using this guide: https://is.gd/note9adhell
Pay attention that for Note 9, you need to edit the package name by editing AndroidManifest.xml, and not by using Basic Edit.
I used Basic Edit and it caused parse error.
So why do you guys all go through the process of compiling the app and all that other stuff when you can simply download the APK and install it.l, then enter your license key? I've been doing it that way for over 6 months, always worked perfectly. But today I downloaded the latest 3.1.1.290 and for some reason it won't accept my license key, it's always worked fine, I did start a thread about it and then found this so thought I'd post here too, see if anyone can help.
beta546 said:
So why do you guys all go through the process of compiling the app and all that other stuff when you can simply download the APK and install it.l, then enter your license key? I've been doing it that way for over 6 months, always worked perfectly. But today I downloaded the latest 3.1.1.290 and for some reason it won't accept my license key, it's always worked fine, I did start a thread about it and then found this so thought I'd post here too, see if anyone can help.
Click to expand...
Click to collapse
Probably because the dev doesn't recommend it and that's how other adblockers got black listed from Knox access. You don't even have to compile it.
You can use the app editor pro and edit the manifest.
Yours isn't working because you didn't modify probably....
I see quite a bit of misinformation in this and similar threads. Please keep in mind that AdHell3 is NOT supported on XDA. For official and up-to-date information about the AdHell3 project, please visit:
Main repo: https://gitlab.com/fusionjack/adhell3
Scripts for compiling: https://gitlab.com/fusionjack/adhell3-scripts
Get your EDU ELM key from: https://seap.samsung.com/license-keys/generate/edu
Official Support Discord Channel: https://discord.gg/hfreZum
Dependable(?) precompiled APKs: https://www.mediafire.com/folder/sb37c6gmhqgbn