Every since flashing back to a stock/asop-look room from 4.2 aokp, my phone has not left extended network. Any ideas how to fix? I even downloaded the new eclipse and installed it. Still the same. I live am in a major city if that comes up and have never been in extended network where I live or work.
Related
At least that's what I think is the cause. It almost always happens when I'm outside so I haven't been able to catch one while running logcat. I've tried both the 10.14.9035.01 and 10.15.9035.02 radios with RILs matched and unmatched, stock ROM and CM7 both after running SuperWipe script, stock kernel and faux's AOSP kernel, and changed to a new SIM card, all with the same result. Any ideas or should I just try to return it and get a new one (I really want to avoid this as I travel a lot and can't wait for a new phone)?
It all began around the weekend of Dec 2 around the time I started using 3G. Before that I was only on the 2G network.
Setting GSM only or WCDMA only seems to remedy the problem but of course WCDMA coverage isn't available everywhere so that sucks. Am I the only one with this problem?
No, I guess not. I had a problem somewhat like it. My device turned itself off a few times a day. Had sent it to HTC for a firmware update, tried a new SIM and heard many horrorstories on the device shutting off without the user wanting it.
Since I disabled automatic network detection the problem hasn't occurred again. At least for now.
Where do I disable automatic network detection?
I am not quite sure but I think it's on wireless settings > Mobile network Settings > Network operators > and then from Search networks try selecting a network manually Sorry I don't really know but I know where this option is
I have a Telus SGH-T959D Samsung Galaxy Fascinate, and I recently flashed it from stock Gingerbread to SlimICS, using Semophore 1.3 kernel. Phone was working about 95% stable (had to flash a modem, had no data/cell), but battery life was fairly short. I decided to try out using Glitch v14 kernel instead as it seemed to be designed for this specific model of phone (well, the release under the link for this phone). I ran a kernel cleaning script, then loaded Glitch. Seemed to work flawlessly, a bit faster with slightly better battery life. I then started playing around with the ROMs built in power saving which allows for adjusting the data settings while the screen is off (similar to juice defender, just built into the rom). Initially it worked fine, but after about a day I was noticing that when I woke my phone there was no cell reception. I went into the phone Usage Stats (*#*#4636#*#*) and under Phone Info I noticed the 'Set preferred Network type' was set to 'GSM Only'. As far as I know, in Canada, the typical network type is WCDMA, so I set it back to that, and cycled the radio on/off. I can get it back for a while sometimes when I do this, however the setting doesn't seem to save at all and when I put the phone to sleep it typically doesn't wake up with signal. I then have to repeat the process.
Is there somewhere that these settings are being stored in a file on the phone that can be text edited and saved? Maybe write protected? Or is there some other kind of fix that anyone might be able to help me with?
Thanks!
Edit: I did disable the power saving feature in the ROM, but it didn't make a difference.
I've only run AICP nightlies but I heard this is a widespread issue from another user on AOSP ROMs. Sometimes my clock changes like I'm in another time zone and my data drops out until I toggle airplane mode (not at the same time). I love AOSP and hate going back to TW but I missed an important alarm this morning. Is there any fix or ROM this doesn't happen with? Both issues seem related maybe considering the time is from the network. TIA!
I have had the time zone issue quite frequently on different AOSP based ROMs. Just go into your date and time settings and manually specify the time zone (you can still leave date on auto) and it should correct that issue. In terms of data dropping, some people have tried flashing this but it never really improved signal for me. Try running one of the newer Blisspop builds, it has been working for me switching between lte and 3g and I have data connectivity 99% of the time.
Dopamin3 said:
I have had the time zone issue quite frequently on different AOSP based ROMs. Just go into your date and time settings and manually specify the time zone (you can still leave date on auto) and it should correct that issue. In terms of data dropping, some people have tried flashing this but it never really improved signal for me. Try running one of the newer Blisspop builds, it has been working for me switching between lte and 3g and I have data connectivity 99% of the time.
Click to expand...
Click to collapse
I've tried flashing blisspop and it says to insert sim at startup and then no service on my phone
Hi. I'm using a Verizon XT926 (HD MAXX model) which recently had an issue so I reflashed it with a more recent ROM - tried SlimKat, Resurrection Remix and CM11 unofficial versions. Also, I'm in Europe (Finland) using this.
All had issues with Google Now bar causing crashes quickly after booting (mic issue?), so I went for a PICO install of only basic Google stuff, and manually added the bits I wanted (not bothered with Now anyway, so no problem), and ended up with stable builds. I settled on the CM11 unofficial version in the end as it seemed most stable - cm-11-20160618-UNOFFICIAL-moto_msm8960
The other consistent issue across the ROMs was not getting mobile internet to work. WiFi was always OK, and I got an "E" for Edge connection after booting, and network signal was showing orange and good signal, but once I left the house, and WiFi dropped, the mobile internet never connected. The only way to get it working 100% is to turn off WiFi, reboot the phone, and use ONLY mobile internet (not fast, but on an unlimited plan so not an issue, thankfully!)
So, anyone else had this WiFi/internet issue, and is there a fix?
Is there a better ROM anyone can recommend as a daily driver?
Thanks!
I recently fired up a Nook Tablet running CM 12.1 and found to my surprise that it would not connect to my router. I am 96% sure that when the router was recently replaced by ATT, I turned on both of my Nook Tablets (and everything else in the house) and got them set up on the new router, SSID, password, etc. Everything was fine.
But now it's not. I should add that I have a variety of relics with old OS that have no trouble connecting to the router (an old KitKat sim-less phone, Nook Simple Touch e-readers, etc.) as well as more current devices (also no problem there). It's just these two Nook Tablets, one with CM 12.1 and the other AOSP 7.0.
I took the tablets to the local library and had no trouble connecting to their WiFi (of course, it's not secured...).
I can see the tablets trying to connect to the saved router (yep, I did "forget" it and start again) but then they just give up and try again and again periodically. I captured a very lengthy and mostly incomprehensible logcat of such a session but I can't see anything that jumps out and says "this is the problem!!!".
Any ideas? (I've thought about wiping the tablets--I have backups--and starting from scratch...I'd rather not...)
nmyshkin said:
I recently fired up a Nook Tablet running CM 12.1 and found to my surprise that it would not connect to my router. I am 96% sure that when the router was recently replaced by ATT, I turned on both of my Nook Tablets (and everything else in the house) and got them set up on the new router, SSID, password, etc. Everything was fine.
But now it's not. I should add that I have a variety of relics with old OS that have no trouble connecting to the router (an old KitKat sim-less phone, Nook Simple Touch e-readers, etc.) as well as more current devices (also no problem there). It's just these two Nook Tablets, one with CM 12.1 and the other AOSP 7.0.
I took the tablets to the local library and had no trouble connecting to their WiFi (of course, it's not secured...).
I can see the tablets trying to connect to the saved router (yep, I did "forget" it and start again) but then they just give up and try again and again periodically. I captured a very lengthy and mostly incomprehensible logcat of such a session but I can't see anything that jumps out and says "this is the problem!!!".
Any ideas? (I've thought about wiping the tablets--I have backups--and starting from scratch...I'd rather not...)
Click to expand...
Click to collapse
Try booting to recovery mode and wipe the cache partition, just in case there is cached data causing issues, but do not factor reset.
Droidriven said:
Try booting to recovery mode and wipe the cache partition, just in case there is cached data causing issues, but do not factor reset.
Click to expand...
Click to collapse
Thanks for your response. I should have tried that (if I didn't already) so I did this morning to be sure, with a known working-at-the-time backup of the CM12.1 ROM. Still no dice.
I got to thinking about the possibility of ATT sending out a security patch or something and then thought about an old repeater I had in a closet (not so old that it was not set up with the new modem). It's one of those WWRT flashed Linksys modems. Ancient. Was working the last I tried, but I thought maybe it would not be able to pass along whatever potential security issues the newer ATT modem/router was exhibiting with this ROM.
I was right. It connected right away to the repeater, full internet access, etc.
Here's what else I know so far. I have a handful of other ROMS from CM11 up to LNOS 14.1, all backed up from a known working configuration. It just happens that the CM 12.1 ROM gave the best performance on the tablet (admittedly near the edge) and that's where I settled eventually.
All of the backups, when restored, connected to the new ATT modem without issue.
So....I can only guess that the developer of the CM 12.1 ROM left something out which hasn't shown up until now. Interesting that even the CM 11 ROM connects without difficulty.
Now I need to decide what to do with the 8 GB tablet (the 16 GB version running AOSP 7.0 magically works after many an attempt to connect to the ATT modem). I hate to go back to CM 11 because many websites don't display properly with available browsers and there are other SSL issues as well.
Maybe take another look at CM 13....or wait. I won't have this ATT modem forever. Perhaps the tablet will work again with some other setup (as it does with open networks now).
nmyshkin said:
Thanks for your response. I should have tried that (if I didn't already) so I did this morning to be sure, with a known working-at-the-time backup of the CM12.1 ROM. Still no dice.
I got to thinking about the possibility of ATT sending out a security patch or something and then thought about an old repeater I had in a closet (not so old that it was not set up with the new modem). It's one of those WWRT flashed Linksys modems. Ancient. Was working the last I tried, but I thought maybe it would not be able to pass along whatever potential security issues the newer ATT modem/router was exhibiting with this ROM.
I was right. It connected right away to the repeater, full internet access, etc.
Here's what else I know so far. I have a handful of other ROMS from CM11 up to LNOS 14.1, all backed up from a known working configuration. It just happens that the CM 12.1 ROM gave the best performance on the tablet (admittedly near the edge) and that's where I settled eventually.
All of the backups, when restored, connected to the new ATT modem without issue.
So....I can only guess that the developer of the CM 12.1 ROM left something out which hasn't shown up until now. Interesting that even the CM 11 ROM connects without difficulty.
Now I need to decide what to do with the 8 GB tablet (the 16 GB version running AOSP 7.0 magically works after many an attempt to connect to the ATT modem). I hate to go back to CM 11 because many websites don't display properly with available browsers and there are other SSL issues as well.
Maybe take another look at CM 13....or wait. I won't have this ATT modem forever. Perhaps the tablet will work again with some other setup (as it does with open networks now).
Click to expand...
Click to collapse
You might try flashing different versions of modem for your tablet to see if any of them work better. Yeah, it sounds like something might have changed in CM but I doubt it is anything the ROM developer did, it is more likely something that the CyanogenMod team changed in the CM source code. I had a Straight Talk Galaxy S3 years ago that didn't require a SIM to be used on the Straight Talk network but when flashed with CM ROMs, it wouldn't connect to mobile data or be able to send MMS without a SIM inserted, this was around the same time as your ROMs were built. The 4.4 ROMs worked without the SIM but the last few builds of 4.4 and above ROMs would not work without the SIM. This was a result of something that the CM team changed in the device's RIL(radio interface level).
You may be facing an issue that is also caused by something they changed in your later ROMs. It could also be because things have changed in the networks that we use today, different bands, network types and protocols.