Tried on 1.6 G1 and 2.1 Droid - no problems.
Minor bug - when switching sound packs before starting the metronome
with FCE off, for the first click the sound from the previous pack is
used.
Also, support for custom sounds will be among the first things users
will ask for :)
On Apr 14, 6:59 am,
Vladmir,
Thanks for your feedback! It´s nice to hear it´s working on 1.6 and
2.1. Indeed, I´m releasing a 1.5 compatible version tonight!
Before this release I will check this bug you have mentioned, but it´s
probably fixed as I have found another minor bug related to starting
the metronome with
I´ve just sent you an e-mail with a beta version for Android 1.5.
I hope it works now. Also, I hope you can help me with a feedback
about the app version I´ve sent you.
Thanks,
Gabriel Simões
On 5 abr, 10:07, Yahel kaye...@gmail.com wrote:
No worries Gabriel,
I really don't know why this
Guys ... the app is on version 1.0.2 now and flurry doesn´t show up
any errors at all!
Seems to be good news but it only shows no exception was caught, but
it doesn´t prove if the app works the way it should: if the click
period doesn´t vary at all, if it´s precise, if it´s synzronized with
UI
got to keep an iphone 3gs check it out.
clickhttp://bizoppoffer.com/x/0/759/6428/
2010/4/5 Gabriel Simões gsim...@gmail.com
Working on Google Nexus One (v 1.0.2) (Thanks for the feedback Bob)
Any other reports?
Also, are the UI changes (click count) syncronized with the sound
click well?
Not working on a Hero - Android 1.5.
When I try to launch your app, it says it cannot run against this
device.
Which Api Level did you use. From the screenshot, I can't see a reason
why you would have purposedly exclude Android 1.5 from your build.
From the screenshot again, your metronome
I ran into this recently. Try this in your AndroidManifest.xml
uses-sdk
android:minSdkVersion=3
android:targetSdkVersion=4 /
--
Android Academy http://androidacademy.com
On Apr 5, 6:01 am, Gabriel Simões gsim...@gmail.com wrote:
Hi all,
After spending some time learning about Android´s SDK
Updating right now
On 5 abr, 08:03, Carl Whalley carl.whal...@googlemail.com wrote:
I ran into this recently. Try this in your AndroidManifest.xml
uses-sdk
android:minSdkVersion=3
android:targetSdkVersion=4 /
--
Android Academyhttp://androidacademy.com
On Apr 5, 6:01 am, Gabriel
I have just updated the app to v. 1.0.1
- Fixed a reported bug on AudioTrack´s internal buffersize
- Added Android 1.5
The thing I´d like to know is how well are the audio click and UI
changes syncronized. It´s hard to measure it using the emulator and
right now Android is not made for it. Tried
Ok, I can run it now but the layout is completely off :
http://www.mediafire.com/imageview.php?quickkey=tyaiewfnk0ithumb=4
Yahel
On 5 avr, 13:46, Gabriel Simões gsim...@gmail.com wrote:
I have just updated the app to v. 1.0.1
- Fixed a reported bug on AudioTrack´s internal buffersize
-
The layout was built using Relative Layout.
By what I´ve read so far, it should work on 1.5, right? I´ve also read
elsewhere that until 1.6 relative layout had problems with the order
in which the widgets where built.
Yahel, sorry for the inconvenience, I will try to fix it as soon as
possible,
No worries Gabriel,
I really don't know why this layout problem appears, doesn't really
show off the compile once/run everywhere mantra :D
Tell me if you find a fix, I'll try it again.
Yahel
On 5 avr, 14:37, Gabriel Simões gsim...@gmail.com wrote:
The layout was built using Relative Layout.
After a little more investigation it seems this issue is related to
RelativeLayout on Android up to 1.5
There's a known bug that up to cupcake, RelativeLayout would build
the UI based on the order in which you declare the widgets on you
Action's XML.
This way, you could end with views drawn one
Also, the compile once run everywhere mantra is known for itś
incompatibilities between different versions of the virtual machine!
hehehehe
On Apr 5, 10:52 am, Gabriel Simões gsim...@gmail.com wrote:
After a little more investigation it seems this issue is related to
RelativeLayout on Android
Relating working on Google Nexus One (v 1.0.2)
Any other reports?
Also, is the UI syncronizing with the sound click well?
Thanks for your time and patience.
On 5 abr, 10:55, Gabriel Simões gsim...@gmail.com wrote:
Also, the compile once run everywhere mantra is known for itś
incompatibilities
Working on Google Nexus One (v 1.0.2) (Thanks for the feedback Bob)
Any other reports?
Also, are the UI changes (click count) syncronized with the sound
click well?
Thanks for your time and patience.
On 5 abr, 10:55, Gabriel Simões gsim...@gmail.com wrote:
Also, the compile once run
16 matches
Mail list logo
