So Fennec was just released.
http://www.mozilla.org/projects/fennec/1.0a1/releasenotes/
I tried it on my linux box, runs pretty well. Any chance they'll make a java version? Or is some one here up to the task? Any ideas?
thanks
I think they said they wouldn't be doing an Android port until Google supports something other than Android Java.
Right.
but couldn't someone download the c code and compile it under the java (with some obvious tweaks throughout)? Or am I way off here?
It would be a major undertaking to port it to Java, and each susequent release would also need to be ported. Unless Mozilla decides to support Android, I doubt we'll see Firefox on the G1 (except for those people who install a full linux distro).
Hi, I'm beginning c++ Development, Done a little stuff with OpenGL but love challenging myself with command line stuff. For this, I mostly use gcc, and either geany or nano.
I did have debian on my G1 so I could use nano and gcc. It worked well, but the only way of getting files to and from would be via ftp.
I was wondering if people who had experience compiling command line stuff for android (Hasn't Bash recently been ported?) could help or give me some tips? nano + gcc would be awesome, though gcc is a must, I'd be able to copy my app to my g1's SD card and have my terminal apps on the go, great for long journeys and stuff.
I'd even be tempted to look at writing an IDE in Java (though I've not much experience in GUI development, I have in programming theory).
Plus, are there instructions for actually compiling linux apps for android, I don't seem to have found any anywhere, and It'd be good, that we could maybe compile more apps like rtorrent and such.
Can any of the devs here compile an android version?
https://wiki.mozilla.org/Mobile/Build/Fennec
I believe everything you need to compile it should be there. If I knew how to do this I would but I'm just starting to learn how to code.
*edit: attached source
Thanks
-Mr. Biggz
The code required to make a proper working Sprint Hero build doesn't exist to the public.
In terms of what? I thought source code was platform independent.
Without knowing anything about fennec it looks like it can currently be compiled for windows mobile or for phones that can install debian packages. While android is linux the applications on our phone are java based.
So while those instructions are for compiling it for linux but that wouldn't actually run on our phone. And source code isn't platform independent, there are hundreds of different languages. For example my kitchen is written in VB. You can't take the source code (which relies on win API) and compile it for another platform.
Mr. Biggz said:
In terms of what? I thought source code was platform independent.
Click to expand...
Click to collapse
Um kinda but not really. C for windows is much like C for linux but there are differences, you can usually port code from one to the other by just doing a primary build then hunting down the errors.
When it comes to cell phones much of the code is platform specific, the Android core kernel is based on linux but requires application specific tweaks per devise which is why we can't just pop 1.6, 2.0, or 2.1 on the HeroC, we don't know how HTC made a GSM only rom work on CDMA because they are hiding what they did to make it work.
Hi, I'm trying out developing for my O2 Flame and was wondering if I could use the GNU GCC Compiler for compiling my programs, as I do not have the money for Visual C++ or something like that. If the GCC Compiler can't, can anybody recommend me a free compiler, Thanks in advanced.
You can use the free version of Embedded Visual C++ 4.0, although it was originally designed for development for WM 2003. If you limit the main menu to two items then WM 5.0 onwards will display the program correctly with the buttons either side of the SIP. Any more, and it switches back to the WM2003 style command bar.
For C++ you can develop in the Win32, ATL or MFC models.
http://www.microsoft.com/downloads/d...displaylang=en
Don't forget to apply SP4 to it after install. (Same page, use the link at the bottom)
It also uses an earlier WM2003 emulator that runs a half way x86/Arm code setup. It works, but the standalone emulator manager with the relevant WinMo SDK does a better job. You will only be able to fully debug the code created in by EVC 4, in its own WM2003 emulator or on a real device, not in the standalone emulator. The standalone emulator images will run your code so you can test it, but you cannot set breakpoints, examine variables. etc.
If you want to develop stuff for GPS, then you may have to add the relevent headers and lib files from later versions of the SDKs
The GNU compiler can be made to work, but I have never tried it.
Thanks for your help!
This is something that is driving me crazy, shouldt be MIPS Android SDK and NDK be compatible with any source maded for the ARM version?
First thing i noticed with this Ainol Novo 7 Basic was that, the small amount of compatible apps, none of the better apps are compatible.
No: Netflix, Skype, Android Terminal Emulator, MX video Player, Chainfire3D, any mame32/nes emu, a working barcode reader, connectbot, adosbox/qemu, opera or any other browser. and the list goes on.
I wonder why, i trought devs will want the larger amount of users as posible.
For the record, i just got Android Terminal Emulator working in my Novo 7 Basic, i had to:
1) Download Term source code
2) Download MIPS Android SDK, NDK, Apache ANT, Eclipse with ADL, cgywin (to compile NDK libs)
3) Import Term project to eclipse
4) change the target build to android-12
5) change Aplication.mk to "APP_ABI := mips mips-r2"
6) build ndk-libs for the app
7) build the project with eclipse
And i know nothing about programing for android, just c/c++
Best guess that anyone will probably give you is that the majority of devices out there running Android are ARM based, but as that changes, the number and quality of available apps should improve.
There is a HUGE obstacle to overcome however. Not many people are going to buy a device today based on what might run on it months from now, especially when there are devices out there that will run it now, and many of those that do purchase a MIPS based device consider it a mistake and end up returning it.
It is not possible to offer two different version on the market and i don't think it is possible to restrict the apps to a specific architecture.
Are the number of MIPS devices really rising? The android market doesn't really seem to be ready for that. It would mean even more app versions devs would have to consider.
Which apps work and which don't?
Maybe those using native code, compiled with NDK don't work, as those routines are compiled specificly for ARM.
Don't take my word for it though, just some thoughts.
its not possible to get 2 different versions on the market.
Rumor has it that the problem is frequently a development oversight and that it's related to omitting some important MIPS related files from the package build.
I imagine that it can also be related to poor programming practices and also programming for optimized code.
~~ Sent from my Velocity Micro Cruz PT701/T105 via Tapatalk ~~
As far as I know, Market supports device specific apk's nowadays, which would make it possible to have an mips apk...
http://developer.android.com/guide/market/publishing/multiple-apks.html
Altough the proccess is not trivial, it is not that difficult either, just minor changes to the manifest and filter the apk for Native Platform...
Also, it would be possible to compile it for all devices that the current NDK supports, by using the latest revision of NDK (as of November 2011):
http://developer.android.com/sdk/ndk/index.html#overview
You just need to add:
APP_ABI := all
Click to expand...
Click to collapse
to the makefile and it should now be compatible with all processor architectures that NDK supports....
So, now there are means to easily support different processor architectures, but, don't expect quick adoption of it, as, unfortunately, this depends entirely upon developer will to change some of its project settings and/or publishing way (it is entirely possible, now, to have a single apk for all platforms)...
Unfortunately, right now, and I would dare to say, in the next 6 - 8 Months, I would not expect this to change much... Altough the official NDK has support for multiple devices, it still doesn't incorporate the MIPS abi, which is not official, and thus, it is not possible to declare that an APK for a native MIPS device as well...
Hopefully MIPS devices will grab a nice piece of the Android devices and then "force" Google to officially support those devices. I believe that it is possible to grab the latest unoficial NDK and use it with APP_ABI all and publish it to the Market, but, as of today, is mostly something recent and that few (if any) developers support (remember, this possibility came with November's NDK, I'm not even sure if MIPs NDK is already up to date with Google's November NDK), so, I would dare to say, MIPS devices are not in a good position right now (even x86 devices, which have official support, are not...).
I have a MIPS based tablet named "MIDI Japan MD-785IP" that is quite nice but is making me sad with the lack of some softwares and in special, lack of ROMs to it. Apparently I am the only person in the internet that have one
shivansps said:
This is something that is driving me crazy, shouldt be MIPS Android SDK and NDK be compatible with any source maded for the ARM version?
...
For the record, i just got Android Terminal Emulator working in my Novo 7 Basic, i had to:
...
Click to expand...
Click to collapse
Hello,
Have you shared that MIPS compatible Android Terminal Emulator?
Thank you
Sure... and here is connectbot too.
Ive attemped to recompile adosbox too but the source code and makefiles are just a big mess and no documentation provided.
And that is another problem, poor documentation in open source projects.
BTW, Market has to have some way to know if a app is for arm or mips, since market on basic only shows up compatible apps.
Also, its no enoght to just incluide the "mips" folder along with "armabi" with all mips compiled .so files inside the libs folder? because is that all what it takes, unless the app is using binaries.
And im agree that google has most of the fault for not incluiding mips supprt in his NDK, the mips one can compile for both.
I wonder what will happen when intel medfield will came out...
I am in an even worse position - I bought 2 NOVO7Paladins - one for the g/f. I had to get one for myself, because I know I will be 1st line support
So, I have a MIPS cpu (with reduced software availability) and also ICS which further reduces app compatibility.
Apps which I consider essential (Samba server, VNC Server, Angry Birds Seasons....) are not available, so l'm currently installing eclipse, JDK, SDK, NDK on a linux box to try to rebuild stuff - it has been many years since I last had to get my hands dirty with code.
I know I have a steep learning curve ahead, but I'm sure it will be many months before there is a significant increase in app availability. I understand though, that if developers have written native code for ARM, they won't be in a hurry to port that to a minority cpu. It is way easier for new apps to be built with different architectures in mind.
Thanks Shivansps, I had been looking for a terminal - I had given up and was trying to get telnet working - a last restort. It was either that or carry a laptop around with me to use ADB
Now, all I need is to get the MIPS ABI to appear in Eclipse AVD setup... (oh, and learn how to code for android )
i dont use Eclipse or SDK myselft any longer, what i do is just recompile shared libs with mips NDK and include the new "mips" folder intro the libs folder of the original .apk file, then re-sign the apk with one click signer.
MapsWithMe for MIPS and x86
maersi said:
I am in an even worse position - I bought 2 NOVO7Paladins - one for the g/f. I had to get one for myself, because I know I will be 1st line support
Click to expand...
Click to collapse
Hi! Do you still have MIPS android device?
Would you please test MapsWithMe on it? It's offline world maps based on OpenStreetMap.
We've built apk for mips and x86 architectures but doesn't have any devices to check if it works.
Apk is available here: dl.dropbox.com/u/24013616/MapsWithMe-203-mips-x86-120502.apk
Cheers,
Alex Zolotarev
MapsWithMe Team
AlexanderZolotarev said:
Hi! Do you still have MIPS android device?
Would you please test MapsWithMe on it? It's offline world maps based on OpenStreetMap.
We've built apk for mips and x86 architectures but doesn't have any devices to check if it works.
Apk is available here: dl.dropbox.com/u/24013616/MapsWithMe-203-mips-x86-120502.apk
Cheers,
Alex Zolotarev
MapsWithMe Team
Click to expand...
Click to collapse
Yes, I still have a mips tablet, but it hasn't gps. Do you want me to check it?
Enviado desde mi ThL W8 usando Tapatalk 2