I'm experiencing very interesting problem with my Galaxy S6 Edge phone with marshmallow. When I go to developer options. Instead of a long list of options I get a message of "developer options not available for this user". As far as I know, I don't have any other user (I even don't know how to add a user, to be honest). I saw a couple of people had a similar issue with kitkat but they weren't even able to get the developer options menu item in the settings. I have that developer options item and I actually have it for a while. I haven't done anything special recently and I wonder anyone experienced this before and whether there is a way of fixing this without factory reset.
Finally there are a couple of more symptoms which may/may not be related with this.
Task Switch button at the bottom of screen doesn't work.
The settings button on the notifications panel doesn't work
EDIT : I had to fix the issue by factory reset, I didn't have the chance to try Victor's answer but I am accepting it as the right answer since there are some people who were able to fix their issue
One solution is to run the com.google.android.setupwizard/.SetupWizardTestActivity activity and step through the setup wizard - https://plus.google.com/u/0/+PaulOBrien/posts/8EGNvpY9jQa
A relatively easy way of running that activity is described here: http://forums.androidcentral.com/samsung-galaxy-s7/659407-s7-edge-not-showing-notifications-tray-recent-apps-button-settings-button-dnt-work.html#post5083902
1) Download Nova Launcher & set it as default to replace TouchWiz.
2) Long press on the home screen.
3) Choose Widgets.
4) At the top, under Nova Launcher, scroll to the right & press & hold on Activities and place it somewhere empty on the home screen.
5) Scroll down to Setup Wizard. I saw 2 Setup Wizard options.
6) Under the first Setup Wizard option, I opened it & scrolled down to the 3rd choice which said ".SetupWizardTestActivity". It might be in a different spot for you, but look at the small writing, that's how I saw this one.
7) Select that to create the widget shortcut.
8) Open it. Apparently you're supposed to have a menu to go through and just click through "Next", but there wasn't one for me.
Following the instructions in that forum post fixed the problem on my Note 4.
I was able to fix this by adding and then deleting a new user:
In Settings, go to "Users".
Tap "Add user" and follow the prompts, including "Set up now" to switch to the new user.
Repeat step #1.
Tap your original user to switch back.
Repeat step #1.
Tap the gear icon next to the new user, then tap "Remove user" and follow the prompts.
Related
I'm developing an Android-/iOS-App with react-native.
I want to allow my customers to select between options upon clicking the "options menu hardware button" in Android (you know, the button usually at the bottom left of the android devices with 3 lines on top of each other, often triggering a menu in the app providing additional options).
Question: How can I listen to the options menu button click?
To clearify, I mean that button:
I know that the button does not exist under iOS and not under all Android phones and I will have to implement another solution for there, but that does not matter at the moment, as I want the button primarily to provide debugging functionality for my customers/testers (e.g. sending me the state of an erroneous screen).
Strangely, I did not find any resources on google regarding this problem, although I would assume wanting to use hardware buttons in react-native is a common task. Maybe I used the wrong search terms - if someone could link me to better terms describing this problem, I'm thankful as well :D.
Only thing I could find is the BackHandler for handling back-button-clicks.
I'm writing a little Android App and things are working out nicely, actually. The only problem I'm facing is that Android Studio won't let me refactor all of the occurrences of the variable I inted to rename (see: attached link).
I'm simply using the Alt-Shift-R Shortcut, entering the wanted text and pressing enter. The field variable is changed - but its occurences (though highlighted before) aren't. Using the preview window doesn't change the outcome.
Am I missing anything? I feel like a moron. :')
Variable naming after hitting Enter-Button
valueAusgabe is the previous naming
If you're on Windows or Linux you should be able to rename all occurrences of your variable (variableAusgabe) by just using the Ctrl+Shift+R shortcut.
When you use this, a pop-up shows up and you have to enter the text you want to replace (variableAusgabe), and the text you want to replace it with. Select Refactor for each occurrence or Replace All.
In Android Studio (ver.3.1) shortcut for Refactor/Rename is: Shift+F6.
ctrl + R in windows,
it works for me
I also faced the same problem a few days back, just go ahead to refactor the variable and when the popup appears to confirm the refactoring the variable just uncheck the "Search in comments and strings", and it should work.
You might have some software running in the background that catches the event and isn't firing it back at the system for other software to process it.
One example, and a very popular one, is GeForce Experience In-Game Overlay (Shadowplay). Shift+F6 is used by it to switch post-processing filter slots.
If you happen to run a device with an nvidia chip, you probably have it running.
Steps to find and fix the issue:
Open its settings:
Alt+Z by default, or
RMB click its icon in the tray -> GF Experience -> Gear icon in the upper-right corner -> Scroll down to In-Game Overlay -> Press the Settings button.
Click the Gear icon on the right.
Keyboard shortcuts.
Find Shift+F6, click, press Delete on your keyboard.
If that software is not running in the background, it may be something else but equally as "greedy" is running then. Look for it in the tray. Good luck!
I'm trying to make a part of my android app go directly to the USB debugging toggle in the settings
I've gotten it to open the Developer options page so far, using
startActivity(new Intent(Settings.ACTION_APPLICATION_DEVELOPMENT_SETTINGS));
However, I've seen some apps (can't recall specific ones) that open a settings page and scroll down to a certain entry.
How can I do the same action, so that I can open the Developer options page scrolled down to the USB-debugging toggle?
Thanks a lot!
After a couple days of research + trying to hack it in, I've concluded that this isn't possible. My app would lose all control the second I call an activity. And there's no possible parameters I can send to the native settings app to launch scrolled down.
Im making this question because, i dont know if im the only one who happened this and how to fixed. In the last month i been acceding to the android.developers site without having any problem, but in the last 2 weeks, it started to show posts in korean, like this:
and it happens in all the site, showing me parts in korean and parts in english. I tryed to access to manually to the site, but it still resending me to the "ko" extension. I have the computer in russian and i dont know if that influences the search. I didnt find anything related to this, and it starts to be really annoying. Thanks!
I had this happen to me too! Clear your cookies and cached app data in settings. Google chrome: Ctrl-H, clear history, check only the above options. Close browser, re-open and check if it is still the same. This happened to me when I clicked on a Korean link to google dev page last week.
At the bottom of the page you can simply choose the language you want and the menu will be in the right language again.
If it happens again: when you have the "intl/ko/" in URL -> just replace "ko" by "en".
IT works just right now (after months of research...)
Rather than clearing your complete browser data,
Right click -> Inspect Element -> Click on Resource Tab Now select
'Cookies' menu -> select developer.android.com Here delete
'android_developer_pref_lang'
Now close this Tab. Open develop.android.com in new tab.
In Chrome, from the javascript console (F12-Application-Console):
document.cookie = 'android_developer_pref_lang=en; path=/'
and then refresh the page
I'm new to the Android framework (using Eclipse) and I have a question about debugging. Recently I did this error in an activity:
// The installation button
Button button = (Button) findViewById(R.id.preparationInstallButtonID);
button.setOnClickListener(this);
setContentView(R.layout.preparation);
i.e. I tried to add an onclick-event prior the layout had been rendered. This crashed the program, "Sorry, the application xxx has stopped unexpectedly". Running it again, with debug-mode, Eclipse opens a Debug-window containing "Thread<3> (Suspended)" etc (I'm sure you know which window I'm talking about).
Now, how am I able to extract useful data here? Regarding the problem above I found how to fix it by trial-and-erroring, but let's say I'm not able to do trial-and-error, how can the debug-window help me find the source of the error? It says "exception RuntimeException", but I don't see any pointers as of where in my code the exception occured.
If You want to debug:
Right click left of Your part of code You want to debug (at line number). select Toggle Breakpoint.
You can see small circle beside the line number, that is the breakpoint.
Then, make run configuration, click small arrow beside run icon, and click 'run configurations..'
Click on android application, you will see this dialog window:
Read it, "highlight" this: 'Press new button to create a configuration of the selected type'. Click the New button, above the tab, You will see this dialog:
fill it, browse Your project,
for example, I add Scrumptious project, and launch default activity. Click on Target Tab, choose Your emulator. If You want to run on physical device, click 'Always prompt to pick device'. I run on physical device this time,
for the Common tab, if maybe You want to check Display in favorites menu for 'Debug' or 'Run' option. It is optional. Click apply.
click debug icon - and select your project. If You activate 'Debug' on Display in favorites menu, the project will shown at the debug option menu.
I choose 'Always prompt to pick device', this dialog will shown. I want to run at physical device, so I click the device at the 'Choose a running Android Device', and click 'Ok'. You can also run on emulator. Just click your emulator, and click Ok.
If eclipse give confirmation to open perspective, select Yes
Then, if You want to know what is value of the variable, just put your mouse to the instance of variable, or You can browse at 'Variables' window at Debug perspective.
Use the LogCat this will give you the error messages and everything else that goes on in your testdevice/emulator.
Window -> Show View -> Other -> LogCat
I strongly recommend this tutorial on debugging in general.
http://www.vogella.com/articles/EclipseDebugging/article.html
It takes you through all the features Eclipse offers in that department and is well worth the time.
As far as the particular trick that might've helped, it might have been useful to set a breakpoint (i.e., clicking in the left margin of the code to make one of those blue pins appear). Then, when running in debug, you could stop near where the problem occurred, and step forward, beat by beat, using the "step into," "step forward," and "step return" commands at the top of debug window. While you're stepping around the code in that way, you might have the variables window open, so you could see what things are set in a manner they should be, etc.
Alternatively, you could set a breakpoint on RuntimeException (even one that's caught), by clicking on the Breakpoints window in debug, and then licking the "J!" button (the mouseover text shows "add Java Exception Breakpoint."
The debug view lets you do other cool stuff too, like:
letting you set "watchpoints", so you can see when the application changes relevant fields, etc.
"Drop to frame" so you can start your app in the middle.
Set up step filters, so that "stepping" through I mentioned earlier can be done more efficiently.
Create a detail formatter, a little snippet of java code that formats the output of a field so you can view it more cleanly in the debugger.
And much more!
Again, I recommend the above-referenced tutorial. And welcome to the wonderful world of debugging.