Develop Bugs

is something wrong with my flashlight???

I just notice that one of the less is not working at all.!!!! I use the flashlight a few times, but no more than 30 seconds each time. The last kernel that I was using is the nertachy 4.1.9
I was using stock froyo btw. I install cm6 again just to se if thatcorrect the problem, but I have the same result. Any suggestions? Thanks

I think you might have a led out. I think i remember seeing on the teardown of the phone that they are wired together. Hence no way to run only one.
Did you try taking a picture and see if both are working?

yes
Yes I did take pictures to test it. And only one led flash. The problem is that I don't have endurance.!!! I only have with the phone like 3 months. Any ideas????

rectangularspace said:
Yes I did take pictures to test it. And only one led flash. The problem is that I don't have endurance.!!! I only have with the phone like 3 months. Any ideas????
Click to expand...
Click to collapse
You don't have endurance? I'm sorry for your girlfriend.
Maybe you should have bought penis insurance.

Saturn2K said:
You don't have endurance? I'm sorry for your girlfriend.
Maybe you should have bought penis insurance.
Click to expand...
Click to collapse
Haha post of the day right here!!

Rooted Kernels and Loss of Service

We're trying to determine the "root" (pun intended) of the problem so if you wanna come in here and start a fight go find a local bar to do so. We need to try and locate the source of the problem so either post something useful or walk away.
There seems to be some confusion and I dont know if its being ignored or what but theres an issue with these kernels that needs to be looked into further before new ones continue to be released.
Theres an obvious problem for a good amount of people and everytime I look I see comments that there isnt a problem. So heres everything I could quickly find regarding it.
Now Im not trying to be a **** about this but I dont get how the issue is unheard of when its one of the biggest topics in this section. And so we're clear, this is happening in ALL kernels. Unfortunately its been more profound in Zedos because it seems more people went with his method.
All Im asking is before more and more kernels are released that someone at least acknowledge the problem and see if it can be addressed before more and more people root and start complaining because they were told there was no LO.S. bug
zedomax said:
data drop? dunno about that, this shizzle will not drop. It's ZEDOMAX!
Click to expand...
Click to collapse
zedomax said:
jump and we will find out. no they should be worked out. there was no data loss kinks in da first place, where did u get that?
Click to expand...
Click to collapse
________________________________________________________________________________________________________
joetemp75 said:
Man I was fine then I flashed v5 and got the no signal issue
Click to expand...
Click to collapse
SupahDave said:
Everything seemed to be fine last night but today I've had 4 separate times now where my phone has lost signal all together and needed to be rebooted to get phone/data back. When this has happened I tried going into About-->Status to see if I could see anything odd and I kept getting a FC of com.android.phone
Click to expand...
Click to collapse
jimbobtexas said:
I did. No love. I'm without a signal, period.
Click to expand...
Click to collapse
MILH0U5E said:
Got the no signal issue here too. I put it in airplane mode overnight and upon waking this morning the no signal circle was there. I had to do a reboot to get 3g and cell signal back.
Looking forward to seeing this process develop.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
wbyrd said:
Yeah this just happened to me too, everything was fine this morning then I played a game of solitaire and after going back to my home screen I saw the circle. Rebooted phone and everything came back on. It's possible that the circle was there before I played the game of solitaire but I didn't notice until right after I quit playing.
Hopefully it gets straightened out soon. At least rebooting fixes the problem, I can handle rebooting for a little while if needed.
Click to expand...
Click to collapse
plmiller0905 said:
I can't really deal with the issue of having no service. My daughter has a heart issue and can't afford to miss a call. It's not like I walk around all day literally looking at my phone's screen seeing if I have service or not.
I did reboot...so like your's my service is back up.
But I definitely hope this gets fixed soon. I'd rather have root with broken heptic feedback than the inability to receive calls.
But I'm sure the Op the get it fixed...
Click to expand...
Click to collapse
volwrath said:
I've had a dead call issue and also tday my radios were just dead and there was a circle in the middle of the notification barr. A reboot fixed the issues each time, but I think it might be a problem. I thing newer kernels will also fix said issues. Still very satisfied
Click to expand...
Click to collapse
JLine05 said:
I am having the issue of the phone (voice) and sms not working. Strange because everything else is working fine. Does anyone have any ideas? Thanks.
Click to expand...
Click to collapse
mcflargen said:
Still seems to have the data drop issue. Popped it on the second u dropped it, was great till a min ago. least a "restart" fixes it.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
joetemp75 said:
Man I just lost data again. This sucks
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
kindaskimpy said:
I'm giving this one a try because with the zedomax kernel I kept losing 3G and CDMA calling and not even noticing it unless someone told me they'd been trying to reach me for hours. A quick reboot would solve the issue but then it would happen again.
I'll report back and let you guys know if this one is giving me the same issue.
Click to expand...
Click to collapse
bbedward said:
I did this one because losing service on the other one, haven't lost it yet but its only been a couple hours
Sent from my sprint galaxy s2
Click to expand...
Click to collapse
fordmanck said:
I tried both, i'm back on this one. I lost service with zedos twice and haven't on this at all.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse

Telling you right now someone is going to come in here and go "this belongs in General" then a mod will move your thread and deduct 5 points from something, not sure...but just a heads up

I also see a lot of people having issues, but I'm now on day 2 of flashing Zedo V1 and have yet to experience any of these issues. Not sure what I did different, but everything just works... The only thing I did was after rooting was getting my MSL from Sprint and erased the proxy servers in the ##3282 menu.
EDIT: Ok, I just lost service 1 1/2 day after rooting... Bug finally hit me..

I dont mind it being moved and I have no clue what the deduction in "points" does but I'll deal with it.
Now Im getting much better battery but I know people are still losing service on the new OC kernel. My roommate happens to be on e the unlucky ones.

Man...thanks for posting this. Hopefully the mod doesn't close this thread. This definitely is a concern and a serious matter. I don't care if these kernels are, "use at your own risk" these kernels should've been listed as betas, and/or the bugs should've been listed and further testing should have been. If those steps were taken, I bet a lot of people would've held back from flashing them. I know I would have.
Shabby posted this earlier in the other thread (post 160):
http://forum.xda-developers.com/showthread.php?t=1267762&page=16
One thing that got to me was this morning I woke up, hoping to see a stock kernel and/or a way to return to stock. And instead, I see a new overclockable kernel. To me that's just not right. I think that you have to prioritize. That's like putting out a rom that has all data broke. Then instead of fixing it, you put out another rom...while disregarding the issues with the first rom. At least acknowledge the issue and let everyone know it's been worked on....don't just blow it off.
I know some of the devs over in the Evo forums was good about this....if something went haywire with one of their roms or mods...they were all on top of it to get the issue fixed and they also communicated with posting updates on the matter.
Like I said, hopefully the mods don't close this.
I'm definately gonna follow this thread...thanks Wingzfan

i rooted yesterday using zedomax method, did the OC kernel last night.. havent had any issues so far ..

plmiller0905 said:
Shabby posted this earlier in the other thread:
http://forum.xda-developers.com/showthread.php?t=1267762&page=16
post 160
I'm definately gonna follow this thread...thanks Wingzfan
Click to expand...
Click to collapse
Bubby does have the stock kernel pulled. I was testing it till 1:30 in the morning but he's gotta recompile it. It was bootlooping so today thats his first order of business.
As for the kernels, I flashed it by choice. I dont blame the devs for ANYTHING, Im just saying acknowledge theres a bug and lets see how to resolve it.

I've been reading through the rooted kernel threads as well prior to jumping on the root wagon and have seen several people mention that they are not rooted and have experienced the loss of service so it seems that the issue may not be exclusive to the rooted kernels...possibly a Samsung bug?

Very possible which is why im hoping we can get an idea of how man people are rooted vs non rooted having it. Now the only thing is I cant find any complaints online about nonrooted phones doing it except a few here and youd think it'd be widely discussed
Sent from a Galaxy far far away...

OrygunGal said:
I've been reading through the rooted kernel threads as well prior to jumping on the root wagon and have seen several people mention that they are not rooted and have experienced the loss of service so it seems that the issue may not be exclusive to the rooted kernels...possibly a Samsung bug?
Click to expand...
Click to collapse
Yeah...I read those too. However, I never lost any service at home with any android phone I've owned..Nexus S 4g, all Evo's, Epics etc. Then today I wake up and I have no service....maybe it is a samsung bug, but I'd rather return to stock myself to see if the issue was still there.

Stocks on its way i promise. Probly tonight actually. Bubby was really close last night. Once we get that Id be curious to see what happens.
Sent from a Galaxy far far away...

wingzfan said:
Stocks on its way i promise. Probly tonight actually. Bubby was really close last night. Once we get that Id be curious to see what happens.
Sent from a Galaxy far far away...
Click to expand...
Click to collapse
Sounds good...can't wait
Sent from my SPH-D710 using Tapatalk

This is an issue that started with mine also yesterday. But not only did I lose data but gps also. A reboot fixed it but I would like to know whats going on. I just came from the evo 3d and there was an issue that had to do with the prl so I am going to give that a shot with the 11115 prl that fixed the evo. Will post back with the results later today.

On V5, Ive only had the loss of data once in about 12 hours, versus about 3 times on Zedo V1.
I also did http://forum.xda-developers.com/showpost.php?p=17703908&postcount=11 for the hell of it to see if that helped (even though I got it at a sprint store)

For the record:
A) People have reported this issue even on the stock kernel. It is not clear where the cause is.
B) For kicks (and because it cannot hurt) I did the whole profile/PRL update thing that someone suggested. Be it luck or real benefit, I have no had the issue since.

wingzfan said:
Very possible which is why im hoping we can get an idea of how man people are rooted vs non rooted having it. Now the only thing is I cant find any complaints online about nonrooted phones doing it except a few here and youd think it'd be widely discussed
Sent from a Galaxy far far away...
Click to expand...
Click to collapse
I would think it would be widely discussed as well so that seems odd. I'm waiting to see what evolves or at least for stock kernel (an undo) before flashing a rooted one. I don't have TEP.

It's still a bit early for the issue to be too widely discussed.

dmarden said:
For the record:
A) People have reported this issue even on the stock kernel. It is not clear where the cause is.
B) For kicks (and because it cannot hurt) I did the whole profile/PRL update thing that someone suggested. Be it luck or real benefit, I have no had the issue since.
Click to expand...
Click to collapse
Nice. I was told by a helpful Sprint cust. serv. rep. a while back that you should update your PRL & Profile when you go into a new area (tavel, move, or even long commute to work) regardless of which phone you have. I would think unboxing your phone would qualify as well. It sure couldn't hurt.
---------- Post added at 06:59 AM ---------- Previous post was at 06:53 AM ----------
dmarden said:
It's still a bit early for the issue to be too widely discussed.
Click to expand...
Click to collapse
Good point. Many people would not likely research on the web/forums, instead they'd likely address the issue directly with Sprint.

plmiller0905 said:
Yeah...I read those too. However, I never lost any service at home with any android phone I've owned..Nexus S 4g, all Evo's, Epics etc. Then today I wake up and I have no service....maybe it is a samsung bug, but I'd rather return to stock myself to see if the issue was still there.
Click to expand...
Click to collapse
Ever owned a Samsung phone before?
This is my 3rd one and I swore after the last one Id never buy a Samsung phone again but I got sucked back in. Samsung is notorious for shipping phones with all kinds of bugs that should be considered showstoppers then pushing out fixes months later.
It would not surprise me at all if that was the case here. I am one of the ones having this issue and I am not rooted. Ive lost data several times after hanging up a call. The data never restores and I have to toggle 3G to get it come back.
I dont think this is a kernel issue. I think its something to do with the rest of the OS, either that or the kernel is a different problem thats just acting the same way.

Ok thats what i was hoping to find is nonrooted and rooted people who are having the issue. Now on my moment this issue was huge so i went to htc and maybe thats the case again. Maybe sammy dropped the ball again. Question is what can be done about it.
Sent from a Galaxy far far away...

[Q] Screen is unresponsive with finger

I was running the tweeked rom on my Note 2 and was loving it, was running great for a few days...
Today the screen froze when I went to unlock and check a missed call. I am unable to get any response from my finger, nothing... The S pen does work though.
T-mobile tech knew nothing about how to fix it. I tried a different rom and still the same.
Any suggestions? Calibration? Anything? Thanks so much.

As it exists across roms, it regrettably sounds like a hardware issue. Have you tried flashing a stock odin? Likely won't help but it might be worth a shot.

dwitherell said:
As it exists across roms, it regrettably sounds like a hardware issue. Have you tried flashing a stock odin? Likely won't help but it might be worth a shot.
Click to expand...
Click to collapse
Thanks for the reply. I am afraid that is a pretty big problem too, related to hardware. 10 minutes before the finger freeze I was just realizing how much I loved the phone with the Tweaked Rom and totally set-up.
Anyways, it's going back to T-mobile. I used Odin to flash to stock and used Triangle Way to reset the flasher... Now I am scared to root it and run a rom on the new one, but I know it was just a freak incident...
Just sucks, I hate getting a refurb replacement... I don't know what dirty, grungy, smelly pocket it's been in for a couple months, uh...

I had an issue on my first note 2 where the top right and left of the screen couldnt register the s pen, had to send the phone back. I flashed jedi as soon as i got the second one and been happy ever since.
Moral of the story, DONT WORRY AND FLASH AWAY. ur right, it was a freak accident and it wont happen again.
Sent from my SGH-T889 using XDA Premium HD app

moabizzi said:
I had an issue on my first note 2 where the top right and left of the screen couldnt register the s pen, had to send the phone back. I flashed jedi as soon as i got the second one and been happy ever since.
Moral of the story, DONT WORRY AND FLASH AWAY. ur right, it was a freak accident and it wont happen again.
Sent from my SGH-T889 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, appreciate the help... I will definitely flash away and have fun with the new phone.

Looks like my phone broke

Well my phone won't respond to my touch at all. Everything does work, I thought it was the rom but I went into recovery but it just won't do anything when I touch it. The volume buttons work. This is so odd, never had this problem with any of my old phones. It could be the digiziter... As of now I'm going to try a few things, pull the battery for a few minutes, factory reset, install another rom. Oh yeah I'm running cm10.1 yesterday's build I belief. So guys any ideas? Tips? Suggestions? Also how could this happen? I didn't drop it last night. It was working fine expect it had to signal because I was in a basement.
Wow the oddest thing just happened. I took the battery off right, well I put it back in and turned the phone in. I unlock the phone which got me excited obviously, but shortly after it stopped working. This had to be a rom issue or damaged digiziter....
What the hell...I haven't installed or factory reset because the phone was charging. Didn't want to mess with low battery. Well I plugged it into my computer. And guess what? It effing worked! Now the touchscreen works. This is making me scratch my head. What the hell happened? How did connecting it into the computer fixed the computer? You guys have any ideas?

Phone is slowly dying, not a rom issue I don't think. Change the rom just in case to find out. Also Google the issue, it shouldn't be just this phone kinda bug.
Sent from my SGH-T999 using xda premium

I'd Odin back to Stock, root66. This way you can completely eliminate a rom, mod, kernel, etc. Run purely stock for a day or two at least and you will have a better idea as to the cause.
Sent from my SGH-T999L using xda premium

mt3g said:
Phone is slowly dying, not a rom issue I don't think. Change the rom just in case to find out. Also Google the issue, it shouldn't be just this phone kinda bug.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It would make sense. I did, there's several people with the same issue, same phone.
DocHoliday77 said:
I'd Odin back to Stock, root66. This way you can completely eliminate a rom, mod, kernel, etc. Run purely stock for a day or two at least and you will have a better idea as to the cause.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
I'll do that, before cm10 I was running miui which was buggy as hell. That rom probably left something behind. I'll Odin, thanks you two.

iwillkillyou said:
It would make sense. I did, there's several people with the same issue, same phone.
I'll do that, before cm10 I was running miui which was buggy as hell. That rom probably left something behind. I'll Odin, thanks you two.
Click to expand...
Click to collapse
Report back this is interesting, I haven't seen it on this forum yet.
Sent from my SGH-T999 using xda premium

This is quite interesting indeed. A similar ordeal kept happening when I was still on stock Touchwiz Rom. It's what forced me to look for alternative roms. I haven't had the unresponsive touchscreen ever since, so I'm interested in finding out if switching roms will solve your problem as well.
[ Sent from my WHAT!? ]

I've had a problem like this with my last two phones, both being Samsung. My phone prior to the sgs3 was the nexus s. About a year in it started randomly opening apps and pulling open the power menu. I thought it might just be the rom or battery went back to stock and got a new battery and it still continued.. So i finally upgraded to the sgs3. I just started having the same problem on my gs3. It would open the power menu and it would randomly open apps and type on the keyboard. I reverted to stock and it seemed to fix the problem on this phone. It's weird though, it's happened on both of my latest devices.

Thats just weird to me. This is the first ive ever heard of this happening on our GS3's. Hopefully its all just corrupted software or something related and a clean Odin flash will fix it.

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

kennyglass123 said:
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
In wasn't asking a question, I was informing the members of our forum about this problem.
DocHoliday77 said:
Thats just weird to me. This is the first ive ever heard of this happening on our GS3's. Hopefully its all just corrupted software or something related and a clean Odin flash will fix it.
Click to expand...
Click to collapse
Andrew421 said:
I've had a problem like this with my last two phones, both being Samsung. My phone prior to the sgs3 was the nexus s. About a year in it started randomly opening apps and pulling open the power menu. I thought it might just be the rom or battery went back to stock and got a new battery and it still continued.. So i finally upgraded to the sgs3. I just started having the same problem on my gs3. It would open the power menu and it would randomly open apps and type on the keyboard. I reverted to stock and it seemed to fix the problem on this phone. It's weird though, it's happened on both of my latest devices.
Click to expand...
Click to collapse
KunoMochi said:
This is quite interesting indeed. A similar ordeal kept happening when I was still on stock Touchwiz Rom. It's what forced me to look for alternative roms. I haven't had the unresponsive touchscreen ever since, so I'm interested in finding out if switching roms will solve your problem as well.
[ Sent from my WHAT!? ]
Click to expand...
Click to collapse
I did return to stock, since then the ploblem hasn't occurred again.

iwillkillyou said:
In wasn't asking a question, I was informing the members of our forum about this problem.
Click to expand...
Click to collapse
I refer you yo the end of your first paragraph. You posted this not yo inform us of your problem, but to ask us for help with it. Even if you managed to avoid any actual "questions", if its even implying that you are asking or requesting, then it belongs in Q&A.
I did return to stock, since then the ploblem hasn't occurred again.
Click to expand...
Click to collapse
So problem solved then? Good deal! Glad to hear you got it worked out!
Sent from my SGH-T999 using xda premium
---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------
Sounds like something got corrupted. I'd make a nandroid now, so you have a known good backup. Just in case.
Sent from my SGH-T999 using xda premium

iwillkillyou said:
In wasn't asking a question, I was informing the members of our forum about this problem.
.
Click to expand...
Click to collapse
You have 3 questions at the end of your post which resulted in people offering advice.

[Q] Proximity sensor ruining my life

Hello everyone! I have been having literally the worst two weeks trying to get the proximity sensor on my Note II to behave consistently. The sensor does not provide any feedback to the system. Using Android Sensor Box just returns the "No change detected yet" message. I am seriously at wit's end with this. I tried starting over and flashing stock using Odin but it doesn't seem like the kernel is at all affected through that and does not provide reliable results. Sometimes I can flash a stock kernel and the sensor works, but as soon as I either flash a different ROM or flash a different kernel, I am not able to use the sensor. I do not believe it to be the hardware because I have tried two different assemblies with the sensor on it to no avail. Is there anyone that could help? (And yes, I have searched high and low for any kind of guidance on this) I really like this phone, but this is definitely a deal breaker.

Firstly what are you trying to do with the proximity sensor, that is not working for you? Auto brightness, or one of the samsung touchless features?

Thank you for replying. What queued me into the fact that it wasn't working was that my screen does not turn off when I put the phone up to my face during a call. But it doesn't work for any purpose. If it's of any help, the light sensor also does not work, so I'm not able to use things like auto-brightness either.

adrianjayy said:
Thank you for replying. What queued me into the fact that it wasn't working was that my screen does not turn off when I put the phone up to my face during a call. But it doesn't work for any purpose. If it's of any help, the light sensor also does not work, so I'm not able to use things like auto-brightness either.
Click to expand...
Click to collapse
What type of Rom/kernels are you flashing that makes it stop working? AOSP or touchwiz?
Have you tried several, all with the same result?
You're saying that it does work when you run stock as well?

crixley said:
What type of Rom/kernels are you flashing that makes it stop working? AOSP or touchwiz?
Have you tried several, all with the same result?
You're saying that it does work when you run stock as well?
Click to expand...
Click to collapse
Both, I've tried using Perseus, Neak, SOAPKernel and of course stock. The ROM does not matter either, I really intend to use PAC-man RC1 Milestone, but right now I am using the Stock ROM and it is still not working.

adrianjayy said:
Both, I've tried using Perseus, Neak, SOAPKernel and of course stock. The ROM does not matter either, I really intend to use PAC-man RC1 Milestone, but right now I am using the Stock ROM and it is still not working.
Click to expand...
Click to collapse
Sounds like failing hardware man :/
Is your flash counter tripped? Are you still within warranty?

crixley said:
Sounds like failing hardware man :/
Is your flash counter tripped? Are you still within warranty?
Click to expand...
Click to collapse
I have definitely flipped the flash counter, but there's always Triangle Away right? I'm actually totally screwed because I busted my screen a while back and replaced it and the one I got was for an International phone. I guess I could try a third sensor? This is bad news

adrianjayy said:
I have definitely flipped the flash counter, but there's always Triangle Away right? I'm actually totally screwed because I busted my screen a while back and replaced it and the one I got was for an International phone. I guess I could try a third sensor? This is bad news
Click to expand...
Click to collapse
You may have damaged it during the screen swap, or it could maybe just be loose or shorting, which is why occasionally it will work.

crixley said:
You may have damaged it during the screen swap, or it could maybe just be loose or shorting, which is why occasionally it will work.
Click to expand...
Click to collapse
Yeah, I actually was worried that I had damaged it when I opened it in preparation for the screen swap, but I couldn't remember well enough when it exactly stopped working. Thank you much, I should have a new one in by the weekend and then we will know.

adrianjayy said:
Yeah, I actually was worried that I had damaged it when I opened it in preparation for the screen swap, but I couldn't remember well enough when it exactly stopped working. Thank you much, I should have a new one in by the weekend and then we will know.
Click to expand...
Click to collapse
No problem man! I hope it works for you.. Maybe before buying a new one check to see if it's just a loose connection (depending on how electrically savvy you are).

crixley said:
No problem man! I hope it works for you.. Maybe before buying a new one check to see if it's just a loose connection (depending on how electrically savvy you are).
Click to expand...
Click to collapse
Okay so my mind is officially blown. Replaced the sensor with a new one and still not getting any feedback from either sensor. I really still do think it's something about the kernel, but because I have limited knowledge of these things, I am probably not the best person to diagnose the issue

The issue is definitely that the sensor just does not turn on, which is odd because the camera works. I found a thread with some proximity sensor calibration stuff but it is a bit over my head.

adrianjayy said:
Okay so my mind is officially blown. Replaced the sensor with a new one and still not getting any feedback from either sensor. I really still do think it's something about the kernel, but because I have limited knowledge of these things, I am probably not the best person to diagnose the issue
Click to expand...
Click to collapse
I find that strange though if you have tried several, all with the same issue

i am having the same issue, except tha also notification led will not work on stock roms but it will work on cm roms.

So, just a conclusion on this issue. I decided to just transplant the sticker from the original screen I had and exchange this phone using its warranty. When I was preparing the phone to return to the device support center, when I flashed back to stock and had already Triangle Away'd, the sensor did turn on and was recognized in the *#0*# diagnostic screen, but it still did not turn the screen off during calls and Motions were still not functioning. So, ultimately, no real solution in my case.

:good:
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can which perfume was over and it was only pressing Gas OFF!! :good::good::good: