Does the official ICS update have on screen buttons, back , home, etc
or use the device buttons?
SonicTab said:
Does the official ICS update have on screen buttons, back , home, etc
or use the device buttons?
Click to expand...
Click to collapse
It uses the device buttons. I believe its just the Galaxy Nexus that uses the on screen buttons. Once some custom roms come out based on official ICS update, you can flash the on-screen button. I flashed it on LPH a while ago and had the on-screen buttons if thats what you want. But it feels like you have less screen space since you have device buttons as well as on-screen using that mod.
But to answer your question, the SGS ICS uses device buttons on official build
Thanks for the reply.
Rather use the device buttons and have full screen display.
Glad to hear its possible,
read somewhere ICS allowed on screen buttons only, glad that is not the case.
just got my rezound(came from thunderbolt) a few days ago and so far so good...using the clean rom....i am missing my cyanogen rom though....my question is this how can such an awesome phone not have a fully functional cyanogen rom? i don't care if its official or not but from what i can find there is no daily drivers for this...anyone know why?
cm9 is being worked on, we need to get RIL working. cm7 won't happen as the devs don't see the need for anymore GB based roms.
i see...the main thing i miss is the force close by long pressing the back button
DreamFX said:
i see...the main thing i miss is the force close by long pressing the back button
Click to expand...
Click to collapse
I feel ya, you could download one of the senseless roms out there, they provide a almost aosp experience and the leedroid tweaks included are really usefull
DreamFX said:
i see...the main thing i miss is the force close by long pressing the back button
Click to expand...
Click to collapse
Why force quit apps?
Android is evolved enough to close items itself if neesed. Or if on ICS you can hold HOME till your apps show up and flick them away to remove them from memory.
I miss long press force close as well. It was very useful when an app was misbehaving. Simply long press the back button instead of going to application settings and force closing.
Sent from my ADR6425LVW using XDA
Missing the Thunderbolt and CM7
DreamFX said:
just got my rezound(came from thunderbolt) a few days ago and so far so good...using the clean rom....i am missing my cyanogen rom though....my question is this how can such an awesome phone not have a fully functional cyanogen rom? i don't care if its official or not but from what i can find there is no daily drivers for this...anyone know why?
Click to expand...
Click to collapse
I almost went back to the Thunderbolt from the Rezound because of this. Hanging on hoping that s-off happens and kernel source are released to see where things go from there.
The Rezound is much better hardware (screen! and proc.) but the Thunderbolt was CM heaven.
I got my s3 this evening..I had following questions regarding the phone-
How do I share Pc's internet with my samsung galaxy S3??
How does the smart stay work??
Is there a way to install apps directly from PC to the phone??
Can the unlock screen be activated using the volume button or the home button..
1. If you want to use your PC's internet for your phone, try looking up reverse tethering. I didn't try it out for myself so I can't say for sure but it's for rooted phones only and I don't know if it works for the GS3.... yet. But I'm sure a nice developer would make one, especially since the phone is so popular.
2. Smart stay basically keeps the phone's screen on past the screen timeout time as long as the front facing camera is looking >directly< at your face.
3. You can unlock the screen with the home button and the power button but not with the volume buttons
dakaringer said:
1. If you want to use your PC's internet for your phone, try looking up reverse tethering. I didn't try it out for myself so I can't say for sure but it's for rooted phones only and I don't know if it works for the GS3.... yet. But I'm sure a nice developer would make one, especially since the phone is so popular.
2. Smart stay basically keeps the phone's screen on past the screen timeout time as long as the front facing camera is looking >directly< at your face.
3. You can unlock the screen with the home button and the power button but not with the volume buttons
Click to expand...
Click to collapse
Thanks are you sure we cannot use internet via usb??Coz I used the same feature with my HTC one X..
And doesn't smart stay lock the phone when ur face is away??
Steve Stiffler said:
Thanks are you sure we cannot use internet via usb??Coz I used the same feature with my HTC one X..
And doesn't smart stay lock the phone when ur face is away??
Click to expand...
Click to collapse
I think you're referring to a Sense standard feature called Internet Pass Through of the HTC One X. Which is only for HTC Sense interfaces. So I'm pretty sure there isn't a built in reverse tethering feature in GS3.
No. Smart stay only prevents the phone from locking as long as you look at the screen. It does not lock by itself as soon as you look away. That would be really annoying.
dakaringer said:
I think you're referring to a Sense standard feature called Internet Pass Through of the HTC One X. Which is only for HTC Sense interfaces. So I'm pretty sure there isn't a built in reverse tethering feature in GS3.
No. Smart stay only prevents the phone from locking as long as you look at the screen. It does not lock by itself as soon as you look away. That would be really annoying.
Click to expand...
Click to collapse
Darn I thought it was Ice Cream sandwich standard feature..ANyways..
And does Smart stay work with every application or specific ones??
can the phone be rooted and unrooted easily or once you root it is just adios to your warranty??
Steve Stiffler said:
Darn I thought it was Ice Cream sandwich standard feature..ANyways..
And does Smart stay work with every application or specific ones??
can the phone be rooted and unrooted easily or once you root it is just adios to your warranty??
Click to expand...
Click to collapse
It should work with every applications since I just tested it with angry birds space .
Rooting is sooo easy thanks to Chainfire! It took me like a minute to root from start to finish.
It is also possible to unroot and reset the flash counter to keep your warranty.
Read all about it here.
http://forum.xda-developers.com/showthread.php?t=1695238
Greetings my fellow XDA experts,
I have a Galaxy S2 (i9100) International version on the NeatROM 4.8 ( XXLSW). What has happened is that my Softkeys are dead and unresponsive.
There is no illumination and response from them. So I have a phone without the menu and back buttons, which implies that I have a f**ked up iPhone like phone with just one Home button to function with.
I took the phone to the service center and they said it's a single piece with the display so the entire display would need to be replaced which is unreasonable and needless since the display works absolutely perfect.
So I was thinking of a remedy in terms of the ROM I use with the phone. Is there any custom ROM available for the S2 which would enable me to use a part of the display as the MENU and BACK buttons itself ? Like the Nexus 4 has ? I don't mind losing out on screen space to enable me to get those buttons back.
Please do suggest me any such ROM's or methods through which I can use the phone without having to change a fully functional touchscreen display. Spending so much just to get the Soft key functionality back is plain ridiculous and a pure manufacturing drawback from Samsung. Yuck
Anyways, please do help with any pointers.
Thanks and Cheers !
HellRazorGod said:
Greetings my fellow XDA experts,
I have a Galaxy S2 (i9100) International version on the NeatROM 4.8 ( XXLSW). What has happened is that my Softkeys are dead and unresponsive.
There is no illumination and response from them. So I have a phone without the menu and back buttons, which implies that I have a f**ked up iPhone like phone with just one Home button to function with.
I took the phone to the service center and they said it's a single piece with the display so the entire display would need to be replaced which is unreasonable and needless since the display works absolutely perfect.
So I was thinking of a remedy in terms of the ROM I use with the phone. Is there any custom ROM available for the S2 which would enable me to use a part of the display as the MENU and BACK buttons itself ? Like the Nexus 4 has ? I don't mind losing out on screen space to enable me to get those buttons back.
Please do suggest me any such ROM's or methods through which I can use the phone without having to change a fully functional touchscreen display. Spending so much just to get the Soft key functionality back is plain ridiculous and a pure manufacturing drawback from Samsung. Yuck
Anyways, please do help with any pointers.
Thanks and Cheers !
Click to expand...
Click to collapse
You'll be hard pressed to find a 4.2.2 ROM that doesn't have some sort of on-screen control. Do a bit of searching around on XDA of all the 4.2.2 ROMs, look at screenshots etc. Navigation bar is the same style as a Nexus 4. Pie controls are a method of on-screen control. AOKP ribbons are also for on screen control. There's probably more. Then there exist ROM's which attempt to mimic the AOSP, Nexus-style experience. Plenty to choose from.
Hopper8 said:
You'll be hard pressed to find a 4.2.2 ROM that doesn't have some sort of on-screen control. Do a bit of searching around on XDA of all the 4.2.2 ROMs, look at screenshots etc. Navigation bar is the same style as a Nexus 4. Pie controls are a method of on-screen control. AOKP ribbons are also for on screen control. There's probably more. Then there exist ROM's which attempt to mimic the AOSP, Nexus-style experience. Plenty to choose from.
Click to expand...
Click to collapse
So basically My ROM territory is now limited to any 4.2.2 AOSP/AOKP Rom's ? Do all of them have on-screen navigation?
Like the Parandroid? No more Sammy Rom's obviously.
HellRazorGod said:
So basically My ROM territory is now limited to any 4.2.2 AOSP/AOKP Rom's ? Do all of them have on-screen navigation?
Like the Parandroid? No more Sammy Rom's obviously.
Click to expand...
Click to collapse
Hmm well I imagine you could find some lower than 4.2.2 with those controls if you wanted to, but no need to if you don't want. You can use ParanoidAndroid if you want, search my posts for a link for i9100, I posted it yesterday or the day before I think. It won't be the first link you find on Google thats for sure, version 3.6 is the latest. As far as 'limited to 4.2.2 AOSP/AOKP'.... Depends how you see it. I don't see it as a 'limitation'. Start here: http://forum.xda-developers.com/showthread.php?p=23231772. Go through AOKP and AOSP till you find something you like. Bear in mind that the AOKP contains waaay more than just plain AOKP, there's hybrid (combos of CM,AOKP,PA, AOSP usually) and all sorts in there.
Enable Navigation Bar in AOSP/AOKP roms etc for getting these functions back.
Alternatively if you want navigation bar in Sammy Roms you can still have them , look for soft key enabler in play store or else you can edit build.prop of your phone , there will be option of soft keys , change it from 0 to 1.
Use pimp my rom it have a option for on screen buttons (back menu and recents) so you can have any rom
Sent from my GT-I9100 using xda premium
S2 soft keys not working
Issue seems to be related to the usb charging receptacle. As long as a good charging cable is connected, the soft keys work. They work for a short time after unplugging and then stop working again.
HellRazorGod said:
Greetings my fellow XDA experts,
I have a Galaxy S2 (i9100) International version on the NeatROM 4.8 ( XXLSW). What has happened is that my Softkeys are dead and unresponsive.
There is no illumination and response from them. So I have a phone without the menu and back buttons, which implies that I have a f**ked up iPhone like phone with just one Home button to function with.
I took the phone to the service center and they said it's a single piece with the display so the entire display would need to be replaced which is unreasonable and needless since the display works absolutely perfect.
So I was thinking of a remedy in terms of the ROM I use with the phone. Is there any custom ROM available for the S2 which would enable me to use a part of the display as the MENU and BACK buttons itself ? Like the Nexus 4 has ? I don't mind losing out on screen space to enable me to get those buttons back.
Please do suggest me any such ROM's or methods through which I can use the phone without having to change a fully functional touchscreen display. Spending so much just to get the Soft key functionality back is plain ridiculous and a pure manufacturing drawback from Samsung. Yuck
Anyways, please do help with any pointers.
Thanks and Cheers !
Click to expand...
Click to collapse
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!