[android-developers] Speech recognition private-API

[Tauno T]

Hi, a quick question about copying internal-APIs to my own project.

hackbod has said that "There should be nothing the regular built-in
apps do that you can't do in your own apps, except for some carefully
considered scenarios, such as dialing an emergency phone number or
directly installing an app without user intervention.". That means
that the private-API's still use low-level APIs that are public? So I
can pull the sources for the android.speech.recognition.* package and
it should compile just fine against the public SDK? (ok, I guess I
have to pull some more "convenience classes that are part of the
system that aren't ready for public use" but you get the idea..). So I
can just include the classes in my application and I don't have to
fear that you change/remove them in a later release (since they all
use public APIs a the end of the day)?

My point is that if your speech recognition is good enough for you
that you use it in your own apps (voicedialer) then it surely is good
enough for me to use it in my application!

Open source programming has always been about (for me at least) "don't
invent the bicycle". If I add something to the code or fix a bug, I'll
submit a patch and if I don't change anything then I can just use the
code and be happy with it?

Or are you suggesting that I write my own speech rec from scratch and
then when you are happy with the state of your implementation of it
and release it as a public API, I can throw away my implementation and
use your version of it?

I just want to know the personal opinion of the Android team regarding
taking private-APIs and bundling them with our apps :)

Tauno

--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: Tips for Orientation

[Tauno T]

I searched the documentation for this kind of functionality but I
overlook that one completely :(
Thanks for pointing that one out! That's exactly what I was looking
for.

Tauno

On Oct 21, 1:37 am, hackbod <[EMAIL PROTECTED]> wrote:
> Don't do that, or moving between your app and others will be flicker.
> Just use android:screenOrientation="sensor".
>
> On Oct 20, 12:47 pm, Tauno T <[EMAIL PROTECTED]> wrote:
>
> > And that's why he want's to set theorientationprogrammatically - the
> > users expect that when the phone is turned "sideways" then the picture
> > is also turned sideways:) The user is not confused - he just thinks
> > that Android has a feature that it does not have (sadly).
>
> > As for the solution - Xolotl Lokis solution will works just fine - you
> > only have to figure out which sensor reading corresponds to the phone
> > being held sideways and then change the layout using
> > setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_*);
>
> > Tauno
>
> > On Oct 20, 10:39 pm, hackbod <[EMAIL PROTECTED]> wrote:
>
> > > Your user is confused.  The standardorientationpolicy is to select
> > > theorientationbased on the keyboard: when the keyboard is closed it
> > > is portrait, when open it is landscape.  Pressing Ctrl+F12 in the
> > > emulator is exactly the same as sliding the keyboard out on the G1.
>
> > > On Oct 20, 11:57 am, Mark Hansen <[EMAIL PROTECTED]> wrote:
>
> > > > From what I was told by a user of my application, that it did not
> > > > change view, even when the keyboard was opened for text entry.
>
> > > > I've built two set's of layout files, and stored them in "layout" and
> > > > "layout-land" for when the view changes.  In emulator mode they work
> > > > fine, CTRL-F12 works fine.. but, and I may be misinformed here, it
> > > > appears the actual phone itself is not rotating the screen based on
> > > > the keyboard of position of the actual phone.
>
> > > > He even stated many of the default Google application aren't rotating
> > > > as well, and that very few actually change based on the way the device
> > > > is being held.
>
> > > > On Oct 20, 12:21 pm, hackbod <[EMAIL PROTECTED]> wrote:
>
> > > > > I don't know what you mean by "turn the view."  When theorientation
> > > > > changes to switch from the dominant to secondaryorientation(portrait
> > > > > to landscape on the g1), the graphics of the entire screen are rotated
> > > > > to result in the screen being shown in the neworientation.  As such,
> > > > > there is no need to do anything yourself, at it looks like to the
> > > > > application is that the size of the screen has changed to match the
> > > > > neworientation.
>
> > > > > For different resources, normally you also don't need to do anything,
> > > > > because when theorientationchanges the current activity is destroyed
> > > > > and a new one started, and the new one is running with a configuration
> > > > > matching the neworientationso will load the appropriate resources as
> > > > > it creates and initializes itself.
>
> > > > > The only except is if you are using android:configChanges to avoid
> > > > > being restarted due to a configuration change...  which is one of the
> > > > > reasons why it is strongly encouraged not to do this, and certainly if
> > > > > you are changing layouts due to theorientationI would really suggest
> > > > > letting the normal destroy/recreate path execute.  If you really
> > > > > really do want to mix the two, you will need to override
> > > > > onConfigurationChanged() and re-inflate your view hierarchy and re-
> > > > > initialize anything else depending on that or changing resources at
> > > > > that point.
>
> > > > > On Oct 20, 5:19 am, Mark Hansen <[EMAIL PROTECTED]> wrote:
>
> > > > > > I've actually created layouts for both vertical and horizontal 
> > > > > > views,
> > > > > > I've had some people testing it and it turns out Android doesn't 
> > > > > > turn
> > > > > > the view, I guess it has to be detected?
>
> > > > > > I was curious how to go about doing that detection.. I know I can 
> > > > > > also
> > > &

[android-developers] Re: Tips for Orientation

[Tauno T]

And that's why he want's to set the orientation programmatically - the
users expect that when the phone is turned "sideways" then the picture
is also turned sideways:) The user is not confused - he just thinks
that Android has a feature that it does not have (sadly).

As for the solution - Xolotl Lokis solution will works just fine - you
only have to figure out which sensor reading corresponds to the phone
being held sideways and then change the layout using
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_*);


Tauno

On Oct 20, 10:39 pm, hackbod <[EMAIL PROTECTED]> wrote:
> Your user is confused.  The standard orientation policy is to select
> the orientation based on the keyboard: when the keyboard is closed it
> is portrait, when open it is landscape.  Pressing Ctrl+F12 in the
> emulator is exactly the same as sliding the keyboard out on the G1.
>
> On Oct 20, 11:57 am, Mark Hansen <[EMAIL PROTECTED]> wrote:
>
> > From what I was told by a user of my application, that it did not
> > change view, even when the keyboard was opened for text entry.
>
> > I've built two set's of layout files, and stored them in "layout" and
> > "layout-land" for when the view changes.  In emulator mode they work
> > fine, CTRL-F12 works fine.. but, and I may be misinformed here, it
> > appears the actual phone itself is not rotating the screen based on
> > the keyboard of position of the actual phone.
>
> > He even stated many of the default Google application aren't rotating
> > as well, and that very few actually change based on the way the device
> > is being held.
>
> > On Oct 20, 12:21 pm, hackbod <[EMAIL PROTECTED]> wrote:
>
> > > I don't know what you mean by "turn the view."  When the orientation
> > > changes to switch from the dominant to secondary orientation (portrait
> > > to landscape on the g1), the graphics of the entire screen are rotated
> > > to result in the screen being shown in the new orientation.  As such,
> > > there is no need to do anything yourself, at it looks like to the
> > > application is that the size of the screen has changed to match the
> > > new orientation.
>
> > > For different resources, normally you also don't need to do anything,
> > > because when the orientation changes the current activity is destroyed
> > > and a new one started, and the new one is running with a configuration
> > > matching the new orientation so will load the appropriate resources as
> > > it creates and initializes itself.
>
> > > The only except is if you are using android:configChanges to avoid
> > > being restarted due to a configuration change...  which is one of the
> > > reasons why it is strongly encouraged not to do this, and certainly if
> > > you are changing layouts due to the orientation I would really suggest
> > > letting the normal destroy/recreate path execute.  If you really
> > > really do want to mix the two, you will need to override
> > > onConfigurationChanged() and re-inflate your view hierarchy and re-
> > > initialize anything else depending on that or changing resources at
> > > that point.
>
> > > On Oct 20, 5:19 am, Mark Hansen <[EMAIL PROTECTED]> wrote:
>
> > > > I've actually created layouts for both vertical and horizontal views,
> > > > I've had some people testing it and it turns out Android doesn't turn
> > > > the view, I guess it has to be detected?
>
> > > > I was curious how to go about doing that detection.. I know I can also
> > > > set the view with:
>
> > > > setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_*);
>
> > > > The problem I'm having is what event to trap or how to go about
> > > > determining which way the phone is being held.
>
> > > > On Oct 20, 12:13 am, hackbod <[EMAIL PROTECTED]> wrote:
>
> > > > > Use the android:screenOrientation attribute when declaring your
> > > > > manifest:
>
> > > > >http://code.google.com/android/reference/android/R.styleable.html#And...
>
> > > > >http://code.google.com/android/reference/android/R.styleable.html#And...
>
> > > > > On Oct 19, 3:23 pm, Mark Hansen <[EMAIL PROTECTED]> wrote:
>
> > > > > > I was thinking Android switched orientation automatically based on 
> > > > > > the
> > > > > > phones position but I'm finding from users this is not the case.
>
> > > > > > Anyone have some sample code on how to switch screen orientation 
> > > > > > based
> > > > > > on the position of the phone?
>
> > > > > > Thanks,
>
> > > > > > Mark
>
>
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: MAC address?

[Tauno T]

Just a note - this string is "null" in emulator and any application
can change the value of the string if it wants to (provided they have
the WRITE_SETTINGS permission).



Tauno

On Oct 18, 1:36 pm, Mark Murphy <[EMAIL PROTECTED]> wrote:
> Al Sutton wrote:
> > Just by looking at the docs, what about getting ANDROID_ID from the
> > System Settings?
>
> > The docs at
> >http://code.google.com/android/reference/android/provider/Settings.Sy...
> > say;
>
> >         public static final String
> >         
> >         ANDROID_ID
>
> > The Android ID (a unique 64-bit value) as a hex string. Identical to
> > that obtained by calling GoogleLoginService.getAndroidId(); it is also
> > placed here so you can get it without binding to a service.
> > Constant Value: "android_id"
>
> Ooo!
>
> That's got possibilities! It doesn't really say what the universe of
> "unique" is, but since it's static, one would hope it is unique to the
> device.
>
> I'll try it out later this morning -- many thanks!
>
> --
> Mark Murphy (a Commons Guy)http://commonsware.com
>
> Android Training on the Ranch! -- Mar 16-20, 
> 2009http://www.bignerdranch.com/schedule.shtml
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: Android FreeTTS server interfacing, a speech solution for your projects

[Tauno T]

Can I ask why you need to use TTS if you just want to play static
sound files like "wow" or "great job"?

Wouldn't it be easier if you just generated the sound files and
bundled them with your game? I mean.. it's just a matter of playing
back a few sound files that you can store in the /res/raw folder.


On Oct 17, 11:25 am, Wesley <[EMAIL PROTECTED]> wrote:
> hi,
>
> thanks to Alvaro Rivas, sharing out the TTS that you have done...
>
> but, many freeTTS interfacing??? isit?? most of them is not working???
>
> but Now, the only problem is, your freeTTS, need to have TTSserver... can it
> be offline one??? I mean standalone in Android devices...
>
> I know some package is removed... but...
>
> because I am developing game for android... hoping to have some TTS effect
> on it... like "wow!!!" or "Great Job" and so on...
> and my Game is offline... not going to be online... + I don't have enough
> resources to setup a server or TTS server
>
> any idea??
> did anyone have done the TTS??? can share out???
>
> I really hope Andriod can support TTS...
>
> your attention is highly appreciated...
>
> thanks...
>
> have a nice day...
>
> Wesley.
>
> On Sat, Oct 11, 2008 at 6:11 PM, Alvaro Rivas <[EMAIL PROTECTED]>wrote:
>
> > Hi blindFold,
> > It's a good thing that there are many freeTTS interfacing. The other two
> > projects I have no idea of the state of implementation. The only thing I
> > know is people has problems  getting speech.
>
> > My contribution is a simple way of getting speech in your applications. I
> > upload a sample hello word that is ok, it is finished, so you can adapt this
> > code in your code to get the speech.
>
> > I  had a lot of problems in order to get speech running in my applications,
> > I programmed a lot of ways until I had a way of getting speech. My
> > contribution may be not the best way but it is a real way of getting speech
> > because it is running.
>
> > Fell free to testing the 3 projects and if my project is the winner "bet",
> > I hope it will be very useful.
>
> > Best regards
>
> > 2008/10/11 blindfold <[EMAIL PROTECTED]>
>
> >> Hi Alvaro,
>
> >> Thanks for sharing!
>
> >> I see a bit of a problem in deciding which TTS interface to "bet" on.
> >> It seems that there are currently at least 3 projects aimed at
> >> offering FreeTTS functionality on Android, in different stages of
> >> development. There is the preliminary Android Market screenshot of the
> >> Text-to-Speech Library by Google's Charles Chen at the URL
>
> >>http://android-developers.blogspot.com/2008/08/android-market-user-dr...
>
> >> Then there is the porting project of FreeTTS by l1ghtm4n at the URL
>
> >>http://code.google.com/p/android-text2speech/
>
> >> and there is your (Alvaro Rivas') porting project of FreeTTS at the
> >> URL
>
> >>http://sourceforge.net/projects/freettsandroidi/
>
> >> Now most likely there will be various differences in the interfaces
> >> for invoking FreeTTS, so even though I am very interested in making
> >> use of FreeTTS on Android at some stage, and am neutral in my choices,
> >> I have no clear idea which of the three TTS projects I should focus
> >> on, and I am inclined to just wait-and-see to first find out which one
> >> turns out to be the most mature or de facto standard. Any ideas?
>
> >> Regards
>
> >> The vOICe Android for Android Phones
> >>http://www.artificialvision.com/android.htm
>
> >> On Oct 11, 1:47 am, "Alvaro Rivas" <[EMAIL PROTECTED]> wrote:
> >> > Hi,
>
> >> > Due to many question about a interfacing with FreeTTS or speech
> >> generation,
> >> > I decided to open source a part of my ADC I project. It is intended to
> >> be
> >> > used for all of you who wants to get a text to speech system in yours
> >> > developments.
>
> >> > Android-freeTTS reads from a Free TTS server a file that can be executed
> >> in
> >> > the android application in order to get speech.
>
> >> > Code has been ported to 1.0 Android SDK. I put a sample "hello word" in
> >> > order to see the results of a speech generation.
>
> >> > Many bugs can be found, but the idea is to give you a basic speech
> >> > generation in order to be included in your developments in others ADC's
>
> >> > Projects are Eclipse projects, maybe you must add JDK System library in
> >> your
> >> > projects.
>
> >> > A documentation file is supplied. Please read the howto section. (IP
> >> address
> >> > and other things must be configured before you use this).
>
> >> > Hope it helps you, if not, sorry!..
>
> >> >http://sourceforge.net/projects/freettsandroidi/
>
> >> > Thanks
>
>
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~--

[android-developers] Alternative to SpannableStringBuilder.drawText()?

[Tauno T]

The method
http://code.google.com/android/reference/android/text/SpannableStringBuilder.html#drawText(android.graphics.Canvas,%20int,%20int,%20float,%20float,%20android.graphics.Paint)

does not exist in the 1.0r1SDK - what is the alternative to draw
Spannable text (so that they are painted with the markup in the spans
already applied)?

And do I have to file a separate bug report for every documentation/
SDK mismatch I find or will the non-existent methods/classes/fields be
removed from the documentation automatically in the near future?



Currently it's quite frustrating that if you want to find features
that you want to implement then you always have to manually check if
the classes/methods/fields really exist.
I mean.. I spend half the day looking for some interesting methods/
classes that would be fun/useful to implement and I feel like "Oh,
wow, you can do THAT so easily in Android" and when I finally start to
implement the ideas, then I see that half of the methods/fields do not
exist and I have to scrap the idea.. I mean.. works hours cost
money :)


Tauno
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: DL Android

[Tauno T]

The source is not yet released. Sorry.
Quoting http://code.google.com/android/roadmap.html:

"Source Code Release

We are currently in the process of preparing for the release of the
source code. This includes a few key tasks:

* Selection of hosting infrastructure
* Updating the build infrastructure for general use
* Creation of a project governance framework
* Final examination of source code for release approval
* Physical upload and release packaging of the source code

This work is already under way, but since Android contains some 8
million lines of code, it's a lengthy process. We expect this process
to conclude (and source code to be released) in Q4 of 2008."



On Oct 17, 10:21 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> hey everyone,
>
> Does anybody know if we can download the Android Source (not the SDK,
> the real Android).
>
> And, if we can, somebody has a link??
>
> Thanks
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Contacts.PresenceColumns documentation/API mismatch.

[Tauno T]

(Sorry if it's a double post but the first message (sent ~20 hours
ago) disappeared from http://groups.google.com/group/android-developers
after some time and it never reached my mailbox)

The dox @ 
http://code.google.com/android/reference/android/provider/Contacts.PresenceColumns.html
indicate that android.provider.Contacts.PresenceColumns contains the
following public static fields: PRIORITY, PRESENCE_STATUS,
PRESENCE_CUSTOM_STATUS, OFFLINE, INVISIBLE, IDLE, DO_NOT_DISTURB,
AWAY, AVAILABLE, IM_PROTOCOL, IM_HANDLE, IM_ACCOUNT but the
android.jar from 1.0r1 contains only the following three public static
fields: IM_PROTOCOL, IM_HANDLE, IM_ACCOUNT.

Am I getting something totally wrong here or is there something
missing in the documentation/sdk?

Tauno
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Question regarding default Contacts application.

[Tauno T]

(Sorry if it's a double post but the first message (sent ~20 hours
ago) disappeared from http://groups.google.com/group/android-developers
after some time and it never reached my mailbox)

Hi,

I added a new contact in the default Contacts app and added all
possible IM names to it. If I click any of the IM options later, then
the following Intents are triggered:
Intent { action=android.intent.action.SENDTO
categories={com.android.im.category.MSN} data=im:name }
Intent { action=android.intent.action.SENDTO
categories={com.android.im.category.AIM} data=im:name}
Intent { action=android.intent.action.SENDTO
categories={com.android.im.category.ICQ} data=im:name }
Intent { action=android.intent.action.SENDTO
categories={com.android.im.category.GTALK} data=im:name }
Intent { action=android.intent.action.SENDTO
categories={com.android.im.category.YAHOO} data=im:name }


However no Intents are generated when clicking on Jabber, Skype and
QQ. Does anyone know whats up with that? Is the behaviour the same on
real devices? (And if so, then what's the point of adding these
contact types if you can't assign an application that handles these?)


Tauno

--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Contacts.PresenceColumns documentation/API mismatch.

[Tauno T]

The dox @ 
http://code.google.com/android/reference/android/provider/Contacts.PresenceColumns.html
indicate that android.provider.Contacts.PresenceColumns contains the
following public static fields: PRIORITY, PRESENCE_STATUS,
PRESENCE_CUSTOM_STATUS, OFFLINE, INVISIBLE, IDLE, DO_NOT_DISTURB,
AWAY, AVAILABLE, IM_PROTOCOL, IM_HANDLE, IM_ACCOUNT but the
android.jar from 1.0r1 contains only the following three public static
fields: IM_PROTOCOL, IM_HANDLE, IM_ACCOUNT.

Am I getting something totally wrong here or is there something
missing in the documentation/sdk?
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Question regarding default Contacts application.

[Tauno T]

Hi,

I added a new contact in the default Contacts app and added all
possible IM names to it. If I click any of the IM options later, then
the following Intents are triggered:
Intent { action=android.intent.action.SENDTO
categories={com.android.im.category.MSN} data=im:name }
Intent { action=android.intent.action.SENDTO
categories={com.android.im.category.AIM} data=im:name}
Intent { action=android.intent.action.SENDTO
categories={com.android.im.category.ICQ} data=im:name }
Intent { action=android.intent.action.SENDTO
categories={com.android.im.category.GTALK} data=im:name }
Intent { action=android.intent.action.SENDTO
categories={com.android.im.category.YAHOO} data=im:name }


However no Intents are generated when clicking on Jabber, Skype and
QQ. Does anyone know whats up with that? Is the behaviour the same on
real devices? (And if so, then what's the point of adding these
contact types if you can't assign an application that handles these?)


Tauno
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: scrolling listview loses background color/drawable

[Tauno T]

For future reference: it works with listView.setCacheColorHint(0) in
code or android:cacheColorHint="#" in xml.

I was sure that I tried this already and it didn't work but it turns
out the change didn't make it to the emulator when I was testing it.

Sorry.

Tauno

On Oct 7, 9:56 am, Tauno T <[EMAIL PROTECTED]> wrote:
> Added as issue 946 if anyone is 
> interested..http://code.google.com/p/android/issues/detail?id=946
>
> Tauno
>
> On Sep 29, 10:27 am,TaunoT<[EMAIL PROTECTED]> wrote:
>
> > "There must be something else you're doing that was wrong."
>
> > Can you please explain what's wrong in this setup? :)
>
> > New project.
> > * main.xml:
> > 
> > http://schemas.android.com/apk/res/
> > android"
> >                 android:layout_width="fill_parent"
> >         android:layout_height="fill_parent"
> >         android:background="@drawable/test">
>
> >      >           android:layout_width="fill_parent"
> >           android:layout_height="wrap_content"
> >           android:entries="@array/test"/>
> > 
>
> > * @drawable/test is a png filled with red (a: 255, r:255, g:0, b:0)
> > * Code:
> > public class ListViewTest extends Activity {
> >     @Override
> >     public void onCreate(Bundle savedInstanceState) {
> >         super.onCreate(savedInstanceState);
> >         setContentView(R.layout.main);
> >     }
>
> > }
>
> > It smells and looks like a bug to me personally.
>
> > On Sep 26, 11:08 am,TaunoT<[EMAIL PROTECTED]> wrote:
>
> > > Here you go:
>
> > > 
> > > http://schemas.android.com/apk/res/
> > > android"
> > >         android:orientation="vertical"
> > >         android:layout_width="fill_parent"
> > >         android:layout_height="fill_parent"
> > >         android:background="@drawable/some_image"
> > >         android:id="@+id/some_id">
>
> > >      > >           android:layout_width="fill_parent"
> > >           android:divider="@android:color/transparent"
> > >           (adding android:scrollingCache="false" here solves the
> > > problem)
> > >           android:layout_height="wrap_content"/>
> > > 
>
> > > The ListView uses a custom ArrayAdapter that returns Views inflated
> > > from the following xml:
>
> > > 
> > > http://schemas.android.com/apk/res/
> > > android"
> > >     android:layout_width="fill_parent"
> > >     android:layout_height="wrap_content" >
>
> > >         
> > >             
> > >              > >                 android:layout_width="fill_parent"
> > >                 android:layout_height="wrap_content" />
> > >         
>
> > >         
> > >                  > >                 android:layout_width="wrap_content"
> > >                 android:layout_height="wrap_content" />
> > >              > >                 android:layout_width="fill_parent"
> > >                 android:layout_height="wrap_content" />
> > >         
> > > 
>
> > > During the Activitys onCreate() another custom View is added to the
> > > inflated LinearLayout (id: some_id) using addView(CustomView, 0)
>
> > > On Sep 26, 9:54 am, "Romain Guy" <[EMAIL PROTECTED]> wrote:
>
> > > > You might notice it on an actual phone. You should not have to disable
> > > > the scrolling cache. There must be something else you're doing that
> > > > was wrong. Normally, disabling the cache color hint is all you need to
> > > > do. Could you show me your XML layout file?
>
> > > > On Thu, Sep 25, 2008 at 11:41 PM,TaunoT <[EMAIL PROTECTED]> wrote:
>
> > > > > Ok, managed to fix it by adding android:scrollingCache="false" to the
> > > > > ListView. From the dox it seems that it makes scrolling a little
> > > > > slower but I didn'tnotice any difference (have a list with ~100
> > > > > entries) - I guess it's too small to notice with my primitive list :)
>
> > > > > On Sep 26, 9:30 am,TaunoT <[EMAIL PROTECTED]> wrote:
> > > > >> Has anyone figured out a w

[android-developers] Re: scrolling listview loses background color/drawable

[Tauno T]

Added as issue 946 if anyone is interested..
http://code.google.com/p/android/issues/detail?id=946

Tauno

On Sep 29, 10:27 am, Tauno T <[EMAIL PROTECTED]> wrote:
> "There must be something else you're doing that was wrong."
>
> Can you please explain what's wrong in this setup? :)
>
> New project.
> * main.xml:
> 
> http://schemas.android.com/apk/res/
> android"
>                 android:layout_width="fill_parent"
>         android:layout_height="fill_parent"
>         android:background="@drawable/test">
>
>                android:layout_width="fill_parent"
>           android:layout_height="wrap_content"
>           android:entries="@array/test"/>
> 
>
> * @drawable/test is a png filled with red (a: 255, r:255, g:0, b:0)
> * Code:
> public class ListViewTest extends Activity {
>     @Override
>     public void onCreate(Bundle savedInstanceState) {
>         super.onCreate(savedInstanceState);
>         setContentView(R.layout.main);
>     }
>
> }
>
> It smells and looks like a bug to me personally.
>
> On Sep 26, 11:08 am,TaunoT<[EMAIL PROTECTED]> wrote:
>
> > Here you go:
>
> > 
> > http://schemas.android.com/apk/res/
> > android"
> >         android:orientation="vertical"
> >         android:layout_width="fill_parent"
> >         android:layout_height="fill_parent"
> >         android:background="@drawable/some_image"
> >         android:id="@+id/some_id">
>
> >      >           android:layout_width="fill_parent"
> >           android:divider="@android:color/transparent"
> >           (adding android:scrollingCache="false" here solves the
> > problem)
> >           android:layout_height="wrap_content"/>
> > 
>
> > The ListView uses a custom ArrayAdapter that returns Views inflated
> > from the following xml:
>
> > 
> > http://schemas.android.com/apk/res/
> > android"
> >     android:layout_width="fill_parent"
> >     android:layout_height="wrap_content" >
>
> >         
> >             
> >              >                 android:layout_width="fill_parent"
> >                 android:layout_height="wrap_content" />
> >         
>
> >         
> >                  >                 android:layout_width="wrap_content"
> >                 android:layout_height="wrap_content" />
> >              >                 android:layout_width="fill_parent"
> >                 android:layout_height="wrap_content" />
> >         
> > 
>
> > During the Activitys onCreate() another custom View is added to the
> > inflated LinearLayout (id: some_id) using addView(CustomView, 0)
>
> > On Sep 26, 9:54 am, "Romain Guy" <[EMAIL PROTECTED]> wrote:
>
> > > You might notice it on an actual phone. You should not have to disable
> > > the scrolling cache. There must be something else you're doing that
> > > was wrong. Normally, disabling the cache color hint is all you need to
> > > do. Could you show me your XML layout file?
>
> > > On Thu, Sep 25, 2008 at 11:41 PM,TaunoT <[EMAIL PROTECTED]> wrote:
>
> > > > Ok, managed to fix it by adding android:scrollingCache="false" to the
> > > > ListView. From the dox it seems that it makes scrolling a little
> > > > slower but I didn'tnotice any difference (have a list with ~100
> > > > entries) - I guess it's too small to notice with my primitive list :)
>
> > > > On Sep 26, 9:30 am,TaunoT <[EMAIL PROTECTED]> wrote:
> > > >> Has anyone figured out a workaround for this? I'm running out of ideas
> > > >> myself :(
>
> > > >> On Sep 24, 11:24 am,TaunoT<[EMAIL PROTECTED]> wrote:
>
> > > >> > I'm having the same issue.
> > > >> > A ListView is inside of a LinearLayout and the LinearLayout has a 
> > > >> > semi-
> > > >> > transparent background.
> > > >> > The background diappears while scrolling the ListView with the mouse.
>
> > > >> > Adding android:cacheColorHint="#" to the LinearLayout has no
> > > >> > effect.
>
> > > >> > On Sep 24, 11:02 am, hackbod <[EMAIL PROTECTED]> wrote:
>
> > > >> > > The color y

[android-developers] Re: What is google's official position on JNI ?

[Tauno T]

Oh, sorry, I misunderstood you there :)

On Oct 1, 12:37 pm, Volker Gropp <[EMAIL PROTECTED]> wrote:
> Hi,
>
> you may call it unfair of course. But please keep in mind, they did
> not tell us that they use it in their apps. But they use it in their
> API to delegate calls to native libs.
>
> Regards
> Volker
>
> On Oct 1, 11:18 am, Tauno T <[EMAIL PROTECTED]> wrote:
>
> > Isn't it a little .. how do I say it.. unfair to tell us that JNI is
> > not supported at all and then use it in their own apps to make them
> > better and give them more features than are available to the rest of
> > the developers?
>
> > On Oct 1, 11:49 am, Volker Gropp <[EMAIL PROTECTED]> wrote:
>
> > > Hi Ranjeet,
>
> > > although I'm not the Android Dev Team i can tell you what ive been
> > > told last weeks about this topic: JNI is currently not supported in
> > > SDK 1.0. The reason is not quite clear, some say cause it may not work
> > > at all, or may break in the (near) future. Plus your app wont be
> > > portable and needs special versions for every hw platform. Actually i
> > > bet Android Dev Team will just tell you: "native libs and JNI is not
> > > supported!".
>
> > > On the other hand JNI is working and Android uses it internally a lot
> > > [google talks]. But you may have problems to link against the stripped
> > > down libc they are using, or may run into other problems you cannot
> > > resolve. Plus please keep in mind there is no real solution to deploy
> > > your app on real phones, because /system/lib is read only. You might
> > > add your .so into the apk as a raw resource and extract it into your
> > > app writable directory under /data. Loading the .so works for me using
> > > System.load(). But this way the .so is stored on your phone in 2
> > > locations, using a lot unnecessary space.
>
> > > Currently for a real world app on real phones i would'nt use JNI and
> > > native libs at all due to those problems. Either wait for JNI support
> > > in future SDK versions or port your library to Java.
>
> > > Regards
> > > Volker
>
> > > On Oct 1, 4:02 am, Ranjeet <[EMAIL PROTECTED]> wrote:
>
> > > > Dear Android Dev Team,
>
> > > > My apologies if I am asking a question that's already been answered.
> > > > Unfortunately I haven't been able to find any documentation within
> > > > Android's reference that officially states Google's position on usage
> > > > of JNI/SharedObjects (written in C++ and compiled via a cross
> > > > compiler) from within Java ui code.  To clarify what I am trying to
> > > > accomplish, we are building an application with the user interface
> > > > completely written using the java/android classes/controls and it
> > > > would use the shared library thats written in C++. There is just so
> > > > much effort gone in to making that library that it would be a LOT of
> > > > effort on our side rewriting it in Java. The library connects to our
> > > > backend web server to fetch XML files over HTTP, stores some of the
> > > > information from it on disk in files, and exposes the features via
> > > > methods.
>
> > > > Is this currently "officially supported" in Android(I have seen hello
> > > > world C++ apps that run on the emulator with some security/chmod
> > > > tweaks).
> > > > Any information is sincerely appreciated.
>
> > > > Thanks,
> > > > -Ranjeet
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: What is google's official position on JNI ?

[Tauno T]

Isn't it a little .. how do I say it.. unfair to tell us that JNI is
not supported at all and then use it in their own apps to make them
better and give them more features than are available to the rest of
the developers?

On Oct 1, 11:49 am, Volker Gropp <[EMAIL PROTECTED]> wrote:
> Hi Ranjeet,
>
> although I'm not the Android Dev Team i can tell you what ive been
> told last weeks about this topic: JNI is currently not supported in
> SDK 1.0. The reason is not quite clear, some say cause it may not work
> at all, or may break in the (near) future. Plus your app wont be
> portable and needs special versions for every hw platform. Actually i
> bet Android Dev Team will just tell you: "native libs and JNI is not
> supported!".
>
> On the other hand JNI is working and Android uses it internally a lot
> [google talks]. But you may have problems to link against the stripped
> down libc they are using, or may run into other problems you cannot
> resolve. Plus please keep in mind there is no real solution to deploy
> your app on real phones, because /system/lib is read only. You might
> add your .so into the apk as a raw resource and extract it into your
> app writable directory under /data. Loading the .so works for me using
> System.load(). But this way the .so is stored on your phone in 2
> locations, using a lot unnecessary space.
>
> Currently for a real world app on real phones i would'nt use JNI and
> native libs at all due to those problems. Either wait for JNI support
> in future SDK versions or port your library to Java.
>
> Regards
> Volker
>
> On Oct 1, 4:02 am, Ranjeet <[EMAIL PROTECTED]> wrote:
>
> > Dear Android Dev Team,
>
> > My apologies if I am asking a question that's already been answered.
> > Unfortunately I haven't been able to find any documentation within
> > Android's reference that officially states Google's position on usage
> > of JNI/SharedObjects (written in C++ and compiled via a cross
> > compiler) from within Java ui code.  To clarify what I am trying to
> > accomplish, we are building an application with the user interface
> > completely written using the java/android classes/controls and it
> > would use the shared library thats written in C++. There is just so
> > much effort gone in to making that library that it would be a LOT of
> > effort on our side rewriting it in Java. The library connects to our
> > backend web server to fetch XML files over HTTP, stores some of the
> > information from it on disk in files, and exposes the features via
> > methods.
>
> > Is this currently "officially supported" in Android(I have seen hello
> > world C++ apps that run on the emulator with some security/chmod
> > tweaks).
> > Any information is sincerely appreciated.
>
> > Thanks,
> > -Ranjeet
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: scrolling listview loses background color/drawable

[Tauno T]

"There must be something else you're doing that was wrong."

Can you please explain what's wrong in this setup? :)

New project.
* main.xml:

http://schemas.android.com/apk/res/
android"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:background="@drawable/test">




* @drawable/test is a png filled with red (a: 255, r:255, g:0, b:0)
* Code:
public class ListViewTest extends Activity {
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
}
}


It smells and looks like a bug to me personally.


On Sep 26, 11:08 am, Tauno T <[EMAIL PROTECTED]> wrote:
> Here you go:
>
> 
> http://schemas.android.com/apk/res/
> android"
>         android:orientation="vertical"
>         android:layout_width="fill_parent"
>         android:layout_height="fill_parent"
>         android:background="@drawable/some_image"
>         android:id="@+id/some_id">
>
>                android:layout_width="fill_parent"
>           android:divider="@android:color/transparent"
>           (adding android:scrollingCache="false" here solves the
> problem)
>           android:layout_height="wrap_content"/>
> 
>
> The ListView uses a custom ArrayAdapter that returns Views inflated
> from the following xml:
>
> 
> http://schemas.android.com/apk/res/
> android"
>     android:layout_width="fill_parent"
>     android:layout_height="wrap_content" >
>
>         
>             
>                              android:layout_width="fill_parent"
>                 android:layout_height="wrap_content" />
>         
>
>         
>                                  android:layout_width="wrap_content"
>                 android:layout_height="wrap_content" />
>                              android:layout_width="fill_parent"
>                 android:layout_height="wrap_content" />
>         
> 
>
> During the Activitys onCreate() another custom View is added to the
> inflated LinearLayout (id: some_id) using addView(CustomView, 0)
>
> On Sep 26, 9:54 am, "Romain Guy" <[EMAIL PROTECTED]> wrote:
>
> > You might notice it on an actual phone. You should not have to disable
> > the scrolling cache. There must be something else you're doing that
> > was wrong. Normally, disabling the cache color hint is all you need to
> > do. Could you show me your XML layout file?
>
> > On Thu, Sep 25, 2008 at 11:41 PM,TaunoT <[EMAIL PROTECTED]> wrote:
>
> > > Ok, managed to fix it by adding android:scrollingCache="false" to the
> > > ListView. From the dox it seems that it makes scrolling a little
> > > slower but I didn't notice any difference (have a list with ~100
> > > entries) - I guess it's too small to notice with my primitive list :)
>
> > > On Sep 26, 9:30 am,TaunoT <[EMAIL PROTECTED]> wrote:
> > >> Has anyone figured out a workaround for this? I'm running out of ideas
> > >> myself :(
>
> > >> On Sep 24, 11:24 am,TaunoT<[EMAIL PROTECTED]> wrote:
>
> > >> > I'm having the same issue.
> > >> > A ListView is inside of a LinearLayout and the LinearLayout has a semi-
> > >> > transparent background.
> > >> > The background diappears while scrolling the ListView with the mouse.
>
> > >> > Adding android:cacheColorHint="#" to the LinearLayout has no
> > >> > effect.
>
> > >> > On Sep 24, 11:02 am, hackbod <[EMAIL PROTECTED]> wrote:
>
> > >> > > The color you have (#000) is solid black.  Use # for a
> > >> > > completely transparent color.
>
> > >> > > On Sep 23, 9:33 pm, Nickname <[EMAIL PROTECTED]> wrote:
>
> > >> > > > Thank you, butit does NOT fix the problem.
>
> > >> > > > Here is what i added to layout xml of the listview:
>
> > >> > > >         ...
> > >> > > >         android:background="@drawable/background"
> > >> > > >         ...
> > >> > > >         android:cacheColorHint="#000"
> > >> > > >         ...
> > >> > > >         android:layout_width="fill_parent"
> > >> > > >         ..

[android-developers] Re: Vote: a device G1 for each ADC entrance

[Tauno T]

Did Apple give every app developer a free or otherwise special device?
No.
Is Symbian giving free (or selling) new devices to developers who
can't buy them officially? No.
Is Sun giving free (or selling) J2ME enabled devices to developers who
can't buy them officialy? No.
The same goes for Windows/Brew/BlackBerry etc etc devices.

Sorry but you can't expect that an OS developer (like Google) is
selling (or giving away for free) devices (that a completely unrelated
company produces(HTC) and a third unrelated company sells (T-Mobile))
to the developers who want to develop on these platforms.



On Sep 26, 3:14 pm, arnouf <[EMAIL PROTECTED]> wrote:
> We could pay something to have a hardware device...not particularly
> free!
> Just have a device for each developer, even if developer have to pay
> (it should be a little bit normal).
>
> Regards
>
> On Sep 26, 1:21 pm, Timbobsteve <[EMAIL PROTECTED]> wrote:
>
> > I am all for Devs getting access to the hardware and I don't think
> > that it should be selected regions either, but I also don't think
> > Google, HTC and T-Mobile "owe" us free devices. I think if Devs could
> > buy subsidized developer hardware before it is released publicly, it
> > would greatly increase the quality of software.
>
> > Having said that, a lot of software will be OSS and OSS Developers
> > have battled without such courtesies for many years so hardware is
> > a bonus. I know many devs that building software for iPhone, GP2X and
> > Xbox without even having access to the device. All testing had to be
> > done through a select group of testers before being released.
>
> > My 2p
> > Timbobsteve
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: intercept incoming and outgoing calls and have customized screen

[Tauno T]

You could do that but there's a catch if you want to see the changes
on a real device - you would have to push the changed Android source
code to phone manufacturers so they use your modified version of the
OS on new phones.

Correct me if I'm wrong..


On Sep 26, 11:02 am, "Pulkit Arora" <[EMAIL PROTECTED]> wrote:
> Thanks for ur reply.. One more question, i believe the android team will be
> releasing the source for the OS in December, i hope i will be able to do any
> kind of tweaks in it then, as in overriding the incoming call event etc.. ?
>
>
>
> On Fri, Sep 26, 2008 at 1:23 PM, hackbod <[EMAIL PROTECTED]> wrote:
>
> > You can't replace the call screen in 1.0.  You can, however, intercept
> > outgoing calls:
>
> >http://code.google.com/android/reference/android/content/Intent.html#...
>
> > On Sep 25, 6:35 pm, chouman82 <[EMAIL PROTECTED]> wrote:
> > > Is it possible to intercept the intent of calling and answering and by
> > > doing that replacing the calling/answering screen.
> > > I see from the logcat that right now com.android.phone.InCallScreen
> > > activity is been started.  Anyway to overwrite that to have my own
> > > activity to show up?
>
> --
> Pulkit Arora
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: scrolling listview loses background color/drawable

[Tauno T]

Here you go:


http://schemas.android.com/apk/res/
android"
android:orientation="vertical"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:background="@drawable/some_image"
android:id="@+id/some_id">




The ListView uses a custom ArrayAdapter that returns Views inflated
from the following xml:


http://schemas.android.com/apk/res/
android"
android:layout_width="fill_parent"
android:layout_height="wrap_content" >












During the Activitys onCreate() another custom View is added to the
inflated LinearLayout (id: some_id) using addView(CustomView, 0)


On Sep 26, 9:54 am, "Romain Guy" <[EMAIL PROTECTED]> wrote:
> You might notice it on an actual phone. You should not have to disable
> the scrolling cache. There must be something else you're doing that
> was wrong. Normally, disabling the cache color hint is all you need to
> do. Could you show me your XML layout file?
>
>
>
> On Thu, Sep 25, 2008 at 11:41 PM, Tauno T <[EMAIL PROTECTED]> wrote:
>
> > Ok, managed to fix it by adding android:scrollingCache="false" to the
> > ListView. From the dox it seems that it makes scrolling a little
> > slower but I didn't notice any difference (have a list with ~100
> > entries) - I guess it's too small to notice with my primitive list :)
>
> > On Sep 26, 9:30 am, Tauno T <[EMAIL PROTECTED]> wrote:
> >> Has anyone figured out a workaround for this? I'm running out of ideas
> >> myself :(
>
> >> On Sep 24, 11:24 am,TaunoT<[EMAIL PROTECTED]> wrote:
>
> >> > I'm having the same issue.
> >> > A ListView is inside of a LinearLayout and the LinearLayout has a semi-
> >> > transparent background.
> >> > The background diappears while scrolling the ListView with the mouse.
>
> >> > Adding android:cacheColorHint="#" to the LinearLayout has no
> >> > effect.
>
> >> > On Sep 24, 11:02 am, hackbod <[EMAIL PROTECTED]> wrote:
>
> >> > > The color you have (#000) is solid black.  Use # for a
> >> > > completely transparent color.
>
> >> > > On Sep 23, 9:33 pm, Nickname <[EMAIL PROTECTED]> wrote:
>
> >> > > > Thank you, butit does NOT fix the problem.
>
> >> > > > Here is what i added to layout xml of the listview:
>
> >> > > >         ...
> >> > > >         android:background="@drawable/background"
> >> > > >         ...
> >> > > >         android:cacheColorHint="#000"
> >> > > >         ...
> >> > > >         android:layout_width="fill_parent"
> >> > > >         ...
>
> >> > > > On Sep 23, 4:53 pm, "Romain Guy" <[EMAIL PROTECTED]> wrote:
>
> >> > > > > Set ListView's cache color hint to 0.
>
> >> > > > > On Sep 23, 2008 6:26 PM, "Nickname" <[EMAIL PROTECTED]> wrote:
>
> >> > > > > It happens to android emulator, on xp as i know.
>
> >> > > > > I depress mouse pointer to scroll a listview. While it scrolls, the
> >> > > > > background drawable disappers. When i release the mouse, the
> >> > > > > background still disappear till i move mouse to touch the screen.
>
> >> > > > > This is a harmless issue but makes me uneasy.
>
> --
> Romain Guywww.curious-creature.org
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: SDK1.0 and 0.9

[Tauno T]

Release notes for 1.0r1: http://code.google.com/android/RELEASENOTES.html
Overview of changes in 1.0r1 compared to 0.9:
http://code.google.com/android/migrating/0.9-1.0/changes-overview.html
API differences in 1.0r1 compared to 0.9:
http://code.google.com/android/migrating/0.9-1.0/changes.html

On Sep 26, 8:27 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> what are the differences between the SDK 1.0 and 0.9?. Any one Please
> give me a reply...
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: SDK 1.0:

[Tauno T]

Release notes for 1.0r1: http://code.google.com/android/RELEASENOTES.html
Overview of changes in 1.0r1 compared to 0.9:
http://code.google.com/android/migrating/0.9-1.0/changes-overview.html
API differences in 1.0r1 compared to 0.9:
http://code.google.com/android/migrating/0.9-1.0/changes.html

On Sep 26, 9:48 am, "De San Nicolas Jean Philippe" <[EMAIL PROTECTED]>
wrote:
> vast no, but there is, with sqlite for exemple
>
> 2008/9/26 dhuri natarajan <[EMAIL PROTECTED]>
>
> > Is there any vast difference between the SDK released 1.0 and 0.9 beta?.
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: scrolling listview loses background color/drawable

[Tauno T]

Ok, managed to fix it by adding android:scrollingCache="false" to the
ListView. From the dox it seems that it makes scrolling a little
slower but I didn't notice any difference (have a list with ~100
entries) - I guess it's too small to notice with my primitive list :)

On Sep 26, 9:30 am, Tauno T <[EMAIL PROTECTED]> wrote:
> Has anyone figured out a workaround for this? I'm running out of ideas
> myself :(
>
> On Sep 24, 11:24 am,TaunoT<[EMAIL PROTECTED]> wrote:
>
> > I'm having the same issue.
> > A ListView is inside of a LinearLayout and the LinearLayout has a semi-
> > transparent background.
> > The background diappears while scrolling the ListView with the mouse.
>
> > Adding android:cacheColorHint="#" to the LinearLayout has no
> > effect.
>
> > On Sep 24, 11:02 am, hackbod <[EMAIL PROTECTED]> wrote:
>
> > > The color you have (#000) is solid black.  Use # for a
> > > completely transparent color.
>
> > > On Sep 23, 9:33 pm, Nickname <[EMAIL PROTECTED]> wrote:
>
> > > > Thank you, butit does NOT fix the problem.
>
> > > > Here is what i added to layout xml of the listview:
>
> > > >         ...
> > > >         android:background="@drawable/background"
> > > >         ...
> > > >         android:cacheColorHint="#000"
> > > >         ...
> > > >         android:layout_width="fill_parent"
> > > >         ...
>
> > > > On Sep 23, 4:53 pm, "Romain Guy" <[EMAIL PROTECTED]> wrote:
>
> > > > > Set ListView's cache color hint to 0.
>
> > > > > On Sep 23, 2008 6:26 PM, "Nickname" <[EMAIL PROTECTED]> wrote:
>
> > > > > It happens to android emulator, on xp as i know.
>
> > > > > I depress mouse pointer to scroll a listview. While it scrolls, the
> > > > > background drawable disappers. When i release the mouse, the
> > > > > background still disappear till i move mouse to touch the screen.
>
> > > > > This is a harmless issue but makes me uneasy.
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: scrolling listview loses background color/drawable

[Tauno T]

Has anyone figured out a workaround for this? I'm running out of ideas
myself :(


On Sep 24, 11:24 am, Tauno T <[EMAIL PROTECTED]> wrote:
> I'm having the same issue.
> A ListView is inside of a LinearLayout and the LinearLayout has a semi-
> transparent background.
> The background diappears while scrolling the ListView with the mouse.
>
> Adding android:cacheColorHint="#" to the LinearLayout has no
> effect.
>
> On Sep 24, 11:02 am, hackbod <[EMAIL PROTECTED]> wrote:
>
> > The color you have (#000) is solid black.  Use # for a
> > completely transparent color.
>
> > On Sep 23, 9:33 pm, Nickname <[EMAIL PROTECTED]> wrote:
>
> > > Thank you, butit does NOT fix the problem.
>
> > > Here is what i added to layout xml of the listview:
>
> > >         ...
> > >         android:background="@drawable/background"
> > >         ...
> > >         android:cacheColorHint="#000"
> > >         ...
> > >         android:layout_width="fill_parent"
> > >         ...
>
> > > On Sep 23, 4:53 pm, "Romain Guy" <[EMAIL PROTECTED]> wrote:
>
> > > > Set ListView's cache color hint to 0.
>
> > > > On Sep 23, 2008 6:26 PM, "Nickname" <[EMAIL PROTECTED]> wrote:
>
> > > > It happens to android emulator, on xp as i know.
>
> > > > I depress mouse pointer to scroll a listview. While it scrolls, the
> > > > background drawable disappers. When i release the mouse, the
> > > > background still disappear till i move mouse to touch the screen.
>
> > > > This is a harmless issue but makes me uneasy.
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: WebView and #links

[Tauno T]

Thanks Mark, it works just fine when using loadDataWithBaseUrl(). I'll
file a bug about that then since it seems like a bug to me :)

On Sep 25, 5:45 pm, Mark Murphy <[EMAIL PROTECTED]> wrote:
> Tauno T wrote:
> > I have a problem with WebView.
> > If I call loadData() with a String parameter that has an anchor with a
> > href that contains the symbol "#" then the WebView will not render
> > anything after that statement.
>
> > For example:
> > loadData("Jump to the Useful Tips Section > \"tips\">Useful Tips Section", "text/html", "utf-8");
> > IS NOT working.
>
> > loadData("http://google.com\";>Jump to the Useful Tips
> > SectionUseful Tips Section", "text/html",
> > "utf-8");
> > IS working.
>
> > The only difference is the actual link.
> > If I save the stuff as a html file on a webserver and open it using
> > loadUrl(); then everything works as expected.
>
> > Am I missing something here or is WebView broken?
>
> Try using loadDataWithBaseUrl(), even giving it a totally bogus base URL
> (e.g., fake://this/is/strange). I wound up switching to this mechanism
> based on a related bug report I filed. It got me past a local-access
> security restriction. I don't know if it will help in this case, but
> it's worth a quick check.
>
> Let us know how it works out.
>
> --
> Mark Murphy (a Commons Guy)http://commonsware.com
> Warescription: All titles, revisions, & ebook formats, just $35/year
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] WebView and #links

[Tauno T]

Hi all!

I have a problem with WebView.
If I call loadData() with a String parameter that has an anchor with a
href that contains the symbol "#" then the WebView will not render
anything after that statement.

For example:
loadData("Jump to the Useful Tips SectionUseful Tips Section", "text/html", "utf-8");
IS NOT working.

loadData("http://google.com\";>Jump to the Useful Tips
SectionUseful Tips Section", "text/html",
"utf-8");
IS working.

The only difference is the actual link.
If I save the stuff as a html file on a webserver and open it using
loadUrl(); then everything works as expected.

Am I missing something here or is WebView broken?
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] (documentation) Is there a typo in ViewTreeObserver.dispatchOnPreDraw() ?

[Tauno T]

>From the dox: "...If a listener returns true, then the drawing pass is
canceled and rescheduled"
It seems to be the opposite.
I tried it and if my listener returns true, then the view hierarchy
will draw just fine but when my listener returns false, then the
hierarchy won't be drawn.

Or am I not getting the point here? :)
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: scrolling listview loses background color/drawable

[Tauno T]

I'm having the same issue.
A ListView is inside of a LinearLayout and the LinearLayout has a semi-
transparent background.
The background diappears while scrolling the ListView with the mouse.

Adding android:cacheColorHint="#" to the LinearLayout has no
effect.

On Sep 24, 11:02 am, hackbod <[EMAIL PROTECTED]> wrote:
> The color you have (#000) is solid black.  Use # for a
> completely transparent color.
>
> On Sep 23, 9:33 pm, Nickname <[EMAIL PROTECTED]> wrote:
>
> > Thank you, butit does NOT fix the problem.
>
> > Here is what i added to layout xml of the listview:
>
> >         ...
> >         android:background="@drawable/background"
> >         ...
> >         android:cacheColorHint="#000"
> >         ...
> >         android:layout_width="fill_parent"
> >         ...
>
> > On Sep 23, 4:53 pm, "Romain Guy" <[EMAIL PROTECTED]> wrote:
>
> > > Set ListView's cache color hint to 0.
>
> > > On Sep 23, 2008 6:26 PM, "Nickname" <[EMAIL PROTECTED]> wrote:
>
> > > It happens to android emulator, on xp as i know.
>
> > > I depress mouse pointer to scroll a listview. While it scrolls, the
> > > background drawable disappers. When i release the mouse, the
> > > background still disappear till i move mouse to touch the screen.
>
> > > This is a harmless issue but makes me uneasy.
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Determining if an Activity is visible

[Tauno T]

Hi all!

A quick question - is there a way to determine if an activity is
visible to the user or not? I'd like to display a notification to the
user but only then when the user is not seeing any of my Activities.

I figure that one possibility is to raise a flag in onResume() and
lower it in onPause() but it's not the best solution for me (since the
app has  way too much Activities in total and implementing this in
every one of them "manually" seems like a silly thing to do)

Tauno

--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: Intercept incoming call

[Tauno T]

I don't agree that changing the in call screen/incoming call screen/
outgoing call screen should be only available to handset manufacturers/
operators. A phone could do SO much more when applications could
somehow hook into these screens (or even control the voice streams).

Imagine an application that could show the name of an unknown caller
based on data gathered from the Internet.
Or an application that displays additional call information while the
call is in progress (eg call length/cost/quality/voice equalizer).
Or an application that let's you choose between a normal call or a
VoIP call when you press the green dial button when selecting a
contact from the "native" phone book.
Or an application that can change the actual voice stream that is
transmitted - so you could add effects such as high/low pitch etc to
your outgoing call.

There are many more fun/useful applications that could benefit from
this openness of the OS. Of course there are security concerns but
still..

For a regular user a call would work like a call and it would be sort
of like a call but for "advanced" users who download these
applications (and click on thousands of security warnings when
installing the app) the phone would be so much more than the phones
that are on the market today.

Just my 2 cents..


On Sep 17, 6:47 pm, "Mark Murphy" <[EMAIL PROTECTED]> wrote:
> > I think the idea is that certain key functions of the phone - calling,
> > and going to the home screen - usurp other functions. All non built-in
> > key functions, e.g. applications, are still equal, but yes a few key
> > functions have a higher priority
>
> I suspect there will be two tiers of development for Android.
>
> At the level of the SDK, you're probably correct -- not each and every
> phone function can be replaced or hooked into, in part for security
> reasons.
>
> If you're willing to roll your own firmware, though, you'll probably be
> able to do whatever you want. So if you're creating your own phone, and
> you want to create a different dialer or in-call display than what stock
> Android comes with, you can probably do it.
>
> Leastways, that's how I'm reading the various tea leaves.
>
> --
> Mark Murphy (a Commons Guy)http://commonsware.com
> _The Busy Coder's Guide to Android Development_ Version 1.2 Published!

--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: Intercept incoming call

[Tauno T]

I wonder if this will be possible on real devices? It should be
according to the "All applications are equal" statement but has anyone
further info regarding this?

On Sep 17, 8:01 am, "Megha Joshi" <[EMAIL PROTECTED]> wrote:
> Unfortunately, you cannot intercept incoming calls in the sdk.
>
> 2008/9/16 sectrean <[EMAIL PROTECTED]>
>
>
>
> > Hi,
>
> > I'm trying to figure out how to intercept an incoming call, but I'm
> > not able to find much documentation on how I would do this.
>
> > I would like to be able to display a custom dialog to accept or reject
> > the call.

--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---