I bought the Verizon Galaxy Tab here in the US (Model SCH-I800, SKU SCHI800BKV) and it appears to be running sub-30 frames per second consistently. I've tried EStrongs Task Manager, Advanced Task Killer, and Android Assistant to try to find background programs that are hogging resources, but they're all below 1% (including Slacker, which I can't uninstall). A Quadrant test gave me ~900 score. I know the CPU is supposed to be a Cortex A8 Hummingbird, but every system spec I've run it through has told me it's an ARMv7 Processor rev 2(v7I) or something nearly identical. Did I get a slower CPU like the Wi-Fi version?
Certain games will run super-speedy, but most everything, including the web browser, the settings menus, and the market, run seemingly below 30fps. I can't get it to consistently run a smooth 60fps which every other Tab (besides the Wi-Fi version) seems to run at.
What can I do? Is there any other benchmarking software I should run? Should I take it back to Verizon?
Related
hi all, i'm currently using ATK advanced task killer, and I realise that when my phone is idling, i have apps like video player and whatever apps that are running and sapping up my ram... may I know is it normal? and is there a way to stop this?
ngkkv said:
hi all, i'm currently using ATK advanced task killer, and I realise that when my phone is idling, i have apps like video player and whatever apps that are running and sapping up my ram... may I know is it normal? and is there a way to stop this?
Click to expand...
Click to collapse
It's normal, delete apps
What I notice is that related apps sometimes run together, so if I'm using video or audio the other type seems to pop up within a few minutes of each other more likely than random app X. There are other cases that are similar for me.
Also, if I use the marketplace, everything under the sun runs and stays in memory. Essentially, Android is more or less designed to use your RAM so the programs in it will launch faster. Empty RAM is wasted RAM and if the system detects low RAM it'll free some up for you.
hmm.. that's probably one thing i dislike...it seems to lag sometimes because of that, even though it boasts 1GHz processor.
Hi fellas,
Something's been peeving me lately with the Atrix, and it's got to do with its memory handling & auto-killing functionality.
This particular situation has been driving me nuts:
I like to use both the native browser & and the Opera browser. Primarily I use the native browser, which is set as the default, and Opera when I want to check something and I want the full (non mobile) webpage layout and its superior (in my opinion) rendering quality and speed.
So, say I've got Opera open on Engadget or XDA, one or two tabs open. I hit the Home button and open Youtube to look something up. Finish the video, hit the Home button again, and launch Opera, and it has exited already and has to reload my tabs again. This of course can cause issues like losing my place in the page or a flash video I had paused, or a message I was typing and wasn't done with.
In this simple example, all I did was launch a browser, open 2 tabs (40-60 or maybe even 80 MBs of RAM usage, depending on page complexity), hit the Home button, launch the YouTube player (30 to 50 MBs RAM usage), hit the Home button again and Opera's already been killed.
OS Monitor shows there's about 470 MBs of RAM free.
What gives? Checking the autokill settings it shows that the OS will kill empty processes when free RAM hits 82 MBs of free RAM (default settings, haven't messed with them)
This behavior doesn't happen only right after a fresh reboot. Once I've opened a few apps, google readers, twitter, facebook, camera/gallery, browser etc., it happens every time. I say this because, while I'm not a programmer (beyond high school level C++ and general computer curiosity), from what I understand by watching the app life cycle videos on Google's Android programmer site, if Opera and YouTube were the last apps to be launched, they should have the highest priority in being kept in memory and not being killed, and previously open apps should be killed off to reclaim memory before them.
I found that using Gemini app manager I can set an app to not be killed automatically, and while I understand that it's not recommended that this is done by end users, it does work, and I use the Exit button in Opera to exit it once I'm done using it.
It just seems ridiculous that I always have between 350-450 of free RAM available to the system, while apps that I use often end up being killed in the background.
Before someone jumps on me, I understand that Android apps are designed to be shut down and reopened seamlessly. My annoyance stems from the behavior of a phone that has 836 MBs of RAM to work with, and about 570 available on startup (I've frozen several motorola processes I don't use, such as the social network integration and home launcher).
I just tried what you did (open opera, loaded bbc and endgadget, watch a youtube video than returned to opera) and opera retained everything including webpage, where I have scrolled to etc. I would suggest you to unfreeze the moto apps and try again, maybe that is what is causing the problem. Sorry I could not be of greater help =(
I'm not disagreeing with you -- like I said, it's not the case after a fresh reboot, or perhaps when not using the phone heavily. It had been a couple of days since rebooting the phone for me, and kept happening all evening long every time I switched apps.
Still, even when I force keep Opera open through the Gemini third party app manager, and while opening other apps, the RAM usage never goes below 300. The OS is overly aggresively in keeping RAM free, and considering it never falls below 100 MBs free of RAM, it shouldn't be shutting down apps EVER -- at least according to the autokill levels. Is there something else I should be looking at in determining when Android kills apps open in the background?
Was it just a fluke due to memory leaks, etc?
Edit:
Further research shows that Gemini app manager doesn't stop it from being killed, but rather removes it from its own auto task kill list (which I don't use). Seeing Opera stay open for a while after a fresh reboot shows that after two or three days of being used, the phone's memory management gets bogged down & that's what caused the very short app lifespan.
I wouldn't mind rebooting more frequently if it wasn't for that damned battery jumping issue.
My note's ram is always above 600 mb. ...pls help
Sent from my GT-N7000 using XDA App
I always use back button to close apps. Clicking home button will not close apps but minimized. More apps opened equal more RAM used.
Sent from my GT-N7000 using Tapatalk
Totally normal. Apps are loaded into RAM so when you want to open an app it loads faster. That's how Android works.
My advice is to not go on a killing spree and kill every app that's running. This will make your device slower and it'll use more battery since it has to use more power to load the apps again and again - and again.
If you want to free up some RAM you can do this:
- Switch launcher. TouchWiz is a resource hog, and you'll gain some RAM if you switch to another launcher like ADW, GO Launcher or LauncherPro
- Freeze/Delete system apps that you don't use/want. If you're not using SocialHub, Reader and Swipe, there's no reason having them. Freeze them and they won't use RAM.
- Flash a custom ROM. You can flash a custom ROM if you want. Your device will be faster and use less battery. Some ROMs has been stripped for "bloatware" like SocialHub etc. so they're fast "out of the box".
I'm currently running ROMOW ROM with ADW EX (and i've frozen a lot of system apps), and my Note is only using around 250MB on boot.
What's the problem with that? You have 800 MB for OS and applications, it's meant to be used. Applications loaded, compiled and the code is stored in RAM, the more RAM you have the more apps you can keep open. With less RAM (like my previous phone, Galaxy S, which had only 330 MB available), the apps have to be unloaded from RAM when you open a new one, so the CPU works more, loading apps again and again.
The RAM contains compiled apps and cached data, to make access faster and save battery, it's good that it's used. Android manages the RAM itself, if you launch an app that needs RAM, it will make room for it, discarding the least used pages. You don't need to take care of this yourself.
In the Samsung system administrator there's a button to clear RAM, press it and it will unload even the touchwiz interface, you'll end up with 400 MB used, but it will increase soon, as apps are opened.
The issue is that when you run a high resource game, have a few web pages open or use google earth then the device closes down touchwiz to free up memory so you may find your homescreen empty or on other occassions android closes the internet application if you switch to another program even briefly so multitasking is poor on the Note.
Its absolutely true,RAM management is implemented very badly on the GNote.Even my HD2 has much much better RAM management with its mere 480MB.
However since this is my first Android device I am not quite sure if this is a Samsung thing or an OS inconvenience.
On my HD2 I could keep multiple web pages open for latter offline reading when internet access is not available and it would keep it in memory even though many services would still be running.
Unfortunately its not the same with my Note,it just rushes to close apps on the first occasion.
Say what you may but being a long time PDA user I found that the old shot-in-the-head by its very same creator the Windows Mobile is the best multitusker I have ever used despite the fact that on those days the RAM was just minimal.
High RAM usage is due to the high number of pixels that need RAM & processing to drive them.
On my old stock rom (KKA) I had the same....usually over 600Mb used.
A few days ago I flashed the latest LA4 stock rom. And what a big improvement that was. Smoother, 2 days on a battery with moderate use. And about 420MB ram used on average. A very big improvement.
I think it would be better if we know which version you have.
So you could upgrade to a newer version or just flash a custom rom.
most of the customroms are better than the stockrom
airwater9 said:
High RAM usage is due to the high number of pixels that need RAM & processing to drive them.
Click to expand...
Click to collapse
Yup, that's also correct.
Hi all,
I guess ever since getting the Nexus 7 when it came out, I've been trying to reduce lag. It has become as sort of project of mine. The last year, I have gone over lots of ROMs, kernels, tweaking tools, and tried lots of good (and very much bad) stuff.
So far, I've come quite far and I am quite happy with the way my Nexus 7 runs. The Nexus runs great in all other apps, really. Browsing is smooth and not comparable in any way to what I started out with. I have some Danish, poorly designed sites that are quite heavy, and I get no lag.
Apart from one thing - i get BAD lag when scrolling down a list which has images in it. I also get minor lag at other lists, but images makes it horrible. My two best examples are the play store (almost unusable) and gReader (slightly better with images off in lists, but hey, shouldn't have to be like that).
I've been googling loads and it seems very few people have the same problem? I've had this problem with all kinds of ROMs, kernels, tweaks, whatever really. I can have a crap setup with a million services running and a google now process gone haywire with cpu at 75 degrees celsius, yet the stutter is just the same in play store and greader (e.g.).
My current setup (but note, I've tried many with same result):
- Completely fresh install of recent CM10.1 nightly
- franco kernel (1.7GHz CPU, 700MHz GPU, 512Kb read-ahead, interactive, deadline, fsync off, gpu scaling off, wifi performance streaming)
- Almost all services disabled, including most of google's, meaning I have greenify running, a few under google services and android keyboard
- Sync is currently off
- Currents is not installed
- I've got fstrim installed and run that recently on all partitions
- I've got 9GB of 13-ish free at the moment
- Location sharing off
- Accessibility off
- No widgets, completely empty homescreen (I use Apex, not locked in memory)
I've been testing on a 100/100Mbit line fiber and 60/15Mbit LTE and identical experience.
I DO have Xposed installed atm, but after this fresh install (and many other similar times), I go straight to play store on a fresh install before installing anything. Same problem always there.
I had been using Trinity kernel for quite some time, at the time I adjusted read-ahead a lot, but in this situation a standard read-ahead actually means less lag for me. I guess it means more, small lags, actually, less noticeable.
I've been testing Seeder and similar apps recently, but get no particular difference with this problem.
When using the older version of Google Play, it is much more smooth, yet in the lists with apps it still stutters. Like 2-3 stutters a second, at times it hangs for a whole second, when scrolling down. It stutters each time and image is placed.
My experience: It seems the act of scrolling AND loading images doesn't work well in parallel.
I really hope someone can help me understand the problem, or, if so lucky, help me eradicate (or at least) reduce it.
Mkay, so it seems I am in a situation, where lagfix etc. doesn't alleviate the problem with very low random write speeds. I have done Forever Gone and various other things, but it just doesn't help. So, after googling a lot again, with inconclusive results:
What the feck is the conclusion on those low read speeds? I have plenty of space free...
delanvital said:
the play store (almost unusable)
Click to expand...
Click to collapse
The Play Store has always stuttered horribly when scrolling, as does Play Music. From my own observations, this is an issue with the implementation of rendering in these applications, rather than a lack of system performance. It is not isolated to the Nexus 7 either; it occurs within these applications on every Android device.
When you load the Play Store (or Play Music with album art) and begin to scroll, images are loaded when they come into view and unloaded once you move past them. I would surmise that the behaviour is intended to conserve RAM on less capable devices, however the consequence appears to be that this constant loading and unloading of images while scrolling results in stuttering. I have tested this hypothesis by comparing image-based applications (such as HTC Music) which do not implement the aforementioned function against those that do. The result is always that the former are completely smooth, while latter stutter incessantly.
Now that most new Android devices are shipping with 2GB of RAM, I do hope that Google will either remove this function or disable it on current devices (based on the brand/model the device identifies as).
Looking for maximum speed without hardware modification (no heatsinks etc).
Using GTX Rom on intel sofia unit.
I use a combination of spotify, waze, google maps, and pocket casts. Just these four apps. Are there specific versions of these apps that work best for Android 6.0?
Does nova launcher significantly slowdown the unit?
Does titianium backup slowdown the unit? Does freezing any additional processes through TB help?
I did search the forum for these specific questions, thanks for the help guys.
juandhi said:
Looking for maximum speed without hardware modification (no heatsinks etc).
Using GTX Rom on intel sofia unit.
I use a combination of spotify, waze, google maps, and pocket casts. Just these four apps. Are there specific versions of these apps that work best for Android 6.0?
Does nova launcher significantly slowdown the unit?
Does titianium backup slowdown the unit? Does freezing any additional processes through TB help?
I did search the forum for these specific questions, thanks for the help guys.
Click to expand...
Click to collapse
There can be differences in Launcher speeds themselves in how they start apps, do screen animations (opening/closing windows, swipes), but once in the background with a running app in the foreground it doesn't make a difference at all, as the launcher just "sits" there. Only the memory footprint can have influence as a micro launcher of 50-250Kb will not take as much memory as Nova up to quite some MBs: 100 ~350 MB, depending on running services, features, etc. And these services can take slightly more cpu, but nothing to worry about.
Same for Titanium. A small portion remains in memory and just sits there waiting for the next scheduled backup (and only if you have that scheduled backup).
The GTX-Rom is already pretty optimized. There is not much too be gained. Simply do not use animated (3D) wallpapers. Even those do not take much resources, but if you want to use every % of the CPU/memory efficient, you should not enable them.
Note also that most apps have more then enough memory in the 2GB memory space on 6.0.1. And having quad-core/8-core CPU's will spread the load. It is not like in the "old days" with single core/dual core cpu's and a more primitive task manager on older Androids.