yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
As of right now I can't, the whole oc/uv code is wrote for 13 steps (100-1600).. so to just add a step I would have to redo the whole oc/uv code....BUT... I can replace a current frequency with it, for example, I can remove the 1600 step and add 1344.. etc..etc..as long as I keep it 13 steps. Im messing around with the voltages for 15/1600 to see if I can get it any closer to stable.. for the next version I lowered it from 1500mv to 1375mv... seemed 1500mv was way to much juice, causing instability. .. ill see how it goes with that config and if people are still unable to get it stable ill mess around with adding 1344 and maybe something else (1450 maybe) in replace for 15/1600 steps ..
[Captivate Android Development] brd912:
i couldnt find that modem in the modems thread. care to tell me where you found it? or wait,would it be in the vibrants thread? sorry,still somewhat newbish here lol
[Captivate Android Development] topiratiko:
Sd fix DOES work. Open your gallery and you can totally tell.

Sent from Paragon Optimized
[Captivate Android Development] topiratiko:
Anyone with wifi reassociation issues after waking phone use blade wifi fix from market. Nice app.

Sent from Paragon Optimized
[Captivate Android Development] harpo1:
Does it allow the wifi to turn off when asleep?
[Captivate Android Development] fractaline:
I've been trying to use alternate frequencies in australia and have heard many different takes on this but I think that the radio chip can be either 850/1900/2100 OR 900/1700/2100 umts....

Do post anything you find out in the new modem thread, (best place for this discussion) I'll do the same. I'm looking for 900 but if I can get that than you should be able to get 1700

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] TRusselo:
can we get a rundown/description of all the onix CWM features? i understand most but not all, and can only imagine some other members....

advanced options (voltage settings -what/when fix permissions-whatis)

onix options (tweak options/ set defualt permissions)

mounts - i get it but many users dont know how to use.

ect...

i know its not all your stuff but a single place to find the info for your kernel would be nice.

screenies too for reference. it would have helped some of my 'tech support' chats...
[Captivate Android Development] johan8:
Most are from Speedmod.

If you know speedmod, you should know most of it.

Voltage settings wipe, used to delete voltage setting script in /etc/init.d

If you were using other kernel or previous SP you will need to delete old voltage and UV setting.

Of course you can do it manually by remount rw to /system then delete that script file.

Default/Fix permissions, used to reset files permission....
[Captivate Android Development] shoman94:
Working good. Faster and my battery drain@ idle is 1% every 1.6 hrs. Wifi on and gmail push on. Again this is perfect drain I think with the performance your bringing with it.
[Captivate Android Development] H3llstorm:
Using QuickPic instead of the "3D" Gallery is even faster! :cool:
[Captivate Android Development] TRusselo:
gee thanks for READING, not all the information was for me, and i acknowledged the fact that that most (not all) features are not native to this (from standard speedmod).

there is no single place to find information on all features (unless you count the search page on xda). i know, i've started the wiki. i was also hoping to get some more accurate professional descriptions to add to the wiki.

http://xdaforums.com/wiki/index.php?title=ClockworkMod_Recovery
[Captivate Android Development] aalh:
ok thanks

I meant 2.0.4 not 5 btw
[Captivate Android Development] aalh:
If I keep mobile data turned off altogether, it doesnt matter whether my phone is on umts or hspa because I am not using data

is that correct?
[Captivate Android Development] H3llstorm:
What does this mean/do? :confused:
[Captivate Android Development] shoman94:
Thats is correct.

I'm pretty sure the voice side doesn't matter.
[Captivate Android Development] Liv33viL:
Any or all system, cache, or other files that may have had their permissions manipulated, by either a modification or corruption.

By utilizing this feature, it will restore and enable the default permissions for each file and/or folder that has been altered from its native permission set.

HtH

Peace-
[Captivate Android Development] rajendra82:
Close, but not quite.

The Vibrant radio chip can do 1700/1900/2100

The Captivate Radio chip can do 850/1900/2100

The i9000 Samsung Galaxy S chip can do 900/1900/2100

It doesn't matter if you flash a modem that supports other frequencies, the phone will not physically connect on anything other than what the radio chip inside can do.
[Captivate Android Development] H3llstorm:
Default Permissions and Fix Permissions do the same thing?
[Captivate Android Development] Ikonomi:
I recently switched to this kernel from SpeedMod on a trial basis to hopefully correct some of the issues I was having with K13D and so far everything is great. Specifically, enabling the CPU threshold tweak cured my stock music player randomly pausing (both while otherwise idle and while using other applications). Good stuff.

I'm currently running what I assume to be a fairly standard 1200 MHz/1200 mV OC/UV.

Perception 10.2 | Onix 2.0.4 | I9000UGKC1
[Captivate Android Development] topiratiko:
Use blade fix in conjuction with wifi timeout app :)

Sent from Paragon Optimized
[Captivate Android Development] jon.groves:
So when I first flashed 2.0.4 everything was great, but as the day went on it got very laggy. Now it is very annoying. I hit the home button and can count a full 1-2 seconds before I feel the haptic feedback. I flashed the 1000Hz version and there is no change. What do you think?

Sent from Captivate with Serendipity 6.3 and Onix 2.0.4 and kc1
[Captivate Android Development] existz:
Try clearing cache/dalvik cache in recovery.. first boot will take awhile to rebuild
[Captivate Android Development] Liv33viL:
One in the Same

Technically.... yes.

If the permissions for a file(s) / folder(s) has been modified from its native permission state... the "FIX" permissions will restore the modified file(s) / folder(s) to the way they were before they became modified. ;)

Native:

IE: rw-rw-r-r-r

Modified:

IE: r-r-r-r-r

Fix:

IE: rw-rw-r-r-r

Capiche' ?

Peace-
[Captivate Android Development] sixstringsg:
What is this timeout app? I can't find it.

Sent from my CM7 powered captivate
[Captivate Android Development] WirelessMike:
Perhaps any wifi timeout app...

I use wifi buddy beta (free in market).
[Captivate Android Development] topiratiko:
Search for wifi fixer/wifi fix. It cimes up as blade wifi fix

Sent from Paragon Optimized
[Captivate Android Development] xtremesv:
I flashed onix yesterday. Today at work my cappy had its first death-charge. My phone is no oc/uv. I' ll test it a little bit longer.
[Captivate Android Development] meadhros:
Correct me if I'm wrong as most of what I learn is trial and error. I was guessing that when media scanning is complete my gallery will load quicker. Performance from this is not my objective. Any subsequent gallery loads for me take about 3-5 seconds. Prior loads were running 15-20 seconds. I carry a lot of pictures as well as two many extra images from that seem to accumulate from extracting framework-res files. Is the read ahead acting as a buffer where this data is being loaded?
[Captivate Android Development] H3llstorm:
I abandoned the laggy "3D Gallery" for Quickpic a while ago, which doesn't need any questionable mods or "fixes" to work properly.
[Captivate Android Development] Seanbest:
No charge deaths for me here yet. Have run it until dead then charged to full and done incremental charges as well.
[Captivate Android Development] IDoMy0wnRacing:
Hey, Good call, QuickPic rocks... Thanks for the tip.
[Captivate Android Development] existz:
Quite a bit of security fixes for 2.0.5, a few mm tweaks, lowered voltages some for 15/1600 to try to improve stability...1500mV might have been to much ..I might switch the 15/1600 steps out for 1344/1450 steps soon though..plus a few other tweaks/clean-ups... should have it tomorrow/friday hopefully..was trying for today but had **** to do last night and didn't get to test as much as I wanted to for the charge death..which ill do that tonite, so look for 2.0.5 tomorrow or friday

Also still messing with O2/O3 options .. O3 is differently quicker, but O2 seems to give better battery life, ill try a few more things before deciding on which one ill use for 2.0.5
[Captivate Android Development] Delicate Donut:
I'm sure no one would mind a little battery drain but you never know >_>. I prefer performance and stability over my battery lasting a week. It is a smart phone after all and it's bound to go dead fairly fast when in use. Keep up the good work man
[Captivate Android Development] ChikiBujia:
Totally agree!!

Onix has been great for me! And I rather have stability and support while carrying a charger in my purse :D
[Captivate Android Development] AReynante:
I'd like performance as well, I have an extended battery, plus never leave for more than 8 hours anyway, so as smooth and as fast as it'll go is perfect.
[Captivate Android Development] bballer182:
+1 here too! I too prefer performance and smoothness over 1-3% per hour.

On topic of the charge death issue could this have anything to do with the build of the phone it self. mine is a 1012 and never had one CD.
[Captivate Android Development] halfsoul:
Did you have to get a bulged back cover? Or did you find a larger capacity & same size?
[Captivate Android Development] LNJ:
I picked up a 2nd Captivate last night for the wifey and the first thing I did was flash Continuum v4 and Onix 2.0.4 hoping that this phone could pass my 1.4Ghz barrier.....if it did, wifey was getting mine and I was keeping the new one :D

But alas same wall. So I set it to UV @ 1.2Ghz and passed it off to her!
[Captivate Android Development] existz:
Im not sure about build numbers, but there was a release of known imei's that have issues with sleep/charge death.. if im not mistaking it could start to happen out of the blue.. im not sure what the range of imei's are, it was floating around here somewhere ..but samsung did release a statement about it ...with those there's nothing I can do, but it seems its hit or miss for some users, the last time it happened (early SuckerPunch) I found out if setting swappiness to below 60 would cause it..but I've made sure to make swappiness=60 (60 is default..it was set to 0 via a tweak in cwm from speedmod) ever since..but I did switch oc/uv code for 1.6ghz compared to SP59 and below, so there could be something simple like that causing it, but it will take me time to exclude every possible option...
[Captivate Android Development] AReynante:
I got the bulged back cover, I don't mind though, it feels better in the hand
[Captivate Android Development] LNJ:
IMEIs manufactured before November 6, 2010: 352982040855394 or lower - 5393, 5392, etc.
[Captivate Android Development] jon.groves:
From Where did you get the extended battery and cover?

Sent from Captivate with Serendipity 6.3 and Onix 2.0.4 and kc1
[Captivate Android Development] AReynante:
I don't know if I can post the link, but a seller on ebay called "sankeymakers". (Also known as transcend shop in the item pictures)

And the battery's name is "3500mAh EXTENDED BATTERY+COVER 4 SAMSUNG CAPTIVATE I897".

If you do decide to purchase it, make sure to order from the auctions with the picture of the battery with a step down on the back side.
[Captivate Android Development] olo567:
Unfortunately I'm getting sleep deaths again with latest Onix, despite having no OC or UV turned on. It seemed to slow down to a crawl and become very laggy right before not responding at all.
[Captivate Android Development] aalh:
sounds more like a lock up than a sleepdeath

if it was a sleep death then it would be asleep when it died and you would not know if it was laggy or not
[Captivate Android Development] FredOak3:
Mine is well before that IMEI range and I've run Onix and SuckerPunch and All kinds of other kernels and never had a problem with CD, so I'm thinking it is a specific range of IMEI numbers and not just all earlier models.

The only thing I know of mine being a 1007 model is that no mater what the GPS sucks.
[Captivate Android Development] olo567:
Well it certainly locked up, but it did become unresponsive again after being put to sleep. Didn't require a battery pull to reboot though, responded to vol+ - power reboot. It definitely was laggy in the 10 minutes leading up to it being "off" though. Call it what you will, something with Onix makes my phone unstable without any OC/UV. Troubling.

That IMEI range is meaningless to us now. The only build that was known to have the hardware issues with sleep death and random shutdowns was 1006. That IMEI range was simply those shipped with JF6. There was a software/firmware issue causing sleep deaths in JF6.
[Captivate Android Development] tehsam:
just flashed 2.0.4 and recalibrated my battery. so far it seems battery life is consistent with my previous kernel (suckerpunch #56) but everything is much smoother.

no sleep deaths yet but I'll report here if I have any.

Thanks for the great work, Existz. my phone is running great.
[Captivate Android Development] AReynante:
I have a 1007 warranty model, running perfect. Never had any deaths, except on early suckerpunch. But later sp and onix are running fine :)
[Captivate Android Development] rajendra82:
I have a build 1007, and my GPS has never been bad enough for me to say that it sucks. It's been great, ever since I flashed the PlumbBob 1.0 fix.

And no charge or sleep death ever, although build 1007 is well before the affected IMEI phones stopped being manufactured.
[Captivate Android Development] VFO:
Well the Sleep Death issue has reapeared for me. It is not as frequent as with 2.0.3 (would die at least 4 to 5 times a day with 2.0.3) but I have had 3 occurances since installing 2.0.4. My phone is a 1011 and not OC or UV. I never had the issue before going to Onix but it is just an annoyance and worth it for the performance of the kernel.
[Captivate Android Development] H3llstorm:
I had to revert to Onix 2.0.3 due to lock-ups requiring battery pulls while scanning QR codes on Appbrain.com.

Scanned a QR code with 2.0.4 overclocked to 1200 with no u/v - lock-up

Scanned a QR code with 2.0.4 with no o/c or u/v - lock-up

Scanned a QR code with 2.0.3 with no o/c or u/v - no lock-up

Scanned a QR code with 2.0.3 overclocked to 1200 with no u/v - no lock-up
[Captivate Android Development] nickm50:
I have gone back to 2.0.3 as well. I am experiencing lagginess and lockups.

It all went away when I went back to the older version.
[Captivate Android Development] jon.groves:
I have been getting this too. I tried clearing cache/dalvik cache, and I clear my voltage settings and reset them. Nothing worked except for reverting to 2.0.3
[Captivate Android Development] johan8:
What steps are you guys enabled ?

I have barcode scanner lockup previously with 2.0.3 and before.

Try disable 600,900Mhz, and no uv at all.

Mine is stable now with 2.0.4....... but still have barcode app lockup sometimes.
[Captivate Android Development] b0wz:
Ditto on the revert to old.....100mhz please....no likey the file conversion, saw weird stuff with icons and apps missing, all was good on the swap back to old.
[Captivate Android Development] LNJ:
Guys don't rule out that certain apps may be causing issues in the background as well.

Run some type of system monitor to check which apps or processes are consuming ram and cpu cycles.
[Captivate Android Development] Johnny Paranoid:
+1

I recommend OS Monitor.
[Captivate Android Development] bududroid:
it work on sgs international?

Sent from my GT-I9000
[Captivate Android Development] existz:
No, its reoriented for the captivate, your sound/auto rotation will be off
[Captivate Android Development] H3llstorm:
I always have 600 & 900 disabled, and as I stated, I wasn't u/v at all.

I cleared the dalvik cache before I reverted to no o/c or u/v. I cleared the dalvik cache again when I reverted to no o/c or u/v, and a third time when I reverted to 2.0.3.

I used Advanced Task Killer and and a Level 2 clear with Task Manager to make sure there were no "rogue" apps or services running in the background. This was not the issue.
[Captivate Android Development] pimpnmaxima:
I was having problems when hitting the home button while the camera app was up. Doing as you recommended solved my hard lock up problem. Thank you very much. 1.3ghz OC with minimal UV NOW(as suggested). Disabled 600 and 900 (as suggested).

Still wondering why disabling 600 and 900 helped anything.

I am running 2.0.4 1000 on Phoenix 7.0 with Modem KC1
[Captivate Android Development] existz:
If you have too many steps enabled it can cause lag/problems, as there would be extra steps the cpu has to scale...slowing it down .. I usually keep it where there's a step every 200 mzh (100,200,400,600,800,1000)...you can try to re-enable the 600 to see if it still does it...if it works then I recommend keeping it, as it helps alot with battery.. if it doesn't work, then keep it disabled...but of course its all up to you .. But in 2.0.4 the 900 step was disabled by default (will only effect if you delete voltage settings or if you flashed onix for the first time...if you had settings saved at boot it will stick whatever you had it saved as before) ... but certain phones like it, some don't...mine works fine with 600/900 ..but I usually just use 600
[Captivate Android Development] LNJ:
I'm currently only running up to 1.2Ghz and the only step disabled is 1120.

But try the suggestion of removing 600 and 900.

I know 600 was a pain to UV for me compared to the others. Anything below -100mv would lock up. All the other frequencies took -125 to -150 with no issues.
[Captivate Android Development] existz:
Ive been thinking about releasing nightly builds.. I have made a script that will compile, package up a cwm zip and then upload to my ftp server every 24hrs automatically.. of course "IF" i do release nightlys, they will be "AT YOUR OWN RISK!!"..as it will compile my source the way it is at that time..so it will be untested, could cause a soft brick..or worst.. etc..etc.. there would be no support for nightlys, all changes would be on my github.. but i compile and flash atleast 3-4 times daily so there shouldnt be any bricking problems, but just wanted to mention that.. as it could!.. so what do you guys think? That way you can test what ive done at up to that point, instead of me releasing build after build..etc.. when trying to fix a problem..let me know what you guys think, im still undecided on it, so who knows what ill end up doing, but figured id throw it out there and see what you guys/gals thought
[Captivate Android Development] LNJ:
I'm game. I have no SD problems like some of the guys but I have an unusual battery drain. This is after a few cycles.

For example it was 100% at 2:45am when I took it off the charger. 15 mins later I turned on the screen to set my alarm and I had already lost 3%

Turned off the screen and woke up at 6:35am and I was at 81%

I was noticing the drain for a couple of days and I thought it was modem related and went backt to JVK for KC1.

Plus I charge my phone 2-3 times a day so since the release of 2.0.4 it has had at least 5+ cycles and calibrated.
[Captivate Android Development] H3llstorm:
As stated in the first line of the post you quoted (bold added for emphasis)
[Captivate Android Development] GGXtreme:
After flashing 2.0.4, my phone will no longer indicate whether or not USB debugging is enabled. I am running a modified Serendipity 6.2 and I've already tried clearing cache and dalvik cache. USB debugging still works, but pre-2.0.4 I would see the notification that said "USB debugging enabled" when I plugged in my USB.

Also, I've been getting terrible and inconsistent battery drain with both 2.0.3 and 2.0.4 (not earlier versions). Even after full calibration, clearing battery stats and drain/charge cycles, I sometimes get a normal 16+ hours, sometimes my phone is dead in 2 hours with no use whatsoever (data/wifi/gps/sync/background data all off, no background apps or active widgets). I was also experiencing some sporadic slowdowns with my phone, but disabling the 900MHz step and enabling 1200MHz seemed to fix this.

Another thing I'm wondering about is the 'wifi error fix'. What exactly is this? For me, it hasn't fixed anything. I still can't get wifi to turn on about 50% of the time, the only difference now is that I don't get "Error" (it just turns back off immediately instead).

Aside from these hiccups in the latest builds, my phone generally runs as well (if not better) than the last Suckerpunch kernel and can achieve similar battery life.
[Captivate Android Development] goodolsen:
I'm running 2.0.4 and Serendipity 6.3 and when I plug in my USB cable with SUB debugging turned on it just says USB connected. Though this isn't kernel related, I believe they took the debugging icon out of the notification bar in Serendipity.
[Captivate Android Development] b0wz:
I think it would be good for testers, but not knowing what changes were made, or no change log....would probably drive me nuts (but then as an IT admin...i kinda have to be anal about that stuff) blind trouble shooting sucks!!
[Captivate Android Development] LNJ:
Sorry man I'm out of ideas.

I know you mentioned you don't OC/UV but do you have the VC app installed?
[Captivate Android Development] bamonkey:
+1 i would be very interested in this. Im just going to say it outright, there are a ton of captivate developers leaving the past few weeks, cm7 progress is very slow right now...i understand the process and whatever but to be frank and make a joke of the situation to make me feel better we will probably have a full cm7....never.. i see the more developers leaving in the future and its not the SGS fault anymore...people just want the "new" stuff. I dont see any need to jump ship yet my device is great with the work xda developers have put in so far. SOOO existz...congratulations because your thread is the only one im following for the 'future' of our device. If i wasnt moving to a new house, saving to get out of my apartment and blah blah blah life event *lol* i would be donating RIGHT now. So keep on because i like your attitude and respect your skills. I may upgrade my phone but honestly the only thing looking sweeeet is the Galaxy 2...yes its samsung we know how we feel but samsung devices are the only ones that dont break completly down... my HTC tilt2 makes a negative case just like samsung but i honestly like my device. anyways rant over hope you decide on nightlies... i would certainly test them as soon as they came out. i do fear for the "why doesnt it work" naggiging that might hit you thou:p
[Captivate Android Development] H3llstorm:
I use the VC app to disable 600 & 900 and enable 1200, with no u/v.

I have no idea which of these changes are responsible...

... but somewhere between Barcode Scanner and the Android Market, I get lock-ups with 2.0.4 that I don't get with 2.0.3 - with no other changes.
[Captivate Android Development] existz:
You can see my changes on github... https://github.com/existz/linux_gt-i9000/commits/onix-2.0.x-dev
[Captivate Android Development] LNJ:
Uninstall the VC app just for kicks and reboot into recovery and do the delete voltage settings just in case and give it a whirl.
[Captivate Android Development] H3llstorm:
Just for kicks, I'm gonna leave things the way they are - working. :cool: