All Things Android - Apps, Phones, Tablets - Discussion

If they're so bad, why did Google add one to Gingerbread?

They're a tool like anything else, if you use them wisely then yes they can be a good thing; if you use them poorly then there's a goof chance you'll just make things worse.

 

LOL yes and meh, ive done it to every phone ive had, not a single problem

Its probably a "safe" task manager. Like the one Samsung includes in TouchWiz. No?

 

That's a company site, and if it were untrue Motorola would have been apologizing like they had to do with the "if you don't like it, go elsewhere" comment earlier this year. I believe they know it's in their better interests to heed the suggestions... I think Motorola makes some awesomely stupid decisions, but they do know what they're doing.

If you want the same benefits, download "Autokiller Memory Optimizer" and use the "Aggressive" memory setting. That will set Android's core to kill off apps more aggressively, by itself... that way Android itself can gauge what apps and services to terminate without causing issues.

I include that with all my custom ROM's. It saves battery. Spare Parts also has that feature, but it's not saved on reboot... so you'd have to set it all the time. Autokiller has an option to run at boot, which is awesome.

 

Why? It is perfectly safe when done right. There are many OC/ UV kernels out there that both help performance and save battery.

Seems like a lot of your comments in this thread are based off no real knowledge of the android platform and phone hardware.

 

I have just started to learn "hardcorely" phone hardware and android phones. Does this thread's title say "Only aknowledged people allowed"? I don't think so. I learn over here, what's the problem with it?

Anyways...
The OC can only be done if you root the phone, correct? What are the safe OC levels to consider?

 

I believe then, Sony Ericsson is going the right way, since the bootloader is available and provided by SE. But, if THEY provide the bootloader, shouldn't it be included in the warranty? I mean, if SE gives users the option to use the bootloader, if in case of a crash, or something going wrong, shouldn't SE disable the warranty void in that case?

 

The problem is that you make statements as if you are knowledgeable on the subject. It's fine to be new and learning... but don't act as if you know everything.

As far as OCing, yes it is only with root. As far as safe level of overclocking, depends on the chipset and phone hardware. In general though, if you stick with kernels from well known developers, you will be good to go. That being said, OCing your phone isn't really a necessity... phones are pretty damn capable already. I just do it because I am bored, and a phone nerd

 

Usually it's stated with the kernel that you end up using. Each kernel has it's limits on how far you can overclock. I can go up to 1.6GHz with my Captivate, but it gets HORRIBLE battery life at 1.6GHz. I usually keep it at 1200MHz, because I can run it at the same voltage for 1200MHz as I can for 1000MHz, so I get extra performance with pretty great battery life.

BUT, since each SoC is manufactured in batches, each batch will have different properties. Example: Some Captivates can only overclock to a maximum of 1200MHz and they have to be overvolted to be stable, while some can be run at 1600MHz (like mine) completely stable. It's mostly just trial and error on what your device can handle.

An unlocked bootloader lets you flash different kernels and even replacement bootloaders... if you unlock it, you're messing with un-supported stuff and you're doing so at your own risk. Bricking your phone with an unlocked bootloader, you know what you're getting into before hand, and you know that what you did shouldn't be covered under warranty.

 

Have I stated that I know everything? I don't. It's more than obvious.

Anyways...

 

I have to agree, i understand where your coming from seeing as OC'ing in general can be labeled as "dangerous"

Correct! It depends on every CPU. the OC'ing is different for every one. My old phone was 528Mhz, i ran it consistantly at around 650Mhz. There are OC kernels that go up to 1Ghz for it.

My phone now is 1Ghz and normal OC's are up to 1.2Ghz, though there are some for 1.4

Personally, i wouldnt OC a phone more than 200 or 300Mhz. Something like the 1Ghz OC for my old phone at 528Mhz stock, i would consider dangerous. And i wouldnt OC a phone unless you actually needed to for performance.

 

Ah, the kernel is pretty much the "heart", and if you mess with it, the fault will be the doctor's fault, which is ours, right?

 

Yep, theres always a risk. its pretty small though. ive never had a problem. its worth the small risk for the benefits, as long as you follow instructions and dont do anything stupid, everything should be fine.

 

If I was rich, I would purposedly buy an HTC or another 1GHz smartphone, and OC it to super extreme levels like 4-5GHz, and watch what happened

But, I believe, as in GPU or CPU OC in PCs, the OC in phones requires lots of knowledge on how to root, etc?

 

Nope. rooting is very simple for most phones.
and even on others (less popular, cheaper phones with less development) it isnt too hard.

The OC'ing part is as simple as using a slider bar and sliding it up

 

I could see Apple doing that...I don't think Google should pull Google Maps from the iOS platform though...that just sounds like a bad idea.

I've told you that for ages, hah. But Hal and Step are right, if used properly, a task manager can be good for some people's usage scenarios. Gingerbread includes a manage apps screen that makes managing apps a bit easier. I still don't run a auto task manager mostly out of lazyness and the whole "if it ain't broke to me, why fix it" philosophy I tend to have. I just let the phone do it's thing.

Yep but it's harmless. I've had mine OC'd to 1.2 ghz for months now, from the previous 600 it had stock. It's nice.

I'm just saying that you see tweets and stuff deleted from corporate accounts all the time. People say things that turn out to not be true and such. Granted I didn't see the updated version of the Engadget article.

Indeed, rooting and overclocking is a fairly uncomplicated procedure on most phones. You might have to install a custom kernel for the overclocking and/or undervolting but that's also fairly simple.

 

Wait, so OC'ing phones doesn't yeld the same risks and potential damage as, a laptop GPU, for example? Why is that, shouldn't a laptop GPU be more resistant?

 

There's always inherent risks, you could cause instability if you overclock too high, but usually that's easily preventable. It also can be a source of heat....it's got to go somewhere...so your phone may get warmer (i suspect its this heat that has caused the adhesive holding down my Droid 1's membrane keyboard to fail around the middle causing it to bubble up a bit.)

 

Why?

Why shouldn't Google reserve Google Maps for the Android platform?
It becomes another feather in it's hat, another selling point over the iPhone.


IMO, at some point Google need to decide whether they want to compete with Apple or pander to their spoilt brat style of doing business.
And if they want to compete, I think they need to start playing hardball.

 

Yeah...

Actually, where does all the heat go? I know this is a weird question, but where does it go? I mean, I only feel the battery get hot, I don't feel the inside...

 

Google already does have google navigation as an android exclusive.

Google is still first and foremost a search company, and iPhone users provide a huge amount of traffic. I highly doubt they would rather bing, or someone else swoop in and replace google maps on the iPhone. Doesn't really seem necessary to take google maps away.

I personally like that google isn't "playing hardball" as you stated. They have a good strategy imo, and closing google maps would take away from the image they have built as a more open company. Clearly their strategy is working, as android is seeing obscene levels of growth. Taking away google maps from iOS would just cause unnecessary tension between apple and google, and allow an other competitor to sweep up ALL iPhone users.

 

I'm fully aware that the navigation element of Google Maps is an Android exclusive. I don't personally feel that really has any bearing on this matter though.

If they're going to be dropped as the iPhone's stock maps program, what difference does it make if they remove it a bit sooner?
Why should it be Apple's decision to dump Google when they're good and ready, why shouldn't Google get to choose the timing and leave Apple in the lurch?



And I respectfully disagree, I think you're wrong - Google is, first and foremost, an advertising company and they get none of the advertising revenue from iPhones as Apple have all that tied up.

Google is as an aside the pre-eminent search engine, people choose to use Google, no matter what platform they're on.
Removing Google Maps wouldn't stop iPhone users using Google to search the web, because like everyone else they want to use a search engine that'll do the job.



I don't believe that choosing to drop Maps support for the iPhone would have nearly as big a negative impact on Google as it would for Apple, who would be left rather embarrassingly with an OS that would be lacking in comparison to their competitors'.

 

Anybody...??

https://market.android.com/details?id=com.google.android.apps.docs

 

I've already used it for its OCR capabilities. Pretty awesome.

 

Nice! I haven't gotten a chance to actually use it yet, but I've got it downloaded. For some reason it takes me forever to actually get around to using an app I've downloaded.

 

Yeah that app seems cool for that feature, I downloaded it but haven't gottena chance to actually use it yet

 

Scratch my earlier comment about mostly running at 1.2GHz. I'm officially defaulting to 1.4GHz. I ran 1.4GHz all day yesterday and got 22 hours of solid usage with 9% remaining. Score! I compiled my own CM7 kernel with some special compiler flags.

 

Anyone up for making a collection of recommended Android software by category like the Windows software? Must be a better way than going through 138 pages...

 

So, I've been having fun getting back into android, and finding all sorts of new apps and whatnot for my LG Optimus S. It's time to get into the rooting side of things, but it's been over a year since I've rooted anything, and it was fuzzy back then.

I found this post ( [How-To] Rooting LS670ZVD with GingerBreak (no reverting and OTA works too!) - Android Forums)

I'm assuming this is the best/easiest way to root my phone? I like the idea of the one click rooting processes, but I haven't found any out there for the Optimus, and I figure it's probably good to know how to do it the long way anyways.

Is there anything I should be on the lookout for? Anything that the guide doesn't mention? Will I lose my apps if I root? (I've been downloading the free ones from amazon for awhile now, I'm getting a decent collection of paid apps for free).

 

GingerBreak seems to be a little hit-and-miss.

SuperOneClick is probably the rooting method of choice, provided you're not ion Gingerbread (2.3).

 

No, not currently on Gingerbread. I took the latest OTA update from Sprint. I'm on Froyo 2.2.2. (LS670ZVD)

I'll take a look at SuperOneClick.
Thanks for the info.

 

@Blake:

I used this [How-To] Guide to rooting with software version LS670ZVD (OUTDATED) - Android Forums

It says outdated for the newer one you linked to, but hey i know it worked

 

Engadget reviewed the Galaxy s2.... it only makes the wait for the device harder. I WANT IT NOW!

Samsung Galaxy S II review -- Engadget

"For a handset with such a broad range of standout features and specs, the Galaxy S II is remarkably easy to summarize. It's the best Android smartphone yet, but more importantly, it might well be the best smartphone, period. Of course, a 4.3-inch screen size won't suit everyone, no matter how stupendously thin the device that carries it may be, and we also can't say for sure that the Galaxy S II would justify a long-term iOS user foresaking his investment into one ecosystem and making the leap to another. Nonetheless, if you're asking us what smartphone to buy today, unconstrained by such externalities, the Galaxy S II would be the clear choice. Sometimes it's just as simple as that."

 

Me gusta!


Too bad it's 700€...

And the TouchWiz UI draws me back too. I hated the TouchWiz 3.0 UI on my S7550... But I think I cannot compare them...?

 

I told my brother to skip the Droid X and wait for the GSII, I hope some carriers pick it up. Samsung has really outdone the competition...

 

Definitely cannot compare them. Touchwiz 4 actually has some useful additions, and if you use launcher pro you will get rid of the iphone-ish icons.

 

I don't know if it's my fanboyism talking, but I found the XPeria Arc more... Unique in terms of design.

SAMOLED+ Is simply gorgeous! The viewing angles are outstanding! Better than Xpera Arc's counterpart, which is still a very good display I must say.

Only if it wasn't so expensive...

Anyways, the only differences between the Xperia arc and the GSII are the CPU, GPU and display. OS-wise and feature-wise they are pretty much the same, right?

 

I think I'm developing the same feeling(s) towards the Galaxy S2 as I had about the original Galaxy S.

I know I should want it, I know on paper it's the best there is but, for some reason, I find myself unmoved.

 

I read the review earlier, it breaks my heart. It looks SO good D:

 

Perhaps it's because the shape is very iPhone-ish?

 

Except it isnt?

 

Seems to be in my opinion : 1 physical button, 1 glass revesting the entire front part ( as engadget mentioned ), form is the same ( pretty much )...
Except the back is different.

 

You are describing pretty much any modern slate style smartphone. There is only so much variation available to manufacturers.

 

The Xperia series "escaped" from that modern style, HTC is pretty unique too...

There is still much creativity as I mentioned, but they don't use it at full potential ( Samsung for example ).

 

Yes, there's only so much variation when it comes to designing a large, touchscreen-based handset but Samsung are really iPhone-y in their designs - much more so than other Android handsets.

The Galaxy S looked a lot like the iPhone 3G/S, the Galaxy Ace is very similar to the iPhone 4 to mention but a couple of more obvious examples.
And then there's TouchWiz itself...


I don't think that's got anything to do with it though, because I very nearly bought an iPhone4 last summer.

 

You described pretty much every component in the phone. Saying "the only differences" implies that these phones are similar. They aren't. Completely different class of phone.

please stop judging the SAMOLED+ and the xperia arc screen from reviews in pictures. As has been mentioned previously, unless you have seen both of these screens in person, you really cannot compare them.

 

Oh i completely agree that the samsung galaxy s was VERY iphone like. I do not however think that is the case with the gs2. They share some similarities, but it is not nearly the carbon copy that the original was.

Also I can somewhat see where your lack of enthusiasm comes from. While I am extremely excited for this phone, and know it will be awesome- I am not as thrilled as I was about the nexus one. For me, I guess I still have issues with the materials used in the Galaxy S line. Sure, plastic is durable and lightweight and I understand why samsung uses it, but i still appreciate aluminum/ hefty phones. This phone meets most of what I want in a new phone, but it still isn't the holy grail for me. So I am excited, but only to a limited extent.

 

What do you mean with "different class of phones"? The Arc is also a Gingerbread 2.3 phone, but the UI is different... Ofcourse the CPU and GPU on the GSII is MUCH better, hence the 250€ increase over the Arc, but I believe, being both v2.3, are similar OS-wise and feature-wise.

 

One is a current high end flagship, the other is a flagship but is no longer high end. Different class of phone.

The arc is grouped in with past gen high end devices like the desire HD and galaxy S.

 

It's not quite as bad but I would still say it's much more iPhone-y than any other brands - HTC, SE, Motorola, LG, none of them look as much like iPhones as the Galaxy S2.
I think it's the single central hardware button that does it.

It's not really that either. I don't think there'll ever be a 'holy grail' of phones, new technologies are being developed all the time, what your ideal phone would be now is unlikely to still hold true in a year because some new technology will have come along that will force you to re-evaluate your needs and wants.
So I tend just to look at what's available now and make a decision.

And to that end, the Galaxy S2 is the best phone announced to date, so I don't get why I'm not taken on it.
Maybe it's just the knowledge that I'm not going to buy one...

 

I agree that samsung does need to find a more unique, cohesive design direction-- as right now they are building functional, albeit generic looking hardware. That is one thing I definitely give motorola and HTC credit for-- their devices have a unified design direction.