android 异常发生的位置日志显示类名.a(unknow source) 是什么意思？
E/RRCTRL_RADIO( 1276): RadioSSeeking&&&freq=96400,signal=0.
E/AndroidRuntime( 1796): FATAL EXCEPTION: main
E/AndroidRuntime( 1796): java.lang.IndexOutOfBoundsException: Invalid index 10, size is 10
E/AndroidRuntime( 1796):
at java.util.ArrayList.throwIndexOutOfBoundsException(ArrayList.java:251)
E/AndroidRuntime( 1796):
at java.util.ArrayList.get(ArrayList.java:304)
E/AndroidRuntime( 1796):
at com.roadrover.radio.MainActivity.a(Unknown Source)
E/AndroidRuntime( 1796):
at com.roadrover.radio.a.handleMessage(Unknown Source)
E/AndroidRuntime( 1796):
at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1796):
at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 1796):
at android.app.ActivityThread.main(ActivityThread.java:4745)
E/AndroidRuntime( 1796):
at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1796):
at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 1796):
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 1796):
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 1796):
at dalvik.system.NativeStart.main(Native Method)
E/RRCTRL_MBP( 1276): MCUReadProcess
其他相似问题
相关参考资料Trolls, feel free to skip to the bottom of this column and post your comments immediately without reading a word. Actually, who are we kidding — you didn’t make it this far.
Everyone else, brace yourselves. You may want small children to leave the room. I’m about to do something I don’t do often — something I always said I’d do if the product deserved it. Something some people seem to think I’m incapable of: praise a Google product — an Android-based Google product, no less.
Is that enough build up for you? Okay.
I like the Nexus 7. I really like it.
I was out of town during Google I/O this year and missed the opportunity to see the unveiling and get my hands on the product a few weeks back. But Google was kind enough to give me a Nexus 7 demo unit last week.
the company credit for this before. For the most part, they don’t mind criticism and genuinely seem to want to build products that all consumers (whether Apple fans or not) will like. And with the Nexus 7, I think they’ve done just that.
To be clear, the product isn’t perfect. But no product is. Yes, that includes Apple products (though the MacBook Air in the pre-retina world was pretty damn close, in my opinion). But with the Nexus 7, Google has, for the first time, created an Android product that I would buy for myself. And I wouldn’t have an issue recommending it to anyone else.
Everyone already knows the device’s two key features: the 7-inch screen and the $199 price. Both have been rumored for months. And I was highly skeptical of both. I love my iPad from the screen size on down. And I didn’t think it would be possible to build a great tablet at such a low price.
But I was wrong.
Granted, Google isn’t making any money selling the device at $199 — at least not directly. And the device isn’t quite iPad-quality. But the iPad starts at $499. This is less than half the price. And the build quality is very good.
Normally when I get a review unit of a non-Apple product, I have to force myself to use it to get a sense of how I might use it in the real world. But with the Nexus 7, I actually find myself wanting to use it. That point can’t be overstated. I actually want to use an Android device. It’s a brave new world.
For me, the key is the size. Again, I was skeptical at first, but for many situations, I’ve come to love the 7-inch frame. The iPad is brilliant when you’re sitting on a couch or camped out in a coffee shop. In my view, the 9.7-inch iPad is slowly but surely becoming a laptop replacement. I expect this to continue. But a 7-inch tablet is different. The iPad is clunky to read in bed, for example. The Nexus 7 is perfect for that.
More broadly, the 7-inch tablet further opens the door to true mobile computing. I find myself constantly using it while walking around the house (as opposed to sitting on the couch). And I don’t think twice about shoving it in my bag when I take off for the day (as I sometimes do with my iPad when I have my laptop with me). Many could say the same about the iPad, but in my view, the 7-inch tablet is more desirable in many circumstances simply because it’s — shocker — smaller. 9.7 inches versus 7 inches may not seem like a huge difference. But it is.
Whereas laptop sizes vary mainly to please screen size preference, I suspect that 7-inch tablets will fit naturally into different use cases than 10-inch tablets. In other words, I believe they’ll end up being closer to two different categories rather than two variations of the same category.
Having used a 7-inch tablet for the past week, I now see it as an
that Apple has to make an iPad with this form factor as well. Of course, such rumors have been swirling for a while — and now the smoke seems too thick for there not to be a fire. It’s coming — but when it does, Apple will find itself in a position it hasn’t been in for some time: being a second-mover to a good product already on the market (as opposed to being a second-mover to a bunch of mediocre-to-shitty products, as has been the case many times in the past).
Back to the Nexus 7 (sorry, this is an “Apple column” remember). For now, its true competitor is the Kindle Fire. But calling the Kindle Fire a “competitor” is probably being too kind to Amazon. All I know is that Amazon better hope their next version of the device is ready to go ASAP and that it’s significantly better than the first version. Because the Nexus 7 seems far better in pretty much every way.
Loaded with Android 4.1 “Jelly Bean”, the Nexus 7 is as fast as advertised. I do spot some lag from time to time (the swiping between main screens could still be smoother when a live wallpaper is running, but that’s a minor thing most regular users probably won’t notice), but it’s almost always within apps which don’t seem custom-tailored for the new OS yet. A good example is the Facebook app. iOS users constantly complain about this app being slow and unreliable — on Android, it’s much worse. That includes on the Nexus 7.
With the Google-built apps, Jelly Bean runs great. Overall, the OS doesn’t seem all that different from Android 4.0 “Ice Cream Sandwich”, but it’s more refined. I imagine it’s similar to what we’ll see with iOS 6 versus iOS 5. These mobile OSes are getting mature enough now where it’s more about refinement. For a long time, Android needed far more than polish. Now it’s at that stage.
Gaming had been one problematic area in the past for Android. With the Nexus 7 and Jelly Bean, it’s solid. I played several games that I play on iOS devices to compare — games like Canabalt, Osmos, Sky Safari, Angry Birds, World of Goo, Flick Golf, and Fruit Ninja. All now seem to run just as well as they do on iOS devices.
While the Nexus 7 has access to apps like Flipboard (and it runs great on the device, though without access to New York Times content, oddly), other apps like Instagram and Tumblr can’t be installed because they say the device isn’t supported. I’m told this is due to code in those apps which puts a “ceiling” on the Android version number on which they can be installed, and this should be fixed soon.
This brings up another important issue: because this is a Nexus device that Google built in conjunction with Asus, it should be fairly future-proof for future versions of Android and apps that require the more advanced APIs they provide. While previous Nexus devices still had issues getting timely updates, the Nexus 7 is WiFi-only, meaning the carriers have absolutely no say when it comes to updates here. In other words, goodbye bottlenecks.
But this is a double-edged sword. One of my favorite aspects of the new iPad is the 4G connectivity both because it’s really, really fast and because it works basically everywhere. With the Nexus 7, you have to rely on a WiFi connection. Again, while that’s great news for future updates, it’s bad news for true road warriors. (It also makes Google Now, the tentpole new feature of Jelly Bean, less useful because it can’t constantly send you new information based on your location.) Still, given Google’s difficulties in dealing with the carriers in the past, I think this was the right call.
As you might imagine, the lack of cellular radio also seems to help the battery life of the device quite a bit. It’s fantastic.
Another nit I have with the 7 involves the software system buttons. A number of times while playing a game in horizontal mode, I would inadvertently activate the buttons and hit one of them. The issue is that because the screen is so small, it’s a bit awkward to use with two hands. Likewise, in portrait mode, there isn’t much of a bezel to grip. It’s easy enough to hold with one hand, but for an iPad user (which features a much larger bezel), this took some getting used to.
When you first boot up the Nexus 7, you’ll notice that Google has given prominent position to Google Play media items. In fact, that entire main screen is dominated by a rather ridiculously large “My Library” widget (which I quickly replaced with my favorite apps instead). This is a weird choice because one area of weakness for the device is the media catalog. The Google Play store still doesn’t have access to any Warner music, for example. And the film, television, magazine, and book libraries are smaller than those that Apple and Amazon offer. I suppose this was a decision made to go right after the Kindle Fire (a “media tablet”), but again, Amazon still wins that battle. It’s not a huge deal, just an odd choice, in my opinion.
Now I’m back to focusing on the negative — old habits die hard, sorry. Again, the fact remains that the Nexus 7 is a great device. Not a great device graded on some weird curve where we pretend that Apple products don’t exist — but a great device, period. The $199 price point is just icing on the cake.
If you’re an iOS person like myself, you obviously have to think about Apple moving into this space as well. And I think the Nexus 7 shows a few places where Apple can improve the 7-inch tablet space — namely in making a device
so it’s easier to hold with two hands, and using their existing pay-as-you-go carrier deals to offer up 3G/4G connectivity. We’ll see.
But for now, Apple’s not in this space. And the clear winner in this space is the Nexus 7.
Enter Address
Popular Posts手机不知道在下载什么东西，出现的是feeliu-android-px.1.a是什么意思，打不开也关不掉_百度知道
手机不知道在下载什么东西，出现的是feeliu-android-px.1.a是什么意思，打不开也关不掉
提问者采纳
.好像不下载完怎么都删不了 下载又猛烧流量 坑爷啊.
采纳率100%
其他类似问题
android的相关知识
按默认排序
其他3条回答
在删除，应该在文件夹里的2个文件中，如果没有只能恢复出厂了。希望你可以满意，删除一个叫renmering-c的文件，我也没有办法了，打开手机中的feeliu-android文件，或者叫懂的人去手机维修店
这是安卓系统的一个下载工具叫飞流下载，是，也不是很大，3m左右
个信软件 没事的 用10M左右流量完成！
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁&&&&& 在开发Android应用时必须遵守单线程模型的原则： Android UI操作并不是线程安全的并且这些操作必须在UI线程中执行。在单线程模型中始终要记住两条法则： 1. 不要阻塞UI线程 2. 确保只在UI线程中访问Android UI工具包 &&&& &当一个程序第一次启动时，Android会同时启动一个对应的主线程(Main Thread)，主线程主要负责处理与UI相关的事件，如：用户的按键事件，用户接触屏幕的事件以及屏幕绘图事件，并把相关的事件分发到对应的组件进行处理。所以主线程通常又被叫做UI线程。 &&&& &比如说从网上获取一个网页，在一个TextView中将其源代码显示出来，这种涉及到网络操作的程序一般都是需要开一个线程完成网络访问，但是在获得页面源码后，是不能直接在网络操作线程中调用TextView.setText()的.因为其他线程中是不能直接访问主UI线程成员 。
android提供了几种在其他线程中访问UI线程的方法。 Activity.runOnUiThread( Runnable ) View.post( Runnable ) View.postDelayed( Runnable, long ) Hanlder 这些类或方法同样会使你的代码很复杂很难理解。然而当你需要实现一些很复杂的操作并需要频繁地更新UI时这会变得更糟糕。 &&&& 为了解决这个问题，Android 1.5提供了一个工具类：AsyncTask，它使创建需要与用户界面交互的长时间运行的任务变得更简单。相对来说AsyncTask更轻量级一些，适用于简单的异步处理，不需要借助线程和Handler即可实现。 AsyncTask是抽象类.AsyncTask定义了三种泛型类型 Params，Progress和Result。 　　Params 启动任务执行的输入参数，比如HTTP请求的URL。 　　Progress 后台任务执行的百分比。 　　Result 后台执行任务最终返回的结果，比如String。 &&&& AsyncTask的执行分为四个步骤，每一步都对应一个回调方法，这些方法不应该由应用程序调用，开发者需要做的就是实现这些方法。 　　1) 子类化AsyncTask 　　2) 实现AsyncTask中定义的下面一个或几个方法 　　&& onPreExecute(), 该方法将在执行实际的后台操作前被UI thread调用。可以在该方法中做一些准备工作，如在界面上显示一个进度条。 　　& doInBackground(Params...), 将在onPreExecute 方法执行后马上执行，该方法运行在后台线程中。这里将主要负责执行那些很耗时的后台计算工作。可以调用 publishProgress方法来更新实时的任务进度。该方法是抽象方法，子类必须实现。 　　& onProgressUpdate(Progress...),在publishProgress方法被调用后，UI thread将调用这个方法从而在界面上展示任务的进展情况，例如通过一个进度条进行展示。 　　& onPostExecute(Result), 在doInBackground 执行完成后，onPostExecute 方法将被UI thread调用，后台的计算结果将通过该方法传递到UI thread. 为了正确的使用AsyncTask类，以下是几条必须遵守的准则： 　　1) Task的实例必须在UI thread中创建 　　2) execute方法必须在UI thread中调用 　　3) 不要手动的调用onPreExecute(), onPostExecute(Result)，doInBackground(Params...), onProgressUpdate(Progress...)这几个方法 　　4) 该task只能被执行一次，否则多次调用时将会出现异常 &&&&& doInBackground方法和onPostExecute的参数必须对应，这两个参数在AsyncTask声明的泛型参数列表中指定，第一个为doInBackground接受的参数，第二个为显示进度的参数，第第三个为doInBackground返回和onPostExecute传入的参数。
从网上获取一个网页，在一个TextView中将其源代码显示出来
package&test.import&java.io.ByteArrayOutputSimport&java.io.InputSimport&java.util.ArrayLimport&org.apache.http.HttpEimport&org.apache.http.HttpRimport&org.apache.http.client.HttpCimport&org.apache.http.client.methods.HttpGimport&org.apache.http.impl.client.DefaultHttpCimport&android.app.Aimport&android.app.ProgressDimport&android.content.Cimport&android.content.DialogIimport&android.os.AsyncTimport&android.os.Bimport&android.os.Himport&android.os.Mimport&android.view.Vimport&android.widget.Bimport&android.widget.EditTimport&android.widget.TextVpublic&class&NetworkActivity&extends&Activity{&&&&private&TextView&&&&&private&Button&&&&&private&EditText&&&&&@Override&&&&public&void&onCreate(Bundle&savedInstanceState)&{&&&&&&&super.onCreate(savedInstanceState);&&&&&&&setContentView(R.layout.network);&&&&&&&message=&(TextView)&findViewById(R.id.message);&&&&&&&url=&(EditText)&findViewById(R.id.url);&&&&&&&open=&(Button)&findViewById(R.id.open);&&&&&&&open.setOnClickListener(new&View.OnClickListener()&{&&&&&&&&&&&public&void&onClick(View&arg0)&{&&&&&&&&&&&&&&connect();&&&&&&&&&&&}&&&&&&&});&&&&}&&&&private&void&connect()&{&&&&&&&&PageTask&task&=&new&PageTask(this);&&&&&&&&task.execute(url.getText().toString());&&&&}&&&&class&PageTask&extends&AsyncTask&String,&Integer,&String&&{&&&&&&&&//&可变长的输入参数，与AsyncTask.exucute()对应&&&&&&&&ProgressDialog&&&&&&&&&public&PageTask(Context&context){&&&&&&&&&&&&pdialog&=&new&ProgressDialog(context,&<span style="color: #);&&&&&&&&&&&&&&&pdialog.setButton("cancel",&new&DialogInterface.OnClickListener()&{&&&&&&&&&&&&&public&void&onClick(DialogInterface&dialog,&int&i)&{&&&&&&&&&&&&&&dialog.cancel();&&&&&&&&&&&&&}&&&&&&&&&&&&});&&&&&&&&&&&&pdialog.setOnCancelListener(new&DialogInterface.OnCancelListener()&{&&&&&&&&&&&&&public&void&onCancel(DialogInterface&dialog)&{&&&&&&&&&&&&&&finish();&&&&&&&&&&&&&}&&&&&&&&&&&&});&&&&&&&&&&&&pdialog.setCancelable(true);&&&&&&&&&&&&pdialog.setMax(<span style="color: #0);&&&&&&&&&&&&pdialog.setProgressStyle(ProgressDialog.STYLE_HORIZONTAL);&&&&&&&&&&&&pdialog.show();&&&&&&&&}&&&&&&&&@Override&&&&&&&&protected&String&doInBackground(String...&params)&{&&&&&&&&&&&&try{&&&&&&&&&&&&&&&HttpClient&client&=&new&DefaultHttpClient();&&&&&&&&&&&&&&&//&params[0]代表连接的url&&&&&&&&&&&&&&&HttpGet&get&=&new&HttpGet(params[<span style="color: #]);&&&&&&&&&&&&&&&HttpResponse&response&=&client.execute(get);&&&&&&&&&&&&&&&HttpEntity&entity&=&response.getEntity();&&&&&&&&&&&&&&&long&length&=&entity.getContentLength();&&&&&&&&&&&&&&&InputStream&is&=&entity.getContent();&&&&&&&&&&&&&&&String&s&=&null;&&&&&&&&&&&&&&&if(is&!=&null)&{&&&&&&&&&&&&&&&&&&&ByteArrayOutputStream&baos&=&new&ByteArrayOutputStream();&&&&&&&&&&&&&&&&&&&byte[]&buf&=&new&byte[<span style="color: #8];&&&&&&&&&&&&&&&&&&&int&ch&=&-<span style="color: #;&&&&&&&&&&&&&&&&&&&int&count&=&<span style="color: #;&&&&&&&&&&&&&&&&&&&while((ch&=&is.read(buf))&!=&-<span style="color: #)&{&&&&&&&&&&&&&&&&&&&&&&baos.write(buf,&<span style="color: #,&ch);&&&&&&&&&&&&&&&&&&&&&&count&+=&&&&&&&&&&&&&&&&&&&&&&&if(length&&&<span style="color: #)&{&&&&&&&&&&&&&&&&&&&&&&&&&&//&如果知道响应的长度，调用publishProgress（）更新进度&&&&&&&&&&&&&&&&&&&&&&&&&&publishProgress((int)&((count&/&(float)&length)&*&<span style="color: #0));&&&&&&&&&&&&&&&&&&&&&&}&&&&&&&&&&&&&&&&&&&&&&//&让线程休眠100ms&&&&&&&&&&&&&&&&&&&&&&Thread.sleep(<span style="color: #0);&&&&&&&&&&&&&&&&&&&}&&&&&&&&&&&&&&&&&&&s&=&new&String(baos.toByteArray());&&&&&&&&&&&&&&}&&&&&&&&&&&&&&&//&返回结果&&&&&&&&&&&&&&&return&s;&&&&&&&&&&&&}&catch(Exception&e)&{&&&&&&&&&&&&&&&e.printStackTrace();&&&&&&&&&&&&}&&&&&&&&&&&&return&null;&&&&&&&&}&&&&&&&&@Override&&&&&&&&protected&void&onCancelled()&{&&&&&&&&&&&&super.onCancelled();&&&&&&&&}&&&&&&&&@Override&&&&&&&&protected&void&onPostExecute(String&result)&{&&&&&&&&&&&&//&返回HTML页面的内容&&&&&&&&&&&&message.setText(result);&&&&&&&&&&&&pdialog.dismiss();&&&&&&&&&}&&&&&&&&@Override&&&&&&&&protected&void&onPreExecute()&{&&&&&&&&&&&&//&任务启动，可以在这里显示一个对话框，这里简单处理&&&&&&&&&&&&message.setText(R.string.task_started);&&&&&&&&}&&&&&&&&@Override&&&&&&&&protected&void&onProgressUpdate(Integer...&values)&{&&&&&&&&&&&&//&更新进度&&&&&&&&&&&&&&System.out.println(""+values[<span style="color: #]);&&&&&&&&&&&&&&message.setText(""+values[<span style="color: #]);&&&&&&&&&&&&&&pdialog.setProgress(values[<span style="color: #]);&&&&&&&&}&&&&&}}
最后需要说明AsyncTask不能完全取代线程，在一些逻辑较为复杂或者需要在后台反复执行的逻辑就可能需要线程来实现了。
阅读(...) 评论()}