According to the N Developer Preview documentation, we can set up Direct Boot support on Android N through Settings > Developer Options > Convert to file encryption. I cannot find this option on a Nexus 6 running NDP2, nor on an NDP2 emulator.
According to that same documentation, we can also set this up by running adb reboot-bootloader and fastboot --wipe-and-use-fbe in a terminal window. This bug report suggests that this too is broken, along with the first option.
So, how do we test this? Specifically:
Has anyone gotten either of the above options to work, on a device or emulator?
Has anyone tried the "emulated Direct Boot mode" (adb shell sm set-emulate-fbe true), and does that work? And did you try that on a device or emulator?
Are there any any known side effects of trying this stuff (e.g., you're likely to brick your device)?
It only works on 6P and 5X, via dev options. The '--wipe-and-use-fbe' option seems not be available yet. FBE appears to work OK, you can always format userdata to revert.
Related
The Developer Options for Android are really useful. But I can't seem to enable them on an Android emulator (Nexus 5 running API 25). I tried clicking with my mouse 7 times on the build number to simulate the 7 taps on a phone. But the Developer Options don't appear.
I have found a video on YouTube and worked for me.
The way you enable it is the same as you'd do in a real device.
Go to: Settings -> System -> About emulated device -> Build number click that as many times as it takes to turn on developer mode, and that's it!
Here is the video:
https://youtu.be/Yxqq7bT1K2A
Developer options is not enabled by default. Below are the steps to enable it in your emulator
Go to Settings -> About emulated device
Click Build number 7 times (or till it says that you're a developer now).
Go back and go to System -> Advanced -> Developer options
adb shell input keyevent 82 is the command
It's probably not possible to turn on the Developer Options in the Android emulator because the documentation calls them On-Device Developer Options: Configure On-Device Developer Options. That said, I don't see an explicit mention that it can't be used on the emulator. I looked in the Configure On-Device Developer Options and the Run Apps on the Android Emulator documentation.
Perhaps the On-Device Developer Options are handled in other ways by the Android emulator. For example, there are the Extended controls, settings, and help. There are also the command-line options you can pass to the Android emulator.
Some options may simply be unavailable on an Android Emulator, such as Try out WebView Beta. Each limitation such as this one may or may not workaround. A possible workaround for updating the WebView on the Android Emulator is Update Android System WebView on SDK Emulator.
To enable 'develper options' in real phone or emulator, we may refer to the official document.
https://developer.android.com/studio/debug/dev-options.
I did it on Pixel 2 API28 emulator following instrucions explained in the link and it worked.
Have a good one!
I never had problems using Android Studio, while debugging directly on device or via emulator. Today after a long time, i tried to install it on my workstation and it looks like there are unidentified problems, that I didn't find anywhere on google ...
Emulator:
I tried 981234912849821 different settings but i can't start an emulation, it worked only ONE time. When i opened it again, it didn't work again D:
The emulator always starts, then crashes saying:
qemu-system-i386.exe has stopped working
I tried to use it with Graphics: Software - GLES 2.0 and this is the result:
I became bored about it, so i tried to directly use my phone and i discovered that android studio wasn't finding it, even by changing type of usb connection ...
Do you have any idea about this problem guys? ^^
PS: Don't flag it as duplicate, I already saw the answers on who has these problems but nothing worked for me :\
You need an ADB driver for your phone installed on your system. Also make sure that under the Developer Settings in Settings of your phone, USB Debugging is enabled.
Note: If you cannot find Developer Settings, just go to > Settings> About Phone> tap on Build Number for 7 times> then just go back to the settings and you'll see the Developer options.
And regarding the emulator, you might want to buff the resolution and the ram of the virtual device and try again.
I would Like to enable Diagnostic (DIAG) Mode on Android.
I have the following questions about the same.
How is DIAG mode helpful ?
Is Rooting the Device necessary to enable DIAG Mode ?
How to verify if DIAG mode is enabled ?
Is it reversible ? Can i go back to Normal Mode ?
I'm using Google Nexus 5.
I'm fairly new to Android Development.
Any help would be appreciated.
1- I personally use DM to collect and analyse the messages between a mobile (UE) and a network. I use it with Qualcomm QXDM and QPST tools to analyse wireless protocol stack messages. With commercial phones, usually the DM is blocked as a security measure as it allows you to decapsulate the messages sent/received by the UE. I haven't heard about another use for it until now.
2- Yes all the commercial UEs I worked with ( mostly with Sony Xperia and currently with Xperia Ray) are rooted.
3- If DIAG mode is enabled, you can see it in your Device Manager. Here is a snapshot of mine. That means you have to install the correct drivers for the device (which was tricky with many phones). The device should has Qualcomm Chipset!
4- Yes you can unroot the device. Never tried with Nexus myself.
Can I ask what is the purpose of using it for you? I mean it's strictly working with protocol stacks.
Hope it helps! Cheers
Diagnostics Mode can be used to change your device's radio band & modem settings and other stuff like changing IMEI address or MAC Address, if you have appropriate software like DFS CDMA Tool or QPST.
You can enable it only if your phone is rooted.
Make sure Qualcomm drivers for your phone are installed in computer.
Enter this in Terminal Emulator in your device:
su
setprop sys.usb.config diag,adb
Note: This will work only if your phone's ramdisk has the appropriate configs enabled for the 'diag,adb' property.
If that didn't work, better open /init.xxxxxxx.usb.rc (xxxxxxx represents your device's codename or chipname or whatever) and check for properties related to 'diag'.
To verify if it's working, just check the Device Manager or the tool you're using & check if your phone gets connected.
Yes, it's reversible. To get back to normal mode, just type this in Terminal Emulator:
setprop sys.usb.config mtp
You'll get back to MTP mode :)
If you mean the developer options, then as of Android 4.2 I believe, one of the things about the developer options is that the menu is just hidden now. You have to purposely enable the menu to access the options.
It's helpful because you need it to help debug your apps while it's connected to your computer and the SDK. There are a lot of options there, depending on what kind of app you are making. Enabling the menu by itself does not do anything to your device.
No it's not necessary.
If you see developer options in the settings menu, then you know it's enabled.
All you are doing is unhiding the hidden developer menu. Not really anything to reverse. You can just turn off the options you turned on during development.
I dont know much about DIAG mode but it's used when you want to read data from phone using qualcomm settings. To get into DIAG mode use ##3424# or *#7284#. And enable DM+MOdem+.. on.
If the following command does not work:
su setprop sys.usb.config diag,adb
You can try:
su setprop sys.usb.config diag,serial_cdev,rmnet,adb
Both set of commands require root. The difference has to do with modem processors.
I am trying to enable USB Debugging on Android so that I don't need to use the emulator.
I did what all the posts all around the web say to do: I went to settings -> applications -> Developer -> USB debugging
It still does not turn on the notification sign that USB Debugging is enabled, and Eclipse does not recognize it, and uses the regular emulator.
Does anyone have any idea what is wrong?
You haven't specified what device you are using or what operating system you are using, so that could be helpful.
A few things to keep in mind:
1 Don't mount as USB storage.
2 You also need to make sure to install the drivers for your phone so that the Android Debug Bridge (ADB) can properly communicate. After these are installed, try the command "adb devices" and you should see an item in your list of devices.
Update based on your comment: You can download Kies from Samsung, which include the drivers (as well as other things): http://www.samsung.com/us/kies/
Or you can find unofficial driver-only packages, such as: http://forum.xda-developers.com/showthread.php?t=961956
I think you'll need the OEM USB dirvers.
Read this:
OEM USB Drivers
My experience with windows has been that you might need to un-install the USB drivers under device manager. Then disconnect the device (restart might be required). After plugging the device back in make sure you use the manufactures drivers if available
you have installed your device driver rite?then right click on your app name->run as->run configurations->target->select manual->apply.after that click on debug button then it will ask you to select the device.
If everything else is tested, try with another USB cable.
On Android 4.2 and higher, the Developer options screen is hidden by default. To make it visible, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options at the bottom.
Fruthermore on some devices you will be asked to accept an RSA key, which allows debugging through your computer. This ensures that other adb commands cannot be executed unless you're able to unlock your device.
Detailed information can be found here:
http://developer.android.com/tools/help/adb.html It is the overview about adb commands (which is used to send data to your device) and it starts with the steps how to bring your phone to debug-mode.
I wish to add to Danation's answer with the following.
If you have installed KIES, and you've tried following instructions a couple of times (for the android SDK package) without success, here's what worked for me:
As a precaution, disconnect the device, and press 'Revoke USB Debugging authorizations'.
Now, go to kies, and reinstall the device driver as seen on the image below.
Connect the device.
For me, it was a routine, it usually works when installing kies, but I was stuck on this today for a little while, and I hope i can help others with my solution as well..
I have never used debugging on real Android devices yet. I read the manual at http://developer.android.com/guide/developing/device.html for debugging.
I downloaded the driver for Acere130 Android 2.1 to test on it. Now I am not getting any devices when I use command on adb, using adb devices. No real device is there. Only when I run the emulator does it show the emulator virtual device. How can I move forward? What am I missing?
go to setting-->Application-->Developement-->and check the USB debugging
make sure its checked.
It is very easy. If you have connected your phone with your computer and as mcnicholls said you need to enable USB debugging. Have a break point some where in your code. And when you Debug as Android Application. It will work. Your break point will be highlighted. And you can debug your program.
Make sure you have the USB drivers installed for the device you are using.
Make sure you see your device's internal storage in My Computer.
You need to go into the developer settings menu on the phone and enable USB debugging.
To list out how many devices are attached to your machine, run the adb devices command:
paresh#technotalkative:~/android-sdk-linux_86/platform-tools$ adb devices
List of devices attached
Before starting development, you should make sure below things (As others has also answered):
Settings->Applications->Unknown Sources (Make it true)
Settings->Applications->Development->USB debugging (Make it true)
Here is a full description which i think you are looking for: Android - Using Hardware Devices