Database Develop

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.

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

freezes on calls

Hi, I have seen similar questions but no real answers. I have a Galaxy S rooted and on a MIUI gingerbread rom with Glitch 13.1 kernel. Phone works perfectly on this rom. Now my problem is I want to install ICS roms, in which I have successfully. Every single 1 of them run smooth except when a call comes in. It freezes up the phone, weirdly enough if you have a set of headphones plugged in it does not freeze. Stock firmware also had same issue. The MIUI rom with glitch kernel do not have these issues. My question is, could there be something in the kernel or the rom that could be transfered into an ICS rom? Or is there something else goin on?

troy550 said:
Hi, I have seen similar questions but no real answers. I have a Galaxy S rooted and on a MIUI gingerbread rom with Glitch 13.1 kernel. Phone works perfectly on this rom. Now my problem is I want to install ICS roms, in which I have successfully. Every single 1 of them run smooth except when a call comes in. It freezes up the phone, weirdly enough if you have a set of headphones plugged in it does not freeze. Stock firmware also had same issue. The MIUI rom with glitch kernel do not have these issues. My question is, could there be something in the kernel or the rom that could be transfered into an ICS rom? Or is there something else goin on?
Click to expand...
Click to collapse
I started having that issue with CM9 and i'm now running Helly Bean and i'm still having the same issue has you are. The only way I can answer a call without having my phone freezing for 30 seconds is to have a headset connected. I've tried a few different modems, cleared my phone.apk cache, flashed numerous times with data wipes and I'm still having this issue.
I noticed yesterday that my IMIE was wrong so I deleted my /efs/ directory and re-installed a backup that I had and now my phone has the right IMIE.
Basically, just wanted to know what you ended up doing with this issue or if anyone has another suggestion.
BTW, I can't use odin to flash a new modem since my phone also doesn't want to connect via usb (download mode / adb / odin).

if you got your,, IMEI, flash stock rom with pit512 and re-partition, PDA, modem, csc, I hope that download works? Uninstall Kies, if you just give the driver and samsung, if you can not download help, jig, or instructions are on the forum.
---------- Post added at 04:26 PM ---------- Previous post was at 04:19 PM ----------
samsung driwer here.
http://forum.xda-developers.com/showthread.php?t=961956

dre_bake said:
I started having that issue with CM9 and i'm now running Helly Bean and i'm still having the same issue has you are. The only way I can answer a call without having my phone freezing for 30 seconds is to have a headset connected. I've tried a few different modems, cleared my phone.apk cache, flashed numerous times with data wipes and I'm still having this issue.
I noticed yesterday that my IMIE was wrong so I deleted my /efs/ directory and re-installed a backup that I had and now my phone has the right IMIE.
Basically, just wanted to know what you ended up doing with this issue or if anyone has another suggestion.
BTW, I can't use odin to flash a new modem since my phone also doesn't want to connect via usb (download mode / adb / odin).
Click to expand...
Click to collapse
Got a cm7 to work also with glitch 13.1 but now it hangs a little to try and hang up but answers fine now. But not 1 issue with Miui gingerbread rom and glitch 13.1 works like new but dont care much for rom so had to do lots of customizing with different apps.

WiFi issues with custom roms

So with custom rims installed I can't activate wi fi. I click the wi fi button and it just flashes and turns off. Quite irritating. I logcat and it says something like WiFi no data found. Somewhere along those lines. So now I'm back at the stock kernel. 10.3.1.E.0.191. I have a locked downloader as mine cannot be unlocked officially. It's C6606, and this is a confusing issue and I can't find a solution anywhere as no one else seems to have this problem. I've tried 2 different roms, uninstalling and reinstalling them. Still nothing...please help its frustrating.

what custom roms have you tried? seeing as you have a locked bootloader you will only ever be able to use a stock kernel and rom based on that

Richy99 said:
what custom roms have you tried? seeing as you have a locked bootloader you will only ever be able to use a stock kernel and rom based on that
Click to expand...
Click to collapse
Modified and existentZ. I use philztouch recovery, if that helps at all. Everything else works fine, just the WiFi won't activate. And seeing as how everyone else says it works for them I can only assume either my phone is incapable of running rims correctly or I'm doing something wrong. Which I'm sure I'm not going to have the first phone to never be...Rom...able.

N910T3 Strange Problems. Please Help!

Ok so I get a brand spankin' new warranty swap and its a N910T3 with 5.1.1 etc. Awesome right? Well not so fast.
I seem to be encountering several strange problems I wanted to see if anyone else had these issues.
First off I started having some issues with the fingerprint scanner. Not reading or scanning as its has been flawless. It occasionally has thrown a "Scanner not working" error and makes me use my backup.
Next occasionally there's some strange lag here and there. I don't mean usual android or sammy lag I mean like something just isn't right lag.
Not sure if the lag is the same but on occasion in the middle of doing something like texting or emailing it will just show the background wallpaper freeze for a few secs and then eventually lock itself.
Also if my phone screen is off and locked and I get some form of notification unlocking the phone acts strange.
All of the issues seem to be more annoying then anything. I have not had any kind of FC at all just pauses and freezes and lags.
This is night and day from my old phone that I used for almost a year. I am just trying to find out if this is perhaps a hardware defect or bugs in this Android version. I am kind of hoping its bugs this phone is squeaky new and it would be a shame to lose this shiny new phone for a old refurb.
Has anyone experienced any issues with their N910T3 while on the latest stock?

DeeXii said:
it will just show the background wallpaper freeze for a few secs and then eventually lock itself
Click to expand...
Click to collapse
That looks exactly like a typical SystemUI FC... (without the FC message in your case) I guess you are not rooted right? If you are... try wiping Data/Cache/Dalvik x3 via TWRP, and Odin the latest stock firmware... DOG1 ... If you are not rooted... simply reset to factory and do the same... Odin DOG1. and re-test your Note 4... if problem persist... then you might have a Real Hardware issue.

TEKHD said:
That looks exactly like a typical SystemUI FC... (without the FC message in your case) I guess you are not rooted right? If you are... try wiping Data/Cache/Dalvik x3 via TWRP, and Odin the latest stock firmware... DOG1 ... If you are not rooted... simply reset to factory and do the same... Odin DOG1. and re-test your Note 4... if problem persist... then you might have a Real Hardware issue.
Click to expand...
Click to collapse
I am not rooted and I have never rooted yet. I was considering it just to test how it was. So that means I have not been able to wipe the Dalvik. Does that get wiped when I Odin? I did indeed tried Odining the DOG1 a few times and still the same results. I am thinking it was hardware but wasn't sure. Do you have a T3? Any problems at all on stock?
It seems its an issue to try to obtain another T3 as now they still have some old regular N910T refurbs back in stock. Plus the IMEI still just populate with "Note 4" and do not differentiate between the two.
Thanks for the reply.

I also got a N910T3 as warranty replacement and had the same issues on non-rooted phone.
Rooted the phone installed custom rom and all those issues gone. Your best best is to root the phone and install custom 5.1.1. ROM

pvsgh said:
I also got a N910T3 as warranty replacement and had the same issues on non-rooted phone.
Rooted the phone installed custom rom and all those issues gone. Your best best is to root the phone and install custom 5.1.1. ROM
Click to expand...
Click to collapse
Ya, I just did that. Flashed Twrp, Rooted, and then Wiped the dalvik and cache.. Seems stock now is running better. Strange.
What rom and kernel are you on? Sucks that this is so different then the N910T.

Anyone else?
Sent from my SM-N910T3 using Tapatalk 2

I have the T3 I'm honestly not experiencing those problems at all. When it was stock. Stock rooted nor cm remix. To me the t3 seems to run smoother than any other the 910t I've had
Sent from my SM-N910T using Tapatalk

I kinda wonder of one of the partitions are messed up. Anyone here familiar with using Odin to erase the band and load the FW back? It could be hardware I guess but if it's just some software glitch I hope I can just figure it out. It's odd that some people experience the same problems and some dont.
Sent from my SM-N910T3 using Tapatalk 2