Related
Hey all,
My phone is rooted. I'm wondering how Overclocking might effect battery life. Better? Worse?
Also, what is a solid speed to OC on the Captivate?
It will be worse, but if you do UV it will last a bit longer...
Battery life will go down, but its by such a small amount, you wont even notice it(depending on how much you OC it)
and stable OC values will be different for every phone since all processors are not made equal. For example, my max stable overclock is at 1.2ghz, but my friend was stable at 1.4 with undervolting by 100.
You really just need to play around with it and find what works for you.
If you really want a solid stable number, im pretty sure every captivate I've seen can go up to atleast 1.2 ghz.
Sent from my Captivate using XDA App
Yuna said:
It will be worse, but if you do UV it will last a bit longer...
Click to expand...
Click to collapse
That is very untrue. I read an article (for the life of me can't find it) that overclocking is actually better for battery life. I have in fact had better results on my LG Optimus V with overclocking at 806mHz (highest stable clock setting) than with 600mHz (standard). LeslieAnn (Harmonia dev) linked to the aforementioned article in one of her posts. If I find the link I will post it.
I've only OC a couple of times but 1200Mhz should be stable for the majority of phones out there. The most I've got out of my phone was 1440Mhz on MIUI with Glitch kernel, while my friend was able to hit 1600Mhz with same rom and kernel. It took me quite a bit to figure out what voltages for what steps etc to get it to work well so if you do not feel like tinkering with it for a long while I wouldn't try to push your OC too high.
Battery life doesn't usually decrease unless you over volt. That being said most Galaxy S will get 1.2ghz-1.3ghz on stock voltage. Usually a good idea to undervolt most "steps" except the high clocks (1ghz+) but this varies on phone, rom, kernel, etc.
prbassplayer said:
Battery life doesn't usually decrease unless you over volt. That being said most Galaxy S will get 1.2ghz-1.3ghz on stock voltage. Usually a good idea to undervolt most "steps" except the high clocks (1ghz+) but this varies on phone, rom, kernel, etc.
Click to expand...
Click to collapse
ohh... i thought that said undervolt... but over clocking as well will make it decrease some.
If you ran faster you would burn more energy in the same amount of time. (over clocking)
If you reduced the weight of your legs or gravity you would burn less energy. (under volting).
Most people dont notice battery drain when overclocked because the processor speed doesnt run full speed all the time. it governs to different speeds for what it needs to do.
go stock speed and play a game till it drops to a percentage.
recharge
overclock with NO undervolting and play the game again till the same percentage.
less time. guaranteed.
just sitting at the homescreen and flipping through your app drawer and using face book wont kick your phone into high gear, with stock or overclocking. you will never notice.
TRusselo said:
ohh... i thought that said undervolt... but over clocking as well will make it decrease some.
If you ran faster you would burn more energy in the same amount of time. (over clocking)
If you reduced the weight of your legs or gravity you would burn less energy. (under volting).
Most people dont notice battery drain when overclocked because the processor speed doesnt run full speed all the time. it governs to different speeds for what it needs to do.
go stock speed and play a game till it drops to a percentage.
recharge
overclock with NO undervolting and play the game again till the same percentage.
less time. guaranteed.
just sitting at the homescreen and flipping through your app drawer and using face book wont kick your phone into high gear, with stock or overclocking. you will never notice.
Click to expand...
Click to collapse
I have my phone and nook's clocking speed set at the same for min/max settings. I play a mean game of RUA and AirAttack HD. I've in fact timed my battery life on standard clock settings and my overclocking. While overclocked, my nook lasted 10 minutes longer than at standard speeds (while playing AirAttack HD, which has intense 3D graphics). And you might suggest I undervolted, but I never touch that stuff. My volting stays where it is.
A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.
ZeppeMan said:
A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.
Click to expand...
Click to collapse
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.
set to 1.13 ghz
then screen off to minimum 245mhz
josemedina1983 said:
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.
Click to expand...
Click to collapse
So you underclocked it, what about the speed? It's not to laggy?
Nexus one can run reasonably smooth @ 600mhz and above. It might not open applications as fast as it will be @ 1GHz though.
i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App
shreyas1122 said:
i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I didn't said I want an overclock. It's allready very fast on 1Ghz (compared to my old Hero ), just wanted to know your thoughts about overclocking the N1.
im overclocked at 1152 mhz and profiles set for 245 max with screen off. Overclocking is nice because i like the snappiness but most people cant tell the difference between 998 mhz and 1152. its not needed to overclock but i think profiles help alot. just my two cents
Ok thx, I will try 1150Mhz and see (if it's stable and) what batterylife does. I'm also going to try underclocking.
I have my N1 only for a couple of weeks now and I must say, this phone is awesome. It's VERY fast compared to my old Hero. I remember when I was installing apps on my Hero it became very slow and couldn't do anything untill installing was finished. With the N1 you still can do things while installing apps without lag. The responsiveness and smoothness is also a lot faster. I loved my Hero Because it never let me down, ok it was all a bit slower, but it was getting there. Now with the release of Gingerbread (custom ROM) it became to slow for me and that's why I sold my Hero and bought the N1. It was very difficult to find one, because of the EOL (end of life). But eventually I found one and i'm very happy with it. The N1 is allready more 1 year old, but it still competes with the best phones out there.
I generally run overclocked at 1075MHz, which gives a good balance between battery power usage and processor power. My understanding is that a different voltage scaling method is generally used above 1075MHz, so power consumption will increase above that point.
Didn't knew the voltage would increase above 1075Mhz, will keep that in mind
ZeppeMan said:
Didn't knew the voltage would increase above 1075Mhz, will keep that in mind
Click to expand...
Click to collapse
This is, of course, dependent upon how the kernel is constructed, but this is what I have generally found to be true.
Give us some feedback
I overclocked it too 1075Mhz when screen is on (screen off 245Mhz). Will give my thoughts in a day or 2.
Just report that my battery drain is almost the same as on stock settings. I think it drains a tiny bit faster on 1075Mhz, but nothing major. On the other hand, I don't feel it's faster on 1075Mhz then on stock speed. Only benchmarks give me performance increase.
I'm now on CM6.1.1 with stock kernel (cyanogen), I tried other kernels like Wilmonks kernel,.. Although it was more responsive, battery was going down even faster. I get best battery results with stock kernel.
Hard to choose
more speed = more battery drain
less speed = longer battery
I think I stay with the last option (less speed = longer battery), because Wildmonks kernel doesn't give me enough performance increase over the stock kernel on stock speed.
I have mine at 998mhz, but overclocked 1152 while plugged into power.
Either way, its so easy to play with the clock settings, i'd just have a play with a bunch of different settings if i were you.
liam.lah said:
I have mine at 998mhz, but overclocked 1152 while plugged into power.
Click to expand...
Click to collapse
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One
ZeppeMan said:
wanted to know your thoughts about overclocking the N1.
Click to expand...
Click to collapse
well my thoughts: underclock!
so you can watch movies on it all night!
Sent from my Nexus One
shreyas1122 said:
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One
Click to expand...
Click to collapse
You can use SetCPU to create profiles based on different circumstances.
Me, I have mine clocked to a max of 1075 and min of 245 with the screen on, 576 max / 128 min screen off, 998/128 charging (to reduce heat - overclocking while power is applied can make it silly hot), and a failsafe to clock down to 576/128 if the temperature gets over 50*C.
Fabulous app.
Correct me if I am wrong. When you use setcpu to "ondemand", the CPU speed can ramp up to max whenever necessary, otherwise the speed will tune down to min especially in standby mode. In that way, you can enjoy the advantages of overclocking and underclocking the CPU speed i.e. increasing performance when needed and saving power when not in use, right? When I loaded Rod's MIUI and Wildmonk's kernel, I can underclock down to 128Mhz and overclock up to 1.152Ghz. At the end of the day, I still have over 60% of power left after not so heavily use (some web browsing, checking email and listen some music). Overall, setcpu is a great app for me.
Cyanogen 8? Is this next? Or is this in the works? Also is 2.3.5 next and would it be numbered a different version when Ice Cream comes out? Also is anything coming from the devs to overclock to 800 yet?
cell2011 said:
Also is anything coming from the devs to overclock to 800 yet?
Click to expand...
Click to collapse
It's been done. So very very few phones are even stable at 800, and those that could generally performed worse in benches at 800 than at lower clocks. Many of these devices bootloop above 700.
Cyanogen 8 will not come out yet since will most likely be ice cream sandwich. I am not even sure is 2.3.5 will even come out and no the devs can not overclock this device to 800mhz because is 768 is the limit of the processor. Most people's phones do not even run that smoothly at 768 anyways. If somehow the dev found a way to overclock it to 800 (impossible btw but this is just a what if kind of statement) since the processor can not handle 800 it would just overheat the thing and cause crashes.
Also, on a side note, this should not be in the Development section. This should be in general or Q&A
This belongs in Q&A for future reference.
CM8 will be next, obviously. It will be based on Ice Cream Sandwich, so no, it won't be in development until ICS is released to AOSP so that the CM team can start using that code. 2.3.5 is an update coming out soon for the Nexus S 4G that fixes wifi and network speed, as well as adding more secure NFC for Google Wallet. It won't really affect us when it is merged into CM7. ICS is expected to be Android 4.0, but it could be 3.5 if Google decides.
There is a kernel that goes over 800Mhz, but anything over 768Mhz can be unstable on some phones. I tried it and there were no real performance gains, but battery life was a lot worse. Performance was actually worse at the highest CPU clock, in my experience. Just stick with 768Mhz. It's stable and chances are that you can get even better performance at a lower clock. I get better battery and performance at 633Mhz. It all depends on each unique phone.
rizdog23 said:
Cyanogen 8 will not come out yet since will most likely be ice cream sandwich. I am not even sure is 2.3.5 will even come out and no the devs can not overclock this device to 800mhz because is 768 is the limit of the processor. Most people's phones do not even run that smoothly at 768 anyways. If somehow the dev found a way to overclock it to 800 (impossible btw but this is just a what if kind of statement) since the processor can not handle 800 it would just overheat the thing and cause crashes.
Click to expand...
Click to collapse
I lol'd at this statement. Did you not read any of the posts above you?
When i began to post there were no posts yet. They must have got posted while i was typing. So seeing as the only post at the time was the op, then yes i did read the post(s) above mine.....
There is a kernel that goes over 800Mhz, but anything over 768Mhz can be unstable on some phones. I tried it and there were no real performance gains, but battery life was a lot worse. Performance was actually worse at the highest CPU clock, in my experience. Just stick with 768Mhz. It's stable and chances are that you can get even better performance at a lower clock. I get better battery and performance at 633Mhz. It all depends on each unique phone.
Click to expand...
Click to collapse
I can confirm that the Godmode kernel was able to push some phones, such as mine, past 800Mhz. Although I had a faster processor speed, my battery would drain incredibly fast as well as overheat. Even though I never hit a bootloop with the kernel, the battery life, overheating, and loss of performance kept me away. Sacrificing too much for having a faster processor speed. Normally I overclock to about 729Mhz and have great battery life, speed and performance in conjunction with a min of 19Mhz and a smartass governor.
Sent from my Hero that never dies! ;D
dastin1015 said:
I can confirm that the Godmode kernel was able to push some phones, such as mine, past 800Mhz. Although I had a faster processor speed, my battery would drain incredibly fast as well as overheat. Even though I never hit a bootloop with the kernel, the battery life, overheating, and loss of performance kept me away. Sacrificing too much for having a faster processor speed. Normally I overclock to about 729Mhz and have great battery life, speed and performance in conjunction with a min of 19Mhz and a smartass governor.
Sent from my Hero that never dies! ;D
Click to expand...
Click to collapse
Thanks. I am glad someone at least confirmed it. I never knew about the godmode kernel as ive only been here for a little bit. Sorry for misinformed post about their not being an 800mhz kernel. As I can see, i was wrong, but also I was correct in saying that the processor can not handle it....sometimes
rizdog23 said:
Thanks. I am glad someone at least confirmed it. I never knew about the godmode kernel as ive only been here for a little bit. Sorry for misinformed post about their not being an 800mhz kernel. As I can see, i was wrong, but also I was correct in saying that the processor can not handle it....sometimes
Click to expand...
Click to collapse
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App
rubyknight said:
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
For some reason my phone never works well with higher clock speeds no matter what rom or kernel i use. I get my best results at 710-352 performance.
In before bierce gives birth over ANOTHER question being in the dev section
Sent from my Android using Tapatalk
rizdog23 said:
For some reason my phone never works well with higher clock speeds no matter what rom or kernel i use. I get my best results at 710-352 performance.
Click to expand...
Click to collapse
Correct me if I'm wrong, but from what I've noticed is that newer Hero's that were sold with Eclair as opposed to the original Donut, when I bought mine, are not able to reach those higher processor speeds past 691Mhz.
Sent from my Hero that never dies! ;D
i bought mine at radio shack back in september and it was still on 1.5 and ive never been able to get over 768mhz without it freezing and bootlooping its different with every hero.
i stay at 352-691 ondemand and thats plenty fast for me
Mine was running 1.5 also and it will run fine at 768 but battery life suffers so I usually run at 352/710 and battery and performance are good (depends on rom kernel)
Where can I get the godmode kernel ....
Sent from my HERO200 using XDA App
I actually got mine two weeks after it came out.....so i mean it could just be that this phone is dead now. I never had a refurb or anything. I got it wet once but it got repaired. I've only had this one the whole time. Do you think that is the issue?
rubyknight said:
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
Hey rubyknight,
just wondering why 19? Ive seen people do that but can the processor really ever do anything at 19? if so, doesnt it affect stuff like wake. Im trying it now just to see for myself. Ive been playing with a really high min value between 480 and 576 with the high at 748 and it actually doesnt only seems to affect battery life a little, both on the .29 and .35 kernels on jaybobs roms and on OMFGB.
Thanks
chalan30 said:
Hey rubyknight,
just wondering why 19? Ive seen people do that but can the processor really ever do anything at 19? if so, doesnt it affect stuff like wake. Im trying it now just to see for myself. Ive been playing with a really high min value between 480 and 576 with the high at 748 and it actually doesnt only seems to affect battery life a little, both on the .29 and .35 kernels on jaybobs roms and on OMFGB.
Thanks
Click to expand...
Click to collapse
It depends on the cpu governor that you use.
nandroids are for
sissies
ch1naski said:
It depends on the cpu governor that you use.
nandroids are for
sissies
Click to expand...
Click to collapse
so update, ive run it at 19/768 on demand all day and after 11hrs 13 min its at 60% thats not bad for my phone! and there was almost no performance difference. Just the slightest UI lag... this is on jaybobs 7/8 with the .29 kernel, with background data off. And my regular usage which is not a lot. but for me its good. i wish I had tried it ages ago.
chalan30 said:
so update, ive run it at 19/768 on demand all day and after 11hrs 13 min its at 60% thats not bad for my phone! and there was almost no performance difference. Just the slightest UI lag... this is on jaybobs 7/8 with the .29 kernel, with background data off. And my regular usage which is not a lot. but for me its good. i wish I had tried it ages ago.
Click to expand...
Click to collapse
I believe that you can set the ramp up frequency and that may help with the lag. Setcpu, advanced settings, I think?
nandroids are for
sissies
Which of the current 2.3 ROMs is considered the fastest/most responsive? Or which ROM would be considered the fastest based on the mods & tweaks used by the developers? I'm not to versed in the technical side of things to discern which tweaks/mods/kernels/etc give way to the most stability, speed, and response and would like the community's opinions on the matter.
Probably CM7, I just started using it and there is never any lag. I haven't even OC'd it yet. This also comes with the price of having to live off a wall charger though.
Sent from my SGH-I897 using XDA App
If you mean fastest in clock speeds, then thats a balance betwen rawr clock and how much battery life you can get out of it. Keep in mind these phones clock easily 1.2ghz-1.3ghz no issues past that you need to increase the voltage. So you can in theory get 1.6ghz-1.8ghz but you will live next to a charger. If you mean fastest on how it feels Id have to say Continuum moved awesome few months back (haven't used it in a while) Atomic Fusion if the ext4 version comes out. But there you should just test them out.
On a side not if you want to OC your phone and not have to pay for the oc app, then Id suggest you stick to I9000 ports or AOSP's like CM7 or MIUI. Native roms like Cognition 5, Atomic Fusion and Nuclear Fusion need Tegrak for OC/UV.
Which of the I9000s seem to run the fastest/smoothest? I've been looking at Dlev and Darky but how does Apex/Symply GS II/Mosaic/Sensation compare?
prbassplayer said:
Keep in mind these phones clock easily 1.2ghz-1.3ghz no issues past that you need to increase the voltage. So you can in theory get 1.6ghz-1.8ghz but you will live next to a charger.
Click to expand...
Click to collapse
I actually read in the Glitch kernel thread that when overclocking, higher voltages doesn't always mean more stability. I'm OC'd at 1.5ghz right now really stable and I was UV'd at -50mv but I just dropped it to -75mv to see if its stable there. I'll keep dropping it till I have issues.
Oh yeah, and CM7's battery life has got WAY better over time, so I'm not having to worry about charging all the time either.
Sent from my Samsung Galaxy S Captivate
Reamer09 said:
I actually read in the Glitch kernel thread that when overclocking, higher voltages doesn't always mean more stability. I'm OC'd at 1.5ghz right now really stable and I was UV'd at -50mv but I just dropped it to -75mv to see if its stable there. I'll keep dropping it till I have issues.
Oh yeah, and CM7's battery life has got WAY better over time, so I'm not having to worry about charging all the time either.
Sent from my Samsung Galaxy S Captivate
Click to expand...
Click to collapse
From my experience to maintain a stable phone i over volt the "step" that's overclocked, and then undervolt the other "steps". Im by no means a expert nor is there a full proof way to do it. Each phone kinda reacts differently on the overclocking past 1.2-1.3ghz.
Which of the I9000 roms should theoretically run faster due to the tweaks/mods used by the developers without the need to overclock?
There if no need to overclock for daily use. Only if you are playing very demanding games. And only during those games.
As for fastest rom....have a search this question gets asked a lot with always the same answer and result:
There is no best rom, all phones are different as well as tastes, what's best for me on my device may not be on yours. Flash and try a few and make you own decision...
CM7 is fastest but Display and Sound quality is not as good as stock ROM .
Before school started for me and i couldnt access a charger when i wanted to, i used MIUI at a stable 1.6 GHz ALL of the time with odemand govenor and i got like 18 hours with moderate use, on Glitch V12! And you dont need to overvolt for higher speeds i have tested it and its better to undervolt higher clocks, i get better battery and performance!
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!
For the 10th time Each phone reacts differently to Overclocking. There is no sure way to get it OC/Uv. On my phone past 1.2ghz i need to over volt.
prbassplayer said:
For the 10th time Each phone reacts differently to Overclocking. There is no sure way to get it OC/Uv. On my phone past 1.2ghz i need to over volt.
Click to expand...
Click to collapse
Well i ran 1.6 GHz undervolted at ever clock speed fine, had better performance than over volting, so its different
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!
Welcome to the Thrillz kernel for LG Thrill 4G (may be compatible for O3D).
Standard disclaimer: You bork, your phone. I take no liability. K?
Includes OC to 1.2 native (no modules) and 100 MHz frequency.
cifs.ko module built in.
Conservative governor enabled.
init.d support native.
More to come.
V2 update includes:
Insecure boot
persistent root shell in adb
Removed 100 MHz frequency (caused more issues than it was worth)
Trying a 200 MHz frequency.
V3 includes:
Lock 200mhz when sleep (was set at 300, swapped due to removal of 300)
---Working on other improvements, may be a week or two due to cleanup of code and removal of non-4430 chaff---
V4
Updated frequencies (300, 600, 800, 1000, 1300)
Lower cpu voltages.
#Note, seems screen is eating more battery than CPU. Will investigate.#
Plan for V5
More governors, possible UV compatible with Xan's Voltage Control app.
If you have suggestions, ideas, please give me them.
I do plan on more governors (maybe smartass, interactive, ect....) more io schedulers (bfq, ect...) and anything else that comes my way.
Special thanks to those who have gone before me and helped my learn what I have: gtg465x, LinuxBozo, and Entropy512 for everything that I've learned from them in the Infuse 4G forums, Excaliburinhand for encouraging me to start my own kernel, CallMeAria, Urabewe, tylerwagler and gtg465x again for what they've done here before me... and to you for choosing this kernel (I know... Video game cheezy, but it's true. )
Git is below, it is under the wagler kernel git as it was what I forked and am pushing to. I decided it's time to get started with this.
And please remember, thanks button is good as is fueling my insanity. If you look at my Infusion kernels, I do recognize my "Insanity Crew." (and if you want to be kept in obscurity, I respect that as well. )
Good job man, everyday this forum gets better.
...fighting ninjas at night. Talking about this and that.
Work pretty good on o3d l'll check battry life let u know later
Sent from my LG-P925 using XDA App
Thanks! Keep the comments and suggestions coming! (hoping for p920h/p925 GB leak and official GB source for p920, but I'm fully supporting this in the mean time. Forward ho!)
So far this is best kernel for my rom (v10kv4) so far I got best mobile speed 1.6up 5down i never got this speed any rom or kernal before best speed i had before 1.5. &4 from thriller
Sent from my LG-P925 using XDA App
I hate to report that my battery life did not impress me at first but after charging it seems to be doing better. But i was losing about 15% every 3 hrs in idle. No wifi data or anything.
Sent from my LG Thrill 4G...
Good to see you guys pushin' the kernel movement forward, and sharing your work.
Good deal on getting that built in overclocking going as well. I've been running the kernel for the past day. I did notice an issue, though. Maybe it's just my phone... But the 300mhz OPP, is not being utilized.
I've attached some screenshots.
I was planning to mention that, will try to fix. (100-300 bug) on battery life, what governor are you running? I've found better life on conservative or on demand.
my battery life is decent not the best try to calibrating battery will give you a decent battery life
bedwa said:
I was planning to mention that, will try to fix. (100-300 bug) on battery life, what governor are you running? I've found better life on conservative or on demand.
Click to expand...
Click to collapse
Usually I'm in hotplug or performance... My device has no service, so it doesn't see "normal use" like most. Most of the time it just sits and sleeps.
So, what I did yesterday, really because I wanted to see if you guys squashed the random reboots I've notice in my own playing with LG's kernel source... Had a fully charged phone, flashed your kernel, ran a few benchmarks, still had over 90%, and just let it sit in hotplug. got back to checking it out maybe 12 hours later, noticed the drain, checked setcpu, and that explained it for me. My phone normally would be 80% to 90% in 300mhz... But I don't think 100mhz is able to accomplish most tasks, so it's always popping out, even when it should be idle sleeping.
One thing for me is wireless tethering.. The device needs to be able to accomplish this in the background, and 300mhz even on a DroidX is able to accomplish this. 100mhz is a no go, though.
If you find it real difficult to get 300mhz functioning with 100mhz, I'd say chop the 100mhz out for now, and give us a bump, or atleast put out a 'high voltage' 1388000 mV(TI's kernel 3.0 number) top slot version of the kernel... The overclock module still works with your kernel, BTW... So, in combination with the voltage bump, those that are real speed freaks can push toward that 1300mhz mark with stability.
P.S. No random reboots, so that gets a big thumbs up!!!
I'm going to try and keep to 5 freqs, going to see if 200 works. If not 300 will be low end. Wanting to see if 1.4 or 1.5 is possible with proper voltage. (we should reach sgs II performance benches at that level. )
bedwa said:
I'm going to try and keep to 5 freqs, going to see if 200 works. If not 300 will be low end. Wanting to see if 1.4 or 1.5 is possible with proper voltage. (we should reach sgs II performance benches at that level. )
Click to expand...
Click to collapse
hehehe twould be pretty nice to rub in the face of the acclaimed best device..
Running new Kernel now, so far seems to be running smooth, max 1200, min 600 on Performance governor
Trekfan422991 said:
hehehe twould be pretty nice to rub in the face of the acclaimed best device..
Click to expand...
Click to collapse
It would be nice but I have yet to see my Thrill out perform my STOCK SGS2 yet with any kind of tweaking.
I only hope it can be done.
sent from my Stock Samsung Galaxy S II
I think I got an issue. Starts to lagg when typing/texting. Maybe its the governor I used. I tried with both concervative and ondemand. Also hotplig too. Conservative had the least amount of lag but still noticeable. The other 2 were way too laggy. Unusable.
I believe that's due to the 100 MHz freq. I rebuilt later night without it and while I am typing this there is no lag for me. Re-uploading V2.
Anyone flashed this can comment on battery life and any issues?
Haven't had it long enough for battery use, but it made slim doomed speedier.
Sent from my LG-P925 using xda premium
Flashed it. So far no lag. Battery life kinda iffy. But it's a brand new battery. I'll clear the stats and see how battery life is then.
No issues, phone feels really fast, more batt drain though. I like it.
Sent from my LG-P925 using XDA App