First of all I am really not sure if it is the right forum to ask this, But I am suffering a lot.
It happens while my phone rings in my pocket after a long break (30 to 45 minutes), I am failing to answer the call. I tried putting the green button in the ring and also pulling up the ring. Currently I am using insertCoin latest 2.3.5 rom with sense 3.5. I tried Senso-maniac (2.3.5+3.5), RCMix (2.3.4+3.0) and all of them had same problem. I haven't tried with stock rom (rooted and upgraded before putting a SIM in IT afternoon).
I captured system log for a failed call and a successful call. Attaching for your kind analysis.
Few more info:
Country- Bangladesh
Operator- GrameenPhone
It was a Sim free handset.
You should flash back stock & make sure if it software or hardware related.
Also check this thread.
I bought a refurbished Motorola Defy+ which came preinstalled with Gingerbread 2.3.4. Out of the box, the phone was able to receive calls, although I didn't test making calls at that time.
I ran the stock Software Update from Settings, and this installed 2.3.6 on the phone. Since that point, I can no longer make or receive calls on the phone. As soon as the phone tries to make the connection, it reboots: either when making a call into the phone, at the first ring, or when dialing out. I have confirmed that it's not the dialer itself that is the problem by using different dialer apps.
I have performed a full factory reset on the phone and tried with wifi, etc turned off but it has made no difference at all. Other features of the phone are absolutely fine and I have had no unexpected reboots due to any other cause.
After searching around it seems quite a few people have had problems with their Defy+ rebooting, but this is generally either during a call or just randomly. In my case it is absolutely at the exact time that it tries to make the phone network connection and at no other time.
Could this be a hardware problem, or is it more likely to be the 2.3.6 ROM installed by the software update? If I install another ROM, is it likely to fix the problem? If so, how would I go about downgrading the phone to the 2.3.4 version?
Thanks in advance.
OK, I jumped the gun.
I hadn't actually connected to any of my mobile phone network's APNs at the time I posted the above. Now that I have configured it to connect via 2G or 3G, I get random reboots all the time.
Not that this helps or anything.
Hi Everybody,
This is my first time posting on here, but I absolutely cannot find anybody with this exact problem after searching the forums and the googles.
So, a couple of weeks ago, I started having trouble sending SMS messages. I don't have any trouble receiving them and I can send MMS messages just fine. I can also make and receive calls without problem. The strange part is that if I leave the phone alone for a little while, I can send one SMS message successfully, then I've got to wait for another hour or more before I can send another one.
I am on a Samsung Galaxy S3 (SIII) with Verizon. I have Cyanogenmod 11 on here and I will list the version and other details below. I have had it rooted with CM for months now with no issue. I believe I may have done a CM update at some point that could be related, but I'm not sure.
Model: SCH-I535
Android Version: 4.4.2
Baseband version: I535VRBMF1
CM Version: 11-20140210-SNAPSHOT-M3-d2vzw
So here's my issue, my Galaxy S Blaze has been switched from ROM to ROM constantly, I have seen ROMS with modified build.props, other added features, and a bunch of other tweaks, you name it! I don't know what all those tweaks mean, I have no idea if it could affect the way my phone receives the signal but it got me so frustrated that I kept switching roms until finally then I went back to stock and am no longer am switching to another ROM.
Here's a history of the ROM switching I've made in the past couple of months:
1st - MIUI
2nd- Cyanogenmod
3rd- Gummy ROM
4th- Liquidsmooth ROM
5th- Cyanogenmod
6th- Dirty Unicorns (problems with signal started occurring right about here, and onwards)
7th- Stock ROM (hmm... nope nothing fixed.)
8th- Validus (still no, I didn't like the constant force-closing of many apps)
9th- Gummy ROM (nope, what's worse is my screen kept freezing if I had atleast 2 apps open and I slid down the notification drawer)
10th- Cyanogenmod (well, maybe switching to cyanogenmod will fix it)
11th- Gummy ROM (*sigh* switching back? Nope, still didn't help my signal)
12th- Stock ROM (you would expect it to be fixed right about here, but nope)
So what's up what is the exact problem with my signal? Here's the thing: My signal works! That's a start atleast. However, if I turn on my Wi-Fi while I'm home, I can still call/text people, all of that works. But after maybe 2 hours or so, the signal bar is still there, it's telling me it has signal and it's connected, SOMETIMES it will be empty meaning I have no signal(when I really do). But in reality, I can't receive texts, nor calls, none of that. So how do I fix it? By restarting my phone sadly, that has been the only solution for me for these past 2 months. People have complained to me because I don't answer my phone anymore, well I'm sorry my phone can't receive those calls due to this messed up signal. There are 3 other T-Mobile phones in the house that have no problem! The problem here is with my Blaze phone.
So what if I turn the Wi-Fi off for the whole day and see if it's the main thing causing the issue? Well, I did this. Turns out that the signal stays on longer than when I'm on Wi-Fi but it still goes out. I have switched SIM Cards, I have tried switching my APN: from "epc.tmobile.com" to "fast.t-mobile.com" but the problem appears to happen more quickly on the "epc" one than the "fast" one. Please help me with this, this has been frustrating me a lot lately. I'm not sure if anyone has even had the same exact problem that I'm having, I've searched online but haven't seen a similar problem.
Some of you might say, wow that is a lot of ROMS you've switched to, I'm sure there were more that I missed but that's as of recent. I can install ROMS correctly, I know how to use CWM when installing a .zip and using Odin when it's a .tar(or other supported file extensions). I've factory reset, wiped the cache, the dalvik cache, all before installing a new rom. After installing each rom, I've also factory reset and wiped the cache to make sure no other problems could affect the way the rom would work. Hopefully I did the procedure right, thanks for anyone who's willing to help me!
Right now I am running:
Baseband Version:
T769UVLH5
Kernel Version:
3.0.8-perf-T769UVLH5-CL990184
[email protected] #1
SMP PREEMPT Fri Aug 17 15:12:14 KST 2012
Android Version:
4.0.4
Another Issue is that I can't even transfer files to and from my phone when connected to my computer! This is another big issue, here are some images:
http :// i.imgur.com/xx699ss.png
http :// i.imgur.com/1wRzJpX.png
Here's what happens when I turn Wi-Fi Calling on but maybe it's just a built-in function that I forgot it had and it's probably normal:
http :// i.imgur.com/cTSqRci.png
By the way, sorry for the links just copy and paste them in a browser to and remove the spaces between the http :// and i.imgur, thanks! Unfortunately, I can't post links until I reach 10 posts. If the links don't work for you, I've also provided attachments.
Many thanks!!!
That last picture does show the proper function of Wi-Fi calling however I don't know what to say about the rest of your problems.
Sent from my SAMSUNG-SGH-T769 using XDA Free mobile app
There are two things I would recommend trying...
1. Use Blackhole System Wipe
I know you've been following all the proper steps in CWM (and I would say to keep doing so), but I've added using Blackhole, in addition to the first steps, and I always get great system performance on my phone, and my parent's phones (I put them on ProvisionMod after stock was being stupid). It works well for pre installation for ANY ROM and helps prevent pesky issues. However, chances are, your issue is baseband related and this probably won't solve it... But still! You never know! It's worth a shot!
2. Reroot your phone
I know this will be annoying and pesky... but sometimes the process goes wrong from the beginning and starts giving issues later on... When I first rooted my mom's blaze, something went wrong, despite my following all the directions, and one of her partitions was completely disabled, no matter the ROM. I redid the process of rooting her phone (not from GB though... From the ICS stock) and fixed the issue instantly! I would try these two steps first and see if they do anything! Good luck!
Sent from The Doctor's Blaze
Hello! I'm going to need some help on someone that might know more than I do.
Here's the challenge:
Phone: Samsung Galaxy S7 AT&T Unlocked (G930A)
Build: G930AUCS4BRA1 (latest)
This phone has two really hard to pin down issues that will surely make a challenge.
First one, is the microphone. Calling or receiving a call makes the person on the other end to hear themselves. It is not explained by the other person using speakers, since it happens 100% of the time, even testing it with the express instruction to not use a speaker.
What the hard-to-pin-down issue is? It doesn't happen with any other calling program. I can voice call from WhatsApp or from an app from my provider using Wi-Fi or 4G and the issue disappears. Only happens if I receive or make a call from the phone without using Internet.
Second one, is a new one that happens randomly. The phone freezes, shuts down and restarts in a loop, about 3 or 4 times, and then works normally. Happens about 2-3 times a day and started two days ago, without any physical damage as a cause.
What has been done to try to fix this issue?
Cleared cache
Phone reset
Installed updates (twice, one from 6.0 to 7.0, and then updated the build number), once by using Odin, and the other one to update from SD Card.
Nothing has fixed any of these issues.
Any ideas?