yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
There seems to be a permissions issue in the roms installer script that's effecting the way Talons initramfs works with bluetooth, so it seems its not Talons fault..Cezar found the issue that's effecting it with Talon and said he has it fixed, also Watsaa said he will have an update that fixes this.. So the permissions problem is only effecting Talon and Chainfires kernel (we use a modded version of Chainfires initramfs) We have used a voodoo based initramfs and the problem is not there, so its def in the way the initramfs is getting executed on boot, not the kernel itself.. So with a bug in the roms installers permissions script, it can very well cause these problems.
[Captivate Android Development] F1reEng1neRed:
Lol, with laserbeams attached to their heads?
[Captivate Android Development] F1reEng1neRed:
No problem existz, the fix is in the works. Between you and the other awesome devs here, stuff doesn't stay broke for long.
[Captivate Android Development] froli13:
Yeah, baby, yeah!
[Captivate Android Development] existz:
Lol yea we try... This one took awhile to figure out, we even went as far as building a new initramfs based off of voodoo since the problem only happened with using Chainfires initramfs, we even diff'ed the differences in ours and other initramfs and found nothing that was out of place, plus we havent messed with any thing BT related that would cause the issue, but next version of Talon should include some BT power saving features from Zachs kernel..so a permissions issue in the installer script does make sense.. but it only effects Chainfires initramfs (or any kernel using his initramfs)... but luckly Cezar figured it out..and hopefully this fixes it for everyone

But as far as the wifi reboot issue, that seems to be a Samsung bug...numerous amounts of us have verified it does happen with stock rom and stock kernel, some kernels are easier to trigger than others, but it does happen with every kernel (darkcore, xcals, chainfires, even stock kernel)...
[Captivate Android Development] F1reEng1neRed:
Wow, sounds like trying to find a needle in a haystack. I'm not a big user of BT myself, but it will be great to know it works if I need it. You guys rock!
[Captivate Android Development] IpwnHLmath:
Dark Core 2.7

Hey guys.. I am having trouble with my Wifi so i decided to flash dark core 2.7 but I am unable to find that anywhere.. Can you guys direct me to the place where i could find it?? thanks!
[Captivate Android Development] F1reEng1neRed:
From what I've read, DARK CORE 2.7.3 hasn't been officially released yet. It's included in Dagr8's SYMPLY ROM, but that's it for now I believe.

All I can tell you is google is your friend. Make sure you use the one for the Cappy though. And as with everything else, you use at your own risk, although you shouldn't have any problems.

Edit: I don't think DK kernel will help your Wifi. It fixes BT, but not Wifi. What is your Wifi issue?
[Captivate Android Development] watsa:
anybody on Talon with BT problem raise ur hands :D
[Captivate Android Development] JustinUhhh:
-raises hand-? Hahaha. I don't use it though. I was just testing stuff and noticed. :cool:
[Captivate Android Development] watsa:
Check ur PM
[Captivate Android Development] F1reEng1neRed:
Watsaa,

"Raises hand!" I did switch to DK kernel and that fixed it. I know you said you had a fix in the works, so if you need a tester, I'm down!
[Captivate Android Development] leoriver42:
Experience with Dark Core wasn't great. It drained lots of battery on standby and ended up with a sleep death. Back to Talon, I'd rather have the bluetooth problem.
[Captivate Android Development] watsa:
PMed u 10 char
[Captivate Android Development] airtower:
My BT works, as in it connects to devices, but actually getting A2DP working is intermittent.

Sent from my Samsung Captivate with ApeX 7
[Captivate Android Development] watsa:
check ur PM.

Matted blues by froli13 should be up soon.

but i guess u r waiting for AOSP???
[Captivate Android Development] froli13:
Soon? It's already up :cool:

Changelog:

http://xdaforums.com/showthread.php?p=13204006
[Captivate Android Development] jlsesler:
Where can I find the standalone talon 2.2 kernel?
[Captivate Android Development] F1reEng1neRed:
Find a post from existz and look at his sig. Go to his chat channel and ask him. He doesn't want his test builds out running rampant.
[Captivate Android Development] justmart:
FYI Xcal's kernel is OUT! for JVP roms!!

Sent from a PRican Captivate.
[Captivate Android Development] F1reEng1neRed:
Yes, it is. Please post feedback for the kernel in excals thread, not here. Remember, the BT issue is said to be ROM, related, not kernel, so if your BT still doesn't work, keep that in mind. Watsaa has provided me a possible fix, but I haven't been able to try it out yet since I'm at work (on Hawaii time).
[Captivate Android Development] froli13:
Open ApeX 7.zip in your favorite archive manager, navigate to the updates folder and extract the file named zImage and flash it with Odin/Heimdall
[Captivate Android Development] torred:
just to clarify

If I use BT all the time I should wait for a update ?

I'm on 6.4.1 right now.
[Captivate Android Development] watsa:
there is one coming in about 15 mins
[Captivate Android Development] torred:
Thank you.

Phone is charged and backed up.

:)
[Captivate Android Development] froli13:
Just letting you know guys that the hacked browser is already included in MattedBlues, and themed. So you won't lose it if you flash the theme over the update.
[Captivate Android Development] RockRatt:
After installing the 7.1 no wipe should it still say version 7.0 in About Phone? Just trying to make sure it actually updated. I know it is a simple change in the build prop but just wanted confirm it. Thanks

Sent from My 2.3.3 or 2.3.4 Captivate Test Phone depending on what Gingergurl I am testing.
[Captivate Android Development] harpo1:
Just to clarify xcals JVP kernel is cwm3 correct? Also it may be a good idea to have people wipe voltage settings in recovery if they've done any oc/uv.
[Captivate Android Development] F1reEng1neRed:
If you're on Xcal's kernel now instead of the Talon that came with it, I would say it took.

Edit: Mine now says Apex 7-Update 1
[Captivate Android Development] dizx:
You should be surfing, not flashing. Lol. Which island?
[Captivate Android Development] watsa:
It should say 7-update-1. it doesnt?
[Captivate Android Development] torred:
So going from 6.4.1 I have to do 7 then go to 7.1 ?
[Captivate Android Development] vamshi999:
I have installed the non wipe version... i was on 6.5...... i updated to 2.3.4..but there is no change in the phone.. like the unlock screens are the same.. is it same for everyone ?
[Captivate Android Development] harpo1:
That is correct.
[Captivate Android Development] RockRatt:
No it says Apex Version 7.0 also I did not change the kernel from the talon kernel since the original 7.0 rom.

Sent from My 2.3.3 or 2.3.4 Captivate Test Phone depending on what Gingergurl I am testing.
[Captivate Android Development] watsa:
There is a wipe version called as 7 between 6.5 and the new non wipe lol
[Captivate Android Development] froli13:
Do it if you plan to flash talon in future (I mean, if you plan to flash talon before you completely wipe the phone) . But xcal's kernel won't use your OC/UV settings
[Captivate Android Development] froli13:
Yes you need to flash 7. And it is not 7.1 it is 7-update 1 ;)
[Captivate Android Development] harpo1:
I'm flashing right back to talon. Is xcals JVP kernel cwm3? I know they have been CWM2.5 in the past.
[Captivate Android Development] watsa:
yep its CWM3
[Captivate Android Development] F1reEng1neRed:
Watsaa, yes, mine says 7-update 1.

I thought it was a little wierd...I cleared cache and Dalvik flashed and rebooted and it started up. Got to the Android letters and then screen went dark again. I though something was messed up. I was getting ready to hit power again because it seemed like the phone was off, but I let it sit for a few minutes and all the sudden my home screen pops up. Good to go.
[Captivate Android Development] watsa:
buddy u have missed something somewhere. its working fine
[Captivate Android Development] pwnerman:
If im on Serendipity 7 should I flash back to 2.1 then follow the instructions for this rom or can i just flash it over Serendipity? im on the serendipity kernel if that matters
[Captivate Android Development] watsa:
If you are on CWM2 flash ApeX, then flash ApeX again. or just flash Talon' kernel before flashing ApeX
[Captivate Android Development] watsa:
I m guessing it took sometime to rebuild the cache again. expected
[Captivate Android Development] F1reEng1neRed:
answered already
[Captivate Android Development] F1reEng1neRed:
Yeah, I'm sure that's what it was doing, but normally, the boot animation would remain on during the process. This time, it had me thinking the phone had shutoff.

If anyone else is experiencing this, your phone didn't shutoff...just let it sit for a few minutes and your home screen should come on.
[Captivate Android Development] rogersa2k:
Stuck at boot logo

I just updated my phone from 7 to 7 Update 1 and my phone just hangs at the Samsung boot logo. I can get into Download mode so I was able to flash TalonDEV 2.1 to get into Recovery mode and try again but same thing. I can hear the lady talking in the background but after 10 minutes it's still on the boot logo.

I applied the zImage from ApeX 7 and I'm happy for now.

- Aaron
[Captivate Android Development] dizx:
I show reorient kernel loaded, but still shows as Apex 7.0...?

I too had a short moment of black screen panic, but reboot went fine. Lol.
[Captivate Android Development] F1reEng1neRed:
Under about phone it doesn't say Apex Version 7-Update-1?
[Captivate Android Development] F1reEng1neRed:
Are you running on ext4?
[Captivate Android Development] RockRatt:
I had to go back out to recovery, clear cache and dalcich cache, then ran the update again. This time it started going again but went to black screen and didn't come up after about 10 minutes. So I held down the volume up and power and got into recovery. Then flashed the update again and now it does show Apex Version 7 Update 1. Thanks for the confirmation earlier. Just wanted to be sure. I knew it took this time since I had to reset my widgets.

Sent from My 2.3.3 or 2.3.4 Captivate Test Phone depending on what Gingergurl I am testing.
[Captivate Android Development] F1reEng1neRed:
LOL, I'm on Oahu.
[Captivate Android Development] dizx:
Nope. See attached.
[Captivate Android Development] F1reEng1neRed:
Wow, that's really weird. Have you tried clearing cache partition and Dalvik and reflashing the update?
[Captivate Android Development] froli13:
When it happens I just touch one of the capacitive buttons to know if the phone is on.
[Captivate Android Development] froli13:
Did you flashed using the CWM app or in recovery?
[Captivate Android Development] F1reEng1neRed:
I tried that, but for whatever reason, my phone just seemed dead. I seriously thought it was off. The first time, it happened I held up and power and rebooted into recovery. I wiped cache part. and Dalvik and rebooted again. That time I just let it sit for awhile and it eventually came up by its own. Scared me at first.
[Captivate Android Development] vamshi999:
why are the graphics are terrible for launcher..on twlauncher they are little better ... not able to see the apps properly at all.. are there any settings which we are supposed to change?
[Captivate Android Development] F1reEng1neRed:
When? What did you just do?
[Captivate Android Development] harpo1:
Can I take the modem out of the update? If so what files in addition to the zimage? I don't feel like converting back to RFS before flashing the update then converting back when I flash talon again.
[Captivate Android Development] watsa:
Sorry there was a problem with script. Fixed now
[Captivate Android Development] froli13:
You don't need to convert again
[Captivate Android Development] watsa:
why not just push the apks from /system/app instead of flashing?
[Captivate Android Development] harpo1:
I do if I want to be on ext4.
[Captivate Android Development] harpo1:
Yeah I just check the zip and that's what I'm doing. Thanks again.
[Captivate Android Development] vamshi999:
yea i just flashed 1/2 hr back..
[Captivate Android Development] froli13:
I was on ext4, flashed the update and I'm still on ext4
[Captivate Android Development] vamshi999:
i got this error when i opened the ext4 manager.. "A CF-Root kernel was not detected. ext4 Manager may not function properly"
[Captivate Android Development] watsa:
yea those apps wont work with XCal, get rid of them using TiBU.. they work only on Talon kernel
[Captivate Android Development] mopo01:
Watsaa you say in the op that sms is not in the call logs. Since I don't have bt issues, do not need to change kernel, mine is working fine. the camera hack I don't "need" which files do I need to fix the call logs. Logs provider? Could you post the file or make a flashable fix :D
[Captivate Android Development] pwnerman:
Is it normal for the date on the pull down bar to be 14/06/2011 lol
[Captivate Android Development] watsa:
until u change date format from settings :p
[Captivate Android Development] pwnerman:
i am an idiot lol
[Captivate Android Development] vamshi999:
can you please elaborate.. don't know what TiBU is.. and what about the graphics in the launcher.. tw is ok...
[Captivate Android Development] harpo1:
Anyone getting the extended power menu when taking a picture?

Edit: Never mind pressing the button too long.
[Captivate Android Development] F1reEng1neRed:
I am if I hold down the button. Just quickly push it and the camera should focus and take the picture without the power menu coming up.
[Captivate Android Development] pwnerman:
you can get rid of all those apps (CWM, ext4, and Tweaks) they arent really needed
[Captivate Android Development] F1reEng1neRed:
Watsaa,

This is probably a dumb question, but is the IM app supposed to do anything? When I open it, it just says connecting and never does anything.
[Captivate Android Development] dizx:
Reflashed and NOW it shows! :D

I feel better now. LOL.
[Captivate Android Development] leoriver42:
Ok updated and BT issue fixed but this kernel doesn't support UV either, will there be any difference in terms of battery life from Talon? Tried with Dark Core before and it wasn't that good I fear.
[Captivate Android Development] pwnerman:
Ive been doing this forever but Ive never really asked if it was safe or not. Well I'll just get straight to the point. After you flash your rom of choice is it ok to go through with a program like titanium backup and delete all the apps that you dont want including system apps?
[Captivate Android Development] harpo1:
Xcal's kernel only came out today so battery life won't be know for a couple days. However with that said his kernels usually do really well in terms of battery life.
[Captivate Android Development] F1reEng1neRed:
I flashed to DARK CORE once I found out that BT didn't work on Talon, and I honestly couldn't tell a difference in battery. I don't OC/UV at all, but I was going a good 12 hours and dropping to around 65-70. The difference between the 2 was negligible. I don't expect any different from excal's.
[Captivate Android Development] watsa:
that depends on which app u r deleting. e.g. deleting email can cause camera to fail.
[Captivate Android Development] pwnerman:
why would deleting email mess up the camera lol
[Captivate Android Development] watsa:
it uses a lib from email
[Captivate Android Development] watsa:
Titanium backup.. what graphics?
[Captivate Android Development] chibixzero:
I have a question about this rom we all know a rom has to have appeal quickness and all but what about video do these roms have all the video codecs that the original captivate rom have?

If you answer yes do the files say high definition videos playable to where there's no lag on the. Video
[Captivate Android Development] pwnerman:
Signature Pics

Are there any Signature Pics for this rom? sorry if this has been asked
[Captivate Android Development] pwnerman:
Pattern Lockscreen

Has anyone thats flashed that mattedblues theme for this rom had issues with the pattern lockscreen not being centered and weird. or is that with the stock rom?
[Captivate Android Development] dizx:
You are in good hands with Xcal's stuff.
[Captivate Android Development] froli13:
I'll test it

Edit: confirmed for Mattedblues, I'll try to fix this soon. Thanks for reporting this issue.
[Captivate Android Development] froli13:
Never mind delete this...
[Captivate Android Development] juxtyce:
I am experiencing the same thing. Looks like it would be a nice app as it ties into the social feeds. Any suggestions on getting this working?

Thanks
[Captivate Android Development] watsa:
looking into that
[Captivate Android Development] juxtyce:
Thanks! You rock!
[Captivate Android Development] eep2378:
Flashing apex fixed sd card apps dissapearing on reboot. Watsaa, great work!
[Captivate Android Development] vamshi999:
This is the problem i am facing.. don't mind the color.. must the screenshot app... u can see the difference in both..
[Captivate Android Development] watsa:
maybe i am blind buddy, i cant see the screenies. dont use ur gmail account in the link
[Captivate Android Development] vamshi999:
sorry.. edited the post..
[Captivate Android Development] watsa:
If u using screenshot app, check the box to invert color and then take a screenie.. that will give u true color
[Captivate Android Development] vamshi999:
Done .. uploaded the new screenshots.. now.. do you see the difference in both the launchers... one is neat and other is kinda blurry..
[Captivate Android Development] watsa:
u mean the GB launcher has problem? try and download one from market and see if that solves the problem for u
[Captivate Android Development] mopo01:
sorry for reposting but this thread is moving so fast I figured you must have missed it since you normally respond in some form. O:-)
[Captivate Android Development] watsa:
Sorry to miss that out buddy :(

You would only need logsprovider.apk. Cant make the flashable zip now in office. will do it by today evening?
[Captivate Android Development] xpakage:
Kernel Change

If I wanted to flash Xcal's from a clean install, could I just place that ZImage in the update folder of the ROM, remove EXT4 and Tweaks apk (not sure of names yet) from apps folder, repack with Winrar and flash?
[Captivate Android Development] watsa:
yep just replace the zimage.. as for those apps just delete them from TiBU
[Captivate Android Development] mopo01:
Will try pushing the apk will let you know if I have an issue and need a fix Thanks, will hit the thanks button when at a computer. :-D
[Captivate Android Development] djinferno806:
i also saw that problem when i first flashed... the default gb launcher seems to have a low resolution app drawer which is inferior to other launchers. i just used lpp and now its all good again.... never saw that problem with gb launcher before though... strange.
[Captivate Android Development] watsa:
yea thats very strange. same launcher was used in previous versions of apex.
[Captivate Android Development] vamshi999:
Hi...gb launcher had low resolution ..but the tw laucher was good.. after using lpp did you any new theme or the same gb launcher..
[Captivate Android Development] keredini:
Just as an FYI. It is strange, both times when i flashed (the initial wipe package and then update 1) i had to flash the update twice.

Followed the instructions in the OP, flashed to stock, did a master clear, flashed the GB bootloaders, flashed the kernel, and then the Apex 7 package. First time after flash I boot looped for about 20 minutes. So I went back into recovery and flashed the Apex 7 package again. After that everything was fine.

Same thing when going to update 1. I flashed the update package, and when my phone rebooted I heard the sweet sounds of that familiar robot :D But when i booted up the version in the About Phone section hadn't changed. So I went back into recovery, wiped cache and dalvik-cache, and applied the update package again. After that, all is working as expected.
[Captivate Android Development] rogersa2k:
Issues with 7 Update 1

Okay, I re-downloaded the 7 Update 1 zip this morning and tried to install it again. I went in to Recovery mode, chose to install zip, selected it, and after about 15-30 seconds my phone rebooted (seems odd). It then showed the Samsung screen for a few minutes and I could hear the voice in the background occasionally. After a while it finally booted up. When I go to About phone it still says Apex version 7.0. Under Kernel version I see reorient_G #21.

I installed 7.0 from scratch yesterday and didn't do anything to the file system or kernel. Thoughts?

Edit: I just noticed the previous post. I went into Recovery mode, cleared Dalvik cache, and applied the update again. This time it did not reboot on its own. My phone is booting up; fingers crossed.

- Aaron
[Captivate Android Development] keredini:
I had to flash the initial package twice and the update package twice before it worked. May want to try flashing again. See my previous post for more info.
[Captivate Android Development] rogersa2k:
Yep. I saw your post almost as soon as added mine. I flashed a second time and now it looks good. Thanks!

- Aaron
[Captivate Android Development] watsa:
There was a problem with the script yesterday, i had to change it. should work now
[Captivate Android Development] tbong777:
WOW

First GB ROM I tried without initial issues. Everything just works. JD Powers initial quality = 100%...

Great idea to use the Xcal Kernel. My phone loves plain jane kernels that just do the job.

Very nice. Donation coming your way...$20 Confirmation number Confirmation number: 6GW75462YG6836156
[Captivate Android Development] Vivified:
My phone loves being pushed to the limit
[Captivate Android Development] rogersa2k:
Well, I downloaded the zip file again this morning. Are you sure you re-uploaded it?

- Aaron
[Captivate Android Development] watsa:
Yep, and dont know what problem u were having, but script was not properly handling app extraction to system partition.

and all is well now, aint it?
[Captivate Android Development] rogersa2k:
Yes, running it a second time took care of it. Loving this rom! :)

- Aaron
[Captivate Android Development] justmart:
That is your opinion?! Right?! LOL
[Captivate Android Development] Vivified:
It sure is. What's yours?
[Captivate Android Development] mopo01:
actually I am having a wifi issue. while it turns on off and connects it just will not actually connect to the web??? :confused::( searched the threads cannot find any help
[Captivate Android Development] dizx:
But isn't that the general reason why we reside in these forums as well as the risk we take to flash these development ROMs? ;)

In order to make our phones better, we must push the limits.

Unfortunately, my phone doesn't OC/UV very well, but I can certainly push it in other ways. ;)
[Captivate Android Development] RockRatt:
+1 Here. My phone works fine on xcal kernel and the Sexual robot voice it LOVES running at 1.5Ghz and undervolted -125. My phone actually thanked me once, I swear I heard it.

That is WHY WE CHOOSE to test our phones to tthe limit huh?

Sent from My 2.3.3 or 2.3.4 Captivate Test Phone depending on what Gingergurl I am testing.
[Captivate Android Development] torred:
After flashing everything seems fine but the boot animation is not Apex like previous version. Is that right?
[Captivate Android Development] rogersa2k:
Correct. They are working on it.

- Aaron
[Captivate Android Development] airtower:
Anyone still on 7.0 experiencing auto brightness issues? Even with the setting enabled, the brightness is static.
[Captivate Android Development] dizx:
Yes, I'm seeing static as well. At first, I thought it was a sign of stability, but after staring at it for a while in different environments, I don't think the auto function is working.
[Captivate Android Development] Barsky:
anyone experiencing their Home button occasionally goes bonkers and acting as if someone was repeatidly pressing it?