Android 2.2 Development

[Guest cooldfuzion]

*VRROOOM!*

*SMACK*

"OW!" Screamed Bobo

"HAHAHA!" Dan loled

HTC EVO 4G gets hacked Froyo port, Sense UI be damned

You know what happens when you give EVO 4Gs to a room full of some of the brightest developers the world has to offer? Well, [expletive] is going to go down, that's what -- so it comes as little surprise that the phone's already been blessed with a seemingly functional Froyo port, even though neither the phone nor the operation system have even seen a public release yet. The largest distribution of the EVO so far has come at the hands of Google itself, which provided the Android 2.1- and Sense-equipped handsets to attendees of its recent IO conference; a timely upgrade to Android 2.2 has unquestionably been a big sticking point for would-be buyers, though, so it's good to see that early owners are already hard at work making this happen. Root is naturally required for the 2.2 port to work -- and there will undoubtedly be some hurdles to overcome to make this totally usable -- but we have full faith in these lovely wunderkinds. Follow the break for video evidence of a Froyo'd EVO in the wild.

Source: engadget

Edited May 30, 2010 by cooldfuzion

[Guest Csöpi]

any update on this project? im just asking, im really happy now with the 2.1 update, but if we would have apps to sd without partitioning the sd card would be awesome of course:)

[Guest Richard_Arkless]

any update on this project? im just asking, im really happy now with the 2.1 update, but if we would have apps to sd without partitioning the sd card would be awesome of course:)

This is 2.1 all over again they couldnt do anything because they didnt have the source code so things wouldn't work so it will most likely be a slow process

What I am more interested in is if we will have the wireless tethering and that we can turn our pulse into a hotspot

[Guest Spooke]

Hi guys, this person is making a guide on a how to port android roms,

He is porting T-Mobile Pulse 2.1 to the HTC Dream/Sapphire, http://forum.xda-developers.com/showthread.php?t=691360

Would this help you guys with what to do? Maybe even port a HTC Dream rom to the Pulse??

Hope it helps?

[Guest Stevos]

What I am more interested in is if we will have the wireless tethering and that we can turn our pulse into a hotspot

Check out Barnacle wifi tether in the market (free / donate).

Not as robust as a built-in system I'm sure, and no substitute for froyo, but it may keep you going until then.

[Guest MarcusHenrique]

UP! Get back to work devs! =P

[Guest BigBearMDC]

UP! Get back to work devs! =P

Actually, we are working on this 24/7 :(

[Guest MarcusHenrique]

Actually, we are working on this 24/7 :(

Hah, this community already loves you BoBo! Don't work too hard!

Hm what am I saying? Work harder! :( :o :o

[Guest]

Hah, this community already loves you BoBo! Don't work too hard!

Hm what am I saying? Work harder! :( :o :o

Yeah, wtf are you saying!?

BOBO, CODE UNTIL YOUR FINGERS BLEED!

(:()

[Guest Lord_Shaithis]

2.2 would be awesome, if only for flash support. *Curse adobe*

[Guest Celeb]

Actually, we are working on this 24/7 :(

and how is that progressing? any results so far?

[Guest eckengucker1]

You can watch the progress on our git.

[Guest Celeb]

You can watch the progress on our git.

Is there any document to track progress for regular people (meaning not bugs fixes etc, but state like "we got kernel working" or "we got 2.2 working, wifi doesnt work properly")?

[Guest Ashbeard]

Is there any document to track progress for regular people (meaning not bugs fixes etc, but state like "we got kernel working" or "we got 2.2 working, wifi doesnt work properly")?

I checked the git and to my eyes there was one update about one bug. Maybe I was looking in the wrong place.

[Guest gege001]

I know nothing about these things, but I'll help out by giving moral support!

Great going everybody, keep up the good work! :)

+1

[Guest eckengucker1]

Currently we are waiting for the 2.2 source. Afaik the kernel should work but the drivers aren't included

[Guest Epic-Emodude]

Currently we are waiting for the 2.2 source. Afaik the kernel should work but the drivers aren't included

When do you expect the source. And I presume that its going to take a long time to make the drivers work?

Anything someone with a little expecience in VB can do to help?

[Guest Epic-Emodude]

BTW Even the iPhone has FroYo now... http://www.engadget.com/2010/06/06/yep-the...ndroid-2-2-too/

[Guest david_dawkins]

Currently we are waiting for the 2.2 source. Afaik the kernel should work but the drivers aren't included

Is there any chance that the emulator froyo-2.2 image would work packaged against the T-Mo HUN 2.1/2.6.29 kernel?

The kernel already has the drivers "baked" in , and we don't expect the compiled 2.2 source to be any different to that found in the emulator image (is that correct?)

I'm assuming:

1) froyo can work with 2.6.29 (I saw a post demonstrating this)

2) the android 2.2 image can be extracted from the emulator's system.img (?)

3) the kernel can be extracted from the T-Mo HUN 2.1 ROM (use the Perl script)

4) a ROM can be constructed from 2 and 3 (GIT wiki contains at least some of the instructions for doing this)

I'm sure it cannot be this easy, so would appreciate knowing what assumptions are wrong.

Dave

Edited June 7, 2010 by david_dawkins

[Guest Tom G]

Is there any chance that the emulator froyo-2.2 image would work packaged against the T-Mo HUN 2.1/2.6.29 kernel?

The kernel already has the drivers "baked" in , and we don't expect the compiled 2.2 source to be any different to that found in the emulator image (is that correct?)

I'm assuming:

1) froyo can work with 2.6.29 (I saw a post demonstrating this)

2) the android 2.2 image can be extracted from the emulator's system.img (?)

3) the kernel can be extracted from the T-Mo HUN 2.1 ROM (use the Perl script)

4) a ROM can be constructed from 2 and 3 (GIT wiki contains at least some of the instructions for doing this)

I'm sure it cannot be this easy, so would appreciate knowing what assumptions are wrong.

Dave

I've had it almost booting for about a week, but haven't had time to play with it any more. It boots enough that I get an FC displayed on the screen (touch screen works :)) but it never gets any further (I end up with a black screen with an FC message). Hopefully with a bit more time I can get a bit further.

I'm using the Swiss kernel (T-Mo should also work) with a userspace based on a G1 Froyo rom.

I have disabled a lot of services (rild etc) to reduce problems in getting it to boot. Hopefully once it does boot adding things back in won't be too difficult.

It gets into a loop with a java error (on a JNI call). If anyone is interested I can provide more info later.

[Guest david_dawkins]

I've had it almost booting for about a week, but haven't had time to play with it any more. It boots enough that I get an FC displayed on the screen (touch screen works :)) but it never gets any further (I end up with a black screen with an FC message). Hopefully with a bit more time I can get a bit further.

I'm using the Swiss kernel (T-Mo should also work) with a userspace based on a G1 Froyo rom.

I have disabled a lot of services (rild etc) to reduce problems in getting it to boot. Hopefully once it does boot adding things back in won't be too difficult.

It gets into a loop with a java error (on a JNI call). If anyone is interested I can provide more info later.

WOW!

I would definitely appreciate instructions on how to get as far as you did. It would be worth adding to a wiki somewhere.

[Guest Celeb]

Currently we are waiting for the 2.2 source. Afaik the kernel should work but the drivers aren't included

waiting for the source? how come devs could make it work on HTC phones, iphone od motorola then? dont quite understand what you are waiting for. they all got 2.2 source arent they?

[Guest Epic-Emodude]

waiting for the source? how come devs could make it work on HTC phones, iphone od motorola then? dont quite understand what you are waiting for. they all got 2.2 source arent they?

With the HTC phones they make the dev phones so some of the hardware works with the emulator image. Im not sure about the motorola, but I would imagine that it was hacked to death for the iphone (in the video it said it was on a custom kernel and not much worked)

[Guest thisweb]

Is there any chance that the emulator froyo-2.2 image would work packaged against the T-Mo HUN 2.1/2.6.29 kernel?

The kernel already has the drivers "baked" in , and we don't expect the compiled 2.2 source to be any different to that found in the emulator image (is that correct?)

I'm assuming:

1) froyo can work with 2.6.29 (I saw a post demonstrating this)

2) the android 2.2 image can be extracted from the emulator's system.img (?)

3) the kernel can be extracted from the T-Mo HUN 2.1 ROM (use the Perl script)

4) a ROM can be constructed from 2 and 3 (GIT wiki contains at least some of the instructions for doing this)

I'm sure it cannot be this easy, so would appreciate knowing what assumptions are wrong.

Dave

This is what I thought. But I am confused about the kernel and the hardware drivers. If we assume Froyo can run with 2.6.29 kernel, the same as 2.1, can't we just put Froyo on top of our current 2.1 kernal with included hardware drivers then just replace the 2.1 OS bit ? Or I guess thats too simple. ??

[Guest Tom G]

This is what I thought. But I am confused about the kernel and the hardware drivers. If we assume Froyo can run with 2.6.29 kernel, the same as 2.1, can't we just put Froyo on top of our current 2.1 kernal with included hardware drivers then just replace the 2.1 OS bit ? Or I guess thats too simple. ??

But if Froyo is made for different hardware it will look for devices that don't exist on our platform. The java problem I have at the moment is a missing "file". The error doesn't say what the file is, but I suspect it is actually a missing device (devices are shown as files in /dev/).

I didn't have time to play with it last night, but hopefully should tonight. I will post the error message and upload a rom of what I have so far (it doesn't work, so don't expect much).