[ADDON] CM7 Dewonkificator [v1.4 03/17/11]

Search This thread

Chosen_on184

Senior Member
Jul 27, 2009
874
65
Only rears its head when i have this app installed. Like i said i went without it for a few weeks and it never showed up.

Installed this app and withing 5 minutes phone became unresponsive.

Not bashing the app, it works for the majority, however it has been mentioned in a few kernel threads that this app does cause it.

I know the call wonk (delay before someone can hear you) is a GB issue. The black screen to my knowledge is not.
 

Bay Harbor Butcher

Senior Member
Nov 26, 2009
180
15
Hi..I love this app but I hate to have any icon in my notification bar.
I installed latest release and I have a little android in my bar.
Is it possible to delete it keeping the app working?thanks..
 

Bay Harbor Butcher

Senior Member
Nov 26, 2009
180
15
thanks..but I have huge problems with dewonkificator and my N1 with CM7.
Phone freezes and need to remove battery..
It is quite strange,I used this app for more than 1 month with first releases of CM7 and never had one freeze.
 

Chosen_on184

Senior Member
Jul 27, 2009
874
65
thanks..but I have huge problems with dewonkificator and my N1 with CM7.
Phone freezes and need to remove battery..
It is quite strange,I used this app for more than 1 month with first releases of CM7 and never had one freeze.
Yea its a side effect of running dewonkificator. I had that issue for quite some time before i narrowed it down to this app. Went without the app for a month and dealt with the call delay bug and never had a wake issue.

Soon as i installed and ran the app again wake issues started up again.
 

new2smart

Member
Sep 30, 2010
12
0
I am using I897 with CM 10.1.3-RC2 currently but as far as i can remember have always have this issue of caller unable to hear me when I answer the phone until about 10secs (I looked at the timer on the screen) on most calls. I have no issues if I am the one calling.

I tried Dewonkifier and also call delay patch but none works. What can be done about this? Its frustrating as its as good as not having a phone since I can't answer incoming calls like how a phone should.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 48
    OK, I have written an app to attempt and stop call wonkyness on CM7 builds. Specifically the phone locking up when making and receiving calls.

    It's my observation that it's the mic that causes the phone to lock up and so this app opens and closes the mic every minute to keep it "fresh". It's a long shot, but I can't seem to duplicate wonkyness with it enabled so I'm posting it for other to try.

    Now after a few positive comments to help boost my confidence in the app, I've made it's own thread to make it easy to track comments.

    Just install and run (or just reboot as it auto-start on boot). To disable, uninstall it.

    Please post your results!

    Change Log:
    Version 1.4
    • Made service more persistent by adding notification bar. Turns out, Android was killing off the service when memory was running low causing wonk to surface.

    Version 1.3
    • Can only be installed on internal memory. Needed to make sure the service can started up on boot. (Thanks to mjukis for pointing this out)

    Version 1.2
    • Only dewonkificates when screen is off to avoid conflicts with any apps you may be using.
    • Removed debug logging
    5
    OP updated with 1.2 (Only dewonkificates when screen is off to avoid conflicts with any apps you may be using.)
    2
    QUOTE=tolemac;11140837]I don't know what it's the real problem, what is the cause of this problem?
    The first thing that I thought when I saw the code were to handle the incomming call intent, but I don't understand why you are using this interval (1 minute)

    Every way, I get this error each minute in my nexus one. Extracted with ddms:

    Code:
    02-05 06:28:00.990: ERROR/MediaRecorder(7960): stop failed: -1007
    02-05 06:28:01.000: ERROR/Dewonkificator(7960): recorder.stop()
    02-05 06:28:01.000: ERROR/Dewonkificator(7960): java.lang.RuntimeException: stop failed.
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at android.media.MediaRecorder.stop(Native Method)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at com.mb.dewonkificator.DewonkificatorBroadcastReceiver.onReceive(DewonkificatorBroadcastReceiver.java:45)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:709)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at android.os.Handler.handleCallback(Handler.java:587)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at android.os.Handler.dispatchMessage(Handler.java:92)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at android.os.Looper.loop(Looper.java:123)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at android.app.ActivityThread.main(ActivityThread.java:3809)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at java.lang.reflect.Method.invokeNative(Native Method)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at java.lang.reflect.Method.invoke(Method.java:507)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
    02-05 06:28:01.000: ERROR/Dewonkificator(7960):     at dalvik.system.NativeStart.main(Native Method)

    thanks,[/QUOTE]

    You're make an assumption that the code fixes the wonk, when, in fact, its actually preventing it. Wonk happens when an app tries to access the mic after the phone has been sleeping. Doing it when the phone state changes would be to late. This app keeps the mic "fresh" for when it's needed by using it once a minute.

    Oh, and i already removed the extra logging and updated the OP

    Sent from my SCH-I800 using XDA App
    1
    That's great news and I'm happy that it looks like it's working for people. I was on the edge of rolling back and this was a desperate attempt to fix it. :D
    1
    I don't see any different in battery drain. If there was any kinda drain, it's not enough to offset the good this app is doing.:D