• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Dirrk's D01 overclocking kernels with lagfix

NOsquid said:
Which ones seemed to do it for you? Are you in the clear now? If its what those peeps on xda are saying with the cpu locking up in a process i would expect it to be less likely with OC...?
Click to expand...

Yep, I'm in the clear so far for several days on the LV 1100 kernel. I had something freeze on me yesterday, but it was minor. No phone reset required. Little things like that don't bother me once in a while. With the LV and SV 1200 it was several times a day.

Also, just FYI, I decided to be brave and let SetCPU run with 1100 max and 100 min on boot. So far so good. May have found a sweet spot. Battery life has been fantastic.
 
Yeah I'm tempted to as well because i've forgotten to set it after a reboot and wondered why my phone was slow for a good while before remembering.

Tell ya what, be careful with the setCPU widget, it slowed my launcher to a crawl. I used the passive one too, i just wanted it to tell me what profile i had in case i forgot to set it. It was driving me crazy, i was uninstalling all kinds of things until i figured it out. Didn't suspect it would be that.
 
SirKronan said:
Yep, I'm in the clear so far for several days on the LV 1100 kernel. I had something freeze on me yesterday, but it was minor. No phone reset required. Little things like that don't bother me once in a while. With the LV and SV 1200 it was several times a day.

Also, just FYI, I decided to be brave and let SetCPU run with 1100 max and 100 min on boot. So far so good. May have found a sweet spot. Battery life has been fantastic.
Click to expand...

I have the same settings as you SirKronan but my battery life isn't that great recently. I just set SetCPU on boot (1100 max 100min) yesterday, so we will see. I will test it out. I have had the LV1100 kernel since last Sunday. Before I had SetCPU set to start on boot, my battery life was fantastic, but I'll give this the better part of a week to decide how it affects the battery.


On a different note, saps I know you said you uninstalled autokiller. Has that had a positive, negative or negligible effect on your battery life?
 
Mazeraski said:
I have the same settings as you SirKronan but my battery life isn't that great recently. I just set SetCPU on boot (1100 max 100min) yesterday, so we will see. I will test it out. I have had the LV1100 kernel since last Sunday. Before I had SetCPU set to start on boot, my battery life was fantastic, but I'll give this the better part of a week to decide how it affects the battery.


On a different note, saps I know you said you uninstalled autokiller. Has that had a positive, negative or negligible effect on your battery life?
Click to expand...
I'd say negligible
 
Mazeraski said:
I have the same settings as you SirKronan but my battery life isn't that great recently. I just set SetCPU on boot (1100 max 100min) yesterday, so we will see. I will test it out. I have had the LV1100 kernel since last Sunday. Before I had SetCPU set to start on boot, my battery life was fantastic, but I'll give this the better part of a week to decide how it affects the battery.


On a different note, saps I know you said you uninstalled autokiller. Has that had a positive, negative or negligible effect on your battery life?
Click to expand...

I don't use the widget either. The start on boot option works good for some, and for others, not so much. By the way, it's been a few days since I restarted my phone, and today, "android.process" or something like that kept force closing. Everything I was doing seemed to keep working, but it was getting annoying. I restarted my phone, wiped the cache in CW recovery, and now it seems fine again. I can handle a restart every few days. With my Eris it was a few restarts EVERY DAY.
 
SirKronan said:
I don't use the widget either. The start on boot option works good for some, and for others, not so much. By the way, it's been a few days since I restarted my phone, and today, "android.process" or something like that kept force closing. Everything I was doing seemed to keep working, but it was getting annoying. I restarted my phone, wiped the cache in CW recovery, and now it seems fine again. I can handle a restart every few days. With my Eris it was a few restarts EVERY DAY.
Click to expand...

with voodoo kernels i wipe davlick cache every 2 days in recovery and never have a problem
 
nitsuj17 said:
with voodoo kernels i wipe davlick cache every 2 days in recovery and never have a problem
Click to expand...

That must be the ticket then. I'll just clear the cache every couple of days. All day it's been rock solid, and probably will tomorrow. I'll just wipe it before bed. That's maintenance I can handle.
 
SirKronan said:
I'll just wipe it before bed. That's maintenance I can handle.
Click to expand...

saps said:
I really need to not type what Im thinking here :p
Click to expand...

That's maintenance we all can handle.


Seriously though, that made me laugh so hard :D



Anyway, what I was originally going to say before being distracted by saps' post was that I have yet to wipe the davlik cache since I started using my current kernel over a week ago. The only thing I get occasionally is a FC from FancyWidget, but nothing really too annoying to worry about.
 
Mazeraski said:
That's maintenance we all can handle.


Seriously though, that made me laugh so hard :D



Anyway, what I was originally going to say before being distracted by saps' post was that I have yet to wipe the davlik cache since I started using my current kernel over a week ago. The only thing I get occasionally is a FC from FancyWidget, but nothing really too annoying to worry about.
Click to expand...
Yeah I dont wipe as often as SK does :p. Although before I got this 1600kernel I was having some issues with my BW. I havent noticed them since going to this new kernel
 
saps said:
Yeah I dont wipe as often as SK does :p. Although before I got this 1600kernel I was having some issues with my BW. I havent noticed them since going to this new kernel
Click to expand...

BW sucks right now if you don't have the stock 4x5 grid on your homescreens. I've emailed the dev a couple of times and they finally wrote me back something about skins not playing nice with hi-res phones.

Well, I hate to break it to ya, but:

Galaxy S (all variants)
Droid X
G2
Nexus One (and likely 2)
EVO

And many others are all boasting some serious hi res. If you want to rake in the dinars from those customers make your stupid app work right on their phone. It worked FINE on my phone for a while. The next two updates jacked it all up, and I can't get it to display right at all. I'm specifically referring to the weather only widget, as their clock is just a hair ugly compared to free clock alternatives, in my opinion ...
 
I
NOsquid said:
When I removed TW, it ran at 250/325 instead of 270ish and was snappy, but by the end of the next day it was hanging out at 270 again. Reinstalled AK on "strict" and it's been hanging out at 250 for a couple of days now. It could be in my head, but the phone feels quicker with that little bit of extra RAM for cache. Whatever...if something starts acting up I'll uninstall again.

On another note, I should really be slapped when I talk about upgrading my phone. Why risk a Voodoo/Odin fiasco? I'm not that savvy, and I hate using Windows. I've been stable on 1.2LV, it's the first kernel I tried, I've yet to soft brick my phone apart for a brightness widget-related crisis (knock on wood). As it is, my phone is stoopid fast. It loads web pages faster than my dad's iPad over the same WiFi network, Safari pales in comparison to xScope running on this thing IMO. I don't really know why I need more. I don't wanna be the next "help" thread.

I'm sure I'll get over this sentiment quickly when the next best thing comes out :D
Click to expand...

The phone will not use that extra ram as cache. This its not a Windows pc.
 
NOsquid said:
Woke up to dead phone again. Wasnt plugged in this time. Went from close to fully charged to 17% in 6 hours when I turned it back on after battery pull.

Some Google-fu reveals that the phone coma/deep sleep is a known problem on this phone. Root or no root, Voodoo or no Voodoo. Long thread in the Galaxy Q&A forum on XDA. Happens to some people several times a day, others rarely, some claim based on location, some say phone was completely fine for weeks (like mine) then started acting up. Some speculation that it had to do with the phone draining its battery looking for data, or something with the battery management. They say the phone is just stuck, not dead, you can hold power button for 10sec, no need for battery pull (haven't verified this myself). Possibly some background process with mobile data locking the CPU, which also drains battery. Some people fixed by toggling their APN off. Allegedly cured in Froyo. Some say going back to TouchWiz helped. I did a battery stat wipe in cwm just for shits. Also took off the traffic exception in Juice Defender so it shuts my data off even if something is syncing. I don't know if that will really help.

Anyone know if *228 will cause any problems on a rooted/oc/voodoo phone? doesn't seem like it would but never hurts to ask...

[Q] Why my Galaxy S locks up?! (Comatose Syndrome on going investigation) - xda-developers
Click to expand...

Left my phone off the charger again last night and woke with it 7% lower, maybe something I did above helped. Can't say just yet.

For the battery stat wipe I did it, charged it until I got the "full" popup, and used it until it died at 0%, then recharged it to full. May have helped my battery life - I was 39% after 24hrs with light-ish use. ~45min web, 51min phone, ~20 texts.
 
SirKronan said:
BW sucks right now if you don't have the stock 4x5 grid on your homescreens. I've emailed the dev a couple of times and they finally wrote me back something about skins not playing nice with hi-res phones.

Well, I hate to break it to ya, but:

Galaxy S (all variants)
Droid X
G2
Nexus One (and likely 2)
EVO

And many others are all boasting some serious hi res. If you want to rake in the dinars from those customers make your stupid app work right on their phone. It worked FINE on my phone for a while. The next two updates jacked it all up, and I can't get it to display right at all. I'm specifically referring to the weather only widget, as their clock is just a hair ugly compared to free clock alternatives, in my opinion ...
Click to expand...
Good info; isn't 4x4 stock though? I run 4x5 but I thought I changed that. Yeah I use BW more for the clock than the weather, so Im about to start looking for a replacement because sometimes BW just does not reload probably. Admittedly, since upgrading to 3.21 the problem has not shown up:confused:
 
nitsuj17 said:
with voodoo kernels i wipe davlick cache every 2 days in recovery and never have a problem
Click to expand...

I have problems with the launcher being slow (both Launcher Pro and Samsung's). How do you wipe the davlick cache, where is it located?

Does that usually help speed things up? I've gone as far as increasing the minimum speed, works fine for a bit, but after awhile its slow again moving from screen to screen.
 
bezerk19 said:
I have problems with the launcher being slow (both Launcher Pro and Samsung's). How do you wipe the davlick cache, where is it located?

Does that usually help speed things up? I've gone as far as increasing the minimum speed, works fine for a bit, but after awhile its slow again moving from screen to screen.
Click to expand...

lpp is never slow for me. but i also wipe davlik cache every 2 days (on the same kernel) or before every kernel install.

you can do it in titanium backup, but from what I understand it does a half-assed job at it.

boot into clockwork, go to advanced, and wipe davlik cache is in there.

works for me at least with avoiding slowdown :cool:
 
nitsuj17 said:
lpp is never slow for me. but i also wipe davlik cache every 2 days (on the same kernel) or before every kernel install.

you can do it in titanium backup, but from what I understand it does a half-assed job at it.

boot into clockwork, go to advanced, and wipe davlik cache is in there.

works for me at least with avoiding slowdown :cool:
Click to expand...

Thanks, I'll give it a try and post my results.
 
You can try the advanced memory settings in LP too. Also if you happen to have 7 screens with widgets, I don't know if anything will help. Some widgets are worse than others, just have to remove one at a time and see.
 
Well, that's funny. I loaded up SetCPU to see if it's been working lately. I checked yesterday and it was fine. 30 something hours of happy battery life. Checked today, and it's set to 528MHz max and 19.2Mhz min. I've had it on "Set on Boot" for a few days. Where the heck is it getting those settings from?

Anyhow. I autodetected and set it all back. We'll see how it does. I'm gonna restart my phone just for good measure. Gosh it's been running good the last few days though. On 100 and 1100 and apparently this morning on 19.2 and 528 ... (still felt responsive enough I wasn't worried.)
 
Ok, it's doing it again. I cleaned the caches and rebooted. I opened up SetCPU to check, and the autoboot settings of 1100 max and 100 min were displayed, but both sliders were set to 19.2MHz. WHAT IS UP??
 
SirKronan said:
Ok, it's doing it again. I cleaned the caches and rebooted. I opened up SetCPU to check, and the autoboot settings of 1100 max and 100 min were displayed, but both sliders were set to 19.2MHz. WHAT IS UP??
Click to expand...

setcpu doesnt tend to play nice with fascinate kernels. its nothing to worry about though, if you have an 1100 kernel its still running at 100 min and 1100 max

if it bothers you though just autodetect on reboot...i never set on boot though anyway so i always do this as a habit.
 
SirKronan said:
Ok, it's doing it again. I cleaned the caches and rebooted. I opened up SetCPU to check, and the autoboot settings of 1100 max and 100 min were displayed, but both sliders were set to 19.2MHz. WHAT IS UP??
Click to expand...

nitsuj17 said:
setcpu doesnt tend to play nice with fascinate kernels. its nothing to worry about though, if you have an 1100 kernel its still running at 100 min and 1100 max

if it bothers you though just autodetect on reboot...i never set on boot though anyway so i always do this as a habit.
Click to expand...
Yeah honestly I keep setcpu in my dock so its right there when I need it. It literally takes 5 seconds to re-set it. The only kernel I ever set on boot was the 1200LV and that was after I was so familiar with it after a week+ of using it. The new beav and Hex kernels are not getting set on boot from me
 
NOsquid said:
Left my phone off the charger again last night and woke with it 7% lower, maybe something I did above helped. Can't say just yet.

For the battery stat wipe I did it, charged it until I got the "full" popup, and used it until it died at 0%, then recharged it to full. May have helped my battery life - I was 39% after 24hrs with light-ish use. ~45min web, 51min phone, ~20 texts.
Click to expand...

saps said:
Yeah honestly I keep setcpu in my dock so its right there when I need it. It literally takes 5 seconds to re-set it. The only kernel I ever set on boot was the 1200LV and that was after I was so familiar with it after a week+ of using it. The new beav and Hex kernels are not getting set on boot from me
Click to expand...

Yep. I've got it in my dock too. I just wanna clarify, though. Even though it says the 19Mhz thingy on the sliders, is it still working right from boot? The phone seems to run perfectly smooth (although I still get a bit of delay when adding apps to homescreens. The first time it pulls up the list it's a few second delay. Shorter than when TW was still running, but odd on such a powerful phone, nonetheless) and battery life is fantastic. I mean, really fantastic.
 
You must log in or register to reply here.
Back
Top Bottom