yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] pmos69:
further tweaks

Warning: This only applies when using the latest rootfs (with 80GB compcache and other tweaks):

http://www.4shared.com/file/128010689/3abc9ae7/rootfs-2009-08-26-CompCache32MBswapSquashFS.html

and latest zImage (26-08-2009):

http://www.4shared.com/file/127944087/4f4cf254/zImage-2009-08-26SquashFS.html.

Latest zImage responds a little different to vm settings than previous kernels, so this may have very different results with other files.

This seems to have a positive effect (when using the files referenced)

echo "10">/proc/sys/vm/vfs_cache_pressure
echo "100">/proc/sys/vm/swappiness

Compcache in-memory swap usage with these settings tends to keep between 55MB and 65MB most of the times and system responsiveness seems improved.

For reference, the default value for swappiness in the referenced rootfs is 75 and the default value for vfs_cache_pressure is 100.

Other tweaks allready applied by the refrenced rootfs, besides the 80MB compcache are:

echo "0">/proc/sys/vm/page-cluster

echo "5" > /proc/sys/vm/laptop_mode
echo "1500" > /proc/sys/vm/dirty_writeback_centisecs
echo "20" > /proc/sys/vm/dirty_ratio
echo "10" > /proc/sys/vm/dirty_background_ratio
[Touch CDMA Android Development] enatefox:
pmos69, can you tell me/point to the lmgtfy.com on what the new kernel has? I get what you wrote is good for rootfs.img but I wanted to try DMA wifi again and wanted to see where it was sourced from. All the images with wifi I uploaded are using the old one because I haven't had good luck but that was when it was brand new.

I meant going to wallpaper settings or Album which it opens anyways. I've got them all and I just did a fresh install to try to see if I can get it faster than you've seen. When it did happen, it would go away when I hit back then go back and repeat a couple of times. It seems to get exhausted reading all of the files and just continues after x seconds. They're in /sdcard/mydocs/pics/walls/ and a couple in DCIM. I have an awesome $15 at the time 2GB card that's nothing special. Is anyone else able to run Hero as fast as the video I made? I'm about to make one when I find my camera actually using it to set wallpaper, web browse, etc.
[Touch CDMA Android Development] pmos69:
lmgtfy.com?

http://tinyurl.com/n9somh

:)

Or go directly:http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue

About wifi, I guess this is still valid, no? http://xdaforums.com/showpost.php?p=4350730&postcount=256

And I haven't look at this, but it seems pertinent: http://xdaforums.com/showpost.php?p=4222572&postcount=1
[Touch CDMA Android Development] sshark:
Hero 1.6 Version 1 is most stable so far as far as Rosie is concerned.

I have following config with no lag

Home 1: [empty]

Home 2: Stocks

Home 3: Shortcuts + GPS widget

Home 4: Pure calendar + Dual Clock + two shortcuts + 2 Android Organizer Live Folders

Home 5: People + Shortcut

Home 6: Twitter

Home 7: Album

----------------

Only problems are sms are unreliable and web connection switches between 3G to dial up to no connection sometime.

-----------

There is much talk about SD card and its speed, I am using stock 512 mb card that came with Touch when I bought the phone.

I was using class 4 8gb and found that performance on smaller card (512 mb) is much better than the bigger one.

Let me see if I can post a vid, I have a miniDV cam so don't know how to move vid from miniDV to PC.
[Touch CDMA Android Development] enatefox:
I'm trying out Missed Call (free from Market) to see if/how it works. It's a standalone call/SMS/whatever listener that you can set the LED color/flash and vibrate, ringtone, etc. Just not sure how well it works yet. It would be really easy to fix the notification stuff with it.
[Touch CDMA Android Development] pmos69:
su

Enatefox,

Using JACHeroski1.6r2a with wifi you provided, It seems applications that require su access (like SUFBS) don't work correctly.

Tried to install SuperUser from market but it doesn't install.

Can something be done?
[Touch CDMA Android Development] enatefox:
That's what I mean, addisu has his rootfs.img to fix overheating so I'd need to dig and add that to the one you posted or would DMA be in them already?

It does not work right because it's a sqsh image for some reason. I noticed but didn't bother much more since Zenulator's doesn't have it working either. The permissions are correct but maybe the 4 in chmod can't setuid on the FS? You can use, should be able to at least, /bin/su for direct root access which should be fixed in rootfs.img on releases I think.
[Touch CDMA Android Development] pmos69:
The one I posted is based exclusively on your files (the ones you sent me before).

FYI, just tried to make a version replacing your files with the ones in addisu's rootfs and it does not work.

Wifi turns on, then says it can't scan and turns off again.

(I think I saw this behaviour in another of the posted builds... don't remember which one...)

I think you should take a look at this :) (You are the right person to do it)

Yes /bin/su works (thanks to you)

It's just that this behavior affects other applications and /bin/su does not solve that. :(
[Touch CDMA Android Development] enatefox:
Ideally, /system/bin/su should symlink to /bin/su and /bin/su should be set 4755. I don't know if that's how rootfs.img's have been pushed so I've just hardlinked it properly in /system. This fails with the file system type I suppose. That's the solution though.

I don't know if things have been forked with DMA work and the rest but I'd rather use it-- it was just in testing when I tried it. You're saying with the zImage you posted, his rootfs.img and the system.sqsh I uploaded it didn't work? I have the original wifi files there and they probably override what's in rootfs.img like su does. If that's all then it's easy to fix, same solution as before. Just symlink back to the rootfs.img files or change PATH. If you have a good setup that works, let me know as I'm trying to do the same.
[Touch CDMA Android Development] zenulator:
in the latest build i'm working on i placed symlinks to /bin/su in /system/bin and /system/xbin. /bin/su is in rootfs.img so you can just mount that and chmod it yourself. i have a build right now that has the advanced hero themed launcher included. i also took out a lot of stuff out like i did in pureblack. all the way down to replacing the browser with better browser and removing flash. basically it's going to be a mix of hero/rogers/xrom with rosie/touchflo still included. i'm going to modify the init.hero.rc in rootfs.img to not load wifi when hero starts so that way vogue users should just be able to use the wifi enabled images and not have it lockup when it first starts plus it should load faster for vogue users because currently a lot of startup time is waisted with hero complaining about not being able to load the wifi driver when running on the vogue.
[Touch CDMA Android Development] SkywalkerPD:
Superb Android version!

Is there any way to sync my contact from SIM to contacts? I see this is working in the Zenulator's JACMANxROM1.4r3 vogue port, but not in this build.
[Touch CDMA Android Development] Brshk1:
If you have a google account, you can import your contacts from the SIM with JACMANxROM1.4r3 or other working version and then sync them with your account.

This way, you will never have to import them again from SIM when trying other versions, as they will be synced from Google automatically. There is a similar procedure from Windows Mobile, but you have to be careful if you don't want to erase them accidentally.
[Touch CDMA Android Development] enatefox:
That's what I do instead of SIM contacts too. It's easier than trying to fix it.

Zen, can you tell me (maybe PM) how you removed flash? I'd like to keep up with the latest but want to be able to have that. It's weird about su on a squashFS so at least it's an easy workaround to symlink to rootfs.img.

I haven't really gotten a chance to play with Missed Call app but it may work or at least we can glean some info on how it works since it uses a standalone service to handle incoming events.
[Touch CDMA Android Development] zenulator:
I'll keep the flash libraries in so you can just replace the browser.apk with the original apk and odex.
[Touch CDMA Android Development] enatefox:
aww... it's browser dependent? I was hoping I could use it in Opera too. Oh well, it's good enough
[Touch CDMA Android Development] zenulator:
Have you tried using opera in hero to see if it works with flash? I doubt it will but it never hurts to try. Truthfully I don't like the hero browser and the only time I notice flash is with ads. I did try to play bloxorz but it wasn't a very smooth experience same with watching a flash video.
[Touch CDMA Android Development] enatefox:
No, hadn't tried it but have issues with imeem mobile has been flaky and I need the new flash for the site. Speaking of, I've got a hosts file full of goodies, copied from my laptop that blocks a metric ton of ads. If you don't mind "page cannot be displayed" in place of the "you've won an ipod and aids" banners, you can get most of my list here and I add extra ones from Bluetack. Just, change 127.0.0.1 to 255.255.255.0. People commonly put localhost but that ends up bombing it with requests when resolving to a fake IP is much better. Works wonders.
[Touch CDMA Android Development] natefish:
Hey enatefox, I finally got gscript to find this file once I ran a fresh data image. When I run it, though, it tells me the "sleep 500" line is a bad variable. What am I doing wrong? Thanks!
[Touch CDMA Android Development] enatefox:
How did you save the file? In Windows? It might be format issue. I'd double check it in Android or Linux to make sure it's all good. If it looks like the one I posted it will be okay. I'm working on a rootfs.img tweaked just a little to do that, have the hosts file I mentioned, compcache over 100Mb, etc. so it won't matter then.
[Touch CDMA Android Development] zenulator:
Uploaded a new test build. It's faster than JACxHeroski1.6r2a. Use it with the rootfs.img I posted at vogue-hero. It's cramfs. So use the regular kernel at vogue-android. The rootfs.img I posted is about the same one as the one thats posted at vogue-android except it has a few hero tweaks for vogue users without wifi. I also added the hero themed advanced launcher so when you switch to the regular android home screen you still get that hero feel. I also included some widgets and apps like the flipclock weather widget, better browser, different youtube.apk etc...and symlinked su to /bin/su. Let me know how it works out.
[Touch CDMA Android Development] enatefox:
And in rootfs.img, the tweaks are just for Vogue users? Should I keep the 8-26 one pmos69 linked to then for Kaiser? About to try now
[Touch CDMA Android Development] natefish:
SWEET! Yeah, I formatted it in Windows. Is there a good editor for this kind of thing in Android? Not sure if Astro File Manager will let me change the extensions.
[Touch CDMA Android Development] zenulator:
The new rootfs.img doesn't try to load wifi or bluetooth at start since these aren't needed for vogue. Other than that it has the same ramzswap parameters and some other stuff I thew in there.

page_cluster=0	# default 3, (0 since CM3.9.6+)
laptop_mode=0	# default 0
dirty_expire_centisecs=3000	# default 3000
dirty_writeback_centisecs=500	# default 500
dirty_background_ratio=5	# default 5
dirty_ratio=10	# default 10

I don't know how well the above works but it's some things taken from cyanogenmod.
[Touch CDMA Android Development] enatefox:
those dirty writebacks...

If it doesn't try to load it at start that shouldn't affect it when I manually start it you think? I'm perfectly fine with it disabled at start if that's the case. 8 hours > 2 hours of battery life
[Touch CDMA Android Development] zenulator:
Give it a shot. I didn't add the wifi stuff to the latest test image. So you might want to play around with it first. You can also add back the htc browser by removing the existing Browser.apk and inserting the Browser.apk and Browser.odex from JACxHeroski.
[Touch CDMA Android Development] arleybarros:
testing on my niki100 (i know, its not this topic, but i'll give it a try).
[Touch CDMA Android Development] radem205:
The test builds works great and is faster I think! Great job. But the weather/flip clock doesn't update (internet is working) and the weatherwidget from hero crashed when you select a place.
[Touch CDMA Android Development] arleybarros:
the same here, its a lot faster...

anybody else heaving problem with "com.htc.launcher"?
[Touch CDMA Android Development] enatefox:
The problem with the weather widget is a known issue and it's specific to that, not the build. I haven't found better and I don't use it for that reason. I mean the Weather Widget Donate app, not Hero's
[Touch CDMA Android Development] pmos69:
Did you make a mistake in the post?

laptop_mode=0 will reduce the life of your sdcard and should not improve performance.

laptop_mode, dirty_expire_centisecs, dirty_writeback_centisecs, dirty_background_ratio and dirty_ratio are usually tweaked to prolong the life of flash media, and not for performance reasons.

In the post, you've set them all to their default values, so no change. Are you sure that's what you did?

page_cluster=0 on the other hand, will improve performance.
[Touch CDMA Android Development] natefish:
Latest Cramfs hero image...

Initial test with fresh data image was REALLY quick and responsive. Touchflo reloaded with less resources being used than in the squash. I only had about half as many widgets running as I did in squash and no flip clock either. Is there a difference in how much one can handle over the other?

After running for a while, seems just as good as squash overall except for more Touchflo reloads.

DEFINITELY FASTER AT RECEIVING CALLS!!! I was about to switch back to squash and then thought better of it for that reason alone. Great job with that. This build with enatefox's updated rootfs he is working on may be the perfect combination.

Oh, also, it didn't read my "Resource" folder. At least nothing showed up when I tried to change my ringtone.
[Touch CDMA Android Development] zenulator:
Actualy I did. How about we just call a script from the sdcard that way anyone can tweak their own settings including compcache/swap. I just used the defaults what do you suggest?
[Touch CDMA Android Development] pmos69:
you're the cook :)

we just taste the result ;)
[Touch CDMA Android Development] toubeau:
+1

a "settings.txt" file could be great and an easy to tweak solution... but for sure not inside default.txt itselft
[Touch CDMA Android Development] zenulator:
we'd just have init call the userinit script on your sdcard so you can edit it to your liking. compcache, swap, renicer, etc...
[Touch CDMA Android Development] pmos69:
For testing and development, I think it's a great idea. Avoids having to rebuild rootfs.img for every test.

As things get more stable and "production ready", that call could be eliminated (avoiding the inherent security hole)
[Touch CDMA Android Development] zenulator:
i see you ask the question about elevator=noop in the kernel thread. did you hear anything back on that?

something like...

cat /sys/block/mmcblk0/queue/scheduler

noop [anticipatory]
[Touch CDMA Android Development] pmos69:
not yet... let's see...

btw, what's the result of that cat (I am switching sdcards and can't boot right now :o)
[Touch CDMA Android Development] zenulator:
ok i'm almost done the userinit. i just tested it and looks like it's almost all good. a couple errors i'll work out before i post it.
[Touch CDMA Android Development] enatefox:
Can someone explain if using deadline scheduling would be useful/relevant as well? http://www.brighthub.com/computing/linux/articles/9170.aspx

noop is supported and anticipatory is the one currently in use (at least with 1.6r2a that I'm using at the moment). How can I benchmark the performance gain? Would this be a vmstat thing? I don't know (yet) how to make sense of it's output besides "numbers go up and down" but I can post the results.

Glad you asked about it-- first I've heard of this stuff before except vague references to real-time OS.
[Touch CDMA Android Development] pmos69:
noop would definitely be the one indicated for our devices. It's just a FIFO with no extra processing involved.

It's also the one indicated when using linux under vmware for essentially the same reasons.

There are 4 different elevators in Linux, I think. All the others try to optimize disk access so physical disk heads can be used in an efficient manner.

As you can imagine, this takes some processing and is of no use with sdcards and other flash media.
[Touch CDMA Android Development] enatefox:
Okay, the link I sent is in regards to SD but I know that SD has its own management not limited to wear-leveling and all so I don't know why deadline was recommended. I'm testing noop at the moment with vmstat. It's not quite the same as familiar Unix but I'll do some brief testing with it. Since I've already got ADB connected. I'm not able to save vmstat output though. Any idea? > and | tee are not working-- empty log file.
[Touch CDMA Android Development] zenulator:
Don't know. I did some googling and I've seen both noop and deadline recommended for sdcards.
[Touch CDMA Android Development] pmos69:
here's a good reference:

http://linux.com/index.php?option=com_rubberdoc&view=doc&id=12&format=raw

As you can see, all the other schedulers deal with the disk's moving head and the spreading of data blocks on disk. This has absolutely no usefulness in sdcards.
[Touch CDMA Android Development] enatefox:
Nice. I just did a benchmark with vmstat after setting noop and made a video. Might upload it if someone cares. Long story short, here's the results after using the same 1.6r2a I had in the video but with 101,916KB of compcache glory. Before running it, I had ~40MB of compcache in use. After, 62MB used.

I did noop first then back to anticipatory. Maybe it would make a difference. Seems like mixed results. Maybe someone can do a more thorough test

Here are the two files though I don't know if one's redundant or not:

cat /sys/block/mtdblock0/queue/scheduler

cat /sys/block/mmcblk0/queue/scheduler
[Touch CDMA Android Development] natefish:
On the latest cramfs test build:

2nd fresh data image: still no resources being read from SD card. Market works, albums only partially load. Still fast at receiving calls.
[Touch CDMA Android Development] pmos69:
Confirmed: adding elevator=noop to default.txt changes the system wide default scheduler.

There are further io scheduler parameters that could probably have a performance effect:

/sys/block/mmcblk0/queue/nr_requests

and

/sys/block/mmcblk0/queue/read_ahead_kb

...
[Touch CDMA Android Development] tatnai:
using the latest test system.img/rootfs. disabled sense UI, and it runs pretty fast initially. much faster startup as well, creating new data.img. I've been dying to use the new facebook/email/text integrated contacts, the new album with facebook/flickr integration, etc, but have always given up because hero was too slow and didn't like the default theme. This is a great combo for me. album works, downloading from market works, pro paint camera works, resources are available (ringtones, etc).

Only issue was that it slowed down after opening up a few programs. I noticed that it did not create a swap file on first boot as I've had happen before, so I'm running without swap. Can I just dump the 32mb swap.fil file into my SD root, and will I then be good to go, or do I have to do something else? after dumping in the swapfile, booting up and using a few programs, this is still definitely a touch slower than the latest JAC xROM.

Only other note is that the long press function of popwer to rotate works, but not long press camera to open the application manager. Also, with all the hero builds, even after disabling auto backlight, I can't seem to get any backlight program (backlight!, brighteriffic, brightness level, etc) to be able to turn the backlight up or down. It acts like it works for a split second, then goes back to what it was before. Opening up the backlight setting, it immediately jumps to whatever my last action with other programs had set it to. Weird; has anyone had this work for them?
[Touch CDMA Android Development] enatefox:
tatnai, go to Settings and disable the auto backlight. It's a feature not on our phones like orientation. Disable and you're good. It took me a minute too to figure that out since it's not in ION or Cupcake. I have over 100MB of compcache with no swap file. When it slows, what does "free" say is being used? You should not be tapping it out with "a few" programs.

I just finished doing some tweaks to rootfs.img and getting wifi on the new test image. About to boot it and thanks to zenulator and pmos69 for the talk about settings, I'm putting them in like laptop_mode=1 and will see how it works out. Renicer will be automatic too if I can subtract my usual suck and have it work for once..
[Touch CDMA Android Development] tatnai:
I did disable the auto backlight, didn't work, rebooted, still could not change backlight.

Even after dumping in the swap file, i'm waiting seconds for responsiveness after a few min of use when opening albums, messaging, calendar, etc. I did add elevator=noop to my default.txt as well.

I take it "free" is a program? will look into this.
[Touch CDMA Android Development] enatefox:
free is a basic Unix tool to show memory usage. Just type it in a terminal. When I made the video using JACxHeroSki1.6r2a, I had about 45MB compcache in use and about 40MB or so free. I since upped compcache to over 100MB and it's just so much better than that was.

Can't wait, about to try the newest test image with my usual stuff but with some new things too. I'll run Benchmark on it then and compare it to the last one. From the feedback, I might need another video. That thing got like 500 views within 2 days.
[Touch CDMA Android Development] zenulator:
open up a terminal app and type

free

it should show how much memory is being used and how much swap is being used as well as how much is free. i had to use taskiller to kill off some tasks to bring it back to life. plus the htc music app eats hero alive. as nice as it is it will spike the cpu and slow everything to a crawl. i don't think i had this big of a problem with the htc music app with the pre-update heros.

as for swap i'm working on a userinit type configuration where you can just edit a txt file like the default.txt and choose if you want compcache or swap plus tweak a couple other settings. it should be done tomorrow. i'd put out what i have tonight but it's not finished. but if someone wants to add something to it or fix some things. they can have at it.
[Touch CDMA Android Development] tatnai:
free:

Swap: used 17584, free 64332.

Mem: used 97088, free 1732.

Still feeling slow. Should more of my swap be in use? there are definitely periods where things open fast and everything feels responsive, but then I don't know what happens. I can go straight into messaging with no lag after opening the first time, then after a while it takes a full 5-6 seconds to open it up.
[Touch CDMA Android Development] enatefox:
Zen, can you help me get renicer working? It should be fun/simple for us to get the custom settings going and if you/we could add a setting to specify compcache/swap size that would be perfect. How are you parsing the file? Grep or similar? I couldn't decide on a good way to do it. Then, renicer.sh in /bin wasn't "found" at bootup for me either so it's probably my fail at work.

That music widget's a killer for sure unless you have yours running right.

17MB is a little low to say it's running slow. Get it up to about 40MB and you should be golden. Simply setting wallpaper, going to the Market, whatever should shoot it up real quick. That should ensure Touchflo among others is included in swap and it should take off from there.