Related
Hi,
Sometime today I lost my phone signal on my SG2. I'm not sure exactly at what moment as I first noticed that I had a couple of bars but no 3G when I tried to browse the web. So I restarted the phone but to no avail. Since then I've lost all bars and can't make any calls either.
The only thing I have done today "out of the ordinary" was to connect to the phone using Wifi File Explorer to transfer a file, which I tried to connect to without being on a wifi network by first trying the "Wifi Direct settings" in Settings, which didn't work, and then by tethering by Wifi which worked. Maybe some setting got stuck in the process, but I'm not sure since never checked if it worked right before and after.
If anyone has any idea what could be wrong please let me know, as I am literally without a phone!
I recommend downloading http://www.androidzoom.com/android_applications/communication/no-signal-alert-pro_fyyo.html this will definitely be of benefit to you if your suffering from signal problems, it has been of good use to me.
Check your IMEI is the correct one for your phone .If not restore your backed up EFS folder .
Or try backup data and factory reset as a first step.
jje
Thanks for the quick replies!
The IMEI does not correspond to the one I have written down, though I'm not 100% I what have on my note is the latest IMEI; but how could that change though by itself, if my note is correct??
Also, I just saw something very strange: I turned on my phone and had full bars (no 3G though), and right in front of my eyes all bars dropped, one by one, during the course of 5-6 seconds. Something is VERY off...
Regarding factory reset: my phone is rooted (thanks to XDA!) and I have Tit.backup: can I will my phone still be rooted if I do a factory reset?
Something went probably wrong when rooting it (not neccesarily any errors) and effed up tge EFS folder.
Try to flash back to stock ROM, it might work to restore your.folder.
Sent from my GT-I9100 using xda premium
UPDATE
bruflot said:
Something went probably wrong when rooting it (not neccesarily any errors) and effed up tge EFS folder.
Try to flash back to stock ROM, it might work to restore your.folder.
Click to expand...
Click to collapse
I should have been more clear on that, but I rooted the phone about a month ago and it has worked flawlessly since then, so it couldn't be that.
Anyway, I looked around a little and found this post:
http://androidforums.com/samsung-ga...connectivity-but-no-idea-why.html#post2722784
He seemed to have had the exact same problem that happened to me, so I decided to wait, and sure enough the connection reestablished itself about an hour ago and while I was watching for it, with the signal slowly creeping back up during a couple of minutes, and several hours after I lost it. Very odd.
This surely has to be an Android bug but that only shows up under certain and rare conditions.
To be sure I made a speed test and got 4.84 Mbps/up, 1.19 down, which I guess is fine; I never did one prior to this so I have nothing to compare to.
Again, appreciate the advice!
EDIT: For posterity, I should add that during these hours, even when I briefly apparently had a (non-3G) signal, I had a notification during all this time saying that I could only make emergency call.
I'm having the same issue. No Bars at all most of the time and when I have some, it never connects to 3G, G at most, and can't load any thing at all.
Very frustrating. I have been using Lite'ning rom 6.1 for a few months and had no problems at all until about a week ago.
I flashed back to a stock rom and still having the same issue.
I've also seen the bars drop down one by one in a 5 second window, bizarre!
Anyone find a fix for this? Or could the phone be faulty?
malicedix said:
I'm having the same issue. No Bars at all most of the time and when I have some, it never connects to 3G, G at most, and can't load any thing at all.
Very frustrating. I have been using Lite'ning rom 6.1 for a few months and had no problems at all until about a week ago.
I flashed back to a stock rom and still having the same issue.
I've also seen the bars drop down one by one in a 5 second window, bizarre!
Anyone find a fix for this? Or could the phone be faulty?
Click to expand...
Click to collapse
I was on Lite'ning about 3 weeks ago and actually completely lost signal several times. Reboots and hard resets solved the problem temporarily. I then flashed Batista FH 2.4 with ICS and things were great. I'm now on GingerMod. No issues.
I don't know how it could be kernel related though, especially if you are 100% stock again.
Ok, so here's the scoop.
Earlier today for no reason that I can pinpoint I lost all Cellular connectivity on my photon while at work. No calling, no 3G, etc. I figured it was just a hiccup or possibly that they where working on the towers in my area and that it would eventually just come back up.
That was over 12 hours ago, and I have already traveled from work, to home and still no change.
I began to think that maybe my PRL was out of date, so I flashed back to a blur based Rom that has worked for me in the past (I normally use CWM7.2 and moved to Imperium_Initiative_v1.0.5 to try and do this) and tried to initiate the update there.
Still, no results. Not only would the PRL & profile not update but I got a general "NETWORK_ERROR" every time I attempted to do so.
I'm getting a little desperate because I really need to have my phone active for work and other reasons.
I've already restored old NAND backups, restarted the phone numerous times, and so far nothing is working...
If it is indeed a PRL issue, is there a way to manually flash an updated version onto the phone?
Any help that anyone can offer is greatly appreciated!
-Timboman
P.S. The only major change that has been made to the phone recently was I purchased a new extended battery about a month back. It's been working great since I broke it in, and have no so much as flashed a new rom image since I got it. It's the Trexcell Motorola Photon 3570mah Extended Battery.
Well I decided to bite the bullet and do a full re-lock and stock re-flash and I now have gotten my signal back.
Still have no idea why it happened to begin with, but I have apparently solved my issue.
If anyone can give me a reason this might have happened then at least this topic can be of future use to someone else.
-Timboman
Timboman said:
Well I decided to bite the bullet and do a full re-lock and stock re-flash and I now have gotten my signal back.
Still have no idea why it happened to begin with, but I have apparently solved my issue.
If anyone can give me a reason this might have happened then at least this topic can be of future use to someone else.
-Timboman
Click to expand...
Click to collapse
This happened to me once while on cm7, again, for no apparent reason. After being baffled for an hour i got pissed and went to bed thinking my radio died. Signal was back by morning. Id be willing to bet yours would have come back too. Pawn it off as a hiccup and keep flashin stuffs.
Sent from my MB855 using XDA
So after flashing Cookies and Cream 4.1.2 and working fine for a few days, Calling and texting stopped working. I flashed an ICS Rom and it worked again, for 1 call. Midway the call dropped and everything stopped working again. Phone still gets signal, data works and everything else too. I clean flashed 3 different stock ICS roms with TWRP, nothing is working. Any ideas as to what could have happened?? Im thinking I can only fix it by flashing stock image with ODIN, but im curious as to what could have gone wrong. Im thinking maybe the IMEI got screwed up?? But the symptoms dont really seem like that would be the issue. Any help would be greatly appreciated!!
H0rn3t920 said:
So after flashing Cookies and Cream 4.1.2 and working fine for a few days, Calling and texting stopped working. I flashed an ICS Rom and it worked again, for 1 call. Midway the call dropped and everything stopped working again. Phone still gets signal, data works and everything else too. I clean flashed 3 different stock ICS roms with TWRP, nothing is working. Any ideas as to what could have happened?? Im thinking I can only fix it by flashing stock image with ODIN, but im curious as to what could have gone wrong. Im thinking maybe the IMEI got screwed up?? But the symptoms dont really seem like that would be the issue. Any help would be greatly appreciated!!
Click to expand...
Click to collapse
Try flashing a different modem?
H0rn3t920 said:
... Im thinking I can only fix it by flashing stock image with ODIN, but im curious as to what could have gone wrong? ...
Click to expand...
Click to collapse
That's what I would do...then take it back for warranty repair. Extremely unlikely any ROMS caused this problem.
crutzulee said:
Try flashing a different modem?
Click to expand...
Click to collapse
It sounds like you have a modem that isn't compatible. Many times it will still catch a strong signal, but your sound, if there is any, will be garbled. I would try flashing a couple of different ones and make a test call with each to find what you like and works.
Sent from...
I've got 2 I717 with that problem, good signal 'Not Registered On Network'. I think it's a hardware issue. I've seen more than a few posts about it now. I've tried everything to correct this, I have a good IMEI.
H0rn3t920 said:
So after flashing Cookies and Cream 4.1.2 and working fine for a few days, Calling and texting stopped working. I flashed an ICS Rom and it worked again, for 1 call. Midway the call dropped and everything stopped working again. Phone still gets signal, data works and everything else too. I clean flashed 3 different stock ICS roms with TWRP, nothing is working. Any ideas as to what could have happened?? Im thinking I can only fix it by flashing stock image with ODIN, but im curious as to what could have gone wrong. Im thinking maybe the IMEI got screwed up?? But the symptoms dont really seem like that would be the issue. Any help would be greatly appreciated!!
Click to expand...
Click to collapse
I am having similar problems and after weeks of flashing (ROMS and modems) to no avail, I am going to take my phone in and get a refurb.
I would reflash a stock ROM with Odin, then flash a custom ROM of your choice and the radio(s) that work for your carrier and check the APN setting. If none of that helps, it may more than likely be a hardware issue and would need to be fixed.
Depending on your carrier you can just warranty your phone as a hardware problem. If they refuse because you flash your phone I have yet to hear of Samsung refusing service or warranty because of it. My note stopped working and I have flashed tons of modems & roms, no questions asked it was fixed and back in my hands in 5 working days.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
AT&T's Device Support Center(s) can replace your phone on the spot so long as you're within warranty and they can duplicate the issue after a factory reset/OS flash.
wasnt this version released February 2012? Then shouldnt any i717 qualify under the Samsung 1 year warranty. I'm having the same problem with mine while trying to connect to Mobilicity in Canada. Doesnt help that it drops the Wifi connection every now and again for no reason.
Making me wonder why i just got rid of my S2X yesterday for
Warranties don't start the second the device comes off the assembly line.
The warranty goes into effect on the date purchased, so yes every single I717 falls under the oem warranty.
Shirokishi said:
wasnt this version released February 2012? Then shouldnt any i717 qualify under the Samsung 1 year warranty. I'm having the same problem with mine while trying to connect to Mobilicity in Canada. Doesnt help that it drops the Wifi connection every now and again for no reason.
Making me wonder why i just got rid of my S2X yesterday for
Click to expand...
Click to collapse
Good grief, I was speaking in general terms. AT&T's MDS terms apply to any phone you buy from them.
I've had issues where voice has been lost and nothing can fix it except a reflash. Happens on my sII and the gnote. Luckily I'm able to fix it but I'd rather it never happen.
As the title suggests, suddenly I started getting force closes with com.android.phone when I'd receive a call. I immediately tried to call out, same story. I've been troubleshooting for the past few hours, and had no luck finding anything relevant on XDA or any other site.
Firstly I switched kernels, since I'd updated to DSB's latest, though I'd had no issues with it until then. That failed, so I reverted to Viper's stock build.prop, undoing some changed I'd been running for a while (and hadn't modified at all today).
With no luck there, I backed up my sdcard and did a full factory reset and formatted the sdcard in twrp and then in cwm, followed by a reinstall of the latest Viper ROM. Even that didn't work, so I relocked and RUU'd back. Twice. Same exact issue. I can text anyone just fine, data over LTE goes on as normal, but anytime I try to make a call, be it with the stock dialer or through a diff one from the play store (for kicks, last resort). I reseated the SIM card a multitude of times, to no avail. I get full functionality with my SIM in my other phone, so I'm sure it must be the hardware itself on the phone. Every time com.android.phone stops, the SIM initialization happens like when you physically re-seat the SIM.
The troubling thing is that I haven't done anything, save for a simple kernel and recovery update, which would've been negated by two RUU runs to stock. I haven't touched the SIM card or anything, at least until that started happening. Furthermore confusing is how all other functionality can remain except for actually making phone calls.
Removing the SIM entirely and dialing a number does the exact same thing, just as an FYI.
Has anyone seen this? Any ideas?
As I've unlocked my phone, my last resort is to go into a VZW store and act like an idiot so they don't check to see if i unlocked it. Further complicating that is the fact that the DNA was actually purchased on my own account, which I closed, and brought to an unlimited data line that was preexisting. I'm half tempted to wait for the official OTA and see if that will remedy the issue, but my fear is this may be a physical issue beyond the remedy of a firmware update.
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
ergotelis said:
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
Click to expand...
Click to collapse
thanks for the thread, for the life of me i couldn't find anything exactly relating to what i described. that is spot on though, and def makes me feel a bit more at ease that maybe it can be resolved with an update to the firmware that's due soon.
yea, the funny thing is that it worked flawlessly, i never even got the SIM error message, i'd been texting my gf, a few friends, and my parents and then my pops called in the evening and it immediately closed out the call before it really even rang. i called him right back and that's when the force closes started happening, calls never working agian thereafter. however, i was able to still text everyone i was before and data was working flawlessly as always, just no calls, not even after all the crap i did to troubleshoot.
the update is hopefully going to be out soon. the support documents came out a few days ago. i def can't survive on this galaxy nexus after having used my DNA since launch!
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
ergotelis said:
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
Click to expand...
Click to collapse
The update is out now, can someone send it to me too? I am overseas, trying to find a way to download it.
OP, can you test this one to see if you get a fix?Thanks!!!
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
After saying all that I just got the new update from Verizon. I assume I shouldn't flash this since I'm on a custom rom.
Sent from my Nexus 7 using xda premium
Thanks for the input, really interesting!Will try it right away! Hope you won't have any problems with the update now!
msturner79 said:
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
Click to expand...
Click to collapse
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
ergotelis said:
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
Click to expand...
Click to collapse
Hi guys i got a similar problem. My DNA was perfect since yesterday but now i can use data connection for internet. All the other stuff is working fine....SMS,call, wifi, the only thing that is not working is the 3g data. All of this problem came when i flashed the viper DNA, so i flashed the supercharged hoping it was an issue of the rom. Olso with the supercharged the problem was always here.... So i decide to came back to stock and i re-lock my bootloader and flasched stock RUU. But data connection is still not working :crying:
can anyone please tell me what can i do?
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
As I've unlocked my phone
ergotelis said:
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
Click to expand...
Click to collapse
yes but notthing changed.... :'(
Now i'm compleatly stock and the problem is still here.
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
ergotelis said:
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
Click to expand...
Click to collapse
Which version of viper worked for you?
hard problem
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
jimmydee62 said:
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
Click to expand...
Click to collapse
Still broke?
Sent from my HTC6435LVW using xda app-developers app
kaliblazin707 said:
Still broke?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it is still broke I just don't know what to do at this point paper weight right now.
Been having a problem with Task's latest ROM (4-14) and the previous version (4-1). Both take several minutes to obtain carrier signal (AT&T) after booting. I've tried flashing with full wipe several times, different modems, and adjusting APN settings, but nothing fixed it. My phone usually picks up service after about 5 minutes, but sometimes I've waited 10+ minutes and had to reboot again, because it still hadn't connected. Also, maybe this is just how it's supposed to work, but I've noticed that while my phone has no service, if I go to System Settings->More->Mobile networks->Access Point Names there's nothing there at all. Just a blank window until it finally connects. Is anyone else having this problem or know of any possible solutions? Thanks!
Samsung Galaxy S II SGH-i777
Android Version: 4.2.2
ROM: Task650
Build: 4.14.2013
Modem: UCLL6
Have you tries rebooting with airplane mode enabled and then disabling it when fully booted? This has worked for me in the past, although I've never had to wait as long as you've stated you have for a signal.
Phalanx7621 said:
Have you tries rebooting with airplane mode enabled and then disabling it when fully booted? This has worked for me in the past, although I've never had to wait as long as you've stated you have for a signal.
Click to expand...
Click to collapse
I tried this method and it didn't work for me , I even did a complete wipe and re-flashed the rom and gapps, I also re-flashed two separate modems amd was never able to connect to the mobile network. when I first flashed the ROM everything worked great, but when my device went to deep sleep it never came back
Phalanx7621 said:
Have you tries rebooting with airplane mode enabled and then disabling it when fully booted? This has worked for me in the past, although I've never had to wait as long as you've stated you have for a signal.
Click to expand...
Click to collapse
Thanks for the advice, but it's a no go. I reboot with airplane mode enabled, but when I disable it my phone still takes forever to get a signal.
maninblack86 said:
Thanks for the advice, but it's a no go. I reboot with airplane mode enabled, but when I disable it my phone still takes forever to get a signal.
Click to expand...
Click to collapse
I have the same problem despite wiping everything many times. mine take approx two minutes to get back the signals and meanwhile emei and baseband remains unknown.
chacha123 said:
I have the same problem despite wiping everything many times. mine take approx two minutes to get back the signals and meanwhile emei and baseband remains unknown.
Click to expand...
Click to collapse
Mine does exactly the same. Baseband is unknown and there's no IMEI info until it finally connects. I also noticed that under service state it said "radio off" until it connects and then changes to "in service".
That's very odd. It's not just this rom it does this on is it?
Phalanx7621 said:
That's very odd. It's not just this rom it does this on is it?
Click to expand...
Click to collapse
I went to the Jedi ROM with no issues....I've used tasks ROM since its infancy and never had one issue until this latest update. Kind of bummed. But in the same hand I'm liking the Jedi ROM also...:thumbup:
Phalanx7621 said:
That's very odd. It's not just this rom it does this on is it?
Click to expand...
Click to collapse
Yeah dude, I've been using Task's ROM for a while now and this has only started happening since the 4-1 version. I even flashed back to the 3-13 build just to make sure and this problem doesn't happen with that build. I was hoping the 4-14 build would fix it, but it didn't. I did see on Task's developer thread someone made a post about having this issue, but it looks like they never posted a logcat or anything to help Task resolve it. I would gladly post one if I could, but I'm new to XDA and they won't let me post on a developer thread.
i have same issues. along with my time going screwy from time to time.
phermey said:
i have same issues. along with my time going screwy from time to time.
Click to expand...
Click to collapse
I no longer have any issues with the time zone changing in the newest build (4-14). I don't know if you're on that build, but the workaround for that problem was to set your own time zone manually.
maninblack86 said:
I no longer have any issues with the time zone changing in the newest build (4-14). I don't know if you're on that build, but the workaround for that problem was to set your own time zone manually.
Click to expand...
Click to collapse
i am still on 4.1. i am not prepared for a full wipe yet.
Apparently, what's happening is the radio doesn't turn on during boot (Radio baseband not recognized error or something). I fixed this problem by turning on the wifi temporarily then turning it off. Apparently this will turn on the radio and should stay that way. I hope this works for you.
epicstar1 said:
Apparently, what's happening is the radio doesn't turn on during boot (Radio baseband not recognized error or something). I fixed this problem by turning on the wifi temporarily then turning it off. Apparently this will turn on the radio and should stay that way. I hope this works for you.
Click to expand...
Click to collapse
That worked dude, thanks! It took me a couple tries, I probably didn't give my phone enough time to boot, but I got it. Definitely a lot faster than waiting for it to connect on it's own.
I wonder why this only seems to affect some of our phones, but not the majority? If I didn't know any better, I'd say it almost seems like they have slightly different hardware. I bought mine directly from AT&T the first week it was released. Don't know if they possibly made any hardware revisions since?
phermey said:
i have same issues. along with my time going screwy from time to time.
Click to expand...
Click to collapse
Did you try turning off the "Automatic Time Zone" option in the Date & Time settings? My phone always sets the time to GMT+0 when I have that turned on.
maninblack86 said:
That worked dude, thanks! It took me a couple tries, I probably didn't give my phone enough time to boot, but I got it. Definitely a lot faster than waiting for it to connect on it's own.
I wonder why this only seems to affect some of our phones, but not the majority? If I didn't know any better, I'd say it almost seems like they have slightly different hardware. I bought mine directly from AT&T the first week it was released. Don't know if they possibly made any hardware revisions since?
Click to expand...
Click to collapse
I have been having this problem as well.
Yesterday I did another wipe and reinstall. I did a full wipe (and in mounts formatted everything except my external SD which was temporarily removed.) after flashing the rom, I rebooted recovery and did another wipe data/factory reset and wiped dalvik, then I installed gapps. I then formatted the cache and data again and rebooted the phone. It seems to have fixed the issue for me.
Kasdarack said:
I have been having this problem as well.
Yesterday I did another wipe and reinstall. I did a full wipe (and in mounts formatted everything except my external SD which was temporarily removed.) after flashing the rom, I rebooted recovery and did another wipe data/factory reset and wiped dalvik, then I installed gapps. I then formatted the cache and data again and rebooted the phone. It seems to have fixed the issue for me.
Click to expand...
Click to collapse
Thanks for the suggestion, but this didn't work for me. Tried it exactly as you said, but still have the problem.
phermey said:
i have same issues. along with my time going screwy from time to time.
Click to expand...
Click to collapse
Same issues here, Ive just resorted to manually entering the time zone, but no solution for the delayed connection.
Caligula36 said:
Same issues here, Ive just resorted to manually entering the time zone, but no solution for the delayed connection.
Click to expand...
Click to collapse
Known issue for months now about the time zone. And apparently some others have experienced a longer than normal connection delay too. Weird.
maninblack86 said:
Been having a problem with Task's latest ROM (4-14) and the previous version (4-1). Both take several minutes to obtain carrier signal (AT&T) after booting. I've tried flashing with full wipe several times, different modems, and adjusting APN settings, but nothing fixed it. My phone usually picks up service after about 5 minutes, but sometimes I've waited 10+ minutes and had to reboot again, because it still hadn't connected. Also, maybe this is just how it's supposed to work, but I've noticed that while my phone has no service, if I go to System Settings->More->Mobile networks->Access Point Names there's nothing there at all. Just a blank window until it finally connects. Is anyone else having this problem or know of any possible solutions? Thanks!
Samsung Galaxy S II SGH-i777
Android Version: 4.2.2
ROM: Task650
Build: 4.14.2013
Modem: UCLL6
Click to expand...
Click to collapse
I have the same problem. I have been using Task's ROM for a few months now and I never had any problems.
updated to version 4-14 and was enjoying it until today. Lost my phone service, for some reason the IMEI got corrupted...I don't even have the access point names choice in mobile networks...no amount of rebooting fixed it...had to flash the phone with a backup file and so far its doing fine..