yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mtcarey:
OK, that helps. Look in your /sbin folder (at the root of the file system) and see if there is anything called "mount". There shouldn't be, but who knows? There should only be about 12 files in there total.
[Captivate Android Development] herofmm:
I was an idiot. Thanks a lot.
[Captivate Android Development] Kyuta Syuko:
Ah ok I'll admit I didn't really pay attention to what settings were being talked about...
[Captivate Android Development] kevria:
Oh thats bad :)

I copied the kernel and rom install files from my phone to my wifes, uninstalled swype and swype installer, wiped cache's, rebooted into recovery, installed the rom, rebooted into recovery, installed the kernel, rebooted into recovery, switched Scaling governor to Ondemand and IO to Deadline, rebooted, switched to swype and 20 minutes later her phone was locked...argh. Pulled battery and rebooted and her phone has been ok since.

No I havent switched hardware yet.
[Captivate Android Development] mcala:
Ok first vote I guess. NAY!
[Captivate Android Development] popfan:
Hate to say this, but you are the last of a dying breed.
[Captivate Android Development] mtcarey:
The nays win! For now....
[Captivate Android Development] mtcarey:
I've noticed. The march of progress, and all that.
[Captivate Android Development] robm1911:
We're not a dying breed we're just building for a dying device. Lets face it the cappys days are getting shorter. Most other devs have moved on to other devices. If not for the work of mtcarey (thanks btw) and some other devs still hanging around we'd be stuck at stock kk4.
[Captivate Android Development] mtcarey:
What really killed me was getting a text from AT&T last weekend with a link and instructions for updating to Gingerbread! Sure wish Samsung had released the I897 source code a long time ago.
[Captivate Android Development] robm1911:
Just think where we could be now if they had
[Captivate Android Development] prbassplayer:
I got the text today..... xD
[Captivate Android Development] IDoMy0wnRacing:
I got the same text also... LOL
[Captivate Android Development] nycmon:
How are you adjusting your OC/UV values? I can't seem to make Tegrak ultimate work with Corn 7.06. At this point I am using the 1200mhz OC through the extra settings in CWM since I cant get Tegra to load....

Any help to an alternative or solution would be appreciated! Thanks!

How is your battery life so good with these settings? Lol My settings are almost identical (except LMK@70) and my battery life is ATROCIOUS! Also any recommendations on which stock/system apps/services to freeze for a better Captivate experience? It would be great if I could go more than 3-4 hrs with light use lol :(:mad::(
[Captivate Android Development] prbassplayer:
Use voltage control or set cpu
[Captivate Android Development] kevria:
My phone locked up last night with Scaling at OnDemand and I/O Sched set to Deadline so I switched those back to default for this kernel and turned off BLN for testing.
[Captivate Android Development] storm717:
As mentioned, use Voltage Control app.

My battery life is fine, I can make it through the day plenty of texting/music/apps/twitter and an eBook at night no problem. If you bat is only lasting 3-4 hours then there's something seriously wrong. Check battery usage in Settings and use CPU Spy to see if the phone is actually going into deep sleep. If everything checks out then you probably just need a new battery,
[Captivate Android Development] mtcarey:
This kernel is not compatible with Tegrak. As mentioned above, use Voltage Control or SetCPU apps from Market. And you should be able to go at least 24 hours between charges with any settings, unless you are using the Performance governor. If not, you have a problem unrelated to the kernel.
[Captivate Android Development] RTBee:
Just wanted to say that I've been extremely happy with Corn kernels, since I switched back to I897. I checked out a couple others, but quickly flashed back to Corn. I've left it alone as far as tweaks go and left it rfs as well. My phone works great, runs smooth and has great battery life. I love tweaking it, but with this kernel it seems to be as good as it can be right now. I've tried a few other roms since switching, Fusion was great (still watching them), but I'm back with Illuminance 3.0. It's a great combo. As far as Talon or Samsung, I'd rather not vote and let you do what you think is best! You've not steered us wrong yet. Donation on the way, thanks for a great product and support! :)
[Captivate Android Development] mtcarey:
Thanks... very appreciated! On the topic of reserved video memory, I mentioned the Talon values but didn't mention that the (also excellent) Semaphore kernel values are higher than Samsung's. More reserved memory rather than less. One of the frustrating things about working on these kernels is that so many of these things seem arbitrary, and absolutely nobody comments their code. Even figuring out where these values are used can be a nightmare... makes me really miss Visual Studio and Intellisense!
[Captivate Android Development] aww.W.T.F?:
I paired up 7.0x with legend 3.0 ICS edition, no tweaks, smartass v2 formatted over to ext4 .. WOW , what a difference. Thanks for including what each change will do if you select it, always good not to be blind when screwing with the settings, thanks again for your time and effort to make life for us development challenged people better and donation has been sent.
[Captivate Android Development] kevria:
Whats the default Scaling Governor and IO Scheduler for 7.0a?
[Captivate Android Development] aww.W.T.F?:
[REF][&Tweaks] Kernel Governors, Modules, I/O Schedulers & CPU Tweaks: Siyah & Others Read Posts 1, 2 & 3

4-2ndtwin posted this and some other info on thread page 108.
[Captivate Android Development] kevria:
I have looked at the descriptions of the various params before, I was just wondering what mtcarey put as the defaults for corn.
[Captivate Android Development] aww.W.T.F?:
These are the defaults

init.rc tweak injection: No Tweaks

I/O Scheduler: sio

Scaling Governor: smartassV2

Partition formats: rfs,

The only change I made was reformatting to ext4
[Captivate Android Development] ulupinar:
7.06 crashes

Fist, let me start by thanking the developer for an excellent kernel. I have been happily using version 7.03 with Serenity 6.3 for quite a while. When 7.06 came out, I decided to give it a try.

As soon as I loaded it up, I experienced the crash issue some people mentioned. It crashes very regularly about 5 minutes after the phone boots up. Strange thing is that, when I went back to 7.03, it exhibits the same behavior. I had go all the way back to 7.0A to eliminate the crashing. But, the web browser is very problematic. On a slightly complicated web page (e.g., yahoo finance, desktop view), it becomes very unresponsive to the point that I have to reset the phone.

My be there is some problem with the tweaks I used. Is there a way to erase all the tweaks? I am using ext4.

While talking about problems, I would like to report one more: The power button on my phone stopped working completely about 2 weeks ago. I do not know if it is a HW or SW problem, I am thinking it might be a HW problem, as it does not work even in clockwork operation. Would anyone know anything about getting this button to work. Currently, I have installed a slew of apps to replace the power button functionality.

I appreciate any help you can provide especially on the crash of 7.06 kernel.

Thanks

fatih
[Captivate Android Development] mtcarey:
Ondemand and SIO for 7.0A.

SmartassV2 and SIO for 7.06.
[Captivate Android Development] mtcarey:
Try deleting the entire /system/etc/cwm5sc folder and reboot. That's where all the settings (tweaks) are stored and maybe something's messed-up. It will be re-created with defaults. Don't worry about partition format... it will be auto-detected.
[Captivate Android Development] aww.W.T.F?:
Ah chit, my bad, I had read those defaults on page 109. and I assumed, we know what that does.
[Captivate Android Development] ulupinar:
Thanks for the help. Unfortunately, with 7.06 my phone still crashes after about 5 minutes of booting. I wiped cache partition and dalvik cache. It does not seem to help.

I am testing the 7.03 now. If that does not work either, I 'll go back to 7.0A, without any overclock :(

Fatih
[Captivate Android Development] IDoMy0wnRacing:
I had the same problem with the power button not working. I corrected it by flashing all the way back to stock (froyo stock) and wiped and formatted everything… as if you were going to turn it in to AT&T for repairs

And at stock, the power button started working again.

Then flash the custom ROM and Kernel of your choice and enjoy.
[Captivate Android Development] rayburne:
I don’t do much with oc/uv settings so won’t surprise me if this is user error but, when going into recovery and turning 1200 MHz Overclock off, CPYspy still shows the phone cycling at 1200MHz.

I am making the change from recovery here:

Reformatting, tweaks and more> Tweaks and Settings> Misc. System toggles> Overclock to 1200MHz = Off

Running Suarom Rom with Corn 7.06, Installed via CWM. No other tweaks are set other than default.

Yesterday the phone rebooted on me twice while on a call with work. Other than that hiccup, it never has given me any trouble.

I like Voodoo Color so I would rather not use Corn 7.0A if possible.

Anyone successful at setting Corn v 7.06 to 1000MHz? If yes, how?
[Captivate Android Development] mtcarey:
Turning it off works fine for me. Did you save "boot settings" in the Voltage Control app? If so, use the app to delete it.
[Captivate Android Development] -Thrive-:
Yes, I have used the setting in CWM to switch back and forth successfully a number of times with 7.06. Maybe a remnant from past use of voltage apps? You could try downloading Voltage Control from the Market and see if that works. It also works for me on 7.06.
[Captivate Android Development] rayburne:
Thanks for spelling it out for me (I probably should have searched more).

When I found the setting 1200MHz = On/Off in recovery, I thought that was all there was to toggle it.

I downloaded Voltage Control, set it to boot to the 1000MHz setting and saved.

Will see how it goes and report back.

The only reason I want to test this is because of the phone reboots that have only happened once. I use this phone for work so I can’t have it reboot in the middle of calls.

Other than this first issue, all the Corn kernels have been awesome and solid for me. This has never happened before.

mtcarey is a the man and can’t say thanks enough for sharing his work.

Thanks mtcarey and Thrive for the helpful reply.
[Captivate Android Development] mtcarey:
Actually, the Recovery setting is all you need to toggle it. The only reason I mentioned Voltage Control was because it's possible to override the Recovery setting with it. If the Recovery toggle isn't working, it's because something is overriding it (or something else is messed-up).
[Captivate Android Development] rayburne:
The recovery setting doesn't seem to be toggling it. Anything I can check to see why it may not be working correctly?

The voltage control app seems to working well though.

Like I mentioned other than installing Saurom then flashing the kernel, I haven't made any other settings changes or tweaks with the CPU other than trying to toggle the 1200 MHz on/off setting. Thanks again.
[Captivate Android Development] basily:
I use smugmug to host my photos online, and recently I've noticed that the app quits uploading when I open another app, or even just when I turn off my screen. It didn't use to do this, so I'm thinking LMK settings, but I can't find them -aren't they in recovery?
[Captivate Android Development] bimmernut318:
Yes it is in recovery under reformatting, tweaks and more then tweaks and settings
[Captivate Android Development] mtcarey:
Other than checking the usual suspects (init.d scripts, sysctl.conf, etc.) I would suggest uninstalling or freezing with Tibu any apps that might be messing with the cpu frequency, such as Tegrak, Voltage Control, SetCPU, etc.

Then use Android Terminal or ADB to execute these two commands:

echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

----

echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

After each, see if CpuSpy picks up the change. If not, then try re-installing CpuSpy.
[Captivate Android Development] Strugs:
Any luck on the IPsec issue? I did notice that after flashing from corn to a stock kernel, the issue remains.
[Captivate Android Development] mtcarey:
Just figured it out! The settings.apk is not setting permissions properly in the keystore! The way around it is to use Root Explorer to set the permissions on the folder /data/misc/keystore to r/w/x for owner, group, and others. Then use the settings app to create the IPSec connection, including the shared key and secret. Save the connection, then open up /data/misc/keystore with Root Explorer and set the permissions on all the new files in there (should be 3) to r/w for everybody. Now it will work!

P.S. In the next version I will change the permissions on the folder at boot, but I'm not sure what to do about the file permissions, other than re-writing settings.apk. Not really practical since it is often customized in various ROMs.
[Captivate Android Development] basily:
Found it. I was using 7.05 and it wasn't there. On 7.06 now...
[Captivate Android Development] Strugs:
I will give it a shot. Thanks!
[Captivate Android Development] basily:
Worked for me! Thanks!
[Captivate Android Development] bobapunk:
Yesterday I was trying to squeeze all the possible performance out out my cappy. I set the LMK to 80MB, OC to 1200mhz on, and changed the governor to "performance".

Now I am getting force closes on gapps and acore.

I set the kernel settings back to 60, OC to off, and smartassv2 (where I had them before) but I am still getting the FC's.

The only other thing I changed on the phone was adding whitepages premium app. The phone reboot itself during the install which I thought was odd, but the app seems to be working properly and fully.

Is there anything that I can do short of wipe and reflash?

I am on Corn 7.06, Sparko KK4 Rom, GO Launcher EX. The FC's happen on booting.
[Captivate Android Development] mtcarey:
Reading reviews of the app, I see a couple of similar reports from Galaxy S owners. It's an autostart app... if you can't get the phone stable enough to uninstall it, you'll probably need to re-flash you ROM.
[Captivate Android Development] bobapunk:
Ok, I froze it in TiBackup and still had the same FC issues.

I ran partition repair on all 4 partitions, still had the FC's, and all the apps that are on my external SD are now "not installed on the phone"

Reconverted all the partitions back to RFS, still have the FC's and all the apps are still showing as "not installed"...

what would wipe and factory restore do? Or should I just re-flash the ROM? Is there anyway to get TiBackup to back up all the apps are showing as "not installed"?

Thanks!
[Captivate Android Development] mtcarey:
Try clearing the dalvik-cache in Recovery. Other than than I don't know....

Edit: Actually, if you re-formatted then the dalvik-cache would have been cleared for you. The app may have installed something to the system partition that pushed space used over the total partition size, resulting in a partial (broken) install. You can try uninstalling (rather than freezing), but you'll probably need to re-flash the ROM.
[Captivate Android Development] bobapunk:
Ok, Rom Reflashed, Corn 7.06 reflashed.

Lets see how it takes for me to mess something up this time!

:D
[Captivate Android Development] mcala:
I found an issue with Shadowgun & syscorps tweaks. If I have them enabled the game lags really bad & crashes. It can be repeated. For now I disabled the tweak and the game flies. Maybe not an issue but just a side effect!

Crashed once using Maldroitweaks but then was playable. No tweaks is still the best!
[Captivate Android Development] DDNV:
7.0A and Tegrak Pro Trouble

Hello all,

History

-I was on Legend 3.0 with Corn 7.06

-Used i897uckk4 Odin One Click - Stock, NO Bootloaders, Re-partition, Full Wipe

-Odin'ed Corn 6.03 for root

-Flashed SimplyStock which I think is suppose to have 7.0A but I still had 6.03 after flash

-Flashed 7.0A

-wiped data/factory reset in recovery, then wiped cache

When I go to load the overclock module in Tegrak Pro I get the "unmatched driver version" message one would expect with 7.06.

Any advice? Just a bad flash? I'd be surprise because I effectively did two full wipes, right?

Edit: Forgot to say I check init.d and sysctl. I didn't delete cwm5sc. Should I?

Thanks,

DDNV
[Captivate Android Development] Liv33viL:
Green Screen Flash

Just figured I throw this out there to see if anyone has been experiencing a green tint flashing over the device display, almost simultaneously with a screen timeout or a manual screen lock... with the Corn v7.06 kernel?

Really odd... never had this before and have been trolling the boards for the last three days looking for some insight.

I just noticed this "green tint flash" after flashing the Corn v7.06 kernel and hadn't has this prior to flashing.

Basically my device is an I897 with a fresh OTA UKK4 2.3.5 bone stock.

I went through CWM and explored all the features and options to see if there was anything that needed to be tweaked or untweaked, but didn't see anything of the sort in any of the menus.

Since the "green tint flash" has been occuring, I have OC'd the kernel to 1.2ghtz, governors, schedulers are set from within CWM...

I use Voltage Control Extreme (v4.9.12) to monitor the voltages or quick change if need be from a gui...

I'm also using the Voodoo Control Plus app for audio tweaks and to see if I may be able to get rid of that damn green flash. ... To no avail...

I don't need to get too much into detail about my device settings (Voltages, Heap Size, or Cache Pressure or Read Ahead speeds etc..) being as I do not believe this is having an effect in this issue.

The issue happened almost immediately after I flashed 7.06 with OTB defaults only... no OC, no scripts and no tweaks.

The issue is not occurring with the Stock KK4 kernel.

Just figured I throw this out there and see if I wasn't alone with this.

Appreciate any feedback regarding this green tint flash on timeout or manual screen lock.

Peace-
[Captivate Android Development] storm717:
Green flash on screen off is caused by aggressive Voodoo color adjustments from what I can tell. Never really messed with finding a fix for it so I just adjusted the settings until it went away. Do you have the CRT animation for screen off? I was wondering if that would fix the issue (as I think the fade-to-black with tweaked RGB kernel settings is what causes the flash).
[Captivate Android Development] Liv33viL:
No on the CRT animated screen lock. There is an app on the market Screen Off and Lock that creates that effect, but rather than bog down resources with a non essential process, I would manually modify the system UI with a simple code modification that these effect applications are based on.

Anyhow, I kind of figured that it was video pressed related. I'll look to see if I can tame the settings down some in Voodoo, if not, there's always the Chainfire 3D app.

In any event, when I resolve the issue, I'll post post with the resolve for anyone else who may be plagued with the Green Lantern Flash...

Thanx for the response Storm.

Peace-
[Captivate Android Development] lactardjosh:
I had the green ghosting you're talking about. I turned the CRT animation, which also got rid of the green ghost.

CRT animation is just a framework-res.apk change. You just need to change the value in the bools.xml for animatescreenlights to False. If you're using an unmodified framework-res.apk at the moment, you can flash the mod I made. http://xdaforums.com/showpost.php?p=22357615&postcount=46
[Captivate Android Development] Liv33viL:
I resolved the issue last night without adding to anything... I just backed off the GAMMA settings in my GPU settings via Voodoo and ...

Viola' - the trick... she was done! No more Green Lantern meets Flash Gordon on my device ... :)

Thanx for the feedback and suggestion though Lactardjosh.

Yes I already modded a copy of my framework-res.apk with the code switch for CRT shutdown. Pretty cool!

Peace-
[Captivate Android Development] DDNV:
7.0A and Tegrak Pro?

Bump.

Any thoughts, comments, or suggestions based on my post below?

Basically I'm not getting Tegrak Pro to work with 7.0A.

Thanks,

DDNV
[Captivate Android Development] sa1yan:
You are on 7.0A, even though it says 6.03. That's because when I made that ROM, I forgot to clear the dalvik cache in the install script. You are on 7.0A, but the settings doesn't show the correct version. So go into CWM, and clear cache and dalcik-cache and reboot and it should give you the right reading in settings :)
[Captivate Android Development] KMan94:
just a little eat up with the stupids here...

This goes in the PDA slot correct? I've always gotten by without using odin although I've read a bunch about it. Just making sure.
[Captivate Android Development] mtcarey:
Yes, PDA slot.
[Captivate Android Development] DDNV:
No probelm there. Since I flashed 7.0A after flashing SimplyStock, it read 7.0A. I then did all the clears (cache, dalvik, system).

Overlocking 7.0A with Tegrak would be way cool.

DDNV
[Captivate Android Development] bobapunk:
I didn't think that this kernel was compatible with Tegrak...?
[Captivate Android Development] DDNV:
7.06 is not compatible, but 7.0A is based on the OP.

DDNV
[Captivate Android Development] mtcarey:
I might be wrong. Has anyone else used Tegrak with 7.0A?
[Captivate Android Development] nycmon:
as far as 7.06 I've found it works best with CPU Master Pro in my experience so far.....Love it!

Much more stable and better featured than tegrak overclock extreme....

no offense to tegrak^^

It just works better for me...
[Captivate Android Development] RTBee:
MT, given any thought to an ICS version of your kernel? Or have I missed it? Maybe something like IceCreamCorn? :D
[Captivate Android Development] mtcarey:
Working on one right now!
[Captivate Android Development] robm1911:
You da man!!!!
[Captivate Android Development] RTBee:
Sitting on pins and needles! Thanks! I've played around with Fusion XII and Corn 7x and loved it. I'm on Fusion ICS now, I'm liking it a lot and with one of your kernels, well it could be my retirement plan for my cappy. I love your work, so in advance, thanks for your corny kernels!! :D:D They're a-'maize'-ing!
[Captivate Android Development] Red_81:
I see what you did there and I'm loving it.

P.S. I work for a major seed brand so its only right that I support corn.
[Captivate Android Development] herofmm:
I could't resist posting a reply. Super super sweet!!!
[Captivate Android Development] nycmon:
Hey I don't know if this a problem only I am having or not but ever since I ran the maladroit tweak from CWM, my applications cannot connect thru mobile networks....only browser, market, and other system apps are connecting. Everything connects fine with wlan but not with mobile networks...

I have tried setting it to syscorps tweak with no results. I tried turning off init.d from CWM with no results...I deleted all files from the init.d folder with no results...I went from 7.06 to 7.0A with no results...

Are there settings maladroit tweak changes which are permanent or something? I had no connectivity issues until i mistakenly tried that tweak :-(
[Captivate Android Development] mtcarey:
What ROM are you using? Those tweaks include some "setprop" 3G adjustments that might have messed things up for you.
[Captivate Android Development] mtcarey:
I think you can fix this by typing the following three lines into Android Terminal:

-----

su

setprop ro.ril.hsxpa 1

setprop ro.ril.gprsclass 10

-----

I'll get rid of those "setprop" settings in the maladroit.tweaks... they shouldn't be there.