• Android thread V-garychencool finally rooted his phone and got ICS edition
    10,001 replies, posted
Is the Galaxy Ace 2 a good choice for a low-mid range phone?
no
[QUOTE=Ezhik;37884470]no[/QUOTE] What about the HTC One V?
[QUOTE=PyroCF;37882702][B]HEY FOOLS[/B] WANT YOUR ANDROID DEVICE TO SOUND LIKE SHIT?!?!?! WELL LOOK NO FURTHER [URL="http://forum.xda-developers.com/showthread.php?t=1888366"]You can now run every EQ that ever existed at the same time for the worst experience ever[/URL] [URL="http://forum.xda-developers.com/showthread.php?t=1666203"]I should also install this guys themes for the most satirical device ever[/URL] [IMG]http://img.tapatalk.com/3e2b21c5-a1a9-6f9f.jpg[/IMG][/QUOTE] [IMG]http://forum.xda-developers.com/attachment.php?attachmentid=1222049&d=1343256959[/IMG] kill me
Now it just needs bloom to be perfect.
[QUOTE=PyroCF;37882702][B]HEY FOOLS[/B] WANT YOUR ANDROID DEVICE TO SOUND LIKE SHIT?!?!?! WELL LOOK NO FURTHER [URL="http://forum.xda-developers.com/showthread.php?t=1888366"]You can now run every EQ that ever existed at the same time for the worst experience ever[/URL] [/QUOTE] ~Ultra Sound Enhacement Technology~
Okay phone works again, but the home button doesn't.. w/e it works
Well, I'm back on HTC stock Sense ICS because of ROM stability issues. It's definitely a large cause of lag on my Vivid/Raider. The de-sensed ROM was actually smooth. But at least my FM radio works now!!
It's not very often I facepalm but jesus this is totally in need of it. [URL="http://forum.xda-developers.com/showthread.php?t=1914724"]Read the problem in the thread title and then read his "solution"[/URL]
So how often do you guys charge your phone in terms of full charge cycles per day? For me it's 2. So I charge my phone overnight and I end up charging it at school (to save money at home and to be more efficient), then I charge it again in the evening, then leave it charging overnight. In total, it's about 2 full charges.
[QUOTE=Hunt3r.j2;37878808]I can see the problem. You have ATK.[/QUOTE] Is there a better task killer? What's the problem with using it?
[QUOTE=garychencool;37886219]So how often do you guys charge your phone in terms of full charge cycles per day? For me it's 2.[/QUOTE] every evening after heavy use, every 2 nights if I'm just texting
[QUOTE=garychencool;37886219]So how often do you guys charge your phone in terms of full charge cycles per day? For me it's 2. So I charge my phone overnight and I end up charging it at school (to save money at home and to be more efficient), then I charge it again in the evening, then leave it charging overnight. In total, it's about 2 full charges.[/QUOTE] Recharge my phone once I get home from school, and if i've used it and it's gone down again; recharge it before i go to bed
i always charge when going to bed, my phone lasts me all day
My phone battery is weird. I haven't really been doing anything on it, but it drained quickly from 100% down to around 50% and now it's levelling off. [img]http://i.imgur.com/c42GF.png[/img]
[QUOTE=venn178;37886225]Is there a better task killer? What's the problem with using it?[/QUOTE] Don't use any - you're asking for data corruption/battery wear in exchange for a placebo effect in regards to any perceived performance gain. Android doesn't work like Windows in regards to task management. If you find an app to be a considerable issue in terms of background performance/battery degradation - remove it and find an alternative. A bad app is going to be a bad app even if you're killing it with a task manager. [url]http://android-developers.blogspot.com/2010/04/multitasking-android-way.html?m=1[/url]
[QUOTE=Sgt. Jerky;37887482]Don't use any - you're asking for data corruption/battery wear in exchange for a placebo effect in regards to any perceived performance gain. Android doesn't work like Windows in regards to task management. If you find an app to be a considerable issue in terms of background performance/battery degradation - remove it and find an alternative. A bad app is going to be a bad app even if you're killing it with a task manager. [url]http://android-developers.blogspot.com/2010/04/multitasking-android-way.html?m=1[/url][/QUOTE] Nope. I've recorded noticeable performance gains on stock ROMs by killing off background processes because Android doesn't leave enough RAM left for the OS to run properly. If it gets below a certain threshold it starts to stutter really bad, usually occuring on devices with 512MB or lower RAM. Even occurs on devices just using stock apps. Dianne Hackborn is also not somebody to be trusted regarding performance whatsoever. Here's a statement from her brilliant mind about performance on the Nexus S. [url]https://plus.google.com/105051985738280261832/posts/2FXDCz8x93s[/url] [quote]Looking at drawing inside of a window, you don’t necessarily need to do this in hardware to achieve full 60fps rendering. This depends very much on the number of pixels in your display and the speed of your CPU. For example, Nexus S has no trouble doing 60fps rendering of all the normal stuff you see in the Android UI like scrolling lists on its 800x480 screen.[/quote] Absolutely ridiculous. The Nexus S struggles to perform any sort of scrolling fluidly, even lists of text. I used it for hours when it launched, and I own the Galaxy S which suffers from the same issues even when running AOSP ROMs. This is a Google engineer who is incapable of noticing blatant issues with device smoothness, somebody who would never be hired on the Windows Phone or iOS software teams.
[QUOTE=garychencool;37886219]So how often do you guys charge your phone in terms of full charge cycles per day? For me it's 2. So I charge my phone overnight and I end up charging it at school (to save money at home and to be more efficient), then I charge it again in the evening, then leave it charging overnight. In total, it's about 2 full charges.[/QUOTE] My Galaxy S Fascinate usually goes for about a week before I need to charge it. Granted, I never use it now that I have my tablet.
[QUOTE=Sgt. Jerky;37887482]Don't use any - you're asking for data corruption/battery wear in exchange for a placebo effect in regards to any perceived performance gain. Android doesn't work like Windows in regards to task management. If you find an app to be a considerable issue in terms of background performance/battery degradation - remove it and find an alternative. A bad app is going to be a bad app even if you're killing it with a task manager. [url]http://android-developers.blogspot.com/2010/04/multitasking-android-way.html?m=1[/url][/QUOTE] thanks hun~
Task Killing will make your device faster if it's a low end phone like mine. I would task kill games when I'm done with them. Why? Because the devs slapped on a BillingService part of the app that still runs when you close the game. Very annoying indeed.
I never really noticed slowdown, I was just assuming general upkeep is a good thing. Don't run unnecessary shit, etc. Oh well, I never notice the slowdown so I guess I'm fine.
I just put my phone on charge when I sleep. I laugh at people when they say their alarm doesn't go off because their phone died. There's an obvious solution.
so i have two unused androids that are just sitting there not in service, i want to take them apart and make something with them any suggestions?
[QUOTE=garrynohome;37887634]Nope. I've recorded noticeable performance gains on stock ROMs by killing off background processes because Android doesn't leave enough RAM left for the OS to run properly. If it gets below a certain threshold it starts to stutter really bad, usually occuring on devices with 512MB or lower RAM. Even occurs on devices just using stock apps. Dianne Hackborn is also not somebody to be trusted regarding performance whatsoever. Here's a statement from her brilliant mind about performance on the Nexus S. [url]https://plus.google.com/105051985738280261832/posts/2FXDCz8x93s[/url] Absolutely ridiculous. The Nexus S struggles to perform any sort of scrolling fluidly, even lists of text. I used it for hours when it launched, and I own the Galaxy S which suffers from the same issues even when running AOSP ROMs. This is a Google engineer who is incapable of noticing blatant issues with device smoothness, somebody who would never be hired on the Windows Phone or iOS software teams.[/QUOTE] While she may be wrong about performance of scrolling, that doesn't necessarily mean she's wrong about everything regarding android development - if she was, she wouldn't have her job, regardless of whether or not you personally believe she should or shouldn't. You mention recording noticeable performance gains by killing background processes. Was that using a task killer, or by manually killing off the problem applications? Even on devices with stock apps and low RAM, the issue isn't necessarily android - it's poorly designed applications that cause the problem (yes, even google/stock apps can be built with issues). When set properly, OOM will properly handle the issue of foreground processes not having enough available RAM to operate android-smoothly (I say android-smoothly because you and I both know that there is no iOS/WinPhone comparable smoothness to be found on any android device). I know this because I have maintained an OG Droid all the way up through Jellybean with considerably solid performance (800mhz cpu and 256mb RAM mind you). Not once have I had an issue of crashing, lagging, or stuttering due to low available RAM (outside of the NORMAL pre-jellybean UI jitteriness), nor have I used any sort of task killing app. Yes, occasionally task killers will catch an app stuck in some sort of weird loop or hang and they ARE good for freeing that RAM back up, but the point I'm trying to make is that task killers are a nuke-from-orbit solution to a specific problem. It may [I]seem[/I] to make a difference, but more often than not the problem with apps that hog RAM is that they don't stay dead after they've been killed - they resurrect almost as soon as you kill them (Google Maps NetworkLocationService is a particularly nefarious example of this). In theory, task killers mediate this issue by killing the app once it rebirths, but in doing so on low spec devices (like you mentioned), you have to take into account that this action isn't free - it comes at the cost of cpu cycles and system I/O, as well as the loss of RAM space that has to be dedicated to the task killer app. This can cause any number of instabilities and jitteriness as the applications fight each other and take resources away from whatever foreground operation you or your phone is trying to perform. In the long run, the best way to manage the issue of low RAM is to double check your OOM settings to make sure they're operating at levels appropriate for your device, as well as figuring out which apps are causing issues and freezing/replacing/uninstalling them. I mention here the OOM settings because this is a native function of the Android OS - one that doesn't require extra dedicated RAM to handle memory conservation. I know you are obsessive about the performance of Android's UI, so I'm not surprised by your sensitivity to UI jitteriness from low available RAM. I just can't believe that task killers are still around when there are native tools in android to tackle this issue, namely OOM and the ability to freeze apps in ICS/JB. I hope my post doesn't come across as standoffish, as I really do understand that low-spec devices often struggle hard with RAM conservation, but task killers are a band-aid solution to the problem.
is ics to jb worth the trouble?
[QUOTE=Rika-chan;37889414]is ics to jb worth the trouble?[/QUOTE] project butter is the best. it also looks a lot nicer. do it.
There are a fair amount of steps and it requires a full wipe and a chance of bricking if you fuck one thing up. [editline]3rd October 2012[/editline] I have the ics version of this rom [url]http://forum.xda-developers.com/showthread.php?t=1854212[/url]
Depends on the phone, my nexus and nexus 7 are practically unbrickable. You can screw something up and just flash stock back onto it.
Just rooted my Galaxy Note and put CM10 on it. The battery life is so much better for some reason.
[QUOTE=Sgt. Jerky;37889408]While she may be wrong about performance of scrolling, that doesn't necessarily mean she's wrong about everything regarding android development - if she was, she wouldn't have her job, regardless of whether or not you personally believe she should or shouldn't. You mention recording noticeable performance gains by killing background processes. Was that using a task killer, or by manually killing off the problem applications? Even on devices with stock apps and low RAM, the issue isn't necessarily android - it's poorly designed applications that cause the problem (yes, even google/stock apps can be built with issues). When set properly, OOM will properly handle the issue of foreground processes not having enough available RAM to operate android-smoothly (I say android-smoothly because you and I both know that there is no iOS/WinPhone comparable smoothness to be found on any android device). I know this because I have maintained an OG Droid all the way up through Jellybean with considerably solid performance (800mhz cpu and 256mb RAM mind you). Not once have I had an issue of crashing, lagging, or stuttering due to low available RAM (outside of the NORMAL pre-jellybean UI jitteriness), nor have I used any sort of task killing app. [/QUOTE] I brought her up because she was wrong about the entire UI, not just scrolling. She clearly was incapable of seeing the difference, or she had never actually used an Android device before. If it's the former then she is indeed unqualified, and if Apple of Microsoft saw that she'd probably be on the do not hire list until she got some eye examinations. Back to the actual issue. Occurs when using either a task killer app or using built in app stopping, on devices with 512MB RAM of lower. I've noticed it seems to be when it drops below ~60-65MB free that it occurs. I really disagree with the notion that it's bad apps. How could Google and all the third party developers keep making bad apps when some of those same developers make WP7 and iOS ones that work perfectly? [editline]3rd October 2012[/editline] Oh and I don't know why actual task killing apps exist either considering it's built in, no arguments there.
Sorry, you need to Log In to post a reply to this thread.