LoneWolfArcher
Silver Member
- Joined
- Dec 29, 2009
- Messages
- 1,808
- Reaction score
- 481
Only ICS? Dang!
This * infinity!
Come on Motorola, hurry up with ICS for the Razr!
Only ICS? Dang!
This * infinity!
Come on Motorola, hurry up with ICS for the Razr!
its a tad quicker than stock...otherwise its very similar to stock IMO. I haven't left Mozilla yet on my laptop, so there's not a ton of incentive to have chrome on my phone
Sent from my Galaxy Nexus using Tapatalk[/QUOTE
yeah I'm finding it to be the same speed. Spell correct works though, so I'll probably stick with it.
switching tabs is hard, and many pages load as white....and it takes awhile for it to render
after a few outcries and updates it'll probably be a much usable beta. Betas are of course...not finals. So I'm not expecting greatness yet. I don't mind waiting. I'll just keep using stock for the meanwhile
My Weather app is currently using 52. GoLauncher is using 60. 50 is not that much for an essential service, and I consider a browser to be an essential service.chrome is such a memory hog, even when you close all tabs and exit the app it's still using over 50mb ram.
This isnt 2010. Since GB that problem has pretty much vanished. I almost never had to force-close anything even on my Droid 1 after GB. Really, this "problem" has been resolved since Froyo. Thats why no one uses task killers anymore.android doesn't always manage it's memory efficiently hence the option to forceclose apps that are memory residents when they shouldn't be like chrome.
If you say so. I rarely have more than 20% of my RAM free, and my phone flies. I did benchmarks after I rooted and got rid of Sense and other memory-resident apps...the scrores are almost exactly the same.i'd understand if you have pages open and hit home key to do other tasks, but if no pages are open and all tabs are close and app is closed it should not reside in memory. this is another + for default browser and another - for chrome.