yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] pinetreehater:
Just thought I would check back in.....

After several weeks of running Cyanogen's latest on both of my G1's, I have had a good deal of experience with both caching techniques. I have basically been carrying both phones (one on me and one in my briefcase)...and for the most part, what I do to one I do to other.

Consistently, Compcache is slower. I am not sure about the actual speed at which programs open from a cold start, but the Linux swap always outperforms the Compcache. It seems, that after sitting for several hours, the compcache gets its data pushed out of memory. This rarely happens for the Linux swap.

I am not going out on a limb and stating flatly that Compcache is inferior to the Linux swap...but for my setup, it does work consistently better. Fewer reloads is my goal.

BTW, for compcache, I am not using any script. It just runs as cyanogen prescribed it to...for the Linux swap I do use a script, but the only thing that gets tweaked is the cpu_up_threshold....it is at 35(40 stock). Other than that, both caching techniques are at 60 swappy and use 32mb.....

I appreciate all the additional feedback everyone has given on this thread....maybe it will help some user to make informed choices.
[G1 Android Development] dwang:
If you are not using any script for compcache, then thats the reason why you are seeing more reloads. By default compcache only allocates 24megs of swap.
[G1 Android Development] miketaylor00:
A couple of things. First, if you are using CM 4.0.4 it appears from my testing that the swap free notify feature is getting rid of data that it shouldn't be. So almost nothing is staying in cache for very long. This will cause reloads and basically defeat the purpose of caching. I think the CC team needs to do a little work on it.

Second, if you are using a swapiness of 60 with compcache that is way too high. You are going to fill up your compcache memory pretty quickly that way and when compcache has no more memory to deal with you it can't work.

Are you using backing swap with compcache? If you aren't then you are going to see a lot of reloads anyway. You can't use the same settings with Linux Swap that you do with Compcache. It just isn't going to work the same way. One uses compression the other doesn't. You can't expect them to run the same way with the same settings.
[G1 Android Development] dwang:
I'm going to have to disagree with this. I think a value of 30 is too low. The entire of having a swap is to have unused memory pages moved to swap instead of just freeing it.

The higher the swappiness the more aggressive the kernel will move those pages to swap. A value of 30 means the kernel isn't going to be very aggressive in moving those pages which will causes way more browser refreshes than a value of 60. If the swap gets filled it will then begin to move the least recently used memory pages out of swap to keep the most recently used pages in.
[G1 Android Development] miketaylor00:
Just because a page is not in swap that doesn't mean that it is thrown away. It can still be sitting in RAM and be reused. You want to use your available RAM. When you have a really high swapiness it is going to use swap even when RAM is still available. If the data is in RAM it will be reloaded faster than if it is in swap. If the phone needs more memory and RAM is full, it will move it to swap (either CC or linux or backing swap, CC is technically swap). The goal is to use RAM first, compressed RAM second, and swap parition third.

For Hero you want a high swapiness because you NEED to use swap often. RAM will quickly run out so it is better to rely on swap in the first place. Cupcake builds are a different story. They will run ok with only RAM. CC and swap are merely memory extensions to be used as needed. They should be configured that way.
[G1 Android Development] xdaofficeuser111:
I found that compcache has a swap space of 24MB? I do a FREE in terminal and saw this figure.

However, I have no idea why, whenever I use Mike's user.conf and userinit.sh, no matter what settings I set, once the files are in place, FREE also gives only 24MB after I restart ...

how can I know whether I have compcache / linux swap in place?
[G1 Android Development] xdaofficeuser111:
I have a swap partition of 32MB
[G1 Android Development] dwang:
Your assertion is only true when u have a lot of free ram available. On the g1 you almost never have very much free ram so its either going to go to swap or freed.
[G1 Android Development] miketaylor00:
On cupcake you have enough. On Hero you don't. Which is why I said there is a difference between the two.
[G1 Android Development] dwang:
So are you saying that running 30 swappiness will cause less browser refreshes than 60 on cupcake?
[G1 Android Development] prince.siraj:
would you say that compcache with backing swap or linux-swap only is better?
[G1 Android Development] miketaylor00:
There are too many factors involved to give a yes/no answer to that. If you have a high swapiness and a small memlimit and backing swap then you will have more reloads with 60. If you have an equivalent amount of memory allocated then it will be about the same. The difference is that with a higher swapiness you won't get the same responsiveness from what I have seen in my testing.
[G1 Android Development] miketaylor00:
Never use compcache with linux swap. It is the worst setup I have found. They do not work very well together. Either use Linux swap or compcache with backing swap.
[G1 Android Development] dwang:
I've noticed the same issue as you. The browser seems to reload less often using straight linux swap than compcache with the same settings.

I've raised this issue with the compcache author regarding data getting freed from compcache swap much faster than with regular swap. Feel free to add any additional comments.

http://code.google.com/p/compcache/issues/detail?id=39
[G1 Android Development] ultra spikey:
I've been running Compcache WITH a Linux swap since Cyanogen included compcache in his ROMs. Works way better with Linux swap. Although, I have never tried compcache with a backing swap, so I can't compare those two. I really don't even know what the main difference is between compcache+linux swap and compcache+backing swap???
[G1 Android Development] miketaylor00:
Try backing swap instead for a comparison. I will bet anything that it is faster. The difference is that with backing swap you have Compcache managing the swap file as well as the compressed data. With regular Linux swap the data has to be handed back to the OS to deal with after it is determined that it can't be compressed. It's just more efficient to let Compcache send it straight to the swap partition.
[G1 Android Development] miketaylor00:
BFS has made a huge impact on performance and there have been significant changes to Compcache since this testing was done. I think this comparision should be done again, if the OP is up for it. I'd be happy to provide suggested settings for both Linux swap and Compcache.
[G1 Android Development] dwang:
I think I figured out the problem.

Cyanogen ROMs have the vm.page-cluster value set to 0 by default, which means only 1 page is written to swap in a single attempt. Moving it to a higher value and browser doesn't seem to refresh as often.

I had played with the page-cluster value before, but didn't make the connection between that value and browser refresh until now.

These are the settings I currently use. Seems to work decently. I'll keep on tweaking it in the coming days.

swappiness=60

compcache with backing swap (memlimit=14megs backing swap=48 megs)

page-cluster=2 (writes 4 pages at a time) Setting it to 3 or higher and I notice performance problems and slowdown.
[G1 Android Development] miketaylor00:
Thanks for the info. I was noticing performance problems at 3 so I set it back to 0. I'll try it out with 2. I would recommend going higher than 14 on the memlimit though. When I push my phone really hard I have gotten it up to that on xROM. I know it is a different ROM but they are using a lot of the same stuff so I'm sure you could do it too. I like 18 for that value.

Edit: I just got my fastest benchmark pi time ever. 11.104 - I'm number 14 on the all time list now.
[G1 Android Development] dwang:
Doesn't seem like setting page-cluster to 2 fixes the problem. After running with page-cluster set to 2 for the whole day, I'm still noticing that the browser is refreshing very often even when the swap is only half full.

I'm guessing there might be some performance enhancements in donut that is killing the apps in memory more frequently than with cupcake. One thing about donut is that it stays consistently fast even after days of not rebooting.
[G1 Android Development] miketaylor00:
Either way, it seems to have helped me. I think that the consistency in performance has a lot more to do with BFS than it does with Donut. BFS is much better at managing the memory.
[G1 Android Development] WMO_Magic:
i've got a question. I'm running Evil Hero Rom 2.7 Remixed with:

#compcache related parameters

compcache{

compcache_en=1

cc_disksize=64

cc_memlimit=16

cc_backingswap_en=0

cc_backingswap=/dev/block/mmcblk0p3

partition device, swap

cc_swappiness=60

}

what would be recommended a linux swap with cc or enable the backswap.

I'm running on a Vodafone Magic so its the 32B with 198 RAM and i've gotten a 8GB Class 6 sdcard withc is formatted 512mb linux swap 1024 mb ext4 and everything else fat32 (i know the partitioning might be overdone but so be it. Dont really use 8 GB on my phone)
[G1 Android Development] gohaneri:
But in the end, with the last cyano rom, what is faster in g1 + 4gb sd class 6 64mb swap partition ?
[G1 Android Development] miketaylor00:
I don't know where to post this information so I thought this would be a good place. I hinted around about figuring out something about Compcache that no on else seemed to know. If you read the second post in the JacHeroSki thread you will know what I was talking about. If not, I'll explain it here.

With Compcache running without backing swap, the disksize is the total amount of memory that can be used by Compcache and the memlimit is the amount of memory that can be used for compressed data. When you turn backing swap on the disksize setting is ignored. The backing swap device size becomes the disk size. The memlimit was assumed to be the amount of memory that can be used by compcache for compression. But it's not. The memlimit is the amount of uncompressed data that can be compressed by Compcache. If you set the memlimit to 1GB and that 1GB of data was compressed down to 10MB, it would stop compressing data after 10MB.

Most people were setting their memlimit low because they didn't want to use a lot of RAM. So settings like 16 or 18 were very common. However, with a memlimit of 18MB you will probably only be using about 3-4MB of RAM. That is why Hero never performed well with Compache. It would chew up that 18MB memlimit just during startup. Then as memory freed up it would do better for a while and then fill up. So you would see good performance followed by lag and slow down. With JacHeroSki I set it to 48MB and it never runs out. Now BFS is a big part of that performance increase we are finally letting Compcache work the way it was meant to. And it is only taking up 6-12MB of RAM. For Cupcake ROMs I suggest setting the memlimit with backing swap to 32MB-48MB. You will see a huge improvement.
[G1 Android Development] Vlad83:
Good to know, thanks.
[G1 Android Development] IConrad01:
Has anyone else encountered this?

No matter what efforts I take to adjust the disk-size and memlimit of CompCache, it's defaulting to 32 MB disk-size and 16 MB memlimit.

I have attempted revising the userinit.sh script *directly*; I have attempted revising the user.conf file; I have also attempted to manually edit these statistics via rzscontrol.

Every time, I receive no error messages; the changes simply fail to take place.

Anybody have any ideas why this would be? I'm running Cyanogen 4.1.11.1 on a G1.
[G1 Android Development] dumfuq:
Yup. I've noticed it defaults to 16 when I make memlimit bigger than my backing swap.
[G1 Android Development] miketaylor00:
Yes and it sees your swap space as being a couple MB less than what it really is. With a 64MB swap I had to set it to around 60MB to keep it from going back to the default.
[G1 Android Development] Ohsaka:
With these user.conf settings:

*** CompCache ***
compcache_en=1
cc_memlimit=48
cc_disksize=60
cc_backingswap_en=1
cc_backingswap=/dev/block/mmcblk0p3
swappiness=30

./userinit.sh -i reports the following:

=== free ===
total used free shared buffers
Mem: 107292 103436 3856 0 1848
Swap: 62240 0 62240
Total: 169532 103436 66096

=== swaps ===
Filename Type Size Used Priority

/dev/block/ramzswap0 partition 62240 0 -1

=== rzscontrol /dev/block/ramzswap0 -s ===
BackingSwap: /dev/block/mmcblk0p3
DiskSize: 62249 kB
MemLimit: 49152 kB

So it looks like the parameters are being used by the system properly...
[G1 Android Development] :
So, few months have past and is the landscape still the same? Which option rules the speed crown...?

BTW, which is faster? A dedicated swap partition or a swap file?
[G1 Android Development] Temar:
Usually a swap partition, because:

It is a continuous space (a swap file can be fragmented).

It has no filesystem.

It does not interfere with filesystem cache => Filesystem cache can be used for real apps/files.
[MDA Compact II Accessories] drcps03:
hiiii

anybody plz tel where can i download free softwares for my htc PDA PM 200 model? recently i unlocked this t mobile handset
[MDA Compact II Accessories] Clondyke:
Try google...

...or look here:

http://www.pocketpcfreeware.com

http://www.1800pocketpc.com

and many many more. I am shure you can find a lot of other pages. ;)
[MDA Compact II Accessories] jsfojsf:
low quality post 1

i have a perfectly legitimate question for a developer forum so here is low quality post 1
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] OndraSter:
Welcome here bro.

How is it when you removed Notes and you click while incall on Notes? Because in default it opens Notes with some predefined layout and caller name.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] arjen888:
any screens?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
Thanks for the heads up. I re-installed notes, and the files shown in post #1 reflect the fix. So this is no longer an open issue.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
Thanks for the suggestion. I added screen shots, and they can now be seen in post #1.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] msd24200:
SWEET, welcome new chef, have you tried running android on your rom yet???
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gathrottle:
Another Chef and another great ROM. Tried it out and it is real good. The above material all in one place is a good thing also.

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
Post is no longer relevant. Post #1 has been updated.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
Thanks. No, I have never used Android on the Kaiser. I was tempted, but all the posts I read states that many things don't work yet; so I passed. Have you?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] msd24200:
yeah just started recently using it, was thinking of flashing a super light rom to see if there is a noticeable speed increase in android, the hero android rom i pretty buggy still but is coming along nicely, graphically it looks really good, android with wifi is excellent, bt and camera doesn't work on either tho
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ceralon:
This could be interesting. I too hate all the extra stuff in the phone that I never use. I'm going to try it. My biggest complaint about WM is the threaded SMS -- it seems over time it takes longer and longer to load messages. I think im going to try your rom.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] msd24200:
clean them out from time to time, i couldn't live without threaded sms :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
Updated: Bare WM 6.5 23009 Cooked ROM with unnecessary items removed.

Updated: Bare WM 6.5 23009 Cooked ROM with unnecessary items removed

I have updatd the "Bare WM 6.5 23009 Cooked ROM with unnecessary items removed" files.

- There is now two flavors (Vanilla & Chocolate)

- Screen shots of both flavors are included

- Description of what is included in each flavor is included.

- Download files updated.

- 'Notes' problem (described in post #4) is solved.

Enjoy.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] xxbabiboi228xx:
Just what i was looking for a 6.5 Bare bones rom running android hero sense ui as well
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Chaisu:
This is exactly what I want!! I was going to try to develop a very similar ROM but you've done all the work for me! I have so much junk on my phone that I don't use, so this will be perfect. I'll flash it tomorrow, then load of spb mobile shell, pocketplay, iGO, a few others and I should have a nice clean setup for once!

btw, great post. easy to understand and all the files are very helpful.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gelf:
Awesome...

just Awesome.. thank you very much :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
I used Spb Mobile Shell 3.01 when I was using WM 6.1, but after switching to WM 6.5 I realized that if I put a little bit of work on the WM 6.5 Today Screen (Titanium) I could completely get rid of spb Shell, saving some RAM in the process and some confusion as well.

I encourage you to give the new Today screen a shot. I use the following plugins on my WM 6.5 today screen:

Clauncher - You can get 3 Launchers (for up to 9 applications) from the first post, and an additional 3 Launchers (which I created) on post 163 (page 17)

http://xdaforums.com/showthread.php?t=514490

Comm Manager

http://xdaforums.com/showthread.php?t=513747

Titanium Notifications - The original one had some bugs. I fixed it. Get it from post #146.

http://xdaforums.com/showthread.php?t=513431&page=18

Showaco Titanium Weather

http://xdaforums.com/showthread.php?t=487090

Favorite People

http://xdaforums.com/showthread.php?t=506221

Artesea Twitter

http://xdaforums.com/showthread.php?t=511919

I think you will like the Titanium screen once you have the above items installed.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] xxbabiboi228xx:
Just curious does this rom have decent battery life?

Witschey
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
Your question is not easy to answer because it depends on how you use your device. The battery will drain quickly if:

- You keep the light on all the time.

- You are constantly connected to MS Exchange.

- You do a lot of web browser use or play a lot of music/video files.

- You keep the 3G connection on all the time (I switch to GSM/EDGE most of the time and only use 3G when I really need it)

- You keep both GSM/EDGE or 3G on while also having WiFi on.

So I am afraid I can't answer your question. For me battery life is not an issue as I put the phone in the charger every time I don't use it. I even have a charger in the car for while I am traveling.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] xxbabiboi228xx:
ok thanks but very true on the answers you gave me I agree 100%
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] siulmagic:
dude thx so much, this is what iv been looking for, a clean 6.5 rom omfg i love this
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mb:
GREAT!!!

I've been after a ROM like this for some time. I've been using hang.tuah and 888's masterpiece, but it is no longer developed.

Thanks for doing this.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] daigoro64:
Fully agreed.

Thanks again for sharing your work.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] obaz:
this rom miss microsoft task manager. dutty`s one more advanced, but it handle task operation bad. few times it just hag`s, when mikrosoft one works well.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] daigoro64:
No access to Wireless LAN property page

Using chocolate flavor (6 buttons CommManager), the standard way to access Wireless LAN property page (from Comm Manager/Settings/Wireless LAN) is not working. Without this page you cannot set, for example, the power transmission for the wireless card.

Update: this issue has been solved by witschey in v10018, released on Aug 15, 2009 11:50pm UCT
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] chteh0721:
if want to get rid of chome, is it possible ?

which are these files that i need to remove ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] OndraSter:
All CHome from SYS and maybe ConfettiCore, but I wouldn't risk it. Also Bronze (this one maybe not, I'm not sure), Bronze_DPI_96 and BronzeNonEA
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mcfarlan:
MSD...is not really all that buggy....BT and Camera does not work but after configuring it propoerly it will grow on you. If there was a way I would post some screen shots in the other thread but, I sync with google for contacts and calendar, have downloaded some stuff from Market, YouTube is faster than WM (picture quality not so hot), weather works I mean there is enough going there to make me want a Hero as my next phone :) I am going to try it on this ROM and will probably cry if my setup breaks :(
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
What do you mean by it handles task operations bad. Could you explain?

Only the chocolate flavor has the advanced task manager. The vanilla flavor does not. Even though I tried to remove the build in task manager completely I have noticed that if you go into the windows directory on your PPC after installing either the vanilla or chocolate flavors, you will still find the original task manager (perhaps only part of it; not sure). In the worst of cases you can cook your own ROM with the files I made available and move the original task manager back. The files I removed are available for download and you can easily move them back. I kept the same directory structure so you know where they go.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stylez:
Just wanted to say welcome, only just seen your post congratualtions on release :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
Solution has been incorporated into a new ROM. Please download the most up to date files in post #1 to solve the issue.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
If by chome you mean the Today Screen (also called Titanium), I am afraid that I have never tried to remove it (because I like it!)

However looking at the SYS folder you could try to remove:

\Sources\SYS\23009\CHOME

\Sources\SYS\23009\CHOME\CHome_DPI_96

\Sources\SYS\23009\CHOME\CHome_Lang_0409

and maybe also

\Sources\SYS\23009\Bronze_DPI_96

\Sources\SYS\23009\BronzeNonEA

be particularly careful about Bronze_DPI_96 because it contains a file called bronzeres.dll which I think is used elsewhere (outside of the Today Screen)

The 'Bronze' directory that OndraSter mentioned is already gone from this build. So YES you would have had to replace it if you were using some other source files, but with my source files that one is long gone.

Now here goes my disclaimer. Beware that I have NEVER removed the Today Screen myself, so I can't assure you that it will work. If it works, you are likely to end up with two shortcuts on the start menu that point to nowhere. A Today shortcut on the startmenu that you can delete by going to "Windows\Start Menu" on the PPC (using any File Explorer), and one inside of settings that I don't think you will be able to delete, because the shortcuts inside of the settings menu are created in a different way which I don't quite understand.

Good luck.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] daigoro64:
This page seems to be in WLANSettings.exe.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] witschey:
Issue is solved. This post is no longer relevant.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] daigoro64:
I'll do it. Thanks again.