Database Users

problem S2U2 on X1.

has anyone experience any problem when using S2U2 on X1? I can press panel key or Ok key then it will take me to the panel/today screen without slide to unlock.
S2U2 screen sometimes display abnormal
Please?

randy_c said:
has anyone experience any problem when using S2U2 on X1? I can press panel key or Ok key then it will take me to the panel/today screen without slide to unlock.
Click to expand...
Click to collapse
Same here. The Panelbutton as well as the Camera button still work in S2U2 lock mode. It doesn't concern me much, because it's essential that noone gets a phone call or music starts to play while the phone is in my pocket. If the panel-button is accidentally pressed nothing bad happens.
S2U2 screen sometimes display abnormal
Please?
Click to expand...
Click to collapse
This sometimes occured when I set the "Display Mode" to DirectDraw. Now I use RawBuffer and haven't had this problem for 3 weeks now.
Let me ask you a question:
When in landscape-mode and the phone is locked with S2U2 the button to slide reacts very slow. In portrait-mode the button follows the finger very quickly. Is it the same with your phone?

Let me ask you a question:
When in landscape-mode and the phone is locked with S2U2 the button to slide reacts very slow. In portrait-mode the button follows the finger very quickly. Is it the same with your phone?[/QUOTE]
I have the same problem. Maybe it's the X1

Thanks, so then I'm calmed First I thought it could be an issue of the picture I use but after a few different ones it was still the same. So it's not just my phone

that's interesting, with the exception of the landscape problem I wasn't aware of the x-panel and camera button issues. This is more likely going to be a fix / update needed for S2U2...

I have got the same problem.
S2U2 doesn't work correctly in landscape mode on my Xperia. The sliding thing and the whole program become very slow.
This problem doesn't seem to be solved yet.
I am wondering if its a Xperia only problem, otherwise in should have been fixed till now.

F-Styla said:
I have got the same problem.
S2U2 doesn't work correctly in landscape mode on my Xperia. The sliding thing and the whole program become very slow.
This problem doesn't seem to be solved yet.
I am wondering if its a Xperia only problem, otherwise in should have been fixed till now.
Click to expand...
Click to collapse
The Xperia always seems to be very slow in landscape mode no matter if I'm using the SE panel, the messaging application or touchflo3D. Very strange behaviour considering the display resolution stays the same.

It is partly a xperia specific problem. The panel button is controlled at a very low level in the phone. The panel button action is located in the registry, but that action is called from a low level. The button isn`t recorded by most programs.
A_C knows of this issue.
btw, you can disable landscape for s2u2. So it`s in portrait allways.

dekeijzer said:
btw, you can disable landscape for s2u2. So it`s in portrait allways.
Click to expand...
Click to collapse
Yeah, that's right. But then sometimes the screen messes up completely when I slide out the keyboard and the phone wants to change the screen mode. Also, I have problems with the dialer and S2U2. Sometimes the dialer screen stays on top but S2U2 locks the screen. There is no way to unlock the screen anymore because S2U2 is not on top but the dialer screen cannot be closed.

If this problem is Xperia specific, I will disable S2U2 in landscape mode. I always hoped they will bring a update which solves this problem.
The Xperia always seems to be very slow in landscape mode no matter if I'm using the SE panel, the messaging application or touchflo3D. Very strange behaviour considering the display resolution stays the same.
Click to expand...
Click to collapse
Yes i realized the same. I thought this would be a problem of Windows Mobile and not of the Xperia. If it is a Xperia problem, this is a big minus point for the phone.

It's a nice unlock system, but I have found that when I use this programme the battery loses power quickly.

was using ver 1.44 very stable for a long time
until i installed panel manager from r3a... same issues with panel button unlocking and ok button unlocking
upgraded to 1.62 and problems got worse...
downgraded to 1.52 and switched back to panel manager r2a for the time being.. which is ok.. b/c i rarely used the growing panel and the new cnn panel sucked anyway..
would love to have all the features of s2u2 1.62 but alas xperia doesn't quite seem to work that well with it
currently i have s2u2 set to ignore screen rotation and not unlock with keyboard slide out
my only real grief at this point is that it won't let me use slied to answer or just the regular answer keys with caller id turned on ... i have to turn it off and use the SE answer key completely unlocks my phone to display that message too so agravating...
A_c makes a kick ass program none-the-less ... !!!

same problem here. Also with last version no lock for panel button and camera button...

Camera and Panel button are known issues ...but not a problem for me either -as I do not see S2U2 as a "security focused lock" ...instead I see it as a "prevent accidental calls etc" type of lock
I still use the system lock with password if I need to "security lock it" (using a today shortcut that immediately invokes it, with password)
Must say I suffered some probs with v1.4 and v1.5 (caller ID & power drain)
But am using 1.62 without problems -it doesn't freeze on caller ID (I have it on window rather than full screen) and the battery drain has gone completely (uses <10% overnight for example, with G-alarm and data / active sync both running all night)
I found that it really was critical to uninstall, delete the S2U2 folder in program files, and delete the whole S2U2 tree in the registry ...and then soft reset -before installing the new version
I'm a huge fan of S2U2 ...its just awesome -without a doubt THE must-have app IMHO and always the first thing I install after a hard reset

I use S2U2 and have just upgraded to 1.62. Seems to be working ok so far, although no-one's called me since I upgraded so not sure of freeze problem :-(
(note to self: Get out more, make some friends ;-)
I find landscape doesn't work well at all with S2U2, but then I also find that with PointUI Home2, so maybe it's an X1 thing with particular software...?

The battery drain issue does seem to be resolved in 1.62.
I too am having problems with screen freezing when a call is received - the slider doesn't answer and since I had the buttons disabled there was no way to answer the call.
I'm still experimenting with other settings but I don't get many calls so it is a long process.
Still, a superb program and essential for me because of the problems with a magnetic case which causes calls to be answered just by removing the phone from the case.

jcsxda said:
Camera and Panel button are known issues ...but not a problem for me either -as I do not see S2U2 as a "security focused lock" ...instead I see it as a "prevent accidental calls etc" type of lock
Click to expand...
Click to collapse
Which means it can't even do accidental call prevention properly, as I found today. It's still quite easy to press the Panel button then the Call button in succession, as they are next to each other, especially if the phone's in a case. Result - pocket dialling, defeating the whole object of program. Shame really, as I've found S2U2 ideal on other phones.

Yep landscape is very slow ..... when i put ignore screen rotation on sometimes when open the keyboard screen goes all fuzzy... bitof a problem. But its a great program...sure it just needs some tweaks n bugfixxes for the X1

sweeet on v2.02 im no longer getting these landscape issues

[Q] Navigation Bar not working in Portrait working in Landscape in Nexus 4

My Nexus 4 has Stock ROM Android 4.3 & the Navigation bar at the bottom does not respond to touch in Portrait position but works in Landscape position for applications where I can use the Landscape mode. In the Landscape mode the screen rotates the position of the Navigation bar.
I have through the developer option selected the Show Touches option which shows me the exact touch position on screen as a blob. In the portrait position I can see the touch points on the Navigation bar the home screen works for Google Now but the back & task do not work however I can see from the Show touch it registers the touch but no execution of the command happens. The same Navigation bar in Landscape mode works perfectly as required. These developments are after the OTA 4.3 upgrade. Can someone help me to either remove the navigation bar in the Stock ROM Android 4.3 as now I have an application from Google store called Button Saviour (Non Root) working perfectly. I have also observed that the due to the Show Touch option activation it generates sometimes on the navigation bar area on the extreme left a clear Show touch blob where as there is no one touching the screen. This Show touch blob sometimes rapidly oscillates horizontally in the Navigation bar area & which ever icons it crosses it automatically triggers them as well randomly. On touching the screen in the Navigation Bar at that time does not make the back or task button work but without touching I can the Show touch blob while oscillating managing to make it work while crossing over the respective button icons.
So the hardware does not seem to be the issue but some bug in the new 4.3 which is triggering this weird behaviour. I use the Nexus 4 mostly in Portrait mode hence it is frustrating to now suddenly not have the Navigation bar functional the way it was suppose to work. Can some one help & guide me on what to do to resolve this problem.

The softkeys are enabled within the framework.
Sent from my Nexus 4 using Tapatalk 4

Help
manojsap said:
My Nexus 4 has Stock ROM Android 4.3 & the Navigation bar at the bottom does not respond to touch in Portrait position but works in Landscape position for applications where I can use the Landscape mode. In the Landscape mode the screen rotates the position of the Navigation bar.
I have through the developer option selected the Show Touches option which shows me the exact touch position on screen as a blob. In the portrait position I can see the touch points on the Navigation bar the home screen works for Google Now but the back & task do not work however I can see from the Show touch it registers the touch but no execution of the command happens. The same Navigation bar in Landscape mode works perfectly as required. These developments are after the OTA 4.3 upgrade. Can someone help me to either remove the navigation bar in the Stock ROM Android 4.3 as now I have an application from Google store called Button Saviour (Non Root) working perfectly. I have also observed that the due to the Show Touch option activation it generates sometimes on the navigation bar area on the extreme left a clear Show touch blob where as there is no one touching the screen. This Show touch blob sometimes rapidly oscillates horizontally in the Navigation bar area & which ever icons it crosses it automatically triggers them as well randomly. On touching the screen in the Navigation Bar at that time does not make the back or task button work but without touching I can the Show touch blob while oscillating managing to make it work while crossing over the respective button icons.
So the hardware does not seem to be the issue but some bug in the new 4.3 which is triggering this weird behaviour. I use the Nexus 4 mostly in Portrait mode hence it is frustrating to now suddenly not have the Navigation bar functional the way it was suppose to work. Can some one help & guide me on what to do to resolve this problem.
Click to expand...
Click to collapse
same issue here even i try a factory reset
I flash the stock rom again and no clue of what to do

The exact same issue here, started behaving quirky since 4.3 and went bat**** crazy after the update second 4.3 ota (1.8mb patch google released recently). i used developer options to show the on screen touch blobs as well and it registers touches in the nav bar area, it just will not work in portriat (or rather that section of the screen) It is extremely frustrating.
I even went as far as to use adb and fastboot to restore my phone to stock 4.3 which would remove all files and place a stock 4.3 directly from dev.google but still It doesn't work.

The same issue
Im having this exact issue just a few days after i install a new update i hope that its a software issue :crying: and if is not warranty will cover it?

Navigation Bar issue
Same problem here , wont respond on portrait mode.
I did try to downgrade my android version to 4.2.2 (from 4.3) after the factory reset did not work, that did not work either.
Any ideas? could use some help

I have the same problem, I tried to restore the 4.3, the 4.2, but the problem remains, I also tried the cyanogenmod and 4.4, but it still does not work the navbar in portrait mode ..
No one knows a solution to the problem? You may have a hardware problem? Who takes care of the navbar?

Having the same issue here. Works in Landscape but not portrait. It went spastic this morning randomnly opening the clock and pullin the bar down itself. Show touches showed it registering touches all around the nav bar then suddenly it stopped. I cant use the bar now at all in portrait but the random touches are gone. I downloaded a touch detector and it shows all the way up to where the nav bar would be then deadzone, but fine in landscape again

anyone know a solution to the problem? I tried to put the last KRT16S factory image, but the problem is always the same ...

sorschumi said:
anyone know a solution to the problem? I tried to put the last KRT16S factory image, but the problem is always the same ...
Click to expand...
Click to collapse
Before update to 4.4, I installed purity rom, and in purity system settings there was option to change navigation bar height. Default height is 48dp, but you can change to 52dp and the buttons working. Not ideal solution, sometimes you must to hit button few times, but it's working!
But, after I update my N4 to 4.4 kitkat, and install purity rom for 4.4, there is no option to set button height to 52dp (max heigth is 48dp-default height) I hope so that purity rom will be updated and return option to set to 52dp.

Same issue here
Tried lot of things still not working .........
pls someone find the solution.......

skycoresaunish said:
Tried lot of things still not working .........
pls someone find the solution.......
Click to expand...
Click to collapse
I think it's a hardware problem. Mine just went bad as well.

I have this problem now, too. Google now NAVRING still works to open Google Now from the middle nav button, which is why I do not understand why they nav bars do not work at seemingly the bottom of the screen. It just seems like that part of the screen has died, though some times it randomly works....... what the hell is this?

Huawei ascend mate navbar problem
I have same problem. And not only that my landscape control also got messed up After factory reset.
Also when I try to scroll down the web page in landscape mode it dosent work on the same area. So does this mean screen is screen is not registering my touch.
Some times the middle button start acting funny. It operates by itself even the internet is off. Like virus or some thing I did checked with antivirus nothing found. After activating show touch option it is shows Google shortcut is always pressed.
Dont know how to fix. Dont know the reason pls. Help. Xda.

Do you use dt2w? For me, after enabling that feature this would happen after a while. The borders of the screen would become unresponsive. I disabled dt2w, rebooted and it was fine again.
Sent from my Nexus 4 using XDA Free mobile app

Hi to everyone!
I have the same problem since some days with the nav bar on stock 4.4.2. Factory reset + rom flash via fastboot + CM 11 innstallation did not help at all. I'll bring my Nexus 4 today back to the retailer for reparation / replacing.
I'll inform you guys about the report of service center but it can take up to 45 days.

Thanks. This works for me
haris0032 said:
Before update to 4.4, I installed purity rom, and in purity system settings there was option to change navigation bar height. Default height is 48dp, but you can change to 52dp and the buttons working. Not ideal solution, sometimes you must to hit button few times, but it's working!
But, after I update my N4 to 4.4 kitkat, and install purity rom for 4.4, there is no option to set button height to 52dp (max heigth is 48dp-default height) I hope so that purity rom will be updated and return option to set to 52dp.
Click to expand...
Click to collapse
Hi, I was facing the same issue on my mako. It just started without any notice. Being a flashaholic I thought it could be due to something I installed. Tried a lot of differnt ROMS including stock but no luck. Read somewhere about the "Show touch" function in the developer options and found that almost 7.5mm of the bottom of screen was not responding to touch. I then installed the stock 4.4.3 ROM, rooted it and installed gravity box. In Gravity I changed the navigation bar height to 120% and selected "keep at bottom" for landscape. I am now able to use the phone. I wish some custom ROMS start implementing 52dp height option so we could use these directly. I tried using gravity with Mahdi ROM but there is some conflict and I cant see the recents button. Also, the NB reverts to original and it needs to be enabled again manually
But thanks anyways. I dont want to buy a new phone for the next 6 months and this will work well for me.
Cheers

No touch input after update to Lollipop

Need help as my phone became barely usable aftaer OTA update.
The top end of the screen (about 1 cm top to down) is not responding to touch. I cant tap any input in common use cases like using google search box widget, answering a call while in app using the new call feature, tap Send when composing an email and so on...
The only case this part of screen is active is when pulling down the notification bar, tapping objects like the clock (time display) Setting icon etc'. So I beleave this is not a hardware issue.
I did wipe the catch with no help and reset to factory setting with no help as well.
Did anyone experiance the same issue?
Any idea how can I overcome this except down grading back to 4.4.2?
Any easy trick for some one who is not a developer or deeply technical?
THANKS!

Navigation buttons issue

Hello all. Just yesterday my XT1575 started acting up, the navigation buttons - all three, Back, Home, Recents - are not working anymore. Initially, I thought it was a minor thing that could be sorted out with a reboot. I rebooted yet no show, still not working. I went to the extreme and did a factory reset, still no show. I fastbooted a fresh install, no show. I installed custom recovery and flashed a ROM, no show. But I made one discovery - in TWRP recovery the navigation buttons work just fine, and they are almost at the same location the main ones are on the phone screen when booted. This made me more skeptic if it was a hardware issue. As it is now I'm thinking of getting another screen to replace this one, but want to be sure this will fix the issue before shelling out more than $50 for a replacement screen.
Please all suggestions and advice is very welcome. I need to fix this. I love this phone. Thanks all.

maybe try to go to settings, enable dev options and then enable show touches

iks8 said:
maybe try to go to settings, enable dev options and then enable show touches
Click to expand...
Click to collapse
I also agree. Doing this will allow you to see if any key presses being registered when pressed in the affected spot.

Fix(?)...
OK. I stumbled on a fix, maybe a permanent fix, maybe not... I rooted with BETA-SuperSU-v2.62-3-20151211162651.zip directly flashed in TWRP recovery, no need messing with extracting anything and all those long steps in a related rooting thread. Flashed Xposed (xposed-v86-sdk23-arm64.zip), installed XposedInstaller_3.1.1.apk and after all this, installed Gravity module for Marshmallow. Go to Navigation bar tweaks in Gravity, activate master switch, enable navigation bar and scroll down and then increase the height and width of horizontal navigation bar to 124 or more (124 is the minimum for things to work again). And, voila... The navigation buttons work again. I hope this helps someone with this issue.

ezeuba said:
OK. I stumbled on a fix, maybe a permanent fix, maybe not... I rooted with BETA-SuperSU-v2.62-3-20151211162651.zip directly flashed in TWRP recovery, no need messing with extracting anything and all those long steps in a related rooting thread. Flashed Xposed (xposed-v86-sdk23-arm64.zip), installed XposedInstaller_3.1.1.apk and after all this, installed Gravity module for Marshmallow. Go to Navigation bar tweaks in Gravity, activate master switch, enable navigation bar and scroll down and then increase the height and width of horizontal navigation bar to 124 or more (124 is the minimum for things to work again). And, voila... The navigation buttons work again. I hope this helps someone with this issue.
Click to expand...
Click to collapse
Hi im having the same issue. How did yours happen? Mine happened after dropping my phone. Also I enabled Show Touches in Dev Options and the pointer would only go to the top of the nav bar and not on it even though my finger is on the nav bar.

I had this exact same issue with my Moto X Style. I was not willing to spend anything on this 3 year old device. Looked around for solutions but none worked. Finally settled for a 3rd party app which floats on screen, but very annoying. Found a commnet on a Youtube video who asked to change the display setting and it worked.
Settings -> Display -> Display Size. Change it from Default to large, larger or largest. It worked for me when I set Large. Just wanted to share it here, so it might help someone desparate.

https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049

lockscreen problem Moto G4 Nougat

Hi anyone else experiencing a bug where it takes like 5/6 trys to slide the lockscreen up. Its like im not sliding up enough but im going off the top of the screen i have to flick like 20 times sometimes.

Indeed Nougat seems to require a slightly different swipe-up-to-unlock action than Marshmallow. If you're going off the top of your screen, though, you are doing it wrong. You're not catching Pokémon, just slowly swipe up about an inch, that should already trigger the unlock. Do a practice run, see how slow and short you can do it, you'll be surprised.

I also have this problem since the update to Nougat, sometimes the screen will unlock with a short swipe and others you have to go the full length of the screen!
I have taken the screen lock off for now as i am fed up with swiping 5+ times to unlock the phone

If you disable swipe to shrink screen in moto actions then it works fine.
Sent from my XT1039 using Tapatalk

Yeah it works fine with swipe to shrink disabled now thanks
Shame that the swipe to shrink is causing the problem.

I can confirm the issue, and for the moment, also the solution! Thanks guys
Enviado de meu Moto G (4) usando Tapatalk

Had same problem but this didn't fix it for me. Ended up disabling/enabling Moto app. Noticed System UI tuner had disappeared so re-enabled that also. So far so good...

This is an old thread, but my findings may be relevant. A short time ago, I also started to have problems with all sort of swiping, on the home screen, but also when swiping away notifications or within apps. (Ironic, since I initially discarded those problems in the first answer here. Mea culpa.)
Eventually, I found the reason for it. I used a small app, "Media Volume Only", which hooked into the special "read phone status" permissions (in this case to monitor and modify volume keys behaviour). I assume in the process of monitoring gestures/keys it interferes with swiping actions. After disallowing, disabling and deinstalling this app, my swiping actions are as responsive as they should be.
So if you still have problems with swiping, it may well worth looking into these apps that carry that special permission.

Disaable all smart lock option.
Mainly on body detection option.
Thanks....
Its working 100%

martinisok said:
If you disable swipe to shrink screen in moto actions then it works fine.
Sent from my XT1039 using Tapatalk
Click to expand...
Click to collapse
You nailed it! Not only does their "Swipe to shrink screen" feature work TERRIBLY, as if that wasn't poor enough execution, it works terribly at the expense of making the swipe to unlock so completely frustratingly UNRELIABLE.
These folks need to take a leaf out of Huawei's book and make the swipe to shrink, work by swiping horizontally across the navigation bar ... (Huawei, incidentally, are FAR from perfect and need to fix their TERRIBLY laggy, sluggish phones) - you can SEE why people side with iPhone, can't ya!

cs5210 said:
Disaable all smart lock option.
Mainly on body detection option.
Thanks....
Its working 100%
Click to expand...
Click to collapse
On body detection is the reason in my case.
Problem solved now