Prepare Your Device For The iOS 6.1 Evad3rs Untethered Jailbreak

We now know that the iOS 6.1 Untethered Jailbreak from the Evad3rs will becompatible with all iOS devices that can run iOS 6.1, besides the 3rd generation Apple TV, and we also know when theEvad3rs Jailbreak will likely be released. With all of this information known, it is now time to start preparing for the release of the iOS 6.1 Untethered Jailbreak.
You might be thinking to yourself, well this will be easy! I simply update over-the-air to iOS 6.1 and wait for the Evad3rs to release the Untethered Jailbreak. Unfortunately this isn’t the case and if you update over-the-air you will likely run into some issues. There is a few things that should be done to prepare for the iOS 6.1 Untethered Jailbreak and in this article I will go through them.
First things first you want to make sure that your device is covered by the iOS 6.1 Untethered Jailbreak. This shouldn’t be too hard to determine and we even outlined the compatibility of the Evad3rs Untethered Jailbreak in a previous article, but in case you missed it, here it is one more time. Essentially the only device not supported is the 3rd generation Apple TV.

iPhone 3GS
iPhone 4
iPhone 4S
iPhone 5
iPod Touch 4th Generation
iPod Touch 5th Generation
iPad 2
iPad with Retina Display 3rd and 4th Generation
iPad Mini
2nd Generation Apple TV

When you have ensured that your device is compatible with the iOS 6.1 Untethered Jailbreak you will indeed want to update to iOS 6.1 right away to avoid doing it at the last minute. It is important to keep in mind that you cannot just update to iOS 6.1 over-the-air. As MuscleNerd has explained over Twitter, there are a few reasons you don’t want to do this, which include having different SHSH blobs than a normal restore. For the Evad3rs to support over-the-air updates it would be double the work, which may happen in the future, but for now we strongly suggest you update through iTunes instead. If you have already updated over-the-air thenunfortunately you will need to restore your device to iOS 6.1. As pointed out by Benlego65 in the comments, instead of restoring through iTunes you can SHIFT + Update on Windows or Option + Update on Mac OS X. If this changes we will let you know, but updating to iOS 6.1 through iTunes NOT over-the-air at this time is a must.

Sunday is Funday!!! (Evad3rs hints to release the jailbreak on this sunday) YAY!!

 Apple software hackers unveiled a website late Wednesday where the latest untethered jailbreak is expected to be released soon.

Well folks it’s official! The iOS 6 Untethered Jailbreak from the Evad3rshas a name — Evasi0n.

Pod2G sent out a tweet not long ago stating that the website was online and to check it regularly for updates. We learned earlier this week that the iOS 6 Untethered Jailbreak was fully functioning with the iOS 6.1 firmware update Apple pushed on Monday and thus the Evad3rs announced it wouldn’t be long before we would see a public release of the Jailbreak. In fact, MuscelNerd tweeted that it could be as early as this Sunday. It is important to keep in mind however, this is just an estimation and it could be released later or even earlier depending on how private beta testing goes. 

According to the official website the Evasi0n Jailbreaking tool will take 5 minutes of your time, requires a computer running Windows, Mac OS X or Linux and a compatible iPhone, iPod Touch or iPad. You can take a look at the requirements in a bullet form list below…

• 5 minutes of your time!
• A computer, running Windows (XP minimum), Mac OS X (10.5 minimum) or Linux (x86 / x86_64)
• An iPhone, iPad or iPod running iOS 6.0 through 6.1 (you may check in Settings / General / About => Version)
• A USB cable to connect the device to the computer

Right now the Evad3rs are in the middle of finishing the GUI (graphical user interface) for the tool, once this is complete private beta testing will start and then it will be made public. The individuals working on the iOS 6 Untethered Jailbreak include MuscleNerd, Planetbeing, Pod2G and Pimskeks. Phoenixdev, Surenix, Hanéne Samara, the Chronic Dev-Team and the iPhone Dev-Team also contributed to the Jailbreak. Apparently even Kiki the cat was involved.

Delete permanently facebook account

If you deactivate your account, your timeline disappears from the Facebook service immediately. People on Facebook won't be able to search for you, though some info, like messages you sent, may still be visible to others. We also save your timeline information (ex: friends, photos, interests, etc.) in case you want to come back.

If you don't think you'll use Facebook again, you can request to have your account permanently deleted. Please keep in mind that you won't be able to reactivate your account or retrieve any of the content or information you've added. Before you do this, you may want to download a copy of your info from Facebook. Then, if you'd like your account permanently deleted with no option for recovery, log in to your account and fill out this form.


If you can't log in to your account, you'll need to reset your password first. To do this, go to www.facebook.com and click the Forgot your password? link below the password field. Once you’ve followed the instructions to reset your password and can log into your account, you can deactivate or delete your account using the steps outlined above.


Source :- facebook.com

How To Make Boot Animations for an android phone

Hi guys!
Today, I'm going to teach you how to make your own boot animations. Please read this thread carefully to the end, in order to succeed in making your boot animation.

Requirements:
-A photo-editing program (GIMP and Photoshop are the best), which can save pictures in .png format
-A text editor (everyone has that)
-An archive-managing program (Power Archiver, WinZip), that is capable of making .zip archives

Tutorial:
1. Create part0 and part1 folders (in this folders, the frames of the boot animation are stored. Usually, there are only 2 parts in a boot animation, but you can add as many as you want. The frames in the part0 folder are usually repeated once, and the frames in part1 folder are usually looped several times, or infinite.)
2. Draw every frame of your boot animation manually (save every frame as you do it. Save the first one as 10001.png, the second one as 10002.png, and so on. Save them in the part0 and part1 folders - the frames in part0 folder will be showed only once, and the frames in part1 folder will be looped. But, you can change that if you want. Changing the looping property will be discussed in the following steps. WARNING: ALWAYS SAVE THE FRAMES IN .PNG OR .JPG FORMAT!)
3. Make a desc.txt file in the directory where the part0 and part1 folders are and edit it as following:

Quote:

320 480 30 p 1 0 part0 p 0 0 part1

(The numbers 320 and 480 is the resolution of your boot animation. Change them as you want. The number 30 means the speed of the animation. Speed set to 30 is good for me. Then, the "p 1 0 part0" property means that the frames in part0 folder will be repeated once - you point that with the first number in the "p 1 0 part0" property, which in this case is 1. The second number is the delay between loops, and it's expressed in milliseconds (1000ms = 1s). I've set it to 0 because I don't want to be any delay between my loops (p 1 0 part0). And last, but not least, you set the folder with the folder name - in this case is part0. Then, you type the property for the part1 folder - that's "p 0 0 part1". The first "0" means that the folder will be looping infinite times, the second "0" means there's no delay between loops, and then we set the folder to part1. Note: if you have more folders, you'll have to write properties for them too! WARNING: DON'T FORGET TO LEAVE AN EMPTY LINE AT THE END OF THE DESC.TXT FILE!)
4. Compress the folders and the desc.txt file in a zip file (WARNING: MAKE SURE YOUR COMPRESSION METHOD IS STORE! OTHERWISE, THE BOOT ANIMATION WON'T WORK!)
5. Open your new boot animation and check the folders, if there are Thumbs.db files. If there are Thumbs.db files in your boot animation, delete them from the archive.
6. Install your boot animation on your device with one of the following methods:

Quote:

Root Explorer method: 1. Rename your boot animation to bootanimation 2. Put it on your SD card 3. Open Root Explorer and copy bootanimation.zip to /system/media. This will replace the existing boot animation 4. Reboot your phone ADB method: 1. Make sure you have downloaded android sdk  2. Put android sdk in C:\ 3. Set the directory of command prompt to C:\android-sdk-windows\platform-tools. Click here for a video tutorial. 4. Rename your boot animation to bootanimation and put it in C:\android-sdk-windows\platform-tools 5. Open cmd 6. Type in order: -adb remount -adb push bootanimation.zip /system/media/bootanimation.zip -adb reboot

7. Enjoy your new boot animation!

How to add sound (all courtesy of colpophage)(UPDATED!!):

Quote:

1. Download this shell script: http://db.tt/NolFWEp  2. Place bootsnd.sh in /sdcard 3. Run terminal emulator, and execute the following: su cd /sdcard sh bootsnd.sh 4. Use a rooted file manager and navigate to /system/bin, and verify that there is now a file called bootsound there, and it has 777 (rwxrwxrwx) permissions. Modify the permissions to 777 if needed.  5. Place your desired sound file, renaming it android_audio.mp3, in /system/media. 5.1 For the original quietly brilliant sound, download: http://db.tt/Oy20ZqT (remember to rename it).  5.2 I now put custom boot animations into /system/media as well, and this is my favorite so far: http://db.tt/LMkqs3f (rename to just bootanimation.zip).  6. Reboot and enjoy.

Info About Batteries and Battery Power Saving Tricks

So after noticing how much of a difference people get in their battery lives, I've decided to do some research and make a guide-line that will give us all we need to know about properly using our batteries. First part is a general information and usage techniques for LIBs, second part is taken from Google materials on Android-powered devices (G1, Magic, Droid, Nexus One, etc).

Sources:

Wikipedia - http://en.wikipedia.org/wiki/Lithium-ion_battery
BatteryUniversity - http://www.batteryuniversity.com/parttwo-34.htm
Google IO Conference 2009 - http://www.youtube.com/watch?v=OUemfrKe65c
Electropaedia - http://www.mpoweruk.com/life.htm

General Lithium-Ion Battery (LIB) Usage:

1. • Discharging your LIB fully (or less than 2.4 Volt per cell) is bad for the battery. Every time you do that, it can be said that small part of your battery (some cells) dies (they forever lose their charge). Do not store your batteries depleted, there's a high chance they will die completely or will become very "weak".
2. • You cannot restore bad LIBs by overloading/heating/praying. You gotta go buy a new one. They DO degrade overtime, some cells naturally lose the ability to gain/give electricity.
3. • Although it is said that LIBs do not have memory, it's not entirely true. LIBs have gauges that monitor performance of cells, and if you do a lot of small charges, it won't let those gauges to monitor a full battery potential, causing an invalid indication of charge level. A complete charge/discharge should be made when battery capacity seems reduced, that will calibrate gauges and they will provide your phone with correct charge level status. A full charge/discharge cycle should be done every 30 (or so) partial charges.
4. • LIBs have a shelf-life. Do not buy them to store them. Use them early, use them often, they will die whether you use them or not. Do not buy LIBs to use them in 6 months/year/etc, buy them right before actually using them.
5. • LIBs have short lives (in comparison to NiCa batteries, etc). You should expect to buy a new battery in 2-3 years after being manufactured. It is caused by internal oxidation and there's nothing you can do to stop or prevent that.
6. • Worst LIB treatment is to keep it at 100% charge level at high temperature (think laptop/phone under direct sunlight, like car dashboard).
7. • Best LIB treatment, or LIBs "favorite" charge level - 40%. That's also the usual charge level you buy them with.
8. • LIBs don't like heat. For example, while always at 100%, typical LIB in a laptop, at temperatures of 25C (77F) will lose 20% (twenty percent!) of full capacity per year. That capacity loss is reduced to 6% (six percent) at 0C (32F), and increased to 35% loss at 40C (104F). So, keep them cool (LIBs like fridges), don't let your devices sit in the sun or overheat at charge. Also, keep in mind that while in use, battery will be significantly hotter than phone/outside environment
   
9. • LIBs like frequent partial charges/discharges more than they like full charges/discharges.

General Android power usage advice from google:

1. • Although this part is somewhat controversial, they do recommend having a complete, full FIRST charge to be made. If time allows, a preferred time for the first charge is 12 hours. This may have more to do with the OS than the battery.
2. • Battery on a Android device, in average, will last about a full day with normal use (some videos, mail, calls). That's what you should kind-of expect.
3. • Speaking in averages, "idling" 3G/EDGE connection (when phone is sleeping and no data is transferred through 3G), drains almost no energy. Just a little more than having 3G/EDGE radio off completely. So when no apps are using 3G, you don't need to keep it off.
   
4. • Same goes to WiFi connection - although it's on, if there is no data flowing through it, it uses almost no energy.
5. • At full throughput (100% data flow), EDGE is using more energy than 3G. In average, 3G is more energy-efficient than EDGE.
6. • WiFi is using more energy than 3G (when both are at 100% use), but since it transfers files much faster and then goes to "sleep", it's actually recommended to use WiFi whenever possible. Since it'll "sleep" more often than 3G, overall it will use much less battery than using 3G.
7. • Some bad apps or widgets can use android's "WakeLock", keeping CPU at 100%, screen always-on, or both. I myself have encountered such widget (I won't mention the name, it's in the market) that used a WakeLock to keep CPU spun-up at 100% all the time. That makes a huge impact on battery life. My advice - use a CPU profiling app to monitor the CPU - make sure that CPU slows down by itself when it's not used. So, beware of such widgets/apps. To check for CPU cycles, many recommend OSMonitor(free from market, install it, go to options, sort by "Load" in descending order. It'll give you "busiest" processes at the top). At rest you should be getting about 10-20% for OSMonitor itself, and 1-10% Android System. At rest, everything else should be 0-1%.
8. • Android slows down CPU when not in use by itself, as a built-in feature. Apps that throttle/change CPU frequency, are not necessarily needed.

All this info comes from those reputable resources I mentioned above, I didn't make any of it up.

Linear Programming I : Formulation and Graphic Solution