Related
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
Hi all.
For the last month or so I have been unable to use wifi because it drains my battery too fast. I have had this problem with Litening rom 3.1-2, Sensation Rom, running the stock rom, using stock kernels, litening kernel, siyah... I have no idea what else to try. I have wiped data, all of the caches, reflashed, bricked, fixed the brick, and still dont know what to do. Does anyone have any advice?
Thank you in advance.
Given everything you've tried, that's obviously a router issue. Maybe update your router firmware or try another router. Definitely not a phone issue. There's something in your router settings causing it, you could also do a factory reset on the router as well (make a note of all your settings first) & remove all encryption, then add back settings one by one in order to try and isolate what's causing it.
I dont have a problem with my computer or any other devices on my home router. And the phone has battery drain when wifi is on, not necessarily connected even... The one thought i had that might be connected to my home router is that it disconnects and reconnects every 5 seconds when on my home router.
jbarol said:
I dont have a problem with my computer or any other devices on my home router. And the phone has battery drain when wifi is on, not necessarily connected even... The one thought i had that might be connected to my home router is that it disconnects and reconnects every 5 seconds when on my home router.
Click to expand...
Click to collapse
Try this...on your wifi settings go to Advanced then on Keep Wi-Fi on during sleep. choose Only when plugged in or Never. This will turn-off your wifi when your phone is sleeping.
Also, the drain can be caused by other applications not necessarily your wifi. Use BetterBatteryStats to check the wakelocks.
This is from the fluxi kernel thread:::
Q: Wakelocks "wlan_rx_wake" wake up my device constantly what I can do about it?
A: The problem is neither Android nor the kernel, but the router and the (Windows7) network. In the network properties, uncheck "IPv6", disable the service "IP Helper", "Shell Hardware Detection" and "Windows Media Player Network Sharing Service", which provide ongoing Traffic. Then they scored again 98% of deep sleep.
jbarol said:
Hi all.
For the last month or so I have been unable to use wifi because it drains my battery too fast. I have had this problem with Litening rom 3.1-2, Sensation Rom, running the stock rom, using stock kernels, litening kernel, siyah... I have no idea what else to try. I have wiped data, all of the caches, reflashed, bricked, fixed the brick, and still dont know what to do. Does anyone have any advice?
Thank you in advance.
Click to expand...
Click to collapse
Have You tried a ICS 4.0.4 CM9 nightly??? They are very stable and muuuuuch better than the stock ROMs. I've got WiFi on all the time and still can reach over a 24hrs with screen on for aprox. 4hrs..... Maybe this will work for You.
kjplasma said:
This is from the fluxi kernel thread:::
Q: Wakelocks "wlan_rx_wake" wake up my device constantly what I can do about it?
A: The problem is neither Android nor the kernel, but the router and the (Windows7) network. In the network properties, uncheck "IPv6", disable the service "IP Helper", "Shell Hardware Detection" and "Windows Media Player Network Sharing Service", which provide ongoing Traffic. Then they scored again 98% of deep sleep.
Click to expand...
Click to collapse
Im gonna try this next. But why do you think that the problem only just started in May? Ive had the same router set up since November...
My Wifi keeps getting disabled. And by disabled, I mean it shows it is ON ( I've to toggle the Wifi to switch it OFF ) but there's an exclamation mark on it.
To get it working again, I've to switch the Wifi OFF and then turn it back ON again.
Can someone help me pinpoint the underlying cause? I'm using A1EXANDER'S MIUI with the UCLE5 modem.
Ronin42 said:
My Wifi keeps getting disabled. And by disabled, I mean it shows it is ON ( I've to toggle the Wifi to switch it OFF ) but there's an exclamation mark on it.
To get it working again, I've to switch the Wifi OFF and then turn it back ON again.
Can someone help me pinpoint the underlying cause? I'm using A1EXANDER'S MIUI with the UCLE5 modem.
Click to expand...
Click to collapse
I have a similar problem with a different phone, but wonder if anyone has ever addressed this issue.????
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
Yes, this long waited thread has been opened at last. Rejoice!
So this is my problem, WiFi connection suddenly drops while I'm browsing. It shows it's still connected, but no data transfer. The little arrows on the WiFi icon shows that "sending" thing occurs (it blinks) but no "receive". Sometimes this happens right after a few seconds I turn on WiFi and start browsing, sometimes a longer time later, like a few minutes or something. Sometimes in a row; I turn off my WiFi and on again for a couple of times to get it working well. Sometimes it never happens and I can browse for a long time without having an issue. But when it happens, the only way to get rid of it to go on Fast Settings on notification center where you pull it from top of screen like a drawer and turn off WiFi, wait a few seconds and turn it on again.
I have a Smartband SWR10, which means Bluetooth is always on on my Xperia Z2. Do you think it's because the 802.11n and Bluetooth signals interference with each other since they're both on the 2.4GHz band? I have a 802.11ac router at home aswell, and when I'm connected to it (5GHz signal) I don't think I had this problem.
Thanks in any advance.
Edit ---> I didn't join this site on June 2014, for sure, I'm a way older member than that. But I just did a "forgot password" procedure. Maybe this is a bug?
I have the exact same issue and I use a Smartband as well. It seems to be related to wifi on 2.4 GHz only, since I can connect to 5 GHz APs just fine. So BT interference of some sort might be a factor, yes.
Sometimes I'm connected to the AP, the status bar indicator is showing traffic, but I have no internet connection, everything just times out. Other times it takes ages to connect and get an IP from DHCP, before it finally just disconnects from the AP and returns to mobile network.
Checking logcat, there's a constant barrage of errors in wpa_supplicant when this happens:
Code:
06-26 12:19:17.435 1326-1326/? I/wpa_supplicant﹕ wlan0: CTRL-EVENT-SCAN-STARTED
06-26 12:19:27.455 1326-1326/? E/wpa_supplicant﹕ wpa_supplicant_ssid_bss_match : wapi is null
06-26 12:19:30.535 1326-1326/? I/wpa_supplicant﹕ wlan0: CTRL-EVENT-SCAN-STARTED
06-26 12:19:40.555 1326-1326/? E/wpa_supplicant﹕ wpa_supplicant_ssid_bss_match : wapi is null
...
06-26 12:30:27.811 1326-1326/? I/wpa_supplicant﹕ wlan0: CTRL-EVENT-SCAN-STARTED
06-26 12:30:37.821 1326-1326/? E/wpa_supplicant﹕ wpa_supplicant_ssid_bss_match : wapi is null
And from dmesg:
Code:
<6>[181101.181887] CFG80211-ERROR) wl_cfg80211_add_iw_ie : Previous IW IE is equals to current IE
<6>[181111.211414] CFG80211-ERROR) wl_scan_timeout : timer expired
<6>[181111.211648] CFG80211-ERROR) wl_escan_handler : WLC_E_STATUS_TIMEOUT : scan_request[ef36b300]
<6>[181111.211699] CFG80211-ERROR) wl_escan_handler : escan_on[1], reason[0xffffffff]
<6>[181111.214041] CFG80211-ERROR) wl_escan_handler : escan is not ready ndev f3f96800 wl->escan_on 1 drv_status 0x0 e_type 69 e_states 4
<6>[181161.199815] CFG80211-ERROR) wl_cfg80211_add_iw_ie : Previous IW IE is equals to current IE
<6>[181171.211406] CFG80211-ERROR) wl_scan_timeout : timer expired
<6>[181171.211569] CFG80211-ERROR) wl_escan_handler : WLC_E_STATUS_TIMEOUT : scan_request[ef36bc00]
<6>[181171.211615] CFG80211-ERROR) wl_escan_handler : escan_on[1], reason[0xffffffff]
<6>[181171.213941] CFG80211-ERROR) wl_escan_handler : escan is not ready ndev f3f96800 wl->escan_on 1 drv_status 0x0 e_type 69 e_states 4
<6>[181281.231732] CFG80211-ERROR) wl_cfg80211_add_iw_ie : Previous IW IE is equals to current IE
<6>[181291.251421] CFG80211-ERROR) wl_scan_timeout : timer expired
<6>[181291.251633] CFG80211-ERROR) wl_escan_handler : WLC_E_STATUS_TIMEOUT : scan_request[efcd3900]
<6>[181291.251683] CFG80211-ERROR) wl_escan_handler : escan_on[1], reason[0xffffffff]
<6>[181291.254184] CFG80211-ERROR) wl_escan_handler : escan is not ready ndev f3f96800 wl->escan_on 1 drv_status 0x0 e_type 69 e_states 4
<6>[181401.258382] CFG80211-ERROR) wl_cfg80211_add_iw_ie : Previous IW IE is equals to current IE
<6>[181411.271395] CFG80211-ERROR) wl_scan_timeout : timer expired
<6>[181411.271554] CFG80211-ERROR) wl_escan_handler : WLC_E_STATUS_TIMEOUT : scan_request[ef36b200]
<6>[181411.271604] CFG80211-ERROR) wl_escan_handler : escan_on[1], reason[0xffffffff]
<6>[181411.274855] CFG80211-ERROR) wl_escan_handler : escan is not ready ndev f3f96800 wl->escan_on 1 drv_status 0x0 e_type 69 e_states 4
<6>[182002.187708] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH_IND
<6>[182002.187772] link down if wlan0 may call cfg80211_disconnected. event : 6, reason=2 from XX:XX:XX
<6>[182002.194251] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_LINK
<6>[182002.207744] cfg80211: Calling CRDA to update world regulatory domain
A Google search for the error message "wapi is null" doesn't turn up much apart from a few others having that issue with the Xperia Z/ZR and in those cases it seems to be an hardware issue (although it seems to be the same person involved in all of those forum and blog posts?). That doesn't bode too well, but on the other hand, I can connect to my 5 GHz wifi AP at home and at work just fine.
I guess I should do a few tests with Bluetooth turned off. I'm pretty sure I wasn't having this issue when I first got this phone (and running SW version .55), although I can't say for certain since I can't remember exactly when this issue popped up.
Update:
Definitely related to Bluetooth in some way. I turned off Bluetooth, rebooted the phone: Wifi connected to the 2.4 GHz AP at work just fine.
Logcat and dmesg with working wifi:
Code:
06-26 13:09:43.009 1328-1328/? I/wpa_supplicant﹕ wlan0: CTRL-EVENT-SCAN-STARTED
06-26 13:09:46.539 1328-1328/? E/wpa_supplicant﹕ wpa_supplicant_ssid_bss_match : wapi is null
Code:
<6>[ 40.070989] CFG80211-ERROR) wl_cfg80211_add_iw_ie : Previous IW IE is equals to current IE
<6>[ 43.165393] CFG80211-ERROR) wl_cfg80211_connect : Connectting withXX:XX:XX channel (11) ssid "REMOVED", len (13)
<6>[ 50.298294] CFG80211-ERROR) wl_cfg80211_add_iw_ie : Previous IW IE is equals to current IE
<6>[ 118.524346] CFG80211-ERROR) wl_cfg80211_add_iw_ie : Previous IW IE is equals to current IE
OK, so the "wapi is null" and "Previous IW IE" error messages still pop up, even with working wifi. So probably not related.
Then I turned on Bluetooth, Smartband connected, and what do you know? Wifi is now instantly borked again.
Dmesg, the wl_escan errors return:
Code:
<6>[ 1310.249870] CFG80211-ERROR) wl_scan_timeout : timer expired
<6>[ 1310.250082] CFG80211-ERROR) wl_escan_handler : WLC_E_STATUS_TIMEOUT : scan_request[f0083500]
<6>[ 1310.250131] CFG80211-ERROR) wl_escan_handler : escan_on[1], reason[0xffffffff]
<6>[ 1310.254431] CFG80211-ERROR) wl_escan_handler : escan is not ready ndev f3b2e800 wl->escan_on 1 drv_status 0x0 e_type 69 e_states 4
I've used the Smartband since the first day I received the phone (since it was bundled with the phone), and I can say with 99.99% certainty that this wasn't an issue to begin with. Unfortunately, I can't remember exactly when this happened first, so it's hard to track down which changes (if any) to the phone causing this. I updated from .55 to .402 at one point (.69 was never released for this phone I think?), and I've unlocked the bootloader while on .402.
There have also been at least two firmware updates for the Smartband since I started using it, no idea if that could cause any issues like this.
Update 2:
I turned off wifi and restarted the phone. When the phone powered up again, with smartband connected, I activated wifi. Now it suddenly works. No "wapi is null" errors in logcat, no wl_scan / wl_escan related dmesg entries. Could be a driver / firmware issue rather than an actual hardware issue, which is a good thing I suppose. Let's see how long it keeps working...
I had the same issue when I was connected to my 2.4Ghz channel but 5Ghz works fine. Had that problem when I was back on .55 firmware. Haven't tested if it has been fixed by the .438 FW yet.
Android 4.4.2 has some wifi issues, sony may have patched in upcoming firmwares
Google have fixed the issue in 4.4.3
Sent from my D6503 using XDA Premium 4 mobile app
My Xperia Z2 does not connect on 802.11n wifi, this is a bug in the firmware .402 ?
Envious_Data said:
Android 4.4.2 has some wifi issues, sony may have patched in upcoming firmwares
Google have fixed the issue in 4.4.3
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hope it comes soon then...unless they are working on Android L instead...
benengyj said:
Hope it comes soon then...unless they are working on Android L instead...
Click to expand...
Click to collapse
Android L is not coming at all for a very long time
This update is supose to fix things
Sony had listed on their support site
Fixed all heating posible
Fixed some lag problems
Some others, i dont remember site or what else it says,
I think it may be coming to Z2 from few weeks to a couple of months, of course sony being sony they also mentioned the update is unstable, and also not to mention it hasent been certified by PTCRB
Sent from my D6503 using XDA Premium 4 mobile app
Einride said:
Update 2:
I turned off wifi and restarted the phone. When the phone powered up again, with smartband connected, I activated wifi. Now it suddenly works. No "wapi is null" errors in logcat, no wl_scan / wl_escan related dmesg entries. Could be a driver / firmware issue rather than an actual hardware issue, which is a good thing I suppose. Let's see how long it keeps working...
Click to expand...
Click to collapse
Hey, guess what? I was having this problem all throughout the last couple of days (wifi would be a pain to connect and when it did, it might as well not be connected at all) and you'll never guess what solved it... Yes, just like above, I turned off wifi (keeping bluetooth on - I also have the SmartBand on from day one) and when the phone powered up again, wifi turned itself on (location based), but it worked as it should - no problems at all.
I'm guessing this is really a driver/software issue. Really hope the 4.4.4 update solves it...
No need to restart the phone, just enable airplane mode a few seconds and disable it. Wifi will work again.
I seem to have fixed my issue by restoring the factory settings on my modem/router and resetting it.
Tiu Fiu said:
I'm guessing this is really a driver/software issue. Really hope the 4.4.4 update solves it...
Click to expand...
Click to collapse
Yeah, I haven't had this issue in weeks now, so it's definitely down to softwware and/or drivers.
new update! 17.1.2.A.0.314 ! wifi fixed or not?!
Its not 4.4.3/4 which 4.4.2 seems to have the bug, we will have to see if someome flashes the firmware
Sent from my D6503 using XDA Premium 4 mobile app
This bug was caused by the extended standby feature of stamina mode. After turn it off i don't have any issue with wifi anymore
Tiu Fiu said:
Hey, guess what? I was having this problem all throughout the last couple of days (wifi would be a pain to connect and when it did, it might as well not be connected at all) and you'll never guess what solved it... Yes, just like above, I turned off wifi (keeping bluetooth on - I also have the SmartBand on from day one) and when the phone powered up again, wifi turned itself on (location based), but it worked as it should - no problems at all.
I'm guessing this is really a driver/software issue. Really hope the 4.4.4 update solves it...
Click to expand...
Click to collapse
Weirdly, yes - this worked for me as well. I was getting amazing wifi speeds, even after rooting the phone... then last night, it just stopped. Same problem: strong signal, connected...but no internet. (DNS problem, maybe?)
Doing what was suggested above: turning off wifi, rebooting, turning on wifi "corrected" the problem. So, some cache somewhere was cleared out by this action - or some sort of collision between the wifi chip and something else on the phone occurred during one of the reboot cycles.
Either way, it's weird - and I hate weird. Gonna keep my eye on this.... but thank you for the suggestion, man - worked great.
Are you all using smartband or BT hands-free?
I have this problem only on wifi and only when my BT is in (smartband connected)
Few times per day I have to activate airplane mod to reset wifi connection.
But when my BT is off - there's no problems at all...
I really hope that Sony will find a way to "fix" or set (maybe better word) BT and wifi combo...
Sent from my D6503 using Tapatalk
I've had wifi issues for a while, it never even crossed my mind it could be my smartband. It really annoyed me this morning so I looked into it and found this thread. I wish they'd fix it soon. It's irritating. :/
Same problem here but no smart watch
Same problem here but I don't have blue tooth on or use that Smartband. Same trick solves the issue tho.
Cheers, Bentree
Can anyone confirm if the 4.4.4 firmware has fixed this bug? Still waiting for my countries firmware update but I am hoping it is resolved...
Wi-Fi
Hey Guus,
I have the same issue with Wi-Fi connection. Also on 4.4.4, it drives me crazy . Only what helps sometimes is turning Wi-Fi off ----> Wi-Fi on.
Hope that anyone knows how to solve this problem very soon.