|
2010-01-11
, 07:39
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#3
|
|
2010-01-11
, 10:14
|
Posts: 9 |
Thanked: 6 times |
Joined on Dec 2009
|
#4
|
Wait, what?
This bug is resolved as FIXED
|
2010-01-11
, 10:16
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#5
|
|
2010-01-11
, 16:12
|
Posts: 254 |
Thanked: 122 times |
Joined on Nov 2009
|
#7
|
|
2010-01-11
, 16:44
|
Posts: 329 |
Thanked: 142 times |
Joined on Oct 2009
|
#8
|
FIXED state means nothing for Nokia endusers
According to this reply The only meaning of that is that someone in Nokia thinks they have a solution for problem. It doesn't mean that you'll see this problem fixed in nearest software update or even in any other update.
Just wait and use community-created USSD dialer for now.
These are control codes required by many providers in germany
The 'bug' here seems to be the QA release policy by nokia. While i understand and appreciate the that bugfixes involving significant progamming are QA tested as part of a whole system, this bug breaks phone for those german providers I have used. If this is simply due to application rejection of dialing characters, I suggest a fasttrack to address trivial application bugs that make device sales impossible.
Am i incorrect in thinking that this is a trivial fix, without deeper problems?
I am really not a phone guy, feel free to vote this down, tell me to jump in a lake, or point me to the relevant discussion thread. thanks
find . -name \*.mp3 -exec mplayer -quiet -shuffle "{}" +
das ist your media player, and yuu vill like it