Module adds WIFi SSID next to Clock in status bar.
Screenshot, how it looks: http://oi58.tinypic.com/2eoef55.jpg
Download here: http://repo.xposed.info/module/com.pyler.xssidindicator
Thanks, great
Sent from my tablet. Odoslané z môjho tabletu.
It works but it has some incompability with the xposedstatustext module ,since it doesnt adapt the color
supergonkas said:
It works but it has some incompability with the xposedstatustext module ,since it doesnt adapt the color
Click to expand...
Click to collapse
Why you quoting me?
Ja_som said:
Why you quoting me?
Click to expand...
Click to collapse
it was derp, i pressed the wrong reply button xD
This is exactly what I want
Thanks very much，I have too many wifi signal around me，I really want to know which one i am using easily.
it seems suitable for tablet which has more space the notificationbar，if there could be some option to change the font size or ssid displaying localtion and something else will much helpful for smaller screen
Can someone post a screenshot of this? Link in OP is not working.
norml said:
Can someone post a screenshot of this? Link in OP is not working.
Click to expand...
Click to collapse
For me is working, and another screenshot is in my post #2
Ja_som said:
For me is working, and another screenshot is in my post #2
Click to expand...
Click to collapse
Thanks
Nice module, but why it has 1MB size?
Sent from SGNII using Tapatalk Pro 4.5.2
@_jis_: I see 262.5 KB, not 1 MB
@reginofchaos: in new update, I added function to wrap SSID if is longer than 7 chars to just 6 chars (so if you wifi ssid is "myverynicewifi", then it will show "myvery". I think you still recognize on which Wifi you are connected.
@supergonkas: sorry, I will not fix. You should decide which one you will use.
for all: thank your for your support
pyler said:
@_jis_: I see 262.5 KB, not 1 MB
@reginofchaos: in new update, I added function to wrap SSID if is longer than 7 chars to just 6 chars (so if you wifi ssid is "myverynicewifi", then it will show "myvery". I think you still recognize on which Wifi you are connected.
@supergonkas: sorry, I will not fix. You should decide which one you will use.
for all: thank your for your support
Click to expand...
Click to collapse
May be even a smaller length and size option.
Sent from my SM-G900T using Tapatalk
pyler said:
@_jis_: I see 262.5 KB, not 1 MB
Click to expand...
Click to collapse
It is not about apk archive packed size, but about App info real size. It is 0.98MB. This is the space your app occupy after installation.
Just one file classes.dex has 673KB.
Sent from SGNII using Tapatalk Pro 4.5.2
Love the module, great job on it!
However, I do have a request; Could you change the way the indicator is placed? It does what it says it does(place the wifi network next to the clock), and that is immediately the issue here. I have my clock centered, with another module. and like it said it does, the SSID now also is centered.
Would be great if this could be taken into account.
_jis_ said:
It is not about apk archive packed size, but about App info real size. It is 0.98MB. This is the space your app occupy after installation.
Just one file classes.dex has 673KB.
Sent from SGNII using Tapatalk Pro 4.5.2
Click to expand...
Click to collapse
I probably cant help you Well, if app is too big for you, dont use it. I dont know why it is 1 MB in device when APK is less than 300 KB.
WesleySmalls said:
Love the module, great job on it!
However, I do have a request; Could you change the way the indicator is placed? It does what it says it does(place the wifi network next to the clock), and that is immediately the issue here. I have my clock centered, with another module. and like it said it does, the SSID now also is centered.
Would be great if this could be taken into account.
Click to expand...
Click to collapse
Module hooks clock updating so it is not possible. It will always be next to clock.
pyler said:
I dont know why it is 1 MB in device when APK is less than 300 KB.
Click to expand...
Click to collapse
See the attached snapshot as proof of it.
Here is the answer:
http://stackoverflow.com/questions/...device-differ-than-the-apk-or-play-store-size
Try to use ProGuard.
pyler said:
Well, if app is too big for you, dont use it.
Click to expand...
Click to collapse
More than size bothers me the errors in the debug log:
Code:
-----------------
17.4.2014 17:39:43 UTC
Loading Xposed v47 (for Zygote)...
Running ROM 'JZO54K.N7100XXDME6' with fingerprint 'samsung/t03gxx/t03g:4.1.2/JZO54K/N7100XXDME6:user/release-keys'
Loading modules from /data/app/hk.valenta.completeactionplus-1.apk
Loading class hk.valenta.completeactionplus.XCompleteActionPlus
Loading modules from /data/app/uk.co.villainrom.pulser.fivebyfourlauncher-1.apk
Loading class uk.co.villainrom.pulser.fivebyfourlauncher.FiveByFourLauncher
Loading modules from /data/app/com.ugglynoodle.allnotificationsexpanded-1.apk
Loading class com.ugglynoodle.allnotificationsexpanded.AllNotificationsExpanded
Loading modules from /data/app/de.robv.android.xposed.mods.appsettings-2.apk
Loading class de.robv.android.xposed.mods.appsettings.XposedMod
Loading modules from /data/app/com.germainz.crappalinks-2.apk
Loading class com.germainz.crappalinks.CrappaLinks
Loading modules from /data/app/com.greenbattery-1.apk
Loading class com.dully79.xposed.mods.batteryreplacement.BatteryReplacement
Loading modules from /data/app/com.oasisfeng.greenify-2.apk
Loading class com.oasisfeng.greenify.pro.FrameworkPatch
Loading class com.oasisfeng.greenify.pro.SettingsPatch
Loading modules from /data/app/pk.qwerty12.playstorelinkinappinfo-1.apk
Loading class pk.qwerty12.playstorelinkinappinfo.PlayStoreLinkInAppInfo
Loading modules from /data/app/com.pyler.xssidindicator-2.apk
Loading class com.pyler.xssidindicator.XSSIDIndicator
Loading modules from /data/app/com.mohammadag.burnttoast-2.apk
Loading class com.mohammadag.burnttoast.XposedMod
Loading modules from /data/app/com.germainz.activityforcenewtask-2.apk
Loading class com.germainz.activityforcenewtask.XposedMod
Loading modules from /data/app/com.germainz.stopswitchdelay-2.apk
Loading class com.germainz.stopswitchdelay.XposedMod
Loading modules from /data/app/com.mohammadag.smoothsystemprogressbars-2.apk
Loading class com.mohammadag.smoothsystemprogressbars.SmoothSystemPBar
Loading modules from /data/app/ma.wanam.youtubeadaway-2.apk
Loading class ma.wanam.youtubeadaway.Xposed
Loading modules from /data/app/ind.fem.black.rayyan.xposed.gesturenavigation-1.apk
Loading class ind.fem.black.rayyan.xposed.gesturenavigation.Ray
java.lang.NullPointerException
at com.pyler.xssidindicator.XSSIDIndicator$1.afterHookedMethod(XSSIDIndicator.java:29)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:654)
at com.android.systemui.statusbar.policy.Clock.updateClock(Native Method)
at com.android.systemui.statusbar.policy.Clock.onAttachedToWindow(Clock.java:136)
at android.view.View.dispatchAttachedToWindow(View.java:12064)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2714)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2714)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2714)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2714)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1339)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1131)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:4611)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:725)
at android.view.Choreographer.doCallbacks(Choreographer.java:555)
at android.view.Choreographer.doFrame(Choreographer.java:525)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:711)
at android.os.Handler.handleCallback(Handler.java:615)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4898)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1008)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:775)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:133)
at dalvik.system.NativeStart.main(Native Method)
java.lang.NullPointerException
at com.pyler.xssidindicator.XSSIDIndicator$1.afterHookedMethod(XSSIDIndicator.java:29)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:654)
at com.android.systemui.statusbar.policy.Clock.updateClock(Native Method)
at com.android.systemui.statusbar.policy.Clock.onAttachedToWindow(Clock.java:136)
at android.view.View.dispatchAttachedToWindow(View.java:12064)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2714)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2714)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2714)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2714)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1339)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1131)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:4611)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:725)
at android.view.Choreographer.doCallbacks(Choreographer.java:555)
at android.view.Choreographer.doFrame(Choreographer.java:525)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:711)
at android.os.Handler.handleCallback(Handler.java:615)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4898)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1008)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:775)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:133)
at dalvik.system.NativeStart.main(Native Method)
love the idea but the mod also change the size of clock in the notification panel
possible to retain the original size?
momomok said:
love the idea but the mod also change the size of clock in the notification panel
possible to retain the original size?
View attachment 2693512
Click to expand...
Click to collapse
momomok, sadly, no yet. i have no idea what needs to be hooked.
Released new version!
- you can set maximal length of WiFi SSID in status bar! Everytime you change it, please restart your device.
Download in Xposed repo!
XSSID Indicator
It is cool and nice app.
But there is a small issue
When I change the color of the module called "clockcolorchanger", this can change the color of the "XSSID Indicator"
Please fix it...
mohjab12 said:
It is cool and nice app.
But there is a small issue
When I change the color of the module called "clockcolorchanger", this can change the color of the "XSSID Indicator"
Please fix it...
Click to expand...
Click to collapse
That is not possible. We are using (hooking) some "thing".
Related
Not sure if you want the stock Android 4.4 launcher on your Ultra... but we all like tinkering right??? Ok so here it is, and the tutorial...
Requirements:
Make a BACKUP!
Download:
LINK
Instructions:
1. Download the zip from the link above
2. Extract the zip and place the apks on internal/ external SD
3a. Install PrebuiltGmsCore.apk
3b. Install Velvet.apk
3c. Install GoogleHome.apk
4, Press home button, then select your new launcher
Done...
Issues:
Camera - photosphere not working
F/C - switch language, then back to English US/UK
By me doesnt work geht this in my logcat:
2013-11-01 12:57:59.057 E 9925/AndroidRuntime: FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.googlequicksearchbox/com.google.android.launcher.GEL}: java.lang.UnsupportedOperationException: Can't convert to dimension: type=0x12
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2071)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2096)
at android.app.ActivityThread.access$600(ActivityThread.java:138)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1207)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:213)
at android.app.ActivityThread.main(ActivityThread.java:4787)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:809)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:576)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.UnsupportedOperationException: Can't convert to dimension: type=0x12
at android.content.res.TypedArray.getDimensionPixelSize(TypedArray.java:463)
at android.view.ViewGroup$MarginLayoutParams.(ViewGroup.java:5729)
at android.widget.LinearLayout$LayoutParams.(LinearLayout.java:1867)
at android.widget.LinearLayout.generateLayoutParams(LinearLayout.java:1779)
at android.widget.LinearLayout.generateLayoutParams(LinearLayout.java:62)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:748)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
at com.android.internal.policy.impl.PhoneWindow.generateLayout(PhoneWindow.java)
at com.android.internal.policy.impl.PhoneWindow.installDecor(PhoneWindow.java)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java)
at android.app.Activity.setContentView(Activity.java:1867)
at com.android.launcher3.Launcher.onCreate(Launcher.java:428)
at com.google.android.launcher.GEL.onCreate(GEL.java:81)
at android.app.Activity.performCreate(Activity.java:5008)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2035)
... 11 more
Gesendet von meinem LT25i mit Tapatalk Pro
Thanks!! I tried it and it works well but the icons look oversized. The icons in the app draw look huge!! Ill let someone else tinker so it looks crisp.
Sent from my C6802 using Tapatalk 4
I didn't use the contents from the ZIP yesterday and i didn't have any issues. What's it for? Either way, i really like this launcher, but the app drawer icons are HUGE and it looks messy. Also, no way to hide apps, which makes it even messier. I think i'll wait for Nova Launcher to be updated to 4.4.
For me....any time I exit an app with the home button my keyboard pops up for no reason!
I'm on Carbon....which might be why/
Search closes every time I use it.
yeah for a screen like ours, its probably not the best 'stock' launcher.
TREMER said:
For me....any time I exit an app with the home button my keyboard pops up for no reason!
I'm on Carbon....which might be why/
Click to expand...
Click to collapse
Yup, same here. Search and everything else works fine though.
Sent from my C6833 using XDA Premium 4 mobile app
Fixed force close. Switched to English UK, did a search, then switched back to English US. No further problem.
Launcher looks pretty good if you force 720p the only thing that changes it the app tray icon ?
NEW! Navbar button issue appears to have been resolved.
This is my first go at an Xposed module, or any Android app for that matter, so wish me luck!
Intro:
Anyway, I was using a lot of Xposed mods that were cool, but my IT policy has the lockscreen set to pin or password and none of the bypasses around quite gave me what I wanted. LucasR93 created this really nice mod for those of you that really like just a sliding lock on your screen, but I really wanted to use the fantastic NFCSecure Lockscreen, which works best with no lockscreen enabled at all. (PS. you guys should check out NFCSecure, it's so much easier than even a pattern! And the developer is pretty responsive, open to any suggestions you have. *this spot is not paid for by the developer of the app. I just really like it that much*)
So, I made my own mod.
What it does:
The mod utilizes the Xposed Framework to find the KeyguardViewMediator class and hook the doKeyguardLocked method, completely mocking it out. Therefore, any time the system tries to lock the screen it'll just go down the memory hole, and do nothing. Thus, even if you have a device policy mandating a pin/password the phone will never lock, ever.
This works like the aforementioned mod by LucasR93, in that it doesn't touch the actual lock policy or setup; if you go into your settings, to the security section, you will see all of the settings as normal. Nothing that needs the pin/password will complain because as far as they know it works just fine. This is (IMHO) much safer than attacking the policy and security parts of the OS directly, as they could open some more serious vulnerabilities.
What devices this mod works on:
I only have a Droid MAXX running 4.4 right now, but the way the code is implemented it should be able to work on anything 4.0+ and AOSPish, as long as Xposed Framework works properly.
Nexus 4 and Nexus 5 reported working, KitKat stock and ParanoidAndroid ROM.
I'd like to formally request anyone running Xposed on 4.0-4.3 to test this and give feedback as to if it works on these devices.
I am using some of the info provided to LucasR93 to try to also add support for the HTC lockscreen but I'll need some HTC testers for that one.
Installation Instructions:
Ensure that the Xposed Framework (a.k.a. Xposed Installer) is installed and properly functioning on your device.
Go to the Download section of the Xposed Installer, or here, to find the Complete Keyguard Disabler. Check the box in the Xposed Installer Modules list, and reboot the phone.
Upon reboot, you may or may not see your lockscreen. Some devices (Nexus devices it seems) show the lockscreen on boot, but never again. Some devices (Droid line, possibly Moto X) are completely unlocked upon reboot.
Every time your phone would normally lock, a log entry will be written to the Xposed log "Not locking the screen".
If it doesn't work:
Uncheck all other Xposed modules. Reboot. If it still doesn't work, copy the logs from the Xposed Installer and post them in this thread, with your phone model and Android version, and I'll try to help.
This new experimental build tries a few things, and logs a LOT of things. Try it out.
Is this unsafe?
Actually, maybe. If you lose your phone you will be unable to lock it remotely by using Android Device Manager (or probably carrier/manufacturer/corporate specific device admins as well). You can, however, locate and wipe without issue.
I am pondering a way to detect the ADM lock and toggle the screen, but if you use this to get NFC lockscreens working it's not something you have to worry about.
Special Thanks: @rovo89, obviously, for the Xposed Framework. @LucasR93, for his initial app that gave me most of the inspiration for this.
Does not work on my S4
No relevant logs found to post :/
hamidoo said:
Does not work on my S4
No relevant logs found to post :/
Click to expand...
Click to collapse
OK, first, Samsungs are usually nowhere near aosp, but I could try to see if I could make it work.
Second, what version of Android are you running? And is it a stock or custom ROM?
Third, I know you said nothing is relevant in the logs, but if you could post what's there I'd know if my module even loaded.
It works on my nexus 4, but just partially.
As soon as the module is active and I chose anything else than no Lockscreen I'm getting a result as on the screenshot - no navigation keys
{
"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"
}
Gesendet von meinem Nexus 4
fabi280 said:
It works on my nexus 4, but just partially.
As soon as the module is active and I chose anything else than no Lockscreen I'm getting a result as on the screenshot - no navigation keys
View attachment 2515462
Gesendet von meinem Nexus 4
Click to expand...
Click to collapse
Oh?! That's really interesting. It appears you have the lockscreen navigation bar. That's, if I may be candid, pretty cool :silly:. Can I get the android version you're on? I can assume I know what the log says (although this will give a hint as to your version as well). I have capacitive navigation keys, so I did not see that one coming.
I'm on the latest Omni Rom build (14th January one, 4.4.2)
Gesendet von meinem Nexus 4
fabi280 said:
I'm on the latest Omni Rom build (14th January one, 4.4.2)
Gesendet von meinem Nexus 4
Click to expand...
Click to collapse
I'm working on it. Can you try something for me? Switch your keyguard to no lock (whatever got you the buttons) and reboot, then switch to a pin unlock and see if the mod works correctly.
No, I'm getting those buttons on every setting except on the No Lockscreen setting.
Upon reboot the buttons are there, until I press the standby button, then they are gone and it doesn't matter whether I go from pin to pattern/swipe or pattern to pin/swipe or swipe to pattern/pin. They only go back to normal after setting it to no Lockscreen.
Gesendet von meinem Nexus 4
fabi280 said:
No, I'm getting those buttons on every setting except on the No Lockscreen setting.
Upon reboot the buttons are there, until I press the standby button, then they are gone and it doesn't matter whether I go from pin to pattern/swipe or pattern to pin/swipe or swipe to pattern/pin. They only go back to normal after setting it to no Lockscreen.
Gesendet von meinem Nexus 4
Click to expand...
Click to collapse
OK, so to be clear, if you boot up the phone in "No Lockscreen" you have the normal buttons (Back, Home, Recents) but the instant you enable any lockscreen you get the lockscreen navigation bar buttons, correct? You do not have to do a reboot to get the buttons to break? That makes it more straightforward to fix, I believe, but it isn't as clean of a solution.
I had thought maybe it was giving you those buttons because on boot the phone tries to start in locked mode, which I thwart. But it appears as if every time the phone is "locked" the system updates the navigation bar buttons and also shows the keyguard. I'll look into nuking these functions, but I was hoping i could just nuke the call that sets them that way.
dtreth said:
OK, so to be clear, if you boot up the phone in "No Lockscreen" you have the normal buttons (Back, Home, Recents) but the instant you enable any lockscreen you get the lockscreen navigation bar buttons, correct? You do not have to do a reboot to get the buttons to break? That makes it more straightforward to fix, I believe, but it isn't as clean of a solution.
I had thought maybe it was giving you those buttons because on boot the phone tries to start in locked mode, which I thwart. But it appears as if every time the phone is "locked" the system updates the navigation bar buttons and also shows the keyguard. I'll look into nuking these functions, but I was hoping i could just nuke the call that sets them that way.
Click to expand...
Click to collapse
No, it doesn't matter which keyguard Mode i've set up before rebooting.
As soon as I am locking the phone I'm getting the Lockscreen navigation bar on unlocking again.
The only way to get back to normal is setting to no keyguard. And if I reboot without keyguard set, they don't switch to Lockscreen navigation bar after locking and unlocking.
Sorry English isn't my mother's tongue
Gesendet von meinem Nexus 4
fabi280 said:
No, it doesn't matter which keyguard Mode i've set up before rebooting.
As soon as I am locking the phone I'm getting the Lockscreen navigation bar on unlocking again.
The only way to get back to normal is setting to no keyguard. And if I reboot without keyguard set, they don't switch to Lockscreen navigation bar after locking and unlocking.
Sorry English isn't my mother's tongue
Gesendet von meinem Nexus 4
Click to expand...
Click to collapse
Don't apologize, I was getting very specific and you responded prefectly. Thanks. I'll get a new version uploaded later today, with some exploration code to uncover what's causing this.
fabi280 said:
No, it doesn't matter which keyguard Mode i've set up before rebooting.
As soon as I am locking the phone I'm getting the Lockscreen navigation bar on unlocking again.
The only way to get back to normal is setting to no keyguard. And if I reboot without keyguard set, they don't switch to Lockscreen navigation bar after locking and unlocking.
Sorry English isn't my mother's tongue
Gesendet von meinem Nexus 4
Click to expand...
Click to collapse
Try this new build. I will be updating the OP soon.
hamidoo said:
Does not work on my S4
No relevant logs found to post :/
Click to expand...
Click to collapse
Also try this new build. It has Experimental SUPERDEBUG enabled, which is just me looking for possible apks to hack on others' phones.
dtreth said:
Don't apologize, I was getting very specific and you responded prefectly. Thanks. I'll get a new version uploaded later today, with some exploration code to uncover what's causing this.
Click to expand...
Click to collapse
1. Downloaded your updated module
2. Activated it
3. Set a Pin (0000)
4. Reboot
5. It asked me for the pin the first time
6. Standby
7. Wake-Up: Lockscreen Navigation bar; No Pin
8. Sent the log to my computer
9. Reproduced 6 & 7 for 3 more times.
10. Set keyguard to no lock -> Standby -> Normal Nav Bar (not on the log anymore)
Code:
-----------------
15.01.2014 07:59:19 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-2.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard com.teamkang.fauxclock [SUPERDEBUG]
I doubt fauxclock could be a keyguard, it's a kernel setup tool.
Oh more logs:
Code:
-----------------
15.01.2014 07:59:19 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-2.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard com.teamkang.fauxclock [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
fabi280 said:
1. Downloaded your updated module
2. Activated it
3. Set a Pin (0000)
4. Reboot
5. It asked me for the pin the first time
6. Standby
7. Wake-Up: Lockscreen Navigation bar; No Pin
8. Sent the log to my computer
9. Reproduced 6 & 7 for 3 more times.
10. Set keyguard to no lock -> Standby -> Normal Nav Bar (not on the log anymore)
Code:
-----------------
15.01.2014 07:59:19 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-2.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard com.teamkang.fauxclock [SUPERDEBUG]
I doubt fauxclock could be a keyguard, it's a kernel setup tool.
Oh more logs:
Code:
-----------------
15.01.2014 07:59:19 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-2.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard com.teamkang.fauxclock [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
Click to expand...
Click to collapse
Yeah, thanks. The [SUPERDEBUG] lines are just searching any loaded package that has "lock" or "guard" in the name. I found the samsung lockscreen this way: "com.sec.android.app.keyguard".
I am currently trying out a new hook spot for the show lockscreen part, but I doubt it'll affect your issue. It does, however, make the hack work smoother on my phone. I'll push that one soon. I still need to do some more digging in the code to even find points to test, and it's slow goign when I have no soft nav to play with. I think I will just have to buy that nexus 7 after all :silly:. (Really waiting as long as I can for a new Nexus 10)
It's weird that the statusbar log message appears to function almost at the right time. I wish there was a KeyguardDispatchNavigationUpdate or something, that would make this easy.
I've got an idea. In the security settings there is something like automatically lock. If you set this value to not instant lock and the phone goes into standby by timeout you aren't asked for your pin.
So maybe you could override this value to like -1 or any other value it can't reach and link the powerbuttons standby to the timeout standby.
I'm not familiar with xposed module development, just did some heavy amount of Java coding for desktop/server applications... So this is just an idea, I'm unsure if it is doable.
If this would work fine it'd be an awesome solution for the VPN password requirements
Sent from my Nexus 4
fabi280 said:
I've got an idea. In the security settings there is something like automatically lock. If you set this value to not instant lock and the phone goes into standby by timeout you aren't asked for your pin.
So maybe you could override this value to like -1 or any other value it can't reach and link the powerbuttons standby to the timeout standby.
I'm not familiar with xposed module development, just did some heavy amount of Java coding for desktop/server applications... So this is just an idea, I'm unsure if it is doable.
If this would work fine it'd be an awesome solution for the VPN password requirements
Sent from my Nexus 4
Click to expand...
Click to collapse
Yes, you have a very good point, although I think the problem there is the system could still call the lockscreen through other means, like upon first boot. That's not something we really want. Well, I don't really want that, but I'll definitely look into that.
fabi280 said:
I've got an idea. In the security settings there is something like automatically lock. If you set this value to not instant lock and the phone goes into standby by timeout you aren't asked for your pin.
So maybe you could override this value to like -1 or any other value it can't reach and link the powerbuttons standby to the timeout standby.
I'm not familiar with xposed module development, just did some heavy amount of Java coding for desktop/server applications... So this is just an idea, I'm unsure if it is doable.
If this would work fine it'd be an awesome solution for the VPN password requirements
Sent from my Nexus 4
Click to expand...
Click to collapse
In the source of KeyguardViewMediator I found "Temporary enable/disable (e.g. the "back" button) are done in KeyguardHostView." so I am trying to also mock out showSecurityScreen there. Try this version and tell me what the logs say if it doesn't work. Also, if it almost works, but doesn't show recents, I can fix that pretty quickly.
FINGERS CROSSED! [NOTE: alpha build will NOT work on anything but 4.4 AOSP for this fix. I will build it for all if this is confirmed working. ]
dtreth said:
In the source of KeyguardViewMediator I found "Temporary enable/disable (e.g. the "back" button) are done in KeyguardHostView." so I am trying to also mock out showSecurityScreen there. Try this version and tell me what the logs say if it doesn't work. Also, if it almost works, but doesn't show recents, I can fix that pretty quickly.
FINGERS CROSSED! [NOTE: alpha build will NOT work on anything but 4.4 AOSP for this fix. I will build it for all if this is confirmed working. ]
Click to expand...
Click to collapse
I think it could actually work if I'd use Stock AOSP and not Omni
Code:
-----------------
15.01.2014 21:56:44 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-1.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method showLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method showSecurityScreen in class 'com.android.keyguard.KeyguardViewHost'
de.robv.android.xposed.XposedHelpers$ClassNotFoundError: java.lang.ClassNotFoundException: com.android.keyguard.KeyguardViewHost
at de.robv.android.xposed.XposedHelpers.findClass(XposedHelpers.java:52)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:179)
at net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler.handleLoadPackage(CompleteKeyguardDisabler.java:37)
at de.robv.android.xposed.IXposedHookLoadPackage$Wrapper.handleLoadPackage(IXposedHookLoadPackage.java:20)
at de.robv.android.xposed.callbacks.XC_LoadPackage.call(XC_LoadPackage.java:34)
at de.robv.android.xposed.callbacks.XCallback.callAll(XCallback.java:70)
at de.robv.android.xposed.XposedBridge$2.beforeHookedMethod(XposedBridge.java:202)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:527)
at android.app.ActivityThread.handleBindApplication(Native Method)
at android.app.ActivityThread.access$1500(ActivityThread.java:135)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1256)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5017)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:126)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.ClassNotFoundException: com.android.keyguard.KeyguardViewHost
at java.lang.Class.classForName(Native Method)
at java.lang.Class.forName(Class.java:251)
at external.org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:823)
at de.robv.android.xposed.XposedHelpers.findClass(XposedHelpers.java:50)
... 19 more
Caused by: java.lang.NoClassDefFoundError: com/android/keyguard/KeyguardViewHost
... 23 more
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.keyguard.KeyguardViewHost" on path: DexPathList[[zip file "/system/priv-app/Keyguard.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
... 23 more
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
I've noticed that effect also on the Active Display feature of the rom. I guess they have fixed it...
Take a look at this:
https://github.com/omnirom/android_...r/policy/activedisplay/ActiveDisplayView.java
Line 675
Code:
private void unlockKeyguardActivity() {
try {
// The intent we are sending is for the application, which
// won't have permission to immediately start an activity after
// the user switches to home. We know it is safe to do at this
// point, so make sure new activity switches are now allowed.
ActivityManagerNative.getDefault().resumeAppSwitches();
// Also, notifications can be launched from the lock screen,
// so dismiss the lock screen when the activity starts.
ActivityManagerNative.getDefault().dismissKeyguardOnNextActivity();
} catch (RemoteException e) {
}
handleForceHideNotificationView();
}
I guess this could help
This was the change that fixed it - at least I'm thinking that it would be: https://github.com/omnirom/android_frameworks_base/commit/72642b27a90bc760ee803c40a15c164a6a2ffa1c
Look at Line 645-660
fabi280 said:
I think it could actually work if I'd use Stock AOSP and not Omni
Code:
-----------------
15.01.2014 21:56:44 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-1.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method showLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method showSecurityScreen in class 'com.android.keyguard.KeyguardViewHost'
de.robv.android.xposed.XposedHelpers$ClassNotFoundError: java.lang.ClassNotFoundException: com.android.keyguard.KeyguardViewHost
at de.robv.android.xposed.XposedHelpers.findClass(XposedHelpers.java:52)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:179)
at net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler.handleLoadPackage(CompleteKeyguardDisabler.java:37)
at de.robv.android.xposed.IXposedHookLoadPackage$Wrapper.handleLoadPackage(IXposedHookLoadPackage.java:20)
at de.robv.android.xposed.callbacks.XC_LoadPackage.call(XC_LoadPackage.java:34)
at de.robv.android.xposed.callbacks.XCallback.callAll(XCallback.java:70)
at de.robv.android.xposed.XposedBridge$2.beforeHookedMethod(XposedBridge.java:202)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:527)
at android.app.ActivityThread.handleBindApplication(Native Method)
at android.app.ActivityThread.access$1500(ActivityThread.java:135)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1256)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5017)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:126)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.ClassNotFoundException: com.android.keyguard.KeyguardViewHost
at java.lang.Class.classForName(Native Method)
at java.lang.Class.forName(Class.java:251)
at external.org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:823)
at de.robv.android.xposed.XposedHelpers.findClass(XposedHelpers.java:50)
... 19 more
Caused by: java.lang.NoClassDefFoundError: com/android/keyguard/KeyguardViewHost
... 23 more
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.keyguard.KeyguardViewHost" on path: DexPathList[[zip file "/system/priv-app/Keyguard.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
... 23 more
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
I've noticed that effect also on the Active Display feature of the rom. I guess they have fixed it...
Take a look at this:
https://github.com/omnirom/android_...r/policy/activedisplay/ActiveDisplayView.java
Line 675
Code:
private void unlockKeyguardActivity() {
try {
// The intent we are sending is for the application, which
// won't have permission to immediately start an activity after
// the user switches to home. We know it is safe to do at this
// point, so make sure new activity switches are now allowed.
ActivityManagerNative.getDefault().resumeAppSwitches();
// Also, notifications can be launched from the lock screen,
// so dismiss the lock screen when the activity starts.
ActivityManagerNative.getDefault().dismissKeyguardOnNextActivity();
} catch (RemoteException e) {
}
handleForceHideNotificationView();
}
I guess this could help
This was the change that fixed it - at least I'm thinking that it would be: https://github.com/omnirom/android_frameworks_base/commit/72642b27a90bc760ee803c40a15c164a6a2ffa1c
Look at Line 645-660
Click to expand...
Click to collapse
Yeah, that build had, like, 6 typos in it, sorry. I cannot use that idea as posted (already tried it earlier and it completely borks), due to the way I slice into the keyguard and disable the lock. Somewhere there's a message that gets sent out to the navbar, I just can't find it. It doesn't help that if you google "navigation bar" google's results are full of "action bar" either....
Well, I cleaned some things up, this one shouldn't give you any exceptions, but I'd bet it still won't work. I'm gonna just buy a Nexus I think. I wanted one anyway. But I'll spend tonight trying to understand the navigation bar code and seeing if I can get it from that side.
In a related note, if anyone just wants to mock out a method, I wrote this snippet that simplifies the Xposed work:
Code:
private boolean mockOutMethod(final String logMessage,
ClassLoader cl,
String className,
String methodName,
Object... parameterTypes) {
try {
XposedBridge.log("hooking method '" + methodName + "' in class '" + className + "'");
// create the XCReplacement
XC_MethodReplacement mockOut = new XC_MethodReplacement() {
// do a full replacement of the method
@Override
protected Object replaceHookedMethod(MethodHookParam param) throws Throwable {
// do nothing, but log it
XposedBridge.log(logMessage);
return null;
}
};
// build the parameter list
Object[] parameterTypesAndCallback = Arrays.copyOf(parameterTypes, parameterTypes.length + 1);
parameterTypesAndCallback[parameterTypes.length] = mockOut;
// actually hook the method
XposedHelpers.findAndHookMethod(
className,
cl,
methodName, parameterTypesAndCallback);
}
catch (Throwable t) {
XposedBridge.log(t);
XposedBridge.log("hook method failed: '" + className + "." + methodName + "'");
return false;
}
return true;
}
dtreth said:
Yeah, that build had, like, 6 typos in it, sorry. I cannot use that idea as posted (already tried it earlier and it completely borks), due to the way I slice into the keyguard and disable the lock. Somewhere there's a message that gets sent out to the navbar, I just can't find it. It doesn't help that if you google "navigation bar" google's results are full of "action bar" either....
Well, I cleaned some things up, this one shouldn't give you any exceptions, but I'd bet it still won't work. I'm gonna just buy a Nexus I think. I wanted one anyway. But I'll spend tonight trying to understand the navigation bar code and seeing if I can get it from that side.
Click to expand...
Click to collapse
Code:
16.01.2014 00:25:17 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-2.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method 'showLocked' in class 'com.android.keyguard.KeyguardViewMediator'
hooking method 'showSecurityScreen' in class 'com.android.keyguard.KeyguardHostView'
Not locking the screen
Not showing the screen
Not showing the screen
Not locking the screen
Not locking the screen
Upon reboot after the update (with "slide away" keyguard) I had a lockscreen without any unlock element and a home button
But after the first lock and unlock it showed the Lockscreen Navbar
Stops shouting for a Lolli.
THIS MODULE PREVENTS LOLLIPOP FROM USING UPCASE EVERYWHERE, LIKE NOTIFICATION ACTIONS, DIALOGS AND BUTTONS. I DON'T LIKE IT AND THINK IT WAS A BAD DECISION.
Additional it is also annoying to have a 7" display, but the dialog buttons are shrinked now. Most time there is just a JA, NO, OK or GO - and you have to hit it. I'm not a monster, but my fingers are larger than of a 10 year old child.
So this module also uses for these buttons the whole width of the dialogs, like it was previously. You could set the position for a the text of 1 button dialogs to center or default position by open the module. Initial its random so you could check what's more suitable for you.
Only compatible with AOSP Lollipop!
Website: http://tinyurl.com/nq32zze
Play Store: http://tinyurl.com/mebbnqb
Xposed Repository: http://tinyurl.com/pc8tp4f
APK download: http://tinyurl.com/mzert7f
This affects not only dialogs but also tabs in apps, eg Tasker, nova launcher, ... Could you please make it its only for dialogs?
Sent from my Nexus 4 using Tapatalk
XlAfbk said:
This affects not only dialogs but also tabs in apps, eg Tasker, nova launcher, ... Could you please make it its only for dialogs?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
:good: ya would be better i think too but still nice addon
The width ot the "casing" of tabs?
defim said:
The width ot the "casing" of tabs?
Click to expand...
Click to collapse
not sure i get it so i'm attaching screenshots. none of these "toolbars" should be affected imho, only dialogs.
XlAfbk said:
not sure i get it so i'm attaching screenshots. none of these "toolbars" should be affected imho, only dialogs.
Click to expand...
Click to collapse
Thx for the screenshot! I've disabled the upcase transformation global, there is not available by which component it is requested.
But anyway upcase tabs are ugly, it so Visual Studio style ^^
It would be great if you could add buttons to enable/disable upcase. I really like your work of putting the buttons in center and using the whole width, that is great. But I like the capital letters, too :angel: :good:
fiz:ik said:
It would be great if you could add buttons to enable/disable upcase. I really like your work of putting the buttons in center and using the whole width, that is great. But I like the capital letters, too :angel: :good:
Click to expand...
Click to collapse
I've split the functions into 2 separate modules and just uploaded them to Xposed repo
Excellent, again! Two BIG thumbs up!
thanks for the split modules
sometimes the button text resets to its default place, even when i choose "center" in the module settings (only happens with single-button dialogs).
module: HowGiveLolliButton
device & rom: moto g 2013 / android 5.0.1 (gpe)
kingkaminari said:
sometimes the button text resets to its default place, even when i choose "center" in the module settings (only happens with single-button dialogs).
Click to expand...
Click to collapse
With the same dialog? Can you long touch the button to see if it used the whole width even the text is not in right place?
@defim yes. The button uses the whole width even with the text out of place. Can't post a screenshot right now because I downgraded to KK.
Sent from my XT1032 using Tapatalk
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
I was previously using the original module (HowGiveLolli) but I prefer this one since I don't have problems with that whole load of uppercase text [emoji14]
Sent from my XT1032 using Tapatalk
kingkaminari said:
@defim yes. The button uses the whole width even with the text out of place. Can't post a screenshot right now because I downgraded to KK.
Sent from my XT1032 using Tapatalk
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
I was previously using the original module (HowGiveLolli) but I prefer this one since I don't have problems with that whole load of uppercase text [emoji14]
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Sometimes Android "forget" to create shared_pref directory in the apps data dir. Then savin preferences is not possible, but no error. You could check with a root enabled file manager. Or you could get an "shared preferences" editor/viewer from play store to verify that there was a value saved
defim said:
Sometimes Android "forget" to create shared_pref directory in the apps data dir. Then savin preferences is not possible, but no error. You could check with a root enabled file manager. Or you could get an "shared preferences" editor/viewer from play store to verify that there was a value saved
Click to expand...
Click to collapse
if i create that dir myself, will it solve the problem?
kingkaminari said:
if i create that dir myself, will it solve the problem?
Click to expand...
Click to collapse
Should. Is it missing?
defim said:
Should. Is it missing?
Click to expand...
Click to collapse
didnt check that at the time. i'll have to install lollipop again soon (to test a deodexed stock rom i created) so i'll test your module again and create that dir if needed, then report back
i can confirm that no shared prefs dir was created. even after i created the dir, no preference was written
kingkaminari said:
i can confirm that no shared prefs dir was created. even after i created the dir, no preference was written
Click to expand...
Click to collapse
If you create it by "root" only root is allowed to r/w/x -> set user+group+permission like other dirs, eg the existing "files" or "cache".
Another "fix" could be to remove & reinstall.
But the suspect is that the directory is missing sometimes!
defim said:
If you create it by "root" only root is allowed to r/w/x -> set user+group+permission like other dirs, eg the existing "files" or "cache".
Another "fix" could be to remove & reinstall.
But the suspect is that the directory is missing sometimes!
Click to expand...
Click to collapse
actually, i just cleared the app's data and its working fine now
I quickly got quite annoyed by Chrome's new 'feature' of showing customized address bar colors for certain websites. I simply prefer my address bar (and anything attached to it) to be the same default color as it always was.
As there was no option in chrome to disable this feature, I wrote this tiny Xposed module that intercepts the call to 'getThemeColor' for the chrome tabs and simply returns the default color instead.
Tested on Galaxy S4 (GT-I9505) running CM12.1
// Edit:
As I was not that consistent with my naming scheme, the name in the Xposed repo turned out slightly different: "Chrome toolbar Color Killer"
(For those interested that were unable to find the module)
Thanks for this, was annoying me too!
Seems to work fine on my Nexus 5 running 6.0.1
irvdijk said:
I quickly got quite annoyed by Chrome's new 'feature' of showing customized address bar colors for certain websites. I simply prefer my address bar (and anything attached to it) to be the same default color as it always was.
As there was no option in chrome to disable this feature, I wrote this tiny Xposed module that intercepts the call to 'getThemeColor' for the chrome tabs and simply returns the default color instead.
Tested on Galaxy S4 (GT-I9505) running CM12.1
// Edit:
As I was not that consistent with my naming scheme, the name in the Xposed repo turned out slightly different: "Chrome toolbar Color Killer"
(For those interested that were unable to find the module)
Click to expand...
Click to collapse
I'm sorry but you can disable this by tapping chrome://flags/ in your url bar and search for the option to disable
Dead-neM said:
I'm sorry but you can disable this by tapping chrome://flags/ in your url bar and search for the option to disable
Click to expand...
Click to collapse
I can't see that option in flags. What is it called?
i don't see the option in flags either, but maybe i'm missing it?
also I can't get the chromecolorkiller apk to work - i've installed it but headers are still changing color... am i doing something wrong?
thanks
louislouis said:
i don't see the option in flags either, but maybe i'm missing it?
also I can't get the chromecolorkiller apk to work - i've installed it but headers are still changing color... am i doing something wrong?
thanks
Click to expand...
Click to collapse
Same. It worked at first but after a few reboot all is the same as usual
Same here.
Running today's CM13 nightly (23-02-2016) and Chrome version 48.0.2564.95
Xposed log says this:
02-23 10:00:22.103 E/Xposed ( 6901): java.lang.NoSuchFieldException: No field mDefaultThemeColor in class
does it support any chrome builds and derivatives? beta/dev/chromium/caf
hey man, it's just an idea for you, but could you make this work the other way round too? i mean, forcing chrome to tint the bar of a webpage in a certain color.. it could be a pro feature so you could make some cash i'm no programmer so i don't know the technical difficulties behind this but it sure would be awesome
Sorry guys for not replying any sooner, but I've been crazy busy at work
Also, I got myself a new phone which remains unrooted for now, so any of the issues that may occur with the Xposed module I cannot reproduce.
an0therus3r said:
Same here.
Running today's CM13 nightly (23-02-2016) and Chrome version 48.0.2564.95
Xposed logsays this:
02-23 10:00:22.103 E/Xposed ( 6901): java.lang.NoSuchFieldException: No field mDefaultThemeColor in class
Click to expand...
Click to collapse
From your log I assume that Chrome has moved some internals around since I built this module. Perhaps someone would be interested in picking things up and figure out what to tap into to disable this annoying feature once more.
OT-Xtreme said:
does it support any chrome builds and derivatives? beta/dev/chromium/caf
Click to expand...
Click to collapse
Would not be able to say this for certain, but my first guess would be No. Apparently chrome itself also became incompatible
bombaglad said:
hey man, it's just an idea for you, but could you make this work the other way round too? i mean, forcing chrome to tint the bar of a webpage in a certain color.. it could be a pro feature so you could make some cash i'm no programmer so i don't know the technical difficulties behind this but it sure would be awesome
Click to expand...
Click to collapse
Sounds like a great idea! Though that is one hell of a lot more complicated than what I was aiming for. I would be happy to share the code I have with anyone who might be interested in fixing / updating stuff. Maybe they could also figure out a way to include your idea.
For now I won't be working on this module anymore, but if someone would be interested in the source code, just let me know. There's probably a way I can share it...
A simpler idea is to make the bar always default to a color, for example black. Coupled with chromium night mode it would be the ultimate night browsing experience.
Let's fix this great module!
irvdijk said:
For now I won't be working on this module anymore, but if someone would be interested in the source code, just let me know. There's probably a way I can share it...
Click to expand...
Click to collapse
I really love the feature of this module.. And I also like the idea to set a user-chosen color of the toolbar for each website (for example I LOVE black!!) So if you can share the code (preferably for Android Studio) there are many chances to succeed! I am a developer too and I already build some "tests" Xposed modules.. So let me know! Thanks
..And sorry for my English but I'm Italian xD
Great module! Not working for me at the moment though. Not sure if chrome has been updated recently.
Thank you!
Androyx96 said:
I really love the feature of this module.. And I also like the idea to set a user-chosen color of the toolbar for each website (for example I LOVE black!!) So if you can share the code (preferably for Android Studio) there are many chances to succeed! I am a developer too and I already build some "tests" Xposed modules.. So let me know! Thanks
..And sorry for my English but I'm Italian xD
Click to expand...
Click to collapse
hey there, did u managed to continue the work of this module ?
What a good module
Can it change default color to black?
It will be more save battery
No longer works
It no longer works, could you try to update it so it will work again?
bombaglad said:
hey man, it's just an idea for you, but could you make this work the other way round too? i mean, forcing chrome to tint the bar of a webpage in a certain color.. it could be a pro feature so you could make some cash i'm no programmer so i don't know the technical difficulties behind this but it sure would be awesome
Click to expand...
Click to collapse
I've actually wanted this for quite a while. That's how I found this module.
irvdijk said:
Sounds like a great idea! Though that is one hell of a lot more complicated than what I was aiming for. I would be happy to share the code I have with anyone who might be interested in fixing / updating stuff. Maybe they could also figure out a way to include your idea.
For now I won't be working on this module anymore, but if someone would be interested in the source code, just let me know. There's probably a way I can share it...
Click to expand...
Click to collapse
You could share the source code on github. I do not have any time right now, but I would be interested in working on it, come April (2017). That is, if someone else has not already done it by then.
---------- Post added at 06:44 AM ---------- Previous post was at 06:42 AM ----------
Androyx96 said:
I really love the feature of this module.. And I also like the idea to set a user-chosen color of the toolbar for each website (for example I LOVE black!!) So if you can share the code (preferably for Android Studio) there are many chances to succeed! I am a developer too and I already build some "tests" Xposed modules.. So let me know! Thanks
Click to expand...
Click to collapse
+1 :good:
Burnt Toast Revived is an updated version of @MohammadAG's Burnt Toast Xposed module. In this version I added support for the latest versions of Android that have rounded toast messages, and fixed the problem of the text too near to the border.
NEW! It's now possible to change the size of the icon.
NEW! It's now possible to change the size of the margins.
Description:
This modules adds the app icon to toast messages, giving a more colorful look to them, and also making them more understandable.
Notes:
Support for Android versions before Lollipop has been dropped. Please use the original module on KitKat and before.
Changelog:
v1.6
Added option to change margins size.
Added more sizes, and removed some bigger ones.
Fixed controls not visible on some devices and in landscape.
No more overlapping or delayed toast messages. When you change size, the old toast is dismissed before generating a new one.
v1.5
Added option to change icon size
Added support for some ROMs with different layout for toast messages
v1.4
Initial release
Links:
Source code: GitHub
Download: Xposed Repo
Works perfectly well! Great job?
Not sure if you know this but Apps that are doing something with root access shows magisk icon.
Pixel 2xl Oreo 8.1
smartymcfly said:
Not sure if you know this but Apps that are doing something with root access shows magisk icon.
Pixel 2xl Oreo 8.1
Click to expand...
Click to collapse
It's normal. The app that manages root is Magisk (or SuperSU or another), so the notifications are coming from that app.
Could you add options to change the design of the message istelf like xtoast did?
mali_ said:
The toasts are too big. Can't you make it like in custom roms with just a small icon next to the toast? Or options to change size?
Click to expand...
Click to collapse
I'm working on it.
adwait96 said:
Not working on my device.
Oneplus 3 using RR-N-v5.8.5-20171217-oneplus3-Final
Rooted with xposed v89 and magisk installed.
I checked on apps that doesn't require root like lookup, fly gps and sesame shortcuts and root app like greenify.
I have disabled system toast notifications(from settings->configurations->animations->toast) n magisk toast notifications so it should not affect this module.
I would love to use this cause system n magisk uses small icons which are barely visible.
Thanks anyways!
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Can you please send me the file /system/framework/framework-res.apk extracted from your phone?
Thaodan said:
Could you add options to change the design of the message istelf like xtoast did?
Click to expand...
Click to collapse
It's not in my plans, sorry.
adwait96 said:
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Sorry, I don't see any link or file. Please upload it somewhere and send me the link.
adwait96 said:
It didn't upload because of the file limit
My bad
Edited and shared the link in previous post.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
I sent you a DM, please check it out.
v1.5 is out now
Changelog:
Added option to change icon size
Added support for some ROMs with different layout for toast messages
mali_ said:
I can't change the size. It shows the same size no matter which button I tap on - 128 in xposed logs.
Is it possible to achieve this kind of toasts that's available in custom roms? Please check picture.
Click to expand...
Click to collapse
Please give me more information: what device are you using? What ROM and Android version?
I don't think it's possible to put the icon in the corner (if that's what you're asking for) without heavily modifying the layout. I will look into it.
Working properly on LOS 14.1. I would just recommend to center icon within the whitespace after changing the icon's size, so it looks better.
Thank you!
mali_ said:
Nexus 5, stock marshmallow 6.0.1
Click to expand...
Click to collapse
Please send by PM the output of the following commands:
Code:
ls -al /data
ls -ald /data/data/me.rapperskull.*
ls -alR /data/data/me.rapperskull.*
ls -ald /data/user/0/me.rapperskull.*
ls -alR /data/user/0/me.rapperskull.*
Tletl said:
Working properly on LOS 14.1. I would just recommend to center icon within the whitespace after changing the icon's size, so it looks better.
Thank you!
Click to expand...
Click to collapse
Please attach a screenshot to clarify the problem.
Hi,
Thanks for the modules revival. Could you please make the paddings adjustable too? Even with a small icon size the toast is still a lot larger than standard toast.
Oreo 8.0 on OnePlus 5
XlAfbk said:
Hi,
Thanks for the modules revival. Could you please make the paddings adjustable too? Even with a small icon size the toast is still a lot larger than standard toast.
Oreo 8.0 on OnePlus 5
Click to expand...
Click to collapse
It's already scheduled for the next version, but it varies with the device. Please send a screenshot to highlight the problem.
Rapper_skull said:
It's already scheduled for the next version, but it varies with the device. Please send a screenshot to highlight the problem.
Click to expand...
Click to collapse
Original width, just cut out the application above
XlAfbk said:
Original width, just cut out the application above
Click to expand...
Click to collapse
Please send me the file /system/framework/framework-res.apk
Rapper_skull said:
Please send me the file /system/framework/framework-res.apk
Click to expand...
Click to collapse
Pm
Rapper_skull said:
Tletl said:
Working properly on LOS 14.1. I would just recommend to center icon within the whitespace after changing the icon's size, so it looks better.
Thank you!
Click to expand...
Click to collapse
Please attach a screenshot to clarify the problem.
Click to expand...
Click to collapse
Attached.
Icon is aligned to the right, beside the text. Would look better to center it within the whitespace to the left of toast's text.
Tletl said:
Attached.
Icon is aligned to the right, beside the text. Would look better to center it within the whitespace to the left of toast's text.
Click to expand...
Click to collapse
Unfortunately some of the margins are fixed, so I can't reduce them so much. In the next version I will add a slider to set margin size.
Rapper_skull said:
Please send me the file /system/framework/framework-res.apk
Click to expand...
Click to collapse
Hello, i have exactly the same problem, i send u my apk file too if you can take a look please :good:
Thanks in advance