Related
Can an informed person contrast these 2 roms for me please
Sent from my SCH-I500 using XDA App
I am not informed but I can tell you dl09 broke my GPS. It takes 10 minutes to get a sporadic lock. I had to revert to dj05 in order to fix it.
I'm curious too. So far, I haven't really seen anything, so I haven't upgraded.
I've been running it for a week now. Looks like the GPS doesn't lock as fast anymore compared with DJ05. It also currently has me on the wrong side of the freeway by my office so it's not that pinpoint accurate either. I think the WiFi is faster & stronger on DL09 than DJ05. It's probably not worth making the jump to DL09 but I'm not going to revert to DJ05.
Dj 05 works better...everything works on it. Dl 09 not so much...
Radio DL09 gps did not lock as fast wifi about the same on each.
Move back to dj05 working great for me.
Sent from my SCH-I500 using XDA App
For me, I noticed tremendous increase of battery life with DL09
hkseo100 said:
For me, I noticed tremendous increase of battery life with DL09
Click to expand...
Click to collapse
You are correct. After 8 hours I'm at 72% battery remaining. I think it's because of the under volted kernel.
voghan said:
You are correct. After 8 hours I'm at 72% battery remaining. I think it's because of the under volted kernel.
Click to expand...
Click to collapse
I am starting to not believe that undervolted kernels actually do not save any battery.
I've noticed this pattern with all of the kernels that claim undervolting.
But if what you're saying is true, you can run Adrynalyne's kernel with DJ05 and get better battery life.
I think that's what I'm running. I'm also running a Gingerbread Theme which displays everything black when possible thus reducing battery consumption from the screen, but my phone is still sucking for battery life.
2cents.
RacerXFD said:
I am starting to not believe that undervolted kernels actually do not save any battery.
Click to expand...
Click to collapse
Do you mean you don't believe they do save battery?
I had a UV kernel on my phone for a little while, and there WERE noticeable gains in battery life. It wasn't anything crazy, but running the same programs and the same activity over an 8-9 hour span (sitting at work), I had more battery left at the end of the day with a UV kernel than I did running a normal one.
I didn't really pay much attention to it until I forgot to charge my phone on my way to practice one night. Phone would usually be *****ing to be charged, but it was doing good.
I have been running a lot of different UV kernels over the past few weeks, and there is a point where you go from the UV helping your battery and it hurting battery life. From my testing, as the size of the UV increases, the processor will reach a point where it can keep up at a given clock speed and will then move up as needed. It will get to a point where it's staying at 400/800 clock speeds more often than the 100/200 clock speeds, and the effect is negated.
I'm sure this point is going to be different on all phones, but for my phone is somewhere around a -100mV drop from stock voltages. It will help your battery when sleeping since your phone isn't doing anything, it will use even less power, but as soon as it tries to do something again, the battery life will tank. I also used PowerTutor to look at the usage trend for the CPU, and the system was using more power on average for some larger mV drops. I also started to notice lag as the drops increased, likely due to the processor being unable to keep up.
At the moment, I'm trying to see how a big drop on just the lowest clock speed, and then less of a drop on 200-1000 does. I also made a few adjustments to the scaling factors to help reduce lag at 100/200mhz and keep it in the lowest possible clock speed when running. So far, it seems somewhat promising, though I've only been running my current test for a few hours.
Voltage has nothing to do with how much work the processor can do in a clock cycle. Higher voltages allow faster clock speeds, but the voltage itself doesn't matter if the circuit is synchronized (i.e. has a clock). It's just more likely that you won't be able to run at a given clock speed with a lower voltage, but that will just cause glitches and instability, not less work being done and needing to run at a higher speed.
I realize that it shouldn't matter, but it did. I'm guessing that the lower voltage preventing the CPU from running at the actual clock speed, causing it to high the usage threshold sooner. I could barely keep the phone at 100mhz after restarting with just SetCPU running in the foreground. I didn't look into what was happening much because the battery drain was pretty bad, so I went on to a new test.
Also DL09 is officially supported by vzw....
jv
had my phone charging of my usb on my laptop last night while i was texting a friend, when i noticed that the the Kick stand was getting warm so i checked the temp through my battery widget and found the temp to be 114.5* F I immediatly unplugged my phone and took my case off and the back off to let it cool. I was wondering if this is common or even a safe temp. My setup is as follows
Azrael X 3.1
Net's 2.3 more aggressive universal havs NO SBC
Amon RA 1.8
Max temp for the battery is 60C/140F. I have had temps in that range if I had the screen on for a long time or wifi tether. Around 50/55C though and I would worry.if you notice it often and overclock then I would lower the max cpu frequency.
elegantai said:
Max temp for the battery is 60C/140F. I have had temps in that range if I had the screen on for a long time or wifi tether. Around 50/55C though and I would worry.if you notice it often and overclock then I would lower the max cpu frequency.
Click to expand...
Click to collapse
Thanks for the response on this i'm not overclocked so i guess it was the screen being on to long. I will keep a close eye on it from here on out
Jbcarrera said:
had my phone charging of my usb on my laptop last night while i was texting a friend, when i noticed that the the Kick stand was getting warm so i checked the temp through my battery widget and found the temp to be 114.5* F I immediatly unplugged my phone and took my case off and the back off to let it cool. I was wondering if this is common or even a safe temp. My setup is as follows
Azrael X 3.1
Net's 2.3 more aggressive universal havs NO SBC
Amon RA 1.8
Click to expand...
Click to collapse
You are definitely within safe limits on temperature. The only bad thing is the batteries capacity degrades quicker when at a high temperature, but you will probably replace the phone prior to actually realizing the degradation.
Its fine. Mines been a little higher. I don't like using my phone around those temperatures though.
Sent from my Evo using XDA app.
I've read 120 F as safe. So it's close.
General consensus is that using the phone while on USB tends to yield higher temps, but no one knows why.
Well ill start off by saying I'm new here and this is my first post. I'm also very new to this stuff and have a lot to learn. A buddy of mine recently rooted and overclocked my phone using the sense 2.6.32.21 1.5ghz oc/uv kernel. I currently have it set to 1.19 max 768 min and am experiencing temps above 107 running emulators and just web browsing.. I am also seeing pretty poor batt life even using battery booster and advanced task killer.. any help is greatly appreciated!
Battery apps and task killers tend to have the opposite of their intended effect on battery. Android has a built in utility to watch battery usage, why do you need a 3rd party one? Also do some reading on task killers, you will see why they are unnecessary on Android. I've stopped using one and my phone runs faster and more stable than before.
768 min is VERY high. Might explain the heating and battery life drain quite a bit.
Try this for me, please. Set your governor to interactive and drop your min down to 245. Run that for a whole charge. You may be surprised.
Sent from my PG06100
Also, I second the post above me. Advanced Task Killer and anything like it ultimately cause more harm than good. Battery apps, such as Juice Defender, also shouldn't be necessary. Although, it is YOUR phone.
Thanks a lot for the replys. I set the min to 245 and am seeing serious changes in temps. I also uninstalled atk but installed appkik. I am also still running battery booster but may get rid of it soon.. I feel like this phone should have better batt life. Any suggestions?
bearsblack said:
Thanks a lot for the replys. I set the min to 245 and am seeing serious changes in temps. I also uninstalled atk but installed appkik. I am also still running battery booster but may get rid of it soon.. I feel like this phone should have better batt life. Any suggestions?
Click to expand...
Click to collapse
well they gave some suggestions. which it seems you dont want to listen to. you dont need task killers of any kind
Sorry I'm stubborn. Uninstalling now
No disrespect here, but seriously, if you don't know what and why you're overclocking, don't know the inherent risks, etc, why are you doing it?
Compusmurf said:
No disrespect here, but seriously, if you don't know what and why you're overclocking, don't know the inherent risks, etc, why are you doing it?
Click to expand...
Click to collapse
because all the cool kids are doing it smurf...duh.
But seriously, min. should not be set at anything greater then 245. Only use performance if you are benchmarking. Default at the moment should be interactive.
Just gonna add my 2 cents in from personal observation....after doing some reading on overlooking and stuff I've noticed when going into the different ## modes, the shift usually drops its processor cycles to pretty low numbers in the 200-300 mhz range when its just in standby or not doing anything...it only kicks it up when you need the power. So the heating up is probably caused by constantly running at what used to be its max territory...PLUS youre going above and beyond the original limits/specs at a constant so it never gets to relax even when the phone is idle...I hope that makes sense. So as one poster mentioned keep the min at the stock setting and if you really want to/need to then raise the max mhz to whatever your phone can handle reliably. Correct me if I'm wrong anyone who is more into the overlooked setups. Me personally, stock has been able to keep up with whatever I have thrown at it after 30 days and still getting 25+hrs on one charge.
Sent from my PG06100 using XDA App
I currently have it governed at 245 max screen off. Running 1.2ghz max interactive with no task killers or batt savers. Batt life seems to be somewhat better but temps still creep past 105. Thanks a lot for the info
alittle off of the beaten path, but i tried runing 245/1801 interactive on evervolv and noticed alot of random reboots. set it back at on demand and am having good luck with that. why is everyone leaning towards interactive??
Excuse me if I am wrong it's early and im too lazy to reread up on it but I believe the difference is with on demand there is a slight delay(second or two) and it gradually kicks up to where it needs to be where is interactive is a spike the second you need it...
JAREDR said:
alittle off of the beaten path, but i tried runing 245/1801 interactive on evervolv and noticed alot of random reboots. set it back at on demand and am having good luck with that. why is everyone leaning towards interactive??
Click to expand...
Click to collapse
Interactive is, usually, a lot better for battery life.
If you look at your cpu's scaling history when on the two, TYPICALLY, you'll see a whole lot more time in higher frequencies using ondemand.
That's not to say, however, that with some devices and some kernels they will act the same.
Sent from my HTC Speedy
Can over clocking the phone can burn or cause damage to the hardware except excess battery usage and does overclock an 1ghz processor to 1.5 will really give a boost or its just a gimmick
Sent from my Desire HD using XDA App
Excessive overclocking really did damage your hardware, depends on the quality.. Overclocking from 1.0ghz to 1.5ghz really give a performance boost, in benchmarking.. In real life, only noticeable in process hungry apps, such as 3d games.. Gimmick? Well, if its a gimmick, it won't give any sudden resets or lock ups.. The processor have a safety switch if the temperature increase because of oc'ing.. If it's to hardcore, for example, 1.0Ghz to 1.8Ghz or even 2.0Ghz, for sure you processor will overheat and lock ups.
Well, mine running at 1.5Ghz, no lock ups or whatever..
SAPPH1RE said:
Excessive overclocking really did damage your hardware, depends on the quality.. Overclocking from 1.0ghz to 1.5ghz really give a performance boost, in benchmarking.. In real life, only noticeable in process hungry apps, such as 3d games.. Gimmick? Well, if its a gimmick, it won't give any sudden resets or lock ups.. The processor have a safety switch if the temperature increase because of oc'ing.. If it's to hardcore, for example, 1.0Ghz to 1.8Ghz or even 2.0Ghz, for sure you processor will overheat and lock ups.
Well, mine running at 1.5Ghz, no lock ups or whatever..
Click to expand...
Click to collapse
My phone is running quite happily on 1.84Ghz.No lock ups or overheating.
ttav said:
My phone is running quite happily on 1.84Ghz.No lock ups or overheating.
Click to expand...
Click to collapse
Good for you though.. Mine can only be stable at 1.7Ghz.. At 1.8Ghz, only about couple of mins gaming, and then hang till forever..
niks_5in said:
Can over clocking the phone can burn or cause damage to the hardware except excess battery usage and does overclock an 1ghz processor to 1.5 will really give a boost or its just a gimmick
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
You will barely notice the difference in most circumstances. Even if your phone runs fine at 1.5 or 1.8 ghz it will probably reduce the life of the chip over a prolonged period.
-----
Someone Swyped my idea.
I think it will give minor boost at the cost of burning your hardware
Sent from my Desire HD using XDA App
it will help in cpu intensive tasks, that which require lots of calculations, math stuff, 3d drawing done via cpu, faster cpu, better...
in other tasks, don't even bother, there are lots of other things far slower then cpu.
downside, heating, battery drain, increased rate of damage..!
Im using SetCPU for saving battery life. Set the cpu for 384 while screen is off. Noticed quite a difference.
OP, your asking if a overclocked cpu will give a better performance or if it's a gimmick? Really??
Of course it will give you better performance, that goes without saying but the question is, are you willing to sacrifice battery life? The chip will most probably last for years and years if overclocked but 1 thing that kills chips is heat and volts.
I only overclock when I need to and when I'm done I go back to how it was, usually.
My phone is fast enough at 1GHz, dont need overclocking, all games and apps goes fine fine
Most OC kernals are also undervolted anyway so I wouldn't worry about it
to be honest, i use mine with "underclocked" at 800mhz, trying to get at least a half-hour of battery life... i don't see the point in overclock a 1ghz processor, imo, even with a speed gain, the bad side effects easily override the good ones...
i truly believe that overclock my old milestone was the main cause of the problem that happens after...
thiagodark said:
to be honest, i use mine with "underclocked" at 800mhz, trying to get at least a half-hour of battery life... i don't see the point in overclock a 1ghz processor, imo, even with a speed gain, the bad side effects easily override the good ones...
i truly believe that overclock my old milestone was the main cause of the problem that happens after...
Click to expand...
Click to collapse
I'd look at other reasons for your battery life, if it's really that bad.
I'm running at just a touch above 1GHz with no side affects what so ever and get 24+hrs with heavy use, 30+hrs with moderate use and 40+hrs with light use, and that's never turning wifi / 3G off unless I'm in bed when I switch to 2G.
At 1GHz the OCUV kernal I have installed uses less voltage than stock kernal at stock speeds so in theory it's actually safer.
It's not that bad, but it's not so great as yours too. I got about 16hrs with 'hard' use, what is enought most time, but sometimes i get in home with the blinking orange led. Quite annoying...
I try my best to improve the battery life, but i was becoming a battery freak, or something like that, always checking currentwidget...
I get 3 or 4ma at stand by, what is considered normal, i guess... and always use full brightness, hate to use anything bellow...
Sent from my Desire HD using XDA App
thiagodark said:
It's not that bad, but it's not so great as yours too. I got about 16hrs with 'hard' use, what is enought most time, but sometimes i get in home with the blinking orange led. Quite annoying...
I try my best to improve the battery life, but i was becoming a battery freak, or something like that, always checking currentwidget...
I get 3 or 4ma at stand by, what is considered normal, i guess... and always use full brightness, hate to use anything bellow...
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Full brightness is your problem. I bet it uses like 70% of the current while you use your phone.
going up to 1.8GHz still running stable, thats crazy man!
smurcoch said:
Full brightness is your problem. I bet it uses like 70% of the current while you use your phone.
Click to expand...
Click to collapse
Yep, you are correct, it's using about 75% of the battery...
Sent from my Desire HD using XDA App
Any performance boost on 1.8 ghz
Sent from my Desire HD using XDA App
Quick, and great battery. Overclocking is pointless unless you play games on your phone, or care about your quadrant score.
Sent from my Nexus S 4G using XDA App
Yup, I agree with you
+1
I had a Milestone for 1.5 years on stock ROM (that is 550Mhz), pretty much served most of my needs perfectly....you know, the normal stuff you use your phone for.
I rarely notice my phone is underclocked... with smartass governor, it's more responsive than stock clocks with a less responsive governor.
Battery life doesn't seem improved, but I know that my weak signal is causing the problem here.
synaesthetic said:
I rarely notice my phone is underclocked... with smartass governor, it's more responsive than stock clocks with a less responsive governor.
Battery life doesn't seem improved, but I know that my weak signal is causing the problem here.
Click to expand...
Click to collapse
I Sunni it's different for me.. When in use it seems to drain about the same but last night I set the phone down around 11 worth 84% battery life and got up at 6 with 78% still and that's setting the governor to smartass
It's bad for me because my phone goes without signal about half the time in my apartment. I'll be moving soon so it's not a huge issue, but it is kind of disconcerting to feel my phone heating up from just sitting around doing nothing.
synaesthetic said:
It's bad for me because my phone goes without signal about half the time in my apartment. I'll be moving soon so it's not a huge issue, but it is kind of disconcerting to feel my phone heating up from just sitting around doing nothing.
Click to expand...
Click to collapse
You could try disabling the governor and let one like, setcpu do it? Before I went Incredikernel I set up a profile in setcpu that whenever my screen was off it wouldn't run any faster then 128MHz but when on was set for either on demand or performance. Using two governors at the same time causes lag I've found so you'd have to be running a rom that doesn't already have one (that you can see and change) built in
Yea, this is true. OC'ing I thought it was giving me speed, but I actually took the time to really see the speed on OC'ing and to me it dosent seem to change. Well maybe alittle bit, but still. But yea, so I just hit 1ghz and I just leave it there.
Pete's latest w/Yennob-Base2 kernel at 1ghz and its going good.
kijp15 said:
Yea, this is true. OC'ing I thought it was giving me speed, but I actually took the time to really see the speed on OC'ing and to me it dosent seem to change. Well maybe alittle bit, but still. But yea, so I just hit 1ghz and I just leave it there.
Pete's latest w/Yennob-Base2 kernel at 1ghz and its going good.
Click to expand...
Click to collapse
Yeah I honestly can't tell a difference between running at 998 MHz and 1,113 MHz other than a physically hotter phone and faster battery loss lol
IAmTheOneTheyCallNeo said:
Yeah I honestly can't tell a difference between running at 998 MHz and 1,113 MHz other than a physically hotter phone and faster battery loss lol
HTC-Incredible on Android 2.3.5
CyanogenMod-7 Nightly (8/18)
Chad's Incredikernel-GB #9 (SA)
Click to expand...
Click to collapse
Ahaha, yea. Everytime I would hit 1.3ghz or 1.4ghz for the fun of it, my phone would get that way too. It would get hot and it feels like it would explode in my face and yea battery life would drop like crazy.
Personally, I find myself running into a wall with RAM more than with processor power. I really hope the next Nexus at least doubles it.
No problems with overclocking: http://forum.xda-developers.com/showpost.php?p=16791637&postcount=124
Well the SuperOSR is only for nexus s.. If there was one for the ns4g, well then after reading that, I would be OC'ing like a maniac.
zorak950 said:
Personally, I find myself running into a wall with RAM more than with processor power. I really hope the next Nexus at least doubles it.
Click to expand...
Click to collapse
This. I'm really feeling the loss of RAM coming from a mytouch 4G. That extra 256MB really made a difference. Using juwe's RAM optimization script seems to help, though.
Ehm, how can Ram be a problem?
Android is managing it itself and can't run out of it, usually.
Sent from my Nexus S using XDA App
rentaric said:
Ehm, how can Ram be a problem?
Android is managing it itself and can't run out of it, usually.
Click to expand...
Click to collapse
Things get killed that you don't want getting killed, and when it starts to run low things slow down considerably. It's not that something won't run, but it may run badly, or cause other apps to close that you were multitasking on, which is inconvenient.
I average 16 hours with normal for me use, which is a lot of texting, Facebook, internet browsing, listening to music.
Sent from my Nexus S 4G using XDA App
Skimp Killah said:
I average 16 hours with normal for me use, which is a lot of texting, Facebook, internet browsing, listening to music.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
How so? I normally get around 9-10 hours max with moderate use, also depending on the signal i get half the time.
I use netarchys latest bfs kernel with proton to undervolt all CPU frequencies to -20mv. And I have the CPU limited to 100-800mhz, with the on demand governer. With those 2 thing I get 15-16 hours everyday. I also usually let my batter get down to atleast 5% before charging.
Sent from my Nexus S 4G using XDA App
Skimp Killah said:
Quick, and great battery. Overclocking is pointless unless you play games on your phone, or care about your quadrant score.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
it's true
i always Under clock the phone with SetCPU to save battery life