Hello to all D331 owners!
For the last couple of weeks, I've been testing the official Lollipop ROM, released for the CIS region (D33120c_00). Similar ROM was also released for TelCel (Mexico) and Avea (Turkey). My phone originally came with D33110f_00 unbranded KitKat ROM (V10f_EUR_XX). The Lollipop ROM was flashed using LG Flash Tool 2014, after which a factory reset was performed.
Here are the bugs I've found so far, and it seems we're dealing here with an unpolished, test ROM. Values in brackets (High, Medium, Low) represent the severity of the problem:
1. [High]: Magnetic field sensor lag. The sensor's polling rate won't go above 15 Hz, which causes reduced framerate in most of the compass apps. Since polling rate in KitKat was well above 50 Hz, this could indicate a major optimization flaw, rendering apps which require precise magnetic sensing useless.
2. [Medium]: Sensors report themselves incorrectly. In various diagnostic apps, sensors report themselves as "MTK [sensor name]". In KitKat, they were correctly reported as "LGE [sensor name]".
3. [Medium]: Apps take way more storage. Actually not a bug, since ART runtime in Lollipop works that way. Nevertheless, it's a good reminder since Smart Cleaning reports 30% storage in use on the first Lollipop boot (it was nearly half that much in KitKat).
4. [Medium]: Play Store lag. This problem is present in KitKat too, but in Lollipop it feels a bit worse. When you scroll up or down the list of paid / free apps (after you select a category), scrolling framerate drops on random spots throughout the list. In landscape orientation, the framerate drops even more.
5. [Low]: Blurry recent apps previews. In the new recent apps list, previews of currently opened apps are a bit blurry. They were perfectly sharp in KitKat. On a rare occasion, some previews would exhibit black horizontal lines.
6. [Low]: Non-standard font in Wi-Fi password field. When a popup window to enter your Wi-Fi credentials appears, the password entry field doesn't feature the standard Roboto font. It features some sort of fixed-length font (similar to Lucida Console on Windows). Bug not present in KitKat.
7. [Low]: Stock Jelly Bean wallpaper on first boot. When you flash the Lollipop ROM, you'll be presented with one of the stock Android wallpapers (which dates back to Jelly Bean). Once you select another wallpaper, you cannot select this one again, as it can't be found in the stock LG wallpaper gallery. In KitKat, you are presented with the default LG wallpaper.
8. [Low]: Phone app recent list leftover. After you finish a call or dial an USSD code, they will suddenly appear in the recent apps list - but not before all other recent apps are swiped away. If you use the "Clear all" button, they won't appear. The correct behavior would be to list them among all other recent apps immediately, not only after all other apps were swept away.
(Note: This list is not finalized, there could be more bugs that are yet to be found.)
To conclude this report, I have a question - is it possible to report these kind of bugs directly to LG technical teams, is there any official procedure? I mean, they have to get aware of bugs somehow - or do they find and correct them on their own, without any kind of user reports?
For the last couple of weeks, I've been testing the official Lollipop ROM, released for the CIS region (D33120c_00). Similar ROM was also released for TelCel (Mexico) and Avea (Turkey). My phone originally came with D33110f_00 unbranded KitKat ROM (V10f_EUR_XX). The Lollipop ROM was flashed using LG Flash Tool 2014, after which a factory reset was performed.
Here are the bugs I've found so far, and it seems we're dealing here with an unpolished, test ROM. Values in brackets (High, Medium, Low) represent the severity of the problem:
1. [High]: Magnetic field sensor lag. The sensor's polling rate won't go above 15 Hz, which causes reduced framerate in most of the compass apps. Since polling rate in KitKat was well above 50 Hz, this could indicate a major optimization flaw, rendering apps which require precise magnetic sensing useless.
2. [Medium]: Sensors report themselves incorrectly. In various diagnostic apps, sensors report themselves as "MTK [sensor name]". In KitKat, they were correctly reported as "LGE [sensor name]".
3. [Medium]: Apps take way more storage. Actually not a bug, since ART runtime in Lollipop works that way. Nevertheless, it's a good reminder since Smart Cleaning reports 30% storage in use on the first Lollipop boot (it was nearly half that much in KitKat).
4. [Medium]: Play Store lag. This problem is present in KitKat too, but in Lollipop it feels a bit worse. When you scroll up or down the list of paid / free apps (after you select a category), scrolling framerate drops on random spots throughout the list. In landscape orientation, the framerate drops even more.
5. [Low]: Blurry recent apps previews. In the new recent apps list, previews of currently opened apps are a bit blurry. They were perfectly sharp in KitKat. On a rare occasion, some previews would exhibit black horizontal lines.
6. [Low]: Non-standard font in Wi-Fi password field. When a popup window to enter your Wi-Fi credentials appears, the password entry field doesn't feature the standard Roboto font. It features some sort of fixed-length font (similar to Lucida Console on Windows). Bug not present in KitKat.
7. [Low]: Stock Jelly Bean wallpaper on first boot. When you flash the Lollipop ROM, you'll be presented with one of the stock Android wallpapers (which dates back to Jelly Bean). Once you select another wallpaper, you cannot select this one again, as it can't be found in the stock LG wallpaper gallery. In KitKat, you are presented with the default LG wallpaper.
8. [Low]: Phone app recent list leftover. After you finish a call or dial an USSD code, they will suddenly appear in the recent apps list - but not before all other recent apps are swiped away. If you use the "Clear all" button, they won't appear. The correct behavior would be to list them among all other recent apps immediately, not only after all other apps were swept away.
(Note: This list is not finalized, there could be more bugs that are yet to be found.)
To conclude this report, I have a question - is it possible to report these kind of bugs directly to LG technical teams, is there any official procedure? I mean, they have to get aware of bugs somehow - or do they find and correct them on their own, without any kind of user reports?
No comments:
Post a Comment