yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] :
Hahaha,

yeah you may have got the prize cpu of the lot;)

well my experience with uvoc was that i didnt have instability untill i got to around 15 percent battery left, then i was getting more fc's than usual. Then also the phone was switching off at around the same time, as if it was empty and giving a false reading to the OS. Also i found uvoc gave brilliant battery life when running at 345-245 sleep, when it was running on normal 1267-245 it eat battery stronger than just oc only. i spunked my battery in about 8 - 10 hours...

Its almost impossible to do a fair test so i suppose we will never know for sure, we just have our opinions. I also read somewhere a blog by some guy who it top notch on the nexus scene, and he seems to think that uv is the bane of the oc world.

But you can look at it what way you want, and if uv works for you and your happy then stick with it.

There is definatly no wrong and no right in this senario, just experiences;)

and as for ohm's law, i got an A in Physics at A'level, so i think i know a bit about relative energy transference.. lol

JD
[Desire Android Development] MacCarron:
Of course, it's just that imho we should stress this "it all comes down to luck" thing, rather than demonizing something that has its own logic per se :p. If i can venture a guess, i think that this is a possible rather precise explanation of the whole "UV drains more" phenomenon:

CPUs are produced in circular wafers, then cut individually. The rule of thumb is "the closer to the center, the better" as far as oc/ov/uc/uv is concerned, most of all uv/ov. It is obvious that most CPUs will not be "lucky" CPUs. UVing/OVing/OCing/UCing an "unlucky" CPU may cause some processes to crash. Unlike windows, android tries to restore such processes, thus enabling the OC (if it is set to "on demand"), other processes will crash, creating a sort of loop beacuse of which the CPUs drains more power because it spends a lot of time at full speed. So it is not true that UV+OC will drain more battery than plain OC, that happens because the CPU can't cope with lower voltages and spends all its time at full speed endlessly trying to restart crashed services :p. This of course is an extreme case scenario, but you get the idea.

Just like with x86 CPUs, you gotta be lucky ;)
[Desire Android Development] :
i think i will stick with my friend the oc for now;) May revert back in the future, but im loving the battery life;) i would love to hear Richards view on this..

JD
[Desire Android Development] MacCarron:
Oh yeah i'm not trying to say that plain OC is crap, just suggesting that people should give UV+OC a try it rather that skipping straight to the OC only part, they might get lucky just like me ;)

I too would be curious to hear richard's opinion on this, as i know very little of how android and its kernel operate.
[Desire Android Development] Reigenspieler:
The only thing what its does, is that my phone can't boot. Very funny. :D
[Desire Android Development] xtcislove:
MCR_UV_OC on MCR3.1 Kitchen ROM Apps2sd+@ext3

Works flawlessy! Great Battery Life and Great Perfomance!
[Desire Android Development] :
Hmmmmm......

I think i will do a test,

but my phone has now been on 1 day and 1 hour and has 30 percent left, with normal usage,

I think i never had that sort of battery life from stock kernel or uv-oc.....

But i might do an experiment, starting on monday;)
[Desire Android Development] fstluxe:
Dear Richard,

do you have the Stock version of V14 ?

thanks
[Desire Android Development] terryhau:
I flashed mcr v14 uvoc and it crashed once in a while, so i flashed v14 oc and it only goes up to 883mhz.
[Desire Android Development] tedman:
I can confirm this. I also flashed v14 oc (because the uvoc caused occasional restarts), but my max freq is also 883 MHz even if the slider is set to 1113 MHz.
[Desire Android Development] M4cr0s:
Just a normal anecdotal user report on v14 uvoc. Seem to work fine here after a couple of days use. No instability issues like reboots and the like. Run it up to 1113mhz max on Pays 1.9 and let it idle on 245mhz. I really can't say if it is any better than the stock 1.15 ROM my Desire came with batterywise. After a day at work with a bit of surfing, calling and such I'm down to about 50 % after 12 hours when using 3G primarly. At home I'm on wifi and it drops about 5 % per two hours when mostly idle, just an SMS every now and then. In other words, it lasts a day just fine, but I can't say it's heaven or hell compared to stock setup.

I do appreciate the good work by richardtrip (and Pays + a truckload of others too) though, and beer-money donations are coming!

Mac
[Desire Android Development] Too51oll:
+1 On MCR3.1 V14 OC getting 883 MHz max if setting are up to 1113 MHz but if max is set to 1267 MHz it works fine. Weird.

Sent from my HTC Desire
[Desire Android Development] nitrox1:
+1 PaYS Sparta 1.1, V14 OC getting 883 Mhz max, but slider and governor on 1113 Mhz.
[Desire Android Development] richardtrip:
posted new oc_v14 versions, please test. If all is ok i will post Stock rom versions later.
[Desire Android Development] :
Whats the changelog? My v14 oc only was fine, i am getting 1267mhz...

JD
[Desire Android Development] blunatic:
wont boot my Desire with mcrV14 on stockrom :(

Damn ! Just delete my other versions

test stock V14 only oc
[Desire Android Development] richardtrip:
Re: [KERNEL] UVOC or OC-only + CFQ + ext4 + tun + 8MB hack

I post the stock rom version later.
[Desire Android Development] :
Changelog?
[Desire Android Development] Pyr0x64:
hi richard,

have you had a chance to try the -mfpu=neon flag?
[Desire Android Development] blunatic:
thx................... !!
[Desire Android Development] nitrox1:
Sorry but what do you mean by change log?

But I get the same as tusiol_n95

Can use the sliders to get the numbers above 1000Mhz, but the actual Mhz never goes above 883Mhz

(On all previous kernels it's been fine)

As so with quadrant it's showing it running slower than standard desire. (Again with setcpu to all it's max settings)
[Desire Android Development] :
mine is going to the 1267mhz range, and im using a setcpu.txt i have from earlier files, i suppose that was the only problem, therefore the only change?

But i wouldnt know as getting a reply from richard is like waiting for a telegram from the queen of england;)

JD
[Desire Android Development] RiotRick:
Just downloaded this one. Seems to be stuck at 883mhz maximum.
[Desire Android Development] :
can you upload your setcpu.txt file? I have the v14 oc only and im getting 1267mhz no problem, and im using an old setcpu file i had from v7
[Desire Android Development] richardtrip:
Re: [KERNEL] UVOC or OC-only + CFQ + ext4 + tun + 8MB hack

There is no changelog. Compiled again. People reported problems about 883mhz or something. Just to make sure nothing is wrong.
[Desire Android Development] :
have you enabled the device selection in setcpu?
[Desire Android Development] munkimatt:
Erm...just to confuse matters, no contrast bug here. Using the MCR version.
[Desire Android Development] asci:
Uhm that's very strange...did you set cpu with with SetCPU?
[Desire Android Development] MacCarron:
Weird contrast bug for me as well, after locking and unlocking the phone.
[Desire Android Development] manook:
Contrast bug for me as well - MCR r3. Ok after initial boot but after a couple of mins or so bug is back.
[Desire Android Development] munkimatt:
Yeah, screenshot attached with widget showing clock speed.
[Desire Android Development] stingerpl:
Re: Kernels + ext4 + tun + cifs (1113 MHz oc-uv WORKING NOW)

Maybe you cant see the bug? ;)
[Desire Android Development] munkimatt:
Well everyone says they get it after locking/unlocking the screen. I don't. Any more helpful comments?
[Desire Android Development] biebi:
Its not the unlocking/locking part.

Its the screen falling asleep and waking up again. Which usually still happens on boot.

So contrast gets bugged after a sleep/awaken cycle.
[Desire Android Development] ivicask:
Flashed MCRbfsbravo-signed

When i lower brightness to min some black spots get pink color. Also after i boot phone, brightnes is ok. After just one screen turn off- turn off, all colors gets brightnen (Not screen brightness), black color is not black.
[Desire Android Development] MacCarron:
Wow you are right, just tried it myself :p:p. I had not noticed since i usually keep maximum brightness on (yeah i'm a show off ;) ).
[Desire Android Development] asci:
Well I installed his new Kernel with OC working over its previous version, maybe @munkimatt did a clean flash of fixed kernel...

munkimatt can you tell us...???
[Desire Android Development] munkimatt:
I hadn't used the previous overclock kernel, I installed over the BFS one.
[Desire Android Development] richardtrip:
Re: Kernels + ext4 + tun + cifs (1113 MHz oc-uv WORKING NOW)

No contrast bug here. Patches attached to first post. Will look into it and see wat i can do.
[Desire Android Development] manook:
hmm just reinstalled mcr over the top to try and remove kernel and the modified kernel is still there. Done a full wipe as well, strange. Anyone have the standard kernel i can flash?
[Desire Android Development] stingerpl:
Re: Kernels + ext4 + tun + cifs (1113 MHz oc-uv WORKING NOW)

Do you still have the bfs kernel? Maybe I'll try to install bfs, and the newest kernel over it. Did you try to lower your brightness to 0? When I have high brightness the bug is barely visible.
[Desire Android Development] asci:
Did someone figure out how to use that Patch.zip? I tried to flash it, but it aborted.

However I tried to install Kernel one more time over my Nandroid Back up, and after switching off/on display, contrast bug appeared.
[Desire Android Development] asci:
Sorry mate, how to use the patch?
[Desire Android Development] richardtrip:
That is the zipped kernel patch (sourcecode). use one of the other two (or wait until i looked at the contrast bug).
[Desire Android Development] Pyr0x64:
nice work richard :)

hope you can manage to fix the contrast problems people are having
[Desire Android Development] atconc:
Just tried the MCR no BFS version (MCRnoBFS_ocuv2-signed.zip)- MCR R2 no apps to SD

set CPU auto detect picked up frequencies up to 1125 and seemed to be working fine but I also got the "contrast" bug once the screen had been off and back on. So am Nandroid restoring now - looks like throttling back the cpu like this will be a good battery saver once it's fully working though so am excited by the future potential :)

Also the topic says uv - just wondering how much the cpu is being undervolted by and if this is configurable?
[Desire Android Development] richardtrip:
Re: [KERNEL] UVOC or OC-only + CFQ + ext4 + tun + 8MB hack

I tested that on the froyo build. Didn't make any difference in linpack or quadrant scores.
[Desire Android Development] RiotRick:
Yes I have, can't get over 883Mhz even with the slider set higher.
[Desire Android Development] :
Rich i think they just have not enabled custom device selection in setcpu, or they have a corrupt setcpu.txt file, because mine is working fine;)
[Desire Android Development] RiotRick:
I used the setcpu.txt that was in the zipfile with the kernel.
[Desire Android Development] :
That is very strange, let me upload a setcpu.txt for you to try
[Desire Android Development] :
Try this;)

http://www.4shared.com/document/r-XDgzbn/setcpu.html

JD
[Desire Android Development] RiotRick:
With this setcpu.txt my slider will go up to 1.2GHz instead of 1.1GHz. But the max is still stuck at 883MHz
[Desire Android Development] :
Did you go to set custom settings on device selection?

JD
[Desire Android Development] RiotRick:
Yes offcourse.

I just flashed the ucov v14 kernel. That one is scaling up fine. So there's definately something wrong in the v14 oc kernel.
[Desire Android Development] :
thats really weird because mine is scaling from 245 - 1267mhz fine, and im using the v14 oc only....

Android OS freaks me out and every phone seems different;(

JD
[Desire Android Development] richardtrip:
Telegram's are going faster here (more important :-))
[Desire Android Development] richardtrip:
Stock rom versions posted (oc_v14 and uvoc_v14)
[Desire Android Development] richardtrip:
Maybe you set profiles (and kind of overrule the max setting?). It happened to me a couple of times :)
[Desire Android Development] nitrox1:
Don't be scared!

But don't send me a file either ;-) mr droid

Heard richard say he'd re-uploaded the MCR_V14 OC kernel.

So I have flashed this one again.

But sorry to say again. Stuck at 844-883 Mhz Scaling range.

Before the setCPU min and max would be up at 1100Mhz, but now they will only go to 844-883 Mhz.

Before the actual refresh Mhz, would never go above 883 Mhz, and it is still the same.

The quadrant results have gone up to 528, though.

I am selecting custom freq. from device, and have highest mhz of 1113600 in my setcpu.txt. Profiles off/on etc

And I have used 4 of richards kernels.
[Desire Android Development] RiotRick:
No the profiles are not set. I just tried again flashing the oc v14 kernel back. Same thing keeps stuk at 883MHz max. Then flashed the ucov v14 kernel, that one scales up just fine.
[Desire Android Development] :
Hmmmmm

What rom are you using?
[Desire Android Development] :
In the uk they are always on strike;)
[Desire Android Development] RiotRick:
MoDaCo rom v3.1
[Desire Android Development] Too51oll:
Mine is working fine in between 245-1267 however it's only hits 883 if 245-1113
[Desire Android Development] richardtrip:
Could you please test the attached kernel? (just a kernel update).
[Desire Android Development] stewcp:
I've just checked mine out and its exactly the same... nothing seems to kick it past the 883 mark... I've even downloaded the setcpu.txt again with no difference!
[Desire Android Development] RiotRick:
Same thing, still stuck @ 883MHz max.
[Desire Android Development] Too51oll:
Nope it doesnt work. 883 is max if slider is lower than 1267.
[Desire Android Development] :
yes, on mine as well,

Can confirm when max is lower than 1267mhz it will not pass 800mhz;(

But my max is always on full so I have never noticed this..

JD
[Desire Android Development] Too51oll:
List of all frequencies that doesnt work: 422, 537, 729, 921, 960, 998, 1036, 1075, 1113. Looks like something is really messed up.
[Desire Android Development] richardtrip:
The acpuclock-scorpion.c values are the same as the uvoc version except for the voltages of course. Can't check it myself (running Froyo atm).
[Desire Android Development] :
how lucky is that, i dont use any of them frequencys

245 - 1267 Normal

768 - 1267 Charge

245 - 345 Sleep

JD
[Desire Android Development] Too51oll:
Well it still skipping those frequencies for some reason.
[Desire Android Development] nitrox1:
Hi richard,

Tested it, (	oc_v14_test-signed.zip)

and it is the same.

Just can't force it above 883Mhz with setCPU.

Quadrant :423
[Desire Android Development] Too51oll:
In charge mode it will skip most frequencies in between but I guess you dont care, however i normal mode as it will skip some of them your device will run slower or will drain more battery because instead of runnig 998 for example it'll go for 883 (slower) or 1267 (juice draining). Sense?
[Desire Android Development] :
Yeah i understand your point, maybe i will switch to the uvoc untill this is sorted;)
[Desire Android Development] Too51oll:
And that is exactly what Im gonna do for now

;)
[Desire Android Development] :
even on the uvoc there are frequency's that are skipped...

But less than the oc only;)

JD
[Desire Android Development] Too51oll:
UVOC V14 is skipping some frequencies as well: 422, 537, 729, 921, 960, 1036, 1075, :confused: so is it whole v14 broken?
[Desire Android Development] i6bazar:
I've installed v14 but I loose something 25% every 12H of IDLE (MCR 3.1)

I think it is huge.

Can someone upload v11 MCR oconly ?

EDIT: found it from here : http://www.wuala.com/HTC_Desire/Kernel/MCR OCUV/?dl=1&lang=zh
[Desire Android Development] i6bazar:
@richard

Can you please post the acpu_freq_tbl structure used in v14 ?

Thanks !
[Desire Android Development] fxone:
Is there any chance to Enable "netfilter owner" the Droidwall does Work and other apps too.

thx

p.s. Great Work v14OC Runs Great without any Problems

That´s from the Droidwall Issue Page, I don´t no if it helps.

edit: Here is a sample from the Magic with enabled Netfilter/owner HTC Magic Sample
[Desire Android Development] PaY87:
I cannot confirm the battery drain here. v14 oc only works good!

Only the 883 Mhz bug I can confirm. :)

Also I really would like to see "netfilter owner" included, too ;)

Just donated you 5 (usd) bugs, keep up your work!
[Desire Android Development] erpalma:
Can we combine boot.img of app2sd with this kernel?
[Desire Android Development] PaY87:
Do you mean if you can use a2sd together with this kernel?

If yes your answer is yes ;)

Doesn't matter :)
[Desire Android Development] erpalma:
With the app2sd update.zip there is also a boot.img, doesn't it overwrite the kernel image?
[Desire Android Development] JDouce:
Any chance of these mods being transferred to the 2.32.9 kali kernel
[Desire Android Development] MasDroid:
Comment Deleted.
[Desire Android Development] erpalma:
UVOC and Audio mod probably, 8MB dunno. (CFQ, ext4, tun, etc are not mods).
[Desire Android Development] alanjp168:
yea it seems cpu freq stuck @ 883mhz

but tbh, it is just as fast as stock 998mhz and i couldnt notice any performance

gain on 1113 and 1267 when it worked. maybe in the endfroyo is what we really

need... :)
[Desire Android Development] JDouce:
since i want it for froyo i dont need the ext4 i not too bothered about tun ... would like audio , uv , oc , ram tho
[Desire Android Development] MasDroid:
Does anyone else have an issue where their phone automatically crashes and reboots when browsing and using the keyboard especially at times? I have noticed and wonder if its related to the kernel. Tried v11 oc and current kernel v14 oc.

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

Sent via the XDA Tapatalk App
[Desire Android Development] PaY87:
Did not happen to me (yet) :)
[Desire Android Development] d3sm0nd:
Is it good or bad to use profiles? I have charging profile enabled and set to about 700MHZ... I think it will charge faster this way. I have also sleep/stand by profile set to about 300MHZ... all are on demand.

Are these good settings? I've been using it for about two days and battery went from 100 to 60%.. I think it's good ?
[Desire Android Development] MasDroid:
@Pay87 since reboot, all seems well, no freezes/crashes... time will tell i guess ;)

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

Sent via the XDA Tapatalk App
[Desire Android Development] MarvinFS:
Happening to me all the time. when actively browsing (especially on 3G) when actively typing with vibro feedback turned on. also i noticed that lower back part of the phone (beneath the battery) in intensively heats up during such activity and then instant reboot... i've wrote about this issue to official support and here and to modaco - no answer ever...

i've tried already almost all avail. ROMs and kernels with or without OC and UV i've turned off the setcpu and also tried different profiles... behaviour is just all the same...

and the last one: reboot are more frequent when AC adapter is plugged in
[Desire Android Development] MasDroid:
Ok, good to know that i was not the only one to have this issue. My phone had also rebooted when getting quite warm and I had forgot to apply the custom setcpu settings... since applying and rebooting phone, i have not experienced any freezes/crashes. I will keep monitoring this issue and hope it does not happen again. This does question the stability of these modified kernels... let me know if you find any solutions.

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

Sent via the XDA Tapatalk App
[Desire Android Development] PaulW21781:
Same issue aswell. I noticed that pre-8MB hack, it ran fine (I was originally using V11), but V14 does seem somewhat unstable (reboots on plugging in of charger at times, 3G data while browsing...)

Does anyone have an old Stock V11 mirror?? The only copy I can find which I downloaded was the MCR one...
[Desire Android Development] Jagdish84:
I used the MCR one on my stock rom and it worked just fine mate...
[Desire Android Development] PaulW21781:
Aye, I've just gone through the ramdisk image, very little differences so all seems well :)
[Desire Android Development] MarvinFS:
here you go mate, actually i wanna try the original stock ROM w/o A2SD (may be it's the main issue?!) but still lazing to do this! :)
[Desire Android Development] PaulW21781:
Well I'm using the stock 1.21 Rom now with a modified v11 kernel for A2SD and it seems pretty solid now compared to the random reboot with v14 kernel. I've put up the modified kernels in the rooted WWE 1.21 thread on here (on page 3) which give A2SD support in it. Only real difference is the ramdisk image in the modified boot image. Aswell as the A2SD scripts and such obviously lol
[Desire Android Development] kerpz:
i'm running on oc_v14 and the battery is always around 3600-4000mV. is that normal?
[Desire Android Development] BlackLine7:
I'm having problems since the 8mb ram hack has been added.

Problems are battery drain, max freq 883MHz (since v14),...

Richard can you please post a version without the ram hack. Or make an option for v15, so we can test it. Imho the extra 8mb it's not worth the battery life!
[Desire Android Development] MasDroid:
I beg to differ, battery life seems fine.

Regarding the crashing/rebooting issue, it seems to have rectified itself. I have not really changed anything apart from appling setcpu custom frequencies and rebooting phone.

The phone itself is quite hot (currently 32 degrees celcius with wifi on), been using it a lot today and not noticed any lag and had no reboots since :)

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

Sent via the XDA Tapatalk App
[Desire Android Development] rdy2go:
Re: [KERNEL] UVOC or OC-only + CFQ + ext4 + tun +

My battery is ok with v 11 but sucks in the later versions...

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

Sent via the XDA Tapatalk App
[Desire Android Development] FSGuruh:
One more bug in r14 kernel

Did anybody notice that the setCpu.txt misses the highest frequency about 1267MHz? So this gives you two choices:

- Not activate SetCpu which gives you the highes possible frequency.

- Actiavte SetCpu. The highest selectable frequency is 1,1GHz which is not supported so you result in 883MHz. With the uv version you get at least 1,0GHz but no overclock at all.

So the result is actually the opposite what the title says, you get either a underclocked 883MHz or not overclock but at least undervolted phone, but never overclocked.

What is anyway the point of using SetCPU at all? The phone itself scales the CPU frequency anyway, without that tool perfectly. So it will never stay at 1GHz if nothing is to do. Also the voltages are kernel things and are not up to the program. So why it is not simply enough to have a patched kernel with more (high frequencies) and changed voltage levels are described and that's it. All scaling tasks are done anyway regardless if SetCPU runs or not.

IHMO:

My impression is SetCPU just confuses the user. So the user has to give the program again the specs about frequencies supported. Why asking the user again, the information is anyway in the kernel built in. Why not just using this information.

If you give SetCPU other frequencies than supported by the kernel it will simply not run anyway. I can't find a point what SetCPU is good for, as just running a further task doing the same what the kernel anyway does itself and costing CPU load with is totally unneeded.

@Richard:

Can you please clarify what happens with uv or oc kernel not running SetCPU. I noticed the are still scaling CPU frequency, so what's your option, knowledge about.
[Desire Android Development] Too51oll:
Add ,1267200 to your setcpu.txt and you'll be able to run this speed. Next time read a bit about before you post that something doesnt work.

Sent from my HTC Desire