i got a problem.
my battery (HD orig with 1350mA) last about 2 days, which is ok.
BUT,
now i checked the consumption with PowerGuard.
The result is: i start the prog after charging - 100%
now, there are 3% left and i got a consumtion of 743 maH
what happened there?
battery broken?
anybody got an explanation for this?
does a program exist, which can check if my battery is ok? may this be a powerguard problem?
Hi all,
the camera on my Glacier appears to be broken. Any "camera related" app I try to launch force closes after a few seconds. This is true for the built-in camera app, for a barcode scanner app and even for a torch app that would use the flash and not really the camera.
I have already cleared the cache and Davlik and have fixed the permissions to no avail. I ran a logcat from launching the camera app until after I clicked the "force close" button:
Code:
I/ActivityManager( 1351): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera bnds=[96,721][192,800] } from pid 1702
I/ActivityManager( 1351): Start proc com.android.camera for activity com.android.camera/.Camera: pid=3292 uid=10048 gids={1006, 1015}
I/WindowManager( 1351): Setting rotation to 1, animFlags=1
V/CameraHolder( 3292): open camera 0
W/WindowManager( 1351): App freeze timeout expired.
W/WindowManager( 1351): Force clearing freeze: AppWindowToken{40a23298 token=HistoryRecord{40a230d8 com.android.camera/.Camera}}
I/InputDispatcher( 1351): Application is not responding: AppWindowToken{40a23298 token=HistoryRecord{40a230d8 com.android.camera/.Camera}}. 9279.3ms since event, 5004.2ms since wait started
I/WindowManager( 1351): Input event dispatching timed out sending to application AppWindowToken{40a23298 token=HistoryRecord{40a230d8 com.android.camera/.Camera}}
I/Process ( 1351): Sending signal. PID: 3292 SIG: 3
I/dalvikvm( 3292): threadid=4: reacting to signal 3
I/dalvikvm( 3292): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1351): Sending signal. PID: 1351 SIG: 3
I/dalvikvm( 1351): threadid=4: reacting to signal 3
I/dalvikvm( 1351): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1351): Sending signal. PID: 1617 SIG: 3
I/dalvikvm( 1617): threadid=4: reacting to signal 3
I/dalvikvm( 1617): Wrote stack traces to '/data/anr/traces.txt'
W/ActivityManager( 1351): Activity idle timeout for HistoryRecord{40a230d8 com.android.camera/.Camera}
I/Process ( 1351): Sending signal. PID: 1572 SIG: 3
D/dalvikvm( 1351): GC_EXPLICIT freed 732K, 38% free 6779K/10823K, external 1561K/2073K, paused 88ms
E/ActivityManager( 1351): ANR in com.android.camera (com.android.camera/.Camera)
E/ActivityManager( 1351): Reason: keyDispatchingTimedOut
E/ActivityManager( 1351): Load: 3.4 / 3.17 / 2.89
E/ActivityManager( 1351): CPU usage from 5627ms to 1ms ago:
E/ActivityManager( 1351): 4.2% 1351/system_server: 3.1% user + 1% kernel / faults: 796 minor
E/ActivityManager( 1351): 3.5% 3050/adbd: 0.1% user + 3.3% kernel
E/ActivityManager( 1351): 2.3% 1245/mediaserver: 0% user + 2.3% kernel
E/ActivityManager( 1351): 2.1% 1572/com.android.systemui: 1.2% user + 0.8% kernel / faults: 1 minor
E/ActivityManager( 1351): 1.7% 1268/logcat2: 0.1% user + 1.5% kernel
E/ActivityManager( 1351): 1.4% 3071/com.google.android.apps.maps: 1% user + 0.3% kernel / faults: 292 minor
E/ActivityManager( 1351): 1.4% 3290/logcat: 0.3% user + 1% kernel
E/ActivityManager( 1351): 0.8% 1249/akmd: 0.3% user + 0.5% kernel
E/ActivityManager( 1351): 0.7% 1252/htc_ebdlogd: 0% user + 0.7% kernel
E/ActivityManager( 1351): 0.3% 6/events/0: 0% user + 0.3% kernel
E/ActivityManager( 1351): 0.3% 921/emmc-qd: 0% user + 0.3% kernel
E/ActivityManager( 1351): 0% 1184/jbd2/mmcblk0p28: 0% user + 0% kernel
E/ActivityManager( 1351): 0% 1658/wpa_supplicant: 0% user + 0% kernel / faults: 11 minor
E/ActivityManager( 1351): 0% 2310/twc.provider: 0% user + 0% kernel / faults: 43 minor
E/ActivityManager( 1351): 0.1% 3292/com.android.camera: 0.1% user + 0% kernel
E/ActivityManager( 1351): 14% TOTAL: 6.9% user + 7.8% kernel
E/ActivityManager( 1351): CPU usage from 297ms to 819ms later:
E/ActivityManager( 1351): 7.4% 1351/system_server: 0% user + 7.4% kernel
E/ActivityManager( 1351): 5.5% 1528/InputDispatcher: 0% user + 5.5% kernel
E/ActivityManager( 1351): 3% 3050/adbd: 1.5% user + 1.5% kernel
E/ActivityManager( 1351): 3% 3050/adbd: 0% user + 3% kernel
E/ActivityManager( 1351): 1.5% 3055/adbd: 1.5% user + 0% kernel
E/ActivityManager( 1351): 1.3% 1245/mediaserver: 0% user + 1.3% kernel
E/ActivityManager( 1351): 1.3% 2450/Binder Thread #: 0% user + 1.3% kernel
E/ActivityManager( 1351): 1.3% 1252/htc_ebdlogd: 0% user + 1.3% kernel
E/ActivityManager( 1351): 1.3% 1268/logcat2: 0% user + 1.3% kernel / faults: 2 minor
E/ActivityManager( 1351): 1.3% 1572/com.android.systemui: 1.3% user + 0% kernel
E/ActivityManager( 1351): 1.3% 1572/ndroid.systemui: 1.3% user + 0% kernel
E/ActivityManager( 1351): 11% TOTAL: 5.7% user + 5.7% kernel
I/InputDispatcher( 1351): Dropping event because the pointer is not down.
I/InputDispatcher( 1351): Dropping event because the pointer is not down.
W/ActivityManager( 1351): Force finishing activity com.android.camera/.Camera
I/Process ( 1351): Sending signal. PID: 3292 SIG: 9
I/ActivityManager( 1351): Killing com.android.camera (pid=3292): user's request
I/ActivityManager( 1351): Process com.android.camera (pid 3292) has died.
W/InputManagerService( 1351): Window already focused, ignoring focus gain of: [email protected]
My next step now would be a factory reset, but before I do that I'd like to see whether anybody's got a better idea. Any help is appreciated.
Thanks.
---------- Post added at 12:51 PM ---------- Previous post was at 12:35 PM ----------
I just did another reboot and launched the camera app, again. On the first attempt the behavior was the same as before: the app force closed after a while. On any subsequent attempts to launch the camera app I now get the error message "Camera Error / Cannot connect to camera".
We need more info. Are you rooted? What rom? What kernel? Any mods, themes? Things like this can break stuff.
If youre rooted and running a custom rom, just reflash the rom from a full wipe.
Sent from my HTC Glacier using xda premium
I would try full wipe and flash the ROM again.
Sent from my HTC Glacier using XDA App
the device is rooted; I am running CM 7.0.3 with kernel 2.6.35.14 demonspeed v9. It's probably the kernel that causing these problems. After re-flashing CM 7.0.3 (thus going back to the kernel that comes with the ROM), the camera started working again ...
Recently the camera on my z just force closes whenever I try to use it, whether its the camera app, or another app that uses the camera, I.e; barcode scanner, this is fairly recent, and I have tried a few different roms, with no success using my camera again, the roms I tried are miui, cm7, and virtuous unity, so I have no idea what is causing the fc's, and was wondering if there's anyone here who can help me?
Sent from my HTC Desire Z using XDA App
are you restoring system data with TB? are you super wiping and clearing all the caches manually before flashes?
Yeah, I have tried a full wipe (system,cache,dalvik?), and a clean rom without restoring anything with TB and I still get the FC issue.
Sent from my HTC Desire Z using XDA App
i suppose it could be hardware related, have you tried any rooted stock roms with a stock kernal etc? See if that works? I know the wrong kernal with the wrong rom will break camera functionality
I haven't tried that, I'll have a look around for one, any you'd reccomend?
Sent from my HTC Desire Z using XDA App
Update, tried a few stock rooted roms here, with the htc kernel, still no camera :/
Could you do a logcat ? At least you would see whats happening when the camera Force Closes?
Good call lol I always read longcat lol
10-15 14:45:31.513 D/dalvikvm(1190): GC_EXPLICIT freed 11K, 50% free 2699K/5379K, external 0K/0K, paused 73ms
10-15 14:45:31.593 D/dalvikvm(1190): GC_EXPLICIT freed <1K, 50% free 2699K/5379K, external 0K/0K, paused 94ms
10-15 14:45:31.633 V/com.miui.camera.Camera(7315): onCreate
10-15 14:45:31.633 I/com.miui.camera.Global(7315): initialize global variables
10-15 14:45:31.633 I/com.miui.camera.Global(7315): DEVICE: vision
10-15 14:45:31.673 D/dalvikvm(1190): GC_EXPLICIT freed <1K, 50% free 2699K/5379K, external 0K/0K, paused 75ms
10-15 14:45:31.713 I/com.miui.camera.CameraGlobal(7315): initialize global variables
10-15 14:45:31.773 V/com.miui.camera.CameraHolder(7315): open 0
10-15 14:45:31.773 V/com.miui.camera.CameraHolder(7315): open camera 0
10-15 14:45:31.913 D/dalvikvm(1387): GC_EXPLICIT freed 157K, 41% free 4671K/7879K, external 0K/0K, paused 47ms
10-15 14:45:41.333 W/ActivityManager(1279): Launch timeout has expired, giving up wake lock!
10-15 14:45:41.523 W/ActivityManager(1279): Activity idle timeout for HistoryRecord{40d02118 com.miui.camera/.Camera}
10-15 14:45:49.561 D/dalvikvm(7278): GC_EXPLICIT freed 133K, 49% free 4282K/8327K, external 1166K/1218K, paused 65ms
10-15 14:45:54.576 D/dalvikvm(1654): GC_EXPLICIT freed 73K, 45% free 3713K/6727K, external 0K/0K, paused 81ms
10-15 14:46:15.001 I/ActivityManager(1279): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.miui.camera/.Camera bnds=[129,128][239,259] } from pid 1387
10-15 14:46:15.161 I/ActivityManager(1279): Start proc com.miui.camera for activity com.miui.camera/.Camera: pid=7327 uid=10036 gids={1006, 1015}
10-15 14:46:15.291 V/com.miui.camera.Camera(7327): onCreate
10-15 14:46:15.291 I/com.miui.camera.Global(7327): initialize global variables
10-15 14:46:15.291 I/com.miui.camera.Global(7327): DEVICE: vision
10-15 14:46:15.321 I/com.miui.camera.CameraGlobal(7327): initialize global variables
10-15 14:46:15.321 V/com.miui.camera.CameraHolder(7327): open 0
10-15 14:46:15.321 V/com.miui.camera.CameraHolder(7327): open camera 0
10-15 14:46:17.824 D/PowerManagerService(1279): reactivateScreenLocksLocked mProxIgnoredBecauseScreenTurnedOff=false
10-15 14:46:22.839 I/InputDispatcher(1279): Application is not responding: AppWindowToken{40d8da38 token=HistoryRecord{40977b98 com.miui.camera/.Camera}}. 5009.7ms since event, 5009.6ms since wait started
10-15 14:46:22.839 I/WindowManager(1279): Input event dispatching timed out sending to application AppWindowToken{40d8da38 token=HistoryRecord{40977b98 com.miui.camera/.Camera}}
10-15 14:46:22.909 I/Process (1279): Sending signal. PID: 7327 SIG: 3
10-15 14:46:22.909 I/dalvikvm(7327): threadid=4: reacting to signal 3
10-15 14:46:22.909 I/dalvikvm(7327): Wrote stack traces to '/data/anr/traces.txt'
10-15 14:46:22.909 I/Process (1279): Sending signal. PID: 1279 SIG: 3
10-15 14:46:22.909 I/dalvikvm(1279): threadid=4: reacting to signal 3
10-15 14:46:22.929 I/dalvikvm(1279): Wrote stack traces to '/data/anr/traces.txt'
10-15 14:46:22.929 I/Process (1279): Sending signal. PID: 1448 SIG: 3
10-15 14:46:22.929 I/dalvikvm(1448): threadid=4: reacting to signal 3
10-15 14:46:22.929 I/dalvikvm(1448): Wrote stack traces to '/data/anr/traces.txt'
10-15 14:46:22.929 I/Process (1279): Sending signal. PID: 1368 SIG: 3
10-15 14:46:22.929 I/dalvikvm(1368): threadid=4: reacting to signal 3
10-15 14:46:22.929 I/dalvikvm(1368): Wrote stack traces to '/data/anr/traces.txt'
10-15 14:46:23.309 D/dalvikvm(1279): GC_EXPLICIT freed 1277K, 30% free 10605K/15047K, external 0K/0K, paused 120ms
10-15 14:46:23.900 E/ActivityManager(1279): ANR in com.miui.camera (com.miui.camera/.Camera)
10-15 14:46:23.900 E/ActivityManager(1279): Reason: keyDispatchingTimedOut
those are the parts of the logcat i have refering camera, if you'd like anymore of said logcat, lemme know!
I'm having a similar issue, but the camera only force closes if I try to use a shooting mode outside of no effect or black and white. All other modes cause a crash
running insertcoin 1.6
barryweston said:
I'm having a similar issue, but the camera only force closes if I try to use a shooting mode outside of no effect or black and white. All other modes cause a crash
running insertcoin 1.6
Click to expand...
Click to collapse
I'd be happy with that, i only ever used normal mode anyway :/
Hey,
I've made some research... In fact my phone can freeze not even in games but in everything...Like every 3 or 4 days even if I don't touch the phone !
Like today : I tried to wake it up but it didn't respond (screen stay black). After some time, it turns on again and it seems the system has reloaded himself without full reboot (reload of the icon on the desktop, searching for new media on the sd, etc... ).
I looked in the logs, and here what I found :
02-29 20:00:53.945 D/dalvikvm(714): GC_EXTERNAL_ALLOC freed 15K, 37% free 8193K/12935K, external 51174K/51462K, paused 77ms
02-29 20:00:53.964 E/dalvikvm-heap(714): 1463040-byte external allocation too large for this process.
02-29 20:00:53.988 D/SmsProvider(811): update content://sms/1661 succeeded
02-29 20:00:54.046 E/GraphicsJNI(714): VM won't let us allocate 1463040 bytes
02-29 20:00:54.046 D/dalvikvm(714): GC_FOR_MALLOC freed <1K, 37% free 8193K/12935K, external 51174K/51462K, paused 70ms
02-29 20:00:54.050 D/skia (714): --- decoder->decode returned false
02-29 20:00:54.050 W/dalvikvm(714): threadid=20: thread exiting with uncaught exception (group=0x40015578)
02-29 20:00:54.058 V/MmsSmsProvider(811): uri=content://mms-sms/conversations/6
02-29 20:00:54.070 I/ActivityManager(714): Process com.sec.android.provider.logsprovider (pid 27151) has died.
02-29 20:00:54.089 V/MmsSmsProvider(811): uri=content://mms-sms/conversations/6
02-29 20:00:54.124 E/ (714): Dumpstate > /data/log/dumpstate_sys_error
02-29 20:00:54.124 E/AndroidRuntime(714): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy
02-29 20:00:54.124 E/AndroidRuntime(714): java.lang.OutOfMemoryError: bitmap size exceeds VM budget
02-29 20:00:54.124 E/AndroidRuntime(714): at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:563)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:439)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:697)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.content.res.Resources.loadDrawable(Resources.java:1709)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.content.res.Resources.getDrawable(Resources.java:581)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.widget.ImageView.resolveUri(ImageView.java:501)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.widget.ImageView.setImageResource(ImageView.java:280)
02-29 20:00:54.124 E/AndroidRuntime(714): at com.android.internal.policy.impl.CircleLockScreen.<init>(CircleLockScreen.java:146)
02-29 20:00:54.124 E/AndroidRuntime(714): at com.android.internal.policy.impl.LockPatternKeyguardView.createLockScreen(LockPatternKeyguardView.java:941)
02-29 20:00:54.124 E/AndroidRuntime(714): at com.android.internal.policy.impl.LockPatternKeyguardView.recreateLockScreen(LockPatternKeyguardView.java:767)
02-29 20:00:54.124 E/AndroidRuntime(714): at com.android.internal.policy.impl.LockPatternKeyguardView.recreateScreens(LockPatternKeyguardView.java:787)
02-29 20:00:54.124 E/AndroidRuntime(714): at com.android.internal.policy.impl.LockPatternKeyguardView.access$1100(LockPatternKeyguardView.java:78)
02-29 20:00:54.124 E/AndroidRuntime(714): at com.android.internal.policy.impl.LockPatternKeyguardView$2.recreateMe(LockPatternKeyguardView.java:336)
02-29 20:00:54.124 E/AndroidRuntime(714): at com.android.internal.policy.impl.PatternUnlockScreen.onConfigurationChanged(PatternUnlockScreen.java:480)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.view.View.dispatchConfigurationChanged(View.java:4156)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.view.ViewGroup.dispatchConfigurationChanged(ViewGroup.java:729)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.view.ViewGroup.dispatchConfigurationChanged(ViewGroup.java:733)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.view.ViewGroup.dispatchConfigurationChanged(ViewGroup.java:733)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.view.ViewRoot.updateConfiguration(ViewRoot.java:1804)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.view.ViewRoot.handleMessage(ViewRoot.java:1939)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.os.Handler.dispatchMessage(Handler.java:99)
02-29 20:00:54.124 E/AndroidRuntime(714): at android.os.Looper.loop(Looper.java:130)
02-29 20:00:54.124 E/AndroidRuntime(714): at com.android.server.WindowManagerService$PolicyThread.run(WindowManagerService.java:622)
and ..
02-29 20:14:24.382 I/ServiceManager(95): service 'mount' died
02-29 20:14:24.382 I/ServiceManager(95): service 'usbstorage' died
02-29 20:14:24.382 I/ServiceManager(95): service 'encrypt' died
02-29 20:14:24.382 I/ServiceManager(95): service 'SurfaceFlinger' died
02-29 20:14:24.382 I/ServiceManager(95): service 'sensorservice' died
02-29 20:14:24.382 I/ServiceManager(95): service 'entropy' died
02-29 20:14:24.382 I/ServiceManager(95): service 'power' died
02-29 20:14:24.382 I/ServiceManager(95): service 'batteryinfo' died
02-29 20:14:24.382 I/ServiceManager(95): service 'usagestats' died
02-29 20:14:24.382 I/ServiceManager(95): service 'telephony.registry' died
02-29 20:14:24.382 I/ServiceManager(95): service 'package' died
02-29 20:14:24.382 I/ServiceManager(95): service 'activity' died
02-29 20:14:24.382 I/ServiceManager(95): service 'account' died
02-29 20:14:24.382 I/ServiceManager(95): service 'meminfo' died
02-29 20:14:24.382 I/ServiceManager(95): service 'cpuinfo' died
02-29 20:14:24.382 I/ServiceManager(95): service 'permission' died
02-29 20:14:24.382 I/ServiceManager(95): service 'backup' died
02-29 20:14:24.382 I/ServiceManager(95): service 'content' died
02-29 20:14:24.382 I/ServiceManager(95): service 'vibrator' died
02-29 20:14:24.382 I/ServiceManager(95): service 'appwidget' died
02-29 20:14:24.382 I/ServiceManager(95): service 'hardware' died
02-29 20:14:24.382 I/ServiceManager(95): service 'battery' died
02-29 20:14:24.382 I/ServiceManager(95): service 'alarm' died
02-29 20:14:24.382 I/ServiceManager(95): service 'window' died
02-29 20:14:24.382 I/ServiceManager(95): service 'bluetooth' died
02-29 20:14:24.382 I/ServiceManager(95): service 'bluetooth_a2dp' died
02-29 20:14:24.382 I/ServiceManager(95): service 'bluetooth_hid' died
02-29 20:14:24.382 I/ServiceManager(95): service 'application_policy' died
02-29 20:14:24.382 I/ServiceManager(95): service 'eas_account_policy' died
02-29 20:14:24.382 I/ServiceManager(95): service 'roaming_policy' died
02-29 20:14:24.382 I/ServiceManager(95): service 'misc_policy' died
02-29 20:14:24.382 I/ServiceManager(95): service 'device_policy' died
02-29 20:14:24.382 I/ServiceManager(95): service 'devicestoragemonitor' died
02-29 20:14:24.382 I/ServiceManager(95): service 'statusbar' died
02-29 20:14:24.382 I/ServiceManager(95): service 'clipboard' died
02-29 20:14:24.382 I/ServiceManager(95): service 'clipboardEx' died
02-29 20:14:24.382 I/ServiceManager(95): service 'network_management' died
02-29 20:14:24.382 I/ServiceManager(95): service 'input_method' died
02-29 20:14:24.382 I/ServiceManager(95): service 'netstat' died
02-29 20:14:24.402 I/ActivityThread(799): Removing dead content provider: settings
02-29 20:14:24.425 I/ActivityThread(21071): Removing dead content provider: settings
02-29 20:14:24.429 I/ServiceManager(95): service 'wifi' died
02-29 20:14:24.429 I/ServiceManager(95): service 'connectivity' died
02-29 20:14:24.429 I/ServiceManager(95): service 'throttle' died
02-29 20:14:24.429 I/ServiceManager(95): service 'accessibility' died
02-29 20:14:24.429 I/ServiceManager(95): service 'diskstats' died
02-29 20:14:24.429 I/ServiceManager(95): service 'notification' died
02-29 20:14:24.429 I/ServiceManager(95): service 'datarouter' died
02-29 20:14:24.429 I/ServiceManager(95): service 'usb' died
02-29 20:14:24.429 I/ServiceManager(95): service 'location' died
02-29 20:14:24.429 I/ServiceManager(95): service 'search' died
02-29 20:14:24.429 I/ServiceManager(95): service 'dropbox' died
02-29 20:14:24.429 I/ServiceManager(95): service 'wallpaper' died
02-29 20:14:24.429 I/ServiceManager(95): service 'audio' died
02-29 20:14:24.429 I/ServiceManager(95): service 'tvoutservice' died
02-29 20:14:24.429 I/ServiceManager(95): service 'FMPlayer' died
02-29 20:14:24.429 I/ServiceManager(95): service 'uimode' died
All the process died... and restarted later. What do u think about this? Apparently it's a system process problem but I don't know how to find where is the probleme coming from... (714) = is it the process number? I don't know what is behind this process...
Thanks for your help.
Bib
Hey.
Try to restore factory settings from recovery or wipe data / factory resert.
Hey. Thanks for your answer. I already tried that, no change
Maybe it works:
Go into recovery mode. WIPE (factory reset + wipe cache + wipe dalvik cache) + "format system"
then flash a oirginal samsung stock rom
then flash custom rom
So I followed the guide on porting in the development section and am trying to port a MIUI rom from the desire hd section using cm9 beta 5 as the base but it stays stuck in the MIUI.us united worldwide boot animation. I did a logcat and get the following errors at the end of it, it keeps on repeating this error.
I/ServiceManager( 1208): service 'media.audio_flinger' died
I/ServiceManager( 1208): service 'media.audio_policy' died
I/ServiceManager( 1208): service 'media.player' died
I/ServiceManager( 1208): service 'media.camera' died
ps. I left this overnight and never passed this section, any help would be greatly appreciated.