• 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

saps said:
Thanks bud. I'll see what else today brings. Kinda waiting on birdman too. I plan to be on there tonight so I'll ask some to post it again... unless bird really brings something to the table
Click to expand...

yeah ill leave irc on over night and see whats there when i wake up :eek:
 
Yeah, on eclair we get about .8mflops per 100Mhz give or take. With froyo its like 1.4mflops per 100Mhz. So a 1.2Ghz froyo should be near 17
 
NOsquid said:
Thank you kindly, I'll try to remember to do this once in a while.

Google'd the deep sleep thing and it seems some people attribute this to setCPU. Would increasing the min be the way to go if this sleep issue crops up? Or something more complicated?

How are you liking JT's new hawtness? Is it as fast as Dirrk's OC stuff? Are you talking about his new super clean rom or did he release a new Voodoo kernel on that IRC thing everyone keeps talking about?
Click to expand...

Increasing the min didn't help me at all on the kernels I used that had the deep sleep issue. I haven't checked out these latest ones yet, though.
 
SirKronan said:
Increasing the min didn't help me at all on the kernels I used that had the deep sleep issue. I haven't checked out these latest ones yet, though.
Click to expand...
Yeah I've seen guys trying 200 and even 400 as the low point. That does not cure the problem. Im always run 100 min and while I can admit once or twice I had this problem too I cannot recall what the conditions were and have not been able to replicate it since I got rid of TW and autokiller. Its probably unrelated, Im sure it is. I seem to recall one of the two times was when I fell asleep on the phone and I postulated that perhaps they phone got too warm under my hot body[pun intended :D] Who knows? I dont regularly have the problem and as such dont worry about it
 
Just tried both of jt's newest kernels. The 1Ghz was slow for me. The app drawer thing was laggy. I wasn't impressed at all. So then I loaded 1.2 and it was snappier but then I got the same quadrant freezing going up the stairs I always get with jt' kernels at 1200. So Im back to Dirrk's 1200LV. Oh well, Im fine with this. Everything is now as I expect it to be. I cannot explain why but jt's 1200's always are finicky with my SF. No complaints being back on Dirrk though.
 
saps said:
Just tried both of jt's newest kernels. The 1Ghz was slow for me. The app drawer thing was laggy. I wasn't impressed at all. So then I loaded 1.2 and it was snappier but then I got the same quadrant freezing going up the stairs I always get with jt' kernels at 1200. So Im back to Dirrk's 1200LV. Oh well, Im fine with this. Everything is now as I expect it to be. I cannot explain why but jt's 1200's always are finicky with my SF. No complaints being back on Dirrk though.
Click to expand...

interesting...maybe the phones that handle the lv well dont agree with jts kernals as well say the phones similar to mine (cant handle lv)....funny seeing the differences

if id have to give a verdict now, id say the new jt is a tick above dirrks 1200sv for me just in responsiveness and load speed for apps. id like to see how it is when compiled with birdmans new edits.

again id love to see more of dirrks kernles...:( everyone has a life outside of here obviously but he kinda went dark
 
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...

http://forum.xda-developers.com/showthread.php?t=775017
 
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. 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...
Click to expand...

*228 is fine regardless of voodoo
 
AgtHex seems to be working on a 1.4 and 1.6 kernel but like Dirrk his numbers dont give in the benchmarks
 
saps said:
AgtHex seems to be working on a 1.4 and 1.6 kernel but like Dirrk his numbers dont give in the benchmarks
Click to expand...

It had indicated that he was not seeing any gains past 1.3 which to me indicated that the current kernel can hit 1.3 just hasn't been clocked at that in a release yet
 
nitsuj17 said:
It had indicated that he was not seeing any gains past 1.3 which to me indicated that the current kernel can hit 1.3 just hasn't been clocked at that in a release yet
Click to expand...
Yeah saw that. Its funny I have left my irc window open for like 4 days now so I can go back see everything but damn there's a lot of jibber jabber in there. But I totally agree. I dont want/need 1.6 now. Or even 1.4 although that sounds like its close. But shoot throw out a 1.3 at least I need that hit :D
 
saps said:
Yeah saw that. Its funny I have left my irc window open for like 4 days now so I can go back see everything but damn there's a lot of jibber jabber in there. But I totally agree. I dont want/need 1.6 now. Or even 1.4 although that sounds like its close. But shoot throw out a 1.3 at least I need that hit :D
Click to expand...
Yeah beaver said he d try 1.4 later but I'd rather just he throw up a 1.3 and get that stable than these bigger jumps
 
Its nice to have a few new guys in the mix though, especially with jt out of commission and dirrk mia
 
saps said:
Its nice to have a few new guys in the mix though, especially with jt out of commission and dirrk mia
Click to expand...

yeah, jt puts in the legwork and others compile the oc its looks like from now on.....this sounds stalkerish but i checked dirrks xda profile and it shows activity for him recently (i guess just logging in) but no posts in 2 weeks

id love for him to jump back in and push the envelope :D
 
nitsuj17 said:
yeah, jt puts in the legwork and others compile the oc its looks like from now on.....this sounds stalkerish but i checked dirrks xda profile and it shows activity for him recently (i guess just logging in) but no posts in 2 weeks

id love for him to jump back in and push the envelope :D
Click to expand...
Yeah call me a user but I dont care who gets me to 1.3 or 1.4 I just wanna get there
 
SirKronan said:
Increasing the min didn't help me at all on the kernels I used that had the deep sleep issue. I haven't checked out these latest ones yet, though.
Click to expand...

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...?
 
Has anyone run setCPU profiles on Dirrk's LV 1200? Was gonna take it down to 800 when the screen is off maybe?
 
NOsquid said:
Has anyone run setCPU profiles on Dirrk's LV 1200? Was gonna take it down to 800 when the screen is off maybe?
Click to expand...
If you run conservative preset it will take it down to 100 when screen is off; great for battery life. In fact unless you set the preset to performance it will throttle when not needed
 
Have you monitored it somehow when the screen is off? I ask, because if anyone would it'd be you :) It doesn't throttle up for syncing or any kind of background process?
 
NOsquid said:
Have you monitored it somehow when the screen is off? I ask, because if anyone would it'd be you :) It doesn't throttle up for syncing or any kind of background process?
Click to expand...
:p. I dont personally have anything on auto-sync. But even if you did it would throttle right back down when done. There obviously no way to monitor while off. But what you can do is go into the Info tab and make a notation of your Time in State stats, then turn screen off for whatever duration you please and then come back and re-check. In my case I have Handcent set up to give me a pop-up, so the cpu does cycle up for that but otherwise it does rest at 100Mhz when not being used
snap20101022_103740.png
 
You must log in or register to reply here.
Back
Top Bottom