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.
Related
This has been happening a lot lately. Sometimes I'll look down at my phone and the signal bars will completely drop for a second, and then go back to normal. I am in an area with full-coverage. This happens anywhere I go in Connecticut.
I am rooted, running Das Bamf Remix, the Adrenalyne Kernel 4.4.3, and Jcase's radio combination #2.
Any other settings I should check to diagnose the problem?
This is becoming an issue because people are telling me my phone "goes straight to voicemail" at times. Any help appreciated.
I see this happen when the phone switches between 1x, 3G, and 4G, but haven't noticed it any other times.
Did it happen when you were stock?
g00s3y said:
Did it happen when you were stock?
Click to expand...
Click to collapse
No, it was never a problem back then
I seem to be having the problem as well now, again. Its pretty annoying.
Could it have anything to do with underclocking and/or using SetCPU profiles?
EDIT: I haven't noticed it happening since I disabled profiles in SetCPU..
First and final bump. Contrary to my last post, it's still happening.
Anyone else see this phenomenon?
Yes I do all the time. I also notice that sometimes data will stop and then 4g restarts and I'm back to normal. Doesn't matter which kernel.
Sent from my ADR6400L using XDA App
I have been experiencing problems with this too. My data connection has been on and off today. I'm totally stock right now btw since I just got a replacement.
This happens to me quite a bit. I rooted yesterday but am still stock and it happened before and after root.
I see this happening most when my phone's been sleeping for awhile and I turn on the screen. It'll have 0 service bars the first second the screen is on but then goes right back to where it's supposed to be a second after. Hasn't affected my syncs or push mail.
I came in here just to look if someone had a similar problem
I have been noticing this too, happens when I get home on the outskirt of 4g, but solid 3g. I only show the bars but says I have no signal. usually a reboot fixes it but it is annoying
running bamf stripped 1.7, never had my phone stock long enough to know if it happened then
I don't live in 4g area (thanks raleigh) and I have had this issue since I got the phone launch day
Just wanted to add that the problem consistently happens when I wake the screen. I can see the bars QUICKLY go from full to 0 (on wake). Then after I unlock and wait a second the bars come back.
I've just noticed it today, I thought it had something to do with the new radio. I've had the TB since launch day but just noticed it now...
I'm currently using InsertCoin 3.4.3 along with bricked kernel 1.5, with no real issues to mention other than poor battery life and the odd force close or lockup when first turning the phone on. After pulling the battery and rebooting it's then fine for some reason.
Anyway, I was on InsertCoin 3.4.2 until last night when I installed the bravia addition to make it 3.4.3. Since then, my battery life hasn't faired as badly as it has been over the past few days, but today I've noticed an issue with my wifi.
When first turning the phone on, wifi works for a bit. Then after a while it just drops connection and can no longer see any networks. If I go into the network menu screen all it shows is that wifi is still turned on, shows my remembered networks, but keeps sasying it's unable to scan for networks. This is obviously preventing service, but does anyone know why it's happening? If I pull the battery and reboot the phone it'll work again, for a bit and then the problem returns...
try latest faux kernel and not to say bad things about bads rom but there are better devs and roms around try rc mix its far better!
I've already tried the faux kernel and the phone ran red hot. Not tried any other roms yet though.
Restoring a backup of 3.4.2 has sorted it, so there must be an issue with the insertcoin bravia addition.
Sent from my HTC sensation using Tapatalk
After running this a few days, I'm really not happy with whatever changes Samsung has made. Not only have the NOT resolved the now infamous "SOD" issue, but they've created new problems (at least for me) with wifi.
I usually keep my wifi "sleep policy" set to "never when plugged in." For every device I've owned, this would keep the wifi turned on and connected if my device was power on (display on) or the device was plugged into AC power. I've never had any problems with it.
With this latest firmware update, however, it keeps dropping the wifi connection while the device is turned on (screen on.) I'm sitting literally 20 feet from the AP, and there are 4 signals for the device to choose from (2 2.4GHz channels and 2 5GHz channels.) However, for some reason, it decides it just doesn't want to be connected to ANY of them. The wifi radio is still enabled, but it won't connect (or even see) any AP.
Samsung: I don't know what you THINK you may have fixed with this latest firmware update, but you not only failed to correct the most prominent issues people are having, but you've already created at least one new one.
I'm going back to KL1...
Gary
I got the notification of the new firmware update and was looking for what this update about. Thanks for posting here... I am now holding on the update...
I am also going to hold off on the update. Thanks Gary for all your do.
Sent from my GT-P6210 using Tapatalk
mine stops checking for update.. cannot get the "Update" stuff to work.. probably a good thing for now..
My Wifi works fine with LA3...
I'm a happy camper
My WiFi is also working fine with LA3. I was actually having a minor issue with the last firmware where the WiFi would occasionally not follow the WiFi sleep policy I had chosen. I had it set to never sleep but every once in awhile (very randomly) when I brought the tab out of sleep, I found that the WiFi had also gone to sleep. I have had LA3 on my tab for 2 days now and so far so good. It has adhered to the WiFi sleep policy I have set but 2 days is not a good indication that the issue I had been experiencing with the last firmware has been corrected in LA3. I am going to give it a few weeks before I say one way or the other if the issue still exists or not. But as I said, so far so good for me.
garyd9 said:
After running this a few days, I'm really not happy with whatever changes Samsung has made. Not only have the NOT resolved the now infamous "SOD" issue, but they've created new problems (at least for me) with wifi.
I usually keep my wifi "sleep policy" set to "never when plugged in." For every device I've owned, this would keep the wifi turned on and connected if my device was power on (display on) or the device was plugged into AC power. I've never had any problems with it.
With this latest firmware update, however, it keeps dropping the wifi connection while the device is turned on (screen on.) I'm sitting literally 20 feet from the AP, and there are 4 signals for the device to choose from (2 2.4GHz channels and 2 5GHz channels.) However, for some reason, it decides it just doesn't want to be connected to ANY of them. The wifi radio is still enabled, but it won't connect (or even see) any AP.
Samsung: I don't know what you THINK you may have fixed with this latest firmware update, but you not only failed to correct the most prominent issues people are having, but you've already created at least one new one.
I'm going back to KL1...
Gary
Click to expand...
Click to collapse
Oddly enough, I'm not experiencing that. Never when plugged in works correctly for me. It also manages to turn off the wifi when the screen is off while I'm on battery, which is an improvement over the previous firmware. I did experience two SODs in the two days after upgrading, but they have since stopped. (I'm not using Auto Airplane Mode anymore, so I'm quite pleased with that.) Are you now experiencing the SOD with the new firmware, because if I remember correctly, you weren't experiencing it on your tab with the previous firmware. Also, I'm wondering if whatever was keeping your tab from experiencing the SOD with the last firmware is causing your issues with this one. Nevertheless, I'm sorry you're experiencing issues. If there's anything I can do to help, pulling logs or testing, I'm more than willing. Good Luck
@garyd9 Could you send me a link to the firmware of KL1? I'm having problems with LA3 and root and busybox. I'm trying to revert it back and try again but couldn't find the link of firmware. Thank you!
At least one of the things it does is stop the phone going into the deep sleep. Based on CPU spy my phone had no deep sleep at all. When I turn it off my phone started going to deep sleep.
Not using that feature again. Good to know. Try it yourself.
Sent from my HTC One X using Tapatalk 2
This may in fact be the issue I have been having. After around an hour or so (seemed to vary) the WiFi seemed to stop working. The WiFi symbol was still there and even doing a ipconfig check all the "numbers" came back correct yet there really was no connection.
I am going to give this a try and really hope it works. This issue has had me contemplating returning the phone, which I really don't want to do.
Funny thing is, if this works it was not part of the solution that HTC recomended me trying to fix the problem.
Maybe this is connected to the push notification problems that the phones are having while on WiFi.
Sent from my HTC One X using Tapatalk 2
I had that option checked and I noticed my battery life sucked. When checking usage I saw "Android OS" had used 25%. I turned it off and it dropped to 5% or less
After turning this on last night I have not had to "toggle" the WiFi on and off like I had to do before. I am not quite convinced this fixed the issue but it seems to have a shot.
Only weird thing is after leaving WiFi on all night I checked the battery status to see what was using it and there was a large gap of the WiFi not using any battery but again I never had to toggle so I guess I am not sure what that means. Was the WiFi off during that time and I would have received no emails etc... Or was it really connected.
I am wondering if any of this may also have to do with my router. My previous phone would also loose connection to WiFi but no where near as often. However my other devices using WiFi (PS3, GoogleTV, TV. etc..) have never had an issue of loosing connection. So I am sticking to it is the phones fault
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