data connection constantly switching between umts and hspa

Search This thread

jodue

Senior Member
Dec 15, 2009
453
37
vienna
my device has this odd behaviour i have already seen years ago on my htc magic. tje mobile data connection switches between umts and hspa constantly which can be observed by the chqnging H/3G icon. every time it switches the transfer stops which makes the mobile data connection painfully slow at most times... wifi is working perfectly btw.

as far as i understand it this is a bug in the radio firmware. my htc magic stopped showing this behaviour after a firmware update...

anyone else having this issue?
 

Thiesen

Senior Member
Aug 8, 2009
301
18
Oh the dreaded "arrow up" "bug" is at large still with 3 it seems.'

I have the HTC Desire (will be getting the HOS) and 3 as carrier too...

That "bug" was even present in my HTC Hero.

Three different phones on 3 all made by HTC can't be an coincident?
 

jodue

Senior Member
Dec 15, 2009
453
37
vienna
Three different phones on 3 all made by HTC can't be an coincident?

4, including my htc magic ;) however the one s is an awesome phone and i guess this problem will be fixable with a radio firmware update soon... interresting that it seems to happen with 3 mostly...didn't have it with my galaxy s however. seems to be htc+3 ...

i will probably write htc's and 3's tech support. as 3 austria will be introducing the one s soon they will have to deal with this bug soon anyway...

Sent from my HTC One S using XDA
 

keinengel

Senior Member
Dec 7, 2009
461
32
I've actually got the exact same problem on my Desire Z on T-Mobile DE. Not sure what to make of it. And I've played with the One S in a Telekom Shop and it seems to be switching wildly between 3G and H too.
The same Desire Z didn't have this problem with a Vodafone Romania SIM card in Bucharest.
 

jodue

Senior Member
Dec 15, 2009
453
37
vienna
I've actually got the exact same problem on my Desire Z on T-Mobile DE. Not sure what to make of it. And I've played with the One S in a Telekom Shop and it seems to be switching wildly between 3G and H too.
The same Desire Z didn't have this problem with a Vodafone Romania SIM card in Bucharest.

hm ... i guess/hope it's a bug in the radio firmware as the data transfer works fine for the rest of the connection after the initial 2 switches from HSPA to UMTS and vice versa. a google search shows that many people with different devices seem to have this issue...

anyway i wrote two emails, one to my carrier (three-austria) and one to htc. i will post any replys!
 

Nightfrag07

Member
Mar 31, 2009
6
0
I have the same Problem with my new HTC One S. :(

The connection switches constantly between 3G and H and the connection stops. It loads 1-3 MB and after that it takes !10 or more seconds! before it is loading another 1-3MB...

You can not do things like Youtube or Mobile TV because the loading process takes forever with a 3G and HSPA switching connection!

I tried my new (big) SIM Card (from 3 Austria) with my HTC HD2 before i switched to the micro SIM (from 3 Austria) and the connection speed on my HD2 was 5-10 times faster as with my new HTC One S and this can not be!! :confused: (HD2 is running Custom Andriod 2.3.7 with radio 2.15.50.14.)

It has to be a major radio software bug that is unexaptable for such an expensive phone!

The Internet is extremely fast with Wifi on my One S... but on the way i doesnt have a Wifi connection...

I really want to keep the phone and everything else works amazingly good but this bug drives me crazy. :(

I reported this problem to HTC and 3 (drei) as well via E-Mail.

Should i keep the phone?? Or is it better to send it back to Amazon, because i have only 12 days left to send it back without any reason.

Is HTC going to release a radio firmware update very soon? I have no experience with Android updates and HTC. How long does it usually take to receive updates from HTC?

Thanks in advance!
 

jodue

Senior Member
Dec 15, 2009
453
37
vienna
hi, i understand that you are also on three (drei) in austria, probably even in vienna?!

i also sent mails describing the exact problem to three and htc. however neither one was able to give me any more information than what i already new. inbetween i tried a hardware (factory) reset and another sim (on yesss!), but the problem persited.

after several mails back and fourth the htc guy now wrote me a standard "your unit maybe broke and you can send it in for repair" email. however i am pretty sure that this is no hardware defekt but a bug in the radio firmware in which case exchanging the phone would not serve.

it is hard to say how long it will take htc to deliver an update for the radio firmware that fixes this bug. despite the htc support giving me the standard "exchange the unit" answer i will try to push them to get the ticket to the development department. i think that this should not be too hard to fix if they are aware of the problem.
 

jodue

Senior Member
Dec 15, 2009
453
37
vienna
i was just at a local three store in vienna. they said that they don't know of other people having this issue. i checked the software version of the devices they sell against my unlocked one s. same baseband version however a different (and newer!) build number. sadly this firmware is not available yet so there is no way to check if an update will solve the issue.
 

packetlos

Senior Member
Jan 13, 2009
66
13
North East England
I have this problem with T-Mobile UK, I have had the same problem in the past with the Desire HD however it was eventually resolved with a software update.

With the chipping problem and now this it is really starting to put a downer on owning this phone. :(
 

jodue

Senior Member
Dec 15, 2009
453
37
vienna
I seem to have the same problem on Vodafone Germany

Sent from my HTC One S using XDA

I have this problem with T-Mobile UK, I have had the same problem in the past with the Desire HD however it was eventually resolved with a software update.

With the chipping problem and now this it is really starting to put a downer on owning this phone. :(

can you please post your build number? i have 1.53.401.2 CL47230 however the device in the three store had somthing like 1.53.771.*
 

jodue

Senior Member
Dec 15, 2009
453
37
vienna
hm interresting! so the problem actually occurs with many different carriers... would be good to know if anybody solved the problem by exchanging the device?!!

@Goody81: i am not 100% sure but i'd say after all testing and looking at system-/kernel-logs i am pretty convinced that this is a firmware (software) issue. i cannot say that the slightly newer build on the device was due to carrier modifications or if they actually changed something to fix this issue. the guy how showed my the device was no engineer and had no idea what i tried to explain :D

if this is a software issue and they already fixed it i hope htc delivers the update soon!
 

Nightfrag07

Member
Mar 31, 2009
6
0
hi, i understand that you are also on three (drei) in austria, probably even in vienna?!

i also sent mails describing the exact problem to three and htc. however neither one was able to give me any more information than what i already new. inbetween i tried a hardware (factory) reset and another sim (on yesss!), but the problem persited.

after several mails back and fourth the htc guy now wrote me a standard "your unit maybe broke and you can send it in for repair" email. however i am pretty sure that this is no hardware defekt but a bug in the radio firmware in which case exchanging the phone would not serve.

it is hard to say how long it will take htc to deliver an update for the radio firmware that fixes this bug. despite the htc support giving me the standard "exchange the unit" answer i will try to push them to get the ticket to the development department. i think that this should not be too hard to fix if they are aware of the problem.

No but i live close to vienna. ;)
I tried everything! Restarts, factory reset, delete all stuff on the device, the full program but still the same problem.

Yesterday i received a phone call from 3 Tech support in Germany and i described the problem to him!
He said the problem does not exist with their 3 branded phones.
Then i said, i have a open (not branded) phone from Amazon and i think that is a part of the problem. Later i asked about updates and then he said in most cases it took 9 Month to receive a original update from HTC and thats way to long for me.

So i decided to send my phone back and now i am looking for a phone with the newer radio software on it. It seems the only way for now is to buy it at a 3 (three, drei) Store.

But that's just my own opinion ! You can also wait for a custom rom or radio here at xda and hope this problem will be fixed soon.

But if you want to get sure to receive a working phone with fast internet connection you should buy it direct from a 3 store because they have a customized (and branded) software in order to get it working!
And that software doesnt exist or is not available on a open phone yet.

Anyway, i was not very excited when I heard about that! :(
 

jodue

Senior Member
Dec 15, 2009
453
37
vienna
Later i asked about updates and then he said in most cases it took 9 Month to receive a original update from HTC and thats way to long for me.

hehe i think 9 month is a "little" exaggerated ... this is not a major update like a new android version but a small bug-fix update. i would guess that an updated firmware will leak soon and if you are willing to unlock the bootloader you can update instantly. however i have to agree, i am tempted to return the device as well or at least try a demo unit in a store with my sim card to make 100% sure it's no hardware defekt...

this is an unfortunate pain in the a** since i like everything else about this phone and don't want to return it ^^
 

Nightfrag07

Member
Mar 31, 2009
6
0
hehe i think 9 month is a "little" exaggerated ... this is not a major update like a new android version but a small bug-fix update.

this is an unfortunate pain in the a** since i like everything else about this phone and don't want to return it ^^

Yeah you are right. It would be a bug-fix or only a radio update but i liked that phone and i want a working (non switching) one asap! :D

And of course i have to try it in the 3 Shop first with my own SIM card. ;)
 

Nightfrag07

Member
Mar 31, 2009
6
0
Three different phones on 3 all made by HTC can't be an coincident?

Oh i forgot!!

The 3 Tech support man from Germany also said they having the same problem on Samsung phones with Android 4.0.4. I think they will also have a fix for this soon.

So make sure not to buy such a phone as well at this time! :p

It's definitive not only a HTC problem... ;)
 

jodue

Senior Member
Dec 15, 2009
453
37
vienna
Oh i forgot!!

The 3 Tech support man from Germany also said they having the same problem on Samsung phones with Android 4.0.4. I think they will also have a fix for this soon.

So make sure not to buy such a phone as well at this time! :p

It's definitive not only a HTC problem... ;)

yeah, i told my girlfriend about the issue yesterday and she has experienced it on her (my old) galaxy s with the new cm9 nightlies as well. not as often as on my one s however ...

after reading about this issue on this forum (german) and more general about mobile data connections with umts/hspa (german) i think it the issue is the result of an error in the umts<->hspa switching algorithm. as explained on the 2nd link the device will switch from umts to hspa if the bandwidth increases above a certain threshold (~380k) which will interrupt the connection. so far this is normal behaviour however it should not change constantly between during the transfer of data. i am able to achieve a stable (uninterruped) download if a set the maximal bandwidth below ~300kbit. above this threshold the problem occures.

i am now 99.9% sure this is no hw-issue so i will keep the device and a) hope for either htc or three to make modifications/an update to solve this isssue. b) i will investigate if this threshold/algorithm can be influenced with either build.prop or some other method in which case i will root the device and try do develop a fix. i think everybody that has this issue should inform htc about it as they probably have the best chance to fix it fast.

edit: if someone with a three (drei) branded device reads this: i would very much appreciate it if you could post your /system/build.prop file here! thank you in advance!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    I had the same annoying switching problem and i managed to fix it by rooting the phone and changing fast dormancy rule to look like this :

    ro.ril.fast.dormancy.rule=#

    also changing the following line to look as shown solved my no network issues when i was in areas of weak reception

    ro.ril.disable.power.collapse = 1
    1
    So if i want to read the build.prop file directly on the phone i have to root it. Right?

    no you don't but you would need a file manager that allows you to browse the entire file system (not only the sdcard) like "OI File Manager". but after playing with the properties in the build.prop file, i think the issue can't be solved just by adapting this file. i managed to force the phone to use UMTS-only (ro.ril.hsxpa=0) which solved the connection hickups but the connection was slow: down average ~200kbit/sec, up average: ~350kbit/sec. not yet a solution but a start that i consider one more pointer towards a SW-bug.

    Im not what you are calling an expert at this forum but i am reading much and try to understand most of the programs on my phone.

    i think being curious is all that counts :)
    1
    Another curious know-nothing here - using Astro I looked in system > build, but it says "file type prop not found".

    Since I am on 3UK I was going to try and give some of the info you asked for. Am i looking in the wrong place?

    1.53.771.4 is the software number of my phone.
    1
    Baseband version is 0.15.31501S.19_2_10.13.31501S.06L

    And kernel version is 3.0.8-01051-g0772019

    Not too familiar with the inner workings of my phone but I'll have bash at retrieving the info. :eek:

    ---------- Post added at 01:13 PM ---------- Previous post was at 01:05 PM ----------

    ro.ril.ecc.H3G-AT=112,911
    ro.ril.ecc.H3G-SWE=112
    ro.ril.ecc.H3G-ROI=112,999
    ro.ril.ecc.H3G-UK=999,112
    ro.ril.enable.a53.H3G-UK=1
    ro.ril.enable.amr.wb.H3G__001=1
    ro.ril.enable.a53.H3G-SWE=1
    ro.ril.enable.gea3.H3G__G04=1
    ro.ril.enable.dtm.H3G__G04=0
    ro.ril.enable.amr.wb.H3G__G04=1
    ro.ril.enable.gea3.H3G__106=1
    ro.ril.enable.dtm.H3G__106=0
    ro.ril.enable.amr.wb.H3G__106=1
    ro.ril.enable.a52=0
    ro.ril.enable.a53=1
    ro.ril.enable.dtm=1
    ro.ril.hsdpa.category=14
    ro.ril.hsupa.category=6
    ro.ril.hsxpa=4
    ro.ril.fast.dormancy.rule=2
    ro.ril.disable.fd.plmn.prefix=23402,23410,23411,23420,27202,24002
    ro.ril.enable.sdr=1
    ro.ril.oem.show.act=1
    ro.ril.n-roaming.mcclist=234,272,222,240,232
    ro.ril.set.mtusize=1500
    ro.ril.enable.r8fd=0
    ro.ril.disable.cpc=1
    ro.ril.h3g.efust=1
    ro.com.google.clientidbase=android-htc
    ro.com.google.clientidbase.yt=android-htc
    ro.com.google.clientidbase.am=android-h3g-{country}
    ro.com.google.clientidbase.gmm=android-htc
    ro.com.google.clientidbase.ms=android-h3g-{country}
    ro.ril.vmail.23420=+447782333123
    ro.ril.vmail.27205=+353833333171
    ro.product.model=HTC One S
    ro.htc.checkin.delay=1
    ro.watch.appid=com.sdgtl.watch.vieu_40_ics
    ro.ril.fd.pre_r8_tout.scr_off=3
    ro.ril.fd.pre_r8_tout.scr_on=0
    ro.ril.fd.r8_tout.scr_off=0
    ro.ril.fd.r8_tout.scr_on=0
    dev.defaultwallpaper=/system/customize/resource/scene_wallpaper_htc_default.jpg
    dev.deviceimage_large=/system/customize/resource/ville-htc_187x370.png
    dev.deviceimage_small=/system/customize/resource/ville-htc_32x58.png
    # begin build properties
    # autogenerated by buildinfo.sh
    ro.aa.customizationid=346854
    ro.aa.project=Ville_U
    ro.aa.romver=1.53.771.4
    ro.aa.maincid=H3G__001
    ro.aa.modelid=PJ4010000
    ro.aa.cidlist=H3G__001,H3G__106,H3G__G04
    ro.aa.rid=680
    ro.aa.taskid=251870
    ro.aa.skulist=771
    ro.aa.mainsku=771
    ro.cwkey=H3G__001
    ro.com.google.clientidbase=android-htc
    ro.build.id=IML74K
    ro.build.display.id=IML74K
    ro.build.version.incremental=47441.4
    ro.build.version.sdk=15
    ro.build.version.codename=REL
    ro.build.version.release=4.0.3
    ro.build.date=三 3月 21 19:49:30 CST 2012
    ro.build.date.utc=1332330570
    ro.build.type=user
    ro.build.user=
    ro.build.host=ABM010
    ro.build.tags=release-keys
    ro.product.model=VLE_U
    ro.product.brand=h3g_uk
    ro.product.name=ville
    ro.product.device=ville
    ro.product.board=MSM8960
    ro.product.cpu.abi=armeabi-v7a
    ro.product.cpu.abi2=armeabi
    ro.product.manufacturer=HTC
    ro.product.locale.language=hdpi
    ro.wifi.channels=
    ro.board.platform=msm8960
    # ro.build.product is obsolete; use ro.product.device
    ro.build.product=ville
    # Do not try to parse ro.build.description or .fingerprint
    ro.build.description=1.53.771.4 CL47441 release-keys
    ro.build.description=1.53.771.4 CL47441 release-keys
    ro.build.changelist=47441
    ro.build.fingerprint=h3g_uk/ville/ville:4.0.3/IML74K/47441.4:user/release-keys
    ro.build.characteristics=default
    ro.build.project=Ville_U:251870
    ro.product.version=1.53.771.4
    ro.build.languageremove=0
    ro.build.sense.version=4.0
    keyguard.no_require_sim=1
    # end build properties
    #
    # system.prop for surf
    #
    ro.sf.lcd_density=240

    rild.libpath=/system/lib/libril-qc-qmi-1.so
    # RilLibPath for Ganlite
    rild.libpath.ganlite=/system/lib/librilswitch.so
    rilswitch.vendorlibpath=/system/lib/libril-qc-qmi-1.so
    rilswitch.ganlibpath=/system/lib/libganril.so

    rild.libargs=-d /dev/smd0
    persist.rild.nitz_plmn=
    persist.rild.nitz_long_ons_0=
    persist.rild.nitz_long_ons_1=
    persist.rild.nitz_long_ons_2=
    persist.rild.nitz_long_ons_3=
    persist.rild.nitz_short_ons_0=
    persist.rild.nitz_short_ons_1=
    persist.rild.nitz_short_ons_2=
    persist.rild.nitz_short_ons_3=
    persist.rild.ril.ltedr=0
    persist.rild.ril.ltedrtable=max_retries=infinite,10000
    ril.subscription.types=NV,RUIM
    DEVICE_PROVISIONED=1
    debug.sf.hw=1
    debug.egl.hw=1
    debug.composition.type=dyn
    # For ICS project, default 32m/48m
    dalvik.vm.heapsize=128m
    dalvik.vm.heapgrowthlimit=48m
    ro.sf.compbypass.enable=1
    debug.enabletr=true
    debug.qctwa.preservebuf=1
    dev.pm.dyn_samplingrate=1

    persist.radio.adb_log_on=1
    ro.baseband.arch=msm

    # Default network type.
    # 0 => WCDMA preferred.
    ro.telephony.default_network=0

    #
    # system props for the cne module
    #
    persist.cne.UseCne=false
    persist.cne.bat.range.low.med=30
    persist.cne.bat.range.med.high=60
    persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
    persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
    persist.cne.bwbased.rat.sel=false
    persist.cne.snsr.based.rat.mgt=false
    persist.cne.bat.based.rat.mgt=false
    persist.cne.be.ge.sqi.min=0
    persist.cne.be.ge.sqi.max=100
    persist.cne.be.umts.sqi.min=0
    persist.cne.be.umts.sqi.max=100
    persist.cne.be.hspa.sqi.min=0
    persist.cne.be.hspa.sqi.max=100
    persist.cne.be.1x.sqi.min=0
    persist.cne.be.1x.sqi.max=100
    persist.cne.be.do.sqi.min=0
    persist.cne.be.do.sqi.max=100
    persist.cne.be.wlan.sqi.min=0
    persist.cne.be.wlan.sqi.max=100
    ro.hdmi.enable=true
    lpa.decode=true
    lpa.tunnel=true
    lpa.use-stagefright=true
    htc.audio.lpa.a2dp=0
    htc.audio.global.state=0
    htc.audio.global.profile=0
    htc.audio.q6.topology=0
    #export for SoundHound
    persist.htc.audio.pcm.samplerate=44100
    persist.htc.audio.pcm.channels=2

    #system props for the MM modules

    media.stagefright.enable-player=true
    media.stagefright.enable-http=true
    media.stagefright.enable-aac=true
    media.stagefright.enable-qcp=true
    media.stagefright.enable-fma2dp=true
    media.stagefright.enable-scan=true
    #
    # system props for the data modules
    #
    ro.use_data_netmgrd=true
    persist.data_netmgrd_mtu=1440

    #
    # system props for telephony modules
    #
    #device supports LTE
    ro.config.lte=true
    #device supports EHRPD
    #ro.config.ehrpd=true
    #device supports simultaneous 1x voice + LTE
    #ro.config.svlte1x=true
    # Modify MMS APN retry timer from 5s to 2s.
    ro.gsm.2nd_data_retry_config = max_retries=3, 2000, 2000, 2000

    # holiday RF team request
    ro.ril.enable.dtm = 0
    ro.ril.gprsclass = 12
    ro.ril.hsdpa.category = 14
    ro.ril.hsupa.category = 6
    ro.ril.hsxpa = 4

    # For the default value of agps
    ro.ril.def.agps.mode = 2

    # For HSDPA low throughput
    ro.ril.disable.power.collapse = 1

    #system props for time-services
    persist.timed.enable=true

    # System props for audio
    persist.audio.fluence.mode=endfire
    persist.audio.vr.enable=false
    persist.audio.handset.mic=analog

    #
    # system prop for opengles version
    #
    # 131072 is decimal for 0x20000 to report version 2
    ro.opengles.version=131072

    #
    # system prop for Bluetooth Dialup Networking
    #
    ro.qualcomm.bluetooth.dun=false

    # system prop for Bluetooth FTP profile
    ro.qualcomm.bluetooth.ftp=true
    #
    # system property for Bluetooth Handsfree Profile Wide Band Speech
    #
    ro.qualcomm.bluetooth.hfp.wbs=false
    #
    #system prop for Bluetooth hci transport
    ro.qualcomm.bt.hci_transport=smd
    #
    # system prop for requesting Master role in incoming Bluetooth connection.
    #
    ro.bluetooth.request.master=true
    #
    # system prop for Bluetooth Auto connect for remote initated connections
    #
    ro.bluetooth.remote.autoconnect=true
    # system property for Bluetooth discoverability time out in seconds
    # 0: Always discoverable
    #debug.bt.discoverable_time=0

    # system property for Bluetooth Hardware information
    ro.product.bluetooth=4.0

    #system prop for switching gps driver to qmi
    persist.gps.qmienabled=true

    # System property for cabl
    ro.qualcomm.cabl=0

    # system property for thermald
    persist.thermal.monitor=true

    # For internal fat file system
    ro.phone_fat = 1

    # Following property will be reference by Settings.
    ro.product.display_resolution = 4.3 inch qHD resolution

    # Camera H/W information
    ro.product.main_camera = 8M
    ro.product.front_camera = VGA

    ro.product.processor = Dual Core
    ro.product.ram = 1GB

    # hTC FOTA property for SIE.
    ro.htc.checkin.delay = 3
    ro.config.htc.nocheckin = 0
    ro.config.htc.noappupdate = 0

    # wifi
    wifi.softap.interface=wlan0
    wifi.softapconcurrent.interface=softap.0
    ro.product.wifi = 802.11 b/g/n

    init.svc.wpa_supplicant=
    init.svc.dhcpcd_wlan0=
    dhcp.wlan0.autoip=
    dhcp.wlan0.dns1=
    dhcp.wlan0.dns2=
    dhcp.wlan0.dns3=
    dhcp.wlan0.dns4=
    dhcp.wlan0.gateway=
    dhcp.wlan0.ipaddress=
    dhcp.wlan0.leasetime=
    dhcp.wlan0.mask=
    dhcp.wlan0.ooxx=
    dhcp.wlan0.pid=
    dhcp.wlan0.reason=
    dhcp.wlan0.result=
    dhcp.wlan0.server=
    net.wlan0.dns1=
    net.wlan0.dns2=
    wifi.wpa_supp_ready=
    wlan.driver.status=

    # Support HW reset
    ro.product.hwreset = 1

    # Support autobot car pc
    ro.htc.htcmode.data.path = /dev/ttyHSUSB3

    #
    # ADDITIONAL_BUILD_PROPERTIES
    #
    ro.config.notification_sound=OnTheHunt.ogg
    ro.config.alarm_alert=Alarm_Classic.ogg
    drm.service.enabled=true
    ro.setupwizard.mode=DISABLED
    ro.com.google.gmsversion=4.0_r1
    ro.vendor.extension_library=/system/lib/libqc-opt.so
    ro.com.google.clientidbase=android-qualcomm
    htc.audio.swalt.enable=1
    htc.audio.swalt.mingain=14512
    htc.audio.alc.enable=1
    ro.service.dpsvr.enabled=true
    net.bt.name=Android
    dalvik.vm.stack-trace-file=/data/anr/traces.txt
    1
    did the first change and things looks really better!!!
    as I mentioned, the 2nd one was already in that state (maybe due to 1.78 update).
    another issue I'm and other are having is a drop of network signal - probably due to lack of ability of the phone to re-register to the network - do you have any clue of a change can be done to resolve that? I'm on automatic network choosing.

    To tell you the truth i made a lot of changes to my build prop using various different sources.

    Here is my build.prop

    http://dl.dropbox.com/u/76981927/build.prop

    Compare them and see if anything stands out.

    Make a backup first before you make any changes and save it as something different (just add ".old" without speech marks) as root explorer will automatically write over any previous .bak you have of the file.