-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Apps people recommend???
- Thread starter nybadboy6
- Start date
-
- Tags
- lg marquee
Bionic Chronic
Android Enthusiast
I also purchased the Marquee as my first smartphone. After tinkering with it for 3 weeks now I have came to rly like these apps:
Battery Info https://market.android.com/details?...ubWF0aGlzLmFuZHJvaWQudWx0aW1hdGViYXR0ZXJ5Il0.
Lookout Security https://market.android.com/details?...esult#?t=W251bGwsMSwxLDEsImNvbS5sb29rb3V0Il0.
Android Assistant (Many features that help conserve battery plus usefull settings that do not come stock) https://market.android.com/details?id=com.advancedprocessmanager&feature=order_history
Rings Extended (Adds more settings in the sounds settings such as adding custom ringtones for notifications and setting contact ringtones without going to music and add as ringtone first.) https://market.android.com/details?....android.rings_extended&feature=order_history
Adobe Reader https://market.android.com/details?id=com.adobe.reader&feature=order_history
Adobe Flash 11 (Comes stock with Adobe Flash 10) https://market.android.com/details?id=com.adobe.flashplayer&feature=order_history
Dolphin HD Browser (One of the best i have found, also has add-ons such as color themes and remember password and kill all other processes) https://market.android.com/details?id=mobi.mgeek.TunnyBrowser&feature=order_history
-(Browse Faster [kills other processes to allow Dolphin to browse faster.] https://market.android.com/details?id=mobi.mgeek.browserfaster&feature=order_history )
-(Password Manager https://market.android.com/details?id=mobi.mgeek.PasswordManager.Lite&feature=order_history )
-(Red Theme https://market.android.com/details?id=mobi.mgeek.TunnyBrowser.Theme.V5.Red&feature=order_history )
If you want to change UI themes instead of that Regular GingerBread Look I highly recommend the following:
Go Launcher EX https://market.android.com/details?id=com.gau.go.launcherex&feature=order_history
-Ice Cream Sandwich [Android 4.0] Themehttps://market.android.com/details?id=kov.theme.ics&feature=order_history
-Black and Green Theme https://market.android.com/details?id=com.gau.go.launcherex.theme.cb&feature=search_result
-Neon Blue Theme (One of my fav's though I mix and match icons to make a more personalized theme) https://market.android.com/details?id=com.BahagHariArts.BlueNeonGoTheme&feature=search_result
---------there are many themes you can search the market and find them-----------
**Also There is Go SMS Pro which has a great variety of skins as well plus adding a lot of other neat options that do not come with the stock sms program.**
Go SMS Pro https://market.android.com/details?id=com.jb.gosms&feature=search_result
Now for fun apps I recommend these:
Pandora Radio https://market.android.com/details?id=com.pandora.android&feature=order_history
Google Music (If you have setup Google Music on your Google Acct. you can use this app to stream music you uploaded to google music.) https://market.android.com/details?id=com.google.android.music&feature=order_history
Drag Racing ( I normally don't play games on my phone and this is the only one. Very addicting so figured Id share it) https://market.android.com/details?id=com.creativemobile.DragRacing&feature=order_history
Shazamm (If you ever wondered what the song that is playing on the radio was? This app will listen and tell you +MORE) https://market.android.com/details?id=com.shazam.android&feature=order_history
Police Scanner https://market.android.com/details?id=com.berobo.android.scanner&feature=order_history
Gas Buddy (Weather you wonder what the lowest gas price around is or just need to get to a gas station and don't know where the closest one to you is, this app is awesome) https://market.android.com/details?id=gbis.gbandroid&feature=order_history
Barcode Scanner ( It will scan regular barcodes and QR (Quick Response Codes and give you info on those scanned items.) https://market.android.com/details?id=com.google.zxing.client.android&feature=order_history
__________________________________________________________________
Well these are the apps I have found to be useful and/or entertaining. Hope it is useful and Enjoy!
+++ Also if you want to use a couple other apps such as (SetCPU [cpu clocking modification], Screenshot, WiFi tether, or ES Explorer) You need to root your phone. Rooting is only beneficial for those who intend on using root required apps and to delete certain bloatware. If you decide to root your device you can private message me and I will tell which apps you can remove safely from the (Boost Mobile) LG Marquee.
!!(DISCLAIMER: the forums and members posting on them are not responsible for bricking or damage to your device, root at own risk)!!
Bionic Chronic
Android Enthusiast
Cannot take credit here but this is a useful app on rooting the LG Marquee.
--Even though it is for the LG Enlighten it will work 100%--
Also Not sure if this makes a difference but, I downloaded the most current Marquee drivers from the Lg site itself. Other than that great video by Knoxville, I cannot take any credit for his video.
How to ROOT Boost Mobile LG Marquee - YouTube - LG Marquee / LG Enlighten OneClickRoot
--Even though it is for the LG Enlighten it will work 100%--
Also Not sure if this makes a difference but, I downloaded the most current Marquee drivers from the Lg site itself. Other than that great video by Knoxville, I cannot take any credit for his video.
How to ROOT Boost Mobile LG Marquee - YouTube - LG Marquee / LG Enlighten OneClickRoot
Bionic Chronic
Android Enthusiast
No problem. The least I can do is post what I found useful in case others can find it useful as well.
Bionic Chronic
Android Enthusiast
Not a problem. I know the market can sometimes be difficult especially when there are similar apps with the same name.. I am glad my post could help.
Thanks man quick question if i use the dolphin browser i can delete the stock broswer and there be no problems with the phone. On the the Go Launcher what exactly is that???? too save battery life i downloaded something called juice defender unsure how to use it but all i did was click enable hope doesnt mess anything up...now for a task killer what is recommended or is juice defender a task killer as well.
Bionic Chronic
Android Enthusiast
I recommended Android Assistant. It has Task killer plus many other options in one app, that is what I use so I am not sure about Juice Defender. GO Launcher EX is sort of like a theme launcher like in Windows. You can use it to apply different themes instead of the boring Stock Android theme, and change around your UI (User Interface). Here is a good in depth video on GO Launcher EX: Android Apps In Depth - 02 - Go Launcher EX - YouTube .
As for the browser, I am not sure. I wouldn't recommend uninstalling it since I am not sure if the phone needs the browser for anything. I do know you couldn't uninstall it without root anyway.
mvaness
Android Enthusiast
If you are interested, go to to getjar's website. They have a lot of paid apps for free. The site is legit, they compensate developers, and it is endorsed by Android Forums. Well, maybe not endorsed, but they approve.
Beautiful Widgets, BeWeather Pro, and lots more!
Hope this helps...
Beautiful Widgets, BeWeather Pro, and lots more!
Hope this helps...
mvaness
Android Enthusiast
Just a suggestion, but I would hold off on downloading a bunch of "utility apps" for killing tasks. There is a lot of debate about their effectiveness or if they are even needed. There are a lot of threads about this topic in the android forums.
I am not trying to discredit any apps or any others suggestions, just trying to point out to do your research, you will be better off in the end.
hope this helps.
Android is designed to not need a task-killer. You can look at the description of how Android works by Googling android development, and looking at Google's explanatory documents. They are quite lengthy, but a very interesting read if you are interested in the inner-workings of android. Many developers I have seen on forums strongly recommend to not get any task-killers.
sik00
Android Enthusiast
3 more apps I'd like to add that I've been using for a while now..
AirDroid: Lets you manage your phone from a web browser over your Wifi
https://market.android.com/details?id=com.sand.airdroid&hl=en
RemoteDroid: Lets you use your Android device as a wireless keyboard and mouse over your Wifi (because I'm lazy
)
https://market.android.com/details?id=com.joshsera&hl=en
ColorNote: Simple notepad. I use checklists for work a lot, and I love the checklist on this app. Fast and simple.
https://market.android.com/details?id=com.socialnmobile.dictapps.notepad.color.note&hl=en
AirDroid: Lets you manage your phone from a web browser over your Wifi
https://market.android.com/details?id=com.sand.airdroid&hl=en
RemoteDroid: Lets you use your Android device as a wireless keyboard and mouse over your Wifi (because I'm lazy
)https://market.android.com/details?id=com.joshsera&hl=en
ColorNote: Simple notepad. I use checklists for work a lot, and I love the checklist on this app. Fast and simple.
https://market.android.com/details?id=com.socialnmobile.dictapps.notepad.color.note&hl=en
Why i wouldn't use a task killer and just let things take its course.....
A lot of people have asked us what the best app is for killing tasks? Well, the answer is none of them. Sure there are some nice apps out there for killing tasks, but the fact is you just don’t need one with Android. In fact, most developers won’t even look at your logcat file if they see you running a task killer app on your Android-based phone.
To clear things up about this, Google’s blog has finally put this debate to rest about why a task killer is unnecessary, as well as why there are certain services that run in the background all the time, I’m sure at one time or another you’ve seen them and asked yourself “Why do those services keep starting after I kill them?”. Below you can read about when applications stop. If you want to learn more about this topic to can read the full post by clicking here.
1) Killing a task does NOT SAVE BATTERY. It WASTES BATTERY. If a process isn’t doing ANYTHING, then it isn’t using ANY BATTERY AT ALL. The ACT of killing it consumes CPU cycles, which means BATTERY.
2) Applications that don’t restore properly are badly written applications. This is not a fault of ANDROID.
3) The “task killer” in the rom is nothing new. Its been there for a while, and in fact, has been part of UNIX since the beginning of time. The usefulness of the integrated task killer is related to forcing THAT application’s current state to die so that THAT application can be reloaded from fresh. This is an alternative to starting up a whole bunch of other applications just to force that one to get reclaimed.
And of course, the really really big ugly problem with task killers:
SOME PROCESSES WANT TO RUN, and when you KILL them, they will just start right back up. So now you have an automatic task killer continually killing some process that keeps respawning forever. This will REALLY kill your battery FAST.
It has nothing to do with killing off misbehaving applications, which is a good thing (and is actually built into android). It has to do with using task killers (especially AUTOMATIC task killers) to save memory or battery. A task killer is NOT going to save memory or battery.
A lot of people have asked us what the best app is for killing tasks? Well, the answer is none of them. Sure there are some nice apps out there for killing tasks, but the fact is you just don’t need one with Android. In fact, most developers won’t even look at your logcat file if they see you running a task killer app on your Android-based phone.
To clear things up about this, Google’s blog has finally put this debate to rest about why a task killer is unnecessary, as well as why there are certain services that run in the background all the time, I’m sure at one time or another you’ve seen them and asked yourself “Why do those services keep starting after I kill them?”. Below you can read about when applications stop. If you want to learn more about this topic to can read the full post by clicking here.
When does an application “stop”?
A common misunderstanding about Android is the difference between a process and an application. In Android these are not tightly coupled entities: applications may seem present to the user without an actual process currently running the app; multiple applications may share processes, or one application may make use of multiple processes depending on its needs; the process(es) of an application may be kept around by Android even when that application is not actively doing something.
The fact that you can see an application’s process “running” does not mean the application is running or doing anything. It may simply be there because Android needed it at some point, and has decided that it would be best to keep it around in case it needs it again. Likewise, you may leave an application for a little bit and return to it from where you left off, and during that time Android may have needed to get rid of the process for other things.
A key to how Android handles applications in this way is that processes don’t shut down cleanly. When the user leaves an application, its process is kept around in the background, allowing it to continue working (for example downloading web pages) if needed, and come immediately to the foreground if the user returns to it. If a device never runs out of memory, then Android will keep all of these processes around, truly leaving all applications “running” all of the time.
Of course, there is a limited amount of memory, and to accommodate this Android must decide when to get rid of processes that are not needed. This leads to Android’s process lifecycle, the rules it uses to decide how important each process is and thus the next one that should be dropped. These rules are based on both how important a process is for the user’s current experience, as well as how long it has been since the process was last needed by the user.
Once Android determines that it needs to remove a process, it does this brutally, simply force-killing it. The kernel can then immediately reclaim all resources needed by the process, without relying on that application being well written and responsive to a polite request to exit. Allowing the kernel to immediately reclaim application resources makes it a lot easier to avoid serious out of memory situations.
If a user later returns to an application that’s been killed, Android needs a way to re-launch it in the same state as it was last seen, to preserve the “all applications are running all of the time” experience. This is done by keeping track of the parts of the application the user is aware of (the Activities), and re-starting them with information about the last state they were seen in. This last state is generated each time the user leaves that part of the application, not when it is killed, so that the kernel can later freely kill it without depending on the application to respond correctly at that point.
In some ways, Android’s process management can be seen as a form of swap space: application processes represent a certain amount of in-use memory; when memory is low, some processes can be killed (swapped out); when those processes are needed again, they can be re-started from their last saved state (swapped in).
And basically saying.....A common misunderstanding about Android is the difference between a process and an application. In Android these are not tightly coupled entities: applications may seem present to the user without an actual process currently running the app; multiple applications may share processes, or one application may make use of multiple processes depending on its needs; the process(es) of an application may be kept around by Android even when that application is not actively doing something.
The fact that you can see an application’s process “running” does not mean the application is running or doing anything. It may simply be there because Android needed it at some point, and has decided that it would be best to keep it around in case it needs it again. Likewise, you may leave an application for a little bit and return to it from where you left off, and during that time Android may have needed to get rid of the process for other things.
A key to how Android handles applications in this way is that processes don’t shut down cleanly. When the user leaves an application, its process is kept around in the background, allowing it to continue working (for example downloading web pages) if needed, and come immediately to the foreground if the user returns to it. If a device never runs out of memory, then Android will keep all of these processes around, truly leaving all applications “running” all of the time.
Of course, there is a limited amount of memory, and to accommodate this Android must decide when to get rid of processes that are not needed. This leads to Android’s process lifecycle, the rules it uses to decide how important each process is and thus the next one that should be dropped. These rules are based on both how important a process is for the user’s current experience, as well as how long it has been since the process was last needed by the user.
Once Android determines that it needs to remove a process, it does this brutally, simply force-killing it. The kernel can then immediately reclaim all resources needed by the process, without relying on that application being well written and responsive to a polite request to exit. Allowing the kernel to immediately reclaim application resources makes it a lot easier to avoid serious out of memory situations.
If a user later returns to an application that’s been killed, Android needs a way to re-launch it in the same state as it was last seen, to preserve the “all applications are running all of the time” experience. This is done by keeping track of the parts of the application the user is aware of (the Activities), and re-starting them with information about the last state they were seen in. This last state is generated each time the user leaves that part of the application, not when it is killed, so that the kernel can later freely kill it without depending on the application to respond correctly at that point.
In some ways, Android’s process management can be seen as a form of swap space: application processes represent a certain amount of in-use memory; when memory is low, some processes can be killed (swapped out); when those processes are needed again, they can be re-started from their last saved state (swapped in).
1) Killing a task does NOT SAVE BATTERY. It WASTES BATTERY. If a process isn’t doing ANYTHING, then it isn’t using ANY BATTERY AT ALL. The ACT of killing it consumes CPU cycles, which means BATTERY.
2) Applications that don’t restore properly are badly written applications. This is not a fault of ANDROID.
3) The “task killer” in the rom is nothing new. Its been there for a while, and in fact, has been part of UNIX since the beginning of time. The usefulness of the integrated task killer is related to forcing THAT application’s current state to die so that THAT application can be reloaded from fresh. This is an alternative to starting up a whole bunch of other applications just to force that one to get reclaimed.
And of course, the really really big ugly problem with task killers:
SOME PROCESSES WANT TO RUN, and when you KILL them, they will just start right back up. So now you have an automatic task killer continually killing some process that keeps respawning forever. This will REALLY kill your battery FAST.
It has nothing to do with killing off misbehaving applications, which is a good thing (and is actually built into android). It has to do with using task killers (especially AUTOMATIC task killers) to save memory or battery. A task killer is NOT going to save memory or battery.