Database Develop

Accelerometer stuck

I've had my Diamond for a couple of weeks and the accelerometer has worked normally until now. But now it seems to have stuck - in Teeter, the ball is fixed in the upper left corner and will not move, and apps like Opera and the photo viewer does not react to rotating the phone anymore. I've used the cool Sushi Profile Switcher v.0.2 (http://forum.xda-developers.com/showthread.php?t=406769) and have
shaken the phone a lot. Has anyone experienced anything similar? Is it possible that I've physically broken the g-sensor? - I've hard-reset the phone but it didn't help.
Thanks in advance for any answers
Jon

Use the Bubble level program which visualizes the angle of your phone. It offers the ability to calibrate the phone. Maybe it helps.
You can find the program here: http://forum.xda-developers.com/showthread.php?t=408056&highlight=bubble+level
Maybe there is a reason that HTC didn't build in a profile shaker... that would be something :|

205_lacoste said:
It offers the ability to calibrate the phone.
Click to expand...
Click to collapse
That's not true. it only calibrates it in the app itself. As soon as you leave the app, your gsensor has the same calibration as before.

Thanks for the suggestion - I installed the BubbleLevel program, and allthough it didn't solve the problem, but I think it does give a hint that it might just (hopefully) be a matter of calibration. The green blob doesn't move at all, but the degree number in the top changes from 71,5 when the phone is flat on the table to 90 in vertical position, so movements are still registered.

Could it be that one of the axis the sensors measure is broken?
Come to think of it...: Even though it isn't calibrated, it should work no matter what. If it's calibrated wrong the axis still should register movement in any direction. The only thing wrong would be the read-out compared to the horizon.
I'm affraid that something is physically wrong with the device
Does the 'shake app' still work, or isn't it? Maybe there is a difference in sensing shocks (g's) and the angle sensors.
Probably there is another app, but I wouldn't know one other at the moment: The light sabre applet has a 'debug' feature from which you can see if G's are measured along the axis. Should give an indication too...
kkempe said:
That's not true. it only calibrates it in the app itself. As soon as you leave the app, your gsensor has the same calibration as before.
Click to expand...
Click to collapse
Didn't know that Thanks for the heads up!

Did you try a hard reset? I presume soft reset has been made?
Maybe the drivers are just f*** up

Riel said:
Did you try a hard reset? I presume soft reset has been made?
Maybe the drivers are just f*** up
Click to expand...
Click to collapse
Read the first post and you'll see he did...

Riel said:
Did you try a hard reset? I presume soft reset has been made?
Maybe the drivers are just f*** up
Click to expand...
Click to collapse
he posted in the very first post that hard reset did not help

Ah, I see.

Warranty? do you have?

at least you are not alone with your problem - i do have it oo

CujoEgan12345 said:
I've hard-reset the phone but it didn't help.
Click to expand...
Click to collapse
I don’t want to sound condescending, but do you know what a hard reset is?
It's not simply removing and replacing your battery!
http://forum.xda-developers.com/showpost.php?p=2332732&postcount=1

I do not understand what is the problem .. to play whit the diamond you keep diamond to the hand and not on the table no?? also tends in my hand a little, but I have no problem playing ...
Ric

the problem is, that a broken G-Sensor does not even allow you to play Teeter. When you open opera, it stays in landscape mode as the device "thinks" it's turned sideways

imranbashir_uk said:
I don’t want to sound condescending, but do you know what a hard reset is?
It's not simply removing and replacing your battery!
http://forum.xda-developers.com/showpost.php?p=2332732&postcount=1
Click to expand...
Click to collapse
I know, unfortunately I did hard reset the way described in the guide, but the sensor is still not working.
I've also made a simple little test-application using the g-sensor api described here: http://forum.xda-developers.com/showthread.php?p=2381034
Running this on my Diamond shows that movement on the x-axis is not registered at all, movement on the y-axis only shows very small changes, while movement on the z-axis seems to be registered fine. I guess this suggests that the g-sensor is actually broken

Bäcker said:
at least you are not alone with your problem - i do have it oo
Click to expand...
Click to collapse
Hi Bäcker
So did your sensor also work for a while until appearently broken? And did you by any chance also 'shake' your unit quite a lot before it happened?

it worked fine, now it does work, but its drasticly registering negative X axis data
So teeter can't be used and it flips opera/album on it's own
i did not shake it but a relative's kid (5yrs) dropped it on the carpet - which might be the reason

Just get it replaced under warranty

Me too
I have exactly the same issue.
I dropped the phone once - on a soft surface, no scratches or external damange but...
Teeter Game - ball only rolls on one axis, otherwise stuck at top of scree.
No Rotation in Opera or Camera
Camera, after taking photos and then viewing them in the viewer the are presented upside down and can not be rotated.
I've done a hard reset twice with no resolution.
Contacted HTC. they said that since it's past the 30 since order date the best they can do is have me send the phone in for repair - no replacement.
My main concern now is that since this seems to be a problem others are having too from similar 'small knocks' is it even worth sending back for repair. At this rate all owners will soon be facing the same issue.

MasterOfDesasters said:
That's not true. it only calibrates it in the app itself. As soon as you leave the app, your gsensor has the same calibration as before.
Click to expand...
Click to collapse
Is that why my teeter ball changes its habits depending on how I calibrate the sensor? Oh okay.
Download the calibration tool stripped from the Raphael.

Can't Tap Screen

I've searched and could not find an answer. So I'll just start a new thread.
No matter what radio I use, no matter what ROM I flash, I cannot get my screen to respond to taps.
It was responding to manual buttons but no touch. I flashed to a new ROM hoping that would fix it, but now I can't even past the calibration screen...
This all just happened suddenly too. I have been using an iphone for the past couple of months so I have not been too concerned. However I wanted to use my kaisar as a modem at an offsite sales event but it's still the same....
Probly been asked a few times, but I took the plunge away....
Flame or answer away....

Just flash ur shipped ROM & see if it can back to normal again. If not, just return for warranty or repair.

have you updated your HardSPL?
if you have spl1.0 with the wm6.1 installed, these problems are common.

hang.tuah said:
Just flash ur shipped ROM & see if it can back to normal again. If not, just return for warranty or repair.
Click to expand...
Click to collapse
That may work. But I'd rather not downgrade to 6.0 if that is not the problem. Plus I have no valid warranty. ATT Tilt is from the United States and I live in Canada...
ccaparli said:
have you updated your HardSPL?
if you have spl1.0 with the wm6.1 installed, these problems are common.
Click to expand...
Click to collapse
I have tried 2-3 Hard SPL's.
I suspect that it has something to do with the Hyperdragon 3 Diamond ROM. All my problems started when I flashed that paticular ROM.
I will try downgrading to 6.0 and see if that does the trick. I somehow doubt it though. I think that this may need another, trickier remedy, ie: unbricking a bricked PPC.
I was sort hoping that this was a more common problem and advice would be more readily available...

So I downgraded to the original ROM, but still the same problem. Perhaps if I also downgrade the SPL. Does anyone have this file?
Btw, though I am not a developer or anything I have been flashing ROM's for awhile.
This problem just came out of nowhere...

bump...............

This should help:
http://forum.xda-developers.com/showthread.php?t=334679
Also, make sure you run JumpSPL/SSPL-KAIS in order to successfully change the SPL.

KMFM$ said:
This should help:
http://forum.xda-developers.com/showthread.php?t=334679
Also, make sure you run JumpSPL/SSPL-KAIS in order to successfully change the SPL.
Click to expand...
Click to collapse
Ya, I forgot about that thread. I haven't used that since I upgraded my spl to Hard3.28. I can understand why I would get problems with the RESTORED STOCK ROM that I flashed my device wouldn't work with the latest Hard SPL, but why would this occur with a ROM it was supposed to work with.
This wasn't something that happened after I flashed, it just happened out of nowhere... They key to fixing this understanding WHY. it may or may not be the SPL...

last bump...

jzalapski said:
last bump...
Click to expand...
Click to collapse
After you flash a rom or hard reset, are you able to get past the screen calibration?

Look here It will not fix the problem, but at least it will let you to bypass the "aligment screen"

liquidfork said:
After you flash a rom or hard reset, are you able to get past the screen calibration?
Click to expand...
Click to collapse
No. I figured the problem had something to do with the SW, so I just flashed figuring that would fix it, but now it's basically useless (not like I'm using it right now anyway, but)...

timurg said:
Look here It will not fix the problem, but at least it will let you to bypass the "aligment screen"
Click to expand...
Click to collapse
Thank you. I will try that when I have time later. I'm not sure what it is yet, but I'm sure it will work...

jzalapski said:
Thank you. I will try that when I have time later. I'm not sure what it is yet, but I'm sure it will work...
Click to expand...
Click to collapse
hehe, just create an empty file "welcome.not" in the root of SD card and ... PROFIT!

timurg said:
hehe, just create an empty file "welcome.not" in the root of SD card and ... PROFIT!
Click to expand...
Click to collapse
step 1: Create File on SD Card
step 2: ...
step 3: Profit

I had a similar problem on my trinity. It was an hardware problem, a spoiled thin strip that is between the LCD and front cover. As someone told me that
send it to warranty would take a long time to get it back I replaced myself the strip and now is working...

It's probably a hardware issue. You will have to replace your LCD+Touchscreen and if that doesn't work, you'll have to replace the flex that connects the LCD with the motherboard itself.
I fixed a TILT with that problem. I ended up buyina a new LCD when the problem was caused by the flex
PS, LCD screen is way cheaper than the flex.

Hey. So it looks like I did buy a replacement warranty. So I took it to my guy and he said that he would just replace it. He asked if I wanted the same one or if I wanted to pay the difference and get a new one....
I paid an extra $250 and got a diamond...
Problem Solved.... See you in the Diamond Section...

had same problem - which i solved by dissasembling and putting few paper pieces under the screen to make a good fit of screen inside the housing - and it helped - touhscreen works fine

maxxis said:
had same problem - which i solved by dissasembling and putting few paper pieces under the screen to make a good fit of screen inside the housing - and it helped - touhscreen works fine
Click to expand...
Click to collapse
I had a similar problem with a Wizard and it turned out to be a bit of dirt that was stuck under the screen on one corner, resulting in constant contact that prevented the device from registering my taps. I removed the screen and cleaned it thoroughly to fix.
Also try "rubbing" the screen in each direction with both thumbs to see if you can slide the screen around and dislodge any dirt from the edges. The screen will move around slightly under the case without damaging the device.

Help me please, dead tytn2 :(

Hello guys, i really need your help!
My phone is so strange now, i have been using Ultimate-X.V9 -21054, but in last days, my phone has gone to white screen some times when i press to screen up sometimes everything is fine, but others not and my phone sometimes dont respond to my touch, and sometimes is a bit slow
Now i have flashed to RUU_Kaiser_HTC_PTG_3.28.410.0_radio_sign_25.83.40.02_1.65.17.56_Ship, during the upgrade my phone stay on tree colors, but on computer appeared the status bar! and everythime i turn on my phone now is like 90% is allways white :O i have open my phone, and reconected all again, but the problem still there! im using 3.34 hard spl!
Please someone help meee... i really love my tytn2 is there any way to put this fine? its hard spl problem?
Please help me

Please help meee My phone now is more slow than normal :/

That happened to me a while back, I took it apart several times and checked connections etc. but that did not fix it. I ended up buying a new LCD off of ebay which fixed it perfectly. So, I would suggest doing that (I bought one for 15USD used).

But this to me seems to be a problem on the main board, because the phone sometimes gets really slows And sometimes that white problem appears and others not, like 90% when i need to use my phone

Flash Stock ROM?
Did you flash if back to a OEM ROM? Did it work OK if you left it on the OEM ROM? I have used "Kaiser_HTC_ASIA_HK_WWE_3.34.721.2" as a OEM to upgrade from on many phones that I had upgrade issues with.

i think RUU_Kaiser_HTC_PTG_3.28.410.0_radio_sign_25.83.40. 02_1.65.17.56_Ship is an OEM rom isnt? :x

P4k1t0 said:
Hello guys, i really need your help!
My phone is so strange now, i have been using Ultimate-X.V9 -21054, but in last days, my phone has gone to white screen some times when i press to screen up sometimes everything is fine, but others not and my phone sometimes dont respond to my touch, and sometimes is a bit slow
Now i have flashed to RUU_Kaiser_HTC_PTG_3.28.410.0_radio_sign_25.83.40.02_1.65.17.56_Ship, during the upgrade my phone stay on tree colors, but on computer appeared the status bar! and everythime i turn on my phone now is like 90% is allways white :O i have open my phone, and reconected all again, but the problem still there! im using 3.34 hard spl!
Please someone help meee... i really love my tytn2 is there any way to put this fine? its hard spl problem?
Please help me
Click to expand...
Click to collapse
did you ask in the proper thread before starting a new one?

msd24200 said:
did you ask in the proper thread before starting a new one?
Click to expand...
Click to collapse
Lolol? and what is the proper thread? --' dont you see this is any rooms i have tried?

P4k1t0 said:
Lolol? and what is the proper thread? --' dont you see this is any rooms i have tried?
Click to expand...
Click to collapse
noticed when searching all your post that you went straight to starting a new thread for this instead of asking in on of the flashing threads. http://forum.xda-developers.com/showthread.php?t=533976

Dude, and in what that link will help in my problem? if search on it, you will find the solution to my problem? the answer is NO, maybe you should read a bit better!

P4k1t0 said:
Dude, and in what that link will help in my problem? if search on it, you will find the solution to my problem? the answer is NO, maybe you should read a bit better!
Click to expand...
Click to collapse
dude the answer is yes go ask in the flashing for newbs thread, or one of the other great links in the thread i posted. maybe you should read better the rules about starting new threads because you are having a flash related problem that needs to be asked in a thread already setup to deal with flash related matters instead of starting a new thread.
have you tried pushing the hard buttons to get into bootloader? do you think MTTY may help your current problem?

msd24200 said:
dude the answer is yes go ask in the flashing for newbs thread, or one of the other great links in the thread i posted. maybe you should read better the rules about starting new threads because you are having a flash related problem that needs to be asked in a thread already setup to deal with flash related matters instead of starting a new thread.
have you tried pushing the hard buttons to get into bootloader? do you think MTTY may help your current problem?
Click to expand...
Click to collapse
Dude i can enter on bootloader yes, can i use my phone yes! but the problem is that sometimes (i mean, like all the time) the screen stay white when i turn it on, and the phone stays slow!!!!

jsgjm said:
Did you flash if back to a OEM ROM? Did it work OK if you left it on the OEM ROM? I have used "Kaiser_HTC_ASIA_HK_WWE_3.34.721.2" as a OEM to upgrade from on many phones that I had upgrade issues with.
Click to expand...
Click to collapse
i have tried that rom too, but nothing the problem is here

It sounds like your Screen is on the way out. I would replace it.
No lets play nice. Or Ill break out the fish heads lol

zelendel said:
It sounds like your Screen is on the way out. I would replace it.
No lets play nice. Or Ill break out the fish heads lol
Click to expand...
Click to collapse
Well, if is about the screen, i can say im safe :x
But one thing on my mind, the white screen i could say to change the screen to one new, but the problem is the kaiser stay a bit slow, and sometimes it dont respond to what i want!
With that stay thinking that the problem is about the mainboard or something like that :s but i hope the problem is the screen, i will buy a new on ebay

The ribbon cable for the digitizer (touch screen) attaches to the LCD, and then both signals feed through the same cable into the D-pad board, so its possible that there is a bad connection somewhere in the LCD/Digitizer assembly that causes it to not sense your inputs, even when the LCD itself is working. Mine just failed completely to a white screen and did not come back. It could be something besides the LCD..try flashing a new HardSPL and/or a different ROM, but if I had to bet, I would bet on the LCD.

zelendel said:
No lets play nice. Or Ill break out the fish heads lol
Click to expand...
Click to collapse
Thankyou made me chuckle

P4k1t0, I know you're frustrated that you phone doesnt work, but do not get uppity at the other forum posters. If you sound off against msd24200 and a mod sees it, its likely to lock your topic.

i had the same situation two weeks back after i flash with my own cooked rom.
what i did is flash the stock rom through SD/storage card and everything is fine.
you already try this method ? you can search on how to flash from SD/storage card

to flash by sd card? ok ok i will try it right now to see

Hardware experts, I need your help! :(

Ok, so I searched the forums and the internet in general via Google, but didnt' find anything that specifically matched the issue that I'm having.
I'm wondering what part that I need to replace or what I need to do to get my trackball and touchscreen back working reliably.
My G1's touchscreen is only accurate about 20% of the time. THe other 80% it either does not work at all or misreads my fingers are being somewhere else on the screen. It also performs long presses while not being touched at all (SOOO ANNOYING).
I would say that the digitizer simply needs to be replaced, but I have found that it can be temporarily fixed by going into recovery and wiping the cache. It'll work for 20 or so minutes perfectly after that but will go back into crazy mode and p*ss me off no end.
Also, the trackball will mistrack or not track at all sometimes, even in the recovery screen.
The phone has not be immersed in water but has been in the bathroom with me while showering. I saw a thread where it was reccommended that a blow dryer be employed to remove any condensation that might be trapped inside the phone, but I'm not sure what I have to remove or what tempature I should be using to do this.
Anyway, here are my specs:
G1
Lastest Radio xxx.x...x.261
Cyanogenmod 4.2.5
Buuf theme 0.8
Amen Ra Recovery 1.3.2
This issue occurs even after a fresh full wipe and whether my rom is themed or not. It even happens with JF1.5.1
Any reccommends will be appreciated.
Thanks

To dry it, you can put it in a bowl of rice. Also, if your having problems even on JF, its most likely a hardware problem. Try flashing back to RC29 and seeing if its still there. If so, more than likely its hardware

So you don't think that I need a new digitizer?

cashless said:
So you don't think that I need a new digitizer?
Click to expand...
Click to collapse
Digitizer is hardware. This is most likely the part that needs to be replaced

Captivate accelerometer [hardware related]

I have a problem with my accelerometer. it's not working.and i tried the fix you can find on internet.delete ms3c_yamaha.cfg or smthing like that and recalibrate using that yamaha tool you start from terminal.
And it didnt help.maybe i did something wrong.after that i just gave up and reflashed to 2.3.4 which i was using before. im using DlevRom 4.2 right now.
I'm thinking of maybe trying that again.calibration and stuff.
But my main concern is if somehow i broke the accelerometer...which sounds almost impossible to me but you never know.
So is there like a service manual for captivate bcs i couldnt find one. I'm not sure how accelerometer looks like and where to find it on motherboard.
And if someone who's accelerometer works can put a picture of his accelerometer so that i can compare that to mine when i find it.
Thank you guys in advance for any kind of help.

I don't know how you could have broken the accelerometer but you may be able to be covered under warranty. Have you tried flashing back to stock? And how are you testing it?
Sent from my GT-I9000 using XDA App

Do a master clear and it should reset itself. If you just reflash a rom on top of itself, it would not work.
Dave
Sent from my SGH-I897 using XDA App

I tried flashing to stock.Im testing it using *#0*# test mode and games that require accelerometer.

should i first do a odin back to stock and then master clear or master clear then odin to stock?

Z1nK said:
should i first do a odin back to stock and then master clear or master clear then odin to stock?
Click to expand...
Click to collapse
I don't believe Odin back to stock is needed. At least I didn't have to when it happened to me.
Sent from my SGH-I897 using XDA App

*#*#0*#*#*

Yeah i forgot to mention.on that test mode.all values are changing except accelerometer values which are on top of the sensor page.and on that image test page also nothing is changing.its always staying on the same number.

If your light sensor works, then the i2c bus is operating. Try changing kernels again. If that does not work, then the accelerometer is loose, unpowered, missing, or broken.

ok,thank you sir.
I'm currently on stock Eclair ROM.Rooted only.
This whole situation is weird...I was in USA this summer and got this phone from ebay and it worked perfectly...I havent dropped it at all...accelerometer just stopped working out of a clear sky...I dont have many options if accelerometer is broken since i cant afford buying whole new captivate.. sticky situation :/

if you're brave you can always try solder reflow... that's where you take a heat gun to the board and attempt to make the solder flow again so that it can rejoin. This is a technique used on XBOX360s Red Ring of death or other small surface mount devices. I would not recommend it, but it's an option.
If it were my phone, I'd call AT&T AND Samsung about warranty replacement... Samsung may warranty your phone still.

well the problem is i obviously dont live in USA.if you think i should go for it...well..maybe i should.

can someone tell me where is accelerometer located on motherboard and how it looks like.because i cant get it to work...when i recalibrated it using yamaha sensor calib util, its vaules in test mode have changed and are now standing still on acnew value...