My Iphone 4 alarm dont work ! EDIT theres a way to fix it

Originally Posted by solemunchies

I wish I could talk crap about your Droid & Iphone heads. I'm running BB
30t6p3b.gif
Click to expand...

I'm running WebOS 
ohwell.gif
 
If you need an alarm because you have to work early on Jan 1, it's not the phone...you fail at life.
 
If you need an alarm because you have to work early on Jan 1, it's not the phone...you fail at life.
 
roll.gif
 @ android fanboys... i rather have my alarm not go off than this:
http://www.engadget.com/2...g-bugs-thatll-get-you-f/




[h4]Android still has horrible text messaging bugs that'll get you fired, busted, or otherwise embarrassed[/h4]
By Chris Ziegler   posted Dec 31st 2010 1:12PM

Pardon us if the headline is a little sensational, but this is one that we've personally experienced -- and it's not pretty. For at least the last couple versions, Android has been plagued with a couple extremelyserious bugs in its text messaging subsystem that can ultimately end up causing you to text the wrong contact -- even contacts that you've never texted before. There appear to be a few failure modes; the one we definitely experience on the Gingerbread-powered Nexus S involves being routed to the wrong thread when you tap it either in the Notifications list or the master thread list in the Messaging application, so if you don't notice, you'll end up firing a message to the wrong person.

More seriously, though, there's also an open issue in Android's bug tracking system -- inexplicably marked "medium" priority -- where sent text messages can appear to be in the correct thread and still end up being sent to another contact altogether. In other words, unless you pull up the Message Details screen after the fact, you might not even know the grievous act you've committed until your boss, significant other, or best friend -- make that former best friend -- texts you back. There seem to have been some attempts on Google's part over the year to fix it; we can't confirm that it still happens in 2.3, but for what it's worth, the issue hasn't been marked resolved in Google Code... and it was opened some six months ago.

This is akin to an alarm clock that occasionally won't go off (we've been there) or a car that randomly won't let you turn the steering wheel -- you simply cannot have a phone that you can't trust to communicate with the right people. It's a deal-breaker. We're pretty shocked that these issues weren't tied up and blasted to all affected phones as an over-the-air patch months ago, but whatever the reason, we'd like to see Google, manufacturers, and carriers drop every other Android update they're working on and make sure this is completely resolved immediately.

Want to see this fixed as much as we do? Scroll to the bottom of the Google Code page and hit "Vote for this issue and get email change notifications."
 
roll.gif
 @ android fanboys... i rather have my alarm not go off than this:
http://www.engadget.com/2...g-bugs-thatll-get-you-f/




[h4]Android still has horrible text messaging bugs that'll get you fired, busted, or otherwise embarrassed[/h4]
By Chris Ziegler   posted Dec 31st 2010 1:12PM

Pardon us if the headline is a little sensational, but this is one that we've personally experienced -- and it's not pretty. For at least the last couple versions, Android has been plagued with a couple extremelyserious bugs in its text messaging subsystem that can ultimately end up causing you to text the wrong contact -- even contacts that you've never texted before. There appear to be a few failure modes; the one we definitely experience on the Gingerbread-powered Nexus S involves being routed to the wrong thread when you tap it either in the Notifications list or the master thread list in the Messaging application, so if you don't notice, you'll end up firing a message to the wrong person.

More seriously, though, there's also an open issue in Android's bug tracking system -- inexplicably marked "medium" priority -- where sent text messages can appear to be in the correct thread and still end up being sent to another contact altogether. In other words, unless you pull up the Message Details screen after the fact, you might not even know the grievous act you've committed until your boss, significant other, or best friend -- make that former best friend -- texts you back. There seem to have been some attempts on Google's part over the year to fix it; we can't confirm that it still happens in 2.3, but for what it's worth, the issue hasn't been marked resolved in Google Code... and it was opened some six months ago.

This is akin to an alarm clock that occasionally won't go off (we've been there) or a car that randomly won't let you turn the steering wheel -- you simply cannot have a phone that you can't trust to communicate with the right people. It's a deal-breaker. We're pretty shocked that these issues weren't tied up and blasted to all affected phones as an over-the-air patch months ago, but whatever the reason, we'd like to see Google, manufacturers, and carriers drop every other Android update they're working on and make sure this is completely resolved immediately.

Want to see this fixed as much as we do? Scroll to the bottom of the Google Code page and hit "Vote for this issue and get email change notifications."
 
Originally Posted by al3x89

roll.gif
 @ android fanboys... i rather have my alarm not go off than this:
http://www.engadget.com/2...g-bugs-thatll-get-you-f/




[h4]Android still has horrible text messaging bugs that'll get you fired, busted, or otherwise embarrassed[/h4]
By Chris Ziegler   posted Dec 31st 2010 1:12PM

Pardon us if the headline is a little sensational, but this is one that we've personally experienced -- and it's not pretty. For at least the last couple versions, Android has been plagued with a couple extremelyserious bugs in its text messaging subsystem that can ultimately end up causing you to text the wrong contact -- even contacts that you've never texted before. There appear to be a few failure modes; the one we definitely experience on the Gingerbread-powered Nexus S involves being routed to the wrong thread when you tap it either in the Notifications list or the master thread list in the Messaging application, so if you don't notice, you'll end up firing a message to the wrong person.

More seriously, though, there's also an open issue in Android's bug tracking system -- inexplicably marked "medium" priority -- where sent text messages can appear to be in the correct thread and still end up being sent to another contact altogether. In other words, unless you pull up the Message Details screen after the fact, you might not even know the grievous act you've committed until your boss, significant other, or best friend -- make that former best friend -- texts you back. There seem to have been some attempts on Google's part over the year to fix it; we can't confirm that it still happens in 2.3, but for what it's worth, the issue hasn't been marked resolved in Google Code... and it was opened some six months ago.

This is akin to an alarm clock that occasionally won't go off (we've been there) or a car that randomly won't let you turn the steering wheel -- you simply cannot have a phone that you can't trust to communicate with the right people. It's a deal-breaker. We're pretty shocked that these issues weren't tied up and blasted to all affected phones as an over-the-air patch months ago, but whatever the reason, we'd like to see Google, manufacturers, and carriers drop every other Android update they're working on and make sure this is completely resolved immediately.

Want to see this fixed as much as we do? Scroll to the bottom of the Google Code page and hit "Vote for this issue and get email change notifications."
Click to expand...

so, you went to engadget. looked up the article, highlighted everything. hit ctrl+c or command + c and came here and hit ctrl + v or command + v just to call somebody else a fanboy? man, your feelings must have really gotten hurt.

the alarm thing also happened to my brother, even after i told him about the bug
30t6p3b.gif
got to work late thx to it.
 
Originally Posted by al3x89

roll.gif
 @ android fanboys... i rather have my alarm not go off than this:
http://www.engadget.com/2...g-bugs-thatll-get-you-f/




[h4]Android still has horrible text messaging bugs that'll get you fired, busted, or otherwise embarrassed[/h4]
By Chris Ziegler   posted Dec 31st 2010 1:12PM

Pardon us if the headline is a little sensational, but this is one that we've personally experienced -- and it's not pretty. For at least the last couple versions, Android has been plagued with a couple extremelyserious bugs in its text messaging subsystem that can ultimately end up causing you to text the wrong contact -- even contacts that you've never texted before. There appear to be a few failure modes; the one we definitely experience on the Gingerbread-powered Nexus S involves being routed to the wrong thread when you tap it either in the Notifications list or the master thread list in the Messaging application, so if you don't notice, you'll end up firing a message to the wrong person.

More seriously, though, there's also an open issue in Android's bug tracking system -- inexplicably marked "medium" priority -- where sent text messages can appear to be in the correct thread and still end up being sent to another contact altogether. In other words, unless you pull up the Message Details screen after the fact, you might not even know the grievous act you've committed until your boss, significant other, or best friend -- make that former best friend -- texts you back. There seem to have been some attempts on Google's part over the year to fix it; we can't confirm that it still happens in 2.3, but for what it's worth, the issue hasn't been marked resolved in Google Code... and it was opened some six months ago.

This is akin to an alarm clock that occasionally won't go off (we've been there) or a car that randomly won't let you turn the steering wheel -- you simply cannot have a phone that you can't trust to communicate with the right people. It's a deal-breaker. We're pretty shocked that these issues weren't tied up and blasted to all affected phones as an over-the-air patch months ago, but whatever the reason, we'd like to see Google, manufacturers, and carriers drop every other Android update they're working on and make sure this is completely resolved immediately.

Want to see this fixed as much as we do? Scroll to the bottom of the Google Code page and hit "Vote for this issue and get email change notifications."
Click to expand...

so, you went to engadget. looked up the article, highlighted everything. hit ctrl+c or command + c and came here and hit ctrl + v or command + v just to call somebody else a fanboy? man, your feelings must have really gotten hurt.

the alarm thing also happened to my brother, even after i told him about the bug
30t6p3b.gif
got to work late thx to it.
 
You must log in or register to reply here.

Similar threads

feeninlikejodeci
Tactics to scare Landlord?
Replies
12
Views
1K
feeninlikejodeci
feeninlikejodeci
us3less
Healing/Recovering from Anxiety and Panic Attacks - by Allowing the Feelings and Thoughts to Happen
Replies
1
Views
1K
Belgium
Belgium
numbah1
Curbing cell phone addiction
2 3
Replies
56
Views
6K
jpzx
jpzx
crumps brother
What’s your move? Ordering on fast food apps
2
Replies
26
Views
2K
wayniac211
wayniac211
dblplay1212
StockX scamming? How is this legal?
2 3
Replies
58
Views
8K
runyc
runyc

Latest News

View All News

The ultimate sneaker enthusiast community.

Site contents may not be incorporated into AI training data or any other derivative works without prior express written consent.

Links to participating merchants may generate referral or affiliate commissions that help support our community. See our policies for details. NikeTalk is NOT affiliated with Nike Inc. in any way, shape, or form. All opinions expressed herein do not necessarily reflect those of Nike, Inc.

© 1999-2024 NikeTalk.com

Share this page

Back
Top Bottom