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
I'm new at these forums, I came here for tips & advice to learn how to get rid of all the T-Mobile branding from my HTC Desire HD. With no technical experience of such devices (other than standard use) I soon found out there was a lot to learn.
The purpose of this thread is to get as much information for myself (and other newbies) to learn about the technical terms used, all in one place.
Would anybody be so kind as to offer plain English explanations of the following words/phrases.
Although I have a little understanding of some of these words/phrases, I have had trouble in the past so I am listing them for the benefit of others;
S-OFF/S-ON
HBOOT
ENG
Root
Flash
ROM
Radio
ClockWorkMod
CyanogenMod
RUU
BootLoader
Kernal version
Build number
Superuser
I think this is all for now. If you are also a newbie, feel free to post more related Jargon here to help build an all-in-one jargon busting thread!
I am my no means an expert but will try and help as much as I can.
S-OFF/S-ON - Security On/Off, this is to do with being able to write to protected parts of the device memory.
ENG <----This is the custom HBOOT that is part of the security work around ^^
ROM - Read Only Memory, usually this is the operating system that you are installing, eg LeeDroid or CyanogenMod.
Radio - Is the software used to link the hardware to the operating system.
ClockWorkMod - A custom recovery image that is used to install new roms, also allows you to do backups of the existing rom (operating system) before upgrading or patching.
CyanogenMod - A team of people developing an AOSP (Android Open Source Project) rom. It has no "sense" from HTC and is very minimalistic, usually very fast and stable.
RUU - (ROM Update Utility) The stock rom installer, use the correct one to return your phone to stock, usually used for returning to the manufacturer.
Build number - The version of the software you are looking at, usually it is in chronological order.
I have not answering the one's I know nothing about, better to wait for someone with more knowledge to come along. I may not be 100% correct, I am sure someone will correct me if I am wrong.
Good luck.
Blinky
Thanks Blinky!
On another thread CitizenLee pointed me to a website that contains a lot of the jargon and their descriptions! I found this unbelievably helpful. Here it is guys;
http://www.villainrom.co.uk/vBwiki/index.php/Glossary_of_Android_Terms
Very nice site, have bookmarked that myself, cheers.
06/16/2011
The screenshots are not important. This is not a theme!
You can install a theme from here, for example if you like.
The theme it comes with is the:
Go Louncher Classical Theme (The new version of it)
The software installed is also not important, because you can remove it.
Google Market is installed, and you can install what ever you like, just like on your computer.
https://market.android.com
This is the actual Android Froyo operating system for the HTC Kaiser
So, stop asking me for screenshots and software installed, it's not relevant.
And the how to install guide is been posted here
Bug reports are welcome, other then that, I don't wont to hear from you.
Don't post a thank you either, there is a bottom for that, and you can also vote on the poll up there, but install and test it first!
Again Bug reports only, please!
I been working on this for 3 days straight, and figure I'll share what I got.
Everything seems to be working, except the camera is blurry, but that seams to be the norm.
Included is the rom, radio and kernel
ROM: 2.2.1
Kernel: 2.6.25
Radio: KAISER 1.70.19.09
Panel: 2
Key Map: US Normal
Resolution: 240x320
Storage: Nand & Nand
Most everything is installed in userspace and can be uninstalled or upgraded.
Oh got GO Launcher EX installed (Also in user space)
Credits:
I stole ideas from, and used following tools:
Makers of atools
Makers of NBH creator
HTC Flasher
kallt_kaffe
Krazy-Killa
dzo (dzo's posts wore a big help. just wish he would answer his own questions after he found the solution)
n2rjt
and many more.
@todo
Resize NAND partitions to the smaller system size
Original post and download Links are posted on my blog:
http://press.pzzazz.net
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
MaRekRM said:
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
Click to expand...
Click to collapse
Yeah witch apps are include. Some yours tweaks or etc... ???
MaRekRM said:
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
Click to expand...
Click to collapse
That sounds like a trick question.
Yes, at first I compiled everything my self but then to resolve bugs, I looked at other systems and basically stole stuff from them to fix my bugs. In other words, I can't take all the credit, it was a community effort.
Neo2SHYAlien said:
Yeah witch apps are include. Some yours tweaks or etc... ???
Click to expand...
Click to collapse
I removed most everything from the system and installed it in user space. So the system is very lean. You can uninstall what you don't like.
how is the rom？just waiting to see
gruessle ...!! thanks for your efforts in getting this done... I been looking from long time to install Android on my HTC TyTN II. However i was not able to get the proper build...
can you share the screenshots of the build which you provided as well some steps at high level on installing this..
Thanks in advance.
Please, I don't really understand how to go upgrade this. I find it hard to do. Is everything needed packaged in this download, or please can u list things needed to change to android. I'll appreciate your response.
tundelogic said:
Please, I don't really understand how to go upgrade this. I find it hard to do. Is everything needed packaged in this download, or please can u list things needed to change to android. I'll appreciate your response.
Click to expand...
Click to collapse
here is the howto
http://forum.xda-developers.com/showthread.php?t=680518
kkp said:
gruessle ...!! thanks for your efforts in getting this done... I been looking from long time to install Android on my HTC TyTN II. However i was not able to get the proper build...
can you share the screenshots of the build which you provided as well some steps at high level on installing this..
Thanks in advance.
Click to expand...
Click to collapse
The screenshots are not important.
This is not a theme.
You can install a theme from here, for example if you like:
http://golauncher.goforandroid.com/category/themes/
The theme it comes with is the:
Go Louncher Classical Theme (The new version of it)
The software installed is also not important, because you can remove it.
Google Market is installed, and you can install what ever you like, just like on your computer.
https://market.android.com/
This is the actual android froyo operating system.
Anyone else having trouble getting the kernel to install?
I get to 33% and the phone reboots...
Radio installed fine even though I was already using 1.70.19.09, just to be sure I installed everything in the package.
Installed HardSPL 3.34 and a WinMo 6.1 rom (custom) to see whats wrong. Installed L1q1d's kernel and goes right in like it should.
Checked .NBH with NBHCreator and only found 1 thing wrong: kernel set to Eclair instead of Froyo. Changed to Froyo and saved, attempted reflash and still won't go in...
;(Losted);
I also tried to install this kernel but I can't. Flashing in hardspl after few second give folowing error:
00018003
Os Fail
Update Terminate
UPDATE Fail.
Changing parameters in atools not helping. Every another kernel is flashing without problems so it's not phone fault
Gruessle, thanks for your efforts! I want to try your rom but being a noob waiting for more comprehensive list of known errors before flashing it to my kaiser.
Ok, quick "bug report":
After working with the kernel pack multiple times I have come to the conclusion that there might be a bug in the actual kernel file itself, throwing a code back to HardSPL and RUU (how I install).
I first noticed a problem in that the kernel was originally set up for a Polaris and had no resolution set. The size of the file should be unimportant as Scoot's newer kernel is in the order of 3.2-3.3MB in size (with the RIL patch installed it gets even larger), this one is 3,099KB, and l1q1d's is almost always 3,092KB.
The second issue I noticed is with the Froyo package itself... It's split up into many files (open the package in 7zip and you'll see what I mean). Normally, the packer has the files all listed inside the .tgz file, this one has the files inside many other files.
I have thus not installed the system on either phone because (correct me if I'm wrong), the kernel contains the basic directories for where everything is installed, and if I were to try and install this package on say, l1q1d's kernel, the phone would most likely crash because the files would not be found, including /system.
If ANYONE wants to dig deeper into this problem, feel free to message me. Personally, I think we've about finished getting all we can from the Kaiser, and much respect goes out to those who have done all the work in the past, but there's always that glimmer of hope that someone will find a way to pack this into a working rom installable through RUU or HardSPL.
I have one last thing to say:
Gruessle, please do your homework BEFORE posting things like this. There are people out there who still depend on this phone to operate as it is their only phone. I Personally cannot afford to go spend $100-200 on a replacement phone if this one goes down (thats why I have 2 of them). If you post something that does not work on the platform that you say it will, please correct it or move it to the proper forum.
BTW, I call shenannegans on one of the 5-star votes... just sayin'.
Your kernel have fake ;/ . rom works great ;D
sorry for bad english;p
PoXFreak said:
Ok, quick "bug report":
After working with the kernel pack multiple times I have come to the conclusion that there might be a bug in the actual kernel file itself, throwing a code back to HardSPL and RUU (how I install).
I first noticed a problem in that the kernel was originally set up for a Polaris and had no resolution set. The size of the file should be unimportant as Scoot's newer kernel is in the order of 3.2-3.3MB in size (with the RIL patch installed it gets even larger), this one is 3,099KB, and l1q1d's is almost always 3,092KB.
The second issue I noticed is with the Froyo package itself... It's split up into many files (open the package in 7zip and you'll see what I mean). Normally, the packer has the files all listed inside the .tgz file, this one has the files inside many other files.
I have thus not installed the system on either phone because (correct me if I'm wrong), the kernel contains the basic directories for where everything is installed, and if I were to try and install this package on say, l1q1d's kernel, the phone would most likely crash because the files would not be found, including /system.
If ANYONE wants to dig deeper into this problem, feel free to message me. Personally, I think we've about finished getting all we can from the Kaiser, and much respect goes out to those who have done all the work in the past, but there's always that glimmer of hope that someone will find a way to pack this into a working rom installable through RUU or HardSPL.
I have one last thing to say:
Gruessle, please do your homework BEFORE posting things like this. There are people out there who still depend on this phone to operate as it is their only phone. I Personally cannot afford to go spend $100-200 on a replacement phone if this one goes down (thats why I have 2 of them). If you post something that does not work on the platform that you say it will, please correct it or move it to the proper forum.
Click to expand...
Click to collapse
1) The kernel doesn't care where you place the files. Right now I use a debian system with Ferora and Gentoo in a chroot. Both work fine with the Debian kernel.
In other words, if you have a kernel that works for you then use that it should work with the rest of the installation.
2) I don't get what you mean with files are "split up into many files", I am just guessing but you must be extracting it wrong. Maybe it's a windows thing, I haven't used windows in 15 years so I wouldn't be able to help you with that.
3) I have included everything you need to duplicate what I got, which works for me, and it appears to work for others too. Now i don't use that phone much, and there might be bugs I am unaware of, but don't tell me it doesn't work at all, just because you can't get it to work.
barmalini said:
Gruessle, thanks for your efforts! I want to try your rom but being a noob waiting for more comprehensive list of known errors before flashing it to my kaiser.
Click to expand...
Click to collapse
barmalini, it appears that a few people have trouble installing the Kernel, but the ROM seams to work for everybody as far as I can tell.
According to my server records the files have been downloaded over 200 times and I have yet to hear a complain about the ROM.
So I would say try to install the Kernel, but if you can't still use the ROM with a Kernel that works for you.
If you have trouble installing from windows you can also try a live CD from debian or knoppix. I installed everything from a Debian system. (Knoppix is based on Debian)
If you don't know what a live CD is then go here for info:
http://wiki.debian.org/LiveCD
PoXFreak said:
Installed HardSPL 3.34 and a WinMo 6.1 rom (custom) to see whats wrong. Installed L1q1d's kernel and goes right in like it should.
Checked .NBH with NBHCreator and only found 1 thing wrong: kernel set to Eclair instead of Froyo. Changed to Froyo and saved, attempted reflash and still won't go in...
;(Losted);
Click to expand...
Click to collapse
PoXFreak,
you are not the only one having trouble, installing the ROM it appears.
I am wondering, are you also using Microsoft Windows to install the ROM?
If so can you try again with Linux, because it worked fine for me.
If you don't have Linux you can use a Live CD
Also if you can't get it to work, try the ROM with a Kernel that works for you.
Please report, I will check back.
Dear All,
I have recently got a new gts2. This is my first time using and Android phone. So may be you can guess that I am pretty naive and amateur in terms of all the technical stuff.
I have some questions that I would like someone to answer. (Although the questions might be very silly and simple for some).
What is lightening rom?
Should I flash or stay on what I have
How do I change to lightening rom (the procedure)
Which one is the best
What is Kernel and can I flash any kernel?
my android version is 2.3.3
kernel is 2.6.35.7 - i9100xxwkdd (dont know if this helps)
gingerbread.jpkg2
A detail reply would be really appreciated.
Thanks
1. The name of the rom. Called this because it is claimed to be fast as lightening.
2. If you're satisfied with it, then stay. If not, then change.
3. See here: http://forum.xda-developers.com/showthread.php?t=1095274
4. No answer. Reason: Different people have different opinions/preferences. I may not like one which you may like.
5. Did a quick search and found this: "An operating system kernel is the piece or pieces of software that is responsible for servicing resource requests from applications and the management of resources. A kernel has facilities to receive resource requests and grant access to resources such as allocating space for a new file or creating a network connection. To generalize, kernels use a system call (or syscall) interface to handshake with applications."
No you cannot flash any kernel. You have to flash a kernel made specifically for your device.
Thanks my friend. I really appreciate your efforts for replying to my question.
What specifics per device are needed to "match" roms to attempt a port or create cust
I'm pretty new at all this buy the basics of installing already made roms I get my question is when attempting to create new custom roms what information about the device say (cpu, gpu, modem, kernal, etc) need to match up to attempt using or moding those said parts of the dev process in order to build a working tree. Continued below Sidenote........
Sidenote : idk if the terms I used were correct in there placement or meaning but I feel that any who will reply to this thread probably grasp what I'm getting at.
So essentially what I'm attempting to do is figure out what things to change and how to change them in order to figure out what goes into building a rom or the favorable option that I'm shooting for is what to look for to attempt to match up a already built custom rom from another device I need little to no changes in order to use on my device's, reason being, both devices I am currently woking on, which are a Samsung Galaxy Core Prime sm-g360t and a HTC Desire 626s, do not have a official or even, to my knowledge, have an official CM and honestly besides one,the HTC which I have TWRP and it's running now off the AdvancedStock rom I found on this site and it keeps wanting to break or just doesn't work the way I want .
ANY HELP IS GREATLY APPRECIATED