So I have this app that only works on ARM based Android devices and not x86 based ones. Sorry I'm not too tech savvy so I might sound like I'm absolutely dumb... Anyways any suggestions? And for reference, I don't have the source code for the apk file but I know the devs so yeah... Help?
Related
I would like to port Firefox OS to my device (that is not supported by Mozilla but it has Android 4.2). I've read from net that some of the drivers haven't been developed yet, but if FFOS uses the kernel from Android, then it can load the drivers from my Android ROM, right?
From this point, my real question is: if I build my FFOS ROM correctly, would I still have some bugs from hardware/drivers?
Thank you!
Leakspin, I'll try to give you some context on whether it's doable, and what has been done yet.
if FFOS uses the kernel from Android, then it can load the drivers from my Android ROM, right?
Yes and No. There is much more than that. As you can see, Firefox is built putting together several pieces, such as Gonk(what you were referring to "android kernel", Gecko (our application runtime), and finally Gaia (user interface). Take a look at the Stack. For more info, please follow the architecture blog post at MDN.
Has it been ported yet to any Android devices?
Yes, but it's not a simple process and there is no guarantee that it will work on all android devices. Here, have a look at the list of devices and which tools you will need to perform such operation.
There is also a porting tutorial you might want to follow.
f I build my FFOS ROM correctly, would I still have some bugs from hardware/drivers?
Unfortunately, very likely that you will do.
I tried my best to style this answer, but the stupid stackoverflow limited the amount of links and images I'm able to post. Sorry for that.
Links:
How to port Firefox OS
Pre-requisites.
I would like to understand how an application like AlsaMixer or MixGet, mixer widget with alsa is working.
Specially, I would like to develop an application which makes use of the "/etc/asound.conf" which would be available with ALSA.
Has anyone more knowledge on this? How can I "build" ALSA for every Android-device?
I personally have tested those applications on my own Samsung Galaxy Nexus which natively uses "tinyalsa" and on an "HTC Desire" which uses something with "/dev/msm_audio_out" (don't know what this is exactly).
It seems that those apps require root, ok no problem, but they work without larger modifications and on a large range of devices).
Thanks in advance for your help, I've read hundreds over hundreds of docs and found no real informations.
If an Android device
actually uses ALSA drivers; and
is rooted (so that your app can access the device files),
then you could the NDK to access the ALSA libraries.
In that case, ALSA works just like on any other machine.
I am interested in building Android for Source for a Galaxy S3 (but just knowing how to do it in general will be quite helpful)
I know how to do it for all the nexus devices in general, but I was wondering how to do it for some of the other phones. I know that it is possible because CyanogenMod and other modders do it. Usually when they announce them they include the source for the kernel.
How do you put the pieces together? Getting the android source code and the custom kernel together in something that can be flashed.
Generally it is not trivial. You need some binary files for hardware support (camera, WiFi, NFC, etc) and you need to figure out which those are and how to pull them from the device. The kernel is GPL licensed, so the the manufacturer will release their version/patches at some point, but you might have to wait. Then you have to create device build files to put all those together in an image for the particular device. Your best bet is to get CyanogenMod source and see how it is done in practice.
I can't find a clear list of what files needs developer's attention when i'm building a new Android image.
All the guides that i have found until now are way too generic or really old.
I'm supposing that i'm not interested on customize the platform, i just want a vanilla flavour but for my device only.
The answer is a bit complicated. You probably cannot build a vanilla Android for your device, unless your device is one of the google developer phones. Here is a list of the devices you can build Android for. The reason being that the manufactures usually does not publish all the parts needed to actually build Android for their devices.
But do have a look at the cyanogenmod project, and see if they support your device. They are kind of trying to make a "vanilla" android source for the devices which the manufactures themselves does not support. And they are doing quite a nice job, in my opinion. I have a custom build of Android 4.0 for my Galaxy SII running for months now, and it is working perfectly fine.
If you update your questions with the devices your are using, I can probably provide specifics on how you can build cyanogenmod for your specific device.
What are you trying to do ?
Declare some images or layout specific to only one device ?
You can't do it with a selector on a folder (-large, -fr, ...), but with some code. Check this out : http://developer.android.com/reference/android/os/Build.html#MODEL,
I have a Xoom tablet and it would be great if I could run statistical analysis using R on it. As far as I know it is not possible to use R on iPad due to license problems (GPl x iTunes etc.) and a lack of compiler for Fortran in the Apple tablet.
But what about tablets using android? Arguably, the GPL issue is not a problem, so any help here on how to use R on my tablet?
I used Linux Installer from http://android.galoula.com/en/LinuxInstall/ (my Dezire Z was rooted beforehand), installed stable debian and R! on this Linux install. I`m not a Linux-geek and total time for installation (first time loop file size was insufficient, and I repeated the whole process) wass less than hour however.
(source: gyazo.com)
At some point, smartphones and tablets will have browsers capable enough to run RStudio in its server mode via the browser. Currently, the latter demands too much in terms of newer GWT, Javascricpt, ... magic that it remains limited to (recent enough) desktop browsers; see here for a bit more on this.
You can always ssh out though. Connectbot is a capable ssh client for Android, and of course free. No graphs though.
The Android SDK offers developers the facility to program in Java, ... not C or Fortran, which are the languages in which R is written. Although some have said that hacking the Android tablets voids their warranty and prevents upgrades, Motorola only requires that the device be relocked before doing upgrades. For this question I think it still boils down to "if you have to ask the question, then you cannot do it".
EDIT: But somebody else will probably try it.
(I haven't found gcc for the Android.)