yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shane87:
I have been wandering about this issue. This is the third or fourth time I have seen someone that does not have /system/etc/ram.conf and so memory freak does not work.

For anyone who opens mem freak and everything is blank, do me two favors, please:

1. Check in /system/etc for ram.conf

2. Check in /bin for ram.conf.default

If you DO NOT have ram.conf, follow this method to check that you have the correct busybox version installed:

1. Download stericson's busybox installer from the market

2. Use it to install busybox 1.17.1 in /system/bin

3. Go to /bin, /sbin, and /system/xbin and delete any instances of busybox.

4. Reboot

5. Check for ram.conf again.

And if you do not have ram.conf.default, then you probably need to reflash, as that file is created when you flash the kernel.

The ram.conf setup is handled by runparts at boot time. Certain busybox builds do not have runparts. If you don't have run parts, the script that recreates ram.conf when necessary, such as when you have deleted it, or after a fresh rom flash, will not run, and ram.conf will not be created.

For thise interested, the init script calls a script located in /bin, called post-boot.sh. This script in turn runs some clean up scripts, and also runs a few programs to check for ram.conf, and create it from ram.conf.default if it does not exist. The post-boot.sh script is also responsible for calling init.d scripts, and it calls all of these functions using runparts. Hence, no runparts, no ram.conf, no options in mem freak, and, also, no init.d support.

This is all just my take on how this stuff works, from studying the files in /bin, and reading through some of the init scripts, including post-boot.sh. If I am wrong, feel free to correct me.

And I hope the steps I outlined above help someone!!

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] tmng95014:
Reflash Talon and still MF blank. I think I give up here. Thanks for trying to help.
[Captivate Android Development] geokilla:
Memory Freak did not work for me prior to flashing the oram CWM file. I did everything that I quoted here, except for the parts in bold. My dad's Captivate however, worked fine. We were both running the same ROM, modem, and kernel.
[Captivate Android Development] shane87:
Hmm, very strange. Have you always had the same roms on the two phones? Because some roms place busybox in sbin, and if a newer rom does not remove that copy of busybox, amd that copy does not have runparts, it can cause problems. I know that when I first made the jump to gb, the busybix issue was a HUGE pain in the a**. And, with some roms copying a version of bb 1.18.4 that did not have runparts to sbin, even flashing a new rom that included a working busybox did not always fix the issue. Again, this is all my understanding of the issue, and there may be some deeper problem that has not beed found yet. However, if you have busybox 1.17.1 and ram.conf.default is located in /bin like it should be, then upon a reboot ram.conf SHOULD be placed in /system/etc unless it is already there.

I hope we can get to the bottom of this soon, I have a new version of mem freak coming up soon, just a few more things to future-proof and it will be ready.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] -Thrive-:
I'm on Busybox 1.18.4. Updated it a while back using the TIBU update function. I have no problems with MF.
[Captivate Android Development] tmng95014:
I installed busybox 1.17.1 in /system/bin as you suggested and the problem is fixed. MF is working now and retained setting across boot. I tried to delete busybox from /bin but the file system is read-only so I leave it there. I think it is probably harmless. Previously I installed busybox 1.17.4 in /xbin. I leave it alone also. there is nothing in sbin. Thanks for the suggestion.
[Captivate Android Development] BitteredBro:
I'm having an issue with de new .22 1200 BIGMEM + UGKG3 Modem. After a couple of seconds the audio from my side goes off. If I use JVR everything works well, but the reception is crappy in my home. It's mandatory to use JVR?
[Captivate Android Development] shane87:
No problem, I'm glad you got it working. As a side note, you can mount any of the filesystems as read/write if you have a terminal emulator or root explorer. With root explorer it is a little easier, since all you have to do is go to the folder you want to remove something from, and there will be a button at the top that says "Mount RW" Pressing that button will allow you to delete the file you want, then you can click the button again to mount as read only.

In a terminal emulator, you can type "su" to get root access, then type "mount -o remount,rw /" to mount the root filesystem as rw. After you delete the files you want to remove, launch the terminal emulator again, type "su" again, then type "mount -o remount,ro /" to put the rootfs back to readonly. And you can do the same thing for but replace "/" with "/system" to mount system as rw then back to ro. And mounting the root fs as rw will also make /sbin and /bin as rw.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] tmng95014:
Thanks for your help. I try to issue this command under terminal emulator yesterday but it seems the system does not recognize the mount command. I got the mount command syntax. After tried this a few times last night, I gave up. There is probably something not right with mount command due to busybox issue... I use Super Manager and it has issue to delete also.... Don't know whether using root explorer will make any diff...
[Captivate Android Development] existz:
The busybox in bin is actually generated by the kernel, kodos96 went through and setup most of the initramfs so he might be better to explain this, but i think he has it setup where during part of the boot process it will use busybox is bin, then at a certain point it switches to the one rom side. So might be best to leave the one in /bin if its not causing any issues
[Captivate Android Development] geokilla:
Yup always, up until two days ago. Now I'm on Apex while he's staying on Mosaic. I encountered the same problem on Apex as well so it's making me think that it might not be a ROM issue or busybox issue, but something else. Could be a Talon issue, or it could be a MemoryFreak issue. It could also be a software issue where when I went to Gingerbread stock, it missed something while it got everything for my dad.
[Captivate Android Development] shane87:
Yrah, I have a busybox in /bin, /system/bin, and /system/xbin. The bb in bin is the one used by the kernel. The bb in /system/bin is the rom supplied one, and the one in /system/xbin is a symlink, I am guessing to the bb in /system/bin, but I'm not sure as I haven't checked.

Edit: The bb in /system/xbin is a symlink to /system/bin/busybox.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] topiratiko:
What determines what busy box you have and y do only some have this issue? Just curious

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] rajendra82:
Talon is based on i9000 JVQ source code. You can't mix it with a Captivate modem like UGJK3. You have to use an i9000 modem with it. If you want to use a Captivate modem, use a Captivate based kernel like the one that is included with Cognition.
[Captivate Android Development] topiratiko:
Kg3 is i9000 aint it?

Kh3 is i897

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] shane87:
The version of bb you have depends on what version is included with your rom. Also, if a previous rom installed bb to a place that does not normally get overwritten on a rom flash, such as /sbin, you may still have the bb provided by an old rom. To find out which version your phone is using, launch a terminal emulator and type "busybox" That will call the first version of busybox found in your PATH variable, and list some of the functions built in, along with the build version of that busybox. If it says version is 1.18.4, you likely will have issues with busybox, since the 1.18.4 version did not have runparts built in. You can check to see if you have another version of busybox installed in a different location by typing "/system/bin/busybox", "/sbin/busybox", "/system/xbin/busybox", or "/bin/busybox" and then comparing the versions.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] topiratiko:
1.19. Is that what were supposed to have?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] shane87:
No, I think kg3 is i897 as well. I'm pretty sure that all of the Uxxxx builds are i896/i897.

Nevermind, I just proved myself wrong, lol. UGKG3 is i9000 based. I'm not sure what all of the letters stand for, other than they do somehow specify the build time and date. I know that the "k" in ugkg3 specifies that the build happened in 2011, and a "j" in that spot means a 2010 build. The next letter specifies the month (not sure of how the letters line up with the months) and the number at the end is, I believe, the build number, so ugkg3 would be the third build of month "g", which I think means july, since the i897 uckh3 was built in august of 2011, so "kh" means august, 2011.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] shane87:
1.19 is what I have (Continuum 6.1) and it works great.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] topiratiko:
Negative. Kg3 is in fact I9000. Just checked modem thread. Not tryin to be a ****. :D

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] shane87:
Its all good, I just did the same thing, and edited my post, striking out the incorrect info.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] topiratiko:
I just flashed it and its actually pretty loud. Louder than Jvr. Give it a shot lol.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] BitteredBro:
As you said, a i9000 modem most be used with a i9000 Kernel. I'm not using UGJK3 but UKGK3. Some other people are using it too. Thing is that on a earlier version of Talon it used to work for me and now it dont.

Maybe it's just happening to me...
[Captivate Android Development] topiratiko:
KG3! Too many letters its getting outta hand

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] tmng95014:
I have been using KC1 for a long time and have no reason to switch.
[Captivate Android Development] iXNyNe:
wouldnt that mean that jvb, jvh, jvq, jvr, etc were all built in 2010 because of the J? and the V would mean they were all built the same month?

that doesnt seem quite right too me, unless for some reason these builds use a different naming scheme, but jvr and kg3 are both i9000 builds i thought?
[Captivate Android Development] shane87:
Well, this is how it was explained to me by haloruler64 on the Cog5 thread. The K/J denotes 2011/2010, the V would denote month, and the last letter/number denotes which build, i.e. 1st, 2nd, etc.

I see what you mean though, I am pretty sure that jvb, jvh, jvq and jvr were all built in 2011. And I am pretty sure that they were NOT built in the same month. It may be that the i9000 builds use a different numbering scheme. I just know that it was explained that way to me on the Cog5 thread, like I said above.

And yes, jvr and kg3 are i9000 builds.

Sorry to ex for getting off topic! Back to the regularly scheduled programming.

Edit: It also occurred to me that the numbering scheme I described above may only be in use on Uxxxx builds, such as UCKC1, UGKG3, etc. JVB, JVQ, etc use the XX scheme, i.e. XXJVB. As far as the difference between Uxxxx and XXxxx, I have no clue.
[Captivate Android Development] morpheus_1987:
I love what's been done with the battery indicator when the phone has been fully charged and starts draining. Now that it shows the true %, I have a better idea of the battery consumption during idle (e.g. overnight) as opposed to during the day when I would periodically check my phone.

I remember reading that the phone should charge again if it dropped to 90% while on the charger after having been fully charged once. I noticed last night that mine had dropped down to 80% before it started charging again. By the time I woke up, I only had 86% charge. Need every little % I can get as I've been having some battery drain issues with Apex 9.2 which I'm trying to figure out with Battery Monitor Widget Pro and BetterBatteryStats.
[Captivate Android Development] mpencexda:
Mine charges just fine.. Hits 100 drops down to 98 and then charges back up. Its always somewhere between 98-100 no matter how long its on the charger.. I made sure and re-calibrated my battery and wiped battery stats when I changed to the new kernel though.
[Captivate Android Development] iXNyNe:
For me (using talon 0.4.4.22 with ondemandX and apex 9.2 as my rom) if I leave my phone plugged into my computer tethering overnight I wake up with like 60% battery and a warm phone.

If I don't tether or hotspot I wake up usually with 98-100% battery.

This tells me that either my phone is recharging below a certain threshold but only when tethering isn't on overnight (unlikely) or that nothing really sucks battery life with my current setup other than when I leave tethering on and that my phone idles like a champ.

So my recommendation to anyone consistently waking up to a phone that isn't charged to at least 95% is you should look at what apps you have installed and make sure nothing is sipping away at your battery life.

I have an app installed from the market called autorun manager that lets you disable apps from running on boot, but I read somewhere not to use this app to disable apps for some reason, so all I use it for is to see what runs and then uninstall it through titanium backup if I don't actually use it. Example: swype, Samsung apps, etc. So I'm slimmed down a bit.

Also do NOT sign in to latitude in the maps app, it causes battery drain just being signed in regardless of telling it not to report your location (that's kinda old news).

Anyway, thanks ex for the great work, I'm really looking forward to your oc module.
[Captivate Android Development] unknownyello:
i was having issues with memory freak showing up blank as well. follow these steps, delete all instances of bb from the 3 locations, install the bb in /bin folder, reboot and there was no ram.conf in the /etc folder. now i can copy and paste a ram.conf file in /etc folder and MF would work. :)

running dlev 5.0 btw.

thanks
[Captivate Android Development] tmng95014:
+1 same here. Yesterday phone recharged to 100% drop to 99% then came back up to 100%.
[Captivate Android Development] daverup:
This does seem to help with charge issues.

My only problems seem to occur when I've flashed and not re-calibrated and wiped battery stats.

With the re-calibrate and wiped stats my battery charges normally, even with the charger still connected after full notification.
[Captivate Android Development] demarton:
no charge bug happens on captivate official UCKH3, nor UCKF1 IIRC.

Charge to 100%, use it, un plug, still shows 100%, it's been like this for about a week on UCKH3.

too bad source is not out yet on this beta to be integrated by dev.
[Captivate Android Development] iXNyNe:
I think kh3 source would put a quick end to reoriented i9000 roms and kernels on the captivate :)
[Captivate Android Development] existz:
Well, maybe, maybe not... when KB1 source dropped barley anyone picked it up and i9000 kernels were still built. I still see i9000 kernels being built and used even if kh3 sources dropped, just for the soul fact of more work/customization..etc.. etc is being done on i9000 roms, people like more choices
[Captivate Android Development] morpheus_1987:
I had 0.4.4.22 on Apex 9.1 for a while and everything was OK. 9.2 seems to be causing problems with quick battery drain for me and I can only narrow it down to GTALK ASYNC CONN with BetterBatteryStats (or Google Services from Android Settings -> About Phone -> Battery Use).

What's weird is Battery Monitor Widget Pro shows idle was fine from 7am until roughly 10:30 am for the past 2 days and then the drain picks up, however the phone just sits idle in my pocket at work until Noon hour for lunch.

Not sure what app setting could have changed when I flashed from Apex 9.1 to 9.2 but I'm tempted to Nandroid back to my 9.1 backup.

Can't live without Voodoo sound and color. Somehow the RGB colors in this kernel for voodoo was better than the Froyo KB8 Kernel. I could never adjust it right, but the default in Talon is fantastic. Love your work, existz.
[Captivate Android Development] iXNyNe:
Kb1 is 2.2 though, by the time sources dropped we already had reoriented 2.3.x i9000 stuff. Kh3 is 2.3.4 so it would bring captivate users up to speed and then it would just be a matter of porting in the customizations from i9000 stuff.

Not to say I don't love the i9000 stuff I have right now, but I wouldn't mind having a working audience chip, I would miss hsupa, but I can live without it, and as for the customizations you mentioned may I ask what specifically you are referring to? Only thing I can think of that I haven't yet seen on a cappy rom is TSM menu and jkays app, but they should be relatively easy to port over.
[Captivate Android Development] watsa:
KF1 dropped almost 2 months ago. Have you seen any MOD ported so far? I9000 roms are modded by captivate, Vibrant and I9000 devs, The dev community is much larger. By the time all these features will be ported to a captivate ROM, I9000 roms will have more features added in them
[Captivate Android Development] mkr14:
The source for KF1 was never released correct? You are very limited with what you can do with the KF1 release from my understanding.

EDIT: Also, the i9000 has been way ahead of the curve in terms of having the latest Android versions available. Everyone wants the latest and greatest, thus everyone is using i9000 based ROMS.
[Captivate Android Development] Kyuta Syuko:
As far as I can tell the main reason there are more I9000 based ROMs rather then I897 based ROMs is because the I9000 software has always been ahead on which version of Android it was built on, and who doesn't want the latest and (hopefully) greatest?
[Captivate Android Development] geokilla:
Later does not always seem better as you said. However I am a I896 Captivate user, which according to the community lacks the audience chip. Why should I run I896/I897 ROMs when there are better ROMs out there or ROMs that are themed to my liking? Only benefit I recall from running I896/I897 ROM is the noise cancellation, which I haven't seen again since I ditched stock Rogers Eclair. Even FireFly didn't have it despite being based on Rogers Froyo.
[Captivate Android Development] existz:
Its not really about the latest and greatest, but more about dev support.., when i897 gingerbread source drops, i bet there will only be 2 maybe 3 devs/chefs that do anything with it.., compared to the devs/chefs working on i9000 roms from captivate, vibrant and i9000 forums.. Talon will remain and always will be i9000 source based (just like Onix was for froyo), but that doesnt mean i wont merge over some stuff from i897 source, it will def help us out in one way or another regardless
[Captivate Android Development] mrhaley30705:
Also, nearly 4 months of development has already been put into I9000 roms and kernels for GB. To start over simply because of new source would be a giant step backwards. I don't think any developer would be willing to throw away 4 months of hard work.
[Captivate Android Development] Kyuta Syuko:
Which just goes more into what I was saying about the I9000 always being ahead.
[Captivate Android Development] pikachu01:
Existz normally do a "diff" on the source codes like Infuse to see if anything new is added onto them and then cherry picks relevant codes that can be implemented into Talon. Hence we will get the best of both worlds :)
[Captivate Android Development] iXNyNe:
Sorry to have taken the thread so off topic (again). I see the points being made and I'm swayed towards the i9000 side now :)

Anyway back on topic I've had 3 random reboots today. One mid day battery was probably around 50%, I was trying to unlock the phone, and then two a few minutes ago both while on a phone call and battery has been under 20%

I'm using 0.4.4.22 ondemandX and apex 9.2 both flashed the day they released, and I have never seen this issue before.
[Captivate Android Development] pikachu01:
So far random reboots are due to UV/OC. Did you UV/OC?
[Captivate Android Development] iXNyNe:
Oc 1200

UV 150, 125, 100, 75, 50 in order from 100 to 1200. This has always been stable on my device through MANY tests on each frequency.

My process is to start at 100 and limit Max frequency and disable higher states, UV, run quadrant to ensure it completes without issue, run stability test for at least 20 cycles, after finding stable UV move up to next frequency and repeat, don't jump voltages too far like -100 on 400mhz and then -25 on 800mhz cuz voltage jumps are bad.

Using that method and mentality I ended up with an extremely stable set of UV values for my device that has worked perfectly since January (retested every time I've done a major rom or kernel switch most recently from continuum to apex when apex 8 came out I think)

I've had this rom and kernel for 3 days now and it hasn't given me any issues until this evening.
[Captivate Android Development] pikachu01:
Hmmm, I too use the method you've described in your post. Never had a reboot. I've had my fair share of blackscreens though, mainly due to the XDA app. Manually closing (Force Stop) it would solve the issue for me.

Did you by any chance flash any addons/themes or have any scripts in your init.d (just trying to eliminate the usual suspects).

Also, try not UVing/OCing for a few days and see if it happens again. One UV value on a kernel might not work for another.
[Captivate Android Development] nappent:
I would dial back the UV for 100 since the phone most often is running in that range. Personally I don't go any further then -125. Yes my phone can run -150 but I like to add a little buffer to increase the stability. Yes each phone is different but playing it a little on the safe side can help.

Also it doesn't hurt to clear your cache too if you haven't tried that already.
[Captivate Android Development] existz:
If you have lockups and/or reboots, please try running at 1ghz with no OC before posting.. 99% of the time both are caused by unstable oc/uv.. alot of things change from build to build, so the scaling of the CPU can change its behavior, so whatever was stable before (ie -100mV or whatever) ,might not be stable now. If it doesn't happen at stock frequencies and/or voltages, then chances are its unstable and needs to be adjusted.
[Captivate Android Development] RashaMatt:
Ditto here since .21, and before I would ALWAYS get the charge bug (on Serendipity VII).

____________________________________________________________

AT&T Captivate SGS I897, Dlev ROM 5.0, TalonDEV 0.4.4.22, KC1
[Captivate Android Development] mpencexda:
Has anyone played with the modems. I am testing UGkC3 right now and it seems a little better the UGKC1.. Just wanted to see if there was a reason we are using UGKC1 instead..
[Captivate Android Development] nh5:
Picked up a refurb captivate yesterday from the AT&T store went from a build 1008 to 1012 what a difference such a smoother experience. Running Apex 9.2, -100, -150, -150, -175, -200 UV and stable on .22 1200 Bigmem. Got my mem settings to Nexus S and 160/50% anyone find a good mem configuration they've found?

Sent from my SGH-I897
[Captivate Android Development] tmng95014:
I think Modem is depending on the area and carrier. KC1 has been good for me since I got the phone last year. I tried out other modems but always came back to it. I live in Cupertino, California and KC1 is good there, San Francisco, San Jose...
[Captivate Android Development] existz:
Yea i agree, KC1 is a good modem, but all just depends on the area and carrier.. but KC1 seems to be a good overall universal modem