Related
As a N1 user what I loved more than many other devices is that it has trackball wake and notifications colors for missed calls and sms (though thanks to Mod), do you think the main button under the screen of the SGS2 can do the same?
vegetaleb said:
As a N1 user what I loved more than many other devices is that it has trackball wake and notifications colors for missed calls and sms (though thanks to Mod), do you think the main button under the screen of the SGS2 can do the same?
Click to expand...
Click to collapse
Probably not. I think the main home button is like in the SGS. For SGS developers made a mod called BLN which uses the capacitive buttons on the sides of the main home button for notifications.
Who knows, guess we will have to wait and see what the great Devs can accomplish.
I think remaping the home button will be easy for XDA devs but use its light for notifications...will take another couple of hours to implement it
Would be nice to be able to see notifications. Although I am not to concerned, I am coming from a iPhone which doesn't have any methods of notifications aside from sound.
vegetaleb said:
As a N1 user what I loved more than many other devices is that it has trackball wake and notifications colors for missed calls and sms (though thanks to Mod), do you think the main button under the screen of the SGS2 can do the same?
Click to expand...
Click to collapse
vegetaleb said:
I think remaping the home button will be easy for XDA devs but use its light for notifications...will take another couple of hours to implement it
Click to expand...
Click to collapse
...yes it shouldn't take more than couple of hours from xda-devs to get the light out of black piece of plastic....
The homebutton of SGSII already works the same way as trackballwake on N1, no need for development on that one.
Axefield said:
...yes it shouldn't take more than couple of hours from xda-devs to get the light out of black piece of plastic....
Click to expand...
Click to collapse
The SGS's solution is probably the way to go. Light up the capacitive buttons with a custom kernel.
But I think I read somewhere that the SGS2 does that out of the box.
Edit: they say something here http://translate.google.com/transla...=http://www.mobiset.ru/articles/text/?id=5408
"And if they glowed in the precursor together with the backlit screen, but now the user can customize their work, there are several options."
It can mean anything, and who knows what google did with the translation. Sorry
They need the back lights to 'fade' in & out or 'pulse'. This gives such a high quality look to a device.
Sent from my GT-I9000 using XDA Premium App
KLoNe1 said:
They need the back lights to 'fade' in & out or 'pulse'. This gives such a high quality look to a device.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
This.
______________
tintol said:
...
Edit: they say something here http://translate.google.com/transla...=http://www.mobiset.ru/articles/text/?id=5408
"And if they glowed in the precursor together with the backlit screen, but now the user can customize their work, there are several options."
It can mean anything, and who knows what google did with the translation. Sorry
Click to expand...
Click to collapse
Here is human translation:
And while in the previous model they [buttons] lit up only with the screen backlight, now the user can define how and when the buttons light up from a number of available settings.
Is there a way to have the 3 hardware "buttons" stay on anytime the backlight is on? I switch between devices often and it can be a pain to remember which button is which at night.
This question comes up often. Please do a search.
Download Adjbrightness (free, need root) from market.
it has options to force soft buttons on or off
Hope it helps
Sent from my Dell Streak using Tapatalk
asianftw said:
Download Adjbrightness (free, need root) from market.
it has options to force soft buttons on or off
Hope it helps
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
This seems to allow a full range of screen brightness adjustment but doesn't seem to offer any option to keep the buttons turned on when the screen is on.
bigddybn said:
This seems to allow a full range of screen brightness adjustment but doesn't seem to offer any option to keep the buttons turned on when the screen is on.
Click to expand...
Click to collapse
Have you try AdjBrightness -> Menu -> Option -> Lock on Button lights ?
asianftw said:
Have you try AdjBrightness -> Menu -> Option -> Lock on Button lights ?
Click to expand...
Click to collapse
Yeah unfortunately that seems to do a whole lot of nothing.
bigddybn said:
Yeah unfortunately that seems to do a whole lot of nothing.
Click to expand...
Click to collapse
sorry to hear that.
I am on streakdroid 1.9 and when i have that option checked + setting the brightness in that app, the buttons do stay on for me
Anyone else have an idea? I flashed streakdroid 1.9 just to see if the above suggestion worked. Still no go.
alperin1 said:
This question comes up often. Please do a search.
Click to expand...
Click to collapse
Quit quibbling about that... what is a forum for?
I run a Corvette forum and don't jump someone for asking the same questions, especially new members. After awhile the new members figure out how to search...
You also must press the set button.
Sent from my Dell Streak using XDA Premium App
pawdog said:
You also must press the set button.
Sent from my Dell Streak using XDA Premium App
Click to expand...
Click to collapse
Still no go. Used both the brightness and the timeout set buttons. Button backlight only stays on for about 5 seconds.
same here.....
At first I didn't like the light not staying on either, however after about a week, it was pretty easy to remember which the 3 buttons are and where... even in the dark. Now I don't mind at all.
Tip... touch lightly anywhere on that side and it lights up.
william58 said:
At first I didn't like the light not staying on either, however after about a week, it was pretty easy to remember which the 3 buttons are and where... even in the dark. Now I don't mind at all.
Tip... touch lightly anywhere on that side and it lights up.
Click to expand...
Click to collapse
Thanks but that doesn't help at all.
bigddybn said:
Thanks but that doesn't help at all.
Click to expand...
Click to collapse
So your saying you can't remember where the three buttons are on your phone then?
william58 said:
So your saying you can't remember where the three buttons are on your phone then?
Click to expand...
Click to collapse
No I'm saying your post was useless and didn't help answer the question as is this one.
hi everyone one of the major problem is with xperia s i the capasitive keys arent very responsive sometimes have to press twice,and more.
is there actually a way to improve is it rom or kernel related can it be fixed by kernel tweaks. i know many of you say will get used to it its just pain in neck
Don't press, swipe!!!
Mano1982 said:
Don't press, swipe!!!
Click to expand...
Click to collapse
was xperia s design that way not pressing!
Mano1982 said:
Don't press, swipe!!!
Click to expand...
Click to collapse
Thank you very much. I couldn't have figured it out :-D
Sent from my LT26i using xda premium
what a nonsense! swipe well how do you get to recent apps by swiping! you meant to long press. my question was any solution as (kernel) not to workaround it. it was never designed to work swipe it was designed to work by press, and it does not!
I removed the screen protector and it did improve the touch sensitivity considerably.
defsix said:
I removed the screen protector and it did improve the touch sensitivity considerably.
Click to expand...
Click to collapse
does it really?
I think so, I did the same with my Arc and Tablet S . Improved response and not so much a dust magnet
cihanleanne said:
what a nonsense! swipe well how do you get to recent apps by swiping! you meant to long press. my question was any solution as (kernel) not to workaround it. it was never designed to work swipe it was designed to work by press, and it does not!
Click to expand...
Click to collapse
Swipe actually works fine for the recent apps. Just stop on the dot and wait.
Personally, I find the swipe motion easier then aiming for the silly dot. Never had issues since starting to swipe rather than press. But that's just me.
For me it works when pressing above the dots, not directly at the dots (about halfway from the dots to the display).
Also, I can press anywhere near the dots when using the whole thumb instead of only a fingertip.
so what you saying we cant increase sensivity with kernel
cihanleanne said:
so what you saying we cant increase sensivity with kernel
Click to expand...
Click to collapse
This is typically a hardware restriction. No software changes could possibly enhance the touch sensitivity. These dots weren't made like other Androids' capacitive buttons.
Correct me if I'm wrong though, but to me it doesn't seem possible
Hermantje said:
This is typically a hardware restriction. No software changes could possibly enhance the touch sensitivity. These dots weren't made like other Androids' capacitive buttons.
Correct me if I'm wrong though, but to me it doesn't seem possible
Click to expand...
Click to collapse
you right thanks
Hi.
I am writing this to ask a small favor. I am working on an Xposed Module called Xposed Additions, and several users of SGS4 and Note3 has issues with Haptic Feedback as their Back and Menu button is not being registered as Capacitive. In the original Android source, these are identified by checking the PolicyFlags for WindowManagerPolicy.FLAG_VIRTUAL, however this flag does not seam to be set for these two devices when using the TouchWiz ROM's. Instead I tried checking the KeyEvent flag for KeyEvent.FLAG_VIRTUAL_HARD_KEY. But this identified all buttons as virtual, including power and volume.
These two devices using the TouchWiz ROM seams to be the only once affected by this. Even TouchWiz on other devices like SGS3 works the way it should, using both ways of checking key type for Capacitive.
Since some devices has pure hardware buttons, I cannot just hard code Haptic Feedback on Back and Menu. I need some other way to identify these two buttons on those devices, but since I don't have one, I cannot play around with the different event flags. Does anyone know how I can go about this?
Also, if someone has some idea as to where this bug might be, I really would like to know. KeyEvent.FLAG_VIRTUAL_HARD_KEY is part of the standard application API, so that one should have worked as expected as it will otherwise break any regular application that depends on it, which means that it has to be a bug.
dk_zero-cool said:
Hi.
I am writing this to ask a small favor. I am working on an Xposed Module called Xposed Additions, and several users of SGS4 and Note3 has issues with Haptic Feedback as their Back and Menu button is not being registered as Capacitive. In the original Android source, these are identified by checking the PolicyFlags for WindowManagerPolicy.FLAG_VIRTUAL, however this flag does not seam to be set for these two devices when using the TouchWiz ROM's. Instead I tried checking the KeyEvent flag for KeyEvent.FLAG_VIRTUAL_HARD_KEY. But this identified all buttons as virtual, including power and volume.
These two devices using the TouchWiz ROM seams to be the only once affected by this. Even TouchWiz on other devices like SGS3 works the way it should, using both ways of checking key type for Capacitive.
Since some devices has pure hardware buttons, I cannot just hard code Haptic Feedback on Back and Menu. I need some other way to identify these two buttons on those devices, but since I don't have one, I cannot play around with the different event flags. Does anyone know how I can go about this?
Also, if someone has some idea as to where this bug might be, I really would like to know. KeyEvent.FLAG_VIRTUAL_HARD_KEY is part of the standard application API, so that one should have worked as expected as it will otherwise break any regular application that depends on it, which means that it has to be a bug.
Click to expand...
Click to collapse
What exactly is your end goal? Are you looking to override the haptic feedback intensity or?
elesbb said:
What exactly is your end goal? Are you looking to override the haptic feedback intensity or?
Click to expand...
Click to collapse
No, I use XposedBridge to hook PhoneWindowManager.interceptKeyBeforeQueueing(). From here I add custom actions on enabled and configured key codes. at the same time, I make sure to invoke Haptic Feedback the same way done in the original source using the original method.
In the original source and in mine, is looks like this
Code:
if ((policyFlags & FLAG_VIRTUAL) != 0) {
// Perform feedback, but SGS4 and Note3 never get's here
}
Those two devices never get's past the check.
dk_zero-cool said:
No, I use XposedBridge to hook PhoneWindowManager.interceptKeyBeforeQueueing(). From here I add custom actions on enabled and configured key codes. at the same time, I make sure to invoke Haptic Feedback the same way done in the original source using the original method.
In the original source and in mine, is looks like this
Code:
if ((policyFlags & FLAG_VIRTUAL) != 0) {
// Perform feedback, but SGS4 and Note3 never get's here
}
Those two devices never get's past the check.
Click to expand...
Click to collapse
So you are saying, the back and menu keys never get detected in the method interceptKeyBeforeQueueing()? I do know that in my own apps running on my S4 i am able to detect what keys are pressed by KeyEvent.KEYCODE_BACK || KeyEvent.KEYCODE_MENU. I don't know if it matters or not if the key is virtual. So in your case it would be something like:
if(keyCode == KeyEvent.KEYCODE_BACK) {
//Do your custom action here, and call the default performHapticFeedback() method
elesbb said:
So you are saying, the back and menu keys never get detected in the method interceptKeyBeforeQueueing()? I do know that in my own apps running on my S4 i am able to detect what keys are pressed by KeyEvent.KEYCODE_BACK || KeyEvent.KEYCODE_MENU. I don't know if it matters or not if the key is virtual. So in your case it would be something like:
if(keyCode == KeyEvent.KEYCODE_BACK) {
//Do your custom action here, and call the default performHapticFeedback() method
Click to expand...
Click to collapse
No, they are detected fine. I am just not able to detect that they are Capacitive as they get registered as Hardware Buttons. And using KeyEvent.KEYCODE_BACK will not help, because some devices do have real hardware Back buttons, and those should not get Haptic Feedback on key presses.
dk_zero-cool said:
No, they are detected fine. I am just not able to detect that they are Capacitive as they get registered as Hardware Buttons. And using KeyEvent.KEYCODE_BACK will not help, because some devices do have real hardware Back buttons, and those should not get Haptic Feedback on key presses.
Click to expand...
Click to collapse
I finally understand what you are saying lol. I was lost at first but tried to help and figured and i understand what you are having issues with. Let me look at the source (smali) code i have and i will try to help more. You want haptic feedback on only capacitive buttons but not hardware buttons. Correct? I think i got it. Thanks!
elesbb said:
I finally understand what you are saying lol. I was lost at first but tried to help and figured and i understand what you are having issues with. Let me look at the source (smali) code i have and i will try to help more. You want haptic feedback on only capacitive buttons but not hardware buttons. Correct? I think i got it. Thanks!
Click to expand...
Click to collapse
That is it yes
This is how it is done originally, but that does not work on the SGS4, because it never get's pased the check.
dk_zero-cool said:
That is it yes
This is how it is done originally, but that does not work on the SGS4, because it never get's pased the check.
Click to expand...
Click to collapse
So, i looked at my ROM's (4.2.2) PhoneWindowManager.smali, and its totally different than CMs. Thats prolly why its not working.. there is a method KeyEvent.getFlags() have you tried seeing the result of that? I'm not sure what flags are passed to it but it might hold the necessary info for determining if its a virtual key or not. As of the source code in TouchWiz, there doesn't seem to be an actual condition of determining if the button is virtual or not, this may be due to it being hard coded by the system.
What you could do, is create a special conditional statement for the TouchWiz ROMs. Easiest way to do that would be to have the user tell your xposed module that it is a touchwiz ROM, then check that in the interceptKeyBeforeQueuing method of your xposed module, and if its a back or menu key via KeyEvent.KEYCODE_BACK and KeyEvent.KEYCODE_MENU then perform the custom action and perform the haptic feedback.
---------- Post added at 01:06 AM ---------- Previous post was at 01:00 AM ----------
Just checked KeyEvent flags and there is a KeyEvent.FLAG_VIRTUAL_HARD_KEY so in KeyEvent.getFlags() it might have that flag. So this might work:
interceptKeyBeforeQueuing(KeyEvent event) {
if(event.getFlags() == KeyEvent.FLAG_VIRTUAL_HARD_KEY) {
//This is a virutal key
}
elesbb said:
What you could do, is create a special conditional statement for the TouchWiz ROMs. Easiest way to do that would be to have the user tell your xposed module that it is a touchwiz ROM, then check that in the interceptKeyBeforeQueuing method of your xposed module, and if its a back or menu key via KeyEvent.KEYCODE_BACK and KeyEvent.KEYCODE_MENU then perform the custom action and perform the haptic feedback.
Click to expand...
Click to collapse
It seams to be the kernel that has issues. Got confirmation about the same issue on the Play Store SGS4 which does not have TouchWiz. So I would have to identify the Device Board and make special case there.
elesbb said:
Just checked KeyEvent flags and there is a KeyEvent.FLAG_VIRTUAL_HARD_KEY so in KeyEvent.getFlags() it might have that flag. So this might work
Click to expand...
Click to collapse
That I already did try. The FLAG_VIRTUAL_HARD_KEY flag is set for all buttons, including Hardware like Power and Volume. Like I said, there is something really strange going on with those two devices.
dk_zero-cool said:
It seams to be the kernel that has issues. Got confirmation about the same issue on the Play Store SGS4 which does not have TouchWiz. So I would have to identify the Device Board and make special case there.
That I already did try. The FLAG_VIRTUAL_HARD_KEY flag is set for all buttons, including Hardware like Power and Volume. Like I said, there is something really strange going on with those two devices.
Click to expand...
Click to collapse
The S4 prolly has the buttons hard coded in the PhoneWIndowManager since Cyanogenmod is cross device compatible they have their own methods in them.
And your surprised all keys hold that flag? Come on this is Samsung we are talking about a lot of things are strange xD lol Anyhow, that might be your best bet, get the device version either the mainboard or some other method, then make a conditional statement based off that and the keycode for which buttons are pressed.
If you need any help let me know! I have the smali code from my 4.2.2 TW ROM so i can easily look at things for ya if you'd like!
elesbb said:
And your surprised all keys hold that flag? Come on this is Samsung we are talking about a lot of things are strange xD lol Anyhow, that might be your best bet, get the device version either the mainboard or some other method, then make a conditional statement based off that and the keycode for which buttons are pressed.
Click to expand...
Click to collapse
Not really, I have had my share of Samsung (Still do, SGS3), so I am used to it by now. Especially kernel issues. Samsug properly has the worlds dumbest kernel devs working for them. And it is tipical them to just make a fast hard code instead of fixing the actual solution and make it work as intended. The worst part is that KeyEvent.getFlags() is in the Application API, so this will also break normal apps that use it.
elesbb said:
If you need any help let me know! I have the smali code from my 4.2.2 TW ROM so i can easily look at things for ya if you'd like!
Click to expand...
Click to collapse
You have been a really big help, but there one more thing if you don't mind. Samsung has Sound Feedback? Is this just triggered when doing Haptic Feedback, or is there a specific method used for this in that intercept query method?
dk_zero-cool said:
Not really, I have had my share of Samsung (Still do, SGS3), so I am used to it by now. Especially kernel issues. Samsug properly has the worlds dumbest kernel devs working for them. And it is tipical them to just make a fast hard code instead of fixing the actual solution and make it work as intended. The worst part is that KeyEvent.getFlags() is in the Application API, so this will also break normal apps that use it.
You have been a really big help, but there one more thing if you don't mind. Samsung has Sound Feedback? Is this just triggered when doing Haptic Feedback, or is there a specific method used for this in that intercept query method?
Click to expand...
Click to collapse
It might be the same method the haptic feedback is. I'm not sure 100 percent but sadly I have work today. So I will have to check when I get home, which I can't wait for already xD
Sent from my SGH-M919 using Tapatalk
@dk_zero-cool have you been able to solve the issue? I saw on Xposed Additions Changelog, but still no haptic feedback on back and menu press...
yurividal said:
@dk_zero-cool have you been able to solve the issue? I saw on Xposed Additions Changelog, but still no haptic feedback on back and menu press...
Click to expand...
Click to collapse
Not yet. But I did manage to find a Samsung Released ROM for my SGS3 with the same issue. Have not yet had time to try it, but I will start looking at that some time after Christmas. It does make it easier when I can test it on my own device while working on it.
dk_zero-cool said:
Not yet. But I did manage to find a Samsung Released ROM for my SGS3 with the same issue. Have not yet had time to try it, but I will start looking at that some time after Christmas. It does make it easier when I can test it on my own device while working on it.
Click to expand...
Click to collapse
Nice! hope you can figure that out. Keep up the owesome work! Thanks once again, and enjoy your christmas!
Hi team,
Do y'all know if there's a way to disable using Power+vol down for screenshot? My gallery is filled with accidental screenshots because of this shortcut, and the knock knock one works perfectly well.
Thanks.
Lol, not sure but I do this at least once a day too!!
Sent from my LYA-L29 using Tapatalk
Maybe button mapper might work?
Darkat70 said:
Maybe button mapper might work?
Click to expand...
Click to collapse
Thanks for the advice. Doesn't look like it though. Also can't map Power button with it.
I have eleventy trillion accidental screenshots and they are from touching my screen in some way.
I actually asked Huawei support about this as I used to take a bunch of accidental screenshots at first. They confirmed this can't be disabled right now.
That said, I've had the device for a few weeks now and only take accidental screenshots 1-2 times a week now instead of like 5 times a day.
Hopefully they add the option in a future FW update.
and there was me thinking this was a default Android rather than Huawei specific keyboard combo ;o)
Any solution guys....?
May I know why are you guys using that combination in the first place if you don't want to take a screenshot?
anu3682 said:
May I know why are you guys using that combination in the first place if you don't want to take a screenshot?
Click to expand...
Click to collapse
Because it's very easy to hit both buttons simultaneously, as they are next to each other.