[android-developers] Re: Unsuccessful Install
Have you done http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware ? On Nov 9, 10:57 pm, BCatDC [EMAIL PROTECTED] wrote: Hi there, I'm just getting started with android developing. I have a very frustrating problem. I've worked with samples to do a number of little .APKs a few different hello worlds. A slightly modded version of lunar lander. Very basic stuff. They work great in the emulator, and they seem to export just fine. But then things go south. I've used my web server to download them over the air. I've transfered them to the sd card and tried to install them with Apps Installer (by modmyGphone) It doesn't seem to matter what I do. Every install fails with the stupid check mark and the words Unsuccessful Install. Needless to say I'm very frustrated, I have no idea how to trouble shoot this and move forward. FYI I have Unknown Sources checked in my settings. And I've successfully installed plenty of non market apps both over the air and off the sd card. Alright android geniuses thats where I'm at can you help me? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Orientation Sensor yaw values. Is your G1 compass bad?
Besides figure eights, this forum thread http://forums.t-mobile.com/tmbl/board/message?board.id=Android3thread.id=7341view=by_date_ascendingpage=10 suggests turning G1 screen down and tapping the phone on the back. This heimlich maneuver worked for me today, my compass is working again, not sure for how long. On Nov 8, 12:39 pm, hackbod [EMAIL PROTECTED] wrote: The compass auto-calibrates itself as it is used, but coming near a magnet can uncalibrate it so it won't give good data until getting calibrated again. To help it along, you can hold the phone and move it around in figure eights. That is not a joke. :) On Nov 6, 11:23 am, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I noticed the same thing on mine... It seems like it was accurate at one point, but recently it's not working so well. Let me know what you find out. On Nov 4, 2:06 pm,mitush[EMAIL PROTECTED] wrote: I have connected G1 to my PC and Compass (Orienteer) and my app started to get good and consistent readings from the sensor again. After I disconnected, Orienteer sort of works (has 360 range), but the north is off by 0-50 degrees depending on orientation and a little jumpy. Might be a battery power issue then. My battery is 97% (immediately after PC disconnect). Will check Orienteer again later. On Nov 4, 2:29 pm,mitush[EMAIL PROTECTED] wrote: In the process of writing an app for my G1 I think I got stuck with similar problem. Running Orienteer application (from the Market) confirms that; turning my G1 by 360 degrees while holding it flat, the reading on the Orienteercompassgoes between 0 and 90 degrees only. The same thing happens when usingcompassview with the maps/street view, here I could only get about 90 degrees view angle as well (in other words I cannot see other side of the street and other direction of the street). The funny thing is that, in my G1 app I was listening and logging SensorManager.SENSOR_ORIENTATION_RAW values and earlier today the returned values had the range of 360 degrees, and I have the log file to prove it was not a dream :) When I run the same app now, it shows limited range values only, consistent with Orienteer . As if something got broken between now and few hours ago. I also recall that when I triedcompass/map/streetview few days ago, I was able to rotate my view without any constraints. There is not much metal around, I tried changing my location as well. For a second, I though it could be the car, which my wife parked outside the house an hour ago, but Orienteer shows the same problem even 120 ft away in the backyard. I did not drop G1 or did anything of that sort. On Nov 4, 4:01 am, bryan [EMAIL PROTECTED] wrote: I've been trying to figure out the cause of acompassrelated error for a while. After debugging and standing out in the rain slowly spinning in circles for a while, I finally found out that my device is reporting back yaw values inconsistently. For example, the range of offset from magnetic north is +/- 46 degrees. The average offset is just under 20 degrees. Depending on how I orient my G1, the error can go to 46 degrees off of magnetic north. Has anyone here experienced similar results when reading yaw from the sensor? I've gotten a number of reports from others complaining about inaccuracy withcompasstype results and am wondering if this is a per phone error or if all of the G1s have poor yaw/orientation sensors. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Orientation Sensor yaw values. Is your G1 compass bad?
In the process of writing an app for my G1 I think I got stuck with similar problem. Running Orienteer application (from the Market) confirms that; turning my G1 by 360 degrees while holding it flat, the reading on the Orienteer compass goes between 0 and 90 degrees only. The same thing happens when using compass view with the maps/street view, here I could only get about 90 degrees view angle as well (in other words I cannot see other side of the street and other direction of the street). The funny thing is that, in my G1 app I was listening and logging SensorManager.SENSOR_ORIENTATION_RAW values and earlier today the returned values had the range of 360 degrees, and I have the log file to prove it was not a dream :) When I run the same app now, it shows limited range values only, consistent with Orienteer . As if something got broken between now and few hours ago. I also recall that when I tried compass/map/streetview few days ago, I was able to rotate my view without any constraints. There is not much metal around, I tried changing my location as well. For a second, I though it could be the car, which my wife parked outside the house an hour ago, but Orienteer shows the same problem even 120 ft away in the backyard. I did not drop G1 or did anything of that sort. On Nov 4, 4:01 am, bryan [EMAIL PROTECTED] wrote: I've been trying to figure out the cause of acompassrelated error for a while. After debugging and standing out in the rain slowly spinning in circles for a while, I finally found out that my device is reporting back yaw values inconsistently. For example, the range of offset from magnetic north is +/- 46 degrees. The average offset is just under 20 degrees. Depending on how I orient my G1, the error can go to 46 degrees off of magnetic north. Has anyone here experienced similar results when reading yaw from the sensor? I've gotten a number of reports from others complaining about inaccuracy withcompasstype results and am wondering if this is a per phone error or if all of the G1s have poor yaw/orientation sensors. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Orientation Sensor yaw values. Is your G1 compass bad?
I have connected G1 to my PC and Compass (Orienteer) and my app started to get good and consistent readings from the sensor again. After I disconnected, Orienteer sort of works (has 360 range), but the north is off by 0-50 degrees depending on orientation and a little jumpy. Might be a battery power issue then. My battery is 97% (immediately after PC disconnect). Will check Orienteer again later. On Nov 4, 2:29 pm, mitush [EMAIL PROTECTED] wrote: In the process of writing an app for my G1 I think I got stuck with similar problem. Running Orienteer application (from the Market) confirms that; turning my G1 by 360 degrees while holding it flat, the reading on the Orienteercompassgoes between 0 and 90 degrees only. The same thing happens when usingcompassview with the maps/street view, here I could only get about 90 degrees view angle as well (in other words I cannot see other side of the street and other direction of the street). The funny thing is that, in my G1 app I was listening and logging SensorManager.SENSOR_ORIENTATION_RAW values and earlier today the returned values had the range of 360 degrees, and I have the log file to prove it was not a dream :) When I run the same app now, it shows limited range values only, consistent with Orienteer . As if something got broken between now and few hours ago. I also recall that when I triedcompass/map/streetview few days ago, I was able to rotate my view without any constraints. There is not much metal around, I tried changing my location as well. For a second, I though it could be the car, which my wife parked outside the house an hour ago, but Orienteer shows the same problem even 120 ft away in the backyard. I did not drop G1 or did anything of that sort. On Nov 4, 4:01 am, bryan [EMAIL PROTECTED] wrote: I've been trying to figure out the cause of acompassrelated error for a while. After debugging and standing out in the rain slowly spinning in circles for a while, I finally found out that my device is reporting back yaw values inconsistently. For example, the range of offset from magnetic north is +/- 46 degrees. The average offset is just under 20 degrees. Depending on how I orient my G1, the error can go to 46 degrees off of magnetic north. Has anyone here experienced similar results when reading yaw from the sensor? I've gotten a number of reports from others complaining about inaccuracy withcompasstype results and am wondering if this is a per phone error or if all of the G1s have poor yaw/orientation sensors. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Problems writing to SD card of physical T-Mobile G1?
*** also posted on T-mobile G1 forum *** I have received the update, so my Use for USB Storage was replaced by the notification. But where is the option to unmount the USB disk, while G1 is still connected to the PC? I am writing a G1 app which writes to the sdcard and, when debugging/testing, I have to constantly cycle through open notifications-click-mount then look at the files on PC and then phisically disconnect-reconnect US. Before the update, it was just a single click both ways. If android developers read this, could you please give us an otion to unmount as well? On Oct 31, 5:24 pm, blindfold [EMAIL PROTECTED] wrote: Thanks Jason! Great find! Seems that the user interface for controlling this setting is now changing with later firmware, judging from the discussion at http://forums.t-mobile.com/tmbl/board/message?board.id=Android3threa... Regards On Oct 28, 12:27 am, Jason Proctor [EMAIL PROTECTED] wrote: writing to /sdcard on my G1 failed until i turned off act as USB disk in the G1 preferences. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: install test app on g1
'adb install ~/hello_android.apk' actually does seem to work, even if it prints Failure message, since my test application appears in the list of applications on G1 and I can run it even without being connected to the PC. On Oct 29, 8:13 pm, mahadevan v [EMAIL PROTECTED] wrote: You need to sign your app. Please see: http://code.google.com/android/devel/sign-publish.html On Oct 29, 6:33 pm, mitush [EMAIL PROTECTED] wrote: I went through creating the Hello, Android application using Eclipse Ganymede/ADT (on Ubuntu 8.04) as described inhttp://code.google.com/android/intro/hello-android.html. It works both in emulator, if my productionG1is not connected, and on theG1 itself, if it is connected (thanks tohttp://code.google.com/android/intro/develop-and-debug.html#developin...). I would like toinstalland run my test app onG1without it being connected to my Linux box. How can I do that? I have tried 'adb install~/hello_android.apk' and it fails as follows 131 KB/s (6739 bytes in 0.050s) pkg: /data/local/tmp/hello_android.apk Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES] (and I did set my 'debuggable' flag to true in the app manifesto and enabled USB debugging inG1) Could somebody please help? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Problems writing to SD card of physical T-Mobile G1?
You've mentioned turning off act as USB disk on G1. Did you mean use for USB storage under Settings-SD card or something else? On Oct 27, 6:27 pm, Jason Proctor [EMAIL PROTECTED] wrote: writing to /sdcardon myG1failed until i turned off act as USB disk in theG1preferences. On Oct 25, 12:03 pm, blindfold [EMAIL PROTECTED] wrote: Have others encountered problems writing to theSDcardof aG1? I've tried a small application that opens and writes text file into sd card (using plain Java File FileWriter) and it works on emulator but fails onG1probably due to permission problem (query file.canWrite() returns false). And how about you? Which API do you use towritedata on SD? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] install test app on g1
I went through creating the Hello, Android application using Eclipse Ganymede/ADT (on Ubuntu 8.04) as described in http://code.google.com/android/intro/hello-android.html. It works both in emulator, if my production G1 is not connected, and on the G1 itself, if it is connected (thanks to http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware). I would like to install and run my test app on G1 without it being connected to my Linux box. How can I do that? I have tried 'adb install ~/hello_android.apk' and it fails as follows 131 KB/s (6739 bytes in 0.050s) pkg: /data/local/tmp/hello_android.apk Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES] (and I did set my 'debuggable' flag to true in the app manifesto and enabled USB debugging in G1) Could somebody please help? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
