Most people don't yet know that many Android software leak all sorts of information to the internet with only scant user acknowledgement (basically what you accept when you install the app).
Due to this and the fact that there are already privacy information harvesting apps for Android on the marketplace - a team of security experts have created TaintDroid:
What is TaintDroid?
From the project's web page: "A realtime monitoring service called TaintDroid that precisely analyses how private information is obtained and released by applications "downloaded" to consumer phones."
From: http://appanalysis.org/index.html
How can I install TaintDroid?
As TaintDroid is currently compiled into the kernel, you cannot easily install it, but you have to cook your own kernel. Instructions (for Nexus 1) are available at the project web site: http://appanalysis.org/download.html
How does TaintDroid work?
Here's a video demonstrating how TaintDroid works once it is installed and configured:
http://appanalysis.org/demo/index.html
Why would you want to install this?
There can be many reasons for installint TaintDroid:
- You want to learn about privacy features and play with Android kernel
- As it is currently impossible to differentiate between innocent and sneaky Android apps based only on what access rights they request, you may want to dig in deeper
- You are worried about what apps are doing behind your back and you want to know which apps to uninstall
- You want to help create Android a more secure and privacy-protected platform, instead of the swiss cheese it currently is
What can you do?
As compiling kernels is mostly beyond the reach of mere mortals currently, consider cooking TaintDroid into your kernel, if you are cooking one yourself and offering it available for others to try and use.
Hopefully increased awareness and usage will bring this program eventually into other modders and perhaps even Google's attention and something more easily accessible is offered for the public at large.
BTW, I'm just a user, interested in getting TaintDroid on my own Galaxy S. I'm not affiliated with the research program, but I like what they are doing. This information is purely FYI.
+1 for the idea
Sent from my GT-I9000 using XDA App
+1
Since we cannot expect information gatherer Google to come up with a good privacy protection mechanism soon I think we are forced to take measures ourselves.
I also learned that several of my bought applications are constantly forcing me to enable synchronisation and/or 3G internet. They either randomly uninstall (Asphalt 5), their icons disappear (for example: Mini-squadron) or won't start, with (Schredder Chess) or without a message. Angry Birds Beta2 lite (free game) and Hungry Shark are 2 more examples. So much for an incentive to buy games...
It would be great if applications used a well-defined mechanism to check their validity on-line, and not have this sneaky, lingering attack from all sides to any privacy or battery consumption aware user.
I can not cook Kernels, but this is something i want to use.
Not that i am worried, but i dont know what apps are sending when you open them. Thats something i want to know!
I am sure i am not the only one.
+1
Yes please... This should be in all android phones... as a security option you could turn on!!!
Antonyjeweet said:
Not that i am worried, but i dont know what apps are sending when you open them. Thats something i want to know!
Click to expand...
Click to collapse
And do some of these applications only send stuff when you open them?
--
From a user perspective it currently is really difficult to judge applications that need to start at boot-up and deal with many facets of your computer (Launchers, tools combining lots of divers features).
Do you know some ROM where Taindroid is included?
I've posted in hardcore and laststufo kernel threads to ask if they could add it.
We just need more people wanting it so they think about adding it
exadeci said:
I've posted in hardcore and laststufo kernel threads to ask if they could add it.
We just need more people wanting it so they think about adding it
Click to expand...
Click to collapse
glad you did that
+1 support the idea. hope some of our hardworking kernel builders will add this in.
My concern is how much another real time service will affect battery life. For people trying to make the leanest, fastest kernel I'm not sure it's viable.
I have been wanting TaintDroid built into android by default since the day it was announced, but I really do not think google cares about this, so please, please ROM cookers out there (Maybe Doc?), lets add this into our galaxy S roms.
Well, this seems to work only on android 2.1
Make it so.
+1
Combined with walldroid (or other firewall) this could put back power into users hands. Would really love to see this inside hardcores kernel. Maybe as an option for the stable releases?
+1
This should be the next standard in aAndroid
idea about spoofidroid application
how about a program to spoof or make the phone send fake:
GPS location,
IMEI,
phone number,
simcard id,
etc... information to applications that ask without permission.
this way you can feed these application with information they want but without breaking your privacy. (both end sides are more than happy)
-----
nice option to have:
1) enable/disable auto generate different id every time.
2) allow list / ban list of application to have real or fake id.
3) enable/disable notify for application request.
-----
there are all ready applications that fake your simcard PLMN mobile network codes without the need of kernel rights, but you need to enable disable the flight mode to restore the default code.
===========
good luck to spoofidroid or similar applications.
Jumba said:
My concern is how much another real time service will affect battery life. For people trying to make the leanest, fastest kernel I'm not sure it's viable.
Click to expand...
Click to collapse
I hope there will be developers out there who prioritize privacy/security over speed/battery and storage usage.
I'm the project lead of the TaintDroid system. We are currently working on a few extensions of TaintDroid but unfortunately are short on engineering resources to port TaintDroid onto other systems than Nexus One that we originally developed. We'd greatly appreciate it if XDA developers would take on this effort! Many ongoing projects would hugely benefit from having easy-to-run TaintDroid ROM available for many different devices and upcoming Android systems let alone user benifit.
Thanks,
Jaeyeon
Research Scientist @ Intel Labs Seattle
Ettepetje said:
I also learned that several of my bought applications are constantly forcing me to enable synchronisation and/or 3G internet. They either randomly uninstall (Asphalt 5), their icons disappear (for example: Mini-squadron) or won't start, with (Schredder Chess) or without a message. Angry Birds Beta2 lite (free game) and Hungry Shark are 2 more examples. So much for an incentive to buy games...
Click to expand...
Click to collapse
beta2 lite? i think that was malware, make sure it came from rovio otherwise it's fake and you should delete it.
It's really scary to see with the lookout app how many apps can access to your imei, telephone number "Read Identity Info", can access your contacts, track your position, and can send out all this data.
Here a HTC Desire user, asking for some privacy.
Best regards!
Hello to all XDA developers and chefs
Before giving this idea i would like to introduce myself I'm a new programing student interested in the Java programing language, also interested in mobile programing. I've already tried searching for this idea and as far as my research went there has been none like this.
Here it goes
-Everyone know how much of a pain it is for several people to use the skinned versions of android on their phone (blur, sense, other), we all would like to get more stock android from our companies but it seems to become a unreachable dream. now many have said that they must find an workaround for this, yet no idea seems to become a reality....
now my idea consist in having to android packages on every phone from stock one package that will be installed for default and another package that the user may choose to install, the default package will come with a skin while the optional package will contain stock android, now the way to manage this two is via an application from witch the user by running it will decide to have stock rom or skinned.
Now this is the way I think this should work
-User opens the app
-App pops a warning to the user telling him its phone will be fully reseted
-The user accepts the consequences
-The app turns the phone into a recovery mode with a selection for witch package to recover from (for example return a #1 indicating that the user wants skins on his phone will install the package with the skin or a #2 to run a package with no skins at all)
why am I asking help from XDA? because of two things
-I currently don't know that much about programing
-I think XDA would be the best site for the idea to grow and become something significant
what are my plans with this idea? I'm currently writing an open letter to Google and the manufacturers to bring many options to the OS. I thought i would be a great idea not only to deliver this letter but to give the materials they could work on...
do I get anything if I help with developing such an idea?
I currently have no plans on taking credit or any remuneration of any kind from this "project" but I would clearly name those who made this idea possible, now if "bounties" where to come from this then you may earn them...
what are you asking me to do?
-Brainstorming, I would like to see how this idea gets refined.
-Development, when the idea is complete having many attempts to get the idea to work would be great.
-Testing and feedback, help the idea to work on as many devices as possible
-Support, when the protect gets completed i would like everyone to spread the voice. if its a great idea then it should be heard.
Thanks for your Time.
reserved.....
Cyanogen mod is basically stock android with a few mods and tweaks. If doesn't have all of the bloatware that skinned manufacturer roms have so its alot faster and I think stock android looks better than sense, etc.... Its been compiled for a wide range of phones.
K Dotty said:
Cyanogen mod is basically stock android with a few mods and tweaks. If doesn't have all of the bloatware that skinned manufacturer roms have so its alot faster and I think stock android looks better than sense, etc.... Its been compiled for a wide range of phones.
Click to expand...
Click to collapse
I know about the cynamogen mod have it on my pone,where I'm trying to go with this idea is that there might be other methods for the companies to deliver stuff to the end user and the dev. many know that for example with blur the phone does not work the same when it as blur removed, thats because the 'blur' its being integrated a lot with the OS and in some cases seems to be a pain to remove...
So basically, you have no programming experience and I would hope that English isn't your native language.
Your best bet for now would be to sit back and watch those ahead of you and ask questions as needed.
I think he's suggesting that any code that came about from this would get pushed into stock and hopefully integrated by Google. Manufacturers wouldn't tamper with it; rather, they would make their custom skinned Android (so HTC Sense, or Samsung Touchwiz, or MotoBlur/NinjaBlur) be separate. Phones would require more system space to accommodate for the backups, but it wouldn't have to be astronomical, as only the parts of the system that the skin makers actually modified would be in those recovery partitions. So then the recovery utility launched by the included app would pull all of the packages from whichever partition (recovery_SENSE, for example, or recovery_VANILLA for stock) and push them into /system. So the phone's system would have three total partitions: /system, which would be mounted by the phone during normal boots, /recovery_[whatever_skin], which would hold the manufacturers version of anything they skinned, including apps, frameworks, anything they added, etc, and /recovery_VANILLA, which would only hold the stock versions of anything in the /recovery_[whatever_skin] partition, plus anything the manufacturers took out.
Furthermore, if the partitions are all made big enough, they could future-proof phones. recovery partitions would hold the entire system, skin (or lack of skin) and all, then Google would be made responsible for pushing out the updates to the /recovery_VANILLA partition, keeping all phones up to date. People who ACTUALLY want to sacrifice features for the skin and possible other features could do so. And because everything is backed up to your Google account, there'd be no problems. Everything would get synced at first, but after that you'd be smooth as butter.
I think if this was implemented, and Google told manufacturers they had to do this, it would do a whole lot in the way of moving us away from skins. I think as Google updates are pushed out and manufacturers are updating far less frequently, more and more people will switch to their stock partitions, and, through ad information, manufacturers would realize the skins are wack.
momentarylapseofreason said:
So basically, you have no programming experience and I would hope that English isn't your native language.
Your best bet for now would be to sit back and watch those ahead of you and ask questions as needed.
Click to expand...
Click to collapse
I actually don't mind if someone takes this and makes something out of it... I don't even want the credit, but I as well will be working and reading as much as I can to get something working, I know this may be hard or complicated but if I see this being implemented and people enjoying it I'll be happy
guitargler said:
I think he's suggesting that any code that came about from this would get pushed into stock and hopefully integrated by Google. Manufacturers wouldn't tamper with it; rather, they would make their custom skinned Android (so HTC Sense, or Samsung Touchwiz, or MotoBlur/NinjaBlur) be separate. Phones would require more system space to accommodate for the backups, but it wouldn't have to be astronomical, as only the parts of the system that the skin makers actually modified would be in those recovery partitions. So then the recovery utility launched by the included app would pull all of the packages from whichever partition (recovery_SENSE, for example, or recovery_VANILLA for stock) and push them into /system. So the phone's system would have three total partitions: /system, which would be mounted by the phone during normal boots, /recovery_[whatever_skin], which would hold the manufacturers version of anything they skinned, including apps, frameworks, anything they added, etc, and /recovery_VANILLA, which would only hold the stock versions of anything in the /recovery_[whatever_skin] partition, plus anything the manufacturers took out.
Furthermore, if the partitions are all made big enough, they could future-proof phones. recovery partitions would hold the entire system, skin (or lack of skin) and all, then Google would be made responsible for pushing out the updates to the /recovery_VANILLA partition, keeping all phones up to date. People who ACTUALLY want to sacrifice features for the skin and possible other features could do so. And because everything is backed up to your Google account, there'd be no problems. Everything would get synced at first, but after that you'd be smooth as butter.
I think if this was implemented, and Google told manufacturers they had to do this, it would do a whole lot in the way of moving us away from skins. I think as Google updates are pushed out and manufacturers are updating far less frequently, more and more people will switch to their stock partitions, and, through ad information, manufacturers would realize the skins are wack.
Click to expand...
Click to collapse
Indeed thats what I'm thinking... I don't think space should be much of a problem, especially on hight end phones.
When I posted this my fist idea was to give someone an idea I don't mind how you implemented or who you decide to work with (I'll probably just slow you down anyways)
K Dotty said:
Cyanogen mod is basically stock android with a few mods and tweaks. If doesn't have all of the bloatware that skinned manufacturer roms have so its alot faster and I think stock android looks better than sense, etc.... Its been compiled for a wide range of phones.
Click to expand...
Click to collapse
Basically stock? AHAHAH
It's all but stock... so many changes, have you ever run a stock Gingerbread or even FroYo recently? Way faster than CM. The truth is that ATM CM is just a candy ROM ATM with large phone models support.
I'd really like to see a stock rom for older devices - here is where CM is proud of. But it's not stock.
As of the application support, you may use my ROM Updater ( http://www.elegosproject.org/android-rom-updater ) to setup repositories of stock ROMs (and in a near future extra downloads like kernels, themes and so on).
[GUIDE | READ ME | DISCONTINUED-28/06/12 ] A Newbie Guide for your Galaxy Tab 7.7 ▓░░
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do terms like ‘Android ROM’ confuse you? Is your understanding of ‘flashing’ limited to acts of exhibitionism? Do you feel left out or clueless when your friends talk about flashing the latest custom ROM to their Android device ? here is a guide for you to make your life easier
Hey guys, this is a guide which will help many people (new users).
The Very Beginning!
Android is an Operating System (OS), like Windows or OSX to your computer or iOS [1] to the iPad and iPhone. It controls how the phone reacts to your inputs, what's displayed on the screen and when. Many would argue, the OS is the most important factor of any mobile device. Whether or not you agree, it certainly has a massive impact on user experience, hopefully at the end of this, you'll be able to make up your own mind.
Note-
Red color means -> its important !!
Click to expand...
Click to collapse
Understanding ROM’s and Builds
A ROM is essentially a custom version of Android. Each tweaks, combines, or optimizes Android to offer something standard versions lack. Within ROM’s, you have what are known as builds (basic branches of Android code) that offer certain features and characteristics.
Think of it as a crude metaphor for Microsoft Windows. There’s XP, Vista, and Windows 7. All three are Windows operating systems and can typically run the same programs, but there are major differences between them. Within each OS, there’s further distinction between Vista Home, Vista Pro, and Vista Ultimate. Likewise, one ROM can spawn multiple versions. For instance, there are several flavors of Drake’s Hero ROM..
Be advised that some ROM’s require a wipe (erases all information stored on your phone) before or after installation. This is done when you enter the recovery mode and perform a “factory data reset.”
What is Firmware?
The read-only operating systems that we just discussed above are also called ‘firmware’, as they stay firmly in place without modification access to the users of the device. Modification of firmware is still however possible, just not under normal usage. Many devices require specialized hardware to be used for the purpose while other devices have the storage set as read-only through software protection only, which can be removed or overridden without the need for any specialized hardware, just by using software written for the purpose, often but not always requiring connection to a computer.
Thus, the terms ‘operating system’ and ‘firmware’ both refer to the same thing and can be used interchangeably when applied to such devices.
Flashing
The ROM memory used in smartphones and tablets etc. is often same as flash memory found in SD cards and USB flash drives, simply optimized for better speed and performance while running the operating system. As explained above, it is read-only under normal usage and requires a special procedure for any modifications to be made to its contents. The procedure of modifying or replacing the contents of such flash memory is known as flashing. Thus, in layman’s terms, flashing is essentially the same as installing or modifying the firmware of a device that is stored on its protected flash memory.
2 – Mobile Operating Systems
ROM as the Operating System
When it comes to smartphones and tablets, the term ROM is used to refer to the firmware stored in the internal memory of the device, rather than the internal memory itself. It can also refer to a file prepared for the purpose of replacing this firmware with another version of using a special method.
Thus, when you are told by someone to download a ROM, they are referring to the file that contains the firmware in a format ready to be installed to your phone to replace it’s existing firmware. Similarly, when asked what ROM is your phone running or when told by someone their phone is running a particular ROM, they are again talking about the particular variant of the firmware.
Types of ROMs->
Unlike most desktop operating systems, mobile operating systems can be found in installable format in multiple forms, which can be categorized as follows.
A)Truly Stock ROMs / firmware:
This is the operating system in its default form, without any modifications made to it except for any device-specific support required to run it on the particular device. Truly stock firmware provides the standard user experience of the operating system without any cosmetic or functional changes made.
B)Manufacturer or Carrier branded Stock ROM / Firmware:
This type of firmware has had enhancements added over the default operating system by the device manufacturer or the mobile service carrier. This often includes interface enhancements, proprietary applications and in most cases, restrictions intended to limit the use of the device with a specific carrier or region. There are often further restrictions preventing installation of firmware not released by the carrier or manufacturer.
C)Custom ROM / firmware:
Independent developers who like to customize their devices beyond the standard options provided often tend to release the fruits of their labor for the rest to enjoy, in form of custom ROMs.
3 – Stock Vs. Custom ROMs
Both stock and custom ROMs have their merits and demerits and choosing between the two requires careful consideration. In this section, we are going to make a comparison between the two types of ROMs to help you make the right choice. Let us begin by taking a look at their advantages and disadvantages.
Advantages & Disadvantages of Stock ROMs
Stock firmware is the result of a lot of research and testing done by the operating system vendor, the device manufacturer and/or the mobile service carrier. Therefore, it carries several advantages:-
1>It is usually quite stable upon release.
2>Almost all bugs are patched during the extensive beta testing before release.
3>It carries the official support by the firmware vendor, device manufacturer and the mobile service carrier.
4>Updates are pushed automatically to the device by the carrier.
Along with its advantages, stock firmware also carries its disadvantages and these include:
1>Updates aren’t frequent, as development is done mostly by corporations who have to follow a scheduled release cycle.
2>Providing feedback to the manufacturer in case of any issues is either impossible, unwelcome (often with Apple devices), or a long, tedious process.
3>Similarly, getting official support can be a hassle as well, involving a tedious process.
4>If the device manufacturer and operating system developer are different (as is the case with Android and Windows Phone 7), any updates released by thekoperating system vendor need to be edited by the device manufacturer or mobile carrier to add compatibility and additional software before release. Hence, some devices get updates delayed by months.
5>Updates are often released first in the United States, leaving the rest of the world waiting. (A world does happen to exist beyond the United States, we’ve confirmed it ourselves!)
6>Worse still, when manufacturers choose to no longer release official updates for their older devi#es in favor of newer ones, their users are essentially stuck with old versions of the operating system. This case is evident with many Android devices barely a year and a half old.
Advantages & Disadvantages of Custom ROMs-
Custom ROMs are as good or as bad as the effort put into them by their developers. Key advantages of custom ROMs are:
1)First and foremost, choice! There are thousands of custom ROMs out there for a range of devices, each offering a diverse set of features not found in the stock ROM.
2)Update frequency – custom ROMs are often under active development and newer releases of the core operating system are incorporated in them way before updated official ROMs are released.
3)Providing feedback is as easy as leaving a message on the development forum for the ROM in question.
Getting support with your issues at the forums is similarly easy, as not only the main developers themselves but also other experienced users of the ROM from the community are glad to help you with your issues and in the process, improve the ROM for everyone.
4)Custom ROMs usually have all the extra restrictions removed
5)Performance enhancements and optimizations found in many custom ROMs can make them much faster than stock ROMs ,enabling users to get the most out of their devices.
5)Overclocking options are built into some custom ROMs, further speeding up the devices.
6)Undervolting options found in some ROMs on the other hand result in improved battery life.
7)Old phones with little internal memory can benefit most from custom ROMs that allow them to use the external SD card memory for the apps exactly the way they would use the internal memory.
So with all these advantages, there should be no reason to stick with the stock ROM, right? Not necessarily! Like all things in life, custom ROMs come with their disadvantages as well:
1)Due to the lack of extensive testing prior to release, many custom ROMs can be buggy in the beginning and installing a ROM with missing or corrupt critical files can even brick your phone.
2)Several custom ROMs that are ports of ROMs from other phones can have missing functionality that hasn’t been made to work on your phone with the ROM yet.
Installing a custom ROM usually involves wiping your phone to factory settings, so you lose your data and start from scratch. Fortunately, Android’s built-in contact syncing along with apps offering message, call log and app backup/restore make this process easier, letting you retain your data.
The installation process can be cumbersome and requires you to root your phone and often circumvent its security features to allow for custom ROM installation in the first place.
Installing a custom ROM will in most cases void your phone’s warranty, though often the process is reversible, meaning you can turn your phone back to stock as long as it isn’t bricked.
Choosing the Right Custom ROM
With several custom ROMs available for most Android devices, choosing the right one isn’t always easy. The question of ‘which is the best ROM for _____ phone / tablet’ is as often frowned-upon at the forums as it is asked, since there is no universal answer for it. One ROM may be the best for me while another might suit you better. The only solution is to read a lot, go through the feature list, read user response and if required, ask the developer questions at the forum page for the ROM. Attempt to install the ROM only after you are fairly satisfied that doing so will not harm your device to the extent you can’t fix.
Nandroid BACKUPA Nandroid Backup is a backup file of your current ROM and its settings, you can do it manually using Clockwork Mod Recovery, it's fairly intuitive so you shouldn't have too much issue figuring these steps out.*IMPORTANT*
RISKS OF ROOTINGWhen a root exploit is initially found, it may or may not be stable. What this means is that it may not work reliably, or worse, it may cause a permanent failure of the phone, preventing it from booting up. A responsible phone hacker will therefore test the exploit extensively across many phones and modify the exploit as needed to make it stable. When the exploit has been proven to work safely and reliably, it is released to the public. However, this does not guarantee that the exploit will work with every single phone that it targets. The person or team that releases the exploit will make it clear that the exploit is "use at your own risk." Each person considering rooting their phone needs to understand this risk and decide whether it's worth proceeding or not.
Once the exploit has removed the NAND protection, the risk of permanently damaging your phone becomes very, very low. That's not to say that you can't get yourself into a bind, but with a little bit of know-how, rarely does a bad situation mean a bricked phone. If you haven't guessed already, a bricked phone is a phone that shares the qualities of a brick: it can look rectangular and do nothing.
As a preemptive safety measure, the custom recovery program installed as part of the root exploit contains a very useful tool called a NANDroid backup/restore. This utility backs up your internal memory and essentially is a save-state. No matter how you change your phone in the future, you can always bring your phone back to the state it was in at the time of the backup. It is highly recommended to make a NANDroid backup before flashing anything.
Knowledge is power here. If you've read this far, you already have a really good foundation into the Android rooting world. For more excellent infor-ation, I recommend reading this post: Quick INTRO TO ROOTING for those new to rooting, which will give you a broader vocabulary of root-related terminology. The more information you gather, the more you will realize that the risks of rooting are very low, while the rewards are very high.
And don't hesitate to use these forums to ask questions and seek clarifications. The rooting community is strong, and there are tons of people eager to help. Today's newbies are tomorrow's experts. Good luck in your endeavor%r1
The Android Family Tree
Android has a come a long was since its birth in 2008, however we're not here to fire into its history specifically, but what its history might mean for you! Android has been released in incremental versions. Each phone may differ in what version it has installed, usually the vendor decides what version it will choose, and develops Android into a specific ROM [2] for the device. To find out what version of Android your device is, navigate to the settings menu and select 'about phone', under 'Android version' there will be three numbers, the first two, will tell you what release you're running. There are currently 5 flavours of Android for phones, these are;
1.5 - Cupcake
One thing you'll learn, Android has quirky names! This version of android is likely the most basic version you'll meet, very few handsets still selling have this version. If you have a handset with version 1.5, you're limited in a big way! There are many features missing that means 1.5 just can't support many of the applications offered up in the market!
1.6 - Donut
Donut offered a few improvements over Cupcake; Voice search, turn-by-turn navigation and an improved market to name a few! It's still missing a few features that don't allow the more advanced apps to run. So don't be suprised if you're missing a few from the market.
2.0/2.1 - Eclair
Google picked up their game with the move to 2.1, it is arguably the largest and most important update Google made. Most applications will work on 2.1! It also included support for Microsoft exchange (if you don't know what this is, you don't need it) increased speed, smoothness, and improved the user interface immensely.
2.2 - Froyo
Currently the largest version in use, you're with a masses here and perhaps will find comfort in it. a few performance tweaks, faster browsing and the ability to run Adobe Flash 10.1 is among the few things you can do over your 2.1 bretheren.
2.3/2.4 - Gingerbread
Updated UI, higher resolution screens, VoIP calls, improved keyboard, introduced NFC to the world, faster performance, and a better battery life are among the benefits over your older bretheren. This released also improved voice-to-text engine input, copy and paste, audio effects, and enabled simultaneous multiple camera support.
4.0 - Ice Cream Sandwich
Ok huuuge update here, haven't played on it yet but this is shaping up to be the biggest update since 2.1, if not ever! Combining Gingerbread and Honeycomb, this is loooking a very mature and slick version of Android. Massive UI overhaul; hardware acceleration, no physical/permanent buttons, new Roboto font, Honeycomb task manager, new screen layouts, easily customisable folders, widget app drawer and a customisable launcher. Other improvements include new contacts or 'people' app, further improved copy and paste, further improved keyboard, visual voicemail with improved functionality, improved gestures, new lock screen, integrated screenshot capture, facial recognition unlocking, Android Beam utilising NFC, and awesome 3g data management software!
Click to expand...
Click to collapse
Power saving tips:
Dont use a live theme
Use a dark wallpaper
Turn off wi-fi & bluetooth when not in use
Stop friendstream, facebook & peep updating every 5mins. Set mine to manual.
Set email app to manual
Set screen brightness to auto or 40% (lower if you can put up with it).
How does one flash a kernel?
The process is a simple as flashing a ROM, put the .zip on ur sdcard, go into recovery,wipe cache,dalvik-cache, install .zip from sdcard, reboot phone and ur done.
How to Flash A Custom ROM-
Download a ROM of your choice from the All Things Root section (The Forum you are in) You can find direct links to each of them in the All Things Root Guide that is stickied at the top of this forum.
1- Once downloaded, its recommended to download it from your computer and place it on your phone, put it on the root of your internal or external sd cards. Root meaning not in a folder.
2- Reboot into recovery using Quick Reboot.
3- Using your volume keys to scroll and your power key to select, scroll down tand select "Wipe data/Factory Reset" then scroll to "Yes" and select.
4- Scroll down and select "Wipe Cache Partition" and then select "Yes"
5- Scroll down and select "Advanced" and select "Wipe Dalvik Cache" and then select "Yes" then scroll down and select "Go Back"
6- Sroll down and select "mounts and storage" then scroll down and select ONLY these 3 listed, "format data" and then select "Yes", then scroll down and select "format cache" and then select "Yes", then scroll down and select "format system" and then select "Yes". Then scroll down to and select "Go Back"
7- Then scroll down to "Install Zip From Sd", if you put the ROM on your external SD card select "choose zip from SD". If you put it on your internal scroll down and select 'choose zip from internal". Then after you selected one of those depended on where you put the ROM, scroll down and select the ROM and then Select "Yes".
Let it run and do its thing and once it says its done, select "reboot system now" and enjoy
How To Flash A Theme-
Download a theme of your choice from the All Things Root section (The Forum you are in) You can find direct links to each of them in the All Things Root Guide that is stickied at the top of this forum.
1- Once downloaded, its recommended to download it from your computer and place it on your phone, put it on the root of your internal or external sd cards. Root meaning not in a folder.
2- Reboot into recovery using Quick Reboot.
3- Using your volume keys to scroll and power button to select, scroll down and select "wipe cache partition" and then select "Yes"
4- Scroll down to and select "Advanced" and then select "Wipe Dalvik Cache"
5- Then scroll down and select "Go Back"
6- Then scroll down to "Install Zip From Sd", if you put the theme on your external SD card select "choose zip from SD". If you put it on your internal scroll down and select 'choose zip from internal". Then after you selected one of those depended on where you put the theme, scroll down and select the theme and then Select "Yes".
Let it run and do its thing and once it says its done, select "reboot system now" and enjoy
You can find stock firmwares here -sampro.pl
sammobile
Important (Read it carefully) -> Forum & Marketplace Rules & announcements
Some other guides by some great developers-
> [ROM&GUIDE] Official Firmwares SGT 7.7 P6800 + P6810 Download By xenix96
>[GUIDE] Root By Jade Eyed Wolf
> [Guide] Full Tutorial To Install Custom ROM [GT-P6800] BY haidharbbc
Useful posts -
> [FAQ] Com-on Issues with the P6800 and their Solutions (where available) By Theory
>Welcome To the Galaxy Tab 7.7 Forum -Please Read Before Posting- by original_ganjaman
>[REF] Partitions P6800 + P6810 By Chainfire
> Simple ways to speed up your tablet!!
HONYCOMB FULL PREVIEW USER GUIDE *IMPORTANT*
I will update it ,when there is a need.
--->I will add more. If I ever miss anything please send me a private message
That should be enough to get you started.
CHANGELOG-
UPDATE - 22/04/12 MAJOR UPDATE !! lot of information added!!!!
UPDATE -02/05/12 Android Terms,Slang & Definition added to guide see post #3 !!
UPDATE - 28/06/12-Due to fact, i dont own this tab anymore, there will be no updates.sorry!
Click to expand...
Click to collapse
I hope this guide helps you.......
Thanks..........
Please comment if you have any problems, or want to share anything.
Please give an REVIEW ,it means a lot to me.Thank you.
-------------------*Important Tips*---------------------
--- Important Tips ---
[1]THERE IS NO SUCH THING AS THE *BEST* ROM OR *BEST* TWEAKS
-everything that has *best* in it's name is mainly made by questioner's preference.
[2] STOP ASKING FOR ETA'S....Stop asking when will it be released or when will that be released.its silly you know. IT WILL COME WHEN ITS READY GET IT ?
[3]OK this will be quite simple. If it says DEVS ONLY leave it alone. Don't comment unnecessary trash and ask for ETA's.
It's unstable so don't go making a thread in general section asking if it's stable or not.ok ?
[4]RESPECT THE DEVELOPERS*IMPORTANT*
[5] Read or search before posting anything! GOOGLE is your best friend!
https://www.google.com (use me)
SEARCH SEARCH SEARCH SEARCH BEFORE DOING SOMETHING !!!!!
I hope i am clear.....
[6] Stop posting and posting the same stuff over and over and over again! If it says in the ROM description that ""This" is not working" Dont keep on asking is "this" working? or something like that.
[7] Post in the proper section. You will get more help if you do this.
For example... don't start a question thread in developers forum just because you think it's more active than general section. EVERYTHING HAS IT'S PURPOSE
[8] If a bug has been reported once,then THATS ENOUGH REPORTING < Read once more,enough said
[9] LOOK,READ AND THEN ONLY POST,If there is something you want to post,then look at thread,read the whole thread and then ONLY post.
Credits - DooAce ,prawesome
Android Terms,Slang & Definitions*Important* + How to Increase Battery Life !
PART #1
Android Terms,Slang & Definitions
Apps2SD:A method of storing applications and cache on the device's microSD card.
ADB:Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
•A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
•A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
•A daemon, which runs as a background process on each emulator or device instance.
AMOLED:Active Matrix Organic Light Emitting Diode. Basically, a very colorful, bright, display found in some smartphones.
APK:Android application package file. Each Android application is compiled and packaged in a single file that includes all of the application's code (.dex files), resources, assets, and manifest file. The application package file can have any name but must use the .apk extension. For example: myExampleAppname.apk. For convenience, an application package file is often referred to as an ".apk".
Alpha:The alpha phase of the release life cycle is the first phase to begin software testing (alpha is the first letter of the Greek alphabet, used as the number 1). In this phase, developers generally test the software using white box techniques. Additional validation is then performed using black box or gray box techniques, by another testing team. Moving to black box testing inside the organization is known as alpha release.[1]
Alpha software can be unstable and could cause crashes or data loss. The exception to this is when the alpha is available publicly (such as a pre-order bonus), in which developers normally push for stability so that their testers can test properly. External availability of alpha software is uncommon in proprietary software. However, open source software, in particular, often have publicly available alpha versions, often distributed as the raw source code of the software.
The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be a feature complete.
Boot Animation:Boot animation is a term for a graphical representation of the boot process of the operating system.
Boot animation can be a simple visualisation of the scrolling boot messages in the console, but it can also present graphics or some combinations of both.
Unlike splash screens, boot screen or boot animation is not necessarily designed for marketing purposes, but can be to enhance the experience of the user as eye candy, or provide the user with messages (with an added advantage of color coding facility) to diagnose the state of the system.
Bootloader:This small program's only job is to load other data and programs which are then executed from RAM.Often, multiple-stage boot loaders are used, during which several programs of increasing complexity load one after the other in a process of chain loading.
Bootloop:When your system recycles over and over without entering the main OS.
Beta: is the software development phase following alpha. It generally begins when the software is feature complete. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it.
The users of a beta version are called beta testers. They are usually customers or prospective customers of the organization that develops the software, willing to test the software without charge, often receiving the final software free of charge or for a reduced price.
Beta version software is often useful for demonstrations and previews within an organization and to prospective customers. Some developers refer to this stage as a preview, prototype, technical preview (TP), or early access.
Some software is kept in perpetual beta—where new features and functionality is continually added to the software without establishing a firm "final" release.
CPU:It stands for Central Processing Unit and handles all the complex mathematical formulas necessary to do everyday things like surfing the Internet.
Cache:A component that transparently stores data so that future requests for that data can be served faster. The data that is stored within a cache might be values that have been computed earlier or duplicates of original values that are stored elsewhere. If requested data is contained in the cache (cache hit), this request can be served by simply reading the cache, which is comparatively faster. Otherwise (cache miss), the data has to be recomputed or fetched from its original storage location, which is comparatively slower. Hence, the greater the number of requests that can be served from the cache, the faster the overall system performance becomes.
CDMA:Mobile phone standards called cdmaOne, CDMA2000 (the 3G evolution of cdmaOne) and WCDMA (the 3G standard used by GSM carriers), which are often referred to as simply CDMA, and use CDMA as an underlying channel access method.
CIQ:Carrier IQ. A piece of preinstalled software that runs with elevated access in the background of portable devices by default and records everything. Potentially can be exploited to steal information.
Dual Core:A dual core processor is a central processing unit (CPU) that has two separate cores on the same die, each with its own cache. It essentially is two microprocessors in one. This type of CPU is widely available from many manufacturers. Other types of multi-core processors also have been developed, including quad-core processors with four cores each, hexa-core processors with six, octa-core processors with eight and many-core processors with an even larger number of cores.
Dalvik:The Android platform's virtual machine. The Dalvik VM is an interpreter-only virtual machine that executes files in the Dalvik Executable (.dex) format, a format that is optimized for efficient storage and memory-mappable execution.
Dalvik Cache:Writable cache that contains the optimized bytecode of all apk files (apps) on your Android device. Having the information in it's own cache makes applications load faster and perform better.
EXT2:The ext2 or second extended filesystem is a file system for the Linux kernel. It was initially designed by Rémy Card as a replacement for the extended file system (ext).
ext2 was the default filesystem in several Linux distributions, including Debian and Red Hat Linux, until supplanted more recently by ext3, which is almost completely compatible with ext2 and is a journaling file system. ext2 is still the filesystem of choice for flash-based storage media (such as SD cards, and USB flash drives) since its lack of a journal minimizes the number of writes and flash devices have only a limited number of write cycles. Recent kernels, however, support a journal-less mode of ext4, which would offer the same benefit along with a number of ext4-specific benefits.
EXT3:Third extended filesystem, is a journaled file system that is commonly used by the Linux kernel. It is the default file system for many popular Linux distributions, including Debian. Stephen Tweedie first revealed that he was working on extending ext2 in Journaling the Linux ext2fs Filesystem in a 1998 paper and later in a February 1999 kernel mailing list posting, and the filesystem was merged with the mainline Linux kernel in November 2001 from 2.4.15 onward.Its main advantage over ext2 is journaling, which improves reliability and eliminates the need to check the file system after an unclean shutdown. Its successor is ext4.
EXT4:It was born as a series of backward compatible extensions to ext3, many of them originally developed by Cluster File Systems for the Lustre file system between 2003 and 2006, meant to extend storage limits and add other performance improvements.However, other Linux kernel developers opposed accepting extensions to ext3 for stability reasons,and proposed to fork the source code of ext3, rename it as ext4, and do all the development there, without affecting the current ext3 users. This proposal was accepted, and on 28 June 2006, Theodore Ts'o, the ext3 maintainer, announced the new plan of development for ext4.
FC/FC's:Short for "force close," meaning an app that has crashed.
Fastboot:A diagnostic protocol used primarily to modify the flash filesystem in Android smartphones from another computer over a USB connection. It is part of the Android Debug Bridge library.
Utilizing the Fastboot protocol requires that the device be started in a boot loader or Second Program Loader mode in which only the most basic hardware initialization is performed. After enabling the protocol on the device itself it will accept any command sent to it over USB via a command line. Some of most commonly used fastboot commands include:
•flash - Overwrites a partition in flash with a binary image stored on the host computer.
•erase - Erases a partition in flash.
•reboot - Reboots the device into the either the main operating system or the system recovery partition.
•devices - Displays a list of all devices (with Serial #) connected to the host computer.
Flashing:The ROM memory used in smartphones and tablets etc. is often same as flash memory found in SD cards and USB flash drives, simply optimized for better speed and performance while running the operating system.
Hotspot:A spot that offers Internet access over a wireless local area network through the use of a router connected to a link to an Internet service provider. Hotspots typically use Wi-Fi technology.You can connect wifi campatible devices to it.
HDMI:High-Definition Multimedia Interface) is a compact audio/video interface for transmitting encrypted uncompressed digital data.It is a digital alternative to consumer analog standards, such as radio frequency (RF) coaxial cable, composite video, S-Video, SCART, component video, D-Terminal, or VGA (also called D-sub or DE-15F). HDMI connects digital audio/video sources (such as set-top boxes, DVD players, HD DVD players, Blu-ray Disc players, AVCHD camcorders, personal computers (PCs), video game consoles (such as the PlayStation 3 and Xbox 360), AV receivers, tablet computers, and mobile phones) to compatible digital audio devices, computer monitors, video projectors, and digital televisions.
JIT:The Just-in-Time Compiler. Released with Android 2.2, it's a method of greatly speeding up apps in Android on the software side.
Kang:Someone writes a code,someone else modifies the code to make their own release,its concidered a kang release.
Kernel:A kernel is a layer of code that allows the OS and applications to interface with your phone's hardware. The degree in which you can access your phone's hardware features depends on the quality of code in the kernel. The homebrew (rooting) community for HTC has made several kernel code improvements that give us additional features from our hardware that the stock kernel does not. When you flash a custom ROM, you automatically get a kernel. But you can also flash a standalone kernel ROM on top of the existing one, effectively overwriting it. These days, the difference in custom kernels is less about new features and more about alternate configurations. Choosing a custom kernel is basically choosing one that works best with your ROM.
Launcher:Collectively, the part of the Android user interface on home screens that lets you launch apps, make phone calls, etc. Is built in to Android, or can be purchased in the Android Market.
LCD Density:Pixel density is a measurement of the resolution of devices in various contexts; typically computer displays, image scanners, and digital camera image sensors.
First of all you need to understand that the Android User Interface uses something called a "display independent pixel" or a "dip" (yes, it's confusing because the density settings are in "dots per inch" or "dpi" which are considered the same as "ppi" or "pixels per inch" as well).
The default LCD Density setting on Android is 160 dpi. As far as the operating system is concerned 1 dip @ 160 dpi = 1 screen pixel. It doesn't mean that's actually true, but you've gotta start somewhere. In my opinion it would have been a lot nicer if they'd chosen 100 dpi because then it would be an easy percentage thing, but they didn't so we're stuck with this formula.
Mod:The act of modifying a piece of hardware or software or anything else for that matter, to perform a function not originally conceived or intended by the designer.
Nightly:A build that is performed at the end of each day of development. If you use a continuous integration server, it will generally be configured to build the code and run the unit tests on every check in. At the end of each day you may want to run more extensive tests, regression test and integration tests for example, which take too long to run on each check in and these would be triggered after the nightly build. If you have a full continuously delivery pipeline the nightly build may also be used to deploy the built code to environments for user testing.
Open GL:An open source 3D graphics library used in many devices, including Android devices.
Open & Closed Beta:Developers release either a closed beta or an open beta; closed beta versions are released to a select group of individuals for a user test and are invitation only, while open betas are from a larger group to the general public and anyone interested. The testers report any bugs that they find, and sometimes suggest additional features they think should be available in the final version.
Overclock:To increase the speed of your CPU.
Partition:The phone's internal memory (not the SD card) is solid-state (flash) memory, AKA NAND. It can be partitioned much like a normal hard drive can be partitioned. The bootloader exists in its own partition. Recovery is another partition; radio, system, cache, etc are all partitions.
Here are the standard partitions on an Android phone:
/misc - not sure what this is for.
/boot - bootloader, kernel
/recovery - holds the recovery program (either clockworkmod or RA recovery for a rooted Evo)
/system - operating system goes here: Android, Sense, boot animation, Sprint crapware, busybox, etc
/cache - cached data from OS usage
/data - user applications, data, settings, etc.
The below partitions are not android-specific. They are tied to the hardware of the phone, but the kernel may have code allowing Android to interact with said hardware.
/radio - the phone's radio firmware, controls cellular, data, GPS, bluetooth.
/wimax - firmware for Sprint's flavor of 4G, WiMax.
PRL:The Preferred Roaming List, basically a way of telling your phone which towers to connect to first.
RUU:a complete software package released by HTC, it can contain many things they are trying to update. Radio, ROM, bootloader, etc... Installing an ruu is like installing an image on a hard drive it wipes the phone and installs the image. It will wipe everything data and all so if you install one be prepared.
Radios:On the HTC side of things,the radios persist of:
•WiFi, which operates at 2.4-5ghz depending on what channel it's running
•Cellular/3G, which carries voice and data
•4G/WiMAX, which only carries data
•GPS, which is receive-only
•Bluetooth, which talks to WiiMotes and headsets
Flashing a radio means updating the code that controls the phones way of sending and recieving a signal.
Root:The first level of a folder.
SBC:(the ability to charge your battery beyond the default safe limit). The concept is similar to overclocking a processor: you're overriding the safety limits established to achieve additional performance. The benefit here is that you may gain more use of your battery per charge. The drawback is that you can damage the battery and significantly reduce its longevity. Some kernels claim they are using a safe technique to prevent battery damage. Just be aware of the potential risks.
Sideloading:It means installing applications without using the official Android Market.
Splash Screen:A splash screen is an image that appears while android is loading.Splash screens cover the entire screen or simply a rectangle near the center of the screen. The splash screens of operating systems and some applications that expect to be run full-screen usually cover the entire screen.
Superuser/SU:On many computer operating systems, the superuser is a special user account used for system administration. Depending on the operating system, the actual name of this account might be: root, administrator or supervisor.
Normal work on such a system is done using ordinary user accounts, and because these do not have the ability to make system-wide changes any viruses and other malware - or simple user errors - do not have the ability to adversly affect a whole system. In organizations, administrative privileges are often reserved for authorized experienced individuals.
Script:The Scripting Layer for Android (abridged as SL4A, and previously named Android Scripting Environment or ASE) is a library that allows the creation and running of scripts written in various scripting languages directly on Android devices. SL4A is designed for developers and is still alpha quality software.
These scripts have access to many of the APIs available to normal Java Android applications, but with a simplified interface. Scripts can be run interactively in a terminal, in the background, or via Locale.
SDK:(SDK or "devkit") is typically a set of software development tools that allows for the creation of applications for a certain software package, software framework, hardware platform, computer system, video game console, operating system, or similar platform.
Stock:This is the operating system in its default form, without any modifications made to it except for any device-specific support required to run it on the particular device.
S-On:Security on,means no acces to the phones operating system.
S-Off:Security was exploited,now have access to the operating system.
Tethering:Means sharing the Internet connection of an Internet-capable mobile phone with other devices. This sharing can be offered over a wireless LAN (Wi-Fi), Bluetooth, or by physical connection using a cable. In the case of tethering over wireless LAN, the feature may be branded as a mobile hotspot.The Internet-connected mobile phone acts as a portable router when providing tethering services to others.
USB:Stands for Universal Serial Bus. Is a method of connecting devices to a computer. Most smartphones now use microUSB cables to charge and sync.
Updater Script:When Android devices install updates via 'update.zip' files using recovery mode they have to perform a wide range of functions on files and permissions. Instead of using a minimal shell such as {b,d,c}sh the Android designers decided to create a small functional language that can be extended by device manufacturers if necessary. Since the Android "Donut" release (v1.6) the scripting language is called Edify and is defined primarily in the bootable/recovery/{edify,edifyscripting,updater} directories of the Android source-code tree.
Wireless N:Wireless N technology increases wireless internet connection. Wireless 'N' routers also work with Wireless 'G' and 'B' wireless adapters.
WiiMax:(Worldwide Interoperability for Microwave Access) is a communication technology for wirelessly delivering high-speed Internet service to large geographical areas.
YAFFS:Yaffs1 is the first version of this file system and works on NAND chips that have 512 byte pages + 16 byte spare (OOB;Out-Of-Band) areas.[clarification needed] These older chips also generally allow 2 or 3 write cycles per page,which YAFFS takes advantage of - i.e. dirty pages are marked by writing to a specific spare area byte.
Newer NAND flash chips have larger pages, 2048 bytes + 64 bytes spare areas, and stricter write requirements.Each page within an erase block (128 kilobytes) must be written to in sequential order, and each page must be written only once.YAFFS2 was designed to accommodate these newer chips.YAFFS2 is based on the YAFFS1 source code,with the major difference being that internal structures are not fixed to assume 512 byte sizing,and a block sequence number is placed on each written page. In this way older pages can be logically overwritten without violating the "write once" rule.[clarification needed]
YAFFS is a robust log-structured file system that holds data integrity as a high priority.A secondary YAFFS goal is high performance.YAFFS will typically outperform most alternatives.It is also designed to be portable and has been used on Linux, WinCE, pSOS, eCos,ThreadX and various special-purpose OSes.A variant 'YAFFS/Direct' is used in situations where there is no OS, embedded OSes and bootloaders: it has the same core filesystem but simpler interfacing to the OS and NAND flash hardware.
Zipalign: An archive alignment tool introduced first time with 1.6 Android SDK (software development kit). It optimizes the way an Android application package (APK) is packaged. Doing so enables the Android operating system to interact with the application more efficiently, and hence has the potential to make the application and overall the whole system much faster. Execution time is minimized for zipaligned applications, resulting is lesser amount of RAM consumption when running the APK.
CREDITS-Diablo67
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------
PART #2How to increase battery of Your Tab !
While many of us, and our readers, are seasoned vets of the Android ecosystem, there are many that are just starting out. After spending the last hour looking for something to cover that was extreme, I had an idea. That idea is what you are seeing here. A newbie friendly series of posts that will outline various topics from the simple, to the more complex. Not always about some new root tool, some new device or some insane kernel. More focused on basic daily operations, things that can improve upon the newest users experience to the Android ecosystem.
In today’s newbie guide we are going to outline a few battery saver tips and tricks that can help extend the life of your battery.
Tip #1 - As much as we all love the look of live wallpapers, they suck battery. Sticking to a static, or regular picture, will help out. Alternatively, the best option for many devices is using a true black png image. This is particularly helpful on AMOLED based screens, as color pixels use power where as black does not. Click the link to head to a black png, long press on it and save it. Then apply it as your wallpaper. If you can set it as a lockscreen wallpaper too that would be a good idea.
Tip #2 – Cut back on the widgets. While widgets are pretty, fun and often times useful, over doing it can hurt you long-term. Not just in battery performance, but even device performance. For instance, using Beautiful Widgets, you can get the date, time and weather in one widget versus running three different ones. If you can’t live with out them, then at least adjust the settings for when they update. Instead of polling the weather every time you turn your screen on, set it to every 4 or 8 hours. Most widgets will also let you set them to only pol manually. While it might be a slight inconvenience, pulling data for updates uses power and it uses your data plan.Similar rules apply to apps like Hootsuit, Facebook and so on.
Tip #3 – Screen brightness can dramatically affect your overall battery life. Many devices have an auto brightness setting that will use your light sensor to adjust the brightness according to the current lighting conditions. It is recommended that you leave that turned on. I have found that while it is nice, I prefer to have manual control of my brightness. If you spend a great deal of time indoors, the lowest brightness setting is enough to see your screen and use your phone. While the next statement might seem to contradict the widget tip, not all widgets consume power. Most Android version have a ‘power control’ widget which gives you quick access to WiFi, Bluetooth, GPS, Sync and brightness. If your device doesn’t have one, you can locate single button widgets that offer the brightness control, such as this one. I personally keep it to the lowest setting and if I need more light, just tap the brightness button to make it brighter when I need it.
Tip #4 - This one is simple and easy. Keep Wi-Fi and GPS off unless you actually need them. Both are easily controlled with the power control widget ro any other number of apps to keep you from having to go through the settings all the time. Heck, many newer devices even have those in the notification drop down bar now.
Tip #5 – When traveling or staying in an area that has no reception, turn of the devices radios. Sounds silly right? But if you are somewhere that gets no service at all, your device is going to be constantly searching for service and your battery is going to drain like crazy. The easiest and most universal way to turn of your radios is to put the device in ‘airplane mode.’ That is generally under Menu > Settings > Wireless and Networks. Although some UI’s have it in a different location and there are also apps and widgets that can accommodate this function. This also works out well in an office environment where Wi-Fi might be present but cell service is non existent. You might need to toggle the Wi-Fi back on for data use, but your phone won’t be searching for cell connection the whole day either.
Tip #6 – Adjust your screen off time. Many of us seasoned vets just hit the power button when we are done on our phone to turn of the screen. While it is rare, some devices don’t have that option. Setting the screen off time to the lowest amount of time will help ensure your phone’s screen goes off in case you forget. Believe me, I have seen people set their phone down with the screen on for hours and wonder why their battery dies so quickly. This can be accessed via Menu > Settings > Display. Depending on your current device, it might be screen off timer or sleep. Maybe others, not sure.
Tip #7 – This tip has a few various parts. First, running your battery through a few charge cycles is always a good idea. This means fully charging the device, then running it until it powers off. While it is off, plug in and charge it to 100%. Then repeat the process at least twice, but three times is a good idea. Sadly, the batteries the manufacturers use, aren’t always of the highest quality. Bummer huh.
Tip #8 – Watch for ‘rogue’ apps. By that we mean, if you have recently installed an application and you have noticed that your battery life has also recently gotten worse, you may have a rogue app running. This is usually pretty easy to find by checking Menu > Settings > Battery. You can usually see what apps are sucking juice. If you locate one, you can kill that process to stop it from eating battery, or if it is an app you hardly use simply uninstall it.
Tip #9 – Final tip for this post. Your launcher. Yes, your current launcher might be the culprit as well and you may not even know it. The fantabulous Sense UI found on HTC devices, TouchWiz found on Samsung devices and MotoBlur found on Motorola devices can also attribute to battery brain. Often times switching to a new launcher such as Go Launcher EX, ADW Launcher EX or countless other launchers can provide not only a boost in battery performance, but also a boost in your devices speed. Not to mention the added benefit of fun UI elements, themes and tweaks.
While there are plenty of other tips and tricks that I am sure our readers will add to the comments, these are 9 that can really make a difference in your daily consumption. Give them a try if you haven’t already done so and give it a couple of days. Nothing happens over night.
CREDITS-> Stormy Beach.
Good guide for the noobs
Thread updated - Major update - 22/04/12
Please comment if you have any problems, or want to share anything.
Please give an REVIEW ,it means a lot to me.Thank you.
Great job. I'm sure it'll help newbies a lot. Too bad that there is still not much in the development section to put your guide to work. Hopefully that'll come soon.
Marand55 said:
Great job. I'm sure it'll help newbies a lot. Too bad that there is still not much in the development section to put your guide to work. Hopefully that'll come soon.
Click to expand...
Click to collapse
yes , you are right... there is not much in the development section ,it can be due to since its new tablet . hope it gets better.
Thanks for putting all this together... haven't read through it all yet as I think it probably covers a lot of what I know and have learnt since I joined the Android world last year, but I will bookmark it so I can point friends this way if they leave the iPhone flock.
Ruxin said:
Thanks for putting all this together... haven't read through it all yet as I think it probably covers a lot of what I know and have learnt since I joined the Android world last year, but I will bookmark it so I can point friends this way if they leave the iPhone flock.
Click to expand...
Click to collapse
Thank you
This is a fantastic guide not only for someone new to the p6800/p6810, but anyone new to the Android ecosystem in general. Thank you for clearing a lot up for me!
JemaKnight said:
This is a fantastic guide not only for someone new to the p6800/p6810, but anyone new to the Android ecosystem in general. Thank you for clearing a lot up for me!
Click to expand...
Click to collapse
Your welcome ;-)
Great information. I wish I had it to look at when I first started playing around with rooting my Nook Color! This is a good thread to keep handy when a real novice gets the bug. Thanks.
GUIDE UPDATED -2/05/12"Android Terms,Slang & Definitions" added SEE post #3
Thanks for using the siggy!
And thanks again for the effort on piling things up!
billy_overheat said:
Thanks for using the siggy!
And thanks again for the effort on piling things up!
Click to expand...
Click to collapse
Your welcome !
Thumbs Upz! This is amust read and priority post before u go to other topics.
Help
Great Post!
Please I know I am most likely in the wrong area or post, I have had a Desire HD before and been down the road of rooting and flashing roms on it, I now own a Galaxy tab 7.7 and feel as if this is all new for me again. unfortunately I am in South Africa and had bought my tablet online, I was not told it would be a Arabic region tablet. Could I please ask who to speak to or ask for help on roms, I have the build number (HTJ85B P6800JPKL4) and want to know what roms will work and what not to use on this.
Please, I know you guys have better things to worry about but your advise or help would be gladly appreciated
Thank you in advance!
evil_penguin said:
Tip #1 - As much as we all love the look of live wallpapers, they suck battery. Sticking to a static, or regular picture, will help out. Alternatively, the best option for many devices is using a true black png image. This is particularly helpful on AMOLED based screens, as color pixels use power where as black does not. Click the link to head to a black png, long press on it and save it. Then apply it as your wallpaper. If you can set it as a lockscreen wallpaper too that would be a good idea.
Click to expand...
Click to collapse
Does anybody have a link to the png? I have misplaced mine, and I miss it. There doesn't seem to be a link here anywhere. thx.
Thanks
Thanks, really helpfull covers many things I was wondering about
thx
very helpful
Hello Guys,
before I start: My apologies for this, I am not quite sure if I am even in the right Topic.
I think of myself as pretty new to Android, but got some experiences in Rooting, Custom Roms and such. But that is already as far as it gets.
Now my Problem: We lost our BES and now my Company decided to go with Android (SG4 I9505) and I have to make it happen :angel:.
1. I Need some Kind of Freeware tool to administer Android Devices (Basic: find device, delete data, restrict Apps)
2. If something like this dont exist (which I dont think-I just havent found it)), I would Need to know if I can use CM 10.2 as our Standard Rom and before you start rolling your eyes with experimental and such....
I have to restrict the phone solely to Telefone, Exchange and some preselected (mostly travel)Tools. NO GAPPS!!! and I think that nightly CM provides this with no problems
To realize this I downloaded the nightly from 18th, I think. I then added some APK´s into \System\app Folder and installed the ROM. This actually worked fine until I updated to phone afterwards via build in updating tool - all Tools were gone.(what did I miss?)
Now, our Standard is SG4 I-9505.
Any ideas on how I could do this? (I couldnt find what I was looking for)
1. Adminster a fleet of androids (free)
2. Customize a Custom ROM for corporate Identity (How to pre-setup Exchange Boot Logo, Lockscreen, etc.)
3. or customize a ROM to the Point it cannot do much except what is in the \System\app Folder and turn off updates
Any link is much appreciated. Sadly there is sooooo much andoid articles out there that I seem to get lost while searching for the right one. Thanks in advance!!!!
AccEss-dEniEd said:
1. Adminster a fleet of androids (free)
2. Customize a Custom ROM for corporate Identity (How to pre-setup Exchange Boot Logo, Lockscreen, etc.)
3. or customize a ROM to the Point it cannot do much except what is in the \System\app Folder and turn off updates
Click to expand...
Click to collapse
My guess is I'll get flamed for saying this - but here goes.
Android corporate (MDM) leaves a lot to be desired next to iOS, at least as far as I've been able to find. We manage a lot of iPads and obviously minus the custom ROM we've been able to do it all for little to no cost. We've shied away from Android a lot because of the limited MDM control.
But, since you asked:
1. Meraki Systems Manager (and the accompanying app from Google Play)
2. Good luck with that
3. See number 2
I think the reality is you're going to need to do something to the effect of either cook your own ROM and deploy it or use a tool like CWM to create an "image" that you would then restore to the devices. I did that with a batch of 60+ Nexus 7s and it worked out pretty well.
Edit:
With all that said - I would urge your management to reconsider their approach as the world has changed since Blackberry was the only game in town. Yes, still stick with MDM, device location, remote wipe etc. But unless you're dealing with highly sensitive information (exp banking), let people actually USE the device you're giving them. Don't lock it down to where its basically a first generation iPhone. I'm a big fan of giving someone a good tool and letting them use it the way that works best for them, while still keeping the device and more importantly the data under corporate control.
Assuming you have Exchange, does this not provide the management part?
AccEss-dEniEd said:
Hello Guys,
before I start: My apologies for this, I am not quite sure if I am even in the right Topic.
I think of myself as pretty new to Android, but got some experiences in Rooting, Custom Roms and such. But that is already as far as it gets.
Now my Problem: We lost our BES and now my Company decided to go with Android (SG4 I9505) and I have to make it happen :angel:.
1. I Need some Kind of Freeware tool to administer Android Devices (Basic: find device, delete data, restrict Apps)
2. If something like this dont exist (which I dont think-I just havent found it)), I would Need to know if I can use CM 10.2 as our Standard Rom and before you start rolling your eyes with experimental and such....
I have to restrict the phone solely to Telefone, Exchange and some preselected (mostly travel)Tools. NO GAPPS!!! and I think that nightly CM provides this with no problems
To realize this I downloaded the nightly from 18th, I think. I then added some APK´s into \System\app Folder and installed the ROM. This actually worked fine until I updated to phone afterwards via build in updating tool - all Tools were gone.(what did I miss?)
Now, our Standard is SG4 I-9505.
Any ideas on how I could do this? (I couldnt find what I was looking for)
1. Adminster a fleet of androids (free)
2. Customize a Custom ROM for corporate Identity (How to pre-setup Exchange Boot Logo, Lockscreen, etc.)
3. or customize a ROM to the Point it cannot do much except what is in the \System\app Folder and turn off updates
Any link is much appreciated. Sadly there is sooooo much andoid articles out there that I seem to get lost while searching for the right one. Thanks in advance!!!!
Click to expand...
Click to collapse
I currently work in the infrastructure of a good sized corporation. We're using IOS with a mixture of android hardware and there's some good news and bad news for what you want to do.
Good news is, like Jpcurrie said, exchange will handle remote wiping and locking the phone down. you can require the phone to use a PIN, remote wipe and and a bit more. As for locating the phone, Google actually has finally built in remote locating of your device and remote wipe as well. There's a couple good apps out there (lookout) will turn on your GPS and allow you to locate the phone and they're free. If you happen to have a virtualized environment with VMware, you could also use VMware View Horizons which builds in a secure sector on the phone and you can remotely manage which apps and files the user can use. the best part of View is you can use a BYOD model and keep corporate data secure. The biggest issue is if you don't happen to already use a VMware architecture it gets pricey quickly.
Here's the rub now. you want to install your own logos on the bootup which you could do by installing a custom ROM. This will void your warranty on the hardware and as it isn't 100% stable you'll be spending a LOT of time trying to keep a consistent environment.
Like netsyd said, talk to management about an MDM, and the branding of the devices, maybe even talk to them about using a BYOD to reduce costs of hardware and administration of that hardware.
Isn´t Knox supposed to allow administrators to only delete the data that belongs to the Corporate account (emails, calendars, tasks, etc.), or an administrator can still force a full device wipe? Sorry if the questions is too basic, I've tried searching around for info on Knox but couldn't find anything besides press releases.
I'm not a network administrator, I'm just a user and my school secure wifi installs a device administrator.
I'm sorry to deviate the topic a little bit from the original.
At Delta we use Air Watch but it's far from free. You can however manage devices and remote wipe. You can also view installed apps and remove what should not be there. Options for device profiles also. I help maintain these devices everyday. Not Free but an MDM is your best bet.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
long time - no see
Hiya,
sorry I didn t answer - kinda was overwhelmed with this Task.
Wanted still to thank you: I did what you suggestet and wanted to let you know where I am now.
1. Meraki = implemented - now runnning 160+ devices. (at no costs)
2. CM12.1 implemented (without GAPPS/no SU)
3. Standard Image/w Apps defined. (Mostly Offline capable Tools like "here" etc.(which actually reduced costs))
4. Since Android has limited capability to be administered in a "real" professional Fashion we mitigated this issue by creating a policy to forbid the user to temper with the device (e.g. Installation of Software/SU etc) yet to allow the Installation of Software manually by us via creating a ticket. We check the Software mainly for "sanity" and malware and install it if ok.
This has been working so far like a charm for us. None of the user were happy to loose the Gapps obviously - but once they had their Software and settled in, all was ok. For the Administering part: Meraki can tell me if Software is beeing installed without our Knowledge, also we see if SM doesnt speak with us anymore. So, for now, we got the most out of the System and I am happy to say: I got minimal Control in a Quality sense. No no more "KO Critera" - and we have implemented Android. Tracking etc. is forbidden in Germany anyway - so we use Meraki mainly to wipe if lost and to check if someone goes against policy.
What is still open:
- I am still working on a way to have the user enter his credentials and automatically enter These in all respective config files. (haven't had much luck - with the absense of SU obviously.
- a Little cosmetics still open (I am still trying to figure out how the theming really works ... I usually f**k up the Pictures and sounds.... but so far making Progress
- with less and less good Android devices coming out (now, I am probably beeing flamed now ) that suits our needs (open bootloader, known/supported CPUs, removable battery, SD Card Slot) - I think we might Switch by Q4/2016.
netsyd said:
My guess is I'll get flamed for saying this - but here goes.
Android corporate (MDM) leaves a lot to be desired next to iOS, at least as far as I've been able to find. We manage a lot of iPads and obviously minus the custom ROM we've been able to do it all for little to no cost. We've shied away from Android a lot because of the limited MDM control.
But, since you asked:
1. Meraki Systems Manager (and the accompanying app from Google Play)
2. Good luck with that
3. See number 2
I think the reality is you're going to need to do something to the effect of either cook your own ROM and deploy it or use a tool like CWM to create an "image" that you would then restore to the devices. I did that with a batch of 60+ Nexus 7s and it worked out pretty well.
Edit:
With all that said - I would urge your management to reconsider their approach as the world has changed since Blackberry was the only game in town. Yes, still stick with MDM, device location, remote wipe etc. But unless you're dealing with highly sensitive information (exp banking), let people actually USE the device you're giving them. Don't lock it down to where its basically a first generation iPhone. I'm a big fan of giving someone a good tool and letting them use it the way that works best for them, while still keeping the device and more importantly the data under corporate control.
Click to expand...
Click to collapse