[android-developers] Re: Geofence not working over 3G/WiFi in Android 4.4+(KitKat) versions

2014-08-09 Thread dashman
There are some serious problems with the Google Play geofencing api.

Most notably - not detecting fence transitions.

Wrote my own.



On Tuesday, July 29, 2014 2:10:08 AM UTC-4, Abhishek Kumar Gupta wrote:

 In Android 4.4+ versions, I am not able to add/remove geofence over 
 3G/WiFi. Every time I am getting 1000 as a status code which means error. 
 When I am enabling GPS(it doesn't matter whether GPS is fixed or not), 
 everything works fine but accompanied with the problem of battery drain.

 Is there any alternative solutions? If yes, then please guide me.

 Note: In Android 4.3 and below versions, every thing works perfect.


-- 
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/d/optout.


[android-developers] Re: Geofence not working over 3G/WiFi in Android 4.4+(KitKat) versions

2014-08-09 Thread Pent


 There are some serious problems with the Google Play geofencing api.

 Most notably - not detecting fence transitions.

 Wrote my own.


Havn't used geofencing, but it was the same with location manager area 
trigger back in 2009
coincidentally (want reliability, write own).

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/d/optout.


[android-developers] DefaultHttpClient / AndroidHttpClient - Multiple Cookie Headers

2014-08-09 Thread Gaurav Vaish
Hi,

I noticed that DefaultHttpClient as well as AndroidHttpClient do not work 
nicely if multiple Cookie or Cookie2 headers are set in a request.

I tried with a simple test code:
 
String url = http://www.myserver.com;;
DefaultHttpClient dhc = new DefaultHttpClient();
HttpParams hparams = dhc.getParams();
hparams.setParameter(CookieSpecPNames.SINGLE_COOKIE_HEADER, true);

HttpGet req =new HttpGet(url);

req.addHeader(Cookie, A=B);
req.addHeader(Cookie, C=D);
req.addHeader(User-Agent, AndroidExp/ApacheHttpClient);

try {
HttpResponse response = dhc.execute(req);
message = (response == null) ? No response : (Status -  + 
response.getStatusLine().getStatusCode());
} catch(Exception e) {
message = e.getClass().getName() +  =  + e.getMessage();
e.printStackTrace();
} catch(RuntimeException e) {
message = e.getClass().getName() +  =  + e.getMessage();
e.printStackTrace();
}


And then monitored via Charles Proxy. The request being created is as 
follows:

GET / HTTP/1.1
Cookie: A=B
Cookie: C=D
User-Agent: AndroidExp/ApacheHttpClientTask

As per HTTP spec, there can be only one Cookie header.
The same happens with AndroidHttpClient as well.

Do I have a wrong config or did I just find a bug in the code?

Any pointers will be useful.

- Gaurav
www.m10v.com


-- 
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/d/optout.


[android-developers] Re: DefaultHttpClient / AndroidHttpClient - Multiple Cookie Headers

2014-08-09 Thread Jonathan S
I see you add two Cookie Headers.

On Saturday, August 9, 2014 3:08:32 PM UTC-4, Gaurav Vaish wrote:

 Hi,

 I noticed that DefaultHttpClient as well as AndroidHttpClient do not work 
 nicely if multiple Cookie or Cookie2 headers are set in a request.

 I tried with a simple test code:
  
 String url = http://www.myserver.com;;
 DefaultHttpClient dhc = new DefaultHttpClient();
 HttpParams hparams = dhc.getParams();
 hparams.setParameter(CookieSpecPNames.SINGLE_COOKIE_HEADER, true);

 HttpGet req =new HttpGet(url);

 req.addHeader(Cookie, A=B);
 req.addHeader(Cookie, C=D);
 req.addHeader(User-Agent, AndroidExp/ApacheHttpClient);

 try {
 HttpResponse response = dhc.execute(req);
 message = (response == null) ? No response : (Status -  + 
 response.getStatusLine().getStatusCode());
 } catch(Exception e) {
 message = e.getClass().getName() +  =  + e.getMessage();
 e.printStackTrace();
 } catch(RuntimeException e) {
 message = e.getClass().getName() +  =  + e.getMessage();
 e.printStackTrace();
 }


 And then monitored via Charles Proxy. The request being created is as 
 follows:

 GET / HTTP/1.1
 Cookie: A=B
 Cookie: C=D
 User-Agent: AndroidExp/ApacheHttpClientTask

 As per HTTP spec, there can be only one Cookie header.
 The same happens with AndroidHttpClient as well.

 Do I have a wrong config or did I just find a bug in the code?

 Any pointers will be useful.

 - Gaurav
 www.m10v.com




-- 
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/d/optout.


Re: [android-developers] DefaultHttpClient / AndroidHttpClient - Multiple Cookie Headers

2014-08-09 Thread Michael Banzon
You don't set a cookie - you set a header. Twice.

It's the expected result...


On Sat, Aug 9, 2014 at 9:08 PM, Gaurav Vaish gaurav.va...@gmail.com wrote:

 Hi,

 I noticed that DefaultHttpClient as well as AndroidHttpClient do not work
 nicely if multiple Cookie or Cookie2 headers are set in a request.

 I tried with a simple test code:

 String url = http://www.myserver.com;;
 DefaultHttpClient dhc = new DefaultHttpClient();
 HttpParams hparams = dhc.getParams();
 hparams.setParameter(CookieSpecPNames.SINGLE_COOKIE_HEADER, true);

 HttpGet req =new HttpGet(url);

 req.addHeader(Cookie, A=B);
 req.addHeader(Cookie, C=D);
 req.addHeader(User-Agent, AndroidExp/ApacheHttpClient);

 try {
 HttpResponse response = dhc.execute(req);
 message = (response == null) ? No response : (Status -  +
 response.getStatusLine().getStatusCode());
 } catch(Exception e) {
 message = e.getClass().getName() +  =  + e.getMessage();
 e.printStackTrace();
 } catch(RuntimeException e) {
 message = e.getClass().getName() +  =  + e.getMessage();
 e.printStackTrace();
 }


 And then monitored via Charles Proxy. The request being created is as
 follows:

 GET / HTTP/1.1
 Cookie: A=B
 Cookie: C=D
 User-Agent: AndroidExp/ApacheHttpClientTask

 As per HTTP spec, there can be only one Cookie header.
 The same happens with AndroidHttpClient as well.

 Do I have a wrong config or did I just find a bug in the code?

 Any pointers will be useful.

 - Gaurav
 www.m10v.com


  --
 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/d/optout.




-- 
Michael Banzon
http://michaelbanzon.com/

-- 
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/d/optout.


[android-developers] Exception when starting activity: android.os.TransactionTooLargeException

2014-08-09 Thread luca
Hi,

i launched my app and it crashed with the following exception stack trace:


E/JavaBinder(314): !!! FAILED BINDER TRANSACTION !!!
W/ActivityManager(314): Exception when starting activity SplashScreen
W/ActivityManager(314): android.os.TransactionTooLargeException
W/ActivityManager(314): at android.os.BinderProxy.transact(Native Method)
W/ActivityManager(314): at 
android.app.ApplicationThreadProxy.scheduleLaunchActivity(ApplicationThreadNative.java:660)
W/ActivityManager(314): at 
com.android.server.am.ActivityStack.realStartActivityLocked(ActivityStack.java:673)
W/ActivityManager(314): at 
com.android.server.am.ActivityStack.startSpecificActivityLocked(ActivityStack.java:782)
W/ActivityManager(314): at 
com.android.server.am.ActivityStack.resumeTopActivityLocked(ActivityStack.java:1694)
W/ActivityManager(314): at 
com.android.server.am.ActivityStack.completePauseLocked(ActivityStack.java:1097)
W/ActivityManager(314): at 
com.android.server.am.ActivityStack.activityPaused(ActivityStack.java:1009)
W/ActivityManager(314): at 
com.android.server.am.ActivityManagerService.activityPaused(ActivityManagerService.java:4162)
W/ActivityManager(314): at 
android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:371)
W/ActivityManager(314): at 
com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:1610)
W/ActivityManager(314): at android.os.Binder.execTransact(Binder.java:338)
W/ActivityManager(314): at dalvik.system.NativeStart.run(Native Method)
W/ActivityManager(314): Force removing ActivityRecord{41c93388 
SplashScreen}: app died, no saved state
D/dalvikvm(23535): Late-enabling CheckJNI
I/MusicBrowser(10651): [MediaPlaybackService.java:1266:onReceive()] oo 
{intent=Intent { act=android.intent.action.CONFIGURATION_CHANGED 
flg=0x6010 }}
I/ActivityManager(314): Start proc [...] for activity SplashScreen: 
pid=23535 uid=10107 gids={1015, 3003}

The app is composed of a number of activities, some from third-party sw 
libs (ex: AdActivity of google, facebook login activity an so on). The most 
important ones are
1. splash screen activity (launcher)
2. main app activity

The SplashScreen activity has this intent:

intent-filter
  action android:name=android.intent.action.MAIN /
  category android:name=android.intent.category.LAUNCHER /
/intent-filter

while the main app activity has this:


intent-filter
action android:name=android.intent.action.VIEW /
action android:name=android.intent.action.EDIT /
action android:name=android.intent.action.SEND /
category android:name=android.intent.category.DEFAULT /
data android:mimeType=image/* /
/intent-filter

because it can receive images.

The SplashScreen view is made of a relative layout with an image as a 
drawable and three textview that each show some text (version, app name and 
so on).
The drawable is a .png file of 960x640 (xhdpi).

I launched the app touching the icon (not by sharing an image with it: in 
that case only the main app would be started and not the splash screen 
activity) and it crashed. 
I have absolutely no idea of what happened, but it seems to me that the 
splash screen activity did not start at all.
Any idea?

-- 
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/d/optout.


Re: [android-developers] Shape with a pattern fill

2014-08-09 Thread Peter Teoh
http://stackoverflow.com/questions/1700099/android-how-to-create-a-background-from-pattern


On Tue, Jul 29, 2014 at 5:47 AM, dashman erjdri...@gmail.com wrote:

 Is it possible to create a shape with a pattern fill - instead of a solid
 color.


  --
 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/d/optout.




-- 
Regards,
Peter Teoh

-- 
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/d/optout.


Re: [android-developers] DefaultHttpClient / AndroidHttpClient - Multiple Cookie Headers

2014-08-09 Thread Gaurav Vaish
There is no other way to add cookie, isn't it?

Or do you mean it is my responsibility to format / combine all cookies?

What's the purpose of CookieSpecPNames.SINGLE_COOKIE_HEADER parameter then?
How do I use that?

- Gaurav

On Saturday, 9 August 2014 12:38:00 UTC-7, mbanzon wrote:

 You don't set a cookie - you set a header. Twice.

 It's the expected result...


 On Sat, Aug 9, 2014 at 9:08 PM, Gaurav Vaish gaurav...@gmail.com 
 javascript: wrote:

 Hi,

 I noticed that DefaultHttpClient as well as AndroidHttpClient do not work 
 nicely if multiple Cookie or Cookie2 headers are set in a request.

 I tried with a simple test code:
  
 String url = http://www.myserver.com;;
 DefaultHttpClient dhc = new DefaultHttpClient();
 HttpParams hparams = dhc.getParams();
 hparams.setParameter(CookieSpecPNames.SINGLE_COOKIE_HEADER, true
 );

 HttpGet req =new HttpGet(url);

 req.addHeader(Cookie, A=B);
 req.addHeader(Cookie, C=D);
 req.addHeader(User-Agent, AndroidExp/ApacheHttpClient);

 try {
 HttpResponse response = dhc.execute(req);
 message = (response == null) ? No response : (Status -  
 + response.getStatusLine().getStatusCode());
 } catch(Exception e) {
 message = e.getClass().getName() +  =  + e.getMessage();
 e.printStackTrace();
 } catch(RuntimeException e) {
 message = e.getClass().getName() +  =  + e.getMessage();
 e.printStackTrace();
 }


 And then monitored via Charles Proxy. The request being created is as 
 follows:

 GET / HTTP/1.1
 Cookie: A=B
 Cookie: C=D
 User-Agent: AndroidExp/ApacheHttpClientTask

 As per HTTP spec, there can be only one Cookie header.
 The same happens with AndroidHttpClient as well.

 Do I have a wrong config or did I just find a bug in the code?

 Any pointers will be useful.

 - Gaurav
 www.m10v.com


  -- 
 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 
 javascript:
 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/d/optout.




 -- 
 Michael Banzon
 http://michaelbanzon.com/ 


-- 
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/d/optout.