How do mobile apps know whether you actually performed an action on 3rd party website?

Developing Android Apps - Mon, 08/27/2018 - 13:17

Note: I don't know anything about mobile development so I am not aware of what applications can and cannot do, what generic API's mobile platforms have that would make something like this a piece of cake to do.

Basically, probably everyone came across a game that will give you X gems once you follow the developer on twitter, some more if you like them on facebook, etc etc, trivial stuff.

But how do they know? How do they check that you actually logged in and liked them on facebook? And that it really was you?

How does this "integration" work? Is this something like one with ads? To the point where ANYONE can shove 30 ads up my ass and the only way to get rid of them is to not use it or buy it because it's unusable otherwise?

It would help me if I'd know the name of this action (which is why I am asking here and didn't just google it, I couldn't find anything about this besides it being so widespread that almost every mobile game has this) and general steps on how it's done so I can look into it, because I'd like to integrate it into my next project.

submitted by /u/PurpleIcy
[link] [comments]
Categories: Android, Linux

Accessibility Impact on Performance

Developing Android Apps - Mon, 08/27/2018 - 12:31

I hope this falls within the sub's scope. I feel it's related to Android code, specifically how accessibility is coded and actually works. In the past few months, I've seen a few different viewpoints on how accessibility affects performance, and they seem to contradict each other:

XDA Editor's explanation from this article:

  • Claims performance impact depends on what accessibility events are requested.

  • Events are only monitored if requested.

When all Services are disabled under Settings –> Accessibility, Android does not collect or send any Accessibility Events. But when the user starts enabling Accessibility Services, Android will begin monitoring and collecting only those Accessibility Events that the Accessibility Service requests.

In essence, not every Accessibility Service will cause lag. A single Accessibility Service that requires a high frequency Event may cause lag, especially if said Service is coupled with another Service that requires another high frequency Event to be monitored.

Greenify dev's view from this thread

  • Claims there is performance impact as soon as an app requests accessibility service, due to event monitoring

  • All events are monitored if accessibility service is enabled for even just 1 app

Android delivers accessibility events to active accessibility service in two phases. Events are first generated in the current interacting app and immediately sent to system process, then dispatched to separate accessibility services, each in its own process.

If no accessibility services enabled, both phases are shutdown, thus no performance affection at all. If at least one accessibility service is enabled, the first phase is turned on, in full power, no matter which types of events are interested (declared by accessibility service). The second phase is taking that into consideration and only delivers the interested events to each accessibility service.

The performance lag comes mostly out of the first phase because some types of accessibility events are so heavy, considering how frequently they are triggered.

  • Additionally, says there was some change in Android O and cites this commit.

Although Android O took a step to address that, the situation is still not changed fundamentally. Maybe in Google's view, accessibility service is not intended for general users, so performance optimization is never in the priority.

ElementX and Button Mapper dev from this thread

  • Claims accessibility services has no impact on Android devices with Oreo, and non-Samsung devices on Nougat. Doesn't comment on pre-Nougat.

  • Only one specific permission/event (FilterKeyEvents) causes a performance impact, and it was limited to certain phones

There was a bug in accessibility that caused stuttering if filter keyevents permission was turned on. It was present on HTC and OnePlus phones as well (and maybe others too), but they fixed it with Android 7.1 updates, while Samsung didn't fix it until the Oreo update.

Are they all correct in some way? I'd appreciate any help in better understanding how accessibility works, especially on Oreo devices. There seems to be a lot of speculation out there without hard evidence, mostly just anecdotal. It seems like it should be better understood since Android is open source.

submitted by /u/Citizen_V
[link] [comments]
Categories: Android, Linux

Just a reminder that Spotify still has major issues on Android. E.g. Notification controls disappearing, music randomly stopping and non-functional search.

Android - Mon, 08/27/2018 - 12:28

These issues seems to have been around for a couple of weeks/months. I'm not sure whether they're related but they almost have to be.

Issues include:

  • Notification controls disappearing.

  • Media server (music playback) randomly getting killed (probably because the notification isn't elevating rights anymore).

  • Search showing "Offline" even though the device is very much online.

  • Spotify thinking it's casting to a chromecast (you see the notification) even though playback is actually local and no chromecast is powered on.

  • Chromecast queue not sticking.

  • A mismatch between the song that is actually playing and which song the UI thinks is playing.

  • Share button results in a crash (only on devices that are in the new UI A/B test group).

  • Other issues?

There's a thread about this issue on the Spotify Community Forums. Spotify isn't currently even acknowledging the issue exists. Are you having this issue? Please let your voice be heard in the thread. Also, contact Spotify support.

A temporary fix seems to be killing Spotify. Looking for a more permanent fix? Flashing version armv7 also has some reports to work!

I also posted about this issue on the Spotify subreddit this morning, got about 20 people to contact Spotify through it. Let's create some more traction on this issue through r/Android!

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

Android P Mute Mode

Tasker: Total Automation for Android - Mon, 08/27/2018 - 11:52

How would I trigger the new mute mode? All I'm able to find is how I can set it to vibrate or start Do Not Disturb.

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

Liquid cooling - the worst buzzword of 2018

Android - Mon, 08/27/2018 - 11:22

When you think liquid cooling, you probably think of high end PCs. These systems have tubes, radiators, fans, etc. This year manufacturers have somehow all decided that they will pretend that they’ve managed to miniaturize this and put it into a phone.

Phones do not have liquid cooling systems, they have heat pipes. Yes, heat pipes have a miniscule amount of fluid in them, so in the most technical sense this is liquid cooling, but then all cooling would be liquid cooling as well. This year we’ve seen a focus on larger heat pipes, which is good, don’t get me wrong, but the problem is the marketing divisions, and the review sites which have bought into their bs. Seriously, I get so frustrated when I’m looking at a phone review and I see “liquid cooling system” like NO IT’S NOT!

Earlier in the year I tired to tolerate smaller companies like xiaomi with the black shark. But when samsung, the biggest phone company in the world, did this shady, stupid marketing, that was the breaking point for me. Am I insane for caring about this?

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

I wrote up a small plugin that lets you map scripts/shell commands to a keyboard shortcut

Developing Android Apps - Mon, 08/27/2018 - 10:52

While developing I'd have to run scripts to update a repository or clean gradle cache routinely, thought it'd be easier to have them mapped to a keyboard shortcut.

Here is the link to the Github Project

Here is the link to the plugin

submitted by /u/xotxo
[link] [comments]
Categories: Android, Linux

Help with apktool

Developing Android Apps - Mon, 08/27/2018 - 10:12


I‘m currently trying to make an app that was designed for an minSDkversion of 19 to run on level 18. I decompiled and recompiled it using apktool. But it doesn’t seem to work as i still can’t install the app. I changed the value in the manifest and apktool.yml. Has anyone any idea what else I need to do? Note: I won’t distribute this app or something like that. It’s pure curiosity on getting apps to run on old hardware.


submitted by /u/XxnatsugaxX
[link] [comments]
Categories: Android, Linux