Are there two physical radios in the Tilt/TyTN II? I ask because I'm experiencing a strange problem that nobody else seems to have seen before. That, or nobody noticed my posts here:
http://forum.xda-developers.com/showthread.php?t=335096
The problem is that phone/data work fine when the phone is in non-3G mode. (In the Comm Manager, available in most recent ROMs, I have disabled the 3G mode, so I'm using only GSM here in the US).
In 3G mode, I'll get a 3G icon (used to get an H, months ago), but will be unable to place/receive calls, and no data connections will be established -- they'll all time out or say that "the answering modem has disconnected."
So, back to my question: is it possible that my radio is partly damaged? Can that happen? I'm not sure how else to explain the utter lack of 3G on my phone.
can't have a damaged radio, you could have the wrong radio for the device and/or version of windows mobile. 3g only works if in 3g area,have it enabled and turned on through comm manager.also make sure you're network settings are correct and make sure phone is set to auto in networks tab in phone settings,not set to gsm/cdma
PS, the search tool/wiki are you're friends since this has been covered too many times
dyetheskin said:
can't have a damaged radio, you could have the wrong radio for the device and/or version of windows mobile. 3g only works if in 3g area,have it enabled and turned on through comm manager.also make sure you're network settings are correct and make sure phone is set to auto in networks tab in phone settings,not set to gsm/cdma
PS, the search tool/wiki are you're friends since this has been covered too many times
Click to expand...
Click to collapse
Thanks for the advice. Unfortunately, I've tried everything I can think of, and everything suggested. Nearly ever ROM I've seen, with nearly every radio; every combination of wap.cingular, isp.cingular, etc. The AT&T store thinks the phone is defective b/c they can't figure it out, either. In response to your comments: tried every version of windows mobile and most of the radios available; I'm very much in a HSDPA 3G area (used to get 5 bars "H" all the time); 3G is enabled; network settings are correct; phone is set to auto/auto.
Any other ideas, anyone? I appreciate it!
I've been have the same exact problem. I posted about it about a month and a half ago, but got nothing.
Everything worked perfectly until one day, out of nowhere, 3G stopped working for me. I've also tried multiple radios and ROMs and to no avail. The weird thing is that when it stopped working, nothing had been changed in months.
I know that I'm definitely in a 3G coverage area because I used to get 3G service all the time.
If I turn 3G on, it'll work in an edge only area, but as soon as it switches over to WCDMA, the problems occur.
This is super aggravating.
AndyNJ said:
I've been have the same exact problem. I posted about it about a month and a half ago, but got nothing.
Everything worked perfectly until one day, out of nowhere, 3G stopped working for me. I've also tried multiple radios and ROMs and to no avail. The weird thing is that when it stopped working, nothing had been changed in months.
I know that I'm definitely in a 3G coverage area because I used to get 3G service all the time.
If I turn 3G on, it'll work in an edge only area, but as soon as it switches over to WCDMA, the problems occur.
This is super aggravating.
Click to expand...
Click to collapse
Well, the good part is, you're not alone. I found another forum online (can't remember where, I'm at work now and I found it last night) were several people were having the exact same problem -- in various countries around the world, including the US.
They had decent luck flashing the stock HTC ROM and then the French radio mentioned on the big XDA radio post (search google for "kaiser radio" and you should see it). However, I did the same and still have the 3G problem.
did you try using a shipped att rom and see if you still have this problem? if the problem goes away, then maybe its just a rom/radio mismatch problem. if it doesnt, then its more likely a hardware failure.
I'm in france, and since few days, i've the same problem, and i haven't change the radio. the phone is going for repair.
link to my post
XtreMe_G said:
did you try using a shipped att rom and see if you still have this problem? if the problem goes away, then maybe its just a rom/radio mismatch problem. if it doesnt, then its more likely a hardware failure.
Click to expand...
Click to collapse
Yep -- I've tried going all the way back to the original ROM and radio. No go.
yeantbron said:
I'm in france, and since few days, i've the same problem, and i haven't change the radio. the phone is going for repair.
link to my post
Click to expand...
Click to collapse
Can you keep us posted on what happens when it comes back? If it's really a hardware problem, many inquiring minds would love to know.
Bonne chance!
chaosniner said:
Are there two physical radios in the Tilt/TyTN II? I ask because I'm experiencing a strange problem that nobody else seems to have seen before. That, or nobody noticed my posts here:
Click to expand...
Click to collapse
As mentioned in this thread, some shipments of the TyTN II have faulty hardware with broken 3G support.
No patch or driver update can fix this because it is a hardware problem. I experienced exactly the same issue with my first TyTN II and finally replaced it with a new device which works flawlessly out of the box.
I believe you should also better get your device replaced if you ever want to use 3G.
Can you keep us posted on what happens when it comes back? If it's really a hardware problem, many inquiring minds would love to know.
Click to expand...
Click to collapse
Yes of course !
Well, 4 days to receive my phone !!
and they have changed :
_motherboard
_antenna
and MAJ rom and radio
Version de ROM : 1.56.163.8 ===> 1.56.163.9
Date de ROM : 09/04/07 ===> 10/15/07
Version de radio : 1.27.12.11 ===> 1.27.12.32
Version de protocole : 22.45.88.07H ===> not changed
are you saying you have gotten your phone back? is it working now?
Related
Hello All,
Been reading this forum for quite a while, 1st time posting. This community has helped me improve my life immeasurably in the past couple years.
I got an HTC Tilt a couple days ago. Unfortunately it's not able to be returned or warrantied. When I first turned the device on it saw the 3G network (or at least displayed the icon; I never had the chance to connect). I navigated to my sd card and went to delete Fieldtest.exe, which I had placed there for ease of use from my previous 8525 (I do some network testing for my job). I forgot and tapped it rather than holding down the stylus and opened the program; the 3G icon disappeared and went to E and I haven't been able to get it back. I've tried clearing the memory and have completely reflashed the device using the HTC retail ROM. Also tried kaisertweaks to enable HSDPA and the bandselect tool.
This is really bizarre. I don't think that Fieldtest.exe could have damaged just the 3G portion of the chipset.. but I'm running out of ideas. I've searched through this forum (finding wonderful nuggets of information as usual - can't wait to try Digitaltigre's method for using the Kaiser, or maybe old 8525, as DiNovo Mini) and others to try to find others with a similar experience and I've done the obvious (reflashing the radio I thought for sure would do it). Besides this the device works great - EDGE connects and is usable, voice calling works, tethering works, etc.
Any ideas you folks can come up with would be greatly appreciated,
Thanks,
Shoehopper
ROM: 1.62.502.0
ROM date: 01/17/08
Radio version: 1.27.14.09
Protocol version: 22.45.88.07H
And I'm in a very strong 3G area (-65 to -70 dBm typically)
did u try changing your rom or doing a clear storage?
I tried both. The ROM I reflashed was the same version as the ROM that was already on it however.
try a different one
are you sure your area is 3G enabled? or at least have decent enough 3g coverage.
try this one addon it's called band select. it adds a tab to your phone settings where it lets you pick auto, regular gsm (G,E), or 3G. You can then force it to be on 3G only. The problem is, if this doesnt work it may mean what you thought earlier that either your 3G chip is messed up or you just not in a decent coverage area for 3G.
i cant find it on my pc, if you do a quick search you may unveil it. hope that helps
using 3g off/on in comm manager works for me or if i wanna get serious i use bandswitch or comm manager pro www.commmgrpro.com
shoehopper said:
...Unfortunately it's not able to be returned or warrantied...
Click to expand...
Click to collapse
Why is this? Even a secondhand Tilt will be less than 1 year old, and covered by AT&T's warranty.
I tried using BandSwitch, when I pick UMTS it constantly searches for signal (... under the antenna icon and x on the connection icon). Selecting Auto reverts to E.
I am certain of being in UMTS area (Redmond, WA HQ building of certain large wireless organization.. which is also why I cannot warranty or exchange he device).
Thanks,
shoehopper
errr nm i did some homework. Thought i had an answer.
eeeekkkkkkk
weird. I have some bugs depending where i am if the signals are real strong, i sometimes cant seem to leave my wifi on and stream info over 3g AND use my bluetooth. Are you running anything else at ALL. ? in the case i mentioned, i sometimes have to turn off my wifi to get my bluetooth to work.
Maybe some weird bug w/ something else your running?
NotATreoFan said:
Why is this? Even a secondhand Tilt will be less than 1 year old, and covered by AT&T's warranty.
Click to expand...
Click to collapse
Found on the side of the road?
fell out of the truck?
Stolen?
It was company provided, which means I'm not out anything personally, but it does have a $ value nonetheless. Being company provided but outside the retail channel, it is not able to be warrantied or returned. Sheesh.. people assume the worst.
I am not running any fancy connections. Haven't even turned on the Wifi or Bluetooth. No programs (besides the aforementioned kaisertweaks, and now BandSelect). It's not that it doesn't connect; it doesn't even SEE that there is UMTS coverage available, only EDGE.
Thanks,
shoehopper
I'd try a warranty exchange anyways, if I were you. (Once you've determined if there is a hardware problem...) Supposedly the warranty follows the device, no matter what channel it takes to get to the current end user. Anyways, that's what I've heard, and it wouldn't hurt to try. Just call customer service and ask for the warranty department.
Hey all,
I've had my TyTn II for a while now and everything's been ok.
I recently upgraded my rom, from an old Duttys rom to a new one, since doing that my phone would not pick up signal at all - I couldn't phone and people couldn't phone me - it looked like my phone had reception but the second I went to call all the bars dropped off.
I posted on here. - It's the radio people assured me. I swapped radios. 1 million times.
Everytime, the 3g would work for a few hours and then the same problem.
I decided it was the rom. I installed a different duttys rom yesterday, and low and behold, the phone worked. Calls, tinterwebs the works.
Got home. Same old problem.
The one thing that links the roms is they're both Windows 6.1.
I'm using a MDA Vario 3 on T-Mobile UK.
Can anyone help me?
31 views - 0 replies.
No one had this before? Or any ideas? Seriously, if someone solves this I'll paypal them £20 as a thanks - it's getting on my nerves THAT much!
bazzlad said:
31 views - 0 replies.
No one had this before? Or any ideas? Seriously, if someone solves this I'll paypal them £20 as a thanks - it's getting on my nerves THAT much!
Click to expand...
Click to collapse
If you want to stick with WM6.1 do as follows:
(i hope you've got HARDSPL...)
Run the TriColor mode and install radio same as i do (signature)
when it start to restarts hold the camera button so you can boot tricolor again without loading rom.
Install your favorite ROM,
When everything is configured, run Connection setup again and restart your phone. Test it.
If it still doesent give anything it could problem with some third party apps or your device itself.
You can try my configuration it works perfectly for me.
Cheers,
Chris
Giving that a go today - will chuck you over some $$$ wonga if it works! Thanks.
I hope that everything will work fine for you. Im always happy to help.
Cheers,
Chris
Tried - No joy - but thanks - anyone else got any ideas?
I have a similar issue. On my 3rd phone now (Orange) due to phone not connecting in 3g mode to make calls. Seems to be an issue where it fails to switch automatically between GSM and 3G, although it often shows there is a network connection (even though there isn't - really anoying).
However, by turning off hsdpa it finally seems (6 hours or so) to stay connected to the network and able to make calls. Can anyone else with the same problem try this?
I don't enough about hsdpa to understand why having it switched on should make a difference, unless it changes the functionality of the radio. Suggestions welcomed.
You may have a faulty handset.
Exactly the same problem as my friend experienced with his MDA Compact 2. I tried flashing new ROMS and it seemed to fix it but in time he'd begin to suffer from a disappearing signal bar and random dropouts before, during and after calls.
You could try turning your network to GSM only and see if that makes a difference. I'm on T-Mobile and I know that last week I couldn't use my phone in 3G mode for 36 hours or more owing to a network problem in my area, gsm worked fine though.
not convinced about the faulty handset although it is a possibility.
I am starting to think that with the hsdpa enabled it somehow changes the way data and voice calls are handled.
Really could do with some opinions on hsdpa and whether enabling it or disabling it changes the functionality of the phone or the interaction with the networks
bazzlad said:
31 views - 0 replies.
No one had this before? Or any ideas? Seriously, if someone solves this I'll paypal them £20 as a thanks - it's getting on my nerves THAT much!
Click to expand...
Click to collapse
Just search a bit in the Kaiser forum, quite a few people (including me) have had similar problems. Radio hardware on some units is faulty and requires return to service center for repair.
The radio starts by not being able to send/receive calls/data on 3G while it still works on GSM, then later GSM will eventually fail too.
T-mobile have had problems with there 3G in the last week in northern Uk. I am still getting a few problems each day as you describe. I dont know, but I am assuming they are doing some repairs
kilrah said:
Just search a bit in the Kaiser forum, quite a few people (including me) have had similar problems. Radio hardware on some units is faulty and requires return to service center for repair.
The radio starts by not being able to send/receive calls/data on 3G while it still works on GSM, then later GSM will eventually fail too.
Click to expand...
Click to collapse
Still, my experience is that there maybe faulty hardware out there, but by disabling hsdpa everything is fine. I'm currently making plenty of calls on 3g network, dowloading lots of data on 3g network. My previous problems were when the handset showed it was connected to the 3g network when it wasn't able to take or make calls or download data. Before, the only thing I had tried was manually selecting GSM in the connection settings.
I'm not saying that disabling hsdpa is a good thing or a solution, just that it might help some smart person to identify what is going wrong.
Any help out there?
Hi!
i am new here, and i do have a problem.
I have my HTC Diamond since 2 weeks, and it is blocking (freezing) once per day: the device is on standby, i try to turn it on, but nothing happens, always a black screen, not even the restart button works; the only solution is to remove and put back the battery.
the issue is that if someone calls me during this "freeze", he gets that my phone is ringing; but i get nothing; and not even a missed call after i succeed to turn it on.
- ROM version: 1.93.479.3 WWE
i highly appreciate if somone can help me with this problem.
thanks,
Tony
I've had this exact problem, but the reset button on the back does work when this happens. I'm in the US on T-Mobile in NYC using a European Diamond. I work in a building that has very weak T-Mobile coverage and I've found that I only get the problem when I am at work. On the weekends and at night, the problem never happens because I am usually in an area that has either no coverage or good coverage. I have not eliminated the problem, but I have discovered that setting the network type to "GSM" and the band to "UMTS(850+1900)GSM(850+1900)" reduces the incidence of the problem for me to once every few days. I'd love to hear a good solution to the problem as well.
sounds like a problem with the Radio, it could be that the weak signal is causing the phone problems.
Try flashing a newer Radio version, and make sure all the settings (as Drachen said) are correct.
If you arent happy with Flashing a Radio, then send it back and get a repacement (chances are it will have newer firmware)
I have the exact same issue as you have. I had basically tried all sorts of ROMS, be it stock or cooked. It seems that since the upgrade to all v1.93 roms, this problem became more frequent.
Check this link here. I posted some screenshots of my problems there.
http://www.ppcsg.com/index.php?showtopic=102551
I've tried Vic's rom, Swift's roms, stock 1.93 rom with stock spl etc.. all with no success. it would be stable for the first 1-2 days after flashing, but immediately after that, it will happen like twice a day.
Like your case, I'm having this "whitenoise" screen (instead of a blank screen, which i used to have at times also) and I tried calling myself from my land line. I can hear the ringing but my phone does not respond.
So since then, here's my suggestion.
DISABLE your TouchFlo3D. Use default Today screen or SPB Mobile Shell. Thats what I did and I haven encountered a single issue since then for 2 days straight. Try it for a day or two to see.
Base on my analysis, our Diamonds has a defect on the 3D gpu chip. Cos corruption only occurs on programs using the HTC 3D driver (e.g. the OpenGLES api from Koush) while normal 2D functions is perfect.
I am waiting for the next ROM update to see if it fixes the issue before I send in my set for repair before my warranty ends, but I feel its gonna be hard to replicate the issue to the service engineer.
I'm going to wait until the end of the week to declare that the problem has been solved, but I'm having a LOT of luck with the latest radio ROM (v1.00.25.BS14) since it was posted on Fri morning (for me), and have had no freezing problems through the end of Tues. Tony1313, try upgrading to the latest radio ROM on the radio ROM thread in the development forum for a while and see if it helps you. Another set of eyes on the problem would be good.
knave, I don't think the cause of the problem for you is the same as it is for me. I haven't gotten any graphical glitches yet on my Diamond and I've only seen the snow screen you're talking about once when charging overnight (in the 3 months I've had the Diamond). As I mentioned, the crashes only happen in one location (my office) and never happen after-hours, weekends or on vacation. The two things I did to reduce the frequency of problems (that helped) were to change Exchange Activesync from "Automatic" to "Manual" during work hours and to set the bands in the control panel as above. All that makes me believe my problem is radio/reception related.
Drachen said:
I've had this exact problem, but the reset button on the back does work when this happens. I'm in the US on T-Mobile in NYC using a European Diamond. I work in a building that has very weak T-Mobile coverage and I've found that I only get the problem when I am at work. On the weekends and at night, the problem never happens because I am usually in an area that has either no coverage or good coverage. I have not eliminated the problem, but I have discovered that setting the network type to "GSM" and the band to "UMTS(850+1900)GSM(850+1900)" reduces the incidence of the problem for me to once every few days. I'd love to hear a good solution to the problem as well.
Click to expand...
Click to collapse
Hi Drachen I did a similar thing to you except I set it too GSM + AUTO it solved my SOD problems completely. Here is my story.
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2 where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
i have freezes many times each day, even if im using it with no sim card. i don't even know what to do.
i have a stock rom.
I bet you got the 1.93 ROM and not 2.03, go update to it!
My problem is:
when a turn it on, it just show htc background and that's all
who faced with this problem?
Hi,
I recently updated to Froyo using the registry hack, i was on uk orange jf3 before.
Since being on it i have constantly been struggling with the 3g and the network signal, at first i thought the 3g was disconnecting when i turned the wifi on but then the network signal starting disappearing and it would show the circle symbol with the diagonal strike through it to show that it was not picking up any networks.
I read somewhere that cycling flight mode might solve the issue, but for some reason once i turn on/off flight mode it just hangs at that stage and will not change until after a restart.
I have also tried formatting both the internal and ext sd cards and i have done a factory reset twice.
Nothing has helped, it connects to 3g initially (which shows that it shouldn't be a setting problem?) and the network signal is also fine initially but then after a short amount of time or inactivity or switching on wifi the 3g won't connect and the network signal just dies.
If anyone has any ideas as to what is causing this or how to fix it i would really appreciate it.
Having a phone that can't make or receive calls when i need it to is really f'ing me off.
P.s. I have read and searched other topics for help on this but nothing so far has helped.
Might be something like I have? But I got no reply here...
see my post 8601578 (cant publish link here)
lorinthe said:
Might be something like I have? But I got no reply here...
see my post 8601578 (cant publish link here)
Click to expand...
Click to collapse
Yer i read your post, what i don't understand is that it was totally fine in 2.1 and now in 2.2 it's messed up, not sure if that is the same for you?
I think it is something to do with it being for Norwegian users not UK and that somehow affects it.
I have checked the apn and it all seems correct, do you also have the issue with flight mode not working properly?
Just found this on an internet search...
: Samsung Galaxy S v2.2/Froyo update
Posted: 5 days ago in response to: stefan
Some news on the update to Android 2.2 for the Samsung Galaxy S. Currently we are making some changes to get it working better when using Orange signal, and are therefore looking to release the update by the end of November – obviously this is a delay on our original release date but we hope it will be worth the wait!
Kind Regards
Stef
Forum Team
Click to expand...
Click to collapse
Not sure exactly what that means but it sure sounds like this might be the problem i am having.
I would be interested to know if other UK orange users have been having problems?
I would also like to know if it is possible for me to go back to to a previous version so i can actually use my phone.
I am orange uk, and have similar problem at home, but works well at office. Maybe it is due to the barrier of signal. if the signal level is lower than this barrier, only emergency call can be.
I do not know how to do but my friend advised me to update the moderm
So, right now I am using the Axura RC1 CE (I will update later), but I have had the problem described in the topic on various other ROMs using the JK3 modem.
It works fine for a few days (time is random, I have not been able to manually reproduce the issue), then randomly I lose all reception. Switching to flight mode fails, it gives no error, it just does nothing, in the notification bar it just says (searching). I have to reboot the phone to get the phone functioning again.
Anyone else experiencing this on ATTs network, or if there is a fix, I spent the last hour searching and going through the various threads to no avail (or I just suck at searching)..
Did you try the Axura thread?
Sent from my liberated Captivate via XDA App.
I'm having the same issue but I've tried Assonance as well and still get the random no service. Tried different i9000 modems as well--anyone know if its safe to use a captivate modem??? I'm guessing no but just want to know if anyone has tried it without borking the phone.
derek_h77 said:
I'm having the same issue but I've tried Assonance as well and still get the random no service. Tried different i9000 modems as well--anyone know if its safe to use a captivate modem??? I'm guessing no but just want to know if anyone has tried it without borking the phone.
Click to expand...
Click to collapse
I'm having this same issue as well, that's why I've tried to stay away from the UGJK3 modem, however, it's seems every custom ROM is starting to use it
As far as using a captivate modem with an i9000 ROM, I've tried that also, while it didn't totally brick my phone, I did get random FCs. I've read that is a dangerous path to go down.
I feel the same way. I might try the CogKernel and see if that helps...
Please, please, PLEASE do not post these types of things in Development.
Sent from my Captivate.
+1 Lets keep this forum area clean .. its just for development stuff guys.
I have had the same issue with all I9000 modems, the only fix that has worked for me is to enter the service menu and force WCDMA 850 Band only. Also, questions should be posted in the question forum.
[this thread is pretty relevant to development - considering the rom chefs are using this modem in their releases and it has a potential major flaw. if the mods find it better to be in Q&A, then please move it - otherwise, i think the right eyes will see it here]
yes, yes and yes!
ive been posting about it in the perception thread, but no one (save for 1 user) chimed in with the same issue.
we both noticed that we both have an issue where we will bounce from 3G to H and back fairly often. this leads me to believe that it could be part of the problem.
i just odin'ed back to stock because my phone isnt receiving incoming calls now.
what i had planned to do was flash the latest perception but use a different modem... but it seems like the only sensible modem is the JK3 (although there is word on the street a new one just leaked?). so that idea is kind of out.
someone here said they were going to try cogkernel2, but i was on setirons and cogkernel2 and it happened with both. it seems to be a modem issue.
i wanted to lock the phone to use 3G only to see if that would help, but no one shared a way how... but reading this post it seems i can do it from the service menu - though i dont know exactly what to set/change to keep it only on 3G. (any help would be great).
so i believe im going to flash perception 8 and see if i can lock it into 3g mode and go from there. this is getting pretty tiring. im hoping if a new modem releases that will help, but i honestly am not sure i can wait since it is making the phone unusable.
below are my posts from the perception thread on the issue.
--
keener31 said:
i searched but did not find...
i see others have had issues with APN force closing. i do as well, but assuming that isnt a problem, i dont mind.
my issue is that after a certain period of time left asleep, my phone will completely fall off the network. changing flight and data mode dont work, nor help. a restart works. this has started a day or two ago, but was not an issue for the first week (give or take). if it is relevant, my network constantly swaps between H and 3G where i live.
i have not found a setting to force 3g (and disable hsdpa) as i figured it was the network hopping that was doing it. am i just missing that setting? anyone else with this issue? (again, i saw people with the apn force close but not complete loss of network unrelated to initial flash)
also, i think that each build should get its own thread. it is VERY difficult to find accurate information on the current build once a thread has 4 builds and 250 pages in it. even with search, it would still be a good idea.
thanks and thanks.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
keener31 said:
anyone having this issue or have any ideas?
of note: going into wifi settings is also borked. it will eventually time out and FC. i also think that the times my phone has completely lost network and not reconnected have happened more often when charging. but that could be coincidence.
(mobile)
sghi897-perception b.5
Click to expand...
Click to collapse
this continued the same way on perception7 with cogkernel2. no real difference.
Ryukeima said:
I have had the same issue with all I9000 modems, the only fix that has worked for me is to enter the service menu and force WCDMA 850 Band only. Also, questions should be posted in the question forum.
Click to expand...
Click to collapse
in relation to my post below yours, does locking the 850 band only force the phone to use only 3G, or is HSDPA/HSUPA still enabled but you found the 850 band to be more stable.
this is what my next attempt will be to get a solid platform going.
I've tried different modems other than jk3 and it doesn't fix the problem. Stinks that you've used Cogkernel2 and it doesn't help. I also tried the different band selection in service mode and it also hasn't help me (apparently this worked for some people). If you want to give it a shot do the following:
1. Dial *#0011#
2. menu button then soft back key
3. then phone control -> network control -> band selection
4. good luck!
derek_h77 said:
I've tried different modems other than jk3 and it doesn't fix the problem. Stinks that you've used Cogkernel2 and it doesn't help. I also tried the different band selection in service mode and it also hasn't help me (apparently this worked for some people). If you want to give it a shot do the following:
1. Dial *#0011#
2. menu button then soft back key
3. then phone control -> network control -> band selection
4. good luck!
Click to expand...
Click to collapse
ugh. that is disheartening. i will try the band lock, thanks.
can you confirm or deny that when you notice your phone goes completely out of service that it has been hopping between 3G and H? it would be interesting to see if we all have that issue as part of it.
also, fingers crossed for that supposed new modem.
/sigh
Yeah this really sucks because these roms are great with this one very big exception. I haven't noticed the hoping before I need to reboot. I have noticed that if I switch into airplane mode once I drop service I can't turn it off.
I had the same issues with Axura and Percetion. I found that switching my network control to WCDMA 1900 only pretty much fixed it. The only problem I had after was that any time I lost service naturally, ie, bad area, or shielded rooms, whenever I came back into a good service area I could never get a signal again. So I would have to reboot.
In the end, I'm back on Cog, 2.3b7 and no issues for about 14 hours now.
bobbylx said:
I had the same issues with Axura and Percetion. I found that switching my network control to WCDMA 1900 only pretty much fixed it. The only problem I had after was that any time I lost service naturally, ie, bad area, or shielded rooms, whenever I came back into a good service area I could never get a signal again. So I would have to reboot.
In the end, I'm back on Cog, 2.3b7 and no issues for about 14 hours now.
Click to expand...
Click to collapse
gotcha. keep us posted on how that turns out!
glad to hear that that version of cog seems to fix the issue. which version did you get--oc or non-oc?
derek_h77 said:
glad to hear that that version of cog seems to fix the issue. which version did you get--oc or non-oc?
Click to expand...
Click to collapse
I'm using the non oc. I'm not gaming or doing anything too wild with my phone so non is just fine for me.
hmmm, makes me think that's the issue then. most of these roms have kernels that have the oc feature.
hey keener, did you have the oc version of cog?
derek_h77 said:
hey keener, did you have the oc version of cog?
Click to expand...
Click to collapse
sadly ive been running non-OC this whole time, so that doesnt appear to be it :/