Strange Vibration when holding menu+back keys? - myTouch 3G Slide Q&A, Help & Troubleshooting

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

Ace42 said:
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
Click to expand...
Click to collapse
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

whoa... same here... that's weird.
it vibrates.. then about 30 seconds later it gives me a triple vibrate

Thanks for the replies, I thought it was only me.
Sent From My MT3GS

you all fell for that? now your phone with be restored to factory settings on the next reboot jk

guitarist5122 said:
you all fell for that? now your phone with be restored to factory settings on the next reboot jk
Click to expand...
Click to collapse
For you reading this it doesn't restore factory settings at all. I guess it's some kind of unused function or something.

Neat, I guess. Running latest nightly, so doesn't appear to be a rom thing. Someone should check their logcat on it, since I am too lazy.

Omg after doing this, after a couple seconds it vibrates like crazy lol.

Ace42 said:
For you reading this it doesn't restore factory settings at all. I guess it's some kind of unused function or something.
Click to expand...
Click to collapse
No sense of humor
Sent from my T-Mobile myTouch 3G Slide using XDA App

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

Pretty interesting Monkey.. i have no idea what that means.. but i'm sure someone here does... and @guitarist... i chuckled. LOL

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

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

migueltherocker said:
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
Click to expand...
Click to collapse
I dont have a slash on mines, I got it around august before they had the newer ones.

migueltherocker said:
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
Click to expand...
Click to collapse
Got mine in june. Are you holding it down till it vibrates?
Sent from my T-Mobile myTouch 3G Slide using XDA App

i got mines in may (when it came out) and it does it

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.

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.

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)

agentg1001 said:
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)
Click to expand...
Click to collapse
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

Related

[Q] Logcat, GC_EXPLICIT in standby mode

Hi,
I do get a lot of GC_EXPLICIT in logcat when phone is in standby mode.
Example:
D/dalvikvm( 384): GC_EXPLICIT freed 1815 objects / 106712 bytes in 66ms
D/dalvikvm( 1976): GC_EXPLICIT freed 725 objects / 45704 bytes in 56ms
D/dalvikvm( 1908): GC_EXPLICIT freed 813 objects / 42024 bytes in 64ms
D/dalvikvm( 1960): GC_EXPLICIT freed 4864 objects / 252600 bytes in 68ms
Do anyone know where this comes from? I think it has something to do with the android email app and exchange.
I'm running Cyanogenmod 6.1 RC2.
Would be interesting to know from you, if this happens on your ROM, and if you use exchange or not.
How to reproduce:
Connect phone to computer. Open CMD. Type ADB shell. Type logcat. Turn of display with power button. Give it 5 minutes to see what comes out. This is also a nice way to diagnose buggy apps and see what drains your battery
Thanks!

[Q] CM 6.1.1: Screen not turning on from blank while downloading stuff via wifi

I currently have a CM 6.1.1 stable installed on my Desire, which runs just fine.
But there has always been this annoying problem that, when the screen turns off while the market or sth is downloading stuff via wifi,
there is a high chance of screen not turning on again. The phone is still responsive, and I can log into it via usb cable.
Logcat shows the following piece of info each time I tap OJ/Power:
D/KeyguardViewMediator( 283): wakeWhenReadyLocked(26)
D/KeyguardViewMediator( 283): handleWakeWhenReady(26)
D/KeyguardViewMediator( 283): pokeWakelock(5000)
I/power ( 283): *** set_screen_state 1
D/AK8973 ( 227): Compass Start
D/WifiService( 283): ACTION_SCREEN_ON
D/setcpu ( 631): Charging Profile 1113600, 1113600, ondemand
D/dalvikvm( 504): GC_EXPLICIT freed 220 objects / 10224 bytes in 37ms
D/dalvikvm( 631): GC_EXPLICIT freed 1633 objects / 77736 bytes in 33ms
I/power ( 283): *** set_screen_state 0
I/GPSButton( 283): Update State
D/WifiService( 283): ACTION_SCREEN_OFF
D/setcpu ( 631): Charging Profile 1113600, 1113600, ondemand
D/AK8973 ( 227): Compass CLOSE
D/dalvikvm( 504): GC_EXPLICIT freed 47 objects / 2472 bytes in 25ms
And dmesg shows nothing.
When I type 'adb shell reboot', nothing happens and the reboot command does not return.
This happens before setcpu is installed, so I think it is not to blame.
I use Darktremor a2sd script to install app in SD card, but this happens when SD card is removed, so it is not to blame, either.
Any suggestions or moves from you guys that I can try on my phone? The situation occurs quite frequently.
Thanks in advance.
P.S. I believe this to be a software issue because 3 days ago I was running another ROM and did not have this problem.
I checked Logcat of normal situation, which reads:
D/KeyguardViewMediator( 283): handleWakeWhenReady(0)
D/KeyguardViewMediator( 283): pokeWakelock(5000)
I/power ( 283): *** set_screen_state 1
D/SurfaceFlinger( 283): Screen about to return, flinger = 0x12d0e8
D/AK8973 ( 227): Compass Start
D/WifiService( 283): ACTION_SCREEN_ON
D/setcpu ( 634): Charging Profile 1113600, 1113600, ondemand
D/dalvikvm( 504): GC_EXPLICIT freed 178 objects / 7760 bytes in 85ms
D/dalvikvm( 504): GC_EXPLICIT freed 212 objects / 9680 bytes in 42ms
Comparing to this, one line was missing from the problematic log, the SurfaceFlinger:
'D/SurfaceFlinger( 283): Screen about to return, flinger = 0x12d0e8'
which means the surface flinger may have died when the screen no longer wakes up, I suppose?

[Q] Issue with LCD screen

I'm running my htc vision with Pyromod v2.0 (2.3.3 gb ROM) with the pyro kernel, which i believe is an altered version of pershoots latest kernel. Fantastic ROM, i've been using it since sunday morning with no problems, it's fast, slick, and incredibly small and responsive...
but, last night i ran the phone, with gps on, and streaming over amazonmp3 app, got to my location, sent a text, closed the keyboard, and hit the power button to put the screen to sleep. I got out of my car, walked up to the front door and was about to call to be let in, take out my phone, screen won't turn on, buttons on the bottom the screen light up and respond as normal. I have it set so i can hit the back button to unlock, so i hit back, and adjust the volume.. i hear the tone, so i knew i was on the main screen and past the lockscreen. After i get into the apt after being noticed, i do a battery pull. The phone reboots, i heard the vibrate that comes on right when the htc boot logo comes up, but STILL NOTHING on the screen! I try this a few more times.. let it boot, and have my girlfriend call me, she does, phone rings and i can answer it, touchscreen is responsive to slide to answer, but NOTHING on screen! phone functions, but the screen won't turn on. i leave the battery out overnight, in the morning my gf puts the battery in while i'm in the bathroom, unknown to me.. i come back and she holds up my phone, booting up, screen on.. needless to say i was thrilled! Flash forward, i'm at work during the day, screen and phone have been working fine.. around 3.. i turn the screen off.. and it doesn't turn back on again, same as before!
Now that i'm home i have messed with it a bit, if i leave the "blank" screen on while the phone is charging, eventually it times out.. but when i hit to power it on again for a 2nd time, the screen returns to life... but if i turn it off i have to do that again.
I've tried changed the cpu scaling, removing software.. but deep down i don't think that it's a problem with the software, does anyone think it could be the rom?
I guess my questions are
-does anyone know how i can test the unit via adb to see what's wrong?
-has anyone experienced anything like this before?
-anyone know where i can find the stock rom in case i have to return this thing?
EDIT: UPDATE: Here is the Logcat from my device
https://rapidshare.com/files/2442882484/logcat.txt
Pretty much this is what happens when i tried to turn the screen on and got nothing
I/power ( 1340): *** set_screen_state 0
W/IInputConnectionWrapper( 3292): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper( 3292): getExtractedText on inactive InputConnection
D/SurfaceFlinger( 1340): About to give-up screen, flinger = 0x93b98
D/TEST] ( 2419): There are 0 instances of Clock
I/com.dropbox.android.activity.lock.LockReceiver( 3322): Received action: android.intent.action.SCREEN_OFF
D/AK8975 ( 1234): Compass CLOSE
D/dalvikvm( 3322): GC_EXPLICIT freed 293K, 51% free 3343K/6791K, external 1K/513K, paused 79ms
D/dalvikvm( 3153): GC_EXPLICIT freed <1K, 51% free 2750K/5511K, external 0K/0K, paused 86ms
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/H7CTransparentBlack_base_small_95.png
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlysunny.png
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlysunny.png
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlysunny.png
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_chancestorm.png
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlycloudy.png
I/power ( 1340): *** set_screen_state 1
D/SurfaceFlinger( 1340): Screen about to return, flinger = 0x93b98
D/AK8975 ( 1234): Compass Start
D/TEST] ( 2419): There are 0 instances of Clock
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 334K, 53% free 2881K/6023K, external 1331K/1444K, paused 42ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 316K, 53% free 2846K/6023K, external 932K/1163K, paused 35ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 53K, 49% free 3127K/6023K, external 1524K/1725K, paused 35ms
D/dalvikvm( 1340): GC_EXTERNAL_ALLOC freed 169K, 53% free 6663K/14151K, external 4375K/4478K, paused 72ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 349K, 53% free 2881K/6023K, external 1314K/1381K, paused 28ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 317K, 53% free 2845K/6023K, external 932K/1163K, paused 34ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 46K, 53% free 2879K/6023K, external 1612K/1725K, paused 35ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 316K, 53% free 2844K/6023K, external 932K/1163K, paused 26ms
D/dalvikvm( 1340): GC_EXTERNAL_ALLOC freed 25K, 53% free 6658K/14151K, external 4405K/4478K, paused 69ms
D/GoogleVoice( 3139): MASFUpdateSettingsRpc.createRequestPayload: ENT
D/GoogleVoice( 3139): MASFUpdateSettingsRpc.createRequestPayload: RET
I/System.out( 3139): [INFO:5970349]: LogSource: Running flush
I/System.out( 3139): [INFO:5970352]: LogSource: Sending payload [bytes=660]
Could be anything; from to high OC to bad flash.
Try reflashing and afterwards do not overclock over 900. Also do not underclock. See what happens then.
reflashed via adb lastnight, no luck, also i only overclocked to around 900 normally and managed to disable that before reflashing.. also cleared cache, when i flashed i cleared cache and data, no dice.. as a matter of fact, now i can't seem to even "trick" it to turn on
do you think it could really be a ROM issue? i thought the rom only loaded after the splash screen and/or hboot? I get nothing on screen even as soon as the phone is turned on
anyway called t-mobile and they said it's a "known defect on early models of the g2 (much like the loose hinge)." Managed to convince them to ship me another phone at no charge to me with 3 day shipping.. now i just need to try to downgrade it and get it back to stock in the next 10 days... oh joy.

[Q] [ICS 4.0.3 CM9] PowerAmp crashing

Hi guys,
I have problems with PowerAmp in ICS, it is crashing quite often, sometimes it plays 2 hours just fine, and then I switch track or open library and it frozes and force quits.
Does anyone knows what is wrong? Author says that PowerAmp should be complatible with ICS.
There are logs:
D/ComprehensiveCountryDetector( 632): onServiceStateChanged
W/InputManagerService( 632): Window already focused, ignoring focus gain of: [email protected]
W/InputManagerService( 632): Starting input on non-focused client [email protected] (uid=1000 pid=632)
I/ActivityManager( 632): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.maxmpz.audioplayer/.StartupActivity} from pid 847
I/ActivityManager( 632): START {flg=0x24000000 cmp=com.maxmpz.audioplayer/.PlayerUIActivity} from pid 4595
V/PhoneStatusBar( 706): setLightsOn(true)
D/libEGL ( 4595): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 4595): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 4595): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 4595): loaded /system/lib/egl/libGLESv2_adreno200.so
I/ActivityManager( 632): Displayed com.maxmpz.audioplayer/.PlayerUIActivity: +742ms (total +805ms)
W/InputManagerService( 632): Starting input on non-focused client [email protected] (uid=10021 pid=847)
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer RETRY mBufferCount:2 mServerBufferCount:2
D/SurfaceTexture( 79): SurfaceTexture::dequeuebuffer: MIN EXCEEDED mBuffer:3 bumped
D/SurfaceTexture( 79): SurfaceTexture::dequeuebuffer: MIN EXCEEDED mBuffer:4 bumped
D/SurfaceTexture( 79): SurfaceTexture::dequeuebuffer: MIN EXCEEDED mBuffer:5 bumped
D/ActivityThread( 4595): Loading provider com.maxmpz.audioplayer: com.maxmpz.audioplayer.unlock.DataProvider
D/SurfaceTexture( 79): SurfaceTexture::dequeuebuffer: MIN EXCEEDED mBuffer:6 bumped
D/SurfaceTexture( 79): SurfaceTexture::dequeuebuffer: MIN EXCEEDED mBuffer:7 bumped
I/ActivityManager( 632): START {dat=content://com.maxmpz.audioplayer.data/files/20 flg=0x20000000 cmp=com.maxmpz.audioplayer/.PlayListActivity} from pid 4595
V/PhoneStatusBar( 706): setLightsOn(true)
I/ActivityManager( 632): Displayed com.maxmpz.audioplayer/.PlayListActivity: +662ms
D/ActivityThread( 4595): Loading provider com.maxmpz.audioplayer: com.maxmpz.audioplayer.unlock.DataProvider
D/SettingsProvider( 632): external modification to /data/data/com.android.providers.settings/databases/settings.db; event=2
D/SettingsProvider( 632): updating our caches for /data/data/com.android.providers.settings/databases/settings.db
D/SettingsProvider( 632): cache for settings table 'secure' rows=47; fullycached=true
D/SettingsProvider( 632): cache for settings table 'system' rows=60; fullycached=true
I/ActivityManager( 632): START {flg=0x24000000 cmp=com.maxmpz.audioplayer/.PlayerUIActivity} from pid 4595
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer RETRY mBufferCount:2 mServerBufferCount:2
I/InputDispatcher( 632): Application is not responding: AppWindowToken{41919ba8 token=Token{41838c68 ActivityRecord{4183d440 com.maxmpz.audioplayer/.PlayerUIActivity}}}. 5001.2ms since event, 5000.9ms since wait started
I/WindowManager( 632): Input event dispatching timed out sending to application AppWindowToken{41919ba8 token=Token{41838c68 ActivityRecord{4183d440 com.maxmpz.audioplayer/.PlayerUIActivity}}}
I/Process ( 632): Sending signal. PID: 4595 SIG: 3
I/dalvikvm( 4595): threadid=3: reacting to signal 3
I/dalvikvm( 4595): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 632): Sending signal. PID: 632 SIG: 3
I/dalvikvm( 632): threadid=3: reacting to signal 3
I/dalvikvm( 632): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 632): Sending signal. PID: 706 SIG: 3
I/dalvikvm( 706): threadid=3: reacting to signal 3
I/dalvikvm( 706): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 632): Sending signal. PID: 832 SIG: 3
I/dalvikvm( 832): threadid=3: reacting to signal 3
I/dalvikvm( 832): Wrote stack traces to '/data/anr/traces.txt'
D/dalvikvm( 632): GC_EXPLICIT freed 1145K, 15% free 17014K/19847K, paused 3ms+8ms
E/ActivityManager( 632): ANR in com.maxmpz.audioplayer (com.maxmpz.audioplayer/.PlayerUIActivity)
E/ActivityManager( 632): Reason: keyDispatchingTimedOut
E/ActivityManager( 632): Load: 2.4 / 2.17 / 2.13
E/ActivityManager( 632): CPU usage from 11063ms to 81ms ago with 99% awake:
E/ActivityManager( 632): 2.2% 632/system_server: 0.7% user + 1.5% kernel / faults: 84 minor
E/ActivityManager( 632): 2.2% 4595/com.maxmpz.audioplayer: 1.7% user + 0.5% kernel / faults: 213 minor 2 major
E/ActivityManager( 632): 1.8% 79/surfaceflinger: 0.9% user + 0.9% kernel / faults: 5341 minor
E/ActivityManager( 632): 0.2% 706/com.android.systemui: 0.1% user + 0% kernel / faults: 1 minor
E/ActivityManager( 632): 0.2% 5020/kworker/0:2: 0% user + 0.2% kernel
E/ActivityManager( 632): 0.1% 4623/com.quoord.tapatalkxdapre.activity: 0% user + 0% kernel / faults: 1 minor
E/ActivityManager( 632): 0% 6/rcu_kthread: 0% user + 0% kernel
E/ActivityManager( 632): 0% 847/com.teslacoilsw.launcher: 0% user + 0% kernel / faults: 58 minor
E/ActivityManager( 632): 0% 1589/com.touchtype.swiftkey: 0% user + 0% kernel / faults: 2 minor
E/ActivityManager( 632): 0% 3037/com.twitter.android: 0% user + 0% kernel
E/ActivityManager( 632): 0% 3638/wpa_supplicant: 0% user + 0% kernel
E/ActivityManager( 632): 0% 5026/logcat: 0% user + 0% kernel
E/ActivityManager( 632): 10% TOTAL: 3.6% user + 3.2% kernel + 3.8% iowait
E/ActivityManager( 632): CPU usage from 1215ms to 1821ms later with 99% awake:
E/ActivityManager( 632): 20% 632/system_server: 4.7% user + 15% kernel / faults: 1 minor
E/ActivityManager( 632): 20% 668/InputDispatcher: 1.5% user + 19% kernel
E/ActivityManager( 632): 18% TOTAL: 3.2% user + 14% kernel
W/ActivityManager( 632): Force finishing activity com.maxmpz.audioplayer/.PlayerUIActivity
I/ActivityManager( 632): Killing ProcessRecord{41a8bfe0 4595:com.maxmpz.audioplayer/10071}: user's request
I/ActivityManager( 632): Process com.maxmpz.audioplayer (pid 4595) has died.
I/WindowManager( 632): WIN DEATH: Window{416d18f8 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayerUIActivity paused=true}
W/WindowManager( 632): Force-removing child win Window{416da920 SurfaceView paused=false} from container Window{416d18f8 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayerUIActivity paused=true}
W/ActivityManager( 632): Service crashed 2 times, stopping: ServiceRecord{41790680 com.maxmpz.audioplayer/.player.PlayerService}
W/ActivityManager( 632): Service crashed 2 times, stopping: ServiceRecord{4178a7a8 com.maxmpz.audioplayer/.widgetpackcommon.WidgetUpdaterService}
E/SurfaceTexture( 79): [SurfaceView] dequeueBuffer: SurfaceTexture has been abandoned!
W/InputDispatcher( 632): channel '41769160 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayListActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 632): channel '41769160 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayListActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
W/WindowManager( 632): Failed looking up window
W/WindowManager( 632): java.lang.IllegalArgumentException: Requested window [email protected] does not exist
W/WindowManager( 632): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7156)
W/WindowManager( 632): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7147)
W/WindowManager( 632): at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:1529)
W/WindowManager( 632): at android.os.BinderProxy.sendDeathNotice(Binder.java:417)
W/WindowManager( 632): at dalvik.system.NativeStart.run(Native Method)
W/InputDispatcher( 632): Attempted to unregister already unregistered input channel '41769160 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayListActivity (server)'
I/WindowManager( 632): WIN DEATH: null
I/WindowManager( 632): WIN DEATH: Window{41769160 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayListActivity paused=false}
I/WindowManager( 632): WINDOW DIED Window{41769160 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayListActivity paused=false}
W/ActivityManager( 632): Launch timeout has expired, giving up wake lock!
W/InputManagerService( 632): Got RemoteException sending setActive(false) notification to pid 4595 uid 10071
Click to expand...
Click to collapse
Thx for any help.

AOSP build failing camera, bluetooth

Hi there,
for some days I try to build a clean AOSP build for my Galaxy Nexus GSM Edition.
I read this guide and the whole topic but I still fail, asking on the android devel list didn't really help so seems like you guys are my last chance, so here in short what I have done:
I set up an Ubuntu 10.04 LTS like you advised me to.
Chose repo with:
repo init -u https://android.googlesource.com/platform/manifest -b
android-4.0.3_r1
synced it.
Downloaded the 2 sh files for building properitary modules via
http://code.google.com/intl/de/android/nexus/drivers.html#maguro
Started both sh files to extract? modules.
Started building with:
source build/envsetup.sh
lunch -> 8 for maguro
make clobber
make -j2
make -j2 otapackage
First installationtry was wiping the device and applying the
update.zip file.
This resulted in a non working bluetooth and camera.
So I thought about applying img. files via fastboot and I packed them
alltogether to an .zip file, like the factory images, applied the
android-info.txt and did a
fastboot -w update update.zip.
Got the bootloop, rebooted after some time, android starts up but adb
lolcat gives me those:
Code:
I/bluedroid( 208): bt_enable: ret: -1, errno: 19
I/bluedroid( 208): bt_enable: ret: -1, errno: 19
I/bluedroid( 208): bt_enable: ret: -1, errno: 19
I/bluedroid( 208): bt_enable: ret: -1, errno: 19
I/bluedroid( 208): bt_enable: ret: -1, errno: 19
Ok... no bluetooth, I could live without that but after starting
camera, nothing happened.
Screen black, device did not really respond on pressing backkeys in
the Logs I can see:
Code:
/ActivityManager( 196): Start proc com.android.camera for activity
com.android.camera/.Camera: pid=968 uid=10007 gids={1006, 1015}
D/OpenGLRenderer( 374): Flushing caches (mode 1)
E/CameraHAL( 120): Couldn't get camera properties
W/dalvikvm( 968): threadid=11: thread exiting with uncaught exception
(group=0x40a351f8)
E/AndroidRuntime( 968): FATAL EXCEPTION: Thread-72
E/AndroidRuntime( 968): java.lang.RuntimeException: Fail to get
camera info
E/AndroidRuntime( 968): at
android.hardware.Camera.getCameraInfo(Native Method)
E/AndroidRuntime( 968): at
com.android.camera.CameraHolder.<init>(CameraHolder.java:102)
E/AndroidRuntime( 968): at
com.android.camera.CameraHolder.instance(CameraHolder.java:66)
E/AndroidRuntime( 968): at
com.android.camera.Util.openCamera(Util.java:267)
E/AndroidRuntime( 968): at com.android.camera.Camera
$4.run(Camera.java:1100)
E/AndroidRuntime( 968): at java.lang.Thread.run(Thread.java:856)
W/ActivityManager( 196): Force finishing activity
com.android.camera/.Camera
D/OpenGLRenderer( 374): Flushing caches (mode 0)
D/dalvikvm( 968): GC_CONCURRENT freed 207K, 3% free 12857K/13127K,
paused 2ms+3ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 11K, 2% free 12893K/13127K,
paused 13ms
I/dalvikvm-heap( 968): Grow heap (frag case) to 13.283MB for 662416-
byte allocation
D/dalvikvm( 196): GC_FOR_ALLOC freed 1829K, 14% free 16064K/18631K,
paused 38ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 1K, 3% free 13538K/13831K,
paused 11ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 20K, 2% free 13885K/14087K,
paused 14ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 5K, 2% free 14259K/14471K,
paused 12ms
E/CameraHAL( 120): Couldn't get camera properties
D/AndroidRuntime( 968): Shutting down VM
W/dalvikvm( 968): threadid=1: thread exiting with uncaught exception
(group=0x40a351f8)
I/Process ( 968): Sending signal. PID: 968 SIG: 9
I/ActivityManager( 196): Process com.android.camera (pid 968) has
died.
W/InputManagerService( 196): Window already focused, ignoring focus
gain of: com.android.internal.view.IInputMethodClient$Stub
[email protected]
I/ActivityManager( 196): START {act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x10200000
cmp=com.android.camera/.Camera bnds=[40,785][200,985]} from pid 374
I/ActivityManager( 196): Start proc com.android.camera for activity
com.android.camera/.Camera: pid=990 uid=10007 gids={1006, 1015}
D/dalvikvm( 118): GC_EXPLICIT freed 36K, 3% free 12559K/12867K,
paused 2ms+3ms
D/OpenGLRenderer( 374): Flushing caches (mode 1)
D/dalvikvm( 118): GC_EXPLICIT freed <1K, 3% free 12559K/12867K,
paused 9ms+2ms
D/OpenGLRenderer( 374): Flushing caches (mode 0)
D/dalvikvm( 118): GC_EXPLICIT freed <1K, 3% free 12559K/12867K,
paused 1ms+2ms
E/CameraHAL( 120): Couldn't get camera properties
W/dalvikvm( 990): threadid=11: thread exiting with uncaught exception
(group=0x40a351f8)
E/AndroidRuntime( 990): FATAL EXCEPTION: Thread-75
E/AndroidRuntime( 990): java.lang.RuntimeException: Fail to get
camera info
E/AndroidRuntime( 990): at
android.hardware.Camera.getCameraInfo(Native Method)
E/AndroidRuntime( 990): at
com.android.camera.CameraHolder.<init>(CameraHolder.java:102)
E/AndroidRuntime( 990): at
com.android.camera.CameraHolder.instance(CameraHolder.java:66)
E/AndroidRuntime( 990): at
com.android.camera.Util.openCamera(Util.java:267)
E/AndroidRuntime( 990): at com.android.camera.Camera
$4.run(Camera.java:1100)
E/AndroidRuntime( 990): at java.lang.Thread.run(Thread.java:856)
W/ActivityManager( 196): Force finishing activity
com.android.camera/.Camera
D/dalvikvm( 196): GC_CONCURRENT freed 530K, 13% free 16374K/18631K,
paused 7ms+6ms
D/dalvikvm( 990): GC_CONCURRENT freed 236K, 3% free 12824K/13127K,
paused 3ms+7ms
D/dalvikvm( 990): GC_FOR_ALLOC freed 12K, 2% free 12899K/13127K,
paused 13ms
I/dalvikvm-heap( 990): Grow heap (frag case) to 13.290MB for 662416-
byte allocation
D/dalvikvm( 990): GC_CONCURRENT freed 3K, 3% free 13543K/13831K,
paused 2ms+4ms
D/dalvikvm( 990): GC_FOR_ALLOC freed 20K, 2% free 13889K/14087K,
paused 20ms
D/dalvikvm( 990): GC_FOR_ALLOC freed 5K, 2% free 14263K/14471K,
paused 13ms
E/CameraHAL( 120): Couldn't get camera properties
D/AndroidRuntime( 990): Shutting down VM
W/dalvikvm( 990): threadid=1: thread exiting with uncaught exception
(group=0x40a351f8)
I/Process ( 990): Sending signal. PID: 990 SIG: 9
I/ActivityManager( 196): Process com.android.camera (pid 990) has
died.
W/InputManagerService( 196): Window already focused, ignoring focus
gain of: com.android.internal.view.IInputMethodClient$Stub
[email protected]
D/dalvikvm( 374): GC_CONCURRENT freed 1178K, 30% free 17250K/24583K,
paused 6ms+5ms
I/ActivityManager( 196): START {act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x10200000
cmp=com.android.camera/.Camera bnds=[40,785][200,985]} from pid 374
I/ActivityManager( 196): Start proc com.android.camera for activity
com.android.camera/.Camera: pid=1011 uid=10007 gids={1006, 1015}
D/OpenGLRenderer( 374): Flushing caches (mode 1)
D/OpenGLRenderer( 374): Flushing caches (mode 0)
E/CameraHAL( 120): Couldn't get camera properties
W/dalvikvm( 1011): threadid=11: thread exiting with uncaught exception
(group=0x40a351f8)
E/AndroidRuntime( 1011): FATAL EXCEPTION: Thread-78
E/AndroidRuntime( 1011): java.lang.RuntimeException: Fail to get
camera info
E/AndroidRuntime( 1011): at
android.hardware.Camera.getCameraInfo(Native Method)
E/AndroidRuntime( 1011): at
com.android.camera.CameraHolder.<init>(CameraHolder.java:102)
E/AndroidRuntime( 1011): at
com.android.camera.CameraHolder.instance(CameraHolder.java:66)
E/AndroidRuntime( 1011): at
com.android.camera.Util.openCamera(Util.java:267)
E/AndroidRuntime( 1011): at com.android.camera.Camera
$4.run(Camera.java:1100)
E/AndroidRuntime( 1011): at java.lang.Thread.run(Thread.java:856)
W/ActivityManager( 196): Force finishing activity
com.android.camera/.Camera
D/dalvikvm( 1011): GC_CONCURRENT freed 206K, 3% free 12858K/13127K,
paused 7ms+3ms
D/dalvikvm( 1011): GC_FOR_ALLOC freed 11K, 2% free 12898K/13127K,
paused 13ms
I/dalvikvm-heap( 1011): Grow heap (frag case) to 13.288MB for 662416-
byte allocation
D/dalvikvm( 1011): GC_CONCURRENT freed 1K, 3% free 13543K/13831K,
paused 7ms+1ms
D/dalvikvm( 1011): GC_FOR_ALLOC freed 20K, 2% free 13889K/14087K,
paused 32ms
D/dalvikvm( 1011): GC_FOR_ALLOC freed 5K, 2% free 14263K/14471K,
paused 31ms
E/CameraHAL( 120): Couldn't get camera properties
D/AndroidRuntime( 1011): Shutting down VM
W/dalvikvm( 1011): threadid=1: thread exiting with uncaught exception
(group=0x40a351f8)
I/Process ( 1011): Sending signal. PID: 1011 SIG: 9
I/ActivityManager( 196): Process com.android.camera (pid 1011) has
died.
W/InputManagerService( 196): Window already focused, ignoring focus
gain of: com.android.internal.view.IInputMethodClient$Stub
[email protected]
I/power ( 196): *** set_screen_state 0
D/SurfaceFlinger( 117): About to give-up screen, flinger = 0xf1b918
D/dalvikvm( 196): GC_CONCURRENT freed 913K, 12% free 16407K/18631K,
paused 6ms+6ms
D/dalvikvm( 196): GC_EXPLICIT freed 54K, 13% free 16352K/18631K,
paused 3ms+6ms
D/NfcService( 359): NFC-C OFF, disconnect
V/TransportControlView( 196): Create TCV
[email protected]
D/PhoneStatusBar( 263): disable: < expand icons alerts ticker
system_info back home RECENT* clock >
D/dalvikvm( 196): GC_CONCURRENT freed 34K, 8% free 17147K/18631K,
paused 3ms+7ms
W/IInputConnectionWrapper( 196): showStatusIcon on inactive
InputConnection
and
Code:
I/ActivityManager( 196): START {act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x10200000
cmp=com.android.camera/.Camera bnds=[40,785][200,985]} from pid 374
I/ActivityManager( 196): Start proc com.android.camera for activity
com.android.camera/.Camera: pid=968 uid=10007 gids={1006, 1015}
D/OpenGLRenderer( 374): Flushing caches (mode 1)
E/CameraHAL( 120): Couldn't get camera properties
W/dalvikvm( 968): threadid=11: thread exiting with uncaught exception
(group=0x40a351f8)
E/AndroidRuntime( 968): FATAL EXCEPTION: Thread-72
E/AndroidRuntime( 968): java.lang.RuntimeException: Fail to get
camera info
E/AndroidRuntime( 968): at
android.hardware.Camera.getCameraInfo(Native Method)
E/AndroidRuntime( 968): at
com.android.camera.CameraHolder.<init>(CameraHolder.java:102)
E/AndroidRuntime( 968): at
com.android.camera.CameraHolder.instance(CameraHolder.java:66)
E/AndroidRuntime( 968): at
com.android.camera.Util.openCamera(Util.java:267)
E/AndroidRuntime( 968): at com.android.camera.Camera
$4.run(Camera.java:1100)
E/AndroidRuntime( 968): at java.lang.Thread.run(Thread.java:856)
W/ActivityManager( 196): Force finishing activity
com.android.camera/.Camera
D/OpenGLRenderer( 374): Flushing caches (mode 0)
D/dalvikvm( 968): GC_CONCURRENT freed 207K, 3% free 12857K/13127K,
paused 2ms+3ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 11K, 2% free 12893K/13127K,
paused 13ms
I/dalvikvm-heap( 968): Grow heap (frag case) to 13.283MB for 662416-
byte allocation
D/dalvikvm( 196): GC_FOR_ALLOC freed 1829K, 14% free 16064K/18631K,
paused 38ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 1K, 3% free 13538K/13831K,
paused 11ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 20K, 2% free 13885K/14087K,
paused 14ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 5K, 2% free 14259K/14471K,
paused 12ms
E/CameraHAL( 120): Couldn't get camera properties
D/AndroidRuntime( 968): Shutting down VM
W/dalvikvm( 968): threadid=1: thread exiting with uncaught exception
(group=0x40a351f8)
I/Process ( 968): Sending signal. PID: 968 SIG: 9
I/ActivityManager( 196): Process com.android.camera (pid 968) has
died.
W/InputManagerService( 196): Window already focused, ignoring focus
gain of: com.android.internal.view.IInputMethodClient$Stub
[email protected]
Some guy on IRC told me that the imgtech properitaeries are extracted to the wrong folder so I tried copying them like this:
Code:
cp -av vendor/imgtec/maguro/* vendor/samsung/maguro/
This didn't work.
I also tried the documentation from: http://www.franziroesner.com/blog/2...ary-binaries-for-custom-android-galaxy-nexus/
Did not work. I get mad...
And yes, I could have this one attached to the build thread, but I didn't want to brick this one more and get a new clean starting for help.
Pretty sure camera and bt proprietaries come from 4.0.2.
As said, there are different binaries needed for camera/bluetooth. Not got a link personally but I have seen it somewhere in the Compile thread on here
I read the thread and tried both ways of getting the properitary modules.
Both fail.
You might want to contact the dev of this http://forum.xda-developers.com/showthread.php?t=1444413
Sorry, I can't help much, as I am not a developer
Sent from my Galaxy Nexus using xda premium
t4c said:
I read the thread and tried both ways of getting the properitary modules.
Both fail.
Click to expand...
Click to collapse
Define 'both ways'.
adrynalyne I tried to extract the files via the 2 files I can download on the code.google page.
The other way I tried was the one mentioned in the build thread: http://www.franziroesner.com/blog/2...ary-binaries-for-custom-android-galaxy-nexus/
Did you make clean? The second method certainly should have worked.
I always make clean before make.

Categories

Resources