Database Users

Dj05 vs dl09

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

[Q] Battery

So I have my phone running Ice Glacier 1.1.6 everything is fine but like I see a significant drop in battery from not much use. and it says display is taking most of the battery power. I have auto brightness on and not many widgets.. Any ideas ??

Do as I did change your blacklight settings and don't use auto bright. Then disable some service using 3rd party apps and trust me there is alot of them that you will never use or need so get rid of them from even starting and if it even restarts have it shutdown. I am also using IGv1.1.6 as I flashed it last night and normally comparing it with IGv1.1.5 its better. Also scale your mCPU with SetCPU and when idle underclock it normally its 800mhz on avg load. Don't waste your battery trying to OC it lol just so you can brag about benchmark. Do this 3 you will see improvement, most folks always talk about uptime but we talk about awake time as thats what really matters.

STHNS said:
Do as I did change your blacklight settings and don't use auto bright. Then disable some service using 3rd party apps and trust me there is alot of them that you will never use or need so get rid of them from even starting and if it even restarts have it shutdown. I am also using IGv1.1.6 as I flashed it last night and normally comparing it with IGv1.1.5 its better. Also scale your mCPU with SetCPU and when idle underclock it normally its 800mhz on avg load. Don't waste your battery trying to OC it lol just so you can brag about benchmark. Do this 3 you will see improvement, most folks always talk about uptime but we talk about awake time as thats what really matters.
Click to expand...
Click to collapse
i dont understand the SetCPU stuff =/

^^^^BUMPP^^^^^

Set cpu is a program you can download that allows you to change the speed your cpu runs at. U can even make profiles so say when ur battery reaches a certain level it will under clock the cpu to run at a lower level to increase your battery life. It also allows you to overclock your phone to run faster but at a significant loss to your battery life.
Hope that helps.
Oh set cpu isn't free now but there are others on the market that do the same thing that are.
Kevin
Sent from my HTC Glacier using XDA App

I have set CPU but I don't understand how to operate it

What most ppl do is set a profile to run at the minimum speed when the phone is turned off to increase batt life..also, use a reasonable on demand setting for all other usage..no need to do crazy overclocking if you dont need the power
Sent from my HTC Glacier using XDA App

oc'd phone heating up during normal use and poor battery life

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

SetCPU app and it's effectiveness? Syndicate Frozen ROM

Hey there, I just a few days ago rooted and flashed the Syndicate Frozen rom and am not getting such good battery life...
I was wondering how big of a difference SetCpu makes on battery life/performance in general? With moderate/heavy use (internet browsing, facebook, email, txt messaging) how much should it improve battery life? am getting around 10hours at the moment with moderately light use... Is there any free alternative app that runs comparatively well?
I guess what I'm really asking is: is it worth it to buy setcpu, and will it make a dramatic difference on my battery life? This Rom is supposed to improve battery life, and I think I read is overclocked to 1.2... Will setcpu let me set this underclocked to 1,0 and then like 800 with screen off, 600 idle? Am new to the android thing [have had my EPIC only around 2 weeks today]
Thanks for any help!

Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.

You can set the speed to.anything you want. If you want battery to be the best then.set it to 100/1000 on demand. If you emwant performance then 100/1200. Also I don't set profiles cause I was reading somewhere that they aren't good to use on any galaxy phone.
Sent From My Evo Killer!

http://www.setcpu.com/
Nice info read up on it and yes you can set it anyway you want like stated above. I bought mine from the market to support the dev for the hard work involved in making setcpu, dont know if you know but it is free for xda members just search for setcpu. It is only $2.00 well worth the price so please support the dev if you can.

063_XOBX said:
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
Click to expand...
Click to collapse
20Mhz would freeze the phone. :O
I personally like running it @ 100 Mhz when screen is off and 1Ghz when screen is on.

Overstew said:
20Mhz would freeze the phone. :O.......
Click to expand...
Click to collapse
I am pretty sure XOBX meant 200, cause your right 20 is pretty much crawling...

Yep, I meant 200, the damn autocorrect kept changing mhz to Hz and I must've clicked backspace one too many times.

Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated

androikid said:
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
Click to expand...
Click to collapse
Don't expect it to magically give you another 4 hours up time. 1 extra hour would be high hopes.

I use SetCPU with the CPU set to 200/1000 and ondemand, and the battery life has improved GREATLY, well worth the $2 to support the Dev, IMO, even though XDA members get it free.

I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.

I have mine set to 100/1200 on demand, and it works well for the demands I put on it. Way low consumption at idle, but when I need something it instantly responds.
I routinely get 16-18 hours off the charger, and put it back on the charger with sometimes as much as 40% remaining, but as always YMMV. A lot of it has to do with the ROM, but I'd say that CPU scaling has realized a tangible gain for me.

dwallersv said:
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
Click to expand...
Click to collapse
Talking about Bonsai ROM tweaks on a Syndicate thread would be like me talking about BMW mods on a Honda forum. Either way, I looked around in the system folders and I can't find the 24-cpu file you're talking about. I upgraded yestereday from the 2.1 SyndicateROM to this, and for the first few hours, the ROM itself was definately quicker...I don't know if that's just because I came from 2.1 to 2.2, not to mention all the other 2.2 tweaks. After a few hours, I completely forgot that I could overclock this to 1.2Ghz. Installing SetCPU and bumping it to 1.2Ghz felt like just another jump. System resource consumption aside, it makes the phone all that much quicker while going between screen, apps list, closing apps, etc.
I could care less about battery life because I've learned to always have a charger around me since my days of the Moment, of hell, even my Treo's. I want fast, SetCPU is something I can see the difference in just from turning it on and off and seeing the differences.

CPU never goes above 1.440 ghz

So I usually use CPUSpy to monitor my CPU usage. This comes in handy once the device is rooted and I can see how custom kernels and settings affect battery life and cpu cycles. My LG G4 is the tmobile variant and obviously not currently rooted. I notice through CPUSpy that my cpu speed literally never exceeds 1440mhz.
I don't have any problems with that per say, everything on the device still runs buttery smooth without anything more than the occasional hiccup or lag. I'm curious if anyone else has monitored their CPU speeds and noticed the same thing? I just find it a little interesting.

CPU spy can't even see the A57 cores so there's no way it can see what speed it's running at.

4 cores are limited to 1.44 the rest are 1.8

I have not used CPUSpy. But CPU-Z will show you the speed of each of the 6 cores. As mentioned, the last 2 are the only ones I've seen reach 1.8GHz, the first 4 seem to top out at 1.4 GHz.

Ok.. Using cpu-z..

That's how mine looks "at rest". When it's sitting quietly, saving the battery. Crank up some apps, and you should see those clock speeds rise.
But, trying to improve my battery life, and keep the temps down, I've been hoping to see those numbers stay low, not actually show how high they can go

I agree.. As ive stated, the device runs great i just found it odd. It even calls it a 1.44ghz cpu in the cpu profile and mostly no matter how hard i push the device i cant break that speed

Right as CPU-Z opens, the clock speeds spiked briefly. I was able to get a screenshot quickly.
Do yours also jump up for a second or two right as the app opens?

This has been discussed already. As the previous post shows, they do get to 1.8Ghz when required.