yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] Winshit:
i'm not shure if its the radio rom

Hi at all.

Yesterday I tried to get it back running. And something what i noticed was:

I did the Unlocking process, and after this procedure my reception went bad. So, I'm not shure if its caused by the radio roms.Afterwards I flashed the rom, with bepe's 0.67 premium. The reception didn't went better.

Afterwards i changed the radio to the 1.64.08.21. The reception was still the same poor quality. So I flashed back to the original rom. Still the same s***!

So I decided to install the 1.64.08.21 again and reflash the bepe rom.

And, it was better. (I had no reception before, now i got 2 bars. Its still not as good as original but, better :)

Currently I am at work, an usually i got recipience here. Currently I dont have some. So, its not good enough for me, and i am going to send it in.

greets
[Touch Cruise ROM Development] mavvy4ever:
I also have the feeling and afaik my reception problems occured after the hardspl flash...
[Touch Cruise ROM Development] m3uch4:
Just to add my 0,02 : did the HardSPL, then SIM Unlocked the device, then replaced the french SFR ROM with the original HTC rom, and my reception is still perfect (3-4 bars most of the time, 1-2 bars in the underground public transportation)
[Touch Cruise ROM Development] jirisrba:
I went thru the history of flashing and I suspect the Polaris SIM Unlocker

http://xdaforums.com/showthread.php?t=375338

the second step with "unlock radio" with the reception issue. Every step I reverted back (radio, rom, erase partition...) don't help to resolve this issue. Actually I dont have any idea how to revert back the step "unlock radio". Can you point me how to do that ?
[Touch Cruise ROM Development] zoopido:
Under my experience, I did not notice any loss of reception after hardspl, it was only after flashing to the latest radio.
[Touch Cruise ROM Development] Rroet:
It's definetly the radio rom. Cause that's the only thing that directly interfaces with the radio hardware.

I've upgraded my SPL and OS rom today (NO F***** way I'll touch my radio again) and it all went ok!

Besides everything, I've had a look at the tests the kaiser people did on the different radio roms and it seems that the 1.58.21.23 rom I have by standard now is one of the best. Definetly not going to touch it for now.

All working perfectly.. AND as the cherry on the cream:

I was in the top story of my 2 story building today, I had 2 satelites reception on the GPS? Indoors reception of GPS!
[Touch Cruise ROM Development] Rroet:
That's what I did with the first polaris, didn't have issues there. (And it didn't unlock the polaris, because it's sold as a unlocked device)...

That's what I did with the second polaris, broke the device.

Didn't do it to my polaris I have right now. That one is working perfectly and like mentioned before, it's already unlocked. I just used Hard-SPL of Olipro and upgraded the OS rom afterwards.
[Touch Cruise ROM Development] Anolnx:
Oh my, I feel lucky...

I got my SFR/Vodafone branded Polaris and I:

- flashed the original HTC UK Rom to fire the red boot screen,

- flashed the original HTC FR Rom (1.25.406.1 FRE),

- flashed the radio (1.64.08.21),

- unsimlocked the device,

and still, no problems... 2 bars inside my house, 4 bars outside. And no, I don't live a meter away from an SFR antenna ;)

Well, I hope we'll find a solution for the people out there that don't have this luck...
[Touch Cruise ROM Development] vdavide:
yes i'm one of the lucky here but i hope for a solution for all because i will not flash anything for now since the problem will be solved .

I think the problem isn' t hardware related , flashing something doesn't broke anything . I think there must be a 'software solution'...
[Touch Cruise ROM Development] mavvy4ever:
Oh yeah, I remember now that I did it too! SIM Unlocker. Between the Hard-SPL and OS. That's more plausible...

Everybody who has this issue: did you do the SIM Unlocker? And if so... is there a solution to revert this back? Could be worth a try...
[Touch Cruise ROM Development] QAN:
Yes I did the unlock too. Shame I did not read the forum first. I have actually seen with my own eyes that after the unlock the reception went bad. When using the unlocker the device is resetting after every phase. And after step two the reception went bad. So I think the patched radio did something more as it shoot have.
[Touch Cruise ROM Development] bob2k4:
I didn't do the unlocker, yet I still developed the problems.
[Touch Cruise ROM Development] fab35:
Here is my experience:

* French SFR Touch Cruise (locked SFR ROM)

Next steps:

* Hard-SPL + Unlock OliPro

* HTC original ROM

* BePe's ROM 0.5x

* Radio ROM 1.64...

* Bepe's ROM 0.67 WWE

=> still seems OK for 3G/HSDPA reception, 2 bars in, 4 bars outside...

I'll test visio and high datarate transfers to confirm.

Concerning BT, not tested yet.

WiFi OK.

FM OK.

GPS OK.

But battery power seems to decrease quicker!

Could we centralize information on "what should be avoided" in ROM's updates (perhaps depending on operator, mobile...) ?
[Touch Cruise ROM Development] Sunbuzz:
If soo, is there a way to compare the nvram from an effected phone, with an unaffected one?
[Touch Cruise ROM Development] jltricot:
Hi !

I think i have a problem with my cruise but i don't know if the trouble come from my operator (SFR) or my cruise. From my work, everything is OK : signal max. From Home, i have a bad reception and ALL incoming call are lost :-(

if i change the phone parameters (i change the type of networks from Auto to GSM) then i can receive incoming calls ...
[Touch Cruise ROM Development] nico1885:
change network from auto to gsm

if i change the phone parameters (i change the type of networks from Auto to GSM) then i can receive incoming calls ...

This was good idea, i did the same settings as you, and i had full signal on GSM

Nico
[Touch Cruise ROM Development] blackbird26:
For me that switching from Auto to GSM won't work either. By the way, if it would work, it's still not really a solution.

I have tried many roms and radio roms now, but nothing works compared to what it was. In some cases I have reception, but it doesn't look like the reception I have had, before I performed the hard spl. I am thinking about sending the device in and let it replaced.

If anyone knows a solution, share it with everyone...
[Touch Cruise ROM Development] jltricot:
Switch from auto to GSM let me receive calls BUT not H when i go Internet only G.

I don't understand beacause i have this problem for 3 days. Before my cruise was OK.

I hope someone could finely help us !!!

thanks
[Touch Cruise ROM Development] vdavide:
You can find more info about reading NV items in this thread :

http://wiki.xda-developers.com/index.php?pagename=HTC_Wings

and here too:

http://xdaforums.com/showpost.php?p=1860063&postcount=30

This work on wings ( HTC S730) wich is based on same chipset of polaris ... if someone will give a try...
[Touch Cruise ROM Development] Sunbuzz:
OK, I will try this on my polaris (which is affected and has BAD reception) and post the results... if someone could do the same on unaffected one it would be great!
[Touch Cruise ROM Development] Rroet:
We're making progress, lovely.

Time to wake up the devs and direct them into this thread and hope they'll do something with this usefull information.
[Touch Cruise ROM Development] vdavide:
Note that this functionality is based on Hard-SPL . I think polaris hard-spl is differ from wings hard-spl so it may not work ... these are deep-hardware info so be carefull at what u are doing...
[Touch Cruise ROM Development] kutonglupa:
It looks like this issue affects only those who flashed Radio 1.68.08.21 and not to those who flashed Hard SPL and SIM Unlock but retain their radio ROM.

Sequence;

...Flashed Hard SPL

...Flashed SIM Unlock

...Flashed cooked ROM

.....Everything's fine.

...Flashed Radio 1.68.08.21

.....Still, everything's fine:)

...Re-Flashed another cooked ROM

.....Problem Starts :o

...Re-Flashed Radio to Original

.....Problems remains.:(

...Re-Flashed ROM to original,

.....Problems remains.:mad:

Verdict: Radio 1.68.08.21 seems good only at first install. The moment you flashed another ROM, then, say goodbye to your BT, Camera, Reception etc.,

Noob's, Dummie's, newbie's(Like me) beware the urge to take the plunge. Other's maybe getting "Cream a la Cream" result with radio 1.68.08.21 but, that does'nt mean, you too, will.

Sidenote: It could be possible that the HTC Camera Patch corrupts the radio.
[Touch Cruise ROM Development] aCarrot:
I have totally the same problem with you!!!!

I have polaris and Radio 1.64.08.21 protocol 25.74.40.02W

I use swtos all included rom and pleased this rom.

Thanks for your share.
[Touch Cruise ROM Development] scripttec:
i'm having the same problem here...

flashed from "original" GER to new radio and WWE and then everything began

currently i doesn't even get a signal :(

having now also the latest radio 1.64.08.21 installed on WM6.1

my next problem is, that WiFi is also not working (which actually never did)

some help available??
[Touch Cruise ROM Development] vdavide:
NV items

Here NV items from my working ( not affected by radio problems ) polaris ,

POLA100 , radio 1.64.08.21 , OS WM6.1 ( not important , i think ... )

Start share pls so we can see if NV is related to the problem or not ...
[Touch Cruise ROM Development] FlaTEriC18041983:
I have Pola100:

after 2 months on stock Radio and ROM I first Hard-SPL'd (v2.2), then first changed to Radio 1.64.08.21, after few days I changed ROM to "swtos WM6.1 OS5.2.19209 all HTC-apps included ROM"...

I think that nothing has changed: my reception on GSM only is good (3-4), on 3G (1-2), Wi-Fi is always good, BT (can't tell, never used it), camera works as poorely as before...

still thing is during calls, I often have cut-offs, I don't really know if this was the same before?!

A thing I don't understand is, how can a same device be affected differently?
[Touch Cruise ROM Development] emarati:
bluetooth fix

Just install this cab file and hope it will solve the problem,,,it solved mine--If it solve the problem please update us...
[Touch Cruise ROM Development] kutonglupa:
First post and you already got a cab. Where did you got this?
[Touch Cruise ROM Development] scripttec:
well, another day passed...

it looks like that maybe the power for the signal of the device is too low!

when i'm outside and in the near of a station, i'm having a (good) signal.

indoors is nothing

i think i'm going to return my cruise on monday...

anyone knows if there could be a problem because of the flashing when returning to shop/service center???
[Touch Cruise ROM Development] kutonglupa:
Look at your manual. Tampering with the software that come's with your device void your warranty.:D
[Touch Cruise ROM Development] scripttec:
this sounds like a problem for me... :(
[Touch Cruise ROM Development] kutonglupa:
Flash back to your Original ROM and then take a look at this thread http://xdaforums.com/showpost.php?p=2075574&postcount=2 :p
[Touch Cruise ROM Development] scripttec:
thanks for the advice, was already thinking about it...

now i only have to find a similar ROM :D
[Touch Cruise ROM Development] rxdoctor:
same problem here

not sure when it happened because I upgraded to bepe .67 basic first and had problems first hour with so many other issues so i tried swtos and it worked for a few extra hours enough time to figure our reception sucks not cant even connect in house - prior had 4 bars...I now went back to stable htc rom and still having the same issues - I get 1 to 2 bars where I used to have 4 bars by my window....LOL - price u pay for being on the forefront of technology :(
[Touch Cruise ROM Development] rxdoctor:
connection wizard cab

did any of you use the connection setting wizard cab from swtos skinny page? I thought this is where my problems started...I could not even connect to cell service until i installed this cab - then I noticed reception sucked big donkey c__k.
[Touch Cruise ROM Development] emarati:
I got it from another forum and tried it and it solved my problem,,thats why i wanted to share it
[Touch Cruise ROM Development] rxdoctor:
poll admin

you need to expand you votes...i have read a few who have had problems with a specific rom. We need to pinpoint the cause. Others like myself have tried several roms prior to recocnizing the problem...
[Touch Cruise ROM Development] rxdoctor:
been there done that

I have redone all my steps reinstilling bepe .67 basic where now i think the problem occured and then swtos .93 ultra light then i reinstalled htc official rom and hard-spl 1.25 still have no reception where i used to get 3-4 bars...in the best area in downtown big city I do get 1 or 2 bars where it used to be 4 bars all the time - even in buildings....now if i go inside a building service drops - man this is frustrating...im sending in my phone....cant do this anymore....looks like no solution. others who installed bepe are having same problem and are sending in their phones....
[Touch Cruise ROM Development] blackbird26:
Exactly.. That's what I did today.. Sending my phone in and let HTC fix the problem. In my opinion there is absolutely no solution at the moment if these things as you quote sound familiar to you..
[Touch Cruise ROM Development] mavvy4ever:
I have at least a possible idea why so many people have problems with UMTS(3G) reception and many people don't. I tried 4 different sim cards A, B, C and D where A, B and D are from provider 1, and C is provider 2.

When I first updated my rom and radio I had to face the problems.

Scenario 1: using sim card A (AFAIK one of the first UMTS cards which the provider provided to their customers) -> after entering the PIN, phone is searching, finds UMTS, gets 4 bars signal strength, suddenly reception falls down to 0 bars with a "!" and the signal is lost... not even an automatic retry to connect to GSM.

Scenario 2: using sim card B (from a second contract with the same provider that I made some months later) -> nearly the same: entering PIN, phone finds UMTS, gets 4 bars, suddenly 0 bars with "!" but 2 or 3 seconds later it reconnects using GSM.

Scenario 3: using sim card C (a different provider where I use a UMTS flatrate) -> entering PIN, phone searches and gets a UMTS signal, it can connect but only with 1 bar. After some time signal strength fluctuates between 1 and 3 bars, and sometimes 4 bars at my office.

And now...

Scenario 4: reporting that problem to the customer service of provider 1 they said it could be a sim card issue, so they send me a new one (card D) for replacement of my simcard A.

Some days later I received the new sim card. The chip on the simcard D looks a bit different (see picture in attachment).

This simcard D gets a UMTS connection with 2-3 bars inside my apartment and 4 bars outside.

So... I assume, reception strength depends also a lot on the simcard technology and maybe some people have a state-of-the-art simcard and don't even notice that the reception of their Orbit2/TC is suffering??? And some do notice the problem, because they have an old card???

Maybe some with these problems could ask for a new simcard and maybe they will notice an improvement on their Orbit2... just an idea...
[Touch Cruise ROM Development] NikMel:
I have my SIM for more then 4 years and I must say this card works great on 3G/UMTS network.

I think it's some how a network or radio problem?!?!?!:confused:
[Touch Cruise ROM Development] rxdoctor:
thanks for y effort but.....doesnt solve my problem

My phone had 4 bars all the time in my house prior to upgrading rom - now it has a problem searching for reception and if I get one bar i am very lucky. I just think the new radio rom may have strained hardware and now it is damaged or new radio rom gave me worse reception and even when I reverse to official htc radio rom it is not reseting the radio....in device settings it is exactly the way it came in the box and exactly the way it was when it got 4 bars all the time in my home even spl 1.25 but some how it may be still on the upgraded rom....due to it not reseting??? does this make sense or is it possible? I even tried switching to radio 1.79olinex which is suppose to be a big improvement in reception cell and gps and lower battery usage....that i do not understand....they are trying to save battery but you must decrease signal strength to do that....is there some other setting that I am missing because I would be willing to loose a lot of battery life to increase my reception a little bit...911 help plz...
[Touch Cruise ROM Development] :
Welcome to the club !!!

Hello,

I've just received my Cruise few days ago and I decided to upgrade my ROM (0,67 bepe Fr + Radio 1.64.08.21).

Before maade this upgrade I tried to read all the post but I didn't find this post (problem reception), what's pitty becouse now, I have exactly the same problem !!!

Do you think than thre is a solution ?
[Touch Cruise ROM Development] d_dreamer:
Same here. I tried all radio, four different roms & flashed one official rom with radio, three different sim cards with two diffrent phone providers but still no luck :(
[Touch Cruise ROM Development] :
I'm not a specialist but I can't imagine that these differents upgrades damaged the hardware !!!! May be, there is a One Time Programming component in the HTC cruise but if this one is damaged, it should be impossible to connect the GSM network !!!!

I tried few times to dowgrade the ROMs (radio + original ROM) and nothing better. I think I will put the old SPL and send the Cruise to the Aftersales !!!!

I haven't got other solution.
[Touch Cruise ROM Development] vdavide:
i posted my idea about this problem ( try search in this thread ) but seem no one interested to try ... i have NV items from my polaris that has currently no problem for me using radio 1.64.

I think that my NVitems can be restored to a fault device ( it's only an idea , don't know if really possible ) to see if it restart work.

vdavide
[Touch Cruise ROM Development] rxdoctor:
I dont understand

What is it - I will try it! NVitems how and what do I do?
[Touch Cruise ROM Development] vdavide:
see posts 52 57 64 ...

search for qpst 2.7 build 215 or more on this forum, u can read your nv items that can be compared with a working polaris...then we will see
[Touch Cruise ROM Development] rxdoctor:
post the working nv items pls

will QPST 2.7.247 work or do i need build 215? anyways I will give it a shot - need someone to do to working polaris to compare....
[Touch Cruise ROM Development] olotam:
RXDoctor, the working nv items are on the #64 post, on page 7.
[Touch Cruise ROM Development] d_dreamer:
Hi,

Using mtty and set the command "rtash c" I got these msg:

Cmd>rtask c
Calibration

Card inserted

Cmd5 CMD_TIMEOUT
SD 2.0 HC card
SD Init OK

SDFATChkConf: RhOpenFile() failed POLACONF.txt
HTC_SMEM_CE_RADIO_DBG_FLAG:300

Enter Radio Image

Then I exit mtt and ran "QPST Configuration". For two seconds A phone named "em6700" or something appeared but dissapeared quickly. After that there's no phone detected or connected.

Any ideas?
[Touch Cruise ROM Development] d_dreamer:
Here's my NV item. I have little or no knowledge of this file. I just follow some instructions in this forum.

http://www.bhtholdings.com/nv/dreamer_qcn.zip
[Touch Cruise ROM Development] d_dreamer:
Now can I applied vdavide file into my phone? If yes how?

BTW, I tried build 215 on two computers and has no luck. Build 247 worked fine on my third computer.

I also bought my TC from HK.
[Touch Cruise ROM Development] arvind09:
Radio problem

Ok so i was in the same fix as everyone,flashed bepe's .67 basic rom and then flashed the 1.64.80.21 radio and then no receception,tried flashing different radios but again the same problem,flashed the orignal stock rom but again no signal(showed no service)then after flashinng the stock rom restored the orignal ipl and AFTER that hard reset the phone and guess what all four bars of signal back again and the phone is working without a problem,guess i was lucky,but if this helps someone then all the best.
[Touch Cruise ROM Development] mavvy4ever:
Hi, I know all the files are on this forum, but can you please provide us with the exact files (rom/ipl) that u were using? i am curious which stock rom u used.
[Touch Cruise ROM Development] arvind09:
I used this stock rom RUU_Polaris_HTC_WWE_1.25.405.1_radio_sign_25.65.30.04_1.58.21.23_Ship and not once but twice just to be sure that it was'nt a fluke chance the first time and the result was the same,ie the phone is working perfectly.
[Touch Cruise ROM Development] mavvy4ever:
cool, this is what I just downloaded and flashed once... now doing it a second time... but how did u restore ipl? or do u mean spl (originalspl.zip)?
[Touch Cruise ROM Development] arvind09:
Oops sorry mistype yes meant the spl orignal,now starting the unlocking process all over again to see what happens now.
[Touch Cruise ROM Development] d_dreamer:
Flashed using RUU_Polaris_HTC_WWE_1.25.405.1_radio_sign_25.65.30.04_1.58.21.23_Ship.exe. Applied originalspl.zip. Hard reset. As much as I want it to work but I tried twice with no results.:(
[Touch Cruise ROM Development] :
Is this ROM (RUU_Polaris_HTC_WWE_1.25.405.1_radio_sign_25.65.30 .04_1.58.21.23_Ship.exe) a multi-language ROM ? I'm looking for the original French ROM for the Cruise but I don't know where I can find it.

Anyboby is able to help me ? If I have the good original French ROM, I going to try these actions :

Original SPL (POLA100 as written behind my battery).

Original French ROM.

Original ROM Radio.

Hard reset.
[Touch Cruise ROM Development] rxdoctor:
I tried this 3 times and did not work

if you meant spl yes I put back spl did ship flash and still same problems....this is not a fix you must have done something else...but I am interested. Maybe you dropped your phone too :) or went through airport security xrays lol....this problem is so ****ing funny I wish someone who really knows the hardware of the radio or antenna would help us out!!!
[Touch Cruise ROM Development] rxdoctor:
Beware Bepe Basic Rom
[Touch Cruise ROM Development] rxdoctor:
which was your first and second cooked rom?

Still trying to pin point - I hate blaming someone who does hard work and does not deserve it...so which was your first cooked rom and the second cooked rom....for me it was bepe basic .67 then swtos ultra light .93....I noticed the problem with swtos but I did not try bepe for longer than about an hour because of so may hangs....so really I do not know exactly when the problem started....but like you I know for sure it was a problem after the second cooked rom....I just wonder if my second rom would have been back to original shipped htc rom would i still have this problem????
[Touch Cruise ROM Development] olotam:
NV items

Vdavide, I compare yours nv items with the mine ( I've receptions problems with Polaris) and I find some diferences on entries like:

525 NV_WCDMA_LNA_OFFSET_VS_FREQ_| ;

726 NV_GSM_RX_GAIN_RANGE_1_FREQ_COMP_;

730 NV_DCS_RX_GAIN_RANGE_1_FREQ_COMP_;

1059 NV_GSM_1900_RX_GAIN_RANGE_2_FREQ_COMP_;

What do you think ? Is the problem here ?

I'm using the same radio rom, 1.64.08.21
[Touch Cruise ROM Development] rxdoctor:
can a cooked rom change NV items?

thats my only problem - from what I see cooked roms do not change nv items...and i am afraid to change anything here - might disable phone all together...I guess can always send in to HTC and say there must me some awsome virus that changes NV items hehe
[Touch Cruise ROM Development] olotam:
Sincerely I have no idea from this topic, but it's possible that someone know something about this.
[Touch Cruise ROM Development] mavvy4ever:
Does anyone have an original UNTOUCHED German O2 Orbit 2 and can post what versions are showing on boot for comparison? Here is mine:

R 1.58.21.23

G 25.65.30.04H

D 1.25.00.00
[Touch Cruise ROM Development] Olioaglio:
So far I can see this is OK...

Olioaglio