Related
Really? I liked downloading and keeping CABs.
Yes you have to use the marketplace. I think the market saves all of your downloads for you.
Yeah but it's not the same is it?
If something is no longer available for WinMo 6.x, but if you have an old CAB you're ok. This new model takes the power from us and gives it to the vendors. This isn't in my interest at all.
at45 said:
This isn't in my interest at all.
Click to expand...
Click to collapse
I don't agree, at least in my experience it has been much easier to get my applications back with the MS store than with CABs for several reasons. After I flash a new ROM (analogous to a new phone, etc.):
I simply log in to get my store applications - 1 button push to 'install all'
I get the latest version
I don't forget which CABs I have to install, and don't have to make sure they're all up to date.
It's a trade-off, but it is in your interest.
I guess that's ok if you trust the apps to remain available.
I don't have to do much work either though after a hard reset or new ROM. I just run Sashimi which configures every part of the phone exactly how I told it to. I know this is a mile from what MS is doing with WP7 and that's not a bad thing.
But I am hopeful that devs will find a way to let us install apps independently of Marketplace. It might be that someone writes a great app that MS doesn't allow onto the marketplace, mightn't it?
I too am not a fan of the fact that MS gets to dictates which software I can and cannot use. Whilst I consider them to be far more liberal than Apple how can I be sure that what is permitted today will be allowed tomorrow.
It is conceivable that something I download today is retrospectively deemed to be in violation of some hitherto non existent rule- this could be the result of a legal ruling or MS regime change.
Nor am I comfortable about the fact that one firm will have the low down on ALL of the software that I buy.
Whilst i can see some advantages to the market place, what happens if I need to hard reset in an area with no internet access? Or if I am abroad?
An advantage of the cab scenario is that I am only reliant on my sd card. I can carry my backups wherever I go and reinstall at no cost and virtually instantly.
Straying off topic, perhaps, the success of yet another o/s orientated market place might have very serious implications for the way that we source software for our main computers...
whilst that may be true that it is nice to have cabs you can install yourself, the reason for just 1 market place is the fact that you'll end up with experiences like android where multiple market places exist and carriers are changing the market place so you can't access another. and then it's up to the developer to make it available in all these variations of market places. where as at least with iOS/WP market places, it's a 1 place submission.
you also get stupid conditions as well such as amazon's (future?) android marketplace where no app can be released before them in an update. they must be released all at the same time. how hard is that to co-ordinate?
clean thread.
I believe the answer was given. closed Thread.
now the wp7 is jailbrocken we are able to install apps but where can we get some ...and how do we install apps ?
well i've found out that you can deploy apps from visual basic express for windows phone directly to your phone when it's unlocked.
so if some of the app developers can upload their apps as a visual basic project you can deploy it to your phone.
Yesterday i've downloaded some apps from the apps hub of MS and deployed it to my phone.
Just for testing purpose but they work
Now it's time for me to learn to create programs, but i don't know what to create
i''ve made the standard apps from visual basic express, but they aren't very usefull...
The chevronwp7 tool has 2 purposes and not the third...
1. For developers to test their apps without needing to pay the developer fee, this is more beneficial for those regions that don't yet have a way to pay for a developer account, but want to start working on it anyways
2. For apps that may use native code which won't get into market place, and in this case they can provide the xap which you can deploy.
In these two and all other cases, no developer in their right mind would hand out their intellectual property (their source code) unless they were doing it for others to learn from. Especially with a paid application, why would they give the source code out when it is in the market place?
The creators of chevronwp7 have already stated that this will not help in loading paid apps from market place either.
Hope this clears things up for you.
I have no intention to "steal" apps from their developers.
I just want to create my own programs, and learn from others.
There are dozens of free apps in the marketplace, and there were plenty of developers in the time of wm 6.5 which were programming for fun, and release their apps here on XDA so others can benefit from.
I think when time goes by these developers will release their apps here, because of the fee MS charges for developers to release the apps on marketplace.
So if your app is free, why not release the xap? No hassle with marketplace and native codes, and people who aren't interested in the code won't even think to look at the code.
I hope I made my point clear, it's not to install paid apps for free, but to help the developers who don't have acces to marketplace.
yea, which was it's original intent which is good. though given that chevronWP7 has now been taken down by it's creators we have to wait and see as to what they're doing with MS. MS has started negotiations with them to try and encourage the homebrew. lets see what happens of it all.
mtem1985 said:
well i've found out that you can deploy apps from visual basic express for windows phone directly to your phone when it's unlocked.
so if some of the app developers can upload their apps as a visual basic project you can deploy it to your phone.
Yesterday i've downloaded some apps from the apps hub of MS and deployed it to my phone.
Just for testing purpose but they work
Now it's time for me to learn to create programs, but i don't know what to create
i''ve made the standard apps from visual basic express, but they aren't very usefull...
Click to expand...
Click to collapse
I'm sure developers will release commercial apps in source form Even *most* free app developers won't do it, because of the way others like to copy code and create redundant apps. That has never been a popular trend on any mobile OS, and I don't see it becoming such.
@ OP: The unlock that came out for WP7 is not a jailbreak. It does nothing but allow you to use you device to test and deploy applications, instead of the emulator.
Hello everybody,
I got a WP7 Samsung Focus and I want to port my old application to this device and join native forces for WP7
My plan is simple: I'll convert my app into a dll, rewrite new gui in C# (or whatever the way to do it on WP7). I saw multiple posts about calling native code (original from Cris Walsh: http://goo.gl/2Tjks). Then I saw a few posts mentioning that it's impossible etc etc.
So, a few questions:
0) can I do it for my app (I don't need marketplace exams etc, I don't care for that)? I know that some WinAPI could be unavailable/broken, all I ask at this point if it's possible to load and run native dll without changing or re-flashing ROM.
1) ms wants 100$ out of my pocket to be able to deploy to my own device (WTF?!). What can I do to deploy to my phone without paying the crooks? (VS2010 tell me to register there and registration askes for 100$).
2) Is there a sample project I could D/L and run, I have zero experience in C# and I have no idea how to load and call native DLL from managed code in WP7? All these half broken samples are totally useless to me, I simply wanted to working HelloWorld app that loads and runs simple dll.
thanks
0) Yes, what you describe is possible. There are lots of limits, though - WP7 applications have very low permissions, and calling native code doesn't fix that. Unless you need to edit something outside the app's own iolated storage, though, you're probably OK.
1) Aside from the official marketplace account ($100), there are a few options:
a) if you've got an LG phone, they come with a built-in registry editor that can be used to dev-unlock your phone. I forget the exact key you need, though.
b) if you've got a student email address (ends in .edu) you can try registering through DreamSpark. This is free.
c) if you don't mind rolling back to pre-NoDo (7004 or 7008) you can use ChevronWP7 Unlock (instructions available on this forum). If you don't have a restore point that far back you can flash an official ROM for that version.
d) if you don't mind waiting, ChevronWP7 Labs will be available at some point (no ETA that I've seen, but it's been talked about for months) and will provide dev-unlock (but not marketplace account) for a nominal fee.
2) There are lots of apps distributed with source, and most of them will use some native code. You could do a search on this forum for subject lines including the tag "[SOURCE]" and find several (I release source for all my apps). However, I suspect what you'd find most useful is Heathcliff74's guide to WP7 apps that use native code, which is on this forum at http://forum.xda-developers.com/showthread.php?t=1299134. It includes step-by-step instructions.
Hope that helps! I look forward to seeing your app. Also, don't hesitate to ask for help with the actual development; I suck at GUIs and Silverlight but am fairly proficient at C# if you need somebody who knows that language, for example.
There is an ETA for the new ChevronWP7 unlocker:only a few weeks away from launch!
Hi GoodDayToDie
GoodDayToDie said:
0) Yes, what you describe is possible. There are lots of limits, though - WP7 applications have very low permissions, and calling native code doesn't fix that. Unless you need to edit something outside the app's own iolated storage, though, you're probably OK.
Click to expand...
Click to collapse
At this point I want to make a DLL from my simple app and call a few functions that interact with filesystem and network. FS is needed only for simple stuff (loading config file etc) from installation folder and creating some temporary files for local storage. Network is tcp/udp, I guess network should be available.
GoodDayToDie said:
1) Aside from the official marketplace account ($100), there are a few options:
...
Click to expand...
Click to collapse
I did some search, it seem that I've done that part. Chevron dev unlock was pulled out from their site, but the old version remains scattered all over the board. There is a good thread a good thread on how to do it. It happens that my phone is 7004. Where can I get old ROM in case if something goes bad and I need to re-flash? Is it easy, am I risking to brick and loose my phone?
I just tried to run sample phone app and it runs on the phone. Initially it said that it was revoked by MS, I run dev-unlock one more time and now it works.
GoodDayToDie said:
2) There are lots of apps distributed with source, and most of them will use some native code. You could do a search on this forum for subject lines including the tag "[SOURCE]" and find several (I release source for all my apps). However, I suspect what you'd find most useful is Heathcliff74's guide to WP7 apps that use native code, which is on this forum at http://forum.xda-developers.com/showthread.php?t=1299134. It includes step-by-step instructions.
Click to expand...
Click to collapse
I'll try to search, hope I'll be up and running soon. Too bad WP7 is DOA. They always had much better tools than all these ghetto Symbian/Android/Xcode crapware tools... WTF is wrong with these guys, at the point when they were surpassed at speed of light by newbies iPhone and Android they made some backward steps to cut off most of the devs (but they added all these 500K Silverlight newbie devs...). I'm so disappointed with Android, seems like they hired all these retards who were fired at symbian: same **** tools
I downloaded a few samples and it seems that all of them contain prebuild dll's and all of them are COM dlls or something like that.
What I'd like to find is simple sample that contains src code to native WinMo dll and C# project that it uses.
As far as I know native dll cannot be build with latest tools (am I right?), but I can use cegcc or VS2008 to build native DLL's.
stuff like:
Code:
if (ComBridge.RegisterComDll("ComFileRw.dll", new Guid("EEA7F43B-A32D-4767-9AE7-9E53DA197455")) != 0)
is totally unknown to me. I would really like to avoid to even elarning anything about COM related stuff. I prefer not to mess up with code that isn't portable.
HI mtlgui,
unless Heathcliff finishes his WP7 Root Tools SDK, you don't have any other way to access native c++ code besides using COM. DFT (The DarkForcesTeam) released a firmware loader, that allows you to flash customized unsigned firmware. They were also able to do some native c++ coding with the WM API. However the used firmware for that is not public and it is limited to HTC devices.
Did you already consider to write your application in c#? Mango has now TCP/UDP socket support for outgoing connections. Incoming connections or services running on the phone aren't possible without using native code, at least for the moment.
Hi rudelm,
if the only way to use native is to build COM dll, then I'm OK with that. My app code is old and I'd rather throw my WP7 device to trash can than trying to rewrite my app in C#.
Eventually, down the road while hacking maybe I'll learn c# well enough to do anything with it other than GUI and calling native/COM dlls.
So, just to confirm my understanding. I need to write COM dlls that access native API (socket, filesystem, wavein/waveout etc) and then load these COM dlls and call their functions from C# (or whatever is the closest lang to c/c++ in the WP7 world).
@mtlgui:
You've pretty much got it. A few thoughts, though:
There is a webserver project available on this site. It includes source for its C++ native component (the library is called NativeIO; I can probably send you the source if you can't find it). It exposes registry, filesystem, and TCP server and client sockets to COM. Note that because this library was built for pre-Mango phones, just compiling it and shipping it may not work on Mango phones as many deprecated libraries were removed in Mango and if the DLL contains any references to them, it won't load.
Generally speaking, what you're asking for with TCP/UDP is possible, though you may have to code against the winsock API directly. It sounds like you're doing as little as possible with C#, so even if the Socket API that is available with Mango were sufficient for your app's needs, you wouldn't be using it.
Filesystem access... even if you have read access to your app's install folder (I haven't checked, though you should), you almost certainly won't have write access. Each app does have a writable "isolated storage" though, under \Applications\Data\{GUID}\Data\IsolatedStore\. I've only ever tried writing to it using C# though, so I don't know for sure if it's writable using the native APIs directly (should be, though).
It's probably perfectly OK to write your app as one big native DLL (hell, it *might* work to just change the build type from Application to Library, then rename main() or something like that). You will need to expose the library to COM, but that's easy. You can then write a very simple C#/Silverlight app (see Heathcliff's instructions, or just post the COM interface and soembody could write it for you). All the C# app needs to do is use ComBridge to access the native DLL, and call a "run()" function or something similarly simple.
For what it's worth, C# is very close to a superset of C++, at least on the desktop. The phone version is crippled a little by not allowing the use of pointers - everything has to be done with strongly-typed references instead, which can make network code a little annoying but is otherwise rarely a problem - but with a little experimentation you may find your disdain for C# to be misguided. It's a useful language to know it today's job market, if nothing else.
Why is your phone still on 7004? That's the launch retail build, something like eight months out of date. On the plus side, this means that things like ChevronWP7 Unlocker still work for you, as you found. On the minu side, it means you're putting up with bugs and missing features that you needn't be. Have you tried updating at all? If/when you do update, make sure to back up the restore points that the Zune software generates (they got in %localappdata%\Microsoft\Windows Phone Update\). That way, if you ever need to roll back to 7004, you can do it. Normally, only the most recent restore point is kept.
Flashing ROMs is safe so long as you don't try something like flashing the wrong one for your device. Unless your bootloader is unlocked (only possible on HTC), you can only flash official ROMs anyhow, which saves you from most of the risks. On the other hand, you're already on as old a ROM as you will find, and so long as you keep your restore points, you can return to it any time you want to, easily.
I'm googling now the board to find NativeIO and that webserver app. So far only references to it, but no src code.
I'm ok with isolated read/write access. All I care is persistent fs storage.
My phone is still 7004 because I just bought it so I can do some WP7 development. I don't want to mess up with updates at the moment.
As I understand from another post ComBridge is C#->COM->native c++ dll or any other dll that can be used, right? I'm just learning some COM to learn enough to start actually programming for the phone. I see that I can pass whatever data I want, but I don't seem to be able to see a way to register callbacks so that native/COM could call back to C#
mtlgui said:
I'm googling now the board to find NativeIO and that webserver app. So far only references to it, but no src code.
I'm ok with isolated read/write access. All I care is persistent fs storage.
My phone is still 7004 because I just bought it so I can do some WP7 development. I don't want to mess up with updates at the moment.
As I understand from another post ComBridge is C#->COM->native c++ dll or any other dll that can be used, right? I'm just learning some COM to learn enough to start actually programming for the phone. I see that I can pass whatever data I want, but I don't seem to be able to see a way to register callbacks so that native/COM could call back to C#
Click to expand...
Click to collapse
Basic introduction to native code and COM, including references to more background info: http://forum.xda-developers.com/showthread.php?t=1299134.
Callback from C++ -> COM -> C# can be done. Decompile the WP7 Acrobat Reader app. You'll see how it works.
Ciao,
Heathcliff74
Hi hackers!
Found something pretty cool while I was digging around looking for new interop-unlock hacks. The bad news is that it looks like it's not usable for interop unlock, the good news is that it's still pretty cool.
This previously required a dev-unlock, but no longer does. It does not require interop-unlock. It works on all phones (as far as I know).
UPDATE 3: ZIP file usable on non-unlocked phones EDIT: I think this will not work on most phones. Sorry! The XAPs still work, if you can sideload them
I've added a ZIP file that can be used to switch the OEM Marketplace without needing to sideload a XAP at all. Instructions are inside, but basically you tap the XML file for the OEM you want, then reboot the phone.
UPDATE 2: Dell Apps.xap, Nokia Apps.xap (v2)
The Dell apps collection is hidden, like the Nokia one was (see Update 1 below). The only app I was able to find was "Newsroom" (another app kind of like HTC Hub). If there are others, please let me know and I'll try to find them.
Nokia has collected their apps into a single marketplace section, like HTC/Samsung/LG. The new Nokia Apps.xap reflects this, so disregard the Update 1 note below for Nokia, and download the new XAP!
UPDATE 1: Nokia Apps.xap (See the Update 2 note - Nokia Apps.xap has been changed)
Be aware that this app works a little differently. Rather than actually adding a "Nokia" store to your Marketplace list, it just enables your phone to access Nokia's apps though the normal marketplace. Not sure why some OEMs did their own store and others didn't, but that's why it wasn't working before (it isn't a stand-alone store section).
An easy way to find the Nokia apps is to do a seach for a well-known app, like Nokia Maps. Then, open it and tap the "More from Nokia Corporation" link. This will take you to a list of all of Nokia's apps.
WHAT IS IT?
Install a XAP or tap an XML file in the ZIP, and restart your phone. Then, open the marketplace, and you'll discover that, instead of "HTC Apps" or "Samsung Zone" or whatever your default is, you can install OEM apps from a different OEM.
WHAT CAN I DO?
If you want to install Nokia, HTC, Samsung, LG, or Dell apps, open the ZIP file on your phone, look for the OEM name you want, and tap the XML file immediately under that OEM name. You'll need to restart your phone before the Marketplace changes.
If you want to help out, give me as much info as you can about the other OEM marketplaces (Toshiba/Fujitsu, perhaps?)
IS IT DANGEROUS?
Well, it's a hack. There's always *some* danger. However, you don't need to worry very much. The phone will automatically revert the Marketplace after a day or so. You can also get your proper marketplace back by installing the corresponding app/tapping the desired ZIP.
However, you *really* should keep an up-to-date restore point any time you're messing with stuff like that, especially with new hacks. If something screws up and doesn't straighten out, restore a backup or hard-reset and it will fix itself.
EDIT: The ZIP does not appear to work on most phones. The XAP files should still work on 7.8, though.
WHO CAN I THANK?
Well, aside from myself thanks go to:
Heathcliff74, for the XAP deployer hack and the Samsung marketplace configuration file.
Schaps, for TouchXplorer (let me find the relevant file).
Voluptuary, for info about both OEM and MO marketplaces (working on those).
wpxbox, for the info about "Nokia collection".
CAN I ASK A QUESTION?
You just did, or at least, I did for you. Please see the next post after this one for FAQ. Otherwise, feel free to post a reply with your question. Please, if it's at all relevant, include the make, model, and version of your phone and OS/firmware.
OK, I know you all will have some questions. I'll try to collect them, and their answers, here so people don't have to read every post.
If you ask a question that is already answered here, I may facepalm and/or use sarcasm.
DO I NEED TO RUN THIS APP?
No, you don't. It doesn't do anything at all after installing. In fact, I re-used another app that I had handy, so the message you see isn't even accurate!
WHY DOES THE MESSAGE IN THE APP TALK ABOUT INTEROP UNLOCK? CAN I USE THIS APP FOR INTEROP UNLOCK?
It talks about it because I reused in interop-unlock app (which works exactly the same way, but with a different file). This app will not interop-unlock your phone, or even allow you to do so. However, it doesn't need interop-unlock, either. Furthermore, why are you running the app? You don't need to; none of the instructions say to run it.
CAN I DELETE THE APP?
Yes. Once it's installed, you can delete it immediately if you want to.
HOW DO I GET MY OWN OEM'S MARKETPLACE BACK?
You can either install the corresponding XAP and reboot, or you can wait a day or so for the phone to recover on its own.
HOW CAN I GET BACK TO AN OEM MARKETPLACE THAT I ACCESSED BEFORE?
Remove the app (and any variant of it), if it's currently installed. Then, install it again. Then, reboot as before, and you should see the marketplace corresponding to whatever XAP you used.
WHY DON'T ALL APPS WORK?
Many apps will use native drivers to do their work. These drivers are specific to each OEM's firmware, and are baked into the ROM. Apps that don't need special permissions, like the Samsung Now app or LG's Look n Type, should work. Apps that have high permissions or do device-specific things, like a Network Profile app or HTC Sound Enhancer (if it ever appears again) won't work on other phones.
SOME OF THESE APPS HAVE ID_CAP_INTEROPSERVICES, CAN WE USE THEM FOR INTEROP UNLOCK?
No. The apps may appear to work (even on interop-locked phones) because they were installed from the Marketplace and have valid signatures. However, they won't actually be able to do anything useful, because the wrong drivers will be installed (see the previous question).
CAN YOU ADD A XAP FOR ANOTHER MARKETPLACE?
Sure, once the required configuration data is available. This can be tricky - for example, the values for HTC and Samsung are "HTC" and "Samsung", respectively, but the one for LG is actually "LGE" (LG Electronics). I don't know what they are for Toshiba/Fujitsu, and I'm not sure I have everything from Dell, and I don't have any others. Any help here would be appreciated!
CAN I ACCESS MORE THAN ONE OEM MARKETPLACE AT ONCE?
No, sorry. I tried to build support for multiple OEM markets, but it didn't work. The last one overwrites the previous.
WILL APPS KEEP WORKING AFTER THE MARKETPLACE REVERTS?
So far, yes. I don't know whether they'll get updates, although I suspect they will.
CAN SOMETHING BE DONE ABOUT APPS COMPLAINING THEY DON'T WORK ON MY PHONE?
Sadly, no (nothing safe). Most of the LG and Samsung apps that I've tried work just fine (interop aside) on my HTC phone. It helps that in Mango, a lot of formerly interop capabilities (like compass for LG ScanSearch) are now in the official APIs. Some apps will still check though, and there's nothing I can do about that.
CAN WE ACCESS MARKETPLACES FOR OTHER OPERATORS?
It's probably possible, but I haven't bothered to try yet. If there are interesting apps for carriers that work outside of that carrier's network, I'll give it a shot. It's a different file but the structure is very similar.
IS THERE A LIST OF APPS KNOWN TO WORK?
Courtesy of user JusThinK, as of 1 Feb 2012:
JusThinK said:
Converter
FunShot
HTC Hub
Look n Type
MiniDiary
Notes
Now
Photo Enhancer
Photo Studio
Photo Stylist
Photogram
ScanSearch
SmartShare(previously know as Play To - Working fine on with my Samsung HDTV)
ToolBox
Click to expand...
Click to collapse
can you just deploy all three and have access to all 3 sources in marketplace?
once you install apps from the other oem sources, and the market reverts back, do you lose the apps you have installed?
No. I tried to build it so you could access multiple OEM marketplaces at once, but it didn't work - only ever used the last one in the config file.
Apps stay installed and runnable even after the marketplace reverts. However, I can't promise they'll receive updates. I think they will, but I haven't been testing this long enough to find out.
Dell's marketplace string is "Dell"
Nokia's marketplace string is "Nokia"
I still haven't figured out Fujistu's.
thanx dude,
The 3 xap files are working on the HTC Trophy.
But the LG apps that you can download, if you run the downloaded app from LG place. He said Only for LG devices.
So are you editing the files in the 'keepers' folder? I had found those some time ago and posted them HERE back in October. I thought they would lead to this since when they were deleted the OEM marketplaces would simply go away, same can be done to remove the carrier marketplaces, but I had trouble getting them off my device to really look at them.
Be warned though in my similar pre-mango hack with the registry we found that changing the OEM marketplace values made the DRM wig out and would prevent any apps from starting. The only way to fix it was a full reset or restore to a point before the modifications were done.
I would guess that if you edit LKG_MOStoreConfig.xml you could do the same thing with carriers.
OEM's:
Samsung
HTC
LGE
Dell
Nokia
MO's:
Att
Tmous
Tmode
I am pretty sure these are case sensitive too so keep that in mind.
Thanks GoodDayToDie
this solution it gives me solved my phone not show OEM App in market
Just wondering and perhaps some people might want to test with me if we set LKG_MOStoreConfig.xml and LKG_OEMStoreConfig.xml to read only will it stay set instead of only lasting a few days?
The reason I want this is becuase I want at&t's stupid marketplace entry to remain GONE so I edited LKG_MOStoreConfig.xml to this:
Code:
<ConfigurationFile version="1">
<MOStore>
<setting id="MOName"></setting>
<setting id="MOStoreName"></setting>
<setting id="MOStoreID"></setting>
<setting id="MOStoreEnabled">False</setting>
</MOStore>
</ConfigurationFile>
Now I'm just guessing that this is how it should look since like I said before I never could get the original files off my phone to look at them.
@voluptuary: That would probably work (in fact, the "false" alone is probably enough). Marking the file read-only may or may not be sufficient.
@cyclonemon: You're welcome! I didn't even realize people were having that issue but yes, it should help there too.
I am confused, can't I do this already with Milkman's WP7 3MktPlace? I can search/list 3MktPlace apps . I can add new info such as Nokia to the application. It finds and saves the XAP to the PC and from which I can deploy it to the phone.
ok, after reading more carefully, the program process above would require interop unlock, your route doesn't
@voluptuary (again): Thanks for the OEM names. I'm pretty sure I tried "Nokia" and it didn't work, but I'm trying it again (I did the edit on the phone during testing, and that's pretty typo-prone). For what it's worth, they are not case sensitive (a good thing, since the official casing for Samsung is actually SAMSUNG).
EDIT: Confirmation, "Nokia" does not work.
You're exactly right about which file I'm replacing (you can see that if you crack the XAP). I was looking to use the embedded provxml in MOConfig to do interop-unlock, but it looks like the process which reads that file doesn't have the required permissions. I could do something for the MO marketplaces too, but I'm really not sure there's value to it; do the MOs have apps that are useful if you're not a subscriber?
So far, no DRM wig-outs. I'm hoping it works when I don't mess with the registry. We shall see.
@derausgewanderte: This method doesn't use up unsigned app limit (aside from briefly, when the configuration app is installed). It also allows updates from the phone itself.
GoodDayToDie said:
@derausgewanderte: This method doesn't use up unsigned app limit (aside from briefly, when the configuration app is installed). It also allows updates from the phone itself.
Click to expand...
Click to collapse
I see, thanks for the clarification.
just for your info. Milkman's program works with "Nokia" if that helps.
Thanks, but... neither "Nokia" nor "Dell" are working. It's rather annoying. Samsung I had the actual file to work from, but LG[E] I figured out on my own, and it works. Not so with Nokia or Dell though.
Nokia on the marketplace has the string nokia.
As this seems a nice hack, be very carefull with changing the OEM name of your phone. Doing this a couple of times will invalid something with the DRM and will force you to do a hard reset. You will not be able to run any app installed trough the MP otherwise and you will not be able to install anything.
I dont know for sure if the same thing would happen trough this method, but I'm not going to try it out. I tried it with editing the registry and if you do that about 5 times, your phone cant do anything without a hard reset.
I'm posting this to avoid problems, not to kill this hack. Because its defenetly good work, but before any complications arise, be warned.
Marvin_S said:
Nokia on the marketplace has the string nokia.
As this seems a nice hack, be very carefull with changing the OEM name of your phone. Doing this a couple of times will invalid something with the DRM and will force you to do a hard reset. You will not be able to run any app installed trough the MP otherwise and you will not be able to install anything.
I dont know for sure if the same thing would happen trough this method, but I'm not going to try it out. I tried it with editing the registry and if you do that about 5 times, your phone cant do anything without a hard reset.
I'm posting this to avoid problems, not to kill this hack. Because its defenetly good work, but before any complications arise, be warned.
Click to expand...
Click to collapse
Yes yes please heed this warning. It happened to me.
I'm aware of the problem with the registry editing method. I can't guarantee it won't happen here (make sure you have a recent backup!) but I'm hopeful. I've made far more than 5 changes, and while I haven't had it in this state for weeks yet, I have for days, and so far no problems at all.
EDIT: @VoodooKing: Just to confirm, your problem was with the registry tweak method, right? If you hit that problem with these XAPs, please let me know.
GoodDayToDie said:
@voluptuary (again): Thanks for the OEM names. I'm pretty sure I tried "Nokia" and it didn't work, but I'm trying it again (I did the edit on the phone during testing, and that's pretty typo-prone). For what it's worth, they are not case sensitive (a good thing, since the official casing for Samsung is actually SAMSUNG).
EDIT: Confirmation, "Nokia" does not work.
You're exactly right about which file I'm replacing (you can see that if you crack the XAP). I was looking to use the embedded provxml in MOConfig to do interop-unlock, but it looks like the process which reads that file doesn't have the required permissions. I could do something for the MO marketplaces too, but I'm really not sure there's value to it; do the MOs have apps that are useful if you're not a subscriber?
So far, no DRM wig-outs. I'm hoping it works when I don't mess with the registry. We shall see.
Click to expand...
Click to collapse
Yeah, I can't get Nokia to work either, however my Lumia 800 never had a "Nokia Marketplace" to begin with on the phone so that may have something to do with it. I think the other programs that have been mentioned are pulling apps in a slightly different way than what acctually happens on the phone. I would guess pehaps there is some handset ID matching or something on the phone marketplace whereas with the PC/Web based methods there isn't. (just guessing)
On a side note I tried setting the MOConfig to read only (like I said before) and while att's marketplace still sadly came back, it came back different. It used to be "AT&T AppCenter(tm)" now it reads "AT&T Featured" so that is odd. As for carrier app usefullness IMHO the at&t ones are garbage but I can't speak to any other carriers.
You have to search for Nokia apps in the marketplace for them to show up. There is no Nokia store.
Yes changing registry a few times caused my phone to not launch apps and install from marketplace. I think I changed the name more than 5 times.
Out of curiosity why isn't root allowed out of the box on the Nexus 7?
I mean I get that no one should use superuser access/root privileges on anything more than a "need to use" basis and honestly, I'll even admit that with the way the ecosystem has evolved, root isn't really entirely "needed" but, it still boggles my mind that there is no way I can just open up a terminal, type in a code, and get root.
I've tried googling the issue but, I generally get a bunch of responses about things which aren't quite related.
Snow_fox said:
Out of curiosity why isn't root allowed out of the box on the Nexus 7?
I mean I get that no one should use superuser access/root privileges on anything more than a "need to use" basis and honestly, I'll even admit that with the way the ecosystem has evolved, root isn't really entirely "needed" but, it still boggles my mind that there is no way I can just open up a terminal, type in a code, and get root.
I've tried googling the issue but, I generally get a bunch of responses about things which aren't quite related.
Click to expand...
Click to collapse
I think its fine the way it is. its jailbroken out of the box so you can use your device how you wish and that is what matters. You can't expect a company to support users to change everything about it. Then people complain about bricked devices or contact them for support for some custom rom.
However I believe they made it pretty easy to root. They certainly could have made it a lot harder. Anyone who has the skills (or patience to learn how) to use root certainly can root a device based on the tutorials given. And other users who don't want to worry about it don't ever see it. The little bit of effort helps weed out the people who would mess things up for themselves.
firesoul453 said:
I think its fine the way it is. its jailbroken out of the box so you can use your device how you wish and that is what matters. You can't expect a company to support users to change everything about it. Then people complain about bricked devices or contact them for support for some custom rom.
However I believe they made it pretty easy to root. They certainly could have made it a lot harder. Anyone who has the skills (or patience to learn how) to use root certainly can root a device based on the tutorials given. And other users who don't want to worry about it don't ever see it. The little bit of effort helps weed out the people who would mess things up for themselves.
Click to expand...
Click to collapse
I don't expect a company to support me changing anything I want about it. If I misuse root privileges, then I don't expect to have a lifeline when I call asus/google. I don't expect say Dell or HP to cover my PC if I try to install ubuntu and I botch something up.
However, refusing to let me have root because "might" mess something up is also flawed logic. I may also for one reason or another need root access.
While I am glad they make it easy to root, the reality is there is they are being counter productive. Honestly, just leaving in root access would decrease the chances of me bricking my device at this point. As of now to get root access I'll have to flash a custom recovery compared to just giving the ability to go into a terminal and type in "oem -su enable" or something.
If the flashing issue is really that big of a deal, then why force users to flash to get what they want in the first place?
Snow_fox said:
I don't expect a company to support me changing anything I want about it. If I misuse root privileges, then I don't expect to have a lifeline when I call asus/google. I don't expect say Dell or HP to cover my PC if I try to install ubuntu and I botch something up.
However, refusing to let me have root because "might" mess something up is also flawed logic. I may also for one reason or another need root access.
While I am glad they make it easy to root, the reality is there is they are being counter productive. Honestly, just leaving in root access would decrease the chances of me bricking my device at this point. As of now to get root access I'll have to flash a custom recovery compared to just giving the ability to go into a terminal and type in "oem -su enable" or something.
If the flashing issue is really that big of a deal, then why force users to flash to get what they want in the first place?
Click to expand...
Click to collapse
Root can cause problems. It can cause security problems if not used right and can brick not only while rooting but while flashing custom roms and things.
while you and I don't go asking for support, a lot of people do. People try to pass things off as warrenty problems and do call and email asking for support for things not originally on that phone.
And it hurts them in other ways. Google makes pretty much all their money from ads. Rooting makes it easy to block ads and you average rom might have it built right in. The only reason google bothers with android was for the ad money. So there is no incentive for them give root out of the box. They already are more open and free than their main competitions.
You could look at samsung. THey make their money of the hardware and so have been more open with rooting with odin, thought they still don't really care for it (probably because of the support issue)
And the carriers are even worse because rooting allows for things like wireless tethering for free and data is their biggest costs. Their certnaly isn't any reason for carriers to push for root.
I honestly don't know the true answer; only Google would know.
But in my opinion, it's because Android is an open source OS, and giving users root access allows them to alter .apk's very easily. This is bad for developers, because most developers make money from advertisements or in-app currency, and allowing users to alter their .apk to easily block ads or change in-app currency would thwart developer interest.
In Windows for example, the OS is not open source, but users have "root" access because they can always get to the root of every program/file. BUT users CANNOT EASILY alter the programs installed on Windows - if they want a hacked version, they usually have to download a hacked version that someone else hacked.
Whereas in Android, it's very easy for me to download any .apk I want, run my hack app that says "Search for this value and change it to this" and BAM it's now hacked in literally seconds.
firesoul453 said:
Root can cause problems. It can cause security problems if not used right and can brick not only while rooting but while flashing custom roms and things.
while you and I don't go asking for support, a lot of people do. People try to pass things off as warrenty problems and do call and email asking for support for things not originally on that phone.
And it hurts them in other ways. Google makes pretty much all their money from ads. Rooting makes it easy to block ads and you average rom might have it built right in. The only reason google bothers with android was for the ad money. So there is no incentive for them give root out of the box. They already are more open and free than their main competitions.
You could look at samsung. THey make their money of the hardware and so have been more open with rooting with odin, thought they still don't really care for it (probably because of the support issue)
And the carriers are even worse because rooting allows for things like wireless tethering for free and data is their biggest costs. Their certnaly isn't any reason for carriers to push for root.
Click to expand...
Click to collapse
I'm not going to deny adblocking is one of my many vices. While many people have many views on it, all I can say is until ads no longer break my experience completely, I'll be stuck using adblockers. While this is becoming less of a problem with phones/tablets that have faster processors I've had my entire phone lock up before because of certain types of ads my phone couldn't handle. On top of that many are frustrating to deal with as there is no "x" visible for me to tap and I have to back out of whatever I was doing because the phone can't handle the discrepancy in size and find some way to navigate around the ad.
While this is only one example there have been other issues. Hell I had to use a script that required root back when I had my captivate just to get it it to work on my schools wifi. There were a number of issues and I imagine there are still a number of issues that make the lack of root almost a deal breaker.
Sure you can argue from a support issue point of view but, realistically as I already said, I wouldn't have to flash anything if I had access to root... I guess they just chalk it up to "some people are going to do whatever it takes anyway...." but, that just doesn't make much sense to not let people have it anyway.
Geodude074 said:
I honestly don't know the true answer; only Google would know.
But in my opinion, it's because Android is an open source OS, and giving users root access allows them to alter .apk's very easily. This is bad for developers, because most developers make money from advertisements or in-app currency, and allowing users to alter their .apk to easily block ads or change in-app currency would thwart developer interest.
In Windows for example, the OS is not open source, but users have "root" access because they can always get to the root of every program/file. BUT users CANNOT EASILY alter the programs installed on Windows - if they want a hacked version, they usually have to download a hacked version that someone else hacked.
Whereas in Android, it's very easy for me to download any .apk I want, run my hack app that says "Search for this value and change it to this" and BAM it's now hacked in literally seconds.
Click to expand...
Click to collapse
This is actually one of the best reasons I think I've ever heard and I've actually asked this question a lot in different places over the years. That's a pretty feasible answer.
Geodude074 said:
I honestly don't know the true answer; only Google would know.
But in my opinion, it's because Android is an open source OS, and giving users root access allows them to alter .apk's very easily. This is bad for developers, because most developers make money from advertisements or in-app currency, and allowing users to alter their .apk to easily block ads or change in-app currency would thwart developer interest.
In Windows for example, the OS is not open source, but users have "root" access because they can always get to the root of every program/file. BUT users CANNOT EASILY alter the programs installed on Windows - if they want a hacked version, they usually have to download a hacked version that someone else hacked.
Whereas in Android, it's very easy for me to download any .apk I want, run my hack app that says "Search for this value and change it to this" and BAM it's now hacked in literally seconds.
Click to expand...
Click to collapse
Rooting has nothing to do with decompiling apks. apk hacking is bad but thats a whole other thing. Anyone can get a hold of pretty much every apk easliy, no need for root.
Windows doesn't really have root, its pretty different. You can give programs administrator privileges I guess, but not exactly the same. Decompiling apks is only easier because its java, it has nothing to do with the os or root privileges.
Don't expect any of these companies support to support root until they have a reason to.