yashsingh1/xdaforums huggingface dataset:
[Xperia SP Android Development] Furrydaus:
Attention!

I am really getting quite annoyed at the same post being repeated again and again so I shall clarify something's.

1) This ROM same like MrSteve ROM.

->It will have almost every hardware related bug because I am using HIS device source code. Android Source though is different because thats cm12 and this is RESURRECTION REMIX. If you do not know what all this means, look it up on Google and wake me up only when you've proven yourself worthy for me to talk to. :eek:

2) I CANT INSTALL ROM! YOU STUPID DEVELOPER

-> Knock,knock where's your brain at? I have made the first section clarifying the installation issues and all its fixes. You obviously did not read correctly :rolleyes:

3) I GOT FIRED BECAUSE THIS ROM DIDNT WAKE ME UP.

-> Again, knock knock? I placed a disclaimer that takes quite a large portion of the thread so if you did get fired, deal with it :cool:

4) When next update?

-> It is up to me and the Resurrection Remix to decide, please don't ask this type of questions all the time. If someone has already said it once, no point saying it again.

5) Support my device SLAVE!

-> Slave trade is illegal sorry.
[Xperia SP Android Development] tidusfox:
hi [MENTION=5934815]Furrydaus[/MENTION]

I turned off the option to develop and now I can not turn it back on it though I have clicked on the version number so many times

how to fix :confused:
[Xperia SP Android Development] pranavthombare:
You can find the fix here on xda
[Xperia SP Android Development] Furrydaus:
Thanks! Luckily it took me 10min to edit and upload the video. My old PC would take like 2hours :p
[Xperia SP Android Development] Nimagho:
We live in Iran!!lol :D

We cannot access to website ( social network , ...)

And so we must use VPN:p:D
[Xperia SP Android Development] pranavthombare:
It's okay, and don't think that you are being discriminated. Till now I never knew where you were from. I don't even know where furry is from. Who cares, here we are all the same.
[Xperia SP Android Development] kinggod018:
thak for your post

what about vpn ? is that fix this rom?

thaks
[Xperia SP Android Development] lop2lop:
:D thanks for your support friend :D

If you installed this ROM , Please test it :D

Thanks !

ROMi ke vpn roosh kar nakone ROM nist :D
[Xperia SP Android Development] SingularityHRT3:
RR 5.0.2 is working great for Me... I was using CM12 and I did a cache wipe and dirty flashed RR and after the 1st reboot I flashed Gapps... Till noe working Great... Thanks for the Great work [MENTION=5934815]Furrydaus[/MENTION]...

.

.

.

Waiting for a completely fixed ROM (don't care even if it is not that stable, just want all necessary things working by default incl. WiFi, Data n all...
[Xperia SP Android Development] air001:
Please don't repeat this false statement!

MrSteve hasn't got CM12 rom. CM12 was made by Bagyusz!

It's my fault. Sorry. I forgot that Steve relaesed the 21/11 build.:silly:
[Nexus 5 Q&A, Help & Troubleshooting] daScholar:
Hey guys,

So this is my first post after visiting XDA for quite some time, so you'll have to forgive my lack of finesse in my formatting. Anyway, I've had the common issue with the microphone in my Nexus 5 where the noise canceling was going overboard or the microphone wasn't picking up my voice well enough even being like 2 cm away. I found previous solutions that end up disabling EndFire in the build.prop. This has worked as a workaround, and a very noisy one as it picks up a ton of environment sound and I would get my own echo with absolute annoying clarity (which is what I'd rather the person on the other end hear). I've had this issue across a great number of roms so I know that those who experience this issue with their microphones won't get a solution by just changing and it goes to show how the software is in fact screwing up somewhere.

So I've done some experimenting from what I can pick up from the great community here and actually sorta stumbled on a two-part solution to this issue. This solution has me so stoked because I had a clean sound for the first time in a long while. So without further ado here's what you do.

View attachment 3087241

Before

View attachment 3087242

After

View attachment 3087243

Admittedly I don't know what changing those things does other than the fact that my microphone woes only happened on calls. I do know whenever I'd send a voice clip through fb and whatnot generally it went through just fine. So my hypothesis is that this forces the phone to uses those "channels" persay as I did pull those three changes from a different part in this xml. I also found the broadside term in this file just below endfire. Maybe it's an unused config, I dunno but it works, so best of luck to you who still need a clean voice calling solution.

Please help this solution get out there as I've yet to see anyone working on the mixer_paths.xml in this fashion (If I'm wrong about that my apologies). I've seen a large number of people trying to adjust the number values but to little success. I hope that this gets out there and proves to be a big solution for the community. Share if this helped!

Be awesome out there,

daScholar
[Nexus 5 Q&A, Help & Troubleshooting] chicocardo:
Loud echo

Thank you so much for this! It works, people can hear me now. Trouble is, there's a loud echo on the other end. Meaning that the other person hears their voice really loud making it quite annoying for them.

Any thoughts on this??

Thank you!
[Nexus 5 Q&A, Help & Troubleshooting] daScholar:
I'll look into this for sure. Thanks for the response. I tested this with myself on skype so not exactly the best experiment I'll definitely see if I can replicate this and tweak it so that doesn't happen. I've not heard of the receiving phone getting an echo from itself because of the senders phone settings, but I'm definitely no expert. Thanks for the feedback, will get back to ya soon.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
If it helps, the same echo is achieved by making these build.prop edits which I use to combat my ultra-low mic volume on lollipop

persist.audio.fluence.voicecall=false

persist.audio.fluence.voicecomm=false

persist.audio.fluence.voicerec=false
[Nexus 5 Q&A, Help & Troubleshooting] chicocardo:
Thanks, but echo continues. :( Echo is on other end, not my end.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
You've not been given a solution so why wouldn't echo continue?

I'm confused
[Nexus 5 Q&A, Help & Troubleshooting] chicocardo:
I thought you posted solution for the echo. I managed to sort out muffled mic with the solution on the initial thread, but with that came the echo from the other end. I thought you posted the solution for it.

Thanks
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
No. I was telling the OP that the build.prop edits that I use to combat low mic volume produce the same echo as his solution.
[Nexus 5 Q&A, Help & Troubleshooting] daScholar:
K So I've been trying to replicate it on my phone and can't seem too. Everyone I called said that things were just normal. Have you tried resolving the mic issue before by boosting the mic or speaker volume? Because maybe that's a factor and needs to be reset/disabled. I'm using a fresh rom install so nothing else audio wise has been touched. One thing I'd try is if you have MultiRom then just install another rom so you have a fresh install to try this fix on.

Another option is to go back to that mixer_paths.xml file and lower the values of either the "handset-mic" or one of the speaker values. I found the solution above with a lot of trial and error seeing what's happening. If nothing changes undo what you did and try another spot. (Make Sure to reset your phone everytime)

Is it everyone you are calling says that?
[Nexus 5 Q&A, Help & Troubleshooting] chdloc:
Just a quick note to the OP: the microphone device "broadside" has been deprecated in the audio HAL as of Android 5.0

I have spent way more time with audio on the Nexus 5 than I probably should have, but believe me, there is no real solution to this problem that can come from this community. At the telephony level, audio is adjusted via proprietary vendor blobs. Also, telephony audio never reaches user space.

Having said that, I did manage to find a workaround that disables array processing while retaining echo and noise control. It involves a custom kernel, Tasker, shell scripts, and a whole lot of TLC. Certainly not recommended for the casual user...
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
I'd be interested... I'm familiar with all those things. Please let me know
[Nexus 5 Q&A, Help & Troubleshooting] chdloc:
Please send me a PM as I do not intend to release my workaround publicly.

It would cause a major support headache...
[Nexus 5 Q&A, Help & Troubleshooting] daScholar:
Thanks for the info I am still on kitkat so that's a good thing to note for sure.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
I can only send pms to people on my friends list. I'll send a request shortly, please accept it.
[Nexus 5 Q&A, Help & Troubleshooting] chdloc:
Be careful. What you have done here is change the microphone from the main one (close to the USB port)

to the auxiliary one (close to the headphone port) for the "handset-mic" device. Echo is almost inevitable due

to the close proximity between the microphone and earpiece. As you can see in the mixer file, speakerphone

mode deliberately switches from the main microphone to the auxiliary one for (likely) this very reason.

Also, I suspect that the "handset-mic" device is not even used during cellular telephony when beamforming (any dmic device) is enabled.

I cannot currently verify this suspicion as I have disabled beamforming altogether in my setup. But you can easily check by looking at the output of

logcat | grep audio_hw_primary

while making a cellular call.

Edit: Just checked, and no, by default the "handset-mic" device is not used while making cellular calls.

Note that dual-microphone processing is enabled only when making cellular calls. Skype, Hangouts, Viber, other VoIP apps, and other random voice recording apps (including Google Now) *will* use the "handset-mic" device and possibly choke when presented with your mixer_paths.xml edit.

Edit: Come to think of it, you guys having issues with low TX levels, try to lower your earpiece (loudspeaker playback) level as much as practical. Depending on what the dual-microphone algorithm (endfire) actually does, it is possible that TX levels are reduced due to the occurrence of double-talk in the presence of very high coupling between the earpiece loudspeaker and the auxiliary microphone. If my theory is correct, then your TX level may be modulated as a function of how loud the far-end is (regardless of whether it's speech or some other background signal).
[Nexus 5 Q&A, Help & Troubleshooting] daScholar:
Thanks for that info. The strange thing is now I've reverted the mixer file back to the original and I'm not getting all the background noise that I was before... Not quite sure why it's working now. I've still got broadside in my build.prop in place of endfire. Strange thing was is that the first time I had only made that change to the build.prop I still got tons of environment noise. I've only used this on Kitkat and looks like this won't work on lollipop. You we right about the other apps being choked out as I hadn't even thought to look into that, rarely using them. Thanks so much for all the input, being somewhat of a noob to this, all of the info you guys are giving is a treasure trove for me. Thanks.

Edit: Forgot to mention something specifically about that handset-mic device put back to default is causing an echo where I hear myself did you have any suggestions pertaining to that?

Edit: so I changed the ADC3 parts back to ACD1 and left the DEC4 change as is I'm now getting both VoIP and Calls clearly dunno how that's related to the echo though as you said there wasn't anything in the log pertaining to the handset-mic
[Nexus 5 Q&A, Help & Troubleshooting] chicocardo:
Thanks for giving it a try. Yeah, everyone is complaining about that issue. I find it wierd that you don´t have that, other users are complaining about the same echo,

Which ROM do you have? I have Cataclyst.

Thanks
[Nexus 5 Q&A, Help & Troubleshooting] chdloc:
What you are seeing may be related to what I have observed in my own testing several months ago. Broadside seems to be working, but I noticed it being a lot more finicky than endfire in that it would attenuate the TX much more frequently than endfire would. Plus, the first call after a reboot was always bad (echo and noise). Toggling speakerphone fixed that for the remainder of the system uptime. Not sure what is up with that, but I think it is related to calibration. As I said before, the broadside setup has been removed from the audio HAL as of Android 5.0

Do you hear yourself with a delay or does it sound pretty instantaneous?

If it is instantaneous, then what you are hearing is called sidetone. Every handset feeds a low-level copy of the microphone signal back to the loudspeaker in order to make up for the sound blocked by the device being pressed to your ear. The idea is to make a telephone conversation sound more like a natural face-to-face conversation where you can hear yourself clearly without any obstructions that cover your ear. Pretty clever if you ask me.

In your case the sidetone may be too loud.

If you hear yourself with a delay, then the sound is being reflected by either the far-end (acoustic echo) or by the network itself (network echo).

Do you hear yourself when you revert to stock settings throughout your system?

So how does your mixer_paths.xml file look like? From what you are writing it is not quite clear what you did.
[Nexus 5 Q&A, Help & Troubleshooting] daScholar:
So I've installed the stock 4.4.2 and changed just the build.prop to broadside and it seems to be working thanks for the advice. No changes now to the mixer file.
[Nexus 5 Q&A, Help & Troubleshooting] silviu_nanau:
Fixed my phone

I followed both steps, and made tests after each of them.

Step 1 - Fixes the microphone problem, but there are still fade-outs in the voice and possible echoes in noisy conditions.

Step 2 - Resolved the echoes and provides crystal clear clarity.
[Nexus 5 Q&A, Help & Troubleshooting] migimantas:
I owe you my life!!! Thank you. I have replaced flex cable I have been trying to reflow solder joing of flex connector and nothing helped my nexus 5 mic was still not working and after your SOLUTION MY PHONE MIC IS FIXED AND RECORDED SOUND IS VERY GOOD QUALITY!!!!!
[Nexus 5 Q&A, Help & Troubleshooting] sinno:
Hi,i have been trying to solve the mic issue on lollipop 5.1.1,are there any special settings,i only get sound from youtube with headphones and mic doesnt work with easy voice recorder but does with headphones
[Nexus 5 Q&A, Help & Troubleshooting] biro2200:
You are a true hero! It worked for me!
[Nexus 5 Q&A, Help & Troubleshooting] berhan:
Please excuse my bad english.

First of all, I use an N5 with MM. The N5 is rooted.

When I change in the build.prop the persist.audio.dualmic.config from endfire to broadside, after a reboot the N5 didn't use broadside. It use the hendset-mic configuration (I have checked this with logcat) but in the build.prop persist.audio.dualmic.config the config is endfire. The sound is better, but I have no dualmic configuration with noise cancelling.

So I go back to the original configuration and overwrite the build.prop persist.audio.dualmic.config endfire with endfire and start the N5 again. Now the N5 use the speaker-dmic-endfire configuration.

In the next step, I study the mixer_path.xml and modify the Dual MIC configuration.

I change the

<path name="speaker-dmic-endfire">

<ctl name="AIF1_CAP Mixer SLIM TX7" value="1" />

<ctl name="AIF1_CAP Mixer SLIM TX8" value="1" />

<ctl name="SLIM TX7 MUX" value="DEC6" />

<ctl name="DEC6 MUX" value="ADC1" />

<ctl name="SLIM TX8 MUX" value="DEC4" />

<ctl name="DEC4 MUX" value="ADC3" />

<ctl name="SLIM_0_TX Channels" value="Two" />

</path>

to

<path name="speaker-dmic-endfire">

<ctl name="AIF1_CAP Mixer SLIM TX7" value="1" />

<ctl name="AIF1_CAP Mixer SLIM TX8" value="1" />

<ctl name="SLIM TX7 MUX" value="DEC6" />

<ctl name="DEC6 MUX" value="ADC1" />

<ctl name="SLIM TX8 MUX" value="DEC4" />

<ctl name="DEC4 MUX" value="ADC3" />

<ctl name="SLIM_0_TX Channels" value="Two" />

<ctl name="ADC1 Volume" value="17" />

<ctl name="DEC6 Volume" value="88" />

<ctl name="ADC3 Volume" value="10" />

<ctl name="DEC4 Volume" value="80" />

</path>

Now the sensitivity of the second microphone is lower, and the sound is fine for me.:laugh:

You can check the different of the sensitivity with the app "audio recorder" with the function microphone test.

The only problem is now a different sensitivity for stereo tone recording.
[Nexus 5 Q&A, Help & Troubleshooting] dalepothen:
Can any one help me ?? Im using blisspop rom 5.1.1 can any one give there details to change. I have the same problem my incall mic is not workind but when i put it to. speakerphone it works

---------- Post added at 07:37 AM ---------- Previous post was at 07:09 AM ----------

And i dont have persist.audio.dualmic.confi in build prop ??
[Nexus 5 Q&A, Help & Troubleshooting] berhan:
Does your microphon works with other applications. When the microphone (near the usb port) never works, maybe you have a hardware problem. I can not post a link but you can find many solutions in google with "youtube nexus 5 mic".
[Nexus 5 Q&A, Help & Troubleshooting] Gialloblu:
It worked! but indeed it sounds a bit like you're in an echo environment... but hey! I'm just happy people understand me! Thanks!
[Nexus 5 Q&A, Help & Troubleshooting] daScholar:
So I'm no longer on the Nexus 5 so I won't be able to help much. What I can say is if in the Build.Prop editor changing endfire value to broadside alone fixed my issue. I never came up with any terminal options when saving the xml files. Since I don't have the phone I can't experiment with the xml, but all I did was save changes.
[Nexus 5 Q&A, Help & Troubleshooting] Gialloblu:
It's fixed, had to press back on soft keys and not on top! But interesting.. Did both, but maybe broadside was also enough..

Verstuurd vanaf mijn Nexus 5 met Tapatalk

---------- Post added at 07:23 PM ---------- Previous post was at 07:17 PM ----------

there is indeed an echo for the others which they find annoying, any help on that please?
[Nexus 5 Q&A, Help & Troubleshooting] daScholar:
Aside from editing the mixer_path.xml file I can't say I know of anything else. I do know that can mess with other applications use of the microphone. Wishing you luck though, Sorry mate.
[Nexus 5 Q&A, Help & Troubleshooting] Gialloblu:
It's apparently very loud echo and it's irritating for others..

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Nexus 5 Q&A, Help & Troubleshooting] amilt0n:
This solution is really helped me to almost remove echo: http://xdaforums.com/showpost.php?p=63563656&postcount=24
[Nexus 5 Q&A, Help & Troubleshooting] drmuruga:
Thank you so much. You save my phone. As per your guide my n5 mic working well. Such a genius you are.
[Android Apps and Games] samba270:
This is an fun and educational math game for everyone, this is a good brain test and you can improve your math calculations speed. After playing this cool math game, you definitely will calculate faster !

This is my very first game. So I would really appreciate feedbacks :good:

Thanks ! :D

Link: https://play.google.com/store/apps/details?id=com.kheygames.swingmath
[Android Apps and Games] samba270:
Update 1:

New Design :D
[Android Apps and Games] Entangled Multiverse:
Hey, I like your math game, it's simple and fun ;)

If you want to add features here are my suggestions:

- different difficulty levels (for young kids that are just starting, it would be good to offer versions with just addition, no negative valued results etc.)

- sound + music

- leaderboards

- functions like share / rate
[Android Apps and Games] samba270:
Thanks for your feedback :D
[Android Apps and Games] samba270:
Others feedbacks ?

Please :D
[Android Apps and Games] samba270:
Up
[Android Apps and Games] can_i_be:
Entangled Multiverse pretty much said it all

1. Vary the difficulty level ([+,-], [+, -, *], [+, -, *, /]) and calculations that give negative numbers

2. Add some form of music and/or sounds

3. A way to track highscores (leaderboard)

4. Highlight the question/answer got wrong?

All in all, nice concept.
[Android Apps and Games] Katie Ka:
good)

New desighn is good)
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] a.demarco:
So out of the blue my 1-year old SM-P600 won't charge. Tried 2 different charging cables, and nothing. Haven't tried plugging it in to a computer yet through a USB cable, gonna try that when I get home today.

Anyone else run into this yet? If so, what were your solutions?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] uncensoredtr:
Have you tried different cables only or different chargers? If charging from usb works, try another charger.

SM-P601 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] a.demarco:
I tried two chargers and two cables... One charger is bad because it doesn't charge my phone either, didn't know that until I tried it. The other will charge my phone, but not my tablet.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] uncensoredtr:
We should wait for if charging from pc works or not. If it doesn't work then your charging circuit fried and you should take the tablet to samsung, if it works then you should buy another suitable charger.

SM-P601 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] a.demarco:
No warranty since it is rooted, correct?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] uncensoredtr:
I guess it depends on the country and your ability to persuade them that rooting and charging hardware are not related.

SM-P601 cihazımdan Tapatalk kullanılarak gönderildi
[HTC Desire 510] _ck_:
I am trying to decide if I want to get in on the last week for Cricket with the htc 510 for free after rebate.

Reading up on this phone it looks like you do have root but the 64bit cpu is causing a hinderance with getting things like TWRP recovery and cyanogenmod.

It also doesn't appear to have little quality build things like gorilla glass.

Since the phone really isn't free, you have to pay for service for a month or two, I am wondering if anyone would hesitate to sink money into it again.

I don't see the benefit of 64bit on a phone and being the first means it also will be last to get software extras.
[HTC Desire 510] DX///M:
no, due to its complicated steps of hacking

- unlock bootloader (relock, and re-unlock (not available yet?)),

- TWRP recovery not assessable after relock bootloader (fastboot oem lock)

- cricket online would show device as "non-cricket device" and your phone's bootloader would say "TAMPERED" -> reduced resale value

- scarce ROM options compared to MOTO G

- ROM/radio/kernel options are mixed up for Sprint/Boost/Virgin/Cricket and no one knows for sure which works on which...

- digitizer seems not register touches properly. you need to touch lower part of what you wanted to touch (button, softkey) to get the phone respond

- digitizer seems sometimes less responsive to touches while other times too sensitive to a little moistures (like sweat from hands)

- its charging port on the right bottom side make it inconvenient to get docked in the phone holder in my car and be charged in the same time. (The stopper is usually on both sides of the phone, leaving the middle part open (where most phones having their charging ports))

i have mine in light use since 12/26 and i regretted my decision, I used MOTO G before but I dislike its round and curve back case and I wanted to experience stock Sense UI. So I took the chance experiencing it... but...

if you have a MOTO G in mint condition from cricket (LTE-support), I'd consider a trade with the extra $25 LOL

good luck