Fixed
Status Update
Comments
sk...@gmail.com <sk...@gmail.com> #2
[Comment deleted]
to...@gmail.com <to...@gmail.com> #4
Same problem on htc evo
en...@google.com <en...@google.com> #5
Sample problem/bug on Samsung Captivate (Galaxy S) running 2.2. Probably pretty annoying to my co-workers...
en...@google.com <en...@google.com> #6
Same problem om Samsung Galaxy S II
an...@gmail.com <an...@gmail.com> #8
Same here, pretty annoying. Using a Samsung Galaxy S running 2.2.1
bd...@google.com <bd...@google.com> #9
Also same here on Desire Z, is it really that difficult to fix this ?
[Deleted User] <[Deleted User]> #10
Same issue on Incredible 2...I like to use my headphones for privacy. If I wanted to annoy those around me I would play my music through the speakers. But I'm sure my notifications are annoying those around me just fine. PLEASE fix
co...@androidgecko.com <co...@androidgecko.com> #11
same problem on xoom wifi (honeycomb 3.0) and it happens not only on wired headphones but also bluetooth headphones. i'd really love to mute the speakers when i use the headphones to listen to music and still be able to be notified and NOT disturbing others around me in the library. Please, at least make it an option ?
to...@gmail.com <to...@gmail.com> #12
ditto - Droid Charge.
As some help... looking at forums online made it look like it was past a Droid problem and that all Verizon CDMA phones have this issue and it may not be possible to fix it (although you're Google, I've got my confidence in you!).
With a little more research, it looks like that's not true because iPhones (possible AT&T? but don't think so) can elegantly play the ringtones however the user wishes (like the majority of posts are requesting)
On the contrary... many people said they had it playing through the headphones AND the speaker, which does not happen for me (although I've only tried on vibrate... but still it would be nice for the notification/ringtone to be played through the headset even with the phone on vibrate)
As some help... looking at forums online made it look like it was past a Droid problem and that all Verizon CDMA phones have this issue and it may not be possible to fix it (although you're Google, I've got my confidence in you!).
With a little more research, it looks like that's not true because iPhones (possible AT&T? but don't think so) can elegantly play the ringtones however the user wishes (like the majority of posts are requesting)
On the contrary... many people said they had it playing through the headphones AND the speaker, which does not happen for me (although I've only tried on vibrate... but still it would be nice for the notification/ringtone to be played through the headset even with the phone on vibrate)
to...@gmail.com <to...@gmail.com> #13
Same problem. please fix.
ks...@google.com <ks...@google.com> #14
same problem. not happy with my choice. you better fix it!
jv...@google.com <jv...@google.com> #15
Not only that, but the minimum volume is so loud, I can't use it in my office. So, I'm screwed. Vibrate for notifications doesn't work either. So, I either have to have the notifications very loud for everyone to hear, or none at all. this sucks!
to...@gmail.com <to...@gmail.com> #16
Also motorola xoom.
jv...@google.com <jv...@google.com> #17
Same on Xperia Mini Pro, 2.3
Very annoying bug indeed!!
Very annoying bug indeed!!
to...@gmail.com <to...@gmail.com> #18
Same issue on my HTC Thunderbolt running Android 2.3.4
Description
If I debugging code with multiple return statements, eclipse jump to the last one return 'statement' also when another should be used.
Here is simple example:
public int test() {
int row = 1;
if (row >= 0) {
int count = 10;
if (count > 0) {
return count;
} else {
return 0;
}
} else {
return -1;
}
}
When you will debug this code, you will se that Eclipse jump to the "return -1" after evaluating "if (count > 0) {", but count > 0 is true and next line should be used. Method return right value, problem is only in debugger.
Here is more complex video example:
Original thread:
(where Xavier Ducrohet suggest to write bug to the dalvik component)