Hi all,
I'm running cm10 currently, have been using it for a long time. I have the 2.40 telestra radio installed, never had an issue in the past with it.
After flashing the new 0127 weekly from cm10 (4.1.2), I cannot make or receive any phone calls. SMS works fine, data works fine. I have recovered to an old backup that was working fine, still cant call/receive calls. The call begins, 2 seconds of nothing then says call ended. I have flashed a brand new ROM, recovered to 3 different ROMs (MIUI,venom,AOKP) all the exact same issue, I did a clean install, Ive tried different radio's 2.09/2.40 (only ones that seem to work well data wise for me), I've done everything except flash the stock ruu (which I'm having trouble finding documentation on, I believe the easiest way is with the one click tool, scared to flash the wrong ruu though )
My screen has a crack in it, not sure if its relevant as the issue began after I flashed the new nightly, I don't understand how this could be physical.
All in all, I'm stuck can't use the calling feature at all. The mic still works, tested with a recording app. I'm just looking for a suggestion as a next step.
The phone is a rogers HTC one x, please let me know any suggestions or if anyone has encountered this before.
Thanks in advance guys,
Josh
wilkins502 said:
Hi all,
I'm running cm10 currently, have been using it for a long time. I have the 2.40 telestra radio installed, never had an issue in the past with it.
After flashing the new 0127 weekly from cm10 (4.1.2), I cannot make or receive any phone calls. SMS works fine, data works fine. I have recovered to an old backup that was working fine, still cant call/receive calls. The call begins, 2 seconds of nothing then says call ended. I have flashed a brand new ROM, recovered to 3 different ROMs (MIUI,venom,AOKP) all the exact same issue, I did a clean install, Ive tried different radio's 2.09/2.40 (only ones that seem to work well data wise for me), I've done everything except flash the stock ruu (which I'm having trouble finding documentation on, I believe the easiest way is with the one click tool, scared to flash the wrong ruu though )
My screen has a crack in it, not sure if its relevant as the issue began after I flashed the new nightly, I don't understand how this could be physical.
All in all, I'm stuck can't use the calling feature at all. The mic still works, tested with a recording app. I'm just looking for a suggestion as a next step.
The phone is a rogers HTC one x, please let me know any suggestions or if anyone has encountered this before.
Thanks in advance guys,
Josh
Click to expand...
Click to collapse
Got it fixed, I ended up speaking with tech support from my carrier, they "refreshed my number" on the network, solved the issue. I ended up going through the entire RUU rewrite process for no reason. Just an FYI for other people out there, start with tech support first, ended up being an issue with the network, not my software.
Related
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
brandon827 said:
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
Click to expand...
Click to collapse
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
sliderocket22 said:
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
Click to expand...
Click to collapse
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
homeslice976 said:
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
Click to expand...
Click to collapse
Man, I'm glad I'm not the only one having this problem. I thought my phone was defective at first, and now I don't feel so crazy anymore. My sister was furious with me, I had to pick her and her boyfriend up from DIA yesterday to take her to Copper Mountain to snowboard with my girlfriend and myself, and she called me 4 times and I didn't receive a single one. I wonder if it has anything to do with HSUPA being enabled on the phones, but at this point I'm just ready to give up root and go back to stock. I don't make tons of calls, but I'd like to be able to when I need to, and for my phone to not hang up on me in the middle of one. I have noticed though it's particularly bad for me when I'm on bluetooth.
I was also having those problems
I am using Revolution 4G 2.1. I'm in the process of trying to get the problem figured out. Stock rooted rom had problems for me because you couldn't set it to GSM only, and that's the only way I've found to make the phone reliably work as a phone.
If anyone can figure it out, I'd love to know what causes it. I've been poking around myself, but haven't come up with anything worthwhile. I suppose I'll flash a different rom and try that.
Sent from my Desire HD using XDA App
Anyone found any clue as to why this happens? I've searched the dev forums but nobody seems to mention this, which makes me wonder if most people have this problem.
Sent from my Desire HD using XDA App
I have never had this problem. Running a rooted stocker.
Sent from my Desire HD using XDA App
It happened to me again last night. Still had data but lost the ability to make/receive calls. I switched network to GSM only, the data switched to EDGE, and i was able to make/recieve calls. Turned back to GSM/WCDMA, no calls. Rebooted, no calls. Turned back to GSM only, calling functionality returned. I did another full wipe, installed AR 2.1, sound fix, apache 1.6 kernel, and calling is restored when connected to HSDPA/WCDMA. Has been working fine for the last 12 hours. I'll keep you updated. I don't know why it's doing this, and it doesn't make sense as to why a wipe would fix it. The first time this happened I was runing the stock radio. Last night when it happened i was running the recommended radio in the AR thread (M2). I've now switched back to stock this time...let's see what happens
Edit: I am also glad to know I'm not the only one having these issues...maybe someone a LOT smarter than I am can figure it out. It's annoying to have to have a slow data connection to have a reliable voice connection. The last Android I had (LG GW620 Eve), also did this from time to time, but I just blamed it on the fact that it was a POS. My voicemail actually went like this "This is Greg. I probably have no idea you called me just now, so please leave a message and I'll get back to you"
Edit: mike1986 (android revolution developer) just chimed in in his thread and stated these issues should be fixed in version 3.0 set to be released soon. Is anyone else that's having these problems NOT running Revolution?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
I had this problem when I first rooted (running Inspire 4G Stock Rom w/Root, HSUPA, and Sideloading from the development section) I installed Android Revolution 2.1 and it went away.
I know from my captivate days that sometimes a ROM just hiccups and a fresh flash can fix the issues. I don't know if this is the same with HTC, but it's all android so It's plausible.
Hey everyone,
I have had the infuse roughly since it was released. Never really had any call isuues or anything. Lately however, about 90% of my calls end up dropping. Also, when i try to end a call, the phone kind of freezes and shows that the call has not ended, but it should have. The phone symbol shows up at the top or the status bar stays green... I have no idea what this could be attributed to. I have used different roms and never had an issue. My most recent rom is the Max Q Rom and everyhing was working fine then after a few weeks this calling and ending calls situation started. Tried reflashing the Rom, but problem is still present, dont really think it is Rom related.
Anyone have any input? I cannot seem to figure it out and my phone as a phone has become virtually unusable...
Thanks for any and all help!
Heuser1 said:
Hey everyone,
I have had the infuse roughly since it was released. Never really had any call isuues or anything. Lately however, about 90% of my calls end up dropping. Also, when i try to end a call, the phone kind of freezes and shows that the call has not ended, but it should have. The phone symbol shows up at the top or the status bar stays green... I have no idea what this could be attributed to. I have used different roms and never had an issue. My most recent rom is the Max Q Rom and everyhing was working fine then after a few weeks this calling and ending calls situation started. Tried reflashing the Rom, but problem is still present, dont really think it is Rom related.
Anyone have any input? I cannot seem to figure it out and my phone as a phone has become virtually unusable...
Thanks for any and all help!
Click to expand...
Click to collapse
Have never heard of that.... still have you tried a data and cache wipe in cmw? then install a rom on a fresh device? I know you will have to back up all your stuff but may be the answer.
Also try another modem may help. Im not sure since ive never experienced that but give it a try.
Heuser1 said:
Hey everyone,
I have had the infuse roughly since it was released. Never really had any call isuues or anything. Lately however, about 90% of my calls end up dropping. Also, when i try to end a call, the phone kind of freezes and shows that the call has not ended, but it should have. The phone symbol shows up at the top or the status bar stays green... I have no idea what this could be attributed to. I have used different roms and never had an issue. My most recent rom is the Max Q Rom and everyhing was working fine then after a few weeks this calling and ending calls situation started. Tried reflashing the Rom, but problem is still present, dont really think it is Rom related.
Anyone have any input? I cannot seem to figure it out and my phone as a phone has become virtually unusable...
Thanks for any and all help!
Click to expand...
Click to collapse
I can relate. I had the same exact issue a few days ago. I just flashed and didn't look back.. though I probably will eventually. Try Mitra, very good. I loved it. Experimenting with Caty's rom now. Good luck. Wipe/factory reset, wipe dalvik and fix permissions. Then flash. Let it sit for 10-15 before you start using it. Make sure it settles and gets used to, "it's native infuse guts," as EXPERIMENT put it.
As title says, I went to the theatre today and realized I still had 5 bars of WiFi when I was 20KM away from home, was this a one time glitch or is it a known problem?
sounds familiar....
hey there,
I'm down here in New Zealand with a both versions of device, X & XL
my XL has the problem you speak about.
When i leave my house, it takes for ever to disconnect, pain of course because the 3G or 4G wont flip on while it thinks it is still on wifi.
When i return to my home/SSID the device takes for ever to reconnect, if it even does. i go to the wifi settings, and the connection initiation is just cycling, end attempts to connect, over and over.
I've thought i had fix it once before, by installing a new RUU. I was on RUU 1.77.708.3 Asia, could only find 1.77.708.2.
this seemed to fix disconnection on departure problem, but the cycling and hunting continued when i returned.
I have since found that this must be linked to the bluetooth. I say this because while the wifi is hunting/cycling i flip off the bluetooth and the wifi reconnects within seconds. I tested this more and with bluetooth disabled i have no wifi problems at all, but with bluetooth on, its gives my problems.
The second issue is the bluetooth its self. unlike my flawless desireHD, i can only stream music to my car head-deck, when i get a phone call, the music cuts out like it should, but the phone audio doesn't happen, been like that from the get go. wifi was a problem all the time because this dodgy bluetooth was on all the time so i could listen to music in the car and hopefully one day take calls in the car also.
well i have good news for me, today i flashed CleanROM.3.Standard .
http://forum.xda-developers.com/showthread.php?t=1655011
Today for the first time I can take calls over bluetooth in the car. this is good news because i was certain this was a hardware issue, even it it is, i am confident it can be resolved in the software now.
I'll do a few drive-by's my house tonight to test this wifi, see if that got resolved also. I'll let you know the result later.
I tell you all this in-case our issues are the same, it might save you some time... maybe.
good luck with, and check that bluetooth theory because i'm dying to know if its a common problem.
Cheers
Thank you for that very detailed post.
I also have bluetooth running (connected) to my car and it works flawlessly but it may be a cause for the WiFI staying connected as well. I will turn it off and see how it goes as the week progresses and keep this updated as well.
I would also like to flash clean rom but I am using the Rogers variant so I am worried it might not be compatible.
an_xda said:
As title says, I went to the theatre today and realized I still had 5 bars of WiFi when I was 20KM away from home, was this a one time glitch or is it a known problem?
Click to expand...
Click to collapse
This has been a known problem since the HOX has been released.
an_xda said:
As title says, I went to the theatre today and realized I still had 5 bars of WiFi when I was 20KM away from home, was this a one time glitch or is it a known problem?
Click to expand...
Click to collapse
First reaction: It's not a glitch, that's just really good WiFi...
Sent from my HTC One X using xda premium
I did those drive-by's......
Me again...
I did those drive-by's of my house, unfortunately there is no joy for me, still the WiFi behaves the same as before.
Its funny, down here we have assumed that the X is the same as the XL apart from the cpu. But in reality they are two completely different machines.
So I turned off Bluetooth and the problem does not occur anymore, WiFi disconnects as needed but it is obviously not a permanent fix. Another problem is the WiFi being on and off with 5 bars swapping between 4G and WiFi...
CleanROM again......
OK, I was doing some more reading and have since found that the developer of CleanROM has released a GSM patch so the hotspot on his ROMs now work.
You might remember i said earlier in this thread that CleanROM.3 worked best for me but the hotspot didn't work so i couldn't use it.
Now i have CleanROM installed again, Hotspot works, bluetooth both Audio & Phone work, and the WiFi at this stage seems to be doing what it should without having to manually toggle the bluetooth on and off. No apparent bugs to report at this stage.
Software Info on phone says this version is built around 1.29.728.12. I don't know if that means all ICS version of that number are good or not, but again its a place to start. Its looking like some versions have the issue and some don't, this re-assures me that it can be resolved within the software. I don't mind testing this stuff, as long as the developers don't mind developing it, and its a good learning curve.... its all good.
Check this CleanROM work out, it could be your answer.
http://forum.xda-developers.com/showthread.php?t=1655011
I'll check back in in a day or so and update you on my WiFi situation.
Cheers!
Thanks again for all your research and assistance.
I have the Rogers variant, should be no problem flashing it to CleanROM correct? Also, for each new CleanROM update, I would have to wipe and flash again? Seems troublesome.
Can you advise on the process required to flash the ROM? I am new to Android and the steps in the thread is not as comprehensive.
Many thanks.
hi there, show you how to load roms, thats a big job for me....
...I'm new to this myself, but i know a tutorial that will save me a ton of typing.
you need to do 2 things first, before flashing roms.
1,Unlock your bootloader
2,Install clockworkmod
have a look at this ,
http://forum.xda-developers.com/showthread.php?t=1647272
Study this thread, very helpfull. He explains how to install clockworkmod on your device, once you have that done you are 80% there, and you only have to do this process once, once done, flashing roms will always be the last 20%, you never do this again.
Infact flashing roms and backing up your own rom is a very simply task. the commands are on a list, just choose them as you go. To backup, wipe, and flash a new rom takes me less than 10 minutes.
Go to you tube and look at this, this shows you how Clockworkmod works.
http://www.youtube.com/watch?v=XOQEmQYFEeY
dont be freaked out, take it step by step, you'll be fine.
I also started this thread, regarding working roms for this wifi issue
http://forum.xda-developers.com/showthread.php?p=27585586#post27585586
no one has replyed yet, but it might yeild helpfull info later on perhaps
Thanks, I will do this shortly. Will unlocking the bootloader or doing any of the aforementioned steps give me the tampered signature?
Yes
yes, your phone will be marked.
Boot loader will be marked "Unlocked" , even if you relock it, its just gonna say "relocked" . nothing you can do about that.
The boot loader will also say "tampered" if you update the rom, but that msg dissappears completely if you update the phone via an RUU.exe
Can this hurt me with regards to warranty requests? I know I can remove the tampered status by flashing a stock ROM but I am concerned re: bootloader.
Okay, so I flashed Paranoid Android 2.16. Everything went great, flashed fine. But I could not get wifi to work at all. It would turn of and back on randomly, would not connect to any network, etc. So, I flashed the ROM by Team Viper. Again, flashed fine, worked fine, but Wifi would not work, it would do the same thing.
So, then I restored my nandroid backup, and wifi works grand. Is there something I missed? Stock isn't too bad on this phone, but I'm a flash junkie, and I'll miss JB on my GNex. PA works beautifully, except for the damn wifi issue.
So, any suggestions on how to get wifi to work on my custom ROMs? Loving this phone so far, I've missed HTC. The three things that would make it my *perfect* phone is SD card slot, bigger battery, and 720p screen. But the phone is gorgeous and feels amazing physically and performance wise.
Same problem...
pritz786 said:
Same problem...
Click to expand...
Click to collapse
Okay, I'm glad that it's not just me. I'm going to try again, sometime tomorrow or later today. I'm hoping that it's something that can be fixed with a little more digging, or if it's something that we need a wifi module for.
Same thing here. Just fixed a soft brick now I got utb ROM working. Flashed trick droid and WiFi is gone.
Sent from my Nexus 7 using xda app-developers app
Okay, there was another post with this issue, something that I missed. But apparently it's because of the last update (ICS 4.0.4 & Sense 4.1).
Flashing ROMs over this update seems to be breaking wifi. Here's the other post: http://forum.xda-developers.com/showthread.php?t=1913757
I'm having a lot of trouble with this as well. I just bought a One S a few days ago and got to work rooting, etc. After trying to install other ROMs, I can't get wifi to connect.
I have a T-Mobile version One S and can only assume it's gone through the latest updates prior to my purchase (got it through craigslist).
I have a decent idea of what I'm doing with these phones most of the time, but it seems like this time around I may need a little hand holding through the potential fixes. Like an idiot, I didn't bother to do a backup before jumping into flashing my first ROM, so I probably shouldn't be surprised that I'm having troubles.
Anyways, any help would be greatly appreciated. Right now I'm just stuck here.
What info do you need and how can I find it?
Extra info:
I did try the 1.84 and 2.35 partition fixes but still couldn't get the issue resolved.
Yeah.. I flashed the international version of trickdroid and my wifi signal was great, then I flashed the TMO version (I have a tmo one s) and it messed up my wifi signal completely, weird.
Have you guys found a way to fix it? Im having the same issues with all the custom roms, I've tried several of them and even different versions of the same rom(I thought it was an issues with that rom version) but the wifi never seems to work on any rom I flash. I'm using a htc vivid with att. If you found a fix could you pm me?
ISSUE RESOLVED
Thanks, SlimSnoopOS!
Alright let me say that while I am very inexperienced with ROM-ing and the like, I have done it once successfully in the past (several years ago with my Droid X) without any issues. I rooted my phone today and installed the latest D2VZW release (not nightly) of the Carbon ROM.
My biggest problem is that I have no mobile network connection. I have looked at other discussion boards with people having similar problems, but were not of help to me as I have no idea what they are saying. I can say, however, that my IMEI number is correct (had it written down), but my phone number according to the Status is 000-000-2212.
EDIT: There is a mobile network connection. I have the bars, and "4G" switches back and forth to "R". I can't, however, call or receive calls, or text message at all.
EDIT2: Upon updating to latest version, my phone number is reporting correctly, but I still can't use my mobile network connection. It does not ask me to do the initial setup upon starting for the first time after flash.
Second, there is no lock screen, the home button doesn't work, most apps don't come up at all, etc. I'm totally lost.
I appreciate all help trying to get me pointed in the right direction here, or at least figuring out what's happening. I will do my best to provide as much information as I can, and I apologize ahead of time for my lack of understanding.
EDIT: If it's not something I can fix, I'll try to reset it back to stock using the pinned thread, but I don't have time to do so right now.
EDIT2: I updated from v1.0 to v1.8, and it resolved most of the problems, which I deleted from this thread. The vital ones are still present, however.
When you flashed CarbonRom, what did you wipe in recovery? Also, have you done any of these steps? Lastly, since you performed some edits, could you clarify what is currently wrong with your phone?
Thanks for your reply! I was actually going to delete this post and start a new one because I've greatly narrowed down my problem. Just typing it all out above seemed to help me think about the problem and fix it.
After getting all updated ZIPs and flashing them, I got the ROM working properly.
The problem with the mobile network persisted, but after trying Fix #2 in your link, it worked. As far as I can tell, my phone is fully functioning now. Thanks a ton!
Always here to help!
Sent from my SCH-I535 using Tapatalk 4