I ran CTS PLAN and after it finished, I saw that my Android device asked me enter a PIN code to access the device. However, I didn't set a PIN to lock the device, and I don't know which PIN I'm supposed to provide.
This problem happened to me on 2 more Android devices when I ran CTS on them.
I tried some passwords but they have not solved this.
I'm looking for a solution to this problem, but can't find any other mention of this problem.
NOTE: I ran CTS with a script, but has it really change something?
I had same issue,I entered pin as 12345.It's worked for me try from your side and let me know
Related
I cannot solve this error. The app seems to build just fine but, for some reason, can't seem to connect to the emulator. It always ends with "Lost connection to device" while installing. I also tried it on a physical device, still won't work. I have tried numerous possible solution, but none of them worked.
What I've checked:
Memory enough
No connection problem
flutter doctor -v shows no issues
The problem might be some plugin issue, but I don't know what or how to solve it. It also might be something else. If further code or information is required do let me know. Does anyone know how to solve this issue?
I have two times facing this issue, to fix it sometime it is a bit tricky.
It is coming from 2 possibilities:
Device you are using
Invalid SDK after accidentally updates its version.
But, if the problem is on your device, try this.
Reset the debug authorization on your device
Go to settings > developer options > revoke USB debbuging authorization.
If problem persist.
Check the disable adb auth timeout if it unchecked.
Modify the Logger buffer size to max (Mine is set off before, now it is 8MB, and changing this to 64k is working on small apps, but bigger apps need to log the debug process much bigger so it needs to increase its capacity).
Hope this can helps you mate!
What usually fixes it for me is to close the emulator, go into Android Studio Device Manager and 'Wipe Data' for that emulator. See image:
I'm using to make automatic build and releases of my android library.
One of the steps is, of course, automated testing. Since I can, I run the tests on a real device.
The issue is, I have to unplug then re-plug my device between every launch otherwise I get an error saying that my device is either not found or offline.
So the drivers are all fine since it's working the first time, but I can't figure out what's happening after that.
I'd love to be able to build and test release candidate everytime I push on develop but this is preventing me from doing it properly ;(
I tried re-installing everything with no changes. Has anyone else encountered the same issue or have a fix to this behaviour?
Thanks a lot!
I was wondering if there is any way to get any feedback of what's going on behind the scenes when running an app on an Android device. If I use the emulator and eclipse I can see what's happening in the logcat. But I'm making a program with ROS android and it I cannot run it on the emulator. Now my program crashes and I don't know why. Is there any way I can get more information?
Thanks
You can use adb to debug the app on your device. See http://developer.android.com/guide/developing/device.html
I can think of a couple (less than elegant) ways to try and find out what's going on.
1) Display toasts from potential problem areas (Does it have a screen?)
2) Write logs to the SD card (does it have an SD card??)
EDIT
I wasn't thinking clearly... you have to be able to load the program to the device, so you must be able to connect it to your PC. So, as Agarwal pointed out, you can most likely hook it up, run it on the device/robot/whatever and see what happens with the logcat.
while i add this line to my code
Process process = Runtime.getRuntime().exec("su -c");
or
Process process = Runtime.getRuntime().exec("su");
trying to run the"su" command,
process.exitValue() returns 1 which means fail.
This happens to my one Android device while my the other rooted android device works perfectly with this command. (process.exitValue() returns 0)
Can anyone teach me how to trace the error or how to fix it?
I am confused with this error while my two devices almost in the same condition.
Thanks for your reply in advance.
Hi guys,
Thanks for discussing this issue with me. Your reply hints me a clue that I have removed my old su and place a new su. Luckily enough, the return value is now 0 and I guess it means correct. However, Does any of you might know what is the difference between .exec("su -c") and .exec("su")? Please let me know if you know the difference.
I suspect you lack Superuser on the problematic phone, do you?
Or at least something about Superuser could be wrong (versions, binaries...)
su calls Superuser which allows root access or not.
Many problems seems to occurs on latest versions of Superuser.
Try to remove it and install other version:
http://goo.im/superuser
Another note: if you're trying to gain root access or to execute commands as root, you should not only use exec("su"). Take a look at the RootTools a library by stericson himself ;)
http://code.google.com/p/roottools/
The command su (which means Super User) is only valid on rooted phones. That is why your rooted phone recognizes it and works as expected. So, either you root your other device(s) or drop this idea on non-rooted phones :)
Since this is the only result I got for searching for the phrase, thought I'd post an update for anyone else coming across this.
Was following the instructions for installing Cyanogenmod. My issue was resolved by disabling Mass Storage mode on the device (change it to one of the other options).
I am trying to view a sample app on a real device (a ViewSonic G-tablet), but the device won't display in the "Choose a running Android device" area. The virtual devices show, but no real devices show (there is only one plugged in, the G-tablet). Some other information...
I am using a Mac with Eclipse SDK 3.7.1 w/Android
App is noted as debuggable in manifest file (android:debuggable="true")
G-Tablet is set to allow debugging
Device selection is set to manual in SDK
I CAN view files on G-Tablet using Finder
I have reviewed Android developer docs
I have searched a lot online for a fix, without success
Please also note...
There is NO option on G-tablet to allow "unknown sources". However, I have downloaded apps outside the customary channels (e.g. Firefox from the Firefox site) and it works fine.
I do NOT want to do anything to the G-tablet to void the warranty.
I have already checked for/installed updates using the Android SDK Manager.
The fixes I was able to find on StackOverflow related to this problem did not work for me. I am thinking the problem may be device specific. One fix discussed getting a driver for the device, but I couldn't find one.
Can anyone please help me figure out how to get the SDK to recognize my device? I'd appreciate any insight on this.
Can you export the app as an .apk and run that on your G-tablet?
also is the android:minSdkVersion set to a value lower than your G-tablet's version?
Found the answer after trying a zillion things. All that needed to be done to fix the problem was turn to OFF 'USB debugging' and then turn it right back on. I found the idea on this page... http://www.mobileread.mobi/forums/showthread.php?t=156247 . Hope that might save someone else hours of time.