Database Info

[Q] how to permanently turn off touch wheel

the question is as in topic
how to permanently turn off touch wheel or whatever its called ( the round thing to scroll things and zoom in/zoom out )
i have a problem because its broken and it just goes zooming or scrolling without any reason :O
So is there a tweak to turn it off even if i'm using xandroid (especially at this system)

Use a task manager (like dotfred's or sk tools) and open up the 'Services' tool, then stop the Smarttouch.dll service. I'm pretty sure that will kill the scroll wheel. You can also delete this registry key:
[HKEY_LOCAL_MACHINE\Services\SmartTouch]
Click to expand...
Click to collapse
Just stopping the service is safer, in case there are any bad side effects.

thanks i will check it later if it works ;]

i'm afraid it didn't help. Sense interface loops with turning it on and in xandroid still the same problem with scrolling lots of times ;]

Well, it's not going to help you with android. I'm not sure why it doesn't help with sense; disable sense, that's my recommendation.

yea but i use sense all the time

[Q] Disable Tap To Click on dock.

Prime's old rom used to have an option to disable tap to click on the touch pad for the dock. It doesn't as of ver 1.9, I really loved this feature. Is there anyway to get it back on the newer honeycomb roms?

My dock has a button on the top of the keyboard to disable touchpad. Top row, 4th button from the left between Bluetooth and Brightness
Cheers!
PS: Re-read post and guess its not what your looking for......sorry

There is an app called "input settings" that disabled touch to click. It's floating around here somewhere. It was included with some of the transformer custom roms, and I think the rom has to support it to use it. Check the rom threads for it.
I really like the the app, however it never saved it's settings upon reboot, so you have to reactivate it every time you boot. Absolutely awesome app though.

Yea I've looked for the input settings APK with no luck. Supposidly the kernel can be compiled with support for tap to click disabled. I don't want to disable the touchpad completely, just tap to click.

Unfortunately the code that was in the kernel has been removed. Probably something to do with the new pointer/gestures options and the app no longer works.
If I find a way to disable the tap to click I see if it can be implemented.

Is this 3.2 specific, or specific to the transformer? I'll start digging and see what I can find.

Has anyone found a solution to this wth 3.2? Just picked one of these guys up and the touchpad is useless if it's not disabled since I keep bumping it with my thumbs when I hit space.

Auto Hide Taskbar

Hey bro i get this app from the market Honeybar it work great with root access.
I work with touchwiz work 100%.
Program tested MX Video Player,Dolphin Browser HD.

It works well and I suggest using Button Savior in conjunction. Barely seen my taskbar in a week

Works pretty well, main problems I have with it are accidentally re-enabling the taskbar in games (tapping near the bottom), and also accidentally hiding it when trying to hit the 'menu' button in portrait mode. They're too close together so it's hard to avoid hitting it.
I asked the author about the possibility of other trigger locations, or gestures, and he responded but didn't sound like he planned to do anything soon.

I installed HB myself, and although it is nice in some ways to get the taskbar (I use that reference with tongue'in'cheeck) out of the way, there are too many apps I have that place "menu" in the location of the hidden button even when I set it to shift left. Many apps I have to rotate to landscape to get to the apps settings menu hidden behind the shift-left positioning for HB. It's just not a sound UI choice.
The option to just leave the taskbar hidden and use Button Savior is better, but it's like using one hack to make another one work halfway correctly in its effects. HB needs more development and it doesn't look like it's going to happen as of now.

koreanschoolkid said:
It works well and I suggest using Button Savior in conjunction. Barely seen my taskbar in a week
Click to expand...
Click to collapse
Thanks very much for your info. Yeah... this Button Savior is a real true name in case of the HoneyBar's gone somewhere..

Problem I see with using Button Savior all the time is that you do lose the notifications.. and then it's still easy to accidentally bring back the real bar when playing games etc. Oh well.

speedrabbit said:
Problem I see with using Button Savior all the time is that you do lose the notifications.. and then it's still easy to accidentally bring back the real bar when playing games etc. Oh well.
Click to expand...
Click to collapse
I don't know about the games... the notification is hiding except the sound but the real trouble is when the call is coming.... you have to activate the task bar to bring back the panel "Answer or Denied" (!!!)
FYI

speedrabbit said:
Problem I see with using Button Savior all the time is that you do lose the notifications.. and then it's still easy to accidentally bring back the real bar when playing games etc. Oh well.
Click to expand...
Click to collapse
I did indeed get quite angry at the loss of notifications but I was able to (sort of) get around that by changing the screen density to 171 using Blade Buddy. This set me back to a 2.x launcher.
It doesn't really work 100% however as browser, Gmail, Google Talk will constantly crash. I was able to work around the browser by just getting another browser and Gmail by uninstalling the Honeycomb version of Gmail and installing the Gingerbread version. I didn't care enough to do anything more than uninstall Google Talk.
On the positive side I no longer have to deal with the taskbar. Ever.

koreanschoolkid said:
I was able to work around the browser by just getting another browser and Gmail by uninstalling the Honeycomb version of Gmail and installing the Gingerbread version.
Click to expand...
Click to collapse
Does the Gingerbread version have the Gingerbread UI? i.e. without the multi-paned stuff? I tried loading a Gingerbread version a while back but it didn't work (just crashed). I prefer Gingerbread style -- more room for the content rather than lists of labels.

Sigilist said:
I installed HB myself, and although it is nice in some ways to get the taskbar (I use that reference with tongue'in'cheeck) out of the way, there are too many apps I have that place "menu" in the location of the hidden button even when I set it to shift left. Many apps I have to rotate to landscape to get to the apps settings menu hidden behind the shift-left positioning for HB. It's just not a sound UI choice.
The option to just leave the taskbar hidden and use Button Savior is better, but it's like using one hack to make another one work halfway correctly in its effects. HB needs more development and it doesn't look like it's going to happen as of now.
Click to expand...
Click to collapse
Yes this is exactly my only issue with honeybar. it would be nice if we could choose the right side as the "offset". Even in portrait I have space just to the right of center that would allow access to honeybar on/off and not interfere with the menu on a lot of apps.

There's a much better way to do this. Using tasker, I have a profile set up that auto hides the toolbar for certain apps and then restores it automatically when I switch away from them.
Follow the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=1301857
Sent from my GT-P6210 using Tapatalk

Yes but how do you switch away from them?

That is actually what I am trying to figure out how to do. I am trying to set it up when in specific apps it takes away the task bar but also only within these apps after something... (haven't really figured that out yet) happens it will bring it back for an exit. In a perfect world I would love to be able to press both volume buttons to close an app. Which in this case would be perfect but tasker can't do that...

I'm using task switcher pro. It lets you map a gesture to the back button or home button.
Sent from my GT-P6210 using Tapatalk

what might be cool is to "shake" device to bring back the bar.

you guy also can use AutomateIt... kind of like tasker but to me it more friendly user...
http://forum.xda-developers.com/showthread.php?t=1123423
and the pro version is cheaper too...

Using tasker I did manage to make the bar go away by shaking. Instead of setting programs to do it make it toggle the bar by using a shake. I don't have it in front of me to do step by step but if someone wants me to I can put it up.

I would most certainly love to see that "How too" Zadeis.
Thanks.

Here you go!
gucabe said:
I would most certainly love to see that "How too" Zadeis.
Thanks.
Click to expand...
Click to collapse
OK the link smaug408 put up leads to a guide on how to set up a task that when an App starts it will remove the bar at the bottom. The thing is though you no longer have a back button and get out of the app unless it has a dedicated exit button.
http://forum.xda-developers.com/showthread.php?t=1301857
I take no credit for the premade files for tasker. The thanks goes to the creator Quietthinker through that link.
-First Open the link and download the attached StatusBarToggle.zip and place the files into /sdcard/Tasker/tasks (in this case you will only need the StatusBarToggle.tsk.xml, the StatusBar_Hide.tsk.xml, and the StatusBar_Show.tsk.xml files)
-Second open tasker and go to the "tasks tab" and tap and hold the Tasks Tab at the top. An options window will come up but select Import and import all of them into tasker
-Third go to the profiles tab and tap the Green plus at the left and give it a name. ShakeToToggle can work but you can name it whatever you like.
A context window will popup and you will select Event and then the Sensor Category and finally select the Shake Event.
You can mess around with the setting for the shake gesture now or tweak it in to your liking after everything is set up up to you.
-Forth once you have the setting you like press the green check mark, select the StatusBarToggle task and you are done. Now when you shake your tablet side to side it will make the status bar go away.
Now I just happened to figure out that you can shake instead of using an app for the context. I take little credit for how this works.
This method requires Super User Permissions. It will ask on the first toggle of the bar if you allow it to remember it afterward, if not it will ask each time.

Great app. Works perfectly

Change the function of the hardware keys?

Searched around alittle to see if anyone had found any means of doing this, but didn't find anything.
Anyone know if it's possible to assing the "settings" function to the browser key?
Thanks

siggehandf said:
Searched around alittle to see if anyone had found any means of doing this, but didn't find anything.
Anyone know if it's possible to assing the "settings" function to the browser key?
Thanks
Click to expand...
Click to collapse
Look here. It has a lot of information on it. You should be able to do with relative ease.
Cheers.

Sweet!, Worked like a charm with root explorer.

Just stumbled on this thread and thought id give it a shot on my K1. Everything went fine, files were same name and in same location, mounted the dir. Rw then changed my hardware button (the one thats Home/Back/Menu), saved the file with a backup but no changes were made. I even changed the buttons in the other file showing only hardware buttons and then rebooted but still nothing...
Im thinking that since this mod was for the TPT and Im on a K1, theres something Im missing. Any K1 owners had any success with re-mapping the hardware buttons?
Sent From My K1

may need to set permissions on file
You may need to set permissions on the file before you can save. Using "File Manager HD" I had to enable root explorer and mount systems folders under the settings and then add write permissions to Group and Others in the permissions dialog, probably don't need Others but I am lazy. Don't forget to change the permissions back after you save your changes. Incorrect permissions settings can sometimes really bork things.
Also seems that the settings might be a little different under ICS, I am getting "Touchscreen Toggled" instead of the menu after setting 150 to MENU.
-j

On the Lenovo boards, it has been comfirmed in the released chineese manual, that pen only mode is avaible. SoSweet!

Menu's not allowed in ICS
Well, here is why remapping the browser button to MENU does not work in ICS, looks like we are no longer allowed to have a menu.
http://android-developers.blogspot.com/2012/01/say-goodbye-to-menu-button.html
Still playing with it but it appears that no matter what I put on the line after key 150 I just get touch-screen toggled, which is useful but not what I want.
-j
BTW doin' this on a Thinkpad Tablet

[Q] Weird Stock Browser Issue

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.