Database Users

Performance drops after some time

Hi,
I have noticed that my Nexus' performance starts to drop after some hours on: going from one home screen to the other becomes quite choppy, and so do the animations of opening an application.
Have you guys noticed that too, or is it just me?

It was like this for me until I bought Advanced Task Manager. I have it auto end applications that I don't need to run all the time. It runs much better now.

The issue is RAM. The kernel that shipped with the Nexus One doesn't support the full 512MB of RAM. However, CyanogenMod 5.0-beta4 does and the difference in speed is amazing. With 26 apps running I have 167MB free atm.
But like stickerbob said, you should have Advanced Task Manager at the least.

Deathwish238 said:
The issue is RAM. The kernel that shipped with the Nexus One doesn't support the full 512MB of RAM. However, CyanogenMod 5.0-beta4 does and the difference in speed is amazing. With 26 apps running I have 167MB free atm.
Click to expand...
Click to collapse
I don't get it. Isn't Android supposed to kill unused apps when it's running out of RAM?

frandavid100 said:
I don't get it. Isn't Android supposed to kill unused apps when it's running out of RAM?
Click to expand...
Click to collapse
Yep but some people just don't get that, ah well...

efeltee said:
Yep but some people just don't get that, ah well...
Click to expand...
Click to collapse
Well, that doesn't really explain the performance drops. Does the phone run out of RAM, or not? It seems to be snappy again after a reboot, so there must be something.

frandavid100 said:
I don't get it. Isn't Android supposed to kill unused apps when it's running out of RAM?
Click to expand...
Click to collapse
That is what I have read, but it did not work for me. I downloaded the free version of advanced task man to troubleshoot the problem and found that most of my apps were still running in the background even when my ram was down to 10-20mb. That is about when the phone would start acting up on me. When I ended the tasks the phone would act normal again. So I just broke down and bought the app for $.99. If you do this make sure you exclude some system apps, if you don't your phone could freeze while it is trying to restart them.

10-20mb free is normal operation. This is how the OS is designed to operate, linux and even windows7 now also operate in this fashion (show very little 'free' memory). there is no performance problem with low free memory, purely a misconception on modern memory managment. Whats going on is that you have a buggy application, which is why 'killing' apps looks to be resolving your issue. You're only resolving the symptom, not the problem.
I never kill apps and have had weeks of uptime without any slow down. This gets rehashed over and over again by people claiming task killers help performance. The reality is they do nothing for performance, only nice to have around for that great once and a while an app runs away from you, or in troubleshooting if you have a poorly written app. It should not be anyones habit to do a kill all on a regular basis, if it were the OS would do this automatically.
btw, compcache has been known to cause this slowdown over time issue, it has since been removed from most of the popular custom baked rom's.

frandavid100 said:
I don't get it. Isn't Android supposed to kill unused apps when it's running out of RAM?
Click to expand...
Click to collapse
Yes it does...
bofslime said:
10-20mb free is normal operation. This is how the OS is designed to operate, linux and even windows7 now also operate in this fashion (show very little 'free' memory). there is no performance problem with low free memory, purely a misconception on modern memory managment. Whats going on is that you have a buggy application, which is why 'killing' apps looks to be resolving your issue. You're only resolving the symptom, not the problem.
I never kill apps and have had weeks of uptime without any slow down. This gets rehashed over and over again by people claiming task killers help performance. The reality is they do nothing for performance, only nice to have around for that great once and a while an app runs away from you, or in troubleshooting if you have a poorly written app. It should not be anyones habit to do a kill all on a regular basis, if it were the OS would do this automatically.
btw, compcache has been known to cause this slowdown over time issue, it has since been removed from most of the popular custom baked rom's.
Click to expand...
Click to collapse
Well then there must be many buggy applications. I had to rely on Advanced Task Manager to keep my G1 running acceptably fast. The N1 slows down without its full RAM available so I needed to use Advanced Task Manager then too.
If the RAM is not the issue, why does having the extra 200 MB available make the phone run much smoother with 20+ apps running?

frandavid100 said:
I don't get it. Isn't Android supposed to kill unused apps when it's running out of RAM?
Click to expand...
Click to collapse
well technically no, it reallocates what is being used and frees up memory for programs currently running but non the less the OS manages itself
personally i close apps that i do not have going with the task manager. i seem to notice a performance difference if i do it manually, it takes 2-3 extra taps for peace of mind rather than relying on the OS to figure it out for me...

Deathwish238 said:
The issue is RAM. The kernel that shipped with the Nexus One doesn't support the full 512MB of RAM. However, CyanogenMod 5.0-beta4 does and the difference in speed is amazing. With 26 apps running I have 167MB free atm.
But like stickerbob said, you should have Advanced Task Manager at the least.
Click to expand...
Click to collapse
The speed benefits of CM's ROM isn't due to the HIGHMEM supporting kernel, but rather other tweeks he's done with his build. Extra ram is nice, but there is certainly no limitation with the 213 or so userspace memory that is available now. Android itself does not even use this memory, it has its own reserved memory space, userspace memory is only for applications to be loaded in. And there is speed for keeping as much of your applications loaded in memory as possible.
swetland said:
Roughly 220MB is available to userspace in the shipping build (ERD79).
Quite a lot of memory is dedicated to the radio firmware (41MB), dsp firmware (32MB), display surfaces (32MB), gpu (3MB), camera (8MB), a/v buffers (41MB), and dsp buffers. Much of this needs to be set aside for these specific tasks due to hardware requirements of very large physically contiguous buffers which can be difficult or impossible to obtain after boot once the physical memory space gets fragmented.
The big limitation though is that the Linux kernel needs to do a 1:1 physical:virtual map of general purpose memory used by the kernel and userspace (which excludes the special purpose stuff described above). This eats into the available kernel virtual address space, which is also needed for cross process shared memory used by the binder, etc. Run out of virtual memory and things get unhappy.
In 2.6.32, HIGHMEM support for ARM will allow us to avoid this requirement for a 1:1 mapping which will allow us to increase memory available to userspace without running the system out of virtual memory adddress space.
Click to expand...
Click to collapse

The speed difference I'm talking about is what I experienced when running CM beta3 and CM beta3 w/ highmem. The difference was huge. I assumed the change was mainly attributed to the double RAM available.
Even now with the full RAM available, things run faster when I end the other apps running. It's not necessary, but the difference is there.
It would be nice to be able to pinpoint which apps caused slow downs.

The best way I've seen this put I found in a thread where someone wanted to disable apps from auto-starting entirely. I saved it, because I though it was very elegant way to explain androids mem management.
equid0x said:
I just wanted to chime in here about the whole apps on startup thing....
Android has the concept of services which are programs that typically have a frontend piece, like a GUI for IM that you would normally use, that only runs when you are using it, and a background piece, the service, which is constantly running to keep you connected to your IM servers. This will account for some portion of the things you see running on startup, depending on how many apps you have installed, and whether or not they were written to run as a service.
There are also some, usually older, android programs that existed before "services" were really used.. that basically use triggers to keep reloading themselves. These programs are less efficient, and probably should be re-written to use the official service method of operation, caveat emptor.
Android also makes several modifications to the stock process handling that comes with any Linux kernel, which is already radically different from what most would be used to seeing on Windows as it is. Android attempts to keep commonly used applications running(loaded into memory), but in a sleeping state (using no cpu), so that they may be quickly resumed on request. Android also contains some agressive modifications to the behavior of the OOM(out of memory) task killer in Linux, that seem to cause it to keep applications running until nearly all memory is consumed, killing apps it deems unnecessary only when absolutely necessary. However, Android also supports a methodology of saving the running state of a program, so that if it is killed due to an OOM condition, it may be restarted with relevant data restored, to give the appearance of never having been killed at all.
This functionality is not all to alien to Linux as a platform in general, though Android has many modifications which tend to favor aggressive app management in memory, and less so filesystem cache. This was likely a design choice made to suit the low-speed/low memory platforms Android targets.
Click to expand...
Click to collapse

Good read.
So then given that...only services running should slow down the phone and not the background apps running.
However, this doesn't really answer the OP's question. If it's not a memory issue...what's causing his slowdowns?

Could be too many widgets on the home screen, I don't run that many but its possible that while in an app for a while, and switching back to home the OS may have to kill a whole bunch of apps to allow it to reload all the widgets on the home screen.
I tested this, and loaded the crap out of my home screens with widgets, and then launched a game. When I exited the game there was a good 500ms - 800ms delay in my homescreens from displaying anything other than the background. However, after it loaded, scrolling between screens looks smooth. The new kernel with highmem support can help this, but I would suspect some crazy widget filled homescreen with a 3rd party live wallpaper (star's configured with too many stars) and all of that combined could be an issue even still. Apple combats this by allowing only one app at a time, they know people will go overboard if allowed.

Well, that doesn't really explain the performance drops. Does the phone run out of RAM, or not? It seems to be snappy again after a reboot, so there must be something.
Click to expand...
Click to collapse
There's probably no easy answer to this question. There could be IO contention, a runaway process, high CPU usage, a memory leak, shoddy code in some app, etc etc... One would really have to take a look at the whole state of the system at the time the problem is happening to be able to ascertain what is causing the slowdown.
The phenomenon is in no way unique to Android. I'm sure nearly everyone is familiar with the common complaint "my computer is running slow". The reasons that can happen on a common PC are the very same reasons that can be happening here, and unfortunately there are many of those reasons. While in many cases, throwing memory at the issue may appear to solve the problem temporarily, it often is not a permanent fix.
The amount of userspace memory available really amounts to 1 thing and 1 thing only -> the total number of running processes that we can keep totally in memory at any given time. On stock android, slowdown due to an OOM condition should be minimal, since stock android doesn't swap. Discounting any other bottlenecks, there is a practical limit to the number of programs once would be able to run in the memory space that is available. Realistically speaking, android programs tend to be fairly small, so you'd really have to be running a lot of them to exhaust this space. It is far more likely one or 2 poorly written programs are hogging huge amounts of memory (and probably other resources), which is causing constant killing and restarting of other apps you are trying to run concurrently. You end up with contention on the slow flash, resulting in poor performance.
You can't even really compare the Nexus One to the G1 in this regard, because the G1 truly is terribly deprived of memory. Though, the argument in both cases could really be made that you are attempting to run the hardware beyond its design specifications...
Its been my experience that the culprit is usually one or 2 specific programs. Sometimes the best, although inconvenient, way to figure out which programs these are, is to keep watch of your usage habits, and if you suspect something is the problem, uninstall it, and see if the issue persists. Its time consuming but there really isn't any better way to figure it out without using all kinds of tools that android doesn't really provide convenient access to. There are a few apps on the market that help with this but I am not sure what they are called offhand.
Programs that were identified as sources of slowdown for me have been:
Weatherbug
The Weather Channel
Calorie Counter
Locale
SMS Popup
10000
USA Today
National Geographic Wallpapers
CNN News Widget
Streamfurious
Nav4All
Waze
Just about every app with Admob Ads
And this is really just what I can think off offhand... there are more...

equid0x said:
There's probably no easy answer to this question. There could be IO contention, a runaway process, high CPU usage, a memory leak, shoddy code in some app, etc etc... One would really have to take a look at the whole state of the system at the time the problem is happening to be able to ascertain what is causing the slowdown.
The phenomenon is in no way unique to Android. I'm sure nearly everyone is familiar with the common complaint "my computer is running slow". The reasons that can happen on a common PC are the very same reasons that can be happening here, and unfortunately there are many of those reasons. While in many cases, throwing memory at the issue may appear to solve the problem temporarily, it often is not a permanent fix.
The amount of userspace memory available really amounts to 1 thing and 1 thing only -> the total number of running processes that we can keep totally in memory at any given time. On stock android, slowdown due to an OOM condition should be minimal, since stock android doesn't swap. Discounting any other bottlenecks, there is a practical limit to the number of programs once would be able to run in the memory space that is available. Realistically speaking, android programs tend to be fairly small, so you'd really have to be running a lot of them to exhaust this space. It is far more likely one or 2 poorly written programs are hogging huge amounts of memory (and probably other resources), which is causing constant killing and restarting of other apps you are trying to run concurrently. You end up with contention on the slow flash, resulting in poor performance.
You can't even really compare the Nexus One to the G1 in this regard, because the G1 truly is terribly deprived of memory. Though, the argument in both cases could really be made that you are attempting to run the hardware beyond its design specifications...
Its been my experience that the culprit is usually one or 2 specific programs. Sometimes the best, although inconvenient, way to figure out which programs these are, is to keep watch of your usage habits, and if you suspect something is the problem, uninstall it, and see if the issue persists. Its time consuming but there really isn't any better way to figure it out without using all kinds of tools that android doesn't really provide convenient access to. There are a few apps on the market that help with this but I am not sure what they are called offhand.
Programs that were identified as sources of slowdown for me have been:
Weatherbug
The Weather Channel
Calorie Counter
Locale
SMS Popup
10000
USA Today
National Geographic Wallpapers
CNN News Widget
Streamfurious
Nav4All
Waze
Just about every app with Admob Ads
And this is really just what I can think off offhand... there are more...
Click to expand...
Click to collapse
I'm banking on it being an issue with an app that the OP has installed as well...not the phone or Android. I have only a handful of tried and true apps, and haven't experienced a slowdown even after 150 hours without a reboot.
OP... start uninstalling apps a couple at a time and wait several hours in between to narrow down the problem app.

I can't speak for the OP, but when I was having that problem I had 5 widgets running on my home screen. The Google Search, Sports Tap, Power Control, Calendar, and The Small Weather Channel. Does this seem like too much? I hope not.

stickerbob said:
I can't speak for the OP, but when I was having that problem I had 5 widgets running on my home screen. The Google Search, Sports Tap, Power Control, Calendar, and The Small Weather Channel. Does this seem like too much? I hope not.
Click to expand...
Click to collapse
It's not just widgets that you should be thinking about... any app you've installed can throw something off.

stickerbob said:
I can't speak for the OP, but when I was having that problem I had 5 widgets running on my home screen. The Google Search, Sports Tap, Power Control, Calendar, and The Small Weather Channel. Does this seem like too much? I hope not.
Click to expand...
Click to collapse
I removed the weather & news widget and the phone seems much faster now. I'll keep it like that for a day, see if it stays fast.

How much available memory do you usually have?

I tend to have 70-80mb free, I use task panel a bunch to kill all backgrounds apps once I get down to 40mb or so.

Need Help
I was about to make a new post asking for help for this...
I have a mytouch 3G.
When it was stock, the available ram varied from 20 to 30 MB.
At the moment I have Cyanogen 4.2.14.1, and my ram varies from 15 to 24 MB.
My info from system setting:
Baseband 62.50s.20.17u_2.22.19.26i
Kernel 2.6.29.6-cm42
Mod Version: CyanogenMod-4.2.14.1
Build DRC92
I thought this was supposed to speed it up, and not slow it down. Moment it drops down less then 22 MB, it slows down considerably.
The rebooting time is very high, and the only Widget I am using is Power Control. I would like to use calendar, and Retro Clock and weather or something, but cant even think of it, due to how slow it is.
I am using App2SD, and so I was wondering if anyone help me out and give me directions as to my next action.....
Thanks,

mumbojumbo01 said:
I was about to make a new post asking for help for this...
I have a mytouch 3G.
When it was stock, the available ram varied from 20 to 30 MB.
At the moment I have Cyanogen 4.2.14.1, and my ram varies from 15 to 24 MB.
My info from system setting:
Baseband 62.50s.20.17u_2.22.19.26i
Kernel 2.6.29.6-cm42
Mod Version: CyanogenMod-4.2.14.1
Build DRC92
I thought this was supposed to speed it up, and not slow it down. Moment it drops down less then 22 MB, it slows down considerably.
The rebooting time is very high, and the only Widget I am using is Power Control. I would like to use calendar, and Retro Clock and weather or something, but cant even think of it, due to how slow it is.
I am using App2SD, and so I was wondering if anyone help me out and give me directions as to my next action.....
Thanks,
Click to expand...
Click to collapse
People;
Android is NOT Windows.
This means Android is supposed to use as much RAM as possible because Android is Linux-Kernel based, meaning Android properly and correctly handles RAM. It uses as much RAM as possible so every program that is running runs faster, it does not mean the phone is slowing down with less RAM. You guys have to get it out of your head.
"Unused RAM is useless RAM"

hol17 said:
People;
Android is NOT Windows.
This means Android is supposed to use as much RAM as possible because Android is Linux-Kernel based, meaning Android properly and correctly handles RAM. It uses as much RAM as possible so every program that is running runs faster, it does not mean the phone is slowing down with less RAM. You guys have to get it out of your head.
"Unused RAM is useless RAM"
Click to expand...
Click to collapse
Thank you very much for your insight.... Please tell me how much RAM do you have left when you are running your system?
Yes low RAM does not mean that phone is slowing down.. but when at 19MB you start noticing your keyboard doesnt act properly, you are not able to open apps at the same speed that you were before when it was 25 MB... I believe that means its slowing down....
Or maybe I am just assuming things.....

mumbojumbo01 said:
Thank you very much for your insight.... Please tell me how much RAM do you have left when you are running your system?
Yes low RAM does not mean that phone is slowing down.. but when at 19MB you start noticing your keyboard doesnt act properly, you are not able to open apps at the same speed that you were before when it was 25 MB... I believe that means its slowing down....
Or maybe I am just assuming things.....
Click to expand...
Click to collapse
I have 28MB of RAM left on average and that is with these running:
- Facebook App
- AK Notepad
- Browser
- Alarm
- Footprints
- Gmail
- Google Maps
- IM
- Mail
- Peep
- NetCount
- Stocks
- Weather
- People Widget
- And a few more.
The keyboard does lag sometimes but it's due to Android catching up and removing an app from RAM I believe. That's when it speeds up a bit.

See Right there is the issue,
You have 28MB ram with so many things running.
I have 21 mb Ram with
Power Widget
Messaging
Gmail
and Ebuddy running
Hence the reason why I was questioning this, and if I need to do anything to correct this.
I wasnt looking for 40MB ram or anything. I would just like it to run good with a few more things.
Moment I opened up Google Maps with the above, my Ram dropped to 18 MB and it slowed down that I could not even add the TO location for a while...
So again I ask, if I desire to reinstall the ROM etc, would someone please help me out with the steps, or direct me to it. Keeping in mind that I have App2SD. I would rather use another method then reinstalling the ROM.
Currently using Cyanogen 4.2.14.1 with Cyanogen latest recovery image.
Thank you

mumbojumbo01 said:
See Right there is the issue,
You have 28MB ram with so many things running.
I have 21 mb Ram with
Power Widget
Messaging
Gmail
and Ebuddy running
Hence the reason why I was questioning this, and if I need to do anything to correct this.
I wasnt looking for 40MB ram or anything. I would just like it to run good with a few more things.
Moment I opened up Google Maps with the above, my Ram dropped to 18 MB and it slowed down that I could not even add the TO location for a while...
So again I ask, if I desire to reinstall the ROM etc, would someone please help me out with the steps, or direct me to it. Keeping in mind that I have App2SD. I would rather use another method then reinstalling the ROM.
Currently using Cyanogen 4.2.14.1 with Cyanogen latest recovery image.
Thank you
Click to expand...
Click to collapse
Even with all those things running, if I don't need my data enabled, I disable it. When you open Google Maps it tires to find your location, download map data and upload data. Even though mine is running, when I'm done with it I disable my data so none of my apps can slow down my phone by downloading/uploading.

I'm curious about this too if anyone could help, my phone seems to run really slow and often only shows around 25 megs free.

adambrouillard said:
I'm curious about this too if anyone could help, my phone seems to run really slow and often only shows around 25 megs free.
Click to expand...
Click to collapse
Check if you have a 32A or 32B board first by going to the boot menu (Power + Back); if you have 32B then there is a reason why it's running so slow -- you have 50% less RAM overall then the 32A boards.
If you have 32A then disable GPS, data, bluetooth, anything after you are done using applications on your phone. Remember that applications run in the background and that means they actually still use all your wireless communications. Since your phone is receiving and sending out data it tends to slow down and feel sluggish.
If it still feels slow or you don't feel like turning off your wireless communications then use a task killer. Make sure to ignore ANY application that does not use wireless communications (ie, Clock, Alarm, HTC sense, Touch Input) and once you are done using an application like Gmail, you can go into task killer and kill the task. Just make sure not to use the widget because now the task killer application is running all the time in the background, monitoring your whole phone, it will drain the battery a bit faster.

I purchased the new MyTouch 3G 1.2 last Monday and installed approximately 60 apps on it and my available memory is at 235! And I must say the battery lasts me a full day with all everything on and heavy usage! I'm diggin' this new purchase!

zombierockstar said:
I purchased the new MyTouch 3G 1.2 last Monday and installed approximately 60 apps on it and my available memory is at 235! And I must say the battery lasts me a full day with all everything on and heavy usage! I'm diggin' this new purchase!
Click to expand...
Click to collapse
Installing and running are 2 different things. Installing an app does not mean it is running in the background and using memory.
I'm also surprised that you have that much available memory with heavy usage because that seems impossible if you are opening many apps. You are looking either at false info or not reading the information correctly.

hol17 said:
Installing and running are 2 different things. Installing an app does not mean it is running in the background and using memory.
I'm also surprised that you have that much available memory with heavy usage because that seems impossible if you are opening many apps. You are looking either at false info or not reading the information correctly.
Click to expand...
Click to collapse
Just went into settings/SD card & phone storage/ and it states my internal phone storage has 233MB available!

hol17 said:
Check if you have a 32A or 32B board first by going to the boot menu (Power + Back); if you have 32B then there is a reason why it's running so slow -- you have 50% less RAM overall then the 32A boards.
If you have 32A then disable GPS, data, bluetooth, anything after you are done using applications on your phone. Remember that applications run in the background and that means they actually still use all your wireless communications. Since your phone is receiving and sending out data it tends to slow down and feel sluggish.
If it still feels slow or you don't feel like turning off your wireless communications then use a task killer. Make sure to ignore ANY application that does not use wireless communications (ie, Clock, Alarm, HTC sense, Touch Input) and once you are done using an application like Gmail, you can go into task killer and kill the task. Just make sure not to use the widget because now the task killer application is running all the time in the background, monitoring your whole phone, it will drain the battery a bit faster.
Click to expand...
Click to collapse
Yeah, I have a 32b. So pretty much 25 megs of free ram is what I should be expecting then?

zombierockstar said:
Just went into settings/SD card & phone storage/ and it states my internal phone storage has 233MB available!
Click to expand...
Click to collapse
That is not RAM -- that is the amount of space available to install updates/applications on initial phone STORAGE.
This topic is about phone MEMORY. You can only view it with a third-party application from the market.
You read the information wrong and you posted something that is irrelevant.
adambrouillard said:
Yeah, I have a 32b. So pretty much 25 megs of free ram is what I should be expecting then?
Click to expand...
Click to collapse
In short -- yes.
The 32B board has 192MB of RAM compared to the 288MB a 32A board has so you can expect the phone to run a bit slower.

Improving performance by removing virtual keyboard

My biggest problem with G1 is not having enough ram. While checking what sits in my ram with MemoryUsage app I noticed virtual keyboard. Since I almost never used it, I killed it. This caused home to reload, but I believe that keyboard has not been loaded instantly.
But after some time, I could see it there again hogging my precious 9MB. Since my phone has usually only like 15MB ram free, this was quite annoying.
After doing some research and BACKUP, since I am rooted I decided to rename the application to see if it will work. The app in question is LatinIME.apk. I renamed it to LatinIME.apkBkp. While I have been there, I did the same thing with LatinImeTutorial.apk. Both files are located in /system/app.
You have to remount it writable first, search this forum for how to do it.
After renaming that file (and maybe killing the app, don't remember exactly) my phone tried to reload home. It failed to do so, force closed and then tried again, resulting in infinite loop.
I rebooted the phone and it worked well, starting normally. Now I have more ram and performance of my phone improved a bit. My free ram stays a bit higher and apps are not so often removed from it.
Overall I am happy about the result and I am looking for more unnecessary stuff to remove.
I am on CyanogenMod 4 btw., so there might be different keyboard apps on other roms.
I have not found anyone mentioning this here, only some tutorials how to change default keyboard, so hopefully someone will find this useful.
If you have any suggestion how to sqeeze even more ram from my G1, bring them on please. (I know of swap, compcache, 10mb hack and keeping low number of apps)

raqua said:
My biggest problem with G1 is not having enough ram. While checking what sits in my ram with MemoryUsage app I noticed virtual keyboard. Since I almost never used it, I killed it. This caused home to reload, but I believe that keyboard has not been loaded instantly.
But after some time, I could see it there again hogging my precious 9MB. Since my phone has usually only like 15MB ram free, this was quite annoying.
After doing some research and BACKUP, since I am rooted I decided to rename the application to see if it will work. The app in question is LatinIME.apk. I renamed it to LatinIME.apkBkp. While I have been there, I did the same thing with LatinImeTutorial.apk. Both files are located in /system/app.
You have to remount it writable first, search this forum for how to do it.
After renaming that file (and maybe killing the app, don't remember exactly) my phone tried to reload home. It failed to do so, force closed and then tried again, resulting in infinite loop.
I rebooted the phone and it worked well, starting normally. Now I have more ram and performance of my phone improved a bit. My free ram stays a bit higher and apps are not so often removed from it.
Overall I am happy about the result and I am looking for more unnecessary stuff to remove.
I am on CyanogenMod 4 btw., so there might be different keyboard apps on other roms.
I have not found anyone mentioning this here, only some tutorials how to change default keyboard, so hopefully someone will find this useful.
If you have any suggestion how to sqeeze even more ram from my G1, bring them on please. (I know of swap, compcache, 10mb hack and keeping low number of apps)
Click to expand...
Click to collapse
Unused RAM is wasted RAM. The system will kill applications when more memory is needed. Don't worry about it.
And time for you to upgrade to CM6, don't you think?

lbcoder said:
Unused RAM is wasted RAM. The system will kill applications when more memory is needed. Don't worry about it.
And time for you to upgrade to CM6, don't you think?
Click to expand...
Click to collapse
Idiocy runs rampant at Dream forums, huh? Blame the stupid Advanced Task killer dev for getting all these idiots believing killing apps actually serves a purpose...
Anyway, if the OP is concerned about memory usage and bloat, I very much doubt CM6 is a step in the right direction. Maybe the latest CM 5 is a better option.

lbcoder said:
Unused RAM is wasted RAM. The system will kill applications when more memory is needed. Don't worry about it.
And time for you to upgrade to CM6, don't you think?
Click to expand...
Click to collapse
Yep, I am very well aware how does it work, but killing the app and loading the other one uses CPU cycles and makes system slow. Especially if it happens all the time as it does on my phone. This is actually the biggest source of laggines imho.
Plus, I am pretty sure, that system apps are not unloaded (some of them at least) or they are unloaded as a last resort. Which was also the case here. I could see other apps being killed (which I did not wanted to be killed) while unused virtual keyboard was happily sitting there.
For the record, I do not use task killer of any sort, does not make significant difference for me and occupies more ram than it saves. So please save that 'idiot' for someone else.
I do not plan to switch to CM5 or CM6, because those need even more ram as CM4 does. Afaik, those roms use hw graphics support which prohibits 10mb hack. I definitely keep 10mb hack on my phone. Did a lot of good to it's speed.

Okay so what setup are you using?
I have tryed every which rom out there since i got into it and i usually only use my phone for browsing youtube music and normal phone stuff and am find these new firmwares to be getting sluggish. Basically i want a lightning quick basic build. I am interested in what exactly you are using.

elltg said:
Okay so what setup are you using?
I have tryed every which rom out there since i got into it and i usually only use my phone for browsing youtube music and normal phone stuff and am find these new firmwares to be getting sluggish. Basically i want a lightning quick basic build. I am interested in what exactly you are using.
Click to expand...
Click to collapse
I am using last version of CyanogenMod from 4 series. That is Android 1.6 based.
I have apps2sd, 10mb hack and compcache enabled. No swap. Was not working for me. I removed all the apps that stay in memory like all widgets etc. The only things that is running in my memory permanently are: SeePU (to monitor my phone), JuiceDefender (to save battery), Battery Left widget and Astrid.
I set my phone to keep Home app in memory all the time, removed all the unnecessary effects in Spare Parts and removed virtual keyboard.
With this setup, my phone performs quite ok. Not as snappy as I would want it to be, but acceptable.
Hope it helps.

I have been using Super-D 1.9.3 with 10mb hack. Removed VPN, VoiceDialer, GenieWidget and some other misc things. Latest ADW instead of Launcher.apk, MusicMod 1.5 instead of stock music, latest 1.6 Phone.apk from Wysie. I also themed my lockscreen and Powertop widget. I has been about 4 months since I flashed it and it hasn't slowed down much at all (and I rarely reboot it). Not a singel FC! Battery lasts me thru the day (I have facebook, twitter and Gmail updating themselves). All in all, its one of the best set-ups I've used. I strongly suggest trying out earlier Super-D roms if you're looking for reliable daily driver (anything before 1.11 should be quite good, 1.11 is when it all went downhill)
Good luck.

raqua said:
I am using last version of CyanogenMod from 4 series. That is Android 1.6 based.
I have apps2sd, 10mb hack and compcache enabled. No swap. Was not working for me. I removed all the apps that stay in memory like all widgets etc. The only things that is running in my memory permanently are: SeePU (to monitor my phone), JuiceDefender (to save battery), Battery Left widget and Astrid.
I set my phone to keep Home app in memory all the time, removed all the unnecessary effects in Spare Parts and removed virtual keyboard.
With this setup, my phone performs quite ok. Not as snappy as I would want it to be, but acceptable.
Hope it helps.
Click to expand...
Click to collapse
You have options.
-Remove apps2sd and use the mtd patch method. That way you cut out the slowest link on the phone: the memory card. With the MTD hack, you can get maybe 150 megs or more of internal space for apps on a donut rom.
-Use the latest version of setcpu since it doesn't stay in memory. You can try an overclock, it will help but shorten battery life some. Maybe 576 or 595 would be enough of an overclock to make it feel faster yet not drain battery like crazy.
-Keep CC on and lock home in memory
-remove the battery widget lol.
=Delete juicedefender and just use the power control widget.
-I usually remove apps that tend to launch on their own, such as the genie widget or the voice search, as well the the VK since I never use those. It's easy enough to write a script or remove them by hand from the terminal. for example, to remove the VK, open terminal and type
Code:
su
mount -o rw,remount /system
rm -f /system/app/LatinIME.apk
-reboot your phone often, and try clearing your cache using cachemate or similar

*** Galaxy Tab Master Tweak Thread***

Hi everyone.
Id like to start a thread where we collect, post and discuss all known individual tweaks and changes that can be made to the Galaxy Tab in order to gain performance and stability.
My experience with the Galaxy Tab has been similar to my latest phone, an HTC HD2. When I got the HD2 about one year ago, I positively hated it... slow, unstable, all sorts of problems, lags, crashes... its the way most of the hardware today is released. One year later, my HD2 has become the most amazing machine I've ever owned. From pushing it 1.6GHz stable, to tweaking registry, XML files, services and making everything work well. I remember not being able to watch smooth video on the HD2 to being able to watch flawlessly 720p content and going from the extreme of detesting the phone to loving it.
It was with the HD2 I discovered Android and fell in love with it. Since I have now two HD2s I have one with an SD ROM version of Gingerbread (that I can dual boot still from Windows Mobile) and a Froyo NAND. I run Android on the HD2 much much much faster and smoother than on the Galaxy Tab, that I also hated when I bought it a few weeks and that am starting to like after getting to know it, a new ROM, apps, etc. Even at 1GHz stock the HD2 with Froyo is vastly faster, smoother, more responsive and better to use. The approach d like to do as far as tweaking the Galaxy Tab is the same as I did for the HD2 with Windows Mobile, that is, install the best/fastest ROM I can, delete and remove all stuff I don't need and then tweak what's left.
The tweaks I've done so far on the Galaxy are simple but have made a huge difference. Id like with this thread to be able to collect individual tweaks and post them all here to share with everyone.
Im using Roto JMI Pre-Rooted Firmware v2 which was the main step after getting rid of the stock Samsung Rom that is nothing but a collection of problems.
The first thing I learned with this Tab is that WHATEVER IS ON YOUR HOME SCREENS THAT MOVES, IS BAD! Forget about having ANY type of apps or widgets that do any type of refresh, including stuff running on the upper task bar if they change icons or the move around… that mean a CPU cycle and refresh each time and there goes the tab's performance and battery life. The same goes for any type of Live Wallpaper. Beautiful but deadly. Never touch them!
- So, after a new ROM, the first thing I did was changing the file system to EXT4. This is the SINGLE BEST THING you can do to radically improve the performance of the Tab. Its extremely easy to do and the step-by-step instructions are as follow:
- Make sure you have an miniSD Card in with plenty of available space (it will be used automatically to backup your system during the conversion process)
- Get p1000-mck-r3-ext4-cwm.tar (the EXT4 Conversion Kernel)
- Connect the Tab in Downloading Mode to your PC via USB, start Odin3 1.7 and load the Kernel (click on the PDA button and select the p1000-mck-r3-ext4-cwm.tar and make sure PDA stays ticked after selecting the file).
- UNTICK Re-Partition check box and make sure the only boxes ticked are:
Auto Reboot
F. Reset Time
The PDA tickbox
- Click start and wait for PASS! (it will show highlighted green or Yellow on Odin)
- Now the Tab will restart and get stuck on the Samsung loading screen. This is normal. Turn it off by holding the power button for 5 seconds.
- Turn on the Tab again on into RECOVERY mode (Press Volume UP and Power On at the same time) and the EXT4 conversion will start automatically. The process will take up to one hour depending on how much stuff you have on your Tab. It took about 10 minutes on mine because I have a fresh install of Roto JMI v2.
- Once finished, click "Reboot System Now" (by pressing the power button).
- The reboot may take a while first time so be patient!
- Done!
- After that, the first tweak I did was to get rid of all my favorite widgets that moved around… net meter, news, weather and all these beautiful things KILL the Tab. Equally I had a CPU meter on the tray refreshing every 2 seconds and it took me a while to figure out that was the reason why every 2 seconds the system would stutter, whether watching a movie or browsing the web. So, out!
- Next was to install SetCPU under the ON DEMAND setting, minimum around 750MHz and maximum 1000MHz (unfortunately only with a custom Kernel you can go higher, currently up to 1.4GHz but not full stable and with lots of issues pending so I don’t recommend it)
- My following step was to get rid of the stock Samsung Homescreen (that is a resource hog and slow as hell) and replace it with a new one. I've tried them all and am making no recommendation here but the one that works for me and is by far the best IMO is LauncherPro. This single app makes using the Tab a whole better experience.
- Next was to disable the USELESS and (resource pig) Gallery and replace it with an app called QuickPic that is blazing fast (actually instant) and simply amazing to browse and view all media on the Tab.
- Next was to greatly improve the poor native GPS reception by replacing high performance files and drivers from the Orange Rom P1000JHKA1 that seems to work on all versions of the Tab, as originally posted here:
http://forum.xda-developers.com/showthread.php?t=922692
- With SystemApp Remover 4.12 I have disabled all system apps and services I don’t need (BE VERY CAREFUL AND DON'T REMOVE ROM APPS YOU WILL NEED). I have actually deleted some from ROM (Root access required of course), this includes useless stuff like STK Service starting every time, most of the Samsung stuff that I really don’t care for and just about all apps I know for sure I will never open a single time. Now, its important to understand if these apps are removed they will be removed PERMANENTLY from ROM so to get the back a hard reset will not be enough, you'll have to fully flash the ROM again. For most system apps I don’t use but am not sure, I use a different option and that is to simply disable them. In my case this includes all Bluetooth stuff (I never use it and even if it's off the Services are still running robbing performance and memory) and apps like the built-in Browser, Email and Messaging that suck and that I replaced with better apps. Its always a safer bet, at least initially to disable the apps you don’t need that uninstall them because at least you can go back and change your mind This is one area where Id like to learn more. There are many background services that I don’t know what they do and if they can be disabled or not. If someone knows what each one does and the safety of getting rid of them OR NOT, it would be great to post it here!
- Them, with Startup Auditor 2.3.2 I have disabled all unnecessary apps that start automatically every time the Tab boots so I don't have excess applications starting up that are not needed. Some I configured to be killed AGAIN if the system tries to restart them later after the boot-up
- Using Task Manager 1.0.7 and letting always run on background, I have configured all apps that I don’t need running to be auto-killed every time the phone goes to stand-by (screen off). This saves me lots of memory and CPU time on apps that I am actually not using.
- Finally, I monitor what is going on with an app called CPU Usage Timeliness Free 1.7.1.0 and use it to see EXACTLY which applications are using CPU cycles and interfering with performance. With it I have found that on my Tab I have an unsolved problem that is using over 100MB of memory and non-stop CPU usage between 15% and 45% of something called SECURITY STORAGE. I have no idea what it does. It can't be disabled and I don’t know where all the activity comes from. If someone know more about this and how to fix it, that will be great. Most of the performance issues I have on my Tab come from this Service that I don’t know how to tame. Surely, we can find a solution.
The system background services is one area where I'd like to know one by one, what each service does and if we need them or not, if it can be tweaked, disabled or deleted. Below is a complete list of the services I have safely disabled so far that have given me great performance boosts and with no negative issues on the system (IN BOLD), and OTHERS I WOULD LIKE TO KNOW MORE ABOUT (not bold). Please note these are background services that start automatically. The changes made to the disabled apps/services is that they are reverted to ON-DEMAND so they all still work perfectly.
CALENDAR
CALENDAR STORAGE
COM. SEC.ANDROID.PROVIDERS.DOWNLOADS
CSC
DOWNLOAD MANAGER
DRM CONTENT
EMAIL
GALLERY
GOOGLE PARTNER SETUP
GOOGLE SERVICES FRAMEWORK
MARKET
MEDIA STORAGE
MESSAGING
MUSIC
SAMSUNG ACCOUNT
SERVICE MODE
SNS
WIPEOUT RECEIVER
WORLD CLOCK
Furthermore I uninstalled several of the Samsung Apps I don’t use and STK Service and disabled these system Apps I don’t use (YOU SHOULD CHOOSE THE ONES YOU WANT TO ENABLE OR DISABLE AS YOU MIGHT HAVE DIFFERENT NEEDS):
All Bluetooth Services
All LiveWallpapers Services
Browser
CarHomeGoogle
CarHomeLauncher
Google Feedback
Screen Capture Service
Voice Search
Originally with my Tab I was getting Quadrant below 600 on average. Now, its always over 1900. This is not a "little" improvement, this is amazing upgrading. But id like this to be a starting point to learn and share more ways with everyone we can all share on things we can do to make the Tab as good as it was intended to be for everyone
Cheers!

1.4 oc is stable, and doesn't have any issues for alot of users.
all the things you disabled are all the things i use every day lol
never the less, good post, im going to use a couple apps you mentioned.

natious said:
1.4 oc is stable, and doesn't have any issues for alot of users.
all the things you disabled are all the things i use every day lol
never the less, good post, im going to use a couple apps you mentioned.
Click to expand...
Click to collapse
The first block of disabled items (in bold) from CALENDAR to WORLD CLOCK are disabled start-ups but the apps works as usual. It just frees resources not required on boot till you actually start the application when you want.
The second block from Bluetooth Services to Voice Search are all disabled as I use none of those. Items disabled can be restarted again at any time upon activating them follwing a reboot, while items deleted (like Samsung Apps and STK) are gone forever.
Ive never flashed a ModaCo Kernel and got lots of feedback regarding probelms with 1.4OC. Do you have any issues at all or none? We are using different ROMs... What Quadrant do you get currently?
Cheers

Thank you for your post.
You have solved many of my questions. Also I am User of HD2 and had the same impressions, but now with Android Nand everything was great, also started to love it.
As for GTAB'll make those adjustments you suggested, some will not disable because I use Bluetooth as an example.
Any news please keep posting.
Success!

VeEuzUKY said:
The first block of disabled items (in bold) from CALENDAR to WORLD CLOCK are disabled start-ups but the apps works as usual. It just frees resources not required on boot till you actually start the application when you want.
The second block from Bluetooth Services to Voice Search are all disabled as I use none of those. Items disabled can be restarted again at any time upon activating them follwing a reboot, while items deleted (like Samsung Apps and STK) are gone forever.
Ive never flashed a ModaCo Kernel and got lots of feedback regarding probelms with 1.4OC. Do you have any issues at all or none? We are using different ROMs... What Quadrant do you get currently?
Cheers
Click to expand...
Click to collapse
So far the oc is good, things load a little faster, especially nfs shift. Last run of quadrant was 2300-2400.
Ill try it again later after these optimizations and see how it goes, a member here has gotten 3000.

Having done nothing but root, my tab gets about 1000 quadrant score. I have tried setcpu using on demand and it actuall has made my tab worse. I am very hesitant to flash anything on the tab. It seems very involved and complicated. I have an HD2 as well and have been flashing since Android was on SD. That process is simple. Everything I have read about flashing things to the tab doesn't look that way. I really havent had any issues with my tab as stock other than a bit laggy at times. I would like to hear more about all of this. The oppinions I have read are either do it or don't do it. There are more problem posts after attempting to flash than there are good ones where it worked. I really could care less about a quadrant score to be honest, but I would like to have a faster smoother running tab. I really dont care about making calls on it either. Thats why I have a phone. JMO. I think part of the issue in this thread is that there are Euro and USA version which are completely different and require different roms and such.
I have been reading and lurking in the tab development thread for a while now and am not impressed with any of it yet. Maybe someone could shed some light on things and change my mind.

dubie76 said:
Having done nothing but root, my tab gets about 1000 quadrant score. I have tried setcpu using on demand and it actuall has made my tab worse. I am very hesitant to flash anything on the tab. It seems very involved and complicated. I have an HD2 as well and have been flashing since Android was on SD. That process is simple. Everything I have read about flashing things to the tab doesn't look that way. I really havent had any issues with my tab as stock other than a bit laggy at times. I would like to hear more about all of this. The oppinions I have read are either do it or don't do it. There are more problem posts after attempting to flash than there are good ones where it worked. I really could care less about a quadrant score to be honest, but I would like to have a faster smoother running tab. I really dont care about making calls on it either. Thats why I have a phone. JMO. I think part of the issue in this thread is that there are Euro and USA version which are completely different and require different roms and such.
I have been reading and lurking in the tab development thread for a while now and am not impressed with any of it yet. Maybe someone could shed some light on things and change my mind.
Click to expand...
Click to collapse
flash modacos kernel and rom, convert to ext4, you'll be amazed.
to OP
In startup auditor i just checked disable all, and am not having any problems, unless you are using task manager to disable
...CALENDAR
CALENDAR STORAGE...
edit: But when i check advanced task killer, it still shows that all the disabled apps are running

dubie76 said:
Having done nothing but root, my tab gets about 1000 quadrant score. I have tried setcpu using on demand and it actuall has made my tab worse. I am very hesitant to flash anything on the tab. It seems very involved and complicated. I have an HD2 as well and have been flashing since Android was on SD. That process is simple. Everything I have read about flashing things to the tab doesn't look that way. I really havent had any issues with my tab as stock other than a bit laggy at times. I would like to hear more about all of this. The oppinions I have read are either do it or don't do it. There are more problem posts after attempting to flash than there are good ones where it worked. I really could care less about a quadrant score to be honest, but I would like to have a faster smoother running tab. I really dont care about making calls on it either. Thats why I have a phone. JMO. I think part of the issue in this thread is that there are Euro and USA version which are completely different and require different roms and such.
I have been reading and lurking in the tab development thread for a while now and am not impressed with any of it yet. Maybe someone could shed some light on things and change my mind.
Click to expand...
Click to collapse
I agree. The process of flashing the Galaxy is much more dauting than anything on the HD2. I suggest you do the EXT4 file converstion. All you need is follow the step by step I wrote above. It makes a huge difference. As for everything else, I too hold off to do too much flashing. The ROM I use now is great and lighter than stock but your seems to work well so keep it. For me when a ROM is good I just use it. When I bought the HD2 I flashed it 2 times with a custom ROM till i found one that worked for me and kept it for 8 months. But backing up and restoring WinMo is much easier... on Androind its all more complicated if you dont know what you are doing. Disable some start-ups on your unit, convert the file system to EXT4 and make sure you have nothing on your home screen doing a lot of refreshing and your tab will work great

natious said:
flash modacos kernel and rom, convert to ext4, you'll be amazed.
to OP
In startup auditor i just checked disable all, and am not having any problems, unless you are using task manager to disable
...CALENDAR
CALENDAR STORAGE...
edit: But when i check advanced task killer, it still shows that all the disabled apps are running
Click to expand...
Click to collapse
Is everything working 100% on that ROM? I do not want any ROMS that are having problems.

I too am not impressed with anything that us out yet...seems like any ROM process is tedious and complicated.
Glad the thread starter modified his tab to his liking, but what's the point of having it if you need to drastically change everything. I have a rooted DInc and not use any of things......didn't really see a performance gain with set CPU.
I'm going to continue waiting for something more reliable and use my tab the way it was meant to be, with all its hardware and widgets.
dubie76 said:
Having done nothing but root, my tab gets about 1000 quadrant score. I have tried setcpu using on demand and it actuall has made my tab worse. I am very hesitant to flash anything on the tab. It seems very involved and complicated. I have an HD2 as well and have been flashing since Android was on SD. That process is simple. Everything I have read about flashing things to the tab doesn't look that way. I really havent had any issues with my tab as stock other than a bit laggy at times. I would like to hear more about all of this. The oppinions I have read are either do it or don't do it. There are more problem posts after attempting to flash than there are good ones where it worked. I really could care less about a quadrant score to be honest, but I would like to have a faster smoother running tab. I really dont care about making calls on it either. Thats why I have a phone. JMO. I think part of the issue in this thread is that there are Euro and USA version which are completely different and require different roms and such.
I have been reading and lurking in the tab development thread for a while now and am not impressed with any of it yet. Maybe someone could shed some light on things and change my mind.
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App

dubie76 said:
Is everything working 100% on that ROM? I do not want any ROMS that are having problems.
Click to expand...
Click to collapse
Sure is, I use my tab as a phone replacement so I had to have everything work, you will be waiting eons for a decent update from samsung
Sent from my Galaxy Tab of awsomeness

AlpineM3 said:
I too am not impressed with anything that us out yet...seems like any ROM process is tedious and complicated.
Glad the thread starter modified his tab to his liking, but what's the point of having it if you need to drastically change everything. I have a rooted DInc and not use any of things......didn't really see a performance gain with set CPU.
I'm going to continue waiting for something more reliable and use my tab the way it was meant to be, with all its hardware and widgets.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
How are you not impressed if you haven't tried anything?
Sent from my Galaxy Tab of awsomeness

Thank you for your detailed post. While I agree with you that the stock SGT rom and browser suck but where do you think the JMI, JMF, JMx ROMs coming from?
Most ROMs I've seen (except for CM) are based from some sort of Jxx
Please keep the tweak posts going. Good stuff and thanks!

natious said:
How are you not impressed if you haven't tried anything?
Sent from my Galaxy Tab of awsomeness
Click to expand...
Click to collapse
Not impressed with all the problems being posted just tring to flash it, and how complex it is to do it. Guess that's what I meant. Flashing the hd2 is a very simple process. Tab is not
Sent from my HTC HD2 using XDA App

My boy,
Only getting my Galaxy tomorrow but looking through threads on my favorite forum.
And guess the first one I happen into... I will follow avidly.

Hi dubie76,
Try an app called OCLF 2.0 on the Market. It is a Lag fix app for the Samsung Galaxy S which also works on the Tab.
https://market.android.com/details?id=com.rc.QuickFixLagFixR2
You have to install EXT2 tools and then install one click lag fix, both are done within the app.
I had this on my Tab before flashed to a custom ROM. The tab was much faster and did not have and lag compared to stock, the Quadrant score was around 1900.
Also you can uninstall the modifications in the app and easily reverse back to stock. The only disadvantage is you will loss about 800mb of internal memory (the 2Gb space), so if you don't have much space left, you will need to uninstall some apps and reinstall them once you applied the lag fix.
P.S. thanks to OP for the SystemApp Remover & Startup Auditor suggestion.

Custom ROMs?
Hi everyone!
Consider this:
The locked GTab (in standby) on an original ROM with a connected to it BT headset wakes up after replying a call from BT and can potentially have anything pressed as being in the bag due to its size...
My point is that there is NO fix for this on XDA therefore why should I expect any significant advancements from a custom ROM if such simple things cannot be fixed on Android.
My personal view is that Android is unfortunatelly not as flexible for adjustments as WinMo (i have HD2 as well with a wonderful custom Artemis ROM).
I've tried two Roto ROMs on my GT and they havent provided any noticeable enhancements in performance to my eye (perhaps some rating went up - I dont care about tech stats). I reverted to stock ROM P1000XWJMI that works as fast for a "regular user".
I am sad to resume my experience with hacking the GT as not worth it: you get serious risk of getting the GT bricked (much more complicated than with WinMo), loose the warranty and are open for instability and sudden incompatibilities with crashes.
On the third custom ROM installation attempt I was stuck on a black screen after powering on (stuck on the bootloader!) and couldnt initiate flash for multiple times. I was shocked and very nervous. Thats when the stock ROM saved my ass and I am not willing the risk of playing around any more with non-firmware ROMs for Android GT.
Regarding the alternative screen lockers available - please do not suggest Screen Suite (the best of the worst) and things like No-Lock (to get rid of the original locker) as they all mess up once in a while (tested) with the default ROM settings and the original core locker.
PS
In my view the best thing we can and should do first of all is to COMPLAIN to SAMSUNG Tech Support and Software Developers (I did twice already).
If every one of us from theese GTab forums would do this they would definitely get faster with resolving issues.

mrbuz said:
Hi everyone!
Consider this:
The locked GTab (in standby) on an original ROM with a connected to it BT headset wakes up after replying a call from BT and can potentially have anything pressed as being in the bag due to its size...
My point is that there is NO fix for this on XDA therefore why should I expect any significant advancements from a custom ROM if such simple things cannot be fixed on Android.
My personal view is that Android is unfortunatelly not as flexible for adjustments as WinMo (i have HD2 as well with a wonderful custom Artemis ROM).
I've tried two Roto ROMs on my GT and they havent provided any noticeable enhancements in performance to my eye (perhaps some rating went up - I dont care about tech stats). I reverted to stock ROM P1000XWJMI that works as fast for a "regular user".
I am sad to resume my experience with hacking the GT as not worth it: you get serious risk of getting the GT bricked (much more complicated than with WinMo), loose the warranty and are open for instability and sudden incompatibilities with crashes.
On the third custom ROM installation attempt I was stuck on a black screen after powering on (stuck on the bootloader!) and couldnt initiate flash for multiple times. I was shocked and very nervous. Thats when the stock ROM saved my ass and I am not willing the risk of playing around any more with non-firmware ROMs for Android GT.
Regarding the alternative screen lockers available - please do not suggest Screen Suite (the best of the worst) and things like No-Lock (to get rid of the original locker) as they all mess up once in a while (tested) with the default ROM settings and the original core locker.
PS
In my view the best thing we can and should do first of all is to COMPLAIN to SAMSUNG Tech Support and Software Developers (I did twice already).
If every one of us from theese GTab forums would do this they would definitely get faster with resolving issues.
Click to expand...
Click to collapse
So what if the screen goes on in your bag, unless you have a fresh finger floating around in there nothing can press any buttons on the capcitive screen, also my tab I just hit the lock button in a bt call, screen turns off phone stays on
Sent from my Galaxy Tab of awsomeness

Im so confused. I have my tab rooted and oclf 2.0. Im scoring 2200 in quadrant and.my dolphin hd browser is SO laggy. Even with flash disabled. Any ideas?

koxville said:
Im so confused. I have my tab rooted and oclf 2.0. Im scoring 2200 in quadrant and.my dolphin hd browser is SO laggy. Even with flash disabled. Any ideas?
Click to expand...
Click to collapse
because quadrant doesn't mean **** in the real world, i score 2300 but thats with the 1.4 oc.
Give miren a try, tbh its the best

Browser killed after phone sleep for a while

If I load a few pages in a browser (have tried many different browsers, all works the same) they gets killed after a sleeping for a while, meaning I have to reload the content. It seems to happen after a certain time not being used.
This did not happen on my HTC Desire HD.
I tried today to place a browser (miren) into the /system/app folder, to see if that made any difference, but it didn't.
Why is this happning? any why not on the desire HD?
any hack I can do to fix it?
It's useful to when on fast internet load 10 pages and read them sometime later.

Just a guess, but it may be a RAM management thing. My N1 will exit the browser occasionally even when the phone is asleep to free up RAM.

I'm experiencing this issue as well and it's irritating. I wondered, too, if it was a ram management issue, but it'll happen even after just a few minutes with no other apps launched. None of my other phones have closed the browser for ram issues without a long time of inactivity and many other apps opened using lots of ram.
Is there some way to specify the browser as preferred or something so the system won't close it, in case it is ram management?

maxh said:
Is there some way to specify the browser as preferred or something so the system won't close it, in case it is ram management?
Click to expand...
Click to collapse
I guess it has something to do with ram management, so how to adjust that?
I tried putting it in system folder, that didn't make any difference, tried running it as root, no difference.
Maybe another kernel would do it differently? anybody knows? Don't want to spend lots of time installing a new kernel if it doesn't make any difference.

This is both a browser and a ram management issue.
Android automatically kills off apps that are using ram on the background after they are inactive for a period and most browsers, the stock one included, tend to hog a surprising amount of memory which in turn makes them priority number 1 for android to kill off.
I have no answer as to how to fix this problem aside from trying other browsers, sorry.

akselic said:
This is both a browser and a ram management issue.
Android automatically kills off apps that are using ram on the background after they are inactive for a period and most browsers, the stock one included, tend to hog a surprising amount of memory which in turn makes them priority number 1 for android to kill off.
I have no answer as to how to fix this problem aside from trying other browsers, sorry.
Click to expand...
Click to collapse
what you're saying is not completely accurate, because this does not happen in other phones, desire HD has less RAM also.
I don't think it's a browser issue, as I have tried many different and it will work the same. The ram does not need to be critically low before it gets killed, it might happen when there is more than 250mb free

It happens for me with messaging app also. It can be the only thing running with loads of free ram. And suddenly its killed, very annoying because its pretty slow starting again. Never happened in my SG SII
Sent from my GT-N7000 using Tapatalk

nick5000 said:
what you're saying is not completely accurate, because this does not happen in other phones, desire HD has less RAM also.
I don't think it's a browser issue, as I have tried many different and it will work the same. The ram does not need to be critically low before it gets killed, it might happen when there is more than 250mb free
Click to expand...
Click to collapse
The Note isn't my first android phone that does this (mind you I haven't owned any HTC devices) but if this is the case then it means that ram management on the Note is quite aggressive. The only way to "fix" this is with custom kernels unless Samsung does something about it themselves (and I wouldn't count on that)

I'm experiencing the same problem but I don't really mind since I don't open many tabs at time. So I just have to go to the history tab to reopen the page.
At least for the stock browser it would have been better just to save the URL while killing the browser so when u open it again it will reload all the pages.
Sent from my GT-N7000 using xda premium

Is it possible the S-pen places greater demands on the Note's RAM than other phones? Perhaps it tries to keep a certain amount of RAM free at all times for this purpose.

Maybe, but remember that with higher resolution and higher amount of RAM the device will use more RAM.
An example is computers. I have a netbook and a standard notebook (laptop). The netbook has 1GB RAM and the resolution is 1024x600 and running Ubuntu. It uses 90MB at boot (after tweaking)
My notebook has 2GB RAM, and the resolution is 1366 x 768 and is also running Ubuntu. It uses 200MB at boot (same tweaks as the notebook)
- Higher resolution = More pixels and more information that needs prosessing on the screen
- More RAM = It can allow itself to use more
I've seen A LOT of this at Ubuntuforums and other places with people with 8 and 16GB RAM, and they are complaining about high RAM usage. It's the same with computers with HD screens.
I've tried to find the thread about this, but i can't find it

BazookaAce said:
Maybe, but remember that with higher resolution and higher amount of RAM the device will use more RAM.
An example is computers. I have a netbook and a standard notebook (laptop). The netbook has 1GB RAM and the resolution is 1024x600 and running Ubuntu. It uses 90MB at boot (after tweaking)
My notebook has 2GB RAM, and the resolution is 1366 x 768 and is also running Ubuntu. It uses 200MB at boot (same tweaks as the notebook)
- Higher resolution = More pixels and more information that needs prosessing on the screen
- More RAM = It can allow itself to use more
I've seen A LOT of this at Ubuntuforums and other places with people with 8 and 16GB RAM, and they are complaining about high RAM usage. It's the same with computers with HD screens.
I've tried to find the thread about this, but i can't find it
Click to expand...
Click to collapse
Excellent points.

solved
So I played with root explorer and moved many of the samsung apps that I don't use out of /system/app folder.
I'm not sure what exactly did it. The email program was the only one I deleted (by accident) - but it was set to not sync, so it shouldn't be working in the background anyway.
I also put the Miren browser in the /system/app folder. Didn't notice any difference to that at first, so not sure if that contributed at all.
Another thing I did was to install adfree. It didn't seem to work, but I don't know if it made any changes that would make a differnece. I'm just listing up everything I did that day.
But the biggest change after all this is:
BATTERY LIFE !!
has doubled! I used to get around 10-12 hours with moderat usage, yesterday I was at 50% after 12 hours usage. And Miren browser now does not shut down, except I push the phones with other ram hungry applications.
Funny is, that display used to be high up on the battery usage statistics, but now Andoird OS is very high, but the phones use much less battery! Doesn't make any sense, but I don't complain..
I'm running stock european 2.3.6 firmware that I downloaded from sammobile.com. I rooted it, but didn't notice any differnce before or after the root.

Can you list down what apps did u remove? Thanks

entaro said:
Can you list down what apps did u remove? Thanks
Click to expand...
Click to collapse
I moved the following to /data/app, but they don't seem to work anymore, not sure what is needed to make them work, but anyway disabling them did the job.
Email was deleted.
Analogclock,
bluesa
buddiesnow
crayonphysics
days
dualclock
emailwidget
fmradio
kobo
livewallpapers
oceanweatherwxga
samsungapps
samsungappsuna3
samsungservice
samsungwidget_news
samsungwidget_stockclock
splannerappwidget
videoeditor
voicetogo
windyweatherwxga
zinio

nick5000 said:
If I load a few pages in a browser (have tried many different browsers, all works the same) they gets killed after a sleeping for a while, meaning I have to reload the content. It seems to happen after a certain time not being used.
Why is this happning? any why not on the desire HD?
any hack I can do to fix it?
It's useful to when on fast internet load 10 pages and read them sometime later.
Click to expand...
Click to collapse
I am pretty sure it is not a memory management issue. I come from the GalaxySII and it never happened despite having many browser windows open. I think this phone now is harder trying to close unused apps, based on inactivity time, to improve battery life (which is much better than SGS2) and shuts down apps that may not allow the CPU to go to deep sleep.
To me it does not look like an issue, more like a feature, it is not like you get you work "killed" or unsaved. And you could always load pages from your browser's history. -I know, I know, you like to preload your webpages to look at them later.-
Also, updated versions for the note have several options to battery saving within the browser, have you tried them?

runaway64 said:
I am pretty sure it is not a memory management issue. I come from the GalaxySII and it never happened despite having many browser windows open. I think this phone now is harder trying to close unused apps, based on inactivity time, to improve battery life (which is much better than SGS2) and shuts down apps that may not allow the CPU to go to deep sleep.
To me it does not look like an issue, more like a feature, it is not like you get you work "killed" or unsaved. And you could always load pages from your browser's history. -I know, I know, you like to preload your webpages to look at them later.-
Also, updated versions for the note have several options to battery saving within the browser, have you tried them?
Click to expand...
Click to collapse
More excellent points. I'll bet you're right.

runaway64 said:
I am pretty sure it is not a memory management issue. I come from the GalaxySII and it never happened despite having many browser windows open. I think this phone now is harder trying to close unused apps, based on inactivity time, to improve battery life (which is much better than SGS2) and shuts down apps that may not allow the CPU to go to deep sleep.
To me it does not look like an issue, more like a feature, it is not like you get you work "killed" or unsaved. And you could always load pages from your browser's history. -I know, I know, you like to preload your webpages to look at them later.-
Also, updated versions for the note have several options to battery saving within the browser, have you tried them?
Click to expand...
Click to collapse
Yeah, it might be something to better battery life, but then it's the complete opposite of my recent findings that the battery life was much better while the browser does not get killed (after removing system apps).
I guess this issue/feature wouldn't have been a problem if I lived in a world with perfect high speed internet access all the time. here in China, it can get slow, some pages take a long time to load, so why should I want to reload them..
also, when I fly, i like to load up 10 pages and read them while up in the air. last week I was very disappointed when i found out that just leaving the phone by itself for halv and hour had made the browser restart.
Anyway, I'm happy now, after the mod Miren browser does not reload alot, only after loading several heavy progams in between. Still, it makes me want to optimise it more, so i could get even more free ram to use.

nick5000 said:
Yeah, it might be something to better battery life, but then it's the complete opposite of my recent findings that the battery life was much better while the browser does not get killed (after removing system apps).
Click to expand...
Click to collapse
Wait, what? I interpreted your results as consistent with his hypothesis. You removed apps that were draining the battery, allowing better battery life. Perhaps that's why the system is no longer compelled to shut down the browser.

bigmout said:
Wait, what? I interpreted your results as consistent with his hypothesis. You removed apps that were draining the battery, allowing better battery life. Perhaps that's why the system is no longer compelled to shut down the browser.
Click to expand...
Click to collapse
he said that the better battery life is because the browser gets shut down.