yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] airtower:
I backup all user apps and data, and only the system data elements in green (alarms, wifi access points, bluetooth pairings, etc). Then I have a schedule set up to redo all backups nightly. This way I can easily restore everything I have because I've only backed up restorable elements.

Whenever I go from rom to rom, i redownload everything from the market to be safe and only restore user app data, but that's just me. You can probably get away with just restoring all user apps + data.

Tibu differs from a nandroid backup, which is an entire system image. Tibu only backs up app data.
[Captivate Android Development] mbc663:
The i9000 forum refers to it as such
[Captivate Android Development] tallsilver:
Working fine

AOKP23 working good with B5. Don't mess with diddle. :D

Thanks, Glitchmiester!!
[Captivate Android Development] apg5031:
how is your battery life?
[Captivate Android Development] nakedninja42:
B5 working great with THS Build 16.
[Captivate Android Development] leezrd:
Thanks for letting me know was wondering if would work with v23.. And go *****
[Captivate Android Development] ptesmoke:
is your data always displaying H?
[Captivate Android Development] apg5031:
is the AOKP23 similar to

http://xdaforums.com/showthread.php?t=1503769

?
[Captivate Android Development] leezrd:
I think they are all based of the open Kang project wich is nexus s based
[Captivate Android Development] tallsilver:
Very good. I'm not a heavy user except when I'm flashing. :D

It's not quite as good as KK4 was but darn close!
[Captivate Android Development] billyjed:
Have you tried doing everything from CWM? I always shutdown the phone and then use the 3 Byron combo to get into CWM to flash and backup/restore.
[Captivate Android Development] tallsilver:
Only problem I had was the B4......SOD but B4.1 fixed that and B5 hasn't had any problems.

I'm running 1300 max with 105 overclock and all seems well.

Charleston, eh? Yardcocks threepeat!!
[Captivate Android Development] billyjed:
Are you talking about restoring or backing up? I ran into the same problem restoring and just restored twice and it worked the second time.
[Captivate Android Development] tallsilver:
Your life will be much simpler if you "forget" Rom Manager!! Use CWM to install the zips...........works for most everyone else. ;)
[Captivate Android Development] leezrd:
Mine didn't over clock very well past 1.2ghz and doesn't play well with under volt....

And i live in Lancaster now but still chucktown to the heart
[Captivate Android Development] scottcwhite:
@ Tk-Glitch - I've been using smartassV2 govenor but would like to know what govenor you run personally as your OC, etc knowledge far surpasses mine. i.e. did the tweeks you made to conservative (don't see anything names Franco so I assume the one titled conservative is the one you speak of in your changelog) for more speed make it better now than the renamed saV2 ?

Also, I've read the Live OC guide provided in the OP 3 times and my simple mind is still not grasping the whole ARM/INT voltage tweeking thing. Because of my lack of knowledge should I just leave them at what they are set at with your kernel ? Is this a fairly good setting or is there a specific adjustment I can make that would gain me a lot better battery, etc. ?
[Captivate Android Development] nakedninja42:
My wifi has been connected the entire time since flashing, hadn't been paying attention. As soon as I read your question I turned wifi off and it showed H then switch to 3G then back to H since I was using data. I'll keep my eye on it for couple hours and let you know.

I am using KB3 nexus s modem.
[Captivate Android Development] ptesmoke:
much appreciated thanx man. mine used to fall back to 3g when data wasnt in use...now its constantly on H all the time. itll flash to 3g briefly but goes right back to H within a second. ive never seen this behavior before im used to it idling on 3g until data is needed. im on att right now as im down in florida for work. dunno if its a network issue as if i go into the advanced settings and set the radio to umts only itll stay on 3g... very odd. also if i click 2g networks only that works as well. im currently on jk4 modem....but ive tried jvu,kp1 and the one you mentioned to no avail. same behavior. ive also wiped and wiped and fresh installed THS build 16 with stock kernel...same behavior. flashed glitch beta 5 same behavior, now back on beta3 and same behavior. im out of ideas lol

edit: id do a reflash to stock but i do not have access to a pc here...and im pretty sure odin is the only way to flash stock and master clear...unless there exists a way with cwm?
[Captivate Android Development] sixstringsg:
I've never seen the behavior you described. When you have HSUPA signal, the H should always be displayed. It shouldnt switch to 3G as far as I know, regular 3G doesn't have better battery life than HSUPA.
[Captivate Android Development] ptesmoke:
six, ive also read your take on this as well. tho even with my desire z it would sit idle on 3g until data was needed and then fire up on H. ive just flashed the nexus modem kf1 and it now behaves as i describe. idles on 3g and when i open something that needs data the H comes up and data goes...

i know this may sound backward but this is the behavior ive always seen on my past 5 android devices. also when i was stuck on H data was very unstable...and phone got very hot. i have no idea what the issue was.
[Captivate Android Development] techguy615:
Same issue here as well. I went from beta3 to beta5 and the problem developed. I fixed it by rebooting back into recovery, fixing permissions, and then running the backup again. After that it ran without any problems. I have yet to do a restore yet and see if that works.
[Captivate Android Development] TheSoaresan:
Works on those states well
[Captivate Android Development] nsyik:
Without wifi on, no SOD occur. With wifi, SOD when screen turn off. On THS build 16. No OC/UV, with the amazing glitch v14B5

*all of sudden, SOD occur again. Even with wifi off.
[Captivate Android Development] jerkysh:
Spoiler alert!!!

Flashed the B5, love the modded GlitchassV2 , running smoothly, no problems with OC + Live OC... Thanks sixstrings!!!:thumbup:
[Captivate Android Development] ptesmoke:
ok so i flashed the nexus kf1 modem and it seemed to have fixed my data issue. i think may have been caused by the kb3 nexus modem. i just tried reflashing kb3 and wiping cache...resulted in stuck H icon and hot battery. flashed kf1 and cleared caches...data works as intended (idles on 3g and fires up H when needed) no hot battery.

hope this helps someone who runs into this sometime...
[Captivate Android Development] ChuckDaEngineer:
I am having the same backup issue with V5. I reverted back to Beta 3 and all is well.
[Captivate Android Development] krufttangoud:
I use CWM almost exclusively, first time I tried the updater.
[Captivate Android Development] zuN!:
"Added a DIDLE enabler into screensate scaling script to kill BT in sleep and make DIDLE work with both TOP=ON and TOP=OFF. You'll need to enable screenstate scaling in Glitch menu from recovery in order to get DIDLE to use this (disabled by default). It's mostly for testing purposes - Feel free to report your experience with it"

"- A few fixes on the wifi driver to work better with our devices Please report your experience with DIDLE enabled. It may be required to disable DIDLE on some phones to prevent SOD/COD/softreboots or other instabilities. Also MAKE SURE YOU HAVE A DAMN GB BOOTLOADER"

My phone enters the DIDLE TOP=ON state with WiFi. The fixes on the WiFi driver seem great as my phone hasn't had any SOD or reboots and enters DIDLE quite nicely.

Does entering DIDLE only occur if you're using WiFi/GPS/BT/listening to music?
[Captivate Android Development] phrix626:
I just flashed b5, now BLN times out after a couple of seconds no matter what I do. I've tried adjusting timeout setting in NStools and the BLN control app. makes no difference. Any thoughts?
[Captivate Android Development] Geoff-dev:
Beta 5 - Signal bars

Dropped B5 on THS build 16 using KP1 modem on the i897. Everything is working great but the bars on the top for cell tower strength are blank. Ran Network Signal Info and it showed what would be 5 bars of strength. No mods to OC or voltage.

Other then that, all is working perfectly. Looking good guys! Thanks!
[Captivate Android Development] ptesmoke:
yea i have no idea whats been changed ril wise but i now only have one modem that works properly. kp1 gives me stuck H with broken data now...but i also wiped and reflashed build 16 andwas still borked. can garbage in your efs folder mess this up somehow? it seems ever since i flashed a nexus s modem from this dev forum things havent been the same. im stuck using kf1 nexus modem now as nothing else works...
[Captivate Android Development] sicmadek:
which scheduler and governor is everyone using. i left it at default for a while but im trying the smartassv2. it seems a lot better than the glitchondemand. i thought noop was a good scheduler, so why fiops? i dont want to oc or anything. i just want responsive and smooth.
[Captivate Android Development] topiratiko:
Fiops and Glitchass v2

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14B5
[Captivate Android Development] shuyin1102:
+1 SOD only when wifi on. I tried to enabe screenstate scaling in cwm but the phone stuck in kernel logo. So i think i will turn off didle and wait for the fix.

Thanks for this hard work, the wifi and proximity sensor are really great!
[Captivate Android Development] RootTheMachine:
Same problem here. I don't get why there is a different implementation now in this kernel if this kernel is supposed to officially support CM9 only. Don't make me go back to v3...

Oh, and also, setting CMLed to 180 or below causes one softkey to stay lit. Really weird behavior
[Captivate Android Development] nuwan32:
hmm so i just flashed v14b5 and i still cant use didle. everytime i i turn off my phone it never reboots, it just dies with didle on. i even enabled screenstate scaling. anyone else having this problem?
[Captivate Android Development] sicmadek:
i dont see glitchass, only smartass. im on b3 btw.
[Captivate Android Development] topiratiko:
Glitchass=smartass renamed in b5

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14B5
[Captivate Android Development] scottcwhite:
It was also modified when renamed. Ton of changes were made in b5. Update from b3

---------- Post added at 12:13 AM ---------- Previous post was at 12:03 AM ----------

Same here, live oc 110%, max 1320. Phone is super fast and smooth a silk

---------- Post added at 12:16 AM ---------- Previous post was at 12:13 AM ----------

BLN is definitely no longer working. Hope this gets fixed soon
[Captivate Android Development] cheese74:
I'm trying to backup. One other factor is that maybe there is some kind of corruption in my internal SD card. When I plug it into Windows 7, it keeps popping up a dialog box about fixing it. Running chkdsk on it results in the scan not completing and exiting with:

"xxx\xxx\xxx is entirely unreadable. folder entry removed"
[Captivate Android Development] sicmadek:
everyone is having too many problems with b5. ill wait for fixes cuz i cant live without bln.
[Captivate Android Development] scottcwhite:
I wonder if the bln app from the market would work since kernel is already set up for it
[Captivate Android Development] Javier.San1993:
Anybody have any good settings for colors in codename Android 1.3.3?

Sent from my SGH-I897
[Captivate Android Development] Javier.San1993:
BLN works fine for me...

Sent from my SGH-I897
[Captivate Android Development] Silencer96:
IcyGlitch VB5 has fixed my problem with the screen touch response freezing up occasionally.

Thanks for the superb work guys! :)

Edit: DidleV2 is very problematic for me, Glitch B2's Didle mode was much more efficient for me. Now, whenever I turn off my Cappy's screen, my phone turns off permanently -_-' And no, I didn't play around with the voltages or anything in NSTools...
[Captivate Android Development] shuyin1102:
I have flashed b5 and now i can enable screnstate scaling in cwm, but the DIDLE seems to be conflict with the wifi when sleep, only works without wifi
[Captivate Android Development] sinichi21:
CMled does not control the BLN led it control the softkeys light timeout its the same control on settings/ advance/ backlight timeout setting it to low will make the light have that behavior since 180 milliseconds is too fast the lowest on the the settings is 1.6 sec which is 1600 on the nstools cmled

BLN works fine did you guys check the pulse light notification and on Nstools service enable service for bln miss call and timeout its Located on the settings on nstool.
[Captivate Android Development] Boldizzle:
I must be blind coz I don't see any b5 links on the OP?
[Captivate Android Development] Koizuma:
Click here

and take note of the file name that pops up labeled B5, it was in the OP but its still labeled as B4 in the OP :P
[Captivate Android Development] RootTheMachine:
I'm aware, and how does your bln work? Are you on THS?

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] apg5031:
if you are having issues with BLN going away in 5seconds. you can download the BLN Control app from market place. It will work fine. Or mess around with NSTools.
[Captivate Android Development] sicmadek:
i installed b5 last night, then went to bed. when i woke up this morning my phone said mobile network unavailable. airplane toggle did not help. i only got service back when i rebooted. did something change with the ril?

im on kf1 modem btw.
[Captivate Android Development] daskanda:
Which rom are you using?
[Captivate Android Development] sicmadek:
weui which ive been on for weeks with b3
[Captivate Android Development] RootTheMachine:
Bln definitely doesn't work. What are your exact settings on either app?

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] sixstringsg:
First off, this is why we didn't want to do BLN. second, those with issues, if you don't set your buttons to time out while screen on, they shouldn't when screen off.
[Captivate Android Development] apg5031:
i got the BLN Contro pro app

my settings are

BLN Status Enabled

Activate BLN

Open BLN Blinking ->

Activate Blinking - ON

Blinking Duration (total)

3h

ON Internval Length

2sec 0m sec

OFF Interval Length

0sec 500m sec

DONE

NStools

Backlight notification

Status ON

LED Timeout

0sec

CMLED

LED Timeout

1800sec

Yes, it will blink, but ts better than having it on for only 5secs.

---------- Post added at 04:43 PM ---------- Previous post was at 04:43 PM ----------

hopefully u keep the BLN on the next release...it is pretty good....
[Captivate Android Development] pickupman66:
I had internet Issues with B5. Extremely slow, not waking up after screen off. Could not even pull up the weather... Swapped back to B3.
[Captivate Android Development] ptesmoke:
if im having radio issues...and no access to a pc or odin...would a cwm flashable gingerbread rom fix anything? and flash back to ics? i realize this is off topic but alot of experts in here specially the glitch devs whos advice i greatly appreciate.
[Captivate Android Development] tbrummell:
I was wondering why mine was doing that! LoL
[Captivate Android Development] airtower:
I say screw BLN. The only thing it gets you is the ability to flash and timeout the LED's. The 1% of people that want it talk it up so much it seems like there's a following for it.

Button timeout for me is set for never. Some notifications keep the lights on, some never at all (i've never noticed it time out, but then again i dont get notifications and just stare at the lights). I saw similar behavior when BLN was implemented in the GB kernel.
[Captivate Android Development] apg5031:
but not all the ROMs work on cmled.....as far as i know some are on BLN...or am i mistaken?
[Captivate Android Development] sicmadek:
how exactly do i disable bln? does the box in nstools need to be checked or unchecked?
[Captivate Android Development] RootTheMachine:
Thanks six, this does work. To the person who posted their settings with blinking, be aware that the blinking consumes battery more than static lights.

This whole bln thing is a situation of "if it ain't broke, why break it?"

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] topiratiko:
A lot of us love bln. Looking at the phone and seeing keys lit NOTIFYS you of an alert...hopefully we can just revert a thing or 2 as it was fine on prior releases...shuts off after 5sec now

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14B5
[Captivate Android Development] topiratiko:
I've set the time out to 0 in every available application galaxy s settings bln app and also an nstools and they still timeout after 5 seconds

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14B5
[Captivate Android Development] airtower:
however this kernel only officially supports CM9, with has perfectly working LED notifications

Oh believe you me, I want the lights on when i get a notification, but LED notifications and BLN are not one in the same. LED notifications does the same thing. It works fine in CM9. Only extra thing BLN gets you is the ability to flash the lights, which consumes more battery.
[Captivate Android Development] topiratiko:
Your right. I didn't mean bln the app. Led notification did work fine with 4.2 and b3 but b5 the lights timeout in 5 sec. I just wish there was a workaround. I'm happy with teamicssgs 4.2 and although I would switch to ths because of the back button kills app option...I DONT wanna start all over again :/

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14B5
[Captivate Android Development] Oxicottin:
So with the new kernel how do i just get the led to work like it used to like when i miss a txt or call the buttons stay lit, dont care about blinking.
[Captivate Android Development] krufttangoud:
V5 working great.

DIDLE OFF

glitchondemand

OC value 105%

MAX 1260

UV is stable

INT volt set to High Leakage.

fiops

Oh and WEUI 6.6

So far lasted the entire night, no issues.
[Captivate Android Development] zuN!:
Exactly.

Glitch kernel officially supports CM9, so stating that other ROMs don't support CM LED is not a valid argument in this case.

I agree with airtower, screw BLN. It's always been so finicky compared to CM LED.

Sent from my SGH-I896 on Pre-CM9
[Captivate Android Development] capocaccia:
Agreed. Performance and stability > features (didle, bln, OC/UV,)

But I will say, the one thing that kernels I use MUST have is voodoo sound. Its probably the one thing besides a ROM that changes my phone in a way that I am impressed with every single time I use it. Voodoo color is nice too but its not a must have.
[Captivate Android Development] airtower:
step one: read the last 10 posts in this thread
[Captivate Android Development] Oxicottin:
Step two.... Why does everybody always assume nobody reads you always have the idiots that wanna be cool and waste people's time with smart ass answers like this one. Cant anyone post a helpfull post/answer. Thats all i do is read then if i cant find my answer then i post. I answer posts and pms all the time in my thread even if they have been asked over and over mabe im just nice!
[Captivate Android Development] eddalysse:
Amen to that Oxicotin
[Captivate Android Development] k2ham:
I'm with you. I've been reading and keeping up with this and have the same question as you. I think I've put in sufficient effort trying to figure it out but am still confused. It was a simple question and likely there is a simple answer if someone would kindly provide it.
[Captivate Android Development] airtower:
I apologize for being terse in my reply. In response to your question, BLN control supposedly works. Although I can't confirm, since even though I own a license for it, I won't install it over principal :D. CMled should work in a CM/MIUI-only kernel.
[Captivate Android Development] sinichi21:
Yes I am on THS build 16 and it works just fine you cam download the bln app on the market like the other guy said it works also
[Captivate Android Development] airtower:
I went ahead and tried it, but no dice for me. Lights timeout after less than a second. Not, and won't be, using flashing.
[Captivate Android Development] scottcwhite:
I agree with the above and I to MISS BIG TIME my soft keys staying lit up when I have an unchecked notification and really hope it get's working again in a future release. Right now they go black after 5 seconds.

However, I'm on ICSSGS wich this kernel does not support so I don't have a leg to stand on when it comes to complaining about non working functions.

Additionally, when I bought my Captivate it didn't have that feature either so I'm content to live with either.
[Captivate Android Development] Oxicottin:
Thank you for your responce.... I have BLN pro also and after messing with it and trying everyone's settings that was posted i too can not get just the buttons to light up and stay lit untill i wake phone. I uninstalled it and i get nothing. Im sure it will be fixed in the next version, I hope. I think im going back to v3 where it worked but the v5 is running better for me.
[Captivate Android Development] scottcwhite:
Same here with me. The smoothness of 5 outweighs the BLN working on 3
[Captivate Android Development] sinichi21:
ok heres what i did I think the nstools does not recognized the changes until you reboot your phone since i frequently reboot i did not notice it im not using bln app just the nstool. Now if you guys want it to function like the cm led on ns tool make sure the led timeout is 0 and status is on now swipe all the way to settings and uncheck the nstools service then reboot. make sure you guys also check the pulse notification on the setting advance on THS see if this helps.
[Captivate Android Development] airtower:
Here's what I've tried:

No BLN Control App, CMled on, nstools BLN service not running - no lights

BLN control App, CMled on, nstools BLN service not running - Lights time out after >1 second

BLN control app, CMled on, nstools BLN service running - no lights (BLN control app test notification doesn't even go away when i unlock...strange)

No BLN control app, CMled off, nstool BLN service not running - no lights

rebooting between all three, pulse notification light always on with no timeout
[Captivate Android Development] prbassplayer:
Thank you. The reboot part did the trick. On a side note I understand all of you opinions against bln, but I'm grateful that the Glitch team implemented BLN. There is a surplus of ICS Roms on the I9000 thread for us to use but no kernels for i897 except Glitch. So Thanks
[Captivate Android Development] sinichi21:
Where is my thanks button :p joke but yeah I totally agree with you im grateful for tk since we dont have enough kernel he is doing the best he could to help us. Everyone just be patiently wait and give time rather than raging to take this off, why this and why that give it time lately i see people dont have patience anymore pls let not pressure tk or six on this issue they have the right to do what they want lets just suggest or ask politely
[Captivate Android Development] prbassplayer:
Sorry thought I had, Tapatalk decided to denied I guess xD
[Captivate Android Development] airtower:
So this is weird...

I flashed back to 4.1, then 3 trying to get CMled back. Still didn't work, so I went back to b5. A test sms I had sent myself but never read (using goSMS) renotified and the LED's worked! No BLN control or messing about with nstools settings (they were cleared on kernel flash). But, after sending myself another test sms, the LED's did not stay lit after the screen turned off.

yes, BLN is indeed finicky.
[Captivate Android Development] shaker2k:
Question. I know this has probably been covered, but I'm on the road with no computer so it is harder to search.

Anyway. What is the biggest danger when over clocking? Heat?

Also is getting to 1400 mgz by oc+ live oc ,better than straight oc to 1400 with no live oc?

Thanks!
[Captivate Android Development] prbassplayer:
Heat and voltage.