Android 4.2 Plagues by Major Bugs and Issues


Recommended Posts

While Jelly Bean (4.1) was very well received and perceived as one of the best update to Android, 4.2 is not getting the same treatment. Report tell that "some aren't that bad, but some can just ruin your day."

Source: http://www.androidpolice.com/2012/11/19/android-4-2-gate-here-are-some-of-the-major-issues-plaguing-googles-newest-release/

I have Nexus 7 running 4.2 (note original Nexus 7 that shipped with 4.1 upgraded to 4.1 update, then 4.2)

Not experiencing battery / extreme drain.

Not had random reboots or instability.

No flickering w/ auto brightness and typically used in darker rooms.

Not used bluetooth, so can't evaluate that one.

Not used camera much or widgets on the lock screen, can't evaluate that.

Confirmed Dec is missing on personal contact information event dates (bday, anniversary, etc).

I updated my galaxy nexus to android 4.2, complete fresh load.

I removed it yesterday and went back to 4.1 I experienced the random reboots, the instability, battery drain and slow charging and odd behaviour on the lockscreen. I also noticed my phone got extremely hot after a full charge :(

When 4.1 was first released I upgraded straight away and never looked back, 4.2 however just isn't quite right yet :(

Running 4.2 on my nexus 7 fine here, only had 8gb space instead of 16gb after flashing stock images but that was easily fixed ^^

I updated my galaxy nexus to android 4.2, complete fresh load.

I removed it yesterday and went back to 4.1 I experienced the random reboots, the instability, battery drain and slow charging and odd behaviour on the lockscreen. I also noticed my phone got extremely hot after a full charge :(

When 4.1 was first released I upgraded straight away and never looked back, 4.2 however just isn't quite right yet :(

You're just holding your phone wrong :p

You're just holding your phone wrong :p

I knew it :p damn!!!!

My battery life has gotten worse over the past couple of days but I think that's because I'm using the Cloud Player when I'm out and about.

My battery died quite quickly without using the cloud player, but using the cloud player.....well, that just destroyed the battery :p

I have a Galaxy Nexus (Verizon) and Nexus 7 both running Jelly Bean 4.2

I will say on the Nexus 7 (stock, unrooted), I took the OTA, and I have experienced the December bug, and the poor battery life. Other than that, it's rock solid, no slowdowns, no reboots, lockscreen (widgets) work fine.

On the Galaxy Nexus, it's rooted, and running a custom ROM, but I haven't experienced anything but the December bug.

I'm sure Google will come up with a fix. It's not like we haven't heard of such issues happening after an OS upgrade (with a different mobile OS).

Running 4.2 on a Galaxy Nexus & Nexus 7 - the Nexus 7 I ran the OTA, on the GNex I did a full system image. Both are running fine and I have not experienced any bugs (other than the December bug, but that is easily remedied by updating your contacts online).

I haven't noticed any of those bugs on the Nexus 7, but then again I'm not using that People/Contacts app there, nor have I used bluetooth so far.

I'm not too fond of the lock screen widgets and the new separate notifications and settings drop downs, but other than that it seems to be running as fine as 4.1.

This topic is now closed to further replies.
  • Posts

    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
    • Windows 11 KB5094126 BSODing, freezing, forcing BitLocker lockout, breaks OneDrive, and more by Sayan Sen Microsoft released Windows 11 KB5094126 and KB5093998 last week as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. While Microsoft has so far not acknowledged any major problems with the release, some users online are running into problems. These range from OneDrive and Dropbox access issues, BitLocker recovery lockouts, to blue screens and BSODs. The most common one seems to be happening with HP systems wherein affected users say they hit 0xc0430001 BSOD (blue screen of death) error code after the KB5094126 update. We wonder if this could be related to the recent bug we covered on HP devices wherein the ongoing Secure Boot certificate updates are leading to similar issues. While we are not certain, users affected by this issue likely need to ensure that the boot.stl file is included on the installation media (such as a USB installer or ISO), if the above-mentioned dynamic updates are deployed. If this file is missing, computers may fail to boot from the installation media and could display the error 0xc0430001. This STL file is used by Secure Boot to verify that the boot files are trusted, so it must match the same Windows version and system architecture. To ensure the file is included, Microsoft recommends using the Update WinPE script, which automatically updates the image and handles the required files. Alternatively, you can manually copy the boot.stl file from the Windows\Boot\EFI folder on a Windows device and place it in the matching folder on your installation media before deploying the updated image. Aside from blue screening some users also note their systems have been freezing following the update. This could be happening to Lenovo PCs specifically. In the case of the OneDrive and Dropbox access issues, a user figured out that there could be a conflict with UAC. He explained: "Okay, so I did some digging, and in our environment KB5094126 breaks OneDrive and Dropbox in Explorer. I went through all our GPOs and found out that the combination of disabling UAC and having my user being a local admin breaks OneDrive in Explorer. ... If I enable UAC again, then it works, even with KB5094126 still installed." Hopefully, Microsoft will look into these issues. Source: Microsoft forum (link1, link2, link3, link4), Reddit (link1, link2, link3, link4)
    • It is when it's a desktop in my house though for a PC that's lightly used and not really important when it is. If it was a laptop, it would be a different story. The real solution is varied and begins starting at post #22 in that thread.
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!