search

teze / speakerproximity

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

Intermittent on Droid Incredible #18

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
HTC Droid Incredible, 2.2

Michel, this is a great add-on for me personally. Just by pulling the phone 
away from my face, it automatically turns on the speakerphone, that's just 
awesome.  However, I have this issue that the proximity sensor STAYS ACTIVE 
even after the call is ended. In other words, even after the call is hung up, 
the screen still goes out when the phone detects a change.

Original issue reported on code.google.com by qt8...@gmail.com on 29 Oct 2010 at 8:23

GoogleCodeExporter commented 8 years ago 
Hi
Could you attach a logcat for me?

I experienced that if the phone is low on memory, sometimes the call ended 
broadcast won't be received...

Original comment by michel.racic on 1 Nov 2010 at 11:07

GoogleCodeExporter commented 8 years ago 
How far back does the log retain?  I just looked at it and it only has the 
notes of the most recent call.  If that's the case, then I would have to send 
it to you when the problem occurs.  It doesn't do it all the time; it seems 
like it would do it after the 4th or 5th call, I haven't been able to see the 
pattern.

Original comment by qt8...@gmail.com on 1 Nov 2010 at 12:55

GoogleCodeExporter commented 8 years ago 
The log gets cleared after every reboot.
Best is if it happens again, create a log with aLogcat (from the market) or 
directly with adb just after it happen and send it to me.

My guess is that exactly at the time of this call the memory was filled up and 
Dalvik ended the SpeakerProximity Service and before it could get restarted the 
broadcast has been sent... I have to do some more analisys to see how to 
overcome this...
I had this behaviour a couple times but after I uninstalled some apps that I 
havent used for a long time and freed some memory I didn't had it again.

My biggest problem with this is that I can't just easily replicate the bug but 
I will try to solve it one way or the other ;-)

Original comment by michel.racic on 1 Nov 2010 at 1:27

GoogleCodeExporter commented 8 years ago 
Thanks for responding so quickly.  I will see if I can come up with a logical 
pattern.

Original comment by qt8...@gmail.com on 1 Nov 2010 at 2:54