Android 2.2 Development

[Guest]

For the less android-educated; what does it mean that phildrip has kernel messages on the screen? :rolleyes:

I'm so curious on 2.2 even if I know nothing about developing Android. :D

Edited May 26, 2010 by Guest

[Guest klutsh]

i managed to install adobe flash player 10.1 on my pulse but i can not use the application in anyway. i can see the application in the installed applications list but not in the launcher. (btw i think this apk was meant for the nexus one) i will attach the apk here if it helps.

what i did was i changed the "ro.build.version.sdk=7" in build.prop to "ro.build.version.sdk=8" and then installed the application via file manager

EDIT: I am using BB and Pauls 2.1 rom r6 a2sd+ with launcherpro beta :rolleyes:

You know the Air and Flash Player 10.1 APK's are under a NDA don't you? they should not be made public in anyway!

[Guest niko1986]

You know the Air and Flash Player 10.1 APK's are under a NDA don't you? they should not be made public in anyway!

http://labs.adobe.com/downloads/flashplayer10.html#android

Looks pretty publicly available to me.

[Guest phildrip]

For the less android-educated; what does it mean that phildrip has kernel messages on the screen? :rolleyes:

I'm so curious on 2.2 even if I know nothing about developing Android. :(

I mean that we should see debug information coming straight from the kernel scrolling past on the screen instead of seeing the 'ANDROID' logo.

Helps us to see what's going on in the kernel :D

[Guest]

I mean that we should see debug information coming straight from the kernel scrolling past on the screen instead of seeing the 'ANDROID' logo.

Helps us to see what's going on in the kernel :rolleyes:

Oh, that must help out a lot :D

Good luck, all devs.

[Guest BigBearMDC]

I mean that we should see debug information coming straight from the kernel scrolling past on the screen instead of seeing the 'ANDROID' logo.

Helps us to see what's going on in the kernel :rolleyes:

We should add this immediately to the .32 source on our repo.

Do you have a github acc?

I'd give you commit rights :D

Best regards,

BigBear

[Guest phildrip]

We should add this immediately to the .32 source on our repo.

Do you have a github acc?

I'd give you commit rights :rolleyes:

Best regards,

BigBear

Right now this is still on the 2.6.27 kernel - the .32 doesn't even boot yet :D Well, I haven't managed to make it boot anyway.

But I'll get a github a/c when we start on .32.

[Guest BigBearMDC]

Right now this is still on the 2.6.27 kernel - the .32 doesn't even boot yet :rolleyes: Well, I haven't managed to make it boot anyway.

But I'll get a github a/c when we start on .32.

Okay :D

Would you mind sharing the bits you changed?

Best regards,

BigBear

[Guest phildrip]

Okay :rolleyes:

Would you mind sharing the bits you changed?

Best regards,

BigBear

Yeah, course. Although right now, I'm not 100% sure which bits are necessary :(

The crucial part is the boot parameters:

mem=128M console=ttyMSM2,115200n8 androidboot.hardware=qcom console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0

Right now I'm using:

root=/dev/ram rw mem=128M loglevel=6 console=tty0 console=ttyHSUSB0

It's the 'console' parameters that affect where these messages go. console=tty0 directs them to the screen, console=ttyHSUSB0 should send them over the usb link too, but I'm not sure about that. To verify that I can use the USB cable as some sort of serial link, I plugged phone into laptop and did

modprobe usbserial vendor=0x12d1 product=0x1501

That creates /dev/ttyUSB[0-3]. I ran

screen /dev/ttyUSB0

this'll give you a blank terminal, for now. I then ssh'd into the phone over wifi and ran

echo "hi!" > /dev/ttyHSUSB0

And it appeared on my terminal on the laptop, over the USB link. So that proved the concept :D

I also tinkered with the kernel - switched on virtual terminal, and FB console too. Here's the .config.

Small steps... :(

config.gz

[Guest eckengucker1]

A small step for man a giant leap for pulsemankind

[Guest BigBearMDC]

A small step for man a giant leap for pulsemankind

+1 :D

This is pretty cool :rolleyes:

Would be awesome to just have the kernel messages print to screen, would save a lot of trouble during debugging.

Edited May 27, 2010 by BigBearMDC

[Guest Basher52]

I dont know if its working, ist was just a thought:

As we know, the Pulse Hardware ist also used (logical) in other devices, eg the Screencontroller (Synaptics 3000 Series, used in Nexus One), or the CPU (MSM 7200a, Hero and other devices). By getting closer information about the other Hardware (radio, bluetooth(while not sooo needed in firs Froyo Build)) it could be possible to port the drivers from other devices instad to port them manuelly.

What do you think about this simple idea?

[Guest Ashbeard]

http://www.engadget.com/2010/05/28/android...-dream-and-mag/

2.2 ported to an even older phone than the Pulse. I presume that this was easier due to the hardware being closer to the Nexus One.

[Guest robertopero]

http://www.engadget.com/2010/05/28/android...-dream-and-mag/

2.2 ported to an even older phone than the Pulse. I presume that this was easier due to the hardware being closer to the Nexus One.

But if my information's good, the HTC and the G1 can run the default Android ROM's, no need to hack anything. But it's not true for Pulse.

[Guest BigBearMDC]

Good news!

Andrew got the .32 kernel booting in qemu :rolleyes:

Next step is to get it booting in the emulator, and then finally on our Pulse :D

Best Regards,

BigBear

[Guest Epic-Emodude]

Good news!

Andrew got the .32 kernel booting in qemu :rolleyes:

Next step is to get it booting in the emulator, and then finally on our Pulse :D

Best Regards,

BigBear

Maybe you will do it before we get 2.1 then...

[Guest Nirva]

Does the official 2.1 Rom from T-Mobile Hungary help you guys in any way ?

[Guest Pipe Merchant]

Does the official 2.1 Rom from T-Mobile Hungary help you guys in any way ?

I believe the 2.1 rom uses an older kernel, froyo requires the .32 kernel iirc. So I don't it will be too much help...

[Guest rhen]

I believe the 2.1 rom uses an older kernel, froyo requires the .32 kernel iirc. So I don't it will be too much help...

But it upgrades some firmware and contain new version of the drivers, that maybe helpful.

Edited May 28, 2010 by rhen

[Guest Spooke]

I heard that Froyo works on .29?

Anyway good luck with 2.2 :(

[Guest dodge-167]

I heard that Froyo works on .29?

Anyway good luck with 2.2 :(

hmmmm.....

HTC hero on 2.2

[Guest BigBearMDC]

hmmmm.....

[pic]

HTC hero on 2.2

I wonder who will throw the first rock at me :(

FroYo running on every HTC device...

[Guest David Roper]

I wonder who will throw the first rock at me :(

FroYo running on every HTC device...

bigbear get crack'a'lackin' with multitouch on the new official rom :(

[Guest Stevos]

Further confirmation that Froyo can run on .29 kernel : It has been ported to the Evo 4g.

(about 40 seconds in.)

I would suspect it would run less well than on the .32 kernel due to the supposed memory system improvements.

[Guest DanWilson]

I wonder who will throw the first rock at me :(

FroYo running on every HTC device...

*VRROOOM!*

*SMACK*

"OW!" Screamed Bobo

"HAHAHA!" Dan loled