yashsingh1/xdaforums huggingface dataset:
[Windows Phone 7 General] RustyGrom:
I agree as long as it's handled appropriately. WP7 will get it, it's just a matter of when.

Meh. For developers, yea. And we can. Enterprise users will get a solution. People often mention the enterprise for side loading even though enterprise users would never use side loading.

Meh. If the actual use cases for file system access are covered, you don't really need it (unless you're just trying to tweak/hack things but we'll have file system access through a 'jailbreak' anyways)

Rather vague. WP7 is pretty customizable. It doesn't go as deep as WM or Android but it is much easier and more stable.

It will come. IE will get an updated rendering engine. Keep in mind that HTML5 is still a draft spec.

Yes/no. From most accounts, it's practically useless on Android. That being said, Microsoft and Adobe have committed to it. Adobe was actually working on it already and had it mostly done but Microsoft made some changes to how the OS renders graphics and broke Adobe's work.

Meh, pretty superfluous. Who cares what engine it is as long as it works?

While it is definitely lacking in many areas at the moment, you don't really need native APIs if the managed APIs are good enough. WP7 has a fantastic, managed gaming platform and most of the other stuff you would need native code for wouldn't be allowed in the marketplace anyways.

Quality > quantity. That said, they will come. How many did Android have at launch?

Would be kinda nice but not really that useful to average joe. Using your logic, it hasn't hurt the iPhone (even though I'm sure this sort of thing has cost the iPhone at least a few sales).
[Windows Phone 7 General] Fermat:
Still full of lame excuses, instead of talking about real advantages. Typical fanboy.

Even if you could excuse all the shortcomings, that still wouldn't make WP7 better than anything else.

And you can't excuse the shortcomings. 'Meh' is not an excuse, 'it will come some time in the far, far away future is not an excuse, 'I don't need it' is not an excuse.
[Windows Phone 7 General] vetvito:
Thank you, my point!!!!

They say yes it will, then I say NO it Won't, they say yes it will because of Updates; then I say why buy a new phone, then the circle begins.
[Windows Phone 7 General] Fermat:
Haha, hilarious! But obviously, it won't. That's the nature of technology.
[Windows Phone 7 General] RustyGrom:
And as I said before, devices will get smaller/thinner, have better battery life, better screens, better camera(s), more storage, faster CPU, etc.
[Windows Phone 7 General] Fermat:
...and software that doesn't work on older devices.
[Windows Phone 7 General] RustyGrom:
Took 3yrs for that to happen on iPhone.
[Windows Phone 7 General] 12aon:
Mod: Tone down one the name-calling please, it's not called for.

12aon
[Windows Phone 7 General] Fermat:
Wrong. Took one year. In every iPhone OS release there were features that didn't work on older iPhones. The same will happen with WP7, naturally.
[Windows Phone 7 General] RustyGrom:
Small, hardware reliant features that don't really affect developers.

And they don't really cause much consumer confusion since it's still a highly spec'd device and they only have more than the old version. The same hasn't been true on WM and Android. Soo many devices have extremely poor experiences because they're missing basic things. How many Android/WM devices come with hardly any storage, for example? That's why WP7 has strict minimum requirements that includes things like proximity sensors and accelerometer.
[Windows Phone 7 General] Fermat:
Small? No. Hardware reliant? No. Don't affect developers? Wrong.

Android makes it really easy to write apps that work on all phones. Much easier than iOS. Does it matter that there are different versions when it's so easy to make apps work on all of them? Of course not.

And I'm still waiting for posts about the good things in WP7 instead of the lame excuses. I guess I could name more good things in WP7 than all the faboys. But I'm also not shy about naming the shortcomings. No need for lame excuses.
[Windows Phone 7 General] RustyGrom:
I'm glad you back up your accusations with evidence. :facepalm:
[Windows Phone 7 General] vetvito:
Do you see the circle? You can guess my answer to your statement.
[Windows Phone 7 General] vangrieg:
There is no circle. Some fragmentation is inevitable as it's a consequence of progress. This is not the issue. The issue is with the scale and causes of the fragmentation. If three years from now smartphones will be powered by 5GHz quad-core 64 bit processors which last for five days of heavy use, everything released today will be worthless plastic. But that's not what's happening with Android. When you buy a device which is outdated the day you bought it and nobody can say when you'll get an update, when Google releases Google Maps or Twitter or what not that don't work on the overwhelming majority of devices in the market, when the word "Android" doesn't mean squat about the phone's capabilities - you can sync with multiple exchange accounts, just one, multiple but no calendar etc. etc., when you have to have a dozen devices to see whether your app performs well on different hardware which is similar (i.e. not worlds apart like 1GHZ ARM and 5GHZ 64 bit stuff) and recent in theory, and you managed to do it in just one year, your platform is a freaking mess, both for developers and users (even though the latter may not realize it when they listen to what salesemen at Verizon pitch). Google themselves acknowledge it reluctantly and talk about addressing the issue, although they initially said they would do it in 2.2, now they talk about 3.0, and I doubt they can do much about it because Android is a freaking committee where everyone who feels like a cook can add to the broth whenever he feels like, and because, according to Andy Rubin, even within Google features get to releases randomly. They just like doing whatever they feel like doing. This platform just isn't managed. Therefore it looks like a mess, progresses like a mess and works like a mess.
[Windows Phone 7 General] RustyGrom:
The circle is only in your mind. There's two separate things here.

1. Hardware will get better. People will have to buy new phones to get the new hardware.

2. Software will get better. Free updates will be delivered to both the first gen and later model phones.

Just because the software is the same on the old devices as the new one, doesn't mean that the hardware is the same. The strict baseline that MS has set allows them to reliably release updates for all devices. When will Microsoft leave old devices behind? Who knows. Yes, it will happen eventually (as Apple did with the iPhone after 3yrs) but it certainly won't be less than 2yrs out. And by then you'll be ready for a new device. And I know not all countries operate on the same subsidized model that exists in the US but most carriers allow subsidized phone upgrades every 2yrs or less. I mean just look at WinMo... The HTC Apache can run the same WinMo 6.5 as the Touch Pro2, does that mean that there's no value in the newer device?

Also, people lose, break, scratch, etc phones a LOT. So if for no other reason, a vast majority of people will buy new devices out of necessity regardless of new features.

edit: and what vangrieg said :)
[Windows Phone 7 General] Fermat:
You guys are so desperate... you can talk about it as much as you want, but fragmentation will never become an issue. ;)

But if talking about it makes you feel better... well...

As I said, fragmentation gives fanboys something to talk about, but nothing else. Oh and maybe you think about your 'arguments' again and why they make zero sense. Or talk about something that really matters, like multitasking.
[Windows Phone 7 General] RustyGrom:
Try writing a 3D app for WinMo and then supporting it. Shoot, try writing ANY app for WinMo (beyond hello world). The vast range of devices and software makes it a nightmare to develop and test something that works on even a significant minority of WinMo devices.
[Windows Phone 7 General] Fermat:
Yeah comparing WM to Android makes a lot of sense... shows how clueless you are. You have no idea what you're talking about.

I won't tell you again that Android makes it very, very easy to write something that works on all Android phones - regardless of the OS version. Google isn't stupid, they made sure that there would be no issues. That's why they do things like running apps in the Dalvik VM.

WM is a different story. Developing for that OS sucks, plain and simple. WM doesn't have universal APIs for anything. No sensor API, no compass API, no graphics drivers on most phones... nothing.

Obviously you have no clue about developing... that's probably why you think Android fragmentation is an issue.
[Windows Phone 7 General] RustyGrom:
I've never developed for Android so I'm just going off my experience. I have a decent amount of experience in developing for various platforms (just not android). Have you actually developed for Android? If so, what have you released? You said "fragmentation will never become an issue", without any mention of Android. You've repeatedly stated that fragmentation isn't an issue on any platform.

How is it not a problem trying to develop for the vast arange of screen sizes, CPU speeds, etc that exist for Android? How can you write a high performance game when it will barely work on half the devices? How can you take advantage of APIs released in 2.2 that don't exist on 90% of devices that are currently on store shelves? What about all those devices stuck on 1.6 that will never see such basic things as Google Maps Navigation?

Fragmentation has shown to be a problem on several platforms in history. It always has and likely always will be. Android is certainly fragmented. Many unbiased sources have noted this.
[Windows Phone 7 General] Windcape:
10 different screen sizes, and different API availability due to fragmenetation of the OS? It's still around 50% of the phones running a pre-Eclair (2.0) version, which limits your abilities as developer. This means any serious application would have to be written for the Cupcake (1.5) API.

It's also impossible to make anything uniform on Android, as Android don't have any standards, and the manufactures are pushing their own UIs (like Sense), making it even more impossible to create a integrated look'n'feel.

More like the opposite. If you don't consider the OS fragmentation a problem, then you're clearly not a software developer.
[Windows Phone 7 General] RustyGrom:
Just for fermat...

Platform	API Level	Distribution

Android 1.5	3	15.3%

Android 1.6	4	20.3%

Android 2.1	7	59.7%

Android 2.2	8	4.5%
[Windows Phone 7 General] Windcape:
Lets include the source on that one RustyGrom :p

http://developer.android.com/resources/dashboard/platform-versions.html
[Windows Phone 7 General] RustyGrom:
Thanks. Wouldn't want him to go off spouting how I'm making it all up.
[Windows Phone 7 General] vetvito:
You see how you guys easily point out the problems with other OSs? Why can't you do the same for WP7?

I guess you don't see any problems with WP7. You just say an update is coming.

You point out problems with Android as if there not being addressed. Android by far is the most updated OS. They know about the fragmentation problem and it will be addressed, updates will slow down, and you will be surprised at all the changes.

The big problem is WP7 is NOT competing against Android. They've made it obvious that they're competing against the iphone.
[Windows Phone 7 General] vangrieg:
And why is it a problem?
[Windows Phone 7 General] Windcape:
Because they aren't. Google refuse to force the OHA to update all their devices.

No, it's not. Look at the numbers for god sake.

They known about the fragmentation problem for a year, and they done absolutely nothing to change it. The first release of the OS didn't even have Over-the-Air updates!

Yes, because Android is low-end phones, and is more considered a take on Symbian than iPhone, in the first place. Android's success is due to most devices it's sold on is cheap hardware.
[Windows Phone 7 General] vangrieg:
I don't know who you mean by that "you", but I do see problems with WP7. Fragmentation just isn't one of them. Lack of multitasking is for some scenarios that aren't critical for me personally, so I can live with that. Lack of C&P for me is a bummer, file handling is annoying (mostly for pdfs in my case). I'll need to see the codec support in real devices, but the list is shrinking, and there's no hope for third-party solutions. So there are things that plain suck. There are also great things, and there's no single platform out there that doesn't suck in one thing or another. So it's not a choice between a perfect thing and imperfect ones. It's a choice between things that are imperfect in different ways.

A real showstopper for me is miserable language support though (again with no hope to get it from third parties). Without a Russian keyboard it's completely useless here. On the bright side, by the time WP7 gets it, it might be at 7.1 already. :)
[Windows Phone 7 General] Fermat:
Since I'm a developer and I have a clue what I'm talking about, I know those numbers.

Luckily Android is not crap like WM and making apps work on all Android phones easy as pie.

Too bad you have no clue. Anyway, those numbers didn't prevent Windows from owning the market.

Android will own the market like Windows and it's much easier to make stuff work on all Android versions than to make it work on all Windows versions.

Fragmentation doesn't hurt anyone. It gives stupid fanboys something to talk about.
[Windows Phone 7 General] Windcape:
lol

You're hopeless. Enjoy coding your 1.5 Android apps for 10 different screen sizes. I'm sure your boss consider double work well paid.

You're not a developer. This just proves you're talking out of your arse.
[Windows Phone 7 General] Fermat:
I enjoy coding for Android. Gives me much more possibilities than WP7.

I rather care about a few different versions than not having important features like multitasking. Having to implement methods for getting files onto the phone because there's no file system access or USB storage mode isn't great either. On Android, I don't have to care about stuff like this because the OS does everything for me.

And actually, I don't even care about different versions because 99.9% of the time stuff just works on Android. On all versions.

You're searching for an issue that doesn't exist, because you can't find any real advantages in WP7. I bet I know more real WP7 advantages than you, lol :D (yes, it has real advantages - but being locked down is not one of them)
[Windows Phone 7 General] Windcape:
Seeing you have squad idea about the possibilities in WP7, and how to code Silverlight, you should kept your mouth shut.

99.99% of all applications for phones don't need multitasking. Your personal hobby applications don't need it either.

Just shows you never written a production scale application targeting both 2.x and 1.x

Here's a guide for you: http://www.brighthub.com/mobile/google-android/articles/61895.aspx

"just works" eh? Perhaps actually try write a application for more than once device, and you would find out what we're talking about.
[Windows Phone 7 General] Fermat:
Well, I could go on telling you that you have no clue, but I think you're a waste of time.

You must be a pretty lousy developer if you can't even make stuff work for different screen resolutions. :D

Yeah stuff on Android just works. Let's see whether WP7 can do that, too... oh, wait, we already know it can't because it's so limited.

How about going back to topic and trying to excuse the lack of multitasking?

Oh, wait, there is no excuse.

Let's just wait and see whether fragmentation will keep Android from becoming number one OS worldwide. Only Nokia is left... tell me again that fragmentation hurts Android when it owns 70% of the smartphone market.

It won't take that long. In a few months we'll see who was right ;)
[Windows Phone 7 General] 12aon:
Mod: Guys I appreciate your eagerness to prove each other wrong but the way you are doing it could be taken the wrong way. I want to emphasize a respect attitude amongst each other, otherwise I'll close the thread before this escalates.

12aon
[Windows Phone 7 General] Fermat:
It's gone completely OT anyway... people should go back to topic and continue searching for excuses for the lack of multitasking.

The problem is, when they realized that were were no excuses, they went OT and tried to find flaws in competing platforms.

Now that they can't find those flaws and can't excuse the lack of multitasking, you may as well close the thread.
[Windows Phone 7 General] vetvito:
Do you believe the stuff you type? Do you, or you just make it up as you type?
[Windows Phone 7 General] Fermat:
OMG who wrote that nonsense?

Android is low-end phones? Android is not the fastest developing OS? WP7 is competing against the iPhone?

You're kidding, right?
[Hero CDMA Themes and Apps] adamboyd83:
Anyway of getting this ported to the hero build?

http://xdaforums.com/showthread.php?t=735480

First theme for vanilla that I have seen that I actually like.
[Hero CDMA Themes and Apps] adamboyd83:
I have no idea how to port a theme. It would be awesome to get this theme.
[Hero CDMA Themes and Apps] smolck:
Visit the android themes forum there is a program now that ports themes
[Hero CDMA Themes and Apps] daPorkchop:
Can you provide a link? To the auto porter?

Ive been working on porting some of his stuff. Ive got almost all his status icons. Ive thrown in a few of my own as well and some stuff from other themes. I just don't know how to sign a flashable zip. I was also planning on doing some app icons and some tweaking to launcher pro.
[Hero CDMA Themes and Apps] adamboyd83:
Im at work and dont really have time to mess with this so if you get it working hook me up.

http://xdaforums.com/showthread.php?t=737526
[Hero CDMA Themes and Apps] daPorkchop:
Haha yeah Im at work to so ill work some more on it tonight.
[Hero CDMA Themes and Apps] daPorkchop:
From the author.
[Hero CDMA Themes and Apps] adamboyd83:
Even better. Im a big fan of the lockscreen and the taskbar.
[Hero CDMA Themes and Apps] JiveMods:
i agree way sick lockscreen
[Hero CDMA Themes and Apps] PlagaDeRock:
I started a port of this to our heros but I'm porting it to CSRoM. If you are using that then your good to go but if your using CM6 and want to port it to that it will be alot easier as I've resized most of the images for our heros. :)

Download Link
[Hero CDMA Themes and Apps] sdotcarlisle:
Download Sculpted for zomg_notthedogtoo Froyo Update Credit to Phinnaeus and PlagaDeRock This will only be good for a few days i'd imagine as this rom is still early stages but i'll try to keep up and post updates here. http://xdaforums.com/showpost.php?p=6271011&postcount=14
[Hero CDMA Themes and Apps] adamboyd83:
Sweet thanks. Giving it a try now.
[Hero CDMA Themes and Apps] PlagaDeRock:
I'm still working on it more so I'll let you guys know when I got more ported over. :)
[Hero CDMA Themes and Apps] adamboyd83:
when i flashed, it btought back the LED stick issue. But a damn good start.
[Hero CDMA Themes and Apps] incorrect:
here's an updated version for the n00bz froyo update, thanks to tomatosoup
[Hero CDMA Themes and Apps] wtfdusk:
?

Is It possible for some one to bring this over to Fresh rom? This Is The bestest theme i've seen.
[Hero CDMA Themes and Apps] phinnaeus:
Yeah, still working on it. My hero was RUU'd to the 2.1 official .5 build and I spent all last night trying to root it and get a CM nightly on it for testing. It did not go well.

Anyway, with such adoring fans I suppose there really isn't that much need to test it myself, and I already know what to do if things break, so I've been working all day on getting the mdpi image elements ready. You guys have a slight advantage in that it doesn't take nearly as long to batch resize than it does to remake everything from scratch for a smaller screen :P
[Hero CDMA Themes and Apps] vincebb72:
Will this work with Darch rom?
[Hero CDMA Themes and Apps] PlagaDeRock:
I'm having issues getting the jog lock to match up evenly. Hopefully you can get it right lol. Thanks for the support for our heros. :)
[Hero CDMA Themes and Apps] atreyu954:
Does anyone know where I can get this background, I've been looking and can't find it.

I second that. I'm running 2.7 about to go to 2.8 tonight, and would love to use this on mine.
[Hero CDMA Themes and Apps] PlagaDeRock:
I'll post it in a minute. ;)

There you go.
[Hero CDMA Themes and Apps] daPorkchop:
Yes.

10chars
[Hero CDMA Themes and Apps] atreyu954:
Thank you Plagaderock
[Hero CDMA Themes and Apps] PlagaDeRock:
No problem.
[Hero CDMA Themes and Apps] barakisbrown:
2.2 Test2

Could we get it updated where it will work on future 2.2 version of CM6 for the hero?? I like the theme..:)
[Hero CDMA Themes and Apps] phinnaeus:
my port of it is made for cyanogen mod.
[Hero CDMA Themes and Apps] chomafin:
I'm also wondering if we can get this updated for the Hero CM6 Nightlies; Or the RC1? The Noobz & notmydog versons break things unfortunatly.

phinnaeus, This is a pretty awesome skin. Good work for sure.
[Hero CDMA Themes and Apps] phinnaeus:
When I finally get around to compiling it, yes, it will be built off of the cm6 nightlies. Hopefully I will be able to release sometime before .Ssaturday (when I go off to university).
[Hero CDMA Themes and Apps] PlagaDeRock:
Thanks for the extra love phinnaeus. :D
[HD2 General] nobisz:
Hello,

My configuration windows xp via us robotics router telephone network to hd2

My problem is following.

Remote Desktop Mobile on HD2 on local connection to windows xp via active sync - no problem.

Remote Desktop from Laptop via hd2 (working as modem to telephone network) to windows xp - no problem.

Remote Desktop Mobile on HD2 via telephone network no connection.

What could be the problem?

Nobisz
[HD2 General] cubalibre79:
are you using an internal ip address to connect? when you try to connect from the phone using the mobile connection you would need to use the external ip address of the remote desktop you are trying to reach, therefore opening ports is needed.

give us more details to be able to help.
[HD2 General] rp-x1:
Hi,

As cubalibre has said, you'll need to set it up so that your phone can talk to the computer from the outside world.

You'll need to log into your router (while you're at home) using the address:

http://192.168.1.1 (this is the standard I could find for US Robotics)

Once logged in, you'll need to find where you can add 'Port Forwarding' or edit the firewall in the settings to allow traffic through port 3389 to your computer's local IP address.
[HD2 General] nobisz:
i use the external ip and the forwarding is set i have also set the dmz. as wroten bevore it works from a laptop connected from internet only hd2 will not connect from internet
[HD2 General] nobisz:
please take a look at the pictures.

images47.fotosik.pl/321/f84345dc8269d99dmed.jpg

That works fine with local ip adres of the computer i like to connect.

images43.fotosik.pl/321/12a34835b9fd59b1med.jpp

Works fine, in RD address from external IP of the router in router port forwarding, acces to the forwarded computer.

images47.fotosik.pl/321/4786af86ac42a623med.jpg

No connection in the RD from HD2, in the RD of hd2 is the external IP address from router.

There is 1 point i dont understand, if i like to connect from external network from my laptop i need first to estabilish the vpn connection and then can i use the RD, maybe there is the problem, because hd2 don't supports VPN, how to connect to my network without vpn or how to estabilish vpn connection from hd2?
[HD2 General] FRANQ_23_PL:
There is many apps for that like RealVNC, freeware or payware. Search it in Google or test one from these (no one app is warez):

http://www.multiupload.com/7WN51D9TOS

or use Remote Desktop app - "RDM+": http://www.rdmplus.com/

Osobiście polecam RDM+ ale wersji z witaminką nie idzie znaleźć, więc jedyna opcja to... kupić.

Pozdrawiam

PS. A zdjęcia z fotosika wstawiaj w tagach
[EVO 4G Q&A, Help & Troubleshooting] firsttimer44:
2.0 just isn't cutting it for me, can I reflash back to 1.36?