yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] sboltman:
Okay, I can do that. Can you give me some direction. I tried doing an ODIN back to 2.3 GB, and ran into more questions than answers.

What I really need is a concise set of steps (as possible) with links to the correct pieces to download. There is a million discussions on ODIN, ODIN oneclicks, etc etc. Can you point me to the place that you would use to perform this? Mucho appreciation!!

Same goes for CM10.

Can you assist?

You know, and earlier question I had was whether -first- going to CM9 or CM10 was required, but no definiitive answer was supplied. That is why I have kep my course here...

Btw, I just tried a CM JK4 modem install, and same thing, nothing in /Radio folder...

thanks!
[Captivate Android Development] prbassplayer:
This 1 click should get you to 2.3.5, it has pit file and a cwm kernel included. One with i897 GB bootloaders another without (use as you need). Once that is booted up get Cm 10 running, Id assume you need to flash the zip 2 or 3 times once its booted up reboot in to recovery and flash slim device and gapps.
[Captivate Android Development] sboltman:
Cool, thanks for the link. How do I know what bootloaders I have? I just googled this, but the answer was not forthcoming. I don't know if I have GB bootloaders on this phone or not. How do I determine this?

UPDATE: using the ODIN without GB bootloaders... Odin is running now... It ran successfully.

Rebooting now...

UPDATE: Phone makes calls now. So back to good. Should I download Nitrality to use to backup my /efs? Hmmm actually I wonder if my phone is still rooted at this point? What are my next steps before going to CM10? Do you have a "best" link to CM10?
[Captivate Android Development] bcflyfisher:
I've always kept efs backups on my PC and external mem card but no matter what I've done I haven't had to use them. I'm not sure how people sometimes lose the efs folder.

When I went to Slim ICS I just downloaded the latest CM9 nightly build, although they also have "monthlies" now too. Haha...wonder if they really thought that one through.

Could just pick from their site... http://get.cm/?device=&type=nightly

You're only going to use it for a few minutes so it doesn't really matter which version choose as long as it's the right one for your phone. I was on CM for about 3 minutes before I flashed Slim.

The bootloader thing is interesting. I skipped GB completely on my way to ICS and I was still on pre-GB bootloaders. I ended up going back and switching because I didn't know if it would be a problem one day in the future with some new Android version. I can say for sure that ICS works just fine on pre-GB bootloaders but I can't comment on JB. If you ever installed an official GB release you should have GB bootloaders.
[Captivate Android Development] sboltman:
So i successfully ODIN back to 2.3, phone works, except I cannot get to Market...

A server error has occurred. Retry, or cancel and return to previous screen.

I wanted to go grab Titanium Backup, and restore my Root Explorer, and copy off my /efs... before I install the CM10 I just downloaded.

Any ideas on Market not working after Odin?

---------- Post added at 08:39 PM ---------- Previous post was at 08:07 PM ----------

DISREGARD the Market Errors.... I was on a public wireless that requires you to accept before getting to the net, and that was the problem.

So my phone is no longer rooted. What is the best approach to root the phone? Its been a couple years since I root this, and forget how. I imagine there is now a handful of ways. What is the best?

---------- Post added at 09:04 PM ---------- Previous post was at 08:39 PM ----------

Phones rooted now...

Restoring TitBackPro, Root Explorer, and ROM Manager... Once I copy off my /efs, I will them install CM10.

Can someone link me, or note here, the proper pre-steps (wipe user data, format system, clear dlavik, etc) I need to do prior to installing the CM10 zip? I just want to make sure I don't screw up...

---------- Post added at 09:13 PM ---------- Previous post was at 09:04 PM ----------

My ROM Manager is version: 5.0.0.8

Should I "Flash ClockworkMod Recovery" (version 2.5.1.2) before I proceed towards going to CM10?
[Captivate Android Development] sboltman:
Goi Slim installed!

Special thanks to prbassplayer, plus the others who helped me.

They key I believe was installing CM10 from GB first.

The ODIN oneclick prbassplayer shared was key.

From there, I got into Recovery, clearced user data and cache and dalvik, then installed CM10.

Repeated same steps but with Slim 3.0. Added gapps. Done.

thanks!
[Captivate Android Development] Kyuta Syuko:
I was able to flash Slim from Stock just fine myself. Had to flash stock because my IMEI became a generic one (some ROM I flashed overwrote my efs folder which is typically how IMEIs get messed up) and I wanted to fix it. I've been doing the whole clear caches, flash ROM, reboot to recovery 2-3 times (depending on if I'm going from an old Slim to a newer Slim or from somewhere else to Slim) and my phone works as well as I expect.
[Captivate Android Development] soumian:
Hi, i just installed this ROM coming from a not so good experience with helly bean and looking for a change of speeds. I seem to have hit the nail as this rom looks awesome. The only thing i'm wondering about and wanted to ask you guys too was the LCD density thingy, i never changed that and by default on this ROM i have 182. At first it looked weird but i think i could get used to it, the question is basically if i change that to the default one (think it was 240) would i get any change (for good or bad) in speed of the phone? Do you guys have the 182 one on your devices? Would i encounter any kind of problems with this when using apps or playing videos?

Don't get me wrong i just want to hear your opinions about this feature on this particular rom.

Thanks to the developers for this great piece of work, when i get some money on PayPal i will gladly donate!
[Captivate Android Development] thunor:
Not really. It just adjust the pixel density. I'm running on 240 and my wife's Cappy's on 180. Actually hers is a bit slower. That's just because she insists on using ADW launcher though, which I used to love, but just had to discard 'cause it makes the phone too damn laggy. Trying to get her to switch to Zeam :P
[Captivate Android Development] prbassplayer:
Screen density shouldn't matter. Though since it smaller you can fit more crap on your screen so more widgets could = more power usage or add lag but thats user's fault :p
[Captivate Android Development] Shoey Peachew:
Not sure what's up, but I'm having issues with all my texts randomly disappearing. It happens after a few weeks. It happened with previous versions of this rom. I also have delete old messages unchecked. I installed this rom from scratch using a Cyanogen nightly build then flashed Slim Bean over it. One more thing, this ROM rocks!
[Captivate Android Development] soumian:
Well, since my sight isn't really great and the text on the lower density was too small i changed it and went back to 240. The performance is the same, i noticed a little lag sometimes but my guess is that Avast is causing it since i installed it after changing the density and i haven't even tweaked the kernel option so far so i'll be good. Seriously this rom is the ****, i thought Team-Nyx ICS was good but when it comes to JB i think this one is as stable as you can get and the speed is just flawless. And to think that i was even considering retiring my Cappy in favor of a newer and more powerful phone...shame on me
[Captivate Android Development] grndnl:
Does the 360 sphere actually work? Or is it like maps that the compass does not work anymore.
[Captivate Android Development] bradddo:
Don't think it does on the cappy. Apparently we're missing a sensor.
[Captivate Android Development] Tsaukpaetra:
Compass works fine for me, I'm on Devil 1.7.5 for my kernel and I had to calibrate it (waving my phone around like an idiot for a bit), but at least that's working. GPS is still terrible, but that's normal. ;)
[Captivate Android Development] prbassplayer:
Compas works on Semaphore. 4.2 camera uses another sensor that SGS devices does not have. At leat AFAIK
[Captivate Android Development] ccheung:
HELP!! invalid IMEI

I wipe and format the Slim ICS, then flash Slim bean. The Slim bean is up, but it gives me invalid IMEI error everytime I boot up. How can I fix that?
[Captivate Android Development] pkadavid:
If you don't have a backup of the EFS folder from before the flash, then you need to go back to stock. Then save the EFS folder separately on your external SD card (or computer), flash Slim and replace contents of EFS folder if the IMEI issue persists.
[Captivate Android Development] xtremists:
Can Someone tell me How to Backup Efs FOlder
[Captivate Android Development] AtoZ0to9:
Use a root file manager... efs folder is in the root of the directory tree... copy it to your SD, then computer...
[Captivate Android Development] sboltman:
Couple questions about this ROM

Just got Slim installed yesterday. Came from GB.

1) Noticed I don't have voice capability on the JB keyboard. Is there a way to add that in? Are their better keyboard choices, one which would have the voice option?

2) How do you switch to a different keyboard? I don't recall how to do this on GB, but I believe it was holding a button down in the typing area, or somewhere, and the popup menu gave you an option to change the keyboard (to Swype, for example).

3) If I find I am getting bad reception, can I install another radio/modem without issues? For example: radio-cm7-ics-captivate-ugjk4-signed.zip?

thanks!
[Captivate Android Development] karlgo:
Just switched to this ROM. How are you able to specify 180 on your Cappy? I only see options for "213 - Nexus 7, 240, and 320". I'd love to set it to 180 / 182.

Thanks!
[Captivate Android Development] m1batt1:
1. If you get the extras from the slim site and install them you should get the voice option.

2. Holding down the comma button should give you the menu that you're looking for but you'll have to install swype.

3. Yes the zip you quoted will flash without problem. However, some modems will effect your GPS performance so you may have to try a couple different ones.

Default on slim is 182 DPI so unless you've changed it that's what you're set at. However you can manually edit the build prop to whatever you would like. Most file explorers allow you to open it as a text file and then just edit it to your liking, save, and reboot.
[Captivate Android Development] karlgo:
Wonderful, that is what I thought, but wanted to make sure I wasn't overlooking something.

Thanks m1batt1
[Captivate Android Development] soumian:
1) and 2) There is a voice imput option (Google Voice typing) you just have to enable it on the Language & input section on System Settings. After that you can even select the voice typing or other keyboards with the settings key hidden under the comma or when you are typing by lowering the status bar where you can find an option to do just that. You can also select to show or hide the voice command on the stock AOSP keyboard.

You have a guide to follow to change this setting, just try to read all the steps because the last one is adjusting it to whatever density you like and not those 3 defaults you said before. This option/guide is under System settings>Interface>General UI>LCD Density so there's no need to mess with the build.prop file ;)
[Captivate Android Development] xtremists:
I Hope This rom soon gets updated to 4.2 :D Waiting Anxiously

And our Old cappy is still competing
[Captivate Android Development] prbassplayer:
It's being worked on, some devices already have alpha test on 4.2. However we will be releasing a final 4.1.2 build soon before we go full speed on 4.2.
[Captivate Android Development] lordxentris:
Nice to hear that. :D
[Captivate Android Development] kevria:
Does anybody know if its possible to have only one accounts worth of contacts shown by default when a phone has multiple accounts setup on it?
[Captivate Android Development] AtoZ0to9:
Go in the phonebook, Menu => Contacts to display => Customize => Choose the account to hide contacts, uncheck My Contacts...
[Captivate Android Development] kevria:
Ive tried that but next time I go in it shows all of the contacts again.
[Captivate Android Development] AtoZ0to9:
Then uncheck Contacts in the sync settings for that account...
[Captivate Android Development] kevria:
And they are still there.
[Captivate Android Development] AtoZ0to9:
Just unchecking the sync isn't going to remove them... try manually removing them... You should have been able to hide them through the phonebook settings... Did you reboot after unchecking that accounts contacts in what to display?
[Captivate Android Development] kevria:
I had not rebooted after unchecking it. I exited the phonebook then went back in.
[Captivate Android Development] AtoZ0to9:
It's acting a little janky for me as well, but I got them to hide... I unchecked the box, and rebooted... they were still there... the box was checked... unchecked it again, and they disappeared... checked the box to show them again, rebooted, and had to check the box again to make them show...
[Captivate Android Development] kevria:
still showing them even after unchecking it. Iguess I would have to go in and remove all 500+ contacts.
[Captivate Android Development] AtoZ0to9:
It worked for me, just was kinda janky... i unchecked it, they were still there, rebooted, still there, box was checked, and uncheck it again, they disappeared...

if you really want to delete the contacts, go to http://www.google.com/contacts to delete that many
[Captivate Android Development] kevria:
Unfortunately I need them for gmail, just not for dialing.
[Captivate Android Development] AtoZ0to9:
then remove the phone number from them all at google.com/contacts and resync
[Captivate Android Development] mrsubway:
APN Help

Can someone give me the default APN data for ATT from this ROM? I was tweaking some settings, and now I cannot get data no matter what I do. I have searched XDA and found the right APN settings for ATT, but I still cannot connect no matter what!

EDIT: Apparently it was the password. You don't need the CINGULAR1 password. That's what was messing it up. Weird. I remember you used to need that. Mods please delete if you wish with my apologies.
[Captivate Android Development] kevria:
None of them have phone numbers
[Captivate Android Development] prbassplayer:
3.1 is out. Read the changelog carefully. This is the final official release for 4.1.2.

Cheers
[Captivate Android Development] diakonos:
Today I noticed my battery draining faster than normal (down to 55% in 6 hours with little to no use -- really only a single phone call). I first checked the Settings > Battery screen and see that "Android OS" is at 62% with "CPU Total" of 10m 25s and "Keep Awake" of 5h 32m. Voice calls is next @ 20% usage (Time on is 27m). Screen was third with just 7%.

I then checked BetterBatteryStats and see under Kernel Wakelock something called "suspend_backoff" at 3h 40m and "svnet" at 50m. I have NO deep sleep and CPU states are split between 800 MHz (46%) and 200 MHz (49%). Does this sound like a known issue in JB or is it more likely related to one of my apps (that I need to investigate more)? Seems that when I've noticed this "runaway" battery use a reboot clears up the issue, but I was hoping to figure out why it happened in the first place (if app-related). Otherwise, I'll just write it off to a small, very intermittent nuisance because otherwise SlimBean 3.0 has been rock solid.
[Captivate Android Development] prbassplayer:
suspend backoff is usually what bb says when it has many smaller (partial) wakelocks in a small amount of time.
[Captivate Android Development] bcflyfisher:
suspend_backoff showed up for me a few days ago for the first time and it was almost non-stop. As far as my internet searching goes, it's something to do with Google Chrome.

I eliminated it by going into Chrome>Settings>Developer Tools>Disable Tilt Scrolling (uncheck)

FWIW, In my case, PowerManagerService is the one that reflects all my Partial Wake Locks.
[Captivate Android Development] Soccer_Dad:
I noticed a pretty significant battery boost when I turned off BLN. I bike a lot, and I know there were times I would ride for a while with the LED's on (couldn't hear/feel the phone in traffic). But I didn't think it would make as much of a difference as it has. I'm talking about the difference between having 50% battery left at the end of the day vs. 25%.
[Captivate Android Development] Tsaukpaetra:
I had this as well, and it was after a call, the lockscreen went all glitchy because the screen was trying to turn on (I took the phone away from my ear) and it was trying to turn of (lockscreen timeout). A reboot did fix it, but since I don't do so many calls it hasn't happened since. :angel:
[Captivate Android Development] notthere:
Is there anybody here who got USB OTG to work on this ROM?

I tried it with a USB stick as well as an 3.5" external HDD but... nothing.
[Captivate Android Development] pqee:
I wasn't able to on 3.0 but blamed it on the $1 cable I was using.

Sent from my Jellied SGH-i896.
[Captivate Android Development] Kyuta Syuko:
Yay new version! Sad it's not 4.2 yet, but love this ROM regardless. Can't wait to see what 4.2 brings.

Think I'm going to go with a clean install since my phone keeps lagging and rebooting...
[Captivate Android Development] lordxentris:
Don't worry, it will be here soon.
[Captivate Android Development] ZephCr:
Do you need to full wipe if coming from 3.0?
[Captivate Android Development] pqee:
Did you even read the changelog? http://www.slimroms.net/
[Captivate Android Development] ZephCr:
Yes, change log says you do need to full wipe but the installation page doesn't :confused:
[Captivate Android Development] droyd666:
Does anyone else get errors when downloading most of the apps from google play? I think it might have something to do with the dpi that the rom comes with by default. I made the phone restore the apps from the backed up list on google play and then I started getting error after error when downloading apps and when I try to install them manually it says "your device isn't compatible with this version" when I was just using the app this morning on CM10. I'm using 3.1

Update: Definitely wasn't the dpi because I changed it to 240, rebooted, cleared play store data and the apps still say that they are incompatible.

Update: Rebooted again just for the heck of it without changing any settings and now the problem seems to have fixed itself. Not sure what happened but all the apps are compatible once again.
[Captivate Android Development] prbassplayer:
Can't be DPI our market and googleframeworkservices are modded for this. Something else is wrong.
[Captivate Android Development] m1batt1:
I've run into this issue recently on both Slim and Helly. After a fresh flash several of my apps say they are not compatible but after a couple reboots and waiting a while it fixes its self.
[Captivate Android Development] prbassplayer:
I'd recommend wipping app data for playstore, google play services and google framewor service apks
[Captivate Android Development] mrsubway:
I just wiped cache/dalvik and flashed 3.1 and all the 3.1 gapps updates, reflashed my kernel and all is well.

Sent from a heavily modded Cappy from parts unknown. Slimbean/Semaphore. FTW.
[Captivate Android Development] brianray14:
Haven't updated to 3.1 yet but I noticed an ongoing problem with either my phone or slim 3.0. Whenever my battery gets down to under 10%, my data connection is lost. Anyone else notice this issue. If so, has it been rectified in 3.1?

Sent from my SGH-I897 using Xparent ICS Tapatalk 2
[Captivate Android Development] kong00:
3.1 is amazing and is the smoothest release. I dirty flashed from 3.0 and haven't run into any issues. Bugs that were in 3.0 for me were fixed, like the notification drawer in landscape. Thanks guys again.
[Captivate Android Development] sboltman:
Update Me

DISREGARD THIS. I read the ChangeLog. Thanks!!!

New to Slim, installed it last week.

Can someone tell me what the "Update Me" app is? Its telling me a new ROM is present. I see, its notifying me about the 3.1 Slim version.

What is the reccomended procedure for updating?

Download, clear system (x 2), clear Dalvik, install?

thanks
[Captivate Android Development] prbassplayer:
Go read the changelog ;)
[Captivate Android Development] soumian:
I also did a dirty flash, just wiped cache/dalvik and so far so good!
[Captivate Android Development] Kyuta Syuko:
That's a strange issue. I'd like to say I've not encountered it, but I'm usually on WiFi so I don't know...
[Captivate Android Development] Wakamatsu:
Do you have any of those battery saver apps? Some of them have settings that will cut data when the battery reaches a certain level in order to cut down drain.
[Captivate Android Development] droyd666:
I decided to try CM10 for a while and I just had to come back to Slim. The first reason being that the battery life is so much better because I left it overnight in airplane mode and it still hasn't dropped by a single percent while CM dropped by 5-7 percent within a few hours even in airplane mode . The second reason being that it is more customizable and finally because the Semaphore kernel makes the phone much more stable and smooth. I just felt like I needed to post the results of my little study :laugh:
[Captivate Android Development] OKAstro:
Sorry if this has been addresses...been searching and didn't see it.

Voice Dialer FC with "failed to initialize message". I've tried reboot, wipe, format system, clean install, etc. but no luck yet.

On 3.1 version. Any help is appreciated

Thanks
[Captivate Android Development] couldnthinkaone:
I did a complete wipe, flashed twice, and still have no mobile network/phone signal. Any suggestions?
[Captivate Android Development] brianray14:
Good suggestion, but i only have better battery stats running. No apps that cut out services

I had this issue when flashing 3.0. When you say full wipe, did that also format system also?

Edit: updated to 3.1 and the problem is still present. Bummer..down to 13% battery and no mobile connection again. This occurred after a reboot. Was at 35% beforehand. Any ideas on why batt would drop so much after reboot or no data connection when batt is this low?

Sent from my SGH-I897 using Xparent ICS Tapatalk 2
[Captivate Android Development] couldnthinkaone:
I just did a "reset". Can I do it from recovery?
[Captivate Android Development] brianray14:
In recovery under mounts and storage. I'm still having connection problems too so this solution may not fix your prob

Sent from my SGH-I897 using Xparent ICS Tapatalk 2
[Captivate Android Development] dwmoss:
I can't seem to find how to turn off a "ringing" type messaging notification sound.

If i get a text message, it keeps "ringing" until reboot. Can't seem to find the setting. Someone mind helping a noob?
[Captivate Android Development] A Ham Sandwich:
3.1 has been a significant and awesome update, loving all the new options!

Great way to wrap up 4.1.2 development by putting out such a solid release.

Looking forward to the 4.2 iteration.

THANK YOU Slim Bean devs, I'm sure you won't be getting coal this Christmas.
[Captivate Android Development] bradddo:
Not that 3.0 was bad at all, but 3.1 is great so far. Seems more stable and though its still early, battery life is up a bit. Thx for a great ROM.
[Captivate Android Development] sboltman:
Go find my posts. I experienced the same issue. I resolved it by ODIN back to GB. Just read my posts for what I did to get it working.

---------- Post added at 12:57 AM ---------- Previous post was at 12:56 AM ----------

It appears to all be set correctly, and alarm (actually all) volumes are set high... yet no sound when the Alarm time arrives.

Phone claims alarm is set.

Any ideas? SLim Bean 3.0
[Captivate Android Development] prbassplayer:
Nope i used 3.1 for a few days and worked fine (I depend on alarms a lot). Maybe ringtone gets deselected?

Just text msg?

Sent from my SlimBean 4.2 Alpha powered Captivate