I know that the Iphone unlock feature is only intended for touch screen devices. However, S2u2 Version 1.01 will allow me to use the center control button to unlock. Looks cool and works fine. The problem is I can not change any of the settings in the S2u2 setting exe file because the phone is not a touch screen. The only setting that I want to change is the setting for automatic phone shutoff after 17 seconds. I like the unlock feature but it sticks if it shuts my phone off after 17 seconds!!! I tried finding a config file to manually change but I was not successful. Does anyone have any ideas?
John123456789 said:
I know that the Iphone unlock feature is only intended for touch screen devices. However, S2u2 Version 1.01 will allow me to use the center control button to unlock. Looks cool and works fine. The problem is I can not change any of the settings in the S2u2 setting exe file because the phone is not a touch screen. The only setting that I want to change is the setting for automatic phone shutoff after 17 seconds. I like the unlock feature but it sticks if it shuts my phone off after 17 seconds!!! I tried finding a config file to manually change but I was not successful. Does anyone have any ideas?
Click to expand...
Click to collapse
check here in your registry:
\HKEY_CURRENT_USER\Software\A_C\S2U2.
OffLCD=17
Please remember to RESTART iLock2 after any registry settings changed, otherwise it won't work):
That did it! A million thanks!!
BTW, i was able to get this to work using SOTI pocket controller. That way i dont have to do all the reg edits. BTW the caller Id function built into this application doesn't work very well on the S620. And you have to replace the wallpaper file ( which is a portait) with your own wallpaper file ( 320 X 240) in order to get a full screen image. Anywho, i just love this application!
do you guys mind posting a screen shot of this application so i know how it looks like and what it does? thanks
lukybandit said:
do you guys mind posting a screen shot of this application so i know how it looks like and what it does? thanks
Click to expand...
Click to collapse
Ok here's the link to the app. http://forum.xda-developers.com/showthread.php?t=381588 Its basically a screen saver/key lock application/potential photo caller ID application that is made to emulate the iphone. And it doesn't interfere with the windows 6.1 chome homescreen. It's made for the PPC and not the smartphone, but it works on the smartphone. There are some things you'll want to change in the settings, but the settings proggy is only touch based, so you'll either have to do some regedits or install SOTI pocket controller and use your PC to open the application on your phone and make the adjustments. anyway enough of my babbling, here are some screenshots i took on my S620. The first one is the app running while your phone is locked and running on battery power. The 2nd is the same thing only while its running on External power (aka charging)
{
"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"
}
here's the other
in order for U to unlock your phone all you have to do is push your 4-way D pad to the right intil the little slider reaches all the way to the right and your homescreen will re-appear. enjoy!
BTW: if you set the settings correctly and disable the "Power of in" and turn on the '"lock when backlight turns off" it will enable this program , esentially locking your keys automatically, but with a lot more flare!
pudgedaddy said:
Ok here's the link to the app. http://forum.xda-developers.com/showthread.php?t=381588 Its basically a screen saver/key lock application/potential photo caller ID application that is made to emulate the iphone. And it doesn't interfere with the windows 6.1 chome homescreen. It's made for the PPC and not the smartphone, but it works on the smartphone. There are some things you'll want to change in the settings, but the settings proggy is only touch based, so you'll either have to do some regedits or install SOTI pocket controller and use your PC to open the application on your phone and make the adjustments. anyway enough of my babbling, here are some screenshots i took on my S620. The first one is the app running while your phone is locked and running on battery power. The 2nd is the same thing only while its running on External power (aka charging)
here's the other
in order for U to unlock your phone all you have to do is push your 4-way D pad to the right intil the little slider reaches all the way to the right and your homescreen will re-appear. enjoy!
BTW: if you set the settings correctly and disable the "Power of in" and turn on the '"lock when backlight turns off" it will enable this program , esentially locking your keys automatically, but with a lot more flare!
Click to expand...
Click to collapse
Now that's what I call - A TRUE XDA MEMBER
Thanks for being so helpful, I really appreciate it - I just asked you one question and you gave me the descripton, the link to the program - basically what i need to know and I honestly have to say, not many members are like you.
It's good to know we have people like you that go out of their way to help others. Thanks once again - I'm heading to university right now but I definitely will try the application tonight and posts the results..
P.S: It does look rather stunning. cant wait
pudgedaddy said:
check here in your registry:
\HKEY_CURRENT_USER\Software\A_C\S2U2.
OffLCD=17
Click to expand...
Click to collapse
just change OffLCD=17?
Another program that could be used to control the phone on your PC and change the s2u2 settings is
MyMobiler
http://www.mtux.com/
I just set up s2u2 1.1 on my dash and it is working fine.
The only thing I want to be able to do is activate S2U2 when I hold down the end call button [which normally locks the phone]. How do I make it happen?
EDIT: Ok Im one step closer. I followed the steps in this link http://forum.xda-developers.com/showpost.php?p=1177366&postcount=9 and with the MYmobiler program running, I edited the settings thru my PC. I changed the end call button to long press and assigned that function to s2u2. It works ALMOST perfect. The only problem is when I unlock s2u2, the default windows lock is still on.
I may just be stupid but I cannot figure out how to change the wallpaper into something that I want. I see that pudgdaddy did it but I cannot get it to do the same on my device. Can someone please tell me how this works?
Edit: Nevermind. I figured it out. Wow am I dumb sometimes.
Does anyone else have the problem that when the phone is idle for a while this program stops? I am afraid that the keys are no longer locked and I am going to push buttons while it is in my pocket or the case. Is this just my phone?
yea, i had this problem too...... which is why i don't use it anymore.... i'd looove to use it again but that was a deal breaker for me
pudgedaddy said:
yea, i had this problem too...... which is why i don't use it anymore.... i'd looove to use it again but that was a deal breaker for me
Click to expand...
Click to collapse
I actually figured it out. You just have to set your homescreen so that it never times out. It is under the normal homescreen settings. Seems to have worked so far. Even when I came back to my phone overnight it was still running so hopefully that actually fixed the problem.
USF NATE said:
I actually figured it out. You just have to set your homescreen so that it never times out. It is under the normal homescreen settings. Seems to have worked so far. Even when I came back to my phone overnight it was still running so hopefully that actually fixed the problem.
Click to expand...
Click to collapse
i set autostart and idlestart to 1 and it seems to work
acidlestart doesnt seem to work as it never locks when my phone is plugged in (wall or usb)
when s2u2 locks my phone, my tzones (opera mini) and message buttons still work. im trying to create a string "DisableLNK0" "short_ie.lnk" and "DisableLNK1" "short_MSG.lnk" now to see it that disables these buttons. **UPDATE: DIDN'T WORK**
also would there be a way for me to reprogram the action that happens when i hold down the end call button? (switching from htcphonelock to s2u2 when this actions takes place?)
any help would be appreciated as working out all the little bugs for the smartphone has been kind fun and challenging but i lose productivity at, ahem*, work. lmao
Well looks like Im back to square one with this s2u2 program. All this time Ive been trying to remap the keys to make it work properly but I overlooked a key element.
When I received a call today, s2u2 was running and I could not answer the call simply because THERE WAS NO WAY TO CONTROL THE MENU! Since it's designed for touch screen phones, which the Dash isn't, the program doesn't respond to the green or red phone keys.
I had to send the call to voicemail and then call the person back.
fuLLah said:
Well looks like Im back to square one with this s2u2 program. All this time Ive been trying to remap the keys to make it work properly but I overlooked a key element.
When I received a call today, s2u2 was running and I could not answer the call simply because THERE WAS NO WAY TO CONTROL THE MENU! Since it's designed for touch screen phones, which the Dash isn't, the program doesn't respond to the green or red phone keys.
I had to send the call to voicemail and then call the person back.
Click to expand...
Click to collapse
in my registry for s2u2 i had a string S2ACallKey and i set it to 1 which allowed the green call button to answer incoming calls
and the same for S2AEndKey. it should equal 1.
oh and my callerid key is set to 0. i think the caller id thing doesnt function correctly for smartphones.
when i did use the caller id i had it set to 1 (you can use 1 or 2 and caused my phone call screen to never come up when i made a call). when my caller id was on the green and red "touch" buttons worked with the physical buttons, but the screen looked funny so i just threw it out.
where did you place the string? what folder and subfolder?
fuLLah said:
where did you place the string? what folder and subfolder?
Click to expand...
Click to collapse
correct me if i'm wrong renegadedj, but i believe its in \HKEY_CURRENT_USER\Software\A_C\S2U2 i didnt see it either, but i created that dword in that key and assigned it a value of 1. i havent had a chance to try it, but i will let you know once i get a call
pudgedaddy said:
correct me if i'm wrong renegadedj, but i believe its in \HKEY_CURRENT_USER\Software\A_C\S2U2 i didnt see it either, but i created that dword in that key and assigned it a value of 1. i havent had a chance to try it, but i will let you know once i get a call
Click to expand...
Click to collapse
yep thats right where it was. but mine was already there. i didn'nt have to do any work on that one.
any word on if i can disable the short_msg.lnk or tzones (short_ie.lnk??)
and/or/more and... can i change the action of holding down the end call button in idle to do and "htc" phone lock?
You guys still use this ? I use version 1.22 on my blackjack and it works pretty well. I just installed it on a friend's Dash and it works very well also!
Related
so i just got a tilt 2 today. and I can't get screen orientation to change whenever I would like it to. I have calibrated G-Sensor and it works for a few programs. But it doesn't work for the home screen. I put a registry editor on my phone and noticed that the gsensor only has like 5 programs for it. how can i go about fixing this? I've tried to do a few searches, but haven't been able to find quite what I'm looking for
You want to use this:
[APP] G-Config (Configurator for the new SensorSDK 4)
really simple to add programs to your rotation registry.
If you read through that thread There's a way to ad manilla/sense/touchflo3d.... whatever you call it as everyone calls it what they want to the list.
That said, you will find this REALLY annoying. I had it set to that back when I had my touch pro and after a day I got rid of it cause even if you tilt the phone slightly the phone rotated and yeah... just annoying as hell.
An alternative you can have is download RhodiumKBDControl. Search for it on google and you'll find it. You can program buttons on your phone to do certain things. Most people with the tilt2 reprogram their PTT button to do something like open the camera or rotate the screen or adjust the brightness. The cool thing about it is you can program it so a long press does one thing while a single press does another while a double or triple press does something different too. This works for ANY key on our phone.
You're better off setting it to rotate via the button because like said after a day or so you'll just be sick of it.
thereason222 said:
so i just got a tilt 2 today. and I can't get screen orientation to change whenever I would like it to. I have calibrated G-Sensor and it works for a few programs. But it doesn't work for the home screen. I put a registry editor on my phone and noticed that the gsensor only has like 5 programs for it. how can i go about fixing this? I've tried to do a few searches, but haven't been able to find quite what I'm looking for
Click to expand...
Click to collapse
I use a program called Gyrator. Its awesome, and i have no problems with it.
You'll find it on the "software worth installing on the TP2" thread.
Good luck
thereason222 said:
so i just got a tilt 2 today. and I can't get screen orientation to change whenever I would like it to. I have calibrated G-Sensor and it works for a few programs. But it doesn't work for the home screen. I put a registry editor on my phone and noticed that the gsensor only has like 5 programs for it. how can i go about fixing this? I've tried to do a few searches, but haven't been able to find quite what I'm looking for
Click to expand...
Click to collapse
use the registry editor and you can add the programs yourself. all you need to know is the class name and where the .exe is stored. i have a .reg back up file to add rotation to apps. i originally found it on here somewhere but ive added/removed a few things.
otherwise you can do it manually.. if u want to know how, tell me; No mch time to write, right now
vic000 said:
otherwise you can do it manually.. if u want to know how, tell me; No mch time to write, right now
Click to expand...
Click to collapse
Already gave it to him vic
Aaron McCarthy said:
.....
An alternative you can have is download RhodiumKBDControl. Search for it on google and you'll find it. You can program buttons on your phone to do certain things. Most people with the tilt2 reprogram their PTT button to do something like open the camera or rotate the screen or adjust the brightness. The cool thing about it is you can program it so a long press does one thing while a single press does another while a double or triple press does something different too. This works for ANY key on our phone.
You're better off setting it to rotate via the button because like said after a day or so you'll just be sick of it.
Click to expand...
Click to collapse
Hi, I've done a search and can't find anything here (although my searching skills might not be all that good).
On my Milestone the volume rocker would let me change the ringer volumes like on the Galaxy S2 but with a small, but very useful additional feature.
When using the volume down button to reduce the ringer level, or to set the phone on vibrate only, if you pressed the volume down once more after vibrate, the phone would be set on silent mode.
This is actually really useful and I'm missing it a lot, as if you're busy and somebody keeps calling you back there's no quick way to just set the phone on silent. Or similarly if you're in a messaging app and somebody keeps messaging then the phone keeps vibrating again and again and again even though you know that you've received a message.
Is there anyway to make this modification on the galaxy s2?
(I'm using stock ke7 btw)
Yeah I really missed this feature from my Nexus S when I traded it for an Atrix.
Shame it isn't on the GSII... it'd be cool to have this feature again. Anyone...?
In the meantime you can use a widget to toggle between vibe and silent mode.
Hi yamanote, thanks for the heads up. Any widget in particular you would recommend?
Hope someone takes up this mod soon
I have Silent Toggle Widget (free, by Droidmania) installed. Nice icons and most importantly works (toggles between Ring, Vibrate and Silent)
Thanks, its working great
DonJassa said:
Hi yamanote, thanks for the heads up. Any widget in particular you would recommend?
Hope someone takes up this mod soon
Click to expand...
Click to collapse
Widget Locker works well and replaces the lock screen which I hate on the SGS2.
I've seen several people complaining about this and started to wonder.... If you're willing to install a widget, would you be willing to drag down your Notification Bar and click on the fourth button (between GPS & Auto Rotate) to switch between Sound, Silent & Vibration?
Wow. I've import just flashed ke7 yesterday and didn't notice if that's what changed it, but on my stock s2 the fourth button there had something to do with network data mode.
Either way thanks alot for pointing that out! I'll ber using it until (if) somebody works out how to do the mod with the volume rocker. =)
The Day Dreaming Sheep said:
Widget Locker works well and replaces the lock screen which I hate on the SGS2.
I've seen several people complaining about this and started to wonder.... If you're willing to install a widget, would you be willing to drag down your Notification Bar and click on the fourth button (between GPS & Auto Rotate) to switch between Sound, Silent & Vibration?
Click to expand...
Click to collapse
If you can get that stock toggle to do that I'm sure you can get the volume rockers to do the same
Hey guys, I've made an app that emulates the old rocker functionality, it's a bit hacky so I made a 36 hour trial so you can make sure it works properly.
Advanced ringer rocker (trial)
Advanced ringer rocker
Thanks for creating that app.
It works fine on vr1.1, but three glitches I can see:
1)
{
"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"
}
Going from volume to vibe works fine, but when going into silent mode it looks like there's another screen which overlaps the vibration screen.
Look at the image if you don't understand.
2) minor annoyance- the stock pop-up says 'Ringer volume' while the app's version says 'Ringer Volume'.
3) When going from sound to vibe it vibrates once for ~1 second, but when going from silent to vibration mode there are two short pulses.
If you can fix it and make it feel more stock then i'll buy it for sure
Sent from my GT-I9100
yamanote said:
1)
Going from volume to vibe works fine, but when going into silent mode it looks like there's another screen which overlaps the vibration screen.
Look at the image if you don't understand.
Click to expand...
Click to collapse
Because of the Android API limitations, this is unfortunately the only way I can make it work. It's not possible to disable the standard volume popup screen, so I just overlap my own.
The screen behind it (standard system popup) will be displaying an incorrect icon when you change from vibrate to silent or silent to vibrate, so I display the correct one over the top.
It looks slightly too low on your screenshot, I'm not sure what's causing that, it doesn't do that on my device (ZTE blade) or the emulator so I presume it's due to a different UI theme (?) Although that shouldn't cause it to misalign.
2) minor annoyance- the stock pop-up says 'Ringer volume' while the app's version says 'Ringer Volume'.
Click to expand...
Click to collapse
Thanks, I missed that
3) When going from sound to vibe it vibrates once for ~1 second, but when going from silent to vibration mode there are two short pulses.
Click to expand...
Click to collapse
Will look into that
edit: Can't reproduce that. Can you try disabling advanced ringer rocker, then go into the android settings menu/sounds and switch between vibrate and normal mode (click the Silent Mode checkbox) and tell me if your phone vibrates
If you can fix it and make it feel more stock then i'll buy it for sure
Click to expand...
Click to collapse
Do you mean the background colour? Is it different to your regular one?
Apps like Tasker or Timeriffic don't show any volume popups when they change the volume levels. Tasker even has an option if you want to show the volume popup, so I am sure it's possible, but it doesn't matter one bit. I'll test it out, because this seems all good to me. Thanks.
richardop said:
Because of the Android API limitations, this is unfortunately the only way I can make it work. It's not possible to disable the standard volume popup screen, so I just overlap my own.
The screen behind it (standard system popup) will be displaying an incorrect icon when you change from vibrate to silent or silent to vibrate, so I display the correct one over the top.
It looks slightly too low on your screenshot, I'm not sure what's causing that, it doesn't do that on my device (ZTE blade) or the emulator so I presume it's due to a different UI theme (?) Although that shouldn't cause it to misalign.
Click to expand...
Click to collapse
The ROM I'm on doesn't have a theme, its the stock Samsung look. And yeah I understand why you can only make it overlap- the issue I was describing was how the overlapped box was slightly lower than the normal pop-up
Just curious- would it be possible to disable the stock popup if I have root?
richardop said:
Will look into that
edit: Can't reproduce that. Can you try disabling advanced ringer rocker, then go into the android settings menu/sounds and switch between vibrate and normal mode (click the Silent Mode checkbox) and tell me if your phone vibrates
Click to expand...
Click to collapse
If I have vibration set to only in silent mode or always [on] then yes toggling between silent (vibe) and ringer does initiate one ~1 sec vibration.
richardop said:
Do you mean the background colour? Is it different to your regular one?
Click to expand...
Click to collapse
Nah I just meant 'fix the above glitches and I'll buy it'
Sent from my GT-I9100
maedox said:
Apps like Tasker or Timeriffic don't show any volume popups when they change the volume levels. Tasker even has an option if you want to show the volume popup, so I am sure it's possible, but it doesn't matter one bit. I'll test it out, because this seems all good to me. Thanks.
Click to expand...
Click to collapse
Thanks for the great feedback.
Because I can't directly detect volume button key-presses (can only do that if you are the currently active activity) I basically listen for volume changes and calculate when to enter silent mode. Android responds to your key-presses as it usually does by displaying the (now incorrect) ringer mode popup since it's unaware of my app running around behind it changing the ringer mode.
yamanote said:
The ROM I'm on doesn't have a theme, its the stock Samsung look. And yeah I understand why you can only make it overlap- the issue I was describing was how the overlapped box was slightly lower than the normal pop-up
Just curious- would it be possible to disable the stock popup if I have root?
Click to expand...
Click to collapse
With root you can pretty much do anything, so yes I would say that is entirely possible but I'm not sure how.
I can't think why the overlay isn't exactly aligned on your device, I've tried something that may help but if it hasn't fixed it then sadly I don't know what will.
If I have vibration set to only in silent mode or always [on] then yes toggling between silent (vibe) and ringer does initiate one ~1 sec vibration.
Click to expand...
Click to collapse
I've fixed the typo, fixed the double vibrate. It's now an option under menu/advanced options, you'll need to disable it. It seems some devices vibrate and some don't (Gingerbread change?).
Also added a different style, stock/dark gingerbread which it will default to on 2.3.
I don't think it's going to be possible to make this work 100% on all devices, so I've dropped the price to $0.99
If you need more time to test these changes on the trial version then PM me your UUID (reinstall the app or clear data, then start it up without an internet connection and it will show your UUID)
richardop said:
With root you can pretty much do anything, so yes I would say that is entirely possible but I'm not sure how.
Click to expand...
Click to collapse
I can't think why the overlay isn't exactly aligned on your device, I've tried something that may help but if it hasn't fixed it then sadly I don't know what will.[/QUOTE]
The updated version unfortunately doesn't fix the misalignment Will probably flash an updated version of my current ROM or flash another ROM when I'm free so yeah maybe that'll fix it. Thanks for the attempt though.
I've fixed the typo, fixed the double vibrate. It's now an option under menu/advanced options, you'll need to disable it. It seems some devices vibrate and some don't (Gingerbread change?).
Click to expand...
Click to collapse
Yep can confirm that the typo and double vibe have been fixed (the latter after disabling the checkbox).
Also added a different style, stock/dark gingerbread which it will default to on 2.3.
Click to expand...
Click to collapse
Just a heads-up for others- if you've got the stock Samsung theme on then you'll want to switch to the Froyo style.
I don't think it's going to be possible to make this work 100% on all devices, so I've dropped the price to $0.99
If you need more time to test these changes on the trial version then PM me your UUID (reinstall the app or clear data, then start it up without an internet connection and it will show your UUID)
Click to expand...
Click to collapse
Price drop is always a nice incentive to purchase, hah
PM'd you my UUID, thanks.
Will test it a bit more and will most likely purchase it after I get Google Checkout sorted out- probably tomorrow (it's 5am here and i'm tired lol)
You might want to look into using Widgetlocker. Next to the fact is freaking awesome on itself it also offers the silent option
So, the nav-bar eating a portion of my screen was bothering me for a while and I wanted my device to rely on gestures only, so I decided to search for the most suitable way for me to solve this problem... LMT of course, but first I got rid of the nav-bar using FullScreen Toggle.
Big thanks to the creators of both those apps
LMT can be found here: http://forum.xda-developers.com/showthread.php?t=1330150
FullScreen Toggle can be found here: http://forum.xda-developers.com/showthread.php?t=1497558
Now, as the title says, I'd like to share with you my LMT configuration. There are many things that I'm currently unable to understand about how LMT should actually be configurated, I just used a trial&error approach, but the result I got is more then decent and worthy of being shared IMO. If I'll get some suggestion on how to improve what I did I hope to turn this post in a clean LMT ISAS guide for the Nexus 4.
PLEASE NOTICE that I didn't want to use the pie and I (almost*) didn't use LMT's gestures. The following configuration is for ISAS only.
That's because I wanted to get rid of softkeys and still have an easy to use and reliable N4. Complicated gestures tend to be hard to use and to reproduce consistently, they will give you an hard learning curve and will slow down every operation. Here I'm trying to get the benefits of gestures without making everything overcomplicated.
Now... let's get into it, I'm gonna use pictures to make everything easier to understand
This is what I ideally wanted to get:
{
"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"
}
Each colored part corresponds to a ISA on LMT
YELLOW is ISA 1 (bottom left), assigned to BACK
RED is ISA 2 (bottom center), assigned to HOME
BLUE is ISA 3 (bottom right), assigned to RECENT APPS
GREEN is ISA 9 (left bottom), assigned to OPTIONS
ORANGE is ISA 6 (top right)
this is an optional one that I wanted to add. It's assigned to search longpress, wich triggers an activity of the app "Screen Off and Lock". Basically it locks the screen with a swipe.
Sadly, if you assign the ISAS as shown without changing any value within LMT your ISAS will look nothing like the picture, you'd get something like this:
Why? I promise I don't know. I read the posts about how to use LMT, but I couldn't really understand how the 4 settings for ISAS work. So as I said, I went for trial&error. At first I thought that "Activation area thickness" was the setting I had to modify to get what I wanted, but it didn't help in any way, and the same happened with "Min bbox size", so I left those two as they were by default.
Then I found out that increasing the value for "Touchscreen to screen factor Y" reduces the colored rectangles areas. I found the value 209 to be ideal. The rectangles were now more like lines closed to the frame, but many things were still off. Here's how it looked like:
The home button is far too small, everithing is too much to the left and I don't really know what the heck orange is doing down there.
Finally, I changed the "Touchscreen to screen factor X" value to 250, and it got me to my final result
It's not perfect, but it's pretty close. I would like yellow red and blue to be better centered, but this configuration is really reliable and easy to use. It actually took me some time to realize that it's not exactly as I wanted it, the only thing that you have to remember if you you're gonna use this, is to stay well to the right when you want to swipe into recent apps.
If you apply this settings you will be able to use easy gestures that can't be activated by mistake while you are using other apps or games and you'll gain precious space on your screen.
My final LMT values are:
Min bbox size: 1 (default)
Activation area thickness: 80 (default)
Touchscreen to screen factor X: 250
Touchscreen to screen factor Y: 209
*I also enabled the X shaped gesture on LMT and associated it with FullScreen Toggle. If anything goes wrong while you are using your phone and you can't open the app drawer to get to FullScreen Toggle and enable the navbar, just perform the gesture, toggle the navbar back and reboot your phone.
Known issues with this configuration.
There are two of them.
First, since you have an ISA for options, you will be able to use the options in any app that has an option menu. The problem is that for some reason when FullScreen Toggle is activated you will not be able to see the 3-dots on-screen icon that opens the menu on any apps. That icon disappears from the top right corner or wherever it's supposed to be. That means that you will have to remember which apps have an option menu or just try to swipe and open it in case there is one.
Second, with LMT ISAS change positon properly when you go from portrait to panorama mode only if you rotate your device 90° to the left. If you rotate your device to the right ISAS from the bottom go to the top and ISAS on the right side go to the left side and viceversa.
However this is not a big problem to me and maybe it will be fixed by LMT's developer anyway.
Sorry for the long post and for any grammatical error (probably a lot). Hope someone finds this intresting and helpful
Cool guide thanks.
Did you try GMD gesture control? Seems like it would be easier to setup how you like. Complex or simple. I guess if you got LMT working fine then its all good.
jarayn said:
Cool guide thanks.
Did you try GMD gesture control? Seems like it would be easier to setup how you like. Complex or simple. I guess if you got LMT working fine then its all good.
Click to expand...
Click to collapse
I tried it but I was not satisfied with it. It's really great and extremely customizable, but in my expirience it's a bit buggy, it gave me problems right after the boot, can't remember if the auto-start was too slow or if there was actually something worse then that.
Also, it doesn't allow you to hide the navbar only, if you want to hide the navbar you have to hide the status bar too.
Marlon90 said:
I tried it but I was not satisfied with it. It's really great and extremely customizable, but in my expirience it's a bit buggy, it gave me problems right after the boot, can't remember if the auto-start was too slow or if there was actually something worse then that.
Also, it doesn't allow you to hide the navbar only, if you want to hide the navbar you have to hide the status bar too.
Click to expand...
Click to collapse
Ah ok. I dont use the hiding functions at all just use the Rom for that. The gestures aren't buggy at all and are a lot easier to set up than lmt. Also you get the launch pads.
Anyway it doesn't matter. It's a good guide and lmt is free so that's something.
Awesome post, thanks!
2 Questions...
Is there any way I can swipe back with the keyboard up without typing anything? I end up with a million drafts using LMT.
Also, is there a setting to actually see the areas like you show them for the touch locations?
ace7196 said:
Awesome post, thanks!
2 Questions...
Is there any way I can swipe back with the keyboard up without typing anything? I end up with a million drafts using LMT.
Also, is there a setting to actually see the areas like you show them for the touch locations?
Click to expand...
Click to collapse
First answer... this kind of things are the ones that bother me too with gestures, and doing what I showed in the OP I specifically tried to eliminate or reduce them. My answer to that problem was having a little line instead of a rectangle, and not so tiny that it's hard to trigger the gesture. It works well for me, and I think it requires very little getting use to.
Try it yourself if you want and maybe accomodate it to yur preference. Maybe you will type something from time to time but I hope the guide makes it so that it happens rarely.
Also, I never tried this on another N4... I don't see why it shouldn't work the same way for others, but a little feedback would be a very good thing.
As for the second question, there's no such setting that I know of, you should ask to the develoer of LMT. If there was such an option it would be so much easier to configure the app perfectly.
Fyi: touchscreen to screen factors for the nexus 4 are 200/200. It's written in the OP.
Hth!
Sent from my Nexus 4
noname81 said:
Fyi: touchscreen to screen factors for the nexus 4 are 200/200. It's written in the OP.
Hth!
Sent from my Nexus 4
Click to expand...
Click to collapse
I know that, but does it work for you? On my device it does not, if I don't mess around with X and Y I always get rectangles
Marlon90 said:
I know that, but does it work for you? On my device it does not, if I don't mess around with X and Y I always get rectangles
Click to expand...
Click to collapse
200 by 200 work best for me. OP: Are you able to simple press those hidden areas, or do you have to do a small swipe? I have to do the latter.
Yes these are the correct values to divide each side of the screen into 3 areas with equal size.
Sent from my Nexus 4
noname81 said:
Yes these are the correct values to divide each side of the screen into 3 areas with equal size.
Sent from my Nexus 4
Click to expand...
Click to collapse
Well, then I guess I'm left with a big pile of nothing... What happens to me is I have big areas in wich a swipe triggers the action. At 200 they take a big part of the sceen and if I increase Y even slightly they become lines, but some other things are off as I said. I've read around about people not being able to get ISAS to work and I thoght I was into something, but if that's just me then I'm at a loss... I guess I'll do a nanobkp and wipe and see if everything start working with 200/200
Great!, thanks for the guide.
tyraelasd said:
Great!, thanks for the guide.
Click to expand...
Click to collapse
yeah, you are welcome... read the rest of the thread, chances are this guide is useless for most people
jarayn said:
Cool guide thanks.
Did you try GMD gesture control? Seems like it would be easier to setup how you like. Complex or simple. I guess if you got LMT working fine then its all good.
Click to expand...
Click to collapse
I use both LMT and GMD for different gestures and I'm pretty satisfied, I also use glovebox for frequently used apps.
My setup is a little different, when I'm from the pc (and hopefully I'll remember XD) I'll share also my setup with you
Sent from my Nexus 4 using xda app-developers app
I personally use the Extend Desktop feature easily accessible from the power button on CM. Probably the way to go if you already have a custom ROM.
my gestures setup
I use, as I said, both LMT and GMD for my gestures setup. I tried a bit to emulate ubuntu for phones. (I also use glovebox as you see)
(In the image, the rectangles are actually the area you have to swipe to activate the gesture)
GMD custom gestures:
with a swipe from the left center you go home
with a wipe from the right center you go to the previous app
LMT ISAS:
swipe form the bottom center to go home
swipe from the bottom left to go back
swipe from the bottom right to recent apps
swipe from the top right to go back (useful when you have the keyboard open and you don't want to accidentally type)
the settings for the apps are the following
LMT
min bbox (how much do you have to swipe to activate the gesture: 5
activation area thickness: 25
touchscreen factor x,y: 200
GMD
gesture size (under "advanced"): 492
home and prevapp gesture may have to be disabled when keyboard is on depending on your keyboard
I'm pretty satisfied with this setup, only little thing that bothers me is that sometimes when I type a bottom gesture is activated, but it happens very few times
Im testing this Now, thanks
I like it. I had to use 100 instead of 80 but works mint.
issues with typing is messing with this. Also its hard to swipe up to go back on some apps. It keeps opening the keyboard.
I just wanna thank the OP and everyone on this thread. I read all the responses and was able to get it working perfectly for me. I like this setup way more than using PIE.
Hi, on request of our fellow user @Viper_21 i built a tool that gives a bit more control to the touch2wake feature built into some custom kernels like googy_max and other kernels.
You have options to configure touch2wake on a more finegrained basis and up to higher values (seconds and minutes) as well as a different value for when headphones are connected. Also you can set it to forever when connected to a power source.
While some may consider this as useless, this may be helpful for special usecases as in car, where you can't easily unlock your device normally, or at home. I didn't even have the need for such an app until i did the first tests with it.
If you think it could be a nice to have thing, feel free to download and please leave a comment on how you use it and also about any bug you came across.
Download: https://app.box.com/s/4n2r7f1zze2xtdvrlz35 v1.0.8
{
"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"
}
Changelog:
14-02-12 v1.0.8
workaround for Devil2 kernel proximity issue thanx to @-MaD-
13-09-26 v1.0.7
Built with tasker 4.2beta8 (fixes manual input issue)
Better positioning and sizing of number pickers to support touchwiz design
Added toast message when value applied
13-09-26 v1.0.6
Added current timeout Display
Changed sliders to number pickers
Number pickers now always show standard timeout
13-09-24 v1.0.5
Initial public release
Thanx to:
Googy_Anas for his amazing kernel
Viper_21 for idea and testing
Pent for his allmighty Tasker tool
This App is free and without ads,
if you like it, just hit the thanx button!
If you feel generous, you can even
(no beer please, i dont drink!)
i got something weird, it doesn't require Root Access ?
maybe you should add a pop-up to tell that setting has been applied.
most important of all !!!
why can't you make number a little bigger ...
Nope, root acccess is not required to access sys/class/... folder. Realized already with scoobycontrol.
What number you want bigger?
_________________________
tapatalked from GalaxyS3
FadeFx said:
Nope, root acccess is not required to access sys/class/... folder. Realized already with scoobycontrol.
What number you want bigger?
_________________________
tapatalked from GalaxyS3
Click to expand...
Click to collapse
I mean display it in bigger size...
Sent from my GT-I9300 using xda premium
qtwrk said:
I mean display it in bigger size...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
ah, now i know what number you mean, but its part of the slider element in tasker, i can not modify this. only option is to have an extra number display somewhere but i think in near future i am gonna change the sliders against number pickers anyways....
the popup is planed for next release...
tapatalked from MK908v3
Is this similar to the PGM app in nexus line?
nakawanaoki said:
Is this similar to the PGM app in nexus line?
Click to expand...
Click to collapse
I have no idea what pgm app is about... can you give more info?
Edit: found it, but no, its different.
Touch2Wake is a kernel feature that lets you wake the device by a simple touch for a given time after screen goes off by screen timeout. No gesture needed at all.
This app gives control of the time you have from screen off to wake the device, but also lets you choose different time for headphone mode or when connected to power source.
_________________________
tapatalked from GalaxyS3
New version is out...
_________________________
tapatalked from GalaxyS3
FadeFx said:
New version is out...
_________________________
tapatalked from GalaxyS3
Click to expand...
Click to collapse
Something funky with 1.06.... I don't see the number "rollers" as shown in your screenshot. Above each number there is only an up arrow, no down arrow below them. So can only increase numbers for now.
If I tap the number to enter a value manually, then screen gets all mangled when keyboard pops up and impossible to work with,
-Viper21
Excuse my ignorance, but what does touch to wake do?
Sent from my GT-I9300 using xda premium
Viper_21 said:
Something funky with 1.06.... I don't see the number "rollers" as shown in your screenshot. Above each number there is only an up arrow, no down arrow below them. So can only increase numbers for now.
If I tap the number to enter a value manually, then screen gets all mangled when keyboard pops up and impossible to work with,
-Viper21
Click to expand...
Click to collapse
thanx for reporting, can you provide a screenshot please?
Manguish said:
Excuse my ignorance, but what does touch to wake do?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
please read the thread, i think i already described what it does. also you need to have a kernel installed that features Touch2Wake also called Touchwake.
Edit: ok, i did not... so here with the words of ezekiel, the creator of touchwake:
So with Touch Wake, one can wake the device from suspend (for a certain user-defined time after screen off) by touching the touchscreen or the touchkeys. Combined with a OS level tweak which disables the lock screen on timeout for a certain time or altogether (for example in CM 7.03, but also available as standalone apps from the Market), one can achieve the same functionality as Screen Dimmer. Compared to Screen Dimmer, Touch Wake has the advantage that the screen will not be blanked as long as the FLAG_KEEP_SCREEN_ON is set and also the battery drain while the screen is off will be significantly less because only the touch controls are kept enabled and the Android OS and running apps are properly put to sleep. For the record, with Touch Wake, while the touch controls are still enabled, the kernel is kept in a wake lock, so the battery drain will still be a little higher than for the normal stock screen lock...
Click to expand...
Click to collapse
tapatalked from MK908v3
FadeFx said:
thanx for reporting, can you provide a screenshot please?
Click to expand...
Click to collapse
Attached to post.
Viper_21 said:
Attached to post.
Click to expand...
Click to collapse
Thanx, try this one please:
Link removed
_________________________
tapatalked from GalaxyS3
FadeFx said:
I have no idea what pgm app is about... can you give more info?
Edit: found it, but no, its different.
Touch2Wake is a kernel feature that lets you wake the device by a simple touch for a given time after screen goes off by screen timeout. No gesture needed at all.
This app gives control of the time you have from screen off to wake the device, but also lets you choose different time for headphone mode or when connected to power source.
_________________________
tapatalked from GalaxyS3
Click to expand...
Click to collapse
I guess i need this hehe. I've been looking for this since i moved from nexus to s3. it will save my physical hardware buttons.
FadeFx said:
Thanx, try this one please:
https://app.box.com/s/22ce4gumroy7h887wpuc
Click to expand...
Click to collapse
Full screen is better, but not perfect (the decrease arrows appear now but are smaller than the increase arrows). Check attachment.
Keyboard mode is is still mangled like before.
Note that if I make a change to the headset value using arrows, then tap one of the global values to manually enter a value, then press back key, the headset value I chose before is not stored (goes back to previous value). Not sure if this is expected behaviour, but because the headset value has not Apply button, I owuld've expected any change to it's value be automatically applied as I change it.
Just as a minor improvement, you might want to add a Cancel button for those who made a change but want to exit without applying latest changes.
Headset values in fact should be applied immediately. Have to look at that issue a bit further. Cancel button is not needed imo.
For the graphics thing i can get that sorted, just a matter of size... with the manual input thing i need to wait for an answer from tasker dev, as it seems it is not meant for this.
Edit: just tested, and the headset values in fact are applied but on back the old values appear, when you exit the app and open it again you see that the values are applied thou...
_________________________
tapatalked from GalaxyS3
Viper_21 said:
Full screen is better, but not perfect (the decrease arrows appear now but are smaller than the increase arrows). Check attachment.
Keyboard mode is is still mangled like before.
Note that if I make a change to the headset value using arrows, then tap one of the global values to manually enter a value, then press back key, the headset value I chose before is not stored (goes back to previous value). Not sure if this is expected behaviour, but because the headset value has not Apply button, I owuld've expected any change to it's value be automatically applied as I change it.
Just as a minor improvement, you might want to add a Cancel button for those who made a change but want to exit without applying latest changes.
Click to expand...
Click to collapse
Another testie, should fix all issues (thanx pent for latest tasker beta) except the one where values jump back...
Please report if now you have the full arrows.
https://app.box.com/s/8saq5lpikoggdw8sov3e
_________________________
tapatalked from GalaxyS3
FadeFx said:
Another testie, should fix all issues (thanx pent for latest tasker beta) except the one where values jump back...
Please report if now you have the full arrows.
https://app.box.com/s/8saq5lpikoggdw8sov3e
Click to expand...
Click to collapse
Yep, 1.07 is looking good (except for the back issue of course). Thanks for the quick fix.
PS. Liking the new controls much better than the previous sliders.
Sent from my GT-I9300 using Tapatalk 4
Viper_21 said:
Yep, 1.07 is looking good (except for the back issue of course). Thanks for the quick fix.
PS. Liking the new controls much better than the previous sliders.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
That's the main reason why i implemented this, sliders are quite inaccurate with higher ranges.
_________________________
tapatalked from GalaxyS3
Great!! Thank you!:good:
I've put together a Tasker project (based on the information I found in this post) which allows the OP5's capacitive button backlights to be kept on all the time and to easily be switched back and forth between different states, via either a popup dialog or quick settings tile. I've only used it on Android OOS versions of Oreo 8.1 and I have no idea if it works on Pie.
Once the project has been downloaded and imported, follow these steps to get things working and looking right:
If you plan to use the popup, set a shortcut to open the task "Backlight Status Control With Icons", this will open up a dialog from which you can choose how you want the backlights to behave. There's also a profile and tasks included to set up a quick settings tile to cycle through the different settings. The dialog and quick settings tile can be used alongside each other, as can the native settings app, nothing should cause conflicts.
Dialog / Scene icons: You can use the dialog as-is, but it'll look stupid and you'll get laughed at, which is why I've uploaded icons for you to add to it. It isn't hard to do. First, download the attached icons zip file and extract it wherever. In Tasker, open the scene "Backlights Menu" for editing and click on the "AZ" icon at the bottom left. This will open a list of all the scene elements. There are three icon elements, open these one at a time and point them to the corresponding icons from the extracted zip (Image>>Local Media>>extracted folder). There are also three dividers which all use the icon "divider.png", plug these in and you're all set!
Quick Settings tile: The profile and task I set up cycle the button backlights through each of the three states (default>>always on>>always off). To set a custom QS tile, pull down quick settings and click on the pencil icon at the bottom right to open it for editing. On the bottom half of the screen are the unused tiles. Tasker has three tiles available to use, the one farthest to the right is number three, and that's the one I've set up the profile to use. (If you're already using that one, open up the tasks "Backlights QS Tile", "Backlight Reset QS Tile" and "Backlights Kill QS Tile" and edit the actions in those so they don't conflict with your current setup.) Drag that one to the top half of the screen where the active tiles are, get everything arranged how you want it and then back out and go and open up Tasker. Import the project if you haven't already. Tap on the task ""Backlights Reset QS Tile" to open it and tap the play icon at the bottom left. The tile should now be initialized.
Recommended: I put a couple icons in the zip for the QS tile, "icon_default.png" and "icon_off.png". They should be added to the tasks "Button Backlights Off" (icon_off.png), "Button Backlights On" (icon_default.png), and "Button Backlights Default" (icon_default.png). Add them by opening each task for editing, clicking the grid icon at the bottom of the screen, and then navigating to the extracted icons (Local Media>>extracted icons folder).
Hello, Thanks for the work.
Do you know if it is possible to increase the brightness?
AlexCmb said:
Hello, Thanks for the work.
Do you know if it is possible to increase the brightness?
Click to expand...
Click to collapse
I'm absolutely sure I did find something involving scripts to adjust the brightness, but right now I can't seem to find it, I'll let you know if I do.
OK, I'll go ahead and upload the continuation of my work. It's a Tasker project which, when triggered, pops up a dialog with the options of setting the backlights always on, always off, or the default behavior; basically just a cleaner and easier way to toggle the settings back and forth. It also forces the lights off almost as soon as the screen turns off, as well as when the daydream/screen saver kicks in. I would love to export this as an apk, but I haven't managed to make that work, so Tasker (and root) are required.
Import the project into Tasker and set a shortcut/trigger for the task "Backlight Status Control", it's pretty much self-explanatory from there.
Update: Figured out how to get App Factory to work, so now there's an installable apk for those who don't have Tasker installed. Still requires root, of course, and I would also recommend turning off battery optimization for the app and clearing caches, it behaved a bit strangely before I did that. If you have Tasker, I recommend importing the project anyway as it seems to run just a touch faster.
All links are in the OP.
New version up, the main difference is that the chosen state survives a reboot whereas before rebooting with the lights set to Always On caused the lights to actually be always off when the device restarted. I probably fussed with the icons a bit as well, can't remember if I had already done that or not.
Links are in the first post.
And another one. This version fixes two things. First, it only keeps the profiles active when they're actually needed rather than all the time, giving you probably a minute or two of extra battery life. And then it (hopefully) fixes the last potential conflicts when switching states in the device's settings app rather than this project's dialog. This required an extra one each of profile, task and variable as well as adding some actions to a few existing tasks.
As of right now, I'm only uploading xml's, as the exported apk's have been unstable when I've tested them on my device. If you really want to try it and don't have Tasker installed, pm me and I'll send you the app to install at your own risk.
Anyone who has downloaded and imported the xml may have correctly guessed that I don't have a whole lot of experience with Tasker. I would like to take this opportunity to invite anyone who has noticed something that could be done better and/or differently to give me honest feedback. As simple as this project is, it has nevertheless been frustrating at times and I would love to have the benefits of others experience.
Can't import, Tasker says the project "contained bad data." File seemed to download fine, 41.83 kb.
smalis said:
Can't import, Tasker says the project "contained bad data." File seemed to download fine, 41.83 kb.
Click to expand...
Click to collapse
Sorry to hear it's not working for you. I've successfully downloaded and imported the project using two different devices, so the file itself doesn't seem to be the problem. It's possible, of course, that your download somehow got mangled along the way, so if you haven't already, try downloading it again and see what happens.
And... I'm honestly not sure what other advice to give you. Google just turned up really basic stuff like making sure you're not in beginner mode and that you're not actually trying to import it as a task or profile, stuff like that.
Tasker can be massively frustrating and picky, and I'm far from being an expert on it. Considering this is the first real feedback I've gotten on this thread, I don't know if anyone else has had similar issues, I just assumed no news is good news and that it works for everyone who's tried it. If anyone else has any ideas about why this would happen, feel free to share!
New xml up. No new functionality, I just debloated and cleaned things up a bit. Instructions in the first post still apply.
Updated xml now with HAPTIC FEEDBACK omg lol! Also changed/added quite a bit of stuff to hopefully make it run a bit more efficiently in the background, so a few less toast notifications and magisk log entries to look at, otherwise nothing really noticeable.
EDIT: Apologies to those who already downloaded the new one, but I just updated the update :/ Maybe it's just placebo, but it feels like decreasing the vibrate duration made it feel a bit more responsive, no need to redownload if you're already happy with it.
Any screenshots of this same in action?
arvindgr said:
Any screenshots of this same in action?
Click to expand...
Click to collapse
I mean, the buttons aren't actually on the screen so no, I can't really screenshot how it looks. If you want a screenshot of the dialog box that you use to choose the state, then sure, I can do that...
{
"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"
}
I totally forgot that Tasker lets you set Quick Settings tiles! So I've uploaded a new version that can set up a quick tile to cycle through the button states, it's disabled by default and naturally requires a bit of work to get it going but the instructions are, as usual, in the first post along with the attachments. Note that if you're going to use the quick tile you might also want to download the new icons.zip as well, check out the instructions and screenshots to see how it looks. Otherwise the only other change is the dialog pop-up got a bit smaller and very slightly transparent, there's a screenshot of that as well to help you decide if it's worth the bother.
EDIT: If you had problems with the QS tile not cycling through the settings correctly, download the newest version, it seems to have fixed it. Sorry for the inconvenience.
New one up. The last version was inconsistent updating the QS tile when setting the lights from the settings app. Let's see how I screwed up this one then. Link and instructions in the first post, blablabla...
Another week, another try to make the QS tile behave the way I want. Seems to be working over the last days of testing it, but then I say that every time. I also changed some task names so that the labels under the QS icons are accurate, and I uploaded a new icon zip with icons that imo look better in the OOS beta builds, the ones for the stable builds are still in there as well. You guys are smart, you'll figure it out.
Hi, I'm quite new with the Tasker projects! I have tried this one on my Xiaomi Redmi Note 4x (Android 7.0 Xiaomi.eu) and Samsung Galaxy Note 2014 Edition (LineageOS 14.1). I wanted to achieve buttons backlight when charger plugged in, but without screen waking. On Xiaomi it seems to work fine, but on Samsung I ended up with the error:
16.48.31/E Run Shell: ->
16.48.31/E Run Shell: ->
16.48.31/E Run Shell: ->
16.48.31/Shell runBackground echo 1 > /sys/class/leds/button-backlight/brightness root: true timeout: -1
16.48.31/Shell start process-thread ID 341
16.48.31/E add wait type Shell1 time 2147483647
16.48.31/E add wait type Shell1 done
16.48.31/E add wait task
16.48.31/E Error: 1
Can somebody explain me in a simple manner, what is wrong? I'm still begginer with Tasker ?
Lord Sithek said:
Hi, I'm quite new with the Tasker projects! I have tried this one on my Xiaomi Redmi Note 4x (Android 7.0 Xiaomi.eu) and Samsung Galaxy Note 2014 Edition (LineageOS 14.1). I wanted to achieve buttons backlight when charger plugged in, but without screen waking. On Xiaomi it seems to work fine, but on Samsung I ended up with the error:
16.48.31/E Run Shell: ->
16.48.31/E Run Shell: ->
16.48.31/E Run Shell: ->
16.48.31/Shell runBackground echo 1 > /sys/class/leds/button-backlight/brightness root: true timeout: -1
16.48.31/Shell start process-thread ID 341
16.48.31/E add wait type Shell1 time 2147483647
16.48.31/E add wait type Shell1 done
16.48.31/E add wait task
16.48.31/E Error: 1
Can somebody explain me in a simple manner, what is wrong? I'm still begginer with Tasker ?
Click to expand...
Click to collapse
You're in a wrong thread and possibly wrong forum too. This is about AoD on OxygenOS, not MIUI or LOS or Tasker.
Thanks, you helped me a lot :good:
david19au said:
You're in a wrong thread and possibly wrong forum too. This is about AoD on OxygenOS, not MIUI or LOS or Tasker.
Click to expand...
Click to collapse
I mean, "Tasker" is in the thread title... And this thread is about the capacitive button backlights, which is what Lord Sithek is asking about, not AoD.
Lord Sithek said:
Can somebody explain me in a simple manner, what is wrong? I'm still begginer with Tasker ?
Click to expand...
Click to collapse
Sorry, I don't think I can help you, I don't really know that much about shell commands and definitely can't troubleshoot for an unfamiliar device. You'd be better off trying the Tasker forums on XDA or /r/tasker. Good luck!
Oh, thanks, it's a nicer reply It's true I rushed a little bit, I just googled "Tasker buttons backlight" and I didn't check what device is actually considered I'm still newbie here, but I want to learn more :cyclops: Thanks for the links, I will check the threads :good:
I haven't updated this in a few months because it more or less worked; however, I still encountered problems with the quick settings tile not cycling properly after a reboot, as well as Tasker throwing errors, although these didn't seem to affect functionality. Anyway, I had a few days off during the holidays and was able to stop the errors from occurring as well as come up with a workaround (although not a real solution) for the problems I had with the qs tile. And so, I present what should be the final version of this mod. Link in the first post, along with setup instructions.
Btw, anyone tried this with Pie? I'm not planning on making the jump anytime soon, so I'm just curious if it works or not.