Hello I had read about the problem of stalling. In the OCLF thread, I read that this is due to the RFS used.
BTW anyone can verify if this is still the problem in Android 2.2 build.
Thanks.
Sent from my GT-I9000 using XDA App
dplate07 said:
Hello I had read about the problem of stalling. In the OCLF thread, I read that this is due to the RFS used.
BTW anyone can verify if this is still the problem in Android 2.2 build.
Thanks.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Still rfs in the leaked froyo builds; no one can verify what the official build will be like, because it hasn't been released yet.
Seems pretty unlikely that samsung would consider a change in fs for the i9000 at this stage in it's development. I think manufacturers like to stick to their own proprietary fs...
This is the 1st and the last time I purchase a Samsung Phone Android, no matter what we do, still crapy slow. I start to hate this phone.... Android is cool but I9000 phone have the best hardware but the software suck....
halabibk said:
I start to hate this phone.... Android is cool but I9000 phone have the best hardware but the software suck....
Click to expand...
Click to collapse
No device is perfect. Most problems are fixable, I think. If Samsung doesn't do it, I'm sure the talented developers in this forum will do something - that's the beauty of Android..
the voodoo kernel puts the phone to rights. with that fix, its the fastest thing on the market.
it's just a shame only a small minority of users will see the benefit and the phone will ultimately fail because of this.
are you reading this samsung?
chrissyg123 said:
the voodoo kernel puts the phone to rights. with that fix, its the fastest thing on the market.
it's just a shame only a small minority of users will see the benefit and the phone will ultimately fail because of this.
are you reading this samsung?
Click to expand...
Click to collapse
Hi, may I know what is the voodoo kernel? Can you please provide us with a link to the forum. Cheers.
chrissyg123 said:
the voodoo kernel puts the phone to rights. with that fix, its the fastest thing on the market.
it's just a shame only a small minority of users will see the benefit and the phone will ultimately fail because of this.
are you reading this samsung?
Click to expand...
Click to collapse
I'm sorry to say that even the voodoo kernel starts to lag after a while. I don't know whats wrong with this phone but I'm never ever buying Samsung again, no matter how nice the specs are.
cavinsoo said:
Hi, may I know what is the voodoo kernel? Can you please provide us with a link to the forum. Cheers.
Click to expand...
Click to collapse
public beta 2 should come online within short time
f samsung...this is the first time in my years and years of using a mobile phone that i have to learn about filesystems and mobile phones.....lol
Disagree
kmrdeva said:
No device is perfect. Most problems are fixable, I think. If Samsung doesn't do it, I'm sure the talented developers in this forum will do something - that's the beauty of Android..
Click to expand...
Click to collapse
True that no device is perfect, but for the money we pay to purchase such a device, we expect a product that works out-of-the-box, which is not the case for the Galaxy S.
Compared to the hardware Samsung put into it, its shockingly laggy and other phones in the market with half the hardware specs dont show such lag due to the tweaked software they have
A mobile phone is not just a piece of hardware, its the hardware with its software that enables the optimum use of the hardware and also the accompanying PC software where Samsung has yet failed through the horribel "Kies"
I am a big fan of android, but Samsung has tarnished android through this ****ty product
This will be clearly seen once a pure android 2.2 OS (with no samsung software on top) is available for the SGS with the proper file system and memory manager
There are 2 problems with the phone.
1. File System
2. Memory
File system can be fix by using lag fix. After you implement lag fix, you feel phone is snappy and fast and you start running and install tons of apps.
This started the 2nd problem, even though is 512MB ram, most you get is 200Meg usable, however with some background service it reduces to 130 on average. After few hours of apps used or longer time the available memory can drop down to 30Meg. This is when you feel the 2nd lag. Even with 80Meg ram available you will still feel lag, and swype start behaving funny.
This can only be solve or temp fix (some people say you shouldn't) if you use softwares like ATK, SystemPanel Apps. (Just KILL THEM ALL) when you feel your phone start to slow down and your phone will than be alive!!!
The real fix for the memory issue.. unfortunately.. i believe we need a phone with minimum 6 to 700MB free RAM. Than you should feel the phone responsive all the time until all the apps start clogging up the usable RAM.
I understand where you're coming from, regarding this. However, being somewhat of a tech freak, I am quite happy that so many tweaks have been developed by the experts here in this forum - my Galaxy S works well enough for me, rooted and sped up with the one-click-lagfix app.
My experience so far with Android on the Galaxy S (shortcomings and all) has generally been way better than my previous experiences with S60v5 on the Nokia 5800 and N97.
kmrdeva said:
I understand where you're coming from, regarding this. However, being somewhat of a tech freak, I am quite happy that so many tweaks have been developed by the experts here in this forum - my Galaxy S works well enough for me, rooted and sped up with the one-click-lagfix app.
My experience so far with Android on the Galaxy S (shortcomings and all) has generally been way better than my previous experiences with S60v5 on the Nokia 5800 and N97.
Click to expand...
Click to collapse
I am so so so so so so AGREE WITH YOU!!!!
Maybe that's why we appreciate the problems that comes with Android and SGS.
xtrememorph said:
There are 2 problems with the phone.
1. File System
2. Memory
File system can be fix by using lag fix. After you implement lag fix, you feel phone is snappy and fast and you start running and install tons of apps.
This started the 2nd problem, even though is 512MB ram, most you get is 200Meg usable, however with some background service it reduces to 130 on average. After few hours of apps used or longer time the available memory can drop down to 30Meg. This is when you feel the 2nd lag. Even with 80Meg ram available you will still feel lag, and swype start behaving funny.
This can only be solve or temp fix (some people say you shouldn't) if you use softwares like ATK, SystemPanel Apps. (Just KILL THEM ALL) when you feel your phone start to slow down and your phone will than be alive!!!
The real fix for the memory issue.. unfortunately.. i believe we need a phone with minimum 6 to 700MB free RAM. Than you should feel the phone responsive all the time until all the apps start clogging up the usable RAM.
Click to expand...
Click to collapse
I haven't had these problems for a long time, actually using a taskkiller makes it slower for me. Since JM* it's not possible anymore to have only 30Megs free as the least low memory killer level starts at around 40 Megs which turns into having 50ish free all the time. The only time i get lags is when installing apps but otherwise never with loads of apps installed. I use the oneclick lagfix btw.
The filesystem choice is not wise from samsung, the hardware and software interaction are because samsung is using Hummingbird processor and that google developed android to improve it on snapdragon because the nexus one is running it and most of the andro phones. So samsung has to "fix" android for their processor.
For the memory "issues" like I said on another topic
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Linux however isn’t generally affected by this. While I admit that I don’t know the architecture and reason for this… linux will run the same regardless of if you have 20mb free memory or 200mb.
Click to expand...
Click to collapse
Related
Hello!
I-m trying to apply several live wallpapers. Some crash, its acceptable.
Others, plain buggy. Example: Galatic Core.
I select it in the Livewallpapers selector, it does not error, and shows a black screen. i press settings, get the message "buy the app", and then it shows!
If i then select it, i get a black screen... and then the original wallpaper again.
Anyone got more luck than i ?
They were never meant to run on our phones so they will be iffy at best for performance
Also if your using cm6 that's a known issue across the board with them
Sent from my HERO200 using XDA App
thoughtlesskyle said:
They were never meant to run on our phones so they will be iffy at best for performance
Also if your using cm6 that's a known issue across the board with them
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Could you guys please stop doing that ?
"" XPTO was not meant to run on our phone ""
What is it there... that our phones have... or have not... that make a given app not run ? Sure... we can agree on "it wasn't designed for 320x240. Ok, i agree too.
But either than that ?? Yeah, our CPU is the slower MSM on the field, at least compared to Diamonds/Raphaels and upwards... but hey!! We have 1/4 of the pixels to take care of. That sould give us some room...
Now, don't get me wrong. It was not designed to run Android. But that doesn't mean it was not meant to. Take for example a simple little phone, sold here on Portugal as Optimus Boston. It has a MSM cpu... it came with 1.6 running at 600mhz... but the latest update to Eclair 2.1... underclocked it to 480. My kaiser usually runs at 550. (official rom, its possible to have custom roms running at the original 600.) and it still is a great phone... look at the simple specs :
http://www.gsmarena.com/gigabyte_gsmart_g1305_boston-3201.php
Now, someone explain... why can't our Kaiser/Vogue/Polaris run Android like that leatle freak underclocked to 480 runs. Please.
The fact that we have absolutely no RAM doesn't play into it ever since sheer clock speed always determines speed, to be honest I haven't even seen them run well on my hero and I have it OC'd to 691
But hey if you want to argue about it there are links to the source around go in and fix the problem, most of the devs for this project have more important things to focus on at the moment
Sent from my HERO200 using XDA App
thoughtlesskyle said:
The fact that we have absolutely no RAM doesn't play into it ever since sheer clock speed always determines speed, to be honest I haven't even seen them run well on my hero and I have it OC'd to 691
But hey if you want to argue about it there are links to the source around go in and fix the problem, most of the devs for this project have more important things to focus on at the moment
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Do not feel ofended. It was not my intention.
My point is that if we had accepted the slowness of our devices, we would never had attempted to port Android.
As for the RAM, agree.. it is a bottleneck...
Now, has for speed... i've seen them run well... on other devices of course.
I did many tests on my Kais130 Fresh Froyo, about livewallpapers
I agree with Daedric on the ability of our device.
I managed to run the "Grass" Wallpaper properly. Others, like Mario, Galactic Core, ... Sometimes with bugs and/or too many resources used.
It seems to me that LiveWallpapers work less well in the latest Froyo
Well were not the slowest android phone anymore. But that doesnt mean much, we still have a lot of instability. The ram limitation can be overcome with comp cache (virtual memory) but that brings only more instability and adds overhead that we don't need. Also the performance just isnt there yet. Our phones beat only one phone and thats because that phone doesnt have froyo on it. Otherwise it would beat ours out. Also that was with my kaiser overclocked to 572 mhz with a gpu overclock as well. Any other phone msm 7200 phone at those speeds kick our kaisers ass. I think the resource intense ones are just not meant to work well at all for us. My background works at least lol, I use a background that shows the core of a 486 cpu.
aceoyame said:
Well were not the slowest android phone anymore. But that doesnt mean much, we still have a lot of instability. The ram limitation can be overcome with comp cache (virtual memory) but that brings only more instability and adds overhead that we don't need. Also the performance just isnt there yet. Our phones beat only one phone and thats because that phone doesnt have froyo on it. Otherwise it would beat ours out. Also that was with my kaiser overclocked to 572 mhz with a gpu overclock as well. Any other phone msm 7200 phone at those speeds kick our kaisers ass. I think the resource intense ones are just not meant to work well at all for us. My background works at least lol, I use a background that shows the core of a 486 cpu.
Click to expand...
Click to collapse
Should we assume... that at the same speed, diferent MSM devices offer diferent performance ? Or, are we simply doing still things wrong, i don't know, perhaps a poor schedule, buggy drivers which introduce lag, perhaps the graphic one.
We must remember, they kick our kaiser hard, but they have much more pixels, how can that be ?
After I updated my phone to 4.1 i'm only showing 1.56GB of ram in the task manager app. Has anyone else had this problem?
I did notice that I lost a large chunk of free ram... 4.0.4, I used to consistently have about 1 gig free, now I stay around 500-600 megs free
I've noticed this with any 4.1 rom with touchwiz and bloatware.
It's much better using a custom 4.1 TW rom (bacon!!) with some bloatware removed.
Sent from my SGH-I747M using xda app-developers app
I sent an email to Samsung just now. Let's see what they say.
Anyway, this is def. NOT natural. If you bring up a terminal console and type "free" you will see it state that your phone only has 1.5 gigs of ram.
I'm wondering of project butter is using 500 megs of ram to do the speedup we're seeing...
Response from Samsung 2012-12-6:
Dear ycavan,
Thank you for your inquiry. We understand that the RAM of your phone was reduced after the upgrade made on youe phone. We do apologize for the inconvenience that these issues might have caused you. Thank you for bringing to our attention the issue of your phone model missing. We will forward this information to the appropriate department.
The possible reason why RAM of your phone was reduced after the upgrade made on youe phone is because of the new application that is installed on the phone which is part of the enhancement.
Do you have more questions regarding your Samsung Mobile Phone? For 24 hour information and assistance, we offer our new FAQ/ARS System - Automated Response System at http://www.samsung.com/support.
It's like having your very own personal Samsung Technician at your fingertips.
We appreciate your continued interest in Samsung products.
Sincerely,
Mark
Technical Support
End Response 2012-12-6.
My take-away is that they did, in fact, use the extra 512megs for a new application that is part of the enhancement. My guess is butter.
Its most likely just the system using that RAM, like pretty much every android phone on the planet
Sent from my SGH-I747M using xda premium
Wow. Big difference. I'm seeing the same.
I never thought 2GB would get so low available so quick.
Who cares, really?
I'd rather have my 2Gb completely filled up as it's most likely just cached applications anyway.
If need be, this memory will be released anyway by Android's garbage collector.
On the other hand, history shows us that every new iteration of Android needs more RAM, so that's kinda expected.
My GS1 only has 512Mb which is more than enough if running Android 2.x (Eclair, Froyo & Gingerbread) but rapidly falls short RAM if running ICS.
HiKsFiles said:
Who cares, really?
I'd rather have my 2Gb completely filled up as it's most likely just cached applications anyway.
If need be, this memory will be released anyway by Android's garbage collector.
On the other hand, history shows us that every new iteration of Android needs more RAM, so that's kinda expected.
My GS1 only has 512Mb which is more than enough if running Android 2.x (Eclair, Froyo & Gingerbread) but rapidly falls short RAM if running ICS.
Click to expand...
Click to collapse
free memory is waisted memory for some. I disagree when it comes to devices using a battery. Processes use memory and battery life...
I hate to see apps running in background even when I didn't use them since the last reboot. Self running apps grabbing infos about me suck. If Google dont want to stop these behaviors then its time for a new OS.
My next phone ?: http://www.youtube.com/watch?v=oG3tLxEQEdg&feature=colike
Bagbug said:
free memory is waisted memory for some. I disagree when it comes to devices using a battery. Processes use memory and battery life...
I hate to see apps running in background even when I didn't use them since the last reboot. Self running apps grabbing infos about me suck. If Google dont want to stop these behaviors then its time for a new OS.
My next phone ?: http://www.youtube.com/watch?v=oG3tLxEQEdg&feature=colike
Click to expand...
Click to collapse
You got it wrong.
Cached apps in memory do not actually run.
They are just left there so that they can start more quickly the next time you use them.
Bagbug said:
free memory is waisted memory for some. I disagree when it comes to devices using a battery. Processes use memory and battery life...
I hate to see apps running in background even when I didn't use them since the last reboot. Self running apps grabbing infos about me suck. If Google dont want to stop these behaviors then its time for a new OS.
My next phone ?: http://www.youtube.com/watch?v=oG3tLxEQEdg&feature=colike
Click to expand...
Click to collapse
RAM has to refresh whether it is used or not. The RAM has no idea if a particular bit is used or not.
The last ICS update also lowered the RAM to 1.59GB. I believe it has to do with how much RAM is assigned to the GPU. It is normal.
HiKsFiles said:
Who cares, really?
I'd rather have my 2Gb completely filled up as it's most likely just cached applications anyway.
If need be, this memory will be released anyway by Android's garbage collector.
On the other hand, history shows us that every new iteration of Android needs more RAM, so that's kinda expected.
My GS1 only has 512Mb which is more than enough if running Android 2.x (Eclair, Froyo & Gingerbread) but rapidly falls short RAM if running ICS.
Click to expand...
Click to collapse
I only care because of my past experience: the more apps I load, the more memory gets used, and the slower it runs. I tend to use a log of apps. Memory was a struggle on the ole' Captivate.
I want this phone to perform good for a while.
ewingr said:
I only care because of my past experience: the more apps I load, the more memory gets used, and the slower it runs. I tend to use a log of apps. Memory was a struggle on the ole' Captivate.
I want this phone to perform good for a while.
Click to expand...
Click to collapse
well then just close off some apps, I've never had a problem memory on this phone at all yet
Sent from my SGH-I747M using xda premium
My ram dropped to 1.59 since before Jellybean
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------
Actually my first s3 when it released had 1.89 of ram but I sold it. This one I bought on black Friday only has 1.59
Sent from my SAMSUNG-SGH-I747 using xda premium
I'm curious what the International phones have since they only started with 1g
Sent from my SGH-I747M using xda app-developers app
If you dont want any back ground processes go to the developer options and limit the number of background processes
Sent from my SAMSUNG-SGH-I747 using xda premium
Currently running: CM 10.1, build 0319 stock kernel and cpu settings.
TL;DR - The Hercules and its 1GB RAM suddenly seem like it can't multi-task like it once could. However maybe its app developers just heinously demanding more resources so their apps can look amazingly fluid because they forcefully killed everything else in the back?
What's the deal?
I remember a time in yesteryear yonder, whence I would have 5-7 apps running in the back without breaking nary a sweat. SO WHAT THE HELL happened Android? That was back on Touchwiz and Gingerbread!
Today I can't have utorrent and chrome open simultaneously. TWO apps. For instance if I've utorrent downloading, ill switch to Chrome (recent apps switch; not open) and maybe answer a Whatsapp immediately after; utorrent will undoubtedly be killed and must be reactivated.
Now I understand that chrome and utorrent are naturally RAM heavy applications, but it helps further my point. Why are apps being killed so quickly today? Was it Touchwiz that was great at ram management? Was it gingerbread? Or have apps been slowly updating over the last two years and demanding more allocation of RAM from the get go so that everything else gets forcefully killed? I remember when the Hercules was announced and all the reviewers claimed 1GB was such a stupid amount of overkill RAM and we'll never see it taxed. Now that 2GB has become the standard with the introduction of the GS3, I theorize app devs are being more liberal in demanding resources from devices without giving too much consideration for older models. So apps are killed more frequently to make room to the foreground.
So why do you care?
-The stock stopwatch app will die if you run a few more apps afterwards. This is just derp. Really, try this yourself. Can you imagine your morning alarm was silently force killed because you were reading a website before bedtime?
-Some audio apps can be killed as well. ie Doggcatcher. Audio actually stops if certain conditions of apps are opened after Doggcatcher. Derp.
-Device slows to a complete crawl during the course of a day. I don't believe I've ever owned a device (clamshell Sammy, Blackberry or Android) that didn't exhibit facepalm-worthy memory leak issues. If Android was designed to have its RAM filled, why do slowdowns exist?
-Incoming phone calls suffer lag when re-acquiring attention. This seems bizarre because in About > System you can see the Hercules indicates it has 768MB RAM, indicating a quarter is reserved for system apps. Which means it shouldn't really have this problem.
-Application settings requesting 'Persistent Notifications' to ensure app foreground attention. Apps like Tasker, utorrent, Battery Guru request this to remain alive. Is this the solution now? And is this 100% immune if system requires the resources?
-Apps take longer to open. I can't quite pinpoint this. Just a feeling.
Alright man relax, the Galaxy S4 and HTC One come packing with 2GB
Upgrading to a new flagship doesn't seem to be the solution to stifle this issue. App developers are excellent at what they do and naturally want their product to look its best with the resources available to it. With 3D games exhibiting the capabilities of a Snapdragon 600 and Tegra 4, where's the incentive to tell either to slow down? This same logic can be directly applied to the smartphone spec war and the recurring battery life bottleneck story.
Excellent read here from Gizmodo:
http://gizmodo.com/5992917/battery-life-is-the-only-spec-that-matters
Click to expand...
Click to collapse
So what's your point?
I'm not sure I have one. I'm just observing whats happening. We are finally actually seeing applications that are pushing our hardware to its limits. While 1GB of onboard RAM used to be a drool inducing spec, 2GB is not really a huge leap considering the jump the Snapdragon S3 made to the S4, S4 Pro and now the 600 in magnitudes of processing power. 2GB would certainly be astronomical, if it took a trip back in time and only had to run 2011 apps. I guess my point is: I'm throwing a tantrum that the Hercules is showing its age, even if it's not its fault.
Forgive my rambling and lack of proof-reading. At work.
mettleh3d said:
Currently running: CM 10.1, build 0319 stock kernel and cpu settings.
TL;DR - The Hercules and its 1GB RAM suddenly seem like it can't multi-task like it once could. However maybe its app developers just heinously demanding more resources so their apps can look amazingly fluid because they forcefully killed everything else in the back?
What's the deal?
I remember a time in yesteryear yonder, whence I would have 5-7 apps running in the back without breaking nary a sweat. SO WHAT THE HELL happened Android? That was back on Touchwiz and Gingerbread!
Today I can't have utorrent and chrome open simultaneously. TWO apps. For instance if I've utorrent downloading, ill switch to Chrome (recent apps switch; not open) and maybe answer a Whatsapp immediately after; utorrent will undoubtedly be killed and must be reactivated.
Now I understand that chrome and utorrent are naturally RAM heavy applications, but it helps further my point. Why are apps being killed so quickly today? Was it Touchwiz that was great at ram management? Was it gingerbread? Or have apps been slowly updating over the last two years and demanding more allocation of RAM from the get go so that everything else gets forcefully killed? I remember when the Hercules was announced and all the reviewers claimed 1GB was such a stupid amount of overkill RAM and we'll never see it taxed. Now that 2GB has become the standard with the introduction of the GS3, I theorize app devs are being more liberal in demanding resources from devices without giving too much consideration for older models. So apps are killed more frequently to make room to the foreground.
So why do you care?
-The stock stopwatch app will die if you run a few more apps afterwards. This is just derp. Really, try this yourself. Can you imagine your morning alarm was silently force killed because you were reading a website before bedtime?
-Some audio apps can be killed as well. ie Doggcatcher. Audio actually stops if certain conditions of apps are opened after Doggcatcher. Derp.
-Device slows to a complete crawl during the course of a day. I don't believe I've ever owned a device (clamshell Sammy, Blackberry or Android) that didn't exhibit facepalm-worthy memory leak issues. If Android was designed to have its RAM filled, why do slowdowns exist?
-Incoming phone calls suffer lag when re-acquiring attention. This seems bizarre because in About > System you can see the Hercules indicates it has 768MB RAM, indicating a quarter is reserved for system apps. Which means it shouldn't really have this problem.
-Application settings requesting 'Persistent Notifications' to ensure app foreground attention. Apps like Tasker, utorrent, Battery Guru request this to remain alive. Is this the solution now? And is this 100% immune if system requires the resources?
-Apps take longer to open. I can't quite pinpoint this. Just a feeling.
Alright man relax, the Galaxy S4 and HTC One come packing with 2GB
Upgrading to a new flagship doesn't seem to be the solution to stifle this issue. App developers are excellent at what they do and naturally want their product to look its best with the resources available to it. With 3D games exhibiting the capabilities of a Snapdragon 600 and Tegra 4, where's the incentive to tell either to slow down? This same logic can be directly applied to the smartphone spec war and the recurring battery life bottleneck story.
Excellent read here from Gizmodo:
So what's your point?
I'm not sure I have one. I'm just observing whats happening. We are finally actually seeing applications that are pushing our hardware to its limits. While 1GB of onboard RAM used to be a drool inducing spec, 2GB is not really a huge leap considering the jump the Snapdragon S3 made to the S4, S4 Pro and now the 600 in magnitudes of processing power. 2GB would certainly be astronomical, if it took a trip back in time and only had to run 2011 apps. I guess my point is: I'm throwing a tantrum that the Hercules is showing its age, even if it's not its fault.
Forgive my rambling and lack of proof-reading. At work.
Click to expand...
Click to collapse
lol...I totally agree. My apps seem to close a lot quicker, yet my RAM never dips below 280 MB free. Don't really get it myself...
Come to think of it, our phone is truly amazing.
It has far-exceeded its original shelf-life, and is still very capable to uphold itself in these upcoming years.
Three cheers for Android!
HOORAY HOORAY HOORAY
Sent from my Galaxy Nexus using XDA Free mobile app
I
Reinvented said:
Come to think of it, our phone is truly amazing.
It has far-exceeded its original shelf-life, and is still very capable to uphold itself in these upcoming years.
Three cheers for Android!
Click to expand...
Click to collapse
yea, it's just sucks a little that Google/TI no longer support it.
and also apparently didn't do much of anything in the ways of optimizing code as per omapzoom and other things. I just feel like this thing still has a pretty nice amount of untapped potential in it and wish I knew how to do anything at all in order to pull it out. because while SURE it can perform nicely, there ARE times where you can tell it's strained. and it Just seems like with proper coding it shouldn't at all. Imho the cpu is plenty good enough to handle more than it does, but due to other factors that also put a damper on battery life, it has been held back just a bit from it's full power in order to squeeze that extra necessary juice out.
(which brings me to a side question here, not trying to thread hijack sorries. but, a lot of times you see kernels and roms that have descriptions for "battery tweaks". and in my experience, saving battery tweaks usually go in hand with a slight, even if minute, drop of performance. what I'm trying to find out is what specifically was changed for those "battery saving tweaks". I would personally like to play around with those values. one thing I came across was I believe kernel tweak for "random read/write wake threshold" in sysctl which a lot put to 128/256 respectively as a battery saving tweak. I'm still researching/testing into just exactly WHAT that is for, but I have lowered those values from anywhere of 64/128 to 8/16. but I'd like to couple that with any OTHER changes to see what can be squeezed so to speak lol...anyone let me know if you know of any that you used in the past so that I might look into them and see if were implemented in my setup and reverse them if possible....pm me IF OP would rather this not clog up the thread lol sorry)
but yeah I agree mostly as well, especially with the great devs who worked on & the newer guys who have been jumping on to keep things moving forward, it's just GREAT community for a solid device.
it's my first nexus and I'm extremely happy I got it within 4months of launch so that I could be around and grow WITH it, learning a ton and experiencing it's evolution. it's been fun and STILL is after so long. it is cool to see that even when development started to slow a bit, others jumped to the plate and started digging in, reviving all the excitement. cheers to all in this community!
I see it the other way:
That newer phones may have gotten better specs but Android OS has not changed enough to justify updating to the latest/greatest phones.
For the past 20 months I'm still enjoying using 4.1.2 ROM seeing as the GN was the official 4.1 Jellybean show piece.
I've personally found KitKat to be a dumbed down version of Android, especially since Google removed tablet mode.
ashclepdia said:
I
yea, it's just sucks a little that Google/TI no longer support it.
and also apparently didn't do much of anything in the ways of optimizing code as per omapzoom and other things. I just feel like this thing still has a pretty nice amount of untapped potential in it and wish I knew how to do anything at all in order to pull it out. because while SURE it can perform nicely, there ARE times where you can tell it's strained. and it Just seems like with proper coding it shouldn't at all. Imho the cpu is plenty good enough to handle more than it does, but due to other factors that also put a damper on battery life, it has been held back just a bit from it's full power in order to squeeze that extra necessary juice out.
(which brings me to a side question here, not trying to thread hijack sorries. but, a lot of times you see kernels and roms that have descriptions for "battery tweaks". and in my experience, saving battery tweaks usually go in hand with a slight, even if minute, drop of performance. what I'm trying to find out is what specifically was changed for those "battery saving tweaks". I would personally like to play around with those values. one thing I came across was I believe kernel tweak for "random read/write wake threshold" in sysctl which a lot put to 128/256 respectively as a battery saving tweak. I'm still researching/testing into just exactly WHAT that is for, but I have lowered those values from anywhere of 64/128 to 8/16. but I'd like to couple that with any OTHER changes to see what can be squeezed so to speak lol...anyone let me know if you know of any that you used in the past so that I might look into them and see if were implemented in my setup and reverse them if possible....pm me IF OP would rather this not clog up the thread lol sorry)
but yeah I agree mostly as well, especially with the great devs who worked on & the newer guys who have been jumping on to keep things moving forward, it's just GREAT community for a solid device.
it's my first nexus and I'm extremely happy I got it within 4months of launch so that I could be around and grow WITH it, learning a ton and experiencing it's evolution. it's been fun and STILL is after so long. it is cool to see that even when development started to slow a bit, others jumped to the plate and started digging in, reviving all the excitement. cheers to all in this community!
Click to expand...
Click to collapse
But linaro,omapzoom,cyanogen and much others still support our phone
What we need to do?We need to update to 3.4 kernel and add all 3.4 new things,inprove trim support,fix power hall(fix deep sleep mostly)
i will try to fix those,its my mission
I like how light kit kat is. But I remember better battery life on JB ROMS. I thought it would be the other way around but it's still nice to be on the latest version of android
Sent from my Galaxy Nexus using Tapatalk
In all honesty, I have found that my battery life has been about the same between JB and KK.
Whiteboy_cannon said:
I like how light kit kat is. But I remember better battery life on JB ROMS. I thought it would be the other way around but it's still nice to be on the latest version of android
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Newer Android is usually the best route.
I've never personally understood why people cling onto Android 4.1, or 4.2.2 (when theyre rooted and have this specific phone)
Reinvented said:
Newer Android is usually the best route.
I've never personally understood why people cling onto Android 4.1, or 4.2.2 (when theyre rooted and have this specific phone)
Click to expand...
Click to collapse
I don't get it either. But to each his own
Sent from my Galaxy Nexus using Tapatalk
Unless you play games you really don't need a new super powerful phone with a 2.5ghz quad core processor and 3gb of ram.
The Galaxy Nexus does an alight job for every day use, i do feel it could be quicker sometimes and wish i had better battery life, but as phone ive used daily for two and a half years i really cant complain too much.
it truly is a great device. It's all thanks to the great Devs working so hard for a device that has been forsaken by Google, itself lol.
InsaneNutter said:
Unless you play games you really don't need a new super powerful phone with a 2.5ghz quad core processor and 3gb of ram.
The Galaxy Nexus does an alight job for every day use, i do feel it could be quicker sometimes and wish i had better battery life, but as phone ive used daily for two and a half years i really cant complain too much.
Click to expand...
Click to collapse
GN can run games just fine, problem is app builders don't support it so some great games don't even show up on the play store.
Eg.
Real Racing 3
isajoo said:
GN can run games just fine, problem is app builders don't support it so some great games don't even show up on the play store.
Eg.
Real Racing 3
Click to expand...
Click to collapse
That game you mentioned shows up and lets me install on my Galaxy Nexus fine:
I dont really play many demanding games on my phone, the latest i have played is Trials Frontier which has never given me any problems.
InsaneNutter said:
That game you mentioned shows up and lets me install on my Galaxy Nexus fine:
I dont really play many demanding games on my phone, the latest i have played is Trials Frontier which has never given me any problems.
Click to expand...
Click to collapse
Why would I need to make it up?
It may just be my ROM that's some how blocking certain games even though the example you gave is compatible with Android 2.3+.
The desktop play store version has always been weird.
Eg.
Electronic arts developer has 37 apps listed on desktop play store where on my GN via play store app there's only 17.
LOL
isajoo said:
Why would I need to make it up?
It may just be my ROM that's some how blocking certain games even though the example you gave is compatible with Android 2.3+.
The desktop play store version has always been weird.
Eg.
Electronic arts developer has 37 apps listed on desktop play store where on my GN via play store app there's only 17.
LOL
Click to expand...
Click to collapse
I'm not saying you made it up, i believe you, i was simply showing at least on my Galaxy Nexus i had no problem with the game you mentioned.
Maybe its a regional thing? for example the Trials game i linked to was only out in Finland for a few weeks, then it got released to more countries after that.
Totally agree with the op.. Software wise it still runs great.... And hardware wise I still feel it one of the most beautifully designed phones ever..
Sent from my Galaxy Nexus using Tapatalk
It's a beautiful phone indeed, if you don't use the 2100 mAh battery and the "assy" cover which makes it a little ugly.
Agree.. I have not added any extended batteries for the same reason .. I like it's slim and curvy profile... Just got an oem one as the original had worn out
Sent from my Galaxy Nexus using Tapatalk
My guess is people tend to remember better battery life with JB because their battery was new back then Totally agree with OP, I've been using my GNex for 2 years now and thanks to continued support from developers I'm still excited and try new stuff to this day. I plan to change it in 2015, but as much as my next phone will be so much better in every department, I do have a feeling that I'll miss my good old GNex somehow
This is the most versatile phone I've ever used.
Sent from the homie
I know unused ram is wasted ram, but I'm constantly at 90% ram and it's causing the phone to lag and stutter to the point its unusable unless I reboot then I'm good. Just wanted to see if anybody was going through the same thing or if I have a rouge app up to something.
I've noticed that myself.. That is why I have debloated my phone without root. I have also notice the biggest user of the ram is the Android OS 1.3 Gb.
Joe199799 said:
I know unused ram is wasted ram, but I'm constantly at 90% ram and it's causing the phone to lag and stutter to the point its unusable unless I reboot then I'm good. Just wanted to see if anybody was going through the same thing or if I have a rouge app up to something.
Click to expand...
Click to collapse
Same here. It's a typical LG thing. Their Android mods are slick and lovely, but they're far from lightweight.
I moved from a Sony XZ1 Compact to a G7, and it is generally a significantly slower, laggier experience. With the Sony it would generally use less than 2gb of RAM at the outset. I could come back to an app a week later and it'd still be open. With this G7 I think it's rare to see it under 3gb consumption, and every time I open the camera I'm evicted most other apps from memory.
Then there's the lag! I thought a years newer flagship tech would have minimized the LG lag experience, but no.
Also no, at least for T-Mobile uS G7, no root, no AOSP and official device trees. I am made of regret, definitely never another LG, and Sony for me from here on out.
This phone has given me the least amount of issues with lag and freezes out of any phone I've had. I do a lot of gaming on here and rarely have an issue. I try to install as much as possible on my SD card, I don't know if that would make a difference with RAM usage, and I don't leave a bunch of apps running in the background.