Database Info

[Q] App Installs from Market cause "Process System Not Responding" warning.

After installing or updating an app in the newest version of the android market I receive the warning "Process System is not responding" with the option to either force close or wait. I choose "wait" and everything continues as normal. It's not a major issue just a mild annoyance, also it interferes with automatic updates. I have tried fixing permissions, wiping dalvik cache, etc. but to no avail. Has anyone else seen this issue? I have googled this problem but haven't found too many relevant threads. I am running CM 7.1.0 android version 2.3.7 with Tiamat kernel 4.1.0 on a HTC EVO 4G.
Here is where I believe the timeout occured:
02-06 11:49:02.300 W/SharedBufferStack( 250): waitForCondition(LockCondition) timed out (identity=3, status=0). CPU may be pegged. trying again.
02-06 11:49:03.301 W/SharedBufferStack( 250): waitForCondition(LockCondition) timed out (identity=3, status=0). CPU may be pegged. trying again.
02-06 11:49:04.302 W/SharedBufferStack( 250): waitForCondition(LockCondition) timed out (identity=3, status=0). CPU may be pegged. trying again.
02-06 11:49:05.293 W/SharedBufferStack( 250): waitForCondition(LockCondition) timed out (identity=3, status=0). CPU may be pegged. trying again.
02-06 11:49:07.955 W/ActivityManager( 171): Timeout of broadcast BroadcastRecord{40b706d8 android.intent.action.PACKAGE_ADDED} - receiver=android.app.ActivityThread$ApplicationThr [email protected], started 10002ms ago
02-06 11:49:07.955 W/ActivityManager( 171): Receiver during timeout: ResolveInfo{40afb560 com.android.server.AppsLaunchFailureReceiver p=0 o=0 m=0x208000}
02-06 11:49:08.235 I/ActivityManager( 171): Start proc com.svox.pico for broadcast com.svox.pico/.VoiceDataInstallerReceiver: pid=2067 uid=10048 gids={}
Here is a longer log:
02-06 11:48:57.235 D/installd( 123): DexInv: --- END '/data/app/com.vevo-1.apk' (success) ---
02-06 11:48:57.245 D/PackageManager( 171): Registered content provider: com.vevo.SearchSuggestionsProvider, className = com.vevo.SearchSuggestionsProvider, isSyncable = false
02-06 11:48:57.245 D/PackageManager( 171): Providers: com.vevo.SearchSuggestionsProvider
02-06 11:48:57.245 D/PackageManager( 171): Services: com.vevo.services.VevoService
02-06 11:48:57.245 D/PackageManager( 171): Activities: com.vevo.Startup com.vevo.Home com.vevo.activities.VideosActivity com.vevo.MusicMapActivity com.vevo.QRCodeResultActivity com.vevo.ShareResult com.vevo.activities.RegistrationActivity com.vevo.PreferencesActivity com.vevo.activities.AboutActivity com.vevo.activities.ArtistsActivity com.vevo.activities.ViewArtistActivity com.vevo.PlaylistsActivity com.vevo.activities.MyPlaylistsActivity com.vevo.activities.ViewPlaylistActivity com.vevo.activities.WatchCompletionActivity com.vevo.activities.VevoWatchActivity com.vevo.FlashWatchActivity com.vevo.BrowserActivity com.vevo.activities.SearchResults
02-06 11:48:57.245 I/ActivityManager( 171): Force stopping package com.vevo uid=10144
02-06 11:48:57.435 I/installd( 123): move /data/dalvik-cache/[email protected]@[email protected] -> /data/dalvik-cache/[email protected]@[email protected]
02-06 11:48:57.445 D/PackageManager( 171): New package installed in /data/app/com.vevo-1.apk
02-06 11:48:57.965 D/szipinf ( 171): Initializing inflate state
02-06 11:48:57.975 D/HomeLoaders( 273): application intent received: android.intent.action.PACKAGE_ADDED, replacing=false
02-06 11:48:57.975 D/HomeLoaders( 273): --> package:com.vevo
02-06 11:48:57.975 D/HomeLoaders( 273): --> add package
02-06 11:48:58.106 D/dalvikvm( 171): JIT code cache reset in 3 ms (1048556 bytes 1/0)
02-06 11:48:58.116 D/dalvikvm( 171): GC_EXPLICIT freed 1458K, 34% free 8594K/12935K, external 1828K/2161K, paused 98ms
02-06 11:48:58.126 D/Finsky ( 1999): [9] 1.packageInstalled: Package install status for "com.vevo" is 1
02-06 11:48:58.276 D/szipinf ( 171): Initializing inflate state
02-06 11:48:59.247 D/szipinf ( 171): Initializing inflate state
02-06 11:48:59.657 D/szipinf ( 317): Initializing inflate state
02-06 11:48:59.657 D/szipinf ( 171): Initializing inflate state
02-06 11:48:59.687 D/szipinf ( 171): Initializing inflate state
02-06 11:48:59.707 D/szipinf ( 317): Initializing inflate state
02-06 11:48:59.757 D/szipinf ( 171): Initializing inflate state
02-06 11:48:59.777 D/szipinf ( 317): Initializing inflate state
02-06 11:48:59.817 D/szipinf ( 171): Initializing inflate state
02-06 11:48:59.917 D/szipinf ( 317): Initializing inflate state
02-06 11:48:59.927 D/szipinf ( 317): Initializing inflate state
02-06 11:49:00.067 D/szipinf ( 317): Initializing inflate state
02-06 11:49:00.088 D/szipinf ( 317): Initializing inflate state
02-06 11:49:00.148 D/szipinf ( 317): Initializing inflate state
02-06 11:49:00.248 D/szipinf ( 317): Initializing inflate state
02-06 11:49:02.300 W/SharedBufferStack( 250): waitForCondition(LockCondition) timed out (identity=3, status=0). CPU may be pegged. trying again.
02-06 11:49:03.301 W/SharedBufferStack( 250): waitForCondition(LockCondition) timed out (identity=3, status=0). CPU may be pegged. trying again.
02-06 11:49:04.302 W/SharedBufferStack( 250): waitForCondition(LockCondition) timed out (identity=3, status=0). CPU may be pegged. trying again.
02-06 11:49:05.293 W/SharedBufferStack( 250): waitForCondition(LockCondition) timed out (identity=3, status=0). CPU may be pegged. trying again.
02-06 11:49:07.955 W/ActivityManager( 171): Timeout of broadcast BroadcastRecord{40b706d8 android.intent.action.PACKAGE_ADDED} - [email protected], started 10002ms ago
02-06 11:49:07.955 W/ActivityManager( 171): Receiver during timeout: ResolveInfo{40afb560 com.android.server.AppsLaunchFailureReceiver p=0 o=0 m=0x208000}
02-06 11:49:08.235 I/ActivityManager( 171): Start proc com.svox.pico for broadcast com.svox.pico/.VoiceDataInstallerReceiver: pid=2067 uid=10048 gids={}
02-06 11:49:08.265 I/Process ( 171): Sending signal. PID: 171 SIG: 3
02-06 11:49:08.265 I/dalvikvm( 171): threadid=4: reacting to signal 3
02-06 11:49:08.286 I/ActivityThread( 2067): Pub com.svox.pico.providers.SettingsProvider: com.svox.pico.providers.SettingsProvider
02-06 11:49:08.366 I/ActivityManager( 171): No longer want com.google.android.maps.mytracks (pid 1520): hidden #16
02-06 11:49:08.386 D/GTalkService( 292): handlePackageInstalled: re-initialize providers
02-06 11:49:08.386 D/GTalkService( 292): [RawStanzaProvidersMgr] ##### searchProvidersFromIntent
02-06 11:49:08.386 D/GTalkService( 292): [RawStanzaProvidersMgr] no intent receivers found
02-06 11:49:08.396 I/dalvikvm( 171): Wrote stack traces to '/data/anr/traces.txt'
02-06 11:49:08.396 I/Process ( 171): Sending signal. PID: 265 SIG: 3
02-06 11:49:08.396 I/dalvikvm( 265): threadid=4: reacting to signal 3
02-06 11:49:08.396 I/ActivityManager( 171): Start proc com.google.android.partnersetup for broadcast com.google.android.partnersetup/.AppInstalledReceiver: pid=2075 uid=10015 gids={}

I've been having this same exact problem. I've tried fixing permissions which I thought had worked but the problem came back shortly. I'm wondering if it's a hardware problem or I need to completely wipe by unrooting and rooting again? Have you had any luck fixing this? I'm running Gummy Nex ROM 1.2.0 on Galaxy Nexus with Imoyesan's latest lean kernel.

Solar 2 (game) from Humble Indie Bundle Android #5 - not working

If anyone who bought the latest Humble Bundle and has managed to run the Solar 2 game, what ROM are you running?
I'm on CM10.1 and the game just never starts.
For anyone else interested, here is a link to it in the Google Play Store:
https://play.google.com/store/apps/details?id=com.murudai.Solar2
There is also a free demo.
Sent from my GT-N8013 using Tapatalk HD

Using stock ROM. I got the Humble Bundle as well.
The game works without problems.

Just chiming in
Not working on my SGS3 (I9300) either running CM10.1 nightly (2013/02/24)
The rest of the games seem to be running fine.
I'll update my rom and update this.
Edit: Latest nightly - no difference (I do like the new SuperUser though)
Here's the Logcat snippet:
Code:
03-06 11:48:51.205 I/ActivityManager(2264): Start proc com.murudai.Solar2.humble for activity com.murudai.Solar2.humble/solar2.Activity1: pid=10534 uid=10168 gids={50168, 1028}
03-06 11:48:51.210 D/dalvikvm(10534): Late-enabling CheckJNI
03-06 11:48:51.255 I/dalvikvm(10534): Turning on JNI app bug workarounds for target SDK version 13...
03-06 11:48:51.310 I/InputReader(2264): Reconfiguring input devices. changes=0x00000004
03-06 11:48:51.310 I/InputReader(2264): Device reconfigured: id=11, name='sec_touchscreen', size 720x1280, orientation 1, mode 1, display id 0
03-06 11:48:51.310 I/ActivityManager(2264): Config changes=1480 {1.0 272mcc5mnc en_GB ldltr sw360dp w640dp h335dp 320dpi nrml long land finger -keyb/v/h -nav/h s.112 themeResource=null}
03-06 11:48:51.385 E/Trace (10534): error opening trace file: No such file or directory (2)
03-06 11:48:51.425 D/dalvikvm(10534): Trying to load lib /data/app-lib/com.murudai.Solar2.humble-1/libmonodroid.so 0x4202dd98
03-06 11:48:51.430 D/dalvikvm(10534): Added shared lib /data/app-lib/com.murudai.Solar2.humble-1/libmonodroid.so 0x4202dd98
03-06 11:48:51.550 I/QuickSettingsController(30342): Tiles list: toggleUser|toggleBrightness|toggleSettings|toggleBluetooth|toggleWifi|toggleMobileData|toggleScreenTimeout|toggleAirplane|toggleAutoRotate|toggleGPS
03-06 11:48:51.575 D/BluetoothAdapter(30342): 1110089576: getState() : mService = null. Returning STATE_OFF
03-06 11:48:51.575 D/BluetoothAdapter(30342): 1110089576: getState() : mService = null. Returning STATE_OFF
03-06 11:48:51.575 D/BluetoothAdapter(30342): 1110089576: getState() : mService = null. Returning STATE_OFF
03-06 11:48:51.575 D/BluetoothAdapter(30342): 1110089576: getState() : mService = null. Returning STATE_OFF
03-06 11:48:51.575 D/BluetoothAdapter(30342): 1110089576: getState() : mService = null. Returning STATE_OFF
03-06 11:48:51.575 D/BluetoothAdapter(30342): 1110089576: getState() : mService = null. Returning STATE_OFF
03-06 11:48:51.645 E/mono (10534): WARNING: The runtime version supported by this application is unavailable.
03-06 11:48:51.645 E/mono (10534): Using default runtime: v2.0.50727
03-06 11:48:51.685 W/libc (10534): WARNING: generic atexit() called from legacy shared library
03-06 11:48:51.710 W/monodroid-gc(10534): GREF GC Threshold: 46800
03-06 11:48:51.730 D/dalvikvm(2264): GC_FOR_ALLOC freed 4602K, 34% free 34190K/51516K, paused 104ms, total 104ms
03-06 11:48:51.730 I/dalvikvm-heap(2264): Grow heap (frag case) to 35.614MB for 2073616-byte allocation
03-06 11:48:51.815 D/dalvikvm(2264): GC_FOR_ALLOC freed 21K, 33% free 36194K/53544K, paused 80ms, total 80ms
03-06 11:48:51.890 D/BluetoothAdapter(30342): 1110089576: getState() : mService = null. Returning STATE_OFF
03-06 11:48:51.935 D/dalvikvm(30342): GC_FOR_ALLOC freed 2159K, 24% free 36693K/48236K, paused 44ms, total 44ms
03-06 11:48:51.940 I/dalvikvm-heap(30342): Grow heap (frag case) to 38.058MB for 2073616-byte allocation
03-06 11:48:51.985 D/dalvikvm(30342): GC_FOR_ALLOC freed 16K, 24% free 38702K/50264K, paused 44ms, total 45ms
03-06 11:48:52.090 D/UsbTetherTile(30342): ACTION_TETHER_STATE_CHANGED
03-06 11:48:52.090 D/UsbTetherTile(30342): ACTION_USB_STATE
03-06 11:48:52.260 I/iNemoSensor(2264): enable(): handle(0), en(1), what(0)
03-06 11:48:52.260 D/AkmSensor(2264): akm_enable_sensor: Accel is enabled. (orien = 0)
03-06 11:48:52.260 I/AkmSensor(2264): enable_accelerometer, mEnabled = 0, enable = 1
03-06 11:48:52.260 D/iNemoSensor(2264): enable(): MASK_ACC (1) MASK_MAG (0) MASK_GYR (0)
03-06 11:48:52.260 D/iNemoSensor(2264): enable(): mEnAcc(1) mEnMag(0) mEnGyr(0)
03-06 11:48:52.260 I/iNemoSensor(2264): update_delay wanted_accel = 20000000
03-06 11:48:52.260 D/iNemoSensor(2264): setDelay(): handle(0), en(200000000)
03-06 11:48:52.260 I/iNemoSensor(2264): update_delay wanted_accel = 200000000
03-06 11:48:52.260 D/AkmSensor(2264): MeasureSNGLoop: interval.interval = 200000000, doze_max = 196000, prms->enabled = 2
03-06 11:48:52.265 D/iNemoSensor(2264): setDelay(): handle(0), en(66667000)
03-06 11:48:52.265 I/iNemoSensor(2264): update_delay wanted_accel = 66667000
03-06 11:48:52.460 D/AkmSensor(2264): MeasureSNGLoop: interval.interval = 66667000, doze_max = 65333, prms->enabled = 2
03-06 11:48:52.565 D/iNemoSensor(2264): setDelay(): handle(0), en(66667000)
03-06 11:48:52.565 I/iNemoSensor(2264): skip update_delay wanted_accel = 66667000 current delay = 66667000
03-06 11:48:52.565 W/SensorService(2264): sensor 00000000 already enabled in connection 0x5cec70d8 (ignoring)
03-06 11:48:52.565 D/iNemoSensor(2264): setDelay(): handle(0), en(20000000)
03-06 11:48:52.565 I/iNemoSensor(2264): update_delay wanted_accel = 20000000
03-06 11:48:52.595 D/AkmSensor(2264): MeasureSNGLoop: interval.interval = 20000000, doze_max = 19600, prms->enabled = 2
03-06 11:48:52.600 V/PhoneStatusBar(30342): setLightsOn(true)
03-06 11:48:52.640 D/MonoGame(10534): AndroidGameWindow.CreateFrameBuffer
03-06 11:48:52.660 D/libEGL (10534): loaded /system/lib/egl/libEGL_mali.so
03-06 11:48:52.665 D/libEGL (10534): loaded /system/lib/egl/libGLESv1_CM_mali.so
03-06 11:48:52.665 D/libEGL (10534): loaded /system/lib/egl/libGLESv2_mali.so
03-06 11:48:52.675 E/ (10534): Device driver API match
03-06 11:48:52.675 E/ (10534): Device driver API version: 17
03-06 11:48:52.675 E/ (10534): User space API version: 17
03-06 11:48:52.675 E/ (10534): mali: REVISION=Linux-r3p1-01rel1 BUILD_DATE=Thu Jan 24 17:16:14 KST 2013
03-06 11:48:52.765 D/MonoGame(10534): AndroidGameWindow.SurfaceCreated: surfaceFrame = Rect(0, 0 - 1280, 720)
03-06 11:48:52.785 D/MonoGame(10534): AndroidGameWindow.SurfaceChanged: format = Rgb565, width = 1280, height = 720
03-06 11:48:52.840 W/IInputConnectionWrapper(5908): showStatusIcon on inactive InputConnection
03-06 11:48:52.845 I/ActivityManager(2264): Displayed com.murudai.Solar2.humble/solar2.Activity1: +1s649ms
03-06 11:48:52.985 D/MonoGame(10534): GraphicsDeviceManager.ResetClientBounds: newClientBounds={X:0 Y:0 Width:1280 Height:720}
03-06 11:48:53.605 D/dalvikvm(10534): GC_CONCURRENT freed 300K, 19% free 2473K/3044K, paused 1ms+1ms, total 12ms
03-06 11:48:54.080 I/ActivityManager(2264): Process com.android.providers.calendar (pid 9981) has died.
03-06 11:48:54.280 D/dalvikvm(10534): GC_CONCURRENT freed 418K, 23% free 2480K/3204K, paused 1ms+1ms, total 11ms
03-06 11:48:54.315 D/dalvikvm(10534): GC_EXPLICIT freed 45K, 24% free 2436K/3204K, paused 1ms+1ms, total 14ms
03-06 11:48:55.040 D/dalvikvm(2264): GC_EXPLICIT freed 2234K, 37% free 34089K/53544K, paused 5ms+11ms, total 170ms
03-06 11:49:01.180 W/ActivityManager(2264): Launch timeout has expired, giving up wake lock!
03-06 11:49:01.370 W/ActivityManager(2264): Activity idle timeout for ActivityRecord{42577208 u0 com.murudai.Solar2.humble/solar2.Activity1}
03-06 11:49:16.020 D/dalvikvm(10534): GC_CONCURRENT freed 114K, 13% free 2705K/3076K, paused 2ms+1ms, total 13ms
03-06 11:49:16.355 I/InputDispatcher(2264): Application is not responding: Window{429fafe0 u0 com.murudai.Solar2.humble/solar2.Activity1}. It has been 5005.6ms since event, 5005.3ms since wait started. Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
03-06 11:49:16.355 I/WindowManager(2264): Input event dispatching timed out sending to com.murudai.Solar2.humble/solar2.Activity1
03-06 11:49:16.410 I/Process (2264): Sending signal. PID: 10534 SIG: 3
03-06 11:49:16.410 I/dalvikvm(10534): threadid=3: reacting to signal 3
03-06 11:49:16.440 I/dalvikvm(10534): Wrote stack traces to '/data/anr/traces.txt'
03-06 11:49:16.440 I/Process (2264): Sending signal. PID: 2264 SIG: 3
03-06 11:49:16.440 I/dalvikvm(2264): threadid=3: reacting to signal 3
03-06 11:49:16.455 D/dalvikvm(10534): GC_CONCURRENT freed <1K, 12% free 2710K/3076K, paused 3ms+0ms, total 17ms
03-06 11:49:16.800 E/Sensors (2264): poll() failed (Interrupted system call)
03-06 11:49:16.825 I/Process (2264): Sending signal. PID: 30342 SIG: 3
03-06 11:49:16.825 I/dalvikvm(30342): threadid=3: reacting to signal 3
03-06 11:49:16.825 I/dalvikvm(2264): Wrote stack traces to '/data/anr/traces.txt'
03-06 11:49:16.825 I/Process (2264): Sending signal. PID: 2595 SIG: 3
03-06 11:49:16.825 I/dalvikvm(2595): threadid=3: reacting to signal 3
03-06 11:49:16.915 I/dalvikvm(30342): Wrote stack traces to '/data/anr/traces.txt'
03-06 11:49:16.915 I/Process (2264): Sending signal. PID: 2601 SIG: 3
03-06 11:49:16.915 I/dalvikvm(2601): threadid=3: reacting to signal 3
03-06 11:49:16.920 I/dalvikvm(2595): Wrote stack traces to '/data/anr/traces.txt'
03-06 11:49:16.945 I/dalvikvm(2601): Wrote stack traces to '/data/anr/traces.txt'
03-06 11:49:17.220 D/dalvikvm(2264): GC_EXPLICIT freed 2249K, 36% free 34582K/53544K, paused 4ms+9ms, total 120ms
03-06 11:49:17.760 I/Process (2264): Sending signal. PID: 8417 SIG: 3
03-06 11:49:17.760 I/dalvikvm(8417): threadid=3: reacting to signal 3
03-06 11:49:17.850 I/dalvikvm(8417): Wrote stack traces to '/data/anr/traces.txt'
03-06 11:49:17.855 E/ActivityManager(2264): ANR in com.murudai.Solar2.humble (com.murudai.Solar2.humble/solar2.Activity1)
03-06 11:49:17.855 E/ActivityManager(2264): Reason: keyDispatchingTimedOut
03-06 11:49:17.855 E/ActivityManager(2264): Load: 1.24 / 1.1 / 2.01
03-06 11:49:17.855 E/ActivityManager(2264): CPU usage from 11393ms to 0ms ago:
03-06 11:49:17.855 E/ActivityManager(2264): 101% 10534/com.murudai.Solar2.humble: 101% user + 0.2% kernel / faults: 68 minor
03-06 11:49:17.855 E/ActivityManager(2264): 3.7% 8417/com.google.android.gm: 3.1% user + 0.6% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 2.3% 2264/system_server: 1.3% user + 1% kernel / faults: 282 minor 1 major
03-06 11:49:17.855 E/ActivityManager(2264): 1.5% 30342/com.android.systemui: 1.4% user + 0.1% kernel / faults: 3 minor
03-06 11:49:17.855 E/ActivityManager(2264): 0.1% 9733/kworker/0:2: 0% user + 0.1% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 0% 526/com.nuance.swype.beta:SwypeConnect: 0% user + 0% kernel / faults: 91 minor
03-06 11:49:17.855 E/ActivityManager(2264): 0% 891/irq/387-melfas-: 0% user + 0% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 0% 1895/surfaceflinger: 0% user + 0% kernel / faults: 140 minor
03-06 11:49:17.855 E/ActivityManager(2264): 0% 7556/kworker/u:27: 0% user + 0% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 0% 9290/kworker/u:0: 0% user + 0% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 0% 10390/com.nolanlawson.logcat: 0% user + 0% kernel / faults: 2 minor
03-06 11:49:17.855 E/ActivityManager(2264): 0% 10500/kworker/u:2: 0% user + 0% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 0% 25983/net.dinglisch.android.tasker: 0% user + 0% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 0% 28131/wpa_supplicant: 0% user + 0% kernel / faults: 37 minor
03-06 11:49:17.855 E/ActivityManager(2264): 26% TOTAL: 26% user + 0.4% kernel
03-06 11:49:17.855 E/ActivityManager(2264): CPU usage from 829ms to 1346ms later:
03-06 11:49:17.855 E/ActivityManager(2264): 101% 10534/com.murudai.Solar2.humble: 100% user + 1.9% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 98% 10534/i.Solar2.humble: 98% user + 0% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 1.9% 10552/er$SensorThread: 0% user + 1.9% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 3.8% 2264/system_server: 0% user + 3.8% kernel / faults: 1 minor
03-06 11:49:17.855 E/ActivityManager(2264): 3.8% 2348/InputDispatcher: 0% user + 3.8% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 3.8% 8417/com.google.android.gm: 3.8% user + 0% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 3.8% 8469/WebViewCoreThre: 3.8% user + 0% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 1.2% 3/ksoftirqd/0: 0% user + 1.2% kernel
03-06 11:49:17.855 E/ActivityManager(2264): 26% TOTAL: 25% user + 0.9% kernel
03-06 11:49:17.895 W/DropBoxManagerService(2264): Dropping: data_app_anr (10 > 0 bytes)
03-06 11:49:19.630 W/ActivityManager(2264): Force finishing activity com.murudai.Solar2.humble/solar2.Activity1
03-06 11:49:19.645 I/ActivityManager(2264): Killing ProcessRecord{42a1df28 10534:com.murudai.Solar2.humble/u0a10168}: user's request
03-06 11:49:19.720 W/InputDispatcher(2264): channel '429fafe0 com.murudai.Solar2.humble/solar2.Activity1 (server)' ~ Consumer closed input channel or an error occurred. events=0xd
03-06 11:49:19.720 E/InputDispatcher(2264): channel '429fafe0 com.murudai.Solar2.humble/solar2.Activity1 (server)' ~ Channel is unrecoverably broken and will be disposed!
03-06 11:49:19.720 I/iNemoSensor(2264): enable(): handle(0), en(0), what(0)
03-06 11:49:19.720 D/AkmSensor(2264): akm_disable_sensor: Accel is disabled. (orien = 0)
03-06 11:49:19.720 I/AkmSensor(2264): enable_accelerometer, mEnabled = 1, enable = 0
03-06 11:49:19.720 I/WindowState(2264): WIN DEATH: Window{42a1a0a0 u0 SurfaceView}
03-06 11:49:19.720 I/ActivityManager(2264): Process com.murudai.Solar2.humble (pid 10534) has died.
03-06 11:49:19.725 D/iNemoSensor(2264): enable(): MASK_ACC (0) MASK_MAG (0) MASK_GYR (0)
03-06 11:49:19.725 D/iNemoSensor(2264): enable(): mEnAcc(0) mEnMag(0) mEnGyr(0)
03-06 11:49:19.725 D/iNemoSensor(2264): setDelay(): handle(0), en(20000000)
03-06 11:49:19.725 W/InputDispatcher(2264): Attempted to unregister already unregistered input channel '429fafe0 com.murudai.Solar2.humble/solar2.Activity1 (server)'
03-06 11:49:19.725 I/WindowState(2264): WIN DEATH: Window{429fafe0 u0 com.murudai.Solar2.humble/solar2.Activity1}

Balls
Looks like its a CM10.1 compatibility error, then.
Sent from my GT-N8013 using Tapatalk HD

[THINK TANK] Are you having reboots/wifi issues on older firmware + JB?

I've seen some mention of these things lately, so I decided to pull it all together to see if there is really an issue here.
I was on 1.82 firmware/1.09 hboot until very recently, running JB roms/kernels. I was unstable to the point of getting 10+ reboots a day, almost always while the screen was off and I wasn't doing anything. During this period, I noticed some odd wifi behavior, such as wifi remaining stuck on even when the phone was asleep. Or, wifi would return an error when I tried to turn it on. Changing roms and kernels did not help. It continued no matter what I was running, no matter what kernel settings I was using.
Other people have mentioned similar problems, thought I'm not sure they're identical. I've begun to suspect there may be some incompatibilities between the original/early firmware and the newest bases and radios.
This weekend, I ruu'd to 2.20 and flashed the new AT&T ota, then flashed a new JB rom. So far, I haven't gotten any reboots, though it's too soon to be sure this has solved the problem (sometimes the reboots would stop for a day or two).
If anyone else has seen this, let's discuss it.
(Note: Please post only if you have something useful to contribute. Don't clutter this thread with "I love my phone, I've had no problems at all" posts)

Re: [THINK TANK] Are you having reboots/wifi issues on older firmware + JB
I'm on 1.85 I had reboots until I updated WiFi partitions when jelly bean first came out and has been reboot free ever since.
Sent from my HTC One X using xda premium

You brought up interesting points in the CR6 thread so I'm wondering if there's a good reason for someone like me (hboot 1.09 and s-off) to upgrade the firmware without creating a mess somewhere else. I do notice random reboots in some ROMs. Mostly with Sense ROMs to be honest. When I flash back to CM I don't notice any reboots unless it's a bug in the nightlies or a known issue (GPS for instance was crashing CM at one point).
That said, h8rift (Evita's CM maintainer) advocates downgrading touchscreen firmware to be able to use any AOSP ROM. In his thread on downgrading, he calls out 2.14 OTA but I'd imagine this would also apply to 2.20, no? Seems like the 1.09 crowd has to pick between instabilities in Sense/stable AOSP and stable Sense and no AOSP.
Thoughts?

There may be something to this. I've seen a lot of /proc/last_kmsg and some of them have reboots caused by wifi failing to suspend properly. IIRC, basically it tries to suspend but wakes up repeatedly until it has an unrecoverable crash and the system shuts down. I don't have any of these handy, but if anyone gets a random reboot while the phone is off, post /proc/last_kmesg here for reference. It may be of help figuring out what the problem is.

I suspect it is indeed a Sense issue. I don't think it's been reported on AOSP roms.
As far as upgrading like I did, I've never been into AOSP on my HOX, so I'm not concerned about the touchscreen issue. But if you want AOSP, I believe you're stuck with earlier hboots until someone comes up with a fix.
Note that 2.20 is the AT&T 4.0.4 base; 2.14 is the JB hboot. The latest AT&T base is 3.18.

Re: [THINK TANK] Are you having reboots/wifi issues on older firmware + JB
I have only gotten a WiFi induced reboot in a very low signal (ie unusable) area. It would just keep trying to reconnect until it finally reboot. I upped the voltage to stock and it seemed to go away.
I had/have firmware 1.73 and hboot 1.09. Currently running ElementalX bulletproof, CleanROM JB beta, 3.18 radio + RIL. Haven't had any reboots in months.
Sent from my HTC One X using xda premium
Sent from my HTC One X using xda premium

ECEXCURSION said:
I have only gotten a WiFi induced reboot in a very low signal (ie unusable) area. It would just keep trying to reconnect until it finally reboot. I upped the voltage to stock and it seemed to go away.
Click to expand...
Click to collapse
I tried playing with my voltage, and it didn't help. Even "extra" voltage didn't stop the reboots.

I was having major reboot issues as well. I was about to ruu to 2.20 when I played with voltage on the latest elemental kernel and viper's latest and have been ok. I have had one reboot over volted and lag with chrome here and there. I still may upgrade.

Updated my HOX to CR6, and have reboots
Loaded CR6, and radio 0.24p.32.09.06_10.130.32.34L. I've been having random reboots since. I'll have the phone on my desk, screen off, and see the phone turn on, and reboot. I grabbed catlog, and set it to log Info and above. Now have running debug and above. wireless does do several scans before the reboot, but here are a few seconds before it does the reboot...
3-11 17:45:47.841 W/LocSvc_adapter( 603): W/virtual loc_api_adapter_err LocApiAdapter::enableData(int): default implementation invoked
03-11 17:45:47.841 W/LocSvc_adapter( 603): W/virtual loc_api_adapter_err LocApiAdapter::setAPN(char*, int): default implementation invoked
03-11 17:45:47.891 I/ActivityThread( 7215): Pub com.google.android.youtube.SuggestionProvider: com.google.android.youtube.core.suggest.SuggestionProvider
03-11 17:45:47.911 I/PackageManager( 603): setEnabledSetting(), pkgName=com.google.android.youtube, clsName=com.google.android.youtube.app.prefetch.PrefetchService, state=1, flag=1, pid=7215, uid=10139
03-11 17:45:47.911 I/PackageManager( 603): setEnabledSetting(), pkgName=com.google.android.youtube, clsName=com.google.android.youtube.app.prefetch.PrefetchService$DeviceStateReceiver, state=1, flag=1, pid=7215, uid=10139
03-11 17:45:48.421 W/AlarmManager( 603): RXTXtriggerAlarmsLocked
03-11 17:45:48.461 I/ConversionPing( 7215): Sending ping:[http-edited out so I can post]googleads.g.doubleclick.net/pagead/viewthroughconversion/[/url][removed]
03-11 17:45:48.502 I/ActivityManager( 603): Start proc com.htc.cs.dm for broadcast com.htc.cs.dm/.receiver.NetworkChangeReceiver: pid=7260 uid=10028 gids={3003, 1028}
03-11 17:45:48.512 E/ConversionPing( 7215): ConversionPing could not reach the url, no conversion sent.
03-11 17:45:48.562 I/ActivityThread( 7260): Pub com.htc.cs.dm: com.htc.cs.dm.provider.ConfigCacheProvider
03-11 17:45:48.562 I/ActivityManager( 603): No longer want com.htc.idlescreen.base (pid 6298): hidden #16, adj=15
03-11 17:45:48.582 I/ActivityManager( 603): Recipient 6298
03-11 17:45:48.602 I/ActivityManager( 603): Start proc com.google.android.gcm for broadcast com.google.android.gms/.gcm.ServiceAutoStarter: pid=7277 uid=10024 gids={3003, 1015, 1028, 2001, 1007, 3006}
03-11 17:45:48.642 I/ActivityManager( 603): No longer want com.cequint.ecid (pid 6336): hidden #16, adj=15
03-11 17:45:48.652 I/ActivityManager( 603): Recipient 6336
03-11 17:45:48.702 I/ActivityManager( 603): No longer want com.google.android.gsf.login (pid 5955): hidden #16, adj=15
03-11 17:45:48.732 E/TelephonyManager( 1234): Hidden constructor called more than once per process!
03-11 17:45:48.732 E/TelephonyManager( 1234): Original: com.google.android.location, new: com.google.android.gsf
03-11 17:45:48.752 I/ActivityManager( 603): Recipient 5955
03-11 17:45:48.762 I/ActivityManager( 603): Start proc com.cequint.ecid for broadcast com.cequint.ecid/com.cequint.cityid.CityIdBroadcastReceiver: pid=7296 uid=10008 gids={3003, 1015, 1028}
03-11 17:45:48.852 I/ActivityThread( 7296): Pub com.cequint.ecid: com.cequint.cityid.CallerIdContentProvider
03-11 17:45:48.852 I/ActivityThread( 7296): Pub com.cequint.cityid: com.cequint.cityid.CityIdContentProvider
03-11 17:45:48.872 I/PackageManager( 603): setEnabledSetting(), pkgName=com.cequint.ecid, clsName=com.cequint.cityid.activity.UserLaunch, state=2, flag=1, pid=7296, uid=10008
03-11 17:45:48.882 I/ActivityManager( 603): Start proc com.htc.reportagent for broadcast com.htc.reportagent/.receiver.NetworkChangeReceiver: pid=7311 uid=10099 gids={3003, 1007, 1028}
03-11 17:45:48.882 I/ActivityManager( 603): No longer want com.htc.android.worldclock (pid 6492): hidden #16, adj=15
03-11 17:45:48.942 I/ActivityManager( 603): Start proc com.google.android.apps.uploader for broadcast com.google.android.apps.uploader/com.google.android.picasasync.ConnectivityReceiver: pid=7324 uid=10094 gids={3003, 1015, 1028}
03-11 17:45:48.952 I/ActivityManager( 603): Recipient 6492
03-11 17:45:48.992 I/ActivityThread( 7324): Pub com.google.android.apps.uploader.PicasaUploadProvider: com.google.android.picasasync.PicasaContentProvider
03-11 17:45:49.042 I/EASAppSvc( 6530): [ NA ]- onCreate()
03-11 17:45:49.052 I/PackageManager( 603): setEnabledSetting(), pkgName=com.htc.android.mail, clsName=com.htc.android.mail.eassvc.EASEventReceiver, state=1, flag=1, pid=6530, uid=10092
03-11 17:45:49.072 I/ActivityManager( 603): Start proc com.chrome.beta for broadcast com.chrome.beta/com.google.android.apps.chrome.preferences.ConnectionChangeReceiver: pid=7342 uid=10221 gids={3003, 1006, 1015, 1028}
03-11 17:45:49.142 I/ActivityThread( 7342): Pub com.chrome.beta.snapshot: com.google.android.apps.chrome.snapshot.SnapshotProvider
03-11 17:45:49.142 I/ActivityThread( 7342): Pub com.chrome.beta.ChromeBrowserProvider;com.chrome.beta.browser;com.chrome.beta: com.google.android.apps.chrome.ChromeBrowserProvider
03-11 17:45:49.192 I/ActivityManager( 603): Start proc com.google.android.apps.plus for broadcast com.google.android.apps.plus/com.google.android.picasasync.ConnectivityReceiver: pid=7361 uid=10186 gids={3003, 3002, 1015, 1006, 1028}
03-11 17:45:49.302 I/ActivityThread( 7361): Pub com.google.android.apps.plus.content.ApiProvider: com.google.android.apps.plus.content.EsApiProvider
03-11 17:45:49.302 I/ActivityThread( 7361): Pub com.google.android.apps.plus.content.EsGooglePhotoProvider: com.google.android.picasasync.PicasaContentProvider
03-11 17:45:49.352 I/ActivityThread( 7361): Pub com.google.android.apps.plus.iu.EsGoogleIuProvider: com.google.android.apps.plus.iu.InstantUploadProvider
03-11 17:45:49.382 I/ActivityThread( 7361): Pub com.google.android.apps.plus.content.EsPicasaStoreProvider: com.google.android.picasastore.PicasaPhotoContentProvider
03-11 17:45:49.392 I/ActivityThread( 7361): Pub com.google.plus.platform: com.google.android.apps.plus.content.AdsProvider
03-11 17:45:49.392 I/ActivityThread( 7361): Pub com.google.android.apps.plus.content.EsProvider: com.google.android.apps.plus.content.EsProvider
03-11 17:45:50.173 I/MediaScannerConnection( 7361): ===== scanFile =====
03-11 17:45:50.253 W/MPL-sup ( 603): MLGetAKMComassStatus, gAKMCompassStatus = 0
03-11 17:45:50.253 I/ ( 603): mpu3050_suspend: suspending sensors to 0000
03-11 17:45:50.253 I/ ( 603): mpu3050_suspend: Will resume next to 0070
03-11 17:45:50.444 I/dalvikvm-heap( 7361): Grow heap (frag case) to 46.359MB for 33554448-byte allocation
03-11 17:45:50.604 I/LocationManagerService( 603): request passive (pid 5114) 5000 0
03-11 17:45:50.614 E/TelephonyManager( 1234): Hidden constructor called more than once per process!
03-11 17:45:50.614 E/TelephonyManager( 1234): Original: com.google.android.location, new: com.google.android.gsf
03-11 17:45:50.624 W/MediaProvider( 6360): genre is an empty string, do not insert it
03-11 17:45:50.654 I/PackageManager( 603): setEnabledSetting(), pkgName=com.cequint.ecid, clsName=com.cequint.cityid.activity.UserLaunch, state=2, flag=1, pid=7296, uid=10008
03-11 17:45:50.764 I/PackageManager( 603): setEnabledSetting(), pkgName=com.google.android.music, clsName=com.google.android.music.leanback.AutoCachingService$ActionReceiver, state=1, flag=1, pid=7189, uid=10097
03-11 17:45:50.824 I/ActivityManager( 603): Start proc com.google.android.gms for broadcast com.google.android.gms/.recovery.AccountRecoveryService$Receiver: pid=7395 uid=10024 gids={3003, 1015, 1028, 2001, 1007, 3006}
03-11 17:45:50.914 I/ActivityThread( 7395): Pub com.google.android.gms.plus;com.google.android.gms.plus.action: com.google.android.gms.plus.provider.PlusProvider
03-11 17:45:50.924 I/Recovery( 7395): Received: Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.recovery.AccountRecoveryService$Receiver }
03-11 17:45:50.944 I/Recovery( 7395): Received: Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.recovery.AccountRecoveryService$Receiver }
03-11 17:45:50.944 I/ActivityManager( 603): Start proc com.google.android.gsf.login for service com.google.android.gms/.recovery.AccountRecoveryService: pid=7408 uid=10024 gids={3003, 1015, 1028, 2001, 1007, 3006}
03-11 17:45:51.014 I/ActivityManager( 603): No longer want com.htc.task (pid 6514): hidden #16, adj=15
03-11 17:45:51.024 I/Recovery( 7395): Received: Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.recovery.AccountRecoveryService$Receiver }
03-11 17:45:51.034 I/ActivityManager( 603): Recipient 6514
03-11 17:45:51.114 I/ActivityManager( 603): No longer want com.alfray.timeriffic (pid 6547): hidden #16, adj=15
03-11 17:45:51.124 I/ActivityManager( 603): Recipient 6547
03-11 17:45:51.655 I/wpa_supplicant( 5634): DISCONNECT enter
03-11 17:45:51.655 I/wpa_supplicant( 5634): wlan0: State: SCANNING -> DISCONNECTED
03-11 17:45:51.655 I/wpa_supplicant( 5634): wpa_supplicant_set_state -
03-11 17:45:51.655 I/wpa_ctrl( 603): [wpa_ctrl_request] ctrl address = 55a137b8, ctrl_conn address = 0
03-11 17:45:52.776 I/PackageManager( 603): setEnabledSetting(), pkgName=com.google.android.music, clsName=com.google.android.music.leanback.AutoCachingService$ActionReceiver, state=1, flag=1, pid=7189, uid=10097
03-11 17:45:54.288 I/wpa_supplicant( 5634): wlan0: CTRL-EVENT-DRIVER-STATE STOPPED
03-11 17:45:54.288 I/wpa_supplicant( 5634): wlan0: State: DISCONNECTED -> DISCONNECTED
03-11 17:45:54.288 I/wpa_supplicant( 5634): wpa_supplicant_set_state -
03-11 17:45:54.288 I/wpa_supplicant( 5634): wlan0: State: DISCONNECTED -> INTERFACE_DISABLED
03-11 17:45:54.288 I/wpa_supplicant( 5634): wpa_supplicant_set_state -
03-11 17:45:54.288 I/wpa_ctrl( 603): [wpa_ctrl_request] ctrl address = 55a137b8, ctrl_conn address = 0
03-11 17:45:55.449 I/ActivityManager( 603): Recipient 5998
03-11 17:45:55.449 I/ActivityManager( 603): Process com.nitrodesk.droid20.nitroid (pid 5998) has died.
03-11 17:45:55.449 W/ActivityManager( 603): Scheduling restart of crashed service com.nitrodesk.droid20.nitroid/com.nitrodesk.daemon.ActiveSyncListenerSvc in 5000ms
03-11 17:45:55.789 W/ActivityManager( 603): Scheduling restart of crashed service com.nitrodesk.droid20.nitroid/com.nitrodesk.daemon.ExchangeListenerSvc in 14658ms
03-11 17:45:57.061 I/ActivityManager( 603): No longer want com.google.android.gm (pid 6209): hidden #16, adj=15
03-11 17:45:57.131 I/ActivityManager( 603): Recipient 6209
03-11 17:45:58.152 I/ActivityManager( 603): No longer want com.htc.htcpowermanager:remote (pid 5086): hidden #16, adj=15
03-11 17:45:58.212 I/ActivityManager( 603): Recipient 5086
03-11 17:46:00.514 I/ActivityManager( 603): Start proc com.nitrodesk.droid20.nitroid for service com.nitrodesk.droid20.nitroid/com.nitrodesk.daemon.ActiveSyncListenerSvc: pid=7467 uid=10163 gids={3003, 1015, 1028}
03-11 17:46:00.705 I/ActivityThread( 7467): Pub com.nitrodesk.dataproviders.TouchDownExt: com.nitrodesk.libraries.data.ExternalContentProvider
03-11 17:46:00.725 I/ActivityThread( 7467): Pub com.nitrodesk.droid20.dataproviders.FolderViewProvider: com.nitrodesk.nitroid.FolderViewProvider
03-11 17:46:00.725 I/ActivityThread( 7467): Pub com.nitrodesk.droid20.dataproviders.WindroidDataProvider: com.nitrodesk.nitroid.WindroidDataProvider

iElvis said:
I've seen some mention of these things lately, so I decided to pull it all together to see if there is really an issue here.
I was on 1.82 firmware/1.09 hboot until very recently, running JB roms/kernels. I was unstable to the point of getting 10+ reboots a day, almost always while the screen was off and I wasn't doing anything. During this period, I noticed some odd wifi behavior, such as wifi remaining stuck on even when the phone was asleep. Or, wifi would return an error when I tried to turn it on. Changing roms and kernels did not help. It continued no matter what I was running, no matter what kernel settings I was using.
Other people have mentioned similar problems, thought I'm not sure they're identical. I've begun to suspect there may be some incompatibilities between the original/early firmware and the newest bases and radios.
This weekend, I ruu'd to 2.20 and flashed the new AT&T ota, then flashed a new JB rom. So far, I haven't gotten any reboots, though it's too soon to be sure this has solved the problem (sometimes the reboots would stop for a day or two).
If anyone else has seen this, let's discuss it.
(Note: Please post only if you have something useful to contribute. Don't clutter this thread with "I love my phone, I've had no problems at all" posts)
Click to expand...
Click to collapse
iElvis, are you suggesting that we update the hboot version from 1.09 to 2.14 or newer? I'm S-OFF, so I don't think it really matters unless I want to use AOSP, which would just mean to downgrade right? I'm 1.09, and after seeing you using ElementalX on CR6, I decided to follow suit and the reboots still happen.

this morning my phone rebooted itself 3 time while it was in my pocket. I took it out , and played with it . When I opened Google now , the app was frozen and then my phone rebooted again. I disabled Google now and my phone is running fine until now. Maybe something relate to Google now I guess .
Sent from my HTC One X using Tapatalk 2

xandr115 said:
iElvis, are you suggesting that we update the hboot version from 1.09 to 2.14 or newer? I'm S-OFF, so I don't think it really matters unless I want to use AOSP, which would just mean to downgrade right? I'm 1.09, and after seeing you using ElementalX on CR6, I decided to follow suit and the reboots still happen.
Click to expand...
Click to collapse
What I did was fully update my firmware and hboot. My phone came with 1.73 and I ran the 1.82 ruu when it came out, then never did anything else beyond flashing roms and kernels. That's what I suspect starting causing reboots at some point. It wasn't the roms or kernels because they continued no matter what I was on, including stock roms.
As long as you're s-off, you can update everything like I did, then flash back to 1.09 hboot if you're concerned about the AOSP touchscreen bug.
I'm going on three days with my new setup and haven't had a single reboot or any instability.
Edit: The AOSP thing requires downgrading the touchscreen firmware, not hboot. Got that mixed up.

iElvis said:
What I did was fully update my firmware and hboot. My phone came with 1.73 and I ran the 1.82 ruu when it came out, then never did anything else beyond flashing roms and kernels. That's what I suspect starting causing reboots at some point. It wasn't the roms or kernels because they continued no matter what I was on, including stock roms.
As long as you're s-off, you can update everything like I did, then flash back to 1.09 hboot if you're concerned about the AOSP touchscreen bug.
I'm going on three days with my new setup and haven't had a single reboot or any instability.
Click to expand...
Click to collapse
So what firmware and hboot are you based on right now? Thanks, phone's rebooted twice in the past few minutes.

xandr115 said:
So what firmware and hboot are you based on right now? Thanks, phone's rebooted twice in the past few minutes.
Click to expand...
Click to collapse
3.18 and 2.14.
If it's just rebooting on its own for no apparent reason, you've likely got the wifi bug.

You know, noe that I think about it, I never had reboots. But my hox refuses to stay connected to WiFi, using 1.85 firmware/1.09 hboot. While my nexus 4 RARELY has issues. Part of the issue is the router, but my n4 works flawlessly on WiFi compared to my hox
Sent from my Nexus 4

mirGantrophy said:
You know, noe that I think about it, I never had reboots. But my hox refuses to stay connected to WiFi, using 1.85 firmware/1.09 hboot. While my nexus 4 RARELY has issues. Part of the issue is the router, but my n4 works flawlessly on WiFi compared to my hox
Sent from my Nexus 4
Click to expand...
Click to collapse
I had the same problem. Same hboot and firmware as you. Mine would also reboot in low WiFi signal areas trying to connect over and over and finally give up and reboot. After the WiFi update it will now stay connected and I don't think I have had a reboot since.
Sent from my HTC One X using xda premium

Do you guys think the hboot could have anything to do with why I can't flash certain rom's on my phone. I have hboot 1.14 and downgraded touch panel but still can't flash miui since going soff.
Sent from my HTC One X using xda premium
---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------
Zonen said:
Do you guys think the hboot could have anything to do with why I can't flash certain rom's on my phone. I have hboot 1.14 and downgraded touch panel but still can't flash miui since going soff.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
By the way I did a 2.20 ruu as well to try to fix this but no luck. Viper flashes, xylon works, clean rom works, but no miui.
Sent from my HTC One X using xda premium

Yesterday I noticed that I had forgotten to apply Turge's JB Wifi partition update after I had jumped back and forth between ROMs. Since I applied the partition update I haven't had a reboot. All the other Sense ROMs randomly reboot on me so I'm thinking that's part of it. Firmware may be a factor too. I'm not aware of another Sense ROM that takes into account the wifi paritition so maybe that's the culprit, especially with early hboots?
If I get the itch to jump to CleanROM or another I'm going to upgrade the firmware/hboot since I'm s-off. For now Viper is running really well and no reboots in the past 34 or so hours. I'm running 3.2.6 w/ flar's Bulletproof kernel.

edditnyc said:
Yesterday I noticed that I had forgotten to apply Turge's JB Wifi partition update after I had jumped back and forth between ROMs. Since I applied the partition update I haven't had a reboot. All the other Sense ROMs randomly reboot on me so I'm thinking that's part of it. Firmware may be a factor too. I'm not aware of another Sense ROM that takes into account the wifi paritition so maybe that's the culprit, especially with early hboots?
If I get the itch to jump to CleanROM or another I'm going to upgrade the firmware/hboot since I'm s-off. For now Viper is running really well and no reboots in the past 34 or so hours. I'm running 3.2.6 w/ flar's Bulletproof kernel.
Click to expand...
Click to collapse
Hasn't been nearly quite as long, but I've been running for a couple of hours with the 2.14 hboot now (upgraded from 1.09) on Cleanrom 6. So far so good.

draziw1 said:
Loaded CR6, and radio 0.24p.32.09.06_10.130.32.34L. I've been having random reboots since. I'll have the phone on my desk, screen off, and see the phone turn on, and reboot. I grabbed catlog, and set it to log Info and above. Now have running debug and above. wireless does do several scans before the reboot, but here are a few seconds before it does the reboot...
Click to expand...
Click to collapse
I used RRU: htc_one_x_RUU_2.20.502.7_att_us_08022012.zip, which bumped hboot up, and rolled the radio back... Then had it take the OTA, which bumped hboot up, and bumped the radio. I set wifi to allow sleep. It is no longer self-rebooting (at least not in > 1h, before it happened in < 20m), but, when I've picked the phone up after not using it, it has shown wifi still up, instead of off, then re-establishing after screen wake..edit: I'm not sure which change did it, but wifi is now sleeping normally. Only downside I still see vs my prior 4.0 install is the sense weather clock will show the state, or county weather instead of my city weather.

[Q] How to completely and permanently disable wifi?

My nexus 5 has a broken wifi. I just upgraded to Lollipop and it appears that whenever the phone goes into sleep, it'll try to initilize the wifi and run into some error. This causes the phone to reboot and the same error repeat itself during the next sleep cycle. The catlog as follows:
I/PowerManagerService(23996): Going to sleep due to power button (uid 1000)...
E/Sensors ( 186): sns_acm_mr.c(432):Transport error -45
I/PowerManagerService(23996): Sleeping (uid 1000)...
I/Adreno-EGL(23996): <qeglDrvAPI_eglInitialize:410>: QUALCOMM Build: 10/24/14, 167c270, I68fa98814b
I/WifiNative-HAL(23996): startHal
E/wifi (23996): getStaticLongField sWifiHalHandle 0x9d7fb86c
I/WifiHAL (23996): Initializing wifi
I/WifiHAL (23996): Creating socket
I/WifiHAL (23996): Initialized Wifi HAL Successfully; vendor cmd = 103
D/wifi (23996): Did set static halHandle = 0xb3e33040
D/wifi (23996): halHandle = 0xb3e33040, mVM = 0xb4f5c280, mCls = 0x40162a
E/wifi (23996): getStaticLongField sWifiHalHandle 0x9d7fb81c
D/wifi (23996): array field set
D/PhoneStatusBar(24166): disable: < expand ICONS alerts SYSTEM_INFO back HOME RECENT clock SEARCH >
F/libc (23996): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x5000001 in tid 24123 (WifiStateMachin)
I/libc (23996): Suppressing debuggerd output because prctl(PR_GET_DUMPABLE)==0
I/ServiceManager( 164): service 'country_detector' died
Is there a way to totally disable or remove the wifi device? I know I should get the device RMA but due to some constrain, I am unable to do it now. Any help appreciated.

I'm investigating the same problem. Currently no progress.
I have discussed this issue in thread: http://forum.xda-developers.com/google-nexus-5/help/android-5-0-rebooting-screen-shut-off-t2938805

AOSP 11 for Pixel 5A (barbet) - no audio in calls.

I am running AOSP on the Pixel 5A (Android 11). When I make or receive a call, the call seems to go through, but I get no audio. I have tried the headset and speakerphone.
I can hear other system sounds and alerts -- it's just an issue for calls. I have tried this on the June, September, and October releases, with the same results.
Does anyone else have this issue, or, more to the point, know the solution?
Looking at logcat, I get the following, repeated constantly, (which I presume is related to the problem):
10-12 17:26:26.366 875 875 D Zygote : Forked child process 9118
10-12 17:26:26.368 9118 9118 I libc : SetHeapTaggingLevel: tag level set to 0
10-12 17:26:26.372 1474 1632 I ActivityManager: Start proc 9118:com.qualcomm.qti.telephonyservice/1001 for restart com.qualcomm.qti.telephonyservice
10-12 17:26:26.375 1047 1089 I adbd : jdwp connection from 9118
10-12 17:26:26.384 9118 9118 I elephonyservic: The ClassLoaderContext is a special shared library.
10-12 17:26:26.388 9118 9118 D NetworkSecurityConfig: No Network Security Config specified, using platform default
10-12 17:26:26.388 9118 9118 D NetworkSecurityConfig: No Network Security Config specified, using platform default
10-12 17:26:26.389 9118 9118 I QtiTelephonyService: onCreate:
10-12 17:26:26.389 9118 9118 D AndroidRuntime: Shutting down VM
10-12 17:26:26.389 9118 9118 E AndroidRuntime: FATAL EXCEPTION: main
10-12 17:26:26.389 9118 9118 E AndroidRuntime: Process: com.qualcomm.qti.telephonyservice, PID: 9118
10-12 17:26:26.389 9118 9118 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/qualcomm/qcrilhook/QcRilHook;
10-12 17:26:26.389 9118 9118 E AndroidRuntime: at com.qualcomm.qti.telephonyservice.QtiTelephonyService.onCreate(QtiTelephonyService.java:62)
10-12 17:26:26.389 9118 9118 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
10-12 17:26:26.389 9118 9118 E AndroidRuntime: at android.app.ActivityThread.access$1500(ActivityThread.java:237)
10-12 17:26:26.389 9118 9118 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
10-12 17:26:26.389 9118 9118 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-12 17:26:26.389 9118 9118 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-12 17:26:26.389 9118 9118 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7664)
10-12 17:26:26.389 9118 9118 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-12 17:26:26.389 9118 9118 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
10-12 17:26:26.389 9118 9118 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-12 17:26:26.389 9118 9118 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: com.qualcomm.qcrilhook.QcRilHook
10-12 17:26:26.389 9118 9118 E AndroidRuntime: ... 10 more
10-12 17:26:26.391 1474 1630 V RescueParty: Disabled because of active USB connection
10-12 17:26:26.391 1474 1616 W ActivityManager: Process com.qualcomm.qti.telephonyservice has crashed too many times: killing!
10-12 17:26:26.392 9118 9118 I Process : Sending signal. PID: 9118 SIG: 9
10-12 17:26:26.399 875 875 I Zygote : Process 9118 exited due to signal 9 (Killed)
10-12 17:26:26.399 1474 1616 I ActivityManager: Process com.qualcomm.qti.telephonyservice (pid 9118) has died: pers PER
10-12 17:26:26.400 1474 1633 I libprocessgroup: Successfully killed process cgroup uid 1001 pid 9118 in 0ms
10-12 17:26:26.400 1474 1616 W ActivityManager: Scheduling restart of crashed service com.qualcomm.qti.telephonyservice/.QtiTelephonyService in 0ms for persistent
10-12 17:26:26.400 1474 1616 W ActivityManager: Re-adding persistent process ProcessRecord{d872c28 9118:com.qualcomm.qti.telephonyservice/1001}
10-12 17:26:26.401 1474 1616 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 1001; state: DISABLED
10-12 17:26:26.401 1474 1616 D CompatibilityChangeReporter: Compat change id reported: 135754954; UID 1001; state: DISABLED
Looking at adb shell dumpsys package output, I do see the qcrilhook listed under Libraries:
com.qualcomm.qcrilhook -> (jar) /system_ext/framework/qcrilhook.jar
I also see it listed in the usesLibraires section of the telephonyservice package:
Package [com.qualcomm.qti.telephonyservice] (683ce82):
userId=1001
sharedUser=SharedUserSetting{4ce8a18 android.uid.phone/1001}
pkg=Package{bb21669 com.qualcomm.qti.telephonyservice}
codePath=/system_ext/app/QtiTelephonyService
resourcePath=/system_ext/app/QtiTelephonyService
legacyNativeLibraryDir=/system_ext/app/QtiTelephonyService/lib
primaryCpuAbi=null
secondaryCpuAbi=null
versionCode=30 minSdk=30 targetSdk=29
versionName=11
splits=[base]
apkSigningVersion=3
applicationInfo=ApplicationInfo{bb21669 com.qualcomm.qti.telephonyservice}
flags=[ SYSTEM HAS_CODE PERSISTENT ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
privateFlags=[ PRIVATE_FLAG_ACTIVITIES_RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION ALLOW_AUDIO_PLAYBACK_CAPTURE DIRECT_BOOT_AWARE SYSTEM_EXT PRIVATE_FLAG_ALLOW_NATIVE_HEAP_POINTER_TAGGING ]
forceQueryable=false
queriesPackages=[]
dataDir=/data/user/0/com.qualcomm.qti.telephonyservice
supportsScreens=[small, medium, large, xlarge, resizeable, anyDensity]
usesLibraries:
android.test.base
com.qualcomm.qcrilhook
qti-telephony-hidl-wrapper
qti-telephony-utils
timeStamp=2021-10-11 17:41:33
firstInstallTime=2021-10-11 17:41:33
lastUpdateTime=2021-10-11 17:41:33
signatures=PackageSignatures{bddb8ee version:3, signatures:[b4addb29], past signatures:[]}
installPermissionsFixed=false
pkgFlags=[ SYSTEM HAS_CODE PERSISTENT ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
declared permissions:
com.qualcomm.qti.permission.USE_QTI_TELEPHONY_SERVICE: prot=signature|privileged, INSTALLED
com.qualcomm.qti.permission.ACCESS_USER_AUTHENTICATION_APIS: prot=signature|privileged, INSTALLED
User 0: ceDataInode=2169 installed=true hidden=false suspended=false distractionFlags=0 stopped=false notLaunched=false enabled=0 instant=false virtual=false

Figured this out, so posting answer in case anyone else runs into the same issue (or in case I hit it again in a year and can' t remember what I did.)
1) Add the following .xml files in vendor/qcom/barbet/proprietary. (I copied them from sunfish) :
qti_telephony_hidl_wrapper.xml
qti_telephony_utils.xml
2) Update device-partial.mk in vendor/qcom/barbet to copy these new files along with the other .xmls.