Related
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
Reserved
Sent from my Nexus 4 using Tapatalk
Thanks
This day just keeps getting better and better! Thanks again guys! (out of thanks today. I'll thank you tomorrow). One question though, is the camera working on this build?
I'm giving it a try now anyway, so I will report
Downloading...NOW!!! :highfive:
oh yeah!! :victory: :victory:
new version is up guys
the launcher problems as well the keyboard popup we cannot do anything...this is a bug on googles closed sourced new launcher lol. Lets hope they will update it as well soon. You can use nova instead which is in our builds as well
about camera we need to wait for the new bloobs from google. All other would be a hackish workaround which does not make sense assuming the blobs will be released soon
whatever
Fixes new version:
- added dalvik optimizations....so speed up step one
- reworked and adapted status bar clock and date customization to 4.4
- added some of our camera features (smart captchure, jpg quality, color filter, gps indicator)
- reworked the complete camera to the new google style. Google stoped it after they finished the photo camera interface lol. So all into new PIE style + some fixes + more consistent now
- added a bunch of Mms/SMS fixes
- activated on supported devices lockscreen transparency on nav and statusbar
- some stability fixes
- fixed some google 4.4 code derps
- a lot small stuff
have fun and cheers
PS. the camera features for deb of course you cannot use right now
I'm probably gonna flash this today The only question I have is this: I'm coming from an old nightly build of CyanogenMod 10.2, which is 4.3.
I remember when we made the jump to Jellybean, a new CWM had to be used and there were a bunch of changes.
It seems like the changeover from 4.3 to 4.4 is way less drastic.
WOuld I be able to get away with a dirty flash and just clear Dalvik cache, or do I have to do a full factory reset? I can Titanium Backup, I just would prefer not to
-edit- somehow doubleposted on accident, sorry!
DivinityCycle said:
I'm probably gonna flash this today The only question I have is this: I'm coming from an old nightly build of CyanogenMod 10.2, which is 4.3.
I remember when we made the jump to Jellybean, a new CWM had to be used and there were a bunch of changes.
It seems like the changeover from 4.3 to 4.4 is way less drastic.
WOuld I be able to get away with a dirty flash and just clear Dalvik cache, or do I have to do a full factory reset? I can Titanium Backup, I just would prefer not to
-edit- somehow doubleposted on accident, sorry!
Click to expand...
Click to collapse
Defiantly do a factory reset and format /system. 4.3 to 4.4 is too big of a jump for that.
I can't find TWRP 2.6.3.2
The newest version seems to be 2.6.3.1
Will it work with this version?
I flashed this last night using the same CWM Touch I used to flash cm10.2.
Flashed with twrp 2.6.3.1 all ok
Inviato dal mio Nexus 7 utilizzando Tapatalk
I have successfully flashed it, but I can't use this ROM for my daily driver because BlueTooth is broken. I use both a Pebble watch and a pair of A2DP headphones, and both lose connection after the screen is off for a couple minutes. Its acting like the Bluetooth interface is going to sleep for power savings, but this is happening while I am actually listening to audio via Bluetooth. I do this roughly 20 hours a week and "need" this functionality in my tablet.
As a result, I'm going back to CM10.2 for now...
sunra0815 said:
I can't find TWRP 2.6.3.2
The newest version seems to be 2.6.3.1
Will it work with this version?
Click to expand...
Click to collapse
yes, that's OK. I fixed the error in the OP. sorry about the confusion
Thanks for bringing slim KitKat tastyness to deb, I'm using the same ROM on my Nexus 4 and there the keyboard popup does not appear.
Everything working sweetly never would guess this is an alpha build
Sent from my Nexus 7 using Tapatalk 4
hay
Im flashing this room but the cam not working befor
Instul this room
What the mater
There is no camera app or is this purposedly taken out. I use gosms n cannot input any characters - is this a bug?
Sent from my C6833 using XDA Premium 4 mobile app
it is currently a hard task on the one hand we bring all our devices up on the other hand we put back our features...some are redefined some we programm completly from scratch with new stuff. Eg today we pushed about 200 commits from 4.3 into 4.4 for our other devices + fixes for current devices
but mostly ppl are interested in new features...so new build has:
- superuser included (need to be enabled in developer options!!!)
- a lot new features just discover them...to much to write up
- a new crt animation...check it out
- fix settings locale language problem
- and tons of fixes under the hood
and new build is up
I added a simple list yesterday but it is actually more we have already included:
- all keyboard features are back (force auto rotate, disable landscape fullscreen, force enter button, ime notification, volume key cursor control)
- clock statusbar features
- crt animation
- statusbar brigthness slide
- safe headset volume
- volume rocker features (wake device, sound skip)
- slims privacy guard
- volume panel features we had
- keyguard on supported devices shows now transparent navbar/statusbar as well
- wifi country code
- advanced reboot menu
- custom LED battery and notification features
- swipe qs -> notification and back
- disbale OTA from google
- slims camera and video features (smart capture, image quality, image size, gps indicator etc)
- implemented root (needs to be enabled in developer settings or in superuser settings. Disabled by default)
- tons of fixes in google code and optimizations
- a lot under the hood stuff
- and whatever I forgot to mention lol
Awesome!... I actually just flashed the rom today and love it... Can I dirty flash today's build?.. 8)
Dirty was just fine... I see the camera app in titanium but can't find it in my app drawer... Real smooth so far!... Cheers...
Sent from my Nexus 7 using XDA Premium 4 mobile app
mobile88 said:
There is no camera app or is this purposedly taken out. I use gosms n cannot input any characters - is this a bug?
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Me too
This Xposed module allows you to change the NavBar buttons on your Xperia/AOSP devices. On stock ROM, there're only three buttons on the NavBar (Back, Home and Recent Apps). Now you can have complete control of the buttons and how they look like.
Features
Show or hide Recent Apps, Menu and Search buttons
Re-order buttons
18 themes with different colors
Use your own images for buttons http://forum.xda-developers.com/showpost.php?p=53045744&postcount=136
Restart SystemUI to see changes immediately without rebooting (Busybox required)
Activate changes on the fly without root (Nougat only)
Define left and right margin
Define navbar height
Define search button action
Requirements
Your phone must be rooted
Xposed framework must be installed first http://forum.xda-developers.com/showthread.php?t=1574401
Xposed library 2.2 is required
Instructions
Install the module
Run Xposed Installer and enable the module Android NavBar Buttons
Reboot the phone
If you want to use your own button images, check out this link.
Permissions
WRITE_EXTERNAL_STORAGE - store stock button images for preview
READ_EXTERNAL_STORAGE - read stock button images for preview
GET_TASKS - used by Switch to Last App function
REORDER_TASKS - used by Switch to Last App function
Limitations & supported devices
I developed this module based on AOSP source code and tested only on my Xperia devices. I expect it to work also on AOSP devices such as Google Nexus. You can try it on other devices but I don't expect it to work universally, especially HTC and Samsung devices because their framework is heavily modified.
If you enable this module and Tinted Status Bar together, the color for the Home/Menu/Recent/Back buttons will be controlled by Tinted Status Bar while the Search button color will be controlled by this module.
If you're also using GravityBox, you must disable Navigation Bar Tweaks. Otherwise, this module won't work.
Currently the following devices are supported: (to be updated)
Sony Xperia ZR stock 4.3 ROM
Sony Xperia V stock 4.3 ROM
Sony Xperia ZL stock based custom ROM/eXistenZ
Sony Xperia SP ExistenZ 3.3.0
Sony Xperia T
Sony Xperia M dual stock 4.2.2 ROM
Sony Xperia Z1 4.4 ihackers 4.1
Sony Xperia Z1 Compact stock KK ROM
Sony Xperia Z stock 4.3 ROM
Nexus 5 stock 4.4.2
Nexus 7 (2013) stock 4.4.2
MUCH i5s
Moto G stock 4.4.2 ROM
Moto X stock 4.4.2 ROM
Samsung Galaxy Lollipop or older devices (you need to set qemu.hw.mainkeys=0 in build.prop to enable Navbar)
Samsung Galaxy Marshmallow or higher devices
Sony Xperia X series devices Marshmallow ROM
Credits
I used this guide to help me develop this module. This document is outdated but the concept is still the same.
Huge thanks to atticus182 for his great work of Softkey collection
http://forum.xda-developers.com/galaxy-nexus/themes-apps/softkeys-softkey-collection-t1413582
Thanks to C3C076 for his wonderful GravityBox! This module uses some of his codes for search button actions.
Supports & troubleshooting
If you're using Android 6 and are unable to see folders when importing image files for user define theme, you need to grant Storage permission in App settings.
If you find that this module doesn't work on your device and see FC repeatedly and both notification and navigation bar disappeared, don't panic! Just run Xposed Installer, disable this module and reboot.
If you want me to add support for your device, please send me the following:
Xposed log file
Your device model
Android and ROM version
Deodexed /system/app/SystemUI.apk or you can send me a link for the ROM
** I can only work on Xperia/AOSP devices at the moment, please don't send requests on other devices **
** CM ROM is not supported because it has its own implementation of NavBar **
Source code
You can find source code for this module from GitHub here.
Download
Xposed Module Repository | Play Store
Change Log
Code:
6.3
- Fix the issue that customized navbar is not activated after a reboot for Nougat and higher devices
6.2
- On Nougat and later, customzied navbar will be applied much earlier after a system reboot
6.1
- Add support for Android 8 (Oreo)
- Fix the issue that settings are not applied after system reboot for Nougat and higher
6.0
- Add support for Nougat
- Rename application as Android NavBar Buttons
- Settings can be activated on the fly without root in Nougat (except navbar height and width)
5.3
- Fix issue with Sony Xperia latest X series devices
5.2
- Automatically enable navbar on Samsung devices on Android 6
5.1
- Fix button size issue when orientation is changed on tablet
5.0
- Fix issue with Asus Zenpad when using user define theme
4.9
- Fix theme issue with Xperia device on Android 5.0 and higher
4.8
- New separator which can be used to split buttons into 2 groups to mimic tablet mode in Android 6.0.1
4.7
- Fix missing buttons on Huawei devices when theme is applied
4.6
- Add support for Android 6.0
4.5
- Fix theme not working for Home/Menu/Recent/Back buttons on HTC devices
4.4
- Fix button image size and navbar height issue in KK
4.3
- Fix button image size issue in Android 5.1
- Fix search button crash in ICS
4.2
- New search button actions (Launch shortcut, Kill foreground app)
4.1
- Add Russian translation
4.0
- Add support for Lollipop (Android 5.0)
3.8
- Bug fix that setting UI crashes on some devices
3.7
- New option to customize search button actions
3.6
- Bug fix an issue that navbar height adjustment doesn't work on some devices
3.5
- Maximum margin is now automatically set to 75% of screen width
- NavBar height adjustment
- Added Lollipop buttons to theme
3.4
- Fix issue during orientation change when recent button is disabled
- Larger margin values
3.3
- Define left and right margin
3.2
- Fix button alignment issue for Samsung Tab
3.1
- Add translation for Chinese (Thanks to surwscl)
3.0
- User define button images [URL="http://forum.xda-developers.com/showpost.php?p=53045744&postcount=136"]http://forum.xda-developers.com/showpost.php?p=53045744&postcount=136[/URL]
2.3
- Fix preview stock buttons not displayed correctly if a theme is currently in effect
2.2
- Fix preview stock button size on some devices
2.1
- Fix missing buttons in landscape mode in Nexus 7
- Fix stock button size on some devices
2.0
- New option to choose themes (17 themes with different colors)
- Bug fixes
1.2
- New option to show or hide Recent Apps button
1.1
- Add support for MUCH i5S
1.0
- New option to re-order buttons
0.7 alpha
- New option to select Menu and/or Search button to show
- Restart SystemUI process to apply changes immediately
0.5 alpha
- Initial version
.
install failed
TheC92 said:
install failed
Click to expand...
Click to collapse
Re-uploaded and fixed MD5 issue. Please refresh and try again. Thanks for letting me know. :good:
Hi Dev good job, works fine on my Xperia ZL with stock based custom rom... It would be better if I can change the position of the elements or choose which elements add to nav bar...do u think it is possible in future? Many thanks
Sent from my C6503 using XDA Premium 4 mobile app
Is this how its supposed to look?
Sent from my MUCH i5s using xda app-developers app
cikoxda said:
Hi Dev good job, works fine on my Xperia ZL with stock based custom rom... It would be better if I can change the position of the elements or choose which elements add to nav bar...do u think it is possible in future? Many thanks
Sent from my C6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I'm planning more in the future. Go see post #2.
iRhyiku said:
Is this how its supposed to look?
Sent from my MUCH i5s using xda app-developers app
Click to expand...
Click to collapse
The recent apps button is missing which is supposed to be in the middle. You can see a sample in the OP. Can you post your Xposed log here?
Xperia SP
Works great in Xperia SP ExistenZ 3.3.0
itandy said:
Yes, I'm planning more in the future. Go see post #2.
Click to expand...
Click to collapse
OMG I had not seen it...thank you
itandy said:
The recent apps button is missing which is supposed to be in the middle. You can see a sample in the OP. Can you post your Xposed log here?
Click to expand...
Click to collapse
Oh that makes sence actually. For some reason my ROM (Stock-which is a slightly modified AOSP on my MUCH i5s) disabled and hid the Recents button from the navbar leaving a gap on the right, I was hoping this would solve that issue. Well thanks anyway, I will keep this modual enabled as I do like the looks of the navbar now rather than just two buttons
But if there was a way to enable it or have something in it's place to do the same thing, i would love to know.
Thank you!
Image of search button does not change in SoftkeyZ app. However, module very good!
나의 Nexus 7 의 Tapatalk에서 보냄
TheC92 said:
Image of search button does not change in SoftkeyZ app. However, module very good! View attachment 2692948
나의 Nexus 7 의 Tapatalk에서 보냄
Click to expand...
Click to collapse
Glad that it works on N7. I may add support for custom image in the future.
iRhyiku said:
Oh that makes sence actually. For some reason my ROM (Stock-which is a slightly modified AOSP on my MUCH i5s) disabled and hid the Recents button from the navbar leaving a gap on the right, I was hoping this would solve that issue. Well thanks anyway, I will keep this modual enabled as I do like the looks of the navbar now rather than just two buttons
But if there was a way to enable it or have something in it's place to do the same thing, i would love to know.
Thank you!
Click to expand...
Click to collapse
Please try this test build. You may like to test it in different orientation (portrait, landscape) and different modes. Some apps turns the buttons into small dots in fullscreen mode, such as camera. There may still be bugs. :silly:
Doesn't seem to change anything
Though when on landscape mode I so have this bug, it does nothing if pressed but if held it opens search.
Sent from my MUCH i5s using xda app-developers app
iRhyiku said:
Doesn't seem to change anything
Though when on landscape mode I so have this bug, it does nothing if pressed but if held it opens search.
View attachment 2693159
Sent from my MUCH i5s using xda app-developers app
Click to expand...
Click to collapse
So it's more complicated than I thought. If you can send me the info needed (check post #1), I can look at the source and fix it.
cool, very good
Hi, this module is beta 10 but I have no problem with the App. Although I expect more updates such as if you could add buttons allow you want, Of course also the order. I just want 4 button. Return home, and recent menu so hopefully no more and add an interface, still thank you for all your contributions so far.
chalofito said:
Hi, this module is beta 10 but I have no problem with the App. Although I expect more updates such as if you could add buttons allow you want, Of course also the order. I just want 4 button. Return home, and recent menu so hopefully no more and add an interface, still thank you for all your contributions so far.
Click to expand...
Click to collapse
Do you mind telling me what device and ROM are you using?
thaxxx
I'm using v4 ROM for Xperia ZL eXistenZ, sorry my bad english I'm Latino. But only appreciate the 4 basic buttons. - Back - Home - recent - menu. Regards
Just uploaded new version. Not sure how well the restart SystemUI function works. Please test it and let me know if there's any problem.
0.7 alpha
- New option to select Menu and/or Search button to show
- Restart SystemUI process to apply changes immediately
overflow:hidden;
AKA Remove Action Overflow Button
"Because naming your module after a CSS rule is fashionable and socially acceptable!"
A simple module that completely removes the action overflow button from various apps. Useful for people that have a hardware menu button on their device and don't want to see the superfluous button on action bars.
This is similar to another module: "Noverflow" by el1t. However, my implementation should be more thorough in removing the overflow button from sometimes-stingy apps, such as Google Chrome.
Only tested on 4.4 CM-based ROMs, but it should work on previous versions of Android (anything 4.0 ICS or newer should be okay), as well as ROMs that aren't CM-based. If not, let me know and I'll try to resolve the problem.
Thank you to GravityBox for originally implementing the important lines of code!
Instructions:
Download, install, enable and reboot. No configuration interface included, nor is one necessary.
Changelog:
Code:
v1.0:
Initial release
v1.1:
- Removed overflow button in AOSP calculator app (thanks, Micks29!)
- Added try/catch blocks for safety
- Bumped up minSdkVersion to 14 (will change if I can make older Android versions compatible)
- Minor addition to app description string
v1.2:
- New name and icon!
- Only attempt to hook methods if user's version of Android has original methods properly implemented
v1.3:
- Removed overflow button in AOSP browser app (thanks, a4apple!)
- General project clean-up (APK file size has been significantly reduced and leftovers from previous project name have been purged)
- Compile project based on Java 1.7 to make use of some handy new development techniques
- Added TODO notes within project's source to inform anyone interested in my pending tasks
v1.4:
- Ensure the overflow button in AOSP browser app is correctly being removed
- Change a few fields to help prevent the overflow button from being shown in some apps, in some cases
- Use the latest Xposed API (d'oh!)
v1.41:
- Found and removed yet another instance of the overflow button in the AOSP browser app
Download:
http://repo.xposed.info/module/me.jjohnson1988.android.xposed.removeactionoverflowbutton
Source:
https://github.com/JJohnson1988/overflow-hidden
@JJohnson1988 can u implement gingerbread support plz?
killoid said:
@JJohnson1988 can u implement gingerbread support plz?
Click to expand...
Click to collapse
I thought Google forced the overflow button in Android versions that came /after/ Gingerbread. And I also forgot that a back-port of Xposed for Gingerbread even exists.
I can lower the minimum required version of the module, but if that doesn't work for you, I'll try to implement a workaround.
Sent from my SAMSUNG-SGH-I747
On second thought, I don't think lowering the minimum SDK version would help. Here's what I found out:
Google didn't implement the necessary classes that the module hooks into until 4.0 ICS (for one of the hooks) and 4.1 JB (for the other hook). So whatever apps you're using on 2.3 GB must have their own non-standardized implementations to display the overflow button.
Which apps in particular are you having trouble with?
JJohnson1988 said:
On second thought, I don't think lowering the minimum SDK version would help. Here's what I found out:
Google didn't implement the necessary classes that the module hooks into until 4.0 ICS (for one of the hooks) and 4.1 JB (for the other hook). So whatever apps you're using on 2.3 GB must have their own non-standardized implementations to display the overflow button.
Which apps in particular are you having trouble with?
Click to expand...
Click to collapse
in telegram messenger. i contacted them to include an option to remove that menu button if one's device has a hardware menu button. still didn't get that,so i thought this module might help.
Thanks for the info. I'll look into it for you.
You may be in luck.
Certain action bar features are able to work in older Android versions due to a support library, and I'm pretty positive Telegram Messenger uses ActionBarSherlock to obtain this compatibility.
http://actionbarsherlock.com/
It's pretty common, so I wouldn't be surprised. I'll find out for sure tomorrow.
I'm also going to experiment with Daniele Segato's v7 support library tomorrow as well.
https://github.com/danielesegato/android-support-library-archive/tree/master/v7/appcompat
It's possible to remove 3-dots button in calculator app please? :fingers-crossed:
Using Noverflow for now but 3-dots button in calculator app still here!
Micks29 said:
It's possible to remove 3-dots button in calculator app please? :fingers-crossed:
Using Noverflow for now but 3-dots button in calculator app still here!
Click to expand...
Click to collapse
Thanks. I'll look into that as well.
Let me know if there are any other base apps with the overflow button still visible.
Well, I couldn't sleep and decided to get my coding on.
v1.1 changelog:
- Removed overflow button in AOSP calculator app (thanks, Micks29!)
- Added try/catch blocks for safety
- Bumped up minSdkVersion to 14 (will change if I can make older Android versions compatible)
- Minor addition to app description string
Looks like you got your wish, Micks29!
Actually, do me a favor and test out the calculator app with v1.1. I'm pretty certain the button is removed now, but when I uninstalled the module to verify certain apps were again displaying the overflow button, the button that normally shows up in the calculator is still missing. Not that I'm complaining, but it's not the behavior I was expecting.
JJohnson1988 said:
Well, I couldn't sleep and decided to get my coding on.
v1.1 changelog:
- Removed overflow button in AOSP calculator app (thanks, Micks29!)
- Added try/catch blocks for safety
- Bumped up minSdkVersion to 14 (will change if I can make older Android versions compatible)
- Minor addition to app description string
Looks like you got your wish, Micks29!
Click to expand...
Click to collapse
Great thank a lot man ! Overflow button in Calculator app is gone !
I keep definitly your module, thanks again. :good:
JJohnson1988 said:
Actually, do me a favor and test out the calculator app with v1.1. I'm pretty certain the button is removed now, but when I uninstalled the module to verify certain apps were again displaying the overflow button, the button that normally shows up in the calculator is still missing. Not that I'm
complaining, but it's not the behavior I was expecting.
Click to expand...
Click to collapse
I just tried to disable mod, reboot and the overflow button is back so the behavior is ok for me.
What about a module name more short? R.A.O.B for example...anyway it's not a big deal
I think I just need sleep. That might explain everything.
As for a shorter name, I originally had "overflow:hidden;” in mind, based on the very useful CSS rule. But Android Studio gave me crap because of the colon and semicolon. Maybe I'll try again later?
Sent from my SAMSUNG-SGH-I747
Overflow Hidden sounds very good!
Good night
v1.2 changelog:
- New name and icon!
- Only attempt to hook methods if user's version of Android has original methods properly implemented
What do you guys think about the AOSP Clock and Phone apps? There are overflow buttons in those apps and the hardware menu button doesn't seem to do anything.
Do you think it would be tasteful and worthwhile to bind the menus to the hardware key instead and remove the overflow buttons? Or keep it the way it is?
JJohnson1988 said:
What do you guys think about the AOSP Clock and Phone apps? There are overflow buttons in those apps and the hardware menu button doesn't seem to do anything.
Do you think it would be tasteful and worthwhile to bind the menus to the hardware key instead and remove the overflow buttons? Or keep it the way it is?
Click to expand...
Click to collapse
Good idea for Clock app! But for Phone app I think that will be not esthetic to have a blank space on the right side relative to other buttons (call log & dialer buttons).
What if the keypad/phone icon took the position of where the overflow button was?
Sent from my SAMSUNG-SGH-I747
Hmm why not
JJohnson1988 said:
What do you guys think about the AOSP Clock and Phone apps? There are overflow buttons in those apps and the hardware menu button doesn't seem to do anything.
Do you think it would be tasteful and worthwhile to bind the menus to the hardware key instead and remove the overflow buttons? Or keep it the way it is?
Click to expand...
Click to collapse
hmm.... if we can have the option for that, it would be great. For me, I did use the overflow button on those apps. Can you please remove the overflow button on the aosp browser as well?
JJohnson1988 said:
What if the keypad/phone icon took the position of where the overflow button was?
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Not a bad idea!
I'll check out the browser. Thanks.
Sent from my SAMSUNG-SGH-I747
This Xposed module enables LG's knock code for Lollipop and Marshmallow devices . The knock code is highly customizable, from changing colours to visibility, error messages, background, etc. You can even hide the emergency button.
What's more, you can use codes to directly open specific shortcuts from the lockscreen, for example use 11212 to unlock, 221 to open WhatsApp, 111 for email, etc. These shortcuts don't have to be just apps, they can be anything on your device, like Direct Dial, open a specific Contact, etc. You even have the option to launch these shortcuts without unlocking the phone! (Requires App Settings Xposed, link available in app)
The module is pretty self explanatory, and will prompt you to set a pattern on the lock screen, because that is what it replaces. Other than that, there are no specific instructions to use it. Should the module or Xposed be disabled for any reason, your phone will still remain secure with that pattern.
Compatibility :
I personally test on CM13, and I will support CM12.0, CM12.1, AOSP 5.x and 6.0.x and derivatives. HTC support is limited unless I find a tester. Support for other OEM ROMs is absent beyond basic working functionality.
The only caveats are because of the way Xposed works.
A. Your code(s) will be visible to any one or any app on your device. No root required. The codes are stored encrypted, but anybody determined to get them will be able to, provided they can lay hands on your device. One way to avoid this is to disable USB debugging to prevent chances of a local exploit.
B. You need root to restart the keyguard after changing the full screen option. It is not mandatory, you could manually reboot if you require. All other changes will be reflected automatically, but not this one.
Tags (ignore) : knock lock screen exposed xposed xda tuesday unlock tap full screen fullscreen lockscreen shortcut custom quick launch pattern pin protected pinned authentication dual two factor rijul ahuja
XDA:DevDB Information
KnockCode Lockscreen, Xposed for all devices (see above for details)
Contributors
Rijul.A, MohammadAG
Xposed Package Name: me.rijul.knockcode
Version Information
Status: Abandoned
Current Stable Version: 1.3.0
Stable Release Date: 2016-03-25
Created 2015-12-17
Last Updated 2017-08-15
Reserved
FAQ
Does this work with screen off?
No, that is device specific and I can't implement it without having a device in hand, and even then, it is beyond my abilities.
Module does not work at all
Give me logcat, SystemUI.apk or any other lockscreen.apk which your device uses, I will try to implement it.
Some features, particularly emergency button related, do not work
Give me logcat, SystemUI.apk or any other lockscreen.apk which your device uses, I will try to fix it, but if it gets too difficult to manage because of your OEM ROM, it will not be done.
I am stuck on the lock screen, please help!
Long press the buttons 5 times. Your stock pattern will be restored.
I would like to contribute
Thanks! File a pull request on Github
I would like to contribute by translating your app and I can work with Github
Thanks! File a pull request
I would like to contribute by translating your app and I don't know Github
Thanks! Download the strings.xml file from here and translate away. Upload the contents on hastebin and send me the link with the language.
CM / HTC / Xperia / TouchWiz support?
Works on some HTC, Xperia and TouchWiz devices and not all features work properly.
CM is supported before 20th June nightly I believe.
Reserved
Screenshots
Knock Code Entry
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Custom shortcut selection
Some settings
More screenshots
Changelog
1.3.1
If you didn't previously update to 1.3.0, please uninstall your old version before updating.
- Better colour handling for dots
- Bugfix from incorrect dots implementation
1.3.0
Please uninstall app, it has been entirely remade from scratch
- Size reduction
- Add option to launch shortcut without unlocking
- Add dots animation
- Translations removed
Older versions
1.2.5
Please clear data of app because of new shortcut scheme
- Module now prompts for pattern if unset
- MOAR shortcuts (thanks @ CyanogenMod)
- Cosmetic changes
- Fix crash if launcher icon was hidden
1.2.4
- Fix custom shortcuts bug
1.2.3
- Added margin b/w dots and lines on lock screen
- You can now add other knock codes to launch apps directly (A la PIN/Pattern Shortcuts Xposed)
- Translation changes
- Long pressing the knock code in activities will now reset it
1.2.2
- Translations (Polish by pantinPL, Mexican Spanish by Alan Yadir)
- Attempted to remove lag while locking and unlocking
- Animate the view when unlocking (not the old green animations, but from AOSP)
- If knock code is never set, module will not replace pattern even if switch is on
- Disabling emergency button in MainActivity will disable option below it
1.2.1
- HTC
- Translation update
1.2.0
- Failsafe option
- Size reduction
1.1.8 (Beta)
- Attempted HTC compatibility, but no testers.
1.1.7
- Bugfix to prevent device lockout when too many incorrect attempts too many times
1.1.6
- Reimplemented KnockCode with buttons, faster now - ripple taps are now confined to boxes
- Added Brazilian Portuguese translations by Gabriel Campos
- Fixed issue with dots view where incorrect mode would still allow dots to be entered.
1.1.5
- Added red colour animation when pattern incorrect
- Fixed a hook so unlocking should be smoother now
1.1.4
- Issues with dots view fixed by using AOSP implementation (if you had issues with v1.1.3, this should fix it)
- Changed tap rectangle to material ripple
1.1.3
Fixed possible ANRs
Added dots view on lock screen (with animations Ooooooo)
1.1.2
Fixed issue with 5.0.x hooks
1.1.1
Minor bugfixes
1.1.0
You will need to enable the module from UI after install
- Xperia issue fixed (if version 1.0.7 produced an issue with you, it should work now)
- Module on/off switch ((thanks @Maxr1998)
- Hide module from launcher (thanks @Maxr1998)
- Change pattern size
- Hide emergency button text but keep button
- Vibration settings
- Module active checker (thanks @Maxr1998)
1.0.7
Marshmallow users will need to delete old version
Implemented emergency button
1.0.6.2
Working Marshmallow support, finally
1.0.6.1
- Improved Marshmallow support
- Fix a bug where module would prevent non pattern lock screens from loading
1.0.6
- Attempted Marshmallow compatibility
- Tried to increase the Lollipop success rate
Older versions
- Overhauled UI, added Lollipop compatibility, removed backward comptability (v1.0.5)
- MohammadAG's release (v1.0.4)
Please ignore this post
Tags : gesture lock screen exposed xposed xda tuesday unlock draw swipe full screen fullscreen lockscreen shortcut custom quick launch pattern pin protected pinned authentication dual two factor rijul ahuja
Whats the effect of this module on battery? I think this is like doubletap2wake function which is a real battery drainer.
Sent from my Nexus 5 using Tapatalk
Didn't work when i enabled the module, chnaged the password and rebooted. Had to uninstall xposed framework, uninstall your app, then re-install xposed. Anything I'm doing wrong with how to enabke the module? I have a galaxy s5 with cm12.1 nightlys.
pradhyu69 said:
Whats the effect of this module on battery? I think this is like doubletap2wake function which is a real battery drainer.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
DT2W is a real battery drain on Nexus 5, obviously due to digitizer and panel being powered together opposed to say an HTC M8/M7 or LG G3/G4 where they are powered separately and natively support DT2W. Your Nexus 5 was never designed with this in mind. DT2W is not a battery drainer. Your hardware just wasn't meant to do this.
N
I tried this module, and after restart my phone stuck at lock screen.. I tried the default pattern to unlock but nothing happened..
Please someone help me out
Benrap said:
Didn't work when i enabled the module, chnaged the password and rebooted. Had to uninstall xposed framework, uninstall your app, then re-install xposed. Anything I'm doing wrong with how to enabke the module? I have a galaxy s5 with cm12.1 nightlys.
Click to expand...
Click to collapse
You need to set up a 3x3 pattern in your default settings. My module checks if it is active, and then overrides it with the knock code. This is done so that there is a fallback pattern lock screen if/when Xposed is disabled for any reason. If it still doesn't work, please give me your Xposed logs. I will try to fix it. I am using the nightlies too!
pradhyu69 said:
Whats the effect of this module on battery? I think this is like doubletap2wake function which is a real battery drainer.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This module only works while screen on, and therefore, is not the kind of battery drainer that you are taking about.
Dhaval2904 said:
I tried this module, and after restart my phone is stuck at lock screen.. I tried the default pattern to unlock but nothing happens.. Please someone help me out
Click to expand...
Click to collapse
Hi, sorry to hear that Dhaval. You should boot into recovery, go to advanced -> file manager -> delete /data/app/me.rijul.knockcode-*/base.apk. Alternatively, you could disable Xposed if you have a flashable ZIP available.
While you're at it, could you get me a logcat (when your phone is on)
Code:
adb logcat *:E > logcat.txt
Dhaval2904 said:
I tried this module, and after restart my phone is stuck at lock screen.. I tried the default pattern to unlock but nothing happens..
Please someone help me out
Click to expand...
Click to collapse
I also got this problem too.
because I still don't have any pattern lock or pin lock (just swipe)
then I disable Xposed and config Pattern lock in 3x3 (as dev said)
then enable module and reboot again.
now it's work like a charm.
good luck.
Hi, you're right. I tried it myself to see that there is some error which occurs, I'll fix it tonight after I get home. Thank you for identifying it.
I use a CM12.1 based ROM (SaberMod) for my Galaxy S4 and installed your new knock module.
I followed the suggestions (first set a 3x3 pattern, then enabled the module, restart the phone, unlock with default pattern and then set an own pattern) - and everything works
The only thing which is somehow strange is the following:
- I switch off the screen
- I switch the screen on again - the lock screen is visible
- I have to swipe up - an empty screen (only background) is shown
- now I can "knock" to unlock
Is that additional "swipe up" - step normal?
BTW, I'm using the lightning launcher if that matters...
Awesome for someone to take on this project forward! (Since MohammadAG is great at making new modules but terrible at mantaining any of them, or even replying)
It would be awesome if at the end, you talked with some kernel dev that permited Double tap to wake or such and combine efforts for screen-off knock code
Also, could the grid be expanded? 2x2 is small, it would be cool if we could change it to 3x3, 4x4, etc
Thanks a lot!
--
Edit: Tested it on Stock N5 6.0.1 and it blocks you right past the lock screen (knock code lockscreen): after it, a black screen and wallpaper changes to original M wallpaper and lockscreen is shown again and again. Need to disable the module to be able to go past the lockscreen again (and so lost the xposed log for that moment) .
Yes, I had 3x3 pattern lockscreen when activating the module. And the knock code lockscreen appears, but again and again on a loop.
RusherDude said:
Awesome for someone to take on this project forward! (Since MohammadAG is great at making new modules but terrible at mantaining any of them, or even replying)
It would be awesome if at the end, you talked with some kernel dev that permited Double tap to wake or such and combine efforts for screen-off knock code
Also, could the grid be expanded? 2x2 is small, it would be cool if we could change it to 3x3, 4x4, etc
Thanks a lot!
--
Edit: Tested it on Stock N5 6.0.1 and it blocks you right past the lock screen (knock code lockscreen): after it, a black screen and wallpaper changes to original M wallpaper and lockscreen is shown again and again. Need to disable the module to be able to go past the lockscreen again (and so lost the xposed log for that moment) .
Yes, I had 3x3 pattern lockscreen when activating the module. And the knock code lockscreen appears, but again and again on a loop.
Click to expand...
Click to collapse
For your first suggestion, you should refer to http://forum.xda-developers.com/nex...pp-hellscode-knockcode-mod-hellscore-t3135899
For second, yes, the size modification is on my to do list, but first is stability and compatibility.
If you could please use adb logcat *:E? I will try to fix this. I have not yet tested the module personally on Marshmallow, and support for it is very limited. I have been trying to install it on my device, but the build keeps failing. Thanks for feedback!
Bodenseematze said:
I use a CM12.1 based ROM (SaberMod) for my Galaxy S4 and installed your new knock module.
I followed the suggestions (first set a 3x3 pattern, then enabled the module, restart the phone, unlock with default pattern and then set an own pattern) - and everything works
The only thing which is somehow strange is the following:
- I switch off the screen
- I switch the screen on again - the lock screen is visible
- I have to swipe up - an empty screen (only background) is shown
- now I can "knock" to unlock
Is that additional "swipe up" - step normal?
BTW, I'm using the lightning launcher if that matters...
Click to expand...
Click to collapse
Yes, that is the expected behaviour. It emulates stock, wherein you swipe up the screen to show the pattern entry or the pin entry.
Bodenseematze said:
Is that additional "swipe up" - step normal?
BTW, I'm using the lightning launcher if that matters...
Click to expand...
Click to collapse
Yep it's normal, you can change it from stock settings>lockscreen>tick directly show pattern view.
======
Thanks OP the module working perfectly on my gt-n7100 unofficial cm12.1 rom by Ivan Meler. I wish I could unlock it even in a screen off state, just like LG devices
Dhaval2904 said:
I tried this module, and after restart my phone stuck at lock screen.. I tried the default pattern to unlock but nothing happened..
Please someone help me out
Click to expand...
Click to collapse
aillez said:
I also got this problem too.
because I still don't have any pattern lock or pin lock (just swipe)
then I disable Xposed and config Pattern lock in 3x3 (as dev said)
then enable module and reboot again.
now it's work like a charm.
good luck.
Click to expand...
Click to collapse
RusherDude said:
Awesome for someone to take on this project forward! (Since MohammadAG is great at making new modules but terrible at mantaining any of them, or even replying)
It would be awesome if at the end, you talked with some kernel dev that permited Double tap to wake or such and combine efforts for screen-off knock code
Also, could the grid be expanded? 2x2 is small, it would be cool if we could change it to 3x3, 4x4, etc
Thanks a lot!
--
Edit: Tested it on Stock N5 6.0.1 and it blocks you right past the lock screen (knock code lockscreen): after it, a black screen and wallpaper changes to original M wallpaper and lockscreen is shown again and again. Need to disable the module to be able to go past the lockscreen again (and so lost the xposed log for that moment) .
Yes, I had 3x3 pattern lockscreen when activating the module. And the knock code lockscreen appears, but again and again on a loop.
Click to expand...
Click to collapse
Hello, I have updated the module to allow users to set a pattern (that is, allows to use non pattern screen) after it has been activated. So silly of me to have done that wrongly - MohammadAG's ways were very well thought out. Could you please test again?
@RusherDude, I think that this process should also enhance Marshmallow compatibility, but I can not be too sure. If you would test it again, I will gladly work on it further. But I have started a MM ROM download anyway, so you can wait for me to vouch for the module too. Please provide logs if you end up testing.
Thanks for your valuable feedback!
Works well on Z3 5.1.1 with smart lock
Rijul.A said:
For your first suggestion, you should refer to http://forum.xda-developers.com/nex...pp-hellscode-knockcode-mod-hellscore-t3135899
For second, yes, the size modification is on my to do list, but first is stability and compatibility.
If you could please use adb logcat *:E? I will try to fix this. I have not yet tested the module personally on Marshmallow, and support for it is very limited. I have been trying to install it on my device, but the build keeps failing. Thanks for feedback!
Click to expand...
Click to collapse
Thanks for the fast answer! I will try logcat when Im back home. Also that post you linked, will investigate it, thanks!
Rijul.A said:
Hello, I have updated the module to allow users to set a pattern (that is, allows to use non pattern screen) after it has been activated. So silly of me to have done that wrongly - MohammadAG's ways were very well thought out. Could you please test again?
@RusherDude, I think that this process should also enhance Marshmallow compatibility, but I can not be too sure. If you would test it again, I will gladly work on it further. But I have started a MM ROM download anyway, so you can wait for me to vouch for the module too. Please provide logs if you end up testing.
Thanks for your valuable feedback!
Click to expand...
Click to collapse
Nothing is fixed on this version yet unfortunately, same error. A detail I didn't say before tho:
- The knock code only awaits for FIVE touches (my password had 5 touches too, maybe just that?), after that the black screen comes and..
- If the code was OK, the lockscreen appears again but you maintain your wallpaper.
- If the code was not OK, the lockscreen appears again but the background turns to the stock marshmallow one (the one in the dev preview).
That may help you or not, not sure tho. Ill try to help if im able later.
thanks!
I have been using POCO F1 for about two months now, and I was using Honor 6x in which I have cool fingerprint gestures such as toggle notifications and also in some phones the applications like PayPal, Gpay and Paytm would recognise and utilise fingerprint as a method of logging in. But in Poco I am unable to use the fingerprint for any other purposes other than unlocking the device and also the UI is little dull (my experience with EMUI was excellent), is there any way to have EMUI based custom ROM for this inconvenience or any other method to use the above things without third party applications. I also used third-party applications, but if I use a third-party application, the fingerprint is not registering more than one finger. Please help thanks in advance.
OEMs like Oneplus and Xiaomi have disabled the two APIs needed for this on their ROMs for security purposes. You might not find any luck from custom ROMs either because this is disabled by default. Also, ever since 9.0, Android doesn't allow to listen to background action for these APIs from apps either so Huawei's EMUI is amongst the very limited choices you have.
Nyuubi said:
OEMs like Oneplus and Xiaomi have disabled the two APIs needed for this on their ROMs for security purposes. You might not find any luck from custom ROMs either because this is disabled by default. Also, ever since 9.0, Android doesn't allow to listen to background action for these APIs from apps either so Huawei's EMUI is amongst the very limited choices you have.
Click to expand...
Click to collapse
are the three os you specified, have customisations and are those as customisable and fun to have as the EMUI?
huntersreeni said:
are the three os you specified, have customization and are those as customizable and fun to have as the EMUI?
Click to expand...
Click to collapse
That's my signature listing all my previous/current devices. Lineage OS is pretty good in terms of performance and battery but is pretty bland in terms of customs go for ROMs like crDroid if customization is your main priority.