Messages (Become)

Hi!
I completly killed my G5 (hardware kill)!!!
I´m buying a new (bigger) phone but I want to continue to help the G5 development team.
So, I need a cheap (used/new) i5500 phone to buy here on brazil (preferable).
Thanks.

Maybe the vsync implementation on mdp.c driver has problems on our phone...
Maybe the mdp_disable_irq_nosync errors on mdp driver is locking the irq handler. Locking the drivers that irq are used...
Can you test this? The mdp driver can be reverted to 2.6.38 version?

On this link You are not allowed to view links. Register or Login  a user hs the same problem...
or this You are not allowed to view links. Register or Login

Did you tryed to use the same toolchain to build kernel and android?

Maybe a stupid question: the arm11boot don´t use "img" format?
I´m not so confident on these conclusions to encourage a potencially harmful test like this...

Maybe another stupid question: have you tryed to dd "flash" the bml5.img into another partition and tryed to do a stl dump or mount?

Try this You are not allowed to view links. Register or Login, please.

Kernel panic, sorry.

I tried to build as a module and then loaded while streaming /proc/kmsg, but the phone hard reboots before anything shows up in the log.

I don´t see anything helpfull on "generic" onenand driver (suited for sansumg SOC)... I think we need more help.

Maybe samsung fsr driver can teach us something...

Hi!
I updated the source of GT-I5508 touch.
The default calibration values was reseted to test calibration routine.
To calibrate:
1. abd shell echo 1 > /sys/class/touch/msm_touch/calib
2. touch the whole screen. The driver will take the correct xmin/xmax/ymin/ymax.
3. abd shell echo 0 > /sys/class/touch/msm_touch/calib
The first step activate the calibration mode, the last deactivate and save the values... A reboot is needed to use the new calibration values...

PS: if the calibration routine works I will return the default values...
PS2: The code has a problem. Wait. I will fix it...Now it is OK!

Guys i have some questions, please reply me if you know... #1 ...

#1 Ask on support forum!
#2 Same as above!
#3 Psyke will NEVER do any modding to this rom! See post 1-3!
#4 This is for official CM roms...

Please. This is a development topic!!!

OuNao,

I'm now compiling your driver by default in my kernel (including my new 2.6.35 kernel), because you've added the multitouch input events that are useful for ICS (and maybe also for the open CWM touch recoveries - I will be looking into those later). The only problem is the actual fake dual-touch function .

I would love it if we could use your updated driver, but have a mechanism in which we can explicitly allow or disallow the fake dual-touch, maybe through a /sys node so that we can control it via userspace. I'm going to try to implement this myself, but if I fail, maybe you'll consider trying this yourself?

Well, give me some time anyway...

I think this can be done. I will try something...

PS: I saw the post on CM7 topic. Interesting problem...

EDIT: Try if this compile. If yes, the next step is include some if statements...
<URL>You are not allowed to view links. Register or Login</URL>

Hi everyone!
This module is only a FAKE dualtouch implementation for GT-I5500 phone...
GT-I5500 hardware can´t do REAL dualtouch!!

Installation:
On CM9: Already included on last versions. See CM9 topic...
On CM7: Already included on last versions. See CM7 topic...
On froyo: Copy the module on any folder. On terminal type "su", enter, "insmod pah/to/module/synaptics_i2c_rmi4.ko"

The files:
V9.2
Same as V9.1
Removed debug messages, removed old touch API code, removed some trash code, included SYSFS code to module activation.
*Usage: (2 modes: DT and GM)
1- DT:  Counter-clock circle motion started on top-right quadrant of the screen ending on the same quadrant (ie: TR > TL > BL > BR > TR quadrants). When activated, one finger is fixed on the center of the screen and the "real" finger is the second touch.
2- GM: Clockwise circle motion started on top-right quadrant of the screen ending on the same quadrant (ie: TR > BR > BL > TL > TR quadrants). when the finger is released the coordinates are saved and used next touch as a "second" touch (fixed). This way the fixed touch can be selected and not allways on center...
source = You are not allowed to view links. Register or Login
module = not released
V9.1 corrected
Same as V9
Removed debug messages
Included Psyke83´s patch to correct touch detection bug on some edges.
source = You are not allowed to view links. Register or Login
module = You are not allowed to view links. Register or Login
V9
The module now has to modes:
DT: The same behavior and activation of V8.
GM: Activated with a clockwise circle motion started on top-right quadrant of the screen ending on the same quadrant (ie: TR > BR > BL > TL > TR quadrants). when the finger is released the coordinates are saved and used next touch as a "second" touch (fixed). This way the fixed touch can be selected and not allways on center...
source = You are not allowed to view links. Register or Login
module = You are not allowed to view links. Register or Login
V8
The dualtouch mode is now activated with a counter-clock circle motion started on top-right quadrant of the screen ending on the same quadrant (ie: TR > TL > BL > BR > TR quadrants). When activated, one finger is fixed on the center of the screen and the "real" finger is the second touch.
source = You are not allowed to view links. Register or Login
module = You are not allowed to view links. Register or Login
V7.1
Screen turn of after resume bugfixNot yet...   Bug not present on CM7.x
source = You are not allowed to view links. Register or Login
module = You are not allowed to view links. Register or Login
V7
Same activation method. The driver only sends to framework the touchs number 1 and 4 (less garbage information to frame work)... 2 corners options for the 1st and 2nd touch: top-left and bottom left for the 1st, top-right and bottom right for the 2nd. Must do the 2nd touch less then 2 seconds from the first...
source = You are not allowed to view links. Register or Login
module = You are not allowed to view links. Register or Login
V6
Now you need 4 touchs to do the gesture.
1 touch: bottom or top / lef corner
2 touch: bottom or top / right corner
the dualtouch mode is then activated
3 touch: the 1st finger of pinch zoom
4 touch: the 2nd finger of pinch zoom. On release this finger the dualtouch mode is deactivated...
source = You are not allowed to view links. Register or Login
module = You are not allowed to view links. Register or Login
V5
Now you need to activate the "dual touch mode", the "1st" finger is fixed. Then any touch will do pinch zoom. No need to deactivate "dual touch mode"
module: You are not allowed to view links. Register or Login
source: You are not allowed to view links. Register or Login[/color]