Saturday, September 23, 2017
Wednesday, September 20, 2017
Moving Apps to the SD Card.
Now find an app that moves apps to the SD card.
Tuesday, September 19, 2017
Recently uploaded a new APK for W.A.R. II only to discover that it now supports exactly 0 devices. This even after I installed the APK on my own devices running Marshmallow and Nougat.
After e-mailing Google Support who did not identify anything specific in the manifest, I decided to add
and remove android:required = true from
Now the W.A.R. app supports 11268 devices.
Wednesday, August 23, 2017
Now I need to root the device in order to run Kali Linux. I also want to root, because I am a control freak.
Here are the steps assuming you already have ADB and Fastboot installed on your PC.
For kicks you may also want to visit the Asus support site for additional software tools.
Wednesday, July 19, 2017
Wednesday, July 12, 2017
I am writing a calendar app that will listen for clicks on dates and drive the remainder of the app's functions by date and user.
The reason I am posting this is that my fragments replaced the main activity okay on a Lollipop device, but not on Marshmallow
After many hours of frustration, I happened to tilt the Marshmallow phone just enough to have the external light source reveal that the fragment was indeed present on the main activity, but BEHIND IT. This was not readily detected because the backgrounds are the same color and size while the main activity layout was 100% opaque. It was my elevation shadow that showed another layer beneath the main activity
Shazam!!! This fixed that problem:
This may not be proper form, but I don't care as I must push on and build the server application to the mobile. Meanwhile, here are some screen shots of the actual source code that I built and compiled directly on a Samsung Tablet with AIDE.
Aha...the all important build.gradle file
Saturday, July 8, 2017
I started by reading the AWS documentation.
Get AWS account and create and Windows Server Instance - Already plenty of on-line documentation.
Saturday, July 1, 2017
RESOLUTION: Use the CORRECT constructor for ActionBarDrawerToggle:
ActionBarDrawerToggle (Activity activity,
Toolbar toolbar, ◄ - THIS IS THE KEY. Previously missing.
The main activity should extend AppCompatActivity.
and create an instance of android.support.v7.widget.Toolbar
There are plenty of full code examples online but remember to setSupportActionBar(toolbar); and that is it!
Here is what my build.gradle looks like:...
Thursday, June 29, 2017
First, the only thing that I changed in the last 6 months of use was the addition of another Google Account and perhaps OEM lock was checked/unchecked?
Regardless, the aforementioned companies should know how to do this:
Now I can resume on the fly development using AIDE
Forgot to mention that I will once again root following XDA so that I can remove bloatware and view the LogCat on the device.
Tuesday, June 27, 2017
So far, two clients:
Thursday, April 20, 2017
Wednesday, March 8, 2017
Monday, March 6, 2017
Not having to insert game CDs into the CD drive is a good reason to do this. I recently used BurnAware's "Copy to ISO" function.
Once you have the ISO (CD/DVD image) on your hard drive, you can use a virtual drive from Elaborate Bytes to mount the image.
Tuesday, February 28, 2017
I am unable to get past a flashing wallpaper screen after disabling system apps that I should NOT have disabled. STUPID!
Since I am quite fond of the 6 inch screen Android device, I am determined to get past this, but the ADB devices command reveals:
List of devices attached
Boo!http://www.mediafire.com/file/q4co2pz2iibt734/adbfastboot.zip http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ http://www.dominantwire.com/2012/11/how-to-install-adb-and-fastboot-on.html Copied contents of adbfastboot folder into existing and overwriting adb folder. System environment variables set to execute adb After I get:
C:\Users\thinkpad>adb devices adb server is out of date. killing... * daemon started successfully * List of devices attached 008808075227056M offline http://www.droidextra.net/install-adb-drivers-for-any-android-device/
After a long absence from the above nonsense, I simply followed the instructions at Imma Wake on YouTube
If the above did not work at all, then try Kingo Root.http://forum.xda-developers.com/showthread.php?t=2684210 http://linuxcommand.org/lts0070.php http://adbshell.com/commands/adb-shell-cp Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\adb>adb devices adb server is out of date. killing... * daemon started successfully * List of devices attached 310092303ce76300 device C:\adb>adb version Android Debug Bridge version 1.0.31 C:\adb> apt-get install android-tools-adb android-tools-fastboot
Monday, February 6, 2017
Saturday, January 7, 2017
After putting all the pieces together from resources on the internet like SimplifiedCoding, I am unable to consistently send messages to the app through the Firebase Console notification feature. The message is not always displayed on the device but appears to have been sent through Firebase.
Maybe this is the problem, maybe not.
"FCM usually delivers messages immediately after they are sent. However, this might not always be possible. For example, if the platform is Android, the device could be turned off, offline, or otherwise unavailable. FCM might intentionally delay messages to prevent an app from consuming excessive resources and negatively affecting battery life. When this happens, FCM stores the message and delivers it as soon as it's feasible. While this is fine in most cases, there are some apps for which a late message might as well never be delivered. For example, if the message is an incoming call or video chat notification, it is meaningful only for a short period of time before the call is terminated. Or if the message is an invitation to an event, it is useless if received after the event has ended. You can use the time_to_live parameter, supported in both HTTP and XMPP requests, to specify the maximum lifespan of a message. The value of this parameter must be a duration from 0 to 2,419,200 seconds, and it corresponds to the maximum period of time for which FCM stores and attempts to deliver the message. Requests that don't contain this field default to the maximum period of four weeks. Here are some possible uses for this feature: Video chat incoming calls Expiring invitation events Calendar events Another advantage of specifying the lifespan of a message is that FCM never throttles messages with a time_to_live (TTL) value of 0 seconds. In other words, FCM guarantees best effort for messages that must be delivered "now or never." Keep in mind that a time_to_live value of 0 means messages that can't be delivered immediately are discarded. However, because such messages are never stored, this provides the best latency for sending notification messages."