Related
This is an undervolt test version of my new StupidFast Kernel v1.2.3. This is a TEST release (NO VOODOO). This kernel aims to be fast, compatible, stable, and have good battery life. It is based on my StupidFast v1.0.36.
Code:
Changes since 1.2.2:
Fix for the 0.5-1.0 second pause/lag opening apps/drawer
Scheduling Tweaks
I/O Tweaks
Changes since 1.1.23:
Stock 1ghz @ 1225mV
Changes since 1.1.14:
Tweaked minfree settings
tweaked io scheduler
more compiler flags for cortex/hummingbird cpu
tweaked wifi scan interval to help with battery life
Changes since 1.0.36:
removed custom boot animation to trim size.
using kernel jhash3 instead of jhash2.
optimized compiler flags for the hummingbird cpu.
changed some kernel scheduling timings.
BLN disabled by default (configurable with [url=http://forum.xda-developers.com/showthread.php?t=823922]this app[/url])
You will see that the custom boot animation was removed. It's okay. If you already have v1.0.36, 1.1.4 or 1.1.23 installed on your phone, the animation will stay. If you're new to my kernels with v1.2.3, your old boot animation will be there.
I'm not seeing any lag on the phone. Gallery opens pretty much instantly. Settings->Applications->Manage opens pretty much instantly. Launcher Pro+ pretty much instantly appears when the phone starts up.
Testers could NOT find any audio problems with this kernel using the media player in JT's Clean ROM. I've tested Youtube and Pandora and have had no audio issues. Also, we couldn't find any issues with USB mount/unmount, settings changes, etc.
As always, if you find a bug or what you think might be a bug, let me know. This is NOT the final stable release of the 1.2 kernel. Stay tuned to #samsung-fascinate on FreeNode or @geeknik on Twitter!
Download:
http://dl.dropbox.com/u/6088006/stupidfast-test-v1.2.3.zip
saps from #samsung-fascinate said that v1.0.36 was "far and away the fastest real world kernels I've ever seen, period"
If you like my kernel, show me some love. Donate today!
Thanks to saps, jt1134 my beta testers and the kind folks that donated cash to the cause! Keep fighting the good fight!
sweet. dowlloading now.
Downloading also.
I like your kernels, but I just noticed I am getting a super weird output in ADB when I try using that. I also have superdark ROM so it could be either one.
Ok, I just rebooted and checked again and all is running fine with 1.2.2 in recovery, but not in running android system, must mean its the rom.
Downloading now.. went with full full wipe with jts clean, and still getting popping, on asop player, double twist, pandora
Besides the battery life which is supposed to be increased, is there any other benefit to UV ???? Longer processor life, runs cooler, etc.
What are the drawbacks, if any ???? Does performance take a big hit, etc.
I'm asking more in general terms. Obviously I will observe first hand with this kernel, which I'm downloading now.
mexiken said:
Besides the battery life which is supposed to be increased I assume, is there any other benefit to UV ???? Longer processor life, runs cooler, etc.
What are the drawbacks, if any ???? Does performance take a big hit, etc.
I'm asking more in general terms. Obviously I will observe first hand with this kernel, which I'm downloading now.
Click to expand...
Click to collapse
In theory, as I know computer not cell phone, UV will allow it to run cooler, which does mean last longer (but is that really a problem?) and use less juice while still being as fast as before. If it runs stable you will not see a performance hit and it will better with the battery. It will just freeze your phone if its too low and requires more juice, really no harm can be done, overvolting is more dangerous as that burns up cpus, but you overvolt to make the higher frequency stable. Simple overclocking principals apply, you want the lowest voltage for your cpu frequency.
spyd3r05 said:
Downloading now.. went with full full wipe with jts clean, and still getting popping, on asop player, double twist, pandora
Click to expand...
Click to collapse
are you upping the CPU to 200mhz to run those? I am doing that and its just fine, although I never had a popping problem at 100mhz either. I just set the min to 200 because that cleans up a little bit of the lag too.
Possibly related, every once and a while my phone will just decide to press a soft key on its own, what is that? (that causes a slight skip in the music when I am playing it)
destroyerbmx said:
are you upping the CPU to 200mhz to run those? I am doing that and its just fine, although I never had a popping problem at 100mhz either. I just set the min to 200 because that cleans up a little bit of the lag too.
Possibly related, every once and a while my phone will just decide to press a soft key on its own, what is that? (that causes a slight skip in the music when I am playing it)
Click to expand...
Click to collapse
see if listening to it while hooked to power recreates the problem... i noticed for me atleast its only when plugged in...
I have it up to USB and its not skipping or popping right now, I am also using mixzing
v1.2.2 is the least fastest of all the geeknik kernels for me. There is 1 almost 2 second pause loading and exiting apps unless it was already in memory.
Still faster then everyone elses kernel. And so far battery life looks to be way better on this one but I haven't had it long enough to say for sure.
Nothing has changed on my audio popping issues so I am still using SetCPU at 200min still. I am short 6 hours of battery life like this by my best guestimate... which isn't a big concern for me- just reporting for those who need to make it thru a day without a charger nearby.
Never had any FC's with USB.
Touchwiz/JT's Super Clean ROM
And a thank you to geeknik for all your efforts! love how your pumping these out!
Kernal runs great! No unwanted sounds from the stock music player in jt's rom. USB works just fine. Thanks for your hard work!
are you using setcpu? if so that helped me fix it bumping min to 200... any one else having the problem might try that...
Interestingly enough, this kernel does seem a touch slower than the 1.2.23 regular voltage kernel. Hangs just the slightest bit when firing up and exiting dolphin browser and xda app. Still, appears to be MUCH better with battery life, as the previous geeknik kernels were ravaging my battery.
Definite progress but not quite perfect imho. Still thanks for all your work geeknik, you're killing it with these.
Also fyi, running custom blackhole, with sns and lp
Sent from my StupidFast Fascinate using XDA App
This kernel is running fairly smooth, like the other 2. I can deal with the extra 0.5 second delay when first opening an app, as long as BLN is optional and battery life is extended. Thank you very much for taking the time to come up with these kernels for us. Other kernel providers tend to make their products less accessible for us XDA users, but you take the stress out of the search. Thank you again.
Thank you very much for taking the time to come up with these kernels for us. Other kernel providers tend to make their products less accessible for us XDA users said:
This is because these development forums are filled with junk threads, nobody taking the time to read a Lil bit. Its getting worse and devs leave because of it. Not the devs fault at all. Just a point to make: )
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Can someone explain how to get bln. I saw a post about it but can't find it or I'm over looking it like an idiot
Sent from my SCH-I500 using XDA App
zachsx said:
Can someone explain how to get bln. I saw a post about it but can't find it or I'm over looking it like an idiot
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Re-read the first post of this thread, there's a link to how to enable/disable bln
The uv kernel is a winner of course. I test these kernels for geeknik before he throws them up for the masses. Not just running quadrant [although I do that too] but going thru the real phone stuff itself. The manage applications load, replacing new dock shortcuts, gallery, apps and stuff everything we actually want to see improve with.
I for one never had battery issues with previous stupidfast kernels but I know some did, same this music crackling. It seems to me most of you that do are either running blackhold or deodexed rom though and quite humbly I'd look their for your culprit moreso than the kernel. If there was a music skipping issue from the kernel itself it would manifest itself across the boards but it doesnt.
Anyway, battery life is going to be stellar trust me, under light-moderate use Im only using like 2% per hour here swyping 8-10 texts per hour here, very good indeed
Hey Saps- I see ya on all the forums and your contributions have really helped me out...
That being said I keep seeing an overlook of real world usage in these testings. Can you guys test beyond stock apps? I mean checking stock should be the first thing you do obviously but how many people use the stock music player or the stock browser, etc? I am betting most the people that have the knowledge enough to test these kernels and ROMs aren't using stock functionality and apps.
Please test this kernel with the PowerAMP or Music PlayerPro music apps before writing off the issue.
Use Dolphin to check the internet, etc. Use K-9 to check email, etc.. ya know- use the popular apps during testing also if you could?
Audio cracking, FC's with the USB settings, and I even heard mention of live wallpapers having issues. These reports coming from 3 reported different ROMs.
How are you missing this?
I myself have had great success with battery life on the Stupid Fast kernels. Better then stock kernel for sure. But I've been having to run my battery faster by using my workaround to avoid the music crackling.
JT's Super Clean ROM using TouchWiz
Just suggestions so we can all get on the same page and enjoy these badass mods.
P.S. What ROM are you using during testing of this kernel? I'll gladly switch to fix the issues
So I finally got the 10 posts I need to post here and for my first post I would like to ask, when are we getting Froyo for the Fascinate? I have been waiting for so long and I would like to say that I am starting to get tiJUST KIDDING
Against the backdrop of an imminent 2.2 release, I would like to share these kernels I haxed (read: kanged) together, because nobody else did and I was lazy. Based upon jt1134's recent kernel with the Voodoo sound patch that those of us with decent headphones have been having such a ball with these days, I integrated some fixes from the codebases of some of the very talented devs who are working on this phone.
Included in all of these are the Voodoo lagfix, Voodoo sound, and SirGatez's USB fix for the phone being recognized as a CD drive (also used by Adrynalyne).
Additionally, these kernels include SirGatez's fix to disable the VZW battery check, allowing batteries for the other Galaxy S phones as well as third-party batteries to charge on the Fascinate. Although it looks like for the vast majority of us with the OEM battery, nothing has changed and everything will continue to work as it has, this is untested. While the $6 battery I got from Hong Kong for the i9000 appears to charge fine, I haven't tested charging it very much yet and I must disclaim ALL RESPONSIBILITY should there be some issue with overcharging or batteries exploding. Again, this is only a concern if you are not using a Samsung-branded battery for the Fascinate. Well, the full battery popup works with the Chinese battery I have, and the phone is no longer charging it. Probably means that the fix is good for everyone with no battery explosions. Hooray! I still disclaim ALL RESPONSIBILITY as indicated above
As with all of the kernels based on jt1134's codebase, also included is the new red Voodoo-aware Clockworkmod Recovery. BLN is supported as well.
All in all, I am really happy that all these fixes from near and far work (well, AFAIK) together. I can't think of any fix/tweak that is missing, except for some of the more hardcore things like changing around the task scheduler and memory settings that don't affect day-to-day functionality of the phone as much, but are implemented by some of the real devs out there.
Update 1/31/2011: So as people have been discovering, the 7-step OC is causing some weird problems as far as call signals dropping out and various instability issues for some people, but perhaps not for others. I have spoken to SirGatez about the issue and it is a known issue with timings and such that largely boils down to faulty Samsung code (instead of waiting for a reply when using I2C to talk to peripherals as should be the case, Samsung likes to just shove more data down the pipe, or something like that). Luckily SirGatez seems to know his **** and has almost fixed the issue already in his codebase. As it turns out, although he is on a slightly newer codebase than pretty much everyone else still building DJ05/DL09 kernels (Linux 2.26.9.6 as opposed to 2.26.9, IIRC), the fact that the exact same issues showed up in my kernel and his with the 7-step OC helps him narrow his search considerably. Glad it helped, SirGatez.
For the moment, I would not recommend flashing an OC kernel - I've gone back to 1GHz myself because of the problems. I will see if his fixes are amenable to inclusion into my source tree with the view of releasing a new batch of kernels at some point in the near future.
Frankenkernel download links: (Voodoo only!)
1000MHz, 100% stock (standard) voltage settings: dropbox
1000MHz, Adrynalyne's more aggressive undervolt settings: dropbox
1200MHz, SirGatez's regular 7-speed OC settings: dropbox
1200MHz, SirGatez's undervolted OC settings: dropbox
It bears repeating that I take no responsibility for breaking anything. That said, it should all work fine, but here is an Odin package to go back to an earlier Adrynalyne-built Voodoo kernel + recovery if something breaks working on your phone. I believe this is Test6 from his current thread. dropbox This should also be useful for your after-Odin-to-stock hijinx, if you know what you're doing.
All credit should go not to me, codestealing kanger that I am, but to jt1134, Adrynalyne, SirGatez, and the other devs and users who I either stole code from, have asked lots of annoying noob questions to, or have flashed and tested my kernel. Especially SirGatez, who is apparently a decent dev, but has been toiling away in obscurity. Thanks for getting my $6 battery working, man, come say hi to the rest of us on IRC!
"included in all of these are the Voodoo lagfix, Voodoo sound, and SirGatez's USB fix for the phone being recognized as a CD drive (also used by Adrynalyne)."
Thank you!!!
Cool stuff, thanks. I look forward to trying some of these out and seeing how they run.
quick question.
If I wanted to flash the 1200 MHz UV kernel over my current kernel (adrynalyne's 1/21 UV voodoo), would I have to do any additional steps? I mean, it should be as easy as booting into red cwm and flashing it, right? I just want to be 100% sure.
tripacer99 said:
quick question.
If I wanted to flash the 1200 MHz undervolted kernel over my current kernel (adrynalyne's 1/21 UV voodoo), would I have to do any additional steps? I mean, it should be as easy as booting into red cwm and flashing it, right? I just want to be 100% sure.
Click to expand...
Click to collapse
Yes u can just flash it
Sent from my SCH-I500 using XDA App
So far, very nice! I flashed the iv/ 1200 and its running smooth!
I really like the hack for the batteries. I use a couple on Hong Kongers and it was always a pain the rear to pull them out and charge separate.
Thanks!
Sent from my SCH-I500 using XDA App
tapout27 said:
Yes u can just flash it
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thanks!
btw, the 1200 UV kernel is running great and smooth! Voodoo sound is nice addition too.
Is the uv 1200 kernel also a 7 slot?
Also, if not already done can you upgrade this to BLN 2.3+? It adds blinking capability in BLN control and the newest blinky.
Sent from my SCH-I500
n0yd said:
Is the uv 1200 kernel also a 7 slot?
Also, if not already done can you upgrade this to BLN 2.3+? It adds blinking capability in BLN control and the newest blinky.
Click to expand...
Click to collapse
Yes, it's a 7-slot.
I'm not sure if it's BLN 2.3+ but I just tested on Blinky. It says the enhanced BLN is not found but blinks fine when I test it. Does that mean it's not 2.3+?
SirGatez is definitely an interesting character. Seems to be in his own little world, doing his thing.
Gps
Using adrenalyns kernel, seems to have broke gps on mine. Using super clean. 4 Dl09 with the Dl09 modem.
i know / read that the voodoo sound fix does wonders for the headphone jack listening... however, what about for bluetooth media? (not calls, but actual streaming mp3's over bluetooth to a stereo... which sucks and I want it to sound better ).
anyone that has tried it and can respond, thanks.
dnoyeb said:
i know / read that the voodoo sound fix does wonders for the headphone jack listening... however, what about for bluetooth media? (not calls, but actual streaming mp3's over bluetooth to a stereo... which sucks and I want it to sound better ).
anyone that has tried it and can respond, thanks.
Click to expand...
Click to collapse
This was the First thing I tried as I only use bluetooth headphones with my fascinate. And i can tell you that voodoo sound does nothing about the Bluetooth Audio.
I flashed this last night and was loving the battery life, but today I discovered that I couldn't make phone calls - when I click on the call button a box pops up that says I have no service. I flashed back to one of adrynalyne's test kernels and now it works. Just thought I'd let you know - other than that it was great tho, thank you!
Sent from my SCH-I500 using XDA App
Great!
Flashed the 1200 SV Kernel last night and I've been running great with no obvious glitches. GPS, phone calls, battery life all look good! Thanks!
Flashed this yesterday on top of Superh 09. Runs great with setCPU processor runs a lot cooler. Thanks!
Sent from my SCH-I500 using XDA App
Whitepaint said:
This was the First thing I tried as I only use bluetooth headphones with my fascinate. And i can tell you that voodoo sound does nothing about the Bluetooth Audio.
Click to expand...
Click to collapse
Bluetooth is something that will be looked into. Go find the sound thread in the i9000 forum to see planned features and keep track of development.
I've posted these details in SirGatez thread for his kernel, thought I'd share them here since it's also applicable.
When using your kernel with SirGatez' OC settings, the CPU throttling is really high, it likes to spend times at higher clock rates when at rest. My remedy to it was setting a minimum processor speed of 200 MHz, then the at rest throttling was SUPER TAME, giving the greatest resting battery life I've ever experienced with no performance issues at all.
BUT, sadly your kernel shares the exact same "No Service" bug that SirGatez' does, causing erratic loss of service that has to be waited out, Airplane Mode switch is frozen at this time. This sadly had me have to give up the 7-slot kernel. Otherwise, great experience.
CrushD said:
I've posted these details in SirGatez thread for his kernel, thought I'd share them here since it's also applicable.
When using your kernel with SirGatez' OC settings, the CPU throttling is really high, it likes to spend times at higher clock rates when at rest. My remedy to it was setting a minimum processor speed of 200 MHz, then the at rest throttling was SUPER TAME, giving the greatest resting battery life I've ever experienced with no performance issues at all.
BUT, sadly your kernel shares the exact same "No Service" bug that SirGatez' does, causing erratic loss of service that has to be waited out, Airplane Mode switch is frozen at this time. This sadly had me have to give up the 7-slot kernel. Otherwise, great experience.
Click to expand...
Click to collapse
That's what I had - a "No Service" bug. Glad I am not alone on this one, I was really puzzled when I saw that pop up!
Sent from my SCH-I500 using XDA App
I want to flash the 1200 kernel but I was wondering if there is a significant difference between the regular and uv
Hello - this is a pretty n00bish question but I have had a hard time finding the exact answer I was looking for on this threads and on Google. The Thunderbolt is my first Android phone, and I got it last week and already rooted it with Das BAMF Remix 1.6.3. I also have WidgetLocker, Launcher Pro, and other programs to really customize the phone. I was playing around with the DAS Bamf Toolkit and I was noticing the CPU and governor settings. I was wondering what CPU settings and governor settings people use? Right now I have the default, which is 1.037 Ghz at max frequency, 245 Mhz at min frequency, and using the ondemand governor. I have seen a lot of people use the smartass governor, and I was wondering what the difference does - especially between interactive and conservative (powersave and performance I can guess at what they specialize in). What would be the best settings for optimizing battery life while still having good performance? I know a lot of people say to do your own testing and find out what works best for your phone and your needs, but I am just curious at what other people work at and how they like their settings.
Another question I have it about different kernels. Right now I am using the kernel that came with Das BAMF Remix 1.6.3 (2.6.32.21.bamf_4.4.7-g21c0620-dirty (by a adrynalyne #1)), but I know some people have been using Imoseyon's kernels. Do people find their phone more or less stable when using Imoseyon's kernel on Das BAMF instead of using adrynalyne's kernel? (I figured since he was one of the people who developed Das BAMF, his kernel would work best, but it seems to me a lot of people have been mixing/matching).
One final random question that I thought of while writing this thread, I also only ever flashed Das BAMF Remix 1.6.3; I never flashed any new radio or anything like that because at first I assumed it came with the ROM, but reading some threads on the forum, it seems that comes separate, and I am not sure if the stock/leaked radio is better/worse for battery or if it works with the ROM.
Again, sorry if these sound like very amateur questions but I just want some clarifying on these things and any help would be greatly appreciated. Thank you very much!
Other information about my phone:
Android Version: 2.2.1
Baseband Version: 1.16.00.0402w_1
Kernel Version: 2.6.32.21.bamf_4.4.7-g21c0620-dirty (by a adrynalyne #1)
Build Number: 1.13.605.7_Das_BAMF_Remix_1.6.3
Software Number: 1.13.605.7
Expiramenting with what combination works for you is the best idea, HOWEVER, always backup what works, and make sure you have the right radio for the ROM you're flashing. Three quarters of what makes this fun is funding out what will and will not make your phone better. The other half is learning how to fix what you just broke.
Also, In my expierience, overclocking to anything over 1.6ghz causes problems.
Sent from my super duper deluxe rooted re-romed Thunderbolt. ( and yes, it can also wash my car AND do the dishes)
heres a list of readios ---> http://forum.xda-developers.com/showthread.php?t=1045081 im on das bamf 1.6.3 with the first one on this list and it works great. also im on that same kernel overclocked to 1280 max and 368 min and i have great speed and battery life (also using setcpu and underclocking to 368 max when screen off so thats probably why ). using the ondemand governer. never tried smart ass but heard good things. the conservative is good for saving battery i use it on my screen off profile.
Awesome, I am going to try to flash that radio... Is it bad that I am not flashing it around the time I flashed the ROM, or would that still be fine? And again, I am sorry if this next question sounds amateur, but to flash it, I would just copy the PG05IMG.zip to my SD Card, reboot my phone in Bootloader (or Recovery?) and install the radio from there (assuming I first wipe the cache/dalvik, or do I need not to do that for radio?).
My battery life is fine, I have the extended battery and I get about 31 hours (but I am on Wi-Fi a lot instead of 3G, which I heard is better for battery, and I am not that heavy of downloading/games), but I heard people getting 2+ days, so maybe flashing this newer radio may show improvements, who knows, ha.
I will have to download SetCPU, because at first I thought you can only change the CPU settings on the Das BAMF Toolkit, but it looks like SetCPU has a lot more options. Dak_181, when you say you have great battery life/speed, how much out of your battery do you get?
BACKUP when making these changes. 10 minutes can save you an hour.
Right, I use Nandroid and Titanium Backup - if I were to flash a new radio as well as Imoseyon's 2.5.1 kernel, should there be an order I do it in (radio first, then kernel, or kernel first, then radio?), or does it not matter?
smartass is interactive gov with some tweaks (interactive makes the CPU clock up faster when you interact with the screen) and basically does a conservative screen off automatically. i think the max clock speed on the TB Is like 400 while the screen is off. i might be wrong on that number but you get the idea.
Zepius said:
smartass is interactive gov with some tweaks (interactive makes the CPU clock up faster when you interact with the screen) and basically does a conservative screen off automatically. i think the max clock speed on the TB Is like 400 while the screen is off. i might be wrong on that number but you get the idea.
Click to expand...
Click to collapse
InteractiveX sets the cpu @ about 250 ish when the screen is off. That is the lowest idle state for the most part, I did however see some testimg trying to get 184mhz to work.
Sent from my ADR6400L using XDA App
Aup808 said:
Awesome, I am going to try to flash that radio... Is it bad that I am not flashing it around the time I flashed the ROM, or would that still be fine? And again, I am sorry if this next question sounds amateur, but to flash it, I would just copy the PG05IMG.zip to my SD Card, reboot my phone in Bootloader (or Recovery?) and install the radio from there (assuming I first wipe the cache/dalvik, or do I need not to do that for radio?).
My battery life is fine, I have the extended battery and I get about 31 hours (but I am on Wi-Fi a lot instead of 3G, which I heard is better for battery, and I am not that heavy of downloading/games), but I heard people getting 2+ days, so maybe flashing this newer radio may show improvements, who knows, ha.
I will have to download SetCPU, because at first I thought you can only change the CPU settings on the Das BAMF Toolkit, but it looks like SetCPU has a lot more options. Dak_181, when you say you have great battery life/speed, how much out of your battery do you get?
Click to expand...
Click to collapse
it doesnt matter when you flash the radio, and you dont need to wipe data or cache. to install put it on the root of your sd card and reboot into.. recovery? whichever one you get to by powering off then holding down volume and power untill it starts up. it will find the update and install it automatically then reboot. make sure to delete it from sd card right away or youll get problems next time your flash anything. and i got about 15 hours with the stock battery and pretty consistence use in a low coverage area (bouncing between 1x and nothing all day).
15 hours with NO 4G I presume? I got about 8 hours of medium use in a good 4G coverage area. I am running BAMF 1.63 with BAMF Toolkit CPU on SmartAss gov. No overlooking.
Does it make a big difference to install the kernel first or the radio first? Also, does anyone think they find better results using Imoseyon's 2.5.1 kernel on Das BAMF Remix 1.6.3, or do they find using the stock kernel for that is best since it was made for that ROM?
And thanks for all the help about installing!
I am getting ridiculously good battery life and performance with Das Bamf 1.6.3 and Imoseyon's leankernel 2.5 running on extreme with custom undervoltage and interactiveX governor.
One of the key contributors to my battery life is the custom undervoltage. The leankernel extreme is already undervolted, but to be compatible with more TBs it isn't undervolted as much as it can be. After the tweaks i made, which included setting the min clock speed to 368 since I have it using the same low voltage as 245 (750 mv).
I have heard that smartass also gives great battery life with imoseyon's kernel, but since interactiveX has been so good I have had no desire to switch.
I hope that helps!
lanwarrior said:
15 hours with NO 4G I presume? I got about 8 hours of medium use in a good 4G coverage area. I am running BAMF 1.63 with BAMF Toolkit CPU on SmartAss gov. No overlooking.
Click to expand...
Click to collapse
thats right. it was part wifi and part 1x/nothing. i have crappy service in my area. also recently learned that having task killers is useless on the thunderbolt and its actually draining my battery. gonna see if it changes without it today
If I were to install the radio using ClockwordMod Recovery (I guess the option to install .zip from SD Card), and it happens there is something wrong and I want to go back to the stock radio I had, would that be where Titanium Backup/Nandroid comes in play, or do they not backup radio stuff, and I would have to find another .zip of the stock radio?
(Again, sorry if this sounds n00bish, I am just very new to this and I want to be sure I know what I am doing, I appreciate all the help I am getting here, it is awesome )
thegeebo said:
I am getting ridiculously good battery life and performance with Das Bamf 1.6.3 and Imoseyon's leankernel 2.5 running on extreme with custom undervoltage and interactiveX governor.
One of the key contributors to my battery life is the custom undervoltage. The leankernel extreme is already undervolted, but to be compatible with more TBs it isn't undervolted as much as it can be. After the tweaks i made, which included setting the min clock speed to 368 since I have it using the same low voltage as 245 (750 mv).
I have heard that smartass also gives great battery life with imoseyon's kernel, but since interactiveX has been so good I have had no desire to switch.
I hope that helps!
Click to expand...
Click to collapse
I know about managing the CPU clock, but what is undervolting do? I don't have that option in my ROM, so do I have to download it somewhere?
What exactly the SmartAss governor do?
Yeah, I second lanwarrior, I am confused at how exactly to undervolt my phone? Is that just in the CPU settings when you go and change them in SetCPU or Das BAMF Toolkit?
Radios, have to be renamed to that special name(PG..... Whatever it is lol) and on the root of the SD card. Then you go to hboot (power + volume down when booting) and it will automatically scan for the file and ask to install if it does.
Trying to install the radio from recovery won't work to my knowledge because it can't update the radio that way I believe, only through hboot.
And to revert back to an older radio, there is plenty of radios out there to try and see which one works. If you are planning to upgrade to the new gingerbread radio that was leaked, I'd highly suggest you wait as because of the recent(today) rumors of it super bricking phones. If I left anything out about the radio, feel free to ask.
About the kernels, I'm not too sure about. I do know about the governors mostly, as for the underclocking , it just means that people are making their lowest CPU speed (the Min CPU setting mostly) go lower than normal, pretty much like the concept of overclocking. Kernels tend to be the same but tweaked in many different ways, like how the voltage is and how specific you can be with setting a specific CPU speed.
Some kernels also have more/better tweaks making them faster and more battery efficient.
Best thing to do, is mix and match these things to find the one that you find that works best.
And one last note: ALWAYS MAKE BACK UPS.
I have learned that multiple times by now, especially when screwing around with that stuff
Sent from my ADR6400L using XDA App
Awesome, thanks so much for your help. I just recently found this thread as well that gives good explanations on how to flash using ABD (I am not using their radio, but their instructions are nice: http://forum.xda-developers.com/showthread.php?t=1048128). I still might just copy it on my SD card and then try through Bootloader, the way you described (sounds a little easier to do). And no no, I was not planning on doing the GB radio - I am staying away from GB ROMs and that of sort until the actual release of it and people have been using the ROMs for a bit and know it is stable/will not brick the phone - I am fine with Froyo for now. I plan on just installing the first radio link here (http://forum.xda-developers.com/showthread.php?t=1048128, which is the 1.13.605.7 CDMA/LTE radio combo - I have been told that works fine, but knowing my luck, something might go wrong, ha).
Based on some threads I have been reading, Imoseyon 2.5.1 kernel seems to work very well and seems to have no problem with Das BAMF Remix 1.6.3. I think I might try installing the radio tomorrow, then the kernel, then installing SetCPU and playing around with the SmartAss governor a bit since that also seems to be popular (even though I am not 100% on what it does yet, ha, but I guess I will find out).
I currently get around 31 hours of battery life (with extended battery) on mainly just Wi-Fi and doing minimal downloading and doing some texting/calls, which seems good, but I feel there are a lot of people getting even more so I might try to get more out of my battery.
Well like I said, find what works best and always backup! Haha. I went through a couple different radios to find the best one for me. The other one I tried, would make me reboot a couple times a day randomly. And now the one I'm on, not a single reboot since it has been installed.
But others say it the other way with this one rebooting and the other working, so just gotta find the best.
And don't forget to delete the radio off the SD card root ASAP just in case you get stuck rebooting and need to go to recovery. (Only way to get in without fully booting is through hboot, which will try to install the radio every time only unless it is deleted. ) believe me I have been stuck in a bootloop with a radio on the SD card lol. Only way around it was use my sisters phone to delete the radio from the SD card
Sent from my ADR6400L using XDA App
Oh jeez, thanks for the advice. If you do not mind me asking, which radio are you using/which one gave you the random reboots a day one? Which ROM are you on (if you are rooted)?
So far I've just been using SetCPU for over/underclocking but have never messed with undervolting. I was wondering what most people use if your main priority is undervolting for better battery life. I'm running Siyah 2.6.7 with SHOstock ROM. Any help/feedback is appreciated.
mpkothari said:
So far I've just been using SetCPU for over/underclocking but have never messed with undervolting. I was wondering what most people use if your main priority is undervolting for better battery life. I'm running Siyah 2.6.7 with SHOstock ROM. Any help/feedback is appreciated.
Click to expand...
Click to collapse
Well, undervolting is very tricky. Each CPU differs in its ability to undervolt, so settings that work for one may not work for others. You'd have to do some testing. I recommend either a.) undervolting one tick and run AnTuTu benchmark multiple times as well as a demanding game/app (Run them for a long time), or b.) undervolting one tick and using your phone normally as per your current usage and if by the next morning it's still running as normal, repeat one tick.
Do NOT set "Set on Boot" to on until you've run these tests and have had no issues.
Hope this helps a little.
Do not worry about 1400,1600 mhz till later since that's when your overclocking.
Bump everything else down by 25mv, run the stress test and a few intensive programs like benchmarks/games.
Keep doing that till you start to notice problems and then revert to the best setting you had. (make sure to backup or not set on boot)
Once you go through all that then you can do it for individual mhz and see which can still be lowered.
This should keep you busy for a hour or so.
I'll share what I posted in another thread. Doing stress tests are fine, but if you test throughout the course of a day or more, you have the opportunity to come across situations you might not think of during testing.
Simba501 said:
Ouch....I think the best way to experiment with undervolting is to use Voltage Control. Save the stock settings as your boot settings (it saves everything - governor, frequencies, etc; so, make sure those are what you want them to be as well), then undervolt (at the beginning of the day). If you make it to the end of the day with typical usage, you can save those as your new boot settings. Undervolt further at the beginning of another day, etc. Once you make it to the point where you get locked up, voltage control will set the previous values at boot and you'll know that those are your limits.
EDIT: If you want to play it extra safe, run values for more than one day.
Click to expand...
Click to collapse
I'm at work right now trying not to get easily distracted by xda since I keep checking whether or not an ICS leak has been ported or something. Thanks guys for your much appreciated input. I've been running with all voltage values knocked down by 50mV with the exception of 1.4 and 1.6 GHz. Those I kept stock since I'm not overclocking. So far so good actually with sio/ondemand and Max 500 Mhz. It's surprisingly smooth and battery of course is doing exceptionally well at these settings. Switched over to voltage control for now.
Sent from my SAMSUNG-SGH-I777 using xda premium
I personally have become very fond of voltage control where as I'd previously been using set-cpu for nearly ever since the H1 and mytouch days. Voltage controls just allows more freedom and tweakability.
Alucardis666 said:
I personally have become very fond of voltage control where as I'd previously been using set-cpu for nearly ever since the H1 and mytouch days. Voltage controls just allows more freedom and tweakability.
Click to expand...
Click to collapse
Right there with you. just "converted" to Voltage Control. (thanks Simba!)
K Rich said:
Right there with you. just "converted" to Voltage Control. (thanks Simba!)
Click to expand...
Click to collapse
Heh, glad I'm not the only defector
Simba501 said:
I'll share what I posted in another thread. Doing stress tests are fine, but if you test throughout the course of a day or more, you have the opportunity to come across situations you might not think of during testing.
Click to expand...
Click to collapse
That's the post I was thinking of, I just honestly couldn't figure out where I saw it or who wrote it.
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Just try clearing app data rebooting and reinstalling the app. That problem has happened to me every once in a blue moon and that fixed it for me.
Sent from my SGH-I777 using Tapatalk 2
Thanks, I'll try reinstalling the kernel.
Which app are you referring to? because I had this problem no matter which app I used to change the governor (Extweaks, voltage control, setcpu).
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
bacon_n_icecream said:
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
Click to expand...
Click to collapse
It's the lulzkernel for some-reason :|
I have problem goto smartassv2 it's ok just steps heavy
Thanks for your suggestion. I just moved over to ondemand and its been ok for me. Too early to make any judgments but I'll try smartassv2 next.
Not that I'm glad to that you're having problems, but I'm glad I'm not the only one with this issue. Thanks for the response
Winklie said:
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Click to expand...
Click to collapse
DONT use kernel cleaning scripts. They cause more problems than good.
Sent from my AT&T I777 running AOKP build 3X
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
bacon_n_icecream said:
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
Click to expand...
Click to collapse
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
thanks, I generally do that any way along with the script cleaner
K Rich said:
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
CPU related as well...
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
kbulut said:
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
Click to expand...
Click to collapse
Lots of questions there. Phone overclocking is the same and at the same time different than PC overclocking. I too bought SetCPU and due to bugs and problems have completely abandoned it. Honestly with the exception of running an epeen benchmark there is little incentive to overclock. Find a newer Kernel (I use NEAK which has no overclocking ability) and install it, performance is stellar. You really have to ask yourself, is my phone slow enough that I need more CPU power to make it faster?
To see what time your CPU is spending at a given clock speed, download CPUSpyhttps://play.google.com/store/apps/details?id=com.bvalosek.cpuspy&feature=nav_result#?t=W251bGwsMSwyLDNd, you will be surprised to see your phone spend very little time at it's max clockspeed.
Due to the immaturity of the fab process for our CPU's (well SoC), what is a stable overclock for one person might not even load for another. These CPU's are not like an Intel Sandy Bridge, with 1Ghz of free overclocking, nearly guaranteed. You can certainly play with voltages to try and attain a higher overclock, but at the expense of CPU lifetime, as well as battery.
Additionally, it takes a new Kernel 3 or so full charge, discharge cycles on a phone to really 'settle in' and 'learn' a particular phones battery, while yours got hot, which to me indicates an endless loop of some kind running in the background.
My advice would be as follows: Choose a ROM you like, feel free to play with different Kernels, again, I use NEAK, which does not work for some folks, or crashes or whatever. Give it several days to 'settle in' and if your still not happy with performance or have stability problems, try a different governor/scheduler. You really need to establish a good, solid baseline of your phones performance and make small changes and give them long enough to establish any changes to your phones overall stability. Basically running cowboy through your phone and making changes will have a negative overall outcome. Make small, documented changes, test and see what overall effect this has to your phone's stability and battery life, and make another change.
bacon_n_icecream said:
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Click to expand...
Click to collapse
Lulz has known problem in 3.2b2-1
Gokhan has fixed it in 3.2b2 - 2
Wait for ktoonsez to update it for us
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Thank you so much for the information. Could I simply uninstall the setcpu and go back to normal? Simply reflash the rom and/or kernel? I really like shostock2 with the cherry picker kernel for now. I want to give them a week of try to make my mind. Before the setcpu I think.I was better off
Thanks for the help by the way. I appreciate it.
Thanks for the update about the new siyah kernel. Glad it wasn't just me with the issue. I was going to post this question in the siyah thread but am new to the site so didn't have permission so thanks for finding me all the way over here
Phalanx7621 said:
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going off what I've seen in the Siyah/NEAK threads. Most of the lock-ups/random reboots I've heard people having had used the cleaning script. Either that or its just coincidence.
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
bacon_n_icecream said:
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
Click to expand...
Click to collapse
Hmm, well I've just manually wiped cache and dalvik and have never had problems between roms/kernels.
Sent from my SGH-I777 using Tapatalk 2