yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] brettchuck:
I've had alot of random reboots on build 38. And some if I turn Wi-Fi off and then turn it back on later it will reboot.

I too have done a full wipe and install. So far, today, it has been stable....fingers crossed!

---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------

I did the no oc and it has been stable so far. Always before, I've been stable at 1500 with most past ROMs. Build 37 was stable at 1400 but quirky at 1500.
[Captivate Android Development] jde984:
well... i've had about 4 or 5 since posting that.

edit: and just to be clear, i'm running a couple mods here and there, so may not be the fault of aokp itself.
[Captivate Android Development] igoa:
Please tell me how to make any call recording app work with AOKP build 38?
[Captivate Android Development] brettchuck:
For what it's worth, I've been doing some more playing around with build 38. At least on my phone, it seems the FC's and reboots happen only when I OC to anything. I tried Semaphore 1.2.1c and had the same reboots and FC's.

If I leave it at 1000 Mhz, it is stable. I also noticed that the wallet ap had some issues with my phone. I uninstalled it and that helped as well.

So, I'll try staying at 1000Mhz with the latest Glitch and use GlitchassV2 and see how thing go.

It was flying great OC at 1500 while it lasted but was just not stable.
[Captivate Android Development] know50:
Build 38 stock oc 1.3 uv -75 looks great running fine for me. No reboots or lag. My internet is a little slow but I doubt it's the roms fault. Best ROM sense m5!
[Captivate Android Development] sinichi21:
Having reboots here I lost count already :( happens on all kernels i have installed and no oc on every kernel. I have installed glitch, semaphore, devil they all reboot once in a while I think its the rom love the ui changes though will still check hopefully the rebooting will stop xD
[Captivate Android Development] Joecascio2000:
Just thought I should chime in with my build 38 experience. I flash build 38 right over prefixed build 37 (no wipe) and all is good. Had to lower my clock speed to 1200 but my voltage settings are the same and have had no reboots. One thing I have noticed (probably not the roms fault) when installing/uninstalling/updating an app, my phone freezes and I get a system not responding message. I always hit wait and all is good. Probably time for a wipe install. Other than that so far so good. Even at a lower clock speed it still flys.
[Captivate Android Development] CheesyNutz:
no reboots here running build 38
[Captivate Android Development] RickHenry:
I also have had the wifi tethering issue with both b37 and b38. I tried flashing the Semaphore kennel and still did not work. I flashed the stock Glitch v14 b6 and it started working. I don't know what I am missing from the optimized Glitch that Sixstring ships with the b38 ROM, but wifi tethering is working.

BTW, with fiops scheduler and glitchassv2 governor, battery life is excellent.

Sent from my ICS Captivate
[Captivate Android Development] moymike:
Having issues with 38 also

The day 38 came out, I loaded it. (coming from 37) I did a factory reset and tibu'ed my apps back, as I have done for the past number of updates.

The two issues I have had with 38 are, poor battery performance and B(lack)SOD.

I have tried everything I can think of to deal with the battery, but with 35-37, I would end the day with about 50 percent. With version 38, around 6pm my phone goes dead.

This morning, after fully charging and loading the updates on the market, I jumped into my car and could not wake up my phone. It looked off, but would not turn on. I popped the battery, and got it running, but now two hours later, same thing.

I loaded 38 the day it came out, and have been careful with not adding any new apps, in case these are app issues. This morning, I am flashing back to 37(fixed version), and looking forward to version 39.
[Captivate Android Development] brettchuck:
So far, I've not had any reboots since dropping my OC speed down to 1000Mhz and took out the Wallet app yesterday. Voltages are still stock settings.

I moved up to 1200 last night and still stable. I'm still on GlitchassV2 and have real good battery life.

We'll try going up to 1300 today and see what happens.
[Captivate Android Development] moymike:
Very strange, my wife is running Milestone 5, and her phone did the same thing. I was able to pop the battery and boot it, only to see it go back into black screen before I could even run TiBu.

Besides both running AOKP (M5 and 38) the only thing our phones had in common is that I did the market updates on both this morning. I'd guess something in the update caused the issue.

I was able to get both phones working okay by reflashing the ROM and Gapps.
[Captivate Android Development] richsale:
I'm on v38 2 days now and have'nt touched oc and haven't had a reboot. So far I'm really liking this rom.
[Captivate Android Development] kangi26:
Just to add in a point that maybe it's a base related issue(not that I'm a dev or actually HAVE the knowledge) but, I'm currently on CM9 Official Nightly 20120603 stock everything and came from stock JF6 and master cleared. I am having the wifi hotspot drop when checked, BUT it'll stick if I hit it again, and immediately hit configure.

Like I said I dont know if this info helps even a little bit, but it seems coincidental to me
[Captivate Android Development] mbc663:
You guys having to do battery pulls...are u making sure deep idle is OFF
[Captivate Android Development] zelendel:
You know guys giving a logcat of the reboot may help a bit more then just saying how many times it has done it. But hey thats just a thought.
[Captivate Android Development] bdithug:
Ive had that issue with stock Gingerbread before. Screen doesnt turn on, it looks like the phone is off, but when you hold the power button it doesnt turn on. The phone is still on but its the screen that doesnt respond. If you hold or press the volume keys a bunch of times you will sometimes hear the phone make a sound as if you are turning up the volume on the phone, so I knew the phone was on. Instead of taking out the battery, try holding the power button+volume up+volume down for 10 seconds. It forces a reboot
[Captivate Android Development] Soccer_Dad:
The FAQ link in the OP is dead.

Hoping this ROM (or the last milestone) manages to stop the SOD's.
[Captivate Android Development] Jammn:
Hello I am running build 37 and getting a "Low on Space" message. Does anyone know how to fix this? I've checked to phone but cannot figure out where is almost full.
[Captivate Android Development] know50:
You should download goo manager and update to 38. Also I found a low space fix flashable zip that worked for me. I can't remember where I found it but I'm sure if you google something like low space cm9 aokp you'll find it to. Haven't had the problem since I flashed the fix.

---------- Post added at 10:36 AM ---------- Previous post was at 10:23 AM ----------

Just want to through this out there.. I'm now oc to 1.4 and uv at -75 with no sod or random reboots and my phone is flying. Only time I've had any issues was when deep idle is on or when I change from glitchass v2 or deadline. On 37 I couldn't uv at all without having issues. Also on 38 I noticed it was a little buggy until I used tibu to uninstall a bunch of apps that I really didn't need then all was better. I wish I could say which app or apps was causing the problems but I uninstalled like 30 apps ( mostly bloatware ) so I'm not really sure which ones were trouble. everything is smooth as butter now and IM loving it. Good luck to all and to sixstringsg and all of the devs, you guys are so awesome! Thanks a bunch!
[Captivate Android Development] jde984:
I'd love to provide one... Unfortunately adb has been a no go on the work pc (i can't install crap...), and it was happening at work. :(
[Captivate Android Development] leezrd:
Download "alogcat" from they market
[Captivate Android Development] jde984:
normally good alternative... but not very effective for logging reboots...
[Captivate Android Development] Jammn:
Installed build 38 today once with no wipe, and once with full wipe. Both times wifi would be toggling on/off by itself with no way to stop it.

Reverted to build 37. Anyone had that problem?

PS. After reinstalling build 37 and restoring apps and data "low on space" error has gone away
[Captivate Android Development] TRusselo:
running build 38 with the kernel from 37 and have no issues anymore... no oc / yes deep idle.
[Captivate Android Development] bdithug:
What's this Roms new website? My bookmarks is telling me its down.

I'm still on milestone 5 because I'm hesitant about upgrading. Ive noticed more people having issues with the proceeding builds. Hopefully it wont be long until milestone 6, my number one priority is the Rom being stable and bug free, not any new features or bells and whistles. Even milestone 5 has more bugs than milestone 4.
[Captivate Android Development] Sword_of_a_1000_truths:
just reflashed 38 and everything stock out the box and having a prob with wifi not turning back on when toggling off then on. wifi works fine after initial setup but after a while ill toggle it off then on and it either reboots or wont detect any networks anymore. any one else repeat this problem on their phone?
[Captivate Android Development] Wdustin1:
Flashing devil kernel solved all issues for me
[Captivate Android Development] RCDuke:
I also had the wifi rapid toggle on/off issue, but I wiped and reflashed build 38 and it hasn't happened again.

I'm running without any OC or change in voltage, and I have yet to get a sleep death yet. Haven't tried charging overnight yet.
[Captivate Android Development] theaudioguy:
When ever I flash a build (either new, or trying to to get the attached kernel) without doing a wipe, I always end up with the ROM control fc due to the weather option. How do I stop this from happening? I don't think it's an issue with the ROM or anything because people have success doing this.
[Captivate Android Development] jde984:
you wipe...
[Captivate Android Development] theaudioguy:
That's what I usually do when a new build comes out. But when I want to reflash the built-in kernel (I haven't looked into extracting it by itself yet) I just reflash the ROM. But I always get that fc. I know other people flash the ROM without a wipe. Just wondering what they do.
[Captivate Android Development] pizz0wn3d:
did you install gapps? I get that problem whenever I forget to flash gapps with AOKP.
[Captivate Android Development] theaudioguy:
I do when I do a wipe then flash the ROM. But I don't reflash gapps when I flash without a wipe. I might have to try that sometime.
[Captivate Android Development] know50:
When you flash the ROM to get the kernel you need to wipe cache, wipe dalvik cache, flash ROM, flash gapps, and fix permissions. This has always been the method as far as I know. Below is a link that should help you extract the kernel. It's easy

http://forums.infectedrom.com/showthread.php/1031-How-To-Extract-a-Kernel-From-a-ROM
[Captivate Android Development] theaudioguy:
You are a lifesaver. Thank you, kind sir. (I assume you're a sir)
[Captivate Android Development] know50:
Lol yep I'm a sir. you're welcome
[Captivate Android Development] xhalz:
Can someone help me out...so I recently flashed AOKP Build 37 on my Samsung Captivate and it is working great, but Swype doesn't work

I tried Swype Beta and I get a parse error, tried restoring Swype from titanium backup and it doesn't allow me to select as a keyboard option though, i tried da swypes but it did not install and i tried an older swype installer 3.26 which apparently doesn't give parse error, but did not install for me..

It is not the end of the world, but can someone put me on the right track of what I must do to get Swype
[Captivate Android Development] Marvout:
Just flashed my daughter's captivate to AOKP 38. I'm getting a non-responsive solid black screen if I turn the screen off and try to power it up after more than 10 seconds. An instant off/on will turn the screen off and then back on. But anything more than about 10 seconds and I can't turn the screen back on.

The only way I can get it to turn on again is if I do a number of power button presses/holds and finally it will give me a boot screen.

This was a stock Rogers Froyo and I rooted it via Odin. I've flashed the ROM, cleaned caches, factory data reset it and reflashed over again. I've been at it all evening and I can't get it to power back on like it should.

I've read about deep idle, but I can't find that setting. I don't know if that's related.

Any ideas what I should try next?
[Captivate Android Development] pizz0wn3d:
Did you ever put gb bootloaders on it?

Herp derp Captivate Tapatalk 2
[Captivate Android Development] tvotony:
+1
[Captivate Android Development] xhalz:
hmm I hate to post so soon, but I really like AOKP so far, but I have a bigger issue than my swype one.

I was on andromeda and flashed to AOKP. I used the Galaxy S Unlock Tool on andromeda and it worked fine

but when I went to check if my phone was unlocked by using *#7465625# it tells me

"Connection problem or invalid MMI code."

I am traveling in a few days and need to be sure my phone is unlocked, can someone please help me out!
[Captivate Android Development] know50:
you should delete everything Swype related with titanium backup first. Then probably download the Swype installer from the website and go through the setup with the installer just as a starting point. I think you should prolly just download goo manager and upgrade to build 38 with a full wipe and don't use titanium backup to restore Swype. Start from scratch, do a backup first of course though.
[Captivate Android Development] b-eock:
Once unlocked always unlocked... please search and don't post non sense in the development section...
[Captivate Android Development] fractaline:
I'm using da Swypes.... which i restore from tibu after a wipe.

Remember

you need to select Swype in settings before you can select it in ime switcher. also make sure you uninstall the installer before you side load Swype. Hope that helps.

Phoned in.....
[Captivate Android Development] ssallen1971:
Flashed to B-38 tonight, I dont have radio signal, and I dont know how to get it back. Can a kind person help me out.

Thanks.

Steve

UPDATE: I fixed it, I just wiped everything and started over...

Now if I can get TiBU to find my back up ill be set...

Steve
[Captivate Android Development] melvinaury:
Just go to TIBI in the prefetence menu, backup directory and choose the location of you're backup directory or you can select search to let the program find the folder.
[Captivate Android Development] Marvout:
I did do number 5 from here, so as far as I understand, Yes, it should have a GB bootloader.

Interestingly, the Captivate has been plugged into my computer all night to charge and had no problem turning the screen on this morning. So screen off/on works while charging. Just not while on battery.
[Captivate Android Development] know50:
what build are you on? And have you tried flashing twice? Reboot into recovery, wipe data factory reset, wipe cache, wipe dalvik, then go into mounts/storage and wipe everything except sd card and emmc. reflash build 38, reflash gapps then fix permissions and reboot. Good luck

---------- Post added at 09:04 AM ---------- Previous post was at 08:21 AM ----------

For everyone that's having the low on space message problem here is the fix I used. Works for me so I hope it helps.

http://xdaforums.com/showthread.php?t=1541942
[Captivate Android Development] pizz0wn3d:
Do NOT wipe everything but those. Only wipe /system. Wiping /boot can cause some serious issues. It's how I bricked my last Cappy.

Herp derp Captivate Tapatalk 2
[Captivate Android Development] Marvout:
This is what I read on my about page:

Kernel Version

3.1.10_IcyGlitch_V14-B6_I896-I897

Sun Sat June 3 18:10:58

Build Number

IMM76I

Mod Version

aokp_captivatemtd_build-38

---

I went through every step, exactly as you stated and still have the same issue. It seems though I never left it alone long enough, because actually it is a boot loop! Screen powers off and after about 30 seconds the phone reboots.

I've reflashed before. I think about 4 times. I even tried build 37. It had the same issues. I had never done any of the mounts/storage formats before, but I did all the other wipes.

I'm still stuck. Any other ideas? Does the boot loop change the possible issue?
[Captivate Android Development] pizz0wn3d:
Odin back to stock gb and reflash.

Herp derp Captivate XDA Premium App.
[Captivate Android Development] know50:
I didn't know that. I've never had any problems wiping boot.

---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------

+1

---------- Post added at 03:21 PM ---------- Previous post was at 03:13 PM ----------

Maybe you got a bad download. I would probably do what pizzown3d said and odin back to stock gingerbread. Then I'd probably redownload everything and start the flashing process over again.
[Captivate Android Development] Marvout:
I would have been way ahead had I done that in the first place. It worked fine. Well sorta. Did the One-Click Odin back to Rogers stock GB. That worked as adverstized. Then flashed SpeedMod, completed fine but wouldn't load into recovery until more than a dozen tries, but I only had CM9 on my SD at that point (I had formatted it in between). Flashed that to to give me a CWM Recovery that could see the external SD. Then I flashed AOKP-38. But this gave me CM9 boot screens and AOKP finally loading. So I wiped all I could and over flashed AOKP-38 again. But this gave me the WIFI twitch. So I wiped all I could over again, and re flashed AOKP-38... and ta da! It worked.

Thanks for the advice and help. So my word of advice (to myself, because I'll forget before next time) is to go to stock Gingerbread before trying to move to ICS.
[Captivate Android Development] Joecascio2000:
The Linaro Code looks promising. Hope we see it with AOKP. But I can't imagine my cappy faster than it already is.
[Captivate Android Development] leezrd:
Looks nice
[Captivate Android Development] know50:
For some reason Android OS is eating up a lot of battery on build 38 for me. The past 3 hours I've went from 100% to 70% and haven't used the phone at all. And this is with everything stock, no oc or uv. I noticed that I was getting way worse battery life when I first installed 38 but wanted to give it some time to see how it played out but it almost feels like it's gotten worse. Anyone else seeing this?
[Captivate Android Development] CheesyNutz:
Notice this as well androidOS chewing up the battery. Not as high as yours but staying around 30%
[Captivate Android Development] TRusselo:
wondering if anyone else is running build 38 on a sim unlocked captivate and has service with IMEI showing anything at all....

few weeks ago I unlocked a friends stock rogers captivate with galaxy_s unlock by herloz then flashed it to aokp build 36. all went well. works great on fido network and IMEI is fine (correct)

the past few days i have been trying to do the same to my phone, but aokp 37 and 38 will say imei unknown, and obviously has no network connection. build 36 will show imei but the wrong imei. ending in 0000

my process is as follows, flashed to stock GB, root, busybox update, then sim unlock, GB sees IMEI just fine, then update to AOKP, but IMEI is unknown at this point, no signal. flash back to GB stock, IMEI is correct and working.. still sim unlocked. so it would not be a corrupt efs folder if it works on GB and not aokp. I have tried several times but still cant get it to work, though my friends captivate works fine still. but she is on build 36...

one other note.. the rogers captivates do not have the sim unlock code "in" the phone, and must be unlocked by the root "change lock bytes" method.

i followed the same process for both phones... confused. I need to have my phone unlocked as my new job is in a location that does not have rogers service, i have a bell sim card to use at work. if build 35 does not work i may have to suffer with stock at work for the 15 days i am stuck here every 3 weeks... (camp job).

something must have changed in build 37 that changes how efs folder (imei) is handled/read.
[Captivate Android Development] theaudioguy:
a couple months ago I used that to unlock my phone, now I'm on AOKP 38 and all is good. Not sure of how I

can be of any help though.
[Captivate Android Development] TRusselo:
did you use the "change lock bytes method" or "unlock CODE method"??
[Captivate Android Development] leezrd:
Will using hext editor on the nv data file and going to 1600 and something line, then going and changing file from 01 to 00 not work?

Edit: here is line 181468 and added picture
[Captivate Android Development] theaudioguy:
Unlock code method
[Captivate Android Development] TRusselo:
yeah then you missed the point of my post...
[Captivate Android Development] armando_rod:
There's already an AOKP build with Linaro's optimizations (not sure if is official) but hoping to see that for the Captivate
[Captivate Android Development] leezrd:
Would the method i said not work?
[Captivate Android Development] leezrd:
Hope to see it on cappy
[Captivate Android Development] TRusselo:
i was just about to try your method. thanks for the great pic and info.

BUT. i just fixed it!! flashed build 34 from stock, then upgraded to 38 and all is good now. also took out the sim card while i did it.

damn F.R.E.D.s (Friggin Re-tod-did Electronic Devices). some times these phones make me feel like "eye em sofa king we tod did"
[Captivate Android Development] theaudioguy:
I guess I did.
[Captivate Android Development] sixstringsg:
Gerrit is currently down, so I can't grab the linaro stuff yet.
[Captivate Android Development] b-eock:
Hey six this showed up on B38. The brightness control using the status bar as the slider( not the one in the notification area, just sliding your finger on the bar to adjust brightness) doesn't work. I have the option enabled.
[Captivate Android Development] brettchuck:
Try using Fiops as your active scheduler and GlitchassV2 at your Governor. That increased my battery life a lot and I'm OC'd to 1400Mhz.
[Captivate Android Development] know50:
Thanks for the advice I'm giving it a try now
[Captivate Android Development] Joecascio2000:
Auto brightness can't be enabled.
[Captivate Android Development] fractaline:
I use it daily on b38..... works well.

Phoned in.....
[Captivate Android Development] know50:
It's not working for me either
[Captivate Android Development] TorqueWrench001:
Enabled this feature and it didn't work till I rebooted. Now its working well.

+1 I am interested to see what blazing speed can be achieved incorporating this code into our AOKP rom.
[Captivate Android Development] know50:
I can confirm that sliding finger slowly across the status bar for brightness is now working after reboot. It only works if you go slow and if the pulldown is up.

---------- Post added at 08:01 PM ---------- Previous post was at 07:54 PM ----------

Fiops and glitchass v2 has actually increased my battery life noticeably. thanks a bunch. Also want to add that Android OS has gone back to normal again. I don't know what made it jump up so high though.
[Captivate Android Development] RickHenry:
Did you go to b38 from a build that had internal SD and EMMC reversed? The only time I have seen Android OS with a significant amount of battery time was when I did that. Don't know if it was rebuilding the file system on the new mount or what, but whatever it was it got done doing it and my battery life went back to its normal awesomeness. Also been using fiops and glichassv2 for quite a while, it seems to be the best combination of battery life and performance.