Related
Now that Windows 8 will support ARM and have a tablet touch interface, will it be possible for a company to make a Windows 8 phone? Just would need supported hardware buttons and ability to make calls and take a SIM card. Likely/unlikely?
This would be a boon for Windows Mobile users who will not have to wait for Windows Phone 9 for all their old features to come back. In fact they would have something more powerful by a long way than any phone ever made.
(Of course some people claim Windows Phone 7 will be based on Windows 8 anyway... but even if it is it may be limited in important ways.)
you won't like a phone based on a desktop ui.
sorry, but the mouse is antiquated.
ohgood said:
you won't like a phone based on a desktop ui.
sorry, but the mouse is antiquated.
Click to expand...
Click to collapse
Windows 8 has an optional tablet UI than does not require a mouse to do anything.
I think it will eventually be the same OS on your PC, Tablet & Phone yes. PC & Tablet are in Windows 8, and maybe not WP8 but perhaps the next one will be the same OS with a layout for the phone like you see now, and be dockable (like the Moto Atrix, only actually functional).
No need for WP8 as Windows 8 already has a touch based interface and the ability to turn off unneeded features automatically (not just programs but also under the hood operations), saving ressources and making it available on ARM powered devices.
Sent from my Nexus S using XDA App
Now some more information is out.
It looks like Windows 8 will have phone calling in the Metro interface:
http://www.istartedsomething.com/20110918/windows-8-to-include-phone-calling-capability/
So Windows 8 (Metro) will be useable as-is as a phone system.
The issue may be hardware. Processor speed, memory, GPU will be fine, but the problem is the minimum resolution.
Windows 8 Metro apps require 1024x768 resolution:
http://www.winmatrix.com/forums/ind...o-apps-require-1024-x-768-minimum-resolution/
For a phone 768 pixels on the smaller dimension is excessive. The Apple "Retina display" is 960x640 and Toshiba's upcoming(?) display is 1,280x720, still not enough:
http://www.pcmag.com/article2/0,2817,2385574,00.asp#fbid=I7vQ_5t19x6
So unless Windows 8 changes requirements (which seems quite likely to me) this will be the main problem.
When windows phone 8 comes out we have the best camera and other few changes lets hope wp8 will be awesome
Probably possible but I doubt it would ever be supported by major carriers.
So I'm getting a better idea of the different operating systems for mobile phones. iOs, Android, and Windows seem to be the big 3. What are the differences between windows mobile and windows phone 7?
Everything. There are no points of commonality between the two in the developer or user experiences. The Windows Phone 7 experience is more closely related to the experiences on iOS or Android than on Windows Mobile.
This is mostly because Windows Mobile is a mobile operating system which debuted on Pocket PC's (remember those?) in 2000, predating iOS by seven years. Windows Phone 7, on the other hand debuted less than 18 months ago, meant to compete directly with iOS and Android and secure Microsoft's place in the mobile market.
If you're trying to get a feel for Windows Phone 7 as a former Windows Mobile user, I suggest you go to a phone store and try the Windows Phone; there are too many differences to enumerate here.
The answer is almost everything.
Windows Phone is as similar to Windows Mobile as the iPad is to the Apple Newton
Ireyn said:
Everything. There are no points of commonality between the two in the developer or user experiences. The Windows Phone 7 experience is more closely related to the experiences on iOS or Android than on Windows Mobile.
This is mostly because Windows Mobile is a mobile operating system which debuted on Pocket PC's (remember those?) in 2000, predating iOS by seven years. Windows Phone 7, on the other hand debuted less than 18 months ago, meant to compete directly with iOS and Android and secure Microsoft's place in the mobile market.
If you're trying to get a feel for Windows Phone 7 as a former Windows Mobile user, I suggest you go to a phone store and try the Windows Phone; there are too many differences to enumerate here.
Click to expand...
Click to collapse
Wrong
Windows mobile is more close to the android experience. With that i mean - battery life varies highly between each. HTC sense is found on windows mobile that are htc's which android also has. multiple hardware buttons. Applications can have root access and effect the whole phone. Multiple roms available that are custom built
Windows phone is closer to the Iphone only in terms like ease of use and smoothness. It however is very different from the Iphone. Like the iphone, things are more sand boxed. An application cannot bring the whole phone down. Security is high and malware on both iphone and windows phone is non existant. Windows phone uses live tiles that scroll vertically and flip and move to show information without actually opening the app. Iphone scrolls horizontally in grids of icons that are small and do not show extra information.
tkoh said:
So I'm getting a better idea of the different operating systems for mobile phones. iOs, Android, and Windows seem to be the big 3. What are the differences between windows mobile and windows phone 7?
Click to expand...
Click to collapse
In one word?
Metro.
When I wanted to know more about Windows Phone 7, I watched some videos, but then went into the Verizon phone store and tired the Trophy... and loved it. Bought one the very next day.
There is no "official" backwards compatibility with WM 6.x apps... but DFT is working on a full blown WM 6.x series emulator that might allow for those apps to work.
As far as experience, I won't touch an iPhone for moral reasons... but compared to Android, Windows Phone 7's experience is much smoother and much better on batteries in general. Windows Phone 7 runs smooth as silk (especially since most phones aren't duel+ core and full of power hogging hardware).. and I just love the experience.
The only REAL downside I can find is no Swype keyboard, but I've dealt with it since voice input works very well (for me).
I think the biggest factor about seeing the demo phone in person... was figuring out all the major functions of the phone on my own in less then 10 mins. A few things aren't obvious, but now I think about how to use phones differently with Windows Phone 7 (like holding stuff and seeing if options pop-up, or pressing ... for more options on some screens).
Definatly as stated watch some videos. You won't see live tiles on the demo phones doing much because they do not have live accounts attached to them. You miss 25% of the experience when demoing in a store.
I know that Microsoft is only going to release Windows 8 RT as a pre installed OS on the specific device. I also know that they will lock the boot loaders of these devices. I know the chances of getting this seam close to impossible, but i found this device on Asus website.
http://eee.asus.com/global/event/2012/computex2012/tablet-600.html
It looks exactly like the TF300T just running windows 8 RT, it is even using the same exact processor. Do any of the developers think that it would be possible to extract the OS from this device and port it over to the TF300T? Also wouldn't Asus also have to post the image of the OS on their site to restore the device in case of a crash and you need to reload? If the second is the case wouldn't we just need to have a custom boot loader that would allow us to flash and actually boot into Windows 8 RT? I am mainly just trying to get a developers viewpoint on this to see if it would even be possible.
it had double the ram, a different resolution, NFC, led flash...
these things alone will make it near impossible to port windows 8 over to our tf300's, its seems the only spec to match is the processor, and even then it doesnt say what type of tegra 3 that is, so i really wouldn't get your hopes to high
coffmad said:
it had double the ram, a different resolution, NFC, led flash...
these things alone will make it near impossible to port windows 8 over to our tf300's, its seems the only spec to match is the processor, and even then it doesnt say what type of tegra 3 that is, so i really wouldn't get your hopes to high
Click to expand...
Click to collapse
If windows 8 RT is anything like the current windows operating system ( which Microsoft says it shares most of the same code as the x86 based version), than having more ram does not matter. The only thing that really matters is that the chip set drivers are the same and that the storage controller drivers are the same. So as long as the chip set is the same (or the diver is the same) than i do not see how it wouldn't work.
Its not an x86 PC, mind it... Embedded ARM platforms dont have plug and play, "smart" buses and standarts in general... It doesnt matter if device X is visually the same as device Y, all the meaningful stuff - GPIO, interrupts etc - maybe completely different.
As far as my experience goes (i 'launched' (cant say ported, i only 'welded' assorted driver code and kernel) linux on wince acer s200 ), CPU and miscellaneous hw initialization may be completely different on WinRT. Besides, why you want an OS which is incompatible with either WM7 or old WinCE/WinMo?
tsamolotoff said:
Its not an x86 PC, mind it... Embedded ARM platforms dont have plug and play, "smart" buses and standarts in general... It doesnt matter if device X is visually the same as device Y, all the meaningful stuff - GPIO, interrupts etc - maybe completely different.
As far as my experience goes (i 'launched' (cant say ported, i only 'welded' assorted driver code and kernel) linux on wince acer s200 ), CPU and miscellaneous hw initialization may be completely different on WinRT. Besides, why you want an OS which is incompatible with either WM7 or old WinCE/WinMo?
Click to expand...
Click to collapse
I understand your points. I was simply pointing out that Microsoft stated that the majority of the code for Win RT is the same as the x86 version. I know that it has nothing to do with the look of the product and everything to do with the hardware inside. The only reason i would prefer Win RT over Android right now is that Win RT supports the full desktop version of IE 10. Android is lacking a fully functional desktop version ( chrome does not support apps, the full version of java, ETC.) If Android where to get a fully functional desktop web browser, i would be perfectly happy. Also it would be nice to have the full suite of Microsoft office for college.
I think its more connected to limited IO and CPU resources of ARM tablets, rather than OS limitations... MS can say absolutely anything, but the fact is that there would be no software on release... especially if you take into account that Valve/major OEMs had already sent their 'f-bombs' to MS and its plans with windows 8.
Would the fact that all RT tabs ship with locked boot loaders halt anything as well? I don't believe MS wants RT out on anything but approved tabs.
Sent from my SAMSUNG-SGH-T989 using xda premium
You do know that since almost all win apps are in net frame work making them work is one click in vs2012?
Sent from my ASUS Transformer Pad TF300TG using Tapatalk 2
So after playing with my Surface for 5 days now, it is obvious there is a lot of capability in the back end through the Desktop. II have networked printers, and drives at both home and office going, streaming content etc. It is very capable for what it is, way beyond any other Ipad and Android tablet out there. So it seems to me it is just a matter of time before some XDAer figures out a way to unleash it and possibly load other programs (non-RT) programs some way. We know the official MS word is no, but it seems to me it is a fully capable Win8 machine that just has some goierners on it and limited processing power, just waiting to be cracked.
Am I just dreaming?
I would love to see this happen. The one thing holding me back from purchasing one. I'd love a Windows 8 Pro version tablet at the Surface RT pricing but wouldn't we all...
I dont think rt can run x86 app properly. Because the cpu is not as good as x86 core. I am interested in porting rt to compatiable device such as tergra 2 and 3 pad.
Sent from my GT-N7000 using xda app-developers app
liu2002 said:
I dont think rt can run x86 app properly. Because the cpu is not as good as x86 core. I am interested in porting rt to compatiable device such as tergra 2 and 3 pad.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I don't think it's necessarily about the Tegra being "as good" as an x86 - the issue is that you'd need an emulator, or the source for the x86 app which you'd then need to re-compile for ARM. I believe MS made a developer toolkit available that allows simpler conversion from x86 to ARM but it's still up to the app vendors to do it.
In theory, the same code could compile for both x86/64 and ARM (RT), but VS2012 will not allow you to compile an ARM desktop app. There is no legit way to write/compile a desktop app on RT. Its an arbitrary BS limitation put in place by MS. You cannot side load apps, everything must come through the MS store, RT enterprise being an exception... which doesn't help us. And the MS store will only offer Metro apps. MS office shows that's desktop apps are fully possible, albeit recoded/recompiled for ARM, but MS will not allow it. In an ideal world, RT would be a fully supported OS, and the likes of Adobe and others could release desktop apps for RT, but sadly it won't happen.
Sent from my Galaxy Nexus using Tapatalk 2
Skitals said:
In an ideal world, RT would be a fully supported OS, and the likes of Adobe and others could release desktop apps for RT, but sadly it won't happen.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Why do you say that?
Because its not allowed, only metro style apps published through the app store are allowed. Even if you compile compatible desktop software, the OS won't run it. Its a closed sandbox.
At best we can hope for a "homebrew" community to compile open source software, and find some hacks to get it running.
Sent from my Galaxy Nexus using Tapatalk 2
Hello,
I’m a happy owner of the Surface RT and I just wanted to add my 2c.
I think that Metro UI is great for tablet, but lacks apps !
So I cannot understand why Microsoft didn’t include .Net on this platform ! I think the main goal and the first “Homebrew” must be recompilation of Mono for ARM. As this will allow us develop a lot of programs, quickly and using “good” tools (Visual )
I just started to study WinRT and I’m already hitting a lot of blocks (For instance, I cannot find a way to open Shared Socket ! So if any other app listen on 1900 port, I lose my SSDP discovery... )
But I think recompilation of Mono is definitely a way to go ! I think i’ll try it this week-end, if I have some time, but It’s sure I will not be able install on my surface As for now it seems to be impossible to enter Testing Mode on it.
Jurion
jurion said:
So I cannot understand why Microsoft didn’t include .Net on this platform !
Click to expand...
Click to collapse
I think people seem to be missing something here (well, not just here, on other threads/forums.blogs too). MS have essentially (it’s really quite impressive) ported over the entire Windows OS to run on ARM – and this includes all of .NET v4 with supporting libraries/DLLs.
You only have to pop to C:\Windows\Microsoft.NET\Framework\v4.0.30319 on your Surface RT to see – all the same libraries for the same version of .NET a x86 desktop seem to be there - including Linq, SQL, reflection etc.
Now, this could be really great news! I’d bet that it would be entirely possible for standard .NET applications (by standard, I mean programs that only use managed code and nothing legacy) to be reasonably easily recompiled to run on ARM - ideally as easyily as changing a drop-down!
Furthermore, this is all supported in Visual Studio, it’s just locked down a bit - I’ve been able to compile, with VS2012 (and a minor tweak to remove the ARM compile block) a simple command line EXE for ARM (using .NET calls – though only in C++ which is a shame). The problem is, as soon I open it on Surface, I get an error saying the ‘digital certificate’ couldn't be validated – a common issue which has a simple fix documented online. The catch... that the instructions to remove this block don’t work with secure boot enabled, and - at present - we can’t disable this on the Surface (on normal PCs this can be turned off in the bios).
So – the key to all this, is for MS to open it up (not impossible, but who knows if or when) or for someone to get round this secure boot/certificate requirement. I’m sure there’s some smart people on here with abilities to work on, and hopefully succeed in doing this. Even if people aren't able to work a way round this block, I'm hopefully that eventually MS may release some firmware update tools that someone can hack to switch off UEFI secure boot. Or perhaps someone at MS or a partner may leak some file/app/boot that unlocks this for dev/enterprise purposes.
I look forward to it happening!
T
Skitals said:
In theory, the same code could compile for both x86/64 and ARM (RT), but VS2012 will not allow you to compile an ARM desktop app. There is no legit way to write/compile a desktop app on RT. Its an arbitrary BS limitation put in place by MS. You cannot side load apps, everything must come through the MS store, RT enterprise being an exception... which doesn't help us. And the MS store will only offer Metro apps. MS office shows that's desktop apps are fully possible, albeit recoded/recompiled for ARM, but MS will not allow it. In an ideal world, RT would be a fully supported OS, and the likes of Adobe and others could release desktop apps for RT, but sadly it won't happen.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Everything doesn't have to come through the MS store, you can install applications that you build in Visual Studio 2012 for Windows Store, create an appx package and choose not to publish it in Windows Store. VS2012 then creates an appx package as well as a PowerShell script that you can run on Surface, accept security warning, get the developer's license on the device (it's free) and that's it!
It is fairly obvious why MS does not allow installation of "Desktop" apps on ARM tablets. Otherwise dev's would get lazy and just recompile desktop apps for ARM. The experience on a touch tablet would not be great on (unmodified) Desktop apps, hence Microsoft set this constraint on Windows RT in order to push dev's towards making a proper touch friendly app. The result is of course the lack of apps initially, but in the long run the benefits will be a greater experience as the apps would be optimized for touch.
Sure there are obvious downsides to this strategy, but the decision itself makes a lot of sense from a useability standpoint. You already read the complaints in reviews about "Office" not being Metro-style and unfriendly to touch. However this is naturally a decision due to time constraints, because MS would have also preferred to not include a desktop on RT. Office is the selling point now, to gravitate people towards RT and when there is enough demand, the touch friendly (Metro) apps will flow in eventually
Backflipping said:
I think people seem to be missing something here (well, not just here, on other threads/forums.blogs too). MS have essentially (it’s really quite impressive) ported over the entire Windows OS to run on ARM – and this includes all of .NET v4 with supporting libraries/DLLs.
You only have to pop to C:\Windows\Microsoft.NET\Framework\v4.0.30319 on your Surface RT to see – all the same libraries for the same version of .NET a x86 desktop seem to be there - including Linq, SQL, reflection etc.
Now, this could be really great news! I’d bet that it would be entirely possible for standard .NET applications (by standard, I mean programs that only use managed code and nothing legacy) to be reasonably easily recompiled to run on ARM - ideally as easyily as changing a drop-down!
Furthermore, this is all supported in Visual Studio, it’s just locked down a bit - I’ve been able to compile, with VS2012 (and a minor tweak to remove the ARM compile block) a simple command line EXE for ARM (using .NET calls – though only in C++ which is a shame). The problem is, as soon I open it on Surface, I get an error saying the ‘digital certificate’ couldn't be validated – a common issue which has a simple fix documented online. The catch... that the instructions to remove this block don’t work with secure boot enabled, and - at present - we can’t disable this on the Surface (on normal PCs this can be turned off in the bios).
So – the key to all this, is for MS to open it up (not impossible, but who knows if or when) or for someone to get round this secure boot/certificate requirement. I’m sure there’s some smart people on here with abilities to work on, and hopefully succeed in doing this. Even if people aren't able to work a way round this block, I'm hopefully that eventually MS may release some firmware update tools that someone can hack to switch off UEFI secure boot. Or perhaps someone at MS or a partner may leak some file/app/boot that unlocks this for dev/enterprise purposes.
I look forward to it happening!
T
Click to expand...
Click to collapse
Hmmm, sorry my bad, didn't look enougth to find .Net assemblies.
As for open it for MS, may be, maaaay be it's the same scheme which they followed with Windows Phone 7.
No native developpment for 7.0 -- 7.8
But they open it for 8.0
May be they just want to force people developp Metro app to populate the store first.
So where's the best place to get one?
I'm looking into buying one very very soon, I found some on ebay for $585 with the cover, That sounds like a win to me. I wish QVC had it, That'd be lovely.
I'm praying we get a work around for all this, But still If the device isn't made for it, I can't be mad that it doesn't do it, That's like being angry that my car doesn't fly.
But it's such a tease, it worries me that I'll have an entire desktop, Sitting, Obselete, With nothing but Office, which I wont even use.
Can't_Live_Without_My_Evo said:
I'm looking into buying one very very soon, I found some on ebay for $585 with the cover, That sounds like a win to me. I wish QVC had it, That'd be lovely.
I'm praying we get a work around for all this, But still If the device isn't made for it, I can't be mad that it doesn't do it, That's like being angry that my car doesn't fly.
But it's such a tease, it worries me that I'll have an entire desktop, Sitting, Obselete, With nothing but Office, which I wont even use.
Click to expand...
Click to collapse
It is made for it. It has the full desktop, and the full desktop Office suite. Its a big tease. The whole "do more" campaign advertises you can "click in" and have full laptop productivity with touchpad and mouse/keyboard. Except the only software to take advantage of it is desktop IE and Office.
Sent from my Galaxy Nexus using Tapatalk 2
Right now 8.1 is a preview but what happens when it is fully released? Will windows RT auto update to it even if we don't like 8.1 and want to stay on Windows 8 RT?
I know you can disable auto-updates by hacking the registry but Id rather not have to do that.
Any way to keep automatic updates but ensure your system never upgrades to 8.1?
Why? 8.1 works great.
ap3604 said:
Any way to keep automatic updates but ensure your system never upgrades to 8.1?
Click to expand...
Click to collapse
Windows RT is supported by WSUS. I never tested it myself, but you can setup your device to get updates not from MS site but from your local WSUS server - and just don't approve there the updates you don't like.
And similar to earlier service packs - there would be an "8.1 blocker" (look for Win7 SP1 blocker here: http://www.microsoft.com/en-us/download/details.aspx?id=22464). As this is just a registry key - it may work on RT too.
Dane Reynolds said:
Why? 8.1 works great.
Click to expand...
Click to collapse
One massive issue with 8.1 which is enough to keep a large user base from updating: jailbreak.
Once there is a jailbreak for 8.1 though, then your argument would be valid.
Not sure why you wouldn't want to run updates but so far Windows 8.1 rocks! Makes RT so much better.
SixSixSevenSeven said:
One massive issue with 8.1 which is enough to keep a large user base from updating: jailbreak.
Once there is a jailbreak for 8.1 though, then your argument would be valid.
Click to expand...
Click to collapse
You talking about a jailbreak for 8.1 RT? Is so what type of stuff can you do with the jailbreak?
Dane Reynolds said:
Why? 8.1 works great.
Click to expand...
Click to collapse
phantomlightgames said:
Not sure why you wouldn't want to run updates but so far Windows 8.1 rocks! Makes RT so much better.
Click to expand...
Click to collapse
Not on the Asus Vivo RT it doesn't :silly:
8.1 really f#&@'s up the trackpad
Wow that's good to know.. I'm currently running it on a Dell T3500 desktop both Surface RT & Pro.
Are you sure it's not a driver issue. Maybe Asus have some updates available for track pad?
@Dane Reynolds: You new here? The Windows RT jailbreak has been a pretty big deal - especially on the RT Dev&Hacking sub-forum here - since its initial reveal over half a year ago. It removes the signing restrictions that Microsoft uses to lock out third-party desktop apps. With the jailbreak, you can:
1) Run .NET 4 (or later) desktop programs.
2) Run open-source Win32 desktop programs that were recompiled for RT (there's a list of them; check my sig).
3) Run a handful of programs specifically written for Windows RT tablets, including an x86 emulation layer.
4) Run various non-.NET legacy programs (some x86 through the emulation layer, some Java through IKVM, some Python through an incomplete port, Perl, Ruby, Lua, and a bunch of game engines).
5) Install third-party drivers (such as the open-source program Process Hacker uses).
Windows RT 8.1 breaks the method used to jailbreak RT 8.0. There are people working on getting it back - the OS is a hell of a lot more useful when you can run things like PuTTY and 7-Zip and even WebKit-based web browsers - but until them, most people that hang out around here are either dual-booting 8.0 and 8.1 (if they have enough space) or just sticking with 8.0.
GoodDayToDie said:
@Dane Reynolds: You new here?
Click to expand...
Click to collapse
Nah, I've been here since RT was released, I heard about the jailbreak but was never interested, but the only reason I wasn't interested was I never found any fun stuff to do with the jailbreak.
Dane Reynolds said:
Nah, I've been here since RT was released, I heard about the jailbreak but was never interested, but the only reason I wasn't interested was I never found any fun stuff to do with the jailbreak.
Click to expand...
Click to collapse
no fun stuff? Quakes 1, 2 and 3. Numerous other games, MAME I think.
Python.
.NET
FreeDownloadManager
a torrent client
An html5 browser other than IE (hopefully chromium or Firefox eventually)
PuTTY (would be an absolute must have for me)
Loads of other software many either useful or fun or both.
It really opens up the desktop side of RT
Damn, quake sounds fun and I could use chrome ... I kind of regret getting 8.1
I see the use for a jailbreak but I think it brings the OS backwards. These desktop apps aren't optimized for touch. I think building apps for the new interface is the way to go.
Funny; I get around fine using touch on the desktop (no, my fingers aren't even tiny). Well, except for typing. That sucks, Desktop or Metro. So, I have a Touch Cover, which makes typing a lot nicer. It also has a trackpad, so I only use touch when it's better than using a trackpad.
So, now I have a keyboard and pointing device, in addition to touch, for the device to be useful to me. Care to explain to me again why using apps which are amenable to all three input methods, instead of only one, "brings the OS backwards"? Because the way I see it, taking a multi-input device and excluding all those apps which aren't (over) optimized for a single form of input is a hell of a lot *more* backward...
Dane Reynolds said:
Damn, quake sounds fun and I could use chrome ... I kind of regret getting 8.1
Click to expand...
Click to collapse
I love quake and doom, been playing through doom again on my PSP actually (CFW-PRO to effectively jailbreak the PSP, then there are 2 or 3 ports for PSP)
Chrome isnt out for RT yet. GoodDayToDie had a look, but its complicated. Kudos to him for taking a look anyway, but so far 1 guy on his own hasnt managed to do it. Firefox also has its own issues. We may or may not see them eventually though. The jailbreak would be the first step before you could run them though.
As for 8.1. Trig0r has 8.0 recoveries for the surface RT which you could use to downgrade. Hopefully someone will get 8.1 jailbroken soon too, but microsoft patched the exploit that was being used before.
Thanks, I might ask for a recovery as I love gaming, speaking of gaming i know the Surface's hardware isn't high enough to run games but i was wondering if Onlive would be releasing an app for RT.
That would actually be a legitimate use for OnLive... wasn't sure I'd ever see one of those.
Surface (Pro or RT) are fine for light gaming, or for running older games. The RT does actually have NVidia graphics, they're just really underpowered. The Pro has only Intel graphics, but the Intel GMA for the i5 might actually be more powerful than the RT's Tegra 3 (haven't checked). In any case, there are lots of games known to work (if not always at max resolution / quality) on the Pro, and the RT has a number of older games which have been ported over working fine, and some old x86 games that run in the dynamic recompilation engine also working (though so far as I know, none of those ones are 3D).
ap3604 said:
Not sure why you wouldn't want to run updates but so far Windows 8.1 rocks! Makes RT so much better.
Click to expand...
Click to collapse
Not on the Asus Vivo RT it doesn't :silly:
8.1 really f#&@'s up the trackpad
Click to expand...
Click to collapse
I own VivoTab RT 3g - no problems with trackpad in 8.1. Currently I have no major problems with 8.1 except for the blinking screen issue that is present in 8.0 too. Even VPN works fine, so I finally can connect to my workplace and read email with Outlook, use RDP or Citrix Receiver.