My search-fu is dreadful, so if there IS a thread about this and I just didn't see it, please link me and I'll begin anew.
Within the past couple of weeks, any CM based ROM has rebooted, primarily while listening to music with my bluetooth headset (but sometimes bluetooth is not on at all). I didn't see any reports from other users with this trouble, so I wiped my phone's internal storage completely and installed the latest (at the time 4/28) nightly for CM 10.1. Same issue. Weird, I updated from MB1 to MD4 using a modem update from freeza and service got better and for 24 hours -- blissful stable use of phone.
On my commute to work today, BAM reboot several times. I managed to grab a logcat this time using a terminal app. The log cuts off ~1 1/2 minutes before the lockup and there are no F/ tagged messages and all the E/ messages appear to be accelerometer related.
The strange part of this is that TouchWiz ROMs do not suffer the same trouble. I can abuse the battery on Stock-based ROMs with no trouble but any CM based ROM (I tried AOKP and CM nightlies. I even tried CM 10 stable!) reboots in what appears to be random. No basis on Wi-fi status, no basis on network status. It reboots more reliably when using Bluetooth.
My question(s) is (are): What am I missing? I have TEP from Sprint, so should I just throw my phone against a wall and grab a refurb that might work better?
Again: If I missed a thread about this, please just link me Logcat attached because HAHA I'M A NOOB
I don't know anything but I'm pretty sure it's a kernel related issue. Have you tried the AOSP roms with a different kernel than what they come with? It's not your phone so throwing it against the wall won't solve anything.
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
I don't know anything but I'm pretty sure it's a kernel related issue. Have you tried the AOSP roms with a different kernel than what they come with? It's not your phone so throwing it against the wall won't solve anything.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
While using AOKP, I was using the "underwear" kernel that it came with, whereas with CM I used the default kernel with those. Ktoonz kernel, for months, has caused a squeal in audio no matter what version I used. There were a lot of suggestions about tweaking Bluetooth Mhz to get rid of the issue that never worked for me. Agat seems okay, but I've only seen it working in TouchWiz ROMs.
What would be a good "tester" kernel I could try?
I only suggested throwing the phone against the wall because it would cost me about 150 to get another from Sprint.
EDIT: I'm going to give Ktoonz another try right now. It brought me so much battery joy in its early days
EDIT2: Ktoonz kernal -- locked up before I even got my apps installed. Odd, instead of rebooting, it just hung until I pulled the battery.
This stuff has been talked about in the CM thread. And you have to remember a nightly in not stable.
Sent from my Nexus 7 using Tapatalk 2
GiantJay said:
This stuff has been talked about in the CM thread. And you have to remember a nightly in not stable.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Very true, but I get the same problem using CM 10 stable as well. I'm going to hunt through the nightly thread again, I was only looking at posts about the last week or so of nightlies. It alarmed me that half the users were cheering about "almost stable" and I couldn't get a hour of normal use.
Checking again for solutions, thanks for the tip.
I'd like to thank the posters who responded patiently and to the posters that refrained from mocking me I have resolved my own problem by following basic forum/flashing rules.
I want to put important steps here in case someone searches and finds my stupid thread. (NOTE THESE ARE ELSE WHERE AND I JUST DIDN'T FIND THEM):
-Make sure you have a third party cable (I like blackberry's older/thicker USB cables)
-Don't just search the forum for your exact problem, search the thread the ROM is in!
-A good ROM will provide the md5 of their download. Google a basic md5 checker, put in your downloaded file and check the md5. If it is not an exact match, DO NOT FLASH.
-When in doubt, reflash
-Double check that you are flashing the correct items (check Linux version, check ROM version, check Kernel version, check phone type)
-On nightly ANYTHING, do not expect to get the same results other users are getting. The stars may not align, a witch may have put a curse on you, a meteor was passing by when you downloaded it etc.
Thank you/sorry/thank you.
Related
I posted this in NilsP's Business GingerSense thread, but don't think it's a ROM issue, more of a Google Talk issue. Running the 2.0 version of that ROM.
The issue is where Google Talk shows all your contacts as Offline after a period of say five to ten minutes, maybe shorter than that. I'll be messaging someone, and after a few minutes when they haven't responded, I'll wake my phone and open GT. All the contacts are Offline. A simple sign out/sign in fixes that, and the usual contacts show Online or Away.I've noticed this all week, so I'm thinking it's a GT issue, but I've never had it happen before.
Don't want to have to sign out/in every time I want to use it. Cleared GT cache, fix permissions, multiple wipes of data/system/cache/boot/dalvik/user data before each ROM install, and haven't had this before now.
Thoughts?
EDIT: After playing, it happens when switching from 3G to WiFi and vice versa, so maybe it is a ROM thing...?
i'm having the same issue. noticed after my gingerbread OTA update from verizon.
Droid 2.
It seems to happen a few minutes after logging on.
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
carapauzinho said:
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
Click to expand...
Click to collapse
Me too. Anyone was able to do something?
Well I've since moved on, and haven't noticed it on other ROMs. Right now I just tested toggling Wifi on and off, and the contacts would appear offline, then come online once 3g or wifi connected.
I'm thinking in my case, it was that version of the ROM I was running at the time.
Sent from my ADR6300 using xda premium
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
dragon droid said:
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
Click to expand...
Click to collapse
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
RMarkwald said:
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
Click to expand...
Click to collapse
Hi,
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Thank you both for your input.
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
RMarkwald said:
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
Click to expand...
Click to collapse
Yes, we are.
The thing is that it seems to me that it happened only after XXVJR (meaning it happened to me in XXJVS and XXJVT, and now we're already at XWJVU, all these being Samsungs "leaks"), and I have a friend with XXJVS that works just fine.
I even tried flashing a stock ROM, to see if it happens again. Testing that one now.
Thanks for your advice.
Same problem here.
Although I have not tried it with stock non rooted phone...
I'm having the same problem on a stock rooted Motorola Photon. Very annoying to have to sign out and back in to see who's online. Hopefully someone comes to the rescue with a solution.
Hi,
The only thing I could find is that the problem is, indeed, NOT in the custom ROM's. It's google's problem.
The only way I could get by was with an alternative IM. And, for me, the better is Trillian (taking battery, performance, etc. in consideration.)
I updated my software which included an updated gtalk with video..so far so good.
crs77 said:
I updated my software which included an updated gtalk with video..so far so good.
Click to expand...
Click to collapse
Mine got better with one of those. But it ended up all the same.
DarkSorcerer said:
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Click to expand...
Click to collapse
I am having this issue too. I have had it since the beginning, when I had the preinstalled stock rom, I had it with all the other stock roms I flashed, I had it with all the versions of Talk I tried (those which supported video calls), I had it with all the other customs roms I tried (Simplicity, CyanogenMod, MIUI). I never used any task killer. For these reasons I am strongly convinced this is a Google Talk related bug.
Some more details about the problem:
after a few minutes after having logged in, contacts are shown offline on Android while they appear online on the desktop client;
despite their offline status I still receive messages from them and as soon as I answer only that contact appears online while the others keep being shown offline;
signing out and back in fixes the problem temporarily, but it happens again after a few minutes.
What surprises me is how come very few people seem noticing it or being annoyed by it? How come a huge bug like this has been out for so long and Google hasn't fixed it yet? All the posts I have seen reporting this problem on Google Talk Help Forum have been ignored.
Exact same problem with my I9100, Gtalk with video. Very annoying.
I have the SGS i777 (Samsung Galaxy S2 on AT&T), and just recently (since late February) started experiencing the same issue. When on WiFi, it doesn't appear to be an issue, only when not on WiFi, particularly if I have just recently turned off WiFi.
Other "friends" show me as "Away", so I am connected.
This is bone stock 2.3.6 Samsung official ROM (never rooted UCKK6).
I tried crawling a bit through the logs (aLogCat output), filtering for "[Tt]alk", but I can't make enough heads or tails about where the failure might be (not being an actual developer), other than lots of messages get created. I'll see if I can't figure something more useful out about it.
A hard reset with no apps installed has the same problem. Though I've noticed that the problem appears to get "worse" as the phone "ages" - namely, hard reset fixes the problem, but it slowly (over days) gets worse and worse.
Update: I have not noticed this issue at all since getting the official Samsung/AT&T ICS build (IML74K.CLE5).
Google Talk failing for toooo loooong
Hi there,
I'm a cyanogen 7.1 (stable) android user, and I just want to join myself to every other person who's affected by this issue.
I'll leave here some links to other places discussion exactly the same issue:
code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=gtalk%20offline&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=24242
You may check this thread: groups.google.com/a/googleproductforums.com/forum/#!topic/chat/6m0YqHoiIDg
Until now, I wasn't also able to find any clue to what the cause may be.
Starting to suspect that's something on Google's side, not android/rom itself.
Maybe something to do with our google accounts' settings?
Are there any news about this issue? I'm having the same problem.
Hey guys,
I've clicked around a bit but can't seem to find anyone with the same issue, and I went through about 40 pages on Calkulin's ROM but I really don't want to go through all 200 and some if somebody here can provide a solution.
I've used his ROMs for the past year, really fantastic, no complaints at all. I flashed his beta ICS build a few months ago and it worked well with the exception that it would randomly reboot for no apparent reason. I could be in the middle of a text message or it could be sitting on my desk and all of a sudden, reboot. I went back to his old ROM and decided to put off ICS for a few months to work out the bugs. Today I put his newest ICS ROM up and once again, random reboots. It doesn't seem that others are having the same problem so I'm not sure what to make of it. And for the sake of putting it out there, it's always a clean install - Format All, flash modem and ROM.
Anybody have any ideas? Suggestions? Any help is seriously appreciated.
Thanks guys.
Ive heard of someone else having this issue before have you tried a fresh install with a new download of EL29 or EL26? When i have had issuez in the past that could be the culprit try a new download also you could try one of the new kernals posted that may help as well.
Sent from my SPH-D710 using XDA
Are you using 4g?? This is a known issue with leaving 4g enabled.
Sent from my SPH-D710 using XDA
It is a known issue that if the hacked Hotspot is installed and you are running on 4G that you will experience random reboots. Mijjah74 has implemented a fix for it in his ROMs and it is beginning to go out among the other developers as well.
Until your developer implements the fix the cure is to not use 4G.
Awesome, thanks a ton. What a goofy bug. Yes I frequently use 4g, hourly even, and although I rarely use the hot spot, it is installed. I wonder if un installing it would fix the issue.
Thanks again.
Any idea if using am older modem would fix it?
iJoshh said:
Awesome, thanks a ton. What a goofy bug. Yes I frequently use 4g, hourly even, and although I rarely use the hot spot, it is installed. I wonder if un installing it would fix the issue.
Thanks again.
Any idea if using am older modem would fix it?
Click to expand...
Click to collapse
No, reinstalling won't help. I was testing 4g for this and (for me at least) it would reboot at about exactly the 1 hr mark if 4g is running constantly. Pretty strange but it did it several times in a row that way. I think someone said that they have the timing down pretty well and I can't recall exactly what the recommendation was, turn 4g off and back on right before it's going to reboot (you should time yours to see when it does it). Something like that.
Addendum: FYI, I'm running stock EL29 modem. A different modem won't change the 4g reboot issue either, sorry.
I had random reboots on every ROM. I went all the way back to stock unrooted, and started back over. Haven't has any issues since.
Sent from my SPH-D710 using xda premium
Hi,
I'm running the latest CM10 (Linaro). My Wi-Fi connection constantly drops for a few seconds then reconnects. It was doing this on CM9 as well. Not sure about what it did when stock (wasn't stock for long).
Is this an issue with the Kindle, or with the rom(s)? Is there a hardware update? Any help would be appreciated.
Thanks!
mike
Seems to be a common gremlin with custom ROMs. There are a few that don't drop, or as often. Gotta test em all.
gtFlue said:
Seems to be a common gremlin with custom ROMs. There are a few that don't drop, or as often. Gotta test em all.
Click to expand...
Click to collapse
Thanks. I just did a full wipe and installed [ROM][10/10/2012] Unofficial AOKP Jellybean Build 4.
Same problem. I suspect if I went back to a stock rom, the wifi issue would disappear. But no way... this Jellybean build is fricken awesome.
Might a different kernel help? Could it be that I just have a lemon?
-mike
resarfekim said:
Thanks. I just did a full wipe and installed [ROM][10/10/2012] Unofficial AOKP Jellybean Build 4.
Same problem. I suspect if I went back to a stock rom, the wifi issue would disappear. But no way... this Jellybean build is fricken awesome.
Might a different kernel help? Could it be that I just have a lemon?
-mike
Click to expand...
Click to collapse
This sounds like a hardware problem. While there have been some wifi issues in the past, these have been resolved. Dropping constantly is hardware. Reload stock and exchange it with Amazon.
Sent from my Amazon Kindle Fire using xda app-developers app
Ixthusdan said:
This sounds like a hardware problem. While there have been some wifi issues in the past, these have been resolved. Dropping constantly is hardware. Reload stock and exchange it with Amazon.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I installed the stock rom (MoDaCo Custom ROM). The wi-fi seems to be working great.
Maybe I'll just leave it stock. It's not so bad once I put Go Launcher on!
- Update - I did a thorough wipe of everything, installed the latest CM10 (SEMI-NIGHTLY] CM10 + 4AI.1.7 KERNEL [STABLE). WiFi seems to be working properly now.
Thanks,
Mike
Mine is/was doing this on CM10 SGT7, but I think it's application specific. Some apps kick the wifi off constantly, like every 20 seconds, while it can stay on perfectly fine on others. If I shut down all apps I seem to stay online just fine. I'll keep experimenting and see what is doing it. I'm also wondering if it's a combination of the KF and my DIR-655 router, which doesn't like some devices anyway and maybe just has a conflict with this one for some reason.
Anyway I'm going to keep testing the SGT7 before wiping and switching. I'm also going to wipe and reinstall SGT7 because if it was really a ROM-specific problem it would probably be identified as a problem for a lot more people using those ROMs and be listed as such.
I'm guessing it's a problem that some versions of the KF have, but is also due to a few specific apps and how they access data. I just hope it's not Chrome that's doing it.
WiFi Drops
I'm running straight up Hashcode's ROM 4.1.2 / Kern 3.0.31+ (Oct 10 2012). It's been an ongoing issue. Not sure how someone can say "It's hardware related" when stock amazon rom doesn't have this issue. I've been able to recreate it almost 100% using a torrent client (aTorrent, etc) soon as bandwidth hits about 300kb range, the wifi turns to an off setting. Seems if you don't throttle the connection somewhat, the system drops the network layer completely as a out of control app?
I'm going to try a wipe/update and see what happens. It's very annoying trying to get sypebeta installed when its downloader just goes full balls to the wall and dumps at nearly 90% every time
Intro:
I have the Samsung Epic 4G. Great phone, running into problems. I originally started out rooted and modded with the CyanogenMOD 10 Nightly. Everything was going great and I love the mod but I started getting MMS problems where I couldn't see the pictures being sent or the ones I was sending. There was an easily located temporary fix found online to delete the telephony file and restart the phone. No biggie I can deal. Then bigger problems started arising as I was no longer getting all of my text messages. Sometimes none. I contacted Sprint and they ran through the whole ordeal of giving me some codes to input which of corse wouldn't work on the MOD and I couldn't update the profile so they said they'd check the tower where I was located and turned out nothing was wrong with it.... My wife and I are having a baby so being unable to contact her without calling constantly is a no go.
Main:
I flashed the stock for the SPH-D700 and all of my problems were fixed. This is a no bueno for me because it's full of bloatware and the phone without modification dies before my workday is out practically, even without heavy usage (and forget heavy usage because that was like shooting the battery into the sun and who the hell wants a smart phone that works for only like an hour?). After looking around I located the stock FC09 Deodexed MTD which comes with ShadowKernel (aweeeesome!) and flashed that. Didn't have any issues and all my texts were coming and going through. This was tested at work using a series of seperate sequential alphanumeric texts and all was good. I installed the usual suspects, Voltage Control, Juice Defender, SD Maid, ES Explorer, the WiFi hack, etc... Not being a fan of the stock messaging app I also downloaded the standard Chomp SMS app (which is def a step up and ad free) as well. I knocked the voltages down reasonably and tested them using Voltage control to do that and control the CPU (no overclocking). I got rid of all of the apps that the XDA Wiki said I could and backed everything up. All was well until yesterday. I charged the phone the previous night and went to work doing the normal kinda day act. I sent my wife some messages but figured she was busy when she didn't respond. Hours later I realized that she probably had responded because she never goes that long without doing so. I asked a few friends to text me and I texted myself as well and now I wasn't getting ANY texts. I did the phone dance with Sprint to no avail and they told me to take the phone to my local store. This would be the second Epic 4G that they would be replacing. The first one had this problem too but fixed itself when I flashed the stock rom. Then there was some water damage which thankfully insurance covered and I got my replacement earlier this week when I worked on modifying my phone to something I found acceptable. I think this rules out a hardware issue. On a whim I restored to a backup that I had made after getting my phone neat and tidy and some odd things happened. I started getting texts, but not the ones that I had already missed, and I was getting some later ones first before getting the first ones sent, I.E. i'd send 1, 2, 3, 4, 5 and get back 5, 2, 3, 4, 1 but they would arrange themselves in the correct order onces they came. It was also taking them forever to come in as I would send them and have to wait five to ten minutes for them to come.
Conclusion:
Tired, frustrated, and somewhat perturbed I reflashed the stock rom and the problem again has fixed itself. My question is has anyone else run into this? I've looked everywhere and can't find a similar case. Am I just not seeing something that's directly in front of me? Ideally i'd really like to put Cyanogen back on but I can't afford not to be in contact with my pregnant wife. I'd also reaaaally like the WiFi cabailities that were advertised with the phone but then neglected to mention that I would have to pay 30$ extra a month for. Is this a similar issue to the MMS telephony file issue that can be resolved with perhaps a nightly deletion of a file? Is there anything I can do NOT to be on the stock rom with the worthless battery life and bloatware that chokes?????
Sincerely,
Ignored Thoughts
ignoredthoughts said:
Intro:
I have the Samsung Epic 4G. Great phone, running into problems. I originally started out rooted and modded with the CyanogenMOD 10 Nightly. Everything was going great and I love the mod but I started getting MMS problems where I couldn't see the pictures being sent or the ones I was sending. There was an easily located temporary fix found online to delete the telephony file and restart the phone. No biggie I can deal. Then bigger problems started arising as I was no longer getting all of my text messages. Sometimes none. I contacted Sprint and they ran through the whole ordeal of giving me some codes to input which of corse wouldn't work on the MOD and I couldn't update the profile so they said they'd check the tower where I was located and turned out nothing was wrong with it.... My wife and I are having a baby so being unable to contact her without calling constantly is a no go.
Main:
I flashed the stock for the SPH-D700 and all of my problems were fixed. This is a no bueno for me because it's full of bloatware and the phone without modification dies before my workday is out practically, even without heavy usage (and forget heavy usage because that was like shooting the battery into the sun and who the hell wants a smart phone that works for only like an hour?). After looking around I located the stock FC09 Deodexed MTD which comes with ShadowKernel (aweeeesome!) and flashed that. Didn't have any issues and all my texts were coming and going through. This was tested at work using a series of seperate sequential alphanumeric texts and all was good. I installed the usual suspects, Voltage Control, Juice Defender, SD Maid, ES Explorer, the WiFi hack, etc... Not being a fan of the stock messaging app I also downloaded the standard Chomp SMS app (which is def a step up and ad free) as well. I knocked the voltages down reasonably and tested them using Voltage control to do that and control the CPU (no overclocking). I got rid of all of the apps that the XDA Wiki said I could and backed everything up. All was well until yesterday. I charged the phone the previous night and went to work doing the normal kinda day act. I sent my wife some messages but figured she was busy when she didn't respond. Hours later I realized that she probably had responded because she never goes that long without doing so. I asked a few friends to text me and I texted myself as well and now I wasn't getting ANY texts. I did the phone dance with Sprint to no avail and they told me to take the phone to my local store. This would be the second Epic 4G that they would be replacing. The first one had this problem too but fixed itself when I flashed the stock rom. Then there was some water damage which thankfully insurance covered and I got my replacement earlier this week when I worked on modifying my phone to something I found acceptable. I think this rules out a hardware issue. On a whim I restored to a backup that I had made after getting my phone neat and tidy and some odd things happened. I started getting texts, but not the ones that I had already missed, and I was getting some later ones first before getting the first ones sent, I.E. i'd send 1, 2, 3, 4, 5 and get back 5, 2, 3, 4, 1 but they would arrange themselves in the correct order onces they came. It was also taking them forever to come in as I would send them and have to wait five to ten minutes for them to come.
Conclusion:
Tired, frustrated, and somewhat perturbed I reflashed the stock rom and the problem again has fixed itself. My question is has anyone else run into this? I've looked everywhere and can't find a similar case. Am I just not seeing something that's directly in front of me? Ideally i'd really like to put Cyanogen back on but I can't afford not to be in contact with my pregnant wife. I'd also reaaaally like the WiFi cabailities that were advertised with the phone but then neglected to mention that I would have to pay 30$ extra a month for. Is this a similar issue to the MMS telephony file issue that can be resolved with perhaps a nightly deletion of a file? Is there anything I can do NOT to be on the stock rom with the worthless battery life and bloatware that chokes?????
Sincerely,
Ignored Thoughts
Click to expand...
Click to collapse
So that's a big wall-o-text. I didn't read it, and just skipped down to your conclusion. You can flash another CM based 4.2.2 rom to test SMS/MMS. It all works fine for me on Slim. If you want TouchWiz, then flash The People's ROM. This rom has no bloat and better battery life than stock. All of these roms have the Wifi access point built in.
nikon120 said:
So that's a big wall-o-text. I didn't read it, and just skipped down to your conclusion. You can flash another CM based 4.2.2 rom to test SMS/MMS. It all works fine for me on Slim. If you want TouchWiz, then flash The People's ROM. This rom has no bloat and better battery life than stock. All of these roms have the Wifi access point built in.
Click to expand...
Click to collapse
I'm dloading the latest CM 10.1 RC4 to give it another shot. I'm not confident that this won't happen again either immediately or within a few days. Thank you for your input.
IT
I guess my concern is that this happened across both roms, FC09Deodexed and CM10.
Ok so no luck. Flashed CM10 and no bueno. Not getting all of the messages I send to myself. Massive delay between send and receive.
Then you're left to using Odin to get back on stock. Check auto-reboot, repartition, and f. reset time. After you are back on stock FC09, you may as well update PRL, but be sure to update profile. Test on 100% stock again.
If things work like they should on stock, then Odin in CWM without auto-reboot checked. Battery pull, then reinsert. From there boot into recovery and flash a rom of choice. Test again on newly flashed rom.
If things are not working properly on stock rom, then bring it into a Sprint store for service.
Sorry to say but all of that's been done and put in the original post (which you only speed read through the last part). I appreciate your help though. This is the second Epic 4G to do this to me on everything but the stock rom which makes me think it's not hardware but if it's not happened to anyone else then not much else I can do.
ignoredthoughts said:
Sorry to say but all of that's been done and put in the original post (which you only speed read through the last part). I appreciate your help though. This is the second Epic 4G to do this to me on everything but the stock rom which makes me think it's not hardware but if it's not happened to anyone else then not much else I can do.
Click to expand...
Click to collapse
Haha, yea well it was a big wall of text.
I've burned through my ideas, lol. Good luck to ya.
Np, I really appreciate the advice. So far i've rerooted, reflashed the FC09DeodexedMTD and did a straight sprint (no lollygagging with install and uninstall of apps) to a barebones what I want system, apps include then backed up via CWM. So far it's still working great though i'll keep my fingers crossed. Should anything happen I have a backup from the getgo that should put things back to the way they were, ie. working. Stupid problem, of corse it has to only be me with it.
Ciao
IT
Long time fan; first time post.
I was hoping this posting had provided a solution, but the 'Contacts Fix' did not help with my apparent issue:
(Synergy ROM) Phone app now not working?
I'm lovin' the Synergy ROM, however every time I start up the phone, I always get the 'com.android.phone has stopped' error.
Please, would anyone like to take a look at the Logcats provided?
Attached in the zip file are two logcats. One records my attempt to make a phone call; the other I hope reflects what's happening when the phone is starting up: AttemptedPhoneCall.txt & StartingUpPhone.txt
Sure, I could go back to my High On Android ROM (Have to give a nod to its author, Max of GalaxyS3root.com), but it was Max that raved about Synergy in the first place, and it has grown on me.
Despite the fact I can't send or receive any calls. I can text and surf, but it's not a phone anymore.
I never received that error on Synergy, but I have seen it on other ROMs. Have you tried a full wipe and reflash? In my experience, flashing Synergy worked best when I flashed it from another TW based ROM.
You could try a different kernel such as ktoonsez kernel. I had a lot of issues with the standard ziggy kernel when I used synergy
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Will do
altrikdout21 said:
I never received that error on Synergy, but I have seen it on other ROMs. Have you tried a full wipe and reflash? In my experience, flashing Synergy worked best when I flashed it from another TW based ROM.
Click to expand...
Click to collapse
Thanks, altrikdout21.
Yes, I intend to. I was just curious if there were some developers out there that like to look at logcats for kicks.
Didn't think of that.
Domoo said:
You could try a different kernel such as ktoonsez kernel. I had a lot of issues with the standard ziggy kernel when I used synergy
Click to expand...
Click to collapse
Problems with the ziggy, uh?
Ok, I'll try another and let you know.
Thanks, Domoo.
Got it working...almost sort ya.
Restored my last ROM, HighOnAndroid. I did do the reflash of Synergy with a stock kernel, but there was no improvement, and so I restored my previous ROM. I can now start up the phone without the 'com.android.phone has stopped' error. However, there's a problem. I still can't make a phone call! Yikes! Now how can that be??? I did a ROM restore. Shouldn't the phone app be back as it was? It appears all the other apps are working. I can text, surf, etc. What's happening here?
I start up the phone app, select a contact, press the phone icon on the contact's screen, it comes up like it's going to initiate a call but then I see the 'end call' just as fast and the phone app then retreats back to the previous screen listing the contact I had selected to call.
As an aside, is there a place to drop off you logcats on this forum? Being an old VB programmer (what's that you ask?!), I'm curious to see what these new fangled 'android programmers' can do. However, now I'm ever more anxious to find out what's wrong with the phone app since I've restored my ROM only to find the one lone thing I do use regularly (it's a phone for pete sake!) is still not working.