[android-developers] Adding AdMob jar to javac breaks compilation
Hello, I am trying to add AdMob to my project, but I have a big problem during the compilation part. Basically I have a script which does all the steps to generate the APK. When I don't add the AdMob jar, my script works perfectly, except that javac will throw an error that AdMob is not declared. But if I add the AdMob jar, like this: SET PATH=C:\Programas\android-sdk\tools;C:\Programas\android-sdk\platform-tools\;C:\Program Files (x86)\Java\jre6\bin;C:\Program Files\Java\jdk1.6.0_45\bin;C:\Programas\android-sdk\build-tools\17.0.0 SET APP_NAME=truedemocracy SET ANDROID_HOME=C:\Programas\android-sdk SET APK_SDK_PLATFORM=C:\Programas\android-sdk\platforms\android-11 SET APK_PROJECT_PATH=C:\Programas\felipedocs\Programas\publicpolicy\android SET APK_PACKAGE_PATH=com\felipe\truedemocracy REM Java compiler call javac -verbose -classpath %APK_SDK_PLATFORM%\android.jar:C:\Programas\GoogleAdMobAdsSdkAndroid-6.4.1\GoogleAdMobAdsSdk-6.4.1.jar -d bin\classes src\%APK_PACKAGE_PATH%\TrueDemocracy.java gen\%APK_PACKAGE_PATH%\R.java src\com\jjoe64\graphview\*.java src\com\jjoe64\graphview\compatible\*.java Then I get: [search path for source files: C:\Programas\android-sdk\platforms\android-11\and roid.jar:C:\Programas\GoogleAdMobAdsSdkAndroid-6.4.1\GoogleAdMobAdsSdk-6.4.1.jar ] [search path for class files: C:\Program Files\Java\jdk1.6.0_45\jre\lib\resource s.jar,C:\Program Files\Java\jdk1.6.0_45\jre\lib\rt.jar,C:\Program Files\Java\jdk 1.6.0_45\jre\lib\sunrsasign.jar,C:\Program Files\Java\jdk1.6.0_45\jre\lib\jsse.j ar,C:\Program Files\Java\jdk1.6.0_45\jre\lib\jce.jar,C:\Program Files\Java\jdk1. 6.0_45\jre\lib\charsets.jar,C:\Program Files\Java\jdk1.6.0_45\jre\lib\modules\jd k.boot.jar,C:\Program Files\Java\jdk1.6.0_45\jre\classes,C:\Program Files\Java\j dk1.6.0_45\jre\lib\ext\dnsns.jar,C:\Program Files\Java\jdk1.6.0_45\jre\lib\ext\l ocaledata.jar,C:\Program Files\Java\jdk1.6.0_45\jre\lib\ext\sunjce_provider.jar, C:\Program Files\Java\jdk1.6.0_45\jre\lib\ext\sunmscapi.jar,C:\Program Files\Jav a\jdk1.6.0_45\jre\lib\ext\sunpkcs11.jar,C:\Programas\android-sdk\platforms\andro id-11\android.jar:C:\Programas\GoogleAdMobAdsSdkAndroid-6.4.1\GoogleAdMobAdsSdk- 6.4.1.jar] src\com\felipe\truedemocracy\TrueDemocracy.java:3: package android.app does not exist import android.app.*; ^ src\com\felipe\truedemocracy\TrueDemocracy.java:4: package android.content does not exist import android.content.*; and hundreds more of errors everywhere If I remove AdMob from my project and compile like this: call javac -verbose -classpath %APK_SDK_PLATFORM%\android.jar -d bin\classes src\%APK_PACKAGE_PATH%\TrueDemocracy.java gen\%APK_PACKAGE_PATH%\R.java src\com\jjoe64\graphview\*.java src\com\jjoe64\graphview\compatible\*.java Then everything works great! But as soon as I add the admob jar it goes crazy =( I double checked that : should be the correct separator and I tryed also using , Any ideas? thanks, Felipe Monteiro de Carvalho -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Need Html5 and Phone gap Examples with Android.
Hi All, I would like to learn and develop the apps on Html5 and Phonegap. Earlier I was worked on Android so want learn but i have searched a lot on web but i didn't get good links so guys can you help me out in this. Appreciated if any one share good examples/links/blogs... -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Adding AdMob jar to javac breaks compilation
call javac -verbose -classpath %APK_SDK_PLATFORM%\android.jar:C:\Programas\GoogleAdMobAdsSdkAndroid-6.4.1\GoogleAdMobAdsSdk-6.4.1.jar -d bin\classes src\%APK_PACKAGE_PATH%\TrueDemocracy.java gen\%APK_PACKAGE_PATH%\R.java src\com\jjoe64\graphview\*.java src\com\jjoe64\graphview\compatible\*.java You have used : (colon) as path separator, while on windows it's ; (semicolon). -- Bart -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Adding AdMob jar to javac breaks compilation
I am trying to add AdMob to my project, but I have a big problem during the compilation part. Basically I have a script which does all the steps to generate the APK. When I don't add the AdMob jar, my script works perfectly, except that javac will throw an error that AdMob is not declared. But if I add the AdMob jar, like this: BTW. I'd strongly recommend using ant for that, standard android SDK generated ant can be easily extended and it's more robust solution for APK deplyment. -- Bart -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Need Html5 and Phone gap Examples with Android.
Hi buddy , please find the below whih gives a basic idea abt html5 usae in andriod http://www.youtube.com/watch?v=uVqp1zcMfbE On Fri, May 24, 2013 at 11:46 AM, vamshi ch vamshi0...@gmail.com wrote: Hi All, I would like to learn and develop the apps on Html5 and Phonegap. Earlier I was worked on Android so want learn but i have searched a lot on web but i didn't get good links so guys can you help me out in this. Appreciated if any one share good examples/links/blogs... -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] detect intrumentation
Hello, i would like to know how to find out if the app is running in an intrumentation runner? Thanks Daniel -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Adding AdMob jar to javac breaks compilation
thanks, indeed that was the problem! Felipe Monteiro de Carvalho -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] How to change name of app in the drawer?
Hi, How can I change the name of my app name when it shows up as an icon in the app drawer? I want to change my name from DMToolbox_BETA to DMToolbox. Every time I try to upload another one, it wants ONLY DMToolbox_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 android-developers+unsubscr...@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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: How to change name of app in the drawer?
(I use MIT's AppInventor) -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Get context of PopupMenu like ContextMenu
Hey Kostya, Thanks. The getTag() and setTag() methods of a View are exactly what i needed. -Etienne -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Get context of PopupMenu like ContextMenu
Hey Kostya, Thanks. The getTag() and setTag() methods of a View are exactly what i needed. -Etienne -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
I am glad you found a solution, guys. I haven't tried it yet, but I will. But I still don't get it. Some of my apps which are still listed as compatible with the Galay Tablet 10.1 (GT-P7500), only supports 3 screen sizes. (xlarge was introduced in Android 2.3, and these apps only require a minimum of Android 2.2), and their AndroidManifest file ONLY have a mimimum Sdk Version (and NOT a target one) ! And the GT-P7500 has an *xlarge *screen*.* So - this seems to be a confusing and messy business. Terry On Thursday, May 23, 2013 11:52:46 PM UTC+2, bob wrote: Yes, setting *android:targetSdkVersion* to 11 worked for me. Thanks. On Thursday, May 23, 2013 2:23:29 PM UTC-5, Fredrik Hyttnäs-Lenngren wrote: Confirmed! Adding *android:targetSdkVersion *with a value higher or equal to 11 fixed this issue. On Thursday, 23 May 2013 19:20:04 UTC+2, Fredrik Hyttnäs-Lenngren wrote: I added the *android:targetSdkVersion *with a value higher or equal to 11 to my manifest file and uploading it to the developer console. The apk details now highlights *xlarge * as a new feature. Going to publish the update and see if it REALLY did it or if it's just the Developer Console fooling me. // Fredrik On Thursday, 23 May 2013 17:50:41 UTC+2, jjbunn wrote: Hi Fredrik, I'm also having the same problem as OP. Nothing changed in my Manifest, or build procedure, but now Google Play marks my app as incompatible with e.g. the Nexus 10. It would be really nice if there was some way of asking Google directly if they have changed something, rather than us all speculating on what might have happened or what the fix might be :-) If I browse the APK in the dev. console I see the following. (I'm not sure what this information means precisely - I've never looked at it before!) Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades. Less - Devices currently running *version 76* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 4 and *Screen layouts* containing any of [small, normal, large, xlarge*]and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] - Devices currently running *version 13* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 3 and *Screen layouts* containing any of [normal, large*, xlarge*] and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] Julian On Thursday, May 23, 2013 2:35:05 AM UTC-7, Fredrik Hyttnäs-Lenngren wrote: I actually see now that when I browse the APK in the developer console to read the details about it, that it claims that it only supports 3-screen-layout, rather than 4 (xlarge missing). It should be possible to tinker with the manifest and upload a new apk, look at the details and verify what does the trick instead of uploading - publish - wait - check - repeat... // Fredrik On Thursday, 23 May 2013 09:21:09 UTC+2, Fredrik Hyttnäs-Lenngren wrote: Did you update the apps My Anchor Watch Free and My Anchor Watch Pro or did they just suddenly become incompatible? I'm looking towards adding the *android:targetSdkVersion *to one of my apps and release it and see if it works. This is exactly the issue Google had with the Hangout app not being compatible with tables once they update it from Talk, so they must have been caught by surprise as well. Fredrik On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: I don't think that *android:**minSdkVersion or ** android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the *android:targetSdkVersion* included within the *uses-sdk *tag while the others only have the *android:minSdkVersion. * * * * * On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: I have not found a common denominator yet. Strangely enough, those of my apps which are suddenly incompatible with the GT-P7500, (according to Play Store), are listed as compatible with the same device in the Developers Console. So it seems pretty
[android-developers] Re: Suddenly Lots of Apps in Play Store are no longer compatible my Galaxy Tablet
I have apps which also only supports 3 screen sizes (according to APK details) where I don't have *android:targetSdkVersion *in the uses-sdk tag, but still show up on xlarge devices. Only difference is that I have not updated them recently. I believe that this requirement only applies to updates/new-apps. // Fredrik On Friday, 24 May 2013 10:31:01 UTC+2, Terry wrote: I am glad you found a solution, guys. I haven't tried it yet, but I will. But I still don't get it. Some of my apps which are still listed as compatible with the Galay Tablet 10.1 (GT-P7500), only supports 3 screen sizes. (xlarge was introduced in Android 2.3, and these apps only require a minimum of Android 2.2), and their AndroidManifest file ONLY have a mimimum Sdk Version (and NOT a target one) ! And the GT-P7500 has an *xlarge *screen*.* So - this seems to be a confusing and messy business. Terry On Thursday, May 23, 2013 11:52:46 PM UTC+2, bob wrote: Yes, setting *android:targetSdkVersion* to 11 worked for me. Thanks. On Thursday, May 23, 2013 2:23:29 PM UTC-5, Fredrik Hyttnäs-Lenngren wrote: Confirmed! Adding *android:targetSdkVersion *with a value higher or equal to 11 fixed this issue. On Thursday, 23 May 2013 19:20:04 UTC+2, Fredrik Hyttnäs-Lenngren wrote: I added the *android:targetSdkVersion *with a value higher or equal to 11 to my manifest file and uploading it to the developer console. The apk details now highlights *xlarge * as a new feature. Going to publish the update and see if it REALLY did it or if it's just the Developer Console fooling me. // Fredrik On Thursday, 23 May 2013 17:50:41 UTC+2, jjbunn wrote: Hi Fredrik, I'm also having the same problem as OP. Nothing changed in my Manifest, or build procedure, but now Google Play marks my app as incompatible with e.g. the Nexus 10. It would be really nice if there was some way of asking Google directly if they have changed something, rather than us all speculating on what might have happened or what the fix might be :-) If I browse the APK in the dev. console I see the following. (I'm not sure what this information means precisely - I've never looked at it before!) Previously active APKs supported more devices than those in the draft configuration. Some devices will not receive upgrades. Less - Devices currently running *version 76* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 4 and *Screen layouts* containing any of [small, normal, large, xlarge*]and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] - Devices currently running *version 13* are no longer supported by the current configuration. Such devices will not receive upgrades. *API levels* = 3 and *Screen layouts* containing any of [normal, large*, xlarge*] and *Features* containing all of [android.hardware.MICROPHONE, android.hardware.TOUCHSCREEN] Julian On Thursday, May 23, 2013 2:35:05 AM UTC-7, Fredrik Hyttnäs-Lenngren wrote: I actually see now that when I browse the APK in the developer console to read the details about it, that it claims that it only supports 3-screen-layout, rather than 4 (xlarge missing). It should be possible to tinker with the manifest and upload a new apk, look at the details and verify what does the trick instead of uploading - publish - wait - check - repeat... // Fredrik On Thursday, 23 May 2013 09:21:09 UTC+2, Fredrik Hyttnäs-Lenngren wrote: Did you update the apps My Anchor Watch Free and My Anchor Watch Pro or did they just suddenly become incompatible? I'm looking towards adding the *android:targetSdkVersion *to one of my apps and release it and see if it works. This is exactly the issue Google had with the Hangout app not being compatible with tables once they update it from Talk, so they must have been caught by surprise as well. Fredrik On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: I don't think that *android:**minSdkVersion or ** android:targetSdkVersion *has anything to do with it. Some of my apps which are now shown as incompatible *and *some which are still compatible, *both *only have the *android:**minSdkVersion *in the AndroidManifest file. Two of my apps which were shown in the Play Store as compatible only a few days aga, but which are now shown as incompatible (with e.g. GT-P7500) are My Anchor Watch Free and My Anchor Watch Pro. They are both listed as compatible (with this particular device) in the Developer's Console. Terry On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren wrote: I published a completely new app at the same time I published the updates, and it shows up on Google Play for all devices. Only difference I can see between them is that the new app has the *android:targetSdkVersion* included within the
[android-developers] Re: Fragment state (and view) not restored when using ViewPager with nested fragments
Hi!
So, I checked onAttachActivity and onDetach and this is very puzzling.
onAttach is called, I store the reference to the activity, but onDetach
is not called, and when I try to call getActivity(), or reference the
stored activity, I always get null back.
So that is the reason FragmentManager is failing as well, only I don't know
why the activity is missing...?
If I dump the fragment manager, I see that the activity is there (see
emphasis):
Active Fragments in 414896e0:
#0: null
#1: ConnectFragment{41505ae0 #1 id=0x7f060001}
mFragmentId=#7f060001 mContainerId=#7f060001 mTag=null
mState=5 mIndex=1 mWho=android:fragment:1 mBackStackNesting=0
mAdded=true mRemoving=false mResumed=true mFromLayout=false
mInLayout=false
mHidden=false mDetached=false mMenuVisible=false mHasMenu=false
mRetainInstance=false mRetaining=false mUserVisibleHint=false
mFragmentManager=FragmentManager{414896e0 in MainActivity{41489470}}
mActivity=com.islonline.isllightdesign.MainActivity@41489470
mContainer=android.support.v4.view.ViewPager{4145c668 VFED
0,0-800,1033 #7f060001 app:id/pager}
mView=android.support.v4.app.NoSaveStateFrameLayout{414b1258 V.E.
800,0-1600,1033}
mInnerView=android.support.v4.app.NoSaveStateFrameLayout{414b1258
V.E. 800,0-1600,1033}
#2: MainFilesFragment{4155a430 #2 id=0x7f060001}
mFragmentId=#7f060001 mContainerId=#7f060001 mTag=null
mState=5 mIndex=2 mWho=android:fragment:2 mBackStackNesting=0
mAdded=true mRemoving=false mResumed=true mFromLayout=false
mInLayout=false
mHidden=false *mDetached=false* mMenuVisible=true mHasMenu=false
mRetainInstance=false mRetaining=false mUserVisibleHint=true
mFragmentManager=FragmentManager{414896e0 in MainActivity{41489470}}
*mActivity=com.islonline.isllightdesign.MainActivity@41489470*
mContainer=android.support.v4.view.ViewPager{4145c668 VFED
0,0-800,1033 #7f060001 app:id/pager}
mView=android.support.v4.app.NoSaveStateFrameLayout{4155bcf8 V.E.
1600,0-2400,1033}
mInnerView=android.support.v4.app.NoSaveStateFrameLayout{4155bcf8
V.E. 1600,0-2400,1033}
Child FragmentManager{4155b598 in MainFilesFragment{4155a430}}:
Active Fragments in 4155b598:
#0: ComputerListFragment{4155b7b8 #0 id=0x7f060010 COMPUTER_LIST}
mFragmentId=#7f060010 mContainerId=#7f060010 mTag=COMPUTER_LIST
mState=1 mIndex=0 mWho=android:fragment:2:0 mBackStackNesting=1
mAdded=false mRemoving=true mResumed=false mFromLayout=false
mInLayout=false
mHidden=false mDetached=false mMenuVisible=true mHasMenu=false
mRetainInstance=false mRetaining=false mUserVisibleHint=true
mFragmentManager=FragmentManager{4155b598 in
MainFilesFragment{4155a430}}
*mActivity=com.islonline.isllightdesign.MainActivity@41489470*
mParentFragment=MainFilesFragment{4155a430 #2 id=0x7f060001}
mSavedViewState=android.util.SparseArray@41690a60
#1: FileShareBrowserFragment{41690840 #1 id=0x7f060010}
mFragmentId=#7f060010 mContainerId=#7f060010 mTag=null
mState=5 mIndex=1 mWho=android:fragment:2:1 mBackStackNesting=1
mAdded=true mRemoving=false mResumed=true mFromLayout=false
mInLayout=false
mHidden=false mDetached=false mMenuVisible=true mHasMenu=false
mRetainInstance=false mRetaining=false mUserVisibleHint=true
mFragmentManager=FragmentManager{4155b598 in
MainFilesFragment{4155a430}}
*mActivity=com.islonline.isllightdesign.MainActivity@41489470*
mParentFragment=MainFilesFragment{4155a430 #2 id=0x7f060001}
mContainer=android.widget.FrameLayout{4155b210 V.E.
0,0-800,1033 #7f060010 app:id/file_browser_container}
mView=android.support.v4.app.NoSaveStateFrameLayout{41698148
V.E. 0,0-800,1033}
mInnerView=android.support.v4.app.NoSaveStateFrameLayout{41698148
V.E. 0,0-800,1033}
#2: null
Added Fragments:
#0: FileShareBrowserFragment{41690840 #1 id=0x7f060010}
Back Stack:
#0: BackStackEntry{41690780 #0}
mName=null mIndex=0 mCommitted=true
Operations:
Op #0: REPLACE FileShareBrowserFragment{41690840 #1
id=0x7f060010}
Removed: ComputerListFragment{4155b7b8 #0 id=0x7f060010
COMPUTER_LIST}
Back Stack Indices:
#0: BackStackEntry{41690780 #0}
Any help or pointers on what to look for would be appreciated!
Thanks!
Miha
On Thursday, May 23, 2013 9:51:07 PM UTC+2, Miha wrote:
Hi Streets Of Boston!
On Thursday, May 23, 2013 4:16:22 PM UTC+2, Streets Of Boston wrote:
When using fragments inside a fragment, you should use the fragment's
ChildFragmentManager and not the (activity's) main FragmentManager.
You are right. It's working when using child fragment manager, but the
backstack inside the child fragment
[android-developers] License check on free apps ?
Hi, according to: http://developer.android.com/google/play/licensing/overview.html it's possible to use the Google Play Licensing service on free apps. The page says You can implement licensing controls for a free app, but only if you're using the service to provide APK expansion fileshttp://developer.android.com/google/play/expansion-files.html Now, i tried this approach and indeed i get back from the store app a ResponseData with a LICENCED response code. My question is: does anybody know if this request can fail (see : return anything but LICENCED) on free app? So far i don't really understand under which condition this license control could fail with a free app. Thanks for the help! Andrea -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] License check on free apps ?
On Fri, May 24, 2013 at 6:11 PM, reaand andrea.carlev...@gmail.com wrote: Now, i tried this approach and indeed i get back from the store app a ResponseData with a LICENCED response code. My question is: does anybody know if this request can fail (see : return anything but LICENCED) on free app? So far i don't really understand under which condition this license control could fail with a free app. Probably if you side loaded the app. The whole idea of this 'license' check is to make sure that people that didn't download the app from the Play Store don't hit their servers and download GB's of data files. -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: DisplayMetrics xdpi and ydpi returning incorrect values
I was just being hti by this problem as I'm working on my own UI engine and I need to calculate my own device indepentent unit ratio using these XDPI and YDPI values So how the Android native UI is calculating the DP (independent device unit) on a device where the DPI is incorrectly set? Does tha mean the native UI is then wrongly scaled as well? Thanks for any usful information. Rick On Tuesday, 25 October 2011 22:27:04 UTC+2, Dianne Hackborn wrote: Sorry you just can't use them. Nothing in the platform makes use of them. They need to be set by the manufacturer (there is no way for the platform to know what they are), and as of today they are just not consistently set correctly across devices, and because nothing in the platform relies on them it is easy for devices to have them set incorrectly. This information is just not available, sorry to say. Why do you need the actual physical dpi? On Tue, Oct 25, 2011 at 12:44 PM, ashughes ashu...@gmail.comjavascript: wrote: The values reported by xdpi and ydpi are still incorrect on some devices. Samsung Galaxy Tab 10.1 (from Google I/O): xdpi: 160.15764 ydpi: 160.0 Lenovo ThinkPad Tablet: xdpi: 160.15764 ydpi: 160.0 HTC Jetstream: xdpi: 150.51852 ydpi: 149.41176 The Galaxy Tab and ThinkPad Tablet report incorrect values, while the Jetstream reports correct values. I don't know why the xdpi and ydpi values are different (unless they *actually* are on they physical display, in which case that makes sense since both values for the Jetstream are close to the correct overall value). Is the value reported by xdpi and ydpi set somewhere by the device manufacturer? Is that why the values are correct on some devices and not on others? Is there going to be any guarantee in the future that these values will always be reported as correct (it would be great if this were a requirement for passing the CTS)? It would be really helpful to be able to reliably query for the actual dpi of a device without having to rely on a database of known device values. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@googlegroups.comjavascript: To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hac...@android.com javascript: 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Opera App Store?
Has anyone else had an email from Opera trying to get you to develop for their app store? *One of the leading independent app stores in the world, the Opera Mobile Store, has doubled its traffic in a year, reaching 60,000,000 monthly visitors and more than 2,000,000 app downloads per day. The strongest growth has been attained in the emerging markets such as India, Russia, Brazil, Mexico and others. More than 12,000 developers have already significantly grown their user-base as a result of cooperation with our Store. We invite you to become the Opera Mobile Store partner-developer and benefit from the great international mobile user audience.* * * Personally I'm not really interested but has anyone else had this email? Steve -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] License check on free apps ?
That was my guess. But i am running my test app on a phone with play account that is not my dev account, and it's not in the list of License Test accounts that you can set in the dev portal. Still i get LICENSED all the time... On Friday, May 24, 2013 11:22:02 AM UTC+2, Nikolay Elenkov wrote: On Fri, May 24, 2013 at 6:11 PM, reaand andrea.c...@gmail.comjavascript: wrote: Now, i tried this approach and indeed i get back from the store app a ResponseData with a LICENCED response code. My question is: does anybody know if this request can fail (see : return anything but LICENCED) on free app? So far i don't really understand under which condition this license control could fail with a free app. Probably if you side loaded the app. The whole idea of this 'license' check is to make sure that people that didn't download the app from the Play Store don't hit their servers and download GB's of data files. -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Seeking advice for a suite of apps
I am considering a single 'foundation' app that contains: a custom Account (for AccountManager), a SyncAdapter and all of the ContentProviders for use by the actual 'consuming' apps. The idea is that the 'foundation' app is a pre-requisite for the 'consuming' apps as it provides their Account addition/login, data layer and data-sync. I just wanted to ask the community if this sounds sane and for tips of anyone who has achieved this architecture. 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 android-developers+unsubscr...@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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Fragment state (and view) not restored when using ViewPager with nested fragments
I checked the childFragmentManager state, and surprisingly, it is empty.
So, the fragmentmanager dump output in previous posting shows all of the
fragments, but when doing the same with child fragment manager, the output
is:
FragmentManager misc state:
mActivity=null
mContainer=android.support.v4.app.Fragment$1@41603ca0
mParent=MainFilesFragment{4169ccf0}
mCurState=0 mStateSaved=false mDestroyed=false
Why is that?
Regards,
Miha.
On Friday, May 24, 2013 10:54:12 AM UTC+2, Miha wrote:
Any help or pointers on what to look for would be appreciated!
--
--
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
---
You received this message because you are subscribed to the Google Groups
Android Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Google Wallet spam
Since yesterday I get spammed by Google Wallet. At least a 100 emails a day telling me about a failed credit card check, and telling me not to ship. -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Opera App Store?
Yes, we got it too. I haven't yet got around to sorting out what my opinion is. :-) On Fri, May 24, 2013 at 11:57 AM, reaktor24 stevebruc...@gmail.com wrote: Has anyone else had an email from Opera trying to get you to develop for their app store? *One of the leading independent app stores in the world, the Opera Mobile Store, has doubled its traffic in a year, reaching 60,000,000 monthly visitors and more than 2,000,000 app downloads per day. The strongest growth has been attained in the emerging markets such as India, Russia, Brazil, Mexico and others. More than 12,000 developers have already significantly grown their user-base as a result of cooperation with our Store. We invite you to become the Opera Mobile Store partner-developer and benefit from the great international mobile user audience.* * * Personally I'm not really interested but has anyone else had this email? Steve -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: DisplayMetrics xdpi and ydpi returning incorrect values
The UI doesn't use these values. We use the density field instead so that the conversion factor is the same on both axis. On May 24, 2013 2:56 AM, Rick rsmo...@gmail.com wrote: I was just being hti by this problem as I'm working on my own UI engine and I need to calculate my own device indepentent unit ratio using these XDPI and YDPI values So how the Android native UI is calculating the DP (independent device unit) on a device where the DPI is incorrectly set? Does tha mean the native UI is then wrongly scaled as well? Thanks for any usful information. Rick On Tuesday, 25 October 2011 22:27:04 UTC+2, Dianne Hackborn wrote: Sorry you just can't use them. Nothing in the platform makes use of them. They need to be set by the manufacturer (there is no way for the platform to know what they are), and as of today they are just not consistently set correctly across devices, and because nothing in the platform relies on them it is easy for devices to have them set incorrectly. This information is just not available, sorry to say. Why do you need the actual physical dpi? On Tue, Oct 25, 2011 at 12:44 PM, ashughes ashu...@gmail.com wrote: The values reported by xdpi and ydpi are still incorrect on some devices. Samsung Galaxy Tab 10.1 (from Google I/O): xdpi: 160.15764 ydpi: 160.0 Lenovo ThinkPad Tablet: xdpi: 160.15764 ydpi: 160.0 HTC Jetstream: xdpi: 150.51852 ydpi: 149.41176 The Galaxy Tab and ThinkPad Tablet report incorrect values, while the Jetstream reports correct values. I don't know why the xdpi and ydpi values are different (unless they *actually* are on they physical display, in which case that makes sense since both values for the Jetstream are close to the correct overall value). Is the value reported by xdpi and ydpi set somewhere by the device manufacturer? Is that why the values are correct on some devices and not on others? Is there going to be any guarantee in the future that these values will always be reported as correct (it would be great if this were a requirement for passing the CTS)? It would be really helpful to be able to reliably query for the actual dpi of a device without having to rely on a database of known device values. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@**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=enhttp://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hac...@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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Google Wallet spam
Bram, I hope there are lots of successes too! The simple answer is to add a filter to send those messages directly to trash and mark as read. That's what I've been doing for the last couple of years. -John Coryat On Friday, May 24, 2013 9:48:45 AM UTC-5, Bram Stolk wrote: Since yesterday I get spammed by Google Wallet. At least a 100 emails a day telling me about a failed credit card check, and telling me not to ship. -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console
I solved this by adding an explicit uses-screens section to the manifest, and setting minsdk to 9 (required because xlargescreens is not supported in 8). supports-screens android:smallScreens=true android:normalScreens=true android:largeScreens=true android:xlargeScreens=true android:anyDensity=true / I still don't know what Google changed to make this necessary. Julian On Monday, May 20, 2013 9:50:39 AM UTC-7, jjbunn wrote: I uploaded a new APK for one of my apps on Friday. There was no change to the manifest or build settings for the app, but some of my customers using tablets like the Note 10 and Nexus 10 tell me that the new APK is marked as incompatible in the Google Play store, whereas they were happily using the previous version on those devices. In my Android Developer Console, the APK is marked as being compatible with those tablets (in fact it is marked as compatible with over 2000 devices, and incompatible with 0 (zero)). So I am very puzzled what has happened, and would really appreciate some help :-) Here is the Manifest. I build with the Android 2.2 SDK. ?xml version=1.0 encoding=utf-8? manifest xmlns:android=http://schemas.android.com/apk/res/android; package=com.xxx.xxx.xxx android:installLocation=auto android:versionCode=76 android:versionName=5.9.2 uses-permission android:name=android.permission.RECORD_AUDIO/ uses-permission android:name=android.permission.MODIFY_AUDIO_SETTINGS/ uses-permission android:name=android.permission.WRITE_EXTERNAL_STORAGE/ uses-sdk android:minSdkVersion=4/ application android:icon=@drawable/icon android:label=@string/app_name android:theme=@android:style/Theme.NoTitleBar activity android:name=.MyApp android:label=@string/app_name intent-filter action android:name=android.intent.action.MAIN / category android:name=android.intent.category.LAUNCHER / /intent-filter /activity /application /manifest -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Google Wallet spam
They changed the sender field of cancelled messages, so if you were filtering on that then suddenly you're not. Pent -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: DisplayMetrics xdpi and ydpi returning incorrect values
Yeah, I noticed the density in the API docs and thought so right after I posted the question here, sorry :-) But isn't the density or densityDpi value defined also by the Device vendor? If so It just seems to me a bit odd why the vendor is not defining also correct value for the x/ydpi when they manage it for the other fields. Does that mean the the density and densityDpi fields are more likely to be correct because they are not so precise (ie. just fit the density range group)? I'm just curious... Anyway thanks a lot for your clarification! I'll use the density(Dpi) field so my resolution result should be on par with the native UI. Should be good enough. Best regards, Rick On Friday, 24 May 2013 17:34:40 UTC+2, Romain Guy (Google) wrote: The UI doesn't use these values. We use the density field instead so that the conversion factor is the same on both axis. On May 24, 2013 2:56 AM, Rick rsm...@gmail.com javascript: wrote: I was just being hti by this problem as I'm working on my own UI engine and I need to calculate my own device indepentent unit ratio using these XDPI and YDPI values So how the Android native UI is calculating the DP (independent device unit) on a device where the DPI is incorrectly set? Does tha mean the native UI is then wrongly scaled as well? Thanks for any usful information. Rick On Tuesday, 25 October 2011 22:27:04 UTC+2, Dianne Hackborn wrote: Sorry you just can't use them. Nothing in the platform makes use of them. They need to be set by the manufacturer (there is no way for the platform to know what they are), and as of today they are just not consistently set correctly across devices, and because nothing in the platform relies on them it is easy for devices to have them set incorrectly. This information is just not available, sorry to say. Why do you need the actual physical dpi? On Tue, Oct 25, 2011 at 12:44 PM, ashughes ashu...@gmail.com wrote: The values reported by xdpi and ydpi are still incorrect on some devices. Samsung Galaxy Tab 10.1 (from Google I/O): xdpi: 160.15764 ydpi: 160.0 Lenovo ThinkPad Tablet: xdpi: 160.15764 ydpi: 160.0 HTC Jetstream: xdpi: 150.51852 ydpi: 149.41176 The Galaxy Tab and ThinkPad Tablet report incorrect values, while the Jetstream reports correct values. I don't know why the xdpi and ydpi values are different (unless they *actually* are on they physical display, in which case that makes sense since both values for the Jetstream are close to the correct overall value). Is the value reported by xdpi and ydpi set somewhere by the device manufacturer? Is that why the values are correct on some devices and not on others? Is there going to be any guarantee in the future that these values will always be reported as correct (it would be great if this were a requirement for passing the CTS)? It would be really helpful to be able to reliably query for the actual dpi of a device without having to rely on a database of known device values. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@**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=enhttp://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hac...@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-d...@googlegroups.comjavascript: To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com javascript: 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To
Re: [android-developers] Re: DisplayMetrics xdpi and ydpi returning incorrect values
The density is a bucket. Typically the buckets will be 160dpi (density=1.0), 240dpi (1.5) and 320dpi (2.0). It does not match the physical density of the display exactly but it's close enough to work and make everybody's life easier. The density field is guaranteed to always be correct. On Fri, May 24, 2013 at 10:59 AM, Rick rsmo...@gmail.com wrote: Yeah, I noticed the density in the API docs and thought so right after I posted the question here, sorry :-) But isn't the density or densityDpi value defined also by the Device vendor? If so It just seems to me a bit odd why the vendor is not defining also correct value for the x/ydpi when they manage it for the other fields. Does that mean the the density and densityDpi fields are more likely to be correct because they are not so precise (ie. just fit the density range group)? I'm just curious... Anyway thanks a lot for your clarification! I'll use the density(Dpi) field so my resolution result should be on par with the native UI. Should be good enough. Best regards, Rick On Friday, 24 May 2013 17:34:40 UTC+2, Romain Guy (Google) wrote: The UI doesn't use these values. We use the density field instead so that the conversion factor is the same on both axis. On May 24, 2013 2:56 AM, Rick rsm...@gmail.com wrote: I was just being hti by this problem as I'm working on my own UI engine and I need to calculate my own device indepentent unit ratio using these XDPI and YDPI values So how the Android native UI is calculating the DP (independent device unit) on a device where the DPI is incorrectly set? Does tha mean the native UI is then wrongly scaled as well? Thanks for any usful information. Rick On Tuesday, 25 October 2011 22:27:04 UTC+2, Dianne Hackborn wrote: Sorry you just can't use them. Nothing in the platform makes use of them. They need to be set by the manufacturer (there is no way for the platform to know what they are), and as of today they are just not consistently set correctly across devices, and because nothing in the platform relies on them it is easy for devices to have them set incorrectly. This information is just not available, sorry to say. Why do you need the actual physical dpi? On Tue, Oct 25, 2011 at 12:44 PM, ashughes ashu...@gmail.com wrote: The values reported by xdpi and ydpi are still incorrect on some devices. Samsung Galaxy Tab 10.1 (from Google I/O): xdpi: 160.15764 ydpi: 160.0 Lenovo ThinkPad Tablet: xdpi: 160.15764 ydpi: 160.0 HTC Jetstream: xdpi: 150.51852 ydpi: 149.41176 The Galaxy Tab and ThinkPad Tablet report incorrect values, while the Jetstream reports correct values. I don't know why the xdpi and ydpi values are different (unless they *actually* are on they physical display, in which case that makes sense since both values for the Jetstream are close to the correct overall value). Is the value reported by xdpi and ydpi set somewhere by the device manufacturer? Is that why the values are correct on some devices and not on others? Is there going to be any guarantee in the future that these values will always be reported as correct (it would be great if this were a requirement for passing the CTS)? It would be really helpful to be able to reliably query for the actual dpi of a device without having to rely on a database of known device values. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@**googlegroups.com To unsubscribe from this group, send email to android-developers+**unsubscribe**@googlegroups.com For more options, visit this group at http://groups.google.com/**group**/android-developers?hl=enhttp://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hac...@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-d...@**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=enhttp://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+**unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- -- You received this message because you are subscribed to the Google Groups
Re: [android-developers] Re: DisplayMetrics xdpi and ydpi returning incorrect values
I for one have to say though that it's a shame [xy]dpi are not guaranteed to be correct. We are sometimes balancing our UI element sizes within rather narrow limits and if we need something to be 9mm across it'd better turn out that way - 11mm might look crammed or even collide with something else and 7mm cannot be reliably hit by an average human. I mean, being off by 15-20% as it can happen with the buckets is not always good enough... On Fri, May 24, 2013 at 8:28 PM, Romain Guy romain...@android.com wrote: The density is a bucket. Typically the buckets will be 160dpi (density=1.0), 240dpi (1.5) and 320dpi (2.0). It does not match the physical density of the display exactly but it's close enough to work and make everybody's life easier. The density field is guaranteed to always be correct. On Fri, May 24, 2013 at 10:59 AM, Rick rsmo...@gmail.com wrote: Yeah, I noticed the density in the API docs and thought so right after I posted the question here, sorry :-) But isn't the density or densityDpi value defined also by the Device vendor? If so It just seems to me a bit odd why the vendor is not defining also correct value for the x/ydpi when they manage it for the other fields. Does that mean the the density and densityDpi fields are more likely to be correct because they are not so precise (ie. just fit the density range group)? I'm just curious... Anyway thanks a lot for your clarification! I'll use the density(Dpi) field so my resolution result should be on par with the native UI. Should be good enough. Best regards, Rick On Friday, 24 May 2013 17:34:40 UTC+2, Romain Guy (Google) wrote: The UI doesn't use these values. We use the density field instead so that the conversion factor is the same on both axis. On May 24, 2013 2:56 AM, Rick rsm...@gmail.com wrote: I was just being hti by this problem as I'm working on my own UI engine and I need to calculate my own device indepentent unit ratio using these XDPI and YDPI values So how the Android native UI is calculating the DP (independent device unit) on a device where the DPI is incorrectly set? Does tha mean the native UI is then wrongly scaled as well? Thanks for any usful information. Rick On Tuesday, 25 October 2011 22:27:04 UTC+2, Dianne Hackborn wrote: Sorry you just can't use them. Nothing in the platform makes use of them. They need to be set by the manufacturer (there is no way for the platform to know what they are), and as of today they are just not consistently set correctly across devices, and because nothing in the platform relies on them it is easy for devices to have them set incorrectly. This information is just not available, sorry to say. Why do you need the actual physical dpi? On Tue, Oct 25, 2011 at 12:44 PM, ashughes ashu...@gmail.com wrote: The values reported by xdpi and ydpi are still incorrect on some devices. Samsung Galaxy Tab 10.1 (from Google I/O): xdpi: 160.15764 ydpi: 160.0 Lenovo ThinkPad Tablet: xdpi: 160.15764 ydpi: 160.0 HTC Jetstream: xdpi: 150.51852 ydpi: 149.41176 The Galaxy Tab and ThinkPad Tablet report incorrect values, while the Jetstream reports correct values. I don't know why the xdpi and ydpi values are different (unless they *actually* are on they physical display, in which case that makes sense since both values for the Jetstream are close to the correct overall value). Is the value reported by xdpi and ydpi set somewhere by the device manufacturer? Is that why the values are correct on some devices and not on others? Is there going to be any guarantee in the future that these values will always be reported as correct (it would be great if this were a requirement for passing the CTS)? It would be really helpful to be able to reliably query for the actual dpi of a device without having to rely on a database of known device values. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@**googlegroups.com To unsubscribe from this group, send email to android-developers+**unsubscribe**@googlegroups.com For more options, visit this group at http://groups.google.com/**group**/android-developers?hl=enhttp://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hac...@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-d...@**googlegroups.com To unsubscribe from this group, send email to android-developers+**unsubscr...@googlegroups.com For more options, visit this group at
[android-developers] Re: Google Wallet spam
Ah bingo! Thanks, I was indeed filtering on 'nore...@checkout.google.com' which suddenly got changed into 'nore...@wallet.google.com' Bram On Friday, May 24, 2013 10:36:19 AM UTC-7, Pent wrote: They changed the sender field of cancelled messages, so if you were filtering on that then suddenly you're not. Pent -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] [Android Studio]How to add library to my project
Hello anyone can give some tutorial How to add library to my project on Android Studio.. it's will be nice if i can have some video tutorial.. i follow tutorial from here.. http://stackoverflow.com/questions/16588064/how-do-i-add-a-library-project-to-the-android-studio?lq=1 but still not working.. :( -- -- 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
