Is it Good services or not to compare other software’s services.
What do you mean to say ?
Answer:
Hey friend, first thing to understand is that, every software and application is different and needs different sets of codings for the development. Secondly, suppose you want to develop a JAVA software application for which you cannot use the codings for Android applications, they may be completely differ or may very less similar in some cases.
So, comparing android application development services to other softwares is something not possible.
Related
maybe either through API level, or by querying market info
Reason: i want to check on GB before I upgrade to ICS, which apps will not work.
don't know if relevant but it is for SGS II
Thx in advance
repost from here as nobody could really answer my question
can't believe I'm the only one with that issue
maybe an idea for a dev? would be willing to pay for that ;-)
I don't see why this can't be done:
-http://stackoverflow.com/questions/2695746/how-to-get-a-list-of-installed-android-applications-and-pick-one-to-run
-http://developer.android.com/reference/android/content/pm/PackageManager.html
-http://developer.android.com/reference/android/content/Context.html#getApplicationInfo()
I haven't thought through the problem just yet, but its seems to be doable. If you don't find an app soon, I will start working on a script that does it and, if successful, a proper, free software app. I am hoping the available methods won't require something as stupid as launching each app fully. But again, I haven't thought it through. Thanks for the idea btw.
EDIT:
Made a little more effort
https://groups.google.com/forum/?hl=en&fromgroups#!topic/android-developers/dXLACRIizKc
I will work on something this weekend and get back with y'all.
EDIT 2:
So it looks like I would need maxSdkVersion which I don't find in the API. Furthermore, it is strongly suggested that one not use maxSdkVersion when building an app so that doesn't sound all that useful. I have received another, much more complicated suggestion that may do what I want, but I will have to look hard at it. Looks like I'm going nowhere in my effort. Always open to suggestions. More to come later this weekend.
I'm not the sharpest tool in the shed, but I thought this was mostly a straightforward task using the API's exposure to AndroidManifest.xml. As per my previously posted link to an Android Developers discussion on the topic, my approach is dead in the water as far as I can see. I did try to find an answer though to the best of my limited ability. If anyone has or ever solves this problem (I consider it a problem) I would hope they find the this thread.
Thanks for the learning experience. I give up.
Most older apps will work fine on ICS, its pretty backwards compatible. If the app uses legacy menus the button will appear in the old lower left hand corner location instead of the upper right hand corner like apps written for ICS.
i'm no dev so bear with me if i write stupid stuff
one likely but not very promising sounding way might be to use android:targetSdkVersion as "As Android evolves with each new version, some behaviors and even appearances might change. However, if the API level of the platform is higher than the version declared by your app's targetSdkVersion, the system may enable compatibility behaviors to ensure that your app continues to work the way you expect. You can disable such compatibility behaviors by specifying targetSdkVersion to match the API level of the platform on which it's running. For example, setting this value to "11" or higher allows the system to apply a new default theme (Holo) to your app when running on Android 3.0 or higher and also disables screen compatibility mode when running on larger screens (because support for API level 11 implicitly supports larger screens)."
question though is how many apps actually use this?
However after having read this re android:maxSdkVersion "Warning: Declaring this attribute is not recommended. First, there is no need to set the attribute as means of blocking deployment of your application onto new versions of the Android platform as they are released. By design, new versions of the platform are fully backward-compatible. Your application should work properly on new versions, provided it uses only standard APIs and follows development best practices. Second, note that in some cases, declaring the attribute can result in your application being removed from users' devices after a system update to a higher API Level. Most devices on which your application is likely to be installed will receive periodic system updates over the air, so you should consider their effect on your application before setting this attribute." (taking from here) i now don't know how important my op is, but then why do all app devs release new versions "fixing things" for ICS?
One pretty significant example which actually currently will prevent my phone from getting ICS for now is that the subsonic app in the current version produces stuttering when playing audio while downloading (problem description here).
Isn't there any way to instead of searching the phone searching google play/android market instead?
Randi said:
maybe either through API level, or by querying market info
Reason: i want to check on GB before I upgrade to ICS, which apps will not work.
don't know if relevant but it is for SGS II
Thx in advance
repost from here as nobody could really answer my question
Click to expand...
Click to collapse
Here's a list of some working games/apps for ICS
Theoretically an Android app (or a combo of say App Engine and Android) could find your installed apps, seacrh Play for said apps and then scrape the page for relevant information. Doesn't sound to hard, but I didn't think about too hard either. Perhaps I will check out what useful info is on Play and how feasible scraping its markup will be. I will get back at y'all if I do.
Hi. I'm about to get my first Android phone, and would naturally like to know more about the OS. I would describe myself as intimately familiar with ordinary GNU/Linux systems, but let's face it, Android is hardly your ordinary such creature. Moreover, there seems to be very few technical introductions to Android around; those I've found tend to be idiotic user's guides (not technical at all) or focused on software development (interesting, but not what I'm looking for right now).
Things I wonder about with Android include:
There's an unusual libc, right? Is the GNU userland around, though?
The file system directory structure. It's hardly LSB-compliant, eh?
The package system. Everything I've come across is centered around the SDK, and hides many of the details of what goes on here. Sub-questions: Is it only "apps" (gah, I hate the word, I'm sorry) that use the package manager, or is everything covered by it, as in a normal Linux system?
The boot loader. Experience with other ARM/non-x86-systems indicate this is a world very different from GRUB, and also a highly varied one.
How do shared libraries fit into the Android ecosystem? Some places I get the impression everything is static. Is that really true?
What's this non-X display system? How do you configure it, etc.?
What's the init system like?
As far as I've understood, the actual phone software (is "baseband" the right terminology?) tends to be proprietary and separate from the OS. How does it fit into all of this? Does the OS execute code at some mysterious memory location? Is some special-purpose hardware run? Is it just a standard process? Is it in kernel-space?
I'm not looking to get these questions answered here. Rather, I'm asking: Are there any documents or books around that try to fill the role of bringing an experienced Linux user with decent development background and technical knowledge into Android?
As we see that there is big list of android apps for the particular thing and activity. How can one identify the mistakes made by the android app developer that even a Lehman can understand who generally use the Android phone and don't well acquainted with core technical stuff
Friends! There is a problem:
In my application, I have a need to make troubleshooting instructions with notifications, usually these problems are related to:
a) Battery optimization settings;
b) And additional battery parameters;
But in different models, brands and versions of Android, the scripts and interface of system windows are different to solve problems A and B. Is there any special reference or framework that can be implemented in your application?
P.S. in Google Play, I met applications that have instructions for any smartphone, did they not prescribe everything themselves?
xokid32671 said:
Friends! There is a problem:
In my application, I have a need to make troubleshooting instructions with notifications, usually these problems are related to:
a) Battery optimization settings;
b) And additional battery parameters;
But in different models, brands and versions of Android, the scripts and interface of system windows are different to solve problems A and B. Is there any special reference or framework that can be implemented in your application?
P.S. in Google Play, I met applications that have instructions for any smartphone, did they not prescribe everything themselves?
Click to expand...
Click to collapse
I am not sure that I have completely understood what you mean.
Yes, there are differences introduced by manufacturers into the firmware running on their devices. But the basic operating system is the same: Android from Google.
So the basic services, interfaces, settings should be nearly the same on every Android device ... as long as the manufacturer had not changed it.
Whilst I understand that there are no hard and fast rules when it comes to software development, and that the cost ultimately comes down to the scope of the project. It would however be nice to figure out as to how much it normally costs for a fully customised version of Android OS that can be used professionally. This customised ROM of Android would then need to be flashed to a device.
I understand that I have a choice of either reusing an existing ROM, or starting with AOSP. In both cases, I would need to customise that, and then package it along with the OEM vendor's kernel and drivers.
I know that there will be a lot of work involved, and also understand that I need to get a professional onboard. I don't however know / understand as to how much something like this will cost.
The plan would be to create a ROM that would be fairly similar to how the firmware on the Switch operates. In this way, the ROM must have the following features:
be devoid of all bloatware so as to increase performance of the hardware and to also allow apps to load and run faster.
tangentially... the ROM must "feel" native to the device, and allow developers to maximise performance of the device by creating and running apps that run as if they've been "written to the metal".
has a variation of the Google Play Store from which apps can be bought and downloaded from.
ROM is linked to host website.
has DRM and copy-protection features implemented where the OS checks for the authenticity of the device it's running on, and the authenticity of the app where only apps sold via the store will be able to run on the customised ROM of the Android OS. This would also probably mean that the apps would need to be authenticated by the server on a regular basis, otherwise there would be an online ban.
allows for Android apps and exports from gaming engines such as Unity, GameMaker, Unreal to be made available and to run on the device - with DRM / Copy Protection features.
development of all necessary API.
not allow the device to be easily hackable / rooted, or even be customisable by casual users.
acts as a launcher for (gaming) apps, and minimises / stops all other processes from running in the background.
I just don't know how much something like the above would cost...
How many hours would it take to create a ROM based on the above specification, and assuming that the developer charged $30 per hour, what sort of budget should I be looking at?
A stock ROM is the adaptation of the telephone's working framework that accompanies your telephone when you get it.
A custom ROM is a completely independent adaptation of the OS, including the piece (which makes everything run), applications, administrations, and so on - all you require to work the gadget, with the exception of it's redone by somebody here and there.
So what does the "altered" part mean? Since Android is open source, engineers are allowed to take stock ROMs, adjust them, strip them of trash, streamline them, add things, and essentially do whatever their creative mind and abilities permit.