Related
Hi, yesterday i was trying to launch android on my BA and i DID IT!
It works like ****:
Touchscreen doesn't work (you can activate list scrolling by pushing it on the side)
Some buttons don't work
No sound
Navigation:
D-pad (left, right, up, down)
Enter (on the keyboard, since D-Pad center doesn't work)
!WARNING! there is no end call and back buttons, you can't exit applications
How to? Here is the tutorial:
Create a folder on your memory card
Get the latest HaRET from here http://handhelds.org/~koconnor/haret/
Get the latest zImage from here http://www.angstrom-distribution.org/unstable/autobuild/htcblueangel/
(i use zImage-2.6.21-hh20-r16-htcblueangel.bin)
Rename it to zImage
Put that default.txt
Code:
set kernel zImage
set initrd "initrd-android.gz"
set CMDLINE "rootdelay=3 root=/dev/ram0 ramdisk_size=23504 init=/linuxrc"
boot
Now you need the system - Android
Get that: http://it029000.massey.ac.nz/vogue/initrd-android
Don't forget to rename it to initrd-android.gz
I've got it from here http://it029000.massey.ac.nz/vogue/
it stays in jumping to kernel... i followd the steps above, did you copy pasted the command correctly??
rafyvitto said:
it stays in jumping to kernel... i followd the steps above, did you copy pasted the command correctly??
Click to expand...
Click to collapse
Try different kernel. It works for me
GVG said:
Try different kernel. It works for me
Click to expand...
Click to collapse
Could you please tell us how did you install android on Blue Angel? Procedures and everything else. And also your opinion about it's performance. thank you very much
blackout_pt said:
Could you please tell us how did you install android on Blue Angel? Procedures and everything else. And also your opinion about it's performance. thank you very much
Click to expand...
Click to collapse
Just launch Haret.exe
Speed... hm... Almost like WM6
a lot slower than wm6 the android image should be tweaked in order to have proper drivers for touchscreen keys and sound
wow...very cool, I'll be looking for updates (if there are any)
hi friends,
i tested android and seems a good toy
i did make a rar with all files needed, you need only to extract to SD and run haret
Code:
http://rapidshare.com/files/147524450/android.rar.html
i'm really interested to go further on android.
about my tests, i can conclude two things:
- D-pad works, but not very well
- Touch screen is not working, but i know it detect moves on it
(try to dpad a icon, then touch the touch-screen, you ll see)
I'm not a expert on pocket pc, but i have my skills.
I found an other thing, hardware specification.
Code:
http://www.handhelds.org/moin/moin.cgi/BlueAngelHardware
if the information is right, the touchscreen is from the same family that the vogue one.
To continue this adventure, i need some lights. I know we have a developer from the kernel/Opie/GPE in this forum. If you are him, i need some lights about your work.
The other thing, i'll try to do is asking help to vogue/kaiser android project, to give me some lights how they touchscreen work.
The last thing. All the help is appreciated, everybody is invited in this project and all the help is welcome. And i really need it lol
udapte (23/9/2008)
Well i talk do vogue android project man, and the answer from him is simple. His work was only to port kernel to vogue platform. I will have to find who made the one we are using.
The touchscreen is detected, but somehow it doesn't work.
i have failed .
my BA get a FlashDIsk and ramdisk in WM6 enrironment..
when i run haret ....
after jumping to kernal
an error occur
can't mount SDcard .it's halt..
why...
How about your work? I'm working on this task also. Need more information to make it working. Could you give me some patches for BA's kernel.
Also the SC Card Message, any adivice o workaround?
w0w...
it runs on my BA. Great!
However I cant do anything inside. But thanks to all of you that make this possible.
I'm waiting for the next release, hope it will run faster, and all get better.
Thanks.
Is anything happening with this?
Any news?
Is vogue version working? I have try to build a kernel for BA but false to boot
Will try and report later....
kernel
I have A LOT of, like everything I could find, files to load linux on the Blue Angel. Angstrom, Familiar, QT...somethingsomething... Anyway, it works well except the wireless which I think should work until the thing goes into standby. Would the zImage/initrid files or any of the others help? I'd like to help ya get this working, I think most of the works been done. I must say, however, I am just learning about how this stuff works. I can't code, but I have a BA, lots of experience repairing hardware like ppcs and I really would love the chance to finally give back to this wonderful community after they've given me so much.
It would be great to get this working. It would give my pda2k a whole new lease on life.
any updates on this?
Thanks
so, any news? android would be quite nice.
i concur. i'd liketo see a android on the blueangel, why isnt there one? linux runs fine on it, theres an older android that supposidly boots on it.
cmon somebody make the damn thing work.
Due to a lot of newbie questions arising in the Kaiser forum lately, I've decided to open this topic. Maybe we can all contribute to it and also make it sticky. Hopefully it will prevent pollution of Kaiser Android forum with common newbie questions that were answered like 100 times already.
Here are some common questions I've seen lately, with answers. Suggestions and corrections are welcome. I invite all experienced Android users to contribute to this topic with their Q/A posts or maybe suggestions and corrections for my Q/A post.
Q: I'm trying to install Android, but don't know where to start and how to do it?
A: You have to options, SD install (keeps Windows Mobile on the device in case you change your mind about Android) or NAND install (it wipes your Windows Mobile of the device). Follow the guide for SD install here or the guide for NAND install here.
Q: Everybody is talking about DZO's repository for kernel (NBH/zImage) files. Where can I find it?
A: Here!
Q: Found the kernels but I'm confused now. Which kernel / panel should I choose for my Kaiser?
A: You will have to find out which panel type is your Kaiser using: 1, 2 or 3. If you pick wrong you will have errors on your screen. The best way to test is to start with an SD install, use zImage kernel and edit andboot/default.txt with the "board-htckaiser.panel_type" set to 1, 2 or 3, until you get the righ one for your Kaiser. User zenity wrote also about this here.
Q: I'm trying to do an SD install to ext2 partitions but don't know how to format SD card?
A: You will need an Ubuntu Live CD. Get it here. Then boot it and just follow this great video guide by user loserskater.
Q: I installed Android 2.1 (eclair), but camera and BT audio is not working. What am I doing wrong?
A: Camera and BT audio are currently not supported under Android 2.1 (eclair) on Kaiser devices. You could however use one of the older Android builds (Donut), like Myn's Warm Donut. Camera and BT audio are supported on most of the Donut builds, but keep in mind that quality is still not comparable to quality on Windows Mobile.
Q: How can I mount SD card through USB?
A: Here is the same problem with a solution.
Q: Which is the best Android build for Kaiser?
A: Hard question to answer. Actually there aren't many Kaiser dedicated builds. Luckily Vogue builds works on Kaiser, if you apply Wifi and BT updates (if they are available). You should probably try and decide by yourself. Keep in mind that older Donut 1.6 builds have camera and BT audio supported, while newer Eclair 2.1 builds have more functions and also better UI. Two very popular builds are Myn's Warm Donut and Incubus26Jc's Super Eclair 2.1.
Q: I installed Android but now everything is blurry.
A: It's due to wrong resolution. Kaiser phones have panel for 230x320 but you're probably using 320x480 build. Here is a post by user tatnai where he explains this situation for Vogue devices (it goes same for Kaiser).
Q: I have Android up and running. Now I need navigation software. Which one to use?
A: Well, iGo & iGo Amigo works on Android, so does Ndrive and Sygic. But you may bump into the resolution problem if you are using 230x320 and want to use iGo. Read this topic.
Q: My battery status is wrong. How can I fix this.
A: You need to "calibrate" the battery with your Android. Here is a guide made by user Millence.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'd also invite all Android newbies to go through Android Vogue FAQ topic as mostly it's all valid for Kaiser devices as well.
BT Audio work in the old polymod build. Use delta or gamma+BTUpdate.
Sd Install guide.
I just checked out the SDcard link its outdated, doesn't reference androidinstall.tar. Having l33t xperts direct n00bs to easy sounding guides which result in failure is a huge pet peeve, so please stop if your not even going to test your own advice. Newb's, like myself?, are having issues because we are trying to use haret or otherwise we are trying things reported to work, yet seem to have never been tried in recent times. FYI: Haret method is broke. If you don't believe me disprove me, please disprove me. Start from scratch, reference http://forum.xda-developers.com/showthread.php?t=680963. For now it seems that sdcard/nand not using haret is the only way to get a working droid w/ sound and everything. That guide is here: http://forum.xda-developers.com/showthread.php?t=680963, but I haven't gone that route as I like my winmo. The furthest I got with haret was booting droid w/o sound and no one has been able to offer any advice that i haven't already tried. I tried a bunch of different kernels, a few different radios. Please prove me wrong I think requiring users to nuke their winmo when android is still beta and lacking drivers is insane. (i.e. my winmo takes about 6hours to install and tweak everything and I use it regulary, why should i have to wipe it just so I can preview the development progress?)
thebulletfromhell said:
BT Audio work in the old polymod build. Use delta or gamma+BTUpdate.
Click to expand...
Click to collapse
I almost forgot that BT audio works on polymod. Couldn't we just take the fix and apply it to other Eclair builds like Incubus26Jc's Super Eclair or mssmison's CM 5.0.7 test 3?
tyler51773 said:
Newb's, like myself?, are having issues because we are trying to use haret or otherwise we are trying things reported to work, yet seem to have never been tried in recent times. FYI: Haret method is broke. If you don't believe me disprove me, please disprove me.
Click to expand...
Click to collapse
I'm Haret booting every day. It works. With sound. On some builds also with camera and BT. But you're right - the links are outdated, it's for the old SQSH method - sorry. Can't find any newer in-depth SD install guide (if somebody knows one please post a link) but here is a quick quide by user tatnai that works.
However I believe Android on Kaiser is still not ready for prime-time use. If you need a stable OS where everything works as it should, you should stick to WinMo at least for a while. You want to contrubute do developement? Welcome. If you have a problem / question? That's what forum is for and we will help you if we can.
I made this FAQ in a good faith to help users start - I had problems starting Android on HTC also when I first decided to do it. But I tried & tried, read the forum throughly and eventually I succeeded.
Android on Kaiser is still in developement and things change on a daily basis. Thta's why forum is for, so we can discuss that and help each other.
Versioning?
Maybe its cause I've used the newest sources or because my hardware is different, would be nice to know either way what it is that causes me not to have sound. I basically did follow that guys guide, but I'm still sol. Can you download the newest ones and give it a go? If it works then I'll follow your instructions, if not can you backtrack which sources you used so perhaps we can do a diff on it to see what needs to be done? Please check out the http://forum.xda-developers.com/showthread.php?t=680963 and post a solution if you can come up with one that produces an android w/ sound via haret, about 3-7 of us who have posted there would appreciate it, and god knows how many others who are keeping their mouth shut as well.
tyler51773 said:
Maybe its cause I've used the newest sources or because my hardware is different, would be nice to know either way what it is that causes me not to have sound. I basically did follow that guys guide, but I'm still sol. Can you download the newest ones and give it a go? If it works then I'll follow your instructions, if not can you backtrack which sources you used so perhaps we can do a diff on it to see what needs to be done? Please check out the http://forum.xda-developers.com/showthread.php?t=680963 and post a solution if you can come up with one that produces an android w/ sound via haret, about 3-7 of us who have posted there would appreciate it, and god knows how many others who are keeping their mouth shut as well.
Click to expand...
Click to collapse
Let's try it like this.. Here is the link to copy of my andboot folder, with incubus26jc's & Vilords Tattoo Sense Android androidinstall.tar build for Vogue and Kaiser. This one is native 240x320 with working Wifi and Camera on Kaiser. Latest dzo's zImage is included. This one works for me superbly. Build still lacks support for BT but I think it will be solved soon.
http://dl.dropbox.com/u/72524/andboot.7z
Download it and install it. Before installation change (in default.txt) panel setting "board-htckaiser.panel_type=3" to your panel type and also set "board-kaiser-battery.battery_capacity" parameter to 2000 if you're using 1350mAh stock Kaiser battery. Please report if your sound works with this configuration. Hope it helps.
Two things....one can we get a Tutorial for how to revert back to WM? Also can we get an admin to make this sticky!!??
toolfan2k4 said:
Two things....one can we get a Tutorial for how to revert back to WM? Also can we get an admin to make this sticky!!??
Click to expand...
Click to collapse
If you have flashed winmo ever before, you shouldnt have a problem. just boot into the bootloader and flash as usual.
i install system in NAND and data in ext2
but when i check in my sd (windows only can detect fat32 format),
data.img in my sd. it is normal?
You suppose to put data on sd card partition. Its kinda confusing.
thebulletfromhell said:
You suppose to put data on sd card partition. Its kinda confusing.
Click to expand...
Click to collapse
i cant understand?
i wnt data in ext2. so android can run faster
but when i check my fat32 partition, data.img in this partition
should i put androidinstall.tar in my ext2 partition when i install??
Select Data On SD Card Partition. The Other Option Make Data.IMG(which is formatted in ext2)
thebulletfromhell said:
Select Data On SD Card Partition. The Other Option Make Data.IMG(which is formatted in ext2)
Click to expand...
Click to collapse
i cant choose NAND and SD partition...
only can choose NAND and ext2
Still no sound.
I get the same series of errors every time. (The slide that is most specifc to sound, i.e. ept error)
milanche said:
I'm Haret booting every day. It works. With sound. On some builds also with camera and BT. But you're right - the links are outdated, it's for the old SQSH method - sorry. Can't find any newer in-depth SD install guide (if somebody knows one please post a link) but here is a quick quide by user tatnai that works.
However I believe Android on Kaiser is still not ready for prime-time use. If you need a stable OS where everything works as it should, you should stick to WinMo at least for a while. You want to contrubute do developement? Welcome. If you have a problem / question? That's what forum is for and we will help you if we can.
I made this FAQ in a good faith to help users start - I had problems starting Android on HTC also when I first decided to do it. But I tried & tried, read the forum throughly and eventually I succeeded.
Android on Kaiser is still in developement and things change on a daily basis. Thta's why forum is for, so we can discuss that and help each other.
Click to expand...
Click to collapse
Hey milanche, thanks a million for making this FAQ. It has been very helpful for me. I am LOVING android on my Kaiser! I got a sweet sweet taste of it when using my friend's X10 and was HOOKED. Now, I'm HOOKED UP!!!
deezy7?
Deezy, are you using haret? Did you get sound off the bat?
The 'local ept for program xxxxx' error is normal, as are the first ones about tty and job control, I see these 'errors' every time I boot, and it seems to have no effect, the rpc ones i get sometimes, usually followed by a load of FC's once android starts, the init sys_prop ones I have seen before also, with the same results.
Basically once this happens I have to pull the battery and reboot, which usually fixes things, in my case that is.
However I'm beginning to wonder if there is something more serious going on with your device, having followed your trials it seems that no matter what you try you are dogged by bad luck, I'm sure it's not you, or that you are making mistakes, simply that, for whatever reason, android hates your Kaiser.
Sorry I can't be of more help, this one simply baffles me.
@tyler51773
Did you try this: http://forum.xda-developers.com/showpost.php?p=6570064&postcount=7
And what were the results?
what option i have to take if want install system in NAND and data in ext2??
because when i choose system on NAND and data on ext2, my data.img will go to my SD
I need your help with creating a sqsh(or ext2) file with latest build of Froyo Android.
I tried to do it but as a result Vogue Linux(HaRET) can't mount it and also the job control is off(there is no way to turn it on without correct keymaping)...
Application that I used for making sqsh file is mksquashfs.exe .
I've already heard about a ext2 file format, that is better and faster...
I don't have any idea how to operate this files, etc., etc...
P.S. Sorry but I can't post links, you will must to search for it
mafiu95 said:
I need your help with creating a sqsh(or ext2) file with latest build of Froyo Android.
I tried to do it but as a result Vogue Linux(HaRET) can't mount it and also the job control is off(there is no way to turn it on without correct keymaping)...
Application that I used for making sqsh file is mksquashfs.exe .
I've already heard about a ext2 file format, that is better and faster...
I don't have any idea how to operate this files, etc., etc...
P.S. Sorry but I can't post links, you will must to search for it
Click to expand...
Click to collapse
There is already one made. Be patient, and I will post a build with it.
Really Thanks for this
P.S. The answer was "quite" fast
ETA of complete FroYo build for TP2?????????????
i should have never given my vogue away
fadimo305 said:
ETA of complete FroYo build for TP2?????????????
i should have never given my vogue away
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=627997
Hi developers,
i have a big question:
I read some time ago, that it is possible to install android on NAND of the HD2.
My question is : is it possible to install it on the NAND on the Touch Pro?
Because it is really slow, if i run android over MicroSD card, and it would be awsome ,when android runs faster.
Best regards,
BikerBoy030
At the moment (and to my knowledge) the answer to your question is no. User e334 tried but failed and bricked his phone. You can read more about his attempt in THIS thread. He was attempting to find out a few values that are apparently required but he did leave a few hints of his findings in that thread.
By the way, what version or build (neopeek-variants or xdandroid) are you using and have you updated everything to reflect the latest that is out and relevant.
brick !!! too sad
So, is this the end of hope for NAND on touch pro ???
pls somebody told me !!!
For now, yes :enter sadface of choice here: However, the xdandroid dev team are steadily working at improving stability and adding features some doubted at first; such as camera which is, in testing phase atm. The only thing I can say is that, "it ain't over till it's over!"
n-Joie! (Enjoy)
BikerBoy030 said:
I read some time ago, that it is possible to install android on NAND of the HD2.
My question is : is it possible to install it on the NAND on the Touch Pro?
Because it is really slow, if i run android over MicroSD card, and it would be awsome ,when android runs faster.
Click to expand...
Click to collapse
Just FYI, NAND will not provide any improvements in speed. The optimizations really need to happen in the system, moving to NAND will not solve those problems.
The HD2 guys had a ridiculously complete port of Android when they were still on Haret. We're still not near that stage.
They have it easy, they just rip builds from Desire, etc...
thanks for the fast answer:
that is really sad, that he briked his phone....this is such a sweet phone
I used xandroid, updatet all and could use all programms etc.
But it wasn't smooth...it stocks a bit at all,what it did.
It feels like it used a "bullet-time-mode"
Maybe it would be enought if i willl overclock it to 710 mhz this COULD be enought, but i didn't tested it.
Wich version is more smooth: neopeek or xandroid?
Regards:
bikerboy030
To my knowledge, OC'ing will not help stability. If anything it will make it more unstable. Neopeek builds seem smoother but requires more setup time upfront (multi-partitions and what not). XDAndroid builds may seem rocky at first but are much quicker to setup and it has a nice plug-n-play feel.
n-Joie! (Enjoy)
i had no problems with the stability, it was only too slow.
than i will try neopeek, maybe it feels better.
the problem is: a good friend owns a desire z, overclocked to 1400mhz...that is smooth.....
but if the touch pro works smooth, it would be fine
Well, i can be totally honest to say as far as speed, that XDA android runs quicker then WM does even on my touch pro. I am running wm6.5.5 NRG rom (jan.4), which is pretty zippy to a month ago version of 6.5.5, noticably, but android is actually visually faster. Now that camera is working fine, battery i get around 7-8 hours with little less then normal usage, and would honestly use it SOLELY if it didn't randomly drop data and needed a reset to fix (which i usually just stay in WM when it happens.), but ALSO mostly since at work (IT Tech) i use tethering a lot to grab a driver almost daily (our net connection is 'clear' and is a bit worse in speed then my phone. SAD yes.)
Hmm ... I'm one of those people who eagerly await with great versions of NAND. What exactly is needed to it came to Raphael? Of course, I'm not asking for what must have been fixed and asking, I assume that in theory it already is. Let me add that I've read about, whose founder bricked his Raphael.
Bootloader is required.
Corias said:
Bootloader is required.
Click to expand...
Click to collapse
Ok, I'll ask differently. What is needed to create this Bootloader for Raphael?
GoldAngelo said:
Ok, I'll ask differently. What is needed to create this Bootloader for Raphael?
Click to expand...
Click to collapse
Knowledge of how to write a bootloader? What do you mean?
We have one called tinboot that dzo wrote for the vogue guys. That's what the RHOD is using, but A LOT of work needs to be done to get it to work on other devices. It's not even a full NAND flash for the RHOD....
arrrghhh said:
Knowledge of how to write a bootloader? What do you mean?
We have one called tinboot that dzo wrote for the vogue guys. That's what the RHOD is using, but A LOT of work needs to be done to get it to work on other devices. It's not even a full NAND flash for the RHOD....
Click to expand...
Click to collapse
I would like to know what is needed to version NAND and how this process (creating nand and tools that you need, such as the bootloader and other ) should follow you. Of course, theoretically. Perhaps someone from another country would take on this (not everyone knows looks at XDA;-) maybe after the publication of the national forums that someone will take).
GoldAngelo said:
I would like to know what is needed to version NAND and how this process (creating nand and tools that you need, such as the bootloader and other ) should follow you. Of course, theoretically. Perhaps someone from another country would take on this (not everyone knows looks at XDA;-) maybe after the publication of the national forums that someone will take).
Click to expand...
Click to collapse
I'm no dev, so I won't be able to help you out directly. But look up tinboot, and look at what us TP2 guys have for a NAND bootloader thus far.
ACL has a GIT repo for our NAND tree that is publicly available as well.
We started talking about Raph and Diam nand in the Blackstone thread somewhere around here: http://forum.xda-developers.com/showpost.php?p=11051880&postcount=124
I've compiled the kernel for blackstone-nand and will try to flash this onto my diamond tonight or maybe tomorrow. Wish me luck
detlef25 said:
We started talking about Raph and Diam nand in the Blackstone thread somewhere around here: http://forum.xda-developers.com/showpost.php?p=11051880&postcount=124
I've compiled the kernel for blackstone-nand and will try to flash this onto my diamond tonight or maybe tomorrow. Wish me luck
Click to expand...
Click to collapse
I wish you a lot of luck
If you succed please share your values,maybe we can make it to boot ext2 partition bulids
Is 512 MB of Raphael's internal NAND enough for Android?
Corias said:
Is 512 MB of Raphael's internal NAND enough for Android?
Click to expand...
Click to collapse
More than enough, I thing the G1 had like 192 or something.
arrrghhh said:
More than enough, I thing the G1 had like 192 or something.
Click to expand...
Click to collapse
Yeah,a build is about 150 mb
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.