search

Artemych / speakerproximity

Automatically exported from code.google.com/p/speakerproximity
0 stars 0 forks source link

force close after unanswered call #17

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.receive a phone call
2.do not answer
3.get speaker proximity needs to be closed (long-short-short vibration)

What is the expected output? What do you see instead?
Nothing

What version of the product are you using? On what ROM?
latest Google code download on Samsung Galaxy S jp6 ultk kernel

Please provide any additional information below.

Attach a logcat output if possible.

Original issue reported on code.google.com by g.ste...@gmail.com on 28 Oct 2010 at 9:41

GoogleCodeExporter commented 9 years ago 
Sorry, Version is 0.3.3 beta

Original comment by g.ste...@gmail.com on 28 Oct 2010 at 9:43

GoogleCodeExporter commented 9 years ago 
That sounds very strange... could you attach a logcat of the process as I'm 
unable to replicate that behaviour on my phones (I don't own a Galaxy).

I looked trough the code and if you don't pick up it should not get into case 
TelephonyManager.CALL_STATE_OFFHOOK that starts the functionality of 
SpeakerProximity but it could be possible that it gets into case 
TelephonyManager.CALL_STATE_IDLE and there I unregister a listener where I dont 
check for null reference before...
app.getSensorManager().unregisterListener(app.getProximityListener());

I have to try a few things on it but with a logcat from your device I should 
clearly see where the problem is.

Original comment by michel.racic on 28 Oct 2010 at 9:58

GoogleCodeExporter commented 9 years ago 
Hmm, will try to get a logcat this weekend...

Original comment by g.ste...@gmail.com on 5 Nov 2010 at 10:32

GoogleCodeExporter commented 9 years ago 
managed to get a logcat today, but didnt see anything special in it. however, i 
realized that prox sensor is still active and switching off the display of my 
Galaxy S after a missed call, only way arround this is a reboot

Original comment by g.ste...@gmail.com on 8 Nov 2010 at 8:13

Attachments:

GoogleCodeExporter commented 9 years ago 
btw, did do this logcat with OS-Monitor, and a tag filter "SpeakerProximity" 
hope thats ok...

Original comment by g.ste...@gmail.com on 8 Nov 2010 at 8:17