[DaveRichardson]

Anyone else getting echo complaints from people on the other end of calls? I don't mean the normal AOSP speakerphone echo. Even in normal phone calls (with my speaker volume turned way down) the other person says they can hear themselves echo louder than they can even hear me speak. They have to pause every 3 seconds to let themselves "stop talking."

Otherwise, I couldn't be happier with the rom. Thanks, Phantom, for all your work bringing AOKP to our phones!

[MistaWolfe]

DaveRichardson, on 14 November 2012 - 06:08 PM, said:

Anyone else getting echo complaints from people on the other end of calls? I don't mean the normal AOSP speakerphone echo. Even in normal phone calls (with my speaker volume turned way down) the other person says they can hear themselves echo louder than they can even hear me speak. They have to pause every 3 seconds to let themselves "stop talking."

Otherwise, I couldn't be happier with the rom. Thanks, Phantom, for all your work bringing AOKP to our phones!

Known issue.

Sent from my SCH-I535 using Tapatalk 2

[kingdroid]

MistaWolfe, on 14 November 2012 - 08:19 PM, said:

Known issue.

Sent from my SCH-I535 using Tapatalk 2

do u no what eclipse is based off of??.. I ask cause on eclipse I dnt experience any of the echo issues.. 😲

Sent from my SCH-I535 using Tapatalk 2

[thekendog]

I had to enable both NFC and S Beam on an ICS TW rom then go back to a nandroid of AOKP to get NFC back. Anyone know why this appeared in recent builds? I'm on M1 for now.

[PhantomGamers (OP)]

kingdroid, on 14 November 2012 - 09:16 PM, said:

do u no what eclipse is based off of??.. I ask cause on eclipse I dnt experience any of the echo issues.. 😲

Sent from my SCH-I535 using Tapatalk 2

it probably just doesn't use the open source audio drivers we use

[mds96]

I reported this on Hilbe's forum so I figured I should post it here also. I did a couple more NFC tests and all went well. First I flashed his latest unstable over a backup that I had already flashed the NFC fix zip over and NFC was working as it should. Next I did a new, clean flash of the unstable build and NFC was working from the start. The only test I didn't do, which would probably be the most help, was flashing the unstable after being on a rom w/o NFC working. If no one wants to try it, I could probably do that also! Lol

Edit:The above tests also were successful with Phantom's 11/14 build. Now I'm gonna flash a rom with the NFC fix not included, then try both Phantoms and Hilbe's builds. Will report back when done

Edit: Last test complete. Flashed a clean install of Hilbe's latest stable(doesn't include the NFC fix), and as expected, NFC would grey out when checked. Then I clean flashed Phantom's 11/14, and NFC worked from the start. So my theory is, unless the PS2 that Phantom informed me that BMc submitted works, then you still have to go back to a TW rom, enable it, then you will be good after that. I say this because if it didn't work for people, then it has to work for me since I enabled it on Beans build 2 before coming back to AOKP a few builds ago. Hope all this testing helps some users.

Edited by mds96, 15 November 2012 - 10:15 AM.

[luv2increase]

mds96, on 15 November 2012 - 09:15 AM, said:

I reported this on Hilbe's forum so I figured I should post it here also. I did a couple more NFC tests and all went well. First I flashed his latest unstable over a backup that I had already flashed the NFC fix zip over and NFC was working as it should. Next I did a new, clean flash of the unstable build and NFC was working from the start. The only test I didn't do, which would probably be the most help, was flashing the unstable after being on a rom w/o NFC working. If no one wants to try it, I could probably do that also! Lol

Edit:The above tests also were successful with Phantom's 11/14 build. Now I'm gonna flash a rom with the NFC fix not included, then try both Phantoms and Hilbe's builds. Will report back when done

Edit: Last test complete. Flashed a clean install of Hilbe's latest stable(doesn't include the NFC fix), and as expected, NFC would grey out when checked. Then I clean flashed Phantom's 11/14, and NFC worked from the start. So my theory is, unless the PS2 that Phantom informed me that BMc submitted works, then you still have to go back to a TW rom, enable it, then you will be good after that. I say this because if it didn't work for people, then it has to work for me since I enabled it on Beans build 2 before coming back to AOKP a few builds ago. Hope all this testing helps some users.

That was really informative. Thanks for sharing.

Sent from my SCH-I535 using Tapatalk 2

[TenderloinShadow]

MistaWolfe, on 14 November 2012 - 08:19 PM, said:

Known issue.

Sent from my SCH-I535 using Tapatalk 2

damn, i thought we finally had that fixed.

[mds96]

I have great news everyone! BMc posted a pic of AOKP 4.2 on our device! He said it will be added once it is functional! It has the com.android.phone has stopped warning and it looks like it has no data, but it is booting, so that's a big plus in itself!! Not much longer peeps!

Attached Thumbnails

• 

Edited by mds96, 28 November 2012 - 06:16 PM.

[PhantomGamers (OP)]

Not to get ya'll too excited but I feel like we're right around the corner of a 4.2 AOKP build