Related
Ok after bricking one phone, i got a new one and loaded voodoo and dirkks SV1200 kernal. also oc'd to 1200. everything has been perfect and had scores in the 18 or 1900s. this morning i was using my phone and noticed it was very laggy. i checked quadrant scores again and it scored in the 14's. as i ran the benchmark, i noticed it hangs on the I/O 3of4 for longer then usual. i have restarted the phone, no luck. even reflashed the kernal, no luck. I cant think of any new programs or changes to the phone. any ideas?
Jeff5886 said:
Ok after bricking one phone, i got a new one and loaded voodoo and dirkks SV1200 kernal. also oc'd to 1200. everything has been perfect and had scores in the 18 or 1900s. this morning i was using my phone and noticed it was very laggy. i checked quadrant scores again and it scored in the 14's. as i ran the benchmark, i noticed it hangs on the I/O 3of4 for longer then usual. i have restarted the phone, no luck. even reflashed the kernal, no luck. I cant think of any new programs or changes to the phone. any ideas?
Click to expand...
Click to collapse
Well the 3rd I/O test does take the longest to complete. If you are having I/O issues this certainly would give you a fluctuating Quadrant score since so much is I/O affected especially on a voodoo'd SF. Have your other benchmarks taken a dip as well? Does the phone lag in regular use? If its just a Quadrant issue I would not overly panic. Cross check with other benches
My phone did that with voodoo too, I installed dirrks lv 1200, and when I upgraded it started acting up. I did remove the fix before I updated, did everything right, but it still lagged so I just glassed back to stock and did all the steps for remove lagfix. Still on stock kernel now but will install birdman optimized tonight.
Adrynalyne is the man BTW. Ok, as to the OP, have you reset the CPU in SetCPU after you restart your phone? If I don't, I get a score of 1400 ish too.
that would make sense as I believe it resets to 800 instead of 1200
thestigwins said:
that would make sense as I believe it resets to 800 instead of 1200
Click to expand...
Click to collapse
Yes, it resets to 800. 1.2 ghz is nice, I would like to see 1.6. G2 OC'ed at 1450 I believe... Ugh, one day, one day.
No luck with OC kernels
I have tried a few, everytime I get issues. Seems like setcpu just does not play well with this phone. I get 1800 on stock voodoo .2. Don't see a need for the extra conservative 200mhz that an OC can provide. Good luck with the kernels though.
Anyways, as stated, make sure set CPU is set to 1.2 GHz and not 800 MHz which is where it defaults. I use the widgit and crank up the speed any time I'm using the phone, else, I leave it at 800 when charging / idle etc.
Also, go into System Panel (best app killer around) and do an END ALL - it will kill everything... THAN run quadrant. If your scores skyrocket, don't be alarmed. Quadrant likes to have a very clean system to run on, if you have a lot of cached or running applications, Quadrant seems to suffer, I'm assuming due to the delay between it requesting more RAM from Android and the time it takes for it to release it. Seems to make sense as to why it would slow down to me at least based on what I know about how Android handles RAM.
Just make sure to reboot your phone after to restore your normal app library of running apps.
With a 1.2 GHz overclock on jt's voodoo kernel most of us are/were getting about 1925 . I've not ran dirrk's LV kernel, the undervolting is very minimal and I'd rather error on the side of stability, YMMV.
Accused: Everyone flaming & veering off-topic (You know who you are)
Charge: Violation of XDA Anti Spamming, Trolling & Flaming Rules
Verdict: GUILTY
Resolution: All violating posts have been deleted
Warning: Further transgressions might result in a BAN!
COURT'S ADJOURNED!
Most of what is below is still accurate, but see this post for links to the kernel download and important infoshttp://forum.xda-developers.com/showpost.php?p=12397646&postcount=580
1-18-11
v.4 - GB’s Impressive Sounding Name Kernel
* As always, many, many thanks to xcaliburinhand.
* Consolidating Steam and Voodoo/CWM kernels into one thread. The two kernels are the same except for recovery, and jfs support in the Steam kernel.
* Started using a proper changelog
* Implemented Impressive Sounding Name Technology AND Dynamic Naming Technology patches; next update to include Dramatic Use of Imagery, with possible Reference to Mythical Creatures patch.
* Cherry-picked some recent commits not included in JPX source. (Will post source this evening, I hadn’t planned on releasing this just yet, but it seems as though it’s already being packaged into a ROM so might as well, right?)
* CONFIG_ARM_THUMBEE=y, enables ThumbEE processor mode, should give some minor JIT performance improvement.
* config_hz=100. With this value, kernel hz = user hz which eliminates HZ <--> USER_HZ conversions. It should also slightly increase battery life without affecting performance.
* Increased default overclock to 1280 MHz. Your may want to revise your undervolt settings, 1280MHz runs at the same voltage as 1200MHz did/does, so you **may** not be able to undervolt as much at 1280. (Yes, I previously said I wouldn’t go past 1200MHz, but, I feel ok going to 1280 since the voltage hasn’t changed and it’s still well below the max vdd_arm.) Use voltage control or setCPU to limit clock speed if you don’t want to use this. Delete your Voltage Control boot settings before booting this kernel. I’m currently using Voltage Control 3.0a.
* Added Voodoo Sound. I hadn’t really planned on it but there were a lot of requests for it.
* Removed i9000 splash screen and replaced with an old familiar one.
* Want lower screen brightness? I know Hardcore did tinkering with the kernel source to do this, but I really like Screen Filter, it even has a Tasker plugin.
* From previous versions: Backlightnotification 2.3, Voodoo color/video fixes re-enabled against my better judgment and even though single-blind testers couldn't tell me which kernels had it and which did not. .
Downloads of v.4 - The file you want is something like rGB-v.4-011811-XXXXX.zip/tar
By clicking any of these links, you agree to flash delete your Dalvik cache and remove any oc/uv boot settings you have before booting. v.4 ClockworkMod zip at the bottom of this post, tar files of Voodoo5/CWM and Steam below for those of you who like to use Odin.
tar of v.4 with Voodoo5 & CWM recovery
tar of v.4 with Steam recovery
Credits
Xcaliburinhand, supercurio, raspdeep, SztupY, sorry if I forgot anyone else.
Stuff I wrote a while ago and may or may not be accurate any more.
1-6-11
This seems to be stable again. Started over from scratch and added in BLN 2.3. Everyone who was affected by charging problems with the previous kernels has not had a shutdown over the last two days of testing. Hopefully we're good again.
1-4-11
Closed testing on newer kernels until I'm fairly confident the issue is resolved again. I had still been getting intermittent reports of charger instability from the reoriented-balls-1-3-11-ocuv-bln23.zip (#47) kernel. Anyone affected by this please switch back to the 'f' builds below, which is the last known rock solid (I think) version.
-----------------------------------------------------------------------------------------------
This kernel is fast, and this kernel is stable. It's overclocked by default to 1.2GHz, but if you don't want to overclock at all, just install either setCPU or download xan's app which I have attached to this post and set the max clock speed to 1.0GHz. This kernel supports init.d scripts, so you have save your settings and have them load at boot.
1100-1200+ Quadrant score on RFS at 1GHz. 1500-1700+ on /data, /dbdata, and /cache on ext4. ~14.1 Linpack at 1GHz. Compare that to any other kernel available here at the same speed and I think you'll see this one comes out on top. I'm not doing this for donations, I just want to my experience with the phone as good as possible. Since this is a Voodoo 5 kernel, you can also make /system ext4 as well for an even smoother experience. This kernel has great battery life and is very stable as well. And when I say stable, I mean, you can use the phone however you want to, you don't have to do any workarounds to keep it from freezing. (edit - as long as you're using one of the build f kernels it seems...) Although, as always, if you aren't 100% satisfied with any of my products, I will give you a full refund.
What this kernel is -
Kernel for 2.2.1 ROMs, (may work on 2.2, but I haven't personally tested it), built from JPX source, with Supercurio's Voodoo 5, overclocked by default to 1.2GHz with raspdeep's code, and Neldar's backlight notification enabled, and re-oriented with xcaliburinhand's code. The undervolting code has been fixed to keep your phone from dying while charging. I'll not be supporting anything beyond 1.2GHz. I hardly use 1.2GHz myself, and from what I've read, many users (but obviously not all) have stability issues with anything much beyond that. This post from one of the senior Android engineers at Google also struck a nerve with me, and is also part of the reason I'll not support anything past 1.2GHz. Samsung actually wrote most of the code for 1.2GHz into the kernel source but had it commented out, so I don't have a problem providing software that will allow users to push it to that level.
Again, for voltage control, use xan's app. I've attached an older version of the app as I'm not sure if the newer one is backwards compatible with the 'older' methods of power management.
Also, standard disclaimers about how if this blows up your phone or tells your girlfriend she's getting fat, it's not my fault. I've had this kernel on my phone for a couple days, so none of that should happen.
How to install - Either flash in ClockworkMod, or use Neldar's really awesome kernel flashing app.
gb-reorient-12-23-build-f.zip is a zip tarred zImage. Unzip, then flash the tar with Odin, or extract the zImage and flash it with Heimdall or Neldar's kernel flashing app.
gb-reorient-fixed-ocuv-f-cwm.zip is a ClockworkMod flashable kernel.
Some thoughts on undervolting
The whole point of undervolting is to safely do the same amount of work with your CPU while using less energy (ie more battery life). Your phone is idle most of the time, so you can the most from undervolting lower frequencies more. Undervolting is safe WHEN you find the settings that work for your phone. Generally, -75mV seems to be stable for everyone. If you want to push it further, go ahead, but realize that if you push it too far, you phone will freeze, and you'll have to pull the battery. Relatively harmless, but, be aware it can happen. Personally, my phone is perfectly stable at the following settings (from 100MHz to 1000MHz) -125mV, -100mV, -100mV, -100mV, -75mV. These settings may not work for your phone. You might find that you can get by with undervolting a little more, but your system will freeze randomly, so if that happens, don't undervolt as aggresively. So, for example, I found that I can usually get by with -150, -125, -125, -125, -100, but every once in a while the phone will freeze up. And since I want a stable system, I've backed down from that. I can't tell you what to do though, but keep in mind that undervolting too much may lead to system instability.
- If you still want to try to find a oc/uv kernel which works for you, don't undervolt at all and tell me if it still happens with kernel #7 (12-23 build from my other thread). As far as I know, no one has had an issue with charger instability on that kernel. If it does still happen, I need to know the kernel version # and for good measure, the production code under your battery (can someone tell me what the name for this is again, I don't feel like shutting off my phone to check), it will be a number like 08.10, 10.10, etc.
- If even with the 12/23 build f kernels and not undervolting at all, you're still get shutdowns when charging, you probably want to get a different kernel. If you insist upon using that one anyway, try charging via USB instead of the wall outlet, it seemed to happen less frequently on older kernels, and I haven't had a charge death in weeks now, so, I'm good at least.
- See if your phone is one of the ones being recalled. If your phone is under recall and these don't work for you, I'm not sure what else I can do.
- These fixes work for me and a lot other people who had the same problem with other oc/uv kernels. Like I said, we're running these out of spec, so a few unlucky souls might not have phones that can handle this. Or maybe some of these kernels have been sprinkled with pixie dust and others haven't. If you find a different kernel that works for you by all means use it. It's all about choice people.
Thanks. Going to try it now.
I flashed 'em at 94%, so we'll see.
But FWIW- I think I've had MAYBE 2 charge deaths when I was on perception. But I was using Setiron's kernels, so I dunno...
I'll report back in a bit.. gonna let it over-charge for a bit and see what happens.
Darky 7.0.1 with your kernel and 100% battery power for 2.5 hours plugged in to the wall and no power off yet. Hopefully this is the fix, I am tired of leaving my computer on all night to charge on usb
thank you so much for this...been looking for something exactly like this, and seems sleep death is gone
darky 7.0.1 here also.
I had it charge around an hr and a half past 100% and no death!
So we'll see how it does overnight
I'll try it out and let you know how it goes, i charge by ac overnight so I should have the results of it to you by morning I'm using it with Assonance 5.2 by the way.
Well no charge death for me last night...
Sent from my GT-I9000 using XDA App
Absolutely no problem, left on ac all night with an undervolt and everything. Great job with this, it made oc/uv usable for me.
Doc's 6.1.3 + your kernel = 100% joy
I found your thread last night after a long and happy Christmas day with the family. Followed your instructions to the letter. Charged overnight from 45% and woke up to find the phone operating fine. This might be the answer to all our prayers!! Thank you so much!
Runs great with eugenes ginger clone. Slightly better benchmarks than other rom/kernel combos. I peak out at 1.3ghz so 1.2 seems like a good medium. One request though is to look into changing the divider for the gpu. I know we don't need it but its good for bragging. Unhelpful had this and I could set the gpu down to 166.750 For lower clocks to save battery and up to 222.334 (stable) for benchmarks. I never tried other clocks so I don't know if it would work on other settings. It depends on how his code works. but it seems by my math the gpu is divided off a 2000 or 2001mhz frequency. There is a margin of error I guess. and stock is divided by 10. In unhelpfuls code it is divided by 9 (222.334) default but could be set to 10 or 12. If we bump that up to 15 or 20 we might reduce battery consumtion with a gpu clock at 133 or even 100mhz. Id also like to try the divider at 8 for 250mhz. Im curious as to how that would benchmark if its stable.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Ive been charging since 2pm yesterday and its still on. I think you got the fix
No problems here charging overnight. For those who care about quadrant scores, mine was about 250 points higher than the other 1.2ghz kernel I was using.
I get better quadrant scores too vs.my setiron 1.47 1200 kernel. I don't know if it's due to this kernel, but for some reason I'm getting much better battery life since flashing it.
opcow said:
I get better quadrant scores too vs.my setiron 1.47 1200 kernel. I don't know if it's due to this kernel, but for some reason I'm getting much better battery life since flashing it.
Click to expand...
Click to collapse
Same here, battery life seems better..I've noticed it not draining so quickly, im at 85% when usually id be at 50-60%
Sent from my Captivate
I've found Darky's 7.01 works best on my phone, could it be true this makes it run faster? Do I need to have full charge or can i flash this at any battery level?
I didn't look at the actual quadrant score. But my fps is on average about 2-3 greater. Similar to running at 1300 on other kernels. Battery life is much improved over the kernel in eugenes ginger clone rom.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I just flashed it over SetiroN 1.5.6 and can see a speed difference already. 1200 O/C is perfect, I really like the kernel. Working great on Darkys 7.0.1
I too just installed over Darky's 7.0.1, bit more speed is noticable but i mainly did it for the possibility of better battery because right now thats all i am after.
i just installed but i want some more about voltage control
how can i modified that option?
thx a lot!
Is it just my phone that seems to run as smooth or smoother in real world use at the undervolted 1ghz setting? I haven't seen any difference in opening apps and when playing Mega Jump it stutters at 1.2ghz just as much if not more than 1.0ghz. I'm not complaining in the least as my e-peen has no relation to the speed of my phone. The undervolting is also an added bonus of running the 1ghz setting. Coupled with Juice Defender and a few battery concious settings my phone is lasting crazy long. I'm running Bonsai's stock Genocide kernel at 1ghz conservative. When I was on ACS I think 1.2ghz my have been a bit smoother.
Yes i believe its just the kernels that are out right now...
i think they recommend 1000-1200 IF you want to OC but im not sure
As Randy pointed out in one of the Bonsai threads, much more battery is saved by lower operating freqs than by undervolting... 1000-1200 will drain the battery faster than 200-1200, even with the undervolt at 1000.
Sent from my mind using telepathitalk
I swear no one ever takes the time to fully read my posts on this forum :facepalm
stir fry a lot said:
I swear no one ever takes the time to fully read my posts on this forum :facepalm
Click to expand...
Click to collapse
I have noticed just the opposite of your OP. Running at 1000 I find that some of my games are a tad choppy at times. Going up to 1200 and they are smooth.
To be completely honest, I run at 100-800MHz on the SFR rom, no hiccups or lag differences between 800MHz and 1000MHz that I can tell, so why not run it at 800MHz.
what are your OC scaling?
Ondemand or Conservative?
100-1ghz Conservative (as recommended in the Genocide thread)
100-1.2ghz On Demand when I was running ACS.
I have personally found that setcpu is my phones nemesis. I get waaaaay better battery life and crazy better performance running genocide 0.2a 100-1200 "stock" than running any combination of settings / parameters, other versons of same kernel, or even another kernel for that matter.
Seven Sisters EPIC using XDA App
Bonsai rom uses genocide kernel? I thought it was it's own custom kernel, I'm on bonsai 3.0.1 with the bonsai 3.0.0 kernel and gpu performance is much improved over stock, running @ 1.2Ghz and much improved battery life over stock eb13.
Its an optimized version of Genocide from my understanding
I have personally found that setcpu is my phones nemesis. I get waaaaay better battery life and crazy better performance running genocide 0.2a 100-1200 "stock" than running any combination of settings / parameters, other versons of same kernel, or even another kernel for that matter.
Click to expand...
Click to collapse
I set it to 1.2ghz and deleted SetCPU. My phone is flying now. Thanks for the advice.
stir fry a lot said:
Its an optimized version of Genocide from my understanding
Click to expand...
Click to collapse
Ok, I've never read that anywhere before and my first thought was.....you switched out the kernel for genocide and thus caused your own performance issues.
No bonsai is not the same as the genocide kernel at all. Its their own kernel that they made.
Sent From My Evo Killer!
Well in that case I'm running the Bonsai kernel.
I am running the Twilight Zone kernel, and have it set at 200-1000 with ondemand
My battery life has been AWESOME, and the I have noticed no lack of response in anything I have run
stir fry a lot said:
I set it to 1.2ghz and deleted SetCPU. My phone is flying now. Thanks for the advice.
Click to expand...
Click to collapse
Apologies in advance if I misinterpreted your statement (it's a bit ambiguous).
If you set it in SetCPU, then got rid of SetCPU, the change will not stick. Any settings done through SetCPU do not make permanent changes to startup scripts, but are instead applied by the SetCPU application. To make them persist, the "Set on boot" checkbox must be checked, and when this is the case, SetCPU simply does its thing quietly in the background as a service.
If, instead, you modified startup scripts to set CPU speed and governor, well, then, never mind
dwallersv said:
Apologies in advance if I misinterpreted your statement (it's a bit ambiguous).
If you set it in SetCPU, then got rid of SetCPU, the change will not stick. Any settings done through SetCPU do not make permanent changes to startup scripts, but are instead applied by the SetCPU application. To make them persist, the "Set on boot" checkbox must be checked, and when this is the case, SetCPU simply does its thing quietly in the background as a service.
If, instead, you modified startup scripts to set CPU speed and governor, well, then, never mind
Click to expand...
Click to collapse
No, I got you. I've heard of people changing scripts in lieu of SetCPU. I just had read somewhere by one of the devs that if you set it to the 1ghz setting and remove SetCPU that the undervolting would stick. I though it would be the same for clocking. Either way my phone seems t be running very smooth without it so I'm ok with that.
After reading through the Thread for the Pre Release of FuguMod Ultra in the development section of this forum I thought I would post some info up for people who are wondering why it doesn't work with their phone, and just some general info on overclocking.
- First off, not all phones will be able to run at 1366MHz. Every CPU made has a range of freuqencies it will work at, and it is different for every single one. So some may be able to handle 1366MHz and above, others may max out at 900MHz. If you are getting black screens, freezes, or random behaviour, then your CPU doesn't like the frequency you have it at, try a lower frequency.
- Always keep an eye on the temp of the CPU when testing overclocking, if the CPU gets too hot, and fail safes don't work, there is a chance you could fry your CPU.
- With the FuguMod Ultra kernel, you must also be aware that gpu bus frequencies have been changed, so if your phone is not happy with that it will black screen. (as bus speeds are like cpu speeds, every different device can handle different clock speeds)
- plls values have been changed, and these may cause problems on your phone.
So if you want to have a go at overclocking your phone, back it up, and then give it a go. Select a frequency, and test with something pretty cpu intensive (3d game, multiple quadrant passes) and see if there are any bugs/overheating during a 15min time period. If you notice any problems/too much heat, try a lower frequency, and try again. And if for some reason your phone doesn't like the kernel, you can reflash with your previous kernel or a new ROM as you have already backed up your data.
If you have any other questions about overclocking, feel free to post here and I will try my best to answer them.
--- Samsung G3, InDroid 4.3, FuguMod 2.4 B3 800MHz ---
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
dilzo said:
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
The battery temp is a good representation of how hot the processor is getting as it is right next to the battery (only a thin sheet of metal seperating it) If the battery rises in temperature by a few degrees, then you can summize that the cpu is probably getting a few degrees hotter than that. I really wouldn't recommend letting the battery get above 55degrees (celcius) as this means the CPU may be getting up close to 65degrees (celcius) which is a very bad thing.
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
marcellusbe said:
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
Click to expand...
Click to collapse
Yes, Very true!!
Must also say, Your kernels are pretty legendary! Waiting patiently for the offical release of your FuguMod Ultra
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Piyush Rawal said:
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Click to expand...
Click to collapse
How have you got your phone set up? i.e. what ROM are you using etc.
I am using stock jpq with app2sd, swap, zipalign, ramhack and stuff. Setcpu is installed with default min/max freakquency, No profiles in use and undervolt a bit.
Ok,
This may be an issue caused by XXJPQ, as it is a new release there may be some sort of conflict. Have you tried asking if anyone else has this issue in this thread? http://forum.xda-developers.com/showthread.php?t=1132697
I haven't played around with JPQ yet so don't know what the bugs are yet.
Also, are you running a stock kernel? Have you confirmed that the phone has been rooted properly as well?
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Piyush Rawal said:
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Click to expand...
Click to collapse
Ok cool, I'll report the bug to the developer so that he can have a look into it. Thanks for testing and proving to the kernel.
Little bit of info some might find helpful. After some recent testing, I have found that some people might experience a black screen freeze when phone is in standby for a while with 83MHz min setting and on demand governor. I am not sure of the exact reason for this, whether it is a bug, or that the processor just doesn't like going that low for extended periods of time. If you experience this type of error, just hard reset the phone then open setcpu after phone has loaded and change the "standby" profile minimum to at least the next step up on the slider. Personally I use 223 setting as it provides a smoother lock screen animation, and no significant difference in battery drain.
Sent from my super smooth GT-I5800 using XDA App
hi
i have a htc evo 4g running android 2.3.5 and kernel 2.6.35.10-g4b48446 [email protected] #1 and i have a few questions on setcpu. its a stock rom and it is rooted.
I shut off my profiles and disabled the perflock - it said success. So i ran the long bench test and only got 2078 ms, not 5000. so i dont know if its really working. I reengaged the profiles and i think it works with the screen off. the rest of the time i am not so sure. in fact it seems to still drain fairly rapidly unless i turn on some battery saver or something. I have the following settings on my profile all are set to ondemand except charging which is set to performance. the only other setting i can choose is user
in call 998 max and 245 min priority 91
screen off 384 max and 245 min priority 88
charging any 998 max and 245 min priority 85
battery <25% 460 max 245 min priority 81
bbattery <50% 883 max 245 min priority 65
Temp> 42 C 614 max 245 min priority 50
what am i doing wrong? I have it enabled and i have notifications off
i have system panel to try and monitor but its not recording and it also drains the battery like crazy so i think thats set wrong as well but i dont know why.
i also tried juice defender but it doesnt work right because it says the AOSP file isnt found in the system/app folder. I looked there and also in teh data/app folder and its not there. So i dont know what to do about that.
thanks
stock sense is just not all that efficient really. (well thats my opinion) profiles seem to look ok but also finding a different kernel with different governors (smartass v2 is rather efficient and changing around the frequencies as needed)
auto sync settings as well? turning some stuff of that you dont use or look at and so on can help too
and calibrating battery a bit can help aka a full discharge a full charge and full discharge will sure help (also what i have found personally)
kernels
thanks for the reply. You mentioned different kernels. I understand about rooting my phone but not so much about how to load a different kernel or different rom. Where do i go to learn about that?
jjdonohue said:
thanks for the reply. You mentioned different kernels. I understand about rooting my phone but not so much about how to load a different kernel or different rom. Where do i go to learn about that?
Click to expand...
Click to collapse
look around in the development section as there are some great kernels available right now...Ca1ne just released a new version of the underworld SBC v6 that i personally like with great battery life ...Mason kernels are also great with great battery...just make sure u read the threads completely to make sure u are using the right kernel for the rom u are using...ie there are kernels for ics...sense....and so on......also the kernels load through recovery...just load kernel to sd and wipe cashe and dalvik and flash zip...hope this helps...Carp
Hi another question about kernels. I am a bit of a newbie other than rooting my phone so i want to understand what advantages/disadvantages different kernels have. You mentioned smartassv2. i have seen others like
chopsuey kernal
freedom kernel
golden monkey kernel
savaged-zen kernel
tiamat kernel
all of these i think support sense roms.
as i understand it , you have to go into the recovery screen and load hte zip file off the sd card and reboot with the new kernel. What are the risks/rewards of doing so? I guess i am trying to understand which one would suit me best.
i have the current sprint lovers rom i guess since it is factory stock so should i also be considering changing the rom? Maybe i am getting ahead of myself here.
thank you again.
which rom are u wanting to run....this will help us steer u in the right direction
im sorry your entire post didnt load on my end i see ur running sprint stock....that is a fine rom but i have not ran it myself....
---------- Post added at 01:53 AM ---------- Previous post was at 01:36 AM ----------
i personally have switched to sbc kernels when they came out with a sense version...i am addicted to sense 3.5...just my personal likings...sbc is superior battery charging whichcarp will give u better full charge on your battery so when the light turns green and u unplug it it wont drop down to like 90% battery in just a few mins....i can squeeze another couple hours out of my battery with sbc and even more depending on light usage....but u will stil need to play around with different cpu speeds like 786..921 and so on to see what your individual evo can stand....what works for 1 may or will not work for another....lags and bootloops etc...
You don't need to change Roms, you can if you want, but changing kernels will unleash new features. Some features are:
Full hdmi mirroring
The ability to over/under clock CPU
2 way call recording
Improve battery charging
Enable swap space
Improved performance of phone
Some kernels allow under volting CPU to further save battery (this can cause some stability issues so start slow with undervolting)
You may want to take a look at Lionfish kernel also, just note first boot may take a while.
Also ditch the profiles in set CPU, I tried profiles and it never seemed to work right. A good governor will handle all your profile settings.
I like smartass, and intellidemand the most on my set up.
As an idea ok the battery life I am getting, I streamed Pandora over 3g for about 8 hours not much other phone use, screen off most of the time, and my phone was at like 20 %. I thought that was pretty good.
Sent from my Synergized Aggressive Lionfish Evo using the XDA app
thanks detcup4evr for helping out explaining that better...i blew out my back and between no sleep and pain meds the brain just dont want to fire...thanks for stepping in bro....carp
smartassV2 vs InteractiveX ... which one giver better performance AND battery life??? currently I am running LIONFISH 1.8 with interactive X
Using profiles in setcpu actually uses more battery life. Because it has to be running all the time and monitoring phone state to know when to change to a different profile.
interactiveX vs smartassv2 all depends on how you use the phone and really which kernel it is. I've noticed little things like on mason's I got better battery with smartassv2 but on other kernels I get better battery with interactiveX. As far as performance, you won't realize a difference.
ok so it sounds like i should try the sbc sense 3.5 kernel with the smartassv2 governor. Did i get that right? i will look around to see where i can download that.
Were you refering to this kernel?
Underworld Sense Kernel v0.6
yes this is the kernel i run with ODJDub HD Bliss!! Sense 3.5...if u choose to run this rom it will give u alot of different options of kernels and apps and other things from the installer....if i can help u more just feel glad to hit me up....carp
Ok so with lionfish 1.8 kernel and interactivex, I should not use a profile? What does CPU go to on screen off? also where does it mention profiles use battery? I'd like to read more into this..
Thanks
Sent from my PC36100 using Tapatalk 2
Sense rom with Underworld v 0.6
At Carp -
thank you for the advice. I was thinking maybe i would use my ROM still (its a sense i believe) and load the underworld v0.6 kernel with sbc and see how that goes. I havent done very much research on ROMs so i dont know that i want to get that deep into this just yet. It seems like underworld has alot of nice features. One thing that i am wonderig though is with the new kernel would have any further ability to unload some of the sprint bloatware or do i need a new rom to do that or is there another way to do it? Things like qik video , gmail, accuweather blockbuster etc all load themselves periodically. I kill them but then they come back like weeds. Even programs i do like , like pandora, wheres my droid etc come back also. But i dont want them to.
no u will be fine getting rid of apps and bloatware u dont wont...u wont need a special rom....i use a free app in the market called root uninstaller to get rid of useless bloatware,apps etc...then u can go in and manually uninstall what u don't want...be careful not to uninstall anything which the phone needs to boot and operate such as android system...you will see the things u are looking for when u load the app...hope this helps...carp
I actually did something unusual.
I have universal aggressive lionfish SBC 1.8, swagged out stock N, and smartassv2
I set the ideal, sleep, and wake freq for smartass v2 to 128, while setting the up rate to 245. I used set cpu to lower the min freq for my device to 128. I set max load to 100, and min load to 85, and down time to 0. I then set a profile for "ondemand" during screen off, of 128-384.
I actually have pretty awesome battery life (I'm an uber heavy user).
Sometimes it reads that I spend over 70% of my time at 128mhz.
I feel no lag. It clocks to 998mhz maybe 15% of the time, mainly when loading web pages.
flashed underworld v 0.6
Hi Carp,
well, i flashed the underworld v 0.6. So i see in set cpu that i can underclock to 128 and overclock to 1228. however, i slid the slider over to 1228 by accident and it froze the phone even though it says its still at 998 mhz. then it rebooted by itself. so i guess that wasnt a good idea. Anyway, theres a ton of governor choices now in the profiles section. i am not familiar with alot of them but i was wondering which of those would provide the most benefit. they are as follows -
ondemandx
interactive x
intellidemand
smartass
interactive
conservative
smartass 2v2
performance
along with ondemand and user space from before.
thanks
Good to hear....u will need to try different settings as each evo will be a little different...ie.. some can take alot of overclock and as u said when u went to high it locked up......my evo likes min 245 and i dont go very little over 998...mine does not like high overclock....i run between 768 and 998 or until i can see a lag or slow down in performance..depends on which rom i am running...i like ondemand x and smartass 2 on my evo but there is a good read in papa smurph's smurphed out v6.6 thread in development on governors and such...go to post #2....i wish there was a perfect setting i could give u but u will have to see what your evo can take...part of the fun of android.....carp
Governors
Thanks carp. I guess experimentation is the only way to know. i charged my phone last night ad i noticed that it does take alot longer to go from 100% charge to 90% but i also noticed that the phone temp was at like 110 deg F and a voltage around 4.263 or so. i have read some thread where they claim its bad for the Lithium ion batt to be over 4.2 V but as soon as i unplug it it drops to 4.1 something usually. I am using battery indicator app to measure it. i am using the underworld w/sbc kernal currently but the voltage being higher has me a bit concerned that i am damaging the battery kind of like pumping water into a jar with the the lid on tight til it bursts. Or in the batteries case - too hot i guess or until it plates.