Status Update
No update yet.
Comments
jn...@gmail.com
Which device? All devices supported in AOSP run either 4.1 or 4.3 at this point.
ta...@gmail.com
Device Samsung Galaxy with android 4.0.4
ne...@gmail.com
This report applies to an Android-based device, and the issue tracker where you reported it specializes in issues within the Open Source source code of the Android platform.
We are not able to provide support for individual devices. Please report this issue in the support forum for your device, which might be hosted by your device manufacturer or by the operator where you got your device.
We are not able to provide support for individual devices. Please report this issue in the support forum for your device, which might be hosted by your device manufacturer or by the operator where you got your device.
ne...@gmail.com
Damn fuckers you googlers,
howcome it has not been fixed yet until today? huh?
Even very latest model still have same problem. LG G2. 4.4.2.
since this kind of HUGE problem has not been notified to the manufacture.
Mean that you google NEVER think about the impact to the market income of each publishers. This is not only one or two person's problem but the Google company problem
which is lazy and just burning the Google company's money(payroll).
Really shame. thins kind of malpractice, carelessness, amateurism is not only few times of problem, but big problem in the Google which still going on.
Shame.
Fix RIGHT NOW, not tomorrow.
howcome it has not been fixed yet until today? huh?
Even very latest model still have same problem. LG G2. 4.4.2.
since this kind of HUGE problem has not been notified to the manufacture.
Mean that you google NEVER think about the impact to the market income of each publishers. This is not only one or two person's problem but the Google company problem
which is lazy and just burning the Google company's money(payroll).
Really shame. thins kind of malpractice, carelessness, amateurism is not only few times of problem, but big problem in the Google which still going on.
Shame.
Fix RIGHT NOW, not tomorrow.
Description
When you load many switch preferences in a preference fragment, they somehow re-set themselves, when you scroll the preferences.
Procedure:
Load a lot of SwitchPreference in a PreferenceFragment, from an XML. If you change the first switch preference , scroll down, scroll back up, the switch is reset. Same is true for other switch preferences which scroll out of view and are visited later.
Platforms affected:
Issue was observed when compiling with API 15. Problem observed both in emulator and a real device.
More discussion and confirmation of issue by others can be found at: