Is there any tutorial/guide for creating a watchface,
but with the power of java and Android Studio?
The only available sources i know, are located in github here and you can read about them in this topic. However these sources do not work out of the box anymore (because of the updates).
There are some other apks here from Marco Fregapane. I believe his work was based on the previous mentioned dev, malvarez. I asked him and he is not willing to release any sources... Not that is so important, since malvarez has done all the basic work
Anyway, you should first start from extracting the need libraries (read here), and read the XDA topic too
Related
Without the inclusion of proper documentation included with an Android Rom or an Android Build users will start filling up the HD2 Android Development Forum with why this wont work when it does on someone elses Rom. To stop this from happening there will be a requirement when creating a Thread for a Rom with Android included, or an Android Build.
------------------------------------------
------------------------------------------
If you are making a Rom with Android built in or an Android Build that is run from haret then please INCLUDE with your file a readme.txt file in the ROOT of your release archive with the following information:
*What BUILD version?
An internal version # that can be used to identify the authors exact release (e.g. my-rom-v0.5.zip) for easier reference for the users and fellow developers benefiting from the release.
*Which kernel image and kernel modules are used?
Where are zImage and modules.ko originally downloaded (in case the chef didn't compile on their own) and where is the kernel source code for the kernel and modules.
In case the chef did not compile on his own, he should still be able find out where the source code is.
(The license under which the Linux kernel is released requires the distribution of the source code that was used when distributing builds.)
*What rootfilesystems are used?
Where was it taken from, what does it include (android version it's based on etc) and in case of self compilation, where is the source code.
(In case of most windows mobile shipped devices that's often some rootfs file e.g. named android.ext2 and an initial ram filesystem often named initrd.cpio.gz).
*ChangeLog*
A ChangeLog is really an essential addition in every build as it informs the end user what modifications have been made from the last build. This will save you ALOT of questions as to what has been added, deleted or modified and therefore is a requirement for everyones benefit.
*WindowsMobile version your Android Build was tested on*
Please include your WinMo Build version, HTC OemDrivers (if known), XIP (if known) and Radio version so that users know what the Android Build was tested on and can replicate if neccessary for fault finding purposes.
------------------------------------------
------------------------------------------
If you are unable to obtain any of this information and thus can't make it available through an included readme.txt you should not distribute your rom and keep it for personal use only.
If you are using an exact copy of a present release (e.g. in case of a WinCE rom that has an android 'dual boot' option) you must include the readme.txt from the original rom chef.
If you release a Rom and do not have the required information then you will be asked to either create and include a readme.txt file with your Rom or ask for the thread to be deleted.
If you have any comments or questions on this please feel free to post.
Mark.
** reserved **
Thanks a lot for the quick action, Mark. I am glad to see a first positive response.
If this will establish I hope that
*users are informed about what they get
=>less unneeded questions and thus more room for constructive feedback
*developers have an easier time to benefit from present releases
*new developers must try to get an understanding of what they are doing
=>more quality releases
The original post can be found here.
I think it would be nice to hammer out the readme.txt requirements together with chefs so we can get some convention that satisfies everybody.
edit: Think it will really be good to always put readme.txt in root of release archive so everybody knows where to look for it.
dcordes said:
edit: Think it will really be good to always put readme.txt in root of release archive so everybody knows where to look for it.
Click to expand...
Click to collapse
Edited the 1st post to include this
Mark.
Will be following this convention for any future releases
DarkStone1337 said:
Will be following this convention for any future releases
Click to expand...
Click to collapse
Thank you
Future releases soon I hope lol
Mark.
May I suggest that the readme include the date of ROM compilation, as well as the date the kernel and root file systems files. I think this will help users and chefs to easily build there own compilations and keep track of it's validity.
And a title format like: [date]-[name]-[version]-{[kernel]-[kerneldate]}-{[modules]-[modules-date]}-[rootfs] (just like rules for 'regular' roms). Both for the post and the archive preferably?
Personally I switch between versions a lot, to find differences/improvements/bugs.
Clear archive-naming should simplyfy this .
Excellent rules! We need to improve stability of ports and eliminate all unnecessary questions !
P.S. Hope there won't be any "bogus", or "copy-paste-claim" ROM-s.
dcordes an mskip +1
ahbad said:
May I suggest that the readme include the date of ROM compilation, as well as the date the kernel and root file systems files. I think this will help users and chefs to easily build there own compilations and keep track of it's validity.
Click to expand...
Click to collapse
Very good idea. I think we should at least add the rom release date to minimum required readme.txt information.
For the rootfs release date I think we should leave it up to the chefs because I think it will be hard to find out in many cases. Reason is rootfilesystems get passed on 20 times...
In case of the kernel release date it might be a good idea to add it. should be easy to find out. When you grab the kernel e.g. from the two sources I link to in the thread
http://oe.netripper.com/files/htcleo_autobuild/
http://cotulla.pp.ru/leo/Android/
you can just copy paste the date from filename or information on the site. This would be very useful assuming the kernel images will be removed at some point.
On a side note: For both kernel examples the source code repository to add in readme.txt is
git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git htc-msm-2.6.32
gitweb: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
So currently in every leo rom readme.txt this must be linked to as kernel source reference. netripper autobuild zImages using this exact source code and cotulla zImages share same codebase (although currently the latest changes are unavailable but will be added in git soon)
shufflez said:
And a title format like: [date]-[name]-[version]-{[kernel]-[kerneldate]}-{[modules]-[modules-date]}-[rootfs] (just like rules for 'regular' roms). Both for the post and the archive preferably?
Personally I switch between versions a lot, to find differences/improvements/bugs.
Clear archive-naming should simplyfy this .
Click to expand...
Click to collapse
To me that seems over exaggerated. Rom version in file name should be enough. Rest can be looked up in readme.txt
So what does everybody think? If we add the release date of kernel and completed rom, do we have an agreement ? In that case we should compile an example and add it in the first post.
best regards
your right dcordes too much information in the title can be a bad thing. Something more like
[Date] [Name] [Version] [Build] [maybe Kernel version]
That should be Enough i think so for Example
[21/07] [Darkstone1337] [v5] [Eclair w/sense] [2.6.32]
Everything else should stay a change log for people to read
David Balfour said:
your right dcordes too much information in the title can be a bad thing. Something more like
[Date] [Name] [Version] [Build] [maybe Kernel version]
That should be Enough i think so for Example
[21/07] [Darkstone1337] [v5] [Eclair w/sense] [2.6.32]
Everything else should stay a change log for people to read
Click to expand...
Click to collapse
I am sticking with my opinion:
*in filename require internal chef rom version
*in readme.txt add:
-rom release date
-kernel release date
Mark what do you think? Any other opinions?
Install to folder
May be a good idea install all files to appropriate folder, not directly root of SDcard as in last darkstone FROYO. Greatly simplify process of testing and changes between several images and don't messy root. Switching between different versions is than as easy as renaming directory.
I think we should also leave directory structure etc to the chef as long as readme.txt with all the required information exists in archive root so users can find it easily.
so do we have some agreement here? Mark ? If so you should update the first post to compile final set of information needed and clarify that it is not a nice extra but a requirement.
dcordes said:
I am sticking with my opinion:
*in filename require internal chef rom version
*in readme.txt add:
-rom release date
-kernel release date
Mark what do you think? Any other opinions?
Click to expand...
Click to collapse
I agree with you on this theres no need to make things more complicated than they need to be. Although there does need to be some sort of standard for the thread title.
And no I cant think of anything else right now that needs to go in.
dcordes said:
I think we should also leave directory structure etc to the chef as long as readme.txt with all the required information exists in archive root so users can find it easily.
so do we have some agreement here? Mark ? If so you should update the first post to compile final set of information needed and clarify that it is not a nice extra but a requirement.
Click to expand...
Click to collapse
Also agree that its upto the chef how they want their files set up as long as its clearly stated in the readme.txt what to do to get it working.
Everything sounds fine What needs adding to the first post to make it complete?
Sorry I have been working on my Loader but its all finished now (I hope).
Mark.
HD2 Android Image & Instructions
Hi All,
Can somebody confirm if there is a working Android image for the HD2 yet? From reading previous threads, it would seem there is still some technical challenges, no image is available yet.
If I am wrong, please could somebody tell me the location of an image and instructions so I can install Android on my HD2? I am struggling with WM6.5 and I much prefer Android. I have used WM for 9-years now but it just doesn't compare - partially because there are limited decent apps available.
All the best,
Youdaler
youdaler said:
Hi All,
Can somebody confirm if there is a working Android image for the HD2 yet? From reading previous threads, it would seem there is still some technical challenges, no image is available yet.
If I am wrong, please could somebody tell me the location of an image and instructions so I can install Android on my HD2? I am struggling with WM6.5 and I much prefer Android. I have used WM for 9-years now but it just doesn't compare - partially because there are limited decent apps available.
All the best,
Youdaler
Click to expand...
Click to collapse
I will just give you a friendly warning this time as it is your first post. This thread is for the discussion of information to be included by Android builders.
If you look in the Android forum then you will see working builds by DarkStone and by Dan1j3l. Look at their threads for how to load Android. to answer your question yes Android does work (95%) on the HD2.
Please confirm you have read this so I can delete these posts and keep the thread clean. In futured please only post in the correct thread and if you arent sure then post in the Q&A thread at the top of the Android forum.
Mark.
Understand. Thanks for clarifying.
I think we should extend the readme.txt items with some section like 'expected issues' or 'known problems' .
And in the readme.txt , could help too:
Tested with:
-WinMo rom x.xx.xx
-Radio rom 2.xx.xx
Sent from my HTC Desire using XDA App
Dear experts,
like many ppl, I am new to Android Development, and would be able to cook my own rom with amazing home-made features before the end of the week... and I want it to be easy, funny, and eventually Fast....
... Indeed, I don't want all of this, so I'll try to be realistic in my incoming questions and beg for your indulgence if some things sound stupid / inexact / already documented and so on : I have performed a long search process before I decided to post here and would not ask it otherwise.
So, first, here's what I have know about android:
- Android Architecture (various layers)
- Android + java programming (beginner with both but skilled with general OOP and smartphone -iPhone- programming)
- Rom flasing process : rooting, bootloader / recovery flashing , using adb, filesystem of a ROM
- Android official source building (from git repository) and patch apply.
- Basic cooking without any source code modification: use of dsixda's kitchen with xda members' home-made roms mainly
Then, the material I am working with :
- Max OS 10.6.5
- A HTC - Tattoo : rooted, with nandroid and busybox installed (also have an available HTC - Hero)
- adb 1.0.26
- HTC Android Kitchen 0.106 - by dsixda
- Android official source from http://android.git.kernel.org/
Now, what I don't know about is advanced cooking... I read a lot about ppl wondering the same, and generally there was no basic answers (not to mention guide/tutorials).
Since I will surely be the nth to ask this, let's try to ask a specific question.
I downloaded from Android github a patch I am very interested in. This patch applies on the framework and does not impact any other layer (especially not the kernel nor the hardware related libs). After building the source, I thus get a framework.jar I would like to replace some target framework.jar with .
I was quite sure it was not very bright to do such with a custom ROM, even a quite standard FroYo-based one, since there was little chance that such a cooked-rom used a virgin framework taken as-it from android github. But I tried anyway with some of the FroYo-based roms taken from the xda list for my tattoo device. I basicely replaced the framework.jar with mine.
... and indeed, it failed : I kept getting stuck at the boot screen everytime I do such.
So.... I am trying to understand what I do wrong.
- I am quite sure I miss some signing process, but although I read many threads about such a signing about apk files, I did not manage to figure out how to do this with frameworks / jar files. Could someone bring me some light about this?
- Provided the signing is not the (only) problem here, could someone explain where / why I am wrong?
- Eventually, since I did not manage to find full source for a FroYo-based (running) cooked rom , do you know of such a source repository I could work with instead of working with android official sources (including the framework java files + compatible with HTC-tattoo / HTC-hero if possible)?
Thanks for all of you for reading until here, whatever your answers (or silence) may be.
And thanks in advance to those who may have some answers or any constructive criticism.
Roger_Rabbit
--------------------------
An old fashioned rabbit
Hello,
first of all - I really used the Search function (for nearly a day) but I could not find any information that really helps me
second - sorry for my poor english, I am always on improving it
third - I already know some programming languages (C, Java, Perl, Python, a bit C++, ...), I already did some android app development and I have some knowledge of Linux internals (did some driver dev).
For my master thesis I have to tinker around with Android, the Linux Android Kernel and probably with the Dalvik VM. So I need as much information about Android internals (API internals, where information e.g. the telephone book are stored, Dalvik, architecture, ...) well and where better to start then here on xda.
So I wanted to ask if someone could provide me with information (papers, blogs, books, xda posts, ...) about how to start into rom development or android internal stuff. Of course I already downloaded the source still some additional information would be great.
Thx a lot - even if you just read my post
First you need Linux installed. I wouldnt recommend using linux on a virtual box for this, since you can have USB problems.
Go to this site: http://source.android.com/source/initializing.html
Read it through and perform every step all the way to the bottom, at the bottom it tells you to go to the next section which is where you download the source.
Basically, when you create a ROM, you have the android operating system, and the kernal for your device. Dont use any random kernel, you could potentially brick your device as I did with my Samsung Galaxy S II Skyrocket (they had to replace some board in the phone to get it to turn on again).
Thx a lot for this information. Does someone knows if there is some documentation of the Android Source ??
Thx
Has python been ported to Android ? I would love to run some Python 3.x scripts on my Android phone.
I searched the forums and this was last asked 2 years ago..
The python app here under Android Scripting, does'nt appear to be currently maintained.
http://code.google.com/p/android-scripting/downloads/list
The best I found was here however the Android api for Python appears limited at present.
https://github.com/kivy/python-for-android
dazdaz said:
Has python been ported to Android ? I would love to run some Python 3.x scripts on my Android phone.
I searched the forums and this was last asked 2 years ago..
The python app here under Android Scripting, does'nt appear to be currently maintained.
http://code.google.com/p/android-scripting/downloads/list
The best I found was here however the Android api for Python appears limited at present.
https://github.com/kivy/python-for-android
Click to expand...
Click to collapse
check out these two links. you need android scripting then install the python plugin
hope this helps. i've been using this for python scripts and you can use function from the phone like camera and stuff
http://code.google.com/p/android-scripting/
http://code.google.com/p/android-scripting/downloads/detail?name=PythonForAndroid_r4.apk
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
SL4A
You want Scripting Layer for Android. Once you've installed that, you can install Python, and other languages, from within the app. I think for Python, there's only Python2.6 at the moment, but it works very well, and your scripts will be able to import a module called android, which offers a pretty comprehensive Android API.
It's trivial to set up and you don't need root. I'd provide a link, but I only just signed up for XDA, so I'm not allowed yet. Just search for SL4A.
Hi.
I'm a java developer who wants to start to develop and learn cyanongenMod and AOSP. Start by saying that I have a good knowledge of Java and Android development but little knowledge of programming and debugging in C / C ++
I have readed all the documents from AOSP sites and following the guide found on source.android.com.I was able to setup Eclipse for all the Java applications
Pros: I can study the whole Java nature of Android and Cyanogenmod, using eclipse as a "code browser"
Cons; unable to edit the layout.xml (for example) and unable to use the Android feature of an eclipse project
It could be nice for Java developing, but for the others projects and OS parts there isn't a "IDE setup guide". I am a little bit confused about how the general development workflow goes. The build procedures for every device found at CM wiki are great but...after that?
How to develop, modify and debug a single Java Application on a real device?
How to develop, modify and debug a c/c++ driver or patch for a real device?
If I want to work only on a single Java application, I can't import it in Eclipse. If I want to debug on a real device (for example, the photosphere feature in Samsung Galaxy Tab 10.1 does not work), I can't setup a debug environment.
Where I can find a good guide-site-tutorial ?
I use this link whenever I get a new computer etc. This not only explains what to do but has all the download links and more. Good luck!
http://www.makeuseof.com/tag/write-google-android-application/
Sent from my Nexus 4 using xda premium
mellowdev said:
I use this link whenever I get a new computer etc. This not only explains what to do but has all the download links and more. Good luck!
Click to expand...
Click to collapse
My question is not about developing android application, but about developing android operating system. I find a lot of articles on makeuseof.org about installing cyanogenmod, for example. But no articles about developing cyanogenmod
sarbyn said:
My question is not about developing android application, but about developing android operating system. I find a lot of articles on makeuseof.org about installing cyanogenmod, for example. But no articles about developing cyanogenmod
Click to expand...
Click to collapse
Sorry but I think that is impossible that no CyanogenMod dev reads XDA forum.
If a noob want to find guide and tutorial and start develop for AOSP o CyanogenMod, where he can ask for help?
Ask from a dev in free xperia project. They develop cyanogenmod