yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile General] skyler17:
I would also love to know. Plus how to get push internet pages.
[Touch Pro2, Tilt 2 Windows Mobile General] NotATreoFan:
Have you tried this typing Opera:config into the address bar, and then selecting the option to make it the default browser?
[Touch Pro2, Tilt 2 Windows Mobile General] Arcarsenal:
Thanks for the config tip. I tried this a few times but Opera never seems to save the settings after I exit. I make the change, save it, & close Opera. Then I restart, open the config screen to confirm the change but the box is still unticked. I might have to edit the .ini file and I don't have time for that at work at the moment. Any other ideas?
[Touch Pro2, Tilt 2 Windows Mobile General] plastikuss:
Have you tried to use the no push internet to really close opera? It seems you doesn´t closed it, as it has not saved
[Touch Pro2, Tilt 2 Windows Mobile General] Arcarsenal:
Not sure what the issue was but I got the settings to stick finally. All of my links now default to Opera except of course TF3D. Thanks for the help.
[Touch Pro2, Tilt 2 Windows Mobile General] HeavyComponent:
Hey, you mind sharing what you did in case someone else has a problem? :D
[Touch Pro2, Tilt 2 Windows Mobile General] buttsbuttsbutts:
Which config category is it under? I expanded all of them but didn't see a default browser box?
[Touch Pro2, Tilt 2 Windows Mobile General] Arcarsenal:
go to opera:config, navigate to the "Install" category.

Check Browser First Time Launch and press Save.

Exit Opera, then restart.

Might have to do this few times because it took a few tries to get it to stick for me.
[Touch Pro2, Tilt 2 Windows Mobile General] dwny:
Worked 1st time for me....Thanks
[Touch Pro2, Tilt 2 Windows Mobile General] jim_0068:
damn it, not working for me. Everytime i exit opera it resets even BEFORE i restart the phone. I have tried 5 times now.

Any other way?
[Touch Pro2, Tilt 2 Windows Mobile General] jayr04:
same here :mad:
[Touch Pro2, Tilt 2 Windows Mobile General] wonghyf:
try this cab.
[Touch Pro2, Tilt 2 Windows Mobile General] jim_0068:
Unfortunately this cab didn't work either, however i can't un-install it. It isn't listed in the remove programs area, do i need a registry editor to get it back to normal?

Thanks
[Touch Pro2, Tilt 2 Windows Mobile General] jayr04:
I have no idea why this works but immediately after I saved the setting, I went a random website in opera and the setting stayed.
[Touch Pro2, Tilt 2 Windows Mobile General] HeavyComponent:
Not working for me either, I gave up on it. :(
[Touch Pro2, Tilt 2 Windows Mobile General] ambanna:
This worked great on my new HTC touch pro2. I clicked on an email link and it took me to the opera browser and opened the link.

What does it change exactly on the registery, and how to revert to IE just in case?

Thanks a million.
[Touch Pro2, Tilt 2 Windows Mobile General] hsidorsky:
I cannot figure out where to find the Opera:Configure setting? :confused:

Thanks in advance,

Howard
[Touch Pro2, Tilt 2 Windows Mobile General] iseedeadpeople:
open opera type in address bar opera:config
[Touch Pro2, Tilt 2 Windows Mobile General] mynlal:
This migt be helpful, once you click on the option to make opera the default browser, go to options and hit exit, opera will ask you if you want to exit or minimize, just hit exit. this way it saved the settings for me.
[Touch Pro2, Tilt 2 Windows Mobile General] alabij:
This works.

http://xdaforums.com/showthread.php?t=550647
[Touch Pro, Fuze General] 427 c6:
My friend hates his Sprint Touch Pro and blames me 4 selling him on HTC.

If anyone can offer any help or fixes, I would greatly appreciate it.

I am going to e-mail him a link to this thread.

Thank you.

The following in quotes is the e-mail he sent me.
[Touch Pro, Fuze General] dwizzy130:
Put Juicy 8 on it and it's a whole new experience.

dwizzy130
[Touch Pro, Fuze General] hyachts:
I can do all these things by default in the stock WinMo contacts on my HTC Fuze :confused:

Know nothing about the Sprint GPS nav app (I assume that's what he's using?) but Garmin Mobile does this, and I suspect most other GPS nav apps do as well.

As far as crashes and battery usage go, the only fix is to flash a different ROM without all the provider bloatware. Sounds like most of his gripes are related to Sprint's implementation of the device, not about HTC or the device itself. In any case, he'll probably never be happy with it - tell him to get an iPhone where he can blithely ignore all the missing features and lack of flexibility.
[G1 Android Development] pinetreehater:
I've been plugging away for the last several weeks trying to decide if CompCache is making my phone faster or slower. I've always been happy with the pure Linux swap, but everyone seems to be on the CompCache bandwagon.

I have installed compcache many times, with all different sorts of settings. No matter what, it always seems to make my phone slower. I had to prove it. However, subjective statements of opinion are not going to carry any validity in this forum. So this is what I did:

Round 1 CompCache vs. Stock

First, I installed a fresh copy of CM 3.6.7 on both of my G1's. On the black one, I installed CompCache 0.6 via userinit. It also had a Backing Swap (not linux as the video states!) of 32mb. Swappiness was set at 20. NO OTHER SETTINGS WERE TWEAKED.

On the other phone was a pure installation of CM 3.9.7. For the stress test, I alternated between a pre-loaded webpage(Valdosta.edu, which is graphics heavy but also has a very high speed connection) and SHERPA.

I Chose Sherpa because it tends to cause the browser to reload by pushing it out of memory or cache.

I filmed the whole thing and you can view it here.

I know the filming kind of sucks, but bear with me. In short, THE PHONE WITHOUT COMPCACHE WAS NOT ONLY FASTER, BUT WENT LONGER WITHOUT NEEDING A RELOAD.

Round 2 Stock G1 vs Linux swap enabled

For the next test, I used the same two phones and ROMs. On the Black phone, ONLY THE LINUX SWAP WAS ENABLED. On the white phone, I had no additional caching (stock CM).

You can watch this video here. IN short, THE LINUX SWAP ENABLED PHONE WAS FASTER THAN STOCK CM 3.9.7

This video is 7 minutes (AND yes I was smoking a cigarette) but I actually show proof that one phone is stock and one has only Linux swap by showing the ADB output of userinit(something I forgot to do with the first video).

Watch these videos and you cannot help but wonder if Compcache is slowing our phones down. Having two phones, I have tried many many times, and Compcache always makes the phone slower.

So to sum it up, a purely stock phone was faster and required less reloading than one with CompCache. However, a phone with Linux swap was faster than stock....so Linux>Stock>Compcache

In fact, for two days I carried around both phones. Whatever I did to one, I did to the other. The compcache enabled phone was ALWAYS sluggish compared to the Linux swap phone. I mean it would be fast at first,but always returned to being sluggish.

I submit that these videos don't PROVE anything. They just bring the question to light so that smarter people can actually figure out why Compcache is bogging our systems. And for those that say their unit flies with Compcache, I say you should try it with only the Linux swap.
[G1 Android Development] alapapa:
I tend to agree...all things being equal, compcache w/ backing swap performs worse in the long run than does just a linux swap partition.

my anecdotal experiences, of course.

& that's not to say that some compcache / sysctl config out there won't make it outperform the run of the mill swap partition

nice to see some real experimentation on this issue
[G1 Android Development] pinetreehater:
Thanks. I wish I had a nicer setup where I could film better.

I really believe that compcache is sucking the life out of our G1s...at least in it's current configuration.

I know there is going to be unbelievers....but that's ok too. To each his own.
[G1 Android Development] jubeh:
i still dont like the implementation of a linux swap partition on the sdcard though. It brings about issues not only with bus bandwidth but also the eventual degradation of the sdcard.

I think a good compromise that frees up the sdcard would be to make a change to the nand partitioning and set up a 24mb partition along with all others to be used for swap. This would mean lessened life on the nand rom instead, but we flash so many roms per week, we're killing the phone already anyway.
[G1 Android Development] huanyu:
For memory intensive applications, Compcache is definitely slower than stock, as it requires additional cpu time to decompress the data and compress the data that need to be swap. Plus additional fetch and store time to main memory. This incurs additional bus transactions. The SD as backingswap increase the bus arbitration delay ( you can also say the bus architecture is the bottleneck for G1 with CC in some situations). Overall, slows down the phone. However, for small applications, you may find it faster. so its really depends the how you use the phone.
[G1 Android Development] cyanogen:
Can you repeat your experiment with CM-3.9.9.1? There is a new helper patch I added to the kernel which improves the performance of compcache. This is the main reason why I enabled it by default.
[G1 Android Development] 51dusty:
seems easier/cheaper to burn a $15-$20 sdcard than the non-replaceable(?) nand flash in the $400 phone.
[G1 Android Development] pascanu:
I seccond that request. 3.9.9.1 is the first build I can really feel compcache making my phone faster linux-swap (same swappiness, i.e. 35 in my case).

Thank you for taking the time to do such a thorough test!
[G1 Android Development] Goog1e Phone:
How do you get compcache to work? Do you have to partition your SD card 3 times? 1 for Fat32. 2nd one for apps2sd. and the 3rd for compcache? I'm confused...can anyone help me?
[G1 Android Development] Lollipop_Lawlipop:
Huh?

The ram on any electronics is designed for a lot of read/write operations...

Compcache is automatic with CM-3.9.9.1. 2 partitions: FAT32 and EXT2/3/4
[G1 Android Development] miketaylor00:
I think some of this is dependent on the ROM and how it is written. Also, you probably didn't have Compcache configured optimally. I made very minor changes to the settings and it made a significant difference in performance. Read through the xROM thread if you don't believe me. Moving the Swapiness from 30 to 28 made an improvement. Who would have thought that? If you were at 20, I'm sure you have problems because at 24 it was really slow for me.

Edit: On the ROMs, I did similar testing with xROM and I found that Linux-Swap was much slower all around on that ROM. I didn't try to tune linux swap like I did compcache because it was so bad to start with. I suppose I could do the same thing I did for linux swap to see if I can get an improvement from it. It's possible that Cyan just works better with Linux Swap than xROM does.
[G1 Android Development] Rmag37:
I think you should definately retry it like cyanogen said, if not on 3.9.9.1 than on the next stable build, 4.0.
[G1 Android Development] cytown:
try swapness set to 60 or more when use compcache.

I do think this will help.
[G1 Android Development] pinetreehater:
I will retest this evening with 3.9.9.1....compCache vs. Swap

stay tuned!
[G1 Android Development] osho741:
Why is a thread on technical issues like lunix swap and compcache suddenly more compelling than a ufc tapout match!?
[G1 Android Development] zimphishmonger:
Excellent experimentation, Pinetreehater! Thanks for doin a pseudo-scientific battery test so we can really try to tweak the settings. I saw that you were using 3.6.7 build, not sure if that was a typo or not??

Anyway you can repeat the test using the new 3.9.9.1 rom, as I have seen significant improvements in memory management for that build in comparison to 3.9.7 and 3.9.8.

Thanks again for your work!

EDIT: Cant wait for the retest results....thanks for taking the time to do this, as the whole community will benefit from your results :)
[G1 Android Development] overground:
I'm starting to hate pine trees too...lots of sap that f&%*s up car paint. Awaiting your future results as I have found similar results as you, but alas, I only have one Dream to test with.:( Keep up the death matches!
[G1 Android Development] mykenyc:
good test well as far as burning out the microsd i doubt i have a phone long enough to burn it out i switch phones like no other, but this is rather interesting...
[G1 Android Development] derfolo:
pinetreehater, great job. As I said a while ago in one of your previous threads, compcache was really sucking for me no matter what the swappiness, and having it disabled entirely seemed to improve the performance of my phone. I'll back you on this, you're not crazy. Anyway, yeah, very interested in your results tonight. Maybe I'll like it this time around.
[G1 Android Development] 51dusty:
nand is not the same as ram. it's like a sdcard and gets worn out over time just the same.
[G1 Android Development] PsychoPomp:
@miketaylor00

Dude, just wanted to take a sec & thank you for your contributions to Android and XDA

On topic, I use straight Linux-swap. 96mb partition w/ 80 swappiness. I rarely get a load screen.
[G1 Android Development] :
Still trying different configurations.

First of all, with a Class 4 microSD, WG Y1 BFS w/RAM hack, 256MB swap partition (I know, it's an overkill...)

CompCache with Backing Swap, no matter what swappiness, seems to be the slowest.

CompCache alone is okay if swappiness is low.

Linux-swap seems fast at first, but gradually slows down till unusable.
[G1 Android Development] s15274n:
Does Cyanogen have recommendations for this on his latest ROM? I assume his ROM has his ideal configuration in it so no changes are needed right?
[G1 Android Development] psrtx:
Best performance on CM (G1)

For me the best performance is 24M Linux swap with swappiness = 30. Anything bigger (in swap size or swapiness) causes the phone to lag after 1-2 days of use.

Also the 10M memory hack helps speed up the phone (10M + 24M swap = 34M additional memory). After trying lots of different settings, this is the most stable and fast settings that I have found.
[G1 Android Development] prince.siraj:
It's not just overkill, it's going to slow down... compcache seems to be the smoothest on standard dream roms, while Linux Swap seems to win but slows down on Sense roms... so I'd say just stick with linux swap though because compcache does add overhead with a high disksize. and don't forget, high memlimit is good, just make it lower than the disksize by like 5. swappiness 50 is ok. I used to run SenseHero 1.4 and I think it was 72 disksize, 60 memlimit, and 50 swappiness or so. pretty nice. or it was 64 disksize. but that was sensehero so play around, no settings are perfect for more than one person, maybe 2 if you're lucky.

If you must stick to a Swap partition, I'd suggest a 96mb partition or lower. Any higher and you WILL have slowdowns guaranteed, because there's a lot of overhead accessing more data than that and will begin to lag. just keep the swappiness lower, otherwise it will fill up too fast and slow down.
[G1 Android Development] JAguirre1231:
Yay, the compcache lover. Missed you Prince, what rom are you currently using and does it work good with compcache
[G1 Android Development] :
Thanks all. Is it possible to downsize the swap partition without re-partitioning all of them...?

CompCache currently doesn't compress the pages before sending to the backing swap, I guess it will enhance the performance when it does so (they said it's on the roadmap)...?
[G1 Android Development] JAguirre1231:
Yes, just remove it and then remake it. However, there fill be space on your sdcard that you can't use until you repartition
[G1 Android Development] :
Thanks, guess I'll leave the partition there for now. Gonna wait for fully-working 2.0 and do a complete wipe.

Now have CompCache at 24MB and swappiness 60, on latest Cyan, so far so good.

Tried 32MB but it seems it leaves too little RAM to run smoothly at all. Lower swappiness leave much of the CompCache empty (at 30, it's about 50% full usually) which doesn't make sense to me at all.

THANKS!
[G1 Android Development] domenukk:
I've just set up swap - for the IM app did always lose connection and webpages reloaded and so on.

now running amazing 256MB of Ram!

Just making shure, nothing ever has to close unless I want it to

Shure speed whatever. Facts can tell what they want, I'm happy with it. 30 or 90 for swappiness - doesn't matter that much...

The longest time I've waited for switch was about 4 seconds (the same time it takes without swap to just change the orientation)

I am super happy!

Maybe its still so amazingly fast due to cyanogens latest rom (.12.2)

:D
[G1 Android Development] Ace42:
uhh the dream only has 192 MB ram...Are you talking about the swap partition? You cant increase ram since its a physical part in the phone.
[G1 Android Development] domenukk:
Yeah i ment additional to the 192 megabyte ram 256 megabyte swap.

Ment one thing and wrote another... (btw: Nokia N900 has a nice 750 mb swap and 256mb ram)
[G1 Android Development] enomther:
I agree here nand is just another flashable board w/limited write cycles (def not RAM). using linux-swap here would yield little to no benefit over linux-swap on your sdcard, except possibly for the bus access tradeoff, which would be

extremely

minimal.

My 2 cents on the OP's results. I would retry the cyanogen 3.9.9.1, or 3.9.10, or whatever it is when you finally read this (;)).

I'm not really sure what version of compcache cyanogen's mods are using, could be 0.6-preX (again not sure). I can tell you on the ROM's I use, I'm utilizing the 0.5.3 version with the implemented ARM fix, and compcache blows linux-swap out of the water (in terms of performance).

Again, just my 2 cents.

~enom~
[G1 Android Development] Temar:
Why did you enable compache+swap? If you have compache and an additional swap device your comparison gets useless, because you can not tell which swap space (compcache or disk) gets used.

I hope you do this comparison again. I would be really interested in real results - meaning a proper compcache vs sd-swap comparison, not compcache+swap vs swap.
[G1 Android Development] maxisma:
Temar is right.

And please check the SDcard write/read speeds ;-)
[G1 Android Development] pinetreehater:
It wasn't Compcache with Linux swap, it was Compcache with backing swap. I was under the impression that a backing swap performs as an overflow buffer when utilized with CompCache 0.6 (but not 0.5)...although I cannot cite that reference anymore. Basically it is CompCache using a cc_memlimit of 16mb, allowing everything above that to be shuttled to the swap. It actually does work well, though I think higher cutoff settings work better (e.g., 28mb).

Anyway, the testing is complete. Pure CompCache 0.6 vs. Linux swap. Both at 32 mb. Both running the illustrious CM 3.9.10.

DSL speed is only 6mb/sec so youtube will take two hours+ to get the file and 20 minutes to convert it properly (it's like 500mb quicktime).

It's been a long day for me (5am)...I'll try to hold out and get it upped tonight. I don't want to say the outcome until the video can be viewed.
[G1 Android Development] enomther:
anxious to see.

~enom~
[G1 Android Development] miketaylor00:
Try my user.conf. I've had confirmation from a couple of people that their phone runs much faster on Cyan builds with my settings.
[G1 Android Development] overpower:
Although you're right in the case where Compcache has a backing swap, if swap devices are enabled with different priorities, then the lower priority swap device is used only when the higher priority swap is filled. Since the swapon which is standardized on most roms doesn't allow priority settings and automatically lowers priority for the next device, enabling multiple swap devices will always have this overflow behavior.

Incorrect. Temar is right. The behavior of a compcache backing_swap is that any memory that fails to compress better than a 2:1 ratio is stored on the backing_swap uncompressd. After memlimit is reached, it may place all requests onto the backing_swap as you expect. (This I can't confirm)

Thus, with a backing_swap enabled, you do not know whether the data is going to compressed memory or the disk. However, I'm pretty sure this means that compcache will ALWAYS attempt to compress the memory if there is space in memory meaning there will always be a performance overhead. As I stated earlier, I don't know whether this will result in continued performance overhead when memlimit is reached.
[G1 Android Development] pinetreehater:
ok, I have some ideas and this is what I believe, at least at this moment:rolleyes:

In short, the overhead to the swap should be no greater than the overhead to ram, especially when RAM is running low.And then you have to worry about the Cache being overwritten by other stuff or vying for access (remember CompCache isn't the only thing to access RAM). In fact, the storage of overflow to internal mem is likely to cause additional hesitation as CompCache has to interrupt and redirect the buffer stream I/O everytime it gets bad compression ratios or is full.

For those running without a backing-swap to their CompCache, their overflow is getting shunted to internal memory where it has vie for system resources just like any other..

ANYHOW, I do not want to get into the merits of having a backing swap for CompCache. The jury is still out on that one, and maybe a future stress test comparison is in order...Personally I agree with you, CompCache is best by itself. Just playing devil's advocate.

The F'ing videos didn't upload. It is next to impossible to upload to youtube during the day (unless you are not browsing...but my whole family uses the DSL and they mutiny when I am uploading to Youtube).

Youtube needs a better background uploader...one that throttles. Nevertheless, I woke up last night at 1am and noticed the upload failed. So I started it again. This morning at 730, it had failed again. No reason, no rationale...just failed. I will start it again as soon as the family "gets their morning surfing out"...

Is there a better way than upoading a 500mb quicktime video...is it easier to change formats (perhaps to Mp4)? I will look into it.

EDIT: My dumb ass been trying to upload in raw .mov format...just figured out how much smaller .mp4 really is....sheesh. Will be done shortly.
[G1 Android Development] dwang:
So don't keep everybody in suspense. What was the conclusion to your tests?
[G1 Android Development] Dyonas:
Look online for a free video converter there are plenty available and any should be fine for your needs here. The video itself doesn't need to be super high quality since it isn't really showing details, only two displays transitioning between apps.
[G1 Android Development] overground:
What are your settings? Where is your user.conf posted?
[G1 Android Development] dwang:
I'm also wondering if the network location slowdown bug (which causes the CPU utilization to increase over time) reported in cyanogen's thread could be affecting the results. This will have a direct affect on compcache since it uses CPU to compress and decompress.

Have you tried your tests with network location and latitude disabled?
[G1 Android Development] miketaylor00:
Sorry. I've posted it in a few threads so I thought I wouldn't post it again. Here is a link to the cyan thread where I posted it

http://xdaforums.com/showthread.php?p=4334135&highlight=user.conf#post4334135