Jump to content

kernel 2.6.32


Guest pier11

Recommended Posts

  • Replies 488
  • Created
  • Last Reply

Popular Posts

Sound/Mic work now. Plays mp3, does google voice search, heard remote answering machine via normal phone call. Plugged qdsp5 from current kernel. Seems to be working OK. 2.6.27 kernel also used s

Ported backlight stuff - driver, related board config, huawei's framebuffer patch. Now brightness changes, also display turns back light completely off when inactive. The device with wifi/3g but

WiFi works now. Compiled ar6000 wifi driver from sources on Huawei site. Also mobile data network works.

Posted Images

3. Added Melfas touchscreen.

Some u8230 devices have it, so touchscreen did not work for them. Please test when new kernel is available and report back.

touchscreen is not worked. touch to a restart :(

Link to post
Share on other sites
Guest al.daun

U8220 (T-Mobile Pulse) - CM6.1 + OC Kernel

My touchscreen is not working as well. Installed fine on my partition layout. Don't know which updata.app i installed last, could be the german one or uk 2010.

dmesg:

http://pastebin.com/YPEu1sZ5

Edit: TS not working on CM7.2 + Kernel 32 from the other thread of course :)

Edited by al.daun
Link to post
Share on other sites

U8220 (T-Mobile Pulse) - CM6.1 + OC Kernel

My touchscreen is not working as well. Installed fine on my partition layout. Don't know which updata.app i installed last, could be the german one or uk 2010.

dmesg:

http://pastebin.com/YPEu1sZ5

melfas-ts: probe of 0-0022 failed with error -5
I see, not good. It's hard to develop not having the hardware... wait. you have different touchscreen - same as mine:
input: synaptics-rmi-touchscreen as /devices/virtual/input/input0

and it should work

Edited by pier11
Link to post
Share on other sites

touchscreen is not worked. touch to a restart :(

run in terminal (reboot phone first to get logs from the beginning)

cat /proc/kmsg > /sdcard/log.txt
or adb
adb shell cat /proc/kmsg > log.txt

and pastebin it please. I don't have that piece of hardware, so it's the only way for me to try to figure what's wrong...

Link to post
Share on other sites
Guest al.daun

melfas-ts: probe of 0-0022 failed with error -5

I see, not good. It's hard to develop not having the hardware...

maybe this helpes as u8150 seems to have melfas driver:

http://mjanja.co.ke/...touch-gestures/

when i enter "getevent" in terminal it states that i have "synaptics-rmi-touchscreen".

did a total wipe and installed cm72... and gapps..., booted fine but without touch.

Edit: found that the melfas_i2c_ts.c is younger in his repo (has copyright 2010 by huawei) as in your repo (copyrighted by google 2007), maybe its worth a try

(i am not an android or kernel dev, so not able to compile and try myself)

Edited by al.daun
Link to post
Share on other sites

maybe this helpes as u8150 seems to have melfas driver:

http://mjanja.co.ke/...touch-gestures/

when i enter "getevent" in terminal it states that i have "synaptics-rmi-touchscreen".

did a total wipe and installed cm72... and gapps..., booted fine but without touch.

Edit: found that the melfas_i2c_ts.c is younger in his repo (has copyright 2010 by huawei) as in your repo (copyrighted by google 2007), maybe its worth a try

(i am not an android or kernel dev, so not able to compile and try myself)

I've edited my previous post soon after. You don't have melfas, but normal "synaptics-rmi-touchscreen", same as mine Pulse.

This makes situation even stranger. There is no other driver for the touchscreen, and it works for me but not for you...

Link to post
Share on other sites
Guest al.daun

I've edited my previous post soon after. You don't have melfas, but normal "synaptics-rmi-touchscreen", same as mine Pulse.

This makes situation even stranger. There is no other driver for the touchscreen, and it works for me but not for you...

Sorry, haven't seen the edit on the other page. I will try to install again without gapps and report results.

Edit: But maybe my thoughts can help u8230 users with melfas

Edited by al.daun
Link to post
Share on other sites
Guest al.daun

are you getting anything from when touching screen (you should if it works):

cat /dev/input/event0

Also please post dmesg from .32 kernel in cm7.2 where touchscreen does not work

So far reinstalling uk2010 didn't help. Same as before. Touchscreen works with uk2010 and german updata.app. CM7.2 can be installed on german update but doesn't boot (hangs at android screen).

I installed USB-drivers that recognize the .32 USB ADB Device in Devicemanager, but i am not able to get a connection to ADB shell ("device not found"). Any hints?

Link to post
Share on other sites

So far reinstalling uk2010 didn't help. Same as before. Touchscreen works with uk2010 and german updata.app. CM7.2 can be installed on german update but doesn't boot (hangs at android screen).

I installed USB-drivers that recognize the .32 USB ADB Device in Devicemanager, but i am not able to get a connection to ADB shell ("device not found"). Any hints?

I think it is turned on by default in rom:

Settings -> Applications -> Development -> USB debugging

Link to post
Share on other sites
Guest al.daun

I'll try adb shell again, maybe my system was crap at the time i tried.

For the touch-issues:

I noticed that in an opensource-package of 2009 (i might have got this on the T-Mobil UK website and it may be donut) there are two device specific drivers for synaptics devices: tm1319 as in your repo and tm1167. Is there a way to determin which specific synaptics touchscreen our handsets use?

Edit: 2.1 oopen-source does not include this

Edited by al.daun
Link to post
Share on other sites
Guest al.daun

I think it is turned on by default in rom:

Settings -> Applications -> Development -> USB debugging

Seems my sdk-tools were to old for this, downloaded actual ones from android.com and it worked.

But: No good news. Probe for synaptics and melfas fail in dmesg

Edit: http://pastebin.com/PDvJDfFk

Edited by al.daun
Link to post
Share on other sites

Attached

Thanks, perfect log.

But it makes situation even stranger.

We have the same touchscreen. It worked for me on .29 and .32 kernel,

but it doesn't probe for you on.32 kernel...

The driver for this touchscreen virtually not changed at all between .29 and .32...

Link to post
Share on other sites
Guest al.daun

but it doesn't probe for you on.32 kernel...

I noticed that on cm6.1 synaptics touchscreen gets probe before msm_i2c error

<6>[1, swapper] [    2.062386] input: synaptics-rmi-touchscreen as /devices/virtual/input/input0

<6>[4, events/0] [    2.062955] msm_chg_usb_i_is_not_available

<6>[1, swapper] [    2.165980] hsusb reset interrupt

<6>[1, swapper] [    2.168226] hsusb resume: speed = HIGH

<6>[1, swapper] [    2.327336] hsusb reset interrupt

<6>[1, swapper] [    2.329590] hsusb resume: speed = HIGH

<6>[1, swapper] [    2.540925] hsusb set_configuration wValue = 1 usbcmd = 80001

<6>[580, USB mass_storag] [    2.873518] usb_mass_storage usb_mass_storage: config #1

<6>[568, usb_work] [    2.874443] msm_chg_usb_i_is_available

<3>[1, swapper] [    2.875243] msm_i2c msm_i2c.0: Error during data xfer (-5)

<3>[1, swapper] [    2.875433] msm_i2c msm_i2c.0: Error during data xfer (-5)

But with your kernel, its probed while msm_i2c is busy:
<3>[1, swapper] [    2.034083] msm_i2c msm_i2c.0: Bus still busy, status 2100, intf 0

<3>[1, swapper] [    2.034129] msm_i2c msm_i2c.0: Error waiting for notbusy

<4>[1, swapper] [    2.034291] synaptics-rmi-ts: probe of 0-0020 failed with error -16

Is this the same behaviour in your setup or is it specific to my device?

Link to post
Share on other sites

OK fellow Melfas owners,

please test this kernel: boot-img-melfas.zip

Just flash it via recovery.

I applied the same patch as in my synaptics touchscreen. That helped me overcome hanging, and essentially make my touchscreen usable for the first time after three weeks of continuous fight with it.

Link to post
Share on other sites

OK fellow Melfas owners,

please test this kernel: boot-img-melfas.zip

Just flash it via recovery.

I applied the same patch as in my synaptics touchscreen. That helped me overcome hanging, and essentially make my touchscreen usable for the first time after three weeks of continuous fight with it.

it works!!! Thanks Pier!!

Edited by Metkii
Link to post
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.