here is my latest app. its called Blimps and its very simple.
i often find myself doing something else with my phone while talking on it. like : SMS, chat, Mails...
by doing something else i always send my dialer to the background and loosing the control of my call options (mute, speaker, hangup...)
whenever i want to use my dialer options i need to stop what i was doing -> pull down the notification bar -> press the dialer -> use it (long time)
well... NO MORE.
With Blimps the dialer features floats (and movable) on top of your screen and you can do whatever whenever while talking with someone.
for now I've created 2 floating features which are Speaker & Hangup button. if all goes well i plan to release more handy features in the future.
As you all know Android has many OS UIs (Touchwiz, LG UI....) so it hasn't been tested on every one of them.
So if you can help me check Blimps on different UIs I'll appreciate your feedback.
Tested on :
- Nexus devices
- HTC One
- SGS 3/ 4
- LG G / G2
- Razar HD
Checkout short video:
- Compatible with Android 4.0+
- Floating End cal & Loud Speaker Buttons (more to come)
- dynamic positioning on screen
- proximity enable/disable to prevent clicking mistakes
- older phones with 4.0+ and LESS than 1GB ram might have resources issues
Seems to be working as advertised. Actually using it right now as I type. The speakerphone button works fine, and the end call button works fine. Very handy. However, when I switched from speaker to regular phone, my screen didn't shut off when I held it to my ear. I'll try it a few more times with and without your app running to see if it's my phone or the app.
Sent from my VS980 4G using XDA Premium 4 mobile app
Can u implement some features from Call Popout like grouping all the options under one movable head (like facebook chat head) and have more options like the call time, silence the ring, pick up, hang up... etc, as Call Popout development seems to be discontinued.
I found a BUG:
* It keeps the proximity sensor ON all the time (I can see the red light) after a call. Until I kill the Blimps process.
Also, for improvement, I think it needs to be implemented as some sort of Service, just so it's not being killed so easily. Virtually any kill app, even the same Android OS, will kill it since it's "just an app in the background". (or you can code it for Xposed Framework!)
The rest of the app seems to be working perfect! Tested for outgoing calls on Defy with CM11.
Just to be curious, why does it need connectivity access permission? Just to open playstore?
"And finally: The battery calibration is a myth! The /data/system/batterystats.bin file is not related to battery charge/life/status (exactly as Google devs stated earlier).
In case of our Defy, real battery status is synced with the battd status when you charge to 100%. That's all you need when changing ROMs or batteries!"
(From this thread)
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?