[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
*-- On Mon, 6/7/09, numan numan@gmail.com wrote: hello my friend how are u latest sexy summer fashion hot fashion videos visit my websitehttp://www.fashioninfokit.com/* --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
Can any of the Google team comment on this?
I found similar reports on the T-Mobile discussion threads, but no
work-arounds other than wipe or replace your phone. I've opened
defect 2864: http://code.google.com/p/android/issues/detail?id=2864
On Jun 2, 8:32 pm, Blake B. bbuckle...@yahoo.com wrote:
I have not installed any system builds other than those pushed by T-
Mobile OTA. So, 1.5 was the first update since 1.1. The OS is
completely stock, non-rooted.
I have both aHome and dxTop desktops installed, and have developed
widgets that support both of those desktops, pre-Cupcake. However, I
have NOT developed any 1.5-compatible widget yet, so would be suprised
if this affected the Android system, unless these desktops are somehow
updated a widget list/registry that is shared by the Android default
desktop? I haven't heard of such a thing, but then, I haven't had a
chance to dig into the 1.5 release much yet.
Blake
On Jun 2, 3:22 pm, Jeff Sharkey jshar...@android.com wrote:
When you saw this error, was it a direct upgrade from the last-OTA'ed
release, or had you installed other builds in the meantime without
wiping data? I think there was an obscure bug if you somehow had
allocated, but unmanaged, appWidgetIds.
j
On Tue, Jun 2, 2009 at 5:19 AM, Blake B. bbuckle...@yahoo.com wrote:
Any update on this? I'm encountering the samecrashand would rather
not wipe my phone if I don't have to. Safe mode does not work. Phone
(stock G1) just keeps cycling at the Android logo image and I have to
pull the battery to kill it.
I received theCupcakeOTA update on Saturday, and yesterday (Monday)
was the first time I rebooted the phone after the update. So, I've
never had a successful reboot withCupcake. The offending call is in
com.android.server.AppWidgetService.readStateFromFileLocked
(AppWidgetService.java:972), getting IndexOutOfBoundsException.
(BTW, great work onCupcake. er except for this of course. :-)
My stacktrace is the same as AndroidApp's:
my log
06-01 22:14:51.893: VERBOSE/WifiStateTracker(62): Connection to
supplicant established, state=SCANNING
06-01 22:14:51.903: VERBOSE/WifiStateTracker(62): Changing supplicant
state: SCANNING == SCANNING
06-01 22:14:51.913: INFO/SystemServer(62): Starting Location Manager.
06-01 22:14:51.943: DEBUG/GpsLocationProvider(62): enable
06-01 22:14:51.953: VERBOSE/WifiMonitor(62): Event [Trying to
associate with 00:1d:5a:d4:eb:d9 (SSID='2WIRE456' freq=2412 MHz)]
06-01 22:14:51.953: VERBOSE/WifiMonitor(62): Event [CTRL-EVENT-STATE-
CHANGE id=-1 state=3]
06-01 22:14:51.953: VERBOSE/WifiStateTracker(62): Changing supplicant
state: SCANNING == ASSOCIATING
06-01 22:14:51.963: DEBUG/GpsLocationProvider(62): GpsEventThread
starting
06-01 22:14:51.973: DEBUG/GpsLocationProvider(62): NetworkThread
starting
06-01 22:14:51.973: DEBUG/GpsLocationProvider(62): NetworkThread wait
for network
06-01 22:14:51.993: INFO/SystemServer(62): Starting Search Service.
06-01 22:14:52.003: INFO/SystemServer(62): Starting Checkin Service.
06-01 22:14:52.003: INFO/SystemServer(62): Starting Wallpaper Service
06-01 22:14:52.013: DEBUG/WallpaperService(62): WallpaperService
startup
06-01 22:14:52.023: INFO/SystemServer(62): Starting Audio Service
06-01 22:14:52.083: DEBUG/AudioHardwareMSM72XX(35): setVoiceVolume
(0.60)
06-01 22:14:52.083: INFO/AudioHardwareMSM72XX(35): Setting in-call
volume to 3 (available range is 0 to 5)
06-01 22:14:52.163: DEBUG/AudioHardwareMSM72XX(35): setVoiceVolume
(1.00)
06-01 22:14:52.163: INFO/AudioHardwareMSM72XX(35): Setting in-call
volume to 5 (available range is 0 to 5)
06-01 22:14:52.183: DEBUG/dalvikvm(62): Trying to load lib /system/lib/
libsoundpool.so 0x0
06-01 22:14:52.203: DEBUG/dalvikvm(62): Added shared lib /system/lib/
libsoundpool.so 0x0
06-01 22:14:52.233: INFO/SystemServer(62): Starting HeadsetObserver
06-01 22:14:52.293: INFO/SystemServer(62): Starting AppWidget Service
06-01 22:14:52.763: DEBUG/dalvikvm(62): GC freed 4358 objects / 252408
bytes in 417ms
06-01 22:14:52.883: INFO/WindowManager(62): Menu key state: 0
safeMode=false
06-01 22:14:52.913: INFO/WindowManager(62): Config changed:
{ scale=1.0 imsi=0/0 locale=en_US touch=3 key=2/1/1 nav=3 orien=1 }
06-01 22:14:52.943: DEBUG/PowerManagerService(62): system ready!
06-01 22:14:52.963: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03
06-01 22:14:52.983: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03000c
06-01 22:14:52.993: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03
06-01 22:14:53.003: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f030003
06-01 22:14:53.253:
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
Any update on this? I'm encountering the same crash and would rather
not wipe my phone if I don't have to. Safe mode does not work. Phone
(stock G1) just keeps cycling at the Android logo image and I have to
pull the battery to kill it.
I received the Cupcake OTA update on Saturday, and yesterday (Monday)
was the first time I rebooted the phone after the update. So, I've
never had a successful reboot with Cupcake. The offending call is in
com.android.server.AppWidgetService.readStateFromFileLocked
(AppWidgetService.java:972), getting IndexOutOfBoundsException.
(BTW, great work on Cupcake. er except for this of course. :-)
My stacktrace is the same as AndroidApp's:
my log
06-01 22:14:51.893: VERBOSE/WifiStateTracker(62): Connection to
supplicant established, state=SCANNING
06-01 22:14:51.903: VERBOSE/WifiStateTracker(62): Changing supplicant
state: SCANNING == SCANNING
06-01 22:14:51.913: INFO/SystemServer(62): Starting Location Manager.
06-01 22:14:51.943: DEBUG/GpsLocationProvider(62): enable
06-01 22:14:51.953: VERBOSE/WifiMonitor(62): Event [Trying to
associate with 00:1d:5a:d4:eb:d9 (SSID='2WIRE456' freq=2412 MHz)]
06-01 22:14:51.953: VERBOSE/WifiMonitor(62): Event [CTRL-EVENT-STATE-
CHANGE id=-1 state=3]
06-01 22:14:51.953: VERBOSE/WifiStateTracker(62): Changing supplicant
state: SCANNING == ASSOCIATING
06-01 22:14:51.963: DEBUG/GpsLocationProvider(62): GpsEventThread
starting
06-01 22:14:51.973: DEBUG/GpsLocationProvider(62): NetworkThread
starting
06-01 22:14:51.973: DEBUG/GpsLocationProvider(62): NetworkThread wait
for network
06-01 22:14:51.993: INFO/SystemServer(62): Starting Search Service.
06-01 22:14:52.003: INFO/SystemServer(62): Starting Checkin Service.
06-01 22:14:52.003: INFO/SystemServer(62): Starting Wallpaper Service
06-01 22:14:52.013: DEBUG/WallpaperService(62): WallpaperService
startup
06-01 22:14:52.023: INFO/SystemServer(62): Starting Audio Service
06-01 22:14:52.083: DEBUG/AudioHardwareMSM72XX(35): setVoiceVolume
(0.60)
06-01 22:14:52.083: INFO/AudioHardwareMSM72XX(35): Setting in-call
volume to 3 (available range is 0 to 5)
06-01 22:14:52.163: DEBUG/AudioHardwareMSM72XX(35): setVoiceVolume
(1.00)
06-01 22:14:52.163: INFO/AudioHardwareMSM72XX(35): Setting in-call
volume to 5 (available range is 0 to 5)
06-01 22:14:52.183: DEBUG/dalvikvm(62): Trying to load lib /system/lib/
libsoundpool.so 0x0
06-01 22:14:52.203: DEBUG/dalvikvm(62): Added shared lib /system/lib/
libsoundpool.so 0x0
06-01 22:14:52.233: INFO/SystemServer(62): Starting HeadsetObserver
06-01 22:14:52.293: INFO/SystemServer(62): Starting AppWidget Service
06-01 22:14:52.763: DEBUG/dalvikvm(62): GC freed 4358 objects / 252408
bytes in 417ms
06-01 22:14:52.883: INFO/WindowManager(62): Menu key state: 0
safeMode=false
06-01 22:14:52.913: INFO/WindowManager(62): Config changed:
{ scale=1.0 imsi=0/0 locale=en_US touch=3 key=2/1/1 nav=3 orien=1 }
06-01 22:14:52.943: DEBUG/PowerManagerService(62): system ready!
06-01 22:14:52.963: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03
06-01 22:14:52.983: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03000c
06-01 22:14:52.993: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03
06-01 22:14:53.003: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f030003
06-01 22:14:53.253: DEBUG/dalvikvm(62): GC freed 2153 objects / 118592
bytes in 235ms
06-01 22:14:53.263: WARN/dalvikvm(62): threadid=13: thread exiting
with uncaught exception (group=0x4000fe70)
06-01 22:14:53.273: ERROR/AndroidRuntime(62): Uncaught handler: thread
android.server.ServerThread exiting due to uncaught exception
06-01 22:14:53.273: ERROR/AndroidRuntime(62): *** EXCEPTION IN SYSTEM
PROCESS. System will crash.
06-01 22:14:53.333: ERROR/AndroidRuntime(62):
java.lang.IndexOutOfBoundsException: Invalid location 1, size is 1
06-01 22:14:53.333: ERROR/AndroidRuntime(62): at
java.util.ArrayList.get(ArrayList.java:353)
06-01 22:14:53.333: ERROR/AndroidRuntime(62): at
com.android.server.AppWidgetService.readStateFromFileLocked
(AppWidgetService.java:972)
06-01 22:14:53.333: ERROR/AndroidRuntime(62): at
com.android.server.AppWidgetService.loadStateLocked
(AppWidgetService.java:750)
06-01 22:14:53.333: ERROR/AndroidRuntime(62): at
com.android.server.AppWidgetService.systemReady(AppWidgetService.java:
125)
06-01 22:14:53.333: ERROR/AndroidRuntime(62): at
com.android.server.ServerThread.run(SystemServer.java:346)
06-01 22:14:53.343: ERROR/AndroidRuntime(62): Crash logging skipped,
no checkin service
06-01 22:14:53.353: INFO/Process(62): Sending signal. PID: 62 SIG: 9
06-01 22:14:53.383: INFO/ServiceManager(30): service 'batteryinfo'
died
06-01 22:14:53.393: INFO/ServiceManager(30): service 'usagestats' died
06-01 22:14:53.393: INFO/ServiceManager(30): service
'telephony.registry' died
06-01 22:14:53.393:
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
When you saw this error, was it a direct upgrade from the last-OTA'ed
release, or had you installed other builds in the meantime without
wiping data? I think there was an obscure bug if you somehow had
allocated, but unmanaged, appWidgetIds.
j
On Tue, Jun 2, 2009 at 5:19 AM, Blake B. bbuckle...@yahoo.com wrote:
Any update on this? I'm encountering the same crash and would rather
not wipe my phone if I don't have to. Safe mode does not work. Phone
(stock G1) just keeps cycling at the Android logo image and I have to
pull the battery to kill it.
I received the Cupcake OTA update on Saturday, and yesterday (Monday)
was the first time I rebooted the phone after the update. So, I've
never had a successful reboot with Cupcake. The offending call is in
com.android.server.AppWidgetService.readStateFromFileLocked
(AppWidgetService.java:972), getting IndexOutOfBoundsException.
(BTW, great work on Cupcake. er except for this of course. :-)
My stacktrace is the same as AndroidApp's:
my log
06-01 22:14:51.893: VERBOSE/WifiStateTracker(62): Connection to
supplicant established, state=SCANNING
06-01 22:14:51.903: VERBOSE/WifiStateTracker(62): Changing supplicant
state: SCANNING == SCANNING
06-01 22:14:51.913: INFO/SystemServer(62): Starting Location Manager.
06-01 22:14:51.943: DEBUG/GpsLocationProvider(62): enable
06-01 22:14:51.953: VERBOSE/WifiMonitor(62): Event [Trying to
associate with 00:1d:5a:d4:eb:d9 (SSID='2WIRE456' freq=2412 MHz)]
06-01 22:14:51.953: VERBOSE/WifiMonitor(62): Event [CTRL-EVENT-STATE-
CHANGE id=-1 state=3]
06-01 22:14:51.953: VERBOSE/WifiStateTracker(62): Changing supplicant
state: SCANNING == ASSOCIATING
06-01 22:14:51.963: DEBUG/GpsLocationProvider(62): GpsEventThread
starting
06-01 22:14:51.973: DEBUG/GpsLocationProvider(62): NetworkThread
starting
06-01 22:14:51.973: DEBUG/GpsLocationProvider(62): NetworkThread wait
for network
06-01 22:14:51.993: INFO/SystemServer(62): Starting Search Service.
06-01 22:14:52.003: INFO/SystemServer(62): Starting Checkin Service.
06-01 22:14:52.003: INFO/SystemServer(62): Starting Wallpaper Service
06-01 22:14:52.013: DEBUG/WallpaperService(62): WallpaperService
startup
06-01 22:14:52.023: INFO/SystemServer(62): Starting Audio Service
06-01 22:14:52.083: DEBUG/AudioHardwareMSM72XX(35): setVoiceVolume
(0.60)
06-01 22:14:52.083: INFO/AudioHardwareMSM72XX(35): Setting in-call
volume to 3 (available range is 0 to 5)
06-01 22:14:52.163: DEBUG/AudioHardwareMSM72XX(35): setVoiceVolume
(1.00)
06-01 22:14:52.163: INFO/AudioHardwareMSM72XX(35): Setting in-call
volume to 5 (available range is 0 to 5)
06-01 22:14:52.183: DEBUG/dalvikvm(62): Trying to load lib /system/lib/
libsoundpool.so 0x0
06-01 22:14:52.203: DEBUG/dalvikvm(62): Added shared lib /system/lib/
libsoundpool.so 0x0
06-01 22:14:52.233: INFO/SystemServer(62): Starting HeadsetObserver
06-01 22:14:52.293: INFO/SystemServer(62): Starting AppWidget Service
06-01 22:14:52.763: DEBUG/dalvikvm(62): GC freed 4358 objects / 252408
bytes in 417ms
06-01 22:14:52.883: INFO/WindowManager(62): Menu key state: 0
safeMode=false
06-01 22:14:52.913: INFO/WindowManager(62): Config changed:
{ scale=1.0 imsi=0/0 locale=en_US touch=3 key=2/1/1 nav=3 orien=1 }
06-01 22:14:52.943: DEBUG/PowerManagerService(62): system ready!
06-01 22:14:52.963: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03
06-01 22:14:52.983: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03000c
06-01 22:14:52.993: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03
06-01 22:14:53.003: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f030003
06-01 22:14:53.253: DEBUG/dalvikvm(62): GC freed 2153 objects / 118592
bytes in 235ms
06-01 22:14:53.263: WARN/dalvikvm(62): threadid=13: thread exiting
with uncaught exception (group=0x4000fe70)
06-01 22:14:53.273: ERROR/AndroidRuntime(62): Uncaught handler: thread
android.server.ServerThread exiting due to uncaught exception
06-01 22:14:53.273: ERROR/AndroidRuntime(62): *** EXCEPTION IN SYSTEM
PROCESS. System will crash.
06-01 22:14:53.333: ERROR/AndroidRuntime(62):
java.lang.IndexOutOfBoundsException: Invalid location 1, size is 1
06-01 22:14:53.333: ERROR/AndroidRuntime(62): at
java.util.ArrayList.get(ArrayList.java:353)
06-01 22:14:53.333: ERROR/AndroidRuntime(62): at
com.android.server.AppWidgetService.readStateFromFileLocked
(AppWidgetService.java:972)
06-01 22:14:53.333: ERROR/AndroidRuntime(62): at
com.android.server.AppWidgetService.loadStateLocked
(AppWidgetService.java:750)
06-01 22:14:53.333: ERROR/AndroidRuntime(62): at
com.android.server.AppWidgetService.systemReady(AppWidgetService.java:
125)
06-01 22:14:53.333: ERROR/AndroidRuntime(62): at
com.android.server.ServerThread.run(SystemServer.java:346)
06-01
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
I have not installed any system builds other than those pushed by T-
Mobile OTA. So, 1.5 was the first update since 1.1. The OS is
completely stock, non-rooted.
I have both aHome and dxTop desktops installed, and have developed
widgets that support both of those desktops, pre-Cupcake. However, I
have NOT developed any 1.5-compatible widget yet, so would be suprised
if this affected the Android system, unless these desktops are somehow
updated a widget list/registry that is shared by the Android default
desktop? I haven't heard of such a thing, but then, I haven't had a
chance to dig into the 1.5 release much yet.
Blake
On Jun 2, 3:22 pm, Jeff Sharkey jshar...@android.com wrote:
When you saw this error, was it a direct upgrade from the last-OTA'ed
release, or had you installed other builds in the meantime without
wiping data? I think there was an obscure bug if you somehow had
allocated, but unmanaged, appWidgetIds.
j
On Tue, Jun 2, 2009 at 5:19 AM, Blake B. bbuckle...@yahoo.com wrote:
Any update on this? I'm encountering the samecrashand would rather
not wipe my phone if I don't have to. Safe mode does not work. Phone
(stock G1) just keeps cycling at the Android logo image and I have to
pull the battery to kill it.
I received theCupcakeOTA update on Saturday, and yesterday (Monday)
was the first time I rebooted the phone after the update. So, I've
never had a successful reboot withCupcake. The offending call is in
com.android.server.AppWidgetService.readStateFromFileLocked
(AppWidgetService.java:972), getting IndexOutOfBoundsException.
(BTW, great work onCupcake. er except for this of course. :-)
My stacktrace is the same as AndroidApp's:
my log
06-01 22:14:51.893: VERBOSE/WifiStateTracker(62): Connection to
supplicant established, state=SCANNING
06-01 22:14:51.903: VERBOSE/WifiStateTracker(62): Changing supplicant
state: SCANNING == SCANNING
06-01 22:14:51.913: INFO/SystemServer(62): Starting Location Manager.
06-01 22:14:51.943: DEBUG/GpsLocationProvider(62): enable
06-01 22:14:51.953: VERBOSE/WifiMonitor(62): Event [Trying to
associate with 00:1d:5a:d4:eb:d9 (SSID='2WIRE456' freq=2412 MHz)]
06-01 22:14:51.953: VERBOSE/WifiMonitor(62): Event [CTRL-EVENT-STATE-
CHANGE id=-1 state=3]
06-01 22:14:51.953: VERBOSE/WifiStateTracker(62): Changing supplicant
state: SCANNING == ASSOCIATING
06-01 22:14:51.963: DEBUG/GpsLocationProvider(62): GpsEventThread
starting
06-01 22:14:51.973: DEBUG/GpsLocationProvider(62): NetworkThread
starting
06-01 22:14:51.973: DEBUG/GpsLocationProvider(62): NetworkThread wait
for network
06-01 22:14:51.993: INFO/SystemServer(62): Starting Search Service.
06-01 22:14:52.003: INFO/SystemServer(62): Starting Checkin Service.
06-01 22:14:52.003: INFO/SystemServer(62): Starting Wallpaper Service
06-01 22:14:52.013: DEBUG/WallpaperService(62): WallpaperService
startup
06-01 22:14:52.023: INFO/SystemServer(62): Starting Audio Service
06-01 22:14:52.083: DEBUG/AudioHardwareMSM72XX(35): setVoiceVolume
(0.60)
06-01 22:14:52.083: INFO/AudioHardwareMSM72XX(35): Setting in-call
volume to 3 (available range is 0 to 5)
06-01 22:14:52.163: DEBUG/AudioHardwareMSM72XX(35): setVoiceVolume
(1.00)
06-01 22:14:52.163: INFO/AudioHardwareMSM72XX(35): Setting in-call
volume to 5 (available range is 0 to 5)
06-01 22:14:52.183: DEBUG/dalvikvm(62): Trying to load lib /system/lib/
libsoundpool.so 0x0
06-01 22:14:52.203: DEBUG/dalvikvm(62): Added shared lib /system/lib/
libsoundpool.so 0x0
06-01 22:14:52.233: INFO/SystemServer(62): Starting HeadsetObserver
06-01 22:14:52.293: INFO/SystemServer(62): Starting AppWidget Service
06-01 22:14:52.763: DEBUG/dalvikvm(62): GC freed 4358 objects / 252408
bytes in 417ms
06-01 22:14:52.883: INFO/WindowManager(62): Menu key state: 0
safeMode=false
06-01 22:14:52.913: INFO/WindowManager(62): Config changed:
{ scale=1.0 imsi=0/0 locale=en_US touch=3 key=2/1/1 nav=3 orien=1 }
06-01 22:14:52.943: DEBUG/PowerManagerService(62): system ready!
06-01 22:14:52.963: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03
06-01 22:14:52.983: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03000c
06-01 22:14:52.993: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f03
06-01 22:14:53.003: WARN/ResourceType(62): No package identifier when
getting value for resource number 0x7f030003
06-01 22:14:53.253: DEBUG/dalvikvm(62): GC freed 2153 objects / 118592
bytes in 235ms
06-01 22:14:53.263: WARN/dalvikvm(62): threadid=13: thread exiting
with uncaught exception (group=0x4000fe70)
06-01 22:14:53.273: ERROR/AndroidRuntime(62): Uncaught handler: thread
android.server.ServerThread exiting due to uncaught exception
06-01 22:14:53.273: ERROR/AndroidRuntime(62): *** EXCEPTION IN SYSTEM
PROCESS.
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
* **visit my site and earn more money** * * http://latesttechnologyinfo.com/* * ** http://latesttechnologyinfo.com/* * **http://latesttechnologyinfo.com/* * ** http://latesttechnologyinfo.com/* * **http://latesttechnologyinfo.com/* * **http://latesttechnologyinfo.com/** * * http://latesttechnologyinfo.com/* --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
--- On wed, 6/3/09, numan numan@gmail.com wrote: hello my friend how are u latest summer fashion hot fashion videos visit my website http://www.fashioninfokit.com/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
oh by the way in case you are wondering, I am using the offical cupcake OTA update, NOT any modified rom On May 25, 7:12 am, zl25drexel zl25dre...@gmail.com wrote: Hey guys, you need to look into this, this morning I downloaded a soft keyboard (a Russian keyboard) from the market, disabled the build-in keyboard and enabled it in locale setting. Then without disabling it, I uninstall the keyboard using the uninstall button in market. Then my phone started to force closes over and over, looked at the logs, clearly the input method is crashing because it couldnt find the keyboard anymore, so I long pressed the power button and chose power off and rebooted the phone, the phone will NOT boot any more I was able to recover it by popping the battery and then hold Home button when powering on to get into recovery mode and did a alt-W to wipe the phone clear and started over. Now imagine someone dont know how to do that would think about the system. Even I recovered it, it's still a pain in the butt to setup everything again. See the logs below, YOU GOT TO FIX THIS W/HAL ( 132): load: module=/system/lib/hw/lights.trout.so error=Cannot find library W/HAL ( 132): load: module=/system/lib/hw/lights.trout.so error=Cannot find library I/SystemServer( 132): Starting Alarm Manager. I/SystemServer( 132): Starting Sensor Service. I/SystemServer( 132): Starting Window Manager. I/EventHub( 132): New device: path=/dev/input/event4 name=compass id=0x1 (of 0x1) index=1 fd=50 classes=0x0 D/SensorManager( 132): found sensor: AK8976A 3-axis Accelerometer, handle=0 D/SensorManager( 132): found sensor: AK8976A 3-axis Magnetic field sensor, handle=1 D/SensorManager( 132): found sensor: AK8976A Orientation sensor, handle=2 D/SensorManager( 132): found sensor: AK8976A Temperature sensor, handle=3 I/EventHub( 132): New device: path=/dev/input/event3 name=trout- keypad-v3 id=0x10001 (of 0x2) index=2 fd=51 classes=0x3 I/EventHub( 132): New keyboard: publicID=0 device-id=65537 devname='trout-keypad-v3' propName='hw.keyboards.0.devname' keylayout='/system/usr/keylayout/trout-keypad-v3.kl' I/SystemServer( 132): Starting Bluetooth Service. I/EventHub( 132): New device: path=/dev/input/event2 name=trout-nav id=0x10002 (of 0x3) index=3 fd=53 classes=0x8 I/EventHub( 132): New device: path=/dev/input/event1 name=synaptics- rmi-touchscreen id=0x10003 (of 0x4) index=4 fd=55 classes=0x4 I/SystemServer( 132): Starting Status Bar Service. I/EventHub( 132): New device: path=/dev/input/event0 name=h2w headset id=0x10004 (of 0x5) index=5 fd=56 classes=0x1 I/EventHub( 132): New keyboard: publicID=65540 device-id=65540 devname='h2w headset' propName='hw.keyboards.65540.devname' keylayout='/system/usr/keylayout/h2w_headset.kl' I/KeyInputQueue( 132): Device added: id=0x10004, name=h2w headset, classes=1 I/KeyInputQueue( 132): Device added: id=0x10003, name=null, classes=4 I/KeyInputQueue( 132): X: min=80 max=3400 flat=0 fuzz=0 I/KeyInputQueue( 132): Y: min=32 max=5336 flat=0 fuzz=0 I/KeyInputQueue( 132): Pressure: min=0 max=255 flat=0 fuzz=0 I/KeyInputQueue( 132): Size: min=0 max=15 flat=0 fuzz=0 I/KeyInputQueue( 132): Device added: id=0x10002, name=null, classes=8 I/KeyInputQueue( 132): Device added: id=0x0, name=trout-keypad-v3, classes=3 I/KeyInputQueue( 132): Device added: id=0x1, name=null, classes=0 I/SystemServer( 132): Starting Clipboard Service. I/SystemServer( 132): Starting Input Method Service. W/ResourceType( 132): No package identifier when getting value for resource number 0x7f060001 I/InputManagerService( 132): Enabled input methods: com.codesector.russian.keyboard/.SoftKeyboard W/InputManagerService( 132): Unknown input method from prefs: com.codesector.russian.keyboard/.SoftKeyboard W/InputManagerService( 132): java.lang.IllegalArgumentException: Unknown id: null W/InputManagerService( 132): at com.android.server.InputMethodManagerService.setInputMethodLocked (InputMethodManagerService.java:919) W/InputManagerService( 132): at com.android.server.InputMethodManagerService.updateFromSettingsLocked (InputMethodManagerService.java:903) W/InputManagerService( 132): at com.android.server.InputMethodManagerService.init (InputMethodManagerService.java:492) W/InputManagerService( 132): at com.android.server.ServerThread.run (SystemServer.java:209) I/SystemServer( 132): Starting NetStat Service. I/SystemServer( 132): Starting Connectivity Service. I/WifiService( 132): WifiService starting up with Wi-Fi enabled I/SystemServer( 132): Starting Notification Manager. I/SystemServer( 132): Starting Mount Service. I/SystemServer( 132): Starting DeviceStorageMonitor service I/SystemServer( 132): Starting Location Manager. V/WifiStateTracker( 132): Connection to supplicant established, state=COMPLETED W/BluetoothHeadset( 132): Proxy not attached to service D/WifiStateTracker( 132):
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
Granted, something looks really weird here. But please do not say the phone was bricked when it was not. You can also boot in safe mode by holding Menu during the boot sequence and use the safe mode to clear data/uninstall apps. On Mon, May 25, 2009 at 4:15 AM, AndroidApp zl25dre...@gmail.com wrote: oh by the way in case you are wondering, I am using the offical cupcake OTA update, NOT any modified rom On May 25, 7:12 am, zl25drexel zl25dre...@gmail.com wrote: Hey guys, you need to look into this, this morning I downloaded a soft keyboard (a Russian keyboard) from the market, disabled the build-in keyboard and enabled it in locale setting. Then without disabling it, I uninstall the keyboard using the uninstall button in market. Then my phone started to force closes over and over, looked at the logs, clearly the input method is crashing because it couldnt find the keyboard anymore, so I long pressed the power button and chose power off and rebooted the phone, the phone will NOT boot any more I was able to recover it by popping the battery and then hold Home button when powering on to get into recovery mode and did a alt-W to wipe the phone clear and started over. Now imagine someone dont know how to do that would think about the system. Even I recovered it, it's still a pain in the butt to setup everything again. See the logs below, YOU GOT TO FIX THIS W/HAL ( 132): load: module=/system/lib/hw/lights.trout.so error=Cannot find library W/HAL ( 132): load: module=/system/lib/hw/lights.trout.so error=Cannot find library I/SystemServer( 132): Starting Alarm Manager. I/SystemServer( 132): Starting Sensor Service. I/SystemServer( 132): Starting Window Manager. I/EventHub( 132): New device: path=/dev/input/event4 name=compass id=0x1 (of 0x1) index=1 fd=50 classes=0x0 D/SensorManager( 132): found sensor: AK8976A 3-axis Accelerometer, handle=0 D/SensorManager( 132): found sensor: AK8976A 3-axis Magnetic field sensor, handle=1 D/SensorManager( 132): found sensor: AK8976A Orientation sensor, handle=2 D/SensorManager( 132): found sensor: AK8976A Temperature sensor, handle=3 I/EventHub( 132): New device: path=/dev/input/event3 name=trout- keypad-v3 id=0x10001 (of 0x2) index=2 fd=51 classes=0x3 I/EventHub( 132): New keyboard: publicID=0 device-id=65537 devname='trout-keypad-v3' propName='hw.keyboards.0.devname' keylayout='/system/usr/keylayout/trout-keypad-v3.kl' I/SystemServer( 132): Starting Bluetooth Service. I/EventHub( 132): New device: path=/dev/input/event2 name=trout-nav id=0x10002 (of 0x3) index=3 fd=53 classes=0x8 I/EventHub( 132): New device: path=/dev/input/event1 name=synaptics- rmi-touchscreen id=0x10003 (of 0x4) index=4 fd=55 classes=0x4 I/SystemServer( 132): Starting Status Bar Service. I/EventHub( 132): New device: path=/dev/input/event0 name=h2w headset id=0x10004 (of 0x5) index=5 fd=56 classes=0x1 I/EventHub( 132): New keyboard: publicID=65540 device-id=65540 devname='h2w headset' propName='hw.keyboards.65540.devname' keylayout='/system/usr/keylayout/h2w_headset.kl' I/KeyInputQueue( 132): Device added: id=0x10004, name=h2w headset, classes=1 I/KeyInputQueue( 132): Device added: id=0x10003, name=null, classes=4 I/KeyInputQueue( 132): X: min=80 max=3400 flat=0 fuzz=0 I/KeyInputQueue( 132): Y: min=32 max=5336 flat=0 fuzz=0 I/KeyInputQueue( 132): Pressure: min=0 max=255 flat=0 fuzz=0 I/KeyInputQueue( 132): Size: min=0 max=15 flat=0 fuzz=0 I/KeyInputQueue( 132): Device added: id=0x10002, name=null, classes=8 I/KeyInputQueue( 132): Device added: id=0x0, name=trout-keypad-v3, classes=3 I/KeyInputQueue( 132): Device added: id=0x1, name=null, classes=0 I/SystemServer( 132): Starting Clipboard Service. I/SystemServer( 132): Starting Input Method Service. W/ResourceType( 132): No package identifier when getting value for resource number 0x7f060001 I/InputManagerService( 132): Enabled input methods: com.codesector.russian.keyboard/.SoftKeyboard W/InputManagerService( 132): Unknown input method from prefs: com.codesector.russian.keyboard/.SoftKeyboard W/InputManagerService( 132): java.lang.IllegalArgumentException: Unknown id: null W/InputManagerService( 132): at com.android.server.InputMethodManagerService.setInputMethodLocked (InputMethodManagerService.java:919) W/InputManagerService( 132): at com.android.server.InputMethodManagerService.updateFromSettingsLocked (InputMethodManagerService.java:903) W/InputManagerService( 132): at com.android.server.InputMethodManagerService.init (InputMethodManagerService.java:492) W/InputManagerService( 132): at com.android.server.ServerThread.run (SystemServer.java:209) I/SystemServer( 132): Starting NetStat Service. I/SystemServer( 132): Starting Connectivity Service. I/WifiService( 132): WifiService starting up with Wi-Fi enabled I/SystemServer( 132): Starting Notification Manager. I/SystemServer( 132):
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
Lol, I didnt expect to get a response this quickly. Romain you are up early (assuming you are still at the west coast) :-) Yes it was a little dramatic, but I was just pretending to be an ignorant user and tell you what someone dont know anything about safe mode and recovery mode would think. The very first I tried was safe mode, I dont think it worked, that's why I did a full wipe. Judging from the log, I dont think safe mode is going to help because the error came from a system service. I know software has bugs, but you guys are google, I expect you jump on an issue and fix it before you go to bed :-) On May 25, 7:18 am, Romain Guy romain...@google.com wrote: Granted, something looks really weird here. But please do not say the phone was bricked when it was not. You can also boot in safe mode by holding Menu during the boot sequence and use the safe mode to clear data/uninstall apps. On Mon, May 25, 2009 at 4:15 AM, AndroidApp zl25dre...@gmail.com wrote: oh by the way in case you are wondering, I am using the offical cupcake OTA update, NOT any modified rom On May 25, 7:12 am, zl25drexel zl25dre...@gmail.com wrote: Hey guys, you need to look into this, this morning I downloaded a soft keyboard (a Russian keyboard) from the market, disabled the build-in keyboard and enabled it in locale setting. Then without disabling it, I uninstall the keyboard using the uninstall button in market. Then my phone started to force closes over and over, looked at the logs, clearly the input method is crashing because it couldnt find the keyboard anymore, so I long pressed the power button and chose power off and rebooted the phone, the phone will NOT boot any more I was able to recover it by popping the battery and then hold Home button when powering on to get into recovery mode and did a alt-W to wipe the phone clear and started over. Now imagine someone dont know how to do that would think about the system. Even I recovered it, it's still a pain in the butt to setup everything again. See the logs below, YOU GOT TO FIX THIS W/HAL ( 132): load: module=/system/lib/hw/lights.trout.so error=Cannot find library W/HAL ( 132): load: module=/system/lib/hw/lights.trout.so error=Cannot find library I/SystemServer( 132): Starting Alarm Manager. I/SystemServer( 132): Starting Sensor Service. I/SystemServer( 132): Starting Window Manager. I/EventHub( 132): New device: path=/dev/input/event4 name=compass id=0x1 (of 0x1) index=1 fd=50 classes=0x0 D/SensorManager( 132): found sensor: AK8976A 3-axis Accelerometer, handle=0 D/SensorManager( 132): found sensor: AK8976A 3-axis Magnetic field sensor, handle=1 D/SensorManager( 132): found sensor: AK8976A Orientation sensor, handle=2 D/SensorManager( 132): found sensor: AK8976A Temperature sensor, handle=3 I/EventHub( 132): New device: path=/dev/input/event3 name=trout- keypad-v3 id=0x10001 (of 0x2) index=2 fd=51 classes=0x3 I/EventHub( 132): New keyboard: publicID=0 device-id=65537 devname='trout-keypad-v3' propName='hw.keyboards.0.devname' keylayout='/system/usr/keylayout/trout-keypad-v3.kl' I/SystemServer( 132): Starting Bluetooth Service. I/EventHub( 132): New device: path=/dev/input/event2 name=trout-nav id=0x10002 (of 0x3) index=3 fd=53 classes=0x8 I/EventHub( 132): New device: path=/dev/input/event1 name=synaptics- rmi-touchscreen id=0x10003 (of 0x4) index=4 fd=55 classes=0x4 I/SystemServer( 132): Starting Status Bar Service. I/EventHub( 132): New device: path=/dev/input/event0 name=h2w headset id=0x10004 (of 0x5) index=5 fd=56 classes=0x1 I/EventHub( 132): New keyboard: publicID=65540 device-id=65540 devname='h2w headset' propName='hw.keyboards.65540.devname' keylayout='/system/usr/keylayout/h2w_headset.kl' I/KeyInputQueue( 132): Device added: id=0x10004, name=h2w headset, classes=1 I/KeyInputQueue( 132): Device added: id=0x10003, name=null, classes=4 I/KeyInputQueue( 132): X: min=80 max=3400 flat=0 fuzz=0 I/KeyInputQueue( 132): Y: min=32 max=5336 flat=0 fuzz=0 I/KeyInputQueue( 132): Pressure: min=0 max=255 flat=0 fuzz=0 I/KeyInputQueue( 132): Size: min=0 max=15 flat=0 fuzz=0 I/KeyInputQueue( 132): Device added: id=0x10002, name=null, classes=8 I/KeyInputQueue( 132): Device added: id=0x0, name=trout-keypad-v3, classes=3 I/KeyInputQueue( 132): Device added: id=0x1, name=null, classes=0 I/SystemServer( 132): Starting Clipboard Service. I/SystemServer( 132): Starting Input Method Service. W/ResourceType( 132): No package identifier when getting value for resource number 0x7f060001 I/InputManagerService( 132): Enabled input methods: com.codesector.russian.keyboard/.SoftKeyboard W/InputManagerService( 132): Unknown input method from prefs: com.codesector.russian.keyboard/.SoftKeyboard W/InputManagerService( 132): java.lang.IllegalArgumentException: Unknown id: null
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
oh another thought, how about defaulting to safe mode if the boot wont finish for a couple time? Or show the safe mode option like windows do when the system was not shut down cleanly? You know there are a lot of people do not know about safe mode and recovery mode that are using the phone. On May 25, 7:18 am, Romain Guy romain...@google.com wrote: Granted, something looks really weird here. But please do not say the phone was bricked when it was not. You can also boot in safe mode by holding Menu during the boot sequence and use the safe mode to clear data/uninstall apps. On Mon, May 25, 2009 at 4:15 AM, AndroidApp zl25dre...@gmail.com wrote: oh by the way in case you are wondering, I am using the offical cupcake OTA update, NOT any modified rom On May 25, 7:12 am, zl25drexel zl25dre...@gmail.com wrote: Hey guys, you need to look into this, this morning I downloaded a soft keyboard (a Russian keyboard) from the market, disabled the build-in keyboard and enabled it in locale setting. Then without disabling it, I uninstall the keyboard using the uninstall button in market. Then my phone started to force closes over and over, looked at the logs, clearly the input method is crashing because it couldnt find the keyboard anymore, so I long pressed the power button and chose power off and rebooted the phone, the phone will NOT boot any more I was able to recover it by popping the battery and then hold Home button when powering on to get into recovery mode and did a alt-W to wipe the phone clear and started over. Now imagine someone dont know how to do that would think about the system. Even I recovered it, it's still a pain in the butt to setup everything again. See the logs below, YOU GOT TO FIX THIS W/HAL ( 132): load: module=/system/lib/hw/lights.trout.so error=Cannot find library W/HAL ( 132): load: module=/system/lib/hw/lights.trout.so error=Cannot find library I/SystemServer( 132): Starting Alarm Manager. I/SystemServer( 132): Starting Sensor Service. I/SystemServer( 132): Starting Window Manager. I/EventHub( 132): New device: path=/dev/input/event4 name=compass id=0x1 (of 0x1) index=1 fd=50 classes=0x0 D/SensorManager( 132): found sensor: AK8976A 3-axis Accelerometer, handle=0 D/SensorManager( 132): found sensor: AK8976A 3-axis Magnetic field sensor, handle=1 D/SensorManager( 132): found sensor: AK8976A Orientation sensor, handle=2 D/SensorManager( 132): found sensor: AK8976A Temperature sensor, handle=3 I/EventHub( 132): New device: path=/dev/input/event3 name=trout- keypad-v3 id=0x10001 (of 0x2) index=2 fd=51 classes=0x3 I/EventHub( 132): New keyboard: publicID=0 device-id=65537 devname='trout-keypad-v3' propName='hw.keyboards.0.devname' keylayout='/system/usr/keylayout/trout-keypad-v3.kl' I/SystemServer( 132): Starting Bluetooth Service. I/EventHub( 132): New device: path=/dev/input/event2 name=trout-nav id=0x10002 (of 0x3) index=3 fd=53 classes=0x8 I/EventHub( 132): New device: path=/dev/input/event1 name=synaptics- rmi-touchscreen id=0x10003 (of 0x4) index=4 fd=55 classes=0x4 I/SystemServer( 132): Starting Status Bar Service. I/EventHub( 132): New device: path=/dev/input/event0 name=h2w headset id=0x10004 (of 0x5) index=5 fd=56 classes=0x1 I/EventHub( 132): New keyboard: publicID=65540 device-id=65540 devname='h2w headset' propName='hw.keyboards.65540.devname' keylayout='/system/usr/keylayout/h2w_headset.kl' I/KeyInputQueue( 132): Device added: id=0x10004, name=h2w headset, classes=1 I/KeyInputQueue( 132): Device added: id=0x10003, name=null, classes=4 I/KeyInputQueue( 132): X: min=80 max=3400 flat=0 fuzz=0 I/KeyInputQueue( 132): Y: min=32 max=5336 flat=0 fuzz=0 I/KeyInputQueue( 132): Pressure: min=0 max=255 flat=0 fuzz=0 I/KeyInputQueue( 132): Size: min=0 max=15 flat=0 fuzz=0 I/KeyInputQueue( 132): Device added: id=0x10002, name=null, classes=8 I/KeyInputQueue( 132): Device added: id=0x0, name=trout-keypad-v3, classes=3 I/KeyInputQueue( 132): Device added: id=0x1, name=null, classes=0 I/SystemServer( 132): Starting Clipboard Service. I/SystemServer( 132): Starting Input Method Service. W/ResourceType( 132): No package identifier when getting value for resource number 0x7f060001 I/InputManagerService( 132): Enabled input methods: com.codesector.russian.keyboard/.SoftKeyboard W/InputManagerService( 132): Unknown input method from prefs: com.codesector.russian.keyboard/.SoftKeyboard W/InputManagerService( 132): java.lang.IllegalArgumentException: Unknown id: null W/InputManagerService( 132): at com.android.server.InputMethodManagerService.setInputMethodLocked (InputMethodManagerService.java:919) W/InputManagerService( 132): at com.android.server.InputMethodManagerService.updateFromSettingsLocked (InputMethodManagerService.java:903) W/InputManagerService( 132): at
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
just tried to reproduce it by installing and uinstalling keyboard, that didnt crash the phone, so it looks like it's a widget service problem. On May 25, 7:42 am, AndroidApp zl25dre...@gmail.com wrote: oh another thought, how about defaulting to safe mode if the boot wont finish for a couple time? Or show the safe mode option like windows do when the system was not shut down cleanly? You know there are a lot of people do not know about safe mode and recovery mode that are using the phone. On May 25, 7:18 am, Romain Guy romain...@google.com wrote: Granted, something looks really weird here. But please do not say the phone was bricked when it was not. You can also boot in safe mode by holding Menu during the boot sequence and use the safe mode to clear data/uninstall apps. On Mon, May 25, 2009 at 4:15 AM, AndroidApp zl25dre...@gmail.com wrote: oh by the way in case you are wondering, I am using the offical cupcake OTA update, NOT any modified rom On May 25, 7:12 am, zl25drexel zl25dre...@gmail.com wrote: Hey guys, you need to look into this, this morning I downloaded a soft keyboard (a Russian keyboard) from the market, disabled the build-in keyboard and enabled it in locale setting. Then without disabling it, I uninstall the keyboard using the uninstall button in market. Then my phone started to force closes over and over, looked at the logs, clearly the input method is crashing because it couldnt find the keyboard anymore, so I long pressed the power button and chose power off and rebooted the phone, the phone will NOT boot any more I was able to recover it by popping the battery and then hold Home button when powering on to get into recovery mode and did a alt-W to wipe the phone clear and started over. Now imagine someone dont know how to do that would think about the system. Even I recovered it, it's still a pain in the butt to setup everything again. See the logs below, YOU GOT TO FIX THIS W/HAL ( 132): load: module=/system/lib/hw/lights.trout.so error=Cannot find library W/HAL ( 132): load: module=/system/lib/hw/lights.trout.so error=Cannot find library I/SystemServer( 132): Starting Alarm Manager. I/SystemServer( 132): Starting Sensor Service. I/SystemServer( 132): Starting Window Manager. I/EventHub( 132): New device: path=/dev/input/event4 name=compass id=0x1 (of 0x1) index=1 fd=50 classes=0x0 D/SensorManager( 132): found sensor: AK8976A 3-axis Accelerometer, handle=0 D/SensorManager( 132): found sensor: AK8976A 3-axis Magnetic field sensor, handle=1 D/SensorManager( 132): found sensor: AK8976A Orientation sensor, handle=2 D/SensorManager( 132): found sensor: AK8976A Temperature sensor, handle=3 I/EventHub( 132): New device: path=/dev/input/event3 name=trout- keypad-v3 id=0x10001 (of 0x2) index=2 fd=51 classes=0x3 I/EventHub( 132): New keyboard: publicID=0 device-id=65537 devname='trout-keypad-v3' propName='hw.keyboards.0.devname' keylayout='/system/usr/keylayout/trout-keypad-v3.kl' I/SystemServer( 132): Starting Bluetooth Service. I/EventHub( 132): New device: path=/dev/input/event2 name=trout-nav id=0x10002 (of 0x3) index=3 fd=53 classes=0x8 I/EventHub( 132): New device: path=/dev/input/event1 name=synaptics- rmi-touchscreen id=0x10003 (of 0x4) index=4 fd=55 classes=0x4 I/SystemServer( 132): Starting Status Bar Service. I/EventHub( 132): New device: path=/dev/input/event0 name=h2w headset id=0x10004 (of 0x5) index=5 fd=56 classes=0x1 I/EventHub( 132): New keyboard: publicID=65540 device-id=65540 devname='h2w headset' propName='hw.keyboards.65540.devname' keylayout='/system/usr/keylayout/h2w_headset.kl' I/KeyInputQueue( 132): Device added: id=0x10004, name=h2w headset, classes=1 I/KeyInputQueue( 132): Device added: id=0x10003, name=null, classes=4 I/KeyInputQueue( 132): X: min=80 max=3400 flat=0 fuzz=0 I/KeyInputQueue( 132): Y: min=32 max=5336 flat=0 fuzz=0 I/KeyInputQueue( 132): Pressure: min=0 max=255 flat=0 fuzz=0 I/KeyInputQueue( 132): Size: min=0 max=15 flat=0 fuzz=0 I/KeyInputQueue( 132): Device added: id=0x10002, name=null, classes=8 I/KeyInputQueue( 132): Device added: id=0x0, name=trout-keypad-v3, classes=3 I/KeyInputQueue( 132): Device added: id=0x1, name=null, classes=0 I/SystemServer( 132): Starting Clipboard Service. I/SystemServer( 132): Starting Input Method Service. W/ResourceType( 132): No package identifier when getting value for resource number 0x7f060001 I/InputManagerService( 132): Enabled input methods: com.codesector.russian.keyboard/.SoftKeyboard W/InputManagerService( 132): Unknown input method from prefs: com.codesector.russian.keyboard/.SoftKeyboard W/InputManagerService( 132): java.lang.IllegalArgumentException: Unknown id: null W/InputManagerService( 132): at
[android-developers] Re: My good god, bugs in Android brick phone, and it's not difficult to reproduce...
AndroidApp wrote: just tried to reproduce it by installing and uinstalling keyboard, that didnt crash the phone, so it looks like it's a widget service problem. That was my interpretation from your posted stack trace. Did you have any widgets on your home screen beyond the standard ones? If you wish, post the stack trace over on http://b.android.com, so it doesn't get lost. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
