dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
9
share rss forum feed


ubermoe

join:2012-09-21
Jordan
reply to OZO

Re: An iPhone Lover's Confession: I Switched To The Nexus 4

I came thought all of the replies on this thread but your reply was a really weird. Let me talk in general, that an individual case cannot be taken as the official view for the platform. Both Android, iPhone, BB, Nokia, each of them has its own failures that is mostly related to software which is pretty easy, amazingly easy to "format" and then install a fresh copy of the OS with Android while it's hard with Nokia, BB, and iPhone. I don't mean factory reset but a complete OS deletion and replacement.

said by OZO:

A third party tool that kills app may not help (and why I should use a tool that closes an app).

Speaking of multitasking, actually users get fooled by the titles of the apps on Play Store and iOS Store. These apps do not make your phone operate better nor make it faster with so many apps running.

Seeing an app in the running tab doesn't mean it's consuming resources and is being executed, simply Android keep what we can call a reference to certain apps to make them ready when the app is needed, this reference is idle but is ready to be invoked when necessary. You must read this article:

Multitasking the Android Way: »android-developers.blogspot.com/···way.html

so basically, these apps are consuming your battery, yes, these "Task Killers" are the reason why your battery is dying faster as they kill everything related to any app causing Android to re-execute it again. Review process life-cycle in the same article.

said by OZO:

GPS may be in "Looking for location" for up to 10 min, while it shows 10 - 12 satellites connected. Battery may not show it's charged 100%, while it is connected to charger and you see that its voltage is already start dropping and, at the same time, it's percentage of "availability" is slowly growing ~10% per 8 hours (so to get it to "fully charged " state from let say 60% you have to charge it ... 24 hours). Next time it may start from different percentage (assigned to the same voltage).

that is pure personal experience. Did you try to factory reset? were you running a ROM?

said by OZO:

There is a lot of memory available, but suddenly you can't install a small new app. You have to find a third party tool, that clears OS's cache and only then you may do it again (and why I should remember to clear the cache manually? it's the OS's job, for god sake).

You sure you're talking about Android 2.3 and up specially Jelly Bean? If you did not try JB, I think you're missing a lot.

I used to be an iPhone user, tried 3G, 3GS, 4, then 4S. Then moved to Galaxy Nexus and I am running the latest JB version of Android. I can say that my life is way easier and I am much more productive in it. Phone design? software UI? both are getting better with every release.

Sure, I disagree with you, completely, but that doesn't mean I don't understand your points. I think it was an awful experience but make sure you try the right phone.

OZO
Premium
join:2003-01-17
kudos:2

You've cut just last part of my point and perhaps "conveniently" omitted the important premise, explaining why I mentioned third party tool, that kills app. Here is what I actually said:

said by OZO:

Apps may behave unexpectedly. Sometimes they work, sometimes they suddenly don't and the only way to get some predictability back is to reboot the phone... A third party tool that kills app may not help (and why I should use a tool that closes an app).

As you see, the question about third party tool that kills the app was rather a rhetorical one. If OS allowed user to exit apps and did its job of cleaning up OS resources properly, I'd never needed those third pary tools. I'd just exit the app, start it again and that's it. The problem is - it doesn't. First, OS doesn't offer a standard way to stop app from running and second, OS doesn't clean up system resources properly all the time. Why I've mentioned the latter? Because even if you find a way to kill the app and restart it again the problem may persist... The only solution in this case is to reboot the OS... ubermoe See Profile, my point was not about multitasking. You didn't get it and then called my post weird...

said by ubermoe:

that is pure personal experience. Did you try to factory reset? were you running a ROM?

Pure personal experience? Perhaps. But then you do your own homework and read many threads in XDT forum (and may other places), containing hundreds of posts each about the same problem, you may start thinking that may be it's not just simple as my personal experience. And yes, I did factory reset and tried many ROM's. They may behave differently, but what I've mentioned above is related to the design of OS itself, not to particular implementation or its version.

said by ubermoe:

You sure you're talking about Android 2.3 and up specially Jelly Bean? If you did not try JB, I think you're missing a lot.

You may find the answer to your question if you read my first post.

said by ubermoe:

Sure, I disagree with you, completely, but that doesn't mean I don't understand your points. I think it was an awful experience but make sure you try the right phone.

1. No. Based on what you've posted, I think you've missed my points. Please peruse what I've posted earlier.
2. So, as a solution your suggest me to "try the right phone"? HTC that cost me around $500 was not "the right phone"? It's not my hobby to buy, to test, and then to sell smartphones just to find the "right phone". It takes time, cost money and ... I have a life, you know. So, may be it's a solution for you, but not for me...
--
Keep it simple, it'll become complex by itself...


Cheese
Premium
join:2003-10-26
Naples, FL
kudos:1

Once again and for the last time, the problems you mention, are NOT NORMAL. Taking 10 min to lock onto GPS? That most certainly IS NOT an OS issue.


OZO
Premium
join:2003-01-17
kudos:2

said by Cheese:

Once again and for the last time,

Thank you so much and I really appreciate your difficult decision to stop that

And I already know that you think that GPS support (as well as WiFi networking and others) is not part of the Android OS... And if something is not working it's all the fault of the user, not OS. I've got that...
--
Keep it simple, it'll become complex by itself...


Cheese
Premium
join:2003-10-26
Naples, FL
kudos:1

1 recommendation

Holy shit, you are obtuse.


Happydude32
Premium
join:2005-07-16
kudos:1
reply to OZO

I’m currently inside of my house, on Verizon’s 3G network, on my Droid DNA I went to Google Navigation, and verbally dictated ‘Navigate To Best Buy’. From the moment I finished that statement until the moment it locked the GPS signal and fully loaded it was 12 seconds read to take me to the closest Best Buy. And now that I have a lock on the GPS satellites the two other places I had Google Nav take me load almost instantly.
--
iPhone: 4” 1136 X 640 Display, 1.30 GHz Dual Core Processor, 1 GB RAM
MyPhone: 5” 1920 X 1080 Display, 1.50 GHz Quad Core Processor, 2 GB RAM
So tell me, why is exactly is the iPhone so great?
Droid Does What Jobs Won’t Let You Do.



Cheese
Premium
join:2003-10-26
Naples, FL
kudos:1

said by Happydude32:

I’m currently inside of my house, on Verizon’s 3G network, on my Droid DNA I went to Google Navigation, and verbally dictated ‘Navigate To Best Buy’. From the moment I finished that statement until the moment it locked the GPS signal and fully loaded it was 12 seconds read to take me to the closest Best Buy. And now that I have a lock on the GPS satellites the two other places I had Google Nav take me load almost instantly.

My S3 is the same, it's almost instant. I load GMAPS and it's got my location in literally seconds.

It's obvious it's an issue with his phone.

OZO
Premium
join:2003-01-17
kudos:2

said by Cheese:

It's obvious it's an issue with his phone.

You can't keep your own promises, can you?
--
Keep it simple, it'll become complex by itself...


Cheese
Premium
join:2003-10-26
Naples, FL
kudos:1

That post, wasn't directed at you.



PeeWee
Premium
join:2001-10-21
Madera, CA

1 recommendation

reply to OZO

said by OZO:

said by Cheese:

It's obvious it's an issue with his phone.

You can't keep your own promises, can you?

Trying to get someone to go away does not make you right. However if you repeat it often enough you may not have to hear it any more. Didn't you post here to hear other opinions and help if necessary? Or are you merely trolling?
--
Iphone. Helping computer illiteracy become popular since 2007

OZO
Premium
join:2003-01-17
kudos:2

I post my personal experience and observations here. Sorry if it's not the same as yours. Repeating "it's an issue with his phone" is trolling in my books...
--
Keep it simple, it'll become complex by itself...



PeeWee
Premium
join:2001-10-21
Madera, CA

You actually sound like an Ifan trying to get validation for his misled opinions on an Android forum. It isn't going to happen. By the way did you really have these experiences or are you just repeating what you may have overheard? If you did have an android phone and had these problems where are your posts from that time?
--
Iphone. Helping computer illiteracy become popular since 2007


OZO
Premium
join:2003-01-17
kudos:2

And now you're trying to start the trolling of this thread too...
--
Keep it simple, it'll become complex by itself...



PeeWee
Premium
join:2001-10-21
Madera, CA

No. Actually, if you stiill have the phone let's fix it. Otherwise what are you looking for?
--
Iphone. Helping computer illiteracy become popular since 2007



Cheese
Premium
join:2003-10-26
Naples, FL
kudos:1
reply to OZO

It's you who is trolling...this thread was about someone switching, and you come in with your rant about YOUR problems claiming it's an Android problem.


Happydude32
Premium
join:2005-07-16
kudos:1

1 recommendation

reply to OZO

So what's the make and model of the phone and on what network? You fail to mention that in any of your trolling.



trparky
Apple... YUM
Premium,MVM
join:2000-05-24
Cleveland, OH
kudos:2
reply to OZO

said by OZO:

As you see, the question about third party tool that kills the app was rather a rhetorical one.

Android is programmed to kill tasks when an available RAM threshold is reached. When that available RAM threshold is reached it starts killing off old apps depending upon when they were last loaded. This is standard behavior and to use Task Killers is actually working against the memory management properties of Android.

This is straight out of the mouths of some of the best third-party ROM and kernel developers as well as Google themselves.
--
Tom
Boycott AT&T uVerse! | Tom's Android Blog | AOKP (The Android Open Kang Project)


Cheese
Premium
join:2003-10-26
Naples, FL
kudos:1
reply to Happydude32

No response...hmmmm


OZO
Premium
join:2003-01-17
kudos:2
reply to trparky

said by trparky:

Android is programmed to kill tasks when an available RAM threshold is reached. When that available RAM threshold is reached it starts killing off old apps depending upon when they were last loaded.

Indeed. But I was talking about the need of re-launching an app, that may start working weird. For example, app, that works with proximity sensor, suddenly stops doing what it's supposed to do. Or a softphone app suddenly stops registering its presence with SIP server. And no matter what you do with that app, it still misbehave. Obviously they have bugs... At this point the only solution offered by Android is to reboot the whole phone (reboot the OS)... If there was a way to correctly stop app (making sure that all system resources are taken back and recycled by system), then starting it again after that incident could help to avoid the reboot.
--
Keep it simple, it'll become complex by itself...


PeeWee
Premium
join:2001-10-21
Madera, CA

said by OZO:

said by trparky:

Android is programmed to kill tasks when an available RAM threshold is reached. When that available RAM threshold is reached it starts killing off old apps depending upon when they were last loaded.

Indeed. But I was talking about the need of re-launching an app, that may start working weird. For example, app, that works with proximity sensor, suddenly stops doing what it's supposed to do. Or a softphone app suddenly stops registering its presence with SIP server. And no matter what you do with that app, it still misbehave. Obviously they have bugs... At this point the only solution offered by Android is to reboot the whole phone (reboot the OS)... If there was a way to correctly stop app (making sure that all system resources are taken back and recycled by system), then starting it again after that incident could help to avoid the reboot.

What is it you want? What does this have to do with the OP?
--
Iphone. Helping computer illiteracy become popular since 2007


Cheese
Premium
join:2003-10-26
Naples, FL
kudos:1

said by PeeWee:

said by OZO:

said by trparky:

Android is programmed to kill tasks when an available RAM threshold is reached. When that available RAM threshold is reached it starts killing off old apps depending upon when they were last loaded.

Indeed. But I was talking about the need of re-launching an app, that may start working weird. For example, app, that works with proximity sensor, suddenly stops doing what it's supposed to do. Or a softphone app suddenly stops registering its presence with SIP server. And no matter what you do with that app, it still misbehave. Obviously they have bugs... At this point the only solution offered by Android is to reboot the whole phone (reboot the OS)... If there was a way to correctly stop app (making sure that all system resources are taken back and recycled by system), then starting it again after that incident could help to avoid the reboot.

What is it you want? What does this have to do with the OP?

I don't think he is going to answer...