froyo 2.2

[Guest Simon O]

I just pulled the .29 kernel config from my phone and extracted the .32 kernel config from the Chinese 2.2 ROM. I don't see any hardware differences at all.

kernel_configs.zip

so I wonder what is preventing the touchscreen from working?

[Guest Stephen Hyde]

possibly drivers in the os itself

2.6.32.9-perf what the hell, thats the same as the one my streak froyo build runs on currently :S

Edited October 19, 2010 by Stephen Hyde

[Guest Stephen Hyde]

update: android 2.2 will be here very soon for the blade- i have touch screen working :P

[Guest DaveMac]

update: android 2.2 will be here very soon for the blade- i have touch screen working :P

:D

[Guest Stephen Hyde]

jus gotta fix all the force closes i am getting - quite interesting when i cant read chinese :P

[Guest challengedavid]

update: android 2.2 will be here very soon for the blade- i have touch screen working :P

yes

[Guest k0nrad]

update: android 2.2 will be here very soon for the blade- i have touch screen working :P

It's getting better and better with each passing day :P

Hopefully by the day I lay my hands on the device I'll have a headache about which awesome ROM to flash ;]

GJ&GL, Stephen!

jus gotta fix all the force closes i am getting - quite interesting when i cant read chinese :D

...you're making silly excuses, y'know? :D

Edited October 19, 2010 by k0nrad

[Guest Stephen Hyde]

lol i do seem to be doing quite well with froyo builds of late :P

[Guest legolamb]

update: android 2.2 will be here very soon for the blade- i have touch screen working :P

Well that's just great, I've just got it to how I like it and now it looks like I might have to start all over again. :D

Nice one, fingers crossed.

Think I've got chinese for Rosetta stone if that's any help :D

[Guest Spooke]

update: android 2.2 will be here very soon for the blade- i have touch screen working :D

Nice work :D, seems like we got alot of developers for the Blade already :P

[Guest vl4d1m1r]

jus gotta fix all the force closes i am getting - quite interesting when i cant read chinese :P

As someone said in the Chinese ROM thread,

Change

ro.product.locale.language=zh

in build.prop to

ro.product.locale.language=en

[Guest Stephen Hyde]

right update v2:

touchscreen works

sound seems to work

sd card works (180mb free on phone storage too)

wifi works

bluetooth works

network - not working yet - fixing once i get adb sorted out again

other than that seems quite usable

[Guest Stephen Hyde]

As someone said in the Chinese ROM thread,

Change

ro.product.locale.language=zh

in build.prop to

ro.product.locale.language=en

thats great but i haven got adb working, the kernel upgrade has changed device ids

[Guest Simon O]

thats great but i haven got adb working, the kernel upgrade has changed device ids

Should be something in the kernel init.rc files that sets the device IDs.

[Guest fluxcapacitor]

right update v2:

touchscreen works

sound seems to work

sd card works (180mb free on phone storage too)

wifi works

bluetooth works

network - not working yet - fixing once i get adb sorted out again

other than that seems quite usable

I love this forum, riding the ups and downs on the froyo news for ages and now were on a major up :P

Excellent work!!!

Whats the deal with RAM ? Is it all usable or limited to the same amount of ram as the chinese model?

Edited October 19, 2010 by fluxcapacitor

[Guest tiggerlator]

update: android 2.2 will be here very soon for the blade- i have touch screen working :P

O_O very nice. i think my blade will like the taste of froyo.

[Guest Stephen Hyde]

vibrate seems to be MIA but not worried about that for now. touch screen works fine tho, seems alot more responsive at min

[Guest vl4d1m1r]

thats great but i haven got adb working, the kernel upgrade has changed device ids

Ah, ouch. I'm not sure what platform you develop on but on Linux it should be relatively simple to make a new udev rule.

Something like

SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="0c01", MODE="0666", OWNER="shyde"

with appropriate values as reported by OS seemed to work for me.

[Guest Stephen Hyde]

yep i was on windows, justswapped to adb on my linux box and got it working straight away :P fixing minor issues now

[Guest Simon O]

The 2.2 rom has set the device ids to VID_19D2&PID_1350

The 2.1 rom had these set to VID_19D2&PID_1354

so should work if you just edit the drivers.

[Guest rickywyatt]

just got my sf today and i cant wait to try 2.2 are you going to add overclock to this?

[Guest Simon O]

and not wanting to steal anybodies thunder but I've got touchscreen working here too :P

[Guest Cribby]

yep i was on windows, justswapped to adb on my linux box and got it working straight away :P fixing minor issues now

This is just awesome :D Thanks for the work dude! And the touchscreen feels better? Sweeet!

[Guest Stephen Hyde]

:P didn say i was the only one developing did i :D

we haven got working kernel source to do overclock yet

[Guest DaveMac]

and not wanting to steal anybodies thunder but I've got touchscreen working here too :P

Fight...fight...fight...

:D pmsl

I won't pretend to be anything other than an android noob, but seriously great work guys :D