yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] cnu4u:
existz.. thanks for wonderful work

I have installed 0.4.4.9 since its launch on JVR-FUN. Due to its color, I am unable to leave talon... Promixity sensor problem is fixed. Lag exists and most of the time my RAM is used close to 290 tough I got 2 - 3 additional apps are installed... Battery is draining little faster but I am NOT complaining on this as there are many factors impacting this...

Great work and will see you when 0.4.4 is out,.... have nice weekend.
[Captivate Android Development] H3llstorm:
Got it, after 5hrs & 49 minutes.
[Captivate Android Development] Jep56:
Yep, took me about 11 hours, then the lag hit. Went back to 0.4.3 Big Men for now.
[Captivate Android Development] existz:
The "lag" after long uptime is in every build, its most likely caused by the memory leak, we are still trying to locate the source of the issue...in the mean time you can try disabling ZRAM_SIZE=0 in /etc/ram.conf then reboot, some users report this really helps for them..but its probably going to be a few more test builds before this ones squashed
[Captivate Android Development] Peaster111:
Yeah... The "old/unfixed lag" seems to kick in around 10-12 hours for me. I just reboot. Exists and company will get it.
[Captivate Android Development] drewbag:
I have been having this exact same problem. I have reproduced it every time my phone is on low battery.
[Captivate Android Development] existz:
And this is with 0.4.4.9? the issue is a known issue with 0.4.3
[Captivate Android Development] TonyStark R.I.P.:
Are you sure this wasn't a modem issue?
[Captivate Android Development] timn2bama:
4.9

Been running 4.9 for 24hrs now :

I put zram=0

Free memory between 74-55

Voltage Control bfq and performance 1200=0,1000=0,800=50,400=100,200=100,100,=100

On ext4 and phone is running smooth and really fast no reboots over night while charging
[Captivate Android Development] topiratiko:
+1 same performance here altho im -125 all the way down. Lookout security is an absolute memory HOG by the way...using 40....why??? lol

JVR modem 3.97 mb down on Saturday morn..good call volume also.

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] shane87:
Ok, so I just noticed something extremely odd. I went to open gallery to view the pics I have on my phone, except gallery was not in my app drawer. Odd, as it is not on any of my homescreens either. I checked in /system/apps, and gallery-3d.apk is there. So I checked my hide apps menu, and gallery is shown there, and listed as not hidden. So I selected hide, then I unhid it. Still no gallery. Then I went to root explorer, and tapped one of the pictures. Gallery launched, but my phone immediately slowed to a crawl, and the picture never loaded. When I finally got out of gallery, my phone immediately speeded back up. And gallery is still not shown on my app drawer.

My setup is:

Continuum 6.1 w/red gingerbread for continuum6.1

Talon 0.4.4.9

Whatever modem continuum ships with.

-25 uv on 1200 and 1000

-50 uv on 800, 400, 200, 100

Go launcher ex

The really odd thing is that gallery was there yesterday before I flashed 0.4.4.9. Of course, I had just come from a possibly bad flash of a personally built talon kernel, and when I finally got talon back on, it converted system back to rfs. I have since converted back to ext4.

Maybe due to the bad flash, or maybe due to the ext4->rfs->ext4 conversions, which were, I think, due to the bad flash.

Just complete strangeness.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] drewbag:
Yes, I just started using the talon kernel 4 days ago with the Dlev 4.2 ROM. Everything is perfect except for the low battery restart issue. Mine only seems to happen below 20 percent though. (when the battery meter goes red)
[Captivate Android Development] pikachu01:
Which Talon version are you using? You can use the newer released one (0.4.4.9 in a few posts back by existz)
[Captivate Android Development] drewbag:
I am sure that I was on 4.4.9 but I just flashed it again to be sure. I have full battery right now so I'll report back at the end of the day.
[Captivate Android Development] existz:
I need a few people who has the "charge bug" and who can reproduce it on a daily basis to msg me (where you charge over night, it says 100% and when u unplug it, it drops down 5-10-20-30%)...got a test build we need tested with a possible fix in regards to this bug.
[Captivate Android Development] manny05:
I wouldn't mind trying the fix exist

I usually have the bug. Goes down to 98% sometimes all the way to 92%.

I usually fix it by recalibrating my battery. But it does get annoying.

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] existz:
Alrighty, we got some fixes we pulled from the infuse source, and so far for me and kodos, its been staying at 99% everytime.. but since the charge bug can sometimes be random, its hard to say if its fixed or not ...or atleast a workaround for it
[Captivate Android Development] sinichi21:
existz will the nexus cypress-touchkey driver be included in the next release i think it fixes my back button going crazy from time to time dont know about the others though my phone doesnt really like the zram off for some reason like the others it really lags so bad from a long time so im going back to zram on. thanks for a great kernel
[Captivate Android Development] existz:
Possibly, zach reported some weird issues with it on his end, not sure yet if its just an i9000 thing or what yet
[Captivate Android Development] Reynaldinho111:
@existz

0.4.4.9 is almost perfect imo. I turn my phone off at night so the charge bug isnt an issue for me. The only trouble im having is with wifi, im frequently rebooting my phone, reseting my router etc just to get wifi to turn connect. Aside from that i have absolutely no complaints.

sent from my beloved cappy!!
[Captivate Android Development] existz:
What does it do? just error out?..have you tried enabling via settings menu?
[Captivate Android Development] sinichi21:
I see I9000 has problem with it. Anyway if you still need testers for the battery charge issue I can test later when I got off from work after 8hours though
[Captivate Android Development] RashaMatt:
"status bar brightness" bug related to lag?

I have noticed for a long time (maybe in all GB ROMS?) that the "drag status bar to change brightness" feature initially works after a boot, but stops working eventually (using it always sets brightness to 100%, while other methods to change screen brightness continue to work).

Today I noticed that the onset of this behavior seems to coincide with the onset of lag, somewhere around 6-10 hours after boot. I killed the StatusBar process but I couldn't figure out how to restart it to see if that fixed it.

Also, setting brightness down to 1% is again turning the screen green - Voodoo color problem, I know - just not sure where to report it.

TalonDEV-0.4.4.9-1200, Serendipity VII build 1
[Captivate Android Development] timn2bama:
I would like to try this version
[Captivate Android Development] existz:
Give me a little bit and once I get a test build ready (still messing with a few things), ill start msg'ing some of you back
[Captivate Android Development] -Thrive-:
My workaround for the charge bug works every time. I just power up the phone in the morning while it is still plugged in and it comes up at 100% every time so I stopped even worrying about it. Of course this isn't an option for people who leave their phones powered on all night.

I am willing to test your new fix.
[Captivate Android Development] hobbs:
I can test your charge bug fix.
[Captivate Android Development] Reynaldinho111:
Sometimes it errors out sometimes it just does nothing, never reboots though and yeah ive tried through settings menu too.

sent from my beloved cappy!!
[Captivate Android Development] VFO:
I am experiencing the same thing. It's weird because if I try and activate wifi from the power menu it is almost certain to error out but if I forgo the power menu and go straight to the setting menu it seems to be less of a chance to error. I am running Talon 0.4.4.9 with Continuum 6.1. I did not start to see this wifi issue until 4.4.8 in which it happened less frequently but with 4.4.9 it seems to be much more frequent. I am also experiencing the charge bug and would like to test the updated "charge bug" release. Other than those issues 4.4.9 has been super slick and runs like a champ. Thanks for the great work and excellent support existz and team.
[Captivate Android Development] melvinaury:
Me too.
[Captivate Android Development] existz:
Test probably wont be till tomorrow, trying to track down a few things since update to latest samsung source...so ill get a new test up tomorrow for you guys, not sure if ill make it a public test yet or not, but def will let a fwe of you know so you can test charge bug
[Captivate Android Development] ngochuy:
In my opinon, talon 0.4.4.8 is better than 0.4.4.9. I got no lag, very smooth eventhoungh the used ram goes up more than 300 MB. 0.4.4.9 is so lag if ram goes up to 290 MB or more
[Captivate Android Development] Koizuma:
I can test as well, pm sent

Swyped from my SGH-I896 using XDA App.
[Captivate Android Development] bballer182:
I had the first one ever since owning the thing happen the other night. said 100% pulled it off to see it dropped down to 46%. haven't been able to reproduce it though...
[Captivate Android Development] tylercarter:
I was texting this morning and my phone rebooted by itself. Hadnt even been on this kernel for 24 hours. its all good though. I love all the tweaks. Cant wait for todays beta!
[Captivate Android Development] BumRush:
Love the new boot logo. One thing is that the "loading talon" wording is not centered. To off to the right. Is the a bug or intentional?
[Captivate Android Development] existz:
its on purpose
[Captivate Android Development] tylercarter:
I like it that way. It looks great!
[Captivate Android Development] manny05:
Not sure if this is happening because of the kernel, rom, or the supercharge script I applied... But lately when i open an app several times through out the day, my phone will freeze.... The screen stays white or black depending on the app... This usually happens more often with my text messaging app (handcent... Now I switch to sms pro to see if it was the app but it still happens). Even my. Phone app froze.. It just had a black screen like it wouldn't load up..i try exiting the app by pressing home and nothing..So I left it there and it rebooted on its own

Any ideas or fix???

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] crazililazn:
One thing I noticed using 0.4.4.9 is that after opening a few apps, the phone doesn't allocate ram as well and the result is that the phone starts lagging.
[Captivate Android Development] demarton:
after that if you fired up any racing / fast paced games, it will stutter as hell.

it's been reported by a few, including myself. Hopefully it will get a fix soon.
[Captivate Android Development] Galaid:
Is this I897 or I9000 version?
[Captivate Android Development] pikachu01:
It's in both i897 and i9000. Binaries in this thread though are for i897. You can search for the same thread at the SGS forum for the i9000 version..
[Captivate Android Development] xThe Enforcer:
Is there a TalonDEV 0.4.4.9 340MB 1200MHZ BIG MEM version?
[Captivate Android Development] Sqb:
Existz usually only does public tests in one release. The actual public release has always had the usual versions. Easier for uploading and less time consuming I'm guessing

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] upNsmokeAllDay:
I had to go back to 0.3.1 as there is no lag or charge issues with that version for me.
[Captivate Android Development] Rrryan2:
Same for me. Unpredictably and unusably laggy to the point of freezing at times but I haven't been able to isolate any consistent precipitating circumstance(s) yet. Happens sometimes immediately after unlocking, sometimes when running graphics-heavy apps (even Google Nav) with wifi on and off, sometimes during background sync and sometimes not.

Running 0.4.4.9, UV and OC to 1.2 SIO/ondemand with Control Freak, Apex 9.0 JVR, TW4. I've been running Cog KF1 for the last month or so and can't really compare to recent Talon or I-9000 ROM iterations.
[Captivate Android Development] topiratiko:
Tw4 is a MAJOR cause of system instability for a lot of users including myself. Code is simply not written for Galaxy S hardware. (written for galaxy s II) Step #1 ditch tw4. Step 2 disable zram. Step 3 apply more aggressive lmk settings. I had fone on overnite and woke up to 245/340 ram and a smooth phone. With the settings i have ive never seen it go over 287/340...once it hits that point it shuts down uneeded programs to free up ram and keep it smooth

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] topiratiko:
These are NOT the settings recommended by anybody on this thread ...i beilive these were juwe11's settings...i do not take responsibility for any screwups/funny business..these settings work flawlessly for me...if your experiencing high ram usage resulting in lag give this a shot. MAKE SURE you include commas and quotes it wont work without it. I personally use efs file explorer to set this...currently on Apex 9.0 with talondev kernel although settings were fine on Apex 8.3

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Rrryan2:
Thanks!

Yeah, TW4 is a potential culprit, why I thought to mention it. But it seems not all kernels have this same difficulty with it...

I just keep hoping that one of these days there will be something that can run a stable version of TW4 as I really like its look and feel, maybe because this was my 1st Android device and I ran stock ROMs for the first few months and got used to TW. Tried a buncha launchers, nothing else feels as intuitive to me as TW and TW-derived (CrushD etc.) launchers.

I'll experiment with zram and lmk but I'll need to learn to do it first. EDIT: Duh. Answered in OP - edit /etc/ram.conf :)
[Captivate Android Development] topiratiko:
Go launcher ex with bulldoze screen transitions is just as smooth as tw4 if not smoother and endless customization

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Rrryan2:
Missing end quote on LMK_MINFREE...? EDIT: nvm, I'm an idiot and didn't see the 2nd line...

Here's the copy/pastable text for anyone who needs as well:

Edit: The LMK settings really messed me up so I removed them to ensure I don't cause problems for others
[Captivate Android Development] topiratiko:
Those are WRONG!!! LOOK at my settings again!

Edit. K were good lol

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Rrryan2:
Yeah, I caught my mistake after a minute and edited. ;)

The lmk settings really screwed things up for me though. Lagged/froze the phone so bad the display timed out and then kept timing out before I could the unlock screen swiped to unlock. Had to adb push a rollback ram.conf to get it working again, LOL.

Afterward I tried *just* setting ZRAM=0 and leaving the rest of lmk alone. While it's still a bit laggy here and there it's nowhere near as bad as it was on stock Apex 9/TalonDev 0.4.4.9. And that's even still running TW4.
[Captivate Android Development] rajendra82:
I copy/pasted the settings before you edited them out. My experience with the new settings has been the opposite of what you had. I am on Continuum 6.1, and with the original LMK settings, the memory usage over time would creep up to 300 MB+. When it got to 320 MB, it was a lot of lag with 0.4.3, and an outright freeze with 0.4.4.9. This was fixed with a reboot until time passed again. It did not seem to matter whether ZRAM was enabled or not. With the LMK settings tweaked I am finally seeing the LMK actually doing its job. After I opened and closed some apps and checked memory usage (under 0.4.4.9), I see more memory free than when I first booted up. This never happened before under Gingerbread, and is more like what I used to see under Froyo, where my phone could go a week before rebooting, not hours.

Edit: Since the past few minutes of testing are so encouraging, I am going to re-enable ZRAM, and see how things go. If I can go a few days between rebooting, I will report back.
[Captivate Android Development] topiratiko:
I have issues with zram enabled....when i shut it off its GOLDEN

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] topiratiko:
Sorry to hear that man....are u sure there wasnt an extra comma or space ANYWHERE? And also make sure you do it under first set of settings and not further down where it says old lmk settings....what Rom r u on?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] rajendra82:
I agree. With ZRAM enabled, the memory footprint kept growing past 300 MB over time. Witout it in the mix, everything gets killed back to the RAM I had upon boot.
[Captivate Android Development] crazililazn:
Umm quick question, where is the ram.conf that you edited?
[Captivate Android Development] topiratiko:
Using efs file explorer...go to folder etc and scroll down till you see ram.config

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Rrryan2:
No need to apologize, comes with the territory. No obvious mistakes that I can see. And seems like Rajendra82 copied & pasted what I had without incident too, so...

Since it seems to work great for Raj I'll go ahead and re-paste it. This is what I had, lines 17-39 (Not in old settings) of /etc/ram.conf under Apex 9.0 (JVR):

# LMK/ZRAM settings
FOREGROUND_APP_ADJ=0
VISIBLE_APP_ADJ=1
PERCEPTIBLE_APP_ADJ=2
HEAVY_WEIGHT_APP_ADJ=3
SECONDARY_SERVER_ADJ=3
BACKUP_APP_ADJ=3
HOME_APP_ADJ=3
HIDDEN_APP_MIN_ADJ=5
EMPTY_APP_ADJ=15
FOREGROUND_APP_MEM=2560
VISIBLE_APP_MEM=4096
PERCEPTIBLE_APP_MEM=6144
HEAVY_WEIGHT_APP_MEM=12288
SECONDARY_SERVER_MEM=12288
BACKUP_APP_MEM=12288
HOME_APP_MEM=12288
HIDDEN_APP_MEM=14336
EMPTY_APP_MEM=18432
LMK_ADJ="0,1,2,3,7,15"
LMK_MINFREE="2560,4096,6144,12288,14336,18432"
ZRAM_SIZE=0
SWAPPINESS=70

Double-checked and can't spot any error, no missing comma or quote etc. Even checked for extraneous whitespace at end of lines.

I adb pulled /etc/ram.conf, adb pulled & edited with Notepad++, mounted /etc/ r/w using Root Explorer and then adb pushed. I didn't use EFS but can't see how that should make a difference.

I'll experiment some more, maybe I got bad push before or did something dumb.
[Captivate Android Development] topiratiko:
Did u reboot after changes?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Koizuma:
Or u can manually edit the file using root explorer, what i did this morning and has been running perfect since then
[Captivate Android Development] topiratiko:
+1 the best way to go

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] topiratiko:
Any luck?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Rrryan2:
Lol. Yes, of course I did!

Eh. I cheated finally. Edited it on the PC, transferred to phone with dropbox, and pasted in with Root Explorer. I just hate text editing on the phone when fine cursor control is needed, so tedious.

Using the above method... HELL YES, it seems like it's working just freaking GREAT now and I must have done something dumb before without knowing it. Snappier than it's ever been even with TW4 and even got a ~200 bump in Quadrant (not that that's necessarily meaningful, but...). Memory usage seems the lowest I've seen on GB, and in particular I can switch back and forth between the browser and other apps smoothly without the browser getting killed, something I don't recall seeing lately on a GB ROM.

And what's bizarre... the stock browser in Apex 9 had been unreliable, supposedly due to a known issue with deodexing the JVR browser. Seems like it works just fine now.

Think we have a winner, folks!
[Captivate Android Development] topiratiko:
Good to hear!

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] johan8:
my experience in Talon 0.4.4 ~ 0.4.4.9

So far here is my experience in Talon 0.4.4 ~ 0.4.4.9

0.4.4.8

This build seems has problem in memory management.

Memory usage will raise to 280~30xMB after some period of time,

then the system will become laggy,

if keep heavy load the phone, such as game, play flash video.....

the system will crash then reboot.

Laggy is telling you the system become unstable.

* in GB, FC vibra is cancelled, you will not note anything during FC.

Sometimes, running apps or background apps has been killed,

it seems normal purge.

But check inside /data/, there is "dumpstate" and "tombstones" created,

means that FC has occurred.

0.4.4.9

Has similar problem as 0.4.4.8, but the situation is worse.

System crash then reboot even in flight mode standby overnight.

0.4.4.6

the stable and smooth build so far.

memory used keeps around 250MB in my phone.

most of the time background apps can be purge normally.
[Captivate Android Development] Yuna:
Dear existz, can kernel do something hit hot screen issue? after 10-15 continiouus usage of device screen becomes a bit hot... ~ 45 C
[Captivate Android Development] Rrryan2:
Undervolting might help some, but only a little. But the real story is that heat is a natural product of high-powered electronics. These are minicomputers we carry in our pockets after all, and there is not room for a cooling fan in a thin phone. There's not much a developer can do to improve the heat management of the phone design afterward.

If the phone is in a case you might consider removing it. Cases act like insulating blankets.
[Captivate Android Development] Yuna:
Well, i know how physics work.

Just a small observation: i had no such issue on froyo (in such scale)
[Captivate Android Development] Rrryan2:
Sorry if I sounded condescending as I meant no offense.

I have noticed lately that my phone seems hot sometimes too, but we must also remember that it's summer and the difference might just be more noticeable on Gingerbread now than it was on Froyo in the winter/spring. Especially Ukrainian winters. I recently rolled back to Froyo for a week and still noticed the heat that hadn't seemed so noticeable before.

And I assure you, I don't mean to question your knowledge of the seasons and I don't mean to insult. :)
[Captivate Android Development] Yuna:
Can we speed up the boot-logo screen process? what taking so long for kernel to pass that screen? can we implement htc's hibernate?
[Captivate Android Development] psycho2097:
My experience on 4.9

I am currently on jvp. Apex 8 series I believe. Previously my phone used to lag like hell on talon 4.1. Flashed 4.9, still lagging. Then applied the new ramfree settings yesterday and set ZRAM to zero. The phone is decidedly faster, and has not lagged after 12 hours of on time. it still seems to have a memory leak though, the free memory was 174 at boot and now after clearing ram its 130ish. Also was able to reproduce charge death of ~60% drop on 4.9 twice, so I guess that's still not fixed.

I am on go launcher ex btw. No oc/uv.

Sent from my cell phone. DUH.
[Captivate Android Development] zacharias.maladroit:
it's extracting the XZ / lzma image

I'll have a look at that & see whether stuff can be sped up

hibernate probably not gonna happen

it's suspending all the way anyway

how often do you need to reboot the phone per day ?
[Captivate Android Development] Yuna:
hmm, too long extraction process :)

i reboot my phone 3-5 times a day.
[Captivate Android Development] topiratiko:
Existz,

Sent you a P.M...some contents courtesy of Juwe11
[Captivate Android Development] existz:
@yuna

Also voodoo initramfs slows it down some, it has some checks..etc..it does during boot..

@topiratiko

Once shane87 gets his app finished, this will solve everyones issue...will be able to choose different preset lmk settings, plus have control to manually adjust certain lmk settings...plus zram/swap settings
[Captivate Android Development] Vivified:
why?

10 char