Related
Hey everyone been around these forums for a while now, but my first post.
Recently my phone has started acting weird.
I am running
IPL 2.26
SPL 2.26
GSM 2.25.11
OS 4.0.0.0
Using nbd.v7.1.touch.ext ROM,
was also using the Faria WM6 ROM
the issue is that the phone picks up my signal, it stays for a few seconds then and then it loses signal and the phone turns off ( in com manager phone is now off), then the phone turns on (in comm manager) and searchs for signal, and it keeps repeating the same sequence.
I have tried changing ROMS and i keep getting the same thing.. I have no clue what the problem is. I even got a new sim card and still problem persists.
Any ideas?
just a guess.. you have cingular? yea it would be the radio ROM. try the t-mobile 2.19 uk rom.. it works best (in my experiences). give it a try.. you can find the link in the wizard wiki.. good luck
.:Nstefanelli:.
PS.. even if you don't.. give it a try anyway
Will give it a try thanks..
sorry i forgot to say, its a t-mobile rom.. im in canada so my service is from fido..
i'll post back with 2.19 results
Alrite, updated or sould i say downgraded to 2.19 radio.. It seems better, but i figured out why i still get low signal now, my back plate (which has the camera lesn on it) also acts like an antenna, and the clips have broken off on my plate so it is siting lose thus not making proper contact with the antenna pins.
Radio did help imporve signal a little, i just have to find a place to buy that backplate now. Any ideas?
omalak said:
Alrite, updated or sould i say downgraded to 2.19 radio..
Click to expand...
Click to collapse
the numbers have no relation to the 'newness' of a radion rom
It seems better, but i figured out why i still get low signal now, my back plate (which has the camera lesn on it) also acts like an antenna, and the clips have broken off on my plate so it is siting lose thus not making proper contact with the antenna pins.
Click to expand...
Click to collapse
that's because the little rubber circle, above and slightly to the left of the flash is the antenna.
replacement covers/cases are sometimes on eBay.
I am running a ROM based on the HTC Official Wm6.1 (5.2.19212, WWE 3.29.707.0). I noticed this behaviour last week but put it down to a random glitch, however today in the same scenario I have hit the same issue.
I have been working in a basement where there is little or no GSM coverage - GSM icon says 'No service' when clicked. I was working there for a few hours so the Kaiser was like this for the whole time. When I eventually finished and got back above ground the GSM icon registered a few bars and I could make a call. There was no audio though - the screen displayed 'Connected' and adjusting the volume did nothing for the audio of the call. The resolution was to soft-reset the Kaiser and then everything was OK.
I had the same behaviour last week when I was working at the same place, but last week I just thought it was a random glitch, todays repeat makes me think it is something more.
Any ideas?
Andy
ADB100 said:
I am running a ROM based on the HTC Official Wm6.1 (5.2.19212, WWE 3.29.707.0). I noticed this behaviour last week but put it down to a random glitch, however today in the same scenario I have hit the same issue.
I have been working in a basement where there is little or no GSM coverage - GSM icon says 'No service' when clicked. I was working there for a few hours so the Kaiser was like this for the whole time. When I eventually finished and got back above ground the GSM icon registered a few bars and I could make a call. There was no audio though - the screen displayed 'Connected' and adjusting the volume did nothing for the audio of the call. The resolution was to soft-reset the Kaiser and then everything was OK.
I had the same behaviour last week when I was working at the same place, but last week I just thought it was a random glitch, todays repeat makes me think it is something more.
Any ideas?
Andy
Click to expand...
Click to collapse
Flash a 1.65.xx.xx radio!
AllTheWay said:
Flash a 1.65.xx.xx radio!
Click to expand...
Click to collapse
Radio is 1.65.20.29.....
Plus it is security unlocked and HardSPL'd using HardSPL 3.56 from JockyW
That's a good radio, usually. Maybe reinstall the radio or have you tried other 65 radios?
Maybe this will help, http://www.google.com/search?hl=en&as_q=no+audio&as_epq=&as_oq=&as_eq=&num=10&lr=&as_filetype=&ft=i&as_sitesearch=http%3A%2F%2Fforum.xda-developers.com&as_qdr=all&as_rights=&as_occt=any&cr=&as_nlo=&as_nhi=&safe=images
kimtyson said:
That's a good radio, usually. Maybe reinstall the radio or have you tried other 65 radios?
Maybe this will help, http://www.google.com/search?hl=en&as_q=no+audio&as_epq=&as_oq=&as_eq=&num=10&lr=&as_filetype=&ft=i&as_sitesearch=http%3A%2F%2Fforum.xda-developers.com&as_qdr=all&as_rights=&as_occt=any&cr=&as_nlo=&as_nhi=&safe=images
Click to expand...
Click to collapse
It's going to be a bit difficult to test as I am not likely to be working there again for a while.....
I'll keep an eye on it and see if it occurs again under any different circumstances.
I did search prior to posting......
Andy
Hmm, it's happened again but different circumstances...
This has just happened again however the circumstances were different. There was no loss of GSM signal, however I did have the GPS & WiFi enabled prior to it failing. I made a call but I didn't hear any ringing, it then said connected but there was no audio. I soft-reset and it is now working again.
I have since enabled WiFi and started TomTom and tested it again and it is working so it doesn't seem consistent.
I upgraded the Radio at the weekend to 1.65.24.36 so this has happened on two different radio versions as well.
Has anyone else seen this behaviour? Is it possible the Kaiser is faulty? (I don't think so, but you never know?)
Andy
ADB100 said:
This has just happened again however the circumstances were different. There was no loss of GSM signal, however I did have the GPS & WiFi enabled prior to it failing. I made a call but I didn't hear any ringing, it then said connected but there was no audio. I soft-reset and it is now working again.
I have since enabled WiFi and started TomTom and tested it again and it is working so it doesn't seem consistent.
I upgraded the Radio at the weekend to 1.65.24.36 so this has happened on two different radio versions as well.
Has anyone else seen this behaviour? Is it possible the Kaiser is faulty? (I don't think so, but you never know?)
Andy
Click to expand...
Click to collapse
there is anohther thread that seems related.
http://forum.xda-developers.com/showthread.php?t=352906
Might prove to be a good place to see if any of your issues are related. Still no fix, unfortunately . . .
I think its related to 3G
I live in area where there is no 3G coverage(ATT sucks!) so I have to turn off 3G functionality in the phone. If I keep 3G mode on then everything works fine but I get the same problem of no audio.
So I suggest try turning off 3G mode when you get this problem and see if this fixed the issue.
Hope that helps,
Regards,
Hardik
I've had this happen twice on AT&T in the last two weeks with official released ROM 1.62.502.0, 1.27.14.09 radio. Both times it happened after I was in an area with sketchy coverage, then returned to good coverage. It was also in a 3G coverage area that would go back and forth between 3G and 2G.
I have a friend who has the same stock ROM and radio, AT&T Tilt phone, who this happens to all the time. He believes it happens when his phone goes to G, and then back to E. Typically that happens if you are close to losing a signal, the phone reverts to GPRS, then bounces back up to EDGE.
I just tried an experiment with some aluminum foil wrapped around the phone to attenuate the signal and bring it back, and couldn't reproduce it. But I don't have 3G here today, so no idea if this is some kind of interaction with 3G.
I don't see any correlation between this and the other thread where the phone ringer is going to zero volume. For me this is complete silence on the call in both directions, even though the phone says connected. When you dial a number, you don't even hear the ringback tone while the phone is ringing on the other end. The other person cannot here you.
One odd thing - I tried to play an MP3 file when the phone was in this state, and heard nothing. I toggled the system volume up and down, to mute, to vibrate, back to full, it didn't make any difference -- still no sound.
thedogger said:
I've had this happen twice on AT&T in the last two weeks with official released ROM 1.62.502.0, 1.27.14.09 radio. Both times it happened after I was in an area with sketchy coverage, then returned to good coverage. It was also in a 3G coverage area that would go back and forth between 3G and 2G.
I have a friend who has the same stock ROM and radio, AT&T Tilt phone, who this happens to all the time. He believes it happens when his phone goes to G, and then back to E. Typically that happens if you are close to losing a signal, the phone reverts to GPRS, then bounces back up to EDGE.
I just tried an experiment with some aluminum foil wrapped around the phone to attenuate the signal and bring it back, and couldn't reproduce it. But I don't have 3G here today, so no idea if this is some kind of interaction with 3G.
I don't see any correlation between this and the other thread where the phone ringer is going to zero volume. For me this is complete silence on the call in both directions, even though the phone says connected. When you dial a number, you don't even hear the ringback tone while the phone is ringing on the other end. The other person cannot here you.
One odd thing - I tried to play an MP3 file when the phone was in this state, and heard nothing. I toggled the system volume up and down, to mute, to vibrate, back to full, it didn't make any difference -- still no sound.
Click to expand...
Click to collapse
Yes, this sounds like exactly the same issue I am seeing. The volume drop to zero is something different - I can move the volume slider up and down when this happens and there is no audio in or out, the only resolution is to soft-reset.
At least it sounds like it isn't a faulty Kaiser
How do you go about raising this as an issue with HTC in an attempt to get them to fix it?
Cheers
Andy
I am also having this loss of sound issue. In a very unscientific test, I seem to have narrowed it down to my use of voice command. By any chance are you using voice command? I turned completely off via the settings and have not had the issue in almost a week. Prior to that it was almost a daily occurrence.
Yes, I have been using MS Voicecommand. Maybe there is a particular build at fault. Last time I had this problem was earlier today, with MS voicecommand 1.6.19209.Bengalih.
I'll try running without Microsoft Voicecommand at all in a fresh ROM for a while, see if that changes anything.
This sounds like the issue discussed here - http://forum.xda-developers.com/showthread.php?t=392606 - and here - http://forum.xda-developers.com/showthread.php?t=390977 - discussion in both threads have died for there was no solution found yet... I had to switch back to Hermes but still keeping the Tilt in the hope that there will be a solution that will bring it back into the usable state.
When I made the switch from the AT&T Tilt to the Fuze in December the one thing that I missed was a working GPS. I travel a lot and with the Tilt I could mount the phone in my rental car and by the time I was out of the lot everything was working. I never even thought about it.
As many of you know by now the Fuze GPS is, shall we say, challenged. Some people have worse results than others. Mine would usually get a fix but it took a while, and the lag was also an issue.
I tried various fixes that I found here and none of them did any good, they have all been removed now. I finally decided to bite the bullet and install the 1.12.25.19 radio that some people were raving about. I noticed very little, if any, improvement.
Then I tried the 1.14.25.05 radio. That was a big improvement. It could get a fix in places that even my Tilt couldn't and it got it quickly. I tried it in the car using Tomtom and was surprised that the lag was almost gone. I never looked at the Tilt this closely, it just worked, but it seems that now the Fuze is working as well as the Tilt.
I have seen reports here saying that 1.14.25.05 isn't as good as some others, but it is worth a try if you are already experimenting with radios.
For the record, I have the stock rom without bloat and started with the 1.02.25.32 radio. And I didn't change the rilphone.dll.
Now if we could just get the Tilt buttons onto the Fuze this device would be perfect.
sdbe said:
Now if we could just get the Tilt buttons onto the Fuze this device would be perfect.
Click to expand...
Click to collapse
ae button!
http://ae.inc.ru/aebplus.php
What part of the US are you in? I'm in Southern California, have the .19 radio and GPS fix is under 10sec when using Google Maps. However, it didn't improve my phone reception very much (my wife's iphone gets 1-2 bars more than I do). Curious to know whether it improved your phone reception at all?
sdbe said:
When I made the switch from the AT&T Tilt to the Fuze in December the one thing that I missed was a working GPS. I travel a lot and with the Tilt I could mount the phone in my rental car and by the time I was out of the lot everything was working. I never even thought about it.
As many of you know by now the Fuze GPS is, shall we say, challenged. Some people have worse results than others. Mine would usually get a fix but it took a while, and the lag was also an issue.
I tried various fixes that I found here and none of them did any good, they have all been removed now. I finally decided to bite the bullet and install the 1.12.25.19 radio that some people were raving about. I noticed very little, if any, improvement.
Then I tried the 1.14.25.05 radio. That was a big improvement. It could get a fix in places that even my Tilt couldn't and it got it quickly. I tried it in the car using Tomtom and was surprised that the lag was almost gone. I never looked at the Tilt this closely, it just worked, but it seems that now the Fuze is working as well as the Tilt.
I have seen reports here saying that 1.14.25.05 isn't as good as some others, but it is worth a try if you are already experimenting with radios.
For the record, I have the stock rom without bloat and started with the 1.02.25.32 radio. And I didn't change the rilphone.dll.
Now if we could just get the Tilt buttons onto the Fuze this device would be perfect.
Click to expand...
Click to collapse
I am in Central Florida where we have good reception almost everywhere. I didn't notice any difference among all three radios that I tried, reception was always the same, which was good.
One thing that I noticed about the 1.12.25.19 radio was that the gps was inaccurate. When I used google maps with my Tilt I could see what room in the house I was in. With the original radio, 1.02.25.32, it was almost as good, at least I could see that I was in the house. The 1.12.25.19 radio would sometimes put me 1/4 mile away from where I actually was. This even happened when I was outdoors. Tomtom seemed to be able to compensate for the errors but with Tomtom it would get 'lost' occasionally. 1.12.25.19 was my least favorite radio. The 1.14.25.05 radio is quick and accurate at least for me.
The 1.14.25.05 doesn't require anything to get an accurate fix. I used to have to use gpstest or some other program to 'prime' the gps. Now I don't have to worry about it. I just turn it on and a few seconds later it is working.
the gps issue has been resolved and proven over here http://forum.xda-developers.com/showthread.php?t=496800
princeasi said:
the gps issue has been resolved and proven over here http://forum.xda-developers.com/showthread.php?t=496800
Click to expand...
Click to collapse
Sorry, I tried it and it didn't do a thing for me with either of the first two radios that I tried. So I guess you could say that I proved that it doesn't work.
The strange thing about this problem is that what works for some doesn't for others.
For me the 1.14.25.05 radio made the gps work like it should have in the beginning. None of the other fixes had any affect. Also note that I used the original rilphone whereas others tried changing theirs. That may be why I had better luck.
At this point I have to say that the Fuze has a very good gps with little or no lag. That is not something that I would have said a few weeks ago. Everything on my phone is original except the newer radio. Maybe HTC discovered this but didn't advertise it.
Im using the stock fuze rom 5.08.502.1 with radio 1.12.25.19. If your looking to speed up the gps lock and have a similar setup, I would recommend using the gps hack first, before flashing a different radio, its much safer, Duces!
Thank you!!!
I can get a fix indoors!!
it was nice of you to share, you helped me a lot.
1.14 is better for me too.
second the original commenter
Both 1.12.25.19 & 1.14.25.05 worked fine for me. However 1.14.25.05 was slightly better. I am also using the registry hack and I set the poll interval to 500.
I recommend this radio to anyone facing problems with GPS.
Thanks for sharing.
This is strange. I live in central florida too, 1/4 mile away from cell phone tower and in the house I'm getting signal strength 2-3 bars, even if phone laying next to the window. From that window I would be able see the tower if it wouldn't be for the huge oak tree in front.
The GPS gets lock in about...5-15 MINUTES! and only outdoors.
With 1.12.25.19 radio I don't get better signal strength, but GPS locks in 10-20 seconds, even indoors.
GPS is definitely better with 1.12.25.19 radio. That radio is by far the champion in overall experience - GPS, GSM signal, HSDPA signal...
As someone already mentioned, it seems results can vary by user. I tried several radios after reading the suggestions on this forum. For my .02 it's the 1.14.25.05v. It gets me a really fast gps lock with usually about ten sattellites. Also, the RF is a little better, calls are clear and whats not to like. I'm stickin' with it.
My phone is a UK i9020t amoled running Android 4.0.4, baseband XXKL1
I'm having an issue where my phone has a total loss of radio after a period of time. This usually happens when the phone hasn't been used and I assume has gone into a period of deep sleep.
I had a look around the forums and whilst not conclusive there does seem to be reports from other users than deep idle is causing this issue. Before I had this problem I was using the Air Kernel v3 without deep idle and never lost service once.
The problem kernel was Air Kernel v3 deep idle test but I've also had the issue running CM9 with it's default kernel, which I later read has deep idle enabled.
Does anyone know if deep idle IS the cause of the problem, or any ideas how to fix?
I would like to also know if anybody with the same phone does not have this issue and if they could share the baseband they are using along with the kernel name.
Cheers everyone.
Deep idle will only be used while the phone is doing something (ie, playing music). While your phone is not in use at all, the phone should be in deep sleep. CPU Spy will show you how long you've been in deep sleep, NSTools will help you enable/disable deep idle (i believe it's disabled by default in all kernels, anyway?) as well as show you how many microseconds it was in each idle/didle state.
When you have low coverage next, open up settings -> about -> status -> mobile network type. Tell me what's listed and the signal strength dB reading. Then when you get good signal again, provide the same information. You may just have weak 3G around your area (like me), and the phone constantly switches between weak 3G and strong 2G.
Thanks. The problem doesn't seem to be caused by poor signal strength. The phone reports no network connected, status shows nothing for signal strength or network and trying to automatically connect to a network or manually just brings up an error message. Turning airplane mode on and off doesn't help bring the network back - I have to reboot the phone. It seems like the radio has crashed (to me, anyway)
Okay, i've seen this issue before but never experienced it myself, unsure if it ever got resolved. First thing i'd do is flash a new radio for your phone, maybe it doesn't play nice with your current one. For now at least, i think it's safe to rule out the ROM being the root cause but you never know.
Let us know how it goes with a new radio (fastboot flash radio radio.img - if you needed to know how to flash one). If you still have problems, do me a favour and take a screenshot of CPU Spy after a few hours of use and what the settings you have are in NSTools. Both are free from the market.
I've flashed KF1 radio and reflashed the air test kernel. I have both of those apps installed so when the issue happens again I'll grab those stats and paste them into here.
Thanks for the help so far. I appreciate it.
No problem, hopefully the new radio works. No point in the phone if it doesn't have somewhat reliable reception.
flibblesan said:
My phone is a UK i9020t amoled running Android 4.0.4, baseband XXKL1
I'm having an issue where my phone has a total loss of radio after a period of time. This usually happens when the phone hasn't been used and I assume has gone into a period of deep sleep.
Click to expand...
Click to collapse
Hi there. I'm using a Canadian i9020A. With any ROM, using either Glados or Matrix (both with deep idle on), I would get similar problems. Never tried any other kernels, so can't comment on whether it's deep idle related or just my bad luck. Usually being in a hospital where reception is poor, I would sometimes just lose my signal after a period of time and have to reboot to get it back.
Currently using a new kernel without deep idle. Will report back.
[edit] flashing radios has no effect and i always get a radio_dump when it happens in the sdcard directory
Update on this issue. Downgrading the radio to KF1 has made a difference. I haven't seen the problem since and I'm still using the Air kernel 3.0 test with deep idle. I consider this fixed.
This is the only reason I always keep a Radio by my side when Flashing a New ROM.
At least if my Mobile radio fails, I can always listen to the FM Radio.
LOL.
Gah spoke too soon. Managed to last 3 days but this morning the phone had a complete loss of cell radio. Had to switch off and back on again to get it to work. Seen posts suggesting this issue IS caused by deep idle so I'm disabling it.
sorry to bring this back up but i am having the same problem
fresh install of cm9 v3.4 with stock kernel (deep idle enabled, KL1 radio)
and when i go into the subways and then come out i have the same issue but the thing is it only happens sometimes.
anyways is this a deep idle or a bt patch fix issue?
and is there a fix
It shouldn't be either, but try disabling deep idle and see if you have the same problem. If you have no problems in a couple of days with it off it is obviously the cause. The btfix just sets an option in the framework that was default in GB, which they changed in ICS.
Harbb said:
It shouldn't be either, but try disabling deep idle and see if you have the same problem. If you have no problems in a couple of days with it off it is obviously the cause. The btfix just sets an option in the framework that was default in GB, which they changed in ICS.
Click to expand...
Click to collapse
Hmm I tried this yesterday as well. My phone lost signal through the night and I had deep idle on. This is actually my first time using DI so i was thinking it was just a normal reception issue. Will try it again tonight and update the forum tomorrow. If this is a major issue, I will stop using DI.
Anyway I am using the Matr1x 17 with CNA 1.4.0 on Smartarsev2/[email protected] 200/1000 (no modifications)
I'm using Matr1x 17.0 cfs with DI enabled. I can tell that it actually saves my battery life. I had no issue with losing radio/signal.
The only issue I have experienced with DI is when I played music with Google Music app. A little bit after the screen went off (maybe 5 - 8 minutes in), the music popped with a repeated distorted sound, the phone was not responding at that time. I had to pull the battery. I disabled DI and had no issue playing music with the screen off. I guess DI kicked in and Google Music didn't like it much.
I've had that happen to me once [email protected] (on stock music app), but since then i've done MANY 10-hour-straight benchmarks in the same situation, and more with real use. It seems to be a one off with me, and hopefully it's the same for you aswell. Obviously if it happens often it's not worth keeping it on, though.
You're right Harbb. It didn't happen all the time for me. But it was smart to happen at the most inconvenient time, like when I was running on the treadmil or working out. Had to stop and rebooted the phone. People were looking at me like "wtf, I'm waiting for you to get off so I can use it".
ashwin988 said:
Hmm I tried this yesterday as well. My phone lost signal through the night and I had deep idle on. This is actually my first time using DI so i was thinking it was just a normal reception issue. Will try it again tonight and update the forum tomorrow. If this is a major issue, I will stop using DI.
Anyway I am using the Matr1x 17 with CNA 1.4.0 on Smartarsev2/[email protected] 200/1000 (no modifications)
Click to expand...
Click to collapse
Yeah, this just happened for the 2nd time just now on DI. rebooted my phone but since I am overclocked at 1460, i really need DI so that my bat does not die off. Sigh, I would just need to monitor my phone more and I really hope this gets fixed.
Was having random signal drops and what seemed to be battery issues. Called T-Mobile for a replacement, but it seems all the issues disappeared. Should I swap it anyway or keep the original with the low h boot?
Mine was doing the same. Then i found out it keep going to Airplane mode turning off. So i had to restart or turn on and off airplane mode. Once i changed the rom on my phone it stopped.
davwman said:
Was having random signal drops and what seemed to be battery issues. Called T-Mobile for a replacement, but it seems all the issues disappeared. Should I swap it anyway or keep the original with the low h boot?
Click to expand...
Click to collapse
If you know what made the issues go away, just keep the one you have.
I can't comment on your battery issues, but for me the cell signal is way more stable since radio 1.06s. Still not very strong, but not as jumpy as it was before.
If it's really a mystery, and you think your issues might suddenly come back, get the replacement, altho that's no guarantee either. Do you know which HBOOT a new one would come with?
-Jobo
Well boot is 1.09 on the one I'm using. Not sure what the replacement is yet because I don't have it in my hands yet. I'm running the EU radio and signal stopped dropping and battery got better. There are way to many factors that could have solved it