I was developing with Android 1.5 api and I published an app to the market.
However , one of my friends told me that he can't find my app on the market.
His phone is running Android 2.2 and having a QVGA Screen.
I tried with an emulator running Android 1.6 QVGA and the same problem was noticed.
I tried to google for the solution and it seems that I don't have correct keywords to specify the problem.
I know I can use supports-screens android:smallScreens="true" , but not for 1.5
Do I need to develop with 1.6 api to support all kind of screens? Or do I just need to include some more at the manifest?
Sorry for my poor English.
I can see no one answered my question, is it because I am reading with a QVGA screen?(Joking)
Please Help.
You need to build the project against the 1.6 API (you can do it in a way that is compatible with 1.5) to support various screen sizes with supports-screen.
The whole process consists of right clicking your project in eclipse, changing the API to build against, adding proper values to the manifest and exporting the app.
It's pretty well explained on the android developers page, but if you can't get it working, I'll post a step by step guide once I get to my laptop (later this day).
Number22 said:
You need to build the project against the 1.6 API (you can do it in a way that is compatible with 1.5) to support various screen sizes with supports-screen.
The whole process consists of right clicking your project in eclipse, changing the API to build against, adding proper values to the manifest and exporting the app.
It's pretty well explained on the android developers page, but if you can't get it working, I'll post a step by step guide once I get to my laptop (later this day).
Click to expand...
Click to collapse
I just found out that I can use 1.6API and support 1.5 after reading your reply.
Thank you , you helped alot!
Related
Hey guys,
Currently I am Java programmer (applications and applets for PCs), but I want to try something new, and so I am instersted in developing apps for cellphones. Hope you can answer my questions:
1) MIDP 2.0 does support animated gifs and allows me to access the phones memory (for loading files) when the phone supports this, right? Whats the name of the API that allows me to access the phones memory?
2) Whats the best free development platform for MIDP 2.0 at the moment? Currently I use Eclipse, but I guess I need something else for mobile development.
3) Are there any websites with tutorials that give me a lil introduction to MIDP? Any links are welcome.
Just started to look at this myself, though not fully understanding it yet, managed to get a MIDP helloworld class compiled and .jar created just using javac / command line so far, but haven't managed to get it working on the device yet, need to look into preverifying so i'm told.
2) J2ME toolkit perhaps, free with registration on java.sun.com, explanation of it is in the link in reply (3), might be worth a look first to see if it's what you're after.
3) http://www.codeguru.com/Cpp/W-P/ce/networking/article.php/c7911/
If anyone has any further info, please respond.
http://today.java.net/pub/a/today/2005/02/09/j2me1.html?page=2
works
I am now working on porting linux to HTC Pharos. Gotten HaREt to boot it, working on the keymap. Will post the image here when it's "usable"
For questions go to the launchpad project's "Answers" page. For discussion, use this thread.
Links:
Progress (Handhelds.org Wiki)
Launchpad project
Git repository
very very cool ... but try to do one better... try to get the android working on our phone !! (the image has been released so it should be possible to compile it for the Pharos)
I'm going to make android work, but I won't make a ROM before next year because android doesn't have a soft keyboard (onscreen keyboard). They plan to develop it in the first quarter of next year though.
Android Roadmap
Still, a working android (but without keyboard) would be cool, so when the linux kernel is good to use, I will start on android.
please DO NOT make it a rom, if possible make it work with HARET because then we have a choice!! (far more flexable)
i see you're dependant on the drivers released by source.android. q1 09 will be great (hell its allmost 2009 anyway)
I'm developing on HaRET, will release that after some time. I will maybe release an android ROM when it's stable and usable. Btw, all releases (ie. files) will be in the first post. So no need to go through pages (if this discussion will be that popular) to look for files...
Also, I can make it work pretty well without the soft keyboard drivers, but not with android. So here's my plan:
1 Make the linux kernel work (keypad and touchscreen most important now...)
2 Release kernel + a distro like familiar
3 Make it work (loosely) on Android
just a supporting note
I will be happy to see your linux rom
Awesome! It will be very interesting to see the progress of this.
i tested linwizard , the touchscreen dont work .
do you found any driver?
what about android?
touchscreen work now.
files will be available soon.
Hey, why don't use kaiser,nike,vogue,polaris zImage and just change the mtype to have android on your Pharos?
Launch haret console and find the gpios button commande and maybe somebody can make a new zimage compatible with your device?
hi,
thank you for the idea.
i already started the project.
touchscreen work very well, and i'm now working on buttons and jog wheel.
pharos is omap850 and many difference/and similarity with list of model you listed.
lets hope it work now.
can you please give me any documentation.I'm very thankful.
Oh yeah i didn't mention it wasn't the same chipset so it isn't possible to merge source with our thread.
I don't know much things but i can try to help you.
Try to contact @ : dzo, dcordes or another member in the kaiser thread
Can you please post a POC zip. I want to test how android is reactive on Pharos.
Thanks.
please join this thread http://forum.xda-developers.com/showthread.php?t=494991
source will be uploaded on server as soon as possible.
for now you can play with proposed file.
you can join our project.
Hello!
as the title indicates I am having trouble cross-compiling. hello world compiles perfectly but bigger programs just wont give in..
I downloaded the android source from git and compiled just the way the website (http://source.android.com/download) says you should (is there anyway to verify that its compiled correctly?)
Then I use the agcc python script(http://plausible.org/andy/agcc) for the linking but when i compile i always get trouble about it not being able to find certain defined fields or other types. So basicly i followed the second part of what this wiki says (eventough using a toolchain from codesourcery for example and cc staticly. It also fails...)
What im really asking is how and what do you guys use to cross-compile to android?
Richard_Xeli said:
Hello!
as the title indicates I am having trouble cross-compiling. hello world compiles perfectly but bigger programs just wont give in..
I downloaded the android source from git and compiled just the way the website (http://source.android.com/download) says you should (is there anyway to verify that its compiled correctly?)
Then I use the agcc python script(http://plausible.org/andy/agcc) for the linking but when i compile i always get trouble about it not being able to find certain defined fields or other types. So basicly i followed the second part of what this wiki says (eventough using a toolchain from codesourcery for example and cc staticly. It also fails...)
What im really asking is how and what do you guys use to cross-compile to android?
Click to expand...
Click to collapse
Hello,
i am having problems with the linker too! i am using the NDK (because it actually does C / C++ code) and the code compiles with very few warnings on some instructions but works well otherwise, it just WOULD NOT LINK the stuff together!! one interesting setting i noticed in some public makefiles for the NDK i noticed is that they actually set the linker to /system/bin/linker, which is obviously a file on the target device. but i don't know how it would access it? any ideas?
BTW: post your error(s) please
Try this
The system won't let me post a link (as a new user), however there is a really good tutorial on native android development and debugging using the AOSP build system. Search on Aton International Incorporated and click on blogs in the menubar. I am in no way associated with the company, just happy to finally be able to cross-compile, link and debug for android.
Maybe someone who has more posts could post a link here.
http://www.aton.com/android-native-development-using-the-android-open-source-project/
Hi,
I would like to test the roms I can find here, on an emulator.
for that, I will need something like the SDK for the Acer tablet A500.
(to build my AVD)
I can't find it. anyone have an idea where I can find it ?
thanks
Olivier
http://lmgtfy.com/?q=android+sdk
ah ah ah . so fun )
unfortunatly, it is not provided by google !
I know well the android SDK, I am talking about a small part which is sometime provided by constructor in order to help the developper to build application with android SDK.
for example, Sony provides the SDK part for some of its device. it has to be added to the android SDK.
I think it could comes from Acer, or developer who has it because they are working near or far from this (in the same way, the Leak comes from someone which is near from developer team)
I am still looking for that.
thanks
Olivier
Im totally confused as to what you are looking for.. If its reference sdk from acer . They have not provided this.. I think its something they provide to google then google adds it to the sdk. or acer will provide a repo to add to your sdk.
now here is what setup i have..
1 download the sdk tools from developer.android.com/sdk i think is the url (use search )
2. download eclipse (there is a link on the developer.android.com site)
3 download the correct FULL Java library abe sure to read the requirements on the version of eclipse you use for what jave version you need )
4 Read read READ .. Read the how to install sdk development environment in Eclipse for your EXACT OS . Pay close attention to every detail. like is is x86 x64 and so on.
5 Follow the instructions word for word on again the install and setup for android development platform for your OS Version.
This is what i use as well as CYGWIN (this is for advanced users) As well as there are other tools that make developing much easier. YES IM NEW TO all of this as well.But have learned alot over the last year.
The above only gets you ready. Once you get to this point . KEEP . WELL YOU KNOW THIS Part already KEEP READING.. in a few weeks you will on your way.
GOOD LUCK developer.android.com has everything your asking and beyond.
If any of the above is incorrect Blame it on developer.android.com or the mighty thor. god of the universe..
Sup XDA, there is one question about porting the sailfish OS. I am guided by the official documentation, according to the latest guide on HADK - https://sailfishos.org/wp-content/u...OS-HardwareAdaptationDevelopmentKit-2.0.1.pdf
I encountered a problem with the point 7.2.1. When performing the rpm/dxd/helpers/build_packages.sh. there is installation and assembly of packages, but it breaks off when creating a middlevare, namely, the libhybris. Here is the complete log of the assembly - https://paste.debian.net/plain/997702
As I understood from the logs myself to build the libhybris, I need to use the compiler with C++11 support, but in the scratchbox2 the old version of the gcc-4.6.3 version is used, which does not understand the standart C++11. I tried to change the CFLAGS from "--std=gnu++11" to "--std=gnu++0x" , but the libhybris does not compile with the flag of the old standards.
What do you propose to do? How to update the compiler in a scratchbox2 target?
P.S. wrote it via google translate, dont be offended pls
memewarrior said:
Sup XDA, there is one question about porting the sailfish OS. I am guided by the official documentation, according to the latest guide on HADK - https://sailfishos.org/wp-content/u...OS-HardwareAdaptationDevelopmentKit-2.0.1.pdf
I encountered a problem with the point 7.2.1. When performing the rpm/dxd/helpers/build_packages.sh. there is installation and assembly of packages, but it breaks off when creating a middlevare, namely, the libhybris. Here is the complete log of the assembly - https://paste.debian.net/plain/997702
As I understood from the logs myself to build the libhybris, I need to use the compiler with C++11 support, but in the scratchbox2 the old version of the gcc-4.6.3 version is used, which does not understand the standart C++11. I tried to change the CFLAGS from "--std=gnu++11" to "--std=gnu++0x" , but the libhybris does not compile with the flag of the old standards.
What do you propose to do? How to update the compiler in a scratchbox2 target?
P.S. wrote it via google translate, dont be offended pls
Click to expand...
Click to collapse
Heyyo, the guide has a messed up sb2 section.
I can't load your Pastebin link but please check my thread here to see how I resolved the bad sb2 guide
https://together.jolla.com/question/172682/unknown-tag-systemd_requires/
Also, just in case you get stuck on 8.5 of that guide here's how I fixed that too
https://together.jolla.com/question...cregister-for-85-building-the-image-with-mic/