yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Sledutah:
Same here, Titanium backup is failing to restore any data and it's now missing some google apps (maps & voice) after restore. I always restore Missing Apps + Data. I noticed data from the restored apps missing so tried to restore some things individually, that is when it fails to restore data. I've never had this problem and I've flashed many different roms from eclair to froyo to gingerbread and never had this problem before.

I'm going to try another rom now and see what happens. I'll edit this post with the results.

Edit: I installed another rom and the same thing, no data is being restored. Guess I'll flash Continuum and start over :(

loraque: Thanks, I did do a factory reset before I flashed Continuum (2x) and before I tried Serendipity VII again. It didn't make any difference.

Was there a update for TiBu in the last few days, maybe that's what happened.
[Captivate Android Development] loraque:
Factory reset, reload the ROM. Should take care of it.

I had some issues with restoring apps coming from JVB/JVH to JVO. I assumed it was something similar to what I experienced the first time I installed GB and tried to restore the backup- same symptoms. For some apps, I had to install and start over as the backup files were disliked. Only a few though.
[Captivate Android Development] Holmes108:
I always see people saying to never backup/restore SYSTEM settings in Titanium Backup.

I see the obvious complications of going ROM to ROM using that feature, but is it still a "no-no" using it to backup and restore system settings within the same rom?

I assume if you're going to use the same rom, then CWM/Nandroid is the better way to go, but I"m just curious.
[Captivate Android Development] Overgloc:
Anyone getting sleep death in 5.6? Happen twice since lastnite. Turn display off for about 30 mib and had to pull battery to reboot.
[Captivate Android Development] cbasse:
Yes - just happened to me last night. Left phone on (not plugged in) when I went to bed, woke up to blank screen. Tried powering on the normal way, but no luck. I had to pull the battery and then power up. Battery dropped from somewhere around 80% to 50%.

I've been reading all about the battery drain issue, but haven't been able to find a lot about sleep death. Is this just a by-product of 2.3.3, or is there something that can fix it?
[Captivate Android Development] emooheo:
5.6 is lagging pretty bad for me. What should I do?

also have had a few random reboots. The worst was when i used TW launcher and used the 4 slider unlock. Rebooted when i slide the green circle one and when it booted up the launcher kept force closing whenever I unlocked Had to reflash.
[Captivate Android Development] typ44q:
It is a known issue, check the release notes. If you assign a function to that button the problem goes away.
[Captivate Android Development] Overgloc:
Well atleast I'm not the only one. Gonna try a reflash later see if that help.
[Captivate Android Development] alexige:
There really is no reason from what i've read and learned to restore system apps because you can run into complications or restore over what ever modifications the rom developer made. I notice the TiBu guys have been working with system app restoring, kinda curious what they are trying to accomplish myself.
[Captivate Android Development] nikooe:
Hi all. When miui lock screen is showing missed call, it reboots as soon as I pull it down to see the call. But when there is no miss call it works fine and jumps to the phone page? Any ideas?
[Captivate Android Development] carey:
Move all apps to internal storage

Disable all the tweaks in the tweaks app

Convert the file system to whichever one you aren't using now

I came, I saw... I left confused
[Captivate Android Development] cbasse:
Let us know if that helps...
[Captivate Android Development] Vivified:
no-a-time tweak is very much recommended by existz
[Captivate Android Development] gocats7:
Haven't posted in a while, things are so smooth. Battery is awesome. I'm on 10 he's on battery with 35% left. But I have a total of over 3 hours of combined display and calls. I do email push every hour during the day, manual at night. As always, super ROM.
[Captivate Android Development] mrhaley30705:
Make sure apps are stored on internal memory, not external. Restore apps first, then go back and restore data.

Yes, Maps was not included because of a battery drain issue with v5.4 and newer(maps, not Continuum). Don't know about you tube. I have it.
[Captivate Android Development] gocats7:
Sleep death for me only happens anymore if I have wifi on. For some reason if I turn that off I'm good. Woke up the past week at 98-100% everyday. I do reboot before going on charge if wifi was on. May just be me.
[Captivate Android Development] mrhaley30705:
Glad to hear you finally got every thing straightened out.
[Captivate Android Development] RN_ReFlux:
Youtube thing was just an idiot moment from me, sorry. Still unable to restore app data, bit someone said there was a problem if coming from a jvh rom to 5.6 so...that sucks. Thanks anyway.
[Captivate Android Development] mrhaley30705:
I had a problem with it using TiBu, but I also used My Backup Root as an extra bu set and it restored every thing (except Shoot Me, which I expected).
[Captivate Android Development] daveyian:
Almost exactly the same problem for me too, except I was plugged in (it still dropped to 60-50%).

I also just now turned off my phone after using it for a little while because it was very hot.

Someone mentioned their problem linked to wifi but mine is never turned on.
[Captivate Android Development] carey:
There are a few that I ended up turning back on. That one, VM:dirtyness, and SD:speed tweak

Shutting them all off should improve the lag greatly. Then try turning those three on an see how it is working

I came, I saw... I left confused
[Captivate Android Development] bferguson:
Im so absolutly pleased with the new version..even though ive only had it installed for 30 mins. Excellent work bro!
[Captivate Android Development] nelsonw:
New ROM is avalaible: http://www.samfirmware.com/apps/blog/show/7340353-android-2-3-4-hits-galaxy-s-gt-i9000-

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] harpo1:
Old news plus there's already a ROM out based on JVP.
[Captivate Android Development] Soccer_Dad:
People always say "Don't restore system settings, but it's a time saver when it works. I've had good luck (skill?) with the system settings in MyBackupRoot. I backup System Settings and Android Home (along with all the other normal stuff like SMS and MMS and my call log), and restore them in the new ROM, and all the settings I would have to go through in the settings menu are restored, with the odd exception of not restoring my default ring and modification tones. But my MobileAP network name and password are stored, along with every other change I would make in the settings menu. It probably saves me 20-30 minutes each flash.

Of course, I restore a few of the Green system settings in TIBU (Bookmarks, Wifi, and Bluetooth Pairings). And my Swype data.
[Captivate Android Development] iXNyNe:
To anyone having battery drain issues thinking its caused by maps would you mind testing (or just confirming my theory) that maps itself isn't causing battery drain but latitude is.

I have maps installed with latitude signed out and I'm not experiencing battery drain. When I leave latitude signed in (even when I have it set to not detect my location) I DO have massive drain.

Previous versions of maps with latitude (not sure how far back) did not seem to cause this issue.

I have not noticed a difference in enabling or disabling any settings in latitude, just being signed in seems to cause the drain.

Anyway, anyone else able to confirm this?

P.s. im using continuum 5.6 with the included kernel and modem in the Reno Nevada area if that matters (reception is nice :D)
[Captivate Android Development] bferguson:
I have yet to use either maps or latitude and so far this rom has been the most battery friendly rom ive used to date
[Captivate Android Development] loraque:
In my experience, it is anything that uses geolocation, Lattitude being a primary cause in my cause. Beautiful widgets was another that I had to disable geolocation on, to stop Maps from the battery drain. It is not necessarily Maps with the problem, but it is the system service that is getting "stuck" on my geolocation aware apps, since they are probably just using the stock method to find out where I am.
[Captivate Android Development] Sledutah:
Update:

Thinking I had a bad backup I deleted all my backups and created a new one. It was then that I confirmed that TiBu was the issue. This morning I see a update for TiBu, and sure enough in the notes it says it fixes the problems of not restoring data :rolleyes:

I've tried 5 different GB roms and this is by far the smoothest one. I've only had it running since yesterday morning so the battery hasn't been cycled yet. But, I had the best battery usage than I've ever had. 11 hours w/4 hrs display time. I usually only get 8 to 9 hrs w/2hrs (max) display, even when running froyo.

Thanks
[Captivate Android Development] Storm T:
Sleep Death

I had mine on last night and experienced sleep death. Woke up this morning and had to pull the battery before it would power on. Never happened with the last several versions for me. Leaving it off tonight to see if it happens again.
[Captivate Android Development] topiratiko:
Thats not a sleep death. Sleep death is just the fone shutting down on its own...it would fire right back up, what your describing is a lock-up/freeze...usually due to overagressive uv settings

Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate. Yea I get 2000+ on quadrant. Yea ive pulled 5.17 mbps down from a tower. I appreciate XDA helping me turn this phone into a beast.
[Captivate Android Development] schtuka:
I love Caesar's work and never had a single problem with his ROMs, but latest release giving me so many issues I went back to 5.5. (sleep death, reboots, email/gmail repeated notifications) Will wait for next release.
[Captivate Android Development] yamaki123:
how can i get the function "vibrate on answer" work ?
[Captivate Android Development] kennonk:
Did you try a reflash? I have found 5.6 to be the smoothest bug-free release yet. Seems weird so many people have such radically different experiences on the same hardware.
[Captivate Android Development] mrhaley30705:
Settings/call settings/all calls/outgoing call vibration
[Captivate Android Development] krufttangoud:
KTLO issue?

Has anyone noticed with an upgrade to 5.6, the loss of KTLO?

I have wiped/uninstall/reinstall. meh.

Bueller,bueller?
[Captivate Android Development] mrhaley30705:
Don't have it here either. Not really missed by me,i usually removed it anyway. I think you can get it from the market if you want it, or pull it from am old backup
[Captivate Android Development] tbong777:
ITs not the OMS. Its the Gingerbread release. It is still very buggy, All GB ROMS have the same issues and specific to phone issues. I found it to be too much of a crapshoot. BUT Every time I see a new ROM releases I read the threads to see if the issues have been resolved. Unfortunately the "honeymoon" wears off within a week on some of these ROMs as applications are used and different aspects of the phones are used. Then things pop up.

There WILL be a consistent ROM released as stable as the best Froyo ROMS in due time. I did my time beta testing. Now I'm waiting for Final releases and small tweaks like call recording and some other things Froyo got later in its development life.

The Eye candy is nice though...
[Captivate Android Development] mark1962nc:
May have been removed since the lights come on with a screen touch....looks like it is set to 5sec default.

You can dl KTLO from the market....there is a free version.
[Captivate Android Development] krufttangoud:
Yeah I have KTLO downloaded no dice
[Captivate Android Development] IDoMy0wnRacing:
Try going in this order: Uninstall, go into recovery and wiping your cache partation, Dalvik cache and fix permissions, reboot, allow to boot completely then reinstall. Go to widget, select KTLO, grant SU permission and you should be good.

KTLO is working on C v5.6.
[Captivate Android Development] krufttangoud:
Thanks I did it in that order again and it worked this time!!!

Nope...after reboot...doesnt work.
[Captivate Android Development] ottawadad34:
I just flashed the beta3 and the about phone still crashes
[Captivate Android Development] bluerap04:
In using UOT Kitchen, which settings are to be used under "File Upload"?

And which file do you upload?
[Captivate Android Development] joedoe:
Do I really have to go to stock before flashing C5?

Wouldn't it be just enough to wipe data and cache/Factory Reset with CWM as recommended in the http://xdaforums.com/showthread.php?t=1045734 thread by HaiKaiDo?
[Captivate Android Development] tysj:
I flashed the B3nowipe zip and it didn't seem to do much. Then I ran the Odin file and it worked but downgraded the kernel to version 6 but fixed the About Phone section. I just reflashed the latest kernel and all was jolly again.
[Captivate Android Development] koreancanuck:
icezar says in OP to flash the nobootloader from ODIN then flash beta3 to fix the About Phone issue. I did do it but it seems that about phone still crashes.
[Captivate Android Development] ottawadad34:
So you reflashed with odin and then flashed the beta3 and then the latest kernel?
[Captivate Android Development] waghoba:
Correct me if I am wrong. I have flashed b1 with bootloaders and now i am on b2 but i am getribg fc on about phone, so i have to flash the packahe without bootloader through odin and then flash b3?

And my data will ke kept?
[Captivate Android Development] tysj:
I flashed the zip first (not sure if it did much), then the Odin, then the latest kernel.
[Captivate Android Development] nikooe:
even after following this:

* if you have force closes on About Phone in Settings, flash the package without bootloaders with ODIN and then C5beta3 from clockworkmod recovery

I have FC on about phone.

any ideas?
[Captivate Android Development] harpo1:
I followed the instructions and installed the noboot from odin then B3 from CWM and still have the FC.
[Captivate Android Development] DigitalEagle:
ALL,

This is directly related to the keyboard. If you select the samsung keyboard as your default, the force closing will stop happening when going into your About Phone menu.

Using Swype and Android keyboard causes the crash. I had a similar experience when trying to import 2.2 keyboards into 2.3.

http://i.imgur.com/i6fsi.png
[Captivate Android Development] waghoba:
You are the man !!! I can confirm this is correct.
[Captivate Android Development] yahooserious:
I booted V2.0 and then the fixed kernal and I am loving using the GB. Thanks goes to the DEVs who keep working on this!

Question:

What modems can i flash to this now? I am bootloaded GB from V1.0
[Captivate Android Development] Rikusaki:
You added the Gingerbread keyboard. I love you. :)
[Captivate Android Development] rons_sacramental:
Yes by making Samsung Keyboard default (As said by DigitalEagle) does not cause FC for About Phone.
[Captivate Android Development] shoman94:
I am using swype... I have no issues.

Are people with the problem on a different theme then what comes stock?... Curious
[Captivate Android Development] DigitalEagle:
It appears Swype is actually working. My bad, I thought I checked that. Appears only the MTM Gingerbread Green keyboard is the culprit.
[Captivate Android Development] rons_sacramental:
Nope i am not on different theme then too i get FC for About Phone but i am using GB keyboard.

EDIT : Using swpye is not causing FC. Its just the GB keyboard.
[Captivate Android Development] tysj:
Still have that multitouch issue though :(
[Captivate Android Development] shoman94:
WHat the heck.... so before it was something else causing the issue or you loaded Gingerbread keyboard? And now it is still doing it again because the keyboard is now part of the rom?
[Captivate Android Development] Alexstarfire:
Anyone else been getting random restarts on their phones? It's happened mostly on the 5.5 and 5.6 releases for me, don't remember it happening before that. It's rather annoying as nothing seems to be triggering it.
[Captivate Android Development] jjtitus098:
I don't understand what about GB is too unstable for daily use? I have been using it since it's been out and never have any problems. Don't know what more could be added or fixed for it to get any better for me.

Sent from my Captivate running Continuum 5.6 with Talon kernel.
[Captivate Android Development] baghera1979:
Is it a restart or a complete shutdown, like have to pull battery to turn on phone again?

I had that problem too and thought it was the ROM at the time. I did some searching in the forums and found that a lot of cappys have had that problem. Theres a specific range- phones with imei numbers between xxxxx to xxxxx. i forget the range, i found it on xda. my phone fell in that range of numbers. turns out thats what was causing the restarts and shutdowns.

edit: heres the link, found it here

http://xdaforums.com/showthread.php?t=884289
[Captivate Android Development] harpo1:
More than likely it has something to do with the wifi issue. What's your wifi sleep policy set to? Additionally are you undervolting any?
[Captivate Android Development] harpo1:
Many of the bugs reported are user error. This guy has been going around for the last month to every GB rom and posting the same statement so take it with a grain of salt.
[Captivate Android Development] daveyian:
GPS Logging is turned on.

GPS Logging is turned on.

Just a heads up; I downloaded Nitrality from the Market.

It's free and is like SGS tools, or incorporates that and some other useful galaxy tools.

LbsTestMode has been replaced with AngryGPS in Gingerbread. At least on our phones.

If you go into secret codes in Nitrality the first thing listed is AngryGPS, it has a few more options than LbsTestMode has.

Under settings/general settings/GPS Logging, mine was set to ON so I switched it OFF.

Maybe something to look out for.
[Captivate Android Development] Alexstarfire:
Could be WiFi.... if only it didn't restart when WiFi was off. Don't know what the policy is set to as it's whatever is default for the ROM. I am currently undervolting but as I just switched to 5.6 today I haven't particularly looked into it yet. I had it happen at stock voltages once on 5.6 when I was setting it up, restoring stuff from TiBu and such, and plenty of times at stock voltage on 5.5 as most of the time it was stock volts. It could be OC related, but I haven't had similar problems before on 2.2 based ROMs. It's been pretty specific to 5.5 and 5.6 as I don't recall having seen in until I installed 5.5, which I did a fresh install on.

I can check it out if it continues to happen on this 5.6 ROM.

Restart. I'll literally be doing something, usually loading a program or switching screens, and it'll just be at the start-up screen all of a sudden. Doubt it's just my phone since it didn't happen with the stock ROM, nor any 2.2 based ROMs. I'll check the list just for the heck of it though.

EDIT: Well, just looking at the date I obviously had a phone that was in that "list" since I purchased my phone in October.... or was it August... or last year. However, in the post itself it says that a software update fixes the issue. The JH7 ROM, which is very old by now, fixed the issue. Or at least they claim. Anyone actually running JF6 these days would kind of deserve to have that issue. It would just be a reminder to update your damn phone.
[Captivate Android Development] Cezar`:
Did you try flashing talon 0.2.1 ? I posted a heads up on Continuum forum.
[Captivate Android Development] cowboi08:
Strange. I have it but I may have had it backed up with tibu.

Sent from me to you. Happy Birthday.
[Captivate Android Development] zerkai:
Hey icezar1, great ROM! Do you have any idea on getting the original "Samsung tune" ringtone to work? Moving it into system ringtones doesn't work, it continuously only plays the first 1 second of it repeatedly.

Also, do you think you can implement the "reset" feature for the Dialer when you reopen it so it always goes back to the dialpad screen?

Thanks.
[Captivate Android Development] tbong777:
It completely depends on ones tolerance for bugs and features whether or not a ROM is worthy of a daily driver.and at the end of the day the ROM is not the same improvement difference as Froyo was to Eclair to make it worth the known issues for now. Just read the last few pages of ANY GB rom...far more issues than not.

Too many are still having some basic issues. Charging issues alone disqualify GB for me as I charge every night. That would come and go depending on the flash more than the ROM. Then there are the sudden lag issues that appeared after a few days. Blank screen on call because of sensor bug. I have always had issues with Talon and Sucker Punch kernels on my phone and excal is not updating. DG has stopped developing 2.3.3 for now. There at too many inconsistencies and one off bugs from device to device. The inconsistencies between CW 2.5 and 3. No call recording available yet which I used a lot. Camera issues. WiFI Bug. Multiple flashes sometimes needed to get things working right. Random restarts. These are very much still in beta stage.

For many the bugs are acceptable. I just decided flashing my device every day to "fix" something or try another ROM was taking too much time. After all is said and done, It's only a cell phone and was taking hours daily from more substantial activities.

So now I read the forums and different threads looking for multiple pages of bug free comments before I try another GB ROM after a new release.

I am a proponent of the developers. I donated $20 and more to every Developer whose ROM I loaded whether or not I kept it. That is my thanks for their time not their product. The difference in "Smoothness" between a well developed Froyo ROM and GB rom cannot be measured. Its very subjective.

All that said I am going to give the first JVP release a try..Maybe 2.3.4 fixed some issues
[Captivate Android Development] krufttangoud:
I figured out the KTLO issue I was using the paid app and not the free app. Paid app has something broken. 5.6 cont/Talon test kernel.
[Captivate Android Development] Taderich:
In Continuum 5.4.1, Ihad the ability to record calls. I don't see this option in 5.6. Is this a setting I'm missing somewhere or a feature no longer included in 5.6?
[Captivate Android Development] FirstNoobToBrickHisPhone:
Isn't that illegal?

Sent from my Samsung Captivate.
[Captivate Android Development] DrDrrae:
Only in a couple of states.