OK, Firstly, does anyone else have the Defy on the Three network and is it working alright for you??
I'm just trying to figure out whether this is a phone problem or a network issue. Basically I'll unlock the phone, go onto google, search for something and that's when the wait starts, it's really weird, I'll have full 3G signal, and neither of the little traffic arrows will do anything, which makes me think it's not a network issue. Absolutely all network traffic locks up, including gmail, market etc
But then if I make a phone call and hang up it will start working again fine. All I can think is that it's just a little software glitch in my phone. Does anyone know if Motorola will send me a ROM update/repair tool for the phone because I'm guessing it's something to do with that, or even try rolling back to Eclair 2.1 to try that. And yes, before you ask, I've tried many times doing a full wipe/factory reset and it makes no difference.
I've quadruple checked all my APN settings for Three which don't even have usernames or passwords and even checked the settings were correct in the secret service menu. Also when I had the problems I ran a ping test (in the secret menu *#*#4636#*#*) and they all returned "failed could not find ip"
It's just so weird how random it is, I can't work it out. Maybe the defy really isn't compatible with three.
If anyone's got any ideas please please please leave info below.
One other thing I forgot to mention is that the defy was previously locked to Tmobile(uk) and was unlocked using a simple unlock code, no hacking or modding involved
Hi mate,
I've been using my defy on 3 UK with no problems since Jan. I've been on eclair the whole time. Currently the 2.51 stock.
Olly
Hi everybody, I usually don't like to make my first post a question but I've been trying to figure this out for a month and no luck. Here goes!
First off, the device isn't a note 2, but judging by the build number I think it is knockoff samsung which is why I'm posting it here and not in the general forum. Here's a pic of the info:
Device is a 'Hyundai P700'. I don't think it actually made by hyundai, just a knockoff using the name. I got it to use as a cheap 3G tablet, but I like it so much I'm using it as my main phone(get lots of funny looks when I hold it to my head).
I'm running it on NET10's BYOP with the AT&T sim. Everything works fine except the 3G. Specs list it has
GSM quadband and WCDMA 850/900/1700/1900/2100MHz.
I'm pretty sure the problem comes down to the 850MHz band(used here for att 3G) being disabled as it isn't intended for the american market.
I have tried and tried and tried to get into the service menu to no avail. The only MMI code it will take(I've tried dozens) is *#*#4636#*#* which brings me to this menu:
As you can see it only lets me select two options, neither of which give me 3G.
I tried installing a service menu shortcut icon, but again that gives an error. All of the dialer codes
that begin with *# and end with # give me the error 'no network connection or invalid MMI code'.
I'm really at a loss. I found a thread that shows how to inject some code straight into the root folder which looked promising, but that's way beyond my expertise with computer/phones.
Here are some other screencaps that may prove helpful:
Any help with this would be awesome! Being on edge data is like being slowly tortured, literally!!!
Edit: So apparently I can't post links to pictures yet. Here's the album with the screen caps, just remove spaces. http: //s194.photobucket.com/user/redtibo/library/Hyundai%20P700?page=1
Here is a way to find out what band/mode is available:
1) From play store, download and install "HiddenApp"
2) Run HiddenApp, it lists all apps in your phone even apps don't usually available in app list.
3) From the list, scroll down and find apps named "EngineerMode".
4) Press and hold "EngineerMode", it creates a shortcut in your home screen.
5) Exit from "HiddenApp" and go to home screen.
6) "EngineerMode" appears in your home screen.
7) Press "EngineerMode", then scroll down to BandMode.
8) Press "BandMode", it shows all available bands.
9) It shows GSM and UMTS modes.
10) All bands (grey out) are not available on your phone.
11) All bands (text color in white) are available on your phone.
12) You may checked and/or unchecked any band with text color in white but not grey out.
13) You may take out a few bands but not adding more.
Please take a few picture if "HiddenApp" work for you.
Awesome! Thanks for the response! I had never heard of that app before and it sounds promising...
I can't test it though because the darn thing bricked itself. Booted into a factory test screen and was completely unresponsive. It's on its way back to the manufacturer for a replacement or a refund, still on the fence about that. If I do get a replacement I will try this first thing!
I have installed slimcat on my Canadian Rogers Note 3 sm-n900w8.
I randomly get the message: mobile network not available.
I can't make a call and sms doesn't send.
I have been rebooting to get past this.
Any ideas how to resolve this?
Versions:
W03-Slim-V14-hlte,
kernel cm11-hlte-temasek-v3.51
Also see screenshots of version info.
One place to start is.
Check your Access Point Names (APN). Go to settings find More Network; Mobile Networks ; Access Point Names. You will see one or more settings. These need to match your carrier.
There is an app called Tweakker that may help you with finding the correct settings. Or do google search for APN settings for your carrier.
Google luck
Sent from my SM-N900T using XDA Premium 4 mobile app
smaisonville said:
One place to start is.
Check your Access Point Names (APN). Go to settings find More Network; Mobile Networks ; Access Point Names. You will see one or more settings. These need to match your carrier.
Click to expand...
Click to collapse
I only get this message sometimes. Most of the time everything works. Also I am referring to voice call and sms. These don't use APN.
david1212 said:
I only get this message sometimes. Most of the time everything works. Also I am referring to voice call and sms. These don't use APN.
Click to expand...
Click to collapse
Try these:
1) Check SIM card, try different SIM, see it is inserted properly
2) Check the SIM slot (can be combined with previous test)
3) Factory reset (just to make sure you tried everything)
rahulisola said:
Try these:
1) Check SIM card, try different SIM, see it is inserted properly
2) Check the SIM slot (can be combined with previous test)
3) Factory reset (just to make sure you tried everything)
Click to expand...
Click to collapse
I have done what you suggested above. Thanks.
Also, I have tried several roms. I am still getting the message once on some days. For example on slimkat 15 I got it on May 18th and today.
I am now toggling airplane mode on and off to get the call/text to work again.
Randomly gives the message "mobile networks not available" and call/text don't work at that time.
-cm11
-slimkat 15 with kernel it came with.
Doesn't give the message.
-Resurrection rom
-no name rom
-stock rom
I really like slimkat and I would like to resolve this.
My thoughts:
-It only happens on some roms.
-it seems to be related to CM11 since slimkat is based on CM11?
-maybe Resurrection rom has some library or package that slimkat doesn't?
I wish I knew how to troubleshoot this.
I find it puzzling that others don't seem to get this problem. Nobody has indicated in the poll that they too get the problem.
Anyone have any other suggestions?
Hello,
I have a Samsung Galaxy Note 2, SGH-M317i (Bell Mobility) and recently installed Cyanogenmod 12.1 (Lollipop 5.1.1). All is running well, the device actually seems to be running much faster...probably due to the lack of bloatware that originally came with it. Sure, I miss some of the "cool" features that the manufacturer had added (ie. hand swipe for screen capture), but overall I am extremely happy with the decision to flash the ROM. Although it does self-identify as a SGH-N7105 now. (About Phone > Device model)
Anyway, I have noticed that when I have my guest networks enabled on my home router (an ASUS RT-N66U running the latest Merlin firmware), my phone insists on connecting to the Guest networks (a2.4 and 5 GHz) instead of my full, "regular" network (hidden SSID, but a "Saved" network in the phone). Even if I go into the WiFi settings and tell the phone to forget those entries, it will still try to connect...even going so far as to say "connected" even though I know it does not have the proper credentials. I have no idea what is causing this as the problem was not present on the stock 4.4.2 KitKat that I had previously.
Sure, I could give it the credentials for those guest networks (all are WPA-Personal protected) but I have restricted those from accessing the intranet as they are primarily for guests who come by, so that is not really a viable option.
Does anyone have any suggestions? It seems strange that it attempts to connect and save these networks, so technically, I shouldn't have to do anything to keep the phone from connecting. However, since it insists, I had thought that Android would have a native (not requiring an app) method of blacklisting these networks. I have looked at apps such as WiFi Ruler, but again would've thought that there is a manual way of doing this. (I don't know if this is obvious by virtue of the fact that I am running a custom ROM, but the phone is rooted.)
Thanks!
used this code and off your wifi power saving mode and try *#0011# select wifi..u may need need press the botom left button to select wifi
Very odd. It seems that since installing CM12.1, my device no longer accepts or recognizes USSD codes. I guess I hadn't noticed since I had rooted and unlocked it prior to flashing Cyanogenmod over the stock ROM. I did some reading and I found that there is a patch to enable those codes (and SMS) on CDMA models of the Note 2. However, mine is LTE and does SMS, MMS, and it uses LTE without issue.
Here is a link to that page:
http://forum.cyanogenmod.org/topic/112400-solution-to-sms-and-ussd-code-on-cm121-cm12-cm11-cm10/
Is this something anyone else has experienced? Should I follow the instructions on that page and install the patch?
Again, my phone is a Samsung Galaxy Note 2, SGH-i317M but since the installation of CM12.1 the About Phone > Device model reports it as being a GT-N7105 with a Baseband Version I317MVLUDNH2.
I'd really like to try the solution to my WiFi problem, so if anyone else has had experience with the USSD codes not working please let me know if there is a solution.
Thanks!
To update my last post:
Some USSD codes do work, I watched the pop ups more closely this time and there is one before the "...invalid MMI code" that says "USSD code running". The main one that find interesting no longer works is the one I had used to unlock my phone *#197328640#. I had figured that it would not have disappeared simply by installing Cyanogenmod. Further, I also followed that thread I had posted the link to a little further, and I'm not comfortable flashing the "patch" it leads to as I cannot confirm it's original source and it does sound like it may be another full ROM.
I had 4G before this update, but nothing I do, no matter how many different APN settings I try, no dice.
I'll tell you where I've been. Have had the phone at least a year and it came with Nougat.
As soon as I got it, I got a Total Wireless SIM (owned by Tracfone and running on Verizon's network) and activated it with no problems. Had full service. 4g, mms, etc. All was great.
Even when I got the 8.0 notification and I updated to Oreo, all worked fine.
A few months back, I got the 8.1 notification. I allowed it to install and when It booted back up, I had no service at all.
Found this thread, Android 8-1 - How to Edit Cellular APN, and one post in there got me with the phone setup and connected to my computer running ADB commands, which allowed me to at least add an APN.
Adding the standard TRACFONE.VZWENTP apn you can easily find via Google searching fixed the problem. (Had to add mms port of 80 but otherwise, all was perfect)
About a week back I get the 8.1 notification again, which i thought was weird since I was already running 8.1
Turns out it was the April Security Patch for 8.1 (i suppose as that's the only reasoning that makes sense to me right now).
After it installed and did it's thing, I only had 3G service, which around here is prone to many interruptions, aside from the slow speed.
I checked, and it's still using the APN I set up. Nothing has changed on that APN, nor anywhere else I can see.
I even added a new one with the same data, and same thing, 3G.
I've searched the threads here, tried some of the other suggestions but none have worked.
I've even went as far as to get Smail to unlock my bootloader (it's a verizon Pixel XL) and from there I've rooted installed twrp and rooted etc, all in hopes that I could try another method listed in that thread i linked above, using an adb shell with root permissions to view the "default" apn data, thinking maybe something in there is messing it all up.
I had no luck there because even though the phone is rooted now, there was something else I have to do to run an adb shell with root permission and seems the easiest way to get that done is just install a custom rom.
Still, what baffles me is, isn't this what the SIM card is partly for?
And why would software updates disable service, or parts of service?
Seems odd that a software upgrade would effect how the phone uses the service, especially when a custom apn is setup and unchanged.
I have scanned these forums for hours over the past few days and I would really love some direction on what to try next.
Any ideas are appreciated. Thanks!
Play around in the *#*#4636#*#* dialer menu just don't hit the update button beside the smsc input field
Sometimes, the best thing to do is to go to total wireless and ***** at them till they deal with it. I don't think its something you need to stress over. It's Verizon's and Total Wireless's responsibility to get your 4g LTE back. I just dealt with T-Mobile with the same issue. no 4G but call and texting worked. APN set right but they did something on their side and got me back on track after handing them my phone.(in store)
DR3W5K1 said:
Play around in the *#*#4636#*#* dialer menu just don't hit the update button beside the smsc input field
Click to expand...
Click to collapse
Oh wow, never knew about this. Brought up all kinds of options. Will mess around and see if I can find something useful.
acters said:
Sometimes, the best thing to do is to go to total wireless and ***** at them till they deal with it. I don't think its something you need to stress over. It's Verizon's and Total Wireless's responsibility to get your 4g LTE back. I just dealt with T-Mobile with the same issue. no 4G but call and texting worked. APN set right but they did something on their side and got me back on track after handing them my phone.(in store)
Click to expand...
Click to collapse
I would but Total Wireless doesn't have a store front or even a kiosk. They're kinda like Straight Talk, but just for Verizon phones. Verizon naturally won't have anything to do with it since I'm paying their competition to use their network.
I had thought about going through the activation again, but when i put my IMEI # on their website now, it says my phone is not compatible. A year ago it said it was, and it has been until this update.
I've considered flashing 8.0 and see if that lets it work again, but I don't like the thought of not being to update my phone or i'll lose parts of my service.
Thanks for the suggestions yall. Will repost if the dialer code leads me somewhere helpful.
kamikazeedriver said:
I had thought about going through the activation again, but when i put my IMEI # on their website now, it says my phone is not compatible. A year ago it said it was...
Click to expand...
Click to collapse
Oh my, can you confirm if your IMEI is the same one as the one as last year?
They are probably getting money hungry and want people to buy phones from them. There is a big chance that hidden menu could solve your problem though. Regarding the imei the only way that could be a problem is if yours was somehow stolen
DR3W5K1 said:
They are probably getting money hungry and want people to buy phones from them. There is a big chance that hidden menu could solve your problem though. Regarding the imei the only way that could be a problem is if yours was somehow stolen
Click to expand...
Click to collapse
I think it shows up as an issue because I'm currently using it. I just tried it again and it said "there was an error." When I tried it a few days ago it had said the same, "there was an error, contact customer support"
It's possible that time it showed up as incompatible i had punched a number in wrong.
Can't confirm if it's the same IMEI i had a year ago but it would be weird if that changed.
Couldn't find anything in the hidden menu except when I checked "Carrier Provisioning Info" showed up that it last attempted it yesterday and had failed.
Well as a last ditch .. just a thought here. Pull the sim power on your phone delete the apn. Perform a reboot insert sim and wait. Still nothing? Check apn add if necessary and reboot. Profit?
DR3W5K1 said:
Well as a last ditch .. just a thought here. Pull the sim power on your phone delete the apn. Perform a reboot insert sim and wait. Still nothing? Check apn add if necessary and reboot. Profit?
Click to expand...
Click to collapse
I did try that after the april update.
With no APN, I get no service, which first happened right after the first 8.1 update. That lead me to adding the APN.
I haven't tried it since I've unlocked the bootloader.
I will try again before flashing back to 8.0.
8.0 was the last time my phone worked just fine with no custom APNs or anything.
I thank y'all for the ideas.
I would like to know if I'm the only one with this specific problem.
Is anyone else experiencing this issue with the 8.1 updates using a Verizon MVNO?
For future reference that provisional menu will be populated with answers other than no. If you have the proper apn etc..
DR3W5K1 said:
For future reference that provisional menu will be populated with answers other than no. If you have the proper apn etc..
Click to expand...
Click to collapse
Want me to take a screenshot of the provisional menu? I don't know what I'm looking for in that menu.
As far as APN, it never needed to make one until the first 8.1 update but all worked fine afterwards. It's only since the April update that I have issues.
Will report back after trying to reset without the sim again
If a fresh image+apn doesn't fix it the only other thing that "you” could try would be replacing the Sim. Sometimes the Sim can fry. Could also be as easy as reseating it.
It's fixed
Here's what I had to do.
I did a wipe install (flash all.bat) of an 8.0 Oreo image as it was the last time I had LTE without even having to do anything (like setup a custom APN etc)
After that was successful, I did a no-wipe install of the 8.1 (April 2018) image, and afterwards, and once it was booted, all was well, I have LTE and everything with no custom APNs needed.
Thanks to everyone who offered help in getting me in the right direction.
In addition to what I previously mentioned that I had tried, I also tried:
-I did try a wipe install of 8.1 a few days ago but still with no success. Even with tweaking APN settings.
-I messed around with the carrier provisioning menu and could see I was not getting LTE and when I told the phone LTE only, then no service at all, so I set it back to LTE/CDMA/UMTS (that's what it was already on.)
-Tried dialer code *228 to "activate" my service, but that had no change.
I went back, this morning, to the thread I first looked at after the first 8.1 update I had which disrupted my service completely and ended up with me using an adb shell to do something that allowed me to add APNs and subsequently setup an APN that worked for me until the 8.1 April security update.
Noticed this post:
ThePhoneGeek said:
I have this same issue and the only solution I've found is to full wipe go back to 8.0 activate on Verizon's network (I too use a VZN MVNO) and then flash the full 8.1 package without wipe.
Click to expand...
Click to collapse
I can't say I understand why that worked when a completely fresh wiped install of 8.1 didn't, but it did so I'll take it.
The next thing I was going to try, if it hadn't worked, was changing the radio band in the provisioning menu as that seemed to work for another person.
Either way, all is well for now. Thanks for all the advice!
kamikazeedriver said:
Noticed this post:
I can't say I understand why that worked when a completely fresh wiped install of 8.1 didn't, but it did so I'll take it.
The next thing I was going to try, if it hadn't worked, was changing the radio band in the provisioning menu as that seemed to work for another person.
Either way, all is well for now. Thanks for all the advice!
Click to expand...
Click to collapse
The only thing I've come up with is that starting on 8.1 flashing full wipe for VZN users (or perhaps limited to VZN MVNO's) with unlocked bootloaders is not allowing the device to activate on the network. I suspect VZN hanky panky at work but I am generally a skeptic that way. Once you get it the way you want it you can update each month with the full firmware but remove the -w in the flash-all.bat file and you should be good.
ThePhoneGeek said:
The only thing I've come up with is that starting on 8.1 flashing full wipe for VZN users (or perhaps limited to VZN MVNO's) with unlocked bootloaders is not allowing the device to activate on the network. I suspect VZN hanky panky at work but I am generally a skeptic that way. Once you get it the way you want it you can update each month with the full firmware but remove the -w in the flash-all.bat file and you should be good.
Click to expand...
Click to collapse
My bootloader was still locked when these issues began with the first 8.1 update (which adding an APN fixed), and culminated in 3G only after the 8.1 April update.
I only unlocked it so I could hopefully find a solution, which thankfully was a success.
I'm just as skeptic as you are when it comes to VZN though. They have the best coverage in this area, and that's the only positive thing I have to say about them.