Related
wm7 = no native API call, stop running of background program and many other controls
let say good bye appl like WKTASK, CPUMonitorMini and many others
we have to wait for official comments next month. however why switch to Android? The native API of WM 6.5.x will not expire on our devices. With it we can do whatever we want.
...
I can't see me now buying a wm7 device in the future and I defenitly switch to android if wm isn't supporting multitasking anymore.
The fact alone that wm7 won't be backward compatible let's me thing about switching.
Thats all really sad because my omnia 2 is actually my first smartphone and I'm very pleased with it, basically because it uses a desktop like os.
drandazzo said:
will the current WM6/6.5 applications work on WM7.. eg. TomTom?
Click to expand...
Click to collapse
No. No piece of WM6 software will work on WP7. Some pieces may be easier for the developers to convert to WP7 than others, but all will require code-level conversion and recompilation of some sort.
Personally I hope 6.5 apps DON'T work on WP7, it'll make developers lazy and not bother re-writing their apps for WP7.
We need a clean break and that means no backwards compatibility. I want all my WP7 apps to have the jazzy new UI, full touch control and full integration with the hubs.
I don't mind paying the devs some more cash for a WP7 version of their apps, and I'm sure they won't mind taking that money off me!
Jim Coleman said:
Personally I hope 6.5 apps DON'T work on WP7, it'll make developers lazy and not bother re-writing their apps for WP7.
We need a clean break and that means no backwards compatibility. I want all my WP7 apps to have the jazzy new UI, full touch control and full integration with the hubs.
I don't mind paying the devs some more cash for a WP7 version of their apps, and I'm sure they won't mind taking that money off me!
Click to expand...
Click to collapse
yeah when wp7 comes out thats when ill start buying my apps
Jim Coleman said:
Personally I hope 6.5 apps DON'T work on WP7, it'll make developers lazy and not bother re-writing their apps for WP7.
Click to expand...
Click to collapse
The majority of the apps I use right now have already a kool looking ui (a lot of freeware is skinable anyway) and are fingerfriendly. And this includes stuff that is no longer in development and won't get updated.
If a developer refuses to update its app than there is a opportunity for someone else the be successful with a better product.
So why can't ms just let the market decide who got the best ui or functionality?
And for hubs, I don't really care for the new ui and would continue to use mobile shell (if still possible).
Shasarak said:
No. No piece of WM6 software will work on WP7. Some pieces may be easier for the developers to convert to WP7 than others, but all will require code-level conversion and recompilation of some sort.
Click to expand...
Click to collapse
I dont see why tomtom or things like igo wouldnt work.
Microsoft said that backward compatiblilty will be difficult because of making it fit in with the OS, but if its full screen it doesnt need to fit in with any part of the os.
TheGoD said:
I ... would continue to use mobile shell (if still possible).
Click to expand...
Click to collapse
No it won't be possible.
loomx said:
I dont see why tomtom or things like igo wouldnt work.
Microsoft said that backward compatiblilty will be difficult because of making it fit in with the OS, but if its full screen it doesnt need to fit in with any part of the os.
Click to expand...
Click to collapse
Ah but you're missing the point. Tomtom, if written correctly within the new Silverlight framework doodad, will be largely subsumed into the Hubs interface - it'll provide new menu options in People, for instance, to navigate to their home or work address. In Calendar it'll do the same for the location of an event. Etc. Perhaps it'll calculate the route in background and then add it to a route list somewhere else on the phone, who knows. But it'll only go full screen with the 3D view etc when you're actually navigating. The rest of the UI will be done via the hubs.
Jim Coleman said:
Ah but you're missing the point. Tomtom, if written correctly within the new Silverlight framework doodad, will be largely subsumed into the Hubs interface - it'll provide new menu options in People, for instance, to navigate to their home or work address. In Calendar it'll do the same for the location of an event. Etc. Perhaps it'll calculate the route in background and then add it to a route list somewhere else on the phone, who knows. But it'll only go full screen with the 3D view etc when you're actually navigating. The rest of the UI will be done via the hubs.
Click to expand...
Click to collapse
Jim doesn't that sound ****ing awesome!?
in my opinion
winmo will be the best or the last
they have only one chance to make it the best mobile os or it will failed completly and all of us will move to android\iphone os
matckal said:
winmo will be the best or the last
they have only one chance to make it the best mobile os or it will failed completly and all of us will move to android\iphone os
Click to expand...
Click to collapse
Depends on what WP7 really will be in the end, I'll switch to it, or just keep my old one. No intentions to switch to anything else, so please don't make such weird assumptions! WM 6.5.x will still be supported for a while by MS, and will be even longer on this board, so I see no reason to jump at the next opportunity because it's now suddenly hip or what?
Im done with Wm for Now...
Im done had all can take my HD2 is up for sale just picked up my Nexus one and its overclocked to 1.3ghz So fast microsoft im done....
Android is the new WinMo.
Except crappier. The slowdowns on the Qualcomm 72** series on the Android is more profound than on Win Mo. Thats how it felt to me.
I've messed around with android and it just doesn't seem that appealing to me honestly. Even though they may be locking down the WP7 UI. I love the integration it's going to have with Xbox Live and Zune. Not to mention the menu systems look very slick to me. I'll be sticking with Microsoft and I guess we will just have to wait for a crack to install our own apps if that's how it's going to go down.
after the recent Apple vs. HTC patent issues I would no longer talk so easy about bright future of Android. We never know what happens.
RAMMANN said:
after the recent Apple vs. HTC patent issues I would no longer talk so easy about bright future of Android. We never know what happens.
Click to expand...
Click to collapse
I was going to say the same thing.
Android might have to get a complete faceleft and lose A LOT of functionality.
**** apple...
RAMMANN said:
after the recent Apple vs. HTC patent issues I would no longer talk so easy about bright future of Android. We never know what happens.
Click to expand...
Click to collapse
Ah, the future of Android has never been clear really. Not because the OS is bad or anything, but simply because Google doesn't really need it. That is, it's nice to have but it's not a life or death situation for them in this business. It's one of examples of their "let's throw all kinds of cool **** around and see later where it sticks" strategy. They pursue things that go easily and just as well abandon things that aren't going smooth - they just don't know where the money will come from, and don't mind that. Heck they didn't even know how to make money from their search business until they stole the context ad idea after unsuccessful attempts to buy it. But make no mistake - they are in business for the money. It doesn't mean they'll necessarily dump it, but it is an unclear and intransparent game.
So if I were an OEM I'd think a dozen times before really betting on Android, with or without the lawsuit. It's fine to use the opportunities it provides in the short run, but long term commitments? Nah.
Seeing as WP7 will be almost as crippled as the iPhone, let's see ways in which it will be better, besides replaceable battery and memory card(and it's not certain every OEM will follow up on those either). So far it has two weaknesses that only the iPhone has: Lack of multitasking and apps must go through the marketplace.
In order to pick up iPhone users it will have to offer some advantage that the average iPhoner will notice.
Some advantages:
Information at a glance a la today screen with the hubs. iPhone has nothing like this.
It will (supposedly) have some degree of multitasking.
Two more hardware buttons.
Its funny since I've had my HD2 I've not really used multitasking and when I had my iPhone only not being able to use Spotify in the background bugged me so maybe certainly for me multitasking isn't a be all and end all.
Having read lots of stuff about WP7S, the conclusion I have come to is this...
There will be two types of apps
1. Apps with no need to run in the background
2. Apps that do need to run in the background
Examples of type 1 are games, spreadsheets and word processors.
Examples of type 2 are IM apps like palringo, and music streaming services such as pandora.
What will happen is that when you develop an app, by default it will not have the rights to use the background APIs. In order to gain access to them and have an app run in the background, you'll need to ask Microsoft to provide the access and make it a type 2 app. Microsoft will only allow this if you can convince them it is necessary for the functioning of your app.
Type 1 apps will simply pause when the user switches away from them. They will remain in memory but will be unable to execute any code until the user switches back to them, whence they will resume execution. This will ensure the app cannot hog any CPU and cause the UI to stutter or slow down. This is definitely a good thing.
Type 2 apps are given access to particular APIs to allow them to, for instance, download updates or postings on IM systems. This will be strictly controlled and priority will always be given to the UI, again to ensure it remains smooth and responsive.
That's my take on what's going to happen, and we'll see if I'm right at MIX 2010 next month.
So your answer is - yes it will multitask but only when it is truly needed. Which to me is the best of both worlds. It will ensure a smooth user experience whilst still allowing background operations.
Jim Coleman said:
In order to gain access to them and have an app run in the background, you'll need to ask Microsoft to provide the access and make it a type 2 app. Microsoft will only allow this if you can convince them it is necessary for the functioning of your app.
Click to expand...
Click to collapse
Lets hope theyre not too stingy with giving out access to these API's!
The hubs/services (I'm not sure what MS is calling these) system looks good; getting new relative options available on multiple hubs just from installing a single app (like they demo'd with Facebook) should make all the apps work together much better than on an iPhone. I already want to try to make one to generate a music playlist based on past plays, and another to find lyrics to the currently playing song; If I understand the system properly, these would automatically integrate into any 3rd party apps using the appropriate media API's.
Also the context-sensitive search looks to be awesome.
One disadvantage: possible lack of native code execution and probably no OpenGL support - making it harder for iPhone app developers to port their existing apps to Windows Phone.
weesals said:
One disadvantage: possible lack of native code execution and probably no OpenGL support - making it harder for iPhone app developers to port their existing apps to Windows Phone.
Click to expand...
Click to collapse
why the heck should iPhone devs have an easy migration to WP7 if WM 6 devs don't?
weesals said:
Lets hope theyre not too stingy with giving out access to these API's!
Click to expand...
Click to collapse
The impression I'm getting so far is that they will be very stingy indeed. The only people who will ever get access to non-standard API's will be phone manufacturers and networks, and even they usually won't get access to the native API's most of the time. Microsoft will not publish any documentation about native API's. To get access to them the manufacturers will have to apply to Microsoft on a case by case basis. If Microsoft judges that a native API is required (and if there actually is one that might help) then only at that point will they release any information, and a condition of this is that they will vet the resulting piece of software to verify that the native API is being used correctly, and forbid the release of the software if it isn't.
What we don't know yet is where multi-tasking sits within all this. Is it a standard managed API, an extended managed API, or a native API?
why must every phone be compared to an iphone...personally I never liked the iphone, never will...only good thing about iphone is the apps..otherwise it sucks..and high end smartphones should not be compared to it!
The only thing I like about iPhone is how I use the virtual keyboard to type text.
I have tested HD2 and iPhone in a store, and from my own perspective, iPhone is more responsive and accurate compared to HD2.
I hope WP7 can be better than those 2 platforms in this task.
giggles33 said:
why must every phone be compared to an iphone...personally I never liked the iphone, never will...only good thing about iphone is the apps..otherwise it sucks..and high end smartphones should not be compared to it!
Click to expand...
Click to collapse
gogol said:
The only thing I like about iPhone is how I use the virtual keyboard to type text.
I have tested HD2 and iPhone in a store, and from my own perspective, iPhone is more responsive and accurate compared to HD2.
I hope WP7 can be better than those 2 platforms in this task.
Click to expand...
Click to collapse
that isnt aways based on the OS or software, but the quality of the touch screen.
Jim Coleman said:
Having read lots of stuff about WP7S, the conclusion I have come to is this...
Click to expand...
Click to collapse
This definitely seems like the best thing to do for multitasking in WP7.
We are going to need a task manager though...
As for comparing to the iPhone:
-WP7 will be available in different hardware configurations, giving the consumer a choice in the style and capability of their device.
-Xbox integration, which will most likely include Arcade games (ported for playability of touchscreens)
-Better hardware standards
-Not quite as locked down (hopefully)
RAMMANN said:
why the heck should iPhone devs have an easy migration to WP7 if WM 6 devs don't?
Click to expand...
Click to collapse
Because that's where the money is.
Seems people are struggling to come up with any, maybe something magical will appear in the next few weeks, although I doubt it, the advantages of WM seem like they will be gone with WP7, people on forums like this and blogs have been asking for a windows mobile iphone [without being an iphone] and it looks like they're going to heed the demand.
The most important advantages are gone.
They've made an exact copy and think it is enough. But it's not. When you try to catch up, you have to be better.
There's almost nothing WP7 is better at. It's an exact copy of iPhone OS with a better UI on top, but lacking the thousands of applications. That's not going to be enough and I really can't think about a reason why consumers and developers would be excited about this.
(and don't get me wrong - I LOVE the UI - it's just not enough)
Free Microsoft Office (Document viewing, creation, downloading, and editing)
Abobe Flash Player 10.1 is coming
File downloads (possibly)
Apps like a Wi-Fi router and file manager will likely come and be allowed
XBOX LIVE! Enough said.
Zune integration and support (I'm a Zune user)
1GHz Snapdragon is the processor minimum (This will lead to awesome apps and games)
WVGA display minimum (You might not care too much about this one, but I've seen the difference, and it's AMAZING!)
Bing search (That's just my preference.)
Contextual search (A handy feature, I suppose.)
There is not an app collection of 100,000 with most of which being totally useless. This means that you"ll be able to find the good apps.
Even if Microsoft won't allow apps like a Wi-Fi router and file manager, all we would need to do would be to get all WinPhone7 users on XDA to install the XNA Game Studio (and possibly the Win Phone7 SDK) and we could simply upload .ccgame files to XDA instead of .cab files.
giggles33 said:
why must every phone be compared to an iphone...personally I never liked the iphone, never will...only good thing about iphone is the apps..otherwise it sucks..and high end smartphones should not be compared to it!
Click to expand...
Click to collapse
I know! Why must smartphones always be compared to a simple feature phone! I've tried the iPhone/ iPod touch (3rd generation) at Best Buy stores, and, let's just say, they froze more and gave out more errors in 5 sec. than 5 WinMo devices did combined over the course of 2 hours. The iPhone's keyboard isn't too great either. It's (the errors thing) 100% true.
Jim Coleman said:
There will be two types of apps
1. Apps with no need to run in the background
2. Apps that do need to run in the background
Examples of type 1 are games, spreadsheets and word processors.
Examples of type 2 are IM apps like palringo, and music streaming services such as pandora.
What will happen is that when you develop an app, by default it will not have the rights to use the background APIs. In order to gain access to them and have an app run in the background, you'll need to ask Microsoft to provide the access and make it a type 2 app. Microsoft will only allow this if you can convince them it is necessary for the functioning of your app.
Type 1 apps will simply pause when the user switches away from them. They will remain in memory but will be unable to execute any code until the user switches back to them, whence they will resume execution. This will ensure the app cannot hog any CPU and cause the UI to stutter or slow down. This is definitely a good thing.
Type 2 apps are given access to particular APIs to allow them to, for instance, download updates or postings on IM systems. This will be strictly controlled and priority will always be given to the UI, again to ensure it remains smooth and responsive..
Click to expand...
Click to collapse
This is the right answer. Anybody who calms down would see that this makes sense. More Apple-like approval process for Type 2, free reign for Type 1
Shasarak said:
The impression I'm getting so far is that they will be very stingy indeed. The only people who will ever get access to non-standard API's will be phone manufacturers and networks, and even they usually won't get access to the native API's most of the time.
What we don't know yet is where multi-tasking sits within all this. Is it a standard managed API, an extended managed API, or a native API?
Click to expand...
Click to collapse
Yeah, you're talking about native vs managed stuff, which is not the same as simply allowing an app to have a background process. True, AT&T and HTC will have to apply to for native API use for stuff relating to making calls, etc, but that was only about OEMS and network operators.
Regular 3rd party guys, of which there are many, will be expected to get a way to do what they need on the device. Pandora we've seen in Music, you can expect apps like Palringo showing up in People
burnblue said:
This is the right answer. Anybody who calms down would see that this makes sense. More Apple-like approval process for Type 2, free reign for Type 1
Click to expand...
Click to collapse
Just because it makes sense doesn't mean Microsoft will act like that. In fact, I'm sure they will not.
The mass market will not benefit from every joe having all the API's because it's going make programs that cause glitches/crashes/memory leaks, etc. They are doing what they think is best for mass market and that is make sure things work well on the device and everything is user friendly with the least amount of hiccups possible. So that means more restrictions on us.
^^^ +1
Jim Coleman said:
What will happen is that when you develop an app, by default it will not have the rights to use the background APIs. In order to gain access to them and have an app run in the background, you'll need to ask Microsoft to provide the access and make it a type 2 app. Microsoft will only allow this if you can convince them it is necessary for the functioning of your app.
Type 1 apps will simply pause when the user switches away from them. They will remain in memory but will be unable to execute any code until the user switches back to them, whence they will resume execution. This will ensure the app cannot hog any CPU and cause the UI to stutter or slow down. This is definitely a good thing.
Type 2 apps are given access to particular APIs to allow them to, for instance, download updates or postings on IM systems. This will be strictly controlled and priority will always be given to the UI, again to ensure it remains smooth and responsive.
That's my take on what's going to happen, and we'll see if I'm right at MIX 2010 next month.
So your answer is - yes it will multitask but only when it is truly needed. Which to me is the best of both worlds. It will ensure a smooth user experience whilst still allowing background operations.
Click to expand...
Click to collapse
This neither solves problems nor guarantees anything though. Poor code is still poor code. Too many apps running is STILL too many apps running (slows the UI). MS can police neither. So, your #2 solution really makes no sense and has no advantages. MS has no way of predicting who will run what app and when on their phones. What if a user chooses to run several "Type 2" apps? Will you get some sort of error message? Will the MS police arrest you for ruining the UI experience? What happens after several years of approved type 2 apps hitting the market? Now were back to the same problems of WM.
Dude, we're talking about 1Ghz+, 512MB+ RAM phones here! You can run lots of apps without slowing anything down. Really, the "multitasking slows down the UI" argument is utter bull****. A good OS handles multitasking in a way that doesn't slow down anything. Restrictions are only necessary if the OS itself sucks. A good OS doesn't need them.
Hey!
So I want to buy the HTC Mozart, but I am not quite sure, because if there is no good community it wont be worth the money. So does anyone know if somebody is working on a root or jailbreak for wp7?
It would make the platform even greater
Thanks in advance!
People are working on it. I'd be surprised if there isn't a jailbreak available in 3 months after it is released.
Ok thanks I am just interested as the beta was already available and the roms have leaked in the htc Mozart category.
To general!
~~Tito~~
the windows mobile community is the reason this message board exists. I wouldn't worry.
Sent from my Dell Streak using XDA App
Made2Last said:
the windows mobile community is the reason this message board exists. I wouldn't worry.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
This ^
Also, XDA calls "root or jailbreak" for WM "HardSPL"
ericc191 said:
This ^
Also, XDA calls "root or jailbreak" for WM "HardSPL"
Click to expand...
Click to collapse
"HardSPL" is a bootloader that allows custom Windows ROMs - like flashing to BIOS in your PC to a 3rd party version
Windows doesn't have the concept of a "root or jailbreak" because there is no root account or Jail Shell.
ericc191 said:
This ^
Also, XDA calls "root or jailbreak" for WM "HardSPL"
Click to expand...
Click to collapse
WM (Windows Mobile) is not equivalent to WP or (Windows Phone) Windows Mobile is the past, Windows Phone is Microsoft moving forward. I think they might actually have something with this new OS
Mhh interesting Thanks!
I tested the OS and it feels great, like my iphone 2g at first and after JB i noticed that it is crap without JB XD so just wondering ^^
~~Tito~~ said:
To general!
~~Tito~~
Click to expand...
Click to collapse
Again To general.
This just discusses WP7, it does not contribute anything developmental wise, just discussion wise .
~~Tito~~
I don't see much of a point in jailbreaking, because there's absolutely squat in regards to API documentation of Iris UIX. No one will be able to write up alternates to the system components.
The only thing that'll make sense right now is unbrand phones, to get carriers out of the loop in regards of updates.
Some of these people think wp7 is ios with a new skin. Let them keep asking about this, Lol.
Sent from my SGH-T959 using XDA App
N8ter said:
Some of these people think wp7 is ios with a new skin. Let them keep asking about this, Lol.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I do not think that this is IOS with a skin!!
I just wanted to know if something like jb or root will come!
Not JB per se but only the concept of being able to do stuff MS doesnt want to!
@Tom Servo
I am not sure but isnt it running on a silverlight platform so it would be rather easy to develop different apps?
A large part of the base system, especially UI, is .NET code but uses a different framework called Iris UIX. It's a descendant of the MCE graphics framework, and also used in the Zune desktop software.
Third party applications are forced to use Silverlight instead.
That's also why there's a disconnect between UI features and performance between the first party and third party apps.
Tom Servo said:
A large part of the base system, especially UI, is .NET code but uses a different framework called Iris UIX. It's a descendant of the MCE graphics framework, and also used in the Zune desktop software.
Third party applications are forced to use Silverlight instead.
That's also why there's a disconnect between UI features and performance between the first party and third party apps.
Click to expand...
Click to collapse
Oh ok thanks!
Now thats kinda stupid from them.....
A long time ago, they hired more developers to work on UIX. Seems like they were more occupied porting it to mobile devices than documenting it and prepping it for general release, or something.
I still hope that it'll be made public at some point in time. It seems to be a way better solution than WPF, judging both the phones and the Zune software, even tho the majority of it is still .NET. Maybe a little less flexible, tho. Seems like some teams over at Microsoft went like "**** it, this is overengineered slow crap" and continued to work on MCML, which turned into UIX.
WPF was on the table long before the flashy Zune client ever came to be, which is also mostly .NET. That tells you something.
Tom Servo said:
I don't see much of a point in jailbreaking, because there's absolutely squat in regards to API documentation of Iris UIX. No one will be able to write up alternates to the system components.
Click to expand...
Click to collapse
How about enabling PInvoke, getting the same access to native WinCE APIs OEMs have? Getting access to filesystem, sideloading, tethering, you name it.
Tom Servo said:
A long time ago, they hired more developers to work on UIX. Seems like they were more occupied porting it to mobile devices than documenting it and prepping it for general release, or something.
I still hope that it'll be made public at some point in time. It seems to be a way better solution than WPF, judging both the phones and the Zune software, even tho the majority of it is still .NET. Maybe a little less flexible, tho. Seems like some teams over at Microsoft went like "**** it, this is overengineered slow crap" and continued to work on MCML, which turned into UIX.
WPF was on the table long before the flashy Zune client ever came to be, which is also mostly .NET. That tells you something.
Click to expand...
Click to collapse
Thanks a lot! I just saw the app you created looks interessting
Is it in the market yet?
So as you develop such apps i have to ask you:
Do you think the problems you mentioned can be overcome like MS says.
Like in one or two months?
Or would you say that the market will not evolve as much as apple and android?
vangrieg said:
How about enabling PInvoke, getting the same access to native WinCE APIs OEMs have? Getting access to filesystem, sideloading, tethering, you name it.
Click to expand...
Click to collapse
My reason exactly!
vangrieg said:
How about enabling PInvoke, getting the same access to native WinCE APIs OEMs have? Getting access to filesystem, sideloading, tethering, you name it.
Click to expand...
Click to collapse
Microsoft doesnt allow native code for 3rd parties, amd pretty much said they'll keep it that way. I doubt WP7 will support unsafe code for 3rd parties. It's too obvious a workaround...
Sent from my SGH-T959 using XDA App
I for one would like to see one of this on the WP7 platform. What are your thoughts?
I hate to say it, but I don't think we will ever see any emulation programs on WP7 until we are allowed to side load data. I doubt Zune would allow loading of roms therefore the program would be useless. This is also assuming Microsoft lets these programs on the market. The emulation/rom market is mostly piracy and Microsoft likely wants no part of that.
I'd love to have a good snes emulator but i just can't see it happening.
if it does itll only be for unlocked devices....
It's definitely possible. Silverlight is powerful enought to emulate code (see here for example). However, the version of silverlight / XNA currently built into WP7 may not be up to the task just yet. But full silverlight support is due to be integrated in upcoming updates.
EDIT: SNES Silverlight Emulator too
Legally speaking though there's little or no chance that an emulator would be allowed on the marketplace. Although MS are open enough with their Marketplace (eg allowing a Kamasutra app and many uTorrent remote clients), emulators need roms and roms are usually copyrighted.
What we will see eventually are emulators that can be sideloaded using Chevron or similar tools, or possibly via a future alternative Marketplace like Cydia. The roms themselves, due to isolated storage in WP7, will need to be loaded from your PC using a Zune Desktop-style tool, or alternatively downloaded from the emulator app itself (eg from a private webserver over Wifi).
It's all definitely possible, there are just a few steps to go first
lyriquidperfection said:
I for one would like to see one of this on the WP7 platform. What are your thoughts?
Click to expand...
Click to collapse
i would love to have sega alongside my nes on wp7 !!!
Oh MAN I hope so.
Shadowrun on on my phone would be beyond incredible.
not going to happen as long as MS tries to pretend to be "moral" about copyright infringement...
I don't mean to necro this thread, but I figured it'd be better than creating a new one.
I've seen NES and Gameboy emulators around, but I've still got my fingers crossed for Master System, Game Gear and (dare I dream?) Genesis/Mega Drive.
I just hope that someone out there is thinking about making these. I, for one, would be eternally grateful.
I am not talking about sideloading. Android and iOS are hacked within weeks if not days of being released. WP7 has been out for a while and it seems there hasn't been any major progress in this front.
Anyone know why this is? Has MS made WP7 THAT secure that even xda can't break into it?
digger1985 said:
I am not talking about sideloading. Android and iOS are hacked within weeks if not days of being released. WP7 has been out for a while and it seems there hasn't been any major progress in this front.
Anyone know why this is? Has MS made WP7 THAT secure that even xda can't break into it?
Click to expand...
Click to collapse
If you're not talking about sideloading, what are you talking about? The primary modes of "hacking" iOS and Android involve sideloading homebrew apps that do different stuff, which is already happening on WP7.
I was mostly talking about system modifications. Where are utilities like quick toggles for the settings and such? Or for example having folders in the app list. These were added pretty quickly when iOS was jailbroken I believe.
digger1985 said:
I was mostly talking about system modifications. Where are utilities like quick toggles for the settings and such? Or for example having folders in the app list. These were added pretty quickly when iOS was jailbroken I believe.
Click to expand...
Click to collapse
Awaiting the proper APIs
Hmm... I was under the impression that the APIs were there but just not available to the devs. Cracking open WP7 was meant to solve this right?
digger1985 said:
Hmm... I was under the impression that the APIs were there but just not available to the devs. Cracking open WP7 was meant to solve this right?
Click to expand...
Click to collapse
Not really. Devs have no access to native APIs and the access they have managed to gain is still sandboxed to restrict what they can do with the phone.
You could still crack open WP7 without access to native APIs, but it makes it more unlikely that anybody will. When devs have access to native APIs, there is more of a chance that somebody has overlooked a method of gaining access to the phone's features.
I'm not 100%, but I'm pretty sure iPhone did not have a native API available when it was jailbroken. Android is mostly open source, so it's pretty much already jailbroken
Just to mention, i was today able to get full root control of running processes on the current phone (phone sided code). And some api's that are hidden by microsoft can easily be reloaded with "LoadLibrary" and "GetProcAddress" like enumerate running processes. (Look under wp7>hacking>dllimport).
its coming...very soon
Why is it taking so long for WP7 to be fully "cracked" open?
Click to expand...
Click to collapse
Microsoft developers are not amatuers, and TBQH I hope it never is. They need to shut down homebrew IMO, or certainly not facilitate it. All it does it lead to issues and I don't think Microsoft wants the solution to issues to be "go to XDA" or "flash CustomROM_01."
Android is a mess because of all that ****.
How long it took for the first iPhone JB?
fiinix said:
Just to mention, i was today able to get full root control of running processes on the current phone (phone sided code). And some api's that are hidden by microsoft can easily be reloaded with "LoadLibrary" and "GetProcAddress" like enumerate running processes. (Look under wp7>hacking>dllimport).
Click to expand...
Click to collapse
Wait-Are you saying you have the ability to run and exit processes from another application on the device?
Edit: Never mind, found your thread here. Just gave me an idea, nice work!
http://forum.xda-developers.com/showthread.php?t=1006331