Android Police

Articles Tagged:

google code


Google officially moves the AOSP issue tracker away from Google Code

The issue tracker for the Android Open Source Project, more commonly known as AOSP, has always used Google Code. However, Code was completely shut down in 2016 (with most projects being forced to read-only in 2015), but the AOSP repository remained active.

Now the AOSP issue tracker has moved over to, which first appeared publicly to collect bug reports from the Android O Developer Preview.

Read More

Google is moving to a new issue tracker

When it comes to Android issue tracking, Google has always used Google Code. However, Google started phasing out Code for most users in 2013, and Google's projects are the only active repositories left. Now the company has started to shift to a new issue tracker, hosted at

Read More

No, Google Won't Enable Ticker Text If You Disable Heads Up Notifications (Peeking) In The Android M Developer Preview

Heads up or "peeking" notifications, the little miniature pop-ups that appear in Android Lollipop if a notification comes in when you happen to be actually using your device, aren't for everyone. That's why Google will include the option to disable them on a per-app basis in the upcoming Android M release. (See Settings>Sound & Notification>App notifications in the Developer Preview.) It's also why apps like HeadsOff have sprung up to cater to those who want them to go away even sooner.


Unfortunately, it looks like Google isn't all that interested in bringing back the pre-Lollipop equivalent, Ticker Text. Ticker Text is that scrolling text you see across the notation bar when a new alert pops up while you're using your phone, but it's gone as of Android 5.0.

Read More

Chrome For Android Will Have Immersive Fullscreen For Non-Video Elements Soon, Probably In Version 43

Do you want to use Chrome in fullscreen immersive mode, without add-on apps or root modifications? According to entries in the Chromium project on Google Code it's coming soon, possibly in the next beta release. But don't get too excited just yet.This behavior is specifically for website elements, not the browser itself (which was possible in some versions of the old AOSP browser). It will enable certain sites or web apps to go fullscreen with Android's immersive mode, just like HTML videos do now.

fullscreen_permission click_fullscreen_permission

The upcoming fullscreen permission management system.

On this page you can follow along with a conversation between Google employees and other participants in the open-source project, detailing the need for and implementation of non-video fullscreen elements like browser-based games and apps.

Read More

Google Code Will Shut Down In January 2016 Because Almost No One Uses It Anymore

Google has announced the end of another service, and this one is a shocker—Google Code is going away on January 25th, 2016. That gives you about ten months to get your code off of Google's servers before it's gone forever. Why is Google breaking your heart like this? According to the company, Google Code simply isn't very popular anymore.

google code

Read More

Google Swats A Bunch More Bugs In Android L, Including An Issue Interfering With Tethering, Due Out In 'The Next Public Release'

Google is making the best of allowing enthusiasts and 3rd-party developers early access to the next release of Android, and the result will be a less buggy release when L finally hits the grand stage. While new issues are reported each day, there's a lot of progress showing up on the Issue Tracker. Just yesterday, a burst of 18 bugs were marked as 'fixed,' following a 2-week gap without any obvious activity.


Among the many fixes, both major and mundane, we can see a lot of attention has gone to the networking and wireless protocols, sensor-related problems, and a fair number of visual tweaks.

Read More

Multiple Google Employees Are Using Android L On The Nexus 4

Nexus 4 owners, don't lose hope. Though your 2012 Google phone was cruelly looked over for the developer preview builds of Android L (along with everything that wasn't a Nexus 7 2013 or Nexus 5), sharp-eyed Google+ users have spotted two different Google employees posting on the Chromium section of claiming to use the Nexus 4 with Android L. Check out this entry from a contributor with a email address, explicitly using the "LRW52G" build of Android on his or her N4. The latest N5 build of Android L is LRW66E.

google employee

That gives us some real hope that Android L will be making it to the current penultimate Nexus, along with the initial partial support from the AOSP code released in July.

Read More

14 Bugs Closed In Android L Preview, Including The AT&T/T-Mobile MMS Error, To Be Patched In 'The Next Public Release'

It's been over two months since Google gave Nexus 5 and Nexus 7 owners a chance to tinker with the upcoming L release of Android, in what has been the biggest beta test in Android's short history. With all of us waiting on a release sometime in the fourth quarter of 2014, it's gratifying to know that the powers that be are hard at work getting Android L ready for primetime. If the latest updates to the public issue tracker are accurate, some of the biggest and most critical bugs in Android L have been patched.

The most dramatic of these is the Nexus devices' inability to send or receive MMS messages through the default Hangouts app.

Read More

Nexus S 4G Factory Image (4.0.4) Now Available Straight From Google, In Case You're Feeling ROM Remorse

Thanks again to the venerable JBQ of Google, the unmodified factory image of Android 4.0.4 for the Nexus S 4G (sojus, Android 4.0.4 IMM76D) is now available here. As JBQ states on Google+, this image is for those among you who have flashed to custom versions of AOSP and want to get back to factory state. No, by the way, there's still no word on an OTA update yet.

2012-04-10 01h22_20


As with all the others, the factory images are available on the Factory Images for Nexus Devices page.

More Info

To get started, head to JBQ's Google+ post on the subject, where he has more info on a known bug where the device reports an incorrect radio version number.

Read More