I have only had the G1 for a week or so but ever since i got root and upgraded to rc33 i noticed that right when i make a phone call i get a buzzing noise in the earphone.
It sounds the same as when your phone is near a speaker and you get a phone call and the speaker starts to buzz and beep. It does it for about 10 seconds and then stops and then comes back after 30 seconds...
anyone else experiencing this?
really starting to annoy me...
first the creek in the screen and now this
any help will be appreciated
My first g1 had this problem I called customer care and did it for him over the phone and they replaced it. Mine was 100% stock as it was a rc30 before we could root. Mine would happen right after I hung up a call or stopped playing music. Just call customer care and they will fix the issue
diabolical28 said:
My first g1 had this problem I called customer care and did it for him over the phone and they replaced it. Mine was 100% stock as it was a rc30 before we could root. Mine would happen right after I hung up a call or stopped playing music. Just call customer care and they will fix the issue
Click to expand...
Click to collapse
I dont think i can call customer care because I didnt buy it from tmobile or a licensed retailer. More from a third party(was a brand new set though). Also not signed up for tmobile.
well outside the tmobile aspect maybe you could get it exchanged but with mine it was defective and replaced. i think its just the unit itself not the update you made to it. maybe another poster has had this problem and been able to fix it. with mine i refused to accept faulty equip as brand new merchendice
Ok so I called HTC today and they told me that they do not do tech support on teh G1 so i was transferred to a TMobile line.
T-mobile told me that it is something that needs to be handled by HTC so they transfer me back to HTC.
HTC rep says that i need to have T-Mobile do troubleshooting first so I get transferred back to T-mobile
T-Mobile representative now tells me that she does not have the correct Documentation to instruct me on how to do a "Hard Reset" so i tell her that i already know how to do all of that and i already did it.
haha now back to HTC so maybe they can repair or replace mine...
Lets hope no more transferring
estimated talk time 2hrs 30min
Same problem here!
Mine (ADP1) had the buzz from day one. Unfortunately, there's no way I could replace it.
The buzz is there when I'm calling, before the other side picks up. If I move the screen just a little bit to the side, there's a abrupt change in buzz volume and then it disappears. If I let go of the screen, the buzzing reappears.
Sounds like a hardware problem (like a bad contact or something).
I didn't have the issue initially but started getting it after a firmware/radio update.
What radio version are you guys running, and what firmware?
Note, im on an ADP1 with AT&T and the radio update from RC33
Also, I noticed that this is highly reproducible when EDGE data is being transferred
Mine also goes away when i move my screen slightly either way.
I think it might be because of the network we are on because im on ATT edge network using the RC33 update.
If it is quite enough i can hear the beeping buzzing sound when data is being transferred as well.
Might be something that we will need to live with...
kp126 said:
Mine also goes away when i move my screen slightly either way.
I think it might be because of the network we are on because im on ATT edge network using the RC33 update.
If it is quite enough i can hear the beeping buzzing sound when data is being transferred as well.
Might be something that we will need to live with...
Click to expand...
Click to collapse
Weird... Well I found a post on the T-Mobile forums about someone complaining about it...
I also noticed that the problem doesnt occur when GPRS is being used (to my knowledge at least).
I'm hoping that maybe the next true official ADP update will fix all this, keep your fingers crossed
someprogr said:
Weird... Well I found a post on the T-Mobile forums about someone complaining about it...
I also noticed that the problem doesnt occur when GPRS is being used (to my knowledge at least).
I'm hoping that maybe the next true official ADP update will fix all this, keep your fingers crossed
Click to expand...
Click to collapse
any useful info in the tmo forums?
kp126 said:
any useful info in the tmo forums?
Click to expand...
Click to collapse
No, just some 1 post thread about a guy that complains about it not working on EDGE... Most likely the guy has AT&T as well..
Do you think it may have anything to do with running RC33? As I said, I updated to ADP1.1 with the RC33 radio and JF 1.43, but I truely have no idea if it was doing it prior to the upgrade.
someprogr said:
No, just some 1 post thread about a guy that complains about it not working on EDGE... Most likely the guy has AT&T as well..
Do you think it may have anything to do with running RC33? As I said, I updated to ADP1.1 with the RC33 radio and JF 1.43, but I truely have no idea if it was doing it prior to the upgrade.
Click to expand...
Click to collapse
the problem is that i dont remember if it was doing it before i flashed to rc33 either which means it probably wasnt because it is something that is very noticeable right away. I wouldnt miss something like that. I am willing to downgrade to rc19 just to test it out if no one else has any other ideas. really dont want to do it because i installed a bunch of stuff and have everything finally customized to the way i want it. but if necessary then it will be done
kp126 said:
the problem is that i dont remember if it was doing it before i flashed to rc33 either which means it probably wasnt because it is something that is very noticeable right away. I wouldnt miss something like that. I am willing to downgrade to rc19 just to test it out if no one else has any other ideas. really dont want to do it because i installed a bunch of stuff and have everything finally customized to the way i want it. but if necessary then it will be done
Click to expand...
Click to collapse
Same here... Not only that, I upgraded the radio to RC33... From what I understand, the original radio.img from stock ADP1 is irretrievable -- So reverting to an older baseband is not an option. If it really starts to nag me, i'll either downgrade and try it out, or wait it out for an official update for ADP.
What really bugs me is the fact that no one else with AT&T is reporting this issue, making me think its a hardware defect.
someprogr said:
Same here... Not only that, I upgraded the radio to RC33... From what I understand, the original radio.img from stock ADP1 is irretrievable -- So reverting to an older baseband is not an option. If it really starts to nag me, i'll either downgrade and try it out, or wait it out for an official update for ADP.
What really bugs me is the fact that no one else with AT&T is reporting this issue, making me think its a hardware defect.
Click to expand...
Click to collapse
But if it is a hardware defect then what about the TMO users who would be experiencing this problem.
There is no possible way to flash the older radio? remember it being possible with wm(of course two totally diff beasts)
If it is hardware, i think i convinced htc to help me with it. The reason i didnt want to do it is because i put on some protective gear on the phone which i shelled out around 25 dollars for (shield skins and unique skins) if i send it in, most likely i will receive another phone.
Hoping it is software and not hardware.
Keep me updated
kp126 said:
But if it is a hardware defect then what about the TMO users who would be experiencing this problem.
There is no possible way to flash the older radio? remember it being possible with wm(of course two totally diff beasts)
If it is hardware, i think i convinced htc to help me with it. The reason i didnt want to do it is because i put on some protective gear on the phone which i shelled out around 25 dollars for (shield skins and unique skins) if i send it in, most likely i will receive another phone.
Hoping it is software and not hardware.
Keep me updated
Click to expand...
Click to collapse
From what I understand in the forums and IRC (Heard from reputable sources like Disconnect) they told me that there was no way to grab the radio from the stock ADP1 hardware. I'm surprised HTC is going to take a look at it, as it is a dev phone and not a branded G1. I may eventually go that route if it starts to really annoy me me, but I'd rather downgrade first rather than actually ship it in (And if im going to ship it in, I'm going to wipe everything so it wouldnt matter anyway).
Let me know if you find out any info, and I'll post if I can figure something out along the way as well.
i have att and i also get the "da da drrr" from phone earpiece when placing a call. i dont get that noise when im on wifi though so i believe its gprs related.
someprogr said:
From what I understand in the forums and IRC (Heard from reputable sources like Disconnect) they told me that there was no way to grab the radio from the stock ADP1 hardware. I'm surprised HTC is going to take a look at it, as it is a dev phone and not a branded G1. I may eventually go that route if it starts to really annoy me me, but I'd rather downgrade first rather than actually ship it in (And if im going to ship it in, I'm going to wipe everything so it wouldnt matter anyway).
Let me know if you find out any info, and I'll post if I can figure something out along the way as well.
Click to expand...
Click to collapse
Mine is branded g1. Not a developer phone and i have no proof of purchase(atleast date wise).
I'm starting to see some consistency regarding reproducing the issue.
I notice that if I press the earpiece part against the keyboard, the buzzing stops. Also the buzzing doesnt occur when the keyboard is out.
I'm concluding that the antenna is inside the keyboard on the other end. Maybe if there is a way to put a piece of tape between the back of the earpart (that touches the keyboard) the problem will go away.
Tape could be anything... Maybe something that blocks interference. Hmmmm
My ADP1 had the buzz with the original radio image too. Upgrading to RC33 radio image changed absolutely nothing.
Also, I don't have gprs/edge turned on, I use wifi almost exclusively. There's no wifi activity when I'm calling. 3G is also turned off.
There's probably an interference between the GSM radio (antenna?) and some phone component (speaker?) which picks up the GSM signal and produces the familiar buzz sound.
torrentss said:
My ADP1 had the buzz with the original radio image too. Upgrading to RC33 radio image changed absolutely nothing.
Also, I don't have gprs/edge turned on, I use wifi almost exclusively. There's no wifi activity when I'm calling. 3G is also turned off.
There's probably an interference between the GSM radio (antenna?) and some phone component (speaker?) which picks up the GSM signal and produces the familiar buzz sound.
Click to expand...
Click to collapse
whats your provider?
Related
OK, I know that may look like a dumb question (and maybe it is!!!)
I have just unlocked my Vario 2 using the "Pof" method with both Sim and SuperCID.
Problem is, my phone needs to be sent back (long story - but basically I am getting a replacement Vario 3). Now obviously I am concerned they will tell me "sorry youve been playing with your phone sonny - its no longer under warrenty", so need to get it back to factory settings if I can.
I appreciate a hard reset will basically wipe any files I have, contacts and settings etc, but will this remove the unlocks that have been done? ie It really does go back to factory settings - or do these unlocks stay on there?
I have been searching the forum and WIKI, but not found the solution. I did think I would need to install a T-Mobile Rom - but all I could find was a hungarian version - which whilst in English, would probably look worse than as I currently have it!
Any help appreciated.
Thanks
EDIT:
For the record, if it makes any difference:
ROM Version 1.21.110.3
Rom Date 06/19/06
Radio version 1.16.00.00
Herm300 IPL-1.01
SPL 1.40.0lipro
a hard reset simply formats the internal drive on the phone and resets it to the factory settings.
generally t mobile wont bother looking at things like that, i unlocked my vario, dropped it, it smashed, they just replaced it after trying to repair it.
A few people have flashed new roms and bricked it, sent it back, tmobile are none the wiser, they are probably unaware people to this to their handsets!
we are all just stupid customers as far as they are concerned!
personally i wouldnt worry about it!
andaroo said:
a hard reset simply formats the internal drive on the phone and resets it to the factory settings.
generally t mobile wont bother looking at things like that, i unlocked my vario, dropped it, it smashed, they just replaced it after trying to repair it.
A few people have flashed new roms and bricked it, sent it back, tmobile are none the wiser, they are probably unaware people to this to their handsets!
we are all just stupid customers as far as they are concerned!
personally i wouldnt worry about it!
Click to expand...
Click to collapse
OK thanks for that. So I assume a hard reset will not over write anything regarding the bootloader radio change and unlocks? I appreciated that it resets the OS - hence the question.
I agree that they probably wouldnt in most cases look into the phone and check, but they have put a note on my account about "charging if not found faulty".
The problem I have been getting is missing calls - even if I am in a strong signal area. I actually work at Waterloo Railway station - and I would doubt too many places would get a better signal! An incoming call is made, my phone doesnt ring and the caller gets a single ring, then nothing. From what I can now gather, this may be to do with the cell shaking hands but not really being connected. ie the phone/cell are duping each other. This appears to be a 3G issue (so is probably likely to still be there on exchange.) Now the silly thing I have noticed; the phone seemed fine until I got web'n'walk put back on and the problem happens once I have been online. Strangely at the moment, I dont think the problem is persisiting (ie Im not aware of missing calls - though of course thats difficult to quantify unless someone tells me!)
Anyway - I have a feeling they will be looking more into this phone as this replacement will be my 5th! (The previous had similar problems with calls being made or incoming that would just fall over before being answered and the signal being completely lost when it was happening. Slightly different this time - but sound related!)
So will there be a way to put it back to being locked and the correct bootloader etc being shown?
Many thanks
I had the same problem with rejected and dropped calls, tmobile couldnt care less from what i learned or are unaware of the problem! try this
1. lock the phone to gsm only (this solved it pretty much straight away)
2) remove the voicemail from your account
3) If you are using gprs data, you will rarely get a phone call through, and by using it i mean looking at web pages or having programs update in the background.
Downgrading the bootloader is way above my head so i wouldnt like to advise.
As regard to relocking the phone to the network, i dont think thats possible, in any event, why would they check the simlock if the phone is having problems with calls!
If its your fifth handset, you should be looking at changing the model at least because thats ridiculous.
It sounds like a network issue rather than a handset problem!
andaroo said:
I had the same problem with rejected and dropped calls, tmobile couldnt care less from what i learned or are unaware of the problem! try this
1. lock the phone to gsm only (this solved it pretty much straight away)
2) remove the voicemail from your account
3) If you are using gprs data, you will rarely get a phone call through, and by using it i mean looking at web pages or having programs update in the background.
Click to expand...
Click to collapse
Yeh, the problems on this phone didnt start until I began using the net again. They did suggest switching off 3G, but since I bought the phone specifically on the promise of a fast connection and HSPDA speeds, that really is an unacceptable solution! I appreciate that signal varies etc - but if a central location where I work isnt good enough, then T-Mobile really shouldnt be advertising themselves as a 3G network!
As it happens, voicemail was switched off on the account. It got put back on again a week ago - and sods law - things now seem to be working, though internet speeds are still very slow.
As regard to relocking the phone to the network, i dont think thats possible, in any event, why would they check the simlock if the phone is having problems with calls!
Click to expand...
Click to collapse
Dunno really. Its just a concern they will and then use it to wriggle out of an exchange!
If its your fifth handset, you should be looking at changing the model at least because thats ridiculous.
It sounds like a network issue rather than a handset problem!
Click to expand...
Click to collapse
When I phoned, I was just looking to get a repair, but it was them that offered a Vario 3 which I accepted. It was agreed for them to be sending the set to me (last Thursday) but all that arrived was a grey bag to send my old one back. I spoke with them at great length again last night and suggested a straight courier swap so I wasn't without a phone. They went through to their repair department, who have now flatly refused the phone change - despite it being agreed already!
Anyway I spoke to another manager who went through my "book" of notes and quoted the sale of goods act and merchandisable quality thing and he has agreed they really have to address this. He is phoning me back today and he did come across as helpful and reasonable. (The second one in 2 weeks - must be a record!!!)
I do agree though, that this issue is likely to be the network and not the phone. I would really love to use O2 as at work and home I get 100% coverage and never had any problems at all - but I ain't paying their data rates! Maybe 3 will be ok - but again, when I had them a few years back, at home they were dire so never bothered again. But one thing is pretty certain, in 5 months time, T-Mobile will be history unless they make amends in a big way and these problems become non existant.
Thanks for your help..... its appreciated.
So apparently whenever I try calling anyone they say I sound loud and I have an echo kind of. My mom who used to be a ham operator described it as sounding "tinny" (the metal). My wife and my other friend said it sounds like I am talking into a trash can. Anyone else have this problem or know of a fix?
u can try:
1: do a wipe
2: pull out sim and reinsert it
3: re-search network
hope it helps
Ok I wiped the phone and pulled the sim and what-not, but my wife told me I still sounded the same. So I took it into my own hands to have her talk into the phone while I listened on her cell phone.
Apparently it's not really an echo as opposed to you can just hear EVERYTHING that is going on around the person with the phone. The microphone is either just really too sensitive or it's not one-directional (bad design or my phone is defective?).
I just realized what it sounded like. It basically sounds as if my outbound is like I am talking through a speakerphone.
EDIT: basically consensus with my friends and family is that I should get the phone replaced. However, I purchased the phone off eBay (it was brand new unopened) and it has a 1yr. manufacturer warranty. So I have 2 new questions...I am currently rooted and to my understanding if I follow the directions here http://code.google.com/p/android-roms/wiki/Unroot my phone will be unrooted, willthis make the phone ok to take in to be replaced? Also, will the technicians at the t-mobile store be able to replace the phone there (if they do find something wrong) or will I need to mail my phone somewhere and wait for it to get mailed back?
hmm.......have u tried re-searching the network again?
maybe its the hardware prob, have u thought of bringing it back to where u bought it?
zgmf-x322a said:
hmm.......have u tried re-searching the network again?
maybe its the hardware prob, have u thought of bringing it back to where u bought it?
Click to expand...
Click to collapse
I bought it off of ebay...there was a "no returns" policy on it.
Also, how would I get it to re-search the network? I wiped the phone then took out the sim and put it back in.
to do a re-search of the network:
go to:
settings --> wireless controls --> mobile networks --> network operators
and it will auto start searching
other than this method, i dun seem to have another option for u.....
but whats the reason why u got it from ebay?
zgmf-x322a said:
other than this method, i dun seem to have another option for u.....
but whats the reason why u got it from ebay?
Click to expand...
Click to collapse
Thanks for the help, but it didnt work. Realized that I could just check to see if it was the mic by plugging in the headset it came with and using that. The outbound quality with the headset is great, while the quality with the internal microphone was bad. Think tmobile will replace the phone for me? I got it off ebay because ebay is generally cheaper than other places. My past two phones were off ebay (Moto Q and HTC Touch).
Have you flashed to the newest Radio?
haha
ill never get it from online....its too risky :S
So HTC will send me a replacement...but now I have the problem with the phone being rooted and having a custom ROM on it.
Does anyone know how to restore the phone back to factory default?
hueman84 said:
So HTC will send me a replacement...but now I have the problem with the phone being rooted and having a custom ROM on it.
Does anyone know how to restore the phone back to factory default?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=491350
I have had the same problem since rooting my phone. I am 99% sure this is a software issue rather than hardware. Just updated the radio, but won't know if it worked until I talk to my girl in the morning. She hates talking to me since I rooted - she can here everything in the background. Seems like somehow, the speakerphone mic profile is active even when on private calls. So annoying.
The problem you are having has to do with the volume hack which is included in many roms. To rid yourself of the issue you can push the normal equalizer files from a stock build and reboot the phone. I think the volume boost hacks are of dubious use anyways. As in my opinion the phone is already too loud even with the default equalizer.
does cm have this hack?
I think pretty much all of them do.
Hi,
Did someone found a solution to this problem? I have exactly the same since I rooted my phone a few months ago.
Where can I find the sound hack file?
Thanks
Is anyone else's volume UP button strangely stopped working. Had the phone less than 24 hours and already it doesn't work. it still clicks in but nothing. Volume down works fine.
Also gutted to send it back I have to wait for it to come back in stock to recieve a replacement unit.
bob2k4 said:
Is anyone else's volume UP button strangely stopped working. Had the phone less than 24 hours and already it doesn't work. it still clicks in but nothing. Volume down works fine.
Also gutted to send it back I have to wait for it to come back in stock to recieve a replacement unit.
Click to expand...
Click to collapse
I've seen another thread with someone talking about the same issue...
here you go:
http://forum.xda-developers.com/showthread.php?t=583399
Once more: http://forum.xda-developers.com/showthread.php?t=583554
Maybe there is a production fault?
It would be every untypical for HTC to launch a device of which the first builts do not have hardware issues.
Was the same with my TP.
Hardware keyboard, black paint coming off the housing, plastic cover coming off the hardware keys below the screen, ... .
Had to send it in for replacement three times, before I got finally one of the more mature builts, which had (and still has) no problems.
As I want to get the HD2 latest for Christmas, I guess I will still get one of the early builts, and have to go through the return procedure at least once or twice.
Is quite bad that this happens. Products shouldn't have to go through several return procedures because of faults.
They should just get it right first time. How many times do they produce prototypes and test models. It's quite annoying how these things crop up. Can't be hard to catch when manufacturing the phones.
Ok, I really don't have any clue about the differences between sim free and sold by a network, but could this have something to do with why it took/is taking so long for the networks to launch the phone ?
As I understand, they also do their own tests ?
Yeah basically networks like to do tonnes of software tests on the devices to make sure that everything is working properly before they release the phone themselves. Makes sense to do it that way instead of blind releasing a phone, not knowing how long they need to test it for however, is baffling. I don't know how they can't put a date on when it'll be done.
timewyrm said:
Ok, I really don't have any clue about the differences between sim free and sold by a network, but could this have something to do with why it took/is taking so long for the networks to launch the phone ?
As I understand, they also do their own tests ?
Click to expand...
Click to collapse
Networks will also bastardise the ROM/firmware to include there own logos, apps, shortcuts etc - they will even remove certain features.
Orange are a nightmare for that...and firmware releases are few and far between...
Nit3m4re said:
Yeah basically networks like to do tonnes of software tests on the devices to make sure that everything is working properly before they release the phone themselves. Makes sense to do it that way instead of blind releasing a phone, not knowing how long they need to test it for however, is baffling. I don't know how they can't put a date on when it'll be done.
Click to expand...
Click to collapse
So, does that mean less chance of ending up with a faulty phone ( I know that they probably only try a few phones in each batch) ?
bigsro said:
Networks will also bastardise the ROM/firmware to include there own logos, apps, shortcuts etc - they will even remove certain features.
Orange are a nightmare for that...and firmware releases are few and far between...
Click to expand...
Click to collapse
Well, I guess I'll find out tomorrow.
Yep mine had exactly the same problem. I sent it back and should hopefully have a new one on Monday.
Broken Up button Volume
Has anyone resolved the broken up button issue? I'm hoping that it can be fixed without having to exchange it because I bought mine overseas.
I sent mine back and they are replacing it. I probably could've fixed it myself but when you pay £500 for a new phone you expect it to be working properly.
hi,
today the same happend to me, after one week of use the up button died, for absolutly no reason. i used the buton mayby 10 times thats it.
I bought my HD2 a couple of weeks ago from my local shop and noticed straight away that the photos all had a big pink spot in the middle. The manager said he'd replace it as soon as he had stock back in (been very good).
I got a phone call this week to say replacement HD2 was waiting for me so I collected it yesterday and this one's camera works - yay... except it's volume up button doesn't work
So, time to replace it again whenever the next stock is in and I'm betting the 3rd phone will have a dodgy camera again, lol
Hello XDA,
I first off want to say that this site is amazing. Alot of good people on here making some great stuff and i just want to say thank you. Now, my issue...
I purchased the HD2 (T-Mo U.S.) the day it was released and ever since i have gotten the phone i have experienced nothing but issues. The first thing i noted about the phone was that the speaker was WAY too loud. Even when i turned it down it just seemed to be still be loud enough that people in the same room could hear my convo. After a while the speaker started to crackle and now the call quality sounds like ****..it's not all the time but most of the time. Another issue i started to have was that everytime i picked up a call the ear speaker would go mute. I would have to either put the convo on speaker OR hold the phone face down to active speaker, then whip it right back to my ear and it would sometimes unmute itself. You can only imagine my frustration when i called the tmobile store and they tell me i can get a replacement as long as i "wait for a new shipment"
So now to my software issues. As far as modding concerns i have not really changed much on the phone. I' ve installed HD tweeks + some games and my contacts. Now every time i exit a game...the OS either freezes...or it just starts buggin out on me. The bottom bar (phone / menu) will freeze or the whole OS will become super laggy and unresponsive. It has even happened just by using the SMS application at times. Also i find that i could be doing the simplest thing on the phone and for no reason...it wil decide to freeze on me. Sometime half the screen, sometimes the whole thing. I have to remove the battery to reset it when that happens.
Now i know about closing opened programs through the task manager and also about clearing sms's regularly and soon and so forth. If there is anything else you guys think i should consider doing i am ready to hear it. I came from a 1st Gen iPhone that i had since 2007, which i jailbroken for tmobile (the OLD way...lol) and in the 2 years i had that phone the HD2 has given me more problems in its 2 weeks.
Do you guys think i got a really defective phone?...or is WinMo really just that ****ty? I dont want to get another phone but as it is,..im really thinking about just giving up on it. Any suggestions would be greatly appreciated and once again thanks!
I think you have a defective phone. My HD2 (from T-Mobile) doesn't have issues at all with the phone going mute. It could also be the HD tweeks, i would do a hard reset and see if you are still having this issue.
i would suggest try flashing a custom rom with new radio and c if that works i had the call sound problem flashed rom n radio now its crystal clear and runs brilliant
greg1fraser said:
i would suggest try flashing a custom rom with new radio and c if that works i had the call sound problem flashed rom n radio now its crystal clear and runs brilliant
Click to expand...
Click to collapse
Oh really?...Can you give me more info on this and your previous issue?
my phone would occasional mute or hold the call without me relising and the call quality was terrible my friend in usa has t mob one and he had similar issue he read the stickies in the rom development forum and flashed a custom rom and radio and he thinks it solved his problem it solved mine if its new i would be tempted to take a new handset and see
hope that helps
greg
i wouldnt flash a rom. its a brand new phone do the factory reset first and if that doresnt work exvhange it. If you flash the rom you will void your warranty most likely. IMHO you're already on 2.10 rom which is pretty new and should have all the latest hotfixes
dipaolnv said:
i wouldnt flash a rom. its a brand new phone do the factory reset first and if that doresnt work exvhange it. If you flash the rom you will void your warranty most likely. IMHO you're already on 2.10 rom which is pretty new and should have all the latest hotfixes
Click to expand...
Click to collapse
You won't void your warranty flashing anymore... the hspl can easily be taken off now with the same app that puts it on. You can try flashing a rom... it might fix it. Otherwise, flash back to stock rom, take hspl off, and then exchange it. I'm still on stock atm, and haven't had any problems people are complaining of. My only issue is T-mobiles crappy 3g coverage that doesn't even work inside my house. I have 1 more day to decide if I want to return it and go back to at&t... Save up and get myself an australian HD2.
Returning the phone today. Even with the issue of broken ear piece, i just cant take this anymore. Beautiful phone, great UI (sense) but the glitchy-ness of WinMo is just too unbearable. guess ill be getting a Nexus.
it is really up to you if you wanna return it back and get a N1. i bought this phone cause of this specs. and for me it do very nice. you can even buy a iphone also which also very easy to use and less bugs ofcourse nothing is perfect as in "Perfect"
not everybody wants to take risk and flash roms and other stuffs so i guess its your best decision. good luck... but if you need any help about HD2 please feel free to come by this threads...
yea i bought the HD2 hopefully i dont get those problem or else NEXUS one for me too.
Ok guys heres my situation.
Im on my third streak, the first one the earpiece stopped working, the second one had the stick slide to unlock, i got my third one today (o2 very kindly gave me a second battery and back cover!)
But im annoyed to see that this new one still has the sticky slide to unlock. I know there are some apps i can use to get round it, but it seems a bit odd for such a device to make it hard to answer calls!!
Anyone know why this happens, is it a hardware thing or is it the rom?
Or any advice what i can do, its on contrat from o2, anything i can do?
Thanks
I'm just guessing but it seems to be a that the screen just becomes un responsive. I can use the side buttons but I can't get the touch screen to work. almost as though its been disabled.
this happens less with 2.2 and I use the menu unlock from knobs. it means that I hardly notice it these days.
Sent from my Dell Streak using XDA App
I have read many people have this problem as a result of keepingthe phone in their pants. Something about the screen being in a constant discharging state that messes with its accuracy.
Sent from my Dell Streak using XDA App
Yea I guess that makes sense, but where do Dell want us to keep it!
Any way to stop this happening?
Well I use a holster for mine. Considering the reports of 'pants stress' cracking the lcd underneath the glass, I don't want to take any chances. Plus it makes a nice fashion statement
Sent from my Dell Streak using XDA App
kapakra said:
Ok guys heres my situation.
Im on my third streak, the first one the earpiece stopped working, the second one had the stick slide to unlock, i got my third one today (o2 very kindly gave me a second battery and back cover!)
But im annoyed to see that this new one still has the sticky slide to unlock. I know there are some apps i can use to get round it, but it seems a bit odd for such a device to make it hard to answer calls!!
Anyone know why this happens, is it a hardware thing or is it the rom?
Or any advice what i can do, its on contrat from o2, anything i can do?
Thanks
Click to expand...
Click to collapse
i had the same problem with the sticky slide to unlock, i'm on the o2 2.1 release, i fixed it by rooting the device and editing the build.prop file. look for build.prop under system, search inside and find "debug.sf.hw=0" and change to "debug.sf.hw=1" ...no more sticky slide to unlock
if your on 1.6, you might want to try the same.
i had the same problem with the sticky slide to unlock, i'm on the o2 2.1 release, i fixed it by rooting the device and editing the build.prop file. look for build.prop under system, search inside and find "debug.sf.hw=0" and change to "debug.sf.hw=1" ...no more sticky slide to unlock
if your on 1.6, you might want to try the same.
Click to expand...
Click to collapse
_________________________________________________________________________________________________________________________________
I sometimes have the sticky slide to unlock problem, I'm on Stephen Hyde's 2.2 has anybody tried this, editing the build.prop file, for the 2.2
hmm... seems i am not alone. I have encountered exactly the same problem. the top bar of screen become sticky after i keep the device in the back pocket.
i am going back to the O2 shop and try to get it fixed or exchanged...
the conclusion is ---never keep it in the back pocket!?
FWIW. i had the same problem. Took my screen protector off it hasn't happened since then although im still curious as to why i never had this problem with 1.6. Lets just hope its resolved in 2.2 then i can put another screen protector on
Sent from my Dell Streak using XDA App
my one is on 2.1. no protector on at all.
i just return it to the O2 shop. the guy told me they need to return it for repair.
i just wondering how will they repair it??? Hope i will get another brand new device from them at the end. Or get it fixed without charging me anything...
need to wait for maximum 10 days for a call from the shop...
Mine was in for 'repair' I got it back one week after putting it in, it was a different phone.
But it's still just the same.
I'm going into o2 tomorrow to see what I can do, I'm going to try to change it for a different phone, maybe a hd7
Just root your phone and follow the steps above to edit your build.prop
U can unroot the phone when your done if you choose
ipguy said:
Just root your phone and follow the steps above to edit your build.prop
U can unroot the phone when your done if you choose
Click to expand...
Click to collapse
what is the rational behind it? why have to make the change? why it work before without the change?
i will ask for model change as well if the problem can't be fixed by O2.
1.6 has the option enabled.
2.1 and 2.2 don't
By enabling the option android will use the phones GPU for graphic nit its CPU
Well I don't agree with the pocket thing. When I was on 1.6 never had issue with it being in pocket. When went to 2.1 is when it all started. 2.1 was horrible with 2.2 being slightly better. As far as editing build prop mine is already set to 1 not 0 so that must not be the problem either. Has to be something in the code somewhere or 1.6 would have had same issue.
I just thought id update this with what's going on now.
I went up to the o2 store in Glasgow and spoke with them, they told me to ring customer services so that they could escalate my problem, when i phoned they told me that the stare has to do it. So I handed my phone to the guy in the o2 shop.
The short of it is that the only way forward (unless i want my 4th streak!) was to put a complaint in and the store manager will 'look into it'
One interesting point is that two of the staff told me that its a known fault!! Dell have admitted there is problem, of course o2 blamed dells software until I said that I was using the o2 2.1 rom (the guy quickly changed the subject)
I will be paying them a visit on Monday again.
Here is my update: after 3 days including weekend, I got my replacement back. it's a new one. Which make me believe DELL didn't spend anytime for repair. Seems they just replace it for me straightaway. I agree that 'it's known issue for DELL'
I got extra back cover and battery!
the ROM version is 1.6 which disapoint me a little bit. offical 2.2 is coming anyway...I will hold my horse for the upgrade this time. just to rule out the rom issue.
1.6 has the option enabled.
2.1 and 2.2 don't
By enabling the option android will use the phones GPU for graphic nit its CPU
Click to expand...
Click to collapse
Is this in reference to the debug.sf.hw...?
...Wouldn't you WANT the GPU for graphics, and NOT the CPU...?
Isn't that the purpose of the GPU...?
I'm on 2.2, enabled debug.sf.hw and the issue is resolved.
No sticky slider. No side affects. No performance change.
...untill I hear a valid reason...it stays
ipguy said:
i had the same problem with the sticky slide to unlock, i'm on the o2 2.1 release, i fixed it by rooting the device and editing the build.prop file. look for build.prop under system, search inside and find "debug.sf.hw=0" and change to "debug.sf.hw=1" ...no more sticky slide to unlock
if your on 1.6, you might want to try the same.
Click to expand...
Click to collapse
the crap did that do? its fixed more than the issue with my sticky slide to unlock. i had an issue when a dialog would make that fadey background thing, the phone would slow down horrifically but this fixed that. im quite happy now, knowing not what that actually fixes.
There seems to be more to the problem
After weeks of faultless operation, I started noticing a sticky slider again, also weird touch screen behaviour
After clearing all caches and restarting the phone, I'm all good again.
I think 2.1 was just hobbled together
Bring on 2.2