Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Solved the battery draining issue

JB with LR on 4.1, battery life is excellent (no change from stock), haven't messed around with MobileSubstrate or anything. Have SBS, TetherMe, BiteSMS, Lock Calendar, and Calendar Pro4.
 
Gavbo said:
Cheers, I think I've done it, there were bits information everywhere ...

Here is what I did:

1)Download - 3209 from: http://apt.saurik.com/debs/
2)Download - Diskaid for pc/mac
3)From Diskaid Drop 3209.deb to var/mobile/media/downloads/
4)Install ifile from Cydia
5)From ifile find 3209.deb and open it with installer
6)Reboot
Click to expand...
Bada-bing. Thanks man.
 
I downgraded to 3209 and I didn't see any difference with my battery life. In fact it made it even worst. At first, It started out just fine when I'm not using my phone. Once I started using it... Safari, texting, etc., I started to see the battery percentage decrease a percent every few minutes or so.
 
Battery was terrible for me. Downgraded to 3209 and looks to be back to excellent.

Bunch of mixed reviews. Bizarre.
 
i've been having battery issues with 4.1. not sure what is causing it though. i've had the exact same thing on 4.0.1 where it would drain by 1% every 5 or so minutes that the phone was on. ended up reinstalling everything, and it worked fine. i'm currently waiting for pwnage tool (hoping it comes out tomorrow) to help remedy this problem, because i'm not really into limera1n.
 
happy!

I am happy to report that battery condition got way better with 4.1 JB with LR. :)
 
After I JB'ed my Iphone 4 4.1 with limera1n I experienced a much shorter battery life. This was not due to the added usage on the phone, because simply leaving it on standby drained the battery about twice as fast as before. No matter how I used it, the battery went low the same night or the next morning.

Now, when I downgraded my MobileSubstrate to 3209, everything seems to be back to normal. Since the last charge I've used it for 3h20m and left it on standby for 1d10h while the battery is still at 66%.

Worked like a charm for me :)
 
sidewinder said:
If you folks want to know when the next new version of Mobile Substrate is available but don't want to see version 0.9.3228-1 in the "Upgrade" list, you will want to make a change in this file:

/private/var/lib/dpkg/status

In this file, find the line that reads:

Version: 0.9.3209-1

Change it to:

Version: 0.9.3228-1

This will make apt (Cydia) think you have 0.9.3228-1 installed. When a newer version is released you will have the option of installing it.


S-
Click to expand...

thanks for this Sidewinder. now i can upgrade and install other packages without worrying about updating my mobile substrate
 
strosz said:
After I JB'ed my Iphone 4 4.1 with limera1n I experienced a much shorter battery life. This was not due to the added usage on the phone, because simply leaving it on standby drained the battery about twice as fast as before. No matter how I used it, the battery went low the same night or the next morning.

Now, when I downgraded my MobileSubstrate to 3209, everything seems to be back to normal. Since the last charge I've used it for 3h20m and left it on standby for 1d10h while the battery is still at 66%.

Worked like a charm for me :)
Click to expand...

i was having the same exact issue with the same exact circumstances. it was my standby that was killing my battery. 3209 did the fix for me. now when the phone is on standby, it doesnt go down at all.
 
How is this thread still going after this?




saurik said:
A) Thank you for not only telling me, but providing a link to this forum. Most users simply talk to each other, and do not report issues.

B) However, this thread is not providing any concrete numbers, or any indication of testing methodology. Meanwhile, there is disagreement among users as to what version is even causing the problem.

Let me be clear about this: MobileSubstrate doesn't actually /do/ anything. If you install just it, and you let your phone then sit there not doing anything, it will /never/ use any CPU, ever. When a program starts up it is injected into its process space, it iterates a folder to see if it should inject anything else, and that's it: if there is nothing in that folder then its involvement in that process is entirely done.

This regime is so thoroughly enforced that the engine it comes with for letting extensions modify code is actually bundled separately, and will not end up in any processes unless one of the extensions actually needs it and requests it.

It's even better than this, though: MobileSubstrate only even loaded anything at all in user space on the primary CPU. Put differently, it only affects normal boring applications. This entire CPU is simply put to sleep when the phone is on standby, and is only woken up occasionally for timers, like an alarm or a calendar event.

I have just now verified that this is the behavior I'm seeing on my device: the entire night my phone was asleep, except at 3am when it woke up to do this "provisioning profile janitor" task that Apple apparently thinks is important enough to do every day at 3am, and which I had never heard of before and am now incredibly curious about the purpose of ;P.

Therefore, it is very difficult to understand how MobileSubstrate could possibly cause whatever issue you feel you are experiencing.

Meanwhile, things people really care about, things like battery life, memory usage, and signal strength, are very difficult to measure. The reason for this is that devices that are this complex use these resources in difficult ways, and they aren't things that you can directly just count.

Like, you can't use the battery percentage indicator to do this, as there is a /large/ amount of complex math that is going on just to pretend that it has any clue how much battery you have.

Example: if you leave it charging while it is at 100%, it typically will keep charging for quite a while, as it doesn't really know it is charged fully, and will continue to trickle charge as it thinks is safe. Then, when it starts discharging, its knowledge of how charged the battery /may/ have updated, allowing it to start decreasing the battery life. However, it also may have not: it depends on how many times it has seen itself in this state.

Then there are issues that simply rebooting the phone is going to cause major changes for a lot of users. As the device is used for a while, memory in processes starts getting fragmented, which leads it to page more and more. You can restart SpringBoard, which helps some, but you really need to reboot to totally fix the problem.

For most users, the only time they reboot is when they upgrade or downgrade MobileSubstrate. Therefore, users who believe "man, my battery performance really sucks" go and do something, and then are like "wow, this helped a lot, thanks!". Unless you switch back and forth multiple times, performing a careful test each time, the data is therefore totally worthless.

Meanwhile, I happen to know that planetbeing has been doing extensive tests regarding the battery usage of ultrasn0w, as he became paranoid that he was doing something weird with the debug serial port after receiving a number of comments like this. As far as I understand, these tests have shown "no drain" (whether you are using ultrasn0w 1.0 or 1.1, btw), and as ultrasn0w uses MobileSubstrate, I can infer.

Finally, there are also comments here that make it sound like jailbreaking itself is an expected battery drain, and that downgrading MobileSubstrate is bringing users "almost" back to where they had been before jailbreaking. Jailbreaking literally changes a few bytes in the kernel, and what it does is actually /bypasses/ code; if anything, if we could measure battery life effectively, what we'd find is that jailbroken phones get infinitesimally /better/ battery life than non-jailbroken phones.

So, please: if you would like to report a battery drain issue in something, I really need you to provide your testing protocol, so we can actually analyze it and determine if it is a true cause of concern or not. When I did similar things for people claiming memory usage issues with WinterBoard, I found that there were serious issues in the "common sense" way people were trying to measure that, and was able to elucidate some the issues.
Click to expand...
 
because it's actually an issue. we're not just spurting out paranoia here. the standby is killing the battery almost as fast as active non-internet use.

if it is from an application USING mobilsubstrate, such as sbsettings, then downgrading the mobilesubstrate still FIXES the issue for many of us.
 
this is funah said:
because it's actually an issue. we're not just spurting out paranoia here. the standby is killing the battery almost as fast as active non-internet use.

if it is from an application USING mobilsubstrate, such as sbsettings, then downgrading the mobilesubstrate still FIXES the issue for many of us.
Click to expand...

That is exactly what you're doing. Spurting paranoia. An application, such as sbsettings, isn't USING MS. It uses it to start not to run. Two completely different processes. My car needs it's starter to start but if I'm getting crap gas mileage I'm not going to assume it's the starter's fault. I'm sure you'll disagree and yeah you probably know more then Saurik when it come to MS.
 
TMar said:
That is exactly what you're doing. Spurting paranoia. An application, such as sbsettings, isn't USING MS. It uses it to start not to run. Two completely different processes. My car needs it's starter to start but if I'm getting crap gas mileage I'm not going to assume it's the starter's fault. I'm sure you'll disagree and yeah you probably know more then Saurik when it come to MS.
Click to expand...

so, what IS the deal? frustrating watching my battery drain; NOT that i would give up my JB for better battery life. but some people SWEAR the MS downgrade helps...
 
fisherking said:
so, what IS the deal? frustrating watching my battery drain; NOT that i would give up my JB for better battery life. but some people SWEAR the MS downgrade helps...
Click to expand...

I understand what your getting at. But I did the downgrade of MS back when I was on 4.0.1, as I was having drain issues as well and I was desperate for a fix too. But it did nothing to help it for me, the issue likely lied in the items I installed and just a fresh iOS install. And while I understand, that's my experience; the same could be said about the others in this topic.
In the end the real fix for me was the 4.1 update, and completely allowing my phone to drain and then allowing it to charge untouched over night.
 
TMar said:
That is exactly what you're doing. Spurting paranoia. An application, such as sbsettings, isn't USING MS. It uses it to start not to run. Two completely different processes. My car needs it's starter to start but if I'm getting crap gas mileage I'm not going to assume it's the starter's fault. I'm sure you'll disagree and yeah you probably know more then Saurik when it come to MS.
Click to expand...

im not saying i know more than saurik :) ... you're trying to get me riled up.

im also not claiming i know all that much other than ive used the 3228 MS for weeks, and my battery went from 100% to 90% ON STANDBY in about an hour, every day.

now that i've downgraded for the second time to 3209 MS, it's taken more than 3 hours to hit 90% on standby even with occasional short use.

perhaps one of the applications is using the startup much more inefficiently in 3228 MS, and is somehow limited in 3209. i dont know for sure, all i know is that my battery is a helluvalot better since i've downgraded my MS. that's all i know, and since saurik cant find the problem either, it is either a collective paranoia or a problem one man hasnt yet found.
 
another strange thing i've noticed:

since downgrading my MS to 3209, "Time since last full charge" has been calculating again.

for example: "Usage - 28mins; Standby 2hrs,24mins" Battery - 95%

when i was on 3228, it never calculated this before. maybe that has something to do with it.
 
this is funah said:
im not saying i know more than saurik :) ... you're trying to get me riled up.

im also not claiming i know all that much other than ive used the 3228 MS for weeks, and my battery went from 100% to 90% ON STANDBY in about an hour, every day.

now that i've downgraded for the second time to 3209 MS, it's taken more than 3 hours to hit 90% on standby even with occasional short use.

perhaps one of the applications is using the startup much more inefficiently in 3228 MS, and is somehow limited in 3209. i dont know for sure, all i know is that my battery is a helluvalot better since i've downgraded my MS. that's all i know, and since saurik cant find the problem either, it is either a collective paranoia or a problem one man hasnt yet found.
Click to expand...

Try upgrading back to the latest mobile substrate and see if the battery drain is there. It's a placebo effect.

this is funah said:
another strange thing i've noticed:

since downgrading my MS to 3209, "Time since last full charge" has been calculating again.

for example: "Usage - 28mins; Standby 2hrs,24mins" Battery - 95%

when i was on 3228, it never calculated this before. maybe that has something to do with it.
Click to expand...

That's always calculated, has nothing to do with mobilesubstrate. It disappears if you respring.
 
moussekateer said:
Try upgrading back to the latest mobile substrate and see if the battery drain is there. It's a placebo effect.
Click to expand...

It's most definitely not a placebo effect for me at least. Downgrading the MS to 3209 has at least doubled the battery life on my i4 4.1.

I always use my phone without 3G, no bluetooth and regularly shut down all background apps; despite all these measures the battery almost completely drained in a day of light usage. I've been observing the battery performance carefully for weeks pre-JB and know what to expect from the battery. The truth is that after limera1n the battery life was a lot worse.

I don't know what aspect of the downgrade it is that causes this improvement, but the fact is that downgrading made my battery life return to what I experienced pre-JB.

EDIT: I'm now at 5h8m usage and 2d12h standby on a 45% battery level. It didn't achieve anything near this battery performance before the downgrade. The battery would certainly have been dead at this point.
 
kalirob99 said:
I understand what your getting at. But I did the downgrade of MS back when I was on 4.0.1, as I was having drain issues as well and I was desperate for a fix too. But it did nothing to help it for me, the issue likely lied in the items I installed and just a fresh iOS install. And while I understand, that's my experience; the same could be said about the others in this topic.
In the end the real fix for me was the 4.1 update, and completely allowing my phone to drain and then allowing it to charge untouched over night.
Click to expand...



gonna try this first (after all, i've done this with all my mac laptops...and there have been many...).
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back