Related
I've had my suspicions about this since I first got the Droid X2. I think it may be possible for much of the lag many (most/all?) people experience at some time or another.
As a test, I can check free RAM in Advanced Task Killer when I first boot up the phone, and it will hover somewhere 150 megs with all user processes killed.
Then, when I check after 24 hours of constant use (with intermittent charging periods) I will struggle to get 100 megs with all user processes killed.
Finally, if I reboot the phone, I will be able to obtain a decent amount of freed-up RAM again.
Anyone experiencing anything similar?
Now, I must mention, I'm operating under the assumption that the X2 does not cache apps or files in the RAM. I suspect there is too little RAM at such a minimal speed to be able to clear RAM fast enough in the event that something non-cached is called on. I mean, even Microsoft was slow to use this cache method, as they first introduced it in Windows 7. A good example of this in Windows 7 is if you check the Task Manager, you will see that roughly only a quarter of your RAM is ever actually labeled as "free", even if you currently have no programs open or are using minimal amounts of RAM.
And it certainly doesn't feel as if the cache is working as intended if Motorola did infact implement it on our phones.
I have contimplated over this for quite some time and have also came to the same conclusion. But the real question is: What can we do about it?
Most likely nothing.
Not sure of this is actually the case but when V6 is ran for instance it does talk about cached apps and gives an "actual" free ram reading. I would guess that zepplinrox would not have worded it that way if it was not the case but I have no real evidence either way.
Sent from my DROID X2 using xda premium
This did happen to me when I ran Advanced Task Killer on cm7. I'd start with a very good 190 free ram (insane I know) and after a few hours I'd struggle to brake 110
Sent from my DROID X2 using Tapatalk 2
This is the nature of Android and Linux in general. When you start an app (or a process), it will remain in memory until it is cleared by the OS. The problem with task killers and Android 2.3.x and above is this: Android 2.3.x and above RESPAWN the killed task since the OS did not kill it. Plus, there is no way to FORCE to OS to kill an app that is in the background. What Android does is renice the process until it is a positive number, greater than 1, then it kills the process. Android 2.3.x was designed to "auto manage" those tasks. If you run htop from an ADB session and launch apps and use the back button to back out of them, you will notice that the amount of free memory diminishes. Then, after sitting for a time, the amount of free memory slowly begins to increase. When an app that requires a bunch of memory is launched, the Android will kill those background apps to free up more memory. In theory, it is a great way to manage the memory. In this respect, apps that have been launched in that past will start up faster. Personally, I like having control over things. You could possibly write a script that will renice a process to something like +20 and then Android will kill it automatically, but that would be a very risky prospect as it might kill RUNNING foreground apps as well.
Hope this little explanation helps!
Ciao!
DX2 Version History lesion / Android Process Cache
theredvendetta said:
I've had my suspicions about this since I first got the Droid X2. I think it may be possible for much of the lag many (most/all?) people experience at some time or another.
As a test, I can check free RAM in Advanced Task Killer when I first boot up the phone, and it will hover somewhere 150 megs with all user processes killed.
Then, when I check after 24 hours of constant use (with intermittent charging periods) I will struggle to get 100 megs with all user processes killed.
Finally, if I reboot the phone, I will be able to obtain a decent amount of freed-up RAM again.
Anyone experiencing anything similar?
Now, I must mention, I'm operating under the assumption that the X2 does not cache apps or files in the RAM. I suspect there is too little RAM at such a minimal speed to be able to clear RAM fast enough in the event that something non-cached is called on. I mean, even Microsoft was slow to use this cache method, as they first introduced it in Windows 7. A good example of this in Windows 7 is if you check the Task Manager, you will see that roughly only a quarter of your RAM is ever actually labeled as "free", even if you currently have no programs open or are using minimal amounts of RAM.
And it certainly doesn't feel as if the cache is working as intended if Motorola did infact implement it on our phones.
Click to expand...
Click to collapse
Your question is a bit complex. See back when Droid X2 first was released it had 2.2.3 for most users, and didn't have very good application memory management. This was the start of many applications such as "Advanced Task Killer" that you mentioned. These apps were supposed to help in closing apps that were running all the time.
Things changed a bit with the Gingerbread (2.3.3) release. This initial release made the Droid X2 useable. In my opinion the DX2 prior to Gingerbread was nearly a brick! I had many reboot issues, FC, connection issues, GPS issues, etc. With 2.3.3 many issues were eliminated, while others were reduced enough that they didn't bother me TO bad.
2.3.4 came out to fix battery issues largely...
Now I realize you weren't asking for a history lesion, but it is useful to know these things to know where things were and where things are today. I am currently running 2.3.5/412 and have been for months. I can say from experience, Android DOES cache background processes. I thought it did back in 2.3.4, but i can't remember... I don't think it did back in 2.2.x or at least the OS didnt' inform the users via GUI.
Your question about performance though? Yeah the DX2 is crap! I love the physical layout, but it has MANY issues with performance... some have been reduced by doing build.prop edits, yet I have realized that many who post these edits have posted wrong.... for example, they are increasing the buffer sizes thinking this will help internet speeds. This is super complex, but Google "Buffer Bloat" and you'll see how larger buffers often mean greater throughput, but MUCH greater latency....
simply put... big buffer == faster download of individual files.... smaller buffer == slightly slower download but MUCH more responsive
I'm not sure if that answered your question or not... let me know how I did or if I just rambled perhaps =P
I wanted to put a list together to compare results of build times (PLEASE, no fan boys here!). The more info you can list, the better visibility is into the amount of time it takes. I'll start with my machine, what I built and how long it took.
The important parts are processor, ram, operating system, what android os you built, any tweaks you used, and if you have a ssd hdd. And, of course total time! I will list mine in a format for easy reading:
-Sony vaio vgn-nr110
-2gb of ram at 533mhz (upgraded )
-Intel pentium dual core t2310 processor
-running ubuntu at the time. I want to say it was version 10.04(been a while)
-no ssd. Regular laptop hdd
-built cm7 for Optimus s
-used the -j4 flag on make
=approx 4-6 hours (was cleaning while it ran because I knew it would take some time)
Mine was a full build/compile from scratch. Please state whether yours is or isn't, and if you used any special tweaks, etc. Do not include sync time in the total time as that is dependent on the Internet connection and not the machine itself (most people won't, but wanted to have it in here just in case)
My purpose behind this is to get a good idea of what type of system specs perform best with building android roms. If there are any tweaks or tricks that anyone would like to contribute, that would be great too! Please try to stick to the format that I have listed for my machine to make it easier for everyone to read.
As a treat: I will have more results for everyone in a week or two on a new machine.
Amd X2, 2 gb ram, 1tb hdd... Build time 4-5 hours, for cm9 for sprint sgs2, and 3-4 hours cm7
Sent from my SPH-D710 using xda premium
Asus i5 normal HDD 8GB ram
cm9= 65 - 75 min _ simple mka bacon no -j
Cna = 75 - 90 min _ simple mka squish no -j
Aokp = 65-75 min _ simple mka bacon no -j
I try to not have anything else open not even file browser or chrome (usually it will add twenty to forty extra minutes if it's on) although these are my best estimate numbers, time results vary. I use cache and restart Ubuntu before building to let it take the lead over everything else. Building while the PC has been active for over a day seems to always take longer. Aokp has been the record holder for me. Slightly quicker than cm9.
Tcp!? Where you been hiding buddy?
We got you a cake for your birthday but it rusted. We made it out of old Android parts and waited to yell surprise but you never showed. Is you okay? Brb I gotta tweet that I found you on xda! Lol B) good to see you Partna...
Sent from my SPH-D710 using Tapatalk 2
Phenom II X6 2.7GHz, 4 GB RAM, dual 640GB Western Digital Caviar Black in RAID 0.
CM7 for LS670: 18 minutes, 38 seconds. Compile options: make -j12 bacon
Cannibal Open Touch recovery for LS670: 59 seconds. Compile options: make -j12 recoveryimage
HydroKernel for LS670/VM670: 1 minute, 13 seconds. Compile options: make -j12
CM10 for Nexus 7: 48 minutes. Compile options: make -j12 otapackage
Yes it is very important to not have any other programs open (I've even crashed my machine trying to do stuff while compiling with -j12), they will take up more RAM and more CPU time.
Thanks for the responses so far. I hope this can become a list that more people can use as a reference to tweaking their machine for building purposes. I haven't seen any sort of list around and when I do read about the amount of time it takes, I usually see an answer like "it takes however long it takes" which leads to no progress. And at the very least I believe it's cool to see what other's results are.
Sent from my Super Galaxy'd SPH-D710
- Acer 5315
- Intel Celeron M 1,86 Ghz processor
- 1GB Ram
- 80GB HDD
on Ubuntu 10.04 it takes half an hour to compile a kernel with make command without any flag.
I will compile CM7 or ICS when i have free time just for fun to see the amount of time it takes, i guess it will take 22-24 hours
I am planning to change my laptop, this thread will be a good reference for me.
Core i3 2120 3.3ghz
Gigabyte Z68 mobo
8gb 1600 ram
Ubuntu 12 installed on a 100gb partition with 8gb swap on a Seagate Green (5900rpm) 1Tb DRIVE takes about 90 minutes to build CM9 for my Sensation.
I ordered a 120Gb OCZ Agility 3 SSD from tiger for $85 hopefully that will cut the time down significantly.
Sent from my Sensation using xda premium
AMD 3GHZ FX8120 Bulldozer Black Edition ;
16GB (1600) DDR3 ;
7200rpm 1TB HDD ;
Not Sure about the Motherboard without checking.
Linux Mint 13 ( 64 Bit )
EDIT: New build times.
aosp android-4.1.1_r4 ; removed previous out directory
full_panda-eng ; make -j12 49m6.429s
reboot
full_stingray-eng ; make -j16 32m47.270s
It came in around 38 minutes on a intial build of ICS time using make -j16.
Lately It's a little longer and I've been unable to get some fresh times because I don't have great cooling and it kept overheating and resetting because of hot whether.
It can be clocked to 5GHz with proper cooling and an SSD would bring the time down, I think, but given some reported times I am more than happy with that as it means I don't have to think twice about (re)building a rom.
In testing however I think this processor did fairly poor especially when up against similar Intel and looking at the couple of Intel times here I'd say they're the ones to go with.
Notes:
I always restart before building, I found it vital to restart after a repo sync as there seems to be a memoy leak in either repo or python, I don't know whether that has been fixed yet.
Incidentally I did Start a build on an Ubuntu VM which had 3 CPU Cores assigned and 4GB Ram, It was still going after 2 Days!
trevd said:
AMD 3GHZ FX8120 Bulldozer Black Edition ;
16GB (1600) DDR3 ;
7200rpm 1TB HDD ;
Not Sure about the Motherboard without checking.
Linux Mint 13 ( 64 Bit )
Incidentally I did Start a build on an Ubuntu VM which had 3 CPU Cores assigned and 4GB Ram, It was still going after 2 Days!
Click to expand...
Click to collapse
that doesnt seem right! lol.. really? not 2 whole days?
justlovejoy said:
that doesnt seem right! lol.. really? not 2 whole days?
Click to expand...
Click to collapse
Yep, You read it right lol. I went out for the weekend and when I came back it was still going I forget to add it was a dynamically sizing virtual disk which probably will account for it.
trevd said:
Yep, You read it right lol. I went out for the weekend and when I came back it was still going I forget to add it was a dynamically sizing virtual disk which probably will account for it.
Click to expand...
Click to collapse
That was with virtual machine right? Have u tried using ccache on an install of ubuntu yet?
Sent from my Super Galaxy'd SPH-D710
basketthis said:
That was with virtual machine right? Have u tried using ccache on an install of ubuntu yet?
Sent from my Super Galaxy'd SPH-D710
Click to expand...
Click to collapse
Yeah, like I put the Ubuntu VM ( Virtual Machine ). That's the day I learned to build on proper hardware, I tried the VM because I was on a later Ubuntu at the time and had run into a couple of issues so I wanted to follow google's aosp instructions to the letter and rule any versioning issues out..... schrooting is a much eaiser way of using a previous disto versions binaries, this is a great article on how build android using schroot. Good If you've ever get an urge for a cupcake or a donut one day
I do use ccache, but thanks for asking. Set in the bash profile so I never forget . Not looked into whether it should be cleared down at any point, I am on a 500GB partition though so I've not hit any limits yet.
trevd said:
Yeah, like I put the Ubuntu VM ( Virtual Machine ). That's the day I learned to build on proper hardware, I tried the VM because I was on a later Ubuntu at the time and had run into a couple of issues so I wanted to follow google's aosp instructions to the letter and rule any versioning issues out..... schrooting is a much eaiser way of using a previous disto versions binaries, this is a great article on how build android using schroot. Good If you've ever get an urge for a cupcake or a donut one day
I do use ccache, but thanks for asking. Set in the bash profile so I never forget . Not looked into whether it should be cleared down at any point, I am on a 500GB partition though so I've not hit any limits yet.
Click to expand...
Click to collapse
Setting up a box with the same processor. I expected to see better than 30 min builds for ICS. I will see what I come up with.
I am guessing that you were on windows and that's why you chose to go with virtual machine?
I have also read that different file systems read i/o faster/slower than others. Reference
Sent from my Super Galaxy'd SPH-D710
basketthis said:
Setting up a box with the same processor. I expected to see better than 30 min builds for ICS. I will see what I come up with.
I am guessing that you were on windows and that's why you chose to go with virtual machine?
I have also read that different file systems read i/o faster/slower than others. Reference
Sent from my Super Galaxy'd SPH-D710
Click to expand...
Click to collapse
Maybe on JellyBean, On ICS i'm not so sure about, From my very casual observations JB seems to be use a lot less ram in it build process, ICS always just touched swap from a start of about 15GB .
Like I mentioned earlier, from the reviews I read the processor is out perfomed by similar intels and a bit a flop apparently. ( I reads these reviews long after I had bought the processor ). Although I'm happy enough with it. Also I've only got a generic kernel installed so there's probably some AMD optimization to be had there if I really wanted to get into it.
I wasn't on windows at the time. I was just young, foolish It was when I was just getting started with building the sources and really didn't know any better....I still am foolish, just not as young.
Right, I'll be back in ( just over ) 30 mins :laugh: I've got a full_grouper-eng to compile.
Thanks for the link, Phoronix are a really useful resource, It's one I stumble upon now and again but always forget the name of it when I want to remember.
Using virtual box on my laptop at the time I was solo boot on windows, longest cm9 ever took was about 3 hours with dynamically resizing and was using two cores with less than 2 GB ram. Still, many things differ, I shut the whole thing down so only virtual box was running. I noticed lag when I would go web browsing so figured, why waste ram and disk space.
Sent from my SPH-D710 using Tapatalk 2
trevd said:
Maybe on JellyBean, On ICS i'm not so sure about, From my very casual observations JB seems to be use a lot less ram in it build process, ICS always just touched swap from a start of about 15GB .
Like I mentioned earlier, from the reviews I read the processor is out perfomed by similar intels and a bit a flop apparently. ( I reads these reviews long after I had bought the processor ). Although I'm happy enough with it. Also I've only got a generic kernel installed so there's probably some AMD optimization to be had there if I really wanted to get into it.
I wasn't on windows at the time. I was just young, foolish It was when I was just getting started with building the sources and really didn't know any better....I still am foolish, just not as young.
Right, I'll be back in ( just over ) 30 mins :laugh: I've got a full_grouper-eng to compile.
Thanks for the link, Phoronix are a really useful resource, It's one I stumble upon now and again but always forget the name of it when I want to remember.
Click to expand...
Click to collapse
Build a kernel
There are fx flags and optimizations....
Edit: If on ubuntu/Linux, you may want to check that your os is recognizing more than 3gb of ram also. I've been reading that anything newer than ubuntu 10.10 or Linux kernel 2.3.something are having issues with recognizing more than approx 3gb of ram. Also, there are issues with 10.04 and optimizations of ssd drives.
Also, I think it was 10.04 that is recognized as the better ubuntu version for building android. It is possible to use a newer (3.0+) kernel and back port it to the older ubuntu. This seems to give the best results...
Putting this info here for reference and to have it in a central location.
Lol, I've read many reviews. I am trying my hardest to keep any opinions out of here and keep it geared toward facts. It appears that Linux is better at multi-threading and we should expect to see gains when building a custom kernel (non-generic) and other things to come in the future. Whereas windows will need much more tweaking. Although I don't know why you would use windows to build android anyway....
Sent from my Super Galaxy'd SPH-D710
Takes about 20m on my pc, i7-2600K, 12GB, 7.2K HDD
real 20m14.526s
user 74m51.913s
sys 4m53.774s
^full-eng from clobber, same for other targets.
cdesai said:
Takes about 20m on my pc, i7-2600K, 12GB, 7.2K HDD
real 20m14.526s
user 74m51.913s
sys 4m53.774s
^full-eng from clobber, same for other targets.
Click to expand...
Click to collapse
I really must be missing a trick here and clearly haven't spent enough time on my considering the finer details of my hardware / kernel configuration.
basketthis said:
Build a kernel
There are fx flags and optimizations....
.....
Edit: If on ubuntu/Linux, you may want to check that your os is recognizing more than 3gb of ram also. I've been reading that anything newer than ubuntu 10.10 or Linux kernel 2.3.something are having issues with recognizing more than approx 3gb of ram
...
Lol, I've read many reviews. I am trying my hardest to keep any opinions out of here and keep it geared toward facts. It appears that Linux is better at multi-threading and we should expect to see gains when building a custom kernel (non-generic)
Sent from my Super Galaxy'd SPH-D710
Click to expand...
Click to collapse
Current Config is Linux Mint 13 x64 which is based off Ubuntu 12.04 with 3.2.0.26 kernel the Ram is Present and correct, However I have come across the 3GB Ram Limit previously so I am familiar with it. I think I must have been I had an 11.04 32bit on my machine.
PAE Extensions is the feature which needs enabling to get your full quota of ram on 32bit. Here's is an Ubuntu Help Page which gives a good explaination if any one is interested
I think there is some research followed by a rebuild on my horizon Thanks for the suggestions and the thread It's proving educational. I'll let you know how I get on, at the very least post some new build times
EDIT / UPDATE
I did some research and made some tentative first steps with my Kernel Configuration.
I decided to get on the mainline and build a 3.6-rc1. I removed a number of options I know to be redundant In my case, e.g Laptop Support, Intel Support etc
My research did throw up this Gentoo Wiki With Some useful "copy/pasta" compiler optimization, they also have a more in depth guide here.
After building this new kernel and clobbering my aosp tree I did
full_grouper-eng for JRO03L and a
make -j10 which resulted in
real 49m32.493s
user 312m45.481s
sys 17m55.599s
While this is still high, it's a step in the right direction, The times are around the same length I was getting for a full_panda with -j12 previously. I'll do a direct comparison also, Kinda Makes sense
I got quiet a lot of room for Improvement and many options, Only Clock at 2.8Ghz at the Moment.
AMD Provide an FX Bulldozer Specific GCC Toolchain which Is going to be employed when the I Rebuild the Kernel again
I Plan to tweak a bit, test a bit and see If I can get the performance some where close and hopefully learn some tricks along the way If all else fails I'll Surmerge the lot in a fishtank full of cooking oil and clock it to 5GHz
UPDATE 2
Following on from the Build Above -
Full_panda-userdebug make -j16
real 32m16.986s
user 196m34.933s
sys 13m9.521s
full-eng
aosp jellybean
fx-8120, 8gb ram, 8gb swap
make -j16
real: 34m2.641s
EDIT: about to test some tweaks! will update.
Machine: Dell Inspiron 1565
Processor: Intel Core 2 Duo 2.0GHz
Hard Drive: 320GB HDD
RAM: 4GB
OS: Ubuntu 11.04
Current Build Time: 2 1/2 +
Build: CM10 PA Source
Just added ccache. We will see on the next build if I shave some time.
I have Samsung drivers
atlas 2.2
odin 1.3
gbbootloaders
cmw4 fixed for cm7
CI500_VZW_EH03_GB_CM
and mutliple releases of CM10.1
I followed instructions exactly how [GUIDE] Installing a Rom/CWM recovery/Root or going back to Stock say to do.
I always end up with a bootloop after flashing. The instructions are flawed. Or, one or more files are corrupted.
fewert said:
I have Samsung drivers
atlas 2.2
odin 1.3
gbbootloaders
cmw4 fixed for cm7
CI500_VZW_EH03_GB_CM
and mutliple releases of CM10.1
I followed instructions exactly how [GUIDE] Installing a Rom/CWM recovery/Root or going back to Stock say to do.
I always end up with a bootloop after flashing. The instructions are flawed. Or, one or more files are corrupted.
Click to expand...
Click to collapse
Did you look at my post which further explains the process.
http://forum.xda-developers.com/showthread.php?p=53235945
Have you installed cm10.1 multiple times?
Some times it doesn't always set thing up in one flash
hhp_211 said:
Did you look at my post which further explains the process.
http://forum.xda-developers.com/showthread.php?p=53235945
Have you installed cm10.1 multiple times?
Some times it doesn't always set thing up in one flash
Click to expand...
Click to collapse
Yeah I read a post saying to do what you just described with success.
However, this phone is really poor. I have tried GB, ICS, JB and all of them I get similar performance just different features.
The phone can't handle two apps at once regardless of the rom.
I was traveling to a different city to get something on Craigs. It constantly would shutdown my Maps and Navigation when I wanted to read a Kik message.
If I have Kik open and want to read a txt msg, it takes like 10 seconds after clicking the txt msg icon to show the txt.
Is there an app or method that everyone uses on this phone that I don't know about to get this phone to run speedy? Or, is it just so outdated it can't run modern versions of apps?
I just want navigation, txt, kik, and a light browser like dolphin.
Can a Fascinate handle all that and be snappy and quick??
In the mean time, I am switching over to my S3, though I don't like how it's so big I can't reach all the screen with one hand.
fewert said:
Yeah I read a post saying to do what you just described with success.
However, this phone is really poor. I have tried GB, ICS, JB and all of them I get similar performance just different features.
The phone can't handle two apps at once regardless of the rom.
I was traveling to a different city to get something on Craigs. It constantly would shutdown my Maps and Navigation when I wanted to read a Kik message.
If I have Kik open and want to read a txt msg, it takes like 10 seconds after clicking the txt msg icon to show the txt.
Is there an app or method that everyone uses on this phone that I don't know about to get this phone to run speedy? Or, is it just so outdated it can't run modern versions of apps?
I just want navigation, txt, kik, and a light browser like dolphin.
Can a Fascinate handle all that and be snappy and quick??
In the mean time, I am switching over to my S3, though I don't like how it's so big I can't reach all the screen with one hand.
Click to expand...
Click to collapse
i think you should understand that this phone has a single-core CPU. running at 1GHz. this phone is almost 4 years old. it's amazing this thing can even run things like Kitkat at all, let alone with the relative finesse the most recent unjust build provides.
it took me a while to realize that apps these days are not optimized for single-core CPUs, it took upgrading to a gs4 to realize that. the fascinate is an admittedly, well, slow phone. or its not meant for multitasking, definitely.
the s3 runs circles around this phone. almost anything does. i've never really found anything that allows for the multitasking and insane speed that i get out of my s4, the closest i've ever gotten was cm7, but that even in its stable release had tons of SOD problems (sleep of death, phone locks and never comes back on).
part of the issue is that the fascinate has 512MB of RAM. back in 2010, it was adequate. not even good, just.. alright. these days the norm is 2GB. a phone with 1GB of RAM is considered outdated. despite google's efforts to optimize kitkat for 512MB devices, this phone's GPU shares RAM with the system, and depending on the configuration, usually 100+ MB is reserved for the GPU, leaving typically about 360-384MB of RAM. You can get more (the kitkat ROM i've mentioned allows 416MB of RAM to the system) but things will start breaking, particularly HD video recording and torch, among other things
skepticmisfit said:
i think you should understand that this phone has a single-core CPU. running at 1GHz. this phone is almost 4 years old. it's amazing this thing can even run things like Kitkat at all, let alone with the relative finesse the most recent unjust build provides.
it took me a while to realize that apps these days are not optimized for single-core CPUs, it took upgrading to a gs4 to realize that. the fascinate is an admittedly, well, slow phone. or its not meant for multitasking, definitely.
the s3 runs circles around this phone. almost anything does. i've never really found anything that allows for the multitasking and insane speed that i get out of my s4, the closest i've ever gotten was cm7, but that even in its stable release had tons of SOD problems (sleep of death, phone locks and never comes back on).
part of the issue is that the fascinate has 512MB of RAM. back in 2010, it was adequate. not even good, just.. alright. these days the norm is 2GB. a phone with 1GB of RAM is considered outdated. despite google's efforts to optimize kitkat for 512MB devices, this phone's GPU shares RAM with the system, and depending on the configuration, usually 100+ MB is reserved for the GPU, leaving typically about 360-384MB of RAM. You can get more (the kitkat ROM i've mentioned allows 416MB of RAM to the system) but things will start breaking, particularly HD video recording and torch, among other things
Click to expand...
Click to collapse
Lol my phone e400 is super multitasker
Sent from my LG-E400 using XDA Free mobile app
fewert said:
Yeah I read a post saying to do what you just described with success.
However, this phone is really poor. I have tried GB, ICS, JB and all of them I get similar performance just different features.
The phone can't handle two apps at once regardless of the rom.
I was traveling to a different city to get something on Craigs. It constantly would shutdown my Maps and Navigation when I wanted to read a Kik message.
If I have Kik open and want to read a txt msg, it takes like 10 seconds after clicking the txt msg icon to show the txt.
Is there an app or method that everyone uses on this phone that I don't know about to get this phone to run speedy? Or, is it just so outdated it can't run modern versions of apps?
I just want navigation, txt, kik, and a light browser like dolphin.
Can a Fascinate handle all that and be snappy and quick??
In the mean time, I am switching over to my S3, though I don't like how it's so big I can't reach all the screen with one hand.
Click to expand...
Click to collapse
skepticmisfit said:
i think you should understand that this phone has a single-core CPU. running at 1GHz. this phone is almost 4 years old. it's amazing this thing can even run things like Kitkat at all, let alone with the relative finesse the most recent unjust build provides.
it took me a while to realize that apps these days are not optimized for single-core CPUs, it took upgrading to a gs4 to realize that. the fascinate is an admittedly, well, slow phone. or its not meant for multitasking, definitely.
the s3 runs circles around this phone. almost anything does. i've never really found anything that allows for the multitasking and insane speed that i get out of my s4, the closest i've ever gotten was cm7, but that even in its stable release had tons of SOD problems (sleep of death, phone locks and never comes back on).
part of the issue is that the fascinate has 512MB of RAM. back in 2010, it was adequate. not even good, just.. alright. these days the norm is 2GB. a phone with 1GB of RAM is considered outdated. despite google's efforts to optimize kitkat for 512MB devices, this phone's GPU shares RAM with the system, and depending on the configuration, usually 100+ MB is reserved for the GPU, leaving typically about 360-384MB of RAM. You can get more (the kitkat ROM i've mentioned allows 416MB of RAM to the system) but things will start breaking, particularly HD video recording and torch, among other things
Click to expand...
Click to collapse
I have not used the kik so I can't really say about it's performance,,, I have seen on the 4.4 kitkat rom from Unjust when I have used google maps navigation it was a huge battery sucker, no matter if I only put it on device [gps] only. I could barely even use it and on a charge it was still draining it faster than it could take it.
i did not have this on jellybean roms
I have not had the the problems you describe '10 seconds to open an app'.
Hangouts used to be slow opening initially but their latest update has made it much faster
I don't think it's multitasking is bad for what it is as a phone given it's specs,,, but everyone use a phone differently,,,
so I mostly agree with the overall jest of what skept is saying,,, it is ultimately limited by the 512MB ram available to use.
for GB and JB roms you can also look at the V6 Supercharger thread, it does help with multi-tasking, it can be a bit hard to understand how to implement it but once you figure that out it goes decent, boot up and time till initial use are much longer than normal, but you just have to plan your reboots for when plenty of time allows
i think jellybean roms are very good performers and given the face that you can use a different kernel that allows for overclocking up 1400 Mhz if desired,,, it's a give and take though,,,, over 1200Mhz and battery life goes south very quickly. [luckily the battery doesn't take long to charge, usually 1 hour,,, and even 5 minutes here or 10 minutes there will really help it last through the day]
Most of the earlier jellybean [4.1.x] versions seemed to give better battery life from what I remember than the newer [4.2.x] ones
and there are a lot of different ones to choose from to suite your style or needs from basic cm to full customization.
most of them were stable enough to be daily drivers,,, the big thing is you will just have to read up on a particular one or just break down and try some to see if they fit what you want.
With all that said though the fascinate will never perform like an S3, S4, Nexus, Nexus 4, Moto G, Moto X
I would consider checking out the Motorola Moto G, it's physical dimensions are nearly she same as the fassy but a hugely better phone, screen size, etc and depending on your phone carrier needs it can be had for as little as $65 bucks...
Well lg optimus l3 is very powerful and performant in fact of multitasking if you're a dev or not a complete noob.My phone can go until 1.2 ghz without probs and its factory clock speed was 800 mhz.Most apps aren't optimized for multi-cores and l3 is single core.384 mb of ram are enough on stock and 301 mb aren't enough on cm.But my kernels got swap.
Battery is very good:10days in stand by,2 days in normal use.
Antutu sucks but i don't believe in it.
So its up to the devs,we're good devs and there are more than 100000 l3s in the world.Now we're getting dualboot.Its all about devs,its all about devs.
Sent from my LG-E400 using XDA Free mobile app
Hi, I'm looking for a very low resource way of measuring power draw over a time interval. I'm looking to measure the power draw as various pictures and videos are displayed on the screen to get an idea of how much power the various components of the phone draw. I've done some looking and I've found this: http://developer.android.com/reference/android/os/BatteryManager.html. Particularly, I noticed Charge_Counter, Current_Average, and Energy_Counter. My issue is that while I have a bit of a programming background (more like a hobby), I have no idea where to start with this. I have some background in Python, Labview, linux scripting, and very little C and .NET, so I understand some of the basic concepts of programming, but anything beyond that is something I would have to pick up. I have virtually no experience in Android programming (other than a few Cyanogenmod compiles from source - as anyone who has been around long enough has ).
I wouldn't need a gui for this, so something like a script would work great. It can (maybe should) be able to be executed via ADB, and needs to be universal - working across modern devices. The app/script I'm envisioning would perhaps poll the battery for a power level, wait a specified time - 2 min, 5 min, 10 min, 1 hour, something like that - then poll it a second time, get the delta, and divide by time to get an average power. Other than those two polls, I would want the app/script to have no interactions with the processor. The greater the accuracy, the better, and if no root is possible, that would be my choice. I would prefer to keep the phones as stock as possible.
My questions are:
- Is something absolutely universal (or mostly universal among newer devices - say 1 yr old or less) possible (no root)?
- Since it needs to be universal, would Java be a good choice of programming language? Or perhaps this can be accessed via the command line (script)?
- How accurate would a method like this be? How do the phones know the instantaneous current, power level, etc? Is it basically a shunt resistor, measuring the V across?
- How much time would it take (generally) for a noob with no Android experience to get a working demo? Days, weeks, months?
Thank you for your time.
I would also mention, this doesn't have to be "polished" for an audience...just simply looking for a down and dirty method that works - mostly for myself.
I have noticed over the last couple years that the resource usage of Chrome OS has continued to balloon beyond any common sense. I can't be the only one can I?
I have two fairly high performance Chromebooks. One, a Google Slate with the m3 and 8G of RAM and a Dell 7410 i5 with 16G RAM. When I first got the Slate, I could run Linux no problem with plenty of RAM to spare. It would startup with less than 3G in use. Now, it has become almost pointless. The Slate boots up to the Chrome OS desktop with less than 3G of free RAM so running Linux or anything that requires significant RAM just causes the OS to start allocating compressed ZRAM.
The Dell 7410 still performs reasonably well but only because it has 16G of physical RAM. Still, it now boots up with almost 8G of RAM in use before I launch a single thing!
Google seems to want power users to take ChromeOS seriously so they've added all kinds of great features like ARCVM and the ability to run multiple Linux VM's. Yet, they still seem to be developing the OS as though it's 10 years ago. Back then they could allocate all the system RAM as they chose because the Chrome browser was the only app the system could run.
Neither MacOS, Windows or various Linux distros go so far as to consume almost 50% of the memory on boot while operating on hardware with 16G or more RAM. What is Google thinking!? A good OS should prioritize resources for user applications and minimize resource consumption by the core OS.
I'm thinking about reflashing my Slate to make it useful again as there is no sign that Google is going to make ChromeOS lean again, anytime soon.
Arpman96 said:
I have noticed over the last couple years that the resource usage of Chrome OS has continued to balloon beyond any common sense. I can't be the only one can I?
I have two fairly high performance Chromebooks. One, a Google Slate with the m3 and 8G of RAM and a Dell 7410 i5 with 16G RAM. When I first got the Slate, I could run Linux no problem with plenty of RAM to spare. It would startup with less than 3G in use. Now, it has become almost pointless. The Slate boots up to the Chrome OS desktop with less than 3G of free RAM so running Linux or anything that requires significant RAM just causes the OS to start allocating compressed ZRAM.
The Dell 7410 still performs reasonably well but only because it has 16G of physical RAM. Still, it now boots up with almost 8G of RAM in use before I launch a single thing!
Google seems to want power users to take ChromeOS seriously so they've added all kinds of great features like ARCVM and the ability to run multiple Linux VM's. Yet, they still seem to be developing the OS as though it's 10 years ago. Back then they could allocate all the system RAM as they chose because the Chrome browser was the only app the system could run.
Neither MacOS, Windows or various Linux distros go so far as to consume almost 50% of the memory on boot while operating on hardware with 16G or more RAM. What is Google thinking!? A good OS should prioritize resources for user applications and minimize resource consumption by the core OS.
I'm thinking about reflashing my Slate to make it useful again as there is no sign that Google is going to make ChromeOS lean again, anytime soon.
Click to expand...
Click to collapse
I say "Ditch Google!" That's ridiculous. I've heard that maybe you can install Linux instead.
You are correct. It's always an option to go into "Developer Mode" on Chromebooks and flash with a new OS image. The new image can be a Linux distro provided it has the right drivers. You still have to go into Developer Mode on every reboot to get past the BIOS but it works. Still, there's just no good reason for this if Google approached OS resource management like any other good OS.
At this point the 8G Slate boots with 2.5G free! That is appalling. Do these Google kiddies have a clue? One has to wonder if there is anybody at Google overseeing the architecture or if there are just 100's of little silos uninterested in how their combined drains on system resources may effect the actual usefulness of the OS.
Arpman96 said:
You are correct. It's always an option to go into "Developer Mode" on Chromebooks and flash with a new OS image. The new image can be a Linux distro provided it has the right drivers. You still have to go into Developer Mode on every reboot to get past the BIOS but it works. Still, there's just no good reason for this if Google approached OS resource management like any other good OS.
At this point the 8G Slate boots with 2.5G free! That is appalling. Do these Google kiddies have a clue? One has to wonder if there is anybody at Google overseeing the architecture or if there are just 100's of little silos uninterested in how their combined drains on system resources may effect the actual usefulness of the OS.
Click to expand...
Click to collapse
Arpman96 said:
Still, there's just no good reason for this if Google approached OS resource management like any other good OS.
Click to expand...
Click to collapse
Well, I'm honestly not sure why you would expect Google, a huge corporation that makes money by harvesting people's data and advertising, to actually care about making a lean and usable OS. Instead it is chock-full of spy-ware.
Arpman96 said:
At this point the 8G Slate boots with 2.5G free!
Click to expand...
Click to collapse
Personally I will never buy a Google or Apple product. This just assures me that I'm not missing out on anything!