Re: [android-developers] Eclipse tools don't exist!

2012-02-06 Thread Kieran
Thanks Romain!
After a bit of Wiresharking, playing around and talking to the proxy admin 
we worked out that the entry for a SOCKS proxy had to be cleared in the 
Eclipse settings. Eclipse always tries to use a SOCKS proxy if there's an 
entry and doesn't fall back to the HTTP or HTTPS proxy if it can't connect.

-- 
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] Eclipse tools don't exist!

2012-02-06 Thread Kieran
I can't get the Eclipse integration to work because the link 404's!
http://dl-ssl.google.com/android/eclipse/

Please fix it ASAP Googlers!

-- 
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] screen lock

2011-07-25 Thread Kieran Back
ok so i put the screen lock in to many times and it locked me out of
the phone and i cant remember  my google email account what do i do

-- 
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: Programmatically check whether Market shows paid apps

2010-03-12 Thread Kieran
I'm on Optus in Australia. Optus is holding out waiting for a bigger
cut from Google because they're greedy bastards. If you send a market
intent everything seems to work but the user gets a "program can't be
found" message.

On Mar 2, 3:25 am, Bob Kerns  wrote:
> Thanks for raising this -- I hadn't considered the problem.
>
> My understanding is that in some places, it's the country that is the
> source of the restrictions (i.e. legal barriers to Google Checkout or
> something like that), while in other places, that barrier doesn't
> exist, but carriers impose their own barriers, or haven't come to
> terms with Google, or something like that.
>
> It's not a free world.
>
> The way I read the T&C's is that they apply to selling outside the
> market things from apps you've sold through the market. In a non-
> Market location, you won't have sold your app through the market. If
> you've sold the app via a different channel, you're not bound by those
> T&C's for that instance of that app.
>
> You could firewall that, and generate a separate version of the app
> for sale outside the Marketplace, to avoid any chance of a bug or
> environmental change leading to sending users outside the Marketplace
> for purchases.
>
> I don't think Google can object to your sending them to your website,
> and also selling your apps elsewhere on your website, if there's no
> attempt to bypass the market. Since they actually encourage you to
> supply a website link.
>
> But you'd like to be more direct about that in the non-Market case.
>
> What happens on a non-Market platform when you try to send them to the
> market? I suspect the intent won't launch, and you could catch that,
> and redirect them to your site or one of the appstores without these
> restricctions. The downside is that you run a risk of accidentally
> violating the T&C. IANL, but I suspect that having checked for the
> Martket first would satisfy the requirements. The upside is that you
> don't have to maintain a list of MCC/MNC code combinations, and miss
> sales if they change.
>
> On Mar 1, 5:24 am, westmeadboy  wrote:
>
> > I checked that link and I don't understand why everyone is talking
> > about the MCC/MNC when I thought that the sim country was the
> > important thing?
>
> > So, in the TelephonyManager, using getSimCountryIso() instead of
> > getNetworkCountryIso().
>
> > The link talks about the Bob operator in Austria. Could it be that the
> > Bob sim card country code is incorrectly set? I notice in my analytics
> > that I have more users using an "austria" network compared to using an
> > "austria" sim card. Admittedly, other factors (roaming) could explain
> > this.
>
> > Either way, users in paid-appcountriesbeing unable to see paid apps,
> > seems to be the exception.
>
> > For me, its crucial that users in non-paid-appcountrieshave an
> > alternative legal way to get hold of a paid app. I thought the Market
> > T&Cs forbid selling apps through apps in the Market?
>
> > On Mar 1, 1:58 pm, Peli  wrote:
>
> > > It is more complicated than that.
>
> > > In somecountries, you can access paid or only non-paid apps depending
> > > on the provider you are currently 
> > > using:http://code.google.com/p/android/issues/detail?id=3852
>
> > > In OI Notepad and OI Shopping List, we provide both links for
> > > extensions and themes (menu > settings > get add-ons): The first one
> > > to Market, and the second one to our developer homepage. We hope
> > > people figure that they should try the second link if the first one
> > > does not show sensible results.
>
> > > Peliwww.openintents.org
>
> > > On Mar 1, 10:27 am, westmeadboy  wrote:
>
> > > > I am about to release a "Pro" version of my app and so would like to
> > > > provide "Get the Pro" links.
>
> > > > However, it makes no sense to do this if the user is taken to the
> > > > Market and then can't see the Pro app (i.e. they are in a non-paid app
> > > > country). Maybe, such users would be sent to a 3rd party Market app
> > > > instead?
>
> > > > So, whats the best way to programmatically check whether the user will
> > > > see paid apps in the Market? I think its based on the sim card country
> > > > right? I assume its good enough to hard code the country codes into
> > > > the app since they don't change that often??? If they do I can just
> > > > update the lite app...
>
>

-- 
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: Preference change notifying the main Activity

2009-11-22 Thread Kieran
I ended up making up a value to commit - it's the only thing that
seems to trigger the PreferenceListener. It works now anyway :)

On Nov 19, 10:12 pm, Kieran  wrote:
> I found that this worked for every preference I had that persisted a
> value, but the 'Clear Cache' button doesn't seem to work. I tried
> extending DialogInterface then using this code:
> public void onClick(DialogInterface dialog, int which) {
>         if(which == DialogInterface.BUTTON_POSITIVE){
>                 callChangeListener(true);
>         }
>         super.onClick(dialog, which);
>
> }
>
> but I still get nothing back from the preference listener. Any ideas?
>
> By the way, I like your book a lot!
> Kieran
>
> On Nov 14, 1:38 am, Mark Murphy  wrote:
>
> > Kieran wrote:
> > > Hi,
> > > I think I've missed something in how Android is supposed to work!
> > > I have the main Activity with a menu option that opens thepreferences
> > > screen. What I need is a way for any changes that were made to be
> > > communicated back to the main Activity as soon as the preference is
> > > activated. At the moment the only way I could get it working is by
> > > using the intent data that gets sent back when the prefs activity
> > > closes but this isn't really enough. The reason why it needs to be
> > > instantaneous is that one of thepreferencesis a 'Clear cache'
> > > button, so I would like the data to be deleted when the user requests
> > > it and no later!
>
> > Attach a preference listener:
>
> >http://developer.android.com/reference/android/content/SharedPreferen...)
>
> > --
> > Mark Murphy (a Commons 
> > Guy)http://commonsware.com|http://twitter.com/commonsguy
>
> > _The Busy Coder's Guide to Android Development_ Version 2.8
> > Available!

-- 
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: Preference change notifying the main Activity

2009-11-19 Thread Kieran
I found that this worked for every preference I had that persisted a
value, but the 'Clear Cache' button doesn't seem to work. I tried
extending DialogInterface then using this code:
public void onClick(DialogInterface dialog, int which) {
if(which == DialogInterface.BUTTON_POSITIVE){
callChangeListener(true);
}
super.onClick(dialog, which);
}

but I still get nothing back from the preference listener. Any ideas?

By the way, I like your book a lot!
Kieran

On Nov 14, 1:38 am, Mark Murphy  wrote:
> Kieran wrote:
> > Hi,
> > I think I've missed something in how Android is supposed to work!
> > I have the main Activity with a menu option that opens thepreferences
> > screen. What I need is a way for any changes that were made to be
> > communicated back to the main Activity as soon as the preference is
> > activated. At the moment the only way I could get it working is by
> > using the intent data that gets sent back when the prefs activity
> > closes but this isn't really enough. The reason why it needs to be
> > instantaneous is that one of thepreferencesis a 'Clear cache'
> > button, so I would like the data to be deleted when the user requests
> > it and no later!
>
> Attach a preference listener:
>
> http://developer.android.com/reference/android/content/SharedPreferen...)
>
> --
> Mark Murphy (a Commons 
> Guy)http://commonsware.com|http://twitter.com/commonsguy
>
> _The Busy Coder's Guide to Android Development_ Version 2.8
> Available!

-- 
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: Growing pains for Android developers??

2009-11-18 Thread Kieran
Thanks for your comment Dianne.

On Nov 17, 3:59 am, Dianne Hackborn  wrote:
> Sorry no I don't.
>
> On Mon, Nov 16, 2009 at 7:37 AM, Robert Woodruff wrote:
>
>
>
>
>
> > Dianne,
>
> > Nice to have response from someone inside Google.
>
> > Do you know when is 2.0 image available for ADP?
>
> > On Mon, Nov 16, 2009 at 2:54 AM, Dianne Hackborn wrote:
>
> >> On Sat, Nov 14, 2009 at 9:14 PM, Kieran  wrote:
>
> >>> Android 2 SDK released: 27th Oct
> >>> Droid released: 6th Nov
> >>> So that's 9 days (with a weekend) to test our apps at the new
> >>> resolution, make any necessary fixes, then deploy to the Market. I
> >>> don't think that's enough, and ultimately it's the Droid users that
> >>> suffer.
>
> >> Android 1.6 was released earlier with multiple screen support being one of
> >> the big new features.  This is not a new feature in 2.0, and in fact there
> >> will be devices shipping on 1.6 with different screens (I believe the 
> >> Tattoo
> >> QVGA device is an example).  We also started beating the drum as soon as 
> >> 1.6
> >> was available for people to update their apps, telling developers that 
> >> there
> >> would soon be devices appearing with different screens.  For example:
> >>http://android-developers.blogspot.com/2009/10/support-for-additional...
>
> >> Not that I think it is okay to have so little time between the SDK and
> >> devices shipping, but this particular case of supporting different screen
> >> sizes is a bad example of the issue.  The new contacts API would be better
> >> if you want to point at something.
>
> >> --
> >> 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, and so won't reply to such e-mails.  All such
> >> questions should be posted on public forums, where I and others can see and
> >> answer them.
>
> >>  --
> >> 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 >>  cr...@googlegroups.com>
> >> For more options, visit this group at
> >>http://groups.google.com/group/android-developers?hl=en
>
> >  --
> > 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 > cr...@googlegroups.com>
> > For more options, visit this group at
> >http://groups.google.com/group/android-developers?hl=en
>
> --
> 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, and so won't reply to such e-mails.  All such
> questions should be posted on public forums, where I and others can see and
> answer them.

-- 
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: Growing pains for Android developers??

2009-11-14 Thread Kieran
Android 2 SDK released: 27th Oct
Droid released: 6th Nov
So that's 9 days (with a weekend) to test our apps at the new
resolution, make any necessary fixes, then deploy to the Market. I
don't think that's enough, and ultimately it's the Droid users that
suffer.


On Nov 15, 1:00 am, wonae  wrote:
> Hey guys,
> I'm a Korean and we don't even find a way to sell our apps!!
> We have to earn a little cash only with AdMob :_(

-- 
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: Growing pains for Android developers??

2009-11-13 Thread Kieran
I'm not sure about anyone else but I just could not work out how to
buy an app from SlideMe. It had steps that it wanted you to do from my
desktop which isn't a big help when I'm on the bus! I was hoping they
would make it big as paid apps aren't available on Android Market for
my phone carrier.

My app has a small bug on QVGA devices (HTC Tattoo) but apart from
that everything is OK. I've programmed for Windows Mobile before and I
think Microsoft's new resolutions were well though out compared to
Google's. If you take the original res (HVGA for Android and QVGA for
WM) you'll see that Microsoft never made a res smaller than the res
everyone was used to. I have no ides how they came up with 854 x 480.

I'm also not happy about having to make a 2D icon when I had a nice 3D
one that met the guidelines! :)

On Nov 13, 11:42 pm, Kaj Bjurman  wrote:
> You can test Android 2.0 applications in the emulator. I've been able
> to correct a bug that I had on 2.0 even though I don't have a phone
> that supports 2.0.
>
> On 13 Nov, 13:57, WoodManEXP  wrote:
>
> > We have spent significant time & energy and $$ producing several
> > Android applications on the bet/hope it will be able to cut into the
> > iPhone market. Unfortunately little is happening.
>
> > - The apps sales are sluggish (the apps are hardly even being pirated
> > as far as we can tell).
> > - ADP cannot be updated to Android 2.0 yet Google has pushed hard for
> > development to be updated to 2.0 and the Droid phone is released. How
> > is one to test?
> > - The Google Market seems ineffective. Consider limitations like the
> > short app descriptions for instance. Google Market has a way to go to
> > catch up with the magic of iTunes.
> > - There is void of two-way communication between Google and the
> > Android developer base so rumor and conjecture and trial and error
> > prevail.
> > - Distribution license agreement is updated in a take it or leave it
> > fashion (with no meaningful explanation or attempt to point out
> > changes). What was that all about?
>
> > The list of this dings goes on. Understandably it is a huge
> > undertaking for Google/Verizon/HTC/Developers and the others to launch
> > Android and support it to go after the market Apple iPhone has proven.
> > On the plus side the SDK and ADP is obviously something Google has
> > invested heavily in and the basic Android system is, IMHO, superior to
> > iPhone system. So that's all good. Hopefully these developer
> > irritations are part of the growing pains and will quickly be
> > resolved.

-- 
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] Preference change notifying the main Activity

2009-11-13 Thread Kieran
Hi,
I think I've missed something in how Android is supposed to work!
I have the main Activity with a menu option that opens the preferences
screen. What I need is a way for any changes that were made to be
communicated back to the main Activity as soon as the preference is
activated. At the moment the only way I could get it working is by
using the intent data that gets sent back when the prefs activity
closes but this isn't really enough. The reason why it needs to be
instantaneous is that one of the preferences is a 'Clear cache'
button, so I would like the data to be deleted when the user requests
it and no later!

-- 
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: Building Dalvik

2009-02-04 Thread Kieran Bingham

Solved this by following the instructions at
http://www.mail-archive.com/android-port...@googlegroups.com/msg01340.html
Also realised - that looks like a more appropriate mailinglist too :)

--
Cheers
Kieran

2009/2/4 Kieran Bingham :
> Hi,
> I've used repo to get android - and wanted to build -but get the
> following error.
> It looks like some environment variable somewhere is getting messed up
> - but I'm having difficulty following it through the build system.
>
> In particular,
> *dalvik/libcore//home/kbingham/projects/android/dalvik/libcore/sub.mk:
> No such file or directory*
>
> looks like somehow the prefixing of the android_root folder has been
> prefixed (or not separated) with the subdirectory of the dalvik ?
>
> Can anyone help me with the following ?
>
> kbing...@atlas:~/projects/android$ make
> build/core/product_config.mk:211: WARNING: adding test OTA key
> 
> TARGET_PRODUCT=generic
> TARGET_BUILD_VARIANT=eng
> TARGET_SIMULATOR=
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_BUILD_TYPE=release
> BUILD_ID=
> 
> build/core/main.mk:180: implicitly installing apns-conf_sdk.xml
> /bin/bash: line 0: cd:
> dalvik/libcore//home/kbingham/projects/android/dalvik/libcore: No such
> file or directory
> /bin/bash: line 0: cd:
> dalvik/libcore//home/kbingham/projects/android/dalvik/libcore: No such
> file or directory
> dalvik/libcore/Android.mk:110:
> dalvik/libcore//home/kbingham/projects/android/dalvik/libcore/sub.mk:
> No such file or directory
> build/core/copy_headers.mk:15: warning: overriding commands for target
> `out/target/product/generic/obj/include/libpv/getactualaacconfig.h'
> build/core/copy_headers.mk:15: warning: ignoring old commands for
> target `out/target/product/generic/obj/include/libpv/getactualaacconfig.h'
> make: *** No rule to make target
> `dalvik/libcore//home/kbingham/projects/android/dalvik/libcore/sub.mk'.
> Stop.
> kbing...@atlas:~/projects/android$
>
>
> --
> Regards
>
> Kieran Bingham
>

--~--~-~--~~~---~--~~
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] Building Dalvik

2009-02-04 Thread Kieran Bingham

Hi,
I've used repo to get android - and wanted to build -but get the
following error.
It looks like some environment variable somewhere is getting messed up
- but I'm having difficulty following it through the build system.

In particular,
*dalvik/libcore//home/kbingham/projects/android/dalvik/libcore/sub.mk:
No such file or directory*

looks like somehow the prefixing of the android_root folder has been
prefixed (or not separated) with the subdirectory of the dalvik ?

Can anyone help me with the following ?

kbing...@atlas:~/projects/android$ make
build/core/product_config.mk:211: WARNING: adding test OTA key

TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=

build/core/main.mk:180: implicitly installing apns-conf_sdk.xml
/bin/bash: line 0: cd:
dalvik/libcore//home/kbingham/projects/android/dalvik/libcore: No such
file or directory
/bin/bash: line 0: cd:
dalvik/libcore//home/kbingham/projects/android/dalvik/libcore: No such
file or directory
dalvik/libcore/Android.mk:110:
dalvik/libcore//home/kbingham/projects/android/dalvik/libcore/sub.mk:
No such file or directory
build/core/copy_headers.mk:15: warning: overriding commands for target
`out/target/product/generic/obj/include/libpv/getactualaacconfig.h'
build/core/copy_headers.mk:15: warning: ignoring old commands for
target `out/target/product/generic/obj/include/libpv/getactualaacconfig.h'
make: *** No rule to make target
`dalvik/libcore//home/kbingham/projects/android/dalvik/libcore/sub.mk'.
Stop.
kbing...@atlas:~/projects/android$


--
Regards

Kieran Bingham

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---