So there is this app that if you use ADB, it can give you Android O's navigation bar...without root: Here
However, when I checked something off in one of the settings, something crashed my phone and sent me back to my lockscreen, now when I try to go to put in my passcode, it crashes before I have a chance to use it. The command I put in is this to get the app to let me use it: "pm grant xyz.paphonb.systemuituner android.permission.WRITE_SECURE_SETTINGS" but thats not what broke it, I think it was a setting where I tried to add a extra button. I dont think my navagation bar works anymore...
Is there a way to reverse this without resetting my phone back to default? Let me know if I need to give out anymore info.
Running Unlocked HTC One A9 on 7.0, stock/unrooted/unmodified.
Try to reboot in safe mode and uninstall that app?
With the phone powered off, press the power button. As soon as you see the HTC logo, release the power button and press and hold the volume down button until you're in the OS. It should now be in safe mode and hopefully that app shouldn't boot.
i had the same problem, after the compatibility test of that app (customized nav bar by paphonb),.. status/notification bar, navigation bar disappeared. and when I try to open an app, the phone freezes. Please help!
Related
Wanted to know if anyone has found the source to do this yet the guy who made lock2.0 He has done it.http://groups.google.com/group/lock2/browse_thread/thread/13c69be014e196ac
Have you tried rebooting after installing? Other users are reporting success after doing that.
Donate version only has the menu screen removed. Works great on my phone. Worth the donation. At least until A_C starts developing for android.
aad4321 said:
i just downloaded that app, and you have to press menu to unlock the phone, then swipe to unlock. who wants to unlock their phone twice?
Click to expand...
Click to collapse
it works, donated version thought. and now has a password feature, its beta right now..
Maybe I'm a little confused here, but here goes.
I've tried downloading the free version just to see how it works, but I have NO idea where the heck to get different skins for this app?
Am I just a bit "slow?"
TooSlo said:
Maybe I'm a little confused here, but here goes.
I've tried downloading the free version just to see how it works, but I have NO idea where the heck to get different skins for this app?
Am I just a bit "slow?"
Click to expand...
Click to collapse
http://androidcommunity.com/forums/f52/lock-2-0-iphone-screenlock-app-13800/
edit: just found this as well http://forum.xda-developers.com/showthread.php?t=489386
FWIW, how would you have it so that you don't press menu in order to get the swipe screen up? You would need to have the screen on at all times.
The difference between the paid/free versions are a nag screen. That's it.
TooSlo said:
Maybe I'm a little confused here, but here goes.
I've tried downloading the free version just to see how it works, but I have NO idea where the heck to get different skins for this app?
Am I just a bit "slow?"
Click to expand...
Click to collapse
Can't find it myself. There's talks of a "Skin Manager" - but I can't find it.
I should note that the Free version removes the menu as well now. He's doing the free versions 1-update behind the donate version. I didn't need to reboot, it worked instantly.
FWIW, how would you have it so that you don't press menu in order to get the swipe screen up? You would need to have the screen on at all times.
Click to expand...
Click to collapse
Power button. Iirc (don't feel like changing it back). Menu or power take you to the locked screen, this just swaps that screen for a slide-to-unlock.
KyleK29 said:
Can't find it myself. There's talks of a "Skin Manager" - but I can't find it.
I should note that the Free version removes the menu as well now. He's doing the free versions 1-update behind the donate version. I didn't need to reboot, it worked instantly.
Power button. Iirc (don't feel like changing it back). Menu or power take you to the locked screen, this just swaps that screen for a slide-to-unlock.
Click to expand...
Click to collapse
Right, but this was a question for aad4321. Either the free or paid versions allow you to press any key to get to the swipe screen.
So I managed to get the different zip files with the backgrounds and whatnot onto my SD card and still no love when I attempt to change the theme or battery logo.
It says that it was successfully changed, then nothing happens. i've tried rebooting since then with no success either.
I was really looking forward to this type of app, I just don't dig the skull screen and grey swipe bar.
Lock 2.0 is a neat idea, but currently pointless graphical fluff as you can bypass the slide to unlock simply by hitting the home key. So pressing any button on the phone (home, send, end, back, or menu), pressing menu, and pressing home unlocks the phone.
If you were to take out the G1 default "press menu to unlock" screen, then pressing home twice would unlock the phone even with lock 2.0 installed.
Not to mention the fact that right now, the lock 2.0 home screen doesn't show signal (or even whether you have phone service at all), and doesn't show notifications. So I'd still want the option of bringing up the default G1 "press menu to unlock screen" until that's remedied by Lock 2.0
Sumanitu said:
Not to mention the fact that right now, the lock 2.0 home screen doesn't show signal (or even whether you have phone service at all), and doesn't show notifications. So I'd still want the option of bringing up the default G1 "press menu to unlock screen" until that's remedied by Lock 2.0
Click to expand...
Click to collapse
Mine shows the signal (upper corner) and currently activated devices (cell location / etc).
My procedure for unlock is:
Power Button to turn screen on > Slide to Unlock
Now mind you, I could very easily do Menu > Menu with the default G1. But I like to turn my phone on to see the time. The fact the default G1 doesn't allow for a background (a feature that I thought they definately should have included) on the lock screen kinda gives this program a boost for usage.
As far as I know, that is the same procedure the iPhone has (you press the one circle button at the bottom).
Seems like you guys want the screen itself to turn on to the Slide-to-Unlock screen by the sense of touch ..?
Lock 2.0 is a neat idea, but currently pointless graphical fluff as you can bypass the slide to unlock simply by hitting the home key. So pressing any button on the phone (home, send, end, back, or menu), pressing menu, and pressing home unlocks the phone.
Click to expand...
Click to collapse
Those buttons don't have that same feature for me (I'm using the free version). The most I get when pressing a button from the lock screen is a popup that says "Free Version". I have to slide to get to the home screen, or hit Menu > Home Screen.
hmmm.. that does not happens to me.. i just tried pressing home twice and it does not unlock.. im using the donated version maybe happens with the free? :/
Looks good, but definitely has a lot of room for improvement. The menu still comes up for me, so I have to press menu, then do the slide to get out. I don't need an extra keyguard screen... :/
*Edit: The version on the market is newer than that on the site, I just tried and the market one fixes this problem.
HOWEVER, there is one other problem keeping me from installing it permanently-- the screen doesn't stay off, it turns itself back on by flashing the "Free version" notification -.-
Once I get a new credit card I'll try the donation version, pretty sure that will fix the problem since it will not be "free".
With the latest version there is an option for a password lock. You have to enter the password to access the menu too. Right now the password is 1234 only for now but once it gets updated it could lock your phone safer than the normal android lock.
Sumanitu said:
Lock 2.0 is a neat idea, but currently pointless graphical fluff as you can bypass the slide to unlock simply by hitting the home key. So pressing any button on the phone (home, send, end, back, or menu), pressing menu, and pressing home unlocks the phone.
If you were to take out the G1 default "press menu to unlock" screen, then pressing home twice would unlock the phone even with lock 2.0 installed.
Not to mention the fact that right now, the lock 2.0 home screen doesn't show signal (or even whether you have phone service at all), and doesn't show notifications. So I'd still want the option of bringing up the default G1 "press menu to unlock screen" until that's remedied by Lock 2.0
Click to expand...
Click to collapse
Don't talk unless you have tried the newest version, which fixes all of these issues.
Last night, my AT&T HOX discharged completely. I'm thinking it might have reset and went into a constant bootloop, but I'm only guessing. So I plugged up to the charger and let it get charged about 10% before really messing with it. So rebooting the phone led me to a "frozen" screen. At first I thought it was the Picture Password Lockscreen app so I uninstalled it. No change.
I then realized it wasn't a frozen screen (although the slow start up continue after each reboot, but the home key would not function. Menu button will function, so would the back button. Only problem was that despite having the haptic response from the keys, I couldn't get to the home screen. It was just a white screen at and the notification bar at the top. The only way I was able to get a launcher to open was due to the Play Store notification that allowed me to open my ADW launcher from the app list. I installed a home switcher, but still, could not get the home button to work. The hepatic response was back, but it would not yield going directly to ADW as my default launcher, nor select one once I cleared defaults. So I dirty flashed my ROM (Venom XL 3.2.6) and again got the slow start and the inability fort he home key to bring me to the homescreen (or the option to select). I then thought the perhaps it was an issue with the kernel, but still the same thing occurs after flashing the stock kernel. I get the haptic response and the screen does a quick flash. Nothing else.
Has anyone encountered this before or have any idea what controls this function and how to fix it?
From launcher, check your hone button settings, preferences-gesture settings. Check Home key - it should say that it is set to Show home screen. If that doesnt work check to see if in pocket detection is enabled. If it is, try disabling.
Sent from my HTC One X using xda premium
Venomtester said:
From launcher, check your hone button settings, preferences-gesture settings. Check Home key - it should say that it is set to Show home screen. If that doesnt work check to see if in pocket detection is enabled. If it is, try disabling.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks for the tip, but I couldn't get it to work. Had to end up wiping data. Thanks anyway.
Hello all,
Recently the power button on my Nexus 5 has been acting really weird. Sometimes it works flawlessly, others it requires pressing it really hard to work. In order to prevent it to stop working indefinetely, I am looking for a way to remap my volume-up button so it can work as a power button. I don't need it to turn my phone on or to work in the recovery mode (from what I read, it seems to be impossible), only when Android is running.
I've already tried some workarounds:
1) Volume Unlock Power Button Fix app: I tried it, but it just allowed me to turn on my phone with volume but not turning off. Also, it drains a LOT of power.
2) Buttonremapper app: It would theoretically do exactly what I wanted, but did not work at all.
3) Editing generic.kl: I tried switching volume-up and power buttons codes in generic.kl, but also did not work. Maybe I need to modify another file?
3) Xposed Framework + Additions: The installation of Xposed went Ok, but after installing Additions module I got stucked in bootloop. I am running Android 5.1 stock, maybe this module is not yet compatible.
So, can anyone help me? Do I need to install a custom ROM?
PS: I live outside US, so no warranty for me. Otherwise I would just use it
Thanks in advance for any help!
Cheers,
Humberto
Hi folks,
Just a heads up for anyone who might be facing the same issue. I decided to change from stock to Cataclysm ROM due to some specific features (listed below). After the installation, here's what I did to work around this problem:
1) Enabled "Volume wake" and "Sleep button on status bar" in "Cataclysm Settings / Miscellaneous".
2) Enabled "Swipe to sleep" and resized NavBar to 115% in "Cataclysm Settings / Navigation bar options". -> This way I can swipe in NavBar at any time (except lockscreen) to turn off screen. I raised it a little to facilitate the swipe gesture.
3) Changed Lockscreen Dialer shortcut to ""Turn off Screen" app shortcut (just search for it in the play store) in "Cataclysm Settings / Lockscreen options" -> This allows me to just swipe right and turn off the screen when my security settings are disabled (which accounts for most of the time). I found it way faster than pressing sleep button in status bar, especially when I'm driving and I can't look at the screen. Plus, I don't really use the dialer function of my phone so often since the invention of Whatsapp ;P
I realize this is not the perfect solution, but I don't see a better way to deal with this power button malfunction problem (except from a hardware fix).
Hope this helps!
Cheers,
Humberto
PS: I am really enjoying Cataclysm. It's a very nice ROM, completely stable and with a lot of other interesting features aside from the ones mentioned above. I strongly encourage anyone to give it a try!
I'm facing the exact same problem but I really need to eliminate the power button or I will need a power button fix soon.
The solutions you found hthiengo are good if not needing to turn off (or worst: running out of battery, something that happens me sometimes). I'm in the situation that next time I hit power button I will need to replace the button, or throw the nexus away
I did installed the xposed additions for lollipop but it is not working, and the Cataclysm trick is not enough in this case
Ok, after some research I've found a temporary solution:
For the power button you can remap modifying the file gpio-keys.kl under system/usr/keylaout (i wonder why anyone could figure out thise before, no that difficult). I would like to map power button leeaving it useless but I've found it impossible to remap the power button (probably because the key number is not 116). I would have liked to see xposed additions to help me map the keys but is not functional at least for me.
If the phone runs out of battery I've found that if I plug the power cable by pressing both volume buttons at the same time, eventually it starts up with the bootloader so I can plug the pc cable and it will reboot sucessfully.
So despite the phone know is pretty disfunctional (not the best phone for a hurry without battery), I can still use it for some weeks before I plan buying a new one or something (or I find a place for reparing). Its a shame I could not find a better solution for example, ADT when powered off so I could just reboot it by using ADT reboot command while powered off.
And It would be really amazing if the volume up button could also power it on from the powered off state.
In my case the power button is broken, but sometimes it gets stuck and puts the phone in a reboot loop: To avoid pressing the power button accidentally I've made a hole in the protective case so its pretty difficult to access it.
That's all for now. If anyone can make it better I will be glad to hear him/her
Hi,
I'm having many issues with my Blade S6.
Home key stopped working, unable to hold down and switch apps, no notifications appearing. I re downloaded the latest update in hope i would just be able to manually update but it promts "update package is not matching, please checK'
I did a factory reset from the os and recovery and still the same problems exist.
Any suggestions?
Long press on home will start google now, long press on menu button will start recent apps. For update, you are doing something wrong, but we need more info...
Try reading this topic http://forum.xda-developers.com/showthread.php?t=3018031 and use it for all questions.
Yes it has previously been working fine with those actions. Also now I can't bring down the toggle bar from swiping down from the top. Also I get no lock screen even though I set a password.
I have attached a screenshot of the update error. Maybe its a build prop error...my blade is from Australia
so when i use 3 button navigation and i repeatedly press back or home button from an app it just shows for a split second a ghost image of the app i was in. a screen recording is attached as well.
smartasiankid said:
so when i use 3 button navigation and i repeatedly press back or home button from an app it just shows for a split second a ghost image of the app i was in. a screen recording is attached as well.
Click to expand...
Click to collapse
Do you have any Magisk modules installed that could conflict with systemUI?
If not, have you installed any apps that require root access/adb commands to work properly? (eg. systemui tuner)
Lada333 said:
Do you have any Magisk modules installed that could conflict with systemUI?
If not, have you installed any apps that require root access/adb commands to work properly? (eg. systemui tuner)
Click to expand...
Click to collapse
no nothing of that sort. i don't even have root on this and i dont have any apps that require adb commands. do you have the same issue on your end? try repeatedly tapping home/ back button on your pixel and let me know if you have the same issue.
I'm setup for no button/gestures atm with magisk & the aosp module which gives me mostly total control over gestures. If u ever want to try out root, now's the time...it's easier than ever! Just sayin'...cuz 3 button is prolly lot long for this world. Not only can u micro-manage the UI, you can squeeze approx. 20-30% more battery time outta android...usually. Switched to 3-button just to see...nothin' tho. Watched ur clip...strange indeed.
smartasiankid said:
no nothing of that sort. i don't even have root on this and i dont have any apps that require adb commands. do you have the same issue on your end? try repeatedly tapping home/ back button on your pixel and let me know if you have the same issue.
Click to expand...
Click to collapse
Luckily, no. I have tried to replicate the issue, doesn't happen my end.
I was having trouble with some apps previously that required adb to work. They would often make my quick settings glitch out, or sometimes have a similar effect when closing apps as what you currently experience.
Try to switch to gesture navigation, do a cold reboot, then switch back to 3 button?
Lada333 said:
Luckily, no. I have tried to replicate the issue, doesn't happen my end.
I was having trouble with some apps previously that required adb to work. They would often make my quick settings glitch out, or sometimes have a similar effect when closing apps as what you currently experience.
Try to switch to gesture navigation, do a cold reboot, then switch back to 3 button?
Click to expand...
Click to collapse
could you please post here a screen recording with 3 button navigation settings and touch pointers enabled in the record settings?
smartasiankid said:
could you please post here a screen recording with 3 button navigation settings and touch pointers enabled in the record settings?
Click to expand...
Click to collapse
What is it that you'd be looking for in a screen recording? I have no input lag when touching the home/back button, and there's no laggy animation for the app minimizing.
Lada333 said:
What is it that you'd be looking for in a screen recording? I have no input lag when touching the home/back button, and there's no laggy animation for the app minimizing.
Click to expand...
Click to collapse
well i would just like you to send a screen recording of you REPEATEDLY pressing home button on different apps and third party apps. you may not have any input lag because you only press the home button once not repeatedly, so please.