Open GoogleCodeExporter opened 9 years ago
Bus stop defective -- please replace.
;-) OK, I've had a few sporadic reports of crashes caused by "sensor overload",
but
I've *never* been able to reproduce it. I'll take a look though. (The graph is
supposed to auto-scale, and always does for me.)
Original comment by heads...@gmail.com
on 17 Feb 2010 at 4:46
Same happens for me on my HTC Tattoo with Tricorder 5.0.
Even though I killed the app with an app-killer, the scanning sound was still
playing!
Had to restart the device to get rid of the sound.
It seems that I can't reproduce it BUT I think that it may be worth looking
into if
more people have experienced this problem.
Original comment by Musenkishi@gmail.com
on 2 Mar 2010 at 10:17
I just installed this app on an HTC Incredible, and had same experience as
Musenkishi
did.
Original comment by joesh...@gmail.com
on 3 Jun 2010 at 1:22
Same just happened to me on a HTC Desire. I had to reboot the phone to kill the
scan
sound.
Original comment by zin...@gmail.com
on 7 Jun 2010 at 11:27
Ran into this bug on an HTC Evo. Happened when I got too close to a powerful
magnet while running the magnetic field scan.
Original comment by tmhedb...@gmail.com
on 15 Jun 2010 at 12:15
Experienced the same problem as described above.
You're not able to reproduce it ?
Try putting your device near the emitter of a strong magnetic field/permanent
magnet (e.g. Loudspeaker)
"Works" out on an HTC Desire even with a fridge magnet (one of these which
don't fall of by opening the door ;)
Original comment by dethi...@googlemail.com
on 9 Jul 2010 at 3:18
Same experience with my Eris when I first ran program. I was near a laptop
computer. App crashed but scan sound persisted until I rebooted phone. I
submitted a new issue report before I found this thread. Droid Eris firmware v
2.1.
Original comment by golla...@gmail.com
on 30 Jul 2010 at 5:51
Same happened on HTC hero, had to reboot and all I used was a friends phone.
Original comment by ISAIAHDA...@gmail.com
on 12 Aug 2010 at 4:30
I've got sources of high magnetic field. Two things appear, and I can reproduce
them:
1) When the field is bigger than 1000 µT (1 mT), which is not that high, '+'
is displayed at the place of the value. Why? Is it because of sensors'
limitations, or because of the application?
2) When the field suddenly increases, the application crashes. To make it
crash, this is really easy to do. Take for example a wall phone, or simply an
alarm clock. Move your phone near to the alarm clock (especially the speakers).
-- HTC Desire, Froyo.
Original comment by merciadr...@gmail.com
on 6 Sep 2010 at 7:46
Issue 108 has been merged into this issue.
Original comment by heads...@gmail.com
on 6 Sep 2010 at 2:33
Also had it crash (with persistent scan sound after crash) when bringing a
magnet near the back of the phone.
The Scale didn't auto scale correctly a few times then it crashed.
Android 2.1 Samsung GalaxyS Captiva
Original comment by pgpprote...@gmail.com
on 10 Sep 2010 at 4:12
Issue 82 has been merged into this issue.
Original comment by heads...@gmail.com
on 18 Sep 2010 at 2:33
I was walking by the door to a room which contains a 3.5 Tesla superconducting
NMR magnet yesterday, with tricorder in MAG mode. It crashed. :)
It looks like the absolute magnitude graph is being drawn out of bounds when
the magnetic field exceeds 255 microtesla or something, hence causing the crash.
Original comment by ursseint...@googlemail.com
on 16 Jan 2011 at 11:35
While posting the text below I realized that this is not a problem of the
magnetic flux mode, but probably of automatic rescaling, as it does also happen
in the accelerometer mode as soon as the magnitude starts to get off-scale.
Original post:
My Samsung Galaxy S II reproducibly crashes back to the home screen as soon as
the magnetic field magnitude reaches about 131 (µT?). The scan sound does not
continue. The speed with which the flux approaches ~131 is seemingly irrelevant.
Is there anything I can do to help you with debugging?
Original comment by marius.w...@gmail.com
on 7 Aug 2011 at 3:35
Hi all,
I understand your frustration with this issue, but I have blasted my device
with powerful magnets until I'm scared of harming it, and I can't get the
crash. If someone can get me a log, that would be a huge help.
Thanks!
Original comment by heads...@gmail.com
on 9 Aug 2011 at 9:00
Hi moonblink, thanks for your response, and it's a great app even with this
problem. :)
I tried to get you some logs, and CatLog seems to have done the job alright. A
log is attached in the zip. It seems not to contain sensitive data, but to
throw off bots it is password protected: "moonblink".
Hope it helps, tell me if I can do anything else!
Original comment by marius.w...@gmail.com
on 10 Aug 2011 at 10:47
Attachments:
Thanks!
This is wierd though... the crash is in native code, and since I don't use
native code, that indicates a platform bug. The only clue is that it may be in
the graphics stack (libskia), so it may be something I'm drawing... that
shouldn't cause a crash, but I'll look into it.
Original comment by heads...@gmail.com
on 10 Aug 2011 at 2:32
Good
Original comment by anhtien8...@gmail.com
on 21 Jul 2014 at 8:46
looks like someone posted a new one fixes the crash....
https://onedrive.live.com/redir?resid=F6D1B31852D1483D%21105
some other nice stuff there too
Original comment by jonespet...@gmail.com
on 21 Jul 2014 at 3:56
Original issue reported on code.google.com by
senacharim
on 17 Feb 2010 at 4:41