[android-developers] Re: Developing on Stock T-Mobile G1?
I think this is the one Raymond is referencing: http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware On Mon, Jan 19, 2009 at 4:44 PM, Raymond Rodgers raym...@badlucksoft.comwrote: deepdr...@googlemail.com wrote: Hi there, is it viable to develop applications using a stock T-Mobile G1? I guess in contrast to the emulator the real thing is restricted when it comes to debugging. But, is there a simple way to just transfer my self developed, self compiled APK to the phone and install it there? I do not have to go through the market for that, do I? :) Then again I guess it's not as easy as with the emulator, just clicking Run in Eclipse - or is there a way to tell Ecllipse to transfer the freshly compiled software to the *locked* phone? Yes, I know I could get an unlocked Dev Phone 1, but, my question is whether this would be *required* or, if not, what my options as a developer are when working with a stock, locked, phone. Thanks! All you should have to do is enable debugging under Settings - Applications - Development - USB Debugging, then plug your phone into your computer with the supplied USB cable, and Eclipse and the SDK will pretty much do the rest if your computer is properly configured. There's a page some where on the development site explaining exactly what needs to be done on Windows, MacOS/X, and Linux, but I couldn't find it with a quick search. Nonetheless, it is possible and relatively simple. Raymond -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Tmobile Android touch screen not working after 2 minutes broswing.
I haven't seen (or heard about) this problem. So, a few quick questions to maybe clear things up. 1. Any aftermarket modifications made? (example: I'm on a custom kernel at the moment. Have you left it untinkered with? ;)) 2. Has this occurred with any other applications? 3. Are you on RC30? Settings About Phone and scroll to bottom. On Sun, Jan 18, 2009 at 1:23 PM, elf elwin...@gmail.com wrote: Hi, I got a Android phone from TMobile. The touch screen stops working after I used the google browser for 2 minutes each time. After reboot, every thing will go back to normal, and that's reason I suspected it is caused by O.S. instead of hardware. Any one have same problem? Thanks. Elf -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Tmobile Android touch screen not working after 2 minutes broswing.
Well, not really sure what to say. If you really think it is a problem of the OS handling screen clicks, you could try doing a monkey -v -v -v 5000 (or whatever number you deem to be appropriate). (DISCLAIMER: This is random events. If this ends up requesting data in anyway and charging you, don't hold me responsible.) This should simulate pretty much every time of hardware interaction without actually using the hardware. If your problem reoccurs, then it is an OS problem. I'm very skeptical of this, however. Have you tried a hard reset? On Sun, Jan 18, 2009 at 6:43 PM, elf elwin...@gmail.com wrote: #1. I didn't do any O.S. level changed (wish I can :). I install a lot of application, and I use the USB debugging quit often. #2. It did happen to other applications, but not as often as the browser. (kind of 30minutes v.s. 2 minutes, or because the browser required more clicking) I don't remember it was so bad before. I got it 2 months ago, I don't think the phone have any hardware damage. #3 I guess u asking about the build id. It is kila-user 1.0 TC4-RC30 116143 Thanks in advance. Elf On Jan 18, 11:32 am, Joel Knighton joel.knigh...@gmail.com wrote: I haven't seen (or heard about) this problem. So, a few quick questions to maybe clear things up. 1. Any aftermarket modifications made? (example: I'm on a custom kernel at the moment. Have you left it untinkered with? ;)) 2. Has this occurred with any other applications? 3. Are you on RC30? Settings About Phone and scroll to bottom. On Sun, Jan 18, 2009 at 1:23 PM, elf elwin...@gmail.com wrote: Hi, I got a Android phone from TMobile. The touch screen stops working after I used the google browser for 2 minutes each time. After reboot, every thing will go back to normal, and that's reason I suspected it is caused by O.S. instead of hardware. Any one have same problem? Thanks. Elf -- Joel Knighton- Hide quoted text - - Show quoted text - -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Viewing G1's data folder (via DDMS)
Any reason you couldn't do an ./adb pull /data/anr/traces.txt ~/traces.txt? (modify for windows if necessary) On Sat, Jan 17, 2009 at 7:26 AM, GiladH gila...@gmail.com wrote: Hi, I fail to to view the content of my G1's data folder via the DDMS console. In fact - the DDMS will not even allow me to expand data folder. No problems in viewing the content of the other two folders: sdcard system. BTW the reason I'm interested in data folder is to view an ANR file (log msg from G1: 'Wrote stack trace to '/data/anr/traces.txt' ). Any ideas? GiladH -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
Re: BUG, TERRIBLE BUG!!! Re: [android-developers] Re: HELP! (was Re: Low on space)
Okay, someone who can replicate this problem, can you perform a cat /proc/yaffs and then post the output here. Curious to see the YAFFS debugging info. On Mon, Jan 12, 2009 at 3:45 PM, Jean-Baptiste Queru j...@google.com wrote: When I tried to reproduce it a few months ago I think that I was able to reproduce it without such a shortcut, but I might be wrong. JBQ On Mon, Jan 12, 2009 at 1:42 PM, Stoyan Damov stoyan.da...@gmail.com wrote: You might want to check whether this is related to having a shortcut of the app on the home screen. I have a hunch it is. Cheers On Mon, Jan 12, 2009 at 11:39 PM, Jean-Baptiste Queru j...@google.com wrote: There is a bug somewhere (it's assigned to me for investigation) where the system process keeps apk files open after they get unlinked in some scenario close to what you mention (install, launch, uninstall), which can then trigger the yaffs2 leak bug. JBQ On Mon, Jan 12, 2009 at 1:35 PM, Stoyan Damov stoyan.da...@gmail.com wrote: Thanks. A little bit more info about that bug - I *am* experiencing it again. It *is* related to re-installs of one and the same application over and over again. I reinstalled my app maybe ~20 times today and slowly my ~70 went to 63 MB. My app is 2MB so I have to have ~68MB but I don't. I noticed the browser took 2MB and deleted them. However, the free memory increased by ONE MB. WTF is going on here? Hurray! :) I did the battery pull and apparently I've hit the right moment to pull the battery. My memory increased from 64 to 69 MB. Now, how the device pulled that off is a mystery to me because my app is 2MB (perhaps the ~70 MB are close to ~71) but what the heck, the good thing is that the bug is indeed *this* one, and not another which I'm the only one experiencing! Problem solved, THANKS to everybody! Cheers On Mon, Jan 12, 2009 at 11:06 PM, Jean-Baptiste Queru j...@google.com wrote: Second hand information about the battery trick: yaffs2 has some sanity-checking code that can detect and recover from unlinked files, but that code is only run when the filesystem wasn't cleanly unmounted. JBQ On Mon, Jan 12, 2009 at 1:02 PM, Stoyan Damov stoyan.da...@gmail.com wrote: On Mon, Jan 12, 2009 at 10:55 PM, Dianne Hackborn hack...@android.com wrote: Another place to look -- there is a filesystem bug that can sometimes happen where unlinked files are not recovered. Here is the comment from an engineer who knows more about it: They can easily tell by looking at the number of unlinked files for the user partition in /proc/yaffs. If that number is very large, then they can reboot the device, wait a few second after they see the android, then pull the battery again. That should make the number of unlinked files drop back down. If that number isn't very large, then it is probably something else. I read about this on the net -- I thought it was some sort of a dark joke or something -- apparently not :) I did pull the battery though - nothing (good) happened. This developer you're talking about - can he elaborate on how the battery pull trick actually works -- I'm genuinely interested. Unfortunately it looks like only root cat read /proc/yaffs (though that seems a little overly restrictive). However you can try the pulling the battery trick and see if that helps. Well, the over-the-air patch @#$%ed root access so I can't look anywhere. The /data/local directory is owned by the shell user, so you don't need root for that -- just cd /data/local and look at what is there. There is a chance that some temp .apk files have been left there from adb install, or some other files created by other shell sessions. I already reset the phone but if I encounter this again I'll check there (+ I'll have root this time :) Thanks, Stoyan -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
Re: BUG, TERRIBLE BUG!!! Re: [android-developers] Re: HELP! (was Re: Low on space)
In fact, if you have root access, a $su #echo all /proc/yaffs #cat /proc/yaffs would be optimal. This should give a fair amount of debugging info for system, userdata, and cache. If you post that up here, I should be able to give it a shot. On Mon, Jan 12, 2009 at 3:54 PM, Joel Knighton joel.knigh...@gmail.comwrote: Okay, someone who can replicate this problem, can you perform a cat /proc/yaffs and then post the output here. Curious to see the YAFFS debugging info. On Mon, Jan 12, 2009 at 3:45 PM, Jean-Baptiste Queru j...@google.comwrote: When I tried to reproduce it a few months ago I think that I was able to reproduce it without such a shortcut, but I might be wrong. JBQ On Mon, Jan 12, 2009 at 1:42 PM, Stoyan Damov stoyan.da...@gmail.com wrote: You might want to check whether this is related to having a shortcut of the app on the home screen. I have a hunch it is. Cheers On Mon, Jan 12, 2009 at 11:39 PM, Jean-Baptiste Queru j...@google.com wrote: There is a bug somewhere (it's assigned to me for investigation) where the system process keeps apk files open after they get unlinked in some scenario close to what you mention (install, launch, uninstall), which can then trigger the yaffs2 leak bug. JBQ On Mon, Jan 12, 2009 at 1:35 PM, Stoyan Damov stoyan.da...@gmail.com wrote: Thanks. A little bit more info about that bug - I *am* experiencing it again. It *is* related to re-installs of one and the same application over and over again. I reinstalled my app maybe ~20 times today and slowly my ~70 went to 63 MB. My app is 2MB so I have to have ~68MB but I don't. I noticed the browser took 2MB and deleted them. However, the free memory increased by ONE MB. WTF is going on here? Hurray! :) I did the battery pull and apparently I've hit the right moment to pull the battery. My memory increased from 64 to 69 MB. Now, how the device pulled that off is a mystery to me because my app is 2MB (perhaps the ~70 MB are close to ~71) but what the heck, the good thing is that the bug is indeed *this* one, and not another which I'm the only one experiencing! Problem solved, THANKS to everybody! Cheers On Mon, Jan 12, 2009 at 11:06 PM, Jean-Baptiste Queru j...@google.com wrote: Second hand information about the battery trick: yaffs2 has some sanity-checking code that can detect and recover from unlinked files, but that code is only run when the filesystem wasn't cleanly unmounted. JBQ On Mon, Jan 12, 2009 at 1:02 PM, Stoyan Damov stoyan.da...@gmail.com wrote: On Mon, Jan 12, 2009 at 10:55 PM, Dianne Hackborn hack...@android.com wrote: Another place to look -- there is a filesystem bug that can sometimes happen where unlinked files are not recovered. Here is the comment from an engineer who knows more about it: They can easily tell by looking at the number of unlinked files for the user partition in /proc/yaffs. If that number is very large, then they can reboot the device, wait a few second after they see the android, then pull the battery again. That should make the number of unlinked files drop back down. If that number isn't very large, then it is probably something else. I read about this on the net -- I thought it was some sort of a dark joke or something -- apparently not :) I did pull the battery though - nothing (good) happened. This developer you're talking about - can he elaborate on how the battery pull trick actually works -- I'm genuinely interested. Unfortunately it looks like only root cat read /proc/yaffs (though that seems a little overly restrictive). However you can try the pulling the battery trick and see if that helps. Well, the over-the-air patch @#$%ed root access so I can't look anywhere. The /data/local directory is owned by the shell user, so you don't need root for that -- just cd /data/local and look at what is there. There is a chance that some temp .apk files have been left there from adb install, or some other files created by other shell sessions. I already reset the phone but if I encounter this again I'll check there (+ I'll have root this time :) Thanks, Stoyan -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- Joel Knighton -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
Re: BUG, TERRIBLE BUG!!! Re: [android-developers] Re: HELP! (was Re: Low on space)
Just anybody. If you'd like, you could still do the first one for me and help out a bit. On Mon, Jan 12, 2009 at 4:00 PM, Stoyan Damov stoyan.da...@gmail.comwrote: I guess by you you don't mean me - I don't have root access. BTW, I just found another bug, which is very weird but I'll send it in a new post. On Mon, Jan 12, 2009 at 11:58 PM, Joel Knighton joel.knigh...@gmail.com wrote: In fact, if you have root access, a $su #echo all /proc/yaffs #cat /proc/yaffs would be optimal. This should give a fair amount of debugging info for system, userdata, and cache. If you post that up here, I should be able to give it a shot. On Mon, Jan 12, 2009 at 3:54 PM, Joel Knighton joel.knigh...@gmail.com wrote: Okay, someone who can replicate this problem, can you perform a cat /proc/yaffs and then post the output here. Curious to see the YAFFS debugging info. On Mon, Jan 12, 2009 at 3:45 PM, Jean-Baptiste Queru j...@google.com wrote: When I tried to reproduce it a few months ago I think that I was able to reproduce it without such a shortcut, but I might be wrong. JBQ On Mon, Jan 12, 2009 at 1:42 PM, Stoyan Damov stoyan.da...@gmail.com wrote: You might want to check whether this is related to having a shortcut of the app on the home screen. I have a hunch it is. Cheers On Mon, Jan 12, 2009 at 11:39 PM, Jean-Baptiste Queru j...@google.com wrote: There is a bug somewhere (it's assigned to me for investigation) where the system process keeps apk files open after they get unlinked in some scenario close to what you mention (install, launch, uninstall), which can then trigger the yaffs2 leak bug. JBQ On Mon, Jan 12, 2009 at 1:35 PM, Stoyan Damov stoyan.da...@gmail.com wrote: Thanks. A little bit more info about that bug - I *am* experiencing it again. It *is* related to re-installs of one and the same application over and over again. I reinstalled my app maybe ~20 times today and slowly my ~70 went to 63 MB. My app is 2MB so I have to have ~68MB but I don't. I noticed the browser took 2MB and deleted them. However, the free memory increased by ONE MB. WTF is going on here? Hurray! :) I did the battery pull and apparently I've hit the right moment to pull the battery. My memory increased from 64 to 69 MB. Now, how the device pulled that off is a mystery to me because my app is 2MB (perhaps the ~70 MB are close to ~71) but what the heck, the good thing is that the bug is indeed *this* one, and not another which I'm the only one experiencing! Problem solved, THANKS to everybody! Cheers On Mon, Jan 12, 2009 at 11:06 PM, Jean-Baptiste Queru j...@google.com wrote: Second hand information about the battery trick: yaffs2 has some sanity-checking code that can detect and recover from unlinked files, but that code is only run when the filesystem wasn't cleanly unmounted. JBQ On Mon, Jan 12, 2009 at 1:02 PM, Stoyan Damov stoyan.da...@gmail.com wrote: On Mon, Jan 12, 2009 at 10:55 PM, Dianne Hackborn hack...@android.com wrote: Another place to look -- there is a filesystem bug that can sometimes happen where unlinked files are not recovered. Here is the comment from an engineer who knows more about it: They can easily tell by looking at the number of unlinked files for the user partition in /proc/yaffs. If that number is very large, then they can reboot the device, wait a few second after they see the android, then pull the battery again. That should make the number of unlinked files drop back down. If that number isn't very large, then it is probably something else. I read about this on the net -- I thought it was some sort of a dark joke or something -- apparently not :) I did pull the battery though - nothing (good) happened. This developer you're talking about - can he elaborate on how the battery pull trick actually works -- I'm genuinely interested. Unfortunately it looks like only root cat read /proc/yaffs (though that seems a little overly restrictive). However you can try the pulling the battery trick and see if that helps. Well, the over-the-air patch @#$%ed root access so I can't look anywhere. The /data/local directory is owned by the shell user, so you don't need root for that -- just cd /data/local and look at what is there. There is a chance that some temp .apk files have been left there from adb install, or some other files created by other shell sessions. I already reset the phone but if I encounter this again I'll check there (+ I'll have root this time :) Thanks, Stoyan -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- Jean-Baptiste M. JBQ
Re: BUG, TERRIBLE BUG!!! Re: [android-developers] Re: HELP! (was Re: Low on space)
Beautiful. It does appear to be nUnlinkedFiles in userdata causing the problem after continual uninstall/reinstall (my phone is at 30k after infrequent installations, I notice yours is at 5k after a fresh install/battery trick). Working on a shell script that could potentially remedy this problem, but this is obviously not an optimal solution. On Mon, Jan 12, 2009 at 4:08 PM, Stoyan Damov stoyan.da...@gmail.comwrote: On Tue, Jan 13, 2009 at 12:05 AM, Disconnect dc.disconn...@gmail.com wrote: Why not? Its available to anyone with a g1 these days (if you are willing to wipe out your data, which it sounds like you have to do occasionally anyway) http://tinyurl.com/g1rc30 On Mon, Jan 12, 2009 at 5:00 PM, Stoyan Damov stoyan.da...@gmail.com wrote: I guess by you you don't mean me - I don't have root access. BTW, I just found another bug, which is very weird but I'll send it in a new post. Until today I didn't have the need to have root access :) Even now I don't *need* to have one, but *will* downgrade to RC29 when I have some spare time. Cheers, Stoyan -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
Re: BUG, TERRIBLE BUG!!! Re: [android-developers] Re: HELP! (was Re: Low on space)
Do you have busybox on the device? If so, I can help you find where the space is gone. With only the included android shell binaries, however, I don't know if I can. On Sun, Jan 11, 2009 at 8:33 PM, Dianne Hackborn hack...@android.comwrote: On Sun, Jan 11, 2009 at 5:04 PM, Stoyan Damov stoyan.da...@gmail.comwrote: Is there *anyone* who'll dare to tell me there's no bug in Android? Why would anyone claim there are no bugs in -any- piece of complicated software? (Except I guess TeX). How the fuck I don't have *anything* installed (besides the pre-installed G1 apps) and my memory is only ONE MB??? Where are the ~70 MBs??? :((( Just to clarify, none of the installed applications are shown to be using a large amount of data? If that is the case, then there are very few places the storage could have gone. First be sure to check in I believe /data/local (may be something else, it's the directory under /data owned by the shell allowing it to place files there). If that is not large, it could be in data/system, but unlikely. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
Re: BUG, TERRIBLE BUG!!! Re: [android-developers] Re: HELP! (was Re: Low on space)
Okay, Stoyan, if you want to do a ls -l -R and then email it to me ( joel.knigh...@gmail.com) I'll read through it and see if I notice a problem. (You can email straight from the terminal app) On Sun, Jan 11, 2009 at 8:41 PM, Joel Knighton joel.knigh...@gmail.comwrote: Do you have busybox on the device? If so, I can help you find where the space is gone. With only the included android shell binaries, however, I don't know if I can. On Sun, Jan 11, 2009 at 8:33 PM, Dianne Hackborn hack...@android.comwrote: On Sun, Jan 11, 2009 at 5:04 PM, Stoyan Damov stoyan.da...@gmail.comwrote: Is there *anyone* who'll dare to tell me there's no bug in Android? Why would anyone claim there are no bugs in -any- piece of complicated software? (Except I guess TeX). How the fuck I don't have *anything* installed (besides the pre-installed G1 apps) and my memory is only ONE MB??? Where are the ~70 MBs??? :((( Just to clarify, none of the installed applications are shown to be using a large amount of data? If that is the case, then there are very few places the storage could have gone. First be sure to check in I believe /data/local (may be something else, it's the directory under /data owned by the shell allowing it to place files there). If that is not large, it could be in data/system, but unlikely. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. -- Joel Knighton -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Secrity with SlideMe
What's this about Android Market not being available on developer phones? Based on the developer phone sitting next to me, I'm going to have to say that's just not true. Android Market is definitely available on developer phones. On Wed, Jan 7, 2009 at 2:31 PM, Michael MacDonald googlec...@antlersoft.com wrote: I believe applications are written to a directory on the phone that is not visible to normal users (via unix permissions). If you have a developer phone (which gives you root access) you could access it. I think that's oneof the reasons Android Market is not available on the developer phones. I don't know what SlideMe's policy is, but I think in general if you make your application installer available to people who have root access to their phones,they will be able to get the .apk and potentially make it available to anyone with the SDK to install. Steff wrote: Hi I am thing about releasing my application on SlideMe. I have talked to someone with SlideMe, and they tell me that priced application is just installed on the device itself. I asked them how they prevent people from just copying the application to another phone - for instance using some filebrowser app for Andoid. They tell me that the applications are stored as private and that they cannot be copied, but I dont quit understand. Is there some feature in Android letting applications (for instance SlideMe's SAM), copy files to the device, files that cannot be copied, but can be loaded to run? If yes, please direct me to some documentation/explanation of that feature! Regards, Per Steffensen -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Secrity with SlideMe
Shane, Although I had not yet attempted to do so, it looks as if your question was already answered. If you need any more information about application installation on the ADP1, feel free to email me personally or post to the list. On Wed, Jan 7, 2009 at 5:08 PM, Dianne Hackborn hack...@android.com wrote: A third party application installed on even a locked G1 can be retrieved from it with a simple adb pull (you just need to know its package name) or programmatically by retrieving its information from the PackageManager and opening and reading the .apk file path it tells you. On Wed, Jan 7, 2009 at 2:05 PM, Shane Isbell shane.isb...@gmail.comwrote: Hi Joel, Are you able to pull the applications that have been installed through Android Market off of the device on the dev phone? SAM is using the system installer, so it will be the same as Android Market. We are limiting paid purchases to just the device. Secure for G1, but interesting to see what the implications are on the dev phone. Web installs, like through Handango or AndroidGuys, go straight to /sdcard/downloads, so that method is wide open, and you might as well be giving your application away. As I discussed with Steff, security is not 100%, some people are going to be knowledgable enough to obtain installed applications, even from Android Market. At SlideME, we will do our best to protect paid content. If there are any security issues that people find, let us know and we will address them. We also have a project that has been under development that I hope will address some of these additional concerns next month. When I was involved in a J2ME provisioning server launch at a US carrier, a number of years ago, a lot of the same concerns existed. Ultimately the fraud rate was pretty low and the carrier did quiet well. Eventually, they implemented things like forward locking, to address the concerns of major content providers. The decision lies strictly in the expected fraud rate and how much the developer is willing to pay to protect themselves. That is largely a personal call. Paying an extra 20-25% to insure that the application can't be forwarded to another user, when the fraud rate is 5%, wouldn't justify it. If you are thinking 30% fraud rate it will. But typically fraud rates are not nearly that high in mobile. Most people aren't motivated enough and wouldn't trust an app from an unknown source. People really do pay for applications in mobile. Thanks, Shane On Wed, Jan 7, 2009 at 12:58 PM, Joel Knighton joel.knigh...@gmail.comwrote: What's this about Android Market not being available on developer phones? Based on the developer phone sitting next to me, I'm going to have to say that's just not true. Android Market is definitely available on developer phones. On Wed, Jan 7, 2009 at 2:31 PM, Michael MacDonald googlec...@antlersoft.com wrote: I believe applications are written to a directory on the phone that is not visible to normal users (via unix permissions). If you have a developer phone (which gives you root access) you could access it. I think that's oneof the reasons Android Market is not available on the developer phones. I don't know what SlideMe's policy is, but I think in general if you make your application installer available to people who have root access to their phones,they will be able to get the .apk and potentially make it available to anyone with the SDK to install. Steff wrote: Hi I am thing about releasing my application on SlideMe. I have talked to someone with SlideMe, and they tell me that priced application is just installed on the device itself. I asked them how they prevent people from just copying the application to another phone - for instance using some filebrowser app for Andoid. They tell me that the applications are stored as private and that they cannot be copied, but I dont quit understand. Is there some feature in Android letting applications (for instance SlideMe's SAM), copy files to the device, files that cannot be copied, but can be loaded to run? If yes, please direct me to some documentation/explanation of that feature! Regards, Per Steffensen -- Joel Knighton -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Secrity with SlideMe
As Dianne mentioned, PacMan doesn't work. You actually can't seem to download it on the ADP1 anyway. However, I could retrieve the .apk of other applications downloaded from the Android Market. On Wed, Jan 7, 2009 at 8:15 PM, Shane Isbell shane.isb...@gmail.com wrote: Hi Joel, Can you download PacMan from the Android Market? Then type: adb pull /data/app-private/com.NamcoNetworks.PacMan.apk See if you can grab that guy off. Or if anyone else with a dev phone, if they have time. Thanks, Shane On Wed, Jan 7, 2009 at 3:16 PM, Joel Knighton joel.knigh...@gmail.comwrote: Shane, Although I had not yet attempted to do so, it looks as if your question was already answered. If you need any more information about application installation on the ADP1, feel free to email me personally or post to the list. On Wed, Jan 7, 2009 at 5:08 PM, Dianne Hackborn hack...@android.comwrote: A third party application installed on even a locked G1 can be retrieved from it with a simple adb pull (you just need to know its package name) or programmatically by retrieving its information from the PackageManager and opening and reading the .apk file path it tells you. On Wed, Jan 7, 2009 at 2:05 PM, Shane Isbell shane.isb...@gmail.comwrote: Hi Joel, Are you able to pull the applications that have been installed through Android Market off of the device on the dev phone? SAM is using the system installer, so it will be the same as Android Market. We are limiting paid purchases to just the device. Secure for G1, but interesting to see what the implications are on the dev phone. Web installs, like through Handango or AndroidGuys, go straight to /sdcard/downloads, so that method is wide open, and you might as well be giving your application away. As I discussed with Steff, security is not 100%, some people are going to be knowledgable enough to obtain installed applications, even from Android Market. At SlideME, we will do our best to protect paid content. If there are any security issues that people find, let us know and we will address them. We also have a project that has been under development that I hope will address some of these additional concerns next month. When I was involved in a J2ME provisioning server launch at a US carrier, a number of years ago, a lot of the same concerns existed. Ultimately the fraud rate was pretty low and the carrier did quiet well. Eventually, they implemented things like forward locking, to address the concerns of major content providers. The decision lies strictly in the expected fraud rate and how much the developer is willing to pay to protect themselves. That is largely a personal call. Paying an extra 20-25% to insure that the application can't be forwarded to another user, when the fraud rate is 5%, wouldn't justify it. If you are thinking 30% fraud rate it will. But typically fraud rates are not nearly that high in mobile. Most people aren't motivated enough and wouldn't trust an app from an unknown source. People really do pay for applications in mobile. Thanks, Shane On Wed, Jan 7, 2009 at 12:58 PM, Joel Knighton joel.knigh...@gmail.com wrote: What's this about Android Market not being available on developer phones? Based on the developer phone sitting next to me, I'm going to have to say that's just not true. Android Market is definitely available on developer phones. On Wed, Jan 7, 2009 at 2:31 PM, Michael MacDonald googlec...@antlersoft.com wrote: I believe applications are written to a directory on the phone that is not visible to normal users (via unix permissions). If you have a developer phone (which gives you root access) you could access it. I think that's oneof the reasons Android Market is not available on the developer phones. I don't know what SlideMe's policy is, but I think in general if you make your application installer available to people who have root access to their phones,they will be able to get the .apk and potentially make it available to anyone with the SDK to install. Steff wrote: Hi I am thing about releasing my application on SlideMe. I have talked to someone with SlideMe, and they tell me that priced application is just installed on the device itself. I asked them how they prevent people from just copying the application to another phone - for instance using some filebrowser app for Andoid. They tell me that the applications are stored as private and that they cannot be copied, but I dont quit understand. Is there some feature in Android letting applications (for instance SlideMe's SAM), copy files to the device, files that cannot be copied, but can be loaded to run? If yes, please direct me to some documentation/explanation of that feature! Regards, Per Steffensen -- Joel Knighton -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I
[android-developers] Re: Deployment of native C library
Issue the commands in this order (from a terminal on the device, otherwise change to use adb shell). $su #mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system Add/change anything you need, then revert to read only. $su #mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system On Fri, Jan 2, 2009 at 12:31 AM, Margaret mawei...@gmail.com wrote: add sudo where you do mount . mawei...@gmail.com 13585201588 2009/1/2 shimo...@gmail.com shimo...@gmail.com: Hi, Thanks ! Where do I issue this command from ? When I do this from PTerminal on my Android device it hangs, then issues a warning box saying: Activity pTerminal (in application pTerminal) is not responding Do you have a Dev Phone ? Thanks. On Jan 2, 3:39 am, Joel joel.knigh...@gmail.com wrote: Sounds as if you don't have root. Did you issue a su command first? On Jan 1, 6:11 pm, shimo...@gmail.com shimo...@gmail.com wrote: Hi, Tried that on my Dev Phone, and got mount: operation not permitted Can you tell me why ? TIA On Nov 17 2008, 11:48 am, li chen freep...@gmail.com wrote: You can use adb shell toremount/system and try again: mount -oremountrw /system -freepine -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Android Dev Phone 1 and AT T
Yes, this is true. It is not a software limitation of any sort. There is not the radio for ATT 3G bands in the Dev Phone 1. On Tue, Dec 16, 2008 at 3:32 PM, Auauaua skraiduo...@gmail.com wrote: I have it working on AtT - however - is it true that we are not able to use the 3G on Android G1???!!! I am only getting edge and G. narkis On Dec 16, 3:35 pm, Vladimir Kelman vkel...@gmail.com wrote: Thank you Justin! In fact, I already found the first link you provided and successfully set up my Android Dev Phone to work with ATT... I just wasn't sure I need to send a message about it. I duplicated set up instructions in my blog athttp:// pro-thoughts.blogspot.com/2008/12/android-dev-phone-1-and-at.html On Dec 16, 1:39 pm, Justin (Google Employee) j...@google.com wrote: Please seehttp:// groups.google.com/group/android-developers/msg/e4a9172898b7d7cc andhttp:// groups.google.com/group/android-developers/search?group=androi... Remember to search first, chances are good that if you've had a question, someone else has too. Cheers, Justin Android Team @ Google On Dec 15, 7:39 pm, Vladimir Kelman vkel...@gmail.com wrote: Did anyone successfully set up Android Dev Phone to work with ATT? I received my phone today and need some guidance. Could you please leave a comment here and / or onhttp://pro-though ts.blogspot.com/2008 /12/android-dev-phon e-1-and-at.html (where I described my problems) ? -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: sim needed for accessing market?
Yes, the Market application is on the Android Dev Phone 1. On Sun, Dec 14, 2008 at 8:27 PM, strazzere str...@gmail.com wrote: @Xavier Can I asked exactly where you are getting your information? Did someone tell you this? @Craig The developer phone can go on networks like T-Mobile if a sim card is provided, though it is not nessicary for the phone to work. It can access the internet without any card via usb connection. The real question is, is does it come with the market application on it. Hopefully someone with a developer phone can answer this, as it isn't on googles page concerning the phone; http://code.google.com/android/dev-devices.html The way everything is worded. I would assume that the market is NOT on the device since it's intended to test YOUR applications. It also notes that it is not intented for everyday users as it is not supported by anyway... So I'd (hopefully safely) assume that you could not expect the market to be on there. -Tim Strazzere http://www.strazzere.com/blog/ On Dec 14, 8:19 pm, Xavier Mathews xavieruni...@gmail.com wrote: Do you have the Dev phone. I belive that you can download from the market to the phone via usb through dsl. I have never tried. On 12/14/2008, Craig csab...@gmail.com wrote: Does anyone know what is required to use the dev phone? Specifically, do I need a phone contract, or can I get online through my DSL connection at home? If I can get online through my home connection, would I have access to the Android Market? I'm asking because I would like a device to develop on and test, but I'm not interested in another phone contract, and I don't have ATT or TMobile. -- Xavier A. Mathews Student/Browser Specialist/Developer/Web-Master Google Group Client Based Tech Support Specialist Hazel Crest Illinois xavieruni...@gmail.com¥xavieruni...@hotmail.com¥truestar...@yahoo.com Fear of a name, only increases fear of the thing itself. -- Joel Knighton --~--~-~--~~~---~--~~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
