Does anyone else's phone give a diff vib when holding both keys, I just discovered this while screen was of.
Sent from my MTS using XDA App
Sent from my MTS using XDA App
Strange Vibration when holding menu+back keys?
- Thread starter Ace42
- Start date
Whoa it does. That's weird. I'm running cr_mod on mine. I wonder why it does that.
Sent from my T-Mobile myTouch 3G Slide using XDA App
For you reading this it doesn't restore factory settings at all. I guess it's some kind of unused function or something.
OK, I got unlazy. Logcat between the time I press the buttons, and then the vibrations shortly after. Dumpstate.
Code:
KeyguardViewMediator( 148): pokeWakelock(5000)
dumpstate( 3499): begin
dalvikvm( 148): threadid=3: reacting to signal 3
dalvikvm( 148): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 251): threadid=3: reacting to signal 3
dalvikvm( 251): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 256): threadid=3: reacting to signal 3
dalvikvm( 256): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 257): threadid=3: reacting to signal 3
dalvikvm( 257): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 279): threadid=3: reacting to signal 3
dalvikvm( 279): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 367): threadid=3: reacting to signal 3
dalvikvm( 367): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 404): threadid=3: reacting to signal 3
dalvikvm( 404): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 434): threadid=3: reacting to signal 3
dalvikvm( 434): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 492): threadid=3: reacting to signal 3
dalvikvm( 492): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 627): threadid=3: reacting to signal 3
dalvikvm( 627): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 803): threadid=3: reacting to signal 3
dalvikvm( 803): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 2007): threadid=3: reacting to signal 3
dalvikvm( 2007): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 2025): threadid=3: reacting to signal 3
dalvikvm( 2025): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 2097): threadid=3: reacting to signal 3
dalvikvm( 2097): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 2694): threadid=3: reacting to signal 3
dalvikvm( 2694): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 2773): threadid=3: reacting to signal 3
dalvikvm( 2773): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 3117): threadid=3: reacting to signal 3
dalvikvm( 3117): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 3133): threadid=3: reacting to signal 3
dalvikvm( 3133): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 3146): threadid=3: reacting to signal 3
dalvikvm( 3146): Wrote stack traces to '/data/anr/traces.txt'
dalvikvm( 3419): threadid=3: reacting to signal 3
dalvikvm( 3419): Wrote stack traces to '/data/anr/traces.txt'
VoldCmdListener( 97): asec list
power ( 148): *** set_screen_state 0
SurfaceFlinger( 148): About to give-up screen, flinger = 0x147de0
GPSButton( 148): Update State
AK8973 ( 106): Compass CLOSE
dalvikvm( 148): GC_FOR_MALLOC freed 19509 objects / 1164744 bytes in 147ms
dalvikvm( 148): GC_FOR_MALLOC freed 16196 objects / 1217480 bytes in 141ms
dalvikvm( 148): GC_FOR_MALLOC freed 17006 objects / 1162640 bytes in 142ms
dalvikvm( 148): GC_FOR_MALLOC freed 19068 objects / 1163904 bytes in 150ms
dalvikvm( 148): GC_FOR_MALLOC freed 20203 objects / 1167408 bytes in 150ms
dalvikvm( 148): GC_FOR_MALLOC freed 6883 objects / 534912 bytes in 138ms
dalvikvm( 257): GC_FOR_MALLOC freed 8276 objects / 582312 bytes in 104ms
dalvikvm( 256): GC_FOR_MALLOC freed 4503 objects / 310096 bytes in 64ms
dalvikvm( 434): GC_FOR_MALLOC freed 11370 objects / 500376 bytes in 71ms
dalvikvm( 148): GC_FOR_MALLOC freed 22590 objects / 1475360 bytes in 148ms
dalvikvm( 148): GC_FOR_MALLOC freed 24687 objects / 1190888 bytes in 147ms
dalvikvm( 148): GC_FOR_MALLOC freed 23109 objects / 1179608 bytes in 150ms
dalvikvm( 148): GC_FOR_MALLOC freed 18521 objects / 1168416 bytes in 145ms
dalvikvm( 404): GC_EXPLICIT freed 883 objects / 51264 bytes in 60ms
dumpstate( 3499): done
Last edited:
Yeah idk what it is, I'm on the latest nightly as well. Must be something htc put in there for some reason, must be a kernel thing?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Sent from my T-Mobile myTouch 3G Slide using XDA App
You guys who it happens to, you all have the new slides right? Check if the number 0 on your kb has a slash through it. If so, you have the newer model.
It doesn't work on mine, and I have the old one. That's why I ask.
Sent from my T-Mobile myTouch 3G Slide using XDA App
It doesn't work on mine, and I have the old one. That's why I ask.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I dont have a slash on mines, I got it around august before they had the newer ones.
Got mine in june. Are you holding it down till it vibrates?
Sent from my T-Mobile myTouch 3G Slide using XDA App
This problem is similar to the /init bug (HTC Legend) and somehow related to Froyo.
When USB Debugging is off, it does exactly the same as described here (vibrates).
In case of USB Debugging deactivated, it causes the /init process to run. This process uses up to 100% of the processor.
When USB Debugging is off, it does exactly the same as described here (vibrates).
In case of USB Debugging deactivated, it causes the /init process to run. This process uses up to 100% of the processor.
I have a slash through my 0, so I guess I have a newer model. I''m running CR_mod now and I just tried it again, different behavior.
w/ screen off, I held down menu and back, it vibrated once, I unlocked, went to setcpu, and it was clocked all the way up to 864, so I'm assuming the usage was at 100%, and then like 7 seconds later or so, it did three quick pulse vibrates in a row and then it clocked back down to 245. Very odd. And as you all probably know, cr_mod is just rooted stock with the OTA update, which is Eclair, nor Froyo, so it can't be a froyo independent thing.
w/ screen off, I held down menu and back, it vibrated once, I unlocked, went to setcpu, and it was clocked all the way up to 864, so I'm assuming the usage was at 100%, and then like 7 seconds later or so, it did three quick pulse vibrates in a row and then it clocked back down to 245. Very odd. And as you all probably know, cr_mod is just rooted stock with the OTA update, which is Eclair, nor Froyo, so it can't be a froyo independent thing.
Hope its not a problem bringing this back up but it also seems to do the same on a mytouch 4g (glacier). I tried it after rooting/s-off/oc to 1.8 etc etc (this is not my phone btw i wish)
Still happens on cm7, phone lags like no other until it vibrated rapidly three times signaling that whatever it's doing is done. Also, it was sending and receiving data during this, might be some sort of sync or update check? Who knows. Probably unrelated, but if you hold down the camera button in cm7 it randomly vibrates continuously until you release it. Didn't happen in cm6.
Sent from my T-Mobile myTouch 3G Slide
