Is the function of slide2unlock possible on our device? (slide2unlock is when the screen is off and you slide your finger on the capacitive buttons to wake it up)
I know its a One X function but my brother managed to put it on his Sensation (with custom ROM).
Do we just need a dev to create it or its not possible at all?
also known as Sweep2Wake
http://www.youtube.com/watch?v=SgQ22IuCcKw
That is an awesome function.I have seen a video。 It was run in HTC Sensation（ sense 3.6.）。This function need to modify kernel,but there are some issue in current kernel。（ the headphone button）I think developers will fix kernel issue first,and then they will add this function to their kernels or roms
Related
After some water exposal, bottom hardware buttons (along with optical trackball) refused to work.
I have fixed them with some precise inside cleaning, but the optical function (not the button himself) continues malfunctioning, which is not a big deal for me, but..
The exact problem: i spotted in dark environment, that the sensor inside continuously glimmers in all modes - scren-off, scren-on (without puting finger over him), etc.. In return, my battery drains extra aprox. 10-12 mA!
I have observed, that in healthy device, sessor glimms only when interacting with him..
Is there a chance to disable this sensor to avoid this? I hope in software manner
I don't think there is anything out there that will disable the optical pad. You could give HTC a call or your carrier and see what they say.
There is this thread on the forums about turning off the backlights.
Should work for trackball as well? Probably. Something about LED Hack on the first or second page. Seems to be something on the 3rd page as well.
Go have a read over here (I just skimmed. its 2am lol) http://forum.xda-developers.com/showthread.php?t=704977
@formformer
If you tell me your kernel version I will try to build a kernel without trackpad support!?
@Meaple 's post was sadly adequate and rips best hope in me ;( ..
@eden2812 I have using 2 led hacks from previous attempts to minimize energy consumption & eye comfort, and they shurely don't do the "trackpad sensor shutting" job..
@AndroidJaspie
it's so damn cool to offer this kind of experience. salute!
i have likely using latest Ginger Villain's compilation, but any recent rom-kernel set, with weak appetite fits my best.
i will be very patient to hear from you..
my current setup is:
OK I built a new kernel from the cyanogenmod sources now without trackball support. I tested it with GingerVillain 1.4 and it worked.
please make a backup and then give the update.zip a try.
Tell me if the new kernel solved your problem or not.
Jasper
Yes Jasper, obviously the sensor is shutted (no glimmering observes) and the xtra drain is all gone now!! I'm so pleased.
But i have found, that the bottom buttons (including the button under the optical trackpad) not waking the phone any more. Is this issue related?
And another, not so important question: Would be this kernel compliant with other Gingerbread releases? or.. could you give me some hint, if is possible to transform your "surgery" into a some kind of a patch, that will give me opportunity to enjoy any feature kernel/roms?
Again, BIG 10x for your respond in this custom problem so far! You make my life happier
karel
No problem i like it to work with things like that. So it's a good chance to improve my knowledge about linux and help other people at the same time.
Are you talking about the all buttons or only about the button around the optical sensor?
If you are talking about the one around the sensor then it's normal that it won't wake up the phone any more. But the others(home, menu, back and search) should work like before.
This kernel works only with cyanogenmod and GingerVillain. On other rom's like Oxygen it doesn't work. But you i can compile you the kernel you want.
At the moment it's only possible to disable the trackball only by editing the kernel configuration. But i will try to get it working without changing the kernel so that you can use every kernel you want.
Jasper
i told so, about the relation of shutted sensor and not working buton.., but yes, others buttons also not working in lockscreen-off mode, where they should or at least worked before. (volume butts still works for wakening..)
ps. a have barely no linux skills, but its interesting for me either!
and if editing & compiling is not so high level task, im going to try first steps right now!
Any way, disabling track sensor without editing kernel settings sounds like a dream..
k
hi, my fried
could you tell me, where in the config I can find the exact setting and how to change it?
hi
if you got the kernel source you can make menuconfig to configure the new kernel. To disable the trackball go to "Device Drivers" --> "Input device support" --> "Opticaljoystick". To disable the joystick press "n" to enable it press "y"
Don't know how to comile your own kernel?
here is a useful links that helped me, too:
-[HOW-TO] Build your own kernel package from source
huh.. 10x 4 the guides, they light me enough to get started week ago, but i get stuck just in the beginning (problems with MBR or something..). and at this moment i have absolute lack of time to deal with this interesting stuff. However.. can i have one more last ask from you: to compile for me an updated kernel.. (they says he has the ability to record 2way call conversations..)
Using the Ginger Villain rom, suppose with this richardtrip kernel. Guess CM will worx too..
Thanks anyway!
ok
a bit late but here it is
a new kernel version 2.6.37.2 from the richardtrip-sources.
kernel features:
-disabled trackball
I don't know anything about "Two-way call recording kernel support" but i will try to find out as much as posible to configure a kernel with it.
jasper
Hi AndroidJaspie, i've the same problem with the optical trackball of my desire. I use the miui rom with the kernel 2.6.37.6-cyanogenmod-g8913be8. Can i use the kernel in your last post? thx bye
Please use the Q&A Forum for questions Thanks
Moving to Q&A
While fiddling around with the multitouch issue in games, i've found out what causes the loss of touch events upon releasing one finger.
A calibration code included in synaptics 3k driver that one x tegra3 is using, causes a reset of the touch screen states when one finger is released in a multitouch combo.
Removing the calibration define in the driver seems to have no negative side effects, and fixes the reset issue in the drriver.
Here's the commit related;
https://github.com/TeamNDVRu/htc-kernel-endeavoru/commit/08d512328aaa898d92190fbb85b7df1382ca29ec
Kernel devs, please test, and try to include this if you think it's appropriate, so users can enjoy a fully working touchscreen with all of the kernels, in combination of aosp derivation roms as well.
Included in IceColdJelly
waiting for feedback
thanks!
I know it sounds weird, and I certainly can't explain it, but the way I got around it was going into the system/lib/modules folder, copying a file (any) then deleting it. All of a sudden touch operated normally again. (until reboot). I'd start a game realise there's no multi touch, and carry out the above weirdness, and hey ho, it worked.
Spooky. But true. Done it over fifty times.
Thanks for the proper fix by the way!
tbalden said:
While fiddling around with the multitouch issue in games, i've found out what causes the loss of touch events upon releasing one finger.
A calibration code included in synaptics 3k driver that one x tegra3 is using, causes a reset of the touch screen states when one finger is released in a multitouch combo.
Removing the calibration define in the driver seems to have no negative side effects, and fixes the reset issue in the drriver.
Here's the commit related;
https://github.com/TeamNDVRu/htc-kernel-endeavoru/commit/08d512328aaa898d92190fbb85b7df1382ca29ec
Kernel devs, please test, and try to include this if you think it's appropriate, so users can enjoy a fully working touchscreen with all of the kernels, in combination of aosp derivation roms as well.
Click to expand...
Click to collapse
Will this be incorporated into your CyanogenMod 9 ROM? Thanks
Sent from my HTC One X using xda premium
theDroidfanatic said:
Will this be incorporated into your CyanogenMod 9 ROM? Thanks
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
yes, that's planned of course!
tbalden said:
yes, that's planned of course!
Click to expand...
Click to collapse
running fine in icecold jelly
thanks
tbalden said:
While fiddling around with the multitouch issue in games, i've found out what causes the loss of touch events upon releasing one finger.
A calibration code included in synaptics 3k driver that one x tegra3 is using, causes a reset of the touch screen states when one finger is released in a multitouch combo.
Removing the calibration define in the driver seems to have no negative side effects, and fixes the reset issue in the drriver.
Here's the commit related;
https://github.com/TeamNDVRu/htc-kernel-endeavoru/commit/08d512328aaa898d92190fbb85b7df1382ca29ec
Kernel devs, please test, and try to include this if you think it's appropriate, so users can enjoy a fully working touchscreen with all of the kernels, in combination of aosp derivation roms as well.
Click to expand...
Click to collapse
will add commit to my kernel and report back. thanks for all your work. really appreciate it
Totally PRO! I knew you guys could do it
tbalden said:
yes, that's planned of course!
Click to expand...
Click to collapse
WooHoo!
Sent from my HTC One X using xda premium
Gonna add this to my future AoSP JB rom thanks tbalden
Team Fire
Hey,man.The work will be started again.The issue appeares again!
JohnYang1997 said:
Hey,man.The work will be started again.The issue appeares again!
Click to expand...
Click to collapse
Yep, i think it's normal: devs are using a fresh source that needs to be patched, most probably because AOSP roms and sense roms are using different libraries.
In case anyone needs it, this Multi touch fix was incorporated into the CM9 kernel, found here: http://d-h.st/ass
EDIT: nvm, its removed
Sent from my One X running Blade v4.7.0. At a mere 217 MB, with tons of AROMA Mods and tweaks, this, is what you want.
All I want to say is http://forum.xda-developers.com/showthread.php?t=2136731 this kernel has already fixed this earlly today(here +8.00)
Thanks will try later
Sent from my HTC One X using Tapatalk 2
tbalden said:
While fiddling around with the multitouch issue in games, i've found out what causes the loss of touch events upon releasing one finger.
A calibration code included in synaptics 3k driver that one x tegra3 is using, causes a reset of the touch screen states when one finger is released in a multitouch combo.
Removing the calibration define in the driver seems to have no negative side effects, and fixes the reset issue in the drriver.
Here's the commit related;
https://github.com/TeamNDVRu/htc-kernel-endeavoru/commit/08d512328aaa898d92190fbb85b7df1382ca29ec
Kernel devs, please test, and try to include this if you think it's appropriate, so users can enjoy a fully working touchscreen with all of the kernels, in combination of aosp derivation roms as well.
Click to expand...
Click to collapse
Just to mention it here:
It seems thatt removing the calibration by default can lead to the
"touchscreen not responsing after wakeup" issue.
This is very random but has been reported on both sense and AOSP
A possible solution is to make calibration control switchable in user-space
using a sysfs. Default is to enable it it and if problems with multi-touch
are experienced to let the user disable it "on demand"
see here for the impl
https://github.com/maxwen/enrc2b-kernel-BLADE/commit/deb62c8e4aa893030abc6a3e546092c9bb61cd74
Code:
echo 0 > /sys/android_touch/calibration_control
I’m wondering if there is a tool or a mod that I can use to change how the notification LED lights up, specifically to increase the blink rate or increase the switched on time of a blink cycle. The tiny LED buried inside the ear piece grill and the way it blinks makes noticing missed alerts almost impossible unless you look at it very carefully. Ideally I would like for it to blink rapidly or the have the LED lit up for a little longer in each blink cycle, I know this can affect the battery, so it would be nice if the behavior can be customized further i.e Have intensive blinking for the first 30 minutes and then fall back to the regular conservative mode to save battery.
A better alternative would be to use the capacitive buttons (back, home, menu) without turning the screen on. My previous Galaxy S1 had a mod which could do that, wondering if there is something similar for One X. If those buttons can be selectively turned on then I guess that would be more prominent than that tiny green LED.
Flash CM10.1 or ICJ to get button light notification.
Sent from my One X using xda premium
Latest XM kernels also include BLN (backlight notification). It's fully cofigurable, including the light level. :good:
Plus, it has all the governor tweaks you can think of.
I Don't know if there's a standalone tool for this
but I use CM 10.1 ROM that comes with this tool included
anyway the control is limited to 2 colors (red and green) and 2 speeds , or you can use it to disable the whole light
and still be able to use hardware keys backlight as a notification light
Thanks for the replies. :good:
Currently I’m on Viper X custom ROM. Last year I installed CM10 but wasn't impressed with battery life or camera performance.
[email protected]|-|oR said:
Latest XM kernels also include BLN (backlight notification). It's fully cofigurable, including the light level. :good:
Plus, it has all the governor tweaks you can think of.
Click to expand...
Click to collapse
Interesting, perhaps I'll try that, seems XM supports Sense ROMs and I found few posts where people have managed to get it working with Viper X. I'm guessing if I managed to get XM kernel working, all I have to do is use BLN app from market ?
Maher88 said:
I Don't know if there's a standalone tool for this
Click to expand...
Click to collapse
i think there is a tool for this: light flow app.
i haven't tried it on my hox yet, but i had limited success with it on my desire. htcs are notorious for terrible led notification control and configuration, i think. on my huawei ideos i had it configured exactly how i wanted it, but this is probably impossible on an htc ... actually i found this thread when searching for a solution how to manage my own led problems. but according to the discussion here there is no solution .
PhoenixFx said:
Thanks for the replies. :good:
Currently I’m on Viper X custom ROM. Last year I installed CM10 but wasn't impressed with battery life or camera performance.
Interesting, perhaps I'll try that, seems XM supports Sense ROMs and I found few posts where people have managed to get it working with Viper X. I'm guessing if I managed to get XM kernel working, all I have to do is use BLN app from market ?
Click to expand...
Click to collapse
viper x works well with xm kernel without a repack, and bln works without any app, just enable it as instructed by xm
Hi Devs, I would like to ask you if it's possible to implement on official 4.3/4.4.2 dt2w or s2w feature. At this time we only have 4.3 kernel sources, but we will get also 4.4.2. Is this possible? If it is, then is really difficult to make it work ? I love this feature on g2/nexus 5/htc one/one s and I would like to have it. Maybe someone is able to do that grabbing the code from kernels that have these features, or at least tell me if it's possible, then I will try (without a good knowledge). Thanks guys.
High everybody
Is there any replacement to Huawei stock roms automatic power on/off features for custom roms because all apps I found only automatic power off only and no app have power on ?
Come on guys no one have any answer to that question?
I think that is very difficult because must have a specific hardware such as microprocessor... if it were so easy to do, you would apply in all smartphones.. I think blackberry had that function and some old motorolas...
This phone have this function on original stock rom but not exist in custom roms or any application.