Android System Requirement Bloat - Android General

I'm using Gingerbread, and I tried Kit Kat, and my phone was super slow on it, so I downgraded back. I looked up the system requirements, and found that all version 4.x require a minimum of 512Mb of Ram. I think Gingerbread was 384Mb. I have read that Lollipop has even higher system requirements. My question is, what are they adding? I don't miss anything having gone back to Gingerbread. What are they doing to Android, that it requires such faster cpu, gpu, and ram?
I read about how "improved" these new versions of Android are over their predecessors, but as an end user, I don't find anything worthwhile. Granted, support will continue to be dropped for Gingerbread... but at the moment, my set of apps do everything I need. Can someone tell me something I can't do right now on Gingerbread?

Related

[Q] alternative OS's on feature phones

Hi, does anyone know if it is possible to load an alternative OS like android on a feature phone? by this I mean phones that have an integrated processor, not like a cortex or a qualcomm one that you can easily find it's clock in the phone's spec sheet. I've been having a terrible time trying to figure this out, and having no results.
I also know that for some phones, this is possible, but they must have some sort of a capable processor and a considerable amount of ram and rom. However, my phone's pretty limited in those terms, but I still think it might be able to load an alternative OS.
BTW my mobile is a samsung s5600
thanks.
I think it is a Samsung S5600 is impossible. because it is just a telephone. In the phone is quite different RAM modules and CPU, which is much weaker and easier.
Sorry for my bad english
no problem, I understood
I still think that with an old android firmware (like 1.5 or 1.6), the phone might be able to withstand it, as they don't require too much ram or a fast CPU. as for rom space, I have no idea...
I really hope to get a dev interested
2.2 requires least ram but would need alot more work with the kernal to port over
yeah, I've heard that somewhere around.
do you know what about v1.6?
P.S.: btw i just found out this phone has an MSM6280 chipset which has in itself an ARM926EJ-S processor
And then there's the fact that someone would have to write drivers for the chipset, graphics, sound, and everything else that the OS is meant to talk to...
Isn't that all integrated in the chipset itself? I mean, wouldn't it just need the chipset driver only in that case?
anyway, the question still remains though. is it really possible or definately not?
Thanks

Android 4.0 for a Lg optimus 3D

Hey people does anyone know if android 4.0 will be available for the Lg optimus 3D when it comes out around December
Virus711 said:
Hey people does anyone know if android 4.0 will be available for the Lg optimus 3D when it comes out around December
Click to expand...
Click to collapse
No........................
Virus711 said:
Hey people does anyone know if android 4.0 will be available for the Lg optimus 3D when it comes out around December
Click to expand...
Click to collapse
almost had heartattack reading topic name :S
we dont have 2.3.3, and you are dreaming about 4.0?
Well let me read the cards...errrr
Some one is flying high. Anyways I can't see why not with a little magic of the dev community.
Sent from my LG-P920 using XDA App
i'm shire it will come also for o3d by lg or through the great developers in this forum.
but why do you what it already? maybe it's crap? i doubt it but maybe....
and one of the golden rules:
be patient, good things need their time
I wouldn't be surprised if 4.0 won't run on this phone due to the ram, even if it does its going to be well into next year before we get it, I would be surprised if we have it for next summer judging how far behind LG are now, this phone and the Optimus X2 should have launched with Gingerbread.
if cyanogen support this device, there will be 4.0 for us
the already support this device
typhex said:
if cyanogen support this device, there will be 4.0 for us
Click to expand...
Click to collapse
but 3D will be useless without the drivers for the cameras and the screen
mmace said:
but 3D will be useless without the drivers for the cameras and the screen
Click to expand...
Click to collapse
True but all the S3D core code it open to the devs thanks to TI as I understand it.
Also it's not even sure it's called 4.0, they haven't set a version number have they? and the number is just a indicator, the jump from 2.3 will be stuff like optimization in the system for dual core, and people still talking about too little RAM is just poppycock.
Most likely performance for the O3D will be better with Ice Cream Sandwich, might even beat all other phones as it's (so far) the only one with dual RAM and dual Channels which keeps the dual-core CPU from being bottlenecked by the rest of the system.
I have to admit, this talk of "ooooh it might not run version xx.yy of Android" or "ooooh what if the new uber fantastic app doesn't work because it ONLY has 512MB RAM" makes me laugh.
Why? Well lets look at what the problems have been in the past:
OS Partition is too small:
This was a problem when the OS was written to fit inside the small flash built-in to the CPU package. As the OS has gotten bigger this had to be solved one way or another. I'm not sure of the specifics, but I think its enough to say this is solved now.
Not enough RAM:
Fitting an advanced OS into 64MB or even 256MB of RAM is tricky, especially when the core OS is based on code from PCs with a lot more RAM than that and the luxury of a swap partition.
However 512MB was the turning point on PC where RAM became less of an issue and in the right configuration you could live without swap. So logically this should hold true, probably moreso, for Android. Because Android until recently was already running in 128MB/256MB without the advantage of swap space.
No Drivers:
Many are open source, we are also working with hardware a lot more standardised than it once was.
I can see from a glance that there are a lot of similarities between my N900 at the hardware level and the O3D. If you are dealing with devices that are basically upgrades of old hardware designs, drivers are a lot easier to deal with - especially if they are open source.
Lack of GPU or certain CPU instructions:
Many older devices could not handle newer Android because they lacked a proper GPU or the CPU did not have the right instructions. This is similar to what happened on PC for a while, when multimedia suddenly became big. Like on the PC once all these multimedia instructions became commonplace it was no longer really an issue. I believe we are at the same place now with high-end Android hardware.
So I really would be surprised to find a newer version of Android outright not be able to run on the O3D, for quite some time.

[P999 CAN HOPE????]Android 4.4 Support To Devices With As Little As 512MB Of RAM

If you've used Android 4.1 or later on a phone or tablet with 1GB of RAM, you know things can get a little tight in the memory department. That's what makes newer and slightly underpowered devices like the Lenovo Yoga a little disappointing. Google has decided to trim the fat with Android 4.4 in an initiative they've christened "Project Svelte." This isn't a single change, it's a wide range of additions to the Android API and optional hardware configurations designed to make KitKat run smoothly on devices with as little as 512MB of system memory.
According to the new 4.4 developer page, Project Svelte starts with recommendations and options targeted at device manufacturers. Specifically:
Dalvik JIT code cache tuning
kernel samepage merging (KSM)
swap to zRAM
tune out-of-memory levels for processes
set graphics cache sizes
control memory reclaim
When it comes to pure software, core processes have been trimmed to use less memory and protect system memory from hungry apps. Android will also launch concurrent services in sequence instead of all at once to prevent slowdown. Imagine it as cleaning out the Startup folder in Windows, except that it's all happening behind the scenes. Developers also have access to the new ActivityManager.isLowRamDevice API, allowing memory-hogging features to be enabled and disabled as needed. Google will be integrating this feature into its own first-party apps, so even those with more powerful hardware should see at least some benefit.
Project Svelte isn't going to magically make older devices compatible with 4.4 - even Google's own Galaxy Nexus (with 1GB of RAM) isn't getting an official update, likely because of the aging OMAP SoC. But this will hopefully help devices like the original Nexus 7 and Nexus 4, not to mention upcoming low-end phones that will launch with 4.4, to better handle resources as apps become more hardware intensive.
Not happening man lol
Sent from my LG-P999 using xda premium
You shouldn't expect anything from LG, and now that almost all the Devs have given up on the g2x, I too have realized that there is no hope for the g2x.
But although this phone got screwed pretty bad, if it wasn't for this phone I would have never known about the xda community and the joy of rooting, and for that I am grateful.
Sent from my SM-N900T using xda app-developers app
Same here, Knotes. If it wasn't for stock 2.3.4 gingerbread driving me insane with its lag, inconsistency and overall weak performance I would have never stumbled upon XDA and have rooted my phone to make it a somewhat halfway decent device (thanks to the amazing devs we've had) lol.
Sadly, I don't use my G2X anymore, I've gone back to using my Nokia E73/Mode Blackberry clone semi-smart phone which uses the obsolete Symbian OS, doesn't have a touch screen, has a real keypad, and does what I need adequately such as Skype, GPS with maps (I recently used it in Italy for a month), Wifi and phone calls. It has great battery life, very good audio quality, great cell radio range, easily fits in my pocket, is extremely well made and durable ( it fell from the roof on top of the 3rd floor of my house, while I was trimming tree branches, onto a concrete sidewalk and bounced into some bushes and only had a few scratches on the bezel at the top left corner. I do use a currently cheapest available Asus Android 7" tablet, that cost $150 new and runs Android 4.2.2 and it has had 3 updates since I bought it 2 months ago. It gets used when I need an app that runs on Android and to surf the net. I will never buy a new Android phone again and definitely not an LG at all, even used, because of what happened to the G2X.
No no and no g2x is dead period
sent from a note taker
Build a new CM11 ROM
Hi there !!! What if someone could actually build one Rom for p999 .... Even Huawei y201 Pro that is working on 512 MB ram has a CM11 based kitkat 4.4.2 rom available. It would be great if someone comes out and do this.:good:
It can be done but nobody can figure out the radio issue so it would be WiFi only. That is what killed this phone.
ROM for P999
Hi !!! This looks real sad. I am using CM 10.1 based on Jellybean 4.1.1 and it looks stable enough and so does the WIFI. Is there any newer version than this that is more stable? I checked the All ROMS thread but the newer ones are all buggy
Darth Tyranius said:
Hi !!! This looks real sad. I am using CM 10.1 based on Jellybean 4.1.1 and it looks stable enough and so does the WIFI. Is there any newer version than this that is more stable? I checked the All ROMS thread but the newer ones are all buggy
Click to expand...
Click to collapse
No that's pretty much it. There's a trick you can do to flash p990 roms, I'm not sure how much development they have going on over there. I actually don't have this phone anymore but if you use one of their nvflash utilities you basically can repartition your phone like theirs except for the radio which doesn't work anyway. If you're up for it there's been a few people who have done it. I make no guarantees. Godspeed.
Thanks For the heads up !!! I will head to the Optimus 2x section and see what i can find there ....

RAM left after loading phone with apps

Hello,
Can anyone here help me to report about ram left when you first get the phone and after you have loaded your phone with apps (viber whatsapp fb etc) these apps always taking up ram so much even when idling in background... I am asking this because i am still surveying which phone i should get. Its either nexus 5 or moto g. If the ram left is still plenty, i guess i might be able to survive with the motog for at least another two years and save some bucks along the way for other purposes. If not, i would opt for the nexus 5, although it would burn my wallet a bit. Thanks!
Edit: And.. I would be happy if there is anyone who would like to report ram usage before and after kitkat since Google has been vocal about kitkat being able to run on phone with 512mb ram, and being ram effiicient.
urra901109 said:
Hello,
Can anyone here help me to report about ram left when you first get the phone and after you have loaded your phone with apps (viber whatsapp fb etc.
Click to expand...
Click to collapse
Sure i'll try answer your question or give you some kind of idea about the amount of RAM left, i have a UK Moto G with Kitkat UK
Ok so I powered on the Moto G, waited 5 minutes while looking at the Running screen inside the Apps settings,
and i see 479MB Used & 403MB free (give or take a a couple of MB)
The user apps that are idling, are :
Vault = 14MB
Kik = 11MB
Applock = 6.2MB
Comodo Security = 4.8MB
If i then open up the 3 main apps that i frequently open (twitter, Kik, Gmail) and go back to the Running Apps Screen,
i see 494MB used & 388MB free
Hope this helps
urra901109 said:
Hello,
Can anyone here help me to report about ram left when you first get the phone and after you have loaded your phone with apps (viber whatsapp fb etc) these apps always taking up ram so much even when idling in background... I am asking this because i am still surveying which phone i should get. Its either nexus 5 or moto g. If the ram left is still plenty, i guess i might be able to survive with the motog for at least another two years and save some bucks along the way for other purposes. If not, i would opt for the nexus 5, although it would burn my wallet a bit. Thanks!
Edit: And.. I would be happy if there is anyone who would like to report ram usage before and after kitkat since Google has been vocal about kitkat being able to run on phone with 512mb ram, and being ram effiicient.
Click to expand...
Click to collapse
If you can live without 4g get the moto g,I use this the same as my HTC one and its super smooth, I run a lot of apps and ram isn't an issue, ram being used is a good thing too,as it means app launch faster as they are stored in memory,saying that I usually have over 200 MB free.
@OP your understanding of RAM is wrong.
Do not worry about the RAM usage.
RAM IS THERE TO BE USED.
There is no point in the system keeping lots of RAM free, this makes the system perform worse. The idea is that as apps are used (either started by the user or automatically started when an app is woken etc) they are of course using RAM, the system keeps them in RAM so they can quickly be accessed next time they are required.
If the system closed all apps etc to free RAM you basically end up with more free RAM, but for what purpose. No use it sitting there empty - may as well go and buy a phone with 128MB rather than 1024MB if you dont want to use much RAM.
If you start an app that needs a lot of RAM (more than is currently free) the system just removes older apps from RAM to free up the RAM required.
It is not worth comparing your phone's normal RAM usage to another phone, each person has different apps and uses the phone in different ways. It makes no sense at all to compare two phones where RAM is concerned.
If your phone is running fine and you have some free RAM, even if just a smallish amount, then most likely things are running just as they should.
@scott_doyland @kierancc88 @cra1g321 thank you for your detailed reply..
@scott_doyland @kieran88: i have same idea about the ram being used is a good thing. But what bothers me is the survivability of the moto g in the next future update for it. Today, according to @cra1g321 and @kierancc88 both reporting that the OS itself is already eating around ~ 700Mb of available RAM w/o any other apps running. What could this number be in the future, will the OS takes more RAM? Thus making reduced RAM available for other apps. Currently i am using SE phone from 2011 with 512mb ram, while it is very responsive on Gingerbread, it does suffer on ICS, my Tasker profile always closes itself due to low ram(most probable culprit). I am afraid it would happen all over like that in the future, but at the same time google seems to move towards more efficient ram usage. Lets hope the ram usage wont increase so much in the next android update.
Butttt.. Maybe i am complicating stuff.. anyways, thanks guys!
urra901109 said:
@scott_doyland @kierancc88 @cra1g321 thank you for your detailed reply..
@scott_doyland @kieran88: i have same idea about the ram being used is a good thing. But what bothers me is the survivability of the moto g in the next future update for it. Today, according to @cra1g321 and @kierancc88 both reporting that the OS itself is already eating around ~ 700Mb of available RAM w/o any other apps running. What could this number be in the future, will the OS takes more RAM? Thus making reduced RAM available for other apps. Currently i am using SE phone from 2011 with 512mb ram, while it is very responsive on Gingerbread, it does suffer on ICS, my Tasker profile always closes itself due to low ram(most probable culprit). I am afraid it would happen all over like that in the future, but at the same time google seems to move towards more efficient ram usage. Lets hope the ram usage wont increase so much in the next android update.
Butttt.. Maybe i am complicating stuff.. anyways, thanks guys!
Click to expand...
Click to collapse
Generally, your point is correct; however, KitKat is actually designed to better utilize a smaller amount of RAM than Jelly Bean. Theoretically, according to Google at least, a phone with 512mb of RAM will run KitKat better than it will Jelly Bean. Theoretically.
When android boots it loads apps into memory, its isn't just the OS that's using ram after a reboot.
Try it - reboot phone and look at running AND cached apps.
bought the dual sim variant of moto g.. Hehehe. So far i am very happy.
scott_doyland said:
@OP your understanding of RAM is wrong.
Do not worry about the RAM usage.
RAM IS THERE TO BE USED.
There is no point in the system keeping lots of RAM free, this makes the system perform worse. The idea is that as apps are used (either started by the user or automatically started when an app is woken etc) they are of course using RAM, the system keeps them in RAM so they can quickly be accessed next time they are required.
If the system closed all apps etc to free RAM you basically end up with more free RAM, but for what purpose. No use it sitting there empty - may as well go and buy a phone with 128MB rather than 1024MB if you dont want to use much RAM.
If you start an app that needs a lot of RAM (more than is currently free) the system just removes older apps from RAM to free up the RAM required.
It is not worth comparing your phone's normal RAM usage to another phone, each person has different apps and uses the phone in different ways. It makes no sense at all to compare two phones where RAM is concerned.
If your phone is running fine and you have some free RAM, even if just a smallish amount, then most likely things are running just as they should.
Click to expand...
Click to collapse
Finally, someone that understands what RAM is really all about.
Too often, I see people trying to limit how much RAM is being used for no good reason. Like what was said, RAM is there to be used, not saved for a rainy day.
I do understand that ram is there to be use. Honestly, the moto g performs really well to my liking. But when i asked the ram usage i was referring to "future proofness" of the device. Good by today's standard but may not be the same after 1-2 android update. Since every update seems to be more resource hungry.
Conclusion: the moto g is very well built product for what we are doing "right now" but with very little wiggle room(RAM) for any future update.
Sent from my XT1033 using xda app-developers app
It seems with Android their focus is to reduce needed resources, that was one of the main features in 4.4
We cant predict the future but Linux/Windows 8 runs fine with 1GB of RAM so if Android begins to exceed this then we need a new mobile OS.
Sent from my XT1032 using xda app-developers app
urra901109 said:
I do understand that ram is there to be use. Honestly, the moto g performs really well to my liking. But when i asked the ram usage i was referring to "future proofness" of the device. Good by today's standard but may not be the same after 1-2 android update. Since every update seems to be more resource hungry.
Conclusion: the moto g is very well built product for what we are doing "right now" but with very little wiggle room(RAM) for any future update.
Sent from my XT1033 using xda app-developers app
Click to expand...
Click to collapse
It also depends if you will always want to update to the latest and greatest OS. Personally Im still running 4.3 on my moto g. The reason is that its performing very well and there is nothing in 4.4.2 that I want. Of course its tempting to upgrade to 4.4.2 to have those few hours of excitement but after those initial few hours I will be using my phone to do exactly the same things as Im doing now.
The only reason I would upgrade to a later Android version is if an app I used a lot became incompatible with 4.3 or if a new Android version increased battery life by some amazing amount.
So the chances are that for me, 4.3 on moto g, is very future proof.
Also consider that in just a couple of years its likely the moto g wont get any more official updates anyway so whether it can run Android version 6 (or whatever) with only 1GB RAM may not even be a point of discussion unless you want to run a custom ROM. If you do this the chances are you will probably have a trimmed down Android anyway, ie GAPPS initially removed etc so RAM usage will be less. Although I appreciate GAPPS isnt part of the OS as such and any GAPPS can be removed from RAM by the OS when required - so my point is sort of skewed there anyway
But I agree with the post above, if 1GB is not enough for the OS and a decent amount of apps to run well then Android is not an OS you really want to be using on a phone regardless of the amount of RAM you actually have.

Android > 5.0.2 for Samsung Galaxy Tab A (SM-T357)

I have an old Samsung Galaxy Tab A (specific model in the title), and sadly, T-Mobile/Samsung updated Android up to 5.0.2. It is also a very slow tablet, given its hw.
Does anyone know about any Android/Linux Distro that could run in this tablet? LineageOS?
Device has a 1.2 GHz quad-core CPU and only 1.5 GB RAM. Changing device's Android OS doesn't make it faster run.
jwoegerbauer said:
Device has a 1.2 GHz quad-core CPU and only 1.5 GB RAM. Changing device's Android OS doesn't make it faster run.
Click to expand...
Click to collapse
I partially agree.
As you know, many manufacturers' Android distros come bloated, so a Vanilla one, with no vendor's "extra services" may help.
There is also the factor that most applications are no longer supported in it due to the Android version. For example, I'm a fan of termux, and I use it extensively in my phone, but the only way to install the latest versions is via F-Droid, and either F-Droid, or its version of termux (I don´t remember which one at this time), don´t work with Android 5.0.2.
I'm just trying to breath a little more life to this old tablet, so I can donate it to anyone that needs it. If I can't I will just throw it away.

Categories

Resources