yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Cezar`:
what do you mean by not being able to contact the office network?
[Captivate Android Development] Jep56:
Been runnin' 5.4 for coupla hours...no issues, except FASTER!
[Captivate Android Development] minotaur507:
The TUN.KO module is a part of the kernel that allows me to create a VPN link to my office. No TUN module, no VPN. Bascially, using it with the VPCC widget, I get an encrypted connection to my office from any place and the apps can't tell I'm not on my office network while I'm physically away from it. I can use it to check on my routers, switches, servers, etc.

It's a minor inconvenience at best...it just means that I have to pull out my laptop instead of doing everything from the palm of my hand. You guys just have me spoiled...lol. The office comment was more of a joke than anything else.

Thanks for everything you and existz do to make my otherwise crippled Samsung phone the most indispensible tool I have...without great developers like you guys, this would just be another phone...
[Captivate Android Development] nelsonw:
i have this problem: All time appears a Android Logo that says : FORCED UPLOAD by KEY PRESSING... for Usb UPLOAD...

it always happens with pressing vol+ HW keys...

Continuum 5.4 and 0.1.6 JVH kernel
[Captivate Android Development] cheetablaze:
I was gonna complain how 5.3 keeps rebootung while I make phone calls. Lol the person answers and it won't wake up... give it 30 seconds and it restarts. Here comes 5.4!
[Captivate Android Development] duuhdave:
Two really quick and minor questions. I'm unable to use the voice function in skype? I click on the microphone and nothing happens. Also I did a first time install onto my sister's captivate and there are no fonts included in 5.4? Thank you in advance. Besides these two issues I am loving this rom more than the usual lol.
[Captivate Android Development] yguns76:
I have also experienced random boots.

I did select Touchwiz as the default launcher.

I did wipe/factory before flashing ROM.

Flashing the Kernel with ODIN after fixed reboots.

attached is the logcat.
[Captivate Android Development] gocats7:
Same for me as well, will just make sure I have my laptop with me until its added back. I will post over in the kernel thread just to see what the deal was but wanted to post here to confirm its not working. Otherwise, zero issues so far and faster.
[Captivate Android Development] keitaroguy:
stupid question...does sgsII have something we don't that will allows us to pan our widgets?
[Captivate Android Development] A.VOID:
Is ext4 enabled by default? I don't see a CWM option to convert it.
[Captivate Android Development] minotaur507:
There is no CWM option. It's now an ext4 application in the drawer.
[Captivate Android Development] climber1872000:
Yes. If you didn't convert back to rfs before flashing then out will be enabled after flashing new version.

Or maybe not. I just assumed.
[Captivate Android Development] Jep56:
I removed my external card.

Factory reset from recovery

rebooted.

wait for media scanning to be done

shut off

re-inserted external card.

rebooted

wait for media scan to complete.

ran Tit BU (missing apps and data...Not system data)

GPS right on

Compass good

super fast and smooth

No troubles after 3 hours

icezar1...Excellent job once again
[Captivate Android Development] loraque:
This only happens when I use LauncherPro, which of course is what I use. Started in 5.3 and it does it 5.4 too. Reinstalled, cleared data, etc. It does not crash with TW.
[Captivate Android Development] p1gnone:
I wanted to go back from Continuum with its GB bootloaders to JF6. Using Odin3 v1.0 I did this flash back to "stock". But on boot the first screen is the black GT-I9000 screen.

I need this so that I can go back and carrier unlock. So really "back" is what I need so to use the SGS tools.

Does the black initial boot screen come from the GB bootloaders? How to fully get back?
[Captivate Android Development] kuherrm:
would this port of the SGS 2 lockscreen work for continuum since its JVH? http://xdaforums.com/showthread.php?t=1070564&page=2
[Captivate Android Development] devadvance:
Anyone else having the issue of orientation data not being saved to photos?

Right now, if a picture is taken holding the phone vertical, the image is saved sideways. This is the same as before, but it used to be that when viewed in Galley 3D or similar applications, the app would read the orientation and display the image properly.
[Captivate Android Development] Holmes108:
It started happening to me off a clean install of 5.4 (no LP installed yet). Was using the Sony launcher at that point. Then it started on Launcher Pro.

It's a minor issue though, since it straightens itself out shortly after boot.... good enough to get me to the next version.
[Captivate Android Development] rockosifraldi:
Odin 1 click, I think the link is there in the OP... if you are still on GB loaders...use the corresponding method to go to download... rest 1 click Odin would do the job.. bee there and done that ... scary but I passed :D
[Captivate Android Development] A.VOID:
It does not convert. I was on RFS before, and I'm still on RFS.
[Captivate Android Development] dizx:
I'm trying to stay locked onto 1ghz max, but when checking system info in quadrant, sometimes it's showing 1.3 ghz.

EDIT: Issue seems to have gone away after converting to ext4. Now able to set ceiling at 1ghz.

EDIT 2: It seems I spoke too soon. Still getting 1.3ghz even when saving as boot settings and rebooting. However, not worried. I know that Cezar will post an update soon. :)
[Captivate Android Development] gio22:
Go into the App Drawer and run the Ext4 app. You can convert there.
[Captivate Android Development] Cezar`:
We are working on fixing the kernel. Most of the issues were sorted out.

Give us few more minutes.
[Captivate Android Development] Holmes108:
Was never worried. You guys are the best.
[Captivate Android Development] whiteguypl:
FTL drive activated? Am i to assume you have stolen technology from destiny?
[Captivate Android Development] gocats7:
What issues are there if I may ask? The only thing I know of is TUN and seriously this thing is solid for me so far.
[Captivate Android Development] sstarre:
+100

SOLID here too :-)
[Captivate Android Development] nelsonw:
Did you saw the Vol+ issue? Enters into a sort of USB Download... weird never see thar screen...
[Captivate Android Development] IamSonoma:
Can we recharge with the sun? :)
[Captivate Android Development] chibixzero:
Lol I was going to say the same. Hes from the lucien alliance mang
[Captivate Android Development] agarp:
using v5.4 and TW4 is causing random restarts. Other than that its perfect, no lag like before.
[Captivate Android Development] breakthru_sep:
I've no issues at all since installing 5.4, everything has been smoother than smooth! And it's incredibly gast at 1ghz too.

Still I was wondering if anybody was using their Cappy fully stable at 1.3 ghz or more and with what UV settings. I know every CPU would react differently but still I'm curious :)

Great work as usual Cezar!!
[Captivate Android Development] bleeman:
Kernel is good

I am not having vol button issues, usb plug rebooting issues or any of the other reported issues except for when I set the cpu for 1200 and after rebooting and running for a while, cpu spy shows me running at 1300, not a problem for me at all, performance is excellent with minimal battery drain so far, I am UV'ing at -25 for all speeds 800 and below. When I flashed, I ran the factory reset first, then flashed, rebooted, unchecked the RAM Min-free box and have been very happy with this ROM/Kernel combo
[Captivate Android Development] smackdownn:
1.2 is the max i can get without reboots/freezes/crashes.!! before in 2.2 i tried 1.3 and 1.4 also..there were no issues.

anywayz great work team :)

and hey what if a FTL drive?
[Captivate Android Development] sstarre:
Running @ 1.3 / uv @ -50 for 100 thru 1000. It's been stable with no problems since 7 Am EST. About 7 hrs...nice !

BTW .. factory reset and flash per OP
[Captivate Android Development] nelsonw:
even in recovery mode, pressing VOL+ HW key enter this mode...
[Captivate Android Development] richsale:
Flashed 5.4 over 5.3 and have NO negative issues. I did not change anything. I'm running GoLauncher. Another great rom from cezar.
[Captivate Android Development] existz:
I had to revert the 1.3ghz and up to 1.5ghz, something in the code was causing it to restart with usb and causing tw to reboot ...so the next version will only be up to 1.2ghz.. Also set different preset values for lmk...if the min free tweak in tweaks app is enabled it will set kodos96 settings, use this if you want to have more apps stored in memory..if its disabled it will set stock jvb style settings (as close to jvb as possible without introducing samsung bug,..) disable the tweak if you want the most optimal speed settings, it doesn't allow as many apps to be stored in memory (compared to tweak enabled).. also disabled printk, should help some with battery life

Ill work on adding higher oc back, but I have to get it stable first .. icezar should have an update soon..also trying to fix cifs/tun support ..im getting there, just give me some time
[Captivate Android Development] gocats7:
no worries, thanks for all your work.
[Captivate Android Development] gio22:
You and Cezar are the best!! Thanks for all of your hard work!!
[Captivate Android Development] minotaur507:
Yes, thank you very much existz!
[Captivate Android Development] A.VOID:
Well, i found out Android ID changer is not a good plan.:(

Stuck on Continuum load after flashing it.
[Captivate Android Development] Time_Zone:
FTL Drive

Clearly he is referencing BSG.

I can't believe there are actually more than 2 people who watch "Stargate: dreary and boring"

I kid of course.
[Captivate Android Development] dizx:
Which Busybox version did you load? Usually, reverting back to 1.17 works well. Note: I haven't tried it yet.
[Captivate Android Development] A.VOID:
I know that worked before, but that was when AndroidID changer would throw an error on 1.18. This rom is on 1.19 and no error thrown in Android ID. So I went and ran it and went it infinite loop.
[Captivate Android Development] sstarre:
Found the same thing. I thought I would change the ID to what I had saved when on Froyo, and after flashing my first GB (Continuum 5.1) it completely hosed the system.. hello re-flash ! - never tried it again...:rolleyes:
[Captivate Android Development] whiteguypl:
haha yeah right sgu is actually a pretty good show, sga could definitely us your title though. ;)
[Captivate Android Development] neonlazer:
Never tried to play with it and I just flashed twice and both times it hanged in the middle of the continuum screen then before it even got to that screen..then shuts off.
[Captivate Android Development] djfrost40:
I hope I don't get cursed out for asking this but, here it goes...does anyone know of the thems created for v5.3 will work with v5.4?
[Captivate Android Development] dizx:
Damn, sorry to hear that. At least you didn't perma-brick!
[Captivate Android Development] mcx6:
No they do not, base of the rom has changed, the themes will need to be updated.
[Captivate Android Development] p1gnone:
Hv been back to JF6 twice via ODIN of JF6_secure.tar.md5 and the full ODIN3 v1.0: I897UCJF6-final-OCD-REV0.exe AS ADVISED in the OP.

Either way I get the initial black screen with "GT - I9000" not the original/stock I897. SGS Unlock [paid], and a generate_code.bat both fail. [with root] Neither seem to get proper access to the nv_data.bin file.

SO I assumed the initial black screens indicate GB bootloader files are in use. and that this was my problem..
[Captivate Android Development] gio22:
They don't.
[Captivate Android Development] topiratiko:
Negative. Bootloops. First hand exp. Themes need porting
[Captivate Android Development] djfrost40:
nice, thanks for the warning...lol appreciate it:)
[Captivate Android Development] djfrost40:
I really love the feeds and updates but wish there was a way to change to color instead of pink...lol,
[Captivate Android Development] p1gnone:
Fine, but what vestige of the Continuum ROM causes the initial black boot screen to show GT-I9000 when in the original JF6 it showed I897? And what impedes access to the original nv_data.bin?
[Captivate Android Development] topiratiko:
+9879989864
[Captivate Android Development] jcr81:
0.1.7 is running flawlessly at 1.5ghz for me. I'm using Launcher pro though so not sure how TW or any other launchers would behave. I disabled Min free and VM: swappiness No usb charging issues, no lag...just perfect. This may have ended my flashing addiction!
[Captivate Android Development] gio22:
I'm sorry, my last post that you quoted was supposed to be the person who asked if 5.3 themes worked on 5.4. I did the post on my phone and the quote didn't copy in correctly.

I'm sorry for any confusion. To your issue, I used DesignGears Odin 1-click to go back to stock with the AT&T bootloader screen awhile back. Don't know if you have tried that or not.
[Captivate Android Development] xtsuname:
Does anyone else experience complete freeze when plugging the phone into USB?
[Captivate Android Development] mcx6:
It is a known issue, just read a few pages back and it is being worked on. looks to be a kernel issue.
[Captivate Android Development] xtsuname:
Ok I thought so. Am travelling so my connection is going on and off and looking through the log using the xda apparently is not that fun.

Thanx. Hope they fixed it soon.
[Captivate Android Development] dizx:
I tried to flash a UOT zip, but it didn't do anything. Can someone verify what boxes are supposed to be (un)checked in the Kitchen?

I had Edify, Patch9 autofix, and Theme Chooser Preview checked off, and uploaded up the framework-res.apk and SystemUI.apk
[Captivate Android Development] existz:
Most of the kernel issues reported, ive fixed.. (usb causing reboot, touchwiz causing lockup/reboot, cifs/tun..etc..) The updated kernel will be in icezars next release, should be soon, i know hes working on it.. But just to let you all know, most of the issues reported have been fixed, so hang tight..it will come soon
[Captivate Android Development] soul4rent:
in case no one has answered you yet or someone else has the problem

there are a few things you can do to get past the usb bug

1. reboot to recovery go to mounts and storage/mount usb storage. that will allow you to use your computer to copy another flashable file to sd

2. use odin to flash the 0.1.6. jvh kernel which doesn't have the bug

3 download the kernel or a different rom directly to the phone(over wifi if you don't have unlimited data)and flash it from the cwm app

btw wall chargers don't trigger the bug if you battery is low
[Captivate Android Development] djfrost40:
yep and the phone completley restarted itself
[Captivate Android Development] gio22:
You're the MAN!!
[Captivate Android Development] Holmes108:
Same thing happened to me when I tried changing the boot animation and battery symbol.

I opened the zip, and manually replaced the files and it worked (this was on 5.3)
[Captivate Android Development] streetsmart999:
Same Thing as above.. When I plug in.. Phone shuts down. + if I'm moving the screens fast the phone freezes. Need to remove battery and re-start. Before and after Flashing I did Factory Reset/ Cache/Dalvic.

Thanks for the development effort.
[Captivate Android Development] existz:
Read just 4-5 post back...i have fixed most of the issues with the kernel, an updated kernel will be in icezars next release..
[Captivate Android Development] olo567:
Great. I've been on GR-X, but am itching to try out JVH and see a lot of positive comments over here! Phone's charging at work and will try this out tonight hopefully!
[Captivate Android Development] dizx:
Ah yes, manually. All this flashing stuff gets me lazy. Diving into Root Exporer now and holding breath. If you don't hear from me, call the cops.

EDIT: I'm back! Manually taking the files and copy/paste into the relevant folders and then reboot. Bingo!
[Captivate Android Development] dc5ftw:
I had the same problem. I even tried manually mount /system and /data in cwm and it still didnt change anything. for right now, i would just wait.
[Captivate Android Development] keitht:
This has been an issue for me as well so I changed my habit. I download the ROM I want to flash then take out the Framework-res.apk and SystemUI.apk before I flash and upload to UOT kitchen. Download the package from UOT when ready, then replace those same 2 files in the ROM before flashing. Repeat this every time a new ROM is released as these same files may be updated in each ROM release. You can also manually replace them if you already flashed the ROM and reboot but I like to have them in the ROM ZIP in case I need to reflash the same in the future.
[Captivate Android Development] A.VOID:
Getting low memory errors.

UGH!

Says low internal memory, but i have 6.5 gb avail. Unless it means the 2gb mem which I show has 200 mb avail.
[Captivate Android Development] Holmes108:
If I remember, bootanimation had to be renamed sanim.zip. The framework and systemUI files I just returned them where I got them.
[Captivate Android Development] neonlazer:
device OS memory is separate from storage memory. should have like 200-300mb I think.
[Captivate Android Development] stuff:
Touch keys don't light up when I am touching the screen. Is this normal?

My apologies if it's been noted. I checked the bug tracker and saw no such listing so I am wondering if it's just me or not.
[Captivate Android Development] dcarter:
...yes.....thank you......hindsight 20/20.....

The browser works with so many more sites, that alone makes it worth it...

plus one can set landscape default for the browser alone...

All good stuff

dcarter
[Captivate Android Development] Uncle Irish:
Did you install the C5 ROM with or without bootloaders?
[Captivate Android Development] Dieabolical:
I installed the Crysis Sensation Theme over in the I9000 forum and it works just fine.
[Captivate Android Development] doctahjeph:
Me too. So awesome!
[Captivate Android Development] Cezar`:
Lets make something clear guys. You will HAVE TO flash bootloaders once att's gingerbread will come out. What then?

I did it, I took the risk several times just to be able to ensure that it is usable and safe enough for you. And I have no warranty!!!!!!!!!!!

OK?

This is by far the most stable gingerbread for captivate and I wanted to share it with everyone.

If you don't want to risk it, then DONT!

I am sorry for those that bricked their phone. I will gather details about the pattern and I will try to make things less risky.
[Captivate Android Development] Vivified:
it's probably a RTFM issue...
[Captivate Android Development] harpo1:
Cezar most of us know the risks as well and are willing to take them. We appreciate all you devs do so don't sweat the small stuff. Bricks are going to happen and people need to understand this. If they don't want a paper weight they need to stay away from flashing.
[Captivate Android Development] whiteguypl:
No reason for you to apologize for something that is not your fault.
[Captivate Android Development] Dieabolical:
One thing I have noticed about this ROM is that flipping through the different home screen pages is stupid fast while using the TWiz launcher. No other ROM, including custom Froyo ones, was able to do this with such smoothness. Battery life is great so far, and it will only get better as this ROM matures.
[Captivate Android Development] shoman94:
mattedBlues port coming very soon....will be beta and will change things as Cezar does. Like the dialer for example. I'm not gonna edit my dialer because he will be getting rid of the videocall button soon I'm sure.
[Captivate Android Development] nakedninja42:
I had absolutely no problems today flashing. I had stock JVB on my phone with xcal kernel for couple days and this morning flashed back to stock 2.1 and did a master clear, then went through the process and flashed Continuum 5. the only issue I have is my About Phone keeps force closing, I did a factory reset twice and still FC. Any one resolve this, I did a search and saw a logcat posted but no follow up. Should I reflash again?
[Captivate Android Development] RichMD:
Summarizing the risks

Thanks Cezar. Please correct me if any of this is wrong. I haven't tried it yet - I'm waiting to see how it goes but I am hoping it will be more solid next weekend.

There are always risks of a hard brick such as

1) Any time you flash a package with boot loaders over USB (such as eclair JF6 via ODIN, etc) - A break in the USB connection at the wrong time (when updating at least one file that takes a couple of seconds) will hard brick the phone.:eek:

2) Cezar created a "stock" eclair flash without updating the boot-loader (at least) that avoids this small but real risk. A search should find this if you want it. I have not seen anyone else create an equivalent and appreciate the effort on this.:D

3) As Cezar pointed out above, if you ever want to go to an AT&T (and I assume any other "ported" official Gingerbread), you will have to update the boot-loaders. That raises the risk but that is out of Cezar's or anyone else's control. CM7 or MUI apparently don't update the boot-loaders but development is a ground-up approach that takes a long time and may never have some of the same functionality. I'm guessing on this so feel free to correct.

4) Additionally, the problem people have had is when they try to revert to eclair boot-loaders after updating to a GB boot-loader. This is not a well understood process and the pattern of when it causes a hard brick MAY be related to a specific hardware build, etc. From what I've read this appears to be related only to the bootloaders and not Cezar's ROM in any way. There was one person that got a hard-brick when doing a CWM flash (no boot-loaders) but for now that seems to be an isolated incident.

5) If you do update to the GB boot-loaders, it appears they are backward-compatible to allow you to flash to a previous FROYO ROM and "probably" even the stock package that Cezar created without boot-loaders - not sure on this. It has been pointed out you won't have the regular AT&T boot image, etc.

6) Additionally, this was listed as BETA - that should clearly indicate that you are taking increasing risk.

7) You can soft-brick a phone many more ways but a JIG or other methods can easily resolve that.
[Captivate Android Development] keredini:
Same here, a great theme for a great ROM.
[Captivate Android Development] harpo1:
Just read someone who installed stock gingerbread bricked their phone going back to stock 2.1. He used the Odin with 3 button fix. I believe someone else in this thread reported bricking their phone using the same procedure. I've read several people using Odin 1-click not having any issues going back to stock so the problem my lie with using the Odin with 3 button fix. Just throwing this out there for thoughts.
[Captivate Android Development] keredini:
Has anyone tried to get the recently-leaked Music player to work on this. Normally when I install that it replaces the stock Music player. On this build it installs but leaves the stock player, and trying to use the newer Music player generates a FC.

Other than that i have no issues currently...
[Captivate Android Development] NeonMonkey:
Ya fortunately When I first booted it had debugging mode on so I was able to reboot to download mode from AIO toolbox.
[Captivate Android Development] climber1872000:
That's exactly what I am beging to think. We won't know for sure until evryone who bricked their phone confirms that they all used the Odin with the 3 button fix. I have flashed back to stock a few times since first installing this beta release and have had zero problems. I didn't use the Odin with the 3 button fix.
[Captivate Android Development] mrhaley30705:
No. but I would not recommend skipping it. I had already installed the kernel and flashed a GB rom. except for that, I followed cezars instructions, adding a Dalvik cache clear.

the only problem I've experienced is from some apps that I restored. Had to uninstall and reinstall from market.