yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Nerz:
i've read someone having the same problem as me but i didnt catch a resolve. I am trying to disable lag fix but for some reason everytime i try it doesn't work. i've tried from cwm with no go. some1 said something about voodoo control app, and although i see some preferences i can't seem to switch the lag fix. anyone know a fix?
[Captivate Android Development] daverup:
One of the builds of 0.4.3 was wiping /sbin. In my case, flashing 0.4.4.6 restored /sbin. This could be your problem, and a possible fix.
[Captivate Android Development] Nerz:
I'm on 4.2 but ill try flashing the latest and see what happens.
[Captivate Android Development] IDoMy0wnRacing:
I am using the Voodoo control Plus 3.0.1 app. If you select the "Lagfix preference", you should have the option to check the block "Ext4 conversion" and then the option to select "Ext4 /system" for a complete Ext4/lagfix conversion at next reboot. Reboot and you are done.
[Captivate Android Development] Nerz:
I'm trying to disable lagfix for the moment, not a full conversion. However, I tried it to see if it could help me disable it but still no success. I'm at a wits end.
[Captivate Android Development] airtower:
Is there only a 1200 OC version of 0.4.4 because it's in public test, or have you done away with higher OC's entirely for this release? Also, are you still planning to do away with the tegrak modules?
[Captivate Android Development] Aus_Azn:
The latest SetCPU supports UV natively with a UV enabled kernel.
[Captivate Android Development] alexige:
Exactly! He said this in a previous post. Im sure the full release will be like normal.
[Captivate Android Development] mjgspr95:
I bought the full version... It still maxed at 1.3ghz. I can set higher with optimizations, but control freak will not recognize voltage on any thing over 1.3ghz. For example I changed top freq to 1500 and second to 1300ghz... control freak shows 1500ghz with "?" for voltage and still shows 1000ghz as second frequency...

I was stable 1.5ghz on talon 2.2R... Not quite their with this.
[Captivate Android Development] smully1:
Is there a non oc 4.4 coming soon?
[Captivate Android Development] existz:
Yes, when 0.4.4 is released....for the test I only put up 1.2ghz because I did not want to build/upload all 4 versions (1ghz/1.2 -- bigmem/non-bigmem) . Official release will be like normal
[Captivate Android Development] mjgspr95:
Does Tegrak work with the 4.4 test build?
[Captivate Android Development] existz:
yes

10char
[Captivate Android Development] airtower:
So normal release means 1.2 max OC?
[Captivate Android Development] existz:
Yes for now, trying to work on our own OC module so we dont have to upload so many versions..with up to 1.4ghz that means 12 versions I have to upload/compile between i897/i9000...so right now only doing 1ghz and 1.2ghz versions, with less versions that means quicker/more updates..because where theres so many builds, i dont release until i get as much as i possibly can done to save on time..but with just 6 builds i dont care to compile/upload more often.
[Captivate Android Development] Peaster111:
Existz,

Well I tried to break it all day... no luck :p I flashed last night and used it today heavier than my typical norm... perfect, no issues. No reboots during phones calls. Had been seeing at least one by now. I think you squished that bug.

The strange thing is that the battery just won't go down despite my best efforts! Did you break the battery meter?! :rolleyes: I'm at 60% at 6:30 PM. It's holding about 10% higher usual and with heavier use. I know results vary wildly day-to-day so take this with a grain of salt, but my battery is def holding up noticeably better.

Thanks!
[Captivate Android Development] -Perp-:
I've noticed this too. My battery refuses to die lol. I have ~1h30min display time and unplugged for 15 hours and sitting at 68%
[Captivate Android Development] ngochuy:
Do u have any plans to update talon to support new base JVR of i9000?
[Captivate Android Development] d_gritza:
Existz,

Using Talon 4.1, 4.2, 4.3 was not a good experience for me with Apex and DlevROM so I kept reverting back to DarkCore.

I've been running the public beta for over a day and it's perfect, no reboots, very very little lag and great battery life.

The battery life is a little worse than DC but that can be due to it being 1200 rather than 1000 which I was using.

Can't wait for the BIGMEM versions to come out. You're on the right track :)

PS: not loving the nexus bootscreen though! You made it, so the talon logo should be loud and proud! IMO!
[Captivate Android Development] airtower:
that's cool. I'm very happy with 0.4.1. I (and the other "hardcore" oc'ers) just don't want to get left in the dust!
[Captivate Android Development] manny05:
I keep getting an error that my memory is running low... A pop up comes up saying that and I click ok and it takes me to the list of all Apps.. And it says I have 1.5gb free... So I'm obviously not running out of space... I uploaded a screenshot to show you what the error looks like. Any ideas or fix?

Mind you i have 16GB of onboard memory plus another 16GB on my microsd card. Which leaves me with 25gb of free memory more or less!

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] shane87:
What rom are you running? I remember having this same issue before, and I think I was on Apex 7.2 when it happened to me. When it started happening to me, I would not only see the low memory notification, but if I tried to download anything through opera mobile browser and save it to /sdcard/download, I would get an error about there not being enough room to save the file, even though I had 4-5gb free, and the file was in the mb size range.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] Koizuma:
So far using the 4.4.6 test kernal, the phone seems more responsive and battery life seems to be better as well. also digging the new start up screen. So far I haven't got any reboots during calls phone was at 3% before I charged it and had ran like a champ.

Awesome work existz

Swyped from my SGH-I896 using XDA App.
[Captivate Android Development] manny05:
actually this started happening when i was using serendipity about 3-4 days ago. so i switched to dlev rom 4.3 and just now i got this error..

however i did some research through google and apparently it has happened to many people..they suggested i go into settings - applications - manage app - and sort it by size..

come to find out contact storage was on top of the list with 107 mb..so i cleared that out and the error went away. before i did this i wasnt able to get any text messages but after i did all of my text msg started to come in one after the other....

weird since i have literally 32gb of space available... cant see why 107 mb would get in the way...

next time i flash a rom im just going to do a full wipe.

i do think maybe titanium backup the old contact storage and just restored it onto the new rom?! could be a possibility. but ill keep an eye on it

this is where i found my answer: last post

http://www.droidforums.net/forum/motorola-droid/43433-constantly-out-memory.html
[Captivate Android Development] dotuananh88:
Existz! I wonder that whether kernel Talon 0.4.X run well and smoothly with 2.3.4 JVR as it does in 2.3.4 JVQ or not ? Because Talon 0.4.X is based on 2.3.4 JVQ, therefore I really need your confirmation

Tks, you did a great job :D !
[Captivate Android Development] darass:
is it possible that if i have JVP rom and installed talon 0.4.3 which as i read now is based on JVQ that this is a cause of my problems with ram management and big lags and random hangs sometimes when using some time after rebot? after rebot 140 - 100MB RAM free, later about one day still free only about 40MB and freezes and lags.
[Captivate Android Development] TheSoaresan:
4.4 public test seems to have fixed my wifi reboot issue... can anyone else confirm? Running Mosaic VI....good job on the kernel existz
[Captivate Android Development] TheSoaresan:
And I'm getting better wifi too!
[Captivate Android Development] IDoMy0wnRacing:
I don't have any reboot issues. I am Really liking TalonDEV 4.4.6.
[Captivate Android Development] johan8:
Try it yourself, and make your own confirmation.
[Captivate Android Development] slayp00n:
Is the test build JVR copmatible?
[Captivate Android Development] Rhiannon224:
Zero reboots here, memory leak is also fixed on my phone with the test kernel.
[Captivate Android Development] daverup:
Getting reboots when toggling wifi on with Dlev4.2 and TalonDev 0.4.4.6.

Also got the reboots under the stock Dlev Talon 0.4.4.x.
[Captivate Android Development] existz:
Wifi reboot is a samsung issue, it happens even on stock rom and kernel.. some kernels are more sensitive than others .. this is from having only jvb source for kernel using with jvh/jvp/jvq/jvr roms... this issue did not happen with JVB, it started with JVH..so until samsung releases updated kernel sources, no way to fix the problem..but a work around is to enable wifi from settings menu instead of drop down/power widget., it still happens but not as often
[Captivate Android Development] tylercarter:
What sources are available? jvr source? jw
[Captivate Android Development] daverup:
Thanks for all your work on this. I simply wanted to report what I had found.

0.4.4.6 was nice, I just can't stop trying other combinations.
[Captivate Android Development] demarton:
lag / leak still

I hate to be the one to bring bad news,

test version 0.4.4.6, zram disabled as per existz intruction, EXT4.

after 15 hours running, lag everywhere.

As for memory leak, need more uptime, we'll see what happen then.

accidentally, I noticed I/O operation seems really slow, I copied some files from /cache to internal sd, only 15MB took like 15sec to finish.
[Captivate Android Development] existz:
What IO scheduler you using? I get really good read/write scores with BFQ or VR
[Captivate Android Development] demarton:
default, SIO I checked.

Just fired up a few games, stutter badly, almost unplayable, no option, need to reboot.

at least on my case I can confirm, lag after long run still not fix yet.

thanks existz for all your effort, I'm very sure you will squash those pesky bugs one day :D
[Captivate Android Development] topiratiko:
DEF switch to vr

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] existz:
Yea, lag after long uptime and memory leak are still there. Shane87 has made some progress on new 'Memory Freak' app for Talon. Hopefully we will have an internal beta this week and hopefully a release soon
[Captivate Android Development] kodos96:
Memory Freak won't fix the memory leak issue though, since the leak isn't related to LMK. I'm still working on tracking down the memory leak - its tough since you have to basically wait a day after each tweak in order to see if it made a difference. Right now I'm thinking it may be zram related, but still not 100% sure.
[Captivate Android Development] RashaMatt:
I've got the same lag in 0.4.4.6, showed up after about 24 hours' use. Seems like it might be a little less severe than before, though.

No other problems :)

_________________________________________

AT&T Captivate, Serendipity VII b1, TalonDEV 0.4.4.6, KC1
[Captivate Android Development] topiratiko:
I usually turn off my fone at night...if not i always reboot in the morn...ALL electrical devices seem to work better that way. How does anything work if it never gets a break? ;)

P.S. Enjoying vacation.

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] apparition:
Has 0.4.4.6 fixed the issue where if you receive a phone call with nothing near the proximity sensor, the screen sometimes goes black (have to press power/trigger the proximity sensor to get it to awaken again)? I'm not sure if this is a ROM issue or not, but I've been getting that with various ROMs and kernels.
[Captivate Android Development] pikachu01:
That is a Talon kernel issue. Should be resolved. It got fixed when I tried it.
[Captivate Android Development] demarton:
tried swapoff diabling zram.

still same lag.

seems like something else causing it.
[Captivate Android Development] aalh:
same thing here
[Captivate Android Development] existz:
Well, was talking to kodos96, and i might have been wrong on this..even when doing swapoff it does not unload the zram module, so its possible the memory leak could still happen if its zram related..we are looking into this and hopefully get it fixes soon...

but on another note, im hoping to get another public test build up today..changes are..

- updated rfkill from samsung infuse source

- updated wifi driver from samsung infuse source

- some upstream fixes to lowmemorykiller driver

- added cgroup timer slack subsystem
[Captivate Android Development] existz:
0.4.4.8 Public Test

So heres another updated public test build. We are still working on the lag/memory leak issue, so please bare with us..we are getting close to figuring it hopefully...but we made a few new changes since 0.4.4.6 and I want to get some feedback on these new changes.

Again, this test is only a 1.2ghz non-bigmem version (just for testing)

Full 0.4.4 Changelog

revert back to 2.6.35.7 base

added new kernel boot logo

disable more kernel debug

updated to JVR version/modules

set VFP mfpu=neon optimization

set usb charging lock to 100mhz

rfkill updates from Samsung Infuse

wifi driver updates from Samsung Infuse

upstream fixes for lowmemkill driver

upstream fixes for sched_autogroup

upstream fixes for RCU/TinyRCU

fix corruption issue with ZRAM

introduce cgroup timer slack subsystem

updated to sched_autogroup v4 (per session)

switch to TinyRCU (smaller memory footprint)

more random upstream fixes to ARM/SAMSUNG

added sampling down factor to ondemand

XZ kernel compression; initramfs to none

tons of general fixes from zacharias.maladroit

few new security fixes from zacharias.maladroit

Changelog since 0.4.4.6

updated to JVR initramfs contents

introduce cgroup timer slack subsystem

critical upstream fix to ZRAM (fixes corruption)

upstream fixes to lowmemorykiller driver

updated rfkill from latest Samsung Infuse source

updated wifi driver from latest Samsung Infuse source

This build has not been fully tested with JVR yet, just updated to JVR precompiled modules and version magic..so as of right now, this build is unsupported with JVR (JVP/JVQ only supported).

Also with this build, it includes updated rfkill/wifi driver updates from latest Samsung Infuse source ..even though the Infuse does not use BCM4329 driver, the source has been updated some.

Please report kernel issues here
[Captivate Android Development] Koizuma:
installing right now, will report back how it does
[Captivate Android Development] Sqb:
Thanks. Will flash once charged. I'm sure you are close to getting it just right. Your hard work shows with each release. Amazing

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] daverup:
Flashed 0.4.4.8 on Dlev4.2.

No problem with the CWM flash, phone, HSDPA working, no wifi problems yet. Using JVR modem.

Thanks for the update, seems pretty snappy so far.

:)
[Captivate Android Development] crazililazn:
Idk if this is related to the kernel, but I was updating some apps in the market and after 2 of the 6 finished updating, it kept saying "there is insufficient space on the device". The rest of the apps wouldn't update and then I can't install any other apps. Is anyone else getting this?
[Captivate Android Development] sinichi21:
You must be updating a huge file happen to me once i was updating with 20mb or 15mb i think just reboot should be fine its a known issue when you have many apps installed
[Captivate Android Development] dayv:
How much space do you have left? Check Settings/sd card and phone storage/system storage.

Now, I have had this happen to me a couple times in the past when I had plenty of space left. What I did to fix was to disable voodoo lagfix, reboot the phone, open the market and install one app, then re-enable voodoo lagfix, reboot the phone again, and that fixed it for me.
[Captivate Android Development] existz:
Ok, so to properly disable ZRAM just set ZRAM_SIZE=0 in /etc/ram.conf then reboot. This will prevent it from loading the ZRAM module on boot, just doing swapoff does disable ZRAM, but the module is still loaded and could possible still cause memory leak if ZRAM is the culprit..so just set ZRAM_SIZE=0 and reboot in /etc/ram.conf...for those of you who want to experiment some and help try to pinpoint this problem
[Captivate Android Development] kodos96:
Can those of you who have the wifi reboot bug try out the latest test release and let me know whether or not the wifi driver update has fixed it for you? Or improved it any?
[Captivate Android Development] TheSoaresan:
So far so good for me. I've enabled and disabled wifi 5 times with no reboots...yet lol
[Captivate Android Development] TheSoaresan:
So I tested it out more thoroughly. Good news: No more reboots, at all, no matter how many times I enabled and disabled it. Bad news:

This error sometimes occurs when wifi settings is not opened in the background.

All the tests were done using the pull down notification wifi toggle.
[Captivate Android Development] -Perp-:
Same error here (but no reboot either)
[Captivate Android Development] existz:
So what about just enabling/disabling normally? Like instead of multiple times back to back? Does it still error out or only when you keep toggling to make it reboot?

What I'm trying to get at is, so if someone just used wifi normally, does this error happen?
[Captivate Android Development] TheSoaresan:
It SOMETIMES errors out...but its mostly okay normally
[Captivate Android Development] existz:
Ok, so once it does error out, are you able to re-enable it again, either from dropdown/power widget or settings? .. if so, then it erroring out every once and again is better than it rebooting...but we might just be fixing one problem with another, but still better than the previous option.
[Captivate Android Development] -Perp-:
I have to turn wifi back on in settings. In dropdown / power widget, it tries to turn on, then stops (and stays off / error mode)
[Captivate Android Development] existz:
Gotcha.. Is this something that happens frequently for you, or just after toggling to try to force a reboot?...if it doesn't happen often, like every other time, then its probably worth keeping the changes to get rid of the reboot issue...or do you think its something that's worst than how it previously was?
[Captivate Android Development] TheSoaresan:
Keep the new wifi infuse driver...so much better that random rebooting! This is a step forward.
[Captivate Android Development] -Perp-:
Seems like I trigger the error EVERY time. I'm already used to turning wifi on in settings however. Actually, unless I'm testing it, I don't even turn off wifi anymore.

I'd still rather have the error than a reboot.
[Captivate Android Development] existz:
Ok, good, thats what i was hoping for. So worst case just enable wifi from settings menu...atleast it seems to fix reboot issue.. :)

So, now next big task is to update to 2.6.35.14 from longterm linux branch... what we will probably do this time, unlike last time when we bumped up to 2.6.35.13 base, is update commit by commit only using what we need..as from .7-.13/14 theres alot of stuff that does not apply to us. Since we figured out that the update does not cause the phone call reboot issue (caused from some sched/nohz commits), we should be good this time updating back up...but of course alot of testing is going to have to go into this. So what ill probably do is, update to a version..for example update to 2.6.35.8 in the next test/release, go from there and then next release bump up to 2.6.35.9..and so on, that way we can fully and publicly test a small amount of changes, instead of a drastic jump to .13/14 and not knowing what caused what problem
[Captivate Android Development] TheSoaresan:
What if we left the wifi menu open in the background all the time, it makes the toggle work. Would that drain battery leaving the wifi settings open in the background?
[Captivate Android Development] Peaster111:
Exists... Excellent plan! It may take some time, but we'll be able to manage progress with knowledge.
[Captivate Android Development] irishvandal:
Existz,

I am not having many/if at all, issue to speak of under 0.4.2 1200. Should I even find a need to flash up? From reading the update log, I wouldn't gain much and lose the gpu controls. Just wondering, cause I can't commit to beta runs for another week and a half, then I will have my two week break to burn this Cappy up for ya. Lol.

Sent from a state of delusion
[Captivate Android Development] existz:
I've also got something I'm wanting to do with talon, I'm pretty sure we can do it, if so it should be a game changer...but will probably take a little while to incorporate it... but ill just leave it at that ;P
[Captivate Android Development] existz:
Gpu controls do not work, even with all previous versions of talon..so not going to lose anything there. But I would recommend updating to atleast 0.4.4.6 (its a few pages back), as 0.4.4.8 was just posted earlier today.. but 0.4.4.6 has proven to be a good release, and an improved update over 0.4.2..which I'm not saying anything is wrong or unstable with 0.4.4.8, hell it might even be better/more stable than 0.4.4.6, just saying we have had 1500+ downloads with great feedback, need to see how 0.4.4.8 goes ..but it should be a good update
[Captivate Android Development] Rhiannon224:
I am on the new test kernel 4.4.8 and I toggled wifi on and off from the pulldown menu about 10 times until it stopped working, it didn't error or reboot, it just literally stopped working. Went into settings menu to turn on wifi expecting to see an error and nope, I just turned it on. Battery appears better since flashing. Each build shows improvements. Thanks for the hard work!
[Captivate Android Development] xTRUEx:
y the teaseeeee
[Captivate Android Development] upNsmokeAllDay:
Is there anyway to fix the charge bug? Once my phone hits Full it stops charging and if im doing anything on the phone when this happens and then unplug it im down 20% all of a sudden because it was not charging while being used while plugged in. Same happens if i let it sit all night and charge and unplug it in the morning.
[Captivate Android Development] RTBee:
Really??? You're just going to drop a bomb like that and walk away? How about another clue or two and maybe an approx. timeline?? Anything? You're killing us here. ;-)
[Captivate Android Development] shadvich:
0.4.4.8 seems to fine with wifi. I have it set to toggle automatically every 10 minutes and it hasn't rebooted yet. Phone uptime is at about 15 hours and no slowdowns yet. UV set to (-100/-125/-125/-125/-150/-150), vr scheduler, max 1200 mhz, ondemand.
[Captivate Android Development] Tatsuya79:
Hi, I've been asked in the i9000 thread to make a Talon version without Voodoo Colours.

As I don't own a captivate flash it at your own risks! (but as Talon devs have made most of the compiling pre-scripted this should be OK I guess)

Voodoo colours hack reverted, Speedmod Neutral MDNIE tweak, classic boot logo.

Removed - doesn't seem to work, I must have messed something while cleaning GalaxyS past template, sorry. :(
[Captivate Android Development] manny05:
Just downloaded the latest talon and it feels so much smoother. I mean I did add the supercharge memory tweak which quite frankly helps alot with memory management. But overall its working great. I was on the phone for hours yesterday and no reboot. Even with battery at 10%! Everything is looking good. Now we just need higher Overclocked :)

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] kitkitfok:
Sorry, this kernel don't work .........