I updated the opening post with two important notes, regarding error 0x81030120 and the crash in HKLM\Microsoft\Software.
Heathcliff74
Note 1: I was under the assumption that it was possible to side-load this app on devices with Mango pre-loaded on it. Unfortunately this does not seem to be true. If you unlock your device with a legit dev-unlock you still can't side-load apps with ID_CAP_INTEROPSERVICES. The reported error-code is 0x81030120. This is a big disappointment and I'm looking into the issue and see if there is a way to get around it and side-load on Mango. Currently the only known work-around has been tested by contable and Marvin_S. You have to be on NoDo and then load and Unlock.xml in the \ProvXml folder. After upgrading to Mango, you can use the GPRS settings in the Diagnostics app to apply these settings and unlock your device. The setting that makes the difference is MaxUnsignedApp=0x7FFFFFFF. It does not seem logical, but it seems that this setting will allow you to side-load apps with native code. So far this is the only possibility to apply this setting. When I find more on this issue I will report on that.
I can't test it now but maybe you could use the samsung regedit to change that .reg (MaxUnsignedApp=0x7FFFFFFF) ?
and then sideload your app , its just an idea so maybe another could test it
(samregedit attached to this post)
Ow and @heatcliff: transfering files is a lot easier on mango, since you just have to copy them to the iso storage of root tools and than run WP Power Tools to download them. Maybe you can make a folder in root tools iso storage and a menu option to copy to iso storage for easy transfer to the pc. No need for a file server or anything.
Here some feedback:
1. speed is very good => browsing the windows folder is much faster than with touchxplorer on my HD7
2. after renaming or deleting a file there is no refresh of the folder
3. multiple file operations are still missing (you pointed that out on post #1)
=> e.g. would make life much easier if you want to copy files to the windows folder
4. a search function like touchxplorer has would be great
=> e.g. *.xap will list all xap files in a folder
Any chance of a cheeky estimate of when HTC version will be out?
Note 1: I was under the assumption that it was possible to side-load this app on devices with Mango pre-loaded on it. Unfortunately this does not seem to be true. If you unlock your device with a legit dev-unlock you still can't side-load apps with ID_CAP_INTEROPSERVICES. The reported error-code is 0x81030120. This is a big disappointment and I'm looking into the issue and see if there is a way to get around it and side-load on Mango.
On the one hand, that's a reasonable and appealing conclusion.I was just thinking how it is odd that the max unsigned apps hack enabled native code to run then I remembered how MS said they would work with the Chevron guys for homebrew in mango and then it hit me, this isn't a glitch or oddity MS did this on purpose. I have a feeling that once the new Chevron unlock for mango comes out all the factory Mango headsets will be able to run native code via Chevron again, something they must have come to some sort of agreement on... We will just have to pony up the couple $$ needed to Chevron unlock the phone and we will be good to go.
2. I can't reproduce that behavior. Anyone else experiencing this? Can you give a path/filename where this happens?
Ciao,
Heathcliff74
Great background info! "Interop-unlocked" is a good term for it on Mango. I hadn't realized it was the MaxUnsignedApps key; I thought it was the Prevent Relock one. Interesting... though you still want Prevent Relock or the phone will reset MaxUnsignedApps periodically. Of course, I'm now wondering if that reset functionality can be exploited (via a proxy, for example) to instead apply interop-unlock to devices that don't have it.I updated the opening post with a lot more background info.
Ciao,
Heathlciff74
I was just thinking how it is odd that the max unsigned apps hack enabled native code to run then I remembered how MS said they would work with the Chevron guys for homebrew in mango and then it hit me, this isn't a glitch or oddity MS did this on purpose. I have a feeling that once the new Chevron unlock for mango comes out all the factory Mango headsets will be able to run native code via Chevron again, something they must have come to some sort of agreement on... We will just have to pony up the couple $$ needed to Chevron unlock the phone and we will be good to go.
Great background info! "Interop-unlocked" is a good term for it on Mango. I hadn't realized it was the MaxUnsignedApps key; I thought it was the Prevent Relock one. Interesting... though you still want Prevent Relock or the phone will reset MaxUnsignedApps periodically. Of course, I'm now wondering if that reset functionality can be exploited (via a proxy, for example) to instead apply interop-unlock to devices that don't have it.
One small typo though: "the ChevronWP7 team will release an unlock-method that will only cost a few bugs ..."
LOL! Typo corrected.
The proxy won't work. The original Chevron unlock tool works like a proxy. It spoofs the developer registration server. In NoDo this was not possible anymore because the certificate for the https server is specifically verified against a root authority. This means the server can't be spoofed anymore, unless you add your own server certificate in the CA store of the phone. This can be done with WP7 Root Tools, but you have WP7 Root Tools running there is no need to unlock anymore.
Ciao,
Heathcliff74
Has anyone downloaded the xap since these notifications have begun appearing? It would be highly irresponsible to allow a xap to be available for download when that xap has expired. It should be removed immediately. I have pm'd the dev and expressed my concern that there was no warning about this ever happening (that I can easily find) and this could have been handled in many other ways other than executing code on our phones that affects a working app. I love his apps and will continue to use them but this was no way to handle this situation. He could merely have said that version .7 Alpha would no longer be supported (don't ask me anymore questions, I will not be monitoring this thread etc.) and that it needed to be uninstalled prior to the installation of the new version (if he was concerned about the upgrade process).
JamesAllen said:I use several of your xaps, specifically because you developed them and I find your efforts useful and stable. I am 63 years old and have been in the business of supporting "bleeding edge" software releases for over 40 years. What you have done with the alpha .7 release is not standard practice by any means. You effectively reached into my device and removed the use of software without any notice. This is hardly standard or acceptable. You could have;
1. Provided a notice that did not require a search to find it,
2. Offered some information about a replacement,
3. Ideally, people should have been made aware of this from the onset.
There was no reason to do this, even if you knew a replacement would not overwrite the installed alpha version. You could have merely let people know they had to deinstall the alpha version and that the alpha version would no longer be supported.
Just offering some advice, the damage to trust and credibility is already done, IMHO. I will still use your xaps with enthusiasm, but what you did here with .7 alpha version has made me pause a bit.