yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Kyuta Syuko:
Just thought I'd put it out there that I can not get this tweak to work no matter what I try =|

Get a losetup not found error and a Device is busy error when trying to mount.

*edit* Actually as is I get a Syntax error with the mount command, but after adding -o rw -t ext4 flags I get the Device or Resource is busy error.
[Captivate Android Development] aobmax:
deleted due unrelated content
[Captivate Android Development] watsa:
You mean stock JF6? Thats a stock eclair build
[Captivate Android Development] geokilla:
0.4.4/0.4.5 just got cancelled?
[Captivate Android Development] color0:
Just wanted to say that I finally got my Cappy's GPS to work reliably. As others have stated, there's never a guarantee, especially with how easy it is to get a bad flash of any single software component you build your phone setup with. But here's what worked for me:

Used TalonDev 0.4.4.22 Bigmem, cleared voltage settings, cache and dalvik-cache before flashing and once again afterwards (CWM seemed to give me issues if I didn't do this, not sure why), reboot back into recovery, and flashed PlumbBob's GPS.conf fix V2.0 beta 11.

I rebooted normally and let everything load; went into the phone's Settings menu > Location and Security > enable GPS and enable sensor aiding. Went into AngryGPS to run a few tracking and TTFF tests, and it was super sluggish at first, wouldn't lock, etc. Went into the GPS settings and changed the Operation Mode from "MS Based" to "Standalone", went back to the TTFF test and got a 10m lock in 10 seconds -- Nice. :) Ran this a couple more times: 10m lock in 11, 9, 11, 10s respectively, very nice. Tracking test wasn't quite as spectacular but it held a 30m lock consistently despite being indoors, no nearby window, and Wifi disabled. It wasn't perfect but it was good enough to follow me around the house, which leads me to believe that performance out on the road with a clear view of the sky should be fairly good. I have not attempted Google Nav yet, but as I said, the phone can follow me around on Google Maps.

Users not in North America presumably will have to update their NTP server settings before optimal GPS performance can be had. Presumably -- you really never know with this phone's GPS implementation...
[Captivate Android Development] iXNyNe:
As much as its great that you seem to be seeing positive results, the version of plumbbob you used is meant for froyo and contains more than just a GPS.conf file, I'm not sure if it would cause issues on a gingerbread rom... hopefully rrryan2 releases a gingerbread GPS fix.
[Captivate Android Development] existz:
0.5.1.1 Public Test

Changelog since 0.4.4.22

- updated to xxjvs initramfs contents

- reverted usb mass storage speed hack

- fixed some cflags for hard float optimizations

- updated to linaro 4.5 (GCC 4.5.4) 2011-08 toolchains

NOTE

This is for JVS, it has not been tested on others, so wifi may/may not work on older versions

So it seems wifi works fine on older versions as well
[Captivate Android Development] reinbeau:
It has been posted in the Plumbob GPS thread that it is definitely not for Gingerbread.
[Captivate Android Development] TheSoaresan:
Wifi on 0.5.1.1 works like a boss on mosaic6
[Captivate Android Development] tmng95014:
I want to try this on Continuum 6.2.1 which is JVQ based. Is there any down side besides Wifi? or perhaps it is safe to stick with 0.4.4.22?
[Captivate Android Development] existz:
Everything should work fine except wifi, which may or may not work..i have not tested it.. there was some changes to the way wifi would be called in the init.rc function, so i don't know if it will work or not on anything besides JVS.. its about a 50/50 shot.. but everything else is fine and hasn't been changed
[Captivate Android Development] tmng95014:
0.5.1.1 worked fine on Continuum 6.2.1 which is JVQ based. I tested browser and rebooted several times with Wifi on without reboot (which happens some time in the past). I am using KC1 modem. Signal and speed look normal.
[Captivate Android Development] existz:
Good good.. anyone else able to confirm? once a few ppl start reporting alls good, ill update the post saying it works on older versions as well
[Captivate Android Development] Holmes108:
Yep, haven't done any extensive speed tests or anything, but I have full Wifi bars, and visited several websites and it seems as zippy as normal. (on 6.2.1)
[Captivate Android Development] Reynaldinho111:
This is bull**** :( My cappy died so I picked up an infuse, no more talon goodness for me :(
[Captivate Android Development] Dungeon47:
Works fine so far, including wifi on Serendipity 7 with JL3.

Sent from my Android using the power of Greyskull.
[Captivate Android Development] nappent:
0.5.1.1 is working ok on Apex 9.3. From the status bar I turn it on and off 5 times in a row (testing) and then the Wifi start to show "error" in the settings screen. Took another 5 attempts to get it to work and connect to my network... but no system reboots so that's good.
[Captivate Android Development] baghera1979:
Ran talon 5. 1 on watsa's JVS ROM and had no problems. Running good so far on continuum 6.2.1 using new talon as well
[Captivate Android Development] existz:
Yea that was fixed awhile back, well more of a band-aid instead of fixed...instead of wifi reboots it will just error out now..usually can be turned back on in settings menu. But with the init.rc function changed for wifi, i did not know if wifi would still work or not on older versions..kind of like how it was changed with JVB to JVH (i believe).. and how pre-JVS kernel wifi does not work on JVS, so wasnt sure if JVS wifi worked on pre-JVS rom
[Captivate Android Development] fuloplori:
No issues so far whatsoever with the new talon build running on SensatioN (jvq). WiFi behaves the same as in pervious vs. Tested dropdown WiFi toggle 10+ times repeatedly and had no errors or any reboots. Gj existz :)

Sent from a captivated SensatioN
[Captivate Android Development] Sqb:
No issues on continuum. Thanks for another great release existz.

true excellence!

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] electroau:
on mosaic 5, no problems

Sent from somewhere using something
[Captivate Android Development] jdogg21:
No Issues on 6.2 Continnum
[Captivate Android Development] cuticuti:
on my captivate, when I charging i saw frequency may attempt to use 1200Mhz

may be very hot when charging

i'm using new talon 0.5.1.1 with apex 9.3
[Captivate Android Development] smully1:
Does bigmem still break 720p video?
[Captivate Android Development] Kyuta Syuko:
No issues with 5.1.1 here. The brightness change on unplug seems to be gone too.
[Captivate Android Development] irishvandal:
grrrr,

wh tonight exists? i got a freakin test tomm morning. lol.

guess i will throw it in the MOD folder on the Cappy and see what happens.

thank the geek god for CWM back-ups. lol

i have retracted my offer. i will be waiting for the fresh Cappy goodness of Pinnacle JVS to mature and let you iron some of your kinks out. After that, if it works out how i just read, I will be a JVS bb for life. Cappy BL with Cappy Kernel with a Cappy ROM, for a Cappy to a Cappy. Freakin Captivate me already. lol.

About time 897'z could stand on there own again. Thanks for the tit 9000, but Daddyz home now, lol.

tnx bro for all the hard work.
[Captivate Android Development] johan8:
In order to squeeze a few more MB, need to break 720p memory space.

It is always break 720p video in bigmem.
[Captivate Android Development] pikachu01:
If you're using 1.2GHz version, some apps may climb to 1.2GHz (even when your screen is off). The problem is with the app, not the kernel.
[Captivate Android Development] reinbeau:
Is this why I can no longer watch YouTube videos in my browser? I have to go to the YouTube program to watch anything now.
[Captivate Android Development] RTBee:
What's the default setting for watching YouTube videos in your browser? I have mine defaulted to the highest res, which can be 720. If you've got big mem version then it may not be downgrading the res automatically. Might be posssible to change default to something lower??
[Captivate Android Development] shane87:
No, bigmem does NOT affect video playback. It only affects video recording. The camera has to have a completely contiguous chunk of memory to work properly, as does the modem. The only way for the kernel to guarantee that those chunks of memory are contiguous is to set them aside at boot time and not let them be used. That is why we have 340/353(bigmem) mb of ram available, even though the phone has 512mb memory installed.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] pulsorock:
I'm using TalonDEV 0.4.3 (TalonDEV-0.4.3-1200-BIGMEM-CWM3) with Serendipity VII Build 2 and I love it. Love the speed, love the colors. However after a couple of days running it starts getting really slow, up to the point that is almost impossible to use it. Usually gets resolved with a phone restart, but was wondering if anyone have had this problem too.

I'm using ControlFreak 0.5b to manage the OC. I have the CPU Scheduler in noop, Max CPU to 1.2 Ghz, Scaling Governor to ondemand. I also have all CPU states selected.
[Captivate Android Development] reinbeau:
I think this is an Android drain bug. I have to restart my phone also, although I have to say it got a lot better on this kernel.
[Captivate Android Development] pulsorock:
The thing is that I have never experienced it as extreme as with this combination after couple of days running. I've had this phone for one year, and tried several roms/kernels. And really like this combination, until it starts getting so slow.

Edit: I'm going to try the new test version posted recently to see if I got any improvements.
[Captivate Android Development] pikachu01:
Try updating to the latest test version, 0.5.5.1.
[Captivate Android Development] Holmes108:
That's interesting, I'm the exact opposite. My browser used to go to the youtube app, but now it does it in the browser, and I actually much preferred the old way of using the app.

I wonder what has caused the change (for both of us). I'm using Opera Mobile, btw (and always was).

Edit: Oh wait, I think I misunderstood you. You have to manually go and USE the app? That's no good. What I meant was that when I used to click on the video in my broswer, it automatically played in the app.... but now it's playing embedded in the page, like on a desktop.

Are you sure you still have Adobe Flash installed from the market?
[Captivate Android Development] RTBee:
Yep! I have to agree with you, I thot it went both ways, but you're right it should not effect playback only recording. Sorry for the brain fart :o
[Captivate Android Development] reinbeau:
Yup, I do. Everything is the same except this kernel....maybe I should uninstall and reinstall and see if it fixes it....
[Captivate Android Development] kitkitfok:
Noise cancellation function is relative with kernel or rom?

Will you delvelop KH3 (have Noise cancellation function rom) kernel?

I want to use this function. :D
[Captivate Android Development] shane87:
Audience chip (noise cancellation) is kernel dependant. You MUST be running an i897-based kernel, such as kh3. Unfortunately, kh3 sources have not been released, so there is very little, if anything, that kernel devs can change with kh3.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] existz:
Its in the kernel and possibly modem, we do not have sources to port it to i9000 source. As for KH3, same thing, no sources...without source code i cannot do anything

1+ shane87 ^^
[Captivate Android Development] Kyuta Syuko:
I was doing some research about ways to increase the file size limitation on what can be downloaded from the market on our phones (30Mb as most know) and I came across this thread which I thought was interesting.

Though what I want to point out that I found even more interesting and was wondering if existz knew anything about is on page 5 starting at post 45 where the guy brings up the limitation down through to post 47 where they talk about the kernel changing the location the market saves the downloaded app to.

That being from /cache to /data/cache which supposedly eliminates the restriction (with exception to the space available on the phone).
[Captivate Android Development] iXNyNe:
Moving the cache mount the way you mentioned is basically accomplishing the same thing the virtual cache fix in my sig accomplishes, but like you said it is only limited by the available space on the phone where the fix in my sig has a specific size that can easily be increased as needed (which in my opinion is a form of control to keep the cache from overrunning our phones if its not cleaned)

The fix you recommended also comes with the same downfall pointed out about the fix I use which is that the built in 30mb cache is then wasted because its still in place just not being used (to which I replied "I can spare 30mb")
[Captivate Android Development] iXNyNe:
*separate post because this is a different idea*

Would it be possible for a script or an app to adjust your governor settings based on your battery level?

Ex: the lower your battery level gets the more conservative your governor becomes as far as scaling?

Maybe this is something better accomplished by lmk settings?
[Captivate Android Development] Kyuta Syuko:
Yeah but as I posted in that thread I keep getting a mount error when trying to mount the Virtual Cache, and according to the posts in the thread I referenced it's something Samsung had supposedly caked into the Froyo kernels when Google started letting files larger then 30 Mb be added to the market. If that's true I wonder where it went. Though I doubt the truthfulness of that since they could just release a pit file with a resized cache. Which I'm thinking about experimenting with. Already did the research and hexed the pit file but I have no need or want to reflash my phone to test it...
[Captivate Android Development] IDoMy0wnRacing:
Working well on Continuum v6.1 - JVQ

No issues... yet LOL
[Captivate Android Development] foit:
Using 0.5.1.1 on Apex 9.3, it comes to a crawl and starts lagging after a day, but I'm glad to see my charging bug disappear and the TW4 launcher stop crashing a dozen times per day when I was on DC 3.1.
[Captivate Android Development] Kyuta Syuko:
Have you tweaked Memory Freak any? Try the Nexus S LMK Settings and tweak the ZRAM and Swappiness. Various people have had different experiences with different settings. Maxing both seems to work well for me.
[Captivate Android Development] pikachu01:
Try this setting:

Hidden App - 48

ZRAM - 160

Swappiness - 50

It will still lag eventually, but the probability of that will be lesser. (from my own testing)
[Captivate Android Development] topiratiko:
Click the link in my Sig.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Kyuta Syuko:
Yes I use topiratiko's tweaked settings myself with the exception of Swappiness which I have maxed out like I said (where as topi's is at 90) and they seem to work quite nicely.
[Captivate Android Development] IDoMy0wnRacing:
pikachu01,

Where do you go for the: "Hidden App" modification?

I am currently using:

LMK - Nexus S

ZRAM - 160

Swappiness - 50

I don't see where to adjust Hidden App. :confused:
[Captivate Android Development] Sqb:
Hidden app is only with talon settings. Kodos set it up custom for existz.

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] Kyuta Syuko:
Or if you're feeling "brave" you could just edit the /system/etc/ram.conf file yourself.

Would be nice if who ever is working on the Memory Freak app (not really sure who's doing it) would add in a custom LMK option for more advanced users that would allow them to tweak more of the settings and also show the settings for the other LMK options.

Like have an "Advanced Options" button/link to a new window or something that just displays the LMK settings for preset options and allows you to tweak them when custom is selected.
[Captivate Android Development] IDoMy0wnRacing:
Before MemoryFreak came out, I did take the advice of others and edited the /system/etc/ram.conf file. But MemoryFreak has made minor adjustment so much more easy. LOL

There were recommendation for scripts (S98screenstate_scaling and S98system_tweak ) to be added at one time (0.4.4.22 era). Would they be beneficial to 5.1.1?

(ref: Modded Platypus Scripts for Talon by Zach).

If so, where does one Change the file permissions to 755/(rwxr-xr-x)
[Captivate Android Development] pikachu01:
Yes, platypus scripts is still beneficial for 0.5.5.1.

You can use File Expert:

Long press on the file > File Operations > Permissions > Tick it according to

r - read

w - write

x - execute

http://en.wikipedia.org/wiki/Chmod
[Captivate Android Development] topiratiko:
Has anything been discovered concerning the memory leak?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] shane87:
I am the dev behind memory freak. I just sent existz an update for memory freak. The update has a few minor string changes, requested by kodos96, and I also increased max zram size, again per kodos, plus loading the "Talon" settings from ram.conf.default so that memory freak is future proof, since kodos will change the defaults in ram.conf.default any time he makes changes.

As far as an "Advanced Options" screen, I had the same idea about a month ago and brought it up to kodos. Kodos was less than enthusiastic about it, and I understand why, and agree with him after he explained his reasoning to me: Memory Freak is a way for users to adjust ram.conf without falling into traps that can happen very easily when playing with oom/low memory killer settings. By adding advanced options, I would re-open the pit falls that Memory Freak is designed to prevent. When it comes to memory settings and playing with ram.conf, I deffer to kodos, since the lmk settings and ram.conf file are kodos' design.

If you want to mess with advanced settings, the best option is to manually edit ram.conf, although note that changing ram.conf manually is potentially hazardous to the performance of your phone, and certain changes may make memory freak have odd/undefined behaviour, since it determines your curent preset via certain values set in ram.conf.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] pikachu01:
I think I found out what would cause memory leaks at the end of the day.

If doing:

Solves this problem, it's due to vfs_cache_pressure being too low and dirty_ratio being too high.

With that, I've updated the system_tweak yet again, with this knowledge by making the VM settings more aggressive, which will trigger the memory leak faster. I made this so, as there's a workaround to clear the caches when it gets full.

Having a low vfs_cache_pressure and a high dirty_ratio will save battery and make your device perform faster at the cost of higher RAM usage.

You can read more here:

http://people.redhat.com/nhorman/papers/rhel4_vm.pdf

Updated Zach's scripts:

http://xdaforums.com/showpost.php?p=17400617&postcount=3147
[Captivate Android Development] iXNyNe:
So do these new scripts automatically drop caches? Or do we still do that via terminal?
[Captivate Android Development] pikachu01:
You still have to do it via terminal. Or you can create a cronjob to do that every day.
[Captivate Android Development] no driver:
I'd suggest that something about Memory Freak being included with the kernel be added to the OP.

I haven't been paying close attention for a while, just installing the latest version of Continuum, but my phone was slowing down after a couple of days of uptime and I saw folks in this thread talking about adjusting settings, and spent a decent amount of time searching for the .apk before I realized that it was already on my phone.
[Captivate Android Development] topiratiko:
How? What command in terminal to drop?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] pikachu01:
Do this:

echo 3 > /proc/sys/vm/drop_caches

You can install script manager from the market to make this into an icon that you can click so that its easy to do it.
[Captivate Android Development] zacharias.maladroit:
if there are issues please report those in my kernel thread or notify me via PM

otherwise I won't know of any fixes that need to be applied

thanks !
[Captivate Android Development] topiratiko:
Permission denied. Lol im not important enuff

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] pikachu01:
You need to be superuser to do that :)
[Captivate Android Development] topiratiko:
But i am. ?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] pikachu01:
Umm, type su before entering the command. :)
[Captivate Android Development] topiratiko:
Typed su, space then command still denied

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] pikachu01:
No,

Type

su <enter>
echo 3 > /proc/sys/vm/drop_caches<enter>
[Captivate Android Development] topiratiko:
When hitting enter it just went to the next line. Did that do it?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] existz:
Most likely yea, you can do...

cat /proc/sys/vm/drop_caches

And it will display whatever it is set to, so if its the same as what u typed then it worked
[Captivate Android Development] topiratiko:
existz after doing that it shows '3' im assuming thats echo 3 from command line. thanks for all your guys's help
[Captivate Android Development] pikachu01:
Yeah, and when you do a cat, it will display a 0 again. It's normal, that means your caches are cleared and all the uncommitted data are committed into your NAND disk.

Let me put it into code so that it's easier to see.

1. Go to terminal emulator

su <ENTER>
free <ENTER>

This will show your buffers and free memory.

My example:

total used free shared buffers
Mem: 348548 340280 8268 0 1320
Swap: 163836 47292 116544
Total: 512384 387572 124812

Then do this:

sync <ENTER>
echo 3 > /proc/sys/vm/drop_caches <ENTER>

You will get:

3 /proc/sys/vm/drop_caches

Type:

free<ENTER>

And you'll realize that the buffers will reduce and free memory will increase, like this example:

total used free shared buffers
Mem: 348548 305212 43336 0 88
Swap: 163836 46804 117032
Total: 512384 352016 160368

That means it's done.
[Captivate Android Development] topiratiko:
after the su command i get:

#

after cat command i get:

3
[Captivate Android Development] existz:
If you echoed 3 to it, then you get 3 when you do cat, then it worked ...for ****s and giggles echo 2 to it, then cat it, it should show 2... then of course echo 3 back ..just to see if its changing

When you echo 3 to drop_caches it clears pagecaches, dentries and inodes, you can do "free" before and after to see if it cleared

Echoing "1" will clear pagecaches, "2" will clear dentries and inodes, "3" clears all... when you "cat" it, your not actually checking cache, etc, you must do "free" before and after if u want to see if it's clearing it ...
[Captivate Android Development] topiratiko:
lol battery is DONE and my chargers at work. DOH! lol will try at work later
[Captivate Android Development] Thunder22:
@existz...just troed the echo 2 and 3 commands as well as the cat line after each. Each results in it saying a 3 no matter if i do echo 2 pr 3

Edit: disregard above. It did list 0 when i catted the echo 3 line. Before I didnt reboot after fixing permissions on the files. Sorry.
[Captivate Android Development] justin860:
I just want to say that I love how the colors come out with your kernel I will be donating to you soon. Keep up the good work
[Captivate Android Development] crazililazn:
Just to clarify, can this be flashed on roms with captivate bootloaders?
[Captivate Android Development] fuloplori:
yep, i9k roms that is

Sent from a captivated SensatioN
[Captivate Android Development] crazililazn:
so it won't work with a KH3 based rom?
[Captivate Android Development] shane87:
No, and the major benefit of kh3, or any i897-based rom, the audience chip support, would not work with this kernel, even if it did work on those roms.

Sent from my SAMSUNG-SGH-I897