PPCGeeks - [[Speed Improvements]] Brainstorming & Testing Thread!!

PPCGeeks (http://forum.ppcgeeks.com/index.php)

- Android On TP2 (http://forum.ppcgeeks.com/forumdisplay.php?f=179)

- - [[Speed Improvements]] Brainstorming & Testing Thread!! (http://forum.ppcgeeks.com/showthread.php?t=146441)

[[Speed Improvements]] Brainstorming & Testing Thread!!

Hey guys,

Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.

I'm only interested in discussing the latter ;).

A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!

I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.

So here's the disclaimer.

****DISCLAIMER****

Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster :D.

Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!

Topic 1

Difficulty Easy - Apps/Widgets

I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.

Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.

On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!

The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.

Topic 2

Difficulty Easy - Controlling app 'net Access

This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.

Topic 3

Difficulty Moderate - SD cache/readahead tweaking

The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will ;). This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...

So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).

There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!

I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!

Topic 4

Difficulty Moderate - Overclocking

Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line

Code:

acpuclock.oc_freq_khz=710400

for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.

Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well ;). Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.

Here's the full *example* startup.txt:

Code:

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2292

set KERNEL zImage

set initrd initrd.gz

set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"

boot

You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.

Topic 5

Difficulty Advanced - How Android Manages Memory/apps

Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.

Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...

If you want to do it manually, Starfox suggests:

Code:

echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree

To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.

I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!

I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:

Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.

Topic 6

Difficulty Advanced - Managing Apps that auto-start on boot

This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!

This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.

The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,

Code:

Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}

Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!

So in the shell,

Code:

pm disable nextapp.systempanel/.monitorservice.BootReceive

This will be persistent across boots, it will go with your data.img.

Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.

Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!

Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

I've noticed Starfox's test kernel with that turbo mode enabled actually creates quite a boon. It's RHOD-only, so I didn't include it in the first post...

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

acpuclock.oc_freq_khz=710400

is that something that gets added to the cmdline section or an entire line of its own?

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by nerys (Post 2137677)

acpuclock.oc_freq_khz=710400

is that something that gets added to the cmdline section or an entire line of its own?

cmdline section, I need to expand on that section...

Edit - updated that section. Thanks for the reminder ;).

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

I guessed that and tried it. did not blow up on me :-) once I let it load IT DOES seem quite a bit spunkier now. the gui is not much faster (but not intolerable) but apps LOAD quite a bit faster now at least they seem to so I assume its working. Now to go hunt for an auto killer since it seems to run an awful lot of background apps that I just don't need running in the background. (like gv and slacker etc..)

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by nerys (Post 2137685)

That's what the PM commands are for. If you go thru it (it's a pain, I know...) it'll disable these apps from starting on boot automatically (I had a ton when I started!) The problem with task killer apps is they don't solve that problem.

The other part of the problem is freeing up memory appropriately, which is hopefully addressed in the minfree stuff. I'd be curious of there's better values, I am going to run them for a while and see if changing them does make a difference.

It's not nearly as pretty, but using ADW, disabling all animations in Android and ADW have made things really, really snappy.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

maybe you did explain it clearly and I am unable to understand (lack of linux command line knowledge??)

but how do I know "WHAT" to type after pm ? ie where did you get the info? seems to be this logcat thing - where do I get that how do I read it?

there are some apps that just don't make sense (for me) to run in the background. for example if ebay is running in the background I am ok with that since it performs a function I desire. but I can not think of a reason why slacker should be in the background on boot or ever. same with quite a few other apps.

I want then to run when I run them but when they are backgrounded I want them dead :-) how do I do this?

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by nerys (Post 2137692)

Well that's what this thread is for, to discuss how to cut down on apps that start on boot, and how to manage memory in Android.

If you read the links, I provide one to the FAQ that jumps directly to the ADB section. This in turn has a link titled 'logs' that explains how you pull logs.

The commands can be entered in a local console on the phone (ConnectBot, Terminal Emulator, whatever) or thru adb. I find thru adb to be much easier, once you get it setup of course. I guess I need to flesh out a how-to a little more, gimmie time I threw this together kinda quickly and on a whim. Reading the links I provided & searching is always a good practice, but I will try to flesh out the explanations...

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

now are the processes I see running in say estaskmanager "different" from what your talking about here? or the same?

if the same the solution is really easy. I got this program called auto killer memory optimizer. its basically a front end to "adjust" the built in functionality of android to handle automated task closure to preserve operating memory.

ie safe :-) for the most part (I don't mess with the first half just the background stuff)

I set it all to 75mb and that keeps pretty much anything not running "active" out of memory and REALLY seems to improve performance. though how much of that is from the OC and how much from this I don't know but it does help.

I will await the howto and I appreciate you doing it too :-) I make a lot of how to's in my arena's (rocketry and photography) and I know how much of a pain them can be to do :-)

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by nerys (Post 2137754)

You can probably find an app to do everything I've outlined. As I said at the beginning of the diatribe I posted, I don't want to use any apps... I don't want more overhead, and I want complete control of what's going on - IE, I want to control Android directly. I don't want some app doing it for me, since I don't really know what it's doing (you're asking, but I don't know without watching what is in the logs when the app is first run...)

I didn't want the overhead of any more apps, and I also wanted to use the built-in abilities of Android to manage things. All any of these apps *should* be doing is adjusting these values, but how do you know a good task manager app from a bad one? Honestly they're all bad IMHO and I would prefer to do it directly. This thread is for those who want the same :D.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

thats fine. but I still don't know what your talking about hence the questions :-)

ie my primary question. the apps your doing this pm stuff with. are those the "SAME" apps I see when I open a task manager or are they "hidden" apps your closing?

if they are the same they I don't really need to worry about this PM stuff since resetting the built in memory clearance limits appears to do exactly what I want. stop the background stuff from grinding the system to a halt.

on the other hand of this PM stuff is "OTHER" apps that are NOT visible in a task manager or hidden apps taking memory then it might be of interest to me to know how to do what your doing to improve performance.

thats the only reason I asked. I don't care which way I do it manually or with an app. I am perfectly comfortable in a command line interface once I know what to type.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by nerys (Post 2137776)

Like I said, I have no clue what you're seeing in these apps. I'm not using any apps. I want the direct control. If you find an app that does what I'm talking about, great... that's on you.

If you're wondering what apps I'm using to put all these commands in, everything was done thru adb shell.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

I have no idea why you have decided consciously or subconsciously that I am your enemy or something.

Direct control is silly. your only interface is that keyboard stylus and screen. You can't have direct control. everything you do has to by definition be through a proxy IE an app.

a task manager is just that. it shows me "whats running" thats it. nothing more. it does not really DO anything (though it will let me kill an app) its no different than 3 fingering your windows box and bringing up the task manager. thats all.

NOW if your recall windows task manager you have TWO windows their and they are different.

one including running apps and one includes "processes" which include a lot more than just running apps.

I am trying to understand if yours is this "other" part or just the same as what I am looking at already.

My question stands. I don't want to ask it again since I think that will just aggravate you more which is not something I want to do.

I will wait till you finish your toot and "try it" and see what happens then.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

You're missing the point (again). First, you're not some mortal enemy. You just keep asking the same stupid questions over and over and you're either missing my points, or completely not grasping them, or just flat out ignoring them... I don't know.

First, how is direct control "silly"? I'm talking about something you setup ONCE. The system then manages it from there on... no need for user intervention, no need for apps to constantly monitor things... all of that is unnecessary. You tell the system how you want it to manage itself, and it does a very good job of doing that. You don't need to keep tweaking and looking at running apps... let the system manage it. "Set it and forget it", seriously. That's the point of direct control. That's the point of my thread.

Quit bringing up WinMo. This isn't WinMo. This is Android. If you want to use WinMo, then go use WinMo by all means... Android is different, and that's why I like it. For your information, what logcat is looking at is everything. Providers, processes, apps, whatever-the-heck is run on boot. Everything.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Mortal enemy? please. grow up.

sorry I will keep bringing up winmo as often as I need to. its my only point of reference for comparison. Nothing I can do about that.

the auto killer thing I got does PRECISELY that it modifies system settings and then thats it. the system "does its thing" from then on with the new settings.

I did not say direct control was silly the CONCEPT of direct control is silly since you by definition can not have it. unless you have a jack in the back of your head and can think code ?? it was intended as humor which clearly buzzed clear over your head.

"For your information, what logcat is looking at is everything. Providers, processes, apps, whatever-the-heck is run on boot. Everything."

and watch your tone with me. in case your not "getting" it yet that answer minus the attitude is EXACTLY what I asked for.

would it have been so hard to just give THAT as the answer instead of all your diatribe?

you are a very angry person. you really need to chill out and enjoy this instead of getting all nasty and steamy. won't do your health any good either.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by nerys (Post 2137792)

I don't even know how to respond to this other than...

Meh. I don't respond to empty threats.

Use the crap I posted, or don't. But don't spew all over my thread anymore, k? Thanks.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

hey. everything I typed was a DIRECT response to the "crap" you spewed in my direction. I initiated none of it. all "reply"

Hey arrrghhh how to you keep the new minfree settings to stick on reboot?

Sent from my Neopeek using Tapatalk

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by vzihome (Post 2137838)

Hey arrrghhh how to you keep the new minfree settings to stick on reboot?

I'm thinking a line in the user.conf file would be enough. Cat the value after rebooting to make sure it stuck.

Otherwise... I think you'd have to change the init.rc.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Updated topic 4. Should be much easier now to figure out the memory management stuff. Feel free to re-read that topic.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by arrrghhh (Post 2137588)

Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.

Quote:

Originally Posted by original thread

... Do NOT run the V6 SuperCharger install script at boot!

and something like
run it with Terminal Emulator or ADB , Script Manager is not needed ...
I´m a little bit confused. Can you please explain it?
(With this script the phone seems to be snappier indeed.)

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by Tippfehler (Post 2139546)

You're not running the SuperCharger script at boot, you're running a script that it specifically sets up to be run at boot. Read the original SuperCharger thread if you want more info. It creates a script, /data/99SuperCharger.sh that basically reapplies all of the settings you chose in the original SuperCharger script. This is not simply re-running the original script... As you can see the path is significantly different from wherever the original script is (usually /sdcard...)

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

lol... hey arrrghhh

Quote:

Originally Posted by nerys (Post 2138396)

if its sprint and works fine no issues I will take it for $50 :smile:

I am stocking up on TP2's especially since droid is running so nicely on it now.

Who wudda ever thunk it eh? :) Some things are just too funny
Happy it's working after all that!:-D

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

well its the best I can do. Sprint illegally changed the terms of my contract to prevent me from ESN swapping hardware they deem requiring a more expensive plan.

SO I make the most of the best hardware I can get access too. I will never pay more than I do now. I will cancel before paying more.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

I shuffled things up and added another topic - but it's Topic #3 because of the sufflings.

I'd really be curious to see if it does have a positive effect on the mini-resets people are experiencing in FRX07 that they did not experience in FRX06. Obviously they can still happen, but tweaking this setting seems to at least partially prevent it...

So let me know how it goes guys, enjoy!

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

I did start using the ADW launcher - and its pretty snappy now !! Half of the sluggishness has disappeared.. Thanx arrrghhh !!

I will try the others...

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Very, very helpful post, and entertaining exchange! I had been taking the wrong approach with task killers, so thanks for taking the time to put this together. These are the measures I've taken so far:
Topic 1: Switched to ADW Launcher, and speed problems related to home screen (i.e. switching from portrait to landscape & back) seem to be resolved.
Topic 2: Skipped, have extended battery so only looking for performance improvements.
Topic 3: SD readahead was somehow initially set to 256kb for my FRX07.1, so I increased it to 2048kb. 'Mini-resets' seemed to occur at same rate, typically during new app install or app update, so I decreased it to 1024kb.
Topic 4: Have played with overclocking in the past, but disabled it due to battery drain with standard battery. Turned it back on using recommended freq now that I have the extended battery.
Topic 5: I think this was the best recommendation and helped the most. I used the V6 SuperCharger Update 8 script with the recommended options (#2, #11, #17). Now I seem to consistently have 40-50Mb of free RAM, while before I only had 20-25Mb. Is there a way to make the internal taskkiller even more aggressive?
Topic 6: The "failure to boot" comment made me hesitant to experiment with this. I really like the idea, but I will need more time for proper backups before I can try this.

Thanks again for your work putting this together. I'll try to report back after a few days of use.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by auburnham (Post 2154240)

Topic 5: I think this was the best recommendation and helped the most. I used the V6 SuperCharger Update 8 script with the recommended options (#2, #11, #17). Now I seem to consistently have 40-50Mb of free RAM, while before I only had 20-25Mb. Is there a way to make the internal taskkiller even more aggressive?
Topic 6: The "failure to boot" comment made me hesitant to experiment with this. I really like the idea, but I will need more time for proper backups before I can try this.

Glad you like it! For #5, I also noticed it was extremely helpful. For more aggressive settings, look at his beta versions. Grab the newest - and set it really aggressively! I have mine on the middle 512mb setting, and it seems to work very well.

As for topic 6, it's only for apps that start on boot that you really don't want to start on boot. It's honestly not useful for anything other than that, but for me anything to speed up the boot process is welcomed!

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by arrrghhh (Post 2154253)

For more aggressive settings, look at his beta versions. Grab the newest - and set it really aggressively! I have mine on the middle 512mb setting, and it seems to work very well.

Even better! I used the most aggressive 512mb setting and I'm starting with 80-90mb+ free! Outstanding!

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

After a few days of use, I've been very pleased with the performance improvement. I've had no 'mini-resets', even with two major app update cycles, so the SD card setting must be good, or it could be a combination of that setting and increased memory.

The only issue I had was two instances of the device 'sleeping to death'. I was running an app in the foreground in both instances and let it sit long enough to turn the screen off. In one instance the device went to sleep (green LED) and would not wake up. In another instance, the screen turned off, but the LED was orange, and the screen would not turn back on. I gave the device over 5 minutes to respond in each case before pulling the battery. I will change my V6 SuperCharger Update 9 beta script setting to the mid-512 Mb level to see if that resolves the problem.

Another strange issue that I discovered is that when I switched from the 9/14/11 rootfs.img to the 10/19/11 rootfs.img my initial free memory dropped from ~81 Mb to ~43 Mb. I switched back and forth between rootfs files several times to confirm, and even re-ran the V6 SuperCharger script again with the new rootfs, but there was always a discrepancy. It was as if the V6 SuperCharger script wasn't effective with the new rootfs. I will stick with the old rootfs until we understand what's causing that.

Update: With the mid-512 Mb setting in V6 SuperCharger (and 9/14 rootfs), I'm starting with ~77 Mb free. Still very good!

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by auburnham (Post 2155017)

Unless there's a tangible slowdown, I wouldn't worry about it. You should be on the newest rootfs (and kernel), because it sounds like your LED still indicates sleep/wake status. That's been "fixed" for a little while now ;).

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by arrrghhh (Post 2155021)

I did notice a slower response with the newest rootfs, so I don't think it is a false reading. I am on the newest kernel, I've just forced the old led_regime mode because I like it better.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by auburnham (Post 2155025)

I did notice a slower response with the newest rootfs, so I don't think it is a false reading. I am on the newest kernel, I've just forced the old led_regime mode because I like it better.

Fair enough.

I'd be curious about your rootfs slowdowns - is there a particular rootfs where it starts occurring? You said you switched from 9/14 to 10/19, but there is no 9/14 rootfs. 9/2, 9/18, 20, & 30.... then 10/19.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by arrrghhh (Post 2155049)

Those were the modified dates of the rootfs.img files, so I guess it doesn't correspond to the version for the older file. How do I determine the version of the rootfs.img file? I believe it was the rootfs.img that came in the FRX07.1_Full_Bundle_20110901.zip file.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by auburnham (Post 2155053)

If you already have a rootfs, there's no fool-proof way that I can think of off the top of my head. I'd just go to the rootfs autobuild and then you'll know for sure.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by arrrghhh (Post 2155058)

If you already have a rootfs, there's no fool-proof way that I can think of off the top of my head. I'd just go to the rootfs autobuild and then you'll know for sure.

From the rootfs autobuild log and the date code of the FRX07.1 bundle, I would guess the older rootfs.img file was from 8/31. However, it could be the 9/2 version since there is a note about lowering the SD readahead buffer to 256kb, which mine was originally. The newer rootfs.img is definitely from 10/19.

Looking through the rootfs autobuild log between those dates, the only entry I see that may be related to memory is from 9/30/11: fixup /dev/block/ramzswap0 creation

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Arrrghhh,

I really like this thread... I am very tired so I may have missed it in this thread but there are a few things I didn't see that should help speed Android up... These basically center around starting with a better base... These are not Android tweaks per se but because they speed up android by giving it a better foundation I thought you may want to include them in your speed tread...

The first thing I want to try is losing less to begin with to Windows Mobile... From our thread on SprintUsers the recommendation is to start with a stripped down WM6.1 ROM. The current recommended ROM is Calkin's Stripped down ROM for Android:
http://www.sprintusers.com/forum/showthread.php?p=2640948#post2640948

Anyone disagree with this train of thought and/or have a better ROM recommendation?

The other recommendation I didn't see, also along the lines of starting with a better base, is getting a faster SD card and it may be the newer larger read optimized cards are maybe NOT better:

http://forum.ppcgeeks.com/android-tp2/147357-sd-cards-performance.html

　

Lastly, I am not a Windows Mobile guy and am confused on changing ROMs and HSPLs and such.

If anyone can throw me a bone and point me toward easy instructions to changing the ROM on my Sprint TP2 I would really appreciate it.

Re: [[Speed Improvements]] Brainstorming & Testing Thread!!

Quote:

Originally Posted by nodoze (Post 2158872)

Well unfortunately none of these would speed up Android.

1) Many have done tests with all sorts of different WinMo ROM's... and the conclusion is WinMo speed has absolutely, positively nothing to do with how fast Android runs. Gen.Y or a slim ROM will help you get to Android faster, but it won't make Android faster - hope that makes sense. Again, WinMo ROM does not effect the speed of Android.

I love how you suggest changing ROM's, but don't know how too. lol.

2) SD card speed also doesn't do anything for Android's speed. With that said, if you have a bad card with a ton of bad blocks etc then I'm sure the performance on the card would be slower. But unfortunately our phones can't really take advantage of Class 10 or even Class 6 cards speed - that's really for high-end cameras that need that much memory bandwidth to record 1080p. Again, people have done many extensive tests and the cards with the best random read/write performance (which SD cards are horrible at) were Sandisk cards. You really have to test each card's throughput on your phone to get an idea of how it'll effect Android.

As far as WinMo, you really shouldn't ask questions about it in the Android section. But it's really quite easy - flash HSPL (http://forum.ppcgeeks.com/cdma-tp2-d...w-hardspl.html) then flash a ROM.