Related
hello,
their seems to be a few posts on this being ported to BA recently. ow ive got linux running on my BA fairly well (havent got round to setting up gprs etc yet though but thats a different matter) and id be willing to try and get a port of android working, if someone can extract the 3 img files in the android sdk as ive not managed to do that yet ? anyone want to try and help or am i talking of a lost cause
ok, ill post this incase anyone is watching. i made some progress getting andriod running but i keep getting seg fault tryingto run it, any1 who could provide insight let me know pelase
Unfortunately I can't help you but I'll be keeping a VERY close eye on this thread!
Good luck, I'm sure there are a whole load of people who'd buy you a beer if you succeed.
Steve
glad to see someones watching . ill have another play around over weekend see what i can come up with
it will be interesting to see how android works on BA keep up with the good work
Nice.
I like my BA and I don't wont to change it until an open linux mobile is avaible (an open Iphone could be great).
Maybe a sub-forum called "Blue angel linux" could help.
I'm bored or a problem with the actual BA linux is the acces to the wifi chipset?
And this seems noise. And I don't want to pay for having linux on my BA!
http://www.a-la-mobile.com/news/press/pr080114.html
aperles said:
I'm bored or a problem with the actual BA linux is the acces to the wifi chipset?
Click to expand...
Click to collapse
Not the access, but a nice gui/setup.
remember linux is designed primarily for people who know what their doing. yes theirs guis now which help but you stil need command line to use linux properly. except on the iPhone and android from what ive seen
actually there was an earlier thread regarding android. and with 921+ adding 200+ views here, We bet there are people that are REALLY interested porting this.
hope we get it up and running.
anything for our BA.
even alternatives to WM6 are welcome.
well im not having a lot of look, it seems to be segfaulting pretty much constantly. think its down to the busybox shell though so im going to find a newer one and try that later, does anyone know what version of the arm feature set the BA uses. (because from reading http://benno.id.au/blog/2007/11/21/android-neo1973) android only seems to work on devices using ARMv5 featureset. whatever that means)
UPDATE: thats not a problem, the pxa263 in the BA is ARMv5TE so thats ok - gotta love wikipedia (http://en.wikipedia.org/wiki/XScale)
Further update: ok been reading up a bit more and im doing the risky thing of building my own kernel for android see if i can get round these damn segfaults
ok just thought id post up so people done think ive given up here . still havign issues compiling the linux kernel with the android addidtions. mainly because i ahvent got a proper linux machine at home (only virtual pc on this computer)...dont suppose anyone uses linux and has a decent knownledge of compiling kernels on here ??
DJ_Steve said:
ok just thought id post up so people done think ive given up here . still havign issues compiling the linux kernel with the android addidtions. mainly because i ahvent got a proper linux machine at home (only virtual pc on this computer)...dont suppose anyone uses linux and has a decent knownledge of compiling kernels on here ??
Click to expand...
Click to collapse
I've compiled kernels under Linux before, but not for an embedded system like the angel's.
Where did you get the tarballs for everything? And what distro of Linux did you install?
Really, real machine vs virtual machine, in this case, shouldn't matter. It might, but shouldn't.
not so much the fact im using a virtual machine, its the fact im only on a 2mb connection so downloading linux cd images takes ages and since debian is the only distro ive seen which has arm crosscompile tools that work that means 2 dvds or 9+cd images. most of the tarballs ive had to rip direct from the android sdk emulator. i could host them somewhere if someone wants to try and help me out getting a kernel running - after that i think most of android should fall into place on its own, but getting openbinder support in the kernels proving difficult
EDIT/UPDATE: ok just tried installing the arm crosscompiliers on my development dedicated server and it seems to be compiling a kernel as i type (hopefully) so looks to be some progress happening here
Been following your thread with interest.
I should be getting a new PDA from work, so then I could take the risk of bricking my trusty and battered Blue Angel.
Any chance you could post some links to the various bits you are using? Not a step by step (unless you have the time) but the starting points so others can attempt to duplicate your efforts in parallel?
Good luck - I'm rooting for you!
ok, im just tarballing up the files on my webserver now, didnt have any success with kernel, looks like im going to have to take the blueangel drivers etc from the kernel posted on handhelds.org and manually merge the config files into the android kernel image to get it to compile. unless anyone can suggest a way to do that easily (windows or linux routine i dont mind)
the main sites ive used to help out ive listed below
http://benno.id.au/blog/ << somewhere on their theirs a link to the android root filesystem image. (http://benno.id.au/android/system.tar.gz and http://benno.id.au/android/data.tar.gz)
http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html
http://euedge.com/blog/2007/12/06/google-android-runs-on-sharp-zaurus-sl-c760/
http://handhelds.org/moin/moin.cgi/BlueAngelKernel
the three above above links help even though their not scriptly related to android on blueangel
the rest of the files are in http://radiodmp.net/android-files/ - the 365mb file contains the 2 arm cross compilers and also both the newest blueangel linux kernel and the android kernel - as said above these need merging (android kernel needs to be the one that is the final kernel as its newer i believe
edit: ive just put the system and data tars linked above into the folder on my server also to save people time.
hope that helps
if anyone wants any help drop me a message and ill try and help out. will of course keep trying to sort it myself too
Any update on this?
Actively watching this thread and just wanted to know. I'd love to be able to play with Android.
good to see ppl interested. ive not had time to try and merge the kernels yet, hopefulyl might get chance this week
DJ_Steve said:
good to see ppl interested.
Click to expand...
Click to collapse
Still watching, still interested!
Keep it up.
Steve
ok managed to hack together the two kernels, compiling it as i type - hopefully it'll workon my BA
This thread discusses Linux for HTC Diamond and HTC Raphael
User resources
To get started with android real quick use this site http://wiki.xda-developers.com/index.php?pagename=RaphaelDonut
Further information on progress with Linux and Android and help can be found at the Raphael Linux wiki page.
Developer resources
The wiki of the htc-linux.org project has all the required uptodate research information http://www.htc-linux.org/wiki
If you want to contribute in the kernel porting project, please use this wiki.
The latest kernel code for Raphael, Diamond (and the other msm7xxxA devices) can be found in the htc-msm-2.6.27 branch of the linuxtogo.org git repository.
To view my signature, click my nickname to view the profile and then 'about me'
_______________________________
original post:
Hi,
Would be nice if somebody could try and test if the kaiser linux kernel boots on their diamond. Here's what you need
http://linuxtogo.org/~lgorris/kaiser-bootkit/
It has a small documentation but here's what you need to do again:
Get haret.exe, default.txt, zImage and angstrom-console on your diamond into the same folder, run haret.exe and tap run.
edit: the link above points to a website with kernel builds for the kaiser (msm7200). since diamond has msm7201A, it would be better to build directly from the android-msm-2.6.25 branch which has the halibut machine type. halibut is also an msm7x00A. there are some differences between the A and non-A msms.
google git is at
git.android.com
checkout the branch android-msm-2.6.25 ( it's most uptodate)
Click to expand...
Click to collapse
I have in fact been researching this since yesterday. The vanilla Android is for 7x00A devices, and should work on Diamond without too much fuss. I'm not a Linux developer though, so I'll need some help with that part. (though I am a developer)
The Kaiser boot kit does not work. Once it's done loading the device freezes entirely. Kaiser uses 7200 though, not 7201A, and for all I know it might actually be (partly somewhat) running, but with no frame buffer.
agreed with the freezing part.
From Haret:
WinCE reports memory size 134217728 (phys=118571008 store=115261440)
Where did the rest 64 MByte go?
Ok who's seriously interested in getting this to work?
Whats the progress so far? Lets try to get something packaged and up for diamond.
me
I am definately going to spend some time trying to gets this to work when I get my Diamond.
teddyen66 said:
I am definately going to spend some time trying to gets this to work when I get my Diamond.
Click to expand...
Click to collapse
I haven't been able to compile the kernel, but it sounds like you'll be able to. Give it a shot and I'll test it.
I'll test it too.
k, can you also try the vogue builds? http://it029000.massey.ac.nz/vogue/
http://wiki.xda-developers.com/index.php?pagename=DiamondResearch
the shared memory looks similar to the on on kaiser. So it will probably be easy to make communication with the phone work as soon as it works on kaiser. Of course you need to be able to boot first
Hi guys,
I've been trying to get Android running on my Diamond for a few days to no avail.
I've tried the Kaiser set of files and Vogue set of files. The furthest I've got is to make it display the 'Go Go Go...' message and then it hangs.
Has anyone actually got Android to run on a Diamond before?
Thanks.
Vogue does not work, but might be because of HaRET, don't know.
7201A is different from 7200. I would not expect it to work. However, the vanilla kernel is for Diamond type chips, so if anyone could compile a vanilla kernel it's worth testing. HaRET might need a few modifications though.
Very interesting!
This Android thing, getting it to run, what would the expectations be? Functionality, speed?
Just very curious, having once installed some linux-thingy on my magician.
I don't have a Diamond to test on, but I suspect the dev team for the Advantage could be of help. The build they have is running ok on Advantage, the touchscreen driver even works. No phone yet (last I checked). Maybe it will also run on Diamond?
nopes advantage is a different platform
I believe it'll just be a matter of time before we get a fully functioning Android build for the HTC Diamond because I can foresee it to be a very popular platform for the Android.
If there's any modifications to the default.txt boot file that would potentially make this work I'll be happy to try it out and let you guys know the results.
happyguy82 said:
I believe it'll just be a matter of time before we get a fully functioning Android build for the HTC Diamond because I can foresee it to be a very popular platform for the Android.
Click to expand...
Click to collapse
I hope that too . I can not wait to run Android on my Diamond.
I guess it'd be a matter of setting up a cross compile (toolchains - chroot, binutils, gcc, glibc) environment for the ARM, compiling the kernel with the correct drivers and bootstrapping for the ARM.
Am I right? Or did I miss something?
Would this link be of any help ?
http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html
I would like to get involved if someone is already working on it
Darn that's running smooth ...
... hope we can get some linux running on this hardware.
adwinp said:
I guess it'd be a matter of setting up a cross compile (toolchains - chroot, binutils, gcc, glibc) environment for the ARM, compiling the kernel with the correct drivers and bootstrapping for the ARM.
Am I right? Or did I miss something?
Click to expand...
Click to collapse
Well, kinda. Where do you intend to get "correct drivers" for Diamond
Its not that easy, since HTC doesnt provide 'em
Greetings all,
I would like to know something that seems to be so simple it hasn't been documented here anywhere.
My question is: How do I build the source provided by Google for my Desire HD?
Yes, there are tutorials, don't point me to them. They either provide you with the AOKP way or the CM way.
I want to build my stuff from scratch.
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I know about the vendor files, these are created by a third party. How do I know what vendor files I need to create? How do I know how to name them?
Don't get me wrong, I've used C, C++ and C# for YEARS (I think about 8 now) and I know how to code. I just don't know how to compile android!
It doesn't seem that hard though, I've seen threads where people provide ROMs for the Desire HD without even having the device!
Also, how would I test this and debug it? I don't think it's safe to just flash my rom once I get it compiled to my actual device and possibly brick it.. Can I use an emulator?
I hope you will read this post before answering something alike "Plenty tutorials" or "This can be found everywhere", because it can not. I can only find AOKP or CM ways, I want neither.
Greetings Ultimate-Tester
The only time I know of that this has been achieved for this device is aospX, an ICS ROM on the Inspire 4G forums. It is much harder than you would think. Google does not support this hardware, HTC does. So there was never AOSP source for this device.
Yes, I can imagine how hard it is. As I said I have programming experience, it's just that I don't have it with Android ROMS.
I have built mainly for Windows, also on Ring0 level (which is the lowest level you can get) so I think making drivers is a task I can handle. I am definitely not underestimating it.
Could anyone give me an answer to this line:
Code:
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I am very interested in how other people knew what folders to create and what files to put in them. How would the Google Source (envsetup) know which device files to use and what not? Again, can I generate the file structure somehow?
Greetings,,
My suggestion is to use device trees from AOSP-based ROMs that already exist for this device. For example, look in the cfX manifest.xml for Ace-specific stuff (kernel, device, etc.). I personally haven't seriously tried this before, so that's all I can offer.
Okidoki, will do. Then for the last item: Testing.
What will be a safe way to test out my brew?
What will actually happen if I flash a ROM with missing files? I hope there's an underlying catcher that will send something I can see in logcat and fix it that way.. Is this the case, or will I immediately brick my phone once I do something wrong? Do I need to make sure something is 100% there in order to reach my recovery again?
Greetz,,
I'm nor aware of any safety nets. If you're developing, you probably have to be willing to take the risks.
Continuing the discussion from Firefox OS is the way to go!
Hi guys!
I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.
I am following this guide: Porting Firefox OS
Currently I am stuck at the following: Create a manifest for the new device
[edit]
Which changes do I have to make to the hamachi manifest mentioned there?
I figured out, that most of the stuff is hamachi-specific and thus not required. My current manifest is attached. Could you please take a look and tell me, if this is enough?
These files are at hand:
madde on Fairphone Forum said:
Well there already is a recovery file for the fp1 + fp1u by chrmhoffmann up and running. The MTK6589 source code is kind of released and there has been a lot of work on the android code by the omnirom project, which might come in handy.
Should be definitely manageable to build and try out Firefox OS on the FP1. UnfortunatelyI'll just don't have the time to really dig into that. Maybe someone with a bit more experience can give it a shot. I'd love to see and try out the result...
Click to expand...
Click to collapse
I am inviting @madde-, @_keesj and @chrmhoffmann, I hope you, or others, can help me out.
Thanks in advance, Stefan
PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.
Edit: My current manifest is attached.
I'm very interested by a portage of Firefox OS to the Fairphone
Don't have enought time to test for now, but I stay connected
Newluck77 said:
Continuing the discussion from Firefox OS is the way to go!
Hi guys!
I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.
I am following this guide: Porting Firefox OS
Currently I am stuck at the following: Create a manifest for the new device
[edit]
Which changes do I have to make to the hamachi manifest mentioned there?
I figured out, that most of the stuff is hamachi-specific and thus not required. My current manifest is attached. Could you please take a look and tell me, if this is enough?
These files are at hand:
I am inviting @madde-, @_keesj and @chrmhoffmann, I hope you, or others, can help me out.
Thanks in advance, Stefan
PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.
Edit: My current manifest is attached.
Click to expand...
Click to collapse
Did you try your file out? I's think it's probably best to cut down on just the relevant settings.
madde- said:
Did you try your file out? I's think it's probably best to cut down on just the relevant settings.
Click to expand...
Click to collapse
Yes, the config.sh got stuck at like 93%.
Also I have no idea, what exactly I have to include into the manifest file. I think I need a toolchain, but I am not sure where to get one, and how to apply it. (I somehow know what it is though, I think... )
Ok, running the config.sh comes at the very end, so I probably should continue with the configuration tree[1]...
Does everything in here [2](@chrmhoffmann's repo android_device_fp_FP1) go to the configuration tree?
[1]: https://developer.mozilla.org/en-US/Firefox_OS/Developing_Firefox_OS/Porting#Create_a_configuration_tree_for_the_new_device
[2]: https://github.com/chrmhoffmann/android_device_fp_FP1
PS.: Sorry, not allowed to post links...
Newluck77 said:
Yes, the config.sh got stuck at like 93%.
Also I have no idea, what exactly I have to include into the manifest file. I think I need a toolchain, but I am not sure where to get one, and how to apply it. (I somehow know what it is though, I think... )
Ok, running the config.sh comes at the very end, so I probably should continue with the configuration tree[1]...
Does everything in here [2](@chrmhoffmann's repo android_device_fp_FP1) go to the configuration tree?
[1]: https://developer.mozilla.org/en-US...reate_a_configuration_tree_for_the_new_device
[2]: https://github.com/chrmhoffmann/android_device_fp_FP1
PS.: Sorry, not allowed to post links...
Click to expand...
Click to collapse
any progress on that? Might be able to help you a little bit in the next few weeks.
Cheers!
madde- said:
any progress on that? Might be able to help you a little bit in the next few weeks.
Cheers!
Click to expand...
Click to collapse
No haven't been able to work on this.
I still have no idea, where and how to build this configuration tree. Do you have advice on this?
Thank you, Stefan
Fyi, a build is now available. As a new user on XDA, I can not post link here (what a ****ty rule), but check bug 1139642 on bugzilla and search Fairphone on the Mozilla Developer Network (MDN) to have more info.
Wrong phone (FP1(U) vs FP2)
The build, you are referring to, is for FP2, not for FP1.
A Firefox OS for FP1 could possibly be built using the source by @chrmhoffmann: http://forum.xda-developers.com/fairphone/orig-development/rom-fairphone-fp1-kitkat-4-4-2-t3243623
Hi
I have asked this before but I haven't gotten the answer and some things have changed.
My goal is to edit the kernel of my device to include rtl8192cu driver.
I have the sources from http://gitgub.com/puresoul/android_kernel_lge_d605 (I hope I got the link right) I am currently stuck at creating the .config file and getting the right files to include the driver. Could anyone help me out, any links to tutorials that actually tell me how to? The guides online are almost all specific to a certain device or their goal is different.