yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Kyuta Syuko:
Since doing a "dirty" flash of 3.0 I've been having drainage issues with my phone. Typically it'd last from ~06:20 until between 19:00 and 22:00 (not sure what's up with the broad range since I used it about as much every day) and now it goes from ~06:20 until about 16:00... One thing I can say for sure is at least it's more consistent now than it was before...
[Captivate Android Development] prbassplayer:
Wake locks? I've been having problems with Maps myself.
[Captivate Android Development] Kyuta Syuko:
For me in BBS under Partial Wakelocks I have some AlarmManager at the top. Sometimes it's the one tied to Android System though currently it's the one tied to HD Widgets =|
[Captivate Android Development] bcflyfisher:
My main partial wake locks were maps (eliminated that problem with Autostarts but haven't frozen it so it still functions) and Alarm Manager.

The main Alarms I had issue with were Calendar (when I had notifications on) and Juice Defender (which I don't use any more).

Turn off all location services too, btw.

I'm getting the best battery life I've ever had with my Captivate right now, but that's partially attributed to the 1800mAh battery.
[Captivate Android Development] thunor:
3.0 working beautifully right now. Fastest JB ROM I've tested so far. I'd tried out 1.0 and had a lot of lag so I had changed over to Helly Bean a while back. No JB ROM until this has felt virtually lag free on my cappy. Runs just about as great as Slim ICS used to for me. And that was pretty great (best ICS ROM ever IMO). Also JB 4.2 swype-like keyboard from this thread is working fine: http://xdaforums.com/showthread.php?t=1964726 You can get all 4.2 gapps, holo launcher, KB, camera/gallery, etc. from there as well. Also, I'm using camera/gallery (with picasa sync working) from this link, and working fine on 3.0.: http://goo.im/gapps/

So basically thanks for this krarvind and team. This is pretty awesome.
[Captivate Android Development] shuyin1102:
Is it possible to customize the haptic feedback level? Its too strong for me. Thank you so much, this is the best rom ive ever try :thumbup:
[Captivate Android Development] prbassplayer:
Semaphore app let's you. Though I can't speak for it myself.

Edit: Happy thanksgiving everyone.
[Captivate Android Development] kevria:
Does anybody know how to change the number dialed to enter Voicemail?

Edit: Found it, its under Call->Settings instead of Settings->Call
[Captivate Android Development] mrsubway:
It is in the Semaphore app under vibration. Accidentally set mine to 0 and thought my phone was broken. :/

Sent from a heavily modded Cappy from parts unknown. Slimbean/Semaphore. FTW.
[Captivate Android Development] ZephCr:
Can I put this right over gingerbread illuminance rom? Just factory reset & such right?
[Captivate Android Development] kevria:
Is there a way to change what app is used for selecting ringtones/notification tones?
[Captivate Android Development] sephhi:
For ringtones, yes. You have to install a third party app from the play store, try different music players.
[Captivate Android Development] kevria:
When I first went to select a notification on my wifes phone today after installing SlimBean I had to choose an app to use to select the notification and stupidly said "Always" and it was the wrong app, thus I want to change it.
[Captivate Android Development] brianray14:
Can you just go to said app that you chose "always" for and clear the data?
[Captivate Android Development] The Sonos:
Go into said app through settings-> application manager, then 'clear defaults' or something to that effect, it will be a check box towards the bottom
[Captivate Android Development] Kyuta Syuko:
Well rebooted my phone to get a more precise BBS reading and my phone's been behaving all day... unplugged it around 08:00. It is now just after 22:00 and it's sitting at 60%
[Captivate Android Development] kevria:
I was looking at it a if I had to clear the data on the app that would launch the selector so I wasnt finding it. Thanks, its all set now.
[Captivate Android Development] FrankI897:
Remember when I asked you about SSH executable that I used in CM9 and that It was already included... Well, Just to tell you that I did it, I extract "ssh" file from /system/xbin folder in CM9 Image, placed it in SlimBean(3.0) same folder, and It works! :D

I just wanted to share it :) In case some lost soul got the same "problem" :)
[Captivate Android Development] RDI:
It is 2:00am, Saturday morning in Tampa, Florida. The temperature on my lock screen says:

21° F something is wrong...

50° | 70 °

12° F

42° | 71° refreshed @6:17am

and Google says it is 54°

How do you take a screen shot of a locked screen?

Sent from my Samsung Captivate running 4.1.2 Slim Bean v3.0 w/KG3 Modem
[Captivate Android Development] Tsaukpaetra:
It's Sunday already? Hmm. Didn't attach a screenshot, did you refresh the weather?
[Captivate Android Development] brianray14:
Dunno how tsaukpaetra (sorry spelling) got Sunday out of your original post which clearly states Saturday, but anyway.. are all of the boxes checked in --> settings --> location?

Sent from my SGH-I897 using Xparent ICS Tapatalk 2
[Captivate Android Development] sboltman:
Please help this noob

Quick background: I flash a rom once a year. So I get techie enough to do it, but I don't follow the boards. I do follow instructions to a T though.

Phone had Phoenix Ultimate on it for a while, and then latest I installed Mosaic 9. I think the means my phone was GB when I tried installing SlimBean.

I followed the instuctions on SlimBean (link first page), downloaded the ROM zip and GApps zips. I think my problem was I did NOT get booted into CM9 or CM10 first, before doing the "From another JB or ICS ROM" steps. I am guessing at this point I leap frogged a whole upgrade step that has led me to where I am at now:

I am in a boot loop.

After installing the Slim zip, it would sit there on the Semaphore banner. It would not progress. I think it was looping so fast that the screen image showing Sempahore logo was constant.

I then tried reflashing my old Mosaic 9 using Odin. I got that flashed, but like Slim, it was struck in its boot loop (watched the Mosaic 9 boot animation go over and over again).

WHERE I AM AT: I can get into Download mode, I can get Odin to recognize the phone, and I can get into the Semaphore recovery.

The SlimBean zip is on my external SD, not the internal.

I am reading through the pages of this forum, trying to self rememdy. So I am making efforts to solve this on my own. But any help would be GREATLY appreciated. Greatly :)

I read somewhere that I simply need to go grab on of the Odin oneclicks and reinstall an earlier bootloader. Knowing that I had Mosaic 9 running fine all year, I assume that I am GB, but when I look at the list of Odin oneclicks, I see different versions of GB (2.3.4, 2.3.3, etc), so I am not sure which to choose.

Pressing on... I hope someone can help.

Thanks!
[Captivate Android Development] bcflyfisher:
HII would use Odin to get back to any GB, probably latest is fine. If possible I would try for one WITHOUT bootloaders. I assume you already have GB bootloaders and should never have to install them again. They're the "risky" part of using Odin.

Then Odin to get a kernel with recovery (I used the Corn kernel to accomplish this).

Then flash CM9 (the critical step you missed), and follow the rest of the steps from the Slim instructions.

Check this thread for links to the Odin files I used: http://xdaforums.com/showthread.php?t=1835161
[Captivate Android Development] m1batt1:
Before you go through the trouble of a one click I suggest you get into recovery. From there flash slim again and the gapps and then try to boot. If you get stuck in a boot loop try getting back into recovery and do a full wipe including formatting /system then flash everything again. It might even require a third flash.

If that doesn't work then you'll have to resort to the one clicks. If that is the case I suggest the KK4 with boot loaders. It will be in the third post of the sticky thread.

Also just so you know what has likely happened to cause the boot loop... when going from GB or ICS to JB there is a difference in the partition layout. During the initial flash it installs the kernel and changes the layout at this time. In order to complete the flash it requires a reboot and the majority of flash packages do not automatically reboot your phone back into recovery which leads to the boot loop.
[Captivate Android Development] sboltman:
Okay, I managed to successfully flash the SlimBean.zip file. Phone booted up into SlimBean, things look fine. I now am trying to get into recovery so that I can then install the slim_gapps.zip... and I cannot seem to get into recovery...

Should I be going into google and/or using titanium backup to do a restore first?

Also, I came across this comment about the phone first MUST have cm9 or 10 installed before going to Slim Bean. Is this accurate? Because it seems like I have SlimBean installed...

Here is that comment I found. Thanks for any clarifications:

Since SlimBean is based off CyanogenMod 9/10 and needs alot of the kernel/firmware flashes, you must flash CM 10 or 9 before flashign Slim Bean.

The easiest way to do this is through ClockworkMod Recovery and the easiest way to get ClockworkMod installed is through ROM Manager.

1. Download ROM Manager through Play Store

2. Open up ROM Manager and select the first option "Flash ClockworkMod Recovery"

3. Download CyanogenMod 10 and the latest Slim Bean which should be version 2.8

4. Reboot into recovery through the option in ROM Manager

5. Clear data, cache, and Dalvik cache.

6. Install ZIP from SD Card > Choose ZIP from SD Card > Pick CyanogenMod 10 FIRST

7. Let it flash all the way through and then reboot your phone when you are back at the recovery menu

8. Boot into CyanogenMod 10 ROM and play around to make sure everything is working and good

9. Go into Play Store and install ROM Manager again

10. This time, just boot into recovery. No need to reflash ClockworkMod since you already have it.

11. Clear data, cache, and Dalvik cache.

12. Install ZIP from SD Card > Choose ZIP from SD Card > Pick SlimBeanT959 rom this time

13. Reboot into SlimBean to make sure everything works. If so, go back into recovery and flash the Slim Gapps and whatever else you may want to use.

Good luck and enjoy SlimBean.
[Captivate Android Development] arse87zx:
If you click reboot in the power menu there will be the option to reboot into recovery.
[Captivate Android Development] Tsaukpaetra:
Yesterday, 12:15 AM (Last edited by RDI; Yesterday at 04:29 AM.)

The post was clearly edited after I made my own reply. You see my quote? I made my reply minutes after he posted, then afterward (apparently 4:14 hours later) he revised his post. Just to let ya know I'm not totally crazy. ;)
[Captivate Android Development] grndnl:
What are the changes that come with the camera / gallery? and so you are not using the camera/galley from the xda thread, but the one from the goo.im thread?
[Captivate Android Development] prbassplayer:
I disagree to use rom manager you need root and even then it doesn't always work on our captivates. Easiest way to get cwm is flashing a kernel through odin ;)
[Captivate Android Development] sboltman:
Newbie has gotten further

MUCH FURTHER, But now stuck on....

I'm the guy in previous two pages, going from Phoenix to Mosaic to, now, Slim Bean

I have Slim Bean installed, plus slim_gapps.zip.

I now have the following symptoms (from another poster with same issue):

I have an unlocked Captivate SGH-i897 running Jelly Bean (Slim Bean). I am trying to use it with a T-Mobile Sim card. I cannot connect to data in any form (wifi is fine), texts come in and go out but take a very long time (about an hour), and calls do not work (with the exception of one time one went through), saying "Mobile Network Not Available."

Back to me: I noticed I do not have an IMEI number listed, and I tried copying over on top of "my backup of original /efs folder" onto what is there on the phone currently, and rebooted. That had no effect. Which is strange.

What are my next best steps to get the IMEI to be known, which I believe in turn will allow calls yo go out, and text messages as well.

Thanks!!!
[Captivate Android Development] prbassplayer:
You forgot to set permissions of the folder. I would re-restore the backup reboot to recovery and fix permissions and then it should restore imei. If that doesn't work you need to ODIN back to stock, yup sorry no other way of restoring IMEI.
[Captivate Android Development] sboltman:
So I went back in via Root Explorer, mounted r/w, went to external SD to copy my original /efs folder, went back to / root, pasted, it detected existence of /efs already, asked to merge, said yes. Rebotted to recovery, ran fix permission successfully, rebooted.

IMEI still does not show in device phone settings.

I look at my backup's /efs/imei/bt.txt: looks to be hexidecimal, but does not convert to my IMEI listed on my phone label (under battery)

At any rate, assuming I did the steps above correctly, you mention I I have to Odin back to stock... Is there a URL to point me to, or clear set of steps, to get me pointed in the right spot. I can certainly google it, but there may be variations that then confuse me.

Let me know. I do have Odin installed, and can interact with the phone (as I have installed Mosaic 9 using Odin, previously).

thanks!!
[Captivate Android Development] RDI:
I believe someone fixed the above problem by loading the correct modem.

Sent from my Samsung Captivate running 4.1.2 Slim Bean v3.0 w/KG3 Modem
[Captivate Android Development] antonyvijai:
CM10 to slimbean

I installed Slimbean3.0 from CM10 through CWM recovery method. In CM10 my wifi did not work. It is still the same with Slimbean. Is there anything I need to do to resolve this issue? Also, my mac is not recognizing the captivate anymore. Any help is appreciated.
[Captivate Android Development] lordxentris:
Try restoring to Stock Rom, check it your WiFi works then, if it doesn't then its a hardware issue. But if it does then flash Slim Bean and try a different radio.
[Captivate Android Development] prbassplayer:
You can attempt flashing another modem as mentioned, never seen that work for me personally. As for ODIN you can use the one without bootloaders found here. KI2 1 click package that repartitions and flashing Boog's kernel with cwm. Else you can look for standard packages with a pit file to do the same. Hope it helps.

Sorry I have to agree with the guy above flash back to stock and verify it works, could be hardware.
[Captivate Android Development] sboltman:
What is the correct modem? I know zreo about naming etc. I did see someone say they reloaded JK4 modem.

Can you give me a direct URL to the correct one? or tell me how I mwould determine this?

Also, how do you install a modem? is it a zip installed via CWM Recovery, or is it an Odin thing? (in which case, do you open the modem file under PDA, PIT, ? ? What is PIT...)

thanks
[Captivate Android Development] RDI:
modem link

http://soggycashew.weebly.com/cm7miui--ics-modems.html

zip installed via CWM Recovery

I have had good luck with KG3 modem

Here is a link to download the modem I have been using. http://db.tt/dyaoZDfS
[Captivate Android Development] bcflyfisher:
Another vote for KG3. I've had much better balance of reception / battery than with the other modems I've tried.
[Captivate Android Development] thunor:
Yes, i'm using the one from goo.im. The 4.2 camera has a really cool menu that appears anywhere in the screen by pressing your thumb. Also the 360° sphere shot in place of the old panorama mode. Not sure if there were any other new features in the 4.2camera/gallery. I prefer the one from goo for now because the picasa sync is more important to me right now. Hopefully they'll come out with a 4.2 version with picasa sync soon :->

---------- Post added at 08:18 PM ---------- Previous post was at 07:55 PM ----------

So far I've never had a problem using the KK4 Heimdall one-click with optional bootloaders whenever I have any kind of rom flashing problems. You can get it from here (as well as many other stock n Odin and Heimdall one-clicks):

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

I usually then Odin flash an old darky kernel from an old Apex zip package to get clockwork recovery. Of course afterward install CM9 or CM10 depending on which platform you're going to (ie. CM9 for ICS or CM10 for JB). Never had an issue with this combination of either my Cappy out the wife's. Good luck.
[Captivate Android Development] sboltman:
Am I fooling myself?

I'm the guy who is going from Mosaic 9 (GB) to Slim Bean... without having installed CM9 or CM10.

I think I am a modem-install away from having this work... the ROM is installed, but I have no BandVersion (unknown) or IMEI (unknown).

So several mentioned that a mission radio/modem could be the issue.

Could that be my last hurdle?

Or am I fooling myself, and I really need to go through a CM9 or CM10 installed PRIOR to a SlimBean install?

thanks
[Captivate Android Development] prbassplayer:
You need a modem flash that. If you still have a bad IMEI then you need to restore your backup of your EFS folder. If you don't have one Odin back to stock and back it up and start again.
[Captivate Android Development] thunor:
So I've just installed Gmail, Music & Camera/Gallery from 4.2 GAPPS thread I linked to in a previous post and all are working perfectly so far on Slim 3.0. And btw gallery does have Picasa sync. So double win!!!
[Captivate Android Development] sboltman:
SO I pulled down the modem discussed a couple posts above... and installed it via CWM Recovery.

After reboot I still had no BandVersion, Mobile Network, IMEI, etc...

So I went into Root Explorer, went to external SD, highlighted my /efs (the original I pulled from the phone before my first ever flash to Phoenix),

chose Copy, navigated back to internal SD root directory, hit Paste button, warning says "efs folder exists, do you want to merge?", I choose Yes. It does its merge.

I then reboot into Recovery, and do a Fix Permissions (cuz someone told me I needed to do that)... then reboot system...

Then shut back down, insert SIM, and start back up. (Note: my external sd card was installed during modem install)

Btw, I am using Semaphore CWM Recovery 6.0.1.5, if that matters at all.

Didn't work... Still no bars... Network: Unknown, Mobile Network Type: unknown:0, Service state: out of service, Mobile network state: disconnected, My phone number: unknown, IMEI: unknown, IMEI SV: unknown

Did I not do the proper modem install? Should I try the I9000UGJK4 modem that I used to have? Could that be the solution?

Need your help! thanks!!!
[Captivate Android Development] prbassplayer:
Did you use a cm modem zip?
[Captivate Android Development] thunor:
These modems should work:

http://soggycashew.weebly.com/cm7miui--ics-modems.html

KG3 & KP1 have worked best for me. Though I still think the best and cleanest solution is to go stock GB and go on from there.
[Captivate Android Development] sboltman:
I downloaded the one mentioned in post #1284 right above here. I do not know a "CM Modem" from a hole in the wall. I am learning fast though.

Is this one not a CM modem? Can you point me to one (or a list of) which are?

thanks!

I know these newbie questions are painful, and you want me to read... trust me, I am reading, a ton, but I am catching up a a year of ROM technology... thanks!!!
[Captivate Android Development] prbassplayer:
Link above is where I dl my modems ;)
[Captivate Android Development] sboltman:
The KG3 one was the one I downloaded and tried... my results are in the last post above... so I think I am doing something fundamentally wrong.

I installed the KG3 zip using CWN, rebooted, used Root Explorer to copy over my orignal /efs, rebooted into recovery, ran fix permissions, rebooted... still nothing.

Like I said, I am doing something fundamentally wrong I believe... waiting for someone to tell em "well, did you run this after?" or "did you do this?"... or perhaps "dude, you are supposed to go to CM9 or CM10 before SlimBean!!", or something...

Anyone got an idea?

ROM is loaded, I just don't have any connectivity except wireless to the Net.
[Captivate Android Development] thunor:
The ones in the link on my last post are all CM (ie. Cyanogen Mod compatible) modems. They need to be if your using a Cyanogen Mod based rom, which this is.
[Captivate Android Development] sboltman:
So that KG3 I installed was a CM modem. Any thoughts on my steps, what I might be missing?
[Captivate Android Development] 305Freak:
After you copied the efs folder with root explorer did you change the permissions of the folder and the files inside it with root explorer? That could be it. You could be skipping this step or setting them wrong.
[Captivate Android Development] NIMBAH:
Yeah this is most probably where your going wrong. If your not bothered to set the permissions for each individual file then just set permissions for the whole efs folder. That's what I do.
[Captivate Android Development] sboltman:
Still stuck... More info...

So I set permissions on /efs to be -rwxrwxr-x

When I went in there, owner did not have any, so I added rwx for owner. That results in the -rwxrwxr-x

Rebooted. Still no luck.

After I install a modem, I don't have to go into Settings somewhere and choose something do i?

I installed without the SIM in. Is that correct?

How do I validate my "good" /efs/ is in fact good? can I look in the /efs/imei/ folder and validate the contents of bt.txt somewhow? it looks to be a hexidecimal. Is it supposed to convert to decimal and match the IMEI that is on the label of my phone?

It feels like the modem is missing, perhaps not install properly, or configured after the fact... Can anyone tell me how to validate the modem did in fact install properly?

UPDATE: I went into Root Explorer, and in the /Radio folder there is nothing but a Lost+Found file. This doesn't seem right. Again, I installed the CM KG3 modem linked to me in a post above, copied that zip to my internal, went into recovery, installed the zip, install output looked good, rebooted. Copied over backup /efs, fixed permissions, reboot, put SIM card in, reboot... I'll try reinstalling the modem once more while I wait for a response here.

I believe BAseBand Version is what lists the modem ID. On my wife's Captivate, that still has Mosaic IX installed and running (same ROM I had on mine), the BaseBanced version shows: I9000UGJK4

Thoughts? Help?
[Captivate Android Development] prbassplayer:
At this point your easiest fix would be ODIN back to 2.3.x make sure your baseband and IMEI is correct and back that up start over. Just my 2 cents
[Captivate Android Development] sboltman:
I would that, but here is the deal:

When I Mosaic IX on here, phone worked fine. This means the /efs folder was fine.

When I first attempted installing Slim, it made a copy of that /efs over into a /backup folder. So I am confident I have a good copy of my working /efs.

I just now went a reinstalled the modem/radio (radio-cm7-ics-captivate-ugkg3-signed.zip), then rebooted, then immediately went into Root Explorer... and the /Radio folder is still empty.

It should have files right?

Is that radio file I called out here the right one? Its one I was pointed to.

Again, and a second phone (wifes) that is still running Mosaic iX, her BandVersion lists as "i9000UGJK4"

So should there be files in /Radio?

Is this the write modem?
[Captivate Android Development] prbassplayer:
Should have a lost&found folder and a modem.bin file. Like I said ODIN back with repartition and do the CM10 first :)