I found a new problem, which can potentially be really annoying since there's no other way to solve it apart from power cycle the phone.
I was messing around with the phone camera and switching between camcorder and camera mode, then the whole screen went black with the soft buttons showing in "dot" form.
I went back to the home screen and launched Camera app once again and still no activity. After a few seconds the OS informed that Camera app stopped working so I hit "Close". Then once I tried starting the Camera app again, there was this error "Cannot connect to camera"
Has anyone had this problem before?
cannot connect to camera
Just had this problem today. Was doing some video of setting up a new generator. That went ok. Got things set up and was going to take a pic. Screen was black. Tried opening a couple of times and got message "cannot connect to camera. I am doing a power cycle now.
Al
yeah I've had it before using cyanogen on my HTC sensation. had to power cycle. its annoying, happens often.
Sent from my Sensation using XDA App
It happened once on mine and I'm running standard 4.02. Never had it happen til yesterday.
Sent from my Galaxy Nexus using Tapatalk
This happened to me yesterday. Running stock 4.02. power cycle was the only way to get the camera working again.
Has happened to me on every rom i've tried, stock 4.0.1, arhd 2.1, cyanogenmod, villianrom etc. Very odd, happens when i try to enter the camera from the lock screen and rotate the device to landscape.
I'm also getting the same issue; has happened about 6 times in 4 days. Power cycle fixes it, which is very annoying. I'm not sure if the camera is active too long? It's usually running in Recent Apps.
I've been trying to exit out of the camera when I'm done as opposed to swapping apps or going to standby to see if that helps.
I'm having the same issue with my G-Nexus... 2nd time it's happened in 5 days.
Read in another blog that it could be caused by apps that access the camera that are not updated for ICS. NOt sure. But I uninstalled all such apps... we'll see.
I have this issue as well on my new GSM G-NEX that I have own for only three days now. Getting "cannot connect to camera" whenever I try to access camera, and power cycling doesn't help.
cannot connect to camera
after installation of cm7.1 i have the same problem with my zte blade. when i open the camera app, it says cannot connect to camera. idont no what to do. please help
I've had that problem a few times, usually from bad camera apps. Force closing the camera apps seem to fix the problem for me
Sent from my GT-P1000 using XDA App
I started having the same problem yesterday after taking a handful of pictures. Tried force stoping the Camera app, tried clearing its data/cache - no luck.
Here's a screenshot of the error:
h ttp://dev.npike.net/public/1325185257.png
I've read that if you have "force GDP rendering" on in the developer options it is screwing up the camera and camera apps
I don't have the option to force hardware acceleration enabled, but here is the output of logcat during the error:
Code:
I/ActivityManager( 185): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.camera/com.android.camera.Camera bnds=[40,785][200,985]} from pid 476
I/WindowManager( 185): createSurface Window{41f14030 Starting com.google.android.camera paused=false}: DRAW NOW PENDING
I/InputReader( 185): Reconfiguring input devices. changes=0x00000004
I/InputReader( 185): Device reconfigured: id=6, name='Melfas MMSxxx Touchscreen', surface size is now 720x1280, mode is 1
I/ActivityManager( 185): Config changed: {1.0 311mcc480mnc en_US layoutdir=0 sw360dp w598dp h360dp nrml land finger -keyb/v/h -nav/h s.29}
D/OpenGLRenderer( 268): Flushing caches (mode 0)
D/OpenGLRenderer( 268): Flushing caches (mode 0)
V/CameraHolder( 3737): open camera 0
W/CameraService( 118): CameraService::connect X (pid 3737) rejected (existing client).
E/CameraHolder( 3737): fail to connect Camera
E/CameraHolder( 3737): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 3737): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 3737): at android.hardware.Camera.<init>(Camera.java:302)
E/CameraHolder( 3737): at android.hardware.Camera.open(Camera.java:264)
E/CameraHolder( 3737): at com.android.camera.CameraHolder.open(CameraHolder.java:131)
E/CameraHolder( 3737): at com.android.camera.Util.openCamera(Util.java:267)
E/CameraHolder( 3737): at com.android.camera.Camera$4.run(Camera.java:1008)
E/CameraHolder( 3737): at java.lang.Thread.run(Thread.java:856)
D/dalvikvm( 3737): GC_FOR_ALLOC freed 142K, 2% free 16021K/16263K, paused 22ms
I/dalvikvm-heap( 3737): Grow heap (frag case) to 16.346MB for 662416-byte allocation
D/dalvikvm( 3737): GC_CONCURRENT freed 1535K, 11% free 15132K/16967K, paused 2ms+4ms
D/OpenGLRenderer( 476): Flushing caches (mode 0)
D/dalvikvm( 3737): GC_FOR_ALLOC freed 18K, 9% free 15476K/16967K, paused 14ms
D/dalvikvm( 3737): GC_CONCURRENT freed 8K, 7% free 15928K/16967K, paused 1ms+2ms
I/WindowManager( 185): createSurface Window{41cf6e00 com.google.android.camera/com.android.camera.Camera paused=false}: DRAW NOW PENDING
I/WindowManager( 185): createSurface Window{41ee9870 com.google.android.camera/com.android.camera.Camera paused=false}: DRAW NOW PENDING
D/OpenGLRenderer( 476): Flushing caches (mode 1)
D/OpenGLRenderer( 476): Flushing caches (mode 0)
I/WindowManager( 185): createSurface Window{42067810 SurfaceView paused=false}: DRAW NOW PENDING
V/camera ( 3737): surfaceChanged. w=960. h=720
I/ActivityManager( 185): Displayed com.google.android.camera/com.android.camera.Camera: +822ms
It sounds like when the Camera app crashes it doesn't release its resources correctly - preventing anything else on the system from acquiring the camera.
Update: I have reported this issue to Google ht tp://code.google.com/p/android/issues/detail?id=23776
Strange.. I had this phone for quite a while and I suddenly started seeing this problem. That's after moving from Franco's kernel to popcorn. I'm wondering if its something to do with the kernel.
Any updates so far?
I've had this problem--but only when I accidentally started the Cartoon Camera app. Essentially, my GN hates it when two apps are using the same camera .
dmmarck said:
I've had this problem--but only when I accidentally started the Cartoon Camera app. Essentially, my GN hates it when two apps are using the same camera .
Click to expand...
Click to collapse
I've also discovered that the official battery might be the factor. I have two official samsung galaxy nexus batteries, I think one is causing the camera to crash everytime. Maybe the NFC inside the battery?
I've had the problem numerous times. Stock 4.0.2. Sometimes it's when I'm out and about. I was beginning to think it could be related to GPS. I've sent several email trouble reports to Google and received no feedback/response.
I have the same issue, it seems to occur when I use the camera for a while, and joum between home and camera a lot. I have a completely stock setup at the moment and it happens much less frequently now than it did when I was running MRC r10.
Well, from what I am experiencing, it's something about task switching (like what TheBishopOfSoho mentioned) and also probably something about screen rotation. I have very little apps which I allow to rotate (camera is one of them) so it has to vigorously switch rotation when I switch apps.
But overall, the prob always comes unexpectedly.. so it's hard to pinpoint it
EDIT: One thing that has remained constant throughout my experience is that all camera problems were present when I was using the Popcorn kernel. Franco's kernel hasn't experienced it yet.
Franco 18.2: OK
Popcorn 7.x : Cam problems started appearing (can't remember which version I used)
Franco: 18.5: OK
Franco: 18.6: OK so far...
So maybe it's something in the kernel.. the cpu governor, speed, etc..
Just trying to get as much info as possible so hopefully we can find out the root cause of this..
Related
Phone:
T-Mobile G2
CM-7.0.0(full wipe then flashed from Post-OTA Stock ROM)
O/Cd to 1.017 Ghz with SetCPU
.26 Radio
Problems:
- Lockscreen never appears at all. Phone wakes straight into last activity
- Volume Down wakes phone. Not set in settings to do so.
- Home button gives haptic feedback on press, but performs no action on short or long press.
- All calls, whether to T-Mo or GV number go straight to voicemail.
Context:
I had just fixed a boot issue with CM7 by wiping cache and dalvik. I then decided to install Zeam Launcher, which has since been uninstalled. Have used SetCPU to set clock with On Demand governor back to max 800 mhz. No effect.
Also have been testing app on device but only has simple activities with no permissions needed and it runs with no errors or warnings.
Anyone have an answer to any of these issues? I have done a soft reboot and a battery pull. Thanks for the help.
Ok, here's the logcat log when I press the power button to turn the screen off, and the again to unlock it.
04-22 20:04:03.297: INFO/power(1485): *** set_screen_state 0
04-22 20:04:03.347: DEBUG/WifiService(1485): ACTION_SCREEN_OFF
04-22 20:04:03.497: DEBUG/SurfaceFlinger(1485): About to give-up screen, flinger = 0x93b98
04-22 20:04:03.507: DEBUG/AK8975(1385): Compass CLOSE
04-22 20:04:08.167: INFO/power(1485): *** set_screen_state 1
04-22 20:04:08.257: DEBUG/SurfaceFlinger(1485): Screen about to return, flinger = 0x93b98
04-22 20:04:08.327: DEBUG/AK8975(1385): Compass Start
04-22 20:04:08.687: DEBUG/WifiService(1485): ACTION_SCREEN_ON
04-22 20:04:16.267: DEBUG/dalvikvm(2483): GC_EXPLICIT freed 11K, 55% free 2708K/5959K, external 461K/973K, paused 76ms
04-22 20:04:31.247: DEBUG/dalvikvm(2491): GC_EXPLICIT freed <1K, 52% free 2789K/5703K, external 0K/0K, paused 60ms
Click to expand...
Click to collapse
Have you tried to reflash? redownload the rom and then flash.
Sent from my HTC Desire Z/G2 Using XDA Premium App
I was trying to avoid it, but I did a complete wipe(user data, cache, and dalvik) then re-flashed. Everything back to normal. With the calls, is there a known issue with Google Voice hijacking email causing issues on T-Mo in general or with CM7 in specific?
Thanks for the help. Just needed someone to convince me that the wipe-and-flash was what I had to do. Just a time suck.
I'm going through the same exact problem, I tried doing a full wipe, fixing permissions, reflashing, I don't know what else to do?
hey, did you ever get this issue resolved? I'm having a similar issue and my volume key won't respond
I'm facing this problem after going from Jellybean back to Gingerbread. Anyone resolved this?
---------- Post added at 11:44 AM ---------- Previous post was at 11:15 AM ----------
Solved. I flashed ICS gapps instead of GB gapps.
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.
Actually I have this problem with CM7 RC1v2, but in the past I had the same issue with Froyo ROM (Barebones one and if a remember well also official one): before going to sleep I put the phone in aeroplane mode and in the following morning I found it switched off.
This is not systematic, or better, last 3-4 days it happened always but from when I flash CM7 the problem seemed to be solved.
Last night I made a CatLog (attached) and reading it today I have noticed the following lines:
07-13 01:37:01.553 D/dalvikvm( 8555): GC_CONCURRENT freed 421K, 52% free 3204K/6663K, external 898K/1410K, paused 3ms+4ms
07-13 01:52:20.514 E/BATTD ( 1923): unrecoverable_error=AP Panic
07-13 01:52:20.514 I/BATTD ( 1923): SBCM_GLUE: Battery Exhausted, Sending 0 capacity to Power down
07-13 01:52:20.522 I/ActivityManager( 2149): Starting: Intent { act=android.intent.action.ACTION_REQUEST_SHUTDOWN flg=0x10000000 cmp=android/com.android.server.ShutdownActivity (has extras) } from pid 2149
I'm not so skilled in linux/android debuging (what is BATTD? sure something related to the battery...), but I think this is the moment that cause the shutdown of the defy.
Due to the fact that the issue happens both with CM7 than Froyo rom, I (unfortunately) suspect that may be a problem of the battery.
Have someone an idea about the possible cause of the problem? Or could it get more information than me from the catlog?
Many thanks.
EDIT: obviously the battery was charged, during catlog logging was around 60%. If the defy is connect to the power supply the issue seems not happen.
No one can help me to understand the catlog?!
Today happened another time, but I have not the catlog.
Please, no one have any idea? Or the only way is to understand is to buy another battery?
Again...
07-25 00:05:25.366 D/dalvikvm( 2286): GC_FOR_MALLOC freed 358K, 46% free 3720K/6791K, external 0K/512K, paused 57ms
07-25 00:22:46.530 E/BATTD ( 1927): unrecoverable_error=AP Panic
07-25 00:22:46.530 I/BATTD ( 1927): SBCM_GLUE: Battery Exhausted, Sending 0 capacity to Power down
07-25 00:22:46.538 I/SSM ( 1935): UEvent: PA Boost - Battery TOO LOW
Id suggest buying a second battery and see if the problem persists. If it does not, ditch your first battery, if it does hope for help
I would buy a cheap after market battery - they should be avaible on ebay fo less than 10$-
Yes, I just ordered one: 2,27 euro shipped from HK ahahah OK, only to see if it resolves the problem and if it reveals good in all, well I was lucky, otherwise I will buy an original one
Thanks for the reply!
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.
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.