Interesting siri bug.....?

I tried to create a calendar entry today for a John Smith. But siri refused until I told her which of the 25 "johns" I have in my address book is the right one. Trouble is John Smith isn't in my address book and never will be! Its a one off appointment.
Surely there is a way to make it create an appointment without having to refer to my address book???

Similar Messages

Interesting thread bug

Hi,
I'm developing a client/server whiteboard system for my term project. I've hit to an interesting threading bug. The very brief description of the goal is like this: A client has a method (getActiveUsers) to get the list of active(logged in) users from server. In order to accomplish this, it sends a command to server to receive the user list. In an undeterministic time frame, the server sends a message as a reply, which includes the user list. When the client gets the user list, it is expected to update its local user list. The code for these goes like this:
// The method that returns the list of active users
// in the system
public Vector getActiveUsers()
synchronized(activeUsers)
channel.send(new ListActiveUsers(username));
try
activeUsers.wait();
catch (InterruptedException e) {}
return activeUsers;
// The method that is fired when a new message
// is received (Observer pattern)
public void update(Message msg){
if (msg instanceof ActiveUsersList)
synchronized(activeUsers)
activeUsers=((ActiveUsersList)msg).activeUserList;
activeUsers.notifyAll();
return;
inform(msg);
the Error message is this:
java.lang.IllegalMonitorStateException: current thread not owner
     at java.lang.Object.notifyAll(Native Method)
     at domain.Whiteboard.update(Whiteboard.java:49)
     at services.messaging.Channel.inform(Channel.java:95)
How can a thread be not owner of an object when it enters a synchronized block for that object?
Thanks for any help.
Regards...

You synchronized on one object, referred to by your variable activeUsers, but then you reassigned activeUsers to refer to a different object and called notifyAll on that object. Remind yourself of the difference between variables and objects.

Siri bug accept reminders but doesn't store them in my calender

To me it seems to be a SIRI bug:
Dictating a new date/event for the calender, SIRI accepts reminders (when repeating, what has to be added to my calender, reminder is mentioned). But it doesn't store the reminder in the date/event.
I'm using iPhone 5 with iOS 6.0.2. (German settings). Standard Calender Reminder Setting are "without" (e.g. normally the events dont have a reminder, if not explicitely set).

Hi rtsmith53
This sounds like an accessibility option that has been enabled.
Try double tapping each key of your pin, this should work.
Once you're back into your phone, tap Settings and then tap General. Tap VoiceOver and disable it.
Hope this helps
Ads

Siri bug reporting?

How can one submit a bug report for Siri? Below for your review - this is sort of important, I think...
Note that Siri is saying "Street Agnes Hospital" instead of "Saint Agnes Hospital" - therefor she finds nothing.
If I search for baltimore hospitals, I can select "Saint Agnes Hospital" from a list.

Is there no phrase in Siri that would simply submit the last query (and Siri's response) as being unsatisfactory? Why should one have to go to a web form to file a bug against a handsfree interface that is not responding appropriately??

IPhone 5 ios 6.1 siri bug with headphone

Hello,
I noticed today that after I updated to IOS 6.1 siri no longer works when I use a headphone and have the phone in my pocket. If I initiate siri using the headphone button, it beeps for me to speak then immediately beeps to indicate siri is no longer active. It works if the phone is out of my pocket. Perhaps there is a bug with the proximitiy sensor that turns off siri? Can anyone confirm this and if so, how can I submit this as a bug to apple?

Same thing happens to me. It's happening because using the headset activates the siri button, then your leg touches the button immediately dismissing or quitting siri. The only solution I know of is to turn the screen of your phone away from your leg while the phone is in your pocket.

Interesting Siri/iOS 5 issue

I've found an interesting glitch with Siri, and I was wondering if anyone had a workaround.
Siri will only dial numbers that have a +1 or similar international code in front of them. This poses a problem, as in contacts, 5555555555 and +1 (555) 555 - 5555 are thought of as two DIFFERENT numbers, for some reason. In other words, if I were to send a text to someone, I would get a response back from a number like 5555555555. However, when I ask Siri to dial this person, it replies that it can't call them. Why would that be? Does anyone have a workaround?

According to this forum: http://forum.lowyat.net/topic/2175165/all, it seems that Siri is expecting a 7-8 digit phone numbers excluding the country code and area code, so adding an extra "0" digit or two at the back of the phone number may be able to fix your problem. The phone number should still connect correctly. Try that, it works for me in Indonesia where some phone numbers are still 6 digits.
Hindra

Interesting PCD bug? Runaway process creating objects?

Currently, we are on EP 6 sp 16. We have had a very interesting situation occur with our development portal at random times. Not always, but every so often, the following happens. We will either copy an oobject (for instance an iView) to another folder or change the id on an object. As we step through the wizard on the final step where it should complete the action, it will sit at 50% complete and just flash over and over....50%....over and over....after several minutes, it will error out. You would think that nothing happened, but what actually happens is that it makes THOUSANDS of copies of the object...naming them like myiview_0, myiview_1, myiview_10, myiview_100, myiview_1000, myiview_2, myiview_20....and on and on. And yes, there will be thousands made. As you can guess, it is VERY annoying. Luckily our folder layout makes it easy to simply go delete the whole folder with all the multiple copies, but had we not done that.....geeez....lots of work. What is worse is that sometimes, you can't actually see all the duplicate objects until the portal is restarted (I found this out, because they showed when I tried to create a package but not in the PCD in content admin). They actually are invisible in the PCD!
Sooooo anyone else run across this? Any idea why this might be happening?

Well...no one seemed to be having the same problem. We have not found the root cause, but thankfully, using the PCD Inspector tool makes it MUCH easier to delete all the "corrupt" objects (though it is still time consuming as each "hiccup" creats about 30 pages of bad objects). I will just mark this one up to one of those portal "oddities". =)

Interesting artwork bug...

This is going to be an interesting one to explain. Please read VERY carefully:
On my iPhone, along with many other songs, i have the In Flames album titled "Come Clarity" and the All That Remains album called "The Fall of Ideals." For some odd reason, whenever i pull up the In Flames album ON MY IPHONE, it displays the All That Remains (ATR from here on out) artwork instead. My initial thought was that, somehow in my media library, it had put in the ATR artwork for in flames - i wish it had been that easy.
If i go into my music library ON MY COMPUTER, it displays the proper album artwork and if i right click -> get info -> album artwork tab it shows the proper In Flames, Come Clarity album artwork (which is an awesome album artwork by the way). If i have only the in flames album on my iphone, obviously, it displays the proper album artwork because the getalbumartwork(), or equivalent, would have nothing else to pull from the directory. Now for the fun stuff.
As i said above, the album artwork is correct on my computer for in flames, however, when having the iphone plugged into my computer - and this is the important part - i click on the iphone device, then music, putting me in the iphone directory, and go through the same steps as above (right click -> get info -> album artwork tab), it still displays the correct album artwork. Put simply, the artwork is correctly stored on the iphone itself, however, there seems to be something wrong with the getartwork() function in the coding itself, or at least you would think so; but why, then, would it perfectly pull my nearly 2000 other songs and their album artworks from the directory?
I have tried deleting all the music from my phone and then re-syncing multiple times. I have also tried different syncing orders; for instance, putting in flames on first, then the rest of my music, or putting on all my other music first, then the in flames album. All of which have the same end result.
If anyone can figure this one out, you're my hero.
Thanks in advance.

http://kelleytown.blogspot.com/2008/01/what-apple-doesnt-want-you-to-know-part.h tml

Really interesting bizarre bug in TreePath, I'm confused beyond belief

Inside a large program, in which I use custom TreeModel instead of DefaultMutableTreeNode's etc, I have a following method which needs to recurse up a TreePath.
This seems to be a MAJOR bug, because if you look in the following ten lines, I verify several times that the argument is non-null (and even return early if it is).
However, at the line "while( ... )" it throws a NullPointerException! What, is the keyword "while" null ???!?!?! Because we know that tp is NOT null.
We also know that we can call "tp.getPathCount()" because I do so and even print it out!#
If you have any thoughts, please CC to [email protected], because at the moment I'm sure Sun will refuse a bug report (without more info) and I doubt I can make a small program that demonstrates this - otherwise surely it would have been found before!
public static Hashtable getMapping( TreePath tp )
System.out.println( "tp = "+tp );
Hashtable rc = new Hashtable();
if( tp.getPathCount() > 0 )
else
return rc;
System.out.println( "tp = "+tp );
int tpcount = tp.getPathCount();
System.out.println( "tp.count = "+tp.getPathCount() );
while( tp.getPathCount() > 0 )
return rc;
}

Oh dear. After prolonged testing, I realised the problem: when the TreePath is the root, it returns null as parent , which happens just before I do the test as to whether to carry on - I had originally put the test just before that, but had moved it to just afterwards, thereby causing the problem!
Very foolish, really.

IOS 7 and iOS 7.02 Siri bug and issues

on the first version of iOS 7 and the most recent update (iOS 7.02) siri refers to me as tiffany every so often but is now more frequent than before. And before iOS 7 came out, siri was much better in general, for it will not recognize speech as easily as before. But to past and still current siri problems. my favorite thing to do with siri is show people how it shows you were to get rid of a dead body. But it simply replies "hmmm... i used to know the answer to that." and siri after iOS 7 will no longer tell you the scores of major sporting events such as college or nfl football.

Restore your iPhone in iTunes from your backup. I'm not having any of those issues...well, except for the dead body one.

Any Siri bugs?

Siri on my iPhone 4S seems to think that NYC is in Texas........
anybody else have issues?
If Siri has a robot voice, restore as new iPhone. Problem solved

I have talked with a number of users who decided to go to the 4 S primarily because of the Siri feature, however they appear to be having similar issues. Are you aware of anything that can be done to improve the quality of the feature or are you experiencing problems as well. Thanks

Interesting security bug

I just encountered this with my Essbase user community: We are forcing password changes, and some users are getting locked out after they change their passwords. It seems that this is why it's happening: 1. User logs in on Sheet1, using ID and current password. 2. Essbase "remembers" the ID and current password, so user can do implicit connections (just using Essbase Retrieve, for example) on Sheet2, Sheet3, etc. 3. User is prompted for new password and changes password. 4. The new password is not "remembered", even though it's used to connect Sheet1. Essbase still "remembers" the old password, and will try to use it on the next implicit connection. So...the obvious solution is for users to just make sure they either disconnect and then reconnect after changing their passwords, OR, make sure they do an explicit connect when they go to a new sheet. I know, this is not anything major--just thought I'd mention it. Jared

any solutions to how to install an older update to see if you tube can be loaded

Interesting little bug...

Ok. I've been able to repeat this and a friend of mine is able to repeat it as well:
1. Select any channel fader (mixer or arrange)
2. Double-click the volume amount (0.0db); either midi or audio
3. Enter -10 as the amount
4. What do you get when you hit enter? Hint: It's NOT -10.
What is the link to report these?

That's not strictly true, and is a common misconception.
The audio "faders" and pan controls are MIDI resolution (you're always going to have limited resolution, becase the minimum you can move a fader is 1 screen pixel).
However, Logic's internal automation system is much more accurate than that. Using a Mackie Control will let you take advantage of 10-bit resolution for automation.
Is there a way of using 10-bit automation without using an MCU? Yes - if you use the little automation slider in each track, it will write automation data as 10-bit values (you can verify this by opening the automation event editor and looking at the values - regular automation will be 7-bit values, 10-bit resolution will have the extra bytes in the list (like a sysex mesage).
But yes, the onscreen controls will write 7-bit automation only...

Interesting Feature/Bug?

Try this: Play a song in iPod, and if you have a Internet connection, hit that as well.
In the top right corner, you'll see a small blue play button. Scroll down the page a bit, then hit that button. It does nothing in iPod, but zings you back to the top of the page you're viewing.
OK - what's that about?

Hey Podcaster,
Im not able to recreate that issue either.
You could try restoring the iPhone as described here:
http://docs.info.apple.com/article.html?artnum=305744 and see if the issue persists.
Jason

[BUG] iOS 6 - BATTERY DRAIN : SIRI Raise to Speak/Proximity Sensor Always On/Flashing When Screen Active

Bug: Raise to Speak sensor for Siri remains on whenever the screen is active - regardless of Siri Raise to Speak Setting (enabled or disabled).
After updating to iOS 6 (via iTunes - not OTA), I noticed that my battery was taking quite a bit of a hit. Granted I was checking out the new features but aside from a very short call, nothing major in the way of activity.
I had also noticed that Siri sounded quite a bit different with iOS 6 (10A403) than with 5.1.1 (9B206). Not only did the Siri Voice change but also the responses vary between the two iOS versions.
Example: What is the weather like in Alaska?
iOS 5.1.1 response:
Here's the forecast for Juneau, Alaska through Monday
iOS 6.0 response:
Here's the weather for Juneau, AK through Monday (note: Siri does not say "Alaska", instead Siri says 'A-Kay'
With iOS 6, Siri sounds more robotic. After looking at speech rate settings and comparing between the two versions, I could find nothing different. I decided to post a video and this is where the Siri bug became interesting and tied into the battery drain with iOS 6.
Remember with 5.0.1 we saw a hit on battery drain and one of the fixes was a fix to the proximity sensor (http://hottipscentral.com/could-siri-be-hurting-iphone-4s-battery-this-little-li ght-might-mean-something/). Well, it appears this bug is back in iOS 6. When I went to do the video, I noticed that my 4s had a flashing light near the earpiece. It remained on continuously. The only time it would stop flashing was when the phone was locked and the screen inactive. As soon as I hit the lock button to bring the phone out of lock, the sensor would begin to flash again.
Give it a shot, hold up your iPhone to a webcam and see if your result is the same.
Submitting this to Apple via the feedback form. Please do the same if you are seeing the same behavior.
http://www.apple.com/feedback/iphone.html

I dont believe so Amy. Phone has not sustained any damaging drops nor any liquid spills. Was not an issue before but I figured I'd post as I believe this is a definite bug. I neglected to mention that I have my wife's 4s (5.0.1 build) which I am using as a comparison.
Based on the issues folks are reporting with the ambient light sensor, its either the proximity or the ambient light sensor causing the drain. I've turned auto brightness AND raise to speak both off and the sensor continues to flash as I described in my opening post.
If others can confirm, this will definitely need to be looked at by Apple and fixed.
I just found this - same behavior (posted 7/24/2012 on another forum - source link below).
Hi folks, remember the proximity sensor (always on bug) I reported here in iOS 6 Beta 1 bugs/feedback thread? It continues to happen in beta 3, I reported to Apple and the answer I got from them is that it behaves how it's intended to do
Thing is, when you turn Raise To Speak feature off, and use your webcam (no IR filter) to verify if it turned infrared proximity sensor off, results that it didn't. Since iOS 5 this bug has been present, power cycling, or doing a soft reset solves this issue but this solution does not apply in iOS 6. Don't have an idea on how hard it is on battery draining, but it makes no sense that this sensor stays on forever even when you turn this feature off. Unless it has to do with constantly display brightness adjust feature that we have noticed came with iOS 6 version. Doing some test of this feature (some of you commented about a brightness bug in earlier posts) I noticed that ambient light variations make that display brightness adjust accordingly to brighter or darker ambiences. Previous to iOS 6, the sensor samples the ambient light, and adjusts the brightness; it does this only once--each time you unlock the phone after waking it. Now in iOS 6 you can easily watch how brightness slider adjusts itself when display senses light variations. If you open Passbook app it raises brightness to full (it is supposed to act this way for easy reading of barcodes) but getting out of Passbook app makes that brightness readjusts itself responding to actual ambient light intensity (this adjusting task occurs slowly until brightness slider stops to right level).
I've checked and ambient light sensor and proximity sensor are separate and work differently but if Apple says that an always on proximity sensor in this iOS version is behaving how it is intended to do; all that I could think of is that it has to do with ambient light "sensing"??
Source: http://forums.imore.com/1894808-post55.html

Interesting siri bug.....?

Similar Messages

Maybe you are looking for