Ask Slashdot: Getting Apps To Use Phones' Full Power?

First time accepted submitter MurukeshM writes "I have a 16 GB Nexus 4. I rarely manage to push the RAM usage above 1 GB (not counting cached processes). Yet I find it increasingly annoying when apps do stuff to save on RAM usage, such as having a browser reload a tab if I havent used it for a long time, instead of keeping it in memory or have an ebook reader load from storage instead of keeping the entire eBook in RAM. I know there are plenty of phones with far less memory, but when most of the RAM is unutilized, with more and more phones and tablets having 1GB+ RAM, isn't it time that apps check on available RAM and use optimizations accordingly? And it isn't only about RAM. Android by default only downloads one thing at a time, whether it be an app from Play Store or a file from a site. When connected to WiFi or 3G/LTE, there's no reason why multiple simultaneous downloads shouldn't be used. How do Slashdot readers with high-end phones get the most out of their device? Are there custom ROMs which act more sensibly?"

Comments

That phone has 2GB of RAM

[Anonymous Coward]

The 16GB Nexus 4 doesn't have 16GB of RAM. It has 2GB. Your post reads like you think it has 16GB of RAM.

Re:That phone has 2GB of RAM

[adycarter]

exactly what I was just about to say.

The 16gb in your 16gb Nexus 4 is internal storage memory.

It has 2gb of Ram

Re:That phone has 2GB of RAM

[jeffmeden]

Also, my Nexus 7 certainly seems to download multiple files at once.

This. Certain apps (like the play store) download one at a time because they are trying to be nice on your phone (since the time saved from multiple downloads is negligible anyway, unless you have a really good 4G signal). How much time do you spend waiting on play store app downloads anyway? The OS at large has no such restriction, you can download things from the play store while you are downloading things from a web page, or things from a Torrent, or whatever; it is all up to the app. I have run a Torrent client with 32 connections across 5 file downloads and Android had no problem with it (it did make video playback skip occasionally). I agree that phones are generally more powerful than the software expects at this point, but the way the question was worded, this is a problem looking for a solution.

How about this: How can I get my phone/tablet to do compute work (folding @home, whatever) when it's plugged in and fully charged (like, most of the night)? These devices have multiple GB of ram, 2 to 4 CPU cores, and 4 to 8 GPU cores, why not put them to work if they are on-charger and full of juice (when the charger's role is done)?

Summary a bit confusing...

[bondsbw]

Just a note for future articles:

I have a 16 GB Nexus 4. I rarely manage to push the RAM usage above 1 GB

There is no need to include "16 GB". Both devices have 2 GB of RAM. To someone who doesn't know this, the summary might imply that they have some awesome 16 GB RAM model.

The problem with ram

[Anonymous Coward]

The problem with ram is that you can't do that. Unfortunately traditional apps live in a world where memory can't be "taken back". By taken back I mean that precisely as you request, an app could have a minimum requirement of 10MB, but maybe it could cache stuff for 1GB. However, there is no easy way to the OS to tell the app politely "hey, may you please give back as much memory as you can because something else needs it?". The problem is two fold for mobile apps: they may be "thawed", so they are not really executing to save CPU, so they can only be asked if they are currently running. And second, the memory another app is asking, is it because it requires that memory to work, or it also wants to create a big cache of discardable stuff? You see, malloc et all don't have an option to say "I want this much memory but I don't really need it, so don't purge other processes form memory if there is none available".

The end result is OSes have to deal with killing apps to free memory because they end up over allocating memory. And especially if you consider all of the above to be for well behaved apps, you can surely understand apps could DOS your OS if they could get away with hogging available memory for themselves...

cyanogenmod

[admdrew]

I run Cyanogenmod on all of my Android devices (currently Galaxy Nexus for my main phone, Nexus 7 tablet, and an older HTC G2 phone for playing around with), and have never looked back.

As others have mentioned here, though, sounds like you may not fully understand what's going on, since the Nexus 4 doesn't have 16GB of RAM, and we all seem to be able to do multiple downloads at once.

Re:Ferrari

[Chrisq]

Dear Slashdot:

I bought this Ferrari and I live in a suburban part of the US. I can't drive it over 70mph on the highways and I'm constantly in stop and go traffic in the city. It's so frustrating!

Can anyone of you tell me how to get the most out of my car?

Sure, Dress in a flashy suit then drive slowly (20mph or less) past a hangout of hot babes. Then go in and ask "anyone fancy a ride?".

Force stopping 'Running Apps' from 'Switch Apps'

[SternisheFan]

A little OffTopic about Android's 'switch apps' feature (on ICS and higher) from a recent Slashdot discussion.

I've learned that swiping the app offscreen to the left doesn't 'force stop' it, it just removes the icon from the 'running apps' list.

Doing a 'long press' on the apps icon brings up a sub-menu of 2 options, "remove from list" and "app info". Tapping on the 'app info' shortcut brings you to the 'app info screen', from there the app can be 'force stopped'.

I'm posting this here in the hopes that it'll clear up any confusion caused by that previous discussion. :-)

Re:On the other side

[tlhIngan]

Exactly. The problem with Android is that for every flagship nexus or SGS4 sold, dozens more crappy low end ones are sold.

The free phones. The ones with crap screens, crap processors, and/or diddly squat for RAM (though for Android these days, that applies for anything smaller than 4.5" screen, annoyingly). After all, Google claims about 1.3M daily Android activations, while the most popular Android flagship phone, the SGS3, has sold around 40M units in all its various combinations. That's barely a month's worth of Android phone sales.

And possibly, ancient OS versions (heads up - Gingerbread is no longer the majority! Though it is by far the largest slice). So you can have apps that use all the power of the device (I've seen special edition apps restricted to certain devices), but most devs don't have the resources to maintain and test two or three separate sets of code bases and/or assets. Especially as a lot of the exclusives are often comissioned by the manufacturer who just pays for the port and no maintenance.

So devs have to keep in mind the vast majority of phones out there don't have 2GB, or even 1GB of RAM, and have 1GHz processors if they're lucky. And maybe 320x480 screens. Or 5" 480x800 screens.

Yes, Android has basically wiped out featurephones (more profitable, and carriers get to sell a very profitable data plan to someone who probably will be lucky to use 1MB out of their 100MB). (And stats show this - despite Android outselling iOS 3+:1, iOS data usage still beats Android 2+:1).

It's like PCs these days - you can get a top notch PC with the latest graphics, but end up finding most PC games assume an Intel graphics accellerator or are ported from consoles. It just isn't that big a market.

Then again, there's something to be said that the people who buy the flagship phones tend to be the heavier users, so ignoring the low end isn't that bad a strategy either. Why go for the 80% market when fewer than 10% of those probably would even see your app, but go after the 20% when 50% or more will probably buy it? (Generally speaking, it's the reasoning behind developing for iOS first).

Re:Read up on ARM

[TheRaven64]

This is a platform that was not designed to have a scheduler carving up resources

Uh, what? The ARM architecture was designed for Acorn's line of 32-bit desktop computers, which shipped with a multitasking OS from the start. Now, it wasn't preemptively multitasking, but the only difference between cooperative multitasking and preemptive from a hardware perspective is that you need (relatively) cheap timer interrupts to enable preemptive multitasking, and ARM has always had this.

The cost of context switching boils down to a small number of things:

• The cost of delivering the timer interrupt (interrupts on ARM are cheap and have a small number of aliased registers to play with so the code in the interrupt handler can be simple)
• The size of the register set that needs to be saved (ARM is 15 32-bit GPRs, which can be saved and loaded in a single multi-cycle instruction, only x86 has a smaller register set)
• The cost of TLB flushes and refills required during the switch (ARM has a tagged TLB, so you only need to invalidate any TLB entries when you recycle an ASID)

In summary, the orifice that you are talking out of is not your mouth.

Single digit GB/mo cap

[tepples]

most people don't have anywhere near [50 megabit per second wired service] for their home/office, but can get it through 4G.

A 50 Mbps downstream is fine for the first 800 seconds, after which it drops to 0 Mbps for the rest of the month because the customer has hit the 5 GB/mo cap. The advantage of wired is that the cap is 50 times as high: 250 GB/mo, not 5 GB/mo.

you basically need to saturate the google server sending you the app

It's not just Google Play Store. If I'm downloading a bunch of files through Chrome, I want to saturate multiple servers, most of which are not operated by Google.