Database Develop

[SOLVED!] Accelerometer/G1's Sensor Issues

All right, so a while ago say..few hours or a day ago, I dropped my phone. Nothing seemed wrong, everything was working fine. Until I decided to go play Abduction World Attack. It's a game where you tilt the G1 and the little character moves according to how you tilt it. Surprise Surprise I ran into my problem. The little avatar wouldn't move and it was just stuck there no matter how I turned my phone. I also just noticed that auto-rotate won't work. I believe it's because the accelerometer is broken...Anyone have any advice on how to fix this or calibrate it? I've tried calibrating inside apps that use the accelerometer. I've searched but to no avail. Help will be appreciated Thank-you.
[Edit]: A wipe has fixed this! =)

If your under warranty, you may want to try and get it exchanged. Let T-Mobile/HTC know that it just stopped working.
If you are out of warranty, you can attempt at looking for a solution by taking apart the phone. The official manual is here
The manual has all of the disassemble instructions. Hopefully that will lead you to a solution.

Sounds like it could be a hardware issue but no harm in testing to see if it is a software one. Tried rebooting the mobile? If so see if other programs like Bubble works. If not then a final resort would be a reflash to at least eliminate the software side of things.
If its no go then best to try and get it exchanged...

I've fixed it guys ^^ Seemed like a wipe would do it. I changed to the hero build for a second and then reflash CM after a wipe and accelerometer is fixed. Thanks for the suggestions though! Greatly appreciated

The power of the mighty wipe ^_- Good to hear its been sorted. Since you're the OP too, could you edit the title to SOLVED so people know?

NeoBlade said:
The power of the mighty wipe ^_- Good to hear its been sorted. Since you're the OP too, could you edit the title to SOLVED so people know?
Click to expand...
Click to collapse
Sure. OP and title has been updated!

Sure wish I had your luck. I'm having the same problem and a wipe didn't do me any good.
I have tried several different mods and none of them work.
tested with browser, bubble, Papi game apps, and Accelerometer xyz Values.
I don't have any akm files located in /data/misc
I do have a /system/bin/akmd but my ps output doesn't show it running.

whatchamccallum said:
Sure wish I had your luck. I'm having the same problem and a wipe didn't do me any good.
I have tried several different mods and none of them work.
tested with browser, bubble, Papi game apps, and Accelerometer xyz Values.
I don't have any akm files located in /data/misc
I do have a /system/bin/akmd but my ps output doesn't show it running.
Click to expand...
Click to collapse
Most likely a hardware problem then mate. You could try un-rooting and see if the accelerometer works.

If I install RC29 then the accelerometer works without issue. So that rules out hardware issue.

Here is another thread I found that goes in much more detail about what I am experiencing.
http://forum.xda-developers.com/showthread.php?t=533749
so far there isn't any movement on this thread. I'm surprised that this issue isn't more wide spread.

I just had the accelerometer on my HTC Sapphire go belly up.
Auto-rotate was broken, compass apps wouldn't initialize, tilting maze games would slowly move the ball to the top left side regardless of actual tilting, etc..
Reboot didn't fix it. However I did have a file under /data/misc/akmd_set.txt and most of the values in it were set to 0.
I renamed that file to akmd_set.txt, then killed akmd, per instructions in a neighboring thread.
akmd rose from its ashes, a new akmd_set.txt automagically appeared, with lots of different numbers for each value in it. All my accelerometer-depending features were happy again.
so yay, and all that.
As a side-note, I've been playing with some not insignificant magnets on my desk, and I'm wondering if abnormal magnetic fields around my phone might have caused the accelerometer miscalibration?

Good for my G1 too.
Kudos to the OP, this solution worked perfectly on my G1 with the same symptoms. Many Thanks!

Nexus One charging at 106F ~Froyo

my nexus one is charging on a regular basis around 106-7 F. I know there is another thread about this issue but the question was not resolved. So does anyone have experience with this issue. Is it a defect or dangerous? I have OSmonitor installed, this si where I am reading my temps. I also notice the CPU usage is pegged around 98-99%..is this normal?
I heard using setCPU with a charging profile can solve this problem if you have root?

No, it is not normal for the cpu to be maxed out while charging. Are you using the car dock or a wall charger?

nexous one
mine does the same thing all the time its not going to damage your phone at all
my phone has got about 120 F on car doc
my phone is perfect just set your set cpu for fail safe and your all good

You probably could use SetCPU to solve this problem, but the fact that your CPU usage is so high in the first place means there is something going wrong - my guess would be a rogue app.
Try downloading a task killer from the Market. Kill each app running one at a time then check your CPU usage. You'll soon find the culprit.

sn95chico said:
my phone has got about 120 F on car doc
Click to expand...
Click to collapse
Yeah I'm starting to see the problem with the phone having a metal casing. Not good when it's summer and you have to place it under direct sunlight for extended amounts of time, while using navigation AND charging
That thing can get burning hot alright.

Are you using froyo 2.2?
I have had the same problem; I also have random periods of high cpu use when not charging as well. This issue is not caused by problem apps either. I must reboot to fix the issue, sometimes I must reboot several times until the cpu load is back to normal.
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
I will also try to reapply the 2.2 update.

Marine6680 said:
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
Click to expand...
Click to collapse
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.

frandavid100 said:
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
Click to expand...
Click to collapse
I bet your heat issues are related to cpu loads or staying at high frequencies like mine. Sometimes the phone does not feel like it is really running as hard as the system monitors say, though it may still get hot.
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
I am re-flashing the leaked 2.2 update to make sure there was no issue with the original install. I am also using the copy my GF downloaded when I sent her the instructions on the off chance that my download was corrupted in some small way; unlikely but hey. I do think that the original flash may have gone wrong, as mine hung and never rebooted after the flash was complete; I had to manually reboot. Lets hope this fixes it.
This issue may be more widespread than we realize, as many people do not actively monitor their cpu or notice/worry about the heat after charging. I do believe that these leaked ROMs send debug data to google, I remember reading something along those lines; these are internal test ROMs after all. Maybe this is a reason that 2.2 is not out yet, this and other bugs found during real world use.

Marine6680 said:
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
Click to expand...
Click to collapse
What I did was follow this guide up to the point where you have a stock eclair rom, then not upgrade to Froyo. Keep using that for some time, see whether the phone gets hot or not, THEN (if you want) move back to Froyo.

I am using the wall charger hat came with the nexus one. I am also running Froyo 2.2... can I set a CPU fail safe without my phone being rooted? Also what is a quick to check if my phone is rooted? I just bought this Nexus One from someone. I know on my G1 it was rooted bc I had Superuser permissions.

Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.

The fastest way I can think would be installing Lamppu, then trying to use it to light up the camera flash. If it works your phone is flashed, if it doesn't it's not.
As for your other questions... sorry, i don't know. I hope someone else can help you.

foethalove said:
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
Click to expand...
Click to collapse
Thats a system process so you can not kill it.
Going to test my GFs nexus and see if she has these issues as well.

I restored my N1 to the factory image, the updated back through each update to 2.2; so far so good. My GF's N1 has been running fine since I really started watching it, so I figured it would hurt to try to restore and redo the update.

No 100% cpu load during charging any more!

i am using the Motorola charger and my phone is not getting hot at all. with the charger that comes in the box for the N1 it seems to heat up.

Still had the CPU load get stuck at 100% today; though charging is not forcing 100% loads any more.

By the way, how do you measure how busy the processor is? How do you know that it's at 100%?

frandavid100 said:
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
Click to expand...
Click to collapse
System monitor apps, some will even put a little icon in the notification tray that shows current cpu load.

[Q] Audio only works after reboot

The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?

timmyjoe42 said:
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
Click to expand...
Click to collapse
Your search method must be flawed, as this is a known & frequently discussed issue.

timmyjoe42 said:
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
Click to expand...
Click to collapse
It's defective. Get a new one.

Thanks for the reply.
Now to unroot...

Mine had the same exact problem. Audio usually stopped working after the screen went to sleep for the first time after a reboot. I recently flashed the 900mhz "screamer" overclock kernel and I've yet to have an audio problem since then. As much sense as that does or doesn't make, it seemed to fix the problem for me. Its worth a try. Hope it works for you (if you haven't already unrooted and returned by now)
Sent from my Droid using XDA App

When you get your hands on the new one, before you leave the store do this. After power on & such, try the audio (V0l + -). Works? Put to sleep for >10sec. Wake & test audio. No-work? Reboot, (Long power press) Try sleep/wake sequence again. If it works you are golden, now check a few other things & go home & root it! If it fails the test, don't let the Nook Genius tell you that you should let it charge for at least 4 hrs. before testing. The three that I have received had between 50% & 90% charge OOB. That's plenty for it to work properly, assuming the battery level meter is accurate. Put together your own checklist based on info on this forum. Crossword to test edges of screen, kbd. when charging from wall adapter etc.
Good luck, when you get a good one they are solid!
kev

trumpet444 said:
Mine had the same exact problem. Audio usually stopped working after the screen went to sleep for the first time after a reboot. I recently flashed the 900mhz "screamer" overclock kernel and I've yet to have an audio problem since then. As much sense as that does or doesn't make, it seemed to fix the problem for me. Its worth a try. Hope it works for you (if you haven't already unrooted and returned by now)
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Interesting! That would support the thinking that this issue is related to timing & initializing the audio codec or something related. Hardware specs may be skewed just enough for it to not work when waking up. That's actually encouraging! Means that all those with this problem may see a F/W fix if they don't want to re-clock it.
Cheers,
kev

Well, I unrooted and restored it to factory new using the 9 reboot method. This brought the device back to 1.0.0. I then went back to the store. The manager came out, took the device, and said "it needed 1.0.1 to fix the problem. Let me load it for you." I was thinking, "whatever dude. It had 1.0.1 on it and it still had the issue." But the guy was super nice and ran off with the device to some back office. He came back while it was installing 1.0.1 and it's working fine now. I kept trying to get it to recreate the problem with no luck. (So it actually is good luck.)
I'm assuming the 1.0.1 software update didn't install properly the first time.
I could have done all that myself without going to the store.

timmyjoe42 said:
Well, I unrooted and restored it to factory new using the 9 reboot method. This brought the device back to 1.0.0. I then went back to the store. The manager came out, took the device, and said "it needed 1.0.1 to fix the problem. Let me load it for you." I was thinking, "whatever dude. It had 1.0.1 on it and it still had the issue." But the guy was super nice and ran off with the device to some back office. He came back while it was installing 1.0.1 and it's working fine now. I kept trying to get it to recreate the problem with no luck. (So it actually is good luck.)
I'm assuming the 1.0.1 software update didn't install properly the first time.
I could have done all that myself without going to the store.
Click to expand...
Click to collapse
That's interesting. I had the audio/sleep problem with 1.0.0 & exchanged it for another 1.0.0 that worked fine. ?????

[Q] Touch buttons dont work after call

Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks

coola71 said:
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
Click to expand...
Click to collapse
Same problem here! I don't need to take out battery, just reboot device
Any idea? Root? What ROM?

This thing has too many troubles for users. Just got mine but haven't used it yet. Samsung hasn't made a good phone so far. Problems left to right. Note could be my last Samsung phone.

i have noticed the same thing too, but i am running Sheep Rom, it seems intermittent. what rom are you running?

coola71 said:
Hi everyone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
Click to expand...
Click to collapse
I used to have issues with my prior android phone if I got dirt or whatever over the proximity sensor.
Android phones disable the touchscreen/buttons during a phone call so your cheek doesn't hang up the phone.
If your phone is dirty, however, it gets confused, and keeps things disabled after the call.
This happened to me fairly often when I had a case/screen collector that tended to collect pocket lint.
- Frank
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
CyberGhos said:
This thing has too many troubles for users. Just got mine but haven't used it yet. Samsung hasn't made a good phone so far. Problems left to right. Note could be my last Samsung phone.
Click to expand...
Click to collapse
You can't be bleeding edge without some bleeding.
The GNote ain't perfect and it's a bit rough on the edges, but there's no way I would trade it for any other phone.
- Frank

ChodTheWacko said:
I used to have issues with my prior android phone if I got dirt or whatever over the proximity sensor.
Android phones disable the touchscreen/buttons during a phone call so your cheek doesn't hang up the phone.
If your phone is dirty, however, it gets confused, and keeps things disabled after the call.
This happened to me fairly often when I had a case/screen collector that tended to collect pocket lint.
- Frank
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
You can't be bleeding edge without some bleeding.
The GNote ain't perfect and it's a bit rough on the edges, but there's no way I would trade it for any other phone.
- Frank
Click to expand...
Click to collapse
This. You shouldn't go Samsung or Android if you don't want to do some finetuning. If you want an out of the box solution take buy an iPhone. Then you can wait for Apple to release updates instead of being able to fix it yourself the same day.

i agree, its not even a hardware problem, its a software problem. i can accept small glitches as long as i can fix them, unfortunately you cant fix a hardware malfunction with software, unless of course the patch your applying is going directly over the antenna like a certain iGadget4

coola71 said:
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
Click to expand...
Click to collapse
Hi
Even i am facing the same issue n need to know what is the sol. If it is a hardware issue should i get my phone replaced. I bought it only yesterday.
For me too it happens occassionally and requires restart of the phone.
Please help someone.
Just a guess - if all users r not facing it is it a hardware issue

I had this happen once after about 4weeks of using sgn. I don't know if i had made a call prior or what, just before it happened. A reboot made the problem go away for an hour or so. It came back.
I had installed an app a few hours earlier (dell store mobile app). I removed it - not really expecting to fix it. . . It didn't.
After some futzing, I rebooted into cwm recovery: flushed dalvic cache and fix permissions and rebooted. .. it has been working ever since.
This has happened only once, a few days ago. I'd wager it is a software issue.
Sent from my GT-N7000 using xda premium

Even I am also facing the same issue on Sheep ROM
Is this a ROM specific issue or Kernel ?

Same problem here !
I have been using the SGN for the past 4 days. I had this problem in the Stock ROM and it remains even after rooting the phone.
This phone/tablet seems to be a premature release with loads of small problems here and there. I guess they plan to remove these errors directly in ICS.

I believe the problem is on the kernel, try to get some that is stable.
If you are on original stick with it, if you have it rooted try to get the newest kernel.
What happen is that the proximity sensor closes the phone screen, and lower the speed of the cpu, in some times the cpu have some collapses and forget, what you need is to control the cpu or turn off the proximitor sensor, something like that.
I dont have that problem, with both official rom and rooted phone with abyssnote.
I hope this help.

It happened with me too, 2-3 times. Few hours ago I was checking a pdf document and I received a call and the other party couldnt hear me well. While he was calling me again everything froze. Neither touch buttons nor the screen was working. I had to take the battery out, since I couldnt turn it off because of the unresponsive screen. This is really bugging me off.

I've had this occur to me twice, first time I was fidgeting with some app I can't even remember which, second time just a while ago (and that's why I went in here searching), right after making a call.
Using the S-Pen to swype-gesture back and menu they work though, it's just the buttons themselves that are dead.
Wouldn't think the proximity has anything to do with it (nice idea anyway) because then the whole screen should be unresponsive to touchm, wouldn't it?
BTW I am using xlite rom now, and maybe I could go for the cache wiping.
EDIT: I had cleared cache partition and dalvik cache this morning, ths afternoon the note has been sitting idle on the desk, 2mA drain according to battery monitor widget estimates, and without any calls the buttons stopped working again...

xinato91 said:
I believe the problem is on the kernel, try to get some that is stable.
If you are on original stick with it, if you have it rooted try to get the newest kernel.
What happen is that the proximity sensor closes the phone screen, and lower the speed of the cpu, in some times the cpu have some collapses and forget, what you need is to control the cpu or turn off the proximitor sensor, something like that.
I dont have that problem, with both official rom and rooted phone with abyssnote.
I hope this help.
Click to expand...
Click to collapse
+1 I'm using Abyssnote kernel too - no problems with soft buttons yet.

anyone find a fix for this yet? i have to reboot my phone after pretty much every call to get the buttons working again. starting to get really annoying
forgot to mention im on stock rom unrooted

Reset and Root - CFKernel and AbyssNote worked for me
n0thingr3mains said:
anyone find a fix for this yet? i have to reboot my phone after pretty much every call to get the buttons working again. starting to get really annoying
forgot to mention im on stock rom unrooted
Click to expand...
Click to collapse
I had rooted and applied CF Kernel to my rom and had faced a few problems. But after wiping and applying CFRoot (latest) again I did not face any problems.
I have had no problems in the past 24 hours.
You can use the guide by Chainfire to root and apply CF Kernel (the best guide ever) and test for a day or two. then try moving to AbyssNote1.4 (I moved because I wanted to test OC)
Before you root and flash kernel, I will recommend factory resetting(since you are unrooted at the moment) and do not install any apps - because that is what actually worked for me.
UPDATE :
I havr started facing button issue on 1.4 AbyssNote as well.

Same problem here not woking :-( :-( :-(
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
How to fix this bug???

So, some news. I've been fighting with a nasty battery drain due to the phone being unable to keep the deep sleep status. In the process I've tried flashing AbyssNote kernel 1.2 (people were saying 1.4 suffered from high drains, and I haven't seen this problem since then... but it's been just a few, so it may be too soon.

ephestione said:
So, some news. I've been fighting with a nasty battery drain due to the phone being unable to keep the deep sleep status. In the process I've tried flashing AbyssNote kernel 1.2 (people were saying 1.4 suffered from high drains, and I haven't seen this problem since then... but it's been just a few, so it may be too soon.
Click to expand...
Click to collapse
I can confirm high battery drains with Abyss 1.4 (revert back to 1.2). But it is the only kernel which don´t suffer "touch buttons bug"

Help - Phone Randomly Powering Down

Hi Everyone
Bit of help please.
Having problems over the last 20 days or so. The phone keeps powering down completely at random.
I had flashed No Root Stock Debloated/Deodexed N6 ViPER|Atmos Audiophile 1.6 and after a week the above started.
Fully wiped (including data) the N6 and re-installed from a OTG USB through TWRP. After a week the same random shut-downs began again.
Another full wipe and installed ver 1.7 from the above and within a couple of days the shutdowns started again.
Today thought a different ROM may be the answer. Full wipe and tried [MMB29U/Q][6.0.1][STOCK][OMNI][MOKEE][CMTE][LAYERS] FLUENCE HD9 and the shut-downs are still here.
Seems to be getting worse.
Not using layers or anything abnormal - nova launcher and popular apps, nothing strange. No Kernel optimizations.
Really stumped as to what I have done. Wondering if I have a HW fault rather than custom rom or apps. Going to un-root, lock the BL and give Google stock image a go, unless anyone has a suggestion.
TIA

Any water damage that you can think of? Any parts of the phone getting extremely hot?
You could try ordering a new battery, and see if that fixes the issue, as it is not a software issue.

I'm also having a similar issue, but it occurs when trying to open camera and having relatively low charges(%20). I could not pinpoint my issue exactly but generally complete shutdowns caused by battery problems(temperature, voltage, mis-feedback). Like flyeyes says it is probably a defected battery unit.

Grab some logcats or a crash message. Without them the only thing I can advise is that it is one of your apps causing it or a hardware issue.

Have you tried complete stock firmware from Google with no customizations? If so, does it happen then? If it happens on complete stock from Google you might be looking at a hardware issue. If it only happens on custom ROMS after you set them up, then it might be an inconsistency with whatever apps/changes you make to it.