Related
Can I disable in any way middle button (home/window/start) on my device? Is there any registry value to disable this button? Or maybe some hack? I have LG E900 with installed MFG app. In this app I can see that it can test use of hardware buttons, so probably it's possible to block this middle button in some way.
I'd need to decompile and examine the MFG app, but yes, it's probably possible.
Out of curiosity, why that key in particular? Usually, people are complaining about Search (or sometimes Back) much more.
I wan to create application that user cannot leave. I already found that I can disable Search button. Back button is no problem, because WP7 SDK support cancelling using it.
Don't forget to also block camera, volume, long-press on Back (which the SDK does not officially let you block), and power...
No offense, but if you can't come up with a better use case than that, it's going to be really low on my priority list. I've currently got (not really in order):
Re-implement SetKMode for HaRET.
Fix HtcRoot on multi-threaded apps.
Enable full-unlock on stock ROMs with HtcRoot.
Enable custom policies with HtcRoot.
Explore the AppMgr databases, see what I can learn and what I can tweak.
Find an interop-unlock that works on gen2 HTC (and hopefully others).
Find a way to use HtcUtility (a working version, for HtcRoot) on up-to-date stock ROMs.
Explore modifying ROM files using HtcRoot.
Release the next version of Root Webserver.
Update my MultiTaskToggle app.
Polish up and release my AppDataBackup app (and PC utility).
Release XapInstaller app for stock ROMs (HtcRoot).
Figure out what the hell is going on with DllImport (P/Invoke - some marketplace apps can use it?!?).
... I'm honestly losing track. I know there's more. Some are small and silly, some are huge and will take months.
Mendoza32 said:
Can I disable in any way middle button (home/window/start) on my device? Is there any registry value to disable this button? Or maybe some hack? I have LG E900 with installed MFG app. In this app I can see that it can test use of hardware buttons, so probably it's possible to block this middle button in some way.
Click to expand...
Click to collapse
you can't disable middle button (home/window/start) but you can turn off vibrate with Registry code :
Code:
[HKEY_LOCAL_MACHINE\Software\OEM\KeyState]
"application_btn_vibrate3"=dword:1
text1 said:
you can't disable middle button (home/window/start) but you can turn off vibrate with Registry code :
Code:
[HKEY_LOCAL_MACHINE\Software\OEM\KeyState]
"application_btn_vibrate3"=dword:1
Click to expand...
Click to collapse
Can I do this with a locked phone?
thanks
text1 said:
Code:
[HKEY_LOCAL_MACHINE\Software\OEM\KeyState]
"application_btn_vibrate3"=dword:1
Click to expand...
Click to collapse
This entry does not power off vibration but sets the duration of the vibration at 1ms
Ok, so I may be a little iffy here.
I have tasker and secure settings w/ helper installed and I'm running the latest version of cleanrom lite.
So in secure settings I have the GPS option enabled via helper and in Tasker I'm able to select it as a misc action.
What I want to do is have it enable GPS when I launch the Map, Nav, or Places application and disable when I leave them. I think I have it set up properly, but my problem is it isn't enabling the GPS. The profile will enable but it won't change the setting.
Any feedback here?
Edit: I found the fix. I feel derpy. For anyone looking to do something similar once you have Secure Settings w/ Helper installed and you go to set the setting in Tasker do not attempt to go Misc - > GPS. It won't work. Instead select Plugin -> Secure Settings -> Configuration and choose GPS. That'll get it working for you just peachy.
soapbubble said:
Ok, so I may be a little iffy here.
I have tasker and secure settings w/ helper installed and I'm running the latest version of cleanrom lite.
So in secure settings I have the GPS option enabled via helper and in Tasker I'm able to select it as a misc action.
What I want to do is have it enable GPS when I launch the Map, Nav, or Places application and disable when I leave them. I think I have it set up properly, but my problem is it isn't enabling the GPS. The profile will enable but it won't change the setting.
Any feedback here?
Edit: I found the fix. I feel derpy. For anyone looking to do something similar once you have Secure Settings w/ Helper installed and you go to set the setting in Tasker do not attempt to go Misc - > GPS. It won't work. Instead select Plugin -> Secure Settings -> Configuration and choose GPS. That'll get it working for you just peachy.
Click to expand...
Click to collapse
Thank you mate! Was just having this problem with jellybean. Either way working on the exit function.
soapbubble said:
Edit: I found the fix. I feel derpy. For anyone looking to do something similar once you have Secure Settings w/ Helper installed and you go to set the setting in Tasker do not attempt to go Misc - > GPS. It won't work. Instead select Plugin -> Secure Settings -> Configuration and choose GPS. That'll get it working for you just peachy.
Click to expand...
Click to collapse
I'm rooted, I have Superuser, busybox, secure settings and helper all installed. I have "green circles" at each location in helper indicating that I can change all these things but when i hit "Plugin>secure settings>configuration" I only get the top half of the list...not the bottom half.
can someone help?
Edited to add: found the answer; the right side green check boxes needed to be checked.
Thank you thank you. I've been looking for this fix. love tasker not easy to use though
Thank you!
soapbubble said:
Ok, so I may be a little iffy here.
I have tasker and secure settings w/ helper installed and I'm running the latest version of cleanrom lite.
So in secure settings I have the GPS option enabled via helper and in Tasker I'm able to select it as a misc action.
What I want to do is have it enable GPS when I launch the Map, Nav, or Places application and disable when I leave them. I think I have it set up properly, but my problem is it isn't enabling the GPS. The profile will enable but it won't change the setting.
Any feedback here?
Edit: I found the fix. I feel derpy. For anyone looking to do something similar once you have Secure Settings w/ Helper installed and you go to set the setting in Tasker do not attempt to go Misc - > GPS. It won't work. Instead select Plugin -> Secure Settings -> Configuration and choose GPS. That'll get it working for you just peachy.
Click to expand...
Click to collapse
I've tried this I've set it to enabled and toggle and nothing happens when I open my satnav app waze.
Any ideas
Just as a note : be careful with this particular formula in Tasker. I use it as well, but the problem is if you're using, say, a navigation program. You open it up, Tasker sees it open, enables GPS, everything is right with the world. You're chugging along. You stop at a red light, and... get a text or something, and you tap to see it. As soon as you switch away from the navigation app, even if it's running in the background, Tasker will count that as "exiting" the program, and disable GPS (at least in my experience). Your navigation app will still run in the background but not have GPS to tell you where to go until you bring it to the foreground again.
Can you get Tasker/GPS to work on an un-rooted phone?
No.
Sent from my Evita
timmaaa said:
No.
Click to expand...
Click to collapse
Dangit.
Hi
I know in settings you can stop it from launching camera when locked, but I want it to not launch it at all.
Reason: When running I often push it by mistake and then it thows off my GPS (endomundo).
Wondering if there is a registry edit for it anyone knows of.
Read the Registry Tweaks thread on the dev&hacking forum; I found the registry key controlling the camera button's behavior just last night. I believe it's HKLM\Software\Microsoft\Shell\Camera, though I may be misremembering. Renaming or clearing out the "Application" registry value at that key should do the trick. You'll need to reboot afterward. I haven't tested this (I tested changing the button's function but not disabling it) so no guarantees, but it's worth a try.
GoodDayToDie said:
Read the Registry Tweaks thread on the dev&hacking forum; I found the registry key controlling the camera button's behavior just last night. I believe it's HKLM\Software\Microsoft\Shell\Camera, though I may be misremembering. Renaming or clearing out the "Application" registry value at that key should do the trick. You'll need to reboot afterward. I haven't tested this (I tested changing the button's function but not disabling it) so no guarantees, but it's worth a try.
Click to expand...
Click to collapse
Works perfect cheers, I just took the last number off the guid so I can turn on and off easily. Many Thanks
Two things:
Firstly, when I type in the browser the screen moves up on every key press...weird.
Secondly, the top of the screen (in expanded desktop mode, with full screen lab running) gets corrupted - legacy downloading blue lines and tabs - which should disappear. Weird.
Any ideas from the brains trust out there? It's been happening sporadically for a couple of weeks - I'm on CM10.1 Nightlies - been the same with various versions of CM10.1.
dgjl said:
can anybody explain and /or solve the following two things:
Firstly, when I type the screen moves up on every key press...weird and annoying.
Secondly, the top of the screen (in expanded desktop mode, with full screen lab running) gets corrupted - legacy page downloading blue lines and tabs - which should disappear remain in the top part of the screen.
Any ideas from the brains trust out there? It's been happening sporadically for several weeks - I'm on CM10.1 Nightlies - been the same with various versions of CM10.1.
Click to expand...
Click to collapse
Bump - any ideas? Has this really never been seen before (did a clean install yesrerday and it still happpens).
Over 100 views and no ideas? Someone must know something. Surely it's not a unique set of problems .
It's definitey an issue with the 'labs' setting - turn that off and it goes away. Any reason why this should happen? can anyone replicate this?
dgjl said:
It's definitey an issue with the 'labs' setting - turn that off and it goes away. Any reason why this should happen? can anyone replicate this?
Click to expand...
Click to collapse
Hi dgjl-
I'm replying to this post with your same settings and having none of the same problems. No scrolling when I typing, no ghosted tabs or lines above? I do have some wierdness with the cursor positioning though and positioning the cursor with the arrow keys does not work in desktop mode but does in mobile mode (user agent). Also the page seems to have a white hue like its been whitewashed.
Labs, Developer Settings, and Experimental all mean about the same thing. It means its a new feature that hasn't been fully tested so use it at your own risk. I tend to avoid these settings unless you want to be a beta test site for Asus. You may then have to disable other settings that previously worked fine to run your new setting as they may conflict. You may have to "experiment" to find the combination of settings that work together.
If you type "about:debug" into the address line, then go back into settings there is a new menu item "debug" and in there are a slew of new settings to check out. Enabling "enable cpu upload path" speeds things up, and there is also controls for OpenGL and WebGL that you might experiment with. Also try disabling "fast scroller" under the advanced settings as it may conflict with the labs flyouts. I am also running my Multi browser2RAM startup script which is the same as browser2RAM.
elfaure said:
Hi dgjl-
I'm replying to this post with your same settings and having none of the same problems. No scrolling when I typing, no ghosted tabs or lines above? I do have some wierdness with the cursor positioning though and positioning the cursor with the arrow keys does not work in desktop mode but does in mobile mode (user agent). Also the page seems to have a white hue like its been whitewashed.
Labs, Developer Settings, and Experimental all mean about the same thing. It means its a new feature that hasn't been fully tested so use it at your own risk. I tend to avoid these settings unless you want to be a beta test site for Asus. You may then have to disable other settings that previously worked fine to run your new setting as they may conflict. You may have to "experiment" to find the combination of settings that work together.
If you type "about:debug" into the address line, then go back into settings there is a new menu item "debug" and in there are a slew of new settings to check out. Enabling "enable cpu upload path" speeds things up, and there is also controls for OpenGL and WebGL that you might experiment with. Also try disabling "fast scroller" under the advanced settings as it may conflict with the labs flyouts. I am also running my Multi browser2RAM startup script which is the same as browser2RAM.
Click to expand...
Click to collapse
Thanks. I've been through the various debug settings already - what's strange is that when debug is operating (i.e., in the same browsing session as 'about:debug' is launched) the problems don't seem to occur. Is there anyway to make debug permanent - as it is on Cromi, for example?
dgjl said:
Thanks. I've been through the various debug settings already - what's strange is that when debug is operating (i.e., in the same browsing session as 'about:debug' is launched) the problems don't seem to occur. Is there anyway to make debug permanent - as it is on Cromi, for example?
Click to expand...
Click to collapse
This is the first I'm hearing about the "about:debug" settings you change not being "permanent". I don't follow you. When I change a debug menu setting in a browser session, then launch a new tab and url "about:debug" in that session, all the settings I changed in the previous session are applied to all new tabs I create. Same is true if I shut it down and relaunch the browser. The settings persist. Yours don't?
Are you running the old browser2RAM that loads the actual browser app as well as its cache into RAM ["mount | grep tmpfs" to check all mounts from the terminal] so the session data doesn't persist? If so, use my startup script 3 in my signature instead - data persists. Its a more versatile replacement for browser2RAM that works on 4.2 as well. For 4.1 and below you can run it from the terminal as su after boot. For 4.2 you need to run it as su *at boot* using either an init.d method or the Script Manager (Devwom) app.
I'm kinda liking this lab flyout! Makes for quick navigation. But this cursor thing is starting to P me O. I use Chrome instead.
@sbdags do you have any suggestions?
elfaure said:
This is the first I'm hearing about the "about:debug" settings you change not being "permanent". I don't follow you. When I change a debug menu setting in a browser session, then launch a new tab and url "about:debug" in that session, all the settings I changed in the previous session are applied to all new tabs I create. Same is true if I shut it down and relaunch the browser. The settings persist. Yours don't?
Are you running the old browser2RAM that loads the actual browser app as well as its cache into RAM ["mount | grep tmpfs" to check all mounts from the terminal] so the session data doesn't persist? If so, use my startup script 3 in my signature instead - data persists. Its a more versatile replacement for browser2RAM that works on 4.2 as well. For 4.1 and below you can run it from the terminal as su after boot. For 4.2 you need to run it as su *at boot* using either an init.d method or the Script Manager (Devwom) app.
I'm kinda liking this lab flyout! Makes for quick navigation. But this cursor thing is starting to P me O. I use Chrome instead.
@sbdags do you have any suggestions?
Click to expand...
Click to collapse
Actually I'm running your script for b2r… As for 'permanent' I just meant the menu for debug being always available, not the settings. When it's there as an option the typing doesn't move the screen up - though screen corruption still happens as described.
Using Dolphin currently as I'm a full screen addict and Chrome doesn't offer that - or flash.
dgjl said:
Actually I'm running your script for b2r… As for 'permanent' I just meant the menu for debug being always available, not the settings. When it's there as an option the typing doesn't move the screen up - though screen corruption still happens as described.
Using Dolphin currently as I'm a full screen addict and Chrome doesn't offer that - or flash.
Click to expand...
Click to collapse
Ah, gotcha. About:debug>enable cpu load path fixed some of the corruption I was having with my cursor. Its not just for speed. Developer Options>Force GPU rendering fixes random reboots and other things if you haven't tried that. Make sure you have my script version 3 for Dolphin support. That's about all I've got for you @dgjl.
elfaure said:
Ah, gotcha. About:debug>enable cpu load path fixed some of the corruption I was having with my cursor. Its not just for speed. Developer Options>Force GPU rendering fixes random reboots and other things if you haven't tried that. Make sure you have my script version 3 for Dolphin support. That's about all I've got for you @dgjl.
Click to expand...
Click to collapse
Thanks for taking an interest, Elfaure. Looking around the 'web' I don't think I'm the only one with ths issue, but there's no one out there with the solution yet. It's just strange that it started without an obvious cause...
SORTED:
I found this thread http://code.google.com/p/android/issues/detail?id=39811
I had downloaded a notifiation app which ran under Settings>Accessibility. The moment I disabled it the probem went away!
Marvellous!
dgjl said:
Thanks for taking an interest, Elfaure. Looking around the 'web' I don't think I'm the only one with ths issue, but there's no one out there with the solution yet. It's just strange that it started without an obvious cause...
Click to expand...
Click to collapse
You might want to unload my script and see if the problem persists. If it does then ? If not, then maybe some switches could be added to your mount line (nodev, nosuid, gid=...etc.)
elfaure said:
You might want to unload my script and see if the problem persists. If it does then ? If not, then maybe some switches could be added to your mount line (nodev, nosuid, gid=...etc.)
Click to expand...
Click to collapse
The solution is in my previous post - anything running in Settings>Accessibility with conflict with the stock browser/lab and cause this to happen. trouble is now I don't know what to do for a notification widget as they all use 'accessibility' and I don't want the notification bar to be visible. Good old Android - there's always something!
dgjl said:
The solution is in my previous post - anything running in Settings>Accessibility with conflict with the stock browser/lab and cause this to happen. trouble is now I don't know what to do for a notification widget as they all use 'accessibility' and I don't want the notification bar to be visible. Good old Android - there's always something!
Click to expand...
Click to collapse
So its either accessibility notifications and a different browser or labs flyouts with the stock brower - your choice. Good you got the bottom of it. That's always the first step in fixing a problem. Looks like you can't have your cake and eat it too on this firmware.
So ive been having this issue recently where the phone will turn off apps that i want to run in the background and i cant figure out a way to fix it. The biggest issue is with AdGuard. When im using it, the phone will randomly kill the background process and the vpn will turn off allowing all the adds to come pouring in. I've mentioned this issue on the oneplus forums and nobody there seems to know how to fix it. I'm considering moving to a custom rom once i find one that works well with my needs but first i want to make sure this isnt something that i can fix on the stock rom since i dont really need all the custom settings that come with custom roms. Im running the latest stable 9.0 pie/OOS.
Thanks for any help in advance
When you open the recent app tab press on the 3 dots right above the app. The press lock. That worked for me
did you set it to not optimize in battery settings?
under battery optimization. disable advanced optimization.
MrSteelX said:
under battery optimization. disable advanced optimization.
Click to expand...
Click to collapse
ive disabled all battery optimization options including adaptive battery.
whizeguy said:
did you set it to not optimize in battery settings?
Click to expand...
Click to collapse
yes ive gone into the specific adguard app and disabled battery optimization in that app
noppoer2 said:
When you open the recent app tab press on the 3 dots right above the app. The press lock. That worked for me
Click to expand...
Click to collapse
Ive enabled the lock and it still clears it and i have to reopen the app and re-enable the lock
Ive also set background process limit to be unlimited in the developer options. I cant think of anything else to do except maybe install adguard as a system app???? I've seen that this problem occured with the OP5 as well and people modified build.prop to increase the process limit, i've since found out that the option thats in the build.prop file is gone in the OP6 so i cant do that either. This is driving me crazy and i dont even know if its related to the os or the kernel.