• Content count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About D3@TH

  • Rank

Profile Information

  • Gender

Recent Profile Visitors

13.8k profile views
  1. DB

    It's ok
  2. I am works good battery life is better then my iPod 4g on 5.0.1
  3. DB

    1st thing is 1st This is not a support Thread if you want support click here
  4. 3Gs go with the medium to be on the safe side if everything still runs smoothly after a few days then replace with the ultra
  5. DB

    Try searching this topic maybe someone had the same problem and there's an answer on that topic
  6. Makes your battery last longer since there was a battery drainage problem in iOS 5.0.1
  7. Orginial Post 5.1 .plist file Needed Are you a heavy iPhone user and always struggling with saving power on your device? Here’s something that you can try on your jailbroken iOS 5.0 or iOS 5.0.1. Just like a computer’s operating system, iOS also comes with a power management system that adjusts how much your device uses power. By editing the com.apple.SystemPowerProfileDefaults.plist file, you may be able to squeeze more juice out of your battery. I left my iPhone overnight at 85% battery power with WiFi, 3G and GPS turned on. By 8am the next day, it only consumed 2% of power. Not too bad at all. Steps: 1. Download DiskAid or i-FunBox. 2. Download one of these power profiles: Ultra power saving profile ultra_power_saving_mode.zip Medium power saving profile medium_power_saving_mode.zip Default power profile defaul_power_saving_mode.zip 3. Launch DiskAid or i-FunBox and browse to the following folder location: /System/Library/CoreServices/powerd.bundle/ 4. Replace or overwrite the com.apple.SystemPowerProfileDefaults.plist with the one you just downloaded in step 2. 5. Reboot your device and you’re done! If you like to revert to default power profile, simply use the default power profile plist file. I haven’t tried this on iOS 4.x yet but if you would like to try (at your own risk), the .pfile file is located at the following folder: /System/Library/SystemConfiguration/PowerManagement.bundle Difference between plists: Plist Difference CREDITS: Atlasadam-iOS 5.1 original .plist ~CrAcKzZZ-Original thread, conception of replacing .plist Karan_98- 5.1 Extra .plist Rev0l2ti0n-Ultra-Battery-Saver .plist rl421403-Medium-Batteery-Saver.plist
  8. Thanks
  9. http://youtu.be/NKNSago3jwk
  10. I have a iPhone 4s 5.0.1 every since I added that stupid battery plist that helps make your battery last longer when I go to open a app it crashes instantly. Is there a way to fix this since I can't restore and rejailbreak?
  11. Does anyone on iPhone 4s with firmware 5.0.1 have the original plist I forgot to back mine up so everytime I open a app no it instantly crashes?
  12. How would I write that where it backups the respring@2x.png into a folder called Backup and restore it when my theme gets removed?
  13. I need help getting this script to work: #!/bin/bash OUTPUT=/private/var/mobile/Library/SBSettings/respring@2x.tgz BUDIR="/private/var/mobile/Library/SBSettings/Backup/" echo "Starting backup of directory $BUDIR to file $OUTPUT" tar -cZf $OUTPUT $BUDIR if [ $? == 0 ]; then echo "respring@2x.png:" echo $OUTPUT echo "was created as a backup for:" echo $BUDIR fi I want it to backup the respring@2x.png for SBSettings when my theme gets installed and when it gets removed it will put the original respring@2x.png back
  14. Introduction: While this tutorial is in the Linux section it applies to all *nix systems with a BASH Terminal. I'm not going to go into detail about what BASH is as to explain it requires a lot of background knowledge, instead I shall point you to this piece of literature - it'll provide you with a good footing and foundation. A BASH script is really just a list of commands for the shell to run. This is in order to simplify long-winded operations that may be done often. Right onto the script: What does it do? This script backs-up a directory you specify and stores it in another directory (which you specify) as a .tgz file. I shall go through the script section by section and explain each 'bit' of code as we go along: The Code: Let's start the script: 1.#!/bin/bash That's the first line of the bash script, all shell scripts have to start with #! The "/bin/bash" is just defining which shell to use with the script. Now we'll define the directory where want to store the backup and format the name of the .tgz file we want to create: 1.OUTPUT=/some/directory/to/store/the/backup_$(date +%Y%m%d).tgz The date is added to the filename: that way you can have different backups from different dates stored in the folder - the date format is: YYYYMMDD "OUTPUT" is just the variable name we're giving to the backup-storage directory. Now we'll define the directory we want to backup: 1.BUDIR="/some/directory/to/backup/" "BUDIR" is the variable name given to the directory we want to backup. Now we'll display a message to the user that we're going to initiate the backup: 1.echo "Starting backup of directory $BUDIR to file $OUTPUT" Notice the use of "$BUDIR" and "$OUTPUT" - these are the variables being displayed in the message we print in the terminal. Now we need to actually start the backup: 1.tar -cZf $OUTPUT $BUDIR Again, notice the use of the variables - as the format of the "tar" command is: "tar [flags] [destination] [source]" all the variables are doing is filling in the places of the destination and source files / directories. Now after this we could simply display a message saying the script is done - but what if it hasn't backed up for some reason? What if there was an error? We'll deal with this on the next page by displaying a message if an error occurred during the process. To do this we'll make use of a special variable in the shell - this is the "$?" variable which displays the status of the last program run. POSIX-compliant programs all return "0" if they run successfully - so we can simply check if the variable "$?" is equal to 0. If it is we can display a confirmation message, if it isn't we can display an error message. How will we do this? With an "if" statement - that's right, theyre that good that even the shell can make use of them (the shell can make use of a lot of things): Right, the semantics is similar to most coding languages, but the syntax is different to most you'll probably know: 1.if [ $? == 0 ]; then That starts our "if" loop - now we need something to do if it evaluates to true: 1.echo "The file:" 2.echo $OUTPUT 3.echo "was created as a backup for:" 4.echo $BUDIR What this does is: Displays the text "The file:" Displays the output directory and file (on a new line) Displays the text "was created as a backup for:" (on a new line) Displays the directory we backed up (on a new line) So that's what happens if the backup completed successfully. So what if it didn't? We use an "else" statement: 1.else Now something to do if the backup didn't complete successfully: 1.echo "There was a problem creating:" 2.echo $OUTPUT 3.echo "as a backup for:" 4.echo $BUDIR What this does is: Displays the text "There was a problem creating:" Displays the output directory and file (on a new line) Displays the text "as a backup for:" (on a new line) Displays the directory we backed up (on a new line) Now we need to close the "if" / "else" statement: 1.fi And that's the completed script. On the next page is the full script with comments added. 01.#!/bin/bash 02.####################################################### 03.## Simple backup script.. 04.## Created by Matthew Brunt: (openblue555@gmail.com) 05.## Licensed under GNU GPL v3 or later, at your option. 06.## http://www.gnu.org/licenses/gpl.html 07.####################################################### 08. 09.#Defines our output file 10.OUTPUT=/some/directory/to/store/the/backup_$(date +%Y%m%d).tgz 11. 12.#Defines our directory to backup 13.BUDIR="/some/directory/to/backup/" 14. 15.#Display message about starting the backup 16.echo "Starting backup of directory $BUDIR to file $OUTPUT" 17. 18.#Start the backup 19.tar -cZf $OUTPUT $BUDIR 20. 21.#Checking the status of the last process: 22.if [ $? == 0 ]; then 23.#Display confirmation message 24.echo "The file:" 25.echo $OUTPUT 26.echo "was created as a backup for:" 27.echo $BUDIR 28.else 29.#Display error message message 30.echo "There was a problem creating:" 31.echo $OUTPUT 32.echo "as a backup for:" 33.echo $BUDIR 34.fi And there we have it, your script - run it as a cron job each day and you'll have nice tidy backups
  15. I tried searching google and my iPhone and couldn't figure anything out