Unstable 3G/H connection but 2G and Wi-Fi are fine - Hero, G2 Touch Q&A, Help & Troubleshooting

Ok all here is my problem and I know there many more suffering from this:
Connecting to the internet from my Hero works fine on 2G (GPRS) and Wi-Fi, but is very unstable on 3G (UMTS) and H (HSDPA).
By starting a thread, I want to get to an answer as to WHY this is happening and hopefully find a solution
My problem started around the time I started using custom 2.1 (or radio) ROMs, but I am not sure whether flashing those is actually the cause. I have a SIM unlocked Hero and an unlimited data plan with T-Mobile Netherlands (called Web 'n' Walk Plus @ 1 Mbit/s down, 384 Kbit/s up). I had no problem on the stock 1.5 ROM/radio.
Symptoms:
Whenever an app is making a server request, the 3G icon starts blinking the up arrow, shortly followed by the H icon blinking the up arrow, indicating the request is made.
When all is well, the response is received and communication is quick and smooth. Most of the time though, the phone continues making requests but no response is received and the application reports a network error/timeout. This happens while signal strength is max (4 bars).
Ping test:
Enter *#*#INFO#*#* in the phone dialpad and select Phone Information, press the "Run ping test" button.
- The line "Ping IpAddr" reports: "Fail: IP addr not reachable";
- The line "Ping Hostname(www.google.com)" reports: "Fail: Host unreachable";
- The line "HTTP Client test" reports: "Fail: IOException".
The preferred network type is "WCDMA preferred", as set in the lower part of the same screen.
Note: WCDMA is an air interface standard used for UMTS and the like and is not related to CDMA, which is the mobile access technology used in the USA as opposed to GSM, which is used everywhere else in the world.
The thing is though, that the connection does not seem to fall back to 2G but rather experiences a timeout.
FWIW: the Phone Information screen reports a signal strength of -dBm, 25 asu.
Tried:
- Flashing various ROMs to spot any difference, none found.
- Flashing newer radio ROM (JU instead of EU), no luck.
It is here when I first start posting about it:
http://forum.xda-developers.com/showthread.php?p=6099325#post6099325
Other cases that seem to point at the same problem:
http://android.modaco.com/content/h...93937/hero-strange-3g-data-connection-problem
http://forum.xda-developers.com/showthread.php?t=547563
http://forum.xda-developers.com/showthread.php?t=616475
http://support.t-mobile.co.uk/discussions/index?page=forums&topic=8010384abbabde01276d5f3caa005e2d
I hope that anyone experiencing the same post his or her findings, so that we can try to detect a pattern and maybe the solution to this.
UPDATE: Apparent solution for T-Mobile 3G problems:
http://forum.xda-developers.com/showthread.php?t=595108
Fix includes settings as proposed by adwinp below.
Explanation of some settings: http://forum.xda-developers.com/showpost.php?p=5123531&postcount=46
UPDATE 2:
Well, my problems have vanished "as snow in the sun" (old Dutch proverb)!
Applying the latest radio (JU) and the settings as mentioned by adwinp below made my 3G connection fly again, steady and smooth. Thanks adwinp!
How to modify your build.prop file:
1) Connect your handset via USB, make sure USB debugging is enabled
2) From the Android SDK > tools directory, type the following:
Code:
# adb pull /system/build.prop ~/build.prop
3) Open the file with your favorite editor and append the following lines:
Code:
ro.ril.enable.dtm=1
ro.ril.hep=1
ro.ril.hsxpa=2 #for USA, use 1
ro.ril.gprsclass=12 #for USA, use 10
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.ril.hsdpa.category = 28
ro.ril.hsupa.category = 7
Save the file. Next:
Code:
# adb remount
# adb push ~/build.prop /system/build.prop
# adb reboot
Some sources claim that a second reboot is necessary, check this for yourself.
Good luck!
UPDATE 3:
Seems my joy was short lived; could be that just rebooting was a temporary fix and a good old placebo effect, since I already experienced connection loss again. Sigh. Anyone else with a good idea?
UPDATE 4:
Could this be an MTU issue, like stated here or here? I'd like to know the methods of changing the MTU for 3G, investigating now.
UPDATE 5:
None of the theories above seem to be plausible. Looks like T-Mobile/Orange is the culprit here. Further reading here: https://t-mobile-forum.pocketinfo.nl/showthread.php?p=725207#last (in dutch)

You have either a
1: physical problem with the handset
2: network problem (check if other ppl within the same network have the same problem)
Try playing with these values in /system/build.prop
ro.ril.enable.dtm = 1 # you might want to disable this one, although it doesn't hurt
ro.ril.hep = 1
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.ril.hsdpa.category = 28
ro.ril.hsupa.category = 7
# Default network type 0 => WCDMA Preferred.
ro.telephony.default_network = 0
These settings come from my ROM, which has been tested on various networks in Poland, Germany and Mauritius.
3G performance is flawless.

I have been having this very same problem, and I know others have too. it is strange but has only happened since the newer 2.1 builds have been out.
After lengthy conversations with the high technical team at Orange UK they diagnosed my problem as for some reason the phone is trying to connect to two 3g radio towers at the same time (usually should connect to only one) basically this is confusing the phone.
What the fix seems to be is:
- *#*#4636#*#*
- phone options
- ping test (will probably fail)
- change to "GSM ONLY" - for 30 seconds or more NOT LESS!!
- ping test (should succeed)
- then change back to "WCDMA Only" or "preferred"
- ping again (should now work)
If this does not fix it then you have two more options
- take the sim out the phone for 30 seconds (this is the minimum required time to disconnect your phone from the towers your on)
- OR airplane mode for 30 seconds.
Then try the above again and all should be working.

adwinp said:
Try playing with these values in /system/build.prop
Click to expand...
Click to collapse
As a professional software developer, I always get an itch when I am advised to 'try playing', I need to know if something is working or not
ro.ril.enable.dtm = 1 # you might want to disable this one, although it doesn't hurt
ro.ril.hep = 1
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.ril.hsdpa.category = 28
ro.ril.hsupa.category = 7
# Default network type 0 => WCDMA Preferred.
ro.telephony.default_network = 0
Click to expand...
Click to collapse
Do you have any reference information for these settings? I'll try to look it up myself but I can't fiddle with them unless I know what the possible values are and at least know what each setting is used for

Lennyuk said:
After lengthy conversations with the high technical team at Orange UK they diagnosed my problem as for some reason the phone is trying to connect to two 3g radio towers at the same time (usually should connect to only one) basically this is confusing the phone.
Click to expand...
Click to collapse
Interesting reason; you think this could be related to the fact that the latest VillainROMs stem from CDMA ROMs? What I still don't get is that speech and GPRS traffic are unaffected, these just work.
I already tried your fixes several times but for me they don't work everytime. Ah well, hopefully the official 2.1 update does some good here

j0bro said:
Interesting reason; you think this could be related to the fact that the latest VillainROMs stem from CDMA ROMs? What I still don't get is that speech and GPRS traffic are unaffected, these just work.
I already tried your fixes several times but for me they don't work everytime. Ah well, hopefully the official 2.1 update does some good here
Click to expand...
Click to collapse
Possibly however my problems first seemed to start after the Legend based roms.

j0bro said:
Interesting reason; you think this could be related to the fact that the latest VillainROMs stem from CDMA ROMs? What I still don't get is that speech and GPRS traffic are unaffected, these just work.
I already tried your fixes several times but for me they don't work everytime. Ah well, hopefully the official 2.1 update does some good here
Click to expand...
Click to collapse
I don't think a CDMA source is the issue here.
I've ported a CDMA to GSM with no problem whatsoever.
You could always try replacing libreference-cdma-sms.so, libreference-ril.so, libril.so and libhtc_ril.so from a GSM ROM.

Im also on T-mobile NL with unlimited web n walk
i dont have that issue, and i am currently on aHero 0.7 with latest radio,
also havent encountered the problem on other 2.1 roms
i hope this is some additional information

I always run into this problem as well on all of the 2.1 ROMS pretty much. I'm on the 3 network in the UK. Basically I never had this problem with any of the modaco 1.5 ROMS.

Awesome. Thankyou!
This has fixed my annoying 3G issues, Exactly as you describe.

What exactly is the solution?

Update 2 - First post.
Previously browsing maps would stall and the "up" arrow be stuck on, with the "down" one empty. I say maps, but anything really that uses the data connection. Most often going into Airplane mode and back again fixed it. Now it just works, and quickly too.
BTW - I'm on orange UK.

ChrisCoooo said:
Update 2 - First post.
Previously browsing maps would stall and the "up" arrow be stuck on, with the "down" one empty. I say maps, but anything really that uses the data connection. Most often going into Airplane mode and back again fixed it. Now it just works, and quickly too.
BTW - I'm on orange UK.
Click to expand...
Click to collapse
So just adb those values into the build.prop file and now everything is fine?

Yep. Thats basically all I did, I did a remount, pulled the build prob to my local, edited it, then pushed it back.
First reboot then I had connectivity, but the status bar showed it not being registered on the network. Second reboot and it was all good. A consitent 3G/H signal and no stalling of data transfers.

ChrisCoooo said:
Yep. Thats basically all I did, I did a remount, pulled the build prob to my local, edited it, then pushed it back.
First reboot then I had connectivity, but the status bar showed it not being registered on the network. Second reboot and it was all good. A consitent 3G/H signal and no stalling of data transfers.
Click to expand...
Click to collapse
I edited my OP, since I experienced connection loss again. How is it holding up for you?

Great topic J0bro.
I am having exactly the same problems as you describe. I was just searching the web since at first i couldn't find anything usefull here. I just went back to see if there were some new rom updates and i saw this topic.
I am now running villain 5.2 and latest radio. I was already experiencing the same probs a while back but not as much as i am now. It seems that when I try to open an app on the market i get a lot of connection errors. The switching between the 3g and H takes too long and times out.
I now have a stream running on stream live radio and that uses my H connection. Once it is continuously using H it seems just fine......
Strike that italic part.... When i was typing that it disconnected went back to 3G and lost connection. Now its switching back and forth between 3G and H
Damn this sucks man. I will try the part of of the build.prop....
Pff and i just got my debricked hero back
FYI I am on t-mobile NL with web n walk plus

Did you try replacing the ril libs I mentioned in /system/lib ?
Did you test this in another city?

adwinp said:
Did you try replacing the ril libs I mentioned in /system/lib ?
Did you test this in another city?
Click to expand...
Click to collapse
Just put it underneath the rest in the build.prop and rebooted twice.
Did I do that right?

Hi there which 2.1 Rom did u try?
On tmobile UK and had same 3g problem with stock rom but its fixed now. Only been testing with villainroms. Version 3.4 and 5 beta2 works perfect, the legend based one doesn't work and has same 3g problems. So its probrqbly not universal across 2.1 roms

Re: [2.1 ROMs] Unstable 3G/H connection but 2G and Wi-Fi are fine
i'm on villain 5.2
Sent from my Hero using the XDA mobile application powered by Tapatalk

Related

Rom 3.16 Post Installation Issues, Icons, etc

I have seen many, many threads about POST installation issues regarding the new 3.16 rom. I would like to attempt a problem/resolution thread that hopefully everyone will participate in order to create a "one-stop-shopping" thread regarding these issues.
I figure the mods will later either delete dormant threads or compile related threads into one. Hopefully we can get most if not all issues related to post installation here and properly labeled...
Please post problem(s) and if applicable, the resolution(s) to the problem regarding the 3.16 rom w/ Rev. A & GPS compatibility, including custom & stock rom. Please keep the thread limited to calls, data ( Rev. A & 0 plus Ev & 1X), task bar icons, prl's, etc and refer GPS questions/issues to threads like TalynOne's The Titan Internal GPS FAQ (01/30/2008) located here...http://forum.xda-developers.com/showthread.php?t=363431
I have included below some links to start off the thread which includes a link to the definition of what the PRL is and what it does and below that is a site with former & current PRL's for numerous carriers.
PRL - http://en.wikipedia.org/wiki/Preferred_roaming_list
PRL Listing - http://corolada.com/prl/
xweaponx said:
I have seen many, many threads about POST installation issues regarding the new 3.16 rom. I would like to attempt a problem/resolution thread that hopefully everyone will participate in order to create a "one-stop-shopping" thread regarding these issues.
I figure the mods will later either delete dormant threads or compile related threads into one. Hopefully we can get most if not all issues related to post installation here and properly labeled...
Please post problem(s) and if applicable, the resolution(s) to the problem regarding the 3.16 rom w/ Rev. A & GPS compatibility, including custom & stock rom. Please keep the thread limited to calls, data ( Rev. A & 0 plus Ev & 1X), task bar icons, prl's, etc and refer GPS questions/issues to other GPS threads...
I have included below some links to start off the thread which includes a link to the definition of what the PRL is and what it does and below that is a site with former & current PRL's for numerous carriers.
PRL - http://en.wikipedia.org/wiki/Preferred_roaming_list
PRL Listing - http://corolada.com/prl/
Click to expand...
Click to collapse
I flashed this ROM and I have since, jumped to DCDs version of it, and then back to 2.17.
I have, and apparently, a lot of folks have had inconsistent EVDO connection problems. Some times it freezes on "Loading"...other times, I can begin to pull up a web page and it times out. Speeds were good when it rarely did work properly.
The odd thing is that I have loaded new ROMS (including the current Sprint OEM ROM) and I'm still having that problem. (I'm taking suggestions to resolve this)
Also, like others, voice signal displayed fewer bars than usual. More "Signal Faded, Call lost than I have ever seen with this device.
On a kinda more positive note...
GPS worked well (when the EVDO connection did)
New Apps sucked up more of our previous RAM, but I didn't have any
latency or freeze ups.
I myself am experiencing a number of problems with the new ROM version, and will be downgrading to 2.17 soon. It took 3 installations of the new ROM to get the GPS to work. Since then, I've experienced several performance issues, including multiple times where the phone will freeze during web browsing in Opera Mobile. Sometimes, the phone won't even freeze, but will come up with a screen saying that the system memory is low, even when I'm only running Opera Mobile, it'll ask me to close either "Opera Mobile" "Phone" "Phone" or "Phone". Weird? I think so...
Also, there are times where I won't even get the internet to work. I'll have to either go in to the connections menu and disable the data connection, or do a soft reset of the phone completely.
In my opinion, it's probably more trouble than I really need to go through. I will be downgrading to 2.17 until the official release comes out.
Same issues for me:
inconsistent EVDO connection problems. Some times it freezes on "Loading"...other times, I can begin to pull up a web page and it times out. Speeds were good when it rarely did work properly.
Also, like others, voice signal displayed fewer bars than usual. More "Signal Faded, Call lost than I have ever seen with this device.
Spent 30 min with VZW level 2 support today. I called due to ##debug HDR an/aaa was = 0.. I was under the impression was supposed to be set to 1. They did look at my SSDR (I think he said that) and found it had a small issue with the authentication (still reads =0), but after he fixed that I still have issues. My HDR RDX power goes from -71db to -96db.
I also noticed every time I call the phone changes from EV to 1x. I know you don't use EV to make voice calls, but I did not remember (key word) seeing it switch like that before. Maybe someone with 2.17 1.40 radio can confirm.
I have thought about moving back too, but my call ticket history is getting pretty long with VZW and if I needed another A-key (yes I have one written down) it may start to look strange.
I'm on sprint and when I tried to update I was stuck on boot loader so I went online and switched esn over to my Treo for the time being as I worked on my Mogul. Eventually I got to load the rom fully and switched esn back. I noticed afterwards that my internet was only locking at 1x. Upon restart it would say EV but anytime it is connected to the net it is 1x. DSLreports clocked it at 50-90kbps so I know as definitely getting 1x speed. Reloaded the rom several times and still the same. This went on for 2 days. Eventually called Sprint and told them of my problem. They noticed that I was still on the regular Vision plan but I have always been able to connect to EVDO speeds so I never thought that was an issue. They updated me to Power Vision and right after I started getting EVDO speeds. I'm not sure if it was because of the change or maybe a restart of my data service that did the trick.
2 other issues I'm having is I noticed my phone is a little slow with this ROM. Opening programs etc. Sometimes the program using GPS like Live Search or GPS Viewer will lock up temporarily. The 2nd issue is what some are also reporting regarding signal. I noticed I get 1 to 2 less signal bars.
Overall 3.16 has been "ok". No problems with flashing really, and memory usage is "ok", I'm averaging around 17-18mb free with no apps running. It's not exactly the 20-22mb I had free with my prior custom rom, but enough to get by.
I'm not having problems with phone freezes or out of memory errors. I am, however, having some problems with BT and with net connectivity.
Data: I'm using Schap's Advanced config tool, version 1.1, and I've selected the option to keep my 'net connection live all the time. Unfortunately, this is not working, and I'm finding that throughout the day my connection goes down. With my prior custom rom, if I was streaming audio content over evdo or 1x, the connection would stay alive as long as the audio program was running, barring a loss of cell signal. Now I'm finding that about once an hour my data connection goes down and interrupts my audio stream.
BT: I have a Plantronics 320 headset, which worked flawlessly (albeit with less than stellar audio quality) with my prior rom. With 3.16, the volume and sound quality are much improved, BUT I am not able to answer calls on my headset. If I initiate a call with BT on, no problems, I can talk till the call is over, then press the headset hard button to hang up. If I *receive* a call, however, when I press the headset hard button to answer, the call is answered, but the audio is not directed to the headset. Instead, it routes to the handset.
GPS works well with TeleNav, GoogleMaps, Live, and generally locks onto 5-7 satellites within about 60 seconds if I'm somewhere with a clear view of the sky.
I tried using GPS2Blue to redirect the GPS data to a BT comm port. When I have BT enabled and attempt to redirect, GPS2Blue says BT port not open, waiting for BT port to open. If I go into comm manager and turn BT off, then GPS2Blue says BT port is open, and begins to wait for a BT connection to my laptop. If I go back into comm manager, the BT icon has been grayed out as if BT is off, but the little circled "X" icon is not superimposed over the BT icon as it would be when BT is off. If I click the icon again, it acts as if BT is being enabled, but the icon doesn't change, and the BT LED does not begin to blink. Don't know if it's a problem with GPS2Blue software or something else. Wish it would work cleanly, I'd love to use my 6800 as a BT GPS receiver for my laptop.
ETA: I've seen a few folks mention that when they answer a voice call their 6800 switches from Evdo to 1X. I'm wondering if this might be a way of implementing simultaneous voice & data. Has anyone tried taking a call and browsing the web simultaneously? I think this may be dependant upon network services in your area, so this may only work for folks in big cities with the most advanced network features, if it works at all...
ETA2: Just tried the above, and I'm getting the usual message that data connections cannot be initiated while on a voice call. I'm in a large city that *should* have all the latest network features, so if it dual voice/data was possible with this radio then it should work here. I'm assuming it's not presently possible, based on my experiment, but I'd be happy to be proven wrong.
with the sprint rom a ton of us have no audio out using an adaptor to listen through headphones
http://forum.xda-developers.com/showthread.php?t=363087
is a big thread about this going on the main board.
Took the plunge and installed the "stock" 3.16 on both my phone and a friend's last night. The first thing I want to note is that it went extremely smooth. No issues to note. It took a bit too long for my liking but it was fine. I didn't have to modify any MSID or MSN data - my phone worked fine right off the bat. Data was hosed, but a quick client-initiated IOTA Programming fixed that. (Settings, Personal, Phone, Services, Internet, Get Settings)
I have two constantly pinging(one 15 mins, one 30) e-mail accounts(one imap, one Exchange) that must keep my data connection alive. I haven't noticed a single decline in my data rate, nor a problem with disconnections. Then again, I live in NYC, which may make a difference.
GPS sucked last night - I couldn't get a satellite to save my life. On the way to work today, though, it was perfect. 4 satellites found in GMaps and tracking worked great.
I'm pretty happy w/the new additions to PocketOutlook too. Has anyone noticed that Gmail's IMAP works perfectly now, and that when you have multiple accounts - hitting messaging (when it's previously closed) brings up a choice of which account to go to? SWEET!
Just a quick "me too" regarding both disconnects and getting hung up during certain downloads. I've noticed that both "Live Search" from Microsoft's site and the latest (2.17) OEM ROM from HTC's site both hang up soon after they start downloading. This occurs both on the phone itself and while tethering to my laptop.
Foetus said:
Just a quick "me too" regarding both disconnects and getting hung up during certain downloads. I've noticed that both "Live Search" from Microsoft's site and the latest (2.17) OEM ROM from HTC's site both hang up soon after they start downloading. This occurs both on the phone itself and while tethering to my laptop.
Click to expand...
Click to collapse
So the phone made me out to be a liar. The LiveSearch download from wls.live.com failed now. It definitely worked last night on my roommate's phone however. Hrm. I downloaded it from my pc and emailed it to myself and it actually downloaded. That's odd.
Foetus said:
Just a quick "me too" regarding both disconnects and getting hung up during certain downloads. I've noticed that both "Live Search" from Microsoft's site and the latest (2.17) OEM ROM from HTC's site both hang up soon after they start downloading. This occurs both on the phone itself and while tethering to my laptop.
Click to expand...
Click to collapse
I didn't try with the ROM update, but I did experience this with Live Search.
New Rom
Vinny75 said:
I didn't try with the ROM update, but I did experience this with Live Search.
Click to expand...
Click to collapse
Had trouble getting my phone to flash, because I flashed the radio before the rom. Once I got phone going is working perfect. Hooked up to pda net on laptop downloading at 1.7 uploading at 500K. Use Holux to get gps started all programs work, Tom Tom is more accurate with my mogul compared to the external gps. Have not tried my s9 headphones yet. Running the DCD beta and I have no complaints except for the memory. Phone quality is the same.
v3.16+ ROM puts a voicemail icon on the 1 key which screws up the keypad if you are using the BlueFrog Big Button Dialer. To fix this, change the registry DWORD value at
Code:
HKCU\ControlPanel\PhoneExtendFunction\CDMA\EnableVoicemailIcon
from 1 to 0, and soft reset.
I was running Custels V1.1 2.14 and radio 1.47.00. I had my data set to connect all the time (which never idled btw...)and had Ev service everywhere. After installing Dcd's 3.16 & radio 3.27 I first recieved the "twin towers"... One had data connection and the other looked like the searching-for-signal tower. Plus my roam indicator was constanlty blinking.
After searching the forums, a helpful soul recommended *228 then press 3 which programs your phone. Remember that you are not upgrading to a new phone.
I then *228 and pressed 2 this time to program the latest PRL (which was 30029 before and still then). After searching some more, I saw that there was indeed a newer PRL which is 40029 (link in the first thread). I downloaded the PRL to my Sd card, dialed **775, entered my Alltel Unlock Code of 000000 and and the first screen I saw was update prl. Click on "Menu" in bottom right and hit the "Edit" button. Now you should see a empty value with "Browse" below it. Browse to the location where you placed your prl, upload and if you exit out correctly, you should be soft resetting your device.
After completeing the steps above, my roaming triangle was gone as well as the extra tower. I still have my data constantly on with Ev coverage all the time but my data actually idles now. Call quality has been noticed by myself and others as clearer and louder than before.
That Reg Entry doesnt exist on mine.
TalynOne said:
v3.16+ ROM puts a voicemail icon on the 1 key which screws up the keypad if you are using the BlueFrog Big Button Dialer. To fix this, change the registry DWORD value at
Code:
HKCU\ControlPanel\PhoneExtendFunction\CDMA\EnableVoicemailIcon
from 1 to 0, and soft reset.
Click to expand...
Click to collapse
Mine has the following instead:
"HKCU\ControlPanel\PhoneExtendFunction\CDMA\VoicemailIcon
Value name:BtnDN_LAND Value data:Windows\_VoicemailBtn1_Land.bmp" and three other similars.
Should that entry be added in it's entirety or should I remove my current entries? Any body else find they have entries like mine?
I thought I had that problem at first, but when I looked more closely, the reg entry is *in* the CDMA folder, not in a sub-folder below CDMA.
!!Major Bluetooth Issue!!
recently installed DCD's new GPS enabled ROM for Verizon. Everything has been working well even the GPS !!EXCEPT!! Bluetooth OBEX. When I try to send / beam any type of file my XV6800 stops responding and I am forced to soft reset.
I don't know if this only affects the Verizon ROM or all carriers for that matter. Is there any one here that has a fix or know's of a fix to resolve this issue? Has DCD released any news on this? I would Gladly appreciate it, as all the people with this issue.
Searching For Service
I loaded the Sprint Test Rom. No when ever I boot my phone it takes ~4 minutes for the phone to lock onto the network.
You are may differ with this situation....
PRL's didn't change. Even reloaded 60610. EVDO roaming is gone. Guess they didn't like people forcing their phone to roaming in areas where Alltel has EVDO and Sprint doesn't. 60611 also removed EVDO roaming in my area. 60610 and 2.17 work fine with EVDO roaming.
CardExport & the My Documents-redirect-to-SD-card reg tweak:
HKLM\System\StorageManager\Profiles\SDMemory
change the value of the string "Folder" to "My documents"
no longer work.

GPS fails unrecoverably within 10min on a GSM SIM, until phone is rebooted.

On the Rezound the location services target-symbol icon is always present in two states. An OFF state where only the main target symbol is showing, and an ON state having an additional pair of lines to its right hand side.
I have been on 4.03.605.2 Update since August with no issues, except two days ago I cancelled Verizon and have been using the phone with a T-Mobile SIM. Again all is working flawlessly (including data, phone, and texts) except the GPS started to fail within 10min of navigation. It fails because somehow the entire location service crashes (the target icon disappears completely), at which point fiddling with settings or AGPS cache and such is irrelevant. Only a phone reboot restarts the service.
(before cancelling Verizon, I was able to drive 1700 miles across country having the GPS fully functional for 8-12 hours at a time daily with no hitches. So there is something new amiss here. Also, I have already wiped the phone and reinstalled the 4.03.605.2 clean from scratch and re-rooted).
->My question is, does anyone know which specific apk is responsible for the location services (including the taskbar symbol) and can it be hot restarted by itself, or what could possible be causing it to crash in the first place ?
If you wanted you could try a new ROM or you could try a factory reset.
Sent from my ADR6425LVW using xda app-developers app
ThomasAn said:
In HTC devices (that I know of) the location services target-symbol icon is always present in two states. An OFF state where only the main target symbol is showing, and an ON state having an additional pair of lines to its right hand side.
I have been on 4.03.605.2 Update since August with no issues, except two days ago I cancelled Verizon and have been using the phone with a T-Mobile SIM. Again all is working flawlessly (including data, phone, and texts) except the GPS started to fail within 10min of navigation. It fails because somehow the entire location service crashes (the target icon disappears completely), at which point fiddling with settings or AGPS cache and such is irrelevant. Only a phone reboot restarts the service.
(before cancelling Verizon, I was able to drive 1700 miles across country having the GPS fully functional for 8-12 hours at a time daily with no hitches. So there is something new amiss here. Also, I have already wiped the phone and reinstalled the 4.03.605.2 clean from scratch and re-rooted).
->My question is, does anyone know which specific apk is responsible for the location services (including the taskbar symbol) and can it be hot restarted by itself, or what could possible be causing it to crash in the first place ?
Click to expand...
Click to collapse
the location icon is stored in framework-res.apk and comes active by the framework.jar and services.jar i know there is a patch floating around that will give the GPS a more accurate location reading with updated north america stats. you can try to find this and run it to see if it patches the problem. i have never heard of this before.
synisterwolf said:
the location icon is stored in framework-res.apk and comes active by the framework.jar and services.jar i know there is a patch floating around that will give the GPS a more accurate location reading with updated north america stats. you can try to find this and run it to see if it patches the problem. i have never heard of this before.
Click to expand...
Click to collapse
I am afraid, the the gps.conf tweak is not helping in my case (tried it). For the lack of better explanation, it is as if the gps driver/daemon crashes (to borrow a windows term) and I can play with the settings and checkboxes all day, it will not come back online until a reboot.
To give you an idea of the symptoms.
For up to 10-15 min it works flawlessly, locking within 2secs, seeing 20 satellites and tracking 10-14 of them. Then within a few turns of GPS navigation the location services icon disappears, the gps icon starts blinking and GPStest screen goes blank with 0 in sight and 0 tracking. No amount of check-box fiddling in settings, or AGPS cache clearing recovers it until reboot.
Uninstalled gMaps, and tried a few other packages as well (CoPilot, Maverick, OsmAnd) makes no difference.
Even without any Nav software running ... just launching the GPStest app and leaving it on with the screen on, it will go for an hour or so before jamming. So GPStest goes for an hour and Nav apps go for 10-15min ... should I assume some kind of GPS buffer overflows and crashes the location service ?
SOLVED.
For some reason the Rezound needs to be either in Global or CDMA mode for the GPS to work indefinitely without fail.
When I put it on GSM / UMTS the GPS only lasts for an hour or so before failing and requiring phone reboot.
In GSM mode it fails within 5-10 min.
In CDMA mode it works perfectly even though it gets no signal due to the GSM SIM inside.
(Keep in mind I use the phone with a GSM SIM)
In summary, keeping the phone in CDMA or Global mode fixes the issue. I also added these lines in the gps.conf for the heck of it (but I really do not think they do anything. I can still get it to fail by switching modes)
PHONE_TYPE=Global
PHONE_TYPE=CDMA
PHONE_TYPE=GSM / UMTS
PHONE_TYPE=GSM
PHONE_TYPE=UMTS
ThomasAn said:
SOLVED.
For some reason the Rezound needs to be either in Global or CDMA mode for the GPS to work indefinitely without fail.
When I put it on GSM / UMTS the GPS only lasts for an hour or so before failing and requiring phone reboot.
In GSM mode it fails within 5-10 min.
In CDMA mode it works perfectly even though it gets no signal due to the GSM SIM inside.
(Keep in mind I use the phone with a GSM SIM)
In summary, keeping the phone in CDMA or Global mode fixes the issue. I also added these lines in the gps.conf for the heck of it (but I really do not think they do anything. I can still get it to fail by switching modes)
PHONE_TYPE=Global
PHONE_TYPE=CDMA
PHONE_TYPE=GSM / UMTS
PHONE_TYPE=GSM
PHONE_TYPE=UMTS
Click to expand...
Click to collapse
Have you tried cm9 yet. Option for GSM and cdma on the same line might help.
Sent from my iPhone...
synisterwolf said:
Have you tried cm9 yet. Option for GSM and cdma on the same line might help.
Click to expand...
Click to collapse
That option on CM9 is the descriptive form of the "Global mode" in the HTC RUU under the hood.
My next step is to understand why the network modes affect the Rezound GPS like this.
Anyone knows if there an HTC doc that describes the official GPS APIs, or at least how to properly construct a gps.conf file with settings that the Rezound actually understands ?
ThomasAn said:
My next step is to understand why the network modes affect the Rezound GPS like this.
Click to expand...
Click to collapse
Did some more searching on this and so far I begin to suspect the possibility that the Rezound is deliberately GPS-locked to the CDMA network by Verizon. (Unlike my earlier claim, the global mode does fail eventually. It just takes a while longer).
I am not happy with this but so far the only workaround is to switch to CDMA while navigating (even if the phone gets no signal due having a GSM sim).
I will keep looking ... and any suggestions are welcome...
The GPS works on the CDMA setting even with the SIM removed completely, (but it fails if set to GSM with no SIM and no data).

Slow 4G Play Store Download Speeds Fixed (kinda)

Okay, so there have been a few of us who've been experiencing really terrible 4G download speeds, most notably so in the Play Store. I'm talking Kilobytes per second here, people. I could transcribe the code and compile it faster than this stuff is downloading.
Anyway, I believe I may have fixed the issue. I've rebooted a couple of times and my changes have persisted through, so I'm hopeful. My download speed went from being measured in KB to MB which made me feel like my phone wasn't trying to operate on dial-up with some free hours left over from one of the thousands of AOL free trials discs found laying about in the early 90's.
So, here's what I tried BEFORE my fix:
-- Various 3G/4G Speed/Network/Signal Optimizer/Fix/Strengthen/Repair apps on the Play Store. Two of those apps actually helped my download speeds for the first app I downloaded from the store; after that the speeds went right back to being dismal and embarrassing. Nothing else helped at all.
-- *#*#4636#*#* to Phone Information and toggled various network preferences. Nothing affected my download speeds.
-- Tried various Mobile Network options in the Settings menu. Nothing helped.
-- Toggled variations of Roaming modes, network types, etc.
-- Flashed back to stock.
-- Flashed to Slim Bean (what I was running before)
-- Tried dirty flashing over the roms after getting everything set up
-- Cleared Dalvik, Cache, Fixed Permissions
-- Completely wiped my entire phone and started from fresh
-- Tried custom kernels
-- Went to the Verizon store and got a brand new sim card
-- In Build.prop I changed ril.subscription.types from NV,RUIM to RUIM,NV. Some google search led me to a forum where someone suggested that. It didn't do anything for me.
-- In Build.prop I saw ro.product.locale.region was set to GB. Changed that to US and rebooted. No change.
Nothing I was doing was working. I was still getting the worst download speeds I've ever seen in my entire life. I swear to god I was getting better download speeds when I was like, 10 years old browsing the internet on a 14.4 modem on a 386 processor with Windows 3.11. I wanted to punch the internet in its e-face with my digital fist.
So, that's when I had a revelation. I just came from having a Razr Maxx that I'd flashed god knows how many different roms and kernels on over the course of the year that I'd owned it. I never had download issues with that, and it too was running on 4G LTE with a micro sim card in it. If that worked fine, then why doesn't this? With that question in mind, I remembered some of the settings I'd seen in the build.props over the past months and one of them stuck out as I was browsing the build.prop for my new SGS4:
ro.telephony.default_network
On this phone, it was set to 8, however I was 100% certain my Razr Maxx has that value as 14. I figured "screw it, let's give this a shot," and changed that value to 14 instead of 8.
When I rebooted my phone stuck at the Samsung boot logo. I had to pull the battery. I booted into recovery and decided to try something different than my usual "Welp this didn't work time to format everything and try again," approach. I wiped Cache, Dalvik, and Fixed Permissions then rebooted. The phone booted up like normal. I ran Speedtest to see if my speeds were still garbage or not. That test wasn't amazing by any stretch of the word. It was something like 6 mbps down, 6 mbps up. I was getting similar speeds before, so I wasn't hopeful. Then, I went to the Play Store "just to see," and downloaded a past purchase.
It started at 50kb and my heart immediately sank. Then, it went to 2 megs. 3.5. 6.2. 9. Download complete. I was hesitant to accept any actual change, so I downloaded another app. Same increased speed. I was happy, but reluctant. I rebooted, completely certain that my old speeds would return and I'd go back to contemplating a full factory wipe and attempt to return the device for another claiming it was defective. After the phone rebooted and obtained its data connection I went back to the store and downloaded another app. FAST SPEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEED!
I don't know what the heck changing that 8 to 14 did or what that value actually represents, but my speeds have remained "fixed". Granted, they're slower than they probably could be, but my Play Store downloads have gone back to acceptable rates so I figured sharing that information with you guys here might help at least one other person who can't understand for the life of them why their new phone refuses to go as fast as it should.
TL;DR: Went to Build.prop and changed ro.telephony.default_network to 14 instead of 8 and my Play Store download speeds went from kbps back to mbps.
My issue has been very similar to yours. Except the only slow downloads I get are when they originate from Google. Running the speedtest app and viewing webpages all show my device is capable of downloading at serveral megs a second. But if I tried to watch videos on Youtube or listen to music I would get constant buffering and some downloads from the market (the more popular one like Angry Birds or Gmail) would only download at about 40k. Then all of a sudden everything started downloading at high speed again. I was overjoyed.
Today I decided to try another ROM and unfortunately after flashing some downloads are incredibly slow again.
I suspect that changing the default_network in the build.prop did not actually fix the issue you were having. Especially since the information I have found about the field suggests it sets your phone default network type to something like CDMA or LTE only after a factory reset of your phone. In any case I have set this same field to 14, cleared dalvik and cache, then fixed permissions and my download speeds remain just as slow.
Well, I'm actually pretty confident it did because I was looking through apns-conf.xml and noticed that every instance of an LTE segment regardless of network (sprint, tmo, vzw) had this value
Code:
bearer="14"/>
. So, because of that, I'm pretty certain that the network type being set to 14 promotes LTE connectivity over whatever the 8 was, which is a value I can't find any reference for in this APN file.
You can try this, which is the actual steps taken for fixing my problem:
Settings -> More -> Mobile Networks
Data enabled [X]
Data roaming [ ]
National data roaming [ ]
Network Mode: LTE / CDMA / EvDo
System select: Home only
CDMA subscription: RUIM/SIM
Press Back, toggle Airplane Mode on then off
ROM Toolbox -> build.prop editor
ril.subscription.types RUIM,NV
ro.com.android.dataroaming false
ro.product.locale.language en
ro.product.locale.region US
ro.telephony.default_network 14
Reboot to recovery
Wipe Cache
Wipe Dalvik
Fix Permissions
Reboot
What ROM are you currently running? At the moment I'm running stock and don't have the options for System Select and CDMA Subscription. I also dont have a ro.telephony.default_network entry in the build.prop.
Edited -> Added more information
chronoquestion said:
What ROM are you currently running? At the moment I'm running stock and don't have the options for System Select and CDMA Subscription. I also dont have a ro.telephony.default_network entry in the build.prop.
Edited -> Added more information
Click to expand...
Click to collapse
I'm using Slim Bean.
If you're on Stock, you should be able to do this in Mobile Networks:
Mobile Data [X]
Global Data Roaming Access: Deny data roaming access
Network mode: LTE/CDMA
In ROM Toolbox Pro's build.prop editor I also saw that the region was set to GB. That should go back to US if you're in the US.
Edit: Actually, if you're on the stock rom you can go to Settings -> More -> About Phone - Status or whatever the option is. If you look for network type or connection type, you should see something like Verizon LTE 14 or something similar. That's the 14 I was talking about. If that says 14, you should be good.

Fujitsu Arrowsx F02E GPS error

I bought Fujitsu Arrowsx F02E phone last week. Great Japan phone for low price. It works great(Fingerprint sensor exelent :fingers-crossed. But,
1. When I turn on GPS using 3G network it restarting again and again(GPS work fine with Wifi)
2. Antutu benchmark shows lower score for processor and GPU (Compared with HTC one X(Both has Nvidia tegra 3)) HTC one x has 1.5quad but this phone has 1.7quad :laugh: . So, why lower score?
3. Asphault 7 not working also(Game opened its Menu is slow and game not started).
Please help me ASAP.
And Can someone please tell me where Can I find custom rom for this?
bump
bump
kk
wkh7777 said:
bump
Click to expand...
Click to collapse
Plz help
i have exactly the same problem with gps on this phone...
have you found some solution by now, perhaps?
To OP:
1.
GPS will crash the phone to restart is normal for ALL NTT Docomo NEXT series Smartphones. I have confirmed with my F-02E, F-06E, SH-06D and an even older NEC MEDIAS.
To use the GPS on these devices, you will have to turn on the Airplane mode to work if you are outside of Japan and is using a foreign SIM card. (GPS will work fine with 3G or 4G LTE Xi with a Docomo USIM in Japan)
*****(Though I have read somewhere that a non-Docomo 128kb MicroSIM might do the trick, but I do not have one to test)*****
Also do not expect the GPS to be as fast and accurate as the Galaxy S3/S4 as the F-02E does NOT support GLONASS.
The GPS receiver is optimized for Japan region only (maybe can change satellite list after root).
A-GPS for faster GPS lock is DISABLED without a Docomo SIM.
2.
The reason for the lower score is because of the lack of optimization, as well as all the BLOATWAREz Docomo has preloaded on the phone. To uninstall these Docomo software (useless outside of Japan), you have to r00t.
Fujitsu kind of failed with the F-02E. Even after the V17 update, Android 4.1.2 is really unstable on the phone. I had the OS crashed in several occasions in different apps and some games.
To get the best performance out of the F-02E, you have to flash a cooked ROM.
Though the stock OS is much faster and stable on the F-06E, though in synthetic benchmark, the F-06E still scored lower than my Galaxy S4 -i337m
3.
Asphalt 7 works fine for me on my F-02E. Also gameplay is rather smooth offscreen at 1080p.
Asphalt 8 works good too, but some occasional frame drops on complex maps.
Shadowgun and DeadTrigger both plays buttery smooth.
Epic Citadel Unreal 3 Benchmark, the F-02E at 1080p on Best Quality setting gets around 30fps - 40fps (Tegra 3 works better on 720p screens, and again lack of optimization from Fujitsu on the software side)
Hope this helps.
Cheers
you're great, man! thanx a lot for your answer -
but where can i find that cooked rom for f02-e?
ndandy said:
you're great, man! thanx a lot for your answer -
but where can i find that cooked rom for f02-e?
Click to expand...
Click to collapse
You will have to find some clues on Japanese BBS boards (2ch etc **NSFW)
Development for this phone in Japan is gathering more people as the average retail no contract price of a brand new F-02E in Japan costs around $160-$180 since around May-June of 2013
You can also find active development in some Chinese forums
mms6 said:
To OP:
1.
GPS will crash the phone to restart is normal for ALL NTT Docomo NEXT series Smartphones. I have confirmed with my F-02E, F-06E, SH-06D and an even older NEC MEDIAS.
To use the GPS on these devices, you will have to turn on the Airplane mode to work if you are outside of Japan and is using a foreign SIM card. (GPS will work fine with 3G or 4G LTE Xi with a Docomo USIM in Japan)
Click to expand...
Click to collapse
I use F-06E with 3G operator and have no problems with GPS, no reboots, navigation apps work good.
Also, I had F-02E, it could not find any satellites at all.
psylence84 said:
I use F-06E with 3G operator and have no problems with GPS, no reboots, navigation apps work good.
Also, I had F-02E, it could not find any satellites at all.
Click to expand...
Click to collapse
You might have a 128k MicroSIM card with your F-06E.
My 64k Rogers Wireless MicroSIM make both my F-02E and F-06E reset when GSM and/or HSPA is turned on (mobile data on/off does not matter), and GPS is on and searching for satellite for location.
***NOTE*** If the GPS is just on and not searching for any satellites, the phone will not reset.
Regarding your F-02E does not find any Satellites in Moscow (Your Location).
The F-02E will find a GPS lock eventually, but it may be unstable and take quite long time to lock. The main problem is because the GPS receiver chip in the F-02E does not support GLONASS, and the GPS locale list is configured in Japan region. So outside of Japan region, GPS will be flaky without rooting and updating the GPS locale conf.
The F-06E on the other hand does have GPS/aGPS and GLONASS support as part of the Qualcomm S600 platform SoC. GLONASS lock should not be a problem.
***NOTE*** The aGPS cellular assisted location service will not work without a Docomo USIM. Hence on phone with only GPS and no GLONASS, like the F-02E, initial lock from cold boot may take some time.
How to change/update GPS locale list
mms6 said:
You might have a 128k MicroSIM card with your F-06E.
My 64k Rogers Wireless MicroSIM make both my F-02E and F-06E reset when GSM and/or HSPA is turned on (mobile data on/off does not matter), and GPS is on and searching for satellite for location.
***NOTE*** If the GPS is just on and not searching for any satellites, the phone will not reset.
Regarding your F-02E does not find any Satellites in Moscow (Your Location).
The F-02E will find a GPS lock eventually, but it may be unstable and take quite long time to lock. The main problem is because the GPS receiver chip in the F-02E does not support GLONASS, and the GPS locale list is configured in Japan region. So outside of Japan region, GPS will be flaky without rooting and updating the GPS locale conf.
The F-06E on the other hand does have GPS/aGPS and GLONASS support as part of the Qualcomm S600 platform SoC. GLONASS lock should not be a problem.
***NOTE*** The aGPS cellular assisted location service will not work without a Docomo USIM. Hence on phone with only GPS and no GLONASS, like the F-02E, initial lock from cold boot may take some time.
Click to expand...
Click to collapse
I am having the same issue with my F10D, GPS keeps trying to locate satellites. I'm considering rooting it to update the GPS Locale list but I need guidance on how to update such list. Any help will be much appreciated! Thanks.
Even if updating the GPS list, the performance is only bit improvement. The antenna/receiver used in these Fujitsu phones before the Snapdragon 600 ---- F-06E are not great to begin with
If you really want a faster phone GPS, then its time to find other phones
As for a flashable GPS locale config for other countries outside of Japan, it will be hard to find if it even exists
New ROM
mms6 said:
Even if updating the GPS list, the performance is only bit improvement. The antenna/receiver used in these Fujitsu phones before the Snapdragon 600 ---- F-06E are not great to begin with
If you really want a faster phone GPS, then its time to find other phones
As for a flashable GPS locale config for other countries outside of Japan, it will be hard to find if it even exists
Click to expand...
Click to collapse
Thanks a lot for the explanation!
One more question - If I flash the phone and install a new ROM, do you think the GPS may work?
Thanks
OK guys, looks like I found a fix for f02-e reboot issues.. will post it after 48hrs from now. Device is under test. Its been 24hrs since I stated.. no reboots, GPS locks with out any issue. GPS+3g works !
Sent from my F-02E using xda app-developers app
Restarting problems. Need a solution. Please ...
Hello, I bought my unlocked F-02E mobile in Japan this summer and I brought it to Spain. I have disabled some docomo apps but the pone keeps restarting. I couldn't find the way to update or download the V17 firmware upgrade because I don't have any Docomo SIM in order to download it. I don't know if there's some cooked rom available to flash it and get a solution to avoid annoying restarting problems when calling or after calling or using 3G data ... (it happens randomly). I use GSM only here in Spain but when I call with data enabled it also reboots sometimes
Neither I don't know if buying a new 128K micro SIM could help to avoid rebooting issues.
I'll wait for your solution.
Thank you very much in advance.
Best Regards
biswaranjan said:
OK guys, looks like I found a fix for f02-e reboot issues.. will post it after 48hrs from now. Device is under test. Its been 24hrs since I stated.. no reboots, GPS locks with out any issue. GPS+3g works !
Sent from my F-02E using xda app-developers app
Click to expand...
Click to collapse
diamoncito said:
Hello, I bought my unlocked F-02E mobile in Japan this summer and I brought it to Spain. I have disabled some docomo apps but the pone keeps restarting. I couldn't find the way to update or download the V17 firmware upgrade because I don't have any Docomo SIM in order to download it. I don't know if there's some cooked rom available to flash it and get a solution to avoid annoying restarting problems when calling or after calling or using 3G data ... (it happens randomly). I use GSM only here in Spain but when I call with data enabled it also reboots sometimes
Neither I don't know if buying a new 128K micro SIM could help to avoid rebooting issues.
I'll wait for your solution.
Thank you very much in advance.
Best Regards
Click to expand...
Click to collapse
I can understand your frustration and pain.. I have gone through the same for past few months. I had verified with 64k, 128k and 256k sims. None of them fixed the issue. It reboots with any kind of sim. so buying a 128k sim will not help. But, only sim I have not verified is 'LTE sim with 3g/2g support'. It might fix the issue.
However as a workaround, I have modified some android props to suit Indian network conditions and the phone is much stable with a 64k sim now ! Still there were two reboots in three days(found the cause, will fix it) and it never rebooted during call ! Earlier it used to reboot 5-6 times a day. It used to reboot during/after calls, when kept idle, when I am cooking, etc...
Fix is to disable LTE on this phone and set some 3g/2g parameters. Additionally you can set some default locale and gps config too.
Please do the following tweaks and let us know the result.
Steps: (search the forum for appropriate links)
1. root your phone and mount /system as read/write. (must)
2. Now disable LTE and configure 3g/2g parameters: Add the following lines to "/system/build.prop" file. (can directly copy paste the following at end of the file)
# system props for telephony modules
# Disable LTE/4G
ro.config.lte=false
# Set default network to be 3g/2g auto (wcdma preferred)
ro.telephony.default_network=0
# set hsdpa/hsupa categories
ro.ril.hep=0
# hsxpa=2 signifies hsdpa and hsupa. you can leave it as 2.
ro.ril.hsxpa=2
# gprsclass=12 is maximum value it can have. all modern networks should support this, else as a conservative setting try 10.
ro.ril.gprsclass=12
# hsdpa=8 and hsupa=6 signifies 7.2mbps dowenload/5.76mbps upload. If your network supports it, leave it as it is. else try 6/4 for these values
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=6
# some signal strength, power tweaks
ro.ril.att.feature=1
ro.ril.disable.power.collapse=1
ro.ril.fast.dormancy.rule=1
ro.config.hw_fast_dormancy=1
# fixes connectivity issues, my phone used to loose network very often.
ro.ril.enable.dtm=0
ro.ril.enable.a53=0
# believed to be signal strength tweaks
ro.ril.enable.ncell.ind=1
ro.telephony.ril.v3=signalstrength,singlepdp,skipbrokendatacal
# better voice quality
ro.ril.enable.amr.wideband=1
3. Now set gps settings in build.prop. Add the following lines to "/system/build.prop" file. (can directly copy paste to the file)
# AGPS mode set
ro.ril.def.agps.mode=2
ro.ril.def.agps.feature=1
4. Now change locale settings. (So that when you do a factory reset, it does not show you japanese text) Find out following props and change it. (in "/system/build.prop" )
ro.product.locale.language=en
ro.product.locale.region=US
5. Now lets fix gps settings: (replace contents of "/system/etc/gps.conf" with the following). you should set NTP_SERVERS for your region. rest of the things should be fine for your region.
NTP_SERVER=asia.pool.ntp.org
NTP_SERVER=0.asia.pool.ntp.org
NTP_SERVER=1.asia.pool.ntp.org
NTP_SERVER=2.asia.pool.ntp.org
NTP_SERVER=3.asia.pool.ntp.org
NTP_SERVER=0.vn.pool.ntp.org
NTP_SERVER=1.asia.pool.ntp.org
NTP_SERVER=0.asia.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
ACCURACY_THRES=0
# Report supl ref location as position, 1=enable, 0=disable
REPORT_POSITION_USE_SUPL_REFLOC=1
# Wiper (wifi positioning), 1=enable, 0=disable
ENABLE_WIPER=1
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_NO_SECURE_PORT=3425
SUPL_SECURE_PORT=7275
SUPL_TLS_HOST=FQDN
SUPL_TLS_CERT=/etc/SuplRootCert
# FOR C2K PDE SUPPORT, set the following
C2K_HOST=c2k.pde.com
C2K_PORT=1234
CURRENT_CARRIER=common
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
# TRUE for "User Plane", FALSE for "Control Plane"
DEFAULT_USER_PLANE=TRUE
6. Change some parameters in "/system/etc/gps/config/pathconfigfile.txt". Replace the file with following content.
#
# Config file
GPSC_CONFIG_FILE /system/etc/gps/config/GPSCConfigFile.cfg
# Patch file
PATCH_FILE /system/etc/gps/patch/patch-X.0.ce
# Aiding file storage
AIDING_PATH /cache/gps/aiding/
#Logger Control
#0->dont log:
#1-> UDP
#2-> NVM
#3-> ANDROID
#4-> STDIO
#5-> CUSTOM FUNC
LOGGER_CONTROL 0
#logger IP & PORT when LOGGER_CONTROL = 1, else ignored
DEBUG_UDP 192.168.16.1 5555
#Logger NVM setting, when LOGGER_CONTROL = 2, else ignored
LOGGER_NVM_FILE /cache/gps/logs/
#Logger - maximum lines in log per file in NVM
MAX_LOG_LINES 100000
#Logger - maximum log files in NVM
MAX_NVM_FILES 10
#To/From Sensor Control
#0->Dont write:
#1->Write to UDP(Not supported):
#2->Write to NVM:
SENSOR_CONTROL 0
#Sensor log NVM setting
SENSOR_NVM_PATH /cache/gps/logs/
#Session log Control
#0->Dont write
#1->Write to NVM
SESSION_LOG_CONTROL 0
#Session log NVM setting
SESSION_LOG_NVM_PATH /cache/gps/logs/
6. Now, DO A FACTORY RESET. AND PLS DO NOT DISABLE ANY DOCOMO APPS. Use the phone for couple of days and if it's stable, start disabling docomo apps.
Please do let me know if it helped.
Note: still you might see a reboot, as I had seen two reboots in last three days. Found the cause, fixed it and device is under test again Let's hope no more reboots on this device.
PS: I hate this device so much, if it reboots again I will throw it out of the window.
How can some one release a device without proper verification ? a docomo user might face same issues while in international roaming !
Thank you
Thank you very much!. I will try these steps you explain but I guess I'm going to buy another mobile because it's not very useful to have a phone which cannot get Android updates and cannot use 3G data without rebooting.
I'm planning to buy a Moto G which is made by Google and they say that Android 4.4 update is sure at the beginning of 2014. And it's cheap and has good specifications
I also had problems of not being able to use 3g data without rebooting. These steps would solve it too don't disable any DoCoMo apps.
But software update is a real prob..
Sent from my F-02E using xda app-developers app
I quit. No further wasting of time n energy.
Rebooted many times today, reboot happens while searching for network.
Am selling the phone now. Will go for Google device.
Sent from my F-02E using xda app-developers app
New Software Update V19R50D?
Hello,
I've seen there's a new nttdocomo software update compilation (V19R50D) and I've read somewhere this update solves rebooting (I read it on a japanese page translated thanks to Microsoft Bing Translator ).
Do you know if there's any way to update software without nttdocomo SIM and outside of Japan?. I've searched but I haven't find any way :crying:
Anyway, I'll buy a new Google device too because my F-02E, although there's a nice device with great specs, it's unuseful if you cannot call without restarting or surfe the web with at least 3G data.
Thanks!
biswaranjan said:
I quit. No further wasting of time n energy.
Rebooted many times today, reboot happens while searching for network.
Am selling the phone now. Will go for Google device.
Sent from my F-02E using xda app-developers app
Click to expand...
Click to collapse
I had tried vpns and Sim location manipulators but did not work hope some one posts a solution.
Sent from my F-02E using xda app-developers app

LTE connection issues on LineageOS & Cyanogenmod on SM-G900T

I recently left the stock rom to install custom firmware on my Galaxy S5 (SM-G900T). I am noticing some strange behavior with LTE, and was wondering if anyone else was experiencing a similar issue. With LineageOS 14.1 (klte) currently, upon rebooting the device, it remains on HSPA+ for at least 10 minutes or so before connecting to LTE. If the device is kept running, and is not turned off or rebooted LTE will persist just fine, even if I change the radio selector to 3G or 2G, it will always go back to functioning LTE. On the Stock rom, I never experienced this issue. I previously ran Android 6.0.1, before upgrading to LineageOS. I have also tried with Cyanogenmod 13 to compare, and experienced the exact behavior. I have tried using the dialer menu on LineageOS (*#*#4636#*#*) to see if changing the radio settings makes any difference, sometimes it will make the device connect to LTE faster, after a reboot. If anyone has any insight on how to correct this that would be great. Thanks.
Which firmware version are you on?
invisiblewave said:
Which firmware version are you on?
Click to expand...
Click to collapse
My current firmware is G900TUVU1GPE1. I am also currently running cyanogenmod 13. I flashed back to stock today to take a look at some settings in the service menu. I tried setting LTE Band preference to 17, and it made no difference upon returning to cm 13.
My current "workaround" in cyanogenmod, after a reboot or poweroff, is to go to the dialer menu (*#*#4636#*#*), change radio to LTE/GSM/CDMA, turn off the radio, select LTE/GSM, turn on the radio, then immediately reboot. After a reboot, I can go to Cellular network settings, toggle 3G, then toggle LTE as preferred. I now have LTE, until the next reboot or poweroff.
I'm wondering if there is something in the stock service mode that has to be set, that cyanogenmod somehow does not have access to?
Thanks
I don't recall anyone else with the same issue. I'd try the latest modem, GPK3.
invisiblewave said:
I don't recall anyone else with the same issue. I'd try the latest modem, GPK3.
Click to expand...
Click to collapse
I just tried out the latest modem (GPK3), and I am still experiencing the same problem unfortunately. I don't believe I mentioned this earlier, but the device is unlocked and I am currently using an AT&T SIM. However, I have had no issue with the LTE persisting on reboot with the stock rom though. I'm curious if an alternate rom might be beneficial, perhaps resurrection remix. Have you ever tried your device with an AT&T SIM? Thanks again.
Partially solved. I discovered now that if I toggle 3G under Cellular Networks before rebooting or turning off the device, I am able to select LTE after a reboot or power off and connect instantly. Perhaps this is somehow related to using an AT&T SIM. This is a little better than before, at least.
I had this issue on CM13, since the CM forums are now gone, it's hard to find the old threads troubleshooting these problems. Here is my solution:
Yes!
Thank you for posting this, my last post was 3 months ago on this issue and I was documenting everything I troubleshooted and getting 0 responses..
There must be something glitched with the APNs on this phone, by default I was only seeing Straight Talk with GID set as the MVNO type, after disabling this I could see more APNs and add more, but could not discard them.
/system/etc/apns_conf.xml - Delete this (you can backup just incase)
Go back to APN Settings and Reset to default, then add your APN.
Once I saw HSPA+ I restarted my phone and got LTE and the radio seems less laggy now, only have been testing for a few minutes now.
Only issue is I restarted with LTE and LTE wouldn't come back, I toggled airplane mode and immediately got LTE (unlike before where the radio would take forever just to get HSPA+)
Click to expand...
Click to collapse
You can use archive.org to view the old Cyanogenmod forums, the buttons don't usually work, so you will need to open them in new tabs.
https://web-beta.archive.org/web/20...org/topic/120995-cm13-lte-doesnt-work/?page=6
Also, if you have problems deleting that file (or simply renaming) try:
Try to use one of the following ways:
mount -o rw,remount -t rootfs /system
or
mount -o rw,remount -t rootfs rootfs /system
You also can use it for any folder that you need even root (/)
Click to expand...
Click to collapse
http://stackoverflow.com/questions/18918456/android-2-3-read-only-file-system-stuck
I'm having the exact problem you're having. But it's not just my S5 on LOS 14.1, it's also my roommate with S4 on LOS14.1 and other roommate with S3 on CM13. We're all on Ting, we all started having the same problems at the same time, exactly like you describe.
I called Ting and they told me the towers were being "modernized", and that NONE of these phones had the optimal frequencies to use their new LTE. I got a long email from them about frequency compatibility but my initial research leaves me skeptical. All these phones have the frequencies tmobile says it uses, according to wikipedia.
So, they're sending us new sim cards, which I bet is just another BS fix, just like the 100 times they had me reset my APN settings and pull my battery : p
I installed the latest LineageOS on my S5. I am now seeing network issues. I get drops after calls, and wifi enable/disable. I see a "x" on the bars in the status menu.
If I cycle data on off it seems to reconnect - on but not on full LTE .
After a google search I found what could be the cause, the Verizion radio variant was added to the KLTE builds. You can see it on that forum at reddit.com/r/LineageOS/comments/605y43/please_dont_add_verizon_variant_into_klte/
I didn't actually try the "fix" they offer there because I don't quite understand it.
I gave it a shot and installed the force_g900f_ril_blobs.zip using TWRP and can report SUCCESS. Its a fix of sorts if you are on T-Mobile using another variant like me, in this case a G900V (S5 Verizon).

Categories

Resources