Jump to content

iOS 7 Final


illest_ios

Recommended Posts

so i know iOS7 will be ready sometime in fall, im running the beta without a registered UDID or a DEV account. when the final verison is ready should i go back to 6.1.4? or am i safe to update over the air?

 

 

thanks :tu:

Edited by illest_ios
  • Like 1
Link to comment
Share on other sites

so i know iOS7 will be ready sometime in fall, im running the beta without a registered UDID or a DEV account. when the final verison is ready should i go back to 6.1.4? or am i safe to update over the air?

 

 

thanks :tu:

safe from what? It's just as illegal regardless.
Link to comment
Share on other sites

If your not running the latest beta I'm not really sure what the point is. Beta 3 is actually pretty stable but still has a bunch of bugs.

 

I would suggest running iOS 7 with a fresh install anyways. So it won't actually matter.

Link to comment
Share on other sites

You generally can't downgrade but Apple always makes the final release available to beta devices, though sometimes you have to restore with iTunes if something is completely busted.

Link to comment
Share on other sites

If you need a Sprint 6.X IPSW file, I can download one and you can roll back.

 

Being an iOS developer has it's benefits. :)

Link to comment
Share on other sites

If you need a Sprint 6.X IPSW file, I can download one and you can roll back.

 

Being an iOS developer has it's benefits. :)

You can roll back as a developer? :o

 

I've actually been wanting to go to 6.1.2 because I'm on 6.0.1. There are a few bugs I want to get rid of. I can't because 6.1.2 isn't signed anymore though.

 

:-(

Link to comment
Share on other sites

You can roll back as a developer? :o

I've actually been wanting to go to 6.1.2 because I'm on 6.0.1. There are a few bugs I want to get rid of. I can't because 6.1.2 isn't signed anymore though.

:-(

I can only grab the latest version of iOS6.

 

I just restore from the iOS6 IPSW file, then restore content & settings from iCloud. I had to do that when I realized my corporate email & VPN soft token wouldn't work w/IOS 7.

Link to comment
Share on other sites

I can only grab the latest version of iOS6.

 

I just restore from the iOS6 IPSW file, then restore content & settings from iCloud. I had to do that when I realized my corporate email & VPN soft token wouldn't work w/IOS 7.

Oh darn.

 

At least there's a way of going back to iOS 6 if someone wanted to try the Beta.

Link to comment
Share on other sites

You can download the old ipsw's from many places. As a non-dev, I cannot do shit with them since Apple changed their signing mechanism again, a while ago.

 

I also did not know devs could get old ones signed and installed. I would pay for a dev license to be able to install old ipsw's in the event, for example, I broke a jailbroken device and replaced it only to find the new model came with 6.1.4 ;)

 

If you had a dev license and the correct 6.1.2 ipsw for the device, can you install it?

Link to comment
Share on other sites

You can download the old ipsw's from many places. As a non-dev, I cannot do shit with them since Apple changed their signing mechanism again, a while ago. I also did not know devs could get old ones signed and installed. I would pay for a dev license to be able to install old ipsw's in the event, for example, I broke a jailbroken device and replaced it only to find the new model came with 6.1.4 ;)If you had a dev license and the correct 6.1.2 ipsw for the device, can you install it?

No, you cannot. Apple developers do NOT have any special privileges as far as downgrading firmware.

If you update to iOS 7 beta (or 6.1.4 for that fact), on a device with an A5 chip or higher, you cannot restore to anything but the latest iOS 7 beta or iOS 6.1.4.

Link to comment
Share on other sites

No, you cannot. Apple developers do NOT have any special privileges as far as downgrading firmware.

If you update to iOS 7 beta (or 6.1.4 for that fact), on a device with an A5 chip or higher, you cannot restore to anything but the latest iOS 7 beta or iOS 6.1.4.

That's what I thought. I had a glimmer of hope I'd missed something really cool ;) Ah, well.

 

Speaking of, how DO developers maintain compatibility with older firmwares across devices, if they can't install old IPSWs? Does the simulator function well enough that it is irrelevant? Or is that part of why apple passively forces users into FW & SW upgrades, so that the burden on devs is less? I guess a serious dev would only need one of each supported device, rather than have to hop FW & SW revs.

Link to comment
Share on other sites

You keep older devices around on older OSes. They've improved the simulator a lot though; it now supports installing various older OS releases. If needed, you can buy an old 3GS running iOS 4 for cheap.

 

The reality is 95% of all iOS devices are running iOS 6 so supporting older OSes past that isn't terribly relevant. They also are pretty good about maintaining stable APIs and deprecated stuff is often available for several major releases before it goes away. In practice, I've only ever run into OS version issues one time. If you dont have experience developing for other platforms, let me just say it seems like a miracle.

Link to comment
Share on other sites

I can only grab the latest version of iOS6.

 

I just restore from the iOS6 IPSW file, then restore content & settings from iCloud. I had to do that when I realized my corporate email & VPN soft token wouldn't work w/IOS 7.

 

thanks buddy. i am A ok with iOS7 right now. luckily i have a 6.1.4 IPSW somewhere in my laptop haha.

Link to comment
Share on other sites

  • 1 month later...

Can anybody confirm the old field test trick for dBm meter instead of bars (now dots) still works in ios 7? I can't get it to work anymore.

 

When I hit the power button, whilst in Field Test mode, then hold the home button to close the FT app, it just resets the app and doesn't close to the home screen. Thus, not allowing me to keep the dBm meter, which reverts back to the dots.

 

Is there another procedure now in ios 7, to force-close an app?

Link to comment
Share on other sites

Can anybody confirm the old field test trick for dBm meter instead of bars (now dots) still works in ios 7? I can't get it to work anymore.

 

When I hit the power button, whilst in Field Test mode, then hold the home button to close the FT app, it just resets the app and doesn't close to the home screen. Thus, not allowing me to keep the dBm meter, which reverts back to the dots.

 

Is there another procedure now in ios 7, to force-close an app?

Just tried it out. The old method still works for me.

Link to comment
Share on other sites

If you guys run into problems with the network on iOS 7, I just got off the phone with a very nice rep who suggested running the PRL update ##update#, then if you're still having trouble, wiping the network settings via ##clear#.

Link to comment
Share on other sites

If you guys run into problems with the network on iOS 7, I just got off the phone with a very nice rep who suggested running the PRL update ##update#, then if you're still having trouble, wiping the network settings via ##clear#.

PRL update and reset network settings are standard, first level attempts to fix issues like you're having. I just quoted you in the other iPhone thread, but has your issue been fixed by using those methods? If not, call them back and make sure they have the proper ICCID activated on your account (ICCID can be found at Settings - General - About).

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
    • So how does this whole direct to satellite thing fit in with the way it works now? Carriers spend billions for licenses for specific areas. So now T-Mobile can offer service direct to customers without having a Terrestrial license first?
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...