yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mrsubway:
Running your version and it works flawlessly! Not one fc and noticeably less lag. Great work! :D. Just a side note. I did a full wipe/format system.
[Captivate Android Development] brttwilliams:
I figured I would try it out to see if everything works, but I'm at a loss at what the difference is supposed to be, I haven't really ran into anything that has any display problems. What little I do know about the change in VSync is that it's supposed to make animations run smoother by allowing the GPU to synchronize the images it's buffering, jargon, jargon, blah, etc.... I'm sure it helps with those who have issues because of any super-detailed games they try to play, and I think I'll give it a run just to see if I can break it :)
[Captivate Android Development] prbassplayer:
We always had Vsync. This one doesn't make your cpu use more cycles than before.
[Captivate Android Development] Tsaukpaetra:
All this fiasco is kinda what reminds me why public betas are hit-and-miss. Oh well, it will settle by the time we have an official, neh?
[Captivate Android Development] prbassplayer:
Next release will have Vsync, when ever that will be. Lots of changes coming (not sure when though), probably new partition among other things. We will see. Whats "hit or miss" about public beta? Btw not really a beta Its exactly same as 2.5 just recompiled to support the new Vsync. I released so people had a rom to use with Stratosk's kernel :p
[Captivate Android Development] Tsaukpaetra:
The hit or miss is whether people understand it or not. For example, a lot of posts center around what the new requirements are, if the existing addons package(s) is still compatible, which kernels work and which don't, that kind of thing. And to top it off, since there really isn't a changelog between the VSync and Non-Vsync enabled builds, people are confused about the difference :angel: .

Hopefully though, people will actually spend more time reading the very informative posts that followed the announcement to really get an idea... but then again, who wants to read when we have a shiny Reply button just itching to be touched? :victory:
[Captivate Android Development] prbassplayer:
Sadly so true, people don't bother searching anymore. I mean if they know I'm maintainer why don't they bother searching my username in this thread? I've said the same thing 100 times across 3 devices. I know xda search is clunky but it does work.
[Captivate Android Development] m1batt1:
What is this "searching" you speak of? Sounds like some new fangled trickery to me!
[Captivate Android Development] pietroxda:
Installed slim-2.5.0-i897.zip gapps aio

Stepping outdoors for GPS Sat test
[Captivate Android Development] DKirk:
A quick note of THANKS for supporting his kernels in your ROM. I really enjoy the synergy between his kernels and your ROM efforts.:good:
[Captivate Android Development] pietroxda:
I got no birds at all with Sat test

So going in deep

http://xdaforums.com/showthread.php?t=1239713

Got there via searching a solution from mnazim

Caveat I have no idea what I am doing
[Captivate Android Development] powerserge1:
I too was having problems with GPS. I flashed the hellstrom fix just for the heck of it, edited the gps.conf file and used GPSaids to download all the data to the phone. Even with all that the GPS was not as good as it should be but leaving it on for awhile has fixed the issue. I just left Sygic on for a 1/2 hr and now I am back in business. Still not 10 out of 12 satellites with 5-10 meters but around 8 satellites max within 10-15 meters.

I upgraded from SlimJB 2.2 to 2.5. For the past year my GPS has been fine until now using various ROMS out there. Took some playing around to get it working but it's decent now. I wont be upgrading until the next major release, it took quite some time to get this going.

Before anyone says "I don't get satellites" or "I cannot get a consistant lock" let the GPS run for a bit and see what happens.
[Captivate Android Development] tkjeeper:
Odd, I got within 15' in less than 10 seconds, no fixes at all!
[Captivate Android Development] tonyzz:
I have been running this rom for about a week updated to 2.5.0 and still great thanks for the great work my phone is the faster ever no bogging or FC battery life has been great for me GPS great have not found anything in my opinion that needs to change

thanks again

Sent from my SGH-I897 running slim bean
[Captivate Android Development] pietroxda:
Alright created new gps.conf and applied it with Root Browser

Tried to clear and reload AGPS data, unsure if this worked - may go with injector http://xdaforums.com/showpost.php?p=16384028&postcount=1907

Phone is sitting outside trying its best at the moment
[Captivate Android Development] powerserge1:
Ya it is weird, I'm sure this is nothing to do with the ROM. Or if it is something minor, the GPS can be fixed with the tools out there. On an earlier version of SlimJB there was a "GPSfix" to apply and that worked because my GPS would not lock otherwise. After flashing the fix all was well again. that's why i was asking if we should do the same for this version or not.
[Captivate Android Development] onlyu132:
I found that when combine this rom with devil kernel 1.5.2, it was smooth at the beginning, however after that, it began to lag here and there, sometimes apps FC and reboot if you use too much app at the same time. But with semaphore kernel, everything ran smooth. Still testing. Tell me whether it's just my personal feeling. The rom is so good, so smooth so far. Thank you for all the hard work !!
[Captivate Android Development] mrsubway:
I've found no reason to switch from Semaphore. It's like the ROM and kernel were made for each other. Butter.
[Captivate Android Development] RDI:
A long time ago, there used to be a way to block calls from certain phone numbers from the rom. I assume that feature's gone for good now. There are times I miss it.

Sent from my Samsung Captivate running 4.1.1 Slim Bean v2.5 w/KG3 Modem
[Captivate Android Development] DKirk:
For those of you with GPS issues. I tried everything that was supposed fix to get my phone to see anything more than 1 satellite, always just one. I would clear everything I could and flash the ROM over and over, restore with Titanium my apps, and every time I would see only 1 satellite. This last time I did the usual clear everything, flash ROM, and then only restored a handful of the most essential apps and this time the GPS worked as good as it ever has, seeing 11 birds instead of 1, and locking quickly. I ran titanium backup again and restored the rest of my apps (no system data, just apps) and once again the GPS began to fail. Some app that I have is killing my GPS after a restore. Again, I'm not restoring system data, only user apps and app alone, no data.

Clear everything, reflash, and the GPS is back. This time I am only restoring apps, one at a time, as I need them.
[Captivate Android Development] UserNamer:
GPS issues: Try a different modem from this link.

At the top of that page is a text file named "i9000_release_dates.txt" which lists the ones which default to 850mhz. If you're on AT&T in the US, try one of the "850mhz default" ones. After having horrible GPS using the default modem in this ROM in the NY metro area on AT&T, I switched to the BVJJW2 modem and get almost instant locks which don't drop.

Your mileage may vary.

On a different note, is there any chance you'd consider supporting AutoPatcher in Slim Bean? It adds support for PDroid from the Play Store to ICS and JB (PDroid provides more granular security options to Android, requiring specific permission for access to a ton of services). There have been a few requests in that thread, but they've had difficulties with Slim Bean and they need someone who understands the ROM and development.
[Captivate Android Development] thuanngotau:
Could sb suggest me another modem instead of KG3 to flash with SlimBean? I'm tired of weird behavior of my phone when switching/turning on off 3G/2G and network connection: very unresponsive and slow...

It might not be the problem with modem at all but... I really don't know why! (Don't blame me on wrong procedure of flashing and/or apps related issues)
[Captivate Android Development] m1batt1:
http://soggycashew.weebly.com/cm7miui--ics-modems.html Here is an extensive list of modems available. Make sure you flash the ones labeled cm7 because the others will fail to flash. Also on the main page of the site there is a map that shows what modems worked best in their area.

I personally use kg3 and don't have issues but then again I don't think I've ever toggled 3g/2g so I don't know if it's an issue or not.
[Captivate Android Development] scottcwhite:
Thanks for the info
[Captivate Android Development] so_iccy:
Please can I nandroid backup this rom
[Captivate Android Development] Shoey Peachew:
BVJJW2 Modem works great in San Francisco. I've been trying to fix it forever.Thanks!
[Captivate Android Development] tkjeeper:
Of course
[Captivate Android Development] lordxentris:
GPS issue might be something to do with the Radio version, might want to try flashing best know ones, and check it out. Always be outdoors and clear sky for quicker lock. Mine locks in immediately after opening Maps, about 5 to 10 seconds, Accuracy to about 1 Meter. :)
[Captivate Android Development] bobo122:
I gotta admit the performance is great , but the battery life here is awful .. I had 150-200% battery on helly bean .. anyone else is experiencing this issue? I'm barely having 6 hours at light use!!
[Captivate Android Development] pietroxda:
Hardware fault certainly

Off to nearly expired SquareTrade warranty service, seems as though with its prior screen replacement they killed it

Its back to fully stock 2.2, sat icon appears for 0.5 seconds and goes away
[Captivate Android Development] Tsaukpaetra:
Go to the contact you want to block, hit the Menu button, checkmark "All Calls to voicemail"
[Captivate Android Development] prbassplayer:
GPS is a hit or miss. I can say mess with the gps data with market apps (example GPS Aid) and you can get it to get a decent lock regardless of the hardware.
[Captivate Android Development] Shoey Peachew:
Unfortunately, I can't use this modem. My data speeds are Like .2 Mbps. Gps works great though
[Captivate Android Development] grndnl:
wait hold on, so why are we isntalling the i9000 modems, and not the i897 ones?

Also, do we have to do the modem dance? What is the modem that comes with this ROM?
[Captivate Android Development] mopo01:
cause the rom is based on i9000 no modem dance if you donnot want to :confused: and this rom does not come with a modem you keep the one you had from wherever you came from :cool:
[Captivate Android Development] diakonos:
I did confirm the card went bad. So, I got a new card and re-copied my backed up files to it and the new one is working fine in my i897. I then tried the old card with a USB reader on my computer and it said the card needed to be formatted. Once I did that it appears to have resurrected my old micro SD. I guess I have a backup card now...
[Captivate Android Development] onlyu132:
I have problem with bluetooth, I can't turn on bluetooth. I'm on semaphore kernel and slim bean 2.5v. Anyone experience this? Any advice to fix this? And I see that I choose smartass v2 governor in semaphore manager but in setting> performance> processor speed, the governor is still Ondemand, so I don't know whether the kernel switch to Smartassv2 or not?

By the way, one more noob question, should I turn the option" force GPU rendering" in developers options on? Is it good for performance, or battery life? Anyone tried? Thanks.
[Captivate Android Development] xisque:
I found the instructions to install this rom a bit confusing, looks like more a kernel than a rom. Anyway, it killed my efs folder (ill restore it later and I cant blame CM10 or Slim).

But I found you SHOULD reflash even if it looks sucessful at first time.

Too bad the developer removed many languages from the source and leaving only 6 in this rom.
[Captivate Android Development] pickupman66:
So, been on 2.5v since a few hours after release. I am getting good battery life and great GPS. I live in a rural area and use the T959TLJL3 Modem. Screenies for your amusement.

The GPS lock was within 18 seconds of launching the app. give it another 5 and I had this lock. I used fasterfix to change the datapool to north-america.pool.ntp.org

battery....I have Live OC set to 110% with NS tools. this is the original battery i got with my phone. it is almost 2 years old.

By the way, both screenies were taken on the same day so you can see how the battery performed.

---------- Post added at 10:04 AM ---------- Previous post was at 09:59 AM ----------

xisque. the languages are removed to "slim" down the rom. I only speak english and a little spanish. anything else is completely un-necessary for me.
[Captivate Android Development] ManuelZRO:
WiFi

I have 3 days with this ROM, and it's amazing how fast it goes my captivate, fairly stable but I have a problem with WiFi. The WiFi works well when the phone is in use to lock the screen but it stops working (if kept on), the problem is that when I download a file to lock the screen and the speed drops considerably (2Kb/s). Any solution to this problem? This only happened to me with CM7 ROMs.

Sorry for my bad English.
[Captivate Android Development] prbassplayer:
I'm currently running a test run with new CM10 Partition layout. If all goes well when Stratosk releases kernel I'll release a unofficial release.
[Captivate Android Development] dank8885:
Just a heads up but the "news" link on the site gets 404 category not found error. Sorry if it is just being edited or something but just wanted to toss that to ya.

Also, 2.5V is amazingly responsive, thanks so much for what you do.
[Captivate Android Development] prbassplayer:
I effed up something in the site. Tortureduck is saving the day. Be patient.
[Captivate Android Development] sa1yan:
Sorry if this has been answered before, but I can't get my settings in the Semaphore app to stick. I enable OC and change the scheduler but when I look at my phone info, it is at stock values. Even after a reboot, no options in the Semaphore app work.

Anyone else have a similar problem? Or what other Semaphore kernel should I use with the latest Slim Bean?
[Captivate Android Development] onlyu132:
+1
[Captivate Android Development] pickupman66:
Try NS tools. It was designed to work with the kernel. That's what I use. Love it!
[Captivate Android Development] ztotherad:
@krarvind would it be cool if i built your rom (slim bean) from source, for the fascinate? if i post it ill give you & your team (?) credit, but i wanted to ask before i did
[Captivate Android Development] krarvind:
I always encourage building from source. Just make sure to link my website and add credits. Cheers
[Captivate Android Development] ztotherad:
thank you sir, i appreciate it :) ill give credit to the proper people and the links
[Captivate Android Development] prbassplayer:
Guys http://slimroms.net/ Goes without saying no unofficial release ;)
[Captivate Android Development] Wakamatsu:
Sounds like there will be lots of changes under the hood. Will a full wipe be required coming from 2.5?
[Captivate Android Development] prbassplayer:
New partition, full wipe required. The zip should warn you.
[Captivate Android Development] kufikugel:
Hey guys......

http://xdaforums.com/showthread.php?t=1911941

have fun ;)
[Captivate Android Development] dank8885:
No you miss read, just download them to your phone, enter CWM, factory reset, format /system, flash device.zip, flash common.zip

A few of us got a reboot to a splashscreen after flashing device.zip (android in middle of a diamond shape with black/grey bubbly background), if that happens reboot to recovery and flash device.zip again then flash common.zip then you should be fine. Make sure when you flash device.zip it takes more than just a few seconds.
[Captivate Android Development] prbassplayer:
Flash device first (it will probably reboot and loop)

Get in to recovery (by using CWM or, if it looped, pull battery and use key combo)

Factory reset & Format /system

Flash device then common

???

profit
[Captivate Android Development] :
Wipe, flash device then common, reboot.
[Captivate Android Development] scottcwhite:
Bass is stating otherwise so I'll go that route
[Captivate Android Development] prbassplayer:
They stated as its in the instructions. However Krarvind wrote does before leaving and it seems the biggest issue people are having is the fact the rom reboots after a second on hitting install. Probably because the difference in kernel. So flashing the rom first will get you that kernel and continue with the flashing. The wipe shouldn't matter if its done before or after the initial flash. BUT I think this method will maintain everyone in same kernel/recovery more unified. I won't update the instructions until Krarvind is back and I speak with him
[Captivate Android Development] scottcwhite:
Well slap me silly and paint me pink :silly:

Young Grasshopper understands now. (That's from Kung Fu for all you young uns)
[Captivate Android Development] basily:
So what's the significance of no /datadata? No more out of memory error when I have too many apps? How do I know if I have a faulty NAND? Why would that happen?
[Captivate Android Development] prbassplayer:
The reasons for eliminating /datadata is the fact JB (full rom not slimmed down) is so big we need a bigger /system partition. The pro of this is well no more low storage warning and you could use a full rom no problem. The cons is a crappy NAND will lead to alot of lag. It seems samsung sucked at quality control and our NAND chips all have very big differences in r/w speeds and slow ones will lag.
[Captivate Android Development] azunino:
So now it seems we'll have to find a workaround... such as running JB from an external SD?
[Captivate Android Development] :
Or just using the devil with /datadata
[Captivate Android Development] prbassplayer:
I'm pretty sure ExtSD is slower than NAND. I will have to test it out later on.
[Captivate Android Development] basily:
Is there a way to check the r/w speed of our NAND and compare it to what others have?

I have no intention of installing Slim Bean at the moment as I'm "all flashed out" right now and am just happy to have a phone (Slim 4.2) that's running beautifully. In fact, the only reasons I would consider installing Slim Bean (or any JB ROM for that matter) is for the reputed buttery smoothness, and for the offline voice recognition.

So is it buttery smooth? Or are people experiencing lag?

Does Slim Bean include the offline voice recognition or did that have come off to keep Slim slim?
[Captivate Android Development] stoehner:
Why are all the ASS settings missing? I get like 3 categories. What's up with that?
[Captivate Android Development] mopo01:
Read up on the web site that is what is available right now , remember this is the first build, he will get there. :cool:
[Captivate Android Development] prbassplayer:
Lol ya because you want all the features that was on Slim ICS 4.2 on Slim Bean 1.0... Yup makes perfect sense :rolleyes:. Still have other things that are more important like how to resolve the lag on bad NAND phones, no HSUPA, fact stock kernel is having trouble playing HD (720) videos, etc. So be patient ;)
[Captivate Android Development] thunor:
Thanks so much!!! Slim ICS, in my experience, is the best ICS ROM out there for the cappy. I've been trying Monfro's ports of DerTeufel's CM10 Devil, but never really had a very good experience with them (still much appreciation and mad props to both of them for putting out that stuff for us). I was always hoping you'd come out with a JB implementation, and now you've fulfilled my wishes. I'm sure Slim Bean will be just as awesome as Slim ICS. LLS!! (Long live Slim!!!)

Sent from my Awesome Slimified Cappy, running Slim ICS 4.1...Soon to be Slim Bean in a little while, Buahahahaha!!!
[Captivate Android Development] thunor:
I'm currently using the themed Swype apk from Docs Master ICS v12 on Slim 4.1. Does anyone know if this will also run in Slim Bean?

Sent from my Awesome Slimified Cappy, running Slim ICS 4.1...Soon to be Slim Bean in a little while, Buahahahaha!!!
[Captivate Android Development] baconatorXVI:
So I'm going to be in a 3rd works country for a few weeks(haiti) soon, odd question, but should i bother flashing jb? I need to know if it's stable enough. I'm really eager to try it out ya know.

Any issues restoring app's with data with titanium backup?
[Captivate Android Development] shaker2k:
I would not risk it. I ran derteufel's cm10 and it was fine for a while then started acting up. Just use slim 4.2 till you come back. When you do it will have that much more time to get better.
[Captivate Android Development] prbassplayer:
What shaker2k said. Although Its running real smooth for some, doesn't mean it will for you. And this build has a whole1 day out ~3 days testing and don't know how it will act after a while.
[Captivate Android Development] prbassplayer:
Site is down

Problems with the site seems to be provider sided. Please be patient :)
[Captivate Android Development] wickerstick:
Been testing the latest for a week. Last night the camera broke. Is say that gallery could not start. But I can open up gallery no problem. I've wiped cache and rebooted the phone and killed the aps but I can't get the camera working was hoping not to have to reflash. Plus I wanted to see if anyone else has had the problem
[Captivate Android Development] m1batt1:
Did you by chance mess with settings in the camera and accidentally hit the forward facing camera option? Did that once and it screwed all kinds of stuff up.
[Captivate Android Development] kafepuya:
I have been having problems with the camera as well, and have been since 2.1. However, since I am traveling I have not been able to upload a logcat so prbassplayer or krarvind could take a look. I did flash Lanaight 6.0 and 5.2 and the camera was not responsive in either one. This leads me to belive that I am experiencing a hardware problem (possibly broken camera) rather than anything to do with Slim.

I recommend you upload a logcat.

Sent from my SGH-I897
[Captivate Android Development] prbassplayer:
2.6 has been released. Flash device 3 times it will wipe data so be warned.
[Captivate Android Development] grndnl:
Hello Everyone, I messed something up in my latest flashing excapades.

Here is what happened:

Download 2.6 via OTA for i897

reboot into recovery

wipe cache & dalvik

install 2.6

ERROR: [status 7] during installation.

wipe cache and dalvik again

install 2.6 again

phone shuts off, when I reboot it stays on the AT&T screen

reboot into recovery

wipe cache + dalvik

install 2.5 + gapps

reboot

NOW the phone still won't go past the AT&T logo.

What is happening? Any advice would be GREATLY appreciated.

---------- Post added at 09:21 PM ---------- Previous post was at 09:20 PM ----------

in the changelog it doesn't say that it will wipe data...
[Captivate Android Development] prbassplayer:
It's a new partition layout it was going to magically keep all your data. As for help mistake 1 didn't read my post. Mistake 2 you flashed 2.5 in the end. Get to recovery and flash 2.6 3 times. If you lost recovery ODIN semaphore.
[Captivate Android Development] kafepuya:
The first thing prbassplayer specifies is to flash three times. According to your post, you flashed only once. Also, 2.6 has the new cm10 partition layout, which should be a give away that you must also wide data (even though the installation wipes data, you should not leave that to chance, since installations can get fubared, as it was in your case.)

EDIT: ninda'd :sly:

Sent from my SGH-I897
[Captivate Android Development] grndnl:
well that was very explanatory. thanks.

---------- Post added at 09:44 PM ---------- Previous post was at 09:32 PM ----------

So I can get into recovery. but when I install 2.6, no matter how many times after wiping everything, I get ERROR status 0.

Also, when I wipe data, it doesn't go through the whole usual process, but the screen just flickers and it returns to the usual recovery screen.

Why?