Develop Bugs

Fresh on Frozen Eclair 537mhz 10 mflops - 1125mhz 21 mflops

Just a general question. Fresh, dc, stock, or baked with even overclock highest mflops i got were 9 mflops. So I added Frozen Eclair JIT to Fresh and was able to get 21 mflops @ 1125mhz. I have balanced my phone now for battery life and performance. I am at 537mhz which is giving me 10mflops and 55 fps on netarchy kernel 3.7.1. My question, Is my phone faster @ 537mhz with jit than stock @ 998mhz? I believe that the higher the mflop the faster the phone right?

mflops, is millions of floating point operations. therefore more is better.

This is a VERY interesting question. I kind of doubt that it will receive a good answer, though. I don't know what the answer is.
I would assume that processor speed is king. But if a lower processor speed gets you higher Mflops than, say, my phone than I guess that Mflops are king. I don't know why that would be that way, though.

SWEET I'll take 10mflops @ 537mhz because everything runs flawlessly internet, streaming video, and phone. When I need to game I can turn up the processor to 998 or 1125 and get 17 to 21 mflops. Thanks. My daily driver for now will be 537mhz. More battery life and more power than 2.1 android.

pongoface said:
SWEET I'll take 10mflops @ 537mhz because everything runs flawlessly internet, streaming video, and phone. When I need to game I can turn up the processor to 998 or 1125 and get 17 to 21 mflops. Thanks. My daily driver for now will be 537mhz. More battery life and more power than 2.1 android.
Click to expand...
Click to collapse
**EDIT**Nevermind............i need to get rid of Sense ui

I had a hard time to getting rid of my raining animations too lol
Sent from my PC36100 using XDA App

SetVsel settings tread.

Wonder what the rest of the lot here have overclocked their defy´s to in this god sent software.
Mine is as follows:
1: 20/300
2: 40/800
3: 70/1300
Please only post stable results, the one You can use without crasches on an everyday basis...

1: 22/300
2: 32/600
3: 52/1000
Quadrant score of 1785
Running CM7 custom rom.
Battery life seems ok (still monitoring it) and it's stable.

24/300
40/650
63/1200
VSel 3 is on the upper limit of stable. 62 made it reboot after half an hour of stress testing.
Im sure I can go lower on the others, but I haven't bothered.

I haven't used SetVsel yet, but I am overclocked with Milestone Overclock @ 1200/80 with no problems. Battery is not the best, but better than stock rom. I just flashed Quarx's CM7 rom and love it. I went from a 1400 Quadrant to a 1900 Quadrant just from flashing.

300 at 33 600 at 48 900 at 66. High 1700's in quadrant
Sent from my MB525 cm7quarx

Mine is:
[email protected]
[email protected]
[email protected]
up_threshold: 86%
limit to vsel1 while screen is off
limit to vsel2 on battery <= 30%
quit stable to me.

Mine is:
[email protected]
[email protected]
[email protected]
up_threshold: 82%

Good thread chaps, it gives us that haven't had the bottle to do it yet something to go on

My Settings
[email protected]
[email protected]
[email protected]
still testing it..
But even using all the tools my defy's doesnt last long than a day
i'm unable to switch to "2G only" network as I lose signal

Setvsel
300 @ 20
700 @ 40
1100 @ 56
rock stable and better battery life...

Mine is:
[email protected]
[email protected]
[email protected]
up_threshold: 86%

Anybody knows what is the perfect setting for CM7 Beta?

300 - 20
600 - 30
800 - 48
1000 - 56

[email protected]
[email protected]
[email protected]
up_threshold: 80%
ROM: CM7 Beta 5

I use setvsel +ledefy，
setvsel settings：
[email protected]
[email protected]
[email protected]
up_threshold: 82%
ledefy
I use a customer brightness

1300 ? my god, you impreesed me

Runs the defy stable at 1300???
As i said i use 1100 with 58 but i think it could be a bit faster though

escrivel said:
Runs the defy stable at 1300???
As i said i use 1100 with 58 but i think it could be a bit faster though
Click to expand...
Click to collapse
Yes, its 100% stable, in fact in forgot that i started the stability test so i ran it for over an hour... It reached 69° celsius, quite hot in other words...
60/1200 was what i ran before.

PetroLars said:
Yes, its 100% stable, in fact in forgot that i started the stability test so i ran it for over an hour... It reached 69° celsius, quite hot in other words...
60/1200 was what i ran before.
Click to expand...
Click to collapse
I have been running 58/1200 for around few months no issue currently on cm7
Sent from my MB525 using XDA App

[email protected]
[email protected]
[email protected]
Using S. Froyo Nordic I edition based on 3.4.2-177. These settings work good for me as I can easily squeeze 2 days out of my battery with moderate usage. I'd probably get 3 days out of my battery if I'd watch less youtube.

OC'ing

What's a safe level to overclock my phone to? I'm running the latest MIUI (1.9.16) with the lastest Tiamat kernel (1.1.3) I'm at about 1344 MHz right now. Can I go much highter?
Sent from my rooted, MIUI DInc2

From my testing, I've found there isn't to much to be gained going over 1.6ghz.
For a safe level I keep mine at 1.2 ghz. This has worked out well for me. Try different frequencies and see what works out for your needs.

I'm running JDKernel with the max set at 1.5 ghz, using the smartass governor. When I look at the "time in state" info, it usually shows about 75% of my time spent at 768 mhz. Seems to be working great.
Sent from my Incredible 2 using XDA App

Well, I tried bumping it up to 1.6, and I locked my phone and the screen turned off, but the keys stayed on, and it wouldn't come back up. So I pulled the battery and went back to 1.3 like it was before. Now its working great. I'm on smartass v2
Sent from my rooted, MIUI DInc2

If your having lockups, try installing Incredicontrol from the market and bump up the voltage on the higher frequencies 25-50mv, this should keep you from locking up. I do this when I use the performance governor and want to run Quadrant or Linpack .

PacerguyDon said:
If your having lockups, try installing Incredicontrol from the market and bump up the voltage on the higher frequencies 25-50mv, this should keep you from locking up. I do this when I use the performance governor and want to run Quadrant or Linpack .
Click to expand...
Click to collapse
I've been using SetCPU, cuz I couldn't understand Incredicontrol..... What's ideal if I'm running around 1.6 for voltage?

On the Jd Kernal, I'll bump it up to 1450 and go from there.

PacerguyDon said:
On the Jd Kernal, I'll bump it up to 1450 and go from there.
Click to expand...
Click to collapse
So, you don't know about for Tiamat? I'm using that one.
Plus, would anyone recommend using his Incredikernel as well?

I'll go about the same on the Tiamat. I usually will start at 50 mv over whatever the stock setting is on the kernel when running performance runs.
I didn't know that Chad had done a Kernel for Aosp romed Dinc2's. I know his Dinc1 Kernels were great.

I accidently had my phone at 1.9 for a day running jdkernel, no crashes or anything
Atm when my phone is charging, it gets bumped up to 1.4 and i have no issues at that speed.

Xperia Arc bootloops every 40-60 hours

Hello guys,
Since a month or a bit less my Arc bootloops every 40-60 hours, mostly while charging. It started without that I changed anything on the device like a new mod or so
It plays the bootanimation again and again and just a batterypull can fix it.
What I did so far:
- Reflashed it without wiping data, didn't help
Mods I applied:
- DooMKernel V15
- Statusbar widgets Indi V2
- Removed Junk Apps
- SuperCharger V6
Setup:
- Overclocked to 1.4GHz
- Underclocked to 122MHz, set it back to 245MHz today to see if it helps
- Undervolted -100mV
- Worked perfect like that for 4 months
I ran out of ideas on how to fix it and hope you guys can help me, as the bug is really annoying, I wake up if that happens at night while charging, which happens most of the time
If you have any idea, post it
Regards,
Flo
Sent from my iPad 2 using Tapatalk

Full wipe is recommended after sometime use personal opinion.
Sent from my MT15i using Tapatalk

Yeah, but I got tons of stuff on it that I don't want to lose.
And I did never do that on my X10 for 7 months and it was never a problem, then I got the Arc...
Sent from my iPad 2 using Tapatalk

Flo95 said:
Hello guys,
Since a month or a bit less my Arc bootloops every 40-60 hours, mostly while charging. It started without that I changed anything on the device like a new mod or so
It plays the bootanimation again and again and just a batterypull can fix it.
What I did so far:
- Reflashed it without wiping data, didn't help
Mods I applied:
- DooMKernel V15
- Statusbar widgets Indi V2
- Removed Junk Apps
- SuperCharger V6
Setup:
- Overclocked to 1.4GHz
- Underclocked to 122MHz, set it back to 245MHz today to see if it helps
- Undervolted -100mV
- Worked perfect like that for 4 months
I ran out of ideas on how to fix it and hope you guys can help me, as the bug is really annoying, I wake up if that happens at night while charging, which happens most of the time
If you have any idea, post it
Click to expand...
Click to collapse
Those are your problems right there. Try by removing overclock, then undervolt and if all else fails go back to stock kernel.

Ok, I'll try that.
But it was stable for 4 months, that's why I didn't touch that yet.
And I noticed when the CPU can't handle something, like 2GHz oc, the phone freezes for a min and restarts then in a normal reboot.
But I definitly try removing that after I know if the bug appears with the min cpu speed of 245MHz.
Sent from my iPad 2 using Tapatalk

Try the 1.6 ghz kernel from doomlord. It is possible that your cpu us a little fried with the 2ghz boot. Might just be more preferred then removing overclock, also i noticed that 1.4 doesn't really give give than 1.3. and only switch to higher values when you REALLY need them
Sent from my LT15i using xda premium

Thought the 1.6GHz kernel is for devices that don't boot wth the 2GHz version which works perfect on mine, it even runs @ 2GHz for a while.
Sent from my LT15i using XDA Premium App

Flo95 said:
Thought the 1.6GHz kernel is for devices that don't boot wth the 2GHz version which works perfect on mine, it even runs @ 2GHz for a while.
Click to expand...
Click to collapse
That doesn't mean that it can handle it. Prolonged stress to the processor can cause damage, so the FIRST thing to check when you see odd behavior is this (kernel, overclock, underclock, undervolt).

I won't stress test it @ 2GHz, don't want to burn it ^^
If it isn't fixed with 245MHz min speed I'll flash the 1.6GHz kernel and check it.
Otherwise I'll flash the stock one back, if it still happens then I ask for a exchange Arc. (It has the crack in the case, too)
Sent from my LT15i using XDA Premium App

Flo95 said:
I won't stress test it @ 2GHz, don't want to burn it ^^
If it isn't fixed with 245MHz min speed I'll flash the 1.6GHz kernel and check it.
Otherwise I'll flash the stock one back, if it still happens then I ask for a exchange Arc. (It has the crack in the case, too)
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
For the Arc (LT15) anything above 1 GHz is potentially damaging, just saying.
The spike during boot is not much of a big deal, but running it constantly at 1,4 for example, could cause issues.
So be careful. And I don't think anyone will give you a new Arc because you can't overclock enough the one you have!

It's totally stable @ 1.4GHz and runs at lower voltage than stock 1GHz, so there shouldn't be any damage.
If the CPU (is damaged or) can't handle sth the phone freezes for a min and restarts then, never had that @ 1.4GHz.
I don't want a new Arc for more oc, just in case I can't fix the bootloop issue. For oc mine is enough for me
Sent from my LT15i using XDA Premium App

Flo95 said:
It's totally stable @ 1.4GHz and runs at lower voltage than stock 1GHz, so there shouldn't be any damage.
If the CPU (is damaged or) can't handle sth the phone freezes for a min and restarts then, never had that @ 1.4GHz.
I don't want a new Arc for more oc, just in case I can't fix the bootloop issue. For oc mine is enough for me
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
If it were "totally stable", you wouldn't have started this thread though...
And what you describe is not the only indicator that the CPU can't handle your settings. Actually, bootloops are quite common for all sort of overclock and undervolt related issues.
Again, try running the phone at 1 GHz and see if the bootloops still occur.
If yes, try going back to stock kernel and observe again.
It's the only way to see if something is really the matter with the hardware.

Yes, well, totally stable was related to using it, works perfect then.
Just after the timegrame it restarts while charging and while charging it doesn't bump up the CPU speed like when doing heavy tasks like browsing. That's why I am so confused, the 50 hours are the time when it happens, if it would be uv or oc related it should happen before that 50 hours timeframe, shouldn't it?
Exam tomorrow, on Wednesday or the day after I should have time and then I flash the stock kernel again.
Atm it runs perfect for 30 hours now with 245-1401MHz, uv -100mV and did heavy usage today.
Why happens stuff like that when you're busy with school, damn
But thanks for your help untill now.
Sent from my iPad 2 using Tapatalk

Update:
It's running for 62 hours now, with 245-1401MHz, seems like the 122MHz caused it, but not sure, it gotta survive some more days to be totally sure.
But why caused 122MHz bootloops after a long time where it was stable?
So happy, that I don't need a new device, if it keeps stable
Thanks again for your help
Sent from my iPad 2 using Tapatalk

Another - bad - update:
After ~75 hours of uptime I updated some apps, got a few FCs and then it bootlooped, I remove the oc now...
Maybe it needs more voltage after some time of use with oc?
EDIT:
Damn, I really can feel the loss of the 400MHz, fresh started phone lags, never had that with oc.
Horrible
Ok, that's because of a background progress I guess. 20Mflops @ 1GHz and 29 @ 1.4GHz
EDIT 2:
Increased the voltages +25mV, hope that helps, last step before flashing stock kernel.
Most speeds are undervolted -75mV now, but some are @ -175mV like 800-1024MHz now, had -200mV from one of the CM7 kernels before.
Using it @ 122-1401MHz now.
Voltages:
MHz mV
122 825
245 825
368 825
460 875
576 925
652 975
768 975
806 1025
921 1025
1024 1025
1113 1075
1200 1125
1305 1175
1401 1175

That did the trick.
Happy user again
But it's strange that I had to increase the voltages imo
Anyways, works perfect again.
Thread can be closed

whoops missed page 2 sorry
Pvy.

Overclock problem in Cyanogen.

Hi, I'm Spanish, so my English is very poor. I have an HTC Wildfire, and when I installed one rom of Cyanogen, the stable version 7.1, Android 2.3.7 and tried to overclock with the options "Performance", 518mhz of minimum and 768mhz of maximum, the system freezes after a few minutes. I tried several times and with the stable version 7.2, and it is always so. I wonder if you can help me.
Thanks.

Don't clock it to max.
Your phone can't handle it.
Try 528-710 for example.

My phone don't suport 728mhz? Only to 710mhz?

BuzzWildfire said:
My phone don't suport 728mhz? Only to 710mhz?
Click to expand...
Click to collapse
The point I was trying to make is to try a lower frequency. Doesn't necessarily have to be 710MHz

BuzzWildfire said:
Hi, I'm Spanish, so my English is very poor. I have an HTC Wildfire, and when I installed one rom of Cyanogen, the stable version 7.1, Android 2.3.7 and tried to overclock with the options "Performance", 518mhz of minimum and 768mhz of maximum, the system freezes after a few minutes. I tried several times and with the stable version 7.2, and it is always so. I wonder if you can help me.
Thanks.
Click to expand...
Click to collapse
I can't overclock my WF to the maximum too so i clocked it to 729mHz and it runs fast aswell. I don't think you notice the 30mHz difference.

BuzzWildfire said:
My phone don't suport 728mhz? Only to 710mhz?
Click to expand...
Click to collapse
The hardware may vary (slightly or even significantly) in both directions (some people may overclock to more than 768MHz while others even can't up to 710). Varies also with different kernels - but freezes generally are a sign that you've gone over max - independant from your kernel).
From my experience it doesn't really make a big difference if I set 710 or 768 (besides the battery drains faster and my Willy is getting freakin' hot at times) - overclocking is a bit overestimated anyway

After running my wildfire for months at 768 i decided there wasn't much point in going above 633 for the things i did on it. Also the speed margin was minimal.
I'm now on a dual core 1.2ghz s2 running at 1ghz on a single core and its almost doubled my battery life, the 2nd core is hardly used unless its needed so i turned it off, i see no difference in speed but high gains in battery life.....
Sometimes a high Oc isn't what's needed to make a phone faster........
Sent from my GT-I9100 using Tapatalk 2

@ scratch and event
but try getting people to believe these facts!
groundhog days lol......
Forum fishing.... Who's biting!

I tried to 748mhz and the Wildfire are ok. Thanks.

everyone has "different" wildfire. For example you get freezes at 768 Mhz but I don't get it and my willy is getting well with it. Anyway, the biggest difference you can see when you overclock willy to 729 Mhz. Higher is not important because you cannot see any difference in performance. You will only drain your battery life

drewniany92 said:
everyone has "different" wildfire. For example you get freezes at 768 Mhz but I don't get it and my willy is getting well with it. Anyway, the biggest difference you can see when you overclock willy to 729 Mhz. Higher is not important because you cannot see any difference in performance. You will only drain your battery life
Click to expand...
Click to collapse
Thanks. I choose the configuration in 518mhz-729mhz in performance. I'm testing this configuration since eleven hours.

IMO bes configuration is from 264 or 176 to 729 and smartass v2 governor. Low values because when ur phone is in sleep mode it drain ur battery less than on 518 mhz (; give a try (;
Sent from my HTC Wildfire using xda premium

drewniany92 said:
IMO bes configuration is from 264 or 176 to 729 and smartass v2 governor. Low values because when ur phone is in sleep mode it drain ur battery less than on 518 mhz (; give a try (;
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
That's the best configuration for YOU.
Not everyone has the same taste as you

Yes (; for me it is the best so i wrote IMO m8. But i think that this conf. would be much better for battery than yours but urs would be faster of course (;
Sent from my HTC Wildfire using xda premium