Database Develop

All calls end after 36 secs-Anyone else?

Looked at the sticky, but did not see this issue. It was happening on my cyan builds once I went to donut. I swapped, updated all, wipe, install per instructions, but the prob found me again. This time I am not the official 1.6(DRC83, 2.22.19.26I) Anyone else have this happen to them?
Fixes?

Okay, so the time ranges between 30 seconds and a minute.
From what I am seeing, I may have to revert back to stock settings and give it a go. If that works, then I will attempt to ROOT again.
I only began having this issue after I upgraded to 1.6 via cyanogen.
I swapped ROMs hoping to solve the issue ( thought it may have been b/c of the experimental/beta version)
But after being on this build for one day, I am already experiencing the issue again. I even went as far as repartitioning and wiping before I started so it would be a clean slate.

ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?

derfolo said:
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
Click to expand...
Click to collapse
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.

ljnick19 said:
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
Click to expand...
Click to collapse
The HTC recovery may have messed your radio up. Try reflashing the radio.

Thanks for the input! I was worried no would have any ideas. I'll give that a shot. Now when reflashing the radio, do I need to do the whole-radio, spl, rom, wipe thing? Or just radio?

I am also using Ra v1.2.2 recovery, could that be causing issues w/ 1.6, Donut ROMs?

One more issue to add: AdvancedLauncher (processandroid.process.acore) has stopped unexpectedly. FC almost every time i press the home button. Made the mistake of making advanced launcher my default home button action...

For the launcher make sure you have the latest version. Then reinstall or run fix permissions. U only have to flash the radio, and the recovery should only affect flashing the roms

Thanks a mill for the help, I really thought this was going to fall flat. I'll attempt later this afternoon and post results.

For those of you that took a moment to not only read, but to assist, THANK YOU!
Results are:
I went from OTA 1.6 to Cyan 4.1.999
I wiped and repartitioned the sd as well as redoing the radio
So far, I have not experienced any FC's. Unfortunately, I have not made a lot of calls either. Crazy thing was that on the OTA build today, calls seemed to be functioning, but the FC's were excessive.
I also ran fix permissions as well as cleared the dalvik cache.
Again, thanks for the support. I hope to pass it on if I am ever able to help, it is appreciated!
LJ

Constant rebooting

i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.

If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?

I do have a overclocked under volted kernal

sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...

WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !

Does your phone lock up (unresponsive) before rebooting?

Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.

Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.

I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.

Kernels causing reboots? Or is it something else

When I was on DocRambone's 7.5 JPA with the older ReOrient kernel 2.1.1 I never had soft reboot problems and then it seems I started getting them after a lot of the Captivate kernels started incorporating these small tweaks.
After reading a lot of other posts other people have been having this same problem but we have no idea what is causing it. At first I thought it was one of the tweaks that you enable in the new recovery ULF tweak section but after disabling all those tweaks and doing a factory reset I was still getting them.
I tried a very untweaked setting with haptic feedback and only bln (no lagfixes, etc...) and it still happened.
Has anyone been able to find the culprit? I've tried 2 different kernels: Reorient and SetiroN's.
When I have my phone in my pocket and I'm driving I'll randomly feel haptic feedback even though I dont have a call or text and shortly thereafter I'll get 2 small vibrations and then a reboot. Once it reboots it seems to come back up for a few minutes and reboot again. I was using ChompSMS with BLN and haptic enabled and that was pretty much the only things I changed from stock.
P.S - The purpose of this thread is to put a collaborative effort in finding out WHY our phones are restarting for some unknown reason. As this community and devs grow, sometimes problems like this arise.

I have seen a few post about the reboots. I have never had any with the kernels. Its kinda strange some of us dont have the issue.

there are several reasons for soft reboots.
if you are running an i9000 rom with a captivate modem, you will get them
if you are running an i9000 rom with a particular modem that doesnt work in your area, you will get them when the modem tries to hand off between towers.
you can get them from oc/uv, bad framework hacks, bad rom, etc. it is all circumstantial, it all depends on what changes you have made from stock....

Pirateghost said:
there are several reasons for soft reboots.
if you are running an i9000 rom with a captivate modem, you will get them
if you are running an i9000 rom with a particular modem that doesnt work in your area, you will get them when the modem tries to hand off between towers.
you can get them from oc/uv, bad framework hacks, bad rom, etc. it is all circumstantial, it all depends on what changes you have made from stock....
Click to expand...
Click to collapse
The DocRambone 7.1 and 7.5 I9000 ROM uses the JPP modem if I'm not mistaken, and I never had reboots. It wasn't until I went to reorient kernel 2.1.2 (or 2.1.3 can't remember) that these reboots occurred.
Right now I'm doing Doc 7.6 MikeyMike01 with JG8 modem and SetiroN 1.2. I also had a previous setup of using JPP and a different rom with both kernels and had reboot problems.
If the modem is somehow causing reboots I may go to the stock captivate modem and see what's going on.
So far in my apartment the phone has not rebooted by itself (has had a constant HSUPA connection). I'm also running the ROM stock without recovering any of my apps. When I leave here soon I'll see if my phone restarts. If it does, then it would appear a modem issue may be at hand.

smokestack76 said:
I have seen a few post about the reboots. I have never had any with the kernels. Its kinda strange some of us dont have the issue.
Click to expand...
Click to collapse
What type of setup do you have?

LinuxNewb said:
What type of setup do you have?
Click to expand...
Click to collapse
Cog 2.3b modded with setiroNs kernel. No oc/uv enabled, Using the jpp modem with Hsdpa working.

For some reason clearing dalvik cache and fix permissions in recovery did it for me..i haven't reboot since
xdaApp via Captivate

darkamikaze said:
For some reason clearing dalvik cache and fix permissions in recovery did it for me..i haven't reboot since
xdaApp via Captivate
Click to expand...
Click to collapse
If my phone crashes ill try that and see if works. So far at home it's been perfect.

LinuxNewb said:
If my phone crashes ill try that and see if works. So far at home it's been perfect.
Click to expand...
Click to collapse
That makes me think modem.

smokestack76 said:
That makes me think modem.
Click to expand...
Click to collapse
why is that .. ? soft reboots did only happen to me when I wasn't home lol

darkamikaze said:
why is that .. ? soft reboots did only happen to me when I wasn't home lol
Click to expand...
Click to collapse
as i stated earlier, the soft reboots usually occur due to modem/rom incompatibilities when the modem is trying to hand off from network to network.
this was a part of our experiments with the ji6/jpk roms that boomerod, shep, and several others were testing. it has to do mostly with the 850mhz frequency.

interesting.. well i'm on JPP right now.. so far stable

darkamikaze said:
interesting.. well i'm on JPP right now.. so far stable
Click to expand...
Click to collapse
i am on jpp right now also, and am about to go for a drive to make sure its completely stable with the handoffs.

I remember one time i did a certain combination of install rom, restore apps and apply jfs lagfix and a popup came up that said i had mismatching uid's and that i had to format /data directory.
Sure enough soft reboots all.over the place after some fc's.
I found that the best way to use the lagfix is to restore apps b4 lagfix and activate the tweaks at the same time as the fix. It works for me
Sent from my GT-I9000 using XDA App

The JG8 modem for me in Shep's ROM causes frequent soft reboots. As soon as I get rid of it, problem solved.

fatttire said:
The JG8 modem for me in Shep's ROM causes frequent soft reboots. As soon as I get rid of it, problem solved.
Click to expand...
Click to collapse
Ya... as soon I started driving my phone would restart. When it's at home nice and solid connection theres no problem lol
So if we narrowed it down to a possible modem issue lets start testing which ones work.
Fatttire - If you could attach the modem you're using so we can try it out that'd be cool did anyone play with the combi bands or any other settings within the service mode?

tytdfn said:
I remember one time i did a certain combination of install rom, restore apps and apply jfs lagfix and a popup came up that said i had mismatching uid's and that i had to format /data directory.
Sure enough soft reboots all.over the place after some fc's.
I found that the best way to use the lagfix is to restore apps b4 lagfix and activate the tweaks at the same time as the fix. It works for me
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I didn't even restore apps or do any lagfixes and I'm having this issue Good to see yours worked for you though. Hopefully we'll find a modem thats compatible with this JPA/JPP setup.

I've only used stock modems on our two captivates - occasionally they will restart out of the blue.
Once in particular I think it was because of a live wallpaper. After disabling it, everything seemed smooth running again. I just use plain black wallpaper and mine never reboots.

K-mart Shopper said:
I've only used stock modems on our two captivates - occasionally they will restart out of the blue.
Once in particular I think it was because of a live wallpaper. After disabling it, everything seemed smooth running again. I just use plain black wallpaper and mine never reboots.
Click to expand...
Click to collapse
Ive done so many weird configs of roms/firmware/kernel/custom frameworks and I've never had an issue with reboots. I ran a 2.1 i9000 setup with HSUPA and that never ever reset on me.

JG8 is only to start with to enable 850
fatttire said:
The JG8 modem for me in Shep's ROM causes frequent soft reboots. As soon as I get rid of it, problem solved.
Click to expand...
Click to collapse
The JG8 is an Eclair modem, not Froyo. Its purpose is to use at the beginning of an install from stock JF6. Once you have the rom and kernel you want, you need to replace it with a Froyo (suggest JPP) modem.
Don't leave yourself running a Froyo (i.e. Shep) rom with an Eclair modem, you are just asking for trouble.

[Q] Upgrading speedmod to k13a

When you upgrade from the kernel baked into serendipity, do you need to do anything other than flash the new one? When I did this without changing any kernel settings in CWM, I got horrible battery drain, and looked to see kswapd0 jumping in at 50-75% on osmonitor. I know this has something to do with the lagfix but didnt want to monkey around in CWM until I was clear. In other words does flashing k13a over the serendipity speedmod carry over tweak settings or does it not, which would have caused my problem, or could the runaway kswapd0 be from something else? Flashing back to the backed up original kernel does fix the runaway process.
Only reason I want to upgrade is to keep learning how this all works together. And im a sucker for the latest and greatest. Searching yielded info on that process, but not much about how to remedy the issue, so apologies if im missing a relevant thread.
Thanks in advance.
Captivate fixed by Serendipity 5.7

sonicdescent said:
When you upgrade from the kernel baked into serendipity, do you need to do anything other than flash the new one? When I did this without changing any kernel settings in CWM, I got horrible battery drain, and looked to see kswapd0 jumping in at 50-75% on osmonitor. I know this has something to do with the lagfix but didnt want to monkey around in CWM until I was clear. In other words does flashing k13a over the serendipity speedmod carry over tweak settings or does it not, which would have caused my problem, or could the runaway kswapd0 be from something else? Flashing back to the backed up original kernel does fix the runaway process.
Only reason I want to upgrade is to keep learning how this all works together. And im a sucker for the latest and greatest. Searching yielded info on that process, but not much about how to remedy the issue, so apologies if im missing a relevant thread.
Thanks in advance.
Captivate fixed by Serendipity 5.7
Click to expand...
Click to collapse
I would start by calibrating the battery. http://forum.xda-developers.com/showthread.php?p=7723557 this usually fixes my drain. hope that helps otherwise i would start with a stock reflash with odin before trying again it couldnt hurt.

I dont think its battery stats.since.flashing back fixed it, pretty sure its a setting im not fixing or an incompatible app.
Captivate fixed by Serendipity 5.7

sonicdescent said:
I dont think its battery stats.since.flashing back fixed it, pretty sure its a setting im not fixing or an incompatible app.
Captivate fixed by Serendipity 5.7
Click to expand...
Click to collapse
yes, 5.7 comes with k13a.

It does? Mines still k12s.

Reboot & Wifi "error" after 2 weeks of using any ROM

Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!

Sorry for the double post,
Is there a better forum to post this in?

spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate

Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.

Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance

spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.

I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.

bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...

New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?

New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl