485 replies to this topic

[al.daun]

pier11, on 24 January 2012 - 06:37 PM, said:

try this version of dtox's 7.2 rom with previous version of .32 kermel - without melfas at all. It should not make a difference, but who knows...

same as before. tried your melfas boot.img as well. what's the name of the module? maybe i can try to probe it again in adb shell.

[pier11]

al.daun, on 25 January 2012 - 08:41 AM, said:

same as before. tried your melfas boot.img as well. what's the name of the module? maybe i can try to probe it again in adb shell.

no module. It's compiled into the kernel.
honestly I run out of ideas on what it can be...
try ProjectMenu from official rom - interesting how official soft identifies your touchscreen...
Because your case is unique. Most people have synaptics and I heard no complaints. The rest got melfas and we just made it working couple hours later too...

[al.daun]

Interessting. Tried the TRE2.1 Updata.app (from TWRock) and guess what: touchscreen is NOT working in the original 2.1 TRE ROM.

Installed your cm7.2 on top of that rom (with gapps). touchscreen still not working.

dmesg: http://pastebin.com/6Ff2CdeL

now reverting to official german and try to find out more

[al.daun]

pier11, on 25 January 2012 - 11:10 AM, said:

try ProjectMenu from official rom - interesting how official soft identifies your touchscreen...

synaptics-rmitouchscreen

ov3647 + ov7690

hynix-0x5510baad

samsung lcd

[al.daun]

@pier11, can you try to compile a kernel with synaptics drivers from this .32 8150 kernel?

https://github.com/m...put/touchscreen

it was patched in several ways, specially multitouch, but that is not important


thanks in advance

Edit: You may have to apply patches in board-msm7x25.c as well

Edited by al.daun, 25 January 2012 - 02:06 PM.

[dtox125]

@pier11
added oc to your kernel.and it works.

[pier11]

dtox125, on 26 January 2012 - 02:04 PM, said:

@pier11
added oc to your kernel.and it works.

beautiful!
your are the man!
many people have missed it and expressed a wish.

send diff if you inclined to do so, will add to repo.

/people also add smartass2 governors I saw... /

Edited by pier11, 26 January 2012 - 02:13 PM.

[dtox125]

here are the changes i´ve done to oc the kernel.

Attached Files

•  patchfile.rar   1.65K   18 downloads

[pier11]

dtox125, on 26 January 2012 - 04:55 PM, said:

here are the changes i´ve done to oc the kernel.

thanks a lot, dtox

will apply/test hopefully later today.

send more patches

[kiler4fun]

pier11, on 26 January 2012 - 05:15 PM, said:

thanks a lot, dtox

will apply/test hopefully later today.

send more patches

Dtox can you release a flashable oc kernel?

[dtox125]

i think this should be it..

Attached Files

•  signed_cm7.2_oc_kernel.zip   2.4MB   20 downloads

[kiler4fun]

dtox125, on 26 January 2012 - 10:40 PM, said:

i think this should be it..

Thnx gonna try it

EDIT: it says installation aborted, any ideas?

Edited by kiler4fun, 26 January 2012 - 11:06 PM.

[dtox125]

i suspected that sory.you should use the boot.img from the zip and replace with the one in the rom that you used to install cm7.2 and reinstall the rom.

Edited by dtox125, 26 January 2012 - 11:24 PM.

[D-D-]

There is no update script in it.
Inside the script:

show_progress 0.1 0

format BOOT:
write_raw_image PACKAGE:boot.img BOOT:

show_progress 0.1 10

edit:  http://dl.dropbox.com/u/15703389/CM7oc.zip
Just needed to test something.
It works.

Edited by D-D-, 27 January 2012 - 12:33 AM.

[pier11]

dtox125, on 26 January 2012 - 04:55 PM, said:

here are the changes i´ve done to oc the kernel.

thanks again - perfect patch.

tested, added to repo, added to our resulting rom as well.

[pier11]

Our msm7200a brother LG KH5200 (aka GW620 in Europe) has here .32 kernel sources published and also android open source part along with instructions how to build it.
http://www.lg.com/gl.../opensource.jsp

Search for KH5200:
KH5200(Andro-1) Android Froyo

[dr.flo]

pier11, on 04 February 2012 - 05:35 PM, said:

Search for KH5200:
KH5200(Andro-1) Android Froyo

Well so many news today...
I quickly looked at the system.img inside "Froyo_GW620_officially_LG.rar" (which is said to contain the official version of that rom).
Their libcamera wants /dev/msm_camera/msm_camera0, so they seem to have built some sort of compat-kernel-32 like you did

[dr.flo]

Some findings on ar6000 WIFI integration, possibly related to wifi suspend issues....

[b] Linux version < 2.6.32 (Android < 2.2)
 No native MMC suspend and resume method[/b]

[b] Linux version == 2.6.32 (Android 2.2 Froyo)
 Cut power mode is supported
 Clock, high speed mode and bus width need to be reset after resume[/b]

 Linux version > 2.6.34 (Android > 2.2)
 Deep sleep mode is support
 MMC_PM_KEEP_POWER
 WoW is supported
 MMC_PM_WAKE_SDIO_IRQ and MMC_PM_KEEP_POWER
 Bus width will to switch to 1 bit mode after suspend and restore to 4 bits mode after resume

This might explain why kernel .29 wifi integration cannot be ported into kernel .32 easily.
Maybe we need to look at sources of a v 32 kernel which integrates ar6000.ko - are sources for zte blade kernel available? see next post


another thing: you once said that wifi mac address = function( bt addr ), and bt addr is known?
if so, could we code a script that reads bt addr, then calculates and sets wifi mac address (in the same fashion as setMacAddress  - how does setMacAddress set a mac address?). The script could be called once by update.zip - wifi mac bug would be solved (or at least worked around in an elegant fashion).

edit: mac is simply written (in binary form) into system/wifi/caldata.bin*
I'm pretty sure this process could be automated. Now how to get bt addr?

Edited by dr.flo, 13 February 2012 - 11:37 AM.

[dr.flo]

https://github.com/k...host/msm_sdcc.c

is this one any different to ours?
If this one misses integration stuff specific to our ar6000.ko - while it still works for the zte blade - then maybe we just need to use this code in kernel, combined with their stock froyo ar6000.ko?

Possibly, ar6000.ko built from pulse-mini source isn't setup to properly integrate into kernel .32 natively - likely, since wifi integration seems to have changed between eclair and froyo, as stated in presentation linked above. Same might be true for ar6000.ko on ascend where it is just a dead file.

Edited by dr.flo, 13 February 2012 - 11:40 AM.

[pier11]

try to replace our ar6000.ko with one from blade and see what happen