I have Android Studio 3.1 and for some reason I am unable to scroll using the touchpad. I have to manually scroll by dragging the scroll bar on the right, and this can get very tedious and inconvenient if im working on a large project. I used to be able to two-finger scroll on previous versions of Android Studio but for some reason its just not working anymore. I have windows 10 if thats relevant. Any idea how I can fix this?
I had the same issue and found a solution by making a small change to a registry entry:
Open regedit.exe using run
Go to HKEY_CURRENT_USER -> SOFTWARE -> Elantech -> Smartpad
Change ScrollControl_Mode from 0 to 1
I found the answer here:
https://www.reddit.com/r/techsupport/comments/3lhmhq/win10_elan_touchpad_scrolling_issues/
Just go to File>Settings or Ctrl+Alt+S. Then Select Appearance in Appearance & Behavior menu. Now Scroll down to Windows option and Select the Smooth Scrolling checkbox. Below there is an image. This worked for me.
https://i.stack.imgur.com/bXApl.png
Two-finger scrolling problem generally occurs due to malfunctioning of touchpad drivers of windows 10.
Things you can try are:
Go to File>Settings or Ctrl+Alt+S. Then Select Appearance in Appearance & Behavior menu. Now Scroll down to Windows option and select the Smooth Scrolling checkbox
as suggested by #Nikhil
You have to update your touchpad drivers:
For updating driver:
Go to the Device Manager.
Expand "Mice and other pointing devices".
Right-click on your touchpad (probably Asus Support Device)
Properties.
Driver Tab.
Roll Back Driver.
Restart computer.
If it still doesn't work now try updating your touchpad driver again after rolling back.
If it still doesn't work try to uninstall your touchpad driver and reinstall it.
Important: Always Remember to restart your computer every time you make any change.
For me, the problem is often caused by other apps that are currently running. For example cmd or OneNote. After closing those scrolling works again.
Related
Similar questions had been asked for earlier versions of and I found the most recent was in October 2015. At that time users were no longer be able to drag and drop widget to Design view of activity_main.xml but were able to do so to design view of content_main.xml. Last week (late Sep 2016) I updated Android Studio to 2.2 on macOS Sierra.
The design view is now showing two views for the screen (not sure how to correctly call its name) and I cannot drag and drop widget to either of them. It simply does now allow me to drag any widget from Palette. I tried the menu File/Invalidate Caches/Restart.and it did not help.
Thanks.
In macOS Sierra i don't know why drag n drop function is not working but in windows android studio 2.2 its working under design Tab, May be some problem when you configure android studio. Please check ones
I don't have Android Studio 2.2 on Windows to try it yet. Possible reasons I can think of includes the following:
Android Studio 2.2 does include something that caused this on macOS Sierra. And I happened to updated the Android Studio and mac OS last week;
My Android Studio has been installed since probably 1.4 and has been updated for each release. It's not fresh new 2.0 install. Uninstall and reinstall will be a lot of pain and time wasting.
My mouse is wireless Logitech M510 which was is connected to a four port StarView DVI KVM switch. But this is a wild guess. It's unlikely the culprit unless one had same issue with windows mouse but not with Mac mouse. I am using 2012 mac mini.
I had the same problem but then I found this useful answer https://code.google.com/p/android/issues/detail?id=211582, and this post give me the solution:
11 nan.y...#gmail.com
OK, finally I found how to solve this problem. But it is still strange. I think may be it is still a bug in AS 2.2.
Key is Preferences->Appearance->UI Options->"Drag-n-Drop with ALT pressed only". This is checked as default both in my AS2.1.1 and AS 2.2.
Then
1) In AS 2.1.1, only I press ALT and then drag items in Project Pane, I can move java class from one package to the other one. In layout editor, I can drag widget from palette to layout without ALT key pressed.
2) In AS 2.2, same as AS2.1, I need to press ALT to drag items in Project Pane. But in layout editor, no matter I press ALT key or not, I cannot drag widget from Palette to layout. The strange is here:
2-1) I uncheck this option, then I can drag item in Project Pane without ALT key pressed, but I still cannot drag widget in Palette.
2-2) I check this option again, then I need to press ALT to drag item in Project Pane. AND THEN ! I can drag widget in Palette with ALT key pressed.
2-3) After two step above, if I check this option I need to press ALT to drag a widget from palette. If I uncheck this option I can drag widget directly without ALT press.
Now, dragging widget in Palette works properly in my AS 2.2, but I still think this solution is wacky. I hope my solution could help to dig out the root cause of this issue.
I am using
Android studio 2.1.1 Build #AI-143.2821654 build on April 28, 2016.
JRE: 1.8.0_77-b03 x86_64
OS X El Capitan 10.11.3
I have met Android studio mouse problem a lot of times recently. I cannot use mouse to click anything in Android studio. All I can do is to use keyboard and shortcuts.
And only solution I found is to restart my whole computer. I have noticed that there is problem in other version of Android studio. So my question is that how can I deal with it?
I found that sometime I can reproduce this problem after I middle click the Editor Tab to close tab.
Just had this issue this morning. Android Studio wasn't responding to mouse click events. The odd thing was that it was responding to mouse position (tooltips, hover effects).
I updated to the newest version of Android Studio using Android Studio > Check for Updates and navigated the dialog menu with tab and spacebar. This did not solve the issue, but is probably worthwhile to try.
I'm not 100% certain what solved it, but I started pressing other buttons on my mouse (right-click, middle click, etc). Eventually it started accepting my left-click input again.
It happened to me with Intellij IDEA, when a dialog window has been opened by the IDE, but for some reason it is hidden behind the main window. You may try to find if there is any open dialog and close it.
I had the same issue on my Android Studio (4.1.1) on my MacBook Pro (macOS 11.1). For me, I just restarted my MacBook and the mouse click started working on Android Studio.
Not sure what caused it.
The mouse clicks thing and closing the android studio from task manager and open again did not help for me. im not sure why but CTRL+ALT+DELETE and going back to desktop fixed the problem.
Here is how I fixed this issue:
Use keyboard arrows and tab key to navigate to google assistant
Press enter to launch it
type and search "Power Menu : Software Power Bu"
navigate to install the app in results from playstore
Open the app after install and accept & set permissions
Open Power Menu now And you will get Android Power Options
Navigate to "Restart" and restart device
Viola!!! Now Emulator clicks works
In my case it happened, because one of the plugins started crashing in the loop, somehow disabling mouse click handlers.
Verify logs
Log file location:
~/Library/Logs/Google/AndroidStudio2020.3/
Remove bad plugins
~/Library/Application Support/Google/AndroidStudio2021.3/plugins
The genymotion emulator starts from AndroidStudio. It shows its white screen but never goes beyond that. It never comes to the home screen. Tried running the app. does not work. I have tried API 18 emulator. does not work. I have tried changing sdk path, setting android_home. does not work??
Did you checked logs for errors or possible explanation? Do you have both VirtualBox and Genymotion configured properly? It is hard to answer your question more accurately cause you did provide little information.
Going into my BIOS and enabling Intel Virtualization Technology under the CPU Options, and then going into GenyMotion and changing the device's # of virtual processors fix this issue for me.
Some time ago i also faced the same problem ... you can try above all suggestion but what worked for me is :-
Downloading Oracle VM VirtualBox
Here is the link , DOWNLOAD and install it.
http://www.oracle.com/us/technologies/virtualization/virtualbox/overview/index.html
I often have the same problem. If I delete the virtual device and then reinstall it, it usually fixes the problem for me.
To delete it, open the genymotion desktop application
Delete the device that's giving you the white screen - select the device and then click on the trash can icon
After it's deleted, reinstall the device - press add, search for the device, select it and press next twice
The device will be installed again, and it may start properly this time around.
I use android studio 0.4.2 and logcat does not work (its just empty). USB debugging is enabled, filters are disabled and log level is verbose. Any ideas?
In logcat, try going to the bottom right corner where there is a ">>" and select that. It restarts it.
Click on the "Debug App" Icon next to the "Run App" Icon or press SHIFT + F9. That seems to do the trick for me.
Try going to developer settings on the phone, and scrolling to the "Monitoring" then "Enable OpenGL Traces" and select LogCat.
I tried everything. I unintentionally found that empty tags never show. If you are using empty tags, like me, try filling with some letter (blank spaces didn't work for me).
On your android monitor:
Restart your LogCat.
Set no filters because Android studio 2.2 has Firebase.
Clear your searching filter.
Select your running device.
If not work clear Android studio caches. File->invalidate caches/restart
When apply all way but still not working then use Android device monitor. Tools -> Android -> Android device monitor.
In my case, restarting Android Studio works for me.
Go to "Window -> Preferences"
From the left panel, expand "Android" and select "Logcat". Check if "Show logcat view if message priority is atleast:" is equal to "VERBOSE". If needed, select "VERBOSE" and apply.
Now you can see your device events in LogCat.
In my case, it usually takes 20 or more seconds for my logcat to display anything. After it does, I see "debugger waiting to settle" messages. This happens every single time.
Try waiting a while to see if it ends up showing up.
Old question, but the issue seems to occur frequently while running Android Studio 1.1.0. This often happens after I clear all existing log.
When it does, I tap the restart icon (green curved arrow on top of a grey square) and it start working again.
I had the same problem and solved it in the device developer options by disabling and enabling Usb debugging.
To add to this thread of solutions,
Check for if you have multiple devices connected. Than select the device that you want logs from (upper left corner on logcat window). Sometimes, different device is selected rather than one you are debugging your app on. Hope this helps.
In my case, I had two Android phones plugged in for debugging. Switching phones, using the drop down box, didn't do a thing, so I:
-unplugged both
-restarted Android Studio (and the project)
-plugged in the (one) device for which I wanted to see the logs
That did it for me. Logs were back ... now just to fix the code.
In case you make it down here, #Maarten's comment above worked for me. Close Android Studio then adb devices at Ubuntu terminal:
ewan#xxxx:~/AndroidStudioProjects/projectx$ adb devices
List of devices attached
adb server version (41) doesn't match this client (39); killing...
* daemon started successfully
FA7Bxxxxxx2 device
Restarted Android Studio and logcat window worked again.
UPDATE: d'oh I found that I was inadvertently using version 39 from the terminal window whereas Android Studio was using 41
I'm developing an android app on Eclipse Juno.
The android emulator starts up properly loads my splash screen
and then moves on properly but none of the buttons on the emulator
work. All of the buttons that represent the buttons on the phone do
nothing when clicked and also when I try to click any buttons on my
app nothing happens. Anyone have this problem before?
start the eclipse
start android virtual device manager.
select the AVD which you use.
4.select edit in right corner.
in the hardware option select new.
add keyboard lid support and keyboard support.
set value yes for this properties.
now start emulator this will work.
In the new ADT, they changed the way the keyboard support works for emulators...so you need to manually add support for it. If you go to your AVD Manager then edit your AVD, in the Hardware section click New and add 'Keyboard support' and set the value to 'yes'. That should fix it for you.