Hey everybody. I have searched and searched, and while I see posts on other forums that field utils works for the wifi xoom, and the SPC code is 000000, mine isn't.
Currently I can only go into the radio info section of field utils, but the other menu options are there.
I can't seem to locate any tools that would let me find it out, I don't see anything in getprop for the MSL, so my question is:
Does anyone know how I could get that, since it's a wifi device? The field utils app is there, but it's not 000000, its not 555555, I tried a bunch of other combinations, but so far have been unable to randomly stumble across it, or find an app that would get it for me.
(rooted, btw, running 3.2)
Related
Hi,
When entering the dialer code for the GPS info, nothing happens. I have done this awhile back and I know it worked on my phone before. I can also put in other dialer codes and the ones I've tried worked (ex. 4636, 232338, 44336, etc.) But with the GPS one, it takes it and does nothing (dialer shows "Add to Contacts" and at the last entry (#) that goes away)
I'm even using the Phone Codes v1.4 app and while the other default button codes work, the GPS Test one doesn't.
Any ideas? What setting did I muck with to cause this?
(I897UCJH7),
Thanks
Try *#3214789650#
Mac
Thanks Mac, that worked.
But I still don't understand why the other didn't. Any clues?
Thanks again...
Samsung changed it to defer people from using the settings people posted around here.
last evening I unlocked my samsung captivate using Nwolf's method.
everything worked and i was happy until i thought of checking the network status using the code #7465625#..
the response i get is "rejected".
I searched the for this problem on the net some people were talking about turning the "mobile tracker" off.
i searched on my captivate for this option in location and security but there is no option as such (to my horror).
is anything wrong with my captivate? i have faithfully followed Nwolf's instructions to the letter.
somebody please help...
FOUND SOLUTION i missed the * before #...
but still would like to know whether other captivate owners have the "mobile tracker" option in "location and security".
No, never saw 'Mobile Tracker' in there.
ok that's something to relieve me. I was thinking may be i made some mistake in the process.
thanks a lot.
I have it. I'm running Andromeda 1.0.
If you have this bug I don't need to explain anything else. If you don't have it consider yourself lucky.
I have read the other threads on this forum and everyone seems to talk about switching the radio.
I think an easier solution would be to disable the search button.
You could do this possibly by
1) commenting out the search lines in the keyboard file
2) installing buttonremapper by beansoft and swapping the search button for something else like "focus" (Note: buttonremapper is available for free through this site or 99 cents through applications
I haven't rooted my phone yet and would prefer not to go through that if I know it won't work.
Looking for volunteers who have already rooted their phone to try one of the two solutions above and report back on their success.
Thanks
What is the bug?
Do a google search for "Nexus s Voice search major problem" and you will find the google forum entry.
I can't post a link because I am a noob and it won't let me.
Basically the search button fires at random at times making the phone unuseable
I don't seem to encounter this yet. Or maybe it has been fixed in 2.3.4?
It's a problem in 2.3.4 and possibly 2.3.3
It does not hit all the Nexus S in Canada only some.
Very aggrevating
I have this bug on FIDO. Phone came with baseband UCKD1. Tried software 2.3.3. and 2.3.4 and no difference.
Goes away if you disable 3G or use WIFI.
I'm having good results with the new radio. I flashed XXKB3 and have not seen the search button fire off in the last 2 days. Have not used WIFI at all either, so I think it's good.
However, issue with FIDO is that this radio will make it look like you're roaming, when in fact you aren't. I believe it has something to do with the older radio not recognizing that ROGERS now owns FIDO...
featherdust said:
If you have this bug I don't need to explain anything else. If you don't have it consider yourself lucky.
I have read the other threads on this forum and everyone seems to talk about switching the radio.
I think an easier solution would be to disable the search button.
You could do this possibly by
1) commenting out the search lines in the keyboard file
2) installing buttonremapper by beansoft and swapping the search button for something else like "focus" (Note: buttonremapper is available for free through this site or 99 cents through applications
I haven't rooted my phone yet and would prefer not to go through that if I know it won't work.
Looking for volunteers who have already rooted their phone to try one of the two solutions above and report back on their success.
Thanks
Click to expand...
Click to collapse
This drives me INSANE. I'm rooted. I've tried option 2 and it doesn't seem to work for me. I'll give option 1 a try, if someone can tell me the file I'm looking for...?
Thanks!!
I have the voice search bug as well on an I9020A (AT&T) I purchased recently. I took the risk even after hearing about the bug. Was a solution ever found or has everyone moved on to new phones? The screenshot is attached.
I hate that my phone has this bug. Other than this absolutely glaring bug it is a spectacular phone.
For those that do not know, the bug only occurs on some I9020A (US: AT&T Canada: Rogers) models. When the phone is attempting data transfers over 3G where signal strength is relatively low (on stock ICS ~2 bars or lower), the voice search will randomly fire. When downloading a large file over 3G, this can mean it fires almost constantly and makes the phone unusable. That's about the best description I can give.
EDIT: The voice search bug came back no matter what radio or distro I installed, so I just disabled the search capacitive button.
To do this:
***Enable R/W mode in Root Explorer****
1. Open /system/usr/keylayout on phone using Root Explorer.
2. Open mxt224_ts_input.kl in a Text Editor (long press, find option)
3. Comment out the search line by putting a # at the beginning of the line.
4. Save changes
5. Open cypress_touchkey.kl in a Text Editor
6. Comment out the search line by putting a # at the beginning of the line.
7. Save changes
8. Restart phone
Example edited line:
# key 217 SEARCH VIRTUAL
This works for me since I do not use the search button anyway.
Thanks to stumpy352 for starting a thread on instructions for disabling capacitive buttons.
I received a new phone today that I got on eBay, a Cobalt SP300. The hardware itself is pretty decent, except for the camera, but I've run into some issues with Android. I think it might be my APN settings, even though I've tried many different variation, but I can't get outbound texting to work. It just says sending for a while and then fails. Inbound texting however works fine.
Another issue is that I am stuck on the Edge network. I took a game since the eBay description said Edge only, but I was hoping it might have been in error since this chipset inherently has 3G built into it. But I think for some reason this company disabled it. Also kind of odd since it says it allows HSDPA right on the box... Anyway,when I go into the info screen (*#*#4636#*#*) I see it says GSM only, but it won't let me change it. I remember seeing on a russian site some sort of debugging screen where you could see all bands the phone allows. Anyone know how to get to that?
Would anyone be able to help with this?
Would knowing the baseband or kernel version help?
Thanks
I have also tried getting into an engineering mode as well using *#*#3646633#*#* and *#*#197328640#*#* to view band modes but neither of those codes work, it just brings me back to the dialer screen.
As far as the no incoming texts go, I figured that out by putting the proper SMSC code for AT&T in the messaging app setting. Hopefully this bit might help anyone else with the same problem.
I don't know if anyone may be able to answer this now but with so many of these selling on eBay someone else is bound to searching for the same fix as I am for the 3G. I made the EDGE bearable by using Opera Mini however.
Also, I found the original Chinese version of this phone, the Morningside A206.
And it turns out I'm not alone in the search for 3G, I found something in Chinese with someone inquiring why their A206 won't connect to 3G.
I would post these links but I don't have enough posts.
3G is looking less likely to be activated.
I found an app called Mobileuncle MTK Tools that gets you into engineer mode. I go down to Band Modes (Screenshot attached) and the GSM modes are all selectable but all of the UMTS modes are grayed out. It just seems so weird I know this is a MT6575 chipset which supports it. Is there anything else that can be done?
I also happened to find out how to root the phone if anyone comes across this and needs to know.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2046161
I also had to find the drivers elsewhere, so just google this .rar file: usb_driver_MT65xx_Android_ZTE_v821.rar
The first google result from rghost . net worked fine
I've recently left my i9100 for an i9305 and decided to start by flashing the equivalent to my favourite ROM from my S2, namely SlimSaber (SlimKat unoffical build with Saber Mod) from here (build 8.0).
Anyway, regrettably i never tested out the phone much with the stock software because i wanted to go strait back to the KitKat experience I'm used to. I did however unlock the phone using USSD code *#19732864# as outlined in method 3 here. I believe I followed it exactly and it worked without a hitch
With it unlocked i put in my GiffGaff SIM and the first thing I noticed was that after every text, instead of getting the regular message saying "woohoo that text was free" or relevant credit update, i just get a similar box with a load of Chinese text.
Then I realised that the proximity sensor doesn't work. I don't mean to go specifically into that problem in this thread but while researching a fix I came across some USSD codes that might help. Now I can get a few to work: *#06# to show my IMEI , *#31# (Checks outgoing caller ID settings) and *#*#4636#*#* (User statistics and Phone Info), but all others I've tried just give me "Running USSD Code" and then "Connection problem or invalid MMI Code". This includes the one I unlocked my phone with in the first place and all the ones that are supposed to help my problem. A couple of the codes (*#526# and *#528#, both for WLAN Engineering Mode) yielding more Chinese text in place of the second message. I've tried putting a coma or semi-colon after the codes to no avail.
I presume that the network messages run on the same system as USSD/MMI and that the problems are connected. Not sure if the proximity sensor issue is connected.
The fact that a code worked before, but then stopped working seems to imply that it was something to do with flashing the ROM. Can anyone confirm that custom ROMs can mess with your USSD codes? Or could the unlock process have changed something? I've tried different kernels but the problem persists. Does anyone know at what firmware level native USSD codes are defined?
Many thanks for any input.
Hi,
The best place to find help would be in your device section, here...
> Samsung Galaxy S III I9300, I9305 > Galaxy S III Q&A, Help & Troubleshooting
Good luck!
Moved
Ok, great thanks. Seeing as you said nothing about getting it moved I just made a duplicate thread there. You can find it here:
http://forum.xda-developers.com/galaxy-s3/help/network-messages-coming-chinese-invid-t2913800
Mods feel free to delete this one.