I've been on ICS with my Epic 4G Touch (CREDO, but Sprint's network) for a while and I really love it however the last 2 ROMs I've used have had this problem where my phone restarts itself seemingly at random. I remember seeing somewhere that it could be because of having the 4G on too long and the phone restarts itself? This seems silly to me and I feel like it's not the problem. The most recent ICS rom I have (Blu Kuban) disables 4G at startup and I feel like this might be why. However after searching through this forum and the threads of the ROMs I had the issue with I can't seem to find any information that anyone else gets this. The CM9 Alpha 2 and 3 I tried didn't have this issue, but when I switched to Mijjah74's MIJJz BLEND FE10 and RUJELUS22's The Blu Kuban FE10 (I also tried updating to FE16 kernel and modem same problem) I get this restarting issue where my phone will be tethered to my laptop and then not. I have an updated Gingerbread rom I've been considering testing to ensure it's not my hardware however I figure I'd ask on here and if anyone had experienced similar problems and if there is any kind of fix other than turning off 4G. Thanks!!
Hot reboots have been a nagging thing ever since I started messing with custom roms. There are so many variables its not even funny. Just make sure that when you are testing its always from a clean start. Bad data, kernel issue, rogue apps - I have seen it all cause hot reboots.
You seem to have the right idea keep trouble shooting but remember it should always be from a clean install. Also you should try and fix permissions as well since that has helped me in the past.
playya said:
Hot reboots have been a nagging thing ever since I started messing with custom roms. There are so many variables its not even funny. Just make sure that when you are testing its always from a clean start. Bad data, kernel issue, rogue apps - I have seen it all cause hot reboots.
You seem to have the right idea keep trouble shooting but remember it should always be from a clean install. Also you should try and fix permissions as well since that has helped me in the past.
Click to expand...
Click to collapse
Yeah always from a clean start (EL29 stock rooted CWM5 ----> ICS rom) I saw all those warnings, if the ROM gets another larger update I'll keep clean installing. Glad I'm on the right path. When you say fix permissions, what exactly where are you talking about? Could it be a program that's accessing part of the phone while it's locked and in the confusion my phone thinks the best course of action is a total restart? Such a silly pocket computer teehee.
watchout5 said:
Yeah always from a clean start (EL29 stock rooted CWM5 ----> ICS rom) I saw all those warnings, if the ROM gets another larger update I'll keep clean installing. Glad I'm on the right path. When you say fix permissions, what exactly where are you talking about? Could it be a program that's accessing part of the phone while it's locked and in the confusion my phone thinks the best course of action is a total restart? Such a silly pocket computer teehee.
Click to expand...
Click to collapse
Go to the market and download an app called fix permission. It fixes any mismatches with your system to keep everything running smooth. I usually do it through a custom recovery on GB. Quite helpful
All right, I've googled the crap out of this topic and have found many threads on many sites where people think they are STUCK at this screen, and have to pull the battery. For some people that may be the case, but in my case, it is a delay of about 5 minutes. And it is driving me crazy that nobody finds this as troublesome as I do.
I have the Verizon GNex, and I just recently unrooted and got back to stock in order to get the official Jelly Bean OTA update from Verizon. Once I got it, I rooted using CWM and SuperUser. Everything's great except that almost every time I boot my phone it gets stuck on the Google Logo for about 5 minutes before resuming boot. I've used CWM to clear cache, clear dalvik cache, fix permissions, etc. Not fixed, still does it (not EVERY time, but more often than not).
For the love of Homer Simpson, WHAT IS THE SOLUTION TO THIS PROBLEM?!? It is clearly a Jelly Bean issue, as every JB Rom I've tried has the issue, where ICS never did. I turn my phone off at night, and can't deal with this almost every morning. Can anybody else with Verizon's stock JB just comment and let me know if you also have this problem, and if you know how to make it stop PLEASE SHARE! Thank you in advance!
I would say try flashing the new bootloader but since you took the OTA I would think it came with it. It might be worth a shot anyway.
It is a common problem with JB. Mine takes a minute or two even with the new bootloader.
Allons-y
The ota did indeed come with the new bootloader. So I don't know what else to do. Extremely annoyed about it, especially since there is no REASON I've heard that explains why it happens. Thanks for posting though, good to know I'm not the only one.
I wanted to get the opinion of the devs who make all of the ROMS for this device. Below is my experience and my theory:
I have had the phantom soft key issue on every incarnation of the GSII software. I un rooted and went all the way back to the beginning. I used each rom version till the issue occurred, then I let the phone update to the next ROM version and repeated the process. Every single un rooted update had the same issue and then every single Rooted ROM all ROMS for the ET4G were tried and the issue occurred.
Strange part is it came out of nowhere. I have had and have been flashing for an entire year without issue and one day all of a sudden... BOOM. I don't think it is as simple as the signal issue. I think it has to do with flashing as well. Unless this is happening to someone who has never rooted their device, I think something in the roms we flash trigger the issue which is related to signal.
Has anyone known anyone who has never rooted their device and has had the issue? By the way, the store gave me a brand new factory OEM screen and the issue still occurs.
Gorguts said:
I wanted to get the opinion of the devs who make all of the ROMS for this device. Below is my experience and my theory:
I have had the phantom soft key issue on every incarnation of the GSII software. I un rooted and went all the way back to the beginning. I used each rom version till the issue occurred, then I let the phone update to the next ROM version and repeated the process. Every single un rooted update had the same issue and then every single Rooted ROM all ROMS for the ET4G were tried and the issue occurred.
Strange part is it came out of nowhere. I have had and have been flashing for an entire year without issue and one day all of a sudden... BOOM. I don't think it is as simple as the signal issue. I think it has to do with flashing as well. Unless this is happening to someone who has never rooted their device, I think something in the roms we flash trigger the issue which is related to signal.
Has anyone known anyone who has never rooted their device and has had the issue? By the way, the store gave me a brand new factory OEM screen and the issue still occurs.
Click to expand...
Click to collapse
I had the issue straight out of the box when we still had gingerbread. I hardly get it anymore besides on occasion
Sent from my SPH-D710 using Tapatalk 2
Elw00d said:
I had the issue straight out of the box when we still had gingerbread. I hardly get it anymore besides on occasion
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Right outta the box before rooting it?
I personally think its hardware related with, either over time the screen moving and the heating up of the device causing phantom button presses... this only recently started happening to me and after i wipe screen with cloth while its turned off it goes away. for awhile... idk haha
I disabled the hardware capacitive keys and use the software on screen buttons. Problem solved
Sent from my SPH-D710 using xda premium
As said above, I had this issue on Gingerbread..out the box, no root. It'd press menu by itself lol, always gave me WTF moments. I'm on ICS now, and no problems at all.
Crazy, ok. Well I got the answers I was looking for. Thank you everyone for your info. Note 2, here I come.
Yup, happens here too. Menu key goes nuts when charging.
FYI just cause you want to get a developers opinion does not give you permission to ask a question in the development section.
Papa Smurf151 said:
FYI just cause you want to get a developers opinion does not give you permission to ask a question in the development section.
Click to expand...
Click to collapse
I will begin chastising myself at once....
Gorguts said:
I will begin chastising myself at once....
Click to expand...
Click to collapse
Picture please ^^^^^^^^^
I have this issue on out of box uprooted and other sget4g were okay for some time after rooting and flashing custom made roms... They too fell prey to the mysterious phantom presses... Ahhh the horror.
My fix was....... To
I have had this issue several months and now have a good solution. Use this info posted by elijahbrown on Page 464 in PA thread I believe. http://forum.xda-developers.com/showthread.php?p=34125394
" Disables menu key!
Ooookay..
Go to system/usr/keylayout
Select sec_touchkey. kl and edit as text. You'll see key 217 is search. Delete that line of code or put a "#" in front of it to turn it into a comment. Save the file.
Re boot and let meet know.
Just curious as to why you want to do this so bad? "
# comment out menu and search keys. Save file and Set permissions.
Then head over to the play store and get Button Savior. I paid for the advanced features and am very happy. Have to keep the phone until may 2013, sprint claims liquid damage so no replacement.
Button Savior on screen hidden pop up menu buttons works great and no more phantom presses menu or search pop ups ever again! 
For the longest time I was on stock rooted EK02. I recently took the plunge and wiped all and installed CM10, which I love. The only problem I've had is that *all* sound suddenly decides to just go away whenever it wants to (ring/notif tones, touch clicks, app sounds, everything except in-call audio). It might last 5 minutes, or it might last an hour, but it always comes back on its own, and a reboot does not fix it. I can't seem to trigger the problem with a certain app or a certain action, but for example, I will be sitting here playing Angry Birds Star Wars, and the sound will just drop out completely. A few levels later, it comes back on its own. I put the phone down, go do something else, and the entire phone has muted itself again. Frustrating...
I'm on CM10 beta2 nightly 20121108
Kernel version says 3.0.15-CM-g8e7ed92, which seems appropriate since it references CM and this is the first CM I've ever had on the phone. Should I try other kernels though? AFAIK, no one else has mentioned this particular audio problem in the CM10 discussion thread. At least I don't think this is related to the "low volume in some apps" issue.
HOWEVER, something interesting, the baseband/radio version says EK02. I guess I should update that to get better comm, but it couldn't be causing an intermittent muting issue, right? I guess I assumed incorrectly that a ROM installed after a wipe would have to include its own modem. Argh.
This is frustrating, as I said. Thanks for any help.
Wow. 5 days and no replies. Can't someone at least tell me what you think? I've never understood why I can ask a legitimate, polite, and descriptive question after searching the forums as much as possible, and it gets ignored, while someone else can post something completely redundant that barely forms a coherent sentence, yet it sparks a 10 page discussion... frustrating.
I am not exceedingly familiar with cm10 but I would bet it is not the modem causing that issue. I would be inclined to think you have intentionally and / or accidentally changed the "quiet hours" or setup some form of silent profile. Otherwise it was perhaps a bad flash, you did not wipe CLEANLY (IE. calkulins format all or odin a full wipe/restore rim first) or maybe not install with what many revs believe to be a CWM safe kernel???
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
also do you have anything (pc or stereo) connected to Bluetooth with the phone nearby?
trmitche2 said:
Wow. 5 days and no replies. Can't someone at least tell me what you think? I've never understood why I can ask a legitimate, polite, and descriptive question after searching the forums as much as possible, and it gets ignored, while someone else can post something completely redundant that barely forms a coherent sentence, yet it sparks a 10 page discussion... frustrating.
Click to expand...
Click to collapse
Nobody knows the answer to your questions. This is not a common problem and as mentioned above the modem has nothing to do with it. My only suggestion would be to flash a stock release one click, not a leak, and go from there.
Agree with above and mainly because I borked my build... it was perfect and then I tried a gps fix flash. Can confirm now that wipe in CWM and calks format all does not do crap for aosp, jb, or the like. So long story short, yeah you gotta one click or my guess is best served to clean slate with a stock ROM and in consequently factory wipe and just stay there.....
Wow thanks for the replies guys! I was really getting discouraged there for a bit.
I don't think it's a quiet hours setting, because all sound is cutting in and out *every 5-10 minutes*,
I will use Calk's wipe and start from scratch as suggested.
Although unrelated, surely EK02 is not a recommended modem for CM10, right? I guess I made a naive assumption that a full wipe followed by CM10 install would replace my old modem. I'm just curious what kind of problems might be caused by using such an old modem, even though I know sound is not one of them.
Can anyone recommend a modem for this ROM from personal experience? I understand from the main beta2 thread that the FK modems break 3G...
Just flash a one click, it will wipe everything and install a new modem. I'm using fi27 modem with codename rom, works fine. My current install method is run one click update prl and profile and get gps lock then do the install process of the rom.
someguyatx said:
Just flash a one click, it will wipe everything and install a new modem. I'm using fi27 modem with codename rom, works fine. My current install method is run one click update prl and profile and get gps lock then do the install process of the rom.
Click to expand...
Click to collapse
Yes. Do this. Then. Format all is still a good idea if you choose to revert to a GB ROM like el29 and progress.
UPDATE: I fixed this.... accidentally. What fixed it is hard for me to believe or accept, but Iv'e confirmed it by being able to reproduce it. The problem was being caused by the FRIKKIN' FACEBOOK APP. :/ I uninstalled the FB app for a totally unrelated reason: battery drain pointed out in another post. I realized the next day that the sound had not cut out once since then, I re-installed FB, and the problem returned quite predictably: all sounds started cutting in and out every few minutes. Uninstalled FB again, and sound has been fine ever since. My best guess is that the sound was cutting out/in each time a background sync of FB occurred. So now my sound is perfect and my battery life is much better to boot. I never used that damn app anyway.
Unrelated, but for what it's worth, I never installed a new modem as discussed above. Still running EK02 with CM10 nightly from 11/28. Have no problems to speak of. I didn't leave it on purpose, (noob mistake, thought CM10 installation would replace it), but I don't see any reason to change it as long as everything seems perfect, unless anyone can tell me what types of problems it could cause. Any further thoughts welcomed, but thanks again to you guys who already gave me advice.
trmitche2 said:
UPDATE: I fixed this.... accidentally. What fixed it is hard for me to believe or accept, but Iv'e confirmed it by being able to reproduce it. The problem was being caused by the FRIKKIN' FACEBOOK APP. :/ I uninstalled the FB app for a totally unrelated reason: battery drain pointed out in another post. I realized the next day that the sound had not cut out once since then, I re-installed FB, and the problem returned quite predictably: all sounds started cutting in and out every few minutes. Uninstalled FB again, and sound has been fine ever since. My best guess is that the sound was cutting out/in each time a background sync of FB occurred. So now my sound is perfect and my battery life is much better to boot. I never used that damn app anyway.
Unrelated, but for what it's worth, I never installed a new modem as discussed above. Still running EK02 with CM10 nightly from 11/28. Have no problems to speak of. I didn't leave it on purpose, (noob mistake, thought CM10 installation would replace it), but I don't see any reason to change it as long as everything seems perfect, unless anyone can tell me what types of problems it could cause. Any further thoughts welcomed, but thanks again to you guys who already gave me advice.
Click to expand...
Click to collapse
None, modems are interchangeable between builds with the exception of the fk-- and newer modems, they only work with Touchwiz based JB roms. If your modem is performing well speed and call quality wise then there's no need to change. However you could always test other modems to see if you get any improvement in your location. If you choose to change modems you should be on a touchwiz rom so you can update prl and profile after the modem flash. Modems are a YMMV item each one interacts with different devices and locations differently so to find the best modem for you you just need to flash and test them out if you so choose
Sent from my hand to your eyes!
Samsung: Intercept, Galaxy S2, Galaxy S3, Galaxy Note 2, Nexus10
HTC: EVO4g, EVO 3d
LG: Optimus G, Nexus 4
Asus: Nexus7
Motorola: Photon
Amazon: Kindle Fire, Kindle Fire HD
We are legion, for we are many!
Thanks KoN! Extremely helpful post, as always. All other replies in this thread have been thanked as well. I learned a lot.
Still wish I knew how FB could make my sound cut in and out every few minutes, but if no one else has seen that issue, it must've been a quirk, so I imagine I'll never know. Moving on....
I wanted to ask someone with expertise regarding my d2tmo.. I am experienced with flashing roms and anything with rooting and trying roms. I wanted to ask you about a camera issue I am having. The problem is when my camera is using flash to snap pics and also sometimes when making videos without flash my system crashes and forces reboot. Before seemed like was only in aosp roms and i was thinking it could be just that cm10 bug with the cameras, but then I noticed it was happening in Tw roms and so i odin flashed stock firmware and the problem still persists. I asked someone before and they told me it for sure was a software issue and not hardware, but since I was on stock seems like could be hardware. Have you heard if this happening before? could you offer me some kind of insight for this? I am sending the phone back to tmo and getting a warranty replacement for another issue ( and yeah i triangle awayed lol) , but i was wondering if this would happen still with the new phone if i decided to flash some custom roms.. Is there a chance that samsung could of improved components or did anything different since I bought my s3 last october? I am sorry for the long story, but I really can't find help anywhere else and I really use my camera alot for work.
thanks in advance.
- J.RAD