yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] delugeofspam:
I'm beginning to think that my efs backup is missing a file.

Back to stock GB for a moment, I guess.
[Captivate Android Development] delugeofspam:
I have been hacking away at this on and off for hours, and I can't seem to get it to work.

I flashed back to stock Eclair, made a back-up of a known-good /efs, then brought it to Slim ICS and it still won't take. I've used several different tools (.apks and .exes) and methods (tar, zip, cat > .img) and I still can't get it right.
[Captivate Android Development] AtoZ0to9:
I've always just used root explorer to overwrite the current nv_data.bin with the backup and rebooted...
[Captivate Android Development] delugeofspam:
When I flash this ROM, efs comes back completely empty. From there, it doesn't matter how I restore it-- unzip efs, paste one file, cat an img back to efs --the files are all there, the phone just doesn't want to play.
[Captivate Android Development] lordxentris:
Hi, is anyone experiencing slow transfer rates with JB 1.0? I am getting crawling speed with this. And my external MMC doesn't show up. Changed I/O Schedulers but doesn't fix the issue. Any ideas?
[Captivate Android Development] dank8885:
I'm assuming you're talking about Slim Bean v1.0? If so post there, this thread is for Slim ICS.

Edit: Also, I don't recall having slow transfer speeds but I haven't tried moving anything large.
[Captivate Android Development] lordxentris:
Noted. Thanks.
[Captivate Android Development] arse87zx:
Did you flash cm9 before you flashed slim? If not try that to get the partitions set up properly.
[Captivate Android Development] delugeofspam:
Thanks for the tip, but I got this figured out earlier.

I'm not sure which of these was the solution, but I did two things at the same time:

1) Flashed a CM modem.

2) Restored a /efs backup that I had made 12/2010, from the original stock OS of the phone. I can't even believe I found that thing.

But really, I'm almost entirely certain that the problem was the lack of a CM/ICS modem. #2 *may* have been the solution (as my other /efs backups didn't have a .nv_data file) but I seriously doubt it.

Either way, this ROM is great. Loving it.
[Captivate Android Development] arse87zx:
That would make sense. I forgot that this rom doesn't include a modem. Glad you figured it out, this is a great rom.
[Captivate Android Development] beall49:
This is gonna sound weird but I just flashed this and everything went through fine...however after flashing common I boot up the device and all I have is a blue line on the bottom that looks like a screen indicator. I have no homescreen...yet the bottom buttons light up on touch? I can't get it back into recovery either....it goes straight to boot every time...

Any ideas?
[Captivate Android Development] mms6:
Does this work on my old Rogers Captivate i896 ?
[Captivate Android Development] pqee:
It sure does. I'm running it on mine right now.

Sent from my Jellied i896 Captivate.

-----------

My bad, thought this was Slim Bean thread. I ran SlimICS on my Rogers i896 for months (running Slim Bean now) and loved it. Just use the files for the i897 and you should be fine.
[Captivate Android Development] delugeofspam:
If you can adb, 'reboot recovery'

If you can't, sounds like a job for Odin.

mobile sig: I897/Cognition 4.1.1/speedmod k13c/UGJK4 SlimICS/CMJVT using xda app.
[Captivate Android Development] aluvn:
So today I decided to reinstall the ROM (due to some problems with the fonts, it's my bad). I used TiBu to create a backup, but I forgot to check the symlink option in Troubleshoot Settings. Now I've reinstalled the ROM, and when I restored, everything force closed, and it stuck on the ROM bootscreen if I reboot, even if I checked the symlink option and flash datafix script. Any thought?
[Captivate Android Development] beall49:
Yeah I had to Odin, thanks for the reply.
[Captivate Android Development] aluvn:
Nevermind, I restore apps only and it works. I have to reconfigure apps from scratch though.

But turns out, the font problem seems to be ROM related. I still can't see any non-latin characters on my device with this ROM. These last 3 songs have Japanese names. Chinese characters don't seem to show up as well.

And yes, I did a full wipe before flashing. My DPI setting is 182 btw.
[Captivate Android Development] delugeofspam:
I'm having a hell of a time replacing the fonts, here.

I *had* done it before, but I flashed back to stock to restore some other things, then full-wiped back to SlimICS. Now, when I replace DroidSansFallback nothing changes. If I replace DroidSans or DroidSans-Bold I get a boot loop, same with replacing Roboto-Regular and Roboto-Bold.

I don't understand why it worked before but not now. This ROM looked great with Storopia.

Additionally:

Root Explorer is giving me stupid errors about how much space is in /fonts, even after I've deleted exactly the same amount/size files that I'm trying to add.

Why are the fonts causing boot loops? Why are they done with symlinks? This seems like a pretty fragile set-up.

---------- Post added at 01:17 PM ---------- Previous post was at 01:02 PM ----------

And now it is behaving itself.

I should just stop posting. Don't ever listen to anything I say.
[Captivate Android Development] n311.dunkle:
I'm using 2.3.6 currently so I guess I'm using GB bootloader. Do I need different bootloader for this ROM out just devil kernel then flash ROM?
[Captivate Android Development] dank8885:
http://www.slimroms.com/installationics.htm

Going by that I'd say any ICS kernel should do the trick.
[Captivate Android Development] bcflyfisher:
Been on SlimICS for a few days now and love it!

Just switched over from Darky 9.5 (Froyo, but I never had a problem so never bothered with GB).

I did all the usual backing up, flashed a CM9 nightly, followed all the steps here and it worked flawlessly. Clear instructions are nice.

The only think I'm curious about is bootloaders. I went from custom Froyo to CM9 then SlimICS. I did everything through CWM and only ever used Odin when I was going from stock 2.1 to Darky 9.5 (Froyo). Is there an easy way for a non-developer (hint, hint) to determine what bootloader they have? Do I just assume since I followed those steps that everything is fine and I should stop thinking about it?

Should add....the only problem I have is that Voice Search FCs all the time. I've wiped the cache, cleared VS data, still no go.

Cheers, thanks for the great ROM!
[Captivate Android Development] prbassplayer:
You can assume that if it booted up you're running GB bl. Did you flash the zip for voice feature?
[Captivate Android Development] krarvind:
he is on froyo bl. He didn't Odin to 2.3 based on his post.
[Captivate Android Development] prbassplayer:
Wouldn't 2.2 bl give the rom issues? Like not boot up or looping?
[Captivate Android Development] krarvind:
nope. Froyo bl works fine, gb bl was better for battery on cm7. No idea what it is for ics/jb
[Captivate Android Development] prbassplayer:
Well I stand corrected then. Thanks :p
[Captivate Android Development] The.Se7enth:
Well. As much as I like the ICS features, I've had a lot of issues with this rom in only a few days. Apollo app doesn't show half of my music, so I tried installing Songbird; unfortunately, it locks up and crashes constantly. Still having issues with the keyboard -- while I got Swype to work, it still asks me to pick a keyboard every single time I try to type. And every now and then, varying lengths of having the phone on, it slows down to such a sluggish point that even the TV zoom animation for locking actually lags, and when I try to unlock, it just barely shows a dim screen and won't respond, so I have to take out the battery and put it back in to even start it up again.

I don't really know what I'm dealing with here, but, from my experiences, it's been a very frustrating rom. Had some fantastic features, but the features aren't worth it if I'm dealing with so many problems on the side. Ah well, it was worth the try. And, don't take this as a complaint, it's not meant to be.
[Captivate Android Development] bcflyfisher:
- Just going off the instructions on the Slim website got me where I am (I repeat - excellent instructions). I must still be on Froyo BL. Is this eventually going to cause me any issues if I go to try a different kernel or JB down the road?

- because I went straight to SlimICS 4.2 I just flashed the device and common zips. Didn't realize that there was a zip for voice feature. I was further confused because in Swype the voice dictate works fine. I'll have to look into that more....

EDIT

- OTA app, addons, SpeechRec_VoiceDial

- I've never been super impressed with my battery life but in my case it's usually because of screen on time and searching for weak-to-non-existent signals. Never thought BL could be related.

THANKS!
[Captivate Android Development] Tsaukpaetra:
A boot loader is a BOOT loader. Its' primary purpose is to load the kernel and control the initializing processes before the kernel takes over.

On my Captivate, it's the part where the screen is blindingly white with the AT&T logo. Once you see the kernel's logo, the bootloader will have nothing whatsoever to do with battery or anything else, because the kernel will be doing the instructing and whatnot to actually get the phone working.

IMHO the whole bootloader thing is all hogwash. Bootloaders never had any affect on my battery life, because the code that made it up ran for at most ten seconds on initial startup. The most things that affect battery life, are the actual devices turned on/off (wifi bluetooth etc) whether the screen is on/off, and whether you have an app not totally compatible with the rom that keeps it awake. I personally had an issue with a data-monitoring app, that broke apparently between gingerbread and ICS, because of the way wakelocks were handled for a service thread (basically, because the app had requested updates from the kernel for every bit of data that would be transferred, ICS thought that in order to service that request, it would need to stay awake in order to keep the pipe open, resulting in "phantom" battery drain, with Android OS taking up 86% in Battery Usage).

Your best bet is to start with a clean install (after full wipe etc) and see what the battery life is. Then, you can add apps like Gmail etc until you know which app is actually playing dirty.
[Captivate Android Development] scottcwhite:
Still here waiting to make the cross to slimbeam. Waiting a bit as my phone is perfect at the moment.
[Captivate Android Development] elsaghir:
voice feature

Did the voice future zip fix the problem. I am using a different ICS ROM and we have the same issue "I think" using any voice search program?

Edit:

I did try it and did not change anything for my Rom. I still get FC and all apps trying to access voice engine fail
[Captivate Android Development] mrsubway:
It seems like I cannot flash modems. I'm using Semaphore and all the cm3 modems give me an error.
[Captivate Android Development] prbassplayer:
Cm3? Any Cyanogenmod modem zip for i9000 should work. Else it might be kernel related.
[Captivate Android Development] mrsubway:
Meh. Just overwrote the modem.bin using root explorer. The reason I'm playing with modems is because I'm not connecting to Google. Imei seems okay but no blue.
[Captivate Android Development] topiratiko:
Wouldn't happen to be data counter app would it

Sent from my Samsung Galaxy SII

CM9 8-3-2012/Skyfire
[Captivate Android Development] Tsaukpaetra:
In my situation, it was indeed a data counter. (3g watchdog or something). Once I culled that the phone was fine. ;) The built-in data usage counter made that app (mostly) obsolete anyways, it wasn't too painful. :P
[Captivate Android Development] kalda01:
I'm using latest ROM and Semaphore kernel. Battery is draining very fast even when phone is idle and screen off.

Battery usage implies WHATSAPP is killing the battery.

There are over 2000 contacts in my address book. Is that a problem ?

How can I fix this issue ?
[Captivate Android Development] tonyzz:
Thank you this is a great rom I only changed the kernel to semaphore Ics as i like to tweak some things overclock a little. It has been running great for me, people I call say I sound clearer now, bonus once in a while I get slim ass has quit working and force closes. It starts again noticed only at boot up. I change batteries 3 times a day as I'm on it most of the time but only at boot and no other issues found. Thanks again. Will wait to go to slim bean as this runs great no need to upgrade yet for me

sent from my captivate running Slim ICS
[Captivate Android Development] bcflyfisher:
The Voice zip worked for me. I can now open Voice Search and use it without FC.

One weird thing.....Apex Launcher won't "see" Voice Search under Settings>Apps or in the App Drawer. It doesn't exist. I can make it appear in the App Drawer if I click on the "All Apps" icon in the list. Then it shows up and I can launch it from the drawer - but if I long hold on it and select "Add to launcher" it sends it to the Lightning Launcher homescreen instead. I don't use LL and Apex is my default Launcher. If I Freeze LL through TiBu then I don't even get the "All Apps" icon in the App Drawer. Fortunately, a long hold of the Search button opens Voice Search anyway so I don't need a homescreen icon.

To answer your other question, before the Voice zip I couldnt' use Voice Search or Voice Dialer even though the apps were there. I could, however, use the voice dictate in Swype.
[Captivate Android Development] kalda01:
I'm still on 4.1. didn't have time to mess around with upgrading. Probably will go to SB 2.0 when I can find the time.

Currently having a few issues with 4.1:

1. Whatsapp is chewing up over 50% of battery usage and the phone gets extremely hot .

2. The notifications pull down does not show the WIFI/BT toggles anymore.

Any suggestions ? should I try to flash 4.2 before going to SB (which requires a full wipe)
[Captivate Android Development] SynGamer:
So I went to stock, then upgraded to 4.2 and I don't have any service/signal...

EDIT: I'm back to stock (1-click KH3 GB)...tried flashing to SlimICS but still no service...where do I go from here? I have service with the stock ROM I just mentioned.
[Captivate Android Development] prbassplayer:
When on Slim are you sure you have a modem?....
[Captivate Android Development] SynGamer:
Yes. I've tried flathing empire 1.2.6sc via din and later cwm and the Rom flashes just fine bit have no service. Im currently using KH3 rooted...
[Captivate Android Development] nawlage:
Edit: post moved to Q&A
[Captivate Android Development] SynGamer:
So I'm on GB stock (rooted) thanks to 1-click. A few questions if anyone minds answering them:

1. how can I find out what my bootloader is?

2. I was using the Semaphore 1.2.6sc kernel + Odin to flash to my phone BEFORE flashing the device.zip and slimcommon (as the instructions advised). Is there a more guided post/thread for doing this? Perhaps I'm just not doing it right?

3. I. hate. stock.
[Captivate Android Development] justan00b:
Sorry if this is something dumb and the answer is posted somewhere but I couldn't find it... I tried flashing my girlfriends Captivate from CornKernel GB KK4 Legend ROM to this, but after flashing and rebooting system, it shows the AT&T World phone logo, then the (kernel?) boot logo of g 4.03 th or whatever, then it blinks twice and goes the CWMR Touch. I tried flashing CM9 and this but it does the same thing. Tried going back to my nandroid backup just to get the phone back to being a phone at least, but CornKernel just hangs after the loading bar fully finishes, tried even reinstalling fresh but can't figure out anything

Anyone have any suggestions? I'd reaaaaally appreciate it. Thanks in advance :)

Edit: I used the install instructions here installing a ICS kernel (devil), and then installing Slim ICS and the Slim common. http://www.slimroms.com/installationics.htm
[Captivate Android Development] prbassplayer:
1)If you are on stock GB then GB bootloaders. If when you turn off the phone it says AT&T i897. If you see i9000 then i9000 bl

2)Follow the instructions @ site. Get Cm9 booting then continue instructions.

First off that page is not being older page not being used. Use this one. Second it also says use CM9. Its better if you get CM9 booting THEN flash Slim ICS. Also remember that when you jump from Samsung rom to AOSP you need to flash the rom twice. (or when ever the rom partition is different you need to flash the rom twice, ei short flashing time).
[Captivate Android Development] justan00b:
Hey thanks for the reply.. Okay, so I'm trying to just flash CM9 for now like you suggested and get it booting. I flashed it twice and it updated me to CWM 6.0.1.1 or whatever, but every time it boots it only goes into CWM, it won't actually boot up. It shows the AT&T world phone logo, then galaxy s cyanogen mod logo, then blinks once and shows CWM and thats it, every time, and it wont boot into the actual phone/system. Its like it thinks I'm trying to go to recovery... ugh wish I knew what was wrong. Any ideas? Thanks man.. I tried installing CM9 twice, installed it and rebooted, installed it again and rebooted, but just goes to recovery like I was saying

Thanks for your reply! Just trying to get this freakin phone back working at 11PM here :(

Edit: Well I just used the stock KK4 odin installer ( http://xdaforums.com/showthread.php?t=1300843 ) for now and I'm back up and running... maybe I'll try this again later if I can figure out what I did wrong :(
[Captivate Android Development] prbassplayer:
Next time flash then flash a second time. If it boots to recovery then factory reset and format /system and reflash.
[Captivate Android Development] SynGamer:
OK, so I'm still on stock and I'm stuck with 3e right now. How do I upgrade from that so that I have a normal (modern?) CWM? This is the issue I always have when flashing, and none of the guides for the ROMs mention how to upgrade from 3e...
[Captivate Android Development] hitechchef:
These are the steps I follow to get from froyo to ICS and GB BLs with custom boot image. Many users may disagree, but they work for me every time.

1. Download and install stock. Use 512 pit ODIN. This will not change your BLs. Reboot. Now you have stock recovery.

2. Root your device and install Trusello's 3e recovery. Alternatively, there is a thread somewhere that points to stock kernel with infused voodoo and CWM recovery. You can use that also.

3. Place a rooted GB rom, Team Nyx ICS and slim ICS files on your internal storage.

4. Flash GB bootloaders. You can use i896 or i9000 BLs. I use i9000, seem to work smoother and better battery life for some reason,

5. Flash rooted GB rom from your internal storage. Reboot.

6. In case you want to change the image for your bootloader, now is the time. Follow Trusello's sig. You cannot change this image after flashing ICS. You will get stuck in bootloops and will have to start over.

7. Flash team Nyx ICS. In the installer, choose "stock kernel with Devil recovery". Slim is uncomfortable with TWRP. Reboot.

8. Flash slim rom files. Reboot and enjoy.

Skip the steps you have already covered. All the best.

PS: Good idea to have a working jig, in case you get stuck some where. Also remember to remove any lagfixes between any rom and kernel flashes. Also not a good idea to restore from CWM or tibu between different versions.
[Captivate Android Development] diakonos:
Low space, settings resetting

1. I'm still fighting off the low space warning message. The most free space I can seem to get with my current app list (~99 downloaded apps) is just over 30 MB. Using my phone and building some cache files brings me down to around 13-15 MB when the message shows up. I've noticed as I've tried to use the App2SD and Link2SD apps in an attempt to free up /datadata space, the "system data" has gone from about 75 MB up to nearly 100 MB. Is that normal? I've gotten used to using a "cache cleaner" regularly to keep the low space warning at bay. Clearing off MMS messages with images seems to help regain free space. The latest Google Maps update seems much larger than the last version as well :-|.

2. On a separate note (maybe related), I've been losing some settings when I restart my phone. My ringtones and notifications sound choices are either "unknown" or assigned to some other sound file seemingly at random. Also, I have an imported playlist in PowerAmp that seems to get cleared out each time I reboot as well and I have to re-import it from a saved .M3U file. Lastly, I use Swype Beta for text input and have it selected as the default but sometimes I notice that the Android Keyboard has changed to the default and I have to switch it back to Swype.

Do either of these problems sound familiar?

EDIT:

SlimICS 4.2 running stock kernel

i897 Captivate
[Captivate Android Development] kalda01:
Any suggestions ?
[Captivate Android Development] AtoZ0to9:
With all those issues, it's best to just wipe and move on to SB 2...
[Captivate Android Development] kalda01:
I read in the SB2 thread that many people had boot loop issues when flashing SB2 over SLIM ICS, so i'm a bit hesitant to go that way.

I never had any boot loops when flashing other ICS roms or going from GB to ICS.

Could the battery drain and over heating be related to the Semaphore Kernel ? is there a better Kernel I can use with SLIM ICS ?
[Captivate Android Development] AtoZ0to9:
Well it's kinda hard to tell man... You're running 4.1, which is old... and Semaphore didn't give me any problems with my cappy when I had it... have an S3 now...

I'd do this:

ODIN Oneclick I897UCKH3 Android 2.3.4 Gingerbread [With CWM Injected Kernel from Boog]

Flash latest CM9 with proper full wipes (to convert the FS)... might bootloop, just go back into recovery, and flash it again

Flash SlimBean 2 with proper full wipes
[Captivate Android Development] kalda01:
Thanks. I'll try the suggested procedure.
[Captivate Android Development] rcllcr:
Phone Being Deactivated by ATT Remotely

Hello all,

I am running slim ics and I love it. The only problem is (I don't know if this is rom related) my phone keeps being deactivated remotely by ATT. It happened once last month, and again today. My phone is blocked from using the ATT network, no text messages or phone calls. I can still use wifi. When I call ATT support, they tell me the phone has been deactivated because it was reported as stolen, even though I did not steal my device.

Anyone else having this same issue?

I appreciate the help.
[Captivate Android Development] prbassplayer:
Check your IMEI
[Captivate Android Development] rcllcr:
My IMEI number is:

00499******0000

I understand I may have a generic IMEI number and I must revert it. I can't find an up to date guide on how to do this.

Help is much appreciated.
[Captivate Android Development] prbassplayer:
First off don't ever say what your IMEI is, thats how it gets stolen ;). Second Did you have a backup of /efs? If not then your only prayer is Using ODIN to flash back to stock and see if it fixes it. Else you might need to send it for service. There is a method somewhere in i9000 forum but I have never used it.
[Captivate Android Development] rcllcr:
I do not have a backup but I have searched my IMEI number on google and many people have had the same problem as me. Apparently, the IMEI number I have is a generic one, note sure what that means.
[Captivate Android Development] prbassplayer:
Means your /efs folder got messed up. If your lucky flashing back to stock GB with ODIN will restore it. If it does back up the /efs folder and reflash SlimICS. If you get generic IMEI just use the backup /efs and should fix it up.
[Captivate Android Development] AtoZ0to9:
If nothing works, you need IMEI repair... go to this thread he has a Z3x box and shares it's USB connection over network, teamviewers into your computer, and repairs it...
[Captivate Android Development] AtoZ0to9:
DBL post...