Can somebody help me understand why ther min SDK version in the AndroidManifest.xml and default.properties?
using the android examples: hello-jni, san-angeles
I used the default NDK make APP=<app> syntax
and 'ant debug' to build the apk(s);
I found:
fopen() in hello-jni.c will only work with android-3
san-angeles requires android-4 or android-5
and multi touch MotionEvent is only available with android-5
The biggie is simply adding fopen to hello-jni and it runs fine.
change android-3 to android-4 in the manifest and default.properties
rerun android.bat update project
and it fails.
Please help guide me in getting fopen for write to work in min-sdk-android-5
fopen() for read works so far although I am experiencing intermittent results with reading from a file.
Thanks
Write_external_storage
sorry, found the answer here
http://developer.android.com/sdk/android-1.6.html#api-changes
sorry for the spam
Related
Hi all,
I have developped a small plugin for TL 0.9.3 that will display the birthdays to come on any page.
There is no cab installer yet, I will try to find out how to make one if someone may ask for it.
It is my first try to developping in c#, so it may be bugged...
Please report any comment / error you may have
[09/03] : No more ini file. All the configuration is made through params in xml file. See ReadMe.txt in zip file for details.
Thanks.
I'll give it a look.
screenies?
Fresh2Death said:
screenies?
Click to expand...
Click to collapse
+ 1
gratzi!
Screenshots
JstarLuvsTina said:
+ 1
gratzi!
Click to expand...
Click to collapse
Screenshots added
Congrats!!
Hi!!
First of all thank you for developing a plugin for throttle . I've tested it and have a little issue:
- You're searching for the fixed path by using \Program Files\ThrottleLauncher\Plugins hardcoded... This has make plugin crash on my device as I have an Spanish ROM and path is "Archivos de Programa" instead of "Program Files". Also user's can have Throttle Installed on their SD card. The simplest alternative to take the path that will solve this two problems. Add a parameter to the throttleplugin:
Code:
<throttleplugin name="ThrottleBirthday" path="#$THROTTLE#\Plugins\ThrottleBirthday\ThrottleBirthday.dll" height="25" class="ThrottleBirthday.ThrottleBirthday">
<param name="path" value="#$THROTTLE#\Plugins\ThrottleBirthday\"/>
</throttleplugin>
Also you can get rid of the ini file by using params:
Code:
<throttleplugin name="ThrottleBirthday" path="#$THROTTLE#\Plugins\ThrottleBirthday\ThrottleBirthday.dll" height="25" class="ThrottleBirthday.ThrottleBirthday">
<param name="font" value="Arial"/>
<param name="size" value="10"/>
...
</throttleplugin>
That way people developing setups for throttle can parametrize your plugin so it can be configured through the main ConfigDialog of the setup by using:
Code:
<param name="font" value="#@ThrottleTodayFont#"/>
Now... as you are the first developer for plugins for throttlelauncher may I ask you how it was? Did you encounter any problems or lack of documentation?
thank you very much again!!
If I could do it...
Hi APBilbo,
First of all, thanks for the tips, I will do my best to apply them for the next version
Regarding the difficulties I had, I started from your HelloWorldPlugin and learned C# from scratch, and well, asides from the problem of getting Throttle directory, it was quite a piece of cake.
It was a pleasure (and a great fun !!!) to develop a plugin (as simple as it may be) for your Throttle, as this app is for me a good representation of what a pocket pc app should provide
I will be on vacation next week, but I was curious about developping a ThrottleCal.0.2...
Be sure you will have news from me
No more ini file
Hi all,
Thanks to APBilbo' advices , there is no more ini file, only params in the xml file, and it should work on any region ROM (no more hardcoded silly path ).
You may check the Readme.txt in the provided zip file for details.
malrok37 said:
Hi all,
Thanks to APBilbo' advices , there is no more ini file, only params in the xml file, and it should work on any region ROM (no more hardcoded silly path ).
You may check the Readme.txt in the provided zip file for details.
Click to expand...
Click to collapse
Thanks . Keep up good work . And enjoy your vacations!!
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/
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!
Hello Friends,
I have just been introduced to android libraries and have checked out a lot of them. But I have no idea how to use them in my android app.
So can someone post a guide on how to Search, Download, and integrate them in our android project. As I have searched on internet and got to know that we have to put the jar in lib folder, and use the particular classes, but can someone guide how to do the same and how to use them in out layout to give cool effects to our app.
Thanks
In the layout you need to put the full name of the class (including the package):
Code:
<com.example.test.MyButton
... />
You have already answered the question how to integrate them.
For search this is the best starting point: http://forum.xda-developers.com/showthread.php?t=2226547
Second is Google.
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/