Catch Bugs Together —— Summary of Android 5.0 Bug

Android 5.0 Bug:Nexus 7 can't play video.

Android 5.0 provides upgrade support for two generations of Nexus 7, which is a good thing. Unfortunately, Android 5.0 in Nexus 7 20 13 will cause the problem that the video cannot be played. Users found that after Nexus 7 20 13 was upgraded to Android 5.0, playing video would fail, mainly in the native system player of Android 5.0. The developer studied the system log and found the following fields:

Simply put, the reason is that the video player has lost the position of the video track. If you want to solve the problem, you can try to shut down and restart first. If it is not solved, enter the Settings-Developer option, close and restart "Use NuPlayer". If it really doesn't work, it can be solved by restoring the factory settings, but it will also lose data.

This Android 5.0 problem will affect the playback of online videos (YouTube, etc.). ) and local videos are still very troublesome. To solve it completely, we have to wait for Google's follow-up update.

Android 5.0 Bug: flashlight causes camera failure

Android 5.0 introduces the native flashlight function of the system, and you can see the shortcut button of the flashlight in the drop-down notification bar. This is a very convenient design, but it brings trouble-in Android 5.0, the flashlight function may cause the camera to fail, and neither the native system camera nor other camera apps can call the camera.

In Android 5.0, if the flashlight is turned on and not turned off manually, it will go out automatically after a certain period of time, which makes the camera unusable. At this point, whether you want to turn on the flashlight or turn on the camera again, you will be prompted "Unable to connect the camera". This error should be because after the flashlight goes out automatically, the corresponding process still occupies the calling interface of the camera, resulting in other apps being unable to call the camera.

This error needs to be solved by restarting the system, but it is easy to avoid-just don't let the flashlight go out automatically. Be careful not to turn on the flashlight for a long time at ordinary times to avoid this trouble.

Android 5.0 Bug: SMS may not be sent.

In order to adapt to the mobile network, Google deliberately postponed the Android 5.0 upgrade of Nexus 4 and Nexus 5. However, the problem still arises. Users found that under the network of some operators, Android 5.0 could not send short messages, while Android 4.4 did not have this problem. It seems that Google's work to adapt to the network is not so perfect.

After upgrading to Android 5.0, some users will be prompted with "error code 38" when sending short messages, and short messages cannot be sent. At present, it is known that Vodafone in the Netherlands, Mobistar in Belgium and some operators in India are all affected by this Bug, and there is no solution at present. If you want to use SMS normally, you can only drop back to the old version of Android. Fortunately, Google already knows about this Bug, and I believe that a patch will appear soon.

Android 5.0 Bug: Switching to Canadian French causes crash.

This is a very bad question. If Android 5.0 uses Canadian French as the system language, the system interface will crash frequently and will not work normally at all. This problem may not appear, but once it does, it will be enough to make people crazy. In short, Canadian users have complained.

In Android 5.0, if the system language is set to Franais (Canada), the user interface of the system will always crash when charging or synchronizing, but it is no problem to unplug the charger. At the same time, it is also French. If you choose French (Franais), there will be no problem. This Bug is really strange.

Choosing Canadian French for Android 5.0 may cause the system interface to crash.

Google employees have responded to this, confirmed the existence of this Bug, and said that this Bug was originally a problem with the old version and should have been fixed. I don't know why the old disease recurred in the public edition. Google, please have more snacks during the exam!

Android 5.0 Bug: unable to connect to corporate WiFi.

Android 5.0 has greatly increased security and should be attractive to enterprise users. But unfortunately, Android 5.0 made a mistake in enterprise applications. Some users reported that Android 5.0 could not connect to encrypted enterprise WiFi, which brought great trouble to the work.

There is a problem with Android 5.0 connecting to corporate WiFi.

It is reported that a large number of users have confirmed this problem. After investigation, the fault scope is locked in the compatibility problem of Cisco routers with WPA2 AES encryption enabled. If Android 5.0 connects to the new WiFi network of this kind of router, there is no response after entering the password and clicking Save Connection, and the problem 100% reappears.

This problem only occurs when connecting to a new WiFi network. If the corresponding encrypted network has been saved in the old system Android 4.4, you can connect automatically when upgrading to Android 5.0. Once you need to connect to a network you have never seen before, you will not be able to connect. This problem is still very troublesome, I hope Google can solve it as soon as possible.

Android 5.0 Bug: synchronization menu design error

This is a small problem with little influence, but the error is so low that people can't help laughing. In the synchronization menu of Android 5.0, click the three-point button in the upper right corner to bring up the menu, and you will find that the first item that pops up is not "synchronize now", but "cancel synchronization", even if there is no synchronization at present. So what happens when you click this option without synchronization? The answer is nothing will happen. Under normal circumstances, if there is no synchronization behavior, this option should be "synchronize now", and Google made a design mistake.

Android 5.0 will have a menu to cancel synchronization even if it is not synchronized, but this menu is invalid.

Even weirder, if you don't check a synchronization item, then check it again, and then click the menu, you will find the "synchronize now" button! This problem has been reported to Google twice, but Google did not mark it as a Bug. I don't know when the problem can be fixed.

Android 5.0 design flaw: shortcut keys cannot be deleted.

Android 5.0 has a great new feature. If you check an item in the Settings menu, it will appear in the list of shortcut buttons in the drop-down notification bar. For example, if you turn on screen rotation in the settings, the shortcut switch for screen rotation will become a button and be nailed to the shortcut button list. This is really convenient, but the problem arises-this button can't be removed.

What problems will this cause? If you switch an unpopular function in the settings menu, such as the new "reverse color" in Android 5.0, you can change the color scheme of the system to reverse color, then this function will always stay in the shortcut button list. The problem is that few people need to change the system to reverse the tone frequently. In most cases, as long as you press the new setting option after upgrading the system, this option can no longer be deleted from the shortcut button list. Google is trying to kill obsessive-compulsive disorder!

This problem is not a Bug, but a design problem of Google. I hope Google will correct it soon.

Android 5.0 is suspected to be flawed: idle memory also frequently kills the background.

Android 5.0 replaces Dalvik with Art. According to Google's official statement, this will greatly improve the efficiency of the system. But in actual use, many users report that Android 5.0 is not as fast and smooth as Android 4.4. The reason is that Android 5.0 will restart the App frequently, which will greatly reduce the multitasking experience and make the system run slowly-even if the system still has a lot of free memory.

According to users, Android 5.0 will frequently kill background programs. The background program is reloaded to the foreground and needs to be reloaded, which will lose the workflow and consume more time and traffic. Generally speaking, if the Android application does not choose to quit when the user leaves, it will stay in the background, and users do not need to reload it when they reopen the application, thus realizing background multitasking. However, in Android 5.0, even if there are continuous notifications (such as music players), an application will often be closed in the background after a long time without being closed or restarted. So there is no way to multitask backstage.

This problem is more serious in 2G RAM models such as Nexus 4, Nexus 5 and Nexus 9, and Nexus 6 is much better. I also encountered this problem when I upgraded my Nexus 5 to Android 5.0. At present, it is not known whether this problem is a Bug such as memory leak, or whether Android 5.0 really improves the hardware requirements. I hope that the subsequent upgrade can improve this problem.

Summary: Overall, there are still many problems with Android 5.0. Android 5.0 is a big version update, which spans such a big update, has a large workload and is often prone to problems. Even if the quality of iOS is better than that of Android, there are many bugs when updating iOS8. Apple had to quickly release iOS8. 1 to fix the defect. According to foreign media reports, Google is currently testing the version of Android 5.0 MR 1, namely Android 5. 1. Not surprisingly, it will be a version used to fix many problems in Android 5.0. Google released the developer preview version of Android L early, which made the test period of Android 5.0 as long as half a year, but problems still emerged one after another. I hope Google can finish the repair work as soon as possible.