Develop Bugs

Not receiving calls?

Before I get n00b bashed, I did "Search this thread" for the answer... (and other forums) Maybe I am just too n00b? Anyway, here goes.
Given kudos on this ROM already (Syndicate Rom: Frozen...anything is better than stock Froyo, but this is just AMAZING). But I was having some troubles with receiving incoming calls. Caller always got "All circuits busy" Or "cannot complete call as dialed".
Soooo, I wiped and reflashed. Tried to make a call (before restoring titanium backups) it worked, but my girl was still having troubles calling me...
So I restored most of my titanium backup (stuff that mattered?) and when trying to call out, I get "com.android.phone stopped working" and had to forcibly close it. So, I specifically restored phone 1.0 and contacts and all that from my titanium Backup, and still got the same issue. I am currently backing up stuff to my computer off the phone, going to format the card and do a fresh flash and see if that helps.
Thing to note, my account IS linked with Google Voice. Could that be an issue? And if not, is anyone else having this issue? Seriously the ONLY problem I am having with this rom. Thanks, guys!
Edit. Wipe and reflash did not help, however the phone is running MUCH better! Still not getting phone calls, though. Data works, MMS, etc, spotty 3G acceptance, though. Starting to get a bit aggravating. ANY help would be GRAND.

*sigh* think I got it. Flashed a different modem (EC03?) and it did not work, then flashed BACK to EC05 (AFTER the fresh flash) and it seems to have rectified the issue. HUGE thanks to QBKING77 (if that is his name on here) for the AWESOME video tuts and great linking to the site. I will update if call status changes. But I would still be interested in knowing if anyone else was having the same issues?

Sorry no one ever got to you for help. The Q&A section doesn't exactly have dedicatedhelpers. =/
I'll be trying to help this section more. So please do update if it comes again.
Sent from my Epix 4G using XDA

Shoulon said:
Sorry no one ever got to you for help. The Q&A section doesn't exactly have dedicatedhelpers. =/
I'll be trying to help this section more. So please do update if it comes again.
Sent from my Epix 4G using XDA
Click to expand...
Click to collapse
No worries. My girl and I gave it another go this morning, and all went well. Also received all my calld last night with no issue. Definitely made my girl a happy camper. Lol. Now I just have to calibrate my battery when I get to work, and all will be golden!
Sent from my SPH-D700 using XDA Premium App

the only thing I could think of is did you "freeze" any apps in titanium LOL yes I froze the wrong thing once and got the same error's I think it was the voice mail stuff seeing i went to gvoice didn't think I needed it but I did.

Nope. All apps were left unfrozen, just because I am too n00b for that chit, lol.
However, I flashed the EC05, and all incoming calls (90%) seem to be coming to me. Odd part is, it SHOULD be going to my voicemail if it cannot be dialed. I am thinkin Sprint is to blame, and I need to have it out with them.
*sigh*
Oh well, everything else is tits... Just waiting EAGERLY for 1.2... Chompin at the bit and all that!
Might get bored tonight and flash back to stock... see if I have the same problem.
Question. Let's say I want to "image" my phone the way it is right now (kinda like Norton Ghost used to do?) Flash back to stock, yadda yadda... Is there a way to RESTORE my phone as is (every byte) back with clockwork? Or is that what Nandroid does? Because if I flash back to Stock, play for a bit (see if it is sprint's fault) and want to flash back, I will have to reconvert back to EXT4... using clockwork 3.0, should I just use the .zip (.img?) that nandroid creates instead of the base ROM?
If any of that makes sense, kudos will be given for a clear answer, lol

just loaded Emerald Envy 2.0....
Absolutely love the ROM, but I can no longer receive calls. I've tried the wipe (x3), re-downloaded the ROM, no joy. no combination that I can think of. Have tried all the latest modems (EC05/EF02), no joy.
I did notice that the phone log does log that a call was received, but it never rings or brings up the phone application.
I also tried flashing the Genocide 1.1 kernal. no joy.
I'm about to go back to my Midnight ROM that I Nandroid'd earlier today before I started down this road. Really hope I don't have to, i'm hooked on this ROM!
Any help would be greatly appreciated!
-Todd

Sully1965 said:
Absolutely love the ROM, but I can no longer receive calls. I've tried the wipe (x3), re-downloaded the ROM, no joy. no combination that I can think of. Have tried all the latest modems (EC05/EF02), no joy.
I did notice that the phone log does log that a call was received, but it never rings or brings up the phone application.
I also tried flashing the Genocide 1.1 kernal. no joy.
I'm about to go back to my Midnight ROM that I Nandroid'd earlier today before I started down this road. Really hope I don't have to, i'm hooked on this ROM!
Any help would be greatly appreciated!
-Todd
Click to expand...
Click to collapse
My errors seem to be different than yours. Mine would not show up in my call log at all, nor would the calls go to voicemail. Are your callers able to leave messages?
Mine turned out to be a sprint/phone issue. Their networks have been all kinds of crappy in my area since january. Sucks, but all I could do was call, complain, and get credits.
My new epic seems to be working fine, and sprint seems to have fixed their issues in my area. I was running 1.2 up until last night with no issues callin/receiving. I only updated to the latest GB leak because it is hella stable and netflix works. Just seems to have some 3d issues. But I do not game much on here.
Keep troubleshooting, and give 1.2 a whirl. While your problem is not ROM related, I am very confident your experience (and battery) will be much better.
Oh. And call Sprint. Complain and whine. You will get credit on your bill. Lol.
Sent from my Epic. Which is better than yours.

Google Talk issue - after a few minutes Contacts are all offline when not

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.

Galaxy S III fails to sent long SMS

Well, this is an odd issue and i'm sure many other have it because all of my friends with GS3's have this problem. I have a rogers GS3, my friend has a Telus and other videotron and multiple times a week, when we try to send a moderate or long sms (3 lines and more) the phones fails to send the message. This is very odd because i've tried everything from a factory reset, full odin wipe, different roms, and nothing works. I'm on CM10 M2 now and the problem is also there.
When i try to send a long sms, it fails, then i sent a short one right after, it works, then i copy and resetn the original one that failed and it faisl again. I pretty sure many of you have it because we have 3 different GS3 on 3 different networks and it happens to all of us
I tried looking around, i have not found much, maybe somebody has such problem and perhaps a solution?

This happened to me earlier this morning. No idea what can even cause an issue like this.

nobody??? im sure many people have this

I think this is based on all aosp roms.
I don't know if it's fact or opinion, but I always get the "sent" message after receiving the "not sent" error.
In other words, it seems like it still sends the whole text, but just throws you an error initially.
Can someone correct me if I'm wrong?

Well i can correct you wrong because i've tested it it does not sent the messages nor does it have anything to so with AOSP roms because i've used both AOPK and they both have the issue,

I send long sms no problem.. some in fact so. Long it automatically breaks them into two. What firmware are you on.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

First off this belongs in Q&A so I will move it
Second AOKP is also considered an AOSP type ROM
There should be an option in your mms app to split messages over 160 characters. Make sure it is checked.
On the Touchwiz ROMs that came with the SIII and all TW custom ROMs this is not an issue. This is a Touchwiz phone so changing your ROM to anything but that will have some bugs and require fixes and workarounds.
Friendly Neighborhood Moderator

Contact your carrier
Especially if you're having this issue on and off

Do other apps work? I use ChompSMS (fixes lots of annoying bugs in the TW SMS app) and I can send long messages fine.

kennyglass123 said:
F
On the Touchwiz ROMs that came with the SIII and all TW custom ROMs this is not an issue. This is a Touchwiz phone so changing your ROM to anything but that will have some bugs and require fixes and workarounds.
Click to expand...
Click to collapse
i have to disagree. I had like i said in OP, i tried ALL roms, stock, stock rooted, cyanogen and many other, this was an issue in all roms.

polish_pat said:
i have to disagree. I had like i said in OP, i tried ALL roms, stock, stock rooted, cyanogen and many other, this was an issue in all roms.
Click to expand...
Click to collapse
are you using a mms app other than what's provided with the rom? And are you able to send any messages at all? or does it fail to send only on long ones?
If you were on stock and still can't send any/long messages, check your apn settings and make sure it's correct for your provider, especially if you are installing roms (stock or custom) that are specifically developed for AT&T phones. From your profile I'm assuming you have a Canadian version.
Check the APN settings. If that's all correct, return the phone for a new one

all apn settings are fine and this is not an issue with the phone because like i said, it would be one hell of a coincidence if this happened to both of my friends with gs3s on different providers. Also i am using stock sms app and this only happens with moderately long sms, it doesnt always ahppen, its random

If it's intermittent, and it's not just you but also your friends, it sounds like a provider problem. From what I have been reading on different forums, it seems service in Canada has been sketchy because they're adding LTE towers everywhere.
I don't know if that's really the case, but all I can say is texting works well for me down here on the AT&T network, both on AOSP (which also includes AOKP as you were mistaken earlier) and stock-based ROMs, although I do get the error on AOSP based roms for long messages. I've asked my friends and they say they receive the whole message just fine.
Last thing I can think of is if you flashed a custom kernel and it messed with some of your drivers. I know KToons kernel has modified drivers, and you're supposed to flash the stock kernel provided in that thread if you're going back to stock. Try that and see if that fixes your problem.

yup, i've flashed ktoon kenel as i had major issues with faux kernel as per this thread: http://forum.xda-developers.com/showthread.php?t=1937476
i'll report back in a week to see if any different
thanks for you help

2 common problems that I've always had issues with

Alright, I’ve had Sourcery JB on my phone for a while now. V4.3
Over time these are the problems I just can’t understand and need some light shined on them please.
The GPS:
Is a joke. It has NEVER been accurate one single time since I’ve installed the rom. It’s always 2000+m OFF. what the faq? All my apps are updated, what’s the deal?
Sending pictures:
I use GOSMS. However, I CANNOT for ANYTHING send pictures via text in this app. I have to go through the native app every single f’ving time and that only works 50% of the time. Wtf is going on here? Is it AT&T? Is it the rom or my phone or what?
Would going back to stock JB fix all these issues? I love the ROM(s) but the problems listed above are VERY important to get working as they are some of most basic functions phones have.
I almost just updated to JBSourcery V5 and tried sending picture using default text msg app. Still, same results. It won’t f’ving send.
Please help.

Not sure about your GPS issues - mine has always been pretty quick to lock regardless of the ROM I'm using.
But in regards to your problems with MMS messaging - I had the same issue on every ROM, including stock until I switched to AOKP. I called ATT to make sure everything on their end was as it needed to be. Double and triple checked my APN settings, all to no avail. Not sure what it was about this particular ROM, but since flashing, I haven't had any issues.

[Q] AOSP reboots but TW is fine

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.