Cover photo
Paresh Mayani
3,199 followers|976,130 views


[Interesting observation/issue - Lint reports]

During the discussion with my colleague +Ketan Parmar in the office, we have observed an interesting issue in the Gradle and Android studio

1) If you run gradle clean build from terminal, it generates lint reports (even if lint options in build.gradle are not configured).

2) If you do clean project and make project in android studio then it's not generating lint reports (even tried after configuring lint options in the build.gradle file).

Observation is if you run the gradle clean build command from terminal, it executes :app:lint as a subtask and hence it's generating lint reports. But the same task is not getting executed when we clean and make project in Android studio.

For more details =>

One more issue has been founded successfully :-)
Android Open Source Project - Issue Tracker
Ketan Parmar's profile photoJimmy Leonardo's profile photo

Paresh Mayani

Shared publicly  - 
I think I have to buy a super computer or a laptop with as much as RAM as HD to work with Android Studio and Gradle!

I have already included a with suggested points:

org.gradle.jvmargs=-Xmx1024m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8


Attached is the proof of the culprits responsible this crime and these 3 are not happy with my system (i5, windows 8.1, 4 GB RAM) and I am all like..#F***Pushing
sergej shafarenka's profile photoKiran Rao's profile photoParesh Mayani's profile photoSowmya Guru's profile photo
I use 4GB ram with Firefox. :-/ (Obviously, not chrome!) and Ubuntu 14.04 for work. Works like a charm. 

Paresh Mayani

Shared publicly  - 
Interesting article with good tips for Effective Session Submission.

Via +Romin Irani 
Useful tips on submitting conference proposals from Arun Gupta.
This blog will show do's and don'ts for an effective session submission at a conference.
View original post

Paresh Mayani

Shared publicly  - 
Looks like a library for the lazy Android developer :-)


Via +Paul Lammertsma
Tired of writing the same code over and over again? We made a library you'll like! #100DevTips
View original post
Gabor Orosz's profile photoVladimir Bjelakovic's profile photo

Paresh Mayani

Shared publicly  - 
#androidDev, Interesting JSON library , which focuses on performance 
LoganSquare - Screaming fast JSON parsing and serialization library for Android.
View original post
Faiz Malkani's profile photomanas shukla's profile photoNayanesh Gupte's profile photoParthiv Shah's profile photo
+Nayanesh Gupte ha ha ha that's not a bad idea :P
Have him in circles
3,199 people
Nile Hadwards's profile photo
yatendrasinh joddha's profile photo
Zoe Lloyd's profile photo
Dan Romescu's profile photo
Amrit Sanjeev's profile photo
Jd Geier's profile photo
Sandip Patel's profile photo
Krishnamoha Gupta's profile photo
Coulibaly Adama's profile photo

Paresh Mayani

Shared publicly  - 
[Part 10 – The Hitchhiker’s guide to Android Testing]

This part in lazy android developers series is completely written by +Wiebe Elsinga and +Ali Derbane, with love towards #AndroidDev  community.

In this part, they have explored about android testing and tools:
1. JUnit
2. Hamcrest
3. Robotium
4. Calabash
5. Espresso
6. Selendroid
7. Robolectric

Thank you Wiebe and Ali for sharing your knowledge with us.
Writing tests gives you a good understanding about the stability, quality and performance of an application. There are multiple android testing tools.
David Sanders's profile photoScott Olcott's profile photoJulien Banse's profile photoSuhatt Jantorn's profile photo
published in

Paresh Mayani

Shared publicly  - 
This is one of the superb initiative taken by +Google Malaysia. Congratulations +Amit Chopra and Kudos to the SEA DevRel team.

Looking forward and I am sure the same initiative will be taken by +Google India DevRel team. CC: +Sunil Rao, +Amrit Sanjeev, +Avik Debnath
Are you a professional Android developer? We'd love to see you at the Google Developers Summit KL this March 19.

The summit will be a day long event and speakers are flying in from US, Singapore, Tokyo and Sydney. This event will be geared towards professional Android developers, so you must have a published app on Google Play. 

Topics include: 
- Core Android Development,
- Material Design (including a workshop), 
- Google Play Best Practices, 
- New Android APIs, 
- Google Cloud Platform.

Register here: 
2 comments on original post
Facing an issue while creating android wear emulator => The skin directory does not point to a valid skin.

Anyone have faced this issue earlier or any pointer?
Jhon Miller Barrera's profile photo
Announcing a new and interesting series on soon, authored by +Harsh Dattani​, who is exploring the horizon of cyber security. #StayTuned

And two more awesome experts +Wiebe Elsinga​ and +Ali Derbane​ are writing an article for the lazy android developers series. Awesome article is awaited!

Yeah after 4 years, TechnoTalkative, my blog is gone multi-authored :-) #Happy
Romin Irani's profile photoVladimir Bjelakovic's profile photo
Looking forward to high quality articles as always on your blog.

Paresh Mayani

Shared publicly  - 
#AndroidDev => [Interesting observation: Gradle + Android Studio]

compile ''

If you want to access the APIs and features of google play service, you have to mention the artifact of the google play service in the build.gradle file.

Now, the actual picture comes into the picture, if you haven't downloaded "Google repository" from the 'extras' section in the SDK manager then it won't be able to use the features of google play service library but it gives below error[1] while building the project.

Yes, we assume gradle downloads .pom file of the particular library from the maven central or jcenter repository, but it seems it doesn't download the play service pom file actually!

P.S. I got to know about this when I was trying to build the projects on console in my laptop, which was actually having plain android sdk folder.

[1] Error:

$ gradle clean

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> A problem occurred configuring project ':myExampleLibrary'.
   > Could not resolve all dependencies for configuration ':myExampleLibrary:_debugCompile'.
      > Could not find
        Searched in the following locations:
        Required by:

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.


Total time: 17.841 secs
Stefan Hoth's profile photoSaid Tahsin Dane's profile photoParesh Mayani's profile photoGabor Orosz's profile photo
+Said Tahsin Dane Seriously It should give proper message with action buttons (whether user wants to update or cancel) rather than updating it silently! Otherwise user would not come to know what was the issue exactly.

Paresh Mayani

Shared publicly  - 
Looks like API level 22 is coming soon
Android Open Source Project - Issue Tracker
View original post
Have him in circles
3,199 people
Nile Hadwards's profile photo
yatendrasinh joddha's profile photo
Zoe Lloyd's profile photo
Dan Romescu's profile photo
Amrit Sanjeev's profile photo
Jd Geier's profile photo
Sandip Patel's profile photo
Krishnamoha Gupta's profile photo
Coulibaly Adama's profile photo
Senior Software Engineer
Android, Java, WordPress
Software Engineer, Lazy Android developer, Founder/Organizer @ Google Developers Group Ahmedabad
Basic Information