I'm coming from a thunderbolt and that was my first android and rooting experience. I just wanted to make sure using cwm is the same.
If I want to flash just the kernel that's cool right?
I mainly want to get the smartass governor because that worked well on my tbolt.
Is flashing radios done in bootloader like the thunderbolt? I believe the tbolt was unique because it was the first so it had two radios. I assume the note isn't?
Sorry, that turned into more than one question.......just want to be happily flashing again.
yes, you can flash only a kernel, or only the recovery
I've had this note now for 3 weeks....am stock rooted with different da_g kernel v2 .....overclocked with set cpu. few build prop tweaks I edited..and this phone is blazing fast and not one bug....gonna keep this way to ics gets here and maybe get a rom then,as of now they seem unstable,and not worth it...stick with your kernel only idea.....
thanks for the responses.
That's exactly what I was planning to do wish.
I would like to debloat though.
I was going to flash the 0.2 kernel. Is that what you meant?
This one http://forum.xda-developers.com/showthread.php?t=1504920
I have already taken the processor down to 192 and might oc but just a little. I'd start of with keeping it at 1.5 and see if its fast enough. I really liked smartassv2 on my Tbolt.
Thanks again.
schrochem said:
thanks for the responses.
That's exactly what I was planning to do wish.
I would like to debloat though.
I was going to flash the 0.2 kernel. Is that what you meant?
This one http://forum.xda-developers.com/showthread.php?t=1504920
I have already taken the processor down to 192 and might oc but just a little. I'd start of with keeping it at 1.5 and see if its fast enough. I really liked smartassv2 on my Tbolt.
Thanks again.
Click to expand...
Click to collapse
yes that's the one 'Version 0.2 CWM Zip' And yes debloat everything you find necessary...it does help i should have been more specific sorry.
i have mine set at 384 min and 1.89 max on demand...in set cpu
From here are some build prop tweaks: http://forum.xda-developers.com/showthread.php?t=1560588
i didn't use those net speeds because are phones have that by default you can tell from looking in folder "int.rc"
And no boot animation is just wierd and still takes as long booting ..lol
in root explorer i only used parts of that script, im using
#Battery
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
#Response
debug.performance.tuning=1
video.accelerate.hw=1
#extras
persist.sys.use_dithering=0
ro.ril.hsxpa=3
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
persist.adb.notify=0
ro.kernel.android.checkjni=0
ro.home_app_adj=1
windowsmgr.max_events_per_sec=150
Those are huge improvements to your system it will cause the system to fall asleep when the screen is off almost instantly which brings the phone into deep sleep..saving battery hard core
*tip-make sure system power saving in system in unchecked...
* and turn Auto-sync off in (Accounts and sync)..saves some battery
Hopes this helps buddy let me know...also as you already know let the battery get used to these settings with a couple days...my phone has the best battery life with performance when needed..
Thanks!
I never knew about the build.prop. Is that in all android phones?
I pretty much did the same as you except didn't oc yet.
I'm using system tuner pro to watch, modify and monitor. Also his battery widget pro.
I noticed CPU 0 gets used like I would expect. However, CPU1 is mostly 'offline'
Is this something that can be tweaked or baked into a kernel?
get rid of system pro..half the time those setting don't stick......yes build prop is in /system/buildprop folder....long press open with edit text and you can manually add those props at the end of the list...like as in the thread..easier just to copy and paste them...and save...reboot..and go back make sure they stuck...get set cpu for overclocking works flawlessly and cpy spy shows the phone on each setting the cpu uses and for how long..and you can see when the phone enters deep sleep and how long....showing that those two scripts work....
schrochem said:
Thanks!
I never knew about the build.prop. Is that in all android phones?
I pretty much did the same as you except didn't oc yet.
I'm using system tuner pro to watch, modify and monitor. Also his battery widget pro.
I noticed CPU 0 gets used like I would expect. However, CPU1 is mostly 'offline'
Is this something that can be tweaked or baked into a kernel?
Click to expand...
Click to collapse
trust me cpu0 and 1 works....normally when doing higher process like games interent stuff...if where to be on all the time it would use more battery...this way the system can utilize the cores more efficiently
Related
[KERNEL][CM7][Froyo] Dalingrin's OC kernel w/fixed IO perf (quadrant) & 1.2Ghz test
Disclaimer: As always, flash at your own risk.
Background
So, recently there has been alot of debate over why quadrant (and to some extent, system performance) was lower with the OC kernel, as compared to the stock CM7 kernel. (http://forum.xda-developers.com/showthread.php?t=1002504) As part of my examining the problem, i went looking for a solution. Starting from the first OC CM7 kernel, i would run quadrant and see how the performance fared. I finally found the issue appeared in the 3-08a kernel; using that, i rolled back changes until i found the commit remove to fix the issue. Specifically, it seems to be somewhere in the 2.6.29.6 update: https://github.com/dalingrin/nook_kernel/commits/gingerbread-exp
In short, using his source, i have compiled a kernel with fixed I/O performance, and all his other tweaks (interactive gov, etc).
So, I want to make this clear; this is still dalingrin's kernel; in no way do i wish to take credit for his work. But, while he is out, work must go on, right?
Information
Who is this kernel for?
eMMC Froyo and CM7 users
Will this work on SD cards?
It may if you manually replace you uImage, but i cannot guarantee it (since i cannot test it)
Is everything working in this release?
everything like bluetooth and dsp should still be just fine (you may have to do a few hard shutdowns/reboots to kick on BT, like normal).
Kernel Links -3/25/10
OC kernels (up to 1100Mhz, Interactive gov, BT and DSP):
Regular
http://www.mediafire.com/?k00ruvyulf01y64
Extra network features (PPP, etc)
http://www.mediafire.com/?i9h76wn483tk16v
OC kernel (up to 1190Mhz, Interactive gov, BT and DSP):
http://www.mediafire.com/?v6d2jpzaynvchde
For those having problems setting this speed in the CM7 performance settings, give setCPU a try, but don't use profiles. Using set CPU, i am able to get my system stable at 1190, where the CM7 manager instantly locks up.
Feedback
After flashing, please make note of OVERALL system response. The dip in quadrant scores prompted the fix, but i feel that the system is overall better; I would like some more input if others are seeing this as well.
Any and all feedback is welcome, and I will do what i can for support...
Great job man, you and dalingrin both!
Ran 3 quadrant tests on newest nightly (#30)
1. 1856
2. 1700 even
3. Whopping 2030!
Can you be more specific about which network features are in the second choice ?
Thanks !!
ADude said:
Can you be more specific about which network features are in the second choice ?
Thanks !!
Click to expand...
Click to collapse
Um....truth is, i am really not too familiar with it, but looking a the diff between the two configs:
# Core Netfilter Configuration
# IP: Netfilter Configuration
# CONFIG_TUN
# CONFIG_PPP
I am trying out the net kernel again, to see if it is better than the last time i tried it..
Edit: Its looking better than the last time i tried it. Launcher pro hangs for a but on startup, but so far so good after that.
Just started using CM7 last night (w/bottom keys mod, so the nightly is from a few revisions back), but just installed this kernel (the regular version, w/out the Net adds, which I don't need), wiped cache & Dalvik, rebooted, set OC to 1100 and "performance" in CyangenMod Settings and now getting 1918 Quad score...vs. 1372 on the stock kernel with no OC.
I can definitely live with that score...great work to you and dalingrin!!
Thanks for taking care of this while I am gone. Much appreciated.
The update to *.6 is not necessary anyway.
When I get back I will revert the *.6 update and compile some of the netfilter/iptables and tun as modules as this seems to be more compatible than compiling them directly into the kernel.
Madcat, kudos to you. This is perceptibly faster.
great work!
so is this a 2.6.29.5 kernel then?
WOW, scrolling through XDA forum is much smoother than it used to be.
Tried on SDcard, installed by copying uImage to Boot. Reboots to EMMC when trying to load desktop. Back to CM7 stock. I guess I'll wait. Thanks though!
Homer
Can I have the config file for the first? I'm going to play with the kernel a bit.
EDIT: I'm just going to keep my big mouth shut for a while. I hoped it was just a bug with quadrant, but I flashed your kernel just now. There is a huge difference in interactivity. I was playing with the app drawer yesterday and couldn't get it to be smooth with "labels fade in" turned on and a 1000ms or so time on the animation for the app drawer. Now it's perfect every time.
GOOD JOB!
I love Open Source.
Will try this in some minutes. (Nook charging)
Ok, tested it. My scores below.
** QUADRANT SCORES **
Before update, 1100mhz: ~700
After update, 800mhz: ~1500
Now, 1100mhz: 1920
**********************
Awesome!
Just flashed it on mine and seems silky smooth to me. Not real sure there is a big difference, but it is not worse at least. Seems better to me.. Good job Madcat!!
Waiting anxiously for Dalingrin to return to his lab and see what else he can whip up for us..
nice!
i'm getting the same numbers as others (~1800) now. haven't really tested for overall smoothness yet.
will this kernel ever get a nookie version?
cowballz69 said:
will this kernel ever get a nookie version?
Click to expand...
Click to collapse
I have to admit - i said CM7 only, since that is all i have to test it on. If you do want to try it, you don't really risk anything; if it doesn't work, simply reboot to recovery and flash your last working kernel again.
As it is, i haven't really given a good look at what might be different between versions, so i can't give much advice on why it would/wouldn't work on Froyo.
Homer_S_xda said:
Tried on SDcard, installed by copying uImage to Boot. Reboots to EMMC when trying to load desktop. Back to CM7 stock. I guess I'll wait. Thanks though!
Homer
Click to expand...
Click to collapse
Got the same issue with the Net feature kernel. However the other one works fine. Got 1918 Quadrant on SD Card with OC 1100 GHz + interactive gov.
So I guess CM7 performance on SD is not too bad compared to eMMC
@Divine_Madcat : Could you look into the problem of the Net features kernel with SD Card booting? It run into eMMC after the bootanimation.
Thanks much for your work, an action is much better than thousand words !!
I tried both of these from SD card. The non-net features version boots but posted some terrible #s for me (<700 Quadrant and ~6-7 Linpack); the net features version doesn't boot. Is there something special I need to do with the first kernel to see the benefits? I checked and was clocked to 1.1GHz in CM settings.
victle said:
@Divine_Madcat : Could you look into the problem of the Net features kernel with SD Card booting? It run into eMMC after the bootanimation.
Thanks much for your work, an action is much better than thousand words !!
Click to expand...
Click to collapse
Ill be happy to take a look, but can't promise anything right away.
SCWells72 said:
I tried both of these from SD card. The non-net features version boots but posted some terrible #s for me (<700 Quadrant and ~6-7 Linpack); the net features version doesn't boot. Is there something special I need to do with the first kernel to see the benefits? I checked and was clocked to 1.1GHz in CM settings.
Click to expand...
Click to collapse
hmmmm.. that doesn't sound right at all. May i ask which nightly you are using? Right now, i am on nightly 27, and haven't seen anything like that (in my case, it either works, or just boot loops, if i set the clock too high).
Hi,
I recently installed viperROM v2.1.1 Redline with Tiamat v1.1 Sense on my HTC EVO3D. So far I love it! It runs super smooth and I love many of the included features. I have set maximum overclock through vipercontrol to 1.56GHz. I have just a few questions:
1.) I have occasionally had my alarm not go off. One time I caught it come on the screen, but no sound even. Sometimes the screen didn't wake up at all. This hasn't happened in about a week, so hopefully it fixed itself. I've done a few cache and dalvik cache wipes. Has anyone else experienced this issue, or may know what caused it?
2.) I have occasionally had a black screen on some incoming calls. This also has not happened in about a week so hopefully it fixed itself.
3.) How do I know how far I can overclock on this ROM and still maintain stability? This is my first experience with this on Android phones. I am very familiar with overclocking computers though and I know there are programs to test the stability of your overclock. There seems to be no such thing with phones.
4.) I know everyone says Quadrant scores don't mean squat, but why are they so low on this ROM? It certainly feels faster.
5.) What does everyone think of this ROM compared to other EVO 3D Sense ROMs? Are there any others I should look at? I'm only really interested in Sense based ROMs, I know they are heavy, but I really love the GUI and the phone seems to handle it quite nicely.
Thank you everyone for your time, and to all the developers thank you for all your hard work!!
I also forgot to ask, how is TWRP 2.0? Is it worth flashing? I'm still using the old clockworkmod recovery because that's what I've been used to.
Get TWRP 2.0. Its nice.
Do you have any screen off profiles? If so set it to 192-486mhz or 384-486mhz so the screen can wake with no problems. Also, flash an Anthrax kernel and see if you get black screen errors while waking up the phone. I dont know if the tiamat kernel is built into the Rom but it may be outdated if you picked it from the Dev Section.
The quadrant score may have to deal with the mods and tweaks in the Rom. They dont always reflect the truth.
You may be able to overclock to 1782mhz. Most of our phones can do this. Try a program like setcpu and see if you can raise it higher but "uncheck" the boot option. If you clock high and the phone automatically freezes, it means the clock speed is too high so try again with a lower speed until good.
My Blog: knowledgexswag.tumblr.com
Twitter: @knowledge561
knowledge561 said:
Get TWRP 2.0. Its nice.
Do you have any screen off profiles? If so set it to 192-486mhz or 384-486mhz so the screen can wake with no problems. Also, flash an Anthrax kernel and see if you get black screen errors while waking up the phone. I dont know if the tiamat kernel is built into the Rom but it may be outdated if you picked it from the Dev Section.
The quadrant score may have to deal with the mods and tweaks in the Rom. They dont always reflect the truth.
You may be able to overclock to 1782mhz. Most of our phones can do this. Try a program like setcpu and see if you can raise it higher but "uncheck" the boot option. If you clock high and the phone automatically freezes, it means the clock speed is too high so try again with a lower speed until good.
My Blog: knowledgexswag.tumblr.com
Twitter: @knowledge561
Click to expand...
Click to collapse
I'll give TWRP 2.0 a try then.
I'm using vipercontrol to set the min and max freq. Right now it has it set at 192MHz for min freq. I actually tried the Anthrax kernel before and had constant screen wake issues even setting the min freq up to 486MHz. I then decided to use Tiamat kernel, which so far has been much more stable for me. I only had the screen wake issue a couple times on Tiamat. Anthrax would do it every 5 minutes no matter what I tried.
I might try 1782MHz tonight. Will having it overclocked too much cause the battery to drain significantly faster? Or since most the time the phone is sleeping and not running at full speed it won't matter much?
Thanks for all your help!
Decided to try 1782MHz now, seems to be working great!
Graphics on my N64oid games seem to be smoother now.
Overclocking will drain it a bit quicker. Ive decided not to set any custom clock speeds or profiles at all. I kept a stock kernel and did nothing to it.
My Blog: knowledgexswag.tumblr.com
Twitter: @knowledge561
knowledge561 said:
Get TWRP 2.0. Its nice.
Do you have any screen off profiles? If so set it to 192-486mhz or 384-486mhz so the screen can wake with no problems. Also, flash an Anthrax kernel and see if you get black screen errors while waking up the phone. I dont know if the tiamat kernel is built into the Rom but it may be outdated if you picked it from the Dev Section.
The quadrant score may have to deal with the mods and tweaks in the Rom. They dont always reflect the truth.
You may be able to overclock to 1782mhz. Most of our phones can do this. Try a program like setcpu and see if you can raise it higher but "uncheck" the boot option. If you clock high and the phone automatically freezes, it means the clock speed is too high so try again with a lower speed until good.
My Blog: knowledgexswag.tumblr.com
Twitter: @knowledge561
Click to expand...
Click to collapse
First of all, not picking at you, just the first post I read and don’t have a lot of time here
The black screen errors are an issue within the kernel. Last time I used tiamat this was still a common bug in the kernel. You can fix it by downloading and installing and setting up a call recording app by the dev “voix” or something like that… don’t use the one on the market because it will do nothing for you. You need to download the one specific to 3D. it is found on the dev’s website.
Quadrant scores should be taken with a grain of salt. Depends on the ROM. I will state however that quadrant’s database read and write tests are accurate with real performance in that function of your ROM. I have personally tested this theory. Also, your database read/write tests contribute to a lot of the scoring in your overall performance summary with the free version. Just keep that in mind.
Don’t use set CPU, it is a good program, but designed for single core applications. Use system tuner pro, CPU master pro, or No Frills cpu. All of those are WAY more in depth and offer other adjustable variables that are critical for performance like setting the I/O scheduler.
Also, you need to manually adjust cpu1’s operating parameters, because when that CPU turns on and off constantly, it slows down your phone, causes lag, all this bull****. I cant figure out why it was programmed from the factory the way it was. It makes no sense whatsoever to have the two cores running two separate scaling governors. Set it to demand in root explorer by adding this line to init.d or init.post_boot.sh…
chmod 666 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo “ondemand” > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
also, in init.d or init.post_boot.sh, adjust your ondemand parameters to match your settings in CPU master, system tuner pro, etc…
you will see a line like this (for “cpu0” and “cpu1”)…
echo “60000” > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
change that value to 10000.
You will also see one similar for the up threshold… the end of it will read “…ondemand/up_threshold” with a value at the beginning probably of 95 or 90…
Change that value to 70
Basically, you should set both cores to ondemand, and tune that governor for performance by adjusting it’s operating parameters. Very responsive, good balance of performance and battery with a little more weight on the performance side of the scale.
---------- Post added at 03:34 PM ---------- Previous post was at 03:29 PM ----------
EDIT*** also, the two lines i gave you to add, put them in before any lines with "system chown" in them.
honestly man, if you want i can just email you a copy of my init.post_boot.sh, and init.d files, and you can just delete yours and add mine. lol.
i have them saved on my sd card so every time i flash a rom i remove the dev's tuning parameters and add my own, lol
the kernel is reason your phone is having wake issues another reason viper suggests using a minimum 384 on sleep helps prevent the wake issues.
Sent from my HTC Evo 3D using xda premium
Bradfordv said:
the kernel is reason your phone is having wake issues another reason viper suggests using a minimum 384 on sleep helps prevent the wake issues.
Sent from my HTC Evo 3D using xda premium
Click to expand...
Click to collapse
Is there something wrong with Tiamat kernel? I thought it was supposed to be one of the better kernel's for our phone?
Okay, I looked at what ziggy and cron247 did over on XDA and tried to make it better.
This kernel is unsecured, meaning adb connects with root.
It OverClock's up to 1.836MHz.
It has the SmartAss V2 governor.
It uses my ramdisk, not the one you have. I cannot forsee this being an issue. If it becomes one, let me know.
Updates:
Version 1.1.3 changes the version of lagfree, the old one was having issues. Also removes forcing the second CPU to be online which was causing choppiness.
Version 1.1.2 adds increased read ahead, writeback tweaks, decreased dirty ratio settings, simple I/O scheduler, and the lagfree governor.
Version 1.0.5 adds mpdecision fix by Mr X, thank you whoever you are, if you removed mpdecision, put it back. Also added voltage control for you UV lovers.
The only control program I have tested to work is AnTuTu CPU Master (Free), I have had issues with SetCPU and a few others. This one does speed, governor, and voltage all very well.
Get it here: AnTuTu CPU Master (Free)
The following problems seem to be fixed at this point: governor and speed settings not sticking, smartass staying at top speed, random reboots or bootloops overnight.
READ THE INSTRUCTIONS, THIS IS A SINGLE FILE
To install this kernel:
Copy the file to the root of your SDcard.
Reboot into recovery (CWR or AmonRa).
Flash the file from the SDcard.
At the end of the flash the phone will reboot to fastboot.
Once fastboot loads, tap PWR to get to HBOOT.
HBOOT will find the update and ask you to install.
Tap Vol Up to begin the install.
When it finishes it will say tap PWR to reboot. Do it.
After the phone boots remove the PH98IMG.zip file from your SDcard.
Use AnTuTu CPU Master (Free) to set min/max/gov/voltage.
Enjoy!
Thanks to ziggy and con247 for getting us started and having stuff out there for me to get ideas from.
Download:
Link: dsb9938 Kernel 1.1.3
MD5: a2558e70f9af572f43e258c9aedb4b40
Source on GitHub.
My favorite Rezound kernel so far. Haven't had one crash, even at max OC. Thanks so much guys at BAMF!
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
dccoh said:
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
Click to expand...
Click to collapse
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Argent36 said:
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Click to expand...
Click to collapse
It's kernel related; I'm running rezrom and had the same exact issue with my alarm running this kernel.
Do you think ziggys is more stable?.. or do I just need to find the right overclock/underclock settings?
I seem to recall seeing them have that problem on ziggy's - but I never had that problem on earlier versions of dsb's - so maybe it's just something that is fixable for the next release
*wanders off to test it again*
This is no doubt me doing things wrong that led to this, but I downloaded the kernel through the phone browser, then flashed it from the download directory on the internal SD. When I flashed Incredikernel from there it copied the PH98 to the sdcard, but no dice on this kernel until I copied it to the sdcard then flashed it.
I probably should have copied it to the sd card myself first anyway, but I figured I would let you know!
Well this morning - my alarm clock went off - I was able to snooze it - and then a few minutes later the phone went in to boot loops - had been running stable all weekend - once I pulled the battery the phone booted back up just fine.
we'll see if it repeats this behavior tomorrow morning or not...
Call recording support in the kernel?
timp123 said:
Call recording support in the kernel?
Click to expand...
Click to collapse
Nope, only Ziggy's kernel currently supports this.
I only set one alarm at a time usually, but I have one set to go off every morning at 7:30 & it has worked perfectly everyday for a few weeks now.
~John
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
sandman_nyc_316 said:
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
Click to expand...
Click to collapse
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
hgoldner said:
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
Click to expand...
Click to collapse
Thanks! How's your battery life been with those settings?
sandman_nyc_316 said:
Thanks! How's your battery life been with those settings?
Click to expand...
Click to collapse
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
hgoldner said:
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
Click to expand...
Click to collapse
Appreciate it. Gonna see what happens. Will update with my results. Thanks again!
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
zetsumeikuro said:
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
Click to expand...
Click to collapse
Good question. I haven't had a single bootloop since flashing this kernel after coming from Ziggy's. Been running this 192min/183max and UV'd -75 across the board and running great.
Hopefully I don't jinx myself.
Guys with bootloops/lockups...are you running any profiles?
Make sure you do a dalvik cache wipe....
Ziggy's would always lock up on me (multiple times per day) so I gave up on it. The only problem I have with this on (and this was a problem with Ziggy's too) is the min jumping to max.
My frequencies bounce on this kernel. It spends about equal time between the highest setting, and lowest setting. It works great other than that. My question is this bad for my CPU? I get great battery life, and performance, just scared the bouncing could be bad for the processor. Any help would be great.....
Sent from my ADR6425LVW using Tapatalk
Sorry i had to post this here, i couldn't reply on viperboys thread. Ive been able to keep 1600 mhz running after reboot by opening cpu5.sh with script manager and selecting execute.Hope i could help. Sorry if i couldnt.
Thanks but this is known though. U can use script manager or gscript to do this. I use to have it like that but changed it back. I'd rather overclock on demand. I can use my Prime in balanced mode with no overclock n still be fast as a mofo in everything. Amazing how powerful device already is stock. But evertime I see someone mention overclock, it usually makes me go apply mines..lol. I love it but not the shortened battery life. Plus I have a method to take regular overclocking a step further than vipercontrol or ATP tweaks. I can make it so that all 4 cores run @ 1.6Ghz at the saw time, all the time. Regular overclocking doesn't do this. But battery drains even faster. Sometimes we take stock speedsfor granted on prime. Amazing how powerful it is stock and the great battery life it gets. Usuallyif I overclock, ill make sure I'm near a power source.
Dang, now u made me wanna overclock...SMH....
What are you using to overclock?
Hello. I have been running CyanogenMod 10.1-10.2 since I got my device back in July, everything has been working great. Bugfixes have been lovely and all that good stuff; however one thing continues to annoy me. I cannot underclock my device properly. Let's say I go into the normal CyanogenMod Performance settings. Then I put my CPU to something like 1024MHz, then I see how the results went over with PerfMon from Chainfire, it will underclock only on Core 0, the rest of the cores still run up to the standard limit, 1890MHz. The only way I can somewhat successfully underclock is by setting my CPU to 594MHz or lower, at which point it will disable all cores except Core 0.
This has been annoying me for a while, I am running the standard CyanogenMod kernel, and recently I tried the Elite Kernel. The only thing the Elite Kernel did was remove the ability to disable the other 3 cores when below 594MHz. (And add the ability to go up to 2.2GHz, but who wants to overclock the Galaxy S4 yet?)
It may be worth mentioning if I try to tweak individual core settings with Tasker, on Core 0 it will let me set a CPU frequency, then if I go in and try to set something on Core 1, it won't have any of the default values for anything, and I enter them manually, then it will give me some errors about not finding the governor I said and stuff like that.
Anyone who knows any way to fix this (Custom kernels, different ROMs (Only for curiosity, I would stick to CyanogenMod anyway), etc) would be greatly appreciated.
Anyone who questions my motives for underclocking, question away. I don't like how my battery life is next to junk when I'm not even touching my phone all day, and the GS4 hardly needs the CPU it has, so I plan to use Tasker to set up a bunch of power saving mechanisms.
I suppose I do have one other question. Will underclocking even benefit me if I can't modify the voltage settings? Are they modified automatically when you're running at lower frequencies? (You would hope so, considering it's kinda a mobile device with a power source that isn't infinite). But if it won't help me without lowering my voltage (and if it isn't modified automatically) is there any good way to do that with a Tasker based setup, so it can be switched instantly whenever I do something? For example, launching a music player. All 4 cores shoot up to 1890MHz (I know they eventually settle down to lower frequencies, but for example's sake), I would rather have it so when I launched the app, Tasker would come in and set my CPU to ~800MHz with only a single core. Everything might slightly lag, but it would work and I would potentially get better battery life while listening to music.
Also, I never tested this on TouchWiz, as I didn't stay on it for more than 30 minutes after I got my device.
I am running the latest CyanogenMod nightly in case it matters (20131002, and it'll be 20131003 tomorrow unless it breaks something)
Thanks in advance to anyone who can possibly help with this. I'm sorry if the post is unorganized, but I hope it's understandable.
[bump]
Forgive me for my ignorance since I'm on ME7 and unable to flash CM10.x yet, but couldn't you just try different governors instead? On my old phone I was using lulzactive and it gave me great battery life, and you could tweak all the values any way you want for more performance or battery life.
I also remember when I experimented with undervolting and much to my dismay it turns out it made my battery life WORSE because of all the error correcting it was doing.
I get at least a days worth of moderate/heavy use on mine and with how fast it charges I don't really care about battery life but I'm curious how much actual gain you'll get for your efforts