Latest iPad update

The_Unbeliever

Honorary Master
Joined
Apr 19, 2005
Messages
103,193
Reaction score
10,233
Location
Nkaaaaandla
Did update my iPad software beginning this week.

Gonna roll back because this new update chomps battery life :(

Have to charge more frequently, and I can see that it depletes quicker overnight.
 
Isn't there something in the tips section about rollback being possible by hacking something?
 
iOS 5.1? For what it's worth - I haven't picked up any problems...
 
Roll back would only be possible on an iPad 1 that has been jail broken and had its shsh blobs saved.
 
Did update my iPad software beginning this week.

Gonna roll back because this new update chomps battery life :(

Have to charge more frequently, and I can see that it depletes quicker overnight.
I did get a sense that battery life took a small hit recently but wondered if I was imagining it.

Sorry but rolling back isn't going to be possible unless you prepared for it before you updated. :o
 
My iPad was still running 4.3.0 when I received it. Updated to 5.1 first thing and personally find it an improvement overall.
 
Just to confirm you cannot do any rollbacks re the baseband was updated in this release i.e. making it incompatible with anything lower.

Also this release fixes battery issues, and does create them, have been testing it for > 4 months... check your settings post update for changes possibly from a restore of a backup that had settings you disabled at a point.
 
[)roi(];8021724 said:
Just to confirm you cannot do any rollbacks re the baseband was updated in this release i.e. making it incompatible with anything lower.

Also this release fixes battery issues, and does create them, have been testing it for > 4 months... check your settings post update for changes possibly from a restore of a backup that had settings you disabled at a point.

I think it's more a case of Apple not signing off on 5.0.1 than baseband related. If shsh blobs are saved you can use iFaith to stitch together an IPSW and restore to 5.0.1 (or any firmware version for which you have blobs saved). Excludes A5 devices.

For me the battery drainage issues pertain to apps suspended and/or running in the background. There different levels of "suspension". iPod and Tunein Pro would be examples of apps running in the background and not suspended which would result in battery drainage.

Then Whatsapp for example, suspended in the background drains battery where one could close Whatsapp altogether and still receive push notifications without it being a drain on the battery. Leave your phone in standby overnight with Whatsapp "suspended" in the background will result in 5-7% battery drain as well as inflating your usage figures. Close it and you'll lose 1-2% over night.

EDIT: Not entirely sure on the relationship between baseband and jailbreak but afaik the baseband version is immaterial on unlocked devices.
 
Last edited:
Jailbroken 4s running 5.0.1

14223395.jpg
 
I think it's more a case of Apple not signing off on 5.0.1 than baseband related. If shsh blobs are saved you can use iFaith to stitch together an IPSW and restore to 5.0.1 (or any firmware version for which you have blobs saved). Excludes A5 devices.

For me the battery drainage issues pertain to apps suspended and/or running in the background. There different levels of "suspension". iPod and Tunein Pro would be examples of apps running in the background and not suspended which would result in battery drainage.

Then Whatsapp for example, suspended in the background drains battery where one could close Whatsapp altogether and still receive push notifications without it being a drain on the battery. Leave your phone in standby overnight with Whatsapp "suspended" in the background will result in 5-7% battery drain as well as inflating your usage figures. Close it and you'll lose 1-2% over night.

EDIT: Not entirely sure on the relationship between baseband and jailbreak but afaik the baseband version is immaterial on unlocked devices.

Sorry it's is the baseband, I wanted to roll back during beta testing to reproduce a bug for Apple, their engineers said this was not possible re baseband upgrade incompatible with older versions. Nothing to do with signing. I have a copy of their email to me if you need physical proof btw (can only PM re dev license prevents me from posting onto public forums)

I.e. until JB's are certified properly for 5.1 do not upgrade, you can't go back.
 
Last edited:
My mistake for neglecting to specify differences re new and older kit.

1st far too techy for most, basically the package mixes an older baseband upgrade with the downgrade package (yes you right it works, but if JB is important rather avoid 5.1 -- there is no real benefit of 5.1 for the older kit anyway)

2nd A5 chips have no solution (so most of the new iPad 2 and iPhone 4S people are screwed if you upgraded, again if JB is important for you, then wait for the 5.1 JB)

It's quite possible that the JB guys could offer a similar baseband downgrade for the A5...

The issue though is that the 5.01 A5 baseband was so buggy, hence the baseband change in 5.1 to fix the issues --

for example : No sim, signal drop outs, dodgy wifi, ...

Considering this, why would anyone want to downgrade the A5 baseband, as this is only going to introduce crap -- IMO the JB team will focus on a solution for 5.1 and not bother with a reversal solution as it makes no sense.
 
Last edited:
It was not the update, but a zombie thread running amok.

Switching the ipad off and on again resolved the issue.

I'm a happy camper once more.
 
Top
Sign up to the MyBroadband newsletter
X