Questions Thread - May 19, 2016

Questions Thread - May 19, 2016


Questions Thread - May 19, 2016

Posted: 19 May 2016 05:05 AM PDT

This thread is for simple questions that don't warrant their own thread (although we suggest checking the sidebar, the wiki, or Stack Overflow before posting). Examples of questions:

  • How do I pass data between my Activities?
  • Does anyone have a link to the source for the AOSP messaging app?
  • Is it possible to programmatically change the color of the status bar without targeting API 21?

Important: Downvotes are strongly discouraged in this thread. Sorting by new is strongly encouraged.

Large code snippets don't read well on reddit and take up a lot of space, so please don't paste them in your comments. Consider linking Gists instead.

Have a question about the subreddit or otherwise for /r/androiddev mods? We welcome your mod mail!

Looking for all the Questions threads? Want an easy way to locate today's thread? Click this link!

submitted by /u/AutoModerator
[link] [comments]

Google I/O 2016 Day 2 Thread

Posted: 19 May 2016 07:31 AM PDT

To keep the front page from getting overrun with posts, we're going to go with daily megathreads for I/O discussion.

As always, being a jerk is still not allowed.

Cheers,

Da Mods

submitted by /u/burntcookie90
[link] [comments]

The Infinite Loop of Misery that is Play Store Suspensions

Posted: 19 May 2016 10:15 AM PDT

Short Version: Had an app suspended because Google thought my title was infringing a brand name while it was just a Noun. Explaining the difference(the word is not English), led nowhere and the suspension still stands. Long Version: I had a nearly three year old app called Seithigal, I created a new app recently that would unify my other news apps and upon release I updated Seithigal to display a message on startup to indicate it is being archived and gave an option to the users to visit the play store to install the new app. I updated the title in the play store to indicate it is being archived, and added the information in description(I don't have a screenshot of it because it is suspended but it was just a few lines saying why it is being archived and a link to my new app) only to wake up the next day with the dreaded suspension email waiting for me. As usual, there was no reason cited just that it violates impersonation policy, which just robs any chance of making a meaningful argument in the one chance you get to make your case.

I tried to explain all the changes I made, from title to description and explained that this app is being archived and given there is a thousand character limit that is pretty much all I could guess of their intentions to explain it to them. I got a reply next day. I just couldn't believe their reason, it was so surreal to the point if they hadn't told me that I would have never guessed it. The name that they thought was infringing the copyright of this news channel(based on a three line Wikipedia article rather than the channel's homepage or something) is a Noun. Seithigal just means News, it's not an obscure word either, It is the word for News. I tried my best to explain this with my reply hoping this was just a misunderstanding and everything would be cleared up soon. Just a few minutes after sending that e-mail I found what I thought was definitive proof that would clear this thing up once and for all, I sent that as well.

I got a bewildering reply back that basically amounted to nothing, but they did indicate this is the only problem they have, and when I pressed on, I just got a case is closed and need your feedback email. I replied again as suggested in the e-mail and waited over the weekend and for four business days and there has been no other communication from the side of Google.

I cannot describe just how frustrating this whole thing has been, Apart from the anemic support system, the fact that it was suspended and not rejected in the first place is crazy especially since every suspension counts against your standing(which is opaque), and getting your account terminated pretty much means the end of things. I understand the need to monitor copyright infringements, and I even understand that there are sometimes false positives like my case, but a rejection with a chance to explain or even correct their mistake(if any) would be a far better option than the current nightmare and the play store desperately needs a proper grievance readdressal mechanism with escalation options.

Links in my e-mail: https://en.wikipedia.org/wiki/Seithigal

https://translate.google.co.in/#ta/en/seithigal

http://streema.com/tv/Kalaignar_Seithigal

https://www.google.co.in/search?q=Kalaignar+seithigal

https://www.google.co.in/search?q=%E0%AE%9A%E0%AF%86%E0%AE%AF%E0%AF%8D%E0%AE%A4%E0%AE%BF%E0%AE%95%E0%AE%B3%E0%AF%8D

https://play.google.com/store/search?q=seithigal&hl=en

submitted by /u/siddware
[link] [comments]

What are some not so obvious things a new Android Developer should learn?

Posted: 19 May 2016 09:40 PM PDT

In my journey of learning Android I have been shocked to see how many things are common knowledge/use to the average programmer but are not specified in pretty much any tutorials like:

  • RXJava/Android
  • RetroFit
  • POST/GET
  • JSON/GSON
  • Hosting and saving info to a server

Actually almost everything I've learned on networking is through accidental discovery browsing post's on SO.

And to someone who is not in school, it can be frustrating as you literally have 0 knowledge of these things that are basically a necessity. Sure learning RetroFit or RxAndroid may not be that difficult to learn, but they're impossible to learn if you don't know they exist.

What are some basic things someone making an app should know that wouldn't be covered in tutorials?

submitted by /u/kaio37k
[link] [comments]

What are 5 things you wish you had know before developing your first app?

Posted: 19 May 2016 08:42 AM PDT

Just started making my first app to test what i have learnt in the past 2 weeks i have been developing. Im not going to release it unless its better than i expect, but this is sort of a test for me. Its a pretty long process so far and im sure there are ways i can speed it up that will be very simple but i will learn later.

However i was wondering what are 5 things app developers wish they had known before releasing their first app?

I can be useful resources, pieces of advice, tools, inspiration, the harsh truth about what it will be like or anything related.

submitted by /u/MaxoJggwp
[link] [comments]

Why does AppCompat exist?

Posted: 19 May 2016 06:16 PM PDT

More specifically:

  • Why does AppCompat have to re-implement features introduced in newer API versions instead of the Android team implementing the features in support in the first place? (eg elevation, android.support.v7.widget.Toolbar)

  • How is it possible that the AppCompat team can implement features which do not seem possible under old APIs? (eg Fragments)

  • Why are features created for new APIs when they can also be integrated in AppCompat, preventing fragmentation?

submitted by /u/KolakCC
[link] [comments]

The absolute minimum Android developers need to know about UX — Part 3 of 5

Posted: 19 May 2016 07:10 AM PDT

Is anyone else running into this immensely frustrating bug where DAC is served in Vietnamese?

Posted: 19 May 2016 08:31 AM PDT

Details on how those million Android apps will be running the latest version of Android on ChromeOS

Posted: 19 May 2016 08:29 PM PDT

Android N Preview 3 Issues?

Posted: 19 May 2016 10:12 PM PDT

I recently upgraded to the N Preview 3, and noticed that almost every app had improved in terms of performance except for my own. Ever since the update, my app's MediaPlayer keeps killing itself after initialising, with an error 100 code.

Has anyone else noticed any strange goings-on with the new build? Or am I alone?

submitted by /u/pghahaha
[link] [comments]

Mononoki - a font for programming and code review

Posted: 19 May 2016 06:10 AM PDT

Dark Sky Weather App Arrives On Android, Dev Q&A Included

Posted: 19 May 2016 09:40 PM PDT

Bring Your Android App to Chromebooks

Posted: 19 May 2016 11:54 AM PDT

App suspensions; an alternative

Posted: 19 May 2016 07:32 PM PDT

Google needs to reserve the right to suspend apps. Developers need some way to make changes safe in the knowledge that they're not ruining their life.

Google, give people a way to submit proposed changes for approval. Validate the changes and post the outcome directly to developers with the reason for rejection if appropriate.

That's all it would take to turn the current system into something that doesn't utterly destroy the livelihood of some developers who misjudge or mistakenly break the terms of the use.

Google, you'll earn a lot of goodwill from a lot of disenfranchised developers who have paid you for the privilege of developing and listing their apps.

Let's just be pragmatic about the relationship we have as providers here and work together. It's a terrible customer experience to have your app and account blacklisted for life because of one mistake or misunderstanding. It's not like there's no workable solution.

submitted by /u/ess_tee_you
[link] [comments]

PropertyName missing from com.google.firebase:firebase-database:9.0.0. Am I the only one?

Posted: 19 May 2016 10:38 AM PDT

The following annotation: https://firebase.google.com/docs/reference/android/com/google/firebase/database/PropertyName seems to be missing from the sdk com.google.firebase:firebase-database:9.0.0. Am I the only one facing this issue?

submitted by /u/Vinaybn
[link] [comments]

Is anyone thinking of migrating from their Parse back-end to Firebase?

Posted: 19 May 2016 06:48 AM PDT

I am hesitant to do so since Parse made me cautious about back end as a service, but I'm curious what others think.

submitted by /u/pickle_inspector
[link] [comments]

Android Studio 2.2 Preview - New UI Designer & Constraint Layout

Posted: 19 May 2016 10:18 PM PDT

So how do fellow developers feel about background service restrictions?

Posted: 19 May 2016 05:53 AM PDT

In the Android battery and memory talk at the Google IO, they mentioned that sometime after N, they will start restricting background services. If I understood correctly, after change, there will be only two ways to run code in the background:

  • Through the JobScheduler. That is the preferred way, but you can only do some things with it. For example you cannot listen to the sensors in the background, plus JobScheduler is designed to defer tasks as much as possible to save on resources so it is not useful for anything that needs quick reaction.
  • By using foreground service and displaying persistent notification. If user has many apps installed, that could mean a lot of clutter in the notification tray. I realize many apps do this already right now, but for every app that clutters the tray I would say there are many other apps that use services and don't do it. Yes, some of these could be migrated to JobScheduler, but many would be forced to put notification out there.

/r/Android is cheering and I agree that some apps do abuse background services and need policing, but I'm skeptical of this ban everything approach.

What does everybody here think? I know there is thread about this on /r/Android, but I wanted to get some opinions from fellow developers.

Is it reasonable to expect for Google to add some way for user to explicitly allow background operations of specific app without cluttering notification tray?

submitted by /u/matejdro
[link] [comments]

How to send an SMS from Android

Posted: 19 May 2016 01:21 PM PDT

FloppyVideoView, a combination of TextureVideoView and ImageView's scaleType

Posted: 19 May 2016 10:34 AM PDT

So I created a simple VideoView widget with the power of TextureView and the flexibility of ImageView's scaleType, called it FloppyVideoView.

It's of course open source here: https://github.com/eneim/FloppyVideoView

Version 1.0.0 is almost transparent to VideoView and texturevideoview. But I have plan to upgrade it to be more powerful in the future.

Any comment or issue are welcome.

submitted by /u/ene__im
[link] [comments]

Bring Your Android App to Chromebooks

Posted: 19 May 2016 12:42 PM PDT

Has there been any talk from Google about reeling in some of the control they give device manufacturers WRT the SDK?

Posted: 19 May 2016 10:56 AM PDT

I just released a major update to my app and almost instantly I'm getting bug reports from almost exclusively Samsung users with major issues that I never caught during my testing on Nexus devices and emulators.

The fact that we can't even trust the SDK API itself to have a common implementation is so frustrating. I'm sick of having to branch my code to accommodate manufacturers (let's be honest, mostly Samsungs) bullshit.

Has there been any word on what, if anything, Google is doing about this?

submitted by /u/b1ackcat
[link] [comments]

Firebase announcement is one of the most helpful for us developers. But Parse shutting down, kills whole excitement.

Posted: 19 May 2016 02:01 PM PDT

I have developed a couple of hobby projects and demos around firebase and parse, this time was around November last year, and these services were right on the spot for hobby developments which can be expanded to a serious business.

Yesterday, the announcement of Firebase made me excited about them. I can see Customer segments being core feature for many business in near future, on top of which notifications, invites, dynamic links and configs can really be the right tools for business to survive. And with normal google techs, having iOS sdks available will help small teams like us to jump in as quickly as we want to. Last years GCM 3.0 with topic management was received with equal enthusiasm in both mobile teams and web guys at my job.

I see this years Firebase sdks will be equally useful for everyone. But as I have discussed this things today, within my company and within local community, who are familiar with this type of development. I was faced with these concerns-questions regarding to firebase.

  • Firebase may face similar fate as Parse.

  • There will be pain to migrate fully SQL database to a NoSQL one, so Database migration is no chance. But if we chose to go for other goodies, there should be some way to control those things using our db or coding.

  • Some of them thought Firebase is a third party solution, not having Google with it's name. First they don't believe in third party solution, and second what's happening to parse is not helping anybody.

  • If I am not wrong, Normal GCM, Google Analytics, Admob etc will continue to work for longer time. They won't go out in a year or two. So there is no reason to switch.

As a rebuttal

  • Firebase themselves posted 3 months ago that they are not going anywhere, but it's too hard to believe.

  • Google is not Facebook, they care about developers and developer tools more than Facebook, so even if they plan to shut firebase down, it won't happen in a year or two, and they will have a better migration plan and support than Parse's.

  • And for last point I can see that google will push the use of firebase extensively and specially GCM and Analytics will face to fate of C2DM (will be deprecated and shut down eventually).

For me SQL to NoSQL is pretty controversial, and leaving that point aside, what are the other points you can add to keep this discussion on, So we can clear more doubts and can have more people willing to try firebase?

submitted by /u/lordVader1138
[link] [comments]
Thanks for reading my news about Questions Thread - May 19, 2016 at my blog Custom Droid Rom if you want too share this article, please put the resource, and if you think this article is very usefully dont forget to bookmark this site with CTRL + D on your keyboard to web browser.

New and Hot Article's :

Note: only a member of this blog may post a comment.