Related
Hi everybody,
I just moved from an iphone 3g (which i had jailbroken) to an incredible thanks to at&t contract finally finishing. Hv rooted the inc on my mac using the unrevoked method. Everything works fine (still have stock eclair 2.1 and sense running). Hv installed a bunch of apps from the market but hv not sideloaded anything yet or uninstalled anything (htc sense etc etc) yet. I would really appreciate some guidance from the community on the following since i am very new to the platform as a whole.
1. I dont want to lose the ability to update to the official froyo release (whenever it happens) so will I have to unroot (if thats even possible) to get the froyo update? If yes, whats the correct way so that I can bookmark that.
2. I want to be able to use the tethering without paying 20$ extra per month to VZ (in fact would probably use USB tethering to my macbook more often than wifi tethering/hotspot, but obviously I would like both! ). How should i do that? Obviously the stock app will just alert verizon, right? Is there another app that will work now that i hv rooted? Any special instructions to follow?
3. Would like to optimize the capability of the device by removing crapware and useless stuff which comes with the phone. Hv not yet even figured out what each app does yet. I will use my inc primarily for entertainment - games, social networking, browsing, streaming music, videos, google voice, true VoIP (not official VZ skype), GPS navigation, tethering (when no wifi) but will be OTA syncing my office exchange email account, contacts, calendar as well to make this a backup phone to my official bberry. Any suggestions on which apps to remove? Also how should I remove them without bricking the phone. Is there a cleaner method?
4. I actually like Sense even though it seems it uses up some memory - any way i can remove the useless parts of Sense (since I wont be using USB sync and I am sure some other stuff in sense is just bloatware) without losing the other features that look great - to be honest the phone looks too plain without sense (nexus 1 looked really naked). I would like to retain the look and feel of the sense ui.
5. How do I get swype on this? I played with it when i was shopping for android phones on the captivate (which unfortunately was on at&t) and I am amazed at how great that was! I badly badly badly badly need that!!
6. Any standard add-ons, apps which you would recommend for my intended usage?
7. Now that I am rooted which post-root apps should i install to make the inc more useful? Any obvious ones which you would recommend?
8. The people sense widget is just too much, anything a bit saner which is like a launchpad but without the screen wastage?
9. In jailbroken iphones, you could install lockinfo which was a spectacular agglomeration of all things (missed calls, voice mails waiting, email msg list, twitter feed, facebook feed, weather, calendar, tasks, sms msgs) in 1 simple scrollable screen. Anything similar in Sense/HTC widgets/App store? Just one glance would tell me everything.
Sorry, since I am new I decided to ask all questions in 1 shot. Obviously dont expect to have all questions answered by 1 person but if the devs/users can point me in the right direction, with links and some comments, I will greatly appreciate it.
Thanks and hoping to be a contributor to the android community sometime soon as I was in the iphone community until i just could not take at&t anymore.
1.yes you need to unroot to recieve otas
2.there is an app incthe market called wifi tether that is free.
3.look in the theme/app sectiom. there is a skinned version there.
4. adb in recovery os the only way to remove crapware
7-8 . there are not many apps for root users lile there was with cydia.
also, there are many widets avaliable in the android market. there is lots of good apps in the market. explore.
if you have any other questions feel free to pm me amy time.
jdkoreclipse said:
1.yes you need to unroot to recieve otas
Click to expand...
Click to collapse
No, if you are running the stock rom ou will recieve OTAs. The OTA doesn't magically detect "this phone is rooted."
rpearl said:
No, if you are running the stock rom ou will recieve OTAs. The OTA doesn't magically detect "this phone is rooted."
Click to expand...
Click to collapse
doesnt somethong change the ctacerts and otacerts?
Sent from my Incredible using XDA App
No. it's also not suggested and is reported to have negative side effects.
One important thing, Install Rom Manager from the market.
With this app you can do a backup of the Rom (stock sense and rooted) you're running now and install others to try, if you don't like them just restore the one you had before and done, you can as many back up as you want.
Also check in the theme section and you'll find lots of themes to make your phone look and work beautiful, this also allows you to get to recovery without having to turnoff your phone and install anything you want from the sd card.
Also, if you don't like some of the crap ware that Sense has, there's a post for removing the apps you don't want on Sense and it tell you which ones are safe to remove.
http://forum.xda-developers.com/showthread.php?t=710009
Hope this helps a little.
Some apps for us the rooted...shootme or drocap to take pictures of your screens, titanium backup, wifi tether, etc.
Appreciate the help everybody! Only thing I am still seeking an answer for is swype on my inc if anybody can guide me.
Thanks
khanam said:
Appreciate the help everybody! Only thing I am still seeking an answer for is swype on my inc if anybody can guide me.
Thanks
Click to expand...
Click to collapse
Here you go. I use the red skinned Swype, looks great and works great.
http://forum.xda-developers.com/showthread.php?t=701198
Thanks! Just realized one more thing. I cant seem to be able to use skype over wifi only. Is this verizon's way of using up my minutes one way or another?
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).
After perusing the forums for a while I'm considering loading a new ROM/Kernel. Maybe I'm to much of a noob to know but I can't find a thread that lays out the structure of Android. The stuff I can find assumes that I am already on intimate terms with this stuff, but I'm not.
I flashed CWM 3.1.0.1 which allowed me to clear caches and reset the battery gauge which has really helped. In trying to go further I'd like to piece the structure of the system together so I know where I am in the bigger scheme of things. I rely on the Epic for work. I can't afford to go down the wrong path and find myself in a far away town relying on a hotel internet connection to get back up off the ground. The picture I have is this:
Root lets me do the things I have mentioned before. Namely clear caches, backup my phone, reset battery meter, run some utilities to aid in device management. Similar to root or SU on *nix systems.
ROM drives the hardware and basic user interface, seems to me to be equivalent to the boot ROM and some lower level of OS functionality
Kernel is the actual software that runs on the device. This would be some OS and phone system overlay and the basic applications that show up in your applications folder. This provides your Sprint connection, network interface and the like
Applications are the other things that you actually run on the phone like games, social media programs GPS etc. Some come wrapped with a kernel, or they could be pick and choose.
I'm a bit fuzzy on where the ROM leaves off and the Kernel begins, maybe someone can clarify this.
Which leaves me here:
I see stuff that makes flashing new kernels and ROMs sound as if they are a magic elixir. I see posts that make it sound as if its a playground for folks who are hobbyists. Some posts talk about things that don't work any more with this flash or that. Where is the list of stuff that works and does not work for various mods?
My needs are very basic.
I need a reliable phone.
I need reliable Google mail & calendar (there are a few advantages to outsourcing corporate email to google).
Usable but not mission critical texting and GPS.
Better battery life.
This phone is for business. I do not need: social media, games, gadgets, widgets, toys.
Any light you can shed on the subject to help a brother out is appreciated.
Root = Elevated privilege access.
Kernel = The software that drives the phone.
Rom = The files on the phone's storage.
Apps = Also files on the phone's storage.
Root gives you the ability to do things the phone manufacturer did not intend for you to be able to do. (Think limited user account on Windows/Linux).
The Kernel is like the "engine" of the phone, w/o it the phone does nothing.
The Rom is the files on the phone, some are used by the kernel in order to make the phone work.
Apps... you know what these are. =]
The kernel controls the device, it has the drivers for hardware to make that hardware work.
The kernel is a Linux kernel built specifically for the device (phone) it will be run on.
The Rom is a collection of files to be installed onto the phone.
The Rom contains the operating system (the part that makes it an "android").
A Rom also includes apps, might include a theme (modifications to images, colors), and possibly numerous other modifications to the "stock" files.
The "stock" files, or a "stock" Rom, is what we are given by Sprint.
The different custom Roms you see available here on XDA are basically the stock files, modified by someone to their liking.
Some include a theme to give a custom look, most include modifications to make things "better" (ie hacked Sprint Hotspot, the 6 or 8 Lockscreen mod, etc).
There are many other aspects at play here, and much more that could be said about each item you listed, but the above is a generalized rundown.
Android runs on top of Linux, so the more familiar you are with Linux the better off you will be.
Do yourself a favor and take the time to read as much as you can, Google is your best friend.
=]
I'm using twa_priv's Jelly Bean ROM with SGT7 enhancements on my (first-generation) Kindle Fire, and wanted to install and use WhatsApp on this device.
Not having an Android phone, I found that the instructions here worked well: use Bluestacks on my PC to help get the needed code to install and start up WhatsApp. But when I actually tried to enter a chat on WhatsApp, the application kept crashing.
After seeing that someone else was having the same problem, and looking through the logcat.txt, I figured out that the crash has something to do with a bitmap/image operation in WhatsApp. That led me to a workaround, and now I can use WhatsApp on my Kindle Fire running CM10.
The relevant setting is found in Settings -> Chat preferences -> Wallpaper. I simply set it to "No wallpaper" (it's the conversation, not the background, that matters to me!). But I found it also works if I choose an image somewhere in my filesystem ("Android System"); selecting "WhatsApp" prompts me to download the WhatsApp Wallpaper package, which I don't really care to do. Just don't set it to "Default" -- that's what leads to the app crashing.
This workaround works using WhatsApp Messenger 2.8.4930. Hope this helps others!
Update for WhatsApp 2.9.2871
With the latest version of WhatsApp as of this writing (2.9.2871) running on twa_priv's version of the CM10.1 port, I no longer have to set the chat wallpaper to "No wallpaper" to avoid a crash when entering chats. I'm not sure whether it's because of a fix in CM10.1 or in WhatsApp, but that's one less workaround needed. Hurray!
ezekiel_quacks said:
With the latest version of WhatsApp as of this writing (2.9.2871) running on twa_priv's version of the CM10.1 port, I no longer have to set the chat wallpaper to "No wallpaper" to avoid a crash when entering chats. I'm not sure whether it's because of a fix in CM10.1 or in WhatsApp, but that's one less workaround needed. Hurray!
Click to expand...
Click to collapse
I have recently bought a kindle fire and was hoping to use whatsapp on it. I was pleased to find the recent messages re this, however I am a middle-aged grandmother and I'm sorry but they may just as well be written in an alien language from another planet! Is there any way instructions can be given to me that I could easily follow? Thank you for any help.
you can use Whatsapp if you are willing to use a custom ROM...
mario's mum said:
I have recently bought a kindle fire and was hoping to use whatsapp on it. I was pleased to find the recent messages re this, however I am a middle-aged grandmother and I'm sorry but they may just as well be written in an alien language from another planet! Is there any way instructions can be given to me that I could easily follow? Thank you for any help.
Click to expand...
Click to collapse
Before I attempt to do so, I'd have to first ask some preliminary questions:
1. Which version of the Kindle Fire are you using? My instructions were based on my experiences on the first generation Kindle Fire, so if you have something different, then I'm not 100% sure this will work for you.
2. Are you running the default software/firmware for the Kindle Fire?
3. If so, are you willing to install a custom firmware (like the various kinds being discussed on these forums), or would you prefer to stick with the default firmware? Installing a custom firmware ("flashing a custom ROM") is not for the technologically faint of heart, even though it's in practical terms not that difficult.
I'm not sure if my instructions will work with the default ("stock") firmware on any version of the Kindle Fire. But depending on your answers, I might still be able to offer some pointers...
ezekiel_quacks said:
Before I attempt to do so, I'd have to first ask some preliminary questions:
1. Which version of the Kindle Fire are you using? My instructions were based on my experiences on the first generation Kindle Fire, so if you have something different, then I'm not 100% sure this will work for you.
2. Are you running the default software/firmware for the Kindle Fire?
3. If so, are you willing to install a custom firmware (like the various kinds being discussed on these forums), or would you prefer to stick with the default firmware? Installing a custom firmware ("flashing a custom ROM") is not for the technologically faint of heart, even though it's in practical terms not that difficult.
I'm not sure if my instructions will work with the default ("stock") firmware on any version of the Kindle Fire. But depending on your answers, I might still be able to offer some pointers...
Click to expand...
Click to collapse
Thank you,
1. How can I find this out? I've looked on the box and the two small leaflets that came with it and all I can see is Model Number D01400? I have literally just bought it.
2. I presume I am running the default/firmware as I haven't made any changes or downloaded anything - would you agree?
3. I'm willing to give anything a go - as long as I can understand what I am supposed to be doing and also as long as it is not going to cause any lasting damage.
Actually I think I should not have bought the kindle and what I wanted was an android tablet - my mistake. But if by installing anything you suggest this would enable me to download Whatsapp - and any other app that Amazon does not seem to allow - then I would be happy. Is this what may be achieved?
Thanks again, sorry I'm not good at all this technical stuff!
mario's mum said:
Thank you,
1. How can I find this out? I've looked on the box and the two small leaflets that came with it and all I can see is Model Number D01400? I have literally just bought it.
2. I presume I am running the default/firmware as I haven't made any changes or downloaded anything - would you agree?
3. I'm willing to give anything a go - as long as I can understand what I am supposed to be doing and also as long as it is not going to cause any lasting damage.
Actually I think I should not have bought the kindle and what I wanted was an android tablet - my mistake. But if by installing anything you suggest this would enable me to download Whatsapp - and any other app that Amazon does not seem to allow - then I would be happy. Is this what may be achieved?
Thanks again, sorry I'm not good at all this technical stuff!
Click to expand...
Click to collapse
Swipe down from the top of the screen. And press more, from there go to the device section, What does the software version say?
read the beginner's guide first
mario's mum said:
Actually I think I should not have bought the kindle and what I wanted was an android tablet - my mistake. But if by installing anything you suggest this would enable me to download Whatsapp - and any other app that Amazon does not seem to allow - then I would be happy. Is this what may be achieved?
Thanks again, sorry I'm not good at all this technical stuff!
Click to expand...
Click to collapse
Well, let me be the first to say that I admire your courage, at least! :good: You need to understand, though, that you probably have to do more than just install some app -- this is more like completely replacing the operating system (e.g., Windows) on your PC with another one (e.g., MacOS X). If you make it through these minefields, you'll effectively have a pretty fully functional Android tablet, but it's generally more for the technically minded (i.e., geeks) to attempt and maintain.
Maybe a good first step would be for you to go here and read through a Beginner's Guide: http://forum.xda-developers.com/showthread.php?t=1552547. If that's too intimidating, then you probably won't be able to get to the point where I can help you install Whatsapp on your Kindle Fire.
ezekiel_quacks said:
Well, let me be the first to say that I admire your courage, at least! :good: You need to understand, though, that you probably have to do more than just install some app -- this is more like completely replacing the operating system (e.g., Windows) on your PC with another one (e.g., MacOS X). If you make it through these minefields, you'll effectively have a pretty fully functional Android tablet, but it's generally more for the technically minded (i.e., geeks) to attempt and maintain.
Maybe a good first step would be for you to go here and read through a Beginner's Guide: http://forum.xda-developers.com/showthread.php?t=1552547. If that's too intimidating, then you probably won't be able to get to the point where I can help you install Whatsapp on your Kindle Fire.
Click to expand...
Click to collapse
Hello again, thanks for that - but after reading what you've said I don't think my courage extends that far! Anyway, not just so I can Whatsapp when I've got it on my phone. I'm hoping I'll get used to the kindle in time - while I save up for what I really wanted in the first place!
Thanks again.
might be just as well...
mario's mum said:
Hello again, thanks for that - but after reading what you've said I don't think my courage extends that far! Anyway, not just so I can Whatsapp when I've got it on my phone. I'm hoping I'll get used to the kindle in time - while I save up for what I really wanted in the first place!
Click to expand...
Click to collapse
You may find that the Kindle Fire, other than its awkward launcher, may fit the bill just fine as you get used to it. Try browsing the Amazon App Store, and you will probably find most of the apps you'd regularly use on a generic Android tablet. As for Whatsapp, you can't really run it with the same account on more than one device at the same time anyway, so it might be just as well that you only use it on your phone. :cyclops:
ezekiel_quacks said:
You may find that the Kindle Fire, other than its awkward launcher, may fit the bill just fine as you get used to it. Try browsing the Amazon App Store, and you will probably find most of the apps you'd regularly use on a generic Android tablet. As for Whatsapp, you can't really run it with the same account on more than one device at the same time anyway, so it might be just as well that you only use it on your phone. :cyclops:
Click to expand...
Click to collapse
Oh that's made me feel a bit better about the Whatsapp!, and you're right I am getting used to it. Thanks for your advice.
Aplogies for bumping an old thread
I have a rooted Kindle Fire (first generation).
I would like to install WhatsApp Messenger on it. I don't have a CUSTOM-ROM. This is rooted without any customizations.
Is there something I can do, to get this started? Any pointers in the right direction are appreciated.
Well, it's been over a year since my original post, and I no longer run Whatsapp on my Kindle Fire now, so I can't be sure what works now. But I'd suggest you follow the links in the first post on this thread for starters, and see if that gets you anywhere.
Hi, a new guy here!
I recently became a happy owner of 32Gb wi-fi only N7. I’m familiar with software dev (windows developer for 20 years with some work on unix) and customization/modding/flashing process (mostly for satellite receivers). However this is my first tablet and my first Android device so I could use some help
I successfully unlocked, rooted and installed custom recovery on my N7. I would like to get to a bare bones state of the N7 and then slowly add new features/programs to it when it becomes necessary for me. So I would like to remove all non essential parts that were preinstalled on my N7.
I was under impression that I could uninstall programs using N7 UI after device gets rooted. However it seems that for majority of the apps I still only have an option to disable.
I shelled into N7 and looked around. It seems that all (majority?) of the apps are in /system/apps folder. Can I simply remove the apps and their files from that folder? Does this folder only contain user apps or does it also have system apps that are essential for N7 to function? Is there a chance to brick it by removing something (everything?) from that folder?
I searched on a forum for a list of apps that are safe to remove. I thought it would exist since it seems to be something many of us would be interested in doing. I didn’t find the list. If there is such a thing and someone could direct me there, it would be great!
Given that I can remove apps by deleting them from that folder safely, I still have a question what each app does and how important it is. Is safe to assume that any app that has a wheel with a drive belt on it as an icon in apps screen on N7 is system app and has to stay?
I have two keyboard app installed – one is Android keyboard and one is ASUS keyboard. Judging by the name 2 of these are essential since Android is the OS and ASUS is the manufacturer. But do I really need two of them?
If there is a resource/thread that discussed something similar, please let know. I look forward to learn from anyone on this forum!
_Diver said:
Hi, a new guy here!
I recently became a happy owner of 32Gb wi-fi only N7. I’m familiar with software dev (windows developer for 20 years with some work on unix) and customization/modding/flashing process (mostly for satellite receivers). However this is my first tablet and my first Android device so I could use some help
I successfully unlocked, rooted and installed custom recovery on my N7. I would like to get to a bare bones state of the N7 and then slowly add new features/programs to it when it becomes necessary for me. So I would like to remove all non essential parts that were preinstalled on my N7.
I was under impression that I could uninstall programs using N7 UI after device gets rooted. However it seems that for majority of the apps I still only have an option to disable.
I shelled into N7 and looked around. It seems that all (majority?) of the apps are in /system/apps folder. Can I simply remove the apps and their files from that folder? Does this folder only contain user apps or does it also have system apps that are essential for N7 to function? Is there a chance to brick it by removing something (everything?) from that folder?
I searched on a forum for a list of apps that are safe to remove. I thought it would exist since it seems to be something many of us would be interested in doing. I didn’t find the list. If there is such a thing and someone could direct me there, it would be great!
Given that I can remove apps by deleting them from that folder safely, I still have a question what each app does and how important it is. Is safe to assume that any app that has a wheel with a drive belt on it as an icon in apps screen on N7 is system app and has to stay?
I have two keyboard app installed – one is Android keyboard and one is ASUS keyboard. Judging by the name 2 of these are essential since Android is the OS and ASUS is the manufacturer. But do I really need two of them?
If there is a resource/thread that discussed something similar, please let know. I look forward to learn from anyone on this forum!
Click to expand...
Click to collapse
I don't have the energy right now to address every app one at a time, but I'll nudge you in the right direction. That should help you start tinkering.
The Nexus 7 is very popular in this community because it's intentionally more open, and less bloated, than much of the competition.
That being said, sure there are apps you could uninstall if you decide to. Some of the custom ROM's will have probably already have done this for you, but may create little unexpected quirks here and there.
The first thing you'll want to do is backing everything up thoroughly. I would use Titanium Pro (you'll see it referred to as Tibu a lot), to backup all apps and settings. Then I would use the Google Nexus 7 toolkit (found in the forums here) to do a backup, as well as make a nandroid backup.
Ok, so you're ready to tinker. Well, if you bought Titanium Pro from the app store, you've already got all you really need. First, use titanium to freeze an app you don't feel you need, and don't think is required. Re-boot, go about your daily routine, and see if all is ok. Continue on in this manner. Once you've frozen everything you're interested in, and made sure all is well, you can probably go ahead and uninstall them through Tibu. Freezing them should generally make them not start up anyways, so unless the tiny amount of space they take up is a concern, that's really all you generally need to do *.
* Ok, sometimes you have to fully uninstall things you don't want, but this should get you plenty to tinker with for now.
bladebarrier,
Thanks for your response. I understand the approach you suggested – disabling apps one at a time and then when they all disabled and device is working to my liking for a while I could uninstall them.
However, I’m somewhat frustrated with a sheer number of apps that I have out of the box and I can’t find a good description of what they do. For example:
Mobile Network Configuration
Google Partner Setup
Google Services Framework
Searching online doesn’t yield definitive answers if it’s something I need or will N7 work without them. I have google play store and google play services installed – does store app require services? Reading a bit about it doesn’t make it seem so, but I’m not 100% sure. So I was wondering if there is a list of apps that are required for N7 well being and that cannot be removed no matter what.
For example, Black Viper has an excellent example of what I’m looking for but for windows nt services: (can't post a link)
This page explain what each service is, what it does and if it’s safe to disable it depending on configuration you’re seeking – minimal set, typical, out of box of experimental. I would love to find something like that for N7 system apps
I installed CWM recovery when I rooted and as far as I can understand I does NAND backups. I plan on moving the backup file from the device to my desktop and keeping it there for safety reason.
The Tibu process that you described, as far as I understand (and I might be wrong here) is basically equivalent of disabling the apps using native N7 setting app, rebooting, using it for a while and then removing .apk and .odex (or simply app_name.*) files from system/apps folder. Tibu just makes it easier. Did I get that right?
And it’s still removing one app/widget at the time. I’d like to clean it out completely first and start from that point. So Tibu will probably not help me there. So my main Q is still out there – can I brick it by removing everything from system/app? Are there only user apps there or essential system apps as well? With CWM back up file on hand will I be able to recover if my experiment goes bad?
> * Ok, sometimes you have to fully uninstall things you don't want, but this should get you plenty to tinker with for now.
One of the reasons I want to have them removed is to clean up the list of apps I have on N7. Right now I have 5 pages of apps and I have little idea what they do and if I need them – I had Korean keyboard installed for example.
As I mentioned I’m a newb in this area, so maybe my approach is a bit dumb, so please be patient with me
_Diver said:
bladebarrier,
Thanks for your response. I understand the approach you suggested – disabling apps one at a time and then when they all disabled and device is working to my liking for a while I could uninstall them.
However, I’m somewhat frustrated with a sheer number of apps that I have out of the box and I can’t find a good description of what they do. For example:
Mobile Network Configuration
Google Partner Setup
Google Services Framework
Searching online doesn’t yield definitive answers if it’s something I need or will N7 work without them. I have google play store and google play services installed – does store app require services? Reading a bit about it doesn’t make it seem so, but I’m not 100% sure. So I was wondering if there is a list of apps that are required for N7 well being and that cannot be removed no matter what.
For example, Black Viper has an excellent example of what I’m looking for but for windows nt services: (can't post a link)
This page explain what each service is, what it does and if it’s safe to disable it depending on configuration you’re seeking – minimal set, typical, out of box of experimental. I would love to find something like that for N7 system apps
I installed CWM recovery when I rooted and as far as I can understand I does NAND backups. I plan on moving the backup file from the device to my desktop and keeping it there for safety reason.
The Tibu process that you described, as far as I understand (and I might be wrong here) is basically equivalent of disabling the apps using native N7 setting app, rebooting, using it for a while and then removing .apk and .odex (or simply app_name.*) files from system/apps folder. Tibu just makes it easier. Did I get that right?
And it’s still removing one app/widget at the time. I’d like to clean it out completely first and start from that point. So Tibu will probably not help me there. So my main Q is still out there – can I brick it by removing everything from system/app? Are there only user apps there or essential system apps as well? With CWM back up file on hand will I be able to recover if my experiment goes bad?
> * Ok, sometimes you have to fully uninstall things you don't want, but this should get you plenty to tinker with for now.
One of the reasons I want to have them removed is to clean up the list of apps I have on N7. Right now I have 5 pages of apps and I have little idea what they do and if I need them – I had Korean keyboard installed for example.
As I mentioned I’m a newb in this area, so maybe my approach is a bit dumb, so please be patient with me
Click to expand...
Click to collapse
Removing Google framework services is a big no-no. To be honest, the easiest way to accomplish what you want is installing a custom ROM like CyanogenMod, especially since you've done all the prep work for such a thing.
Once you install any official CM build it is as close to app-less as you can get on a modular OS like this.
littleemp said:
Removing Google framework services is a big no-no. To be honest, the easiest way to accomplish what you want is installing a custom ROM like CyanogenMod, especially since you've done all the prep work for such a thing.
Once you install any official CM build it is as close to app-less as you can get on a modular OS like this.
Click to expand...
Click to collapse
that's what i suspected! i thought that google framework would be something essential, but there is not much easily available information there to arrive at that conclusion
since i'm new to this, i thought i should stay away from any rom flashing until i get a bit more familiar with a device, terminology and stuff like that. i'm looking at the "[ROM] CyanogenMod 10.1 [OFFICIAL]" thread and i'm not sure about half of the terms - GAPPS, PSA, Nightlies i do know what ROM is, I do know what kernel is, virtual machine, etc. But it's applied to the platform that I have little experience with, so it makes me a little bit uneasy
_Diver said:
bladebarrier,
Thanks for your response. I understand the approach you suggested – disabling apps one at a time and then when they all disabled and device is working to my liking for a while I could uninstall them.
However, I’m somewhat frustrated with a sheer number of apps that I have out of the box and I can’t find a good description of what they do. For example:
Mobile Network Configuration
Google Partner Setup
Google Services Framework
Searching online doesn’t yield definitive answers if it’s something I need or will N7 work without them. I have google play store and google play services installed – does store app require services? Reading a bit about it doesn’t make it seem so, but I’m not 100% sure. So I was wondering if there is a list of apps that are required for N7 well being and that cannot be removed no matter what.
For example, Black Viper has an excellent example of what I’m looking for but for windows nt services: (can't post a link)
This page explain what each service is, what it does and if it’s safe to disable it depending on configuration you’re seeking – minimal set, typical, out of box of experimental. I would love to find something like that for N7 system apps
I installed CWM recovery when I rooted and as far as I can understand I does NAND backups. I plan on moving the backup file from the device to my desktop and keeping it there for safety reason.
The Tibu process that you described, as far as I understand (and I might be wrong here) is basically equivalent of disabling the apps using native N7 setting app, rebooting, using it for a while and then removing .apk and .odex (or simply app_name.*) files from system/apps folder. Tibu just makes it easier. Did I get that right?
And it’s still removing one app/widget at the time. I’d like to clean it out completely first and start from that point. So Tibu will probably not help me there. So my main Q is still out there – can I brick it by removing everything from system/app? Are there only user apps there or essential system apps as well? With CWM back up file on hand will I be able to recover if my experiment goes bad?
> * Ok, sometimes you have to fully uninstall things you don't want, but this should get you plenty to tinker with for now.
One of the reasons I want to have them removed is to clean up the list of apps I have on N7. Right now I have 5 pages of apps and I have little idea what they do and if I need them – I had Korean keyboard installed for example.
As I mentioned I’m a newb in this area, so maybe my approach is a bit dumb, so please be patient with me
Click to expand...
Click to collapse
Tibu requires root access, in order to perform what we're discussing. I'm relatively new to JB, but I can't imagine any stock settings replicating its capabilities.
As far as a whole bunch of apps being in your list, that's sort of the way Android works. Think of it like "superfetch", or whatever that term was in Windows Vista. Basically, two things happen when you boot. Android looks at a list of apps that are designed to start on boot, and also apps that it expects you may want to run in the future. Both of these are designed to make the device run smoother overall, and it will kill apps if extra ram is required and they are not in use. Certain Android apps require themselves to run at all times. Some of these are apps like Tasker (if you're using tasker profiles), some of these are system apps that make the device function, some of these are apps that maintain widgets or background monitoring (weather apps, gmail, calendar).
Now, there are two ways to go about sorting what is bloat, and what is there because Android decided to load it. You can install an app called Autostarts, that will give an insight into apps that start up when certain criteria are met. You can also use it to stop those apps from queuing up at those trigger points. This is another root required app, and while I purchased it long ago, may have a free version as well. It's time consuming to use, and not perfect, which is why Tibu is better for flat out locking down unwanted apps.
Back to my initial thoughts though, you will see apps in your system list that you haven't touched since boot, because Android tries to anticipate your needs. People used to use "task killers" to close the apps, and came to realize that unless one is causing a real problem, it's just going to go back into the cached app list again anyways, thus reducing battery life when it has to load it over and over again. "Task killer" is a dirty word around XDA, unless you're using it to close an app that doesn't just go into the background like a good little app should.
Basically, you're going to start playing whack-a-mole if you want your list to remain as small as possible, at all times, and yet still actually use the device for anything interesting. You can reduce it, via various methods, and if this were a device from say "insert-name" brand, and was loaded with bloat apps, by all means you should clean those out. However, I think you'll find that while google does install things that aren't needed, or even used by everyone, it's mostly not a big issue.
Check out Better Battery Stats, in the XDA forums. It's an app that shows a pretty good picture of what is actually going on when you're not looking, and can provide data on how to improve your performance. It's probably a better way to start delving into what processes are actually being used, and which ones are just basically harmless. You'll also learn a good bit about how Android works from the Dev's explanations of many of the processes.
---------- Post added at 08:36 PM ---------- Previous post was at 08:32 PM ----------
_Diver said:
that's what i suspected! i thought that google framework would be something essential, but there is not much easily available information there to arrive at that conclusion
since i'm new to this, i thought i should stay away from any rom flashing until i get a bit more familiar with a device, terminology and stuff like that. i'm looking at the "[ROM] CyanogenMod 10.1 [OFFICIAL]" thread and i'm not sure about half of the terms - GAPPS, PSA, Nightlies i do know what ROM is, I do know what kernel is, virtual machine, etc. But it's applied to the platform that I have little experience with, so it makes me a little bit uneasy
Click to expand...
Click to collapse
Make sure whichever ROM you use, if you decide to, supports your HSPA+ model. There is a separate development section in the Nexus 7 forums, for those of us that have the HSPA+ version. We are the minority, as the Nexus 7 was initially released as a wifi only tablet.
bladebarrier said:
Tibu requires root access, in order to perform what we're discussing. I'm relatively new to JB, but I can't imagine any stock settings replicating its capabilities.
Click to expand...
Click to collapse
i do have SU privileges, so what i was talking about was disabling an app thru N7 setting screen and then when i deem the app ok to remove, going to adb shell and removing the actual file.
i just did this:
mount -o remount rw /system
rm iWnnIME_Kbd_White.apk
rm iWnnIME.apk
and it removed the japanese keyboard. however when i go back to app screen under settings, i still see it but now it has a grey icon with a SD symbols in the corner. so it appears it recognizes that the app is gone, but it's still referenced in the list. i pushed the files back using NRT and it all back to the way it was. so looks like my idea of cleaning the list by removing the apk might not fly.
and now I wonder how Tibu uninstalls the apps.
bladebarrier said:
People used to use "task killers" to close the apps, and came to realize that unless one is causing a real problem, it's just going to go back into the cached app list again anyways, thus reducing battery life when it has to load it over and over again.
Click to expand...
Click to collapse
I understand the notion of apps being in the cache and being removed when more RAM is needed, however the purist in me just doesn't want the junk apps to be there in first place However there is a lot of validity to these of your words:
bladebarrier said:
Basically, you're going to start playing whack-a-mole if you want your list to remain as small as possible, at all times, and yet still actually use the device for anything interesting.
Click to expand...
Click to collapse
My wife got Kindle Fire HD recently and she's been using it happily. While I was thinking why would anyone want a closed up system (well, more closed up system then Nexus), she's been using it and I've been frustrated with my N7 so i might just let it go and enjoy the japanese and korean keyboards anyway
bladebarrier said:
Make sure whichever ROM you use, if you decide to, supports your HSPA+ model.
Click to expand...
Click to collapse
i'm wifi only
ngshniq every
i think i found what i was after: http wiki.cyanogenmod.org/wiki/barebones (url modified since i still can't post urls). this wiki page has the list of app with a short description and if it's safe to remove. it also has additional information that explains why i still saw the reference to the app in the list when apk file was deleted:
looks like i need to pay attention to 2 additional files:
/data/system/packages.xml
/data/system/packages.list
i bet I would find a reference to the apps in these and i would need to remove it in order to have the app disappear from the app list. i'll play around a bit more and report back
One thing, could you explain your reasoning behind wanting to delete everything but the essentials? Do you have a particular goal in mind or is it because of your windows background? Because if so, you should know that android operates very differently when compared to windows, and such, the requirements to keep your device working in tip top shape vary greatly.
In my opinion, with your current limited knowledge of each process/app inner workings, what you're trying to do surefire way to break something beyond repair and needing to use a factory image to get back to zero. A custom ROM will be much safer and yield the exact same results that you're looking for. (Eventually, once you understand what each thing does, then this manual approach could satisfy your needs)
Note: GApps are the basic Google apps to flash on top of the barebones system. Gmail, Play store, and the framework.
Nightlies are experimental builds compiled nightly by a bot with the latest CyanogenMod code available.
Sent from my Nexus 7 using Tapatalk HD
My goal was to simplify my approach to N7 by removing anything that I don’t need now and slowly adding all necessary components as I get familiar with it. But it seems at this point that this approach is a bit more complicated as thought it would be.
So I think I would leave it alone for now and revisit this later
_Diver said:
My goal was to simplify my approach to N7 by removing anything that I don’t need now and slowly adding all necessary components as I get familiar with it. But it seems at this point that this approach is a bit more complicated as thought it would be.
So I think I would leave it alone for now and revisit this later
Click to expand...
Click to collapse
From what you've done manually, you're clearly far ahead of a new user when it comes to understanding linux/unix.
If you want to lock down parts of what google implements, purely to keep it minimalistic, I would agree with the above poster. Go for one of the popular ROM options that are available, like CM, and work your way backwards. The Nexus 7 only has as much bloat as you allow it to have via the settings. This is another reason why Better Battery Stats is an excellent way to make sure your device isn't draining battery, yet isn't locked down. The other day I noticed an app that kept fetching my position, even though the case was closed (magnetic sleep mode). It turned out I forgot to disable the tracking in google maps (why it was defaulted to ON, I have no idea). BBS showed me what was running during the sleep phase, and I fixed it when I woke up the next morning after wondering why my battery dropped.
The Kindle Fire is a great option, because it doesn't require any of this fussing about. My woman loves hers. LOVES IT. Personally, I like to tinker a bit, and I'm too invested in Android apps to not have access to the play store. The Nexus 7, is for people like what you find here. We like to tinker, and make everything custom. At the same time, you could spend all day trying to figure out why EntriesRefresh_wakelock is your highest partial wakelock count, at 60seconds per 7 hours, or you can find that you just went 7 hours and only used 6% of the battery, even though you've been connected to wifi, texting, emailing, and checking the weather and news, the whole time. Not bad, honestly.
The biggest investment you can do for your Nexus, is probably getting a case that magnetically puts it to rest when you close it. After that, learn about the settings that drain battery in the background. Then, get Tasker and play around that (it's like programming, without the need to learn the code). After that, go to a custom ROM, or dig out Tibu, and basically start customizing which apps you will use. If that doesn't pass the time long enough, you can literally make your own ROM and put together exactly what you want. Whether the performance will be that much better or not, and whether you'll spend most of your day trying to look for coding errors, is up to you. I don't have the patience to code, but you're a coder, so what is broccoli to me, may be bacon to you.