Good to know that. Maybe coincidence after all and some junk is down there that needs cleaning.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
3.0 Bugs...
- Thread starter RxMac
- Start date
- Sort by reaction score
Good to know that. Maybe coincidence after all and some junk is down there that needs cleaning.
in tweetie you can't swipe on a tweet to quick reply
again, facebook not displaying pics..
youtube works fine for me..
visual voicemail works fine for me..
mms even though its ON, doesn't seem to exist in the Messages app... might be the O2 carrier settings not being present maybe?
i didn't do a clean restore either.. it was just an upgrade from 2.2.1 to 3.0
does feel a little laggy but i can lie with that!!
questions:
anyone managed to get ical subscriptions to sync using mobileme?
and where do notes sync to? can't see anything in mail
again, facebook not displaying pics..
youtube works fine for me..
visual voicemail works fine for me..
mms even though its ON, doesn't seem to exist in the Messages app... might be the O2 carrier settings not being present maybe?
i didn't do a clean restore either.. it was just an upgrade from 2.2.1 to 3.0
does feel a little laggy but i can lie with that!!
questions:
anyone managed to get ical subscriptions to sync using mobileme?
and where do notes sync to? can't see anything in mail
I noticed when setting up email accounts that the backspace key would sometimes hang for a while (20-30 seconds) before moving again.
It's definitely a lot better than Clippy (and that other one, can't remember what it was called.) You either double tap or press and hold and you'll get the little pop ups. Once you figure out what does what you'll be good to go. Very easy.
Mail rarely opens for me... it opens up and then crashes after a few seconds. This is the only real bug i've found. Other than that, it's a bit laggy.
So far here is my list of bugs:
b. (3.0 sdk Xcode - cannot transfer my apps to the 3.0 device, can't find my certificate?? Never had this problem before...)
1. YouTube does not work, period.
2. General lag in scrolling for certain apps (Not Contacts, oddly enough)
3. Major audio issues involving built in Sounds and iPod app. After receiving a phone call that interupted my music, then music did not resume, but the "play" triangle remained in the status bar, and all other sounds became muted (ringtone, mail, sms). Restarted the phone, all returned to normal.
4. 3.0 hogs Memory like a Windows version of (insert_app). There is new MemoryApp in the App store designed to help 3.0 testers, it can free 50+ mb of memory at once. Definitely necessary, as just a few tasks eat up all available memory, very quickly.
b. (3.0 sdk Xcode - cannot transfer my apps to the 3.0 device, can't find my certificate?? Never had this problem before...)
1. YouTube does not work, period.
2. General lag in scrolling for certain apps (Not Contacts, oddly enough)
3. Major audio issues involving built in Sounds and iPod app. After receiving a phone call that interupted my music, then music did not resume, but the "play" triangle remained in the status bar, and all other sounds became muted (ringtone, mail, sms). Restarted the phone, all returned to normal.
4. 3.0 hogs Memory like a Windows version of (insert_app). There is new MemoryApp in the App store designed to help 3.0 testers, it can free 50+ mb of memory at once. Definitely necessary, as just a few tasks eat up all available memory, very quickly.
I am doing a fresh install as we speak, since I did restore from backup (which seemed to work fine).
See if it really makes a difference or not....
shouldn't these bugs also be reported to apple as well?
That's all I've been doing besides working with the new API's for the last 24 hours....believe me, they know...
Thank you for pointing this out, I just did a Fresh 3.0 install, did not restore from back up, and You Tube is fully functional again.
Gratitude.
I wonder if Forstall was slightly embarrassed when opening up the Messaging app the other day on the screen. That lag was brutaaaaaal. And is clearly a problem that I hope they address.
I started with a fresh install and input all of my data back into PocketLint, 1Password, To-do's, etc.
I haven't had a single program crash on me. My YouTube works flawlessly. The only major bug I've found is trying to reorganize the springboard. Rather than simply touching and dragging, you have to push and hold until the icon dims and enlarges slightly then move it.
Nothing I can't deal with til June/July.
I haven't had a single program crash on me. My YouTube works flawlessly. The only major bug I've found is trying to reorganize the springboard. Rather than simply touching and dragging, you have to push and hold until the icon dims and enlarges slightly then move it.
Nothing I can't deal with til June/July.
I've been playing with it alot and it seems to be on par with 2.2.1 if not a little bit better. I played with it all-day yesterday, did a 35 min Voice Memo in class and left it on my nightstand (no charging) all night and the notice that I had 20% battery life remaining just popped up after using Google Reader web apps to read about 30 stories.
I haven't had most of the issue that other people are talking about other than YouTube. My favorites that are saved in the phone will play fine, but I am unable to search for videos or log-in. Most things seem a little quicker, but there are some issues with lag that I assume will be addressed.
When i try to move and scale a wallpaper it works for a bit then stops. Thus i'm not able to move the picture or anything
Edit: Well i have to press kind of hard to move the picture.
Edit: Well i have to press kind of hard to move the picture.
My Messages app doesn't not take nearly that long to open, so it really could have been the projector...
The alarm clock feature is unpredictable and dangerous in 3.0 beta.
So this morning I took my friend to the airport at 5am, came back at like 6:30am dead tired, wrote my boss saying that I had taken my friend to the airport and that I was gonna be in by 10am (so I could sleep a little bit). My alarm was set for 7:30am but I fully intended to just wake up to it, and then reset it to 9am so I could be to work by 10am.
I woke up at 8:37am to a text message sound, immediately followed by my alarm clock. I was very confused, but also very tired, so I just set my alarm for 9am and went back to sleep.
Next thing I know, it's 11am! I get up and frantically start getting ready, wondering what had happened. I assumed I must have set my alarm for PM instead of AM, so I unsleep my phone to take a look, and immediately the alarm starts going off. It's 11:07am at this point.
Here is what I think is happening. The alarm clock can't work in sleep mode and needs something else to happen first so the alarm clock can go off. The first time when I had it set for 7:30am, it went off at 8:37am once I got a text message first. Then when it was supposed to go off at 9am, it only went off once I unslept the phone at 11:07am.
Anyway, moral of the story, WATCH OUT those who have jobs! I like 3.0 beta enough that I'm gonna go get a cheap alarm clock at Wal-mart or something today... Now I understand why everyone was stressing that 3.0 beta should not be used on your main phone but only a testing phone. This is my own fault I guess. Luckily I have an understanding boss.
So this morning I took my friend to the airport at 5am, came back at like 6:30am dead tired, wrote my boss saying that I had taken my friend to the airport and that I was gonna be in by 10am (so I could sleep a little bit). My alarm was set for 7:30am but I fully intended to just wake up to it, and then reset it to 9am so I could be to work by 10am.
I woke up at 8:37am to a text message sound, immediately followed by my alarm clock. I was very confused, but also very tired, so I just set my alarm for 9am and went back to sleep.
Next thing I know, it's 11am! I get up and frantically start getting ready, wondering what had happened. I assumed I must have set my alarm for PM instead of AM, so I unsleep my phone to take a look, and immediately the alarm starts going off. It's 11:07am at this point.
Here is what I think is happening. The alarm clock can't work in sleep mode and needs something else to happen first so the alarm clock can go off. The first time when I had it set for 7:30am, it went off at 8:37am once I got a text message first. Then when it was supposed to go off at 9am, it only went off once I unslept the phone at 11:07am.
Anyway, moral of the story, WATCH OUT those who have jobs! I like 3.0 beta enough that I'm gonna go get a cheap alarm clock at Wal-mart or something today... Now I understand why everyone was stressing that 3.0 beta should not be used on your main phone but only a testing phone. This is my own fault I guess. Luckily I have an understanding boss.
Beejive crashes after going to type a message after having scrolled through received messages. I've reported the bug to them.
I just tested this out and had no issues. It's on snooze right now so I'll report back when/if it goes off again.