All Devices iOS 13.3.1 Beta 3 ― Bug Fixes, Changes, and Improvements

Status
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.

Banglazed

macrumors demi-god
Original poster
Apr 17, 2017
3,253
3,230
Cupertino, CA
iOS 13.3.1 Beta 3

Release Date ―
January 22, 2019
Build Number ― 17D5050a
Darwin Kernel Version ― 19.3.0 Thur Jan 9 22:14:54 PST 2020; root:xnu-6153.82.3~2

iOS 13.3.1 Beta 3 Release Notes

New Features & Changes
New Issues
Remaining Issues

  • Mail Sync issues with push notifications, but mail needing to be pulled when opening mail app - Since iOS13 Dev Beta 1
  • All mail notifications cleared when any one of them clicked on the notification centre to open that mail.
Resolved Issues
Temporarily Removed
Additional Notes

  • Intel iPhone 11/Pro/Max: 1.04.06
  • Intel iPhone XR/XS/Max: 2.04.03
  • Qualcomm iPhone 8/8 Plus/X: 5.30.01
  • Intel iPhone 8/8 Plus/X: 3.03.03
  • Qualcomm iPhone 7/7 Plus: 7.10.01
  • Intel iPhone 7/7 Plus: 4.01.02
  • iPhone SE: 9.11.01
  • iPhone 6S/6S Plus: 7.30.02
United States
  • Verizon - 40.0
  • Visible (MVNO Verizon) 34.0
  • Verizon (iPad) - 38.5
  • T-Mobile - 39.5.1
  • T-Mobile (iPad) - 34.5
  • AT&T - 40.0
  • AT&T (iPad) - 37.0 (b6)
  • Cricket - 40.0
  • MetroPCS -
  • U.S. Cellular - 32.5.9
  • Sprint - 40.0
  • TracFone/Straight Talk/Walmart Family Mobile - 39.0.2
  • Xfinity Mobile 39.0
United Kingdom
  • EE - 40.0
  • BT-UK MVNO on EE- 40.0
  • Three - 3
  • iD Mobile MVNO on Three - 36.5.4
  • O2-UK - 36.0
  • Vodafone UK - 39.0
  • Virgin Mobile MVNO on EE- 39.5
Germany
  • Vodafone.de - 39.5.2 (downgraded)
  • Telekom.de - 40.0
  • O2-DE - 40.0
Australia
  • Optus - 32.0
  • Telstra - 40.0
Belgium
  • Orange B - 32.5.7
  • BASE - 33.0
  • Telenet - 38.0
Canada
  • Videotron - 40.0
  • Rogers - 40.0
  • Fido - 38.0
  • Bell - 40.0
  • Telus - 32.5.12
  • Freedom Mobile - 34.0
  • Fizz - 40.0
  • Virgin Mobile - 40.0
France
  • Bouygues Telecom - 40.0
  • Orange France - 31.5.1
  • Orange Morocco - 31.5
Netherlands
  • KPN -
Southeast Asia
  • Singapore Singtel -
  • Philippines Globe - 39.0
  • Philippines Globe (iPad) - 38.0
  • Philippines Smart - 36.1
  • Thailand AIS -
  • Malaysia Umobile - 33.0
  • Malaysia Maxis -33.0
  • Malaysia Digi -
  • Malaysia celcom -
  • Hong Kong - 32.0
Sweden
  • Comviq -
  • Tre - 31.0
Switzerland
  • Salt - 40.0
  • Swisscom - 39.5
Ireland
  • Eir - 33.5
  • Vodafone IE - 38.0
Turkey
  • Turkcell (Lifecell) - 36.5.5
  • Vodafone TR - 32.0
  • Turk Telekom - 32.0
Poland
  • T-Mobile -
  • Orange - 32.0
  • Play - 31.0
Portugal
  • Vodafone P - 40.0
Greece:
  • Cosmote - 38.0
India
  • Airtel - 39.5.1
  • Jio - 40.0
  • Vodafone Idea - 40.0
  • Idea Cellular - 40.0
Mexico
  • Mexico - Telcel - 35.0
Guatemala
  • TIGO GT - 40.0
Other
  • Docomo - 32.5.10
  • AlwaysOnline -
 
Last edited by uandme72:

macintoshmac

macrumors 68040
May 13, 2010
3,559
3,051
There is some code optimisation for iPhone 7 and 8, possibly. IPSW used to be 4.01 GB and now it is 4.00 GB. Minor, but I'm interested to know what might have happened and if that brings any noticeable positive improvement to these devices.
 

macintoshmac

macrumors 68040
May 13, 2010
3,559
3,051
Every build will be slightly different in size due to code and asset changes.
Yes. I noticed that the last few releases for iPhone 7/ 8 have all been 4.01 GB but this one is 0.01 GB less so caught my eye and I wonder if changes produce a noticeable impact. 10 MB reduction ought to make something better! :D
 

john991

macrumors 68020
Sep 30, 2014
2,436
752
Ontario
Every time I change the eSim / sim label name under cellular it eventually changes back to primary and secondary. My secondary is a physical sim.

this has been happening since iOS 13. Rather annoying, sent bug to Apple and of course nothing.

anyone else notice this?
 

bizack

macrumors 6502a
Apr 21, 2009
577
368
There is some code optimisation for iPhone 7 and 8, possibly. IPSW used to be 4.01 GB and now it is 4.00 GB. Minor, but I'm interested to know what might have happened and if that brings any noticeable positive improvement to these devices.
Code optimization for performance typically produces larger binaries, not smaller. Removing dead/unused code will lead to smaller binaries.
 
  • Like
Reactions: macintoshmac

macintoshmac

macrumors 68040
May 13, 2010
3,559
3,051
Code optimization for performance typically produces larger binaries, not smaller. Removing dead/unused code will lead to smaller binaries.
It appears I might have used the term 'code optimisation' loosely? I meant to say dead/ unused code might have been removed. Is that not optimisation?
 
  • Like
Reactions: atomic.flip
Status
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.