ORIGINALLY POSTED BY doixanh:
It seems that X8 and X10mini use the same touchscreen controller, so this module may work with X10 mini, too!
I'm working with a kernel module to replace SE touchscreen driver to support dualtouch. However, as I found out, it will mostly not be supported by our hardware, because X8 has only 1 sensor and that sensor supports only 1 finger. I don't know whether we can have dual touch if we flash the screen firmware. I will have a look on that.
A temporary solution now is to make a one finger pinch zoom. The idea is that we make Android to think that the second finger is also pressed, by generating second finger events from the driver.
Because I need to modify hw_config.sh and each ROM has a different hw_config.sh, there will be a specific update.zip for each ROM.
Release history
April 13 v004. Rewrite from scratch. Pinch zoom with one or two fingers.
April 03. Source released.
March 26 v003. Specify zoom-in position.
March 25 v002. Zoom-out, rotate. Module size optimization.
March 24 v001. Better finger detection. Reduced zoom-in speed.
March 23 v000. 1 finger pinch zoom-in only
Very Important : How to zoom
For v004
To activate gesture, put your two fingers one-by-one (one finger first, then another after - don't put both at the same time) on the screen, away from each other for at least 1cm. The 2nd finger should have more pressure onto the screen. After putting your 2nd finger on the screen, wait for 0.5s, the gesture will be activated.
After the gesture is activated, you can
- Use your two pressed fingers, or
- Lift up one finger and use the remaining finger
to zoom-in/out/rotate.
I prefer keeping two fingers on the screen, because it's natural for pinch zoom. You can look at the tutorial for v004 here, and practice with MultiTouch Visualizer 2.
For v003 and below
Right now it supports only zoom-in, zoom-out, and rotate. I will improve it over time. For who says it's not working, please read this how-to very carefully:
- To activate gesture : Put two fingers near each other, lift one finger up.
- To zoom-in (make things bigger): Activate gesture near the center of the screen. Move your remaining finger away from the gesture position to zoom-in.
- [new in v003] To zoom-in with specified zoom-in position: Do a normal touch to the zoom-in position (your face in an image, for example), then activate the gesture a little bit away from the zoom-in position shortly after the previous normal touch, then drag to zoom. I know, it's a little bit hard to understand ~.~ I will make a short clip for the tutorial
- To zoom-out (make things smaller): Activate gesture at the corner or the side of the screen. Move your remaining finger toward the screen center to zoom-out.
- To rotate : Activate gesture at the corner or the side of the screen. Move your remaining finger around the screen center to rotate.
Practice your 1 finger pinch zoom with MultiTouch Visualizer 2. Tutorial for zoom in, zoom out, and rotate can be watched here
Requirements
- Rooted
- xRecovery (for update.zip installation)
For people who have previous x8gesture.ko and want to only update to new one without any other changes use the attached x8gesture_v004_update.zip to flash with xRecovery. Then edit hw_config.sh and add following code at top:
Code:
#dx: our modded touchscreen driver
insmod /system/lib/modules/x8gesture.ko
[IMG]http://tapa.tk/mu/7560d9ef-d470-2e3d.jpg[/IMG] [IMG]http://tapa.tk/mu/7560d9ef-d484-c533.jpg[/IMG]
Hope it helps.[/U][/B][/SIZE][/COLOR]
[SIZE="4"][COLOR="DarkOrchid"][B][U]Instruction for manual installation:[/U][/B][/COLOR]
- Remount /system as rw
- Copy the attached x8gesture.ko below to /system/lib/modules
- Change hw_config.sh in your /system/etc, add this code at the beginning
Code:
# dx: our modded touchscreen driver
insmod /system/lib/modules/x8gesture.ko
- Push modified hw_config.sh back to your phone, reboot[/SIZE]
[B][U][COLOR="Blue"]Instruction for installation with update.zip:[/COLOR][/U][/B]
- [B][U][SIZE="4"][/SIZE][/U][/B]: These update.zip will disable X8Overclock if it's enabled on your system. It's much better if you do the manual installation above.
- Download update.zip accImportant ording to your current ROM
- Reboot and flash with xRecovery
- Report bugs
[B][COLOR="DarkOrchid"]List of update.zip[/COLOR][/B]
[B][COLOR="DarkOrchid"]v004 releases[/COLOR][/B]
- For Stock SE 2.0.1.A.0.47 : update-2.0.1.A.0.47-2011-04-13-signed.zip (9.69 KB) [url]http://www.multiupload.com/JQIPMR4FS5[/url]
- For Stock SE 2.1.1.A.0.6 : update-2.1.1.A.0.6-2011-04-13-signed.zip (9.45 KB) [url]http://www.multiupload.com/EJPLJL0NEY[/url]
- For racht's CM7-J005 HACKDROID : pdate-cm7j005hackdroid-2011-04-13-signed.zip (9.98 KB) [url]http://www.multiupload.com/EMU5K5ZYNF[/url]
- For jerpelea's CM7-006a : update-cm7j006a-2011-04-13-signed.zip (9.61 KB) [url]http://www.multiupload.com/4KER24ZCXX[/url]
- For racht's HACKDROID 0.15 : update-floyo15-2011-04-13-signed.zip (9.69 KB) [url]http://www.multiupload.com/PS9UPCX46B[/url]
- For nobodyAtall's MiniCM beta 2 : update-minicm2-2011-04-13-signed.zip (9.44 KB) [url]http://www.multiupload.com/LHT0RC4F4M[/url]
[B]v003 releases[/B]
- For Stock SE 2.0.1.A.0.47 : update-2.0.1.A.0.47-2011-03-26-rel-signed.zip (9.71 KB) [url]http://www.multiupload.com/USKMD30N67[/url]
- For Stock SE 2.1.1.A.0.6 : update-2.1.1.A.0.6-2011-03-26-rel-signed.zip (9.47 KB) [url]http://www.multiupload.com/CL2SH8FJGK[/url]
- For racht's CM7-J005 HACKDROID : update-cm7j005hackdroid-2011-03-26-rel-signed.zip (10 KB) [url]http://www.multiupload.com/1X0IWZKRN6[/url]
- For jerpelea's CM7-006a : update-cm7j006a-2011-03-26-rel-signed.zip (9.63 KB) [url]http://www.multiupload.com/6N2HAGE9OC[/url]
- For racht's CM7-1.0 RC1 : update-cm7r1.0rc1-2011-03-26-rel-signed.zip (9.62 KB) [url]http://www.multiupload.com/PMN0H2LB52[/url]
- For racht's HACKDROID 0.15 : update-floyo15-2011-03-26-rel-signed.zip (9.71 KB) [url]http://www.multiupload.com/UJK029BLIX[/url]
- For nobodyAtall's MiniCM beta 2 : update-minicm2-2011-03-26-rel-signed.zip (9.47 KB) [url]http://www.multiupload.com/Z7XKFKP3A5[/url]
For other ROMs, please upload your /system/etc/hw_config.sh so I can customize your ROM's hw_config to load the kernel module
[B][U]Troubleshoot[/U][/B]
Q. Help! It doesn't work!
A. Try this command from your PC shell
[CODE]
adb shell
dmesg | grep X8Gesture
If there is some output, that means the module is loaded. You need to practice first.
Q. Help! I did as above, but nothing was output
A. Check your hw_config.sh or your ramdisk to be sure that it's loaded during boot
Q. Help! dmesg above output something, but it doesn't work!
A. Maybe you're trying to load it in X10 Mini Pro or other devices? It supports only X8 and X10 mini.
Give it a try.
If u like my post, thank me!!
Yep works on MiniCM, althrough..I think most of the packages won't suit to our x10mini(I mean official firmware ones)
omg is working!!!!!! But it wants callibration. I downloaded a multitouch tester from the market and it found 2 touch points.
sorry for my bad english!!
Works well on MiniCM-Beta2 !
Tested in Google Maps, Web Browser, and checked with Multitouch Tester.
thank you so much. Works perfect in my x10 mini SE 2.1.1.A.0.6.
Works Great ! on E10i 2.1.1.A.0.6
it can be zoom in Angrybird?
make one for cyanogen6 v3.4?
nakato124 said:
Works Great ! on E10i 2.1.1.A.0.6
it can be zoom in Angrybird?
Click to expand...
Click to collapse
Here it works.
It's good and it's a good start !!
Works on cm7!
congratulation!
great job,will try this out later on this evening!
Keep it up.
Best wishes.
Its really awesome aint it guys! Yup it requires calibration though.....but otherwise, its the next best alternative to the pinch-zoom for X10!!
guys because i don't have the x10 mini yet (in 2 days i will buy it)i cant test this one question:it makes the x10 mini recognise 2 fingers? or something like emulate the second finger?
I need a help from you X10mini guys: can somebody do a fresh restart and paste the content of dmesg on your X10mini? I don't have an X10mini but I want to see your dmesg info.
Thanks.
Sora94 said:
guys because i don't have the x10 mini yet (in 2 days i will buy it)i cant test this one question:it makes the x10 mini recognise 2 fingers? or something like emulate the second finger?
Click to expand...
Click to collapse
Hey its just a 1-pinch zoom (read how it works in the main thread). And i suggest u dont buy the mini! No offence....SE have quit on it and wont provide any new updates on it!
doixanh said:
I need a help from you X10mini guys: can somebody do a fresh restart and paste the content of dmesg on your X10mini? I don't have an X10mini but I want to see your dmesg info.
Thanks.
Click to expand...
Click to collapse
Alrite mann! I'll let u no ASAP. Thanks for the work. Am out rite now, will post as soon as i come back.
Regards,
death214
doixanh said:
I need a help from you X10mini guys: can somebody do a fresh restart and paste the content of dmesg on your X10mini? I don't have an X10mini but I want to see your dmesg info.
Thanks.
Click to expand...
Click to collapse
1 q....how do i see the dmesg info?
death214 said:
1 q....how do i see the dmesg info?
Click to expand...
Click to collapse
I think you can see in adb logcat but i don't know what is fresh restart.
Sorry for my english
Sent from my X10mini using XDA Premium App
Here is the dmesg info from my mini.
nice work dude
Thanks for uploading the dmesg @nishan.
Related
[size=+2][APP][Update 2009/04/08] SSMaHo 0.0.4.0 [/size]
Guys
I reimplemented the old SSMaPa. completly new technology.
There aren't many new features till now, but the new architecture allows further changes..
some new features
- differing between mail and sms now possible
- added some new replacements
- landscape mode fully supported
- should be working generic on all manila versions
I also added gsgetfile.dll as default file chooser for ssmaho
How to use:
- if you was using old ssmapa, do first a 'full restore' in ssmapa!
- Extract all 4 files and copy them to a folder on your phone (the folder has to stay on the phone.. I recommand /programs/ssmaho)
- run ssmahogui.exe
- click on the first button
- click on load configuration
- click on "Start INIT-Assistant"
- There are two modes, prefer the fast init, only if this is not working, choose the manila file from the slowinit box. Click on Fast Init (or maybe slow init)
- There should appear something like: "CreateProcessW offset found: 0x002d4240, ..." If that's not the case and "unknown exetype" appears, then use slow init.. In some cases you have to click 2 times... If this isn't working too, then sorry, ssmaho will not work on your device.
- click close
- click on "start assigner mode"
- minimize ssmaho (click right top corner, fast, or start -> today)
- Go back to manila
- click on every element you want to replace in manila
- there should pop up a window 'Assigner'. enable in minimum following checkboxes: Active, EXE Name, all News
---- Match condition commandline is useful for hooking sms inbox and mail inbox
- with the button "..." choose the new file
- click ok
- assign as many as you want.. windows are not working, but there are more than in ssmapa.. also landscape alignment should be working
- when you're done go back to ssmahoGUI and click on "Stop all".
- go to shortcuts, I recommand enabling all...
- click on "Save Configuration"
- click on About (or don't do it )
- close the program
- You have under programs new shortcuts: SSMaHo Attach / SSMaHo Detach. click on "ssmaho attach" and the new programs get called when working with manila.
--> You have to execute the attacher everytime manila crashes. If you use autostart it should automatically attaching after softreset, but not after a crash.
I don't think that this tool is able to destroy something on the phone. Never mind, I'm not responsible for any damages.
[size=+1]Upgrade instructions[/size]
1. copy all the new files to the same directory
2. Click on "Install new HookerDll"
2.1. If this fails, click on "Load Configuration" -> "Stop All"
2.2 Reclick on "Install new HookerDll"
3. ReDo the initialisation. You should use FastInit. There should appear 6 offsets
4. Ready.. You can now use ssmaho...
With version 0.0.3.0 I implemented a real inline patch (hooking a function of manila). a generic solution for smt. like this is heavy... theoretically it should work (tested on a rhodium and old manila)... but as soon as htc changes smt deep, it won't be working anymore..
[size=+1]Tricks[/size]
- Everytime the first button is available, click it... you'll then have lesser "where the hell"-messages
- if you have problems with one function / one hook, deactivate it with "manual configuration"
[size=+1]Important[/size]
- The new inlinefunction-hooking of manila can only be searched with fast init. Also, fast Init isn't as fast as before, because it has to search more data... be patient after clicking on it..
Please donate for me! I'm a apprentice and use a lot of my free time for working on the computer, to be able to create such tools.
[size=+2]Thank you [/size]
Received Donations:
15 Euro - 28wagram - 2009/05/13 - nice, thank you
10 Euro - ppc3300 - 2009/04/07 - thank you
10 Euro - lacasi - 2009/07/23 - thank you
10 Euro - Martin L. - 2010/01/02 - thank you
5 Euro - juwenio - 2009/04/03 - thank you
5 Euro - Trident - 2009/04/09 - thank you
5 Euro - mpayne - 2009/06/11 - thank you
5 Euro - 1swat - 2009/06/25 - thank you
5 Euro - aussiebum - 2009/08/02 - thank you
5 Euro - plerche - 2010/02/23 - thank you
Changelog:
Version 0.0.4.0 (2009/04/08)
- Improved slow init. ssmaho now fully working on all devices where manila.exe isn't read-accessible (file is fully readable in ram )
--> Full support for Dutty 2.6 xtreme !
- added crash handler
--> on new phones, evertime manila crashes (not restart, crash) ssmaho gets reattached automatically. This feature is like all other event-based and not polling anything..
- fixed some bugs
Version 0.0.3.2 (2009/04/06)
- Removed exe limitation.. all filetypes are now supported
Version 0.0.3.1 (2009/04/05)
- ssmapat2hook.dll doesn't get removed after install
- improved --with-wait function. probably it helps, probably not..
- filename is no more case-sensitive
- last filename will be shown in fast-init box
- change on assigner: clicking to cancel will do the original action, clicking Ok will supress it
- added architecture for an external api interface (if your're interested, contact me)
- added new patch (only for developer usage, on page change)
Version 0.0.3.0 (2009/03/28)
- After hours and many evenings of work, I am proud to present the new ssmaho-version!
- Added special-infile-patch, hooks every subview of manila.
- Rhodium calendar / Call History and much more gets triggered (altough, on old manila versions, call history isn't hookable)
- bugfixes, autosave, ...
- added manual offset changer for professionals
Version 0.0.2.0 (2009/03/19)
- Added new hook (click on sms / mails / maybe rhodium calendar)
Version 0.0.1.0 (2009/03/16)
- First official release
- Thank NLS and hanackin for their patience on beta testing
P.S. Excuse me for my english...
[email protected]
Thanks a bunch, Svenso... I am a long time SSMAPA user, and I am very happy to see this new app.
So will this prog allow me to have wmp open instead of tf3d music player when i touch the music tab in touchflo? also will this software work on the new manila?
cheers
That´s indeed nice improvments. The question is if this app supports the upcoming "XBmod Manila Rhodium port". If it is you´re my hero!!
Really cool tool. I hope that no bugs will be found.
Hmm, previous version of this tool used manila's files patches, I suppose, but now we have to check an autostart option... that means that you patch manila in the RAM, but not the file. Does your app hang in memory or it starts after a soft reset, patches and unloads?
Testing now... not sure if I am clear on what everything on the pop-up assignment screen does.
*edit* Ok, I think I've got it. I have successfully mapped the "time click" on XBMod's HD manila.
If I click on the call history button it brings up the call history instead of bringing up the assignment screen. I'm assuming this element cannot be mapped?
Yes unfortunately you assume correctly.
But SSMaHo is a better base to develop on, anyway.
NLS said:
Yes unfortunately you assume correctly.
But SSMaHo is a better base to develop on, anyway.
Click to expand...
Click to collapse
I'm already loving it. The fact that it works on the HD manila is wonderful.
*edit* How does the "differing between mail and sms" work? If I click on the "all messages" button on the sms tab will it just remap this button?
Hi,
Thanks a lot for all your effort with this tool. It's a great idea and hopefully it'll work on my device in one of the next versions. Stumbled upon your tool yesterday and read the whole thread of the previous tool, and now tried this one. But it seems there's still something going on with this manila version, your tool doesn't like.
When I press "Start Assigner Mode" I get a popup saying "thats bad. Proc not found -.-"
I'm using a new HTC Touch Cruise (09). It already features the new "Footprint Tab". In case I can send any file to you to help, please don't hesitate to ask.
Until then: good luck with your exams!
What you mean a new "HTC Touch Cruise"?
Unless I miss something Touch Cruise is an old (obsolete) model...
change music player?
Ok i searched the old thread (alpha version) as well and found no answers as to whether this software could replace the manila music player in touchflo.
Could someone please confirm or deny whether its possible to change it to say windows media player?
thanks in advance
Why don't you just try?
i tried using it on the rhodium port but it doesnt seem to work :-\
im just following the instructions and it cant initiate the manilla.exe properly
great work none the less for the HD manilla! =D
sayazs said:
i tried using it on the rhodium port but it doesnt seem to work :-\
im just following the instructions and it cant initiate the manilla.exe properly
great work none the less for the HD manilla! =D
Click to expand...
Click to collapse
The Rhodium port is probably manila2.exe. Haven't tried it yet, I'm just guessing.
NLS said:
Why don't you just try?
Click to expand...
Click to collapse
Because I'd like to hear from others who have tried it first and hear about their experiences in case theres a major problem or other.
And now with the above posts i now know that it doesnt work with the new manila and therefore i dont have to risk messing up anything on my phone.
Hoping in the future that Rhodium/Manila2 is supported as it looks like a great app!
Cheers
This application cannot mess anything with your device.
Try to manually attach first, see if it works, then choose to autostart.
I've try it in my jade ( aka touch 3g ) and works perfectly !!!
i replace time link with better g-alarm !!!!
tnku very much.
Many thanks.
I've tried in my HD with Manila-Rhodium (Dutty exreme 2.2 ROM). After Start Assigner-Mode there isn't any pop up window
Any help.
Thanks
Not working at my Touch HD... My current ROM is Touch of HD v3.4.1 and when I click at Start Assigner-Mode it gives back the error: Master failure. where the hell you put my dll in?!
I placed all the four files in a folder (named it SSMaHo) at the root of the phone!
May 18th. I'm not in a good mood today.
I'm tired of repeating the same thing every time. Many people pretend that they know lots of things while knowing nothing about it. I'm really tired and bored.
To me, pinch zoom is enough. That's my initial goal of this project. I don't care about such Game Mode. I made that for those noisy kids, and you can see what I got in return.
As I said, this project will be discontinued. I pushed everything on github, anybody can improve it.
Good luck to you guys. Anyone who continues to improve this can send me a PM for editing this thread content.
dx.
_____________________________________
Rom cookers: if you include this module in your ROM, please make a link to this post in your release post, so your users can know how to work with it and update the module themselves
Intro
I'm working with a kernel module to replace SE touchscreen driver to support dualtouch. However, as I found out, it will mostly not be supported by our hardware, because X8 has only 1 sensor and that sensor supports only 1 finger. I don't know whether we can have dual touch if we flash the screen firmware. I will have a look on that.
A temporary solution now is to make some gestures based on user fingers' relative position. The idea is that we make Android to think that the second finger is also pressed, by generating second finger events from the driver. Anybody who wants to get more details about the previous development, please have a look at this thread
Release history
May 11 v007. Game mode added. Look at HOWTO section for more details.
May 06 v006. No more pinch zoom after 1 finger is lifted. Less pinch zoom activation time. Fixed incorrect positions for generated events.
April 30 v005. Much better "native" pinch zoom now! More stable movements, less unpredictable positions. Zoom in position is specified by your two fingers, not at the screen center.
April 23 andrej456's x8gesture. Well this is not my work, it's andrej456's work, but it's better for all of you to find the module in the first post. You guys can grab it in his post. Thanks to andrej456!
April 13 v004. Rewrite from scratch. Pinch zoom with one or two fingers.
April 03. Source released.
March 26 v003. Specify zoom-in position.
March 25 v002. Zoom-out, rotate. Module size optimization.
March 24 v001. Better finger detection. Reduced zoom-in speed.
March 23 v000. 1 finger pinch zoom-in only
Source is provided at github : https://github.com/doixanh/X8Features
Very Important : HOWTO
Modes
Starting from v007, X8Gesture supports two gestures: Pinch Zoom and Game Mode. Default mode is Pinch Zoom initially after each reboot.
1. Game mode
To activate game mode, keep your phone at "vertical" state, keep one finger at the bottom right and then another at the top left of your screen, one-by-one (don't release first finger).
Generally you should have more pressure with your second finger so that the digitizer recognizes it as the moving finger.
I tested with Tank Hero and it seems to work. This is not dual touch. It only makes you feel more comfortable with MT games. Sometimes it's incorrect though. That's the limitation of our hardware.
Thanks firdausmbois for the idea and your very well designed illusion!
2. Pinch Zoom
To activate Pinch Zoom mode, keep your phone at "vertical" state, keep one finger at the bottom left and then another at the top right of your screen, one-by-one (don't release first finger).
For v005 and above
It's much like natural pinch zoom now. There is no need to "activate gesture" like v004 or below anymore. However you will probably need some practice with Multitouch Visualizer 2.
For v004
To activate gesture, put your two fingers one-by-one (one finger first, then another after - don't put both at the same time) on the screen, away from each other for at least 1cm. The 2nd finger should have more pressure onto the screen. After putting your 2nd finger on the screen, wait for 0.5s, the gesture will be activated.
After the gesture is activated, you can
- Use your two pressed fingers, or
- Lift up one finger and use the remaining finger
to zoom-in/out/rotate.
I prefer keeping two fingers on the screen, because it's natural for pinch zoom. You can look at the tutorial for v004 here, and practice with MultiTouch Visualizer 2.
For v003 and below
Right now it supports only zoom-in, zoom-out, and rotate. I will improve it over time. For who says it's not working, please read this how-to very carefully:
- To activate gesture : Put two fingers near each other, lift one finger up.
- To zoom-in (make things bigger): Activate gesture near the center of the screen. Move your remaining finger away from the gesture position to zoom-in.
- [new in v003] To zoom-in with specified zoom-in position: Do a normal touch to the zoom-in position (your face in an image, for example), then activate the gesture a little bit away from the zoom-in position shortly after the previous normal touch, then drag to zoom. I know, it's a little bit hard to understand ~.~ I will make a short clip for the tutorial
- To zoom-out (make things smaller): Activate gesture at the corner or the side of the screen. Move your remaining finger toward the screen center to zoom-out.
- To rotate : Activate gesture at the corner or the side of the screen. Move your remaining finger around the screen center to rotate.
Practice your 1 finger pinch zoom with MultiTouch Visualizer 2. Tutorial for zoom in, zoom out, and rotate can be watched here
Requirements
- Rooted
- xRecovery (for update.zip installation)
- Some basic adb knowledge
Instruction for manual installation:
- Remount /system as rw
- Copy the attached x8gesture.ko below to /system/lib/modules
- Change hw_config.sh in your /system/etc, add this code at the beginning
Code:
insmod /system/lib/modules/x8gesture.ko #dx: add gestures
- Push modified hw_config.sh back to your phone, reboot
If you are using a ROM that has x8gesture already, it's simple to upgrade
- Download latest x8gesture, unzip
- Mount USB, copy from PC to sdcard
- Unmount USB
- Use Root Explorer, mount /system as RW
- Copy the extracted x8gesture.ko to /system/lib/modules, overwite existing file
- Reboot.
Instruction for installation with update.zip:
- Important : These update.zip will disable X8Overclock if it's enabled on your system. It's much better if you do the manual installation above.
- Download update.zip according to your current ROM
- Reboot and flash with xRecovery
- Report bugs
List of update.zip
v005 releases and above will not be provided in update.zip.
v004 releases
- For Stock SE 2.0.1.A.0.47 : update-2.0.1.A.0.47-2011-04-13-signed.zip (9.69 KB) http://www.multiupload.com/JQIPMR4FS5
- For Stock SE 2.1.1.A.0.6 : update-2.1.1.A.0.6-2011-04-13-signed.zip (9.45 KB) http://www.multiupload.com/EJPLJL0NEY
- For racht's CM7-J005 HACKDROID : pdate-cm7j005hackdroid-2011-04-13-signed.zip (9.98 KB) http://www.multiupload.com/EMU5K5ZYNF
- For jerpelea's CM7-006a : update-cm7j006a-2011-04-13-signed.zip (9.61 KB) http://www.multiupload.com/4KER24ZCXX
- For racht's HACKDROID 0.15 : update-floyo15-2011-04-13-signed.zip (9.69 KB) http://www.multiupload.com/PS9UPCX46B
- For nobodyAtall's MiniCM beta 2 : update-minicm2-2011-04-13-signed.zip (9.44 KB) http://www.multiupload.com/LHT0RC4F4M
v003 releases
- For Stock SE 2.0.1.A.0.47 : update-2.0.1.A.0.47-2011-03-26-rel-signed.zip (9.71 KB) http://www.multiupload.com/USKMD30N67
- For Stock SE 2.1.1.A.0.6 : update-2.1.1.A.0.6-2011-03-26-rel-signed.zip (9.47 KB) http://www.multiupload.com/CL2SH8FJGK
- For racht's CM7-J005 HACKDROID : update-cm7j005hackdroid-2011-03-26-rel-signed.zip (10 KB) http://www.multiupload.com/1X0IWZKRN6
- For jerpelea's CM7-006a : update-cm7j006a-2011-03-26-rel-signed.zip (9.63 KB) http://www.multiupload.com/6N2HAGE9OC
- For racht's CM7-1.0 RC1 : update-cm7r1.0rc1-2011-03-26-rel-signed.zip (9.62 KB) http://www.multiupload.com/PMN0H2LB52
- For racht's HACKDROID 0.15 : update-floyo15-2011-03-26-rel-signed.zip (9.71 KB) http://www.multiupload.com/UJK029BLIX
- For nobodyAtall's MiniCM beta 2 : update-minicm2-2011-03-26-rel-signed.zip (9.47 KB) http://www.multiupload.com/Z7XKFKP3A5
For other ROMs, please upload your /system/etc/hw_config.sh so I can customize your ROM's hw_config to load the kernel module
Troubleshoot
Q. Help! It doesn't work!
A. Try this command from your PC shell
Code:
adb shell
dmesg | grep X8Gesture
If there is some output, that means the module is loaded. You need to practice first.
Q. Help! I did as above, but nothing was output
A. Check your hw_config.sh or your ramdisk to be sure that it's loaded during boot
Q. Help! dmesg above output something, but it doesn't work!
A. Maybe you're trying to load it in X10 Mini Pro or other devices? It supports only X8 and X10 mini. Also, perhaps your digitizer is not Synaptics, it may be a Cypress. Look at the Attention section.
Notice:
1. This is NOT Dual Touch, as big X10 or X10 Mini Pro.
2. This is a Work In Progress. It may not behavior correctly.
3. Read the above "How to zoom" carefully before reporting that it is not working!
4. Who installed gesture module on 23-03-2011 manually : please remove the old synaptics_i2c_rmi4_dx.ko and replace with x8gesture.ko below. Update your hw_config.sh also. Sorry for the inconvenience.
ATTENTION
I've just received a full dmesg from kueh9. I see that in his X8 there is a Cypress digitizer while most of us (including me) are using Synaptics digitizer! That's why x8gesture is not working in some devices.
Thank you kueh9 for your dmesg!
For devices that are unable to use x8gesture, try this command in your phone (either with terminal or with adb shell):
Code:
dmesg | grep "cyttsp-i2c"
If you have something like this, that means your X8/X10mini is using Cypress and therefore it will not be supported by x8gesture:
Code:
<6>[ 4.185259] cyttsp_i2c_probe: Successful registration cyttsp-i2c
In this case, because I don't have X8 with Cypress digitizer, I cannot do anything for you guys. I'm sorry.
ATTENTION #2 : About multi/dual touch capabilities
For X10Mini:
Nobody sees this, at step 14? It's Synaptics T1021A !
And nobody sees this? T1021A is ClearPad 1000 !
And nobody also sees this? ClearPad 1000 is Single-Touch !
I highly believe X8 also this digitizer (Synaptics T1021A).
And guys, stop dreaming about DT/MT with custom kernels! You are the one who develops kernel modules? Or me? You think that Synaptic kernel driver can do what my kernel module cannot??
Big thanks to andrej456 for the idea and code to remove SE touchscreen driver.
Disclaimer
I'm not responsible if this module bricks your lovely phone. Use it at your own risk!
This is awesome!! Thank a lot!
This mod works on all X8 ROMs?
Wow! Thanks. Finally somebody who cares about X8.
How does it work?
Sent from my E15i using Tapatalk
doixanh said:
I'm working with a kernel module to replace SE touchscreen driver to support dualtouch. However, as I found out, it will mostly not be supported by our hardware, because X8 has only 1 sensor and that sensor supports only 1 finger. I don't know whether we can have dual touch if we flash the screen firmware. I will have look on that.
A temporary solution now is to make a one finger pinch zoom. Please notice that this is NOT 2-finger pinch zoom, as big X10.
This is a short video clip during the development.
I'll post the driver binary and instructions soon.
Big thanks to andrej456 for the idea and code to remove SE touchscreen driver.
Click to expand...
Click to collapse
I had a look at the video and it seems amazing. Im backing up my system and are waiting for you to release it so i can test it.
Be fast.thanks.
Sent from my E15i using XDA Premium App
Sounds good cant wait
Where is update.zip?
Sent from my E15i using XDA Premium App
I'm in progress of creating an update.zip for MiniCM beta 2 ~.~
doixanh said:
I'm in progress of creating an update.zip for MiniCM beta 2 ~.~
Click to expand...
Click to collapse
Not for 2.1?
Sent from my E15i using XDA Premium App
Look at the first post...
Each ROM has a different ramdisk, and thus, there will be a specific update.zip for each ROM.
Click to expand...
Click to collapse
Yap good start for MT progress
Going to test a manual installation of this module with Jerpeleas CM7 2.3.3 v006
Going to test on my Elelinux CM6
gosh... thats amazing!!
Nice n awesome!!
Woohoo
Sent from my X8 using XDA App
What update.zip need to use to enable dualtouch on stock 2.0.1.A.0.47?
wat abt playing PES? Will that support, coz u know, its quite hard to play PES without that....
Sent from my E15i using XDA Premium App
while flashing update in xrecovery i got E:Syntax Error in Update Script. Pls fix it
sorry for noob question..
i cant find ramdisk.tar in /system/bin/ for manual installation..
It finally happened. A persistent and good dev "AnDyX" managed to get the digitizer working with multitouch
His thread:
http://forum.xda-developers.com/showthread.php?t=1135965
I think I can say on behalf of the X8/cypress community THANK YOU.
This thread is now obsolute, and is kept only as a info thread!
-------------------------------------------------------------------
The digitizer in the X8 is:
CY8CTMA340
These are some officiel links for the chipsets
Product Sheet:
http://www.cypress.com/?docID=29019
Product info on the homepage:
http://www.cypress.com/?id=1938&rID=51366
Android beta drivers from cypress homepage
http://www.cypress.com/?rID=44238
I have created an account and downloadet these drivers and attached them to this post. It is an i2c driver for the module View attachment Cypress_TTSP_Android_Driver_Test.zip
However the driver included in the driver release by sonyericsson looks much simpler, and thats maybe why it does not support multitouch: View attachment cyttsp.zip
The "cyttsp_i2c.c" file included in the sonyerricson release contains 160 lines of code, and the one from cypress homepage contains 2009 lines of code !
But that one also works for multiple devices.
Detection of which chipset the phone has!
Please there is no secure way to determine what digitizer the phone has from the package, as I initially thought. I maybe thought the SI number had anything to do with it but i was WRONG.
Please stop posting SI numbers in the thread. They cannot be used
You MUST root your phone and have a terminal installed in order to see the chipset version, sorry but that's the only current way:
Taken from doixanh synaptic thread:
Try this command in your phone (either with terminal or with adb shell):
Code:
dmesg | grep cyttsp-i2c
If you have something like this, that means your X8/X10mini is using Cypress and therefore it will not be supported by x8gesture:
Code:
<6>[ 4.185259] cyttsp_i2c_probe: Successful registration cyttsp-i2c
Also in my experience if you have "permission denied" you must first enter this in the terminal
Code:
su
and then you can enter the above commands!
Progress from here on
See the beginning of the thread!
Please write in this thread http://forum.xda-developers.com/showthread.php?t=1135965 if you have anything usefull regarding development of the driver and try to keep it clean.
Usefull links
[Dev] Bootloader bypassing by Blagus
http://forum.xda-developers.com/showthread.php?t=1023670
[Module] X8Gesture Pinch zoom | X8 | X10mini | v007 | 11-05-11 by Mr. module man himself, doixanh
http://forum.xda-developers.com/showthread.php?t=1004740
Multi Touch ? Mod Edit: Use this thread for the purpose.
http://forum.xda-developers.com/showthread.php?t=976948
mcmanuf said:
Hello all you genius devs.
It could be really cool if you could possibly be looking into the cypress digitizer for X8.
I know many of you don't have the X8 with the cypress digitizer, but the synaptic as also stated in this thread:
http://forum.xda-developers.com/showthread.php?t=1064576
Also some digitizer which looks alot the same as the cypress in the X8 is in the x10 mini pro thread
http://forum.xda-developers.com/showthread.php?t=1064558
Would a dev be looking into it if someone could borrow the DEV a X8 with a cypress digitizer? That would be awesome.
I don't own a X8 myself otherwise I would gladly send it over to a dev.
But my brother owns a white X8 and it has a cypress digitzer. My father has a black X8 and that one has a synaptic.
On the White X8 box it says:
E15i
SI 1242-3079.4 DA
Maybe this string contains some identification to the fact it is a X8 with cypress.
Click to expand...
Click to collapse
yeah..it would be cool if some dev can unleash the multitouch potential of the cypress..i own an x8 with cypress myself and i really want it..i dont really care about gaming,i only want the pinch zooming ability because i surf the net a lot with my phone..
Which color X8 do you have?
And can you list what it says on the package if you still have it?
E15i (white, dark blue)
SI 1241-9136.2 EN,IN from Indonesia
hope this can help
go dualtouch!!!
My X8 has cypress digitizer too..
E15i White
SI 1242-4842.2 EL, EN Greece
On my box is
E15i. White/silver
SI 1243 - 5606. 3. EN
So i have synaptics or cypress digitizer ??
Sent from my X8 using Tapatalk
proadi96
I am not sure..
I would probably say cypress because of the "SI-124" but there is a better way to check it you have terminal on the phone..
I will be sure whenever i can confirm that the synaptic have something different other than "si-124" on the package--
My Synaptics X8 also has got 124x-xxxx SI code. SI code doesn't tell the HW revision. SI code represents region.
Thanks for that info.. So now at least i know that is useless info indeed..
The problem is the box does not state the manufactoring date :-(
Anyway this was just trying to identify the digitizer type without rooting the phone..
I will update the first post to reflect this..
Mine says SI 1242-4363 White X8.
Does that mean I've got a Cypress digitizer?
I'm not a Dev but would love to help any Dev with testing?
Roland
we can't look at si, i change my si to get update and si is only region
more(or maybe all) members xda have coustoms roms si is changed
but any works at mt(or dualtouch) is good idea
if u do something , i test it with pleasure
My xperia x8 that i buy from amazon, is 1241-9136.2 and fake dual touch doesnt work for me
SI is not needed for that
i put code from frist post and nothing happen
Please read the first post again. This is a developer thread. The module/driver HAS NOT been developed yet..
Hello from me too I have a cypress digitizer phone but i have found a strange thing today (while i was reading about linux kernel modules as general) - no kernel module is loaded for it but one for synaptics is
# cat /proc/modules
cat /proc/modules
tiwlan_drv 950068 0 - Live 0xbf12c000
x8uv 1228 0 - Live 0xbf03f000
x8mddi 1116 0 [permanent], Live 0xbf039000
synaptics_i2c_rmi4 11908 0 - Live 0xbf034000
twofish 9308 0 - Live 0xbf02c000
twofish_common 15740 1 twofish, Live 0xbf026000
dm_crypt 13052 0 - Live 0xbf01d000
dm_mod 53216 1 dm_crypt, Live 0xbf00b000
sdio 20708 1 tiwlan_drv, Live 0xbf000000
#
Click to expand...
Click to collapse
... So can anyone point me to the source code for 2.1 on our devices because i can't find it on SE development page. I'll continue to investigate ... thanks in advance
Cypress chip that the newer x8 uses is 4 touch supportive.
So change the topic name from DualTouch to Multitouch!
Batcila said:
Hello from me too I have a cypress digitizer phone but i have found a strange thing today (while i was reading about linux kernel modules as general) - no kernel module is loaded for it but one for synaptics is
... So can anyone point me to the source code for 2.1 on our devices because i can't find it on SE development page. I'll continue to investigate ... thanks in advance
Click to expand...
Click to collapse
what do you mean by there is no kernel module loaded? from what i see, the phone loads many modules there. and also yes, the synaptic module is also loaded but useless in cypress phones.
source code is in android's github.
aldee_s said:
what do you mean by there is no kernel module loaded? from what i see, the phone loads many modules there. and also yes, the synaptic module is also loaded but useless in cypress phones.
source code is in android's github.
Click to expand...
Click to collapse
What i mean is that driver for cypress is not loaded as module but compiled with the kernel ... and i can't find source for our x8 (e15i) here http://developer.sonyericsson.com/cws/devworld/search-downloads/opensource?cc=gb&lc=en there is only one for e16i(w8) ... and x8 on android 1.6 .... but as i remember we have e15i from December 2010 when people found that sony-ericsson didn't give their last source
edit: sorry my bad .... found them ^_^
When I type
Code:
dmesg | grep "cyttsp-i2c"
into terminal I got
Code:
<6>[ 2.5DD486] cyttsp_i2c_probe: probe of 0-0D24 failed with error -12
as response.
Does it somehow help you.
I am using latest MiniCM6 Release
This is module that enables dual touch in Cypress touchpad.
Currently there is nothing new to implement unless there will be some breakthrough e.g: datasheet for Cypress chip. I know that FroyoBread people have problems I couldn't solve it without help.
Prerequisites:
- cypress based touchpad,
- X8,
- Baseband x15
Known issues:
- on FroyoBread - you can't accept or reject the incoming call - works if added in hw_config.sh - thanks der_mart
- cypress chip don't report second touch if distance between fingers is lower then about 110 pixels (by AnDyX)
- if you slide one finger to second - chip reports one finger and geometric center will be in the middle of two fingers (by AnDyX)
- sometimes doesn't report second touch if you quickly press both fingers alltogether (by AnDyX)
- on FroyoBread sliding position of touch from first finger to second if you release first and quicly press second finger in another position - could you check both v003 versions guys ?
How to check which chip our X8 has:
- if you already have X8Gesture module from doixanh and it works on your X8 - you have synaptic - so from now stop yelling, screaming and complaining - for me this is disrespect his work !
- run following command in shell (via adb or Terminal Emulator):
Code:
dmesg | grep cyttsp-i2c
If you have something like this, that means your X8 is using Cypress chip otherwise your X8 has Synaptic chip (so look at note above):
Code:
cyttsp_i2c_probe: Successful registration cyttsp-i2c
if you have "permission denied" you must first enter this in the terminal
Code:
su
and then you can enter the above commands.
Manual installation:
- push ax8mt.ko to /system/lib/modules
- run the following command
Code:
insmod /system/lib/modules/ax8mt.ko
- run dmesg in shell, must contains following lines:
Code:
ax8mt: module v005 loaded
input: cyttsp-spi as /devices/platform/i2c-adapter/i2c-0/0-0024/input/input3
cyttsp-i2c 0-0024: ax8mt_cyttsp_setup_input_dev: Registered input device cyttsp-spi
ax8mt: Enjoy dual touch now :)
ax8mt_init: Mode set to: andyx
Thats all - dual touch should works now.
If system reboot happens, get last kernel messages (get it using adb command:
Code:
adb pull /proc/last_kmsg
) and share
Check in Multitouch Visualiser - if it works correctly.
Until you're sure that it works with your hardware, don't install it to hw_config.sh.
Release history
v005:
- now there are four modes in driver (can be switched on the fly) each differently reports touches to OS:
* 'original' - uses code from driver - don't send tracking id that chip reports - so OS must do tracking fingers it by itself,
* original_tid' - uses code from driver - send tracking id from chip - in Multitouch Visualiser/Tester - there are additional id number,
* 'andyx' - default mode - send tracking id to OS - but only reports track id set to 1 or 2 - so there is no additional id number in Multitouch Visualiser,
* 'desire' - don't send tracking id that chip reports - so OS must do tracking fingers it by itself; reports touches similar to driver in HTC Desire.
In XGin - all version works - so by default 'andyx' mode is set, IMHO - don't forces OS to track touches by itself and up to 2 tracking id ( two fingers ), so should be fastest.
How to change mode:
In dmesg output there will be line:
Code:
ax8mt: module v005 loaded
input: cyttsp-spi as /devices/platform/i2c-adapter/i2c-0/0-0024/input/input3
Use device name from second line without two last slashes at the end and add '/sys/ at the beginning:
Code:
echo "andyx" > /sys/devices/platform/i2c-adapter/i2c-0/0-0024/mode
Dmesg command output should contain:
Code:
attr_driver_mode: Mode switched to: andyx
v004:
- driver reports smaller constant touch area,
- this is version that not send tracking id sent to OS,
- added sending the same information from driver to OS like in Synaptic driver - maybe it helps FroyoBread people.
v003:
- removed all hacks - module is initialised in init section,
- two versions with and without tracking id sent to OS.
v002:
- code cleaning,
- module is removable using rmmod command,
- driver send track id to OS - visible in Multitouch Visualiser.
v001:
- just initial version
I should mention that der_mart published his version at nearly the same time: DT
Cypress product info:
I found this on cypress page:
Availability
The CY8CTMA340-XXX-03 (two-finger support) and CY8CTMA340-XXX-11 (four-finger support) device families are both available today from Cypress. Qualified customers can contact Cypress for more information and to obtain samples.
Click to expand...
Click to collapse
So everything depends which version of chip is in our X8.
Note:
It uses code to hijacking methods from doixanh X8Overclock module.
Disclaimer
I'm not responsible if this module damages your lovely phone. Use it at your own risk!
Nice work. At least there's someone with Cypress device
Gratz!
Can i try it out on my synaptics x8 ?
Sent from my X8 using Tapatalk
I hope that soon cypress owners get this module stable enough to enable auto load on boot and have fun. Nice work mate.
Sent from my X8 using XDA App
when i copy
insmod /system/lib/modules/ax8mt.ko
in terminal emulator it says "failed (operation not permitted)"
what i have to do?
You need to write first
Code:
su
and press allow
Congratulations Guys
Cheers,
d4.
proadi96 said:
Can i try it out on my synaptics x8 ?
Sent from my X8 using Tapatalk
Click to expand...
Click to collapse
Nothing really happened, for synaptic you must use X8Gesture module from doixanh
it works for me thanks a lot
Tried it twice yet (I rebooted the phone after the first success), no kernel panic, it works. As I wrote in the generic MT topic: "When you make 2 touch simultaenously it's ok, but when you lift one of your finger it won't recognise the second touch until you move your finger that left off on your screen."
Don't be offended, it is just a bug report, and I know this is the first DT module for us, and yet, it is now far better than the Fake MT that synaptics can do. We are really lucky that you're here and do this. Thanks a lot!
Now I'll try to make a kernel panic reboot. I'll report back how many tries it needs to fail the loading.
(on ROM FroyoBread v12- from doixanh <-- great man too )
skowrone said:
it works for me thanks a lot
Click to expand...
Click to collapse
how did it work you mean you got real dual touch now on your x8!
it woooooorks
thank you!!
WOW man !!!
It's working ...
I've just test it in Multitouch Visualizer, Google Maps and Gallery
edit: Yeah it works in games too ...
Just downloaded few games and apps with multitouch features just to test ... so far so good
dzadzev said:
WOW man !!!
It's working ...
I've just test it in Multitouch Visualizer, Google Maps and Gallery
Click to expand...
Click to collapse
It works under games too, this is the proof we have got real DT (without pressure recognizing for now), not fake DT or Pinch Zoom!
can some one make a youtube video to show us this module and how it works , congratulations for the x8 cybress users too bad for us the synpatics users we are waaaaaaaaay out of luck on this one
skyboyextreme said:
can some one make a youtube video to show us this module and how it works , congratulations for the x8 cybress users too bad for us the synpatics users we are waaaaaaaaay out of luck on this one
Click to expand...
Click to collapse
Don't be sad or disappointed. You've got pinch zoom and game mode, so if you're not a big mobile gamer, it is like the cypress module. BTW this developement is for showing SE that how rude are they with their customers, and to say SE that they must stop lie and get these REAL developers on XDA a good job for good money! Because as I see, the devs here on XDA are far more good at programming than SE's developers. Cheers.
BTW Tomorrow I'll make a video of it, but now it is too late here for this
after reboot it doesn't work...
how can i reactivate it?
WOW real DT? Realy cool! We have so greaaaaaaat devs here on XDA! What they made and are making for us is realy incredible! So thx all of us!!! X8 rocks!
Sent from my X8 using XDA App
feel jealous now!!!
cosworth1988 said:
after reboot it doesn't work...
how can i reactivate it?
Click to expand...
Click to collapse
You need to insmod again.
If you wanna do it permanent, you need to edit hw_config, and add the insmod on it, you can check my signature, there's a HW_Config Editor
cosworth1988 said:
after reboot it doesn't work...
how can i reactivate it?
Click to expand...
Click to collapse
You can reactivate it only if you read AnDyX first post, even you'll get enlightened that this is not a permanent module, this is why it must not loaded at boot! It can cause kernel panic, so it is better for now if you load it manually after the OS loaded
Hi all,
I make this thread to poll how many people have sensors problem with MiniCM7. ( if you have trouble, post a message, because i do a mistake with the poll, and i can t see we have trouble , thanks )
My accelerometer doesn't work
NAA knows this probleme.
NAA have changed the driver of the sensor in the last MiniCM ( 2.1.4,2.1.5,.2.1.6,2.1.7 ) and now my sensor doesn t work. ( and for some other users )
### MiniCM7-2.1.4
* Sensors are now built from source (no compat mode). No sensor delays
* Many CM fixes related to stability, bugs and new features
* Disabled automatic light sensor screen dimming
* Automatic brightness now works (select tickbox from display settings and also allow light decrease from CM Display Settings)
* Liblights fixes
Click to expand...
Click to collapse
I hope NAA is working on this probleme
But you can do that for now :
Open MiniCM 2.1.3 with winrar :
You need : libsensorservice.so ( system => lib ) and sensors.default.so ( system => lib => hw ); sensors.goldfish.so ( system => lib => hw )
Extract this 3 files .
Now, open the new MiniCM ( ex : 2.1.7 the lastest ) with winrar :
-go to system => lib; delete libsensorservice.so and add libsensorservice.so ( that s taken from MiniCM 2.1.3 )
-go to system => lib => hw; delete sensors.goldfish.so and sensors.robyn.so; and add sensors.default.so and sensors.goldfish.so ( that s taken from MiniCM 2.1.3 )
Now, flash your phone with the new MiniCM that is created, and your phone will use the compatibility driver, and your acceleromter must work
TESTED with my phone !
PS: This is my Modify version with compatibility driver
http://depositfiles.com/files/axqjrblfd
Don t forget, for a fresh install : ( you will lose all data )
Flash your phone with the last NAA kernel ( 09 )
Turn on your phone and go to recovery
Wipe data/factor reset
Wipe cache partition
=>advanced , Wipe dalvik cache
Install MiniCM ( modified )
Install gapps
If some people have same problem, and if my modified MiniCM works for other; I will upload the new MiniCM modified.
Just ask, and i will do
Original thread : http://forum.xda-developers.com/showthread.php?t=1456028
http://code.google.com/p/minicm/iss...Milestone Owner Summary&groupby=&sort=&id=347
Sorry for my bad English
Hi,
I ve trouble with my sensor / accelerometer ( again and again ).; he doesn t work
This is my adb logcat and dmesg with MiniCM 2.1.9 + K 11
ADB logcat http://www.mirorii.com/fichier/23/495158/logcat_2-1-9-txt.html
DMESG http://www.mirorii.com/fichier/41/495159/dmesg_minicm_2-1-9-txt.html
And I use MiniCM 2.1.9 with older lib ( from MiniCM 2.1.3, libsensorservice.so ( system/lib ) and sensors.default.so + sensors.goldfish.so ( system/lib/hw ) ) and my sensor / accelerometer works ( in compat mode )
This my adb logcat and dmesg with MiniCM 2.1.9 with old lib + K 11
ADB logcat http://www.mirorii.com/fichier/91/495168/logcat_2-1-9_MOD-txt.html
DMESG http://www.mirorii.com/fichier/40/495172/dmesg_minicm_2-1-9_MOD-txt.html
I hope someone can help me
Some of you don't see it. but there is a clear difference between 2.1 and custom.
small lags for starters.
no filtering secondly.
Also the source SE drops is mostly missing bits.
I'm really not trolling the developer..
To be honest every rom since 2.2.1... has Accl issue's.
Custom kernel or not.
My accelerometer works.. fine.. good enough.
This is my MiniCM7 2.1.9 modify
http://www.mirorii.com/fichier/64/495974/MiniCM7-2-1-9-MOD-zip.html
SpliFFdu95240 said:
This my MiniCM7 2.1.9 modify
http://www.mirorii.com/fichier/64/495974/MiniCM7-2-1-9-MOD-zip.html
Click to expand...
Click to collapse
?? explain.
Is this a mod for the Accelerometer?
SpliFFdu95240 said:
Hi all,
I make this thread to poll how many people have sensors problem with MiniCM7. ( if you have trouble, post a message, because i do a mistake with the poll, and i can t see we have trouble , thanks )
My accelerometer doesn't work
NAA knows this probleme.
NAA have changed the driver of the sensor in the last MiniCM ( 2.1.4,2.1.5,.2.1.6,2.1.7 ) and now my sensor doesn t work. ( and for some other users )
I hope NAA is working on this probleme
But you can do that for now :
Open MiniCM 2.1.3 with winrar :
You need : libsensorservice.so ( system => lib ) and sensors.default.so ( system => lib => hw ); sensors.goldfish.so ( system => lib => hw )
Extract this 3 files .
Now, open the new MiniCM ( ex : 2.1.7 the lastest ) with winrar :
-go to system => lib; delete libsensorservice.so and add libsensorservice.so ( that s taken from MiniCM 2.1.3 )
-go to system => lib => hw; delete sensors.goldfish.so and sensors.robyn.so; and add sensors.default.so and sensors.goldfish.so ( that s taken from MiniCM 2.1.3 )
Now, flash your phone with the new MiniCM that is created, and your phone will use the compatibility driver, and your acceleromter must work
TESTED with my phone !
PS: This is my Modify version with compatibility driver
http://depositfiles.com/files/axqjrblfd
Don t forget, for a fresh install : ( you will lose all data )
Flash your phone with the last NAA kernel ( 09 )
Turn on your phone and go to recovery
Wipe data/factor reset
Wipe cache partition
=>advanced , Wipe dalvik cache
Install MiniCM ( modified )
Install gapps
If some people have same problem, and if my modified MiniCM works for other; I will upload the new MiniCM modified.
Just ask, and i will do
Original thread : http://forum.xda-developers.com/showthread.php?t=1456028
http://code.google.com/p/minicm/iss...Milestone Owner Summary&groupby=&sort=&id=347
Sorry for my bad English
Click to expand...
Click to collapse
Same for 2.1.9
It's going fine in my MiniPro with MiniCM7 2.1.9 and nAa kernel v11.
i have problem with the new sensor drivers too! They were working at the beginig but not now! I have the same problem with ics!
jccz said:
It's going fine in my MiniPro with MiniCM7 2.1.9 and nAa kernel v11.
Click to expand...
Click to collapse
Same here mini pro naa v11 minicm 2.1.9 all sensors working fine
Sent from my U20i using xda premium
stelios97, maybe you can ask to NAA if he can help us ( because your are a Recognized Developer ).
I ve already ask to NAA, but I m not sure he work on it ( because I m the only one who spoke about this problem )
Sorry for my bad English
Accelometer problem
Since minicm 2.1.3 I have the same problem too...Sensors don't respond at all...I had asked nAa but we couldn't find a solution and I thought I was the only one with this problem...
I have no sensors problems at all, sometimes just a little lag
I have that problem too. In alarmdroid, alarm can be stopped via flip or shake - I am used to that and now it doesn't work. App worked in original system, in SonyStyle but when I switched to this, it stopped working.
EDIT: Is there any way, how to use posted fix without system wipe? I just (friday) installed new rom, all apps, and then set them up properly - it took me some time and I don't have much of that right now. I don't really want to wipe again
Tested mine extensively...
1.What is your default cpu settings?
2. Do you have a screen off profile?
I am sorry, I just missed something in app - it works when alarm sounds, but it doesn't work in app, when I try to setup it. I have checked it via some sensor monitor and it works well.
I jumped to conclusion, because previously, it worked in that app even in setup mode and now I presumed, that it doesn't due to system changes.
GonziHere said:
I am sorry, I just missed something in app - it works when alarm sounds, but it doesn't work in app, when I try to setup it. I have checked it via some sensor monitor and it works well.
I jumped to conclusion, because previously, it worked in that app even in setup mode
Click to expand...
Click to collapse
I use Alarmdroid too (and MiniCM 2.2.0), and I have exactly the same issues: sensors don't work in app setup, but they do when an alarm sounds or when testing with other apps.
Sent from my E10i using XDA
I had this problem back in version 2.1.1... the sensors didn't work at all... I put it in the miniCM thread and n4a told me to do a full wipe, which I did, and now everything works like a charm ^^.
Sent from my E10i using xda premium
I have this problem since I flashed cm 10.. I then downgraded to cm7 but the problem persists. Here's the question : can I just replace the files that where posted on the first post without having to flash the rom again? So just replace the files...
Send from beneath my cloak of magic