Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Has anyone else been experiencing frequent dropouts in Bluetooth audio (particularly played via Spotify) on iOS 10 PB2? Wondering if it is a bug or a shift in functionality because of the message sending/receiving sound.

I am noticing the dropouts sometimes when using another application (such as sending/receiving messages through iMessages or viewing GIFs in the iMessage app drawer), but they also occur occasionally while I am not interacting with the phone. The dropouts were not previously present in the most recent 9.x.x PB. Additionally, the volume behavior when connected to an external Bluetooth speaker has changed in iOS 10 PB2 from what it previously was in the most recent 9.x.x PB.

Edit: Nope, the dropouts are pervasive everywhere. Virtually un-listenable when idle on the home screen. Anyone else?

Been getting drop out on my 1.5 hour journey in my car today. Reported to Apple.
 
I've got a 6s and the lock screen was a disaster in the first public beta even with 3D Touch available for notifications. I was thrilled when I heard they added the option back in to return to the iOS 9 press to unlock Touch ID functionality with the home button.

When the new public beta was released I installed it immediately and I love it. If I want to see notifications on the lock screen after they've come in and the screen has gone dark again I can press the button on the right side of the device. If I want to unlock it I can press the home button once and get right through to the home screen.

If you value your privacy and limit unlocked notifications returning to iOS 9 style press to unlock with the home button makes perfect sense. Who the hell wants to press it twice to unlock the phone under that scenario? Further, the new functionality was buggy as hell. Press the home button lightly and I had to press twice to unlock it, press it and hold it in too long and it activated Siri but if I pressed it just right in between a light press and a longer press it would go through Touch ID and unlock the phone. Having to look down to see which of those three behaviors had happened was a PITA and eliminated the whole point of using Touch ID to unlock the device!

If Apple wouldn't have added this option back in I would have reverted to iOS 9 and wouldn't upgrade. As such the 6s would've been my last iPhone.

Their logic is that Raise to Wake turns on the display, then you can decide to unlock with a press of the home button.

It may not work in all situations (the phone is sitting on your desk and you don't want to pick it up, etc), but that's what they were thinking anyway.
 
I'm shocked it says there's moisture in my connector when I am sure there is not.
And how do you know "it" was just introduced with this beta?

Erm, because the check was only introduced in this beta. Since it's both a beta and a new feature, I'm not sure why you're so 'shocked' at seeing a warning. Are you a developer or someone just keen to play around with new pre-release features? I'm assuming this isn't your primary device?
 
Anyone on a 6S plus verify animations aren't slow, and pressing certain icons doesn't put you in "jiggle" mode?
I can't speak to the second problem as I have not experienced it, but animations seem smoother and more timely. There had seemed to be a delay before most actions executed but that seems to. E fixed.

I'm only using a regular 6S tho so YMMV.

What does still happen tho when typing up posts on this website is pressing return or backspace suddenly scrolls to the bottom of the page. Does that happen for you?
[doublepost=1469055726][/doublepost]
Their logic is that Raise to Wake turns on the display, then you can decide to unlock with a press of the home button.

It may not work in all situations (the phone is sitting on your desk and you don't want to pick it up, etc), but that's what they were thinking anyway.
I can see both sides, but here's what matters: raise to wake is slow in the best of times and fails completely in the worst of times. Even on the watch, I'd say it just isn't ready for prime time.
 
  • Like
Reactions: jb-net
Typical Apple BS designed to add wear and tear to your hardware be requiring the user to push the home button EVERY TIME you want to unlock your device. ANYTHING to sell more product! iOS 10 = TURD!
 
This beta is much improved. It solves a freezing issue with the iPad mini 2 whenever playing random games. It would just lock up in the middle. Also, my iPhone 6s used to just lock up randomly for no reason at all with PB 1. So far that seems to be happening less often.
 
Has anyone else been experiencing frequent dropouts in Bluetooth audio (particularly played via Spotify) on iOS 10 PB2? Wondering if it is a bug or a shift in functionality because of the message sending/receiving sound.

I am noticing the dropouts sometimes when using another application (such as sending/receiving messages through iMessages or viewing GIFs in the iMessage app drawer), but they also occur occasionally while I am not interacting with the phone. The dropouts were not previously present in the most recent 9.x.x PB. Additionally, the volume behavior when connected to an external Bluetooth speaker has changed in iOS 10 PB2 from what it previously was in the most recent 9.x.x PB.

Edit: Nope, the dropouts are pervasive everywhere. Virtually un-listenable when idle on the home screen. Anyone else?

Yes, This happens to me in the car too. Seems to happen in any app (google play music, podcast app, audible etc). Must be the IOS not the individual apps.
 
I saw from someone that it doesn't perform well on the Air... Darn it! Was hoping it was an improvement from beta 1.
 
Will there be a Watch OS3 public beta does anyone know? I have had very few issues with the public beta on my iPhone, but have found my iPad to be rather buggy.


I doubt that they'd add an option for a public beta for watchOS since there's no option to downgrade the OS. If it's too glitchy for someone's liking or if they had any other reason to downgrade a beta software, they'd be stuck with it. :|
 
I doubt that they'd add an option for a public beta for watchOS since there's no option to downgrade the OS. If it's too glitchy for someone's liking or if they had any other reason to downgrade a beta software, they'd be stuck with it. :|

On the other hand, Apple's public beta page offers a profile for installation on watchOS. Maybe they're still thinking about it, or waiting for the betas to mature a little more.
 
Hmmm... What should I do?
 

Attachments

  • image.png
    image.png
    201.4 KB · Views: 260
Where are the release notes available? The link apple gave just takes me to the public beta basic info website...
 
downloading, only had two issues with 1:

1) Some third party apps, particularly banking apps, would crash out when trying to log on,
2) alteration of the new Photos features like the People Album would cause CPU to massively spike rapidly draining the battery which wasn’t resolved even by a hard reset. It just took a very long time connected to power for it to calm back down. Person caveat: I have 52K of pictures on iCloud and so my phone is maintaining a massive facial recognition database.

Yup. My 'banking app' did not work in Beta 1. I advised Apple, and I assume others did also. It's FIXED in Beta 2! Yea!
 
  • Like
Reactions: HackDaBox
Anyone noticed screenshots are difficult now ? I found holding sleep/wake then tapping home works every time but holding home and tapping power either puts the device to sleep or takes you to the shutdown screen or activates Siri !
 
You're clearly on a 6s series phone--it really just feels broken on my 6. The response time to read the fingerprint on my 6 is sufficiently slow that I never had a problem accidentally unlocking the phone if I just wanted to see what was on the lock screen. Now I press the button and it takes long enough to scan my fingerprint that there's a noticeable delay before I can press the home button to go to my springboard.

That said, I may try to get used to this behaviour because I'll have a faster phone eventually...

Exactly. When I went from 6 to 6s, that's when my frustration with blowing past the lock screen started. Going forward, this will be a problem for more and more people as everyone's TouchID sensor would be upgraded to the faster one as they get new devices. Perhaps they changed it a bit early in their haste to appease the more recent upgraders.
 
Is anyone else's installation erroring out? I've tried multiple times, power cycling, and freeing up plenty up and space
 
Are you talking about unlocking the device when you say "just to rest a finger on the button"?

If so, you can do exactly that and have it how it was in iOS 9. Go Settings> General> Accessibility> Home Button and toggle the "Rest Finger to Unlock" option.

Yeah, I found this about an hour or so after I posted my comment. I'm rather miffed that it's listed under "Accessibility", as if to infer there's something "broken" about users who prefer this method of authenticating their device(s).

What also bothers me is the little blurbage "Press home to unlock" since, now that I've re-enabled "rest finger to unlock", is not accurate. I could understand having to put the "Slide to unlock" blurb on earlier devices. But this new bit of text is off, and it got me to thinking... if in 2016 you have to explain on the device how to unlock it, you're doing it wrong.
 
I use Bluetooth headphones for music and have not had any issues on PB1 or 2.
I've been having trouble too, and submitted a bug report on it. My headphones will connect, then silently disconnect.

If I'm in the Bluetooth options screen at the time, they'll connect, and then actually show as disconnected. Tapping on the device reconnects them properly. I can also reconnect them by trying to force my headphones to reconnect by pressing the play button repeatedly. Everything was fine with Bluetooth under iOS 9.

It's actually slightly better under Beta 2--the headphones reconnect much more quickly.
[doublepost=1469110903][/doublepost]
Exactly. When I went from 6 to 6s, that's when my frustration with blowing past the lock screen started. Going forward, this will be a problem for more and more people as everyone's TouchID sensor would be upgraded to the faster one as they get new devices. Perhaps they changed it a bit early in their haste to appease the more recent upgraders.
It's also worth noting that for the 6s, you can have raise-to-wake enabled, and I can't. Until everything has a speedy sensor and will turn on the screen when you pick up the phone, I think Apple will be forced to have the old method available in settings.
 
Hi, does anyone know how would the "moments tab" in the Photos App would go through your entire photo library if every pic is in iCloud? I think they said that it'll process al that stuff locally but what about when you have thousends
 
Hi, does anyone know how would the "moments tab" in the Photos App would go through your entire photo library if every pic is in iCloud? I think they said that it'll process al that stuff locally but what about when you have thousends
I thought it was supposed to download them, process them and delete them.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.