yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] pikachu01:
Talon didn't change anything related to GPS since the last 10 or so builds (since the compass fix from 0.3.x. Might just be the your position where a lot of buildings are interfering with the GPS or you'll need to calibrate your GPS using those GPS apps (or using Angry GPS to calibrate your settings by disabling/enabling AGPS).

You may say that flashing other kernels makes the GPS work, but I don't see othe kernels doing any changes to the GPS (from their source code, and yes they are using the same code base - Samsung code base)

Try using Memory Freak to set some settings that are more applicable to your usage patterns. E.g. disabling ZRAM or reducing ZRAM and swappiness or using Nexus S LMK settings.

Try deleting the ram.conf and let it regenerate. It might be related to your busybox version. It might be a long stretch, but try deleting all instances of busybox and reflashing the kernel. (In /system/bin /system/xbin or /bin). WARNING - This might make your ROM unusable. As without busybox, you can't even perform root functions. However, I did encounter this issue while installing some ROMs that comes with different busybox versions. In the end, I had to remove all instances and install the busybox app from the market and used root to place the files correctly. After that, I removed the superuser APK and installed the one from the market, letting it update the superuser to the latest version.

Are you UVing too much?

Read my explanation above. The ROM might be bundling a busybox version that is incompatible to Talon's.
[Captivate Android Development] Coak5:
Does anyone notice a more significant battery drain on .21 compared to .20?
[Captivate Android Development] pikachu01:
Which governor are you using? Ondemand or OndemandX. If it's OndemandX, the threshold has been upped a bit by Existz:

Hence, you'll see battery is more draining in OndemandX. I personally use OndemandX and I found insignificant battery drain (around 2-5% more?) with the newer version. I can live with that :P
[Captivate Android Development] RashaMatt:
I renamed it and rebooted - now there is none; it was not regenerated! /etc is r/w.

I had System Tuner installed, which does some of that, but I froze it with Tibu before this last reboot. I've never made any manual changes.

'cat /proc/swaps' just gives me a header line.

'free' always shows all zeros on the swap line.

____________________________________________________

AT&T Captivate SGS I897, Serendipity VII b.1, TalonDEV 0.4.4.21, KC1
[Captivate Android Development] RashaMatt:
Can anyone suggest a different ROM for me to try - something that's worked well for you with Talon?

____________________________________________________

AT&T Captivate SGS I897, Serendipity VII b.1, TalonDEV 0.4.4.21, KC1
[Captivate Android Development] TwinkyOfHope:
I went from S7 b2 to apex 8.0, and have kept up with every apex update ever since. It is different though, a lot less black. However I'm in love with it
[Captivate Android Development] pikachu01:
Did you try this?
[Captivate Android Development] Coak5:
My governer was ondemand but my battery life was lasting about 6-8 hours on very light use. I reverted back to .20 and am getting at least 20 hours battery life on light to moderate usage.
[Captivate Android Development] pikachu01:
Weird, never had that before. Did you check what exactly is draining your battery?
[Captivate Android Development] Wdustin1:
I messed with Oc/UV on froyo roms and i never really do anything that makes overclocking nessary but i have been considering UV only for battery life. Is the life really good enough to make it worth it
[Captivate Android Development] greasyguy:
But this version is for captivate only right? I have the international one.
[Captivate Android Development] pikachu01:
i9000 version is here:

http://xdaforums.com/showthread.php?t=1106075
[Captivate Android Development] Coak5:
Nothing. I checked battery usage and task manager and everything was running the usual as I run currently on the reverted .20. I couldn't pinpoint the exact problem. Maybe it was either a bad flash or I should redownload the file and reflash again?
[Captivate Android Development] pikachu01:
Yup, please flash the newest version and report back. We would like to squish as many bugs as possible for the final release :)

Thanks!
[Captivate Android Development] pikachu01:
It is for me. I get about ~10-20% more hours on it if I don't UV. It could be due to the apps I install or placebo, but since it doesn't pose any risk, why not?
[Captivate Android Development] mystichobo:
Well, after flashing 20/21, I've suddenly picked up the charging bug :(

Phone reached 100% on the charger, the unplug your charger message popped up, then the phone proceeded to discharge.

Are there any log files or anything I can dump to help?
[Captivate Android Development] pikachu01:
The charging bug can occur randomly. Sometimes you'll have it and sometimes you don't. I've only seen mine having that bug once a long time ago (on some other kernel) and never had it since (even when I'm using the same kernel).
[Captivate Android Development] mjgspr95:
.21 on my phone definitely does not like the performance govenor... (oc'd over 1400 also). Never tried on other builds always on demand... may be my phone not build.
[Captivate Android Development] existz:
I only recommend using ondemand or ondemandX... The performance governor could not be disabled, that's why its left there...plus if you run it, make sure you are 100% stable because it only runs at Max clock.., it does not scale

Also, I believe I've got ondemandX fixed to where when a phone call comes in its not a black screen for a few seconds..will be fixed in next update
[Captivate Android Development] iamprayl:
I think the black screen bug is fixed on .21 never experienced that again since I updayed from .20.

Phone: Samsung Captivate

Kernel: TalonDev Kernel 0.4.4.19

ROM: Sensation ROM 2 with

i9000 Bootloader
[Captivate Android Development] RTBee:
I was on DlevRom 4.2 for a while which comes with a version of Talon (4.4.5, I believe) and upgraded as the newer test versions came out. Nice combo! If you check many of the Sigs on this thread, you'll notice many are sporting a version of Apex Rom, which comes with Dark Core kernel, but many have switched to Talon with great results as well. There are others that work well with it also, but these two I can personally recommend! ;-)
[Captivate Android Development] Time_Zone:
Can you please make sure you test pairing a bluetooth headset? I have lost two phones now to corrupt filesystem.
[Captivate Android Development] geokilla:
Tried doing what you said, and now even with superuser installed it says I don't have root. Flashing the Mosaic root update doesn't work either. So now I'm off to work on a phone without root. Luckily the app I'll be using the most today doesn't need root.
[Captivate Android Development] apparition:
I noticed this kernel seems to break the Voice Dialer app. It says please reboot when opening. The same app works fine on DarkCore though. I don't really use this app--just thought I'd point it out.
[Captivate Android Development] tallsilver:
Works fine for me running Dlev 4.2 and kernel .21 :D
[Captivate Android Development] pikachu01:
Many people have tried this without problems. Only the Phone.apk FC which can be fixed by flashing a 2.3.3 Phone.apk (and odex file if your ROM is an odexed ROM)

Try flashing speedmod and then apply root at recovery. Then flash Talon again.

Works fine for me too.
[Captivate Android Development] geokilla:
There is no Speedmod for Captivate. I'll just wait till tomorrow morning and see if I can use SuperOneClick to get root back.
[Captivate Android Development] studacris:
Its a kernel swap root method, you aren't going to be running it at all...you flash the kernel apply root in recovery and then flash talon. You never have to go into the os...
[Captivate Android Development] aalh:
http://xdaforums.com/showthread.php?t=893880&highlight=speedmod
[Captivate Android Development] pikachu01:
You can flash Speedmod Gingerbread for i9000 just to get root. Install it at CWM, reboot, apply root at CWM and then install Talon at CWM. All at 1 go. Note: I'm not sure if Speedmod CWM is able to install CWM 3 packages though. You might need Odin to install Talon if this is not the case.
[Captivate Android Development] RashaMatt:
I deleted ram.conf and rebooted - it did not regenerate.

Then I deleted all the busybox files from /bin, /system/bin, /system/xbin, and superuser.apk. This completely borked my cappy so I couldn't reinstall Busybox OR SuperUser. But after rebooting - still no zram and no ram.conf generated.

Then I installed Dlev 4.2 (I was running Serendipity VII before) after factory-reset, clearing cache, dalvik, etc. I noted that the Dlev wipe-install re-partitioned /system, /data, etc.

And STILL NO RAM.CONF, STILL NO ZRAM.

Then I installed TalonDEV 0.4.4.21 - STILL NO RAM.CONF, STILL NO ZRAM.

Put some debug logging in there if you want me to try anything else.
[Captivate Android Development] pikachu01:
Ok, can you install speedmod and try apply su+busybox?

When you remove busybox, you shouldn't remove superuser.apk also. It's needed to gain su.

After that, install the busybox app from the market and install busybox 1.17.x. Only after that, remove superuser.apk and install the one from the market and let it update the su. (However, it might fail for some people as it's pretty fragile)

Try flashing speedmod and using speedmod's method, install su + busybox.
[Captivate Android Development] IDoMy0wnRacing:
This is a froyo kernel

This link is for GB: http://xdaforums.com/showthread.php?t=1042543

I'm not sure if it's what you are looking for.
[Captivate Android Development] Kyuta Syuko:
existz mentioned some fixes being implemented in the next test version. Is there an ETA or even a rough ETA on when it'll be ready? Just curious since I'm thinking of giving Talon a try again but if he's going to turn around and release a new one tomorrow or later this week I would rather wait for it.
[Captivate Android Development] crazililazn:
All of a sudden my phone became soft-bricked. Everytime I try to boot the phone, it gets stuck at the "Loading Talon" boot screen. I can't get into Recovery mode either. Any suggestions on what i should do?
[Captivate Android Development] pikachu01:
Try reflashing an older version of Talon using Odin? Then with the CWM, flash to the current version 0.4.4.21
[Captivate Android Development] crazililazn:
Just want to make sure, kernels go to 'PDA', right?
[Captivate Android Development] pikachu01:
Yes. Kernels go into PDA.
[Captivate Android Development] crazililazn:
Didn't seem to work :/ Stuck at the Talon bootscreen if the older kernel as well.
[Captivate Android Development] Fate-Silver:
Can go into Download Mode?

If can, then, flash back to STOCK Gingerbread KF1 ROM 1st.

Then, start everything all over again.
[Captivate Android Development] pikachu01:
The cause is not because of the kernel then. Can you explain what you did before this soft-brick happened?

Yes, at worse, you'll need to do a reflash from stock and start all over again.
[Captivate Android Development] crazililazn:
I really didn't do anything lol. It was in standby in my pocket for awhile and when i took it out, the phone was stuck at the "Loading Talon" screen :/
[Captivate Android Development] pikachu01:
If you're willing to lose all your data, you should flash into stock JVR and start over again.

Never encountered this before and never been reported.
[Captivate Android Development] crazililazn:
Yeah, I was hoping that there would be another way ><
[Captivate Android Development] TwinkyOfHope:
I'm currently running .21, vr, and OndemandX.

Is 8 hours at 100mhz normal?
[Captivate Android Development] pikachu01:
It is, if you're running sync in the background where the phone will wake up intermittently.

I'm on OndemandX too, but only have 6% in 100MHz with 1GHz even lesser and 88% on Deep Sleep.
[Captivate Android Development] TwinkyOfHope:
I only have Sync on for pushed Gmail, but that is totally not worth it!

Thank you very much, and I appreciate the quick reply.

I'm going to turn it off and see how it goes.
[Captivate Android Development] Coak5:
Hey, I guess it was a bad flash. I redownloaded and reflashed .21 and everything seems to be working in order so far today. Amazing battery life like .20. No problems whatsoever so far.
[Captivate Android Development] RashaMatt:
I already installed DlevRom (a wipe install), so I have root and su and bb again. So, no need for speedmod.

Still no zram here...

____________________________________________________________

AT&T Captivate SGS I897, Serendipity VII b.1, TalonDEV 0.4.4.20, KC1
[Captivate Android Development] pikachu01:
The busybox that comes with the ROM might be incompatible. Try downloading the busybox from market and install the version 1.1.7.x. After that, make sure your su binary is the latest by checking for update.

Next, restart your phone and see if ram.conf is there or not.
[Captivate Android Development] cnu4u:
reboot

with recent updates, I was never under 10% of battery. Today, I was on call and my phone's battery fell to 7% and restarted wiping battery stats after 30%. :eek: I have seen this issue in earlier versions of 0.4.4. Not sure if anyone else have this issue.
[Captivate Android Development] existz:
If you had it hooked to USB then yes, it charges at 100mhz on USB (default was 200)
[Captivate Android Development] rlorange:
Were you charging during that time via USB?

**Simply Honey3.9, Talon kernel1.3ghz**
[Captivate Android Development] rlorange:
Did read your reply 1st but good to know I know some stuff... lol!

**Simply Honey3.9, Talon kernel1.3ghz**
[Captivate Android Development] Time_Zone:
I don't believe this to be true. Who is successful using a bt headset with 4.4.21 and Apex 9.1?

I have lost 2 phones due to file system corruption after enabling bt with 4.4.21. 4.3 did not have this problem, DC 3.0 also did not. I have posted logs in this thread if you want to look. I posted them last week.
[Captivate Android Development] tmng95014:
I used Continuum 6.1 and 0.4.4.21 without any problem.
[Captivate Android Development] Wdustin1:
If you have lost 2 phones due to this shouldn't there be a warning on the OP in huge letters warning against it because it is bricking phones. I didn't even know phones could get bricked because of the file system
[Captivate Android Development] mrhaley30705:
I don't think a kernel flash will hard brick a phone. Scramble the param.lfs and make you think its a hard brick, maybe. I've heard a few stories of black screens being revived with odin, so I'm skeptical.
[Captivate Android Development] Time_Zone:
Right, but I am not seeing the data of users using a bt headset with 4.4.21 and apex and am not convinced it is tested. Hence my uncertainty. If you are confident, could you try this combination and tell me your results? 4.4.21 + apex + BT headset (paired)? The devs in here understand what I am trying to dig for. No one is arguing or fighting. This is just a priority I really want to get some data on.
[Captivate Android Development] Time_Zone:
How does one unscramble param.lfs? I had thought flashing stock would fix that.

Scenario:

1. Flash Apex + 4.4.21 no bluetooth. wait 24 hours... no crash

2. Pair Bt headset. many reboots over the next few hours until I only get a bootloop from talon screen onward.

3. download mode and flash I897UCJF6-final-OCD-REV0.exe. After flash it would reboot and list an error about unable to access /data.

Again. Not arguing. Just mining for some data from people who are successful using this combination. I still do not have this confirmation.

Edit: I really hope I am wrong and this is just something stupid on my part. But if there IS a problem, isn't better for the devs to know?
[Captivate Android Development] justin860:
I am getting charging issues with the new kernel in about 4 roms that I tried it with, It will only charge to about 93% but as soon as i change the kernel it goes to 100% with some more time charging
[Captivate Android Development] mrcpu:
Minor saga:

I had to mount / rw, then run /bin/install-ramfs-setup or whatever it is to get a /system/etc/ram.conf file to appear. Otherwise my use of memoryfreak was just blanked out.

After changing it to nexus s settings/160/50, I am *very impressed*. The thing I notice the most is the fact that the camera starts up so fast. usually it's a loooooooooong pause before it's ready to take a pic. With this thing, yeehaw.

I am very happy right now.

Continuum 6.2.1-pre-platinum, talon 4.4.21
[Captivate Android Development] TwinkyOfHope:
Oh! Yes I was charging via USB. I never realized it did that, thank you. And it's an honor to have my question personally answered by you haha
[Captivate Android Development] pikachu01:
Not quite sure what you're saying. Sorry.

You mean, using BT will actually hard brick a phone? Never encountered that before actually. Can you flash something other than UCJF6? How about going back to Froyo?

Yes, my phone can only charge to 96%. It is the real value however (from LiOn's charge getting worse as time goes because of use). 93% might be your real value your battery can charge. Before this, it will show 100% as the phone is lying to you. You can read the changes Existz made in his github to know more about this "battery value" issue:

https://github.com/existz/linux_gt-i9000-gb/commit/18fb4bb7eb3588b583bd38a380170925ff0f16bc

It might be a busybox problem that Talon can't do the ramfs-setup at boot. Try reverting to an older busybox (using the busybox installer from the market) And, I'm using Nexus S values too. It seems fast for me too with ZRAM at 160 and swappiness at 50.
[Captivate Android Development] cnu4u:
Reboots with 7% battery was experienced during early versions of 0.4.4. Recently I never got to test my phone under 10% battery. Currently I am on .21 version and when battery was 7%, phone got restarted. I was on call when this happened :(. Hope this explains the issue.
[Captivate Android Development] pikachu01:
I'll troubleshoot the problem and get back to you on that.

Edit: But so far, haven't had a reboot because of low battery, as it was personally solved quite a few builds ago by my testing and Existz's code revert. Try not UVing for now? or reduce your UV?
[Captivate Android Development] Spidious:
Well going back to darky kernel. No matter what I do, after the phone is on for about three hours. It starts lagging big time. So bad it is almost unusable.

Sent from my phone in a secret location.
[Captivate Android Development] pikachu01:
Did you use Memory Freak and used these settings:

Nexus S LMK

ZRAM 160

Swappiness 50

Never had lagginess after applying these settings
[Captivate Android Development] rmntruexjr:
I hadn't changed these settings yet since i didn't have time to test but since you posted those values I decided to try it. For some reason it wont save/apply the settings. It acts like it does but after reboot it shows the default values. any Ideas?
[Captivate Android Development] Rrryan2:
Just thought I would try since my battery was low anyway. I can successfully place calls at 3%.

Agree that whatever's causing the reboots probably isn't (directly) kernel related. Maybe it's just at that point that the memory lag is catching up, or maybe a over-UV problem. And I'm UV'd down to -125 on most of the stock states, -150@200MHz, -175@100MHz. I know, my phone is ridiculously tolerant of UV. ;)
[Captivate Android Development] pikachu01:
Did you give SU to MemoryFreak? You might have multiple busybox versions in your phone. Try removing all except /system/xbin's busybox. And make sure xbin's busybox is version 1.17.x
[Captivate Android Development] rlorange:
Anyone else using tegrak to oc beyond 1.2ghz? I'm at 1.4ghz and very surprised I only need 1340mv and 1110mv internal voltage to achieve this. 100% stabke

**Simply Honey3.9, Talon kernel1.3ghz**
[Captivate Android Development] rmntruexjr:
For some reason it didn't work for me until I installed the same version of busybox (1.17.4) to both /xbin and /bin. Running on Continuum6.2.1.

Thanks for pointing me in the right direction!:)
[Captivate Android Development] Vaanhoot:
That happened to me on Dlev 4.2 and Talon 0.4.4.21, and I use Bluetooth all the time. I thought it was caused by Voodoo lagfix. Just got my replacement phone today, they replaced the main board to get it working again. What is a safe version to use cause I thought it was caused by the lagfix so I am back on Dlev 4.2 and Talon 0.4.4.21.

Edit: sorry thought I quoted from few posts back about Talon 0.4.4.21 and Bluetooth corrupting filesystem copy and pasted below.
[Captivate Android Development] existz:
Try flashing back to stock with a different one click, i had the same issue when i came back from Miui (all of this was unrelated to Talon, was on MIUI), all went well then when it rebooted it spit out errors about /data..., for example, the KF1 (without bootloaders) one click would not work for me..kept giving me errors about /data, had to flash back to JF6 w/ bootloaders ...but you might get lucky with a different one.. As long as you can get into download mode, its not hard-bricked, there is away to go back to stock..just have to find the right combo

Heres the link to the JF6 one click that worked successfully for me when i had the problem, might be same as yours, but just incase...also theres a couple other ones out there you can try..(KF1..etc)

NOTE that this will flash back to JF6 and froyo bootloaders, you will then have to flash gingerbread bootloaders afterwards..

http://xdaforums.com/showthread.php?t=731989&highlight=jf6+one+click
[Captivate Android Development] Time_Zone:
I tried that one, kf1, cog 5 beta, darky resurrection 10.2. What I didn't try was pulling the sim card. Might try that if I am in the same position again. For now 4.3 and dark core have not exhibited the problem.
[Captivate Android Development] Vaanhoot:
I had the same problem as poster. I just got my phone back on warrenty and decided to flash back to Talon 0.4.3 to be on the safe side and got an error entering recovery:

Error: unable to mount mckblock01p1

Error: unable to mount dbdata.

Sdcard appears empty and flash back to stock via odin does not resolve issue, get the same error on stock. I am able to boot stock rom but i get fc's aglore and internal memory is 0.00 bytes so I can't install any apps, says there is not enough available space when i try to install something even though I have zero apps installed. Same problem as before. Definately cause by talon 0.4.4.21 and Bluetooth.
[Captivate Android Development] Time_Zone:
Pull your sim out and boot. Does this fix it?
[Captivate Android Development] pikachu01:
Guys, I think the your pit files are not correctly being set. I advise a repartition from stock with 512 pit before flashing anything on your phone.
[Captivate Android Development] Time_Zone:
Tried that too, darky resurrection does that
[Captivate Android Development] RashaMatt:
Ok, I finally got zram working by following the advice of 2 others here:

1. Installed busybox 1.17 to BOTH /bin and /xbin

2. Mounted / as r/w, then ran /bin/ ramset-install-conf

After Rebooting, swap now exists, and MF is working. Thanks pikachu and everyone else for all the help and suggestions.

____________________________________________________________

AT&T Captivate SGS I897, Serendipity VII b.1, TalonDEV 0.4.4.20, KC1