Related
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.
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!
First of all, thanks to @xtermmin for pointing me in the right direction for this.
Steps to increase touch sensitivity and get DTTW functioning better:
Download Shortcut Master Lite
Hit the ellipsis at the top right and click App Explorer (Yes to the error)
Tap anywhere to get the loading circle to go away and find something called Force Touch
In the Force Touch menu, select ZteLCDPressureSettings and hit Launch
Here you will find some options.
Tap Pressure Sensitivity and move the red dot slider all the way to the left where the green "Light" is.
Back out of the menu and you are done.
There are some other things under features that may be of interest as well to some people.
Additionally, there are a couple other items in the Force Touch menu that could play a role in ROMs down the line. The "Press Image" option has a toggle within that item but it does not stick upon backing out and reentering the menu.
If you find anything else of interest, please let everyone know so we can make this the best phone we've ever owned.
Thanks!
Awesome, T2W works better now.... Thanks
P. S. Adding your thread to my all in one place guides.
xgerryx said:
First of all, thanks to @xtermmin for pointing me in the right direction for this.
Steps to increase touch sensitivity and get DTTW functioning better:
Download Shortcut Master Lite
Hit the ellipsis at the top right and click App Explorer (Yes to the error)
Tap anywhere to get the loading circle to go away and find something called Force Touch
In the Force Touch menu, select ZteLCDPressureSettings and hit Launch
Here you will find some options.
Tap Pressure Sensitivity and move the red dot slider all the way to the left where the green "Light" is.
Back out of the menu and you are done.
There are some other things under features that may be of interest as well to some people.
Additionally, there are a couple other items in the Force Touch menu that could play a role in ROMs down the line. The "Press Image" option has a toggle within that item but it does not stick upon backing out and reentering the menu.
If you find anything else of interest, please let everyone know so we can make this the best phone we've ever owned.
Thanks!
Click to expand...
Click to collapse
With the shortcut master i had several loading problems, i used QuickshortcutMaker and this is more easy, Thanks !
xgerryx said:
First of all, thanks to @xtermmin for pointing me in the right direction for this.
Steps to increase touch sensitivity and get DTTW functioning better:
Download Shortcut Master Lite
Hit the ellipsis at the top right and click App Explorer (Yes to the error)
Tap anywhere to get the loading circle to go away and find something called Force Touch
In the Force Touch menu, select ZteLCDPressureSettings and hit Launch
Here you will find some options.
Tap Pressure Sensitivity and move the red dot slider all the way to the left where the green "Light" is.
Back out of the menu and you are done.
There are some other things under features that may be of interest as well to some people.
Additionally, there are a couple other items in the Force Touch menu that could play a role in ROMs down the line. The "Press Image" option has a toggle within that item but it does not stick upon backing out and reentering the menu.
If you find anything else of interest, please let everyone know so we can make this the best phone we've ever owned.
Thanks!
Click to expand...
Click to collapse
This definitely helped! Kinda odd that there is a slight delay from when you double tap and when it actually wakes. I remember the LG G2 responding more quickly with this feature. Also miss the double tap to lock screen too that almost no other phone had (though with nova launcher and an app, you can do this). Regardless, I'm glad the functionality is there.
What's interesting about this little hack is that it clearly is using the force touch settings that will be found in the 6GB RAM model that has a force touch display. Funny how it remains in the ROM anyway, just tucked away since this model doesn't use force touch.
Can I remove the vibration when I use the double tap to wake?
This has made 0 difference for me. I've got a 64gb US variant. I've also noticed double tap to wake stops working when the phone is in Doze. Anyone else have this issue?
Same same with doze, but when my phone isn't deeply asleep this tip indeed increased touch sensitivity.
Sent from my ZTE A2017U
DrakenFX said:
Awesome, T2W works better now.... Thanks
P. S. Adding your thread to my all in one place guides.
Click to expand...
Click to collapse
Did you know this app is also present on the a2017u usa version?
But it is not doing anything...
manu7irl said:
Did you know this app is also present on the a2017u usa version?
But it is not doing anything...
Click to expand...
Click to collapse
I'm using the a2017u LoL always has been.
tolymatev said:
Can I remove the vibration when I use the double tap to wake?
Click to expand...
Click to collapse
Is there a setting to disable the vibration with double tap to wake?
I've tried the mod but don't see any differences for better response for the double tap to wake.
Sent from my iPad Air 2
I don't have anything like force touch in quick shortmaster app or shortcut master lite. I'm on european B03 update... Can anyone confirm this?
kodrnusa said:
I don't have anything like force touch in quick shortmaster app or shortcut master lite. I'm on european B03 update... Can anyone confirm this?
Click to expand...
Click to collapse
It's actually there as been always and with B02 software version.
Do hard reset if not see it
Something get wrong with upgrade in your case.
pklee said:
Is there a setting to disable the vibration with double tap to wake?
Click to expand...
Click to collapse
Don't have vibration with double tap.
How did you get it
paatha13 said:
Don't have vibration with double tap.
How did you get it
Click to expand...
Click to collapse
It's there by default on the US model, at least.
While this definitely improves DT2W functionality, it's still temperamental. I find that now it responds best to very light touches, but harder taps are ignored. If I tweak it to be less sensitive, it does exactly that: it requires a harder touch at all times. Why can't it just respond to a range of touches? My G3 worked just fine in this regard.
rczrider said:
It's there by default on the US model, at least.
While this definitely improves DT2W functionality, it's still temperamental. I find that now it responds best to very light touches, but harder taps are ignored. If I tweak it to be less sensitive, it does exactly that: it requires a harder touch at all times. Why can't it just respond to a range of touches? My G3 worked just fine in this regard.
Click to expand...
Click to collapse
Totally agree with this. It's still very inconsistent, but mine does work if I slam it twice as well as tap it lightly twice. It doesnt always work and it's still delayed. This was sort of a bandaid for a bigger problem though. I hope CM, and ....probably nothing else? at this point...can address it further.
rczrider said:
It's there by default on the US model, at least.
While this definitely improves DT2W functionality, it's still temperamental. I find that now it responds best to very light touches, but harder taps are ignored. If I tweak it to be less sensitive, it does exactly that: it requires a harder touch at all times. Why can't it just respond to a range of touches? My G3 worked just fine in this regard.
Click to expand...
Click to collapse
At EU version I don't see any option for vibration so far.
But totally agree I would like to be more response to a range of touch.
I remember when had LG flex 2 was better implementation than ZTE.
Hope future update improve that.
Sent from my iPad Air 2
paatha13 said:
At EU version I don't see any option for vibration so far.
But totally agree I would like to be more response to a range of touch.
I remember when had LG flex 2 was better implementation than ZTE.
Hope future update improve that.
Click to expand...
Click to collapse
Quite honestly, the Axon 7's story is perpetually: "[insert company here] did a better job of implementing [insert feature here]". There is very little (if anything) that the Axon 7 does better than the big manufacturers, IMO. It does a passable (sometimes even decent) job of most things, though - and at an appreciable discount - which is why I still have mine. It's a budget flagship. It's high-trim Toyota versus a Lexus. Add to that the potential for improvements via software (which is the source of many of my complaints, really), and I think it's a solid buy with quirks I'm willing to live with for a little while as ZTE steps up and makes improvements.
Yep exactly from hardware point is very very capable device but from software although it's pretty good level but there's still staff for many improvements.
Axon 7 is my first Chinese smartphone from Chinese company until now and I'm quite pleased with the all package offering having it 5-6 days,but I would like to see from ZTE much more effort and listening the user base and bring as much improvement and tweaks to the software.
Sent from my iPad Air 2
paatha13 said:
It's actually there as been always and with B02 software version.
Do hard reset if not see it
Something get wrong with upgrade in your case.
I already did factory reset. And then again . No such setting in quickshortmaker. I can post pics.. Weird...
Edit..
Did change language to English and found it ?
Click to expand...
Click to collapse
I notice no difference in the week that I used this tweak. So I just put this settings back. Yup, still no difference to me.
Sent from my ZTE A2017U using Tapatalk
Hi guys,
I just flashed android 10 on my oneplus 3 via Havoc v3.4.
I was wondering, whether somebody were able to help me with a kind of special problem.
So I'm using my home button to put the phone to sleep by long pressing it. This can be set in the phone settings. so far so good.
But now on android 10 the duration of said long press seems to be unnecessarily long, like over a second. Thats really annoying, when you just want to put your phone away and have to keep your finger on that capacity button for that extra amount of time.
So I was wondering, whether there might be a relatively simple way of tweaking the build.prop or something, to change the duration of said time_out ?
I already tried the hold/delay in the google settings, but that's just for touch inputs on the screen.
Also the forum search didn't pop up any usefull results.
Thanks so far!