1725 replies to this topic

[klutsh]

SDK is a driverless, meant to run on a PC, bare minimum pre-compiled ROM.
Source has everything that's needed to stand a chance of getting it to run on a actual device.

If you note in the SDK video's sdcard, phone, wifi, everything but the screen does not work.

Also like the 2.1 source's available at the minute, you may find that the Pulse's MSM chipset will not have any vendor config's.
2.2 seems to be mainly aimed at snapdragon CPU's.

Edited by klutsh, 21 May 2010 - 08:56 PM.

[eckengucker1]

HTC Hero is running with the same chipset (Qualcomm MSM 7200-A) and they got a vendor-config. We'll see

[Celeb]

Maybe stupid question. But have we considered asking Huawei for source of drivers. It now seems that they aren't gonna make 2.1 work (even tough they did not admit that yet), but once they do, I don't think there should be any troubles for them to share the code with dev community.

[Jan M]

Celeb, on May 22 2010, 19:21, said:

Maybe stupid question. But have we considered asking Huawei for source of drivers. It now seems that they aren't gonna make 2.1 work (even tough they did not admit that yet), but once they do, I don't think there should be any troubles for them to share the code with dev community.

they haven't released it yet, so no point in asking them for anything...and once they release 2.1 you can ask for their kernel modifications...there's no clause in GPL requiring them to release the source for proprietary drivers...the closest you can get to that with a phone is openmoko.

[BigBearMDC]

Celeb, on May 22 2010, 20:21, said:

Maybe stupid question. But have we considered asking Huawei for source of drivers. It now seems that they aren't gonna make 2.1 work (even tough they did not admit that yet), but once they do, I don't think there should be any troubles for them to share the code with dev community.

I already asked Huawei.
Made topics on their forum, wrote a few e-mails... it seems like we'll not get anything from Huawei.

But it shouldn't be an unsolveable problem to get the new kernel working with the old drivers.
It's only a matter of how much work someone wants to put in such a porting project.
The G1 is an dev phone as, same is the Nexus One.
That's why the support for both of this devices is huge.
The Pulse us just not interesting for most if the devs... although it would be a good device IMHO because it's just cheap.

However, we do not necessarily need Huawei's assistance to get this working.
We can get Froyo by our own, but it's definetly not going to be a easy porting task.
Just image a big company is not able to get it working... maybe Huawei would offer jobs to those that are working on this project

Best regards,
BigBear

[rhen]

Epic-Emodude, on May 21 2010, 22:37, said:

So bassicly we cant do anything about making a 2.2 ROM for our pulses untill we have all the sources?

Whats the difference between the source and the SDK that was released yesterday?

SDK (Software Development Kit) if for programmer who want to write program for adroind devices. It contains the necessary libraries to reach the OS and hardware. It also contain the compailer and the debugger for this prupose.

Android source is for hardware manufacturers. The source needed to port the OS to a device.

Edited by rhen, 22 May 2010 - 07:45 PM.

[Sh4d0w940]

BigBearMDC, on May 22 2010, 21:16, said:

maybe Huawei would offer jobs to those that are working on this project

Lol, they would just put crappy T-Mobile stuff in the rom and release it as their own

Edited by Sh4d0w940, 22 May 2010 - 08:19 PM.

[HyvelTjuven]

Don't know if this helps us out at all but you can download Android 2.2 for N1 here.
http://forum.xda-dev...958#post6558958

android.clients.google.com/packages/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip

[robot1000]

Bigbear, have you tried contacting them directly?

[email protected] or 08000501515

[BigBearMDC]

HyvelTjuven, on May 22 2010, 22:26, said:

Don't know if this helps us out at all but you can download Android 2.2 for N1 here.
http://forum.xda-dev...958#post6558958

android.clients.google.com/packages/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip

Yap I will have a brief look at that, but I think the cahnce that this will run on our Pulse is even smaller than with the emulator image
Already saw that on twitter, I follow Paul and AmonRA

Sh4d0w940, on May 22 2010, 22:19, said:

Lol, they would just put crappy T-Mobile stuff in the rom and release it as their own

Hah, that's right

[BigBearMDC]

robot1000, on May 22 2010, 23:16, said:

Bigbear, have you tried contacting them directly?

[email protected] or 08000501515

Yap.
I also asked for the email address of the Research & Development office that works on the Pulse ... I haven't got an answer yet

[HyvelTjuven]

BigBearMDC, on May 22 2010, 23:18, said:

Yap I will have a brief look at that, but I think the cahnce that this will run on our Pulse is even smaller than with the emulator image
Already saw that on twitter, I follow Paul and AmonRA

So the emulator image didn't work out?

[kamikase]

what we really would need is the interface definition to the different parts of the phone like how to "speak" to the radio ic etc so we ould write our own drivers even for android 3.0
but i guess this is too much to ask because this is the entire blue-print

kase

[BigBearMDC]

HyvelTjuven, on May 22 2010, 23:22, said:

So the emulator image didn't work out?

Unfortunately not.
It just freezes at the (animated) Android logo.

[HyvelTjuven]

BigBearMDC, on May 22 2010, 23:28, said:

Unfortunately not.
It just freezes at the (animated) Android logo.

But is it possible for you to replace the drivers of this N1 ROM with drivers from 1.5 U8220?

(noob question  )

[BigBearMDC]

kamikase, on May 22 2010, 23:26, said:

what we really would need is the interface definition to the different parts of the phone like how to "speak" to the radio ic etc so we ould write our own drivers even for android 3.0
but i guess this is too much to ask because this is the entire blue-print

kase

Wow, hold on!
You want to write your own drivers?
Sorry, but are you NUTS??

That's a little bit too much for only one person I guess (assuming you are in the age between 18 and 25 and not a professional Dev ).
But if you're intersted in that:

What I got from the TS driver is that the SW talks to the radio through the I2C bus.
Every device has it's own identifier and the communication is package oriented.

[BigBearMDC]

HyvelTjuven, on May 22 2010, 23:31, said:

But is it possible for you to replace the drivers of this N1 ROM with drivers from 1.5 U8220?

(noob question  )

Nope.
At leasat not for me
You would have to patch the already compiled kernel, which is practically impossible.

[BigBearMDC]

- double post, sorry -

Edited by BigBearMDC, 22 May 2010 - 09:36 PM.

[HyvelTjuven]

BigBearMDC, on May 22 2010, 23:35, said:

Nope.
At leasat not for me
You would have to patch the already compiled kernel, which is practically impossible.

Too bad, but can you use the ones from the 2.1 ROM that you and Paul put together?
(sorry for all the questions, I'm just curious! ^^)

Edited by HyvelTjuven, 22 May 2010 - 09:39 PM.

[BigBearMDC]

HyvelTjuven, on May 22 2010, 23:38, said:

Too bad, but can you use the ones from the 2.1 ROM that you and Paul put together?
(sorry for all the questions, I'm just curious! ^^)

Once the 2.1 kernel source is out we might use it's drivers and patch them into the 2.6.32 kernel.
But I think it should work with the .27 kernel drivers too (Android 1.5 kernel).
The main functions (and the main differences) are not the drivers but other functions in the kernel.
So my thought is that it should not make a big difference which drivers we use, as they nearly stay the same even with never kernel versions.
Why should the drivers be changed if the hardware stays the same?
But that are just my thoughts...

Edited by BigBearMDC, 22 May 2010 - 09:44 PM.