21 replies to this topic

[TechnoLover]

Hello everyone,

as my phone has a bad response on the soft keys I worked on a patch and I think I found one, but I need some testers who want to test out the patch, primary some people who have a bad response on the soft keys

Edited by TechnoLover, 23 May 2011 - 09:19 PM.

[harylauw]

what fix? thank you

[TechnoLover]

it's a fix for your soft keys when they don't work very well, for example your home button does not work properly when you push it when the phone is on the desk and not in your hand. I try to fix this, it was sometimes the same on the Liquid S100

EDIT: Kernel added

be sure that you're on a Froyo Bin & reboot phone in bootloader and run per terminal

fastboot -i 0x0502 boot Acer-Liquid-MT-Kernel-24052011-161035.img

After a reboot you have your old Kernel back

 Acer_Liquid_MT_Kernel_24052011_161035.img   2.48MB   11 downloads

Please give Feedback, if the Keys work better, the same or even worse than before

Edited by TechnoLover, 24 May 2011 - 04:58 PM.

[vache]

TechnoLover, on May 24 2011, 13:43, said:

it's a fix for your soft keys when they don't work very well, for example your home button does not work properly when you push it when the phone is on the desk and not in your hand. I try to fix this, it was sometimes the same on the Liquid S100

EDIT: Kernel added

reboot phone in bootloader and run per terminal

fastboot -i 0x0502 boot Acer-Liquid-MT-Kernel-24052011-161035.img

After a reboot you have your old Kernel back

Acer_Liq...1_161035.img

Please give Feedback, if the Keys work better, the same or even worse than before

On wich BIN it is intend to be flashed ?

[TechnoLover]

It should work on any acer bin and/or acer based rom, I use it on top of Metalounay but it should work an any bin cause it's just acer kernel source, modified.

[vache]

TechnoLover, on May 24 2011, 16:53, said:

It should work on any acer bin and/or acer based rom, I use it on top of Metalounay but it should work an any bin cause it's just acer kernel source, modified.

We have only Froyo kernel sources. The ramdisk, and  the init script are different from Froyo to Gingerbread.
So it is intend to be flash on Froyo only, you'll stuck at Acer logo on Gingerbread.

If i flash back a Froyo bin i'll try it and let you know.

[TechnoLover]

ah sorry I forgot of course it has to be on top of a Froyo Bin

and thanks for testing

[vache]

Just try it on after flash 1.100.35.

First time it booted i thunk soft-key was broken.
With stock boot i have to press key a little bit below of it, with your boot, i have to press them a little bit above.
I have to press the touchscreen in the same time. (my finger exceeds on it)

The sensitive area seems to be less, but it looks like you find something interesting.

Can you point me what file(s) you modify ?

[TechnoLover]

https://github.com/m...m/board-a4-ts.c

starting at line 128

The theory is that the touchscreen don't stops after the normal screen, it goes below the soft keys. So the touchscreen is about 930px long. So after 800px you can change the value to whatever you want, you could also add a fifth key if you want but I've never tried this as I got no idea which key is usable there. Another idea could be, to replace the search-key with another key, such as skip-song or change brightness maybe

Now I try to change the battery percentage to 1%-steps

[TechnoLover]

1%-step battery works btw.

[bozok]

I couldn't use your patch, but i have problems with soft keys from the purchase of the Liquid Metal, and it's the only problem i have.
It seems that the sensibility is quite below the average, and sometimes to make the MT understand i want to go back, or i want to select the option menu, i have to scroll my thumb on the touch area, so that i find the right place where the Metal "understands" my intention.


It would be nice to fix that in order to make our Metal as ready to touch as the other devices.

Edited by bozok, 28 May 2011 - 11:27 AM.

[davidevinavil]

TechnoLover, on May 27 2011, 11:44, said:

1%-step battery works btw.

Good work
Could you share your modified source to have 1% step?
Have you edit also framework-res.apk?

[TechnoLover]

@davidevinavil

look here: https://github.com/m...iquid-MT-Kernel or https://github.com/m...commits/master/ and click on commit

and I haven't changed framework-res.apk yet gonna have a look later, first I have to do some other things first

when using source please credit (:

@bozok

That's the problem I have, too. Maybe I send my MT back to receive a new, the problem is that it's impossible to use the buttons just with the fingertip, you really have to roll your finger/thumb, that's really annoying. When the phone lies on the desk it's even more worse...

[bozok]

TechnoLover, on May 28 2011, 19:18, said:

@bozok

That's the problem I have, too. Maybe I send my MT back to receive a new, the problem is that it's impossible to use the buttons just with the fingertip, you really have to roll your finger/thumb, that's really annoying. When the phone lies on the desk it's even more worse...

I don't know whether this can help, but the problem happens more often when battery is at 60-70% or less..
If the device is full charged, the response to touch is not perfect, but for sure better !

[davidevinavil]

Hi I was looking into your github and I found a little mistake into acpuclock-7x30.c at line 53 there is

+#define PLL2_L_VAL_ADDR  (MSM_CLK_CTL_BASE + 0x33)

but right is

+#define PLL2_L_VAL_ADDR  (MSM_CLK_CTL_BASE + 0x33c)

as written here https://github.com/c...cpuclock-7x30.c



please look at static struct clkctl_acpu_speed acpu_freq_tbl and give me your opinion about that..

{ 184320, PLL_3,    5, 4,  61440,  25, VDD_RAW(25) },
must be
{ 184320, PLL_3,    5, 3,  61440,  25, VDD_RAW(25) },


{ 368640, PLL_3,    5, 1,  122800, 25, VDD_RAW(25) },
must be
{ 368640, PLL_3,    5, 1,  122880, 25, VDD_RAW(25) },



anyway congratulations for your work  
And thank for 1% battery step..

Edited by davidevinavil, 29 May 2011 - 10:33 PM.

[TechnoLover]

Quote

{ 184320, PLL_3, 5, 4, 61440, 25, VDD_RAW(25) },
must be
{ 184320, PLL_3, 5, 3, 61440, 25, VDD_RAW(25) },

why 3?

Quote

{ 368640, PLL_3, 5, 1, 122800, 25, VDD_RAW(25) },
must be
{ 368640, PLL_3, 5, 1, 122880, 25, VDD_RAW(25) },

this seems that it has to be changed

[davidevinavil]

737280 is pll3 frequency so:

737280/(1+1) → 368640

737280/(2+1) → 245760

737280/(3+1) → 184320

737280/(5+1) → 122880

I'm not so good in english to explain why but I think you can understand

Edited by davidevinavil, 01 June 2011 - 12:05 PM.

[TechnoLover]

my english isn't the best, too, but I understood

=> changed

[Svarion]

i've seen this commit https://github.com/m...fbf007a1#diff-0 in arch/arm/mach-msm/Kconfig
seems that you've enabled 80hz refresh frequency...it's a workaround to remove fps limit?

[TechnoLover]

not really =/ the fps are around ~38fps and the only positive is, that vsync is enabled, so there's no "tearing" (?).

Negative aspect is that the battery drain seems higher =(
So I have to search further but I don't give up