Related
I am having an issue where the person I call states that I sound like I'm calling them from the space shuttle. I had someone call me on a landline from my MDA and it actually does sound like a NASA shuttle call.
I've applied the registry edit for AUDIOGAIN:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\AUDIOGAIN]
"EARPHONE_UPLINK_VOLUME"=hex:CC
"RECEIVE_UPLINK_VOLUME"=hex:CC
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\AUDIOGAIN0]
"EARPHONE_UPLINK_VOLUME"=hex:CC
"RECEIVE_UPLINK_VOLUME"=hex:CC
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\AUDIOGAIN1]
"EARPHONE_UPLINK_VOLUME"=hex:CC
"RECEIVE_UPLINK_VOLUME"=hex:CC
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\AUDIOGAIN2]
"EARPHONE_UPLINK_VOLUME"=hex:CC
"RECEIVE_UPLINK_VOLUME"=hex:CC
The problem is present with handset, BT headset, and wired headset. Anything else I should be looking at? I'm on TMO USA, but I roam on AT&T and EinsteinPCS. Problem crosses all networks. The only thing I haven't tried yet is putting an AT&T sim in and see if it's still there. I don't really think that would be the problem since I can put my sim in my Nokia 6230 and it sounds fine.
Running mfrazzz's XM6r2a. Original TMO 2.26.10.2 has same result. Tried 2.19, 2.25 (TMO OEM), 2.40, 2.69 radios. 2.25 seems the best of them all for me. Signal sucks, but call quality is about the best.
Any direction would be appreciated!
yo
dude that's like an added bonus no? you can use that to your advantage say you've went into the space program
seriously though i've tried them all (i'm on ATT) and I stick to 2.25 here in the middle of the USA, I get full bars just about everywhere, i've no doubts that each radio rom has different traits with physical location as well.
Sorry, forgot to mention that when I do have full bars in major cities, the sound quality does not improve.
same problem with me... any ideas?
jr_daza said:
same problem with me... any ideas?
Click to expand...
Click to collapse
Can you elaborate a little more on "YOUR" situation. ROM version, radio version, what you have done...
Went back to original TMO 2.26.10.2 and problem disappears. Copied audiogain settings and went back to XM6r2a. Still no go. I am using the same radio, 2.25.11 as in the TMO 2.26.10.2.
Is there a thread about all the reg keys that deal with the phone/radio?
When I search on phone & radio, it brings up everything but what I'm looking for.
Moderators: Is there a way to have the system not search signatures? Many users have "Radio:" in their signature and it seems like it is pulling on that also. I have been searching each sub-forum individually and it seems like I'm getting at least 1000 hits per search. Also, I show posts, not threads. Thanks!
ndoeberlein said:
Can you elaborate a little more on "YOUR" situation. ROM version, radio version, what you have done...
Click to expand...
Click to collapse
SORRY GUYS..
the people I speak with say that they hear me too bad
i'm using rom blakdaimond 3.1 radio 02.07.10
no other software by now
jr_daza said:
SORRY GUYS..
the people I speak with say that they hear me too bad
i'm using rom blakdaimond 3.1 radio 02.07.10
no other software by now
Click to expand...
Click to collapse
Have you tried having someone call you on a land line to see if it's just quiet, warbly, or cut's in and out?
ndoeberlein said:
Have you tried having someone call you on a land line to see if it's just quiet, warbly, or cut's in and out?
Click to expand...
Click to collapse
what I tried was call my mobile from a land line and put some comversation with good resulst in quiet emviroment but when the place was noise i cant hear a thing
Same problem here. The most frustrating part is the audio on my end sounds fine and is intermittent on the recipients end. Friends tell me it's so bad I should throw out my cheap phone! I've tried 2.19, 2.25 and 2.69 with various 6.0 roms (XDA, TNT, Black Diamond and others) applied Cingular radio hacks and still have the problem. I had to send back the phone for an unrelated reason and it's the same with the replacement. It doesn't seem to be signal strength related and can come and go during a conversation. I don't think it happens with the stock rom but it's so painful to use I've only had it loaded for a few hours. Went back to 2.25 and applied the audiogain hacks above. Will let you know how it goes.
Problem solved... at least for me
Going through the registries of both TMO 2.26.10.2 and 5.2.318's, I found that the GSM codec is being replaced with MSG711. I'm assuming Microsoft's implementation of G.711, probably to support VOIP as well. Since I pulled VOIP when I customized mfrazzz's rom, it's not a concern for me.
I'm assuming that the people who aren't having problems are on a completely EDGE network, where I'm still on many GPRS towers. I don't think that directly has an implication; however, I'm sure providers have greater bandwidth going to towers that handle EDGE, thus the EDGE tower is less likely to go to full capacity, and can handle extra bandwidth.
GSM Codec: http://www.voip-info.org/wiki-GSM+Codec
G.711 Codec: http://en.wikipedia.org/wiki/G.711
Below are the reg fixes that helped me. I flashed TMO 2.26.10.2, then my modified mfrazzz, then applied the reg fixes. Echoing and Deathstar-spaceshuttle voice on the other end has disappeared, and I only had one bar with radio 2.25.11. Haven't tried other radio's yet, and not sure I will for a little while until I know this solved the problem.
Hope this helps!
Reg Fixes:
[HKEY_LOCAL_MACHINE\Drivers\Active\07]
"Hnd"=dword:0003EBC0
"Name"="ACM1:"
"Key"="Drivers\\BuiltIn\\CODEC_GSM610"
"BusParent"=dword:00032400
"InterfaceType"=dword:00000000
"BusName"="BuiltInPhase1_0_43_0"
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\CODEC_GSM610]
"Flags"=dword:00000002
"Order"=dword:00000000
"Index"=dword:00000001
"Dll"="gsm610.acm"
"Prefix"="ACM"
looks like it work, i just chang the registry like you say and i think that works
im going to reflash the phone and see what the other people say
tks a lot
*** IMPORTANT NOTE ***
In the reg key: [HKEY_LOCAL_MACHINE\Drivers\Active\07]
07 is the location under Active where it sits for "ME" after loading my modified mfrazzz and using radio 2.25.11 that's there from the TMO 2.26.10.2 original install. When I applied 2.69.11 for testing, it moved to 02. It moved the contents completely; however, if you apply the reg fix and it's not at 07, it won't solve your problem.
Good rule of thumb would be to check this registry entry manually to verify its location, make any adjustments if needed, then run the fix.
SOLVED - I ended up flashing to the 1.64.08.21 Radio, then Dutty's Latest. Now GPS works. WEIRD!!!!
Hello,
Back story: I'm running Q-Mobile 1.2, all is well, GPS works fine because I used it all the time. Then I had family in town, took some photos using the GPS photo option, didn't work. I filled it away under the curious and just got around to testing.
GPS Test now can't find my device, keeps reading "Searching for GPS Device", HTC GPS Testing tool just stares blankly at me like I have the answers.
Live search GPS doesn't work.
Google Maps GPS doesn't work.
What I've done to try and fix:
I reflashed the 1.27.14.09 radio... didn't change anything.
I reflashed the entire Q-Mobile Rom... didn't change anything.
I tried Dutty's new WM 6.1 Rom... didn't change anything.
I tried Alex's ROM... didn't change anything.
Tried the "new" AT&T Rom from the HTC site... didn't change anything.
I'm back to Q-Mobile, still doesn't work.
There is no reason why the GPS should not be working, the phone hasn't been physically damaged in anyway, everything else works fine.
I'm at my wits end, I need some outside help/guidance. Can ANYONE please help? Everything I've searched for and come up with so far hasn't worked.
As always, any help is GREATLY appreciated!!!
thats funny, because my GPS has been randomly working and not working these past few days....2 days ago it wouldnt pick up a signal at all, yesterday very strong signals, today, dead again......not sure whats wrong...
This is strange.... because a friend just lost his GPS also. He's using a 6.0 based ROM with various radios tested.
He's using a Tilt varient.
Could this be some sort of AT&T issue?
(I run the same ROM as him -I flashed it myself- and am also on AT&T with no problems.... yet)
GPS seems to be location dependent.
But here's my thought : if you want to use WM 6.0 then flash to Radio 1.27.
For WM 6.1 then flash to Radio 1.58.
Don't forget to change the Quick GPS Region in registry & then run it.
Hope that can help.
Dihon said:
GPS seems to be location dependent.
But here's my thought : if you want to use WM 6.0 then flash to Radio 1.27.
For WM 6.1 then flash to Radio 1.58.
Don't forget to change the Quick GPS Region in registry & then run it.
Hope that can help.
Click to expand...
Click to collapse
my region is set to US in the registry.....not sure that its the problem, because it worked perfectly fine w/ these settings before...
Yeah, my GPS as well. At first i worked perfectly. I used Google map and locate me, I show the exact position where I was. Then yesterday and today, my point have been moved further where I'm. And then I tried TOMTOM, and the performance is kinda slowe than before.
I'm using Radio 1.64.08.21, and UDK-7 R2
okay so i just went out to test it again, and ran GPS tool at 4800. I let it go for 2-3 minutes and eventually, it found a fix on about 12 satallites. after that, tom tom locked my location really fast, like a charm.....
give that a try.....if you just flashed, initial gps fix might take some time...
Alright, I'm going to try Dutty's latest again, only this time w/ the 1.64.08.21 radio... I'll see if that matters. I'll post when done.
UPDATE: http://forum.xda-developers.com/showthread.php?t=365058
I installed the ROM on this thread as a test. ROM sucks bizzalls, but GPS Test if finally working! I'm going to flash Dutty's latest overtop, it should keep the radio but put his ROM down. More to follow.
Dihon said:
GPS seems to be location dependent.
But here's my thought : if you want to use WM 6.0 then flash to Radio 1.27.
For WM 6.1 then flash to Radio 1.58.
Don't forget to change the Quick GPS Region in registry & then run it.
Hope that can help.
Click to expand...
Click to collapse
Please post the registry string that changes the demobraphics to the US. Thanks.
Do we have a listing of these location codes as the US is a big place and it might have more than 1 code depending on location.
Can people post what they have in the registry of:
[HKEY_LOCAL_MACHINE\Software\HTC\QuickGPS]
The value of :
"region"="--"
I tried GB in mine (United kingdom) as another user (Dutch had reported using NL in theirs and GB is our equivalent. It definately seemed to lock faster.
I am using Dutty's latest rom and the region was Blank in after the flash, hard reset and setup.
Does the quick gps download different data depending on region or does it download all of them but start the search based on which should be the closest satellites based on the location setting in the registry. I presume once it has gained its locks it remembers for next time. (I think this remembered data is valid for 4 hours).
There are only about 28 satellites in total and up to a maximum of eight to eleven depending on time a(s the satellites are not geostationary) being visible at one time
Regards
Chapelhill
I used Dutty's WM6.1, ran QuickGPS then got a fix (took very long the first time) ... now my registry says Region=US
I noticed that there is another key that might be of interest:
curRegion = 0 (00000000)
Could this be current Region?
I've changed the region in the registry from "--" to "SE" (Sweden), but the string won't stay put. After a reboot and running QuickGPS, it goes back to "--". I've tried waiting a couple of hours after editing and holding the power button to shut down, but it doesn't help. I made a little MortScript and added it to startup:
Code:
While (1)
WaitFor ("QuickGPS", -1)
If NOT regKeyEqualsString ("HKLM", "Software\HTC\QuickGPS\", "region", "SE")
RegWriteString ("HKLM", "Software\HTC\QuickGPS\", "region", "SE")
EndIf
Sleep (10000)
EndWhile
This works and keeps the "SE"-setting, but having the script running constantly isn't exactly optimal as it uses processing power (around 4% currently) and thus adding to battery-drain. Anyone have any ideas on a different way of making the script, which is more effective/power-saving? Or is there an even better way to make the registry key stick?
I am having some GPS issues as well but not as bad as GPS not working. Two problems have been bugging me: Getting a slow GPS fix and my location seems offset. I am using CoPilot Live 7 for my navigation software. It shows me a little bit 'off' from my current location. I am using 1.58.26.20 radio. Should I change my radio? Do I have to change the radio first and then reflash Dutty again?
- TKN
coolVariable said:
I used Dutty's WM6.1, ran QuickGPS then got a fix (took very long the first time) ... now my registry says Region=US
I noticed that there is another key that might be of interest:
curRegion = 0 (00000000)
Could this be current Region?
Click to expand...
Click to collapse
That's interesting, mine says US but "1" for the numeric one.
=====
Update
=====
I'm updating this thread so I don't spam the board.
After trying all kinds of software solutions, resets and all I gave up. It's a hardware problem (as far I can tell) and there is no way to fix it unless you replace one board on the phone.
This is how I found the problem:
I got another shadow from eBay with a broken screen but working wifi.
I swapped the main board and guess what? No wifi. The only thing I could think is that the other board on the phone, the one connected to the screen and circle pad thing was the problem and probably were the wifi part of the phone resides on.
Once I replaced that part the wifi worked with both boards.
If anyone is a hardware expert or just for curiosity want to see some pictures from both working and non-working boards, PM me.
=========
Original Post
=========
Hello guys, I got a T-mobile Shadow and I can't get the wifi to work. On the wireless info says "driver not loaded".
I tried to re-flash it with the original firmware several times (ok... 4 times).
I tried to use the beta version of wm6.1.
I tried to reset and hard-reset the phone over and over.
I tried to put the "wifiinit.lnk" on my startup folder and even run wifiinit.exe.
I tried to mtty it to check for bad nand block but the commands will not work (info 8). This password will work -> BsaD5SeoA
I can't return it to T-mobile because it was a phone with a broken screen that I bought from eBay.
So this is my last resort before I give up on wifi:
Does anyone know anything I could do to try to fix it?
Thanks
This is kind of an expensive solution, and should be used as last resort, you could try getting a WiFi MicroSD card. I'm guessing only the WiFi radio is having problems even though it says it's the driver.
Thanks ND4SPD for the reply.
I also think it's something wrong with the radio part and I guess as long t-mobile don't release an update I will stuck without wifi.
Keep the good work with the 6.1 rom!
I'm using it right now, so long neo interface!
P.S.: If someone find a solution please post it here.
I just looked up some stuff and found that there are quite a few people have had the same problem after updating to tmobiles update. The only two suggestions they had were to hard reset or try the update again.
I have one idea: flash my shadow with the original rom. The only problem is how to get the original rom? I know that there is the raw dump. Is there a way to make it flasheable?
edit:
Just did, I was able to flash it to the first firmware using the files @ ftp.
But still the same thing, no wifi.
I'll keep looking for a solution for this.
Could someone post this reg info from a wifi working shadow?
Code:
[HKEY_LOCAL_MACHINE\Comm\TNETW12511]
"Wireless"=dword:00000001
"ImagePath"="TNETW1251.dll"
"Group"="NDIS"
"DisplayName"="IEEE 802.11b/g Compatible Wi-Fi Adapter"
[HKEY_LOCAL_MACHINE\Comm\TNETW12511\Parms]
"InstanceNumber"=dword:00000000
"PowerSavePowerLevel"=dword:00000000
"defaultPowerLevel"=dword:00000000
"DSCPClassifier03_DTag"="7"
"DSCPClassifier03_CodePoint"="56"
"DSCPClassifier02_DTag"="5"
"DSCPClassifier02_CodePoint"="40"
"DSCPClassifier01_DTag"="1"
"DSCPClassifier01_CodePoint"="8"
"DSCPClassifier00_DTag"="0"
"DSCPClassifier00_CodePoint"="0"
"NumOfCodePoints"="4"
"IPPortClassifier02_DTag"="6"
"IPPortClassifier02_Port"="5003"
"IPPortClassifier02_IPAddress"="0a 03 89 02"
"IPPortClassifier01_DTag"="4"
"IPPortClassifier01_Port"="5002"
"IPPortClassifier01_IPAddress"="0a 03 89 02"
"IPPortClassifier00_DTag"="1"
"IPPortClassifier00_Port"="5001"
"IPPortClassifier00_IPAddress"="0a 03 89 02"
"NumOfDstIPPortClassifiers"="3"
"Clsfr_Type"="1"
"QOS_wmePsModeVO"="0"
"QOS_wmePsModeVI"="0"
"QOS_wmePsModeBK"="0"
"QOS_wmePsModeBE"="0"
"desiredPsMode"="1"
"RatePolicySGRetriesPerRateOfdmA"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicySGRetriesPerRateOfdm"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicySGRetriesPerRatePbcc"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicySGRetriesPerRateCck"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicyUserRetriesPerRateOfdmA"="0,0,0,1,0,0,1,0,0,1,0,0,0"
"RatePolicyUserRetriesPerRateOfdm"="0,0,0,1,0,0,0,1,0,0,1,1,1"
"RatePolicyUserRetriesPerRatePbcc"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicyUserRetriesPerRateCck"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicyUserLongRetryLimit"=dword:0000000A
"RatePolicyUserShortRetryLimit"=dword:0000000A
"RateAdaptationTimeout"=dword:0000012C
"FBLongInterval"=dword:000000C8
"FBShortInterval"=dword:00000028
"RateStepUpThreshold"=dword:00000002
"RateContThreshold"=dword:0000000A
"Beacon_IE_Table"="00 01 01 01 32 01 2a 01 03 01 06 01 07 01 20 01 25 01 23 01 30 01 28 01 2e 01 85 01 dd 00 52 f2 02 00 01"
"Beacon_IE_Table_Size"=dword:00000035
"Beacon_IE_Num_Of_Elem"=dword:00000015
"Beacon_Filter_Stored"=dword:00000001
"Beacon_Filter_Desired_State"=dword:00000000
"ArpIp_Addr"="c0 a8 00 5e"
"ArpIp_Filter_ena"=dword:00000000
"DtimListenInterval"=dword:00000001
"BeaconListenInterval"=dword:00000001
"HTCActiveSyncReconnectWorkaround"=dword:00000001
"dot11AuthenticationResponseTimeout"=dword:000001F4
"dot11MaxAuthRetry"=dword:00000002
"dot11DesiredChannel"=dword:0000000B
"AutoPowerModeDozeMode"=dword:00000002
"ShortSlotTime"=dword:00000000
"Mode4x"=dword:00000000
"MixedMode"=dword:00000000
"SpectrumManagement"=dword:00000000
"MultiRegulatoryDomain"=dword:00000000
"WME_Enable"=dword:00000001
"HTCWiFiLogoMICWorkaround"=dword:00000000
"TxPower"=dword:00000001
"PowerMgmtHangOverPeriod"=dword:00000005
"RSNPreAuthentication"=dword:00000001
"RecoveryEnable"=dword:00000000
"HTCAutoOffInterval4NoActivity"=dword:00002710
"HTCAutoOffIfNoActivityEnable"=dword:00000001
"MinimumDurationBetweenOidScans"=dword:00000005
"FirstConnScanEnabled"=dword:00000001
"WPAMixedMode"=dword:00000001
"RxBroadcastInPs"=dword:00000001
"HTCOutputWLANdebugLog"=dword:00000000
"BThWlanCoexistParamssgAntennaType"=dword:00000002
"BThWlanCoexistParamsnumberOfBtPackets"=dword:00000002
"BThWlanCoexistParamsnumberOfWlanPackets"=dword:00000004
"BThWlanCoexistParamssenseDisableTimer"=dword:00000320
"BThWlanCoexistRate"="0,0,1,0,0,1,1,1,0,1,1,1,1"
"BThWlanCoexistEnable"=dword:00000001
"dot11RTSThreshold"=dword:00001000
"dot11FragmentationThreshold"=dword:00001000
"dot11ShortPreambleInvoked"=dword:00000001
"HTCPreloadLEAP"=dword:00000000
"HTCGetIPWorkaround"=dword:00000001
"HTCAutoOffTimeout"=dword:0001D4C0
"HTCAutoOffMode"=dword:00000000
"HTCPowerMode"=dword:00000002
"ResetOnResume"=dword:00000000
"SysIntr"=dword:0000002B
"BusType"=dword:00000000
"BusNumber"=dword:00000000
Thank you
Maybe I can help.
Dump the file bk_02_0005.img as described here
Hey jockyw2001, thank you for the help.
Here is the file you asked: http://www.lgsilva.com/bk_02_0005.rar
It's a hardware problem. The wlan configuration data integrity is fine, TI chip is recognized. Maybe you should open it up and check if the wlan/BT antenna is properly connected.
Thanks jockyw2001 for your help. I'll try to check the phone but the thing is... the BT works fine. I just can't enable the wlan on the comm manager.
See first post for update (bump).
thx for your update!
Have you noticed a little battery on the board u replaced? It's right under a piece of tape. Please measure the voltage. I suspect it ran out of power on the board u replaced.
Jocky and I spent the entire day trying to resolve this wifi problem.
Unfortunately we have completely disproven your method - it is impossible for your mainboard to work with the non-original daughter board / flexcable.
This board contains your wifi components - they communicate with the main board. The main board firmware is married to the mac address of the wifi controller on your daughterboard. Unless you updated your firmware, your board would never work unless using the board that was originally delivered with the mainboard.
We spent alot of time testing this theory as you threw us off with the mis-information you provided. In the end, we needed to update this thread as it is invalid.
We are now working on tools to read the config of the wifi chip and update the firmware to re-create the married set if you ever need to change this board or your firmware gets corrupted.
Well I flashed from JF ADP1.1h to JF RC33 to get paid apps (IT WORKS!!!) but now I have a major problem that isn't even worth paid apps to me. For whatever the reason, now whenever I make or receive a call, not matter what number it's from, I get a message that says the phone app force closed and even though I can continue to hear the conversation perfectly in the background it locks up and I can do nothing. But wait, it gets better... After I click force close then the radio shuts off and it goes into airplane mode until I go into settings and un-check the airplane mode option. Weirder though is how the statusbar signal icon just shows the no signal icon and not the airplane mode icon. What is the problem? I'm on AT&T on a real Dev Phone. Do I need to wipe? I really don't want to but if I absolutely have to I guess I can... Thanks for all your help!
I had the same issue on the same path (holiday to RC33). I just ended up wiping the phone and it recovered fine. I assume there is some setting in the user data that is incompatible with 33 that it doesn't like. I suppose you could try to find and remove the data that is causing it; I looked into attempting to wipe its specific sql table(s) but didn't know the first place to start.
the same happens to me (still). it happened more when i updated to the rc33 radio.
tried to do a wipe as most suggested. but to no avail. now it even happens when i
get a text message while using the phone. i've just decided to deal with it for now.
try this radio
i recently discoverred that a few of the radios for the Kaiser in the "ultimate radio thread" under Kaiser ROM Developement work on this phone. specifically 1.71.09.01 i use that radio on my phone and i get much better service and i also download twice as fast as before. if you want to flash the radio to your phone all you need to do is the following:
1. go find that thread and click the download mirror to get the radio in .zip format
2. extract the files to any directory
3. open the .nbh file in a hex editing program of your choice
4. do not edit the file but rather save it as "radio.img"
5. download the radio update.zip from JesusFreke in his thread
6. drag and drop the radio.img that you created into the update.zip
7. sign the update.zip and place it on your SD card
8. flash it to your phone
i would upload my update.zip but as i am using the G1 as a tether right now it takes too long and i am impatient. also i'm sure you can just flash the .nbh file after naming it to DREAIMG.nbh but i have not tried that. good luck to you all
Do you think that flashing the radio the kaiser one would start roaming outside of tmobile network for calls and data? Is tmo going to charge for roaming ?
Thanks
Any way we (I) could get you to upload the update.zip when yer not tethering lol?
yeah i'll probably go to burgerking in a bit and steal their wifi to upload this to my 4shared and to xda
here is my 4shared link to the file, you just need to rename to update.zip
http://www.4shared.com/file/90746312/7608bece/1710901.html?dirPwdVerified=1125b7c0
it seems to be too big to upload to xda
I applied the update.zip and went through the motions and let it flash and then checked the version and it's still the one from JF1.43 version 1.22.14.11 baseband.
So, I tried it again and same thing. I didn't see it say anything about the image not being valid. It looked like it applied it but appears that it didn't.
Same problem here...force close when in call and receive another call or text message. I applied the above update and still have the force close. Thanks in advance for any help.
Not sure what happened, when I looked at my setting I see the same radio, but when I flash the rc33 update and run 5 speedtests I consistently get between 40kb/s and 104kb/s when I flash my update it get between 90 and 200 consistently, I would think that means I have a better radio, I am not moving from my spot and the phone sites in the same place for all the tests. Hopfully I can figure this out and help you guys with your problems
Well for me a wipe seems to fix it. I just got over losing the texts. They were sentimental but I cleared it anyway. So my advice either use MyBackup or just get over it and wipe lol
Well, I've tried the radio change and two subsequent wipes and I still have the force closses. Any other ideas? Thanks again.
Installing the zip file worked for me, in that I don't get force closes, but no 3G on AT&T at all, unless 3G in this area is 80-160kbps...
Sorry but you won't get AT&T's 3G on your phone... the G1 or ADP1 will not work on AT&T's 3G.
I heard that the only theoretical way to fix this would be to replace a chip on the inside, but this would require you MAJORLY hardware hack your G1.
tubaking182 said:
Not sure what happened, when I looked at my setting I see the same radio, but when I flash the rc33 update and run 5 speedtests I consistently get between 40kb/s and 104kb/s when I flash my update it get between 90 and 200 consistently, I would think that means I have a better radio, I am not moving from my spot and the phone sites in the same place for all the tests. Hopfully I can figure this out and help you guys with your problems
Click to expand...
Click to collapse
What is a good speed test to use? I have been going to my3gspeed.com and am getting 2.5mbps (320kBps) for download speed rather consistently. Here I thought my connection was slow...
Upload is 224kbps (28kBps)
I'm just wondering how accurate the test is because browsing web pages does not seem that fast...
Well, Over the last few days I've seen more and more reports of "no service" and "unknown" service issues. Where you cant make or recieve calls, or text,and you are only getting data on lte.
" This will work to manual program a vzw phone also if you choose the one that has VZW.only in its name"
The LG LS997 V20 seems to have lost the ability to edit your PTN and MSID under ##786# method, and ive verified they also removed
##6DigitMSL# code. This eliminated the usual route to manually program your phone and get talk and text back without the network sending a update.
Heres the fix
Download Shortcut Master Lite From the playstore
Link here :
https://play.google.com/store/apps/details?id=org.vndnguyen.shortcutmaster.lite
and once downloaded you need to go to the search option and search
iot.cdmasettings
Then you need to click Launch on that one you searched..
Click:
CDMA PREFERENCES
Then:
NAM settings
Then Enter these things
MDN = Your Phone number
HOME SID = 4139
MCC = 310
MNC = 00
MIN2 = YOUR AREA CODE
MIN1 = MSID ( need to get from sprint or sprint.com chat ask for msid )
IMSI_MCC - 310
IMSI_MNC = 00
S2 = 000
S1 = 0001370
then back out and let it reboot,
for some this is a soft fix, for some this may be all you needed- it dosn't address the full issue, but this will at-least get you started to recovery.
Confirmed this worked on my LS997. Awesome Dev took several hours out of his day to troubleshoot this and get a fix.
screenshots added ++++ sorry text is small, i had to remove my personal info from the photos. Just use photos as reference for the text in op!
Hope this helps a few out, im still working on finding a 100% resolution to why this even came out as a issue. I'm almost certain your modem is NOT the issue, but a issue with provisioning and the way your phone is getting updated/or received a bad update
please continue to provide feedback and info related to when this 1st happens so i can figure out the main source.
stenomatic said:
Confirmed this worked on my LS997. Awesome Dev took several hours out of his day to troubleshoot this and get a fix.
Click to expand...
Click to collapse
Def worth the time man. You made it 10x easier being direct and following the info to the T.
EXACTLY what needed to be done for a positive resolution!
:good:
you can also go to the same place by searching msl.
and clicking the bottom one of the 2 that show up, click edit, and put in your ptn click okay the the full msid then okay. once done you need to reboot.
I don't think I'm having any issues other than I seem to experience more areas where I lose service than I did before I rooted.
When I searched for iot.cdmasettings - nothing came up.
I then searched for cdmasettings and again nothing came up.
I then searched for iot and a bunch of stuff came up. I noticed the 2nd. item from the top had iot/cdmasettings so I clicked that one.
My S1 is 0000375
I wonder if MSID is the same as MSL?
The link to the app above didn't work for me.
Try this one - https://forum.xda-developers.com/showthread.php?t=2800117
Jack
midmadn said:
I don't think I'm having any issues other than I seem to experience more areas where I lose service than I did before I rooted.
When I searched for iot.cdmasettings - nothing came up.
I then searched for cdmasettings and again nothing came up.
I then searched for iot and a bunch of stuff came up. I noticed the 2nd. item from the top had iot/cdmasettings so I clicked that one.
My S1 is 0000375
I wonder if MSID is the same as MSL?
The link to the app above didn't work for me.
Try this one - https://forum.xda-developers.com/showthread.php?t=2800117
Jack
Click to expand...
Click to collapse
No.. Your msid is a number sprint uses to provision.
I work for sprint.
Are you on sprint and using my rom?
This only applies to sprint users.
Team DevDigitel said:
No.. Your msid is a number sprint uses to provision.
I work for sprint.
Are you on sprint and using my rom?
This only applies to sprint users.
Click to expand...
Click to collapse
If you call or go online sprint will give you msl, and your msid
Msl is master susbsidy lock code (××××××) 6 digit
Msid is semilar to your phone number (×××-×××-××××)10 digit
Team DevDigitel said:
No.. Your msid is a number sprint uses to provision.
I work for sprint.
Are you on sprint and using my rom?
This only applies to sprint users.
Click to expand...
Click to collapse
The rom I am running is 5.0 or F I think I have seen it referred as. Not sure if it's yours but if it is - Thank You very much for all you have done for us poor left out sprint users. I downloaded a newer version (6.0) but not sure if I want to install it or if I'll gain anything.
midmadn said:
The rom I am running is 5.0 or F I think I have seen it referred as. Not sure if it's yours but if it is - Thank You very much for all you have done for us poor left out sprint users. I downloaded a newer version (6.0) but not sure if I want to install it or if I'll gain anything.
Click to expand...
Click to collapse
i would clean install version 6.5 phh
the majority of us are running it now.
Its stable and soild, and will pass safetynet,
im unsure why you dont have the hidden menu stuff, 6.5 phh should.
update to that and see if its any better.
we may need to get people to backup their radio and see what ones work better.
im on the oldest radio
I made a mistake. I was going to install F but ended up going with J.
6.5 PHH is all downloaded. I'll give it a try.
Thank You very much.
Can u check which version has the stuff to manually program 6.5 phh when i search and find iot.cdmasetting and hit launch in shortcut master it does nothing...
Edit
Nevermind the 6.5 isn't rooted to begin with...I had
A 6.01 back up that works fine
Sent from my LG-LS997 using Tapatalk
nexus6r3plicant01 said:
Can u check which version has the stuff to manually program 6.5 phh when i search and find iot.cdmasetting and hit launch in shortcut master it does nothing...
Edit
Nevermind the 6.5 isn't rooted to begin with...I had
A 6.01 back up that works fine
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
? both 6.5 versions have root, you must be dirty flashing or doing something else.
2 versions of 6.5 bud.
phh root witch is built into magisk,
and supersu root witch is a seperate app.
5.5 and 6.5 both are exactly the same, minus using magisk manager.
I didn't download phh app but it wouldn't request root on 6.5 so I just used a back up
Sent from my LG-LS997 using Tapatalk
nexus6r3plicant01 said:
I didn't download phh app but it wouldn't request root on 6.5 so I just used a back up
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Didn't need any apps. Its built into magisk for root.
Thats the build im using as my daily. Root takes a min to setup as the 1st 15min after boot its still optimizing and doing commands.
Im 100% sure the no calls and text bug comes from using a aosp rom and changing nv info. Knocked me off service all day and didnt know.
Lost my ptn and my msid
Also got hit with a error code 16 and had to speak to the networks solution dept.
Maybe a tad bit more help...
I followed every step the only issue I've noticed is I can now make calls but only when I turn roaming on. If I just connect to the sprint network I get data but it says mobile network unavailable when trying to make a call. Any ideas?
kdouvia said:
I followed every step the only issue I've noticed is I can now make calls but only when I turn roaming on. If I just connect to the sprint network I get data but it says mobile network unavailable when trying to make a call. Any ideas?
Click to expand...
Click to collapse
Can you go under
settings
General
About
Status
What prl do you have?
Team DevDigitel said:
Can you go under
settings
General
About
Status
What prl do you have?
Click to expand...
Click to collapse
I have PRL 162. It's odd because I only receive calls and can make them if set to roaming. If I'm set to roaming to make calls I can't update PRL only when connected to just LTE
kdouvia said:
I have PRL 162. It's odd because I only receive calls and can make them if set to roaming.
Click to expand...
Click to collapse
Thats why, try a update prl and see if it changes. Do it on wifi if it dosnt work try on lte/3g
162 is not a sprint prl
you need PRL 54022 or 54xxx
any version really 54 whatever will work.
if prl update wont change it the only other idea would be
##diag# put into diag mode and use a tool like cdma workshop or similar to push the prl to your phone.
[email protected] is my hangouts email. We can speak more about this but talking about NV items and the tools that work with them
is a grey area on xda. I can not share my version of cdma workshop as its a paid for version linked only to my pc. There are free versions and tutorials out there on how to connect to a phone in diag mode and use cdma workshop or any other es tool to do the prl push
Team DevDigitel said:
Thats why, try a update prl and see if it changes. Do it on wifi if it dosnt work try on lte/3g
162 is not a sprint prl
you need PRL 54022 or 54xxx
any version really 54 whatever will work.
if prl update wont change it the only other idea would be
##diag# put into diag mode and use a tool like cdma workshop or similar to push the prl to your phone.
[email protected] is my hangouts email. We can speak more about this but talking about NV items and the tools that work with them
is a grey area on xda. I can not share my version of cdma workshop as its a paid for version linked only to my pc. There are free versions and tutorials out there on how to connect to a phone in diag mode and use cdma workshop or any other es tool to do the prl push
Click to expand...
Click to collapse
Thank you