yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Q&A, Help & Troubleshooting] dhkr123:
I *really* doubt that it is a hardware problem.

In fact, I've heard those kinds of noises from other phones (i.e. RIM) calling me from the belus network (I use globalive... much better.)

Possibly a radio update might improve compatibility, could also be sim related.

I suggest that you root the thing, upgrade to the latest radio firmware, and install either tmo-ota or cm-mod on it. Also try using it on a DIFFERENT network (it is also compatible with robbers, but not globalive) and try using it on the SAME network with a different sim card.
[G2 and Desire Z Q&A, Help & Troubleshooting] opensourcefan:
Bell and Telus' new WCDMA network stinks. It is super weak as for now they put up the minimum towers to get full coverage. What that means is anything to anything will interfere with the signal strength. If I had my choice I would go back to Rogers in a heartbeat.

You issues sound exactly like a loss of signal issue.
[G2 and Desire Z Q&A, Help & Troubleshooting] MaestroSeven:
My wife has a bell desire z and it had the same problem. Should I return for a new one?
[G2 and Desire Z Q&A, Help & Troubleshooting] MaestroSeven:
Just one more thing. If it is a network related issue (bell). Why does my Samsung Galaxy S on the same network not have this issue? I think it is hardware related.
[G2 and Desire Z Q&A, Help & Troubleshooting] Smartenup:
I have experienced the identical issue a few times and I discovered it happens when you are on a call and the phone either switches to or tries to connect to a wireless network. My specific incidents have always been with a bluetooth connected however. Try turning off the wifi........
[G2 and Desire Z Q&A, Help & Troubleshooting] MaestroSeven:
That is interesting because her wifi is on when it happens.
[G2 and Desire Z Q&A, Help & Troubleshooting] BiMU:
I've just had the same problem... I've had the phone for around 26 days now and this is the first time this problem has happened. Anyone else solve it yet? I haven't even switched on the wifi.
[G2 and Desire Z Q&A, Help & Troubleshooting] Smartenup:
If you are certain that wifi was never on, then we need to call Bell.................
[G2 and Desire Z Q&A, Help & Troubleshooting] ral_shady:
Desire call issue

Hey guys,

Having the same issue, this is my second desire for the same scrambled issue. it sucks. sounds like a transformer is in phone.
[G2 and Desire Z Q&A, Help & Troubleshooting] IVI4V3R1CK:
I'm leaning toward that it's a carrier issue, not a hardware issue. Seeing how there are several people posting they have tried it on different phones and still had the issue, it would show that the hardware is identical between the devices. Also, seeing how people are having issues are localized to the one carrier, that would also make a difference.

I would like to state that I think rooting the phone and flashing a new radio update may fix the issue. If it doesn't, it could be that the radio in the phone just isn't built to process the network. But since it can physically pick up the signal, it may be how the software is transferring it, which is why you're having the issue, which is why I am recommending a root/radio fix.

In regards to the Samsung Galaxy S being brought up, it's different hardware, different software. Though it runs on the Android OS, Samsung uses it's own hardware and scripting, so it may be built to handle the connection better. It's the reason why for the longest time they were having GPS issues and we weren't (at least for the Vibrant variation of the phone).

That's just my humble opinion from my own dealings with phones though
[G2 and Desire Z Q&A, Help & Troubleshooting] MaestroSeven:
Can confirm it happens when wifi is off.
[G2 and Desire Z Q&A, Help & Troubleshooting] Smartenup:
I have had it happen 4 or 5 times and I have owned the phone for 5 months. Twice BT was connected as well. It has only rarely occurred for me...
[G2 and Desire Z Q&A, Help & Troubleshooting] Nerds2You:
My room mate is having the Same issue, stock Bell Desire Z on Bell network. The only two ways I have found so far to fix the issue is ether re-boot the phone or put it into airplane mode and then out of airplane mode. Doing a power off and then back on does NOT fix the problem (using fastboot), i'm sure it would fix it with the fastboot feature turned off.

Turning the radio on and off again fixes the issue so I am guessing it is a software issue. The Desire Z is an upgrade from an iPhone 3GS using the same SIM card on the same account, the iPhone never had the issue over the period of 1 full year.
[G2 and Desire Z Q&A, Help & Troubleshooting] s74:
Same Problem...

Hi everyone,

I wish there were a simple solution to this problem. My phone is doing the same thing (unlocked on the Telus network). I've researched this issue and found out that many people have also had the problem with the alien gurgling noise regardless of which network they're on.

I've had this problem occur regardless of wifi being on or off. It has nothing to do with the type of phone you're calling (as one Bell rep suggested). The problem is with receiving and dialing out calls. I've had several different types of phones while on this network and have never had this problem before. As for letting the problem sort itself out on it's own over time, that also doesn't work.

I brought my phone into Bell to be looked at. They thought the problem was the speaker. So they changed it and returned the phone to me. The first day I turned it on and activated it, the problem was back and worse than before. Couldn't make a successful phone call all day. So now it's back in the shop...again! The Bell rep said he's heard of this problem quite a few times. Something like 1 in 10 Desire Z's has this problem (that number sounds quite high to me). But yet, it doesn't look like these guys have a fix for the issue.

I love my Desire Z but I'm more than fed up because it's practically useless. I'm stuck using my iPhone again (not crazy about it at all) while I hunt for a replacement phone that will be comparable to the Desire Z (that will also work on the Telus network). Any ideas or suggestions? I was considering the Motorola Droid 2 Global but it didn't stand up to the Desire in speed/keyboard feel.

Thanks for listening! :)

P.S. - My phone was never rooted. Just unlocked.
[G2 and Desire Z Q&A, Help & Troubleshooting] theebest:
Your all holding it wrong D: . Jk but I havnt had this issue but my gf tells me that it happens to her
[G2 and Desire Z Q&A, Help & Troubleshooting] Bonusbartus:
I never had this issue, but I did upgrade to 1.72 and last week to 1.82.xxx
[G2 and Desire Z Q&A, Help & Troubleshooting] MaestroSeven:
Are you on bell?
[G2 and Desire Z Q&A, Help & Troubleshooting] Nex2k12:
Hello, first post here

I have had this issue twice. Both times I was calling someone else (Once to Rogers network once to Koodo/Telus) and both times I could hear them fine, but they could not hear me.

For me, it was occurring on the university of waterloo campus, which has notoriously bad reception with Bell. I also have a strange issue where my battery dies within a couple of hours while I'm on campus, which could be bad reception while indoors.

The next time I'm on campus I will try again. When I called back the person when it happened before, the problem persisted. I'm hoping location may narrow down the problem.
[G2 and Desire Z Q&A, Help & Troubleshooting] Nerds2You:
I have a possible resolution to the issue, I am hoping you guys can try it to see if it really works, I did it to my room mates phone on Sunday and it has not happened since.

What I have done is turn OFF ciphering on the phone to see if that resolves it, it could be a total coincidence, but it's worth a try and I am curious about everyone's results.

To turn off ciphering

1) go to phone dialer and type *#*#4636#*#* to get to the test menu

2) choose "Phone Information"

3) scroll to the bottom and toggle ciphering so it says OFF

give it a try and let everyone know if it makes a difference or not.
[G2 and Desire Z Q&A, Help & Troubleshooting] s74:
@Nerd2You,

Thank you for the suggestion. My phone is in repair right now as we speak. And between you, me and the garden fence, I'm not convinced they're going to get this sorted out. So, I will definitely give it a try. In the meantime, I really hope someone else tests out your theory. That would be wonderful.

Hope it pans out!. If so, you should be getting mad props from a lot of people. :)
[G2 and Desire Z Q&A, Help & Troubleshooting] dmason:
I just turned this off on my phone, so i hope to post back within a week or two to let you know. Is there any reason why we wouldn't want ciphering turned off??

Thanks!
[G2 and Desire Z Q&A, Help & Troubleshooting] prcme:
Ciphering appears to be a problem...

I had the problem of no signal in my basement. and after I took the phone back to the dealer (The Source), they gave me a new SIM card. Apparently there is a bunch of SIM cards that have issues. Bell Mobility have a list of serial numbers of questionable SIM cards, so I would recommend this first.

The new SIM card helped a little, but after I shut off the ciphering as you suggested, I now have significant improvement in signal quality where I had no signal before.

Thank you.

Does anyone know what the ciphering does? Will this pose any issues in the future?
[G2 and Desire Z Q&A, Help & Troubleshooting] prcme:
I got a reply from an HTC rep, so I turned the ciphering back on, and shortly after there was a system software update that seemed to fix things for me. The radio and everything were updated. I cut and pasted the reply from the HTC rep...

"Thank you for your patience, whilst I looked further into this for you.

I've spoken with a well-seasoned Bell representative, and basically, Ciphering is a method of encryption used to keep your conversations, as well as your phone's identity private. This is something that poses a personal security risk to you, and is highly unreccomended.

This being the case, we know that there's either:

(a) a network problem with ciphering.

or

(b) a hardware problem with the phone's internal modem.

Either way, we'll most likely need you to contact Bell to inform them that your phone is having problems with reception, and that ciphering seems to cause it. Chances are, they'll need to escalate it and either perform a repair on the phone and replace what they need to, or review how ciphering works on their network and work on it, accordingly.

Sincerely,

Megon

HTC

"
[G2 and Desire Z Q&A, Help & Troubleshooting] awsrasool:
re

hi guys...

i think you guys need to update the radio on the phone ... i had this exact problem a while back and I managed to fix it by updating the radio on the phone (also installed CM 7 RC4) ... the radio version i am using is the 12.50.60.24_26.08.04.1 you can find it in the development section

(http://xdaforums.com/showthread.php?t=970809)

since i updated it my signal got A LOT better and i got full HSPA signal like in most places.

I did the update about a week ago and since I havn't been experiencing these signal issues.

hope this helps...
[G2 and Desire Z Q&A, Help & Troubleshooting] psangha:
Thanks. I've been having this problem for several weeks -- I'm told I have chipmunks in my phone. I just updated to the latest radio (12.50.60.24_26.08.04.16).

Although I'm running GV 1.5 and not CM7. I'll let you know how it goes.
[G2 and Desire Z Q&A, Help & Troubleshooting] psangha:
Since changing radios, I've not had any more complaints about being 'garbled'.
[G2 and Desire Z Q&A, Help & Troubleshooting] dash4g:
Just thought I'd chime in here as well;

I am unlocked on telus as well (using gfree). Had this issue with the t mobile radio garbled, muted weirdness. Upgraded to the Australia radio about a month ago (12.28h.60.140f_26.06.02.27) and haven't had any issues since. Still doesnt fix Telus' deadzones however.

*edit* I also matched ril file libraries with the Radio to RIL Auotmatcher by rmk
[G2 and Desire Z Q&A, Help & Troubleshooting] psangha:
Which ROM are you using?
[G2 and Desire Z Q&A, Help & Troubleshooting] awsrasool:
you shouldnt match the library things if ur running ANY CM based ROM read through the thread first....
[HD2 General] aamszia:
Updated with this shipped rom via USB Cable

RUU_Leo_1_5_TMOUS_3.14.531.1_Radio_15.42.50.11U_2.15.50.14_LEO_1.5_Ship.exe

Hang on Stick Together logo .. 7 times vibration when i power ON ..

Help please

PB81120 SS-B3

SPL-2.10.000 8G XE

MicroP(LED) 0x05

MicroP(Touch) 0x50

Any idea guys ?
[HD2 General] aamszia:
RUU_Leo_1_5_TMOUS_2.13.531.1_Radio_15.39.50.07U_2.10.50.26_Signed_LEO_Ship.exe

I extract this rom & rename the BHH it to leoimg.nbh

& Flashed via Sdcard .. All went Ok

But still Hang on startup logo " Stick Together "

What is the problem ??

HELP
[HD2 General] albertorodast2007:
Give us some more info? have u hspl it before flashing that? enter bootloader and let us know if it reads: spl 2.08.0000 or spl 2.08.hspl Some times the radio is the problem, try flashing another radio, BUT MAKE SHURE you have hspl before attempting anything AND the radio u choose its a compatible T-mo US radio. OR YOU WILL NOT EVEN REACH THE STICK TOGETHER SCREEN NEXT TIME U REBOOT IT!
[HD2 General] aamszia:
Downgraded to 2.08.0000 .. now i can't even flash Stock ROM .. RSA Error by SDcard ...

so as you say ..

I have to change the SPL to 2.08.HSPL ( I did it now )

let me search radio of it ..
[HD2 General] aamszia:
Radio_Leo_2.15.50.14 Flashed now

downloaded from here

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

Still hang on " STICK together " & again 6 times vibrates

Phone has now 2.08 HSPL

any other ideas
[HD2 General] albertorodast2007:
remember if u flash a stock ROM with the SD card it WILL overwrite the spl and ull need to hspl it again...
[HD2 General] aamszia:
first i have 2.10.0000 ( original ) ..

Flashed 2 times with

RUU_Leo_1_5_TMOUS_3.14.531.1_Radio_15.42.50.11U_2.15.50.14_LEO_1.5_Ship.exe

&

RUU_Leo_1_5_TMOUS_2.13.531.1_Radio_15.39.50.07U_2.10.50.26_Signed_LEO_Ship.exe

same problem

then by HSPL3 i do 2.08.0000

then RSA Error , Can't even flash stock roms

then 2.08 HSPL ... New radio flashed still hangs

stocks rom don't help me either

i don't know what the hell i do now ?
[HD2 General] albertorodast2007:
Ohh so that's the problem... u can't hdpl whit the 2.10 spl ull have to flash an older stock rom with 2.08 spl an then flash hspl
[HD2 General] aamszia:
I have tried this but failed

RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe

You have the link for the which you are talking about
[HD2 General] albertorodast2007:
Uhm i guess ull have to dwnld it at tmo website or look at the test and stock roms thread, download any that says has spl 2.08 included and flash it via SD, then use hspl and choose 2.08.hspl... hope this help u

PD. Never mind download this file:

www.2shared.com/file/MAsa78Yo/leoimg.html

www.megaupload.com/?d=VQ11Z040

Sent from my HTC HD2 using Cyanogen Mod Android
[HD2 General] lebmb:
mine is having the same issue, mainly after i take a few pictures or video or wifi

i tried every possible combination of different roms, spl, radios, i've tried them all

i was on stock rom and spl when it happened.

i called htc and im gona send it back to them we'll see what happens
[HD2 General] mrcrich83:
vibrating 7 times

sorry to tell you but the same thing happened to my phone and i had to send it to htc to get the mainboard replaced. its free under warrenty but will cost up to $170 US for the repair. call customer service and see what they say. also note that after the repair it will be returned with the carrier lock in place so you will have to request the code from HTC also.
[HD2 General] alaa_2057:
The same problem please help

no another way to replace the main board
[HD2 General] holigan:
I also experience same problem with my TMOUS HD2.

I confirm that issues seem to appear when the phone is getting hot.(After 10mins. of usage in general)

Fatal Hit error on start up or stuck at magldr's "go go go screen"

Configuration:

2.08 HSPL

Radio 2.15.50.14

Magldr 1.13

All helps would be appreciated.
[Desire General] revthanki:
Hi all, I'm using the Gingerbread Oxygen rom by Adam G. It's fantastic.

But I have a quick question, whose answer I can't find by searching:

My battery life is poor, I think because some app is using a partial wake lock to prevent sleep (grrrr). In my previous ROMs I was able to use the code *#*#4636#*#* to bring up detailed information on which apps were causing problems. However with gingerbread/oxygen this level of detail is not present. Anyone got any ideas how I can find the misbehaving bugger?

Peace out!
[Desire General] Carceri:
I would like to know that too. I'm also using Oxygen, and suffering from very poor battery life.
[Desire General] torwag:
PowerTutor is what are you looking for
[Desire General] Jim_Fear:
Check whether or not your wireless is on but not connected. I found this to be an issue with Oxygen and battery life initially but I set a rule in the power control widget to only turn on bluetooth and wireless when plugged in to a power source.
[Desire General] Carceri:
Thanks. I will try Power Tutor.

The problem happened after I switched to Oxygen from the stock Desire kernel, so I suspect that some apps don't play nicely with Gingerbread, and hence keeps the phone from sleeping. I have tried with WiFi off and the battery drain still happens.
[Nook Color General] giantcrazy:
My kids received Nook Color readers for Christmas, and like everything, they look to Dad to optimize them.

I was going to try rooting, but a couple of things remain unclear:

- Do I have to 'auto-noot' to root the Noot, or are there other options (other tools, manual rooting, etc.)

- Should I upgrade the software to 1.0.1 prior to rooting or not?

I tried to give auto-noot for 1.0.0 a quick run, but I couldn't get the SD card to boot (and a check revealed that I had two FAT16 partitions, one with the appropriate images and the other with the files needed). I'm assuming it's because the card I have might be too slow (portal recommends Class 6 or greater, and the card I'm using is a cheapo card I got with an earlier phone that I'm not too sure of).

Thoughts? Tips?
[Nook Color General] lopezpm:
I upgraded mine to 1.0.1 first then rooted.

What OS is on your PC?

If Windows, did you use Win32DiskImager to write the image to microSD card?

Take a look at here for different ways of rooting here http://www.nookdevs.com/Portal:NookColor#Rooting

The easiest and the way I rooted is below which I borrowed from http://blogkindle.com/2010/12/read-kindle-books-on-nook-color/

Here’s what you need to do:

1. Before rooting make sure that you’ve registered the device with B&N as it might not work after rooting.

2. Download nooter that corresponds to you Nook version. You can check your Nook version by pressing Nook button, selecting “Settings” >> “Device Info” >> “About your NOOKcolor” >> Software version:

--- for 1.0.0 – GabrialDestruir’s auto nooter 2.12.15 file 15 Dec 2010

--- for 1.0.1 – GabrialDestruir’s auto nooter 2.12.25 file 25 Dec 2010

3. Unpack the file

4. On Windows use Win32DiskImager to write the image to microSD card (please note that all data on the card will be lost). For Linux or Mac, check out NookDevs.com for detailed microSD imaging instructions.

5. Completely power off NOOKcolor by holding the power button until the screen blurs and “Power off NOOKColor” dialog appears. Select “Power Off” and wait for the device to shut down completely.

6. Turn device face down and open the microSD card container in the lower right corner. Push the card in with metal contacts facing down.

7. Connect the device to your computer via USB cable. The device will power up and book from the SD card but the screen will not turn on. This is normal.

8. After about a minute your computer show detect the new device. This means that the rooting is complete. Your Windows computer will complain about missing drivers. This is normal.

9. Disconnect the USB cable and remove the card from the reader.

10. Power cycle it by holding the power button for 20 seconds and then releasing it. The press the power button briefly to power the reader on.

11. As the reader boots you will see a red splash screen.

12. Once the reader boots, you will be prompted for you Gmail account (as usually with Android) and some initial settings. This will only happen once.

13. As you open the extras folder you will see that it now contains Android market icon and some extras (Youtube, Gmail, etc)

14. You can now start the market app and download other apps that you like. You will need to reboot the device for apps to appear on the extras page. The apps themselves can be used right away just as with usual Android apps.
[Nook Color General] k8108:
I would look for the thread in the android development section for auto nook 1.01. Update the OS to 1.01, then do the nook-ing process. Its all laid out there in the opening post.

I would definitely root your nooks to get the most out of them.
[Nook Color General] lopezpm:
I'm guessing he meant Auto-Nooter 2.12.25 (1.0.1 Only), which the thread can be found here
[Nook Color General] giantcrazy:
I was looking for a manual method because I didn't have my card reader at work yesterday, and I couldn't get the card I wrote in my Incredible to boot Auto-Noot in 1.0.0.

Oddly enough, after deciding to upgrade to 1.0.1 first, when I tried to root the second time it worked just fine. I did the second one after upgrading, also went without a hitch. Think it just makes sense to upgrade first, seeing as they're both exploitable.
[Nook Color General] clockcycle:
How can you write an image from your Incredible? You need to use a computer to write the "image" not just the files to the sdcard, to make it bootable.

-CC
[Nook Color General] giantcrazy:
I spent some time re-inventing the wheel before I realized someone had documented the method on XDA (my fault for being search lazy):

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

You use the Linux DD command to write the image to the SD card, which renders it with the correct partitions and files needed to complete root. I did it yesterday, and assumed that I had either too slow a card or it didn't work, until I upgraded to 1.0.1 first and it worked at first crack. Just take care to write the card with the correct device name, mmcblk1.

I used GParted on Linux to double-check after doing my fdisk, everything looked kosher to me and it worked flawlessly.
[Nook Color General] clockcycle:
Ah, totally forgot about that.. Well glad you got it sorted.

-CC
[G Tablet General] Das_Negros:
My company has a 802.1x wifi and I would like to add my G TAb to it. Problem is that there isn't an option in the wireless settings for AES/Radius. I can see the name of the network BUT when I click on it, it simply changes the screen to the security screen which is for making passwords visible or resetting the G Tab. Thanks to all who can help me resolve this. I mean what good is having such an AWESOME piece of equipement if you can't use it at work.:confused:
[Galaxy Tab General] Dyonas:
I own an HTC Desire HD but I've been after some form of tablet since before Apple walked in with the iPad. Looking around there's no real choice yet but that's going to change in the next few months. Question is, is the Galaxy Tab with getting now or would you (current owners) wait if you were in my position?
[Galaxy Tab General] heythorp:
Learning to really love the tab, but with the announcements right around the corner I would wait.

Who knows when they will be available, but at least you can then make an informed decision. Only a couple weeks away to see whats coming.

If tabs are going to wait for honeycomb and if the rumors are true that honeycomb wont be available until may or june, then I would say get it now. 6 months is a long time to wait.

With that said wait for the announcements to find out for sure.
[Galaxy Tab General] Hanson68:
I'd only get the Galaxy Tab if I specifically wanted a 7" form factor. If you're more interested in a 10" tablet, wait for Honeycomb.
[Galaxy Tab General] LargePrime:
Note that it is unlikely that the 10"ers will have a higher resolution.