Android L performance on 1st-gen X?

[erikdstock]

My X has been getting slower and slower in the last couple months... especially with maps and hangouts (whose new update I love), I'm starting to wonder what will happen performance-wise when L rolls out.

Does anyone have any idea? Maybe someone using a beta? I've already enabled and disabled ARM after not finding it particularly helpful, but I know the talk is that L might bring some performance improvements. Wishful thinking, I know.

 

[doogald]

We won't know until it comes out. Presumably Motorola will make a build that best works with the hardware and will choose to release it if the performance meets their standards.

 

[Thom]

Welcome to Android Forums.

Performance ...

Did you Wipe Cache Partition and do you do it periodically? (I do it on my Droid Maxx once a week.)

This will remove all temporary files and not touch data that you have saved or settings you have made.

The cache can become fragmented over time and really slow things down as it makes adjustments to save new temporary data.

... Thom

 

[edcooper714]

Can you tell us how to wipe the cache partition?

 

[Thom]

From the Motorola website ...

This will remove any temporary files that may be causing the problem, but will not delete your files or settings.
1. With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
2. The device will display different BOOT OPTIONS
3. Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
Tip: If the device reboots, you may have waited to long to make a selection, you will need to begin the process again.
4. The device will display the Motorola logo and then the Android in distress ( logo with Exclamation mark)
5. Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
Tip: You can try this step, holding the phone in landscape. If you are stuck on step 6, try a force reboot by pressing the Power key and Vol Down key, and start the process again.
6. The device will display additional menu options (Text will appear in BLUE)
7. Use the VOL DOWN Key to scroll to wipe cache partition and the POWER Key to select this option
8. The device will then perform the partition wipe
9. The device will reboot and start the normal power up sequence

From Verizon website ...

Performing a wipe cache partition removes any temporary files that may be causing an issue with the device. All personal files and settings are not be affected by this option.

1. Power the device off.
2. Press and hold the Volume down button then press the Power button and hold both buttons for three to five seconds then release both buttons.
3. From the Boot Mode Selection Menu screen, select Recovery.
   
   
   Utilize the Volume down key to scroll through the options and Volume up to select.
   
   
   If the device reboots, you may have waited too long to make a selection. Restart the process.
4. From the Droid triage screen:
   1. Press and hold the Volume up button.
   2. While holding the Volume up button, press and release the Power button.
   3. When the Android system recovery screen appears, release the Volume up button.
5. Select wipe cache partition then press the Power button.
   
   
   Utilize the Volume buttons to navigate the options.
   
   
   The device restarts.

... Thom

 

[hisense]

My X has been getting slower and slower in the last couple months... especially with maps and hangouts (whose new update I love), I'm starting to wonder what will happen performance-wise when L rolls out.

Does anyone have any idea? Maybe someone using a beta? I've already enabled and disabled ARM after not finding it particularly helpful, but I know the talk is that L might bring some performance improvements. Wishful thinking, I know.

I have Google Maps and Hangouts updated (for SMS only). I do not have any performance issues? Seems to have no impact.

 

[erikdstock]

Is this a real thing? I remember years ago (before i switched to ios) all the mythology around task killers, and it just seems like you shouldn't have to go into recovery mode on a weekly basis to keep a phone running its best. if it's necessary, it should be automatic.

 

[Thom]

It is the nature of the design to not remove tasks and their temporary data. This improves the speed when you switch from one task to another. If the task was removed it would have to be reloaded and reinitialized.

If you don't have any perceptible performance degradation ... don't bother.

If you are noticing a degradation ... Wipe Cache Partition and see the difference.

The problem with task killers is that some tasks are started automatically and it not always obvious that they are. A task killer removes it and it restarts automatically. The cycle continues forever and performance really suffers as a result.

... Thom

 

[svensett]

Is this method better than using a cache cleaning app? I was using App Cache Cleaner on my S3 and it seemed to help.

 

[Thom]

I have never found a source that sys this app does this and that app does that and the build in Wipe Cache Partition does this.

All I know for sure is that the Wipe Cache Partition works.

... Thom

 

[Medion]

Welcome to Android Forums.

Performance ...

Did you Wipe Cache Partition and do you do it periodically? (I do it on my Droid Maxx once a week.)

This will remove all temporary files and not touch data that you have saved or settings you have made.

The cache can become fragmented over time and really slow things down as it makes adjustments to save new temporary data.

... Thom

I would ask that you please be careful giving out information like this. First off, we're using flash storage. Fragmentation doesn't affect it like mechanical hard drives.

Wiping your cache can be beneficial or detrimental. The primary function of the cache partition is to allow the OS to quickly recall things that are commonly used without keeping it in RAM (think of it as the benchwarmer to RAM). By deleting this cache, you are actually SLOWING your device performance.

On the other hand, the cache tends to build up with crud from apps that you no longer use or have even uninstalled. Generally, this is harmless (because apps that aren't installed or used won't be able to recall this dormant cache), but clearing it up will give you some space.

However, sometimes the cache can get bogged down from outdated versions of apps (Chrome is REALLY bad about this). Clearing out the cache for an app that is causing problems (just the app, not all of the cache) can sometimes help. You can also be proactive by wiping the cache for a specific app when it receives an update.

Finally, there are two cache partitions - Dalvik cache and /cache. Wiping dalvik cache (as Thom described) works at a lower level. This will temporarily increase boot/reboot times until the apps have rebuilt their trees, but will clear out garbage from apps that have been uninstalled. This is generally a good idea to do after a firmware update.

The /cache partition can be wiped from inside the OS by going to Settings --> Storage and tapping on the cache. This clears out the data storage by the OS relevant to apps for quick recall. This has a more immediate impact on performance, in that wiping this will usually degrade performance until rebuilt because it's rebuilt on a per-app basis. Best to just leave this alone.

There are many ways to speed up your devices. Wiping the cache (outside of a firmware update) is about as effective as sacrificing a goat. Note: I don't recommend that either.

 

[Medion]

Is this method better than using a cache cleaning app? I was using App Cache Cleaner on my S3 and it seemed to help.

Cache cleaning apps are even more worthless. All they do is trigger the OS front-end cache wipe process, which is done as described in the post above:

-Go to Settings --> Storage, then click on cache. It's wiped (except for a couple of MB that the OS considers important).

 

[Thom]

Wiping your cache can be beneficial or detrimental.

Yes and my suggest was ... if you don't notice a problem ... don't do it. If you notice a degradation ... give it a try.

There is junk left in the cache and it may not be an issue. Then a requirement comes along to store a large contiguous item and existing smaller items are moved around to permit it. This is one way that degradation comes in.

If you don't have this condition then you may never run into the problem.

When people have older phones and are complain about he speed and everything is slowing down and they arte going to buy a replacement ... I recommend wiping the cache to see if it makes a difference.

... Thom