yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] prbassplayer:
Works just fine on Semaphore app. It also worked fine on 2.0.
[Captivate Android Development] m1batt1:
I guess that would be my bad... I found the fast charge toggle in the settings menu and then missed the checkbox for it in the semaphore app... Checked the box and all is good. So all things are beautiful now :D
[Captivate Android Development] noone.dk01:
next version of slim bean should has feature capture screen when press power button :D
[Captivate Android Development] krarvind:
Sure. Code it up. I will put it in
[Captivate Android Development] pulsorock:
What kind of problems are you having with bluetooth? Did you find a solution?

I'm running SlimBean 2.1 on my Captivate and it seems that it has some bluetooth issue. I use my Captivate as a music player and connect to my sound system via bluetooth, and I'm getting disconnection and music skips, like the bluetooth is missing connection.
[Captivate Android Development] jjlwork:
So I've been running 2.1 since it came out last week. Everything seems smooth with the exception that from time I get a "soft" boot. I say soft boot as it goes to the slim animation screeen like it does on boot and then loads back to my homescreen.

This seems to happen frequently when using high memory apps like watching a video, but sometimes just happens at random. It does not usually happen while watching the video, but rather if I pause and walk away and come back to resume watching I'll notice it is in the process of the "soft" boot.

It also seems to happen more frequently after updating to latest version of Holo launcher.

To try and narrow down the problem, I re-flashed and only installed my "essential" apps and refused updates on the Holo launcher. It still seems to be happening less frquently but still happpening.

I did notice on the bug report that there is a bug with soft boots on landscape lock, which is typically my orientation when watching videos, however I've had it happen without going into landscape as well.
[Captivate Android Development] prbassplayer:
Read the bug list, this sounds like the landscape issue
[Captivate Android Development] Veight:
So, I am sitting here looking over some stuff and I notice my phone decided to do a hard reboot and then go into recovery. Thought that was quite odd so I powered it down and reboot it. Now for some reason it's not booting the OS at all. It just sits at the Semaphore boot logo.

I've been running 2.1 for the past week now and besides the random soft boots, everything has been fine up until now.
[Captivate Android Development] prbassplayer:
Did you add any init.d, tweaks or messed with anything at all?
[Captivate Android Development] Veight:
No, I haven't adjusted anything in awhile. Just been using it normally.
[Captivate Android Development] prbassplayer:
Attempt to flash the newer Semaphore kernel and try to see if it boots up, else you can try to delete init.d scrips if you are tempted to play with that. Last is Dirty flash rom again. Can't say what caused it though but trying flashing newer semaphore probably least evasive method.
[Captivate Android Development] Veight:
Well, i said screw it and just re-flashed. Luckily, I forgot to wipe data and it just booted up without any issues. I'll flash the new kernel just in case.
[Captivate Android Development] mrsubway:
I wonder if someone here can help. I was originally on Slim Bean, but had a problem. Needless to say, I Odin one clicked back to a Gingerbread Rom. It seems I can no longer get past Gingerbread. I followed the instructions here to try and install CM10. I even formatted system. No matter what, the phone installs CM10, but then just boots into recovery. I've tried installing Slim ICS, Slim Bean, etc, and always have to Odin back to GB. Are there any Odins out there that are ICS or JB? Please help.
[Captivate Android Development] prbassplayer:
Stop flashing back to GB. No there is no AOSP odin. Whenever you loop or stuck rewipe reformat system and reflash. At worst ODIN a JB kernel if you loose recovery
[Captivate Android Development] sailzfast:
Long story short:

Was on SlimBean 2.1

Borked phone

Odined back to stock JB 2.3.4 (all worked fine)

Factory reset/wiped data/wiped delvik

Flashed CM9...worked fine for 5 minutes til opened play store, which wanted to reinstall all my apps...allowed play store to start reinstalling

Got notification that SD card is damage

Most app Icons disappeared, including play store.

Transferred SlimBean 2.1 device/common zip to phone via PC.

Factory reset/wiped data/wiped delvik/reset system and flashed 2.1.

Everything works fine...but still get damaged SD card notification.

Any ideas? Did I miss a step somewhere?
[Captivate Android Development] mrsubway:
Have tried what you have suggested many, many times. No luck. Still just boots into recovery.
[Captivate Android Development] prbassplayer:
Don't know what to say apart from changing to latest Semaphore and inverted apps I haven't messed with this rom at all and haven't had any issues. =/
[Captivate Android Development] mrsubway:
Phone won't take ANY roms other than Gingerbread stock or Mosaic. CM9, CM10, Slim ICS, Slim Bean, all give the same result. Boot into recovery. I'm at the end of my rope.
[Captivate Android Development] hellomynameis:
What is the "Extra's"?
[Captivate Android Development] whoflung15:
I also have blue tooth issues. On GB I could connect my phone to my car and I could send music through to my car just fine. I than moved to slim ics and I can talk through my car just fine but the music does nothing and this also happens on slim bean. I have tried cm9 and it worked. Not sure what to do, any help would be appreciated.
[Captivate Android Development] Wakamatsu:
http://www.slimroms.net/index.php/addons-and-common-app-list

Scroll down a bit.
[Captivate Android Development] Tsaukpaetra:
Uh Oh!

Not an issue yet, but for some reason the LCD Brightness controls don't work anywhere. Even a work-around app (RootDim) can't seem to tell the display to do anything at all.

Also, in the ASS settings, the "Choose notification background" and Alpha transparency options in General UI don't seem to work properly. The cause the framework to restart, but nothing appears changed.

I'm going to attempt a reflash and post back, but this seems oddly quirky, especially the brightness...

{{Edit}}

Nevermind on the brightness thing, must have been a glitch or something...

Would enabling the Notifications Count affect the notification background setting?
[Captivate Android Development] unglued94ta:
This is how I got slim bean to work...

1. Odin one click back to eclair without boot loaders

2. Super one click root

3. Flash cwm from stock recovery

4. Flash cm9

5. Flash slim bean 2.0

6. It booted part way through the install and went right back to recovery so I flashed it again.

7. Flashed 2.0.1

8. Booted and changed script for the 2.0.1 update

Of coarse I wiped date, cache, dalvik 3 times each between each ROM flash after I rooted except for right before step 6.

Very time consuming but it worked.

Good luck
[Captivate Android Development] ChuckDaEngineer:
Try flashing Doc's Master V12. That seems to set up a stable base and then do the three clears and then format system. After that I have successfully flashed a couple of problematic JB roms (AOKP August 1 edition and SlimBean specifically). This never helped me on Team Nyx though. I still haven't been able to flash that. I always start from Doc's Master when messing with JB ROMs.
[Captivate Android Development] unglued94ta:
:D it's because of docs v12 and being stuck at the att logo and losing access to recovery when trying to flash slim bean the first time that I went back to eclair and started from scratch.
[Captivate Android Development] kafepuya:
I can confirm that sometimes Slim Bean does a soft reboot as Jjlwork stated. Today I have had three soft reboots in less than an hour, while the phone was doing completely different tasks. The first time, I was caching music from Slacker. The second time I had just viewed a message in Handcent SMS, and the third time I was using Google Maps in Landscape mode.

I downloaded and installed aLogcat so I can provide a logcat next time it happens (if it does happen). I was wondering if someone could tell me the correct setting for the program, and as the setting are very expensive, and apparently they affect the level of activity it records.

EDIT: I have the following setting in aLogcat:

Level: Fatal

Format: Raw

Buffer: Events

If I have it set up wrong please let me know. Thanks.

Sent from my phone...
[Captivate Android Development] prbassplayer:
Or you could just open terminal and type "logcat > nameoffile.txt" and works just the same ;) no quotations

Edit: Also make sure you have logger enabled in semaphore app (if you are using semaphore kernel) and it should read "logcat > /sdcard/name.txt" ;)
[Captivate Android Development] kafepuya:
I am using Semaphore kernel. Good to know, when I saw those settings I was like "crap what do I do now"...

Sent from my phone...
[Captivate Android Development] jjlwork:
Looking at the changelog for 2.2 it looks like it will be fixed on the new release. For this release(2.1) I've had great success by turning off auto-rotate, no soft boots since then.
[Captivate Android Development] mrsubway:
YYYYYYYYYYYYYYYYYYYYYYYYYYEEEEEEEEEEEEEEEEEEEESSSSSSSSSSSSSSSSSSSSSSSSSSSS! Finally! Thank you so much!

---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------

Anybody know how to get the menu to change modem frequencies, IE *#2263*?
[Captivate Android Development] prbassplayer:
Not available I believe could be wrong.
[Captivate Android Development] m1batt1:
Its not available through the ROM as it sits. I have an idea as to how you can add the option but I'm at work now so I'll try it later and get back to you.
[Captivate Android Development] kafepuya:
I also turned auto rotate off. I don't normally have it on but I recently started using it. Ever since I turned it off the soft reboots have stopped.

Sent from my phone...
[Captivate Android Development] SynGamer:
How is SlimJB 2.2? I tried 2.0 and it was extremely laggy on my Captivate, and this was after I flashed to stock, then CM9, then SlimJB. I'm back on SlimICS 4.2...but the JB calling is getting harder to ignore.
[Captivate Android Development] prbassplayer:
Lag pretty much gone. Now we are using Cm10 partition layout. Apart from the bugs listed in bug list running solid for me.
[Captivate Android Development] m1batt1:
Ok so as I suspected I can help you out with what you want to do. In order to make that happen you will need to install the Samsung Service Mode apk. Which I have supplied in this message. Here is what you'll need to do.

1. Get some sort of file manager that will allow you to remount your system as r/w. I use ghost commander but a lot of people like root explorer. Doesn't matter as long as it can remount as r/w.

2. You will then need to place the apk into /system/app/

3. You will then need to fix permissions before it will run. I started by trying to simply reboot into recovery, fix permissions, and reboot. I didn't think to try the *#*#2263#*#* because the last time I did this I was on ICS and it actually created an icon in the drawer. So it may work for you by just fixing permissions in recovery. I however went ahead and changed the permissions in terminal emulator and then rebooted. After that I am sure you should be able to use the code and enter the menu you are looking for.

Additionally if you have to manually change permissions with the terminal emulator make sure you capitalize the file name where it is in the command... You may already know to do that but I had a hell of a time getting it to work the first couple times I ever did it cause I wasn't using capital letters and it kept kicking back errors.

Anyway I hope this was helpful and works for you.
[Captivate Android Development] raz123:
What's faster between Slim ICS and Slim Bean?
[Captivate Android Development] hellomynameis:
I must be blind, but I can not find the download for 2.2
[Captivate Android Development] dank8885:
2.2 is WIP current version is 2.1

http://slimroms.net/
[Captivate Android Development] sailzfast:
OK I'm back. I reinstalled extras zip from update me and the damaged SD card notification disappeared. Everything running flawlessly now.
[Captivate Android Development] prbassplayer:
1) Subjective

2)Subjective.

Make a Nandroid backup and flash and test for yourself. The real lag problem was solved in 2.1.
[Captivate Android Development] SynGamer:
So I flashed 2.1 from ICS 4.2 and my screen is stuck in landscape mode...I've tried toggling the rotation option but nothing works.

EDIT: I unchecked auto-rotate in the settings and when I do that it's fixed. However, when I select auto-rotate, the screen goes back to landscape regardless of the position of the phone...
[Captivate Android Development] tkjeeper:
The fact that you're asking this same cut and paste question in every jb rom is embarrassing. It shows you're lazy and want every one else to do the work for you. Go pound salt!
[Captivate Android Development] krarvind:
Ok fellas, 2.2 released. Please read the changelog carefully and get the download from download tab on the website. This release needed a lot of effort would be an understatement that my betas would appreciate. Anyway show support via thanks/donate. Please don't fill up the thread with known issues and minor issues.Cheers
[Captivate Android Development] OwenW71:
Flashing now, but rather than the CWM status bars i'm used to, the phone rebooted itself and is stuck at the 'powered by Semaphore' screen. Been waiting a while, but no change. I don't recall flashing any other ROM that went right to a reboot during the flash without letting me prompt the reboot in CWM.

----Update----

Got sick of waiting and pulled the battery. Rebooted into recovery using three button combo. Ah HA! In Semaphore CWM now. Reflashed i897.zip....things look better now. Flashing common.zip next.
[Captivate Android Development] Tsaukpaetra:
Yep; that's one of the known quirks, ya gotta read the manual!
[Captivate Android Development] mrsubway:
Just want to make sure my flash went okay. In about it says Slim version unknown. Is that normal? Also I have the notification bar on with one button to kill tasks. Since the upgrade that button now fcs the ui.
[Captivate Android Development] prbassplayer:
Did you full wipe and flash both device and commons?
[Captivate Android Development] mrsubway:
This is a full wipe? No I didn't. Will now.
[Captivate Android Development] prbassplayer:
If stuff don't work wipe and try again :). Considering krarvind made a framework overhaul I'd recommend wiping.
[Captivate Android Development] mdoctor:
I did a full wipe install of both device and common, but I still get Slim version unknown. Is that a bad flash???

Also, after installing just a few apps I get a out of space message. Is that normal too???
[Captivate Android Development] prbassplayer:
Where exactly you getting that? OTA or elsewhere?
[Captivate Android Development] mrsubway:
Same. But no low space. To be honest if hold back to kill were an option I wouldn't care. Formatted system too.
[Captivate Android Development] basily:
Changelog says it's an option - isn't it?

"Enable hardware back key to kill app via settings/developer settings/apps"
[Captivate Android Development] prbassplayer:
It seems its a build prop error. Ignore it as of now,shouldn't mess with anything.
[Captivate Android Development] mrsubway:
Read the changelog and missed that. Now I could care less about the nav bar, as that's all I was using it for. :D
[Captivate Android Development] mdoctor:
Actually its not updating some larger apps from the Play Store stating the lack of space issue. When I look at the internal storage, I only have 422MB total. Is that correct???

Edit: I am going to try to re-install everything from Odin-2-GB forward... Maybe it will fix my low space issues???
[Captivate Android Development] prbassplayer:
Please search before asking. I've answered that like 100 times :)
[Captivate Android Development] OwenW71:
All done flashing and restoring....and SlimBean 2.2 is running very smooth and fast. A few very minor annoyances....no option to set wallpaper to 'None' or a single color, and the automatic Backup & Restore of apps that I love so well is not working. I'm assuming that has to do with the version change from ICS to JB, and based on that assumption, I did not use TiBu to restore, but pushed everything back from the Play Store. The weather on the lockscreen is a very nice touch, but it refuses to update my location, so I'm not sure how good it'll be long-term.

Overall, very nice. I like the speed and lack of clutter. All apps seem to be running very well. No serious issues with setup, and it seems stable enough to be a solid daily driver. As I posted earlier, I had an unexpected reboot as the flash installed a new version of CWM which necessitated a battery pull and reboot into recovery. I did a lot of reading prior to installation, but I must have overlooked that quirk.

Kudos to krarvind and team!
[Captivate Android Development] krarvind:
Set custom location

sent from slimmed i747
[Captivate Android Development] Tsaukpaetra:
I noticed that too, must be missing from the cyanogen cherry picks? For now I suppose a workaround would be to create a single-color jpg whatever you want and set it using the gallery selection...

I myself have never gotten the "Backup using google" and "restore this phone from google" to do much of anything, not entirely sure how to invoke it. I always tick the options, but nothing happens :P .
[Captivate Android Development] OwenW71:
Backup and Restore worked great for all my ICS flashes, but did not work this time around.

Maybe I'll take a picture under a blanket and use that...:)

Sent from my Jellybean Captivate.
[Captivate Android Development] kafepuya:
I'm having trouble downloading 2.2. After I download it, I flash it, yet it still shows the version to be 2.1. I re-downloaded the rom, but when I look at build.prop, this is what I get from line 3 through 9

ro.build.id=JRO03L
ro.build.display.id=2.1
ro.build.version.incremental=eng.ar.20120812.082226
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Sun Aug 12 08:25:06 ADT 2012

Has anyone else come across this situation?
[Captivate Android Development] zzmomo73:
Error in build.prop shouldn't effect anything, you still have slimbean 2.2 on your device
[Captivate Android Development] Wakamatsu:
I think it affects the Update Me apk.
[Captivate Android Development] m1batt1:
Ok so where did the Fast Charge toggle go on 2.2? I know it was there in 2.1 because I was an idiot and didn't enable it through the kernel first and therefor thought the toggle was broken... Now unless I'm a complete idiot(which is entirely possible) it is not longer available... I did find an option to turn it on in the performance tab of settings as well as in Semaphore app.
[Captivate Android Development] prbassplayer:
No because UpdstmeMe uses other inputs in build.prop.

Nope not available in toggles just in performance @ settings. Maybe later. Also still need to enable on semaphore app. ;)
[Captivate Android Development] m1batt1:
So sad :crying: Oh well... Everything else looks great! I've even managed to do a small liveOC and not get hit immediately with reboots! Great work all around.

One thing I am curious about is ability to access GPS settings. I have found a solution but I've noticed at least on the JB roms I've used that there is no ability to tweak GPS settings by default.
[Captivate Android Development] kafepuya:
You are right. After playing around some more with the ROM I was able to tell the difference. I couldn't edit my post because my wife was giving me the evil eye...you know how it is...:cool:
[Captivate Android Development] Wakamatsu:
The toggles were changed from AOKP in 2.1 to the current one. I couldn't find the toggle for fast charge either.
[Captivate Android Development] sailzfast:
Angry Birds is making my phone go wonkers...anyone else?
[Captivate Android Development] prbassplayer:
I'm out but when I get my hands on my i897 ill test.

Edit: working just fine on my end.
[Captivate Android Development] MarcianoS:
All working just great here. My Cappy has never run so smoothly! My only problem is that I can't seem to restore Google Play from TiBu. The restore process just hangs. Not sure it's a SB issue though.

Also, not a bug per se, but I kinda liked having the hardware search button trigger Google Now. Right now, pressign the search button does nothing, and Google Now is assigned to a long press of the menu button, which I don't find to be as convenient. Yes, I know I can reassign the menu button, but I wish I could restore the 2.1 behavior. No biggie.
[Captivate Android Development] kalda01:
What is the GPS FIX patch ? does it apply to all devices ?
[Captivate Android Development] AceofSpades90:
Yes it boost satellite locking at expense of accuracy. Its in my Lanight build in signature.
[Captivate Android Development] Tsaukpaetra:
Well.

I'm assuming you're talking about the notification that was sent via Update.me. It stated to flash only if you were having issues getting a lock, and potentially affected devices were listed as well. Honestly, don't fix what ain't broke, but it won't hurt in either case.

It looks like it just updates files libandroid_servers.so and libandroidfw.so.
[Captivate Android Development] kafepuya:
Speaking of GPS, the fix by Mnazim is mentioned in the changelock. I've been using H3llstorm's GPS Fix for quite some time, including SlimBean 2.1 and it has worked well for my purpouse (running apps). Im going to give the Mnezim fix a shot and post the results.
[Captivate Android Development] kafepuya:
OK here are the results from my tests:

8 NTP GPS MOD:

Slim Bean 2.2 GPS FIX BY MNAZIM:

H3llstorm GPS Fix:

These results were achieved by placing my phone in the same place and waiting a minute after GPS lock on Google Maps and GPS test.

It is possible testing method is flawed, since I flashed the fixes in the following order: 8 NTP, MNAZIM fix and finally H3llstorm GPS Fix.

Note: Both MNAZIM and H3llstorm fixes showed 16 feet accuracy, but it only lasted for no more than 5 seconds, before going back to 49 feet, then settling on 33 feet.

Hope this helps someone!

Sent from Slim Bean powered phone...
[Captivate Android Development] jvc73:
You need to use a program such as gps test to see what your gps is doing (and if your phone is actually affected) , mine could only see 1 or 2 sats without the fix.

The slim 2.2 fix is completely different from the other two you listed.

Thanks for your tests anyway!
[Captivate Android Development] lmaoxlong:
I'm having problems getting any data connection after flashing this ROM. Does anyone have this problem? I have AT&T, from California. Thanks
[Captivate Android Development] prbassplayer:
Are you sure you have a baseband, your APN is correct and you have a correct IMEI?
[Captivate Android Development] lmaoxlong:
I checked my IMEI, but I don't know if it's correct or not. I don't know how to check if I have a baseband (or what it is). I checked my APN, and it's correct, as far as what the majority of what the internet has to say to have for AT&T. Any suggestions? Thanks for your help
[Captivate Android Development] Veight:
You can check your IMEI underneath your battery on your phone. The rom should have said something when you first loaded it that your IMEI is wrong.
[Captivate Android Development] lmaoxlong:
I just checked, and indeed it is wrong. How would I go about changing it? I really appreciate your help
[Captivate Android Development] grndnl:
is it normal that after flashing 2.2, the device says that the installed rom is 2.1?

Loving it so far..
[Captivate Android Development] Wakamatsu:
He is using GPS Test.