[android-developers] Re: Dev Phone and RC33 update
The firmware is different. ADP 1.1 is made by google and jail broken G1 probably runs on JF firmware which is a 3rd party developer. 2009/3/30 patg > > Is there any difference between a ADP1 and a jail broken G1? > > Pat > > On Mar 29, 8:31 am, Disconnect wrote: > > Yes you can, and so long as you do not flash the t-mobile SPL you will be > > fine. (For example, do not use any tmobile dreaimg.nbh files you might > come > > across.) > > > > Safer and more functional images are available fromhttp:// > jf.andblogs.net, > > where he sets the security code to 0 (so you have root), secures root > (with > > an app called Superuser that does an "are you sure" popup) and greatly > > enhances the shell environment with busybox, backups, etc. His images > are > > available in all of the standard dream 'flavors' so far (us, uk, adp1, > > holiday) and do not break the spl. > > > > 2009/3/28 Rodin > > > > > > > > > > > > > Jean-Baptiste, > > > > > I've looked around and I'm still not clear on something. > > > If I order the ADP1, is there a possibility to flash the standard > > > TMobile US image and just the use the phone as a fully-functional, > > > locked G1? > > > > > Thanks, > > > Rodin > > > > > On Mar 2, 3:16 pm, Jean-Baptiste Queru wrote: > > > > That wouldn't work, as you could download with the "locked" firmware, > > > > flash an "unlocked" firmware, and get the files out. > > > > > > JBQ > > > > > > 2009/3/2 vendor : > > > > > > > What do you think about the idea of two firmware versions for ADP1? > > > > > > > 2009/3/3 Jean-Baptiste Queru > > > > > > >> As far as I know by the time you remove from ADP1 the features > that > > > > >> would allow access to forward-locked apps (flashable, root, > debuggable > > > > >> system), you have essentially a consumer device. > > > > > > >> JBQ > > > > > > >> 2009/3/2 vendor.net : > > > > > > >> >> Most importantly though, I'm really disappointed in Google's > lack > > > of > > > > >> >> communication on the topic. I have to scour the web just to > find a > > > > >> >> hint of some idea of what's going on with thedevphone. There > is no > > > > >> >> official word or anything. Google should at least have a > posting > > > on > > > > >> >> the Developer's blog. Where is Google's "Contact Us" link for > > > those > > > > >> >> of us who paid the $25? > > > > >> > Totally agree! > > > > > > >> > Hint for some desperate developers who wants to trade ADP1 for > G1. > > > You > > > > >> > can put the G1 firmware. Your phone will be full locked except > for > > > the > > > > >> > sim card I think, but you will have G1 firmware. Just have to > flash > > > > >> > it, but still I didn`t think that this is the solution... > > > > > > >> > I see one possible solution for dealing with the situation: To > have > > > 2 > > > > >> > versions for developers. The first version will be totally > unlocked, > > > > >> > but it will not support the full market. The second version will > > > lock > > > > >> > only these dirs which contains the paid apps. The second version > of > > > > >> > the firmware will lock only the dirs and the processes which > control > > > > >> > the copy/protection of the apps. There could be flaws, but I > will be > > > > >> > happy to read your comments about it. It is a possible solution? > > > JQB? > > > > > > >> > On1Март, 08:08, Sen wrote: > > > > >> >> Well, you all have certainly taken this discussion in an > > > interesting > > > > >> >> direction. > > > > > > >> >> I would just like to add to my original posting. Hopefully we > > > still > > > > >> >> have some official Google person's attention. > > > > > > >> >> I'm pretty understanding when it comes to deadlines not being > met > > > when > >
[android-developers] Re: Dev Phone and RC33 update
Yes, you can do that, but you will fully lock your phone. 2009/3/29 Rodin > > Jean-Baptiste, > > I've looked around and I'm still not clear on something. > If I order the ADP1, is there a possibility to flash the standard > TMobile US image and just the use the phone as a fully-functional, > locked G1? > > Thanks, > Rodin > > > On Mar 2, 3:16 pm, Jean-Baptiste Queru wrote: > > That wouldn't work, as you could download with the "locked" firmware, > > flash an "unlocked" firmware, and get the files out. > > > > JBQ > > > > 2009/3/2 vendor : > > > > > > > > > What do you think about the idea of two firmware versions for ADP1? > > > > > 2009/3/3 Jean-Baptiste Queru > > > > >> As far as I know by the time you remove from ADP1 the features that > > >> would allow access to forward-locked apps (flashable, root, debuggable > > >> system), you have essentially a consumer device. > > > > >> JBQ > > > > >> 2009/3/2 vendor.net : > > > > >> >> Most importantly though, I'm really disappointed in Google's lack > of > > >> >> communication on the topic. I have to scour the web just to find a > > >> >> hint of some idea of what's going on with thedevphone. There is no > > >> >> official word or anything. Google should at least have a posting > on > > >> >> the Developer's blog. Where is Google's "Contact Us" link for > those > > >> >> of us who paid the $25? > > >> > Totally agree! > > > > >> > Hint for some desperate developers who wants to trade ADP1 for G1. > You > > >> > can put the G1 firmware. Your phone will be full locked except for > the > > >> > sim card I think, but you will have G1 firmware. Just have to flash > > >> > it, but still I didn`t think that this is the solution... > > > > >> > I see one possible solution for dealing with the situation: To have > 2 > > >> > versions for developers. The first version will be totally unlocked, > > >> > but it will not support the full market. The second version will > lock > > >> > only these dirs which contains the paid apps. The second version of > > >> > the firmware will lock only the dirs and the processes which control > > >> > the copy/protection of the apps. There could be flaws, but I will be > > >> > happy to read your comments about it. It is a possible solution? > JQB? > > > > >> > On1Март, 08:08, Sen wrote: > > >> >> Well, you all have certainly taken this discussion in an > interesting > > >> >> direction. > > > > >> >> I would just like to add to my original posting. Hopefully we > still > > >> >> have some official Google person's attention. > > > > >> >> I'm pretty understanding when it comes to deadlines not being met > when > > >> >> it comes to stuff like this. We're all developers here and I'm > sure > > >> >> we've all experienced this. I would agree though that I think the > > >> >> people that went out of their way and paid the extra money for a > > >> >> "developer edition" phone, should be the first to get the updates. > > > > >> >> Most importantly though, I'm really disappointed in Google's lack > of > > >> >> communication on the topic. I have to scour the web just to find a > > >> >> hint of some idea of what's going on with thedevphone. There is no > > >> >> official word or anything. Google should at least have a posting > on > > >> >> the Developer's blog. Where is Google's "Contact Us" link for > those > > >> >> of us who paid the $25? > > > > >> >> Why do I have to ask this question?... we really should be better > > >> >> informed. > > > > >> >> Thanks > > > > >> >> On Feb 28,1:16 pm, Jon Colverson wrote: > > > > >> >> > On Feb 28, 6:46 pm, Al Sutton wrote: > > > > >> >> > > method), and, as far as I'm aware, there isn't a method > circulating > > >> >> > > which can be applied to any and every protected application to > get > > >> >&
[android-developers] Re: Dev Phone and RC33 update
Then, could you create a virtual partition for the secure dirs and encrypt it with key which only the System knows and when you flash the system => you loose the key? 2009/3/3 Jean-Baptiste Queru > > You don't need for wipe the data and cache partitions when flashing > the boot, recovery or system partitions. > > JBQ > > 2009/3/2 vendor : > > If you flash with the unlocked firmware you should delete the older > first? > > And to format the partition? > > > > 2009/3/3 Jean-Baptiste Queru > >> > >> That wouldn't work, as you could download with the "locked" firmware, > >> flash an "unlocked" firmware, and get the files out. > >> > >> JBQ > >> > >> 2009/3/2 vendor : > >> > What do you think about the idea of two firmware versions for ADP1? > >> > > >> > 2009/3/3 Jean-Baptiste Queru > >> >> > >> >> As far as I know by the time you remove from ADP1 the features that > >> >> would allow access to forward-locked apps (flashable, root, > debuggable > >> >> system), you have essentially a consumer device. > >> >> > >> >> JBQ > >> >> > >> >> 2009/3/2 vendor.net : > >> >> > > >> >> >> Most importantly though, I'm really disappointed in Google's lack > of > >> >> >> communication on the topic. I have to scour the web just to find > a > >> >> >> hint of some idea of what's going on with the dev phone. There is > >> >> >> no > >> >> >> official word or anything. Google should at least have a posting > on > >> >> >> the Developer's blog. Where is Google's "Contact Us" link for > those > >> >> >> of us who paid the $25? > >> >> > Totally agree! > >> >> > > >> >> > Hint for some desperate developers who wants to trade ADP1 for G1. > >> >> > You > >> >> > can put the G1 firmware. Your phone will be full locked except for > >> >> > the > >> >> > sim card I think, but you will have G1 firmware. Just have to flash > >> >> > it, but still I didn`t think that this is the solution... > >> >> > > >> >> > I see one possible solution for dealing with the situation: To have > 2 > >> >> > versions for developers. The first version will be totally > unlocked, > >> >> > but it will not support the full market. The second version will > lock > >> >> > only these dirs which contains the paid apps. The second version of > >> >> > the firmware will lock only the dirs and the processes which > control > >> >> > the copy/protection of the apps. There could be flaws, but I will > be > >> >> > happy to read your comments about it. It is a possible solution? > JQB? > >> >> > > >> >> > On 1 Март, 08:08, Sen wrote: > >> >> >> Well, you all have certainly taken this discussion in an > interesting > >> >> >> direction. > >> >> >> > >> >> >> I would just like to add to my original posting. Hopefully we > still > >> >> >> have some official Google person's attention. > >> >> >> > >> >> >> I'm pretty understanding when it comes to deadlines not being met > >> >> >> when > >> >> >> it comes to stuff like this. We're all developers here and I'm > sure > >> >> >> we've all experienced this. I would agree though that I think the > >> >> >> people that went out of their way and paid the extra money for a > >> >> >> "developer edition" phone, should be the first to get the updates. > >> >> >> > >> >> >> Most importantly though, I'm really disappointed in Google's lack > of > >> >> >> communication on the topic. I have to scour the web just to find > a > >> >> >> hint of some idea of what's going on with the dev phone. There is > >> >> >> no > >> >> >> official word or anything. Google should at least have a posting > on > >> >> >> the Developer's blog. Where is Google's "Contact Us" link for > those > >> >&g
[android-developers] Re: Dev Phone and RC33 update
If you flash with the unlocked firmware you should delete the older first? And to format the partition? 2009/3/3 Jean-Baptiste Queru > > That wouldn't work, as you could download with the "locked" firmware, > flash an "unlocked" firmware, and get the files out. > > JBQ > > 2009/3/2 vendor : > > What do you think about the idea of two firmware versions for ADP1? > > > > 2009/3/3 Jean-Baptiste Queru > >> > >> As far as I know by the time you remove from ADP1 the features that > >> would allow access to forward-locked apps (flashable, root, debuggable > >> system), you have essentially a consumer device. > >> > >> JBQ > >> > >> 2009/3/2 vendor.net : > >> > > >> >> Most importantly though, I'm really disappointed in Google's lack of > >> >> communication on the topic. I have to scour the web just to find a > >> >> hint of some idea of what's going on with the dev phone. There is no > >> >> official word or anything. Google should at least have a posting on > >> >> the Developer's blog. Where is Google's "Contact Us" link for those > >> >> of us who paid the $25? > >> > Totally agree! > >> > > >> > Hint for some desperate developers who wants to trade ADP1 for G1. You > >> > can put the G1 firmware. Your phone will be full locked except for the > >> > sim card I think, but you will have G1 firmware. Just have to flash > >> > it, but still I didn`t think that this is the solution... > >> > > >> > I see one possible solution for dealing with the situation: To have 2 > >> > versions for developers. The first version will be totally unlocked, > >> > but it will not support the full market. The second version will lock > >> > only these dirs which contains the paid apps. The second version of > >> > the firmware will lock only the dirs and the processes which control > >> > the copy/protection of the apps. There could be flaws, but I will be > >> > happy to read your comments about it. It is a possible solution? JQB? > >> > > >> > On 1 Март, 08:08, Sen wrote: > >> >> Well, you all have certainly taken this discussion in an interesting > >> >> direction. > >> >> > >> >> I would just like to add to my original posting. Hopefully we still > >> >> have some official Google person's attention. > >> >> > >> >> I'm pretty understanding when it comes to deadlines not being met > when > >> >> it comes to stuff like this. We're all developers here and I'm sure > >> >> we've all experienced this. I would agree though that I think the > >> >> people that went out of their way and paid the extra money for a > >> >> "developer edition" phone, should be the first to get the updates. > >> >> > >> >> Most importantly though, I'm really disappointed in Google's lack of > >> >> communication on the topic. I have to scour the web just to find a > >> >> hint of some idea of what's going on with the dev phone. There is no > >> >> official word or anything. Google should at least have a posting on > >> >> the Developer's blog. Where is Google's "Contact Us" link for those > >> >> of us who paid the $25? > >> >> > >> >> Why do I have to ask this question?... we really should be better > >> >> informed. > >> >> > >> >> Thanks > >> >> > >> >> On Feb 28, 1:16 pm, Jon Colverson wrote: > >> >> > >> >> > On Feb 28, 6:46 pm, Al Sutton wrote: > >> >> > >> >> > > method), and, as far as I'm aware, there isn't a method > circulating > >> >> > > which can be applied to any and every protected application to > get > >> >> > > a > >> >> > > protection free copy by following a simple set of instructions > (if > >> >> > > there > >> >> > > is I'd welcome information on it so we can work on fixing the > flaw > >> >> > > it > >> >> > > uses). > >> >> > >> >> > I'm not aware of one either, but I expect that a tool would emerge > >> >
[android-developers] Re: Dev Phone and RC33 update
What do you think about the idea of two firmware versions for ADP1? 2009/3/3 Jean-Baptiste Queru > > As far as I know by the time you remove from ADP1 the features that > would allow access to forward-locked apps (flashable, root, debuggable > system), you have essentially a consumer device. > > JBQ > > 2009/3/2 vendor.net : > > > >> Most importantly though, I'm really disappointed in Google's lack of > >> communication on the topic. I have to scour the web just to find a > >> hint of some idea of what's going on with the dev phone. There is no > >> official word or anything. Google should at least have a posting on > >> the Developer's blog. Where is Google's "Contact Us" link for those > >> of us who paid the $25? > > Totally agree! > > > > Hint for some desperate developers who wants to trade ADP1 for G1. You > > can put the G1 firmware. Your phone will be full locked except for the > > sim card I think, but you will have G1 firmware. Just have to flash > > it, but still I didn`t think that this is the solution... > > > > I see one possible solution for dealing with the situation: To have 2 > > versions for developers. The first version will be totally unlocked, > > but it will not support the full market. The second version will lock > > only these dirs which contains the paid apps. The second version of > > the firmware will lock only the dirs and the processes which control > > the copy/protection of the apps. There could be flaws, but I will be > > happy to read your comments about it. It is a possible solution? JQB? > > > > On 1 Март, 08:08, Sen wrote: > >> Well, you all have certainly taken this discussion in an interesting > >> direction. > >> > >> I would just like to add to my original posting. Hopefully we still > >> have some official Google person's attention. > >> > >> I'm pretty understanding when it comes to deadlines not being met when > >> it comes to stuff like this. We're all developers here and I'm sure > >> we've all experienced this. I would agree though that I think the > >> people that went out of their way and paid the extra money for a > >> "developer edition" phone, should be the first to get the updates. > >> > >> Most importantly though, I'm really disappointed in Google's lack of > >> communication on the topic. I have to scour the web just to find a > >> hint of some idea of what's going on with the dev phone. There is no > >> official word or anything. Google should at least have a posting on > >> the Developer's blog. Where is Google's "Contact Us" link for those > >> of us who paid the $25? > >> > >> Why do I have to ask this question?... we really should be better > >> informed. > >> > >> Thanks > >> > >> On Feb 28, 1:16 pm, Jon Colverson wrote: > >> > >> > On Feb 28, 6:46 pm, Al Sutton wrote: > >> > >> > > method), and, as far as I'm aware, there isn't a method circulating > >> > > which can be applied to any and every protected application to get a > >> > > protection free copy by following a simple set of instructions (if > there > >> > > is I'd welcome information on it so we can work on fixing the flaw > it > >> > > uses). > >> > >> > I'm not aware of one either, but I expect that a tool would emerge > >> > very quickly if the AndAppStore takes off when it starts being > >> > distributed with handsets and such. You could then tweak the system to > >> > stop the tool from working, but then the attacker would release a new > >> > version, and you'd be in an arms race. > >> > >> > The reason why I say they're equivalent is that while the steps along > >> > the way may be different, the end result is the same: people who don't > >> > want to pay will get the apps for free. In my opinion adding extra > >> > hurdles just wastes the developers' time and provides a juicier > >> > intellectual challenge for those who are inclined to try to defeat the > >> > system. > >> > >> > -- > >> > Jon > > > > > > > > > -- > Jean-Baptiste M. "JBQ" Queru > Android Engineer, Google. > > Questions sent directly to me will likely get ignored or forwarded to > a public forum with no further warning. > > > > --~--~-~--~~~---~--~~ 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: Dev Phone and RC33 update
Something unofficial? Not a strict plan like we will be done in 2 days, but something more than:"We understand your concerns and we will make an update which will treat properly the paid applications and in the feature G1/G2 and etc will be synchronized with the ADPs." Just an example. Because now, I as a developer am stuck and don`t know what to expect. Thanks! P.S. I understand you. Such big project and so many expectations, deadlines and a whole new sphere of development, but google should understand us too. We have the right to know whats happening and will happen. On Fri, Feb 27, 2009 at 8:17 PM, Jean-Baptiste Queru wrote: > > No roadmap or ETA, sorry. > > JBQ > > On Fri, Feb 27, 2009 at 10:12 AM, vendor wrote: > > Could you say a roadmap or something? Ex. I did`t know, I was only > > speculating that you are working on this problem, but please share > > information with us. We work together... > > > > On Fri, Feb 27, 2009 at 7:58 PM, Jean-Baptiste Queru > > wrote: > >> > >> It would make more sense to not rely on forward-locking for > >> copyright-related restrictions. It all boils down to finding time to > >> implement it. > >> > >> JBQ > >> > >> On Fri, Feb 27, 2009 at 9:34 AM, Steve Barr wrote: > >> > > >> > On 2/27/09, Jean-Baptiste Queru wrote: > >> >> DRM in this discussion is a mechanism that allows developers to say > "I > >> >> don't want my application to be available on devices from which it > can > >> >> be copied". > >> > > >> > Given rooted devices, would it make more sense to look for DRM which > >> > locked an app to a particular device ID (or user ID), no matter what > >> > kind of device it was? It seems like the Market has to keep track of > >> > which device (or perhaps person) downloaded/purchased which apps > >> > already, so the user can download them again if needed. > >> > > >> > I'm no expert on DRM, but it seems to me there are some pieces > >> > available for a different solution to the problem. > >> > > >> > Steve > >> > > >> > > > >> > > >> > >> > >> > >> -- > >> Jean-Baptiste M. "JBQ" Queru > >> Android Engineer, Google. > >> > >> Please don't contact me directly. > >> > >> > > > > > > > > > > > > > -- > Jean-Baptiste M. "JBQ" Queru > Android Engineer, Google. > > Please don't contact me directly. > > > > --~--~-~--~~~---~--~~ 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: Dev Phone and RC33 update
Could you say a roadmap or something? Ex. I did`t know, I was only speculating that you are working on this problem, but please share information with us. We work together... On Fri, Feb 27, 2009 at 7:58 PM, Jean-Baptiste Queru wrote: > > It would make more sense to not rely on forward-locking for > copyright-related restrictions. It all boils down to finding time to > implement it. > > JBQ > > On Fri, Feb 27, 2009 at 9:34 AM, Steve Barr wrote: > > > > On 2/27/09, Jean-Baptiste Queru wrote: > >> DRM in this discussion is a mechanism that allows developers to say "I > >> don't want my application to be available on devices from which it can > >> be copied". > > > > Given rooted devices, would it make more sense to look for DRM which > > locked an app to a particular device ID (or user ID), no matter what > > kind of device it was? It seems like the Market has to keep track of > > which device (or perhaps person) downloaded/purchased which apps > > already, so the user can download them again if needed. > > > > I'm no expert on DRM, but it seems to me there are some pieces > > available for a different solution to the problem. > > > > Steve > > > > > > > > > > > -- > Jean-Baptiste M. "JBQ" Queru > Android Engineer, Google. > > Please don't contact me directly. > > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
