If you bought a new Nexus 7 tablet and you aren’t having any issues with it, consider yourself lucky. First we caught wind of GPS issues plaguing early units, and now owners are reporting touch screen problems with some tablets. Unfortunately for touch screen issues, it’s not always something as simple as software like the GPS bug.
Supposedly, some tablets are experiencing unintended double taps, ghost taps, and erratic behavior on the screen, which is never something you want to see on your brand new tablet. Google has suggested users boot into safe mode to try to determine if any third-party app is causing the problems, but if that doesn’t cure it, your best bet is to contact Google directly. Returning the tablet to wherever you bought it is also an option (assuming you didn’t buy it from the Play Store) but you may end up with another tab with the same issues.
Any readers out there having Nexus 7 touch screen problems?
source: Google Product Forums
via: Phone Arena
Since officially releasing the Nexus 7 (2013), Google’s latest device has been receiving positive reviews in general. However, some issues have come up, like some GPS problems that Google is aware of and is working on a solution. Another problem that surfaced that has the potential to impact Android fans beyond those who own the new Nexus 7 have been issues revolving around the release of Qualcomm binaries for the device. The issue was so contentious, that Jean Baptiste-Queru went so far as to submit his resignation and walk away from the AOSP project due to the difficulties in getting factory images released. Apparently the bad press related to that was more than Google could fathom as they have now released the factory image and binaries, including the Qualcomm files in question.
ASUS gave a presentation in France earlier today to discuss their roadmap for tablet and smartphone devices, including intentions to get into the U.S. market with their smartphone devices. Two slides from the presentation show the breakdown of devices in each class. Common to both smartphones and tablet devices is the MeMO line, with the MeMOFone HD 5 apparently headed to the U.S. market. Other smartphone devices include the PadFone Infinity, PadFone mini, FonePad HD 7 and FonePad Note FHD 6. The last item in that list appears to imply ASUS will be producing a stylus equipped device to compete in that market.
We don’t need to speculate anymore as to when the new Nexus 7 will be released in the UK. It’s officially going to be August 28. The makers of the tablet, ASUS, had a press event in London and showed the above slide. It will be priced at £199 for the 16GB version and £239 for the 32GB version. If you’re really anxious, some stores will be open at midnight for the launch.
As you can also see, the slide shows us September 1st and September 6th release dates for the MeMo Pad HD 7 and the MeMO Pad FHD 10 respectively. The HD 7 will run £129 and the FHD 10 will set you back £299.
If you just picked up the new Nexus 7 and having problems with the GPS, you’re not alone. Many users are saying that it will get a satellite lock and work great, but at some point it will go back into a “searching” mode with the GPS icon blinking. The length of time that it’s locked in seems to be different for everyone. We have seen as low as 2 minutes and as high as 30 minutes. Rebooting can help, but not guaranteed.
The good news is that Google is aware of the issue and a fix is coming soon. Don’t ask me when because we don’t have a timetable just yet, but it shouldn’t be too long since Google is the one working on the fix.
Are any of you noticing the problem? I haven’t even attempted navigation with mine.
By now I’m sure most of the Android community has heard about the difficulties Google is facing getting factory images available for their new Nexus 7 tablet and head of AOSP Jean-Baptiste Queru leaving the project altogether. Because Qualcomm refuses to allow Google to publish a factory image for the tablet because of proprietary binary code in it that Qualcomm doesn’t want the public to have.
In an attempt to remedy the situation, a Change.org petition has been started asking Qualcomm to let Google release those much desired factory images for their newest flagship tablet. Right now, it only has a few hundred signatures, and if it’s going to get any attention from a big company like Qualcomm, it’s going to need quite a few. Hit the link below to read it and put your name in the list.
As excited as we are about the ushering of the new Nexus 7 tablet, there have been some quiet— but major technical snafus for the Android hardcore which has resulted in one of the most important pieces of the AOSP disappearing from the project all together. Tech stud Jean Baptiste-Queru officially confirmed the various rumors regarding his AOSP position and thus, confirmed that he was leaving everything all together because of his frustration with the difficulty of getting factory images for the newest Google tablet. Check out the following for his reasoning:
Well, I see that people have figured out why I’m quitting AOSP.
There’s no point being the maintainer of an Operating System that can’t boot to the home screen on its flagship device for lack of GPU support, especially when I’m getting the blame for something that I don’t have authority to fix myself and that I had anticipated and escalated more than 6 months ahead.
The reasoning is certainly legit, but what’s really eye-opening is the part where he talks about a Google flagship device not being able to boot to the home screen because of the lack of GPU support. Android purists will recall that the Nexus 4— which also features a Qualcomm Snapdragon chip— originally didn’t have the factory image and source code released in full. Naturally the issues were addressed, but owners of the device weren’t able to enjoy the true Nexus experience since the source code/factory images couldn’t be modified. Now we’re going through the same exact issue as the Snapdragon-powered Nexus 7 doesn’t have the factory images available to the masses. Is it a coincidence that both devices that two Snapdragon-based Nexus devices have had factory image issues? Probably— but one thing’s definitely for sure: it’s certainly going to suck not having Jean Baptiste Queru for our AOSP needs. Hopefully the Android team will find some sort of fix or remedy for future Nexus devices.
source: Android and me
According to the latest snooping in the supply chain, ASUS is on track to ship roughly 3.5 million new Nexus 7 tablets this year. At first, that might seem like a great number for the remainder of the year, but when you consider that the first generation Nexus 7 has shipped over 6 million units and the second half of the year is generally always strongest for technology sales thanks to the holidays, that 3.5 million probably isn’t as high as it should be. Part of the reason is speculated to be that the device will never be available in China because of some Google/China disagreements, as well as some pretty stiff competition in the 7-inch tablet space.
Regardless, this will probably still be a hot ticket item around Christmas in the States this year.
The Nexus Root Toolkit is a really nice piece of software which will help you with pretty much all of your rooting needs for your Nexus device. Yesterday, the software added support for Android 4.3 as well as the new Nexus 7 tablet which is really good news for anyone looking to root their new device. The software will automatically download all the necessary files to carry out the operation, has the ability to bring your device back into stock form, features a backup tool which will backup all of your data in case of a problem during the process, and can flash ZIM files, install applications, modify permissions, and more. Go grab it for free in the source link— donations are appreciated!
Over in Google’s Chromium bug tracker, an entry has shown up suggesting Android 5.0 Key Lime Pie may already be running on some Nexus devices. The entry is included in a bug report regarding a notification the developers wanted to remove when a user is logging in to Chrome. In verifying the issue has been addressed, several devices are listed which have been tested and are working as intended. Even though the new Nexus 7 comes with the latest, greatest Android build, 4.3, the entries for the Nexus 7 and the Nexus 4 report the Android build number is KRS36B. For the other devices, a trio of Samsung units, the build numbers all start with the familiar letter J associated with Jelly Bean builds.
Could the build number starting with a K be an indication that Key Lime Pie is already running on devices within the halls of Google as a test platform for other apps or is this just a typo?