Jump to content

Flash on T-Mobile Pulse?


Guest BigBearMDC

Recommended Posts

Guest BigBearMDC
Is using 9.10 not a good idea when cooking roms then?

I'm using 9.10 and at the moment just installing everything so I can lend a hand and maybe add this into my motoblur rom im after

I thought that using 9.04 is better than 9.10 (because of gcc).

gcc 4.4 (Ubuntu 9.10) is too strict - gcc 4.3 (Ubuntu 9.04) is better.

Thats why i wanted to uninstall gcc 4.4 from Ubuntu 9.10, but - typically for Ubuntu i think - there were many problems with dependencies, so Ubuntu uninstalled nearly everything (even Gnome!).

And i didn't know that it is that easy to set gcc 4.3 as the default compiler instead of gcc 4.4 - so I installed Ubuntu 9.04.

But i think you should be fine if you use Ubuntu 9.10 if you follow the instructions of jimmL.

UPDATE:

Something strange happened i think.

But first, thats what i tried:

I downloaded the android 1.5 r4 source, the HTC Hero kernel source and the Pulse kernel source.

I copied the drivers from the Pulse kernel into the Hero kernel (except of input.h and input.c -> maybe multitouch?).

Then i compiled the kernel (that took me 3 hours!!!).

It compiled without any errors.

Ok then i tried to compile android.

Well I got not a single error.

But i took only 1 minute to complete ?!?

So i thought ok, lets try it anyway.

So i tried to make my boot.img - but wait - where is the kernel???

It should be in /kernel/arch/arm/boot - but it isn't.

So i used the search function to search the kernel (i searched zImage).

And i really found a file called zImage... but in the powerpc folder instead of the arm folder?!?

Alright, I just wasted my time... I'm downloading the 1.6 source at the momnent.

I'll compile it when it finished downloading.

Stay Tuned!

Greetings,

BigBearMDC

Link to comment
Share on other sites

So this is Flash player from Hero on Pulse? You say 1.6 kernal, I dont know anything to do with this stuff, but does this mean your creating a custom rom of 1.6 android for Pulse??

Or will it still be 1.5 with parts of 1.6?

:)

Edited by Spooke
Link to comment
Share on other sites

Guest BigBearMDC
So this is Flash player from Hero on Pulse? You say 1.6 kernal, I dont know anything to do with this stuff, but does this mean your creating a custom rom of 1.6 android for Pulse??

Or will it still be 1.5 with parts of 1.6?

:)

Well if that what I'm compiling at the moment works, we would have android 1.6 on the Pulse.

But thats nothing really new. Android 1.6 already runs on the Pulse, but major parts of the HW don't work.

What I'm trying to find out is if flash works when i compile my android with the Hero kernel.

I think if i can manage to compile android without any errors it should run on the Pulse - and flash should also work.

But at the moment i think I'm going to have some problems compiling android.

When flash works with the Hero kernel, I'll try to port the necessary files to our Pulse ROM (it should be android 1.5 then).

Stay Tuned!

Greetings,

BigBearMDC

Link to comment
Share on other sites

Guest BigBearMDC

UPDATE:

Hell NO!

What am i doing wrong?

I compiled the kernel (took me ~3h again - it should take about 45 mins...).

That created a system, ramdisk and userdata.img (all in all 48MB) but no kernel?!

Compiling android finished in 1 minute again!?

So i have a system.img, a userdata.img and a ramdisk.img.

But wheres the kernel??

I did exactly the steps that are discribed in the "1.6 ROM development" Thread

(except that i used a 1.6 kernel).

I don't know what I'm doing wrong :)

Please help me!

Greetings,

BigBearMDC

Edited by BigBearMDC
Link to comment
Share on other sites

UPDATE:

Hell NO!

What am i doing wrong?

I compiled the kernel (took me ~3h again - it should take about 45 mins...).

That created a system, ramdisk and userdata.img (all in all 48MB) but no kernel?!

Compiling android finished in 1 minute again!?

So i have a system.img, a userdata.img and a ramdisk.img.

But wheres the kernel??

I did exactly the steps that are discribed in the "1.6 ROM development" Thread

(except that i used a 1.6 kernel).

I don't know what I'm doing wrong :)

Please help me!

Greetings,

BigBearMDC

To me it sounds like the first time you're compiling the "kernel" you're actually building android (somehow). Then when you come to compile android it only takes 1 minute because it's really quick to re-compile something that hasn't changed since the last compile.

Is it possible you just keep on compiling the kernel in the wrong directory? Make sure your android sources and kernel sources are in different directories. cd into the kernel directory. Make sure you have the .config set up correctly. Then run

make ARCH=arm CROSS_COMPILE=$ROMDIR/android-1.6-source/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-

the kernel compiles much quicker than android sources. You should end up with only a zImage (no system, userdata or ramdisk stuff - this is only built with android, not with the kernel). The zImage will be at $your_kernel_directory/kernel/arch/arm/boot/zImage

Link to comment
Share on other sites

Guest BigBearMDC

Thanks, jmmL!

I'll try to copy my kernel to -> / .

What i found weird from the beginning on is that repo seems to ignore my folder tree.

I cd into my android-1.5-source folder and init the repo.

But everytime the repo initializes in /home/username and i have to copy all the files and folders manually.

Okay I'll try that immediately.

Stay Tuned!

Greetings,

BigBearMDC

Edited by BigBearMDC
Link to comment
Share on other sites

Thanks, jmmL!

I'll try to copy my kernel to -> / .

What i found weird from the beginning on is that repo seems to ignore my folder tree.

I cd into my android-1.5-source folder and init the repo.

But everytime the repo initializes in /home/username and i have to copy all the files and folders manually.

Okay I'll try that immediately.

Stay Tuned!

Greetings,

BigBearMDC

You'll probably want to initialize repo in the sub-folder you want. For example, cd into android-1.6-sources, then run repo sync.

Just noticed your other post - all working now?

Edit again:

Ignore my first line, just re-read your post. I don't know why repo isn't initializing correctly.

Edited by jmmL
Link to comment
Share on other sites

Guest BigBearMDC

Yap it works now :)

Thanks!

I get errors because i just copied the drivers from the Pulse kernel to the Hero kernel.

But fortunately the errors tell me wich files are missing B)

Stay Tuned!

Greetings,

BigBearMDC

Link to comment
Share on other sites

Guest BigBearMDC

Hah this is really funny B)

I have to edit some functions - return null; - and so on :)

Every second driver makes problems...

Stay Tuned!

Greetings,

BigBearMDC

Link to comment
Share on other sites

Guest BigBearMDC

Thanks!

Luck - thats exactly what i need :)

I have to copy the header files too.

Didn't think about that.

Thats why so many drivers are making problems.

Stay Tuned!

Greetings,

BigBearMDC

Link to comment
Share on other sites

Guest BigBearMDC

UPDATE:

I had to edit the I2C driver.

A function that determines the clock returned an failure.

So i had to set the clock manually to 300kHZ.

I hope this will work...

Stay Tuned!

Greetings,

BigBearMDC

Edited by BigBearMDC
Link to comment
Share on other sites

This sounds GREAT! I cannot wait, good luck and I hope it works for you! :) B)

Thank you!

Edit- Any progress? :/

Edited by Spooke
Link to comment
Share on other sites

Guest BigBearMDC

UPDATE:

I got more errors - i guess because i copied all the header files from the Pulse kernel.

I got not enough time today to copy file for file back to the Hero kernel unfortunately.

But as soon as I got time I'll finish compiling the kernel :)

Stay Tuned!

Greetings,

BigBearMDC

Link to comment
Share on other sites

UPDATE:

I got more errors - i guess because i copied all the header files from the Pulse kernel.

I got not enough time today to copy file for file back to the Hero kernel unfortunately.

But as soon as I got time I'll finish compiling the kernel :)

Stay Tuned!

Greetings,

BigBearMDC

Ah ok, Hopefully you can get it working, Also what I dont undestand is that Hero is android 1.5? so how can it be 1.6 kernal? As i said before im a complete noob B),

Keep going though and good luck, :D

Link to comment
Share on other sites

Guest BigBearMDC
Ah ok, Hopefully you can get it working, Also what I dont undestand is that Hero is android 1.5? so how can it be 1.6 kernal? As i said before im a complete noob

WHAT?

I thought the Hero has android 1.6??

LoL B)

Dosn't matter

I hope it will boot :)

Greetings,

BigBearMDC

Link to comment
Share on other sites

Lol, well when I had my G1 I had a Hero Rom, it was 1.5,

however the tattoo's sense UI is 1.6 I think..

If it works, Do you think you could get 1.6/2.0 rom working? Just asking :)

Link to comment
Share on other sites

Guest BigBearMDC
If it works, Do you think you could get 1.6/2.0 rom working? Just asking :)

Well it never was my plan to port android 1.6 or even 2.0 ... But if the kernel I'm compiling works, that would mean that we have android 1.6- and even a 1.6 kernel (instead of 1.5 from the Pulse) - working on the Pulse.

That would be awesome!

And I think if we had the android 2.0 source, it wouldn't be a big problem to compile it with the Pulse kernel.

Thus android 1.6 has already been ported to the Pulse.

But the problem is that the most important things just don't work - like camera, telephone, GPS, WiFi...

Those things won't work in my ROM either...

But it would be awesome if it just boots up...

So

Stay Tuned!

Greetings,

BigBearMDC

Link to comment
Share on other sites

Android 1.5 and 1.6 use the same kernel; this means that you can compile android 1.6 with the Huawei kernel and vice-versa. That is what they are doing in the other Android dev thread, they are trying to get Android 1.6 to work properly. Android 2.0+ needs a different kernel, which means that in all likelyhood we must wait for Huawei's Android 2.0, because Huawei has not released the source to their drivers, they are not obliged to and probably won't.

The Hero has 1.6 on it, which means that you are compiling Android 1.6, yes.

The problems you note with the GPS, camera, telephone etc are the problems others have been finding, this is the problem we currently have (non-working hardware).

Keep up the good work!

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.