yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RichMD:
Optimized memory timings tweak

Hi existz,

Could you explain why this tweak is optional? I see a pro (not that I understand beyond it is "better") but no con. Why would we NOT want to enable this all the time? I saw someone post in the Continuum thread that there was a memory issue with 2.0.4 and you would update. Does this have anything to do with the tweak or was it the read-ahead for the SD card?
[Captivate Android Development] existz:
Theres no reason for it being Optional, just set it as that because..its optional.. all my tweaks are set optional.. no other reason for it.. As for the memory issue, there really never was a for sure memory issue...just that having to high of a readahead value could cause higher memory usage (on any linux/android system), but it was never proved that 2.0.4 had a memory issue.. or never proved how much higher it would be..might not have even been noticeable..
[Captivate Android Development] aalh:
Flashed 2.0.5 today and disabled soft locker

I have not had a sleepdeath yet

AND

I have it OC to 1300 as well as the CWM Thresh tweak enabled!

You may have found it Existz
[Captivate Android Development] existz:
Fingers crossed! :)...been hunting this one down for awhile now...but i think (hope) its gone this time, either way, if its not..im getting closer
[Captivate Android Development] RichMD:
Thanks for the reply. I saw the battery tweaks that were optional in the past simply became part of the default config. Based on your reply though, I assume there is no reason to not enable the memory tweak. I will try CPU performance on and off to see if it makes a significant difference in battery (or performance).
[Captivate Android Development] antonyvijai:
What is the benefit of disabling soft locker? Is it something related to OC / UV?
[Captivate Android Development] joedoe:
but not at the same time!
[Captivate Android Development] meadhros:
Same thing with kc1 with 2.05. Switched back to jk4 and speeds better. Not sure but I am suffering more in areas with less signal and indoor which may tie this more to a the modem going 1900 than 850.

I've been swapping modems all week as my signal has been hell in a nutshell. Seeing the same thing all over threads. That combined with getting text messages from ATT about cell service towers they are adding in my area, I would attribute our signal issues to ATT trying to get all the stuff ready for LTE upgrades and what not later this year.
[Captivate Android Development] bamonkey:
had flashed 205 after the regular nightly and wowzers everyone is correct this thing is good...like REALLY good. i think my battery cycles are a bit off which is a first in a long time. i got to about 15% and then power just plumeted dramatically. just saw the 4-09-11 nightly and decided to take the dive in. Ok, stop giving our devices android crack! LOL! im using linpack and sdtools and they seem to confirm things feel just a bit faster. Man o man i need to shoot you some beer money
[Captivate Android Development] TRusselo:
google "android softlocker" woulda had your answer hours ago!
[Captivate Android Development] .:Crack:.:
Is there a possibility to use this for i9000? or could you make it work? :D

Thanks!
[Captivate Android Development] TRusselo:
kernels are device specific.. for the most part.

technically it might boot but your sceen orientation would be wrong. dont bother

but go to the i9000 forum. bookmark this http://xdaforums.com/forumdisplay.php?f=656

kernels are in the dev section.
[Captivate Android Development] VFO:
Well so far with the release version of 2.0.5 I have had 3 sleep death issues with no oC/UV. This is odd because I went a whole day without one happening when I used the nightly build from 04-08. Was there any difference between that nightly and the official release 2.0.5?

Edit: Just since I posted this I have had 2 more sleep deaths. I flashed the release version of 2.0.5 last night at about 1:00 AM and when I woke this morning the phone was off. Since then it has had a total of 4 SD issues. There seems to be something different between the 4-18 nightly and the official 2.0.5 release. In that difference I think the answer is.
[Captivate Android Development] H3llstorm:
Hey existz, is this something you'd find useful?

http://xdaforums.com/showthread.php?t=1025561
[Captivate Android Development] aalh:
Well I am having just the opposite

I have had SD and CD since Onix came out, 2.0.5 is the first Onix that doesnt give me sleep death

Suckerpunch didnt, but earlier Onix did
[Captivate Android Development] thresherhorn:
I'd have to agree with this statement so far.

Suckerpunch till about 57 were solid as stone. (Stopped at 57 since my phone was finally getting amazing battery life/stability/etc)

Soon as it converted to Onix (Think I hopped on the bandwagon about 2.0.2) I started hitting SD/CD issues. Numerous accounts of em through 2.0.4 but thus far in all of the day that I've been running 2.0.5 I've experienced 1 patch of "lag" (could have just been a network/app issue as it was trying to load a page with like 6 other things going) and 0 SD/CD.

Crossin fingers it continues! :cool:
[Captivate Android Development] VFO:
Are the nightly releases 1000hz or 100 hz? The reason I ask is maybe it is the 1000hz that is causing me issues. All the release versions I have used of Onix have been the 1000hz versions and have given me sleep death issues. However the nightly from 4-18 did not so if that was a 100hz then maybe thats my issue.
[Captivate Android Development] grkmaster:
I had Charge Death with 2.0.4 and random lock ups.(was at the Mets game, and you have no idea what i was going through trying to get my phone to not flake on me) Flashed 2.0.5 last night and have had no problem with CD at all like 2.0.4
[Captivate Android Development] topiratiko:
Yea 2.0.4 was a little off for sure. 2.0.5 is purrin like a kitty so far

Sent from Paragon Optimized
[Captivate Android Development] Seanbest:
2.0.5 running smooth as butter. 2.0.4 seemed to lag over time. We'll see how 2.0.5 holds up.
[Captivate Android Development] eureb:
I only ever had sleep death issues while my phone was stock, but it would only happen about once ever couple weeks or couple months, so I never worried about it I've been using Onix(2.0.1, 2.0.4 and 2.0.5) & FF(2.7 and 2.8) for about 2 weeks now, and I have yet to have a CD or SD, plus my phone is running better than ever.
[Captivate Android Development] Seanbest:
I had sleep death on stock until I used setcpu to keep the clock at 200 when screen is off, never had it sleep death or charge death on me again.
[Captivate Android Development] fezzy102:
Flashed precision then flashed onix last nite had sleep death.left for work around midnite wiped the volt stats,delvik catche,and catche partition and have had no problems used 10 hours just charged to 100% with no problems.running smooth thanks for the awesome kernel.
[Captivate Android Development] IDoMy0wnRacing:
I am having a problem with: waking up the phone, unlocking (rotary lock) and having the home button stick... it acts like it is being pushed repeatedly until I hold it down and wait for task manager to load, push the back button then all is fine. It doesn't happen all of the time, but it is something that happens.

I have tried turning on and off "BLN", and "Keep the Lights On".

Any advice is appreciated.

I am running Continuum v4 with Onix 2.0.5, 100hz at 1200Mhz slight UV and lag fix.

I have tried different UV settings, with and without lag fix.

This has happened with all of the Onix Kernels, I don't remember this happening with the SP-Voodoo kernels.

Just sharing an issue.
[Captivate Android Development] AReynante:
This happened to me, I had to return the phone. There isn't a fix for the repeated pushing, as far as i know
[Captivate Android Development] meadhros:
Dumb question mostly fo my stupid curiousity. You all out there with the repeated button issue....do you have screen protectors? If so are they the solution applicant ones?
[Captivate Android Development] harpo1:
Title says SIO, has this changed in 2.0.5 to NOOP?
[Captivate Android Development] existz:
No, its still SIO, make sure you dont have something overwriting it in /etc/init.d/ ....(S_volt_scheduler or 99scheduler...etc..)
[Captivate Android Development] topiratiko:
Confusion! Were supposed to use sio instead of noop?

Sent from Paragon Optimized
[Captivate Android Development] existz:
Yes, thats why its default...if it doesnt default, then theres something else overwritting it on boot... make sure nothing in /etc/init.d or /data/init.d/ is setting Noop or whatever
[Captivate Android Development] shane87:
Ok, so I just wanted to provide some feedback on onix 2.0.4, and I see 2.0.5 has been released. I will be downloading 2.0.5 to see if it has the same issue. Ok, so yesterday I flashed onix for a little while to test an app I am writting against a different kernel beside existz kb1 beta. I flashed onix and i9000 based modem tljl3. Upon reboot, I loaded the app I am working on and it fc'ed, but I think I have it fivured out now. However, in the interest of testing stability, I tried some different oc/uv settings in voltage control. I found that, on my cappy anyways, if I enabled the 1600mhz state, my phone would freeze instantly. The first time it happened, I pressed apply now with 1600mhz, 1400mhz, 1200mhz, 1000mhz, 800mhz, 600mhz, 400mhz, and 200mhz enabled, no uv. As soon as I pressed apply now, I pressed menu>exit then slide my homescreen to get to my stability test app. Half way through the homescreen shift, the phone froze. I waited ten minutes, still frozen, pulled battery, and rebooted. Tried again with same states enabled but uv'ed -25 on 1400, -50 on 1000, 800, 600, and -75 on 400 and 200, pressed apply for now, and froze before I could leave voltage control. Pulled battery, reboot, same settings except 1600mhz disabled, ran smooth as butter. Just wanted to share these results. Happy modding to all!!

After testing I did switch back to kb1 beta, just have had better luck with kb1 beta.

ROM: Cognition v4.3

Kernel: eXistZ kb1 beta #8, Voodoo Sound v7, Voodoo Color, Voodoo lagfix

Modem: I897 UCJJ4

HW Build Number: 1101
[Captivate Android Development] harpo1:
So how do I correct this? I see in S90scheduler where it sets noop. I had K13d on here prior to flashing 2.0.5.
[Captivate Android Development] existz:
Just delete S90scheduler..thats all it does is set the scheduler, removing it will let it default to the kernel default
[Captivate Android Development] harpo1:
I set it sio in the voltage control app and rebooted and it stuck. I'll remove the S90scheduler as well. Thanks.
[Captivate Android Development] seanzscreams:
i am losing alll settings on reboot now ,

what is the filesystem i need to convert to ext 2 or 3 to prevent this from happening?

i remember it being mentioned somewhere that ext 4 doesnt retain data as well i am currently on all ext4 i noticed dbdata was set to ext4nj but i changed it to all ext 4 including system, at this point i just need to know which is best for this kernal

thanks
[Captivate Android Development] diablo009:
What do u mean by settings - voltage settings? If its voltage settings, u would need to go to /systems/etc/init.d and

rename the file Voltage Control app creates

to S99_Volt.

And all my partitions are ext4, and have been ext4 for the last few kernels I have been using. I never faced this issue of data loss. I am not sure if u mentioned earlier or not, but is urs a clean install?
[Captivate Android Development] existz:
Use ext4

10char
[Captivate Android Development] seanzscreams:
like for instance any system settings

i start up maps then i change all my settings then i reboot and maps starts like ive never used it before tested several times. never had this problem with any other sp or onix kernal i wiped dalvik etc.

also my phone cany remember which home i want as the default if i open lets say voltage control then i click home it asks which i want as defualt , it only does it like every 10th time and always on a reboot.

i have asked this in other pages and got told it was using some of the tweaks and also the filesystem conversion

i never have this problem on voodoo

or on a non oc kernal

its usually just sp or onix

but i ****ing love it so much ill never change just really want to get it solved

i have wiped this phone tried different roms come back to the same roms and its usually always no setting retained
[Captivate Android Development] diablo009:
I tested it just now. Loaded maps, shut down phone, n powered it back on. Maps works as intended.

I would suggest u do this once:

1. Backup ur data to computer

2. Go to stock

3. Mount to computer n format ur internal SD

4. Copy ur rom, say firefly 2.8

5. Copy this kernel too

6. Copy the cwm recovery update.zip to SD root

7. Go to cwm recovery console

8. Install rom

9. Reboot the phone till its fully on

10. Reboot to cwm

11. Check if lagfix is enabled, if its not, apply it to both data partitions n system partition

12. Reboot

13. Go back to cwm

14. Apply this kernel n reboot

DO NOT RESTORE TIBU DATA UNTIL AFTER STEP 12.

This should work.
[Captivate Android Development] seanzscreams:
yeah i tried that im on darky so maybe its the repartioning thats doing it

but i have noticed on a fresh install no restore of backups i installl only launcher pro and it still id say 75 % of the time requires me to go to task manager and do a level 2 clear, bc it crashes but not fc ...weird just freezes no oc uv either just limit to 1000 no 600 or 900 , then once launcher is gone i hit home and it asks me which auncher i want as default and all is perfect

also maps i dont even need to reboot, if i change my map settings then pump advance task killer a few times and then try and go back into maps , settings are gone. it must be a memory thing

now i have the first four options enabled in tweaks could this be causing itt???

but honestly i have no problems at all just this weird little glitch if i run adw. i never get the freeze on boots ever.
[Captivate Android Development] existz:
How much disk space do you have on system, data and dbdata?
[Captivate Android Development] diablo009:
Pls stop using task killers. For reasons why not to use them, please read the link in my signature that says "android memory management".
[Captivate Android Development] AReynante:
Kinda late, but to whoever asked about the screen protector and button pushing:

It happens with and without my invisible shield (solution based). Also happened with the cheap ones from att store
[Captivate Android Development] Jammn:
Hi existz. Can you please briefly explain what the various tweaks in recovery do, or of it has been answered before direct me to the relevant post.

Keep up the good work, greatly appreciated.
[Captivate Android Development] xreflection:
It's like in the second post of the entire thread, not to mention also has been repeated many times during the life of the thread. Do a search. I doubt existz knows any better where the posts are than we do.
[Captivate Android Development] Jammn:
The second post only mentions two of the tweaks, and while no-one knows where the individual posts are, existz knows what they all do better than any of us. Most are self explanatory from the name, but specifically, the last two optional ones I have no idea what they do.
[Captivate Android Development] fractaline:
Which ones?

Refresh our memories....

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] :
Anybody else's phone turn on immediately after plugging it in?
[Captivate Android Development] diablo009:
Android Logger

I am not sure what this does, but disabling is messing up with protection apps like App Protector Pro. This is one reason devs are now adding this as optional so people like me who use these apps can turn it on.
[Captivate Android Development] diablo009:
Not mine. I just get then battery charging icon for a few seconds when I connect to power when turned off.
[Captivate Android Development] topiratiko:
Thank you kind sir!

Sent from Paragon Optimized
[Captivate Android Development] grkmaster:
I dont want to blame the kernel, but man when i leave my house and im out my battery starts dieing like crazy.

In about 4-5 hours i went from 96 percent to 50.. i barely used the phone... I need to keep it idle in my house overnight to see what the issue is
[Captivate Android Development] Twicebak3d:
It could be a rogue background app. I know telenav wrecked my battery while on phoenix ultimate.
[Captivate Android Development] grkmaster:
I have telenav installed but havent run the program in a while.. would still cause an issue?
[Captivate Android Development] Twicebak3d:
I never ran it and it was still the cause of my uber battery drain.
[Captivate Android Development] grkmaster:
Charging death has come back... I out the phone on charge for about 2 hrs while sleeping and woke up with it off.. Since the last time I charged to 100% I ended up UVing.. is there something connected there?
[Captivate Android Development] VFO:
Update on my sleep death issue. I switched over to the 100hz version yesturday after my previous post and have not had any issues at all. Just prior to that while on the 1000hz version I was having multiple sleep death issues. Could someone explain why this would matter? I guess the 100hz version will be the one for me and to tell you the truth I don't notice any difference between 100 and 1000. This kernel rocks!

Sent from my Continuum powered Turbo Cappy
[Captivate Android Development] sthodupunuri:
When I was charging my phone when it was of it went into some weird kernel messing up screen with many different colored bars.it didn't happen again.why did it happen? Is it a kernel problem?
[Captivate Android Development] fractaline:
So, the 100hz kernel uses the same kernel hz/user hz value.

The 1000hz kernel adapts the

User 1000hz to the kernel 100hz, using more battery.since hz are waves/second it stands to reason that we can't see a difference between 1000 and 100.... Maybe in games or other such intensive apps.. But even still.......

Onix 2.0.5 is 128/150 and super smooth. So to me, whatever is the most effective/efficient is the the go.

That reminds me, I need to make a donation to existz.......

This kernel does rock!

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] topiratiko:
So i downloaded setcpu and saw that default settings on charge was 100mhz min and 1600 mhz max....but off charge was 100 min and 1120 max which are my overclock settings. I adjusted charging max voltage to 1120 and so far so good no charge death....that MAY be the issue...also for those using soft locker set cpu is a must to keep cpu from ramping up while screen off..set it to 100 min 200 max with screen off...doing only 100 is unstable as fone freezes when recieving calls

Sent from Paragon Optimized
[Captivate Android Development] shoman94:
Ok... now I've been getting the same issue with 2.0.4 but nearly as often as 2.0.5. You guys are all getting the sleep/charge death but mine is a bit different. I get a lock up when I UNPLUG the charger. Sometimes it happens where I unplug when the screen is off and it won't wake up..... other times it happens when I wake the phone up first then unplug it... it will just lock up and I have to press power&vol up to reboot it.

This is getting pretty annoying. It only started happening on 2.0.4 and 5.

I'm going back to 2.0.4 for now as it felt faster also.
[Captivate Android Development] diablo009:
SetCPU is known to cause issues on Froyo. Use Voltage Control instead.
[Captivate Android Development] aalh:
CD and SD are back

I left the phone on the charger last night, it was off this morning.

I turned it on and went on with my morning, I just checked it, it is off:(

I had been charging it via usb, this was the first time I had it on the wall charger since flashing 2.0.5

so it would seem that using the wall charger woke up the sleep/charge death issue

I hope it was a fluke
[Captivate Android Development] :
It says clearly NOT to use SetCPU in the first post. Use voltage control to set cpu/voltage settings.
[Captivate Android Development] :
Make sure you're not undervolting too much on the lower end.
[Captivate Android Development] topiratiko:
Im using BOTH and everythings stable and battery consumption with soft locker is improved.

Edit

If you dont set cpu on boot, voltage control takes priority. Only thing i use set cpu for is to create profile to limit screen off mhz to 200. I have 100 mhz uved to 175 and 200 uved to 150 and it equals 4% per hour which is GREAT considering it doesnt enter sleep mode :)

Sent from Paragon Optimized
[Captivate Android Development] existz:
The reason you don't use SetCPU is because the oc/uv code is actually wrote for Voltage Control, the oc/uv code adds new sysfs files that Voltage Control reads (frequency_voltage_table, states_enabled_table...etc..etc)...and SetCPU is not able to read those..the oc/uv code used was originally wrote for the SGS only ... As far as I know SetCPU just reads cpuinfo_min_freq and cpuinfo_max_freq for the cpu and only sets values for those files ...which causes problems because its not reading which states are enabled...etc..etc..so do not use SetCPU

So for example, the code is setup to use states...so by default the kernel sets the states 100-1000 enabled by default, if you do not want to use a frequency, you disable that state, Voltage Control reads these states and shows accoridingly...so if you open up voltage control it will show max clock is at 1ghz..with SetCPU, it does not read these tables, just cpuinfo_min/max_freq...which by default with the oc/uv code, it will show the max freq in cpuinfo_max_freq is 1.6ghz...With Voltage Control, no matter what you set the max clock to, it will always show cpuinfo_max_freq as 1.6ghz, as thats the highest clock available..it will then use the new sysfs files to adjust the max clock and states enabled to whatever you set it to...with SetCPU, it just goes straight to cpuinfo_max_freq and adjust it..and usually causes problems (lockups, reboots..etc..)
[Captivate Android Development] topiratiko:
Can it fry my phone? Because i DO need one it falls in the bad imei range just too lazy to go thru the proccess. lol. Thanks for the info existz.

Sent from Paragon Optimized
[Captivate Android Development] existz:
It wont fry it, using SetCPU can just cause lockups..reboots..etc..cause the way the code is wrote to set the frequencies, max clock, is different than how SetCPU sets it.. but it wont fry anything or damage anything...just instability..
[Captivate Android Development] Nickel Dime Bay:
I'd definitely rock with a 1200 kernel
[Captivate Android Development] existz:
Just to get it out before everyone starts screaming for a 1200/1280 version... At first what I wanted was basically something close to Speedmod but with UV, so I settled for the closes thing to stock, 1120mhz... I plan on doing either a 1200 or 1280 version soon, but theres some other ideas I have that I want to perfect first, then I will release a 1200/1280 varient soon
[Captivate Android Development] LimaI896:
Just flashed this, may be the perfect kernel for me. Will report back any problems and how my uv settings go :)
[Captivate Android Development] sublimaze:
sweeeet. i'll throw this on my cappy this weekend
[Captivate Android Development] Mac11700:
Looking forward to trying a 1280 version with all the goodies...

Mac
[Captivate Android Development] ccdoggy:
EXACTLY my thoughts. speedmod is great but a little UV would be great.

Do you plan on updating this as hardcore develops speedmod? using his latest and changing for release? aka are you going to keep trying to stay uptodate with hardcore's kernel?
[Captivate Android Development] phlunkie:
I love the suckefpunch bootscreen followed ny the cia boot animation . To perfect.

Ps...1200 has my vote. after some testing of course.
[Captivate Android Development] psufan5:
Ive had it on most of the day and hasnt gotten laggy at all. Just rock solid and great battery.
[Captivate Android Development] LimaI896:
My playstation works perfectly so far, I have a.great feeling about this kernel.