Android Enthusiasts

8:37 AM

@Firelord you're right, repeated caller is since Android 6

and I was reminded by your question about pm hide vs pm disable when reading your comment on Dan's answer.

2 hours later…

10:54 AM

@AndrewT. What do you recommend? Should the question be tagged with correct version or marked unclear?

@Firelord I'd say edit it. Android 5.x doesn't have that feature. The steps OP mentioned also confirmed Android 6.

wait, let me research again

So it seems Asus has "repeated calls" feature on Lollipop. Okay, now it seems unclear.

I think we should remain on safe side and close the question. If OP ever returns and the question is not deleted automatically but that time, they can provide necessary details.

I'm not sure how closing the question is safe

Well, how would one proceed to answer, tell me?

@AndrewT. LOL, I already retracted my vote.

another problem is... OP is unregistered and last seen on that day he posted the question (Oct 2015). Not sure they will notice and come back...

11:11 AM

I can't close vote now, so there isn't much left for me to do. Silly me, I acted too fast.

Sorry, my bad. I acted too slow.

At least it would now show up in Close votes queue to rest of the close voters. Thanks!

1 hour later…

12:38 PM

@Firelord I have no idea how to answer, but that's not grounds for closure. If I had seen the same problem on another phone, I could answer with whatever fixed it for me, even though the question's not entirely specific.

spam answer time: android.stackexchange.com/a/137525/12442

@DanHulme I think the ground of closure is that there are not many phones running Android 5.0 with repeated call future and since the device name is not mentioned it would not be good to just assume that it would be this device or that device. Lack of detail I suppose is good ground for closure.

Bo Lawson

12:52 PM

I went on adventure through Google Android source. Started at CM12.1 git but it was evident that it was not caused by something they did. On to Android's git which sadly confirmed my suspicions that the API is the cause of your problem.

I collected a lot of reference links through out my adventure. The history path for the API appears to make my case of the cause being the framework itself:
https://android.googlesource.com/platform/frameworks/base/+log/24b9c83/api

Kitkat to Lollipop was the biggest change android did. Somethings did not transition smoothly causing things to break, creatin…

@Firelord I think "unclear what you're asking" only applies if the question is so lacking in detail that nobody could possibly write a useful answer. If the problem's described well enough that somebody who has seen the same problem would recognise it from the description, or a developer could work out what was intended, I wouldn't close in that case (but I might downvote if it "is unclear or not useful").

1:19 PM

@BoLawson Is this about that appops command I asked? I don't think I understand this comment with regard to that answer. If the implementation of appops command is faulty in Android 5.0.x and you've a bug report of it, then I would say it would suffice as an answer.

The status should show that there indeed was a bug and not just mere hypothesis from bug reporter.

2:02 PM

hey, the mod room has disappeared

so much for being able to get access to mods :-(

@Izzy Can you as a mod access that help desk? We mortals can't do anything from here.

Bo Lawson

2:41 PM

@Firelord Yep the AppOps command that's the one. I was looking more at the commit to merge the needed API'S to resolve the issue. Commits shows the issue and a way to fix it proof of concept. The actions taken by Diane Hackborn in regards to the Permission's and the SYSTEM_ALERT_WINDOW STRING (she is a top engineer for android framework and an actual employee) her acknowledgement is Android acknowledgement. History was just the shortest way to explain that had proof of concept. I have many more links I can resource ;). One of which is a post from Diane Hackborn explaining some of the issue …

3:02 PM

@BoLawson I don't think I'm following all of this. If you've something concrete that directly implies that the implementation of that command is faulty in my Android version, let me know. Thanks!

3 hours later…

6:22 PM

It's the fourth day that I ran out of votes (up/down) again.

Does anyone honestly feels that we should have more moderators active on this site? Only two of them actually seems to be handling flags and their timing (that is when they come online) doesn't seem to cover maximum part of 24 hours (a full solar cycle).
I'm asking this because if more moderators from different time zones are active, my flags would *possibly* get cleared early and I would be able to vote again without having to wait for next day.

Devrim

7:05 PM

hi people.. anyone out there who can help with adb/fastboot

no.. okay

1 hour later…

Bo Lawson

8:29 PM

@Firelord I think the easiest and most convincing concrete evidence would be to verify the string is presence in your Android.Manifest.xml yourself.
Where should I post the instructions here or comments section of your post?