| NVIDIA Tegra Tab 7 gets tested in benchmarks Aug 12th 2013, 17:11, by Cory Gunther Late last week we learned that NVIDIA could be eying their next target. That being the tablet market with a new Tegra Tab 7 device in some trademark filings, which confirmed a 7-inch Tegra 4 quad-core powered Android tablet. Their first own branded NVIDIA SHIELD is already on the market, and now we’re seeing our first benchmark results for the new Tab. 
We don’t know much at this point but it appears that NVIDIA will be entering the tablet market to take on Google’s Nexus 7, ASUS, Samsung, and all the rest. The Tegra Tab (possibly named TegraNote) leaked last week. Being listed as the Tegra Tab-premium here suggests they might have multiple versions, if this leak is indeed even legit. The popular AnTuTu benchmark was reportedly ran on the new NVIDIA tablet, spreading those Tegra 4 quad-core wings and letting it fly in some benchmark testing. However, the results are average at best (for a Tegra 4) even though they beat the old quad-core powered, and the new Nexus 7 both. The reason we’re doubting this 27,000 score is because we’ve seen the Tegra 4 powered NVIDIA SHIELD do much, much better. 
Above is the leaked result for the 7-inch 1280 x 720p Tegra Tab running a quad-core Tegra 4 at 1.8 GHz apparently scoring 27,643. However, our own NVIDIA SHIELD Review showed a far more impressive processor. Which has us doubting this leaks accuracy. The SHIELD with the same Tegra 4 (we’re assuming) came in at 39,000 in AnTuTu. The highest of any device we’ve tested to date. It has a smaller 5-inch display, but comes in with the same 720p resolution. For now we’re not exactly sure what NVIDIA has planned, but with all their popular and quality THD TegraZone enhanced Android games a tablet specifically for those sure makes sense. More details on the Tegra Tab can be found from the original leak linked to below, and we have a feeling more details will be coming out quick. VIA: Unwired View |  | Archos GamePad 2 spotted in FCC filing Aug 12th 2013, 16:30, by Robert Nelson The Archos GamePad launched for those in the US back in March and it looks like the follow-up device is already in the works. The device is called the Archos GamePad 2 and currently sporting a model number of A70GP2. We have yet to hear anything direct from Archos, but judging from the FCC filing where the GamePad 2 was discovered — it looks like it may be several months before anything official is announced. 
The filing is light on the details, however it does have a confidentiality request letter. Said letter was dated for August 2nd and with a confidentiality request of 180 days. This request applies to the user manual as well as the external and internal images, which are basically the parts that would reveal something interesting. That being said, the label location portion of the filing did offer a look at the backside of the GamePad. Sadly though, there wasn’t much we can see from that image (sitting above) aside from a curved backing and trigger buttons sitting up top. Digging a bit deeper into the filing there were some basics though. For example, there was mention of single-band WiFi. Specifically, 802.11 b/g/n. There was also mention of Bluetooth, something that was missing from the original GamePad. Otherwise, as a refresher, the original Archos GamePad has a 7-inch 1024 x 600 display, dual-core 1.6GHz ARM Cortex A9 processor, 1GB of RAM, 8GB of internal storage, a microSD card slot, front-facing camera and Android 4.1 Jelly Bean. Finally, while this filing does have a six month confidentiality request, we do have to remember that Archos could surprise us with something sooner. After all, just last week we learned they were planning to make quite a few announcements during IFA and as many will realize, that takes place in early September. VIA: ArcTablet | | SwiftKey Cloud beta improves Flow prediction, Gmail support, more Aug 12th 2013, 15:43, by Robert Nelson SwiftKey Cloud beta saw an update earlier in the month and it looks like another update has already arrived. This latest takes the app from 4.2.0.94 to version 4.2.0.115. As we have seen in the past, this latest beta release brings the updated version for both smartphones and tablets. Or more important for those using the keyboard — this release has brought a handful of improvements. 
The big change this time around seems to deal with Gmail accounts. Specifically, this latest SwiftKey Cloud beta update brings support for a second Gmail account. The folks at SwiftKey have said it is now possible to personalize from a second Gmail account before personalizing from an earlier one has finished. And in addition, this update brings a fix for the crash that was happening when trying to start the Gmail personalization. Otherwise, there was also mention of increased responsiveness of Flow predictions and additional fixes dealing with the crashes in the Cloud preferences. Some specific apps that were addressed include fixes for Handcent and Hangout emoji entry and predictions being disabled in Pleco (where requested). There was also some removals in this latest beta release. First, the SwiftKey account details have been removed from the Android Settings, and second, the language models are no longer being backed up using Android back up. This applies to those who are also using the SwiftKey Cloud backup and sync and was done in an effort to save on network usage and and battery life. Fixes aside, as SwiftKey Cloud remains beta there are still known issues that may cause some issues. The lead issue here deals with words that are being re-added after they had been removed from predications. With this users may not see that word sync across all devices. The remaining issues include the following; - The showerhead Emoji in GoSMS messes up input
- Spanish inverted ? not visible on plain QWERTY keyboard when Spanish is loaded
- Popup accented characters missing after changing layout or language settings
- Prediction bar too small in landscape mode
- SwiftKey reluctant to replaced a mistyped bottom row character with a space (e.g. 'Hibthere' will not get corrected to 'Hi there')
SOURCE: SwiftKey Blog | |
No comments:
Post a Comment