[Q] RAM, GPS and call volume questions - Captivate Q&A, Help & Troubleshooting

Hello,
I wiil start with the RAM. I've searched the forums for an answer to the lack of ram and people are saying the current kernel isn't supporting 512 ram which is probably bull**** because I saw a Desire HD of a friend, and it uses all the RAM. Other people say that the other Ram goes to graphic use, which is wierd, because again, the Desire HD has 512 RAM.
So my question is did someone knows the real answer? Because I'm pretty disappointed that I have 150 free RAM after I'm killing all the tasks, and some games are laggy from time to time (Angry Birds (espacially Rio), Fruit Ninja). Maybe we can even sue Samsung for publishing false specs XD
My second question is about the GPS, I'm using Phoenix ultimate rom, did anyone tried it with this fix: http://forum.xda-developers.com/showthread.php?t=957164 and saw better results? The GPS in this rom is better then other roms but i'm still find it unusable.
My thirs nd last question is that there's a problem I've saw in all the roms I've been using. When I call someone the volume is high for something like 5-10 sec and then become lower, and the volume in the call itself is pretty low and I can't talk in crowdy places. I know there's a method to increase the volume but I'm not sure how and which volume is recommended. If someone can explain me it will be great!
Thanks in advance, Elad!

For the first question.
first of all you are using 150 ram... rather than having that much left. and I dont think there is any rom right now for the captivate that use all the ram..
2. my phone also never gets good gps. just send it back to at&t and keep getting a new one until you have good gps.
3. i really dont know... sorry..

So you say this this it's the rom that doesn't support? It's really hard for me to believe this because there's a lot of devices that use 2.1 and 2.2 and uses all of the 512 mb.. :/
And for the second answer I'm not living in USA I bought it on ebay because its basebands support my mobile operator basebands lol

For your 3rd question, have you tried different modems?

first of all, you need to read up on how RAM is used in linux and android. free ram is WASTED ram. there are 100 threads on here about that topic alone. please search

studacris said:
For your 3rd question, have you tried different modems?
Click to expand...
Click to collapse
I don't know how to use other modem, is there a guide or something? How will I know if the modem is supporting 850 and 2100 (this is the only basebands my mobile operator supports.. I need them both for full signal.
Pirateghost said:
first of all, you need to read up on how RAM is used in linux and android. free ram is WASTED ram. there are 100 threads on here about that topic alone. please search
Click to expand...
Click to collapse
I know what is RAM, but sometimes there are apps that uses a lot of ram like angry birds rio that when in stand-by mode uses almost 100mb ram. But it doesn't matter, if the phone doesn't really have 512mb they shouldn't write in the specs that it does.

Elad92 said:
I know what is RAM, but sometimes there are apps that uses a lot of ram like angry birds rio that when in stand-by mode uses almost 100mb ram. But it doesn't matter, if the phone doesn't really have 512mb they shouldn't write in the specs that it does.
Click to expand...
Click to collapse
when an app needs the ram it will take it. and the phone does have 512. there are numerous threads about this as well. again, search

Pirateghost said:
when an app needs the ram it will take it. and the phone does have 512. there are numerous threads about this as well. again, search
Click to expand...
Click to collapse
I've searched, and I found some theories, but still I don't know what's true.

Elad92 said:
I've searched, and I found some theories, but still I don't know what's true.
Click to expand...
Click to collapse
there IS 512mb RAM, but its not all usable by the USER APPLICATIONS. some of it is used by the SYSTEM to run...
there is literally a massive thread open on this already somewhere. i will find it later
here is some reading for you to do in the meantime:
http://forum.xda-developers.com/showthread.php?t=1008237&highlight=ram
http://forum.xda-developers.com/showthread.php?t=792512&highlight=512mb

just as others have stated the phone DOES have 512mb of RAM. Just like with your computer you may have 2 gigs of RAM installed but that does not mean that you are going to be able to use all of it. More then likely several hundred mbs of that is going to go to system processes like svchost and explorer.exe. That leaves only part of that available for user applications.
As others have stated ram that is free is doing the phone no good. accesses to ram is hundreds of times faster then accesses to main memory so if a program has to load block into RAM it is going to get slowed down. Its better to just let the phone do its own thing and keep applications that are frequently used in RAM so they dont have to get loaded when needed

I have 2 captivates, the only GPS Fix I found that works, is an article that describes all the settings, and after I understood what each setting was I adjusted them to what makes sense, and it works great now. Accuracy ranges 16 to 32 ft. But none of the video's or anything other article worked.
Here is the title of the article. "Why Samsung Galaxy S i9000 GPS is inaccurate and how to fix it." It is located here on XDA-developers.
And BTW I am using the AT&T release of Froyo. Don't have a need to switch to another ROM, everything works.
Brian

Thank you, the ram questions was answered
Does anybody knows something about the other two questions?

In regards to GPS, I flashed Serendipity and its at least mostly usable now. Before, I couldn't get a lock unless I was standing still, then id lose it when I moved.
Sent from my SAMSUNG-SGH-I897 using XDA App

My previous rom was Serendipity, and I flashed to phoenix few days after because of mysterious problems (which now I know had no connection to the rom). Anyway, I love Phoenix, does anyone have phoenix and can use the GPS?

In response to the GPS questions:
The GPS is designed to use the aluminum backplate as an antenna. If you have a thick case on it will work terribly. Thin silicon cases work well enough. Another thing to look at is the app you are using for navigation. Try and find telenav for the i9000 and it will work for the captivate. Google navigation will work terribly. If you have a navigation app that uses generated maps(telenav) or stored maps your GPS will be decent enough to use and will help quite a bit. Read plumbobs guide for more information in the captivate development section.
Sent from my SGH-I897 using XDA Premium App

the captivate has 512 mb ram total
much of that is hardwired for video. the desire hd if it is the same as the inspire has 768mb total so 512 is available for the system to use.

Has anyone tried using navigation with google maps already pre-loaded? If so how is it? Did it improve navigation performance? Google navigation is absolutely horrible for me. Constantly losing signal while driving rendering it useless.

Related

Slowly Lose RAM Over Time

ok I've voiced my opinion on android multitasking before. but this has me confused. I seem to lose RAM over time.
my setup is that I basically run my phone stock. no killing apps with task killers. I run the following services, HTC keyboard, Google finance, battery widget, Google voice/talk/gmail. that's basically it.
when I first start my phone, a bunch of apps show up running and the phone has 30 mb free RAM. over 24 hours less and less apps stay in the cache as "inactive" or "background", until only the above services I run are left running. yet the RAM stays at 30 mb free RAM still. why is this happening? I tested this out over 24 hours, but it gets to this point much sooner, maybe after an hour or so.
edit: also why can't the OS anticipate the apps I DO frequently use and keep THOSE cached in memory? literally the phone pre loads every single app I DON'T use, like Google earth, mp3 store, etc.
http://developer.android.com/videos/index.html#v=fL6gSd4ugSI
oh and I also run the xda app service too.
oh!
In that case you'll need this link instead: http://developer.android.com/videos/index.html#v=fL6gSd4ugSI
Um, may I ask are you annoyed, or are you just interested? Unless your phone is lagging due to apps being idle, how much RAM you have shouldn't even concern you.. not to sound rude or anything, but are you like this on an actual computer as well? People seem to be obsessed with RAM consumption, if my phone doesn't have any issues.. I don't care how much RAM I currently have.
I'm just curious. this does kind of effect things because things like opera start to close just by switching away from it when these conditions happen. but a reboot and opera will keep my page loaded for hours.
it shouldn't matter either way, we are all trying to learn and understand how android works. and the point me this thread is I think this is a bug or a memory leak that people might not know about.
I don't use a computer ever, all phones.
oh!
In that case you'll need this link instead: http://developer.android.com/videos/index.html#v=fL6gSd4ugSI
Click to expand...
Click to collapse
thank you, can't wait to watch there! might be what I'm looking for.
Eclair~ said:
Um, may I ask are you annoyed, or are you just interested? Unless your phone is lagging due to apps being idle, how much RAM you have shouldn't even concern you.. not to sound rude or anything, but are you like this on an actual computer as well? People seem to be obsessed with RAM consumption, if my phone doesn't have any issues.. I don't care how much RAM I currently have.
Click to expand...
Click to collapse
Not to be redundant but that would be the exact reason why someone would care about their RAM usage xD I actually have that problem as well. Even if I kill all tasks, my phone will lock up still. Not sure what the issue is. I feel like the older the phone gets the more it's messing up. (I have had it only for 2 months lol

GPU Overclocking

I've been playing with the GPU clocks and here's the result with the CPU running at 500MHz and the GPU at 200MHz (I think).
This is actually a better Neocore score than a Nexus One gets (though obviously it has a few more pixels to push).
I pushed the changes to the sourceforge copy of the kernel (ltg is broken) to allow messing with the clock. The best I could get is using 0xa99 in /sys/module/clock_7x00/parameters/gpu which I think is 800MHz/4. (bits 3..6 are the divider-1).
Who knows how stable it will be at this speed.
Neat. It's fascinating that there are people still looking to improve our Vogues to their maximum potential when they are becoming seriously outdated...
looks like an update for rogue tools in needed
I searched and cant find where I would download this via SourceForge.
That's amazing. Overclocking the GPU makes me feel like it's a PC.
Nice work dzo!!
I'll implement this into Rogue Tools ASAP.
great i guess ill hang in for a rogue tools update...
Awesome! Any negative side effects?
code
dzo said:
I pushed the changes to the sourceforge copy of the kernel (ltg is broken) to allow messing with the clock.
Click to expand...
Click to collapse
I don't see the code anywhere, I think you forgot to commit it
gTan64 said:
I don't see the code anywhere, I think you forgot to commit it
Click to expand...
Click to collapse
Following this thread from NOW. DZO, if you were in Spain, I would invite you to my restaurant for an exquisite dinner.
PeterDLai said:
Neat. It's fascinating that there are people still looking to improve our Vogues to their maximum potential when they are becoming seriously outdated...
Click to expand...
Click to collapse
These devices aren't as outdated as some would think. Newer phones have slightly more ram, higher res screen, and that all important accelerometer. Being able to overclock our devices, takes away the CPU advantage these devices have.
The new iPhone 4 (that was announced yesterday) is amazing. It has a front camera that's for FaceTime Video Chat! OMG, my Kaiser clearly doesn't have that. Oh wait! I has a camera in the front of my phone and I can in fact use video chat. Yea, it doesn't work in Android but it does in WM, and it's not limited to Wifi connection only.
The more I look at newer phones, the more homogeneous they seem. The only reason to upgrade your phone is if it's free, or cause your phone broke.
Dukenukemx said:
These devices aren't as outdated as some would think. Newer phones have slightly more ram, higher res screen, and that all important accelerometer. Being able to overclock our devices, takes away the CPU advantage these devices have.
The new iPhone 4 (that was announced yesterday) is amazing. It has a front camera that's for FaceTime Video Chat! OMG, my Kaiser clearly doesn't have that. Oh wait! I has a camera in the front of my phone and I can in fact use video chat. Yea, it doesn't work in Android but it does in WM, and it's not limited to Wifi connection only.
The more I look at newer phones, the more homogeneous they seem. The only reason to upgrade your phone is if it's free, or cause your phone broke.
Click to expand...
Click to collapse
Also us Verizon users who don't have data plans can have a smartphone in the Vogue, use Android, and not pay the outrageous 30 dollar data fee. That's a major point.
TheKartus said:
Also us Verizon users who don't have data plans can have a smartphone in the Vogue, use Android, and not pay the outrageous 30 dollar data fee. That's a major point.
Click to expand...
Click to collapse
+1 to that. that's the only reason I ever got the vogue. of course, now I have the data plan. and i'd never go back to a 'dumb' phone. but still.
nice article on iphone 4 vs android.
http://www.appolicious.com/tech/articles/2066-top-android-phones-shouldn-t-be-wary-of-new-iphone-4
Dukenukemx said:
The more I look at newer phones, the more homogeneous they seem. The only reason to upgrade your phone is if it's free, or cause your phone broke.
Click to expand...
Click to collapse
Idk, I upgraded to the Evo and am VERY happy with it.
mrono said:
Idk, I upgraded to the Evo and am VERY happy with it.
Click to expand...
Click to collapse
A coworker in my office got the Evo. I played around with it, and it is a very nice phone. I actually just sold my Touch Pro 2 for a Vogue because I wanted something smaller, and most of all I wanted to step into Android without breaking the bank (still in contract )!
The Vogue is quite the device! Sure, it's not as fancy as many of today's phones, but it's small, light, and it seems to be infinitely hackable. I have a special place in my heart for it.
Dzo you never fail to amaze me. I still mess with my vogue running 2.1 a couple times a week. I mostly have it for my two sons who are 3 and 7. I disabled the ril and keep some games music and kids games on there for them since it doesn't have service. That damn thing lasted over 2 weeks in standby with out being on a charger. I wish my hero could do that. And 36fps in neocore. I could barely touch that with the hero over-clocked to 761mhz.
On a side note. Anyone ever try the wifi/sdcard thing? Or if it's even possible to piggyback a usb wifi stick on to this? This would greatly extend usability of this device for me at least since I use it as more of a pda.
zenulator said:
Dzo you never fail to amaze me. I still mess with my vogue running 2.1 a couple times a week. I mostly have it for my two sons who are 3 and 7. I disabled the ril and keep some games music and kids games on there for them since it doesn't have service. That damn thing lasted over 2 weeks in standby with out being on a charger. I wish my hero could do that. And 36fps in neocore. I could barely touch that with the hero over-clocked to 761mhz.
On a side note. Anyone ever try the wifi/sdcard thing? Or if it's even possible to piggyback a usb wifi stick on to this? This would greatly extend usability of this device for me at least since I use it as more of a pda.
Click to expand...
Click to collapse
I doubt the wifi stick idea would work. From what I've read, the Vogue's hardware doesn't support USB Host. I've also read that the wifi sdcard thing also didn't work due to lack of driver support.
I think our only way of getting wifi on this thing is to just solder in our own wifi chip.
thehelios said:
I doubt the wifi stick idea would work. From what I've read, the Vogue's hardware doesn't support USB Host. I've also read that the wifi sdcard thing also didn't work due to lack of driver support.
I think our only way of getting wifi on this thing is to just solder in our own wifi chip.
Click to expand...
Click to collapse
The hardware does support usb host and I have the documentation for it but somebody would have to write a driver.
I have a few questions.
#1 How's the battery life overclocking the GPU? Is it the same or worse?
#2 Can anyone get Kwaak3 running so we can get some benchmarks going? I can only get that working on Polys 2.1g, and that was months ago.

Browser always refreshing?

I've been hearing that the One has issues similar to its predecessor, as far as browser multitasking. Has anyone had issues with the browser constantly refreshing when you leave, go to another app, and come back to it?
No such problem with my HTC One. Multitasked between apps and browser, different tabs stayed put(no auto-refreshing).
bengadget said:
I've been hearing that the One has issues similar to its predecessor, as far as browser multitasking. Has anyone had issues with the browser constantly refreshing when you leave, go to another app, and come back to it?
Click to expand...
Click to collapse
I would like to know the same..
EDIT: nvm
bengadget said:
I've been hearing that the One has issues similar to its predecessor, as far as browser multitasking. Has anyone had issues with the browser constantly refreshing when you leave, go to another app, and come back to it?
Click to expand...
Click to collapse
Yes. Me.
Shasarak said:
Yes. Me.
Click to expand...
Click to collapse
What kind of websites does it happen with and how often? It worries me how there's no definitive reason why some people have this problem. It seems to be random.
bengadget said:
What kind of websites does it happen with and how often? It worries me how there's no definitive reason why some people have this problem. It seems to be random.
Click to expand...
Click to collapse
It does it a LOT on a dating site that I use, OKCupid (when accessing the desktop version of the site). I think it may possibly be related to the number of tabs one has open, as well. But certainly it's very annoying. I sometimes do a bit of browsing on London Underground trains. (You get about 20 seconds of wifi when the train is in a station!) What I'd like to be able to do is load up multiple pages in different tabs (each one opened as a new background tab) while the connection is up and then read them in the tunnels between stations; but it insists on refreshing each tab as you go back to it, and, as there's no connection in the tunnel, you can't actually read the page, even though it's fully downloaded and should be cached.
It does it pretty frequently. More with stock browser than with chrome though.
soapbubble said:
It does it pretty frequently. More with stock browser than with chrome though.
Click to expand...
Click to collapse
But that doesn't happen on my Chrome on my Note II... ever! Even if I press a link by mistake I can press back and it will be stored in cache, this is probably an HTC problem then, anyone else having this issue?
Nope. Not a problem for me. Always going back and forth on my browser. No issue there
Sent from my HTC One using xda premium
I agree. I can't remember if it's because I swipe it away with the recent apps button.
But sometimes the browser panics on me and closes on it's own.
Sent from my One V using Tapatalk 2
This was NEVER an issue specific to HTC or its software. The sooner people stop spreading the FUD the better.
The only reason Android will force the browser to clear its cache of a page is because it needs to. That is, it's running low on RAM due to other services/apps and needs more. Your browser is not considered a high-level process in the priority list (it's not a service, unlike many other apps), so it'll get hit more often than other apps.
So, the reason this crops up for some people more than others is simply due to what they have running in the background (services, such as Facebook, Trillian, GMail, etc etc). The more crap you run at the same time, the more likely it's going to run out of RAM. This is how it works for ANY Android phone going all the way back to the 2.0 days. It's ALSO how it works on iOS, BlackBerry 10, and webOS (except those platforms don't use a priority system). Also keep in mind that websites these days actually take up a significant amount of RAM, especially ones with heavy amounts of Javascript and retina-level graphics.
The HTC One has 2GB of RAM, which means you have quite a bit of RAM to work with before this happens, but how often it happens is always going to be determined by how you use it.
Vincent Law said:
This was NEVER an issue specific to HTC or its software. The sooner people stop spreading the FUD the better.
The only reason Android will force the browser to clear its cache of a page is because it needs to. That is, it's running low on RAM due to other services/apps and needs more. Your browser is not considered a high-level process in the priority list (it's not a service, unlike many other apps), so it'll get hit more often than other apps.
So, the reason this crops up for some people more than others is simply due to what they have running in the background (services, such as Facebook, Trillian, GMail, etc etc). The more crap you run at the same time, the more likely it's going to run out of RAM. This is how it works for ANY Android phone going all the way back to the 2.0 days. It's ALSO how it works on iOS, BlackBerry 10, and webOS (except those platforms don't use a priority system). Also keep in mind that websites these days actually take up a significant amount of RAM, especially ones with heavy amounts of Javascript and retina-level graphics.
The HTC One has 2GB of RAM, which means you have quite a bit of RAM to work with before this happens, but how often it happens is always going to be determined by how you use it.
Click to expand...
Click to collapse
Thats false, it was an issue on the HTC One X, and thats why I went for the GS3 instead of the One X (that and battery life), and it was done on purpose by HTC, not sure if they "fixed" it or not since then.
Tsukurimashou said:
Thats false, it was an issue on the HTC One X, and thats why I went for the GS3 instead of the One X (that and battery life), and it was done on purpose by HTC, not sure if they "fixed" it or not since then.
Click to expand...
Click to collapse
No, it wasn't, no more than any other device with 1GB of RAM. I'm sure that's what you thought based on all the fud being spread at the time, but it wasn't true, as anyone who knows more about the internals would acknowledge.
Vincent Law said:
No, it wasn't, no more than any other device with 1GB of RAM. I'm sure that's what you thought based on all the fud being spread at the time, but it wasn't true, as anyone who knows more about the internals would acknowledge.
Click to expand...
Click to collapse
Well I think I know a lot and it was definitely HTC's fault.. it was a software preference made by HTC
darkgoon3r96 said:
Well I think I know a lot and it was definitely HTC's fault.. it was a software preference made by HTC
Click to expand...
Click to collapse
A preference that had no influence apparently, since all it takes is a person with a task manager to confirm what I said was true.
This happens on my Nexus 4. Nothing new to see.
Vincent Law said:
This was NEVER an issue specific to HTC or its software. The sooner people stop spreading the FUD the better.
The only reason Android will force the browser to clear its cache of a page is because it needs to. That is, it's running low on RAM due to other services/apps and needs more. Your browser is not considered a high-level process in the priority list (it's not a service, unlike many other apps), so it'll get hit more often than other apps.
So, the reason this crops up for some people more than others is simply due to what they have running in the background (services, such as Facebook, Trillian, GMail, etc etc). The more crap you run at the same time, the more likely it's going to run out of RAM. This is how it works for ANY Android phone going all the way back to the 2.0 days. It's ALSO how it works on iOS, BlackBerry 10, and webOS (except those platforms don't use a priority system). Also keep in mind that websites these days actually take up a significant amount of RAM, especially ones with heavy amounts of Javascript and retina-level graphics.
The HTC One has 2GB of RAM, which means you have quite a bit of RAM to work with before this happens, but how often it happens is always going to be determined by how you use it.
Click to expand...
Click to collapse
This is also BS. The evo lte I had always dumped the browser and this phone does it as well, even just going back and forth from the browser to the music app. The galaxy i switched to did not exhibit the same behavior. In fact, that thing would often keep the browser in memory till the NEXT DAY. This phone with 2gb ram (and 700 plus free) will dump my browser pages for nothing but time it seems
Sent from my HTCONE using xda app-developers app
greengoldmello said:
This is also BS. The evo lte I had always dumped the browser and this phone does it as well, even just going back and forth from the browser to the music app. The galaxy i switched to did not exhibit the same behavior. In fact, that thing would often keep the browser in memory till the NEXT DAY. This phone with 2gb ram (and 700 plus free) will dump my browser pages for nothing but time it seems
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
It's really not. I had chrome stay in RAM for 3 full hours tonight even when playing games. Don't ever use the stock browser, they're always terrible on all platforms.
Vincent Law said:
It's really not. I had chrome stay in RAM for 3 full hours tonight even when playing games. Don't ever use the stock browser, they're always terrible on all platforms.
Click to expand...
Click to collapse
See, that's what's retarded to me. I too have also ran a heavy game and came back to the browser and my pages were still there. But let me play some music and come back a few minutes later and it's highly likely that it's been terminated
I don't use chrome because the stuttery scrolling. The stock browser is the smoothest I've ever used on android so I'm a bit smitten
Sent from my HTCONE using xda app-developers app
greengoldmello said:
See, that's what's retarded to me. I too have also ran a heavy game and came back to the browser and my pages were still there. But let me play some music and come back a few minutes later and it's highly likely that it's been terminated
I don't use chrome because the stuttery scrolling. The stock browser is the smoothest I've ever used on android so I'm a bit smitten
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Chrome doesn't have any scrolling lag for me on the One.

official ICS so crappy and slow

am using the official ICS and OMG its so stupid!
-it takes up to 8 seconds to open an app
-it drains my battery(8 hours maximum)
-it lags so much and some apps just end up crashing every now and then
-cant tether
-one cant manually toggle between 2G/3G/4G!
-is the processor of this phone really a duo core??????
Is there a better ROM??? or should i just sell off the phone??
Did you do a complete wipe/factory restore when you moved to ICS? I started out that way, and the ROM has always felt fine, and I believe there are reports from other users that had their gripes resolved when they restored from scratch.
I did a wipe but still the rom is so lagging!
Sent from my LG-P925 using xda app-developers app
i had some previous ICS experiences but you should try a few tricks. first, hold down the HOME KEY for about 3 seconds. an APP manager opens. you may have lots of apps that didnt close. hit STOP ALL.
Also notice that you can quickly pop between apps this way. you can kill an app by swiping its image sideways.
Second, in your drop down bar, organize your icons to have the WIFI and DATA buttons quickly available. The DATA is a really battery drainer. if your not using it, turn it off. if your not using wifi, turn it off. your battery can last 2+ days with both turned off.
With Gingerbread, i had issues with the wifi not connecting after the phone was on for a day or so. all that seems to be fixed with ICS. I used to have to reboot the phone 2-3 times a day to fix this. I rarely ever reboot it now.
If you decide to sell off the phone, i know at&t will give you $100 for it as a trade in. I think the used phones are going for about $90 on ebay now
hope that helps!
I've used many devices with ICS and this one byfar takes the tard cake.
I am having the same thing here. seems like getting slower after using for few days.
Worst ROM I have ever used
Sent from my LG-P925 using xda app-developers app
after rooting, it actually wasn't bad. pretty stable and responsive
Sent from my LG-P925 using xda premium
ktan.us said:
after rooting, it actually wasn't bad. pretty stable and responsive
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
I recently got this phone and have been expirimenting with the official stock rom while rooted. It is offensively slow and I believe lg recruited satan to invent the rom and make me kill myself. Either way, a few things that actually worked for me are the following:
Startup manager from the android market, disable all lg/ startup applications under system. This singlehandedly decreased my boot time by about a minute and makes everything much smoother.
rescan media root from the market, use it to disable media scanning. For some reason, the media scanner on stock ics sucks for me, and makes the entire phone unusable. Disabling it with this app also increased my boot time and made the phone run better.
V6 supercharger with kick ass kernelizer and patched services.jar and unledded minfrees. Google v6 supercharger, its the first result.
I still have problems like op describes, sometimes the phone will freeze for four to eight seconds while doing something and takes time to catch up to itself. Not sure why, or how to fix it.
Are you sure about that, I actually flashed ICS on my Thrill and It rocks!!!!!!
Sent from my LG-P920 using xda premium
If you are sure it is not a bad flash, try Supercharger and Ultimatic .jar tools mod over in General Android Dev and Hacks like teebuddy said. Kills lag like no other mod. Also uninstall unneeded apps to free up memory. This phone is 3+ yrs old now.
Or use a better optimized custom ROM
http://forum.xda-developers.com/showthread.php?p=39269819
lol glad I am not the only one.
This phone is a piece of garbage.
My first visit to the forum in months.
I signed up to install ICS official hoping for improvements. It brought me some features. Did it make the phone better? Nope, probably worse.
Phone is laggy and my internal storage isn't even full.
Sometimes opening an app takes 4-6 seconds, other times an app freezes and the buttons on the bottom of the phone do not respond.
Sometimes when in an app it goes black and then takes forever to respond again.
I upgrade to ICS and lose tethering which was a nice feature. I would rather lose 3D which is the biggest gimmick ever.
This phone is beyond pathetic! I have an iPhone 4 which is a single core and runs smooth as BUTTER. I prefer Android OS but LG Optimus 3D sucks.
There is no hope for this pathetic phone now. Once my contract expires next year I will try to sell it.
It is rather ironic that you are locked into a contract
drastic00 said:
It is rather ironic that you are locked into a contract
Click to expand...
Click to collapse
Not sure what you are talking about.
I got the phone in 2011 when it came out. There weren't many options. The contract is 3 years, so it expires summer 2014.
Not sure where you live but contracts were 3 years and only changed to 2 years this July. Anyone before July still has to finish their contract or they can cancel.
The phone sucks period. It is worse than my friends Samsung Galaxy S Captivate and my Uncle's iPhone 4.
linuxlol said:
Not sure what you are talking about.
Click to expand...
Click to collapse
That is also ironic.
It's taken a lot of digging to actually find other people complaining about the lagginess of the device.
I'm currently on stock AT&T ICS after custom flashing it god knows how many times. Super-bricked to restored.
I find the current ICS implementation crazy for how little room it leaves on the device.
I've been able to get the device running a TAD smoother by disabling (Yay ICS disable feature) most of the AT&T junk. The reason the device lags so much, especially compared to other devices, is squarely on the lack of RAM. It has 256MB compared to other devices (like the Evo 3D) which have 512MB.
I know the CPU itself isn't crappy, because games like Asphalt 6 look AND RUN fantastic. If it was garbage, the game would run like garbage.
So anything you can do on the device to prevent apps running in the background will help. Otherwise it's spending a LOT of time closing apps because so much of the RAM is used.
M3wThr33 said:
It's taken a lot of digging to actually find other people complaining about the lagginess of the device.
I'm currently on stock AT&T ICS after custom flashing it god knows how many times. Super-bricked to restored.
I find the current ICS implementation crazy for how little room it leaves on the device.
I've been able to get the device running a TAD smoother by disabling (Yay ICS disable feature) most of the AT&T junk. The reason the device lags so much, especially compared to other devices, is squarely on the lack of RAM. It has 256MB compared to other devices (like the Evo 3D) which have 512MB.
I know the CPU itself isn't crappy, because games like Asphalt 6 look AND RUN fantastic. If it was garbage, the game would run like garbage.
So anything you can do on the device to prevent apps running in the background will help. Otherwise it's spending a LOT of time closing apps because so much of the RAM is used.
Click to expand...
Click to collapse
Um this phone has 512mb ram... Also the processor sucks. It's worse than an underclocked iPhone 4 processor.
I froze all the AT&T apps with titanium backup.

Nexus 7 I/O speed issue

http://androidandme.com/2013/06/opi...from-the-best-to-worst-tablet-ive-ever-owned/
After reading the article, I'm glad I'm not the only one who's experiencing this issue. I've noticed my Nexus 7 slows down and becomes less responsive during heavy writing task(downloading stuff at high speed, stuttering browser, etc).
Before anybody jumping in and saying they don't have the issue, the point is it does happen and it happens to other devices as well. Same issue can be said for Galaxy Nexus, Asus Transformer Infinite Transformer Prime. A good way to test this is to see how your tablet performs when you download something over 1MB/s or 2MB/s.
The reasons some people don't see this are:
1. It's hard to tell in short term. Usually the memory i/o speed degrading starts to show after 6 months to 1 year or longer depending on the quality of the flash memory they use.
2. Interfering factors. Many people think the lag is caused by ROM or kernel. It could be true in some cases.
3. Inconsistent quality control during manufacture. I'd assume that out of some bad batches, there will be also some good units. Also not every device use the exact same flash memory chips.
4. Personal usage difference. Flash memory's life span depends on the limited number of writing/reading. So the degrading rate also depends on each individual. Some people are heavy users who constantly perform copying/reading/removing actions on the device while some others may only use it for internet access which results in less taxing work.
Actually the i/o speed issue is one main reason I'm looking forward to next generation Nexus 7. Just hope ASUS can use better quality flash memory next time.
EDIT: more elaborate point.
Sent from my Nexus 7 using xda app-developers app
hbkmog said:
http://androidandme.com/2013/06/opi...from-the-best-to-worst-tablet-ive-ever-owned/
After reading the article, I'm glad I'm not the only one who's experiencing this issue. Before anybody jumping in and saying they don't have the issue, the point is it does happen. Same issue can be said for Galaxy Nexus and Asus Transformer Prime. Actually this is one main reason I'm looking forward to next generation Nexus 7. Just hope ASUS can use better quality flash memory next time.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't know, if Asus doesn't get it right on 2 devices, all of which I have owned, I can't imagine that they will get it right on the next 2 devices. I was so tired of my laggy infinity that I just sold it on ebay. I was so tired of my laggy nexus 7 that I did a factory reset. But then again, these were essentially first generation products. Hopefully the second gen will be better (seems to contradict what I just said, haha.) I am probably going to wait for a little while before I get the next nexus, anyway. I have an expensive habit of getting the latest on launch, most of the time regretting my decisions.
I haven't seen any of the lag these sites and users complain about. Maybe its because I was more used to my Iconia A500 dragging its feet at the two year mark but I can't see how this is "laggy" or "unresponsive" at all. I think this is the result of seeing the device as "old" rather than "new" so you notice one thing and look for 100 others you never noticed. In the end though it could be worse. You could've paid a pretty penny for it to turn to crap All I can say is that I have not noticed these problems and that if they remain after a wipe and reversion to an older, version then they must have always been there.
Its flash storage over all devices. I've seen the same lag on my wifes ipad and iphone.
armada786 said:
I haven't seen any of the lag these sites and users complain about. Maybe its because I was more used to my Iconia A500 dragging its feet at the two year mark but I can't see how this is "laggy" or "unresponsive" at all. I think this is the result of seeing the device as "old" rather than "new" so you notice one thing and look for 100 others you never noticed. In the end though it could be worse. You could've paid a pretty penny for it to turn to crap All I can say is that I have not noticed these problems and that if they remain after a wipe and reversion to an older, version then they must have always been there.
Click to expand...
Click to collapse
Well, the thing is the performance drop is very distinct and easy to see. When the device comes to a stall during some background writing/reading, then it's problem.
The reason some people don't see this is:
1. It's hard to tell in short term. Usually the memory i/o speed degrading starts to show after 6 months to 1 year or longer.
2. Interfering factors. Many people think the lag is caused by ROM or kernel. It could be true.
3. Inconsistent quality control. I'd assume that out of some bad batch, there will be also some good units. Also not every device use the exact same memory chips.
4. Personal usage difference. Flash memory's life span depends on the limited number of writing/reading. So the degrading rate also depends on each individual. Some people are heavy users who constantly perform copying/reading/removing actions on the device while some others may only use it for internet access which results in less taxing work.
hbkmog said:
http://androidandme.com/2013/06/opi...from-the-best-to-worst-tablet-ive-ever-owned/
After reading the article, I'm glad I'm not the only one who's experiencing this issue. I've noticed my Nexus 7 slows down and becomes less responsive during heavy writing task(downloading stuff at high speed, stuttering browser, etc).
Click to expand...
Click to collapse
Every computer I have ever used - that's over a 30-year period - could have its' UI brought to it's knees with heavy I/O. It's not a surprise, really: mass storage is typically the slowest bandwidth device (ignoring things like uarts or keyboards) in the system.
The problem can be pushed into a corner - for instance using massively more RAM than is needed by the memory footprint of the kernel and apps, so that there is plenty of fast file cache available, but even in that case, a source of sustained high-speed I/O will eventually exhaust the write cache, and slow writes will start occurring and queuing up against all other I/O activity.
But that kind of thing doesn't happen in a $200 tablet. RAM ain't cheap, nor does it come for free in terms of power consumption (and thus battery size needed for a given "on battery" time).
On top of that, you have all the problems of write amplification that occurs with flash memory that performs block erasures and wear-leveling.
IMO, if you think this is something that only occurs on certain OS releases, or certain hardware, you are probably going to be disappointed with every device you ever buy. That will be the case until a non-volatile storage media exists with sustained read/write bandwidth that exceeds that of the system memory bus, and also is not affected by the number of independent transactions per GB of I/O.
BTW, the fact that someone on the internet complains about a problem with symptoms similar to those you experience does not imply that the same root cause is involved, nor does it say anything about the frequency of occurrence of those symptoms amongst the general population. I suppose that some small percentage of the world's population is tired all the time; but that doesn't mean they all have Lyme disease, nor that everybody has it.
cheers
Gruber linked to it. Joy. Prepare for this article to be linked to by every iOS fanboy from now until the end of time.
My theory is that its mostly prevalent on the 8 GB models that were only sold for a short period of time, and thats why only a few people, mostly early adopters, have seen this.
I torrent ... "things" ... at over 1.5 MB/sec.
Don't see a dip in speed at all. Try changing your IO schedulers, people.
Mine gets slow when I have less than 3gb of storage open.. Above that, it is fast. It's not a permanent problem. Try freeing up space before damning the Nexus 7.
Sent from my Galaxy Nexus using xda premium
Also as soon as some one points out an issue, people will come in and tell them they are wrong.
There's def an issue with the n7, sometimes is it is slow as molasses and other times butter smooth. Where as my n4 is always butter smooth
T-Keith said:
Mine gets slow when I have less than 3gb of storage open..
Click to expand...
Click to collapse
ya think?!?!
BrianDigital said:
Also as soon as some one points out an issue, people will come in and tell them they are wrong.
There's def an issue with the n7, sometimes is it is slow as molasses and other times butter smooth. Where as my n4 is always butter smooth
Click to expand...
Click to collapse
The N4 has twice as much RAM as the N7. See my comment about file write caching above. It is quite reasonable to expect the N4 to perform better under equivalent load as there will be substantially larger free memory for write caching (everything else being equal). Simply put the N7 will hit the I/O queue wait wall first.
A statement from one or two users that "my tablet doesn't do that, what are you talking about" is just as relevant information as one or two users claiming "my tablet is always slow".
Neither report is a denial of the experiences of others; but both taken together are a demonstration that the trouble described is not universally experienced.
And since neither set of onesie-twosie reports represent a statistically significant sample, neither of them are capable of saying anything meaningful about how widespread the problem is in the general user population.
cheers
bftb0 said:
The N4 has twice as much RAM as the N7. See my comment about file write caching above. It is quite reasonable to expect the N4 to perform better under equivalent load as there will be substantially larger free memory for write caching (everything else being equal). Simply put the N7 will hit the I/O queue wait wall first.
A statement from one or two users that "my tablet doesn't do that, what are you talking about" is just as relevant information as one or two users claiming "my tablet is always slow".
Neither report is a denial of the experiences of others; but both taken together are a demonstration that the trouble described is not universally experienced.
And since neither set of onesie-twosie reports represent a statistically significant sample, neither of them are capable of saying anything meaningful about how widespread the problem is in the general user population.
cheers
Click to expand...
Click to collapse
I'd also be surprised if most Nexus 4s have had the same amount of wear on them as the Nexus 7s. Just saying.
Your I/O scheduler definitely helps, but unfortunately software fixes can only play catch-up for so long. It's one of the things I really do dislike about flash memory-- yes, I know that spinning disk media also has wear, but I've had some drives running for...practically forever, really. I just don't feel comfortable knowing that SSDs and flash will eventually cop out because of how they're designed (but a lot of that, I'll plainly admit is a psychological thing and has little to do with the tech's actual reliability).
bftb0 said:
The N4 has twice as much RAM as the N7. See my comment about file write caching above. It is quite reasonable to expect the N4 to perform better under equivalent load as there will be substantially larger free memory for write caching (everything else being equal). Simply put the N7 will hit the I/O queue wait wall first.
A statement from one or two users that "my tablet doesn't do that, what are you talking about" is just as relevant information as one or two users claiming "my tablet is always slow".
Neither report is a denial of the experiences of others; but both taken together are a demonstration that the trouble described is not universally experienced.
And since neither set of onesie-twosie reports represent a statistically significant sample, neither of them are capable of saying anything meaningful about how widespread the problem is in the general user population.
cheers
Click to expand...
Click to collapse
Your right when I wake my n7 from sleep with no apps updating or anything running, and it moves at a ants pace. I am wrong its me I guess...right. Every user should have to unlock root and flash a kernel to change how it runs.
I read the comment you made before, its the same copy pasta stuff from when the nexus 7 didn't have issues having the storage full, back early on. This what makes xda so great, people have a issue and someone chimes in tells them they are wrong, or ten posts of "420 root it, and flash mer devs kernel"
But your right my tablet should mostly be lagging because running the launcher and maybe an app slows everything down because its designed to run an app and that's it.
Cheers
EDIT: bftb0 summed up what I wanted to say far better
BrianDigital said:
Your right when I wake my n7 from sleep with no apps updating or anything running, and it moves at a ants pace. I am wrong its me I guess...right. Every user should have to unlock root and flash a kernel to change how it runs.
Click to expand...
Click to collapse
Nobody has denied anybody's experience. If you say that stuff happens, I believe you.
BrianDigital said:
I read the comment you made before, its the same copy pasta stuff from when the nexus 7 didn't have issues having the storage full, back early on. This what makes xda so great, people have a issue and someone chimes in tells them they are wrong, or ten posts of "420 root it, and flash mer devs kernel"
Click to expand...
Click to collapse
off topic = irrelevant. But nice segue.
BrianDigital said:
But your right my tablet should mostly be lagging because running the launcher and maybe an app slows everything down because its designed to run an app and that's it.
Click to expand...
Click to collapse
If that happens on a stock device with no apps that's been rebooted within the past few days, and there are no other pathologies involved (e.g. nearly-full or corrupted file systems), then *probably* there is a hardware problem involved.
Look, I get it. Plenty of folks just want to use their device, not worry about details, and have it work as if it were mint. And they want it to behave that way even after customization (adding random apps). But practical experience with a wide variety of computing devices reveals that performance problems always hinge on details - sometimes incredibly tiny and obscure details. Those "details" can be any number of things - "soft" (correctable) hardware defects, bugs in the OS software, user software that is installed, all sorts of stuff. And even for technically sophisticated users isolating the root cause can be difficult. Until some detective work has occurred, there is no justification to place the blame on any specific component.
BTW, I know how frustrating it can be. My old Android phone (rooted, OC'ed & CM 7 ROM) currently can not be operated with both the messaging app and launcher app locked in memory (It only has 190 MB of RAM!). So I get to choose between losing text messages or waiting 15 seconds !!! for the launcher app to repaint the first home screen after leaving a resource-hungry foreground app such as Maps or the Browser. If I try and set up the Android LMK to do aggressive memory reclaim, the device will occasionally enter a "thrash of death" where the LMK is killing off threads as fast as they are generated - and the whole device will go frozen for minutes at a time. So, yeah, I get the frustration.
That of course is indeed "my fault". I could go back to a factory stock ROM (Eclair w/ HTC Sense - ugh). But I don't want to. I want certain features, and I want certain apps, too. You might claim that's not comparable to a user having a stock ROM device with a whole bunch of market apps installed; but until those apps can be cleared of suspicion, blame cannot conclusively be laid anywhere.
It is what it is. Computers that do not exhibit load dependent performance problems do not exist. That doesn't make things anybody's "fault" - but it is highly unlikely that Google (or Apple, whomever) is going to send someone over to your house to figure out what goes on with your tablet.
So, moaning about a problem on the internet might make someone feel better for a few minutes, but at the end of those few minutes, the problem(s) will still be there.
And BTW I completely get it that if I were to be having a performance issue on my tablet, and I wanted to clear my 72 market apps from suspicion, it would take me as many as log2(72) ~= 7 binary bisection trials (remove half of apps each trial) to finger a suspect or clear them all from suspicion). Pain in the rear to be sure; but it wouldn't be any less work on a different device - Apple, Asus, HTC, Moto, Samsung, whatever. And if it were an intermittent problem? It might take a huge effort to isolate the cause. Way longer amounts of time than simply ignoring a second or two of hesitation in the UI.
But the OP created this thread in the General section, not the Help / Q & A section; was he even interested in getting help?
.
I too feel this way since 4.2 update. I'm stock unrooted with 7gb free of storage.
Sent from my Nexus 7 using xda app-developers app
Try rooting your device, install lagfix.
From the comments in the article linked by Op, should help.
I did not try myself since I'm not having these issues.
Sent from my Nexus 7 using xda premium
Phenryth said:
Try rooting your device, install lagfix.
From the comments in the article linked by Op, should help.
I did not try myself since I'm not having these issues.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Werd. Lagfix made my 7 feel like new again. I scheduled it to run once a week and haven't had any problems since then.
Phenryth said:
Try rooting your device, install lagfix.
From the comments in the article linked by Op, should help.
I did not try myself since I'm not having these issues.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Lagfix does fasttrim command but many kernals nowadays do that already so the effect could be placebo unless you are on the kernel that doesn't fasttrim well.
Sent from my Nexus 4 using xda app-developers app

Categories

Resources