yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] daveid:
Yeah, see the thing is... I do occasionally wonk, sure enough. Though I could never get it to wonk on command, if ya get my drift... so testing a fix, when I couldn't make it break, wasn't logical. Now, it started getting worse and on important calls. So, I thought I would try your app. It does seem to work, I guess, though I didn't wonk all the time without it, at least I haven't wonked since installing it. But, I don't get/make too many phone calls, so I can't say for sure it is doing a thing.

Which is why, when I saw the error messages in my log file, I thought I would ask if that was to be expected. Normally an error from an application means it is not doing something it wants to properly. So, I figured I would ask you (it is your program, right?). Does your logcat show errors similar to mine, does anyone's? If not, wouldn't that indicate that something wasn't right on my setup? Which explains my asking, since no one has posted anything about this in the thread - and I did read each post first to make sure - I thought I may be the only one getting these errors.

Thanks.
[Nexus One Android Development] TheMasterBaron:
It appeas to be normal since I'm getting the error also. I've updated the app to not log the error since it seems to be normal and I really shouldn't be filling up the log with extra stuff. Thanks you pointing it out.
[Nexus One Android Development] daveid:
And thank you for bearing with me and for de-cluttering my log!
[Nexus One Android Development] tolemac:
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:

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,
[Nexus One Android Development] _-..zKiLLA..-_:
LOL you just about made my day bro
[Nexus One Android Development] TheMasterBaron:
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:

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
[Nexus One Android Development] SBERG117:
Just loaded the apk, got the Wonk started message, restarted the phone and made a call.....surprise....it went through first time..lol.

Obviously im gonna have to give it a few days to see if its really doing its thing but having the first one go through was good to see. Thnx.
[Nexus One Android Development] Annihlist:
Just installed apk. No wonks so far. Thanks :)
[Nexus One Android Development] maedox:
Seems to work nicely. Thank you very much! :D

PS: The log message says "Dewonkificatated". Shouldn't it be Dewonkified or perhaps Dewonkificated?
[Nexus One Android Development] TheMasterBaron:
Is it really possible to misspell a made up word? ;)

Glad it's working for everyone
[Nexus One Android Development] temasek:
U see fit what is the name of it cuz u created it. Call it dewonkfuckactor if u like and we will use it gladly. :D
[Nexus One Android Development] [hfm]:
Should change it to Dewonkificator Super Elixir.

Tinctures and Tonics from faraway exotic lands cure all call problems.. Guaranteed!
[Nexus One Android Development] melder2011:
Been using it for maybe 3 days? Seems to be working! I don't call too terribly much, but I havent had a wonk in about 20 calls incoming and outgoing.
[Nexus One Android Development] ~semsem~:
Thanks a lot, perfect with CM7 Nightlies.
[Nexus One Android Development] uberingram:
Pleased as punch. Will report back after a few days. I've been flipping between nightlies and 6.1.1 out of frustration and nerdiness.
[Nexus One Android Development] kitsunisan:
Four days and three nightly flashes and not a wonk in sight. :D
[Nexus One Android Development] martinl1030:
weird i downloaded the apk in my browser but it refused to open when i tried to install it from the download folder. Had to go through astro and it installed without a hitch hopefully this will cure my wonk.
[Nexus One Android Development] TheMasterBaron:
OP updated with 1.2 (Only dewonkificates when screen is off to avoid conflicts with any apps you may be using.)
[Nexus One Android Development] markhm1978:
Thanks! :D
[Nexus One Android Development] Mutalemwa:
Thanks a billion!!

Had issue with N1 for days. Good work.
[Nexus One Android Development] dopedope:
Thank you very much!! Installed for couple of hours, works like a charm! Great Work!!! Can Cyanogen get this plugin for the next nightly release?
[Nexus One Android Development] bu2askoor:
Guys,

I updated to CM7 to face the issue of people not hearing me when i call or receive a call. Even my voice cannot be heard when using an app like voice recorder. I restored to CM6 and faced same issue?! The only way to fix this is to plug a handsfree headphone and unplugging it. Then my mic works fine in voice recorder and in calls.

Is this a hardware issue or a software one? Did anyone face same issue in CM6?

Thanks
[Nexus One Android Development] baseballfanz:
This is a question to ask in CM7 thread not here. Anyhow its a software problem that might be in the kernel. Use Dewonkficator as a temp till solution is found.
[Nexus One Android Development] JesseK:
This thread NEEDS to be bumped.

Wow, amazing.

I was getting so fed up with the nightlies, and my inability to use my phone as a ... phone.

It recently started bogging down and being unable to unlock. So far, this so good.
[Nexus One Android Development] markouk:
This app has saved CM7 Nightlies!! It was driving me mad when I tried to call out or received a call. I was having to call my voicemail first before making a call.

I also had a problem waking the phone with the trackball or even the power button.

Dewonkified and Happy!
[Nexus One Android Development] JesseK:
Same here, to all of that!
[Nexus One Android Development] Echoztrip:
I almost flashed away from a CM7 until I saw this. Tested it this morning and successfully answered a phone call! (unlike yesterday morning when I could hear them, but they couldn't hear me!)

Thanks a lot!
[Nexus One Android Development] markhm1978:
Preach it Brotha! :D

Would still be running CM6 if it wasn't for this jewel.
[Nexus One Android Development] britoso:
version 1.2 worked for me, build 43.

Poor wonk was squashed as soon as he showed up.

Thanks.
[Nexus One Android Development] qvert:
do we still need this at the nightlys? or is it fixxed? or maybe if there is no "fix" can't this app be implemented in cm build?
[Nexus One Android Development] morfy50:
Installed RC1 and was immediately bitten by the wonks.

Dewonkificator saved the day. Works beautifully. Thanks!!
[Nexus One Android Development] mjukis:
I have had big problems with the wonks and couldn't get this defonkificator to work either. After I lost my last hair trying to figure out what I did wrong. To make it work I can't have the app installed on the sdcard. Is this expected behaviour?
[Nexus One Android Development] celloin:
It's wired. Yesterday I removed rom manager premium key from my N1 and the problem seemed to be solved. Anyone else here can verify this for me?
[Nexus One Android Development] rori~:
no rom amnager premium here, but still wonk
[Nexus One Android Development] paulk_:
Never had the premium key, but still get wonks!
[Nexus One Android Development] baseballfanz:
This thread should be up top.:D

Thanks for the update.
[Nexus One Android Development] ChongoDroid:
I live for the wonk, i die for the wonk.

Sent from my Google Phone
[Nexus One Android Development] loadlu1:
for cm7 rc1, it works perfectly, cheers~~
[Nexus One Android Development] Calypsys:
People that call me still get ~5 sec blackouts once i pick up the phone.

App running from internal / CM7 RC1 / Permissions Fixed.

Maybe its Radio thing? I've got 4.06
[Nexus One Android Development] Hanneskitz:
Same problem here! Please help!
[Nexus One Android Development] britoso:
I get this too and dont think its wonk related. My delay is about 2 seconds. I suspect 'flashlight alerts', but I like that app too much to part with it. :rolleyes:
[Nexus One Android Development] WaPeR32:
My delay is about 2 seconds too. Still better than a wonk :D
[Nexus One Android Development] petep86:
You are the man!!! Still can't believe cyanogan put out a release candidate, when the most important part of our phones, THE PHONE, wasn't working! !! I'm in shock. But I guess that means, when gingerbread ota is released, cm7 will go stable..
[Nexus One Android Development] niubia:
sometime word bad:D
[Nexus One Android Development] J360:
What does the zip file do if the other one is the apk?
[Nexus One Android Development] baseballfanz:
Just use the apk. Zip is source file
[Nexus One Android Development] J360:
Got it. Thank you for the help
[Nexus One Android Development] celloin:
Since cm nightly gingerbread 2.3.3 has been released today, do we still need this add-on as temporary solution?
[Nexus One Android Development] baseballfanz:
Yes but only if you're experiencing wonkiness.
[Nexus One Android Development] celloin:
So I'll test it by myself on my Nexus One.
[Nexus One Android Development] celloin:
Since wonkiness issue takes long to reproduce. Can anyone report whether Google has addressed this issue on 2.3.3? New 2.3.3 should be available for Nexus S and Nexus One. So I believe wonkiness should has been fixed?
[Nexus One Android Development] baseballfanz:
it has nothing to do with google.
[Nexus One Android Development] celloin:
CM nightly passion build 11, Gingerbread 2.3.3 did not fix wonkiness issue.
[Nexus One Android Development] Skyheartblue:
So, do we need this patch for build #12 as well?

Is it working?

Thanks,

JB
[Nexus One Android Development] baseballfanz:
It's working fine for me up to build 11. Have not yet try on build 12
[Nexus One Android Development] celloin:
Nightly 13 was out. Hope it fixes wonkiness issue.
[Nexus One Android Development] thatguyzx:
Stayed away from cm7 this whole time cuz of wonk. Trying 13 just to check out progress, got wonkiness on my first test... ha. This actually seems to help though.
[Nexus One Android Development] :
rc2 cm7 reporting in. still got the wonkiness, gonna try the fix now.
[Nexus One Android Development] bluefish76:
I don't have the wonk? Am I in some way abnormal?

I've been following this thread for a while. I didn't flash RC1 due to the amount of people having the wonk. But when RC2 came out I couldn't wait any longer and had to have me some of that Gingerbread goodness.

So I expected the wonk. And had the Dewonkificator on the SD Card ready to install if I had it. But...4 (actually 5) days in and several calls later (outgoing and incoming) I haven't had the wonk?

Could it be that I am just lucky? Or is the wonk lurking behind a curtain or hiding in the cupboard ready to unleash it's wonkiness hell when I least expect it?

All seems a bit wonky to me ;)
[Nexus One Android Development] TheMasterBaron:
Not every phone gets the wonk including Cyanogen's. I think that's why he is having trouble fixing it.
[Nexus One Android Development] makelegs:
Newest prebuilt kernel took a huge step forward. Wonk is substantially reduced. It's almost tolerable, even.
[Nexus One Android Development] TheMasterBaron:
YES! Time to give it a try without the dewonkificator
[Nexus One Android Development] TheMasterBaron:
The phone is no longer locking up, however I'm having 5-10 seconds where the other person can't hear me on an incoming call. Will reinstall dewonkificator and see if that goes away.

EDIT: Well is seems I still need dewonkificator to prevent muting issues on answer.
[Nexus One Android Development] lcchan1:
You have 2 files (zip and app) here, which one to install?
[Nexus One Android Development] TheMasterBaron:
You only need the apk. The zip is source code.
[Nexus One Android Development] DXPetti:
Took my phone 3 or so weeks on RC1 and then the wonk showed its ugly face. Upgraded to RC2 a few days ago and still have the wonk. Very tempted to go stock Gingerbread because of this but I'll give this app a go!
[Nexus One Android Development] bunnahabhain:
Does this work for other ROMs? Tried to install the desire sense BUILD from MoDaCo! An it has the thing that you call wonk :D

See here:

http://xdaforums.com/showthread.php?p=12140385

Thanks in advance...
[Nexus One Android Development] makelegs:
Ummm.....why not try it out and then report back to us??? You could be a dewonkificator pioneer!!! ;)
[Nexus One Android Development] bunnahabhain:
hmm... couldn't installa.

Gives me "There is a problem parsing the package" :(
[Nexus One Android Development] TheMasterBaron:
Have you tried re-downloading the apk?
[Nexus One Android Development] temasek:
When u have that error it usually is a bad download. Try delete that file and re-download again.
[Nexus One Android Development] bunnahabhain:
yeah, i did that allready several times but no luck - same error message :(

In fact the phone loses the signal completely from time to time. And when i call somebody then i couldn't end the call anymore and i have to reboot :)

is that also a wonk :D ?
[Nexus One Android Development] makelegs:
That could actually be a WANK!
[Nexus One Android Development] TheMasterBaron:
Means the service was killed by the system because it wanted to free memory. The log was very helpful! Thanks!

OP updated with 1.4. Service now runs in the foreground by putting a notification in the notification bar.
[Nexus One Android Development] daveid:
Is there no way to run it as a service in the foreground, but get it out of the notification bar? I just don't like the clutter...
[Nexus One Android Development] TheMasterBaron:
I wish there was, I looked around for an alternative, but didn't find one. I too would have preferred not to have the extra notification,.

The wonk is getting close to being fixed, we just need to put up with it for a short time
[Nexus One Android Development] baseballfanz:
Dewonkficator is still the KING.:)
[Nexus One Android Development] markhm1978:
Right on Brotha! :D
[Nexus One Android Development] deekdeek:
I just installed this as i have been hit with the wonk on CM7 rc2

i hope it works!
[Nexus One Android Development] lazie0402:
Does prevent the phone from ever going to sleep?
[Nexus One Android Development] Qunna:
I cannot confirm if it's works (maybe, but difficult to test), but the app really drains my battery.
[Nexus One Android Development] Rod3:
What makes you think it is draining your battery? Is it just a gut feel / observation? According to the battery stats, Dewonkificator has never used any of my battery.
[Nexus One Android Development] Qunna:
I lost 10 percent in about 2 hours. I did nothing with the phone and normally the consumption is about 1-2 percent per hour. Maybe the Dewonkificator prevent the sleeping functionality of the phone?!? But if I remember correctly, I had no draining battery problems with previous version of the Dewonkificator.

I will give the program another chance in the next around.
[Nexus One Android Development] baseballfanz:
Been running dewonkficator since day one. Phone sleep just fine
[Nexus One Android Development] il Duce:
on hero cdma

So I installed this app, worked great for calls, but I think the phone dewonk somehow wonked my music? When listening to music (on cm7 synced 3/23 with stock music) the playback would blip off for a second, about every minute. I figured since the app is supposed to follow that timeframe with the mic restart, maybe that was the culprit. Uninstalled :( and now my music is fine :) Wish there was a dewonker for this dewonker, lol.
[Nexus One Android Development] TheMasterBaron:
I don't get skips. Are you using setCPU profiles to lower the CPU speed when the screen is off? Could be you're limiting it too much for music and dewonking to occur? My settings are 245/422 using ondemand.
[Nexus One Android Development] il Duce:
176/729 ondemand (cmparts). Music actually plays fine, it just stops for a second and continues playing. To be clear, I don't even know if it's your app, but it's the only thing I could figure that made sense, and uninstall seems to have fixed it, who knows. I can't imagine 176 is too low, but I'll reinstall and bump to 264, see what happens.
[Nexus One Android Development] pityr:
I finally got the wonk on RC2. Figured I had avoided it as I had no issues on RC1. Tried IR's latest kernel and it actually made it worse. Loaded dewonkificator and haven't had an issue since :) Thank you for this app.

BTW, Music app works fine while this app is installed. Just went for a run today and it played as it always has.
[Nexus One Android Development] RogerPodacter:
I still have not experienced the wonk, but only been on cyan 7 for a few days with minor calls. I'm not even sure what to look for, but I'll get hit soon enough.
[Nexus One Android Development] il Duce:
It must either be the hero, or something specific to my setup/build. I tried ondemand 264 and 352 min, then tried interactive 264 and 265 min, still got the blip on my music. Totally weird, anyway thanks for the app, I'll try it every nightly to see if that changes.
[Nexus One Android Development] xzr3b0rnzx:
anybody have a link for v1.3?
[Nexus One Android Development] baseballfanz:
V1.3

http://db.tt/lFXG8Fm
[Nexus One Android Development] xzr3b0rnzx:
Thanks dude. Didn't like the notification icon on 1.4. ver 1.3 wasn't giving me problems before
[Nexus One Android Development] Qunna:
This time the battery consumption was okay, but I still got a 2 seconds delay on Desire with CM7 nightly build.
[Nexus One Android Development] tvhoesel:
CM7-RC3

Hi all,

CM&-RC3 is out now. Does is still need to be Dewonkified???

ATM i don't experience any problems with the new RC3.
[Nexus One Android Development] temasek:
Its simple.

Try RC3 w/o wonky app. If wonks then use wonky app. As of latest CM7 nightly / RC3, its already very much less wonky. For one I don't have any wonks for sometime already.
[Nexus One Android Development] RogerPodacter:
i still have not experienced the wonk, i've been uisng #31 for 3 or 4 days now, minor calls though. i'm sure i'll see it eventually. but its strange some people dont see it, some people do. just try and see i guess.

to answer though, no i dont think they found a fix yet officially.
[Nexus One Android Development] chalisto:
Wonk is still there in RC3. I am using dewonk app and wonk is not gone. any ideas? is dewonkificator 1.4 compatible to rc3?
[Nexus One Android Development] cb474:
Yeah, I get some wonk with dewonkificator as well. Occasionally people answer and can't hear me at all. And when I answer there's always a couple second pause before people can hear me.
[Nexus One Android Development] RogerPodacter:
i get the 2 second delay when answering as well. since i havent yet seen what the wonk is, what exactly happens? does the call just suddenly end and hang up right in the middle of a call? or does the phone reboot during the call?
[Nexus One Android Development] cb474:
I'm not sure what exactly the symptoms of the wonk are. I think some people get black screens for a moment, when they launch the phone app. And I think the caller not hearing you is also often part of the wonk. But I'm not sure if it's always the same or what all the different symptoms are.
[Nexus One Android Development] BrotherG:
This works perfectly on RC4. Great job. This should really include on the builds until the issue is completely resolved.
[Nexus One Android Development] relol:
Totally agree with you, this is a MUST!! :D
[Nexus One Android Development] Chosen_on184:
RC4 with this app installed and i get some massive wonk. ( Yea that's what she said too )

More to the point of the phone locks up, meaning trackball or power button won't wake phone up for like 2 minutes

After that time phone will be half awake .. meaning trackball will get you to the lockscreen however you still cannot unlock phone for like another 3 minutes

After 3 minutes of leaving the phone unattended it will start to unlock like normal

Issue is though when all this is happening when you look on the status bar wonk app is not running. Not sure if the system kills the app or something however it is not displayed in the status bar as running .

Once phone starts working like normal it starts back up automatically

Weird .. Makes the phone unusable

Still using stock kernel ..Gonna try flashing a different one but it seems like no dev can pinpoint the source