Develop Bugs

3G notification

I'm currently using the HTC T8285 Telstra. I know that it picks up the 3G here, just in Australia instead of having a 3G icon where the signal is, theirs has an H.
Is there any cab or tweak to either get the H to show up as 3G or have 3G shown beside where is says AT&T ?

Im actually on the Telstra network The icon switches between 3G and H on mine, i think depending on whether the current cell supports HSDPA?

ryche316 said:
I'm currently using the HTC T8285 Telstra. I know that it picks up the 3G here, just in Australia instead of having a 3G icon where the signal is, theirs has an H.
Is there any cab or tweak to either get the H to show up as 3G or have 3G shown beside where is says AT&T ?
Click to expand...
Click to collapse
You realize the "H" is better than "3G"?

H is for HSDPA aka 3.5G

i think ryche316 is referring to the label reading 3G AT&T vs just AT&T. if i'm correct, you'll need a registry editor to fix this. launch the registry editor and goto the registry key HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PhoneSetting and change the Enable3GLongNamePrefix key value from 0 to 1. soft reset and you'll see it now read 3G AT&T. true this is a minor cosmetic item, cuz if it shows H in the signal meter, you're better off. i've rarely seen mine show 3G. i always want to see H.

cortez.i said:
i think ryche316 is referring to the label reading 3G AT&T vs just AT&T. if i'm correct, you'll need a registry editor to fix this. launch the registry editor and goto the registry key HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PhoneSetting and change the Enable3GLongNamePrefix key value from 0 to 1. soft reset and you'll see it now read 3G AT&T. true this is a minor cosmetic item, cuz if it shows H in the signal meter, you're better off. i've rarely seen mine show 3G. i always want to see H.
Click to expand...
Click to collapse
Aye ditto, can also use Schaps 3.3 to do the mod too which will allow you to call 3G whatever you want.

Thanks there Trickster. yea that's what I was referring to. I do realize that the " H " is a 3.5G which has a faster download speed than 3G.
Thanks

Questions about band setting

I live in the UK, and am using a foreign version of a TP2 that I bought on eBay. I think it's probably the Hong Kong version - it's in English, but with support for Chinese characters on the keyboard.
Something I do fairly regularly is switch between 2G and 3G modes on my TP2 manually. I've created a start-menu short-cut to CMBandSwitching.exe which lets me change the phone's Band setting between "Auto", "GSM" and "WCDMA". My somewhat limited understanding of these settings is that "GSM" basically means "2G", and "WCDMA" basically means "3G". When I set the phone to "GSM" it picks up GPRS or EDGE signals (according to the status bar). When I set it to "WCDMA" it picks up HDSPA or 3G signals (if there are any). What I thought "Auto" mode did was simply switch automatically between 3G and 2G mode depending on 3G signal strength - so that if there's a 3G signal it uses that, if not, it uses 2G.
However, it seems like there may be slightly more to it than that. If I have the phone in GSM mode at home and search for available networks, it finds O2, T-Mobile, Vodafone and Orange (in that order - does that mean O2's signal is the strongest, or does it put it at the top of the list because I have an O2 SIM?) In WCDMA mode it only finds O2, which would suggest that O2 is the only 3G signal that can be picked up in my home (and even that's pretty weak ). However, if I set the phone to Auto, then search for networks, then it also starts to get a signal from the 3 network and lists all 5 carriers - in other words, in Auto mode it finds a signal which is not visible in either GSM or WCDMA mode. This suggests that Auto may be doing something else besides switching between 2G and 3G. Can anyone explain this?
Also, if O2 is the only network it can find when set to "WCDMA" does this mean that O2's is the only 3G signal I can receive?
Finally, there are four possible frequency settings in the lower part of the BandSwitching app. These are:
Auto
GSM(900+1800)+UMTS(900+2100)
GSM(1900+850)+UMTS(1900+850)
UMTS(2100+800)
Which is the best setting for UK use? I'm currently using the second one, and it seems to work okay, but would I gain anything by switching it to "Auto"? And can someone give me an idea of which areas in the world I could get decent 2G or 3G reception with that selection of settings available?

(bump)
No one...?

What's code to switch between networks manually?

What is the phone code to get to the screen to switch between networks like 3G and 2G/Edge.
EDIT: Code is *#*#4636#*#*

I Don't know, but try this ...
Settings->Wireless&Networks->MobileNetworks->NetworkMode
WCDMA Only = 3g/HSPA+ ONLY
GSM Only = Edge Only
GSN/WCDMA Auto = The phone decides which network to be on

dav3wash said:
Settings->Wireless&Networks->MobileNetworks->NetworkMode
WCDMA Only = 3g/HSPA+ ONLY
GSM Only = Edge Only
GSN/WCDMA Auto = The phone decides which network to be on
Click to expand...
Click to collapse
In CM6 that option isn't available unfortunately.

[Q] Getting Cricket Data to work on Triband Network

So I've read all of the claims that the EVO simply won't work if you're in an AWS market. Fine, no problem. Somehow i've managed to get it to work for me though! Well, talk and text on the android plan anyway. I still can't seem to get data working though :/ I was wondering if anyone could help me with this.
I started out with myn-WarmTwoPointTwo--RLS-4-Cricket-Zmod played around with settings for about 4 days and finally managed to get talk and text working. However, my "4G" radio would only take me to a webpage that asks me to sign up for clear internet service when I opened the web browser(Hmm i wonder what would happen if i signed in with my clear account, I'll try that in a moment).
Someone mentioned I go for JimminyV's cricket ROM. So i gave that a try and there didn't seem to be any difference at all, but i couldn't get a mobile network connection, so i'm thinking this ROM won't do the trick for me, I went back to twoPointTwo.
I've taken bits from all kinds of tutorials, including JImminyV's ROM post:
http://forum.xda-developers.com/showthread.php?t=784776
The Zmods:
http://forum.xda-developers.com/showthread.php?t=795126
EPST programming codes:
http://forum.xda-developers.com/showthread.php?t=737594
some post ztahoez made over at CDMAGurus.com etc.
Played around with ##Data#(I should give you my settings in there):
Data Profile:
Active Profile = 1
User Name = my#@mycricket.com
SPI MN-HA = 12C
SPI MN-AAA = 2
Reverse Tunnel Preferred = Enable
Home IP = 0.0.0.0
Primary Home Agen = 68.28.15.12
Second Home Agent = 68.28.31.12
HA and AAA shared secret = cricket
DSA Server URL = (couldn't find any info on this so i just wrote https://dsa.mycricket.com) any bells ringing?
EVDO:
DDTM = Enable
Preferred Mode = Auto
Advanced:
MEID = a hex value that can't be edited and i'm not sure if it's safe to share
P_REV = IS-2000(6)
SCM = 58
Slot Mode = Enable
Slot Cycle Index = 1
MMC = 310 - I'm in the US
MNC = 00
MSID = 4433070623 - anyone familiar with that MSID?
ACCOLC = 3
Vocoder = Enable
EVRC-B = Disable
Home and Roam ORig = Voice 13k
LBS PDE IP and Port = unavailable - what is that?
Foreign NID and SID registration = Enabled
DDTM = Enable
Home SID/NID #1 = 6535/65535 - I can't find info for this anywhere
MMS Server URL = http://mms.mycricket.com/mycricket/mms.php
RTSP Proxy Port = 554
RTSP Proxy Address = 0.0.0.0
HTTP PD Proxy Port = 8085
HTTP PD Proxy Address = 0.0.0.0
WiMAX:
Standby Time(minute) = 10
SCAN RATE = 30
NAI = [email protected]
User Name = my#@mycricket.com
Realm = mycricket.com?
a whole bunch of craziness
TLS = enabled
TTLS = disabled
My PRL is 06399
Hmm after messing around with JimminyV's ROM, I can't seem to connect to clear's sign in prompt anymore :/
Other Common problems:
I keep getting error code 65, which with a little googling, means that there's an authentication issue, somewhere :/
[EDIT] I forgot to mention that ##778# and *228 don't work, and if i use *22804, I'll usually connect to Verizon Wireless' configuration menu [/EDIT]
I've tried to be as thorough as i could be. Please let me know if you have any questions for me and if you can help, THANKS!!!

I guess I can post this over at CDMAgurus too, but just wanted you to know, that i was able to log into clear with my account lol(i'd better check if i've been charged, or the lol will be on me.

Hey here, yes here, this is why:....
HEY HERE, YES HERE, THIS IS WHY:....
The reason as to why you only get talk/text on cricket with a dual band phone on a tri-band area/AWS is the following:
Your plan has a national access/roaming (talk/text), meaning that everywhere you go, you will be able to get AT LEAST talk and text. On the regular cricket network, you get EVERYTHING.
Your phone is actually connected to sprints tower because sprint is the roaming partner with cricket. the agreement DOES NOT allows data usage, only talk/text ( i will assume because talk/text does not takes as much bandwidth as data does)
So, to sum-up:
ANY DUAL-BAND PHONE on a AWS market will be on a "Roaming Partner Network"
This is because you are using SPRINTS network (or any other romaing partner network), and the agreement only lets you use talk/text.
HOWEVER, if you take your phone where cricket offers a native DUAL BAND (800/1900) frequency, you will have data working.

Numerous people are sadly mistaken when it comes they're understanding of the Cricket EVO's functionality in triband areas. They have been lead to believe that it's impossible to get it to work or to get all of its features working, but this is about as far from the truth as it gets. People are quick to rely on information which they haven't actually tested themselves. They're like the folks in Columbus's day who didn't believe that the earth is round, but here are the facts...I live in Chicago, which is a triband area, and have been using a fully flashed Cricket EVO for quite some time now with out a single problem whatsoever. Everyone one of my features work perfectly fine, and my network is NOT roaming. Looks like Cricket EVOs work in triband areas afterall!

yeah you're not the first person to say that, but no one's been able to prove it. or show how to do it.

Laserbeak43 said:
yeah you're not the first person to say that, but no one's been able to prove it. or show how to do it.
Click to expand...
Click to collapse
I've been using the proof for a couple of months now & as far as how to do it is concerned, it's posted all over this website & others.

RioSoul said:
I've been using the proof for a couple of months now & as far as how to do it is concerned, it's posted all over this website & others.
Click to expand...
Click to collapse
Last i checked(for weeks) It couldn't be done on cricket. I've had voice but had to use clear for data.

so yyeah i've searched all EVO forums for Cricket and Triband and there's no thread that posts a solution, there are only 3 threads as a matter of fact.
So which thread were you talking about?

bumping this one, willing to donate to a dev of your choice if someone can help me get this EVO working in st. louis. i understand the AWS issues, but i think as a lot have said, that its possible in AWS markets. im willing to try anything. internet works great here with full 3g, just no getting cricket programming when *228, and *22804 does nothing but sit and then hand up. 611 says your account can not be validated.

[Q] LTE Only?

I often do live streaming of events and from time to time I am forced to tether my cell to my laptop for internet access. This actually works better than you would expect. Anyway, back in the ICS (Task650 AOKP) days anytime I needed to do this I would use the old *#*#4636*#*# code and select "LTE only". This worked great, it disabled CDMA (so no calls or texts), and most importantly it prevented the phone from switching between CDMA and LTE (which obviously would be disastrous during a live stream).
Now that I am running JB (tried CM10.1 and Task650 AOKP), this doesn't work anymore. Even though LTE works perfectly fine under normal circumstances, when I select "LTE Only" the phone simply disconnects everything and I never get data back. It seems like there was a change in the modem options or something. When I go into Settings->Mobile Networks->Network Mode I can select LTE/WCDMA, LTE/GSM/WCDMA, GSM/WCDMA. If I select any of these options and go back to the phone info screen using the *#*# code, under "preferred network type" it says "Unknown."
I've tried two modems with the same results:
I747MUMLL1
I747MVLLH1
Any ideas on what I can do?

A quick update. I did try the stock modem firmware. No change. I went back to a stock ROM, which no longer accepted the *#*# code, but did accept the *#2263# code which allowed me to select LTE band preference and locked it into LTE. Is there a way to get into this menu from an AOSP ROM? Is this specific to the dialer?

Maybe a APN change could help this but I don't think you can perma lock LTE as it's not available everywhere.
Also, mind if I ask why you wanna have LTE only? It's already set to use LTE when needed, therefor, you don't need to lock it on.

BWolf56 said:
Maybe a APN change could help this but I don't think you can perma lock LTE as it's not available everywhere.
Also, mind if I ask why you wanna have LTE only? It's already set to use LTE when needed, therefor, you don't need to lock it on.
Click to expand...
Click to collapse
Hi BWolf,
I had mentioned it in my first post but the reason I want LTE only is so I can prevent the switching of bands between LTE and HSPDA when I am live streaming. Anytime a switch occurs there's a down period of a few seconds which causes the live stream to freeze. Even with full LTE bars, the phone seems to switch every now and then.
I know it's possible, because I can do it on the stock ROM, and I could do it with the older AOSP ICS ROM's. After decompiling the stock FactoryTest.apk file it appears that everything is controlled using invokeOemRilRequestRaw commands. I'll dig into it a bit further, I'm sure there's a way to replicate the functionality.

Ugh. I was hoping the setting was actually achieved using some sort of simple command send to the baseband. That is not the case. Apparently the whole menu system resides in the baseband, and the serviceModeApp.apk app simply provides a dummy interface to display the choices and respond back with selections.
I think at this point it's a little more work than it's worth. I can always flash a nandroid of a stock rom for the streaming and then flash back afterwards. Not ideal, but it'll have to do.

Well, I've solved it. After more effort than I care to admit to, I've found the cause of a lot of the grief with the network mode settings. I'll leave this info here in case someone else ever comes looking for it.
First off, it appears selecting "LTE only" wasn't working due to some sort of bug either with the radio baseband or with how some of the custom roms deal with the baseband. This bug was persistent across ROM reflashes because persistent data in the baseband remained. It appeared to have fixed itself when I flashed back to a stock rooted rom and did a factory reset. Other people have found this solution to work for other bizarre radio related issues, such as no LTE. Anyway, that fixed the LTE only selection.
In regards to the apparent disconnect between the list of preferred networks and what the radio was actually doing, as it turns out there is a mismatch. At some point in my search I downloaded the CM10.1 source and started digging around. I found in the ril directory the reference-ril.c file which describes the network modes:
Code:
static int net2modem[] = {
MDM_GSM | MDM_WCDMA, // 0 - GSM / WCDMA Pref
MDM_GSM, // 1 - GSM only
MDM_WCDMA, // 2 - WCDMA only
MDM_GSM | MDM_WCDMA, // 3 - GSM / WCDMA Auto
MDM_CDMA | MDM_EVDO, // 4 - CDMA / EvDo Auto
MDM_CDMA, // 5 - CDMA only
MDM_EVDO, // 6 - EvDo only
MDM_GSM | MDM_WCDMA | MDM_CDMA | MDM_EVDO, // 7 - GSM/WCDMA, CDMA, EvDo
MDM_LTE | MDM_CDMA | MDM_EVDO, // 8 - LTE, CDMA and EvDo
MDM_LTE | MDM_GSM | MDM_WCDMA, // 9 - LTE, GSM/WCDMA
MDM_LTE | MDM_CDMA | MDM_EVDO | MDM_GSM | MDM_WCDMA, // 10 - LTE, CDMA, EvDo, GSM/WCDMA
MDM_LTE, // 11 - LTE only
};
These correspond directly to the spinner selections in the phone info activity, which are:
Code:
private String[] mPreferredNetworkLabels = {
"WCDMA preferred",
"GSM only",
"WCDMA only",
"GSM auto (PRL)",
"CDMA auto (PRL)",
"CDMA only",
"EvDo only",
"GSM/CDMA auto (PRL)",
"LTE/CDMA auto (PRL)",
"LTE/GSM auto (PRL)",
"LTE/GSM/CDMA auto (PRL)",
"LTE only",
"Unknown"};
If you compare the two, you can see that the descriptions are not entirely accurate. In particular, many of the mode strings do not indicate they would select EVDO (even though the mask from reference-ril.c clearly shows they would). On devices which don't support EVDO, such as the i747, selecting these modes fail.
With the LTE only network mode now working, I see no need to implement the service mode band selection menu. With that said I did have a few solid strategies for doing it, if I decided to go that route. I peeked into the SecFactoryPhoneTest.apk a little bit, which is the service Samsung uses to communicate between the RIL and userspace java apps. It connects to a local socket named "Multiclient". I found this really bizarre because the telephony stack already connects to the RIL socket, and second the socket is typically named "rild". I believe Samsung has a custom implementation of rild (the linux userspace daemon which passes RIL requests to the kernel) which implements this extra "multiclient" socket. I could not find this socket on my AOSP based ROMs, so I assume it is a proprietary Samsung thing.
Instead of connecting directly to an RIL socket, you might be able to send the bytes associated with pulling up the band selection menu, and then blind sending the correct menu selections. The samsung service uses reflection to try and send RIL requests through the ITelephony interface (and then falls back on making a direct RIL connection). Here's how it does it:
Code:
Method localMethod = localITelephony.getClass().getDeclaredMethod("sendOemRilRequestRaw", new Class[] { [B.class, [B.class });
Now I think the sendOemRilRequestRaw method is another proprietary function, but a similar one exists in the AOSP RIL implementation which is invokeOemRilRequestRaw. Using the same technique you might be able to send raw bytes to the RIL without messing around with sockets.

Ironically I just found in the source a c program that connects directly to the rild and issues commands to select certain radio options. Path is hardware/ril/rild/radiooptions.c. It connects to the debug ril socket to issue commands. A potentially super easy route to issue commands in the future would just be to modify that and run it as a command with superuser from java.