Search results

No. The shield display is 1280x720 it can not display a higher resolution.

If you are using GFE 2.0.1.0 try updating it the current version is 2.1.0.0 see here http://www.geforce.com/geforce-experience/download

I have had 0 issues with magnets and memory cards/ssd/flash drives. The link from the post you quoted tells why in better detail then I will. HDDs use a magnet system to read and write the to the HDD, flash drives/ssd/memory cards don't work that way.

For me shield = massive paper weight None of the games I would use it for on PC or android support it.

PPSSPP I understand works well, but I have never got it to work. Dolphin is still alpha? and has a lot of bugs. IMO after every update the Shield gets worse. Currently there are very few game that are worth playing for android that support the Shield. To be honest I am seriously thinking about...

As much as I want to buy one and help with this...I hate to say I can not for probably at least 6 months. Engine builds get expensive rather quick. :P The only thing I saw in this thread about GSM and $100 was that the GSM version is $100 more.

I was looking at Verizon Prepaid devices and I saw this http://www.verizonwireless.com/prepaid/smartphone-plans/moto-g-by-motorola+prepaid/ Has anyone else seen that? Is it possible to use a Pre-Paid phone on a line with a monthly bill?

I have a 3g modem for a netbook here. The modem has a meid on it and the Netbook has a simcard slot. How can I test or look up if this is a GSM or CDMA 3g modem? UPDATE i think I found my answer http://www.barebonekit.net/hp-compaq-undp-1-3g-broadband-card_i_ltp3ghpcomundp1.aspx It seems to...

Another idea I have for this would not allow charging but it would slow down the rate of battery drain. I doubt you would find this cable premade, but instead of applying power to the usb otg circuit it would only connect the 2 data wires to the shield, and the 2 power wires to the wall charger...

Unless there are diodes on the usb connector on the shield that will prevent power going into the shield while in usb host mode, I do not see why it wont.

I think If you had something similar to http://www.amazon.com/OEM-UTStarcom-USB-Adapter-Cable/dp/B002W8EDOM/ref=sr_1_1?ie=UTF8&qid=1392490266&sr=8-1&keywords=usb+y+adapter you could use the charger to power both you usb device and the shield. It will just need to connect power to all 3 ends.

Google play is broken for me, but the problems are only on one account and on every device that uses that account. If I completely remove that account from any or all of the devices, and add a different account all the problems and errors are gone. Now moving to that new account would normally...

There is also at least one PSP emulator being worked on for android.

That router is on the list here http://shield.nvidia.com/accessories-hardware/ It is the first router on that list.

As in downloading the source or what? EDIT If you mean downloading the source go to https://developer.nvidia.com/develop4shield and follow the directions under 'Open Source Resources'

I don't build kernels, that said from my quick looking these should be the configs for the kernel. I got them from the android source i downloaded from nvidia.

glad you got it working

it needs a factory rest. my suggestion is to re-flash system (again) using the command fastboot -w flash system system.img the .sh file is for use on Linux, cygwin can probably do that if you have the correct things installed with it.

65 is out and it is a patch based update.

You should not need a custom recovery for this. Due to the download size of this update it appears to be an incremental update. the download size i see is 22.3 MB You would need to see the exact error to try an figure out more. UPDATE Installed fine for me

should be

FMA:Brotherhood by far

http://www.nyko.com/products/product-detail/?name=Shield+Dock EDIT It does not seem to sold anywhere as of right now.

He did post the command... here is a more specific example of the command to boot an image fastboot boot image.name image.name is the name of the image to boot. If your recovery image is named recovery.img then the command becomes fastboot boot recovery.img

Hmm I see an edit.... EA games has been responsible for many games that had promise but they were released very buggy, and rarely got patches to fix the problems. That last game I bought from EA was NFS Most Wanted (2005) Black Edition (That game was lucky to even get all the features EA...

I am going to guess you're not looking for the adb drivers, and you mean the MTP drivers. If that is the case AFAIK Windows is the only place for them.

If people need to ask EA to add shield support to anything the people asking will have a higher chance of winning the lottery without buying a ticket then EA adding support.

If anyone knows the moga controller keylayout it might help someone figure this out.

See OP

Try this it "should" be the recovery I currently have flashed EDIT It instead of flashing the recovery to test it, use "fastboot boot recovery.img"

http://goo.im/devs/agrabren seems to be gone. This was a simple ramdisk edit. I don't know for 100% sure if this recovery is 1.1, but if I am correct 1.0 was based on 4.2.2 and 1.1 on 4.3 From that I am guessing that this is 1.1, as to my knowledge there have been two recovery images so far...

When I was checking to see if I had 1.1 I found the naming error is still there. This brings me to my next point. I had edited the ramdisk on 1.0 to correct the naming error, and not updated to 1.1 Here is a link to 1.1 with the edited ramdisk. Update I messed up the link in Google drive i...

I have had no problems flashing updates with ClockWorkMOD revocery. However if you have the 1.0 version from http://forum.xda-developers.com/showthread.php?t=2390389 the update will fail with an error. 1.0 had a name wrong that makes it think the update are for a different device. the command...

Fixed that line for you. If the device is locked getting Nvidia to fix the software should not be a problem.

To be honest I never read the instructions on the sony site, I do not know what that menu will tell me if I flash a factory firmware. I do know that my R800x has been unlocked. It will not hurt to ignore step 1 there and follow the rest. If it works you have unlocked your bootloader. If not it...

I had typed a long post then I looked at it and saw that I should not post it. I am already running CyanogenMOD, and I fail to see how reinstalling it will fix what is already there. Please tell me how reinstalling what is currently installed will help. Now from your post you make it sound...

the partition that /staging mounts is /dev/block/platform/sdhci-tegra.3/by-name/USP as can be seen in the factory recovery's recovery.fstab # mount point fstype device /recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS /boot emmc...

That is not "official" as "officially" rooting and software mods are not supported. Linux is needed to extract the images that you get from https://developer.nvidia.com/develop4shield#OSR I am not sure what the blobs are for here is part of the blob file in update 63...

The files are located in /system/usr/keylayout, so root is needed to edit them.

I think this is why... This is from Vendor_054c_Product_0268.kl that lists "# Sony Playstation(R)3 Controller" close to the top. # Button "Select" maps to BACK. key 0x120 BACK here is the same key number from the kl for the xperial play key 0x120 BUTTON_SELECT I also do not have a PS3...

I understand that http://unlockbootloader.sonymobile.com/instructions now unlocks the R800x and has for sometime. http://www.xda-developers.com/android/sony-now-allowing-verizon-xperia-play-bootloader-unlock/

does flashing blobs do more that just copy the blob to the USP partition?

Just posting as a follow up to my earlier post here I had to download the superuser.zip from this Superuser page on the play store.

here are two methods both need root 1. dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/storage/sdcard0/boot.img I think this needs adb to be ran as root 2. adb shell "cat /dev/block/platform/sdhci-tegra.3/by-name/LNX">boot.img

the ps3 controller mapping did not change from update 59 to 63.

Glad you think it "works", but IMHO it still does not work because as you stated WiFi does not work. I still think it is something you have broken, you probably have something at the wrong version. If you had read the post I linked to..... ...then you would know that the boot.img you...

I have been looking at the shield key mappings (.kl and .kcm) for a project of mine, and I think something I found my be the cause of the select button error. I am not sure here, and I need to re-download update 63. That just made things worse. In your first post you said So now I am Asking...

read here http://forum.xda-developers.com/showpost.php?p=45819292&postcount=36 I don't have any ideas.

Do you mean the square on the PS3 controller is X on the shield? If that is the case I would guess that X on the PS3 controller will be A on the shield. I also thought the shield sticks had buttons like the PS3 controllers do. I have not used retroarch yet.

Try this CWM "should" work if you have the newest version from http://forum.xda-developers.com/showthread.php?t=2390389 The earlier version had a bug that did not allow OTA updates. As for WiFi I don't really know.