yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] shayne122:
Haha :p sorry for that :p it was early and I'm a bit of a noob - anyway, definitely stable as hell so far, with only a bit more battery drain. Dolphin browser is noticeably smoother.

I was having issues a few weeks ago using any other kernel other than cursors, but this one is working fine (for the obvious reasons). Problem was yellowing and interlacing issues on the screen. I would be curious to try another ROM and flash this kernel to see if it would help those with the newer Rogers magics.

EDIT: don't do this. wouldn't boot past blank screen. wooooo ADB!
[myTouch 3G, Magic Android Development] xaueious:
This is running on my 32A Magic right now. Everything seems okay actually.

Battery life doesn't seem much worse neither. This patch just bumps the frequency up without changing voltage.
[myTouch 3G, Magic Android Development] 5[Strogino]:
WHat's about test with app Benchmark?

http://www.cyrket.com/p/android/softweg.hw.performance/

Before? After?

Real overclock or placebo?
[myTouch 3G, Magic Android Development] xaueious:
If you still think this patch is placebo you have not been around for the last couple weeks
[myTouch 3G, Magic Android Development] csjfong:
does it work on 2.1 Sense UI ROM (e.g. Smoki, CapySlide)?
[myTouch 3G, Magic Android Development] omnikai:
Flashed on top of Capymod's ROM based on Sanpei's Legend 0.4 (Eris). Phone no longer boots.

6.35 Radio

1.76.2007 SPL

HTC Magic 32A (Rogers)

Reverted to pre-patched system.img and it's fine again though.
[myTouch 3G, Magic Android Development] Deviser:
Do you think this is dangerous for the phone? I mean, I know there's always a certain risk, but is it high?
[myTouch 3G, Magic Android Development] shayne122:
tried smoki, wouldn't boot. had to revert to nandroid backup.
[myTouch 3G, Magic Android Development] xaueious:
I said this is for 1.5 Sense roms. Why are you guys even trying this for 2.1 roms?
[myTouch 3G, Magic Android Development] shayne122:
I know in computer OC'ing, the danger is heat, hence the advent of things like water cooling and fans the size of a hubcap.. If the same rings true, I don't think we have too much to worry about as the upping of the frequency hasn't put out any noticeable heat increase during gaming, calls, and regular usage. At least on my phone.

Because we suck at reading.
[myTouch 3G, Magic Android Development] omnikai:
Looks like Sense 2.1 roms won't work with this. Thanks anyway!
[myTouch 3G, Magic Android Development] d3vi:
Strangely enough Linpack reports no apparent improvement after flashing the update over, still in the 2.2-2.3s. Using CursorSense 1.2.6.1, 6.35 radio, on top of 32A. Any ideas?
[myTouch 3G, Magic Android Development] Deviser:
I have the same setup and my results in Linpack went up to 3.1....Sorry, but I don't know how to help you any further.
[myTouch 3G, Magic Android Development] Rugga:
noobs, gota love em... haha
[myTouch 3G, Magic Android Development] 5[Strogino]:
Ok. I'm testing, but...

I installed CursorSense 1.2.4 fresh after full wipe, then 1.2.6 and got problem with superuser, then installed 1.2.6.1 - problems with superuser were gone

Installed Linpack 1.1.2, tested without patch...

Then installed patch via recovery, started, tested with Linpack again

No 3.xxx points, same 2.390-2.410 points

Why?

I explore patch - it contain 08dalviklink script. After installing patch - script can be found in /system/etc/init.d. SO patch installed successfully, but why Linpack results are same???

p.s. In build version: Cursorsense32A-1.2.6 + Dalvik-Cachemod by xau. What's wrong?

p.p.s.

Turned wifi off. Results are same

Disconnect from computer. Results are same.
[myTouch 3G, Magic Android Development] 5[Strogino]:
Second try

Wiped everything

Installed 1.2.4, then 1.2.6.1, then patch

Tested by Linpack - got 2.41

Disappointment...
[myTouch 3G, Magic Android Development] xaueious:
08dalvik? That's the wrong patch. That one is supposed to move dalvik-cache to /cache to save space on /cache

The overclock one includes zImage and wlan.ko
[myTouch 3G, Magic Android Development] xaueious:
edit: double post and I am an idiot
[myTouch 3G, Magic Android Development] 5[Strogino]:
Ok. Why did you post this file in first message in this topic?

boot-2.6.27.6-710MHzOC.zip (2.35 MB, 40 views)

It contain wlan.ko, boot.img and 08dalvinlink

And this is file that i used and got nothing. Where overclocked boot.img?
[myTouch 3G, Magic Android Development] keinengel:
He posted the right file in the CursorSense thread, probably just a mistake.

The right file is located at http://xdaforums.com/attachment.php?attachmentid=326077&d=1273800542
[myTouch 3G, Magic Android Development] 5[Strogino]:
thx,keinengl for right link.

Did some deep tests.

What things i used:

1. SystemPanel. Killed all except 6 apps in memory before and between tests (HTC Sense, Messaging, Clock, SystemPanel, Touch Input and Calendar)

2. Linpack

3. BenchmarkPi

4. CPU Benchmark

5. Benchmark

6. NBench

Did 3 times every test except NBench (it took long time =)

Results (1 - normal; 2 - overclocked)

Linpack 1: 2.394; 2.401; 2.376

Linpack 2: 2.979; 3.155; 3.144

BenchmarkPI 1: 11761; 11658; 11565

BenchmarkPI 2: 8656; 8654; 8528

CPU Benchmark 1: 3531; 3455; 3518

CPU Benchmark 2: 2905; 2916; 2895

Benchmark 1: 169.763; 173.958; 177.001

Benchmark 2: 223.734; 242.071; 213.582

NBench 1 Baseline Linux AMDK6/233

Memory Index: 0.869

Integer Index: 1.523

F-Point Index: 0.199

NBench 2 Baseline Linux AMDK6/233

Memory Index: 1.127

Integer Index: 2.032

F-Point Index: 0.265

All tests show, that overclocked boot.img was faster than normal.

Even Quadrant thinking, thats overclocked Magic is faster) See attached image.

All images with results i attached to my post.
[myTouch 3G, Magic Android Development] pellen:
Have tried this OC'd kernel a day now and it definitely feels snappier now, really nice. I hope you can fix this for 2.1 when it comes out...whenever that happens :)
[myTouch 3G, Magic Android Development] xaueious:
MY MISTAKE. FIXED AND CHECKED

Should be good now :).

2.1

For 2.1 use pershoot's or dumfuq's kernels. You need old radio for that though. This is still the only kernel that plays nice with new radio from. You can ask Sanpei to fix his up, but his kernel is not open source so there's nothing I'm going to do there.
[myTouch 3G, Magic Android Development] xaueious:
Bump after verifying v2 for myself. Cousin is using the phone so I can verify only once in a while. That's why I wanted to hear back from you guys.

Not sure why but can't get setcpu to work at all. Not sure if this was the case with Cursorsense before. The phone still scales from 245-710 MHz (treating 710 MHz as if it is 528 MHz), but this isn't as much control as I would have liked. Anyone have any ideas?
[myTouch 3G, Magic Android Development] vadatte:
and the battery drain more fastly with OC kernel ?

Thanks for you all for you excellent work and test
[myTouch 3G, Magic Android Development] xaueious:
Not sure how much more battery drain is. Try it and if you don't like it just undo.
[myTouch 3G, Magic Android Development] Jus10o:
[32A][6.35] OC Kernel for Cursorsense/Rooted Stock/Others - 710 MHz Stable, 2.6.27.6

There shouldn't be a notable difference in battery life since there is no changing of voltage. Also in a way it should increase battery because the phone will complete task quicker since its OC which means it will return to a lower clock speed faster. Same concept about JIT.

Sent from my HERO200 using the XDA mobile application powered by Tapatalk
[myTouch 3G, Magic Android Development] xaueious:
Not same concept at all. JIT changes the way Android handles Java instructions. This is a hardware overclock.
[myTouch 3G, Magic Android Development] ododoo:
Does not work on Cyanogen 5.x rom. Caught in a boot loop...
[myTouch 3G, Magic Android Development] 5[Strogino]:
Xau, does patch affect to aspuclock.c in kernel? Can you provide more info to other devs?
[myTouch 3G, Magic Android Development] d3vi:
xaueious, thanks for the updated post. Version 2 clocks in at 3.129 mflops, up from 2.367 before. Setcpu still sees it as 528MHz, but then again it's not a biggie, as long as benchmark and general usage results have much improved.
[myTouch 3G, Magic Android Development] d3vi:
One additional note regarding usage of Setcpu, apparently tinkering with the scaling settings is not such a great idea. Choosing anything other than "performance" leads to odd issues when waking the phone up, as backlight goes up, but screen remains black, sometimes it takes multiple sequential presses of menu/hang up to get it showing again (non-deterministic as it seems).

It appears that Cyanogen 5.0.7 overclockers are experiencing similar problems.
[myTouch 3G, Magic Android Development] d3vi:
Can't work, as Cyanogen is using the 3.22 (old) radio, and this update is for 6.35 only. You probably want this instead: [OLD RADIO 32A][KERNEL] Cyanogenmod kernel OC'd to 633MHZ or 710MHZ [UPDATE 14.05.10] (can't post links yet due to forum restrictions).
[myTouch 3G, Magic Android Development] xaueious:
It's in op. maxisma's edits to acpuclock.c on github. In fact just copied acpuclock.c and then hit compile using one of the 32A configs.

Both HTC-CCR-Kernel (what Cursordroid uses for Cursorsense) and maxisma's Hero kernel are really just the Teknologist Hero kernel.
[myTouch 3G, Magic Android Development] lerutis:
Just flashed it, very snappy Cursorsense :D
[myTouch 3G, Magic Android Development] Deviser:
Is it possible to have JIT enabled with CursorSense ROM?
[myTouch 3G, Magic Android Development] Rugga:
Wow it is actually pretty fast. Scrolling home screens, contacts lists etc is so smooth. Thanks.
[myTouch 3G, Magic Android Development] xaueious:
Is there enough interest for me to recompile this without perflock to see if SetCPU works?

I don't have a 32A to test on.
[myTouch 3G, Magic Android Development] smurfhat:
YES!

Iam up for trying it out. I have been using cursorsense and I would defintely be willing to give it a go. :cool:
[myTouch 3G, Magic Android Development] smurfhat:
hmm?

This may be of some use to you. Comes from another forum but I didnt want to link outside the site.

"Well, I did build a kernel without perflock and installed the setCPU app and I can tell you it's a no go...

Slow as hell in changing the freq on wake-up (mostly the same behavior as plain ondemand)

It even exhibits strange behaviors such as the keys light turning on and turning off and on again etc. really a weird wake-up for the phone...
[myTouch 3G, Magic Android Development] Rugga:
Anyone having issues with wifi?

My phone connected to home wifi this morning, but fails at obtaining IP address from two different access points here at work.

All networks are WPA2-Personal, weird.
[myTouch 3G, Magic Android Development] ododoo:
Hehe... Thank you! I guess I should read things a bit closer.
[myTouch 3G, Magic Android Development] xaueious:
From modaco is fine. This is the person who came up with the kernel source that this oc patch is on anyways.

http://android.modaco.com/content/h...k-config-in-the-kernel-to-support-setcpu-app/

If someone wants to build one themself, just found this BFS kernel with the overclock mod built in for the Hero. Should be possible to modify it for the Magic: http://github.com/Soaa-/-lightspeed/tree/master/kernel-hero/

This person also has built this with perlock off: http://android.modaco.com/content/h...ernel-lightspeed-0-1-faster-than-fast-enough/

Here's the .config: http://github.com/Soaa-/-lightspeed/blob/master/kernel-hero/.config

That kernel publisher also mentioned a wake up issue. This might be the same one pershoot has mentioned before in the Dream thread for speeds around 128 MHz. So minimum frequency should not be set below 245 MHz or the phone may not wake from sleep? Not sure what the implications are there.

I might just rebuild based on the Lightspeed kernel changes without any of the BFS stuff. I really like SetCPU on my Dream, and the ability to see what frequency the phone is actually running at is nice as well.

Any kernel changes based on the same kernel is a go. So if you find anything else feel free to post it here and someone can try to build it for the 1.5 Sense ROMs.

Anyways here's a test build to be used with SetCPU

If I built it right, the full list of frequencies is here, not all of which are enabled in setcpu.txt:

176000,245760,352000,480000,528000,537600,556800,576000,595200,614400,633600,652800,672000,691200,710400,729600,748800,768000
[myTouch 3G, Magic Android Development] d3vi:
Thanks again xau, last version seems to work well with setcpu. As far as the wake up problems are concerned, if you're using on demand scaling, make sure to set a high enough min frequency. I've managed to avoid the hickups setting min/max to 480/710.
[myTouch 3G, Magic Android Development] xaueious:
Now posted a v3 that uses SetCPU and setcpu.txt. Now it is fully scalable for the supported frequencies.

Startup frequency is still 710 MHz so some people might not be able to boot with it. But no one has reported issues with booting 710 MHz so I'm keeping it this way for now.

If you want to use the disabled frequencies, you can easily change setcpu.txt to add support for the additional frequencies I listed in the table.

do something like this to get setcpu.txt so you can edit it in notepad or a text editor:

adb pull /system/sd/setcpu.txt .

then push it back with the following

adb remount
adb push setcpu.txt /system/sd

No guarantees about system stability beyond 710 MHz though. There have been reports of some stable GSM Heros stable at 768 MHz in the wild so you can try this for yourself. nandroid first!
[myTouch 3G, Magic Android Development] nelsonxcheung:
Test Report:

Boot ok after flashed v2 & v3

v3: Not much difference at 710 mhz

v2: Feel a little bit faster when using the phone

No obvious improvement in Linpack

Phone info: 32A new radio using stock HTC 1.5 sense UI rom, rooted
[myTouch 3G, Magic Android Development] xaueious:
Make sure you are really at 710 MHz when running your benchmark.

Linpack takes a few tries because the phone scales up and down depending on load. It is also affected by any background processes.

When doing benchmarks with v3: in SetCPU, disable profiles, and set both sliders to 710 MHz. ondemand is fine.

I hope v3 is working alright. I only was able to test the lower frequencies for stability. v3 resolves a possible issue in v2 where the CPU frequency may drop to 19.2 MHz on standby depending on ROM settings. If v2 runs stable for you, great.
[myTouch 3G, Magic Android Development] lerutis:
Flashing it right now! :)
[myTouch 3G, Magic Android Development] lerutis:
Works great!

i used a custom setcpu.txt and didnt use Autodetect in setcpu app, just let it read from the txt file.

Scaling perfect with ondemand between 176 - 710
[myTouch 3G, Magic Android Development] than33:
OK. I've made several tests. Definitely 'ondemand' is VERY slow compared to msm7k. No matter what You will enter in advanced tab. After MANY tests I've set minimum to 480MHz (like in original HTC ROM), and maximum to 768MHz (yes, it works like a charm!), governor msm7k. Everything runs VERY smooth. On other forums they say that msm7k is best for battery.

3.32 on Linpack.

I have 33 fps in Neo Core benchmark. And at 768MHz and 1 hour of testing on Neo Core: no crashes at all. :)

p.s. 'live' version on SetCPU widget tooks about 70% CPU ALL THE TIME > DO NOT USE IT!

p.s. 2 in version 3.1 bogomips is showing OK.

GOOD WORK!
[myTouch 3G, Magic Android Development] xaueious:
Good ideas there. Added notes in op. Thanks for your findings :)

The on_demand cpu freq driver was a bit dated on this kernel and looks primitive compared to some of the newer versions I've seen in the newer kernels (missing a lot of adjustable options), which might explain the performance issues. Modaco ROM defaults to the performance one for the Hero ROM, but msm7k is supposed to save power

Edit: I missed the note about on_demand governor Soaa- noted for his OC Hero kernel. Added

http://xdaforums.com/showthread.php?t=673653
[myTouch 3G, Magic Android Development] lerutis:
I think i fixed the setcpu.txt OKAY, i'm running 768 mhz at the moment but im getting crap results in CPU Benchmarks but good in others.

Gonna try Neo test etc, maybee someone could upload their setcpu.txt?
[myTouch 3G, Magic Android Development] xaueious:
Crap results might be a result of your CPU freaking out at the high frequency. I thought my G1 ran 595 MHz stable but it had occasionally would not wake from standby on battery, where as I have no issues with 576 MHz. I don't have a good way to test the phone for stability. Bootup and running applications is NOT indicative, nor is it going to show up in the form of heat.

Use the one before 768 MHz and see how you do. Try setting governor to performance at least for benchmarking. There are issues with the on_demand governor for sure, but the performance one should be functional despite being more power hungry.

I put a setcpu.txt here. Not going to put it in op because I really don't expect a lot of users to try this:

http://xdaforums.com/showpost.php?p=6512724&postcount=47
[myTouch 3G, Magic Android Development] lerutis:
Yes, i tried that .txt file.

Just god 33 fps in Neocore, very nice =) 768mhz.

Feels really snappy, thanks for this OC kernel!
[myTouch 3G, Magic Android Development] nelsonxcheung:
Flashed v2 and run for 3 hours, found that:

- Very responsive

- After 3 hours, when wake from sleep (usb charging)....clock locked at 245mhz, cannot change or scale up further. Device slow down of course

- now flashing v3.1 with SetCPU to continue to test
[myTouch 3G, Magic Android Development] Switch33:
I flashed v3 and setup mine the same, can confirm 3.3 bogomips in Linpack and seems to work very well with msm7k, stable so far at 768MHz...
[myTouch 3G, Magic Android Development] lerutis:
yep, 768 is running like a charm!!
[myTouch 3G, Magic Android Development] than33:
I've found 768mhz being unstable in yxflash (confirmed several times). I stepped down to 748Mhz and now yxflash works stable (whole film watched for tests).
[myTouch 3G, Magic Android Development] than33:
Ondemand

I finally managed to set ondemand correctly. I have 2 days of incredible fast working. Try my settings for ondemand. I'm using 245-748. Use yours max, but min must be 245 for undervoltage.

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

Sent from my HTC Magic
[myTouch 3G, Magic Android Development] xaueious:
Yep still running fine on my cousin's 32A Magic as well.

Settings aren't as aggressive as yours. I have 176 MHz min and 710 MHz max working just fine for some reason. But you are right by forcing the min frequency a bit higher.
[myTouch 3G, Magic Android Development] Deviser:
Is there any easy way to try 768 MHZ? I'd like to try it but I don't know how to configure setcpu manually.

Thanks.
[myTouch 3G, Magic Android Development] xaueious:
It's all in setcpu.txt, which I threw under /system/sd/setcpu.txt

Something like...

adb pull /system/sd/setcpu.txt .

now edit your setcpu.txt

then

adb shell remount

adb push setcpu.txt /system/sd/

Add the frequency 768000 and it will be enabled. I don't expect it to be stable though so I am not going to provide a flashable version. You can't just add any frequency. They have to be enabled during the kernel compile.
[myTouch 3G, Magic Android Development] than33:
Just copy file that I attached to this post to your sd card. In any way.
[myTouch 3G, Magic Android Development] than33:
I wanted to set everything to work as fast as in performance (always max) mode. And when You will use my settings it will. Additionaly setting powersave to 25 tells ondemand governor to try to use lower frequencies if max is to high (but not to aggresively). Ondemand first goes to max, then goes lower. msm7k goes to max in some steps which makes everything a litle bit slower. Additionaly ondemand goes down to min very fast if cpu is not busy. Setting sampling rate to low is making in fact everything slower because of too much changes in frequency. My idea was to set sampling rate as high as possible, but to not see any lags in speed. I'm really impressed that I have speed comparable to always max, but with battery working for as long as it should (two days of normal working).
[myTouch 3G, Magic Android Development] keinengel:
@than33:

I've tried your setcpu.txt and settings, but got a lot of instability (froze when I was setting up setcpu, SenseUI reloads every now and then, it sometimes takes a lot of time to wake up from sleep). I'm using xaueious' v3.2 kernel with setcpu 1.54 on CursorSense 1.2.6.1. Do your phone have this kind of behaviour?
[myTouch 3G, Magic Android Development] than33:
No. I had almost stable at 768mhz (crashes from time to time) and perfectly stable at 748.

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

Sent from my HTC Magic
[myTouch 3G, Magic Android Development] d3vi:
Same here, 729-748 seems to be stable enough, while 768 is already pushing the limits a bit. Then again, at this point it depends on the physical CPU itself, some can handle higher clock speeds, while others don't, even though all are of the same model.
[myTouch 3G, Magic Android Development] keinengel:
The problem seems to be with SetCPU, because the issues didn't go away after I flashed the v2 kernel, but after uninstalling SetCPU.
[myTouch 3G, Magic Android Development] Deviser:
Updated to v3.2 and used .txt from than33....It's impossible to try 768Mhz...the phone freezes the moment I set it.
[myTouch 3G, Magic Android Development] Rugga:
Works well for me, thanks a lot.
[myTouch 3G, Magic Android Development] than33:
Please tell what has changed in 3.2 version of your kernel??
[myTouch 3G, Magic Android Development] xaueious:
Nothing important. i took the extra wlan.ko i made it flash out from /system/modules/

It's like 600 KB extra in your /system partition if you are really keen on getting rid of it.
[myTouch 3G, Magic Android Development] magicdroid:
Are there any experiments with under volting in the pipeline? ;)
[myTouch 3G, Magic Android Development] Rugga:
I've been running 480MHz max for two days just to test, and I have not noticed any huge difference in battery drain compared to running 710MHz, about 10% difference. You do notice how much slower everything is though (obviously).

I think under volt hack might be good.
[myTouch 3G, Magic Android Development] xaueious:
Not really. There's not any many voltages levels to play with. Plus I don't even have a 32A Magic. The settings are pretty decent right now in my opinion.
[myTouch 3G, Magic Android Development] eyegor:
Perhaps the CPU could overclock further if you increased the voltage instead :)
[myTouch 3G, Magic Android Development] xaueious:
Nothing available to do that, at least not documented in the source code. If you find the Qualcomm MSM7200a datasheets you might be able to check if that's true.
[myTouch 3G, Magic Android Development] mariosraptor:
thanks. this works great on my magic 32A 1.5 sense with GyD's rom. no crashes at all. phone is flying as we say it here in Greece.
[myTouch 3G, Magic Android Development] varader0zs:
hello people.

tell me one thing. it is possible to put this in canongen 6 or above?
[myTouch 3G, Magic Android Development] Kefir.net:
No, its only for old sense roms.
[HD2 Windows Mobile 6.5 Themes and Apps] abumhmmd1:
NCX Sense 2.5 themes - May 13, 2010

Acid Digital Clock theme now available!​

2Dy I've passed throw nice worke of NCX Designs for TP2

Just want to share it here 4 Leo user .

​

:)​

Acid Digital Clock

​

MtNDew WhiteOut theme

​

ZuneHD theme

​

NCX Blue Droid
​

NCX Midnight Blue Clock set

​

THANKs & CREDiT to NCX Designs​

ENJOy

=-=-=-=-=​
[HD2 Windows Mobile 6.5 Themes and Apps] abumhmmd1:
NCX Designs made it a little customizable so you can mix backgrounds vs the clock font if you want or just use the font with the original background.

hope you like them

ENJOy
[HD2 Windows Mobile 6.5 Themes and Apps] abumhmmd1:
Try these numbers to Blue NCX Clock

THANKs Paten ......

-=-=-=-=-
[HD2 Windows Mobile 6.5 Themes and Apps] mmafighter077:
The acid clock is the best digital clock Ive seen. Can you make just the flip part a cab on its own minus the click background. Thanks for your hard work.