来自测试人员的报告如下:
java.lang.RuntimeException: bad array lengthsat androID.os.Parcel.readIntArray(Parcel.java:820)at androID.app.Inotificationmanager$Stub$Proxy.enqueueNotificationWithTag(Inotificationmanager.java:348)at androID.app.notificationmanager.notify(notificationmanager.java:139)at androID.app.notificationmanager.notify(notificationmanager.java:112)at als.wakeup.Awake_Alarm$MyLocationListener.onLocationChanged(Awake_Alarm.java:272)at androID.location.LocationManager$ListenerTransport._handleMessage(LocationManager.java:279)at androID.location.LocationManager$ListenerTransport.accesspublic Notification CreateNotification(double distance){ Intent notificationIntentStop = new Intent(this.getApplicationContext(),StopService.class); PendingIntent contentIntentStop = PendingIntent.getActivity(this.getApplicationContext(),notificationIntentStop,0); Bitmap largeIcon = BitmapFactory.decodeResource(getResources(),R.drawable.logo); Shortcuts shorts = new Shortcuts(this); NotificationCompat.Builder mBuilder = new NotificationCompat.Builder(this) .setSmallicon(R.drawable.logo) .setContentTitle("Localarm Running") .setLargeIcon(largeIcon); //mBuilder.addAction(R.drawable.ico,"Stop",contentIntentStop); if(distance > 0){ mBuilder.setContentText(String.valueOf(roundTwoDecimals(shorts.ConvertUnits(distance))+" "+shorts.GetUnitnames(distance)+" to Alarm.")); } else{ mBuilder.setContentText(String.valueOf("You've reached your destination")); } mBuilder.setPriority(Notification.PRIORITY_MAX); Notification bui = mBuilder.build(); bui.flags|= Notification.FLAG_NO_CLEAR; Intent notificationIntent = new Intent(this.getApplicationContext(),Intro.class); PendingIntent contentIntent = PendingIntent.getActivity(this.getApplicationContext(),notificationIntent,0); bui.contentIntent = contentIntent; return bui;}0(LocationManager.java:208)at androID.location.LocationManager$ListenerTransport.handleMessage(LocationManager.java:224)at androID.os.Handler.dispatchMessage(Handler.java:102)at androID.os.Looper.loop(Looper.java:157)at androID.app.ActivityThread.main(ActivityThread.java:5293)at java.lang.reflect.Method.invokeNative(Native Method)at java.lang.reflect.Method.invoke(Method.java:515)at com.androID.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1265)at com.androID.internal.os.ZygoteInit.main(ZygoteInit.java:1081)at dalvik.system.NativeStart.main(Native Method)
这可以在4.2,4.3中正常工作,但似乎galaxy Note 3和galaxy S5运行4.4重新启动.
原因是什么?它是应用程序相关的还是可能在新的 *** 作系统中出现故障?
刚刚发现,它在Xperia Z1上工作正常,4.4,没有崩溃.似乎只有三星呢这样做,有什么提示?
通知创建功能:
notificationmanager notificationmanager = (notificationmanager) getSystemService(NOTIFICATION_SERVICE); notificationmanager.notify(0,CreateNotification(dist_difference-alert_range));
它被调用:onLocationChanged()
解决方法 这是一个 issue in Android.不幸的是,我不认为你可以做任何事情. 总结以上是内存溢出为你收集整理的android – 不好的数组长度,通知管理器导致电话崩溃4.4全部内容,希望文章能够帮你解决android – 不好的数组长度,通知管理器导致电话崩溃4.4所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。
欢迎分享,转载请注明来源:内存溢出
评论列表(0条)