Related
Can it be done?
emudojo said:
Can it be done?
Click to expand...
Click to collapse
No, search next time please =)
Short answer is no with an adp build but if you really want paid apps you can install JFRC33 to get access to them.
I don't know where these guys are coming up with their info. You most definitely CAN access paid market with ADP, IF you have installed the update available at www.htc.com in the support section.
The only requirement is that you have a US or UK sim card installed, I don't think that it is necessary for the card to be active.
not so short answer
Well, people are kind of right about not being able to download paid apps. I have an ADP1 1.1 phone using Three as my provider here in the UK and I see SOME charged apps. BUT apps that the developer 'copy protects' arel not available. (see below for the unfiltered version)
This is a load of cr4p on Google's part because the 'copy protection' is simply installing the app to a protected directory (no encryption, no validation, nothing). As the ADP1 phone has root, we can get easy access to the apk file, and since we are all criminals we will post them to warz sites. Of course the reality is that there are far more rooted G1s out there (that CAN get all forms of paid apps) then there are ADP1s.
But, of course, Google has plausible denyability when it comes to hacked G1s. This is not the case with ADP1s. I suspect that this was a decision from the law department in Google.
The only sure way to get ALL the apps on an ADP1 is to install one of the hacked JesusFreek ROMS or flash it to a stock G1
Here is the official word from the android developers (http://android-developers.blogspot.com/)
"Some developers have asked about the support for copy-protected apps on developer devices, and indeed there is a limitation you should be aware of. Many developers are concerned about the unauthorized redistribution of their applications, so they make use of the copy-protection feature (known as "forward locking") which prevents applications from being copied off devices. However, developer phones like the ADP1 allow for unrestricted access to the device's contents, making it impossible to enforce copy protection. As a result, the Market application on such devices is not able to access copy protected apps, whether they are free or paid. If you choose to add copy protection when you upload your application to the Android Market, then you won't be able to test it on the ADP1's Android Market client. Your application will always be accessible to users who have standard configurations though, and if your application (whether it is free or paid) is not copy-protected it will appear on all devices, including developer configurations."
lbcoder said:
I don't know where these guys are coming up with their info. You most definitely CAN access paid market with ADP, IF you have installed the update available at www.htc.com in the support section.
The only requirement is that you have a US or UK sim card installed, I don't think that it is necessary for the card to be active.
Click to expand...
Click to collapse
What update????
Try clicking on the link and going to the support section as I said. THAT update.
I don't see any updates for the G1 under the support section, only FAQ, User Guides, and Tips & Tricks. Do you have a direct link?
http://www.htc.com/www/support/android/adp.html
Thanks for the direct link. I was looking under G1... opps. I want to try and switch over to adp, but wont flashing the updates from the link mean I cant flash to a modded build? Even if I can see protected apps with this update, if I chose to use a Modded image, then I will lose the ability once again right?
Im sorry if im not getting this, but I just want to be on an ADP1.1 build that allows me to see AND purchase all apps... Even protected ones, while still being able to run the scripts and other developments that this community has brought. Will this help me accomplish that???
Sorry in advance
Microsoft just announced today that Windows Phone developers can now unlock their devices for free, with a 2-app sideload limit. Those needing higher limits can grab an account for cheap during the summer ($19 USD).
Just use your Microsoft account with the Windows Phone Developer Registration tool and you should be off and running.
Beginning today we are simplifying the developer phone registration process. Now, any developer can unlock and register 1 phone to load up to 2 apps. Registered developers with Dev Center accounts continue to have the option to unlock up to 3 phones and upload up to 10 apps on each.
Click to expand...
Click to collapse
WithinRafael said:
Microsoft just announced today that Windows Phone developers can now unlock their devices for free, with a 2-app sideload limit. Those needing higher limits can grab an account for cheap during the summer ($19 USD).
Just use your Microsoft account with the Windows Phone Developer Registration tool and you should be off and running.
Click to expand...
Click to collapse
Thats awesome news! That gets rid of the need for Chevron mods for all those WP7 people and that makes it easy to test WP8 apps.
thals1992 said:
thats awesome news! That gets rid of the need for chevron mods for all those wp7 people and that makes it easy to test wp8 apps.
Click to expand...
Click to collapse
this is great news!
This whole thing got me thinking, there might be someway to "abuse" the XAP installer that processes the XAP, since the XAP is downloaded straight from the browser.
Hopefully there's some vulnerabilities in the installer.
IzaacJ said:
This whole thing got me thinking, there might be someway to "abuse" the XAP installer that processes the XAP, since the XAP is downloaded straight from the browser.
Hopefully there's some vulnerabilities in the installer.
Click to expand...
Click to collapse
I think you're on to something here....
Not sure what you mean by "the XAP is downloaded straight from the browser" - Store apps are downloaded over HTTP (HTTPS actually, with cert pinning to boot) but the only apps I've seen actually install if they were downloaded from a web browser (or via email attachment, or sent using Bluetooth) are company / LOB apps, not store apps or unsigned (homebrew/development) apps.
That said, the XAPs do get processed by the installer (and rejected) anyhow. It's possible there's a vulnerability in that check process; is that what you're thinking of? If so, I don't believe it has anything to do with the news in this thread in particular (although it *might* help to have dev-unlock enabled) but it's a worthwhile path of exploration anyhow. The XAP installer is one of the relatively few parts of the system that has fairly high permissions but is easily attackable. Of course, that means MS will have reviewed and fuzz tested the hell out of it, but we can hope...
GoodDayToDie said:
Not sure what you mean by "the XAP is downloaded straight from the browser" - Store apps are downloaded over HTTP (HTTPS actually, with cert pinning to boot) but the only apps I've seen actually install if they were downloaded from a web browser (or via email attachment, or sent using Bluetooth) are company / LOB apps, not store apps or unsigned (homebrew/development) apps.
That said, the XAPs do get processed by the installer (and rejected) anyhow. It's possible there's a vulnerability in that check process; is that what you're thinking of? If so, I don't believe it has anything to do with the news in this thread in particular (although it *might* help to have dev-unlock enabled) but it's a worthwhile path of exploration anyhow. The XAP installer is one of the relatively few parts of the system that has fairly high permissions but is easily attackable. Of course, that means MS will have reviewed and fuzz tested the hell out of it, but we can hope...
Click to expand...
Click to collapse
The XAP's developed in App Studio are downloaded in the browser on the phone, not from the store, which could prove to be a vulnerability, but there might be cert pinning since App Studio apps require you to install a certificate first. Hopefully someone with more knowledge, like you, could look at it. Just prep a simple app in App Studio and go through the process and see what you'll be able to find.
Maybe Fiddler might help to determinate if any cert pinning is done?
Ah sorry, I wasn't looking at App Studio. I will investigate... but unless they're giving us access to the signing key, or raw access to the XAP, it probably won't work for anything *too* exciting. Still, if it's a way to install signed apps that we write ourselves (to any meaningful degree), there's hope...
GoodDayToDie said:
Ah sorry, I wasn't looking at App Studio. I will investigate... but unless they're giving us access to the signing key, or raw access to the XAP, it probably won't work for anything *too* exciting. Still, if it's a way to install signed apps that we write ourselves (to any meaningful degree), there's hope...
Click to expand...
Click to collapse
If I've understood it correctly, there is possibility to do changes to the XAP.
Note this tool is browser driven - no Windows 8 machine required - if you're not going to modify the source code that is. There are plans on the way for more goodies, so keep posted.
Click to expand...
Click to collapse
- Source
Cool. Looks like I need to send a request to get into the beta. I should do that... see what I get back. If the XAPs aren't signed, they probably won't be useful for breaking anything but the interaction with the browser might be interesting. If they are signed...
GoodDayToDie said:
Cool. Looks like I need to send a request to get into the beta. I should do that... see what I get back. If the XAPs aren't signed, they probably won't be useful for breaking anything but the interaction with the browser might be interesting. If they are signed...
Click to expand...
Click to collapse
I didn't have to sign up for the beta, think I could use it right away since I'm a registered dev. Just signed in with my dev account and tried it out right away.
IzaacJ said:
I didn't have to sign up for the beta, think I could use it right away since I'm a registered dev. Just signed in with my dev account and tried it out right away.
Click to expand...
Click to collapse
Awwman! I sent the request more than 24 hours ago and I still haven't received any emails. Also I'm a registered dreamspark dev, but that expired March.
@IzaacJ: Thanks for the tip, I'll try that then.
EDIT: Nope! Still demanding an "invitation code".
How the Windows Phone App Studio deploys
thals1992 said:
Awwman! I sent the request more than 24 hours ago and I still haven't received any emails. Also I'm a registered dreamspark dev, but that expired March.
Click to expand...
Click to collapse
Finally got mine a few hours ago. Haven't got very deep in it yet, but the templates are convenient.
---------- Post added at 10:49 PM ---------- Previous post was at 10:35 PM ----------
IzaacJ said:
The XAP's developed in App Studio are downloaded in the browser on the phone, not from the store, which could prove to be a vulnerability, but there might be cert pinning since App Studio apps require you to install a certificate first. Hopefully someone with more knowledge, like you, could look at it. Just prep a simple app in App Studio and go through the process and see what you'll be able to find.
Maybe Fiddler might help to determinate if any cert pinning is done?
Click to expand...
Click to collapse
Here's the output of an almost empty app.
First things first
Remember you have to install the Certificate we sent you via Email.
Click to expand...
Click to collapse
links to dowappdiagnostics.blob.com/aet/AET.aetx
Code:
<wap-provisioningdoc>
<characteristic type="EnterpriseAppManagement">
<characteristic type="5342258">
<parm datatype="string" name="EnrollmentToken" value="PEFFVD48RW50ZXJwcmlzZUlkIFZhbHVlPSI1MzQyMjU4IiAvPjxTaWduYXR1cmUgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvMDkveG1sZHNpZyMiPjxTaWduZWRJbmZvPjxDYW5vbmljYWxpemF0aW9uTWV0aG9kIEFsZ29yaXRobT0iaHR0cDovL3d3dy53My5vcmcvVFIvMjAwMS9SRUMteG1sLWMxNG4tMjAwMTAzMTUiIC8+PFNpZ25hdHVyZU1ldGhvZCBBbGdvcml0aG09Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvMDQveG1sZHNpZy1tb3JlI3JzYS1zaGEyNTYiIC8+PFJlZmVyZW5jZSBVUkk9IiI+PFRyYW5zZm9ybXM+PFRyYW5zZm9ybSBBbGdvcml0aG09Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvMDkveG1sZHNpZyNlbnZlbG9wZWQtc2lnbmF0dXJlIiAvPjwvVHJhbnNmb3Jtcz48RGlnZXN0TWV0aG9kIEFsZ29yaXRobT0iaHR0cDovL3d3dy53My5vcmcvMjAwMS8wNC94bWxlbmMjc2hhMjU2IiAvPjxEaWdlc3RWYWx1ZT5qbVBocDJSTjAydEoxWkJILzVyS0kzVk9tWjNDTmVHOG02bVVIbCtNNkNvPTwvRGlnZXN0VmFsdWU+PC9SZWZlcmVuY2U+PC9TaWduZWRJbmZvPjxTaWduYXR1cmVWYWx1ZT5OcXlEQ3Qvb0RUb3JIOFBrYlJHNDZNRFpVcTNreWhod1ZEQW5ocUtoYTYxSzhhcEk3SzNkNEJTcmQ1SXFaQVdraEMvRTFmNThRWWF4QWhRaEtPajRhdUxNNG5RaHowNis2OU96em84Q1RYMERjYUxJNHJWWXh4VGdvdXRWSzBnVkc1bVU4c0trZjQ3VmhGSnd4ZndPRHNwdGp1cmZyODNUVFN6OEJjZDlydW9ORGpZV25QWU9wTU9rRnZuNEFVb3hBdzE5M3BjYWsrZmV5c29udEN0cUw2OUNVRUEwTXhTczBXdGVxVkdLVWphd3JPSlJ5SVE3UkFLV1hxZnl3RDVQUS91M0h0REZBRDBGVXgxRDlkZ2VYWlQyZzZIZUxxZkVmdkxCcXY0cHA2ZjZFVXJ4RDVFNkNIV1lXWE9FZnVSbmZVaUFNS2dwZnIrMTBHMUJRZlphQUE9PTwvU2lnbmF0dXJlVmFsdWU+PEtleUluZm8+PFg1MDlEYXRhPjxYNTA5U3ViamVjdE5hbWU+Q0E8L1g1MDlTdWJqZWN0TmFtZT48WDUwOUNlcnRpZmljYXRlPk1JSUVTRENDQXpDZ0F3SUJBZ0lRTWYyNzRvTTRBRDkvS09ZV1lCWDB6akFOQmdrcWhraUc5dzBCQVFzRkFEQmtNUXN3Q1FZRFZRUUdFd0pWVXpFZE1Cc0dBMVVFQ2hNVVUzbHRZVzUwWldNZ1EyOXljRzl5WVhScGIyNHhOakEwQmdOVkJBTVRMVk41YldGdWRHVmpJRVZ1ZEdWeWNISnBjMlVnVFc5aWFXeGxJRkp2YjNRZ1ptOXlJRTFwWTNKdmMyOW1kREFlRncweE1qQXpNVFV3TURBd01EQmFGdzB5TnpBek1UUXlNelU1TlRsYU1JR1NNUXN3Q1FZRFZRUUdFd0pWVXpFZE1Cc0dBMVVFQ2hNVVUzbHRZVzUwWldNZ1EyOXljRzl5WVhScGIyNHhMakFzQmdOVkJBc1RKVmRwYm1SdmQzTWdVR2h2Ym1VZ1JXNTBaWEp3Y21selpTQkJjSEJzYVdOaGRHbHZibk14TkRBeUJnTlZCQU1USzFONWJXRnVkR1ZqSUVWdWRHVnljSEpwYzJVZ1RXOWlhV3hsSUVOQklHWnZjaUJOYVdOeWIzTnZablF3Z2dFaU1BMEdDU3FHU0liM0RRRUJBUVVBQTRJQkR3QXdnZ0VLQW9JQkFRQ3lhVWxNM1VLUW1QNnF5RzdwM0g1bjh0MXpnb3BhUUMrMTVlQlhDaUdXZVJQelIzNFlWeHpvODBSWVlpMHJmMEt0TzlmazVlbTk3ZUw0Y3pRT2hVUE1xK3d0OXQwTEREZjBCcFM3OVlXK0N2SFZwazNCaHlEZTZMai9MaUJSSWY2RWMrRUdjMXNhLy84NVE1eUlxT1RkMU5RQWJBY1oxeDlHOTI1a2RYS24zajZUNTdqNWErNXlQQng5elo0SnNCdm0rc0F6SnI0Mzd5Y2hrK2pwd3BONUJMTFdGMkdLbkVGWGxjSllQYmVvSXlJZkZxa3cxYUpQVGd1cmswWEpnVklXWmozVE1IdHcrcms0dEgxMGIwTmVscFJaRndhLzQ4c1ZmTHE1b1BIS2ZpNFNrUjZmcjRiQWZqQ2R1Z0pyOGJ5NHlpL3dxWUVGMm4zVDJiKzJwZGtsQWdNQkFBR2pnY1l3Z2NNd0VnWURWUjBUQVFIL0JBZ3dCZ0VCL3dJQkFEQkZCZ05WSFI4RVBqQThNRHFnT0tBMmhqUm9kSFJ3T2k4dlkzSnNMbWRsYjNSeWRYTjBMbU52YlM5amNteHpMMjF6Wm5SbGJuUnRiMkpwYkdWeWIyOTBZMkV1WTNKc01CWUdBMVVkSlFRUE1BMEdDMkNHU0FHRytFVUJDRFFCTUE0R0ExVWREd0VCL3dRRUF3SUJCakFkQmdOVkhRNEVGZ1FVWENwa0cxa1NEdXB3Z0NFVU9GS3RDTW5wbG9Bd0h3WURWUjBqQkJnd0ZvQVVUZXpmSmdiY0pCREF0cG4wMXpuSGJ4bjRKaWd3RFFZSktvWklodmNOQVFFTEJRQURnZ0VCQUR4V0dkVTB5dHpOd2ZZbEhmMy8rTDNoYkJNZG1XTnNnNktBS2pDQnY4a2d2SDk3b0xXZTE1c01mSG1RNGo5ZVErMDJpdVpFV1FRU0ZZV0xTd0gxTm5WbHpIK1MzMDV4bFFlTVFEVWxVMWxoZGpOeUpXYlFlR0J0OFZZa09JQ005L1pUdm5yMm1YdVpsVHR4eHE4V2U4WTUyK2VaK0Y1R2QrSjBIYmZkYmF3YVhVYXF4L1FnQ3d6TTM4cW9pQld4d2JQZXRXbk83OHhjMmdlYjdSMzBia3hTUXJMTTRFVGNTanhIb3AwaC9JQVdVZUhIcHh3Y29tWkt5NzV1UEllLzJlTnZtcFZLb0dEb0pJOHB6YlNOaDZDMUxLMUZ5ZDNrYXhiQVZKcGVLcFVJSk9Ka0RubzM0bG9hOStZa1BRc1ZIRjI2TVVLQ1BRMHYxdTdqNGY1V3c0cz08L1g1MDlDZXJ0aWZpY2F0ZT48L1g1MDlEYXRhPjxYNTA5RGF0YT48WDUwOUNlcnRpZmljYXRlPk1JSUVMekNDQXhlZ0F3SUJBZ0lDQWFFd0RRWUpLb1pJaHZjTkFRRUxCUUF3Z1pJeEN6QUpCZ05WQkFZVEFsVlRNUjB3R3dZRFZRUUtFeFJUZVcxaGJuUmxZeUJEYjNKd2IzSmhkR2x2YmpFdU1Dd0dBMVVFQ3hNbFYybHVaRzkzY3lCUWFHOXVaU0JGYm5SbGNuQnlhWE5sSUVGd2NHeHBZMkYwYVc5dWN6RTBNRElHQTFVRUF4TXJVM2x0WVc1MFpXTWdSVzUwWlhKd2NtbHpaU0JOYjJKcGJHVWdRMEVnWm05eUlFMXBZM0p2YzI5bWREQWVGdzB4TXpBMk1EZ3hOalE1TXpoYUZ3MHhOREEyTVRJd09URTNOVGRhTUZreEhqQWNCZ05WQkFzVEZVMXBZM0p2YzI5bWRDQkRiM0p3YjNKaGRHbHZiakVlTUJ3R0ExVUVBeE1WVFdsamNtOXpiMlowSUVOdmNuQnZjbUYwYVc5dU1SY3dGUVlLQ1pJbWlaUHlMR1FCQVJNSE5UTTBNakkxT0RDQ0FTSXdEUVlKS29aSWh2Y05BUUVCQlFBRGdnRVBBRENDQVFvQ2dnRUJBTVJ3RG1kQzBkM1lGUXNON2FVZnd3WHA1T2RINGYrYlVmWlJMZHlrS2tUS3MyZVFGTHRRL3pUSElobkxEVlYxR2djbGtNeUNGdXFYNk1qZUVWVXlCNFJxS1JvYkI1MTRxa21ZSGdSdUx6emdLcnRSMFdFSy9wMUFwejZRT1RSb05GMVhGK0Y2aitESjBqRFhaV0xveHl0V1hrTjJ4cUJiVmRjNXVGTEE0d1U2L2dFYWp5ZWJTOWFyaDRuWTBNWThsUHBxRE1KTVlRNVQxNVUwdGprdVk3UWtXTnIvMGhGelZneWRaRFRyb2puY2FpSmd1Wm5kRGhjK2NUS3V1OEdKanlkUW9BcUJ5WGNSbnBIS0s0Y3lYZ2JUNjJFUllqVUtYcVVFWmFURlh0dGdyanR5Y2Q5VTM0L3k0dG5TUTYybS9vanIvUjJLaDE4cnhpSTRCWjY5ZitFQ0F3RUFBYU9CeGpDQnd6QWZCZ05WSFNNRUdEQVdnQlJjS21RYldSSU82bkNBSVJRNFVxMEl5ZW1XZ0RBT0JnTlZIUThCQWY4RUJBTUNCNEF3SUFZRFZSMGxCQmt3RndZSUt3WUJCUVVIQXdNR0MyQ0dTQUdHK0VVQkNEUUJNRUVHQTFVZEh3UTZNRGd3TnFBMG9ES0dNR2gwZEhBNkx5OWpjbXd1WjJWdmRISjFjM1F1WTI5dEwyTnliSE12YlhObWRHVnVkRzF2WW1sc1pXTmhMbU55YkRBTUJnTlZIUk1CQWY4RUFqQUFNQjBHQTFVZERnUVdCQlFKQk1lRmYvdUIxeFZHcTVESTluYm9ZTnE2bXpBTkJna3Foa2lHOXcwQkFRc0ZBQU9DQVFFQUhRV0dzQmpjcWRoK2F6QjJ0MGxXREJJMWFJRTZVZlQ5cjJUYktBN2pkdjRzdk5KRGIrcy9mTit2ZXMydFJqV25YaDZIS0xacVNkbFpUT3NodzIxV1UxNEE1bUlNNnRMNVdGL1F6dll5aU5HTHAwU1VNa2pSdXpFRDlaT0RrSElkV21Ca0FDS1pGWE92ajQ2TWxPVGZLYVJQdXZPR1NEYktkbGRVY3dWalR3UWpnbHpTY05hUjROL3l0M2FsRUUxQ01jZXJjYUpFZ2xITmpsc0svUFZkMGFTU1YzeHRhNmNvTHBURFlFVlB4bjJ4QnVQd21JeHJ6VHh1QkhUMmNSakN3WDhobC9kRkFxSC94YzBQWFQzbEFVbzZDMDY2b2lEZ3JTQ1gwYUhGcVlTZjROZVNselQ5NFdZTWsrblEwdFBLclVvV2p2N1d1UTlWSUsrMzhmQm5HUT09PC9YNTA5Q2VydGlmaWNhdGU+PC9YNTA5RGF0YT48L0tleUluZm8+PC9TaWduYXR1cmU+PC9BRVQ+"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Link to app
http://bit.ly/19fnUyO
It also offers the source code:
http://apps.windowsstore.com/DashBo...4ab6a18?version=59091.elpplk&resource=sources
The file is named WPAppStudio.xap
THIS JUST ADDS MICROSOFT CORPORATION AS A COMPANY ACCOUNT AND DEPLOYS AN XAP BASED ON IT.
So, this isn't really good news. Back to looking at a company account exploit?
thals1992 said:
Finally got mine a few hours ago. Haven't got very deep in it yet, but the templates are convenient.
---------- Post added at 10:49 PM ---------- Previous post was at 10:35 PM ----------
Here's the output of an almost empty app.
links to dowappdiagnostics.blob.com/aet/AET.aetx
Code:
<wap-provisioningdoc>
<characteristic type="EnterpriseAppManagement">
<characteristic type="5342258">
<parm datatype="string" name="EnrollmentToken" value="PEFFVD48RW50ZXJwcmlzZUlkIFZhbHVlPSI1MzQyMjU4IiAvPjxTaWduYXR1cmUgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvMDkveG1sZHNpZyMiPjxTaWduZWRJbmZvPjxDYW5vbmljYWxpemF0aW9uTWV0aG9kIEFsZ29yaXRobT0iaHR0cDovL3d3dy53My5vcmcvVFIvMjAwMS9SRUMteG1sLWMxNG4tMjAwMTAzMTUiIC8+PFNpZ25hdHVyZU1ldGhvZCBBbGdvcml0aG09Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvMDQveG1sZHNpZy1tb3JlI3JzYS1zaGEyNTYiIC8+PFJlZmVyZW5jZSBVUkk9IiI+PFRyYW5zZm9ybXM+PFRyYW5zZm9ybSBBbGdvcml0aG09Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvMDkveG1sZHNpZyNlbnZlbG9wZWQtc2lnbmF0dXJlIiAvPjwvVHJhbnNmb3Jtcz48RGlnZXN0TWV0aG9kIEFsZ29yaXRobT0iaHR0cDovL3d3dy53My5vcmcvMjAwMS8wNC94bWxlbmMjc2hhMjU2IiAvPjxEaWdlc3RWYWx1ZT5qbVBocDJSTjAydEoxWkJILzVyS0kzVk9tWjNDTmVHOG02bVVIbCtNNkNvPTwvRGlnZXN0VmFsdWU+PC9SZWZlcmVuY2U+PC9TaWduZWRJbmZvPjxTaWduYXR1cmVWYWx1ZT5OcXlEQ3Qvb0RUb3JIOFBrYlJHNDZNRFpVcTNreWhod1ZEQW5ocUtoYTYxSzhhcEk3SzNkNEJTcmQ1SXFaQVdraEMvRTFmNThRWWF4QWhRaEtPajRhdUxNNG5RaHowNis2OU96em84Q1RYMERjYUxJNHJWWXh4VGdvdXRWSzBnVkc1bVU4c0trZjQ3VmhGSnd4ZndPRHNwdGp1cmZyODNUVFN6OEJjZDlydW9ORGpZV25QWU9wTU9rRnZuNEFVb3hBdzE5M3BjYWsrZmV5c29udEN0cUw2OUNVRUEwTXhTczBXdGVxVkdLVWphd3JPSlJ5SVE3UkFLV1hxZnl3RDVQUS91M0h0REZBRDBGVXgxRDlkZ2VYWlQyZzZIZUxxZkVmdkxCcXY0cHA2ZjZFVXJ4RDVFNkNIV1lXWE9FZnVSbmZVaUFNS2dwZnIrMTBHMUJRZlphQUE9PTwvU2lnbmF0dXJlVmFsdWU+PEtleUluZm8+PFg1MDlEYXRhPjxYNTA5U3ViamVjdE5hbWU+Q0E8L1g1MDlTdWJqZWN0TmFtZT48WDUwOUNlcnRpZmljYXRlPk1JSUVTRENDQXpDZ0F3SUJBZ0lRTWYyNzRvTTRBRDkvS09ZV1lCWDB6akFOQmdrcWhraUc5dzBCQVFzRkFEQmtNUXN3Q1FZRFZRUUdFd0pWVXpFZE1Cc0dBMVVFQ2hNVVUzbHRZVzUwWldNZ1EyOXljRzl5WVhScGIyNHhOakEwQmdOVkJBTVRMVk41YldGdWRHVmpJRVZ1ZEdWeWNISnBjMlVnVFc5aWFXeGxJRkp2YjNRZ1ptOXlJRTFwWTNKdmMyOW1kREFlRncweE1qQXpNVFV3TURBd01EQmFGdzB5TnpBek1UUXlNelU1TlRsYU1JR1NNUXN3Q1FZRFZRUUdFd0pWVXpFZE1Cc0dBMVVFQ2hNVVUzbHRZVzUwWldNZ1EyOXljRzl5WVhScGIyNHhMakFzQmdOVkJBc1RKVmRwYm1SdmQzTWdVR2h2Ym1VZ1JXNTBaWEp3Y21selpTQkJjSEJzYVdOaGRHbHZibk14TkRBeUJnTlZCQU1USzFONWJXRnVkR1ZqSUVWdWRHVnljSEpwYzJVZ1RXOWlhV3hsSUVOQklHWnZjaUJOYVdOeWIzTnZablF3Z2dFaU1BMEdDU3FHU0liM0RRRUJBUVVBQTRJQkR3QXdnZ0VLQW9JQkFRQ3lhVWxNM1VLUW1QNnF5RzdwM0g1bjh0MXpnb3BhUUMrMTVlQlhDaUdXZVJQelIzNFlWeHpvODBSWVlpMHJmMEt0TzlmazVlbTk3ZUw0Y3pRT2hVUE1xK3d0OXQwTEREZjBCcFM3OVlXK0N2SFZwazNCaHlEZTZMai9MaUJSSWY2RWMrRUdjMXNhLy84NVE1eUlxT1RkMU5RQWJBY1oxeDlHOTI1a2RYS24zajZUNTdqNWErNXlQQng5elo0SnNCdm0rc0F6SnI0Mzd5Y2hrK2pwd3BONUJMTFdGMkdLbkVGWGxjSllQYmVvSXlJZkZxa3cxYUpQVGd1cmswWEpnVklXWmozVE1IdHcrcms0dEgxMGIwTmVscFJaRndhLzQ4c1ZmTHE1b1BIS2ZpNFNrUjZmcjRiQWZqQ2R1Z0pyOGJ5NHlpL3dxWUVGMm4zVDJiKzJwZGtsQWdNQkFBR2pnY1l3Z2NNd0VnWURWUjBUQVFIL0JBZ3dCZ0VCL3dJQkFEQkZCZ05WSFI4RVBqQThNRHFnT0tBMmhqUm9kSFJ3T2k4dlkzSnNMbWRsYjNSeWRYTjBMbU52YlM5amNteHpMMjF6Wm5SbGJuUnRiMkpwYkdWeWIyOTBZMkV1WTNKc01CWUdBMVVkSlFRUE1BMEdDMkNHU0FHRytFVUJDRFFCTUE0R0ExVWREd0VCL3dRRUF3SUJCakFkQmdOVkhRNEVGZ1FVWENwa0cxa1NEdXB3Z0NFVU9GS3RDTW5wbG9Bd0h3WURWUjBqQkJnd0ZvQVVUZXpmSmdiY0pCREF0cG4wMXpuSGJ4bjRKaWd3RFFZSktvWklodmNOQVFFTEJRQURnZ0VCQUR4V0dkVTB5dHpOd2ZZbEhmMy8rTDNoYkJNZG1XTnNnNktBS2pDQnY4a2d2SDk3b0xXZTE1c01mSG1RNGo5ZVErMDJpdVpFV1FRU0ZZV0xTd0gxTm5WbHpIK1MzMDV4bFFlTVFEVWxVMWxoZGpOeUpXYlFlR0J0OFZZa09JQ005L1pUdm5yMm1YdVpsVHR4eHE4V2U4WTUyK2VaK0Y1R2QrSjBIYmZkYmF3YVhVYXF4L1FnQ3d6TTM4cW9pQld4d2JQZXRXbk83OHhjMmdlYjdSMzBia3hTUXJMTTRFVGNTanhIb3AwaC9JQVdVZUhIcHh3Y29tWkt5NzV1UEllLzJlTnZtcFZLb0dEb0pJOHB6YlNOaDZDMUxLMUZ5ZDNrYXhiQVZKcGVLcFVJSk9Ka0RubzM0bG9hOStZa1BRc1ZIRjI2TVVLQ1BRMHYxdTdqNGY1V3c0cz08L1g1MDlDZXJ0aWZpY2F0ZT48L1g1MDlEYXRhPjxYNTA5RGF0YT48WDUwOUNlcnRpZmljYXRlPk1JSUVMekNDQXhlZ0F3SUJBZ0lDQWFFd0RRWUpLb1pJaHZjTkFRRUxCUUF3Z1pJeEN6QUpCZ05WQkFZVEFsVlRNUjB3R3dZRFZRUUtFeFJUZVcxaGJuUmxZeUJEYjNKd2IzSmhkR2x2YmpFdU1Dd0dBMVVFQ3hNbFYybHVaRzkzY3lCUWFHOXVaU0JGYm5SbGNuQnlhWE5sSUVGd2NHeHBZMkYwYVc5dWN6RTBNRElHQTFVRUF4TXJVM2x0WVc1MFpXTWdSVzUwWlhKd2NtbHpaU0JOYjJKcGJHVWdRMEVnWm05eUlFMXBZM0p2YzI5bWREQWVGdzB4TXpBMk1EZ3hOalE1TXpoYUZ3MHhOREEyTVRJd09URTNOVGRhTUZreEhqQWNCZ05WQkFzVEZVMXBZM0p2YzI5bWRDQkRiM0p3YjNKaGRHbHZiakVlTUJ3R0ExVUVBeE1WVFdsamNtOXpiMlowSUVOdmNuQnZjbUYwYVc5dU1SY3dGUVlLQ1pJbWlaUHlMR1FCQVJNSE5UTTBNakkxT0RDQ0FTSXdEUVlKS29aSWh2Y05BUUVCQlFBRGdnRVBBRENDQVFvQ2dnRUJBTVJ3RG1kQzBkM1lGUXNON2FVZnd3WHA1T2RINGYrYlVmWlJMZHlrS2tUS3MyZVFGTHRRL3pUSElobkxEVlYxR2djbGtNeUNGdXFYNk1qZUVWVXlCNFJxS1JvYkI1MTRxa21ZSGdSdUx6emdLcnRSMFdFSy9wMUFwejZRT1RSb05GMVhGK0Y2aitESjBqRFhaV0xveHl0V1hrTjJ4cUJiVmRjNXVGTEE0d1U2L2dFYWp5ZWJTOWFyaDRuWTBNWThsUHBxRE1KTVlRNVQxNVUwdGprdVk3UWtXTnIvMGhGelZneWRaRFRyb2puY2FpSmd1Wm5kRGhjK2NUS3V1OEdKanlkUW9BcUJ5WGNSbnBIS0s0Y3lYZ2JUNjJFUllqVUtYcVVFWmFURlh0dGdyanR5Y2Q5VTM0L3k0dG5TUTYybS9vanIvUjJLaDE4cnhpSTRCWjY5ZitFQ0F3RUFBYU9CeGpDQnd6QWZCZ05WSFNNRUdEQVdnQlJjS21RYldSSU82bkNBSVJRNFVxMEl5ZW1XZ0RBT0JnTlZIUThCQWY4RUJBTUNCNEF3SUFZRFZSMGxCQmt3RndZSUt3WUJCUVVIQXdNR0MyQ0dTQUdHK0VVQkNEUUJNRUVHQTFVZEh3UTZNRGd3TnFBMG9ES0dNR2gwZEhBNkx5OWpjbXd1WjJWdmRISjFjM1F1WTI5dEwyTnliSE12YlhObWRHVnVkRzF2WW1sc1pXTmhMbU55YkRBTUJnTlZIUk1CQWY4RUFqQUFNQjBHQTFVZERnUVdCQlFKQk1lRmYvdUIxeFZHcTVESTluYm9ZTnE2bXpBTkJna3Foa2lHOXcwQkFRc0ZBQU9DQVFFQUhRV0dzQmpjcWRoK2F6QjJ0MGxXREJJMWFJRTZVZlQ5cjJUYktBN2pkdjRzdk5KRGIrcy9mTit2ZXMydFJqV25YaDZIS0xacVNkbFpUT3NodzIxV1UxNEE1bUlNNnRMNVdGL1F6dll5aU5HTHAwU1VNa2pSdXpFRDlaT0RrSElkV21Ca0FDS1pGWE92ajQ2TWxPVGZLYVJQdXZPR1NEYktkbGRVY3dWalR3UWpnbHpTY05hUjROL3l0M2FsRUUxQ01jZXJjYUpFZ2xITmpsc0svUFZkMGFTU1YzeHRhNmNvTHBURFlFVlB4bjJ4QnVQd21JeHJ6VHh1QkhUMmNSakN3WDhobC9kRkFxSC94YzBQWFQzbEFVbzZDMDY2b2lEZ3JTQ1gwYUhGcVlTZjROZVNselQ5NFdZTWsrblEwdFBLclVvV2p2N1d1UTlWSUsrMzhmQm5HUT09PC9YNTA5Q2VydGlmaWNhdGU+PC9YNTA5RGF0YT48L0tleUluZm8+PC9TaWduYXR1cmU+PC9BRVQ+"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Link to app
http://bit.ly/19fnUyO
It also offers the source code:
http://apps.windowsstore.com/DashBo...4ab6a18?version=59091.elpplk&resource=sources
The file is named WPAppStudio.xap
THIS JUST ADDS MICROSOFT CORPORATION AS A COMPANY ACCOUNT AND DEPLOYS AN XAP BASED ON IT.
So, this isn't really good news. Back to looking at a company account exploit?
Click to expand...
Click to collapse
It might be possible to find an exploit in the XAP installer that installs the XAPs from the browser, and use that to install an app with higher privileges, and accessing the filesystem and/or the registry with full access?
Actually, that's pretty good. Company apps have lower restrictions, and are easier to install. Also, that's a provxml document... we should see if we can modify it and get it to do anything else interesting for us!
@GoodDayToDie, I was thinking the same thing of the provxml document. That would be EPIC if we could modify it to change registry...
@GoodDayToDie, @snickler I'm gonna try to use fiddler to redirect that request to my own server with an edited file and see what happens. Going to start with setting the MaxUnsignedApp value. Wish me luck
IzaacJ said:
@GoodDayToDie, @snickler I'm gonna try to use fiddler to redirect that request to my own server with an edited file and see what happens. Going to start with setting the MaxUnsignedApp value. Wish me luck
Click to expand...
Click to collapse
Ohhh please tell me how this works out! I wanted to do the same thing, but I have to wait for MS to get back with my invitation code.
Best of luck!
@snickler No matter how I do, it ends up showing the AET.aetx as a text file. Doesn't matter if it's the original one or the edited one.
Original one is available at: http://www.izz0.eu/AET.aetx
Edited one is available at: http://www.izz0.eu/AET2.aetx
Feel free to try on your own.
@GoodDayToDie, you've got any ideas? You're like a walking knowledgebase ;D
Hello,
this may be a weird question for this forum (if moderators think it is wrongly placed, please push it to the correct section).
I'm a developer but have never developed anything for android. I wonder if what I want to achieve is possible or not.
My problem:
I want to use VSCO cam as my default camera (e.g. on my lockscreen I can specify a default camera to be launched by clicking on an icon)
VSCO cam has for some reason decided not to "register" as a camera app if that makes sense (in the selection screen of camera apps it doesn't show up)
So my questions are:
What does an app need to do to be recognised as a camera app by other apps? Is it as simple as an entry in a config file? Or is it a java routine? Please name all modifications that would have to occur.
I downloaded the VSCO apk and unzipped it - I should be able to modify it and then still install without problems right?
Just to state the obvious - I don't want to offer this modified app to anybody besides myself. I don't want to add it to google play or even offer it as a download somewhere. This would be just a personal project of mine.
Need Android intent filter
001mic said:
So my questions are:
What does an app need to do to be recognised as a camera app by other apps? Is it as simple as an entry in a config file? Or is it a java routine? Please name all modifications that would have to occur.
I downloaded the VSCO apk and unzipped it - I should be able to modify it and then still install without problems right?
Just to state the obvious - I don't want to offer this modified app to anybody besides myself. I don't want to add it to google play or even offer it as a download somewhere. This would be just a personal project of mine.
Click to expand...
Click to collapse
To be recognized as a camera app and be able to respond the incoming request, the Android intent filter has to be specified.
Foxbrush said:
To be recognized as a camera app and be able to respond the incoming request, the Android intent filter has to be specified.
Click to expand...
Click to collapse
Can you be a little bit more specific? Is it just a change of the Android Manifest xml file?
The file looks weirdly compressed. Can you have a look at it and tell me if you think it's possible to do the required changes...
https://dl.dropboxusercontent.com/u/6568643/AndroidManifest.xml
Cool it worked! Thanks a lot!
I had to add this intend as well to the other in order for my lockscreen app to detect it:
<intent-filter>
<action android:name="android.media.action.STILL_IMAGE_CAMERA"/>
<category android:name="android.intent.category.DEFAULT"/>
</intent-filter>
Many of us don't have root and many of us also uninstalled may system apps, including Fire Launcher. That left us with some annoyances. One major annoyance was being kicked to the lock screen whenever we swiped away apps from the recent apps menu. Some people saw annoying flashes. Well this isn't quite a fix, but it pretty much takes care of the problem. You can now remove your lock screen completely and replace it at will and you do NOT need root access.
***WARNING: Touching any other settings on your tablet during this guide can cause a brick!!!***
1. Download and install Settings Database Editor.
2. Plug your tablet into your PC and open an ADB window. Enter the following:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Step number 2 MUST be done in order for this to work.
3. Open Settings Database Editor and tap on the 'secure' tab at the top.
4. These settings are in alphabetical order. Scroll until you see:
Code:
"lockscreen_disabled" "0"
5. Change the 0 to a 1. DO NOT CHANGE ANYTHING ELSE
6. Close Settings Database Editor
Now turn off your screen. Now turn it back on. You are welcome! I have a few more tricks coming. Watch for some later!
IF THE ABOVE DOESN'T WORK, TO DISABLE LOCK SCREEN:
Code:
adb shell settings put secure lockscreen_disabled 1
ENABLE LOCK SCREEN:
Code:
adb shell settings put secure lockscreen_disabled 0
Both methods don´t work on my Fire HD10 2017.
tommes-d said:
Both methods don´t work on my Fire HD10 2017.
Click to expand...
Click to collapse
It worked almost instantly for me. Maybe wait a bit? Did you reboot? It won't work on every device. Doesn't work on my Galaxy S7.
Not working for me too (Fire HD 8 2016). Also, you've made a mistake: original setting name is "lockscreen.disabled" (dot, not an underscore).
sensboston said:
Not working for me too (Fire HD 8 2016). Also, you've made a mistake: original setting name is "lockscreen.disabled" (dot, not an underscore).
Click to expand...
Click to collapse
Disappointing. Today I got a good one though. I can't wait to get home and post a thread.
I know this isn't the correct forum for this but I tried this on a Fire 7 (2017) and it also does not seem to work.
is there an updated way to do this?
is there an updated way to do this?
edit: kindle fire 8 7th gen, confirmed not working.
Doesn't work on my Fire HD8. But while browsing through Settings Database Editor I have found something useful.
In the "Global Table" tab there's a setting called LOCKSCREEN_AD_ENABLED. Change the value from 1 to 0, save. Turn off screen, turn it on again --> ads are gone!
At least for a while...
Seems to be working on KFAUWI (Fire 7 7th Gen) on 5.4.0.0.
EDIT: Maybe it doesn't work with 5.4.0.1 and later?
It would be useful for those reporting success/failure to include not just device model, but fw version as well.
EDIT1: After some time playing around the system I have found out that by default it actually does not work, but if Global Table->"device_provisioned" = 0 then lock screen gets disabled, but serial number gets greyed out and developer options get disabled, while adb remains functional.
On 5.6.0.0 even change to "device_provisioned" did not disable the lock screen.
gabosius said:
Seems to be working on KFAUWI (Fire 7 7th Gen) on 5.4.0.0.
EDIT: Maybe it doesn't work with 5.4.0.1 and later?
It would be useful for those reporting success/failure to include not just device model, but fw version as well.
Click to expand...
Click to collapse
There are settings in the "private" class that override some of these lower ones, usually in favor their using their own software. I think most device stock settings are hidden for the purpose of favoring their own software. Though with Amazon, I scratch my head. Why spend the large amount of money, to install a high tech, customizable GPS system on devices, only to spend more money carelessly blocking your Access?
Sent from my Samsung Galaxy S4 using XDA Labs
DragonFire1024 said:
There are settings in the "private" class that override some of these lower ones, usually in favor their using their own software. I think most device stock settings are hidden for the purpose of favoring their own software. Though with Amazon, I scratch my head. Why spend the large amount of money, to install a high tech, customizable GPS system on devices, only to spend more money carelessly blocking your Access?
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
That's fairly simple, the same goes for one of the iPhones (don't recall which gen exactly) which had two different models of radio chips, one of which did support LTE, but Apple decided to disable LTE support for that gen of the phone altogether.
Now more on the topic, checked the specs of all 7th gen tablets, indeed none of them seem to support GPS officially (for some reason I thought that HD8/HD10 might have it), but if they have the hw, it could be for testing purposes to test proprietary GPS related sw on development devices before introducing it in the next gen? Or simply they decided to drop it somewhere along the way but left the hardware (as we still have Serial/UART on some production devices nowadays, which are used only for debugging in the development stage).
On the other hand, where did you get the info that it actually has GPS related hardware? Because while exploring my device settings I only found a hint on A-GPS support (which is not proven).
gabosius said:
That's fairly simple, the same goes for one of the iPhones (don't recall which gen exactly) which had two different models of radio chips, one of which did support LTE, but Apple decided to disable LTE support for that gen of the phone altogether.
Now more on the topic, checked the specs of all 7th gen tablets, indeed none of them seem to support GPS officially (for some reason I thought that HD8/HD10 might have it), but if they have the hw, it could be for testing purposes to test proprietary GPS related sw on development devices before introducing it in the next gen? Or simply they decided to drop it somewhere along the way but left the hardware (as we still have Serial/UART on some production devices nowadays, which are used only for debugging in the development stage).
On the other hand, where did you get the info that it actually has GPS related hardware? Because while exploring my device settings I only found a hint on A-GPS support (which is not proven).
Click to expand...
Click to collapse
Add a few .xml configuration files to start and there is configuration settings in the framework. Look for an app on the tablet with HERE in all caps in the title. That's the APK module making it possible. And yes I figured out a way to modify framework settings
DragonFire1024 said:
Add a few .xml configuration files to start and there is configuration settings in the framework. Look for an app on the tablet with HERE in all caps in the title. That's the APK module making it possible. And yes I figured out a way to modify framework settings
Click to expand...
Click to collapse
I see, just checked MT8127 specs, and indeed there seems to be integrated support for GPS with GLONASS, that may be something interesting to play with.
EDIT: HD8/HD10 even have broader support of GPS related technologies according to their SoC specs.
Yeah, I was following root progress thread, even tried Blueborne exploit (the one published by Armis labs on github) on KFAUWI without much success as there is no access to /proc/<pid>/maps. And framework-res.apk mod looks promising only for devices having root, as getting required permissions outside /system is rather problematic.
Yet I was surprised that WRITE_SECURE_SETTINGS can be assigned outside /system. As I was poking around com.amazon.dcp.permission.DISPLAY_DEBUG_UI for quite some time.
gabosius said:
Yet I was surprised that WRITE_SECURE_SETTINGS can be assigned outside /system. As I was poking around com.amazon.dcp.permission.DISPLAY_DEBUG_UI for quite some time.
Click to expand...
Click to collapse
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.
lakitu47 said:
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.
Click to expand...
Click to collapse
Tried granting it to other apps and it resulted in "com.amazon.dcp.permission.DISPLAY_DEBUG_UI is not a changeable type" the command I used was pm grant com.amazon.dcp com.amazon.dcp.permission.DISPLAY_DEBUG_UI so yes, the syntax is the same with custom amazon permissions. Also execution of dumpsys package com.amazon.dcp shows that app already has DISPLAY_DEBUG_UI permission.
My guess is that it requires root, as even when I am launching activity from adb shell (not in context of activity manager) I get the same error that it requires the permission, and the same goes for some other hidden amazon applications.
EDIT: you can get list of device permissions by executing "pm list permissions" without quotes from adb shell, there are at least a few interesting ones.
lakitu47 said:
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.
Click to expand...
Click to collapse
That's a great question and one that hasn't been asked before. I can tell you I've been able to, in some apps, modify the manifest permissions. For example, I can use an app to edit the manifest of Jack Pals terminal emulator to add the secure settings permission and have it successfully install etc. I never thought of doing the same with activity launcher and if successful, seeing what happens. This could be very interesting. If you give me a few copies of some of the manifests permissions, I can see if a recompile and install will hold.
DragonFire1024 said:
That's a great question and one that hasn't been asked before. I can tell you I've been able to, in some apps, modify the manifest permissions. For example, I can use an app to edit the manifest of Jack Pals terminal emulator to add the secure settings permission and have it successfully install etc. I never thought of doing the same with activity launcher and if successful, seeing what happens. This could be very interesting. If you give me a few copies of some of the manifests permissions, I can see if a recompile and install will hold.
Click to expand...
Click to collapse
I attached a text document with ALL of the permissions listed by "pm list permissions" since it was too long to put here.
lakitu47 said:
I attached a text document with ALL of the permissions listed by "pm list permissions" since it was too long to put here.
Click to expand...
Click to collapse
Give me a few hours to see if I can modify the app. If I can, I'll upload a. APK
Sent from my Samsung Galaxy S4 using XDA Labs
DragonFire1024 said:
Give me a few hours to see if I can modify the app. If I can, I'll upload a. APK
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
Questionable whether anything would change, as I don't see where activity launcher would need write secure settings permission.
On the other hand I did some digging on the "not a changeable permission type" message, and this provides some answer on what it might be expecting in order to activate?/assign the permission.
gabosius said:
Questionable whether anything would change, as I don't see where activity launcher would need write secure settings permission.
On the other hand I did some digging on the "not a changeable permission type" message, and this provides some answer on what it might be expecting in order to activate?/assign the permission.
Click to expand...
Click to collapse
Interesting. So each permission has a certain "protection" level?
A friend of mine has found that on Play Store there are some apps that aren't "compatible" with the S10+. I too myself have checked and yes, it appears like it isn't compatible.
Can anyone else on other Regions check if this apps appear too like that? I am from Puerto Rico
Apps:
1. Adobe Premier Clip
2. Slice Package Tracker
In Poland (central Europe):
- APClip - same as yours
- Slice - doesn't even show up in results
Explanation
@atrix_noob
If it's any consolation, the applications install just fine if you download the APK directly (e.g., APKPure).
The best thing to do is to reach to the Developers and inquire when your device will be 'officially' supported. They hold the key.
I'll explain why this happens:
When an application is built, a unique file called a 'Manifest' is created alongside it.
The 'Manifest' lists what the application CAN and CANNOT do when used with a specific device.
When the application is searched via Google Play and the result loaded, the 'Manifest' determines whether or not the device IS or ISN'T compatible.
If the Application is, it will install.
And if it isn't, it won't.
Given the popular of Samsung as a whole, you'll likely see availability soon but given the amount of devices released every month, one can only imagine how many updates a Developer must have to prepare.
If you'd like to learn more, take a look at this:
https://developer.android.com/guide/practices/compatibility
Yeah, i've had it with a few runtastic apps. Had to download them manually and install the apk.
piotrkruczek said:
In Poland (central Europe):
- APClip - same as yours
- Slice - doesn't even show up in results
Click to expand...
Click to collapse
Thanks man, I aprecciate your help.
AHE_XDA said:
@atrix_noob
If it's any consolation, the applications install just fine if you download the APK directly (e.g., APKPure).
The best thing to do is to reach to the Developers and inquire when your device will be 'officially' supported. They hold the key.
I'll explain why this happens:
When an application is built, a unique file called a 'Manifest' is created alongside it.
The 'Manifest' lists what the application CAN and CANNOT do when used with a specific device.
When the application is searched via Google Play and the result loaded, the 'Manifest' determines whether or not the device IS or ISN'T compatible.
If the Application is, it will install.
And if it isn't, it won't.
Given the popular of Samsung as a whole, you'll likely see availability soon but given the amount of devices released every month, one can only imagine how many updates a Developer must have to prepare.
If you'd like to learn more, take a look at this:
https://developer.android.com/guide/practices/compatibility
Click to expand...
Click to collapse
Hey, gotcha, I'll be giving that thread a look, thanks for the explanation I really apreciate your patience. I'll try manually installing the APK and wait till updates for fix the compatibility issuses on the app.
Valinorian said:
Yeah, i've had it with a few runtastic apps. Had to download them manually and install the apk.
Click to expand...
Click to collapse
I'll be giving that a shot and test if they install
atrix_noob said:
Hey, gotcha, I'll be giving that thread a look, thanks for the explanation I really apreciate your patience. I'll try manually installing the APK and wait till updates for fix the compatibility issuses on the app.
Click to expand...
Click to collapse
My pleasure. Anytime.
atrix_noob said:
I'll be giving that a shot and test if they install
Click to expand...
Click to collapse
- runtastic six pack
- Runtastic leg trainer
- Runtastic butt trainer.
They dont show up in appstore but work fine when you install it through apk,
Valinorian said:
- runtastic six pack
- Runtastic leg trainer
- Runtastic butt trainer.
They dont show up in appstore but work fine when you install it through apk,
Click to expand...
Click to collapse
Thanks for the headsup there.
I installed the apps of my original post thru APK amd all work flawlessly
AHE_XDA said:
@atrix_noob
If it's any consolation, the applications install just fine if you download the APK directly (e.g., APKPure).
The best thing to do is to reach to the Developers and inquire when your device will be 'officially' supported. They hold the key.
I'll explain why this happens:
When an application is built, a unique file called a 'Manifest' is created alongside it.
The 'Manifest' lists what the application CAN and CANNOT do when used with a specific device.
When the application is searched via Google Play and the result loaded, the 'Manifest' determines whether or not the device IS or ISN'T compatible.
If the Application is, it will install.
And if it isn't, it won't.
Given the popular of Samsung as a whole, you'll likely see availability soon but given the amount of devices released every month, one can only imagine how many updates a Developer must have to prepare.
If you'd like to learn more, take a look at this:
https://developer.android.com/guide/practices/compatibility
Click to expand...
Click to collapse
The thing is that not each device is manually included in the manifest. New devices are released all the time and unless you exclude something specifically, apps are always made available for distribution. This happens with one of the apps my company runs as well. Whenever a new Galaxy device comes out, its always incompatible with the app and its not because of anything we have done with it.
@Blaaargh
'The thing is that not each device is manually included in the manifest.'
No one said every device is included in the manifest. In fact no devices are listed in the manifest; only declarations.
'New devices are released all the time and unless you exclude something specifically, apps are always made available for distribution. Whenever a new Galaxy device comes out, its always incompatible with the app and its not because of anything we have done with it.'
OP wanted to know why APK X and Y weren't working. I provided him with a generalized explanation of why it MAY happen. It could very well be a Samsung issue but without breaking down the APKs in question, there's no way to be certain.