Database Users

Broken HD2

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

Need help with Proximity Sensor Problem

I open a new thread because those already opened are quite dead... the subject is the proximity sensor on the HTC HD2... as i described in oter places this is the behaviour:
Upon receiving calls ALL works as it should
Sometimes when making a call:
1. dial a number
2. press talk
3. take the phone to my ear
4. the screen turns off
5. it starts ringing
6. THE SCREEN GOES ON
7. take the phone from my ear and put it back
8. the screen goes off
9. it answers on the other side
10. THE SCREEN GOES ON
11. take the phone from my ear and put it back
12. the screen goes off and all works well from now on on this call
I have at least a number that EVERYTIME when called does not acts like this... the proximity sensor does its job very well
I have at least one numbet that almost always did the steps described from 1to 12... only 4-5 times it didn't
If i get a busy tone the screen turns on... it will turn of if i do step 7
I've put back original rom and i have the same behaviour. I tried with clean roms and noting installed... still the same...
One time on a clean rom... I called a number that always did that and the first two calls were ok, after that it started again...
Now I'm using Hyper ROM 8.0 and I see that after step 6 if i keep the phone to my ear th screen will turn itself off after a sec or so... i cannot say right now if always...
Considering that this does not happens to many of us and it is not something permanent I think it can have something to do with the network... I don't know exactly what but this is my guess; like in the moments the screen turns on maybe the networks sends out a "signal" like the call would be over... I know it sounds weird but I don't know what else to think...
I even attached a poll to see who gets this behaviour...
So, to all the CHEFS out there... please help.... because HTC is not willing to... they're answer was not helping at all...

This is weird... I use netDrg's 2.5g ROM and I have no issue with the proximity sensor. Sometimes, when receiving a call, if I rotate the phone from portrait to landscape and then immediately take it to my ear, the screen doesn't turn off, but as soon as the display is back to portrait mode, it turns off. This isn't annoying at all, since I rarely pick up the phone and hold it in landscape to talk !
Maybe you should try a different ROM ? If you understand French well, netDrg's ROM is quite good, although it seems to me that the battery drains faster than with the stock ROM...

french is fine.. actually i would learn any language just to have this fixed... i know about landscape and sensor not working... but it is not the case here
it happens so aleatory... i would think it is a hardware issue... BUT i have one number and with it, this NEVER happened
i had almost all the cleanex suite... touch-x, energy and others... i really can't remeber if this happend since the first day i bought it... i've put back the stock rom downloaded from htc and still the same...

ok... i've made like 15-20 calls to the same number and all worked as it should... than all of a sudden it started to do what i've described in first post... just like this... i'm starting to hate this phone...

it looks like i'm not the only one with this issue... how you guys got it solved?..

just a thought... what triggers the screen on on this phone... i know that some apps open the screen... maybe there is a registry tweak to keep the screen off if proximity detected... this should be done automaticly i know... the fact is that the proximity sensor works...

uhm, just to point it out, you should edit your post instead of posting 4 messages in a row in the same thread
Anyway, this is the exact same problem I noticed reported in another thread, and I didn't have it, I mostly receive and rarely call, yet the few times I called I don't seem to remember such problems, will try and remember to test with my other mobile when I get back home.

today i went back to default rom that came with my phone...
RUU_Leo_HTC_WWE_EastEurope_1.48.479.1_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship
and still it does the same
i HSPL again and than put
RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
the same thing
if I call my home landline it works perfectly... if i call one of the numbers i was telling you about it acts like described in post #1
one other thing i discovered though... with the original roms there is a courtain over the buttons on the phone canvas... this not only blocks aditional buttons on the screen but also blocks the top taskbar... wich is a goos thing
anyway for a 4-500 euros phone this thing i'm having shouldn't happen...
still searching... i've seens something with Rilphone.dll... can this make a difference?
LE: Rilphone.dll broke thephone module... hard reset...

Same here ccezar
I only realised in the last couple of weeks that I've hung up on people a few times & sometimes I've tried making the same call on the spot like 5 times in a row & the line has been cut off before it evens rings, which brings me to say that different behaviours on different calling numbers is just a coincidence.
Sort of experimenting at the moment, I think that when I dial, & put the phone to my ear slowly it works. i can see the screen turn off, & the call goes smoothly. Although after I've hung up sometimes the comm manager or arkswitch is on my screen, which only mean that the taskbar is still active...
I almost thought that the screen may have been switching off but the touch function was still there at least for a few more seconds...
There are hundreds(thousands maybe) of us HD2 owners out there, so my feeling is that if there ain't many complaints, it may aswell be a faulty device.
Then again I wonder if that phone canvs slider would make a diference? Anyone know if there's cab for this?

What radio you using
The more I think about it the more I'm convinced that the 2.10.... radios is the culprit for me.
I just flashed my old 2.07.50.27_2 radio, will test for a day or so and see what happens.
If your on a 2.10.50.. radio urself or anyone with the same prob and radio, can I suggest you downgrade to a 2.07 or 2.08/ or 2.09 for euros?

i thought also that it is radio raleted... i tried other radios and still the same...
anyway i don't think it is hardware related... because i have at least one number that never ever got this behaviour... and neither when calling landlines... it is only on some numbers on mobile networks... and i have numbers that get this behaviour only from time to time...
so... how does the proximity sensor works?... when in a call (there is a reg key that appears upon making a call and says activecallcount=1) the proximity sensor activates... if something in the way it turns the screen off... if the call ends the proximity sensor is deactivated... this is where i dont have exact facts... like if i keep the phone to my ear if it will remain with the screen off or once the call ended the screen goes on... i'd go for the second one...
so... my belief is that is has to do with network parameters... you make the call and on steps 5 and 9 from first post i think the phone belives that the call is over... and i guess the network sends a signal that triggers that... i know it sounds like a fairytale...
now i will try to find a sim card from another mobile operator and see if it does the same... i already tried with another seem from my operator and there is no change... maybe if i try a different sim type (there are simple and 3G sims - i have a simple one)
i'll keep digging... anyway... at least one mobile number and all landlines numbers this NEVER HAPPENED...

well that just makes sense ccezar. I'll do the same over the weekend & see what happens.
with another providers sim card that is.
Hey when say you tried with nothing installed, was cookie's hometab on the rom? just a thought

i don't think so... because i also tried with a stock original rom...
LE: i just realized that my phone is network locked... how can i unlock it?

ccezar2004 said:
i don't think so... because i also tried with a stock original rom...
LE: i just realized that my phone is network locked... how can i unlock it?
Click to expand...
Click to collapse
I couldn't tell ya, I can suggest that if you're on a contract your paying for the phone anyway, so you should be able to ring the phone op & ask them for the codes. Where I am, the only time I couldn't have it unlocked is if it was pre paid & less than 12 months old.

after long debates that's the conclusion of HTC
The only option that is left now is to send the device to the Repair Centre so the engineers could examine it. Your device is still under the warranty. But after the diagnosis the engineers will determine whether the fault of the unit is due to misusage, accidental damage or a manufactured fault. Before proceeding with the repair you’ll be notified with the cost of the repair, if it is an out of warranty case. Kindly note that your phone has a global warranty, which means if you have any issues with the phone and would like to get it examined (repaired) it will be through one of our global repair centers Please follow the link below for information about those repair centers. http://www.htc.com/uk/CA_Hotline.aspx?region=GWS Bear in mind as well that if you have European warranty, you’ll be able to repair your phone in any official repair centre in the European Union. Thank you for using HTC products. Please contact us again if you have any questions. Best Regards, HTC Team
Click to expand...
Click to collapse
bummer

Dead camera on every rom....

I for the life of me cant figure out why my camera is completely dead! I have FULLY wiped all caches,everything under 'WIPE' via AMONS and even formatted my SD card as well as trying an alternate SD card(both 8GB--C6speed)--never had a problem w either card on ANY ROM...ALL OF A SUDDEN the past 2days my camera goes to a FULL BLACK SCREEN,when pressing the CAMERA icon. Occasionally the taskbar will remain uptop but will timeout when screen display shutsoff. Now if i launch CAMERA via DESIRE ROM(KING),ill get the notice about clicking trackball to resume camera but as soon as i click it,the message dissapears and the screen will go back to black screen again...and repeat. I SWEAR i have DONE MULTIPLE COMPLETE WIPES AND REFORMATS so im left to believe its THE HARDWARE itself! CAN ANYBODY PLEASE LEND ME A HAND IF the similar problemhas occured...On the Nandroid backups that ive restored from FULLY FUNCTIONING bkups,if i launch NEXUS TORCH it will say CANNOT ACCESS LED---this is THE ONLY info besides the "camera wake message"mentioned earlier that i can provide. Thanks in advance and pleas edont flame for NOT being in Q&A bc this is more of a DEV related restore question.
**oh and BTW--I DID TRY TO INSTALL the DESIRE R2 cam fix and does nothing. I tried it when all was working fine early in the week and it did nothing to help FLASH timing for me,so i NAN restored back to prior state and CAMERA continued working until about THURSDAY night--regardless--PHONE is in OUT OF BOX STATE--MINUS UNLOCKED and it STILL doesnt work!---PEACE and Happy Mothers Day to any Mothers out there in XDA world!

***Captain Obvious to the Rescue!!***
Your hardware has malfunctioned. Contact HTC for a repair.

1. you may have a broken camera, try a stock rom
2. your caps lock button is definitely broken
3. you posted in the wrong section

ghostrida said:
1. you may have a broken camera, try a stock rom
2. your caps lock button is definitely broken
3. you posted in the wrong section
Click to expand...
Click to collapse
1. i should have known you were from Philly and cant read--I TRIED STOCK ROM
2. CAPS is to put highlights on key terms so idiots dont read over the fact that I DID TRY STOCK ROM---see how that helps?
3. Thanks for your informative responses---any suggestions from CAPTAIN OBVIOUS how to get service on a ROOTED device without being charged full price on the phone?? Ahhh--thought not!--So i tried here to see if anyone else had similar situation. AGAIN-thanks for your help as well SERIAL TOON--geez

If it's a hardware failure they won't charge you.

I think it will help if you go through Google Cust service first...they will end up redirecting you to HTC repair. Provide all truthful information on your issue, proving that you have done some legitimate trouble shooting and they will realize that it is a hardware issue, not the ROM flashing or bootloader unlocking that caused the problem. Someone else on the xda forums had a rooted phone with bluetooth problem and was able to send to HTC for repair for free...with a 4 day turnaround!
Good luck!

What do you base this on...Heresay?
BlueScreenJunky said:
If it's a hardware failure they won't charge you.
Click to expand...
Click to collapse
I didnt intend to sound rude,im just a little pissed right now..I Only ask bc i already had an issue in January days after receipt of phone. Issue was solved by sending me a new battery bc other was causing random shutdowns (ive since forwarded this info to another XDAmember that had exact same issue and they give him replacement phone at 1st but issue continued to occur--i told him about my story after he posted his problem, he contacted them this weekend and confirmed with me today that a new battery was on the way..see my public IM's for info). Anyway,when i was dealing with the battery issue they said they would definately NOT be able to fix under warranty bc the phone is rooted and unlocked. I can attest to the few people on here that said theyve been successful in such cases,but either way,IVE ALREADY STATED that i tried the DESIRE R2 camera kernal to see if that helps,so im not going to be dishonest and tell them i havent tried anything other than custom roms. Again..positive suggestions or similar experiences with warranty info would be appreciated....trollers looking for a funny post or to degrade people can eat one!

joshlusignan said:
I think it will help if you go through Google Cust service first...they will end up redirecting you to HTC repair. Provide all truthful information on your issue, proving that you have done some legitimate trouble shooting and they will realize that it is a hardware issue, not the ROM flashing or bootloader unlocking that caused the problem. Someone else on the xda forums had a rooted phone with bluetooth problem and was able to send to HTC for repair for free...with a 4 day turnaround!
Good luck!
Click to expand...
Click to collapse
Thanks JOSH, ill look into it tommorrow--as i stated tho--i feel im being dishonest for trying the DESIRE R2 cam and saying that they should cover it---uninformed people will assume THAT couldve caused it,even though i used phone afterwards for a few days w no side effects

Hey Milton, like others have mentioned in here might want to try flash back to stock and seeing if the problem persists. If it does then your looking at a hardware problem and you should contact HTC/google for repair.

Yea...i was thinking that from get go--(hardware prob). Im on cheesy STOCK ROM right now and have been for cpl hrs...but its obvious its gotta be hardware...NOW comes the crappy part of trying to explain it to HTC when attempting to get an RMA!--Yee Haa!

MOD PLEASE CLOSE OR DELETE---THANKS!

Milton, among the items on the very small list of things folks around here want in return for helping you is that you lay off the caps. Doesn't highlight anything that you'd want to highlight.
Doug

Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...

milton007 said:
Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...
Click to expand...
Click to collapse
That seriously hurts my eyes to look at. Try using proper punctuation and grammar. It's very simple and still gets your point across.
As for your phone. Call Google which will probably have you call HTC. People have gotten their rooted devices fixed for free if it's a genuine hardware problem and nothing caused from the rooting process.

milton007 said:
Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...
Click to expand...
Click to collapse
You should send it to HTC for repair. Charging fee or not, but thats the only option to you right now because its a hardware failure.

mikroN1 said:
That seriously hurts my eyes to look at. Try using proper punctuation and grammar. It's very simple and still gets your point across.
Click to expand...
Click to collapse
I was thinking the exact same thing, don't know where he must have learned how to type. Then you criticize people from Philly, or whatever its called somewhere, for not knowing how to read. I would say mirror that advice and learn how to type.. type properly.

Torch will work until camera app is used then it wont work again until i reboot. After reboot, torch will work ONLY on regular/lower setting. MAX brightness will not work. Toggle back to LOW setting and torch will work again. Im going to try what DOUG suggested bc that is the only thing i havent tried yet...but the way torch and camera are acting up and requiring reboots keeps me willing to try software tricks first...WHAT ties the TORCH's HI setting to the camera app adn yet keeps the LOW setting seperate!??..ill try the TORCH dev real quick for some insight on how the two work hand in hand.Thanks for anyone using their time to help instead of criticize. Sorry for mocking ones ability to read but i was quite [email protected] time bc i lost a major function on my phone.My apologies to all

Seriously Milton? More?
milton007 said:
Please DONT lend assistance to someone like this. IF they cant bither to read THE MOST SIMPLEST instructions, they should NOT be attempting this in the first place...thats just sheer ignorance...
Click to expand...
Click to collapse
The attitude, hostility and the caps are not welcome here.

Along with the others I have no sympathy for you. Learn proper grammar and get a better attitude.

Troll much? Go tell your mother happy mothers day if you have that much time to pull up old posts from people asking questions in a 'kernal forum' about basics. Basics that anyone should know, if not they stand a much better chance on damging their phone. It wasnt being ignorant. Since you know everything there is to know about everyones posts, tell me where the topic dealing with my specific camera issue has been previously posted and ill be glad to read and search thru that forum. I wasnt the one asking questions about something mentioned in the OP (uh oh i used caps--oh geesh-someones gonna be saaad now!)and numerous pages before. Im sorry i dont spend all my life on forums to know that only words approved for caps are indeed CAPITALIZED. Petty little boy-and by the way, i was trying to stress your good advice by typing your name in caps so people would credit you with the help-Sorry to have taken your precious time sir. Good day.

[Q] Sticky slide to unlock (again) advice?

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

Proximity sensor faulty galaxy s gti9000

Does anyone know of a way to remove the proximity sensor drivers or shut it off completely my screen just goes black during a call and i need to use the keypad during calls i have tried all the proximity apps on market and it has no effect, have tried calibration etc odin firmware updates to the point i killed my phone just got it back from repair and was told it needs a new chip to rectify the problem.
I have spent weeks going through forums for a solution and i know on my brothers sgs 2 it has a setting in the menu to turn it off.
This seems to be a common problem with no resolve so im looking for someone to resolve this problem and make alot of people happy.
We all no As these phones age this will be more and more common.
Techies get ur teeth into this or even software writers make An app n earn some cash,
This would b a great ego booster for someone to say i solved that when no one in the world could.
Thanks...........looney
Sent from my GT-I9000

Maybe this sounds stupid but why don't you just press the home button while you call. Screen will turn on again and you can access keypad or speaker or whatever. This takes only seconds...
Sry when I understood you wrong...
Greetz
Gesendet von meinem GT-I9000 mit Tapatalk

The common keypad when using phone is phone-keypad... *#0-9
Never tried other keyboard to send DTMF signals :\
Thx for reading, press THANKS if u like

if your phone screen goes black but does not become visible again when you move the phone from head (proximity sensor got two states 1 and 0) you either have badly flashed firmware or faulty sensor. for the first you can try reflshing to LATEST (unrooted) stock firmware from samsung and then checking again if your bug persist but for second only thing you can do is to return phone on warranty to service center.
anyways no app is needed for that. should work without any.

Hi thanks for the suggestions phone is in a crash state until force close happens so force close won't work pressing the home key or any other for that matter.
As like many i brought my phone second hand and although i have loads of Samsung kit registered with them Im an engineer and look to solve things in the future when warranties have long expired.
Thanks for the reply though monk.
I have googled the problem and i don't seem to be the only person with the fault.
Someone has written an app to kill drivers but don't know where the driver is for the proxy and its a new program with hardly any testing done so not sure if it will have any other adverse effects and killed my phone once already that's why Im asking more expert advice as Im fairly new to android os.
Sent from my GT-I9000 using XDA App

Got the details from my bro the stock he has wich turns it off is
base xxke4
build xwke7
build xwke7
But that's on a galaxy s 2 gti9100 if someone can find identical software that works on the g1 i9000
Sent from my GT-I9000 using XDA App