• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

kernel 2.6.32

489 posts in this topic

Posted

You could try the unlock screen options, there is an unlcok by jogball or somerthing like that..

How to do that? I didn't find anything useful in Settings menu... CM7.1RC1

Unlock security is off, but it still requires to move circle via touchscreen, don't know how to to it via jogball or keypad...

1

Share this post


Link to post
Share on other sites

Posted

maybe I am wrong, but maybe this helps touchscreen issue

http://www.flatterma...-btnmouse.patch

Looks it's patch from Android space, not kernel. My issue is in kernel level... Thanks anyway.

1

Share this post


Link to post
Share on other sites

Posted

The issue with touchscreen is that.

Our driver is: synaptics_i2c_rmi_tm1319.c

It's not changed much between kernel versions 27, 29 and 32.

It was working in versions 27 and 29 with settings vreg="gp6" and gpio=57.

This has changed in v32 I'm playing with (huawei u8150) to:

"gp5" and gpio=29. This neither crash nor work.

But I don't trust those settings as touchscreen could not even be properly detected in probe().

Also those settings are used on msm7x25 boards since at least 2.6.29 kernels (u8110 pulse-Mini). So I think those are propagated somewhat by default to our board, even if our chipset is not supported in that 32 kernel.

So, if I revert back to "gp6" (and remain gpio=29), touchscreen got successfully detected in probe(), register itself as an input device. But no output from that device...

If I change gpio=57 in addition to "gp6", kernel hangs on probe() of the touchscreen. (Somewhere in vreg_enable).

-----

I experimented with that u8150 huawei kernel, plain vanilla Code Aurora v32 kernel, also with LG GW620 v32 kernel (same chipset; openeve project, based on official LG v32 kernel, based in turn on Code Aurora) - nearly the same issues, no luck.

If anyone have slightest idea what might be wrong, please let me know.

1

Share this post


Link to post
Share on other sites

Posted

I did it! WooHoo :)

One line of code in touchscreen driver made it working.

3

Share this post


Link to post
Share on other sites

Posted (edited)

I did it! WooHoo :)

One line of code in touchscreen driver made it working.

If you have compiled kernel 2.6.32 img, could you please put it here

Edited by Metkii
0

Share this post


Link to post
Share on other sites

Posted

If you have compiled kernel 2.6.32 img, could you please put it here

join! tester will

0

Share this post


Link to post
Share on other sites

Posted (edited)

If you have compiled kernel 2.6.32 img, could you please put it here

Here it is: pulse-hw2.6.32_v0.04.img

This image is for CM7.1RC. Extract kernel and repackage to try to use with other roms.

Changes:

- touchscreen works

- transitioned to "usb gadget" code. (Doesn't crash when unplugged from usb.)

Mass storage works, adb, sd card.

Not intended to work in this snapshot: sound, bluetooth, camera, sensors and anything else.

Edited by pier11
0

Share this post


Link to post
Share on other sites

Posted

Here it is: pulse-hw2.6.32_v0.04.img

This image is for CM7.1RC. Extract kernel and repackage to try to use with other roms.

Changes:

- touchscreen works

- transitioned to "usb gadget" code. (Doesn't crash when unplugged from usb.)

Mass storage works, adb, sd card.

Not intended to work in this snapshot: sound, bluetooth, camera, sensors and anything else.

nice piece of work!

i can't try it out now because my pulse is in the service center (trackball was full of s**t and it wouldn't move)

but i'm sure that you will manage to get it working.

just remember that your work is highly appreciated here in the community :)

0

Share this post


Link to post
Share on other sites

Posted

great great and great :) !

0

Share this post


Link to post
Share on other sites

Posted (edited)

I welcome pier11 I think your big work will give the second life to phone

Has checked up a kernel pulse-hw2.6.32_v0.04.img on cyanogenmod Puls-plus 2.2.1 v0.9.1 works !!!!

At button pressing power off the screen is disconnected, but doesn't go out

Edited by skykilla
0

Share this post


Link to post
Share on other sites

Posted

I welcome pier11 I think your big work will give the second life to phone

Has checked up a kernel pulse-hw2.6.32_v0.04.img on cyanogenmod Puls-plus 2.2.1 v0.9.1 works !!!!

At button pressing power off the screen is disconnected, but doesn't go out

Thanks,

I test it with CM7.

Power button allowed me to power off the phone. Short press turns off screen; long press shows menu with power off option...

Ideally you should remake boot image by extracting my kernel and then combining it with ramdisk from your rom's boot image. But not sure it'd affect key buttons.

Thanks for testing.

BTW, did something else accidentally worked for you, like maybe 3g data network? (can't test - don't use it)

1

Share this post


Link to post
Share on other sites

Posted (edited)

TASK:

could someone please help me test wifi driver from u8150's 2.6.32 rom?

Link is here: ar6000

It's important because our original wifi driver comes in binary only form and only compatible with it's 2.6.29 kernel, thus is not supposed to work.

Fortunately the linked driver is compiled against 2.6.32 kernel, support our wifi and in theory should work...

ADDITIONAL INFO:

In CM7 drivers' firmware is located here:

/system/etc/firmware

but very fortunately it's identical (by md5 sums) to what is in 2.6.32 lib archive, so no replacement even needed;

It's only needed to replace ar6000.ko file in the following location and test:

/system/lib/modules

(Don't forget to make backups before.)

Edited by pier11
2

Share this post


Link to post
Share on other sites

Posted (edited)

ok, don't bother,

insmod gives:

<4>ar6000: Unknown symbol msmsdcc_wlan_pwr_ctrl

<4>ar6000: Unknown symbol msmsdcc_wlan_pwr_ctrl_new

<4>ar6000: Unknown symbol enable_wlan_power

<4>ar6000: Unknown symbol msmsdcc_disable_wlan_slot

<4>ar6000: Unknown symbol msmsdcc_enable_wlan_slot

those are missed from drivers/mmc/host/msm_sdcc.c

Edited by pier11
1

Share this post


Link to post
Share on other sites

Posted

found/applied patch from u8120/60 development.

getting better:

sh-3.2# insmod ar6000.ko 

sh-3.2# lsmod

ar6000 155211 0 - Live 0xbf000000

1

Share this post


Link to post
Share on other sites

Posted

WiFi works now.

Compiled ar6000 wifi driver from sources on Huawei site.

Also mobile data network works.

4

Share this post


Link to post
Share on other sites

Posted

WiFi works now.

Compiled ar6000 wifi driver from sources on Huawei site.

Also mobile data network works.

:) it is great!

0

Share this post


Link to post
Share on other sites

Posted

once there's some kind of flashable zip, i'll try it and benchmark it upside down ^_^

0

Share this post


Link to post
Share on other sites

Posted

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 no sound is usable as a small tablet now :)

4

Share this post


Link to post
Share on other sites

Posted

Huh :)

Sound and vibro are the two REALLY necessary things remaining)

The finish line is just round the corner :)

0

Share this post


Link to post
Share on other sites

Posted

Nice work Pier11... :D :D :D

0

Share this post


Link to post
Share on other sites

Posted

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 stock qdsp5 code, with very very minor patches.

While 2.6.29 completely disregarded stock qdsp5 code, and seems ported old code from 2.6.27, renamed it to qdsp5_7200A. (Probably stock version didn't work for them, so they decided to revert to what was working...)

6

Share this post


Link to post
Share on other sites

Posted

I pinged flibblesan and tomg on twitter. I hope they will see this.

(just to show them this retro phone isn't dead yet)

0

Share this post


Link to post
Share on other sites

Posted

Could someone tell me more exactly what the benefits of this kernel is?

0

Share this post


Link to post
Share on other sites

Posted

Sound and vibro are the two REALLY necessary things remaining)

Vibrator works now too.

3

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.