Now that XE16 is available, I decided to update my Glass with the new boot.img. Everything looked like it succeeded, but when I restarted the Glass, the main screen doesn't appear. When I try to use adb commands, it says my device is unauthorized and that I should check the appropriate dialog.
I'd love to check the dialog, but as I said, the screen won't appear.
Is there anything I can do?
It looks like a mismatched boot.img? Try either building the kernel or extracting it from the factory system image (assuming you tested that image).
As for building, the instructions reference glass-omap-xrr02 but the latest accessible one is glass-omap-xrv34 (for XE17). update: glass-omap-xrv60b XE17.2
Related
My question is similar to this one. I'm running Android 4.4 on my device, and want to add additional options to the quick settings. I noticed that turning on/off the Alarm Clock shows/hides a tile in the quick settings, like this:
The biggest difference in the two questions is I want to know what it would take to make it work, either having the device rooted, or flashing a custom app at install or what. I've been trying to browse the source code here, but so far I haven't seen anything that stands out to me.
Sorry about the picture size, I don't know if there's an option to scale them down...
Android N introduced Quick Settings API which allow application to add status icon in quick settings. Please check Android N preview document to learn more.
I'm pretty sure you need to be rooted. I have not come across anything that will let you add tiles under completely stock android. Depending on your phone, you might be able to root it without voiding the warranty explicitly, however it will be tricky. After which you can look at installing something xposed framework and then different xposed modules (I suggest gravity box as it lets you add most options to the quick settings). But again, it's all at your own risk for voiding your warranty or soft-bricking your phone. Good luck!
I have started testing my app in my Samsung Note 2 (real device). In installed it using this guide. However I have few questions if someone please help me:
1) Once I run my app in the device, does it install anything in my mobile (i have database use as well)? If so, what is the proper way to close the connection so that all installed things get deleted automatically?
2) If I change my code and run it again to check, what happens to the previous installation? Does it override or so?
3) When I use AVD with 5.7 inch screen, it shows menu button perfectly. But in my Note II, 3 menu button (out of 5) are shown in the bar, but rest are missing though I set android:showAsAction="ifRoom" for all of them.
Thanks,
1) installed in /data/com.yourapp.pkgname/ , no auto delete, you should uninstall it manually
2) Old one will be overrided
3) It might because your AVD is m-dpi/h-dpi but your phone is h-dpi/x-hdpi
1) Yes, it does perform a "normal" installation of your app. There is no automatic cleanup, so you have to remove any installed packages manually.
2) It will install the changed package to your device, any previous installation of your package will be gone. It will keep any application private data though.
3) Probably there is not enough room to display all of them, you did request "ifRoom" so it will only place them there if it fits.
1) Once I run my app in the device, does it install anything in my mobile (i have database use as well)? If so, what is the proper way to close the connection so that all installed things get deleted automatically?
Answer: When u install your app on device, it will get create a database, sharedperferences and other files that u have created in your application. but to delete the databases you have manually install the app or clear the data from Setting --> app.
2) If I change my code and run it again to check, what happens to the previous installation? Does it override or so?
Answer : The newer version of the app will be overridden by older one, and you can see the new changes from the app.
3) When I use AVD with 5.7 inch screen, it shows menu button perfectly. But in my Note II, 3 menu button (out of 5) are shown in the bar, but rest are missing though I set android:showAsAction="ifRoom" for all of them.
Answer: When u run the app on actual device, os will detect what ever the available space to display the menu items.. so it is not your hand, but you can decide which item you want first.
Hope this help you..
Enjoy..!!!!
I'm able to run my Uiautomator test cases on emulator easily, on both API 16 and 17.
If I run same test case on real device it get stuck in the 1st line only.
I'm not sure with the steps to run on the real device
UiScrollable has some issue, I guess. When I write getUiDevice().pressHome(); it works, but after that nothing works. I'm using the same code written in the Android developer site for Uiautomator (http://developer.android.com/tools/testing/testing_ui.html)
Use uiautomatorviewer to dump the UI hierarchy of your device's home screen. As user2575698 says, it is likely that there is no UiObject with description "Apps".
Also you have to keep in mind that the sample from the android developer site requires the device to have the screen on and that no screen lock is present. Making sure that the screen is on can be done in the following way:
UiDevice device = getUiDevice();
if (!device.isScreenOn()) {
device.wakeUp();
}
device.pressHome();
Screen lock can be disabled in Settings.
Maybe it cannot find the object with description "Apps" on your real devices,you need to give logs for detail things
use "adb shell uiautomator dump " command to get window dump. Then to to sd card and look for dump xml. There look for content-desc attribute of node and code according to that value. content-desc can be different on different device as for application in samsung it is "Apps" but in HTC one it is "All apps".
I am trying to write an application with Mono for Android. In an attempt to do this, I'm using the default template in monodevelop. I can successfully compile and run the application. When I run the application, it looks similar to the one shown here: http://docs.xamarin.com/android/getting_started/hello_world
There are two oddities in my version though:
The button is red
I can't seem to actually click the button. When I use my computers mouse, it acts like it won't click the button. This is not limited to the application either. If I try to click the home or search button in the emulator itself, I noticed that nothing happens either. Its like the emulator is not responding to my mouse.
As someone new to working with Android, can someone please tell me what I'm doing wrong? I'm using MAC OS X with Lion installed. I'm assuming that I have the SDK and Java SDK installed properly considering the app compiles and when I press "play" I can load the app in the emulator. I just can't figure out why I can't actually click the button. So bizarre.
Any ideas?
The title of this question is pretty misleading, since you're saying that the emulator is not very responsive even outside the Mono for Android application. The problem here is with the emulator itself. The one thing I would recommend trying with respect to Mono for Android is to try starting the application without debugging, as debugging will add extra overhead to running the app.
The Android emulator is notoriously slow, since it is fully emulating the ARM instruction set in software. That said, there are certain things you can do in order to squeeze some more speed out of it. One thing that I've seen make a big difference is to decrease the screen size of the emulator image. Setting this to a small screen size (such as QVGA) can make a big difference. You can manage these settings through Android's AVD Manager.
I'm working on modifying a firmware/ROM for an unbranded Chinese Android tablet i got. When i flash it to the Tablet and get to the lockscreen, unlocking it starts the Setup Wizard - but there appear to be TWO - As Android asks me to choose between two activities - the Setup Wizard and some 'defaultActivity'.
So i wonder - Where and how is this controlled by Android to know what to launch on first boot?
I had to remove Provision.APK to get rid of the duplicate APK - According to Cyanogenmod's Barebones page it isnt needed. Not much of a proper solution, But thats all i could find lacking any kind of source code for this device.