Related
Hello i have a HTC G1 with Android 1.6 i downloaded SetCpu 2.10(newest)
but it becomes not higher ?
I tried also custom frequence it still not work
Kernel Version:
2.6.29-00479-g3c7df37
Build Number:
DRC92
Did you bother to stop and consider that maybe 528 is that chip's maximum frequency?
dhkr123 said:
Did you bother to stop and consider that maybe 528 is that chip's maximum frequency?
Click to expand...
Click to collapse
i saw in youtube many people who get the g1 to 650 MHZ
and there is a video he got his g1 to 850 MHZ wow but i cant do it why?
the kernel.
you're using a kernel with a max freq of 528.
don't be tempted and believe everything you see on youtube. ;-) an 850 kernel isn't likely to run stable enough and get you decent uptime.
---
Powered by Android
pl4sMa said:
the kernel.
you're using a kernel with a max freq of 528.
don't be tempted and believe everything you see on youtube. ;-) an 850 kernel isn't likely to run stable enough and get you decent uptime.
---
Powered by Android
Click to expand...
Click to collapse
what is a kernel ?(sorry im a noob
how can i flash my kernel..?
The kernel is core part of any operating system. You will need to find an android build (read: ROM) that incorporated a kernel that will allow you to crank your MHz up to the desired level.
I also recommend that you be careful when overclocking. I am sure you already know you run the risk of frying your phone.
The maximum stable overclock I've been able to get is 614Mhz (with the ocassional random reboot) and 592Mhz completely stable. How high you can clock your processor is completely dependent on what kernel you're running. I'm using CM6.1 right now and the kernel limits the clock to 614Mhz max. I think about 640Mhz is the highest you can go without making it unusable, but you might have a hard time finding a current kernel that lets you overclock that high.
And anyways if you're looking for more performance the CPU isn't the bottleneck. It's the RAM. You should look into swap or compcache to get more performance out of your G1.
592 has been my best stable speed as well with Froyo and now with GingerYoshi 595 is fastest stable for me. Can clock higher but then random reboots and fc's
Download link: http://goo.gl/vzEB4
FAQs: http://forum.xda-developers.com/showpost.php?p=11436660&postcount=11 (Thanks Alienz!)
Yes, the kernel is still based on the i9000 JPX source release. Hopefully we get real source soon.
Main Features:
NEAR STOCK BATTERY!!! (Thanks Morfic!)
Overclock up to 1.4Ghz.
BLN (Backlight Notifications).. A basic app is included to turn it on if you want it
Voodoo lagfix v5
Voodoo Sound v4
Many parts of the "speedmod" patch from the i9000 forum
OC is based on raspdep's OC patches, also from the i9000 forum
Various speed tweaks
CIFS/SMB and NFS support compiled in (no modules)
Tunnel support compiled in (no modules)
Changes since 3.2:
New boot logo. (Thanks Alexia!)
Added battery drain fix in standby discovered by Morfic. Should be about the same battery as stock now.
Voltages and frequency scaling have been adjusted to more quickly jump to higher frequencies and come down slower. Improves response time while you use the phone.
The Voltage Control app has the correct voltages, I recommend leaving the lower speeds alone to start with. Going too low can cause the sleep of death. That's why they are as high as they are. NOTE: The voltage control app does not control the available states they way the older ones do. That screen is useless, ignore it. Set your max and scheduler if you wish, and the voltages if you want to change them.
SetCPU.... If you want to use it, you can have it set min/max. If you set profiles, don't set the max under 800. The phone needs 800 to be available. I use a screen off profile at 100-800 just to keep the OC disabled while sleeping. No reason it should need to really crank up the speed if I'm not looking at it. SetCPU is NOT required, I'm offering this as a tip for fans of that application.
The kernel has proven stable for a number of testers so far. If you get crashes, disable any OC/UV settings and try again. I recommend you only change one setting at a time, and NOT set at boot until you have run for a while to ensure you can run stable at that voltage/speed.
Great job testing it out now. Edit: screen is a little dark but the kernel is super smooth
Sent from my SGH-T959 using XDA App
Going to test! Will post results in a couple of hours.
onix
I am considering flashing this new kernel but have a couple of questions I would like to ask first. I am currently on Bionix V 1.21 and love it. Is this kernel compatible with Bionix V 1.21? It appears that this kernel is Voodoo enabled so I presume I would not have to disable voodoo. If I decide to go back to the Kb1 with voodoo enabled which I believe is the stock kernel for Bionix V 1.21 would i just flash the kernel( is is available on TW forum?)or would I have to flash the whole rom again? I would think I would not have to but want to be sure before I leap. I would not like to have to ask for help for problems that could have been avoided by reading and asking questions. Any and all help is greatly appreciated.
Is it ok to not use set cpu? Will this kernel will oc over 1000?
ttabbal said:
Download link: http://goo.gl/vzEB4
Yes, the kernel is still based on the i9000 JPX source release. Hopefully we get real source soon.
Main Features:
Voodoo lagfix v5
Voodoo Sound v4
Many parts of the "speedmod" patch from the i9000 forum
OC is based on raspdep's OC patches, also from the i9000 forum
Various speed tweaks
CIFS/SMB and NFS support compiled in (no modules)
Tunnel support compiled in (no modules)
Changes since 3.2:
New boot logo. (Thanks Alexia!)
Added battery drain fix in standby discovered by Morfic. Should be about the same battery as stock now.
Voltages and frequency scaling have been adjusted to more quickly jump to higher frequencies and come down slower. Improves response time while you use the phone.
The Voltage Control app has the correct voltages, I recommend leaving the lower speeds alone to start with. Going too low can cause the sleep of death. That's why they are as high as they are. NOTE: The voltage control app does not control the available states they way the older ones do. That screen is useless, ignore it. Set your max and scheduler if you wish, and the voltages if you want to change them.
SetCPU.... If you want to use it, you can have it set min/max. If you set profiles, don't set the max under 800. The phone needs 800 to be available. I use a screen off profile at 100-800 just to keep the OC disabled while sleeping. No reason it should need to really crank up the speed if I'm not looking at it.
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
This kernel is much more stable for me than the dow kernel. Great work.
tenbeau said:
I am considering flashing this new kernel but have a couple of questions I would like to ask first. I am currently on Bionix V 1.21 and love it. Is this kernel compatible with Bionix V 1.21? It appears that this kernel is Voodoo enabled so I presume I would not have to disable voodoo. If I decide to go back to the Kb1 with voodoo enabled which I believe is the stock kernel for Bionix V 1.21 would i just flash the kernel( is is available on TW forum?)or would I have to flash the whole rom again? I would think I would not have to but want to be sure before I leap. I would not like to have to ask for help for problems that could have been avoided by reading and asking questions. Any and all help is greatly appreciated.
Click to expand...
Click to collapse
Im not sure if you have to disable voodoo or not .. probably not but don’t take my word for it and no you do not have to flash the whole rom again, just the kernel. Thanks for not clogging up the forums. Lol I know its hard to ask questions in the vibrant forums, (cause you'll get beaten to death with mean comments) but ask them anyway, someone will answer eventually. Ignore the whiny, ungrateful 2 year olds that somehow wandered onto this forum...
Sent from Bionix powered vibrant! If I helped, hit the thanks button!
I flashed without disabling voodoo
treyvaporizer said:
Im not sure if you have to disable voodoo or not .. probably not but don’t take my word for it and no you do not have to flash the whole rom again, just the kernel. Thanks for not clogging up the forums. Lol I know its hard to ask questions in the vibrant forums, (cause you'll get beaten to death with mean comments) but ask them anyway, someone will answer eventually. Ignore the whiny, ungrateful 2 year olds that somehow wandered onto this forum...
Sent from Bionix powered vibrant! If I helped, hit the thanks button!
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
tenbeau said:
I am considering flashing this new kernel but have a couple of questions I would like to ask first. I am currently on Bionix V 1.21 and love it. Is this kernel compatible with Bionix V 1.21? It appears that this kernel is Voodoo enabled so I presume I would not have to disable voodoo. If I decide to go back to the Kb1 with voodoo enabled which I believe is the stock kernel for Bionix V 1.21 would i just flash the kernel( is is available on TW forum?)or would I have to flash the whole rom again? I would think I would not have to but want to be sure before I leap. I would not like to have to ask for help for problems that could have been avoided by reading and asking questions. Any and all help is greatly appreciated.
Click to expand...
Click to collapse
It is compatible with Bionix 1.2.1, that's what I developed it on.
If you have the red voodoo recovery, there is no need to disable voodoo for flashing. Generally speaking, kernels can be flashed without disabling voodoo in any case.
This is what iv'e done, I've lowered my Volts on some clocks, 1000 and up, and I was wondering should/can I use setcpu for profiles?
Answers to COMMON questions:
1. Can I flash this over Voodoo or RFS (stock)
You do NOT need to disable Voodoo. Flash right over Voodoo or RFS kernels. Make sure you are not running JFS though. JFS is not supported
2. How is stability? Does it crash? Sleep of death? etc?
Stability on this is AMAZING. It will not crash unless you overclock/undervolt and your settings are unstable. If that is the case, you know its your settings.
3. Do I need SetCPU to overclock?
You do not need to use SetCPU (You can if you want to). Use the Voltage Control App to overclock.
4. How do I overclock? Can I use this without an overclock?
By default, the kernel will boot to 1.0Ghz. To OVERCLOCk to 1.4Ghz (or lower) you need to use the app that this kernel installs during the flash. The app is called "Voltage Controll" and can be found in your app drawer after the flash
5. What is the battery life?
Battery life should be close to stock now. The battery drain issue that was present in the I9000-based kernels earlier has been solved.
6. Does this support BLN (Back-light-notificaations)?
Yes. You need the BLN control app from the market to use it.
7. How do I use Voodoo sound? What is it?
Voodoo sound is a vast improvement to the sound quality of your phone. To use it, download the Voodoo Control app from the Market.
8. What ROMs is this compatible with?
This is compatible with ALL Vibrant Froyo ROMS. This means 2.2 ROMS made for the Vibrant. 2.2.1 is not yet tested but should theoretically work.
I hope this helps.
ttabbal said:
It is compatible with Bionix 1.2.1, that's what I developed it on.
If you have the red voodoo recovery, there is no need to disable voodoo for flashing. Generally speaking, kernels can be flashed without disabling voodoo in any case.
Click to expand...
Click to collapse
Thanks so much for your kind and patient and swift reply. Donation just made. I really admire yours and all of TW generosity and patience with noobs like me. I am flashing the kernel now. Thanks again for sharing your brilliant work!!!!!!!!!!!!!!!
cashyftw said:
This is what iv'e done, I've lowered my Volts on some clocks, 1000 and up, and I was wondering should/can I use setcpu for profiles?
Click to expand...
Click to collapse
You can use setcpu for profiles, just keep 800Mhz available. The phone will likely crash if you don't. I set a screen off profile of 100-800 to keep the oc disabled when I don't need it, as 800 is a lower voltage.
Hint with voltages, try to keep 1000 and higher at the SAME voltage. Changing the voltage too often can cause instability as the voltage regulator doesn't adjust as fast as we would like sometimes. OC makes this worse as you need a higher voltage to maintain a stable CPU at the higher frequency. The kernel is set to jump to 1000, then to the max set clock speed. Setting 1000 to the higher voltage gives us some extra time to stabilize the new voltage before the just into the OC speeds.
tenbeau said:
Thanks so much for your kind and patient and swift reply. Donation just made. I really admire yours and all of TW generosity and patience with noobs like me. I am flashing the kernel now. Thanks again for sharing your brilliant work!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Thanks for your kind words and the donation. I'm glad you find my work useful.
just flashed this..
and a few questions ive never used OC before..
What does VOODOO Sound really do?
I set my thing on SetCPU as 1.4ghz as max and .1 as low with conservative.
then a profile with screen off and on conservative.
will those save battery?
xriderx66 said:
just flashed this..
and a few questions ive never used OC before..
What does VOODOO Sound really do?
I set my thing on SetCPU as 1.4ghz as max and .1 as low with conservative.
then a profile with screen off and on conservative.
will those save battery?
Click to expand...
Click to collapse
SetCPU by itself will NOT overclock. You need to use the Voltage app that comes with the kernel. See my above post with the Common questions.
I'd like any of the kernels developers gave me a clue about an issue im having with all custom i9000 based kernels (eugene's and TW's). The problem is with line2 voip app which calls isn't heard in the other end when running these kernels, but in stock/voodoo it works just fine. Please any of you have an idea of what could be going wrong?
thanks.
Okay tested so far, everything is working good (undervolted to about 175 for lower clocks 100-1000 and 75 for higher clocked 1200-1400)
Don't try this, as every phone can't handle some things, i'm just stating.
EDIT: I'm seriously stupid, how do I remove the settings again? I know it's in system/ something
Edit: NEVERMIND fixed
I've never used an OC kernel, was thinking of giving it a try. If I decide its not for me is this like removing a voodoo injected kernel, disable, then flash a diff kernel then delete files?
kcp877 said:
I've never used an OC kernel, was thinking of giving it a try. If I decide its not for me is this like removing a voodoo injected kernel, disable, then flash a diff kernel then delete files?
Click to expand...
Click to collapse
Just flash other voodoo kernel on top of it no need.to.disable voodoo
Sent from my SGH-T959 using Tapatalk
What are the benefits of OC/UV (particularly for CM7)?
I know of improved performance due to OC, but what does UV do in regards to performance. Also, how does an OC/UV kernel compare to one without the option?
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
xredjokerx said:
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
Click to expand...
Click to collapse
You can do either or both but don't have to do both. At some point UVing will cause a crash. Right before that point it can cause performance issues. See the link below for instructions on how to find an optimal UV level to maximize battery savings and performance.
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
OCing improves speed but can also cause stability issues. For a captivate this usually isn't a problem until you get past 1.2 ghz. After that, it depends on the kernel but I have yet to find a kernel that is completely stable past 1.2 ghz under stressful conditions. Samsung designed the processor to handle 1.2 ghz and in theory it can go up to at least 1.6.
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
venomio said:
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
Click to expand...
Click to collapse
Odd as it sounds, my battery life on CM7 is close to 50% better when it is OC'ed to 1.2 ghz and UV'ed than it was on the froyo ROMs under the same conditions.
That really is odd :S I think I'll try it myself.
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!
I have a Samsung S phone.
I am running Cyanogen Mod-7.1.0-NS and Trinity Kernel 1.44Ghz OC version: [email protected]untu #4
The phone freezes at least once a day and the only way to get it back to life is to take out the battery.
Can someone tell me what is causing it and whether I should get a different kernel or ROM on this phone?
Is there a better Kernel to go with this ROM?
Please help!
you know what , i think it is due to the kernel cause as you said it is 1.44 Ghz while the default is 1000 only !!!!!!!!
Should I change the settings back to 1000 then?
OMG yes... why are you even using it overclocked? It's just slowly destroying your phone and drains your battery.
I also think that the freeze is due to excessive overclocking... I would suggest the default 1000 but if you really wanna overclock.. take it to max 1200 .. and if you really wanna overclock to 1400 then do some undervolting too
the oc will only gives you better shoes in bench mark your phone can run very smoothly with oc also.
-----Sent using RemICS-i9000-----
You really shouldn't be overclocking if you haven't done your research and understood what you are doing and its consequences.there is loads of information out there, search. Ask yourself this....will I be upset if I fry my phone?
Sent from the gutter, gazing at the stars
I think you should move to another rom and overclock to maximum 1200 if you desperatly want to overclock, but to be onest...it doesn't help you at all