New Nexus/Android 4.2 Anticipation Thread--October 29th

Rohiggidy

The Big League
Joined
Jun 8, 2012
Messages
6,576
Reputation
70
Daps
2,431
Reppin
New York
How To Unlock the Nexus 4 Bootloader

You'll need to have a few tools at the ready, but they are all freely available and easy to use if you're the least bit technically inclined.

You'll need the fastboot binary for your computer operating system. Windows, Mac, and Linux are all supported. The fastboot binary is a small program that communicates between your computer, and your phone when it is booted into fastboot mode. Visit the sticky posts in the Galaxy Nexus hacking forums if you need help setting this up.
If you're using Windows, you'll need a properly setup fastboot driver. These drivers will be made available through the Android SDK when it's updated. This means someone will suck it out of there and make it available for download shortly after. If you're using a Mac or Linux, you won't need any drivers.
You'll need the cable that came with your Nexus 4.
You'll need to be able to enter commands into a terminal or command line.
Power off your Nexus 4, and reboot it into fastboot mode by holding the volume down button and power. You'll see the familiar green robot, and the word "Start" at the top of the screen.

Plug your phone into a full speed primary USB port on your computer. If you're using Windows, you'll see the pop-up about drivers being installed and initialized.

Open the terminal or command prompt on your computer, and navigate to the folder you have placed the fastboot program in. Advanced users can simply place the fastboot program somewhere in their PATH.

At the command line, type in (without any quotes) "fastboot devices". You should get a device ID returned, which lets you know that fastboot can see your Nexus 4. If you don't see a device ID, stop and investigate. If you're using Windows, chances are you don't have your fastboot driver set up properly. Linux users may have to run fastboot with elevated permissions depending on your system. This is where many folks get stuck, and it's important to realize that you can;t go any further until you see that device ID. Visit the forums, find the help you need -- chances are it's something very simple.

Once you're sure fastboot is set up properly and can communicate with your Nexus 4, type the following command to begin the process (without any quotes) "fastboot oem unlock". Look to your phone, where you'll have to verify the process. Remember that there's no way to undo the data loss that will happen the instant you say Yes.

When the phone reboots, you're done. You're free to install custom software, modified boot images, custom recovery, you name it. The phone is now yours.

Relocking the bootloader is just as easy, should you ever decide to do so, Follow the same instructions, except the last step should be "fastboot oem lock". This will relock your bootloader so that only authentic, signed images from Google can be flashed to the phone.
 

Rohiggidy

The Big League
Joined
Jun 8, 2012
Messages
6,576
Reputation
70
Daps
2,431
Reppin
New York
PHOTOSPHERE OF NYC AFTER SANDY

https://plus.google.com/photos/105046045700292924505/albums/5805569422944253569/5805569421458305522

2012%2B-%2B1



GOOGLE HQ
12%2B-%2B1


https://plus.google.com/+PhilNickinson/posts

soccer field
https://plus.google.com/+PhilNickinson/posts

PANO_20121103_110833.jpg
 

Rohiggidy

The Big League
Joined
Jun 8, 2012
Messages
6,576
Reputation
70
Daps
2,431
Reppin
New York
Inside Android 4.2: Notifications and quick settings

[ame=http://youtu.be/ntq__St2Btk]The new notifications and settings in Android 4.2 - YouTube[/ame]

Your Google+ profile: If you're signed in to Google+, your name and profile picture will appear. Tap it, and you're asked if you want to view your Google+ profile. (Not sure why I'd ever want to get to my G+ profile that quickly, but chances are Google will tweak that at some point.)
Brightness: Tap this, and you get a little popup that lets you adjust the display brightness. This is different (and better) than the full-screen brightness notification. I use this a lot already.
Settings: Ah, there it is. A shortcut to the full settings menu.
Wifi: Shows the network you're own. Tap, and it takes you to the Wifi settings.
Mobile data: Shows which carrier you're on, and signal strength (in bars).
Battery: There's a visual indicator and percentage remaining. (Numbers FTW!) Tap and you get the battery section in the settings menu.
Airplane mode: Shuts off the radios for when you're on an airplane. (Or if you want to pretend you're on an airplane.)
Bluetooth: Takes you to the Bluetooth settings menu. (The quick setting will show on if on, off if off.)

Quick settings and tablets
tablets-pulldown.png
 

Rohiggidy

The Big League
Joined
Jun 8, 2012
Messages
6,576
Reputation
70
Daps
2,431
Reppin
New York
Android 4.2 brings new security features to scan sideloaded apps

verify-apps.jpg


Talking about malware on a mobile platform is a tough thing to do right. Some of what you hear is real, and needs addressed responsibly, but so much of it is just FUD from folks trying to sell you something or get you to change your choice of device. We try to do the former, without downplaying the serious issues, but we also depend on users to be a little bit savvy and not do the things that lead to getting malware on the phone in the first place.

Thankfully, Google has stepped up and taken the reigns here. As ComputerWorld's JR Rapheal has pointed out, starting with Android 4.2 users now have the option to have every application that is being sideloaded scanned before installation. This uses the same technology as Google Play's Bouncer, and is designed to scan for and find malware -- both known cases and suspicious applications. If an app's fingerprint matches known malware, you'll be blocked from installing the application. If the app shows anything that the canner feels is suspicious, you're warned that it may be harmful and given the choice whether or not to install. The service is entirely opt-in, and your choice can be changed at any time through the device security settings.

We're big proponents of responsible reactions to and prevention of mobile security issues. In a time where companies release blurbs in the press that exaggerate the amount of malware (Android VP of engineering Hiroshi Lockheimer notes that actual dangerous malware is extremely rare on the Android platform) and push users to use their products, we're glad to see Google taking this sort of action. There is no substitute for common sense, but Android 4.2's new security scanning feature sounds like the right way forward.

nexusae0_wm_Screenshot_2012-11-01-21-48-14_thumb.png

nexusae0_wm_2012-11-01-21.45.40_thumb.png
 

Rohiggidy

The Big League
Joined
Jun 8, 2012
Messages
6,576
Reputation
70
Daps
2,431
Reppin
New York
nexusae0_Top_100_Android_Apps_Google_Play_Music_thumb.png
Google's New "Explore Similar Artists" Feature Already Live In Play Store For Tablets

nexusae0_wm_Screenshot_2012-11-01-01-30-05_thumb2.png
 

Rohiggidy

The Big League
Joined
Jun 8, 2012
Messages
6,576
Reputation
70
Daps
2,431
Reppin
New York
Here Is Another Reason Google Continues To Shun SD Cards - Multiuser Support


The lack of expandable storage in Nexus devices becomes one of the hottest and most controversial topics every time Google does a refresh and we find out that the next generation lacks SD cards entirely yet again. Couple that with the decision to limit onboard storage options to 16GB max, which is the case with the Nexus 4 at the moment and was the case with the Nexus 7 for a while, and you've got a full-blown revolt.
You may have read one explanation of Google's aversion to SD cards, which was brought up by Android engineer Dan Morrill last year: it's confusing to users to have multiple storage points, the insecure "free-for-all" area was not meant for private app data but rather for media, and essentially SD cards are the sources of all evil. Google's chief of Android user experience Matias Duarte reiterated the same points today. Whether you think the reasons are legitimate or bogus (in consumers' eyes), this is Google's stance on the matter.
Now, with Android 4.2, there's yet another reason, one I hadn't thought of before, but one that makes sense - multiuser support. It's already relevant for the Nexus 10. At the moment, the Nexus 4 still lacks multiuser capabilities - some say due to a possible patent issue - but when Google (or enterprising hackers in the first few hours of 4.2 release) is ready to turn them on, it will become relevant.
There are two separate parts here, actually:
The lack of proper filesystem permissions. Because SD cards are generally formatted using the FAT file system due to high compatibility with multiple operating systems, they lack the concept of file ownership entirely. If Google wants to be taken seriously when it comes to security, there should be no weak links like that. Imagine a modern PC where an unprivileged user could access every file in the file system - sounds pretty crazy when you think of it that way.
Adding the complexity of multiple users to something as portable as an SD card would undoubtedly create an array of problems. What happens when two users are using the same app that stores some of its data on the SD card? What happens when you move your SD card to another device with a different multiuser configuration (or lack of the concept of users entirely)?
Up until now Android didn't have a concept of multiple users. Think back to Windows 98 that had a single My Documents directory and proper multiuser support only arriving with Windows 2000 and its Documents and Settings folder. I could draw so many parallels here.
The key point remains that unlike the migration path between Windows 98 to 2000 and having an internal hard drive vs an easily removable SD card, there is a certain expectation Android users have - seamless OTA updates and backwards compatibility. The /sdcard partition and paths on it have been mistreated so much in the past few years (just look at your card and see how many apps don't store data according to guidelines). If Google were to resolve the path issue and repartition the card upon upgrade to something like /sdcard/user1, /sdcard/user2, etc, it would suddenly become incompatible with other devices. Plus there's still no proper permission support.
It's kind of a mess.
And I don't even want to think of the ways other manufacturers are going to try to handle multiuser support. Google chose a simple path for its own devices. Now what happens when an OEM decides it wants to stick in an SD card slot and enable multiple users? Ugly hacks come to mind, and if there's one thing I hate as a programmer, it's ugly hacks.
Here is my take on the whole situation:
Google needs to start offering more storage options. Not everyone is a power user, but we do exist, and we want our space. I, for one, am out of space with 64GB. I don't want to be. I will pay more to have more storage, but I can't. A few large games and apps, some music, a bunch of nandroid backups, some videos - hey, look, I'm already out.
Google needs to solve the SD card situation properly so that both Nexus and non-Nexus devices can easily utilize them. Dan Morrill said Google would like to do it right, but I'm not sure they want to badly enough. SD storage is cheap. I want to use it. I want to have an option to use it. I want to have an option to pop up an SD card and move it elsewhere, whether just migrating devices or trying to rescue files off a phone that no longer powers on after taking a dive into my dog's water bowl.
In conclusion, let me quote chief Android framework engineer, walking Android encyclopedia, and fearless feline leader Dianne Hackborn who dropped some wisdom yesterday on G+ and put these thoughts in my head in the first place:

Robert Mahon: Another thought about this sd-card stuff, might it have caused issues with the multi-user side of things in 4.2? Most apps aren't following guidelines on where to save their data, so it gets sprayed willynilly on the SD-Card. Now there's more than one person using the system, and possibly overwriting that data/corruption, I can see why Nexus devices, to stop this being a problem before it starts (or at least reducing it to less apps) is not using the sd-cards.
Stewart Gateley: With each user having their own apps and data, SD card makes even more sense. Keep the profiles local while storing large media files on ext storage. Either external files can be shared with all users, or set file permissions. No need to partition space out for each user or something. For a multi-user HD media consumption device, the Nexus 10 is seriously lacking storage. But I thought we were talking about the 4 here.
Dianne Hackborn:

+Robert Mahon This is certainly an issue, we aren't supporting multi-user with the old school FAT partition for external storage (whether that is on an SD card like the original G1 or a separate internal partition like the Nexus S).

+Stewart Gateley SD cards must be formatted with FAT (to inter-operate with desktop computers), which doesn't support file permissions. Not to mention that all you are going to end up with is a mess if you try to set file system permissions (based on uids) on an SD card and then move that to another device.
 

Rohiggidy

The Big League
Joined
Jun 8, 2012
Messages
6,576
Reputation
70
Daps
2,431
Reppin
New York
Google Now has a Built-in Pedometer – Tracks Miles Walked and Biked From Each Month
google-now-pedometer-650x384.jpg
 

Rohiggidy

The Big League
Joined
Jun 8, 2012
Messages
6,576
Reputation
70
Daps
2,431
Reppin
New York
Android 4.2 Camera APK Hands On


[ame]http://youtu.be/pMDxBmxKkdQ[/ame]

[ame]http://youtu.be/YvYTUKgyLHU[/ame]
 

Rohiggidy

The Big League
Joined
Jun 8, 2012
Messages
6,576
Reputation
70
Daps
2,431
Reppin
New York
APK Teardown] Google Maps Is Getting Real-Time Traffic Rerouting, And Google Voice Search Learns How To Hold A Conversation
Posted by Ron Amadeo in APK Teardown, News

Google Maps


Maps is getting real-time traffic rerouting!
Now, you might be saying "But Maps already takes traffic into account, look at this blog post!" but let's take a look at what that blog post really says:
You don’t have to do anything to be routed around traffic; just start Navigation like you normally would, either from the Navigation app or from within Google Maps. Before today, Navigation would choose whichever route was fastest, without taking current traffic conditions into account. It would also generate additional alternate directions, such as the shortest route or one that uses highways instead of side roads. Starting today, our routing algorithms will also apply our knowledge of current and historical traffic to select the fastest route from those alternates. That means that Navigation will automatically guide you along the best route given the current traffic conditions.
Traffic is currently calculated when you hit the 'navigate' button, and then traffic calculation is over. Say you're taking a two hour road trip, and, 5 minutes into your trip, an accident happens in the tunnel you were supposed to take. Today, Maps will still tell you to take the tunnel, because it only takes traffic into consideration during the initial route calculation.
It sounds like this is going to change. There are now several references in Maps to a "route_around_traffic" message, which sounds like it will popup while you are navigating, and say "Hey this route isn't good anymore, do you want to change?" Here's the text for it:
<string name="da_reroute">Reroute</string>
<string name="da_reroute_to_avoid_traffic">Reroute to avoid traffic?</string>
<string name="da_reroute_time_savings" formatted="false">Save %s via %s</string>
<string name="da_speech_reroute_to_avoid_traffic" formatted="false">Traffic ahead. Reroute to save %s via %s</string>
The "save %s via %s" stuff will probably be in the form of "Save 20 minutes via Route 66."
In order for this message to be necessary, Maps would have to be periodically checking traffic conditions and recalculating new routes while you drive. When it finds a better route, it will prompt you with these messages. This would be really helpful for a long trip, and it's something that shouldn't be too hard to implement.
I can't show you the actual UI, but I can show you the components of the UI:
<public type="id" name="da_routeAroundTrafficButtonPanel" id="0x7f10012c" />
<public type="id" name="da_routeAroundTrafficCancelButton" id="0x7f10012d" />
<public type="id" name="da_routeAroundTrafficConfirmButton" id="0x7f10012e" />
<public type="id" name="da_routeAroundTrafficPromptPanel" id="0x7f10012f" />
<public type="id" name="da_rerouteTimeSavedMessage" id="0x7f100130" />
<public type="id" name="da_reroutePromptMessage" id="0x7f100131" />
<public type="id" name="da_rerouteInlineButtonPanel" id="0x7f100132" />
So, just picture a popup box that says "Reroute to avoid traffic?" with the time you'll save placed somewhere, and "Confirm" and "Cancel" buttons. Actually, a popup box might be too intrusive while you're navigating - it will probably be a notification.

Google Search
Google Search will be learning a few new tricks as well, the most exciting of which is probably the last thing that gives me Siri/S-Voice envy: how to hold a conversation. If tell S-Voice to "Send text to Bob," it will say "Ok, sending text to Bob, what would you like it to say?" and then you can verbally dictate a message. These 2 or sometimes 3 step voice interactions are much more natural and easier than the perfectly-executed "verbal command line" that Voice Search requires.
Check this out:
<string name="voice_disambiguation_confirmation">Calling %1$s.</string>
<string name="voice_contact_call_confirmation_prefix">Do you want to call %1$s at %2$s? Say okay, cancel, or try speaking again.</string>
<string name="voice_number_call_confirmation_prefix">Do you want to call %s? Say okay, cancel, or try speaking again.</string>
It's a baby step, but an important baby step. Search will soon ask you for confirmation for "call [contact]" commands. I'm honestly not sure if this works right now or not. I've done a million "call [contact]" tests, and I've never seen it pop up, but maybe I'm not confusing Search in just the right way to trigger this. Has anyone seen this?
The other new Search tidbit is NFC support, which many people spotted in the permissions while updating. A teardown reveals absolutely nothing, which means it's probably not being used for anything right now. The thing is, I can't even imagine a hypothetical use for it. Please speculate in the comments.
 
Top