yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] scottcwhite:
It's based of iOS 5 provided gpu rendering is set to lenticular of the linear position of the horizontal

Sent from my Samsung Galaxy Tab
[Captivate Android Development] topiratiko:
LMFAO 10chars

Sent from my Galaxy S Captivate on Slim ICS 3.6 w/Semaphore 1.0sc Kernel 1.220Ghz@122% live OC and 387mb available RAM. BUTTER
[Captivate Android Development] mirrored:
Does MMS work for everyone?
[Captivate Android Development] prbassplayer:
I've had issue with sending mms, but I'm unsure if its ATT or rom issue and with finals I really haven't had time to fiddle with it.
[Captivate Android Development] mirrored:
I have ATT too. MMS wasn't working on SimplyAOKP either.
[Captivate Android Development] rophiroth:
Yahoo, this is the first ICS who dont restart on the night!, but it does when the phone was 45% battery on sleep mode many times... so its looks like is more a specific phone problem rater a ROM problem, but this didnt happen to me on froyo below 76% battery.

At 25% battery this never restart again mmm. Could it be just a calibrate problem?
[Captivate Android Development] prbassplayer:
If stock kernel I would think its hardware. Then again my phone has never had SoD or CoD unless I used a kernel with Didle on.
[Captivate Android Development] krarvind:
3.7 Released- Read Changelog carefully and my recommended installation for 3.7
[Captivate Android Development] scottcwhite:
I've had zero issues with SMS/MMS

---------- Post added at 08:33 AM ---------- Previous post was at 08:32 AM ----------

Happy day cause sammy just popped up in my status bar :d:d:d
[Captivate Android Development] mopo01:
You are able to set up the gmail to send with the school info as the address
[Captivate Android Development] Fear of Oneself:
Settings>Developer Options>Force GPU Rendering, flick that on.

As for the theme, I was curious if the transitions are android default (fade) or does it have any custom look. (Like how MIUI has everything themed orange and white as opposed to grey and blue)
[Captivate Android Development] rophiroth:
My kernel its 3.0.8 dirty and haven't make changes to it. What is Diddle on?

I always have shutdowns with full battery, but with ISC got at half and even less %

What specific mean sod and cod ?

Thanks
[Captivate Android Development] npt1988:
I'm trying to download the new base using the app, but the md5 check is failing. The captivate essentials file is okay
[Captivate Android Development] prbassplayer:
Dildle= Deep Idle

SoD= Sleep of Death

CoD= Charge of death
[Captivate Android Development] lordxentris:
Bro, You are too Awesome!!! :D
[Captivate Android Development] Ozark_8125:
Only issue I had was on first install the launcher wasn't opening correctly - the dock wasn't populated and there was no way to open the app drawer. Just rebooted back out to recovery and installed base + essentials again and it worked. Only change from the recommendations I did was on first install I did a format/sys from mounts. Working perfectly again - thanks for the hard work!
[Captivate Android Development] mirrored:
I had the same issue. Wiped data/factory reset, wipe cache, wipe dalvik, format system, flashed base then essentials, then after first boot there was nothing in the dock and no way to get to the app drawer
[Captivate Android Development] geokilla:
App Drawer is hidden. Just press the left soft key to bring up the additional menus option.
[Captivate Android Development] scottcwhite:
I've never had that box checked. What is gained or what is the purpose of having it enabled ?
[Captivate Android Development] prbassplayer:
Supposed to make transitions and UI, generally, run smoother and, supposedly, give better battery life. On the negative end it can make older apps not designed for ICS less stable or just unusable. At least that's what I understand from it. I just don't understand what the dude is asking at all since themed or not that feature should work just the same.
[Captivate Android Development] diakonos:
Built into the Zeam launcher by default is the "swipe down" (or is it "up"?) behavior of the home screen to display the app drawer. I found that totally by mistake.

And +1 on the 3.7 wipe data + format system (to be safe) didn't bring back my Zeam launcher screens nor my dock. I restored my Zeam app + data from TiBu and so far it is working fine.
[Captivate Android Development] Ozark_8125:
I was trying to figure out what folder to point the custom apps to for the lockscreen target... since I got a choice to open gallery or oi file manager... then realized you have to click on the left side of the 'target' field (over the custom app wording itself). I was clicking on the red 'don't' circle and I think it was thinking I wanted to choose a picture (icon?).
[Captivate Android Development] mirrored:
Is there any difference in the Maps in the Update Me app or on the SlimICS Rom website than the one on the market?
[Captivate Android Development] prbassplayer:
If the description doesn't say in OTA probably there isn't.
[Captivate Android Development] mirrored:
Sorry, should've read more thoroughly.

Has anyone figured out how to keep Maps from running in the background? If you kill the app in settings, it will just restart. And if you freeze it in Titanium Backup, it will make the icons disappear.
[Captivate Android Development] kruuth:
Silly question here but since I flashed the rom I'm getting a storage space warning even though I've got 9gb free on my captivate. There some setting I need to tweak?
[Captivate Android Development] prbassplayer:
Forum search is working again but this also works. =/
[Captivate Android Development] Ozark_8125:
Try using: settings/ASS/GeneralUI/Hold Back to kill while in the map app. That kills it on mine.
[Captivate Android Development] scottcwhite:
I've tried the above mentioned and everything else you can think of and nothing seems to keep maps from running short of freezing it and defrosting it everyone

Sent from my Samsung Galaxy Tab
[Captivate Android Development] rophiroth:
Thanks!

Im very confused, my phone before ICS just SoD over 80% battery, now is from 20% to 40% +- its looks like a rom change could happen on different, gonna test one more night to see if this will SoD and at how much %

EDIT: Correction, it still SoD when sleep and fully charged, from 20to40% the phone restart (not shutdown)
[Captivate Android Development] cletusarrarr:
You need to calibrate the battery. Always flash Roms while on 100% battery
[Captivate Android Development] scottcwhite:
Latter isn't really necessary any more. I flash at any percentage with zero battery issues

Sent from my Samsung Galaxy Tab
[Captivate Android Development] tkjeeper:
Loving this rom guys, I updated via update me app, from 3.6-3.7 with only cache and dalvic wipes seemingly without issue. Only thing I've noticed that's odd is that I do get a hot reboot when updating from the play store or downloading from update me and installing. I wasn't sure if this was a setting or if it's a result of not doing a factory reset. Everything else is flawless, I know this isn't the place but the only thing I miss on this rom is the "quiet hours", I find that really useful. Thanks all! Oh forgot to mention, I'm on the 0.55b devil kernel.

Edit: tried glitch kernel to see if that was the issue, same result, try this, try and uninstall an app from the app drawer, as soon as I click ok to uninstall it does a hot reboot. It's not a big issue, just wondering if anyone else has this or not.
[Captivate Android Development] prbassplayer:
Myth. Calibration doesn't do anything nor does flashing at 100% charge. What does make a difference is, example, you are getting bad battery after a fresh flash give it 2 or 3 cycles before saying this rom/kernel gives me horrible battery.

On the issues case It seems to me that its hardware, but if it is a "calibration problem" and want to try it (I would to make sure its not a hardware problem) charge it 100% then bump charge and deleted battery.bin. As I said battery calibration is myth but since in your case you should try just to make sure. Random question, what build # is your phone?
[Captivate Android Development] Ozark_8125:
As a followup - does the battery charge while in CWM? I usually have it plugged in when flashing since I'm already copying files over usb. I haven't been worrying about battery either but wasn't sure if it guaranteed no battery death mid flash while usb powered. That all said, battery life on any rom on the captivate is so much better than the skyrocket I had.
[Captivate Android Development] mikeymopar:
by now, either you flashed anyways or figured it out...it's not md5 hash anymore, it's sha1

btw krarvind, prbassplayer, et al...great dev, updates and support...nicely done :)
[Captivate Android Development] geokilla:
Battery does not charge while in CWM.

And battery calibration is not a myth. Though bump charging is a myth. Just my opinion though.
[Captivate Android Development] tkjeeper:
No one?
[Captivate Android Development] Ozark_8125:
Well... back in the 2.3 days I would say odin to stock bootloaders and start the upgrade process again. I would take a wild shot and say something between the radio / kernel / rom is busted and best bet would be to start over at stock and upgrade again. Fdisk it baby. Of course unless there's a cold solder joint in there somewhere...
[Captivate Android Development] prbassplayer:
Hot reboot as in not a full reboot just bootanimation and launcher load (no bootloader or kernel image)? If so I've only gotten that on Devil .55 and .56a/b. I'm currently on the twrp glitch and haven't had that issue, but i haven't had it for a day yet so who knows. If it happens again on Glitch going to try with Semaphore, though I'm waiting for 1.2.
[Captivate Android Development] Wakamatsu:
Installed 3.7 with just the cache wipe beforehand. No issues so far except that I had to pull the battery during the first reboot. Subsequent reboots were fine.

Update: I was getting random reboots so I did the full wipe and reflashed. Krarvind wasn't kidding about the extensive framework changes.
[Captivate Android Development] jvc73:
On 3.7 since yesterday, full wiped before install (was on 3.5 since released).

I can't get the tts working (my default language is italian, however won't work even if I set eng). Already flashed the addons, it just won't speak.

The google tts FCs.

The google navigator hangs ever since I installed the srec addon (at least I think that was it), use to have the problem on 3.5 too, not on the previous ones though. Actually anything using the gps appears to hang.

No use going to stock and reflashing, I've already done that and already reflashed slim many times.

Any help appreciated.

Tks
[Captivate Android Development] kafepuya:
Great work on the ROM krarvind. I'm currently running 3.6, and plan to update this week. I noticed that when I click on the hands free button, MIUI music is launched, rather than Google music. Is there a way to change the music app that launches when I click the button?

On the kernel front, I was wondering which Governor and Scheduler are default on the kernel you build? I get great battery life with it.

Excellent work man!

Sent from my phone
[Captivate Android Development] Wakamatsu:
Check in Settings >> NS Tools
[Captivate Android Development] iregret:
help. i keep on getting error in com.android.phone when doing outgoing and incoming calls. notice this problem in 3.6 but now im on 3.7 i still get this error.

edit: found out that if i set dpi lower than 182 i get this error. is there a fix for this?
[Captivate Android Development] spacecase-25:
I installed the stock ICS launcher, but any time I try to add a widget to the homescreen (using ICS launcher) it crashes. Any ideas?

E/AndroidRuntime( 1862): FATAL EXCEPTION: main
E/AndroidRuntime( 1862): java.lang.SecurityException: bindGagetId appWidgetId=8 provider=ComponentInfo{com.palmarysoft.forecaweather/com.palmarysoft.forecaweather.appwidget.QuarteAppWidgetProvider}: User 10058 does not have android.permission.BIND_APPWIDGET.
E/AndroidRuntime( 1862):	at android.os.Parcel.readException(Parcel.java:1327)
E/AndroidRuntime( 1862):	at android.os.Parcel.readException(Parcel.java:1281)
E/AndroidRuntime( 1862):	at com.android.internal.appwidget.IAppWidgetService$Stub$Proxy.bindAppWidgetId(IAppWidgetService.java:569)
E/AndroidRuntime( 1862):	at android.appwidget.AppWidgetManager.bindAppWidgetId(AppWidgetManager.java:438)
E/AndroidRuntime( 1862):	at com.android.launcher2.Launcher.addAppWidgetFromDrop(Launcher.java:1510)
E/AndroidRuntime( 1862):	at com.android.launcher2.Workspace$12.run(Workspace.java:2957)
E/AndroidRuntime( 1862):	at com.android.launcher2.DragLayer$3.onAnimationEnd(DragLayer.java:579)
E/AndroidRuntime( 1862):	at android.animation.ValueAnimator.endAnimation(ValueAnimator.java:1040)
E/AndroidRuntime( 1862):	at android.animation.ValueAnimator.access$900(ValueAnimator.java:49)
E/AndroidRuntime( 1862):	at android.animation.ValueAnimator$AnimationHandler.handleMessage(ValueAnimator.java:675)
E/AndroidRuntime( 1862):	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1862):	at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 1862):	at android.app.ActivityThread.main(ActivityThread.java:4575)
E/AndroidRuntime( 1862):	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1862):	at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 1862):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 1862):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 1862):	at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 228): Force finishing activity com.android.launcher/com.android.launcher2.Launcher
I/ActivityManager( 228): Clearing package preferred activities from com.android.launcher
W/ActivityManager( 228): Activity pause timeout for ActivityRecord{410a46a0 com.android.launcher/com.android.launcher2.Launcher}
I/Process ( 228): Sending signal. PID: 1862 SIG: 3
I/dalvikvm( 1862): threadid=3: reacting to signal 3
I/dalvikvm( 1862): Wrote stack traces to '/data/anr/traces.txt'
D/WebViewTimersControl( 1896): onBrowserActivityResume
D/WebViewTimersControl( 1896): Resuming webview timers, view=com.android.browser.BrowserWebView@40f36168
W/BaseUi ( 1896): mMainView is already attached to wrapper in attachTabToContentView!
W/BaseUi ( 1896): mContainer is already attached to content in attachTabToContentView!
I/ActivityManager( 228): Process com.google.android.inputmethod.latin.dictionarypack (pid 1722) has died.
[Captivate Android Development] prbassplayer:
Make sure it is in /system/app not data/app
[Captivate Android Development] spacecase-25:
Much thanks. Rookie move on my part.
[Captivate Android Development] HeathicusF:
Installed this ROM tonight, but having some problems.

None of the apps that I restore via Titanium Backup will run. I can uninstall them, re-install from the market, and they will run fine. Then use TiBu to restore just the app's data, and they will no longer run. The reason I even use TiBu is for the app data, not necessarilly the app itself, so this is a pretty big annoyance factor.

I'm coming from Gummy rom. I did a factory reset, wiped the caches, and formatted the /system partition before flashing the base, then Captivate essentials. After that, it was just restoring apps from TiBu. I did set the LCD density to the default 240 (and did the follow-through steps) to see if that helped anything and it did not.

Can I do anything to fix my problem? I'd love to stay with this ROM for a while, but if I can't restore my app data, I'll have to move on.
[Captivate Android Development] scottcwhite:
Not sure what is causing your issue but restoring app+ data works fine for me

Sent from my Samsung Galaxy Tab
[Captivate Android Development] HeathicusF:
After more playing around, I've found that I don't have to uninstall and re-install from the market. All I have to do is clear the app's data, then the app will load just fine. But this really defeats the purpose of the backup...
[Captivate Android Development] prbassplayer:
If some of those apps have save data from GB might give you issues. I haven't had issues with restoring app data except for a hand few of times.
[Captivate Android Development] HeathicusF:
Previous ROM was ICS and the apps I'm trying to restore worked fine with it.

The only thing I can think of that I might have done differently, was that on the previous ROM, I would go into TiBu and move most of the apps to the SD card to avoid the "low disk space" issue.
[Captivate Android Development] bhairya:
NS Tools not working

Flashed this ROM a few days ago from Serendipity 7 and I'm liking it so far. Battery wasn't lasting the day on the included kernel but flashing semaphore fixed that! When I click on NStools the settings menu closes/crashes. This wasn't happening before I flashed semaphore. I tried clearing NStools settings in recovery but that didn't fix it. What do I need NStools for and anyone know how to fix this? Thanks!
[Captivate Android Development] Wakamatsu:
Could be a conflict with the Semaphore app.
[Captivate Android Development] geokilla:
NSTools does not work with Semaphore.
[Captivate Android Development] mrsubway:
I believe with Semaphore you can use either NSTools or the Semaphore app, at least that's what I remember reading on the Semaphore thread. I just freeze NSTools to avoid conflict as it has no extra features I require.
[Captivate Android Development] mbc663:
This is incorrect. The semaphore app causes conflicts, but it is still functional.
[Captivate Android Development] krarvind:
my guess is stratosk removes nstools app in his script. Hence it force closes. Nstools need to be installed.
[Captivate Android Development] prbassplayer:
Didn't on mine.
[Captivate Android Development] krarvind:
well, then the other dude doesn't have nstools installed
[Captivate Android Development] bhairya:
Hmmm so in settings I have ASS, Device Settings and then NS Tools. When I click on NS Tools, the settings menu shuts down. It was opening fine before I installed Semaphore. Are you saying that I don't have NS Tools anymore? Is there a way to install or reinstall it? What exactly is NS Tools for? I do recall seeing BLN settings as well as scheduling silent times ie. no rings which I thought was pretty cool. How do I set BLN for voice mails, missed calls or SMS? Thanks, great ROM btw!
[Captivate Android Development] prbassplayer:
NSTools is meant for tweaking kernel settings, specifically kernels with Ezekeel's Live OC mod. The thing is Semaphore handles that differently. Both apps can work together but its better to just not touch NSTools at all, except for BLN controls. I looked over the update scrip I couldn't see anything that would delete NSTool but I'm no expert. My advice look fro NSTools in settings/apps and delete data, if its not there then the app got deleted as Krarvind said.
[Captivate Android Development] pqee:
This was my problem. NSTools wasn't installed. Reinstalling it from the market worked stopped the FC on settings.
[Captivate Android Development] bhairya:
OK that's the problem then. I don't have it installed. I'm assuming semaphore has the BLN hack in it?
[Captivate Android Development] kevinnol:
I cant use the Theme Changer, if I apply a theme i get a 'hotboot' bootloop :s
[Captivate Android Development] pqee:
From the changelog:

" Theme engine put in for future (unsupported/just for convenience) use. You might have to wait for themers to do it specific for Slim. Try it at your own RISK. Currently CM9/AOKP themes bootloops on SLIM. I put it in due to popular demand, no support provided from my end."
[Captivate Android Development] basily:
Can someone please tell me what permissions they have for the following files:

/system/media/audio/ui/Effect_Tick.ogg

/system/media/audio/ui/Unlock.ogg

I copied some notification and ringtones that I had backed up over to /system/media/audio and by mistake overwrote the ui directory as well. Now I don't have any "Touch sounds" or "Screen lock sound", even though the options are checked under Settings>Sound.

Oh, and I also cleared Media Storage data to get rid of duplicate ringtones and notifications, then rebooted.
[Captivate Android Development] krarvind:
644 or rw-r-r
[Captivate Android Development] basily:
Thanks, I set those permissions, rebooted. Still no sounds. Cleared Media Storage data and rebooted again. Still no sounds.

System volume is turned up, "Touch sounds" and "Screen lock sound" are both checked, but nothing. I wonder what else it could be? The sounds USED to work before I overwrote (merged) my /system/media/audio/ui directory...
[Captivate Android Development] topiratiko:
where do you adjust the time it takes for screen to flip when rotated??? I've done it b4 can't remember!!!

Sent from my Galaxy S Captivate on Slim ICS 3.6 w/Semaphore 1.0sc Kernel 1.220Ghz@122% live OC and 387mb available RAM. BUTTER
[Captivate Android Development] spacecase-25:
I'm having an issue where if I have a lot (11GB / 2400) songs on my SD card (internal or external) my free RAM will rapidly decrease to 0kb free and things become very slow (launcher restarting every time I close an app). It doesn't matter how long I leave the phone to do whatever it may be doing, the memory never comes back. If I don't load all the music, I idle around 50 - 50 MB free as expected.
[Captivate Android Development] psych0phobia:
Dev tools, development settings, transition animation scale.

Alternatively: settings, developer options, transition animation scale.

The second one actually has more choices available.
[Captivate Android Development] Ir0nLy0n:
When I set a transparency for the status bar it works for everything but the lockscreen.
[Captivate Android Development] SuperSync:
I have also lost my UI sounds (lock/unlock screen,button press, etc) ... reflashed 3.7 base and essentials and still no sound. Can play the files fine using the music player and permissions are good.
[Captivate Android Development] scottcwhite:
GPS issues I'm hoping can get fixed in 3.8 that weren't in 3.6. Tested on route to work. Running 3.6 GPS/nav stayed locked entire trip. 3.7 dropped 5 times . Then I found today that while driving and using NAV if you pull down the notification bar to check an alert, when you put it back up the NAV directions screen is just black and you have to force close the app and then restart it, put the address back in, etc. made me miss a turn today.

Sent from my Samsung Galaxy Tab
[Captivate Android Development] faroid:
I used a volume widget from the market to increase the system volume since there is no system volume level control under settings/sound... Sound is back now.

Sent from a Captivate using XDA

Sent from a Captivate using XDA
[Captivate Android Development] SuperSync:
Thanks...that worked!!
[Captivate Android Development] GreenWolf70:
I'm having a problem with the GPS too. All of the NAV apps will lock up my system so hard with a black screen that only pulling the battery will reset. Lots of SOD that I think are also attributable to GPS.
[Captivate Android Development] diakonos:
I've been seeing this more often as well. Occasionally My Tracks (while running) or Google Nav (while driving) will go into a blank screen (SOD) requiring battery pull or Vol-UP/Power restart. I've found that I have better luck if I use a separate "GPS location" app (I like Ulysses Gizmos) to get a location lock first, THEN use the tracking GPS app I seem to have fewer blank screens when trying to come out of lock mode.
[Captivate Android Development] spacecase-25:
I can't seem to set the min CPU frequency below 200 MHz. I've tried through ASS, NS tools, and a CPU control app from the market. It just keeps getting set back to 200. Any ideas?
[Captivate Android Development] prbassplayer:
As long as screen is on it wont drop to 100mhz.
[Captivate Android Development] spacecase-25:
But I should still be able to set the min CPU clock setting to 100 shouldn't I? Also, does that mean it drops to 100MHz when the screen is off rather than going all the way to deep sleep as it did in Gingerbread?