The G1s, as far as I know, got an Over-The-Air upgrade to v1.5 when it
came out. The only thing that the older hardware precludes you from is
testing your app on the newer hardware. The SDK is the same (unless
somebody simply did not update their Android version on the phone).
On Aug 14, 2:23
I'm not sure about the coordinates thing, but if you are trying to use
rotateAnimation to rotate something such that it looks like it is
spinning in-place, then 0,0 are not the coordinates you want. The
coordinates are a 'pivot point'; you could think of them as the
'middle' of the rotation.
If
I was pointed to http://www.android.com/branding.html when I had
questions about some different legal issues. I checked and there isn't
anything there regarding the G1 hardware... I guess because T-Mobile
or somebody else probably owns the hardware licensing?
I doubt anybody is really going to
Hi Mark, I'm pretty unfamiliar with detecting actual Airplane mode
settings, but I do have a potential work-around for you in case you
can't get it working the way you're trying to (which, by the way,
definitely seems like the -right- way to do it). I've been checking
for network connections
I would recommend looking into using AsyncTask to do this (http://
developer.android.com/reference/android/os/AsyncTask.html).
You can check against your mp.isPlaying() in the doInBackground
portion, use a sleep for some appropriate amount of time if it is
still playing (else finish the task),
It really depends on the structure of your app, but one trick you
might employ is to launch your various activities with
startActivityForResult(intent, ID);
and then override onActivityResult to watch for a return value from
the activity you launched. You can then make decisions about whether
you
Bump - any thoughts on this?
On Aug 6, 12:48 pm, jhoffman keshis...@gmail.com wrote:
One other thing I forgot to mention, I checked a few of the strategies
posted on Android-Developers in similar threads, but unfortunately
none of them have worked for me :(
Solutions tried so far were
After all was said and done, that last issue appeared to be a matter
of RelativeLayout and RotateAnimation not playing as nicely together
as I thought. The 'visual' buttons were in a different place than the
'actual' buttons were. I switched to a LinearLayout setup, and things
behaved a lot
Agreed! The orientation issues were a problem for me in an app I
recently developed :(
It ends up working out okay, but if there were support for either
orientation, I think I could've made the app a bit cooler...
On Jul 29, 2:26 pm, Sophie shkass...@gmail.com wrote:
Hi developers,
As I'm just
One other thing I forgot to mention, I checked a few of the strategies
posted on Android-Developers in similar threads, but unfortunately
none of them have worked for me :(
Solutions tried so far were:
Restarting Eclipse
Performing a 'Clean'
Performing a 'Fix Project Properties'
Performing a
Romain, the solution you gave me works perfectly for rotating the
layout upside-down. Unfortunately, I now have another problem! After
the layout has been rotated, the Views no longer respond to clicks and
long clicks. Inside of the RelativeLayout I am rotating, I have a
textView that I allow the
Yeah my apologies on the double-post... I wasn't aware of the
moderation on new posters when I tried to post. I thought maybe the
internet ate my first post. Really sorry to double post, but thank you
both very much for your help, I'll try those approaches now!
On Jul 27, 2:49 am, Jeff Sharkey
12 matches
Mail list logo
