Database Users

XDA App Store

Just wondering if anyone has thought of or better still started to build an XDA App Store.
I am thinking of an app we can all download to our phones, it will auto see what phone you have and only show those apps from XDA users, auto download updates of installed apps, auto download dependancies etc.
I have used an iphone hacked with cydia and such and it is much easier for downloading programs in this manner.
Just my 2 cents guys, I do hope we see something someday.

I know that you said that it should be XDA-specific, but another option is called App2Date.
Take a look here:
http://www.modaco.com/content/windo.../lend-your-support-to-a-generic-updater-tool/
I was thinking of making one myself, but I definitely do not have time to even start such a project. I'm fairly busy with other ones.

Its not quite what I imagined.
That program does the updates, but like cydia for a hacked iphone you should be able to download new programs as well.
I honestly don't think it would be too hard or dificult to make.
All we really need is an app to list the programs based on the device and wm version your currently running.
The only problem will be to find somewhere to store the apps. A solution could be a simple databased maintaned and hosted by XDA, that will list the program name, details, OS and device information (so you can get the correct version for your phone) and a direct download link to the cab file. This way the apps can be hosted anywhere and we can avoid having to run and pay for a huge data transfer of programs.
I can possibly help with the database if anyones interested in helping to write the actuall app. Then the listings can be maintaned by xda registered users.

Hi,
i am one of the developers of mobile2day.com an we have the possibility to provide a big database with applications mapped to several devices. So we can show only applications for a specific device.
We have allready a mobile solution running on http://mobile2day.mobi/en/usd/index.html where you can buy and download applications. Maybe we can think about to add beta software, too.
Please, if you are interested feel free to contact me.

I was owner of an iPhone before I bought my Touch Pro and besides the fact that the iPhone is not that good it has one big advantage: The AppStore
I would love that kind of store for WM Apps

[Q] Cross-tablet apks

Hi all...
I was wondering if and how could be possible to port apks built for one tablet to another of different brand, i.e. I liked a lot the email client of the Samsung Galaxy 10.1 (with multiple email selector and recycle bin emptying feature), but many others are worth a try...
When I try simply to push the email.apk to my Iconia, it won't work (the icon diasppears from apps), if I try to install it I obtain an error (app not installed) probably due to a signing mismatch... I'd like really to learn how to do this, if possible. This knowledge will complete and accomplish any further request about personalization of our tablets, could be a great improvement being capable to get out the "system" you really want...
I tried to figure out how to use apk manager, but it's quite really difficult without some good suggestion, the thread is more than 200 pages long, and I got stoned before simply find out any usefull info about "system apks"...
TIA

I would like to know also. I want the Facebook account integration from the Galaxy.

Some apps are license by that manufacurer and would be considered wares.its a gray area please be careful. And make sure the Dec of all apps you use get paid

simple answer
couple of APK for galaxy are using CORE framework of the galaxy tabs firmware itself
that will not be possible to just install those apk.
such as
touchwizUI
status bar overlay (I mean the minimode menu with quick access), the quick access settings...
Email and Social things
It's their "Marketing Strenght" so they didn't make it easy to be "stolen" by other brands
I run just the dual clock, the memo, and eReader from samsung but I am running a custom firmware so that change many things
At this moment only 1 custom firmware does use Samsung as base, Virtuous Galaxy... but I have to warn that using custom firmware without following backup steps strictly or knowing the consequence is to AVOID.

sanaell said:
...
At this moment only 1 custom firmware does use Samsung as base, Virtuous Galaxy... but I have to warn that using custom firmware without following backup steps strictly or knowing the consequence is to AVOID.
Click to expand...
Click to collapse
first of all, thanks for your answer, and your warn...
I'd like to go deep in the question, as you correctly affirmed, virtuous galaxy's based upon Unity v5 kernel, but virtuous picasso also lays on the same structure, doesn't it?
right now I'm running m-dj's picasso 1.1.0 rom, wouldn't be possible, with any required modification, to run elsewhere coming apks?
I mean, think about having two different pcs, both with the same hardware and the same linux distro and kernel, wouldn't seem wierd that on one pc you could run an application that won't run on the other?
I'm thinking, if they wanted to protect their components why they didn't simply wrote hardware oriented kernels? Therefore, its a fact that on my iconia I can run either a Samsung or an Asus based rom, according to this, where is the cross-platform limit? I mean, is there some sort of documentation defining which part of these Android system is "really" open, under GPL, GNU or whatever structured property info list? I can't find any browsing the net... or maybe I've found too much, its almost impossible to understand what you can and what you can't...

I do not know the whole answer to this question.but I do know this much.if you have any.apk application that is for sale on the market or was installed for free on any device that it was not pre installed on. I would thing it would be considered pirated. As you did not buy it.nor did the developer give permission to run the API on your device.thou some apostle you buy can be installed across the devices you have registered with Googler
if im wrong people please correct me.I just think that developers that fallow rules and write great software MUST BE PAID.

erica_renee said:
I do not know the whole answer to this question.but I do know this much.if you have any.apk application that is for sale on the market or was installed for free on any device that it was not pre installed on. I would thing it would be considered pirated. As you did not buy it.nor did the developer give permission to run the API on your device.thou some apostle you buy can be installed across the devices you have registered with Googler
if im wrong people please correct me.I just think that developers that fallow rules and write great software MUST BE PAID.
Click to expand...
Click to collapse
Right and Wrong
if the application is a paid application and wasn't preinstalled on your tablet it is not really legal
if the application is free but cannot be installed from the market and you install it from other sources it's ok
if the application is from another tablet, and exclusively on this tablet do not expect run it on the stock firmware of your tablet, you have great chance to cannot run it simply, or get some random FC (such as from GALAXY because they use another structure on the file directory... so some application try to get the path and it's return an error, Or they are implemented and integrated with the kernel and that... you can't pass throught)
On my tablet I do run
ASUS widget
Galaxy widget (dual clock)
and some other application not from ACER.
now to get back to the OP
. you are on a virtuous... why not go on the virtuous Galaxy !!! if you want galaxy application... I don't get it...

sanaell said:
now to get back to the OP
. you are on a virtuous... why not go on the virtuous Galaxy !!! if you want galaxy application... I don't get it...
Click to expand...
Click to collapse
I agree to this explanation of yours, when I flash a rom different from the original, aware that's coming from a different brand, I'm more or less conscious that I'm doing something wrong. mmmf... that's philosophy... won't lose your time
The point is, I've tried the Galaxy rom, I don't like the interface, I don't like the extra bar functionalities, in short I mostly appreciated the Email.apk, most of all because it has a convenient "select all" function, even in the recycler bin (I can't stand with an email client stupid like the one embedded in the Acer version). In any case, given the impossibility to get the Galaxy Email, I'll buy a new one on the market...

Accessing second APK?

Hey All -
First, really quick background: I'm a ASP.NET / .NET programmer, and taught myself Java and Android while making the one app I have released (for a hobby of mine) - https://play.google.com/store/apps/details?id=com.tsqmadness.bmmaps
Now, having said that, I'm looking to upgrade my app with a couple features (version 2.0, baby!), and was wondering how to make an 'add on' apk to access from the initial app.
For example (this is one of the several uses I am thinking of for the 'add on'), the easiest one would be -
Main app wants to access an add-on apk to call a function to grind some numbers, and return a result. If that add-on APK's not installed, then the user wouldn't be able to use that function.
The UI stuff I can handle easily, the main purpose of my question here is -
How can I tell if the other 'add on' APK is installed, and
How do I access a function (in a class or some such) in the other APK?
Honestly, I'd google it, but I'm not sure what this process is even called, so my searches have come up pretty sparse.
Thanks guys -
-Mike.

Do you want it to be a feature unlocker? Like a pro version key? For that purpose I'd recommend in-app-purchases because the user doesn't feel limited during download because he's got "just" the free version.
If you want it to execute methods, you could have a look at shared user ids and system broadcasts.

nikwen said:
Do you want it to be a feature unlocker? Like a pro version key? For that purpose I'd recommend in-app-purchases because the user doesn't feel limited during download because he's got "just" the free version.
Click to expand...
Click to collapse
Originally, this WAS a plan. I have switched to in-app purchases for that now, however.
nikwen said:
If you want it to execute methods, you could have a look at shared user ids and system broadcasts.
Click to expand...
Click to collapse
Thanks, that'll give me a starting place to search on. I was thinking a few other reasons for it as well (like, a map marker pack, for a limited basic example..)
Thanks-
Mike.

coyttl said:
Originally, this WAS a plan. I have switched to in-app purchases for that now, however.
Thanks, that'll give me a starting place to search on. I was thinking a few other reasons for it as well (like, a map marker pack, for a limited basic example..)
Thanks-
Mike.
Click to expand...
Click to collapse
Welcome.
The difficult part will be returning a result to the original app.

[Q]App not allowing me to sign in due to custom rom

First of all, forgive me if this is not the right forum to ask this question, because I'm not sure what is.
Hi everyone,
So the company that provides the TV channels in my country (like the cable companies in the US) has a streaming service that streams most of these channels online to phones, tablets, computers.
The problem is that their app is, according to them "not supported on hacked devices". Just so we're clear, we're talking about Android here, and hacked = root/custom rom, which this stupid company considers illegal. In some devices, they check both root and custom rom, in some only one of them, and in some the app will work even if you have both. For example, on my Nexus 4 the app worked with stock rom that was rooted. Now that I am running a custom rom, trying to hide root using various apps does not work. So obviously the problem, with my device at least, is running the custom rom.
I'm currently learning Java & Android development and have decided to use the little knowledge that I have to try to find the lines of code responsible for this idiotic check.
I looked up many tools for decompiling apps and have finally found a good one, called JadX.
http://androidcracking.blogspot.co.i...ler.html#links
This decompiler is excellent, but gives me a scary amount of code files to look. Even so, trying to search all of them (JadX has that functionality) for the code that checks for root/custom rom has turned up nothing. I have also tried to search for the message they give me when I open the app (about hacked devices not working) but I found nothing, again.
One more thing - a developer that also tried to solve this problem said he traced the problem back to DxDrmDlcCore. I searched it, found it a some class, but not sure what to do now (delete the entire class and recompile?)
Can someone here direct me towards what I need to be looking for?
OR
Is the solution really simple, such as editing my build.prop? Someone suggested it once, but did not know what lines to edit.
If someone is ready to step up to the challenge, I can upload the apk.
Thank you!

Uncompatible apps with S10+

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.