iOS 5.0 Speed Up Your iOS Device by Removing Launch Daemons & Background Processes

Discussion in 'iOS Jailbreak & Cydia' started by xXrkidXx, Dec 22, 2011.

  1. Pioneer New Member

    Member Since:
    Mar 2, 2012
    Message Count:
    3
    Device:
    iPhone 3GS (Black)
    ok, thanks
  2. aerozolic Member

    Member Since:
    Sep 25, 2010
    Message Count:
    86
    Device:
    iPhone 5 (White)
    Still haven't gotten an answer for this one.
  3. xXrkidXx Well-Known Member

    Member Since:
    Mar 27, 2009
    Message Count:
    4,615
    Device:
    iPhone 5 (Black)
    I didn't know you were still looking; Yea that's the same thing. I must have forgot to add the "d" in the OP. Sorry about that.
  4. aerozolic Member

    Member Since:
    Sep 25, 2010
    Message Count:
    86
    Device:
    iPhone 5 (White)
    Thanks! :)
  5. pandaa Banned

    Member Since:
    Nov 7, 2011
    Message Count:
    7,438
    Device:
    4G iPod touch
    Of course, anytime. :)
  6. RedFourFive New Member

    Member Since:
    Mar 19, 2012
    Message Count:
    9
    Device:
    4G iPod touch
    deleted the bolded ones but skipped the powerd.plist also works ;)
    which one do you prefer?
  7. pandaa Banned

    Member Since:
    Nov 7, 2011
    Message Count:
    7,438
    Device:
    4G iPod touch
    What do you mean, which one do I prefer?
  8. deprecated New Member

    Member Since:
    Mar 24, 2012
    Message Count:
    2
    Device:
    iPhone 4 (Black)
    Disabling com.apple.powerd.plist is a pretty bad idea. I dug through the plist and found nothing offensive, and couldn't find any evidence to support the claim that the CPU is being throttled during a drain. Much like all modern devices, the powerd plist calls a daemon that manages power profiles for appropriate scaling and handling. I ran 20 rounds of Linpack with com.apple.powerd.plist in place and got an average of 33.80 Mflops/s, and with com.apple.powerd.plist removed I get 33.60 Mflops/s. Purposely draining the battery with music/video playback/flashlight/high screen brightness then repeating the experiment shows no variation in results.

    Furthermore, disabling this daemon DOES have very serious implications and side effects. Disabling this daemon prevents applications from polling the battery level, thus will represent a 0% battery. Also, I have gone through two battery charge cycles to test the following hypothesis: disabling com.apple.powerd.plist has substantial impact on my battery life. 4 resprings and 2 reboots after a full charge (with wifi on/bluetooth off), my battery was completely stone dead. Now whether or not it was actually dead, or the OS was simply reporting it as dead because of powerd not existing is up for debate. I recharged again, copied over my backup of com.apple.powerd.plist, and have not experienced any of the problems mentioned.

    Hope this helps.
  9. pandaa Banned

    Member Since:
    Nov 7, 2011
    Message Count:
    7,438
    Device:
    4G iPod touch
    That's why we were advised not to disable it... xD
    But thanks for the testing. BTW, you cannot find out what the executable does, just by looking at the .plist. For that, you need to use a disassembler of the actual executable the daemon points to.
  10. deprecated New Member

    Member Since:
    Mar 24, 2012
    Message Count:
    2
    Device:
    iPhone 4 (Black)
    Yeah, I figured it was probably noted somewhere in this thread, but I was going by the first page. Sorry :) Also, I poked around some dev notes re: powerd itself, and that's how I determined. Either way, just figured I'd contribute. Cheers!