[Q] getting error run basic android app of hello world...... - General Questions and Answers

on Console getting this :
[2015-05-01 20:20:07 - HelloFriend] ------------------------------
[2015-05-01 20:20:07 - HelloFriend] Android Launch!
[2015-05-01 20:20:07 - HelloFriend] adb is running normally.
[2015-05-01 20:20:07 - HelloFriend] Performing com.example.hellofriend.MainActivity activity launch
[2015-05-01 20:20:08 - HelloFriend] Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'AsdPh'
[2015-05-01 20:20:08 - HelloFriend] Uploading HelloFriend.apk onto device 'emulator-5554'
[2015-05-01 20:20:11 - HelloFriend] Installing HelloFriend.apk...
[2015-05-01 20:22:29 - HelloFriend] Failed to install HelloFriend.apk on device 'emulator-5554!
[2015-05-01 20:22:29 - HelloFriend] (null)
[2015-05-01 20:22:32 - HelloFriend] Launch canceled!
and in the log cat:
05-01 20:19:41.058: E/installd(1660): Running /system/bin/patchoat isa=arm in-fd=6 (/system/app/Email/arm/Email.odex) out-fd=7 (/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex)
05-01 20:19:42.242: E/ActivityManager(1060): ANR in android.process.media
05-01 20:19:42.242: E/ActivityManager(1060): PID: 1546
05-01 20:19:42.242: E/ActivityManager(1060): Reason: executing service com.android.providers.downloads/.DownloadService
05-01 20:19:42.242: E/ActivityManager(1060): Load: 9.16 / 7.46 / 5.52
05-01 20:19:42.242: E/ActivityManager(1060): CPU usage from 1598ms to -25155ms ago with 99% awake:
05-01 20:19:42.242: E/ActivityManager(1060): 45% 1060/system_server: 27% user + 18% kernel / faults: 6285 minor
05-01 20:19:42.242: E/ActivityManager(1060): 12% 1309/com.android.phone: 7.3% user + 4.8% kernel / faults: 1615 minor
05-01 20:19:42.242: E/ActivityManager(1060): 8.3% 1503/com.android.systemui: 6.2% user + 2.1% kernel / faults: 1834 minor
05-01 20:19:42.242: E/ActivityManager(1060): 7.6% 1546/android.process.media: 5.4% user + 2.2% kernel / faults: 2646 minor
05-01 20:19:42.242: E/ActivityManager(1060): 3.1% 64/debuggerd: 0.7% user + 2.4% kernel / faults: 2288 minor
05-01 20:19:42.242: E/ActivityManager(1060): 6.2% 1581/com.android.launcher: 4.9% user + 1.3% kernel / faults: 2943 minor
05-01 20:19:42.242: E/ActivityManager(1060): 3.3% 56/surfaceflinger: 1.2% user + 2% kernel / faults: 20 minor
05-01 20:19:42.242: E/ActivityManager(1060): 2% 26/mtdblock1: 0% user + 2% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 1.2% 62/adbd: 0.1% user + 1.1% kernel / faults: 73 minor
05-01 20:19:42.242: E/ActivityManager(1060): 1.2% 811/zygote: 0.6% user + 0.5% kernel / faults: 1490 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0.9% 51/logd: 0.7% user + 0.1% kernel / faults: 1 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0.7% 1615/com.android.dialer: 0.4% user + 0.3% kernel / faults: 689 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0.2% 1351/android.process.acore: 0.1% user + 0% kernel / faults: 7 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0.2% 1596/com.android.exchange: 0% user + 0.1% kernel / faults: 602 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0.1% 429/logcat: 0.1% user + 0% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0.1% 1278/com.android.inputmethod.latin: 0.1% user + 0% kernel / faults: 9 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0.1% 25/mtdblock0: 0% user + 0.1% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0.1% 54/servicemanager: 0% user + 0.1% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0.1% 1388/kworker/0:1: 0% user + 0.1% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0% 42/jbd2/mtdblock1-: 0% user + 0% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0% 809/installd: 0% user + 0% kernel / faults: 6 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0% 1324/zygote: 0% user + 0% kernel / faults: 2 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0% 1//init: 0% user + 0% kernel
05-01 20:19:42.242: E/ActivityManager(1060): +0% 1644/<pre-initialized>: 0% user + 0% kernel
05-01 20:19:42.242: E/ActivityManager(1060): +0% 1660/patchoat: 0% user + 0% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 100% TOTAL: 57% user + 42% kernel + 0.1% softirq
05-01 20:19:42.242: E/ActivityManager(1060): CPU usage from 23777ms to 24543ms later:
05-01 20:19:42.242: E/ActivityManager(1060): 61% 1309/com.android.phone: 33% user + 27% kernel / faults: 215 minor
05-01 20:19:42.242: E/ActivityManager(1060): 46% 1313/Signal Catcher: 24% user + 22% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 6.6% 1309/m.android.phone: 3.3% user + 3.3% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 3.3% 1567/Cat Icon Loader: 0% user + 3.3% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 2.2% 1398/RILReceiver0: 1.1% user + 1.1% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 1.1% 1434/GsmCellBroadcas: 1.1% user + 0% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 25% 1060/system_server: 10% user + 15% kernel / faults: 8 minor
05-01 20:19:42.242: E/ActivityManager(1060): 20% 1078/ActivityManager: 6.4% user + 13% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 2.1% 1342/Binder_7: 1% user + 1% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 1% 1086/PowerManagerSer: 0% user + 1% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 1% 1163/Binder_4: 0% user + 1% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 1% 1367/Binder_9: 1% user + 0% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 1% 1640/Binder_D: 0% user + 1% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0.7% 26/mtdblock1: 0% user + 0.7% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0.8% 51/logd: 0.8% user + 0% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 1.2% 432/logd.reader.per: 0.8% user + 0.4% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0.8% 62/adbd: 0% user + 0.8% kernel / faults: 2 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0.8% 137/adbd: 0% user + 0.8% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0.7% 1546/android.process.media: 0.7% user + 0% kernel / faults: 7 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0.7% 1558/HeapTrimmerDaem: 0.7% user + 0% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0.8% 1615/com.android.dialer: 0% user + 0.8% kernel / faults: 19 minor
05-01 20:19:42.242: E/ActivityManager(1060): 0.8% 1615/re-initialized>: 0% user + 0.8% kernel
05-01 20:19:42.242: E/ActivityManager(1060): 0.8% 1660/installd: 0.8% user + 0% kernel / faults: 30 minor
05-01 20:19:42.242: E/ActivityManager(1060): 100% TOTAL: 57% user + 42% kernel
05-01 20:19:43.501: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:19:46.834: E/libprocessgroup(1060): failed to kill 1 processes for processgroup 1546
05-01 20:19:48.329: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:20:05.173: E/installd(1683): Running /system/bin/patchoat isa=arm in-fd=6 (/system/app/Calendar/arm/Calendar.odex) out-fd=7 (/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex)
05-01 20:20:11.876: E/ActivityManager(1060): ANR in com.android.systemui
05-01 20:20:11.876: E/ActivityManager(1060): PID: 1503
05-01 20:20:11.876: E/ActivityManager(1060): Reason: Broadcast of Intent { act=android.intent.action.TIME_TICK flg=0x50000014 (has extras) }
05-01 20:20:11.876: E/ActivityManager(1060): Load: 9.34 / 7.67 / 5.66
05-01 20:20:11.876: E/ActivityManager(1060): CPU usage from 0ms to 23987ms later with 99% awake:
05-01 20:20:11.876: E/ActivityManager(1060): 51% 1060/system_server: 30% user + 20% kernel / faults: 6131 minor
05-01 20:20:11.876: E/ActivityManager(1060): 12% 1309/com.android.phone: 6.5% user + 5.5% kernel / faults: 1776 minor
05-01 20:20:11.876: E/ActivityManager(1060): 9% 1503/com.android.systemui: 6.8% user + 2.1% kernel / faults: 1250 minor
05-01 20:20:11.876: E/ActivityManager(1060): 6.3% 64/debuggerd: 1.8% user + 4.4% kernel / faults: 2257 minor
05-01 20:20:11.876: E/ActivityManager(1060): 5.2% 62/adbd: 0.9% user + 4.3% kernel / faults: 610 minor
05-01 20:20:11.876: E/ActivityManager(1060): 4.1% 1581/com.android.launcher: 3.6% user + 0.4% kernel / faults: 1755 minor
05-01 20:20:11.876: E/ActivityManager(1060): 1.9% 1644/com.android.email: 1.1% user + 0.8% kernel / faults: 2350 minor
05-01 20:20:11.876: E/ActivityManager(1060): 0.9% 811/zygote: 0.5% user + 0.4% kernel / faults: 1490 minor
05-01 20:20:11.876: E/ActivityManager(1060): 1% 26/mtdblock1: 0% user + 1% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0.5% 1615/com.android.dialer: 0.2% user + 0.2% kernel / faults: 840 minor
05-01 20:20:11.876: E/ActivityManager(1060): 0.2% 51/logd: 0.2% user + 0% kernel / faults: 3 minor
05-01 20:20:11.876: E/ActivityManager(1060): 0.2% 56/surfaceflinger: 0.1% user + 0.1% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0.1% 1351/android.process.acore: 0% user + 0.1% kernel / faults: 26 minor
05-01 20:20:11.876: E/ActivityManager(1060): 0.1% 25/mtdblock0: 0% user + 0.1% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0.1% 429/logcat: 0% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0% 54/servicemanager: 0% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0% 1596/com.android.exchange: 0% user + 0% kernel / faults: 5 minor
05-01 20:20:11.876: E/ActivityManager(1060): 0% 1//init: 0% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0% 42/jbd2/mtdblock1-: 0% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0% 52/healthd: 0% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0% 809/installd: 0% user + 0% kernel / faults: 7 minor
05-01 20:20:11.876: E/ActivityManager(1060): +0% 1667/<pre-initialized>: 0% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): +0% 1683/patchoat: 0% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): +0% 1687/sh: 0% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): +0% 1689/app_process: 0% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 100% TOTAL: 55% user + 44% kernel + 0.1% softirq
05-01 20:20:11.876: E/ActivityManager(1060): CPU usage from 21893ms to 22934ms later:
05-01 20:20:11.876: E/ActivityManager(1060): 41% 62/adbd: 5.5% user + 36% kernel / faults: 232 minor
05-01 20:20:11.876: E/ActivityManager(1060): 14% 136/adbd: 1.8% user + 12% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 13% 137/adbd: 2.7% user + 11% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 10% 62/adbd: 0.9% user + 9.2% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 2.7% 1685/adbd: 0.9% user + 1.8% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 23% 1060/system_server: 14% user + 8.7% kernel / faults: 1 minor
05-01 20:20:11.876: E/ActivityManager(1060): 23% 1078/ActivityManager: 12% user + 10% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0.9% 1077/android.bg: 0.9% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 5.5% 1644/com.android.email: 4.9% user + 0.6% kernel / faults: 426 minor
05-01 20:20:11.876: E/ActivityManager(1060): 4.3% 1644/m.android.email: 4.3% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 8.5% 1615/com.android.dialer: 5.3% user + 3.1% kernel / faults: 155 minor
05-01 20:20:11.876: E/ActivityManager(1060): 6.3% 1668/IntentService[C: 5.3% user + 1% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 2.1% 1615/.android.dialer: 0% user + 2.1% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 1.3% 26/mtdblock1: 0% user + 1.3% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 3.9% 1309/com.android.phone: 2.9% user + 0.9% kernel / faults: 30 minor
05-01 20:20:11.876: E/ActivityManager(1060): 3.9% 1309/m.android.phone: 3.9% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0.5% 51/logd: 0.2% user + 0.2% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0.2% 80/logd.writer: 0% user + 0.2% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0.2% 432/logd.reader.per: 0.2% user + 0% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0.4% 1351/android.process.acore: 0% user + 0.4% kernel / faults: 1 minor
05-01 20:20:11.876: E/ActivityManager(1060): 0.4% 1385/ContactsProvide: 0% user + 0.4% kernel
05-01 20:20:11.876: E/ActivityManager(1060): 0.6% 1683/patchoat: 0.6% user + 0% kernel / faults: 11 minor
05-01 20:20:11.876: E/ActivityManager(1060): 100% TOTAL: 43% user + 55% kernel + 0.9% softirq
05-01 20:20:15.767: E/memtrack(1689): Couldn't load memtrack module (No such file or directory)
05-01 20:20:15.767: E/android.os.Debug(1689): failed to load memtrack module: -2
05-01 20:20:26.453: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:20:26.801: E/libprocessgroup(1060): failed to kill 1 processes for processgroup 1503
05-01 20:20:29.086: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:20:30.197: E/installd(1718): Running /system/bin/patchoat isa=arm in-fd=6 (/system/priv-app/DefaultContainerService/arm/DefaultContainerService.odex) out-fd=7 (/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex)
05-01 20:20:40.778: E/InputDispatcher(1060): channel '9f8f12e com.android.systemui.ImageWallpaper (server)' ~ Channel is unrecoverably broken and will be disposed!
05-01 20:20:44.478: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:20:50.612: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:20:53.570: E/ActivityManager(1060): ANR in com.android.calendar
05-01 20:20:53.570: E/ActivityManager(1060): PID: 1667
05-01 20:20:53.570: E/ActivityManager(1060): Reason: Broadcast of Intent { act=android.intent.action.LOCALE_CHANGED flg=0x10000010 cmp=com.android.calendar/.alerts.AlertReceiver }
05-01 20:20:53.570: E/ActivityManager(1060): 1% 1726/<pre-initialized>: 0% user + 1% kernel / faults: 59 minor
05-01 20:20:53.570: E/ActivityManager(1060): 1% 1726/re-initialized>: 0%
05-01 20:20:55.594: E/libprocessgroup(1060): failed to kill 1 processes for processgroup 1667
05-01 20:20:56.858: E/installd(1764): Running /system/bin/patchoat isa=arm in-fd=6 (/system/app/DeskClock/arm/DeskClock.odex) out-fd=7 (/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex)
05-01 20:20:57.306: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:20:57.347: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:20:57.505: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:00.527: E/OpenGLRenderer(1581): Could not allocate texture for layer (fbo=1 1024x600)
05-01 20:21:00.923: E/OpenGLRenderer(1581): Error while compiling this shader:
05-01 20:21:00.923: E/OpenGLRenderer(1581): ===
05-01 20:21:00.923: E/OpenGLRenderer(1581): attribute vec4 position;
05-01 20:21:00.923: E/OpenGLRenderer(1581): attribute vec2 texCoords;
05-01 20:21:00.923: E/OpenGLRenderer(1581): uniform mat4 projection;
05-01 20:21:00.923: E/OpenGLRenderer(1581): uniform mat4 transform;
05-01 20:21:00.923: E/OpenGLRenderer(1581): varying vec2 outTexCoords;
05-01 20:21:00.923: E/OpenGLRenderer(1581): void main(void) {
05-01 20:21:00.923: E/OpenGLRenderer(1581): outTexCoords = texCoords;
05-01 20:21:00.923: E/OpenGLRenderer(1581): vec4 transformedPosition = projection * transform * position;
05-01 20:21:00.923: E/OpenGLRenderer(1581): gl_Position = transformedPosition;
05-01 20:21:00.923: E/OpenGLRenderer(1581): }
05-01 20:21:00.923: E/OpenGLRenderer(1581): ===
05-01 20:21:00.925: A/OpenGLRenderer(1581): Shader info log: ERROR: 0:1: '' : Version number not supported by GL2
05-01 20:21:00.931: A/libc(1581): Fatal signal 6 (SIGABRT), code -6 in tid 1659 (RenderThread)
05-01 20:21:03.356: E/NativeCrashListener(1060): Exception dealing with report
05-01 20:21:03.356: E/NativeCrashListener(1060): android.system.ErrnoException: read failed: EAGAIN (Try again)
05-01 20:21:03.356: E/NativeCrashListener(1060): at libcore.io.Posix.readBytes(Native Method)
05-01 20:21:03.356: E/NativeCrashListener(1060): at libcore.io.Posix.read(Posix.java:165)
05-01 20:21:03.356: E/NativeCrashListener(1060): at libcore.io.BlockGuardOs.read(BlockGuardOs.java:230)
05-01 20:21:03.356: E/NativeCrashListener(1060): at android.system.Os.read(Os.java:350)
05-01 20:21:03.356: E/NativeCrashListener(1060): at com.android.server.am.NativeCrashListener.consumeNativeCrashData(NativeCrashListener.java:240)
05-01 20:21:03.356: E/NativeCrashListener(1060): at com.android.server.am.NativeCrashListener.run(NativeCrashListener.java:138)
05-01 20:21:05.567: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:07.879: E/lowmemorykiller(53): Error opening /proc/1667/oom_score_adj; errno=2
05-01 20:21:09.352: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:09.761: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:18.149: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:18.186: E/GpsLocationProvider(1060): no AGPS interface in set_agps_server
05-01 20:21:18.442: E/GpsLocationProvider(1060): no GPS configuration interface in configuraiton_update
05-01 20:21:18.491: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:19.262: E/GpsLocationProvider(1060): no AGPS interface in set_agps_server
05-01 20:21:19.437: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:19.465: E/GpsLocationProvider(1060): no GPS configuration interface in configuraiton_update
05-01 20:21:19.555: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:24.027: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:44.336: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:49.001: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:49.218: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:50.701: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:21:55.075: E/OpenGLRenderer(1770): Could not allocate texture for layer (fbo=1 1024x600)
05-01 20:21:55.505: E/OpenGLRenderer(1770): Error while compiling this shader:
05-01 20:21:55.505: E/OpenGLRenderer(1770): ===
05-01 20:24:37.967: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:24:38.660: E/InputDispatcher(1060): channel '11c4b0b9 com.android.launcher/com.android.launcher2.Launcher (server)' ~ Channel is unrecoverably broken and will be disposed!
05-01 20:24:38.766: E/SurfaceFlinger(56): GL error 0x0501
05-01 20:24:39.641: E/BluetoothAdapter(1945): Bluetooth binder is null
What to do getting frustrated........plzz anyone there ,who can help me plzz.....

Related

Huge number error in log in every second

Hi,
recently I've noticed in radio buffer log by using alogcat app that the following errors repeat in every second.
01-28 22:33:59.867 E/RIL(s) ( 78): RX: (M)IPC_DISP_CMD (S)IPC_DISP_ICON_INFO (T)IPC_CMD_NOTI (len:0x0B mseq:0xFF aseq:0xC7) [ FF 03 00 05 ]
01-28 22:34:00.867 E/RIL(s) ( 78): RX: (M)IPC_DISP_CMD (S)IPC_DISP_ICON_INFO (T)IPC_CMD_NOTI (len:0x0B mseq:0xFF aseq:0xC7) [ FF 04 00 05 ]
01-28 22:34:08.261 E/RIL(s) ( 78): RX: (M)IPC_GPRS_CMD (S)IPC_GPRS_HSDPA_STATUS (T)IPC_CMD_NOTI (len:0x08 mseq:0xFF aseq:0xC7) [ 00 ]
01-28 22:34:08.277 E/RIL(s) ( 78): RX: (M)IPC_NET_CMD (S)IPC_NET_SERVING_NETWORK (T)IPC_CMD_RESP (len:0x12 mseq:0xFF aseq:0xC8) [ 02 02 04 32 31 36 30 31 23 0F 10 ]
It is since I upgraded to ICS. I remember that I hadn't any error in radio log under Gingerbread, but to make sure I checked it on my friend's Nexus S who is still on GB. He has no error in radio log.
Is it only my problem, or is it ICS' bug? Could anybody also check it with alogcat? Or does anybody know what is it?
Thanks!
Sent from my Nexus S using xda premium
There is no Nexus S owner with ICS on xda, who could check it?
:-(
Sent from my Nexus S using xda premium

Decompile Errors

Hey guys,
i am not a noob. i did so many roms before and build my own kernels.
But i am not able to decompile that apks from sense 4 roms.
i tried apktool 1.4.3, 1.4.2 ( and a modded one), 1.4.1. and of course the latest aapt.
Nothing worked!!
Decompile Error:
Code:
I: Baksmaling...
Exception in thread "main" java.lang.RuntimeException: bad magic value: 64 65 78 0a 30 33 36 00
at org.jf.dexlib.DexFile.<init>(DexFile.java:377)
at org.jf.dexlib.DexFile.<init>(DexFile.java:274)
at brut.androlib.src.SmaliDecoder.decode(SmaliDecoder.java:44)
at brut.androlib.src.SmaliDecoder.decode(SmaliDecoder.java:33)
at brut.androlib.Androlib.decodeSourcesSmali(Androlib.java:68)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:85)
at brut.apktool.Main.cmdDecode(Main.java:128)
at brut.apktool.Main.main(Main.java:65)
What did i wrong?
Have you applied Sense framework, so that apktool can use it?
Of course dude

[DUMP] Windows RT 9200 + USB recovery image

Dump from tablet
:: links are now dead. anyone need it I will share it privately ::
IMG from USB Recovery
:: links are now dead. anyone need it I will share it privately ::
Note: no serial number/key/flash instruction/hack is available with the dump. only the system files that are accessible by anyone that holds Windows RT tablet.
Dump includes the recovery partition (WIM), boot partition (UEFI files), and WinPE partition
Total Size: 3,595,076,072
Packed Size: 481,990,544
Code:
Name Size Packed Ratio Date Time Attr CRC Meth Ver
-------------------------------------------------------------------------------
*ReAgent.xml 994 576 57% 26-07-12 07:44 ...HSA. A7EEBE7C m5g 2.9
*Reload.xml 1269 96 7% 08-11-12 00:50 .....A. A558B6A1 m5g 2.9
*bootres.dll 18160 11760 64% 25-07-12 17:52 .....A. CF7DDB67 m5g 2.9
*BCD 24576 4272 17% 13-11-12 10:25 .....A. B27D5BC7 m5g 2.9
*bootarm.efi 749288 405776 54% 20-09-12 01:32 .....A. 30648877 m5g 2.9
*bootmgfw.efi 749288 496 0% 20-09-12 01:32 .....A. 30648877 m5g 2.9
*bootmgr.efi 746728 58320 7% 20-09-12 01:32 .....A. 11E0298B m5g 2.9
*FCT_COMM.FLG 1 16 1600% 03-08-12 23:34 .....A. A505DF1B m5g 2.9
*bootmgfw.efi.mui 63728 5312 8% 25-07-12 18:51 .....A. 23DD3BAD m5g
2.9
*bootmgfw.efi.mui 63728 4720 7% 25-07-12 18:51 .....A. 27E3343D m5g
2.9
*bootmgfw.efi.mui 63728 928 1% 25-07-12 18:51 .....A. F4692AC6 m5g
2.9
*bootmgfw.efi.mui 66800 4416 6% 25-07-12 18:51 .....A. 0E61EDE7 m5g
2.9
*bootmgfw.efi.mui 67312 4496 6% 25-07-12 18:51 .....A. A03E9B2B m5g
2.9
*bootmgfw.efi.mui 73456 1168 1% 25-07-12 18:51 .....A. 0780602F m5g
2.9
*bootmgfw.efi.mui 73456 992 1% 25-07-12 18:51 .....A. F5FEC50D m5g
2.9
*bootmgfw.efi.mui 73456 992 1% 25-07-12 18:51 .....A. C4F32266 m5g
2.9
*bootmgfw.efi.mui 74480 4880 6% 25-07-12 18:51 .....A. BC1D3B72 m5g
2.9
*bootmgfw.efi.mui 74992 4960 6% 25-07-12 18:51 .....A. 5F62C7A4 m5g
2.9
*bootmgfw.efi.mui 74992 4768 6% 25-07-12 18:51 .....A. CF426C26 m5g
2.9
*bootmgfw.efi.mui 74992 4880 6% 25-07-12 18:51 .....A. 16B1F33E m5g
2.9
*bootmgfw.efi.mui 75504 5152 6% 25-07-12 18:51 .....A. EC34594B m5g
2.9
*bootmgfw.efi.mui 75504 5024 6% 25-07-12 18:51 .....A. 85BC7472 m5g
2.9
*bootmgfw.efi.mui 75504 5024 6% 25-07-12 18:51 .....A. 5D75CB81 m5g
2.9
*bootmgfw.efi.mui 76016 5248 6% 25-07-12 18:51 .....A. 05A79A2F m5g
2.9
*bootmgfw.efi.mui 76016 4880 6% 25-07-12 18:51 .....A. 0ED09B3C m5g
2.9
*bootmgfw.efi.mui 76016 4704 6% 25-07-12 18:51 .....A. 3EC04CBD m5g
2.9
*bootmgfw.efi.mui 76016 4672 6% 25-07-12 18:51 .....A. 6DB960C3 m5g
2.9
*bootmgfw.efi.mui 76016 4400 5% 25-07-12 18:51 .....A. 1DD5DCCB m5g
2.9
*bootmgfw.efi.mui 76528 4976 6% 25-07-12 18:51 .....A. 4CC8DB42 m5g
2.9
*bootmgfw.efi.mui 76528 4624 6% 25-07-12 18:51 .....A. 93B96DE6 m5g
2.9
*bootmgfw.efi.mui 76528 3328 4% 25-07-12 18:51 .....A. 77F6A02A m5g
2.9
*bootmgfw.efi.mui 76528 5680 7% 25-07-12 18:51 .....A. CD65456F m5g
2.9
*bootmgfw.efi.mui 76528 4816 6% 25-07-12 18:51 .....A. 65FB5F69 m5g
2.9
*bootmgfw.efi.mui 76528 4016 5% 25-07-12 18:51 .....A. 5D52E309 m5g
2.9
*bootmgfw.efi.mui 76528 4960 6% 25-07-12 18:51 .....A. F76D772E m5g
2.9
*bootmgfw.efi.mui 77040 4688 6% 25-07-12 18:51 .....A. 826B6DF8 m5g
2.9
*bootmgfw.efi.mui 77040 4400 5% 25-07-12 18:51 .....A. E8E9B380 m5g
2.9
*bootmgfw.efi.mui 77552 4976 6% 25-07-12 18:51 .....A. A8260086 m5g
2.9
*bootmgfw.efi.mui 77552 5152 6% 25-07-12 18:51 .....A. 2AE9D2A2 m5g
2.9
*bootmgfw.efi.mui 78064 5376 6% 25-07-12 18:51 .....A. 5AB138C7 m5g
2.9
*bootmgfw.efi.mui 78576 5280 6% 25-07-12 18:51 .....A. E5B05A8C m5g
2.9
*bootmgfw.efi.mui 78576 5088 6% 25-07-12 18:51 .....A. C780ABB9 m5g
2.9
*bootmgfw.efi.mui 79600 5696 7% 25-07-12 18:51 .....A. A12C7178 m5g
2.9
*bootmgr.efi.mui 63728 928 1% 25-07-12 18:51 .....A. A596D5D4 m5g 2
.9
*bootmgr.efi.mui 63728 928 1% 25-07-12 18:51 .....A. 0D2E22EB m5g 2
.9
*bootmgr.efi.mui 63728 912 1% 25-07-12 18:51 .....A. 35B7AC00 m5g 2
.9
*bootmgr.efi.mui 66800 976 1% 25-07-12 18:51 .....A. F8D5D281 m5g 2
.9
*bootmgr.efi.mui 67312 928 1% 25-07-12 18:51 .....A. 9F786A88 m5g 2
.9
*bootmgr.efi.mui 73456 976 1% 25-07-12 18:51 .....A. C856B95F m5g 2
.9
*bootmgr.efi.mui 73456 944 1% 25-07-12 18:51 .....A. E7FC648F m5g 2
.9
*bootmgr.efi.mui 73456 928 1% 25-07-12 18:51 .....A. A09A023F m5g 2
.9
*bootmgr.efi.mui 74480 960 1% 25-07-12 18:51 .....A. DDB08F75 m5g 2
.9
*bootmgr.efi.mui 74992 960 1% 25-07-12 18:51 .....A. DFBCBFF6 m5g 2
.9
*bootmgr.efi.mui 74992 944 1% 25-07-12 18:51 .....A. 618D30A2 m5g 2
.9
*bootmgr.efi.mui 74992 944 1% 25-07-12 18:51 .....A. 051177A2 m5g 2
.9
*bootmgr.efi.mui 75504 960 1% 25-07-12 18:51 .....A. 44B8AD17 m5g 2
.9
*bootmgr.efi.mui 75504 944 1% 25-07-12 18:51 .....A. 117C9FC0 m5g 2
.9
*bootmgr.efi.mui 75504 960 1% 25-07-12 18:51 .....A. 8B62FF97 m5g 2
.9
*bootmgr.efi.mui 76016 960 1% 25-07-12 18:51 .....A. 3850C0A9 m5g 2
.9
*bootmgr.efi.mui 76016 976 1% 25-07-12 18:51 .....A. 03DE418A m5g 2
.9
*bootmgr.efi.mui 76016 960 1% 25-07-12 18:51 .....A. 5EC1740F m5g 2
.9
*bootmgr.efi.mui 76016 944 1% 25-07-12 18:51 .....A. B9F9C69F m5g 2
.9
*bootmgr.efi.mui 76016 976 1% 25-07-12 18:51 .....A. 4DF6C22B m5g 2
.9
*bootmgr.efi.mui 76528 976 1% 25-07-12 18:51 .....A. A4D8FC84 m5g 2
.9
*bootmgr.efi.mui 76528 960 1% 25-07-12 18:51 .....A. 36E41870 m5g 2
.9
*bootmgr.efi.mui 76528 960 1% 25-07-12 18:51 .....A. 6D55E7A6 m5g 2
.9
*bootmgr.efi.mui 76528 944 1% 25-07-12 18:51 .....A. 3DC086E2 m5g 2
.9
*bootmgr.efi.mui 76528 960 1% 25-07-12 18:51 .....A. C9B2F5D1 m5g 2
.9
*bootmgr.efi.mui 76528 960 1% 25-07-12 18:51 .....A. 2ED65BAD m5g 2
.9
*bootmgr.efi.mui 76528 944 1% 25-07-12 18:51 .....A. 68D92AD1 m5g 2
.9
*bootmgr.efi.mui 77040 928 1% 25-07-12 18:51 .....A. F7D6EE7D m5g 2
.9
*bootmgr.efi.mui 77040 960 1% 25-07-12 18:51 .....A. 4CAA149B m5g 2
.9
*bootmgr.efi.mui 77552 960 1% 25-07-12 18:51 .....A. C17B41DA m5g 2
.9
*bootmgr.efi.mui 77552 960 1% 25-07-12 18:51 .....A. 47FCFD60 m5g 2
.9
*bootmgr.efi.mui 78064 944 1% 25-07-12 18:51 .....A. C363D038 m5g 2
.9
*bootmgr.efi.mui 78576 992 1% 25-07-12 18:51 .....A. AA0FDD6B m5g 2
.9
*bootmgr.efi.mui 78576 944 1% 25-07-12 18:51 .....A. AADC35B9 m5g 2
.9
*bootmgr.efi.mui 79600 1040 1% 25-07-12 18:51 .....A. 98F7CE57 m5g 2
.9
*bootres.dll.mui 11504 1184 10% 26-07-12 00:06 .....A. 53CB5923 m5g 2
.9
*boot.sdi 3170304 12016 0% 02-06-12 22:40 ...HSA. 209CB6E6 m5g 2.9
*boot.stl 4186 2704 64% 26-06-12 19:05 .....A. DF0B67ED m5g 2.9
*chs_boot.ttf 3694080 2158352 58% 02-06-12 06:31 .....A. F448962F m5g 2.9
*cht_boot.ttf 3876772 2204352 56% 02-06-12 06:31 .....A. 4F3F9187 m5g 2.9
*jpn_boot.ttf 1984228 1057184 53% 02-06-12 06:31 .....A. E1FE426B m5g 2.9
*kor_boot.ttf 2371360 752048 31% 02-06-12 06:31 .....A. E861D39D m5g 2.9
*malgun_boot.ttf 168212 92624 55% 02-06-12 06:31 .....A. 480CC4F7 m5g 2
.9
*meiryo_boot.ttf 134508 44736 33% 02-06-12 06:31 .....A. D2C11860 m5g 2
.9
*msjh_boot.ttf 154896 59296 38% 02-06-12 06:31 .....A. 5E942DC5 m5g 2.9
*msyh_boot.ttf 146228 51552 35% 02-06-12 06:31 .....A. 63EBECA6 m5g 2.9
*segmono_boot.ttf 36020 14352 39% 02-06-12 06:31 .....A. 0253FF44 m5g
2.9
*segoe_slboot.ttf 77404 29520 38% 02-06-12 06:31 .....A. FCC0A1AA m5g
2.9
*wgl4_boot.ttf 47452 17200 36% 02-06-12 06:31 .....A. 3FBB074B m5g 2.9
*install.wim 3316013255 221419936 6% 13-11-12 10:50 .....A. 50D11B9F m5g 2
.9
*Winre.wim 255672543 253404064 99% 22-08-12 08:57 ...HSA. E8AC0791 m5g 2.
9
en-US 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
bg-BG 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
cs-CZ 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
da-DK 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
de-DE 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
el-GR 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
en-GB 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
en-US 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
es-ES 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
et-EE 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
fi-FI 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
Fonts 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
fr-FR 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
hr-HR 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
hu-HU 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
it-IT 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
ja-JP 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
ko-KR 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
lt-LT 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
lv-LV 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
nb-NO 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
nl-NL 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
pl-PL 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
pt-BR 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
pt-PT 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
qps-ploc 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
Resources 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
ro-RO 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
ru-RU 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
sk-SK 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
sl-SI 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
sr-Latn-CS 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
sv-SE 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
tr-TR 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
uk-UA 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
zh-CN 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
zh-HK 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
zh-TW 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
Boot 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
9432106f-d6b2-11e1-90e9-c4f51fb12e8c 0 0 0% 13-11-12 10:58 .D.
HS.. 00000000 m0 2.9
Boot 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
Logs 0 0 0% 13-11-12 10:58 .D.HS.. 00000000 m0 2.9
Microsoft 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
EFI 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
Recovery 0 0 0% 13-11-12 10:58 .D.HS.. 00000000 m0 2.9
RecoveryImage 0 0 0% 13-11-12 10:55 .D...A. 00000000 m0 2.9
d-WinRE 0 0 0% 13-11-12 10:58 .D..... 00000000 m0 2.9
e-EFI 0 0 0% 13-11-12 10:55 .D..... 00000000 m0 2.9
f-Recovery 0 0 0% 13-11-12 10:55 .D..... 00000000 m0 2.9
-------------------------------------------------------------------------------
143 3595076072 481990544 13%
for password please PM me.. this is for serious dev only (not meant for wild redistribution)
please understand that.
if you can boot into WinPE, then I can supply the partition that contains installed windows
extracted from Snapdragon Liquid MDP
http://www.engadget.com/2011/11/16/qualcomm-announces-snapdragon-s4-liquid-mobile-development-platf/
Update #1
11/14/2012 12:20AM
Disk 0 (GPT)
Partition # Type Size Offset
Partition 1 [Recovery] 500MB 1024KB
Partition 2 [System] 100MB 501MB
Partition 3 [Reserved] 256MB 601MB
Partition 4 [Primary] 24GB 857MB
Partition 5 [Recovery] 3500MB 25GB
Note: Partition 3 is empty and not assigned with any volume
Update #2
11/15/2012 1:17AM
Update #3
1/19/2013 6:24PM
I won't be providing the dump as reminded by M.. sorry folks..
Just for info
http://forum.xda-developers.com/showthread.php?t=1976532&page=2
contains the details of the disk partition layouts on a Surface (Surface RT)
But not the actual contents
See also the Boot from USB threads about how to create a bootable USB drive (copies stuff from the Recovery (WinRE) partition ?)
xsoliman3 said:
Just for info
http://forum.xda-developers.com/showthread.php?t=1976532&page=2
contains the details of the disk partition layouts on a Surface (Surface RT)
But not the actual contents
See also the Boot from USB threads about how to create a bootable USB drive (copies stuff from the Recovery (WinRE) partition ?)
Click to expand...
Click to collapse
I am still downloading the ADK to extract wim files (not able to extract with win7 imagex)
Still need efi bootloader on ARM to boot the system. Any idea?
Update
Am trying to create the recovery drive. Will post that soon.
UEFI bootloaders / firmware is a whole new topic in its own right
There is some stuff going on at DUET to create a UEFI boot firmware (on top of a normal BIOS)
and some intel systems have built in firmware UEFI (incl Mac's)
but non of that is relevant here in the ARM space
I'm not aware of any ARM system with UEFI (prior to Windows RT)
but now obviously the few Windows RT devices (and Windows Phone 8 ?) devices have native UEFI firmware
At some point we will need to try to somehow dump the UEFI firmware of some devices
but not sure where it is or how to pull it off
or whether its in NAND and upgradable or flashable or in ROM
But that will be very specific to a particular hardware device
The WP8 firmware hackers will probably be the ones who find out more about that
Plus to dig into the UEFI Secure Boot stuff ...
Great.
Waited for that long time
xsoliman3 said:
UEFI bootloaders / firmware is a whole new topic in its own right
There is some stuff going on at DUET to create a UEFI boot firmware (on top of a normal BIOS)
and some intel systems have built in firmware UEFI (incl Mac's)
but non of that is relevant here in the ARM space
I'm not aware of any ARM system with UEFI (prior to Windows RT)
but now obviously the few Windows RT devices (and Windows Phone 8 ?) devices have native UEFI firmware
At some point we will need to try to somehow dump the UEFI firmware of some devices
but not sure where it is or how to pull it off
or whether its in NAND and upgradable or flashable or in ROM
But that will be very specific to a particular hardware device
The WP8 firmware hackers will probably be the ones who find out more about that
Plus to dig into the UEFI Secure Boot stuff ...
Click to expand...
Click to collapse
Currently tablet has bootloader to Linux, and if the Linux bootloader can be mod to load EFI files then boot into WinPE it is good enough to start.
Plus, partition 1 (Windows partition) is BitLocker encrypted by default.
If anyone has the manual or method to extract full dump from the Snapdragon Liquid MDP, I'm willing to do that (as long as the device is still with me)
There was a Surface update package released yesterday, that also updates the firmware (as well as Windows RT)
That might help us understand the firmware and how to modify it (but bound to be encrypted obscurified (and signed)
Looks like dism.exe is now used to open/extract/deploy .wim files
More info on 'Linux' planned signed pre-boot loader for UEFI Secure Boot
But they don't have an ARM one yet
http://blog.hansenpartnership.com/linux-foundation-uefi-secure-boot-system-for-open-source/
Technically, shouldn't it be possible to run Windows RT on a N7? They both run on ARM and the exact same Tegra 3 cpu at that, 1GB is enough for RT devices even though Microsoft upped the recommendation to 2GB near release, and finally the installation occupies around 14GB which fits in the N7 16GB SSD - it wouldn't be difficult to create a lighter installation with some elements removed. Also, the N7 resolution is enough for metro apps, just not enough to use the Snap feature, but metro apps would run.
Hopefully someone with enough technical knowledge will attempt this. I'd gladly put Windows RT in my Nexus 7 and have an ultra portable "pc" with Office included - bring a USBtoGo cable with you and connect any keyboard to your N7, all ready to work!
The 14GB of the Surface RT install footprint includes things like a multi-gigabyte recovery partition, so yes, you could definitely fit the OS install on there.
As for the compatibility... that's another question. It's probably possible to get the kernel running, but it depends heavily on how similar the hardware is whether or not the thing would be usable (drivers, etc.). There's also a bunch of platform-specific firmware, the Board Support Package, which would need to be hacked together from a combination of the BSP for the Nexus 7 and a Windows RT device, or in some other way procured. It's possible that an RT device's BSP would be usable on the N7 if it could be extracted and installed there, but I'd be surprised.
soongteck said:
Dump from tablet
:: links are now dead. anyone need it I will share it privately ::
IMG from USB Recovery
:: links are now dead. anyone need it I will share it privately ::
Note: no serial number/key/flash instruction/hack is available with the dump. only the system files that are accessible by anyone that holds Windows RT tablet.
\[ ... \]
Update #2
11/15/2012 1:17AM
links are now offline due to dropbox block
anyone needs it please pm me
will try to upload the recovery USB later today
Click to expand...
Click to collapse
Can you post a link to the USB Recovery image?
GoodDayToDie said:
The 14GB of the Surface RT install footprint includes things like a multi-gigabyte recovery partition, so yes, you could definitely fit the OS install on there.
As for the compatibility... that's another question. It's probably possible to get the kernel running, but it depends heavily on how similar the hardware is whether or not the thing would be usable (drivers, etc.). There's also a bunch of platform-specific firmware, the Board Support Package, which would need to be hacked together from a combination of the BSP for the Nexus 7 and a Windows RT device, or in some other way procured. It's possible that an RT device's BSP would be usable on the N7 if it could be extracted and installed there, but I'd be surprised.
Click to expand...
Click to collapse
Looking at the portal, ERD cotulla has managed to get WinRT running on the HD2! So there definitely is some possibility somewhere
Sent from my GT-P7510 using XDA Premium HD app
[deleted]
scaryshark said:
Looking at the portal, ERD cotulla has managed to get WinRT running on the HD2! So there definitely is some possibility somewhere
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
indeed, they also said they had WM6.5 running as an app on WP7 and WM5 for the Alpine, I love the proof of concept, and I think its great the work they do, but we need to remember that not all proof of concepts come to anything.
in short, lets not get our hopes up until they are happy that they have something that is releasable to the public.
the mere fact that they had something working suggests its potentially possible but I suspect the same issues around drivers that we have on our phone devices today will be all the more problematic with a tablet due to variations in hardware design.
Anyone tried to flash this to a Nexus 10/7?
zAo_ said:
Anyone tried to flash this to a Nexus 10/7?
Click to expand...
Click to collapse
It won't work, without a lot a lot of work, as Windows RT needs an UEFI boot loader.
Hi all !
Guys who have dump Windows RT ?
I need link, i want port this OS to other device
Cheers !! :victory:
WojtasXda said:
Hi all !
Guys who have dump Windows RT ?
I need link, i want port this OS to other device
Cheers !! :victory:
Click to expand...
Click to collapse
see this thread: http://forum.xda-developers.com/showthread.php?t=2079409. And good luck!
Thanks ale07 for the link.
Very Thanks ale07

[Q] TF101 wifi problems, every rom but 1

Hi,
Looking to get some help out there from someone. Ever since I bought my TF101 I have had some issues with the wifi. Mostly it will work and then it will drop the signal. When it drops the signal the tablet becomes unusable. It takes 2 seconds to recognize a touch on the screen and everything is really slow and unresponsive.
This has been the case with every rom I have tried except for a Megatron rom from 2012. It works great on my tablet and I don't have any problems with it. But I want to upgrade to a newer version of Android.
I have tried the Katkiss rom that everyone seems to recommend but on my tablet I get the same bad wifi issue.
Does anyone have any insight as to why my tablet does this and can help me out?
Settings > WiFi > Advanced > WiFi Regulatory Domain
Make sure it is set correctly for your country
*Detection* said:
Settings > WiFi > Advanced > WiFi Regulatory Domain
Make sure it is set correctly for your country
Click to expand...
Click to collapse
I have tried this but had no success. I am using the US. Even though I live in Canada it should be the same. But thank you for your reply.
Maybe it's your router / wireless channel
Use WiFI Analyser from Google Play (Free) to check which channels are the most clear, then change the channel in your router
Also check you are using WPA2 encryption
No the problem persists no matter if I am connected to a network or not. Even if I just have WiFi on and not connected. Or when connected to every network I have tried...
Just bringing this thread up again, I have tried to fix this issue a couple of times and still can't figure it out. I just installed KatKiss ROM - Asus TF101
Lollipop 5.0.0_r7 #11 to try and get Lollipop running but I still run into the same problem every other ROM gives me.
I can connect to my wifi, stays connected for a few minutes and then disconnects. Once it disconnects then the tablet is almost unresponsive. It takes 2 or 3 seconds to recognize a key press and everything is slow. I can turn airplane mode on and it will be back to being responsive so the issue lies in my wifi adapter or firmware.
But the old Megatron rom is the only one where I don't get this behavior after I turn wifi on and off 2 times then it becomes perfect.
Make a logcat and post the logs to Tim the KK dev, he'll be able to tell you what's wrong, but if its happening in all but an ancient ROM, I guess its a hardware issue
You running the latest TWRP recovery?
I am running the newest TWRP and I cant post my catlog here so I'll pm you and Tim, maybe you can have a look for me?
j-waz said:
I am running the newest TWRP and I cant post my catlog here so I'll pm you and Tim, maybe you can have a look for me?
Click to expand...
Click to collapse
I'm not a dev so the logs are double dutch to me, I`ll post them here for you so others & Tim can see them
---
11-30 21:14:01.155 V/RoyWifiUtil(1673): DnsPinger.isReachable() got reply!
11-30 21:14:03.478 D/ConnectivityService(469): updateNetworkScore for NetworkAgentInfo [WIFI () - 108] to 57
11-30 21:14:03.479 D/ConnectivityService(469): rematching NetworkAgentInfo [WIFI () - 108]
11-30 21:14:03.479 D/ConnectivityService(469): Network NetworkAgentInfo [WIFI () - 108] was already satisfying request 1. No change.
11-30 21:14:03.479 D/ConnectivityService(469): notifyType AVAILABLE for NetworkAgentInfo [WIFI () - 108]
11-30 21:14:12.606 E/WifiStateMachine(469): WifiStateMachine starting scan for "FRITZ!Box 7312"WPA_PSK with 2412
11-30 21:14:13.220 E/WifiStateMachine(469): WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0.54 rxSuccessRate=0.39 targetRoamBSSID=9c:c7:a6:f6:b3:b2 RSSI=-1
11-30 21:14:19.301 D/WifiService(469): Client connection lost with reason: 4
11-30 21:14:19.958 E/WifiStateMachine(469): CMD_DELAYED_NETWORK_DISCONNECT and debouncing - disconnect 0
11-30 21:14:19.958 E/WifiConfigStore(469): saveWifiConfigBSSID Setting BSSID for "FRITZ!Box 7312"WPA_PSK to any
11-30 21:14:20.199 D/ConnectivityService(469): reportBadNetwork(NetworkAgentInfo [WIFI () - 108]) by 10014
11-30 21:14:20.202 D/NetworkMonitorNetworkAgentInfo [WIFI () - null]( 469): ValidatedState{ when=-3ms what=532488 arg1=10014 target=com.android.internal.util.StateMachine$SmHa ndler }
11-30 21:14:20.202 D/NetworkMonitorNetworkAgentInfo [WIFI () - null]( 469): DefaultState{ when=-3ms what=532488 arg1=10014 target=com.android.internal.util.StateMachine$SmHa ndler }
11-30 21:14:20.202 D/NetworkMonitorNetworkAgentInfo [WIFI () - null]( 469): Forcing reevaluation
11-30 21:14:20.203 D/NetworkMonitorNetworkAgentInfo [WIFI () - null]( 469): EvaluatingState{ when=0 what=532486 arg1=4 target=com.android.internal.util.StateMachine$SmHa ndler }
11-30 21:14:20.203 D/NetworkMonitorNetworkAgentInfo [WIFI () - null]( 469): Checking http://clients3.google.com/generate_204 on "FRITZ!Box 7312"
11-30 21:14:20.219 E/WifiConfigStore(469): saveWifiConfigBSSID Setting BSSID for "FRITZ!Box 7312"WPA_PSK to any
11-30 21:14:20.223 D/ConnectivityService(469): NetworkAgentInfo [WIFI () - 108] EVENT_NETWORK_INFO_CHANGED, going from CONNECTED to DISCONNECTED
11-30 21:14:20.223 D/ConnectivityService(469): NetworkAgentInfo [WIFI () - 108] got DISCONNECTED, was satisfying 2
11-30 21:14:20.281 E/WifiStateMachine(469): WifiStateMachine: Leaving Connected state
11-30 21:14:20.300 D/WifiNetworkAgent(469): NetworkAgent: NetworkAgent channel lost
11-30 21:14:20.407 D/NetworkMonitorNetworkAgentInfo [WIFI () - null]( 469): Probably not a portal: exception java.net.UnknownHostException: Unable to resolve host "clients3.google.com": No address associated with hostname
11-30 21:14:20.667 D/ConnectivityService(469): notifyType LOST for NetworkAgentInfo [WIFI () - 108]
11-30 21:14:20.671 D/CSLegacyTypeTracker(469): Sending disconnected broadcast for type 1 NetworkAgentInfo [WIFI () - 108] isDefaultNetwork=true
11-30 21:14:20.676 D/NetworkMonitorNetworkAgentInfo [WIFI () - null]( 469): EvaluatingState{ when=-5ms what=532487 target=com.android.internal.util.StateMachine$SmHa ndler }
11-30 21:14:20.676 D/NetworkMonitorNetworkAgentInfo [WIFI () - null]( 469): DefaultState{ when=-5ms what=532487 target=com.android.internal.util.StateMachine$SmHa ndler }
11-30 21:14:20.676 D/NetworkMonitorNetworkAgentInfo [WIFI () - null]( 469): Disconnected - quitting
11-30 21:14:49.403 E/WifiStateMachine(469): Unexpected BatchedScanResults
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
K
11-30 21:14:49.412 D/WifiScanningService(469): SCAN_AVAILABLE : 1
11-30 21:14:49.419 D/WifiScanningService(469): DefaultState got{ when=-6ms what=160007 target=com.android.internal.util.StateMachine$SmHa ndler }

[GAME][FREE][GIVEAWAY] Beat.Me - A game that plays based on your music

Hello !
I want to show you this free game for android called: Beat.Me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download link: Beat.Me - Playstore Link
About the game:
Trailer: https://www.youtube.com/watch?v=yWYKIMI58ow
Old Trailer (version 1.2.5.0): https://www.youtube.com/watch?v=yIPJYUEDOZo
Old Trailer (version 1.0.0.0): https://www.youtube.com/watch?v=p9B_AzyL27A
Beat.Me is a game that plays based on your music. The objective is to hit the obstacles while at the same time trying to avoid being hit by them.
The game creates the levels based on your chosen music-
The ship shoots and moves at the rhythm of the music. You gain points by hitting the obstacles. If you destroy the obstacles, you gain extra points. If you are hit by them, you lose points.
You have two different difficulties you can choose from, and you can also choose to activate two (optional) special abilities that can help you get a better score.
Here is some codes to redeem on the playstore: Beat.Me codes
I hope you like it !
Thank you and good day.
Images:
About me:
I’m a informatics engineering student from Portugal. I made this game because I'm always bored in the commute to school, so I grabbed the two things I love, (games and music) and made this little game so I can play in the bus/train and hopefully others can play it too.
I made this game in my spare time, and this is my first game, tried to put a complete Playstore game experience (leaderboards, saves, unlockables, etc). Any feedback, positive or negative, is highly appreciated, thank you and I hope you enjoy it as much as I learned and enjoyed making it !
UPDATE: version 1.0.0.1 released
Small UI bug fixed.
Great game
thanks
Integration with spotify would be cool
dasti555 said:
Integration with spotify would be cool
Click to expand...
Click to collapse
I thought of that, but I can't do it.
It says in their terms of use (Spotify Terms):
Section IV: Restrictions
3) e.) "Games and Trivia Quizzes. Unless you receive Spotify’s written approval, you shall not use the Spotify Platform to incorporate Spotify Content into any game functionality (including trivia quizzes)."
but thanks for the tip
S YILDIRIM said:
Great game
thanks
Click to expand...
Click to collapse
Thank you !
I'm glad you liked it
NFSS10 said:
I thought of that, but I can't do it.
It says in their terms of use (Spotify Terms):
Section IV: Restrictions
3) e.) "Games and Trivia Quizzes. Unless you receive Spotify’s written approval, you shall not use the Spotify Platform to incorporate Spotify Content into any game functionality (including trivia quizzes)."
but thanks for the tip
Click to expand...
Click to collapse
What if you write them?
dasti555 said:
What if you write them?
Click to expand...
Click to collapse
I may do it.
I didn't do it because it is my first game, and I thought not a lot of people would like it...
but I guess I was wrong, and it seems people are liking the game so I may as well dedicate more into the game. (I will try to learn how to do animation to try and make some cool effects too)
Game already has permissions to read storage, still can't find music..
Sent from my XT1635-02 using Tapatalk
robosaiyuk said:
Game already has permissions to read storage, still can't find music..
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
I use the android built in media database to get the music.
Does it shows on the normal android music player? (BTW it just works with .mp3 and .wav)
NFSS10 said:
I use the android built in media database to get the music.
Does it shows on the normal android music player? (BTW it just works with .mp3 and .wav)
Click to expand...
Click to collapse
Ahhh ok, tried to use ogg[emoji1]
Sent from my XT1635-02 using Tapatalk
Won't work on my kenzo, gonna try reinstall it and get a logcat. It just fc after the best played with headphones.
EDIT: MAybe because i have my music on the sd?
Tatoh said:
Won't work on my kenzo, gonna try reinstall it and get a logcat. It just fc after the best played with headphones.
Click to expand...
Click to collapse
I would really appreciate that. Thank you
Tatoh said:
EDIT: MAybe because i have my music on the sd?
Click to expand...
Click to collapse
I don't think so, I have my music on the SD too.
The only thing I have that makes the game quits is an anti lucky patcher thingy that I put there so my friends wouldn't cheat. (those bastards xD)
Code:
05-01 20:20:26.278 E/Unity (25294): Unable to find AudioPluginMsHRTF
05-01 20:20:26.279 E/Unity (25294): Unable to find AudioPluginOculusSpatializer
05-01 20:20:34.665 E/CRASH (25294): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
05-01 20:20:34.666 E/CRASH (25294): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-01 20:20:34.666 E/CRASH (25294): Build fingerprint: 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V8.2.1.0.MHOCNDL:user/release-keys'
05-01 20:20:34.666 E/CRASH (25294): Revision: '0'
05-01 20:20:34.666 E/CRASH (25294): pid: 25294, tid: 25294, name: .nfss10.Beat.me >>> com.nfss10.Beat.me <<<
05-01 20:20:34.666 E/CRASH (25294): r0 00000000 r1 0011f300 r2 7e938784 r3 f46f3d49
05-01 20:20:34.666 E/CRASH (25294): r4 00000000 r5 f096a954 r6 703a77d4 r7 ffba1490
05-01 20:20:34.667 E/CRASH (25294): r8 ffba141f r9 0019bed8 sl 0019bec8 fp ffba1408
05-01 20:20:34.667 E/CRASH (25294): ip f381239c sp ffba13e0 lr f33d3880 pc f33d3880 cpsr 302e312e
05-01 20:20:34.667 E/CRASH (25294):
05-01 20:20:34.667 E/CRASH (25294): backtrace:
I'm on a custom rom, if it helps
Tatoh said:
Code:
05-01 20:20:26.278 E/Unity (25294): Unable to find AudioPluginMsHRTF
05-01 20:20:26.279 E/Unity (25294): Unable to find AudioPluginOculusSpatializer
05-01 20:20:34.665 E/CRASH (25294): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
05-01 20:20:34.666 E/CRASH (25294): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-01 20:20:34.666 E/CRASH (25294): Build fingerprint: 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V8.2.1.0.MHOCNDL:user/release-keys'
05-01 20:20:34.666 E/CRASH (25294): Revision: '0'
05-01 20:20:34.666 E/CRASH (25294): pid: 25294, tid: 25294, name: .nfss10.Beat.me >>> com.nfss10.Beat.me <<<
05-01 20:20:34.666 E/CRASH (25294): r0 00000000 r1 0011f300 r2 7e938784 r3 f46f3d49
05-01 20:20:34.666 E/CRASH (25294): r4 00000000 r5 f096a954 r6 703a77d4 r7 ffba1490
05-01 20:20:34.667 E/CRASH (25294): r8 ffba141f r9 0019bed8 sl 0019bec8 fp ffba1408
05-01 20:20:34.667 E/CRASH (25294): ip f381239c sp ffba13e0 lr f33d3880 pc f33d3880 cpsr 302e312e
05-01 20:20:34.667 E/CRASH (25294):
05-01 20:20:34.667 E/CRASH (25294): backtrace:
I'm on a custom rom, if it helps
Click to expand...
Click to collapse
It looks it is some conflit with VR. Strange, I don't use VR, it's a 2D game
I think I know what to do, tomorrow after school I should have a fix done.
Thank you very much I really appreciate your time.
With Chrome it asks for username and password.
NFSS10 said:
It looks it is some conflit with VR. Strange, I don't use VR, it's a 2D game
I think I know what to do, tomorrow after school I should have a fix done.
Thank you very much I really appreciate your time.
Click to expand...
Click to collapse
No problem bro, I know the feeling when something in an app won't work and nobody gives you a logcat xD
Zibri said:
With Chrome it asks for username and password.
Click to expand...
Click to collapse
You are searching in the url bar right?
by typing in the url bar "Beat.Me", chrome would interpet as http://Beat.Me and that is some random person website
@NFSS10 Nice game, awesome work! I like how the difficulty change with different songs. One question, are the blue waves just a visual effect or they are dealing damage? I feel like they should deal a bit more damage, I was under the impression that my ship was a little under powered versus all these ennemies or maybe I should just try another music style :laugh:
Also found a minor issue with notifications. I.e whenever I receive a txt or anything showing a notification, the game will "listen" to the notification sound instead of the mp3 and the ship will stop shooting until the notification is gone. (Android 7.1.1)
Oh and congrats making the xda portal :good:
It don't work on my moto g3 aospExtended android 7.1.2.. I gave storage permission but it say no music found.

Categories

Resources