Related
I have a PW10B in the US, using a Cingular SIM. In many locations I cannot get a signal at all, and everywhere else I pull a maximum 2 bars. My other phone, a Motorrola RAZR, will pull good signal in the same locations.
I have already upgraded the Radio Stack to 6.24.20 (Complete with the side excursion around the 1% GSM Upgrade failure) with no noticible improvement. I am likely going to try RS 6.25.02. Anyone have any other recommendations to boost the cellular performance of the Wallaby? Maybe a hardware fix on the antenna itself?
Poor reception
I need to find a way to make this better too! I have the same phone and while I seem to get ok reception (sometimes up to 4 bars) in the city, in somewhat remote areas I get no signal at, while my old phone gets 3 bars. I have a PW10B1.
found the RSU updates at the ftp site:
ftp://xda:[email protected]/Wallaby/
Which version is the latest? The A. version or 6.25? Which is most stable?
For all of you getting a 1% error when trying to load any of the 6.24 .25 updates (or others), make sure you put all of the extracted files in the windows directory on your mobile device. Whenever I put them anywhere else I get the 1% error and the program closes. When I put it in the windows dir I get 100% completion with 6.25 and A. versions. Soft reset when update is done to activate phone.
Still testing. I'll get back to you on stability, performance, etc.
Well, here's what I found, so far...
I have now tried 6.24.20, A20.10, and 6.25.02. OF the three, 6.25.02 seemed to pull a slightly better signal that A20.10 (One extra bar at my house). So, I reinstalled that one and will stick with that unless someone can give me a good reason to change to another stack.
Reception has not noticebly improved with any of the RS changes. Also, as you said, if I simply put the Radio Stack files in the /Windows directory and run RSUPDATE.EXE from there, I have no problems changing. The problems happen if I try putting the RSUPDATE.EXE in the /startup directory as well and then performing a warm reboot.
But it hasn't made much difference, if any at all. But strangley enough, changing the ROM back to a PPC 2002 version (3.17.03) DID seem to make a difference. I know it shouldn't, but the phone is pulling 1-2 bars more than it was in a lot of locations and is getting better coverage. The reception is still inferior to my other phone, but it is now *almost* livable...
Unfortunately, I really prefer the feature set on PPC 2003 (Particularly how it handles the GPRS connectivity) so I am going to continue to futz with it. Again I ask, anyone know of a hardware fix to improve reception??
RSU Stack
Agreed. I have now thoroughly tested bot the A20 and 6.25 stacks and the 6.25 stack get's my vote. I haven't gone back to the PPC 2002 ROM yet, but I might try that too. Currently I'm running the XDA-Developers ROM 3.17. I still don't get a signal at my house with anything but the 6.25 RSU stack definately gets a clearer reception, drops less calls, and works better programmatically. With the A20 for example, even when I showed no bars, if I tried to place a call it would all of a sudden show full bars (3 on my PPC) as if I had great reception - but would never make a call. With the A20 I don't know what to believe. With the 6.25 it works better and WYSIWYG.
L8r
So, glad THAT's settled...
So, I haven't found anything for a radio stack better than 6.25 . But I hate hate HATE PPC 2002 when I know the feature set of 2003SE, so, I'm going to go back to that again. I noted that during my 50 mile drive today, the phone STILL lost signal at the same spots it was previously, but would report better signal where it could get signal at all.
And it's not like I am out in the sticks, we are talking right neat the Nashville airport and down the interstate corridor.
So, at the end of the day, It looks like I will likely just be going back to the RAZR, and saving my pennies for a Himilaya or Wizard....
SO, although this is the Wallaby forum, anyone know if the antenna is any better on the later devices as compared to the Wallaby??
Here in Argentina my PW10B1 Wallaby has poor reception too. I don't get a signal while my friends' cellphones get a strong signal with no hassles. This does not happen in urban areas, only in the road. I think the Wallaby's radio hardware is poor, or the antenna design maybe is bad.
That's a great question lynrd... do newer models have the same poor signal problem???
I think that is a problem of antenna design...
I have problems with signal reception in many places.Most of them happens randomly...
The same problem I mechanically fixed this problem, and it gave me a positive result. The problem is with antenna. 8)
zilant said:
The same problem I mechanically fixed this problem, and it gave me a positive result. The problem is with antenna. 8)
Click to expand...
Click to collapse
Do you have more info about what you did?
What about this?
I found this little circuit that supposose to go behind the battery and improbes the anthena range, anyone knows if it thuth?
http://www.deremate.com.ar/accdb/viewItem.asp?IDI=9968882
Hi gents,
I'm here in Vietnam and have used my XDA 1 for a long time. At first, I also faced the poor signal reception prolem but since I upgraded ROM and Radio stack, it seemed to be ok. Now I'm using Rom ver : 4.01.16 ENG/Radio ver: 4.21.00. Let's try it !
P/S: The Rom ver 4.01.16 along with Radio ver 6.25 but my advise is that you insert Program B (include 4.21.00) into Program A (4.01.16) before upgrade. Good luck ! If there's any problem, pls send and YM: gooseberry_hn
I'm still seraching a hardware solution
At the time of the "shame" (went to a beach trip with my friends, and I lost the signal all day until I hit the road back), I was using stack version 6.02, now I'm using version 6.25.20, untill now I have experience no diferences in reception, I feel tempted to buy the cirkuit to improbe reception (just U4s 2) , but it must go behind the batery, so I must disasemble the Wallaby, anyone has experience doing that?, is it easy to do?
Yes, I have a circuit for you <Note that the instruction in Vietnamese>
Hey folks. I had a quick question if someone'd be so kind to oblige. I have a siemens sx-56, and i just upgraded to the special edition rom from this website. This phone was originally for AT&T and the only carrier supported by this rom was the TMobile. I have a cingular sim card. As of right now, i've unlocked the sim on the phone, but I'm not picking up any phone signal. Is there a way for me to use this on the cingular network? Will I have to upgrade my rom to the newest one that's running WM2003? Props to the developers of the special edition rom. I love all the software that it comes with. Thank you, and have a good one.
I have ROM 4.02.04 and rsu A20. If I want to install/try 6.25 do I (1) connect my PPC to my desk top via USB, (2) activate/connect Activesync, then (3) simply download 6.25?
RSU Update
Yes, download all files and copy them to your Windows folder on the pocket PC, ensure that the machinne is craddled so power supply wont be an issue, then explore the windows dir in the pocket using Commander CE or whatever you have and run the EXE file to begin updating, do not place anything in the starup folder.
Thanks. I'd like to to all that, but:
1. I can't find the windows folder on my Pocket PC. (I can find the windows folder on my desktop.)
2. If I can't find the windows folder in the Pocket PC, I can't explore the Windows dir in the Pocket PC.
3. I don't have Commander CE, but do have 'File Explorer'.
Sorry I am not very good at this, but I am trying and really appreciate you help and patience.
By the way, I am running WM2003 and Rom 4.02.04. Is there any advantage to (a) going back to WM2002 with XDA 1.2 or (2) upgrading further to WM2003SE?
Skip
Find the Folder
You can find the Windows folder with File Explorer, you have to select My Device in the upside bar of the Explorer, then the Windows folder will apear in the bottom.
Sticking with a 2002 version will prevent you from running a lot of programs designed for the PPC2003, one of them, MS Voice Command is one that make's the diference between this machinne and a normal celular phone (you can control the entire unit using your voice, not just make calls). This program will eat most of you 32MB of RAM, so you gonna have to install everything in a SD card, and you'll have to make a backup copy of that storage card, becouse the unit tends, from time to time, to delete the SD card (specially after a RSU update!).
If you want to go to the 2002 version and then to the 4.01.16 or somefhing like that, some people wrote that going that way you avoid errors in the flashing process, my advice?, update the RSU if you have a minor version than the 6.x, otherwise, its asking for trouble.
If you ever update a computer BIOS using the disquette process then go ahead, otherwise... good luck man.
OK, thanks. I found the folder and the exe. I think I'm ready to give it a try.
Looks like I'm ok with 2003 for now as it has some features I like. I'll keep your instructions in case I decide to try MS Voice Command.
Again, appreciate your help. Skip
6.25 loaded fine and is working. However, I see very little improvement in signal strength. Side by side with my wife's Samsung, she gets a steady 4-5 bars while I get 0 to, at most, 2.bars.
I assume the real problem is the Wallaby antenna design. Does anyone have any mods that improve antenna sensitivity?
I am a complete novice when it comes to upgrading, radio roms and os roms..
Anyway, I have been playing around with my Vario II trying different Roms and Radio Roms:
I currently have:
Herm300
ROM Version : 2.025.255.1
Radio Version :1.27.00.00
Protocol Version : 32.60.7020.06H
Anyway, back to the point of this thread.
As I said I have been playing around with all the things you guys have been posting. I reinstalled TOMTOM today.
After about 10 secs, it changes from NO GPS device to Connecting to GPS Device, this is with no external gps being paired.
Then when you go into the menu, it now says no valid gps signal, instead of NO GPS Device.
I have posted this thread in this forum as I know you guys are working hard on the GPS possibilities.
Sorry if Connecting to GPS device and no valid gps signal, doesn't actually mean anything.. I though it was just worth sharing... As before my Vario II never used to say this.
It's probably a TomTom software bug. Your radio version doesn't support GPS, so it shouldn't be possible to even see it. Another possibility is that whatever COM port that software uses isn't being closed properly for some reason, so the software thinks there's something there when it's actually not there.
Hi all , just got an Ameo (U.K T-Mobile version) and upgraded to Windows Mobile 6 Professional CE OS 5.2.1620 (Build 18125.0.4.2) official rom.
Everything works fine except GPS signal that really sucks!! I have red all topics carefully and i have set all parameters right such as COM 5 and baud 9600 but with Destinator 7 it does not fix satellite signal! It gets one satellite on cold start after 3-5 minutes and maybe some 2nd or 3rd but really UNSTABLE...so it loses fix and again from start.. Navigation is almost impossible!
Any suggestions please?Does someone else have the same problem maybe?..Or my device is faulty?Is it possible that Destinator 7 does not work fine with the built in GPS?I have tried external bluetooth gps on other port and baud and it goes fine!!6 satellites minimum 8-9 maximum and fast fix even on cold start.Is it possible that my ROM version is problematic?
ROM Version: 2.35.110.4
ROM Date : 10/09/07
Radio Version: 1.50.00.00
Protocol version: 32.83.7020.20H
I can never get a fix when it's in the faux-leather case, if that's any help... usually get a fix within 30s out of the case.
davemee said:
I can never get a fix when it's in the faux-leather case, if that's any help... usually get a fix within 30s out of the case.
Click to expand...
Click to collapse
agreed, i get better results though in faux leather case, but my primary case is a n aluminum case hahaha so i know my own problem. temp resolve was an external recvr
hahaha
Have you tried the reg change to enable GPS in Camera mode (to allow location metadata to be stored within the picture)? I find if the GPS is ever slow to start up, using this first of all to get a location seems to kick things into life. Also make sure your QuickGPS file is upto date.
For some reason mine is now getting a lock much quicker than ever it has been before. I normally start TT just before I set off and previously it was taking approximatly a mile of driving before getting a lock. Now, it only takes about 1/2 a mile - have the US done something to the signal, or has my Ameo now developed supercow powers?
I'm running the cooked rom v3, radio 1.5 and its in the leather wallet.
Crumbs - half a mile? I usually start CoPilot when i get in the car and by the time I've started moving i have a fix - I take it out f the case to put in my Brodit mount but even in the house in the case it doesn't take that long to get a fix!
It is TomTom !!!
giorgosp: Yes, I can conform the problem and it's driving me mad!
Flashed to the T-Mo ROM this week, as PK3 was giving problems connecting to WMDC (tried a hard reset initially, and no better )
The T-Mo ROM is good, and allows WMDC to connect well, but since flashing, I've been unable to obtain a valid GPS lock. Tried with GPSInfo and iGO2006. I get a couple of small bars, and nothing more. Today, I drove for 45minutes, and no lock at all. My Orbit2 sitting on the car seat with CPL got a lock in 20 seconds from cold.
Previously, I could get a lock within 2 minutes if stationary, and about 10 minutes if moving (I live in a region with lots of windy country lanes, so rarely see the same bit of sy for more than a few seconds!), so this does seem to be an issue with the T-Mo radio.
..and further to the above, I've just downgraded the Radio to V1.47 (which means hard reset), and taken both the Orbit 2 and the Ameo outside- Orbit2 got a full fix in 30 seconds, and Ameo 30 seconds later (so 1min TTFF from cold, which is the best I've yet seen!)
Don't know if going back to radio 1.50 will keep the improvement, but I'm tempted to keep it as it is
im running 1.50 in a pawell rom and it's all good !! I think T-mo have messed things up !
So NeilM do you suggest me to downgrade radio version to 1.47?how many satellites is reaching to fix? ..to get a valid signal i think at least 4 and stable,right?
To all of you using other than the official t-mobile 2.35 rom with radio 1.50: how many sat signals do you achieve to fix using athena with the leather case under normal condition? does the radio version impact on gps signal so much?
I tried reverting to radio V1.50 and same problem, so at least in my Ameo there is a problem with the new T-Mo ROM, Radio 1.50 and the GPS receiver.
Went back to 1.47, and this morning got a cold TTFF in 1 minute.
You need 3 satelites for a 2D fix- locates at ground level, and 4 for a 3D fix, which includes altitude.
From a cold boot, the 1st sat signal takes a while, but it then provides almanac info for any other in its vicinity. As the reciver gets more almanac info it builds a picture of the sky, then the ephemeral data is downloaded.
Once almanac info is obtained, you will see the short bars in GPS apps; once ephemeris is obtained the bars turn dark, or change colour and when you have 3 of those, navigation can commence.
I can't advise you to change the radio version, especially as it needs a hard reset, but can only repeat that it worked for me, here in East Anglia, using the Ameo on Orange.
Neilm,when reverted to radio 1.50 have you used the t-mobile rom or have you used only the radio cab provided by forum?even if my question seems silly i was thinking that maybe a file of those included in t-mobiles 2.35 rom radio 1.50 is problematic??so have you flashed only the radio version back to 1.50 or the entire rom (including t-mob radio 1.50)?
So you suggest change to 1.47?i understand that hard reset is unpleasant setup from beginning but having a dead gps after paying so much for this device is worse.. Could some expert please find this issue..?
..guys i live in rome and i tried everything..it gets 1 sat fix after 3 minutes and upon gets a second one it looses both of them..my ameo is like without gps.. only when i use an external bt i-blue i can use it.. but i bought this mobile for not carrying 200 things with me.. :-(
I used the Radio only link, not the whoe T-Mo ROM, so it seems, for me at least, that it is the radio version, rather than where it comes from.
If you don't mind doing a hard rest, I'd say try it I can't say it will work, because it seems there are a number of factors which I don't understand. Some users have GPS working OK with this ROM and radio 1.50.
My personal experience is that radio 1.47 works much better for me, both for GPS and WiFi, and the phone reception is no worse. Battery use seems about the same.
Are you in Rome city centre? If so, have you tried going to a more open space to get a 1st fix? High density buildings can give a poor view of the sky, and give some 'multipath' interference, which can prevent a proper fix.
Athena GPS Quickconnect can't find anything else vaguely apprnnect
Firstly, sorry to hijack this thread, but I couldn't find anything else appropriate.
Relevant to this thread: I have no problems with my current hard/firm/software combo and GPS connect time. It is about 2-3 mins without a current quickconnect file, but fine with both TomTom 6 and VisualGPSce.
Does anyone know what the antenna hardware is like for the GPS radio in Athena? Is it inbuilt to the semiconductor hardware or is there something else? If there is a physical antenna it could be broken? Try attaching an external bluetooth/USB receiver or external antenna. If one works it can only be the antenna or the GPS hardware at fault, right?
My problem
GPS quick connect will no longer connect through 802.11 wifi, bluetooth activesync or USB activesync. The only thing to have changed is that I briefly enabled and then disabled GPRS wifi. Although the settings for GPRS/WAP have been disabled and in network settings the option for 'programs that use the internet automatically' is set to 'my work network', GPSquickconnect still seems to be using my GPRS service provider (which cannot be deleted).
I know a hard reset will resolve this but it would be nice to know if anyone else has come across this and found a reg tweak to remove the service providers in the drop down connections list.
Thanks is advance.
Hi there.I've been using my 6815 for over a year now and was enjoying it till something happened to the wifi.I've used dozens of different firmwares on my phone and not once have this kind of problem before.Basically my wifi is not usable in any of the firmwares for sometime now.I2ve tried original 5.0 than 6.0 several 6.1 s and several 6.5s.I cant even enable wifi in any of the firmwares.For example right now I am using a clean 6.5 rom, and in Hp Asset Viewer it says for wifi :
driver rev:N/A
firmware rev:n/A
Hardware rev:1.0
ip address : n/a
mac adress : n/a
radio preset : yes
In some custom firmwares there are different wireless connection managers and I cant enable wifi in any these managers too.I tried changing things in registiry as suggested to someone like me but it didnt make a difference either.
so... Any suggestions ?
I have problem like this with wi-fi. Can anybody tell us a solution?
wifi module gone, its faulty on board, no solution. happens on atom series.
atom manufacturer quanta uses cheap conponent to build this device.
common fault on atom/hp68xx series
lcd-cannot see by side view, lcd will appear jumping under sunlight, newton ring appear easily
earpiece jack-on board, always get faulty when user plugin and unplug from it, device will think earpiece is still ard and do not project sound out from normal front speaker.
usb-detach from board easily when user drop the device while charging.
wifi-wifi cannot be on, system thinks wifi module is not ready or unavailable.
Tabbe said:
wifi module gone, its faulty on board, no solution. happens on atom series.
atom manufacturer quanta uses cheap conponent to build this device.
common fault on atom/hp68xx series
lcd-cannot see by side view, lcd will appear jumping under sunlight, newton ring appear easily
earpiece jack-on board, always get faulty when user plugin and unplug from it, device will think earpiece is still ard and do not project sound out from normal front speaker.
usb-detach from board easily when user drop the device while charging.
wifi-wifi cannot be on, system thinks wifi module is not ready or unavailable.
Click to expand...
Click to collapse
yes I confirm that probably wifi module is dead or broken..
My first rw6815 work for 2 weeks and after that suddenly GSM modul disappear... I have good working PDA not phone anymore...when i sent it for warranty..they replace for me the whole phone ...
Hello to you all,
I've a problem with my HD2 with cht2 custom rom.
The bluetooth is working well but for like 25cm only.
I search on treads on this forum an Tweakers ans on google.
But i couldn't find a solution for 5 day's already.
Maybe one of you is common with the issue.
Is there a soul out there that can help me please?
Kind regards,
SvdBent
I have the same exact problem, but different phone, rom and headset.
It seems intermittent, some times I connect my bluetooth and it works fine, other times I connect and it sounds like a bad stereo connection with static unless I have the phone right right next to the headset, and if it is too far away (~ five feet) it will not even connect.
No other bluetooth devices around but my laptop which has the bluetooth disabled usually, and I can turn my laptop's bluetooth on and test the headset on Skype with no problem - so it has to be the phone.
A side note, I also can not hear the person on the phone if someone calls and it is connected to the PC, but that might be a completely separate problem - and this is also why I turn the bluetooth off on my laptop.
Phone: AT&T Tilt (aka Kaiser, TyTN2)
ROM: WM6.5 HyperDragon IV Mega WWE (10/30/09)
Radio: 1.65.24.36
Headset: Plantronics Voyager 510
Any ideas?
EDIT:
And of course the search is broken ("Sorry, search is temporarily unavailable. Please try again in 20-30 minutes."), so I can't search the ROM thread for the problem, and Google was no help, seems this is a rare problem.
EDIT 2:
And now it works fine again...only thing that changed was my battery died from tethering. Could it be Wireless interfering with Bluetooth.....one sec...
OMG, I can't believe I never put figured this out! IT WAS THE WIFI!!! Have had this phone for two years, dont remember when I first noticed it, as they say, I never put two and two together - I never realized it only happened when I was using the Wifi. What causes this and how can it be fixed??