yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Im not sure yet until I see/try the patch.. but im assuming its just GBs kernel thats not compatible with fugu, ive noticed (and verified by DamainGTO) that if having CONFIG_OABI_COMPAT disabled will cause incompatiablity with fugu, it breaks boot animation and causes lockups.. which im not sure why having that set to disabled effects it since its depreciated, but it does..(also im not sure if anything else breaks it, but thats what fixed it for me and DamainGTO).. but im not sure yet till I try it
[Captivate Android Development] harpo1:
How do you apply the patch? SGS Tools?
[Captivate Android Development] rajendra82:
I love to see version numbers change. Happy as a clam that my build 1007 seems to love modem ZNKP1. Only one disconnect after 100% charging, and that took me leaving it in the charger overnight to do that.
[Captivate Android Development] rajendra82:
It's in the kernel source. GB said he will release that by Tuesday.
[Captivate Android Development] zerkai:
Just upgraded to 2.0.3, nice boot logo. Might be just me but I think its more aligned to the left side than the middle.

Maybe you can also include that battery saver setting in the op.

I897, Tapatalk-

I have spoken.
[Captivate Android Development] lospulpo:
Not trying to be rude. I really do love this kernel and all of the features, but I'm a big fan of that stock i897 boot image. Can I pull just the boot image files from the 2.0.1 zip and drop them into the new 2.0.3 CWM zip? If that will work does anybody know which files?

Thanks!
[Captivate Android Development] zerkai:
Hopefully his color settings are there too? ;-)

I897, Tapatalk-

I have spoken.
[Captivate Android Development] existz:
Its actually compiled in the kernel, you would have to re-compile the kernel to change it
[Captivate Android Development] zerkai:
I have a question about one of the recommended tweaks: io scheduler and remount noatime. Since default scheduler is sio, do we enable it? Is it the same?

I897, Tapatalk-

I have spoken.
[Captivate Android Development] 13_:
Thanks for the update. I think my phone has become a victim of the dreaded random shutdown bug. Lol... I also think Onix is so smooth that it is making confirmation difficult. I'm tempted to take it in but want it to survive just a bit longer. :)

Sent from a Captivate on Bluedipity 6.3, Onix 2.0.3, JQ1 with Xda App
[Captivate Android Development] existz:
Its actually 2 different things, SIO as default sets Simple IO scheduler as default, the IO Sched + noatime applies tweaks to the scheduler, but since SIO is, well simple, theres not many tunable tweaks that can be applied to it, unlike CFQ which the tweak was intended for by hardcore, but I actually disabled most of the tweaks since they don't do anything to SIO, plus im still working on rearranging, adding/removing tweaks that are Onix specific...but I do recommend enabling it to set noatime on partitions, which should significantly reduce the number of writes, as now the access time of a file or directory will not be updated.
[Captivate Android Development] pizz0wn3d:
Just want to report that I've been having some sort of charge death with this kernel. I should mention that I also have NOT been oc/uv for the last three days when the problem started.

The issue I'm having is that the phone will occasionally freeze when I unplug it from the charger, requiring a reset with vol up + power. note that this usually occurs when I walk up and pull the cord out of the phone while it's idling with the screen off.

it may have to do with the cpu freak tweak, as that was enabled while these lockups occurred. Gonna keep it off for a few days and see if it still happens.

Herp derp Captivate XDA app.
[Captivate Android Development] grkmaster:
So by using this and I see that my phone is 19% in 1200mhz / 38% in 200mhz / and 24% in 100mhz and the other frequencies are 5% and less.. Do i undervolt more on the frequencies that dont get used much or the ones that get used more?
[Captivate Android Development] existz:
Most likely its from the script, I haven't had a charge death since I first released SuckerPunch ..and I ended up getting one lastnite with the tweak ...i assumed that was what it was from but you confirmed it..so it seems I need to tune the tweak some..ill work on it some and post a new script later
[Captivate Android Development] rajendra82:
You undervolt each frequecy as low as it can go to while still keeping the phone stable. The ones that get used more are more important in terms of the savings in battery consumption, but which frquencies get used changes depending on what you are doing at any given time. The overall stability is the first thing to shoot for. If the phone is unstable, it is usually because you are overzealous in undervolting for the frquency that is being used during that activity and/or have too much change in voltage between the states adjeacent to it.
[Captivate Android Development] existz:
You want to uv the ones being used the most..but I would give it a day or two before judging which ones are used the most..it will fluctuate based on usage
[Captivate Android Development] grkmaster:
Well right now as im using TuneIn radio app and charging my phone 200mhz dropped to 36% and 1200 went up to 20%. Ill just monitor it and go with what programs i usually run everyday that make it use the higher freq. since ive had my phone on for only 7 hours

Phone is very stable. I have absolutely no problem for the past few days. Phone doesn't restart or lock up, so I can toy with more undervolting to see where i can push it?
[Captivate Android Development] abee_13:
Just place the script in etc/init.d folder and reboot. It seriously adds hours to yuhr battery life!
[Captivate Android Development] AReynante:
Is the script the same as the option thats in the onix recovery?
[Captivate Android Development] existz:
No, that's the cpu threshold tweak.. the script tweaks the amount of time the cpu checks the threshold to determine to scale up or down ..also it tweaks the amount the cpu scales when it does scale up/down (% of max clock) ...it should keep the cpu from scaling as much ,as well as keep it at lower frequencies more often ..which the script is battery saver settings, ill work on performance settings once I settle on battery settings ...

So for example, if using the default threshold settings and the script it will...

Checks every 1000000ms (1sec) and if the up threshold is on average of 90% load it will scale up at 10% of max clock ..and if the down threshold is on average of 55% ,it will scale down 10% of max clock ..(performance threshold is 70% up and 30% down)

The tweak in recovery just changes the percentage of load the cpu has to be at before scaling, default is battery saving settings (55/90) and the tweak is performance (30/70)
[Captivate Android Development] JGGW:
I am new to the thread but have read up on the entire 300+ pages so it's been quite the read...my question for you Existz is the script you speak of is NOT?? the one that has to be enabled in recovery called CPU performance threshold? Are you referring to a script that is built into the Kernel? Thanks for clarifying... I am loving this kernel coming from the speedmod ones. I am looking forward to tinkering with oc/uv :)
[Captivate Android Development] abee_13:
So whats new in the recent voodoo sounds?
[Captivate Android Development] existz:
correct, the script is NOT the same thing thats in recovery (performance threshold tweak).. the script is a file I posted awhile back for a few people to test, the values used may to be unstable, thats why I need people to test..seems that it might be to aggressive..causing charge death for some..but thats why I needed it tested so I could adjust accordingly .. as I explained above..

The

tweak in recovery

changes the cpu threshold, the threshold is the

% of load

the cpu must be at before it scales up or down...

the

script

changes the

amount of time

the cpu checks the threshold, and changes the

amount the cpu scales

up/down (its a % of max clock, so with it set to 10%, if you max clock is 1000mhz, it will scale 100mhz up or down)..
[Captivate Android Development] existz:
Everything from the top down until it says v6

https://github.com/project-voodoo/linux_gt-i9000/commits/froyo-voodoo-sound
[Captivate Android Development] JGGW:
thanks, just making sure I was understanding correctly. I will report any charge or sleep deaths.
[Captivate Android Development] harpo1:
This script isn't the cpu freak tweak that was mentioned earlier in the thread is it?
[Captivate Android Development] existz:
The script is the S_cpufreq_tweak.sh script... it changes sampling_rate (amount of time cpu checks threshold) and the freq_step (the amount the cpu scales based on % of max clock... 10% of 1000mhz = 100mhz)

The tweak in recovery tweaks the cpu threshold, which is the % of load the cpu must be at before scaling.. the sampling_rate (amount of time) checks the threshold (% of load the cpu must be at) and then scales based on freq_step (the % of max clock)
[Captivate Android Development] pizz0wn3d:
Yeah I was using the recovery tweak. I know what the cpu tweak is, sets it to 70%-30%. I was just wondering if it might be scaling up when I unplug it because of that, maybe going into the 600hz step and causing it to freeze. But then again I'm no dev so I'm not going to pretend to know what I'm talking about lol.

Any idea what could be causing the charge death? I haven't been using any uv/oc settings other than the occasional oc to 1200/1300, though I haven't saved them as boor settings. Could the oc cause it?

Thanks for the reply and information.

Herp derp Captivate XDA app.
[Captivate Android Development] existz:
If your only using the cpu performance threshold tweak in recovery, then yea its possible, with that enabled it will jump to higher frequencies quicker and wont scale down as quick..so when you unplug the charger the screen will come on, and the cpu should scale while doing this ..so if your oc isn't stable enough, it could freeze.. try disabling the tweak in recovery and set oc/uv to stock .. if it doesnt do it then, then try enabling the tweak (no oc/uv) ..if it doesn't do it then, then set your oc/uv settings...then if it does it, try lowering some of your oc/uv

With the tweak enabled, it will go to higher frequencies quicker, so for example if the tweak is enabled, it could very well jump to 600 step when unplugging...as with the recovery tweak disabled, it might not even move from 100/200 ,or whatever yours idels at..or maybe only 400mhz...you get the idea

Which your oc/uv settings might not be stable (or never was stable to begin with) when enabling/disabling the tweak...if its disabled, the cpu will spend more time at lower frequencies, and it wont scale up as quick, so your higher settings might not need to be as stable as they wouls need to be if the tweak was enabled..cause with it enabled, it will scale higher quicker and it wont scale down as fast, spending more time at higher frequencies

But for those confused, there was a script, S_cpu_thresh.sh with the first version of Onix, however that tweak is now in recovery (cpu performance threshold)..the script we have been talking about is S_cpufreq_tweak.sh, its totally different than the threshold tweak
[Captivate Android Development] AReynante:
Sorry existz, when I asked about the script, I meant the mem timings one.
[Captivate Android Development] existz:
Its my fault, ive posted alot of scripts..it was bound to get confusing sooner or later..but no, the script we were talking about is different than the tweaks in recovery..

S_mem_timings script = Optimize Memory Timings in recovery, no need for script..enable in recovery (optimizes memory timings)

S_cpu_thresh = CPU Performance Threshold in recovery, no need for script..enable in recovery (optimizes cpu threshold values - 30/70 (default 55/90) )

S_cpufreq_tweaks = NEW script, not in recovery, use the script in /etc/init.d/ (tweaks sampling_rate and freq_step)
[Captivate Android Development] AReynante:
Lol, it's alright, I hadn't been following you for like two weeks or so, sucker punch wasn't liking my new phone :p is the script that we have to copy paste in the op?
[Captivate Android Development] fractaline:
My question got lost a few pages back.... can we use the cpu threshold tweak and the cpufreq tweak at the same time?

Although at this point after a couple sleep freezes I think I'll disable the tweak in recovery.

I also want to confirm what the correct path for the script is ...

Thanks

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] existz:
No, the S_cpufreq_tweaks.sh script is posted a few pages back, I kept it out of the OP because i didnt want everyone trying it out first, incase it was unstable settings..so I kinda left it buried so only those that knew about it would try it...but you can find it here..

http://berryfx.com/RobBeane/Kernel/Files/S_cpufreq_tweak.sh

If it causes any instability (charge/sleep deaths) let me know...as mentioned these are battery saver settings, so it may or may not effect performance...ill work on performance settings after I settle on saver settings
[Captivate Android Development] Johnny Paranoid:
I'm sorry existz, but you said that you

are

going to try and find a way to incorporate the S_cpufreq_tweaks into the kernel (or possibly the recovery) if you can make it stable? Because it's not stable right now? If it is stable, you you post it again because I'd like to use it if it's not going to break my phone. You just save the script as a notepad file and name it S_cpufreq_tweaks and put it in /etc/init.d/ with Root Explorer?
[Captivate Android Development] existz:
Yea you can use both at the same time, but the tweak in recovery sets performance settings, the script is battery saver settings... but if you wanted to mix them you can, no biggie... as I mentioned earlier, the way it works is... the script tweaks the sampling_rate (amount of time) before the cpu checks the threshold (% of load)(which is the tweak in recovery, default=55/90, tweak enabled=30/70) and also the script tweaks freq_step (the amount the cpu will scale based on % of max clock.. 10% of 1000mhz=100mhz)..

but if you want the best battery results, use the script with the cpu threshold tweak in recovery

disabled

, using default values for the threshold (55/90)... if you want the best performance, enable the cpu threshold tweak in recovery, but do not use the script.. ill get a script for performance settings later on
[Captivate Android Development] existz:
Once i find the best settings possible ill make the battery saver settings default then I will have an option in recovery to enable performance settings... as of right now, the script works..but it may or may not effect performance or cause issues, thats why i need feedback..These are battery saver settings, so it may or may not effect performance, its soley for better battery life...but if you dont like it, just delete the file and reboot.. but to use the script, all you have to do is download the file, dont rename it or anything, just download it and put it in /etc/init.d/ and then reboot.. http://berryfx.com/RobBeane/Kernel/Files/S_cpufreq_tweak.sh
[Captivate Android Development] Johnny Paranoid:
Cool, my phone is charging ATM but once it's done I'll try it out. Thanks!
[Captivate Android Development] Soccer_Dad:
Thanks for the explanation. Looking at the shell script, I would like to ask about this part:

Max CPU could be one of three things: the standard 1 Ghz native processor speed, the maximum state enabled in voltage control 3, or the limit on the processor speed in voltage control (any version). I have mine overclocked to 1400 now (but rarely get use it) with both the state and the limit, but I'm not sure if 10% of the max is 140 or 100 Mhz (I assume it's the 140).

And since the states available are generally spaced at 200 Mhz (except for the bottom 100-200 transition), anything below a certain threshold value will simply step from one to the next anyway. And does it round up, or round down for a (for example) 280 Mhz transition - i.e. does it go from 400 to 600 if I were to set the freq_step to 20% of 1400, or does it go from 400 to 800 in that situation?

And if I set the transition to 30% or so, how would that "effectively" be different than killing the 400/800/1200 states in voltage control 3, and jumping from 100-200-600-1000-1400 without intermediate steps (5 well-spaced states - ignoring the 100-200 transition for the purposes of this question)?

I'm not trying to be annoying - I'm just interested in the guts of what I'm doing to my phone.
[Captivate Android Development] AReynante:
Thanks for the script link Existz, I'll let you know how things go after a little while. I was running 1.4 oc, with random Uv levels, and never had any sleep/charge deaths, so we'll see how the script does :)
[Captivate Android Development] fractaline:
Thanks, for that, I'm happy to experiment, just don't want to do any thing foolish..

It'll all quite clear now....I'll post any findings...

And thanks for the tip on that app by storm. A must for refining oc/uv.

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] AReynante:
I agree on that app, I like knowing what my phones likes to camp on, but I don't fully understand the way to uv with it :p
[Captivate Android Development] pizz0wn3d:
Ok so I've apparently already had the threshold tweak turned off, but I can't remember when I disabled it so I'll run the phone as is for a couple of days and see how things go.

For reference, here's what I currently have enabled:

-Both of the recommended tweaks in recovery

-the optional mem tweak underneath the threshold tweak.

-fugutweaks

-no oc/uv

Edit: I'm also using the sio scheduler that the kernel defaults to.

I also want to mention that I'm using the autokiller memory optimizer app that changes the system memory settings for when to kill apps, using the aggressive setting. could this conflict with the memory tweak in recovery? Will it override it, or do they even affect the same settings?

Thanks again for all of the help existz :D

Herp derp Captivate XDA app.
[Captivate Android Development] xThaNaturalx:
I'm sorry, I might sound like an idiot here, but what is the difference between the 100 Hz zip and the 1000 Hz. Is that just an OC difference? And if I'm not planning on tweaking, should I be using 100? Thanks.
[Captivate Android Development] Johnny Paranoid:
Read the OP. Second post.
[Captivate Android Development] c0ldburn3r:
I'm on that list of phones that don't like to go past 1.2ghz. The main point behind this kernel is to UV so always try the 1.12ghz kernel a try first.

Note: I usually don't UV I go with stock settings to make sure it's a stable build. May devil into the UV once the charge death is resolved; waiting for my phone to charge to see if some code change fixed the issue.
[Captivate Android Development] c0ldburn3r:
Don't see why you can't since it's a 2.2.1 based rom.
[Captivate Android Development] Kizzmiazz:
Works great with 4.1 except you loose your home button and some, including myself, are having charging death.

Sent from my SuperDuper!Captivate | PHOENIX RISING 3.5 KizzEdition | Firebird 2 v0.5 | VA Green v10 Theme | Member of Team Phoenix
[Captivate Android Development] c0ldburn3r:
Home button feedback or the home button entirely?
[Captivate Android Development] evrionis:
thanks..

What do u mean by "are having charging death." ?
[Captivate Android Development] ryude:
Charge death means your phone shuts off while you leave it charging for a long time, like when you sleep.
[Captivate Android Development] evrionis:
Hey ryude thanks.

Thats not a good thing. Is it a kernel bug or that kernel is not compatible?
[Captivate Android Development] silverslotcar:
I got charger both times I have charged to 100. I look over and see the big green battery symbol at 100% after being shut down.
[Captivate Android Development] ryude:
Can we get a list of the people with charge death report which version of the kernel is doing it?

1280/1120 MHz or 100/500 HZ
[Captivate Android Development] existz:
According to Glitterballs thread, the problem is within the undervolting code, since mine does not have the charge death im unable to trial and error it to find a fix, so im waiting on GB to msg back so I can fix it. Im messing around alittle bit hoping I get lucky, but more than likley going to have to wait till another dev can help
[Captivate Android Development] c0ldburn3r:
It's all the builds and I'm testing a build right now to see if it has the issue. eXistZ has a few more tricks up his sleeve if this one doesn't work.
[Captivate Android Development] ryude:
Ah, thank you. Well I can't wait this kernel is so badass my battery life just went through the roof!
[Captivate Android Development] LimaI896:
I wish I saw the battery improvements everyone is seeing. I cant ever get an accurate reading since I reboot my phone at times.

On my second battery and its the Samsung, hoping to break 10 hours lol I normally get 8 max with moderate use. (moderate in my opinion :rolleyes:)
[Captivate Android Development] ryude:
Hey, battery life is mostly affected by the screen being on. Other than that, I'd say make sure you aren't running any market apps known to drain battery.
[Captivate Android Development] LimaI896:
I try to do a task level 2 clear often, and just have screen set to autobrightness. I have spare batteries so my eye sight > batterylife. I'm just curious if all these other people are getting this great battery life and running auto brightness as well.
[Captivate Android Development] c0ldburn3r:
Run at full brightness with tons of widgets, gps, wifi, sync and bluetooth on. Use was medium to heavy and I saw 12 hrs. I've since slashed all of that and I can get 2 days easy.
[Captivate Android Development] sjavvaji:
No charge death for me...I'm using the 500hz 1280 version with a lot of undervolting...try seeing your underclocks lower before blaming the kernel
[Captivate Android Development] LimaI896:
I swear my battery must just be fried. I've only had the phone since October. I would only get 2 days if I don't use my phone lmao.
[Captivate Android Development] ryude:
I usually get 2-3 days out of my phone, but I do use literally 3-4 things on the phone. I don't mess with apps and widgets too much.
[Captivate Android Development] joeshmoe08:
Those values are for kernel hz and have nothing to do with oc. Basically th 1000hz will be more smooth but will result in less battery life and possible instability, while the 100hz will have better battery. I would recommend 100hz since I think it is plenty smooth and has very good battery.
[Captivate Android Development] antonyvijai:
Thank you. Looks like the berryfx.com site is down or something. I am trying to download 2.0.3 100hz but unable to do that. if you have that .zip file handy can you post it through a reply to this message.thanks a lot
[Captivate Android Development] AReynante:
I have it on my phone, let me transfer it. I'll edit this with the .zip
[Captivate Android Development] pizz0wn3d:
Yeah the link seems to be dead. I actually didn't even realize there was an update posted.

looking forward to flashing this, as I'm hoping the low memory killer fix might keep the kdwapd0 process from spiking so often when I'm switching between programs, often bouncing between 30% and 75% load for a little while.

Either I'm paranoid, or it's causing some annoying power drain.

Herp derp Captivate XDA app.
[Captivate Android Development] pizz0wn3d:
Thank you sir :D

Herp derp Captivate XDA app.
[Captivate Android Development] AReynante:
No problem :)
[Captivate Android Development] antonyvijai:
Thank you
[Captivate Android Development] pizz0wn3d:
I really despise not being able to thank via the xda app.

Herp derp Captivate XDA app.
[Captivate Android Development] AReynante:
Hah, I hate that too. Not fishing for a thanks, but you could always just open it in a browser, I think there's that option somewhere. Idk :p But its all good :)