yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RootTheMachine:
Because it's bumping into me. I can confirm that touching the screen at any time will turn it on. And that happening constantly effectively makes the screen stay on.

Well anyway I just figured out that using NStools to set touchwake to 0 sec results in this behavior

Sent from my ICS Samsung Captivate
[Captivate Android Development] scottcwhite:
NST has no affect on touch wake, Semaphore app does. Set it at 15 seconds and then if your screen self times out, after 15 seconds touch wake will not work. If you've been thinking NST is controlling the settings for it that would be the problem

Sent from my Samsung Galaxy Tab
[Captivate Android Development] askpcguy:
Please explain. And by that I meant over a private message.
[Captivate Android Development] RootTheMachine:
Not true, either one can control it. You can even have semaphore control's touchwake disabled, but still turn it on with NStools.

Sent from my ICS Samsung Captivate
[Captivate Android Development] daskanda:
If you use the power button to lock your screen touchwake can't wake it..... I kep it set at 15 seconds and can confirm that it doesn't stay on forever in my pocket
[Captivate Android Development] Devo7v:
I am also having this same problem. YouTube force closes every time I try to play a video. I am on Fusion ICS and didn't have this problem until I flashed Semaphore 1.1.1c. It is the only thing that has changed, so I'm pretty sure it's a kernel problem.
[Captivate Android Development] scottcwhite:
What setting in NST controls Touchwake ?
[Captivate Android Development] RootTheMachine:
The touchwake setting...

Sent from my ICS Samsung Captivate
[Captivate Android Development] scottcwhite:
I looked and had nothing so I removed NST completely then got it fresh of the market again and now for the first time I see it. Can't even begin to understand that one. My phone has weird issues. I also have 5 photos in my gallery that I've deleted over and over again for over a month straight but yet they never go away

Sent from my Samsung Galaxy Tab
[Captivate Android Development] prbassplayer:
Lol crazy Media server? or your phone just doesn't want you to loose those "memories"? xD
[Captivate Android Development] Nick0703:
Lol, yeah I think his phone wants him to remember those memories forever!xD

I had the same problem with the pictures reappearing in gallery after deleting them, to fix that I went on the PC and deleted it from there. But I found out then that when I was deleting them from gallery they never did, they were basically hidden.:confused:
[Captivate Android Development] scottcwhite:
Yep. Last week traveling to Hawaii from East Coast I got that damn process media server has stopped working every time I turned my phone on in a different time zone. Don't know why I keep getting that. Never had til the latest version. I left VA and landed in Texas. Turned the phone on and got the error. Fixed it. Left Texas and when I turned it back on in Honolulu, same crap. Happened on the way back too. Don't know why the time change would cause it

Sent from my Samsung Galaxy Tab
[Captivate Android Development] scottcwhite:
Oh, and I also have the issue where the thumbnail picture is different than the picture it opens on many of them. Gets quite tricky setting wallpapers sometimes.

Sent from my Samsung Galaxy Tab
[Captivate Android Development] dongfangri:
Compass doesn't work with this kernel.

I have tried AOKP, CM9, and SLIM ROM, All have the same problem. But with other kernel, the compass works well.
[Captivate Android Development] scottcwhite:
Mine works fine with Slim

Sent from my Samsung Galaxy Tab
[Captivate Android Development] bearofbabe:
I turn the FM on in semaphore app. But i don't know how to use it? anyone help
[Captivate Android Development] pizz0wn3d:
FM? As in FM radio? Please tell me you don't mean FM radio.

Herp derp Captivate XDA Premium App.
[Captivate Android Development] mindphaser2k9:
Captivate doesn't have the FM radio hardware, don't even try.
[Captivate Android Development] Devo7v:
Further info:

I noticed that I was not able to play any of the videos that I had taken on my phone. I flashed back to 0.9.7c and I can play videos taken with my phone and YouTube videos, but with 1.0.0c and 1.0.1c I cannot play them. I'm not sure if I'm missing a setting somewhere (I'm using default settings) or if this is just an issue with my phone.

Does anybody else have issues with 1.0.1c not being able to play any videos?
[Captivate Android Development] scottcwhite:
My videos play fine and correctly

---------- Post added at 09:02 AM ---------- Previous post was at 08:59 AM ----------

It's easy to make it work with the Captivate. Just follow these steps:

1. Turn on FM in Semaphore App

2. Start Singing

3. For true realism you can even stop singing temporarily and quote advertisements
[Captivate Android Development] mrsubway:
Fast Charge?

There's an option on Slim ICS called fast charge that is supposed to let your phone charge faster when connected to a PC. I assume it does this by not loading the phone's drives. I enabled the option and it says if the Kernal supports it. When I plug my phone into my PC it is still detecting it, so I assume it's not working. Does Semaphore support this?
[Captivate Android Development] stratosk:
No, Semaphore does not support and not going to support fast charge.

Fast charge allows higher charging current from USB. I don't feel very comfortable 'playing' with charging current.
[Captivate Android Development] prbassplayer:
Not arguing but curious. Doesn't the mod just change the voltage to the same voltage as to when you plug it in the wall, as in 1V vs .5V? I can't see a issue with the cable nor the phone as it both use the same voltage when plugged to the wall maybe the computers USB port? But doesn't computer USB port capable of 5V+- 5% or 10%? Like I said just curious if I should be worried. I rarely use that feature but it is useful when you need a quick charge before heading out.
[Captivate Android Development] mrsubway:
Thanks. Meh I'll just buy an extra OEM charger from EBay for 3 bucks to keep at work. :D
[Captivate Android Development] geokilla:
That's exactly what it does. It's a very useful feature and the only con about Semaphore by not having this feature.
[Captivate Android Development] scottcwhite:
Or get an Anker and your battery will last till you go to bed or longer
[Captivate Android Development] stratosk:
As far as I know, the voltage is always the same 5V.

The charging current is changed. The max current without the fast charge mod is 500mA. And this is the limit of USB 2.0. USB 3.0 may give more (I think it's up to 900mA).

With fast charge enabled the phone 'thinks' that it's plugged into AC. So I *think* that will pull the max current available.

Please note that Samsung in GB kernels has capped the max current to 96mA when in USB.

Because of all the above, and because I'm not sure what is the max current that the phone will pull from USB and I don't know about the side effects that this may have to battery/phone/PC's USB ports, I don't implement this feature.
[Captivate Android Development] scotths:
The usefulness of this is more with chargers other than the one provided by Samsung. Samsung (and SOME other ots chargers) short the USB data connections together to inform the phone that is connected to a charger rather than a computer. If they aren't shorted together the charge the phone can draw is limited to roughly 300mA. If they are shorted together the phone will draw the maximum current it can up to the phone's internal limit (I believe around 700mA). If you are actively using your phone, this can be the difference between a reasonably quick recharge and a situation in which you are barely treading water; essentially just using the power source to power what you are currently doing.

The fast-charge module simply tells the phone to act as if it is connected to a charger. It is less useful on a computer (where the current may be capped anyhow) and more so if you should happen to have a non-Samsung charger or charging battery. As an alternative to the fast-charge module, one can modify a micro-usb cable by cutting into the cable, clipping the (most likely) green and white wires which ordinarily carry data and twisting them together but only in the direction as seen by the phone (the computer/charger should see an open circuit). This creates a cable that will no longer be able to send data but will automatically tell the phone that whatever it is connected to is in fact a charger. I use this with a portable battery, car charger and occasionally an iphone charger all of which do not implement shorting of the data pins.

The fast charge module seems a more elegant solution...

For the reasons given above, this may only charge at 300mA unless it is a Samsung OEM or a non-Samsung that shorts the relevant pins together.
[Captivate Android Development] stratosk:
I agree with your explanation about what fast charge mod do.

Some parts of kernel code (thanks to Lukiqq):

if (chg->cable_status == CABLE_TYPE_AC)
max8998_write_reg(i2c, MAX8998_REG_CHGR1,
(MAX8998_TOPOFF_10	<< MAX8998_SHIFT_TOPOFF) |
(MAX8998_RSTR_DISABLE	<< MAX8998_SHIFT_RSTR) |
(MAX8998_ICHG_600	<< MAX8998_SHIFT_ICHG));
else if (chg->cable_status == CABLE_TYPE_USB)
max8998_write_reg(i2c, MAX8998_REG_CHGR1,
(MAX8998_TOPOFF_25	<< MAX8998_SHIFT_TOPOFF) |
(MAX8998_RSTR_DISABLE	<< MAX8998_SHIFT_RSTR) |
(MAX8998_ICHG_475	<< MAX8998_SHIFT_ICHG));

MAX8998_ICHG_600 means 600mA

MAX8998_ICHG_475 means 475mA

We can discuss without end if it's safe (not only for the phone) or not to change the charging current. There are also a lot of posts here in XDA.

I'm saying again, that I don't claim that fast charge is unsafe. But, until I will prove to myself that this is 100% safe I will not do it. :)
[Captivate Android Development] prbassplayer:
I didn't mean to derail your thread. I was just curious and wanted a dev's point of view. Btw I don't know why I was thinking V when its amps that charge the battery (guess a brain fart)

Thanks
[Captivate Android Development] stratosk:
Absolutely no problem my friend. Of course, I know you didn't mean that. :)

I'm sorry if my posts sounded very strict (I hope this is the exact English word). I just want a totally safe Semaphore.

At the end, from discussion will come up something useful.
[Captivate Android Development] mrsubway:
Sounds like defusing a bomb.
[Captivate Android Development] stratosk:
Because many people requested fast charge will be implemented in next version with this way:

http://xdaforums.com/showthread.php?p=26059655
[Captivate Android Development] energyracing:
I just started using Semaphore with CM9, and I am very happy with it. It seemed to put an end to the sleep deaths I usually would get once a day.

However, when I went to flash a new nightly through CWM, the installation failed and I had to flash a different kernel just to get the installation to succeed. I know this failure happens when a Kernel is sourced from I9000 code and is modded for a Captivate (I897).

Does anyone know of a better method for flashing ROMs when coming from Semaphore, without having to flash other kernels first?

EDIT: I used Semaphore 1.1.1c
[Captivate Android Development] mandy007:
any chance of include the volume boost hack? thanks
[Captivate Android Development] scottcwhite:
+ 10 on this one. Would save me from from having to put the script in myself
[Captivate Android Development] mindphaser2k9:
What the script can help you if a kernel doesn't support this?
[Captivate Android Development] scottcwhite:
Unless it's just my mind playing tricks on me it made a difference just like on glitch that it comes built into. I put the 90call_vol.txt in the init.d folder and changed all on speaker to #3 and had to go back and back it down because it was so loud when playing movie trailers and youtube it was distorting.
[Captivate Android Development] drewbag:
I just came to say thank you. This kernel improved my battery life so much.

Thank you
[Captivate Android Development] kafepuya:
I installed Semaphore 1.1.1sc. I see that the Semaphore App has an option of four Governors (SaveBattery, Conservative, Ondemand and SmartAssV2) and three schedulers (Deadline, No-op, and Simple I/O). However, SlimICS includes NSTools, and in it I only see Noop as the scheduler and Ondemand or Performance as options for Governor. On the Semaphore App I have selected SmarAssV2 but on NSTools, I have Ondemand.

Can anyone clarify this for me please. I have been reading This Kernel thread, and would like to tinker with the kernel settings. TIA
[Captivate Android Development] prbassplayer:
Semaphore has its own app because it has all its features as modules. Use Semaphore app to set everything up Only use NSTool if you need to (voltage, bln, etc) You shouldn't need NSTool at all with semaphore, but it doesn't mean you can't use it, BUT you need to use the kernel app as main.
[Captivate Android Development] kafepuya:
Thanks for the reply. Just to be sure,using Semaphore App will override whatever Governor and Scheduler is selected on NSTools?

Sent from my phone
[Captivate Android Development] prbassplayer:
I would recommend you not using NSTools if you don't want issues. They both can work in coherence but you set something on them wrong your phone will crash and/or loop etc.
[Captivate Android Development] kafepuya:
I understand. The problem is that when I look in NSTools, a Governor and Scheduler are selected, even if I don't touch the settings and only select BLN. I see no options in NSTools to keep it from controlling Governor or Scheduler. As it stands right now:

NSTools: Scheduler (noop) and Governor (ondemand)

Semaphore App: Scheduler (noop) and Governor (SmartassV2)

I'm not having boot loops or any problems, but neither am I sure that the phone is running on the settings from Semaphore App (as I would like) rather than NSTools.

In any case, I will keep tinkering and see if I can come across another solution besides uninstalling NSTools.
[Captivate Android Development] prbassplayer:
When you set it on Semaphore app NSTool will detect the change. The issue is how each app applies the settings is different, so if you set something on Semaphore app and then set up same thing but with a different value on NSTools it can make the phone act wrong, lead to bootloops or instability. I've used to use both apps no problem just have to be careful. Just make sure you have everything backed up just in case you need to wipe ;).
[Captivate Android Development] willbs94:
this is touch recovery correct?

Is there a way to flash this with Odin or such because on the captivate that I'm using, the power button doesn't work.
[Captivate Android Development] prbassplayer:
Using Odin or Heimdall is unlikely on any AOSP rom/kernel. Last I remember Semaphore doesn't have touch recovery, but I could be wrong.
[Captivate Android Development] willbs94:
Can you point into right direction of flashing an ics kernel through Odin or heimdall?
[Captivate Android Development] prbassplayer:
Pretty sure you cant
[Captivate Android Development] scottcwhite:
Here's what I do that gives me great results. Open Sem app select SmartassV2, then SIO scheduler. Leave everything else alone. Now open NST and you will see the same sched/gov. if you do not than wipe data for NST reboot into recov and clear NST settings. Go back and opn NST and you'll see the same sched/gov as you chose in SEM app. Go down to live OC and increase if you choose. I use 120. Everyone's phone is different. Turn BLN on and exit

---------- Post added at 03:25 PM ---------- Previous post was at 03:22 PM ----------

Use your soft keys for CWM and I know you could use a .tar file to Odin kernels pre ICS roms, etc. but as BASS stated the framework or whatever of 4.0.4 doesn't make this doable any longer
[Captivate Android Development] willbs94:
So would it be possible to flash a kernel (.tar) through Odin that has touch recovery but not ics based.

Followed by flashing a touch recovery ics kernel and then a rom.

I know this sounds like a bad idea to go about with not having a power button but its the best I can try at least right?
[Captivate Android Development] prbassplayer:
ICS has nothing to do with it, it's the fact being a AOSP rom. It would be possible but no devs ever got that feature on a samsung based kernel. So no.
[Captivate Android Development] scottcwhite:
Send a PM to top he has a broken power button and can probably help you
[Captivate Android Development] scottcwhite:
And all recovery has touch just use your soft keys like I previously stated
[Captivate Android Development] mirrored:
Do you have to restart the phone when you change settings in the Semaphore app like what CPU frequency you want or what Governor you want?
[Captivate Android Development] mirrored:
So let's say I only used NSTools to set BLN time out times. Would it still be activated and interfering with the Semaphore app settings if they were at different values? The NSTools settings for the frequency and governor would be unchanged, but the Semaphore, if I did change it to overclocking and change the governor, would then conflict with NSTools, correct?

As an alternative, can I uninstall NSTools and use solely the Semaphore app for overclocking & governor settings + another method to control my BLN?
[Captivate Android Development] prbassplayer:
Either would work.
[Captivate Android Development] scottcwhite:
No

Sent from my Samsung Galaxy Tab
[Captivate Android Development] askpcguy:
On MyUi just updated to Semaphore v1.1.1c and been running smooth ever since. Came from Weui v1 and all I did was wipe system/cache and flash. Perfection!
[Captivate Android Development] baconatorXVI:
Here's a minor solution and a question:

Solution: to others who had said they didn't have a touch wake setting available in NStools and re downloading form the market fixed it. well i figured out uninstalling and re installing via titanium backup enabled my touchwake setting toggle button, and it works...

now my 720p and 480p problems...(sorry for any spelling errors and such, i'm really tired, maybe that's why i'm having trouble. LOL!)

I've read and I can't find an answer, thanks for any help.

I'm on CM9 v17 and I like 1.1.1c a lot so far, but i am unable to get any 720p or 480p video recording or playing. My captivate lists 374.2 memory availible, like here.

But i am still unable to play or record anything in 720P or 480p, what am I doing wrong? freezing and defrosting the gallery app didn't help it play any video..

This is with no OC or any tweaks.

I've tried 1.0.0c and that worked for video, non of the S versions played or recorded, but they booted fine.

Thanks for any help with my probably dumb question
[Captivate Android Development] stratosk:
CM9 build 17 does not includes the new pawitp's memory configuration.

I think you have 2 options to make it work:

- upgrade your CM9

- downgrade Semaphore.
[Captivate Android Development] baconatorXVI:
Hey, why not put a new power button in?

search here, or elsewhere.

http://www.globaldirectparts.com/Samsung-Captivate-i897-Replacement-Repair-Parts-s/6412.htm

search for teardown guides if you want help getting things out.

I can't remember taking the power button off, but I've taken every component out of my captivate multiple times, it's pretty easy. it might take a bit of careful work to fix it. I'll probably be helping my brother with his since his power button is starting to die.

I'm not responsible for any damage to your phone. It's not too hard to pull everything out. that's how i fixed my speaker cutout issues.

---------- Post added at 01:29 AM ---------- Previous post was at 01:29 AM ----------

Thanks so much for your quick reply.

dang, this is what i was running, http://xdaforums.com/showthread.php?t=1363760

i'm guessing I'd have to switch to a nightly right?

anyways i'm on 1.0.0c and it's all working.

thanks again.
[Captivate Android Development] stratosk:
Yes, flashing the latest nightly and then 1.1.1c should be fine.
[Captivate Android Development] baconatorXVI:
gosh i'm just so sketched out about the nightlies, idk why i just like how build 17 is really stable, and i dislike how there isn't any change log listed. i guess i prefer seeing exactly what is changed(i'm not smart enough to read through the source and understand waht's going on, i've only done basic c programing). maybe i'll just use slim ics.

thanks again!
[Captivate Android Development] Monfro:
Here you have CM9 changelog:

http://cm-nightlies.appspot.com/?device=captivatemtd

That old CM9 build is not configured to use new bigmem kernels.

It is also Android 4.0.3, while all newer roms are configured and Android 4.04, which is faster than 4.03.

Try some newer builds and you will not be disappointed
[Captivate Android Development] anhthachet:
Waiting for 1.2.0 version for our cappy :)
[Captivate Android Development] mirrored:
I set Lock min scaling frequency to 100MHz when GPU inactive and after locking the phone, I tried to unlock it but the screen wouldn't turn on. Is this a known issue?
[Captivate Android Development] scottcwhite:
It's known to me. Don't know if it's widespread or not. Just hold all the button for about ten seconds and it will reboot into recovery and then you can reboot from. Saves doing a battery pull

Sent from my Samsung Galaxy Tab
[Captivate Android Development] geokilla:
Hey stratosk, when will we get 1.2.0? Been a couple days now and I'm anxiously waiting lol
[Captivate Android Development] holeindalip:
I believe its just vol up+power for a reset
[Captivate Android Development] stratosk:
New version 1.2.1c

- New initramfs (thanks to Mialwe for his cooperation on this)

- Bigmem reservation optional through Semaphore app (bigmem breaks 720p video recording) *

- Smooth UI implemented in conservative, smartassv2 (selected as separate option)

- Semaphore Script Manager application 0.75 (thanks to HM.Carbide)

- Fast Charge support (thanks to Chad Froebe) implemented as module **

- L4 (100MHz) int volt 1100mV (as GB)

- upstream updates

- Dropped LMK scritps

Variations:

Normal versions (for CM9 or ROMs without hugemem configuration)

1.2.1c

- 374.2MB - 386.4MB

For Slim ROM or patched ROMs with hugemem configuration

1.2.1sc

- 387.2MB - 399.4MB

* Needs reboot to takes effect. If the phone shuts down needs additional reboot.

** Enables support for fast charge. It does not enable the feature.
[Captivate Android Development] geokilla:
I'm guessing the .tar versions let me install Semaphore via ODIN?
[Captivate Android Development] igoa:
Bug

1.2.1sc: Frequency Limit to 800 MHz in scripts manager not working (1000Mhz still used) ... sheduler always "noop" no matter what selected in scripts ... Lock min scaling feature locks it to 200Mhz but text says it's should be 100Mhz ...
[Captivate Android Development] Elad92:
Hey,

used this kernel on GB and loved it!

Does it supprot CM9?

Thanks
[Captivate Android Development] prbassplayer:
Please read more carefully. Quoted from OP
[Captivate Android Development] stratosk:
Yes, you are right tar files are for installation via ODIN. You may also use Heimdall after untar the file.

If none of the options in Semaphore app persists after selection, I suspect a busybox issue.
[Captivate Android Development] sinichi21:
Just want to ask is there a risk on fast charge thought it was safe but saw on sema app enable at your risk so got curious thank again for the updates
[Captivate Android Development] stratosk:
Most people say that it's safe. I don't claim the opposite but I don't have any evidence for this (and I guess I'm too lazy to investigate this :) ).

I implemented fast charge because many people asked for this. So, it's user's decision if it is safe or not.

BTW, only support for fast charge is enabled from Semaphore app. You need extra action to actually enable it (via ROM's setting, or a script etc)
[Captivate Android Development] trell959:
Does it work on 4.0.4?

Whatever, I'll try anyway
[Captivate Android Development] mrsubway:
Can you use NStools to set things like overclocking or does the Kernal come with its own program to do that? Glad to see Semaphore on ICS! :D