I'm building an Android Launcher for the elderly, using Android Studio, and I'm trying to change how the UI of an ongoing call looks. I want to know if it's even possible.
I know I could do it by building a Custom ROM, but that's not a solution for me. I'm asking here, because I can't find anything online about this. All I could find was this.
I tried reading the last link 5 times now, but I can't figure out what to do. I feel like I'm overcomplicating something very simple. Remember, I don't want to change how calls are made, nor change any routines and listeners. All I want to change is the user interface.
What I want to change:
Default ongoing android call look
Related
Our project is 5 years old project in Android native.In that we have used Asynctask to make an API call in each and every screen.
As per the documentation Asynctask got deprecated from Android 11 onwards. Currently our project is in play store and there are n number of active users.And it's working fine with android 11 devices also without any issues
Here I have 2 queries
1)Still Asynctask is working fine with Android 11 OS and below versions.Will it affect android 12 OS.I haven't get any clear information about completely removal of Asynctask in android developer site also.
Do I need to take this as serious and have to update my whole project with the replacement of Asynctask?And will it affect upcoming OS versions?
2)If I want to replace that means what will be the best option without making much code changes. Even google suggested some API frameworks like concurrent and coroutines as the best replacement.But I didn't get idea about replacing in existing classes.Because in and every class we are calling AsncTask to make API call.and in onpostexecute we are handing response parsing.
Please suggest some alternate options which will not make much code changes and effective performance..
Thanks in Advance.......
Here I have 2 queries
Just 2? You sure about that?
1)Still Asynctask is working fine with Android 11 OS and below versions.Will it affect android 12 OS.
It's highly unlikely.
I haven't get any clear information about completely removal of Asynctask in android developer site also.
Correct. One would assume (hope) Google would make a very public announcement if and when they decide to remove it completely.
Do I need to take this as serious and have to update my whole project with the replacement of Asynctask?
You need to take this a warning that you should stop using AsyncTask and replace its use in your code if you have time.
And will it affect upcoming OS versions?
No one but someone at Google could answer that, and they're not going to.
2)If I want to replace that means what will be the best option without making much code changes. Even google suggested some API frameworks like concurrent and coroutines as the best replacement.But I didn't get idea about replacing in existing classes.Because in and every class we are calling AsncTask to make API call.and in onpostexecute we are handing response parsing.
"The best option" is going to depend on your code. Google around for "asynctask to coroutines" or something along those lines and you'll find plenty of blog posts on the subject.
Never messed with custom layout in Android.
What I'm basically trying to do is this:
The closest thing I've found is this, but didn't manage to make it work (tried for few hours and no result, it just won't show), and also it would require more work to make it look like the facebook's one.
I'd like to be able to call the toast everywhere from my app, too.
Thanks ahead.
I'm having quite tough problem while developing a testing framework for android apps. The text got a bit long so the actual question is in bold for those that don't want to read the context.
Basically, what I'd like to achieve right now is to trace user activity while he's using the application as one of the features. There's my app that manages context data all the time and developer's app - the one being tested. My idea to do this was to get coordinates where user touched the screen along with taking a screenshot simultaneously. Then I'd use the coordinates to mark the spot on the screenshot to get the idea of what user was doing the whole time with the app. Take hints on user experience and trace crashes.
Non-system apps cannot take a screenshot for security reasons, but application itself can take a screenshot of its Activities without much trouble for non-rooted users, e.g. like here. My only hope here is to interfere with developers' code to implement the functionality of doing so while my testing app is running. Each Activity then would have to extend my overridden Activity instead of regular one, implement an interface, implement broadcast receiver etc.
I am going to write a library for developer who would like his app to be tested with my framework. I'd like it to do the job for me and be as non-intrusive as it's possible for him to use. How to achieve that the best way?
Ideal case would assume linking the library to project with maybe a small addition in manifest that'd get the job done and after just unlinking, removing that bit of xml in manifest for production.
That's an open question. I don't expect any bits of code, but some nifty Java trick, Android OS functionality or even completely other approach that'd solve my problem
I tried to be as clear as possible with the question, but that's a quite tough matter for me to describe so that could have turned out contrary. Don't hesitate to ask me for more details, to speak my mind more clearly or even rewrite the question. Thank you all very much for help!
I'm going to build a music player working on both Android and Desktops. It won't be anything special, I'm doing it more to training myself and know more or less what problems I might encounter if I want to do a real app/program one day. Therefore, since I'm already rather decent at web technologies, I'll try to use something else: Java.
My app / program with have to
be able to read music files and play them (I'm planning on reading the files myself, meaning that I only need to be able to read "raw" sound, WAV or such)
be able to write to music files (to change tags)
be able to communicate with another instance of the program on another device that's on the same network (I want to be able to use my phone as a remote control and my pc as a remote control for my phone)
If possible, show some play/pause buttons on the screen even if it's locked (probably just on android)
And this is where I need your help: What you I do to write as little "device specific" code as possible?
It's obvious I can reuse classes used to encode/decode some music types. Finding the files, reading them, writing them, playing raw sound and connection to the network will be easy to abstract if needed.
But then there is the UI and it looks like if I don't plan carefully, I'll have to do it twice... I've seen libGDX but they kinda insist a lot on the fact it's for games...
All I need is some way to build a simple UI (a few buttons, the cover of the albums) that'd work for both the desktop and the phone.
Should I use libGDX, the "normal" libs (*WT, Swing, neither of which seem to be "compatible" with Android) or something else?
I'd also like to request as few permissions as possible. Meaning that I'd like to have a base music player that only request access to the sd card, and then features requiring additional permissions would be added as other apps/programs or addons.
From what I understood, the only way to achieve this is to create a second app and make the user install it. I think I'll manage to make the two apps communicate (with Intent?) but is it really the only solution?
Thank you in advance for your answers.
Maybe you could consider building the app with something such as Phonegap: http://phonegap.com/ This would let you use your web technologies strength and write a very slim layer of device specific code if any at all!
As for getting a phonegap app to run on the desktop....you could use something like :http://ripple.incubator.apache.org/ to have it run on the desktop. I know this is slightly different and you wanted to tackle writing something in Java - however this is the way mobile development is moving so you may want to get started like this!
So I was looking at the settings in CM10.1(4.2.2) and I saw an option to change the color of the softkeys using a color picker.
Now i'm working on an app and though doing something like that would be cool. But I don't understand how it does it. How does it change the color using code, and why doesn't it require a reboot?
Also, could I use a similar process to change the Colorado of the wi-fi inside my app as well? How would one do this. I am interested in how you can do this, as it would make a great addition to my app.
I saw I wasn't the only one wondering this, and I think this is a good question. If someone could, can you maybe explain what could be going on, and then explain how I could do it, and maybe give me a link to some code to take a look at?
Anything would help. I'm curious, but baffled. I think an answer could help not just me, but many others. Thanks!
Short answer: You can't using the public SDK.
Long answer: This is not a feature of stock AOSP. Cyanogenmod is a heavily modified version of Android, and features like this are implemented at a ROM level, not an app level. If you want to include this feature, you'll have to customize Android at a source level and build a system image for each and every device you want it on.
(Source - Google Employee)